source/adminguide/locale/pot/networking/inter_vlan_routing.pot

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 
# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2014-06-30 12:52+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#: ../../networking/inter_vlan_routing.rst:18
# 536a6b6a19a04686832c0c8f3202472a
msgid "About Inter-VLAN Routing (nTier Apps)"
msgstr ""

#: ../../networking/inter_vlan_routing.rst:20
# 01903cae08524fb18fb51475e29cccc5
msgid "Inter-VLAN Routing (nTier Apps) is the capability to route network traffic between VLANs. This feature enables you to build Virtual Private Clouds (VPC), an isolated segment of your cloud, that can hold multi-tier applications. These tiers are deployed on different VLANs that can communicate with each other. You provision VLANs to the tiers your create, and VMs can be deployed on different tiers. The VLANs are connected to a virtual router, which facilitates communication between the VMs. In effect, you can segment VMs by means of VLANs into different networks that can host multi-tier applications, such as Web, Application, or Database. Such segmentation by means of VLANs logically separate application VMs for higher security and lower broadcasts, while remaining physically connected to the same device."
msgstr ""

#: ../../networking/inter_vlan_routing.rst:33
# d835d5a69985471085a5688b045c4e38
msgid "This feature is supported on XenServer, KVM, and VMware hypervisors."
msgstr ""

#: ../../networking/inter_vlan_routing.rst:35
# 7aecd1ac66b84f9cb92b03fea7d5edde
msgid "The major advantages are:"
msgstr ""

#: ../../networking/inter_vlan_routing.rst:37
# dca4c4be393c4d7bbcda75f49ffc8efc
msgid "The administrator can deploy a set of VLANs and allow users to deploy VMs on these VLANs. A guest VLAN is randomly alloted to an account from a pre-specified set of guest VLANs. All the VMs of a certain tier of an account reside on the guest VLAN allotted to that account."
msgstr ""

#: ../../networking/inter_vlan_routing.rst:43
# d5d8b41e126e4b38913d0cf7de1ec29d
msgid "A VLAN allocated for an account cannot be shared between multiple accounts."
msgstr ""

#: ../../networking/inter_vlan_routing.rst:45
# 4e04be2a6cef4fa8973d317232221018
msgid "The administrator can allow users create their own VPC and deploy the application. In this scenario, the VMs that belong to the account are deployed on the VLANs allotted to that account."
msgstr ""

#: ../../networking/inter_vlan_routing.rst:49
# 48018251e76046c4a606035de8d1b4d5
msgid "Both administrators and users can create multiple VPCs. The guest network NIC is plugged to the VPC virtual router when the first VM is deployed in a tier."
msgstr ""

#: ../../networking/inter_vlan_routing.rst:53
# cc50778ecfab43c38af3373511f47072
msgid "The administrator can create the following gateways to send to or receive traffic from the VMs:"
msgstr ""

#: ../../networking/inter_vlan_routing.rst:56
# 5d91169a83a5400b8408b6ce4ccb84f5
msgid "**VPN Gateway**: For more information, see `\"Creating a VPN gateway for the VPC\" <#creating-a-vpn-gateway-for-the-vpc>`_."
msgstr ""

#: ../../networking/inter_vlan_routing.rst:59
# 1f0ed1ecf964455ab40301bdf5ab2dc2
msgid "**Public Gateway**: The public gateway for a VPC is added to the virtual router when the virtual router is created for VPC. The public gateway is not exposed to the end users. You are not allowed to list it, nor allowed to create any static routes."
msgstr ""

#: ../../networking/inter_vlan_routing.rst:64
# b843201a793749bb924d48f21be04e09
msgid "**Private Gateway**: For more information, see \":ref:`adding-priv-gw-vpc`\"."
msgstr ""

#: ../../networking/inter_vlan_routing.rst:66
# a4ac63d4b99a4edd968087d0f622647a
msgid "Both administrators and users can create various possible destinations-gateway combinations. However, only one gateway of each type can be used in a deployment."
msgstr ""

#: ../../networking/inter_vlan_routing.rst:70
# 50735b7154a64b7880f5543c4792b1c0
msgid "For example:"
msgstr ""

#: ../../networking/inter_vlan_routing.rst:72
# bdd41dc64438436aac12d9f1c8d5a8bc
msgid "**VLANs and Public Gateway**: For example, an application is deployed in the cloud, and the Web application VMs communicate with the Internet."
msgstr ""

#: ../../networking/inter_vlan_routing.rst:76
# f2c3b70246534d5aabdd3954a25ba1eb
msgid "**VLANs, VPN Gateway, and Public Gateway**: For example, an application is deployed in the cloud; the Web application VMs communicate with the Internet; and the database VMs communicate with the on-premise devices."
msgstr ""

#: ../../networking/inter_vlan_routing.rst:81
# 7fb2fe01c3484b80a30d4c6edb0b5782
msgid "The administrator can define Network Access Control List (ACL) on the virtual router to filter the traffic among the VLANs or between the Internet and a VLAN. You can define ACL based on CIDR, port range, protocol, type code (if ICMP protocol is selected) and Ingress/Egress type."
msgstr ""

#: ../../networking/inter_vlan_routing.rst:87
# 95cd03acfa2948c682ec51eaf24346be
msgid "The following figure shows the possible deployment scenarios of a Inter-VLAN setup:"
msgstr ""

#: ../../networking/inter_vlan_routing.rst:90
# a9f3216208ba417681d8885848d2a414
msgid "|mutltier.png|"
msgstr ""

#: ../../networking/inter_vlan_routing.rst:92
# 785b1c5286424a3680f6ffa4fa40de5a
msgid "To set up a multi-tier Inter-VLAN deployment, see \":ref:`configuring-vpc`\"."
msgstr ""