This session was mostly a demo of VMM 2012, where the speaker also covered some enhancements in the upcoming R2 release. Many of the Hyper-V 2012 R2 features have already been covered in other sessions, so there wasn’t a lot of new content. But he did a good walk through of several scenarios using VMM. I had forgotten that VMM can also provision storage from a physical array, automate SAN switch zoning, and present storage to a Hyper-V host, all within the VMM GUI. So you no longer have to pull out SAN tools, then your SAN switch GUI, then your virtualization management tool.
One thing to note is that the Azure Pack and the System Center App controller product are different products. A question was asked whether they would be merged down the road, and the speaker could not comment about futures. But one would hope they unify the provisioning portals and experience, and I expect they will down the road.
- Cloud OS: Three datacenters: On-prem, Windows Azure, Service Provider
- Many customers will have assets across all three clouds
- Customers need a consistent set of building blocks
- The hyper-v that ships to customers is the same version that powers all of Azure
- This session will focus on the on-prem and service provider clouds
What is the Cloud?
- Term is way over used and misunderstood
- Pool compute, storage and networking
- Allocatable on demand
- Automate everything – In VMM everything is Powered by PowerShell (500+ commandlets)
VMM – Enabling the Cloud
- Storage – Can use any kind of storage you wish – SAN (iSCSI, FC), or SMB 3.0
- Networking – In R2 VMM can manage physical switch configuration. NVGRE, PVLANs, etc.
- Compute – Intel and AMD processor support
- Virtualization Support – Hyper-V, VMware, Citrix XenServer
- Do not name your cloud after a department, it is a pool of compute power. Cloud is an SLA construct.
- User roles can be departments (Finance, HR, etc.). Construct an AD group, assign people, and assign access to appropriate cloud resources.
- Model your application you are deploying so you can enable self-service
Announcing the Cisco Nexus 1000v for Hyper-V is now available for production usage.
VMM Investments in 2012 R2
- Services, VMs, Clouds, Networking, Storage, Infastructure
- Think of a “stamp” as a consistent configuration of Storage, compute, edge components and management
- Later this year: All System Center components will be available a service template for fast and standard deployment
- Physical Computer profile is a new feature for a scale-out file server Hyper-V host
- 2012: VMM can appropriately zone SAN switches and provision storage from an array, such as 3PAR
- Enables ODX to copy VMs from the library to production
- Guest clustering using a shared VHDX file. No iSCSI or FC required.
- Service template supports first node having a different configuration from other nodes, so you can automate cluster builds
- VMM integrates with IPAM, so you can push/pull network configs with each other
- VMM will warn on physical switch VLAN misconfigurations with switches that support OMI management
- VMM can remediate network config problems on physical switches, if the network team allows it
- Directly deploy and configure gateway (site-to-site VPN, NAT, or virtual to physical gateway) settings
- Site-to-site VPN optionally supports iBGP
- Site-to-site VPN supports third party devices such as Juniper or Cisco concentrators, or another Windows server
- Delegation: Per-cloud delegated permissions
- New and very rich SCOM management pack for VMM