Apache CloudStack Installation RTD - en to zh_CN translation catalogue (112 entries)

en: LXC Installation and Configuration
zh_CN: LXC安装和配置

en: System Requirements for LXC Hosts
zh_CN: LXC主机的系统要求

en: LXC requires the Linux kernel cgroups functionality which is available starting 2.6.24. Although you are not required to run these distributions, the following are recommended:
zh_CN: LXC要求Linux kernel 2.6.24开始引入的 cgroups功能。尽管不需要运行所有的发行版，但是建议下列的版本：

en: The main requirement for LXC hypervisors is the libvirt and Qemu version. No matter what Linux distribution you are using, make sure the following requirements are met:
zh_CN: LXC hypervisor 要求libvirt和Qemu的版本。无论使用哪种Linux发行版，请确保满足以下要求：

en: libvirt: 1.0.0 or higher
zh_CN: libvirt: 1.0.0或更高

en: Qemu/KVM: 1.0 or higher
zh_CN: Qemu/KVM: 1.0 或更高版本

en: The default bridge in CloudStack is the Linux native bridge implementation (bridge module). CloudStack includes an option to work with OpenVswitch, the requirements are listed below
zh_CN: CloudStack中的默认使用Linux本身的桥接(bridge模块)方式实现。也可选择在CloudStack中使用OpenVswitch，具体要求如下：

en: openvswitch: 1.7.1 or higher
zh_CN: openvswitch: 1.7.1或更高版本

en: In addition, the following hardware requirements apply:
zh_CN: 此外，硬件要求如下：

en: Within a single cluster, the hosts must be of the same distribution version.
zh_CN: 同一集群中主机必须使用相同版本的Linux系统。

en: All hosts within a cluster must be homogenous. The CPUs must be of the same type, count, and feature flags.
zh_CN: 同一群集中的所有节点架构必须一致。CPU的型号、数量和功能参数必须相同。

en: Must support HVM (Intel-VT or AMD-V enabled)
zh_CN: 必须支持HVM(Intel-VT或者AMD-V)

en: 64-bit x86 CPU (more cores results in better performance)
zh_CN: 64位x86 CPU(多核性能更佳)

en: 4 GB of memory
zh_CN: 4GB 内存

en: At least 1 NIC
zh_CN: 至少一块网卡

en: When you deploy CloudStack, the hypervisor host must not have any VMs already running
zh_CN: 在部署CloudStack时，Hypervisor主机不能运行任何虚拟机

en: LXC Installation Overview
zh_CN: LXC安装概述

en: LXC does not have any native system VMs, instead KVM will be used to run system VMs. This means that your host will need to support both LXC and KVM, thus most of the installation and configuration will be identical to the KVM installation. The material in this section doesn't duplicate KVM installation docs. It provides the CloudStack-specific steps that are needed to prepare a KVM host to work with CloudStack.
zh_CN: LXC没有任何本地系统VMs，而KVM需要运行系统VMs。意思为主机需要同时支持LXC和KVM。因此，大部分的安装和配置跟KVM的安装一样。本章节不会复述KVM的安装。这里我们只会给出使KVM与CloudStack协同工作的一些特有的步骤。

en: Before continuing, make sure that you have applied the latest updates to your host.
zh_CN: 在我们开始之前，请确保所有的主机都安装了最新的更新包。

en: It is NOT recommended to run services on this host not controlled by CloudStack.
zh_CN: 不建议在主机中运行与CloudStack无关的服务。

en: The procedure for installing an LXC Host is:
zh_CN: 安装LXC主机步骤：

en: Prepare the Operating System
zh_CN: 准备操作系统

en: Install and configure libvirt
zh_CN: 安装和配置libvirt

en: Configure Security Policies (AppArmor and SELinux)
zh_CN: 配置安全策略 (AppArmor 和 SELinux)

en: Install and configure the Agent
zh_CN: 安装和配置Agent

en: The OS of the Host must be prepared to host the CloudStack Agent and run KVM instances.
zh_CN: 主机的操作系统必须为运行CloudStack Agent和KVM实例做些准备。

en: Log in to your OS as root.
zh_CN: 使用root用户登录操作系统。

en: Check for a fully qualified hostname.
zh_CN: 检查FQN完全合格/限定主机名。

