OPENSTACK-allinone部署 – 馬甲數(shù)據(jù)

<div id="readability-page-1" class="page"><div>
<h2>腦圖</h2>
<p>openstack allinone安裝</p>
<pre><code>1.sudo yum install -y centos-release-openstack-版本名稱

2.sudo yum update -y

3.sudo yum install -y openstack-packstack

4.sudo packstack --allinone
</code></pre>
<p>安裝out:</p>
<pre><code>Testing if puppet apply is finished: 192.168.31.124_controller.pp [ \ ]
192.168.31.124_controller.pp: [ ERROR ]
Applying Puppet manifests [ ERROR ]

ERROR : Error appeared during Puppet run: 192.168.31.124_controller.pp
Error: Command: 'openstack ["volume type", "create", "--format", "shell", ["--property", "volume_backend_name=lvm", "--public", "iscsi"]]' has been running for more than 170 seconds
You will find full trace in log /var/tmp/packstack/20201020-170610-IvtRvk/manifests/192.168.31.124_controller.pp.log
Please check log file /var/tmp/packstack/20201020-170610-IvtRvk/openstack-setup.log for more information

Additional information:

Parameter CONFIG_NEUTRON_L2_AGENT: You have chosen OVN Neutron backend. Note that this backend does not support the VPNaaS or FWaaS services. Geneve will be used as the encapsulation method for tenant networks
A new answerfile was created in: /root/packstack-answers-20201020-170610.txt
Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components.
Warning: NetworkManager is active on 192.168.31.124. OpenStack networking currently does not work on systems that have the Network Manager service enabled.
File /root/keystonerc_admin has been created on OpenStack client host 192.168.31.124. To use the command line tools you need to source the file.
To access the OpenStack Dashboard browse to http://192.168.31.124/dashboard .
Please, find your login credentials stored in the keystonerc_admin in your home directory.
[root@openstack ~]#
</code></pre>
<p>web界面依舊能訪問：</p>
<p>實(shí)例的核心信息

<img decoding="async" src="https://chevereto.mypicbed.top:11443/images/2020/10/20/QQPCRealTimeSpeedup_hEEyrpJGGu.png" alt="QQPCRealTimeSpeedup_hEEyrpJGGu.png"></p>
<p>創(chuàng)建并啟動(dòng)一個(gè)實(shí)例：首先創(chuàng)建1網(wǎng)絡(luò)外網(wǎng)-2路由-3子網(wǎng) 最后在子網(wǎng)里創(chuàng)建實(shí)例：1外網(wǎng)多路由（路由接外網(wǎng)的子網(wǎng)），1路由多子網(wǎng)（子網(wǎng)也是創(chuàng)建一個(gè)網(wǎng)絡(luò))（實(shí)例接子網(wǎng)的子網(wǎng)）。</p>
<p><img decoding="async" src="https://chevereto.mypicbed.top:11443/images/2020/10/21/chrome_j8H9X2JD29.png" alt="chrome_j8H9X2JD29.png"></p>
<p>進(jìn)行實(shí)例管理:實(shí)例可以ping外網(wǎng)班巩，外網(wǎng)可以ping實(shí)例浮動(dòng)ip即實(shí)現(xiàn)網(wǎng)絡(luò)打通</p>
<p><img decoding="async" src="https://chevereto.mypicbed.top:11443/images/2020/10/21/chrome_owpc8m3uu1.png" alt="chrome_owpc8m3uu1.png"></p>
<p>實(shí)例創(chuàng)建一直任務(wù)狀態(tài)調(diào)度中</p>
<pre><code>#查看日志less nova-scheduler.log
ERROR oslo.messaging._drivers.impl_rabbit [req-d5b98d5d-0f56-4db5-9621-18b087ed2140 2d7dc61560294349bb7dd18c7cf22f4b 0b6a88526024451989a0db2e10540c03 - default default] Connection failed: timed out (retrying in 32.0 seconds): timeout: timed out
</code></pre>
<pre><code>[root@openstack nova]# nova service-list
ERROR (CommandError): You must provide a user name/id (via --os-username, --os-user-id, env[OS_USERNAME] or env[OS_USER_ID]) or an auth token (via --os-token).

