kolla安装openstack

admin

Quick Start
1 l0 H3 R: n4 C) D5 X' r' Q- a

[url=https://bugs.launchpad.net/kolla-ansible/+filebug?field.title=Quick%20Start%20in%20kolla-ansible&field.tags=&field.comment=%0A%0A%0AThis%20bug%20tracker%20is%20for%20errors%20with%20the%20documentation,%20use%20the%20following%20as%20a%20template%20and%20remove%20or%20add%20fields%20as%20you%20see%20fit.%20Convert%20[%20]%20into%20[x]%20to%20check%20boxes:%0A%0A-%20[%20]%20This%20doc%20is%20inaccurate%20in%20this%20way:%20______%0A-%20[%20]%20This%20is%20a%20doc%20addition%20request.%0A-%20[%20]%20I%20have%20a%20fix%20to%20the%20document%20that%20I%20can%20paste%20below%20including%20example:%20input%20and%20output.%20%0A%0AIf%20you%20have%20a%20troubleshooting%20or%20support%20issue,%20use%20the%20following%20%20resources:%0A%0A%20-%20Ask%20OpenStack:%20http://ask.openstack.org%0A%20-%20The%20mailing%20list:%20http://lists.openstack.org%0A%20-%20IRC:%20%27openstack%27%20channel%20on%20Freenode%0A%0A-----------------------------------%0ARelease:%209.3.2.dev22%20on%202020-05-28%2020:43:03%0ASHA:%20437c6a1e30182462308903c98c95bbee7b6e001a%0ASource:%20https://opendev.org/openstack/ko ... start.rst%0AURL:%20[/url]][/url]

9 v+ d3 z$ U6 ]* _
THIS PAGE LAST UPDATED: 2020-05-28 20:43:03
# U$ o6 O$ v  L' [6 k

This guide provides step by step instructions to deploy OpenStack using Kolla Ansible on bare metal servers or virtual machines.

Recommended reading¶

It’s beneficial to learn basics of both Ansible and Docker before running Kolla-Ansible.

Host machine requirements¶

The host machine must satisfy the following minimum requirements:

