openstack安装笔记 swift(四)

southlsworld

2015-02-04

关注关注

所有的安装都是yum

改配置

在keystone库中写service表

写endpoint表，作为api调用

有的建立个库

安装swift

yum install xfsprogs openstack-swift-proxy openstack-swift-object openstack-swift-container openstack-swift-account openstack-utils memcached

注释：实际生产环境的话，此处的VG最好和上面的cinder使用的VG不同。自己另外创建一个VG

准备一个单独的逻辑卷或者磁盘，假设逻辑卷是/dev/vgstorage/lvswift

[root@controller rhel65(keystone_admin)]# cd /dev/vgstorage/
[root@controller vgstorage(keystone_admin)]# ls
volume-d6e1529f-633c-4e86-ad45-fc61734b950e
[root@controller vgstorage(keystone_admin)]# lvcreate --size 5G --name lvswift vgstorage
  Logical volume "lvswift" created
[root@controller vgstorage(keystone_admin)]# ls
lvswift  volume-d6e1529f-633c-4e86-ad45-fc61734b950e

[root@controller vgstorage(keystone_admin)]# mkfs.xfs -f -i size=1024 /dev/vgstorage/lvswift
meta-data=/dev/vgstorage/lvswift isize=1024   agcount=4, agsize=327680 blks
         =                       sectsz=512   attr=2, projid32bit=0
data     =                       bsize=4096   blocks=1310720, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0
log      =internal log           bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
[root@controller vgstorage(keystone_admin)]#

mkdir/mnt/sdb1

mount/dev/vgstorage/lvswift/mnt/sdb1

vi /etc/fstab
加入 /dev/vgstorage/lvswift   /mnt/sdb1            xfs     defaults        0 0

mkdir /mnt/sdb1/1 /mnt/sdb1/2 /mnt/sdb1/3 /mnt/sdb1/4
for x in {1..4}; do ln -s /mnt/sdb1/$x /srv/$x; done

mkdir -p /etc/swift/object-server /etc/swift/container-server /etc/swift/account-server /srv/1/node/sdb1 /srv/2/node/sdb2 /srv/3/node/sdb3 /srv/4/node/sdb4 /var/run/swift

chown -R swift:swift /etc/swift/ /srv/ /var/run/swift/ /mnt/sdb1

keystone service-create --name swift --type object-store --description "Swift Storage Service hao"
WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).
+-------------+----------------------------------+
|   Property  |              Value               |
+-------------+----------------------------------+
| description |    Swift Storage Service hao     |
|      id     | dac813a9993c4743977a057c2f4b199e |
|     name    |              swift               |
|     type    |           object-store           |
+-------------+----------------------------------+
[root@controller srv(keystone_admin)]# 

# keystone endpoint-create --service swift  --publicurl "http://172.16.21.233:8080/v1/AUTH_%(tenant_id)s" --adminurl "http://172.16.21.233:8080/v1/AUTH_%(tenant_id)s"  --internalurl "http://172.16.21.233:8080/v1/AUTH_%(tenant_id)s" --region beijing  
WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).
+-------------+-------------------------------------------------+
|   Property  |                      Value                      |
+-------------+-------------------------------------------------+
|   adminurl  | http://172.16.21.233:8080/v1/AUTH_%(tenant_id)s |
|      id     |         50cd09254c324fcc9ce04a4c16836007        |
| internalurl | http://172.16.21.233:8080/v1/AUTH_%(tenant_id)s |
|  publicurl  | http://172.16.21.233:8080/v1/AUTH_%(tenant_id)s |
|    region   |                     beijing                     |
|  service_id |         dac813a9993c4743977a057c2f4b199e        |
+-------------+-------------------------------------------------+
[root@controller srv(keystone_admin)]#

在keystone库的service表中加了一条数据

在endpoint表加了3条数据

---------------

设置rsync:

修改/etc/xinetd.d/rsync文件

disable=no

新建文件/etc/rsyncd.conf

uid = swift
gid = swift
log file = /var/log/rsyncd.log
pid file = /var/run/rsyncd.pid
address = 127.0.0.1

