-Add preferdirect table column to indicate a preference for not going through a hypervisor management if not required

-Add cluster column to hypervisor table to allow informing underlying virtualization technology of hypervisor groupings.


git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@4272 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
This commit is contained in:
jbjohnso 2009-09-30 21:33:54 +00:00
parent 8f888d7181
commit 4a90af84da

View File

@ -60,14 +60,16 @@ vm => {
}
},
hypervisor => {
cols => [qw(node mgr netmap defaultnet comments disable)],
cols => [qw(node mgr netmap defaultnet cluster preferdirect comments disable)],
keys => [qw(node)],
table_desc => 'Hypervisor parameters',
descriptions => {
'node' => 'The node or static group name',
mgr => 'The virtualization specific manager of this hypervisor when applicable',
'netmap' => 'Optional mapping of useful names to relevant physical ports. For example, 10ge=vmnic_16.0&vmnic_16.1,ge=vmnic1 would be requesting two virtual switches to be created, one called 10ge with vmnic_16.0 and vmnic_16.1 bonded, and another simply connected to vmnic1. Use of this allows abstracting guests from network differences amongst hypervisors',
'defaultnet' => 'Optionally specify a default network entity for guests to join to if they do not specify.'
'defaultnet' => 'Optionally specify a default network entity for guests to join to if they do not specify.',
'cluster' => 'Specify to the underlying virtualization infrastructure a cluster membership for the hypervisor.',
'preferdirect' => 'If a mgr is declared for a hypervisor, xCAT will default to using the mgr for all operations. If this is field is set to yes or 1, xCAT will prefer to directly communicate with the hypervisor if possible'
}
},
websrv => {