Abiquo 5.1

Skip to end of metadata
Go to start of metadata

Chef is an infrastructure automation product that uses configuration recipes. You can use Abiquo Chef Integration to deploy a VM that will then configure itself using Chef recipes and roles. In datacenters, the Abiquo Chef integration works with Cloud-init or Cloud-base-init, so you will need compatible templates and you will need to select this guest setup option.
Configure Chef Recipes and Roles

The Chef tab is enabled if the enterprise is Chef-enabled and the VM template is marked for Cloud-init support.

Before you deploy the VM, you can select from the available roles and recipes. By default, you can select roles. Mark the "Select individual components" checkbox to select individual recipes too. The platform will add your selection to the Virtual Appliance's runlist in order of selection. When you deploy the VM, it will download the roles and recipes, and run them in order.

To change the order of the runlist, click on the pencil Edit button beside a role or recipe, then enter the new order number, then click ok.

If you change the runlist after deploy, Abiquo will update the Chef server, and your Chef-client recipe can obtain these changes from the Chef server.

Related links:

Configure Chef Attributes

The Abiquo Chef integration now supports Chef attributes, which are passed to Chef for your recipes. You can find lists of attributes in the Chef recipe configuration files. See https://docs.chef.io/nodes.html  
  1. Edit the VM and go to Chef → Attributes
  2. Enter the attributes, which are the parameters for each recipe, in JSON format. 
    • The Chef attributes must be enclosed in "{ }". You must enter a valid JSON document and Abiquo will validate it
    • Abiquo does not validate the attributes, so check them carefully
  3. Click Save, which will save the entire VM configuration

Related pages

  • No labels