en: This should return a fully qualified hostname such as "kvm1.lab.example.org". If it does not, edit /etc/hosts so that it does.
zh_CN: 该命令会返回完全合格/限定主机名，例如"kvm1.lab.example.org"。如果没有，请编辑 /etc/hosts。

en: Make sure that the machine can reach the Internet.
zh_CN: 确保机器可以连接到互联网.

en: Turn on NTP for time synchronization.
zh_CN: 启用NTP服务以确保时间同步.

en: NTP is required to synchronize the clocks of the servers in your cloud. Unsynchronized clocks can cause unexpected problems.
zh_CN: NTP服务用来同步云中的服务器时间。时间不同步会带来意想不到的问题。

en: Install NTP
zh_CN: 安装NTP

en: Repeat all of these steps on every hypervisor host.
zh_CN: 在所有主机中重复上述步骤。

en: To manage LXC instances on the host CloudStack uses a Agent. This Agent communicates with the Management server and controls all the instances on the host.
zh_CN: CloudStack使用代理管理LXC实例。管理服务器与代理通信并控制主机中所有实例。

en: First we start by installing the agent:
zh_CN: 首先我们安装Agent：

en: In RHEL or CentOS:
zh_CN: 在RHEL/CentOS上:

en: In Ubuntu:
zh_CN: 在Ubuntu上:

en: Next step is to update the Agent configuration setttings. The settings are in ``/etc/cloudstack/agent/agent.properties``
zh_CN: 接下来更新代理配置。在 ``/etc/cloudstack/agent/agent.properties`` 中配置

en: Set the Agent to run in LXC mode:
zh_CN: 设置代理运行在LXC模式下：

en: Optional: If you would like to use direct networking (instead of the default bridge networking), configure these lines:
zh_CN: 可选项：如果想使用直连网络(代替默认的桥接网络)，配置如下行：

en: The host is now ready to be added to a cluster. This is covered in a later section, see :ref:`adding-a-host`. It is recommended that you continue to read the documentation before adding the host!
zh_CN: 现在主机已经为加入群集做好准备。后面的章节有介绍，请参阅 :ref:`adding-a-host`。强烈建议在添加主机之前阅读此部分内容。

en: Install and Configure libvirt
zh_CN: 安装和配置libvirt

en: CloudStack uses libvirt for managing virtual machines. Therefore it is vital that libvirt is configured correctly. Libvirt is a dependency of cloudstack-agent and should already be installed.
zh_CN: CloudStack使用libvirt管理虚拟机。因此正确地配置libvirt至关重要。CloudStack-agent依赖于Libvirt，应提前安装完毕。

en: In order to have live migration working libvirt has to listen for unsecured TCP connections. We also need to turn off libvirts attempt to use Multicast DNS advertising. Both of these settings are in ``/etc/libvirt/libvirtd.conf``
zh_CN: 为了实现动态迁移libvirt需要监听不可靠的TCP连接。还要关闭libvirts尝试使用组播DNS进行广播。这些都可以在 /etc/libvirt/libvirtd.conf文件中进行配置。

en: Set the following parameters:
zh_CN: 设定下列参数：

en: Turning on "listen\_tcp" in libvirtd.conf is not enough, we have to change the parameters as well:
zh_CN: 除了在libvirtd.conf中打开"listen_tcp"以外，我们还必须修改/etc/sysconfig/libvirtd中的参数:

en: On RHEL or CentOS modify ``/etc/sysconfig/libvirtd``:
zh_CN: 在RHEL或者CentOS中修改 ``/etc/sysconfig/libvirtd``：

en: Uncomment the following line:
zh_CN: 取消如下行的注释：

en: On Ubuntu: modify ``/etc/default/libvirt-bin``
zh_CN: 在Ubuntu中:修改 ``/etc/default/libvirt-bin``

en: Add "-l" to the following line
zh_CN: 在下列行添加 "-l"

en: so it looks like:
zh_CN: 如下所示:

en: In order to have the VNC Console work we have to make sure it will bind on 0.0.0.0. We do this by editing ``/etc/libvirt/qemu.conf``
zh_CN: 为了VNC控制台正常工作，必须确保该参数绑定在0.0.0.0上。通过编辑 ``/etc/libvirt/qemu.conf``实现。

en: Make sure this parameter is set:
zh_CN: 请确保这个参数配置为：

en: Restart libvirt
zh_CN: 重启libvirt服务

en: Configure the Security Policies
zh_CN: 配置安全策略

