DevStack 部署 OpenStack 多节点_devstack多节点部署

为了做好运维面试路上的助攻手，特整理了上百道【运维技术栈面试题集锦】，让你面试不慌心不跳，高薪offer怀里抱！这次整理的面试题，小到shell、MySQL，大到K8s等云原生技术栈，不仅适合运维新人入行面试需要，还适用于想提升进阶跳槽加薪的运维朋友。本份面试集锦涵盖了总计 1000+ 道面试题，内容又全含金量又高网上学习资料一大堆，但如果学到的知识不成体系，遇到问题时只是浅尝辄止，不再深

Java老杨

935人浏览 · 2024-05-15 03:24:48

Java老杨 · 2024-05-15 03:24:48 发布

为了做好运维面试路上的助攻手，特整理了上百道 【运维技术栈面试题集锦】 ，让你面试不慌心不跳，高薪offer怀里抱！

这次整理的面试题，小到shell、MySQL，大到K8s等云原生技术栈，不仅适合运维新人入行面试需要，还适用于想提升进阶跳槽加薪的运维朋友。

本份面试集锦涵盖了

174 道运维工程师面试题
128道k8s面试题
108道shell脚本面试题
200道Linux面试题
51道docker面试题
35道Jenkis面试题
78道MongoDB面试题
17道ansible面试题
60道dubbo面试题
53道kafka面试
18道mysql面试题
40道nginx面试题
77道redis面试题
28道zookeeper

总计 1000+ 道面试题，内容又全含金量又高

174道运维工程师面试题

1、什么是运维?

2、在工作中，运维人员经常需要跟运营人员打交道，请问运营人员是做什么工作的?

3、现在给你三百台服务器，你怎么对他们进行管理?

4、简述raid0 raid1raid5二种工作模式的工作原理及特点

5、LVS、Nginx、HAproxy有什么区别?工作中你怎么选择?

6、Squid、Varinsh和Nginx有什么区别，工作中你怎么选择?

7、Tomcat和Resin有什么区别，工作中你怎么选择?

8、什么是中间件?什么是jdk?

9、讲述一下Tomcat8005、8009、8080三个端口的含义？

10、什么叫CDN?

11、什么叫网站灰度发布?

12、简述DNS进行域名解析的过程?

13、RabbitMQ是什么东西?

14、讲一下Keepalived的工作原理?

15、讲述一下LVS三种模式的工作过程?

16、mysql的innodb如何定位锁问题，mysql如何减少主从复制延迟?

17、如何重置mysql root密码?

网上学习资料一大堆，但如果学到的知识不成体系，遇到问题时只是浅尝辄止，不再深入研究，那么很难做到真正的技术提升。

需要这份系统化的资料的朋友，可以点击这里获取！

一个人可以走的很快，但一群人才能走的更远！不论你是正从事IT行业的老鸟或是对IT行业感兴趣的新人，都欢迎加入我们的的圈子（技术交流、学习资源、职场吐槽、大厂内推、面试辅导），让我们一起学习成长！

=========================
DevStack Component Timing
(times are in seconds)

wait_for_service 12
async_wait 102
osc 180
apt-get 71
test_with_retry 5
dbsync 7
pip_install 128
apt-get-update 1
run_process 27
git_timed 85

Unaccounted time 184

Total runtime 802

=================
Async summary

Time spent in the background minus waits: 322 sec
Elapsed time: 802 sec
Time if we did everything serially: 1124 sec
Speedup: 1.4015

This is your host IP address: 192.168.93.21
This is your host IPv6 address: ::1
Horizon is now available at http://192.168.93.21/dashboard
Keystone is serving at http://192.168.93.21/identity/
The default users are: admin and demo
The password: secret

Services are running under systemd unit files.
For more information see:
https://docs.openstack.org/devstack/latest/systemd.html

DevStack Version: 2024.1
Change: f4f09416ca8de09820b52599c7bcd2911b407466 Merge “Drop unused environments for TripleO and heat agents” 2024-03-19 18:55:14 +0000
OS Version: Ubuntu 22.04 jammy


修改网卡配置，增加`bridges`部分，使网桥开机自动启动

stack@devstack21:~/devstack$ sudo vim /etc/netplan/00-installer-config.yaml


应用网卡配置

