openstack安装笔记 swift(四)

linux内核控 linux内核控 博客等级 墨衍会员 · AI 创作全网分发 墨衍智能分发 本文由作者通过墨衍一键同步至各平台 1分发平台 300+累计阅读 391平均单平台 已同步平台 优快云 微信公众号 微博 知乎 掘金 百家号 博客园 抖音 小红书 你的文章也可以这样分发 墨衍会员 ¥399起/年，写一次发全网 我也要 码龄19年
关注
原创 最新推荐文章于 2026-07-21 11:20:58 发布 391 阅读 AI 写同款· GEO 优化 ›
所有的安装都是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]
收录于
linux

当前文章被收录于：

linux
204 篇文章 0 人学习
订阅专栏 查看详情
openstack

当前文章被收录于：

openstack
23 篇文章 0 人学习
订阅专栏 查看详情
标签
#openstack
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
从零开始安装openstack swift 安装环境 所需软件及版本          VMware®Workstation 11.1.0 build-2496824（桌面虚拟计算机软件）          ubuntu-12.04.5-desktop-amd64.iso（ubuntu14.04桌面版，server版也可）          SSH（linux远程连接工具，putty之类的也可） 环境安装          安装 阅读详情

相关推荐

OpenStack Yoga版安装笔记（23）Swift安装

OpenStack Yoga版本 Swift服务安装。

zkyqss的博客 1180

Linux日志

日志轮转（Log Rotation）是一种管理日志文件大小和数量的方法，它通过按照一定的规则自动分割、压缩、删除或归档旧的日志文件，以便为新的日志文件腾出空间。这有助于防止日志文件占用过多的磁盘空间，并保持系统的稳定性。在rsyslogd中配置日志轮转，可以使用参数来指定单个日志文件的最大大小，使用参数来指定保留的备份日志文件的数量，以及使用参数来指定日志文件的最长保存天数。以下是一个简单的示例：打开rsyslogd的主配置文件，通常位于/etc/rsyslog.conf。

weixin_41312759的博客 2027

云计算Openstack Swift

定义：Ring是Swift中用于确定数据在集群中存储位置的核心组件。它通过一致性哈希算法将分区（partition）映射到不同的节点（node）上，从而实现数据的分布式存储。功能数据映射：Ring记录了每个分区与物理存储设备之间的映射关系，使得Swift系统能够快速地定位到数据的存储位置。负载均衡：通过一致性哈希算法，Ring能够确保数据在集群中的均衡分布，避免某些节点负载过重而其他节点空闲的情况。

王小工小工历程 1542

linux下的日志采集---rsyslog

一、linux日志文件及日志分析    1、linux日志简介      Linux系统拥有非常灵活和强大的日志功能，可以保存几乎所有的操作记录，并可以从中检索出我们需要的信息。 大部分Linux发行版默认的日志守护进程为 syslog（后续升级rsyslog），位于 /etc/syslog 或 /etc/syslogd，默认配置文件为 /etc/syslog.conf，任何希望

xianjie0318的博客 2万+

kolla-Ansible部署Openstack2024.1（含cinder、swift安装）

kolla-Ansible部署Openstack2024.1，并安装了cinder、swift，步骤详细，希望对大家的工作和学习有所帮助。

weixin_44872981的博客 4083

OPENSTACK简介OpenStack介绍个人笔记

IaaS：基础设施即服务PaaS：平台即服务SaaS：软件即服务云计算是一个服务，openstack和虚拟化是实现这个服务的手段之一；2.openstack是一个云平台，相当于openstack是一个超市，超市里有产品，而产品并不是超市生产的，openstack是没有资源的，是需要对接资源的，而这些资源指的是虚拟化资源或物理资源。基础管理服务包含Keystone、Glance、Nova、Neutron、Horizon五个服务 扩展管理服务包含Cinder、Swift、Trove、Heat、Centimete

3322855165 1万+

OpenStack Swift集群部署流程与简单使用

之前介绍了《OpenStack Swift All In One安装部署流程与简单使用》，那么接下来就说一说Swift集群部署吧。 1. 简介 　　本文档详细描述了使用两台PC部署一个小型Swift集群的过程，并给出一些简单的使用实例。本文档假定如下前提条件： 使用Ubuntu操作系统。 每台机器都运行Swift的所有服务，既是Proxy Server，又是Storage Serve...

weixin_30599769的博客 335

Openstack swift安装部署

块存储&文件存储&对象存储

仇晗的专栏 2809

OpenStack swift安装

由于实验室项目需要云存储系统，因此在实验室服务器上搭建一个基于OpenStack swift的云存储系统。 最开始按照官方网站上介绍的方法，使用SAIO方式安装http://docs.openstack.org/developer/swift/development_saio.html，但是中间经常安装到最后，测试的时候，认证不成功，而且安装的过程比较繁琐，于是采用了git的安装方式git

