kolla-ansible在ubuntu部署openstack

已于 2022-05-27 10:16:46 修改
阅读量1.9k 收藏 11
点赞数 1
分类专栏： openstack 文章标签： 云计算
于 2022-05-12 17:59:25 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_43266367/article/details/124693424
版权

使用kolla-ansible部署一个openstack victoria版集群，然后对接ceph存储。

环境规划

使用5台虚拟机，详细信息如下

角色主机名规格IP系统
控制节点+部署机+docker-registrycontrol-012u4gens33: 192.168.211.20(用于连接公网和openstack-api)
ens34: 192.168.112.20 (用于neutron-extenal-network)		Ubuntu20.04
控制节点control-022u4gens33: 192.168.211.21(用于连接公网和openstack-api)
ens34: 192.168.112.21 (用于neutron-extenal-network)		Ubuntu20.04
控制节点control-022u4gens33: 192.168.211.22(用于连接公网和openstack-api)
ens34: 192.168.112.22 (用于neutron-external-network)		Ubuntu20.04
计算节点compute-014u8gens33: 192.168.211.20(用于连接公网和openstack-api)
ens34: 192.168.112.20 (用于虚拟机网络)		Ubuntu20.04
计算节点compute-024u8gens33: 192.168.211.20(用于连接公网和openstack-api)
ens34: 192.168.112.20 (用于虚拟机网络)		Ubuntu20.04

准备操作

配置control-01到其他节点的免密

PASS=123456
for i in {20..24}; do \
sshpass -p $PASS ssh-copy-id -o StrictHostKeyChecking=no ceeinfra@192.168.112.$i;done

配置/etc/hosts

在所有节点配置主机名解析，编辑/etc/hosts文件，内容如下：

ceeinfra@control-02:~$ sudo cat /etc/hosts
127.0.0.1 localhost

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
192.168.211.20 control-01
192.168.211.21 control-02
192.168.211.22 control-03
192.168.211.23 compute-01
192.168.211.24 compute-02

# openstack api address
192.168.211.25 openstack-api

部署镜像仓库（可选）

由于我的网络较差，从dockerhub下载镜像很慢（配置了镜像加速也没用），所以我自己在control-01节点搭建了一个镜像仓库，在公网上将download下来后，再传到我的本地仓库。这个步骤是可选的，如果网络够好，下载镜像很快可以忽略这一步。

安装ansible和kolla-ansible

在control-01安装相关依赖包

sudo apt install python3-dev libffi-dev gcc libssl-dev python3-pip

在control-01安装ansible

sudo apt install ansible

然后在control-01安装kolla-ansible，选择和openstack版本对应的kolla-ansible版本即可

sudo pip3 install git+https://opendev.org/openstack/kolla-ansible@stable/victoria

准备kolla-ansible配置文件

复制kolla-ansible的相关配置文件

