网卡

ens37 192.168.140.200 桥接
ens33 192.168.56.3 桥接

cat /etc/sysconfig/network-scripts/ifcfg-ens33
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
#BOOTPROTO=dhcp
BOOTPROTO=static
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=ens33
#UUID=e5e54d63-4bf1-416b-914c-6f7040152312
DEVICE=ens33
ONBOOT=yes
IPADDR=192.168.56.3
NETMASK=255.255.255.0
GATEWAY=192.168.56.2
DNS=114.114.114.114

cat /etc/sysconfig/network-scripts/ifcfg-ens37
TYPE=Ethernet
PROXY_METHOD=none
NAME=ens37
DEVICE=ens37
ONBOOT=yes

cat /usr/lib/systemd/system/docker.service 
[Service]
ExecStart=/usr/bin/dockerd   --insecure-registry 192.168.140.200:4000 -H unix://
MountFlags=shared

修改docker镜像源

sudo vi /etc/docker/daemon.json 
​
{
"registry-mirrors": [
"https://kfwkfulq.mirror.aliyuncs.com",
"https://2lqq34jg.mirror.aliyuncs.com",
"https://pee6w651.mirror.aliyuncs.com",
"https://registry.docker-cn.com",
"http://hub-mirror.c.163.com"
],
"dns": ["8.8.8.8","8.8.4.4"]
}

配置pip加速

mkdir ~/.pipcat > ~/.pip/pip.conf << EOF[global] 
trusted-host=mirrors.aliyun.com 
index-url=https://mirrors.aliyun.com/pypi/simple/EOF

复制代码
重启docker：

systemctl restart docker

3. 安装依赖

yum install git
​
yum install -y epel-release  
​
yum install -y python-pip 
​
pip install -U pip 
​
yum install python-devel libffi-devel gcc openssl-devel libselinux-python

复制代码
4. 安装ansible

yum install ansible

5. 从github 获取Kolla和Kolla-Ansible

git clone https://github.com/openstack/kolla -b stable/stein
​
git clone https://github.com/openstack/kolla-ansible -b stable/stein# 如果已有镜像，只执行第二步即可

docker run -d -v /opt/registry:/var/lib/registry -p 4000:5000 --restart=always --name registry registry:2 

编辑 /usr/lib/systemd/system/docker.service，内容如下：

ExecStart=/usr/bin/dockerd 
ExecStart=/usr/bin/dockerd --insecure-registry 192.168.56.:43000 

作用是为私人镜像服务器添加SSL认证，表明我们的私人镜像服务器是安全的，这样才能正常的push镜像到私人服务器，如果不这样设置，则pull镜像时会报错
6. 安装依赖

# 手动安装kolla-ansible
python kolla-ansible/setup.py install
​
pip install -r ./kolla/requirements.txt 
​
pip install -r ./kolla-ansible/requirements.txt

执行python kolla-ansible/setup.py install报错

ERROR: Cannot uninstall 'PyYAML'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall.

解决

[root@docker01 home]# pip install -r ./kolla/requirements.txt  --ignore-installed PyYAML

继续报错

ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it resolves dependency conflicts.We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default.kolla-ansible 6.2.4.dev4 requires cryptography!=2.0,>=1.9, but you'll have cryptography 1.7.2 which is incompatible.

解决

pip install cryptography==1.9

7. 拷贝配置文件