stack@devstack21:~/devstack$ sudo netplan apply
stack@devstack21:~/devstack$


查看网卡信息

stack@devstack21:~/devstack$ 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
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:0c:29:b0:da:db brd ff:ff:ff:ff:ff:ff
altname enp2s1
inet 192.168.93.21/24 brd 192.168.93.255 scope global ens33
valid_lft forever preferred_lft forever
inet6 fe80::20c:29ff:feb0:dadb/64 scope link
valid_lft forever preferred_lft forever
3: ens37: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master ovs-system state UP group default qlen 1000
link/ether 00:0c:29:b0:da:e5 brd ff:ff:ff:ff:ff:ff
altname enp2s5
inet6 fe80::20c:29ff:feb0:dae5/64 scope link
valid_lft forever preferred_lft forever
4: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 22:0d:02:9f:90:1d brd ff:ff:ff:ff:ff:ff
5: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether f2:ad:f1:af:54:9a brd ff:ff:ff:ff:ff:ff
6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:f2:bf:a4 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
7: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
link/ether 00:0c:29:b0:da:e5 brd ff:ff:ff:ff:ff:ff
inet6 fe80::20c:29ff:feb0:dae5/64 scope link
valid_lft forever preferred_lft forever


查看网桥信息

stack@devstack21:~/devstack$ sudo ovs-vsctl show
8fc32620-e49f-4e8a-87a1-675d4185e1aa
Manager “ptcp:6640:127.0.0.1”
is_connected: true
Bridge br-int
fail_mode: secure
datapath_type: system
Port br-int
Interface br-int
type: internal
Port patch-br-int-to-provnet-4ff27886-1c19-4ba4-bd52-05e6c6524575
Interface patch-br-int-to-provnet-4ff27886-1c19-4ba4-bd52-05e6c6524575
type: patch
options: {peer=patch-provnet-4ff27886-1c19-4ba4-bd52-05e6c6524575-to-br-int}
Bridge br-ex
fail_mode: standalone
Port br-ex
Interface br-ex
type: internal
Port ens37
Interface ens37
Port patch-provnet-4ff27886-1c19-4ba4-bd52-05e6c6524575-to-br-int
Interface patch-provnet-4ff27886-1c19-4ba4-bd52-05e6c6524575-to-br-int
type: patch
options: {peer=patch-br-int-to-provnet-4ff27886-1c19-4ba4-bd52-05e6c6524575}
ovs_version: “2.17.9”


此时已经可以登录dashboard，并创建虚拟机，默认账号为`admin/secret`。

http://192.168.93.21/


#### 安装计算节点


以下操作在计算节点执行。


从neutron文件夹下复制计算节点示例配置文件

stack@devstack22:~$ pwd
/opt/stack
stack@devstack22:~$ cd devstack
stack@devstack22:~$ egrep -v “^#|$” …/neutron/devstack/ovn-compute-local.conf.sample > ./local.conf


配置文件修改后如下：

cat >local.conf<<‘EOF’
[[local|localrc]]

git_base

GIT_BASE=“https://github.com”
#GIT_BASE=https://opendev.org
#GIT_BASE=http://git.trystack.cn

password

ADMIN_PASSWORD=secret
DATABASE_PASSWORD= $ADMIN_PASSWORD RABBIT_PASSWORD=$ ADMIN_PASSWORD
SERVICE_PASSWORD= $ADMIN_PASSWORD SERVICE_TOKEN=$ ADMIN_PASSWORD

OVN

Q_AGENT=ovn
NEUTRON_AGENT= $Q_AGENT Q_ML2_PLUGIN_MECHANISM_DRIVERS=ovn,logger Q_ML2_PLUGIN_TYPE_DRIVERS=local,flat,vlan,geneve Q_ML2_TENANT_NETWORK_TYPE="geneve" LOGFILE=$ DEST/logs/stack.sh.log
enable_plugin neutron https://opendev.org/openstack/neutron
disable_all_services
enable_service n-cpu
enable_service placement-client
enable_service ovn-controller
enable_service q-ovn-metadata-agent
SERVICE_HOST=192.168.93.21
RABBIT_HOST= $SERVICE_HOST Q_HOST=$ SERVICE_HOST
OVN_SB_REMOTE=tcp: $SERVICE_HOST:6642 OVN_BUILD_MODULES=True HOST_IP=192.168.93.22 NOVA_VNC_ENABLED=True NOVNCPROXY_URL=http://$ SERVICE_HOST:6080/vnc_lite.html
VNCSERVER_LISTEN= $HOST_IP VNCSERVER_PROXYCLIENT_ADDRESS=$ VNCSERVER_LISTEN

