设为首页 收藏本站
查看: 655|回复: 0

[经验分享] Install and Configure OpenStack Object Storage (Swift) for Ubuntu 14.04

[复制链接]

尚未签到

发表于 2018-5-3 09:07:20 | 显示全部楼层 |阅读模式
  Based on Ubuntu 14.04 LTS x86_64
DSC0000.jpg

  On keystone auth node:

  # add swift user
keystone user-create --tenant service --name swift --pass SWIFT-USER-PASSWORD

# add swift user in admin role
keystone user-role-add --user swift --tenant service --role admin

# add an entry for swift service
keystone service-create --name=swift --type=object-store --description="Swift Service"

# add an entry for swift endpoint
keystone endpoint-create --region RegionOne --service swift --publicurl=http://LOAD-BALANCER-OF-PROXY:8080/v1/AUTH_%\(tenant_id\)s --internalurl=http://LOAD-BALANCER-OF-PROXY:8080/v1/AUTH_%\(tenant_id\)s --adminurl=http://LOAD-BALANCER-OF-PROXY:8080
  

  On Swift Storage nodes:
  1. using eth0 to connect proxy servers and other storage nodes
  

  2.  vi /etc/hosts
  # remove or comment the line beginning with 127.0.1.1
  192.168.20.30    proxynode1
192.168.20.31    proxynode2

3. aptitude -y install ntp
vi /etc/ntp.conf
server 192.168.20.30 perfer
server 192.168.20.31
restrict 192.168.20.30
restrict 192.168.20.31

service ntp restart

4. aptitude -y install python-mysqldb

5. aptitude -y install swift swift-account swift-container swift-object xfsprogs

6. RAID on the storage drives is not required and not recommended, use a single partition per drive
  

  7. vi /etc/swift/swift.conf
# change (it is shared between Nodes - any words you like)
[swift-hash]
swift_hash_path_suffix = swift_shared_path
  
swift storage node1:
  single partition, using fdisk, /dev/sdb --> /dev/sdb1 --> /srv/node/sdb1
  /dev/sdc --> /dev/sdc1 --> /srv/node/sdc1
  partprobe /dev/sdb /dev/sdc

  mkfs.xfs -i size=1024 /dev/sdb1
  mkfs.xfs -i size=1024 /dev/sdc1
  mkdir -p /srv/node/sdb1; mkdir -p /srv/node/sdc1
echo "/dev/sdb1 /srv/node/sdb1 xfs noatime,nodiratime,nobarrier,logbufs=8 0 0" >> /etc/fstab
echo "/dev/sdc1 /srv/node/sdc1 xfs noatime,nodiratime,nobarrier,logbufs=8 0 0" >> /etc/fstab
mount /srv/node/sdb1; mount /srv/node/sdc1
chown -R swift:swift /srv/node
  

  vi /etc/swift/account-server.conf
bind_ip =192.168.20.40

vi /etc/swift/container-server.conf
bind_ip =192.168.20.40

vi /etc/swift/object-server.conf
bind_ip =192.168.20.40
  
vi /etc/rsyncd.conf
uid = swift
gid = swift
log file = /var/log/rsyncd.log
pid file = /var/run/rsyncd.pid
address = STORAGE_LOCAL_NET_IP # 192.168.20.40

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

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

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

  vi /etc/default/rsync
RSYNC_ENABLE=true

service rsync start
  

  mkdir -p /var/swift/recon; chown -R swift:swift /var/swift/recon
  

  On Swift Proxy Server:

  1. eth0 for management/public/floating (192.168.1.0/24), eth1 for internal/flat (192.168.20.0/24), it's recommended to use seperated nic for management network
  

  2. vi /etc/hosts
  # remove or comment the line beginning with 127.0.1.1
  192.168.1.10    controller
192.168.1.11    node1
192.168.1.30    proxynode1
  192.168.1.31    proxynode2
  

  3. aptitude -y install ntp
  vi /etc/ntp.conf
server 192.168.1.10
restrict 192.168.1.10
  restrict 192.168.20.0 mask 255.255.255.0 nomodify notrap
  
service ntpd restart
  

  4. aptitude -y install python-mysqldb
  aptitude -y install swift swift-proxy memcached python-keystoneclient python-swiftclient python-webob

vi /etc/memcached.conf
-l 192.168.20.30

service memcached restart

5. vi /etc/swift/proxy-server.conf
[DEFAULT]
bind_port = 8080
user = swift

[pipeline:main]
pipeline = healthcheck cache authtoken keystoneauth proxy-server

[app:proxy-server]
use = egg:swift#proxy
allow_account_management = true
account_autocreate = true

[filter:keystoneauth]
use = egg:swift#keystoneauth
operator_roles = Member,admin,swiftoperator

[filter:authtoken]
paste.filter_factory = keystoneclient.middleware.auth_token:filter_factory

# Delaying the auth decision is required to support token-less
# usage for anonymous referrers ('.r:*').
delay_auth_decision = true

# cache directory for signing certificate
signing_dir = /home/swift/keystone-signing

# auth_* settings refer to the Keystone server
auth_protocol = http
auth_host = controller
auth_port = 35357

# the service tenant and swift username and password created in Keystone
admin_tenant_name = service
admin_user = swift
admin_password = SWIFT-USER-PASSWORD

[filter:cache]
use = egg:swift#memcache
memcache_servers = 192.168.20.30:11211

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

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

mkdir -p /home/swift/keystone-signing
chown -R swift:swift /home/swift/keystone-signing

6. vi /etc/swift/swift.conf
# change (it is shared between Nodes - any words you like)
[swift-hash]
swift_hash_path_suffix = swift_shared_path

7. please check http://rackerlabs.github.io/swift-ppc/, you should have at least 3 disks for the ring (my thought :))

  cd /etc/swift
swift-ring-builder account.builder create 8 3 1
swift-ring-builder container.builder create 8 3 1
swift-ring-builder object.builder create 8 3 1
  you should run above commands only once, so take care of the part_power value

  

  Notes: check https://swiftstack.com/blog/2012/04/09/swift-capacity-management/ for more info on weight, you can use disk capacity in GB for weight value during first initilization

  

  swift-ring-builder account.builder add r1z1-192.168.20.40:6002/sdb1 25
swift-ring-builder container.builder add r1z1-192.168.20.40:6001/sdb1 25
swift-ring-builder object.builder add r1z1-192.168.20.40:6000/sdb1 25

swift-ring-builder account.builder add r1z1-192.168.20.40:6002/sdc1 25
swift-ring-builder container.builder add r1z1-192.168.20.40:6001/sdc1 25
swift-ring-builder object.builder add r1z1-192.168.20.140:6000/sdc1 25
  

  swift-ring-builder account.builder add r1z1-192.168.20.40:6002/sdd1 25
swift-ring-builder container.builder add r1z1-192.168.20.40:6001/sdd1 25
swift-ring-builder object.builder add r1z1-192.168.20.140:6000/sdd1 25
  

  Verify the ring contents for each ring (cd /etc/swift to run below commands):
swift-ring-builder account.builder
swift-ring-builder container.builder
swift-ring-builder object.builder
  
swift-ring-builder account.builder rebalance
swift-ring-builder container.builder rebalance
swift-ring-builder object.builder rebalance

chown -R swift:swift /etc/swift

scp /etc/swift/*.gz 192.168.20.40:/etc/swift/
  

  service swift-proxy restart
  

  on swift storage node1
  1. chown -R swift:swift /etc/swift
  

  2. for service in swift-object swift-object-replicator swift-object-updater swift-object-auditor swift-container swift-container-replicator swift-container-updater swift-container-auditor swift-account swift-account-replicator swift-account-reaper swift-account-auditor; do
service $service start
done


  On keystone auth node:
  swift stat
  

运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.yunweiku.com/thread-455141-1-1.html 上篇帖子: ubuntu下查看某个软件的安装位置,配置文件在哪的方法 下篇帖子: Install Configure OpenStack Network Service (Neutron) for Ubuntu 14.04
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表