Difference between revisions of "Vnx-autoconf"
(→Command execution) |
|||
Line 5: | Line 5: | ||
Users can directly interact with virtual machines through their consoles or management interfaces. However, in order to automate the execution of commands in virtual machines, VNX provides three tags for that purpose: | Users can directly interact with virtual machines through their consoles or management interfaces. However, in order to automate the execution of commands in virtual machines, VNX provides three tags for that purpose: | ||
<ul> | <ul> | ||
− | <li>< | + | <li><filetree> to copy of files from the host to the virtual machines,</li> |
<li><exec> to execute commands inside virtual machines, and</li> | <li><exec> to execute commands inside virtual machines, and</li> | ||
− | <li><cmd-seq> to create composed command sequences. | + | <li><cmd-seq> to create composed command sequences.</li> |
</ul> | </ul> | ||
+ | All of them have an attribute named "seq" that allows to associate a string identifier to them. This identifier is used to invoke the execution of that commands from the VNX command line. For example: | ||
+ | vnx -f tutorial_lxc_ubuntu.xml --execute start-www | ||
+ | will execute all the commands defined in 'tutorial_lxc_ubuntu.xml' with the attribute seq='start-www'. | ||
+ | The parameter passed to '--execute' option can be a comma-separated list of seq identifiers to allow executing several set of commands. For example: | ||
+ | vnx -f tutorial_lxc_ubuntu.xml --execute stop-www,start-www | ||
+ | will execute in sequentially the set of commands identified by 'stop-www' and 'start-www'. | ||
+ | |||
+ | === Copying files: <filetree> tag === | ||
+ | |||
+ | === Executing commands: <exec> tag === | ||
+ | |||
+ | === Creating composed command sequences: <cmd-seq> tag === | ||
Revision as of 19:37, 26 August 2015
Autoconfiguration and Command Execution (ACE)
Contents
Command execution
Users can directly interact with virtual machines through their consoles or management interfaces. However, in order to automate the execution of commands in virtual machines, VNX provides three tags for that purpose:
- <filetree> to copy of files from the host to the virtual machines,
- <exec> to execute commands inside virtual machines, and
- <cmd-seq> to create composed command sequences.
All of them have an attribute named "seq" that allows to associate a string identifier to them. This identifier is used to invoke the execution of that commands from the VNX command line. For example:
vnx -f tutorial_lxc_ubuntu.xml --execute start-www
will execute all the commands defined in 'tutorial_lxc_ubuntu.xml' with the attribute seq='start-www'. The parameter passed to '--execute' option can be a comma-separated list of seq identifiers to allow executing several set of commands. For example:
vnx -f tutorial_lxc_ubuntu.xml --execute stop-www,start-www
will execute in sequentially the set of commands identified by 'stop-www' and 'start-www'.
Copying files: <filetree> tag
Executing commands: <exec> tag
Creating composed command sequences: <cmd-seq> tag
The "ostype" attribute is used to specify the type of command included in <exec> tag, either command line (CLI) or graphical (GUI), and whether vnx tool waits for command execution end or not. For values are posible:
ostype | Type of commands | Waits for command execution end |
system | CLI | YES |
exec | CLI | NO |
xsystem | GUI | YES |
xexec | GUI | NO |
Autoconfiguration
To be completed....