0f6abf96c3
'compute-vmware' deployment task deploys nova-compute (VCDriver) on node
that got assigned 'compute-vmware' role:
- it installs nova-compute package
- prepares /etc/nova/nova-compute.conf file
- launches nova-compute service
It happens only if current node name (e.g. node-3) matches 'target_node'
attribute, it means that particuliar vSphere cluster was mapped to
current 'compute-vmware' node.
Change the way how nova-compute gets deployed on controller nodes
(vmware/manifests/compute/ha.pp): nova-compute deploys on controllers
only if 'target_node' attribute in contains 'controllers' value.
Diminish technical debt:
- remove references to 'common.libvirt_type.value'
- remove 'compute_driver' from manifests parameter list, it is inlined
into configuration templates
- Remove useless vmware_index() invocation
Implements: blueprint compute-vmware-role
DocImpact: document new role in User Guide (VMware integration notes),
update screenshots with VMware tab
Change-Id: I42ed40d86c5d43289fc210d426be523da545d268
|
||
|---|---|---|
| .. | ||
| ha.pp | ||