Task Name | - Kubernetes
|
Description | - .
|
Prerequisites | - Tested on 6.5 and
|
Category | Workflow |
Components | vSphere 6.5 |
User Inputs |
|
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 .WFD 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 .WFD 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.
The question came up can you overlap VLAN pools in UCSD?
The short answer is yes, but it has to be set up correctly.
Creation of 2 Pools in 2 different PODs (this is done under network policies):
Pool1 A
Pool2 C
Workflow:
Workflow execution:
Result VLAN 100 was pulled from each pool.
The VLAN usage screen also indicates that VLAN 100 was pulled 2 times:
When the VLAN pools are in the same POD then it will not over lap:
It pulled 100 and 101 on workflow run SR=911
Then it pulled 102 and 103 on workflow run SR=912
On workflow run SR=913 I added a VLAN pool in a different POD and it pulled the next VLAN 104 and from Pool C VLAN 100
The next run it pulled VLAN 105 and VLAN 101
Result is when the Pools are in the same POD then it will not over lab, but if the pools are in a different POD then VLAN overlay can be done.