OpenStack Grizzly无法configuration新的虚拟机

我在Mirantis Fuel安装的CentOS上运行Openstack Grizzly。

[root@controller-20 ~]# cat /etc/redhat-release CentOS release 6.4 (Final) [root@controller-20 ~]# rpm -qa | grep -i openstack-nova openstack-nova-console-2013.1.1.fuel3.0-mira.2.noarch openstack-nova-common-2013.1.1.fuel3.0-mira.2.noarch openstack-nova-scheduler-2013.1.1.fuel3.0-mira.2.noarch openstack-nova-conductor-2013.1.1.fuel3.0-mira.2.noarch openstack-nova-objectstore-2013.1.1.fuel3.0-mira.2.noarch openstack-nova-novncproxy-0.4-8.el6.noarch openstack-nova-cert-2013.1.1.fuel3.0-mira.2.noarch openstack-nova-api-2013.1.1.fuel3.0-mira.2.noarch 

该拓扑结构目前是一个控制器节点和三个计算节点，全部运行在现代戴尔机架安装硬件上。 在问题开始之前，我已经调配了大约25台虚拟机。

由于某种原因，在创build/删除虚拟机的同时，一个固定的IP卡住了一些不确定的状态。 现在，我无法创build新的虚拟机。 Openstack尝试使用它认为仍然是旧VM的一部分的IP，但无法构buildVM。

我的固定networking是10.129.0.0/24。

• ssh挂在Ubuntu MaaS异构集群中
• 了解VPN实施
• 如何在多服务器环境中检测和诊断本地networking问题？
• 通过OpenVPN从特定域传递stream量
• kvm guest无法连接到主机外部，反之亦然

以下是来自nova-manage命令行的问题IP列表：

 # nova-manage fixed list | grep -E 'network|WARNING' -A 1 network IP address hostname host 10.129.0.0/24 10.129.0.0 None None -- WARNING: fixed ip 10.129.0.20 allocated to missing instance 10.129.0.0/24 10.129.0.20 None None -- WARNING: fixed ip 10.129.0.23 allocated to missing instance 10.129.0.0/24 10.129.0.23 None None -- WARNING: fixed ip 10.129.0.25 allocated to missing instance 10.129.0.0/24 10.129.0.25 None None WARNING: fixed ip 10.129.0.26 allocated to missing instance 10.129.0.0/24 10.129.0.26 None None WARNING: fixed ip 10.129.0.27 allocated to missing instance 10.129.0.0/24 10.129.0.27 None None -- WARNING: fixed ip 10.129.0.30 allocated to missing instance 10.129.0.0/24 10.129.0.30 None None WARNING: fixed ip 10.129.0.31 allocated to missing instance 10.129.0.0/24 10.129.0.31 None None WARNING: fixed ip 10.129.0.32 allocated to missing instance 10.129.0.0/24 10.129.0.32 None None WARNING: fixed ip 10.129.0.33 allocated to missing instance 10.129.0.0/24 10.129.0.33 None None WARNING: fixed ip 10.129.0.34 allocated to missing instance 10.129.0.0/24 10.129.0.34 None None WARNING: fixed ip 10.129.0.35 allocated to missing instance 10.129.0.0/24 10.129.0.35 None None WARNING: fixed ip 10.129.0.36 allocated to missing instance 10.129.0.0/24 10.129.0.36 None None WARNING: fixed ip 10.129.0.37 allocated to missing instance 10.129.0.0/24 10.129.0.37 None None WARNING: fixed ip 10.129.0.38 allocated to missing instance 10.129.0.0/24 10.129.0.38 None None WARNING: fixed ip 10.129.0.39 allocated to missing instance 10.129.0.0/24 10.129.0.39 None None WARNING: fixed ip 10.129.0.40 allocated to missing instance 10.129.0.0/24 10.129.0.40 None None WARNING: fixed ip 10.129.0.41 allocated to missing instance 10.129.0.0/24 10.129.0.41 None None WARNING: fixed ip 10.129.0.42 allocated to missing instance 10.129.0.0/24 10.129.0.42 None None WARNING: fixed ip 10.129.0.43 allocated to missing instance 10.129.0.0/24 10.129.0.43 None None WARNING: fixed ip 10.129.0.44 allocated to missing instance 10.129.0.0/24 10.129.0.44 None None WARNING: fixed ip 10.129.0.45 allocated to missing instance 10.129.0.0/24 10.129.0.45 None None WARNING: fixed ip 10.129.0.46 allocated to missing instance 10.129.0.0/24 10.129.0.46 None None -- WARNING: fixed ip 10.129.0.48 allocated to missing instance 10.129.0.0/24 10.129.0.48 None None WARNING: fixed ip 10.129.0.49 allocated to missing instance 10.129.0.0/24 10.129.0.49 None None WARNING: fixed ip 10.129.0.50 allocated to missing instance 10.129.0.0/24 10.129.0.50 None None -- WARNING: fixed ip 10.129.0.52 allocated to missing instance 10.129.0.0/24 10.129.0.52 None None WARNING: fixed ip 10.129.0.53 allocated to missing instance 10.129.0.0/24 10.129.0.53 None None -- WARNING: fixed ip 10.129.0.55 allocated to missing instance 10.129.0.0/24 10.129.0.55 None None WARNING: fixed ip 10.129.0.56 allocated to missing instance 10.129.0.0/24 10.129.0.56 None None WARNING: fixed ip 10.129.0.57 allocated to missing instance 10.129.0.0/24 10.129.0.57 None None -- WARNING: fixed ip 10.129.0.59 allocated to missing instance 10.129.0.0/24 10.129.0.59 None None WARNING: fixed ip 10.129.0.60 allocated to missing instance 10.129.0.0/24 10.129.0.60 None None WARNING: fixed ip 10.129.0.61 allocated to missing instance 10.129.0.0/24 10.129.0.61 None None 

