Shulou(Shulou.com)06/01 Report--

The construction of openstack environment involves the following contents

Safety

It mainly includes the passwords used by various services. Here, in order to prevent password confusion, I recommend using the same password (not recommended in production environments).

The host network configuration is shown in the following figure, for reference only

Time synchronization Settings

For controller controller, time synchronization uses the time synchronizer of external network by default.

1) install the time synchronization package and execute the command as follows:

2) Edit / etc/chrony.conf, modify as follows:

3) add the following fields to the / etc/chrony.conf file to allow 10.0.00Universe 24 network segment hosts to synchronize with controller.

4) set time synchronization boot self-startup

For all other nodes

1) install the time synchronization package

2) Edit / etc/chrony.conf, time synchronization requires the use of controller node time synchronizer

3) set time synchronization boot self-start

Openstack package (installed on all nodes)

The minimum installation of centos7.2 is used in the environment, and the system defaults to LVM, while disabling SELINUX, disabling firewalld and iptables, and doing the following on each node of the centos system:

Install the upgrade package. It is recommended to restart the system after the installation is complete.

Install the openstack client package

Install openstack SELINUX, which will replace the system's own SELINUX. Of course, for security reasons, I disable SELINUX for all hosts by default.

Install and configure the SQL database on the controller node host

1) install the relevant software package and execute the command as follows:

2) create an openstack.cnf under / etc/my.cnf.d/, as shown below:

3) set boot self-startup and start the database service

4) initialize the database, enter the following on the command line

The output of the initialization process command is as follows:

NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS 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 will be blank

So you should just press enter here.

Enter current password for root (enter for none): (enter as enter for the first time 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? [Yzone] y (enter y for the second time, and then set the database password)

New password:

Re-enter new password:

Password updated successfully!

Reloading privilege tables..

... Success!

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

To log into MySQL without having to have a user account created for

Them. This is intended only for testing, and to make the installation

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

Production environment.

Remove anonymous users? [YBO] y (the third input is y)

... Success!

Normally, root should only be allowed to connect from 'localhost'. This

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

Disallow root login remotely? [YBO] n (fourth input is n)

... Skipping.

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

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

Before moving into a production environment.

Remove test database and access to it? [YBO] y (the fifth input is y)

-Dropping test database...

... Success!

-Removing privileges on test database...

... Success!

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

Will take effect immediately.

Reload privilege tables now? [YBO] y (sixth input is y)

... Success!

Cleaning up...

Install the NoSQL database (operate on controller nodes only)

1) install the software package and execute the command as follows:

2) Edit / etc/mongod.conf, modify bind_ip to the controller's management IP, that is, 10.0.0.11, and remove the comment symbol in front of the smallfiles=true

The official statement is as follows

The journal directory does not exist by default under the directory / var/lib/mongodb/. When we modify the loaded / etc/mongod.conf directory to remove the annotation symbol before the smallfiles=true, and start the mongod service

The journal directory will be automatically generated under / var/lib/mongodb/

Message queuing service (operates only on controller nodes)

1) install the software package

2) start the message queuing service and set it to start automatically

3) add openstack users

4) Grant read and write permissions to openstack users

Caching service (operates on controller nodes only)

1) install the software package

2) start the caching service and set it to boot automatically

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

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

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.