source/adminguide/locale/zh_CN/LC_MESSAGES/networking.mo (30 lines of code) (raw):
�� x � � � o � ?
� M � � � �
W T e
G �
� m � A � 4 ; > p � W � � � � ) � � � > ? ? ~ z � % 9 ? _ � �
/ � = � p � � b! W �! � =" �" �"
�" � # � �# ?$ _$ d$ h$ {$
�$ �$
�$ �$ �$ ^ �$ a %% f �% � �% � }& P ' Z U' n �' ^ ( 3 ~( � �( n 4) �) �) � �) U �* q , � y- � . � �. � 3/ , �/ * �/ 4 0 Q0 Z0 l0
x0 �0 2 �0 �0 �0 �0 1
1 + 1 � =1 +2 q ;2 E �2 �2 F 3 / L3 |3 ! �3 � �3 34 S4 n Z4 �4 0 �4 5
5 2 @5
s5 ~5
�6 �6 �6 �6 t �6 S ;9 4 �9 � �9 �: �: �: �: � �: [ I; x �< > r "> � �> ] j@ ; �@ � A � �A @ GC � �D 1 �E ? �E S �E n NG @ �G * �G < )H � fH � 7I E K � [L DM t TN i �O B 3Q : vQ �R 9 �R M S � ZT U �U ` �U ` �U K \V x �V !W 2W
NW � \W � �W �X �X �X �X �X �X �X �X �X �X Y Y Q ^Y c �Y � Z j �Z O [ X R[ d �[ ^ \ $ o\ x �\ s
] �] �] � �] , n^ � �_ � &a � �a � 2b � �b * <c ' gc . �c �c �c �c �c �c 1 �c
-d 8d Ed [d _d id � �d He _ Ue ? �e �e . f $ 4f Yf ! cf v �f �f g I g `g mg * �g ' �g
�g �g
�h �h i i #i ? ?k * k � �k tl �l �l �l { �l " -m Q Pn �o m �o (Optional) Name one of several available providers to use for a given service, such as Juniper for the firewall (Optional) Network tag to specify which physical network to use **Associate Public IP**: Select this option if you want to assign a public IP address to the VMs deployed in the guest network. This option is available only if **Conserve mode**: Indicate whether to use conserve mode. In this mode, network resources are allocated only when the first virtual machine starts in the network. When conservative mode is off, the public IP can only be used for a single service. For example, a public IP used for a port forwarding rule cannot be used for defining other services, such as StaticNAT or load balancing. When the conserve mode is on, you can define more than one service on the same public IP. **Dedicated**: If you select dedicated LB isolation, a dedicated load balancer device is assigned for the network from the pool of dedicated load balancer devices provisioned in the zone. If no sufficient dedicated load balancer devices are available in the zone, network creation fails. Dedicated device is a good choice for the high-traffic networks that make full use of the device's resources. **Default egress policy**: Configure the default policy for firewall egress rules. Options are Allow and Deny. Default is Allow if no egress policy is specified, which indicates that all the egress traffic is accepted when a guest network is created from this offering. **Description**. A short description of the offering that can be displayed to users. **Guest Type**. Choose whether the guest network is isolated or shared. **Inline mode**: Supported only for Juniper SRX firewall and BigF5 load balancer devices. In inline mode, a firewall device is placed in front of a load balancing device. The firewall acts as the gateway for all the incoming traffic, then redirect the load balancing traffic to the load balancer behind it. The load balancer in this case will not have the direct access to the public network. **LB Isolation**: Specify what type of load balancer isolation you want for the network: Shared or Dedicated. **Mode**: You can select either Inline mode or Side by Side mode: **Name**. Any desired name for the network offering. **Network Rate**. Allowed data transfer rate in MB per second. **Persistent**. Indicate whether the guest network is persistent or not. The network that you can provision without having to deploy a VM on it is termed persistent network. For more information, see `“Persistent Networks” <networking2.html#persistent-networks>`_. **Redundant router capability**: Available only when Virtual Router is selected as the Source NAT provider. Select this option if you want to use two virtual routers in the network for uninterrupted connection: one operating as the master virtual router and the other as the backup. The master virtual router receives requests from and sends responses to the user’s VM. The backup virtual router is activated only when the master is down. After the failover, the backup becomes the master virtual router. CloudStack deploys the routers on different hosts to ensure reliability if one host is down. **Shared**: If you select shared LB isolation, a shared load balancer device is assigned for the network from the pool of shared load balancer devices provisioned in the zone. While provisioning CloudStack picks the shared load balancer device that is used by the least number of accounts. Once the device reaches its maximum capacity, the device will not be allocated to a new account. **Side by Side**: In side by side mode, a firewall device is deployed in parallel with the load balancer device. So the traffic to the load balancer public IP is not routed through the firewall, and therefore, is exposed to the public network. **Specify VLAN**. (Isolated guest networks only) Indicate whether a VLAN could be specified when this offering is used. If you select this option and later use this network offering while creating a VPC tier or an isolated network, you will be able to specify a VLAN ID for the network you create. **Supported Services**. Select one or more of the possible network services. For some services, you must also choose the service provider; for example, if you select Load Balancer, you can choose the CloudStack virtual router or any other load balancers that have been configured in the cloud. Depending on which services you choose, additional fields may appear in the rest of the dialog box. **System Offering**. If the service provider for any of the services selected in Supported Services is a virtual router, the System Offering field appears. Choose the system service offering that you want virtual routers to use in this network. For example, if you selected Load Balancer in Supported Services and selected a virtual router to provide load balancing, the System Offering field appears so you can choose between the CloudStack default system service offering and any custom system service offerings that have been defined by the CloudStack root administrator. **Tags**: Network tag to specify which physical network to use. **VPC**. This option indicate whether the guest network is Virtual Private Cloud-enabled. A Virtual Private Cloud (VPC) is a private, isolated part of CloudStack. A VPC can have its own virtual network topology that resembles a traditional physical network. For more information on VPCs, see `“About Virtual Private Clouds” <networking2.html#about-virtual-private-clouds>`_. *Supported Network Service Providers* A network offering is a named set of network services, such as: A service provider (also called a network element) is hardware or virtual appliance that makes a network service possible; for example, a firewall appliance can be installed in the cloud to provide firewall service. On a single network, multiple providers can provide the same network service. For example, a firewall service may be provided by Cisco or Juniper devices in the same physical network. A shared network can be accessed by virtual machines that belong to many different accounts. Network Isolation on shared networks is accomplished by using techniques such as security groups, which is supported only in Basic zones in CloudStack 3.0.3 and later versions. A virtual network is a logical construct that enables multi-tenancy on a single physical network. In CloudStack a virtual network can be shared or isolated. About Virtual Networks Add new network offerings as time goes on so end users can upgrade to a better class of service on their network An isolated network can be accessed only by virtual machines of a single account. Isolated networks have the following properties. Based on the guest network type selected, you can see the following supported services: Bundle different types of network services into network offerings, so users can choose the desired network services for any given virtual machine Citrix NetScaler Click Add Network Offering. Click Add. CloudStack also has internal network offerings for use by CloudStack system VMs. These network offerings are not visible to users but can be modified by administrators. CloudStack ships with an internal list of the supported service providers, and you can choose from this list when creating a network offering. Creating a New Network Offering DHCP DNS DNS/DHCP/User Data Description Elastic IP Elastic IP is enabled. Elastic LB F5 BigIP Firewall For a description of this term, see `“About Virtual Networks” <#about-virtual-networks>`_. For information on Elastic IP, see `“About Elastic IP” <networking2.html#about-elastic-ip>`_. For more information, see `“Adding a Security Group” <networking2.html#adding-a-security-group>`_. For more information, see `“Configure Guest Traffic in an Advanced Zone” <networking2.html#configure-guest-traffic-in-an-advanced-zone>`_. For more information, see `“Configuring Network Access Control List” <networking2.html#configuring-network-access-control-list>`_. For more information, see `“DNS and DHCP” <networking2.html#dns-and-dhcp>`_. For more information, see `“Remote Access VPN” <networking2.html#remote-access-vpn>`_. For more information, see `“System Service Offerings” <service_offerings.html#system-service-offerings>`_. For more information, see `“User Data and Meta Data” <api.html#user-data-and-meta-data>`_. For more information, see the Administration Guide. For the most up-to-date list of supported network service providers, see the CloudStack UI or call `listNetworkServiceProviders`. For the most up-to-date list of supported network services, see the CloudStack UI or call listNetworkServices. Guest network is shared. Host based (KVM/Xen) If StaticNAT is enabled, irrespective of the status of the conserve mode, no port forwarding or load balancing rule can be created for the IP. However, you can add the firewall rules by using the createFirewallRule command. If different providers are set up to provide the same service on the network, the administrator can create network offerings so users can specify which network service provider they prefer (along with the other choices offered in network offerings). Otherwise, CloudStack will choose which provider to use whenever the service is called for. If you create load balancing rules while using a network service offering that includes an external load balancer device such as NetScaler, and later change the network service offering to one that uses the CloudStack virtual router, you must create a firewall rule on the virtual router for each of your existing load balancing rules so that they continue to function. If you select Load Balancer, you can choose the CloudStack virtual router or any other load balancers that have been configured in the cloud. If you select Port Forwarding, you can choose the CloudStack virtual router or any other Port Forwarding providers that have been configured in the cloud. If you select Source NAT, you can choose the CloudStack virtual router or any other Source NAT providers that have been configured in the cloud. If you select Static NAT, you can choose the CloudStack virtual router or any other Static NAT providers that have been configured in the cloud. In Select Offering, choose Network Offering. In the dialog, make the following choices: In the left navigation bar, click Service Offerings. Isolated Isolated Networks Juniper SRX Load Balancer Load Balancing Log in with admin privileges to the CloudStack UI. Network ACL Network Offerings Network Service Providers No Not Supported Overview of Setting Up Networking for Users People using cloud infrastructure have a variety of needs and preferences when it comes to the networking services provided by the cloud. As a CloudStack administrator, you can do the following things to set up networking for your users: Port Forwarding Provide more ways for a network to be accessed by a user, such as through a project of which the user is a member Public Network is a shared network that is not shown to the end users Remote Access VPN Resources such as VLAN are allocated and garbage collected dynamically Runtime Allocation of Virtual Network Resources Security Groups Set up physical networks in zones Set up several different providers for the same service on a single physical network (for example, both Cisco and Juniper firewalls) Setting Up Networking for Users Shared Shared Network resources such as VLAN and physical network that it maps to are designated by the administrator Shared Networks Shared Networks are created by the administrator Shared Networks can be designated to a certain domain Shared Networks can be isolated by security groups Source NAT Source NAT per zone is not supported in Shared Network when the service provider is virtual router. However, Source NAT per account is supported. For information, see `“Configuring a Shared Guest Network” <networking2.html#configuring-a-shared-guest-network>`_. Static NAT StaticNAT is enabled. Supported Supported Services The CloudStack administrator can create any number of custom network offerings, in addition to the default network offerings provided by CloudStack. By creating multiple custom network offerings, you can set up your cloud to offer different classes of service on a single multi-tenant physical network. For example, while the underlying physical wiring may be the same for two tenants, tenant A may only need simple firewall protection for their website, while tenant B may be running a web server farm and require a scalable firewall solution, load balancing solution, and alternate networks for accessing the database backend. The network offering can be upgraded or downgraded but it is for the entire network There is one network offering for the entire network To block the egress traffic for a guest network, select Deny. In this case, when you configure an egress rules for an isolated guest network, rules are added to allow the specified traffic. To create a network offering: User Data VPN Virtual Router When creating a new VM, the user chooses one of the available network offerings, and that determines which network services the VM can use. When creating a new virtual network, the CloudStack administrator chooses which network offering to enable for that network. Each virtual network is associated with one network offering. A virtual network can be upgraded or downgraded by changing its associated network offering. If you do this, be sure to reprogram the physical network to match. When you define a new virtual network, all your settings for that network are stored in CloudStack. The actual network resources are activated only when the first virtual machine starts in the network. When all virtual machines have left the virtual network, the network resources are garbage collected so they can be allocated again. This helps to conserve network resources. Yes You can have multiple instances of the same service provider in a network (say, more than one Juniper SRX device). Project-Id-Version: Apache CloudStack Administration RTD
Report-Msgid-Bugs-To:
POT-Creation-Date: 2014-06-30 12:52+0200
PO-Revision-Date: 2014-06-30 12:04+0000
Last-Translator: FULL NAME <EMAIL@ADDRESS>
Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Language: zh_CN
Plural-Forms: nplurals=1; plural=0;
(可选)在服务的多个可选提供者中指定其一，例如Juniper作为防火墙服务 (可选)用于指定使用哪个物理网络的网络标签 **关联的公网IP**:如果你想给来宾网络中的虚拟机直接分配公网IP，选择这个选项。这个选择只有在以下情况都满足时才有效： **Conserve mode**: 这个选项表明是滞要使用Conserve模式。在这种模式下，网络资源只会分配给网络里第一个启动的虚拟机。当Conserve模式被关闭时，公网IP只能用于一个设备。比如，一个用于端口转发规则的公网IP不会被用于其它StaticNAT或是负载均衡服务。当Conserve模式启用时，你可以在同一个公网IP上定义多个服务。 **单独的**:如果你选择了单独的负载均衡隔离类型，这个区域内的单独负载均衡设备资源池里就会分出一个设备来供使用。如果没有足够的设备，网络创建就会失败。如果要在高流量环境充分利用设备，单独的负载均衡设备是一个很好的选择。 **默认外出策略**: 为防火墙配置默认的外出流量规则。选项有阻止和允许。如果没有特别制定策略的话，所有外出流量都是允许的。这表明，从这个方案创建的客户网络是允许所有外出流量的。 **描述**: 提供一个简短的方案描述。 **来宾类型**: 选择来宾网络为隔离或共享网络。 **Inline mode**: 这种模式只被Juniper SRX 和BigF5负载均衡设备支持。在Inline mode模式下，防火墙设备放在负载均衡设置的前端，这个防火墙作为进入流量的网关，所有的流量会被转发到后端的负载均衡设备上。在这种情况下，负载均衡不是直接连接到公网网络的。 **负载均衡隔离**:指定一种你希望的网络里的负载均衡隔离类型：共享的或单独的。 **模式**: 你可以选择 Inline mode 或 Side by Side 模式: **名称**: 任何网络方案的名称。 **网络速度**: 允许的数据传输速度（MB/秒）。 **持续性**: 表明来宾网络是否支持持续性。无需提供任何VM部署的网络，称之为持续性网络。更多信息，参考 `“持久性网络” <networking2.html#persistent-networks>`_. **冗余路由性能**:这个选项只有在虚拟路由作为Source NAT提供者时才是可选的。如果你希望提供不间断的网络连接，选中这个选项，则系统会提供两个虚拟路由：一个主的，一个辅的。主虚拟路由负载收发用户虚拟机器的相关请深圳市。如主的路由DOWN掉时，由辅助路由升级为主路由接替工作。CloudStack 会将两个邪气路由分别部署在不同的主机上，以保证可用性。 **共享的**:如果你选择了共享的负载均衡设备， 这个区域内的共享负载均衡设备资源池里就会分出一个设备来供使用。CloudStack会将共享设备分配给不少于一定量的帐号共用，如果共享设备到达了最大数量，则这个设备不会再分配给新的帐号使用。 *Side by Side**:在Side by Side模式下，防火墙设备和负载均衡设备是并列的。所以所有的流量都是直接到负载均衡设备而不经过防火墙。因此，负载均衡设备是直接暴露在公网中的。 **指定VLAN**.(只针对隔离来宾网络)这表明无论使用这个方案时是否指定了VLAN，如果你选中了这个选项，并且当你创建VPC层或隔离网络时使用了这个网络方案，那么，你都可以为你创建的网络拽定一个VLAN ID。 **支持的服务**.选择一个或多个可能的网络服务。对于有一个服务，你还必须同时选择服务的提供者。比如，如果你选择了负载均衡服务，那你可以CLOUDSTACK虚拟路由或是云环境中其它配置了此功能的服务者。取决于你选择服务的不同，额外的选项或是对话框的填写项也会相应不同。 **系统方案**.如果你在任务服务提供者中选择了虚拟路由，那就会出现系统方案的填写项。选择你希望虚拟路由在此网络中提供的服务。比如，如果你选择了虚拟路由提供负载均衡服务，系统方案填写项就会出现，你可以选择CLOUDSTACK管理员定义的所有系统服务及默认服务。 **标签**:网络标签用于指定所要使用的物理网络。 **VPC**: 此选项表明是否在来宾网络中启用VPC。 CloudStack中的虚拟专用云(VPC)是专用、隔离的。 一个VPC可以有一个类似于传统物理网络的虚拟网络拓扑结构。有关的VPC的详细信息，请参考 see `“关于VPC” <networking2.html#about-virtual-private-clouds>`_. *支持的网络服务提供者* 网络方案是带名称的一套网络服务，例如： 服务提供者(也称为网络元件)是指通过硬件或虚拟应用来实现网络应用。比如，防火墙应用可以安装在云端来提供防火墙服务。在独立网络中多个提供者能提供相同的网络服务。比如，可以通过思科或者Juniper的设备在同一个物理网络中提供防火墙服务。 共享网络可以被属于不同客户的虚拟机访问。共享网络中的网络隔离通过安全组实现（仅在CloudStack 3.0.3及以后的基本区域中支持） 虚拟网络是使多租户在一个物理网络中的逻辑结构。在CloudStack中，虚拟网络可以被共享或隔离。 关于虚拟网络 随着时间的推移, 添加新的网络方案以便是最终用户升级他们的网络服务. 一个隔离的网络可以访问虚拟机的单一账户。隔离的网络具有下列性质。 基于你选择的来宾网络类型，可以看到如何支持的服务。 绑定不同类型的网络服务到网络方案中, 这样用户可以在给定的虚机中使用期望的网络服务. Citrix NetScaler 点击添加网络方案。 点击 添加 CloudStack 中有给系统虚机使用的内部网络方案。内部网络方案对最终用户是不可见的，但系统管理员可以对其修改。 CloudStack已经预置了一些内置的服务提供者支持列表。你能在创建网络提供方案的时候你能从这列表中选择。 创建一个新的网络方案 DHCP DNS DNS/DHCP/User Data 描述 弹性IP 启用弹性IP 弹性负载均衡 F5 BigIP 防火墙 关于此组的描述，参考 see `“关于虚拟网络” <#about-virtual-networks>`_. 更多信息，参考`“关于弹性IP” <networking2.html#about-elastic-ip>`_. 更多信息，请参考 `“添加一个安全组” <networking2.html#adding-a-security-group>`_. 更多信息，参考`“在高级区域中配置来宾流量” <networking2.html#configure-guest-traffic-in-an-advanced-zone>`_. 更多信息，参考 `“配置网络ACL” <networking2.html#configuring-network-access-control-list>`_. 更多信息，请参考 `“DNS and DHCP” <networking2.html#dns-and-dhcp>`_. 更多信息，请参考`“Remote Access VPN” <networking2.html#remote-access-vpn>`_. 更多信息，参考 `“系统服务方案” <service_offerings.html#system-service-offerings>`_. 更多信息，请参考 `“用户数据和元数据” <api.html#user-data-and-meta-data>`_. 更多信息，请参考管理指南 查看最新的网络服务提供者支持列表请见CloudStack用户界面或者调用listNetworkServiceProviders`.。 要查看最新的网络服务支持列表，请参见 CloudStack用户界面或者调用API listNetworkServices。 来宾网络被共享 Host based (KVM/Xen) 如果StaticNAT启用后，不考虑conseve模式的状态，则此IP不会创建端口转发或是负载均衡规则。然而，你可以通过 createFirewallRule命令添加防火墙规则。 如果不同提供者被设置在网络中提供相同服务，管理员可以通过创建网络提供方案，因此用户能够自己制定使用哪个物理网络提供者(要遵从网络提供方案中的其他选项)。否则CloudStack会在服务被需求的时候选择使用哪个提供者。 如果你创建了一个负载均衡规则且使用包括外部负载均衡设备的网络服务方案，如包括NetScaler，但随后将网络方案改成使用CloudStack的虚拟路由器，则你必须在虚拟路由器上创建一个防火墙规则，这些防火墙规则与已经设置的负载均衡规则一一对应，只有这样，才能使那些负载均衡规则继续起作用。 如果选择了负载均衡功能，你就可以选择CLOUDSTACK虚拟路由或是云环境中其它配置了此服务的提供者。 如果选择了端口转发功能，你就可以选择CLOUDSTACK虚拟路由或是云环境中其它配置了此服务的提供者。 如果选择了 Source NAT功能，你就可以选择CLOUDSTACK虚拟路由或是云环境中其它配置了此服务的提供者。 如果选择了Static NAT功能，你就可以选择CLOUDSTACK虚拟路由或是云环境中其它配置了此服务的提供者。 在选择方案中，选择网络方案。 在对话框中，选择如下操作： 在左侧导航栏中，点击 服务方案。 隔离 独立的网络 Juniper SRX 负载均衡 负载均衡 以管理员权限登录CloudStack用户界面。 网络 ACL 网络方案 网络服务提供者 否 不支持 用户网络设置概览 当涉及到云计算所提供的网络服务, 使用云基础设施的人都有各自不同的需求和喜好. 作为CloudStack管理员, 你可以为你的用户做下面的事情来设置网络: 端口转发 提供更多的途径让一个用户访问一个网络, 比如通过用户所在的一个项目 公网网络作为一个共享网络不会展示给终端用户 远程访问VPN 如VLAN等资源被动态分配和垃圾收集 虚拟网络资源的运行时分配 安全组 在资源域里设置物理网络 在单个物理网卡上为同一服务设置不同的服务提供者(例如, 同时设置Cisco和Juniper的防火墙) 用户网络设置 共享 共享网络资源如VLAN和物理网络，它映射到指定的管理员 共享网络 管理员创建的共享网络 在一个确定的哉中设计共享网络 共享网络通过安全组实现隔离 Source NAT 当共享网络是由虚拟路由提供的服务，则每个区域是不支持Source NAT功能的。然而，每个帐户是支持Source NAT功能的。更多信息，参考`“配置共享来宾网络” <networking2.html#configuring-a-shared-guest-network>`_. 静态 NAT 启用StaticNAT 支持 支持的服务 CloudStack ;提供了默认的网络方案，在此之外，系统管理员可以添加任意数量的自定义网络方案。通过创建多种自定义网络方案，您可以在一个多租户的物理网络基础上提供不同级别的网络服务。例如，尽管两个租户的底层物理网络是一个，租户A可能仅需要用防火墙保护他们的网站，而租户B可能运行一个Web服务器集群，要求一个可扩展的防火墙方案、负载均衡方案、和用于访问后台数据库的可替代的网络。 网络提供可升级或降级，但它是用于整个网络的 有一个用于整个网络的网络方案 为了阻止客户网络的外出流量，选择阻止选项。在这种情况下，当你从一个隔离的客户网络配置一个外出规则时，添加一些特殊的规则以允许外出流量。 创建一个新的网络方案 用户数据 VPN 虚拟路由 用户创建虚机时，需要选择一种可用的网络方案。该网络方案确定了虚机可使用的网络服务。 创建新虚拟网络时，CloudStack 管理服务器可选择该网络使用的网络方案。每个虚拟网络都关联一个网络方案。虚拟网络可以通过改变关联的网络方案来升级或降级。如果您要这样做，请确保调整物理网络以匹配网络方案。 当你定义一个新的虚拟网络，该网络的所有的设置都存储在CloudStack中。只有当第一台虚拟机在该网络中启动时，实际的网络资源才会被激活。当所有的虚拟机都离开了虚拟网络，系统进行网络资源垃圾收集，使它们能够重新分配。这有助于节约网络资源。 是 在一个网络中你可以多个实例使用相同的服务提供者(也可以使用多个Juniper SRX设备)