1. Deploy OpenStack with Ubuntu Autopilot
Taylor Chien

2. Contents OpenStack Overview Autopilot Overview MAAS Overview
What Happened
The Setup
Installation Process
Conclusion

3. Open, scalable hypervisor
OpenStack Overview
Open, scalable hypervisor

4. OpenStack Open, free, massively scalable hypervisor Open source
Extremely modular and scalable
Autopilot
Automated deployment of pre-made Ubuntu Server with OpenStack

5. Metal as a Service by Canonical
MAAS
Metal as a Service by Canonical

6. MAAS Manages physical servers Inventory Installation Disk Erasure
Changing power state
Easy control of hardware using the LOM interface of a server
Different OSes have different versions
Ubuntu LTS, MAAS 1.9
Ubuntu LTS, MAAS 2.0

7. An exercise in futility
What Happened?
An exercise in futility

8. Installation Process Step 1: Prepare Hardware
Enable IPMI interface and assign a static IP
Enable VT-d
Enable PXE boot
Enable second SATA port
Disable all other boot options
Step 1: Prepare Hardware
Step 2: Add repositories
Step 3: Install MAAS
Step 4: Configure the MAAS Cluster
Step 5: Register your hardware with MAAS
Step 6: Launch OpenStack Autopilot

9. Installation Process Step 4: Configure the MAAS Cluster A few issues
Old IP stuck in configuration
IP addresses permanently reserved
Step 1: Prepare Hardware
Step 2: Add repositories
Step 3: Install MAAS
Step 4: Configure the MAAS Cluster
Step 5: Register your hardware with MAAS
Step 6: Launch OpenStack Autopilot

10. Installation Process Step 5: Register your hardware with MAAS
A lot of issues
RAID and LVM are currently broken
mDNS scripts do not sanitize input
mDNS did not delete removed servers
Image had a broken Commissioning script
Step 1: Prepare Hardware
Step 2: Add repositories
Step 3: Install MAAS
Step 4: Configure the MAAS Cluster
Step 5: Register your hardware with MAAS
Step 6: Launch OpenStack Autopilot

11. Installation Process Step 6: Launch OpenStack Autopilot Big issue
Autopilot is not yet available for Ubuntu 16
Juju version 2, needs version 1
MAAS only uses version 2
Step 1: Prepare Hardware
Step 2: Add repositories
Step 3: Install MAAS
Step 4: Configure the MAAS Cluster
Step 5: Register your hardware with MAAS
Step 6: Launch OpenStack Autopilot

12. Conclusion Ubuntu Autopilot on Ubuntu 16 is still in development
Ubuntu MAAS 2.0 is still in development
Juju version 2 is still in development
All need time to mature before working properly

13. Questions
And hopefully answers

14. The Setup Server Name Hardware Purpose CPU Cores RAM (GB) HDD Qty.
HDD (GB)
Ethernet
Totals 16 28 15
2811
Cisco 2811
Router - 1
2960X
Cisco 2960X
Switch
-24
Enterprise
Dell PowerEdge 860
MAAS Region Controller 2 4
750
Yorktown
MAAS Node
Saratoga
MAAS Node (Broken)
Oriskany
Essex
Wasp
dim5150-1
Dell Dimension 5150
MAAS Test Node
160
dim5150-2

15. OpenStack Deployment Model
Three main types of nodes
Controller
Compute
Storage
Alternate nodes
Management Controller
Network

16. MAAS and Juju Juju manages Charms MAAS deploys images
Juju create interactions between different Charms
Different versions
Ubuntu LTS: version 1
Ubuntu LTS: version 2
Version 2 is still in testing

17. OpenStack Deployment Model
Three ways to deploy OpenStack
Single node with all services
Multiple nodes with static services
Multiple nodes with dynamic services

18. MAAS on Ubuntu 14.04 Critical Issue: Broken commissioning image
Caused an internal 500 error when attempting to read allocation data
Metadata was never received, so servers never existed
Servers to be permanently stuck in “New”

19. Image: 500 Error

20. Image: Deletion Error

21. Comparison between Hypervisors
Microsoft Hyper-V (Generation 2)
Pros: Simple, available on all Windows 8 and Server 2008 R2 OSes and newer, supports advanced Windows features
Cons: No interactive web GUI, no template system, no hardware passthrough
Conclusion: Hyper-V is great for desktop virtualization, but not for the massive scale and distribution of OpenStack
ProxMox VE (4.3)
Pros: Simple installation and setup, easy-to-use web GUI, intuitive menu navigation
Cons: HA is difficult to set up, and requires the command line
Conclusion: ProxMox is excellent for single servers and small environments, but any more and each server added takes the same amount of time to install and link to the HA cluster

22. Comparison between Hypervisors
XenServer (7)
Pros: Easy-to-use client, simple cluster creation and management, easy storage configuration
Cons: Client is Windows only, no web GUI
Conclusion: XenServer is the closest to OpenStack’s scalability with MAAS’s hardware control through IPMI. However, it still needs to be installed in the same way as ProxMox, extending its time to deploy.
OpenStack (Newton)
Pros: Easily scalable and highly flexible, can run on most operating systems (even Solaris and AIX)
Cons: Deployment is complex, web GUI can be difficult to navigate
Conclusion: The easiest to deploy with a service like MAAS, but the most complex to set up by hand

23. Ubuntu Autopilot Uses MAAS to deploy OpenStack using Juju Charms
Promoted as “Build your own Cloud”
*Only available with Juju version 1