M7: Cross-Platform Management

1. M7: Cross-Platform Management Symon Perriman Matt McSpirit Technical Evangelist Technical Product Manager

2. Introduction to Hyper-V Jump Start

3. Module Agenda • Citrix Management • VMware Management • Cross-Platform Management

4. Cross Platform Management Application Frameworks Management OS Hypervisor Fabric

5. Citrix Management

6. Citrix XenServer Key Requirements XenServer Must be XenServer 6.0 / 6.1 Citrix XenServer – Microsoft System Center Integration Pack

7. Citrix XenServer 6.x | Host Setup • XenCenter still required for Host Configuration • VMM supports adding both standalone hosts & pools • Pools would be pre-created in XenCenter • VMM can provide Host Power Control • Restart, Shutdown & Power On (if OOB Capable Hardware) • VMM supports Maintenance Mode • Host updates must be managed by XenCenter

8. Citrix XenServer 6.x | Host Storage • VMM supports the management of XenServer 6.0 with: • iSCSI Storage • NFS Storage • Fiber Channel Storage • StorageLink-based Storage • Local or Shared Storage • All storage must be configured through XenCenter • VMM supports the use of ISO’s from ISO Repositories • Repository can be on NFS or CIFS but must be read/write

9. Citrix XenServer 6.x | Host Networking • Hyper-V & XenServer Networking is very different… • With Hyper-V, VLAN tagging takes place closer to the vNIC • With XenServer, VLAN tagging takes place at physical pseudo NIC level • Therefore with XenServer, you end up with a separate switch for each VLAN • VMM wraps a single Virtual Switch around all of the XenServer switches on a single physical adapter

10. Citrix XenServer 6.x | Host Networking

11. Citrix XenServer 6.x | Import Process • Create Run As Account • Add Resources • XenServer Hosts & Clusters • Specify Host Name(s) • Click Add – Finish! • Properties - NICs

12. Citrix XenServer 6.x | VM Management • Templates • VMM Templates are supported with XenServer • VMM will not deploy XenServer Tools • XenServer Templates are not used by VMM • Create VM in XenCenter and create a VMM Template from this • VMM Key Features • VMM Service Templates deployed to XenServer Hosts/Pools • Private Cloud Creation • Intelligent Placement • Dynamic Optimization, Power Optimization & PRO • Live Migration (XenMotion)

13. VMware Management

14. VMware vSphere Key Requirements vSphere Must be vCenter Server 4.1/5.1 ESX/ESXi 4.1 ESXi 5.1

15. VMware vSphere – Key Considerations • VMM isn’t intended to replace vCenter • Aimed at day to day operations of hosts & clusters • Create/Manage/Store/Deploy VMs • More advanced tasks performed in vCenter • Initial Networking Configuration – Port Groups, vDS etc. • Fault Tolerance – VMM recognizes FT VMs, but won’t configure them. • Update Management still requires VUM

16. VMware vSphere | VM Management • Templates • Supports creation of VMDK-based templates from Library • Supports importing of templates from vCenter (No VMDK copy) • VMM Key Features • VMM Service Templates deployed to vSphere Hosts/Clusters • Private Cloud Creation • Intelligent Placement • Dynamic Optimization, Power Optimization & PRO • Live Migration (vMotion) & Storage Migration (svMotion)

17. Cross-PlatformManagement

18. Cross-Platform Management Application Frameworks Management OS Hypervisor Fabric

19. Deploy Linux guests Support • Consistency • Use VM Templates for Linux based VM deployments • Deploy Linux VMs as tiers in a Service • Deploy Linux VMs to Hyper-V Hosts • Customization • Root password • Computername • DNSDomainName • IP address • Timezone • Root ssh public key • Run once commands

20. Cross-Platform Visibility Health monitoring Windows Linux/UNIX support Novel SLES, Red Hat Enterprise Linux, IBM AIX 7.1, HP-UX, Solaris, and others through partner management packs Heterogeneous monitoring

21. Cross-Platform Management Application Frameworks Management OS Hypervisor Fabric

22. Integration Packs for automation across clouds Microsoft Cloud Private Cloud Service Provider Out-of-the-box Out-of-the-box Partner enabled IP’s • Orchestrator integration enables Microsoft and third-party platforms to coordinate and use operational data in the infrastructure across varying cloud scenarios (on-premises, Microsoft cloud and service provider clouds) • Orchestrator integration enables Microsoft and third-party platforms to coordinate and use operational data in the infrastructure across varying cloud scenarios (on-premises, Microsoft cloud and service provider clouds) • BMC • Dell - AIM • NetApp - OCPM • Cisco • UCS • NCM JaxMP/Frysoft • Vision Solutions - DoubleTake • Kelverion • ServiceNow • Data Manipulation • HTTP Applications • All Systems Center Components • Active Directory • Exchange (User and Admin) • IBM Tivoli Netcool/Omnibus • HP (OM, SM, iLO) • All Systems Center Components • Active Directory • Exchange (User and Admin) • IBM Tivoli Netcool/Omnibus • HP (OM, SM, iLO) • Windows Azure • FTP • VMware vSphere • Windows Azure • FTP • VMware vSphere • New capabilities in SP1

23. Cross Platform Management Application Frameworks Management OS Hypervisor Fabric

24. JEE monitoring – supported platforms

25. Microsoft | VMware Comparison vCloud Automation Center focuses on provisioning VMs to alternative hypervisors, whilst the Multi-Hypervisor Manager plug-in for vCenter offers only very basic capabilities VMware do not produce any operating systems, and support is therefore focused not on the guest operating system itself, but instead, on the VM Tools and hardware. vCenter Orchestrator has a limited number of 3rd party plug-ins and vCenter Operations Management Suite requires the purchase of 3rd Party adaptors to integrate. Monitoring capabilities do extend to multiple frameworks but support for many frameworks is out of date - .NET 3.0 is the latest for instance. Also, the monitoring is not connected to any true DevOps capability, and lacks remediation guidance around detected issues. VMware Information: http://www.vmware.com/support/mhm/doc/vcenter-multi-hypervisor-manager-10-release-notes.html, http://partnerweb.vmware.com/GOSIG/home.html,