Neutron options

Q_USE_SECGROUP=True
FLOATING_RANGE=“192.168.72.0/24”
Q_FLOATING_ALLOCATION_POOL=start=192.168.72.110,end=192.168.72.120
PUBLIC_NETWORK_GATEWAY=“192.168.72.8”
PUBLIC_INTERFACE=ens37

Open vSwitch provider networking configuration

Q_USE_PROVIDERNET_FOR_PUBLIC=True
OVS_PHYSICAL_BRIDGE=br-ex
PUBLIC_BRIDGE=br-ex
OVS_BRIDGE_MAPPINGS=public:br-ex
EOF


主要配置参数说明：


* `HOST_IP`: 本机IP地址
* `SERVICE_HOST`：必须是控制节点IP地址


安装计算节点

$ ./stack.sh


确认安装完成

…

DevStack Component Timing
(times are in seconds)

wait_for_service 7
async_wait 0
osc 0
apt-get 264
pip_install 103
apt-get-update 1
run_process 4
git_timed 45

Unaccounted time 100

Total runtime 524

=================
Async summary

Time spent in the background minus waits: 1 sec
Elapsed time: 524 sec
Time if we did everything serially: 525 sec
Speedup: 1.00191

This is your host IP address: 192.168.93.22
This is your host IPv6 address: ::1

Services are running under systemd unit files.
For more information see:
https://docs.openstack.org/devstack/latest/systemd.html

DevStack Version: 2024.1
Change: f4f09416ca8de09820b52599c7bcd2911b407466 Merge “Drop unused environments for TripleO and heat agents” 2024-03-19 18:55:14 +0000
OS Version: Ubuntu 22.04 jammy


修改网卡配置，增加`bridges`部分，使网桥开机自动启动

stack@devstack22:~/devstack$ sudo vim /etc/netplan/00-installer-config.yaml


应用网卡配置

stack@devstack22:~/devstack$ sudo netplan apply
stack@devstack22:~/devstack$


查看网卡信息

stack@devstack22:~/devstack$ 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
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:0c:29:31:a7:2c brd ff:ff:ff:ff:ff:ff
altname enp2s1
inet 192.168.93.22/24 brd 192.168.93.255 scope global ens33
valid_lft forever preferred_lft forever
inet6 fe80::20c:29ff:fe31:a72c/64 scope link
valid_lft forever preferred_lft forever
3: ens37: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master ovs-system state UP group default qlen 1000
link/ether 00:0c:29:31:a7:36 brd ff:ff:ff:ff:ff:ff
altname enp2s5
inet6 fe80::20c:29ff:fe31:a736/64 scope link
valid_lft forever preferred_lft forever
4: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 22:0d:02:9f:90:1d brd ff:ff:ff:ff:ff:ff
5: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 06:0d:1b:71:58:0e brd ff:ff:ff:ff:ff:ff
6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:42:16:35 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
7: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
link/ether 00:0c:29:31:a7:36 brd ff:ff:ff:ff:ff:ff
inet6 fe80::20c:29ff:fe31:a736/64 scope link
valid_lft forever preferred_lft forever
8: genev_sys_6081: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65000 qdisc noqueue master ovs-system state UNKNOWN group default qlen 1000
link/ether 1e:dd:eb:ff:7a:66 brd ff:ff:ff:ff:ff:ff
inet6 fe80::f4be:3fff:fe9b:6d89/64 scope link
valid_lft forever preferred_lft forever


查看网桥信息

