Applies To:

Show Versions Show Versions

Manual Chapter: About Cloud-Init and BIG-IP VE
Manual Chapter
Table of Contents   |   Next Chapter >>

About Cloud-Init and BIG-IP VE

Cloud-Init is automatically installed when you deploy BIG-IP® VE.

You can use Cloud-Init to initiate bash scripts (including tmsh commands) to perform tasks, like creating a virtual server or pool.

In your scripts, you can also call a cloud provider's metadata service to get attributes you might need when running commands. For example, you can query the service to return the hostname, which you can then use to populate values in BIG-IP VE.

Here is sample bash script for calling the AWS EC2 metadata service to return the hostname:
!/bin/bash
hostname=$(curl http://169.254.169.254/latest/meta-data/hostname)
echo $hostname
Important: If you expect your Cloud-Init script to take a long time to execute (10 seconds or more), you should fork to a new process, so that BIG-IP VE can finish deploying and SSH can be available.

F5 provides AWS Cloud Formation Templates (CFTs), which include scripts that are run by Cloud-Init. These scripts query the metadata service to populate specific values in the CFT. For more information about CFTs provided by F5, go to https://github.com/F5Networks.

Hypervisors with Cloud-Init support in BIG-IP VE

Cloud-Init version 0.7.2 is automatically installed when you use BIG-IP® VE on the following hypervisors.

  • Amazon Web Services EC2
  • VMware ESXi
  • Microsoft Hyper-V
  • Citrix XenServer
  • Linux KVM
  • Linux Xen Project
Note: This version of BIG-IP VE does not support Cloud-Init in Microsoft Azure.

Cloud-Init data sources supported in BIG-IP VE

The following data sources are supported in this version of BIG-IP® VE.

  • The EC2 data source is supported in AWS and OpenStack.
  • Config Drive V2 is supported in OpenStack and all non-cloud hypervisors.

Cloud-Init modules supported in BIG-IP VE

The following Cloud-Init modules are supported on the following hypervisors and clouds in this version of BIG-IP® VE.

Cloud-Init module Hypervisors/Cloud Services
Emit Upstart AWS in BIG-IP VE 12.0 only
Final Message All
Migrator AWS in BIG-IP VE 12.0 only
Runcmd AWS in BIG-IP VE 12.0 and 12.1
Scripts Per Boot All
Scripts Per Instance All
Scripts Per Once All
Scripts User All
Ssh Import Id AWS in BIG-IP VE 12.0 only
Write Files All

Determine if Cloud-Init was installed on BIG-IP VE

Cloud-Init is installed on BIG-IP® VE by scripts that run at boot time. If you are having trouble with Cloud-Init, you might want to confirm that it was properly installed.
  1. Use SSH to connect to your BIG-IP VE instance.
  2. At the bash prompt, change the directory.
    cd /var/log
  3. Determine the name of the latest boot log file by showing the contents of the directory.
    dir
  4. Use vi to open the latest boot log file, which might be named something like boot.log, boot.log.1, or boot.log.2.
    vi boot.log
  5. When the file opens, search for the word cloud.
    /cloud
  6. Go to the next instance of cloud until you find cloud-init.
    /n
  7. There should be four entries in the log. Find the most recent entries that contain cloud-init.
    localhost notice 10virtual-platform.sysinit: Enabled service cloud-init-local
    localhost notice 10virtual-platform.sysinit: Enabled service cloud-init
    localhost notice 10virtual-platform.sysinit: Enabled service cloud-config
    localhost notice 10virtual-platform.sysinit: Enabled service cloud-final
    These entries indicate that Cloud-Init was installed when BIG-IP VE booted.

Disable Cloud-Init on BIG-IP VE

Cloud-Init is installed on BIG-IP® VE by scripts that run at boot time. To speed boot time, you may want to stop Cloud-Init from automatically installing.
  1. Use SSH to connect to your BIG-IP VE instance.
  2. Ensure you are at the tmshprompt.
  3. Run this command to disable the Cloud-Init database setting.
    modify sys db service.cloudinit value disable
  4. Run this command to reboot BIG-IP VE immediately.
    reboot
When BIG-IP VE restarts, Cloud-Init is no longer running.
If you decide to re-enable Cloud-Init later, run this command and reboot: modify sys db service.cloudinit value enable.
Table of Contents   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)