[account6012]
max connections = 25
path = /srv/1/node/
read only = false
lock file = /var/lock/account6012.lock

[account6022]
max connections = 25
path = /srv/2/node/
read only = false
lock file = /var/lock/account6022.lock

[account6032]
max connections = 25
path = /srv/3/node/
read only = false
lock file = /var/lock/account6032.lock

[account6042]
max connections = 25
path = /srv/4/node/
read only = false
lock file = /var/lock/account6042.lock

[container6011]
max connections = 25
path = /srv/1/node/
read only = false
lock file = /var/lock/container6011.lock

[container6021]
max connections = 25
path = /srv/2/node/
read only = false
lock file = /var/lock/container6021.lock

[container6031]
max connections = 25
path = /srv/3/node/
read only = false
lock file = /var/lock/container6031.lock

[container6041]
max connections = 25
path = /srv/4/node/
read only = false
lock file = /var/lock/container6041.lock

[object6010]
max connections = 25
path = /srv/1/node/
read only = false
lock file = /var/lock/object6010.lock

[object6020]
max connections = 25
path = /srv/2/node/
read only = false
lock file = /var/lock/object6020.lock

[object6030]
max connections = 25
path = /srv/3/node/
read only = false
lock file = /var/lock/object6030.lock

[object6040]
max connections = 25
path = /srv/4/node/
read only = false
lock file = /var/lock/object6040.lock

新建文件/etc/rsyslog.d/10-swift.conf

# Uncomment the following to have a log containing all logs together
#local1,local2,local3,local4,local5.*   /var/log/swift/all.log

# Uncomment the following to have hourly proxy logs for stats processing
#$template HourlyProxyLog,"/var/log/swift/hourly/%$YEAR%%$MONTH%%$DAY%%$HOUR%"
#local1.*;local1.!notice ?HourlyProxyLog

local1.*;local1.!notice /var/log/swift/proxy.log
local1.notice           /var/log/swift/proxy.error
local1.*                ~

local2.*;local2.!notice /var/log/swift/storage1.log
local2.notice           /var/log/swift/storage1.error
local2.*                ~

local3.*;local3.!notice /var/log/swift/storage2.log
local3.notice           /var/log/swift/storage2.error
local3.*                ~

local4.*;local4.!notice /var/log/swift/storage3.log
local4.notice           /var/log/swift/storage3.error
local4.*                ~

local5.*;local5.!notice /var/log/swift/storage4.log
local5.notice           /var/log/swift/storage4.error
local5.*                ~

修改/etc/rsyslog.conf配置文件，新加一行

$PrivDropToGroupadm

重新启动rsyslog服务
mkdir -p /var/log/swift/hourly
chmod -R g+w /var/log/swift
service rsyslog restart
	•	备份一些配置文件
mkdir  /etc/swift/bak
mv  /etc/swift/account-server.conf   /etc/swift/bak
mv  /etc/swift/container-server.conf  /etc/swift/bak
mv  /etc/swift/object-expirer.conf  /etc/swift/bak
mv  /etc/swift/object-server.conf  /etc/swift/bak

开始修改swift配置文件：

openstack-config --set /etc/swift/proxy-server.conf filter:authtoken admin_tenant_name admin
 openstack-config --set /etc/swift/proxy-server.conf   filter:authtoken admin_user admin
 openstack-config --set /etc/swift/proxy-server.conf   filter:authtoken admin_password openstack
openstack-config --set /etc/swift/proxy-server.conf  filter:authtoken auth_host 172.16.21.233
openstack-config --set /etc/swift/proxy-server.conf  filter:keystone operator_roles admin,SwiftOperator,Member

设置一个随机值
openstack-config --set /etc/swift/swift.conf swift-hash  swift_hash_path_suffix $(openssl rand -hex 10)

在/etc/swift/account-server目录下，新建四个配置文件1.conf,2.conf,3.conf,4.conf，这四个文件的内容如下:

[======account-server目录下的1.conf的内容==========
[DEFAULT]
devices = /srv/1/node
mount_check = false
disable_fallocate = true
bind_port = 6012
user = swift
log_facility = LOG_LOCAL2
recon_cache_path = /var/cache/swift
eventlet_debug = true

[pipeline:main]
pipeline = recon account-server

[app:account-server]
use = egg:swift#account

[filter:recon]
use = egg:swift#recon

[account-replicator]
vm_test_mode = yes
[account-auditor]

[account-reaper]

======account-server目录下的2.conf的内容=========
[DEFAULT]
devices = /srv/2/node
mount_check = false
disable_fallocate = true
bind_port = 6022
user = swift
log_facility = LOG_LOCAL3
recon_cache_path = /var/cache/swift2
eventlet_debug = true

[pipeline:main]
pipeline = recon account-server

[app:account-server]
use = egg:swift#account

[filter:recon]
use = egg:swift#recon

[account-replicator]
vm_test_mode = yes
[account-auditor]

[account-reaper]

======account-server目录下的3.conf的内容===========
[DEFAULT]
devices = /srv/3/node
mount_check = false
disable_fallocate = true
bind_port = 6032
user = swift
log_facility = LOG_LOCAL4
recon_cache_path = /var/cache/swift3
eventlet_debug = true

[pipeline:main]
pipeline = recon account-server

[app:account-server]
use = egg:swift#account

[filter:recon]
use = egg:swift#recon

[account-replicator]
vm_test_mode = yes
[account-auditor]

[account-reaper]

======account-server目录下的4.conf的内容===========
[DEFAULT]
devices = /srv/4/node
mount_check = false
disable_fallocate = true
bind_port = 6042
user = swift
log_facility = LOG_LOCAL5
recon_cache_path = /var/cache/swift4
eventlet_debug = true

[pipeline:main]
pipeline = recon account-server

[app:account-server]
use = egg:swift#account

[filter:recon]
use = egg:swift#recon

[account-replicator]
vm_test_mode = yes
[account-auditor]

[account-reaper]

-----------

在container-server目录下，新建四个文件1.conf,2.conf,3.conf,4.conf，四个文件的内容如下.

cd/etc/swift/container-server

======container-server目录下的1.conf的内容===========
[DEFAULT]
devices = /srv/1/node
mount_check = false
disable_fallocate = true
bind_port = 6011
user = swift
log_facility = LOG_LOCAL2
recon_cache_path = /var/cache/swift
eventlet_debug = true

[pipeline:main]
pipeline = recon container-server

[app:container-server]
use = egg:swift#container

[filter:recon]
use = egg:swift#recon

[container-replicator]
vm_test_mode = yes
[container-updater]

[container-auditor]

[container-sync]
======container-server目录下的2.conf的内容===========
[DEFAULT]
devices = /srv/2/node
mount_check = false
disable_fallocate = true
bind_port = 6021
user = swift
log_facility = LOG_LOCAL3
recon_cache_path = /var/cache/swift2
eventlet_debug = true

[pipeline:main]
pipeline = recon container-server

[app:container-server]
use = egg:swift#container

[filter:recon]
use = egg:swift#recon

[container-replicator]
vm_test_mode = yes
[container-updater]

[container-auditor]

[container-sync]

======container-server目录下的3.conf的内容===========
[DEFAULT]
devices = /srv/3/node
mount_check = false
disable_fallocate = true
bind_port = 6031
user = swift
log_facility = LOG_LOCAL4
recon_cache_path = /var/cache/swift3
eventlet_debug = true

[pipeline:main]
pipeline = recon container-server

[app:container-server]
use = egg:swift#container

[filter:recon]
use = egg:swift#recon

[container-replicator]
vm_test_mode = yes
[container-updater]

[container-auditor]

[container-sync]

======container-server目录下的4.conf的内容===========
[DEFAULT]
devices = /srv/4/node
mount_check = false
disable_fallocate = true
bind_port = 6041
user = swift
log_facility = LOG_LOCAL5
recon_cache_path = /var/cache/swift4
eventlet_debug = true

[pipeline:main]
pipeline = recon container-server

[app:container-server]
use = egg:swift#container

[filter:recon]
use = egg:swift#recon

[container-replicator]
vm_test_mode = yes
[container-updater]

[container-auditor]

[container-sync]

-----------------

在object-server目录下，新建四个文件1.conf,2.conf,3.conf,4.conf，

cd/etc/swift/object-server

======object-server目录下的1.conf的内容===========
[DEFAULT]
devices = /srv/1/node
mount_check = false
disable_fallocate = true
bind_port = 6010
user = swift
log_facility = LOG_LOCAL2
recon_cache_path = /var/cache/swift
eventlet_debug = true

[pipeline:main]
pipeline = recon object-server

[app:object-server]
use = egg:swift#object

[filter:recon]
use = egg:swift#recon

[object-replicator]
vm_test_mode = yes
[object-updater]

[object-auditor]

======object-server目录下的2.conf的内容===========
[DEFAULT]
devices = /srv/2/node
mount_check = false
disable_fallocate = true
bind_port = 6020
user = swift
log_facility = LOG_LOCAL3
recon_cache_path = /var/cache/swift2
eventlet_debug = true

[pipeline:main]
pipeline = recon object-server

[app:object-server]
use = egg:swift#object

[filter:recon]
use = egg:swift#recon

[object-replicator]
vm_test_mode = yes
[object-updater]

[object-auditor]

======object-server目录下的3.conf的内容===========
[DEFAULT]
devices = /srv/3/node
mount_check = false
disable_fallocate = true
bind_port = 6030
user = swift
log_facility = LOG_LOCAL4
recon_cache_path = /var/cache/swift3
eventlet_debug = true

[pipeline:main]
pipeline = recon object-server

[app:object-server]
use = egg:swift#object

[filter:recon]
use = egg:swift#recon

[object-replicator]
vm_test_mode = yes
[object-updater]

[object-auditor]

======object-server目录下的4.conf的内容===========
[DEFAULT]
devices = /srv/4/node
mount_check = false
disable_fallocate = true
bind_port = 6040
user = swift
log_facility = LOG_LOCAL5
recon_cache_path = /var/cache/swift4
eventlet_debug = true

[pipeline:main]
pipeline = recon object-server

[app:object-server]
use = egg:swift#object

[filter:recon]
use = egg:swift#recon

[object-replicator]
vm_test_mode = yes
[object-updater]

[object-auditor]

----------------

#!/bin/bash

cd /etc/swift

rm -f *.builder *.ring.gz backups/*.builder backups/*.ring.gz

swift-ring-builder object.builder create 10 3 1                            haohao:????
swift-ring-builder object.builder add r1z1-172.16.21.233:6010/sdb1 1
swift-ring-builder object.builder add r1z2-172.16.21.233:6020/sdb2 1
swift-ring-builder object.builder add r1z3-172.16.21.233:6030/sdb3 1
swift-ring-builder object.builder add r1z4-172.16.21.233:6040/sdb4 1
swift-ring-builder object.builder rebalance
swift-ring-builder container.builder create 10 3 1
swift-ring-builder container.builder add r1z1-172.16.21.233:6011/sdb1 1
swift-ring-builder container.builder add r1z2-172.16.21.233:6021/sdb2 1
swift-ring-builder container.builder add r1z3-172.16.21.233:6031/sdb3 1
swift-ring-builder container.builder add r1z4-172.16.21.233:6041/sdb4 1
swift-ring-builder container.builder rebalance
swift-ring-builder account.builder create 10 3 1
swift-ring-builder account.builder add r1z1-172.16.21.233:6012/sdb1 1
swift-ring-builder account.builder add r1z2-172.16.21.233:6022/sdb2 1
swift-ring-builder account.builder add r1z3-172.16.21.233:6032/sdb3 1
swift-ring-builder account.builder add r1z4-172.16.21.233:6042/sdb4 1
swift-ring-builder account.builder rebalance

chmod755/root/remakering.sh

/root/remakering.sh

执行

[root@controller ~(keystone_admin)]# ./remakering.sh 
Device d0r1z1-172.16.21.233:6010R172.16.21.233:6010/sdb1_"" with 1.0 weight got id 0
Device d1r1z2-172.16.21.233:6020R172.16.21.233:6020/sdb2_"" with 1.0 weight got id 1
Device d2r1z3-172.16.21.233:6030R172.16.21.233:6030/sdb3_"" with 1.0 weight got id 2
Device d3r1z4-172.16.21.233:6040R172.16.21.233:6040/sdb4_"" with 1.0 weight got id 3
Reassigned 1024 (100.00%) partitions. Balance is now 0.00.
Device d0r1z1-172.16.21.233:6011R172.16.21.233:6011/sdb1_"" with 1.0 weight got id 0
Device d1r1z2-172.16.21.233:6021R172.16.21.233:6021/sdb2_"" with 1.0 weight got id 1
Device d2r1z3-172.16.21.233:6031R172.16.21.233:6031/sdb3_"" with 1.0 weight got id 2
Device d3r1z4-172.16.21.233:6041R172.16.21.233:6041/sdb4_"" with 1.0 weight got id 3
Reassigned 1024 (100.00%) partitions. Balance is now 0.00.
Device d0r1z1-172.16.21.233:6012R172.16.21.233:6012/sdb1_"" with 1.0 weight got id 0
Device d1r1z2-172.16.21.233:6022R172.16.21.233:6022/sdb2_"" with 1.0 weight got id 1
Device d2r1z3-172.16.21.233:6032R172.16.21.233:6032/sdb3_"" with 1.0 weight got id 2
Device d3r1z4-172.16.21.233:6042R172.16.21.233:6042/sdb4_"" with 1.0 weight got id 3
Reassigned 1024 (100.00%) partitions. Balance is now 0.00.
[root@controller ~(keystone_admin)]#

－－－－－－－－－－－－－－－－

权限

chown-Rswift:swift/srv/

chown-Rswift:swift/etc/swift

chown-Rswift:swift/mnt/sdb1

启动

启动memcached

/etc/init.d/memcachedstart

chkconfigmemcachedon

•启动swift(swift没有配置开机启动)

swift-initallstart

开启swift的debug模式(可选)

在proxy-server.conf里的[default]配置里面加上下面2行

log_facility=LOG_LOCAL1

log_level=DEBUG

启动后输出：

[root@controller ~(keystone_admin)]# swift-init all start
Starting container-updater...(/etc/swift/container-server/1.conf)
Starting container-updater...(/etc/swift/container-server/2.conf)
Starting container-updater...(/etc/swift/container-server/3.conf)
Starting container-updater...(/etc/swift/container-server/4.conf)
Starting account-auditor...(/etc/swift/account-server/1.conf)
Starting account-auditor...(/etc/swift/account-server/2.conf)
Starting account-auditor...(/etc/swift/account-server/3.conf)
Starting account-auditor...(/etc/swift/account-server/4.conf)
Starting object-replicator...(/etc/swift/object-server/1.conf)
Starting object-replicator...(/etc/swift/object-server/2.conf)
Starting object-replicator...(/etc/swift/object-server/3.conf)
Starting object-replicator...(/etc/swift/object-server/4.conf)
Starting proxy-server...(/etc/swift/proxy-server.conf)
Starting container-replicator...(/etc/swift/container-server/1.conf)
Starting container-replicator...(/etc/swift/container-server/2.conf)
Starting container-replicator...(/etc/swift/container-server/3.conf)
Starting container-replicator...(/etc/swift/container-server/4.conf)
Starting object-auditor...(/etc/swift/object-server/1.conf)
Starting object-auditor...(/etc/swift/object-server/2.conf)
Starting object-auditor...(/etc/swift/object-server/3.conf)
Starting object-auditor...(/etc/swift/object-server/4.conf)
Unable to locate config for object-expirer
Starting container-auditor...(/etc/swift/container-server/1.conf)
Starting container-auditor...(/etc/swift/container-server/2.conf)
Starting container-auditor...(/etc/swift/container-server/3.conf)
Starting container-auditor...(/etc/swift/container-server/4.conf)
Starting container-server...(/etc/swift/container-server/1.conf)
Starting container-server...(/etc/swift/container-server/2.conf)
Starting container-server...(/etc/swift/container-server/3.conf)
Starting container-server...(/etc/swift/container-server/4.conf)
Starting account-server...(/etc/swift/account-server/1.conf)
Starting account-server...(/etc/swift/account-server/2.conf)
Starting account-server...(/etc/swift/account-server/3.conf)
Starting account-server...(/etc/swift/account-server/4.conf)
Starting account-reaper...(/etc/swift/account-server/1.conf)
Starting account-reaper...(/etc/swift/account-server/2.conf)
Starting account-reaper...(/etc/swift/account-server/3.conf)
Starting account-reaper...(/etc/swift/account-server/4.conf)
Starting container-sync...(/etc/swift/container-server/1.conf)
Starting container-sync...(/etc/swift/container-server/2.conf)
Starting container-sync...(/etc/swift/container-server/3.conf)
Starting container-sync...(/etc/swift/container-server/4.conf)
Starting account-replicator...(/etc/swift/account-server/1.conf)
Starting account-replicator...(/etc/swift/account-server/2.conf)
Starting account-replicator...(/etc/swift/account-server/3.conf)
Starting account-replicator...(/etc/swift/account-server/4.conf)
Starting object-updater...(/etc/swift/object-server/1.conf)
Starting object-updater...(/etc/swift/object-server/2.conf)
Starting object-updater...(/etc/swift/object-server/3.conf)
Starting object-updater...(/etc/swift/object-server/4.conf)
Starting object-server...(/etc/swift/object-server/1.conf)
Starting object-server...(/etc/swift/object-server/2.conf)
Starting object-server...(/etc/swift/object-server/3.conf)
Starting object-server...(/etc/swift/object-server/4.conf)

测试

新建container

swiftposthaocontainer

上传文件

swiftuploadhaocontainera.txt

查询一级目录

swiftlist

查询haocontainer目录下面的文件

swiftlisthaocontainer

[root@controller ~(keystone_admin)]# swift list haocontainer
a.txt
[root@controller ~(keystone_admin)]# swift list
haocontainer

openstack

southlsworld

0 关注 0 粉丝 0 动态

关注关注

OpenStack Cinder服务状态排错

本文转载自微信公众号「新钛云服」，作者舒祝。最近手动搭建了一个openstack环境，创建硬盘时失败，查看日志，提示无法进行调度，怀疑是cinder节点出现问题，去cinder节点查看服务，状态显示正常。结果显示cinder-volume的state

Moolightshadow 2020-07-16

OpenStack Train版-3.安装glance镜像服务

1. 创建数据库并授权

hhphhp 2020-07-05

OpenStack Train版-2.安装keystone身份认证服务

同时，keystone也不再对管理员用户和普通用户的服务端点区分使用不同的端口5000和35357，而是只使用5000端口不再使用35357端口。

fyggzb 2020-07-05

B13-openstack高可用(t版)-horazion计算节点集群

在全部控制节点安装dashboard服务，以controller01节点为例

JeremyLiu 2020-06-14

OpenStack Train版-11.启动实例（控制节点）

指明物理网络的提供者，与下面neutron的配置文件对应，其中provider是标签，可以更改为其他，但是2个地方必须要统一。指明这里创建的网络是flat类型，即实例连接到此网络时和物理网络是在同一个网段，无vlan等功能。neutron subnet-c

gokeibi 2020-06-12

Openstack_第二课_Openstack框架说明

Nova是OpenStack计算的弹性控制器。OpenStack云实例生命期所需要的各种动作都将由Nova进行处理和支撑，这就意味着Nova以管理平台的身份登场，负责管理整个云的计算资源，网络、授权及测读。虽然Nova本身并不提供任务虚拟能力，但是它将使用

zziyuann 2020-06-12

OpenStack Train版-2.安装keystone身份认证服务

GRANT ALL PRIVILEGES ON keystone.* TO ‘keystone‘@‘%‘ IDENTIFIED BY ‘KEYSTONE_DBPASS‘;1 [ ~]# yum install openstack-keystone http

fyggzb 2020-06-12

OpenStack Train版-3.安装glance镜像服务

MariaDB []> GRANT ALL PRIVILEGES ON glance.* TO ‘glance‘@‘%‘ IDENTIFIED BY ‘GLANCE_DBPASS‘;[ ~]# openstack user create --doma

hhphhp 2020-06-12

mysql 删除

-e, --execute=name Execute command and quit. (Disables --force and history file.)

fyggzb 2020-06-10

openstack-neutron-openvswitch

openstack-neutron-openvswitch noarch 1:12.1.1-1.el7 centos-openstack-queens 16 k. openstack-neut

JeremyLiu 2020-06-10

openstack安装glance后上传镜像报错410 Gone

最近几天闲着没事自己研究下OpenStack，第一个服务是keystone，安装起来没什么问题，安装完第二个服务glance后，按照官网进行验证的时候却发现上传镜像的时候报错了，具体报错如下：。[ ~]# openstack image create &q

JeremyLiu 2020-06-10

A18. openstack架构实战-控制节点和计算节点的结合

[ ~]# systemctl restart openstack-nova-compute[ ~]# systemctl restart libvirtd.service

jmppok 2020-06-07

OpenStack 的随手录（一）

查看OpenStack 的docs文档时发现，U系列的 OpenStack Ussuri 已经于2020年5月13日正式发布了，下一个V系列版本 OpenStack Victoria 正在构建中。作为开源产品的拥踅者，我决定好好回馈一下OpenStack社

jmppok 2020-06-05

Openstack 启动一个实例(九)

openstack network create --share --external --provider-physical-network linux36 --provider-network-type flat linux36. --provide

hhphhp 2020-06-01

glance

rc 文件可以在控制面板下载。执行以下命令同步数据库su -s /bin/sh -c "glance-manage db_sync" glance

zziyuann 2020-05-17

什么是openstack

想认识一个事物，必须先弄明白它是什么，能干什么。openstack能干什么，可以搭建公有云，私有云，企业云。上面是一个整体的认识，想进一步了解openstack，就必须了解它的组成。一般生物都有眼睛，鼻子，嘴等。openstack更像是经过计算机的72变之

gokeibi 2020-05-07

10. 配置Horizon — OpenStack Queens 三节点部署

由于配置文件本身是一个Python文件，对缩进要求非常严格，修改时需要小心。‘LOCATION‘: ‘10.0.0.7:11211‘,

gokeibi 2020-04-26

openstack（五）nova(控制节点/计算节点)

yum install -y openstack-nova-api openstack-nova-placement-api openstack-nova-conductor openstack-nova-console openstack-nova-no

gokeibi 2020-04-19

openstack（六）neutron

yum install -y openstack-neutron openstack-neutron-ml2 openstack-neutron-linuxbridge ebtables. mechanism_drivers = linuxbridge,o

gokeibi 2020-04-19

如何实现OpenStack的网络部署

在《OpenStack在行动》这本著作的摘录中，探索了有关OpenStack的部署方法，并给出了实现OpenStack网络部署的建议。组织需要经验丰富的网络工程师才能高效地运营，孤立的IT团队可能无法跟上不断发展变化的技术，特别是涉及到OpenStack部

嗯 2020-04-17

安科网

openstack安装笔记 swift(四)

southlsworld

southlsworld

相关推荐

OpenStack Cinder服务状态排错

OpenStack Train版-3.安装glance镜像服务

OpenStack Train版-2.安装keystone身份认证服务

B13-openstack高可用(t版)-horazion计算节点集群

OpenStack Train版-11.启动实例（控制节点）

Openstack_第二课_Openstack框架说明

OpenStack Train版-2.安装keystone身份认证服务

OpenStack Train版-3.安装glance镜像服务

mysql 删除

openstack-neutron-openvswitch

openstack安装glance后上传镜像报错410 Gone

A18. openstack架构实战-控制节点和计算节点的结合

OpenStack 的随手录（一）

Openstack 启动一个实例(九)

glance

什么是openstack

10. 配置Horizon — OpenStack Queens 三节点部署

openstack（五）nova(控制节点/计算节点)

openstack（六）neutron

如何实现OpenStack的网络部署

southlsworld