[root@openstack ~]# ls
anaconda-ks.cfg keystonerc_admin keystonerc_demo packstack-answers-20201020-170610.txt

[root@openstack ~(keystone_admin)]# nova service-list
ERROR (Unauthorized): The request you have made requires authentication. (HTTP 401) (Request-ID: req-d689c064-7dfb-4558-b555-431742127e50)

上傳admin-openrc.sh

[root@openstack ~]# source admin-openrc.sh

[root@openstack ~]# cat /var/tmp/packstack/20201021-203646-W5knO4/manifests/192.168.31.124_ |grep pass
192.168.31.124_compute.pp 192.168.31.124_controller.pp 192.168.31.124_network.pp
192.168.31.124_compute.pp.log 192.168.31.124_controller.pp.log 192.168.31.124_network.pp.log
</code></pre>
<p>網(wǎng)絡(luò)(可選域)-鏡像=》創(chuàng)建實(shí)例</p>
<pre><code>#重復(fù)安裝 packstack --allinone
**** Installation completed successfully ******

Additional information:

Parameter CONFIG_NEUTRON_L2_AGENT: You have choosen OVN neutron backend. Note that this backend does not support LBaaS, VPNaaS or FWaaS services. Geneve will be used as encapsulation method for tenant networks
A new answerfile was created in: /root/packstack-answers-20201021-203647.txt
Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components.
Warning: NetworkManager is active on 192.168.31.124. OpenStack networking currently does not work on systems that have the Network Manager service enabled.
File /root/keystonerc_admin has been created on OpenStack client host 192.168.31.124. To use the command line tools you need to source the file.
To access the OpenStack Dashboard browse to http://192.168.31.124/dashboard .
Please, find your login credentials stored in the keystonerc_admin in your home directory.
Because of the kernel update the host 192.168.31.124 requires reboot.
The installation log file is available at: /var/tmp/packstack/20201021-203646-W5knO4/openstack-setup.log
The generated manifests are available at: /var/tmp/packstack/20201021-203646-W5knO4/manifests

創(chuàng)建鏡像：狀態(tài)一直保存中查看鏡像相關(guān)組件glance日志

2020-10-22 10:38:11.343 3446 ERROR oslo.messaging._drivers.impl_rabbit [req-6d325443-f566-44a1-b7b4-c93722bc2a7f 17200ace134f4aa8aedb672e087f5854 ac65d4c89b0a4d02acd1130dc9386137 - default default] Connection failed: timed out (retrying in 2.0 seconds): timeout: timed out

nova-schedule.log

2020-10-22 10:33:24.786 3768 ERROR oslo.messaging._drivers.impl_rabbit [req-7ab58d8a-de2d-4fc3-804b-6f17fbee7bf7 - - - - -] Connection failed: [Errno 111] ECONNREFUSED (retrying in 14.0 seconds): error: [Errno 111] ECONNREFUSED

創(chuàng)建成功退出用戶重新登錄掩完，鏡像顯示運(yùn)行中

創(chuàng)建實(shí)例一直調(diào)度中

openstack ERROR oslo.messaging._drivers.impl_rabbit Connection failed: timed out

Host mapping not found for host openstack.pukka.cn. Not tracking instance

egrep -c '(vmx|svm)' /proc/cpuinfo 查看0標(biāo)識cpu不支持虛擬化

使用openstack創(chuàng)建實(shí)例時(shí)提示：No valid host was found召廷？

nova hypervisor-list 為空解決

查找nova-api.log沒錯(cuò)

less nova-schedule.log