cp -r ./kolla-ansible/etc/kolla /etc/
​
cp kolla-ansible/ansible/inventory/* .

单节点默认使用all-in-one不用做修改，多节点部署需要修改multinode
检查playbook文件配置是否正确

单节点

ansible -i all-in-one all -m ping

​

多节点

ansible -i multinode all -m ping

8. 生成随机密码

kolla-genpwd

使用kolla提供的密码生成工具自动生成，如果密码不填充，后面的部署环境检查时不会通过。
为了后面登录方便，可以自定义keystone_admin_password密码，这里改为admin

vi /etc/kolla/passwords.ymlkeystone_admin_password:admin

9. 修改globals.yml
   复制代码

vi /etc/kolla/globals.yml# 指定镜像的系统版本
kolla_base_distro: "centos"# 指定安装的方式，source为源码
kolla_install_type: "source"# openstack版本
openstack_release: "stein"# OpenStack使用的网络接口
network_interface: "[Bond0]"# 宿主机IP
kolla_internal_address: "[172.28.3.101]"# Neutron外部网络，必须是没有绑定ip的可用网卡，否则实例无法访问外部网络
neutron_external_interface: "[enp26s0f1]"# 如果单点部署，高可用设为no
enable_haproxy: "no"enable_placement: "yes"# 使用cinder存储
enable_cinder: "yes"
enable_glance: "yes"
enable_magnum: "yes"
enable_heat: "yes"
cinder_volume_group: "cinder-volumes"

# 如果使用lvm，需先创建cinder-volumes的卷组
enable_cinder_backend_lvm: "yes"

创建卷组的方法如下

1. dd if=/dev/zero of=./disk.img count=200 bs=512MB2. losetup -f3. losetup /dev/loop0 disk.img4. pvcreate /dev/loop05. vgcreate cinder-volumes /dev/loop0

10. 下载镜像

部署时，会检查本地有没有镜像，有的话，使用本地，没有，自动拉取，由于镜像特别大，先下载镜像到本地

kolla-ansible pull

拉取镜像的方法可以参考这篇博客：

https://xuchao918.github.io/2018/05/07/%E5%A6%82%E4%BD%95%E8%8E%B7%E5%8F%96Kolla%E7%9A%84OpenStack%E9%95%9C%E5%83%8F/

11. 开始部署
    11.1 带有kolla的引导服务器部署依赖关系

kolla-ansible -i ./all-in-one bootstrap-servers

11.2 对主机执行预部署检查

kolla-ansible -i ./all-in-one prechecks

执行kolla-ansible -i ./all-in-one bootstrap-servers报错

报错1

说明：这个错误其实是因为pip安装的ansible版本有问题，不是docker版本的问题。
解决：

pip uninstall ansible
pip install ansible==2.5.6

报错

TASK [baremetal : Install python2 and python-simplejson] ************************************************************************************************************************************
fatal: [docker01]: FAILED! => {"changed": true, "msg": "non-zero return code", "rc": 127, "stderr": "Shared connection to docker01 closed.\r\n", "stdout": "已加载插件：fastestmirror\r\nLoading mirror speeds from cached hostfile\r\n * base: ftp.sjtu.edu.cn\r\n * epel: ftp.iij.ad.jp\r\n * extras: mirror.bit.edu.cn\r\n * updates: ftp.sjtu.edu.cn\r\nhttps://yum.dockerproject.org/repo/main/centos/7/repodata/repomd.xml: [Errno 14] curl#6 - \"Could not resolve host: yum.dockerproject.org; 未知的错误\"\r\n正在尝试其它镜像。\r\n\r\n\r\n One of the configured repositories failed (Docker main Repository),\r\n and yum doesn't have enough cached data to continue. At this point the only\r\n safe thing yum can do is fail. There are a few ways to work \"fix\" this:\r\n\r\n     1. Contact the upstream for the repository and get them to fix the problem.\r\n\r\n     2. Reconfigure the baseurl/etc. for the repository, to point to a working\r\n        upstream. This is most often useful if you are using a newer\r\n        distribution release than is supported by the repository (and the\r\n        packages for the previous distribution release still work).\r\n\r\n     3. Run the command with the repository temporarily disabled\r\n            yum --disablerepo=docker-repo ...\r\n\r\n     4. Disable the repository permanently, so yum won't use it by default. Yum\r\n        will then just ignore the repository until you permanently enable it\r\n        again or use --enablerepo for temporary usage:\r\n\r\n            yum-config-manager --disable docker-repo\r\n        or\r\n            subscription-manager repos --disable=docker-repo\r\n\r\n     5. Configure the failing repository to be skipped, if it is unavailable.\r\n        Note that yum will try to contact the repo. when it runs most commands,\r\n        so will have to try and fail each time (and thus. yum will be be much\r\n        slower). If it is a very temporary problem though, this is often a nice\r\n        compromise:\r\n\r\n            yum-config-manager --save --setopt=docker-repo.skip_if_unavailable=true\r\n\r\nfailure: repodata/repomd.xml from docker-repo: [Errno 256] No more mirrors to try.\r\nhttps://yum.dockerproject.org/repo/main/centos/7/repodata/repomd.xml: [Errno 14] curl#6 - \"Could not resolve host: yum.dockerproject.org; 未知的错误\"\r\n/bin/sh: apt-get: 未找到命令\r\n", "stdout_lines": ["已加载插件：fastestmirror", "Loading mirror speeds from cached hostfile", " * base: ftp.sjtu.edu.cn", " * epel: ftp.iij.ad.jp", " * extras: mirror.bit.edu.cn", " * updates: ftp.sjtu.edu.cn", "https://yum.dockerproject.org/repo/main/centos/7/repodata/repomd.xml: [Errno 14] curl#6 - \"Could not resolve host: yum.dockerproject.org; 未知的错误\"", "正在尝试其它镜像。", "", "", " One of the configured repositories failed (Docker main Repository),", " and yum doesn't have enough cached data to continue. At this point the only", " safe thing yum can do is fail. There are a few ways to work \"fix\" this:", "", "     1. Contact the upstream for the repository and get them to fix the problem.", "", "     2. Reconfigure the baseurl/etc. for the repository, to point to a working", "        upstream. This is most often useful if you are using a newer", "        distribution release than is supported by the repository (and the", "        packages for the previous distribution release still work).", "", "     3. Run the command with the repository temporarily disabled", "            yum --disablerepo=docker-repo ...", "", "     4. Disable the repository permanently, so yum won't use it by default. Yum", "        will then just ignore the repository until you permanently enable it", "        again or use --enablerepo for temporary usage:", "", "            yum-config-manager --disable docker-repo", "        or", "            subscription-manager repos --disable=docker-repo", "", "     5. Configure the failing repository to be skipped, if it is unavailable.", "        Note that yum will try to contact the repo. when it runs most commands,", "        so will have to try and fail each time (and thus. yum will be be much", "        slower). If it is a very temporary problem though, this is often a nice", "        compromise:", "", "            yum-config-manager --save --setopt=docker-repo.skip_if_unavailable=true", "", "failure: repodata/repomd.xml from docker-repo: [Errno 256] No more mirrors to try.", "https://yum.dockerproject.org/repo/main/centos/7/repodata/repomd.xml: [Errno 14] curl#6 - \"Could not resolve host: yum.dockerproject.org; 未知的错误\"", "/bin/sh: apt-get: 未找到命令"]}to retry, use: --limit @/usr/share/kolla-ansible/ansible/kolla-host.retry

解决

查找哪个文件决定了url的值
find /usr/share/kolla-ansible/ -type f |xargs grep -i yum.dockerproject.org 
/usr/share/kolla-ansible/ansible/roles/baremetal/defaults/main.yml:docker_yum_url: "https://yum.dockerproject.org"

换了url

vim /usr/share/kolla-ansible/ansible/roles/baremetal/defaults/main.yml
docker_apt_url: "https://download.docker.com"
docker_apt_key_id: F76221572C52609Ddocker_yum_url: "https://download.docker.com"
docker_gpg_fingerprint: "58118E89F3A912897C070ADBF76221572C52609D"

报错

TASK [baremetal : Install docker rpm gpg key] ***********************************************************************************************************************************************
fatal: [docker01]: FAILED! => {"changed": false, "msg": "failed to fetch key at https://download.docker.com/gpg , error was: HTTP Error 404: Not Found"}to retry, use: --limit @/usr/share/kolla-ansible/ansible/kolla-host.retry

解决
找到下载gpg的控制代码

find /usr/share/kolla-ansible/ -type f |xargs grep -i gpg
/usr/share/kolla-ansible/ansible/roles/baremetal/templates/docker_yum_repo.j2:gpgcheck=1
/usr/share/kolla-ansible/ansible/roles/baremetal/templates/docker_yum_repo.j2:gpgkey={{docker_yum_url}}/gpg
/usr/share/kolla-ansible/ansible/roles/baremetal/tasks/pre-install.yml:- name: Install docker apt gpg key
/usr/share/kolla-ansible/ansible/roles/baremetal/tasks/pre-install.yml:    url: "{{ docker_apt_url }}/gpg"
/usr/share/kolla-ansible/ansible/roles/baremetal/tasks/pre-install.yml:- name: Install docker rpm gpg key
/usr/share/kolla-ansible/ansible/roles/baremetal/tasks/pre-install.yml:    key: "{{ docker_yum_url }}/gpg"
/usr/share/kolla-ansible/ansible/roles/baremetal/defaults/main.yml:#docker_gpg_fingerprint: "58118E89F3A912897C070ADBF76221572C52609D"

解决

vim /usr/share/kolla-ansible/ansible/roles/baremetal/templates/docker_yum_repo.j2
gpgcheck=0

报错

TASK [baremetal : Install deltarpm packages] ************************************************************************************************************************************************
failed: [docker01] (item=deltarpm) => {"changed": false, "item": "deltarpm", "msg": "Failure talking to yum: failure: repodata/repomd.xml from docker-repo: [Errno 256] No more mirrors to try.\nhttps://download.docker.com/repo/main/centos/7/repodata/repomd.xml: [Errno 14] curl#35 - \"Network file descriptor is not connected\""}to retry, use: --limit @/usr/share/kolla-ansible/ansible/kolla-host.retry

解决

vim /usr/share/kolla-ansible/ansible/roles/baremetal/templates/docker_yum_repo.j2baseurl={{docker_yum_url}}/linux/{{ansible_distribution|lower}}/{{ansible_distribution_major_version|lower}}/$basearch/stable

报错

TASK [baremetal : Install yum packages] *****************************************************************************************************************************************************
ok: [docker01] => (item=epel-release)
failed: [docker01] (item=docker-engine-1.12.0) => {"changed": false, "item": "docker-engine-1.12.0", "msg": "No package matching 'docker-engine-1.12.0' found available, installed or updated", "rc": 126, "results": ["No package matching 'docker-engine-1.12.0' found available, installed or updated"]}
ok: [docker01] => (item=git)
ok: [docker01] => (item=python-setuptools)
changed: [docker01] => (item=ntp)to retry, use: --limit @/usr/share/kolla-ansible/ansible/kolla-host.retry

解决

find /usr/share/kolla-ansible/ -type f |xargs grep -i docker-engine-1.12.0
/usr/share/kolla-ansible/ansible/roles/baremetal/defaults/main.yml: - docker-engine-1.12.0
首先yum list|grep docker找到本机可用的docker版本
然后将源文件中的版本替换掉
sed -i 's#docker-engine-1.12.0#docker-ce-19.03.13#g' /usr/share/kolla-ansible/ansible/roles/baremetal/defaults/main.yml

11.3 执行OpenStack部署

kolla-ansible -i ./all-in-one deploy

12. 后续的配置
    12.1 安装openstack CLI客户端：

pip install python-openstackclient

12.2 OpenStack需要一个openrc文件，其中设置了admin用户的凭证，依次执行：

kolla-ansible post-deploy 

. /etc/kolla/admin-openrc.sh

12.3 在浏览器输入IP即可访问，界面如图所示：

docker启动报错

-- Unit docker.service has begun starting up.
10月 19 19:08:36 docker01 dockerd[2706]: time="2020-10-19T19:08:36.198915487+08:00" level=info msg="Starting up"
10月 19 19:08:36 docker01 dockerd[2706]: time="2020-10-19T19:08:36.211571575+08:00" level=info msg="parsed scheme: \"unix\"" module=grpc
10月 19 19:08:36 docker01 dockerd[2706]: time="2020-10-19T19:08:36.211608513+08:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
10月 19 19:08:36 docker01 dockerd[2706]: time="2020-10-19T19:08:36.211634784+08:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0  <ni
10月 19 19:08:36 docker01 dockerd[2706]: time="2020-10-19T19:08:36.211645691+08:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
10月 19 19:08:56 docker01 dockerd[2706]: time="2020-10-19T19:08:56.212710000+08:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {unix:///run/containerd/containerd
10月 19 19:09:04 docker01 kernel: perf: interrupt took too long (6598 > 6595), lowering kernel.perf_event_max_sample_rate to 30000
10月 19 19:09:17 docker01 dockerd[2706]: time="2020-10-19T19:09:17.214059855+08:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {unix:///run/containerd/containerd
10月 19 19:09:36 docker01 dockerd[2706]: failed to start daemon: failed to dial "/run/containerd/containerd.sock": failed to dial "/run/containerd/containerd.sock": context deadline exceede
10月 19 19:09:36 docker01 systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
10月 19 19:09:36 docker01 systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit docker.service has failed.
-- 
-- The result is failed.
10月 19 19:09:36 docker01 systemd[1]: Unit docker.service entered failed state.
10月 19 19:09:36 docker01 systemd[1]: docker.service failed.
10月 19 19:09:36 docker01 polkitd[1096]: Unregistered Authentication Agent for unix-process:2699:93048 (system bus name :1.43, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, l
10月 19 19:09:38 docker01 systemd[1]: docker.service holdoff time over, scheduling restart.
10月 19 19:09:38 docker01 systemd[1]: Stopped Docker Application Container Engine.
-- Subject: Unit docker.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit docker.service has finished shutting down.
10月 19 19:09:38 docker01 systemd[1]: Closed Docker Socket for the API.
lines 2300-2338/2374 99%

解决

[root@docker01 yum.repos.d]# systemctl stop containerd
[root@docker01 yum.repos.d]# systemctl start containerd
[root@docker01 yum.repos.d]# systemctl status containerd
● containerd.service - containerd container runtimeLoaded: loaded (/usr/lib/systemd/system/containerd.service; disabled; vendor preset: disabled)Active: active (running) since 一 2020-10-19 19:10:47 CST; 4s agoDocs: https://containerd.ioProcess: 2779 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)Main PID: 2781 (containerd)Tasks: 10Memory: 24.6MCGroup: /system.slice/containerd.service└─2781 /usr/bin/containerd10月 19 19:10:47 docker01 containerd[2781]: time="2020-10-19T19:10:47.385333630+08:00" level=info msg="loading plugin \"io.containerd.grpc.v1.namespaces\"..." type=io.containerd.grpc.v1
10月 19 19:10:47 docker01 containerd[2781]: time="2020-10-19T19:10:47.385343459+08:00" level=info msg="loading plugin \"io.containerd.internal.v1.opt\"..." type=io.containerd.internal.v1
10月 19 19:10:47 docker01 containerd[2781]: time="2020-10-19T19:10:47.385384916+08:00" level=info msg="loading plugin \"io.containerd.grpc.v1.snapshots\"..." type=io.containerd.grpc.v1
10月 19 19:10:47 docker01 containerd[2781]: time="2020-10-19T19:10:47.385398282+08:00" level=info msg="loading plugin \"io.containerd.grpc.v1.tasks\"..." type=io.containerd.grpc.v1
10月 19 19:10:47 docker01 containerd[2781]: time="2020-10-19T19:10:47.385408654+08:00" level=info msg="loading plugin \"io.containerd.grpc.v1.version\"..." type=io.containerd.grpc.v1
10月 19 19:10:47 docker01 containerd[2781]: time="2020-10-19T19:10:47.385417555+08:00" level=info msg="loading plugin \"io.containerd.grpc.v1.introspection\"..." type=io.containerd.grpc.v1
10月 19 19:10:47 docker01 containerd[2781]: time="2020-10-19T19:10:47.385616959+08:00" level=info msg=serving... address=/run/containerd/containerd.sock.ttrpc
10月 19 19:10:47 docker01 containerd[2781]: time="2020-10-19T19:10:47.385644410+08:00" level=info msg=serving... address=/run/containerd/containerd.sock
10月 19 19:10:47 docker01 containerd[2781]: time="2020-10-19T19:10:47.385679993+08:00" level=info msg="containerd successfully booted in 0.022570s"
10月 19 19:10:47 docker01 systemd[1]: Started containerd container runtime.
Hint: Some lines were ellipsized, use -l to show in full.

[root@docker01 yum.repos.d]# systemctl restart docker

从官方源下载镜像
安装kolla-ansible

# git clone https://github.com/openstack/kolla-ansible -b stable/queens
# pip install kolla-ansible/

编辑globals.yml文件，设置相关参数

# vim /etc/kolla/globals.yml
kolla_install_type: "source"
kolla_base_distro: "centos"
openstack_release: "queens"

下载镜像

# kolla-ansible -i all-in-one bootstrap-servers
# kolla-ansible pull

手动构建镜像
下载kolla项目

# git clone https://github.com/openstack/kolla.git -b stable/queens

生成kolla-build.conf文件

# pip install tox
# cd kolla/
# tox -e genconfig

构建openstack镜像

//构建基于centos系统的source源码安装的openstack镜像

# kolla-build -t source -b centos

//或者，构建基于centos系统的binary二进制包安装的openstack镜像

# kolla-build -t binary -b centos

自动化拉取kolla镜像
由于OpenStack社区，已经开始正式将kolla镜像托管在DockerHub上。所以，我们还可以从Docker Hub上直接拉取kolla镜像，由于openstack镜像少则几十，多则上百，因此，这里我编写了一个bash脚本，用于自动化拉取queens版本的kolla镜像。

为了加快从docker hub上拉取镜像，这里，配置上阿里云的镜像加速器。

# cat /etc/docker/daemon.json 
{
"registry-mirrors": ["https://a5aghnme.mirror.aliyuncs.com"]
}

重启docker服务，生效

# systemctl daemon-reload && systemctl restart docker

拉取queens版本的kolla镜像

# cat 01_pull_kolla.sh 
#!/usr/bin/bashimage_tag=queens    #该变量，你可以根据自己需要进行修改# delete images
docker images | awk '{print $3}' | xargs docker rmi -f# pull public images
for public_images in memcached kolla-toolbox cron mongodb mariadb rabbitmq keepalived haproxy chrony iscsid tgtd
dodocker pull kolla/centos-source-$public_images:$image_tag
done# pull monitor manage images
# it is recommended to use telegraf + influxdb + grafana + collectd + Prometheus
for monitor_images in collectd telegraf grafana influxdb prometheus-server prometheus-haproxy-exporter prometheus-node-exporter prometheus-mysqld-exporter prometheus-memcached-exporter prometheus-cadvisor
dodocker pull kolla/centos-source-$monitor_images:$image_tag
done# pull log manage images
for log_images in fluentd elasticsearch kibana
dodocker pull kolla/centos-source-$log_images:$image_tag
done# pull nova
for nova in nova-compute nova-consoleauth nova-ssh nova-placement-api nova-api nova-compute-ironic nova-consoleauth nova-serialproxy nova-scheduler nova-novncproxy nova-conductor nova-libvirt
dodocker pull kolla/centos-source-$nova:$image_tag
done# pull keystone
for keystone in keystone keystone-fernet keystone-ssh
dodocker pull kolla/centos-source-$keystone:$image_tag
done# pull freezer
docker pull kolla/centos-source-freezer-api:$image_tag# pull glance 
for glance in glance-api glance-registry
dodocker pull kolla/centos-source-$glance:$image_tag
done# pull cinder
for cinder in cinder-volume cinder-api cinder-backup cinder-scheduler
dodocker pull kolla/centos-source-$cinder:$image_tag
done# pull neutron
for neutron in neutron-server neutron-lbaas-agent neutron-dhcp-agent neutron-l3-agent neutron-openvswitch-agent neutron-metadata-agent neutron-server-opendaylight opendaylight
dodocker pull kolla/centos-source-$neutron:$image_tag
done# pull openvswitch
for openvswitch in openvswitch-db-server openvswitch-vswitchd neutron-openvswitch-agent
dodocker pull kolla/centos-source-$openvswitch:$image_tag
done# pull ceilometer
for ceilometer in ceilometer-api ceilometer-compute ceilometer-notification ceilometer-central
dodocker pull kolla/centos-source-$ceilometer:$image_tag
done# pull gnocchi
for gnocchi in gnocchi-metricd gnocchi-api gnocchi-statsd
dodocker pull kolla/centos-source-$gnocchi:$image_tag
done# pull aodh
for aodh in aodh-evaluator aodh-api aodh-listener aodh-notifier
dodocker pull kolla/centos-source-$aodh:$image_tag
done# pull heat
for heat in heat-api heat-api-cfn heat-engine
dodocker pull kolla/centos-source-$heat:$image_tag
done# pull horizon
docker pull kolla/centos-source-horizon:$image_tag# pull murano
for murano in murano-api murano-engine
dodocker pull kolla/centos-source-$murano:$image_tag
done# pull magnum
for magnum in magnum-api magnum-conductor
dodocker pull kolla/centos-source-$magnum:$image_tag
done# pull senlin
for senlin in senlin-api senlin-engine
dodocker pull kolla/centos-source-$senlin:$image_tag
done# pull sahara
for sahara in sahara-engine sahara-api
dodocker pull kolla/centos-source-$sahara:$image_tag
done# pull trove
for trove in trove-api trove-taskmanager trove-conductor
dodocker pull kolla/centos-source-$trove:$image_tag
done# pull swift
for swift in swift-rsyncd swift-proxy-server swift-object-expirer swift-object swift-account swift-container swift-base
dodocker pull kolla/centos-source-$swift:$image_tag
done# pull ironic
for ironic in ironic-conductor ironic-pxe ironic-api ironic-inspector
dodocker pull kolla/centos-source-$ironic:$image_tag
done
docker pull kolla/centos-source-dnsmasq:pike
docker tag kolla/centos-source-dnsmasq:pike kolla/centos-source-dnsmasq:queens
docker rmi -f kolla/centos-source-dnsmasq:pike# pull cloudkitty
for cloudkitty in cloudkitty-api cloudkitty-processor panko-api
dodocker pull kolla/centos-source-$cloudkitty:$image_tag
done# pull kuryr
docker pull kolla/centos-source-kuryr-libnetwork:$image_tag# save images
images=`docker images | grep queens | awk '{print $1}'`
docker save -o kolla_queens_images.tar $images# clean pull's images
docker images | awk '{print $3}' | xargs docker rmi -f

将镜像push到本地Registry

# cat 02_push_kolla.sh 
#!/usr/bin/bash# load images
docker load --input kolla_queens_images.tarregistry=172.17.51.27:4000    #请将该registry地址，改为你自己环境的地址# tag images
images=`docker images | grep queens | awk '{print $1}'`
for images_tag in $images
dodocker tag $images_tag:queens $registry/$images_tag:queens
done# delete old's images
delete_images=`docker images | grep '^kolla' | awk '{print $1}'`
for delete_images1 in $delete_images
dodocker rmi $delete_images1:queens
done# push images
push_images=`docker images | grep queens | awk '{print $1}'`
for push_images1 in $push_images
dodocker push $push_images1:queens
done

综合，比较以上三种方法的优缺点。这里，推荐使用第三种方法，速度更快，也更便捷。