nova cloud controller #1

Supports: trusty

Add to new model


OpenStack is a reliable cloud infrastructure. Its mission is to produce
the ubiquitous cloud computing platform that will meet the needs of public
and private cloud providers regardless of size, by being simple to implement
and massively scalable.
. OpenStack Compute, codenamed Nova, is a cloud computing fabric controller. In
addition to its "native" API (the OpenStack API), it also supports the Amazon
. This charm provides the cloud controller service for OpenStack Nova and includes
nova-scheduler, nova-api and nova-conductor services.


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

Special considerations to be deployed using Postgresql

juju deploy nova-cloud-controller
juju deploy postgresql
juju add-relation "nova-cloud-controller:pgsql-nova-db" "postgresql:db"
juju add-relation "nova-cloud-controller:pgsql-neutron-db" "postgresql:db"

Deploying from source

The minimum openstack-origin-git config required to deploy from source is:

openstack-origin-git: include-file://nova-juno.yaml

    - {name: requirements,
       repository: 'git://',
       branch: stable/juno}
    - {name: nova,
       repository: 'git://',
       branch: stable/juno}

Note that there are only two 'name' values the charm knows about: 'requirements'
and 'nova'. These repositories must correspond to these 'name' values.
Additionally, the requirements repository must be specified first and the
nova repository must be specified last. All other repositories are installed
in the order in which they are specified.

The following is a full list of current tip repos (may not be up-to-date):

openstack-origin-git: include-file://nova-master.yaml

    - {name: requirements,
       repository: 'git://',
       branch: master}
    - {name: oslo-concurrency,
       repository: 'git://',
       branch: master}
    - {name: oslo-config,
       repository: 'git://',
       branch: master}
    - {name: oslo-context,
       repository: 'git://',
       branch: master}
    - {name: oslo-db,
       repository: 'git://',
       branch: master}
    - {name: oslo-i18n,
       repository: 'git://',
       branch: master}
    - {name: oslo-log,
       repository: 'git://',
       branch: master}
    - {name: oslo-messaging,
       repository: 'git://',
       branch: master}
    - {name: oslo-middleware,
       repository': 'git://',
       branch: master}
    - {name: oslo-rootwrap',
       repository: 'git://',
       branch: master}
    - {name: oslo-serialization,
       repository: 'git://',
       branch: master}
    - {name: oslo-utils,
       repository: 'git://',
       branch: master}
    - {name: pbr,
       repository: 'git://',
       branch: master}
    - {name: stevedore,
       repository: 'git://',
       branch: 'master'}
    - {name: sqlalchemy-migrate,
       repository: 'git://',
       branch: master}
    - {name: python-cinderclient,
       repository: 'git://',
       branch: master}
    - {name: python-glanceclient,
       repository': 'git://',
       branch: master}
    - {name: python-neutronlient,
       repository': 'git://',
       branch: master}
    - {name: keystonemiddleware,
       repository: 'git://',
       branch: master}
    - {name: nova,
       repository: 'git://',
       branch: master}

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:

  charm: cs:xenial/nova-cloud-controller
  num_units: 1
    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.


