Implementing the HP Cloud Map for VMware vCloud Director

seedgemsbokΑποθήκευση

10 Δεκ 2013 (πριν από 3 χρόνια και 6 μήνες)

373 εμφανίσεις



Implementing the HP Cloud Map for
VMware vCloud Director




Technical
w
hite

paper



Table of contents

Executive summary

................................
................................
................................
...............................

2

Solution environment

................................
................................
................................
............................

3

Objectives

................................
................................
................................
................................
..........

4

HP Matrix OE IO templa
te for the VMware vCloud Director infrastructure deployment

................................
.

4

vCloud Management Cluster template design details

................................
................................
............

5

vCloud Resource Group template design details

................................
................................
..................

9

VMware vCloud Director Management Cluster

................................
................................
......................

10

Resource requirements

................................
................................
................................
....................

10

Deploying a vCloud Management Cluster with the HP Cloud Map

................................
.......................

12

Using the HP Cloud Map for vCloud Director template to create the vCloud Management Cluster

............

13

VMware vCloud Director Resource Group

................................
................................
............................

20

Resource requirements

................................
................................
................................
....................

20

Deploying the vCloud Resource Group with the HP Cloud Map

................................
...........................

21

Using the Cloud Map for vCloud Director template to create the vCloud Resource Group

.......................

21

Summary

................................
................................
................................
................................
..........

22

For more information

................................
................................
................................
..........................

23




2

Executive summary

More and more companies are looking to IT to improve resource utilization, increase automation and
flexibility, and reduce the time to roll out new applications. At the same time, there is also a demand
to reduce energy consumption, datacenter footprint, a
nd ultimately, the IT dollars spent.
Accomplishing this goal requires a shift in datacenter design methodology, away from the traditional
isolated islands of IT resources towards a more efficient and dynamic, converged infrastructure
datacenter design; a d
esign where pools of infrastructure resources can be allocated when business
teams request application services, enabling IT organizations to respond in a matter of hours and
days, rather than weeks and months.

With the HP BladeSystem Matrix (Matrix), com
panies can achieve this vision. Matrix provides an
integrated platform of server, storage, and network resources that can be pooled and allocated when
services are requested. One of the core technologies of Matrix is HP Matrix Operating Environment
(OE). W
ith Matrix OE, companies can change the way applications are deployed in the datacenter
and move towards a service
-
driven, standardized application deployment model. Application services
can be quickly provisioned and re
-
deployed as business demand require
s, based on pre
-
built
infrastructure orchestration templates that define the resource requirements of the service.

VMware vCloud Director enables enterprises to build secure, multi
-
tenant private clouds by pooling
infrastructure resources into virtual dat
acenters and exposing them to users through web
-
based portals
and programmatic interfaces as fully automated, catalog
-
based services. VMware vCloud Director
enables IT organizations to deliver resources to internal users as virtual datacenters. By logicall
y
pooling compute, storage, and networking capacity into virtual datacenters, IT organizations can
manage resources more efficiently with complete abstraction between consumption and delivery of IT
services.

HP Cloud Maps were developed to accelerate the c
reation of a service catalog by providing a guide
to automate infrastructure and application provisioning and deployment. The HP Cloud Map for
VMware vCloud Director includes two templates to automate the infrastructure provisioning and
resources needed to

support a VMware vCloud Director environment. This document describes the
process used to import the template into a target system and customize it for use. The document
describes some specific areas of the template that you will need to modify in order t
o successfully
import the template into the HP Matrix Operating Environment infrastructure orchestration designer
interface.

The template only provisions hardware and operating system resources. Installation of
database and application software is not perf
ormed by the templates.

One template, “vCloudDirectorInfrastrucure.xml” is specifically designed to provision the server,
storage, and network infrastructure resources necessary to support a VMware vCloud Director
deployment. A second template, “ESXivClou
dFarm.xml” is designed to provision the ESXi based
clusters that provide the compute resources for the Provider vDCs (Virtual Data Centers) in the
VMware vCloud Director environment. This document discusses the details of the templates and
describes some s
pecific areas of the templates that you will need to modify in order to successfully
import and deploy the templates in your own environment.

The templates described in this white paper are based on the HP Matrix OE 6.2 software release.

Target audience:
T
his document is intended for IT managers, datacenter architects, and system
administrators looking for an HP infrastructure orchestration template to deploy a reference VMware
vCloud Director environment with Matrix. Knowledge of Matrix and the underlying
components will
be essential when reading this white paper. Please see the “For more information” section of this
white paper for links to additional information on these topics.


3

Note

HP Matrix Operating Environment was previously referred to as HP Insigh
t
Dynamics.

HP Matrix OE infrastructure orchestration (IO) was previously referred to as
HP Insight Orchestration.

The HP Matrix Operating Environment uses a subset of Operations
Orchestration capability. HP Cloud Maps leverage workflows that are
authored

using this subset of Operations Orchestration.

HP Insight Control server deployment was previously referred to HP Rapid
Deployment Pack (RDP).

