configure nova-compute use one vsphere cluster

Bug #1403928 reported by OpenStack Infra
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Medium
Irina Povolotskaya

Bug Description

https://review.openstack.org/122242
commit 47c5088be0ec4486398b2db3196cfce82a661846
Author: Igor Zinovik <email address hidden>
Date: Wed Sep 17 03:07:28 2014 +0400

    configure nova-compute use one vsphere cluster

    - create separate directory '/etc/nova/nova-compute.d' where all
      configuration files that hold all configuration stanzas related to
      vmware compute driver
    - in simple mode we upload init script in appropriate directory and
      create symbolic links on it that are named like
      nova-compute-vmware-%cluster_id% ; script internally splits its own
      file name and extracts cluster name. This allow user to selectively
      start/stop nova-compute services.
    - Ubuntu init system (Upstart) requires initd service to be restarted,
      on CentOS we run '/bin/true'
    - create individual nova-compute configuration file per vSphere cluster;
      file is named `/etc/nova/nova-compute.d/vmware-%cluster_id%.conf',
      e.g. /etc/nova/nova-compute.d/vmware-0.conf
    - create appropriate corosync resource/primitive per nova-compute
      service in case of HA
    - currently we use same login and password for all nova-computes
    - set more strict access permissions (0600) on nova-compute.conf and
      generated files in `nova-compute.d' directory; these files hold
      sensitive information (credentials to vCenter server)
    - set 'multi_host' configuration stanza to False for both deployment
      modes (nonHA/HA)
    - add basic unit test coverage for provided functionality

    DocImpact
    Change-Id: I675dd2b7cdeacae1e703b82001dc2c855511e320
    Impelements: blueprint 1-1-nova-compute-vsphere-cluster-mapping

Changed in fuel:
assignee: nobody → Fuel Documentation Team (fuel-docs)
Stanislav Makar (smakar)
Changed in fuel:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Irina Povolotskaya (ipovolotskaya) wrote :

AFAIK, this will be introduced in 6.1.
Nevertheless, I already have all stuff written (for 6.0)https://review.openstack.org/#/c/130446/
Once there are some major changes, please let me know.

Changed in fuel:
assignee: Fuel Documentation Team (fuel-docs) → Irina (ipovolotskaya)
milestone: none → 6.1
tags: added: docs vcenter
Changed in fuel:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-docs (master)

Reviewed: https://review.openstack.org/130446
Committed: https://git.openstack.org/cgit/stackforge/fuel-docs/commit/?id=4f09f4c562b80808f2411099eb8d6a477c539333
Submitter: Jenkins
Branch: master

commit 4f09f4c562b80808f2411099eb8d6a477c539333
Author: irina povolotskaya <email address hidden>
Date: Thu Oct 23 10:55:28 2014 +0400

    Describes nova-compute-vCenter mapping

    * Remove limitation about 1-1 mapping in Planning Guide
    * Add description and scheme into Operations Guide

    Change-Id: If2936189068c0826a98e9caa264827baab554933
    Implements: blueprint 1-1-nova-compute-vsphere-cluster-mapping
    Closes-Bug: 1403928

Changed in fuel:
status: In Progress → Fix Committed
Changed in fuel:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.