• 2 network interfaces
• 8GB main memory
• 40GB disk space
  
  ! Y' N  v' `) g9 v, D8 T1 G% x

See the support matrix for details of supported host Operating Systems.

( o' O  o1 \7 H& n- yInstall dependencies¶

Typically commands that use the system package manager in this section must be run with root privileges.

It is generally recommended to use a virtual environment to install Kolla Ansible and its dependencies, to avoid conflicts with the system site packages. Note that this is independent from the use of a virtual environment for remote execution, which is described in Virtual Environments.

• For Ubuntu, update the package index.
  sudo apt-get update
  8 N2 E* k- j# I: G8 x- ]2 H! b# [9 j
  
• Install Python build dependencies:
  For CentOS or RHEL 7, run:
  sudo yum install python-devel libffi-devel gcc openssl-devel libselinux-python
  " F* W' I2 c1 c
  
  For CentOS or RHEL 8, run:
  sudo dnf install python3-devel libffi-devel gcc openssl-devel python3-libselinux
  1 r/ d4 y# r" Y9 C# X: L+ [" |
  
  For Ubuntu, run:
  sudo apt-get install python-dev libffi-dev gcc libssl-dev python-selinux python-setuptools
  
  
  : [5 W$ E, @% F% W; h& H" o

Install dependencies using a virtual environment¶

If not installing Kolla Ansible in a virtual environment, skip this section.

• Install the virtualenv package.
  For CentOS or RHEL 7, run:
  sudo yum install python-virtualenv
  . u" `9 G: O" L! P4 r, d
  $ Z2 i& l6 n5 i9 G
  For CentOS or RHEL 8, run:
  sudo dnf install python3-virtualenv
  - ]" i) r: n; U( j( ^: U
  4 g2 s% b% A1 e( X/ ?+ |3 I
  For Ubuntu, run:
  sudo apt-get install python-virtualenv
    B4 y$ e$ N2 _0 x. I/ h: Q
  & _7 h* G9 |1 N+ Z4 Z% y7 A
• Create a virtual environment and activate it:
  virtualenv /path/to/virtualenvsource /path/to/virtualenv/bin/activate
  ' n" M. y! R; [6 H. V4 j
  
  The virtual environment should be activated before running any commands that depend on packages installed in it.
• Ensure the latest version of pip is installed:
  pip install -U pip
  , x7 Q, Y. Q3 Q( K9 @
  
• Install Ansible. Currently, Kolla Ansible requires Ansible 2.6 to 2.9.
  pip install 'ansible<2.10'
  : G3 n1 L+ [+ b6 `- P
  
  

8 K( j5 W9 I7 |1 ~Install dependencies not using a virtual environment¶

If installing Kolla Ansible in a virtual environment, skip this section.

• Install pip.
  For CentOS or RHEL, run:
  sudo easy_install pip
  5 M7 K/ n: E+ o- U
  ! s) z5 I0 C: \" Q$ d  N
  For Ubuntu, run:
  sudo apt-get install python-pip
  
  # _* c" ]" S9 m6 _" ]6 g
• Ensure the latest version of pip is installed:
  sudo pip install -U pip
  + m. j4 _, q# l' y9 N6 x! m/ `* I, N
  , [, i  L& t3 x& Y2 k! y
• Install Ansible. Currently, Kolla Ansible requires Ansible 2.6 to 2.9.
  For CentOS or RHEL, run:
  sudo yum install ansible
  " z* X2 h. A# _+ G( e" _
  
  For Ubuntu, run:
  sudo apt-get install ansible
  
  6 ?: j/ h: l- z
• If the version of Ansible provided by the distribution does not meet the above version requirements, install it via pip.
  sudo pip install 'ansible<2.10'
  
  / S0 I2 Y3 E6 v: t' f
  

! o) g/ a/ q2 ?+ y  v3 V5 L3 Z
Install Kolla-ansible¶Install Kolla-ansible for deployment or evaluation¶

• Install kolla-ansible and its dependencies using pip.
  If using a virtual environment:
  pip install kolla-ansible
  
  ( I4 w0 r7 S0 l6 b4 i0 M/ ^0 j% J
  If not using a virtual environment:
  sudo pip install kolla-ansible
  : b1 D& E) B* r* o6 M
  ! Q0 n- l6 U5 p' Z. {7 e
• Create the /etc/kolla directory.
  sudo mkdir -p /etc/kollasudo chown $USER:$USER /etc/kolla
  
  
• Copy globals.yml and passwords.yml to /etc/kolla directory.
  If using a virtual environment:
  cp -r /path/to/virtualenv/share/kolla-ansible/etc_examples/kolla/* /etc/kolla
  4 J0 W, o8 S5 _# u( z/ T2 L
  5 u" ?7 H/ Z, X3 F* Y) d$ v* {9 T
  If not using a virtual environment on CentOS or RHEL, run:
  cp -r /usr/share/kolla-ansible/etc_examples/kolla/* /etc/kolla
  
  5 p8 S% L9 |( P2 W  z
  If not using a virtual environment on Ubuntu, run:
  cp -r /usr/local/share/kolla-ansible/etc_examples/kolla/* /etc/kolla
  
  ! ]* B7 _+ `6 I; r; O( k7 z/ N' ]
• Copy all-in-one and multinode inventory files to the current directory.
  If using a virtual environment:
  cp /path/to/virtualenv/share/kolla-ansible/ansible/inventory/* .
  ' o+ L6 ^% s7 z
  
  If not using a virtual environment on CentOS or RHEL, run:
  cp /usr/share/kolla-ansible/ansible/inventory/* .
  ) a* o( r( {1 |' L  K8 \" @
  8 l  V7 f4 v1 h- R5 [+ t- P5 g
  If not using a virtual environment on Ubuntu, run:
  cp /usr/local/share/kolla-ansible/ansible/inventory/* .
  
  
  ) F/ ~. A# x6 K7 V4 H/ M, W

Install Kolla for development¶

• Clone kolla and kolla-ansible repositories from git.
  git clone https://github.com/openstack/kollagit clone https://github.com/openstack/kolla-ansible
  
  2 t9 p# s* P" w7 N' h& P: F- A" a
• Install requirements of kolla and kolla-ansible:
  If using a virtual environment:
  pip install ./kollapip install ./kolla-ansible
    b7 c5 F' V4 G4 |3 ]( g
  ! u" i7 T# F! S6 S/ J
  If not using a virtual environment:
  sudo pip install ./kollasudo pip install ./kolla-ansible
  4 B) N) H- b* k0 [
  
• Create the /etc/kolla directory.
  sudo mkdir -p /etc/kollasudo chown $USER:$USER /etc/kolla
  
  7 W  J% K& A) [) Y! @
• Copy the configuration files to /etc/kolla directory. kolla-ansible holds the configuration files ( globals.yml andpasswords.yml) in etc/kolla.
  cp -r kolla-ansible/etc/kolla/* /etc/kolla
  
  ) N' x( z4 q% o
• Copy the inventory files to the current directory. kolla-ansible holds inventory files ( all-in-one and multinode) in theansible/inventory directory.
  cp kolla-ansible/ansible/inventory/* .
  & j/ K+ Q( e( }2 ~7 Y* v4 _
  - R+ X$ C5 h: Q6 ~+ w) z
  7 V/ z0 `5 N% z. u

4 M9 W6 M  E6 q; W$ s: xConfigure Ansible¶

For best results, Ansible configuration should be tuned for your environment. For example, add the following options to the Ansible configuration file /etc/ansible/ansible.cfg:

[defaults]host_key_checking=Falsepipelining=Trueforks=100

2 K/ T9 O# l* ~: B0 z

Further information on tuning Ansible is available here.

Prepare initial configuration¶Inventory¶

The next step is to prepare our inventory file. An inventory is an Ansible file where we specify hosts and the groups that they belong to. We can use this to define node roles and access credentials.

Kolla-Ansible comes with all-in-one and multinode example inventory files. The difference between them is that the former is ready for deploying single node OpenStack on localhost. If you need to use separate host or more than one node, edit multinode inventory:

• Edit the first section of multinode with connection details of your environment, for example:
  [control]10.0.0.[10:12] ansible_user=ubuntu ansible_password=foobar ansible_become=true# Ansible supports syntax like [10:12] - that means 10, 11 and 12.# Become clause means "use sudo".[network:children]control# when you specify group_name:children, it will use contents of group specified.[compute]10.0.0.[13:14] ansible_user=ubuntu ansible_password=foobar ansible_become=true[monitoring]10.0.0.10# This group is for monitoring node.# Fill it with one of the controllers' IP address or some others.[storage:children]compute[deployment]localhost       ansible_connection=local become=true# use localhost and sudo
  
  
  To learn more about inventory files, check Ansible documentation.
• Check whether the configuration of inventory is correct or not, run:
  ansible -i multinode all -m ping
  2 Q4 x9 S& |0 g8 ?. H
  
  
  Note
  0 d. }+ A- s- ]  k% h
  Ubuntu might not come with python pre-installed. That will cause errors in ping module. To quickly install python with ansible you can run ansible -i multinode all -m raw -a "apt-get -y install python-dev"
  
  6 P  h- n4 U) b8 |6 x
  

Kolla passwords¶

Passwords used in our deployment are stored in /etc/kolla/passwords.yml file. All passwords are blank in this file and have to be filled either manually or by running random password generator:

For deployment or evaluation, run:

kolla-genpwd
7 L3 ^! Y+ T( I9 `2 B5 {

For development, run:

cd kolla-ansible/tools./generate_passwords.py

+ d5 I  L9 _8 ]
9 J2 ]/ h# Z$ l* oKolla globals.yml¶

globals.yml is the main configuration file for Kolla-Ansible. There are a few options that are required to deploy Kolla-Ansible:

• Image options
  User has to specify images that are going to be used for our deployment. In this guide DockerHub provided pre-built images are going to be used. To learn more about building mechanism, please refer Building Container Images.
  Kolla provides choice of several Linux distributions in containers:
  • CentOS
  • Ubuntu
  • Debian
  • RHEL
    
    
  For newcomers, we recommend to use CentOS 7, CentOS 8 or Ubuntu 18.04.
  kolla_base_distro: "centos"
  
  # A, A4 G& j, ~" t
  Next “type” of installation needs to be configured. Choices are:
  binary
  using repositories like apt or yum
  source
  using raw source archives, git repositories or local source directory
  
  # Y8 }! ^6 j- y6 o; f& t7 A
  # _$ {# E* @0 R2 e4 o! MNote
  
  This only affects OpenStack services. Infrastructure services like Ceph are always “binary”.
  
    G; y+ N0 P$ Q0 A+ q
  
  / |# G, }1 H! \Note
  9 ?$ Y9 X' A$ q* v$ p; M0 {- o
  Source builds are proven to be slightly more reliable than binary.
  
  kolla_install_type: "source"
  
  ( ?$ v8 q* ^& c5 X' i$ A
• Networking
  Kolla-Ansible requires a few networking options to be set. We need to set network interfaces used by OpenStack.
  First interface to set is “network_interface”. This is the default interface for multiple management-type networks.
  network_interface: "eth0"
  
    y& C) B; q0 |* q( c) t
  Second interface required is dedicated for Neutron external (or public) networks, can be vlan or flat, depends on how the networks are created. This interface should be active without IP address. If not, instances won’t be able to access to the external networks.
  neutron_external_interface: "eth1"
  & ^  S- P% A3 q% Z: m
  
  To learn more about network configuration, refer Network overview.
  Next we need to provide floating IP for management traffic. This IP will be managed by keepalived to provide high availability, and should be set to be not used address in management network that is connected to our network_interface.
  kolla_internal_vip_address: "10.1.0.250"
  
  
• Enable additional services
  By default Kolla-Ansible provides a bare compute kit, however it does provide support for a vast selection of additional services. To enable them, set enable_* to “yes”. For example, to enable Block Storage service:
  enable_cinder: "yes"
  
  
  Kolla now supports many OpenStack services, there is a list of available services. For more information about service configuration, Please refer to the Services Reference Guide.
• Virtual environment
  It is recommended to use a virtual environment to execute tasks on the remote hosts. This is covered Virtual Environments.
  
  

Deployment¶

After configuration is set, we can proceed to the deployment phase. First we need to setup basic host-level dependencies, like docker.

Kolla-Ansible provides a playbook that will install all required services in the correct versions.

The following assumes the use of the multinode inventory. If using a different inventory, such as all-in-one, replace the -i argument accordingly.

• For deployment or evaluation, run:
  • Bootstrap servers with kolla deploy dependencies:
    kolla-ansible -i ./multinode bootstrap-servers
    ' P8 |: L; d5 V
    & k8 W; D8 x" A# H' [
  • Do pre-deployment checks for hosts:
    kolla-ansible -i ./multinode prechecks
    
    
  • Finally proceed to actual OpenStack deployment:
    kolla-ansible -i ./multinode deploy
    
    
    . t* e; o4 W- E- {6 B0 t
• For development, run:
  • Bootstrap servers with kolla deploy dependencies:
    cd kolla-ansible/tools./kolla-ansible -i ../../multinode bootstrap-servers
    
    
  • Do pre-deployment checks for hosts:
    ./kolla-ansible -i ../../multinode prechecks
    $ M! ?2 c! Q* y8 H8 m
    ! `- [# t' v. B7 f
  • Finally proceed to actual OpenStack deployment:
    ./kolla-ansible -i ../../multinode deploy
    
    
    : _! U5 X9 t6 o% X4 \: v
  
  " V, U/ \2 N7 C2 S  z5 w; ?" V

When this playbook finishes, OpenStack should be up, running and functional! If error occurs during execution, refer to troubleshooting guide.

Using OpenStack¶

• Install the OpenStack CLI client:
  pip install python-openstackclient
  
  # w' Y! ^/ W  X: g/ _6 J
• OpenStack requires an openrc file where credentials for admin user are set. To generate this file:
  • For deployment or evaluation, run:
    kolla-ansible post-deploy. /etc/kolla/admin-openrc.sh
    5 W% r3 l7 [) I" ]$ [1 A
    
  • For development, run:
    cd kolla-ansible/tools./kolla-ansible post-deploy. /etc/kolla/admin-openrc.sh
    
    
    
• Depending on how you installed Kolla-Ansible, there is a script that will create example networks, images, and so on.
  • For deployment or evaluation, run init-runonce script on CentOS or RHEL:
    /usr/share/kolla-ansible/init-runonce
    $ d  l# [/ F- r9 `6 s
    9 S6 c* f0 V4 p+ S
    Run init-runonce script on Ubuntu:
    /usr/local/share/kolla-ansible/init-runonce
    
      T/ j( q' u4 f: u
  • For development, run:
    kolla-ansible/tools/init-runonce
    
    # Y6 q% e; X' @& h7 `# ~
  • 
    : I) `0 Z; ]+ \3 ~& x* R) \
    ; S+ T: D# k/ L" H
    
  
  

1 w: o3 i" t, I8 |7 _% j% @4 E, l

/ O3 V6 c7 W8 N4 w3 ~4 |) t

admin

安装环境准备
& I+ Y' |# e$ E7 V- {官方部署文档：
6 W7 Q6 o0 V9 p+ \) K) j0 f. C: lhttps://docs.openstack.org/kolla ... ser/quickstart.html
$ I" _: R1 p/ r( y% K! S) }8 h
. ~' X4 H6 _  e本次部署train版all-in-one单节点，使用一台centos7.8 minimal节点进行部署，该节点同时作为控制节点、计算节点、网络节点和cinder存储节点使用，同时也是kolla ansible的部署节点。
# u" t7 f  N" |7 q8 q2 z# G; a
kolla安装节点要求：

+ Q9 Z' s4 v+ N' Q" s' `3 }  n& j2 network interfaces
4 a; F5 M& D, }. ]8GB main memory
40GB disk space
6 M1 U3 R6 b7 o* y" {7 ?如果是vmware workstation环境，勾选处理器选项的虚拟化引擎相关功能，否则后面需要配置nova_compute_virt_type=qemu参数，这里选择勾选，跳过以下步骤。
6 Z+ |! f. g) T6 H" A+ x, P
# cat /etc/kolla/globals.yml
nova_compute_virt_type: "qemu"

# b( n' V% O7 g1 J+ h/ o#或者部署完成后手动调整
5 x. h+ E4 R4 K1 Q" ]" }& o[root@kolla ~]# cat /etc/kolla/nova-compute/nova.conf |grep virt_type
#virt_type = kvm
virt_type = qemu
& U; o3 j+ r) C% o  a$ M
[root@kolla ~]# docker restart nova_compute
0 c5 z" c/ W7 d: c3 ?, G5 \1
! m5 b0 d5 z3 s2
& k# {, O% D  c( e8 k0 T3
4
8 }1 E# t9 `" b6 y5
! z, S0 ^, l* I- j- P+ M& R6
7
. e/ B- l$ P8 `- @1 F' Z8
$ ]1 G9 `  c0 K. n& h9
kolla的安装要求目标机器至少两块网卡，本次安装使用2块网卡对应管理网络和外部网络两个网络平面，在vmware workstation虚拟机新增一块网卡ens37：

ens33，NAT模式，管理网络，正常配置静态IP即可。租户网络与该网络复用，租户vm网络不单独创建网卡
ens37，桥接模式，外部网络，无需配置IP地址，这个其实是让neutron的br-ex 绑定使用，虚拟机通过这块网卡访问外网。
ens37网卡配置参考：
! e; x& e& P6 z5 j: c% |https://docs.openstack.org/insta ... ing-controller.html
5 m% _0 O) z, `1 O9 s' N4 h& y
cat > /etc/sysconfig/network-scripts/ifcfg-ens37 <<EOF
- F$ h5 @! [( u' cNAME=ens37
DEVICE=ens37
TYPE=Ethernet
ONBOOT="yes"
( g, f) ]( z5 s: V: X; l: eBOOTPROTO="none"
; x9 }. `( x; vEOF

1 n! u; J% Q9 B4 E5 D8 T  T8 l#重新加载en37网卡设备
nmcli con reload && nmcli con up ens37
  t: ?- Q. b) @1 C1 R/ }4 c2 ~2 m( b1
8 ?5 X$ U+ l! I) V9 Q- }9 Y" g! b2
$ b* b2 S1 A4 N7 V3
4
5
* M' |! @- T) I6
7
8
" B+ d+ C( V/ E, c9
10
  |3 A" b/ f/ {# x5 c如果启用cinder还需要额外添加磁盘，这里以添加一块/dev/sdb磁盘为例，创建为物理卷并加入卷组。

pvcreate /dev/sdb
$ S6 h5 H$ f+ y# b4 Mvgcreate cinder-volumes /dev/sdb
; Z6 h2 o  D! r1
8 ~0 s: H, y( W* A6 ]0 d- h2
0 [4 X; ^; o) f4 \注意卷组名称为cinder-volumes，默认与后面的globals.yml中定义一致。

& ^  {: j; |: E2 D# N[root@kolla ~]# cat /etc/kolla/globals.yml | grep cinder_volume_group
#cinder_volume_group: "cinder-volumes"
1
2
5 K) S! }- h7 w$ M部署kolla ansible
配置主机名,kolla预检查时rabbitmq可能需要能够进行主机名解析

hostnamectl set-hostname kolla
1
. o* B4 v+ P, K, W3 p/ B; I安装依赖

yum install -y python-devel libffi-devel gcc openssl-devel libselinux-python
1
- p+ f& z; z. r) v安装 Ansible，注意版本，默认2.9应该可以满足要求
7 e  S: x' e4 I: L% m! V1 A
* H' s" f* i7 Q4 |; w- Syum install -y ansible
; b: y* [  \+ z, u  ?$ q  y2 E1
配置阿里云pip源，否则pip安装时会很慢

mkdir ~/.pip
! x; t4 ^& D. W* K" Qcat > ~/.pip/pip.conf << EOF
[global]
+ L+ ^  N+ ]9 a1 U1 l" H8 j  Xtrusted-host=mirrors.aliyun.com
' O3 S4 ~/ r( y+ zindex-url=https://mirrors.aliyun.com/pypi/simple/
8 [1 ~6 h+ f& o1 q, l# e; \* r" kEOF
1
2
3
8 E+ ]* P  ?4 ^( u4
5
6
' w8 P0 \9 T! M0 j* \安装 kolla-ansible

kolla版本与openstack版本对应关系：https://releases.openstack.org/teams/kolla.html
. m! s4 c. B$ B8 \4 V6 m# k
yum install -y epel-release
yum install -y python-pip
pip install -U pip
, b( E' D7 e8 v8 J! Z0 O/ I3 n( Opip install kolla-ansible==9.1.0 --ignore-installed PyYAML
2 N! q8 ~* M, c5 B& p# w2 F- r1
2
5 I  W/ T9 T4 u2 g: T# [3
$ G# @. W  a) @! ?: E: n1 }4
复制 kolla-ansible配置文件到当前环境
2 W: F6 M+ _- W# k3 ?+ ]8 M
mkdir -p /etc/kolla
( A! q/ ^! l( p% S1 ^chown $USER:$USER /etc/kolla
. K$ J( E  m# ~- D
4 z+ D% Y- V! l" ]* D# t+ [##Copy globals.yml and passwords.yml
! L: ]" l: S; ]$ w* K# _4 Kcp -r /usr/share/kolla-ansible/etc_examples/kolla/* /etc/kolla
. ^# q# m  a: W; C' t
9 r5 Q: E2 X5 q##Copy all-in-one and multinode inventory files
cp /usr/share/kolla-ansible/ansible/inventory/* .
; N8 p) T. b4 Q- R+ X% g1 u' F3 W! X1
+ l1 N9 C- j  x5 y0 S2
4 {/ ^0 {  _8 P. c3
6 t' z% t( B+ p. a) y4 d4
5
6
7
# |# e+ B: }! g, g$ e$ e8
; S* {. G6 v/ A8 k* Y' s) _  P修改ansible配置文件

cat << EOF | sed -i '/^\[defaults\]$/ r /dev/stdin' /etc/ansible/ansible.cfg
host_key_checking=False
pipelining=True
0 T0 c8 {8 t+ n6 n- hforks=100
; i8 M5 L" W4 VEOF
1
2
3
4
, v" H: O( l( Z. o8 T  _* W: j. u- `5
0 Z! }; m3 r* |默认有all-in-one和multinode两个inventory文件，这里使用all-in-one，来规划集群角色，配置默认即可

[root@kolla ~]# cat all-in-one | more
# These initial groups are the only groups required to be modified. The
1 f8 e6 A* P) h4 d# additional groups are for more control of the environment.
[control]
localhost       ansible_connection=local

[network]
localhost       ansible_connection=local
, Q4 X* K8 U1 C& _( [9 f
[compute]
; X- j3 \  e$ Z% m4 r7 I5 vlocalhost       ansible_connection=local
. p* O7 e. v1 n7 l4 c
[storage]
- F/ B% ~; I0 U7 i5 K' mlocalhost       ansible_connection=local
  r: W  h2 `5 z0 T. D
6 ^% u  V$ ?; o5 `0 x* q[monitoring]
, X  R, S" n9 b& O( B" qlocalhost       ansible_connection=local

# K, G! E9 A  B) b( Q3 m[deployment]
9 x" K& @! Z8 C! ^6 m9 nlocalhost       ansible_connection=local
' O- O3 _0 G* D5 Q6 O% u- m2 y0 [; e8 n...
1
2
3
4
- i+ R; t9 |; ^( m1 F/ R- W0 I( j5
6 P. i; [1 J5 _& Y7 b9 o6
" B' C! b: [9 A2 T% ~7
8
9
; F( L4 R) R+ y; P* g7 K10
/ f$ R" Z2 V, a; m& [+ N11
8 i1 M& x5 ?1 t4 c12
13
9 V; P7 T) T2 z9 e, ?# n' V9 |14
15
16
4 H+ r8 S: M+ R! V: a# I17
$ K- e* X0 L6 v. A0 _8 Y/ a* I18
19
: N$ |7 t: x8 |) [6 h20
21
9 y4 z: t2 Y+ ?) E3 v  A检查inventory配置是否正确，执行：
5 d' o' O- o- t0 @+ N; X
2 G* U1 x6 Q! a% }; L. vansible -i all-in-one all -m ping
1
1 N# D5 W7 n4 v% X8 _+ a: @生成openstack组件用到的密码，该操作会填充/etc/kolla/passwords.yml，该文件中默认参数为空。

) y3 t& a$ S7 ]+ mkolla-genpwd
$ @6 d& }' ~/ r9 s1
( A7 X9 @9 S/ B5 l* ~: O修改keystone_admin_password，可以修改为自定义的密码方便后续horizon登录，这里改为kolla。
  Z* f% |( W; b( ?7 X! \, |
$ sed -i 's#keystone_admin_password:.*#keystone_admin_password: kolla#g' /etc/kolla/passwords.yml
; N! w- ^# n/ ^4 u) d# L5 g; l+ [
$ cat /etc/kolla/passwords.yml | grep keystone_admin_password
6 K- f  y4 y6 G: U9 _) R: Okeystone_admin_password: kolla
: V9 B, [  [' I5 p1
# [( G, A! B% O- [2
3
% L7 i# w2 a/ L: r4
. `- s* u; ]4 Y. Z$ d修改全局配置文件globals.yml，该文件用来控制安装哪些组件，以及如何配置组件，由于全部是注释，这里直接追加进去，也可以逐个找到对应项进行修改。

& S/ ]+ q( d. `+ N  tcp /etc/kolla/globals.yml{,.bak}

1 A0 N0 Y5 b& w7 o7 Y: R, |cat >> /etc/kolla/globals.yml <<EOF

7 w# h$ s( U& }  e! M! @# Kolla options
kolla_base_distro: "centos"
kolla_install_type: "binary"
openstack_release: "train"
kolla_internal_vip_address: "192.168.93.200"

. y' q4 e6 l) \5 @0 G# Docker options
docker_registry: "registry.cn-shenzhen.aliyuncs.com"
docker_namespace: "kollaimage"
4 A; j3 W) g: Q
1 ~; K+ k, P8 W# Neutron - Networking Options
* w3 b6 T& q" q, r3 M7 L6 i9 pnetwork_interface: "ens33"
neutron_external_interface: "ens37"
neutron_plugin_agent: "openvswitch"
' ~; Y; j. I: j$ ?* y0 i' \# |/ Fenable_neutron_provider_networks: "yes"

, _. h$ c6 N. N. N: S# OpenStack services
enable_cinder: "yes"
enable_cinder_backend_lvm: "yes"
EOF
7 ^0 B$ e9 [7 ]2 l- v1
2
3
4
1 w3 |; v) ^, I. }0 P' a$ Z5
. q  X/ S3 T" k7 e6
3 r1 ~( t+ _7 i, e$ D7
8
9
10
11
12
; O4 q7 K6 }: l% v13
+ H% {: G' [4 h! H- K% r14
15
16
4 n9 Z4 |' n  y: G17
9 j+ B: m( T, l9 h. S" ]- v18
/ B/ h3 }# C7 e7 L( E* G$ v19
20
21
22
! _+ \* D& I' @$ v  m8 X23
6 q+ ?. k9 |6 m24
/ r$ E" L7 V8 N7 T4 N参数说明：

/ T& M5 N/ b: |kolla_base_distro: kolla镜像基于不同linux发型版构建，主机使用centos这里对应使用centos类型的docker镜像即可。
  ~) C' O; ^  t9 I8 Tkolla_install_type: kolla镜像基于binary二进制和source源码两种类型构建，实际部署使用binary即可。
openstack_release: openstack版本可自定义，会从dockerhub拉取对应版本的镜像
kolla_internal_vip_address: 单节点部署kolla也会启用haproxy和keepalived，方便后续扩容为高可用集群，该地址是ens33网卡网络中的一个可用IP。
" i0 ^3 i  P# z. v  Kdocker_registry: 默认从dockerhub拉取镜像，这里使用阿里云镜像仓库，也可以本地搭建仓库，提前推送镜像上去。但该仓库目前只有train和ussuri版本的镜像，如何自己推送镜像参考该博客的其他文章。
docker_namespace: 阿里云kolla镜像仓库所在的命名空间，dockerhub官网默认是kolla。
9 M9 f# E2 @2 ^' r* m; Pnetwork_interface: 管理网络的网卡
0 O3 {/ }& Q4 }/ l) vneutron_external_interface: 外部网络的网卡
neutron_plugin_agent: 默认启用openvswitch
enable_neutron_provider_networks: 启用外部网络
, q9 e1 o8 h2 _% J3 P5 Jenable_cinder: 启用cinder
enable_cinder_backend_lvm: 指定cinder后端存储为lvm
修改docker官方yum源为阿里云yum源，另外配置docker镜像加速，指定使用阿里云镜像加速。
2 i: z' g% Y+ c* S1 W/ ^( E" P
sed -i 's/^docker_yum_url/#&/' /usr/share/kolla-ansible/ansible/roles/baremetal/defaults/main.yml
: R4 j2 q0 A& g2 U( ?8 F+ Nsed -i 's/^docker_custom_config/#&/' /usr/share/kolla-ansible/ansible/roles/baremetal/defaults/main.yml

cat >> /usr/share/kolla-ansible/ansible/roles/baremetal/defaults/main.yml <<EOF
. b' c8 W6 N0 M; i. V: }docker_yum_url: "https://mirrors.aliyun.com/docker-ce/linux/{{ ansible_distribution | lower }}"
docker_custom_config: {"registry-mirrors": ["https://uyah70su.mirror.aliyuncs.com"]}
EOF
8 j6 E  m  _3 j1
2
8 n- u0 F1 [6 M  Z! h3
4
5
& Y4 _2 P4 _1 ?, t" d$ y9 B; ~( \( p6
* f: ?$ D- Q% q8 F" |: m7
( n( Z$ R$ n; x* e. l部署openstack组件
( Z" D; a: N( r- |- }& @部署openstack

#预配置，安装docker、docker sdk、关闭防火墙、配置时间同步等
kolla-ansible -i ./all-in-one bootstrap-servers

#部署前环境检查
kolla-ansible -i ./all-in-one prechecks
. S# a$ j+ _4 Z6 h& j
$ D4 O0 z2 L6 _( D9 o#拉取镜像，也可省略该步骤，默认会自动拉取
) j: i; I3 P/ C8 ~kolla-ansible -i ./all-in-one pull

#执行实际部署，拉取镜像，运行对应组件容器
' b2 T7 ^( B6 lkolla-ansible -i ./all-in-one deploy
6 d7 F0 I; V; M) b( J
#生成openrc文件
kolla-ansible post-deploy
1
2
3
4
; c; m! ]# {3 J- z5
6
7
8
1 S( A4 R$ z. F# F9
10
2 P- f& z* w. C" n% b1 P11
# p; @' _! {% D) w6 C* {+ O12
( ]# c( o3 \2 x" Q1 e. o: K0 n13
14
, @9 B$ J$ x. X1 \. ?以上部署没有报错中断说明部署成功，所有openstack组件以容器方式运行，查看容器

& J4 ^3 b( r  f1 l  E[root@kolla ~]# docker ps -a
* Y  u  h* ~0 ~  K2 dCONTAINER ID        IMAGE                                                                                        COMMAND                  CREATED             STATUS              PORTS               NAMES
325c17a52c79        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-chrony:train                      "dumb-init --single-…"   36 hours ago        Up 25 hours                             chrony
8 w  O. b5 O) T# }6218d98755ee        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-cron:train                        "dumb-init --single-…"   36 hours ago        Up 25 hours                             cron
0 K  l* X5 N3 ]+ I3 j, u5 w02b6598c1089        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-kolla-toolbox:train               "dumb-init --single-…"   36 hours ago        Up 25 hours                             kolla_toolbox
8 P3 w* E+ @3 F+ C8572e445abad        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-fluentd:train                     "dumb-init --single-…"   36 hours ago        Up 25 hours                             fluentd
f11a103c5ade        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-openstack-base:train              "dumb-init --single-…"   44 hours ago        Up 25 hours                             client
: Q5 `& V, X5 p! e( o5c91def3c963        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-horizon:train                     "dumb-init --single-…"   44 hours ago        Up 25 hours                             horizon
e024bd4f5dd3        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-heat-engine:train                 "dumb-init --single-…"   44 hours ago        Up 25 hours                             heat_engine
3 j8 z) D& U; [6 c; k2d1491bd9e1a        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-heat-api-cfn:train                "dumb-init --single-…"   44 hours ago        Up 25 hours                             heat_api_cfn
eeefcfb31a61        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-heat-api:train                    "dumb-init --single-…"   44 hours ago        Up 25 hours                             heat_api
7 T' o( O9 ?% T8 B! [5 Q  ^9b51b53448fc        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-neutron-metadata-agent:train      "dumb-init --single-…"   44 hours ago        Up 25 hours                             neutron_metadata_agent
9f88a6c0cf31        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-neutron-l3-agent:train            "dumb-init --single-…"   44 hours ago        Up 25 hours                             neutron_l3_agent
! g7 ~9 Y6 K: Z$ P" h0 Pa419cb3270a6        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-neutron-dhcp-agent:train          "dumb-init --single-…"   44 hours ago        Up 25 hours                             neutron_dhcp_agent
% i$ k5 p; A6 z9 K959f6faba972        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-neutron-openvswitch-agent:train   "dumb-init --single-…"   44 hours ago        Up 25 hours                             neutron_openvswitch_agent
cc1b081cf876        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-neutron-server:train              "dumb-init --single-…"   44 hours ago        Up 25 hours                             neutron_server
eea1a87feb43        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-openvswitch-vswitchd:train        "dumb-init --single-…"   44 hours ago        Up 25 hours                             openvswitch_vswitchd
376f81bf75a2        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-openvswitch-db-server:train       "dumb-init --single-…"   44 hours ago        Up 25 hours                             openvswitch_db
c68fd9a92d73        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-nova-compute:train                "dumb-init --single-…"   44 hours ago        Up 25 hours                             nova_compute
0 u: X4 }4 T2 F  j' k4 {- `2492e2a32c80        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-nova-libvirt:train                "dumb-init --single-…"   44 hours ago        Up 25 hours                             nova_libvirt
7 W  \) L9 R# [; s3802d199b29f        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-nova-ssh:train                    "dumb-init --single-…"   44 hours ago        Up 25 hours                             nova_ssh
1281c311ecd4        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-nova-novncproxy:train             "dumb-init --single-…"   44 hours ago        Up 25 hours                             nova_novncproxy
' @8 k& c; ?$ c- U5 q2e8c8478116b        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-nova-conductor:train              "dumb-init --single-…"   44 hours ago        Up 25 hours                             nova_conductor
) W6 J+ S6 G7 F" n* s8 ?950feb59b549        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-nova-api:train                    "dumb-init --single-…"   44 hours ago        Up 25 hours                             nova_api
49497e664922        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-nova-scheduler:train              "dumb-init --single-…"   44 hours ago        Up 25 hours                             nova_scheduler
4 b6 N' I8 n6 y0 A9 J5 ff5eb37b48f7d        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-placement-api:train               "dumb-init --single-…"   44 hours ago        Up 25 hours                             placement_api
! G' i0 [) |; i( e54cd0e3be101        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-cinder-backup:train               "dumb-init --single-…"   44 hours ago        Up 25 hours                             cinder_backup
b4efa4449e7f        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-cinder-volume:train               "dumb-init --single-…"   44 hours ago        Up 25 hours                             cinder_volume
159b669d2fd3        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-cinder-scheduler:train            "dumb-init --single-…"   44 hours ago        Up 25 hours                             cinder_scheduler
9fc7e6a4cb25        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-cinder-api:train                  "dumb-init --single-…"   44 hours ago        Up 25 hours                             cinder_api
b3f8f711f2b1        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-glance-api:train                  "dumb-init --single-…"   44 hours ago        Up 25 hours                             glance_api
760e92d698e2        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-keystone-fernet:train             "dumb-init --single-…"   44 hours ago        Up 25 hours                             keystone_fernet
95f235c4ac10        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-keystone-ssh:train                "dumb-init --single-…"   44 hours ago        Up 25 hours                             keystone_ssh
03306334ce19        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-keystone:train                    "dumb-init --single-…"   44 hours ago        Up 25 hours                             keystone
5173d4191567        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-rabbitmq:train                    "dumb-init --single-…"   44 hours ago        Up 25 hours                             rabbitmq
eb6bca26f6ce        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-tgtd:train                        "dumb-init --single-…"   44 hours ago        Up 25 hours                             tgtd
79fac2ca1b19        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-iscsid:train                      "dumb-init --single-…"   44 hours ago        Up 25 hours                             iscsid
4a3fcefc7009        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-memcached:train                   "dumb-init --single-…"   44 hours ago        Up 25 hours                             memcached
0773eaf446e4        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-mariadb:train                     "dumb-init -- kolla_…"   44 hours ago        Up 25 hours                             mariadb
* N0 e1 H2 N" {  _7 G7 j77f0beaa28e5        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-keepalived:train                  "dumb-init --single-…"   44 hours ago        Up 25 hours                             keepalived
2 i1 F8 M4 x5 s7 m' E" E  ~1 ?$ rb02b744d2da3        registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-haproxy:train                     "dumb-init --single-…"   44 hours ago        Up 25 hours                             haproxy
1
( Z9 o$ Q4 q: s8 [, r- x6 l, u# W& l2
0 a/ N2 n: I* H" E3
) f4 S) G+ l3 ~4
5
6
7
: z+ J/ b4 ^7 l% |; i* s8
9
, P" O* b7 @5 X$ ?) L/ z. K0 j10
11
) z4 a& t; n. Y& k) _/ U12
& \; `9 }2 ?* o13
5 q' p1 n! _2 [3 O# m: m! q4 u14
15
$ w+ j3 G$ N3 P9 C* o& [+ L6 N% c16
17
# C" }$ L: _0 T. j1 C6 S. u/ X7 {18
19
: K- M# S7 G) A+ }20
' U4 H3 r: E5 b! x. Q9 D, h21
22
* o! e  n. y) z9 g  H9 D7 G23
24
, g5 t; Q  Y- g. P25
: ^6 u) s$ O8 i, J' u6 P- Y6 P; e# m26
27
- v* D5 w" M: G, L3 e6 c* S+ L28
9 q1 j6 X; \! Q2 p3 q; ~; r0 e29
$ i7 c  [* E' ?# s* B9 e30
' J, }2 u+ K6 l# P* p( F+ T: b31
& B7 `$ \; [  z* I32
% G6 q3 c9 E6 J33
. q  b, q7 P) I, k34
35
36
8 i, A0 D2 l/ K* [/ a+ @" j9 x7 j0 f37
38
39
% w  i' q( w, e40
* C. P# O# w( S, X2 `3 u- W41
确认没有Exited等异常状态的容器

[root@kolla ~]# docker ps -a  | grep -v Up
  T2 ^* ~9 p# I6 y' v7 Q- F1
本次部署运行了39个容器
9 S; X) ?. k; x$ I! b; U
9 N+ f$ }- x, J& t[root@localhost kolla-env]# docker ps -a | wc -l
  r) f/ z4 c9 j6 H39
1
2
# k* N. T8 U& r' @! i' S2 j# `查看拉取的镜像，发现镜像数量与容器数量是一致的。
  N7 U( u* x& V9 @3 G
( i3 o# L1 S0 B! e$ Z6 T[root@kolla ~]# docker images
REPOSITORY                                                                             TAG                 IMAGE ID            CREATED             SIZE
8 O* f9 P' F7 m* M3 Yregistry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-glance-api                  train               aec757c5908a        2 days ago          1.05GB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-keystone-ssh                train               2c95619322ed        2 days ago          1.04GB
' q/ K- r3 S& H+ f& O7 K: [/ tregistry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-keystone-fernet             train               918564aa9c01        2 days ago          1.04GB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-keystone                    train               8d5f3ca2a73c        2 days ago          1.04GB
+ J  A" ^0 Z) a( W" o, T; W: M! Zregistry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-cinder-api                  train               500910236e85        2 days ago          1.19GB
  h* p: M8 }$ R9 L8 Q1 K2 nregistry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-cinder-volume               train               f76ebe1e133d        2 days ago          1.14GB
, W4 S* `0 n3 S' \! Eregistry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-cinder-backup               train               19342786a92c        2 days ago          1.13GB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-cinder-scheduler            train               920630f0ea6c        2 days ago          1.11GB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-heat-api                    train               517f6a0643ee        2 days ago          1.07GB
( O. M9 w9 \/ _0 O2 x4 E) \registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-heat-api-cfn                train               2d46b91d44ef        2 days ago          1.07GB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-heat-engine                 train               ab570c135dbc        2 days ago          1.07GB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-horizon                     train               a00ddb359ea5        2 days ago          1.2GB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-fluentd                     train               6a5b7be2551b        2 days ago          697MB
9 k: f4 X, G1 \1 Z6 C* K" ?registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-cron                        train               0f784cd532e2        2 days ago          408MB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-chrony                      train               374dabc62868        2 days ago          408MB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-iscsid                      train               575873f9e4b8        2 days ago          413MB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-haproxy                     train               9cf840548535        2 days ago          433MB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-keepalived                  train               b2a20ccd7d6a        2 days ago          414MB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-openstack-base              train               c35001fb182b        3 days ago          920MB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-nova-compute                train               93be43a73a3e        5 days ago          1.85GB
- y! c, W: E! N5 Mregistry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-placement-api               train               26f8c88c3c50        5 days ago          1.05GB
% d2 D2 M5 \3 S  h+ Rregistry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-nova-api                    train               2a9d3ea95254        5 days ago          1.08GB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-nova-novncproxy             train               e6acfbe47b2b        5 days ago          1.05GB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-nova-conductor              train               836a9f775263        5 days ago          1.05GB
1 m* f! [1 u+ e' X0 i! g1 f$ Cregistry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-nova-ssh                    train               f89a813f3902        5 days ago          1.05GB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-nova-scheduler              train               8061eaa33d21        5 days ago          1.05GB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-openvswitch-vswitchd        train               2b780c8075c6        5 days ago          425MB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-openvswitch-db-server       train               86168147b086        5 days ago          425MB
& H# D8 V' L% J7 n- W2 ?: Xregistry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-rabbitmq                    train               19cd34b4f503        5 days ago          487MB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-mariadb                     train               882472a192b5        6 days ago          593MB
- d8 a2 ~" r3 n1 @# g0 B- Hregistry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-neutron-dhcp-agent          train               a007b53f0507        7 days ago          1.04GB
5 b( s( W3 ~  [' p- _8 Nregistry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-neutron-metadata-agent      train               8bcff22221bd        7 days ago          1.04GB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-nova-libvirt                train               539673da5c25        7 days ago          1.25GB
. K) g4 l0 H8 W8 tregistry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-kolla-toolbox               train               a18a474c65ea        7 days ago          842MB
# b( H  B5 T1 w. M' @. mregistry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-tgtd                        train               ad5380187ca9        7 days ago          383MB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-memcached                   train               1fcf18645254        7 days ago          408MB
, K& P7 P8 Z2 F1 ?% cregistry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-neutron-server              train               539cfb7c1fd2        8 days ago          1.08GB
# T  O  E0 K) R8 u' Z6 H8 _. n' s0 R. Mregistry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-neutron-openvswitch-agent   train               95113c0f5b8c        8 days ago          1.08GB
registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-neutron-l3-agent            train               fbe9385f49ca        8 days ago          1.08GB
8 ~, i, V  D7 V( M4 L1
* k9 Q9 G+ r7 M2
* D; [) b3 _, U, s% O6 O% n3
8 M0 @5 U" O0 @1 D4
5
+ A+ [! X; ?# [+ A: I6
7
9 n6 O& L8 k& J8
9
10
11
12
! d2 Z2 y5 \# }( I+ |% _13
4 c+ O4 S" Y; a# i14
15
16
# C/ G6 t6 C0 @17
3 _* e3 @5 H0 U4 K- Y  G8 @: L18
19
20
21
2 ]. ^2 x; N  O+ s  S5 C22
& @3 j% b  E! b( z; }23
2 I7 t3 c& @: x' u- N% X! p6 a24
25
26
27
28
' R9 i6 g: H5 I2 _29
; v8 s( v& P( z9 W5 ~# Y30
0 E/ m% {  v% {3 w/ D- q  {* U31
' {4 q3 Z+ f! ^- d, J) G$ G5 a32
( ]0 |& A/ c6 y$ g% C4 N7 k  d33
8 y( b+ N- v5 p1 ^. s4 {34
- s% _. `) x$ o9 y, A35
36
37
" O1 {, t* R+ ~( _& l38
7 u$ ]/ p' ]' K1 R/ `, c39
% w, P7 h' ^) w: q1 M# [40
41
查看cinder使用的卷，自动创建了lvm

[root@kolla ~]# lsblk | grep cinder
├─cinder--volumes-cinder--volumes--pool_tmeta 253:3    0   20M  0 lvm  
+ G1 M0 o8 q! a0 K! P│ └─cinder--volumes-cinder--volumes--pool     253:5    0   19G  0 lvm  
9 Y3 J" f, x6 R└─cinder--volumes-cinder--volumes--pool_tdata 253:4    0   19G  0 lvm  
0 R! o& R. \! G2 k$ V  └─cinder--volumes-cinder--volumes--pool     253:5    0   19G  0 lvm  

[root@kolla ~]# lvs | grep cinder
  cinder-volumes-pool cinder-volumes twi-a-tz--  19.00g             0.00   10.55
& N: r; ?& u2 Z5 o5 e1
; e+ O% b$ b1 r1 ~& V2
5 P$ X6 S! `1 n3
4
5
6
7
8
查看网卡状态

[root@kolla ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
9 B! E' g" I0 i9 z1 B    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
& D8 f( u. R9 P: t    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:0c:4e:fe brd ff:ff:ff:ff:ff:ff
    inet 192.168.93.30/24 brd 192.168.93.255 scope global noprefixroute ens33
       valid_lft forever preferred_lft forever
, R* j0 l* a! g8 z. R& O. ?    inet 192.168.93.100/32 scope global ens33
: ]7 x. R% y( W) I       valid_lft forever preferred_lft forever
    inet6 fe80::7a6c:d06c:ee49:4cd5/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
2 H$ R" t6 O  N! G3: ens37: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master ovs-system state UP group default qlen 1000
1 q# m& a! s% [; u    link/ether 00:0c:29:0c:4e:08 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::20c:29ff:fe0c:4e08/64 scope link
       valid_lft forever preferred_lft forever
4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
0 A5 f8 k% {' B4 E3 o% g- f. O    link/ether 02:42:2a:d9:93:52 brd ff:ff:ff:ff:ff:ff
. v* K5 ]' F4 N+ F, P/ F    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
# W2 q" G  R9 E* u8 M7 [- @    inet6 fe80::42:2aff:fed9:9352/64 scope link
$ b, q: C& z3 O4 ~) {       valid_lft forever preferred_lft forever
6: veth0c46c6a@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
. D% n) C$ j8 W. S    link/ether 1a:ce:d7:61:d0:cc brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::18ce:d7ff:fe61:d0cc/64 scope link
  {" O' H! w/ j. ]* Q0 T. v5 H       valid_lft forever preferred_lft forever
7: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether de:e5:b7:4d:e8:b8 brd ff:ff:ff:ff:ff:ff
11: br-int: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN group default qlen 1000
5 b1 `  d% W( _: X) h    link/ether 52:14:05:ba:ce:4c brd ff:ff:ff:ff:ff:ff
5 z5 s  C. Z6 U13: br-tun: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
; c9 a8 m; y' Q4 ?/ H4 z    link/ether d2:5b:76:f5:01:49 brd ff:ff:ff:ff:ff:ff
: j9 j5 k, C1 W' H/ r  {14: br-ex: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:0c:29:0c:4e:08 brd ff:ff:ff:ff:ff:ff
22: qbr2749f64b-1f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default qlen 1000
+ f+ l/ X; w5 b' c# ]  u" g: h+ C    link/ether 3a:0d:ad:56:9d:9d brd ff:ff:ff:ff:ff:ff
3 k, N4 _  y0 m. \23: qvo2749f64b-1f@qvb2749f64b-1f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master ovs-system state UP group default qlen 1000
    link/ether c2:c5:8b:a6:72:8b brd ff:ff:ff:ff:ff:ff
    inet6 fe80::c0c5:8bff:fea6:728b/64 scope link
       valid_lft forever preferred_lft forever
: D+ ^0 m5 H: Y. w* }8 c; e) L24: qvb2749f64b-1f@qvo2749f64b-1f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master qbr2749f64b-1f state UP group default qlen 1000
    link/ether 3a:0d:ad:56:9d:9d brd ff:ff:ff:ff:ff:ff
- g0 i* Z7 \% a: m7 ^    inet6 fe80::380d:adff:fe56:9d9d/64 scope link
       valid_lft forever preferred_lft forever
; i% ^; z) q( r* ~  Q+ o6 M25: tap2749f64b-1f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc pfifo_fast master qbr2749f64b-1f state UNKNOWN group default qlen 1000
1 ^; V& ?- b  \! _  k    link/ether fe:16:3e:94:b5:71 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc16:3eff:fe94:b571/64 scope link
       valid_lft forever preferred_lft forever
26: qbr0a14e63d-2e: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default qlen 1000
: S7 N) n* f, M4 O7 P    link/ether 02:f9:32:c0:f4:b7 brd ff:ff:ff:ff:ff:ff
; K& `  d5 F5 U- {2 h2 }  y. c  Q. e27: qvo0a14e63d-2e@qvb0a14e63d-2e: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master ovs-system state UP group default qlen 1000
    link/ether 76:86:46:4c:4f:61 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::7486:46ff:fe4c:4f61/64 scope link
       valid_lft forever preferred_lft forever
$ \* h& J+ o: J: t# A28: qvb0a14e63d-2e@qvo0a14e63d-2e: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master qbr0a14e63d-2e state UP group default qlen 1000
    link/ether 02:f9:32:c0:f4:b7 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::f9:32ff:fec0:f4b7/64 scope link
       valid_lft forever preferred_lft forever
29: tap0a14e63d-2e: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc pfifo_fast master qbr0a14e63d-2e state UNKNOWN group default qlen 1000
    link/ether fe:16:3e:ee:08:6b brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc16:3eff:feee:86b/64 scope link
5 R+ ]$ s* V  _. f       valid_lft forever preferred_lft forever
1
: `* q+ \' D. S% G2 q1 K2
3
4
5
6
7
8
9
10
11
12
5 _$ g# @$ R* K4 A; @) K/ C13
3 }7 `5 `8 S  e14
% c  q4 Z. p; v$ [: j7 j& D15
; F; `+ V1 {' z* Z. Z( b% g$ G3 |3 o- I16
4 L( t, Y# O6 _17
) V5 G) @; w1 m' \- \$ m) ~18
19
# y! \- E5 U& R& o; F$ g5 I: c3 D20
21
0 l9 x, \/ j: ?6 w. M# f( W$ i! V22
% Q& |7 M: t7 H  x: v23
24
25
- p1 I6 f: c/ U; y  a8 E26
2 M& p6 Y4 Q  Y7 Q) }4 z- w! ~& F27
" b' z4 a0 }- D4 M; E( ]28
& P' t" b. f. r; ?& m29
" K. k/ b5 i, Z1 x30
0 W$ M+ E/ K/ _31
  a+ r' D+ v6 {1 H32
: ~; Q0 M- h4 l# p) C3 {* ?4 n3 p33
34
35
6 ~" S) t3 E0 C* j& j' n9 Y' k36
" p* i+ S' y+ s8 b) ]& P" e2 y37
% O4 u. @% @' Q2 g/ a5 D38
( u0 g# z6 \* }7 o& E39
# ?% [: j' F. P" Z2 A  W; e40
41
0 i; `: e2 T' Y5 P* y42
# E7 p4 n# E' ?  j43
  n' _( X/ \! P8 ~2 `44
( |9 D+ e$ P" K, U4 `* c45
46
  y+ a: o# i' M' y5 H47
+ P, O6 o( Q0 @48
+ ~& i% t; V' J/ p6 o- W49
! U( L% P# ]0 ~8 q0 d50
2 E- j1 V8 M& \" I51
52
53
$ w0 F* \; C4 l! {6 W54
" q8 Z% t; M% p55
56
57
58
) ~. i; \5 |( D. v) Y# S4 V& i: M59
60
61
' K2 [' A: x# N3 Y, j* S62
, B" \  ?3 O: ~63
$ @+ C$ o* |% Q9 s64
65
  Y$ a, ^1 K: V+ a# a另外需要注意，不要在该节点安装libvirt等工具，这些工具安装后可能会启用libvirtd和iscsid.sock等服务，kolla已经在容器中运行了这些服务，这些服务会调用节点上的sock文件，如果节点上也启用这些服务去抢占这些文件，会导致容器异常。默认kolla在预配置时也会主动禁用节点上的相关服务。

安装OpenStack客户端
yum安装openstack客户端
4 s  x7 C* f/ z9 v( F# i  h
#启用openstack存储库
yum install -y centos-release-openstack-train

#安装openstack客户端
yum install -y python-openstackclient

#启用selinux,安装openstack-selinux软件包以自动管理OpenStack服务的安全策略
: _- H" M9 q4 N$ qyum install -y openstack-selinux

#报错处理
pip uninstall urllib3
yum install -y python2-urllib3
1
2
3
& L! s& [9 G- M" Z4
6 x: o0 `4 h! }) t3 v- f* j% ?5
6
5 m/ s' d. N" i8 R7 [4 U3 v3 F7
8
9
' g$ T& Q8 Y) ^8 B/ ^, H10
) y8 d# L& S7 O3 [( K" I$ b" z11
& q1 e& g+ H% s12
kolla ansible提供了一个快速创建cirros demo实例的脚本/usr/share/kolla-ansible/init-runonce。
9 T( @0 m0 e% F* @
脚本需要cirros镜像，如果网络较慢可以使用浏览器下载放在/opt/cache/files目录下：
) A' @4 A% a2 v& G' ?  W1 ~
; H) _  C9 [, q/ n* w7 x' x2 l/ fwget https://github.com/cirros-dev/ci ... 4.0-x86_64-disk.img
mkdir -p /opt/cache/files/
! d9 a4 G$ E# d; Fmv cirros-0.4.0-x86_64-disk.img /opt/cache/files/
( L' `6 ]* \# ^, ]1
( X+ a# K/ w% w3 q  A+ o2
3
定义init-runonce示例脚本外部网络配置：
" V9 Z- t' M# l  W
#定义init-runonce示例脚本外部网络配置
# o1 O$ z" }6 K2 g/ nexport EXT_NET_CIDR='192.168.1.0/24'
export EXT_NET_RANGE='start=192.168.1.200,end=192.168.1.250'
5 d' U. s  u" a' bexport EXT_NET_GATEWAY='192.168.1.1'

5 }) S+ u& G4 X: B' R/ ~; ~#执行脚本，上传镜像到glance，创建内部网络、外部网络、flavor、ssh key，并运行一个实例
4 s6 ]9 h$ ~9 \4 N  b) msource /etc/kolla/admin-openrc.sh
1 B# o  z: v, s! Q8 d9 X) e/usr/share/kolla-ansible/init-runonce
1
2
' K( q3 E6 H, _. L' V$ H1 w3
4
5
6
- ~. y. ]/ G8 X+ e7 G& |7
8
参数说明：
5 J1 P. h6 ^* O
EXT_NET_CIDR 指定外部网络，由于使用桥接模式，直接桥接到了电脑的无线网卡，所以这里网络就是无线网卡的网段。
EXT_NET_RANGE 指定从外部网络取出一个地址范围，作为外部网络的地址池
" T/ s) X' d/ c$ H; A0 \3 E' j9 aEXT_NET_GATEWAY 外部网络网关，这里与wifi网络使用的网关一致
( {; U9 h- k- d: C根据最终提示运行实例

8 s0 Y- g* T' |( Z) s* l7 `$ O1 ~! Nopenstack server create \
4 a1 m5 F6 F4 M3 F4 q    --image cirros \
; C" A0 t+ V1 g; N, p# h1 H    --flavor m1.tiny \
    --key-name mykey \
2 c0 |7 W( @5 a8 ~3 ]. S  B    --network demo-net \
    demo1
) i$ a/ L, |9 ]" q: V* X% }- N# X: Y1
2
! P0 q) {5 B" {: {: V0 I* J; O3
- @* t, P/ l. j+ ], h$ G4
5
/ }4 K3 }. L8 d1 s3 O7 \6
也可以使用docker容器作为客户端
7 W1 g. s) U+ W( F
# T' [  u4 t$ b" F1 ?. S4 B& qdocker run -d --name client \
  --restart always \
1 i& z1 r. K. O4 L- s  -v /etc/kolla/admin-openrc.sh:/admin-openrc.sh:ro \
7 k4 y6 ?- @! h+ s  -v /usr/share/kolla-ansible/init-runonce:/init-runonce:rw \
" |0 Z, D# ^# l( W6 \  registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-openstack-base:train sleep infinity
8 x) k' t) @. f' j
9 E; a& w; B6 _* edocker exec -it client bash
. a0 s2 {$ k) A% W+ o6 v, J. k/ k  bsource /admin-openrc.sh
2 t/ D4 e7 H7 Y, `% E2 Bopenstack service list
4 S4 G- g$ I- [# D+ e1
3 b% `1 P  x+ y# z# J  j5 z( b2
/ U3 H( S! s8 u* q3
4
5
6
7
8
- b  A6 K$ `% X, K8 O& U( |9
访问openstack horizon
访问openstack horizon需要使用vip地址，节点上可以看到由keepalived容器生成的vip
: k# w) u6 W: k$ h- Y
[root@kolla ~]# ip a |grep ens33
- k) G( O' Q5 q+ q) Q' A7 ?+ p" |2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    inet 192.168.93.30/24 brd 192.168.93.255 scope global ens33
    inet 192.168.93.100/32 scope global ens33
1
2
) T( D# R2 G- L+ v/ E) w3
0 A/ b4 k5 ~2 \* t: W+ @4
* J: e0 }  f/ B3 _' V- ~浏览器直接访问该地址即可登录到horizon

http://192.168.93.100
0 z) p5 D. L1 P) l9 l- E. |
我这里的用户名密码为admin/kolla，信息可以从admin-openrc.sh中获取

[root@kolla ~]# cat /etc/kolla/admin-openrc.sh
# Clear any old environment that may conflict.
: q$ `: k7 D0 q, z+ _; N! ufor key in $( set | awk '{FS="="}  /^OS_/ {print $1}' ); do unset $key ; done
  k; ~5 y6 k' y  z" i: Z, u; Y! pexport OS_PROJECT_DOMAIN_NAME=Default
export OS_USER_DOMAIN_NAME=Default
export OS_PROJECT_NAME=admin
export OS_TENANT_NAME=admin
* t/ J. w- t) R6 ^& l0 [export OS_USERNAME=admin
export OS_PASSWORD=kolla
export OS_AUTH_URL=http://192.168.93.100:35357/v3
) T' e! K. e, }% w, Xexport OS_INTERFACE=internal
export OS_ENDPOINT_TYPE=internalURL
export OS_IDENTITY_API_VERSION=3
" O7 _% P4 C8 I- j* C: aexport OS_REGION_NAME=RegionOne
export OS_AUTH_PLUGIN=password
1
2
( R/ b: Z( e& ?! i" z4 b3
4
) b' p* F1 q# i2 H: Z8 O3 I5
6
7
8
7 N2 t! s5 E! v/ v4 j9
10
+ M6 s) y1 K0 @  B) k11
12
* d, e1 f( s' D3 F13
14
15
" x/ h. ]: V1 Y* f' b: X默认登录后如下
7 `/ q) y, c. p" W! n

6 R% Z5 e5 K2 B) t  R在horizion查看创建的网络和实例

登录实例控制台，验证实例与外网的连通性，cirros用户密码在初次登录时有提示：

为实例绑定浮动IP地址，方便从外部ssh远程连接到实例

点击+随机分配一个浮动IP


在kolla节点上ssh连接实例浮动IP，cirros镜像默认用户密码为cirros/gocubsgo，该镜像信息官网有介绍：
https://docs.openstack.org/image ... es.html#cirros-test
( ^1 @9 ^0 F  N! y5 Z1 L4 B
. n+ U. `, K' y5 t) S[root@kolla ~]# ssh cirros@192.168.1.248
cirros@192.168.1.248's password:
- H9 X* x4 Z5 m2 ?/ Y/ w$
3 |: g; @1 R$ h6 ]8 v$ j% s$
- T1 u! H# V5 T4 o6 ^+ U! W1
2
3
+ G, g3 g( y, k# r7 L4
9 f" b' Q( |4 d7 w或者在集群外部使用SecureCRT连接到实例。

2 l: L+ g2 }$ G$ }1 r9 _# v+ _
运行CentOS实例
9 t. @/ X# T5 t. P* i- }centos官方维护有相关cloud image，如果不需要进行定制，可以直接下载来运行实例。

参考：https://docs.openstack.org/image-guide/obtain-images.html

CentOS官方维护的镜像下载地址：
* ^3 q" M9 e3 q1 D0 I5 I7 G( Ehttp://cloud.centos.org/centos/7/images/
1 b& Y0 f" ~" \- i1 g( R- Q, z& _
也可以使用命令直接下载镜像，但是下载可能较慢，建议下载好在进行上传。以centos7.8为例：
4 M4 W: Q* p% ?* f% _2 X
wget http://cloud.centos.org/centos/7 ... icCloud-2003.qcow2c
# t0 _( z# s* T- S2 B" {$ s1
$ a+ A/ H" ^$ G0 B; o4 Q) L+ N8 J下载完成后上传镜像到openstack，直接在horizon上传即可。也可以使用命令上传。

注意：默认该镜像运行的实例只能使用ssh key以centos用户身份登录，如果需要使用root远程ssh连接到实例需要在上传前为镜像配置root免密并开启ssh访问。

6 O; o8 J5 ~6 O: V) [参考：https://blog.csdn.net/networken/article/details/106713658

2 [: O/ E5 S: J" }4 p1 d/ E0 @0 j另外我们的命令客户端在容器中，所有这里有些不方便，首先要将镜像复制到容器中，然后使用openstack命令上传。

这里复制到client容器的根目录下。

! g4 T7 k: F. Y+ G. G0 m[root@kolla ~]# docker cp CentOS-7-x86_64-GenericCloud-2003.qcow2c client:/

: c2 v1 O3 N' Q[root@kolla ~]# docker exec -it client bash
()[root@f11a103c5ade /]#
()[root@f11a103c5ade /]# source /admin-openrc.sh
  ?; `( S7 w- c
()[root@f11a103c5ade /]# ls | grep CentOS
CentOS-7-x86_64-GenericCloud-2003.qcow2c
1
2
+ M) N( @: S0 L( X2 B* ?3
4
5
3 x6 g+ _9 x; u# q# R6
7
8
执行以下openstack命令上传镜像
# M+ M9 `3 G, j" v* ]& w* J! E
* h! P. V" i1 F! t8 ^8 Kopenstack image create "CentOS78-image" \
9 T. ]' s- O( q0 B( s) I1 M3 h  --file CentOS-7-x86_64-GenericCloud-2003.qcow2c \
* ]4 I& `: C! ~  --disk-format qcow2 --container-format bare \
  --public
- a8 Y; K6 |% f* r2 ]# j8 M1
2
3
: ?- E% K. }' i# X* D1 r2 P4
- i, m* n! \9 X+ ^" U8 W4 l命令执行结果

()[root@f11a103c5ade ~]# openstack image create "CentOS78-image" \
6 P$ i3 S; l3 B) L6 P5 q8 `% \>   --file CentOS-7-x86_64-GenericCloud-2003.qcow2c \
  V( O) p2 ]" j2 n# q3 j2 R! N>   --disk-format qcow2 --container-format bare \
>   --public
+------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
- C8 o9 y7 g( t- q| Field            | Value                                                                                                                                                                                      |
+------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
4 @& G! s. t0 o7 R! L5 h| checksum         | 362d1e07d42bcbc61b839fb4269b173b                                                                                                                                                           |
* ^7 x' Y3 c" _2 Y- d| container_format | bare                                                                                                                                                                                       |
| created_at       | 2020-06-13T03:23:16Z                                                                                                                                                                       |
| disk_format      | qcow2                                                                                                                                                                                      |
( i$ ~9 {6 e, {% a0 n" l| file             | /v2/images/2d95d8a0-6fba-4ca8-9dde-8696eb7ebdbf/file                                                                                                                                       |
| id               | 2d95d8a0-6fba-4ca8-9dde-8696eb7ebdbf                                                                                                                                                       |
| min_disk         | 0                                                                                                                                                                                          |
| min_ram          | 0                                                                                                                                                                                          |
| name             | CentOS78-image                                                                                                                                                                           |
0 ?2 |9 J& w  C. R* p| owner            | 65850af146fe478ab13f59f7edf838ec                                                                                                                                                           |
$ c  n4 c& R: R| properties       | os_hash_algo='sha512', os_hash_value='aefa398f69e1746b420c44e5650f0dcf15926fb6f8c75f746bb2f48a04f7b140fdc745090f3d06b68fa0fe711ded7d822150765414e2a23f351efd2e181eb7b9', os_hidden='False' |
| protected        | False                                                                                                                                                                                      |
* o; A5 u. r) z8 i# @- ^| schema           | /v2/schemas/image                                                                                                                                                                          |
| size             | 385941504                                                                                                                                                                                  |
# `" I$ C3 T  n( }) k) R| status           | active                                                                                                                                                                                     |
| tags             |                                                                                                                                                                                            |
7 T% V7 F+ \1 l, H* r+ o+ D5 W| updated_at       | 2020-06-13T03:23:20Z                                                                                                                                                                       |
, {4 q1 V% J& C6 F* `+ f| virtual_size     | None                                                                                                                                                                                       |
| visibility       | public                                                                                                                                                                                     |
& d1 f5 }/ V( f. |; l9 |/ g8 c5 k+------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
, s1 D: P1 ~7 i) u. g2 q: r0 ^, G; h1
2
3
. N. ?# t8 ~$ u- Z4
, k+ G$ `# _# Q  A7 Q5
6
, A, p% R  R- Y: [7
8
( q) {, e$ j! w1 t9 D+ p9
10
( Q5 U0 E% Q, {1 N2 _" A11
12
9 {% k& j. G4 P0 z13
14
15
16
6 X; l0 U; l% j) X17
18
19
7 N  K- }- e% J7 z- K, E& P) i$ D20
21
22
9 Y; o$ |0 C( X4 J6 p0 w23
% j( \* i% J  s! B& V24
( B$ Q* J/ f; F4 p, j' d7 D; k25
1 \3 y( k& U# Z26
2 }6 ~# b/ ^" E+ A, I6 m, _27
在horizon中使用该镜像创建实例，其他信息直接使用之前demo创建的资源即可。创建完成后为实例绑定浮动IP。
+ x3 D( l& i/ C+ ]2 J. A
如果实例创建失败可以查看相关组件报错日志
" \7 u9 E% W4 T/ }. n5 _6 P
[root@kolla ~]# tail -100f /var/log/kolla/nova/nova-compute.log
- ]6 ?' q' o5 ]" ]1
未配置root密码连接实例
2 K3 ^, ]  ^2 b! @0 g如果没有提前定制镜像修改root密码，只能使用centos用户及sshkey登录，由于是在容器中运行的demo示例，ssh私钥也保存在容器的默认目录下，在容器中连接实例浮动IP测试
: e/ z/ g6 ^( d  P2 v
[root@kolla ~]# docker exec -it client bash
) Y4 U) a; Q4 a5 H()[root@f11a103c5ade /]#  ssh -i /root/.ssh/id_rsa centos@192.168.1.105
Last login: Sat Jun 13 05:47:49 2020 from 192.168.1.100
8 v5 u0 r" g# H+ v[centos@centos78 ~]$
1 c& T* }) W' I4 {8 x* V  q[centos@centos78 ~]$
- @( c5 o5 [9 Z' Z; E" O1
- V# A0 T8 D2 n' E) S# ^2
. H( P4 J3 D3 ?! c. z- C3
5 s- ~9 _6 l5 ?; F6 b4 l4
$ c# z1 n& A0 X& z6 A5
2 s* y) {  H! M$ ~7 Y或者取出该id_rsa私钥，使用SecureCRT登录：
1 Q" ?0 t+ t+ A* [! x% M5 l
# j( |8 ^! R. A8 E$ R配置root密码连接实例
, w7 c+ ?1 i6 A, S  [6 F
& E" Y! ?" y, D如果提前修改了镜像配置root密码，直接使用root用户密码登录实例即可，

! F- z5 r+ Y0 d$ s! L[root@kolla ~]# ssh root@192.168.1.105
root@192.168.1.105's password:
Last login: Sat Jun 13 05:51:53 2020 from 192.168.1.100
8 c- k2 t1 D. [. s[root@centos78 ~]#
[root@centos78 ~]# ip a
! @6 a9 A+ A+ v/ L: B$ V1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
: |' x6 U4 G! W2 f8 R0 O) y1 C  l       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc pfifo_fast state UP group default qlen 1000
    link/ether fa:16:3e:94:b5:71 brd ff:ff:ff:ff:ff:ff
# n# f3 e3 {( R8 I. Z0 S    inet 10.0.0.193/24 brd 10.0.0.255 scope global dynamic eth0
       valid_lft 84215sec preferred_lft 84215sec
  s5 U0 q% p. u! j    inet6 fe80::f816:3eff:fe94:b571/64 scope link
/ q( \, T) R# r: g! i: P       valid_lft forever preferred_lft forever
, @! C4 i9 n  [/ q! X[root@centos78 ~]#
[root@centos78 ~]# cat /etc/redhat-release
. x& O8 O0 u' i6 U- b, |CentOS Linux release 7.8.2003 (Core)
9 ?& f. x  Z, ]; B0 g( r1
% ^' Q& u0 b1 R6 u7 Q2
& y4 @, g  {& d6 Z$ [8 U' m3
- G7 Q$ j' H" c+ z# k4
% a/ c5 T4 W1 h4 @- |5
6
4 a" O6 }: k* N$ K% R7
8
$ m' A8 ?" Y" ~- ^( i9
10
11
% V7 y+ a8 C, L12
: b( N7 c4 ]+ E0 }4 E% T1 Q- l+ ^, E& t13
2 R4 T+ B1 d- f) W" t14
15
9 F1 X. @0 ]1 D7 ]16
5 a7 f/ q; z, m, Z! v17
18
: a/ Y/ x0 b. H19
$ y0 w. ]- U& [1 U' s1 x20
% w% A3 k! E* e0 m运行Ubuntu实例
下载镜像

$ Z& l7 {( |3 q  x6 y# e8 R0 E2 nwget https://cloud-images.ubuntu.com/ ... -cloudimg-amd64.img
1
: H, O4 I* Y$ v, `/ {上传镜像
2 c( A- ~* W! Z( W/ Y
openstack image create "Ubuntu1804" \
7 Y7 w" R! G5 N6 Q/ l6 L: o' r1 A) _  --file bionic-server-cloudimg-amd64.img \
  --disk-format qcow2 --container-format bare \
  --public
5 k: i5 _7 ]3 A! {8 Y$ _1
" q) r/ I  Q6 U2 O2
: L. I4 ^9 O6 P5 r. ?3 D3
4
+ E- T7 [0 B; g5 Z- M  H按照正常流程创建实例即可，ubuntu镜像默认用户为ubuntu，首次登陆使用sshkey方式，然后执行以下命令即可直接切换到root用户（centos无法使用该方式）

% U" m0 @1 F) \2 h) S$ sudo -i
1
  W3 ~8 x; D* U) V4 M, V" }. p. Q调整集群配置
集群部署完成后需要开启新的组件或者扩容，可以修改/etc/kolla/global.yml调整参数。
或者在/etc/kolla/config目录下创建自定义配置文件，例如
% P  i3 O6 @2 N
/ \$ P0 R  C* u6 q: ^  O3 W  [/ ]; f# mkdir -p /etc/kolla/config/nova
9 K5 i6 T& f# @' Z
# vim /etc/kolla/config/nova/nova.conf
1 R( {3 C( y/ h, }) Q[DEFAULT]
block_device_allocate_retries = 300
block_device_allocate_retries_interval = 3
1
9 N+ W, |! c: C' E- y2
. I" J5 M3 O; O$ g3
4
5
6
重新配置openstack，kolla会自动重建配置变动的容器组件。

, Q3 ?+ C# Y, `# K- l% Q: Fkolla-ansible -i all-in-one reconfigure -t nova
$ e, z; |; w$ ]4 t0 a5 C1
3 o- o, U, S% f, T# @kolla配置和日志文件
6 s1 [) _  u1 i7 Y7 _: u各个组件配置文件目录： /etc/kolla/
各个组件日志文件目录：/var/log/kolla/
清理kolla ansilbe集群
kolla-ansible destroy --include-images --yes-i-really-really-mean-it
' k2 ]0 ^  i! N5 `8 A5 R$ E
#或者
% \0 D1 \  [* X[root@kolla ~]# cd /usr/share/kolla-ansible/tools/
[root@all tools]# ./cleanup-containers
[root@all tools]# ./cleanup-host

5 P+ z3 J0 H6 j# a+ ~( A#重置cinder卷，谨慎操作
vgremove cinder-volume
. z9 |6 u2 d' k8 {9 J5 J————————————————
: X/ q+ B" ^: Z4 U
- S* b+ Z4 Z/ X7 U$ g, I