In this section:
Cloud-init provides an alternative method to running Initial Setup on the SBC SWe Lite. For details on running Initial setup, refer to Running Initial Setup on SBC SWe Lite.
The cloud-init function is supported on all SWe Lite platforms.
The
Both the user_data and user-data file formats are supported.
The cloud-init function
The
If the
openstack/
2012-08-10/
or latest/
content/
ec2
latest/
If the
To create a config-drive image, you must configure the user_data file in the ISO image (see Creating a Config-drive Image). The user_data file contains the initial configuration data that the VNF uses for auto configuration.
The ISO file is only required for the initial boot of the
During the
Use one of the following procedures to create a config-drive image.
Enter the following command from the clout-utils package (Linux). This creates an ISO image, which includes the contents of the user_data file.
It is optional to enter the MACAddress
information of the interface objects (mgt0, pkt0, pkt1, pkt2, and pkt3).
If you provide this information, the cloud-init function performs the interface mapping based on the supplied MAC addresses. If you do not provide this information, the interface mapping is performed using the default PCI order.
You must include the MACAddress
information to perform interface mapping.
cloud-localds vendorconfig.iso user_data
After you create the ISO file, enter the following commands to attach it to either the KVM Hypervisor, VMware, or Hyper-V.
Alter the vendorconfig.iso filename so it identifies the vendor and VNF name.
<disk type="file" device="cdrom"> <driver name="qemu" type="raw" cache="none" /> <source file="/var/third-party/vendorname/vendorconfig.iso" /> <readonly /> <target dev="vdc" /> </disk>
Boot the
Use this procedure if you cannot use the cloud-utils package.
Enter the following commands to navigate to the appropriate directory.
mkdir config_drive mkdir /config_drive/openstack mkdir /config_drive/openstack/<creation date> cd /config_drive/openstack/ ln –s <creation date> latest
Enter the following information in the meta_data.json file.
{ <uuid>: <instance12345.mydomain.com> }
Enter the following information in the user_data file.
It is optional to enter the MACAddress
information of the interface objects (mgt0, pkt0, pkt1, pkt2, and pkt3).
If you provide this information, the cloud-init function performs the interface mapping based on the supplied MAC addresses. If you do not provide this information, the interface mapping is performed using the default PCI order.
You must include the MACAddress
information to perform interface mapping.
{ "setup": { "admin_account": { "adminUserName": "admin", "adminUserPassword": "admin" }, "rest_account": { "restUserName": "rest_user", "restUserPassword": "rest_password" }, "dns": { "primaryDNSServerIP":"125.62.150.2", "secondaryDNSServerIP":"125.62.150.3", "hostName": "SWELite-123", "domainName": "rbbn.com" }, "syslog": { "ServerAddress":"1.1.1.1" }, "ntp":{ "Ntp1ServerName":"10.253.6.92", "IsNtp1AuthEnabled":"1", "Ntp1ServerKeyId":"10", "Ntp1ServerKey":10 }, "mgt0": { "adminIPAddress": "10.21.150.3", "adminNetmask": "255.255.128.0", "gatewayAddress": "10.21.128.1", "MACAddress": "52:54:00:51:2E:4C", "ifIpAddrAssignMethod": "0" }, "pkt0": { "applicationIPV4Address": "192.168.21.2", "applicationIPV4Netmask": "255.255.255.0", "MACAddress": "52:54:00:51:47:4D", "ifIpAddrAssignMethod": "0", "NextHopIP1": "192.168.21.1" }, "pkt1": { "eth2IPV4Address":"192.168.22.2", "eth2IPV4Netmask":"255.255.255.0", "MACAddress": "52:54:00:51:BA:4E", "NextHopIP2": "192.168.22.1" }, "pkt2": { "eth3IPV4Address":"192.168.3.2", "eth3IPV4Netmask":"255.255.255.0", "MACAddress": "00:11:22:33:44:58", "NextHopIP3": "192.168.3.1" }, "pkt3": { "eth4IPV4Address":"192.168.4.2", "eth4IPV4Netmask":"255.255.255.0", "MACAddress": "00:11:22:33:44:59", "NextHopIP4": "192.168.4.1" } } }
Enter the following command to save the ISO file.
mkisofs -R -V config-2 -o vendorconfig.iso /config_drive
After you create the ISO file, enter the following commands to attach it to either the KVM Hypervisor, VMware, or Hyper-V.
Alter the vendorconfig.iso filename so it identifies the vendor and VNF name.
<disk type="file" device="cdrom"> <driver name="qemu" type="raw" cache="none" /> <source file="/var/third-party/vendorname/vendorconfig.iso" /> <readonly /> <target dev="vdc" /> </disk>