Maas+juju+conjure-up fully automated deployment of OpenStack

Maas and JuJu are Ubuntu products, recently want to play OpenStack, see if you can deploy an experimental environment, although finally found that Maas and juju pattern is very useful but the official documents to the thing is too little, here I do not list the specific installation steps, I can only say that the installation steps are simply too simple and do not require very complicated documentation at all.

The combination of Maas and juju with Conjure-up is really powerful, really powerful, and I know that KVM can be a great shock to the heat transfer. Deploying OpenStack

Next, simply explain the deployment of the production environment (the test environment deployed to a machine is relatively simple, the following will be mentioned briefly) hardware preparation Router 1 with NAT function, you can isolate the network switch, depending on how many of your machine's at least 4 servers, According to OpenStack requirements, the compute node is the Nova need at least two network cards, and Storage node (cinder) need at least one NIC, the server generally has IPMI function, if not, I recommend you change the server, reason, and so on explained. Network cable Some ordinary computer one, pre-installed Linux system topology map

This is a very important content, the usual, not explained first, the first picture, the latter will be slowly explained.

CSDN's blog is not very familiar with, I wrote this first, and later changed into a true map

switcher_a->internet (fixed IP)
switcher_b->router (172.16.0.0/24)-lan
Router (172.16.0.0/24)-wan-> Internet

Server ctl-eth0->switcher_a server
ctl-eth1->switcher_b

server ctl-maas-controller-eth0-> Switcher_b Physical server 1-eth0->switcher_a physical server
1-eth1->switcher_b

physical server 2-eth0->switcher_a
Physical server 2-eth1->switcher_b

physical server 3-eth0->switcher_a
physical server 3-eth1->switcher_b

normal pc Switcher_b

Installing Maas

First find a machine to deploy an Ubuntu server and deploy Maas, but this way I am not very recommended, ha ha ha.

I recommend virtualization processing, so I do this, first to the server CTL installation OpenSuse42.3, choose Btrfs File system as the root file system, mainly because btrfs+snapper (in fact, there are Snapper management functions in YaST), In the text mode is really powerful to explode, is simply to the operating system installed a git system, can be back at any time and compare snapshot between the different points.

You can then install the virtualization component in YaST or use the Zypper installation, which is not the specifics, but the system can deploy the virtual machine.

This allows you to install virtual machine manage using a normal computer to remotely manage the VMS on the server CTL.

maas-controller only need to link to a network, to create a virtual machine when the attention.

For installation, see the official documentation for MAAS. Note Before you install Maas, turn off DHCP on router and configure the good one fixed IP. When installing Maas, make sure you can surf the net normally, a bit of nonsense meaning ^_^

MAAS configuration, there is only one focus, MAAS contains the DNS service, so need to put this part of the small pit

Small pits too much, I have so many suggestions, the document Maas FAQ to see more, for example, the installation of Maas when the magic found to change the IP address can not be normal use, there are two ways to solve, first, look at the Maas of the FAQ, second, the machine is configured to install Maas Tai Hang

The big pit is really too big, completely did not speak the network topology structure, does not know how to play, how to start. The official document says two dedicated switches are needed, and I infer the network topology based on this. If you respond enthusiastically, I will write another article explaining it.

Keep talking about the pit. DNS

The first is DNS, and later found in the use of conjure-up, DNS is very critical, must have the correct positive and negative check function. First of all to ensure that the Maas DNS configuration is correct, my method is to find a normal computer (go to a name TESTC), connect the network cable, first see Maas DHCP service is normal, here by the way, it is highly recommended to use the Maas DHCP function, without, PXE, deployment is trouble. If all goes well under Maas's DNS page, you will find TESTC, and then ping the host name of TESTC or nslookup on this computer. If the IP cannot be queried, go back to the various checks, such as the DNS configuration section under setting, or the DNS server configuration under subnet, and so on.

What is the DNS configuration OK? On the Maas controller computer can access the external network on the Maas controller can nslookup to TESTC on the TESTC can access the extranet on TESTC can nslookup to Maas

It's a bit messy, but it's basically the truth. Please note that sometimes you may need to add a domain name, maas the default domain name is Maas, that is, you may want to go to nslookup Testc.maas can see the results, there are problems here will be prompted to resolve out on it.

Why the DNS is a big hole, because, I encountered in the deployment process of most of the problems are caused by DNS, the leading Ah, cattle ah. Please resolve the DNS issue. MAAS, JUJU and conjure-up

Everyone, OpenStack needs a bit of basic knowledge and must look more. In addition OpenStack is actually a very good learning project, and OpenStack uses a lot of very advanced methods that are worth learning.

What is Maas? Just started to see Marvellous, later saw the show tease, Maas is an unattended deployment tool, deploy what. Deploy the operating system, you can deploy a variety of Linux systems, but to avoid trouble, I used the Ubuntu server version directly.

What is JuJu? JuJu is the Orchestration tool, I x, there is not so complicated ah, in my opinion, JuJu is also an unattended deployment tool, deploy what. Deployment Openstack,openstack is still very complex, a variety of services too many, configuration is also a lot, so juju to help you.

What is conjure-up? Believe it or not, the shipment is an unattended deployment tool. Deployment Juju+openstack, look complex, actually quite simple, conjure-up will help install JuJu controller Ah, node these things, while providing a bullish and roaring interface let you go to the Orchestration service, then, conjure-up to help you deploy all, Please note that it is everything, everything.

At first I did not understand the relationship, it is quite passive, and later understand, in fact, things are relatively simple, but also to understand why Ubuntu to write the document so simple, because, really simple, nothing to say. MAAS Recurring restart problem

This is a small pit, just at the beginning, I thought it was a bug, but not, because in the pacified (commissioning) process, this option is allowed to enter SSH and prevent the restart, so it should be Maas deliberately. In fact, after the completion of the pacified Maas will automatically shut down, but I use the server, the server has an IPMI thing, so this thing found shutdown, thought it was a big fault, so to restart, and constantly restart, in fact, as long as the IPMI configuration is OK, I here server is Intel AMT, configuration Well, there's nothing to do, be a quiet Adonis. managing JuJu and OpenStack

Previously said JuJu is an orchestration service, the content of which is OpenStack services, this thing good.

How to manage JuJu. On the conjure-up controller, you can see the login address and password by executing the JuJu GUI. Login to see Openstack-dashboad service, look at the hostname or IP address, the rest of your own brain OpenStack, I here record three keywords, horizon,admin,openstack, ok you guess. Network topology Structure

This thing is a big hole, separately listed to say, Ubuntu JuJu and Maas are not the need for the network structure will be clear, I think it may be because juju and Maas there is no specific requirements, mainly still look at OpenStack network topology requirements.

I think that's the way it should be.

internet<–> firewall <–> External Server <–> intranet <–> internal service cluster

There are many things without screenshots, said the more vague, please forgive me. Think of something and add it.

Removed the Computecapabilitiesfilter