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

[n] openstack-- Computing Service nova (5)

I. introduction to 1.1nova, the nova computing service of OpenStack

Nova is one of the first two modules of openstack, and the other is object storage swift. In the openstack system, one is called a computing node, and the other is called a control node. This is mainly related to nova. We install it as the compute node nova-compute and call it the control node except nova-compute. Nova-compute creates a virtual machine, just creates a virtual machine, and all the control is on another machine.

Introduction of Nova components

API: implements the RESTful API function and is the only way to access Nova externally.

Receive external requests and send them to other service components through Message Queue, which is also compatible with EC2 API, so you can also use EC2's management tools to manage nova on a daily basis.

Scheduler: the module is responsible for deciding which host (compute node) the virtual machine is created on in OpenStack.

There are two steps to decide that a virtual machine should be scheduled to a physical node:

Fliter first gets the list of unfiltered hosts and selects the compute node hosts for the service conditions according to the filter attributes.

The calculation weight (Weight) is filtered by the host, so it is necessary to calculate the weight of the host and select the corresponding host according to the policy.

Cert: responsible for identity authentication

Conductor: middleware for computing nodes to access databases

Consoleauth: authorization verification for the console

Novncproxy:VNC Agent

1.2 installation configuration Nova control node 1.2.1 modify configuration file

[root@linux-node1 ~] # vim / etc/nova/nova.conf

Open 3052 enabled_apis=osapi_compute,metadata comments

3649 [api_database]

3661 connection=mysql+pymysql://nova:nova@192.168.56.11/nova_api

4651 [database]

4678connection=mysql+pymysql://nova:nova@192.168.56.11/nova

Transport_url=rabbit://openstack:openstack@192.168.56.11 under default

Open 14 auth_strategy=keystone comment

5429 [keystone_authtoken] add below

5430 auth_uri = http://192.168.56.11:5000

5431 auth_url = http://192.168.56.11:35357

5432 memcached_servers = 192.168.56.11 purl 11211

5433 auth_type = password

5434 project_domain_name = default

5435 user_domain_name = default

5436 project_name = service

5437 username = nova

5438 password = nova

2062 use_neutron=true

3265 firewall_driver = nova.virt.firewall.NoopFirewallDriver

8384 vncserver_listen=0.0.0.0

8396 vncserver_proxyclient_address=192.168.56.11

4813 api_servers= http://192.168.56.11:9292

Open 6705 lock_path=/var/lib/nova/tmp comments

1.2.2 check the configuration file

[root@linux-node1 ~] # grep'^ [a Murz]'/ etc/nova/nova.conf

Auth_strategy=keystone

Use_neutron=True

Enabled_apis=osapi_compute,metadata

Firewall_driver = nova.virt.firewall.NoopFirewallDriver

Connection=mysql+pymysql://nova:nova@192.168.56.11/nova_api

Connection=mysql+pymysql://nova:nova@192.168.56.11/nova

Api_servers= http://192.168.56.11:9292

Auth_uri = http://192.168.56.11:5000

Auth_url = http://192.168.56.11:35357

Memcached_servers = 192.168.56.11 purl 11211

Auth_type = password

Project_domain_name = default

User_domain_name = default

Project_name = service

Username = nova

Password = nova

Lock_path=/var/lib/nova/tmp

Transport_url=rabbit://openstack:openstack@192.168.56.11

Vncserver_listen=0.0.0.0

Vncserver_proxyclient_address=192.168.56.11

1.2.3 synchronizing the database

[root@linux-node1] # su-s / bin/sh-c "nova-manageapi_db sync" nova

[root@linux-node1] # su-s / bin/sh-c "nova-managedb sync" nova

1.2.4 check the database

[root@linux-node1] # mysql-h292.168.56.11-unova-pnova-e "use nova;show tables;"

1.2.5 start Nova

[root@linux-node1 ~] # systemctl enableopenstack-nova-api.service\

Openstack-nova-consoleauth.serviceopenstack-nova-scheduler.service\

Openstack-nova-conductor.service openstack-nova-novncproxy.service

[root@linux-node1 ~] # systemctl startopenstack-nova-api.service\

Openstack-nova-consoleauth.serviceopenstack-nova-scheduler.service\

Openstack-nova-conductor.serviceopenstack-nova-novncproxy.service

1.2.6 Project and endpoint configuration

[root@linux-node1 ~] # openstack service create-- namenova\

Description "OpenStack Compute" compute

[root@linux-node1 ~] # openstack endpoint create-- regionRegionOne\

Compute public http://192.168.56.11:8774/v2.1/%\(tenant_id\)s

[root@linux-node1 ~] # openstack endpoint create-- regionRegionOne\

Compute internal http://192.168.56.11:8774/v2.1/%\(tenant_id\)s

[root@linux-node1 ~] # openstack endpoint create-- regionRegionOne\

Compute admin http://192.168.56.11:8774/v2.1/%\(tenant_id\)s

1.2.7 verify Nova

[root@linux-node1 ~] # openstack host list

1.3 install configuration Nova compute node 1.3.1 modify configuration file

[root@linux-node1 ~] # scp / etc/nova/nova.conf192.168.56.12:/tmp/

[root@linux-node2 ~] # cp / tmp/nova.conf / etc/nova/

[root@linux-node2 ~] # vim / etc/nova/nova.conf

3661connection=mysql+pymysql://nova:nova@192.168.56.11/nova_api

4678connection=mysql+pymysql://nova:nova@192.168.56.11/nova

8394 vncserver_proxyclient_address=192.168.56.12

8413 novncproxy_base_url= http://192.168.56.11:6080/vnc_auto.html

8359 enabled=true

8375 keymap=en-us

5672 virt_type=kvm

Note: the first step is to determine whether the compute node CPU supports virtualization and hardware acceleration.

Egrep-c'(vmx | svm)'/ proc/cpuinfo executes this command to check. If the return value is 1 or greater, it does not need to be modified. If the return value is 0, you must configure libvirt to use QEMU instead of KVM.

3601transport_url=rabbit://openstack:openstack@192.168.56.11

1.3.2 compare Profil

[root@linux-node2 ~] # diff / tmp/nova.conf/etc/nova/nova.conf

3661d3660

< connection=mysql+pymysql://nova:nova@192.168.56.11/nova_api 4678d4676 virt_type=kvm 6469a6468,6477 >

Url = http://192.168.56.11:9696

> auth_url = http://192.168.56.11:35357

> auth_type = password

> project_domain_name = default

> user_domain_name = default

> region_name = RegionOne

> project_name = service

> username = neutron

> password = neutron

>

8361c8369

< #enabled=true --- >

Enabled=true

8377c8385

< #keymap=en-us --- >

Keymap=en-us

8396c8404

< vncserver_proxyclient_address=192.168.56.11 --- >

Vncserver_proxyclient_address=192.168.56.12

8415c8423

Novncproxy_base_url= http://192.168.56.11:6080/vnc_auto.html

1.3.3 start the service

[root@linux-node2~] # systemctl enable libvirtd.service openstack-nova-compute.service

[root@linux-node2~] # systemctl start libvirtd.service openstack-nova-compute.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.