try packstack cont. 您所在的位置:网站首页 dl388gen9安装cont try packstack cont.

try packstack cont.

#try packstack cont.| 来源: 网络整理| 查看: 265

rpm -qi centos-release-openstack-train URL : http://wiki.centos.org/SpecialInterestGroup/Cloud Summary : OpenStack from the CentOS Cloud SIG repo configs Description : yum Configs and basic docs for OpenStack as delivered via the CentOS Cloud SIG. rpm -qi openstack-packstack URL : https://github.com/openstack/packstack Summary : Openstack Install Utility Description : Packstack is a utility that uses Puppet modules to install OpenStack. Packstack can be used to deploy various parts of OpenStack on multiple pre installed servers over ssh.

如果系统里没有配置epel仓库,就不会出现前文中的库版本冲突的问题。 安装后,重新安装非常麻烦(一般是从安装OS重新开始,卸载openstack再安装很麻烦)。所以安装前做好准备,争取一次成功。

关闭selinux;关闭NetworkManager服务、firewalld。

命令汇总

yum -y update;yum -y install centos-release-openstack-train;yum -y update;yum -y install openstack-packstack; packstack --allinone

创建cirros实例,不管是使用admin的public网络,还是demo的private网络,都是创建失败。

失败的原因都类似,在/var/log/neutron/server.log里: Failed to bind port 这2个网络,都是packstack安装后自动配置好的。将这2个网络都删除掉(先将端口、路由子网接口、路由网关删除),再用demo新建一个demo项目private网络,实例仍然失败,同样的错误。 同时systemctl发现,除了neutron-server是运行状态, neutron-dhcp-agent neutron-metadata-agent neutron-l3-agent 都是未运行和disable状态 openstack network agent list只有OVN Controller agent和OVN Metadata agent。 –allinone安装后是不是个坑啊。完全是开箱不能用啊。

在ECS上试试,配置4C8G NetworkManager停止并禁用掉后,重启ecs,eth0会获取不到内网IP 不过route -n看还是正常的,默认路由从eth0出去,网关是10.0.0.1 而手工ifconfig配上eth0的IP(和建立ecs获取时的一样)后,就正常了,通过EIP可以正常访问。 安装好后的一些信息

[root@ecs-tos ~(keystone_admin)]# openstack service list --long +----------------------------------+------------+--------------+--------------------------------+---------+ | ID | Name | Type | Description | Enabled | +----------------------------------+------------+--------------+--------------------------------+---------+ | 022e617c82dd4ef7b2ca6c24cac5ae01 | cinderv2 | volumev2 | Cinder Service v2 | True | | 25e0a5d5cebf46caa9031a122ceb6652 | placement | placement | Placement Service | True | | 762e6531364a4a95aa7131f7ddda3c20 | aodh | alarming | OpenStack Alarming Service | True | | 7ddbba5f1a1444fdabf1f55ee5cf2f95 | nova | compute | Openstack Compute Service | True | | 800eed572ab54163bc751a7c52b12a21 | neutron | network | Neutron Networking Service | True | | 8af4bddeb5cc40ec808a5673f7eba18a | keystone | identity | OpenStack Identity Service | True | | adbb766a31a5463c9f3511133741e897 | swift | object-store | Openstack Object-Store Service | True | | af76c7e47cce401fa7d7b65a49fd88e6 | gnocchi | metric | OpenStack Metric Service | True | | cef58244db894088977dba89f1c900c0 | cinderv3 | volumev3 | Cinder Service v3 | True | | dc273a3cc8ee496ab8f8a4af152d8733 | ceilometer | metering | Openstack Metering Service | True | | f12faef657b24c5fb80cc8f7d527a8ce | glance | image | OpenStack Image Service | True | +----------------------------------+------------+--------------+--------------------------------+---------+ openstack project list --long +----------------------------------+----------+-----------+-----------------------------------+---------+ | ID | Name | Domain ID | Description | Enabled | +----------------------------------+----------+-----------+-----------------------------------+---------+ | 78d4750705b741de868f0a79c878e95d | services | default | Tenant for the openstack services | True | | 8739dcf9597a4953b0c4d1e4aebc4679 | admin | default | admin tenant | True | | a731aa8b86544b0f8fd370e7aa07c68c | demo | default | default tenant | True | +----------------------------------+----------+-----------+-----------------------------------+---------+ openstack network agent list --long +--------------------------------------+----------------------+---------+-------------------+-------+-------+-------------------------------+ | ID | Agent Type | Host | Availability Zone | Alive | State | Binary | +--------------------------------------+----------------------+---------+-------------------+-------+-------+-------------------------------+ | 95962a75-0fc7-4fda-83c4-ba422871cb74 | OVN Controller agent | ecs-tos | | :-) | UP | ovn-controller | | 06863a10-36b8-4580-ad03-285a4cdcb5bb | OVN Metadata agent | ecs-tos | | :-) | UP | networking-ovn-metadata-agent | +--------------------------------------+----------------------+---------+-------------------+-------+-------+-------------------------------+

/var/log/nova/nova-compute.log: Timed out waiting for nova-conductor. 同时创建cirros实例一直在任务:调度状态,持续十几分钟。 重启 systemctl restart openstack-nova-conductor.service Log里显示:nova-conductor connection established successfully

systemctl status openstack-nova* 看一下各nova组件状态,发现openstack-nova-scheduler.service是active:failed状态,重启之

