Home

HP CloudSystem Foundation Installation Guide

1. Minimum supported 8 cores 96 GB See the formula below Formula to determine the storage requirements for the management hypervisor The formula used to determine the management hypervisor storage requirements is appliance storage glance images snapshots management hypervisor storage e appliance storage 600 GB o 25 GB for templates 160 GB 3 for the Foundation base appliance vCenter proxy appliance and Enterprise appliance 20 GB 3 for the network node appliances o 25 GB for the SDN appliance e glance images snapshots varies Table 3 Glance repository sizing guidelines Linux images 4 GB Windows images 16 Snapshots 20 GB Glance repository each GB each each TOTAL Small 15 10 15 520 GB Medium 20 15 AO 1 2 TB Large 25 30 500 10 1 TB 12 HP CloudSystem installation prerequisites Use the links in the table below to verify component compatibility and find a list of supported hardware Table 4 Verify compatibility and supported versions Additional resources Use this to Where do find it HP Insight Management Support Refer to the supported HP servers http www hp com go Matrix version 7 3 1 tables CloudSystem supports all insightmanagement docs servers supported in the HP Matrix Operating Environment version 7 3 1 e Table 26 e Table 28 e Table 29 e Table 30 The server must have a check in the Matrix OE column HP Support
2. Configure the HP 3PAR storage system to support storage requirements for compute nodes and virtual machine instances This guide does not cover the specific steps required to accomplish this e The 3PAR storage system server certificate must contain a Fully Qualified Domain Name FQDN in the CN attribute Subject field e For block storage volumes use the OpenStack interfaces that are dependent on block storage support e For ephemeral storage define the storage in the flavor definitions Set up the management hypervisor solution ESX or KVM per CloudSystem requirements If using ESX configure vCenter Server Use esstart to deploy the Foundation base appliance Additional resources See Hardware requirements page 12 Software requirements page 15 Networking requirements page 15 See Openstack Cinder documentation HP_3PAR documentation See Installing CloudSystem on an ESX cluster page 26 Installing CloudSystem on a KVM hypervisor page 33 VMware vSphere Documentation at VMware See Configuring the ESX management environment page 28 Configuring the KVM management environment page 40 Enter and save Cloud Networking settings in the CloudSystem Console See Setting up the CloudSystem Console for the first time page 44 Optional Install OO Studio if you want to customize workflows See Preparing HP Operations Orchestration for CloudSystem Foundation page 47
3. ccccccccccccccceeeeesssseeeeeeeeeeeeeeseeeaeeeassssaaeee ees 57 Information to collect before contacting HP nicsx2ceas acini eau ateers ce andenieehacratiee els 57 How to contact H Porra ineine er anaE rR E EERE REE E ERA RA 57 Registering for software technical support and update Service ccccecsceceeeceseeeeeceeeseseaeeeeeeeenaes 57 HP Usher zeclstesel StS cata tov nceca Bia ueenteleu a teee ave Gxcasstese cok ae areersltas Cou anmiwsa sew teen uoateim es x an seelos on 58 Documentation feed ae m aee eeu n inns a ea E E E A OEE e Aa Et UREE 58 Related tor mieticlhy cxteavvacsteuatent teeesvad eta cateantaese us tileteuteatsestebestisten ated catstndialtel ntistatest tuna ubeoataradvais 58 EPGloudsysiem documents srs osnon EE EEE E aad Mead ea i 58 HP Software COG UST 0504 s 2rq os Sia cxestays Aeaeah Biocie we ta nue les Geman ce Mites agi ou nea Co Oe hon see eseyhides Faas anak 59 Finding documents on the HP Software Product Manuals web Site ccccccceeeeeeeesteeeeeeeees 59 HP Insight Management documents cisiieGteies fe Aesnncdteaue visa cateviea creed teitya ene de 59 Third party doc meniSsi ine tre oat se EAEE anh EEA E alot 59 HP 3PAR StoreServ Storage GOCuIMeNtS i 522xcenceridexa cinsedvnickizennddendacatecweesay Gand Gaxheobbthand densdbaeeks 60 Finding documents on the HP Support Center web Site cccccccssceceesesseeceeeeeeeeesteeeeeeeees 60 HP Proliant servers COCUMMGNS ice Aclacie ante silaeerty Glaclit
4. Copy esstart exe to any directory on the Linux workstation or KVM management host Next step Installing CloudSystem on a KVM hypervisor page 33 Preparing to install on KVM 25 5 Installing CloudSystem on an ESX cluster This chapter contains the procedures required to set up the network infrastructure and install the CloudSystem Foundation base appliance on an ESX management hypervisor The checklist below provides an overview of the installation path Table 11 ESX management hypervisor installation path 4 Installation step Related information Create the management host and define the vSwitch or port group IDs and Understanding the network network security settings in vCenter Server infrastructure page 26 Choose the type of security checks to perform when running csstart Configuring the ESX management environment page 28 Launch csstart and install the Foundation base appliance Configuring the Foundation base appliance on ESX page 32 Understanding the network infrastructure 26 Multiple networks provide the communication platform for CloudSystem vCenter Server and the HP 3PAR storage system The configuration of the networks is flexible This section explains the major components of the networking infrastructure and provides an example of a supported configuration This is only a guide Modify the procedure below to fit your network configuration needs For example the VLAN IDs can vary according to
5. Optional Install CloudSystem Enterprise See Installing CloudSystem Enterprise page 49 Understand the installation process 11 Table 1 Installation process continued Installation step Additional resources See Resource Configuration in CloudSystem Foundation Compute node creation in the HP CloudSystem 8 0 Administrator Guide at Enterprise Information Library Stage and prepare compute nodes This guide does not cover the specific steps required to accomplish this Build and manage cloud resources This guide does not cover the specific steps required to accomplish this See Cloud service provisioning deployment and service management in CloudSystem in the HP CloudSystem 8 0 Administrator Guide at Enterprise Information Library Hardware requirements Hardware requirements for management hypervisors compute nodes virtual appliances and SAN and Storage are provided in this section Physical configuration hardware requirements Management hypervisors The following table lists the recommended and minimum hardware requirements for a single ESX or KVM management hypervisor Only HP servers are supported as management hypervisors In an HA configuration both the primary and failover hypervisors must meet the hardware requirements described in this table Table 2 Management hypervisor hardware requirements nn idee p p d Recommended 16 cores 128 GB See the formula below
6. The management hypervisors hosting the Foundation appliance and Enterprise appliance must use the same NTP servers for time sync Why it matters When the two appliances are out of sync then you will not be able to create designs using HP CSA Enterprise and Foundation must use the same IP address conventions If Foundation was configured to support DHCP address assignments this configuration will apply automatically to Enterprise If Foundation was configured to support static IP addresses you must enter an IP address for the new Enterprise virtual appliance If you want to enable strong OpenLDAP or Active Directory certificate validation for authentication to the CloudSystem Portal review the steps in the Enabling strong certificate validation in the CloudSystem Portal appendix of the HP CloudSystem 8 0 Administrator Guidebefore you install Enterprise Strong certificate validation may require a change to the alternate DNS server on the Foundation base appliance Any changes to the Foundation base appliance network configuration must be made before Enterprise is installed because Enterprise uses these settings to communicate with Foundation Prerequisites e Foundation is fully installed and first time setup is complete e In an ESX configuration the Enterprise OVA is added to the datastore that supports the management cluster in vCenter Server e Ina KVM configuration the Enterprise qcow2 im
7. d db properties i HPOOInfoInput xml Importing a service design 70 Use the Cloud Service Management Console to import a service design Procedure 29 Importing a service design 1 Copy all content in the CSA_HOME CSAKit 4 0 Content Archives folder from the Enterprise appliance to a staging server a Log in to the Enterprise appliance console as cloudadmin See the Working with csadmin appendix in the HP CloudSystem 8 0 Administrator Guide at Enterprise Information Library b Copy the CSA_HOME CSAKit 4 0 Content Archives folder to an external device From there it can be imported to HP CSA c Run the following copy command scp ci usr local hp csa CSAKit 4 0 Content Archives lt file path gt user destination file path From the CloudSystem Console select Enterprise From the Tools pane select Cloud Service Management Console Navigate to Designs gt Sequenced Select Import and browse to the folder you copied in step 1 vie ON Configuring additional providers for CloudSystem Enterprise 6 Click Import NOTE For additional information about the process definition tool see HP Cloud Service Automation Process Definition Tool in the Enterprise Information Library Configuring a Matrix OE resource provider After importing a service design to Enterprise you are ready to configure additional providers such as Matrix OE Use the HP CSA documentation to help you complete the following steps e Define additiona
8. CloudSystem 8 0 offering Sign in with your HP Passport or create a new passport account Accept the license agreement Follow the HP Software Depot instructions for downloading the release files Move the following zip files to the Windows workstation ONOMRWNS The Windows workstation used to stage the files must have access to the vCenter Server that you plan to use to deploy the OVAs e HP CloudSystem Foundation ESX 8 0 0 20 zip e HP CloudSystem Enterprise ESX 8 0 0 20 zip e HP CloudSystem Tools 8 0 0 20 zip 9 Extract the zip file content on your workstation 10 Make sure the esstart folder and the three esstart XXX bat files are extracted from the HP CloudSystem Tools 8 0 0 20 zip on your workstation so that you can run them later Next step Installing CloudSystem on an ESX cluster page 26 Preparing to install on KVM 24 This section covers the steps required to download the contents of the release package and stage the files on a Linux workstation You can also use a Windows workstation to stage the files but you will need to substitute Windows commands in the procedures below Figure 9 Path to install from a Linux workstation Linux workstation KVM management host csstart Copy images to the KVM host csstart uses the images CS Base 8 0 0 20 CloudSystem qcow2 images to configure virtual appliances CS Base 8 0 0 20 qcow2 CS SDN 8 0 0 20 CS SDN 8 0 0 20 qcow2 ESHA ODOR CS NN 8 0 0 20 qcow2 CS
9. Enter 8 0 0 20 CS Enter 8 0 0 20 qcow2 Prepare for the installation Prerequisites You have a Linux workstation to stage the KVM kit and run installation tools Required disk storage is approximately 35 GB You have administrator privileges to log in to the KYM management hypervisor Procedure 2 Downloading zip files and extracting KVM contents l ONAMRWN 10 11 12 Log on to the Linux workstation NOTE If you prefer you can use the KVM management host for staging instead of the Linux workstation Make sure you have at least 3 GB of extra space to stage the kits Open a browser and navigate to the HP Software Depot at http software hp com In the Search field type CloudSystem Select the HP CloudSystem 8 0 offering Sign in with your HP Passport or create a new passport account Fill in the required form details and accept the license agreement Follow the HP Software Depot instructions for downloading the release files Move HP CloudSystem Foundation KVM 8 0 Mar 2014 HP CloudSystem Enterprise KVM 8 0 Mar 2014 and HP CloudSystem Tools 8 0 Mar 2014 files to your Linux workstation or KVM management host Log in to the management hypervisor and run gunzip This command unpacks the zip files Move the qcow2 image files and the checksum sh1 files to the CloudSystem images directory In the HP CloudSystem Tools 8 0 Mar 2014 file there is a csstart linux tar file Unpack the tar file
10. Foundation base appliance on ESX page 32 Table 19 ESX troubleshooting tips continued Symptom Possible cause and recommendation Modify the java security file to accept RSA keys shorter than 1024 bits 1 Log on to the Foundation base appliance 2 Open usr lib jvm jre 1 7 0 openjdk x86_ 64 lib security java security 3 Comment out the following line jdk certpath disabledAlgorithms MD2 RSA keySize lt 1024 IMPORTANT Make sure that you understand the security implications of using shorter keys before you modify the java security file Table 20 KVM troubleshooting tips Symptom RHEL default drivers are not able to manage VLANs Possible cause and recommendation Broadcom TG3 NIC driver needs to be upgraded 1 Find the driver and firmware here HP Support Center 2 Install the upgrade and retry the procedure Configuring the Foundation base appliance on ESX page 32 Security checks fail when running csstart and you see the message Using certificate file No File Found Error Failed to validate your vCenter using ssl Users directory does not contain an SSH key 1 Log on to Foundation base appliance 2 Edit the known_hosts file with the SSH key value 3 Run csstart again Symptom Anti virus software prevents OO Studio install and displays the message vbasic error OO Studio installation errors Possible cause and recommendation OO Studio ve
11. Important network configuration information Important to know Make sure the VLANs in the Management Trunk are actually assigned to cables plugged into the interface network ports Why it matters A network of cables must be physically connected to allow the supported virtual appliances to communicate over the networks Make sure the virtual and physical components have correct association such that data can transfer between points between appliances hypervisors servers nodes etc Do not configure the iSCSI initiators on the management hypervisor iSCSI initiators are set up on the compute nodes not the management hypervisor Initiators check to see which storage resource on the network are available Generic names as shown on the sample configuration figure above are used in this procedure Make sure to Installing CloudSystem on a KVM hypervisor It is important to use the same names defined in the hardware profile when assigning the networks in the management hypervisor ifconfig files If the names do not match then network communication errors will occur Table 15 Important network configuration information continued Important to know substitute the actual names of your interfaces ifcfg eth lt IDs bonds ifcfg bond lt IDs tagged VLANs bond lt ID gt lt VLANID gt and bridges ifc g br lt Name gt when configuring the network Do not include spaces in bridge name Prerequisi
12. Server When the additional virtual appliances are created by the Foundation base appliance the certificate is used to verify that the correct hypervisor is used This is selected by running auto accept cert from the command line or by running the esstartgui auto accept bat file to start the installation setup assistant on Windows See csstart commands page 63 e Disable security checks When csstart runs it does not verify the SSL certificate from the hypervisor The Foundation base appliance does not perform security checks when starting up the other virtual appliances This is selected by running insecure from the command line or by running the esstartgui insecure bat file to start the installation setup assistant on Windows See csstart commands page 63 See also e Using the csstart CLI to install the Foundation base appliance page 64 e Troubleshoot installation issues page 52 Configuring the Foundation base appliance on ESX Read the following important notes before configuring the Foundation base appliance Table 13 Important CloudSystem configuration information Important to know Why it matters HP recommends that you sync the management hypervisor with a good set of external NTP servers If CloudSystem is deployed on ESX configure the Foundation and Enterprise appliances to sync with the same NTP servers configured for the ESX hosts Data records can get out of sync between appliances when time is not
13. base appliance on KVM cccceeseceeeceesenneceeeeeeecesnseeeeeeesesseaaeees 41 7 Setting up the CloudSystem Console for the first time cccccscececeeeeeeeeeeees 44 Configuring cloud gars icc dl element aan ePaper OEP PUT Ui eI Reta PETITE EO LESS EPO OAT TORT 44 Performing time synchronization on the Foundation base appliance cceccsceeeereeeeetteeeeeeneeeees 44 Contents 3 8 CloudSystem Foundation installation next Steps cccccccccscccseceeeeeeeeeeeeeeeeeees 46 9 Preparing HP Operations Orchestration for CloudSystem Foundation 47 Using OO nC Siittelliss micas crete 8 tes Ela tee Ne ite acct Med tet cat te Mate CaM emer 47 Istalin OO Studi se sien geet re a ati EAE eh aie ht ab ce ceeded 47 10 Installing CloudSystem Enterprise cccccssceeseeeeeeeeeseeesstesteeeeeeeeeeeeeeees 49 installing thesEntererisexcppol ces racic avert c ade causaiies sete Coace levauan semen cause ei sei sims oe bed aaa 49 11 Troubleshoot installation isSuCS cccccccceeeeeeesseeeeeeeeeceeeeeeeeeaeeeaaaaaaaeeeees 52 Basic troubleshooting AGenaues sdaceatesest os eatacc aliases sc tate deh iigt tata eet ed att ade imsene rac tas 52 SSI errors ieri spon sn nse E A E E EEE acelin ants eterna R 53 OO Studio installation Errors sranie rosa i E E K E E O tna Ee E E Oo 55 Enterprise upgrade 1 ca tee ieee Sec cn Casta g vss see Coes seat ng we ae ees srren oeenn 99 12 Support and other resOurces
14. br lt Name gt when configuring the network Prerequisites It is important to use the same names defined in the hardware profile when assigning the networks in the management hypervisor If the names do not match then network communication errors will occur Step 4 Return to procedure e You have administrator privileges to log in to VMware vCenter Server Procedure 3 Configuring the network infrastructure 1 Log in to vCenter Server with the administrator user name and password Understanding the network infrastructure 27 Create the management hypervisor host in vCenter Server See Important network configuration information page 27 If you plan to use more than one host to manage the virtual appliances they must be in a cluster Select the management host and click the Configuration tab then click the Networking link on the left menu Set up the Management vSwitch or port group IDs according to the configuration that you defined on the server profile and the dedicated network switch You can also refer to the sample diagram above for guidance on setting port group IDs See Important network configuration information page 27 Set the Cloud Data Trunk port group VLAN a To set the port group on a standard vSwitch set the port group VLAN to 4095 all VLANs b To set the port group on a distributed vSwitch list the exact range of VLANs assigned to the Cloud Data Trunk Example 1 4 5 6 10
15. ea heat E AEEA a alah E A sey gee ie Teele a 13 SAN arid Storage sne a e a ee ee ee Ron mr ane Pe a cree a E TO 14 Virtual appliance requirements CloudSystem virtual appliances ccceeesseeeeeetteeeeeeeees 14 Software EGU IEMENISZn28taaz1enlecvsivebsasaddintuachonetinded dontadwhd eebidond de beeowbaged dacaeesmbacued dendnaeesentaroel eeens 15 Networking KSCUICE ITN IS ace cist oes aS ea tae te ah odie teat Ra aie a Std ek ds al 28 Le ede 15 Overview of network TOROlOG a 1c ctie eine ste otc este hie el alate htitadeds Gentes Gs antl 16 Network NINN ONS essai nen ty yiecbu ees tecten a a sn Attia a cle Siu eather 17 Configuration of management N lwonSscccceerr oe ode ea eo ewtue dence 18 BOWSER LOOUIRCHICI Sazcitesnt neactaeqanies seas cua PaE ce Gee areola cant E ve EENE eae Ds Eee RIE 19 Tools requirements staan tact cence gab te niles EEA AA REE AE AE EA E A eh peta REE 20 Prepare for the installations arare ieee EREE EEEN En EE AEAEE 21 IE eIl Sti ts wise E E A E 21 Contents of CloudSystem zip Tiles s s scuscaspesendeaat nnetsantonenduad seomeantonaniaudesoumesmndsantnemseautaseadsangsa 21 Preparing to install on ESD ty c5 uc esse ion vel ea ee kaare orn sccm teas eae dusmerwzans puma aa ye eaamtansotmnnes ome eON aan 23 Preparing to tristalll ori KVM cis aic havc a a aa E e aces AAE E a meh a E REE ES 24 5 Installing CloudSystem on an ESX cluster cccsesseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeess 26 Understanding the netw
16. installation page 21 20 HP CloudSystem installation prerequisites 4 Prepare for the installation Before you begin the installation it is important to have all of the required images and tools unpacked and staged The installation path varies depending on whether you are installing CloudSystem on an ESX or KVM management hypervisor e Installation kits page 21 e Preparing to install on ESX page 23 e Preparing to install on KVM page 24 Installation kits Download the CloudSystem release kit from HP Software Depot at http software hp com There are six zip files that contain the installation components needed for CloudSystem Foundation and CloudSystem Enterprise The installation components vary depending on the type of management hypervisor you plan to install The table below shows the zip files and which installation path they support Table 10 Components included in HP CloudSystem zip files Installation components Foundation ESX Foundation KVM Enterprise ESX Enterprise KVM HP CloudSystem Foundation ESX 8 0 Mar 2014 contains ESX images for base SDN x x appliance and network node appliances HP CloudSystem Foundation KVM 8 0 Mar 2014 contains KVM images for base SDN x x appliance and network node appliances HP CloudSystem Enterprise ESX 8 0 Mar 2014 contains the ESX image for the Enterprise appliance HP CloudSystem Enterprise KVM 8 0 Mar 2014 contains the KVM image for the Enterp
17. is in the cluster datastore e If using a KVM management hypervisor the CS client CLI 8 0 0 2 msi is in the CloudSystem directory Procedure 17 Installing the OpenStack CLI on a Linux workstation 1 From a Linux workstation run yum install CS client CLI 8 0 0 2 rpm The executable is installed under usr bin 2 Open an SSH client and execute the CLI Command line interfaces See also e For a list of unsupported OpenStack Havana CLI commands see the Limitations on support for OpenStack CLI commands appendix in the HP CloudSystem 8 0 Administrator Guide at Enterprise Information Library e Fora list of all OpenStack Havana CLI commands see OpenStack Documention for Havava releases Using CLI commands csstart commands Table 22 csstart commands Task View the EULA before accepting it CLI command save eula Example csstart save eula What it does This command saves a copy of the EULA to your local directory Search for eula html You can open the file and read the EULA before accepting it Create a sample configuration file create config config esstart create config This command creates the configuration file The default name is deployer conf The config flag allows you to create a unique name for the file if you don t want to use the default name Secure start of esstart start config os cacert lt filename gt eula accepted esstart start eula acc
18. miimon 100 Save and close the file d Create a new bond configuration file using the name ifefg bondA X This bond connects to the Data Center Management Network bridge The configuration file should contain the following lines DEVICE bondA X BOOTPROTO none ONBOOT yes NM_CONTROLLED no Configuring the CloudSystem network infrastructure 37 38 USERCTL no VLAN yes BRIDGE br dc mgmt Save and close the file Create a new bond configuration file using the name ifefg bondA Y This bond connects to the Cloud Management Network bridge The configuration file should contain the following lines DEVICE bondA Y BOOTPROTO none ONBOOT yes NM_CONTROLLED no USERCTL no VLAN yes BRIDGE br cloud mgmt Save and close the file Create a new bridge configuration file using the name ifefg br de mgmt This bridge connects the Foundation base appliance the optional vCenter proxy appliance and the Enterprise appliance to the Data Center Management Network The configuration file should contain the following lines DEVICE br dc mgmt TYPE Bridge DNSl name_of _the primary DNS server IPADDR IP_address_of the KVM_management_host NETMASK netmask_ID BOOTPROTO static ONBOOT yes NM_CONTROLLED no DELAY 0 dce mgmt vlan 10 Save and close the file Create a new bridge configuration file using the name ifefg br cloud mgmt This bridge connects the Foundation base appliance the optional vCenter proxy appliance the SDN
19. qcow2 file comes with a corresponding sha1 checksum file When csstart runs it uses the checksum file to verify that the files are copied to the hypervisor without error HP CloudSystem Enterprise ESX 8 0 Mar 2014 27550 01323 zip e CS Enterprise 8 0 0 20 0va OVF package for the Enterprise appliance on an ESX hypervisor HP CloudSystem Enterprise KVM 8 0 Mar 2014 27550 01324 zip e CS Enterprise 8 0 0 20 qcow2 Disk image for the Enterprise appliance on a KVM hypervisor NOTE Each qcow2 file comes with a corresponding shai checksum file When csstart runs it uses the checksum file to verify that the files are copied to the hypervisor without error HP CloudSystem Tools 8 0 Mar 2014 77550 01325 zip e esstartgui secure bat Program used to deploy and configure the management appliances on the management host When csstart runs it verifies the SSL certificate from the hypervisor and also verifies any additional virtual appliances created This is for Windows or Linux systems e _ csstartgui auto accept bat Program used to deploy and configure the management appliances on the management host When csstart runs it does not verify the SSL certificate from the hypervisor but will inject the certificate into the Foundation base appliance and check all subsequent virtual appliances when they are created This is for Windows or Linux systems e esstartgui insecure bat Program used to deploy and configure the management appli
20. 100 Add the following security settings to the Cloud Data Trunk port group e Set Promiscuous mode to ACCEPT e Set MAC Address Changes to ACCEPT e Set Forged Transmits to ACCEPT Add the following security settings to the External Network port group e Set Promiscuous mode to ACCEPT e Set MAC Address Changes to ACCEPT e Set Forged Transmits to ACCEPT Configuring the ESX management environment The management environment consists of a single management hypervisor host or a cluster of management hypervisor hosts that contain the following virtual appliances 28 A Foundation base appliance An SDN appliance An optional vCenter proxy appliance One vCenter proxy appliance is needed for each vCenter that is managing compute nodes in your cloud If your cloud contains only KVM compute nodes then you do not need any vCenter proxy appliances Three network node appliances An optional Enterprise appliance if you are using CloudSystem Enterprise The csstart installation script launches a setup assistant to guide you through the installation process When you run csstart the setup assistant opens and displays fields for capturing details about the new virtual appliance network configuration and vCenter Server connections The information is saved in a configuration file called deployer conf Running csstart applies the configuration information saved in deployer conf to the virtual appliance designated to host the Foundation base appli
21. 9 zip e Content packs that can be installed and edited in OO Studio o OO HP Solutions cp jar OO Systems cp jar OOvirtualization cp jar OO Base cp jar o OO cloud cp jar e O0O installer exe Used to install OO Studio e O0 studio upgrade zip Used to upgrade OO Studio to 10 02 Preparing to install on ESX This section covers the steps required to download the contents of the release package and stage the files on a Windows workstation You can also use a Linux workstation to stage the files Figure 8 Path to install from a Windows workstation VMware vCenter Server Windows workstation ESX cluster CloudSystem OVA images CS Base 8 0 0 20 ova CS SDN 8 0 0 20 0va Co Bde 80 020 CS SDN 8 0 0 20 CS NN 8 0 0 20 0va ITE CS NN 8 0 0 20 CS Enter 8 0 0 20 0va CS Enter 8 0 0 20 Browser CloudSystem installation tools Note Use the same data store for all OVA imports converted templates and running VM vmdks Preparing to install on ESX 23 Prerequisites e You have a Windows staging server with access to your vCenter Server Required disk storage is approximately 35GB e You have administrator privileges to log in to VMware vCenter Server Procedure 1 Downloading zip files and extracting ESX contents Log on to the Windows workstation Open a browser and navigate to the HP Software Depot at http software hp com In the Search field type CloudSystem Select the HP
22. CS client CLI 8 0 0 2 rpm provides the ability to run CloudSystem and OpenStack command lines from a Linux system Preparing to use ClLls The CLls are packaged in the CloudSystem Tools 8 0 0 20 release tar The csstart and csadmin CLls do not require additional installation steps The OpenStack CLls must be installed on either a Windows or Linux workstation Installing OpenStack CLls on Windows Prerequisite e If using an ESX management hypervisor the CS client CLI 8 0 0 2 rpm file is in the cluster datastore e If using a KVM management hypervisor the CS client CLI 8 0 0 2 msi is in the CloudSystem directory Procedure 16 Installing the OpenStack CLI on a Windows workstation 1 From a Windows workstation double click the MSI file to execute it and launch the Windows installer 2 Follow the Windows installer screen instructions to complete the installation The executable is installed in c Program Files Hewlett Packard RemoteCli 3 Open the Windows command prompt and execute the CLI See also e For a list of unsupported OpenStack Havana CLI commands see the Limitations on support for OpenStack CLI commands appendix in the HP CloudSystem 8 0 Administrator Guide at Enterprise Information Library e Fora list of all OpenStack Havana CLI commands see OpenStack Documention for Havava releases Installing OpenStack CLIs on Linux 62 Prerequisite e If using an ESX management hypervisor the CS client CLI 8 0 0 2 rpm file
23. Center Verity the compatibility of the servers http www hp com go hpsc drivers firmware and software HP Customized ESXi images for Find customized ESXi images hito h18004 www 1 hp com management hypervisor Supported versions are 5 0 Update 3 products servers sottware vmware 5 1 Update 2 and 5 5 esxi image html Compute nodes Compute node sizes vary according to your resource needs The following questions are provided to guide you as you determine the size of your compute node e What flavor settings will the provisioned instances use e What oversubscription rate is supported for each compute resource See the Compute Node Management chapter in the HP CloudSystem 8 0 Administrator Guide at Enterprise Information Library e How many instances will each compute node support After answering the questions above determine the amount of CPU cores memory and storage to allocate to each compute node You can also use the HP Sizer for Server Virtualization website to determine hypervisor sizing for compute nodes Table 5 Hardware requirements Additional resources ee Where do find it HP Sizer for Server Virtualization Find details on sizing hypervisors for http h71019 wwwZ hp com website compute nodes Renae es ActiveAnswers us en size Use the links in the table below to verify component compatibility and find a list of supported hardware Hardware requirements 13 Table 6 Verify compatibility and su
24. Flow Content 0010 csa cp 4 0 0 jar user destination file path 2 From the CloudSystem Console select Integrated Tools 3 Log in to OO Central and navigate to Content Workspace 4 Select Deploy New Content 5 Click Add 6 Select the 0010 csa cp 4 0 0 content pack and click Open 7 Click Deploy NOTE The deployment may take several minutes The cursor displays the busy icon during the deployment You can find information about the success of the deployment in the Deployment Result section 8 Click Close to return to the Content Workspace 68 Configuring additional providers for CloudSystem Enterprise Procedure 23 Configuring system accounts for the HP CSA content pack There are three system accounts that must be set up to support the HP CSA content pack 1 From the Content Workspace in OO Central select Configuration Items System Accounts 2 Click Edit 3 In the System Account Name field type CSA_REST_CREDENTIALS 4 In the User Name field type ooInboundUser NOTE The User Name configured for the SA_REST_CREDENTIALS System Account setting must match the Override Value configured for the CSA OO_USER System Property setting 5 In the Password field type cloud Click Save Click Edit In the System Account Name field type CSA_SERVICEMANAGER_CREDENTIALS co NO 9 In the User Name field type falcon 10 Leave the Password field blank 11 Click Save Procedure 24 Configuring s
25. HP CloudSystem 8 0 Installation and Configuration Guide About this guide This information is for use by administrators using HP CloudSystem Foundation and Enterprise Software 8 0 who are assigned to configure and provision compute resources for deployment and use in virtual data centers HP Part Number 5900 3382 Published March 2014 Edition 1 Copyright 2014 Hewlett Packard Development Company L P Microsoft and Windows are U S registered trademarks of the Microsoft group of companies Red Hat is a registered trademark of Red Hat Inc in the United States and other countries Confidential computer software Valid license from HP required for possession use or copying Consistent with FAR 12 211 and 12 212 Commercial Computer Software Computer Software Documentation and Technical Data for Commercial Items are licensed to the U S Government under vendor s standard commercial license The information contained herein is subject to change without notice The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services Nothing herein should be construed as constituting an additional warranty HP shall not be liable for technical or editorial errors or omissions contained herein The open source code used by HP CloudSystem is available on the HP web at http www hp com software opensource Contents 1 Welcome to HP Clow S vst ciccyise ci ct
26. HP solutions such as HP ArchSight HP Fortify HP Load Runner HP Application Lifecycle Management and HP Onboard Administrator e doud cp This workflow supports exposed APIs from cloud providers like OpenStack Amazon EC2 IAM S3 and VMware vCloud Once the workflows are loaded you can run them at any time For more information about HP Operations Orchestration see http www hp com go oo Installing OO Studio There are two parts to the OO Studio installation e Installing OO Studio page 47 e Upgrading OO Studio page 48 Installing OO Studio allows you to customize workflows Customized flows are saved as content packs and exported to a local directory You can then pull the customized flows into OO Central and run them to perform administrative tasks in CloudSystem Foundation Prerequisites e Foundation is fully installed and first time setup is completed e You have access to a Windows workstation e System requirements are met Refer to HP Operations Orchestration System Requirements at Enterprise Information Library Procedure 12 Installing OO Studio 1 Unzip the HP CloudSystem OO Studio 8 0 Mar 2014 zip file Z7550 01319 zip 2 Untar the zip file Using OO Central 47 3 Launch the 00 installer exe file a Take all default settings when moving through the installation setup until the Content packs screen b Do not import content packs at this time Skip to the next screen c Click Next and finish
27. Installing CloudSystem on an ESX cluster The ESX management hypervisor can run as a standalone host Multiple management hypervisor hosts are configured in a cluster The esstartgui bat and the full esstart folder are extracted from CloudSystem Tools 8 0 0 20 tar gz to a Windows workstation Procedure 4 Preparing the CloudSystem virtual machine images 2 3 4 Log in to vCenter Server using the VMware vSphere Client or a web browser Select Inventory Hosts and Clusters and select your management cluster Select File Deploy OVF template Follow the screen prompts Use the CS Base 8 0 0 20 ova image file that was staged on your Windows workstation Make sure to name the template CS Base 8 0 0 20 The name should match the ova file name a Best practice is to select thin provisioning Installation is much faster with this option Thick provisioning requires about an hour for the Foundation base appliance vCenter proxy appliance and Enterprise appliance to install and it requires 560 GB of space b The location where the OVA images are stored is the same location where csstart creates the virtual machine appliances Make sure the datastore you plan to use has 500 GB of space Verify that the virtual appliance was created It should be listed on the left side of the screen under the VMs and templates view Do NOT boot the virtual appliance Repeat steps 3 6 for the SDN appliance selecting the CS SDN 8 0 0 20 0va image file th
28. KVM management environment 41 42 e A CloudSystem images directory is created on the management hypervisor and the qcow2 images and checksums are moved to this directory The CloudSystem images directory should be owned by root and should have permissions set to 755 This setting allows write access only to the root user for the files owned by root e 128 GB of memory is available on the management hypervisor for image storage See HP CloudSystem installation prerequisites page 11 e The esstart folder and the three csstart XXX bat files are moved to the management hypervisor See Prepare for the installation page 21 e The network ifefg files are created in the management hypervisor etc sysconfig network scripts directory See Configure the network infrastructure on the KVM management hypervisor page 36 Procedure 9 Configuring the Foundation base appliance on KVM 1 Gather the following information which you will enter later in the csstart setup assistant e Foundation base appliance host name and IP address if using static IP e Glance disk size e Foundation base appliance new secure password e Data Center Management subnet mask e Gateway address jump box on the management network e Preferred DNS server IP address e Management hypervisor host name user name and password e Name of the Data Center Management Network bridge e Name of the Cloud Management Network bridge e Name of the Cloud Data Trunk bridge e Name of the External N
29. Mware vCenter server Cloud mgmt Data Center Management Cloud Managment External Provider Private The following figure shows a sample configuration with a KYM management host networks and KVM compute nodes Figure 7 KVM management host with KVM compute nodes KVM mgmt host CloudSystem Foundation CloudSystem Enterprise Enclosure External router KVM compute nodes KVM compute nodes Onboard Administrator Virtual Connect Data Center Management Cloud Management External Provider Private For a detailed explanation of the network configuration see Installing CloudSystem on an ESX cluster page 26 Installing CloudSystem on a KVM hypervisor page 33 Browser requirements The following browsers are supported for the CloudSystem installation a Microsoft Internet Explorer 9 10 Mozilla Firefox Extended Support Release ESR 24 Browser requirements 19 Personal Edition Latest version Google Chrome 33 Tools requirements The CloudSystem Tools 8 0 0 20 zip file contains a csstart installation script and several CLI packages The requirements for the systems running these tools are listed in the table below CloudSystem Tool Product Version csstart Windows Version 7 2008 R2 32 bit and 64 bit Linux RHEL 6 4 CLI packages Windows Version 7 2008 R2 32 bit and 64 bit Linux CentOS 6 2 6 3 6 4 Ubuntu 12 04 Next step Prepare for the
30. OK to save the settings 7 Verify that the SDN appliance and network node appliances are created and running c e For ESX check vCenter Server to make sure the appliances are in the cluster e For KVM log in to the management hypervisor and run the command virsh list Performing time synchronization on the Foundation base appliance CloudSystem services can encounter errors and unpredictable system behavior can occur if the time on the Foundation base appliance vCenter proxy appliance and the Enterprise appliance differ by more than a few minutes Make sure the correct Time and Language synchronization setting in the CloudSystem Console is selected before CloudSystem is available for general use Prerequisites e Foundation base appliance is successfully installed on a management hypervisor e Management hypervisor where the Foundation base appliance was installed is synchronized with a set of NTP servers 44 Setting up the CloudSystem Console for the first time Procedure 11 Synchronizing the Foundation base appliance with the management hypervisor NTP servers 1 Log in to the CloudSystem Console 2 From the Settings screen click the Edit icon in the Appliance panel e For ESX 1 In the Time and Language settings section change the setting to Synchronize with time server 2 Enter the IP address of the external NTP servers These servers should be the same NTP servers used by the management hypervisor e For K
31. Security check fails when running csstart and you see the message Warning Different certificates are being used for SSL and Solution users Manual intervention is required Security checks fail when running csstart and you see the message Using certificate file No File Found Error Failed to validate your vCenter using ssl Certificate files do not match 1 Press CTRL C to interrupt csstart 2 Query the hypervisor where vCenter Server is installed keytool printcert rfc sslserver servername port 3 Copy everything from BEGIN CERTIFICATE to END CERTIFICATE into a new file 4 Add a name to the file os cert option lt filename gt 5 Move the file to the same directory where csstart is located 6 Retry the procedure Configuring the Foundation base appliance on ESX page 32 Security checks fail because the SSL certificate expired or is invalid due to a hypervisor host name change Certificate file is missing 1 Use the Add CA Cert option in the vCenter Server Registration screen to add the new SSL certificate 2 Retry the procedure Configuring the Foundation base appliance on ESX page 32 You see the message Certificates do not conform to algorithm constraints Troubleshoot installation issues An upgraded version of vCenter Server has a server certificate with a 512 bit key length 1 Generate a new certificate for vCenter Server 2 Retry the procedure Configuring the
32. VM 1 In the Time and Language settings section keep the setting Synchronize with VM host 3 Save the changes Next steps Choose any of the following next steps e Refer to the HP CloudSystem 8 0 Administrator Guide at Enterprise Information Library for additional information on configuring ESX and KVM compute nodes configuring cloud resources and deploying instances e Preparing HP Operations Orchestration for CloudSystem Foundation page 47 e Installing CloudSystem Enterprise page 49 Performing time synchronization on the Foundation base appliance 45 8 CloudSystem Foundation installation next steps The CloudSystem Foundation installation is complete but you still need to prepare and build resources for the cloud The table below provides links to resources that will help you complete these tasks Table 17 Cloud preparation steps Installation Step Additional Resources See the Resource configuration in CloudSystem Compute node creation chapter in the HP CloudSystem 8 0 Administrator Guide at Enterprise Information Library See Cloud service provisioning deployment and service management in CloudSystem in the HP CloudSystem 8 0 Administrator Guide at Enterprise Information Library Stage and prepare compute nodes Build and manage cloud resources If you are not ready to prepare your cloud you can go to e Preparing HP Operations Orchestration for CloudSystem Foundation page 47 e Installi
33. access at any time while the system is running HP technical support personnel are not granted remote access to the appliance e Information to collect before contacting HP page 57 e How to contact HP page 57 e Registering for software technical support and update service page 57 e HP authorized resellers page 58 e Documentation feedback page 58 e Related information page 58 Information to collect before contacting HP Be sure to have the following information available before you contact HP e Software product name e Hardware product model number e Operating system type and version e Applicable error message e Third party hardware or software e Technical support registration number if applicable How to contact HP Use the following methods to contact HP e To obtain HP contact information for any country see the Contact HP worldwide website htto www hp com go assistance e Use the Get help from HP link on the HP Support Center http www hp com go hpsc e To contact HP by telephone in the United States use the Contact HP Phone Assist website to determine the telephone number that precisely fits your needs For continuous quality improvement conversations might be recorded or monitored htto www8 hp com us en contact hp phone assist html section Registering for software technical support and update service HP CloudSystem includes one year of 24 x 7 HP Software Technical Support and U
34. ae ty Clan lehman eels dos Pate r tad ia 6l A Command line interfaces reirei Rann A 62 Preparing to use Cllsic encrena a EA EEE EEE E E EAr a at 62 Installing OpenStack CLlls on Witdowsy s 5e 2 cehveusdacedlajiueslecondsadadenteenhedshdsctesen ivonbesion aghlecktuens 62 Installing OpenStack ClLls on Winkie esta cei ctu ase eh eda cate Rahat oe hah ga al ee dey 62 Using GN commands aeei aii a R EE EE A Salah tent ga hat E OE AR iC 63 ESIC command S a a A a hom ln a A alti 63 csadmin CLI and OpenStack Ci eeaeiloche featdeeysctsid ccbicaudoscusekiede dand oRetckneSaxl dandgivlacked uel Sarat sidens 64 Additional Elias cheer en CoM meet ee een A nee nen TVET NR SSO CORTE ST ASTON Te APY Te TNT er ree eet 64 Using the csstart CLI to install the Foundation base appliance cccccceeescseeeceeeesseteeeeeeeneaes 64 Enabling REST API for storage ariverss a scare cited aheced cwitheasencuet ux dd ween Must aed vawrevain taceMeeheaerecs 66 Using the CLI to access the Enterprise consoles ci 3 4A ccs Rice as eden eee 66 B Configuring additional providers for CloudSystem Enterprise 000eee 67 Configuring HP Operations Orchestration to integrate with HP CSA ccssssceeeeseeeeeeteeeesteeeees 67 Importing Operations Orchestration flows ccis Aceus ok onal eices sntecteaus ioisveausedebesmensuar tastes ant 69 Importing a service SSI sae be ot see cated ovate ceihcattveratac elec vaitter teer Sstre Eers as tecish cath aadiallen Mami
35. age is saved to the Linux or Windows server where you ran csstart to install the Foundation base appliance e You are using a supported Chrome browser See HP CloudSystem installation prerequisites page 11 e You have selected an IP address if using static IPs and registered the FQDN for the Enterprise appliance with the DNS server Procedure 14 Installing CloudSystem Enterprise 1 Log in to the CloudSystem Console 2 Select Enterprise from the main menu 3 Click the Install CloudSystem Enterprise button The installation window opens Installing the Enterprise appliance 49 50 Figure 12 Enterprise screen in CloudSystem Foundation CloudSystem Console YW Q Search Enterprise Actions v CloudSystem Enterprise gt Not installed CloudSystem Enterprise supports designing and provisioning multi tier infrastructure and application services Requirements Download image Define hostname Identify IP address Register in DNS Components include Enterprise virtual appliance HP Cloud Serice Automation Topology Designer Sequential Designer Marketplace Portal Install CloudSystem Enterprise 4 Review the installation instructions then click Next 5 In the Enterprise appliance host name field enter the FQDN that you registered with the DNS server 6 Enter the static IP address for the new Enterprise appliance NOTE If the Data Center Management Network configured in Foundation uses DHCP skip t
36. ailed CloudSystem Enterprise 8 0 020 was not added to the ESX cluster or KVM management hypervisor 1 For ESX e Log in to vCenter Server and make sure the cS Enterprise 8 0 0 20 OVA is saved to the datastore supporting the management cluster e The image name must be cS Enterprise 8 0 0 20 2 For KVM e Log in to the management hypervisor and make sure the CloudSystem Enterprise 8 0 0 20 image is saved in CloudSystem images You see the message CloudSystem Enterprise installation succeeded but could not start up due toa communication problem Enterprise appliance is not done booting 1 Wait a few minutes The Enterprise appliance is not ready 2 Retry the login action When logging in to HP CSA for the first time you see the message Default organization not found Troubleshoot installation issues Enterprise appliance is not ready 1 Wait a few minutes The Enterprise appliance is not ready and is still trying to bring up the HP CSA appliance or is still recovering from a reboot 2 Retry the login action 12 Support and other resources IMPORTANT This product contains a technical feature that will allow an on site authorized support representative to access your system through the system console to assess problems that you have reported This access will be controlled by a password generated by HP that will only be provided to the authorized support representative You can disable
37. ance When the installation completes the Foundation base appliance appears in the management cluster in vCenter Server The SDN appliance and the network node appliances are automatically created after the Cloud Networking settings are entered and saved Installing CloudSystem on an ESX cluster Selecting hypervisor security level for CloudSystem installation You can select one of three security options when you run the csstart setup assistant e Enable full security checks When csstart runs it validates certificates to ensure that it is accessing the correct hypervisor In an ESX environment csstart searches for the stored vCenter Server certificate and matches it to the vCenter Server defined in the installation setup The stored certificate file must have the hypervisor s certificate along with the complete signing authority chain unless it is a valid self signed certificate The name of the stored certificate file is specified using the os cacert lt filename gt command from the csstart CLI If csstart cannot open the file or validate the certificate then it will fail The Foundation base appliance also verifies certificates before starting up each additional virtual appliance See csstart commands page 63 e Disable security checks for csstart but enable security when creating the remaining virtual appliances When csstart runs it injects the certificate into the Foundation base appliance but does not try to verify vCenter
38. ances on the management host When csstart runs it does not verify any certificates for the initial base appliance installation or for subsequent virtual appliances This is for Windows or Linux systems e esstart linux tar Contains the command line to install CloudSystem from a Linux system e esstart windows zip Contains the command line to install CloudSystem from a Windows system This is packaged as a folder of files along with three bat files which are used to invoke the command e csadmin Provides Linux command line access to perform administrative functions such as storage management support dump actions for management virtual appliances and password setting for management appliance console access e csdamin exe Provides Windows command line access to perform administrative functions such as storage management support dump actions for management virtual appliances and password setting for management appliance console access Prepare for the installation e _ isc remote client 8 0 0 20 msi Installs the Windows version of the commands for OpenStack Keystone Nova Neutron and Cinder e isc remote client 8 0 0 20 rpm Installs the Linux version of the commands for OpenStack Keystone Nova Neutron and Cinder e _rhel kvm deps 8 0 0 20 rpm When run in a YUM repository this file checks for required RHEL RPMs and returns a list of any that are missing HP CloudSystem OO Studio 8 0 Mar 2014 27550 0131
39. appliance and the network node appliances to the Cloud Management Network The configuration file should contain the following lines DEVICE br cloud mgmt TYPE Bridge NM_CONTROLLED no BOOTPROTO none ONBOOT yes DELAY 0 region mgmt vlan 12 Save and close the file 4 Create the interface bond and bridge configuration for the External Network See KVM sample network configuration page 36 a Open the ifefg ethO file and add the following lines MASTER bondB SLAVE yes NM_CONTROLLED no Save the change and close the file Open the ifefg ethP file and add the following lines MASTER bondB SLAVE yes NM_CONTROLLED no Save the change and close the file Installing CloudSystem on a KVM hypervisor Create a new bond configuration file using the name ifefg bondB This bond connects to the External Network bridge The configuration file should contain the following lines DEVICE bondB BOOTPROTO none ONBOOT yes USERCTL no NM_CONTROLLED no BONDING OPTS mode 5 miimon 100 BRIDGE br external Save the change and close the file Create a new bridge configuration file using the name ifefg br external This is the bridge that connects the network node appliances to the External Network The configuration file should contain the following lines DEVICE br external TYPE Bridge BOOTPROTO none ONBOOT yes NM_CONTROLLED no DELAY 0 5 Create the interface bond and bridge configuration files for the C
40. ase properties file and rename the copy to db properties sudo cp PostgreSqlinputSample properties db properties 3 Edit the db properties file and make the following name changes e db url jdbc postgresql 127 0 0 1 5432 csadb to db url jdbc postgresql 127 0 0 1 5432 csa e db user csadbuser to db user csa e 6db password ENC UUV PSwS9If 1INURGSObYPQ to db password csa 4 Save and close the file Procedure 27 Creating an Operations Orchestration input file This procedures uses the sample files that were generated when you performed the tip above If you did not follow the tip instructions complete them now 1 In the working directory CSA_HOME Too1s make a copy of the sample input file HPOOInput Sample xml and rename it to HPOOInfoInput xml sudo cp HPOOInputSample xml HPOOInfolInput xml 2 Update the following attributes and values for all ooengine entries in the HPOOInfolInput xml file e truststore ci usr local hp csa openjre lib security cacerts e 6url https lt foundation_ipaddress or hostname gt PAS services WSCentralService username csaoouser e password cloud e Truststorepassword changeit 3 Save and close the file Procedure 28 Running the process definition tool e Execute the following commands from the Enterprise appliance to run the process definition tool e cd ci usr local hp csa Tools sudo ci usr local hp csa openjre bin java jar process defn tool jar
41. at was staged on your Windows workstation Make sure to name the template CS SDN 8 0 0 20 The name should match the ova file name Repeat steps 3 6 for the network node appliance selecting the CS NN 8 0 0 20 0va image file that was staged on your Windows workstation Make sure to name the template CS NN 8 0 0 20 The name should match the ova file name Repeat steps 3 6 for the Enterprise appliance selecting CS Enterprise 8 0 0 20 ova image file that was staged on your Windows workstation Make sure to name the template CS Enterprise 8 0 0 20 The name should match the ova file name Configuring the ESX management environment 31 32 Procedure 5 Configuring the Foundation base appliance on ESX 1 Gather the following information which you will enter later in the csstart setup assistant See Important CloudSystem configuration information page 29 e Foundation base appliance host name and IP address if using static IP e Glance disk size e Foundation base appliance new secure password e Data Center Management Network subnet mask e Gateway address jump box on the management network e Preferred DNS server IP address e vCenter Server IP address or host name e vCenter Server user name and password e Management cluster name e vCenter Server name for the Data Center Management Network Refer to Cluster gt Host Configuration Networking in vCenter Server to find the network name e yCenter Server name for the Cloud Management N
42. ate 6 Install the RPM file yum install y rhel kvm deps 8 0 0 xx rpm enablerepo RHELDVD Missing RHEL RPMs are identified and installed 7 Verity that the libguestfs and libguestts tools packages were installed yum list grep libguestfs Configuring the CloudSystem network infrastructure Several networks provide the communication platform for HP CloudSystem and the suite of integrated tools The configuration of the networks is flexible This section explains the major components of the networking infrastructure and provides an example of a supported configuration This is only a guide Modify the procedures below to fit your network configuration needs For example the bridge names can vary according to your environment Explanation of CloudSystem networks CloudSystem virtual Management hypervisor Example names for bridges Network appliance interface matches figure below Data Center Management Foundation base appliance vNICO br demgmt Network vCenter proxy appliance vNICO Enterprise appliance vNICO Cloud Management Network Foundation base appliance vNIC1 br cloud mgmt vCenter proxy appliance vNIC1 SDN appliance vNICO KVM compute nodes vNICO Cloud Data Trunk network node appliances vNIC1 br cloud trunk External Network network node appliances vNIC2 br external IMPORTANT All of the networks described above must be distinct networks with the exception of the External Netw
43. ation information Important to know HP recommends that you set the time on the management hypervisor to automatically sync with the NTP server The Foundation and Enterprise appliances should be synced with the virtual machine host running the management hypervisor Why it matters Data records can get out of sync between appliances when time is not set to automatically sync with the NTP server If you are using the RHEL default driver Broadcom TG3 NIC then you must update the driver See HP Support Center Using an outdated driver will prevent you from accessing a provisioned instance with a floating IP If you are using the Emulex driver be2net then you must upgrade the driver to version 4 4 245 0 or later See Citrix support Using an outdated driver will interrupt SSH and TCP network traffic When installing with Linux you should run the csstart setup assistant from a directory with restricted access in order to protect this file The deployer conf file contains confidential information such as passwords and should be kept secure Step 2 The installation images and the corresponding checksums should be placed in the default CloudSystem images directory The csstart setup assistant does not provide a way to change the image location You must update that directly in the deployer cont file See Using the csstart CLI to install the Foundation base appliance page 64 Exit the css
44. automatically creates the SDN appliance and network node appliances For definitions of the SDN appliance and network node appliances see CloudSystem Foundation components page 8 Configuring cloud networking IMPORTANT Before you apply the Cloud Networking configuration in the CloudSystem Console verity that you have the correct subnets Cloud Networking is intended to be configured only once If you need to change Cloud Networking after compute nodes are activated you will need to delete all of the compute nodes first Prerequisites e Minimum required privileges Infrastructure administrator e The appliance is physically connected to the network e The Foundation base appliance is installed Procedure 10 Configuring cloud networking for the first time 1 Open a supported browser and enter the url https lt IP address of the Foundation base appliance gt 2 Log in to the CloudSystem Console using the administrator user name and the new secure password you defined in csstart The console opens to the Dashboard screen 3 Expand the help icon along the right side of the screen 4 Under the Recommended actions heading select Edit Cloud Networking The Cloud Networking window opens 5 Enter the Cloud Management subnet in the field provided This is the Cloud Management Network you established in Configuring the CloudSystem network infrastructure page 35 or Understanding the network infrastructure page 26 Click
45. brary Log in as cloudadmin through the Enterprise console You can use CTRL ALT F1 to switch to the console log in prompt Edit the NTP configuration file to add the server entries sudo vi etc ntp conf Restart the NTP service sudo service ntpd restart Restart the Enterprise appliance See also Refer to the HP CloudSystem 8 0 Administrator Guide at the Enterprise Information Library for additional information on using HP CSA to create designs Next steps See Understanding CloudSystem Enterprise in the HP CloudSystem 8 0 Administrator Guide at Enterprise Information Library Installing the Enterprise appliance 51 11 Troubleshoot installation issues e csstart errors page 53 e OO Studio installation errors page 55 e Enterprise upgrade errors page 55 NOTE For additional troubleshooting information see the Troubleshooting chapters in the HP CloudSystem 8 0 Administrator Guide available at Enterprise Information Library Basic troubleshooting techniques 52 HP CloudSystem has a variety of troubleshooting tools you can use to resolve issues By following a combined approach of examining screens and logs you can obtain a history of activity and the errors encountered e The Activity screen in the CloudSystem Console displays a log of all changes made on the appliance whether user initiated or appliance initiated It is similar to an audit log but with finer detail and it is easier to access from th
46. com Select the and 5 5b Custom virtualization software link HP image For ESXi hosts 5 5 is supported instead of 5 5b VMware vCloud Networking and 5 5 See Third party documents page 59 Security vCNS Required on ESX compute nodes to support security groups for provisioned instances Red Hat Enterprise Linux 6 4 See Third party documents page 59 OO Studio 10 02 The upgrade executable file is available in the OO Studio zip file System requirements must be met to support the upgrade to OO Studio You can confirm requirements here HP Orchestration Operations System Requirements document Networking requirements Before installing CloudSystem plan for the following networks Software requirements 15 Table 9 Network planning Network Data Center Management Network Purpose This network connects virtual appliances to HP 3PAR VMware vCenter Server VMware vCloud Networking and Security vCNS and enclosures Connected to Foundation base appliance VMware proxy appliance Enterprise appliance VMware vCenter Server Cloud Management Network This network connects the Foundation base appliance vCenter proxy appliance network node appliances SDN appliance and KVM compute nodes This is a private network Foundation base appliance SDN appliance network node appliances VMware proxy appliance KVM compute nodes External Network This network allows cloud end
47. d the DNS server IP address vi etc sysconfig network scripts ifcfg etho DNS1 192 0 2 2 18 Restart the network service service network restart Creating a local YUM repository and validating RHEL RPMs 34 An empty RPM file rhel kvm deps 8 0 0 20rpm is included in the CloudSystem Tools 8 0 0 20 tar gz This file lists all the required RHEL RPMs After creating the YUM repository run the RPM file and download any missing RPMs Add the missing RPMs to your local YUM repository See Third party documents page 59 Prerequisites e rhel kvm deps 8 0 0 20rpm is extracted from the CloudSystem Tools 8 0 0 20 tar gz file and moved to the Linux workstation Procedure 7 Creating a local YUM repository and validating dependencies For the configuration in this section use a utility such as WinSCP which can be downloaded from http winscp org 1 Make a new directory and copy RHEL 6 4 to a directory location such as home kits mkdir home kits 2 Make a new directory for the DVD mount point mkdir dvd Installing CloudSystem on a KVM hypervisor 3 Mount the DVD mount o loop home kits rhel server 6 4 x86 64 dvd iso dvd 4 Create the repository a cd etc yum repos d b vi LocalDCRhel repo RHELDVD name Locally Mounted RHEL 6 4 ISO baseurl file dvd enabled 0 5 Import the GPG Key GNU Privacy Guard a rpm import etc pki rpm gpg RPM GPG KEY redhat release b yum clean all C yum upd
48. deployer conf configuration file esstart create config This will create a sample configuration file The default name is deployer conf but you can specify a unique name by putting it inside the config tag 64 Command line interfaces 10 11 Open the config file vi deployer conf Fill in the Hypervisor section of the configuration file The hints provided in the configuration file explain the hypervisor entries Fill in the Image file location section of the configuration file e If you created the CloudSystem images directory and placed images there then enter default for each image location The configuration file hints show each default location e f you created a different directory then enter the actual path to the image location Example CloudSystem templates CS SDN 8 0 0 20 qcow2 Fill in the Appliance setup section of the configuration file e Enter a new administrator password to use when accessing the CloudSystem Console e Enter a support access option Enabled allows HP support to access your system in the event of an error Disabled will not allow access e Enter the amount of space to allocate to the Glance disk in GBs Fill in the Appliance Networking section of the configuration file The hints provided in the configuration file explain the hypervisor entries Add the network configuration to the Network Mapping section The information below corresponds to the sample provided in the network
49. e accepted accepted vCenter certificate ESX or SSH key KVM before creating the base appliance Virtual appliances are also started without certificate checks The config flag identifies the configuration file if you chose not to use the default deployer conf file name The EULA is automatically accepted Start a web server gui listen csstart gui listen The ipaddr port defaults to listening on a specific ipaddr port 127 0 0 1 5000 127 0 0 1 5000 which means port the webs server only listens to a web browser running on the local host A very common value for the listen flag is listen 0 0 0 0 5000 The web server listens for connections from any host such as your workstation csadmin CLI and OpenStack CLI For an explanation of csadmin CLI commands see the Working with the csadmin CLI appendix in the HP CloudSystem 8 0 Administrator Guide at Enterprise Information Library For a list of all OpenStack Havana CLI commands see OpenStack Documention for Havava releases Additional CLI tasks e Using the csstart CLI to install the Foundation base appliance page 64 e Enabling REST API for storage drivers page 66 e Using the CLI to access the Enterprise console page 66 Using the csstart CLI to install the Foundation base appliance Procedure 18 Using the csstart CLI to install the Foundation base appliance 1 Log in to the management hypervisor 2 Run the command to create the
50. e UI The Activity screen also provides a log of health alerts and status notifications e You can download an audit log in the CloudSystem Console to help you understand what security relevant actions took place on the system e You can create a support dump file in the CloudSystem Console to gather logs and other information required for debugging into an encrypted compressed file that you can send to your authorized support representative for analysis Recommendation Details Look fora message About syntax errors e The user interface checks for syntax when you enter a value If you make a syntax error an instructional message appears next to the entry The user interface or command line continues to display messages until you enter the correct value About network setup errors e Before applying them the appliance verifies key network parameters like the IP address and the fully qualified domain name FQDN to ensure that they have the proper format e After network settings are applied the appliance performs additional validation such as reachability checks and host name to IP lookup If a parameter is incorrect the appliance generates an alert that describes validation errors for the Network Interface Card NIC and the connection between the browser and the appliance can be lost Examine the Activity To find a message for an activity screen ss 1 Locate recent activities with a severity of Critical Warning
51. e product name that you selected earlier in your search In the second search field below the first type manuals and press Enter If the list of documents is long it might take a few seconds to load the page with the search results You can refine the search results using the sorting options in the document table headers or by further refining your search criteria in the search feature that is located immediately above the document list Support and other resources HP ProLiant servers documents The HP Integrated Lights Out QuickSpecs contain support information and are available from the iLO product website http www hp com qo ilo HP ProLiant servers o ProLiant BL BladeSystem servers http www hp com go blades ProLiant DL series rack mount servers htto www hp com servers dl ProLiant ML series tower servers htto www hp com servers ml ProLiant SL series scalable system servers http h10010 www 1 hp com wwpc us en sm WFO2a 15351 15351 3896136 html Related information 61 A Command line interfaces Four command line interfaces CLIs are packaged in the CloudSystem release download e csst art exe provides command line access to run CloudSystem installation commands e csadmin exe provides command line access to run CloudSystem administrative commands e CS client CLI 8 0 0 2 msi provides the ability to run CloudSystem and OpenStack command lines from a Windows command prompt e
52. en ace sesoctst ee soutid saudi ntcatssousruie aeuoaes 5 Explanation of solution Componeniss ui24 icc atte sda taeda t cea at a derette alae aS en tl ues ai uals 6 Management hypervisors and integrated tools cccccccesessceeeeceeeseneeeeeeesesesnseeeeeeeeesteaeeeeeens 7 CloudSystem Foundation Componentve xicsdoosiecilecwhesetistedadedachledetaeeeiadel venexduyadendadzieanbedehedenteays 8 CloudSystem Enterprise components ces csisasei cries seitean se aseneat see aarsne th eientauees a8 e 8 CloudSystemi Network Siset hae atts ach carte ee acs Gots engin oie itn t el oat A aha late se tne AS 9 2 Reire yoy Degi meara a ccs a Sar i od rs lr ale or ir renal 10 Audience Sic ds acov avant ves a On pupa E E Been TAN eet EE EA Rain E E E ane oinn tere 10 PSS ON ONOMS os dee ta een acne EA E EE E duets sg dahon da E TRAE TEE AEGON 10 3 HP CloudSystem installation prerequisites cccccsceeeecccceeceeeeeeeeeeessaaeeeeees 11 Understand the installation process ssssnsoesssseonoeessseseoeesssssreoesssssrettsssssretrsrssssereressserererssst 11 Hardware FOCUITEINGNIS al cnn taied sa utes luiatnd ot ctiacatncsdyatnd a atasalatecectuden Siaeelavtiouaitneeet tuatietutewsslaass 12 Physical configuration hardware requireMents cccccescccececeseeseneeeeeeeceeseeeeeeeeeesseseeeeeseeeaaas 12 Management Ny DeIVisO Saas as accuncte sar aueter einer aretemuamecn conta ater Geta sel Geen ase avai 12 Complie Nodes ieie iara ea tar vale dS
53. epted Starts the Foundation base appliance virtual machine and checks the vCenter certificate ESX or SSH key KVM before creating the base appliance Certificates and keys are also checked before starting the other virtual appliances The config flag allows you to specify a configuration file if you didn t use the default deployer conf name The os cacert lt filename gt flag identifies the file used to verity the certificate or key The EULA is automatically accepted See Installing CloudSystem on an ESX cluster page 26 for instructions on pointing to the certificate See Installing CloudSystem on a KVM hypervisor page 33 for instructions on pointing to the SSH key Semi secure start of esstart start config auto accept cert eula accepted csstart start auto accept cert eula accepted Automatically accepts the vCenter Server certificate ESX or SSH key KVM and uses it to verify additional virtual appliances started by the Foundation base appliance 63 Using CLI commands Table 22 csstart commands continued Task CLI command Example What it does The config flag identifies the configuration file if you chose not to use the default deployer conf file name The EULA is automatically accepted Insecure start of start config csstart start Starts the Foundation base esstart insecure eula insecure eula appliance without checking th
54. etwork e vCenter Server name for the Cloud Data Trunk e vCenter Server name for the External Network 2 Log on to the Windows server that has network connectivity to the vCenter Server managing the management hypervisor See Important CloudSystem configuration information page 29 3 Navigate to the esstart XXX bat file with the preferred security checks and double click to launch csstart See Selecting hypervisor security level for CloudSystem installation page 29 Opening the bat file launches a browser opens URL localhost 5000 and starts the csstart setup assistant 4 Follow the prompts in the csstart setup assistant using the information you gathered in step one See Important CloudSystem configuration information page 29 5 When the installation is complete verify that the Foundation base appliance appears in the management cluster in vCenter Server The SDN appliance and network node appliances are created after entering Cloud Network settings in the CloudSystem Console See Troubleshoot installation issues page 52 Next step Setting up the CloudSystem Console for the first time page 44 Installing CloudSystem on an ESX cluster 6 Installing CloudSystem on a KVM hypervisor This chapter contains the procedures required to set up the network infrastructure and install the CloudSystem Foundation base appliance on a KVM management hypervisor The checklist below provides an overview of the installa
55. etwork bridge 2 Log in to the management hypervisor See Important CloudSystem configuration information page 41 3 Set permissions to run csstart chmod 700 csstart 4 Adda hole in the firewall for port 5000 on the Linux system iptables I INPUT 3 p tcp m state state NEW m tcp dport 5000 j ACCEPT 5 Launch the esstart XXX bat file with the preferred security checks See Selecting hypervisor security level for CloudSystem installation page 40 6 Open a supported browser and type http IP_address_of the KVM management _host 5000 7 Follow the prompts in the csstart setup assistant using the information you gathered in step one See Important CloudSystem configuration information page 41 8 When the installation completes log in to the management hypervisor and verify that the Foundation base appliance was created virsh list all The SDN appliance and network node appliances are created after entering Cloud Network settings in the CloudSystem Console Installing CloudSystem on a KVM hypervisor See Troubleshoot installation issues page 52 Next step Setting up the CloudSystem Console for the first time page 44 Configuring the KVM management environment 43 7 Setting up the CloudSystem Console for the first time To complete the final step of the CloudSystem Foundation installation add Cloud Networking information to the CloudSystem Console Once the network setting is saved the Foundation base appliance
56. he base appliance is installed and Cloud Networking settings are saved in the CloudSystem Console A vCenter proxy appliance supports ESX configurations OpenStack Nova and Neutron agents reside in the vCenter proxy appliance which acts as a proxy for the ESX management hypervisor The management hypervisor accepts each vCenter Server cluster as one large compute node This configuration allows your cloud to take advantage of HA and load balancing features supported in vCenter Server The vCenter proxy appliance runs the OpenStack agents for up to 12 ESX clusters Foundation automatically creates the first vCenter proxy appliance when the first ESX cluster is activated in the CloudSystem Console The CloudSystem Console GU supports administrative tasks such as creating storage templates activating compute nodes setting up networks monitoring the Foundation base appliance and performing maintenance tasks on the appliance The CloudSystem Portal GUI is accessed from a modified Foundation base appliance URL by appending portal to the Foundation IP address Example https Foundation_IP portal Instances are created and managed from this portal HP Operations Orchestration OO Central provides the ability to run scripted workflows on the Foundation base appliance Access OO Central from the Integrated Tools screen in the CloudSystem Console HP OO Studio provides the ability to edit the OO workflows It has a separate ins
57. he maximum heop size for the jetty Atlas Java web server from Xmx512m to Xmx750m Example cloudadmin Basehost sudo vi ci etc jvm d jetty Atlas cloudadmin Basehost cat ci etc jvm d jetty Atlas Xss256k Xms256m Xmx750m XX PermSize 128m XX ReservedCodeCacheSize 32m XX UseCompressedOops verbose gc XX PrintGCDetails Xlogge ci jetty Atlas logs gc log XX UseGCLogFileRotation XX NumberOfGCLogFiles 2 XX GCLogFileSize 1m 5 Save the changes 6 Restart the jetty Atlas Java web server using the following command cloudadmin Basehost sudo crm resource restart JettyAtlas 72 Configuring a large scale CloudSystem deployment
58. his step 7 Click Next 8 Enter the user name and password required to log in to OO Central OO Central runs on the Foundation base appliance The user name and password are the same as the user name and password used to access the CloudSystem Console except that you must enter the OO user name with all lower case letters Once you log in to OO Central for the first time you can change the user name and password 9 Click Install 10 Verify that the appliance was created successfully After Enterprise is installed a Tools and Configuration pane are added to the Enterprise screen The Tools pane displays links to the Cloud Service Management Console and the Marketplace Portal All existing Foundation functionality will continue to be available Enterprise appliance details can be monitored in the CloudSystem Console from the Enterprise screen Perform all management tasks for the Enterprise appliance in the CloudSystem Console on the Settings screen Installing CloudSystem Enterprise Procedure 15 Configure Enterprise to use the Foundation NTP servers for time sync If you are using an ESX management hypervisor to mange the Enterprise appliance then you will need to perform the following procedure l 5 Enable the console user for the Enterprise appliance See appendix C Supported console operations on the CloudSystem Foundation appliance in the HP CloudSystem 8 0 Administrator Guide at the Enterprise Information Li
59. i Data Center Management Network BFC SAN Network Bl Provider Private Networks Hl iscsi Network BH Cloud Management Network I External Network SDN vCenter proxy appliance appliance CloudSystem Admin Console API CLI Foundation base appliance CloudSystem OpenStack Portal API CLI OO Contrel 3PAR vCenter Server gt ESX clusters Enterprise appliance Network definitions Management Trunk The Management trunk contains the following networks e Data Center Management Network This network provides access to the CloudSystem Console which is the interface for the Foundation base appliance REST APls calls are made from this Networking requirements 17 network The Foundation base appliance and the Enterprise appliance access vCenter Server and the HP 3PAR storage system over this network Three or more vCenter Server are supported o The Foundation base appliance uses this network to access the vCenter Server that is managing the management hypervisor o The vCenter proxy appliance uses this network to access the vCenter Server that is managing ESX compute clusters This can be a separate vCenter Server or the same vCenter Server used by the Foundation base appliance o The Enterprise appliance also uses this network to access vCenter Server Enterprise can be configured to use a third vCenter Server or it can access one of the two existing vCenter Servers e Cloud Management Network This private net
60. infrastructure section IMPORTANT The following information must match exactly the configuration you created in the network infrastructure section See Configure the network infrastructure on the KVM management hypervisor page 36 You may alter this information to fit your specific configuration needs as long as it corresponds to the setup you performed previously NOTE Delete any trailing spaces after bridge names The bridge names should not contain any white space Data Center Management Network bridge br dc mgmt Cloud Management Network bridge br cloud mgmt Cloud Data Trunk bridge br cloud trunk External Network bridge br external Save and close the configuration file wq Run the script to create the Foundation base appliance csstart start type of security eula accepted See csstart commands page 63 for details on the secure semi secure or insecure mode for csstart NOTE You can modify the above command if you want to generate a log file which is helpful in the event of an error Use csstart start v log file lt name of log file gt Verify that the Foundation base appliance was created on the management hypervisor The SDN appliance and network node appliances are created later after entering Cloud Networking settings in the CloudSystem Console Additional CLI tasks 65 IMPORTANT Do not move or delete images after you create the Foundation base app
61. ints routing Resources Volumes Cinder block storage for VMs g E TT Administrator Servers Storage Networking Manage resources and access Provision VM Hosts HP Converged Infrastructure HP CloudSystem Enterprise expands on CloudSystem Foundation to integrate servers storage networking security and management to automate the lifecycle for hybrid service delivery Template architects can use Enterprise to create infrastructure templates and offer them as services in a Marketplace Portal Users select services from a catalog and manage their subscriptions When a service is requested Enterprise automatically provisions the servers storage and networking Enterprise also includes an enhanced set of Operations Orchestration workflows CloudSystem Enterprise provides a hybrid cloud management platform where you can manage all cloud services See CloudSystem Enterprise components page 8 Figure 2 CloudSystem Enterprise Architects Consumers e Design and publish Browse request amp manage virtualized services infrastructure and applications services e Topology and service Compute Network design tools services services Service Catalog Administrator Storage services Manage catalog subscriptions HP Storage and providers Explanation of solution components HP Networking The component
62. l HP CSA is the administrative portal for the Enterprise appliance Designs are created in the HP CSA portal CloudSystem networks See Network definitions page 17 Explanation of solution components 9 2 Before you begin HP CloudSystem is a flexible cloud management solution that supports multiple installation options This guide does not cover all possible options If the installation required by your organization does not match the installation described in this guide contact an HP Support representative for assistance Audience This guide is intended for experienced system administrators with a working knowledge of the following concepts e TOR switches for networking e CLI commands for Windows and Linux e VMware vCenter Server functionality if using ESX hypervisors and compute nodes e VMware distributed and standard vSwitches e Red Hat KVM hypervisor configuration and use If you plan to use the OpenStack CLI and APIs to manage some of the cloud resources from the command line it is helpful to have experience with OpenStack technologies such as Nova Glance Cinder and Neutron Assumptions 10 This installation guide makes the following assumptions about your readiness for the installation Make sure these assumptions match the state of your environment before you begin the installation e All hardware required to support a CloudSystem installation is installed and configured You can use the requiremen
63. l resource providers e Associate resource offerings like the ones imported in the previous section to the appropriated provider Matrix OE resource offerings with Matrix OE resource providers Refer to the Enterprise Information Library for HP CSA documentation on configuring a Matrix OE resource provider Configuring a Matrix OE resource provider 71 C Configuring a large scale CloudSystem deployment In a large scale deployment CloudSystem Foundation can manage over 4 000 virtual machine instances To a le is type of deployment HP recommends that you update the maximum heap size parameter of the jetty Atlas Java web server on the Foundation base appliance The best practice is to perform the procedure in this section after the Foundation base appliance is successtully deployed using cssstart and before CloudSystem is made available for use by end users See also Working with the csadmin CLI in the HP CloudSystem 8 0 Administrator Guide at Enterprise Information Library Prerequisites e Minimum required privileges Infrastructure administrator e The csadmin CLI package is installed on the CloudSystem Foundation base appliance Procedure 30 Updating the maximum heap size of the j ett y Atlas Java web server 1 From the csadmin CLI enable the cloudadmin user access on the Foundation base appliance 2 Open the VNC Console terminal window to the Foundation base appliance 3 Log in as the cloudadmin user 4 Change t
64. liance In order to speed up virtual machine boot times and save disk space csstart does not make a full copy of the image A copy is shared across all of the virtual machines See Troubleshoot installation issues page 52 Next step Setting up the CloudSystem Console for the first time page 44 Enabling REST API for storage drivers This is a condensed version of the OpenStack instructions You can see the complete instructions here Enabling the HP 3PAR Fibre Channel and iSCSI Drivers Prerequisites e HP3PARFCDriver is installed with OpenStack software e HP3PARISCSIDriver is installed with OpenStack software Procedure 19 Enabling REST API for storage drivers e Verify that the HP 3PAR WebServices API server is enabled and running on the HP 3PAR storage system a Using administrator credentials log on to the HP 3PAR storage system ssh 3parad lt HP EPAR IP Address gt b Check the current state of the WebServices API server showwsapi c If the WebService API server is disabled then start it startwsapi d Ifthe HTTP or HTTPS state is disabled enable one of them setwsapi http enable setwsapi https enable NOTE If you need a list of WebService API commands type setwsapi h A list of Web Service commands will display Using the CLI to access the Enterprise console You can log in to the Enterprise appliance and view configuration files and network properties using the following commands e virsh console en
65. llowing production networks e Provider Network A Provider Network is a data center network routed through the existing data center infrastructure Adding a Provider Network allows you to add an existing data center network to any number of virtual machine instances in the cloud e Private Networks Private Networks are created from a pool of VLANs The cloud administrator configures this pool in the CloudSystem Console Then when the cloud administrator switches to the CloudSystem Portal and creates a Private Networks the OpenStack Neutron networking service assigns a VLAN from the pool OpenStack Neutron networking manages all aspects of this network including external routing IMPORTANT All of the networks described above must be distinct networks with the exception of the External Network You can use the same network for the External Network and the Data Center Management Network Configuration of management networks Management network configuration varies depending on the management hypervisor configuration 18 HP CloudSystem installation prerequisites The following figure shows a sample configuration with an ESX management host networks and ESX compute nodes Figure 6 ESX management host with ESX compute nodes ESX cluster mgmt host Enclosure External router ESX compute nodes ESX compute nodes Onboard Administrator Virtual Connect CloudSystem Foundation CloudSystem Enterprise V
66. loud Data Trunk See KVM sample network configuration page 36 a Open the ifefg ethQ file and add the following lines MASTER bondc SLAVE yes NM_CONTROLLED no Save the change and close the file Open the ifefg ethR file and add the following lines MASTER bondc SLAVE yes NM_CONTROLLED no Save the change and close the file Create a new bond configuration file using the name ifefg bondC This bond connects to the Cloud Data Trunk bridge The configuration file should contain the following lines DEVICE bondC BOOTPROTO none ONBOOT yes USERCTL no NM_CONTROLLED no BONDING OPTS mode 5 miimon 100 BRIDGE br cloud trunk Save the change and close the file Create a new bridge configuration file using the name ifefg br cloud trunk This is the bridge that connects the network node appliance to the Cloud Data Trunk The configuration file should contain the following lines DEVICE br cloud trunk TYPE Bridge BOOTPROTO none ONBOOT yes NM_CONTROLLED no DELAY 0 cloud trunk vlan all Save the change and close the file Configuring the CloudSystem network infrastructure 39 6 Run the following command to restart networking and allow the new configuration to take effect service network restart 7 Run the following command to see a list of the bridges that were created and the interfaces for each bridge bretl show 8 Run the following command to make sure all of the interfaces bridges and bond
67. mand csstart errors 53 54 Table 19 ESX troubleshooting tips continued Symptom Possible cause and recommendation 1 Edit csstartgui bat 2 Add set PYTHONIOENCODING UTF 8 as the first line of the file and save the file 3 Double click the file e Run the Linux version of csstart When you install CloudSystem on a KVM host you can run csstart on the hypervisor e Set English or Chinese as the preferred language in the web browser esstart fails to install CloudSystem on vCenter Server and you see the error message Intlmp1 ESx cloneFromTemplate com vmware vim25 No Permission User does not have proper privileges in vCenter Server to create virtual machines 1 Log in to vCenter Server 2 Add the privilege for clone operations to the role that is running csstart This operation allows users to allocate space in the datastore create virtual machines power up and down virtual machines and delete virtual machines on the management cluster 3 From the Host and Cluster view select the management cluster A Right click the management cluster and select Add Permissions The Assign Permissions window opens 5 In the left pane select the role that is running csstart This is the role that receives the new permission 6 In the right pane scroll down to Virtual machine and expand Provisioning 7 Select the clone virtual machine permission 8 Click OK to save the new permission for the role
68. ment Network External Network Enterprise f SDN appliance appliance Network node appliances vy Oasis Gasp CLIC CloudTrunk VLAND ID All 4095 Cloud Data Trunk Vswitch Port group Cloud Data Trunk Provider Networks Private Network Create the ESX management hypervisor and configure the network infrastructure The following procedure describes the steps required to create the ESX management hypervisor and configure the network interfaces The procedure is based on the information provided in the image above but you can modify the configuration to fit your network needs Do not begin the procedures in this section until you read the following important notes about configuring networks Table 12 Important network configuration information Important to know Do not configure the iSCSI initiators on the management hypervisor Why it matters iSCSI initiators are set up on the compute nodes not the management hypervisor Initiators check to see which storage resource on the network are available Standard or distributed vSwitch names must be unique to each host in vCenter Server vCenter Server requires that all vSwitch names on a host be unique names Step 4 Generic names are used in this procedure Make sure to substitute the actual names of your interfaces ifcfg eth lt IDs bonds ifcefg bond lt IDs tagged VLANs bond lt ID gt lt VLANID gt and bridges ifc g
69. n such as passwords and should be kept secure When installing with Windows you should run the csstart setup assistant from a directory with restricted access in order to protect this file Step 2 DRS is recommended for use in a cluster that is also hosting virtual machines other than the CloudSystem management hypervisors The automatic placement of CloudSystem management hypervisors in the cluster may overload some hypervisors if DRS is not in use If you use a single management host that is not part of a DRS cluster then make sure you have enough resources to host all CloudSystem virtual appliances When you run the csstart setup assistant you will be asked for a Glance disk size The installation creates a Glance disk on the same datastore where the base appliance template is stored See Formula to determine the storage requirements for the management hypervisor page 12 for sizing calculations Each OVA in the datastore needs to have a unique name You cannot use separate folders in the datastore csstart creates the virtual appliances in the first host of a non DRS cluster There is no way to select a specific host All hosts in the non DRS cluster need to be large enough to support all CloudSystem virtual appliances You must have sufficient space for the virtual appliance boot disks as well as the Glance disk or the installation process will not be able to complete Step 3 Return to procedure I
70. nd help for all tasks and procedures Browse help HP Software documents The latest versions of HP Software product manuals and white papers can be downloaded from the HP Software Product Manuals web site at http support openview hp com selfsolve manuals Finding documents on the HP Software Product Manuals web site Follow these instructions to access all technical manuals for HP Cloud Service Automation and HP Operations Orchestration 1 2 Se Go to the HP Software Product Manuals web site http support openview hp com selfsolve manuals Log in with your HP Passport user name and password OR If you do not have an HP Passport click New users please register to create an HP Passport then return to this page and log in In the Product list box scroll down and select a product name In the Product Version list select the version of the manuals that you are interested in In the Operating System list select the relevant operating system Click the Search button to see a list of linked titles HP Insight Management documents The latest versions of HP Matrix Operating Environment manuals white papers and the HP Insight Management Support Matrix can be downloaded from the HP Enterprise Information Library at http www hp com go matrixoe docs including the following documents HP Matrix Operating Environment Release Notes HP Insight Management Support Matrix HP Matrix Operating Environment Infrastruct
71. ng CloudSystem Enterprise page 49 46 CloudSystem Foundation installation next steps 9 Preparing HP Operations Orchestration for CloudSystem Foundation HP Operations Orchestration OO is a next generation IT Process Automation solution OO supports CloudSystem in two ways e HP Operations Orchestration Central OO Central is integrated with CloudSystem Foundation It allows you to run workflows to perform administrative tasks in Foundation e HP Operations Orchestration Studio OO Studio is a separate installation It allows you to customize workflows which you can then run in OO Central Using OO Central To access OO Central open the CloudSystem Console and select Integrated Tools from the main menu OO Central comes with five general use workflows which perform administrative tasks for CloudSystem Foundation You can run these workflows from OO Central e base cp This workflow provides support for integrations with various solutions email excel active directory file system etc It also includes basic operations used by other the content packs e systems cp This workflow provides support for integrating operating systems such as AIX FreeBSD HP UX Red Hat Solaris SUSE Linux and Windows e virtualization cp This workflow supports integration with virtualization platforms such as Citrix Xen Server Hyper V KVM SCVMM and VMware e hp solutions cp This workflow provides support for integrating
72. nstances are started in the same datastore that contains the OVA If multiple OVAs with the same name are stored in the datastore csstart will not know which one to use to create the instance The Enterprise image must be deployed in the same datastore as the other CloudSystem virtual appliance images The Enterprise installation will fail if the Enterprise OVA is not included in the same datastore as the other virtual appliance images Do not move or delete images or rename the images after you create the base appliance In order to speed up virtual machine boot times and save disk space csstart does not make a full copy of the image Changing the name or location of the image disrupts the operation of the shared copy encoded by ecsstart Prerequisites e The management hypervisor network infrastructure is in place See Create the ESX management hypervisor and configure the network infrastructure page 27 e You have administrator privileges to log in to vCenter Server e One large datastore is created with approximately 2 TB to support the virtual appliance boot drives plus additional storage for OpenStack Glance images See Formula to determine the storage requirements for the management hypervisor page 1 2 e The management hypervisor has connectivity to the HP 3PAR storage system This is required if you are using block storage for instances See HP 3PAR StoreServ Storage documents page 60
73. nt pack page 68 e Configuring system accounts for the HP CSA content pack page 69 e Configuring system properties for the HP CSA content pack page 69 NOTE In the following instructions CSA_HOME is the directory where HP CSA resides In Enterprise SCSA_HOME ci usr local hp csa In CloudSystem SSL is already configured between HP CSA and OO Central Procedure 20 Configuring an internal user The internal user configures OO Central for HP CSA and imports the OO flows When importing flows this user is configured in the OO input file used by the process definition tool 1 Log in to OO Central https lt cs foundation_ip or _hostname gt oo 2 Select System Workspace The System Workspace screen displays Select Security Internal Users Click Add In the User Name field type ew csaoouser 6 In the Password field type cloud 7 In the Roles field type ADMINISTRATOR SYSTEM ADMIN 8 Click Save 9 Log out of OO Central and log back in as the internal user csacouser Configuring HP Operations Orchestration to integrate with HP CSA 67 Procedure 21 Deploying required content packs to HP CSA Download the following content packs from HP Live Network Operations Orchestration to a Windows or Linux staging server ool0 sm cp 1 0 0 0010 sa cp 1 0 2 IMPORTANT Make sure to deploy theses required content packs before deploying the HP CSA content pack 1 From OO Central select C
74. o documentation bundled with the OO Studio program files for additional information on using workflows e Refer to the HP CloudSystem 8 0 Administrator Guide at Enterprise Information Library for additional information 48 Preparing HP Operations Orchestration for CloudSystem Foundation 10 Installing CloudSystem Enterprise CloudSystem Enterprise is an laaS PaaS and SaaS solution used for complex cloud provisioning Administrators create infrastructure templates and provide them as service offerings in the Marketplace Portal Enterprise includes designer software the Marketplace Portal and full HP CSA functionality See Explanation of solution components page 6 for a detailed description of components IMPORTANT Do not change the Foundation base appliance network configuration host name IP address subnet mask gateway address DNS server or alternate DNS server after Enterprise is installed Doing so will break communication between Foundation and Enterprise and you will not be able to create subscriptions create or edit designs or manage existing subscriptions in HP CSA Installing the Enterprise appliance Use the CloudSystem Console to launch the Enterprise installation When you install Enterprise a new virtual appliance is created on the management hypervisor The entire installation process should take about 20 minutes Table 18 Important CloudSystem configuration information Important to know
75. oint your concern by posting the document title in the Subject line of your mail message Related information e HP CloudSystem documents page 58 e HP Software documents page 59 e HP Insight Management documents page 59 e Third party documents page 59 e HP 3PAR StoreServ Storage documents page 60 e HP ProLiant servers documents page 61 Use this section to learn about available documentation for HP CloudSystem components and related products HP CloudSystem documents 58 The latest versions of HP CloudSystem manuals and white papers can be downloaded from the Enterprise Information Library at http www hp com go CloudSystem docs including the following documents e HP CloudSystem 8 0 Release Notes e HP CloudSystem 8 0 Installation and Configuration Guide e HP CloudSystem 8 0 Administrator Guide e HP CloudSystem Help e HP CSA Concepts Guide e HP CSA Release Notes Support and other resources HP CSA API Quick Start Guide HP CSA Troubleshooting HP CSA API Reference HP CSA Documentation List HP Operations Orchestration Concepts HP Operations Orchestration Central User Guide HP Operations Orchestration Application Program Interface API Guide Online help for the CloudSystem Console is available by clicking the help control button Ed The help control button expands the help sidebar Links in the sidebar open UI screens for Recommended Tasks help for the current screen Help on this page a
76. ontent Workspace The Content Workspace displays 2 From the Flow Library tab select Deploy New Content The Deploy New Content dialog displays 3 Click Add 4 Browse to the staging server that contains the content packs you downloaded from HP Live Network The staging server can be a Windows or Linux server 5 Select 0010 sm cp 1 0 0 and click Open 6 Click Deploy NOTE The deployment can take several minutes The cursor displays the busy icon during deployment You can find information about the success of the deployment in the Deployment Result section 7 Repeat steps 3 6 for the 0010 sa cp 1 0 2 content pack 8 Click the Close button to return to the Content Workspace Procedure 22 Deploying the HP CSA content pack Make sure the required content packs are deployed in OO before you complete this procedure 1 Copy the CSA_HOME CSAKit 4 0 00 Flow Content oo10 csa cp 4 0 0 jar file from the Enterprise appliance to your staging server a From the Enterprise appliance console enable the cloudadmin user access through the csadmin command line interface CLI See the Working with csadmin appendix in the HP CloudSystem 8 0 Administrator Guide at Enterprise Information Library When enabled log in to the Enterprise appliance console as cloudadmin c Copy the SCSA_HOME CSAKit 4 0 00 Flow Content oo10 csa cp 4 0 0 jar file from the Enterprise appliance to the staging server scp ci usr local hp csa CSAKit 4 0 00
77. or Unknown 2 Read the message for problem identification and potential solutions 3 Expand the activity to add notes to the activity details Examine the appliance When VM host is down or nonresponsive virtual machine ests 1 From the local computer use the ping command to determine if you can reach the appliance e Ifthe ping command is successful determine that the browser settings especially the proxy server are correct Consider bypassing the proxy server e Ifthe ping command did not reach the appliance ensure that the appliance is connected to the network 2 Log onto hypervisor to verify that the hypervisor is running Troubleshoot installation issues Recommendation Details Verify that the virtual guest for the appliance is operational Ensure that the VM host configuration is valid Verify the accuracy of the IP address and other network parameters for the VM host From the management console ensure that the appliance network settings are accurate Examine the hypervisor performance data If the appliance is running at 100 utilization restart the hypervisor Enable console access About console access Use the following csadmin console users CLI commands to enable console access and set the password After running the command you can locate logs for additional troubleshooting information The VM_name is the virtual machine where you want to execute the command The c
78. ork You can use the same network for the External Network and the Data Center Management Network For a detailed explanation of the networks see Overview of network topology page 16 The figure below shows a visual representation of the recommended configuration for networks Configuring the CloudSystem network infrastructure 35 Figure 11 KVM sample network configuration KVM appliance management CloudSystem components vSphere CloudSystem VM Foundation base 5 X appliance VM vNICi vCenter proxy CloudSystem appliance VM Enterprise appliance VM VM Network node appliance VMs multiple a COICO NTC JE VNC Management Vswitch Port groups Management Trunk Data Center Management Network Cloud Management Network External Network Cloud Data Trunk Provider Networks Private Provided Network NOTE The vCenter proxy appliance shown in the figure is only used if you are managing ESX compute nodes from a KVM management hypervisor Configure the network infrastructure on the KYM management hypervisor The following procedure describes the steps needed to configure the network interfaces on a KVM hypervisor The procedure is based on the information provided in the image above but you can modify the configuration to fit your network needs Read the following important information before you configure the networks for the Foundation base appliance Table 15
79. ork intrastrictite soce teeecsieeedanswedskvecatexeseriibeteecredeseaineecaxeceestesinsnweeh etext 26 Create the ESX management hypervisor and configure the network infrastructure ccceceeeee 27 Configuring the ESX management environment ccccccccceeesecneeeeeeeceseneeeceeeseseaaeeeeeseneseeeeeeeees 28 Selecting hypervisor security level for CloudSystem installation ccccessesseeeeeesteeeeeeteeeeenenees 29 Configuring the Foundation base appliance on ESX ccccceesseeeceeesseeeeeeeeesensseeeeeeeesstsaeeees 29 6 Installing CloudSystem on a KVM hypervisor ccccceeseerteeeeeeeeeeeeeeeeeeees 33 Creating the management hy PervisGr isc csnszcesccessnsdiSeusecxtanshjdaed ven ldswierad deetdeowtaowsanes duauauentdexed anaes 33 Preparing the UAV acer i ste eas Seg i ates eA ae a OE SE da eh 33 Installing RA E lanene a toast a ate O a E ates Te 33 Creating a local YUM repository and validating RHEL RPMS cssceccessseeeeeeteeeeeeeteeeeeeenees 34 Configuring the CloudSystem network intrastructites accscc 0aaieiad ees eeic creer iaecev erences 35 Configure the network infrastructure on the KYM management hypervisor ccceeeeeeseeeeees 36 Configuring the KVM management environment cccccccceeeseceeeeeeceeeneeeeeeeeesssaaeeeeeseeeseeeeeeeees 40 Selecting hypervisor security level for CloudSystem installation cccceeseeseeeeeeseeeeeeeteeeeeeenees 40 Configuring the Foundation
80. pdate Service This service provides access to HP technical resources for assistance in resolving software implementation or operations problems The service also provides access to software updates and reference manuals either in electronic form or on physical media as they are made available from HP Customers who purchase an electronic license are eligible for electronic updates only Information to collect before contacting HP 57 With this service HP CloudSystem customers benefit from expedited problem resolution as well as proactive notification and delivery of software updates For more information about this service see the following website http www hp com services insight Registration for this service takes place following online redemption of the license certificate HP authorized resellers For the name of the nearest HP authorized reseller see the following sources e In the United States see the U S HP partner and store locator website http www hp com service_ locator e In other locations see the Contact HP worldwide website http www hp com go assistance Documentation feedback HP is committed to providing documentation that meets your needs To help us improve the documentation send your suggestions and comments to docsfeedback hp com In your mail message include the following information They are located on the front cover e Document title e Published date e Edition number Help us pinp
81. pported versions Additional resources Use this to Where do find it HP Insight Management Support Refer to the supported HP servers hito www hp com go Matrix version 7 3 1 tables CloudSystem supports all insightmanagement docs servers supported in the HP Matrix Operating Environment version 7 3 1 e Table 26 e Table 28 e Table 29 e Table 30 The server must have a check in the Matrix OE column HP Support Center Verify the compatibility of your servers http www hp com go hpsc drivers firmware and software SAN and Storage The table below contains SAN and storage requirements for ephemeral and block storage Table 7 Hardware requirements Requirements Purpose Find more information Ephemeral storage This storage is used for provisioned See HP Matrix Operating Environment instances and is defined in the flavor version 7 3 1 http www hp com When an instance is deleted this go insightmanagement docs storage is released e Chapter 4 Managed system hardware Block storage Block storage allocates storage to See HP 3PAR documentation 3 PAR F Class P7000 P10000 series virtual machine instances attach detach Storage is presented to a single instance via the compute e pre configured zones where node where the instance is hosted storage system is zoned to the appropriate virtual machine host Fibre Channel fabric support e open zoning where no zoning configura
82. r ISO image and complete the following steps Procedure 6 Installing RHEL on the management hypervisor 1 Test the media 2 Set the language 3 Set the keyboard for the language 4 Configure the installation device types a Select Specialized Storage Devices b Click the Multipath Devices tab c Select Boot Volume Creating the management hypervisor 33 WE TIP Take a screen capture of the boot volume to use as a reference for later contiguration d Acknowledge the storage device warning typically Yes discard any data 5 Set the Fully Qualified Domain Name FQDN as the Hostname 6 Click Next and skip configuring the network until later 7 Select the time zone 8 Set the root password 9 Select Use All Space and check the option to Review and modify partitioning layout 10 Define logical volumes The root directory needs to have enough space to accommodate the appliance images and Glance repository See Formula to determine the storage requirements for the management hypervisor page 12 11 Write changes to disk 12 Select the Minimum install 13 Unmount the DVD or ISO image and reboot 14 Update the RHEL installation with the latest security patches from https access redhat com security updates 15 Log in to the management host 16 Configure DHCP_HOSTNAME to allow the management host to register itself with the DNS server vi etc sysconfig network DHCP_HOSTNAME management host name 17 Ad
83. rise appliance HP CloudSystem Tools 8 0 Mar 2014 contains the csstart installation script x x x x and the CLI packages HP CloudSystem OO Studio 8 0 Mar 2014 contains OO content packs and OO Studio installation and upgrade Signature files Each zip file has a corresponding signature file Signature files are used to verify the authenticity of the downloaded files See HP GPG or RPM signature Verification Contents of CloudSystem zip files The contents of each CloudSystem zip file are described in the following section Installation kits 21 22 NOTE Each qcow2 file comes with a corresponding sha1 checksum file When csstart runs it uses the checksum file to verify that the files are copied to the hypervisor without errors HP CloudSystem Foundation ESX 8 0 Mar 2014 27550 01317 zip e CS Base 8 0 0 20 0va Open Virtualization Format OVF package for the base appliance on an ESX hypervisor e CS Base 8 0 0 20 0va OVF package for the SDN appliance on an ESX hypervisor e CS NN 8 0 0 20 0va OVF package for the network node appliance on an ESX hypervisor HP CloudSystem Foundation KVM 8 0 Mar 2014 27550 01318 zip e CS Base 8 0 0 20 qcow2 Disk image for the base appliance on a KVM hypervisor e CS SDN 8 0 0 20 qcow2 Disk image for the SDN appliance on a KVM hypervisor e CS NN 8 0 0 20 qcow2 Disk image for the network node appliance on a KVM hypervisor NOTE Each
84. rsion needs an upgrade 1 Apply the OO Studio upgrade using the Upgrading OO Studio page 48 procedure Enterprise upgrade errors The table below contains errors that can occur during an Enterprise upgrade or when using the HP CSA management console Support dump details You can create a support dump from the csadmin CLI if you have it installed on your Windows or Linux server It is included in the CloudSystem Tools 8 0 0 20 tar Once csadmin is installed there are two relevant commands csadmin appliance list lists the names of the available management virtual machines This lets you find the appropriate appliance name Scsadmin appliance supportdump av lt appliance_ names creates a dump of all relevant logs and stores it on the management hypervisor The support dump is saved to your staging server OO Studio installation errors 55 56 Table 21 Enterprise troubleshooting tips Symptom The Enterprise installation progress indicator is not visible Possible cause and recommendation The console session was terminated 1 While the installation is in progress keep your console session active e Do not refresh the Enterprise screen e Do not log off the CloudSystem Console NOTE While the installation is in progress you can navigate to other console screens and see the progress indicator when you return to the Enterprise screen You see the message CloudSystem Enterprise installation f
85. s e CloudSystem Foundation is the laaS solution used for provisioning virtual machine instances Management tasks for both Foundation and Enterprise are performed from Foundation s CloudSystem Console Foundation includes the following components which all run on virtual machines on one or more management hypervisors o The Foundation base appliance contains the core services and functionality of the CloudSystem Console The CloudSystem Portal OpenStack services OO Central and supporting CLls also reside on the Foundation base appliance The SDN Software Defined Networking appliance is the control center for the network infrastructure of the Foundation base appliance When the OpenStack Neutron service needs to define a new router or a plugin on the Foundation base appliance the request is sent to the SDN appliance CloudSystem Foundation automatically creates the SDN appliance after the Foundation base appliance is installed and the Cloud Networking settings are saved in the CloudSystem Console The network node appliances manage various network services such as DHCP and L3 routing services for provisioned virtual machines and provisioned virtual networks The SDN appliance manages the network node appliances as a cluster When the SDN appliance receives a request to create a new router it creates the router in one of the network node appliances Multiple network node appliances are created during installation after t
86. s are configured and running ifconfig 9 Verify that the network is configured correctly by pinging the DNS server or the gateway server for the Foundation base appliance Configuring the KVM management environment The management environment consists of a single management hypervisor host or a cluster of management hypervisor hosts that contain the following virtual appliances e A Foundation base appliance e An SDN appliance e Three network node appliances e An optional vCenter proxy appliance for ESX compute nodes e An optional Enterprise appliance if you are using CloudSystem Enterprise The csstart installation script launches a setup assistant to guide you through the installation process When you run csstart the setup assistant opens and displays fields for capturing details about the new virtual appliance and network configuration The information is saved in a configuration file called deployer conf Running csstart applies the configuration information saved in deployer conf to the virtual appliance designated to host the Foundation base appliance When the installation completes the Foundation base appliance appears in the management hypervisor appliance list The SDN appliance and the network node appliances are automatically created after the Cloud Networking settings are entered and saved during first time setup Selecting hypervisor security level for CloudSystem installation 40 You can select one of three sec
87. s of CloudSystem Foundation and CloudSystem Enterprise are explained below e Management hypervisors and integrated tools page 7 e CloudSystem Foundation components page 8 e CloudSystem Enterprise components page 8 e CloudSystem networks page 9 6 Welcome to HP CloudSystem Figure 3 CloudSystem architecture neutron L2 and L3 agents E SDN Controller i SDN plug in neutron L2 agent neutron L2 agent b 1 Management hypervisors and integrated tools Management hypervisors host the various virtual machine appliances that make up the CloudSystem solution Both ESX and KVM hypervisors are supported VMware vCenter Server acts as a central administrator for ESX clusters that are connected on a network vCenter Server allows you to pool and manage the resources of multiple hosts as well as monitor and manage your physical and virtual infrastructure You can import and activate ESX clusters in the CloudSystem Console after you register a connection with vCenter Server VMware vCloud Networking and Security vCNS provides security for the ESX compute hosts An HP 3PAR storage system provides a method of carving storage for boot and data disks Block storage drivers are imported from the HP 3PAR storage system to the CloudSystem Console An FC SAN ISCSI or Flat SAN connects the HP 3PAR storage system to compute nodes or ESX clusters Explanation of solution components 7 CloudSystem Foundation component
88. sadmin console users commands are supported on the Foundation base appliance the Enterprise appliance and the Proxy appliances To enable console access 1 2 Enter the command Open the CLI csadmin console users enable vm name VM_name To set the password console access Open the CLI Enter the command csadmin console users set password password CAPasswd vm name VM_name Where CAPasswd is the password for the Cloud Administrator For more information on the use of CLI see HP CloudSystem 8 0 Administrator Guide at Enterprise Information Library csstart errors The log file is the best resource for identifying the type of error that occurred Check the log file first to narrow down error possibilities You can also review the problems and recommendations listed below Table 19 ESX troubleshooting tips Symptom You see the error Installation failed Please correct the error and try again Possible cause and recommendation The csstart web UI does not run correctly on a Japanese Windows system e Before running csstart set the environment variable PYTHONIOENCODING UTF 8 in the steps below If you are running csstart using one of the csstartgui bat files set this variable in the csstartgui bat file that you are using If you are running csstart from a command prompt window set this variable in the csstartgui bat file before running the csstart gui start browser com
89. set to automatically sync with the NTP server If the Foundation and Enterprise appliance date time is out of sync then you will not be able to create designs in HP CSA The management hypervisor must be configured with a FQDN not an IP address The FQDN is necessary when attaching block storage volumes using the 3PAR storage system You cannot have multiple copies of an appliance image stored in vCenter Server esstart looks for appliance image names at random and could select the wrong image Using different datastores or different folders does not resolve the issue If you need two copies of an appliance image on a single instance of vCenter then you must have unique names for each image Edit the deployer conf file with a text editor to point to the correct image Configuring the ESX management environment 29 30 Table 13 Important CloudSystem configuration information continued Important to know The vCenter Server user running csstart only needs the top level privileges for Datastore Network Resource and Virtual machine Why it matters The vCenter Server user that is stored in the base appliance by csstart does not need full administrator privileges on the Windows server running vCenter Server The user does not need full access to vCenter Server Allocating the lowest allowed level of privileges optimizes data center security The deployer conf file contains confidential informatio
90. ta 70 Configuring a Matrix OE resource provideress iecrennnanwrienine ania awe ae as 71 C Configuring a large scale CloudSystem deployment cceeeeeseeeeeeeeeees 72 4 Contents 1 Welcome to HP CloudSystem HP CloudSystem provides a software defined approach to managing the cloud in a converged infrastructure environment CloudSystem consists of two offerings HP CloudSystem Foundation is based on the HP Cloud OS distribution of OpenStack Cloud Software It integrates hardware and software to deliver core Infrastructure as a Service laaS provisioning and lifecycle management of compute network and storage resources You can manage CloudSystem Foundation from an administrative console self service portal CLls and OpenStack APIs It provides an appliance based deployment console to simplify installation and maintenance and an embedded version of HP Operations Orchestration OO for automating administrative processes See CloudSystem Foundation components page 8 Figure 1 CloudSystem Foundation Networks OpenStack Virtual cond Ephemeral 3 machines volumes service offerings endpoints Identity Keystone Consumers users projects Browse request amp manage virtualized services Compute Nova e Simple self service portal images instances gt security groups Network services Storage services tt Itt Network Neutron provider and private tenant networks endpo
91. taller which is included in the HP CloudSystem 00 Studio 8 0 0 20 zip file See Preparing HP Operations Orchestration for CloudSystem Foundation page 47 CloudSystem Enterprise components 8 Welcome to HP CloudSystem e HP CloudSystem Enterprise expands on CloudSystem Foundation by integrating servers storage networking security and management to automate the lifecycle for hybrid service delivery Template architects use Enterprise to create infrastructure templates which are offered as services in the Marketplace Portal When a cloud user requests a service from the catalog Enterprise automatically provisions the servers storage and networking designed in the service Enterprise is installed from Foundation and uses the Foundation platform to conduct management tasks Enterprise includes the following components o The Enterprise appliance contains the core functionality of the Enterprise offering including HP Cloud Service Automation HP CSA the Marketplace Portal Topology Designer and Sequential Designer The Marketplace Portal displays offerings that can be purchased and applied to a cloud environment Enterprise includes two designers Topology Design and Sequential Design The Topology Designer is an easy to use solution for infrastructure provisioning designs Sequential Designer handles more complex application provisioning designs Designs from both designers are offered as services in the Marketplace Porta
92. tart setup assistant before using a text editor to change the advanced fields in the deployer conf file The setup assistant caches the contents of the deployer conf file in memory If you edit deployer conf outside of the setup assistant then the updates are not captured and applied during installation See Using the csstart CLI to install the Foundation base appliance page 64 When you run the csstart setup assistant you will be asked for a Glance disk size Make sure to size the disk appropriately See Formula to determine the storage requirements for the management hypervisor page 12 for sizing calculations The installation creates a Glance disk on the same datastore where the base appliance template is stored You must have sufficient space for the virtual appliance boot disks as well as the Glance disk or the installation process will not be able to complete Step 7 Do not move delete or rename images after you create the base appliance In order to speed up virtual machine boot times and save disk space csstart does not make a full copy of the image Changing the name or location of the image disrupts the operation of the shared copy encoded by csstart Return to procedure Prerequisites e CloudSystem Foundation KVM 8 0 0 20 is downloaded from the release site and images are unpacked on a Linux server e A CloudSystem directory is created on the management hypervisor Configuring the
93. terprise with root credentials gives you access to the Enterprise appliance e ifconfig shows all interfaces created for appliance e Ctr1 Q exits the Enterprise console 66 Command line interfaces B Configuring additional providers for CloudSystem Enterprise HP Cloud Service Automation HP CSA is the administrative portal for the Enterprise appliance You can configure HP CSA to allow Enterprise to connect to HP Matrix Operating Environment Matrix OE CloudSystem Foundation and HP Operations Orchestration OO Central When Enterprise is installed a erga aa is already configured This provider allows Enterprise to provision instances in Foundation Use the procedures in this appendix to create additional connections between HP CSA OO Central and Matrix OE e Configuring HP Operations Orchestration to integrate with HP CSA page 67 e Importing Operations Orchestration flows page 69 e Importing a service design page 70 e Configuring a Matrix OE resource provider page 71 You can find a list of related HP CSA documentation in the Enterprise Information Library Configuring HP Operations Orchestration to integrate with HP CSA OO Central is part of the CloudSystem Foundation base appliance You can configure OO Central to integrate with HP CSA The required configuration steps are listed below e Configuring an internal user page 67 e Deploying required content packs to HP CSA page 68 e Deploying the HP CSA conte
94. tes Why it matters Steps 3 5 esstart does not support spaces in bridge names Steps 3 5 Return to procedure e Red Hat Enterprise Linux 6 4 is installed on the management host e You are using a Linux server as your staging environment e The management hypervisor has connectivity to the HP 3PAR storage system This is required if you are using block storage for instances See HP 3PAR StoreServ Storage documents page 60 Procedure 8 Configuring the network infrastructure 1 Log in to the management hypervisor 2 Change the directory to etc sysconfig network scripts 3 Create the interface bond and bridge configuration files for the Data Center Management Network and the Cloud Management Network See KVM sample network configuration page 36 See Important network configuration information page 36 a Open the ifefg ethM file and add the following lines MASTER bondA SLAVE yes NM_CONTROLLED no Save the change and close the file b Open the ifefg ethN file and add the following lines MASTER bondA SLAVE yes NM_CONTROLLED no Save the change and close the file c Create a new bond configuration file using the name ifefg bondA This bond connects to bonda X for the Data Center Management Network and bond A for the Cloud Management Network The configuration file should contain the following lines DEVICE bondA BOOTPROTO none ONBOOT yes NM_CONTROLLED no USERCTL no BONDING OPTS mode 5
95. the installation 4 Complete the OO Studio upgrade procedure Upgrading to OO Studio 10 02 is required Procedure 13 Upgrading OO Studio 1 From the unzipped HP CloudSystem OO Studio 8 0 Mar 2014 zip file find oo studio upgrade zip 2 Unzip the oo studio upgrade zip file into the C Program Files Hewlett Packard HP Operations Orchestration folder A new folder named upgrade is created IMPORTANT Make sure to extract the zip file directly in the main installation folder and not a sub folder The apply upgrade bat script will only work if the upgrade folder is directly under the main installation folder 3 Open a Windows command line and perform the following directory changes cd HP Operations Orchestration cd upgrade cd 10 02 cd bin 4 Make sure OO Studio is closed You should not execute the following command with the program open 5 Run the command apply upgrade bat 6 Type Y to apply the upgrade 7 Wait for the UPGRADE SUCCESS message to verify that the upgrade completed without errors This can take several minutes 8 Optional If you want to edit the content packs included in OO Central import the content packs using the following steps e Open OO Studio e Under Dependencies click Import Content Pack e Select all the jar files extracted from the OOContentPacks zip and click Open e Verify that the content packs display in the Dependencies section Next steps e Refer to the OO Studi
96. tion is enabled FC SAN iSCSI Flat SAN NOTE REST API interface must be enabled on the HP 3PAR storage system Virtual appliance requirements CloudSystem virtual appliances The table below lists all CloudSystem virtual appliances along with compute memory and storage requirements Table 8 Hardware requirements Foundation base appliance 8vCPUs 32 GB 160 GB Thin Provisioned Glance image storage of 2 4 TB is provided by a 14 HP CloudSystem installation prerequisites Table 8 Hardware requirements continued Virtual appliance Cores RAM Storage separate mounted volume in a production environment SDN appliance Foundation 4vCPUs 8 GB 25 GB Thin Provisioned network node appliances 3 2vCPUs 3 4 GB 3 21 GB Thin Provisioned Foundation vCenter proxy appliance AvCPUs 16 GB 160 GB Thin Provisioned Foundation NOTE 1 vCenter proxy appliance is required for every VMware vCenter Server Enterprise appliance 8vCPUs 16 GB 160 GB Thin Provisioned Total of all Foundation and 30 vCPUs 15 cores 84 GB 568 GB Thin Provisioned Enterprise appliances Software requirements Refer to the table below for a list of supported software versions Software Version Location 3PAR Inform Inform OS 3 1 2 Contact your HP 3PAR support representative for MU2 additional information VMware vSphere ESXi 5 0 3 5 1 2 Available from http software hp
97. tion path Table 14 KVM management hypervisor installation path 4 Installation step Related information Create the management hypervisor Creating the management hypervisor page 33 Configure the network infrastructure Configuring the CloudSystem network infrastructure page 35 Choose the type of security checks to perform when running csstart Selecting hypervisor security level for CloudSystem installation page 40 Launch csstart and install the Foundation base appliance Configuring the Foundation base appliance on KVM page 41 Creating the management hypervisor Use the procedures in this section to create the KVM management hypervisor Preparing the hardware 1 If using a blade edit the server profile 2 On blades or standalone Dls perform the following two tasks a Define the management networks b Define the Cloud Data Trunk and identify the VLANs to include in the trunk Installing RHEL Obtain the installation media from http www redhat com Red Hat distributions and documentation are titled generically as RHEL6 instead of 6 3 6 4 and so on Check the documentation revision history or distribution version to be certain you are referencing the correct information Prerequisites e An iLO connection is established e The time is set in the BIOS e Smart arrays are disabled in the BIOS e The iLO virtual media or physical DVD is presented Using the RHEL installation media mount the DVD o
98. ts chapter to verify this before installation See HP CloudSystem installation prerequisites page 11 e f you are using ESX then VMware vCenter Server is installed and ready to connect to CloudSystem e f you plan to use block storage then an HP 3PAR storage system is configured and ready to connect to CloudSystem e You have a list of user names and passwords for VMware vCenter Server and HP 3PAR storage system e You have a set of IP addresses that you can assign to CloudSystem virtual appliances Next steps HP CloudSystem installation prerequisites page 11 Before you begin 3 HP CloudSystem installation prerequisites This chapter outlines the recommended and minimum hardware and software requirements the networking pre contiguration and the solution integration tools that must be in place before installing CloudSystem Hardware requirements page 1 2 Software requirements page 15 Networking requirements page 15 Browser requirements page 19 Tools requirements page 20 Understand the installation process A high level overview of the CloudSystem installation path is provided in the table below The Additional resources column contains links to information in this guide as well as information from other documentation sources Table 1 Installation process 4 Installation step Verity that the target environment satisfies the hardware software and networking prerequisites described in this guide
99. ure Orchestration User Guide Cloud bursting with HP CloudSystem Matrix infrastructure orchestration Third party documents CloudSystem incorporates OpenStack technology listed below and interoperates with other third party virtualization software Related information 59 OpenStack Havana OpenStack Documentation for Havana releases o Cloud Administrator Guide Virtual Machine Image Guide o API Quick Start o Admin User Guide End User Guide Command reference Keystone commands Glance commands Neutron commands Nova commands Cinder commands Red Hat Red Hat Enterprise Linux 6 documents VMware VMware vSphere documents HP 3PAR StoreServ Storage documents The latest versions of HP 3PAR StoreServ Storage manuals can be downloaded from the HP Support Center including the following documents HP 3PAR StoreServ Storage Concepts Guide HP 3PAR StoreServ Storage Troubleshooting Guide Finding documents on the HP Support Center web site 60 Follow these instructions to access all technical manuals hosted on the HP Support Center Ubon gt Go to the HP Support Center web site http www hp com go su Select the Drivers amp Software tab Type a product name in the Find by product box and click Go Select a specific product from the resulting list On the specific product support page locate the search fields at the top right of the web page The top search field will contain th
100. urity options when you run the csstart setup assistant e Enable full security checks When csstart runs it requests the SSH key from the hypervisor and then verifies the key against the ssh known_hosts file in the Users directory The Foundation base appliance continues to use this certificate to verify that it is communicating with the correct hypervisor before starting up any virtual appliances See csstart commands page 63 e Disable security checks for csstart but enable security when creating the remaining virtual appliances When csstart runs it injects the certificate into the Foundation base appliance but does not perform security checks When the additional virtual appliances are created by the Foundation base appliance that certificate is used to verify that the correct hypervisor is used See csstart commands page 63 e Disable security checks When csstart runs it does not verify the SSL certificate from the hypervisor The Foundation base appliance does not perform security checks when starting up the other virtual appliances See csstart commands page 63 Installing CloudSystem on a KVM hypervisor See also e Using the csstart CLI to install the Foundation base appliance page 64 e Troubleshoot installation issues page 52 Configuring the Foundation base appliance on KVM Read the following important notes before configuring the Foundation base appliance Table 16 Important CloudSystem configur
101. users to attach public IP addresses to their provisioned virtual machine instances network node appliances Provider Networks and or Private Networks at least 1 A Provider Network is a data center network routed through the existing data center infrastructure A Private Networkk is created from a pool of VLANs Both networks support instance communication Overview of network topology Cloud Data Trunk network node appliances Networks are organized into two trunks The Management trunk holds all infrastructure networks that connect the virtual appliances vCenter Server and the HP 3PAR storage system The Cloud Data Trunk holds the networks that connect provisioned virtual machines to the cloud Figure 4 Network trunks vCenter proxy appliance Cloud Mgmt Network Foundation base appliance Data Center Mgmt Network Network node Enterprise appliance appliance SDN appliance External Network Management Trunk vCenter Server Provider or Private Networks Cloud Data Trunk You can use the following interactive graphic to see how each network connects to the CloudSystem virtual appliances Click the play button B enable the graphic then click a network name to see which virtual appliances are supported by the network 16 HP CloudSystem installation prerequisites Figure 5 Interactive network diagram Click a network name to see it attach to the virtual appliances H
102. work for the cloud is typically a VLAN but could also be a physical network The Foundation base appliance runs a DHCP server for this network IMPORTANT The Cloud Management Network should be a dedicated private network for Cloud System Management use only Some of the contents transmitted between compute nodes and the cloud controller are unencrypted Network isolation should be used to prevent unwanted exposure to sensitive data e External Network This network is automatically connected to the network node appliances after Cloud Networking settings are saved during the CloudSystem Console first time setup Subnets must be defined in the CloudSystem Portal before using this network Virtual machines are not connected directly to this network Internal provider or private networks connect directly to a virtual machine then a virtual router is used to connect the internal and external networks A networking service routes outgoing traffic to the External Network When the External Network subnet assigns Floating IPs to virtual machines then the External Network can access them Cloud Data Trunk This network must be configured as a group of VLANs It hosts the VLANs that OpenStack networking makes available to users CloudSystem uses specific VLANs on this trunk as Private Networks Some VLANs may not be dedicated to CloudSystem All compute nodes in the cloud must be connected to this network The Cloud Data Trunk contains the fo
103. your environment Explanation of networks Example names for vSwitch CloudSystem virtual Management hypervisor or port group matches Network appliance vNICs figure below Data Center Management Foundation base appliance vNICO demgmt Network vCenter proxy appliance Enterprise appliance vCenter Server ESX compute nodes Cloud Management Network Foundation base appliance vNIC1 on Foundation base cloud mgmt appliance and vCenter proxy appliance vNICO on SDN and network node appliances SDN appliance network node appliances vCenter proxy appliance KVM compute nodes External Network network node appliances vNIC2 external Cloud Data Trunk network node appliances vNIC1 CloudTrunk all compute nodes IMPORTANT All of the networks described above must be distinct networks with the exception of the External Network You can use the same network for the External Network and the Data Center Management Network For a detailed explanation of the networks see Overview of network topology page 16 Installing CloudSystem on an ESX cluster The figure below shows a visual representation of the recommended configuration for networks Figure 10 ESX sample network configuration Foundation vCenter base appliance proxy appliance vCenter server vNICO ED CZB Management Vswitch Port group Management Trunk Data Center Management Network Cloud Manage
104. ystem properties for the HP CSA content pack 1 From the Content Workspace in OO Central select Configuration Items gt System Accounts 2 Click Edit 3 In the Name field type CSA_REST_URI 4 In the Override Value field type https ENTERPRISE APPLIANCE IPADDRESS OR_FQDN csa rest 5 Click Save Importing Operations Orchestration flows OO flows are imported to HP CSA with the Process Definition Tool This tool creates an HP CSA process definition for every imported OO flow The process definitions are associated with a process engine which corresponds to the OO system containing the imported flows HP CSA uses the flows to perform lifecycle actions and submit delegated approvals e Creating a database properties file page 69 e Creating an Operations Orchestration input file page 70 e Running the process definition tool page 70 9 TIP HP recommends that you generate sample database properties files and an input file Use the following steps to create these files Procedure 25 Generating sample database properties files and an input file 1 Navigate to the CSA_HOME Tool1s directory 2 Run the command sudo ci usr local hp csa openjre bin java jar ProcessDefinitionTool process defn tool jar g Procedure 26 Creating a database properties file 1 Navigate to the CSA_HOME Tool1s directory Importing Operations Orchestration flows 69 2 In the working directory make a copy of the PostgreSql sample datab

HP CloudSystem Foundation Installation Guide

Contents

Download Pdf Manuals

Related Search

Related Contents