stack@devstack22:~/devstack$ sudo ovs-vsctl show
15b21aff-829b-4c9f-8ef6-1fa372eddb3a
Manager “ptcp:6640:127.0.0.1”
is_connected: true
Bridge br-ex
fail_mode: standalone
Port br-ex
Interface br-ex
type: internal
Port ens37
Interface ens37
Port patch-provnet-4ff27886-1c19-4ba4-bd52-05e6c6524575-to-br-int
Interface patch-provnet-4ff27886-1c19-4ba4-bd52-05e6c6524575-to-br-int
type: patch
options: {peer=patch-br-int-to-provnet-4ff27886-1c19-4ba4-bd52-05e6c6524575}
Bridge br-int
fail_mode: secure
datapath_type: system
Port patch-br-int-to-provnet-4ff27886-1c19-4ba4-bd52-05e6c6524575
Interface patch-br-int-to-provnet-4ff27886-1c19-4ba4-bd52-05e6c6524575
type: patch
options: {peer=patch-provnet-4ff27886-1c19-4ba4-bd52-05e6c6524575-to-br-int}
Port ovn-2018dc-0
Interface ovn-2018dc-0
type: geneve
options: {csum=“true”, key=flow, remote_ip=“192.168.93.21”}
bfd_status: {diagnostic=“No Diagnostic”, flap_count=“1”, forwarding=“true”, remote_diagnostic=“Neighbor Signaled Session Down”, remote_state=up, state=up}
Port br-int
Interface br-int
type: internal
ovs_version: “2.17.9”


#### 节点发现


以下操作在控制节点执行。


切换到管理员用户

stack@devstack21:~/devstack$ . openrc admin admin
WARNING: setting legacy OS_TENANT_NAME to support cli tools.
stack@devstack21:~/devstack$


执行节点发现脚本

stack@devstack21:~/devstack$ pwd
/opt/stack/devstack
stack@devstack21:~/devstack$ ./tools/discover_hosts.sh


执行结果如下

stack@devstack21:~/devstack$ ./tools/discover_hosts.sh
INFO dbcounter [None req-1bb45b78-fd14-4fda-bd70-8cb20326bb8e None None] Registered counter for database nova_api
DEBUG dbcounter [-] [131423] Writer thread running {{(pid=131423) stat_writer /opt/stack/data/venv/lib/python3.10/site-packages/dbcounter.py:102}}
Found 2 cell mappings.
Skipping cell0 since it does not contain hosts.
Getting computes from cell ‘cell1’: ac941876-1395-4846-befe-ee823eb14d5e
INFO dbcounter [None req-1bb45b78-fd14-4fda-bd70-8cb20326bb8e None None] Registered counter for database nova_cell1
DEBUG dbcounter [-] [131423] Writer thread running {{(pid=131423) stat_writer /opt/stack/data/venv/lib/python3.10/site-packages/dbcounter.py:102}}
Found 0 unmapped computes in cell: ac941876-1395-4846-befe-ee823eb14d5e
stack@devstack21:~/devstack$


查看新发现的hypervisor


还可以查看 OVN 和 OVS 以查看第二个主机已出现。例如，OVN\_Southbound 数据库的 Chassis 表中将有第二个条目。可以使用 ovn-sbctl 实用程序列出chassis、其配置以及绑定到每个chassis的端口：

stack@devstack21:~/devstack$ sudo ovn-sbctl show
Chassis “2018dc69-862f-45d9-ad7d-0fc4dc5d08c4”
hostname: devstack21
Encap geneve
ip: “192.168.93.21”
options: {csum=“true”}
Port_Binding cr-lrp-7ff9bc36-6877-44c2-aee9-d9d8eb22c8e0
Chassis “1e889c0c-2509-4cc5-ad6e-f9d3bdfb5c40”
hostname: devstack22
Encap geneve
ip: “192.168.93.22”
options: {csum=“true”}


还可以看到创建到另一个计算节点的隧道：

stack@devstack21:~/devstack$ sudo ovs-vsctl show
…
Bridge br-int
fail_mode: secure
datapath_type: system
Port br-int
Interface br-int
type: internal
Port ovn-1e889c-0
Interface ovn-1e889c-0
type: geneve
options: {csum=“true”, key=flow, remote_ip=“192.168.93.22”}
…


两节点openstack已经部署完成，你可以通过openstack CLI或登录dashboard创建虚拟机实例进一步测试。


### 创建虚拟机


在本节中，我们将使用openstack CLI逐步完成创建两个虚拟机的步骤，这些虚拟机具有连接到 `private` Neutron 网络的虚拟 NIC。


