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

Environment: 192.168.205.7: as Chrony, DNS and YUM Source server (self-built yum source for faster installation) 192.168.205.147: as DataBase, install MariaDB, RabbitMQ, Memcached 192.168.205.167: as controller, install keystone, placement, nova, neutron, dashboard 192.168.205.187: as compute node, install neutron agent and nova agent

Note: all operating systems deactivate firewalld,iptable is empty by default, turn off selinux

Version: OS: centos 7 1810 with mini install for controller and SQL server OS: CentOS 7 1511 with mini install for compute node Openstack Minimal deployment for Stein mariadb-10.3.10

Note: other unmarked yum installations

Objective: to minimize the installation of the latest version of openstack stein after the normal running test of each component is completed and successfully set up the real column and run the basic network function steps by running the real test: 1. Environment preparation before installation 2. Install keystone3. Install glance image service 4. Install placement5. Install Nova on controller6. Install Nova on compute node7. Install Neutron on controller node8. Install Neutron on compute node9. Install dashboard10. Verify the preparation of the environment before test installation

The preparation of installation is very important, because there are so many openstack services, the dependencies between services are close, reasonable planning will not lead to installation problems, otherwise there will be all kinds of problems.

The time of all servers in the preparation environment must be the same. We set time service synchronization, which can be an external source or our own time source server. I use a chrony server as a time server, and also do dns parsing and YumSource # yum install chrony#systemctl start chronyd#cat / etc/chrony.conf server 192.168.205.7 iburst#systemctl status chronyd#chronyc sources-v # to check whether the chrony time is synchronized. See that ^ * is synchronized, otherwise the hosts file is not synchronized and the hosts file is copied to the three servers. If dns is used, this step is not necessary, but do not have a hostname. # cat / etc/hosts192.168.205.167 controller1192.168.205.147 master192.168.205.187 node1 uses DNS domain name resolution plan domain name: flex.netname server 192.168.205.7A stack.flex.net 192.168.205.167 controller1A dbs.flex.net 192.168.205.147 database, memcached, rabbitMQ also acts as a forwarding server to install software for yum image editing network card each has three network cards, which are divided into management network, tenant network and external network. The dns for managing the network points to the network for 192.168.205.7eth0 and the network for API # cat ifcfg-eth0NAME= "eth0" DEVICE= "eth0" ONBOOT=yesBOOTPROTO=staticIPADDR=192.168.205.xNETMASK=255.255.255.0TYPE=Etherneteth2 for tenant tenant network use, not IP, set to none#cat ifcfg-eth2NAME= "eth2" DEVICE= "eth2" ONBOOT=yesBOOTPROTO=noneeth3 for public network installation Yum source use, using nat method At the same time, set dns to the dns of the intranet: 192.168.205.7#cat ifcfg-eth3NAME= "eth3" DEVICE= "eth3" ONBOOT=yesBOOTPROTO=staticIPADDR=172.18.18.xNETMASK=255.255.255.0GATEWAY=172.18.18.2DNS1=192.168.205.7 Note: do not modify HWADDR and UUID

To install the source, first enable extras packges. I use the source that came with the original cenos installation, or I can enable the extras source of aliyun or tinghua

# lsbackup CentOS-Base.repo CentOS-Debuginfo.repo CentOS-Media.repo CentOS-Vault.repobackup1 CentOS-CR.repo CentOS-fasttrack.repo CentOS-Sources.repo#yum list Centos-release-OpenStack*... Available Packagescentos-release-openstack-stein.noarch 1-1.el7.centos extrascentos-release-openstack-ocata.noarch 1-2.el7 extrascentos-release-openstack- pike.x86_64 1-1.el7 extrascentos-release-openstack -queens.noarch 1-2.el7.centos extras Note: we need to disable the epel source during installation. We download and install the latest stein source # yum install centos-release-openstack-stein directly through yum.

After the installation is complete, we see some more sources in the directory.

# lsbackup CentOS-Debuginfo.repo CentOS-QEMU-EV.repobackup1 CentOS-fasttrack.repo CentOS-Sources.repoCentOS-Base.repo CentOS-Media.repo CentOS-Storage-common.repoCentOS-Ceph-Nautilus.repo CentOS-NFS-Ganesha-28.repo CentOS-Vault.repo#cat CentOS-OpenStack-stein.repo CentOS-OpenStack-stein.repo... Update package installs openstack client on all nodes # yum upgrade all nodes # yum install python-openstackclient installation database installation database and python component # yum install mariadb mariadb-server python2-PyMySQL establishes the configuration file for the database and writes the following configuration # vi / etc/my.cnf.d/openstack.cnf [mysqld] bind-address = 192.168.205.147default-storage-engine = innodbinnodb_file_per_table = onmax_connections = 4096collation-server = utf8_general_cicharacter-set-server = utf8 allows the system to automatically start the service and start the service when the system boots # systemctl enable mariadb.service# systemctl start mariadb.service runs the mysql_secure_installation script Especially the password of root, assign an appropriate password for root. For demonstration, we set it to root and install the message queue on mysql with the password root123# mysql_secure_installation.

Openstack services use message queues to coordinate operations and status information. Message queues usually run on controller, and openstack supports several message queues such as rabbitMQ, Qpid, ZeroMQ. Most distributions support these specific message queues. In this experiment, we use RabbitMQ because most distributions support it. In this column, our message queue runs in dababase.

The installation package # yum install rabbitmq-server allows the service to start and start automatically when the system boots. # systemctl enable rabbitmq-server.service# systemctl start rabbitmq-server.service adds an openstack user # rabbitmqctl add_user openstack openstack123 allows the openstack user to have write, and read access # rabbitmqctl set_permissions openstack ". * Note: in vhost" / ". Authorize the user "openstack" to install and configure Memcached in the

The identity service authentication mechanism uses Memcached cache tokens, and Memcached usually runs on controller, and for production deployments, we recommend that you enable a combination of firewall, authentication, and encryption to protect it.

Installation package # yum install memcached python-memcached edits the file / etc/sysconfig/memcached and modifies the profile service to use the management IP to allow other nodes to access Memcached#vi / etc/sysconfi/memcachedOPTIONS= through the management IP "- l 127.0.0.1" if you install it on the database server Then change the name of the database server, because parsing has been done in hosts to allow the service to start automatically when the system boots and start the service # systemctl enable memcached.service# systemctl start memcached.service

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.