User's Manual

Template Management 8-5
The workflow of Physical Template consists of the following steps:
• Creating a Logical Template
• Scheduling Template to Create a Session
• Provisioning
Note In the current implementation, there are separate inventory objects for raw blades and
hypervisors/clusters provisioned, where they are brought into the Active System Manager’s
inventory through discovery (these being logical entities have no link information).
Creating a Logical Template
The first step in the workflow consists of creating a Logical template by dragging VMs in the Template
editor. You are also required to drag the VLAN components in the Template editor. Then, link VMs and
managed devices with VLAN components. For more information, refer “Creating New Templates” section
on page 8-6.
Scheduling Template to Create a Session
In the case of Logical template, while scheduling the session, the resources are selected from the associated
Physical template. While scheduling a session, you can view the list of running sessions which are created
from Physical type template where you are a participant. You can select the session, onto which, you want
to realize the Logical template.
Note No session is selected by default. In such a case, the Active System Manager system considers the
template as Normal, for scheduling resources on the template.
After selecting the session, the VMs are to be scheduled on the managed devices, as, clusters or independent
Hypervisors in session (listed in the session parameters of the session, refer “Provisioning” section on
page 8-4). If the selected physical session does not contain a valid device information in the session
provisioning parameters; for example: if none of the devices are in the inventory, then the Logical template
is not scheduled.
Note In case of Logical templates, the link realization is already done on the session
associated with it. It is assumed that the links between VLAN component and VMs
on logical template are Logical, and so, the link feasibility between these can be
skipped while scheduling a session. For the same reason, during provisioning such
links will be marked as realized without actually realizing them.
VLAN IDs for the VLAN component should be within the range provisioned in the session. Also, the
VLAN component in the Logical template should be in AUTO mode.
Note As per the Precondition, t he VLAN component on the chosen Physical session as well
as the current Logical session should be shared. If either Physical session or the
Logical session are exclusive, then the VLAN ids on physical session cannot be used.
However, if the Physical based session is associated with a Logical template, and,
PBS is also set on devices in Logical template, then the session bound mechanism
overrides. In such as a case, the resources for realizing devices from Logical template
are used from the associated session.