Solution environment

The templates were created using HP Insight Dynamics 6.2 with HP BL460c and BL490c server
blades
including QLogic QMH2462 4Gb FC HBAs or Emulex LPe1105
-
hp 4Gb FC HBAs in an HP
BladeSystem c7000 enclosure with two HP Virtual Connect Flex
-
10 Ethernet modules and two Virtual
Connect 8Gb 24
-
Port Fibre Channel (FC) modules. The server where Insight
Dynamics is installed is
known as the Central Management Server (CMS). To download HP BladeSystem firmware, go to
http://www.hp.com/go/matrixcompatibility
.

Table 1 lists the firmware and software vers
ions used during development.

Table 1.
Firmware and software levels

Component

Version

Servers

HP BL460c G6

HP BL490c G6

Application

VMware vCloud Director

HP Onboard Administrator

3.20

HP Virtual Connect Manager

3.15

HP Integrated Lights
-
Out

2.01
(iLO 2)

QLogic Fibre Channel Adapter

QMH2462

ROM BIOS 2.15; Firmware: 5.03.02

Operating System

Red Hat Enterprise Linux 5,

Windows Server 2008 Enterprise R2

Hypervisor

VMware ESXi 4.1

HP Insight Dynamics

6.2

Additional Software

VMware vCenter Server
4.1

Oracle Database 11g Release 2



4

Objectives

The objective of this white paper is to provide an example reference point for you to build from when
designing templates for a VMware vCloud Director environment. The templates described in this
document are
designed to provision the server, storage, and network infrastructure resources
necessary to support the example VMware vCloud Director environment. The intention is for these
templates to be taken and modified or adjusted to a specific Matrix environment.

If the features and
functionality requirements for your VMware vCloud Director environment are different, the templates
need to be redesigned appropriately.

To utilize the templates, download the “HP Cloud Map for VMware vCloud Director” .zip file from th
e
HP Cloud Map site,
http://www.hp.com/go/cloudmaps
.

HP Matrix OE IO template for the VMware vCloud Director
infrastructure deployment

This template is specifically designed to provision the servers, storage, a
nd network infrastructure
resources necessary to support the VMware vCloud Director infrastructure. This configuration supports
a core set of the functionality that VMware vCloud Director provides. The example discussed herein,
and the accompanying templat
e, reflect an example VMware vCloud Director infrastructure
deployment based on the “
vCloud Director Installation and Configuration Guide
”.

This document shows a general case of deploying the HP C
loud Map for VMware vCloud Director.
The procedure covers both physical infrastructure assets and virtual components and will move
between these stacks in a per
-
resource fashion


through networking, storage and software. The
following steps will need to b
e completed in order to successfully publish the HP Cloud Map for
VMware vCloud Director template:



Confirm the physical network resources are in place in the Virtual Connect Manager and provide
an environment
-
specific definition of network connectivity



Modify the virtual network configuration of the vCloud components in the Cloud Map template to
correlate to the environment
-
specific networks defined in the previous step



Validate physical storage resources against the requirements of the vCloud environmen
t described
in the Cloud Map template



Correlate the environment
-
specific source locations for the OS installations and templates with each
of the physical and virtual servers in the template

This document, much like the VMware vCloud Reference Architecture

Kit published by VMware,
separates the discussion between the management components of the vCloud Director environment
from the cloud resources that will host end
-
user workloads. The two sets of resources are separated to
simplify the management and enfor
cement of different availability domains as well as to isolate the
management environment from the end
-
user environments. Specifically, we define the two sets of
resources as:



vCloud Management Cluster



this is the set of servers and virtual machines that

provide the
management and operational services for the vCloud environment; this includes the vCenter Server,
the vCloud Director server, vShield Manager virtual appliance(s), and the Oracle database



vCloud Resource Groups


this is the set of servers tha
t provide the capacity to the cloud; these
resources are grouped into vSphere clusters and pooled into vCloud virtual datacenters to provide
compute, storage and network resources to cloud tenants


5

vCloud Management Cluster template design details

This exam
ple template focuses on designing the requirements to support a small VMware vCloud
Director environment with the following features and functionality:



Multi
-
tenant



Virtual Data Centers (vDC)



Self
-
service web portal



vShield security

Table 2 below provides
the details of the design requirements to support this VMware vCloud Director
configuration.


Note

For detailed information on the architecture and sizing of a VMware
vCloud Director environment, please download and review the VMware
white paper “
Architecting a vCloud

. For specific information regarding
the software and configuration requirements in a VMware vCloud Director
environment, see “
vCloud Director Installation and Configuration
Guide

.


Table 2.

VMware vCloud Director Management Cluster resource requirements

Server
Role

# of
Servers

Physical
Server

or VM

Core

count

Memory
(GB)

Networks

Storage (per server)

Oracle DB


1

Physical

4

16 GB

2 NICs

Management NIC

Management NIC

2 LUNs

48 GB LUN (OS/Oracle
binaries)

50 GB LUN (DB data)

