Programmatic Provisioning with Puppet Enterprise, Razor, and Cisco UCS
Cisco UCS and Puppet have put together solutions for rapid bare metal provisioning and infrastructure management. Visit the main Puppet Modules for UCS page for more information on how to use Puppet with UCS. For more on provisioning UCS with Puppet and Razor, read on!
Provisioning is done through Puppet's Razor module which offers a variety of options for installing host environments on provisioned nodes. One great thing about the solution is that Razor is already part of Puppet Enterprise and you can try Puppet Enterprise on up to 10 nodes for free!
At a high-level, the provisioning is accomplished in 3 steps:
Install and configure Puppet Enterprise for your environment. Puppet Enterprise’s rich set of modules allows for a wide range of managed workloads across all major OS, Virtual Machine, and Container environments. With Puppet Enterprise installed, you can setup Razor on one of your nodes for subsequent host provisioning.
Configure host "roles" in Puppet Enterprise and Razor.
Razor does the provisioning (OS installs) and you will want to create Razor policies for how node tags are matched and installs are done.
Create a UCS Service Profile and name it to match a Razor policy and Puppet Enterprise node group rule. Setting up your Profile to PXE boot from the Razor server and associating it with whatever servers you want to provision will automatically start the provisioning process.
The Service Profile is key to programmatically configuring the underlying infrastructure (compute, network, and storage configuration and policies).
You can automate all aspects of Service Profile creation and maintenance with the UCS Manager Python SDK. Cisco UCS's open API and higher level programming abstractions allow fast, reliable automation and true "infrastructure as code".
Once the above steps are performed and the node boots, it is provisioned by Razor and automatically handed off to Puppet Enterprise!
Details on the solution are provided in the attached whitepaper and you can checkouta video demo on YouTube or see the video on Cisco Communities. The demos pick up the process at step 3 with Puppet Enterprise and Razor already configured and a node being associated with a Service Profile and installed for the desired role.
Additional Information on Using Puppet with Cisco UCS
hi folks, I created two vSAN one on the fabric interconnt (vSAN ID = 100) A and one vSAN on the fabric interconnect B vSAN ID (200). I created the same on MDS A (vSAN 100) and vSAN 200 on the MDS B. I changed the vHBA template vSAN from the def...
Hi All, I am creating and testing backups for the CIMC remotely, these are going well but if I want to restore a backup then I get Status: Partially imported configurationDiagnostic message: Partial Succes From IMC log: parser_ma...
Hi, So my question is pretty basic. The C series servers act independently and can be managed by fabric interconnects does that mean they have built in fabric extenders on board that connect...
Hi All,I am running SNS-2515-K9 appliance for Cisco ISE and I noticed that in CIMC there is Major alarm encountered.Code: F0743 - PSU-REDUNDANCY-FAIL - Power Supply redundancy is lost. This system when purchased comes with only one PSU and as we are ...
Hi, I have a question about the UCSM Capability Catalog and CPUs, to help with my understanding. We have purchased some new M5 blades with 2nd-gen Intel Scalable processors (UCS-CPU-I6248R). My understanding was that the 4.0 firmware supported...