[
https://issues.apache.org/jira/browse/VCL-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15586065#comment-15586065
]
ASF subversion and git services commented on VCL-997:
-----------------------------------------------------
Commit 1765484 from [email protected] in branch 'vcl/trunk'
[ https://svn.apache.org/r1765484 ]
VCL-997
Added subroutines:
DataStructure.pm::get_reservation_info_json_string
OS.pm::get_reservation_info_json_file_path
OS.pm::create_reservation_info_json_file
OS.pm::delete_reservation_info_json_file
Windows.pm::get_reservation_info_json_file_path
utils.pm::prune_array_reference
utils.pm::prune_hash_child_references
utils.pm::prune_hash_reference
OS.pm::create_reservation_info_json_file gets called from reserved.pm::process
only if a variable named 'enable_experimental_features' is true in the database.
This file is removed when a computer is sanitized in
reclaim.pm::call_os_sanitize.
> Create reservation info file on reserved computer
> -------------------------------------------------
>
> Key: VCL-997
> URL: https://issues.apache.org/jira/browse/VCL-997
> Project: VCL
> Issue Type: New Feature
> Components: vcld (backend)
> Reporter: Andy Kurth
> Assignee: Andy Kurth
>
> It would be useful if a file was created on loaded computers containing
> various aspects of the reservation. Such a file could be used by post-load,
> post-reserve, and other scripts to customize the computer based on
> reservation information such as user accounts, account passwords, etc.
> One option would be a simple text file with key-value pairs. This is not
> optimal. Something more structured such as JSON would be better.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)