INFO nova.scheduler.host_manager [req-3f24ed56-f60c-4e71-b40e-86dd0c4612c1 - - - - -] Received a sync request from an unknown host 'openstack.pukka.cn'.

less nova-conductor

ERROR oslo.messaging._drivers.impl_rabbit [req-c7f05020-fd41-41dc-acd1-6a02128ba689 - - - - -] Connection failed: timed out (retrying in 32.0 seconds): timeout: timed out

nova-compute.log

2020-10-22 18:07:20.670 3911 WARNING nova.servicegroup.drivers.db [-] Lost connection to nova-conductor for reporting service status.: MessagingTimeout: Timed out waiting for a reply to message ID 06f3725c34154fe68ddf504534adf7dd
2020-10-22 18:07:20.671 3911 WARNING oslo.service.loopingcall [-] Function 'nova.servicegroup.drivers.db.DbDriver._report_state' run outlasted interval by 50.01 sec
2020-10-22 18:07:45.431 3911 ERROR oslo_service.periodic_task [req-c7f05020-fd41-41dc-acd1-6a02128ba689 - - - - -] Error during ComputeManager._sync_scheduler_instance_info: MessagingTimeout: Timed out waiting for a reply to message ID 7558a0066c9848ee90e443c9c44d4927

less nova-consoleauth.log

2020-10-22 18:02:02.381 1426 ERROR oslo.messaging._drivers.impl_rabbit [-] [2640a29d-a408-45df-b32e-cc670fdf9613] AMQP server on 192.168.31.124:5672 is unreachable: timed out. Trying again in 20 seconds.: timeout: timed out

[root@openstack nova]# ls
nova-api.log nova-compute.log nova-conductor.log nova-consoleauth.log nova-manage.log nova-novncproxy.log nova-placement-api.log nova-scheduler.log

以上nova-*這幾個(gè)服務(wù)之間的依賴關(guān)系弹惦？

nova-api-->conductor-->scheduler-->placement-->compute--->neutron-->cinder-->glance

查看mq狀態(tài)

systemctl status rabbitmq-server.service

解決web界面其他其他機(jī)器無法訪問

編輯rabbitmq.config新增如下配置
{loopback_users, ["admin","guest"]},
{tcp_listeners, [5672]},

重啟mq服務(wù)

</code></pre>
<h2>Nova體系結(jié)構(gòu)</h2>
<p>##這里寫圖片描述</p>
<p><img decoding="async" src="https://chevereto.mypicbed.top:11443/images/2020/10/26/20160707233247115.png" alt="20160707233247115.png"></p>
<h2>實(shí)例創(chuàng)建過程</h2>
<p><img decoding="async" src="https://chevereto.mypicbed.top:11443/images/2020/10/26/openstack.png" alt="openstack.png"></p>
<h2>cinder創(chuàng)建卷過程</h2>
<p><img decoding="async" src="https://chevereto.mypicbed.top:11443/images/2020/10/26/cinder.jpg" alt="cinder.jpg"></p>

