Difference between revisions of "Vnx-autoconf"
Line 2: | Line 2: | ||
== Command execution == | == 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: | ||
+ | <ul> | ||
+ | <li><filtree> to copy of files from the host to the virtual machines,</li> | ||
+ | <li><exec> to execute commands inside virtual machines, and</li> | ||
+ | <li><cmd-seq> to create composed command sequences. | ||
+ | </ul> | ||
+ | |||
+ | |||
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: | 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: |
Revision as of 18:22, 26 August 2015
Autoconfiguration and Command Execution (ACE)
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:
- <filtree> 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.
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....