vCenter
Server

1

Physical

2

8 GB

1 NIC

Management NIC

1 LUN

60 GB LUN (OS/vCenter
Server binaries)

vCloud
Director

1

Virtual

4

8 GB

2 NICs

Production NIC

Management NIC

1 LUN

20 GB LUN (OS/vCloud
Director binaries)

vShield
Manager

1

Virtual

1

4 GB

1 NIC

Management NIC


1 LUN

1 GB LUN (OS/vShield
binaries)


The unmodified Cloud Map for VMware vCloud Director uses seven physical servers to provide the
necessary features and services. One physical server is used for the Oracle database; one physical
server is used for the vCenter Server; one server is used as a
n ESXi host for the vCloud Management
Cluster, consisting of vCloud Director and vShield Manager. The other four physical hosts are used for
the vCloud Resource Group. The Cloud Map defaults can be modified to fit a variety of deployment
configurations; fo
r example, if the vCenter Server were to be deployed in a virtual machine, rather
than a physical server. The vShield Manager, however, is distributed as a virtual appliance and must
be deployed as a virtual machine.


6

The management network is a common net
work across all the servers in the configuration. In the
template this network is named RedNet. The front
-
end production network is named AquaNet in the
template.

This solution is designed to create a simple test environment. Users who want to create a mo
re
complex environment can modify and extend the Cloud Map to address significantly more complex
environments than is presented in the default. For example, most environments will have more than
one host in the vCloud Resource Group; many will contain more

than one vCloud Director Cell or
vCenter Server; others may want to configure additional redundant network connections. This
example is meant to be a basic deployment and thus only single servers are configured in the
template.

For the Oracle 11g R2 data
base server a minimum of 4 processor cores, 16GB of RAM, and 2 NICs
is recommended. The 2 NICs will be used to create a redundant connection to the management
network. The Oracle server has two external LUNs assigned. A 48 GB LUN is used for OS and
Oracle
binaries, while a 50 GB LUN is used for database files.

The vCenter server only requires 2 processor cores, 8 GB of memory, and a single NIC to connect to
the management network. The vCenter Server has a single 60 GB external LUN for the OS boot and
vCent
er binary files.

The vCloud Director server requires 4 processor cores, 8GB of memory, and 2 NICs; one for the
management network and one for the front
-
end production network. This server is deployed as a
virtual machine and will use approximately 20GB of

virtual storage capacity for the OS and vCloud
Director binaries.

The vShield Manager, distributed as a virtual appliance, requires one vCPU, 4GB of memory and one
NIC connected to the management network. The vShield Manager is manually deployed from an
HP
VMM (Virtual Machine Manager) template; therefore, it does not appear in the infrastructure
orchestration service template. One vShield Manager server is deployed for each vCenter Server that
supports the vCloud Resource Groups.

It is important to also

discuss the assumed state of the infrastructure before the Cloud Map is
published and an isolation that is implied in this deployment template. Since some elements of the
Management Cluster will be running in a virtual machine, there must be an existing s
et of virtualized
infrastructure to support these workloads. In this case, both a vCenter Server host and at least one
ESXi Server host are assumed. The Cloud Map will deploy a second vCenter Server host within the
vCloud Management Cluster. While this is
not an absolute requirement, and the existing vCenter
Server could be used, it is currently recommended to deploy the second vCenter host to provide an
isolated vCenter environment that will be managed, primarily, from vCloud Director. While the first
vCen
ter Server is connected to and managed by the Matrix components, the second, vCloud
-
focused
vCenter Server should not be. Presently, Matrix does not inherently understand the vCloud
-
specific
constructs of multi
-
tenancy, virtual datacenters and organization
s. As a result, there are conditions that
might arise that may be justified and acceptable within these contexts that Matrix may misinterpret.
HP and VMware continue to investigate the delivery of an integrated vCloud management
experience.

With that in mi
nd, though, Matrix can greatly simplify and accelerate the initial deployment of a
vCloud Director environment. This document and the associated Cloud Map are evidence to that fact
and provide the foundation for an extremely extensible deployment framework

that can be modified
to address the requirements of even the most complex vCloud environments.

To design the environment, the system administrator or design architect can use the information from
Table 2 above to build or import the vCloud Director infra
structure orchestration service template in
the designer tool. Figure 1 shows the template that was created to provision the resources for this
example vCloud Director deployment.


7


Figure 1.

vCloud Director Infrastructure Matrix OE template





Note

T
he
actual graphical layout of the template is not important and this layout
was only selected for ease of viewing.

The yellow server icons in the template represent the physical server resources for the Oracle
database and vCenter servers. The virtual machin
e for the vCloud Director server is represented by
the purple server icon in the template. The network resources are represented by the blue circle icons
with the expanding lines and are located in the middle of the template and connect to the various
serv
er resources accordingly. The physical storage resources (yellow storage icons) represent the OS
boot LUN requirements for both of the physical server roles, and virtual storage resources (the purple
storage icons) represent the OS boot LUN requirement for

