OPENSTACK-allinone部署 – 马甲数据

<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>实例的核心信息

    <img decoding="async" src="https://chevereto.mypicbed.top:11443/images/2020/10/20/QQPCRealTimeSpeedup_hEEyrpJGGu.png" alt="QQPCRealTimeSpeedup_hEEyrpJGGu.png"></p>
    <p>创建并启动一个实例：首先创建1网络外网-2路由-3子网 最后在子网里创建实例：1外网多路由（路由接外网的子网），1路由多子网（子网也是创建一个网络)（实例接子网的子网）。</p>
    <p><img decoding="async" src="https://chevereto.mypicbed.top:11443/images/2020/10/21/chrome_j8H9X2JD29.png" alt="chrome_j8H9X2JD29.png"></p>
    <p>进行实例管理:实例可以ping外网，外网可以ping实例浮动ip即实现网络打通</p>
    <p><img decoding="async" src="https://chevereto.mypicbed.top:11443/images/2020/10/21/chrome_owpc8m3uu1.png" alt="chrome_owpc8m3uu1.png"></p>
    <p>实例创建一直任务状态调度中</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 ~]# nova list --all-tenants 1
+----+------+-----------+--------+------------+-------------+----------+
| ID | Name | Tenant ID | Status | Task State | Power State | Networks |
+----+------+-----------+--------+------------+-------------+----------+
+----+------+-----------+--------+------------+-------------+----------+

