| Task Name | UCSD BM Provisioning Workflow |
| Description | Sample BM provisioning WF with UCSM |
| Prerequisites | Tested on UCSD 6.6 Tested on BMA 6.6 |
| Category | Workflow |
| Components | |
| User Inputs | Service Profile Template, Server Identity, Organization, Service Profile Prefix, LAN Boot Policy, Root Password, PXE Image, PXE VLAN, Target BMA |
Instructions for Regular Workflow Use:
- Download the attached .ZIP file below to your computer. *Remember the location of the saved file on your computer.
- Unzip the file on your computer. Should end up with a .WFDX file.
- Log in to UCS Director as a user that has "system-admin" privileges.
- Navigate to "Policies-->Orchestration" and click on "Import".
- Click "Browse" and navigate to the location on your computer where the .WFDX file resides. Choose the .WFD file and click "Open".
- Click "Upload" and then "OK" once the file upload is completed. Then click "Next".
- Click the "Select" button next to "Import Workflows". Click the "Check All" button to check all checkboxes and then the "Select" button.
- Click "Submit".
- A new folder should appear in "Policies-->Orchestration" that contains the imported workflow. You will now need to update the included tasks with information about the specific environment.
Created by: Tamil Sankaralingam (tasankar@cisco.com)
Introduction:
This document will help the customer to understand and try out BareMetal provisioning use case in UCSD. The given work flow will work with both UCSD and UCSD Express.
This document will walk through the detailed steps, we need to follow to complete the BM provisioning via UCSD.
Requirements:
We have the following prerequisites in UCS Manager:
- 1. We should have the updating UCS Service Profile Template with the local boot policy
Note: Choose Local LUN in primary boot option for this use case.
- 2. Storage profile should be available with required disk group policy for at least Boot LUNs.
- 3. Boot policy with LAN boot option should be available with primary vNIC as first vNIC.
Note: Disable Enforce vNIC/vHBA/iSCSI Name or make sure the vNIC name is matching
- 4. PXE VLAN should be configured in in UCS Manager.
- 5. Need to have one unassociated server.
We have the following prerequisites in UCS Director:
- 1. The required UCSM Account should be managed by UCSD.
- 2. BMA account added into UCSD.
- 3. Upload Red Hat or CentOS from Administrator -> Physical Accounts -> Baremetal Agents--> Image Repository.
- 4. Modify ks.cfg file with the one available in the attachment and modify the OS version if you are trying with different OS version.
Note: Under Administrator -> Physical Accounts -> Baremetal Agents--> OS Catalog, select the newly uploaded OS and edit the configuration
- 5. Import the attached "Simple BM work flow" and validate.
We have the following prerequisite in Datacenter:
DHCP should have free IP address.
Note: Attachment contains the pxe.cfg and ks.cfg related to RHEL 7.4
Sample BM work flow inputs:
Service Profile Template: Choose the configured updating SP Template with local boot configuration.
Server Identity: Choose the identified unassociated server.
Organization: Choose the org in which you want to create the service profile.
Service Profile Prefix: Provide the preferred SP name prefix.
LAN Boot Policy: Choose the boot policy which has LAN boot as first boot order.
Root Password: Provide the root password to access the console
PXE Image: Choose the newly configured Image
PXE VLAN: Provide the configured PXE VLAN
Target BMA: Choose the BMA where the new image is uploaded
Execution Process:
After user provided the required inputs, the execution of work flow will create Service Profile from the given Service Profile Template. After unbinding the SP from SP Template, the boot policy of Service Profile will be modified to LAN boot policy. PXE VLAN will be associated with the newly created Service Profile. Service Profile will be associated with the selected server. PXE boot will install the OS in the configured LUN. End of the OS installation, the boot policy will be modified back to local boot and the SP binding will be restored with the SP Template. Server power will be reset will make sure that the OS will be booted from the Local LUN.
User can check OS installation in the server KVM console.
Note: Currently supported RAID is only HW RAID and assumption is /dev/sda gets created as part of LUN creation using the storage profile associated to the SP template. Or else we need to update the ks.cfg accordingly.
Troubleshooting:
- After OS installation, upon UCS Server power reset, OS will boot from local boot. If there is any wrong configuration in the boot policy, it may wait for the boot selection during the rebooting.
- In the Local Boot option, if we choose other than the “Local LUN” options, the OS boot will fail during the power reset.
**An independent Baremetal workflow for Cisco communities to consume. This can be tweaked or enhanced as per the use case of the customer.