DevStack 默认使用 libvirt 作为 Nova 后端。如果 KVM 可用，则会使用它。否则，它只会运行 qemu 模拟来宾。这对于我们的测试来说非常合适，因为我们只需要这些虚拟机能够发送和接收少量流量，因此性能并不是很重要。


#### 虚拟机创建流程


1、切换到demo用户

stack@devstack21:~/devstack$ pwd
/opt/stack/devstack
stack@devstack21:~/devstack$ . openrc demo demo
WARNING: setting legacy OS_TENANT_NAME to support cli tools.
stack@devstack21:~/devstack$


2、获取网络 UUID。


查看可用的网络，devstack默认为我们创建了三个网络，我们将使用 `private` 租户网络创建虚拟机

stack@devstack21:~/devstack$ openstack network list
±-------------------------------------±--------±---------------------------------------------------------------------------+
| ID | Name | Subnets |
±-------------------------------------±--------±---------------------------------------------------------------------------+
| 6211312f-ab8e-4346-bc58-aed8a63d4f62 | public | 0cf53da9-2c68-4b7d-8043-8d682fe34b23, 8a1dbf88-3caa-4a88-afa4-6fb6823cb224 |
| 8b8cdb32-c009-49e1-88d4-3d58198e6d6c | private | 24bfad1c-46ab-45a8-b607-da0ed8ea0b3c, 912dae4c-691a-44be-afb1-252c19ebfe24 |
| 98a54015-c7ac-4825-80a8-b3364d41db43 | shared | 0e754263-61ee-496a-8187-3103af900846 |
±-------------------------------------±--------±---------------------------------------------------------------------------+


首先从之前的 `openstack network list` 输出中获取 `private` 网络的 UUID 并将其保存：

PRIVATE_NET_ID=$(openstack network show private -c id -f value)


3、创建 SSH 密钥对。


接下来在 Nova 中创建 SSH 密钥对。稍后，当我们启动虚拟机时，我们会要求将公钥放入虚拟机中，以便我们可以通过 SSH 访问它。

openstack keypair create demo > id_rsa_demo
chmod 600 id_rsa_demo


查看我们创建的keypair


3、选择一种flavor，devstack默认为我们创建了多种flavor。


我们需要为这些测试虚拟机提供最少的资源，因此 `m1.nano` 风格就足够了。

stack@devstack21:~/devstack$ openstack flavor list
±—±----------±------±-----±----------±------±----------+
| ID | Name | RAM | Disk | Ephemeral | VCPUs | Is Public |
±—±----------±------±-----±----------±------±----------+
| 1 | m1.tiny | 512 | 1 | 0 | 1 | True |
| 2 | m1.small | 2048 | 20 | 0 | 1 | True |
| 3 | m1.medium | 4096 | 40 | 0 | 2 | True |
| 4 | m1.large | 8192 | 80 | 0 | 4 | True |
| 42 | m1.nano | 128 | 1 | 0 | 1 | True |
| 5 | m1.xlarge | 16384 | 160 | 0 | 8 | True |
| 84 | m1.micro | 192 | 1 | 0 | 1 | True |
| c1 | cirros256 | 256 | 1 | 0 | 1 | True |
| d1 | ds512M | 512 | 5 | 0 | 1 | True |
| d2 | ds1G | 1024 | 10 | 0 | 1 | True |
| d3 | ds2G | 2048 | 10 | 0 | 2 | True |
| d4 | ds4G | 4096 | 20 | 0 | 4 | True |
±—±----------±------±-----±----------±------±----------+

$ FLAVOR_ID=$(openstack flavor show m1.nano -c id -f value)


4、 选择一个镜像，devstack 默认已经为我们创建了一个cirros镜像


DevStack 默认导入 CirrOS 镜像，这非常适合我们的测试。这是一个非常小的测试图像。

$ IMAGE_ID=$(openstack image list -c ID -f value)


5、设置安全规则，以便我们可以访问接下来要启动的虚拟机。


默认情况下，DevStack 不允许用户访问虚拟机，要启用它，我们需要添加一条规则。我们将允许 ICMP 和 SSH。

openstack security group rule create --ingress --ethertype IPv4 --dst-port 22 --protocol tcp default
openstack security group rule create --ingress --ethertype IPv4 --protocol ICMP default


查看创建的安全组规则