virtual server roles. There is an additional
physical storage resource connected to the Oracle server group for database storage.

To configure the specific attributes for each of these resources, simply right
-
click on the resource and
select the edit res
ource configuration option to open the configuration window. An example of the
physical server resource configuration window for the Oracle 11g R2 Single Instance DB server for
this template, is displayed in Figure 2.


8


Figure 2.

Physical server resource co
nfiguration screen



The figure highlights key resource requirements to support this server role (processors, speed, memory,
etc.).

Once all the resource attributes have been configured appropriately, a green check will appear next
to “Validation Stat
us” in the designer as shown in Figure 1. At this point, the service template can be
published and the template will appear in the self
-
service portal for users to select and provision.

Note:

One of the key aspects of HP Insight Orchestration (IO) templat
es is the
ability to assign cost values to the resources that are consumed. The “Cost
Per Server” attribute shown in Figure 2 is an attribute associated with each
infrastructure orchestration resource. Here, costs can be defined for each
consumed resource
and a total solution cost computed for chargeback
purposes.


9

vCloud Resource Group template design details

This example template is designed to provide the cloud resources to support a Provider VDC in a
VMware vCloud Director environment.

Table 3 below
provides the details of the design requirements to support this VMware vCloud Director
configuration.


Table 3.

VMware vCloud Resource Group server role resource requirements

Server
Role

# of
Servers

Physical
Server

or VM

Core

count

Memory
(GB)

Networks

S
torage

ESXiFarm


4

Physical

4

8 GB

8 NICs

Management NIC

Management NIC

Production NIC

Production NIC

vMotion NIC

vMotion NIC

VLAN NIC

VLAN NIC

1 LUN per server

10 GB LUN (Hypervisor)

1 LUN shared

200 GB LUN (VMFS)



For the vCloud Resource Group deployment, 4 servers are used in the template defaults. Just as with
the Management Cluster, it is necessary to confirm that the network connectivity, defined within Virtual
Connect, will be sufficient for the requirements of

the vCloud Resource Group hosts. In terms of the
template defaults, the management network (RedNet) is a common network across all the servers in
both VMware vCloud Director templates. The production network AquaNet is also used in both
templates describe
d in this document. The ESXiFarm template also makes use of a vMotion network,
and a VLAN network.

For each ESXiFarm server, a minimum of 4 processor cores, 8GB of RAM, and 8 NICs are required.
The 8 NICs will be used to create redundant connections to th
e management network, the production
network, the vMotion network, and the VLAN network. Each ESXiFarm server has two external LUNs
assigned. A 10GB LUN is used for hypervisor files, while one or more shared 200GB LUNs are used
as VMFS datastores.

The sys
tem administrator or design architect can use this information from Table 3 above to build or
import the VMware VCloud Resource Group IO service template in the designer tool. Figure 3 shows
the template that was created to provision the resources


for th
is example, vCloud Resource Group
deployment.


10


Figure 3.

ESXivCloudFarm HP IO template



Configure the specific attributes for each of the resources by right
-
clicking on the resource and
selecting the edit resource configuration option to open the config
uration window. Once all the
resource attributes have been configured appropriately, a green check will appear next to “Validation
Status” in the designer as shown in Figure 3.

VMware vCloud Director Management C
luster

Resource requirements

The following

four sections outline the specific resource requirements that are necessary in the
environment to successfully provision the components

of the VMware vCloud Director Management
C
luster infrastructure. Remember, in the default Cloud Map, there are two phys
ical hosts and two
virtual mac
hines in the vCloud Management C
luster.

Physical server pool requirements

Table 4 defines the physical server resources that must exist to satisfy the requirements for this
template.

Table 4.
Server pool resource requirement
s

Server name

Minimum CPU
frequency

Minimum CPU cores

Minimum
memory

HP server model

Oracle DB

2.0 GHz

4 cores

16GB

HP ProLiant BL460c G6

vCenter Server

2.0 GHz

2 cores

8GB

HP ProLiant BL460c G6


The “HP server model” column in the table provides a representative HP ProLiant server blade that
would be suitable to meet the resource requirements specified in the template.


11

Virtual server pool requirements

The Cloud Map default assumes that the vCloud

Service is going to be installed in an environment
that already contains a VMware vCenter server and at least one ESXi host to support the vCloud
Management Cluster elements that are virtualized. Table 5 defines the virtual server resources that
must be a
vailable on the existing VMware ESXi hosts to satisfy the requirements for this template.

Table 5.
Virtual server resource requirements

Server name

vCPUs

Virtual host
memory

Virtual Storage

vCloudDirector

4 cores

8GB

20GB

vShieldManager

2 cores

4GB

11GB


Storage pool requirements

Table 6 lists the necessary LUNs and logical storage pool entry (SPE) information for the LUNs
requested by this template.

Table 6.
Storage pool resource requirements

LUN description

Total #
LUNs

LUN size

Shared
storage
LUN

Redundant

paths to
storage

Logical SPE
properties field

vCenterBoot

1

