Thanks for your interest in Ubuntu OpenStack. Canonical has sunsetted OpenStack Autopilot and replaced it with conjure-up. We welcome you to visit our OpenStack product page to find an Ubuntu OpenStack solution that meets your needs.
The Ubuntu OpenStack Autopilot deploys an OpenStack cloud using Juju, MAAS and Landscape. It requires an existing MAAS 1.9 server and a certain network layout. This article will show two such network layouts that lead to a successful Autopilot run.
UPDATE: this post was updated on November 1st, 2016, to support MAAS version 1.9. Version 1.8 is no longer supported for the Autopilot.
MAAS, its nodes and the Autopilot will need to be able to reach the internet, or at least these sites (http and https):
If opening holes in a firewall, be mindful that these addresses may resolve to multiple IPs.
There are two basic network layouts that we support. Let’s call them “flat network” and “split network”. In both of these models, at least one node needs to have two network interfaces connected to networks that MAAS knows about. We’ll call them private and public networks.
Keep in mind that OpenStack floating IPs will always come from the public network.
In the following diagrams, the “cloud” that is above the router does not necessarily mean the Internet directly, just that eventually devices on this network can reach the Internet.
The flat network model is the most basic one. Here we trick the system and simply say the public and private networks are the same and connect both NICs to it:
OpenStack floating IPs will come from the same network as MAAS node IPs in this scenario.
In the split network topology, we have two actual distinct networks:
MAAS only manages the private network, for which it will setup DNS and DHCP, but it helps if it knows about the public one. An easy way to handle that automatically is to just hook up a second NIC to the MAAS machine and connect it to the public network as shown. MAAS will then automatically know about it. Otherwise you need to manually register it via the MAAS 1.9 API and this is not covered in this post.
This is how the MAAS server should be installed:
sudo apt update
sudo apt install maas
sudo dpkg-reconfigure maas-cluster-controller
sudo dpkg-reconfigure maas-region-controller
http://maas.ip/MAAS/and follow the instructions to create the administrator, then login with those credentials
http://images.maas.io/ephemeral-v2/daily/and click save
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.
Let’s verify the networking setup in each node. Click on each node from the Nodes listing page and verify:
For the flat network topology:
For the split network topology, nodes with two NICs will have one connected to the private subnet, but the second NIC will have to be changed.
Click on the “fabric” dropdown menu and select the second fabric:
Click on the “subnet” dropdown and select the public subnet:
Leave the “IP address” unconfigured.
To make sure juju can drive MAAS and provision machines, let’s take it for a spin. It’s best to try it out now and fix any issues before more complex services like the Autopilot make use of it.
On the machine being used to drive the installation, run these commands:
sudo apt-get update
sudo apt-get install juju-core juju-deployer
The remainder of this document will assume that the MAAS Juju environment you just configured is the default one.
For a simple test, we will deploy Ubuntu to all nodes. On the machine that is driving the installation, run these commands:
juju bootstrapthis will use one of the MAAS nodes to bootstrap juju. It will take a few minutes to complete
juju deploy ubuntu -n Ndeploy
ubuntuto all remaining nodes. Replace
Nwith the number of nodes minus one, which was used for the bootstrap above. This command returns after a few seconds, but it just starts the process.
juju status --format=yamlperiodically until everything is started
juju ssh ubuntu/0and
wget http://www.ubuntu.comfrom there
juju destroy-environment $(juju env)
MAAS is setup and ready to be used by the OpenStack Autopilot.
Ubuntu offers all the training, software infrastructure, tools, services and support you need for your public and private clouds.
Stu Miniman and John Boyer of theCUBE interviewed Mark Baker, Field Product Manager, Canonical at the OpenStack Summit in Vancouver. Read on to to find out about OpenStack’s increasing maturity. The Kubernetes and OpenStack story isn’t…
Independent Report highlights the TCO of Canonical’s managed private cloud in a diverse multi-cloud strategy and enterprise infrastructure portfolio 451 Research’s latest report, ‘Busting the myth of private cloud economics ’, found that…
Stu Miniman and John Boyer of theCUBE interviewed Stephan Fabel, Director of Ubuntu Product and Development at the OpenStack Summit in Vancouver. Read on for the full interview, and to hear more on Kubernetes, Kubeflow and MicroK8s.…