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
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 CloudSystem.......................................................................5
Explanation of solution components............................................................................................6
Management hypervisors and integrated tools.........................................................................7
CloudSystem Foundation components.....................................................................................8
Importing a service design.......................................................................................................70
Configuring a Matrix OE resource provider................................................................................71
C Configuring a large-scale CloudSystem deployment......................................72
4Contents
1 Welcome to HP CloudSystem
Virtual
machines
Networks
and
endpoints
Ephemeral
volumes
Compute
services
Network
services
Storage
services
Servers
HP Converged Infrastructure
Consumers
• Browse, request & manage
virtualized services
• Simple self-service portal
Administrator
• Manage resources and access
• Provision VM Hosts
Identity (Keystone)
users, projects,...
Compute (Nova)
images, instances,
security groups, ...
Network (Neutron)
provider and private tenant
networks, endpoints, routing
Volumes (Cinder)
block storage for VMs
Resources
OpenStack
service offerings
Storage Networking
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 (IaaS)
provisioning and lifecycle management of compute, network and storage resources. You can
manage CloudSystem Foundation from an administrative console, self-service portal, CLIs,
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
•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).
5
Figure 2 CloudSystem Enterprise
Consumers
• Browse request & manage
virtualized services
Complex service
template
HP Servers
HP Storage
HP Networking
Resources
Compute
services
Network
services
Storage
services
Figure 2 CloudSystem Enterprise
Design, provision, and manage complex services with HP CloudSystem Enterprise
Administrator
• Manage catalog, subscriptions
and providers
Service Catalog
Public
cloud
services
Architects
• Design and publish
infrastructure and
applications services
• Topology and service
design tools
Explanation of solution components
The components of CloudSystem Foundation and CloudSystem Enterprise are explained below.
•Management hypervisors and integrated tools (page 7)
•CloudSystem Foundation components (page 8)
•CloudSystem Enterprise components (page 8)
•CloudSystem networks (page 9)
6Welcome to HP CloudSystem
Figure 3 CloudSystem architecture
CSA Admin UI
(w Designer)
CSA Marketplace
Portal
CSA
Cloud OS
Services
Foundation
Services
OpenStacks CLIs
Horizon UI
CS Foundation Base Appliance
keystone
neutron
SDN plug-in
nova
postgres
cinder
3Par Driver
glance
rabbitmq
CS Management Services
CS Admin UI
Foundation Services
OO Central
OO Central UI
SDN Appliance
SDN Controller
KVM Compute Node(s)
neutron L2 agent
nova compute
libvirtd
neutron L2 agent
nova compute
Foundation
Services
vCenter Proxy
Appliance(s)
vCenter(s)
vCNS(s)
ESX Clusters
ESX Hosts
Network Node
Appliances
LDAP
(e.g. AD)
CS Enterprise Appliance
OO Studio
CS Admin CLI
3Par array(s)
LDAP driver
neutron L2 and L3
agents
Management hypervisors and integrated tools
•Management hypervisors host the various virtual machine appliances that make up the
•VMware vCenter Server acts as a central administrator for ESX clusters that are connected on
•An HP 3PAR storage system provides a method of carving storage for boot and data disks.
•An FC SAN, ISCSI or Flat SAN connects the HP 3PAR storage system to compute nodes or ESX
CloudSystem solution. Both ESX and KVM hypervisors are supported.
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.
Block storage drivers are imported from the HP 3PAR storage system to the CloudSystem
Console.
clusters.
Explanation of solution components7
CloudSystem Foundation components
•CloudSystem Foundation is the IaaS 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:
◦The Foundation base appliance contains the core services and functionality of the
CloudSystem Console. The CloudSystem Portal, OpenStack services, OO Central and
supporting CLIs 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 the 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 GUI 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 installer,
which is included in the HP CloudSystem-OO-Studio-8.0.0.20 zip file.
See Preparing HP Operations Orchestration for CloudSystem Foundation (page 47).
CloudSystem Enterprise components
8Welcome to HP CloudSystem
•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:
◦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 Portal.
–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 components9
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.
•TOR switches for networking
•CLI commands for Windows and Linux
•VMware vCenter Server functionality, if using ESX hypervisors and compute nodes
•VMware distributed and standard vSwitches
•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
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.
•All hardware required to support a CloudSystem installation is installed and configured. You
can use the requirements chapter to verify this before installation. See HP CloudSystem
installation prerequisites (page 11).
•If you are using ESX, then VMware vCenter Server is installed and ready to connect to
CloudSystem.
•If you plan to use block storage, then an HP 3PAR storage system is configured and ready to
connect to CloudSystem.
•You have a list of user names and passwords for VMware vCenter Server and HP 3PAR storage
system.
•You have a set of IP addresses that you can assign to CloudSystem virtual appliances.
Next steps: HP CloudSystem installation prerequisites (page 11).
10Before you begin
3 HP CloudSystem installation prerequisites
This chapter outlines the recommended and minimum hardware and software requirements, the
networking pre-configuration, and the solution integration tools that must be in place before installing
CloudSystem.
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
Additional resourcesInstallation step
SeeVerify that the target environment satisfies the hardware,
software, and networking prerequisites described in this guide.
requirements for compute nodes and virtual machine instances.
This guide does not cover the specific steps required to
accomplish this.
• The 3PAR storage system server certificate must contain a
Fully Qualified Domain Name (FQDN) in the CN attribute
Subject field.
• For block storage volumes, use the OpenStack interfaces
that are dependent on block storage support.
• For ephemeral storage, define the storage in the flavor
definitions.
CloudSystem requirements. If using ESX, configure vCenter
Server.
Enter and save Cloud Networking settings in the CloudSystem
Console.
SeeConfigure the HP 3PAR storage system to support storage
Openstack Cinder documentation
HP 3PAR documentation
SeeSet up the management hypervisor solution (ESX or KVM) per
Installing CloudSystem on an ESX cluster
(page 26)
Installing CloudSystem on a KVM hypervisor
(page 33)
VMware vSphere Documentation at VMware
SeeUse csstart to deploy the Foundation base appliance.
Configuring the ESX management
environment (page 28)
Configuring the KVM management
environment (page 40)
See Setting up the CloudSystem Console for
the first time (page 44)
Optional: Install OO Studio, if you want to customize workflows.
Optional: Install CloudSystem Enterprise.
See Preparing HP Operations Orchestration
for CloudSystem Foundation (page 47)
See Installing CloudSystem Enterprise
(page 49)
Understand the installation process11
Table 1 Installation process (continued)
Additional resourcesInstallation step
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.
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.
See “Resource Configuration in CloudSystem
Foundation: Compute node creation” 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.0Administrator Guide at Enterprise
Information Library
StorageRAMCoresRequirements
See the formula below.128 GB16 coresRecommended
See the formula below.96 GB8 coresMinimum supported
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
•appliance storage: 600 GB
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
◦25 GB for the SDN appliance
•glance images/snapshots: varies
Table 3 Glance repository sizing guidelines
Linux images (4 GB
each)Glance repository
Windows images (16
GB each)
Snapshots (20 GB
each)
TOTAL
12HP CloudSystem installation prerequisites
520 GB151015Small
1.2 TB401520Medium
10.1 TB5003025Large
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
Where do I find it...Use this to...Additional resources
HP Insight Management Support
Matrix version 7.3.1
HP Support Center
HP Customized ESXi images for
management hypervisor
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.
•What flavor settings will the provisioned instances use?
•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.
Refer to the supported HP servers
tables. CloudSystem supports all
servers supported in the HP Matrix
Operating Environment, version 7.3.1.
• Table 26
• Table 28
• Table 29
• Table 30
The server must have a check in the
Matrix OE column.
drivers, firmware and software
Find customized ESXi images.
Supported versions are 5.0 Update 3,
5.1 Update 2, and 5.5.
http://www.hp.com/go/
insightmanagement/docs
http://www.hp.com/go/hpscVerify the compatibility of the servers,
568 GB (Thin Provisioned)84 GB30 vCPUs (15 cores)Total of all Foundation and
3PAR Inform
VMware vSphere
Security (vCNS)
Required on ESX compute nodes to
support security groups for provisioned
instances.
Networking requirements
Inform OS 3.1.2
MU2
ESXi 5.0.3, 5.1.2
and 5.5b (Custom
HP image)
For ESXi hosts, 5.5
is supported,
instead of 5.5b
10.02OO Studio
LocationVersionSoftware
Contact your HP 3PAR support representative for
additional information.
Available from http://software.hp.com. Select the
virtualization software link.
See Third-party documents (page 59)5.5VMware vCloud Networking and
See Third-party documents (page 59)6.4Red Hat Enterprise Linux
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
Before installing CloudSystem, plan for the following networks.
Software requirements15
Table 9 Network planning
3PAR
Foundation
base appliance
vCenter proxy
appliance
Cloud Mgmt
Network
Data Center
Mgmt Network
External
Network
Provider or
Private Networks
Cloud Data TrunkManagement Trunk
Figure 4 CloudSystem appliances and the network architecture
Enterprise
appliance
vCenter Server
Network node
appliance
SDN appliance
Connected to...PurposeNumberNetwork
1Data Center
Management
Network
1Cloud Management
Network
1External Networknetwork node appliances
Provider Networks
and/or Private
Networks
at
least 1
Overview of network topology
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 CloudData Trunk holds the networks that connect provisioned virtual machines to the cloud.
This network connects virtual appliances
to HP 3PAR, VMware vCenter Server,
VMware vCloud Networking and Security
(vCNS) and enclosures.
This network connects the Foundation
base appliance, vCenter proxy appliance,
network node appliances, SDN appliance network node appliances
and KVM compute nodes. This is a private
network.
This network allows cloud end users to
attach public IP addresses to their
provisioned virtual machine instances.
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.
Foundation base appliance
VMware proxy appliance
Enterprise appliance
VMware vCenter Server
Foundation base appliance
SDN appliance
VMware proxy appliance
KVM compute nodes
Cloud Data Trunk
network node appliances
Figure 4 Network trunks
You can use the following interactive graphic to see how each network connects to the CloudSystem
virtual appliances. Click the play buttonto enable the graphic, then click a network name to
see which virtual appliances are supported by the network.
16HP CloudSystem installation prerequisites
Figure 5 Interactive network diagram
Network definitions
Management Trunk
The Management trunk contains the following networks.
•Data Center Management Network: This network provides access to the CloudSystem Console,
which is the interface for the Foundation base appliance. REST APIs calls are made from this
Networking requirements17
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.
◦The Foundation base appliance uses this network to access the vCenter Server that is
managing the management hypervisor.
◦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.
◦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.
•Cloud Management Network: This private network 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.
•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 following production networks.
•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.
•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.
18HP CloudSystem installation prerequisites
The following figure shows a sample configuration with an ESX management host, networks and
Data Center Management
External
Provider
Private
Cloud Managment
Cloud mgmt
VMware vCenter server
CloudSystem Foundation
CloudSystem Enterprise
Enclosure
ESX compute nodes
ESX compute nodes
Onboard Administrator
Virtual Connect
External router
ESX cluster mgmt host
Network architecture for ESX management host with ESX compute nodes and 3PAR storage
Cloud Trunk
Figure 5
3PAR
Provider
Private
External
Cloud Management
Enclosure
KVM compute nodes
KVM compute nodes
CloudSystem Foundation
CloudSystem Enterprise
KVM mgmt host
Onboard Administrator
Virtual Connect
Data Center Management
Management Trunk
Cloud Trunk
Network architecture for KVM management host with KVM compute nodes and 3PAR storage
External router
Figure 6
3PAR
ESX compute nodes.
Figure 6 ESX management host with ESX compute nodes
The following figure shows a sample configuration with a KVM management host, networks and
KVM compute nodes.
Figure 7 KVM management host with KVM compute nodes
Browser requirements
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)
The following browsers are supported for the CloudSystem installation.
VersionProductVendor
9, 10Internet ExplorerMicrosoft
24Firefox Extended Support Release (ESR)Mozilla
Browser requirements19
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.
Next step: Prepare for the installation (page 21)
VersionProductVendor
Latest versionPersonal Edition
33ChromeGoogle
VersionProductCloudSystem Tool
Version 7, 2008 R2 (32-bit and 64-bit)Windowscsstart
RHEL 6.4Linux
Version 7, 2008 R2 (32-bit and 64-bit)WindowsCLI packages
CentOS 6.2, 6.3, 6.4, Ubuntu 12.04Linux
20HP 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.
•Installation kits (page 21)
•Preparing to install on ESX (page 23)
•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
HP CloudSystem Foundation ESX 8.0
Mar 2014
(contains ESX images for base, SDN
appliance, and network node
appliances)
(contains KVM images for base, SDN
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
Enterprise appliance)
HP CloudSystem Tools 8.0 Mar 2014
(contains the csstart installation script
and the CLI packages))
HP CloudSystem OO Studio 8.0 Mar
2014
(contains OO content packs and OO
Studio installation and upgrade)
x
xx
x
xxxx
xxxx
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 kits21
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 Z7550–01317.zip
•CS-Base-8.0.0.20.ova: Open Virtualization Format (OVF) package for the base appliance on
an ESX hypervisor.
•CS-Base-8.0.0.20.ova: OVF package for the SDN appliance on an ESX hypervisor.
•CS–NN–8.0.0.20.ova: OVF package for the network node appliance on an ESX hypervisor.
HP CloudSystem Foundation KVM 8.0 Mar 2014 Z7550–01318.zip
•CS-Base-8.0.0.20.qcow2: Disk image for the base appliance on a KVM hypervisor.
•CS-SDN-8.0.0.20.qcow2: Disk image for the SDN appliance on a KVM hypervisor.
•CS-NN-8.0.0.20.qcow2: Disk image for the network node appliance on a KVM hypervisor.
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 error.
HP CloudSystem Enterprise ESX 8.0 Mar 2014 Z7550-01323.zip
•CS-Enterprise-8.0.0.20.ova: OVF package for the Enterprise appliance on an ESX hypervisor.
HP CloudSystem Enterprise KVM 8.0 Mar 2014 Z7550-01324.zip
•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 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 Tools 8.0 Mar 2014 Z7550-01325.zip
•csstartgui-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.
•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.
•csstartgui-insecure.bat: Program used to deploy and configure the management appliances
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.
•csstart-linux.tar: Contains the command line to install CloudSystem from a Linux system.
•csstart-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.
•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.
•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.
22Prepare for the installation
Loading...
+ 50 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.