<p><img decoding="async" src="https://chevereto.mypicbed.top:11443/images/2020/10/26/1234385-20171007165602677-522246533.png" alt="1234385-20171007165602677-522246533.png"></p>
<h2>Nova主要有API霎挟、Compute柬焕、Conductor审残、Scheduler四個(gè)核心服務(wù)組成，這些服務(wù)之間通過AMQP消息隊(duì)列來進(jìn)行通信斑举。</h2>
<p>Client：Nova Client能夠讓Tenant管理員或用戶終端提交指令搅轿，是Openstack官方為了簡化用戶對RESTful API的使用所提供的API封裝，Client能夠?qū)⒂脩舻恼埱筠D(zhuǎn)換為標(biāo)準(zhǔn)的HTTP請求富玷。</p>
<p>API(nova-api service)：nova-api service能夠接收和響應(yīng)Client的Compute API調(diào)用璧坟，所以API就是Client進(jìn)入Nova的HTTP接口。</p>
<p>Compute(nova-compute service)：nova-compute service是一個(gè)通過hypervisor APIs(虛擬化層API)來實(shí)現(xiàn)創(chuàng)建和終止虛擬機(jī)實(shí)例的守護(hù)進(jìn)程赎懦，Compute通過和VMM的交互來運(yùn)行虛擬機(jī)并管理虛擬機(jī)的生命周期雀鹃。</p>
<p>Scheduler(nova-scheduler service)：nova-scheduler service會從queue中接收一個(gè)虛擬機(jī)實(shí)例的請求，并確定該實(shí)例能夠運(yùn)行在哪一臺Compute server中励两。Scheduler通過讀取數(shù)據(jù)庫的內(nèi)容黎茎，從可用的池中選擇最合適的Compute Node來創(chuàng)建新的虛擬機(jī)實(shí)例。</p>
<p>Conductor(nova-conductor)：nova-conductor module能夠協(xié)調(diào)nova-compute service和database之間的交互当悔，Conductor為數(shù)據(jù)庫訪問提供了一層安全保障傅瞻。</p>
<p>Queue：queue是Nova 服務(wù)組件之間傳遞信息的中心樞紐迁酸。通常使用AMQP(高級消息隊(duì)列協(xié)議Advanced Message Queuing Protocol)的RabbitMQ消息隊(duì)列來實(shí)現(xiàn)。</p>
<p>注意：因?yàn)镾cheduler只能讀取數(shù)據(jù)庫內(nèi)容俭正，和API通過Policy機(jī)制來限制數(shù)據(jù)庫的訪問奸鬓，所以Scheduler和API這兩個(gè)服務(wù)都可以直接訪問數(shù)據(jù)庫。但是支持引入了Conductor服務(wù)之后掸读，更加規(guī)范的方法是通過Conductor服務(wù)來對數(shù)據(jù)庫進(jìn)行操作串远。</p>
<h2>虛擬機(jī)實(shí)例化流程</h2>
<p>Step1：首先用戶執(zhí)行Nova Client提供的用于創(chuàng)建虛擬機(jī)的指令</p>
<p>Step2：nova-api service監(jiān)聽到來自于Nova Client的HTTP請求，并將這些請求轉(zhuǎn)換為AMQP消息之后加入消息隊(duì)列Queue</p>
<p>Step3：通過消息隊(duì)列Queue調(diào)用nova-conductor service</p>
<p>Step4：nova-conductor service從Queue接收到虛擬機(jī)實(shí)例化請求消息后儿惫，進(jìn)行一些準(zhǔn)備工作(EG. 匯總HTTP請求中所需要實(shí)例化的虛擬機(jī)參數(shù))</p>
<p>Step5：nova-conductor service通過Queue告訴nova-scheduler去選擇一個(gè)合適的Compute Node來創(chuàng)建虛擬機(jī)澡罚，此時(shí)nova-scheduler會讀取數(shù)據(jù)庫的內(nèi)容</p>
<p>Step6：nova-conductor從nova-scheduler得到了合適的Compute Node的信息后，在通過Queue來通知nova-compute service實(shí)現(xiàn)虛擬機(jī)的創(chuàng)建</p>
<p>送虛擬機(jī)實(shí)例化的過程可以看出肾请，Nova中最重要的4個(gè)服務(wù)之間的通信都是通過Queue來實(shí)現(xiàn)的留搔。這符合松耦合的實(shí)現(xiàn)方式。</p>
<h2>mq可以打開web界面后重新創(chuàng)建實(shí)例</h2>
<pre><code>#less nova-conductor.log
2020-10-24 11:10:24.809 2988 ERROR oslo.messaging._drivers.impl_rabbit [req-35d2df1c-c27a-4865-bf3d-f6ac197b9707 6f3906719d134f0eaa9a0d79cbc02206 f65dd3ecb37e4cc2995c571df66bd029 - default default] Connection failed: timed out (retrying in 2.0 seconds): timeout: timed out
2020-10-24 11:10:31.818 2988 ERROR oslo.messaging._drivers.impl_rabbit [req-35d2df1c-c27a-4865-bf3d-f6ac197b9707 6f3906719d134f0eaa9a0d79cbc02206 f65dd3ecb37e4cc2995c571df66bd029 - default default] Connection failed: timed out (retrying in 4.0 seconds): timeout: timed out
2020-10-24 11:10:40.829 2988 ERROR oslo.messaging._drivers.impl_rabbit [req-35d2df1c-c27a-4865-bf3d-f6ac197b9707 6f3906719d134f0eaa9a0d79cbc02206 f65dd3ecb37e4cc2995c571df66bd029 - default default] Connection failed: timed out (retrying in 6.0 seconds): timeout: timed out
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager [req-35d2df1c-c27a-4865-bf3d-f6ac197b9707 6f3906719d134f0eaa9a0d79cbc02206 f65dd3ecb37e4cc2995c571df66bd029 - default default] Failed to schedule instances: MessagingTimeout: Timed out waiting for a reply to message ID afcd7c8a06854ceaaa24c388f5fac4aa
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager Traceback (most recent call last):
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager File "/usr/lib/python2.7/site-packages/nova/conductor/manager.py", line 1405, in schedule_and_build_instances
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager instance_uuids, return_alternates=True)
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager File "/usr/lib/python2.7/site-packages/nova/conductor/manager.py", line 832, in _schedule_instances
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager return_alternates=return_alternates)
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager File "/usr/lib/python2.7/site-packages/nova/scheduler/client/query.py", line 42, in select_destinations
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager instance_uuids, return_objects, return_alternates)
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager File "/usr/lib/python2.7/site-packages/nova/scheduler/rpcapi.py", line 160, in select_destinations
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager return cctxt.call(ctxt, 'select_destinations', *msg_args)
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/client.py", line 178, in call
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager retry=self.retry)
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/transport.py", line 128, in _send
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager retry=retry)
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 645, in send
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager call_monitor_timeout, retry=retry)
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 634, in _send
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager call_monitor_timeout)
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 520, in wait
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager message = self.waiters.get(msg_id, timeout=timeout)
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 397, in get
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager 'to message ID %s' % msg_id)
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager MessagingTimeout: Timed out waiting for a reply to message ID afcd7c8a06854ceaaa24c388f5fac4aa
2020-10-24 11:11:51.043 2988 ERROR nova.conductor.manager
2020-10-24 11:11:51.217 2988 WARNING nova.scheduler.utils [req-35d2df1c-c27a-4865-bf3d-f6ac197b9707 6f3906719d134f0eaa9a0d79cbc02206 f65dd3ecb37e4cc2995c571df66bd029 - default default] Failed to compute_task_build_instances: Timed out waiting for a reply to message ID afcd7c8a06854ceaaa24c388f5fac4aa: MessagingTimeout: Timed out waiting for a reply to message ID afcd7c8a06854ceaaa24c388f5fac4aa
2020-10-24 11:11:51.220 2988 WARNING nova.scheduler.utils [req-35d2df1c-c27a-4865-bf3d-f6ac197b9707 6f3906719d134f0eaa9a0d79cbc02206 f65dd3ecb37e4cc2995c571df66bd029 - default default] [instance: 5fbeb69d-8aef-4753-8de1-4f117d609b09] Setting instance to ERROR state.: MessagingTimeout: Timed out waiting for a reply to message ID afcd7c8a06854ceaaa24c388f5fac4aa
2020-10-24 11:11:56.389 2988 ERROR oslo.messaging._drivers.impl_rabbit [req-35d2df1c-c27a-4865-bf3d-f6ac197b9707 6f3906719d134f0eaa9a0d79cbc02206 f65dd3ecb37e4cc2995c571df66bd029 - default default] Connection failed: timed out (retrying in 2.0 seconds): timeout: timed out
2020-10-24 11:12:03.339 2988 INFO oslo_messaging._drivers.amqpdriver [-] No calling threads waiting for msg_id : afcd7c8a06854ceaaa24c388f5fac4aa
</code></pre>
<p>換demo用戶登錄創(chuàng)建實(shí)例</p>
<pre><code>2020-10-21 20:12:57.429 56044 ERROR oslo.messaging._drivers.impl_rabbit [req-f4e293bd-7457-4eea-9c71-49b59c26af43 - - - - -] Connection failed: timed out (retrying in 4.0 seconds): timeout:...skipping...
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 636, in _send
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager raise result
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager NoValidHost_Remote: \u627e\u4e0d\u5230\u6709\u6548\u4e3b\u673a\uff0c\u539f\u56e0\u662f \u6ca1\u6709\u8db3\u591f\u7684\u4e3b\u673a\u53ef\u7528\u3002\u3002
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager Traceback (most recent call last):
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 229, in inner
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager return func(args, **kwargs)
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager File "/usr/lib/python2.7/site-packages/nova/scheduler/manager.py", line 171, in select_destinations
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager allocation_request_version, return_alternates)
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager File "/usr/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 96, in select_destinations
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager allocation_request_version, return_alternates)
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager File "/usr/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 265, in _schedule
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager claimed_instance_uuids)
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager File "/usr/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 302, in _ensure_sufficient_hosts
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager raise exception.NoValidHost(reason=reason)
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager NoValidHost: \u627e\u4e0d\u5230\u6709\u6548\u4e3b\u673a\uff0c\u539f\u56e0\u662f \u6ca1\u6709\u8db3\u591f\u7684\u4e3b\u673a\u53ef\u7528\u3002\u3002
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager
2020-10-24 20:37:45.896 2982 ERROR nova.conductor.manager
2020-10-24 20:37:46.025 2982 WARNING nova.scheduler.utils [req-61ff79dc-e3f1-4c9b-bf7d-67f02bf3aa20 6b2a61b4bbff42e080b766c8d1eaa069 fdcb701a78724aaa8cf9ec8ddffeb3ea - default default] Failed to compute_task_build_instances: 找不到有效主機(jī)铛铁，原因是沒有足夠的主機(jī)可用隔显。。
Traceback (most recent call last):