en: CloudStack does various things which can be blocked by security mechanisms like AppArmor and SELinux. These have to be disabled to ensure the Agent has all the required permissions.
zh_CN: CloudStack的会被例如AppArmor和SELinux的安全机制阻止。必须关闭安全机制并确保 Agent具有所必需的权限。

en: Configure SELinux (RHEL and CentOS)
zh_CN: 配置SELinux（RHEL和CentOS）：

en: Check to see whether SELinux is installed on your machine. If not, you can skip this section.
zh_CN: 检查你的机器是否安装了SELinux。如果没有，请跳过此部分。

en: In RHEL or CentOS, SELinux is installed and enabled by default. You can verify this with:
zh_CN: 在RHEL或者CentOS中，SELinux是默认安装并启动的。你可以使用如下命令验证：

en: Set the SELINUX variable in ``/etc/selinux/config`` to "permissive". This ensures that the permissive setting will be maintained after a system reboot.
zh_CN: 在 ``/etc/selinux/config`` 中设置SELINUX变量值为 "permissive"。这样能确保对SELinux的设置在系统重启之后依然生效。

en: Change the following line
zh_CN: 查找如下行

en: to this
zh_CN: 修改为

en: Then set SELinux to permissive starting immediately, without requiring a system reboot.
zh_CN: 然后使SELinux立即运行于permissive模式，无需重新启动系统。

en: Configure Apparmor (Ubuntu)
zh_CN: 配置AppArmor(Ubuntu)

en: Check to see whether AppArmor is installed on your machine. If not, you can skip this section.
zh_CN: 检查你的机器中是否安装了AppArmor。如果没有，请跳过此部分。

en: In Ubuntu AppArmor is installed and enabled by default. You can verify this with:
zh_CN: Ubuntu中默认安装并启动AppArmor。使用如下命令验证：

en: Disable the AppArmor profiles for libvirt
zh_CN: 在AppArmor配置文件中禁用libvirt

en: Configure the network bridges
zh_CN: 配置网络桥接

en: This is a very important section, please make sure you read this thoroughly.
zh_CN: 本章节非常重要，请务必彻底理解。

en: This section details how to configure bridges using the native implementation in Linux. Please refer to the next section if you intend to use OpenVswitch
zh_CN: 本章节详细介绍了如何使用Linux自带的软件配置桥接网络。如果要使用OpenVswitch，请看下一章节。

en: In order to forward traffic to your instances you will need at least two bridges: *public* and *private*.
zh_CN: 为了转发流量到实例，至少需要两个桥接网络： *public* 和 *private*。

en: By default these bridges are called *cloudbr0* and *cloudbr1*, but you do have to make sure they are available on each hypervisor.
zh_CN:  默认情况下，这些桥接被称为*cloudbr0*和*cloudbr1*，但必须确保他们在每个hypervisor上都是可用的。

en: The most important factor is that you keep the configuration consistent on all your hypervisors.
zh_CN: 最重要的因素是所有hypervisors上的配置要保持一致。

en: Network example
zh_CN: 网络示例

en: There are many ways to configure your network. In the Basic networking mode you should have two (V)LAN's, one for your private network and one for the public network.
zh_CN: 配置网络有很多方法。在基本网络模式中你应该拥有2个 (V)LAN，一个用于管理网络，一个用于公共网络。

en: We assume that the hypervisor has one NIC (eth0) with three tagged VLAN's:
zh_CN: 假设hypervisor中的网卡(eth0)有3个VLAN标签：

en: VLAN 100 for management of the hypervisor
zh_CN: VLAN 100 作为hypervisor的管理网络

en: VLAN 200 for public network of the instances (cloudbr0)
zh_CN:  VLAN 200 作为实例的公共网络 (cloudbr0)

en: VLAN 300 for private network of the instances (cloudbr1)
zh_CN: VLAN 300 作为实例的专用网络 (cloudbr1)

en: On VLAN 100 we give the Hypervisor the IP-Address 192.168.42.11/24 with the gateway 192.168.42.1
zh_CN: 在VLAN 100 中，配置Hypervisor的IP为 192.168.42.11/24，网关为192.168.42.1

en: The Hypervisor and Management server don't have to be in the same subnet!
zh_CN: Hypervisor与管理服务器不需要在同一个子网！

en: Configuring the network bridges
zh_CN: 配置网络桥接

