for the split network case: dynamic range and static range.Carve up your network space into ranges like this:.Set the “Router IP” to the default gateway for this private network.Note: nothing in this form will change the actual NIC configuration in Ubuntu! If needed, configure the IP, subnet mask, broadcast IP.Click the edit symbol for the NIC that’s connected to the private network, that is, the network where all the nodes are and where they will PXE boot from You should see a list of NICs on the machine.Click on the “Clusters” tab and then click on your cluster.Add your SSH key to your user profile by clicking on your login name in the top right corner and selecting “Account”.Let’s continue with the configuration while that download happens. This will take a few minutes, depending on your bandwidth. Go to the Images tab and import disk images for 14.04 LTS (Trusty) 64 bits and 16.04 LTS (Xenial).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 settings tab and change the image download URL in the Boot Images section to and click save.Access the MAAS UI at and follow the instructions to create the administrator, then login with those credentials.Sudo dpkg-reconfigure maas-region-controller Sudo dpkg-reconfigure maas-cluster-controller If you are setting up the split network topology, make sure the MAAS API endpoint is on the private network IP and not the public network:. Install Ubuntu server 14.04 LTS on the machine you want to use for MAAS. This is how the MAAS server should be installed: Otherwise you need to manually register it via the MAAS 1.9 API and this is not covered in this post. MAAS will then automatically know about it. 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 only manages the private network, for which it will setup DNS and DHCP, but it helps if it knows about the public one. Here we trick the system and simply say the public and private networks are the same and connect both NICs to it: The flat network model is the most basic one. 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. Keep in mind that OpenStack floating IPs will always come from the public network. We’ll call them private and public networks. In both of these models, at least one node needs to have two network interfaces connected to networks that MAAS knows about. Let’s call them “flat network” and “split network”. There are two basic network layouts that we support. If opening holes in a firewall, be mindful that these addresses may resolve to multiple IPs. MAAS, its nodes and the Autopilot will need to be able to reach the internet, or at least these sites (http and https): Version 1.8 is no longer supported for the Autopilot. UPDATE: this post was updated on November 1st, 2016, to support MAAS version 1.9. This article will show two such network layouts that lead to a successful Autopilot run. It requires an existing MAAS 1.9 server and a certain network layout. The Ubuntu OpenStack Autopilot deploys an OpenStack cloud using Juju, MAAS and Landscape. We welcome you to visit our OpenStack product page to find an Ubuntu OpenStack solution that meets your needs. Canonical has sunsetted OpenStack Autopilot and replaced it with conjure-up. Thanks for your interest in Ubuntu OpenStack.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |