[
https://issues.apache.org/jira/browse/VCL-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995554#comment-15995554
]
ASF subversion and git services commented on VCL-1000:
------------------------------------------------------
Commit 1793702 from [email protected] in branch 'vcl/trunk'
[ https://svn.apache.org/r1793702 ]
VCL-1000
Added pre_reload directory for each OS under tools. Removed unwieldy x86*
directories under each stage directory.
> Run custom scripts at various stages on the management node
> -----------------------------------------------------------
>
> Key: VCL-1000
> URL: https://issues.apache.org/jira/browse/VCL-1000
> Project: VCL
> Issue Type: New Feature
> Components: vcld (backend)
> Reporter: Andy Kurth
> Assignee: Andy Kurth
> Fix For: 2.5
>
>
> There are cases where it would be useful to be able to have scripts executed
> on the management at various stages of reservations. For example, a script
> could be executed to configure an external firewall or provision storage when
> a computer is reserved. Whatever was configured specifically for the
> reservation could be reverted when the reservation ends by another script.
> We already have this functionality for scripts that get executed on the
> computer ([VCL-564|https://issues.apache.org/jira/browse/VCL-564]). However,
> there are situations where you would need to perform actions from the
> management node.
> The script would need access to information about the reservation. Since it
> resides and is executed on the management node, the script could call mysql
> to query the database. This isn't the safest way of handling things.
> Another option could be to create a text file on the management node prior to
> executing the script(s). The script could parse the text file to extract the
> information it requires.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
