Use fuel to install OpenStack Juno two-Mount OpenStack

Source: Internet
Author: User

Well, we've already installed fuel master, and now we're ready to install OpenStack, so you can see the OpenStack main interface when the installation is complete.

Continue yesterday, we went into the fuel UI and then "new OpenStack Environment" to create the OpenStack deployment environment.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_165243.png "alt=" Wkiom1s8vwxxb7zdaahjlroty4u284.jpg "/>

Give us a name for our deployment environment, I call it "DEMO", OpenStack supports CentOS 6.5 and Ubuntu 12.04.42 versions, we choose CentOS, I personally like Redhat, familiar with it. 6.0 is the Juno version, if you want to deploy Havana, then you have to download 5.1.1, next

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_165258.png "alt=" Wkiol1s8v9jw8p2naahc8mlq80c043.jpg "/>

OpenStack deployment environment has two, one is HA Multi-node, this mode is to support the control node ha, at least three control nodes, why not two nodes, this is because two nodes prone to brain fissure, here is not particularly explained, the attack interested in their own Google.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_165312.png "alt=" Wkiom1s8vwwrp0fbaagbekfqo0c354.jpg "/>

Because I have limited resources here, choose the second, on the node mode, this mode is not control node ha, the actual environment we still deploy the first HA mode, I will create two virtual machines here: Controller and COMPUTE

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_165414.png "alt=" Wkiol1s8v9iikf0aaafn1d7jhoo508.jpg "/>

Here because we run on the virtual machine, so choose Qemu, this is a simulator, running slow, production environment to choose KVM, if used to manage VMware environment, select Vcenter, management vmware must pass vcenter, this is the rules of VMware What else does VMware sell, but OpenStack's bottom-level hypervisor also supports ESXi, and is interested in doing it on its own.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_165428.png "alt=" Wkiom1s8vwbynqghaafyof-yoig810.jpg "/>

The OpenStack network is very responsible, refers to the specialized research, here does not say much, the default chooses the VLAN pattern enough.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_165455.png "alt=" Wkiol1s8v9jrticcaaknzwmy9fa274.jpg "/>

I choose the default here, that is, the block storage and mirroring are local, so the local disk of the compute node is best to be larger. Actual production environment everyone according to their own environment choice, Cinder can use iSCSI, I here default

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_165531.png "alt=" Wkiom1s8vwayvn99aagllchzhz4778.jpg "/>

I do not need here, interested can study the Ceilometer this billing system, but he needs a separate database node, I do not choose three.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_165552.png "alt=" Wkiol1s8v9mafrt6aagzfzmpstk225.jpg "/>

All right, it's done.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_165600.png "alt=" Wkiom1s8vwfceu_iaaezhrlllzy272.jpg "/>

This is where we created the "demo" Environment, and after creating this environment, you know what it is, and it defines the various functional components and patterns that we deploy OpenStack.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_165614.png "alt=" Wkiom1s8vwnsdp8xaanadd4_amm244.jpg "/>

The next step is to formally deploy OpenStack, so we need to prepare two virtual machines, with the controller as an example. Open VirtualBox, click "New", Name "Controller", type select "Linux", "Redhat x64", Next

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_183738.png "alt=" Wkiol1s8v93clucpaailx4ii6mg224.jpg "/>

I temporarily zoned 1G memory for two virtual machines

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_183753.png "alt=" Wkiom1s8vwrgg45baadg0ysq31i673.jpg "/>

Now create

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_183802.png "alt=" Wkiol1s8v92hotquaafydy6zptk421.jpg "/>

Select VDI

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_183811.png "alt=" Wkiom1s8vwuhbp_paafcpcvugd8399.jpg "/>

Dynamic allocation, space saving, real environment recommended select "Fixed size"

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_183819.png "alt=" Wkiol1s8v-gjygeqaafa8yvelcu544.jpg "/>

Space should not be less than 40G suggestions, compute node recommended to more, if need to use cinder words

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_183843.png "alt=" Wkiom1s8vw-sg7_saaef_np9jjq230.jpg "/>

Create a good virtual machine

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_183857.png "alt=" Wkiol1s8v-od9w1laakqbujryzo711.jpg "/>

Right-click Create a good virtual machine, select settings, clicking the System, the floppy drive can be removed, because OpenStack through the PXE boot installation so it is important to check the network here, to ensure that the virtual machine can PXE boot.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_183920.png "alt=" Wkiom1s8vxgtibavaahht8q85_0609.jpg "/>