6、启动一些虚拟机。


现在我们将启动两个虚拟机。我们将它们命名为 `test1` 和 `test2` 。


两个虚拟机启动后，它们的状态将为 `ACTIVE` ：


#### 虚拟机连接


我们可以通过关联公共网络中的浮动 IP 地址来连接到我们的虚拟机。

stack@devstack22:~/devstack$ TEST1_PORT_ID= $(o p e n s t a c k p or tl i s t - - ser v er t es t 1 - c i d - f v a l u e) s t a c k @ d e v s t a c k 22 : / d e v s t a c k$ openstack floating ip create --port $TEST1\_PORT\_ID public +---------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +---------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | created_at | 2024-03-24T05:26:11Z | | description | | | dns_domain | | | dns_name | | | fixed_ip_address | 10.0.0.36 | | floating_ip_address | 192.168.72.119 | | floating_network_id | 6211312f-ab8e-4346-bc58-aed8a63d4f62 | | id | 8b830932-5b79-4445-8730-2143e1779e54 | | name | 192.168.72.119 | | port_details | {'name': '', 'network\_id': '8b8cdb32-c009-49e1-88d4-3d58198e6d6c', 'mac\_address': 'fa:16:3e:6f:4b:92', 'admin\_state\_up': True, 'status': 'ACTIVE', 'device\_id': | | | '88ea2c47-7fe9-460b-b98a-0e4ebf773c98', 'device\_owner': 'compute:nova'} | | port_forwardings | [] | | port_id | 5fc6a820-8b4e-404b-899d-b57090708efd | | project_id | 6525123a5d8d4f048d51edf1ed18f06b | | qos_policy_id | None | | revision_number | 0 | | router_id | c0e52c09-8791-4a4e-9c82-9cd40d27a65e | | status | DOWN | | subnet_id | None | | tags | [] | | updated_at | 2024-03-24T05:26:11Z | +---------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ stack@devstack22:~/devstack$


现在应该能够通过其浮动 IP 地址连接到虚拟机。首先，ping 地址。

stack@devstack21:~/devstack$ ping 192.168.72.119 -c 3
PING 192.168.72.119 (192.168.72.119) 56(84) bytes of data.
64 bytes from 192.168.72.119: icmp_seq=1 ttl=128 time=2.43 ms
64 bytes from 192.168.72.119: icmp_seq=2 ttl=128 time=1.75 ms
64 bytes from 192.168.72.119: icmp_seq=3 ttl=128 time=1.03 ms

— 192.168.72.119 ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 1.031/1.735/2.425/0.569 ms
stack@devstack21:~/devstack$


现在通过 SSH 连接到虚拟机：

stack@devstack21:~/devstack$ ssh -i id_rsa_demo cirros@192.168.72.119 hostname
test1
stack@devstack21:~/devstack$


#### 登录dashboard