60GB

No

Yes

RAID1, boot

OracleBoot

1

48GB

No

Yes

RAID1, boot

OracleData

1

50GB

No

Yes

RAID1

SPE = storage pool entry

Network pool requirements

The VMware vCloud Director configuration defined by this template requires the following networks
described in Table 7 to be configured in HP Virtual Connect (VC) and as virtual machine port groups
on the ESXi hosts, as show in Figure 4.

Table 7.

vCloud D
irector Management Cluster network resource requirements

Network name

Name in service template

Notes

Production network

AquaNet

Production network for incoming
communications to the front
-
end vCloud
Cell servers from the load balancer.

Management network

RedNet

The network on which all servers
communicate. This also doubles as the
deployment network used to install the
OS, using HP Insight Control server
deployment, and for other management
tasks.



12


Figure 4.

ESXi host network configuration screen



Note

Network names are case sensitive. The network names must match exactly
in HP Virtual Connect and the virtual machine port groups.

Deploying a vCloud Management C
luster with the HP Cloud Map

To utilize this template, download the “HP Cloud Map for VMware vCloud Director” from the HP
Cloud Map site at
www.hp.com/go/cloudmaps
. The “Templates, workflows and scripts” file contains
a template that can be imported into a Matrix environment. The template file has the appropriate
resource attributes already configured based on the vCloud Director infrastructure requirements
outlined

in Table 2. It is also necessary to download and review the Oracle 11g R2 Single Instance
Database Cloud Map, as the VMware vCloud Director Infrastructure template is based on it. Many of
the topics covered in the white papers “
HP Cloud Map for Oracle 11g R2 Single Instance Database:
Importing the template
” and “
Inside the
HP Cloud Map for Oracle 11g R2 Single Instance Database

are not repeated in this document. It is required to successfully deploy the Oracle 11g R2 Single
Instance Database template before attempting to deploy the entire VMware vCloud Director
Infrastructu
re template.


13

When importing the “vCloudDirectorInfrastructure.xml” file into the Insight Orchestration Designer,
there will be a reconciliation pop
-
up window indicating that the template references software that is
not found. This is because the HP Insigh
t Control server deployment folders, which are referenced in
the server provisioning and logical server definitions, are unique to each environment and may not
match the paths defined in the Cloud Map template. There are also additional error warnings
high
lighting issues with the network resources as indicated by the red boxes on the resource
components in the imported template. Like the software references, the network resources will also be
unique to each individual environment and must be modified before

the template can be successfully
published in a new environment.

There are resources that will be specifically highlighted with error, and these resources must be
modified before the template can be published successfully. This document will walk through

the
issues that will be required to publish the HP Cloud Map for vCloud Director template. There are
additional areas, however, that may not be highlighted by errors and still need to be examined on a
customer
-
by
-
customer basis, including the storage LUN
resource attributes (described in more detail
below) and any HP Operations Orchestration (OO) workflows. Follow the instructions in the white
paper “
Inside the HP
Cloud Map for Oracle 11g R2 Single Instance Database
” for information on
importing, attaching and troubleshooting OO workflows.

Using the HP Cloud Map for vCloud Director template to create the
vCloud Management Cluster

Network resource template modificati
ons

In order to prepare the Cloud Map for a particular environment, the “Network” resource component
of the Cloud Map needs to be modified to match the definitions of local networks within the
deployment environment. In a Matrix environment, Virtual Connec
t (VC) provides a comprehensive
catalog of the available networks and when the VC domain is configured, the appropriate physical
networks are defined. HP Matrix OE communicates with the VC Manager to catalog and present the
available network resources for
the environment. Further attributes are then defined within the HP IO
service console to make these networks available as a selectable network resource when defining the
infrastructure orchestration template.

Obviously, these network names will be unique
to each environment and thus the placeholder names


RedNet and AquaNet


need to be replaced with appropriately configured local networks. To
modify the network information, right
-
click on the “Network” resource component and select the
appropriate networ
k connections that are to be used as shown in Figure 5. Networks that are defined
in HP Virtual Connect and on ESXi hosts will be reported in the “Source” column as “Virtual and
Physical”. In the unmodified template, both the AquaNet and the RedNet network
s are defined as
“Virtual and Physical.” RedNet is also defined as a boot network with a deployment server. These
networks were used to create the default template and should be replaced, here, with networks that
exist in the deployment environment. Later
in this document, logical server templates will have to be
modified, as well, to update the network definitions to match the networks available in the deployment
environment.

All environments should have a boot network, with an attached deployment server,

a “Virtual and
Physical” network to provide connectivity for the vCloud Management Cluster


that is, between the
vCloud Director, vCenter Server, vShield Manager and Oracle management components


and some
number of “Virtual and Physical” networks to pro
vide connectivity for the vCloud Resource Groups.


14


Figure 5.

Network resource configuration screen



