Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

VMware vSphere - Adam Grare - ManageIQ Design Summit 2016


Published on

ManageIQ for VMware vSphere by Adam Grare at ManageIQ Design Summit 2016

VDS demo:
Reconfigure demo:

Published in: Technology
  • Be the first to comment

  • Be the first to like this

VMware vSphere - Adam Grare - ManageIQ Design Summit 2016

  1. 1. ManageIQ for VMware vSphere Adam Grare
  2. 2. Agenda Introduction What’s new for vSphere in Darga? What’s next? Q&A
  3. 3. Introduction Adam Grare - ManageIQ Developer and Red Hat Senior Software Engineer focusing on VMware vSphere Provider Email: Gitter: @agrare
  4. 4. What’s new in Darga? Features vSphere Distributed Switches (VDS) VM Reconfigure - Adding/Removing Disks Datastore Clusters Behind the scenes Paged inventory collection for large environments Read-only datastore handling
  5. 5. New Features in Darga for vSphere
  6. 6. vSphere Distributed Switches (VDS)
  7. 7. vSphere Distributed Switches - what are they? The Problem: Traditionally host networking was configured per-host, and multiple networks had to have the same name for vMotion to work
  8. 8. vSphere Distributed Switches - what are they? The Problem: As the number of hosts grew configuration overhead increased as did the potential for errors
  9. 9. vSphere Distributed Switches - what are they? The Solution: A VDS aggregates host NICs into a single switch This allows the administrator to configure networking in a single location
  10. 10. vSphere Distributed Switches in ManageIQ ManageIQ already supported provisioning a VM to a VDS by querying the vCenter directly (a temporary workaround added in 2010) This caused issues with networking and session size due to caching all the VDS and LANs
  11. 11. vSphere Distributed Switches - what’s new? DistributedVirtualSwitch and DistributedVirtualPortGroup were added to our VMwareWebService gem The relationship between switches and hosts was changed from 1:1 to many-to-many, and a new model, HostSwitch, was created to track the associations
  12. 12. vSphere Distributed Switches - what’s new? Distributed switches are now collected with inventory refresh, are stored in VMDB, and can be seen on the host network summary page
  13. 13. vSphere Distributed Switches - what’s new? This allows you to provision VMs to a VDS LAN without communicating directly to the vCenter
  14. 14. vSphere Distributed Switches - Demo
  15. 15. vSphere Distributed Switches - what’s next? Improve how VDS are displayed Currently a switch is shown for each host member Want to move display of VDS to the provider level with better summary screens
  16. 16. vSphere Distributed Switches - what’s next? Extend the EventCatcher to pick up new DVPortGroups without a full refresh This will help us integrate better with SDDC tools like NSX which dynamically create DVS LANs
  17. 17. VM Reconfigure - Adding/Removing Disks
  18. 18. VM Reconfigure - Adding/Removing Disks In Addition to CPUs and Memory, Disks can now be added to and removed from VMs using the Reconfigure Virtual Machine page
  19. 19. VM Reconfigure - Adding/Removing Disks Multiple disks can be added and removed in the same ReconfigVM_Task up to the maximum number that VMware supports (60 disks) Disks can be thin or thick provisioned, and snapshot dependence and persistence can be set by the user
  20. 20. VM Reconfigure - Adding/Removing Disks - Demo
  21. 21. Datastore Clusters
  22. 22. Datastore Clusters Similar to Compute Clusters for hosts, Datastore Clusters allow aggregation of individual datastore resources and automated Storage vMotion through Storage DRS
  23. 23. Datastore Clusters - what’s new? The StoragePod type was added to our VMwareWebService gem Datastore Clusters are now collected in inventory refresh
  24. 24. Datastore Clusters - what’s new? Displayed in a tree-view on the Storage page
  25. 25. Datastore Clusters - what’s new? When provisioning a VM, datastores will show which cluster they are in
  26. 26. Datastore Clusters - what’s next? Collect if Storage DRS is enabled and allow provisioning to the datastore cluster, not just a specific datastore
  27. 27. Behind the Scenes
  28. 28. Paged inventory collection Initial inventory collection used to be done in a single API call With large environments it would hit our HTTP timeout, and we would progressively increase this timeout and retry
  29. 29. Paged inventory collection Now initial inventory is retrieved in pages and the timeout+retry loop has been removed, speeding up large inventory collection Both WaitForUpdates and RetrieveProperties were updated to collect inventory in pages
  30. 30. Read-only datastores Mounting an NFS datastore read-only is common for datastores containing e.g.: ISO images These were sometimes being picked by users or auto-placement during provisioning and the VM provision would fail
  31. 31. Read-only datastores Now we track the mount-info of each datastore to each host in the HostStorage model If a datastore is mounted read-only it will be excluded from the provisioning dialog
  32. 32. What’s next for the E-Release? Add Support for Storage Policy Based Management Display Policy on VMs and Datastores Select an existing policy when provisioning a VM This will be first new vSphere Management SDK endpoint added since VIM
  33. 33. What’s next for the E-Release? Enhanced vApp support Power Operations Cloning Provisioning
  34. 34. What’s next for the E-Release? Improve on features added in Darga VDS Datastore Clusters
  35. 35. Q&A Questions?
  36. 36. Thank You!