Network card settings and fuel Master general, here do not repeat, the network planning see the previous blog post.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_183951.png "alt=" Wkiol1s8v-sqlxfzaahaok3p8ne803.jpg "/>

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_184011.png "alt=" Wkiom1s8vxoa-wo4aahwuvogbmq456.jpg "/>

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_184030.png "alt=" Wkiol1s8v-ba_3edaahhs7lic5q443.jpg "/>

According to the controller also create compute virtual machine, you can clone one, the same configuration. Of course, this memory needs to jump large, because the subsequent creation of the cloud host to ensure that there is sufficient memory, I am here to create a virtual machine, temporarily 1G of memory, we know this.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_184258.png "alt=" Wkiol1s8v-fsg-qgaakyedl80gc558.jpg "/>

Virtual machine created, let's take a look at the "network", we are useful is "public" and "management", where the public network can be assigned to the cloud host floating IP, the other IP segments in the future to create a cloud host can be back to see.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_184340.png "alt=" Wkiom1s8vxbxkalvaano_khp8us608.jpg "/>

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_184358.png "alt=" Wkiom1s8vxfc5m7caad_jpvkpe0749.jpg "/>

Here is a network verification, in the construction set their own network, it is best to click here to verify, confirm the network OK and then start to build the environment.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_184411.png "alt=" Wkiol1s8v-rz9kzuaahkefc1nso081.jpg "/>

The content in "settings" is what we defined when we created the sub-environment.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_184444.png "alt=" Wkiom1s8vxjshg5eaakvsxqsrn0908.jpg "/>

The "Log" role is obvious, in the course of your installation if you encounter errors, you can go here to further analysis

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_184453.png "alt=" Wkiol1s8v-3xymwzaan5gq9ketq790.jpg "/>

This is the strength of fuel, can be deployed to complete the OpenStack environment "Health Check", of course, generally not 100% pass, but you see the error point is not related to your actual deployment environment, no deployment, can be ignored.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_184512.png "alt=" Wkiom1s8vx6acaycaalxdwx5fvi177.jpg "/>

"Action" This is very simple, you can rename the sub-environment name, you can delete the environment, re-build.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_184524.png "alt=" Wkiol1s8v_kceuzcaao80fsw9ne009.jpg "/>

OK, the crap is over, then we started to start, the first two virtual machines, the premise is to confirm the network configuration before the problem. If the virtual machine is turned on, because the local disk is empty, the disc does not load the mirror, so it is automatically booted from the PXE network.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_184627.png "alt=" Wkiol1s8v_pdwsfuaagg4kfives595.jpg "/>

We don't have to do anything, the default is automatically started from "Bootstrap"

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_184735.png "alt=" Wkiom1s8vyhzarupaagz5_na-ti305.jpg "/>

The process of starting

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_184820.png "alt=" Wkiom1s8v4rgazs1aak8bz9d1rw802.jpg "/>

The boot is done, OH.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_185053.png "alt=" Wkiol1s8wf2bsk-xaajzn3oqsgw125.jpg "/>

This is back to the fuel UI interface, you can see there are two reminders in the upper right corner

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_185101.png "alt=" Wkiom1s8v4rzjszeaabkcuwvoz0669.jpg "/>

Click to expand to see that master has discovered two hosts

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_185134.png "alt=" Wkiol1s8wf7wxzsdaagnawuwq_y736.jpg "/>

In the upper-right corner, click Add Node

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_185147.png "alt=" Wkiom1s8v42axhpyaaprbhcnxxu185.jpg "/>

We can see "Assigning roles", which is our role in creating virtual machines, which are commonly used by controllers and compute

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_185223.png "alt=" Wkiol1s8wggqda8xaamor2adpns180.jpg "/>

So now look at how to separate virtual machines and how to assign roles to virtual machines. How do we differentiate between controller and compute, MAC address, display case, the local disk may be the same, the memory may be the same, then the only accurate method or indication is the MAC address, such as in this case, 26:D3 and 7d:3a, Turn on the PXE boot MAC address of the virtual machine settings network, so you can be sure 26:d3 this is the controller.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_185350.png "alt=" Wkiol1s8wglcru6zaalqucijpqg643.jpg "/>

We select 26:d3, then select "Controller" for "Assign role", confirm that there is no problem, then click "Apply Changes" in the upper right corner.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_185426.png "alt=" Wkiom1s8v4_x_awoaaplgkwpx3g881.jpg "/>

Then go back to "node" and you can see the situation as

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_185439.png "alt=" Wkiol1s8wgtxo6p3aaqpw05jrgy363.jpg "/>

