Chef agent bootstrap on Ubuntu

There are a few complexities to getting C2 to install a Chef agent on an Ubuntu server during provisioning.  

Specifying Username & Password

In CloudBolt 4.5 and beyond, there is a parameter called "Server Username" that can be set on the C2 Environment or Group so that a username other than "root" can be specified.  Also set the "VM Template Password" or "Server Password" so that C2 has the info it needs to invoke a Chef agent bootstrap.

 

SSH Connectivity

Many Ubuntu installations will not have an ssh server installed and running by default, and this will need to be added to your template before Chef agent bootstrap can succeed.

 

VMware-Specific Challenges

If using VMware, VMware's network customization of Ubuntu has some deficiencies that need to be worked around:

  • With Ubuntu 14, VMware can''t configure the DNS settings, and since Chef depends on DNS lookups, the servers will either need to get their DNS settings via DHCP, or the DNS settings will have to be configured inside the template before it is deployed.
  • The opposite behavior has been observed on Ubuntu 12 - that the servers do not apply their DNS settings when they come from DHCP, so it may be required to assign static IPs to those servers in C2, and ensure that the networks used in C2 have DNS servers set on them.  To set this, go to the resource handler -> networks -> edit settings.
  • C2 provisioning waits for the hostname to be set on newly-built VMs, but the way VMware configures hostnames does not take effect on Ubuntu servers until after the first reboot.  As a workaround, you can enable a post-network configuration reboot hook, as described by Reina in this KB article
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.