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.

#DFWVMUG - Automating the Next Generation Datacenter


Published on

Presentation outlining how the growth in the Datacenter and introduction of new management layers provides automation opportunities that today's administrators and engineers need to be aware and leverage.

Published in: Technology
  • Be the first to comment

#DFWVMUG - Automating the Next Generation Datacenter

  1. 1. Josh Atwell Cloud Architect, SolidFire DFW VMUG UserCon #DFWVMUG @Josh_Atwell Automating The Next Generation Datacenter
  2. 2. @josh_atwell
  3. 3. SolidFire Booth #35 1:15 30 Copies VMUG – End of Day 10 Copies
  4. 4. Back in my day… • Smaller server:admin ratios • More manual processes • Limited scripting/automation tools • Minimal automation targets • Fewer Layers
  5. 5. Physical Hardware Operating System AppApp In the beginning… .bat .vbs bash expect
  6. 6. Physical Hardware Operating System AppApp Virtualization Operating System vCenter Server Then there was… .bat .vbs bash expect
  7. 7. Physical Hardware Operating System App Virtualization VAAI VAIO VASA NSX ACI vCenter Server vRealize Suite Automation Orchestrator Log Insight Business Operating System App App VIO 3rd Party Tools 3rd Party Tools
  8. 8. Today’s Talking points • Infrastructure Extensibility • Policy based management • The Software Defined Datacenter • New Tools/Methods • Will we stop scripting? • Tomorrow’s Skills
  9. 9. Infrastructure Extensibility
  10. 10. Infrastructure Extensibility • APIs and SDKs to manage • Integration with common tools • Agility to change programmatically • Maximum feature availability
  11. 11. Policy Based Management
  12. 12. Policy Based Management • Policies define identity and behavior
  13. 13. Policy Based Management • Policies define identity and behavior • Policies can be one to many
  14. 14. Policy Based Management • Policies define identity and behavior • Policies can be one to many • Consistent and flexible • Control and monitor configuration drift
  15. 15. For Example…
  16. 16. Granular Control OS Basic Performance QoS Profile Min: 1000 Max: 2000 Burst: 5000 QoS Profile Min: 3000 Max: 5000 Burst: 10000 QoS Profile Min: 3000 Max: 8000 Burst: 15000 App Higher Performance Data/DB Specific Performance Storage Policy Based Management
  17. 17. • Software component developed by Storage Array Vendors • ESX and vCenter Server connect to VASA Provider • Provides Storage awareness services • Single VASA Provider can manage multiple arrays • Supports VASA APIs exported by ESX • VASA Provider can be implemented within the array’s management server or firmware • Responsible for creating Virtual Volumes SAN / NAS Virtual Datastore Data Path Protocol Endpoint PE vSphere Virtual Volumes Storage Container Vendor Provider (VASA) Control Path Control Path VASA Provider
  18. 18. VASA Provider Evolution VASA v1 vSphere 5.5 VMFS VVOLs Capability Profile enables SPBMv1 (Dynamic vs Tags) Block Device Storage DRS (Report Yes/No) IO Stats Events Alarms VASA v2 vSphere 6.x Non- VVOLs VASA v2 vSphere 6.x VVOLs VVOLs Profile VVOLs Management SPBM v2 Unmap
  19. 19. VVOL/SPBM Management Workflow Virtual Disk Storage Container(s) Storage policies Virtual Volumes Virtual Machines VASA Provider Virtual VolumeStorage presents capabilities of the storage container to VASA Provider Capabilities are used to build storage policies User selects available storage policy at provisioning Virtual Volume is provisioned through VASA provider Virtual disk resides on Virtual Volume aligned with storage policy Administrators can monitor policy compliance 1 2 3 4 5 6
  20. 20. Storage Policy Based Management (SPBM) Storage Capabilities via VASA Pros • Leverages storage capabilities provided by VASA provider. • Fully dynamic. • vCenter can query Volume/LUN to validate compliance. Cons • Can NOT be used to directly compare platforms. • Limited to what storage vendor presents through VASA.
  21. 21. Storage Policy Based Management (SPBM) vSphere Tags Pros • Widest range of definitions. • Define custom rules. • Can assign policies to any datastore that contains required tags. • Could conceivably be used to compare platforms. Cons • Not a dynamic process. • Requires manual work or automation through PowerShell or vRO. • Administrators must maintain policies and tags.
  22. 22. vRealize Automation
  23. 23. Desired State Tools • Create identity for application, server, or infrastructure. • Configuration drift management • 1:1 and 1:Many deployments DSC
  24. 24. Software Defined • IT as a Service - SLAs • Requires infrastructure extensibility • Leverages policies • Adapts based on active conditions
  25. 25. For Example… • Virus identified • VM tagged as high risk • VM Network policy changes to protect • Once sanitized it can return to normal policy • Or you can kill it and create a new VM
  26. 26. New Tools and Methods • DevOps Culture • Disposable app instances • Containers • Cloudy stuff • Version Control New Challenges to automate!!
  27. 27. Version Control
  28. 28. Version Control • GitHub (Git) • BitBucket • CodePlex • Subversion • FlowGrab (vRO) DO IT!!
  29. 29. Keep on Scripting • Increased extensibility = more scripting • Bridge to Software Defined • Gather info not presented in tools • Ad-Hoc FTW!
  30. 30. Next Generation Skills • Must understand all the application needs • Work to enable self-service • DevOps is not tools, it’s culture • Rise of the Infrastructure Developer
  31. 31. Thank You! • @josh_atwell • • Github/joshatwell • Good luck on the scavenger hunt with the VMUG App!