Mmenkhof Nova Cloud Controller
- By Malte Menkhoff
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/stable | 1 | 19 Mar 2021 | |
latest/edge | 1 | 19 Mar 2021 |
juju deploy mmenkhof-nova-cloud-controller
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
-
bridge-interface | string
Default: br100
Bridge interface to be configured
-
bridge-ip | string
Default: 11.0.0.1
IP to be assigned to bridge interface
-
bridge-netmask | string
Default: 255.255.255.0
Netmask to be assigned to bridge interface
-
config-flags | string
Default: None
Comma separated list of key=value config flags to be set in nova.conf.
-
database | string
Default: nova
Database name
-
database-user | string
Default: nova
Username for database access
-
ha-bindiface | string
Default: eth0
Default network interface on which HA cluster will bind to communication with the other members of the HA Cluster.
-
ha-mcastport | int
Default: 5404
Default multicast port number that will be used to communicate between HA Cluster nodes.
-
network-manager | string
Default: FlatDHCPManager
Network manager for the cloud; supports the following options . FlatDHCPManager (nova-network) (default) FlatManager (nova-network) Neutron|Quantum (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.
-
neutron-database | string
Default: neutron
Database name for Neutron (if enabled)
-
neutron-database-user | string
Default: neutron
Username for Neutron database access (if enabled)
-
neutron-external-network | string
Default: ext_net
Name of the external network for floating IP addresses provided by Neutron.
-
nvp-cluster-name | string
Default: example
Name of the NVP cluster configuration to create (grizzly only)
-
nvp-controllers | string
Space delimited addresses of NVP controllers
-
nvp-l3-uuid | string
This is uuid of the default NVP L3 Gateway Service.
-
nvp-password | string
Default: admin
Password to connect to NVP controllers with
-
nvp-tz-uuid | string
This is uuid of the default NVP Transport zone that will be used for creating tunneled isolated Quantum networks. It needs to be created in NVP before starting Quantum with the nvp plugin.
-
nvp-username | string
Default: admin
Username to connect to NVP controllers with
-
openstack-origin | string
Default: distro
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:precise-folsom, cloud:precise-folsom/updates, cloud:precise-folsom/staging, cloud:precise-folsom/proposed. Note that updating this setting to a source that is known to provide a later version of OpenStack will trigger a software upgrade.
-
quantum-plugin | string
Default: ovs
Quantum plugin to use for network management; supports . ovs - OpenvSwitch Plugin nvp - Nicira Network Virtualization Platform . This configuration only has context when used with network-manager Quantum.
-
quantum-security-groups | string
Default: no
Use quantum for security group management. . Only supported for >= grizzly.
-
rabbit-user | string
Default: nova
Username used to access rabbitmq queue
-
rabbit-vhost | string
Default: openstack
Rabbitmq vhost
-
region | string
Default: RegionOne
OpenStack Region
-
ssl_ca | 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.
-
ssl_cert | 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 certficiate and key issued by Keystone (if it is configured to do so).
-
ssl_key | string
SSL key to use with certificate specified as ssl_cert.
-
use-syslog | boolean
If set to True, supporting services will log to syslog.
-
vip | string
Virtual IP to use to front API services in ha configuration
-
vip_cidr | int
Default: 24
Netmask that will be used for the Virtual IP
-
vip_iface | string
Default: eth0
Network Interface where to place the Virtual IP