Configuration method of swift and keystone Integration
This article focuses on "the configuration method of swift and keystone integration". Interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Now let the editor take you to learn "the configuration method of swift and keystone integration"!
Swift deployment strategy
Keystone deployment strategy
172.18.48.21 proxy01 and keystone authentication nodes
172.18.48.22 proxy02 node
Note: both proxy01 and proxy02 have the environment edge variable openrc, and the swift.conf of each node should be the same.
Get to the point:
The node where the 1.keystone resides executes:
Keystone user-create-name=swift-pass=password-email=swift@example.com
Keystone user-role-add-user=swift-tenant=service-role=admin
Keystone user-role-add-user=swift-tenant=service-role=admin
Keystone service-create-name=swift-type=object-store-description= "openstack object storage"
Keystone endpoint-create-- service-id=$ (keystone service-list | awk'/ object-store / {print $2}')-- publicurl=' http://172.18.48.21:8080/v1/AUTH_%(tenant_id)s'-- internalurl=' http://172.18.48.21:8080/v1/AUTH_%(tenant_id)s'-- adminurl= http://172.18.48.21:8080
If you have multiple proxy nodes, you can use keystone to create endpoint separately. Note that different endpoint should have different region.
For example, add verification service to the proxy2 (172.18.48.22) node, which can only be performed on the keystone node.
Keystone endpoint-create-region RegionTwo-service-id=$ (keystone service-list | awk'/ object-store / {print $2}')-publicurl=' http://172.18.48.22:8080/v1/AUTH_%(tenant_id)s'-internalurl=' http://172.18.48.22:8080/v1/AUTH_%(tenant_id)s'-adminurl= http://172.18.48.22:8080
The 2.proxy node proxy-server.conf settings are as follows
[DEFAULT]
Bind_port = 8080
Workers = 8
User = swift
[pipeline:main]
Pipeline = catch_errors cache authtoken keystoneauth proxy-server
[app:proxy-server]
Use = egg:swift#proxy
Account_autocreate = true
[filter:keystoneauth]
Use = egg:swift#keystoneauth
Operator_roles = Member,admin,swift
[filter:healthcheck]
Use = egg:swift#healthcheck
[filter:authtoken]
Paste.filter_factory = keystoneclient.middleware.auth_token:filter_factory
Delay_auth_decision = 10
Auth_protocol = http
Service_port = 5000
Service_host = 172.18.48.21
Auth_port = 35357
Auth_host = 172.18.48.21
Auth_url = http://172.18.48.21:5000/
Admin_token = password
Cache = swift.cache
Admin_tenant_name = service
Admin_user = admin
Admin_password = password
[filter:cache]
Use = egg:swift#memcache
Set log_name = cache
Memcache_servers = 172.18.48.22 11211172.18.48.21
[filter:catch_errors]
Use = egg:swift#catch_errors
Restart the proxy service
Swift-init proxy restart
At this point, I believe you have a deeper understanding of the "configuration method of swift and keystone integration". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!
