The network virtualization concept of decoupling the logical networking from the physical networking much like in the same way server virtualization de-coupled the operating systems and software from the physical server hardware is permeating IT organizations.
NVP creates an intelligent abstraction layer between hosts and existing networks. Managed by a distributed controller system this intelligent edge transforms the physical network into a pool of network capacity and enables the programmatic creation of tens of thousands of isolated virtual networks to connect workloads in your cloud.
Why am I writing about NVP when I mostly write about EUC/VDI?
I have recently been asked to look at how would be possible to automatically add VMware View virtual desktops into the NVP Controller Cluster. The NVP Controller Cluster is a highly available distributed system that manages all the virtualized network components and connections. The Controller Cluster exposes a RESTful web services API and defines virtual networks.
Besides the known benefits of network virtualization such as dramatically reducing the complexity of the physical network, and creating shared pool of network capacity that can be consumed and repurposed on demand; with the right storage replication technology in place, network virtualization for virtual desktops enables organizations to move desktop workloads dynamically across datacenter boundaries.
As you may be aware VMware View only provide PowerCLI mechanisms for remote management. Whilst I cannot yet provide details on the integration methods utilized, I am able to share a generic PowerShell module I have created to operate the NVP Controller Cluster. This module is not specific for virtual desktops and may be used for any vCenter based virtual machine.
There are 4 cmdlets to be known in order to add a vCenter virtual machine into the NVP Cluster:
- Connect-NVP: Establish connectivity to NVP API. Must be associated to $variable for session persistence (cookies).
- Query-NVPlSwitch: Return the lSwitch UUID. lSwitch UUID is required for other operations. The lSwitch must be created first.
- New-NVPLogicalSwitchPort: Create a logical switch port for the virtual machine.
- Add-NVPVMVIFtoLogicalPort: Attach a virtual machine VIF to the logical lSwitch port.
The PowerShell module below uses PowerShell 3.0 and VMware vSphere PowerCLI.
The module is available to download here.
[css lang=”plain” autolinks=”false” classname=”myclass” collapse=”false” firstline=”1″ padlinenumbers=”false” gutter=”true” smarttabs=”true” tabsize=”10″ toolbar=”true”]
Import-Module -Name nvp_module.psm1
$nvpSession = Connect-NVP -nvpIPAddress "x.x.x.x" -nvpusername "admin" -nvppassword "password"
$lswitch = Query-NVPlSwitch -nvpSession $session -nvpIPAddress "x.x.x.x" -nvplswitch "switch_name"
$lport = New-NVPLogicalSwitchPort -nvpSession $session -lSwitch_uuid $lswitch -vmname "vm_name" -nvpIPAddress "x.x.x.x"
Add-NVPVMVIFtoLogicalPort -nvpSession $session -lswitch_uuid $lswitch -lPort_uuid $lport -vmname "vm_name" -nvpIPAddress "x.x.x.x" -PowerOnVM