Openstack-mitaka Basic Environment Introduction

For the OpenStack environment, the following is roughly what is involved

• Safety

Mainly include the use of various services password, here in order to prevent password confusion, I recommend the use of the same password (in production environment, do not recommend this operation)

• Host network configuration for reference learning only

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M02/89/BC/wKiom1ga8VjAIeUMAAErtbd8y2E373.jpg-wh_500x0-wm_3 -wmp_4-s_3494205037.jpg "title=" qq20161103160203.jpg "style=" float:left; "alt=" Wkiom1ga8vjaieumaaertbd8y2e373.jpg-wh_50 "/> Time sync settings

For controller controllers, time synchronization defaults to using an extranet time Synchronizer

1) Install time synchronization package, execute command as follows:

650) this.width=650; "Src=" Http://s5.51cto.com/wyfs02/M01/89/BC/wKiom1ga-bGzKpbHAAAHsaTJENg237.jpg-wh_500x0-wm_3 -wmp_4-s_1171593809.jpg "title=" qq20161103164701.jpg "style=" float:left; "alt=" Wkiom1ga-bgzkpbhaaahsatjeng237.jpg-wh_50 "/>

2) Edit/etc/chrony.conf, modify as follows: 650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M00/89/BA/wKioL1ga_ Dyqdgxqaaa90ql2hfo816.jpg-wh_500x0-wm_3-wmp_4-s_2374390396.jpg "title=" qq20161103165806.jpg "alt=" WKioL1ga_ Dyqdgxqaaa90ql2hfo816.jpg-wh_50 "/>

3) Add the following fields to the/etc/chrony.conf file, allowing the 10.0.00/24 network segment host to synchronize time with the controller

650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M00/89/BA/wKioL1ga_9HSTvIPAAAHI-oCPVs280.jpg-wh_500x0-wm_3 -wmp_4-s_3584510018.jpg "style=" Float:none; "title=" qq20161103171307.jpg "alt=" Wkiol1ga_ 9hstvipaaahi-ocpvs280.jpg-wh_50 "/>

4) Set time synchronization boot from

650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M01/89/BC/wKiom1ga_9LxS3mlAAAQ0LGbmU8482.jpg-wh_500x0-wm_3 -wmp_4-s_3492337335.jpg "style=" Float:none; "title=" qq20161103171327.jpg "alt=" Wkiom1ga_ 9lxs3mlaaaq0lgbmu8482.jpg-wh_50 "/>

For all other nodes

1) Install time synchronization Package

650) this.width=650; "Src=" Http://s2.51cto.com/wyfs02/M01/89/BA/wKioL1gbARKQ64cqAAAHsaTJENg866.jpg-wh_500x0-wm_3 -wmp_4-s_3355754060.jpg "title=" qq20161103164701.jpg "alt=" Wkiol1gbarkq64cqaaahsatjeng866.jpg-wh_50 "/>

2) Edit/etc/chrony.conf, time synchronization requires using controller node time Synchronizer

650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M00/89/BA/wKioL1ga_cGxEtDvAAA8YPavqYM810.jpg-wh_500x0-wm_3 -wmp_4-s_398859919.jpg "title=" qq20161103170443.jpg "alt=" Wkiol1ga_cgxetdvaaa8ypavqym810.jpg-wh_50 "/>

3) Set time synchronization boot from

650) this.width=650; "Src=" Http://s2.51cto.com/wyfs02/M02/89/BD/wKiom1gbAUWzmFa1AAAQ0LGbmU8340.jpg-wh_500x0-wm_3 -wmp_4-s_1495422314.jpg "title=" qq20161103171327.jpg "alt=" Wkiom1gbauwzmfa1aaaq0lgbmu8340.jpg-wh_50 "/>

• OpenStack packages (installed on all nodes)

Using the centos7.2 minimum installation in the environment, the system uses LVM by default, while disabling SELinux, disabling Firewalld, and iptables, on each node of the CentOS system, perform the following actions:

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M00/89/BA/wKioL1ga_pagIN8iAAAJ_-Nbsog799.jpg-wh_500x0-wm_3 -wmp_4-s_1339148506.jpg "style=" Float:none; "title=" qq20161103170558.jpg "alt=" wkiol1ga_pagin8iaaaj_- Nbsog799.jpg-wh_50 "/>

Install the upgrade package and recommend that you restart the system after the installation is complete

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M01/89/BC/wKiom1ga_paQLsM6AAAGOe5UUcw865.jpg-wh_500x0-wm_3 -wmp_4-s_4136009634.jpg "style=" Float:none; "title=" qq20161103170608.jpg "alt=" Wkiom1ga_ Paqlsm6aaagoe5uucw865.jpg-wh_50 "/>