Once the networks have been reconfigured with the correct network names, click “OK” and return to
the designer tool. Then, right
-
click on the server reso
urces to open the server configuration window.
As shown in Figure 6, this window contains a “Networks” tab which will also need to be modified
appropriately to set the network assignment type (DHCP, Static, or Automatic) for the specific
networks utilized
in your environment.

Some workflows, such as those used to configure the Oracle 11g R2 Database, require the server
group to specify a Static or Automatic network assignment type. These workflows will fail if DHCP is
specified, as the resulting Request.xm
l will not contain the IP addresses the workflow requires.


15


Figure 6.

Network properties of the physical server resource




16

Logical Storage Pool Entry template modifications

When a storage resource is added and defined within the service template of Insigh
t Orchestration,
there are several attributes that must be configured beyond setting the required LUN size and RAID
level. Among other attributes, this task includes specifying whether or not the “Disk is bootable”,
whether or not there are “Redundant SAN
paths to disk”, and specifying any “Tags” values as shown
in Figure 7.


Figure 7.

Physical storage resource configuration screen



These values define the criteria that are used to select an available logical server storage pool entry
(SPE) during the provisioning process. If there are no SPEs that meet the criteria specified in the
storage resource, the provisioning task will pause a
nd request that the appropriate storage be
manually configured.

For Cloud Map elements that will be deployed on physical systems, it is required to configure one
storage pool entry as bootable. Indicate that a storage resource (in other words, an SPE) is
to be used
as a boot LUN, by ensuring that the “Disk is bootable” check box is selected when editing the
resource attributes as shown in Figure 7.


17

Other than defining the physical storage pool entries and ensuring that these SPEs can meet the
requirements

listed in Table 6 and Table 9 of this document, no further customization of the Cloud
Map template is required. This is because the requirements for each of the elements remain consistent
and the attributes in the template are universally applicable.

Whil
e it is not an explicit error that would be generated in the template, in order to fully automate the
provisioning of the boot LUN, the administrator should coordinate the values in the “RAID Level” and
“Tags” fields with the properties fields on the logic
al SPEs. The “Tags” field can be used by the
template designer to specify different classes of storage, RAID level, array names, etc. This
information can then be provided to the administrator responsible for managing the storage pool
resources to configur
e the SPEs as needed.

Note

The specific values needed to configure in the SPEs for each of the LUNs
required by the templates are outlined in Table 6 and 9 in the “Storage
pool requirements” sections of this white paper.

Operating system deployment templa
te modifications

In an HP Matrix Operating Environment, it is helpful to understand the different ways in which the
boot image is deployed. For physical systems, Matrix relies on a coordinated effort between Insight
Orchestration to manage the mapping of a

remote volume to a server and HP Insight Control server
deployment to provide a Pre
-
boot Execution Environment (PXE) to install the operating system into the
remote, bootable volume. For virtual machines, Matrix OE can leverage a vSphere template to creat
e
a functional, bootable instance from a pre
-
existing template.

The Cloud Map template indicates, for each of the systems


both virtual and physical


the source
locations for the software components that will be used to assemble the environment. However,

as
with many other attributes of the deployment, the Insight Control server deployment job folders and
virtual machine template locations will be unique for each environment. When an HP Matrix OE IO
template is imported, the specific Insight Control serve
r deployment provisioning job folder needs to
be selected for all server resources that will be deployed via Insight Control server deployment.

When using Insight Control server deployment to deploy the operating system, specify which Insight
Control serv
er deployment job folder contains the correct OS by opening the server group properties
configuration window and, on the “Software” tab, select the appropriate Insight Control server
deployment folder. Figure 8 shows the “Software” tab of the vCenter serve
r group. Other deployment
jobs for other physical systems, such as ESXi and Oracle, can be seen, as well in Figure 8.


18


Figure 8.

Server group software configuration screen



For virtual server resources that will be deployed using vSphere templates, a sim
ilar step is required.
In this case, the location of the virtual machine templates available in the Matrix environment must be
specified. When selecting the specific OS and software versions to deploy for each server resource in
the vCloud Director environ
ment, consult the “
vCloud Director Installation and Configuration Guide
”.

vShield Manager deployment

Because the vShield Manager appliance has two virtual disks defined, it must be converted to a
v
irtual machine template before it can be deployed in an HP VMM template in HP Matrix OE. This is
a two
-
step process of importing the virtual appliance into vCenter Server to create a virtual machine,
and then converting the virtual machine to a virtual mac
hine template. While it seems redundant, this
step is required because the integrated functionality between vSphere and Matrix do not yet natively
understand the concept of deploying a multi
-
disk Open Virtualization Format (OVF) template, but the
integrati
on completely comprehends a virtual machine template.

Use the vSphere Client to connect to the vCenter server that manages vSphere resources in the Matrix
environment, then select File


Deploy OVF Template. Follow the wizard to import the vShield
Manager

appliance and, when asked, make sure to specify the environment
-
specific management
network that provides connectivity to both vCenter Server and vCloud Director as the Destination
Network, as shown in Figure 9. Once the virtual machine has been imported,

