vCloud Architecture BrownBag


Published on

ProfessionalVMware BrownBag covering the

Published in: Technology, Spiritual
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • The key to building a successful Cloud is ensuring the underlying vSphere layer is designed and built correctly. vSphere is what enables the cloud providing the virtualization layer and without it there is no cloud.
  • Once we have builtvSphere, we look at bringing in vCloud Director and vShield Manager. vCloud Director is the abstraction enginge, and vShield Manager provides the functionality to enable the networking features used within a cloud environment.
  • vCloud Architecture BrownBag

    1. 1. vCloud Architecture Deep Dive Chris Colotti David Hill
    2. 2. Who We AreChris Colotti, VMware David Hill, VMware Global COE Global COE Consulting Architect Senior Consultant VCDX #37 CIM Lead UKTwitter @CColotti Twitter @DaveHill99vCD on Vblock / Upgrades vCAT 2.0 contributorVMworld Presenter 08/09/11 VMworld/PEX Presenter 2011Blogger Blogger
    3. 3. What We Will Talk AboutvCloud “Eco-System” of Components All the possible building blocks Importance of Orchestration and knowledge depthSolution in Practice Based on vCAT 2.0Published Catalog vApp Cloning Based on 3-part “clone wars” blog postsOpen Q&A on anything vCloud
    4. 4. vCloud Eco-System
    5. 5. The Building Blocks
    6. 6. Change in ManagementvSphere was traditionally the management layerWith vCloud Director vCenter is more “Application”LayervSphere administrators may not be vCloudAdministratorsOrchestration and customization may be importantHigh availability of all components involved
    7. 7. Depth of Skills and Knowledge vSphere / ESX Deeper Storage Skills Deeper Networking & Firewall skills Scripting (PowerCLI) Workflows / Automation Capacity Planning Before it was ESX, vCenter and some Scripting It is about Infrastructure Management now
    8. 8. Example Solution in Practice
    9. 9. One vCloud, Two BuildingsTwo On-Campus Datacenters2 vCloud Director Cells per building (4 Total Cells) Single NFS mount in Building A F5 GTM Load Balancer1 vCenter Server per building (2 Total) Protected with vCenter Heartbeat 1 Update Manager server per building 1 Cluster per vCentervShield Manager per building Protected use VMware Fault ToleranceDatabase Servers per buildingvCenter Orchestrator Server per buildingPublished Master Catalogs
    10. 10. Published Catalogs and vApp Cloning
    11. 11. How Cloning WorksvSphere ESX host with VM registered does the cloneBlock based copy when source and destinationpresented (Same vCenter) VAAI can help with offloadNetwork copy when source/destination host storageis not equally presented (Same vCenter)vCloud Director “Transfer” space used when movingbetween vCenter servers
    12. 12. Logical vCloud Director View
    13. 13. Cloning ExamplesSilver to Silver = Block Based between LUNs VAAI can also improveSliver to Gold = Network Copy between ESX hostsSilver to Bronze = vCloud Director Transfer Space(NFS) OVF Export from vCenter 1 OVF Import to vCenter 2 Similar to vCloud Connector Cell Network Design Considerations
    14. 14. Cell Network ConsiderationsToday two maybe three interfaces HTTP/Console Proxy OS Management / DB Backend OS Jumbo Mgmt FramesConsider Additional Ones NFS NFS vSphere Management HTTP/Co L2May require static or additional nsoleRoutes vSphereConsider Separate VLAN’s DB L2Enable Jumbo Frames on NFS,vSphere Ports
    15. 15. Possible Cluster Considerations Dedicated “Catalog” Provider vDC Force all cloning load to hosts not running VM’s VAAI on Storage Challenge to force Org Catalogs to this Provider (vCO?) Within the same vCenter use a Catalog LUN Presented to all hosts even in different clusters Remember cross-vCenter will be network based copy Additional ESX Kernel Ports (No Network I/O Control)
    16. 16. Final Thoughts / Common Themes Window 2008 SYSPREP Re-Arm Not vCloud Specific, but be aware of it DRS Never disable it vCloud Director relies on it Supported Cell Operating Systems Check the latest list, always use what is supported NFS Share permissions Ensure “vcloud” user/group has read write to share vCloud Director and vSphere Maximums apply Combined document now Unique BIOS UUID VMware KB2006605
    17. 17. vCloud MaximumsItem MaximumVirtual machine count 20000Powered‐On virtual machine count 10000Organizations 10000Virtual machines per vApp 64vApps per organization 500Number of networks 7500Hosts 2000vCenter Servers 25Virtual Data Centers 10000Datastores 1024Calalogs 1000 Source: configuration-maximums.pdf
    18. 18. Thank You! We can always use more Followers  PS – Did we mention never Disable DRS with vCloud Director….. QuestionsTwitter @CColotti Twitter @DaveHill99
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.