Iwan ‘e1’ Rahabok Staff SE, Strategic Accounts e1@vmware.com | Skype: e1_ang

1. Building your private cloud VCAP-DCD Iwan ‘e1’ Rahabok Staff SE, Strategic Accounts e1@vmware.com | Skype: e1_ang

2. What is Cloud? Only VMware offers true pooling and all the required Services vCloud Solution End-User Computing Cloud Infrastructure Cloud Application Platform Only VMware address all three Only VMware enables the hybrid cloud EnterpriseHybrid Cloud Private Cloud vCloud Powered Community Cloud

3. Recap from keynote… End User Computing IT Business Management End-UserExperience Desktop Provisioning Dynamic Resource Right-Sizing IT Financial Management IT Governance, Risk & Compliance Service Portfolio Management Cloud Application Platform Platform as a Service ApplicationProvisioning ApplicationPerformance Cloud Infrastructure & Management Automated Operations Security & Compliance EnterpriseHybrid Cloud

4. Private Cloud: what does it look like? Application Services: • Security • Disaster Recovery • High Availability • Fault Tolerant • Live Migration • Load Balancing • Back up vDC Management: • Inventory Management • Configuration Management • Compliance • Life Cycle • Performance Troubleshooting • Capacity Management • Patch Management • Orchestration Business Services (Application) IT Services OS for the entire virtual DC Physical DC 1 Physical DC 2 Uses the “Cloud OS” API

5. But how does it map to actual technology…? vCloud vCenter Portal Virtual DC Hybrid vCenter Standard • vSphere Management • Orchestrator & Automation vShield vCenter Operations Edge App AV • Performance Troubleshooting • Capacity Planning • Chargeback • Application Dependancy • Configuration Management • IT Dashboard vSphere vCenter SRM QoS: CPU, RAM, Disk, Network • DC migration • Automated DR with Failback Storage Appliance Partner plug-in • HA plug-in • Array plug-in • Backup plug-in Resource Abstraction • Network plug-in • Mgmt plug-in • Server plug-in vCenter Heartbeat

6. I got that. But how do I build one?

7. How to build your private cloud • Get the input right • Budget, Timeline, Application, Requirement, etc • Lay the foundation • Architecting the vSphere layer • Add advance services • Security as a service • DR as a service • Add vSphere-specific management • Configuration, Performance, Capacity, Chargeback • Add vCloud appropriately • 2-tier IT • Transient workload To give you some depth… Covered in vShield session Covered in SRM session Covered in VC Ops session Covered in vCloud session

8. Requirements & Goals • Contraints & Risks • Assumptions First Thing First • Budget constraint • Time constraint • Technical constraint • etc • Tech & Non-Tech assumptions • Operational assumptions • etc • Business & IT requirements • How many VMs do you need support? • What applications are you going to run? • etc

9. Design Methodology • Architecting a Private Cloud is not a sequential process • The components are inter-linked, and impact one another.

10. Building Blocks • Your cloud is made of discrete pieces of building blocks • Improve management significantly • Know when to create: • Separate RP, Subcluster, Cluster, Data Center, or vCenter • Separate Datastore, Datastore Cluster, or use RDM • Separate Port Group, vSwitch Network Compute Storage Cluster & Resource Pool Datastore and Cluster vSwitch and Port Groups

11. Methodology: Data Center • When do you create a separate… • Cluster? • vCenter DC? • vCenter? • Factors influencing the above • Security • Manage-ability • Budget • Workload

12. The need for Non Prod Cluster • This is unique in the virtual data center. • Non-Prod Cluster serves multiple purposes • Run Non Production VM • DR • Test-Bed for Infrastructure patching or updates. • Test-Bed for Infrastructure upgrade or expansion • Even with all the above… • How are you going to test SRM properly? • SRM test needs 2 vCenters, 2 arrays, 2 SRM servers. • If all are used in production, then where is the test-environment for SRM? Business IT This new layer does not exist in physical world. It is software, hence needs its own Non Prod envi.

13. The need for IT Cluster • Special purpose cluster • Running all the IT VMs used to manage the virtual DC or provide core services • Separated for ease for management & security This separation keeps Business Cluster clean, “strictly for business”.

14. Cluster Size • Factors impacting cluster size • Availability • Budget • Manage-ability • Overall farm size • Workload • Best practice for cluster • Identical hardware spec with same CPU frequency. • Complies with Fault Tolerant & VMware View best practices • General guide • 4-8 host per cluster • 8 node for View • 4 node for IT Cluster

15. Sample Architecture for vSphere-layer: Large Cloud 500 VM 1500 VM

16. Sample Architecture for vSphere-layer: Large Cloud

17. Sample: 3 tier cluster • The hosts can be identical, but SLA differs

18. Sample: 3 tier Storage • This become the type of Storage Pool provided to VM

19. QoS at Storage Layer • Constraints: • VMs interfere with one another as they share the same physical Storage Pool or Aggregate • Solution • Storage IO Control • All ESX hosts will co-ordinate and comply with policy. 4 1 2 1 2 1 1 3 1

20. QoS at Network Layer • Constraint: • VMs share physical NIC • In 10 GE, only 2 NIC for everything • Solution: • Network IO Control Without Network IO Control Data Mining Print Server Online Store Microsoft Exchange NFS vMotion FT With Network I/O Control Data Mining Print Server Online Store Microsoft Exchange NFS vMotion FT

21. Next Steps • To gain initial understanding, attend the following sessions • vCloud • SRM • VC Ops • vShield • Discuss with your VMware SE on your company private cloud plan • There is a standard “kit” that we follow to help you structure the approach. • Implement a pilot • Go deep on the technology • While private cloud is possible, it’s not as easy in reality.

22. Have a great journey to the Cloud.