Skip to content

CiscoSE/intersight-examples

Repository files navigation

These examples were functional and used for a demo before we were asked to share them publicly. In cleaning them it is very possible we broke a few things.

These were never intended to run in a customer environment and may not be friendly for many customers. There are a lot of dependencies and a lot of decisions need to be validated to a customers needs.

There are no inputs outside of the variables directory. I have tried to make most of it if not all of it variable based with a few exceptions. Even authentication comes from the authentication.yaml file.

We started with this policy, which configures the fabric and would generally need to be run before anything else.

IMM_Fabric_Policy_Creation_Playbook.yaml

Review the variables section to determine the variable files that are used for configuration. I would review every one of them. Plan on running and deleting them several times as you define your environment.

You cannot configure blade servers without a Chassis profile. These policies are needed for the server policies.

IMM_Chassis_Profile_Playbook.yaml

Finally the server profile is generated with this file

IMM_Server_Profile_Playbook.yaml

The esxiBios.yaml file used for the server profile is not user friendly and was never converted to variables.
AMD and Intel have different BIOS settings, and our examples are likely not appropriate for most users.
You should carefully consider how to modify that file if you intend to build a bios file with Ansible.
The current configuration was targeted towards Intel.

Each of the above playbooks is nothing more than a list of variable files and a collection of calls to other files that make up the actual tasks. I believe most if not all tasks are based on rest API calls. You should be familiar / comfortable with APIs if you are going to try to modify the actual tasks, but the task files themselves are intended to help API savvy users understand how to make these kinds of changes.

To learn more about the API, please consult the API developer center

https://intersight.com/apidocs/

PVA customers can just change intersight.com to your dns name of the PVA

:)

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published