en: It depends on the distribution you are using how to configure these, below you'll find examples for RHEL/CentOS and Ubuntu.
zh_CN: 配置方式取决于发行版类型，下面给出RHEL/CentOS和Ubuntu的配置示例。

en: The goal is to have two bridges called 'cloudbr0' and 'cloudbr1' after this section. This should be used as a guideline only. The exact configuration will depend on your network layout.
zh_CN: 本章节的目标是配置两个名为 'cloudbr0'和'cloudbr1'的桥接网络。这仅仅是指导性的，实际情况还要取决于你的网络布局。

en: Configure in RHEL or CentOS
zh_CN: 在RHEL或CentOS中配置：

en: The required packages were installed when libvirt was installed, we can proceed to configuring the network.
zh_CN: 网络桥接所需的软件在安装libvirt时就已被安装，继续配置网络。

en: First we configure eth0
zh_CN: 首先配置eth0：

en: Make sure it looks similar to:
zh_CN: 确保内容如下所示：

en: We now have to configure the three VLAN interfaces:
zh_CN: 现在配置3个VLAN接口：

en: Now we have the VLAN interfaces configured we can add the bridges on top of them.
zh_CN: 配置VLAN接口以便能够附加桥接网络。

en: Now we just configure it is a plain bridge without an IP-Address
zh_CN: 现在只配置一个没有IP的桥接。

en: We do the same for cloudbr1
zh_CN: 同样建立cloudbr1

en: With this configuration you should be able to restart the network, although a reboot is recommended to see if everything works properly.
zh_CN: 配置完成之后重启网络，通过重启检查一切是否正常。

en: Make sure you have an alternative way like IPMI or ILO to reach the machine in case you made a configuration error and the network stops functioning!
zh_CN: 在发生配置错误和网络故障的时，请确保可以能通过其他方式例如IPMI或ILO连接到服务器。

en: Configure in Ubuntu
zh_CN: 在Ubuntu中配置：

en: All the required packages were installed when you installed libvirt, so we only have to configure the network.
zh_CN: 在安装libvirt时所需的其他软件也会被安装，所以只需配置网络即可。

en: Modify the interfaces file to look like this:
zh_CN: 如下所示修改接口文件：

en: Configuring the firewall
zh_CN: 配置防火墙

en: The hypervisor needs to be able to communicate with other hypervisors and the management server needs to be able to reach the hypervisor.
zh_CN: hypervisor之间和hypervisor与管理服务器之间要能够通讯。

en: In order to do so we have to open the following TCP ports (if you are using a firewall):
zh_CN: 为了达到这个目的，我们需要开通以下TCP端口(如果使用防火墙)：

en: 5900 - 6100 (VNC consoles)
zh_CN: 5900 - 6100 (VNC 控制台)

en: 49152 - 49216 (libvirt live migration)
zh_CN: 49152 - 49216 (libvirt在线迁移)

en: It depends on the firewall you are using how to open these ports. Below you'll find examples how to open these ports in RHEL/CentOS and Ubuntu.
zh_CN: 如何打开这些端口取决于你使用的发行版本。在RHEL/CentOS 及Ubuntu中的示例如下。

en: Open ports in RHEL/CentOS
zh_CN: 在RHEL/CentOS中打开端口

en: RHEL and CentOS use iptables for firewalling the system, you can open extra ports by executing the following iptable commands:
zh_CN: RHEL 及 CentOS使用iptables作为防火墙，执行以下iptables命令来开启端口：

en: These iptable settings are not persistent accross reboots, we have to save them first.
zh_CN: 这些iptables配置并不会持久保存，重启之后将会消失，我们必须手动保存这些配置。

en: Open ports in Ubuntu
zh_CN: 在Ubuntu中打开端口：

en: The default firewall under Ubuntu is UFW (Uncomplicated FireWall), which is a Python wrapper around iptables.
zh_CN: Ubuntu中的默认防火墙是UFW(Uncomplicated FireWall)，使用Python围绕iptables进行包装。

en: To open the required ports, execute the following commands:
zh_CN: 要打开所需端口，请执行以下命令：

en: By default UFW is not enabled on Ubuntu. Executing these commands with the firewall disabled does not enable the firewall.
zh_CN: 默认情况下，Ubuntu中并未启用UFW。在关闭情况下执行这些命令并不能启用防火墙。

en: Add the host to CloudStack
zh_CN: 添加主机到CloudStack