it can be converted into
a virtual machine template. The vShield Manager template can be deployed in HP Matrix OE by
selecting Deploy


Virtual Machine


Templates


Deploy Virtual Machine Template.


19


Figure 9
.

Network mapping when importing the vShield Manager virtual appliance



Deploying the vCloud Director Management Cluster

One thing that’s important to note is that, even after modifying the necessary service template
attributes and publishing the template, the template cannot be provisioned unless the compatible and
necessary resources exist in the underlying Matrix environm
ent. When a user attempts to create a
service based on this template, Matrix first runs a validation algorithm that checks to see that all the
necessary resources (servers, storage, and networks) specified in the Cloud Map for vCloud Director
are available
. If the resources are available, they are reserved, and the provisioning process
commences. If the resources are not available, then the allocation halts, the service creation fails and
Insight Orchestration presents an indication of which resource caused

the failure.

Remember, if the Cloud Map for vCloud Director is being extended beyond the scope of this
document to address an environment that has more than one vCenter Server, a vShield Manager
virtual machine must be manually deployed for each vCenter
Server.


20

At this point, the Cloud Map for vCloud Director template should be ready to deploy. All required
modifications to the template should be complete and the physical environment should be prepared
and configured to deploy the vCloud Director environ
ment. Keep in mind that this HP Cloud Map for
VMware vCloud Director seeks only to install the components and provide for infrastructure
connectivity to support the environment. The vCloud Director service is not, yet, configured or fully
functioning. Foll
ow the steps outlined in the “
vCloud Director Installation and Configuration Guide
” in
order to complete the vCloud Director infrastructure deployment. The vCloud Director server still needs
to be
configured to connect to the Oracle instance, the vShield Manager, and the vCenter hosts. The
ESXi hosts must be brought into vCenter and assembled as a cluster. That cluster must be associated
with a Provider vDC; organizations must be defined, etc. In ef
fect, the Cloud Map for vCloud Director
accelerates the provisioning of the vCloud Director environment without completing the service
-
level
configuration of the VMware components.

VMware vCloud Director Resource G
roup

Resource requirements

The following t
hree sections outline the specific resource requirements that are necessary in the Matrix
environment to successfully provision the vCloud Farm service.

Server pool requirements

Table 8 defines the physical server resource requirements that must exist to s
atisfy the requirements for
the ESXivCloudFarm template.

Table 8.
vCloud Resource Group server pool resource requirements

Server name

Minimum CPU
frequency

Minimum CPU cores

Minimum
memory

Architecture

ESXivCloudFarm

2.0 GHz

4 cores

8 GB

x86 64
-
bit


Storage pool requirements

Table 9 lists the necessary LUNs and logical storage pool entry information for the LUNs specified by
this template.

Table 9.
VCloud Resource Group template storage pool resource requirements

LUN description

Total #
LUNs

LUN siz
e

Disk is
bootable

Shared
storage
LUN

Redundant

paths to
storage

Logical SPE
properties field

ESXiBoot

1 per
ESXi
host

10 GB

Yes

No

Yes

RAID1, boot

VMFS

1 or
more

200 GB

No

Yes

Yes

RAID1



21

Network pool requirements

The VMware vCloud Director
configuration defined by this template requires the following networks
described in Table 10 to be configured in HP Virtual Connect (VC).

Table 10.
vCloud Resource Group template network resource requirements

Network name

Name in service template

Notes

Pr
oduction network

AquaNet

Production network for incoming communications to
the ESXi host servers from the load balancer.

Management network

RedNet

The network on which all servers communicate. This
also doubles as the deployment network used to install
the OS, using HP Insight Control server deployment,
and for other management tasks.

vMotion

vmotion

The network used by ESXi host for live migration
s of
virtual machines

VLANTrunk

VLAN100

The network used to trunk VLANs to the ESXi hosts


Deploying the vCloud Resource G
roup with the HP Cloud Map

This template is specifically designed to provision the servers, storage, and network infrastructure
reso
urces necessary to support the ESXi host cluster that will back a Provider vDC in a VMware
vCloud environment.

Using the Cloud Map for vCloud Director

template to create the vCloud
Resource G
roup

To utilize this template, download the “HP Cloud Map for VMware vCloud Director from the HP Cloud
Map site at
www.hp.com/go/cloudmaps
. The “Templates, workflows and scripts” file contains the
vCloud Resource Gro
up template that can be imported into a Matrix environment. The template file
has the appropriate resource attributes already configured based on the vCloud Director infrastructure
requirements outlined in Tables 8 and 9.

When importing the “ESXivCloudFar
m.xml” file into the designer, there will be a reconciliation pop
-
up
window indicating that the template has errors. Software and network resources must be modified
before the template can be successfully published in a new environment. There are also two
additional areas that need to be examined on a configuration
-
specific basis, including the storage
LUN resource attributes and any HP Operations Orchestration (OO) workflows.

The template cannot be provisioned unless the necessary resources exist in your
Matrix environment.

Network resource template modifications