追寻梦想的青春 1934

在ubuntu上安装openstack的swift组件-installing openstack object storage

这几天正在自己搭建一个swift的环境。看了一些资料，结合自己的实践，写下了它： 1.物理环境说明： Linux系统版本：Ubuntu Server 12.04 Proxy Server IP： 10.214.0.181 Storage Server One: 10.214.0.179 Storage Server Two: 10.214.0.180 Storage S

兵临城下 6097

OpenStack Yoga版安装笔记（22）Swift笔记20250418

OpenStack 对象存储（Swift）用于构建冗余、可扩展的数据存储系统，通过一组标准化服务器集群来存储 PB 级（百万 GB）数据，并保证数据可访问。它是一个面向长期存储的大规模静态数据系统，支持数据的检索和更新。

zkyqss的博客 1121

Openstack Swift 安装部署总结

环境 硬件 这里只使用了一台服务器，既作为Controller Node，也作为Storage Node 主机名 IP OS 磁盘 文件系统 sf-dev 10.202.127.4 Centos-7.4 /dev/sdb/dev/sdc/dev/sdd XFS 软件 我们使用Openstack Pike版本 配置可用的Ope...

ch648966459的专栏 5385

OpenStack源码分析之Swift Proxy服务启动

Swift Proxy是Swift的核心组件之一，它负责接收来自客户端的请求，并根据请求的类型将其转发到适当的存储节点上。通过加载配置文件、配置应用程序和启动服务器，Swift Proxy服务能够接收客户端的请求，并将其转发到适当的存储节点上。当我们在Swift Proxy节点上运行以上代码时，Swift Proxy服务将开始监听指定的IP地址和端口号，并等待客户端的请求。通过加载配置文件，我们可以获取到Swift Proxy服务的相关配置项，例如绑定的IP地址、监听的端口号以及认证相关的配置等。

BUG？不存在的！ 262

【Openstack Train】十六、swift安装

OpenStack Swift是一个分布式对象存储系统，它可以为大规模的数据存储提供高可用性、可扩展性和数据安全性。Swift是OpenStack的一个核心组件，它允许用户将大量的数据存储在云上，并且可以随时访问、检索和管理这些数据。Swift的设计目标是为了处理海量数据和大规模数据的高并发访问，它采用了一些独特的技术和架构，如分布式存储、数据冗余、负载均衡、数据分片、对象容器等。在先前的教程中，介绍了安装openstack及其相关组件的具体过程，本文介绍如何安装swift。安装环境如下。

AI爱好者的博客，分享计算机领域相关知识 2305

金融科技创新中人工智能的应用：8篇优质论文精选（含2023）

随着科技的飞速发展，金融领域正经历着前所未有的变革。在这个过程中，人工智能技术发挥着越来越重要的作用。为了深入探讨金融人工智能的研究和应用，享享特地整理了几篇金融人工智能方面的论文，大家可以看一下金融人工智能方向最新的研究成果！面向金融领域的大型语言模型本文介绍了BloombergGPT，一个基于广泛金融数据训练的500亿参数模型。基于彭博（Bloomberg）广泛数据来源，建立了一个基于彭博数据的3630亿令牌数据集，并结合了额外3450亿通用数据令牌。

2401_82426425的博客 3210

从零实现机械臂抓取仿真：用MoveIt+Gazebo完成物体pick&place全流程

本文详细介绍了如何使用ROS的MoveIt框架与Gazebo仿真环境，从零构建机械臂抓取仿真系统。涵盖环境搭建、MoveIt配置、Gazebo集成、抓取动作实现等全流程，帮助开发者掌握机械臂控制的核心技术，实现高效的pick&place任务。

weixin_29250403的博客 476

源码安装OpenStack Swift

文章目录依赖安装Swift CLI（python-Swiftclient）安装Swift复制swift配置文件配置swift向swift中添加驱动器发现驱动器 依赖 在CentOS 6中可能在安装依赖前先安装EPEL库 rpm -Uvh http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm 有可能要安...

CherishL_的专栏 661

WINCC8.1工业组态软件安装与授权配置指南

SCADA系统作为工业自动化控制的核心平台，通过实时数据采集与监控实现生产流程可视化。WINCC作为西门子旗舰级组态软件，其8.1版本凭借稳定的运行时环境在汽车制造、流程工业等领域广泛应用。本文从工业控制系统软件安装规范切入，重点解析WINCC8.1与Automation License Manager的协同工作原理，详细说明包括系统环境检查、安装包校验、授权文件配置等关键技术环节。针对工程实施中常见的内存配置不足、授权管理器报错等典型问题，提供经过现场验证的解决方案，特别适用于需要进行产线监控系统升级维护