sudo mkdir -p /etc/kolla
sudo chown $USER:$USER /etc/kolla
cp -r /usr/local/share/kolla-ansible/etc_examples/kolla/* /etc/kolla
cp /usr/local/share/kolla-ansible/ansible/inventory/* .

编辑/etc/ansible/ansible.cfg，修改部分ansible的参数

[defaults]
host_key_checking=False
pipelining=True
forks=100

编辑kolla-ansible的inventory文件，主要涉及到两个文件：一个是all-in-one，这个文件适用于单机构建openstack集群；另一个是multinode，这个文件适用于多节点构建openstack集群。
因为本次部署是多节点，所以编辑multinode文件，主要修改了control、compute、network、monitoring、storage组对应的主机，其余的保持默认配置，具体内容如下：

# These initial groups are the only groups required to be modified. The
# additional groups are for more control of the environment.
[control]
# These hostname must be resolvable from your deployment host
control-01
control-02
control-03

# The above can also be specified as follows:
#control[01:03]     ansible_user=kolla

# The network nodes are where your l3-agent and loadbalancers will run
# This can be the same as a host in the control group
[network:children]
control


[compute]
compute-01
compute-02

[monitoring:children]
control

# When compute nodes and control nodes use different interfaces,
# you need to comment out "api_interface" and other interfaces from the globals.yml
# and specify like below:
#compute01 neutron_external_interface=eth0 api_interface=em1 storage_interface=em1 tunnel_interface=em1

[storage:children]
control

[deployment]
localhost       ansible_connection=local

[baremetal:children]
control
network
compute
storage
monitoring

[tls-backend:children]
control

# You can explicitly specify which hosts run each project by updating the
# groups in the sections below. Common services are grouped together.

[common:children]
control
network
compute
storage
monitoring

[chrony-server:children]
haproxy

[chrony:children]
control
network
compute
storage
monitoring

[collectd:children]
compute

[grafana:children]
monitoring

[etcd:children]
control

[influxdb:children]
monitoring

[prometheus:children]
monitoring

[kafka:children]
control

[karbor:children]
control

[kibana:children]
control

[telegraf:children]
compute
control
monitoring
network
storage

[elasticsearch:children]
control

[haproxy:children]
network

[mariadb:children]
control

[rabbitmq:children]
control

[outward-rabbitmq:children]
control

[qdrouterd:children]
control

[monasca-agent:children]
compute
control
monitoring
network
storage

[monasca:children]
monitoring

[storm:children]
monitoring

[keystone:children]
control

[glance:children]
control

[nova:children]
control

[neutron:children]
network

[openvswitch:children]
network
compute
manila-share

[cinder:children]
control

[cloudkitty:children]
control

[freezer:children]
control

[memcached:children]
control

[horizon:children]
control

[swift:children]
control

[barbican:children]
control

[heat:children]
control

[murano:children]
control

[solum:children]
control

[ironic:children]
control

[magnum:children]
control

[qinling:children]
control

[sahara:children]
control

[mistral:children]
control

[manila:children]
control

[ceilometer:children]
control

[aodh:children]
control

[cyborg:children]
control
compute

[panko:children]
control

[gnocchi:children]
control

[tacker:children]
control

[trove:children]
control

# Tempest
[tempest:children]
control

[senlin:children]
control

[vmtp:children]
control

[vitrage:children]
control

[watcher:children]
control

[rally:children]
control

[searchlight:children]
control

[octavia:children]
control

[designate:children]
control

[placement:children]
control

[bifrost:children]
deployment

[zookeeper:children]
control

[zun:children]
control

[skydive:children]
monitoring

[redis:children]
control

[blazar:children]
control

# Additional control implemented here. These groups allow you to control which
# services run on which hosts at a per-service level.
#
# Word of caution: Some services are required to run on the same host to
# function appropriately. For example, neutron-metadata-agent must run on the
# same host as the l3-agent and (depending on configuration) the dhcp-agent.

# Common
[cron:children]
common

[fluentd:children]
common

[kolla-logs:children]
common

[kolla-toolbox:children]
common

# Elasticsearch Curator
[elasticsearch-curator:children]
elasticsearch

# Glance
[glance-api:children]
glance

# Nova
[nova-api:children]
nova

[nova-conductor:children]
nova

[nova-super-conductor:children]
nova

[nova-novncproxy:children]
nova

[nova-scheduler:children]
nova

[nova-spicehtml5proxy:children]
nova

[nova-compute-ironic:children]
nova

[nova-serialproxy:children]
nova

# Neutron
[neutron-server:children]
control

[neutron-dhcp-agent:children]
neutron

[neutron-l3-agent:children]
neutron

[neutron-metadata-agent:children]
neutron

[neutron-ovn-metadata-agent:children]
compute

[neutron-bgp-dragent:children]
neutron

[neutron-infoblox-ipam-agent:children]
neutron

[neutron-metering-agent:children]
neutron

[ironic-neutron-agent:children]
neutron

# Cinder
[cinder-api:children]
cinder

[cinder-backup:children]
storage

[cinder-scheduler:children]
cinder

[cinder-volume:children]
storage

# Cloudkitty
[cloudkitty-api:children]
cloudkitty

[cloudkitty-processor:children]
cloudkitty

# Freezer
[freezer-api:children]
freezer

[freezer-scheduler:children]
freezer

# iSCSI
[iscsid:children]
compute
storage
ironic

[tgtd:children]
storage

# Karbor
[karbor-api:children]
karbor

[karbor-protection:children]
karbor

[karbor-operationengine:children]
karbor

# Manila
[manila-api:children]
manila

[manila-scheduler:children]
manila

[manila-share:children]
network

[manila-data:children]
manila

# Swift
[swift-proxy-server:children]
swift

[swift-account-server:children]
storage

[swift-container-server:children]
storage

[swift-object-server:children]
storage

# Barbican
[barbican-api:children]
barbican

[barbican-keystone-listener:children]
barbican

[barbican-worker:children]
barbican

# Heat
[heat-api:children]
heat

[heat-api-cfn:children]
heat

[heat-engine:children]
heat

# Murano
[murano-api:children]
murano

[murano-engine:children]
murano

# Monasca
[monasca-agent-collector:children]
monasca-agent

[monasca-agent-forwarder:children]
monasca-agent

[monasca-agent-statsd:children]
monasca-agent

[monasca-api:children]
monasca

[monasca-grafana:children]
monasca

[monasca-log-transformer:children]
monasca

[monasca-log-persister:children]
monasca

[monasca-log-metrics:children]
monasca

[monasca-thresh:children]
monasca

[monasca-notification:children]
monasca

[monasca-persister:children]
monasca

# Storm
[storm-worker:children]
storm

[storm-nimbus:children]
storm

# Ironic
[ironic-api:children]
ironic

[ironic-conductor:children]
ironic

[ironic-inspector:children]
ironic

[ironic-pxe:children]
ironic

[ironic-ipxe:children]
ironic

# Magnum
[magnum-api:children]
magnum

[magnum-conductor:children]
magnum

# Qinling
[qinling-api:children]
qinling

[qinling-engine:children]
qinling

# Sahara
[sahara-api:children]
sahara

[sahara-engine:children]
sahara

# Solum
[solum-api:children]
solum

[solum-worker:children]
solum

[solum-deployer:children]
solum

[solum-conductor:children]
solum

[solum-application-deployment:children]
solum

[solum-image-builder:children]
solum

# Mistral
[mistral-api:children]
mistral

[mistral-executor:children]
mistral

[mistral-engine:children]
mistral

[mistral-event-engine:children]
mistral

# Ceilometer
[ceilometer-central:children]
ceilometer

[ceilometer-notification:children]
ceilometer

[ceilometer-compute:children]
compute

[ceilometer-ipmi:children]
compute

# Aodh
[aodh-api:children]
aodh

[aodh-evaluator:children]
aodh

[aodh-listener:children]
aodh

[aodh-notifier:children]
aodh

# Cyborg
[cyborg-api:children]
cyborg

[cyborg-agent:children]
compute

[cyborg-conductor:children]
cyborg

# Panko
[panko-api:children]
panko

# Gnocchi
[gnocchi-api:children]
gnocchi

[gnocchi-statsd:children]
gnocchi

[gnocchi-metricd:children]
gnocchi

# Trove
[trove-api:children]
trove

[trove-conductor:children]
trove

[trove-taskmanager:children]
trove

# Multipathd
[multipathd:children]
compute
storage

# Watcher
[watcher-api:children]
watcher

[watcher-engine:children]
watcher

[watcher-applier:children]
watcher

# Senlin
[senlin-api:children]
senlin

[senlin-conductor:children]
senlin

[senlin-engine:children]
senlin

[senlin-health-manager:children]
senlin

# Searchlight
[searchlight-api:children]
searchlight

[searchlight-listener:children]
searchlight

# Octavia
[octavia-api:children]
octavia

[octavia-driver-agent:children]
octavia

[octavia-health-manager:children]
octavia

[octavia-housekeeping:children]
octavia

[octavia-worker:children]
octavia

# Designate
[designate-api:children]
designate

[designate-central:children]
designate

[designate-producer:children]
designate

[designate-mdns:children]
network

[designate-worker:children]
designate

[designate-sink:children]
designate

[designate-backend-bind9:children]
designate

# Placement
[placement-api:children]
placement

# Zun
[zun-api:children]
zun

[zun-wsproxy:children]
zun

[zun-compute:children]
compute

[zun-cni-daemon:children]
compute

# Skydive
[skydive-analyzer:children]
skydive

[skydive-agent:children]
compute
network

# Tacker
[tacker-server:children]
tacker

[tacker-conductor:children]
tacker

# Vitrage
[vitrage-api:children]
vitrage

[vitrage-notifier:children]
vitrage

[vitrage-graph:children]
vitrage

[vitrage-ml:children]
vitrage

[vitrage-persistor:children]
vitrage

# Blazar
[blazar-api:children]
blazar

[blazar-manager:children]
blazar

# Prometheus
[prometheus-node-exporter:children]
monitoring
control
compute
network
storage

[prometheus-mysqld-exporter:children]
mariadb

[prometheus-haproxy-exporter:children]
haproxy

[prometheus-memcached-exporter:children]
memcached

[prometheus-cadvisor:children]
monitoring
control
compute
network
storage

[prometheus-alertmanager:children]
monitoring

[prometheus-openstack-exporter:children]
monitoring

[prometheus-elasticsearch-exporter:children]
elasticsearch

[prometheus-blackbox-exporter:children]
monitoring

[masakari-api:children]
control

[masakari-engine:children]
control

[masakari-monitors:children]
compute

[ovn-controller:children]
ovn-controller-compute
ovn-controller-network

[ovn-controller-compute:children]
compute

[ovn-controller-network:children]
network

[ovn-database:children]
control

[ovn-northd:children]
ovn-database

[ovn-nb-db:children]
ovn-database

[ovn-sb-db:children]
ovn-database

修改完成后，可以用ansible ping模块测试所有主机连通性。

ansible -i multinode all -m ping

然后编辑/etc/kolla/globals.yml，这个文件主要包含一些部署openstack时需要用到的环境变量，只修改了下面的部分配置：

kolla_base_distro: "ubuntu"		#基础镜像
kolla_install_type: "binary"	#安装方式，binary或source
openstack_release: "victoria"	#openstack版本
kolla_internal_vip_address: "192.168.211.25"	#openstack api地址
docker_registry: "kolla-image-registry.com:4000"	#下载相关镜像的仓库地址，这是我搭建本地仓库
network_interface: "ens33"						#openstack internal-api地址使用的网卡
kolla_external_vip_interface: "ens33"			#openstack extenal-api 地址使用的网卡
api_interface: "{{ network_interface }}"		#openstack internal-api地址使用的网卡
neutron_external_interface: "ens34"			#neutron默认使用的external网卡，可以后期在openstack配置文件修改
neutron_plugin_agent: "openvswitch"		#neutron网络插件
neutron_ipam_driver: "internal"		
keepalived_virtual_router_id: "51"		#在同一局域网有多个keepalived集群时需要指定
enable_openstack_core: "yes"			#启用openstack的核心组件
enable_glance: "{{ enable_openstack_core | bool }}"
enable_haproxy: "yes"
enable_keepalived: "{{ enable_haproxy | bool }}"
enable_keystone: "{{ enable_openstack_core | bool }}"
enable_mariadb: "yes"
enable_memcached: "yes"
enable_neutron: "{{ enable_openstack_core | bool }}"
enable_nova: "{{ enable_openstack_core | bool }}"
enable_rabbitmq: "{{ 'yes' if om_rpc_transport == 'rabbit' or om_notify_transport == 'rabbit' else 'no' }}"
enable_chrony: "yes"
enable_cinder: "yes"	#启用cinder
enable_cinder_backup: "yes"	#启用cinder-backup
enable_heat: "{{ enable_openstack_core | bool }}"
enable_horizon: "{{ enable_openstack_core | bool }}"
enable_horizon_heat: "{{ enable_heat | bool }}"
glance_backend_ceph: "no"		
glance_backend_file: "yes"
glance_backend_swift: "no"
glance_backend_vmware: "no"
enable_glance_image_cache: "no"
cinder_backend_ceph: "no"		
nova_backend_ceph: "no"		
nova_compute_virt_type: "kvm"

最后运行下面的命令，生成openstack相关的密码：

kolla-genpwd

所有的密码都保存在/etc/kolla/passwords.yml文件中，如果想要修改可以编辑这个文件。

部署openstack

首先执行bootstrap-servers指令，在节点上执行一些初始化操作，安装一些依赖包，比如docker。

kolla-ansible -i multinode bootstrap-servers

然后运行prechecks指令，进行部署前的环境检查：

kolla-ansible -i multinode prechecks

开始部署openstack，运行下面命令

kolla-ansible -i multinode deploy

等待命令运行完成，并且ansible-playbook没有failed就表示已经成功部署。

测试使用openstack

执行kolla-ansible post-deploy生成环境变量文件

kolla-ansible post-deploy
. /etc/kolla/admin-openrc.sh

在control-01安装openstack客户端

sudo apt install python3-openstackclient

然后执行一条openstack，无报错即可。等对接完ceph后再进行创建虚拟机测试。

对接Ceph存储

ceph存储集群是事先部署的，不包含在这里。具体部署过程可以自行百度。

在所有openstack节点安装ceph客户端

apt install ceph-common ppython3-rbd

在ceph集群上创建对应的pool

创建存储池

ceph osd pool create images 64 64
ceph osd pool create vms 64 64
ceph osd pool create volumes 64 64
ceph osd pool create backups 64 64

初始化pool

rbd pool init images
rbd pool init vms
rbd pool init volumes
rbd pool init backups

创建账号并授权

ceph auth get-or-create client.cinder mon 'allow r' osd 'allow class-read object_prefix rbd_children, allow rwx pool=volumes, allow rwx pool=vms, allow rx pool=images' -o /etc/ceph/ceph.client.cinder.keyring
ceph auth get-or-create client.glance mon 'allow r' osd 'allow class-read object_prefix rbd_children, allow rwx pool=images' -o /etc/ceph/ceph.client.glance.keyring

glance对接ceph

在ceph节点上将ceph.conf和client.glance.keyring复制到所有控制节点/etc/kolla/glace-api目录下：

scp /etc/ceph/ceph.conf /etc/ceph/ceph.client.glance.keyring \
root@control-01:/etc/kolla/glance-api/
scp /etc/ceph/ceph.conf /etc/ceph/ceph.client.glance.keyring \
root@control-02:/etc/kolla/glance-api/
scp /etc/ceph/ceph.conf /etc/ceph/ceph.client.glance.keyring \
root@control-03:/etc/kolla/glance-api/

在所有控制节点修改/etc/kolla/glance-api/config.json，将ceph的文件映射到glance_api容器里：

{
    "command": "glance-api",
    "config_files": [
        {
            "source": "/var/lib/kolla/config_files/glance-api.conf",
            "dest": "/etc/glance/glance-api.conf",
            "owner": "glance",
            "perm": "0600"
        },
        #添加面的内容
        {
            "source": "/var/lib/kolla/config_files/ceph.conf",
            "dest": "/etc/ceph/ceph.conf",
            "owner": "glance",
            "perm": "0600"
        },
        {	#添加
            "source": "/var/lib/kolla/config_files/ceph.client.glance.keyring",
            "dest": "/etc/ceph/ceph.client.glance.keyring",
            "owner": "glance",
            "perm": "0600"
        }

    ],
    "permissions": [
        {
            "path": "/var/lib/glance",
            "owner": "glance:glance",
            "recurse": true
        },
        {
            "path": "/var/log/kolla/glance",
            "owner": "glance:glance",
            "recurse": true
        }
    ]
}

修改/etc/kolla/glance-api.conf配置文件，修改内容如下：

[DEFAULT]
enabled_backends = file:file, rbd:rbd
[glance_store]
default_backend = rbd
stores = rbd
#添加这个rbd这端=段配置
[rbd]
rbd_store_pool = images
rbd_store_user = glance
rbd_store_ceph_conf = /etc/ceph/ceph.conf

重启所有控制节点上glance_api容器，创建镜像测试

docker restart glance_api
openstack image create --file ./cirros-0.3.0-x86_64-disk.img \
--disk-format=qcow2 cirros

查看镜像已经active，说明对接成功
在这里插入图片描述

cinder对接ceph

在ceph节点上将ceph.conf和client.cinder.keyring复制到所有控制节点/etc/kolla/cinder-volume目录下：

scp /etc/ceph/ceph.conf /etc/ceph/ceph.client.cinder.keyring \
root@control-01:/etc/kolla/cinder-volume/
scp /etc/ceph/ceph.conf /etc/ceph/ceph.client.cinder.keyring \
root@control-02:/etc/kolla/cinder-volume/
scp /etc/ceph/ceph.conf /etc/ceph/ceph.client.cinder.keyring \
root@control-03:/etc/kolla/cinder-volume/

在所有控制节点修改/etc/kolla/cinder-volume/config.json，将ceph的文件映射到cinder_volume容器里：


    "command": "cinder-volume --config-file /etc/cinder/cinder.conf",
    "config_files": [
        {
            "source": "/var/lib/kolla/config_files/cinder.conf",
            "dest": "/etc/cinder/cinder.conf",
            "owner": "cinder",
            "perm": "0600"
        },
        #添加
        {
            "source": "/var/lib/kolla/config_files/ceph.client.cinder.keyring",
            "dest": "/etc/ceph/ceph.client.cinder.keyring",
            "owner": "cinder",
            "perm": "0600",
            "optional": true
        },
        #添加
        {
            "source": "/var/lib/kolla/config_files/ceph.conf",
            "dest": "/etc/ceph/ceph.conf",
            "owner": "cinder",
            "perm": "0600",
            "optional": true
        },
        {
            "source": "/var/lib/kolla/config_files/nfs_shares",
            "dest": "/etc/cinder/nfs_shares",
            "owner": "cinder",
            "perm": "0600",
            "optional": true
        }
    ],
    "permissions": [
        {
            "path": "/var/lib/cinder",
            "owner": "cinder:cinder",
            "recurse": true
        },
        {
            "path": "/var/log/kolla/cinder",
            "owner": "cinder:cinder",
            "recurse": true
        }
    ]
}

修改所有控制节点/etc/kolla/cinder-volume/cinder.conf

[DEFAULT]
enabled_backends= rbd
[rbd]
rbd_ceph_conf=/etc/ceph/ceph.conf
rbd_user=cinder
backend_host=rbd:volumes
rbd_pool=volumes
volume_backend_name=rbd
volume_driver=cinder.volume.drivers.rbd.RBDDriver
rbd_secret_uuid = 1fc95a3c-93ab-411d-9728-ed82e629dc7a	#这个值和/etc/kolla/password.yaml里cinder_rbd_secret_uuid的值一致

重启所有控制节点上cinder_volume容器，建卷测试

openstack volume create --size 2 test-vol1	#空白卷
openstack volume create --image cirros --size 2 test-vol1	#镜像卷

查看卷已经创建成功，说明对接成功
在这里插入图片描述

nova对接ceph

在ceph节点上将ceph.conf和client.cinder.keyring复制到所有计算节点/etc/kolla/nova-compute/目录下：

scp /etc/ceph/ceph.conf /etc/ceph/ceph.conf \
root@compute-01:/etc/kolla/cinder-volume/
scp /etc/ceph/ceph.conf /etc/ceph/ceph.client.cinder.keyring \
root@compute-02:/etc/kolla/cinder-volume/

在所有计算节点修改/etc/kolla/nova-compute/config.json，将ceph的文件映射到nova-compute容器里：

{
    "command": "nova-compute",
    "config_files": [
        {
            "source": "/var/lib/kolla/config_files/nova.conf",
            "dest": "/etc/nova/nova.conf",
            "owner": "nova",
            "perm": "0600"
        },
        {
            "source": "/var/lib/kolla/config_files/release",
            "dest": "/etc/nova/release",
            "owner": "nova",
            "perm": "0600",
            "optional": true
        },
        #添加
        {
            "source": "/var/lib/kolla/config_files/ceph.conf",
            "dest": "/etc/ceph/ceph.conf",
            "owner": "nova",
            "perm": "0600"
        },
        {
            "source": "/var/lib/kolla/config_files/auth.conf",
            "dest": "/var/lib/nova/.config/libvirt/auth.conf",
            "owner": "nova",
            "perm": "0600"
        }    ],
    "permissions": [
        {
            "path": "/var/log/kolla/nova",
            "owner": "nova:nova",
            "recurse": true
        },
        {
            "path": "/var/lib/nova",
            "owner": "nova:nova",
            "recurse": true
        }
    ]
}

在所有计算节点执行下面操作：

#查看一下ceph.client.cinder.keyring的内容
cat /etc/kolla/nova-compute/ceph.client.cinder.keyring |grep key
        key = AQBhZHxiuzIsMxAAr7nrPFDWu2sUp7yhJBHnTA==	#key对应的值后边会使用

#进入nova_compute容器执行下面操作
docker exec -it -u0 nova_compute bash
#注意，下面secret.xml文件中uuid值和/etc/kolla/password.yaml里cinder_rbd_secret_uuid的值一致
cat >secret.xml <<EOF	
<secret ephemeral='no' private='no'>
<uuid>1fc95a3c-93ab-411d-9728-ed82e629dc7a</uuid>		
<usage type='ceph'>
<name>client.cinder secret</name>
</usage>
</secret>
EOF
virsh secret-define --file secret.xml
virsh secret-set-value  1fc95a3c-93ab-411d-9728-ed82e629dc7a AQBhZHxiuzIsMxAAr7nrPFDWu2sUp7yhJBHnTA==
rm -f secret.xml

在所有计算节点修改/etc/kolla/nova-compute/nova.conf

[libvirt]
connection_uri = qemu+tcp://192.168.211.23/system
live_migration_inbound_addr = 192.168.211.23
virt_type = kvm
images_rbd_pool = vms
images_type = rbd
images_rbd_ceph_conf = /etc/ceph/ceph.conf
rbd_user = cinder
rbd_secret_uuid = 1fc95a3c-93ab-411d-9728-ed82e629dc7a

重启nova_compute容器

docker restart nova_compute

测试

#创建flavor
openstack flavor create --vcpu 1 --ram 1024 --disk=5 flavor1
#创建网络
openstack network create net1
#创建子网
openstack subnet create --subnet-range 192.168.11.0/24 --ip-version 4 --gateway 192.168.11.1 --network net1 subnet1
#创建虚拟机，从镜像启动
openstack server create --image cirros --flavor flavor1 --nic net-id=net1 test-vm1
#创建虚拟机，从卷启动
openstack server create --volume test-vol2 --flavor falvor1 --nic net-id=net1 test-vm2
#为虚拟机挂载卷
openstack server add volume test-vm2 test-vol1
#为虚拟机卸载卷
openstack server remove volume test-vm2 test-vol1

遇到的问题

  1. 下载镜像慢，导致部署失败
    在公网上找一台服务器，安装kolla-ansible，使用kolla-ansible -i xxx pull命令把所有镜像下载下来，然后打包传到本地，自己搭建一个镜像仓库
  2. glance对接ceph后创建镜像失败
    配置文件问题，rbd-backend要单独写一个section，具体参考上面的配置即可
  3. 创建从卷启动的虚拟机失败
    nova配置里rbd-secret-uuid和cinder配置里写的不一致导致，重新用virsh定义secret，保持两者一致即可
  4. 创建网络不能指定类型，只能使用vxlan网络
    感觉应该是global.yaml中enable_neutron_provider_networks没设置为true导致，但是因为我VMwareworkstation的虚拟机也没法使用vlan网络，所以跳过
林凡修
关注
  • 1
    点赞
  • 踩
  • 11
    收藏
    觉得还不错? 一键收藏
  • 2
    评论
专栏目录
Kolla ansible 部署 OpenStack Zed
不要再踩坑了
02-15 2232
根据官网的快速入门文档，使用Kolla-ansible部署OpenStack Zed
Kolla-ansible自动化部署openstack
qq_45382565的博客
09-02 8072
kolla-ansible
OpenStack Yoga安装部署，手把手使用kolla-ansible部署OpenStack
JamesCurtis的博客
02-03 5639
Kolla 的使命是提供用于运行 OpenStack 云的生产就绪容器和部署工具。Kolla Ansible 开箱即用，但允许完全定制。这允许经验最少的操作员快速部署 OpenStack，并随着经验的增长修改 OpenStack 配置以满足操作员的确切要求。Kayobe是 Kolla 的一个子项目，它使用 Kolla Ansible 和 Bifrost 将 OpenStack 控制平面部署到裸机。
Kolla-ansible部署OpenStack集群
最新发布
最爱雨的博客
04-11 1502
kolla-ansible openstack ceph
用kolla-ansible部署all-in-one openstack Zed版本
Magnet的博客
05-28 4847
目录kolla介绍简介kolla 的优势kolla 的缺点安装前的环境配置节点规划宿主机安装kvmKVM中先创建两个NAT的虚拟网络设备虚拟机硬件规划。OS安装完成后的系统配置更改 kolla介绍 简介 kolla 的使命是为 openstack 云平台提供⽣产级别的、开箱即⽤的交付能⼒。kolla 的基本思想是⼀切皆容器，将所有服务基于 Docker 运 ⾏，并且保证⼀个容器只跑⼀个服务（进程），做到最⼩粒度的运⾏ docker。 kolla 要实现 openetack 部署总体上分为两步，第⼀步是制作
ubuntu22.0.4 kolla多节点搭建openstack ，skyline
冲击
03-16 1546
ubuntu22.0.4 kolla 搭建openstack skline组件搭建
kolla-ansible 搭建 openstack多节点
m0_51077280的博客
05-24 1473
kolla ansible 安装部署 openstack 多节点
ubuntu下容器部署openstack
逆时针
06-06 4720
引言 基本步骤 安装操作系统 其他软件依赖 安装ansible 安装docker 下载kolla-ansble的源码 环境配置 基本环境检查 执行部署 openstack服务验证 对容器进行运维 注意事项 引言 目标： 尝试在一台物理机上利用kolla-ansible安装openstack-all in one环境。 最近研究kolla项目，主要是用容器来自动部署o...
doc-kolla-ansible-Release 10.1.0.dev260.pdf
08-11
"Kolla-Ansible OpenStack自动化部署" Kolla-Ansible是OpenStack官方认证的自动化部署工具，旨在提供生产级容器和部署工具，以便快速部署OpenStack云计算环境。Kolla-Ansible具有高度的定制性，允许操作员根据实际...
kolla-ansible部署openstack-ussuri.pdf
05-10
kolla-ansible部署openstack-ussuri.pdf
Kolla-Ansible的Multinodes离线部署
06-11
Kolla-Ansible的Multinodes离线部署。不包括yum源。pip源。docker仓库搭建。
Openstack_Kolla-Ansible
04-07
Openstack_Kolla-Ansible在Ubuntu 18.04上使用Kolla-Ansible部署多合一OpenStack 系统要求以下是在Kolla-Ansible中部署AIO OpenStack的建议最低要求： 在Ubuntu 18.04上安装必需的软件包在继续之前，需要安装许多...
Ceph学习笔记2-在Kolla-Ansible中使用Ceph后端存储
10-31
- 使用Kolla-Ansible请参考《使用Kolla-Ansible在CentOS 7上部署OpenStack Queens》； - 部署Ceph服务请参考《Ceph学习笔记1-Mimic版本多节点部署》。
利用Kolla-ansible部署OpenStack Zed版（单机双网卡）
qq_41158292的博客
01-28 1623
外网网卡：不能被分配IP但必须启用，否则安装neutron时会报错；密码可手动配置，也可以命令生成（推荐用命令），安装前可修改对应密码。内网网卡：暂时能访问Internet即可，下载必要依赖时有用。如果退出虚拟环境将无法使用openstack命令和docker。两个网卡都需要具备访问互联网的功能，具体配置后续会有。后续操作全部在虚拟环境中操作，退出虚拟环境如下。环境检测如果报错需配置all-in-one文件。
kolla-ansible搭建yoga版openstack
HaZ3876的博客
09-01 665
kolla-ansible工具部署yoga版openstack
kolla-ansible执行openstack对接ceph
weixin_34293141的博客
09-26 803
2019独角兽企业重金招聘Python工程师标准>>> ...
kolla-ansible 部署OpenStack云计算平台
weixin_56744753的博客
11-25 1125
官方推荐的测试版本是cirros-0.4.0-x86_64-disk 经过测试这个是可以的。0.3.4版本的测试镜像不可以通过ssh连接。安装openstack client。安装kolla-ansible。这边使用自己封装的镜像。docker导入镜像。提前拷贝镜像修改配置。
kolla-ansible自动化部署openstack云计算平台
m0_46652469的博客
05-31 1616
Kolla Ansible是一个基于Ansible的开源工具，用于在OpenStack云环境中部署和管理Docker容器化的OpenStack服务。Kolla Ansible提供了一组Ansible Playbooks和Roles，可以自动化地构建、部署和管理OpenStack服务的Docker容器。
OpenStack Kolla-Ansible部署Cinder块存储 对接Ceph，Proxmox
JamesCurtis的博客
02-06 1177
书接上回本章我们继续来完成OpenStack示例配置组件之Web Application中的Cinder块存储服务，OpenStack中的Cinder块存储对接Ceph。
使用kolla-ansible 单节点部署OpenStack
03-19
kolla-ansible是一个用于部署和管理OpenStack的工具，它基于Ansible自动化工具，并提供了一套预定义的角色和任务来简化OpenStack的部署过程。使用kolla-ansible进行单节点部署OpenStack的步骤如下： 1. 安装依赖：在部署节点上安装必要的软件和依赖项，包括Docker、Ansible等。 2. 配置kolla-ansible：创建kolla-ansible的配置文件，其中包括OpenStack的相关配置信息，如网络配置、认证信息等。 3. 生成部署配置：运行kolla-ansible的命令生成部署所需的配置文件，包括Docker镜像、网络配置、服务配置等。 4. 部署OpenStack：运行kolla-ansible的命令开始部署OpenStack，该过程会下载所需的Docker镜像，并在节点上启动相应的服务。 5. 验证部署：使用kolla-ansible提供的验证工具，检查OpenStack各个组件是否正常运行。 6. 使用OpenStack：完成部署后，可以通过OpenStack提供的API或者Web界面来管理和使用OpenStack。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 2
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值