One attribute of the template that requires modification is the “Network” resource component. To
modify the network information, right
-
click on the “Network” resource component and select the
app
ropriate network connections that are to be used.

Once the networks have been reconfigured with the correct network names, right
-
click on the server
resources in the designer tool and open the server configuration window. This window contains a
“Networks”

tab, which will also need to be modified appropriately to set the network assignment type
(DHCP, Static, or Automatic) for the specific networks utilized in your environment. Some workflows,
such as those used to configure the ESXi hosts, require the serv
er group to specify a Static or
Automatic network assignment type. These workflows will fail if DHCP is specified, as the resulting

22

Request.xml will not contain an IP address on the management network (RedNet) as the workflow
requires.

Logical storage poo
l entry template modifications

To indicate that a storage resource is to be used as a boot LUN, the “Disk is bootable” check box
should be selected when editing the ESXiBoot storage resource attributes.

To indicate that a storage resource is to be used as

shared storage, the “Disk is shared across
servers” check box should be selected when editing the VMFS storage resource attributes.

The administrator should coordinate the values specified in the vCloud Resource Group service
template with the properties
fields on the logical SPEs. This information can then be provided to the
administrator responsible for managing the storage pool resources to configure the SPEs as needed.

Deploying the vCloud Resource G
roup

The “Software” tab in the server group properties configuration window allows the designer of the
template to select an HP Insight Control server deployment folder to deploy ESXi. These Insight Control
server deployment job folders will be unique for each
environment. When an HP IO template is
imported, the specific OS provisioning job folder needs to be selected for each of the server
resources.

Summary

A common model for many IT organizations is that the application teams drive the resource
requirements
and purchasing process. This notion is a fundamentally important one since the goal of
IT is to support the business requirements. However, this approach is burdened with tedious, manual
steps and often requires many months of involvement between different

IT groups to get the
application deployed in production. This methodology can also lead to the creation of resource silos
between different application groups within IT. This separation yields a less efficient, less dynamic
and less responsive IT infrastr
ucture to support the demands of the business.

In building a converged infrastructure, you can tear down the proverbial walls between the
application and IT resource teams. This coordination allows IT organizations to create pools of
resources that can be

allocated, with approval, and shared as needed between the different
applications as the demands of the business dictate.

Built on the HP BladeSystem technologies, BladeSystem Matrix is a converged infrastructure platform
providing pools of computer, stor
age, and network resources that can be quickly deployed. The goals
of Matrix are to help accelerate provisioning, optimize IT capacity across physical and virtual
environments and to ensure predictable delivery and service levels. These enhancements enable

companies to address some of the key datacenter issues facing them today, including rising costs, low
utilization rates, and inflexible environments.

This white paper specifically focuses on the design and creation of an HP Matrix OE infrastructure
orche
stration template to support a VMware vCloud Director sample deployment in a Matrix
infrastructure. HP Matrix OE IO allows IT organizations to provision infrastructure consistently and
automatically from pools of shared resources using a self
-
service porta
l.

HP IO templates can be
configured to rapidly provision resources ranging from a single virtual machine to complex multi
-
tier
environments with physical and virtual servers and storage systems.





For more
information

The following links provide more information on VMware vCloud Director:

VMware vCloud Director Documentation


http://www.vmware.com/support/pubs/vcd_pubs.html

VMware vCloud Direct
or Installation and Configuration Guide


http://www.vmware.com/pdf/vcd_10_install.pdf

VMware vCloud Director Administrators Guide


h
ttp://www.vmware.com/pdf/vcd_10_admin_guide.pdf


The following links provide general information on the technologies discussed in this white paper:

HP BladeSystem


www.hp.com/go/bladesystem


HP Virtual Connec
t Technology


www.hp.com/go/virtualconnect


HP Insight Control server deployment


http://h18013.www1.hp.com/pr
oducts/servers/management/deployment
-
migration.html

HP Matrix Operating Environment (delivered through HP Insight Dynamics)


http://www.hp.com/go/matrixoe

http://www.hp.com/go/matrixoperatingenvironment

HP Insight Dynamics (Matrix OE) infrastructure orchestration documentation



http://h18004.www1.hp.com/products/solutions/insightdynamics/info
-
library.html


HP Operations Orchestration


www.hp.com/go/OO


HP EVA StorageWorks arrays


www.hp.com/go/eva


HP Insight Orchestration documentation


http://h18004.www1.hp.com/products/solutions/insightdynamics/info
-
library.html

HP Cloud Map for Oracle
11g R2 Single Instance Database


http://h71028.www7.hp.com/enterprise/us/en/partners/cloudmaps
-
oracle.html


To help us improve our documents, please provide feedback a
t
http://h71019.www7.hp.com/ActiveAnswers/us/en/solutions/technical_tools_feedback.html
.
















© Copyright 20
11

Hewlett
-
Packard Development Company, L.P. 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. Noth
ing herein should be construed as constituting an
additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Oracle is a registered trademark

of Oracle and/or its affiliates.

4AA3
-
3943ENW
, Created March 201
1