File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 229, in inner
return func(*args, **kwargs)

File "/usr/lib/python2.7/site-packages/nova/scheduler/manager.py", line 171, in select_destinations
allocation_request_version, return_alternates)

File "/usr/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 96, in select_destinations
allocation_request_version, return_alternates)

File "/usr/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 265, in _schedule
claimed_instance_uuids)

File "/usr/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 302, in _ensure_sufficient_hosts
raise exception.NoValidHost(reason=reason)

NoValidHost: \u627e\u4e0d\u5230\u6709\u6548\u4e3b\u673a\uff0c\u539f\u56e0\u662f \u6ca1\u6709\u8db3\u591f\u7684\u4e3b\u673a\u53ef\u7528\u3002\u3002
: NoValidHost_Remote: \u627e\u4e0d\u5230\u6709\u6548\u4e3b\u673a\uff0c\u539f\u56e0\u662f \u6ca1\u6709\u8db3\u591f\u7684\u4e3b\u673a\u53ef\u7528\u3002\u3002
2020-10-24 20:37:46.028 2982 WARNING nova.scheduler.utils [req-61ff79dc-e3f1-4c9b-bf7d-67f02bf3aa20 6b2a61b4bbff42e080b766c8d1eaa069 fdcb701a78724aaa8cf9ec8ddffeb3ea - default default] [instance: df36c151-bd58-4fda-8e1a-8f38540c60f5] Setting instance to ERROR state.: NoValidHost_Remote: \u627e\u4e0d\u5230\u6709\u6548\u4e3b\u673a\uff0c\u539f\u56e0\u662f \u6ca1\u6709\u8db3\u591f\u7684\u4e3b\u673a\u53ef\u7528\u3002\u3002
2020-10-24 20:37:51.201 2982 ERROR oslo.messaging._drivers.impl_rabbit [req-61ff79dc-e3f1-4c9b-bf7d-67f02bf3aa20 6b2a61b4bbff42e080b766c8d1eaa069 fdcb701a78724aaa8cf9ec8ddffeb3ea - default default] Connection failed: timed out (retrying in 2.0 seconds): timeout: timed out
2020-10-24 20:37:58.209 2982 ERROR oslo.messaging._drivers.impl_rabbit [req-61ff79dc-e3f1-4c9b-bf7d-67f02bf3aa20 6b2a61b4bbff42e080b766c8d1eaa069 fdcb701a78724aaa8cf9ec8ddffeb3ea - default default] Connection failed: timed out (retrying in 4.0 seconds): timeout: timed out
</code></pre>
<p>修改pack文件指定rabbit的ip</p>
<pre><code>2020-10-25 11:56:44.922 13113 ERROR oslo.messaging._drivers.impl_rabbit [-] [8e9394fc-dbbf-484f-b493-524afb7c33b2] AMQP server on 192.168.31.124:5672 is unreachable: <RecoverableConnectionError: unknown error>. Trying again in 1 seconds.: RecoverableConnectionError: <RecoverableConnectionError: unknown error>
</code></pre>
<h2>引用</h2>
<h2>社交</h2>
<p>每日都有工作和生活記錄饵逐，賞一個(gè)

