Playbooks

The playbooks provided here are intended as standalone examples.  They can be downloaded, copied and/or modified in any way you see fit.

Please be aware that all playbooks provided here are unofficial in nature, are provided as examples only, are unsupported and may need to be heavily modified before they can be used in a production environment.

Most playbooks can be directly accessed from the NutanixDev GitHub playbooks repo.  Larger playbooks will be published via dedicated repos when required.

Please see the License section of this page for information on how these playbooks may be used.

PLAYBOOK COLLECTION

Change VM to PXE Boot

Uses REST API calls to pull the MAC address and cluster VIP, then uses an SSH action to login to the cluster VIP and run

Read More »

Auto Categorize New VMs

Uses the VM created event trigger along with a set of branching actions to add VMs to categories based on their naming conventions.

Read More »

Add/Remove VM from Category

This playbook uses a simple manual trigger paired with a category action. There are 2 playbooks, for adding VMs to and removing VMs from categories.

Read More »

License

All playbooks are covered under the Open Source MIT license, as follows:

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.