cirros实例还是scheduling,18分钟了。烦了,删掉它

WEB操作比较慢,命令行再次创建实例(admin用户) openstack server create --image cirros --flavor m1.tiny --network public cirros-admin1 返回 | OS-EXT-STS:task_state | scheduling | | OS-EXT-STS:vm_state | building | 然后很快失败了。openstack server show cirros-admin1 看原因,但是原因很不明确 | fault | {u’message’: u’Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures for instance 39d76e9c-1c4a-47c3-b8fe-213c85a36409.’,

还是去看Log文件nova-conductor.log:除了上面的报错外,还有具体报错: Binding failed for port 61bf9b44-e1cb-4152-9283-9095c6480c0e, please check neutron logs for more information 再看neutron目录下的server.log:

2023-03-31 22:53:41.411 22276 ERROR neutron.plugins.ml2.managers [...] Failed to bind port 61bf9b44-e1cb-4152-9283-9095c6480c0e on host ecs-tos.openstacklocal for vnic_type normal using segments [{'network_id': '484ce792-978d-45d8-998e-9c9b4b24c450', 'segmentation_id': None, 'physical_network': u'extnet', 'id': 'd56af75c-9bef-46e0-b519-568755d5235a', 'network_type': u'flat'}]

索性把服务都检查一遍 systemctl status openstack-* 发现swift有好几个服务失败;但是它是做OBS的,应该不影响创建实例。

systemctl status neutron-* 奇怪的是它没显示没运行的服务,比如 ● neutron-dhcp-agent.service - OpenStack Neutron DHCP Agent Loaded: loaded (/usr/lib/systemd/system/neutron-dhcp-agent.service; disabled; vendor preset: disabled) Active: inactive (dead) 等等,手工把这3个启动起来 neutron-dhcp-agent neutron-metadata-agent neutron-l3-agent 其中只有l3-agent失败了,不管他

再试创建instance,还是一样的报错。

之前在实体机上试过网络删除重建,也是没有效果。ECS不想再试了,我要换掉allinone的安装参数重新来过。

下面命令在实验过程中修改后的版本

packstack --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-l2-agent=openvswitch --os-neutron-ml2-type-drivers=vxlan,flat --os-neutron-ml2-mechanism-drivers=openvswitch --provision-demo=n --cinder-volumes-create=n --os-heat-install=n --os-swift-storage-size=10G --gen-answer-file /root/answers.txt #因为--cinder-volumes-create=n所以挂一个盘,pvcreate /dev/vdb1; vgcreate cinder-volumes /dev/vdb1 #--provision-demo=n所以不会建demo项目 #--os-heat-install=y这个好像没有什么用,改成n #--nova-libvirt-virt-type=kvm宿主机是ECS,没有硬件虚拟化,这是作死,删掉 packstack --answer-file ./answers.txt

因为配置了openswitch,所以allinone的下面这条输出提示就没有了

* 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

没有建立任何network。也没有那个不能用的cirros镜像。挺好。手工建立

neutron net-create admin-private neutron subnet-create admin-private 10.10.0.0/24 --name admin-private-subnet --dns-nameserver 8.8.8.8 #手工建个cirros镜像 openstack image create --disk-format qcow2 --container-format bare --public --file ./cirros-0.4.0-x86_64-disk.img cirros openstack server create --image cirros --flavor m1.tiny --network admin-private cirros-admin1 #创建实例一下子很卡,发现8G内存快用完了,一样的失败现象。 nova好几个组件日志报错:AMQP server on 10.0.0.100:5672 is unreachable: [Errno 111] ECONNREFUSED. 这个端口是rabbitmq的,没有侦听了

怀疑是内存不够导致问题,于是重启,因为重启后需要手工配置eth0的内网IP,而Openstack是开机启动,部分openstack服务是失败的, systemctl restart redis openstack-* 重启后发现可用内存也不多,所以stop openstack-heat-* ;再禁用掉 再创实例,竟然是这个错

nova-conductor.log/nova-computer.log: Failed to start libvirt guest: libvirtError: invalid argument: could not find capabilities for domaintype=kvm

没有硬件虚拟化,都是该死的安装参数kvm导致的。

先说一下如何避免启动ECS后手工配IP,先修改ifcfg-eth0配置静态网络信息,然后启用老的network服务,chkconfig network on.重启就可以了 静态网络信息:

IPADDR=10.0.0.100 PREFIX=24 GATEWAY=10.0.0.1 DNS1=100.125.136.29 DNS2=100.125.1.250 DEFROUTE=yes

systemctl list-units --type=service发现只有这2个服务失败了openstack-nova-conductor openstack-nova-scheduler 都是连接5000端口的http服务失败,可能是系统控制的服务启动顺序不太完善。重启这2个服务即可。

不用heat后,发现内存有2G可用,所以先不加内存。但是kvm支持没有,所以还是要重新安装 重新安装后,重做建立网络、导入image、创建server返回OK了

| OS-EXT-STS:power_state | Running | | OS-EXT-STS:task_state | None | | OS-EXT-STS:vm_state | active |

下一步优化一下内存占用,内存可用只二百兆了 再就是观察一下,重启ecs后是不是每次有2个nova服务启动失败 总结:packstack train版本allinone模式安装就是个开箱不能用的货。



【本文地址】

公司简介

联系我们

今日新闻

    推荐新闻

    专题文章
      CopyRight 2018-2019 实验室设备网 版权所有