configure nova-compute use one vsphere cluster
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Medium
|
Irina Povolotskaya |
Bug Description
https:/
commit 47c5088be0ec448
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/
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-
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/
e.g. /etc/nova/
- 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: I675dd2b7cdeaca
Impelements: blueprint 1-1-nova-
Changed in fuel: | |
assignee: | nobody → Fuel Documentation Team (fuel-docs) |
Changed in fuel: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in fuel: | |
status: | Triaged → In Progress |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
AFAIK, this will be introduced in 6.1. /review. openstack. org/#/c/ 130446/
Nevertheless, I already have all stuff written (for 6.0)https:/
Once there are some major changes, please let me know.