openstack-manuals/doc/admin-guide-network/locale/openstack-network-connectivity-admin.pot
Diane Fleming 64b6c9261e Folder rename, file rename, flattening of directories
Current folder name	New folder name	        Book title
----------------------------------------------------------
basic-install 	        DELETE
cli-guide	        DELETE
common	                common
NEW	                admin-guide-cloud	Cloud Administrators Guide
docbkx-example	        DELETE
openstack-block-storage-admin 	DELETE
openstack-compute-admin 	DELETE
openstack-config 	config-reference	OpenStack Configuration Reference
openstack-ha 	        high-availability-guide	OpenStack High Availabilty Guide
openstack-image	        image-guide	OpenStack Virtual Machine Image Guide
openstack-install 	install-guide	OpenStack Installation Guide
openstack-network-connectivity-admin 	admin-guide-network 	OpenStack Networking Administration Guide
openstack-object-storage-admin 	DELETE
openstack-security 	security-guide	OpenStack Security Guide
openstack-training 	training-guide	OpenStack Training Guide
openstack-user 	        user-guide	OpenStack End User Guide
openstack-user-admin 	user-guide-admin	OpenStack Admin User Guide
glossary	        NEW        	OpenStack Glossary

bug: #1220407

Change-Id: Id5ffc774b966ba7b9a591743a877aa10ab3094c7
author: diane fleming
2013-09-08 15:15:50 -07:00