Installing the OpenStack Client package

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M01/89/BA/wKioL1ga_pbRXSCXAAAJq6VEHPs633.jpg-wh_500x0-wm_3 -wmp_4-s_3198066225.jpg "style=" Float:none; "title=" qq20161103170621.jpg "alt=" Wkiol1ga_ Pbrxscxaaajq6vehps633.jpg-wh_50 "/>

With OpenStack SELinux installed, the package will take over the system's own selinux, and of course I am, for security reasons, disable SELinux for all hosts by default

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M02/89/BC/wKiom1ga_pejGZKiAAAJ7aH62K0751.jpg-wh_500x0-wm_3 -wmp_4-s_1136948179.jpg "style=" Float:none; "title=" qq20161103170634.jpg "alt=" Wkiom1ga_ Pejgzkiaaaj7ah62k0751.jpg-wh_50 "/>

• Install the SQL database on the Controller node host and configure it

1) Install the relevant package, execute the command as follows:

650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M00/89/BD/wKiom1gbAkKByfh8AAAODnJ0Y-E049.jpg-wh_500x0-wm_3 -wmp_4-s_242967344.jpg "title=" qq20161103172402.jpg "alt=" Wkiom1gbakkbyfh8aaaodnj0y-e049.jpg-wh_50 "/>

2) Create the openstack.cnf under/etc/my.cnf.d/, with the following details:

650) this.width=650; "Src=" Http://s2.51cto.com/wyfs02/M02/89/BB/wKioL1gbBNLTMBdQAAAxVRKgpZo470.jpg-wh_500x0-wm_3 -wmp_4-s_3974943457.jpg "title=" qq20161103173334.jpg "alt=" Wkiol1gbbnltmbdqaaaxvrkgpzo470.jpg-wh_50 "/>

3) Set the boot up and start the database service

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M00/89/BB/wKioL1gbBUHys6gNAAANkAbHzbk073.jpg-wh_500x0-wm_3 -wmp_4-s_2637686282.jpg "style=" Float:none; "title=" Qq20161103173555.jpg "alt=" Wkiol1gbbuhys6gnaaankabhzbk073.jpg-wh_50 "/>

4) database initialization, enter the following at the command line

650) this.width=650; "Src=" Http://s2.51cto.com/wyfs02/M01/89/BD/wKiom1gbBUGTp6I2AAAJAw5MSWE410.jpg-wh_500x0-wm_3 -wmp_4-s_3535500053.jpg "style=" Float:none; "title=" Qq20161103173613.jpg "alt=" Wkiom1gbbugtp6i2aaajaw5mswe410.jpg-wh_50 "/>

The initialization process command output is as follows:

Note:running all PARTS of this SCRIPT are RECOMMENDED for all MySQL

SERVERS in PRODUCTION use! Please READ each STEP carefully!

In order to log into MySQL to secure it, we'll need the current

Password for the root user. If you ' ve just installed MySQL, and

You haven ' t set the root password yet, the password would be blank,

So, should just press ENTER here.

Enter current password to root (enter for none): (first input as carriage return because there is no password)

OK, successfully used password, moving on ...

Setting The root password ensures that nobody can log into the MySQL

Root user without the proper authorisation.

Set root Password? [y/n] y(second input is Y, then set database password)

New Password:

Re-enter new password:

Password Updated successfully!

Reloading privilege tables.

... success!

By default, a MySQL installation have an anonymous user, allowing anyone

To log into MySQL without has to has a user account created for

them. This was intended only for testing, and the installation

Go a bit smoother. You should remove them before moving into a

Production environment.

Remove anonymous users? [y/n] y(the third input is Y)

... success!

Normally, Root should only is allowed to connect from ' localhost '. This

Ensures that someone cannot guess at the root of password from the network.

Disallow Root login remotely? [y/n] n(fourth time input is N)

... skipping.

By default, MySQL comes with a database named ' test ' that anyone can

Access. This was also intended only for testing, and should be removed

Before moving into a production environment.

Remove test database and access to it? [y/n] y(fifth time input y)

-Dropping test database ...

... success!

-Removing privileges on test database ...

... success!

Reloading the privilege tables would ensure that all changes made so far

would take effect immediately.

Reload privilege tables now? [y/n] y(sixth time input y)

... success!

Cleaning up ...

• Installing a NoSQL database (operation only on controller nodes)

1) Install the package and execute the command as follows:

