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

From the image above, we can see that there is a problem with the instance. The reason for this problem is that the qemu1.5 version in the centos7.3 source is low, so just update the qemu version. The solution is as follows: see https://blog.csdn.net/wjciayf/article/details/73741146

Operate on the compute node:

[root@compute1 ~] # virsh version Compiled against library: libvirt 2.0.0 Using library: libvirt 2.0.0 Using API: QEMU 2.0.0 Running hypervisor: QEMU 1.5.3 [root@compute1 ~] # ls # download qemu software qemu [root@compute1 ~] # cd qemu/ [root@compute1 qemu] # ls libcacard-2.5.2-2.1.el7.x86_64.rpm qemu-kvm-common -ev-2.6.0-28.el7.10.1.x86_64.rpm qemu-img-ev-2.6.0-28.el7.10.1.x86_64.rpm qemu-kvm-ev-2.6.0-28.el7.10.1.x86_64.rpm [root@compute1 qemu] # yum install *-y [root@compute1 qemu] # virsh version Compiled against library: libvirt 2.0.0 Using library: libvirt 2.0 .0 Using API: QEMU 2.0.0 Running hypervisor: QEMU 2.6.0 # you can see that the version has changed from 1.5.3 to 2.6.0 on the control node: restart server1

[root@controller ~] # openstack server stop server1 [root@controller ~] # openstack server list +-+ | ID | Name | Status | Networks | + -+-+ | 5d7c18d4-d9d4-4edf-| server1 | SHUTOFF | provider=172.25.83.10 | | a0b6-0503b31421db | 1 | +- -+-+ [root@controller ~] # openstack server start server1 [root@controller ~] # openstack server list +-+ -+-+ | ID | Name | Status | Networks | +-- +- -+ | 5d7c18d4-d9d4-4edf-| server1 | ACTIVE | provider=172.25.83.10 | | a0b6-0503b31421db | 1 | + + [root@controller ~] # openstack console url show server1 +-+-- + | Field | Value | + -+ | type | novnc | | url | http://controller:6080/vnc_auto.html?token=b022d4aa- | | | | 37ea-459b-a3ff-2049db66333e | +-+-+ access the new url in the browser |

From the image above, we can see that there is a problem with the instance. The solution is as follows: see https://blog.csdn.net/a610616898/article/details/69788360

Operate on the compute node:

[root@compute1 ~] # vim / etc/nova/nova.conf [libvirt] virt_type = qemu cpu_mode = none # newly added [root@compute1 ~] # systemctl restart openstack-nova-compute # after modifying the configuration file, restart the service on the control node: restart server1

[root@controller ~] # openstack server stop server1 [root@controller ~] # openstack server list +-+ | ID | Name | Status | Networks | + -+-+ | 5d7c18d4-d9d4-4edf-| server1 | SHUTOFF | provider=172.25.83.10 | | a0b6-0503b31421db | 1 | +- -+-+ [root@controller ~] # openstack server start server1 [root@controller ~] # openstack server list +-+ -+-+ | ID | Name | Status | Networks | +-- +- -+ | 5d7c18d4-d9d4-4edf-| server1 | ACTIVE | provider=172.25.83.10 | | a0b6-0503b31421db | 1 | + + [root@controller ~] # openstack console url show server1 +-+-+ | Field | Value | | +-+- -+ | type | novnc | | url | http://controller:6080/vnc_auto.html?token=46662814-8a2c-49dd-910a-47e5606a4993 | +-- -- + access the new url in the browser

The above figure indicates that our configuration is successful. Log in as "cirrors" user with "cubswin:)" password

From the figure above, we can see that the ip assigned by server1 is 172.25.83.101.

After successfully logging in to the web interface, we can remotely use ssh to connect without secret.