And then follow the same method as above to select the COMPUTE node

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_185511.png "alt=" Wkiom1s8v5gtpgeyaakytfb5pec599.jpg "/>

Then go back to the confirmation page, this is our selection, time environment, may just confirm controller and cinder and other special nodes, because the compute node too many, so to exclude the previous node, all selected can

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_185528.png "alt=" Wkiol1s8wgwixdmeaangxyb3b38991.jpg "/>

Then we have to adjust the network selection of each host, which can also be followed by the completion of the deployment after the change, then select the settings of the node icon, pop up the following popup window, click Network Configuration

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_185625.png "alt=" Wkiom1s8v5laoaasaafldrahcmc628.jpg "/>

The default is the following assignment

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_185634.png "alt=" Wkiom1s8v5srrcrraanssiywecc473.jpg "/>

We need to assign the network and interface as follows, the Admin network can not be changed, stored in this case does not matter, the use of other networks have been introduced before, no longer repeat

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_190241.png "alt=" Wkiol1s8wgjzxe-zaam8quljttq599.jpg "/>

So, all settings are already configured OK, then click "Deploy Change" in the upper right corner

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_190325.png "alt=" Wkiol1s8wgmcbp3gaaodh2gh2da929.jpg "/>

Next look at the settings and start deploying

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_190458.png "alt=" Wkiom1s8v5ews6znaaetxhuear4909.jpg "/>

Take a look at the two nodes that have started to install CentOS at the same time, ready for the OpenStack environment

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_190528.png "alt=" Wkiol1s8wgvzxbicaarmoulnquu864.jpg "/>

Take a look at the installation process of two nodes, this process does not need you to do anything, need to wait, in fact, the process is very long, especially the experimental environment, because we have limited resources, the actual environment is very fast

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_190550.png "alt=" Wkiom1s8v5mjeyjvaamfaacelp8553.jpg "/>

299 packages are actually installed

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-18_191423.png "alt=" Wkiol1s8wgyzbbqsaai7zbo7szw876.jpg "/>

Sorry, just dropped a verification of the network process, of course, this is not a must process, optional, but the recommendation is that network settings OK, everyone in the "network" here, the bottom left to do a verification, the correct words, such as under, there are errors, the best before the installation to solve.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-19_131248.png "alt=" Wkiom1s8v5rxcvysaaetuezpays613.jpg "/>

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-19_131303.png "alt=" Wkiol1s8wg3xwoikaagfd9w_shu163.jpg "/>

All right, CentOS is all set up, so be aware that CentOS is installed at the same time.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-19_133120.png "alt=" Wkiom1s8v5vru0apaalmq9j-siy851.jpg "/>

CentOS Installation Completed interface

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-19_133134.png "alt=" Wkiol1s8wg6y9xfxaade4lz8z00509.jpg "/>

The next step is to install the OpenStack components, which are installed on a per-station basis, so here will be more time-consuming, you can rest

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-19_133449.png "alt=" Wkiom1s8v5ysuqjyaamnrhtaw3q243.jpg "/>

Install another one

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-19_142219.png "alt=" Wkiom1s8v57ilnqsaamzcz0x72w731.jpg "/>

Time is still long, finally installed OK, if the configuration is high physical machine, in fact, is quite fast.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-19_143409.png "alt=" Wkiol1s8whlw8ljaaamijagvfbs466.jpg "/>

Do not panic after installation, wait for the following success appear to be done. According to our environment, is a public network, the other is a private network, it is recommended to use the public address to access the UI, because the private network address is not able to use VNC to open the cloud host

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-19_144124.png "alt=" Wkiom1s8v6gcfcj6aap9zzi51ru123.jpg "/>

Open the browser, enter, the following login screen appears, user name password is admin, the general appearance of this screen shows that OpenStack installation is no problem. I have a cookie problem here, I can't log in, restart my browser, and log in again.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-19_144324.png "alt=" Wkiol1s8whsb6-4kaadij3vv5gs455.jpg "/>

This is the landing after the screen, the content will not be introduced.

650) this.width=650; "src=" "style=" float: none; "title=" 2015-01-19_144933.png "alt=" Wkiol1s8whwwwcypaak4pusls2a817.jpg "/>

Well, OpenStack is already installed, and next we'll show you how to mount volume and base usage if you use OpenStack to create a cloud host.

This article is from the "Heavenly Soul Eternal" blog, please be sure to keep this source

Use fuel to install OpenStack Juno two-Mount OpenStack

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.