ó
±EYc @s£dd
lm
Z

ddlmZ
dZe
jdddƒ

e
jddd	dd
ƒ
e
jddeddƒ
e
jd
ddƒ

e
jdddddddddƒ
e
jdddƒ

e
jdddddddƒ
e
jdddddƒ
e
j	dddddƒ
e
jd dd!dddd"ƒ
e
jd#dd$dd%ƒ
e
jd&dd'ƒ

e
jd(dd)ƒ

e
jd*dd+dd+dd,ƒ
e
jd-dd.dd+dd/ƒ
e
jd0dd1dddd2ƒ
e
jd3dedd4ƒ
e
jd5de
dd6ƒ
e
jd7dedd8ƒ
e
jd9dddddd:ƒ
e
jd;dd<dd=ƒ
e
jd>dd?dd@ƒ
e
jdAdedBe
ddCƒ
e
jdDdeddEƒ
gZe
jdFddGg
ddHƒ
e
jdIdej
dJƒ
ddKƒ
e
jdLddMddNƒ
e
jdOdejdPƒ
ddQƒ
e
jdRddddSƒ
e
jdTddUddddVƒ
e
jdWdgddXƒ
e
jdYdeddZƒ
e
jd[dgdd\ƒ
e
jd]dgdd^ƒ
e
jd_dd`ddaƒ
e
jdbddcdddƒ
e
jdeddfddgƒ
e
jdhdeddiƒ
e
jdjddkddlƒ
e
jdmdeddnƒ
e
jdoddpg
ddqƒ
e
jdrddddsƒ
e
j	dtdduddvƒ
e
jdwdd`ddxƒ
e
jdydd`ddzƒ
e
jd{dd|dd}ƒ
e
jd~dddd+dd€ƒ
e
jddedd‚ƒ
e
jdƒddkdddd„ƒ
e
jd…dd†dd‡ƒ
gZe
jdˆdd‰ddŠƒ
e
jd‹ddŒddƒ
e
jdŽddddd‘e
ƒ
e
jd’dd“dd”ƒ
e
jd•dd–g
dd—ƒ
e
jd˜dd™ddšƒ
e
jd›ddœddƒ
e
jdžddŸdd ƒ
e
jd¡dd¢dd£ƒ
e
jd¤dd¥dd¦ƒ
g
Ze
jd§dd¨dd©ƒ
g
Ze
jdªdd«dd¬ƒ
e
jd­dedd®ƒ
gZeeeeeZd¯„Zd°„Zd±S(²iÿÿÿÿ(
tcfg(
tpathssnova.network.api.APItflat_network_bridgethelpsf

This option determines the bridge used for simple network interfaces when no
bridge is specified in the VM creation request.

Please note that this option is only used when using nova-network instead of
Neutron in your deployment.

Possible values:

    Any string representing a valid network bridge, such as 'br100'

Related options:

    ``use_neutron``
tflat_network_dnstdefaults8.8.4.4s>

This is the address of the DNS server for a simple network. If this option is
not specified, the default of '8.8.4.4' is used.

Please note that this option is only used when using nova-network instead of
Neutron in your deployment.

Possible values:

    Any valid IP address.

Related options:

    ``use_neutron``
t
flat_injecteds!

This option determines whether the network setup information is injected into
the VM before it is booted. While it was originally designed to be used only by
nova-network, it is also used by the vmware and xenapi virt drivers to control
whether network information is injected into a VM.
tflat_interfaces#

This option is the name of the virtual interface of the VM on which the bridge
will be built. While it was originally designed to be used only by
nova-network, it is also used by libvirt for the bridge interface name.

Possible values:

    Any valid virtual interface name, such as 'eth0'
t
vlan_startidtmini
tmaxiþs–
This is the VLAN number used for private networks. Note that the when creating
the networks, if the specified number has already been assigned, nova-network
will increment this number until it finds an available VLAN.

Please note that this option is only used when using nova-network instead of
Neutron in your deployment. It also will be ignored if the configuration option
for `network_manager` is not set to the default of
'nova.network.manager.VlanManager'.

Possible values:

    Any integer between 1 and 4094. Values outside of that range will raise a
    ValueError exception. Default = 100.

Related options:

    ``network_manager``, ``use_neutron``
tvlan_interfaceså

This option is the name of the virtual interface of the VM on which the VLAN
bridge will be built. While it was originally designed to be used only by
nova-network, it is also used by libvirt and xenapi for the bridge interface
name.

Please note that this setting will be ignored in nova-network if the
configuration option for `network_manager` is not set to the default of
'nova.network.manager.VlanManager'.

Possible values:

    Any valid virtual interface name, such as 'eth0'
tnum_networkss6
This option represents the number of networks to create if not explicitly
specified when the network is created. The only time this is used is if a CIDR
is specified, but an explicit network_size is not. In that case, the subnets
are created by diving the IP address space of the CIDR by num_networks. The
resulting subnet sizes cannot be larger than the configuration option
`network_size`; in that event, they are reduced to `network_size`, and a
warning is logged.

Please note that this option is only used when using nova-network instead of
Neutron in your deployment.

Possible values:

    Any positive integer is technically valid, although there are practical
    limits based upon available IP address space and virtual interfaces. The
    default is 1.

Related options:

    ``use_neutron``, ``network_size``
tvpn_ips$my_ips
This is the public IP address for the cloudpipe VPN servers. It defaults to the
IP address of the host.

Please note that this option is only used when using nova-network instead of
Neutron in your deployment. It also will be ignored if the configuration option
for `network_manager` is not set to the default of
'nova.network.manager.VlanManager'.

Possible values:

    Any valid IP address. The default is $my_ip, the IP address of the VM.

Related options:

    ``network_manager``, ``use_neutron``, ``vpn_start``
t	vpn_startiès0
This is the port number to use as the first VPN port for private networks.

Please note that this option is only used when using nova-network instead of
Neutron in your deployment. It also will be ignored if the configuration option
for `network_manager` is not set to the default of
'nova.network.manager.VlanManager', or if you specify a value the 'vpn_start'
parameter when creating a network.

Possible values:

    Any integer representing a valid port number. The default is 1000.

Related options:

    ``use_neutron``, ``vpn_ip``, ``network_manager``
tnetwork_sizei
sÓ

This option determines the number of addresses in each private subnet.

Please note that this option is only used when using nova-network instead of
Neutron in your deployment.

Possible values:

    Any positive integer that is less than or equal to the available network
    size. Note that if you are creating multiple networks, they must all fit in
    the available IP address space. The default is 256.

Related options:

    ``use_neutron``, ``num_networks``
tfixed_range_v6s	fd00::/48s-

This option determines the fixed IPv6 address block when creating a network.

Please note that this option is only used when using nova-network instead of
Neutron in your deployment.

Possible values:

    Any valid IPv6 CIDR. The default value is "fd00::/48".

Related options:

    ``use_neutron``
tgateways

This is the default IPv4 gateway. It is used only in the testing suite.

Please note that this option is only used when using nova-network instead of
Neutron in your deployment.

Possible values:

    Any valid IP address.

Related options:

    ``use_neutron``, ``gateway_v6``
t
gateway_v6s

This is the default IPv6 gateway. It is used only in the testing suite.

Please note that this option is only used when using nova-network instead of
Neutron in your deployment.

Possible values:

    Any valid IP address.

Related options:

    ``use_neutron``, ``gateway``
tcnt_vpn_clientsisz

This option represents the number of IP addresses to reserve at the top of the
address range for VPN clients. It also will be ignored if the configuration
option for `network_manager` is not set to the default of
'nova.network.manager.VlanManager'.

Possible values:

    Any integer, 0 or greater. The default is 0.

Related options:

    ``use_neutron``, ``network_manager``
tfixed_ip_disassociate_timeoutiXs@

This is the number of seconds to wait before disassociating a deallocated fixed
IP address. This is only used with the nova-network service, and has no effect
when using neutron for networking.

Possible values:

    Any integer, zero or greater. The default is 600 (10 minutes).

Related options:

    ``use_neutron``
t"create_unique_mac_address_attemptsis

This option determines how many times nova-network will attempt to create a
unique MAC address before giving up and raising a
`VirtualInterfaceMacAddressException` error.

Possible values:

    Any positive integer. The default is 5.

Related options:

    ``use_neutron``
tteardown_unused_network_gatewaysÔ
Determines whether unused gateway devices, both VLAN and bridge, are deleted if
the network is in nova-network VLAN mode and is multi-hosted.

Related options:

    ``use_neutron``, ``vpn_ip``, ``fake_network``
tforce_dhcp_releases˜
When this option is True, a call is made to release the DHCP for the instance
when that instance is terminated.

Related options:

    ``use_neutron``
tupdate_dns_entriessË
When this option is True, whenever a DNS entry must be updated, a fanout cast
message is sent to all network hosts to update their DNS entries in multi-host
mode.

Related options:

    ``use_neutron``
tdns_update_periodic_intervals


This option determines the time, in seconds, to wait between refreshing DNS
entries for the network.

Possible values:

    Either -1 (default), or any positive integer. A negative value will disable
    the updates.

Related options:

    ``use_neutron``
tdhcp_domaint	novalocals©
This option allows you to specify the domain for the DHCP server.

Possible values:

    Any string that is a valid domain name.

Related options:

    ``use_neutron``
tl3_libsnova.network.l3.LinuxNetL3sá
This option allows you to specify the L3 management library to be used.

Possible values:

    Any dot-separated string that represents the import path to an L3
    networking library.

Related options:

    ``use_neutron``
tshare_dhcp_addresstdeprecated_for_removals

THIS VALUE SHOULD BE SET WHEN CREATING THE NETWORK.

If True in multi_host mode, all compute hosts share the same dhcp address. The
same IP address used for DHCP will be added on each nova-network node which is
only visible to the VMs on the same host.

The use of this configuration has been deprecated and may be removed in any
release after Mitaka. It is recommended that instead of relying on this option,
an explicit value should be passed to 'create_networks()' as a keyword argument
with the name 'share_address'.
tuse_neutronsŽWhether to use Neutron or Nova Network as the back end for networking. Defaults to False (indicating Nova network).Set to True to use neutron.tdhcpbridge_flagfiles/etc/nova/nova-dhcpbridge.confsƒ

This option is a list of full paths to one or more configuration files for
dhcpbridge. In most cases the default path of '/etc/nova/nova-dhcpbridge.conf'
should be sufficient, but if you have special needs for configuring dhcpbridge,
you can change or add to this list.

Possible values

    A list of strings, where each string is the full path to a dhcpbridge
    configuration file.
t
networks_pathtnetworkss

The location where the network configuration files will be kept. The default is
the 'networks' directory off of the location where nova's Python module is
installed.

Possible values

    A string containing the full path to the desired configuration directory
tpublic_interfaceteth0s£
This is the name of the network interface for public IP addresses. The default
is 'eth0'.

Possible values:

    Any string representing a network interface name
t
dhcpbridgesnova-dhcpbridgesï
The location of the binary nova-dhcpbridge. By default it is the binary named
'nova-dhcpbridge' that is installed with all the other nova binaries.

Possible values:

    Any string representing the full path to the binary for dhcpbridge
trouting_source_ips®
This is the public IP address of the network host. It is used when creating a
SNAT rule.

Possible values:

    Any valid IP address

Related options:

    force_snat_range
tdhcp_lease_timei€Q
s~
The lifetime of a DHCP lease, in seconds. The default is 86400 (one day).

Possible values:

    Any positive integer value.
t
dns_servers<
Despite the singular form of the name of this option, it is actually a list of
zero or more server addresses that dnsmasq will use for DNS nameservers. If
this is not empty, dnsmasq will not read /etc/resolv.conf, but will only use
the servers specified in this option. If the option use_network_dns_servers is
True, the dns1 and dns2 servers from the network will be appended to this list,
and will be used as DNS servers, too.

Possible values:

    A list of strings, where each string is either an IP address or a FQDN.

Related options:

    use_network_dns_servers
tuse_network_dns_serverss×
When this option is set to True, the dns1 and dns2 servers for the network
specified by the user on boot will be used for DNS, as well as any specified in
the `dns_server` option.

Related options:

    dns_server
tdmz_cidrs¸
This option is a list of zero or more IP address ranges in your network's DMZ
that should be accepted.

Possible values:

    A list of strings, each of which should be a valid CIDR.
tforce_snat_ranges

This is a list of zero or more IP ranges that traffic from the
`routing_source_ip` will be SNATted to. If the list is empty, then no SNAT
rules are created.

Possible values:

    A list of strings, each of which should be a valid CIDR.

Related options:

    routing_source_ip
tdnsmasq_config_filetsÅ
The path to the custom dnsmasq configuration file, if any.

Possible values:

    The full path to the configuration file, or an empty string if there is no
    custom dnsmasq configuration file.
tlinuxnet_interface_drivers1nova.network.linux_net.LinuxBridgeInterfaceDrivers`