[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>网络(可选域)-镜像=》创建实例</p>
<pre><code>#重复安装 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

创建镜像：状态一直 保存中查看镜像相关组件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

创建成功退出用户重新登录，镜像显示运行中

创建实例一直调度中

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标识cpu不支持虚拟化

使用openstack创建实例时提示：No valid host was found？

nova hypervisor-list 为空解决

[root@openstack nova(keystone_admin)]# nova-status upgrade check
+------------------------------------------------------------------+
| Upgrade Check Results |
+------------------------------------------------------------------+
| Check: Cells v2 |
| Result: Failure |
| Details: No host mappings found but there are compute nodes. Run |
| command 'nova-manage cell_v2 simple_cell_setup' and then |
| retry. |
+------------------------------------------------------------------+
| Check: Placement API |
| Result: Success |
| Details: None |
+------------------------------------------------------------------+
| Check: Ironic Flavor Migration |
| Result: Success |
| Details: None |
+------------------------------------------------------------------+
| Check: Request Spec Migration |
| Result: Success |
| Details: None |
+------------------------------------------------------------------+
| Check: Console Auths |
| Result: Success |
| Details: None |
+------------------------------------------------------------------+
[root@openstack nova(keystone_admin)]# /bin/sh -c “nova-manage cell_v2 discover_hosts --verbose” nova
cell_v2: “nova-manage: 未找到命令
[root@openstack nova(keystone_admin)]# nova-manage cell_v2 discover_hosts --verbose
Found 2 cell mappings.
Skipping cell0 since it does not contain hosts.
Getting computes from cell 'default': 2ad66e08-4b66-46a4-ace4-73821c69985e
Checking host mapping for compute host 'openstack.pukka.cn': 2195ac2d-d893-4ad1-a1f9-697a3b7ffcca
Creating host mapping for compute host 'openstack.pukka.cn': 2195ac2d-d893-4ad1-a1f9-697a3b7ffcca
Found 1 unmapped computes in cell: 2ad66e08-4b66-46a4-ace4-73821c69985e
[root@openstack nova(keystone_admin)]# openstack compute service list
+----+------------------+--------------------+----------+---------+-------+----------------------------+
| ID | Binary | Host | Zone | Status | State | Updated At |
+----+------------------+--------------------+----------+---------+-------+----------------------------+
| 5 | nova-conductor | openstack.pukka.cn | internal | enabled | up | 2020-10-22T08:26:52.000000 |
| 8 | nova-scheduler | openstack.pukka.cn | internal | enabled | up | 2020-10-22T08:26:44.000000 |
| 12 | nova-consoleauth | openstack.pukka.cn | internal | enabled | up | 2020-10-22T08:26:48.000000 |
| 13 | nova-compute | openstack.pukka.cn | nova | enabled | up | 2020-10-22T08:26:52.000000 |
+----+------------------+--------------------+----------+---------+-------+----------------------------+
[root@openstack nova(keystone_admin)]# nova-status upgrade check
nova hypervisor-list
+--------------------------------+
| Upgrade Check Results |
+--------------------------------+
| Check: Cells v2 |
| Result: Success |
| Details: None |
+--------------------------------+
| Check: Placement API |
| Result: Success |
| Details: None |
+--------------------------------+
| Check: Ironic Flavor Migration |
| Result: Success |
| Details: None |
+--------------------------------+
| Check: Request Spec Migration |
| Result: Success |
| Details: None |
+--------------------------------+
| Check: Console Auths |
| Result: Success |
| Details: None |
+--------------------------------+
[root@openstack nova(keystone_admin)]# nova hypervisor-list
+--------------------------------------+---------------------+-------+---------+
| ID | Hypervisor hostname | State | Status |
+--------------------------------------+---------------------+-------+---------+
| 2195ac2d-d893-4ad1-a1f9-697a3b7ffcca | openstack.pukka.cn | up | enabled |
+--------------------------------------+---------------------+-------+---------+

查找nova-api.log没错

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-*这几个服务之间的依赖关系？

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

查看mq状态

systemctl status rabbitmq-server.service

解决web界面其他其他机器无法访问

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

重启mq服务

</code></pre>
<h2>Nova体系结构</h2>
<p>##这里写图片描述</p>
<p><img decoding="async" src="https://chevereto.mypicbed.top:11443/images/2020/10/26/20160707233247115.png" alt="20160707233247115.png"></p>
<h2>实例创建过程</h2>
<p><img decoding="async" src="https://chevereto.mypicbed.top:11443/images/2020/10/26/openstack.png" alt="openstack.png"></p>
<h2>cinder创建卷过程</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四个核心服务组成，这些服务之间通过AMQP消息队列来进行通信。</h2>
<p>Client：Nova Client能够让Tenant管理员或用户终端提交指令，是Openstack官方为了简化用户对RESTful API的使用所提供的API封装，Client能够将用户的请求转换为标准的HTTP请求。</p>
<p>API(nova-api service)：nova-api service能够接收和响应Client的Compute API调用，所以API就是Client进入Nova的HTTP接口。</p>
<p>Compute(nova-compute service)：nova-compute service是一个通过hypervisor APIs(虚拟化层API)来实现创建和终止虚拟机实例的守护进程，Compute通过和VMM的交互来运行虚拟机并管理虚拟机的生命周期。</p>
<p>Scheduler(nova-scheduler service)：nova-scheduler service会从queue中接收一个虚拟机实例的请求，并确定该实例能够运行在哪一台Compute server中。Scheduler通过读取数据库的内容，从可用的池中选择最合适的Compute Node来创建新的虚拟机实例。</p>
<p>Conductor(nova-conductor)：nova-conductor module能够协调nova-compute service和database之间的交互，Conductor为数据库访问提供了一层安全保障。</p>
<p>Queue：queue是Nova 服务组件之间传递信息的中心枢纽。通常使用AMQP(高级消息队列协议Advanced Message Queuing Protocol)的RabbitMQ消息队列来实现。</p>
<p>注意：因为Scheduler只能读取数据库内容，和API通过Policy机制来限制数据库的访问，所以Scheduler和API这两个服务都可以直接访问数据库。但是支持引入了Conductor服务之后，更加规范的方法是通过Conductor服务来对数据库进行操作。</p>
<h2>虚拟机实例化流程</h2>
<p>Step1：首先用户执行Nova Client提供的用于创建虚拟机的指令</p>
<p>Step2：nova-api service监听到来自于Nova Client的HTTP请求，并将这些请求转换为AMQP消息之后加入消息队列Queue</p>
<p>Step3：通过消息队列Queue调用nova-conductor service</p>
<p>Step4：nova-conductor service从Queue接收到虚拟机实例化请求消息后，进行一些准备工作(EG. 汇总HTTP请求中所需要实例化的虚拟机参数)</p>
<p>Step5：nova-conductor service通过Queue告诉nova-scheduler去选择一个合适的Compute Node来创建虚拟机，此时nova-scheduler会读取数据库的内容</p>
<p>Step6：nova-conductor从nova-scheduler得到了合适的Compute Node的信息后，在通过Queue来通知nova-compute service实现虚拟机的创建</p>
<p>送虚拟机实例化的过程可以看出，Nova中最重要的4个服务之间的通信都是通过Queue来实现的。这符合松耦合的实现方式。</p>
<h2>mq可以打开web界面后重新创建实例</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用户登录创建实例</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: 找不到有效主机，原因是 没有足够的主机可用。。
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>每日都有工作和生活记录，赏一个

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

©著作权归作者所有,转载或内容合作请联系作者
  • 人面猴
    序言：七十年代末，一起剥皮案震惊了整个滨河市，随后出现的几起案子，更是在滨河造成了极大的恐慌，老刑警刘岩，带你破解...
    沈念sama阅读 214,904评论 6赞 497
  • 死咒
    序言：滨河连续发生了三起死亡事件，死亡现场离奇诡异，居然都是意外死亡，警方通过查阅死者的电脑和手机，发现死者居然都...
    沈念sama阅读 91,581评论 3赞 389
  • 救了他两次的神仙让他今天三更去死
    文/潘晓璐 我一进店门，熙熙楼的掌柜王于贵愁眉苦脸地迎上来，“玉大人，你说我怎么就摊上这事。” “怎么了？”我有些...
    开封第一讲书人阅读 160,527评论 0赞 350
  • 道士缉凶录：失踪的卖姜人
    文/不坏的土叔 我叫张陵，是天一观的道长。 经常有香客问我，道长，这世上最难降的妖魔是什么？ 我笑而不...
    开封第一讲书人阅读 57,463评论 1赞 288
  • 港岛之恋（遗憾婚礼）
    正文 为了忘掉前任，我火速办了婚礼，结果婚礼上，老公的妹妹穿的比我还像新娘。我一直安慰自己，他们只是感情好，可当我...
    茶点故事阅读 66,546评论 6赞 386
  • 恶毒庶女顶嫁案：这布局不是一般人想出来的
    文/花漫 我一把揭开白布。 她就那样静静地躺着，像睡着了一般。 火红的嫁衣衬着肌肤如雪。 梳的纹丝不乱的头发上，一...
    开封第一讲书人阅读 50,572评论 1赞 293
  • 城市分裂传说
    那天，我揣着相机与录音，去河边找鬼。 笑死，一个胖子当着我的面吹牛，可吹牛的内容都是我干的。 我是一名探鬼主播，决...
    沈念sama阅读 39,582评论 3赞 414
  • 双鸳鸯连环套：你想象不到人心有多黑
    文/苍兰香墨 我猛地睁开眼，长吁一口气：“原来是场噩梦啊……” “哼！你这毒妇竟也来了？” 一声冷哼从身侧响起，我...
    开封第一讲书人阅读 38,330评论 0赞 270
  • 万荣杀人案实录
    序言：老挝万荣一对情侣失踪，失踪者是张志新（化名）和其女友刘颖，没想到半个月后，有当地人在树林里发现了一具尸体，经...
    沈念sama阅读 44,776评论 1赞 307
  • 护林员之死
    正文 独居荒郊野岭守林人离奇死亡，尸身上长有42处带血的脓包…… 初始之章·张勋 以下内容为张勋视角 年9月15日...
    茶点故事阅读 37,087评论 2赞 330
  • 白月光启示录
    正文 我和宋清朗相恋三年，在试婚纱的时候发现自己被绿了。 大学时的朋友给我发了我未婚夫和他白月光在一起吃饭的照片。...
    茶点故事阅读 39,257评论 1赞 344
  • 活死人
    序言：一个原本活蹦乱跳的男人离奇死亡，死状恐怖，灵堂内的尸体忽然破棺而出，到底是诈尸还是另有隐情，我是刑警宁泽，带...
    沈念sama阅读 34,923评论 5赞 338
  • 日本核电站爆炸内幕
    正文 年R本政府宣布，位于F岛的核电站，受9级特大地震影响，放射性物质发生泄漏。R本人自食恶果不足惜，却给世界环境...
    茶点故事阅读 40,571评论 3赞 322
  • 男人毒药：我在死后第九天来索命
    文/蒙蒙 一、第九天 我趴在偏房一处隐蔽的房顶上张望。 院中可真热闹，春花似锦、人声如沸。这庄子的主人今日做“春日...
    开封第一讲书人阅读 31,192评论 0赞 21
  • 一桩弑父案，背后竟有这般阴谋
    文/苍兰香墨 我抬头看了看天上的太阳。三九已至，却和暖如春，着一层夹袄步出监牢的瞬间，已是汗流浃背。 一阵脚步声响...
    开封第一讲书人阅读 32,436评论 1赞 268
  • 情欲美人皮
    我被黑心中介骗来泰国打工， 没想到刚下飞机就差点儿被人妖公主榨干…… 1. 我叫王不留，地道东北人。 一个月前我还...
    沈念sama阅读 47,145评论 2赞 366
  • 代替公主和亲
    正文 我出身青楼，却偏偏与公主长得像，于是被迫代替她去往敌国和亲。 传闻我的和亲对象是个残疾皇子，可洞房花烛夜当晚...
    茶点故事阅读 44,127评论 2赞 352

推荐阅读更多精彩内容