我知道10.129.0.20 IP标记了启动问题的虚拟机实例。 这个问题performance在无法configuration新的虚拟机。

 [root@controller-20 ~]# nova --os-username demetri --os-tenant-name admin --os-auth-url http://localhost:5000/v2.0/ fixed-ip-get 10.129.0.20 OS Password: +-------------+---------------+----------+-----------------------+ | address | cidr | hostname | host | +-------------+---------------+----------+-----------------------+ | 10.129.0.20 | 10.129.0.0/24 | devdbl9 | compute-21.domain.tld | +-------------+---------------+----------+-----------------------+ 

nova-manage命令似乎没有提供回收这些IP的任何工具。 我已经尝试了保留/不保留，但是这并没有办法。 另外，这些IP在名为fixed_ips的nova mysql表中表示。 例：

 +---------------------+---------------------+------------+-----+--------------+------------+-----------+--------+----------+----------------------+-----------------------+--------------------------------------+---------+ | created_at | updated_at | deleted_at | id | address | network_id | allocated | leased | reserved | virtual_interface_id | host | instance_uuid | deleted | +---------------------+---------------------+------------+-----+--------------+------------+-----------+--------+----------+----------------------+-----------------------+--------------------------------------+---------+ | 2013-08-05 11:10:19 | 2013-10-16 11:32:20 | NULL | 21 | 10.129.0.20 | 1 | 0 | 0 | 0 | NULL | NULL | df2e9214-78cf-49d3-b256-e35d48818f29 | 0 | 

为了进一步确认问题涉及到固定的IPnetworking，用户界面反映了一个递增的IP地址，从.21开始，转到.22，到达.23，然后最终以状态“ERROR”失败。

所有这一切都是说，自从这一切开始发生以来，大多数但不是所有试图调用新虚拟机的尝试都失败了。 如何进一步排除故障，最终如何才能平稳地configuration新的虚拟机？

谢谢。