This is the class used as the ethernet device driver for linuxnet bridge
operations. The default value should be all you need for most cases, but if you
wish to use a customized class, set this option to the full dot-separated
import path for that class.

Possible values:

    Any string representing a dot-separated class path that Nova can import.
tlinuxnet_ovs_integration_bridgesbr-ints¨
The name of the Open vSwitch bridge that is used with linuxnet when connecting
with Open vSwitch."

Possible values:

    Any string representing a valid bridge name.
tsend_arp_for_has×
When True, when a device starts up, and upon binding floating IP addresses, arp
messages will be sent to ensure that the arp caches on the compute hosts are
up-to-date.

Related options:

    send_arp_for_ha_count
tsend_arp_for_ha_countis

When arp messages are configured to be sent, they will be sent with the count
set to the value of this option. Of course, if this is set to zero, no arp
messages will be sent.

Possible values:

    Any integer greater than or equal to 0

Related options:

    send_arp_for_ha
tuse_single_default_gateways`
When set to True, only the firt nic of a VM will get its default gateway from
the DHCP server.
tforward_bridge_interfacetallsò
One or more interfaces that bridges can forward traffic to. If any of the items
in this list is the special keyword 'all', then all traffic will be forwarded.

Possible values:

    A list of zero or more interface names, or the word 'all'.
t
metadata_hostsÔ
This option determines the IP address for the network metadata API server.

Possible values:

   * Any valid IP address. The default is the address of the Nova API server.

Related options:

    * metadata_port
t
metadata_portiG"sj
This option determines the port used for the metadata API server.

Related options:

    * metadata_host
tiptables_top_regexs

This expression, if defined, will select any matching iptables rules and place
them at the top when applying metadata changes to the rules.

Possible values:

    * Any string representing a valid regular expression, or an empty string

Related options:

    * iptables_bottom_regex
tiptables_bottom_regexs

This expression, if defined, will select any matching iptables rules and place
them at the bottom when applying metadata changes to the rules.

Possible values:

    * Any string representing a valid regular expression, or an empty string

Related options:

    * iptables_top_regex
tiptables_drop_actiontDROPsŽ

By default, packets that do not pass the firewall are DROPped. In many cases,
though, an operator may find it more useful to change this from DROP to REJECT,
so that the user issuing those packets may have a better idea as to what's
going on, or LOGDROP in order to record the blocked traffic before DROPping.

Possible values:

    * A string representing an iptables chain. The default is DROP.
tovs_vsctl_timeoutixse

This option represents the period of time, in seconds, that the ovs_vsctl calls
will wait for a response from the database before timing out. A setting of 0
means that the utility should wait forever for a response.

Possible values:

    * Any positive integer if a limited timeout is desired, or zero if the
    calls should wait forever for a response.
tfake_networks[
This option is used mainly in testing to avoid calls to the underlying network
utilities.
tebtables_exec_attemptssÜ
This option determines the number of times to retry ebtables commands before
giving up. The minimum number of retries is 1.

Possible values:

    * Any positive integer

Related options:

    * ebtables_retry_interval
tebtables_retry_intervalgð?sm
This option determines the time, in seconds, that the system will sleep in
between ebtables retries. Note that each successive retry waits a multiple of
this value, so for example, if this is set to the default of 1.0 seconds, and
ebtables_exec_attempts is 4, after the first failure, the system will sleep for
1 * 1.0 seconds, after the second failure it will sleep 2 * 1.0 seconds, and
after the third failure it will sleep 3 * 1.0 seconds.

Possible values:

    * Any non-negative float or integer. Setting this to zero will result in no
    waiting between attempts.

Related options:

    * ebtables_exec_attempts
tldap_dns_urlsldap://ldap.example.com:389s0URL for LDAP server which will store DNS entriest
ldap_dns_users%uid=admin,ou=people,dc=example,dc=orgsUser for LDAP DNStldap_dns_passwordtpasswordsPassword for LDAP DNStsecrettldap_dns_soa_hostmastershostmaster@example.orgs5Hostmaster for LDAP DNS driver Statement of Authoritytldap_dns_serverssdns.example.orgsDNS Servers for LDAP DNS drivertldap_dns_base_dnsou=hosts,dc=example,dc=orgsBase DN for DNS entries in LDAPtldap_dns_soa_refresht1800sHRefresh interval (in seconds) for LDAP DNS driver Statement of Authoritytldap_dns_soa_retryt3600sFRetry interval (in seconds) for LDAP DNS driver Statement of Authoritytldap_dns_soa_expiryt86400sGExpiry interval (in seconds) for LDAP DNS driver Statement of Authoritytldap_dns_soa_minimumt7200sHMinimum interval (in seconds) for LDAP DNS driver Statement of Authoritytnetwork_driversnova.network.linux_nets"Driver to use for network creationt
network_topictnetworks!The topic network nodes listen ont
multi_hostsmDefault value for multi_host in networks. Also, if set, some rpc network calls will be sent directly to host.c

CsE|jt
ƒ

|jtƒ

|jtƒ

|jtƒ

|jtƒ

dS(
N(t
register_optstlinux_net_optstnetwork_optst
ldap_dns_optstdriver_optstrpcapi_opts(
tconf((sF/home/tvault/.virtenv/lib/python2.7/site-packages/nova/conf/network.pyRSýs









cCsi
td
6S(NtDEFAULT(
tALL_DEFAULT_OPTS(((sF/home/tvault/.virtenv/lib/python2.7/site-packages/nova/conf/network.pyt	list_optss
N(toslo_configRt	nova.confR
tNOVA_NET_APItStrOpttBoolOpttFalsetIntOpttPortOpttTrueRUtMultiStrOpttstate_path_deft
bindir_deftListOpttFloatOptRTRVRWRXR[RSR\(((sF/home/tvault/.virtenv/lib/python2.7/site-packages/nova/conf/network.pyt<module>s”