diff --git a/.tx/config b/.tx/config index f993f8c931..22632e3c5c 100644 --- a/.tx/config +++ b/.tx/config @@ -58,9 +58,9 @@ source_lang = en type = PO [openstack-manuals-i18n.networking-guide] -file_filter = doc/networking-guide/locale/.po +file_filter = doc/networking-guide/source/locale//LC_MESSAGES/user-guides.po minimum_perc = 75 -source_file = doc/networking-guide/locale/networking-guide.pot +source_file = doc/networking-guide/source/locale/networking-guide.pot source_lang = en type = PO diff --git a/doc-tools-check-languages.conf b/doc-tools-check-languages.conf index 875eb39772..b7c657d0c7 100644 --- a/doc-tools-check-languages.conf +++ b/doc-tools-check-languages.conf @@ -26,5 +26,5 @@ DOC_DIR="doc/" declare -A SPECIAL_BOOKS SPECIAL_BOOKS=( ["user-guides"]="RST" - ["networking-guide"]="skip" + ["networking-guide"]="RST" ) diff --git a/doc/networking-guide/locale/networking-guide.pot b/doc/networking-guide/locale/networking-guide.pot deleted file mode 100644 index 89fbf5295e..0000000000 --- a/doc/networking-guide/locale/networking-guide.pot +++ /dev/null @@ -1,3059 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2015-03-04 06:11+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ./doc/networking-guide/ch_networking-architecture.xml:7(title) -msgid "Networking architecture" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:8(para) -msgid "A standard network architecture design includes a cloud controller host, a network gateway host, and a number of hypervisors for hosting virtual machines. The cloud controller and network gateway can be on the same host. However, if you expect VMs to send significant traffic to or from the Internet, a dedicated network gateway host helps avoid CPU contention between the neutron-l3-agent and other OpenStack services that forward packets." -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:18(para) -msgid "You can run OpenStack Networking across multiple physical devices. It is also possible to run all service daemons on a single physical host for evaluation purposes. However, this is not generally robust enough for production purposes. For greater redundancy, you can run each service on a dedicated physical host and replicate any essential services across multiple hosts." -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:26(para) -msgid "For more information about networking architecture options, see the Network Design section of the OpenStack Operations Guide." -msgstr "" - -#. -#. -#. -#. -#. -#: ./doc/networking-guide/ch_networking-architecture.xml:39(para) -msgid "A standard OpenStack Networking deployment usually includes one or more of the following physical networks:" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:47(caption) -msgid "General distinct physical data center networks" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:53(th) -msgid "Network" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:54(th) ./doc/networking-guide/section_networking_adv_features.xml:41(th) ./doc/networking-guide/section_networking_adv_features.xml:132(th) ./doc/networking-guide/section_networking_adv_features.xml:257(th) ./doc/networking-guide/section_networking_adv_features.xml:315(th) ./doc/networking-guide/section_networking_adv_features.xml:616(th) ./doc/networking-guide/section_networking_adv_features.xml:659(th) ./doc/networking-guide/section_networking_adv_features.xml:870(th) ./doc/networking-guide/section_networking_adv_features.xml:992(th) ./doc/networking-guide/section_networking_adv_features.xml:1061(th) ./doc/networking-guide/section_networking_adv_features.xml:1182(th) ./doc/networking-guide/section_networking_adv_features.xml:1497(th) ./doc/networking-guide/section_networking_adv_features.xml:1586(th) ./doc/networking-guide/section_networking_adv_features.xml:1627(th) -msgid "Description" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:59(emphasis) -msgid "Management network" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:61(td) -msgid "Provides internal communication between OpenStack components. IP addresses on this network should be reachable only within the data center." -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:67(emphasis) -msgid "Data network" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:69(td) -msgid "Provides VM data communication within the cloud deployment. The IP addressing requirements of this network depend on the Networking plug-in that is used." -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:76(emphasis) -msgid "External network" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:78(td) -msgid "Provides VMs with Internet access in some deployment scenarios. Anyone on the Internet can reach IP addresses on this network." -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:84(emphasis) -msgid "API network" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:86(td) -msgid "Exposes all OpenStack APIs, including the Networking API, to tenants. IP addresses on this network should be reachable by anyone on the Internet. The API network might be the same as the external network because it is possible to create an external-network subnet that has allocated IP ranges, which use less than the full range of IP addresses in an IP block." -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:101(title) -msgid "Tenant and provider networks" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:102(para) -msgid "The following diagram presents an overview of the tenant and provider network types, and illustrates how they interact within the overall Networking topology:" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:119(title) -msgid "Tenant networks" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:120(para) -msgid "Users create tenant networks for connectivity within projects; they are fully isolated by default and are not shared with other projects. Networking supports a range of tenant network types:" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:128(term) ./doc/networking-guide/section_plugins-ml2.xml:23(term) -msgid "Flat" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:130(para) -msgid "All instances reside on the same network, which can also be shared with the hosts. No VLAN tagging or other network segregation takes place." -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:137(term) ./doc/networking-guide/section_plugins-ml2.xml:52(para) -msgid "Local" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:139(para) -msgid "Instances reside on the local compute host and are effectively isolated from any external networks." -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:145(term) ./doc/networking-guide/section_plugins-ml2.xml:29(term) -msgid "VLAN" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:147(para) -msgid "Networking allows users to create multiple provider or tenant networks using VLAN IDs (802.1Q tagged) that correspond to VLANs present in the physical network. This allows instances to communicate with each other across the environment. They can also communicate with dedicated servers, firewalls, load balancers, and other networking infrastructure on the same layer 2 VLAN." -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:157(term) -msgid "VXLAN and GRE" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:159(para) -msgid "VXLAN and GRE use network overlays to support private communication between instances. A Networking router is required to enable traffic to traverse outside of the GRE or VXLAN tenant network. A router is also required to connect directly-connected tenant networks with external networks, including the Internet. The router provides the ability to connect to instances directly from an external network using floating IP addresses." -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:172(title) ./doc/networking-guide/section_networking_adv_features.xml:10(title) -msgid "Provider networks" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:173(para) -msgid "The OpenStack administrator creates provider networks. These networks map to existing physical networks in the data center. Useful network types in this category are flat (untagged) and VLAN (802.1Q tagged). It is possible to share provider networks among tenants as part of the network creation process." -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:181(title) -msgid "VMware NSX integration" -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:182(para) -msgid "OpenStack Networking uses the NSX plug-in for Networking to integrate with an existing VMware vCenter deployment. When installed on the network nodes, the NSX plug-in enables a NSX controller to centrally manage configuration settings and push them to managed network nodes. Network nodes are considered managed when they're added as hypervisors to the NSX controller." -msgstr "" - -#: ./doc/networking-guide/ch_networking-architecture.xml:188(para) -msgid "The following diagram depicts an example NSX deployment and illustrates the route inter-VM traffic takes between separate Compute nodes. Note the placement of the VMware NSX plug-in and the neutron-server service on the network node. The NSX controller features centrally with a green line to the network node to indicate the management relationship:" -msgstr "" - -#: ./doc/networking-guide/ch_scalability-HA.xml:7(title) -msgid "Scalability and high availability" -msgstr "" - -#: ./doc/networking-guide/ch_scalability-HA.xml:8(para) ./doc/networking-guide/section_ha-dhcp.xml:12(para) ./doc/networking-guide/section_architecture-overview.xml:12(para) ./doc/networking-guide/ch_networking-data-model.xml:12(para) ./doc/networking-guide/section_deployment-authentication.xml:12(para) ./doc/networking-guide/ch_plugins.xml:8(para) ./doc/networking-guide/section_architecture-server.xml:12(para) -msgid "Bacon ipsum dolor sit amet biltong meatloaf andouille, turducken bresaola pork belly beef ribs ham hock capicola tail prosciutto landjaeger meatball pork loin. Swine turkey jowl, porchetta doner boudin meatloaf. Shoulder capicola prosciutto, shank landjaeger short ribs sirloin turducken pork belly boudin frankfurter chuck. Salami shankle bresaola cow filet mignon ham hock shank." -msgstr "" - -#: ./doc/networking-guide/section_plugins-proprietary.xml:11(title) ./doc/networking-guide/section_plugins-ml2.xml:89(term) -msgid "Proprietary" -msgstr "" - -#: ./doc/networking-guide/section_plugins-proprietary.xml:12(para) ./doc/networking-guide/section_plugins-ml2.xml:25(para) ./doc/networking-guide/section_plugins-ml2.xml:31(para) ./doc/networking-guide/section_plugins-ml2.xml:37(para) ./doc/networking-guide/section_plugins-ml2.xml:43(para) ./doc/networking-guide/section_plugins-ml2.xml:67(para) ./doc/networking-guide/section_plugins-ml2.xml:73(para) ./doc/networking-guide/section_plugins-ml2.xml:79(para) ./doc/networking-guide/section_plugins-ml2.xml:85(para) ./doc/networking-guide/section_plugins-ml2.xml:91(para) ./doc/networking-guide/section_plugins-ml2.xml:103(para) ./doc/networking-guide/section_intro-neutron.xml:19(para) ./doc/networking-guide/section_intro-neutron.xml:23(para) ./doc/networking-guide/section_intro-neutron.xml:27(para) ./doc/networking-guide/section_intro-neutron.xml:31(para) ./doc/networking-guide/ch_advanced.xml:16(para) ./doc/networking-guide/ch_advanced.xml:20(para) ./doc/networking-guide/ch_advanced.xml:24(para) -msgid "FIXME" -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/networking-guide/section_ha-dvr.xml:24(None) -msgid "@@image: 'figures/dvr_diagram.png'; md5=8d69121eb03d90239cab504d21e1c64f" -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:10(title) -msgid "Distributed Virtual Router (DVR)" -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:11(para) -msgid "DVR stands for Distributed Virtual Router. For OpenStack Networking you can provide high availability across compute nodes using a DVR configuration. Both the layer-2 and layer-3 agents work together on a compute node, and the L2 agent works in an enhanced mode for DVR, providing management for OVS rules. In this scenario you do not use a separate networking node unless a legacy one is in place already." -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:18(para) -msgid "Here is a sample network topology showing how distributed routing occurs." -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:21(title) -msgid "DVR configuration diagram" -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:28(para) -msgid "The DVR agent takes responsibility for creating, updating, or deleting the routers in the router namespaces. For all clients in the network owned by the router, the DVR agent populates the ARP entry. By pre-populating ARP entries across compute nodes, the distributed virtual router ensures traffic goes to the correct destination. The integration bridge on a particular compute node identifies the incoming frame's source MAC address as a DVR-unique MAC address because every compute node l2 agent knows all configured unique MAC addresses for DVR used in the cloud. The agent replaces the DVR-unique MAC Address with the green subnet interface MAC address and forwards the frame to the instance. By default, distributed routing is not turned on. When set to true, the layer-2 agent handles the DVR ports detected on the integration bridge. Also, when a tenant creates a router with neutron router-create, the Networking services creates only distributed routers after you have enabled distributed routing." -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:44(title) -msgid "Configure Distributed Virtual Router (DVR)" -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:47(para) -msgid "Edit the ovs_neutron_plugin.ini file to change enable_distributed_routing to True:" -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:53(para) -msgid "Edit the /etc/neutron/neutron.conf file to set the base MAC address that the DVR system uses for unique MAC allocation with the dvr_base_mac setting:" -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:58(para) -msgid "This dvr_base_mac value must be different from the base_mac value assigned for virtual ports to ensure port isolation and for troubleshooting purposes. The default is fa:16:3f:00:00:00. If you want four octets used, substitute again for the fourth octet (00), otherwise three octets are kept the same and the others are randomly generated." -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:68(para) -msgid "Edit the /etc/neutron/neutron.conf file to set router_distributed to True." -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:74(para) -msgid "Edit the l3_agent.ini file to set agent_mode to dvr on compute nodes for multi-node deployments:" -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:79(para) -msgid "When using a separate networking host, set agent_mode to dvr_snat. Use dvr_snat for Devstack or other single-host deployments also." -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:86(para) -msgid "In the [ml2] section, edit the ml2_conf.ini file to add l2population:" -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:93(para) -msgid "In the [agent] section of the ml2_conf.ini file, set these configuration options to these values:" -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:102(para) -msgid "Restart the OVS L2 agent." -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:105(para) -msgid "Ubuntu/Debian:" -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:109(para) -msgid "RHEL/CentOS/Fedora:" -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:113(para) -msgid "SLES/openSUSE:" -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:121(title) -msgid "DVR requirements" -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:124(para) -msgid "You must use the ML2 plug-in for Open vSwitch (OVS) to enable DVR." -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:128(para) -msgid "Be sure that your firewall or security groups allows UDP traffic over the VLAN, GRE, or VXLAN port to pass between the compute hosts." -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:134(title) -msgid "DVR limitations" -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:137(para) -msgid "Distributed virtual router configurations work with the Open vSwitch Modular Layer 2 driver only for Juno." -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:141(para) -msgid "In order to enable true north-south bandwidth between hypervisors (compute nodes), you must use public IP addresses for every compute node and enable floating IPs." -msgstr "" - -#: ./doc/networking-guide/section_ha-dvr.xml:146(para) -msgid "For now, based on the current neutron design and architecture, DHCP cannot become distributed across compute nodes." -msgstr "" - -#: ./doc/networking-guide/section_ha-l3.xml:11(title) -msgid "L3 Agents" -msgstr "" - -#: ./doc/networking-guide/section_ha-l3.xml:12(para) -msgid "The Neutron L3 Agent enables layer 3 forwarding and floating IP support. It provides L3/NAT forwarding to ensure external network access for VMs on tenant networks. The L3 agent achieves High Availability by adopting Pacemaker." -msgstr "" - -#: ./doc/networking-guide/section_intro-namespaces.xml:11(title) -msgid "Namespaces" -msgstr "" - -#: ./doc/networking-guide/section_intro-namespaces.xml:12(para) -msgid "A namespace is a container for a set of identifiers. Namespaces provide a level of direction to specific identifiers and make it possible to differentiate between identifiers with the same exact name. With network namespaces, you can have different and separate instances of network interfaces and routing tables that operate separate from each other." -msgstr "" - -#: ./doc/networking-guide/section_ha-dhcp.xml:11(title) -msgid "DHCP Agents" -msgstr "" - -#: ./doc/networking-guide/section_architecture-overview.xml:11(title) ./doc/networking-guide/section_plugins-ml2.xml:14(title) ./doc/networking-guide/section_architecture-agents.xml:71(title) -msgid "Overview" -msgstr "" - -#: ./doc/networking-guide/section_architecture-overview.xml:22(title) -msgid "Service/component hierarchy" -msgstr "" - -#: ./doc/networking-guide/section_architecture-overview.xml:23(para) -msgid "Neutron server -> plug-in -> agents" -msgstr "" - -#: ./doc/networking-guide/section_architecture-overview.xml:27(title) -msgid "Example architectures" -msgstr "" - -#: ./doc/networking-guide/section_architecture-overview.xml:29(para) -msgid "XIncluded below from Cloud Admin Guide. May need to be reworked. See also http://docs.openstack.org/grizzly/openstack-network/admin/content/use_cases.html and admin-guide-cloud/networking/section_networking-scenarios.xml ." -msgstr "" - -#: ./doc/networking-guide/section_intro-routers.xml:11(title) -msgid "Routers" -msgstr "" - -#: ./doc/networking-guide/section_intro-routers.xml:13(para) -msgid "A router is a networking device that connects multiple networks together. Routers are connected to two or more networks. When they receive data packets, they use a routing table to determine which networks to pass the information to." -msgstr "" - -#: ./doc/networking-guide/section_intro-tunnel.xml:11(title) -msgid "Tunnel (segmentation) technologies" -msgstr "" - -#: ./doc/networking-guide/section_intro-tunnel.xml:13(para) -msgid "Tunneling allows one network protocol to encapsulate another payload protocol, such that packets from the payload protocol are passed as data on the delivery protocol. This can be used, for example, to pass data securely over an untrusted network." -msgstr "" - -#: ./doc/networking-guide/section_intro-tunnel.xml:19(title) ./doc/networking-guide/section_architecture-agents.xml:77(title) -msgid "Layer 2" -msgstr "" - -#: ./doc/networking-guide/section_intro-tunnel.xml:22(term) -msgid "Virtual local area network (VLAN)" -msgstr "" - -#: ./doc/networking-guide/section_intro-tunnel.xml:24(para) -msgid "A VLAN partitions a single layer-2 network into multiple isolated broadcast domains." -msgstr "" - -#: ./doc/networking-guide/section_intro-tunnel.xml:32(title) -msgid "Layer 3" -msgstr "" - -#: ./doc/networking-guide/section_intro-tunnel.xml:36(term) -msgid "Generic routing encapsulation (GRE)" -msgstr "" - -#: ./doc/networking-guide/section_intro-tunnel.xml:38(para) -msgid "GRE carries IP packets with private IP address over the Internet using delivery packets with public IP addresses." -msgstr "" - -#: ./doc/networking-guide/section_intro-tunnel.xml:44(term) -msgid "Virtual extensible local area network (VXLAN)" -msgstr "" - -#: ./doc/networking-guide/section_intro-tunnel.xml:46(para) -msgid "VXLAN encapsulates layer-2 Ethernet frames over layer-4 UDP packets." -msgstr "" - -#: ./doc/networking-guide/section_plugins-ml2.xml:11(title) -msgid "ML2" -msgstr "" - -#: ./doc/networking-guide/section_plugins-ml2.xml:15(para) -msgid "architecture" -msgstr "" - -#: ./doc/networking-guide/section_plugins-ml2.xml:16(para) -msgid "configuration file organization, relationships, etc" -msgstr "" - -#: ./doc/networking-guide/section_plugins-ml2.xml:20(title) -msgid "Network type drivers" -msgstr "" - -#: ./doc/networking-guide/section_plugins-ml2.xml:35(term) -msgid "GRE" -msgstr "" - -#: ./doc/networking-guide/section_plugins-ml2.xml:41(term) -msgid "VXLAN" -msgstr "" - -#: ./doc/networking-guide/section_plugins-ml2.xml:50(title) -msgid "Tenant network types" -msgstr "" - -#: ./doc/networking-guide/section_plugins-ml2.xml:53(para) -msgid "VLAN, VLAN ID ranges" -msgstr "" - -#: ./doc/networking-guide/section_plugins-ml2.xml:54(para) -msgid "GRE, Tunnel ID ranges" -msgstr "" - -#: ./doc/networking-guide/section_plugins-ml2.xml:55(para) -msgid "VXLAN, VNI ID ranges" -msgstr "" - -#: ./doc/networking-guide/section_plugins-ml2.xml:58(para) -msgid "See admin-guide-cloud/networking/section_networking_arch.xml" -msgstr "" - -#: ./doc/networking-guide/section_plugins-ml2.xml:62(title) -msgid "Mechanisms" -msgstr "" - -#: ./doc/networking-guide/section_plugins-ml2.xml:65(term) ./doc/networking-guide/section_networking_adv_agent.xml:78(emphasis) ./doc/networking-guide/section_networking_adv_agent.xml:128(emphasis) ./doc/networking-guide/section_networking_adv_agent.xml:177(emphasis) ./doc/networking-guide/section_networking_adv_agent.xml:309(emphasis) ./doc/networking-guide/section_architecture-agents.xml:80(term) -msgid "Linux Bridge" -msgstr "" - -#: ./doc/networking-guide/section_plugins-ml2.xml:71(term) ./doc/networking-guide/section_networking_adv_agent.xml:57(emphasis) ./doc/networking-guide/section_networking_adv_agent.xml:120(emphasis) ./doc/networking-guide/section_networking_adv_agent.xml:165(emphasis) ./doc/networking-guide/section_networking_adv_agent.xml:301(emphasis) ./doc/networking-guide/section_architecture-agents.xml:87(term) -msgid "Open vSwitch" -msgstr "" - -#: ./doc/networking-guide/section_plugins-ml2.xml:77(term) -msgid "Open Daylight" -msgstr "" - -#: ./doc/networking-guide/section_plugins-ml2.xml:83(term) -msgid "L2 Population" -msgstr "" - -#: ./doc/networking-guide/section_plugins-ml2.xml:98(title) -msgid "Security" -msgstr "" - -#: ./doc/networking-guide/section_plugins-ml2.xml:101(term) -msgid "Options" -msgstr "" - -#: ./doc/networking-guide/ch_intro.xml:11(title) -msgid "Introduction to networking" -msgstr "" - -#: ./doc/networking-guide/ch_intro.xml:12(para) -msgid "The OpenStack Networking service provides an API that allows users to set up and define network connectivity and addressing in the cloud. The project code-name for Networking services is neutron. OpenStack Networking handles the creation and management of a virtual networking infrastructure, including networks, switches, subnets, and routers for devices managed by the OpenStack Compute service (nova). Advanced services such as firewalls or virtual private networks (VPNs) can also be used." -msgstr "" - -#: ./doc/networking-guide/ch_intro.xml:27(para) -msgid "OpenStack Networking consists of the neutron-server, a database for persistent storage, and any number of plugin agents, which provide other services such as interfacing with native Linux networking mechanisms, external devices, or SDN controllers." -msgstr "" - -#: ./doc/networking-guide/ch_intro.xml:35(para) -msgid "OpenStack Networking is entirely standalone and can be deployed to a dedicated host. If your deployment uses a controller host to run centralized Compute components, you can deploy the Networking server to that specific host instead." -msgstr "" - -#: ./doc/networking-guide/ch_intro.xml:41(para) -msgid "OpenStack Networking integrates with various other OpenStack components:" -msgstr "" - -#: ./doc/networking-guide/ch_intro.xml:47(para) -msgid "OpenStack Identity (keystone) is used for authentication and authorization of API requests." -msgstr "" - -#: ./doc/networking-guide/ch_intro.xml:51(para) -msgid "OpenStack Compute (nova) is used to plug each virtual NIC on the VM into a particular network." -msgstr "" - -#: ./doc/networking-guide/ch_intro.xml:55(para) -msgid "OpenStack dashboard (horizon) for administrators and tenant users to create and manage network services through a web-based graphical interface." -msgstr "" - -#: ./doc/networking-guide/bk-networking.xml:5(title) -msgid "OpenStack Networking Guide" -msgstr "" - -#: ./doc/networking-guide/bk-networking.xml:10(titleabbrev) -msgid "Networking Guide" -msgstr "" - -#: ./doc/networking-guide/bk-networking.xml:18(orgname) ./doc/networking-guide/bk-networking.xml:24(holder) -msgid "OpenStack Foundation" -msgstr "" - -#: ./doc/networking-guide/bk-networking.xml:22(year) -msgid "2014" -msgstr "" - -#: ./doc/networking-guide/bk-networking.xml:23(year) -msgid "2015" -msgstr "" - -#: ./doc/networking-guide/bk-networking.xml:26(releaseinfo) -msgid "current" -msgstr "" - -#: ./doc/networking-guide/bk-networking.xml:27(productname) -msgid "OpenStack" -msgstr "" - -#: ./doc/networking-guide/bk-networking.xml:31(remark) -msgid "Copyright details are filled in by the template." -msgstr "" - -#: ./doc/networking-guide/bk-networking.xml:36(remark) -msgid "Remaining licensing details are filled in by the template." -msgstr "" - -#: ./doc/networking-guide/bk-networking.xml:40(para) -msgid "This guide targets OpenStack administrators seeking to deploy and manage OpenStack Networking." -msgstr "" - -#: ./doc/networking-guide/bk-networking.xml:48(date) -msgid "2014-08-08" -msgstr "" - -#: ./doc/networking-guide/bk-networking.xml:52(para) -msgid "Creation of document." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:5(title) -msgid "Advanced features through API extensions" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:6(para) -msgid "Several plug-ins implement API extensions that provide capabilities similar to what was available in nova-network: These plug-ins are likely to be of interest to the OpenStack community." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:11(para) -msgid "Networks can be categorized as either tenant networks or provider networks. Tenant networks are created by normal users. Details about how these networks are physically realized remain hidden from those users. Provider networks are created with administrative credentials, specifying the details of how the network is physically realized. Provider networks usually match an existing network in the data center." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:17(para) -msgid "Provider networks enable cloud administrators to create virtual networks that map directly to the physical networks in the data center. This is commonly used to give tenants direct access to a public network, which can be used to reach the Internet. It might also be used to integrate with VLANs in the network that already have a defined meaning (for example, enable 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/networking-guide/section_networking_adv_features.xml:23(para) -msgid "The provider extension allows administrators to explicitly manage the relationship between virtual networks and underlying physical mechanisms such as VLANs and tunnels. When this extension is supported, 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/networking-guide/section_networking_adv_features.xml:28(para) -msgid "The provider extension is supported by the Open vSwitch and Linux Bridge plug-ins. Configuration of these plug-ins requires familiarity with this extension." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:31(title) -msgid "Terminology" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:32(para) -msgid "A number of terms are used in the provider extension and in the configuration of plug-ins supporting the provider extension:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:35(caption) -msgid "Provider extension terminology" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:40(th) -msgid "Term" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:46(emphasis) -msgid "virtual network" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:47(td) -msgid "An Networking L2 network (identified by a UUID and optional name) whose ports can be attached as vNICs to Compute instances and to various Networking agents. The Open vSwitch and Linux Bridge plug-ins each support several different mechanisms to realize virtual networks." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:53(emphasis) -msgid "physical network" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:54(td) -msgid "A network connecting virtualization hosts (such as compute nodes) with each other and with other network resources. Each physical network might support multiple virtual networks. The provider extension and the plug-in configurations identify physical networks using simple string names." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:61(emphasis) -msgid "tenant network" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:62(td) -msgid "A virtual network that a tenant or an administrator creates. The physical details of the network are not exposed to the tenant." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:66(emphasis) -msgid "provider network" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:67(td) -msgid "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/networking-guide/section_networking_adv_features.xml:73(emphasis) -msgid "VLAN network" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:74(td) -msgid "A virtual network implemented 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/networking-guide/section_networking_adv_features.xml:83(emphasis) -msgid "flat network" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:84(td) -msgid "A virtual network implemented 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/networking-guide/section_networking_adv_features.xml:89(emphasis) -msgid "local network" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:90(td) -msgid "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 can have other uses." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:95(emphasis) -msgid "GRE network" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:98(emphasis) -msgid "tunnels" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:96(td) -msgid "A virtual network implemented as network packets encapsulated using GRE. GRE networks are also referred to as . GRE tunnel packets are routed by the IP routing table for the host, so GRE networks are not associated by Networking with specific physical networks." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:103(emphasis) -msgid "Virtual Extensible LAN (VXLAN) network" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:105(td) -msgid "VXLAN is a proposed encapsulation protocol for running an overlay network on existing Layer 3 infrastructure. An overlay network is a virtual network that is built on top of existing network Layer 2 and Layer 3 technologies to support elastic compute architectures." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:112(para) -msgid "The ML2, Open vSwitch, and Linux Bridge plug-ins support VLAN networks, flat networks, and local networks. Only the ML2 and Open vSwitch plug-ins currently support GRE and VXLAN networks, provided that the required features exist in the hosts Linux kernel, Open vSwitch, and iproute2 packages." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:118(title) -msgid "Provider attributes" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:119(para) -msgid "The provider extension extends the Networking network resource with these attributes:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:122(caption) -msgid "Provider network attributes" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:129(th) ./doc/networking-guide/section_networking_adv_features.xml:254(th) ./doc/networking-guide/section_networking_adv_features.xml:312(th) ./doc/networking-guide/section_networking_adv_features.xml:613(th) ./doc/networking-guide/section_networking_adv_features.xml:656(th) ./doc/networking-guide/section_networking_adv_features.xml:867(th) ./doc/networking-guide/section_networking_adv_features.xml:989(th) ./doc/networking-guide/section_networking_adv_features.xml:1058(th) ./doc/networking-guide/section_networking_adv_features.xml:1179(th) ./doc/networking-guide/section_networking_adv_features.xml:1494(th) ./doc/networking-guide/section_networking_adv_features.xml:1583(th) ./doc/networking-guide/section_networking_adv_features.xml:1624(th) -msgid "Attribute name" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:130(th) ./doc/networking-guide/section_networking_adv_features.xml:255(th) ./doc/networking-guide/section_networking_adv_features.xml:313(th) ./doc/networking-guide/section_networking_adv_features.xml:614(th) ./doc/networking-guide/section_networking_adv_features.xml:657(th) ./doc/networking-guide/section_networking_adv_features.xml:868(th) ./doc/networking-guide/section_networking_adv_features.xml:990(th) ./doc/networking-guide/section_networking_adv_features.xml:1059(th) ./doc/networking-guide/section_networking_adv_features.xml:1180(th) ./doc/networking-guide/section_networking_adv_features.xml:1584(th) ./doc/networking-guide/section_networking_adv_features.xml:1625(th) -msgid "Type" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:131(th) ./doc/networking-guide/section_networking_adv_features.xml:256(th) ./doc/networking-guide/section_networking_adv_features.xml:314(th) ./doc/networking-guide/section_networking_adv_features.xml:615(th) ./doc/networking-guide/section_networking_adv_features.xml:658(th) ./doc/networking-guide/section_networking_adv_features.xml:869(th) ./doc/networking-guide/section_networking_adv_features.xml:991(th) ./doc/networking-guide/section_networking_adv_features.xml:1060(th) ./doc/networking-guide/section_networking_adv_features.xml:1181(th) ./doc/networking-guide/section_networking_adv_features.xml:1585(th) ./doc/networking-guide/section_networking_adv_features.xml:1626(th) -msgid "Default Value" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:137(td) -msgid "provider:network_type" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:138(td) ./doc/networking-guide/section_networking_adv_features.xml:152(td) ./doc/networking-guide/section_networking_adv_features.xml:269(td) ./doc/networking-guide/section_networking_adv_features.xml:282(td) ./doc/networking-guide/section_networking_adv_features.xml:628(td) ./doc/networking-guide/section_networking_adv_features.xml:635(td) ./doc/networking-guide/section_networking_adv_features.xml:677(td) ./doc/networking-guide/section_networking_adv_features.xml:683(td) ./doc/networking-guide/section_networking_adv_features.xml:701(td) ./doc/networking-guide/section_networking_adv_features.xml:889(td) ./doc/networking-guide/section_networking_adv_features.xml:895(td) ./doc/networking-guide/section_networking_adv_features.xml:920(td) ./doc/networking-guide/section_networking_adv_features.xml:966(td) ./doc/networking-guide/section_networking_adv_features.xml:1011(td) ./doc/networking-guide/section_networking_adv_features.xml:1017(td) ./doc/networking-guide/section_networking_adv_features.xml:1080(td) ./doc/networking-guide/section_networking_adv_features.xml:1086(td) ./doc/networking-guide/section_networking_adv_features.xml:1100(td) ./doc/networking-guide/section_networking_adv_features.xml:1202(td) ./doc/networking-guide/section_networking_adv_features.xml:1220(td) ./doc/networking-guide/section_networking_adv_features.xml:1598(td) ./doc/networking-guide/section_networking_adv_features.xml:1604(td) -msgid "String" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:139(td) ./doc/networking-guide/section_networking_adv_features.xml:164(td) ./doc/networking-guide/section_networking_adv_features.xml:283(td) ./doc/networking-guide/section_networking_adv_features.xml:291(td) ./doc/networking-guide/section_networking_adv_features.xml:335(td) ./doc/networking-guide/section_networking_adv_features.xml:344(td) ./doc/networking-guide/section_networking_adv_features.xml:366(td) ./doc/networking-guide/section_networking_adv_features.xml:642(td) ./doc/networking-guide/section_networking_adv_features.xml:678(td) ./doc/networking-guide/section_networking_adv_features.xml:720(td) ./doc/networking-guide/section_networking_adv_features.xml:883(td) ./doc/networking-guide/section_networking_adv_features.xml:1005(td) ./doc/networking-guide/section_networking_adv_features.xml:1074(td) ./doc/networking-guide/section_networking_adv_features.xml:1101(td) ./doc/networking-guide/section_networking_adv_features.xml:1215(td) ./doc/networking-guide/section_networking_adv_features.xml:1233(td) ./doc/networking-guide/section_networking_adv_features.xml:1611(td) ./doc/networking-guide/section_networking_adv_features.xml:1647(td) ./doc/networking-guide/section_networking_adv_features.xml:1663(td) -msgid "N/A" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:141(literal) ./doc/networking-guide/section_networking_adv_features.xml:154(literal) ./doc/networking-guide/section_networking_adv_features.xml:168(literal) -msgid "flat" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:141(literal) ./doc/networking-guide/section_networking_adv_features.xml:146(literal) ./doc/networking-guide/section_networking_adv_features.xml:155(literal) -msgid "vlan" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:142(literal) ./doc/networking-guide/section_networking_adv_features.xml:147(literal) ./doc/networking-guide/section_networking_adv_features.xml:158(literal) ./doc/networking-guide/section_networking_adv_features.xml:169(literal) -msgid "local" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:142(literal) ./doc/networking-guide/section_networking_adv_features.xml:146(literal) ./doc/networking-guide/section_networking_adv_features.xml:158(literal) -msgid "gre" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:140(td) -msgid "The physical mechanism by which the virtual network is implemented. Possible values are , , , and , 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 implemented as , , or network types depending on plug-in configuration." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:151(td) -msgid "provider:physical_network" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:153(td) -msgid "If a physical network named \"default\" has been configured and if provider:network_type is or , then \"default\" is used." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:156(td) -msgid "The name of the physical network over which the virtual network is implemented for flat and VLAN networks. Not applicable to the or network types." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:162(td) -msgid "provider:segmentation_id" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:163(td) ./doc/networking-guide/section_networking_adv_features.xml:689(td) ./doc/networking-guide/section_networking_adv_features.xml:695(td) ./doc/networking-guide/section_networking_adv_features.xml:958(td) ./doc/networking-guide/section_networking_adv_features.xml:1208(td) ./doc/networking-guide/section_networking_adv_features.xml:1214(td) ./doc/networking-guide/section_networking_adv_features.xml:1226(td) -msgid "Integer" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:165(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 or network types." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:173(para) -msgid "To view or set provider extended attributes, a client must be authorized for the extension:provider_network:view and extension:provider_network:set actions in the Networking policy configuration. The default Networking configuration authorizes both actions for users with the admin role. An authorized client or an administrative user can view and set the provider extended attributes through Networking API calls." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:182(title) -msgid "Provider extension API operations" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:183(para) -msgid "To use the provider extension with the default policy settings, you must have the administrative role." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:185(para) -msgid "This list shows example neutron commands that enable you to complete basic provider extension API operations:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:189(para) -msgid "Shows all attributes of a network, including provider attributes:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:190(replaceable) -msgid "NAME_OR_NET_ID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:193(para) -msgid "Creates a local provider network:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:194(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:201(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:211(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:221(replaceable) -msgid "NAME" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:194(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:201(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:211(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:221(replaceable) -msgid "TENANT_ID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:197(para) -msgid "When you create flat networks, PHYS_NET_NAME must be known to the plug-in. See the OpenStack Configuration Reference for details. Creates a flat provider network:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:201(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:211(replaceable) -msgid "PHYS_NET_NAME" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:204(para) -msgid "When you create VLAN networks, PHYS_NET_NAME must be known to the plug-in. See the OpenStack Configuration Reference for details on configuring network_vlan_ranges to identify all physical networks. When you create VLAN networks, VID can fall either within or outside any configured ranges of VLAN IDs from which tenant networks are allocated. Creates a VLAN provider network:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:211(replaceable) -msgid "VID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:214(para) -msgid "When you create GRE networks, TUNNEL_ID can be either inside or outside any tunnel ID ranges from which tenant networks are allocated." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:217(para) -msgid "After you create provider networks, you can allocate subnets, which you can use in the same way as other virtual networks, subject to authorization policy based on the specified TENANT_ID. Creates a GRE provider network:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:221(replaceable) -msgid "TUNNEL_ID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:227(title) -msgid "L3 routing and NAT" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:228(para) -msgid "The Networking API provides abstract L2 network segments that are decoupled from the technology used to implement the L2 network. Networking includes an API extension that provides abstract L3 routers that API users can dynamically provision and configure. These Networking routers can connect multiple L2 Networking networks and can also provide a gateway that connects one or more private L2 networks to a shared external network. For example, a public network for access to the Internet. See the OpenStack Configuration Reference for details on common models of deploying Networking L3 routers." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:236(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). You can allocate and map floating IPs from one port to another, as needed." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:245(title) -msgid "L3 API abstractions" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:247(caption) -msgid "Router" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:262(td) ./doc/networking-guide/section_networking_adv_features.xml:320(td) ./doc/networking-guide/section_networking_adv_features.xml:621(td) ./doc/networking-guide/section_networking_adv_features.xml:664(td) ./doc/networking-guide/section_networking_adv_features.xml:875(td) ./doc/networking-guide/section_networking_adv_features.xml:997(td) ./doc/networking-guide/section_networking_adv_features.xml:1066(td) ./doc/networking-guide/section_networking_adv_features.xml:1187(td) ./doc/networking-guide/section_networking_adv_features.xml:1591(td) ./doc/networking-guide/section_networking_adv_features.xml:1632(td) -msgid "id" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:263(td) ./doc/networking-guide/section_networking_adv_features.xml:290(td) ./doc/networking-guide/section_networking_adv_features.xml:321(td) ./doc/networking-guide/section_networking_adv_features.xml:334(td) ./doc/networking-guide/section_networking_adv_features.xml:343(td) ./doc/networking-guide/section_networking_adv_features.xml:350(td) ./doc/networking-guide/section_networking_adv_features.xml:365(td) ./doc/networking-guide/section_networking_adv_features.xml:622(td) ./doc/networking-guide/section_networking_adv_features.xml:641(td) ./doc/networking-guide/section_networking_adv_features.xml:665(td) ./doc/networking-guide/section_networking_adv_features.xml:719(td) ./doc/networking-guide/section_networking_adv_features.xml:876(td) ./doc/networking-guide/section_networking_adv_features.xml:882(td) ./doc/networking-guide/section_networking_adv_features.xml:998(td) ./doc/networking-guide/section_networking_adv_features.xml:1004(td) ./doc/networking-guide/section_networking_adv_features.xml:1067(td) ./doc/networking-guide/section_networking_adv_features.xml:1073(td) ./doc/networking-guide/section_networking_adv_features.xml:1188(td) ./doc/networking-guide/section_networking_adv_features.xml:1232(td) ./doc/networking-guide/section_networking_adv_features.xml:1592(td) ./doc/networking-guide/section_networking_adv_features.xml:1610(td) ./doc/networking-guide/section_networking_adv_features.xml:1633(td) ./doc/networking-guide/section_networking_adv_features.xml:1646(td) -msgid "uuid-str" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:264(td) ./doc/networking-guide/section_networking_adv_features.xml:322(td) ./doc/networking-guide/section_networking_adv_features.xml:623(td) ./doc/networking-guide/section_networking_adv_features.xml:666(td) ./doc/networking-guide/section_networking_adv_features.xml:877(td) ./doc/networking-guide/section_networking_adv_features.xml:999(td) ./doc/networking-guide/section_networking_adv_features.xml:1068(td) ./doc/networking-guide/section_networking_adv_features.xml:1189(td) ./doc/networking-guide/section_networking_adv_features.xml:1593(td) ./doc/networking-guide/section_networking_adv_features.xml:1634(td) -msgid "generated" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:265(td) -msgid "UUID for the router." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:268(td) ./doc/networking-guide/section_networking_adv_features.xml:627(td) ./doc/networking-guide/section_networking_adv_features.xml:888(td) ./doc/networking-guide/section_networking_adv_features.xml:1010(td) ./doc/networking-guide/section_networking_adv_features.xml:1079(td) ./doc/networking-guide/section_networking_adv_features.xml:1201(td) ./doc/networking-guide/section_networking_adv_features.xml:1597(td) -msgid "name" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:270(td) ./doc/networking-guide/section_networking_adv_features.xml:629(td) ./doc/networking-guide/section_networking_adv_features.xml:636(td) ./doc/networking-guide/section_networking_adv_features.xml:684(td) ./doc/networking-guide/section_networking_adv_features.xml:690(td) ./doc/networking-guide/section_networking_adv_features.xml:696(td) ./doc/networking-guide/section_networking_adv_features.xml:702(td) ./doc/networking-guide/section_networking_adv_features.xml:708(td) ./doc/networking-guide/section_networking_adv_features.xml:890(td) ./doc/networking-guide/section_networking_adv_features.xml:896(td) ./doc/networking-guide/section_networking_adv_features.xml:921(td) ./doc/networking-guide/section_networking_adv_features.xml:933(td) ./doc/networking-guide/section_networking_adv_features.xml:939(td) ./doc/networking-guide/section_networking_adv_features.xml:946(td) ./doc/networking-guide/section_networking_adv_features.xml:953(td) ./doc/networking-guide/section_networking_adv_features.xml:959(td) ./doc/networking-guide/section_networking_adv_features.xml:1012(td) ./doc/networking-guide/section_networking_adv_features.xml:1018(td) ./doc/networking-guide/section_networking_adv_features.xml:1033(td) ./doc/networking-guide/section_networking_adv_features.xml:1081(td) ./doc/networking-guide/section_networking_adv_features.xml:1087(td) ./doc/networking-guide/section_networking_adv_features.xml:1130(td) ./doc/networking-guide/section_networking_adv_features.xml:1203(td) ./doc/networking-guide/section_networking_adv_features.xml:1599(td) ./doc/networking-guide/section_networking_adv_features.xml:1605(td) -msgid "None" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:271(td) -msgid "Human-readable name for the router. Might not be unique." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:274(td) ./doc/networking-guide/section_networking_adv_features.xml:1092(td) -msgid "admin_state_up" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:275(td) -msgid "Bool" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:276(td) ./doc/networking-guide/section_networking_adv_features.xml:974(td) ./doc/networking-guide/section_networking_adv_features.xml:1094(td) -msgid "True" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:277(td) -msgid "The administrative state of router. If false (down), the router does not forward packets." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:281(td) ./doc/networking-guide/section_networking_adv_features.xml:1099(td) -msgid "status" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:285(para) -msgid "Indicates whether router is currently operational." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:289(td) ./doc/networking-guide/section_networking_adv_features.xml:364(td) ./doc/networking-guide/section_networking_adv_features.xml:640(td) ./doc/networking-guide/section_networking_adv_features.xml:718(td) ./doc/networking-guide/section_networking_adv_features.xml:881(td) ./doc/networking-guide/section_networking_adv_features.xml:1003(td) ./doc/networking-guide/section_networking_adv_features.xml:1072(td) ./doc/networking-guide/section_networking_adv_features.xml:1231(td) ./doc/networking-guide/section_networking_adv_features.xml:1609(td) -msgid "tenant_id" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:292(td) -msgid "Owner of the router. Only admin users can specify a tenant_id other than its own." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:296(td) -msgid "external_gateway_info" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:297(td) -msgid "dict contain 'network_id' key-value pair" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:298(td) ./doc/networking-guide/section_networking_adv_features.xml:351(td) ./doc/networking-guide/section_networking_adv_features.xml:358(td) -msgid "Null" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:299(td) -msgid "External network that this router connects to for gateway services (for example, NAT)" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:305(caption) -msgid "Floating IP" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:323(td) -msgid "UUID for the floating IP." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:326(td) -msgid "floating_ip_address" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:327(td) ./doc/networking-guide/section_networking_adv_features.xml:357(td) -msgid "string (IP address)" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:328(td) ./doc/networking-guide/section_networking_adv_features.xml:672(td) ./doc/networking-guide/section_networking_adv_features.xml:903(td) -msgid "allocated by Networking" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:329(td) -msgid "The external network IP address available to be mapped to an internal IP address." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:333(td) -msgid "floating_network_id" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:337(para) -msgid "The network indicating the set of subnets from which the floating IP should be allocated" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:342(td) -msgid "router_id" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:345(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/networking-guide/section_networking_adv_features.xml:349(td) -msgid "port_id" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:352(td) -msgid "Indicates the internal Networking port associated with the external floating IP." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:356(td) -msgid "fixed_ip_address" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:359(td) -msgid "Indicates the IP address on the internal port that the floating IP maps to (since Networking ports might have more than one IP address)." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:367(td) -msgid "Owner of the Floating IP. Only admin users can specify a tenant_id other than its own." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:375(title) ./doc/networking-guide/section_networking_adv_features.xml:383(caption) ./doc/networking-guide/section_networking_adv_features.xml:1677(caption) -msgid "Basic L3 operations" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:376(para) -msgid "External networks are visible to all users. However, the default policy settings enable only administrative users to create, update, and delete external networks." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:379(para) -msgid "This table shows example commands that enable you to complete basic L3 operations:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:388(th) ./doc/networking-guide/section_networking_adv_features.xml:737(th) ./doc/networking-guide/section_networking_adv_features.xml:1249(th) ./doc/networking-guide/section_networking_adv_features.xml:1682(th) -msgid "Operation" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:389(th) ./doc/networking-guide/section_networking_adv_features.xml:738(th) ./doc/networking-guide/section_networking_adv_features.xml:1250(th) ./doc/networking-guide/section_networking_adv_features.xml:1683(th) -msgid "Command" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:395(para) -msgid "Creates external networks." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:404(para) -msgid "Lists external networks." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:412(para) -msgid "Creates an internal-only router that connects to multiple L2 networks privately." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:421(replaceable) -msgid "SUBNET1_UUID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:422(replaceable) -msgid "SUBNET2_UUID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:427(para) -msgid "Connects a router to an external network, which enables that router to act as a NAT gateway for external connectivity." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:431(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:488(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:498(replaceable) -msgid "EXT_NET_ID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:432(para) -msgid "The router obtains an interface with the gateway_ip address of the subnet and this interface is attached to a port on the L2 Networking network associated with the subnet. The router also gets a gateway interface to the specified external network. This provides SNAT connectivity to the external network as well as support for floating IPs allocated on that external networks. Commonly an external network maps to a network in the provider" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:443(para) -msgid "Lists routers." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:451(para) -msgid "Shows information for a specified router." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:454(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:462(replaceable) -msgid "ROUTER_ID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:459(para) -msgid "Shows all internal interfaces for a router." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:463(replaceable) -msgid "ROUTER_NAME" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:468(para) -msgid "Identifies the PORT_ID that represents the VM NIC to which the floating IP should map." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:472(replaceable) -msgid "INSTANCE_ID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:473(para) -msgid "This port must be on an Networking subnet that is attached to a router uplinked to the external network 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/networking-guide/section_networking_adv_features.xml:484(para) -msgid "Creates a floating IP address and associates it with a port." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:489(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:522(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:530(replaceable) -msgid "FLOATING_IP_ID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:489(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:498(replaceable) -msgid "INTERNAL_VM_PORT_ID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:494(para) -msgid "Creates a floating IP address, and associates it with a port, in a single step." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:503(para) -msgid "Lists floating IPs." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:511(para) -msgid "Finds floating IP for a specified VM port." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:519(para) -msgid "Disassociates a floating IP address." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:527(para) -msgid "Deletes the floating IP address." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:535(para) -msgid "Clears the gateway." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:543(para) -msgid "Removes the interfaces from the router." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:546(replaceable) -msgid "SUBNET_ID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:551(para) -msgid "Deletes the router." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:563(title) -msgid "Security groups" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:564(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/networking-guide/section_networking_adv_features.xml:567(para) -msgid "When a port is created in Networking it is associated with a security group. If a security group is not specified the port is associated with a 'default' security group. By default, this group drops all ingress traffic and allows all egress. Rules can be added to this group in order to change the behaviour." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:571(para) -msgid "To use the Compute security group APIs or use Compute to orchestrate the creation of ports for instances on specific security groups, you must complete additional configuration. You must configure the /etc/nova/nova.conf file and set the security_group_api=neutron option on every node that runs nova-compute and nova-api. After you make this change, restart nova-api and nova-compute to pick up this change. Then, you can use both the Compute and OpenStack Network security group APIs at the same time." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:583(para) -msgid "To use the Compute security group API with Networking, the Networking plug-in must implement the security group API. The following plug-ins currently implement this: ML2, Open vSwitch, Linux Bridge, NEC, and VMware NSX." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:589(para) -msgid "You must configure the correct firewall driver in the securitygroup section of the plug-in/agent configuration file. Some plug-ins and agents, such as Linux Bridge Agent and Open vSwitch Agent, use the no-operation driver as the default, which results in non-working security groups." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:596(para) -msgid "When using the security group API through Compute, security groups are applied to all ports on an instance. The reason for this is that Compute security group APIs are instances based unlike Networking, which is port based." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:604(title) -msgid "Security group API abstractions" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:606(caption) -msgid "Security group attributes" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:624(td) -msgid "UUID for the security group." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:630(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/networking-guide/section_networking_adv_features.xml:634(td) ./doc/networking-guide/section_networking_adv_features.xml:894(td) ./doc/networking-guide/section_networking_adv_features.xml:1016(td) ./doc/networking-guide/section_networking_adv_features.xml:1085(td) ./doc/networking-guide/section_networking_adv_features.xml:1603(td) -msgid "description" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:637(td) -msgid "Human-readable description of a security group." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:643(td) -msgid "Owner of the security group. Only admin users can specify a tenant_id other than their own." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:649(caption) -msgid "Security group rules" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:667(td) -msgid "UUID for the security group rule." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:670(td) -msgid "security_group_id" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:671(td) ./doc/networking-guide/section_networking_adv_features.xml:713(td) -msgid "uuid-str or Integer" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:673(td) -msgid "The security group to associate rule with." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:676(td) ./doc/networking-guide/section_networking_adv_features.xml:1638(td) -msgid "direction" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:679(td) -msgid "The direction the traffic is allow (ingress/egress) from a VM." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:682(td) ./doc/networking-guide/section_networking_adv_features.xml:919(td) -msgid "protocol" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:685(td) -msgid "IP Protocol (icmp, tcp, udp, and so on)." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:688(td) -msgid "port_range_min" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:691(td) -msgid "Port at start of range" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:694(td) -msgid "port_range_max" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:697(td) -msgid "Port at end of range" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:700(td) -msgid "ethertype" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:703(td) -msgid "ethertype in L2 packet (IPv4, IPv6, and so on)" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:706(td) ./doc/networking-guide/section_networking_adv_features.xml:1661(td) -msgid "remote_ip_prefix" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:707(td) -msgid "string (IP cidr)" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:709(td) -msgid "CIDR for address range" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:712(td) -msgid "remote_group_id" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:714(td) -msgid "allocated by Networking or Compute" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:715(td) -msgid "Source security group to apply to rule." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:721(td) -msgid "Owner of the security group rule. Only admin users can specify a tenant_id other than its own." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:728(title) ./doc/networking-guide/section_networking_adv_features.xml:732(caption) -msgid "Basic security group operations" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:729(para) -msgid "This table shows example neutron commands that enable you to complete basic security group operations:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:744(para) -msgid "Creates a security group for our web servers." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:752(para) -msgid "Lists security groups." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:760(para) -msgid "Creates a security group rule to allow port 80 ingress." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:763(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:787(replaceable) -msgid "SECURITY_GROUP_UUID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:768(para) -msgid "Lists security group rules." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:776(para) -msgid "Deletes a security group rule." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:779(replaceable) -msgid "SECURITY_GROUP_RULE_UUID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:784(para) -msgid "Deletes a security group." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:792(para) -msgid "Creates a port and associates two security groups." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:795(replaceable) -msgid "SECURITY_GROUP_ID1" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:795(replaceable) -msgid "SECURITY_GROUP_ID2" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:795(replaceable) -msgid "NETWORK_ID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:800(para) -msgid "Removes security groups from a port." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:803(replaceable) -msgid "PORT_ID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:812(title) -msgid "Basic Load-Balancer-as-a-Service operations" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:814(para) -msgid "The Load-Balancer-as-a-Service (LBaaS) API provisions and configures load balancers. The Havana release offers a reference implementation that is based on the HAProxy software load balancer." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:818(para) -msgid "This list shows example neutron commands that enable you to complete basic LBaaS operations:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:822(para) -msgid "Creates a load balancer pool by using specific provider." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:823(para) -msgid "--provider is an optional argument. If not used, the pool is created with default provider for LBaaS service. You should configure the default provider in the [service_providers] section of neutron.conf file. If no default provider is specified for LBaaS, the --provider option is required for pool creation." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:829(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:848(replaceable) -msgid "SUBNET_UUID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:829(replaceable) -msgid "PROVIDER_NAME" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:829(parameter) -msgid "--provider " -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:832(para) -msgid "Associates two web servers with pool." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:833(replaceable) -msgid "WEBSERVER1_IP" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:834(replaceable) -msgid "WEBSERVER2_IP" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:837(para) -msgid "Creates a health monitor that checks to make sure our instances are still running on the specified protocol-port." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:842(para) -msgid "Associates a health monitor with pool." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:843(replaceable) -msgid "HEALTHMONITOR_UUID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:846(para) -msgid "Creates a virtual IP (VIP) address that, when accessed through the load balancer, directs the requests to one of the pool members." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:854(title) ./doc/networking-guide/ch_advanced.xml:15(title) -msgid "Firewall-as-a-Service" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:855(para) -msgid "The Firewall-as-a-Service (FWaaS) API is an experimental API that enables early adopters and vendors to test their networking implementations." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:858(title) -msgid "Firewall-as-a-Service API abstractions" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:860(caption) -msgid "Firewall rules" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:878(td) -msgid "UUID for the firewall rule." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:884(td) -msgid "Owner of the firewall rule. Only admin users can specify a tenant_id other than its own." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:891(td) -msgid "Human readable name for the firewall rule (255 characters limit)." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:897(td) -msgid "Human-readable description for the firewall rule (1024 characters limit)." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:901(td) ./doc/networking-guide/section_networking_adv_features.xml:1128(td) -msgid "firewall_policy_id" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:902(td) ./doc/networking-guide/section_networking_adv_features.xml:1129(td) -msgid "uuid-str or None" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:904(td) -msgid "This is a read-only attribute that gets populated with the UUID of the firewall policy when this firewall rule is associated with a firewall policy. A firewall rule can be associated with only one firewall policy at a time. However, the association can be changed to a different firewall policy." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:911(td) ./doc/networking-guide/section_networking_adv_features.xml:1023(td) -msgid "shared" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:912(td) ./doc/networking-guide/section_networking_adv_features.xml:973(td) ./doc/networking-guide/section_networking_adv_features.xml:1024(td) ./doc/networking-guide/section_networking_adv_features.xml:1039(td) ./doc/networking-guide/section_networking_adv_features.xml:1093(td) ./doc/networking-guide/section_networking_adv_features.xml:1194(td) ./doc/networking-guide/section_networking_adv_features.xml:1654(td) -msgid "Boolean" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:913(td) ./doc/networking-guide/section_networking_adv_features.xml:975(literal) ./doc/networking-guide/section_networking_adv_features.xml:1025(td) ./doc/networking-guide/section_networking_adv_features.xml:1040(td) ./doc/networking-guide/section_networking_adv_features.xml:1449(td) ./doc/networking-guide/section_networking_adv_features.xml:1655(td) -msgid "False" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:914(td) -msgid "When set to True makes this firewall rule visible to tenants other than its owner and it can be used in firewall policies not owned by its tenant." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:922(td) -msgid "IP protocol (icmp, tcp, udp, None)." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:925(td) -msgid "ip_version" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:926(td) -msgid "Integer or String" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:927(td) -msgid "4" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:928(td) -msgid "IP version (4, 6)." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:931(td) -msgid "source_ip_address" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:932(td) ./doc/networking-guide/section_networking_adv_features.xml:938(td) -msgid "String (IP address or CIDR)" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:934(td) -msgid "Source IP address or CIDR." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:937(td) -msgid "destination_ip_address" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:940(td) -msgid "Destination IP address or CIDR." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:943(td) -msgid "source_port" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:944(td) ./doc/networking-guide/section_networking_adv_features.xml:951(td) -msgid "Integer or String (either as a single port number or in the format of a ':' separated range)" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:947(td) -msgid "Source port number or a range." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:950(td) -msgid "destination_port" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:954(td) -msgid "Destination port number or a range." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:957(td) -msgid "position" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:960(td) -msgid "This is a read-only attribute that gets assigned to this rule when the rule is associated with a firewall policy. It indicates the position of this rule in that firewall policy." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:965(td) ./doc/networking-guide/section_networking_adv_features.xml:1516(td) -msgid "action" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:967(td) -msgid "deny" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:968(td) -msgid "Action to be performed on the traffic matching the rule (allow, deny)." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:972(td) -msgid "enabled" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:975(td) -msgid "When set to , disables this rule in the firewall policy. Facilitates selectively turning off rules without having to disassociate the rule from the firewall policy." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:982(caption) -msgid "Firewall policies" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1000(td) -msgid "UUID for the firewall policy." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1006(td) -msgid "Owner of the firewall policy. Only admin users can specify a tenant_id other their own." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1013(td) -msgid "Human readable name for the firewall policy (255 characters limit)." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1019(td) -msgid "Human readable description for the firewall policy (1024 characters limit)." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1026(td) -msgid "When set to True, the command makes this firewall policy visible to tenants other than its owner and can be used to associate with firewalls not owned by its tenant." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1031(td) -msgid "firewall_rules" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1032(td) -msgid "List of uuid-str or None" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1034(td) -msgid "This is an ordered list of firewall rule UUIDs. The firewall applies the rules in the order in which they appear in this list." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1038(td) -msgid "audited" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1041(td) -msgid "When set to True by the policy owner, the command indicates that the firewall policy has been audited. This attribute is meant to aid in the firewall policy audit work flows. Each time the firewall policy or the associated firewall rules are changed, this attribute is set to False and must be explicitly set to True through an update operation." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1051(caption) ./doc/networking-guide/section_intro-firewalls.xml:11(title) -msgid "Firewalls" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1069(td) -msgid "UUID for the firewall." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1075(td) -msgid "Owner of the firewall. Only admin users can specify a tenant_id other than its own." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1082(td) -msgid "Human readable name for the firewall (255 characters limit)." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1088(td) -msgid "Human readable description for the firewall (1024 characters limit)." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1095(td) -msgid "The administrative state of the firewall. If False (down), the firewall does not forward any packets." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1103(para) -msgid "Indicates whether the firewall is currently operational. Possible values include:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1107(para) -msgid "ACTIVE" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1110(para) -msgid "DOWN" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1113(para) -msgid "PENDING_CREATE" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1116(para) -msgid "PENDING_UPDATE" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1119(para) -msgid "PENDING_DELETE" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1122(para) -msgid "ERROR" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1131(td) -msgid "The firewall policy UUID that this firewall is associated with. This firewall implements the rules contained in the firewall policy represented by this UUID." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1141(title) -msgid "Plug-in specific extensions" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1143(para) -msgid "Each vendor can choose to implement additional API extensions to the core API. This section describes the extensions for each plug-in." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1146(title) -msgid "VMware NSX extensions" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1147(para) -msgid "These sections explain NSX plug-in extensions." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1149(title) -msgid "VMware NSX QoS extension" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1150(para) -msgid "The VMware NSX QoS extension rate-limits network ports to guarantee a specific amount of bandwidth for each port. This extension, by default, is only accessible by a tenant with an admin role but is configurable through the policy.json file. To use this extension, create a queue and specify the min/max bandwidth rates (kbps) and optionally set the QoS Marking and DSCP value (if your network fabric uses these values to make forwarding decisions). Once created, you can associate a queue with a network. Then, when ports are created on that network they are automatically created and associated with the specific queue size that was associated with the network. Because one size queue for a every port on a network might not be optimal, a scaling factor from the nova flavor 'rxtx_factor' is passed in from Compute when creating the port to scale the queue." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1162(para) -msgid "Lastly, if you want to set a specific baseline QoS policy for the amount of bandwidth a single port can use (unless a network queue is specified with the network a port is created on) a default queue can be created in Networking which then causes ports created to be associated with a queue of that size times the rxtx scaling factor. Note that after a network or default queue is specified, queues are added to ports that are subsequently created but are not added to existing ports." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1170(title) -msgid "VMware NSX QoS API abstractions" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1172(caption) -msgid "VMware NSX QoS attributes" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1190(td) -msgid "UUID for the QoS queue." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1193(td) -msgid "default" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1195(td) -msgid "False by default" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1196(td) -msgid "If True, ports are created with this queue size unless the network port is created or associated with a queue at port creation time." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1204(td) -msgid "Name for QoS queue." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1207(td) -msgid "min" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1209(td) ./doc/networking-guide/section_networking_adv_features.xml:1227(td) -msgid "0" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1210(td) -msgid "Minimum Bandwidth Rate (kbps)." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1213(td) -msgid "max" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1216(td) -msgid "Maximum Bandwidth Rate (kbps)." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1219(td) -msgid "qos_marking" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1221(td) -msgid "untrusted by default" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1222(td) -msgid "Whether QoS marking should be trusted or untrusted." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1225(td) -msgid "dscp" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1228(td) -msgid "DSCP Marking value." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1234(td) -msgid "The owner of the QoS queue." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1240(title) ./doc/networking-guide/section_networking_adv_features.xml:1244(caption) -msgid "Basic VMware NSX QoS operations" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1241(para) -msgid "This table shows example neutron commands that enable you to complete basic queue operations:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1256(para) -msgid "Creates QoS queue (admin-only)." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1264(para) -msgid "Associates a queue with a network." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1267(replaceable) -msgid "QUEUE_ID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1272(para) -msgid "Creates a default system queue." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1280(para) -msgid "Lists QoS queues." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1288(para) -msgid "Deletes a QoS queue." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1291(replaceable) -msgid "QUEUE_ID_OR_NAME" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1299(title) -msgid "VMware NSX provider networks extension" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1300(para) -msgid "Provider networks can be implemented in different ways by the underlying NSX platform." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1302(para) -msgid "The FLAT and VLAN network types use bridged transport connectors. These network types enable the attachment of large number of ports. To handle the increased scale, the NSX plug-in can back a single OpenStack Network with a chain of NSX logical switches. You can specify the maximum number of ports on each logical switch in this chain on the max_lp_per_bridged_ls parameter, which has a default value of 5,000." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1309(para) -msgid "The recommended value for this parameter varies with the NSX version running in the back-end, as shown in the following table." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1312(caption) -msgid "Recommended values for max_lp_per_bridged_ls" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1317(td) -msgid "NSX version" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1318(td) -msgid "Recommended Value" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1323(td) -msgid "2.x" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1324(td) -msgid "64" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1327(td) -msgid "3.0.x" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1328(td) ./doc/networking-guide/section_networking_adv_features.xml:1332(td) -msgid "5,000" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1331(td) -msgid "3.1.x" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1335(td) -msgid "3.2.x" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1336(td) -msgid "10,000" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1340(para) -msgid "In addition to these network types, the NSX plug-in also supports a special l3_ext network type, which maps external networks to specific NSX gateway services as discussed in the next section." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1345(title) -msgid "VMware NSX L3 extension" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1346(para) -msgid "NSX exposes its L3 capabilities through gateway services which are usually configured out of band from OpenStack. To use NSX with L3 capabilities, first create an L3 gateway service in the NSX Manager. Next, in /etc/neutron/plugins/vmware/nsx.ini set default_l3_gw_service_uuid to this value. By default, routers are mapped to this gateway service." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1353(title) -msgid "VMware NSX L3 extension operations" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1354(para) -msgid "Create external network and map it to a specific NSX gateway service:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1357(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:1360(replaceable) -msgid "L3_GATEWAY_SERVICE_UUID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1358(para) -msgid "Terminate traffic on a specific VLAN from a NSX gateway service:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1360(replaceable) -msgid "VLAN_ID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1364(title) -msgid "Operational status synchronization in the VMware NSX plug-in" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1365(para) -msgid "Starting with the Havana release, the VMware NSX plug-in provides an asynchronous mechanism for retrieving the operational status for neutron resources from the NSX back-end; this applies to network, port and router resources." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1369(para) -msgid "The back-end is polled periodically and the status for every resource is retrieved; then the status in the Networking database is updated only for the resources for which a status change occurred. As operational status is now retrieved asynchronously, performance for GET operations is consistently improved." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1374(para) -msgid "Data to retrieve from the back-end are divided in chunks in order to avoid expensive API requests; this is achieved leveraging NSX APIs response paging capabilities. The minimum chunk size can be specified using a configuration option; the actual chunk size is then determined dynamically according to: total number of resources to retrieve, interval between two synchronization task runs, minimum delay between two subsequent requests to the NSX back-end." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1380(para) -msgid "The operational status synchronization can be tuned or disabled using the configuration options reported in this table; it is however worth noting that the default values work fine in most cases." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1384(caption) -msgid "Configuration options for tuning operational status synchronization in the NSX plug-in" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1393(th) -msgid "Option name" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1394(th) -msgid "Group" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1395(th) -msgid "Default value" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1396(th) -msgid "Type and constraints" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1397(th) -msgid "Notes" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1402(literal) ./doc/networking-guide/section_networking_adv_features.xml:1408(literal) ./doc/networking-guide/section_networking_adv_features.xml:1427(literal) ./doc/networking-guide/section_networking_adv_features.xml:1440(literal) -msgid "state_sync_interval" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1403(literal) ./doc/networking-guide/section_networking_adv_features.xml:1415(literal) ./doc/networking-guide/section_networking_adv_features.xml:1424(literal) ./doc/networking-guide/section_networking_adv_features.xml:1435(literal) ./doc/networking-guide/section_networking_adv_features.xml:1448(literal) -msgid "nsx_sync" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1404(td) -msgid "120 seconds" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1405(td) ./doc/networking-guide/section_networking_adv_features.xml:1437(td) -msgid "Integer; no constraint." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1406(td) -msgid "Interval in seconds between two run of the synchronization task. If the synchronization task takes more than seconds to execute, a new instance of the task is started as soon as the other is completed. Setting the value for this option to 0 will disable the synchronization task." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1414(literal) ./doc/networking-guide/section_networking_adv_features.xml:1419(literal) -msgid "max_random_sync_delay" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1416(td) -msgid "0 seconds" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1417(literal) ./doc/networking-guide/section_networking_adv_features.xml:1423(literal) ./doc/networking-guide/section_networking_adv_features.xml:1441(literal) -msgid "min_sync_req_delay" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1417(td) -msgid "Integer. Must not exceed " -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1418(td) -msgid "When different from zero, a random delay between 0 and will be added before processing the next chunk." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1425(td) -msgid "10 seconds" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1426(td) -msgid "Integer. Must not exceed ." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1428(td) -msgid "The value of this option can be tuned according to the observed load on the NSX controllers. Lower values will result in faster synchronization, but might increase the load on the controller cluster." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1434(literal) ./doc/networking-guide/section_networking_adv_features.xml:1443(literal) -msgid "min_chunk_size" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1436(td) -msgid "500 resources" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1438(td) -msgid "Minimum number of resources to retrieve from the back-end for each synchronization chunk. The expected number of synchronization chunks is given by the ratio between and . This size of a chunk might increase if the total number of resources is such that more than resources must be fetched in one chunk with the current number of chunks." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1447(literal) -msgid "always_read_status" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1450(td) -msgid "Boolean; no constraint." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1452(literal) -msgid "GET" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1451(td) -msgid "When this option is enabled, the operational status will always be retrieved from the NSX back-end ad every request. In this case it is advisable to disable the synchronization task." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1458(para) -msgid "When running multiple OpenStack Networking server instances, the status synchronization task should not run on every node; doing so sends unnecessary traffic to the NSX back-end and performs unnecessary DB operations. Set the configuration option to a non-zero value exclusively on a node designated for back-end status synchronization." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1464(para) -msgid "The fields=status parameter in Networking API requests always triggers an explicit query to the NSX back end, even when you enable asynchronous state synchronization. For example, GET /v2.0/networks/NET_ID?fields=status&fields=name." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1471(title) -msgid "Big Switch plug-in extensions" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1472(para) -msgid "This section explains the Big Switch neutron plug-in-specific extension." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1474(title) -msgid "Big Switch router rules" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1475(para) -msgid "Big Switch allows router rules to be added to each tenant router. These rules can be used to enforce routing policies such as denying traffic between subnets or traffic to external networks. By enforcing these at the router level, network segmentation policies can be enforced across many VMs that have differing security groups." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1481(title) -msgid "Router rule attributes" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1482(para) -msgid "Each tenant router has a set of router rules associated with it. Each router rule has the attributes in this table. Router rules and their attributes can be set using the command, through the horizon interface or the Networking API." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1487(caption) -msgid "Big Switch Router rule attributes" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1495(th) -msgid "Required" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1496(th) -msgid "Input Type" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1502(td) -msgid "source" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1503(td) ./doc/networking-guide/section_networking_adv_features.xml:1510(td) ./doc/networking-guide/section_networking_adv_features.xml:1517(td) -msgid "Yes" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1504(td) ./doc/networking-guide/section_networking_adv_features.xml:1511(td) -msgid "A valid CIDR or one of the keywords 'any' or 'external'" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1505(td) -msgid "The network that a packet's source IP must match for the rule to be applied" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1509(td) -msgid "destination" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1512(td) -msgid "The network that a packet's destination IP must match for the rule to be applied" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1518(td) -msgid "'permit' or 'deny'" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1519(td) -msgid "Determines whether or not the matched packets will allowed to cross the router" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1523(td) -msgid "nexthop" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1524(td) -msgid "No" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1526(literal) -msgid "1.1.1.1+1.1.1.2" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1525(td) -msgid "A plus-separated (+) list of next-hop IP addresses. For example, ." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1527(td) -msgid "Overrides the default virtual router used to handle traffic for packets that match the rule" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1534(title) -msgid "Order of rule processing" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1535(para) -msgid "The order of router rules has no effect. Overlapping rules are evaluated using longest prefix matching on the source and destination fields. The source field is matched first so it always takes higher precedence over the destination field. In other words, longest prefix matching is used on the destination field only if there are multiple matching rules with the same source." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1543(title) -msgid "Big Switch router rules operations" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1544(para) -msgid "Router rules are configured with a router update operation in OpenStack Networking. The update overrides any previous rules so all rules must be provided at the same time." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1547(para) -msgid "Update a router with rules to permit traffic by default but block traffic from external networks to the 10.10.10.0/24 subnet:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1549(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:1553(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:1557(replaceable) -msgid "ROUTER_UUID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1552(para) -msgid "Specify alternate next-hop addresses for a specific subnet:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1556(para) -msgid "Block traffic between two subnets while allowing everything else:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1565(title) -msgid "L3 metering" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1566(para) -msgid "The L3 metering API extension enables administrators to configure IP ranges and assign a specified label to them to be able to measure traffic that goes through a virtual router." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1569(para) -msgid "The L3 metering extension is decoupled from the technology that implements the measurement. Two abstractions have been added: One is the metering label that can contain metering rules. Because a metering label is associated with a tenant, all virtual routers in this tenant are associated with this label." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1574(title) -msgid "L3 metering API abstractions" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1576(caption) -msgid "Label" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1594(td) -msgid "UUID for the metering label." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1600(td) -msgid "Human-readable name for the metering label. Might not be unique." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1606(td) -msgid "The optional description for the metering label." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1612(td) -msgid "Owner of the metering label." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1617(caption) -msgid "Rules" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1635(td) -msgid "UUID for the metering rule." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1639(td) -msgid "String (Either ingress or egress)" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1640(td) -msgid "ingress" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1641(td) -msgid "The direction in which metering rule is applied, either ingress or egress." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1645(td) -msgid "metering_label_id" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1649(para) -msgid "The metering label ID to associate with this metering rule." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1653(td) -msgid "excluded" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1656(td) -msgid "Specify whether the remote_ip_prefix will be excluded or not from traffic counters of the metering label (for example, to not count the traffic of a specific IP address of a range)." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1662(td) -msgid "String (CIDR)" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1664(td) -msgid "Indicates remote IP prefix to be associated with this metering rule." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1672(title) -msgid "Basic L3 metering operations" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1673(para) -msgid "Only administrators can manage the L3 metering labels and rules." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1674(para) -msgid "This table shows example commands that enable you to complete basic L3 metering operations:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1689(para) -msgid "Creates a metering label." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1692(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:1709(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:1718(replaceable) -msgid "LABEL1" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1692(replaceable) -msgid "DESCRIPTION_LABEL1" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1697(para) -msgid "Lists metering labels." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1705(para) -msgid "Shows information for a specified label." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1708(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:1717(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:1726(replaceable) -msgid "LABEL_UUID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1714(para) -msgid "Deletes a metering label." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1723(para) -msgid "Creates a metering rule." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1726(replaceable) ./doc/networking-guide/section_networking_adv_agent.xml:259(replaceable) -msgid "CIDR" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1726(replaceable) -msgid "DIRECTION" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1727(para) ./doc/networking-guide/section_networking_adv_agent.xml:196(para) ./doc/networking-guide/section_networking_adv_agent.xml:260(para) -msgid "For example:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1734(para) -msgid "Lists metering all label rules." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1742(para) -msgid "Shows information for a specified label rule." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1745(replaceable) ./doc/networking-guide/section_networking_adv_features.xml:1751(replaceable) -msgid "RULE_UUID" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_features.xml:1749(td) -msgid "Deletes a metering label rule." -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/networking-guide/ch_deployment.xml:17(None) -msgid "@@image: '../common/figures/Neutron-PhysNet-Diagram.png'; md5=ea581fd58c57da1a6c9512b82027a195" -msgstr "" - -#: ./doc/networking-guide/ch_deployment.xml:7(title) -msgid "Deployment" -msgstr "" - -#: ./doc/networking-guide/ch_deployment.xml:8(para) -msgid "OpenStack Networking provides an extreme amount of flexibility when deploying networking in support of a compute environment. As a result, the exact layout of a deployment will depend on a combination of expected workloads, expected scale, and available hardware." -msgstr "" - -#: ./doc/networking-guide/ch_deployment.xml:20(para) -msgid "For demonstration purposes, this chapter concentrates on a networking deployment that consists of these types of nodes:" -msgstr "" - -#: ./doc/networking-guide/ch_deployment.xml:26(para) -msgid "Service node: The service node exposes the networking API to clients and handles incoming requests before forwarding them to a message queue. Requests are then actioned by the other nodes. The service node hosts both the networking service itself and the active networking plug-in. In environments that use controller nodes to host the client-facing APIs, and schedulers for all services, the controller node would also fulfill the role of service node as it is applied in this chapter." -msgstr "" - -#: ./doc/networking-guide/ch_deployment.xml:38(para) -msgid "Network node: The network node handles the majority of the networking workload. It hosts the DHCP agent, the Layer-3 (L3) agent, the Layer-2 (L2) agent, and the metadata proxy. In addition to plug-ins that require an agent, it runs an instance of the plug-in agent (as do all other systems that handle data packets in an environment where such plug-ins are in use). Both the Open vSwitch and Linux Bridge mechanism drivers include an agent." -msgstr "" - -#: ./doc/networking-guide/ch_deployment.xml:49(para) -msgid "Compute node: The compute node hosts the compute instances themselves. To connect compute instances to the networking services, compute nodes must also run the L2 agent. Like all other systems that handle data packets it must also run an instance of the plug-in agent." -msgstr "" - -#: ./doc/networking-guide/section_architecture-plug-in.xml:11(title) -msgid "Plug-ins" -msgstr "" - -#. This section has not yet been edited. LKB -#: ./doc/networking-guide/section_architecture-plug-in.xml:13(para) -msgid "The legacy networking (nova-network) implementation assumed a basic model of isolation through Linux VLANs and IP tables. Networking introduces support for vendor plug-ins, which offer a custom back-end implementation of the Networking API. A plugin can use a variety of technologies to implement the logical API requests. Some networking plug-ins 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/networking-guide/section_intro-firewalls.xml:13(para) -msgid "A firewall is a network security system that controls the network traffic using a set of rules. Firewalls can be implemented in both hardware and software, or a mix of the two. For example, a firewall might disallow traffic originating from a range of IP addresses or only allow traffic on specific ports. Firewalls are often used between internal networks, where data is trusted, and on external networks such as the Internet." -msgstr "" - -#: ./doc/networking-guide/section_intro-firewalls.xml:20(para) -msgid "Many firewalls incorporate Network Address Translation (NAT). Network address translation masks the IP addresses of the devices on the internal network, so that external devices see only the single public IP address of the device hosting the firewall." -msgstr "" - -#: ./doc/networking-guide/section_intro-switches.xml:11(title) -msgid "Switches" -msgstr "" - -#: ./doc/networking-guide/section_intro-switches.xml:13(para) -msgid "A switch is a device that is used to connect devices on a network. Switches forward packets on to other devices, using packet switching to pass data along only to devices that need to receive it. Switches operate at Layer 2 of the OSI model." -msgstr "" - -#: ./doc/networking-guide/ch_troubleshooting.xml:11(title) -msgid "Troubleshoot OpenStack Networking" -msgstr "" - -#: ./doc/networking-guide/ch_troubleshooting.xml:12(para) -msgid "These sections provide additional troubleshooting information for OpenStack Networking (neutron). For nova-network troubleshooting information, see the OpenStack Operations Guide." -msgstr "" - -#: ./doc/networking-guide/ch_troubleshooting.xml:18(title) -msgid "Visualize OpenStack Networking service traffic in the cloud" -msgstr "" - -#: ./doc/networking-guide/ch_troubleshooting.xml:24(link) ./doc/networking-guide/ch_troubleshooting.xml:33(link) ./doc/networking-guide/ch_troubleshooting.xml:42(link) ./doc/networking-guide/ch_troubleshooting.xml:51(link) -msgid "http://docs.openstack.org" -msgstr "" - -#: ./doc/networking-guide/ch_troubleshooting.xml:28(title) -msgid "Troubleshoot network namespace issues" -msgstr "" - -#: ./doc/networking-guide/ch_troubleshooting.xml:37(title) -msgid "Troubleshoot Open vSwitch" -msgstr "" - -#: ./doc/networking-guide/ch_troubleshooting.xml:46(title) -msgid "Debug DNS issues" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_operational_features.xml:7(title) -msgid "Advanced operational features" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_operational_features.xml:9(title) -msgid "Logging settings" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_operational_features.xml:10(para) -msgid "Networking components use Python logging module to do logging. Logging configuration can be provided in neutron.conf or as command-line options. Command options override ones in neutron.conf." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_operational_features.xml:15(para) -msgid "To configure logging for Networking components, use one of these methods:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_operational_features.xml:19(para) -msgid "Provide logging settings in a logging configuration file." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_operational_features.xml:21(para) -msgid "See Python logging how-to to learn more about logging." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_operational_features.xml:25(para) -msgid "Provide logging setting in neutron.conf" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_operational_features.xml:50(title) -msgid "Notifications" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_operational_features.xml:51(para) -msgid "Notifications can be sent when Networking resources such as network, subnet and port are created, updated or deleted." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_operational_features.xml:55(title) -msgid "Notification options" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_operational_features.xml:56(para) -msgid "To support DHCP agent, rpc_notifier driver must be set. To set up the notification, edit notification options in neutron.conf:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_operational_features.xml:68(title) -msgid "Setting cases" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_operational_features.xml:70(title) -msgid "Logging and RPC" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_operational_features.xml:71(para) -msgid "These options configure the Networking server to send notifications through logging and RPC. The logging options are described in OpenStack Configuration Reference . RPC notifications go to 'notifications.info' queue bound to a topic exchange defined by 'control_exchange' in neutron.conf." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_operational_features.xml:108(title) -msgid "Multiple RPC topics" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_operational_features.xml:109(para) -msgid "These options configure the Networking server to send notifications to multiple RPC topics. RPC notifications go to 'notifications_one.info' and 'notifications_two.info' queues bound to a topic exchange defined by 'control_exchange' in neutron.conf." -msgstr "" - -#: ./doc/networking-guide/section_intro-layers.xml:11(title) -msgid "Networking layers" -msgstr "" - -#: ./doc/networking-guide/section_intro-layers.xml:13(para) -msgid "Network communication is commonly described in terms of the OSI model. The OSI model is a seven-layer model that describes how various protocols and mechanisms fit together. Each layer depends on the protocols in the layer beneath it." -msgstr "" - -#: ./doc/networking-guide/section_intro-layers.xml:19(term) -msgid "7 Application" -msgstr "" - -#: ./doc/networking-guide/section_intro-layers.xml:21(para) -msgid "The Application layer of the OSI model is the user interface layer. Everything here is application specific. Some examples at this layer which could be Telnet, FTP, email." -msgstr "" - -#: ./doc/networking-guide/section_intro-layers.xml:27(term) -msgid "6 Presentation" -msgstr "" - -#: ./doc/networking-guide/section_intro-layers.xml:29(para) -msgid "Here is where data gets translated from the application into network format and back again. The presentation layer transforms data into a form that the application layer can accept. The presentation layer formats and encrypts data which prevents compatibility problems." -msgstr "" - -#: ./doc/networking-guide/section_intro-layers.xml:37(term) -msgid "5 Session" -msgstr "" - -#: ./doc/networking-guide/section_intro-layers.xml:39(para) -msgid "The Session layer manages connections between applications. It is responsible for session and connection coordination." -msgstr "" - -#: ./doc/networking-guide/section_intro-layers.xml:44(term) -msgid "4 Transport" -msgstr "" - -#: ./doc/networking-guide/section_intro-layers.xml:46(para) -msgid "This layer deals with transporting data usually over TCP or Transmission Control Protocol. TCP enables two hosts to establish, connect, and exchange streams of data together. TCP also guarantees delivery of data and the order in which packets are sent." -msgstr "" - -#: ./doc/networking-guide/section_intro-layers.xml:54(term) -msgid "3 Network" -msgstr "" - -#: ./doc/networking-guide/section_intro-layers.xml:56(para) -msgid "This layer handles transmission for data from node to node. The network layer handles routing, forwarding, addressing, inter-networking, and error handling. Usually this is the IP portion of TCP/IP." -msgstr "" - -#: ./doc/networking-guide/section_intro-layers.xml:63(term) -msgid "2 Data link" -msgstr "" - -#: ./doc/networking-guide/section_intro-layers.xml:65(para) -msgid "The data link layer is where most LAN technologies such as Ethernet live. This layer is divided into two sub layers: MAC (Media Access Control): Handles access to data and permissions to translate it. LLC (Logical Link Control): Manages traffic across the physical layer." -msgstr "" - -#: ./doc/networking-guide/section_intro-layers.xml:74(term) -msgid "1 Physical" -msgstr "" - -#: ./doc/networking-guide/section_intro-layers.xml:76(para) -msgid "The physical layer is the description of the physical media or signals used in networking. Examples include the size of the Ethernet, hubs, or other physical devices used to establish a network." -msgstr "" - -#: ./doc/networking-guide/section_intro-layers.xml:83(para) -msgid "OpenStack Networking is primarily concerned with Layer 2 and Layer 3." -msgstr "" - -#: ./doc/networking-guide/section_intro-layers.xml:85(para) -msgid "Layer-3 protocols include the Internet Protocol Suite, which includes IPv4, IPv6, and the Internet Control Message Protocol (ICMP)." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:5(title) -msgid "Advanced agent options" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:6(para) -msgid "This section describes advanced configuration options for server plug-ins and agents." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:8(title) -msgid "OpenStack Networking server with plug-in" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:9(para) -msgid "This web server runs the OpenStack Networking API Web Server. It loads a plug-in and passes the API calls to the plug-in for processing. The neutron-server service receives one or more configuration files as input. For example:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:13(replaceable) ./doc/networking-guide/section_networking_adv_agent.xml:35(replaceable) ./doc/networking-guide/section_networking_adv_agent.xml:106(replaceable) ./doc/networking-guide/section_networking_adv_agent.xml:152(replaceable) ./doc/networking-guide/section_networking_adv_agent.xml:288(replaceable) -msgid "NEUTRON_CONFIG_FILE" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:13(replaceable) ./doc/networking-guide/section_networking_adv_agent.xml:35(replaceable) -msgid "PLUGIN_CONFIG_FILE" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:14(para) -msgid "The neutron configuration file contains the common neutron configuration options." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:15(para) -msgid "The plug-in configuration file contains the plug-in specific options." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:16(para) -msgid "The plug-in that runs on the service is loaded through the configuration option. In some cases, a plug-in might have an agent that performs the actual networking." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:19(para) -msgid "Most plug-ins require an SQL database. After you install and start the database server, set a password for the root account and delete the anonymous accounts:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:24(para) -msgid "Create a database and user account specifically for plug-in:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:25(replaceable) ./doc/networking-guide/section_networking_adv_agent.xml:28(replaceable) -msgid "DATABASE_NAME" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:26(replaceable) ./doc/networking-guide/section_networking_adv_agent.xml:26(replaceable) ./doc/networking-guide/section_networking_adv_agent.xml:27(replaceable) ./doc/networking-guide/section_networking_adv_agent.xml:27(replaceable) ./doc/networking-guide/section_networking_adv_agent.xml:28(replaceable) -msgid "USER_NAME" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:29(para) -msgid "After this step completes, you can update the settings in the relevant plug-in configuration files. Find the plug-in specific configuration files at $NEUTRON_CONF_DIR/plugins." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:32(para) -msgid "Some plug-ins have an L2 agent that performs the actual networking. That is, the agent attaches the virtual machine NIC to the OpenStack Networking network. Each node should run an L2 agent. Note that the agent receives the following input parameters:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:36(para) -msgid "You must complete these tasks before you can work with the plug-in:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:39(para) -msgid "Ensure that the core plug-in is updated." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:42(para) -msgid "Ensure that the database connection is correctly set." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:45(para) -msgid "The following table shows sample values for the configuration options. Some Linux packages might provide installation utilities that configure these values." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:48(caption) ./doc/networking-guide/section_networking_adv_agent.xml:111(caption) ./doc/networking-guide/section_networking_adv_agent.xml:156(caption) ./doc/networking-guide/section_networking_adv_agent.xml:292(caption) -msgid "Settings" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:51(th) ./doc/networking-guide/section_networking_adv_agent.xml:114(th) ./doc/networking-guide/section_networking_adv_agent.xml:159(th) ./doc/networking-guide/section_networking_adv_agent.xml:295(th) -msgid "Option" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:52(th) ./doc/networking-guide/section_networking_adv_agent.xml:115(th) ./doc/networking-guide/section_networking_adv_agent.xml:160(th) ./doc/networking-guide/section_networking_adv_agent.xml:296(th) -msgid "Value" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:61(td) ./doc/networking-guide/section_networking_adv_agent.xml:82(td) -msgid "core_plugin ($NEUTRON_CONF_DIR/neutron.conf)" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:62(td) -msgid "openvswitch" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:66(code) ./doc/networking-guide/section_networking_adv_agent.xml:87(code) -msgid "[database]" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:65(td) -msgid "connection (in the plugin configuration file, section )" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:67(replaceable) ./doc/networking-guide/section_networking_adv_agent.xml:88(replaceable) -msgid "USERNAME" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:67(replaceable) ./doc/networking-guide/section_networking_adv_agent.xml:88(replaceable) -msgid "PASSWORD" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:67(td) -msgid "mysql://:@localhost/ovs_neutron?charset=utf8" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:70(td) ./doc/networking-guide/section_networking_adv_agent.xml:91(td) -msgid "Plug-in Configuration File" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:71(td) -msgid "$NEUTRON_CONF_DIR/plugins/openvswitch/ovs_neutron_plugin.ini" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:74(td) ./doc/networking-guide/section_networking_adv_agent.xml:95(td) -msgid "Agent" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:75(td) -msgid "neutron-openvswitch-agent" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:83(td) -msgid "linuxbridge" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:86(td) -msgid "connection (in the plug-in configuration file, section )" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:88(td) -msgid "mysql://:@localhost/neutron_linux_bridge?charset=utf8" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:92(td) -msgid "$NEUTRON_CONF_DIR/plugins/linuxbridge/linuxbridge_conf.ini" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:96(td) -msgid "neutron-linuxbridge-agent" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:102(title) -msgid "DHCP agent" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:103(para) -msgid "You can run a DHCP server that allocates IP addresses to virtual machines that run on the network. When a subnet is created, by default, the subnet has DHCP enabled." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:105(para) -msgid "The node that runs the DHCP agent should run:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:106(replaceable) -msgid "DHCP_CONFIG_FILE" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:107(para) -msgid "Currently the DHCP agent uses dnsmasq to perform that static address assignment." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:109(para) -msgid "You must configure a driver that matches the plug-in that runs on the service." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:124(td) ./doc/networking-guide/section_networking_adv_agent.xml:132(td) -msgid "interface_driver ($NEUTRON_CONF_DIR/dhcp_agent.ini)" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:125(td) ./doc/networking-guide/section_networking_adv_agent.xml:170(td) ./doc/networking-guide/section_networking_adv_agent.xml:306(td) -msgid "neutron.agent.linux.interface.OVSInterfaceDriver" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:133(td) ./doc/networking-guide/section_networking_adv_agent.xml:182(td) ./doc/networking-guide/section_networking_adv_agent.xml:314(td) -msgid "neutron.agent.linux.interface.BridgeInterfaceDriver" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:138(title) ./doc/networking-guide/section_networking_adv_agent.xml:207(title) ./doc/networking-guide/section_networking_adv_agent.xml:319(title) -msgid "Namespace" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:139(para) -msgid "By default, the DHCP agent uses Linux network namespaces to support overlapping IP addresses. For information about network namespaces support, see the Limitations section." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:142(para) -msgid "If the Linux installation does not support network namespaces, you must disable network namespaces in the DHCP agent configuration file. The default value of is True." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:149(title) -msgid "L3 agent" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:150(para) -msgid "You can run an L3 agent that enables layer 3 forwarding and floating IP support." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:151(para) -msgid "The node that runs the L3 agent should run:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:152(replaceable) -msgid "L3_CONFIG_FILE" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:153(para) -msgid "You must configure a driver that matches the plug-in that runs on the service. This driver creates the routing interface." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:169(td) ./doc/networking-guide/section_networking_adv_agent.xml:181(td) -msgid "interface_driver ($NEUTRON_CONF_DIR/l3_agent.ini)" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:173(td) ./doc/networking-guide/section_networking_adv_agent.xml:185(td) -msgid "external_network_bridge ($NEUTRON_CONF_DIR/l3_agent.ini)" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:174(td) -msgid "br-ex" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:186(td) -msgid "This field must be empty (or the bridge name for the external network)." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:190(para) -msgid "The L3 agent communicates with the OpenStack Networking server through the OpenStack Networking API, so the following configuration is required:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:194(para) -msgid "OpenStack Identity authentication:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:200(para) -msgid "Administrative user details:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:208(para) -msgid "By default, the L3 agent uses Linux network namespaces to support overlapping IP addresses." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:210(para) -msgid "For information about network namespaces support, see the Limitation section." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:212(para) -msgid "If the Linux installation does not support network namespaces, you must disable network namespaces in the L3 agent configuration file. The default value of is True." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:216(para) -msgid "When you set to False, only one router ID is supported per node." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:218(para) -msgid "Use the configuration option to configure the router:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:223(para) -msgid "To configure it, you must run the OpenStack Networking service, create a router, and set the router ID value to the value in the L3 agent configuration file." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:240(title) -msgid "Multiple external networks" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:241(para) -msgid "Use one of these methods to support multiple external networks:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:244(para) -msgid "Assign multiple subnets to an external network." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:247(para) -msgid "Use multiple floating IP pools." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:250(para) -msgid "The following sections describe these options." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:252(title) -msgid "Assign multiple subnets to an external network" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:253(para) -msgid "This approach leverages the addition of on-link routes, which enables a router to host floating IPs from any subnet on an external network regardless of which subnet the primary router IP address comes from. This method does not require the creation of multiple external networks." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:257(para) -msgid "To add a subnet to the external network, use the following command template:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:259(replaceable) -msgid "EXT_NETWORK_NAME" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:264(title) -msgid "Multiple floating IP pools" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:265(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. You can associate a L3 agent with multiple external networks." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:271(para) -msgid "Before starting a L3 agent, you must update the configuration files with the UUID of the external network." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:273(para) -msgid "To enable the L3 agent to support multiple external networks, edit the l3_agent.ini file and leave the and parameters unset:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:285(title) -msgid "L3 metering agent" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:286(para) -msgid "You can run an L3 metering agent that enables layer 3 traffic metering. In general, you should launch the metering agent on all nodes that run the L3 agent:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:288(replaceable) -msgid "L3_METERING_CONFIG_FILE" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:289(para) -msgid "You must configure a driver that matches the plug-in that runs on the service. The driver adds metering to the routing interface." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:305(td) ./doc/networking-guide/section_networking_adv_agent.xml:313(td) -msgid "interface_driver ($NEUTRON_CONF_DIR/metering_agent.ini)" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:320(para) -msgid "The metering agent and the L3 agent must have the same network namespaces configuration." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:323(para) -msgid "If the Linux installation does not support network namespaces, you must disable network namespaces in the L3 metering configuration file. The default value of the option is True." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:330(title) -msgid "L3 metering driver" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:331(para) -msgid "You must configure any driver that implements the metering abstraction. Currently the only available implementation uses iptables for metering." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:336(title) -msgid "L3 metering service driver" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:337(para) -msgid "To enable L3 metering, you must set the following option in the neutron.conf file on the host that runs neutron-server:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:344(title) -msgid "Limitations" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:347(para) -msgid "No equivalent for nova-network --multi_host option. 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 now support running multiple l3-agent and dhcp-agents with load being split across those agents, but the tight coupling of that scheduling with the location of the VM is not supported in Icehouse. The Juno release is expected to include an exact replacement for the --multi_host option in nova-network." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:357(para) -msgid "Linux network namespace required on nodes running neutron-l3-agent or neutron-dhcp-agent if overlapping IPs are in use. 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/networking-guide/section_networking_adv_agent.xml:369(para) -msgid "Linux kernel 2.6.24 or later (with CONFIG_NET_NS=y in kernel configuration)" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:373(para) -msgid "iproute2 utilities ('ip' command) version 3.1.0 (aka 20111117) or later" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:377(para) -msgid "To check whether your host supports namespaces, run these commands as root:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:381(para) -msgid "If these commands succeed, your platform is likely sufficient to use the dhcp-agent or l3-agent with namespaces. In our experience, Ubuntu 12.04 or later support namespaces as does Fedora 17 and later, but some earlier RHEL platforms do not by default. It might be possible to upgrade the iproute2 package on a platform that does not support namespaces by default." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:387(para) -msgid "If you must disable namespaces, make sure that the neutron.conf file that is used by neutron-server has the following setting:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:391(para) -msgid "Also, ensure that the dhcp_agent.ini and l3_agent.ini files have the following setting:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:395(para) -msgid "If the host does not support namespaces, the neutron-l3-agent and neutron-dhcp-agent should run on different hosts because 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/networking-guide/section_networking_adv_agent.xml:402(para) -msgid "If you run both L3 and DHCP services on the same node, you should enable namespaces to avoid conflicts with routes:" -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:407(para) -msgid "No IPv6 support for L3 agent. The neutron-l3-agent, used by many plug-ins to implement L3 forwarding, supports only IPv4 forwarding. Currently, there are no errors provided if you configure IPv6 addresses via the API." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:415(para) -msgid "ZeroMQ support is experimental. Some agents, including neutron-dhcp-agent, neutron-openvswitch-agent, and neutron-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, issues might occur with ZeroMQ and the dhcp agent." -msgstr "" - -#: ./doc/networking-guide/section_networking_adv_agent.xml:424(para) -msgid "MetaPlugin is experimental. This release includes a MetaPlugin that is intended to support multiple plug-ins at the same time for different API requests, based on the content of those API requests. The core team has not thoroughly reviewed or tested this functionality. Consider this functionality to be experimental until further validation is performed." -msgstr "" - -#: ./doc/networking-guide/section_deployment-scenarios.xml:11(title) -msgid "Scenarios" -msgstr "" - -#: ./doc/networking-guide/section_deployment-scenarios.xml:13(para) -msgid "(provide configuration, diagrams, and flow of communications when launching an instance)" -msgstr "" - -#: ./doc/networking-guide/section_deployment-scenarios.xml:17(para) -msgid "Linux Bridge using VLAN" -msgstr "" - -#: ./doc/networking-guide/section_deployment-scenarios.xml:18(para) -msgid "Linux Bridge using GRE" -msgstr "" - -#: ./doc/networking-guide/section_deployment-scenarios.xml:19(para) -msgid "Linux Bridge using VXLAN" -msgstr "" - -#: ./doc/networking-guide/section_deployment-scenarios.xml:20(para) -msgid "Open vSwitch with VLAN" -msgstr "" - -#: ./doc/networking-guide/section_deployment-scenarios.xml:21(para) -msgid "Open vSwitch with GRE" -msgstr "" - -#: ./doc/networking-guide/section_deployment-scenarios.xml:22(para) -msgid "Open vSwitch with VXLAN" -msgstr "" - -#: ./doc/networking-guide/section_deployment-scenarios.xml:23(para) -msgid "Mixed Linux Bridge and Open vSwitch" -msgstr "" - -#: ./doc/networking-guide/section_deployment-scenarios.xml:26(para) -msgid "XIncluded content for possible reuse below" -msgstr "" - -#: ./doc/networking-guide/ch_networking-data-model.xml:11(title) -msgid "Networking data model" -msgstr "" - -#: ./doc/networking-guide/section_deployment-architecture.xml:11(title) -msgid "Example architecture" -msgstr "" - -#: ./doc/networking-guide/section_deployment-architecture.xml:14(title) -msgid "Controller node" -msgstr "" - -#: ./doc/networking-guide/section_deployment-architecture.xml:15(para) -msgid "Functions (provides API)" -msgstr "" - -#: ./doc/networking-guide/section_deployment-architecture.xml:19(title) -msgid "Network node" -msgstr "" - -#: ./doc/networking-guide/section_deployment-architecture.xml:20(para) -msgid "Functions (handles routing, NAT, floating IPs, etc)" -msgstr "" - -#: ./doc/networking-guide/section_deployment-architecture.xml:24(title) -msgid "Compute nodes" -msgstr "" - -#: ./doc/networking-guide/section_deployment-architecture.xml:25(para) -msgid "Functions (implements security groups" -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:11(title) -msgid "Agents" -msgstr "" - -#. This section has not yet been edited. LKB -#: ./doc/networking-guide/section_architecture-agents.xml:13(para) -msgid "Bacon ipsum dolor sit amet ribeye rump pork loin shankle jowl pancetta bacon. Chicken andouille capicola filet mignon shoulder, turducken corned beef boudin hamburger fatback pork chop t-bone kevin. Leberkas turducken short loin t-bone pork belly pig prosciutto chicken beef ribs pork loin short ribs shoulder jerky bacon strip steak." -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:22(systemitem) -msgid "neutron-server" -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:24(para) -msgid "A Python daemon, which manages user requests (and exposes the API). It is configured with a plugin that implements the OpenStack Networking API operations using a specific set of networking mechanisms. A wide choice of plugins are also available. For example, the open vSwitch and linuxbridge plugins utilize native Linux networking mechanisms, while other plugins interface with external devices or SDN controllers." -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:36(systemitem) -msgid "neutron-l3-agent" -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:38(para) -msgid "An agent providing L3/NAT forwarding." -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:44(systemitem) -msgid "neutron-*-agent" -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:46(para) -msgid "A plug-in agent that runs on each node to perform local networking configuration for the node's virtual machines and networking services." -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:53(systemitem) -msgid "neutron-dhcp-agent" -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:55(para) -msgid "An agent providing DHCP services to tenant networks." -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:61(term) -msgid "Database" -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:63(para) -msgid "Provides persistent storage." -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:72(para) -msgid "provide layer-2/3 connectivity to instances, handle physical-virtual network transition, handle metadata, etc" -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:82(para) ./doc/networking-guide/section_architecture-agents.xml:89(para) ./doc/networking-guide/section_architecture-agents.xml:102(para) ./doc/networking-guide/section_architecture-agents.xml:109(para) ./doc/networking-guide/section_architecture-agents.xml:122(para) -msgid "overview/concepts" -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:83(para) ./doc/networking-guide/section_architecture-agents.xml:90(para) ./doc/networking-guide/section_architecture-agents.xml:103(para) ./doc/networking-guide/section_architecture-agents.xml:110(para) ./doc/networking-guide/section_architecture-agents.xml:123(para) -msgid "configuration file" -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:97(title) -msgid "Layer 3 (IP/Routing)" -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:100(term) -msgid "l3" -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:107(term) -msgid "DHCP" -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:117(title) -msgid "Miscellaneous" -msgstr "" - -#: ./doc/networking-guide/section_architecture-agents.xml:120(term) -msgid "Metadata" -msgstr "" - -#: ./doc/networking-guide/section_deployment-authentication.xml:11(title) -msgid "Authentication" -msgstr "" - -#: ./doc/networking-guide/section_intro-neutron.xml:11(title) -msgid "Neutron data model" -msgstr "" - -#: ./doc/networking-guide/section_intro-neutron.xml:12(para) -msgid "FIXME: Explain Neutron terminology and how it maps to networking concepts presented in previous chapters. A small amount of terminology is at http://docs.openstack.org/admin-guide-cloud/content/api_abstractions.html . Probably not worth subsections as outlined here. table or variablelist?" -msgstr "" - -#: ./doc/networking-guide/section_intro-neutron.xml:18(title) -msgid "Networks" -msgstr "" - -#: ./doc/networking-guide/section_intro-neutron.xml:22(title) -msgid "Subnets" -msgstr "" - -#: ./doc/networking-guide/section_intro-neutron.xml:26(title) -msgid "Ports" -msgstr "" - -#: ./doc/networking-guide/section_intro-neutron.xml:30(title) -msgid "Extensions" -msgstr "" - -#: ./doc/networking-guide/ch_advanced.xml:7(title) -msgid "Advanced configuration options" -msgstr "" - -#: ./doc/networking-guide/ch_advanced.xml:8(para) -msgid "The following topics describe advanced configuration options for various system components. For example, configuration options where the default works but that the user wants to customize options. After installing from packages, $NEUTRON_CONF_DIR is /etc/neutron." -msgstr "" - -#: ./doc/networking-guide/ch_advanced.xml:19(title) -msgid "VPN-as-a-service" -msgstr "" - -#: ./doc/networking-guide/ch_advanced.xml:23(title) -msgid "Service chaining" -msgstr "" - -#: ./doc/networking-guide/ch_plugins.xml:7(title) -msgid "Plugins" -msgstr "" - -#: ./doc/networking-guide/section_architecture-server.xml:11(title) -msgid "Server" -msgstr "" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 -#: ./doc/networking-guide/section_architecture-server.xml:0(None) -msgid "translator-credits" -msgstr "" - diff --git a/doc/networking-guide/source/locale/networking-guide.pot b/doc/networking-guide/source/locale/networking-guide.pot new file mode 100644 index 0000000000..e69de29bb2