To set up the Grid Master and begin pre-provisioning vNIOS for KVM Grid members in OpenStack using Elastic Scaling, complete the following.

1. Log in to OpenStack and compose the user data file for the Grid Master using the vi editor. You can also compose the data file locally and move it to the OpenStack node later. Note that you can deploy the Grid Master VM using temporary licenses. Elastic Scaling is not support on the Grid Master. For a sample of the Grid Master user data file, see the SampleUserDataFilesfortheGridMaster section.

2. Execute the neutron port-create command to create port IDs for the network interfaces (MGMT and LAN1/HA). You can use the security-group option to associate the vNIOS instance with the security group(s) you have created. For information, see Setting Up Security Groups. (Optionally, you can associate the vNIOS instance with a security group when you execute the nova boot command.) Following is an example:
   $ neutron port-create --security-group <name of the security group>
   For HA pairs, you must also execute the allowed-address-pairs option to define the VIP port for the HA configuration, using the VRRP MAC address and the Virtual Router ID you use. Following is an example:
   $ neutron port-create VIP –-allowed-address-pairs list=true mac_address= 00:00:5e:00:01:c8 ip_address=10.0.0.22

3. For an HA pair configuration only, ensure that you set allow_duplicate_networks=true in the nova.conf file to remove the restriction of allowing only one interface for each network in OpenStack.

4. Run the neutron port list command to view the network and port IDs generated for all network interfaces so you can copy and paste them into the nova boot command.

5. Execute the nova boot command in OpenStack to spin up the Grid Master VM. (Note: Use the custom name you came up with when creating flavors).
   Following is an example:
   nova boot --config-drive False --image
<nios-7.3.0-314352-2016-01-29-05-02-02-160G-1420-disk1.qcow2> --flavor <vnios1410.160>
– security-groups <name of the security group> --nic net-id=<the network ID for the MGMT interface> --nic net-id=<the network ID for the LAN1/HA interface only if you are configuring an HA pair> --nic port-id=<the IP address ID for the LAN1 interface>
<my-vm-grid-master>
   where:

   1. image defines the name of the software package you downloaded. For information about supported vNIOS for KVM models, see vNIOS for KVM Virtual Appliance Models.

   2. flavor specifies the flavors of the vNIOS for KVM instance. For information about how to define flavors, see Setting Up vNIOS OpenStack Flavors.

   3. security-groups defines the security group with which this vNIOS instance associates. For information about how to create rules for security groups, see Setting Up Security Groups.

   4. nic net-id specifies the network ID for the MGMT interface. Note that when provisioning an HA pair, you must also specify the network ID for the LAN1/HA interface. For more information, see the Sample Commands for Provisioning an HA Pair section.

   5. nic port-id specifies the IP address ID for the LAN1/HA interface.

      Note that for the vNIOS appliance to run in OpenStack, you must specify at least two networks, MGMT and LAN1/HA. To remove networks, use the neutron net-delete command. If some of the networks remain, use OpenStack Horizon to manually remove them.

   6. my-vm-grid-master defines the unique name of the VM.
      The vNIOS for KVM instance automatically spins up after the nova boot command is executed.

6. Log in to the NIOS GUI (Grid Manager) and do the following:

   • Create offline Grid members you plan to join the Grid.

   • Pre-provision these Grid members.

   • Generate a token for each member. Copy this token and save it for use in each Grid member user data file. For detailed instructions on how to pre-provision a member, refer to the Infoblox NIOS Documentation.

7. Log in to OpenStack and compose a user data file for each Grid member you plan to join the Grid. For a sample Grid member user data file, see the Sample User data File for Grid Members section.

8. Execute the nova boot command in OpenStack to spin up each Grid member VM, as follows:
   nova boot --config-drive False --image nios-7.2.4-1410-160.qcow2 --flavor vnios1410.160
--nic net-id=9db90ecf-83e8-44c5-930d-7e3548ff4a02 --nic
port-id=620d9fba-2f2d-4b81-9e51-eecfee551c15 --user-data ./user-data-2 my-vm-grid-member
   Note: Use config-drive True to tell OpenStack to use the virtual CD-ROM drive transport mechanism for the user data file. For information about user data files, see the Defining User Data Settings for vNIOS for KVM Instances section.

   • image defines the name of the software package you downloaded. For information about supported vNIOS for KVM models, see vNIOS for KVM Virtual Appliance Models.

   • flavor specifies the flavors of the vNIOS for KVM instance. For information about how to define flavors, see Setting Up vNIOS OpenStack Flavors.

   • nic net-id specifies the MGMT interface.

   • nic port-id specifies the LAN1 interface.

   • user-data specifies the name of the user data file.

   • my-vm-grid-member defines the name of the VM.

After you execute the nova boot command and launch the vNIOS for KVM instances, the Grid members automatically join the Grid. Further communications with the instance take place through Grid Manager and the NIOS CLI.

Defining User Data Settings for vNIOS for KVM Instances Using Cloud-Init

When you provision appliances using Elastic Scaling, vNIOS for KVM instances in an OpenStack environment require different user data settings. In OpenStack, you compose the user data file in plain text format by using the vi editor in plain text format.
OpenStack supports two transport mechanisms for the user data file: one through a virtual CDROM drive (also known as ISO parameter injection) and the other through the metadata network service. You can provide either or both transport mechanisms. OpenStack will make the user data file available to the vNIOS instance using the transport you configure in the user data file.
You can use the following data fields in the user data files for provisioning new instances using Elastic Scaling:

...

mgmt: fa:16:3e:14:3a:ae
lan1: fa:16:3e:01:29:0b
ha: fa:16:3e:25:43:8a
lan2: fa:16:3e:8e:26:4c

...