[root@controller] # ssh cirros@172.25.83.101 The authenticity of host '172.25.83.101 (172.25.83.101)' can't be established. RSA key fingerprint is 1e:bd:0e:10:4c:cb:d5:b5:d2:79:51:91:d9:ed:f3:9c. Are you sure you want to continue connecting (yes/no)? Yes Warning: Permanently added '172.25.83.101' (RSA) to the list of known hosts. $ip a 1: lo:mtu 16436 qdisc noqueue link/loopback 00 scope host valid_lft forever preferred_lft forever 00 brd 00 00 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:94:eb:0a brd ff:ff:ff:ff:ff:ff inet:: 1 inet 127.0.0.1 inet:: 1 scope host valid_lft forever preferred_lft forever 172.25.83.101 scope global eth0 inet6 fe80::f816:3eff:fe94:eb0a/64 scope link valid_lft forever preferred_lft forever 24 brd 172.25.83.255 scope global eth0 inet6 fe80::f816:3eff:fe94:eb0a/64 scope link valid_lft forever preferred_lft forever $ping 172.25.83.2 PING 172.25.83.2 (172.25.83.2): 56 data bytes 64 bytes from 172.25.83.2: seq=0 ttl=64 time=1.136 ms ^ C-- 172.25.83.2 ping statistics-- 1 packets transmitted 1 packets received 0% packet loss round-trip min/avg/max = 1.136 packet loss round-trip min/avg/max 1.136 ms below we create a cloud host server2 [root@controller ~] # openstack server create-- flavor m1.nano-- image cirros-- nic net-id=d8b14128-0eab-4ad2-8f5f-9a7ffd46ed25-- security-group default-- key-name mykey server2 +-- -+-- + | Field | Value | +- -+-- + | OS-DCF:diskConfig | MANUAL | | OS-EXT-AZ:availability_zone | | | OS-EXT-STS:power_state | 0 | | OS-EXT-STS:task_state | scheduling | | OS-EXT-STS:vm_state | building | | | OS-SRV-USG:launched_at | None | | OS-SRV-USG:terminated_at | None | | accessIPv4 | | | accessIPv6 | addresses | adminPass | 3Lme7tei4JDE | | | config_drive | | created | 2019-04-19T09:08:50Z | | flavor | m1.nano (0) | | | hostId | id | 28aa033b-db84-4497-abef-34e6e5c1d949 | | image | cirros (fe68d600-2b20-45de-8391-2d3eecdaca4e) | | key_ | Name | mykey | | name | server2 | | os-extended-volumes:volumes_attached | [] | | progress | | 0 | | project_id | 4bf385a6bf92458194acf7a2faef794b | | properties | security_groups | [{u' " Name': upright default'}] | | status | BUILD | | updated | 2019-04-19T09:08:50Z | | user_id | c058d3e4f37940dc94ee618826e4ef6f | | +-- +-+ [root@controller ~] # openstack server list +-| -+-+ | ID | Name | Status | Networks | +- -- +-+ | 28aa033b-db84-4497-abef-34e6e5c1d949 | server2 | ACTIVE | provider=172.25.83.102 | | 5d7c18d4-d9d4-4edf-a0b6-0503b31421db | server1 | ACTIVE | provider=172.25.83.101 | +- -- +-+ [root@controller ~] # openstack console url show server2 +-+- -Field | Value | +-+- -+ | type | novnc | | url | Http://controller:6080/vnc_auto.html?token=31353e55-4682-4d84-a56a-7fd4364e8b22 | +-+-+ access server2's url in the browser

From the figure above, we can see that the ip assigned by server2 is 172.25.83.102.

After successfully logging in to the web interface, we can remotely use ssh to connect without secret.

# set iptables on the real machine, so that the virtual machine can surf the Internet [root@foundation83] # iptables-t nat-I POSTROUTING-s 172.25.83.0 ssh cirros@172.25.83.102 The authenticity of host 24-j MASQUERADE [root@controller] # ssh cirros@172.25.83.102 The authenticity of host '172.25.83.102 (172.25.83.102)' can't be established. RSA key fingerprint is 54:cb:b0:70:16:0f:d4:f7:77:ab:d8:cd:4c:04:a8:e3. Are you sure you want to continue connecting (yes/no)? Yes Warning: Permanently added '172.25.83.102' (RSA) to the list of known hosts. $ip a 1: lo:mtu 16436 qdisc noqueue link/loopback 00 scope host valid_lft forever preferred_lft forever 00 brd 00 00 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:70:16:1d brd ff:ff:ff:ff:ff:ff inet:: 1 inet 127.0.0.1 inet:: 1 scope host valid_lft forever preferred_lft forever 172.25.83.102 scope global eth0 inet6 fe80::f816:3eff:fe70:161d/64 scope link valid_lft forever preferred_lft forever 24 brd 172.25.83.255 scope global eth0 inet6 fe80::f816:3eff:fe70:161d/64 scope link valid_lft forever preferred_lft forever $ping 172.25.83.101 PING 172.25.83.101 (172.25.83.101): 56 data bytes 64 bytes from 172.25.83.101: seq=0 ttl=64 time=7.321 ms ^ C-- 172.25.83.101 ping statistics-- 1 packets transmitted 1 packets received, 0% packet loss round-trip min/avg/max = 7.321 www.baidu.com ping statistics 7.321 ms PING www.baidu.com (220.181.112.244): 56 data bytes 64 bytes from 220.181.112.244: seq=0 ttl=50 time=24.378 ms 64 bytes from 220.181.112.244: seq=1 ttl=50 time=23.232 ms ^ C-www.baidu.com ping statistics-2 packets transmitted, 2 packets received 0 packet loss round-trip min/avg/max = 23.232Universe 23.805Universe 24.378 ms you can see how many CVMs are enabled on the computing node.

[root@compute1] # virsh list Id Name State-3 instance-00000001 running 4 instance-00000002 running Thank you for reading this article carefully I hope the article "how to install OpenStack in Linux system" shared by the editor will be helpful to you. At the same time, I also hope that you will support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

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.