openstack安装笔记 swift(四)

最新推荐文章于 2024-05-29 17:55:06 发布
原创 最新推荐文章于 2024-05-29 17:55:06 发布 · 351 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#openstack

本文详细介绍Swift对象存储系统的部署过程，包括配置文件修改、服务及端点注册、rsync配置、日志配置等步骤，并展示了如何通过命令行进行文件操作。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

所有的安装都是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
[code="java"]
# cd /dev/vgstorage/
# ls
volume-d6e1529f-633c-4e86-ad45-fc61734b950e
# lvcreate --size 5G --name lvswift vgstorage
Logical volume "lvswift" created
# ls
lvswift volume-d6e1529f-633c-4e86-ad45-fc61734b950e

# 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
#
[/code]

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


[code="java"]
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 |
+-------------+----------------------------------+
#

# 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 |
+-------------+-------------------------------------------------+
#
[/code]

在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配置文件，新加一行
$PrivDropToGroup adm

重新启动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


chmod 755 /root/remakering.sh
/root/remakering.sh
执行
[code="java"]
# ./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.
#
[/code]
－－－－－－－－－－－－－－－－
权限
chown -R swift:swift /srv/
chown -R swift:swift /etc/swift
chown -R swift:swift /mnt/sdb1

启动
启动memcached
/etc/init.d/memcached start
chkconfig memcached on
• 启动swift (swift没有配置开机启动)
swift-init all start
开启swift的debug模式 (可选)
在proxy-server.conf 里的 [default]配置里面加上下面2行
log_facility = LOG_LOCAL1
log_level = DEBUG

启动后输出：
[code="java"]
# 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)
[/code]


测试
新建container
swift post haocontainer
上传文件
swift upload haocontainer a.txt
查询一级目录
swift list
查询haocontainer目录下面的文件
swift list haocontainer