<img decoding="async" src="https://chevereto.mypicbed.top:11443/images/2020/03/03/a73c4baf7cf83500f0e952e513e97551.png" alt="收款碼"></p>
</div></div><blockquote><p>本文使用 <a href="http://www.reibang.com/p/5709df6fb58d" class="internal">文章同步助手</a> 同步</p></blockquote>

?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請聯(lián)系作者

人面猴
序言：七十年代末括眠，一起剝皮案震驚了整個(gè)濱河市，隨后出現(xiàn)的幾起案子倍权，更是在濱河造成了極大的恐慌掷豺，老刑警劉巖，帶你破解...
沈念sama閱讀 218,546評論 6贊 507
死咒
序言：濱河連續(xù)發(fā)生了三起死亡事件薄声，死亡現(xiàn)場離奇詭異当船，居然都是意外死亡，警方通過查閱死者的電腦和手機(jī)默辨，發(fā)現(xiàn)死者居然都...
沈念sama閱讀 93,224評論 3贊 395
救了他兩次的神仙讓他今天三更去死
文/潘曉璐我一進(jìn)店門德频，熙熙樓的掌柜王于貴愁眉苦臉地迎上來，“玉大人廓奕，你說我怎么就攤上這事抱婉〉凳澹” “怎么了桌粉？”我有些...
開封第一講書人閱讀 164,911評論 0贊 354
道士緝兇錄：失蹤的賣姜人
文/不壞的土叔我叫張陵，是天一觀的道長衙四。經(jīng)常有香客問我铃肯，道長，這世上最難降的妖魔是什么传蹈？我笑而不...
開封第一講書人閱讀 58,737評論 1贊 294
?港島之戀（遺憾婚禮）
正文為了忘掉前任押逼，我火速辦了婚禮步藕，結(jié)果婚禮上，老公的妹妹穿的比我還像新娘挑格。我一直安慰自己咙冗，他們只是感情好，可當(dāng)我...
茶點(diǎn)故事閱讀 67,753評論 6贊 392
惡毒庶女頂嫁案：這布局不是一般人想出來的
文/花漫我一把揭開白布漂彤。她就那樣靜靜地躺著雾消，像睡著了一般。火紅的嫁衣襯著肌膚如雪挫望。梳的紋絲不亂的頭發(fā)上立润，一...
開封第一講書人閱讀 51,598評論 1贊 305
城市分裂傳說
那天，我揣著相機(jī)與錄音媳板，去河邊找鬼桑腮。笑死，一個(gè)胖子當(dāng)著我的面吹牛蛉幸，可吹牛的內(nèi)容都是我干的破讨。我是一名探鬼主播，決...
沈念sama閱讀 40,338評論 3贊 418
雙鴛鴦連環(huán)套：你想象不到人心有多黑
文/蒼蘭香墨我猛地睜開眼奕纫，長吁一口氣：“原來是場噩夢啊……” “哼添忘！你這毒婦竟也來了？” 一聲冷哼從身側(cè)響起若锁，我...
開封第一講書人閱讀 39,249評論 0贊 276
萬榮殺人案實(shí)錄
序言：老撾萬榮一對情侶失蹤搁骑，失蹤者是張志新（化名）和其女友劉穎，沒想到半個(gè)月后又固，有當(dāng)?shù)厝嗽跇淞掷锇l(fā)現(xiàn)了一具尸體仲器，經(jīng)...
沈念sama閱讀 45,696評論 1贊 314
?護(hù)林員之死
正文獨(dú)居荒郊野嶺守林人離奇死亡，尸身上長有42處帶血的膿包…… 初始之章·張勛以下內(nèi)容為張勛視角年9月15日...
茶點(diǎn)故事閱讀 37,888評論 3贊 336
?白月光啟示錄
正文我和宋清朗相戀三年仰冠，在試婚紗的時(shí)候發(fā)現(xiàn)自己被綠了乏冀。大學(xué)時(shí)的朋友給我發(fā)了我未婚夫和他白月光在一起吃飯的照片。...
茶點(diǎn)故事閱讀 40,013評論 1贊 348
活死人
序言：一個(gè)原本活蹦亂跳的男人離奇死亡洋只，死狀恐怖辆沦，靈堂內(nèi)的尸體忽然破棺而出，到底是詐尸還是另有隱情识虚，我是刑警寧澤肢扯，帶...
沈念sama閱讀 35,731評論 5贊 346
?日本核電站爆炸內(nèi)幕
正文年R本政府宣布，位于F島的核電站担锤，受9級特大地震影響蔚晨，放射性物質(zhì)發(fā)生泄漏舅柜。R本人自食惡果不足惜献起，卻給世界環(huán)境...
茶點(diǎn)故事閱讀 41,348評論 3贊 330
男人毒藥：我在死后第九天來索命
文/蒙蒙一走净、第九天我趴在偏房一處隱蔽的房頂上張望诉字。院中可真熱鬧，春花似錦累舷、人聲如沸浩考。這莊子的主人今日做“春日...
開封第一講書人閱讀 31,929評論 0贊 22
一樁弒父案被盈，背后竟有這般陰謀
文/蒼蘭香墨我抬頭看了看天上的太陽怀挠。三九已至，卻和暖如春害捕，著一層夾襖步出監(jiān)牢的瞬間绿淋，已是汗流浹背。一陣腳步聲響...
開封第一講書人閱讀 33,048評論 1贊 270
情欲美人皮
我被黑心中介騙來泰國打工尝盼，沒想到剛下飛機(jī)就差點(diǎn)兒被人妖公主榨干…… 1. 我叫王不留吞滞，地道東北人。一個(gè)月前我還...
沈念sama閱讀 48,203評論 3贊 370
代替公主和親
正文我出身青樓盾沫，卻偏偏與公主長得像裁赠，于是被迫代替她去往敵國和親。傳聞我的和親對象是個(gè)殘疾皇子赴精，可洞房花燭夜當(dāng)晚...
茶點(diǎn)故事閱讀 44,960評論 2贊 355