(boolean) If True enables openstack upgrades for this charm via juju actions. You will still need to set openstack-origin to the new repository but instead of an upgrade running automatically across all units, it will wait for you to execute the openstack-upgrade action for this charm on each unit. If False it will revert to existing behavior of upgrading all units on config change.
(string) The API rate-limit rules to use for the deployed nova API, if any. Contents of this config options will be inserted in the api-paste.ini file under the "filter:ratelimit" section as "limits". The syntax for these rules is documented at
(string) Bridge interface to be configured
(string) IP to be assigned to bridge interface
(string) Netmask to be assigned to bridge interface
(string) Comma-separated list of key=value config flags. These values will be placed in the nova.conf [DEFAULT] section.
(string) Protocol to use when accessing virtual machine console. Supported types are None, spice, xvpvnc, novnc and vnc (for both xvpvnc and novnc)
(string) Console keymap
(string) If console-access-protocol != None then this is the ip published to clients for access to console proxy. Set to local for the ip address of the nova-cloud-controller serving the request to be used
(string) Used for encrypted console connections. This differs from the SSL certificate used for API endpoints and is used for console sessions only. Setting this value along with console-ssl-key will enable encrypted console sessions. This has nothing to do with Nova API SSL and can be used independently. This can be used in conjunction when console-access-protocol is set to 'novnc' or 'spice'.
(string) SSL key to use with certificate specified as console-ssl-cert.
(float) The per physical core -> virtual core ratio to use in the Nova scheduler. . Increasing this value will increase instance density on compute nodes at the expense of instance performance.
(string) Database name
(string) Username for database access
(boolean) Enable debug logging.
(string) Default network interface on which HA cluster will bind to communication with the other members of the HA Cluster.
(int) Default multicast port number that will be used to communicate between HA Cluster nodes.
(int) Client timeout configuration in ms for haproxy, used in HA configurations. If not provided, default value of 30000ms is used.
(int) Connect timeout configuration in ms for haproxy, used in HA configurations. If not provided, default value of 5000ms is used.
(int) Queue timeout configuration in ms for haproxy, used in HA configurations. If not provided, default value of 5000ms is used.
(int) Server timeout configuration in ms for haproxy, used in HA configurations. If not provided, default value of 30000ms is used.
(string) Apply system hardening. Supports a space-delimited list of modules to run. Supported modules currently include os, ssh, apache and mysql.
(string) Used by the nrpe-external-master subordinate charm. A string that will be prepended to instance name to set the host name in nagios. So for instance the hostname would be something like: juju-myservice-0 If you're running multiple environments with the same services in them this allows you to differentiate between them.
(string) A comma-separated list of nagios servicegroups. If left empty, the nagios_context will be used as the servicegroup.
(string) Network manager for the cloud; supports the following options: FlatDHCPManager (nova-network) (default) FlatManager (nova-network) Neutron (Full SDN solution) When using the Neutron option you will most likely want to use the neutron-gateway charm to provide L3 routing and DHCP Services.
(string) Name of the external network for floating IP addresses provided by Neutron.
(string) Comma-separated list of key=value sqlalchemy related config flags to be set in nova.conf [database] section.
(string) Repository from which to install. May be one of the following: distro (default), ppa:somecustom/ppa, a deb url sources entry, or a supported Cloud Archive release pocket. Supported Cloud Archive sources include: cloud:<series>-<openstack-release> cloud:<series>-<openstack-release>/updates cloud:<series>-<openstack-release>/staging cloud:<series>-<openstack-release>/proposed For series=Precise we support cloud archives for openstack-release: * icehouse For series=Trusty we support cloud archives for openstack-release: * juno * kilo * ... NOTE: updating this setting to a source that is known to provide a later version of OpenStack will trigger a software upgrade. NOTE: when openstack-origin-git is specified, openstack specific packages will be installed from source rather than from the openstack-origin repository.
(string) Specifies a YAML-formatted dictionary listing the git repositories and branches from which to install OpenStack and its dependencies. Note that the installed config files will be determined based on the OpenStack release of the openstack-origin option. For more details see
(string) The IP address and netmask of the OpenStack Admin network (e.g. This network will be used for admin endpoints.
(string) The IP address and netmask of the OpenStack Internal network (e.g. This network will be used for internal endpoints.
(string) The hostname or address of the public endpoints provided by the nova-cloud-controller in the keystone identity provider. This value will be used for public endpoints. For example, an os-public-hostname set to '' with ssl enabled will create public endpoints such as:$(tenant_id)s
(string) The IP address and netmask of the OpenStack Public network (e.g. This network will be used for public endpoints.
(boolean) This is used to make sure that juju doesn't run config hook.
(boolean) If True enables IPv6 support. The charm will expect network interfaces to be configured with an IPv6 address. If set to False (default) IPv4 is expected. NOTE: these charms do not currently support IPv6 privacy extension. In order for this charm to function correctly, the privacy extension must be disabled and a non-temporary address must be configured/available on your network interface.
(string) Username used to access rabbitmq queue
(string) Rabbitmq vhost
(float) The physical ram -> virtual ram ratio to use in the Nova scheduler. Increasing this value will increase instance density on compute nodes at the potential expense of instance performance.
(string) OpenStack Region
(string) List of filter class names to use for filtering hosts when not specified in the request.
(boolean) Ensure required relations are made and complete before allowing services to be started By default, services may be up and accepting API request from install onwards. Enabling this flag ensures that services will not be started until the minimum 'core relations' have been made between this charm and other charms. For this charm the following relations must be made: * shared-db or (pgsql-nova-db, pgsql-neutron-db) * amqp * identity-service
(boolean) When this configuration is set to True, a single instance of nova-consoleauth service will be running, this allows users to always authenticate against the same instance and avoid authentications issues when the token used was stored in a different instance. If memcached is being used to store the tokens, then it's recommended to change this configuration to False.
(string) SSL CA to use with the certificate and key provided - this is only required if you are providing a privately signed ssl_cert and ssl_key.
(string) SSL certificate to install and use for API ports. Setting this value and ssl_key will enable reverse proxying, point Nova's entry in the Keystone catalog to use https, and override any certificate and key issued by Keystone (if it is configured to do so).
(string) SSL key to use with certificate specified as ssl_cert.
(boolean) Openstack mostly defaults to using public endpoints for internal communication between services. If set to True this option will configure services to use internal endpoints where possible.
(boolean) Setting this to True will allow supporting services to log to syslog.
(boolean) Enable verbose logging.
(string) Virtual IP(s) to use to front API services in HA configuration. . If multiple networks are being used, a VIP should be provided for each network, separated by spaces.
(int) Default CIDR netmask to use for HA vip when it cannot be automatically determined.
(string) Default network interface to use for HA vip when it cannot be automatically determined.
(int) The CPU core multiplier to use when configuring worker processes for Nova and Neutron. By default, the number of workers for each daemon is set to twice the number of CPU cores a service unit has.