James Page Neutron Gateway Bug1773353

Channel Revision Published Runs on
latest/stable 0 19 Mar 2021
Ubuntu 18.04 Ubuntu 17.10 Ubuntu 16.04 Ubuntu 14.04
juju deploy james-page-neutron-gateway-bug1773353
Show information

Platform:

Ubuntu
18.04 17.10 16.04 14.04

Learn about configurations >

  • aa-profile-mode | string

    Default: disable

    Experimental enable apparmor profile. Valid settings: 'complain', 'enforce' or 'disable'. AA disabled by default.

  • action-managed-upgrade | 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.

  • bridge-mappings | string

    Default: physnet1:br-data

    Space-separated list of ML2 data bridge mappings with format <provider>:<bridge>.

  • data-port | string

    Space-delimited list of bridge:port mappings. Ports will be added to their corresponding bridge. The bridges will allow usage of flat or VLAN network types with Neutron and should match this defined in bridge-mappings. . Ports provided can be the name or MAC address of the interface to be added to the bridge. If MAC addresses are used, you may provide multiple bridge:mac for the same bridge so as to be able to configure multiple units. In this case the charm will run through the provided MAC addresses for each bridge until it finds one it can resolve to an interface name.

  • debug | boolean

    Enable debug logging.

  • dns-servers | string

    A comma-separated list of DNS servers which will be used by dnsmasq as forwarders.

  • dnsmasq-flags | string

    Comma-separated list of key=value config flags with the additional dhcp options for neutron dnsmasq.

  • enable-isolated-metadata | boolean

    Enable metadata on an isolated network (no router ports).

  • enable-l3-agent | boolean

    Default: True

    Optional configuration to support use of linux router Note that this is used only for Cisco n1kv plugin.

  • enable-metadata-network | boolean

    The metadata network is used by solutions which do not leverage the l3 agent for providing access to the metadata service.

  • ext-port | string

    [DEPRECATED] Use bridge-mappings and data-port to create a network which can be used for external connectivity. You can call the network external and the bridge br-ex by convention, but neither is required. . Space-delimited 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 (eth0)

  • 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.

  • flat-network-providers | string

    Space-delimited list of Neutron flat network providers.

  • ha-bindiface | string

    Default: eth0

    Default network interface on which HA cluster will bind to communicate with the other members of the HA Cluster.

  • ha-legacy-mode | boolean

    If True will enable Pacemaker to monitor the neutron-ha-monitor daemon on every neutron-gateway unit, which detects neutron agents status and reschedule resources hosting on failed agents, detects local errors and release resources when network is unreachable or do necessary recover tasks. This feature targets to < Juno which doesn't natively support HA in Neutron itself.

  • ha-mcastport | int

    Default: 5409

    Default multicast port number that will be used to communicate between HA Cluster nodes.

  • harden | string

    Apply system hardening. Supports a space-delimited list of modules to run. Supported modules currently include os, ssh, apache and mysql.

  • 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 accommodate the packet overhead of using GRE tunnels.

  • ipfix-target | string

    IPFIX target wit the format "IP_Address:Port". This will enable IPFIX exporting on all OVS bridges to the target, including br-int and br-ext.

  • nagios_context | string

    Default: juju

    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.

  • nagios_servicegroups | string

    A comma-separated list of Nagios service groups. If left empty, the nagios_context will be used as the servicegroup

  • nova-rabbit-user | string

    Default: nova

    RabbitMQ Nova user

  • nova-rabbit-vhost | string

    Default: openstack

    RabbitMQ Nova Virtual Host

  • 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 Ubuntu Cloud Archive, e.g. . cloud:<series>-<openstack-release> cloud:<series>-<openstack-release>/updates cloud:<series>-<openstack-release>/staging cloud:<series>-<openstack-release>/proposed . See https://wiki.ubuntu.com/OpenStack/CloudArchive for info on which cloud archives are available and supported. . NOTE: updating this setting to a source that is known to provide a later version of OpenStack will trigger a software upgrade unless action-managed-upgrade is set to True.

  • os-data-network | string

    The IP address and netmask of the OpenStack Data network (e.g. 192.168.0.0/24) . This network will be used for tenant network traffic in overlay networks.

  • plugin | string

    Default: ovs

    Network configuration plugin to use for quantum. Supported values include: . ovs - ML2 + Open vSwitch nsx - VMware NSX n1kv - Cisco N1kv ovs-odl - ML2 + Open vSwitch with OpenDayLight Controller

  • 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

  • sysctl | string

    YAML-formatted associative array of sysctl key/value pairs to be set persistently e.g. '{ kernel.pid_max : 4194303 }'.

  • use-syslog | boolean

    Setting this to True will allow supporting services to log to syslog.

  • verbose | boolean

    Enable verbose logging.

  • vlan-ranges | string

    Default: physnet1:1000:2000

    Space-delimited list of <physical_network>:<vlan_min>:<vlan_max> or <physical_network> specifying physical_network names usable for VLAN provider and tenant networks, as well as ranges of VLAN tags on each available for allocation to tenant networks.

  • worker-multiplier | float

    The CPU core multiplier to use when configuring worker processes for this service. By default, the number of workers for each daemon is set to twice the number of CPU cores a service unit has. When deployed in a LXD container, this default value will be capped to 4 workers unless this configuration option is set.