[code="java"]
# swift list haocontainer
a.txt
# swift list
haocontainer
[/code]
OpenStack源码分析之Swift Proxy服务启动
BUG？不存在的！
09-02 194
Swift Proxy是Swift的核心组件之一，它负责接收来自客户端的请求，并根据请求的类型将其转发到适当的存储节点上。通过加载配置文件、配置应用程序和启动服务器，Swift Proxy服务能够接收客户端的请求，并将其转发到适当的存储节点上。当我们在Swift Proxy节点上运行以上代码时，Swift Proxy服务将开始监听指定的IP地址和端口号，并等待客户端的请求。通过加载配置文件，我们可以获取到Swift Proxy服务的相关配置项，例如绑定的IP地址、监听的端口号以及认证相关的配置等。
[部署篇13]VMWare搭建Openstack——Swift的安装与部署
GIS+=地理信息+云计算+大数据+容器+物联网+...
06-04 2523
1.Swift介绍 1.1.       Swift架构概述 官方给出的标准架构进行分析，如图，分别为存储节点（Storage node）、代理节点（Proxy node）和认证节点（Auth node）三部分。 1.1.1.   代理节点 代理节点可以说是Swift的核心，运行着swift-proxy-server进程。它提供Swift API的服务，负责Swift其余组件间
filebeat + logstash进行openstack-swift集群日志收集的一个简单实例
weixin_30532987的博客
11-08 287
在需要收集日志的proxy节点上配置filebeat，步骤如下： 1、安装filebeat，执行如下命令：yum -y install filebeat 2、修改/etc/filebeat/filebeat.yml文件，内容如下：filebeat.prospectors:- input_type: log paths: - /var/log/swift/proxy-serv...
OpenStack Swift安装与配置
qiuyabing的专栏
08-07 725
OpenStack Swift安装与配置 OCT 15TH, 2013 准备环境 1 2 3 192.168.30.150 proxy server 192.168.30.151 storage server 192.168.30.152 storage server 网络配置 Proxy 代理节点网络(单网卡) ...
安装openstack对象存储swift
Young, Simple, Naive
08-03 912
修改Vagrantfile文件如下 #_*_ mode: ruby _*_ #vi:set ft=ruby : nodes={ 'controller' =>[1,200], 'compute' => [1,201], 'swift' => [1,210], } Vagrant.configure("2") do |config| ...
openstack安装之对象存储安装笔记
m0_56539278的博客
06-10 1114
1、控制节点操作1.1、先决条件设置 admin 凭证获得 admin 凭证来获取只有管理员能执行的命令的访问权限，执行如下命令：. /root/admin-openrc创建身份认证服务的凭证创建 swift 用户(密码设置为：zhitu2017)：openstack user create --domain default --password-prompt swift给 swift 用户添加 admin 角色：openstack role add --project service --user swi
OpenStack学习笔记之四：Cinder流程介绍及GlusterFS存储对接
最新发布
大龄IT民工
05-29 1657
Cinder服务由四个进程组成：①cinder-api是一个WSGI应用程序，它接受并验证来自客户端的REST（JSON或XML）请求，并通过AMQP将它们路由到适当的其他Cinder进程。②确定哪个后端应作为卷创建或移动请求的目标。它维护后端的非持久状态（例如可用容量、功能和支持的额外规格），在做出放置决策时可以利用这些状态。调度程序使用的算法可以通过Cinder配置进行更改。③接受来自其他Cinder进程的请求，并充当Cinder驱动程序的操作容器。
Openstack学习笔记
05-11
OpenStack Swift 学习笔记 OpenStack Swift 是 OpenStack 开源云计算项目的子项目之一，旨在使用普通硬件来构建冗余的、可扩展的分布式对象存储集群，存储容量可达 PB 级。Swift 并不是文件系统或者实时的数据存储...
openstack精华笔记
04-21
**四、OpenStack管理** OpenStack 提供了命令行工具（CLI）和Web界面（Horizon）进行资源管理。此外，还可以通过API与OpenStack进行交互，实现自动化运维和集成其他系统。 **五、OpenStack扩展和社区** OpenStack ...
OpenStack学习笔记之三：Glance的使用
大龄IT民工
05-29 771
在配置文件的后面有关于该选项的详细解释，因为是默认配置，因此虽然注释了，但是配置是生效了的。上传镜像的用户必须有相关权限，需要使用admin账户登录后赋权。用bruce账户上传镜像会出错，但是admin镜像是可以的。完成配置后重启服务并查看是否正常。
openstack排错经历
Stroll the clouds
08-28 1万+
整个安装过程，报错是最经常的事，毕竟openstack的很多东西都还不成熟，冷静的排错才是王道，尽管openstack错误不断，但是最终他还是能跑起来的。      出错时候，我本着内事问百度，外事问谷歌的原则寻求帮助，另外也从网上的同行朋友处汲取帮助，可以说错误是多种多样的，这里也只能列举几种常见的错误，未尽之处，各位按照查自己的步骤，查log，查bug列表，查launchpad，求助中国同行
openstack Rocky版本安装和配置swift服务教程
weixin_54628931的博客
03-05 2296
参考openstack官网教程配置了swift服务，详细配置如下。侵权删除。建议在配置的时候注意看清楚IP地址，密码，和其他编码的配置，不要全盘复制粘贴！ 说明： （1）本次配置的openstack版本是Rocky （2）操作系统版本是Centos 7 （3）注意存储节点上也要安装openstack客户端 yum install centos-release-openstack-rocky -y yum install python-openstackclient ...
Unable to locate package错误解决办法
zhangzhetaojj的博客
03-25 2万+
原文地址：http://www.cppblog.com/colorful/archive/2012/04/29/173122.html最近刚开始接触Linux，开始了 sudo apt-get install，结果出现了下面的Unable to locate package错误　　问题出在执行sudo apt-get install之前更换了软件源，但是却忘了update下了，于是执行下面的命令：...
从零开始安装openstack swift
做个专家
08-26 4875
安装环境 所需软件及版本          VMware®Workstation 11.1.0 build-2496824（桌面虚拟计算机软件）          ubuntu-12.04.5-desktop-amd64.iso（ubuntu14.04桌面版，server版也可）          SSH（linux远程连接工具，putty之类的也可） 环境安装          安装
Openstack Swift 学习总结（一）
ch648966459的专栏
02-12 1629
组件 Swift主要使用到如下组件来提供对象存储服务： Proxy servers 处理所有请求调用 Rings 将数据映射到物理磁盘上，实际就是记录了逻辑数据存放在哪一块物理磁盘的那个位置上 Zones 对不同区域的数据进行隔离，一个区域中的故障不会影响集群其他区域数据副本 Accounts and containers 每个账户和容器都是分布在集群中的单独的数据库，账户数据库包含...
OpenStack Swift All In One安装部署流程与简单使用
weixin_30952535的博客
05-11 270
首先要感谢liu大神的翻译与试验，http://www.cnblogs.com/yuki-lau/ 简介 　　本文详细描述使用单台服务器部署一个Swift开发版本的过程，单台服务器运行所有Swift服务，并模拟运行具有4个结点的Swift集群。其中，这里的“服务器”可以是物理机也可以是虚拟机。 　　已验证的部署环境： VMWare 7.1.2 Ubuntu-11.10-d...
openstack_swift源码分析——Swift单机部署
xianghonglee的专栏
05-04 3126
openstack swift 部署详细介绍
rsyslog基本应用
weixin_34226706的博客
01-07 207
一、日志分类：facility: 设施，从功能或程序上对日志进行分类auth, authpriv, cron, daemon, kern, lpr,mail, mark, news, security, user, uucp, local0-local7, syslog其中，local0-local7为自定义facilitypriority: 日志级别(从低到高排序)deb...
linux下的日志采集---rsyslog
热门推荐
xianjie0318的博客
06-09 2万+
一、linux日志文件及日志分析    1、linux日志简介      Linux系统拥有非常灵活和强大的日志功能，可以保存几乎所有的操作记录，并可以从中检索出我们需要的信息。 大部分Linux发行版默认的日志守护进程为 syslog（后续升级rsyslog），位于 /etc/syslog 或 /etc/syslogd，默认配置文件为 /etc/syslog.conf，任何希望
CentOS7.0下OpenStack安装教程
"OpenStack学习安装笔记 - 一篇记录在CentOS7.0环境下搭建OpenStack的详细步骤的文档，作者为杨，属于15软一班级。文章介绍了云计算的基本概念，OpenStack的定义和作用，以及OpenStack的10个核心项目。" **云计算**...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值