Juju Charm - Nova Cloud Controller
Go to file
OpenDev Sysadmins c85d9043dd OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
2019-04-19 19:36:41 +00:00
actions Switch the charm to support py3 2018-10-18 15:43:03 +01:00
charmhelpers c-h: Separate certificates with lineseparator in bundles 2019-01-31 09:24:04 +01:00
files Switch the charm to support py3 2018-10-18 15:43:03 +01:00
hooks service: updates nova-api-os-compute service to use apache wsgi 2019-02-15 09:47:39 +00:00
lib Update tox.ini files from release-tools gold copy 2016-09-09 19:43:30 +00:00
scripts Sync scripts/. 2013-04-09 11:31:23 -07:00
templates Disable BuildFailureWeigher 2019-03-05 12:42:39 +00:00
tests service: updates nova-api-os-compute service to use apache wsgi 2019-02-15 09:47:39 +00:00
unit_tests service: updates nova-api-os-compute service to use apache wsgi 2019-02-15 09:47:39 +00:00
.coveragerc Check in start of py redux. 2013-08-01 20:42:16 -07:00
.gitignore Block endpoint reg if cluster partially formed 2017-10-03 10:02:11 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:36:41 +00:00
.project Add pydev project 2013-09-20 17:36:24 +01:00
.pydevproject Add missing fetch helper 2013-09-23 14:26:04 +01:00
.testr.conf Add tox support 2015-10-30 15:28:07 +09:00
.zuul.yaml Reenable nova-cloud-controller unit tests 2018-10-31 08:13:50 +00:00
LICENSE Re-license charm as Apache-2.0 2016-07-03 16:38:27 +00:00
Makefile Update repo to do ch-sync from Git 2017-09-26 09:55:32 +02:00
README.md Drop postgresql support 2017-12-21 12:01:58 +00:00
actions.yaml Add action for running archive-deleted-rows 2018-01-12 14:11:16 +00:00
bindep.txt Remove charm-helpers from tests dir and use venv instead 2017-05-26 16:24:32 +00:00
charm-helpers-hooks.yaml Updates for stable branch creation 2018-11-19 14:21:14 -08:00
config.yaml Add nova-metadata service 2018-10-03 07:24:05 +00:00
copyright Re-license charm as Apache-2.0 2016-07-03 16:38:27 +00:00
hardening.yaml Add hardening support 2016-03-31 19:30:33 +01:00
icon.svg Update charm icon 2017-08-02 18:08:40 +01:00
metadata.yaml Add support for cells v2 2018-10-05 11:50:21 +00:00
requirements.txt Add nova-metadata service 2018-10-03 07:24:05 +00:00
revision [ivoks,r=] Add support for setting neutron-alchemy-flags 2014-07-16 15:50:01 +01:00
setup.cfg [yolanda] Add postgresql support 2014-03-31 12:56:09 +01:00
test-requirements.txt Update requirements 2018-10-03 13:10:49 -05:00
tox.ini fix tox python3 overrides 2018-10-31 19:32:58 +00:00

README.md

nova-cloud-controller

Cloud controller node for OpenStack nova. Contains nova-schedule, nova-api, nova-network and nova-objectstore.

If console access is required then console-proxy-ip should be set to a client accessible IP that resolves to the nova-cloud-controller. If running in HA mode then the public vip is used if console-proxy-ip is set to local. Note: The console access protocol is baked into a guest when it is created, if you change it then console access for existing guests will stop working

HA/Clustering

There are two mutually exclusive high availability options: using virtual IP(s) or DNS. In both cases, a relationship to hacluster is required which provides the corosync back end HA functionality.

To use virtual IP(s) the clustered nodes must be on the same subnet such that the VIP is a valid IP on the subnet for one of the node's interfaces and each node has an interface in said subnet. The VIP becomes a highly-available API endpoint.

At a minimum, the config option 'vip' must be set in order to use virtual IP HA. If multiple networks are being used, a VIP should be provided for each network, separated by spaces. Optionally, vip_iface or vip_cidr may be specified.

To use DNS high availability there are several prerequisites. However, DNS HA does not require the clustered nodes to be on the same subnet. Currently the DNS HA feature is only available for MAAS 2.0 or greater environments. MAAS 2.0 requires Juju 2.0 or greater. The clustered nodes must have static or "reserved" IP addresses registered in MAAS. The DNS hostname(s) must be pre-registered in MAAS before use with DNS HA.

At a minimum, the config option 'dns-ha' must be set to true and at least one of 'os-public-hostname', 'os-internal-hostname' or 'os-internal-hostname' must be set in order to use DNS HA. One or more of the above hostnames may be set.

The charm will throw an exception in the following circumstances: If neither 'vip' nor 'dns-ha' is set and the charm is related to hacluster If both 'vip' and 'dns-ha' are set as they are mutually exclusive If 'dns-ha' is set and none of the os-{admin,internal,public}-hostname(s) are set

Network Space support

This charm supports the use of Juju Network Spaces, allowing the charm to be bound to network space configurations managed directly by Juju. This is only supported with Juju 2.0 and above.

API endpoints can be bound to distinct network spaces supporting the network separation of public, internal and admin endpoints.

Access to the underlying MySQL instance can also be bound to a specific space using the shared-db relation.

To use this feature, use the --bind option when deploying the charm:

juju deploy nova-cloud-controller --bind "public=public-space internal=internal-space admin=admin-space shared-db=internal-space"

alternatively these can also be provided as part of a juju native bundle configuration:

nova-cloud-controller:
  charm: cs:xenial/nova-cloud-controller
  num_units: 1
  bindings:
    public: public-space
    admin: admin-space
    internal: internal-space
    shared-db: internal-space

NOTE: Spaces must be configured in the underlying provider prior to attempting to use them.

NOTE: Existing deployments using os-*-network configuration options will continue to function; these options are preferred over any network space binding provided if set.