User's Manual

8-4 Active System Manager User Guide, Release 7.0
Linking Editor
The first step in the workflow consists of connecting raw blades and L2 matrix switch in the linking editor.
Creating a Physical Template
The next step consists of dragging and dropping the managed devices in the Template editor to provision
Hypervisors. You are also required to drag some VLAN components in the Template editor, and, assign
some VLAN ID range to it or auto schedule it. Then, connect managed devices to VLAN component.
Note The managed devices to be used in the Physical template should not be shared as the device, being
provisioned with a Hypervisor in a session, should not be used in another session.
For more information, see the “Creating New Templates” section on page 8-6.
Creating Orchestration for Provisioning
In the next step, create a Setup type orchestration, to be mapped to the Physical template. The steps to create
orchestration are as follows:
• Create clusters on the vCenter.
• Create a Hypervisor on the blades.
• Register Hypervisors with the vCenter.
• Add hosts to the cluster created.
• Run discovery to populate the Active System Manager inventory (vCenter discovery) with cluster
entities.
Scheduling Template to Create a Session
The next step consists of scheduling Template to create a session.
Note The session scheduled from the Physical template is of permanent type.
Note If the session scheduled from a Physical template is being used by the system to realize a Logical
template (in present/future), and if the user cancels such physical session, then the system throws
an error.
Provisioning
To provision Hypervisors and clusters, the Resource Adapters are required. To achieve this, a series of
Setup orchestration steps are configured. In the session provisioning parameter, the RA adds cluster or
independent Hypervisor’s assettag [cluster=cluster1,cluster2 hypervisor=hypervisor1,hypervisor2].
Logical Template
The Logical template is used to provision VMs on Hypervisor or cluster, from sessions, created from
physical template. It is also used to provision the VLAN component from VLAN range given in the
Physical template.
Note The difference between the Logical and Normal template is that, the Logical template is realized
upon a Physical template based session.