Manuel d'utilisation / d'entretien du produit 4.2 du fabricant Citrix Systems
Aller à la page of 194
CloudPlatform (powered by Apache CloudStack) Version 4.2 Installation Guide Revised October 27, 2013 11:15 pm Pacific Citrix CloudPlatform.
CloudPlatform (powered by Apache CloudStack) Version 4.2 Installation Guide CloudPlatform (powered by Apache CloudStack) Version 4.2 Installation Guide Revised October 27, 2013 11:15 pm Pacific Author Citrix CloudPlatform © 2013 Citrix Systems, Inc. All rights reserved.
iii 1. Ge tt in g Mo re In fo rm at io n a nd He lp 1 1. 1. A dd it io na l D oc um en ta ti on Av ai la bl e ............................................................................... 1 1. 2. Ci tr ix Kn ow le dg e C en te r ....................
CloudPlatform (powered by Apache CloudStack) Version 4.2 Installation Guide iv 5. 5. Se tt in g Co nf ig ur at io n Par am et er s ................................................................................ 62 5. 5. 1. A bo ut Co nf ig ur at io n Pa ra me te rs .
v 8.10.1. Configuring Public Network with a Dedicated NIC for XenServer (Optional) ... . . . . 106 8.10.2. Configuring Multiple Guest Networks for XenServer (Optional) .. . . . .. . . . .. . . .. . . . .. . . . 106 8.10.3. Separate Storage Network for XenServer (Optional) .
CloudPlatform (powered by Apache CloudStack) Version 4.2 Installation Guide vi 11 .3 .6 . Cr ea te a Bar e Me ta l Ima ge .......................................................................... 14 0 11 .3 .7 . Cr ea te a B ar e Me ta l Co mp ut e Off er in g .
vii 14 .7 .7 . VM wa re T op ol og y Req uir em en ts .................................................................. 17 4 14 .7 .8 . KV M Top ol og y Re qu ir em en ts ....................................................................... 17 4 14.
viii.
Chapter 1. 1 Getting More Information and Help 1.1. Additional Documentation Available The following guides are available: • Installation Guide — Covers initial installation of CloudPlatform. It aims to cover in full detail all the steps and requirements to obtain a functioning cloud deployment.
2.
Chapter 2. 3 Concepts 2.1. What Is CloudPlatform? CloudPlatform is a software platform that pools computing resources to build public, private, and hybrid Infrastructure as a Service (IaaS) clouds. CloudPlatform manages the network, storage, and compute nodes that make up a cloud infrastructure.
Chapter 2. Concepts 4 Massively Scalable Infrastructure Management CloudPlatform can manage tens of thousands of servers installed in multiple geographically distributed datacenters. The centralized management server scales linearly, eliminating the need for intermediate cluster-level management servers.
Management Server Overview 5 A more full-featured installation consists of a highly-available multi-node Management Server installation and up to thousands of hosts using any of several advanced networking setups. For information about deployment options, see Chapter 13, Choosing a Deployment Architecture .
Chapter 2. Concepts 6 • Pod: A pod is usually one rack of hardware that includes a layer-2 switch and one or more clusters. • Cluster: A cluster consists of one or more hosts and primary storage. • Host: A single compute node within a cluster. The hosts are where the actual cloud services run in the form of guest virtual machines.
Networking Overview 7 • Advanced. For more sophisticated network topologies. This network model provides the most flexibility in defining guest networks and providing guest isolation.
8.
Chapter 3. 9 Cloud Infrastructure Concepts 3.1. About Regions To increase reliability of the cloud, you can optionally group resources into multiple geographic regions. A region is the largest available organizational unit within a CloudPlatform deployment.
Chapter 3. Cloud Infrastructure Concepts 10 The benefit of organizing infrastructure into zones is to provide physical isolation and redundancy. For example, each zone can have its own power supply and network uplink, and the zones can be widely separated geographically (though this is not required).
About Pods 11 For each zone, the administrator must decide the following. • How many pods to place in a zone. • How many clusters to place in each pod.
Chapter 3. Cloud Infrastructure Concepts 12 3.4. About Clusters A cluster provides a way to group hosts. To be precise, a cluster is a XenServer server pool, a set of KVM servers, a set of OVM hosts, or a VMware cluster preconfigured in vCenter.
About Hosts 13 server with CloudPlatform. There may be multiple vCenter servers per zone. Each vCenter server may manage multiple VMware clusters. 3.5. About Hosts A host is a single computer. Hosts provide the computing resources that run guest virtual machines.
Chapter 3. Cloud Infrastructure Concepts 14 • Dell EqualLogic™ for iSCSI • Network Appliances filers for NFS and iSCSI • Scale Computing for NFS If you intend to use only local disk for your installation, you can skip adding separate primary storage.
Basic Zone Network Traffic Types 15 type for each network vary depending on whether you are creating a zone with basic networking or advanced networking. A physical network is the actual network hardware and wiring in a zone. A zone can have multiple physical networks.
Chapter 3. Cloud Infrastructure Concepts 16 you must also configure a network to carry public traffic. CloudPlatform takes care of presenting the necessary network configuration steps to you in the UI when you add a new zone.
Advanced Zone Public IP Addresses 17 3.8.5. Advanced Zone Public IP Addresses When advanced networking is used, the administrator can create additional networks for use by the guests.
18.
Chapter 4. 19 Upgrade Instructions 4.1. Upgrade from 3.0.x to 4.2 Perform the following to upgrade from version 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.
Chapter 4. Upgrade Instructions 20 Hypervisor Description OS Type: Debian GNU/Linux 7.0 (32-bit) (or the highest Debian release number available in the dropdown) Extractable: no Password Enabled: no Public: no Featured: no KVM Name: systemvm-kvm-4.2 Description: systemvm-kvm-4.
Upgrade from 3.0.x to 4.2 21 Hypervisor Description Password Enabled: no Public: no Featured: no e. Watch the screen to be sure that the template downloads successfully and enters the READY state.
Chapter 4. Upgrade Instructions 22 5. Stop all Usage Servers if running. Run this on all Usage Server hosts. # service cloud-usage stop 6. Stop the Management Servers. Run this on all Management Server hosts. # service cloud-management stop 7. On the MySQL master, take a backup of the MySQL databases.
Upgrade from 3.0.x to 4.2 23 Note How will you know whether you need to do this? If the upgrade output in the previous step included a message like the following, then some custom content was found in your old file, and you need to merge the two files: warning: /etc/cloud.
Chapter 4. Upgrade Instructions 24 Note After upgrade from 3.0.4 to 4.2, if the usage server fails to restart then copy db.properties from /etc/cloudstack/management to /etc/cloudstack/usage. Then start the Usage Server. 16. (VMware only) If you are upgrading from 3.
Upgrade from 3.0.x to 4.2 25 update cloud.vmware_data_center set password = < _ciphertext_from_step_i_ > where id = < _id_from_step_v_ >; vii. Confirm that the table is updated: select * from cloud.vmware_data_center; c. Start the CloudPlatform Management server service cloudstack-management start 17.
Chapter 4. Upgrade Instructions 26 # service libvirtd restart i. Start the agent. # service cloudstack-agent start 18. Log in to the CloudPlatform UI as administrator, and check the status of the hosts. All hosts should come to Up state (except those that you know to be offline).
Upgrade from 3.0.x to 4.2 27 The content should be like the following: Stopping and starting 1 secondary storage vm(s)... Done stopping and starting secondary storage vm(s) Stopping and starting 1 console proxy vm(s)... Done stopping and starting console proxy vm(s).
Chapter 4. Upgrade Instructions 28 23. (VMware only) After upgrade, if you want to change a Standard vSwitch zone to a VMware dvSwitch Zone, perform the following: a. Ensure that the Public and Guest traffics are not on the same network as the Management and Storage traffic.
Upgrade from 2.2.x to 4.2 29 Starting in 3.0.2, the usage record format for IP addresses is the same as the rest of the usage types. Instead of a single record with the assignment and release dates, separate records are generated per aggregation period with start and end dates.
Chapter 4. Upgrade Instructions 30 Hypervisor Description Zone: Choose the zone where this hypervisor is used. If your CloudPlatform deployment includes multiple zones running XenServer, choose All Zones to make the template available in all the XenServer zones.
Upgrade from 2.2.x to 4.2 31 Hypervisor Description VMware, choose All Zones to make the template available in all the VMware zones. Hypervisor: VMware Format: OVA OS Type: Debian GNU/Linux 7.0 (32-bit) (or the highest Debian release number available in the dropdown) Extractable: no Password Enabled: no Public: no Featured: no e.
Chapter 4. Upgrade Instructions 32 enabled=1 gpgcheck=0 [cloudstack] name=cloudstack baseurl=file:///root/CloudPlatform-4.2.0-1-rhel6.3/6.3 enabled=1 gpgcheck=0 e. Upgrade the host operating system from RHEL 6.0 to 6.3: yum upgrade 6. Stop all Usage Servers if running.
Upgrade from 2.2.x to 4.2 33 12. Choose "U" to upgrade the package. > U 13. If you have made changes to your existing copy of the configuration files components.xml, db.properties, or server.xml in your previous-version CloudPlatform installation, the changes will be preserved in the upgrade.
Chapter 4. Upgrade Instructions 34 • (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudPlatform database. Default: password. It is highly recommended that you replace this with a more secure value.
Upgrade from 2.2.x to 4.2 35 g. Install a libvirt hook with the following commands: # mkdir /etc/libvirt/hooks # cp /usr/share/cloudstack-agent/lib/libvirtqemuhook /etc/libvirt/hooks/qemu # chmod +x /etc/libvirt/hooks/qemu h. Restart libvirtd. # service libvirtd restart i.
Chapter 4. Upgrade Instructions 36 XenServer or KVM: SSH in by using the link local IP address of the system VM. For example, in the command below, substitute your own path to the private key used to log in to the system VM and your own link local IP.
Upgrade from 2.1.x to 4.2 37 Note (VMware only) After upgrade, whenever you add a new VMware cluster to a zone that was created with a previous version of CloudPlatform, the fields vCenter host, vCenter Username, vCenter Password, and vCenter Datacenter are required.
Chapter 4. Upgrade Instructions 38 Note In the latest XenServer upgrade procedure, even after putting the master host into maintenance mode, the master host continues to stay as master. Any VMs running on this master will be automatically migrated to other hosts, unless there is only one UP host in the cluster.
Applying Hotfixes to a XenServer Cluster 39 • If you upgraded from XenServer 5.6 SP2 to XenServer 6.0.2 or higher, change any VMs that have the OS type CentOS 5.6 (32-bit), CentOS 5.7 (32-bit), Oracle Enterprise Linux 5.6 (32- bit), Oracle Enterprise Linux 5.
Chapter 4. Upgrade Instructions 40 xe patch-upload file-name=XS602E015.xsupdate The command displays the UUID of the update file: 33af688e-d18c-493d-922b-ec51ea23cfe9 ii. Repeat the xe patch-upload command for all other XenServer updates: XS602E004.xsupdate, XS602E005.
Applying Hotfixes to a XenServer Cluster 41 11. You might need to change the OS type settings for VMs running on the upgraded hosts, if any of the following apply: • If you upgraded from XenServer 5.6 SP2 to XenServer 6.0.2, change any VMs that have the OS type CentOS 5.
42.
Chapter 5. 43 Installation 5.1. Who Should Read This These installation instructions are intended for those who are ready to set up a full production deployment. If you only need to set up a trial installation, you will probably find more detail than you need here.
Chapter 5. Installation 44 5.3. Minimum System Requirements 5.3.1. Management Server, Database, and Storage System Requirements The machines that will run the Management Server and MySQL database must meet the following requirements. The same machines can also be used to provide primary and secondary storage, such as via local disk or NFS.
Hypervisor Compatibility Matrix 45 • All hosts within a cluster must be homogenous. The CPUs must be of the same type, count, and feature flags. Hosts have additional requirements depending on the hypervisor.
Chapter 5. Installation 46 5.3.3.2. CloudPlatform 3.x 3.0.0 3.0.1 3.0.2 3.0.3 3.0.4 3.0.5 3.0.6 3.0.7 XenServer 5.6 No No No No No No No No XenServer 5.6 FP1 No No Yes Yes Yes Yes Yes Yes XenServer 5.6 SP2 No No Yes Yes Yes Yes Yes Yes XenServer 6.0.0 No No No No No No No No XenServer 6.
Management Server Installation 47 2.1.x 2.2.x VMware ESX 5 and vCenter 5 No No 5.4. Management Server Installation 5.4.1. Management Server Installation Overview This section describes installing the Management Server.
Chapter 5. Installation 48 In RHEL, SELinux is installed and enabled by default. You can verify this with: # rpm -qa | grep selinux b. Set the SELINUX variable in /etc/selinux/config to “permissive”. This ensures that the permissive setting will be maintained after a system reboot.
Install the Management Server on the First Host 49 server 0.xenserver.pool.ntp.org server 1.xenserver.pool.ntp.org server 2.xenserver.pool.ntp.org server 3.xenserver.pool.ntp.org c. Restart the NTP client. # service ntpd restart d. Make sure NTP will start again upon reboot.
Chapter 5. Installation 50 4. When the installation is finished, run the following commands to start essential services: # service rpcbind start # service nfs start # chkconfig nfs on # chkconfig rpcbind on 5. Continue to Section 5.4.4, “Install and Configure the Database” .
Install and Configure the Database 51 The max_connections parameter should be set to 350 multiplied by the number of Management Servers you are deploying.
Chapter 5. Installation 52 8. Set up the database. The following command creates the cloud user on the database. • In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password. • In deploy-as, specify the username and password of the user deploying the database.
Install and Configure the Database 53 # yum install mysql-server # chkconfig --level 35 mysqld on 3. Edit the MySQL configuration (/etc/my.cnf or /etc/mysql/my.cnf, depending on your OS) and insert the following lines in the [mysqld] section. You can put these lines below the datadir line.
Chapter 5. Installation 54 d. Edit the /etc/sysconfig/iptables file and add the following lines at the beginning of the INPUT chain. -A INPUT -p tcp --dport 3306 -j ACCEPT 7. Return to the root shell on your first Management Server. 8. Set up the database.
Changing the Default Password Encryption 55 • VPN password • User API secret key • VNC password CloudPlatform uses the Java Simplified Encryption (JASYPT) library. The data values are encrypted and decrypted using a database secret key, which is stored in one of CloudPlatform’s internal properties files along with the database password.
Chapter 5. Installation 56 <ref bean="SHA256SaltedUserAuthenticator"/> <ref bean="MD5UserAuthenticator"/> <ref bean="LDAPUserAuthenticator"/> <ref be.
Prepare NFS Shares 57 # mkdir -p /export/primary # mkdir -p /export/secondary 2. To configure the new directories as NFS exports, edit /etc/exports. Export the NFS share(s) with rw,async,no_root_squash. For example: # vi /etc/exports Insert the following line.
Chapter 5. Installation 58 /export *(rw,async,no_root_squash) 3. Export the /export directory. # exportfs -a 4. Edit the /etc/sysconfig/nfs file. # vi /etc/sysconfig/nfs Uncomment the following lines: LOCKD_TCPPORT=32803 LOCKD_UDPPORT=32769 MOUNTD_PORT=892 RQUOTAD_PORT=875 STATD_PORT=662 STATD_OUTGOING_PORT=2020 5.
Prepare and Start Additional Management Servers 59 Domain = company.com 8. Reboot the Management Server host. Two NFS shares called /export/primary and /export/secondary are now set up. 9. It is recommended that you test to be sure the previous steps have been successful.
Chapter 5. Installation 60 # tar xzf CloudPlatform-VERSION-N-OSVERSION.tar.gz # cd CloudPlatform-VERSION-N-OSVERSION # ./install.sh You should see a few messages as the installer prepares, followed by a list of choices. 4. Choose M to install the Management Server software.
Prepare the System VM Template 61 Source Port Destination Port Protocol Persistence Required? 80 or 443 8080 (or 20400 with AJP) HTTP (or AJP) Yes 8250 8250 TCP Yes 8096 8096 HTTP No In addition to ab.
Chapter 5. Installation 62 2. If you are using a separate NFS server, perform this step. If you are using the Management Server as the NFS server, you MUST NOT perform this step. When the script has finished, unmount secondary storage and remove the created directory.
About Configuration Parameters 63 Field Value management.network.cidr A CIDR that describes the network that the management CIDRs reside on. This variable must be set for deployments that use vSphere. It is recommended to be set for other deployments as well.
Chapter 5. Installation 64 Field Value to ha_host. Specify the ha.tag value as a host tag when you add a new host to the cloud. 5.5.2. Setting Global Configuration Parameters Use the following steps to set global configuration parameters. These values will be the defaults in effect throughout your CloudPlatform deployment.
Granular Global Configuration Parameters 65 Field Field Value account allow.public.user.templates If false, users will not be able to create public templates.
Chapter 5. Installation 66 Field Field Value Keep the corresponding notification threshold lower than this value to be notified beforehand. cluster cpu.overprovisioning.factor Used for CPU over- provisioning calculation; the available CPU will be the mathematical product of actualCpuCapacity and cpu.
Granular Global Configuration Parameters 67 Field Field Value zone router.template.kvm Name of the default router template on KVM. zone router.template.vmware Name of the default router template on VMware. zone enable.dynamic.scale.vm Enable or diable dynamically scaling of a VM.
68.
Chapter 6. 69 User Interface 6.1. Supported Browsers The CloudPlatform web-based UI is available in the following popular browsers: • Mozilla Firefox 22 or greater • Apple Safari, all versions packaged with Mac OS X 10.
Chapter 6. User Interface 70 6.2.2. Root Administrator's UI Overview The CloudPlatform UI helps the CloudPlatform administrator provision, view, and manage the cloud infrastructure, domains, user accounts, projects, and configuration settings.
Changing the Root Password 71 Warning You are logging in as the root administrator. This account manages the CloudPlatform deployment, including physical infrastructure.
Chapter 6. User Interface 72 For more information on creating a new instance, see Creating VMs in the Administration Guide. 2. Download the script file cloud-set-guest-sshkey from the following link: http://download.cloud.com/templates/4.2/bindir/cloud-set-guest-sshkey.
Creating an Instance 73 2. Copy the key data into a file. The file looks like this: -----BEGIN RSA PRIVATE KEY----- MIICXQIBAAKBgQCSydmnQ67jP6lNoXdX3noZjQdrMAWNQZ7y5SrEu4wDxplvhYci dXYBeZVwakDVsU2MLGl.
74.
Chapter 7. 75 Steps to Provisioning Your Cloud Infrastructure This section tells how to add regions, zones, pods, clusters, hosts, storage, and networks to your cloud. If you are unfamiliar with these entities, please begin by looking through Chapter 3, Cloud Infrastructure Concepts .
Chapter 7. Steps to Provisioning Your Cloud Infrastructure 76 7.2. Adding Regions (optional) Grouping your cloud resources into geographic regions is an optional step when provisioning the cloud. For an overview of regions, see Section 3.1, “About Regions” .
Adding Third and Subsequent Regions 77 3. Now add the new region to region 1 in CloudPlatform. a. Log in to CloudPlatform in the first region as root administrator (that is, log in to <region.1.IP.address>:8080/client). b. In the left navigation bar, click Regions.
Chapter 7. Steps to Provisioning Your Cloud Infrastructure 78 2. Once the Management Server is running, add your new region to all existing regions by repeatedly using the Add Region button in the UI. For example, if you were adding region 3: a. Log in to CloudPlatform in the first region as root administrator (that is, log in to <region.
Adding a Zone 79 2. In the left navigation bar, click Regions. 3. Click the name of the region you want to delete. 4. Click the Remove Region button. 5. Repeat these steps for <region.2.IP.address>:8080/client. 7.3. Adding a Zone Adding a zone consists of three phases: • Create a mount point for secondary storage on the Management Server.
Chapter 7. Steps to Provisioning Your Cloud Infrastructure 80 • Advanced. For more sophisticated network topologies. This network model provides the most flexibility in defining guest networks and providing custom network offerings such as firewall, VPN, or load balancer support.
Steps to Add a New Zone 81 • Public. A public zone is available to all users. A zone that is not public will be assigned to a particular domain. Only users in that domain will be allowed to create guest VMs in this zone. 2. Choose which traffic types will be carried by the physical network.
Chapter 7. Steps to Provisioning Your Cloud Infrastructure 82 7. In a new zone, CloudPlatform adds the first pod for you. You can always add more pods later. For an overview of what a pod is, see Section 3.3, “About Pods” . To configure the first pod, enter the following, then click Next: • Pod Name.
Steps to Add a New Zone 83 • Citrix XenServer Installation and Configuration • VMware vSphere Installation and Configuration • KVM vSphere Installation and Configuration • Oracle VM (OVM) Installation and Configuration To configure the first host, enter the following, then click Next: • Host Name.
Chapter 7. Steps to Provisioning Your Cloud Infrastructure 84 • Hypervisor. Choose the hypervisor for the first cluster in the zone. You can add clusters with different hypervisors later, after you finish adding the zone. • Public. A public zone is available to all users.
Steps to Add a New Zone 85 4. Click Next. 5. Configure the IP range for public Internet traffic. Enter the following details, then click Add. If desired, you can repeat this step to add more public Internet IP ranges. When done, click Next. • Gateway.
Chapter 7. Steps to Provisioning Your Cloud Infrastructure 86 • Start/End Reserved System IP. The IP range in the management network that CloudPlatform uses to manage various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP. For more information, see Section 3.
Steps to Add a New Zone 87 more information, see HA-Enabled Virtual Machines as well as HA for Hosts, both in the Administration Guide. 10. In a new cluster, CloudPlatform adds the first primary storage server for you. You can always add more servers later.
Chapter 7. Steps to Provisioning Your Cloud Infrastructure 88 SharedMountPoint • Path. The path on each host that is where this primary storage is mounted. For example, "/mnt/primary". • Tags (optional). The comma-separated list of tags for this storage device.
Adding a Cluster 89 5. Enter the following details in the dialog. • Name. The name of the pod. • Gateway. The gateway for the hosts in that pod. • Netmask. The network prefix that defines the pod's subnet. Use CIDR notation. • Start/End Reserved System IP.
Chapter 7. Steps to Provisioning Your Cloud Infrastructure 90 3. Click the Compute tab. In the Pods node, click View All. Select the same pod you used in step 1. 4. Click View Clusters, then click Add Cluster. The Add Cluster dialog is displayed. 5. In Hypervisor, choose OVM.
Add Cluster: vSphere 91 2. Log in to the UI. 3. In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone in which you want to add the cluster. 4. Click the Compute tab, and click View All on Pods. Choose the pod to which you want to add the cluster.
Chapter 7. Steps to Provisioning Your Cloud Infrastructure 92 If you have enabled Nexus dvSwitch in the environment, the following parameters for dvSwitch configuration are displayed: • Nexus dvSwitch IP Address: The IP address of the Nexus VSM appliance.
Adding a Host 93 7.6. Adding a Host 1. Before adding a host to the CloudPlatform configuration, you must first install your chosen hypervisor on the host.
Chapter 7. Steps to Provisioning Your Cloud Infrastructure 94 For all additional hosts to be added to the cluster, run the following command. This will cause the host to join the master in a XenServer pool.
Adding a Host (vSphere) 95 7. Click Add Host. 8. Provide the following information. • Host Name. The DNS name or IP address of the host. • Username. Usually root. • Password. This is the password for the user named above (from your XenServer, KVM, or OVM install).
Chapter 7. Steps to Provisioning Your Cloud Infrastructure 96 • Pod. (Visible only if you choose Cluster in the Scope field.) The pod for the storage device. • Cluster. (Visible only if you choose Cluster in the Scope field.) The cluster for the storage device.
Adding an NFS Secondary Staging Store for Each Zone 97 3. Log in to the CloudPlatform UI as root administrator. 4. In the left navigation bar, click Infrastructure. 5. In Secondary Storage, click View All. 6. Click Add Secondary Storage. 7. Fill in the following fields: • Name.
Chapter 7. Steps to Provisioning Your Cloud Infrastructure 98 5. In Secondary Storage, click View All. 6. In Select View, choose Secondary Staging Store. 7. Click the Add NFS Secondary Staging Store button. 8. Fill out the dialog box fields, then click OK: • Zone.
Initialize and Test 99 If you decide to grow your deployment, you can add more hosts, primary storage, zones, pods, and clusters..
100.
Chapter 8. 101 Installing XenServer for CloudPlatform If you want to use the Citrix XenServer hypervisor to run guest virtual machines, install XenServer on the host(s) in your cloud. For an initial installation, follow the steps below. If you have previously installed XenServer and want to upgrade to another version, see Section 4.
Chapter 8. Installing XenServer for CloudPlatform 102 8.2. XenServer Installation Steps 1. From https://www.citrix.com/English/ss/downloads/ , download the appropriate version of XenServer for your CloudPlatform version (see Section 8.1, “System Requirements for XenServer Hosts” ).
Licensing 103 3. Restart the NTP client. # service ntpd restart 4. Make sure NTP will start again upon reboot. # chkconfig ntpd on 8.6. Licensing Citrix XenServer Free version provides 30 days usage without a license. Following the 30 day trial, XenServer requires a free activation and license.
Chapter 8. Installing XenServer for CloudPlatform 104 # xe-install-supplemental-pack xenserver-cloud-supp.iso 2. If the XenServer host is part of a zone that uses basic networking, disable Open vSwitch (OVS): # xe-switch-network-backend bridge Restart the host machine when prompted.
iSCSI Multipath Setup for XenServer (Optional) 105 lrwxrwxrwx 1 root root 9 Mar 16 13:47 /dev/disk/by-id/scsi-360a98000503365344e6f6177615a516b -> ../../sdc 5. Repeat step 4 on every host. 6. On the storage server, run this command to get a unique ID for the new SR.
Chapter 8. Installing XenServer for CloudPlatform 106 Make note of the values you will need when you add this storage to the CloudPlatform later (see Section 7.7, “Adding Primary Storage” ). In the Add Primary Storage dialog, in Protocol, you will choose PreSetup.
Separate Storage Network for XenServer (Optional) 107 labels "cloud-guest" and "cloud-guest2". After the management server is installed and running, you must add the networks and use these labels so that CloudPlatform is aware of the networks.
Chapter 8. Installing XenServer for CloudPlatform 108 • 2 NICs on private, 2 NICs on public, storage uses management network • 1 NIC for private, public, and storage All NIC bonding is optional. XenServer expects all nodes in a cluster will have the same network cabling and same bonds implemented.
NIC Bonding for XenServer (Optional) 109 1. Find the physical NICs that you want to bond together. #xe pif-list host-name-label='hostname' device=eth2 # xe pif-list host-name-label='hostname' device=eth3 These command shows the eth2 and eth3 NICs and their UUIDs.
110.
Chapter 9. 111 Installing KVM for CloudPlatform If you want to use the Linux Kernel Virtual Machine (KVM) hypervisor to run guest virtual machines, install KVM on the host(s) in your cloud. The material in this section doesn't duplicate KVM installation documentation.
Chapter 9. Installing KVM for CloudPlatform 112 patches. It is essential that your hosts are completely up to date with the provided hypervisor patches. The hypervisor vendor is likely to refuse to support any system that is not up to date with patches.
Physical Network Configuration for KVM 113 c. Create a repo file at /etc/yum.repos.d/rhel6.repo. In the file, insert the following lines: [rhel] name=rhel6 baseurl=file:///media enabled=1 gpgcheck=0 4. Install the CloudPlatform packages. You should have a file in the form of “CloudPlatform- VERSION-N-OSVERSION.
Chapter 9. Installing KVM for CloudPlatform 114 • private.network.device These should be set to the name of the bridge that the user created for the respective traffic type. For example: • public.network.device=publicbondbr0 9.5. Time Synchronization for KVM Hosts The host must be set to use NTP.
Primary Storage Setup for KVM (Optional) 115 • Each node in the KVM cluster mounts the storage in the same local location (e.g., /mnt/primary) • A shared clustered file system is used • The admi.
116.
Chapter 10. 117 Installing VMware for CloudPlatform If you want to use the VMware vSphere hypervisor to run guest virtual machines, install vSphere on the host(s) in your cloud. 10.1. System Requirements for vSphere Hosts 10.1.1. Software requirements • vSphere and vCenter, both version 5.
Chapter 10. Installing VMware for CloudPlatform 118 10.1.3. vCenter Server requirements: • Processor - 2 CPUs 2.0GHz or higher Intel or AMD x86 processors. Processor requirements may be higher if the database runs on the same machine. • Memory - 3GB RAM.
Preparation Checklist for VMware 119 10.2. Preparation Checklist for VMware For a smoother installation, gather the following information before you start: • Information listed in Section 10.2.1, “vCenter Checklist” • Information listed in Section 10.
Chapter 10. Installing VMware for CloudPlatform 120 10.3. vSphere Installation Steps 1. If you haven't already, you'll need to download and purchase vSphere from the VMware Website ( https://www.vmware.com/tryvmware/index.php?p=vmware-vsphere&lp=1 ) and install it by following the VMware vSphere Installation Guide.
Configure vCenter Management Network 121 10.5.1.2. Increasing Ports By default a virtual switch on ESXi hosts is created with 56 ports. We recommend setting it to 4088, the maximum number of ports allowed. To do that, click the "Properties..." link for virtual switch (note this is not the Properties link for Networking).
Chapter 10. Installing VMware for CloudPlatform 122 10.6. Configuring a vSphere Cluster with Nexus 1000v Virtual Switch CloudPlatform supports Cisco Nexus 1000v dvSwitch (Distributed Virtual Switch) for virtual network configuration in a VMware vSphere environment.
Nexus 1000v Virtual Switch Preconfiguration 123 • All information given in Section 10.6.3, “Nexus 1000v Virtual Switch Preconfiguration” 10.6.3. Nexus 1000v Virtual Switch Preconfiguration 10.
Chapter 10. Installing VMware for CloudPlatform 124 Network Requirements Value Notes establish and maintain the connection between the VSM and VMware vCenter Server. Packet Port Group VLAN ID The VLAN ID of the Packet Port Group. The packet VLAN forwards relevant data packets from the VEMs to the VSM.
Nexus 1000v Virtual Switch Preconfiguration 125 • The Ethernet port profile created to represent the physical network or networks used by an Advanced zone configuration trunk all the VLANs including guest VLANs, the VLANs that serve the native VLAN, and the packet/control/data/management VLANs of the VSM.
Chapter 10. Installing VMware for CloudPlatform 126 Note Before you run the vlan command, ensure that the configuration mode is enabled in Nexus 1000v virtual switch.
Removing Nexus Virtual Switch 127 Parameters Description vCenter Password Enter the password for the user named above. vCenter Datacenter Enter the vCenter datacenter that the cluster is in. For example, "cloud.dc.VM". Nexus dvSwitch IP Address The IP address of the VSM component of the Nexus 1000v virtual switch.
Chapter 10. Installing VMware for CloudPlatform 128 • VMware VDS does not support multiple VDS per traffic type. If a user has many VDS switches, only one can be used for Guest traffic and another one for Public traffic. • Additional switches of any type can be added for each cluster in the same zone.
Configuring a VMware Datacenter with VMware Distributed Virtual Switch 129 • The Public Traffic vSwitch Type field when you add a VMware VDS-enabled cluster.
Chapter 10. Installing VMware for CloudPlatform 130 Fields Name Description would be ignored and could be left empty for guest traffic. By default empty string would be assumed which translates to untagged VLAN for that specific traffic type. 3 Type of virtual switch.
Configuring a VMware Datacenter with VMware Distributed Virtual Switch 131 you enable the vmware.use.dvswitch parameter, you cannot see any UI options specific to VDS, and CloudPlatform ignores the VDS-specific parameters that you specify. Additionally, CloudPlatform uses VDS for virtual network infrastructure if the value of vmware.
Chapter 10. Installing VMware for CloudPlatform 132 Parameters Description vCenter User name Enter the username that CloudPlatform should use to connect to vCenter. This user must have all administrative privileges. vCenter Password Enter the password for the user named above.
Create an iSCSI datastore 133 Repeat these steps for all ESXi hosts in the cluster. 10.7.3. Create an iSCSI datastore You should now create a VMFS datastore. Follow these steps to do so: 1. Select Home/Inventory/Datastores. 2. Right click on the datacenter node.
134.
Chapter 11. 135 Bare Metal Installation You can set up bare metal hosts in a CloudPlatform cloud and manage them with the Management Server. Bare metal hosts do not run hypervisor software.
Chapter 11. Bare Metal Installation 136 Example: Section 11.3.18, “Example CentOS 6.x Kickstart File” • Ubuntu Docs: https://help.ubuntu.com/lts/installation-guide/i386/automatic-install.html Example: Section 11.3.20, “Example Ubuntu 12.04 Kickstart File” 11.
Enable PXE on the Bare Metal Host 137 Once you are there, set the following: • IP address of IPMI NIC • Netmask • Gateway • Username and password for IPMI NIC CloudPlatform uses ipmitool to control the lifecycle of baremetal hosts. By default, ipmitool uses the interface 'lan' to issue ipmi commands.
Chapter 11. Bare Metal Installation 138 You should see a few messages as the installer prepares, followed by a list of choices. 4. Choose “B” to install the software that is needed for bare metal. > B 5. Run the bare metal setup script. # cloudstack-setup-baremetal 6.
Set Up a File Server 139 • sync: exportfs notify client when file write is complete instead of async notify Warning Be careful with space characters in these NFS configuration files. They must be used exactly as shown in the syntax. 2. In /etc/hosts.
Chapter 11. Bare Metal Installation 140 • rpc.lockd • rpc.rquotad 11.3.6. Create a Bare Metal Image Create an image which can be installed on bare metal hosts later, when bare metal instances are provisioned in your cloud. On the NFS file server, create a folder and put a PXE bootable kernel and initrd in it.
Create a Bare Metal Network Offering 141 11.3.8. Create a Bare Metal Network Offering 1. Log in as admin to the CloudPlatform UI. 2. In the left navigation bar, click Service Offerings. 3. In Select Offering, choose Network Offering. 4. Click Add Network Offering.
Chapter 11. Bare Metal Installation 142 • python-cherrypy: A Python HTTP server which is distributed by default with most Linux distributions. For example, both CentOS and Ubuntu have this package. • ipset: An iptables tool which provides ipset match.
(Optional) Set Bare Metal Configuration Parameters 143 11.3.10. (Optional) Set Bare Metal Configuration Parameters 1. Log in as admin to the CloudPlatform UI. Click Global Settings. Make any desired modifications to the bare metal configuration parameters.
Chapter 11. Bare Metal Installation 144 9. In a new zone, CloudPlatform adds the first pod for you. You can always add more pods later. To configure the first pod, enter the following: • Pod Name. A name for the pod. • Reserved system gateway. The gateway for the hosts in that pod.
Add the PXE Server and DHCP Server to Your Deployment 145 3. Click the Compute and Storage tab. In Clusters, click View All, then click the name of the bare metal cluster you added earlier. 4. Click View Hosts. 5. Click the Add Host button. The Add Host dialog will appear.
Chapter 11. Bare Metal Installation 146 7. In the list of Network service providers, click Baremetal DHCP. In the Details node, click Add Baremetal DHCP Device button.
Provision a Bare Metal Instance 147 • Featured. Choose Yes if you would like this template to be more prominent for users to select. Only administrators may make templates featured. 11.3.16. Provision a Bare Metal Instance Deploy one bare metal instance per host using these steps.
Chapter 11. Bare Metal Installation 148 selinux --permissive timezone --utc Europe/London bootloader --location=mbr --driveorder=sda clearpart --initlabel --linux --drives=sda part /boot --fstype ext3 --size=500 --ondisk=sda part pv.2 --size=1 --grow --ondisk=sda volgroup vg00 --pesize=32768 pv.
Example Ubuntu 12.04 Kickstart File 149 # SELinux #selinux --enforcing selinux --permissive # Services running at boot services --enabled network,sshd services --disabled sendmail # Disable anything g.
Chapter 11. Bare Metal Installation 150 mouse #System timezone timezone America/New_York #Root password rootpw --iscrypted password #Initial user user --disabled #Reboot after installation reboot #Use text mode install text #Install OS instead of upgrade install # Use network installation url --url=http://10.
Using Cisco UCS as Bare Metal Host CloudPlatform 151 %pre #services services --enabled=ntpd,nscd,puppet #Package install information %packages ubuntu-standard man-db wget postfix openssh-server sysstat nfs-common nscd postfix quota ntp %post 11.
Chapter 11. Bare Metal Installation 152 • UCS manager IP address • UCS manager username • UCS manager password 2. Log in to the CloudPlatform UI as administrator. 3. In the left navigation bar, click Infrastructure, then click Zones. 4. Click the name of a zone where Network Type is Basic.
Disassociating a Profile from a UCS Blade 153 11.4.3. Disassociating a Profile from a UCS Blade 1. Log in to the CloudPlatform UI as administrator. 2. In the left navigation bar, click Infrastructure, then click Zones. 3. Click the name of a zone where you have registered a UCS Manager.
154.
Chapter 12. 155 Installing Oracle VM (OVM) for CloudPlatform If you want to use the Oracle VM Server (OVM) hypervisor to run guest virtual machines, install OVM on the host(s) in your cloud. 12.1. System Requirements for OVM Hosts CloudPlatform works with the following version: • OVM Server 2.
Chapter 12. Installing Oracle VM (OVM) for CloudPlatform 156 4. Repeat for any additional hosts that will be part of the OVM cluster. Note After ISO installation, the installer reboots into the operating system. Due to a known issue in OVM Server, the reboot will place the VM in the Stopped state.
Chapter 13. 157 Choosing a Deployment Architecture The architecture used in a deployment will vary depending on the size and purpose of the deployment.
Chapter 13. Choosing a Deployment Architecture 158 13.2. Large-Scale Redundant Setup This diagram illustrates the network architecture of a large-scale CloudPlatform deployment. • A layer-3 switching layer is at the core of the data center. A router redundancy protocol like VRRP should be deployed.
Separate Storage Network 159 • The Management Server cluster (including front-end load balancers, Management Server nodes, and the MySQL database) is connected to the management network through a pair of load balancers. • Secondary storage servers are connected to the management network.
160.
Chapter 14. 161 Network Setup Achieving the correct networking setup is crucial to a successful CloudPlatform installation. This section contains information to help you make decisions and follow the right procedures to get your network set up correctly.
Chapter 14. Network Setup 162 14.2. VLAN Allocation Example VLANs are required for public and guest traffic. The following is an example of a VLAN allocation scheme: VLAN IDs Traffic type Scope less than 500 Management traffic. Reserved for administrative purposes.
Cisco 3750 163 • All VLANs (300-999) are passed to all the pod-level layer-2 switches. 14.3.2. Cisco 3750 The following steps show how a Cisco 3750 is configured for zone-level layer-3 switching. These steps assume VLAN 201 is used to route untagged private IPs for pod 1, and pod 1’s layer-2 switch is connected to GigabitEthernet1/0/1.
Chapter 14. Network Setup 164 2. VLAN 201 is used to route untagged private IP addresses for pod 1, and pod 1 is connected to this layer-2 switch. interface range ethernet all switchport mode general .
External Guest Firewall Integration for Juniper SRX (Optional) 165 To achieve the above purposes you must set up fixed configurations for the firewall. Firewall rules and policies need not change as users are provisioned into the cloud. Any brand of hardware firewall that supports NAT and site-to-site VPN can be used.
Chapter 14. Network Setup 166 8. Make sure the "ssh" and "xnm-clear-text" system services are enabled. 9. If traffic metering is desired: a. a. Create an incoming firewall filter and an outgoing firewall filter. These filters should be the same names as your public security zone name and private security zone name respectively.
External Guest Firewall Integration for Cisco VNMC (Optional) 167 • Public Interface. The name of the public interface on the SRX. For example, ge-0/0/2. A ".x" at the end of the interface indicates the VLAN that is in use. • Private Interface: The name of the private interface on the SRX.
Chapter 14. Network Setup 168 • When a guest network is created with Cisco VNMC firewall provider, an additional public IP is acquired along with the Source NAT IP. The Source NAT IP is used for the rules, whereas the additional IP is used to for the ASA outside interface.
External Guest Firewall Integration for Cisco VNMC (Optional) 169 For more information, see Section 10.6, “Configuring a vSphere Cluster with Nexus 1000v Virtual Switch” . 5. Deploy and Cisco ASA 1000v appliance. For more information, see Setting Up the ASA 1000V Using VNMC 4 .
Chapter 14. Network Setup 170 2. In the left navigation bar, click Infrastructure. 3. In Zones, click View More. 4. Choose the zone you want to work with. 5. Click the Physical Network tab. 6. In the Network Service Providers node of the diagram, click Configure.
External Guest Firewall Integration for Cisco VNMC (Optional) 171 14.5.3.4. Creating a Network Offering Using Cisco ASA 1000v To have Cisco ASA 1000v support for a guest network, create a network offering as follows: 1. Log in to the CloudPlatform UI as a user or admin.
Chapter 14. Network Setup 172 You are prompted with the following message: System config has been modified. Save? [Y]es/[N]o:" b. Enter N. You will get the following confirmation message: "Proceed with reload? [confirm]" c. Restart the appliance.
Topology Requirements 173 • IP Address: The IP address of the NetScaler. • Username/Password: The authentication credentials to access the device. CloudPlatform uses these credentials to access the device. • Type: The type of device that is being added.
Chapter 14. Network Setup 174 14.7.3. Storage Network Topology Requirements The secondary storage NFS export is mounted by the secondary storage VM. Secondary storage traffic goes over the management traffic network, even if there is a separate storage network.
Setting Zone VLAN and Running VM Maximums 175 To set up the integration between CloudPlatform and Traffic Sentinel: 1. On your network infrastructure, install Traffic Sentinel and configure it to gather traffic data. For installation and configuration steps, see inMon documentation at Traffic Sentinel Documentation 5 .
176.
Chapter 15. 177 Amazon Web Service Interface 15.1. Amazon Web Services EC2 Compatible Interface CloudPlatform can translate Amazon Web Services (AWS) API calls to native CloudPlatform API calls so that users can continue using existing AWS-compatible tools.
Chapter 15. Amazon Web Service Interface 178 4. (Optional) The AWS API listens for requests on port 7080. If you prefer AWS API to listen on another port, you can change it as follows: a. Edit the files /etc/cloudstack/management/server.xml, /etc/cloudstack/management/server- nonssl.
AWS API Command-Line Tools Setup 179 $ cloudstack-aws-api-register --apikey= User’s CloudPlatform API key -- secretkey= User’s CloudPlatform Secret key --cert= /path/to/cert.
Chapter 15. Amazon Web Service Interface 180 EC2 command SOAP / REST call CloudPlatform API call The noReboot parameter is not supported. ec2-deregister DeregisterImage DeleteTemplate ec2-describe-images DescribeImages listTemplates ec2-register For the optional parameter architecture , use the CloudPlatform format rather than the EC2 format.
Supported AWS API Calls 181 EC2 command SOAP / REST call CloudPlatform API call Known issue: The CloudPlatform device ID of 0, which represents a root volume, does not map to any EC2 device name to be returned in the command response.
Chapter 15. Amazon Web Service Interface 182 EC2 command SOAP / REST call CloudPlatform API call ec2-delete-tags DeleteTags Remove tags from one or more resources.
Chapter 16. 183 Additional Installation Options The next few sections describe CloudPlatform features above and beyond the basic deployment options. 16.1. Installing the Usage Server (Optional) You can optionally install the Usage Server once the Management Server is configured properly.
Chapter 16. Additional Installation Options 184 CloudPlatform uses Tomcat as its servlet container. For sites that would like CloudPlatform to terminate the SSL session, Tomcat’s SSL access may be enabled. Tomcat SSL configuration is described at http://tomcat.
Database Replication (Optional) 185 # mysql -u root mysql> show master status; +------------------+----------+--------------+------------------+ | File | Position | Binlog_Do_DB | Binlog_Ignore_DB | +------------------+----------+--------------+------------------+ | mysql-bin.
Chapter 16. Additional Installation Options 186 16.3.1. Failover This will provide for a replicated database that can be used to implement manual failover for the Management Servers. CloudPlatform failover from one MySQL instance to another is performed by the administrator.
Un point important après l'achat de l'appareil (ou même avant l'achat) est de lire le manuel d'utilisation. Nous devons le faire pour quelques raisons simples:
Si vous n'avez pas encore acheté Citrix Systems 4.2 c'est un bon moment pour vous familiariser avec les données de base sur le produit. Consulter d'abord les pages initiales du manuel d'utilisation, que vous trouverez ci-dessus. Vous devriez y trouver les données techniques les plus importants du Citrix Systems 4.2 - de cette manière, vous pouvez vérifier si l'équipement répond à vos besoins. Explorant les pages suivantes du manuel d'utilisation Citrix Systems 4.2, vous apprendrez toutes les caractéristiques du produit et des informations sur son fonctionnement. Les informations sur le Citrix Systems 4.2 va certainement vous aider à prendre une décision concernant l'achat.
Dans une situation où vous avez déjà le Citrix Systems 4.2, mais vous avez pas encore lu le manuel d'utilisation, vous devez le faire pour les raisons décrites ci-dessus,. Vous saurez alors si vous avez correctement utilisé les fonctions disponibles, et si vous avez commis des erreurs qui peuvent réduire la durée de vie du Citrix Systems 4.2.
Cependant, l'un des rôles les plus importants pour l'utilisateur joués par les manuels d'utilisateur est d'aider à résoudre les problèmes concernant le Citrix Systems 4.2. Presque toujours, vous y trouverez Troubleshooting, soit les pannes et les défaillances les plus fréquentes de l'apparei Citrix Systems 4.2 ainsi que les instructions sur la façon de les résoudre. Même si vous ne parvenez pas à résoudre le problème, le manuel d‘utilisation va vous montrer le chemin d'une nouvelle procédure – le contact avec le centre de service à la clientèle ou le service le plus proche.