cqwf95925的博客 1651

openstack swift页面安装

参考网址： https://github.com/cschwede/django-swiftbrowser http://docs.openstack.org/mitaka/install-guide-ubuntu/swift-controller-install.html 1.安装swiftBrowser root@controller:/home# pip install django-sw

tyutpanda的专栏 1235

告别环境配置焦虑：在Win10的Ubuntu子系统里搞定CSAPP实验环境（附32/64位库编译指南）

本文详细介绍了如何在Win10的Ubuntu子系统中搭建CSAPP实验环境，包括WSL 2的安装与配置、32/64位库的编译指南以及高效开发工具链的设置。通过优化WSL性能和使用实用技巧，开发者可以轻松应对CSAPP实验中的环境配置问题，提升学习效率。

weixin_30443813的博客 296

瑞萨RA6M5驱动ST7735屏幕避坑指南：从软件SPI到显示汉字与图形的完整流程

本文详细介绍了瑞萨RA6M5单片机驱动ST7735屏幕的完整流程，涵盖硬件连接、软件SPI控制、汉字显示及图形绘制优化等关键步骤。通过避坑指南和实用代码示例，帮助开发者解决屏幕初始化、时序控制、字库移植等常见问题，实现高效稳定的显示效果。

weixin_28705087的博客 275

Swift (OpenStack Storage) 安装

在尝试通过源码安装 Swift 时，遇到了一个 Python 安装程序的错误，错误信息如下： 2、解决方案 以下是解决这个问题的步骤： 解压 setuptools 0.9.8： 进入 setuptools-0.9.8 目录： 安装 setuptools 0.9.8： 返回主目录： 安装 pip： 安装 libffi-dev： 克隆 Swift Git 仓库： 进入 Swift 目录： 安装 Swift： 启动 Swift 服务： 代码例子 Tra

D0126_的博客 831

核心组件大换血：Backbone与Neck魔改篇：YOLO26魔改Neck：引入BiFPN（双向特征金字塔），多尺度融合能力飙升

本文深入解析了YOLO26目标检测模型中Neck部分的优化策略，重点探讨了BiFPN（双向特征金字塔网络）的原理与实现。文章首先指出YOLO26原生FPN+PAN结构在多尺度特征融合上的局限性，特别是在小目标检测和边缘部署场景中的性能瓶颈。随后系统梳理了Neck网络的演进历程，从FPN、PANet到BiFPN和ASFF，详细对比了各架构的特点。核心部分展示了如何将BiFPN引入YOLO26，包括可学习权重融合、双向跨尺度连接等关键技术实现，并提供了PyTorch代码示例。本文为需要提升小目标检测性能或优化边

ZDQ58818的博客 246

openstack essex版安装（4）——swift

swift是openstack的存储项目。这里我用了2台机子 Swift Host:swift1 ip:192.168.0.110 Proxy-server, account-server, container-server, object-server Host:swift2 ip:192.168.0.111 accou

nocturne1210的专栏 2602

lammps 案例：高熵合金FeNiCrCoCu建模及拉伸模拟

高熵合金力学性能模拟包括拉伸、剪切、摩擦等模拟，本文以高熵合金FeNiCrCoCu为例介绍高熵合金建模及拉伸过程模拟。 FeNiCrCoCu原子数量比为1:1:1:1:1 高熵合金的拉伸与单晶拉伸过程类似，主要包含以下步骤： 1.建模 高熵合金含有原子类型较多，建模时，一般以含量最多的原子为主建立初始模型。 使用set type/ratio或者set type/fraction的方式按一定比例替换为其它合金原子。 如随机选择20%的原子1，将其转换为原子2： set type 1 type/ratio 2

lammps_jiayou的博客 6067

【图像去噪】论文精读：FM2S: Self-Supervised Fluorescence Microscopy Denoising With Single Noisy Image

论文题目：FM2S: Self-Supervised Fluorescence Microscopy Denoising With Single Noisy Image —— FM2S：单噪声图像自监督荧光显微镜去噪arXiv 2024！显微图像去噪！通过可视化详细的细胞结构和生物过程，荧光显微镜具有显着先进的生物学研究。然而，由于难以精确建模固有噪声和获取干净图像进行训练，这种图像去噪任务往往面临挑战，这限制了大多数现有方法。在本文中，我们提出了一种有效的。

主要更新底层视觉（去噪、超分等）相关的科研内容，形式为【论文精读】+【论文复现】 408
上一篇： openstack安装笔记 环境（零）
下一篇： openstack安装笔记 Horizon(五)
点赞 0
评论 0
书签 书签 0
linux内核控
linux内核控
博客等级 码龄19年 41粉丝 638原创
+ 关注 专栏目录 订阅专栏
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值