Cleanup config.yaml
Change-Id: Ib3d490db0acaef8b48e4151b2282e37fb6f595f3
This commit is contained in:
parent
663b614c6d
commit
73f531202a
601
config.yaml
601
config.yaml
|
@ -1,11 +1,11 @@
|
|||
options:
|
||||
debug:
|
||||
default: False
|
||||
type: boolean
|
||||
default: False
|
||||
description: Enable debug logging.
|
||||
verbose:
|
||||
default: False
|
||||
type: boolean
|
||||
default: False
|
||||
description: Enable verbose logging.
|
||||
use-syslog:
|
||||
type: boolean
|
||||
|
@ -13,44 +13,38 @@ options:
|
|||
description: |
|
||||
Setting this to True will allow supporting services to log to syslog.
|
||||
openstack-origin:
|
||||
default: distro
|
||||
type: string
|
||||
default: distro
|
||||
description: |
|
||||
Repository from which to install. May be one of the following:
|
||||
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:
|
||||
|
||||
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
|
||||
|
||||
For series=Precise we support cloud archives for openstack-release:
|
||||
* icehouse
|
||||
|
||||
For series=Trusty we support cloud archives for openstack-release:
|
||||
* juno
|
||||
* kilo
|
||||
* ...
|
||||
|
||||
.
|
||||
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.
|
||||
a later version of OpenStack will trigger a software upgrade unless
|
||||
action-managed-upgrade is set to True.
|
||||
openstack-origin-git:
|
||||
default:
|
||||
type: string
|
||||
default:
|
||||
description: |
|
||||
Specifies a default OpenStack release name, or a YAML dictionary
|
||||
listing the git repositories to install from.
|
||||
|
||||
.
|
||||
The default Openstack release name may be one of the following, where
|
||||
the corresponding OpenStack github branch will be used:
|
||||
* liberty
|
||||
* mitaka
|
||||
* newton
|
||||
* master
|
||||
|
||||
.
|
||||
The YAML must minimally include the following repositories, and may
|
||||
also include repositories for other dependencies:
|
||||
repositories:
|
||||
|
@ -73,38 +67,61 @@ options:
|
|||
repository: 'git://github.com/openstack/neutron',
|
||||
branch: master}
|
||||
release: master
|
||||
rabbit-user:
|
||||
default: neutron
|
||||
extra-key:
|
||||
type: string
|
||||
description: Username used to access rabbitmq queue
|
||||
rabbit-vhost:
|
||||
default: openstack
|
||||
default:
|
||||
description: Optional key for archive containing additional packages.
|
||||
extra-source:
|
||||
type: string
|
||||
description: Rabbitmq vhost
|
||||
database-user:
|
||||
default: neutron
|
||||
type: string
|
||||
description: Username for Neutron database access (if enabled)
|
||||
database:
|
||||
default: neutron
|
||||
type: string
|
||||
description: Database name for Neutron (if enabled)
|
||||
region:
|
||||
default: RegionOne
|
||||
type: string
|
||||
description: OpenStack Region
|
||||
use-internal-endpoints:
|
||||
default: False
|
||||
default:
|
||||
description: Optional source for archive containing additional packages.
|
||||
action-managed-upgrade:
|
||||
type: boolean
|
||||
default: False
|
||||
description: |
|
||||
Openstack mostly defaults to using public endpoints for
|
||||
internal communication between services. If set to True this option will
|
||||
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.
|
||||
harden:
|
||||
default:
|
||||
type: string
|
||||
description: |
|
||||
Apply system hardening. Supports a space-delimited list of modules
|
||||
to run. Supported modules currently include os, ssh, apache and mysql.
|
||||
rabbit-user:
|
||||
type: string
|
||||
default: neutron
|
||||
description: Username used to access rabbitmq queue.
|
||||
rabbit-vhost:
|
||||
type: string
|
||||
default: openstack
|
||||
description: Rabbitmq vhost name.
|
||||
database-user:
|
||||
type: string
|
||||
default: neutron
|
||||
description: Username for Neutron database access (if enabled).
|
||||
database:
|
||||
type: string
|
||||
default: neutron
|
||||
description: Database name for Neutron (if enabled).
|
||||
region:
|
||||
type: string
|
||||
default: RegionOne
|
||||
description: OpenStack region name.
|
||||
use-internal-endpoints:
|
||||
type: boolean
|
||||
default: False
|
||||
description: |
|
||||
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.
|
||||
neutron-security-groups:
|
||||
type: boolean
|
||||
default: False
|
||||
description: |
|
||||
Use quantum for security group management.
|
||||
description: Use Neutron for security group management.
|
||||
neutron-external-network:
|
||||
type: string
|
||||
default: ext_net
|
||||
|
@ -123,8 +140,8 @@ options:
|
|||
Please use the system-wide global-physnet-mtu setting which the
|
||||
agents will take into account when wiring VIFs.
|
||||
neutron-plugin:
|
||||
default: ovs
|
||||
type: string
|
||||
default: ovs
|
||||
description: |
|
||||
Neutron plugin to use for network management; supports
|
||||
.
|
||||
|
@ -136,8 +153,8 @@ options:
|
|||
plumgrid - PLUMgrid
|
||||
.
|
||||
overlay-network-type:
|
||||
default: gre
|
||||
type: string
|
||||
default: gre
|
||||
description: |
|
||||
Overlay network types to use, valid options include:
|
||||
.
|
||||
|
@ -164,55 +181,218 @@ options:
|
|||
default: "1001:2000"
|
||||
description: |
|
||||
Space-delimited list of <vxlan_min>:<vxlan_max> for VXLAN provider.
|
||||
# Quota configuration settings
|
||||
quota-security-group:
|
||||
default: 10
|
||||
enable-ml2-port-security:
|
||||
type: boolean
|
||||
default: False
|
||||
description: Enable port security extension for ML2 plugin (>= kilo).
|
||||
enable-ml2-dns:
|
||||
type: boolean
|
||||
default: False
|
||||
description: |
|
||||
Enables the Neutron DNS extension driver (>= mitaka). When enabled,
|
||||
ports attached to Nova instances will have DNS names assigned based
|
||||
on the instance name.
|
||||
haproxy-server-timeout:
|
||||
type: int
|
||||
default:
|
||||
description: |
|
||||
Server timeout configuration in ms for haproxy, used in HA
|
||||
configurations. If not provided, default value of 30000ms is used.
|
||||
haproxy-client-timeout:
|
||||
type: int
|
||||
default:
|
||||
description: |
|
||||
Client timeout configuration in ms for haproxy, used in HA
|
||||
configurations. If not provided, default value of 30000ms is used.
|
||||
haproxy-queue-timeout:
|
||||
type: int
|
||||
default:
|
||||
description: |
|
||||
Queue timeout configuration in ms for haproxy, used in HA
|
||||
configurations. If not provided, default value of 5000ms is used.
|
||||
haproxy-connect-timeout:
|
||||
type: int
|
||||
default:
|
||||
description: |
|
||||
Connect timeout configuration in ms for haproxy, used in HA
|
||||
configurations. If not provided, default value of 5000ms is used.
|
||||
enable-sriov:
|
||||
type: boolean
|
||||
default: False
|
||||
description: |
|
||||
Enable SR-IOV networking support across Neutron and Nova.
|
||||
midonet-origin:
|
||||
type: string
|
||||
default: midonet-2015.06
|
||||
description: |
|
||||
'mem-1.8', 'mem-1.9',
|
||||
'midonet-2015.06'
|
||||
.
|
||||
NOTE: updating this setting to a source that is known to provide a later
|
||||
version of MidoNet (do not change between MEM and MidoNet) will
|
||||
trigger a software upgrade.
|
||||
mem-username:
|
||||
type: string
|
||||
default:
|
||||
description: |
|
||||
The Midokura Enterprise MidoNet username credentials to access the
|
||||
repository.
|
||||
mem-password:
|
||||
type: string
|
||||
default:
|
||||
description: |
|
||||
The Midokura Enterprise MidoNet password credentials to access the
|
||||
repository.
|
||||
config-flags:
|
||||
type: string
|
||||
default:
|
||||
description: |
|
||||
Comma-separated list of key=value config flags. These values will be
|
||||
placed in the neutron.conf [DEFAULT] section.
|
||||
.
|
||||
WARNING: this is not the recommended way to configure the underlying
|
||||
services that this charm installs and is used at the user's own risk.
|
||||
This option is mainly provided as a stop-gap for users that either
|
||||
want to test the effect of modifying some config or who have found
|
||||
a critical bug in the way the charm has configured their services
|
||||
and need it fixed immediately. We ask that whenever this is used,
|
||||
that the user consider opening a bug on this charm at
|
||||
http://bugs.launchpad.net/charm-neutron-api providing an explanation of
|
||||
why the config was needed so that we may consider it for inclusion as a
|
||||
natively supported config in the the charm.
|
||||
default-tenant-network-type:
|
||||
type: string
|
||||
default:
|
||||
description: |
|
||||
The default type for a tenant network e.g. vxlan, vlan, gre etc
|
||||
global-physnet-mtu:
|
||||
type: int
|
||||
default: 1500
|
||||
description: |
|
||||
MTU of the underlying physical network. Neutron uses this value to
|
||||
calculate MTU for all virtual network components. For flat and
|
||||
VLAN networks, neutron uses this value without modification. For
|
||||
overlay networks such as VXLAN, neutron automatically subtracts
|
||||
the overlay protocol overhead from this value.
|
||||
.
|
||||
NOTE: This options is available starting from Mitaka release.
|
||||
path-mtu:
|
||||
type: int
|
||||
default:
|
||||
description: |
|
||||
Maximum size of an IP packet (MTU) that can traverse the
|
||||
underlying physical network infrastructure without fragmentation
|
||||
when using an overlay/tunnel protocol. This option allows
|
||||
specifying a physical network MTU value that differs from the
|
||||
default global-physnet-mtu value.
|
||||
dns-domain:
|
||||
type: string
|
||||
default: openstack.example.
|
||||
description: |
|
||||
Specifies the dns domain name that should be used for building instance
|
||||
hostnames. An empty option or the value of 'openstacklocal' will cause
|
||||
the dhcp agents to broadcast the default domain of openstacklocal and
|
||||
will not enable internal cloud dns resolution. This value should end
|
||||
with a '.', e.g. 'cloud.example.org.'.
|
||||
l2-population:
|
||||
type: boolean
|
||||
default: True
|
||||
description: |
|
||||
Populate the forwarding tables of virtual switches (LinuxBridge or OVS),
|
||||
to decrease broadcast traffics inside the physical networks fabric while
|
||||
using overlays networks (VXLan, GRE).
|
||||
manage-neutron-plugin-legacy-mode:
|
||||
type: boolean
|
||||
default: True
|
||||
description: |
|
||||
If True neutron-server will install neutron packages for the plugin
|
||||
configured.
|
||||
enable-dvr:
|
||||
type: boolean
|
||||
default: False
|
||||
description: |
|
||||
Enable Distributed Virtual Routing (juno and above).
|
||||
enable-l3ha:
|
||||
type: boolean
|
||||
default: False
|
||||
description: |
|
||||
Enable L3 HA (juno and above).
|
||||
max-l3-agents-per-router:
|
||||
type: int
|
||||
default: 2
|
||||
description: |
|
||||
Maximum number of l3 agents to host a router. Only used when enable-l3ha
|
||||
is True.
|
||||
min-l3-agents-per-router:
|
||||
default: 2
|
||||
type: int
|
||||
description: |
|
||||
Minimum number of l3 agents to host a router. Only used when enable-l3ha
|
||||
is True.
|
||||
dhcp-agents-per-network:
|
||||
type: int
|
||||
default: 1
|
||||
description: |
|
||||
The number of dhcp agents to be deployed per network. Note that if the
|
||||
Calico plugin is being used, this option has no effect.
|
||||
worker-multiplier:
|
||||
type: float
|
||||
default:
|
||||
description: |
|
||||
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.
|
||||
# Quota config
|
||||
quota-security-group:
|
||||
type: int
|
||||
default: 10
|
||||
description: |
|
||||
Number of security groups allowed per tenant. A negative value means
|
||||
unlimited.
|
||||
quota-security-group-rule:
|
||||
default: 100
|
||||
type: int
|
||||
default: 100
|
||||
description: |
|
||||
Number of security group rules allowed per tenant. A negative value means
|
||||
unlimited
|
||||
quota-network:
|
||||
default: 10
|
||||
type: int
|
||||
default: 10
|
||||
description: |
|
||||
Number of networks allowed per tenant. A negative value means unlimited.
|
||||
quota-subnet:
|
||||
default: 10
|
||||
type: int
|
||||
default: 10
|
||||
description: |
|
||||
Number of subnets allowed per tenant. A negative value means unlimited.
|
||||
quota-port:
|
||||
default: 50
|
||||
type: int
|
||||
default: 50
|
||||
description: |
|
||||
Number of ports allowed per tenant. A negative value means unlimited.
|
||||
quota-vip:
|
||||
default: 10
|
||||
type: int
|
||||
default: 10
|
||||
description: |
|
||||
Number of vips allowed per tenant. A negative value means unlimited.
|
||||
quota-pool:
|
||||
default: 10
|
||||
type: int
|
||||
default: 10
|
||||
description: |
|
||||
Number of pools allowed per tenant. A negative value means unlimited.
|
||||
quota-member:
|
||||
default: -1
|
||||
type: int
|
||||
default: -1
|
||||
description: |
|
||||
Number of pool members allowed per tenant. A negative value means
|
||||
unlimited. The default is unlimited because a member is not a real
|
||||
resource consumer on Openstack. However, on back-end, a member is a
|
||||
resource consumer and that is the reason why quota is possible.
|
||||
quota-health-monitors:
|
||||
default: -1
|
||||
type: int
|
||||
default: -1
|
||||
description: |
|
||||
Number of health monitors allowed per tenant. A negative value means
|
||||
unlimited.
|
||||
|
@ -225,18 +405,17 @@ options:
|
|||
description: |
|
||||
Number of routers allowed per tenant. A negative value means unlimited.
|
||||
quota-floatingip:
|
||||
default: 50
|
||||
type: int
|
||||
default: 50
|
||||
description: |
|
||||
Number of floating IPs allowed per tenant. A negative value means
|
||||
unlimited.
|
||||
# HA configuration settings
|
||||
# HA config
|
||||
dns-ha:
|
||||
type: boolean
|
||||
default: False
|
||||
description: |
|
||||
Use DNS HA with MAAS 2.0. Note if this is set do not set vip
|
||||
settings below.
|
||||
Use DNS HA with MAAS 2.0. Note if this is set do not set vip* settings.
|
||||
vip:
|
||||
type: string
|
||||
default:
|
||||
|
@ -267,15 +446,14 @@ options:
|
|||
type: int
|
||||
default: 5424
|
||||
description: |
|
||||
Default multicast port number that will be used to communicate between
|
||||
HA Cluster nodes.
|
||||
# Network configuration options
|
||||
# by default all access is over 'private-address'
|
||||
Default multicast port number that will be used to communicate between
|
||||
HA Cluster nodes.
|
||||
# Network config (by default all access is over 'private-address')
|
||||
os-admin-network:
|
||||
type: string
|
||||
default:
|
||||
description: |
|
||||
The IP address and netmask of the OpenStack Admin network (e.g.,
|
||||
The IP address and netmask of the OpenStack Admin network (e.g.
|
||||
192.168.0.0/24)
|
||||
.
|
||||
This network will be used for admin endpoints.
|
||||
|
@ -283,7 +461,7 @@ options:
|
|||
type: string
|
||||
default:
|
||||
description: |
|
||||
The IP address and netmask of the OpenStack Internal network (e.g.,
|
||||
The IP address and netmask of the OpenStack Internal network (e.g.
|
||||
192.168.0.0/24)
|
||||
.
|
||||
This network will be used for internal endpoints.
|
||||
|
@ -291,7 +469,7 @@ options:
|
|||
type: string
|
||||
default:
|
||||
description: |
|
||||
The IP address and netmask of the OpenStack Public network (e.g.,
|
||||
The IP address and netmask of the OpenStack Public network (e.g.
|
||||
192.168.0.0/24)
|
||||
.
|
||||
This network will be used for public endpoints.
|
||||
|
@ -335,9 +513,9 @@ options:
|
|||
type: string
|
||||
default:
|
||||
description: |
|
||||
SSL certificate to install and use for API ports. Setting this value
|
||||
SSL certificate to install and use for API ports. Setting this value
|
||||
and ssl_key will enable reverse proxying, point Neutron's entry in the
|
||||
Keystone catalog to use https, and override any certficiate and key
|
||||
Keystone catalog to use https, and override any certificate and key
|
||||
issued by Keystone (if it is configured to do so).
|
||||
ssl_key:
|
||||
type: string
|
||||
|
@ -349,7 +527,35 @@ options:
|
|||
description: |
|
||||
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.
|
||||
# Neutron Nuage plugin (VSD) configuration
|
||||
prefer-ipv6:
|
||||
type: boolean
|
||||
default: False
|
||||
description: |
|
||||
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.
|
||||
# Monitoring config
|
||||
nagios_context:
|
||||
type: string
|
||||
default: "juju"
|
||||
description: |
|
||||
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 are running multiple environments with the same services in them
|
||||
this allows you to differentiate between them.
|
||||
nagios_servicegroups:
|
||||
type: string
|
||||
default: ""
|
||||
description: |
|
||||
A comma-separated list of nagios servicegroups. If left empty, the
|
||||
nagios_context will be used as the servicegroup
|
||||
# Nuage plugin (VSD) config
|
||||
nuage-packages:
|
||||
type: string
|
||||
default: "nuage-openstack-neutron nuagenetlib"
|
||||
|
@ -361,15 +567,16 @@ options:
|
|||
default:
|
||||
description: |
|
||||
CMS ID is used as an authentication token from VSD to CMS.
|
||||
This value is being generated via nuage scripts and can be set pre/post deployment.
|
||||
This value is being generated via nuage scripts and can be set pre/post
|
||||
deployment.
|
||||
vsd-cms-name:
|
||||
type: string
|
||||
default:
|
||||
description: |
|
||||
This is required only for 3.2 R4 and above releases of Nuage and Kilo.
|
||||
Please give Maas env id so that it is unique per openstack cluster.
|
||||
This name is used to create th CMS ID on Nuage-VSD which should be unique per OSP cluster.
|
||||
Your Deployment will fail if this config is not provided.
|
||||
Please give Maas env id so that it is unique per openstack cluster. This
|
||||
name is used to create th CMS ID on Nuage-VSD which should be unique per
|
||||
OSP cluster. Your Deployment will fail if this config is not provided.
|
||||
vsd-server:
|
||||
type: string
|
||||
default:
|
||||
|
@ -398,36 +605,7 @@ options:
|
|||
type: string
|
||||
default: juju-enterprise
|
||||
description: Name of the Organization or Enterprise to create in Nuage VSD
|
||||
# end of Nuage VSD configuration
|
||||
l2-population:
|
||||
type: boolean
|
||||
default: True
|
||||
description: |
|
||||
Populate the forwarding tables of virtual switches (LinuxBridge or OVS),
|
||||
to decrease broadcast traffics inside the physical networks fabric while
|
||||
using overlays networks (VXLan, GRE).
|
||||
prefer-ipv6:
|
||||
type: boolean
|
||||
default: False
|
||||
description: |
|
||||
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.
|
||||
worker-multiplier:
|
||||
type: float
|
||||
default:
|
||||
description: |
|
||||
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.
|
||||
# VMware NSX plugin configuration
|
||||
# VMware NSX plugin config
|
||||
nsx-controllers:
|
||||
type: string
|
||||
default:
|
||||
|
@ -445,223 +623,30 @@ options:
|
|||
default:
|
||||
description: |
|
||||
This is uuid of the default NSX Transport zone that will be used for
|
||||
creating tunneled isolated Quantum networks. It needs to be created
|
||||
in NSX before starting Quantum with the nsx plugin.
|
||||
creating tunneled isolated Neutron networks. It needs to be created in
|
||||
NSX before starting Neutron with the nsx plugin.
|
||||
nsx-l3-uuid:
|
||||
type: string
|
||||
default:
|
||||
description: |
|
||||
This is uuid of the default NSX L3 Gateway Service.
|
||||
# end of NSX configuration
|
||||
nagios_context:
|
||||
default: "juju"
|
||||
type: string
|
||||
description: |
|
||||
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.
|
||||
enable-dvr:
|
||||
default: False
|
||||
type: boolean
|
||||
description: |
|
||||
Enable Distributed Virtual Routing (juno and above).
|
||||
enable-l3ha:
|
||||
default: False
|
||||
type: boolean
|
||||
description: |
|
||||
Enable L3 HA (juno and above).
|
||||
max-l3-agents-per-router:
|
||||
default: 2
|
||||
type: int
|
||||
description: |
|
||||
Maximum number of l3 agents to host a router. Only used when enable-l3ha
|
||||
is True
|
||||
min-l3-agents-per-router:
|
||||
default: 2
|
||||
type: int
|
||||
description: |
|
||||
Minimum number of l3 agents to host a router. Only used when enable-l3ha
|
||||
is True
|
||||
dhcp-agents-per-network:
|
||||
default: 1
|
||||
type: int
|
||||
description: |
|
||||
The number of dhcp agents to be deployed per network. Note that if the
|
||||
Calico plugin is being used, this option has no effect.
|
||||
nagios_servicegroups:
|
||||
default: ""
|
||||
type: string
|
||||
description: |
|
||||
A comma-separated list of nagios servicegroups.
|
||||
If left empty, the nagios_context will be used as the servicegroup
|
||||
# PLUMgrid Plugin configuration
|
||||
description: This is uuid of the default NSX L3 Gateway Service.
|
||||
# PLUMgrid Plugin config
|
||||
plumgrid-username:
|
||||
default: plumgrid
|
||||
type: string
|
||||
default: plumgrid
|
||||
description: Username to access PLUMgrid Director
|
||||
plumgrid-password:
|
||||
default: plumgrid
|
||||
type: string
|
||||
default: plumgrid
|
||||
description: Password to access PLUMgrid Director
|
||||
plumgrid-virtual-ip:
|
||||
default:
|
||||
type: string
|
||||
default:
|
||||
description: IP address of PLUMgrid Director
|
||||
# end of PLUMgrid configuration
|
||||
manage-neutron-plugin-legacy-mode:
|
||||
type: boolean
|
||||
default: True
|
||||
description: |
|
||||
If True neutron-server will install neutron packages for the plugin
|
||||
configured.
|
||||
# Additional software source configuration
|
||||
extra-key:
|
||||
type: string
|
||||
default:
|
||||
description: Optional key for archive containing additional packages.
|
||||
extra-source:
|
||||
type: string
|
||||
default:
|
||||
description: Optional source for archive containing additional packages.
|
||||
|
||||
# Calico plugin configuration
|
||||
# Calico plugin config
|
||||
calico-origin:
|
||||
default:
|
||||
type: string
|
||||
default:
|
||||
description: |
|
||||
Repository from which to install Calico packages. If set, must be
|
||||
a PPA URL, of the form ppa:somecustom/ppa. Changing this value
|
||||
after installation will force an immediate software upgrade.
|
||||
# End of Calico plugin configuration
|
||||
action-managed-upgrade:
|
||||
type: boolean
|
||||
default: False
|
||||
description: |
|
||||
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.
|
||||
enable-ml2-port-security:
|
||||
type: boolean
|
||||
default: False
|
||||
description: Enable port security extension for ML2 plugin (>= kilo).
|
||||
enable-ml2-dns:
|
||||
type: boolean
|
||||
default: False
|
||||
description: |
|
||||
Enables the Neutron DNS extension driver (>= mitaka). When enabled,
|
||||
ports attached to Nova instances will have DNS names assigned based
|
||||
on the instance name.
|
||||
haproxy-server-timeout:
|
||||
type: int
|
||||
default:
|
||||
description: |
|
||||
Server timeout configuration in ms for haproxy, used in HA
|
||||
configurations. If not provided, default value of 30000ms is used.
|
||||
haproxy-client-timeout:
|
||||
type: int
|
||||
default:
|
||||
description: |
|
||||
Client timeout configuration in ms for haproxy, used in HA
|
||||
configurations. If not provided, default value of 30000ms is used.
|
||||
haproxy-queue-timeout:
|
||||
type: int
|
||||
default:
|
||||
description: |
|
||||
Queue timeout configuration in ms for haproxy, used in HA
|
||||
configurations. If not provided, default value of 5000ms is used.
|
||||
haproxy-connect-timeout:
|
||||
type: int
|
||||
default:
|
||||
description: |
|
||||
Connect timeout configuration in ms for haproxy, used in HA
|
||||
configurations. If not provided, default value of 5000ms is used.
|
||||
enable-sriov:
|
||||
type: boolean
|
||||
default: False
|
||||
description: |
|
||||
Enable SR-IOV networking support across Neutron and Nova.
|
||||
midonet-origin:
|
||||
default: midonet-2015.06
|
||||
type: string
|
||||
description: |
|
||||
'mem-1.8', 'mem-1.9',
|
||||
'midonet-2015.06'
|
||||
|
||||
NOTE: updating this setting to a source that is known to provide a later
|
||||
version of MidoNet (do not change between MEM and MidoNet) will
|
||||
trigger a software upgrade.
|
||||
mem-username:
|
||||
type: string
|
||||
default:
|
||||
description: |
|
||||
The Midokura Enterprise MidoNet username credentials to access the
|
||||
repository.
|
||||
mem-password:
|
||||
type: string
|
||||
default:
|
||||
description: |
|
||||
The Midokura Enterprise MidoNet password credentials to access the
|
||||
repository.
|
||||
harden:
|
||||
default:
|
||||
type: string
|
||||
description: |
|
||||
Apply system hardening. Supports a space-delimited list of modules
|
||||
to run. Supported modules currently include os, ssh, apache and mysql.
|
||||
config-flags:
|
||||
type: string
|
||||
default:
|
||||
description: |
|
||||
Comma-separated list of key=value config flags. These values will be
|
||||
placed in the neutron.conf [DEFAULT] section.
|
||||
.
|
||||
WARNING: this is not the recommended way to configure the underlying
|
||||
services that this charm installs and is used at the user's own risk.
|
||||
This option is mainly provided as a stop-gap for users that either
|
||||
want to test the effect of modifying some config or who have found
|
||||
a critical bug in the way the charm has configured their services
|
||||
and need it fixed immediately. We ask that whenever this is used,
|
||||
that the user consider opening a bug on this charm at
|
||||
http://bugs.launchpad.net/charms providing an explanation of why the
|
||||
config was needed so that we may consider it for inclusion as a
|
||||
natively supported config in the the charm.
|
||||
default-tenant-network-type:
|
||||
type: string
|
||||
default:
|
||||
description: |
|
||||
The default type for a tenant network e.g. vxlan, vlan, gre etc
|
||||
global-physnet-mtu:
|
||||
type: int
|
||||
default: 1500
|
||||
description: |
|
||||
MTU of the underlying physical network. Neutron uses this value to
|
||||
calculate MTU for all virtual network components. For flat and
|
||||
VLAN networks, neutron uses this value without modification. For
|
||||
overlay networks such as VXLAN, neutron automatically subtracts
|
||||
the overlay protocol overhead from this value.
|
||||
.
|
||||
NOTE: This options is available starting from Mitaka release.
|
||||
path-mtu:
|
||||
type: int
|
||||
default:
|
||||
description: |
|
||||
Maximum size of an IP packet (MTU) that can traverse the
|
||||
underlying physical network infrastructure without fragmentation
|
||||
when using an overlay/tunnel protocol. This option allows
|
||||
specifying a physical network MTU value that differs from the
|
||||
default global-physnet-mtu value.
|
||||
dns-domain:
|
||||
type: string
|
||||
default: openstack.example.
|
||||
description: |
|
||||
Specifies the dns domain name that should be used for building instance
|
||||
hostnames. An empty option or the value of 'openstacklocal' will cause
|
||||
the dhcp agents to broadcast the default domain of openstacklocal and
|
||||
will not enable internal cloud dns resolution. This value should end
|
||||
with a '.', e.g. 'cloud.example.org.'.
|
||||
|
|
Loading…
Reference in New Issue