650) this.width=650; "Src=" Http://s2.51cto.com/wyfs02/M01/89/BB/wKioL1gbB0zguvC-AAAJdUtNiO0453.jpg-wh_500x0-wm_3 -wmp_4-s_1282648766.jpg "title=" qq20161103174522.jpg "alt=" Wkiol1gbb0zguvc-aaajdutnio0453.jpg-wh_50 "/>

2) Edit the/etc/mongod.conf, modify the BIND_IP as the controller's management IP, i.e. 10.0.0.11, and remove the preceding comment symbol from Smallfiles=true

650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M01/89/BB/wKioL1gbB-LSL2zjAAAGpuI-AJQ173.jpg-wh_500x0-wm_3 -wmp_4-s_2735590828.jpg "title=" qq20161103174754.jpg "alt=" Wkiol1gbb-lsl2zjaaagpui-ajq173.jpg-wh_50 "/>

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M02/89/BD/wKiom1gbCLOxyqhUAAAUWGO5oGU838.jpg-wh_500x0-wm_3 -wmp_4-s_948734693.jpg "title=" qq20161103175128.jpg "alt=" Wkiom1gbcloxyqhuaaauwgo5ogu838.jpg-wh_50 "/>

Official statements are as follows

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M01/89/BB/wKioL1gbCPnSzNHnAAAurfRT3lU436.jpg-wh_500x0-wm_3 -wmp_4-s_640647323.jpg "title=" qq20161103175228.jpg "alt=" Wkiol1gbcpnsznhnaaaurfrt3lu436.jpg-wh_50 "/>

Under directory/var/lib/mongodb/, the default is that there is no journal directory, when we modify the download/etc/mongod.conf directory to remove the previous comment symbol Smallfiles=true, and start the Mongod service

650) this.width=650; "Src=" Http://s5.51cto.com/wyfs02/M01/89/BB/wKioL1gbCfmTj8FuAAAOrE5PMGE768.jpg-wh_500x0-wm_3 -wmp_4-s_1934548990.jpg "title=" qq20161103175628.jpg "alt=" Wkiol1gbcfmtj8fuaaaore5pmge768.jpg-wh_50 "/>

It will automatically generate the journal directory under/var/lib/mongodb/.

• Message Queuing Service (operation on Controller node only)
  

1) Install the package

650) this.width=650; "Src=" Http://s5.51cto.com/wyfs02/M02/89/C5/wKiom1gb_LTzTP_wAAAJLY9guH4546.jpg-wh_500x0-wm_3 -wmp_4-s_2622535563.jpg "title=" qq20161104110948.jpg "alt=" Wkiom1gb_ltztp_waaajly9guh4546.jpg-wh_50 "/>

2) Start the Message Queuing service and set it to boot from boot

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M02/89/C2/wKioL1gb_MGCn6UYAAAR-EU06xU658.jpg-wh_500x0-wm_3 -wmp_4-s_2356801934.jpg "title=" qq20161104110958.jpg "alt=" Wkiol1gb_mgcn6uyaaar-eu06xu658.jpg-wh_50 "/>

3) Add OpenStack Users

650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M01/89/C2/wKioL1gb_8vjkqPWAAATxk4YAuE806.png-wh_500x0-wm_3 -wmp_4-s_953773180.png "title=" qq picture 20161104112006.png "alt=" Wkiol1gb_8vjkqpwaaatxk4yaue806.png-wh_50 "/>

4) grant read and write access to OpenStack users;

650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M02/89/C2/wKioL1gcAPKiIdUmAAAVT6L04Hw415.jpg-wh_500x0-wm_3 -wmp_4-s_1426535489.jpg "title=" qq20161104113032.jpg "alt=" Wkiol1gcapkiidumaaavt6l04hw415.jpg-wh_50 "/>

• Caching Service (Operation on Controller node only)

1) Install the package

650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M00/89/C2/wKioL1gcAb2RM_huAAALhlAeukw855.jpg-wh_500x0-wm_3 -wmp_4-s_1999771636.jpg "style=" Float:none; "title=" qq20161104113338.jpg "alt=" wkiol1gcab2rm_ Huaaalhlaeukw855.jpg-wh_50 "/>

2) Start the cache service and set it to boot from startup

650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M01/89/C5/wKiom1gcAb2DTThfAAARfY14bs4733.jpg-wh_500x0-wm_3 -wmp_4-s_602027143.jpg "style=" Float:none; "title=" Qq20161104113348.jpg "alt=" Wkiom1gcab2dtthfaaarfy14bs4733.jpg-wh_50 "/>

The installation configuration of each component will be described later, and more exciting, please look forward to.

Reference http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/environment.html

This article is from the "Zhong blog" blog, make sure to keep this source http://capfzgs.blog.51cto.com/7729146/1869286

Openstack-mitaka Basic Environment Introduction