Get a production cloud with OpenStack Autopilot

Install OpenStack Autopilot

Canonical’s OpenStack Autopilot handles every aspect of your production cloud across multiple physical machines through installation, expansion and everyday operations.


  • A minimum of 5 machines with the following roles:
    • 1 machine for the MAAS server
    • 1 machine for the OpenStack Autopilot
    • 3 or more machines for the cloud:
      • At least one must have 2 NICs
      • At least 3 must have 2 disks
  • A dedicated switch to create a private cloud LAN
  • Internet access through a router on that LAN

Before you start, you’ll want this eBook

The phase change from traditional, monolithic software to multi-host microservices-based big software demands that you approach the challenge of deployment, integration and operations from a different perspective.

This eBook will give you a deeper understanding into why there is a perceived complexity to the installation and operations of OpenStack and how tools like Canonical’s conjure-up and OpenStack Autopilot can help you build a modern, scalable, repeatable and affordable private cloud infrastructure.

  • All information provided will be handled in accordance with the Canonical privacy policy.

Installation instructions

  1. Set up your hardware

    Install Ubuntu Server 14.04 LTS on the machine designated to be the MAAS server.

    You need to setup a private network with all machines plugged in and enough IP addresses available for all physical and virtual machines you plan to run. This network must not have a DHCP server: MAAS will fill in that role.

    For the simplest topology, connect the second NIC of the dual-nic machine(s) to the same network.

  2. Add required repositories

    From the command line type the commands below and follow the step-by-step instructions:

  3. Install MAAS

    To install MAAS, start off on your Ubuntu Server 14.04 LTS machine and type the command below following the step-by-step instructions:

    • Create your admin credentials by typing:

    • Login to the MAAS UI at http://<maas.ip>/MAAS/
    • Go to the settings tab and change the image download URL in the Boot Images section to and click save
    • Still in the settings tab, insert an upstream DNS server if needed and then click on the save button for that form
    • Go to the “Images” tab and import disk images for both “14.04 LTS amd64” and “16.04 LTS amd64”. This will take a few minutes, depending on your bandwidth. Let’s continue with the configuration while that download happens
    • In your MAAS user’s settings (top-right corner) add your personal public SSH key so you can later log into the nodes
  4. Configure the MAAS cluster

    • Go to the “Clusters” tab, open the “Cluster master” link, hover over the row for the interface that is connected to the private network and select the edit icon (looks like a pencil — )
      • Set this interface to manage DHCP and DNS
      • Set the “Router IP” to the default gateway
    • Fill in details for the dynamic and static ranges, remembering to leave gaps for the floating IPs
      • Dynamic range — reserve 60 IPs plus total number of NICs connected to the network in MAAS
      • Static range — reserve 20 IPs plus total number of machines in MAAS
      • Floating IP range — that has as many IPs as instances that you’ll want to have in your cloud. This is not a MAAS configuration, but you should leave room for them
      • Save the changes and go back to the Images tab and wait for the image download to be finished. Once that is done, proceed to the next step
  5. Register your hardware with MAAS

    Now you need to enlist and commission machines:

    • Ensure all machines are set to PXE boot, if possible disable all other boot options, including local disk, in the BIOS
    • Power the machines on so they will all appear in the “Nodes” tab of MAAS
    • Edit each machine filling in the power type and parameters
    • Select all the machines and, using the “Take action” dropdown, “Commission” them
    • Wait until all machines have a “Ready” status
    • Verify the networking by going to the details page for the node(s) that have multiple NICs and check that the second NIC:
      • Is connected to the subnet
      • Has the “IP address” field set to “unconfigured”
    • The first NIC should be the same except the IP address field will be set to “Auto assign”
  6. Launch OpenStack Autopilot

    Setup Landscape and launch the OpenStack Autopilot with the following commands:

    • Replace <hostname> above with the hostname of the machine that was selected for the Autopilot role
    • Choose the “Landscape OpenStack Autopilot” option
    • Create a new OpenStack Password
    • Fill in your:
      • Admin email address
      • Admin name
      • MAAS server IP
      • MAAS user API key — found in your user’s settings (top-right corner)
    • When everything is installed, you will be given a link
    • Open that link to access the Landscape UI
    • Login with your admin email and OpenStack password
  7. Review your checklist

    At the bottom of the setup page there is a checklist with the status of all of your resources. These should all be green, if it isn’t follow the instructions to resolve

  8. Choose your OpenStack components

  9. Select the hardware on which to deploy the cloud

  10. Select “Install” to start building your cloud

  11. Create an OpenStack account to access your Horizon dashboard

  12. Monitor your region and scale out

To setup MAAS 1.9 with different network topologies read MAAS 1.9 network layouts for the Landscape Autopilot.

Need more help?

Let our cloud experts help you take the next step.

Contact us ›

Already a Landscape Dedicated Server customer? Upgrading is simple, see the instructions in the release notes.