Skip to end of metadata
Go to start of metadata

The Ubuntu Certified Images are designed by Canonical to be optimized for various cloud infrastructures, including the Joyent Cloud.

The Certified Images support cloud-init to provide a uniform boot-time setup. Joyent Cloud boot script user-script metadata is also available to do per-boot scripting.

You can use Juju to deploy your web applications on Joyent-hosted Ubuntu instances. To learn how to configure Juju to work with the Joyent Cloud, see Configuring for Joyent Cloud in the Juju documentation.

Joyent-supplied Ubuntu images prior to these Certified Images have some basic differences. The Summary of Differences section summarizes those differences.

About the Certified Images

The goal of the Ubuntu Certified Images is to work the same way regardless of the cloud infrastructure hosting them. This section describes some basic differences between the Certified Images and the legacy Joyent-supplied Ubuntu images.

Default User

In Certified Images, the default user is ubuntu. You cannot log in as root. However, the ubuntu user is authorized to use sudo to do things as root.

Default Disk Layout

In Certified images, the ephemeral device (data disk) is mounted at /mnt. In Joyent-supplied images, the ephemeral device is mounted at /data. The following output of the df command shows the default file system in a Certified Image.

Boot-Time Setup

The Certified images can use both cloud-init and Joyent boot-time setup.

Initialization data (like cloud-init) is provided as metadata when the instance is created. You can provide this metadata CLI command option --metadata-file (or --script for Joyent images).

Cloud-init data is provided as metadata with the cloud-init:user-data key. Joyent boot-time data is supplied as metadata with the user-data and user-script keys.

  • cloud-init:user-data is consumed once per instance
  • user-script is consumed each boot
  • user-data is consumed each boot

Keep in mind that you may be able to log in to your instance before cloud-init is finished. Complex cloud-init or user-script scripts could take several minutes to complete. Please plan accordingly.

cloud-init Examples

cloud-init is the Ubuntu package that handles first-boot initialization of a cloud instance. You can learn more information about cloud-init here and in the cloud-init documentation.

These examples use the CloudAPI command-line interface. To run these examples, make sure that you are using at least version 7.2.0 of the CloudAPI tools.

cloud-init with a shell script

Anything in the cloud-init:user-data, runs once per instance on the first boot. In this example, the shell script ubuntu.cloud.sh will run on first boot.

ubuntu.cloud.sh does nothing more than to write a message with the current time in /root/output.txt. It should be in the same directory that you run the sdc-createmachine in.

ubuntu.cloud.sh

To provision an Ubuntu instance, you would use the sdc-createmachine command like this. 46407334-9096-40ef-bb72-6f9a094f0507 is the UUID of the the Ubuntu 13.10 image.

After the instance is provisioned, you can log in to it and verify that the script ran:

output.txt

cloud-init with a cloud-config command

cloud-init can also take a YAML file that describes how to configure the instance. In this example, cloud.init is a cloud-init config file that:

  • updates the package list
  • upgrades installed packages
  • installs the apache2 package
cloud.init

To provision an Ubuntu instance, you would use the sdc-createmachine command like this, using the name of the config file.

After provisioning, you can check that the apache2 packages were installed:

Joyent user-script Example

Any script provided as a user script, will run every time the instance boots. The user script can be provided as the name of a file to the --script option to sdc-createmachine, or as the value of the user-script metadata key.

In this example, the script userscript.sh will run when the instance is provisioned as well as on every reboot.

userscript.sh

Provision the instance:

After provisioning, check the output.

If you were to reboot the instance a few days later, you would see this:

Summary of Differences

This table summarizes the difference between the Canonical Certified images and the Joyent-supplied images.

  Joyent-supplied Canonical-supplied
Default user root ubuntu
Disk layout /tmp on separate partition
/data is the mount point for the ephemeral device
staticaly configured fstab
/tmp on rootfs
/mnt is the mount point for the ephemeral device
dynamic mounts
*Boot-time setup user-script metadata cloud-init
Kernel Locked Uses stock Ubuntu virtual kernel

The Canonical Ubuntu Certified Images

14.04 20140519

Name ubuntu-certified-14.04
Description Ubuntu 14.04 LTS (20140416 64-bit). Certified Ubuntu Server Cloud Image from Canonical.
UUID 7735fbba-3706-49f0-8020-9e69e11f8ea1

What's New in This Image

  • Fix for CVE-2014-0196
  • Added kernel tuning for vm.dirty_background_bytes. This causees dirty data to be flushed at 100 Mbytes for improved performance.

Packages Installed in This Image

For a detailed list of every package installed with this image, click here.

14.04 20140416

Name ubuntu-certified-14.04
Description Ubuntu 14.04 LTS (20140416 64-bit). Certified Ubuntu Server Cloud Image from Canonical.
UUID df165dad-0a5d-4eb7-8646-50507ff1c136

What's New in This Image

Packages Installed in This Image

For a detailed list of every package installed with this image, click here.

13.10 20140519

Name ubuntu-certified-13.10
Description Ubuntu 13.10 (20140519 64-bit). Certified Ubuntu Server Cloud Image from Canonical.
UUID 6ae6cc4e-2885-4144-8da2-2fe822e0c84c

What's New in This Image

  • Fix for CVE-2014-0196
  • Added kernel tuning for vm.dirty_background_bytes. This causees dirty data to be flushed at 100 Mbytes for improved performance.

Packages Installed in This Image

For a detailed list of every package installed with this image, click here.

13.10 20140410

Name ubuntu-certified-13.10
Description Ubuntu 13.10 (20140410 64-bit). Certified Ubuntu Server Cloud Image from Canonical.
UUID 96aae6e5-c130-44aa-a4e3-d2394591eee5

What's New in This Image

  • Updated OpenSSL to address HeartBleed bug (openssl 1.0.1-4ubuntu5.12)

Packages Installed in This Image

For a detailed list of every package installed with this image, click here.

13.10 20140227

Name ubuntu-certified-13.10
Description Ubuntu 13.10 (20140227 64-bit). Certified Ubuntu Server Cloud Image from Canonical.
UUID 049dfe64-6c37-4b88-8e89-4b8aa0f129f2

What's New in This Image

  • Resolved an issue where ssh host keys are not generated when instance is provisioned with one interface.
  • Resolved an issue where the hostid command always returns "00000000" rather than a unique value.
  • Resolved an issue where the sudo command produces a "unable to resolve host.." warning.
  • Ubuntu 13.10 Release Notes

Packages Installed in This Image

For a detailed list of every package installed with this image, click here.

12.04 20140408

Name base
base64
Description Ubuntu 12.04.4 LTS (20140519 64-bit). Certified Ubuntu Server Cloud Image from Canonical.
UUID 0fd57f23-bc80-4bde-8ab2-64acf8a14fe9

What's New in This Release

  • Fix for CVE-2014-0196
  • Added kernel tuning for vm.dirty_background_bytes. This causees dirty data to be flushed at 100 Mbytes for improved performance.

Packages Installed in This Image

For a detailed list of every package installed with this image, click here.

12.04 20140408

Name base
base64
Description Ubuntu 12.04.4 LTS (20140408 64-bit). Certified Ubuntu Server Cloud Image from Canonical.
UUID fe5aa6c0-0f09-4b1f-9bad-83e453bb74f3

What's New in This Release

  • Updated OpenSSL to address HeartBleed bug (openssl 1.0.1-4ubuntu5.12)

Packages Installed in This Image

For a detailed list of every package installed with this image, click here.

12.04 20140227

Name ubuntu-certified-12.04
Description Ubuntu 12.04.4 LTS (20140227 64-bit). Certified Ubuntu Server Cloud Image from Canonical.
UUID e28711b3-7f9c-47a7-be7f-ce07e9a99394

What's New in This Image

  • Resolved an issue where ssh host keys are not generated when instance is provisioned with one interface.
  • Resolved an issue where the hostid command always returns "00000000" rather than a unique value.
  • Resolved an issue where the sudo command produces a "unable to resolve host.." warning.
  • Ubuntu 12.04 LTS Release Notes

Packages Installed in This Image

For a detailed list of every package installed with this image, click here.

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.