4337 lines
254 KiB
Plaintext
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2013-03-12 15:09+0800\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:17(None) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:273(None) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:276(None)
msgid "@@image: 'figures/Quantum-PhysNet-Diagram.png'; md5=f94377ebc99eb0f16d417f64730c5d46"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:4(title)
msgid "Provider Router with Private Networks"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:5(para)
msgid "This section describes how to install the OpenStack Networking service and its components for the \"Use Case: Provider Router with Private Networks\"."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:8(para)
msgid "We will follow the <link href=\"http://docs.openstack.org/folsom/basic-install/content/basic-install_intro.html\">Basic Install</link> document except for the Quantum, Open-vSwitch and Virtual Networking sections on each of the nodes."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:12(para)
msgid "The <emphasis role=\"bold\">Basic Install</emphasis> document uses gre tunnels. This document will describe how to use vlans for separation instead."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:20(para)
msgid "There will be three nodes in the setup.<table rules=\"all\"><caption>Nodes for Demo</caption><thead><tr><th>Node</th><th>Description</th></tr></thead><tbody><tr><td> Controller Node</td><td>Runs the OpenStack Networking service, OpenStack Identity and all of the OpenStack Compute services that are required to deploy a VM. The service must have at least two network interfaces The first should be connected to the \"Management Network\". This will be used to communicate with the compute and network nodes. The second interface will be connected to the API/public network</td></tr><tr><td>Compute Node</td><td>Runs OpenStack Compute and the OpenStack Networking L2 agent. This node will not have access the public network. The node must have at least two network interfaces. The first is used to communicate with the controller node, via the management network. The VM will be able to receive its IP address from the DHCP agent on this network.</td></tr><tr><td>Network Node</td><td>Runs OpenStack Networking L2 agent, the DHCP agent and the L3 agent. This node will have access to the public network. The DHCP agent will allocate IP addresses to the VMs on the network. The L3 agent will perform NAT and enable the VMs to access the public network. The node must have at least three network interfaces. The first is used to communicate with the controller node, this is via the management network. The second interface will be used for the VM traffic, this is on the data network. The third interface will be used to connect to the external gateway on the network. </td></tr></tbody></table>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:60(title)
msgid "Installations"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:62(title)
msgid "Controller"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:68(para)
msgid "Install the packages :<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:72(para)
msgid "Configure Quantum services :"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:75(para)
msgid "Edit <emphasis role=\"bold\">/etc/quantum/quantum.conf</emphasis> file and modify :<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:84(para)
msgid "Edit <emphasis role=\"bold\">/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini</emphasis> file and modify :<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:94(para)
msgid "Edit <emphasis role=\"bold\">/etc/quantum/api-paste.ini</emphasis> file and modify :<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:103(para)
msgid "Start the services :<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:108(title) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:62(td)
msgid "Network Node"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:115(para)
msgid "Install the packages:<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:120(para)
msgid "Start Open vSwitch:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:124(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:200(para)
msgid "Add the integration bridge to the Open vSwitch:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:128(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:207(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:204(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:243(para)
msgid "Update the OpenStack Networking configuration file, <emphasis role=\"bold\">/etc/quantum/quantum.conf</emphasis>:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:135(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:153(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:214(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:163(para)
msgid "Update the plugin configuration file, <emphasis role=\"bold\">/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini</emphasis>:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:146(para)
msgid "Create the network bridge <emphasis role=\"bold\">br-eth1</emphasis> (All VM communication between the nodes will be done via eth1):"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:153(para)
msgid "Create the external network bridge to the Open vSwitch:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:158(para)
msgid "Edit , <emphasis role=\"bold\">/etc/quantum/l3_agent.ini </emphasis> file and modify:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:169(para)
msgid "Edit , <emphasis role=\"bold\">/etc/quantum/api-paste.ini </emphasis> file and modify:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:178(para)
msgid "Edit , <emphasis role=\"bold\">/etc/quantum/dhcp_agent.ini </emphasis> file and modify:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:183(para)
msgid "Restart networking services"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:191(title) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:48(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:111(emphasis) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:122(emphasis)
msgid "Compute Node"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:195(para)
msgid "Install the packages.<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:199(para)
msgid "Start open vSwitch Service<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:203(para)
msgid "Configure Virtual Bridging<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:213(para)
msgid "Update <emphasis role=\"bold\">/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini</emphasis>:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:223(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:259(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:294(para)
msgid "Start the DHCP agent"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:233(title) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:267(title) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:343(title)
msgid "Logical Network Configuration"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:234(para)
msgid "All of the commands below can be done on the Network node."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:235(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:269(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:345(para)
msgid "<emphasis role=\"bold\">Note</emphasis> please ensure that the following environment variables are set. These are used by the various clients to access OpenStack Identity."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:240(para)
msgid "Create <emphasis role=\"bold\">novarc</emphasis> file :<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:252(para)
msgid "Export the variables :<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:261(emphasis)
msgid "Internal Networking Configuration"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:263(para)
msgid "Get the tenant ID (Used as $TENANT_ID later)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:276(para)
msgid "Create a internal network named <emphasis role=\"bold\">net1</emphasis> on the demo tenant ($TENANT_ID will be e40fa60181524f9f9ee7aa1038748f08):"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:298(para)
msgid "Create a subnet on the network <emphasis role=\"bold\">net1</emphasis> (ID field below is used as $SUBNET_ID later):"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:321(emphasis)
msgid "External Networking Configuration"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:323(para)
msgid "Create a router named <emphasis role=\"bold\">router1</emphasis> (ID is used as $ROUTER_ID later):"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:338(para)
msgid "Add an interface to <emphasis role=\"bold\">router1</emphasis> and attach the <emphasis role=\"bold\">net1</emphasis> subnet:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:345(para)
msgid "Create the external network named <emphasis role=\"bold\">ext_net</emphasis>. Environment variables will attach this to the <emphasis role=\"bold\">admin</emphasis> tenant (Used as $EXTERNAL_NETWORK_ID). <emphasis role=\"bold\">Note</emphasis> this is a different $TENANT_ID than used previously:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:369(para)
msgid "Create the subnet for floating IPs. <emphasis role=\"bold\">Note</emphasis> the DHCP service is disabled for this subnet:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:392(para)
msgid "Set the router gateway towards the external network:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:399(emphasis)
msgid "Floating IP Allocation"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:401(para)
msgid "After a VM is deployed a floating IP address can be associated to the VM. A VM that is created will be allocated an OpenStack Networking port ($PORT_ID). The port ID for the VM can be retrieved as follows (VIA the Controller or Compute Node) :"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:423(para)
msgid "Allocate a floating IP (Used as $FLOATING_ID):"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:439(para)
msgid "Associate a floating IP to a VM (in the case of the example it is 9aa47099-b87b-488c-8c1d-32f993626a30):"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:445(para)
msgid "Show the floating IP:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_single_router.xml:459(para)
msgid "Test the floating IP:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:6(title)
msgid "Preface"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:7(para)
msgid "OpenStack Networking was created to provide a rich and tenant-facing API for defining network connectivity and addressing in the cloud. The project, code-named \"quantum,\" gives operators the ability to leverage different networking technologies to power their cloud networking.  "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:13(title)
msgid "Intended Audience"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:14(para)
msgid "This guide assists OpenStack administrators in leveraging different networking technologies to power their cloud networking. This document covers how to install, configure, and run OpenStack Networking."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:18(para)
msgid "The user should also have access to a plugin providing the implementation of the OpenStack Networking service. Several plugins are included in the OpenStack Networking distribution:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:24(para)
msgid "<emphasis role=\"bold\">Openvswitch</emphasis>. Implements OpenStack Networking with Open vSwitch for the KVM and XenServer compute platforms."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:30(para)
msgid "<emphasis role=\"bold\">Cisco</emphasis>. Implements OpenStack Networking for deployments by using Cisco UCS blades and Nexus switches for KVM compute platforms."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:36(para)
msgid "<emphasis role=\"bold\">Linux Bridge</emphasis> Implements OpenStack Networking with the Linux Bridge for the KVM compute platforms."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:41(para)
msgid "<emphasis role=\"bold\">Nicira NVP</emphasis>. Implements OpenStack Networking by using the Nicira Network Virtualization Platform (NVP) for KVM and XenServer compute platforms."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:47(para)
msgid "<emphasis role=\"bold\">Ryu</emphasis>. Implements OpenStack Networking by using the Ryu OpenFlow Controller for KVM compute platforms."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:52(para)
msgid "<emphasis role=\"bold\">NEC OpenFlow</emphasis>. Implements OpenStack Networking by using Trema Sliceable Switch OpenFlow Controller or NEC ProgrammableFlow Controller for KVM compute platforms."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:59(para)
msgid "<emphasis role=\"bold\">Big Switch, Floodlight REST Proxy </emphasis>. Implements the OpenStack Networking plugin API and realizes the network abstractions by leveraging the Big Network Controller (BNC) or Floodlight OpenFlow Controller for KVM hypervisor based compute platforms."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:67(para)
msgid "Plugins can also be distributed separately from OpenStack Networking."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:69(para)
msgid "You should also be familiar with running the OpenStack Compute service as described in the operator's documentation."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:74(title)
msgid "Document Change History"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:75(para)
msgid "The most recent changes are described in the table below:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:80(title)
msgid "Resources"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:81(para)
msgid "For more information on OpenStack Networking and the other network-related projects, see the project page on the OpenStack wiki (<link href=\"http://wiki.openstack.org/Quantum\">wiki.openstack.org/Quantum</link>)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:86(para)
msgid "For information about programming against the OpenStack Networking API, see the <link href=\"http://docs.openstack.org/api/openstack-network/2.0/content/\"><citetitle>OpenStack Networking API Guide (v2.0)</citetitle></link>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_preface.xml:91(para)
msgid "We welcome feedback, comments, and bug reports at <link href=\"http://bugs.launchpad.net/Quantum\">bugs.launchpad.net/Quantum</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:8(title)
msgid "OpenStack Networking Installation"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:9(para)
msgid "This chapter describes how to install the OpenStack Networking service and get it up and running."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:11(para)
msgid "If you are building a host from scratch to use for OpenStack Networking, we strongly recommend using Ubuntu 12.04/12.10 or Fedora 17/18 as these platforms have OpenStack Networking packages and receive significant testing."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:15(para)
msgid "OpenStack Networking requires at least dnsmasq 2.59, to support all the options it requires."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:18(title)
msgid "Install Packages (Ubuntu)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:20(para)
msgid "We are using Ubuntu cloud archive you can read more about it Explanation of each possible sources.list entry can be found here: <link href=\"http://blog.canonical.com/2012/09/14/now-you-can-have-your-openstack-cake-and-eat-it/\">http://bit.ly/Q8OJ9M </link>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:26(para)
msgid "Point to Folsom PPAs:                                                                        "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:33(para)
msgid "Please use \"sudo\" in order to install and configure packages with superuser privileges."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:37(title)
msgid "Install quantum-server"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:38(para)
msgid "Install quantum-server and CLI for accessing the API:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:41(para)
msgid "You will also want to install the plugin you choose to use, for example:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:44(para)
msgid "Most plugins require a database to be installed and configured in a plugin configuration file.  For example:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:48(para)
msgid "A database that you are already using for other OpenStack services will work fine for this.  Simply create a quantum database:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:52(para)
msgid "And then configure the plugins configuration file to use this database.  Find the plugin configuration file in <filename>/etc/quantum/plugins</filename> (For example, <filename>/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini</filename>) and set:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:60(title) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:261(title)
msgid "RPC Setup"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:61(para)
msgid "OpenStack Networking uses RPC to allow DHCP agents and any plugin agents to communicate with the main quantum-server process.  Commonly, this can use the same RPC mechanism used by other OpenStack components like Nova. "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:66(para)
msgid "To use RabbitMQ as the message bus for RPC, make sure that rabbit is installed on a host reachable via the management network (if this is already the case because of deploying another service like Nova, this existing RabbitMQ setup is sufficient): "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:74(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:275(para)
msgid "Then update /etc/quantum/quantum.conf with these values:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:81(para)
msgid "This /etc/quantum/quantum.conf file should be copied to and used on all hosts running quantum-server, quantum-dhcp-agent, quantum-openvswitch-agent, or quantum-linuxbridge-agent (see below)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:89(title)
msgid "Configuring Open vSwitch Plugin"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:90(para)
msgid "Using the Open vSwitch (OVS) plugin in a deployment with multiple hosts requires the using of either tunneling or vlans in order to isolate traffic from multiple networks.  Tunneling is easier to deploy, as it does not require configuring VLANs on network switches, so that is what we describe here. More advanced deployment options are described in the <link linkend=\"ch_adv_config\"/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:99(para)
msgid "Edit <filename>/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini</filename> to specify the following values:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:107(para)
msgid "After performing that change on the node running quantum-server, restart quantum-server to pick up the new settings."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:113(title)
msgid "Configuring Nicira NVP Plugin"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:114(para)
msgid "To configure OpenStack Networking to use the NVP plugin first edit <filename>/etc/quantum/quantum.conf</filename> and set:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:119(para)
msgid "Edit <filename>/etc/quantum/plugins/nicira/nvp.ini</filename> in order to configure the plugin. The quantum database created previously will be used by setting:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:125(para)
msgid "In order to tell OpenStack Networking about a controller cluster, create a [CLUSTER:&lt;name&gt;] section underneath the [nvp] section. Under this new cluster specify the Transport Zone by setting:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:131(para)
msgid "Specify the controllers in this cluster by setting:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:134(para)
msgid "one for each controller."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:135(para)
msgid "Lastly, restart quantum-server to pick up the new settings."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:141(title) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:311(title)
msgid "Install quantum-plugin-*-agent"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:142(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:312(para)
msgid "Some plugins utilize an agent that runs on each node that handles data packets. This includes any node running nova-compute, as well as nodes running dedicated OpenStack Networking agents like quantum-dhcp-agent and quantum-l3-agent (see below). If your plugin uses an agent, this section describes how to run the agent for this plugin, as well as the basic configuration options."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:151(title) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:321(title)
msgid "Open vSwitch Agent"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:152(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:322(para)
msgid "Install the OVS agent:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:154(para)
msgid "The ovs_quantum_plugin.ini created in the above step must be replicated on all nodes quantum-plugin-openvswitch-agent. When using tunneling, each node running quantum-plugin-openvswitch agent should have an IP address configured on the Data Network, and that IP address should be specified using the local_ip value in the ovs_quantum_plugin.ini file."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:162(para)
msgid "Then restart the agent"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:164(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:326(para)
msgid "All hosts running quantum-plugin-openvswitch-agent also requires that an OVS bridge named \"br-int\" exists. To create it, run:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:172(title) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:337(title)
msgid "Install quantum-dhcp-agent"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:173(para)
msgid "The host running quantum-server requires a network interface with an IP address on the “management network” and another interface on the “data network”."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:177(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:183(para)
msgid "Install the agent specific to the plugin (see plugin specific agent section above)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:181(title) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:348(title)
msgid "Install quantum-l3-agent"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:185(para)
msgid "Create a bridge \"br-ex\" that will be used to uplink this node running quantum-l3-agent to the external network, then attach the NIC attached to the external network to this bridge."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:190(para)
msgid "OpenStack does not manage this routing for you, so you need to make sure that your host running the metadata service always has a route to reach each private network's subnet via the external network IP of that subnet's OpenStack Networking router. To do this, you can run OpenStack Networking without namespaces, and run the quantum-l3-agent on the same host as nova-api. Alternatively, you can identify an IP prefix that includes all private network subnet's (e.g., 10.0.0.0/8) and then make sure that your metadata server has a route for that prefix with the OpenStack Networking router's external IP address as the next hop. For more validation information, refer to <link linkend=\"adv_cfg_l3_agent_metadata\">Advanced configuration</link>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:206(para)
msgid "For example, with Open vSwitch and NIC eth1 connect to the external network, run:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:210(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:359(para)
msgid "The node running quantum-l3-agent should not have an IP address manually configured on the NIC connected to the external network. Rather, you must have a range of IP addresses from the external network that can be used by OpenStack Networking for routers that uplink to the external network. This range must be large enough to have an IP address for each router in the deployment, as well as each floating IP."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:218(para)
msgid "The quantum-l3-agent uses the Linux IP stack and iptables to perform L3 forwarding and NAT. In order to support multiple routers with potentially overlapping IP addresses, quantum-l3-agent defaults to using Linux network namespaces to provide isolated forwarding contexts. As a result, the IP addresses of routers will not be visible simply by running \"ip addr list\" or \"ifconfig\" on the node. Similarly, you will not be able to directly ping fixed IPs. To do either of these things, you must run the command within a particular router's network namespace. The namespace will have the name \"qrouter-&lt;UUID of the router&gt;. The following commands are examples of running commands in the namespace of a router with UUID 47af3868-0fa8-4447-85f6-1304de32153b:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:239(title)
msgid "Install OpenStack Networking CLI Client"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:240(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:376(para)
msgid "Install the OpenStack Networking CLI client:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:244(title)
msgid "Init, Config, and Log File Locations"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:245(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:381(para)
msgid "Services can be started and stopped using the 'service' command. For example:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:251(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:387(para)
msgid "Log files are found in /var/log/quantum."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:252(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:388(para)
msgid "Configuration files are in /etc/quantum."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:257(title)
msgid "Installing Packages (Fedora)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:258(para)
msgid "The OpenStack packages for Fedora can be retrieved from: <uri>https://apps.fedoraproject.org/packages/s/openstack</uri>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:262(para)
msgid "OpenStack Networking uses RPC to allow DHCP agents and any plugin agents to communicate with the main quantum-server process.  Commonly, this can use the same RPC mechanism used by other OpenStack components like Nova."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:267(para)
msgid "To use QPID AMQP as the message bus for RPC, make sure that QPID is installed on a host reachable via the management network (if this is already the case because of deploying another service like Nova, this existing QPID setup is sufficient): "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:280(para)
msgid "The Fedora packaging has a number of utility scripts that configure all of the necessary configuration files. The scripts can also be used to understand what needs to be configured for the specific OpenStack Networking services. The scripts will be described below. Please note that the scripts make use of the package openstack-utils. Please install:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:294(title)
msgid "Install quantum-server and plugin"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:295(para)
msgid "Install quantum-server and plugin. <emphasis role=\"bold\">Note</emphasis> the client is installed as a dependency for the OpenStack Networking service."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:301(para)
msgid "Most plugins require a database to be installed and configured in a plugin configuration file.  The Fedora packaging for OpenStack Networking a server setup utility scripts that will take care of this. For example:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:306(para)
msgid "Enable and start the service:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:324(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:341(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:368(para)
msgid "Run the agent setup script:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:331(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:343(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:370(para)
msgid "Enable and start the agent:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:338(para)
msgid "The DHCP agent is part of the openstack-quantum package."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:349(para)
msgid "The L3 agent is part of the openstack-quantum package."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:351(para)
msgid "Create a bridge \"br-ex\" that will be used to uplink this node running quantum-l3-agent to the external network, then attach the NIC attached to the external network to this bridge. For example, with Open vSwitch and NIC eth1 connect to the external network, run:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:375(title)
msgid "Install OpenStack Networking CLI client"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml:380(title)
msgid "<?sbr?>Init, Config, and Log File Locations"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo.xml:4(title)
msgid "Demos Setup"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo.xml:5(para)
msgid "This section describes how to configure the OpenStack Networking service and its components for some typical use cases."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:6(title)
msgid "Authentication and Authorization"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:26(para)
msgid "<emphasis role=\"bold\">Operation-based</emphasis>: policies specify access criteria for specific operations, possibly with fine-grained control over specific attributes;"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:33(para)
msgid "<emphasis role=\"bold\">Resource-based:</emphasis> whether access to specific resource might be granted or not according to the permissions configured for the resource (currently available only for the network resource). The actual authorization policies enforced in OpenStack Networking might vary from deployment to deployment."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:7(para)
msgid "OpenStack Networking uses the OpenStack Identity service (project name keystone) as the default authentication service. When OpenStack Identity is enabled Users submitting requests to the OpenStack Networking service must provide an authentication token in X-Auth-Token request header. The aforementioned token should have been obtained by authenticating with the OpenStack Identity endpoint. For more information concerning authentication with OpenStack Identity, please refer to the OpenStack Identity documentation. When OpenStack Identity is enabled, it is not mandatory to specify tenant_id for resources in create requests, as the tenant identifier will be derived from the Authentication token. Please note that the default authorization settings only allow administrative users to create resources on behalf of a different tenant. OpenStack Networking uses information received from OpenStack Identity to authorize user requests. OpenStack Networking handles two kind of authorization policies: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:43(para)
msgid "The policy engine reads entries from the <emphasis role=\"italic\">policy.json</emphasis> file. The actual location of this file might vary from distribution to distribution. Entries can be updated while the system is running, and no service restart is required. That is to say, every time the policy file is updated, the policies will be automatically reloaded. Currently the only way of updating such policies is to edit the policy file. Please note that in this section we will use both the terms \"policy\" and \"rule\" to refer to objects which are specified in the same way in the policy file; in other words, there are no syntax differences between a rule and a policy. We will define a policy something which is matched directly from the OpenStack Networking policy engine, whereas we will define a rule as the elements of such policies which are then evaluated. For instance in <code>create_subnet: [[\"admin_or_network_owner\"]]</code>, <emphasis role=\"italic\">create_subnet</emphasis> is regarded as a policy, whereas <emphasis role=\"italic\">admin_or_network_owner</emphasis> is regarded as a rule."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:63(para)
msgid "Policies are triggered by the OpenStack Networking policy engine whenever one of them matches an OpenStack Networking API operation or a specific attribute being used in a given operation. For instance the <code>create_subnet</code> policy is triggered every time a <code>POST /v2.0/subnets</code> request is sent to the OpenStack Networking server; on the other hand <code>create_network:shared</code> is triggered every time the <emphasis role=\"italic\">shared</emphasis> attribute is explicitly specified (and set to a value different from its default) in a <code>POST /v2.0/networks</code> request. It is also worth mentioning that policies can be also related to specific API extensions; for instance <code>extension:provider_network:set</code> will be triggered if the attributes defined by the Provider Network extensions are specified in an API request."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:78(para)
msgid "An authorization policy can be composed by one or more rules. If more rules are specified, evaluation policy will be successful if any of the rules evaluates successfully; if an API operation matches multiple policies, then all the policies must evaluate successfully. Also, authorization rules are recursive. Once a rule is matched, the rule(s) can be resolved to another rule, until a terminal rule is reached."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:83(para)
msgid "The OpenStack Networking policy engine currently defines the following kinds of terminal rules:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:87(para)
msgid "<emphasis role=\"bold\">Role-based rules</emphasis>: evaluate successfully if the user submitting the request has the specified role. For instance <code>\"role:admin\"</code>is successful if the user submitting the request is an administrator."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:93(para)
msgid "<emphasis role=\"bold\">Field-based rules: </emphasis>evaluate successfully if a field of the resource specified in the current request matches a specific value. For instance <code>\"field:networks:shared=True\"</code> is successful if the attribute <emphasis role=\"italic\">shared</emphasis> of the <emphasis role=\"italic\">network</emphasis> resource is set to true."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:100(para)
msgid "<emphasis role=\"bold\">Generic rules:</emphasis> compare an attribute in the resource with an attribute extracted from the user's security credentials and evaluates successfully if the comparison is successful. For instance <code>\"tenant_id:%(tenant_id)s\"</code> is successful if the tenant identifier in the resource is equal to the tenant identifier of the user submitting the request."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:85(para)
msgid "<placeholder-1/> The following is an extract from the default policy.json file:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:108(code) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:149(code)
msgid "{"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:109(code) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:150(code)
msgid "\"admin_or_owner\": [[\"role:admin\"], [\"tenant_id:%(tenant_id)s\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:110(emphasis)
msgid "[1]"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:111(code)
msgid "\"admin_or_network_owner\": [[\"role:admin\"], [\"tenant_id:%(network_tenant_id)s\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:113(code) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:151(code)
msgid "\"admin_only\": [[\"role:admin\"]], \"regular_user\": [],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:114(code)
msgid "\"shared\": [[\"field:networks:shared=True\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:115(code)
msgid "\"default\": [[\"rule:admin_or_owner\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:115(emphasis)
msgid "[2]"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:116(code)
msgid "\"create_subnet\": [[\"rule:admin_or_network_owner\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:117(code)
msgid "\"get_subnet\": [[\"rule:admin_or_owner\"], [\"rule:shared\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:118(code)
msgid "\"update_subnet\": [[\"rule:admin_or_network_owner\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:119(code)
msgid "\"delete_subnet\": [[\"rule:admin_or_network_owner\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:120(code) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:157(code)
msgid "\"create_network\": [],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:121(code)
msgid "\"get_network\": [[\"rule:admin_or_owner\"], [\"rule:shared\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:121(emphasis)
msgid "[3]"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:122(code) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:159(code)
msgid "\"create_network:shared\": [[\"rule:admin_only\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:122(emphasis)
msgid "[4]"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:124(code) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:160(code)
msgid "\"update_network\": [[\"rule:admin_or_owner\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:125(code) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:161(code)
msgid "\"delete_network\": [[\"rule:admin_or_owner\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:126(code)
msgid "\"create_port\": [],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:127(code)
msgid "\"create_port:mac_address\": [[\"rule:admin_or_network_owner\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:127(emphasis)
msgid "[5]"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:128(code)
msgid "\"create_port:fixed_ips\": [[\"rule:admin_or_network_owner\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:129(code) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:163(code)
msgid "\"get_port\": [[\"rule:admin_or_owner\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:130(code)
msgid "\"update_port\": [[\"rule:admin_or_owner\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:131(code)
msgid "\"delete_port\": [[\"rule:admin_or_owner\"]]"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:132(code) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:166(code)
msgid "}"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:133(para)
msgid "[1] is a rule which evaluates successfully if the current user is an administrator or the owner of the resource specified in the request (tenant identifier is equal)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:135(para)
msgid "[2] is the default policy which is always evaluated if an API operation does not match any of the policies in policy.json."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:137(para)
msgid "[3] This policy will evaluate successfully if either <emphasis role=\"italic\">admin_or_owner</emphasis>, or <emphasis role=\"italic\">shared</emphasis> evalutes successfully."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:140(para)
msgid "[4] This policy will restrict the ability of manipulating the <emphasis role=\"italic\">shared</emphasis> attribute for a network to administrators only."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:142(para)
msgid "[5] This policy will restrict the ability of manipilating the <emphasis role=\"italic\">mac_address</emphasis> attribute for a port only to administrators and the owner of the network where the port is attached."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:145(para)
msgid "In some cases, some operations should be restricted to administrators only; therefore, as a further example, let us consider how this sample policy file should be modified in a scenario where tenants are allowed only to define networks and see their resources, and all the other operations can be performed only in an administrative context:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:152(code)
msgid "\"default\": [[\"rule:admin_only\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:153(code)
msgid "\"create_subnet\": [[\"rule:admin_only\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:154(code)
msgid "\"get_subnet\": [[\"rule:admin_or_owner\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:155(code)
msgid "\"update_subnet\": [[\"rule:admin_only\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:156(code)
msgid "\"delete_subnet\": [[\"rule:admin_only\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:158(code)
msgid "\"get_network\": [[\"rule:admin_or_owner\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:162(code)
msgid "\"create_port\": [[\"rule:admin_only\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:164(code)
msgid "\"update_port\": [[\"rule:admin_only\"]],"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_auth.xml:165(code)
msgid "\"delete_port\": [[\"rule:admin_only\"]]"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:6(title)
msgid "Plugin pagination and sorting support"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:8(caption)
msgid "The plugins are supporting native pagination and sorting"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:12(th)
msgid "Plugin"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:13(th)
msgid "Support Native Pagination"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:14(th)
msgid "Support Native Sorting"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:20(td)
msgid "Open vSwitch"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:21(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:22(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:26(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:27(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:87(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:208(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:311(td)
msgid "True"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml:25(td)
msgid "LinuxBridge"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:6(title)
msgid "Using OpenStack Networking"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:8(para)
msgid "There are two main approaches to using OpenStack Networking.  The first is to expose the OpenStack Networking API to cloud tenants, allowing them to build rich network topologies.  The second is to have the cloud administrator, or another tool run the the cloud admin, create network connectivity on behalf of tenants.  In this document, we commonly describe operations as being performed by a tenant, but they might also be performed by the cloud admin on behalf of the tenant. "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:17(title)
msgid "Core OpenStack Networking API Features"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:18(para)
msgid "Once OpenStack Networking is installed and running, both tenants and admins primarily interact with the service via create-read-update-delete (CRUD) API operations performed either directly against the API, or more commonly via the 'quantum' CLI tool.  Like other OpenStack CLI tools, the 'quantum' tool is just a basic wrapper around the OpenStack Networking API, so any operation that can be performed via the CLI has an equivalent API call that can be performed programmatically. "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:27(para)
msgid "The CLI supports many options for filtering results, limiting fields show, etc.  For details, refer to the OpenStack Networking CLI documentation.  "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:30(title)
msgid "API Abstractions"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:31(para)
msgid "The OpenStack Networking v2.0 API provides control over both L2 network topologies and the IP addresses used on those networks (IP Address Management or IPAM). There is also an extension to cover basic L3 forwarding and NAT, providing capabilities similar to nova-network."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:35(para)
msgid "In the OpenStack Networking API, an isolated L2 network segment (similar to a VLAN) is called a 'Network' and forms the basis for describing the L2 network topology available in a given OpenStack Networking deployment."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:38(para)
msgid "The OpenStack Networking API uses the notion of a 'Subnet', which associates a block of IP addresses and other network configuration (e.g., default gateway, dns-servers) with an OpenStack Networking network. Each subnet represents an IPv4 or IPv6 address block and each OpenStack Networking network can have multiple subnets, if desired. "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:44(para)
msgid "A 'Port' represents an attachment port to a L2 OpenStack Networking network. When a port is created on the network, by default it will be allocated an available fixed IP address out of one of the designated Subnets for each IP version (if one exists).  When the Port is destroyed, the allocated addresses return to the pool of available IPs on the subnet(s). Users of the OpenStack Networking API can either choose a specific IP address from the block, or let OpenStack Networking choose the first available IP address."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:51(para)
msgid "The table below summarizes the attributes available for each of these abstractions. For more operations about API abstraction and operations, please refer to the <link href=\"http://docs.openstack.org/api/openstack-network/2.0/content/\">OpenStack Networking v2.0 API Developer Guide</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:57(caption)
msgid "Network"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:64(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:146(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:288(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:348(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:530(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:576(th)
msgid "Attribute name"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:65(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:132(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:231(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:147(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:289(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:349(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:531(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:577(th)
msgid "Type"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:66(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:133(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:232(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:148(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:290(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:350(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:532(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:578(th)
msgid "Default Value"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:67(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:134(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:233(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:31(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:149(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:291(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:351(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:533(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:579(th)
msgid "Description"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:72(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:139(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:238(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:296(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:356(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:538(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:584(td)
msgid "id"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:73(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:115(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:140(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:146(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:214(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:239(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:245(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:303(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:297(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:325(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:357(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:370(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:378(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:387(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:404(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:539(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:560(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:585(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:641(td)
msgid "uuid-str"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:74(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:141(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:240(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:276(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:298(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:358(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:540(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:586(td)
msgid "generated"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:75(td)
msgid "UUID for the network."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:78(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:151(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:251(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:302(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:544(td)
msgid "name"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:79(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:94(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:152(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:252(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:155(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:171(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:303(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:318(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:545(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:553(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:597(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:604(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:622(td)
msgid "String"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:80(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:153(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:253(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:291(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:298(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:304(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:546(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:554(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:605(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:611(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:617(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:623(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:629(td)
msgid "None"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:81(td)
msgid "Human-readable name for the network. Might not be unique."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:85(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:258(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:309(td)
msgid "admin_state_up"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:86(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:108(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:207(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:310(td)
msgid "Bool"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:88(td)
msgid "The administrative state of network. If false (down), the network does not forward packets."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:93(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:266(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:317(td)
msgid "status"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:95(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:116(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:147(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:166(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:215(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:246(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:268(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:304(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:156(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:184(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:319(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:326(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:371(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:379(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:405(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:561(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:598(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:642(td)
msgid "N/A"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:96(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:269(para)
msgid "Indicates whether network is currently operational."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:100(td)
msgid "subnets"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:101(td)
msgid "list(uuid-str)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:102(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:182(td)
msgid "Empty list"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:103(td)
msgid "Subnets associated with this network."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:107(td)
msgid "shared"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:109(td)
msgid "False"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:110(td)
msgid "Specifies whether the network resource can be accessed by any tenant or not."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:114(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:213(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:302(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:324(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:403(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:559(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:640(td)
msgid "tenant_id"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:117(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:216(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:305(td)
msgid "Owner of network. Only admin users can specify a tenant_id other than its own."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:124(caption)
msgid "Subnet"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:131(th) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:230(th)
msgid "Attribute"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:142(td)
msgid "UUID representing the subnet"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:145(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:244(td)
msgid "network_id"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:148(td)
msgid "network this subnet is associated with."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:154(td)
msgid "Human-readable name for the subnet. Might not be unique."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:158(td)
msgid "ip_version"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:159(td)
msgid "int"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:160(td)
msgid "4"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:161(td)
msgid "IP version"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:164(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:174(emphasis) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:190(emphasis)
msgid "cidr"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:165(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:172(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:267(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:275(td)
msgid "string"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:167(td)
msgid "cidr representing IP range for this subnet, based on IP version"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:171(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:191(emphasis)
msgid "gateway_ip"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:173(td)
msgid "first address in <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:176(td)
msgid "default gateway used by devices in this subnet"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:180(td)
msgid "dns_nameservers"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:181(td)
msgid "list(str)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:183(td)
msgid "DNS name servers used by hosts in this subnet."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:187(td)
msgid "allocation_pools"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:188(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:199(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:281(td)
msgid "list(dict)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:189(td)
msgid "Every address in <placeholder-1/>, excluding <placeholder-2/> if configured"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:193(td)
msgid "Sub-ranges of cidr available for dynamic allocation to ports [ { \"start\": \"10.0.0.2\", \"end\": \"10.0.0.254\"} ]"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:198(td)
msgid "host_routes"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:200(td)
msgid "Empty List"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:201(td)
msgid "Routes that should be used by devices with IPs from this subnet (not including local subnet route)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:206(td)
msgid "enable_dhcp"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:209(td)
msgid "Specifies whether DHCP is enabled for this subnet or not."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:223(caption)
msgid "Port"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:241(td)
msgid "UUID for the port."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:247(td)
msgid "Network that this port is associated with."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:254(td)
msgid "Human-readable name for the port. Might not be unique."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:259(td)
msgid "bool"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:260(td)
msgid "true"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:261(td)
msgid "Administrative state of port. If false (down), port does not forward packets."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:274(td)
msgid "mac_address"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:277(td)
msgid "Mac address to use on this port."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:280(td)
msgid "fixed_ips"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:282(td)
msgid "automatically allocated from pool"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:283(td)
msgid "Specifies IP addresses for the port thus associating the port itself with the subnets where the IP addresses are picked from"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:289(td)
msgid "device_id"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:290(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:297(td)
msgid "str"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:292(td)
msgid "identifies the device (e.g., virtual server) using this port."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:296(td)
msgid "device_owner"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:299(td)
msgid "Identifies the entity (e.g.: dhcp agent) using this port."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:313(title)
msgid "OpenStack Networking CLI Guide"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:314(para)
msgid "Before going further, we STRONGLY suggest that you quickly read the few pages in the <link href=\"http://docs.openstack.org/cli/quick-start/content/index.html\">OpenStack CLI Guide</link> that are specific to OpenStack Networking. OpenStack Networking's CLI has some advanced capabilities that are described only in that guide."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:319(title)
msgid "Basic Operations"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:320(para)
msgid "Create a network"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:322(para)
msgid "Create a subnet associated with net1"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:324(para)
msgid "List ports on a tenant"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:326(para)
msgid "<emphasis role=\"italic\">device_owner</emphasis> field describes who owns the port. A port whose <emphasis role=\"italic\">device_owner</emphasis> begins with \"network:\" is created by OpenStack Networking and a port whose <emphasis role=\"italic\">device_owner</emphasis> begins with \"compute:\" is created by OpenStack Compute (compute service)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:330(para)
msgid "<placeholder-1/> shows a detail of a specified port."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:334(title)
msgid "Admin API configuration"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:335(para)
msgid "These same calls can be performed by the cloud admin on half of the tenants by specifying a tenant_id in the request, for example:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:339(para)
msgid "This tenant_id should be the tenant ID from OpenStack Identity. To view all OpenStack Identity tenant IDs, run the following command as an OpenStack Identity (keystone) admin user:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:345(title)
msgid "Advanced API Operations Examples"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:347(title)
msgid "Network, Subnet &amp; Port Creation"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:350(para)
msgid "Create a \"shared\" network (i.e., a network that can be used by all tenants)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:354(para)
msgid "Create a subnet that has a specific gateway IP address."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:358(para)
msgid "Create a subnet that has no gateway IP address."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:362(para)
msgid "Create a subnet for which DHCP is disabled."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:366(para)
msgid "Create subnet with a specific set of host routes:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:370(para)
msgid "Create subnet with a specific set of dns nameserver:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:376(title)
msgid "Searches"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:379(para)
msgid "Find all Ports/IPs allocated on a network."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:387(title)
msgid "Using OpenStack Compute with OpenStack Networking"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:389(title)
msgid "Basic Workflow"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:390(para)
msgid "Check available networks:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:392(para)
msgid "Boot the VM with a single NIC on the selected network (net1):"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:394(para)
msgid "Congrats, you have booted a VM on an OpenStack Networking network. You may need to configure <link linkend=\"enabling_ping_and_ssh\">security group rules</link> to allow accesses to the VM."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:398(para)
msgid "There is now an OpenStack Networking port on 'net1' that corresponds to the VM Nic.  You can view it with the following command, which searches for all ports with a \"device_id\" corresponding to the OpenStack Compute instance UUID:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:404(para)
msgid "To view only a few fields of the port, you can limit output using -c.  For example to see only the mac_address of the port, use:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:408(para)
msgid "You could temporarily disable the port from sending traffic by updating it to have admin_state_up=False:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:412(para)
msgid "When we delete the OpenStack Compute VM, the underlying OpenStack Networking port is automatically deleted:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:417(title)
msgid "Advanced VM creation"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:421(para)
msgid "Booting a VM with multiple NICs"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:426(para)
msgid "Booting a VM with a specific IP address. To do this, we need to create an OpenStack Networking port with a specific IP address first, and then boot a VM specifying a port-id rather than a net-id."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:431(para)
msgid "<placeholder-1/> parameter of <placeholder-2/> option in <placeholder-3/> command is not supported with OpenStack Networking at the moment."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:435(para)
msgid "booting a VM with no --nic option specified. In this case the launched VM connects to all networks that are accessible to the tenant who submits the request."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:444(title)
msgid "Security Groups (Enabling Ping and SSH on VMs)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:445(para)
msgid "In Folsom release, the security groups feature is provided by OpenStack Compute not by OpenStack Networking. You can configure security group rules by using <placeholder-1/> or <placeholder-2/> command to enable accesses to your VMs. The example below allows <placeholder-3/> or <placeholder-4/> to your VMs."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml:451(para)
msgid "For more detail about OpenStack Compute security groups, please see \"Networking with nova-network\" in OpenStack Compute Administration Manual."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:21(title)
msgid "OpenStack Networking Administration Guide"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:30(year)
msgid "2011"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:31(year)
msgid "2012"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:32(year)
msgid "2013"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:33(holder)
msgid "OpenStack Foundation"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:35(releaseinfo)
msgid "trunk"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:36(productname)
msgid "OpenStack Networking"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:37(pubdate) ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:51(date)
msgid "2013-02-04"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:40(remark)
msgid "Copyright details are filled in by the template."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:44(para)
msgid "This document is intended for administrators interested in running the OpenStack Networking Virtual Network Service."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:55(para)
msgid "Use OpenStack naming conventions through out document."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:61(date)
msgid "2012-12-20"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:65(para)
msgid "Trunk designation of this document."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:71(date)
msgid "2012-11-09"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:75(para)
msgid "Folsom release of this document."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:82(date)
msgid "2012-09-18"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/bk-networking-admin-guide.xml:86(para)
msgid "First edition of this document."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_high_avail.xml:3(title)
msgid "High Availability"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_high_avail.xml:4(para)
msgid "Several aspects of an OpenStack Networking deployment benefit from high-availabilty to withstand individual node failures. In general, quantum-server and quantum-dhcp-agent can be run in an active-active fashion. The quantum-l3-agent service can be run only as active/passive, to avoid IP conflicts with respect to gateway IP addresses."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_high_avail.xml:11(title)
msgid "OpenStack Networking High Availability with Pacemaker"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_high_avail.xml:13(para)
msgid "You can run some OpenStack Networking services into a cluster (Active / Passive or Active / Active for OpenStack Networking Server only) with Pacemaker."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_high_avail.xml:18(para)
msgid "quantum-server: <link href=\"https://github.com/madkiss/openstack-resource-agents/blob/master/ocf/quantum-server\">https://github.com/madkiss/openstack-resource-agents/blob/master/ocf/quantum-server</link>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_high_avail.xml:23(para)
msgid "quantum-dhcp-agent : <link href=\"https://github.com/madkiss/openstack-resource-agents/blob/master/ocf/quantum-agent-dhcp\">https://github.com/madkiss/openstack-resource-agents/blob/master/ocf/quantum-agent-dhcp</link>  "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_high_avail.xml:27(para)
msgid "quantum-l3-agent : <link href=\"https://github.com/madkiss/openstack-resource-agents/blob/master/ocf/quantum-agent-l3\">https://github.com/madkiss/openstack-resource-agents/blob/master/ocf/quantum-agent-l3</link>  "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_high_avail.xml:16(para)
msgid "Here you can download the latest Resources Agents :<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_high_avail.xml:31(para)
msgid "If you need more informations about \"<emphasis role=\"italic\">How to build a cluster</emphasis>\", please refer to <link href=\"http://www.clusterlabs.org/wiki/Documentation\">Pacemaker documentation</link>."
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:18(None) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:21(None)
msgid "@@image: 'figures/demo_flat_install.png'; md5=27b45d5871859ff4951c92df7c8763d8"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:4(title)
msgid "Single Flat Network"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:5(para)
msgid "This section describes how to install the OpenStack Networking service and its components for the \"<link linkend=\"use_cases_single_flat\">Use Case: Single Flat Network </link>\"."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:9(para)
msgid "The diagram below shows the setup. For simplicity all of the nodes should have one interface for management traffic and one or more interfaces for traffic to and from VMs. The management network is 100.1.1.0/24 with controller node at 100.1.1.2. The example uses the Open vSwitch plugin and agent."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:14(para)
msgid "<emphasis role=\"bold\">Note</emphasis> the setup can be tweaked to make use of another supported plugin and its agent."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:24(para)
msgid "Here are some nodes in the setup."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:30(th)
msgid "Node"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:36(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:79(emphasis) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:91(emphasis)
msgid "Controller Node"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:43(emphasis)
msgid "Note"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:37(td)
msgid "Runs the OpenStack Networking service, OpenStack Identity and all of the OpenStack Compute services that are required to deploy VMs (nova-api, nova-scheduler, for example). The node must have at least one network interface, which is connected to the \"Management Network\". The hostname is 'controlnode', which every other node resolve to the controller node's IP. <placeholder-1/> The nova-network service should not be running. This is replaced by OpenStack Networking."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:49(td)
msgid "Runs the OpenStack Networking L2 agent and the OpenStack Compute services that run VMs (nova-compute specifically, and optionally other nova-* services depending on configuration). The node must have at least two network interfaces. The first is used to communicate with the controller node via the management network. The second interface is used for the VM traffic on the Data network. The VM will be able to receive its IP address from the DHCP agent on this network."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:63(td)
msgid "Runs OpenStack Networking L2 agent and the DHCP agent. The DHCP agent will allocate IP addresses to the VMs on the network. The node must have at least two network interfaces. The first is used to communicate with the controller node via the management network. The second interface will be used for the VM traffic on the data network."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:72(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:281(caption)
msgid "Router"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:73(td)
msgid "Router has IP 30.0.0.1, which is the default gateway for all VMs. The router should have ability to access public networks."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:78(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:90(para)
msgid "The demo assumes the following:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:82(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:94(para)
msgid "Relevant OpenStack Compute services are installed, configured and running."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:86(para)
msgid "Glance is installed, configured and running. In addition to this there should be an image."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:90(para)
msgid "OpenStack Identity is installed, configured and running. An OpenStack Networking user <emphasis role=\"bold\">quantum</emphasis> should be created on tenant <emphasis role=\"bold\">servicetenant</emphasis> with password <emphasis role=\"bold\">servicepassword</emphasis>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:100(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:111(para)
msgid "RabbitMQ is running with default guest and its password"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:103(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:114(para)
msgid "MySQL server (user is <emphasis role=\"bold\">root</emphasis> and password is <emphasis role=\"bold\">root</emphasis>)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:98(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:109(para)
msgid "Additional services <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:114(para)
msgid "OpenStack Compute compute is installed and configured"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:118(title) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:129(title)
msgid "Installation"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:122(emphasis) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:133(emphasis)
msgid "Controller Node - OpenStack Networking Server"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:124(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:135(para)
msgid "Install the OpenStack Networking server."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:127(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:138(para)
msgid "Create database <emphasis role=\"bold\">ovs_quantum</emphasis>. See the section on the <link linkend=\"arch_overview\">Core Plugins</link> for the exact details."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:135(para)
msgid "Update the OpenStack Networking configuration file, <emphasis role=\"bold\">/etc/quantum/quantum.conf</emphasis> setting plugin choice and Identity Service user as necessary:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:164(para)
msgid "Start the OpenStack Networking service"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:169(emphasis) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:186(emphasis)
msgid "Compute Node - OpenStack Compute"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:171(para)
msgid "Install the nova-compute service."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:174(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:191(para)
msgid "Update the OpenStack Compute configuration file, <emphasis role=\"bold\">/etc/nova/nova.conf. Make sure the following is at the end of this file</emphasis>:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:190(para)
msgid "Restart the OpenStack Compute service"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:195(emphasis) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:212(emphasis)
msgid "Compute and Network Node - L2 Agent"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:197(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:214(para)
msgid "Install the L2 agent."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:224(para)
msgid "Create the network bridge <emphasis role=\"bold\">br-eth0</emphasis> (All VM communication between the nodes will be done via eth0):"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:233(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:259(para)
msgid "Start the OpenStack Networking L2 agent"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:238(emphasis) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:270(emphasis)
msgid "Network Node - DHCP Agent"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:240(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:272(para)
msgid "Install the DHCP agent."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:253(para)
msgid "Update the DHCP configuration file <emphasis role=\"bold\">/etc/quantum/dhcp_agent.ini</emphasis>:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:268(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:344(para)
msgid "All of the commands below can be executed on the network node."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:281(para)
msgid "Get the tenant ID (Used as $TENANT_ID later):"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:297(para)
msgid "Get the User information:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:312(para)
msgid "Create a internal shared network on the demo tenant ($TENANT_ID will be b7445f221cda4f4a8ac7db6b218b1339):"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:335(para)
msgid "Create a subnet on the network:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:356(para)
msgid "Create a server for tenant A:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:367(para)
msgid "Ping the server of tenant A:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:375(para)
msgid "Ping the public network within the server of tenant A:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:386(para)
msgid "Note: The 192.168.1.1 is an IP on public network that the router is connecting."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:388(para)
msgid "Create servers for other tenants"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_flat.xml:389(para)
msgid "We can create servers for other tenants with similar commands. Since all these VMs share the same subnet, they will be able to access each other."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:6(title)
msgid "Advanced Operational Features"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:8(title)
msgid "Logging Settings"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:9(para)
msgid "OpenStack Networking components use Python logging module to do logging. Logging configuration can be provided in <filename>quantum.conf</filename> or as command line options. Command options will override ones in <filename>quantum.conf</filename>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:13(para)
msgid "Two ways to specify the logging configuration for OpenStack Networking components:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:17(para)
msgid "Provide logging settings in a logging configuration file."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:18(para)
msgid "Please see <link href=\"http://docs.python.org/howto/logging.html\">Python Logging HOWTO</link> for logging configuration file."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:21(para)
msgid "Provide logging setting in <filename>quantum.conf</filename>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:48(title)
msgid "Notifications"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:50(title) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:431(caption)
msgid "Notification Options"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:51(para)
msgid "Notifications can be sent when OpenStack Networking resources such as network, subnet and port are created, updated or deleted. To support DHCP agent, rpc_notifier driver must be set. To set up the notification, edit notification options in <filename>quantum.conf</filename>:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:87(title)
msgid "Setting Cases"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:89(title)
msgid "Logging and RPC"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:90(para)
msgid "The options below will make OpenStack Networking server send notifications via logging and RPC. The logging options are described in <link linkend=\"ch_adv_logging\">Logging Settings</link>. RPC notifications will go to 'notifications.info' queue binded to a topic exchange defined by 'control_exchange' in <filename>quantum.conf</filename>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:127(title)
msgid "Multiple RPC Topics"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:128(para)
msgid "The options below will make OpenStack Networking server send notifications to multiple RPC topics. RPC notifications will go to 'notifications_one.info' and 'notifications_two.info' queues binded to a topic exchange defined by 'control_exchange' in <filename>quantum.conf</filename>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:166(title)
msgid "Quotas"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:167(para)
msgid "Quota is a function to limit number of resources. You can enforce default quota for all tenants. You will get error when you try to create more resources than the limit."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:171(para)
msgid "Per-tenant quota configuration is also supported by quota extension API. See <link linkend=\"cfg_quotas_per_tenant\"> Per-tenant quota configuration</link> for details."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:177(title)
msgid "Basic quota configuration"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:178(para)
msgid "In OpenStack Networking default quota mechanism, all tenants have a same quota value, i.e., a number of resources that a tenant can create. This is enabled by default."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:181(para)
msgid "The value of quota is defined in the OpenStack Networking configuration file (<filename>quantum.conf</filename>). If you want to disable quotas for a specific resource (e.g., network, subnet, port), remove a corresponding item from <literal>quota_items</literal>. Each of the quota values in the example below is the default value."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:200(para)
msgid "OpenStack Networking also supports quotas for L3 resources: router and floating IP. You can configure them by adding the following lines to <literal>quotas</literal> section in <filename>quantum.conf</filename>. (Note that <literal>quota_items</literal> does not affect these quotas.)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:209(para)
msgid "OpenStack Networking also supports quotas for security group resources: number of security groups and the number of rules per security group. You can configure them by adding the following lines to <literal>quotas</literal> section in <filename>quantum.conf</filename>. (Note that <literal>quota_items</literal> does not affect these quotas.)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:221(title)
msgid "Per-tenant quota configuration"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:222(para)
msgid "OpenStack Networking also supports per-tenant quota limit by quota extension API. To enable per-tenant quota, you need to set <literal>quota_driver</literal> in <literal>quantum.conf</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:225(para)
msgid "When per-tenant quota is enabled, the output of the following command contains <literal>quotas</literal>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:254(para)
msgid "In Folsom release, per-tenant quota is supported by Open vSwitch plugin, Linux Bridge plugin, and Nicira NVP plugin and cannot be used with other plugins."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:258(para)
msgid "There are four CLI commands to manage per-tenant quota."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:265(para)
msgid "Only users with 'admin' role can change a quota value. Note that the default set of quotas are enforced for all tenants by default, so there is no <literal>quota-create</literal> command."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:270(para)
msgid "<literal>quota-list</literal> displays a list of tenants for which per-tenant quota is enabled. The tenants who have the default set of quota limits are not listed. This command is permitted to only 'admin' users."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:282(para)
msgid "<literal>quota-show</literal> reports the current set of quota limits for the specified tenant. Regular (non-admin) users can call this command (without --tenant_id parameter). If per-tenant quota limits are not defined for the tenant, the default set of quotas are displayed."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:298(para)
msgid "The below is an example called by a non-admin user."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:311(para)
msgid "You can update a quota of the given tenant by <literal>quota-update</literal> command."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:312(para)
msgid "Update the limit of network quota."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:323(para)
msgid "You can update quotas of multiple resources in one command."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:334(para)
msgid "To update the limits of L3 resource (router, floating IP), we need to specify new values of the quotas after '--'. The example below updates the limit of the number of floating IPs for the given tenant."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:349(para)
msgid "You can update the limits of multiple resources including L2 resources and L3 resource in one command."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_operational_features.xml:362(para)
msgid "To clear per-tenant quota limits, use <literal>quota-delete</literal>. After <literal>quota-delete</literal>, quota limits enforced to the tenant are reset to the default set of quotas."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:4(title)
msgid "Configuring other OpenStack Components"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:6(title)
msgid "OpenStack Identity Configuration for OpenStack Networking"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:9(title)
msgid "To Configure OpenStack Compute for OpenStack Networking"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:12(title)
msgid "To Create an OpenStack Networking Service Entry"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:14(para)
msgid "OpenStack Networking needs to be available in the  OpenStack Compute service catalog.  The steps for this depend on whether you are using the SQL catalog driver or the template catalog driver."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:19(para)
msgid "With the <emphasis>SQL driver</emphasis>, for a given region ($REGION), IP address of the OpenStack Networking server ($IP), and service ID ($ID) returned by the OpenStack Compute service catalog, run:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:25(para)
msgid "Make a note of the ID returned by the command and put it in the $ID location."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:28(para)
msgid "Here's an example with real values:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:40(para)
msgid "With the <emphasis>template driver</emphasis>, for a given region ($REGION) and IP address of the OpenStack Networking server ($IP), add the following content to your OpenStack Compute catalog template file (default_catalog.templates)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:49(para)
msgid "Here is an example with real values:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:57(title)
msgid "Create OpenStack Networking Service User"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:59(para)
msgid "For OpenStack Compute to speak to the OpenStack Networking API, and for some internal components of OpenStack Networking to communicate with the OpenStack Networking API, you need to provide them with admin user credentials that they can use when accessing the OpenStack Networking API.  The suggested approach is to create a special 'service' tenant, create a quantum user within this tenant, and to assign this user an 'admin' role. Kindly check the ID for user, role and tenant."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:70(para)
msgid "For example:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:79(para)
msgid "See the OpenStack Installation Guides for more details about creating service entries and service users."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:83(title)
msgid "Running OpenStack Compute with OpenStack Networking"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:85(para)
msgid "Unlike traditional OpenStack Compute deployments, when OpenStack Networking is in use, OpenStack Compute should not run a nova-network. Instead, OpenStack Compute delegates almost all of the network-related decisions to OpenStack Networking. This means many of the network-related CLI command and configuration options you are familiar with from using OpenStack Compute do not work with OpenStack Networking."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:93(para)
msgid "Therefore, it is very important that you refer to this guide when configuring networking, rather than relying on OpenStack Compute networking documentation or past experience with OpenStack Compute. If a Nova CLI command or configuration option related to networking is not mentioned in this guide, it is likely not supported for use with OpenStack Networking. In particular, using CLI tools like 'nova-manage' and 'nova' to manage networks or IP addressing, including both fixed and floating IPs, is not supported with OpenStack Networking."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:104(para)
msgid "It is strongly recommended that you uninstall nova-network and reboot any physical nodes that had been running nova-network before using them to run OpenStack Networking. Inadvertently running the nova-network process while using OpenStack Networking can cause problems, as can stale iptables rules pushed down by previously running nova-network."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:113(title)
msgid "Configuring OpenStack Compute to reach the OpenStack Networking API"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:115(para)
msgid "Each time a VM is provisioned or deprovisioned in OpenStack Compute, nova-* services communicate with OpenStack Networking via the standard API. To do so, it requires the following items in the nova.conf used by each nova-compute and nova-api instance: "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:122(para)
msgid "network_api_class: must be modified from default to nova.network.quantumv2.api.API indicate that OpenStack Networking should be used rather than the traditional nova-network networking model."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:129(para)
msgid "quantum_url: must include the hostname/IP and port of the Quantum server for this deployment."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:133(para)
msgid "quantum_auth_strategy: should be kept as default 'keystone' for all production deployments."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:137(para)
msgid "quantum_admin_tenant_name: must be modified to be the name of the service tenant created in the above section on OpenStack Compute configuration."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:143(para)
msgid "quantum_admin_username: must be modified to be the name of the user created in the above section on OpenStack Compute configuration."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:149(para)
msgid "quantum_admin_password: must be modified to be the password of the user created in the above section on OpenStack Compute configuration."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:155(para)
msgid "quantum_admin_auth_url: must be modified to point to the OpenStack Compute server IP and port. This is the Identity (keystone) admin API server IP and port value, and not the Identity service API IP and port."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:164(title)
msgid "Configuring Vif-plugging in OpenStack Compute"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:166(para)
msgid "When nova-compute creates a VM, it must \"plug\" each of the VM's vNICs into an OpenStack Networking controlled virtual switch, and inform the virtual switch about the OpenStack Networking port-id associated with each vNIC. This is done by specifying a field in the nova.conf of the nova-compute instance indicating what type of ''vif-plugging'' should be used. The exact field(s) you need to set depend on your plugin. For plugins not listed below, see the plugin's own documentation."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:177(title)
msgid "Vif-plugging with Open vSwitch Plugin"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:178(para)
msgid "The choice of vif-plugging for the Open vSwitch plugin depends on what version of libvirt you are using, as well as whether you are using OpenStack Compute security filtering (i.e., security groups, provider firewall, VM spoofing prevention)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:185(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:245(para)
msgid "When using libvirt (any version) with OpenStack Compute security filtering: libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:190(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:250(para)
msgid "When using libvirt (version &lt; 0.9.11) without OpenStack Compute security filtering: libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtOpenVswitchDriver"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:196(para) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:256(para)
msgid "When using libvirt (version &gt;= 0.9.11) without OpenStack Compute security groups: libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtOpenVswitchVirtualPortDriver"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:202(title)
msgid "Checking your libvirt version"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:203(para)
msgid "To check your libvirt version, use <placeholder-1/>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:209(title)
msgid "Vif-plugging with Linux Bridge Plugin"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:212(para)
msgid "When using libvirt (any version): libvirt_vif_driver=nova.virt.libvirt.vif.QuantumLinuxBridgeVIFDriver"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:218(title)
msgid "Vif-plugging with Nicira NVP Plugin"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:219(para)
msgid "The choice of vif-plugging for the NVP Plugin depends on what version of libvirt you are using (this assumes you are using NVP for security groups and VM spoof prevention)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:223(para)
msgid "When using libvirt (version &lt; 0.9.11): libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtOpenVswitchDriver"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:227(para)
msgid "When using libvirt (version &gt;= 0.9.11): libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtOpenVswitchVirtualPortDriver"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:231(para)
msgid "When using XenServer: xenapi_vif_driver=nova.virt.xenapi.vif.XenAPIOpenVswitchDriver"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:237(title)
msgid "Vif-plugging with NEC OpenFlow Plugin"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:238(para)
msgid "The choice of vif-plugging for the NEC plugin depends on what version of libvirt you are using, as well as whether you are using OpenStack Compute security filtering (i.e., security groups, provider firewall, VM spoofing prevention)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:264(title)
msgid "Vif-plugging with Big Switch, Floodlight REST Proxy Plugin"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:267(para)
msgid "When using libvirt (any version) and Nova security filtering: libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:274(title)
msgid "Example nova.conf (for nova-compute and nova-api)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml:275(para)
msgid "Example values for the above settings, assuming a cloud controller node running OpenStack Compute and OpenStack Networking with an IP address of 192.168.1.2 and vif-plugging using the LibvirtOpenVswitchDriver with virtio enabled."
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:12(None) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:15(None) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:449(None) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:452(None)
msgid "@@image: 'figures/UseCase-MultiRouter.png'; md5=cdfb679dac788eaa8207635456d4e712"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:26(None) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:29(None)
msgid "@@image: 'figures/demo_routers_with_private_networks.png'; md5=985b8cacfd7161ce50ee13106b27f854"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:4(title)
msgid "Per-tenant Routers with Private Networks"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:5(para)
msgid "This section describes how to install the OpenStack Networking service and its components for the \"<link linkend=\"use_cases_tenant_router\">Use Case: Per-tenant Routers with Private Networks </link>\"."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:19(para)
msgid "The diagram below shows the setup. All of the nodes should have one interface for management traffic. The example uses the Open vSwitch plugin. The agents are configured to use GRE for data transport. There is an external network where we will have floating IPs and router gateway ports. A physical router is connecting these floating IPs and router gateway ports to outside world."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:32(para)
msgid "Below are nodes in the setup: <informaltable rules=\"all\" width=\"100%\"><col width=\"20%\"/><col width=\"80%\"/><thead><tr><th>Node</th><th>Description</th></tr></thead><tbody><tr><td>Controller Node</td><td>Runs the OpenStack Networking service, OpenStack Identity and all of the OpenStack Compute services that are required to deploy VMs (nova-api, nova-scheduler, for example). The node must have at least one network interface, which is connected to the \"Management Network\". The hostname is 'controlnode', which every other node resolve to the controller node's IP. <emphasis role=\"bold\">Note</emphasis> The nova-network service should not be running. This is replaced by OpenStack Networking.</td></tr><tr><td>Compute Node</td><td>Runs the OpenStack Networking L2 agent and the OpenStack Compute services that run VMs (nova-compute specifically, and optionally other nova-* services depending on configuration). The node must have at least two network interfaces. The first is used to communicate with the controller node via the management network. The second interface is used for the VM traffic on the Data network. The VM will be able to receive its IP address from the DHCP agent on this network.</td></tr><tr><td>Network Node</td><td>Runs OpenStack Networking L2 agent, DHCP agent and L3 agent. This node will have access to the external network. The DHCP agent will allocate IP addresses to the VMs on data network (Technically, the addresses are allocated by the OpenStack Networking server, and distributed by the dhcp agent). The node must have at least two network interfaces. The first is used to communicate with the controller node via the management network. The second interface will be used as external network. GRE tunnels will be set up as data network.</td></tr><tr><td>Router</td><td>Router has IP 30.0.0.1, which is the default gateway for all VMs. The router should have ability to access public networks.</td></tr></tbody></informaltable>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:98(para)
msgid "Glance is installed, configured and running. In addition to this there should be an image named tty."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:102(para)
msgid "OpenStack Identity is installed, configured and running. A OpenStack Networking user named <emphasis role=\"bold\">quantum</emphasis> should be created on tenant <emphasis role=\"bold\">servicetenant</emphasis> with password <emphasis role=\"bold\">servicepassword</emphasis>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:125(para)
msgid "OpenStack Compute is installed and configured"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:146(para)
msgid "Update the OpenStack Networking configuration file, <emphasis role=\"bold\">/etc/quantum/quantum.conf</emphasis>, with plugin choice and Identity Service user as necessary:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:175(para)
msgid "Start the OpenStack Networking server"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:176(para)
msgid "The OpenStack Networking server can be a service of the operating system. The command may be different to start the service on different operating systems. One example of the command to run the OpenStack Networking server directly is:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:188(para)
msgid "Install OpenStack Compute services."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:207(para)
msgid "Restart relevant OpenStack Compute services"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:217(para)
msgid "Add the integration bridge to the Open vSwitch"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:221(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:275(para)
msgid "Update the OpenStack Networking configuration file, <emphasis role=\"bold\">/etc/quantum/quantum.conf</emphasis>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:231(para)
msgid "Update the plugin configuration file, <emphasis role=\"bold\">/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini</emphasis>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:234(para)
msgid "Compute Node:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:242(para)
msgid "Network Node:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:252(para)
msgid "Create the integration bridge <emphasis role=\"bold\">br-int</emphasis>:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:260(para)
msgid "The OpenStack Networking Open vSwitch L2 agent can be a service of operating system. The command may be different to start the service on different operating systems. However the command to run it directly is kind of like:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:284(literal)
msgid "allow_overlapping_ips"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:284(emphasis)
msgid "We set <placeholder-1/> because we have overlapping subnets for TenantA and TenantC."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:288(para)
msgid "Update the DHCP configuration file <emphasis role=\"bold\">/etc/quantum/dhcp_agent.ini</emphasis>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:295(para)
msgid "The OpenStack Networking DHCP agent can be a service of operating system. The command may be different to start the service on different operating systems. However the command to run it directly is kind of like:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:305(emphasis)
msgid "Network Node - L3 Agent"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:307(para)
msgid "Install the L3 agent."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:310(para)
msgid "Add the external network bridge"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:314(para)
msgid "Add the physical interface, for example eth0, that is connected to the outside network to this bridge"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:319(para)
msgid "Update the L3 configuration file <emphasis role=\"bold\">/etc/quantum/l3_agent.ini</emphasis>:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:325(literal)
msgid "use_namespaces"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:325(emphasis)
msgid "We set <placeholder-1/> (It is True by default.) because we have overlapping subnets for TenantA and TenantC and we are going to host the routers with one l3 agent network node."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:329(para)
msgid "Start the L3 agent"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:330(para)
msgid "The OpenStack Networking L3 agent can be a service of operating system. The command may be different to start the service on different operating systems. However the command to run it directly is kind of like:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:357(para)
msgid "Get the tenant ID (Used as $TENANT_ID later)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:373(para)
msgid "Get the user information"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:388(para)
msgid "Create the external network and its subnet by admin user:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:427(literal)
msgid "provider:network_type local"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:430(literal)
msgid "router:external true"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:426(emphasis)
msgid "<placeholder-1/> means we don't need OpenStack Networking to realize this network through provider network. <placeholder-2/> means we are creating an external network, on which we can create floating ip and router gateway port."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:437(para)
msgid "Add an IP on external network to br-ex"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:438(para)
msgid "Since we are using br-ex as our external network bridge, we will add an IP 30.0.0.100/24 to br-ex and then ping our VM's floating IP from our network node."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:445(para)
msgid "Serve TenantA"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:446(para)
msgid "For TenantA, we will create a private network, a subnet, a server, a router and a floating IP."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:449(para)
msgid "Create a network for TenantA"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:465(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:627(para)
msgid "After that we can use admin user to query the network's provider network information:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:483(para)
msgid "We can see that it has GRE tunnel ID (I.E. provider:segmentation_id) 1."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:486(para)
msgid "Create a subnet on the network TenantA-Net"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:508(para)
msgid "Create a server for TenantA"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:519(para)
msgid "Create and configure a router for TenantA:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:541(emphasis) ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:704(emphasis)
msgid "We are using admin user to run last command since our external network is owned by admin tenant."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:544(para)
msgid "Associate a floating IP for TenantA_VM1"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:546(para)
msgid "1. Create a floating IP"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:560(para)
msgid "2. Get the port ID of the VM with ID 7c5e6499-7ef7-4e36-8216-62c2941d21ff"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:568(para)
msgid "3. Associate the floating IP with the VM port"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:580(para)
msgid "Ping the public network from the server of TenantA"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:581(para)
msgid "In my environment, 192.168.1.0/24 is my public network connected with my physical router, which also connects to the external network 30.0.0.0/24. With the floating IP and virtual router, we can ping the public network within the server of tenant A:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:596(para)
msgid "Ping floating IP of the TenantA's server"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:610(para)
msgid "Create other servers for TenantA"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:611(para)
msgid "We can create more servers for TenantA and add floating IPs for them."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:615(para)
msgid "Serve TenantC"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:616(para)
msgid "For TenantC, we will create two private networks with subnet 10.0.0.0/24 and subnet 10.0.1.0/24, some servers, one router to connect to these two subnets and some floating IPs."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:620(para)
msgid "Create networks and subnets for TenantC"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:662(para)
msgid "We can see that we have GRE tunnel IDs (I.E. provider:segmentation_id) 2 and 3. And also note down the network IDs and subnet IDs because we will use them to create VMs and router."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:666(para)
msgid "Create a server TenantC-VM1 for TenantC on TenantC-Net1"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:670(para)
msgid "Create a server TenantC-VM3 for TenantC on TenantC-Net2"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:674(para)
msgid "List servers of TenantC"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:682(para)
msgid "Note down the server IDs since we will use them later."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:685(para)
msgid "Make sure servers get their IPs"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:686(para)
msgid "We can use VNC to log on the VMs to check if they get IPs. If not, we have to make sure the OpenStack Networking components are running right and the GRE tunnels work."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:693(para)
msgid "Create and configure a router for TenantC:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:707(para)
msgid "Checkpoint: ping from within TenantC's servers"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:708(para)
msgid "Since we have a router connecting to two subnets, the VMs on these subnets are able to ping each other. And since we have set the router's gateway interface, TenantC's servers are able to ping external network IPs, such as 192.168.1.1, 30.0.0.1 etc."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:712(para)
msgid "Associate floating IPs for TenantC's servers"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_demo_routers_with_private_networks.xml:714(para)
msgid "We can use the similar commands as we used in TenantA's section to finish this task."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:6(title)
msgid "Limitations"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:10(para)
msgid "<emphasis>OpenStack Networking overlapping IPs do not work with Nova security groups or Nova metadata server:</emphasis> Nova was designed assuming that a particular IP address will only ever be used by a single VM at any time. OpenStack Networking supports overlapping IPs if the allow_overlapping_ips config value is set to 'True'. We default this value to false to prevent unintentionally running Nova security groups or metadata server with overlapping IPs. If you enable this flag, you must disable both Nova security groups and the Nova metadata service."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:25(para)
msgid "<emphasis>No equivalent for nova-network --multi_host flag:</emphasis> Nova-network has a model where the L3, NAT, and DHCP processing happen on the compute node itself, rather than a dedicated networking node. OpenStack Networking does not have an equivalent configuration, but is likely to add a similar capability in the future. However, since the nova-network multi_host design has some significant limitations in terms of deployment scale (limited to a single physical L2) and L3 forwarding behavior (does not map to a single L3 router for traffic between instances on separate networks), the OpenStack Networking feature may not be an exact match, or may be limited to a subnet of all OpenStack Networking deployment scenarios."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:43(para)
msgid "<emphasis>Linux network namespace required on nodes running quantum-l3-agent or quantum-dhcp-agent: </emphasis>. In order to support overlapping IP addresses, the OpenStack Networking DHCP and L3 agents use Linux network namespaces by default. The hosts running these processes must support network namespaces. To support network namespaces, the following are required:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:54(para)
msgid "Linux kernel 2.6.24 or newer (with CONFIG_NET_NS=y in kernel configuration) and"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:58(para)
msgid "iproute2 utilities ('ip' command) version 3.1.0 (aka 20111117) or newer"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:62(para)
msgid "To check whether your host supports namespaces try running the following as root:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:66(para)
msgid "If the preceding commands do not produce errors, your platform is likely sufficient to use the dhcp-agent or l3-agent with namespace. In our experience, Ubuntu 12.04 or later support namespaces as does Fedora 17 and new, but some older RHEL platforms do not by default. It may be possible to upgrade the iproute2 package on a platform that does not support namespaces by default."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:71(para)
msgid "If you need to disable namespaces, make sure the <filename>quantum.conf</filename> used by quantum-server has the following setting:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:75(para)
msgid "and that the dhcp_agent.ini and l3_agent.ini have the following setting:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:78(para)
msgid "If the host does not support namespaces then the <systemitem class=\"service\">quantum-l3-agent</systemitem> and <systemitem class=\"service\">quantum-dhcp-agent</systemitem> should be run on different hosts. This is due to the fact that there is no isolation between the IP addresses created by the L3 agent and by the DHCP agent. By manipulating the routing the user can ensure that these networks have access to one another."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:84(para)
msgid "If you run both L3 + DHCP services on the same node, you should enable namespaces to avoid conflicts with routes :"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:90(para)
msgid "<emphasis>No IPv6 support for L3 agent:</emphasis> The quantum-l3-agent supports only IPv4 forwarding. Currently, There are no errors provided if you configure IPv6 addresses via the API."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:94(para)
msgid "<emphasis>L3 Agent supports limited scale for OpenStack Networking Routers:</emphasis> The L3 agent polls the OpenStack Networking API to learn about changes to L3 configuration. If there are a large number of routers or router ports, this can lead to heavy load on the database used by an OpenStack Networking plugin. The suggested work-around is to increase the polling_interval value in l3_agent.ini . This will increase the possible time between when a L3 configuration change happens via the API and when it affects data forwarding."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:107(para)
msgid "<emphasis>ZeroMQ support is experimental</emphasis>: Some agents, including quantum-dhcp-agent, quantum-openvswitch-agent, and quantum-linuxbridge-agent use RPC to communicate. ZeroMQ is an available option in the configuration file, but has not been tested and should be considered experimental. In particular, there are believed to be issues with ZeroMQ and the dhcp agent."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:113(para)
msgid "<emphasis>MetaPlugin is experimental</emphasis>: This release includes a \"MetaPlugin\" that is intended to support multiple plugins at the same time for different API requests, based on the content of those API requests. This functionality has not been widely reviewed or tested by the core team, and should be considered experimental until further validation is performed."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:119(para)
msgid "<emphasis>Horizon does not support Routers/Floating IPs with OpenStack Networking:</emphasis> Horizon support is limited to operations on OpenStack Networking Networks, Subnets, and Ports. Routers and Floating IPs must be configured via CLI."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml:126(para)
msgid "L3 Router Extension does not support IPv6."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:4(title)
msgid "Advanced Configuration Options"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:5(para)
msgid "This section describes advanced configurations options for various system components (i.e. config options where the default is usually ok, but that the user may want to tweak). After installing from packages, $QUANTUM_CONF_DIR is <filename>/etc/quantum</filename>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:9(title)
msgid "OpenStack Networking Server with Plugin"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:10(para)
msgid "This is the web server that runs the OpenStack Networking API Web Server. It is responsible for loading a plugin and passing the API calls to the plugin for processing. The quantum-server should receive one of more configuration files as it its input, for example:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:17(para)
msgid "The quantum config contains the common quantum configuration parameters. The plugin config contains the plugin specific flags. The plugin that is run on the service is loaded via the configuration parameter core_plugin. In some cases a plugin may have an agent that performs the actual networking. Specific configuration details can be seen in the Appendix - Configuration File Options."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:22(para)
msgid "Most plugins require a SQL database. After installing and starting the database server, set a password for the root account and delete the anonymous accounts:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:27(para)
msgid "Create a database and user account specifically for plugin:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:32(para)
msgid "Once the above is done you can update the settings in the relevant plugin configuration files. The plugin specific configuration files can be found at $QUANTUM_CONF_DIR/plugins."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:35(para)
msgid "Some plugins have a L2 agent that performs the actual networking. That is, the agent will attach the virtual machine NIC to the OpenStack Networking network. Each node should have an L2 agent running on it. Note that the agent receives the following input parameters:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:40(para)
msgid "Two things need to be done prior to working with the plugin:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:43(para)
msgid "Ensure that the core plugin is updated."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:46(para)
msgid "Ensure that the database connection is correctly set."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:49(para)
msgid "The table below contains examples for these settings. Some Linux packages may provide installation utilities that configure these. <table rules=\"all\"><caption>Settings</caption><col width=\"35%\"/><col width=\"65%\"/><thead><tr><th>Parameter</th><th>Value</th></tr></thead><tbody><tr><td><emphasis role=\"bold\">Open vSwitch</emphasis></td><td/></tr><tr><td>core_plugin ($QUANTUM_CONF_DIR/quantum.conf)</td><td>quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2</td></tr><tr><td>sql_connection (in the plugin configuration file)</td><td>mysql://&lt;username&gt;:&lt;password&gt;@localhost/ovs_quantum?charset=utf8</td></tr><tr><td>Plugin Configuration File</td><td>$QUANTUM_CONF_DIR/plugins/openvswitch/ovs_quantum_plugin.ini</td></tr><tr><td>Agent </td><td>quantum-openvswitch-agent</td></tr><tr><td><emphasis role=\"bold\">Linux Bridge</emphasis></td><td/></tr><tr><td>core_plugin ($QUANTUM_CONF_DIR/quantum.conf)</td><td>quantum.plugins.linuxbridge.lb_quantum_plugin.LinuxBridgePluginV2</td></tr><tr><td>sql_connection (in the plugin configuration file)</td><td>mysql://&lt;username&gt;:&lt;password&gt;@localhost/quantum_linux_bridge?charset=utf8</td></tr><tr><td>Plugin Configuration File</td><td>$QUANTUM_CONF_DIR/plugins/linuxbridge/linuxbridge_conf.ini</td></tr><tr><td>Agent </td><td>quantum-linuxbridge-agent</td></tr></tbody></table>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:103(para)
msgid "All of the plugin configuration files options can be found in the Appendix - Configuration File Options."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:107(title)
msgid "DHCP Agent"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:108(para)
msgid "There is an option to run a DHCP server that will allocate IP addresses to virtual machines running on the network. When a subnet is created, by default, the subnet has DHCP enabled."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:111(para)
msgid "The node that runs the DHCP agent should run:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:114(para)
msgid "Currently the DHCP agent uses dnsmasq to perform that static address assignment."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:116(para)
msgid "A driver needs to be configured that matches the plugin running on the service. <table rules=\"all\"><caption>Basic settings</caption><col width=\"50%\"/><col width=\"50%\"/><thead><tr><th>Parameter </th><th>Value </th></tr></thead><tbody><tr><td><emphasis role=\"bold\">Open vSwitch</emphasis></td><td/></tr><tr><td>interface_driver ($QUANTUM_CONF_DIR/dhcp_agent.ini)</td><td>quantum.agent.linux.interface.OVSInterfaceDriver</td></tr><tr><td><emphasis role=\"bold\">Linux Bridge</emphasis></td><td/></tr><tr><td>interface_driver ($QUANTUM_CONF_DIR/dhcp_agent.ini)</td><td>quantum.agent.linux.interface.BridgeInterfaceDriver</td></tr></tbody></table>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:146(para)
msgid "All of the DHCP agent configuration options can be found in the <link linkend=\"dhcp_agent_ini\"> Appendix - Configuration File Options</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:149(title) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:225(title)
msgid "Namespace"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:150(para)
msgid "By default the DHCP agent makes use of Linux network namespaces in order to support overlapping IP addresses. Requirements for network namespaces support are described in the <link linkend=\"ch_limitations\">Limitation</link> section."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:153(para)
msgid "<emphasis role=\"bold\">If the Linux installation does not support network namespace, you must disable using network namespace in the DHCP agent config file</emphasis> (The default value of use_namespaces is True)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:161(title)
msgid "L3 Agent"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:162(para)
msgid "There is an option to run a L3 agent that will give enable layer 3 forwarding and floating IP support. The node that runs the L3 agent should run:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:166(para)
msgid "A driver needs to be configured that matches the plugin running on the service. The driver is used to create the routing interface. <table rules=\"all\"><caption>Basic settings</caption><col width=\"50%\"/><col width=\"50%\"/><thead><tr><th>Parameter </th><th>Value </th></tr></thead><tbody><tr><td><emphasis role=\"bold\">Open vSwitch</emphasis></td><td/></tr><tr><td>interface_driver ($QUANTUM_CONF_DIR/l3_agent.ini) </td><td>quantum.agent.linux.interface.OVSInterfaceDriver </td></tr><tr><td>external_network_bridge ($QUANTUM_CONF_DIR/l3_agent.ini) </td><td>br-ex </td></tr><tr><td><emphasis role=\"bold\">Linux Bridge</emphasis></td><td/></tr><tr><td>interface_driver ($QUANTUM_CONF_DIR/l3_agent.ini) </td><td>quantum.agent.linux.interface.BridgeInterfaceDriver</td></tr><tr><td>external_network_bridge ($QUANTUM_CONF_DIR/l3_agent.ini) </td><td>This field must be empty (or the bridge name for the external network).</td></tr></tbody></table>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:209(para)
msgid "OpenStack Identity authentication:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:211(para)
msgid "For example,"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:215(para)
msgid "Admin user details:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:206(para)
msgid "The L3 agent communicates with the OpenStack Networking server via the OpenStack Networking API, so the following configuration is required: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:222(para)
msgid "All of the L3 agent configuration options can be found in the <link linkend=\"l3_agent\"> Appendix - Configuration File Options</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:226(para)
msgid "By default the L3 agent makes use of Linux network namespaces in order to support overlapping IP addresses. Requirements for network namespaces support are described in the <link linkend=\"ch_limitations\">Limitation</link> section."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:229(para)
msgid "<emphasis role=\"bold\">If the Linux installation does not support network namespace, you must disable using network namespace in the L3 agent config file</emphasis> (The default value of use_namespaces is True)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:234(para)
msgid "When use_namespaces is set as False, only one router ID can be supported per node. This must be configured via the configuration variable <emphasis>router_id</emphasis>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:240(para)
msgid "To configure it, you need to run the OpenStack Networking service and create a router, and then set an ID of the router created to <emphasis>router_id</emphasis> in the L3 agent configuration file."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:258(title)
msgid "Multiple Floating IP Pools"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:259(para)
msgid "The L3 API in OpenStack Networking supports multiple floating IP pools. In OpenStack Networking, a floating IP pool is represented as an external network and a floating IP is allocated from a subnet associated with the external network. Since each L3 agent can be associated with at most one external network, we need to invoke multiple L3 agent to define multiple floating IP pools. <emphasis role=\"bold\">'gateway_external_network_id'</emphasis> in L3 agent configuration file indicates the external network that the L3 agent handles. You can run multiple L3 agent instances on one host."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:271(para)
msgid "In addition, when you run multiple L3 agents, make sure that <emphasis role=\"bold\">handle_internal_only_routers</emphasis> is set to <emphasis role=\"bold\">True</emphasis> only for one L3 agent in an OpenStack Networking deployment and set to <emphasis role=\"bold\">False</emphasis> for all other L3 agents. Since the default value of this parameter is True, you need to configure it carefully."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:276(para)
msgid "Before starting L3 agents, you need to create routers and external networks, then update the configuration files with UUID of external networks and start L3 agents."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:278(para)
msgid "For the first agent, invoke it with the following l3_agent.ini where handle_internal_only_routers is True."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:286(para)
msgid "For the second (or later) agent, invoke it with the following l3_agent.ini where handle_internal_only_routers is False."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:293(title)
msgid "OpenStack Compute Metadata Server Support"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:294(para)
msgid "To use OpenStack Compute metadata service, metadata_ip and metadata_port in the L3 agent configuration file need to be configured. Accessing from VMs to OpenStack Compute metadata service is forwarded to an external network through OpenStack Networking L3 router. OpenStack Compute metadata service must be reachable from the external network. As the <link linkend=\"ch_limitations\">Limitations section </link> says, note that OpenStack Networking overlapping IPs support and OpenStack Compute metadata service cannot be used together."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:300(para)
msgid "Allowing VMs to reach the metadata service is a big point of confusion with OpenStack Networking. We need to make sure instructions for how to set this up are displayed more prominently than they already are, and that there are instructions for how to validate and troubleshoot in this scenario."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:304(para)
msgid "Example validation includes:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:305(emphasis)
msgid "VALIDATION STEP #1"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:306(para)
msgid "- on network node(l3_agent running) ping to metadata_ip that specified by l3_agent.py"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:308(para)
msgid "if you are not using namespace, just run:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:311(para)
msgid "for example, if the metadata server IP is 172.16.10.5, run:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:314(para)
msgid "if you using namespaces, identify the UUID of the router and run:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:317(para)
msgid "for example, if the router uuid is d7e9ec57-77c2-4046-aebf-d978ed4a4f83 and the metadata server IP is 172.16.10.5, run:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:321(emphasis)
msgid "VALIDATION STEP #2"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:322(para)
msgid "- on metadata server(nova_api server) check connection to vm's subnets using an un-NATed IP address of the VM, such as 10.0.0.2:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:324(emphasis)
msgid "NOTE"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml:325(para)
msgid "OpenStack does not manage this routing for you, so you need to make sure that your host running the metadata service always has a route to reach each private network's subnet via the external network IP of that subnet's OpenStack Networking router. To do this, you can either run OpenStack Networking without namespaces, and run the quantum-l3-agent on the same host as nova-api. Otherwise, you can identify an IP prefix that includes all private network subnet's (e.g., 10.0.0.0/8) and then make sure that your metadata server has a route for that prefix with the OpenStack Networking router's external IP address as the next hop."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:6(title)
msgid "Advanced Features through API Extensions"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:7(para)
msgid "This section discusses two API extensions implemented by several plugins.  We include them in this guide as they are provide capabilities similar to what was available in nova-network and are thus likely to be relevant to a large portion of the OpenStack community. "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:13(title)
msgid "Provider Networks"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:14(para)
msgid "Provider networks allow cloud administrators to create OpenStack Networking networks that map directly to physical networks in the data center.  This is commonly used to give tenants direct access to a \"public\" network that can be used to reach the Internet.  It may also be used to integrate with VLANs in the network that already have a defined meaning (e.g., allow a VM from the \"marketing\" department to be placed on the same VLAN as bare-metal marketing hosts in the same data center)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:24(para)
msgid "The provider extension allows administrators to explicitly manage the relationship between OpenStack Networking virtual networks and underlying physical mechanisms such as VLANs and tunnels. When this extension is supported, OpenStack Networking client users with administrative privileges see additional provider attributes on all virtual networks, and are able to specify these attributes in order to create provider networks."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:33(para)
msgid "As of the Folsom release, the provider extension is supported by the openvswitch and linuxbridge plugins. Configuration of these plugins requires familiarity with this extension."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:38(title)
msgid "Terminology"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:43(para)
msgid "<emphasis role=\"bold\">virtual network</emphasis> - An OpenStack Networking L2 network (identified by a UUID and optional name) whose ports can be attached as vNICs to OpenStack Compute instances and to various OpenStack Networking agents. The openvswitch and linuxbridge plugins each support several different mechanisms to realize virtual networks."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:55(para)
msgid "<emphasis role=\"bold\">physical network</emphasis> - A network connecting virtualization hosts (i.e. OpenStack Compute nodes) with each other and with other network resources. Each physical network may support multiple virtual networks. The provider extension and the plugin configurations identify physical networks using simple string names."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:67(para)
msgid "<emphasis role=\"bold\">tenant network</emphasis> - A \"normal\" virtual network created by/for a tenant. The tenant is not aware of how that network is physically realized."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:74(para)
msgid "<emphasis role=\"bold\">provider network</emphasis> - A virtual network administratively created to map to a specific network in the data center, typically to enable direct access to non-OpenStack resources on that network. Tenants can be given access to provider networks."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:84(para)
msgid "<emphasis role=\"bold\">VLAN network</emphasis> - A virtual network realized as packets on a specific physical network containing IEEE 802.1Q headers with a specific VID field value. VLAN networks sharing the same physical network are isolated from each other at L2, and can even have overlapping IP address spaces. Each distinct physical network supporting VLAN networks is treated as a separate VLAN trunk, with a distinct space of VID values. Valid VID values are 1 through 4094."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:99(para)
msgid "<emphasis role=\"bold\">flat network</emphasis> - A virtual network realized as packets on a specific physical network containing no IEEE 802.1Q header. Each physical network can realize at most one flat network."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:107(para)
msgid "<emphasis role=\"bold\">local network</emphasis> - A virtual network that allows communication within each host, but not across a network. Local networks are intended mainly for single-node test scenarios, but may have other uses."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:116(para)
msgid "<emphasis role=\"bold\">GRE network</emphasis> - A virtual network realized as network packets encapsulated using GRE. GRE networks are also referred to as \"tunnels\". GRE tunnel packets are routed by the host's IP routing table, so GRE networks are not associated by OpenStack Networking with specific physical networks."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:39(para)
msgid "A number of terms are used in the provider extension and in the configuration of plugins supporting the provider extension:<placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:127(para)
msgid "Both the openvswitch and linuxbridge plugins support VLAN networks, flat networks, and local networks. Only the openvswitch plugin currently supports GRE networks, provided that the host's Linux kernel supports the required Open vSwitch features."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:134(title)
msgid "Provider Attributes"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:135(para)
msgid "The provider extension extends the OpenStack Networking network resource with the following three additional attributes:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:139(caption)
msgid "Provider Network Attributes"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:154(td)
msgid "provider:network_type"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:157(td)
msgid "The physical mechanism by which the virtual network is realized. Possible values are \"flat\", \"vlan\", \"local\", and \"gre\", corresponding to flat networks, VLAN networks, local networks, and GRE networks as defined above. All types of provider networks can be created by administrators, while tenant networks can be realized as \"vlan\", \"gre\", or \"local\" network types depending on plugin configuration."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:170(td)
msgid "provider:physical_network"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:172(td)
msgid "If a physical network named \"default\" has been configured, and if provider:network_type is \"flat\" or \"vlan\", then \"default\" is used."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:176(td)
msgid "The name of the physical network over which the virtual network is realized for flat and VLAN networks. Not applicable to the \"local\" or \"gre\" network types."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:182(td)
msgid "provider:segmentation_id"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:183(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:610(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:616(td)
msgid "Integer"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:185(td)
msgid "For VLAN networks, the VLAN VID on the physical network that realizes the virtual network. Valid VLAN VIDs are 1 through 4094. For GRE networks, the tunnel ID. Valid tunnel IDs are any 32 bit unsigned integer. Not applicable to the \"flat\" or \"local\" network types."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:195(para)
msgid "The provider attributes are returned by OpenStack Networking API operations when the client is authorized for the <code>extension:provider_network:view</code> action via the OpenStack Networking policy configuration. The provider attributes are only accepted for network API operations if the client is authorized for the <code>extension:provider_network:set</code> action. The default OpenStack Networking API policy configuration authorizes both actions for users with the admin role. See <xref linkend=\"ch_auth\"/> for details on policy configuration."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:210(title)
msgid "Provider API Workflow"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:211(para)
msgid "Show all attributes of a network, including provider attributes when invoked with the admin role:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:216(para)
msgid "Create a local provider network (admin-only):"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:220(para)
msgid "Create a flat provider network (admin-only):"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:224(para)
msgid "Create a VLAN provider network (admin-only):"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:228(para)
msgid "Create a GRE provider network (admin-only):"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:232(para)
msgid "When creating flat networks or VLAN networks, &lt;phys-net-name&gt; must be known to the plugin. See <xref linkend=\"ovs_quantum_plugin\"/> and <xref linkend=\"linuxbridge_conf\"/> for details on configuring network_vlan_ranges to identify all physical networks. When creating VLAN networks, &lt;VID&gt; can fall either within or outside any configured ranges of VLAN IDs from which tenant networks are allocated. Similarly, when creating GRE networks, &lt;tunnel-id&gt; can fall either within or outside any tunnel ID ranges from which tenant networks are allocated."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:244(para)
msgid "Once provider networks have been created, subnets can be allocated and they can be used similarly to other virtual networks, subject to authorization policy based on the specified &lt;tenant_id&gt;."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:252(title)
msgid "L3 Routing and NAT"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:253(para)
msgid "Just like the core OpenStack Networking API provides abstract L2 network segments that are decopuled from the technology used to implement the L2 network, OpenStack Networking includes an API extension that provides abstract L3 routers that API users can dynamically provision and configure. These OpenStack Networking routers can connect multiple L2 OpenStack Networking networks, and can also provide a \"gateway\" that connects one or more private L2 networks to a shared \"external\" network (e.g., a public network for access to the Internet). See <xref linkend=\"use_cases_single_router\"/> and <xref linkend=\"use_cases_tenant_router\"/> for details on common models of deploying OpenStack Networking L3 routers."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:267(para)
msgid "The L3 router provides basic NAT capabilities on \"gateway\" ports that uplink the router to external networks. This router SNATs all traffic by default, and supports \"Floating IPs\", which creates a static one-to-one mapping from a public IP on the external network to a private IP on one of the other subnets attached to the router. This allows a tenant to selectively expose VMs on private networks to other hosts on the external network (and often to all hosts on the Internet). Floating IPs can be allocated and then mapped from one OpenStack Networking port to another, as needed."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:279(title)
msgid "L3 API Abstractions"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:299(td)
msgid "UUID for the router."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:305(td)
msgid "Human-readable name for the router. Might not be unique."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:312(td)
msgid "The administrative state of router. If false (down), the router does not forward packets."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:320(para)
msgid "Indicates whether router is currently operational."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:327(td)
msgid "Owner of the router. Only admin users can specify a tenant_id other than its own."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:332(td)
msgid "external_gateway_info"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:333(td)
msgid "dict contain 'network_id' key-value pair"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:334(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:388(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:396(td)
msgid "Null"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:335(td)
msgid "External network that this router connects to for gateway services (e.g., NAT)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:341(caption)
msgid "Floating IP"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:359(td)
msgid "UUID for the floating IP."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:362(td)
msgid "floating_ip_address"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:363(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:395(td)
msgid "string (IP address)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:364(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:592(td)
msgid "allocated by OpenStack Networking"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:365(td)
msgid "The external network IP address available to be mapped to an internal IP address."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:369(td)
msgid "floating_network_id"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:372(para)
msgid "The network indicating the set of subnets from which the floating IP should be allocated"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:377(td)
msgid "router_id"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:380(td)
msgid "Read-only value indicating the router that connects the external network to the associated internal port, if a port is associated."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:386(td)
msgid "port_id"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:389(td)
msgid "Indicates the internal OpenStack Networking port associated with the external floating IP."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:394(td)
msgid "fixed_ip_address"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:397(td)
msgid "Indicates the IP address on the internal port that is mapped to by the floating IP (since an OpenStack Networking port might have more than one IP address)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:406(td)
msgid "Owner of the Floating IP. Only admin users can specify a tenant_id other than its own."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:415(title)
msgid "Common L3 Workflow"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:416(para)
msgid "Create external networks (admin-only)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:419(para)
msgid "Viewing external networks:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:421(para)
msgid "Creating routers"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:422(para)
msgid "Internal-only router to connect multiple L2 networks privately. "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:431(para)
msgid "The router will get an interface with the gateway_ip address of the subnet, and this interface will be attached to a port on the L2 OpenStack Networking network associated with the subnet. The router will also get an gateway interface to the specified external network.  This will provide SNAT connectivity to the external network as well as support for floating IPs allocated on that external networks (see below).  Commonly an external network maps to a network in the provider"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:441(para)
msgid "A router can also be connected to an “external network”, allowing that router to act as a NAT gateway for external connectivity. "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:445(para)
msgid "Viewing routers:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:446(para)
msgid "List all routers: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:448(para)
msgid "Show a specific router: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:450(para)
msgid "Show all internal interfaces for a router: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:452(para)
msgid "Associating / Disassociating Floating IPs:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:453(para)
msgid "First, identify the port-id representing the VM NIC that the floating IP should map to:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:456(para)
msgid "This port must be on an OpenStack Networking subnet that is attached to a router uplinked to the external network that will be used to create the floating IP.  Conceptually, this is because the router must be able to perform the Destination NAT (DNAT) rewriting of packets from the Floating IP address (chosen from a subnet on the external network) to the internal Fixed IP (chosen from a private subnet that is “behind” the router). "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:465(para)
msgid "Create floating IP unassociated, then associate"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:469(para)
msgid "create floating IP and associate in a single step"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:472(para)
msgid "Viewing Floating IP State:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:474(para)
msgid "Find floating IP for a particular VM port:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:476(para)
msgid "Disassociate a Floating IP:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:478(para)
msgid "L3 Tear Down"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:479(para)
msgid "Delete the Floating IP:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:481(para)
msgid "Then clear the any gateway:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:483(para)
msgid "Then remove the interfaces from the router (deleting the network and subnet will do this as well):"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:486(para)
msgid "Finally, delete the router:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:491(title)
msgid "Security Groups"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:492(para)
msgid "Security groups and security group rules allows administrators and tenants the ability to specify the type of traffic and direction (ingress/egress) that is allowed to pass through a port. A security group is a container for security group rules."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:496(para)
msgid "When a port is created in OpenStack Networking it is associated with a security group. If a security group is not specified the port will be associated with a 'default' security group. By default this group will drop all ingress traffic and allow all egress. Rules can be added to this group in order to change the behaviour."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:502(para)
msgid "If one desires to use the OpenStack Compute security group APIs and/or have OpenStack Compute orchestrate the creation of new ports for instances on specific security groups, additional configuration is needed. To enable this, one must configure the following file <filename>/etc/nova/nova.conf</filename> and set the config option security_group_api=quantum on every node running nova-compute and nova-api. After this change is made restart nova-api and nova-compute in order to pick up this change. After this change is made one will be able to use both the OpenStack Compute and OpenStack Network security group API at the sametime."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:512(para)
msgid "In order to use the OpenStack Compute security group API with OpenStack Networking the OpenStack Networking plugin must implement the security group api. The following plugins currently implement this: Nicira NVP, Open vSwitch, Linux Bridge, NEC, and Ryu."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:516(para)
msgid "When using the security group API through OpenStack Compute, security groups are applied to all ports on an instance. The reason for this is that OpenStack Compute security group APIs are instances based and not port based as OpenStack Networking."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:521(title)
msgid "Security Group API Abstractions"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:523(caption)
msgid "Security Group Attributes"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:541(td)
msgid "UUID for the security group."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:547(td)
msgid "Human-readable name for the security group. Might not be unique. Cannot be named default as that is automatically created for a tenant."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:552(td)
msgid "description"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:555(td)
msgid "Human-readable description of a security group."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:562(td)
msgid "Owner of the security group. Only admin users can specify a tenant_id other than their own."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:569(caption)
msgid "Security Group Rules"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:587(td)
msgid "UUID for the security group rule."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:590(td)
msgid "security_group_id"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:591(td) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:634(td)
msgid "uuid-str or Integer"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:593(td)
msgid "The security group to associate rule with."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:596(td)
msgid "direction"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:599(td)
msgid "The direction the traffic is allow (ingress/egress) from a VM."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:603(td)
msgid "protocol"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:606(td)
msgid "IP Protocol (icmp, tcp, udp, etc)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:609(td)
msgid "port_range_min"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:612(td)
msgid "Port at start of range"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:615(td)
msgid "port_range_max"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:618(td)
msgid "Port at end of range"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:621(td)
msgid "ethertype"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:624(td)
msgid "ethertype in L2 packet (IPv4, IPv6, etc)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:627(td)
msgid "source_ip_prefix"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:628(td)
msgid "string (IP cidr)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:630(td)
msgid "CIDR for address range"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:633(td)
msgid "source_group_id"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:635(td)
msgid "allocated by OpenStack Networking or OpenStack Compute"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:637(td)
msgid "Source security group to apply to rule."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:643(td)
msgid "Owner of the security group rule. Only admin users can specify a tenant_id other than its own."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:652(title)
msgid "Common Security Group Commands"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:653(para)
msgid "Create a security group for our web servers:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:656(para)
msgid "Viewing security groups:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:658(para)
msgid "Creating security group rule to allow port 80 ingress:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:662(para)
msgid "List security group rules:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:664(para)
msgid "Delete a security group rule:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:666(para)
msgid "Delete security group:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:668(para)
msgid "Create a port associated with security group:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml:670(para)
msgid "Remove security groups from a port:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:6(title)
msgid "Core Configuration File Options"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:8(title)
msgid "quantum.conf"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:9(para)
msgid "The configuration settings for the OpenStack Networking services are found in <filename>/etc/quantum/quantum.conf</filename>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:11(caption)
msgid "Debugging Options"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:14(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:35(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:90(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:148(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:235(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:287(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:355(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:434(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:475(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:529(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:576(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:684(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:746(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:919(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:959(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1021(th)
msgid "Configuration option=Default value"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:15(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:36(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:91(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:149(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:236(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:288(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:356(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:435(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:476(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:530(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:577(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:685(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:747(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:920(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:960(th) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1022(th)
msgid "(Type) Description"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:21(td)
msgid "debug=False"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:22(td)
msgid "(BoolOpt) Print debugging output"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:25(td)
msgid "verbose=False"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:26(td)
msgid "(BoolOpt) Print more verbose output"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:32(caption)
msgid "Logging Options"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:41(td)
msgid "log_config="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:42(td)
msgid "(StrOpt) If this option is specified, the logging configuration file specified is used and overrides any other logging options specified. Please see the Python logging module documentation for details on logging configuration files. Print debugging output"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:51(td)
msgid "log_format=%(asctime)s %(levelname)8s [%(name)s] %(message)s"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:53(td)
msgid "(StrOpt) A logging.Formatter log message format string which may use any of the available logging.LogRecord attributes."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:59(td)
msgid "log_date_format=%Y-%m-%d %H:%M:%S"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:60(td)
msgid "(StrOpt) Format string for %(asctime)s in log records."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:64(td)
msgid "log_file="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:65(td)
msgid "(StrOpt) (Optional) Name of log file to output to.  If not set, logging will go to stdout."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:70(td)
msgid "log_dir="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:71(td)
msgid "(StrOpt) (Optional) The directory to keep log files in (will be prepended to --logfile)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:76(td)
msgid "use_syslog=False"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:77(td)
msgid "(BoolOpt) Use syslog for logging."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:80(td)
msgid "syslog_log_facility=LOG_USER"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:81(td)
msgid "(StrOpt) syslog facility to receive log lines"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:87(caption)
msgid "Service Options"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:96(td)
msgid "bind_host=0.0.0.0"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:97(td)
msgid "(StrOpt) Server listening IP."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:100(td)
msgid "bind_port=9696"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:101(td)
msgid "(IntOpt) Server listening port."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:104(td)
msgid "api_paste_config=api-paste.ini"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:105(td)
msgid "(StrOpt) The paste configuration file. This is used to configure the WSGI application."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:110(td)
msgid "api_extensions_path="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:111(td)
msgid "(StrOpt) Enables custom addition to be made to the above configuration."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:115(td)
msgid "policy_file=policy.json"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:116(td)
msgid "(StrOpt) JSON file representing policies to access and view data. The usage and format is discussed in more detail in the Authentication and Authorization section."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:123(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1046(td)
msgid "auth_strategy=keystone"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:124(td)
msgid "(StrOpt) The strategy used for authentication. The supported values are keystone and noauth."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:129(td)
msgid "core_plugin=quantum.plugins.sample.SamplePlugin.FakePlugin"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:131(td)
msgid "(StrOpt) The plugin to be loaded by the service."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:135(td)
msgid "pagination_max_limit=-1"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:137(td)
msgid "(StrOpt) The maximum number of items returned in a single response. A value of 'infinite', or a negative integer means no limit."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:145(caption)
msgid "Base Plugin Options"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:154(td)
msgid "base_mac=fa:16:3e:00:00:00"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:155(td)
msgid "(StrOpt) MAC addresses for a port are generated. The first 3 octets will remain unchanged. If the 4h octet is not 00, it will also used. The others will be randomly generated."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:162(td)
msgid "mac_generation_retries=16"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:163(td)
msgid "(IntOpt) The number of times the plugin attempts to generate a unique MAC address."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:168(td)
msgid "allow_bulk=True"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:169(td)
msgid "(BoolOpt) Enable or disable bulk create/update/delete operations."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:173(td)
msgid "allow_pagination=False"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:174(para)
msgid "(BoolOpt) Enable or disable pagination. If plugin doesn't support native pagination, it will enable emulated pagination. Please note native pagination depends on native sorting. If native pagination is enabled, native emulated sorting will be enabled automatically."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:181(para)
msgid "If the plugin supports native pagination, the plugin will returns the maximum limit of items as request. If the plugin didn't support that, quantum API can emulate the pagination behavior. The performance of native pagination is better than emulated pagiantion."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:192(td)
msgid "allow_sorting=False"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:193(para)
msgid "(BoolOpt) Enable or disable sorting. If plugin doesn't support native sorting, it will enable emulated sorting."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:197(para)
msgid "If the plugin supports native sorting, the plugin will returns ordered items as request. If the plugin didn't support that, quantum API can emulate the sorting behavior. The performance of native sorting is better than emulated sorting."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:207(td)
msgid "max_dns_nameservers=5"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:208(td)
msgid "(IntOpt) The maximum amount of DNS nameservers that can be configured per subnet."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:213(td)
msgid "max_subnet_host_routes=20"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:214(td)
msgid "(IntOpt) The maximum amount of host routes that can be configured per subnet."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:218(td)
msgid "state_path=."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:219(td)
msgid "(StrOpt) Top level directory for configuration files."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:223(td)
msgid "dhcp_lease_duration=120"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:224(td)
msgid "(IntOpt) The default expiration time for a DHCP address. This is in seconds."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:232(caption)
msgid "Common RPC Message Options"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:241(td)
msgid "control_exchange=quantum"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:242(td)
msgid "(StrOpt) AMQP exchange to connect to if using RabbitMQ or QPID"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:246(td)
msgid "rpc_back_end=quantum.openstack.common.rpc.impl_kombu"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:248(td)
msgid "(StrOpt) The messaging module to use, defaults to kombu. For qpid, make use of quantum.openstack.common.rpc.impl_qpid"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:254(td)
msgid "rpc_thread_pool_size=64"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:255(td)
msgid "(IntOpt) Size of RPC thread pool."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:258(td)
msgid "rpc_conn_pool_size=30"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:259(td)
msgid "(IntOpt) Size of RPC connection pool."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:263(td)
msgid "rpc_response_timeout=60"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:264(td)
msgid "(IntOpt) Seconds to wait for a response from call or multicall"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:268(td)
msgid "allowed_rpc_exception_modules='quantum.openstack.common.exception', 'nova.exception'"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:271(td)
msgid "(ListOpt) Modules of exceptions that are permitted to be recreated upon receiving exception data from an rpc call."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:276(td)
msgid "fake_rabbit=False"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:277(td)
msgid "(BoolOpt) If passed, use a fake RabbitMQ provider"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:284(caption)
msgid "Rabbit RPC Options"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:293(td)
msgid "kombu_ssl_version="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:294(td)
msgid "(StrOpt) SSL version to use (valid only if SSL enabled)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:298(td)
msgid "kombu_ssl_keyfile="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:299(td)
msgid "(StrOpt) SSL key file (valid only if SSL enabled)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:303(td)
msgid "kombu_ssl_certfile="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:304(td)
msgid "(StrOpt) SSL cert file (valid only if SSL enabled)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:308(td)
msgid "kombu_ssl_ca_certs="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:309(td)
msgid "(StrOpt) SSL certification authority file (valid only if SSL enabled)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:313(td)
msgid "rabbit_host=localhost"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:314(td)
msgid "(StrOpt) IP address of the RabbitMQ installation"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:318(td)
msgid "rabbit_password=guest"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:319(td)
msgid "            Password of the RabbitMQ server"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:323(td)
msgid "rabbit_port=5672"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:324(td)
msgid "(IntOpt) Port where RabbitMQ server is running/listening"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:328(td)
msgid "rabbit_userid=guest"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:329(td)
msgid "(StrOpt) User ID used for RabbitMQ connections"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:333(td)
msgid "rabbit_virtual_host=/"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:334(td)
msgid "(StrOpt) Location of a virtual RabbitMQ installation."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:338(td)
msgid "rabbit_max_retries=0"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:339(td)
msgid "(IntOpt) Maximum retries with trying to connect to RabbitMQ. The default of 0 implies an infinite retry count"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:344(td)
msgid "rabbit_retry_interval=1"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:345(td)
msgid "(IntOpt) RabbitMQ connection retry interval"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:352(caption)
msgid "QPID RPC Options"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:361(td)
msgid "qpid_hostname=localhost"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:362(td)
msgid "(StrOpt) Qpid broker hostname"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:365(td)
msgid "qpid_port=5672"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:366(td)
msgid "(IntOpt) Qpid broker port"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:369(td)
msgid "qpid_username="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:370(td)
msgid "(StrOpt) Username for qpid connection"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:374(td)
msgid "qpid_password="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:375(td)
msgid "(StrOpt) Password for qpid connection"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:379(td)
msgid "qpid_sasl_mechanisms="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:380(td)
msgid "(StrOpt) Space separated list of SASL mechanisms to use for auth"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:384(td)
msgid "qpid_reconnect=True"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:385(td)
msgid "(BoolOpt) Automatically reconnect"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:388(td)
msgid "qpid_reconnect_timeout=0"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:389(td)
msgid "(IntOpt) The number of seconds to wait before deciding that a reconnect attempt has failed"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:394(td)
msgid "qpid_reconnect_limit=0"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:395(td)
msgid "(IntOpt) The limit for the number of times to reconnect before considering the connection to be failed."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:400(td)
msgid "qpid_reconnect_interval_min=0"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:401(td)
msgid "(IntOpt) Minimum seconds between reconnection attempts"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:405(td)
msgid "qpid_reconnect_interval_max=0"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:406(td)
msgid "(IntOpt) Maximum seconds between reconnection attempts"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:410(td)
msgid "qpid_reconnect_interval=0"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:411(td)
msgid "(IntOpt) Equivalent to setting max and min to the same value"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:415(td)
msgid "qpid_heartbeat=60"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:416(td)
msgid "(IntOpt) Seconds between connection keepalive heartbeats"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:420(td)
msgid "qpid_protocol=tcp"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:421(td)
msgid "(StrOpt) Transport to use, either 'tcp' or 'ssl'"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:425(td)
msgid "qpid_tcp_nodelay=True"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:426(td)
msgid "(BoolOpt) Disable Nagle algorithm"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:440(td)
msgid "notification_driver=quantum.openstack.common.notifier.list_notifier"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:442(td)
msgid "(MultiStrOpt) Driver or drivers to handle sending notifications. The default is set as notifier as the DHCP agent makes use of the notifications."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:448(td)
msgid "default_notification_level=INFO"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:449(td)
msgid "(StrOpt) Default notification level for outgoing notifications"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:453(td)
msgid "default_publisher_id=$host"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:454(td)
msgid "(StrOpt) Default publisher_id for outgoing notifications"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:458(td)
msgid "list_notifier_drivers='quantum.openstack.common.notifier.no_op_notifier'"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:460(td)
msgid "(MultiStrOpt) List of drivers to send notifications"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:464(td)
msgid "notification_topics='notifications'"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:465(td)
msgid "(ListOpt) AMQP topic used for openstack notifications"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:472(caption)
msgid "Quota Options"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:481(td)
msgid "quota_driver=quantum.quota.ConfDriver"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:482(td)
msgid "(StrOpt) Default driver to use for quota checks. If the default driver is used then the configuration values below are in effect. To limit quotas per tenant then use: quantum.db.quota_db.DbQuotaDriver"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:491(td)
msgid "quota_items=network,subnet,port"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:492(td)
msgid "(ListOpt) Resource names that are supported by the Quotas feature."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:496(td)
msgid "default_quota=-1"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:497(td)
msgid "(IntOpt) Default number of resources allowed per tenant, minus for unlimited"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:502(td)
msgid "quota_network=10"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:503(td)
msgid "(IntOpt) Number of networks allowed per tenant, and minus means unlimited"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:507(td)
msgid "quota_subnet=10"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:508(td)
msgid "(IntOpt) Number of subnets allowed per tenant, and minus means unlimited"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:512(td)
msgid "quota_port=50"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:513(td)
msgid "(IntOpt) Number of ports allowed per tenant, and minus means unlimited"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:520(title)
msgid "ovs_quantum_plugin.ini:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:521(para)
msgid "For information about the Open vSwitch plugin configurations, see <link href=\"http://wiki.openstack.org/ConfigureOpenvswitch\">http://wiki.openstack.org/ConfigureOpenvswitch</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:526(caption) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:681(caption)
msgid "Database Access by Plugin"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:535(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:690(td)
msgid "sql_connection=sqlite://"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:536(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:691(para)
msgid "(StrOpt) The details of the database connection. For example mysql://root:nova@127.0.0.1:3306/ovs_quantum. Replace 127.0.0.1 above with the IP address of the database used by the main OpenStack Networking server. (Leave it as is if the database runs on this host.)."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:545(para) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:700(para)
msgid "This line must be changed to ensure that the database values are persistent. The sqlite is used for testing."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:552(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:707(td)
msgid "sql_max_retries=10"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:553(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:708(td)
msgid "(IntOpt) Database re-connection retry times. This is in the event connectivity is lost with the database. -1 implies an infinite retry count."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:559(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:714(td)
msgid "reconnect_interval=2"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:560(td) ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:715(td)
msgid "(IntOpt) Database reconnection interval in seconds - in event connectivity is lost."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:566(para)
msgid "<emphasis role=\"bold\">OVS Options</emphasis> (This is in the section ovs)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:568(para)
msgid "This section deals with the specific OVS options common to the plugin and agent."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:572(caption)
msgid "OVS Options Common to Plugin and Agent"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:582(td)
msgid "network_vlan_ranges=default:2000:3999"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:583(td)
msgid "(ListOpt) Comma-separated list of  &lt;physical_network&gt;:&lt;vlan_min&gt;:&lt;vlan_max&gt; tuples enumerating ranges of VLAN IDs on named physical networks that are available for allocation."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:590(td)
msgid "tunnel_id_ranges="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:591(td)
msgid "(ListOpt) Comma-separated list of &lt;tun_min&gt;:&lt;tun_max&gt; tuples enumerating ranges of GRE tunnel IDs that are available for allocation."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:597(td)
msgid "integration_bridge=br-int"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:598(td)
msgid "(StrOpt) This is the name of the OVS integration bridge. There is one per hypervisor. The integration bridge acts as a virtual \"patch port\". All VM VIFs are attached to this bridge and then \"patched\" according to their network connectivity. Do not change this parameter unless you have a good reason to."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:608(td)
msgid "tunnel_bridge=br-tun"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:609(td)
msgid "(StrOpt) Specifies the name of the OVS tunnel bridge used by the agent for GRE tunnels. Only used if tunnel_id_ranges is not empty."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:615(td)
msgid "bridge_mappings=default:br-eth1"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:616(td)
msgid "(ListOpt) Comma-separated list of &lt;physical_network&gt;:&lt;bridge&gt; tuples mapping physical network names to agent's node-specific OVS bridge names. Each bridge must exist, and should have physical network # interface configured as a port."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:625(td)
msgid "local_ip=10.0.0.3"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:626(td)
msgid "(StrOpt) Set local-ip to be the local IP address of this hypervisor. This is used only when tunnel_id_ranges are used."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:631(td)
msgid "enable_tunneling=False"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:632(td)
msgid "(BoolOpt) A flag indicating if tunneling is supported. Not all systems that support Open vSwitch support its GRE tunneling feature, that is, it is not supported in the Linux kernel source tree. This applies to both the server and agent"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:641(para)
msgid "(This is in the section agent)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:642(para)
msgid "<table rules=\"all\"><caption>Agent Options</caption><thead><tr><th>Configuration option=Default value</th><th>(Type) Description</th></tr></thead><tbody><tr><td>rpc=True </td><td>(BoolOpt) If this is True then the agent will communicate with the plugin via the OpenStack RPC (configured in quantum.conf). If this is False then the agent will poll the database for changes. In the event that this is False then please update the relevant database settings on the agent so that it is able to access the database. </td></tr><tr><td>polling_interval=2 </td><td>(IntOpt) Agent's polling interval in seconds. </td></tr><tr><td>root_helper=sudo </td><td>(StrOpt) This enables limiting commands that can be run. Please refer to rootwrap section for more details. </td></tr></tbody></table>    "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:679(title)
msgid "linuxbridge_conf.ini:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:722(para)
msgid "  <table rules=\"all\"><caption>VLAN Configurations</caption><thead><tr><th>Configuration option=Default value</th><th>(Type) Description</th></tr></thead><tbody><tr><td>network_vlan_ranges=default:1000:2999 </td><td>(ListOpt) Comma-separated list of &lt;physical_network&gt;:&lt;vlan_min&gt;:&lt;vlan_max&gt; tuples enumerating ranges of VLAN IDs on named physical networks that are available for allocation. </td></tr></tbody></table>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:743(caption)
msgid "Networking Options on the Agent"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:752(td)
msgid "physical_interface_mappings=default:eth1"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:753(td)
msgid "(ListOpt) Comma-separated list of &lt;physical_network&gt;:&lt;physical_interface&gt; tuples mapping physical network names to agent's node-specific physical network interfaces. Server uses physical network names for validation but ignores interfaces."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:763(para)
msgid "<table rules=\"all\"><caption>Agent Options</caption><thead><tr><th>Configuration option=Default value</th><th>(Type) Description</th></tr></thead><tbody><tr><td>rpc=True </td><td>(BoolOpt) If this is True then the agent will communicate with the plugin via the OpenStack RPC (configured in quantum.conf). If this is False then the agent will poll the database for changes. In the event that this is False then please update the relevant database settings on the agent so that it is able to access the database. </td></tr><tr><td>polling_interval=2 </td><td>(IntOpt) Agent's polling interval in seconds. </td></tr><tr><td>root_helper=sudo </td><td>(StrOpt) This enables limiting commands that can be run. Please refer to rootwrap section for more details. </td></tr></tbody></table>  "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:800(title)
msgid "dhcp_agent.ini"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:801(para)
msgid "<table rules=\"all\"><caption>DHCP Specific Options</caption><thead><tr><th>Configuration option=Default value</th><th>(Type) Description</th></tr></thead><tbody><tr><td>root_helper=sudo </td><td>(StrOpt) This enables limiting commands that can be run. Please refer to rootwrap section for more details. </td></tr><tr><td>dhcp_driver=quantum.agent.linux.dhcp.Dnsmasq </td><td>(StrOpt) The driver used to manage the DHCP server. </td></tr><tr><td>use_namespaces=True </td><td>(BoolOpt) Allow overlapping IP. (Note: If running multiple agents with different IP addresses on the same host this should be \"True\" if not you will get routing problems.)</td></tr></tbody></table>  "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:831(para)
msgid "<table rules=\"all\"><caption>Device Manager Options</caption><thead><tr><th>Configuration option=Default value</th><th>(Type) Description</th></tr></thead><tbody><tr><td>admin_user= </td><td>(StrOpt) Name of the admin user for OpenStack Networking, which is defined in <link href=\"keystone.html\">OpenStack Identity</link> (keystone) </td></tr><tr><td>admin_password= </td><td>(StrOpt) The users password </td></tr><tr><td>admin_tenant_name= </td><td>(StrOpt) The admin tenant name </td></tr><tr><td>auth_url= </td><td>(StrOpt) The URL used to validate tokens. `auth_protocol`://`auth_host`:`auth_port`/v2.0 </td></tr><tr><td>auth_strategy=keystone </td><td>(StrOpt) The strategy to use for authentication. Supports noauth or keystone. </td></tr><tr><td>auth_region= </td><td>(StrOpt) The authentication region </td></tr><tr><td>interface_driver= </td><td>(StrOpt) The driver used to manage the virtual interface. </td></tr><tr><td> dhcp_lease_relay_socket=$state_path/dhcp/lease_relay </td><td>(StrOpt) Location to DHCP lease relay UNIX domain socket </td></tr><tr><td>ovs_integration_bridge=br-int </td><td>(StrOpt) Name of Open vSwitch bridge to use. Only relevant if using Open vSwitch. </td></tr><tr><td>network_device_mtu= </td><td>(StrOpt) MTU setting for device. Only relevant if using Open vSwitch. </td></tr><tr><td>ryu_api_host=127.0.0.1:8080 </td><td>(StrOpt) OpenFlow Ryu REST API host:port. Only relevant if using Ryu. </td></tr><tr><td>meta_flavor_driver_mappings= </td><td>(StrOpt). Mappings between flavors and drivers. Only relevant if using MetaPlugin. </td></tr><tr><td>resync_interval=30 </td><td>(IntOpt) If there is an exception on the quantum-server service, then the DHCP agent will ensure that it syncs with the quantum.conf configuration. The validation about syncing is done every resync_interval seconds. </td></tr></tbody></table>    "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:916(caption)
msgid "dnsmasq Options"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:925(td)
msgid "dhcp_confs=$state_path/dhcp"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:926(td)
msgid "(StrOpt) Location to store DHCP server config files"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:930(td)
msgid "dhcp_lease_time=120"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:931(td)
msgid "(IntOpt) Lifetime of a DHCP lease in seconds"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:935(td)
msgid "dhcp_domain=openstacklocal"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:936(td)
msgid "(StrOpt) Domain to use for building the hostnames"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:940(td)
msgid "dnsmasq_config_file="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:941(td)
msgid "(StrOpt) Override the default dnsmasq settings with this file"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:945(td)
msgid "dnsmasq_dns_server="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:946(td)
msgid "(StrOpt) Use another DNS server before any in /etc/resolv.conf."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:953(title)
msgid "l3_agent.ini"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:956(caption)
msgid "L3 Specific Options"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:965(td)
msgid "root_helper=sudo"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:966(td)
msgid "(StrOpt) This enables limiting commands that can be run. Please refer to rootwrap section for more details."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:971(td)
msgid "external_network_bridge=br-ex"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:972(td)
msgid "(StrOpt) Name of bridge used for external network traffic."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:976(td)
msgid "use_namespaces=True"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:977(td)
msgid "(BoolOpt) Allow overlapping IP. (Note: If running multiple agents with different IP addresses on the same host this should be \"True\" if not you will get routing problems.)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:984(td)
msgid "polling_interval=3"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:985(td)
msgid "(IntOpt) The time in seconds between state poll requests."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:989(td)
msgid "metadata_ip="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:990(td)
msgid "(StrOpt) IP address used by OpenStack Compute metadata server."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:994(td)
msgid "metadata_port=8775"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:995(td)
msgid "(IntOpt) TCP Port used by OpenStack Compute metadata server."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:999(td)
msgid "router_id="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1000(td)
msgid "(StrOpt) If namespaces is disabled, the l3 agent can only configure a router whose ID matches this parameter."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1005(td)
msgid "handle_internal_only_routers=True"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1006(td)
msgid "(BoolOpt) Agent should implement routers with no gateway."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1010(td)
msgid "gateway_external_network_id="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1011(td)
msgid "(StrOpt) UUID of external network for routers implemented by the agents."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1018(caption)
msgid "Device Manager Options"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1027(td)
msgid "admin_user="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1029(link)
msgid "OpenStack Identity"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1028(td)
msgid "(StrOpt) Name of the admin user for OpenStack Networking, which is defined in <placeholder-1/> (keystone)"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1032(td)
msgid "admin_password="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1033(td)
msgid "(StrOpt) The users password"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1036(td)
msgid "admin_tenant_name="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1037(td)
msgid "(StrOpt) The admin tenant name"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1040(td)
msgid "auth_url="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1041(td)
msgid "(StrOpt) The URL used to validate tokens. `auth_protocol`://`auth_host`:`auth_port`/v2.0"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1047(td)
msgid "(StrOpt) The strategy to use for authentication. Supports noauth or keystone."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1052(td)
msgid "auth_region="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1053(td)
msgid "(StrOpt) The authentication region"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1056(td)
msgid "interface_driver="
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml:1057(td)
msgid "(StrOpt) The driver used to manage the virtual interface."
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:347(None) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:350(None)
msgid "@@image: 'figures/UseCase-SingleFlat.png'; md5=bdd61f2967fb1a55e4f50d766db7b113"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:364(None) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:367(None)
msgid "@@image: 'figures/UseCase-MultiFlat.png'; md5=289e38a7a13a2a4413e5a1e62ce55b3e"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:388(None) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:391(None)
msgid "@@image: 'figures/UseCase-MixedFlatPrivate.png'; md5=8da4ceb5a1e5a2357394478645af7449"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:424(None) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:427(None)
msgid "@@image: 'figures/UseCase-SingleRouter.png'; md5=63d21d52d32ed7fa1c1dad1a1fd88eb5"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:6(title) ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:174(title)
msgid "Overview"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:7(para)
msgid "This chapter describes the high-level concepts and components of an OpenStack Networking deployment."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:10(title)
msgid "What is OpenStack Networking?"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:11(para)
msgid "The OpenStack Networking project was created to provide a rich tenant-facing API for defining network connectivity and addressing in the cloud. The OpenStack Networking project gives operators the ability to leverage different networking technologies to power their cloud networking.  "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:16(para)
msgid "For a detailed description of the OpenStack Networking API abstractions and their attributes, see the <link href=\"http://docs.openstack.org/api/openstack-network/2.0/content/\"><citetitle>OpenStack Networking API Guide (v2.0)</citetitle></link>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:26(title)
msgid "A Rich Network API"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:27(para)
msgid "OpenStack Networking is a virtual network service that provides a powerful API to define the network connectivity and addressing used by devices from other services, such as OpenStack Compute.  "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:37(para)
msgid "<emphasis role=\"bold\">Network</emphasis>. An isolated L2 segment, analogous to VLAN in the physical networking world."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:43(para)
msgid "<emphasis role=\"bold\">Subnet</emphasis>. A block of v4 or v6 IP addresses and associated configuration state."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:48(para)
msgid "<emphasis role=\"bold\">Port</emphasis>. A connection point for attaching a single device, such as the NIC of a virtual server, to a virtual network. Also describes the associated network configuration, such as the MAC and IP addresses to be used on that port.  "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:31(para)
msgid "The OpenStack Compute API has a virtual server abstraction to describe compute resources. Similarly, the OpenStack Networking API has virtual  network, subnet, and port abstractions to describe network resources. In more detail: <placeholder-1/>You can configure rich network topologies by creating and configuring networks and subnets, and then instructing other OpenStack services like OpenStack Compute to attach virtual devices to ports on these networks.  In particular, OpenStack Networking supports each tenant having multiple private networks, and allows tenants to choose their own IP addressing scheme, even if those IP addresses overlap with those used by other tenants.  This enables very advanced cloud networking use cases, such as building multi-tiered web applications and allowing applications to be migrated to the cloud without changing IP addresses."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:69(para)
msgid "Even if a cloud administrator does not intend to expose these capabilities to tenants directly, the OpenStack Networking API can be very useful even when used as an admin API because it provides significantly more flexibility for the cloud administrator to customize network offerings.  "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:75(para)
msgid "The OpenStack Networking API also provides a mechanism that lets cloud administrators expose additional API capabilities through API extensions.  Commonly, new capabilities are first introduced as an API extension, and over time become part of the core OpenStack Networking API."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:84(title)
msgid "Flexibility to Choose Different Network Technologies"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:86(para)
msgid "Enhancing traditional networking solutions to provide rich cloud networking is challenging. Traditional networking is not designed to scale to cloud proportions or to configure automatically."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:90(para)
msgid "The original OpenStack Compute network implementation assumed a very basic model of performing all isolation through Linux VLANs and IP tables. OpenStack Networking introduces the concept of a <emphasis role=\"italic\">plugin</emphasis>, which is a pluggable back-end implementation of the OpenStack Networking API. A plugin can use a variety of technologies to implement the logical API requests.  Some OpenStack Networking plugins might use basic Linux VLANs and IP tables, while others might use more advanced technologies, such as L2-in-L3 tunneling or OpenFlow, to provide similar benefits."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:103(para)
msgid "<emphasis role=\"bold\">Open vSwitch</emphasis>. <link href=\"http://www.openvswitch.org/openstack/documentation\">http://www.openvswitch.org/openstack/documentation</link>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:110(para)
msgid "<emphasis role=\"bold\">Cisco</emphasis>. <link href=\"quantum/plugins/cisco/README\">quantum/plugins/cisco/README</link> and <link href=\"http://wiki.openstack.org/cisco-quantum\">http://wiki.openstack.org/cisco-quantum</link>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:120(para)
msgid "<emphasis role=\"bold\">Linux Bridge</emphasis>. <link href=\"quantum/plugins/linuxbridge/README\">quantum/plugins/linuxbridge/README</link> and <link href=\"http://wiki.openstack.org/Quantum-Linux-Bridge-Plugin\">http://wiki.openstack.org/Quantum-Linux-Bridge-Plugin</link>  "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:130(para)
msgid "<emphasis role=\"bold\">Nicira NVP</emphasis>. <link href=\"quantum/plugins/nicira/nicira_nvp_plugin/README\">quantum/plugins/nicira/nicira_nvp_plugin/README</link> and <link href=\"http://www.nicira.com/support\">http://www.nicira.com/support</link>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:140(para)
msgid "<emphasis role=\"bold\">Ryu</emphasis>. <link href=\"quantum/plugins/ryu/README\">quantum/plugins/ryu/README</link> and <link href=\"http://www.osrg.net/ryu/using_with_openstack.html\">http://www.osrg.net/ryu/using_with_openstack.html</link>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:150(para)
msgid "<emphasis role=\"bold\">NEC OpenFlow</emphasis>. <link href=\"http://wiki.openstack.org/Quantum-NEC-OpenFlow-Plugin\">http://wiki.openstack.org/Quantum-NEC-OpenFlow-Plugin</link>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:157(para)
msgid "<emphasis role=\"bold\">Big Switch, Floodlight REST Proxy</emphasis>. <link href=\"http://www.openflowhub.org/display/floodlightcontroller/Quantum+REST+Proxy+Plugin\">http://www.openflowhub.org/display/floodlightcontroller/Quantum+REST+Proxy+Plugin</link>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:101(para)
msgid "The current set of plugins include: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:164(para)
msgid "Plugins enable the cloud administrator to weigh different options and decide which networking technology is right for the deployment."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:170(title)
msgid "OpenStack Networking Architecture"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:171(para)
msgid "This section describes the high-level components of an OpenStack Networking deployment."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:175(para)
msgid "Before you deploy OpenStack Networking, it is useful to understand the different components that make up the solution and how those components interact with each other and with other OpenStack services."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:179(para)
msgid "OpenStack Networking is a standalone service, just like other OpenStack services such as OpenStack Compute, OpenStack Image service, OpenStack Identity service, and the OpenStack Dashboard. Like those services, a deployment of OpenStack Networking often involves deploying several processes on a variety of hosts."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:186(para)
msgid "The main process of the OpenStack Networking server is <literal>quantum-server</literal>, which is a Python daemon that exposes the OpenStack Networking API and passes user requests to the configured OpenStack Networking plugin for additional processing. Typically, the plugin requires access to a database for persistent storage, similar to other OpenStack services."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:201(para)
msgid "<emphasis role=\"bold\">plugin agent</emphasis> (<literal>quantum-*-agent</literal>). Runs on each hypervisor to perform local vswitch configuration. Agent to be run depends on which plugin you are using, as some plugins do not require an agent."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:211(para)
msgid "<emphasis role=\"bold\">dhcp agent</emphasis> (<literal>quantum-dhcp-agent</literal>). Provides DHCP services to tenant networks. This agent is the same across all plugins."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:219(para)
msgid "<emphasis role=\"bold\">l3 agent</emphasis><literal>(quantum-l3-agent</literal>). Provides L3/NAT forwarding to provide external network access for VMs on tenant networks. This agent is the same across all plugins."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:193(para)
msgid "If your deployment uses a <emphasis role=\"italic\">controller host</emphasis> to run centralized OpenStack Compute components, you can deploy the OpenStack Networking server on that same host. However, OpenStack Networking is entirely standalone and can be deployed on its own server as well. OpenStack Networking also includes additional agents that might be required depending on your deployment: <placeholder-1/>"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:231(para)
msgid "Through RPC. For example, rabbitmq or qpid."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:235(para)
msgid "Through the standard OpenStack Networking API.   "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:228(para)
msgid "These agents interact with the main quantum-server process in the following ways: <placeholder-1/>OpenStack Networking relies on the OpenStack Identity Project (Keystone) for authentication and authorization of all API request.   "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:241(para)
msgid "OpenStack Compute interacts with OpenStack Networking through calls to its standard API.  As part of creating a VM, nova-compute communicates with the OpenStack Networking API to plug each virtual NIC on the VM into a particular network."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:245(para)
msgid "The OpenStack Dashboard (Horizon) has integration with the OpenStack Networking API, allowing administrators and tenant users, to create and manage network services through the Horizon GUI.  See the <citetitle>Horizon Administrator Guide</citetitle>."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:252(title)
msgid "Place Services on Physical Hosts"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:253(para)
msgid "Like other OpenStack services, OpenStack Networking provides cloud administrators with significant flexibility in deciding which individual services should run on which physical devices. On one extreme, all service daemons can be run on a single physical host for evaluation purposes. On the other, each service could have its own physical hosts, and some cases be replicated across multiple hosts for redundancy. See <link linkend=\"ch_high_avail\"/> "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:260(para)
msgid "In this guide, we focus primarily on a standard architecture that includes a “cloud controller” host, a “network gateway” host, and a set of hypervisors for running VMs.  The \"cloud controller\" and \"network gateway\" can be combined in simple deployments, though if you expect VMs to send significant amounts of traffic to or from the Internet, a dedicated network gateway host is suggested to avoid potential CPU contention between packet forwarding performed by the quantum-l3-agent and other OpenStack services."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:270(title)
msgid "Network Connectivity for Physical Hosts"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:280(para)
msgid "A standard OpenStack Networking setup has up to four distinct physical data center networks:"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:283(para)
msgid "<emphasis role=\"bold\">Management network</emphasis>. Used for internal communication between OpenStack Components.   The IP addresses on this network should be reachable only within the data center. "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:291(para)
msgid "<emphasis role=\"bold\">Data network</emphasis>. Used for VM data communication within the cloud deployment.  The IP addressing requirements of this network depend on the OpenStack Networking plugin in use. "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:298(para)
msgid "<emphasis role=\"bold\">External network</emphasis>. Used to provide VMs with Internet access in some deployment scenarios.  The IP addresses on this network should be reachable by anyone on the Internet. "
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:306(para)
msgid "<emphasis role=\"bold\">API network</emphasis>. Exposes all OpenStack APIs, including the OpenStack Networking API, to tenants. The IP addresses on this network should be reachable by anyone on the Internet. This may be the same network as the external network, as it is possible to create a subnet for the external network that uses IP allocation ranges to use only less than the full range of IP addresses in an IP block."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:318(para)
msgid "If the OpenStack Compute metadata service is being used, any address space used on tenant networks must be routable on both the API network and on the External network, since the host running nova-api must be able to reply to HTTP requests with the un-SNATed IP address of a VM."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:324(title)
msgid "OpenStack Networking Deployment Use Cases"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:325(para)
msgid "This section describes some of the common use cases for OpenStack Networking. These examples are not exhaustive and can be combined with each other to create more complex use cases."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:329(title)
msgid "Use Case: Single Flat Network"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:330(para)
msgid "In the simplest use case, a single OpenStack Networking network exists. This is a \"shared\" network, meaning it is visible to all tenants via the OpenStack Networking API. Tenant VMs have a single NIC, and receive a fixed IP address from the subnet(s) associated with that network. This essentially maps to the FlatManager and FlatDHCPManager models provided by OpenStack Compute. Floating IPs are not supported."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:337(para)
msgid "It is common that such an OpenStack Networking network is a \"provider network\", meaning it was created by the OpenStack administrator to map directly to an existing physical network in the data center. This allows the provider to use a physical router on that data center network as the gateway for VMs to reach the outside world. For each subnet on an external network, the gateway configuration on the physical router must be manually configured outside of OpenStack."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:356(title)
msgid "Use Case: Multiple Flat Network"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:357(para)
msgid "This use case is very similar to the above Single Flat Network use case, except that tenants see multiple shared networks via the OpenStack Networking API and can choose which network (or networks) to plug into."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:373(title)
msgid "Use Case: Mixed Flat and Private Network"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:374(para)
msgid "This use case is an extension of the above flat network use cases, in which tenants also optionally have access to private per-tenant networks. In addition to seeing one or more shared networks via the OpenStack Networking API, tenants can create additional networks that are only visible to users of that tenant. When creating VMs, those VMs can have NICs on any of the shared networks and/or any of the private networks belonging to the tenant. This enables the creation of \"multi-tier\" topologies using VMs with multiple NICs. It also supports a model where a VM acting as a gateway can provide services such as routing, NAT, or load balancing."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:397(title)
msgid "Use Case: Provider Router with Private Networks"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:398(para)
msgid "This use provides each tenant with one or more private networks, which connect to the outside world via an OpenStack Networking router. The case where each tenant gets exactly one network in this form maps to the same logical topology as the VlanManager in OpenStack Compute (of course, OpenStack Networking doesn't require VLANs). Using the OpenStack Networking API, the tenant would only see a network for each private network assigned to that tenant. The router object in the API is created and owned by the cloud admin."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:406(para)
msgid "This model supports giving VMs public addresses using \"floating IPs\", in which the router maps public addresses from the external network to fixed IPs on private networks. Hosts without floating IPs can still create outbound connections to the external network, as the provider router performs SNAT to the router's external IP. The IP address of the physical router is used as the gateway_ip of the external network subnet, so the provider has a default router for Internet traffic."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:415(para)
msgid "The router provides L3 connectivity between private networks, meaning that different tenants can reach each others instances unless additional filtering (e.g., security groups) is used. Because there is only a single router, tenant networks cannot use overlapping IPs. Thus, it is likely that the admin would create the private networks on behalf of tenants."
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:433(title)
msgid "Use Case: Per-tenant Routers with Private Networks"
msgstr ""
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:434(para)
msgid "A more advanced router scenario in which each tenant gets at least one router, and potentially has access to the OpenStack Networking API to create additional routers. The tenant can create their own networks, potentially uplinking those networks to a router. This model enables tenant-defined multi-tier applications, with each tier being a separate network behind the router. Since there are multiple routers, tenant subnets can be overlapping without conflicting, since access to external networks all happens via SNAT or Floating IPs. Each router uplink and floating IP is allocated from the external network subnet."
msgstr ""
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
#: ./doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml:0(None)
msgid "translator-credits"
msgstr ""