ó
±EYc@s	
dd
lm
Z
ddlmZ
dZejeddddƒ
Zejdd	d
ddƒ
ej	dd	d
ddƒ
ej	dd	dddƒ
ej
dd	dddddƒ
gZejdd	e
ddƒ
ej	dd	ddeddƒ
gZeeZd„Zd„ZdS( iÿÿÿÿ(
tloading(
tcfgtneutronttitlesNeutron OptionsthelpsH
Configuration options for neutron (network connectivity as a service).
turltdefaultshttp://127.0.0.1:9696s

This option specifies the URL for connecting to Neutron.

Possible values:

* Any valid URL that points to the Neutron API service is appropriate here.
  This typically matches the URL returned for the 'network' service type
  from the Keystone service catalog.
tregion_namet	RegionOnesÀ

Region name for connecting to Neutron in admin context.

This option is used in multi-region setups. If there are two Neutron
servers running in two regions in two different machines, then two
services need to be created in Keystone with two different regions and
associate corresponding endpoints to those services. When requests are made
to Keystone, the Keystone service uses the region_name to determine the
region the request is coming from.
t
ovs_bridgesbr-intsÔ
Specifies the name of an integration bridge interface used by OpenvSwitch.
This option is used only if Neutron does not specify the OVS bridge name.

Possible values:

* Any string representing OVS bridge name.
textension_sync_intervaliXtminis6

Integer value representing the number of seconds to wait before querying
Neutron for extensions.  After this number of seconds the next time Nova
needs to create a resource in Neutron it will requery Neutron for the
extensions that it has loaded.  Setting value to 0 will refresh the
extensions with no wait.
tservice_metadata_proxys

When set to True, this option indicates that Neutron will be used to proxy
metadata requests and resolve instance ids. Otherwise, the instance ID must be
passed to the metadata request in the 'X-Instance-ID' header.

Related options:

* metadata_proxy_shared_secret
tmetadata_proxy_shared_secretttsecrets÷
This option holds the shared secret string used to validate proxy requests to
Neutron metadata requests. In order to be used, the
'X-Metadata-Provider-Signature' header must be supplied in the request.

Related options:

* service_metadata_proxy
c

CsD|jt
ƒ

|jtd
t
ƒ


tj|tƒ
tj|tƒ
dS(Ntgroup(tregister_groupt
neutron_groupt
register_optstALL_OPTSt
ks_loadingtregister_session_conf_optionst
NEUTRON_GROUPtregister_auth_conf_options(
tconf((sF/home/tvault/.virtenv/lib/python2.7/site-packages/nova/conf/neutron.pyRjs




cCsFi
tt
jƒt
jƒt
jd
ƒ
t
jdƒ
t
jdƒ
t6S(Ntpasswordt
v2passwordt
v3password(RRtget_session_conf_optionstget_auth_common_conf_optionstget_auth_plugin_conf_optionsR(((sF/home/tvault/.virtenv/lib/python2.7/site-packages/nova/conf/neutron.pyt	list_optsqs
1
N(t
keystoneauth1RRtoslo_configR
RtOptGroupRtURIOpttStrOpttIntOpttneutron_optstBoolOpttFalsetTruetmetadata_proxy_optsRRR (((sF/home/tvault/.virtenv/lib/python2.7/site-packages/nova/conf/neutron.pyt<module>s: