Revision history [back]

click to hide/show revision 1
initial version

Thanks Dzung for the answer, but I'm still have some trouble to configure. Can you give more help?

On Swift host: root@saio:/home/swiftdemo# export ST_AUTH=https://172.17.1.125:443/auth/v1.0 root@saio:/home/swiftdemo# export ST_USER=test:tester root@saio:/home/swiftdemo# export ST_KEY=testing root@saio:/home/swiftdemo# swift stat -v StorageURL: https://172.17.1.125:443/v1/AUTH_3852a9fd-b1e5-4498-8aa4-3a557cebff2e Auth Token: AUTH_tk1a85a0af81364aa3ad104c9e035027c6 Account: AUTH_3852a9fd-b1e5-4498-8aa4-3a557cebff2e Containers: 3 Objects: 1 Bytes: 0 Accept-Ranges: bytes

On Glance node:

vi /etc/glance/glance-api.conf

Which backend store should Glance use by default is not specified

in a request to add a new image to Glance? Default: 'file'

Available choices are 'file', 'swift', and 's3'

default_store = swift

============ Swift Store Options =============================

Address where the Swift authentication service lives

swift_store_auth_address = 172.17.1.125:443/v1.0/

User to authenticate against the Swift authentication service

swift_store_user = test:tester

Auth key for the user authenticating against the

Swift authentication service

swift_store_key = AUTH_tk1a85a0af81364aa3ad104c9e035027c6

Container within the account that the account should use

for storing images in Swift

swift_store_container = CONTAINER

Do we create the container if it does not exist?

swift_store_create_container_on_put = True

Whether to use ServiceNET to communicate with the Swift storage servers.

(If you aren't RACKSPACE, leave this False!)

#

To use ServiceNET for authentication, prefix hostname of

swift_store_auth_address with 'snet-'.

Ex. https://example.com/v1.0/ -> https://snet-example.com/v1.0/

swift_enable_snet = False

Then on glance node, try to add an image. root@glance-node:~# glance add name="swift2" is_public=true < /tmp/test.iso Failed to add image. Got error: 400 Bad Request

The server could not comply with the request since it is either malformed or otherwise incorrect.

Error uploading image: global name 'swift_client' is not defined
Note: Your image metadata may still be in the registry, but the image's status will likely be 'killed'.