切换到demo项目，查看虚拟机管理器  
 ![在这里插入图片描述](https://i-blog.csdnimg.cn/blog_migrate/4122b1b873db0c3d53c9abd36c43d339.png)  
 查看test1实例位于devstack22节点上  
 ![在这里插入图片描述](https://i-blog.csdnimg.cn/blog_migrate/dd11b3c001aa9a0bf3bbcd424256c559.png)  
 查看test2实例位于devstack21节点上  
 ![在这里插入图片描述](https://i-blog.csdnimg.cn/blog_migrate/75c16347dd475dfdf39202eb629ef356.png)



**网上学习资料一大堆，但如果学到的知识不成体系，遇到问题时只是浅尝辄止，不再深入研究，那么很难做到真正的技术提升。**

**[需要这份系统化的资料的朋友，可以点击这里获取！](https://bbs.csdn.net/topics/618635766)**

**一个人可以走的很快，但一群人才能走的更远！不论你是正从事IT行业的老鸟或是对IT行业感兴趣的新人，都欢迎加入我们的的圈子（技术交流、学习资源、职场吐槽、大厂内推、面试辅导），让我们一起学习成长！**

3 ms

--- 192.168.72.119 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 1.031/1.735/2.425/0.569 ms
stack@devstack21:~/devstack$

现在通过 SSH 连接到虚拟机：

stack@devstack21:~/devstack$ ssh -i id_rsa_demo cirros@192.168.72.119 hostname
test1
stack@devstack21:~/devstack$

登录dashboard

切换到demo项目，查看虚拟机管理器
在这里插入图片描述
查看test1实例位于devstack22节点上

查看test2实例位于devstack21节点上

网上学习资料一大堆，但如果学到的知识不成体系，遇到问题时只是浅尝辄止，不再深入研究，那么很难做到真正的技术提升。

需要这份系统化的资料的朋友，可以点击这里获取！

K8S/Kubernetes

K8S/Kubernetes社区为您提供最前沿的新闻资讯和知识内容

更多推荐

【深度】阿里巴巴万级规模 K8s 集群全局高可用体系之美

作者 | 韩堂、柘远、沉醉来源 | 阿里巴巴云原生公众号前言台湾作家林清玄在接受记者采访的时候，如此评价自己 30 多年写作生涯：“第一个十年我才华横溢，‘贼光闪现’，令周边黯然失色；第二个十年，我终于‘宝光现形’，不再去抢风头，反而与身边的美丽相得益彰；进入第三个十年，繁华落尽见真醇，我进入了‘醇光初现’的阶段，真正体味到了境界之美”。长夜有穷，真水无香。领略过了 K8s“身在江

K8S/Kubernetes

如何基于 K8s 构建下一代 DevOps 平台？

作者 | 孙健波（天元）导读：当前云原生 DevOps 体系现状如何？面临哪些挑战？如何通过 OAM 解决云原生 DevOps 场景下的诸多问题？云原生开发应用模型 OAM(Open Application Model) 社区核心成员孙健波将为大家一一解答，并分享如何基于 OAM 和 Kubernetes 打造无限能力的下一代 DevOps 平台。什么是 DevOps？为什么基于 Kub

K8S/Kubernetes

k8s 火了！

2020，上云之年，产品云端化成为一种趋势。在一线城市，很多公司都已经构建了自己的私有云环境，比如阿里云、网易云、华为云等。而Kubernetes 作为基于容器编排领域的王者，具备扩展...

K8S/Kubernetes

所有评论(0)

查看更多评论

Java老杨

@m0_60721823

已为社区贡献2条内容

DevStack 部署 OpenStack 多节点_devstack多节点部署

Java老杨

=========================
DevStack Component Timing
(times are in seconds)

wait_for_service 12
async_wait 102
osc 180
apt-get 71
test_with_retry 5
dbsync 7
pip_install 128
apt-get-update 1
run_process 27
git_timed 85

Unaccounted time 184

=================
Async summary

This is the network config written by ‘subiquity’

git_base

password

OVN

Neutron options

Open vSwitch provider networking configuration

…

DevStack Component Timing
(times are in seconds)

wait_for_service 7
async_wait 0
osc 0
apt-get 264
pip_install 103
apt-get-update 1
run_process 4
git_timed 45

Unaccounted time 100

=================
Async summary

This is the network config written by ‘subiquity’

登录dashboard

所有评论(0)

Java老杨

DevStack 部署 OpenStack 多节点_devstack多节点部署

Java老杨

========================= DevStack Component Timing (times are in seconds)

wait_for_service 12 async_wait 102 osc 180 apt-get 71 test_with_retry 5 dbsync 7 pip_install 128 apt-get-update 1 run_process 27 git_timed 85

Unaccounted time 184

================= Async summary

This is the network config written by ‘subiquity’

git_base

password

OVN

Neutron options

Open vSwitch provider networking configuration

…

DevStack Component Timing (times are in seconds)

wait_for_service 7 async_wait 0 osc 0 apt-get 264 pip_install 103 apt-get-update 1 run_process 4 git_timed 45

Unaccounted time 100

================= Async summary

This is the network config written by ‘subiquity’

登录dashboard

所有评论(0)

Java老杨

=========================
DevStack Component Timing
(times are in seconds)

wait_for_service 12
async_wait 102
osc 180
apt-get 71
test_with_retry 5
dbsync 7
pip_install 128
apt-get-update 1
run_process 27
git_timed 85

=================
Async summary

DevStack Component Timing
(times are in seconds)

wait_for_service 7
async_wait 0
osc 0
apt-get 264
pip_install 103
apt-get-update 1
run_process 4
git_timed 45

=================
Async summary