Tribaal Quantum Gateway
- By Chris Glass
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/stable | 2 | 19 Mar 2021 | |
latest/edge | 2 | 19 Mar 2021 |
juju deploy tribaal-quantum-gateway
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
-
database | string
Default: nova
Database name
-
database-user | string
Default: nova
Username for database access
-
debug | boolean
Enable debug logging
-
ext-port | string
A space-separated list of external ports to use for routing of instance traffic to the external public network. Valid values are either MAC addresses (in which case only MAC addresses for interfaces without an IP address already assigned will be used), or interfaces in their canonical form ("/dev/ethX").
-
external-network-id | string
Optional configuration to set the external-network-id. Only needed when configuring multiple external networks and should be used in conjunction with run-internal-router.
-
instance-mtu | int
Configure DHCP services to provide MTU configuration to instances within the cloud. This is useful in deployments where its not possible to increase MTU on switches and physical servers to accomodate the packet overhead of using GRE tunnels.
-
openstack-origin | string
Default: distro
Optional configuration to support use of additional sources such as: . - ppa:myteam/ppa - cloud:precise-folsom/proposed - cloud:precise-folsom - deb http://my.archive.com/ubuntu main|KEYID . Note that quantum/neutron is only supported >= Folsom.
-
plugin | string
Default: ovs
Network configuration plugin to use for quantum. Supported values include: . ovs - OpenVSwitch nvp|nsx - Nicira NVP/VMware NSX
-
rabbit-user | string
Default: neutron
RabbitMQ user
-
rabbit-vhost | string
Default: openstack
RabbitMQ Virtual Host
-
run-internal-router | string
Default: all
Optional configuration to support how the L3 agent option handle_internal_only_routers is configured. all => Set to be true everywhere none => Set to be false everywhere leader => Set to be true on one node (the leader) and false everywhere else. Use leader and none when configuring multiple floating pools
-
use-syslog | boolean
If set to True, supporting services will log to syslog.
-
verbose | boolean
Enable verbose logging