HP Matrix Operating Environment 7.3 Update 1 Installation and Configuration Guide for Provisioning with Virtual Resources

5. When finished setting up a network, click Save.
The network is now ready to use with infrastructure orchestration.
Trunk and VLAN networks
Cloud deployment environments and multi-tenancy environments require segmented networks for
customer data separation. VLAN tags in network packets can be used for network segmentation
for data separation. This enables a single wire to carry network packets from separate network
broadcast domains that are efficiently managed by switching technology in the data center
infrastructure and in virtualization hypervisors such as ESX and Hyper-V.
In Matrix infrastructure orchestration:
• A trunk is a physical or virtual subnet that carries traffic with multiple tags. It requires a trunk
or tunnel connection at the switch port level and a VLAN-aware network connection within
the server OS. A trunk network cannot be a VLAN network.
A trunk in infrastructure orchestration designer is a VLAN trunk representing a network
connection that carries multiple VLANs to a blade. How that is satisfied during a provisioning
request depends on the resources available to the candidate blades. For example, a trunk in
designer may be configured on the target blade using either Virtual Connect networks mapped
to a single port on the blade or a Virtual Connect tunneled trunk network that was defined in
IO as carrying the desired networks.
Port aggregations/teaming cannot be explicitly defined in infrastructure orchestration designer.
Port aggregation/teaming is primarily an operating system configuration action (for example,
adding the NICs to a vSwitch). This is best accomplished through naming conventions and
customized Operations Orchestration workflow scripts to configure the OS networking.
• A VLAN is carried by one or more Virtual Connect tunnel networks or other trunk networks in
the environment. A VLAN cannot be a trunk network.
Matrix infrastructure orchestration contains VLAN tagged network support to meet the following
objectives:
• Enable IO to be used to deploy a VM Host with a multi-network trunk connected to a server
blade network port
◦ Allow an IO administrator to manage and present trunk networks to be used in IO physical
provisioning
◦ Allow an architect to create a physical service template that designates a trunk network
◦ Provision physical server blades with a trunk connected to at least one of the available
NIC ports
• Enable Hyper-V VM provisioning to a Hyper-V server with a VLAN tagged virtual network
switch
◦ Provide the VLAN ID when creating a Hyper-V VM on a VLAN tagged virtual switch
Matrix infrastructure orchestration adds the ability to detail trunk networks and create templates
that represent a trunk network connected to a Virtual Connect server blade. From these definitions
IO is then able to orchestrate the creation of a Virtual Connect profile with a trunk connection.
With properly configured networks, the service request contains sufficient information to enable
HP Operations Orchestration workflows scripts to configure the Virtual Connect server blade for
trunk aware applications, primarily VM Host clusters.
102 Configuring Matrix infrastructure orchestration