Add 'compute-vmware' granular deployment task

Bug #1478854 reported by OpenStack Infra on 2015-07-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Medium
Fuel Documentation Team

Bug Description

https://review.openstack.org/196114
commit 0f6abf96c3a9bf2a43240df478c78cf475e98601
Author: Igor Zinovik <email address hidden>
Date: Fri Jun 26 18:27:06 2015 +0300

    Add 'compute-vmware' granular deployment task

    '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

Changed in fuel:
milestone: none → 7.0
assignee: nobody → Fuel Documentation Team (fuel-docs)
importance: Undecided → Medium
status: New → Confirmed
Igor Shishkin (teran) on 2015-10-08
Changed in fuel:
milestone: 7.0 → 8.0
Dmitry Pyzhov (dpyzhov) on 2015-10-22
tags: added: area-docs
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers