Best Practices for using vSphere AutoDeploy with Cisco UCS

774 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes

Comments are closed

  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
774
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
31
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Best Practices for using vSphere AutoDeploy with Cisco UCS

  1. 1. Stateless Computing with UCSM and VMwareAutoDeploy – Best PracticesJohn Kennedy TME SAVTG
  2. 2. What does “Stateless” mean?Stateless vs. Statefull Statefull := stuck to the  Stateless := free to migrate hardware where needed Maybe the OS is installed on a Nothing in the hardware prevents local disk, that isn’t replicated… the software from running on other Maybe an Application depends on hardware a burned in identifier, like WWPN MAC addresses, WWPN, etc. or MAC or UUID… move from machine to machine based on the needs of the businessPresentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 2
  3. 3. LAN SAN Storage Server Network SME SME SME • QoS settings • Border port assignment per vNIC • NIC Transmit/Receive • FC Fabric assignments for HBAs Rate Limiting• Subject matter experts • VLAN assignments for NICs • VLAN tagging config for NICs • Number of vHBAs consumed by manual • HBA WWN • assignments configuration chores • Number of vNICs PXE settings • FC Boot Parameters • NIC firmware • HBA firmware • Advanced feature settings• Serial processes and • Remote KVM IP settings • Call Home behavior multiple touches inhibit • Remote KVM firmware • RAID settings provisioning speed • • Server UUID Serial over LAN settings • Disk scrub actions • Boot order • IPMI settings • BIOS scrub actions• Configuration drift and • • BIOS firmware BIOS Settings maintenance challenges Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 3
  4. 4. Aligns People, Policy, and Configuration With Workload Server Name Unified UUID, MAC, WWN Boot Information Management LAN, SAN Config Firmware Policy Server Name Subject Matter Experts UUID, MAC, WWN Define Policies Boot Information LAN, SAN Config Storage Server Network Firmware Policy SME SME SME Server Name UUID, MAC, WWN Boot Information LAN, SAN Config Firmware Policy Server Name Policies Used UUID, MAC, WWN to Create Boot Information Server Policy… Service Profile LAN, SAN Config Templates Firmware Policy Storage Policy… Network Policy… Server Name UUID, MAC, WWN Virtualization Policy… Boot Information Service Profile Associating Service LAN, SAN Config Templates Profiles with Hardware Application Profiles… Firmware Policy Create Service Profiles Configures Servers Automatically Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 4
  5. 5. How does Cisco UCS enable stateless computing?Service profile basics UCS hardware can have any MAC, WWPN, UUID applied to it through software Choose layout Then select the layout with the background you would likePresentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 5
  6. 6. What are the benefits of Stateless Computing?Allows migration of server functionality Simplified provisioning Upgrades of hardware Migration to a new datacenter Without a forklift… Disaster recoveryPresentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 6
  7. 7. How does UCS enable stateless computing?By overriding the servers current WWPN, MAC, UUID, etc. UCS applies a “Service Profile” XML collection of metadata Service Profile is centralized, for ease of management Service Profiles can be removed from one server and applied to another Host OS, Applications, Network and Storage cannot tell the difference Service Profiles can be created from Service Profile Templates Repeatability, ease of management, reliability… When Template is updated, attached profiles get the updates.Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 7
  8. 8. But Doesn’t VMware enable Stateless Computing?Yes, with vSphere AutoDeploy Server boot from the network, not a SAN or local disk State data kept in Host Profiles Allows Elastic Capacity on DemandPresentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 8
  9. 9. AutoDeploy BasicsPresentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 9
  10. 10. Frailties of vSphere AutoDeploy Requires DHCP, TFTP, all must be managed If AutoDeploy server fails, ESXi servers can’t reboot In the event of a Power outage, AutoDeploy has to be running before ESXi can boot from it. If AutoDeploy is running in a VM… Chicken? Egg?Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 10
  11. 11. New Feature in vSphere 5.1: Statefull AutoDeploy Allows AutoDeploy to leave a copy of the ESXi server state on a local disk FlexFlash© , SATA drive, … If server reboots, and AutoDeploy or vCenter isn’t available, server retains it’s identity. When AutoDeploy is available, reboot the server, and it is once again stateless.Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 11
  12. 12. Does AutoDeploy conflict with Service Profiles?The two work together… When a Service Profile moves to another server, vCenter and AutoDeploy don’t see a new MAC or IP address ESXi server retains it’s host profile, and it’s state When a Service Profile moves to another server, the local disk can be “scrubbed” Assumes you use a Full Scrub profile in UCS, so be sure you do… This is an advantage of current servers!Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 12
  13. 13. Attributes unique to UCS The best practice method for autodeploy is to create a deploy rule that is associated with a Service Profile or Service Profile Template so that he infrastructure is consistent for a give deployment. UCS populates the oemstring variables with profile, template, and system name attributes: These attributes enable the creation UCS-specific DeployRules! Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 13
  14. 14. Best PracticesSpecific to this topic… Make your AutoDeploy, DHCP and TFTP highly available! Ensure the IPMI address stays with the profile Enables Distributed Power Management Make DHCP reservation for your Service Profiles Make individual Host Profiles for each Service Profile Set your Host Profiles to use Stateless install on local disk FlexFlash is available on C series only Don’t move B series SP to C series or vice versaPresentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 14
  15. 15. Best PracticesSpecific to this topic… Set your boot order profile to boot from: CDROM (for troubleshooting) vNICA (Best to use just one…) Local Disk Set your vNIC to use Native VLAN Otherwise either DHCP or gPXE will breakPresentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 15
  16. 16. In summary vSphere AutoDeploy 5.1 lets the ESXi server retain state on the local disk But that’s not good if you want to repurpose that server You have to scrub the server yourself The replacement server will have a new MAC, new IP, and won’t look the same to vCenter But with UCS Service Profiles, the MAC, WWPN, etc. go on whatever server you wish So your ESXi server remains available after moving to a new piece of hardwarePresentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 16
  17. 17. Where can I learn more? AutoDeploy documentation http://bit.ly/OgLlZj VMware KB article 2005131 http://bit.ly/OgLH27 Cisco UCS solutions http://www.cisco.com/go/ucsPresentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 17
  18. 18. Questions?Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 18

×