Glance images on S3 storage - shared

Asked by Peter Borghard on 2012-06-10

Hello All,

I'm building out an openstack environment where we have several nodes in different locations. In order to cut down on server space, we are looking to keep images on s3 storage. However we would like the images to be shared between the nodes. Please keep in mind the nodes have no knowledge of each other. When I import an instance into glance using s3 storage, the image is saved with a unique ID. Is it possible to share the images? Without the unique ID? For instance if I uploaded several images to S3 storage(not using glance). Is there a way to configure a list of s3 images on the openstack nodes?

Peter Borghard

Question information

English Edit question
Glance Edit question
No assignee Edit question
Last query:
Last reply:
Jay Pipes (jaypipes) said : #1

You can upload your images to S3 and then add those image locations to Glance using the location field. For instance:

glance add location=http+s3://AWSACCOUNTID:<email address hidden>/BUCKET/OBJECTNAME name="My S3 Image" disk_format=ami container_format=ami is_public=True

You will get a different image ID in each of your glance registry servers, however.


Peter Borghard (pborghard) said : #2


That's what I'm trying to avoid. The path I'm looking to take is:

1.) upload images to S3 storage without using glance
2.) Try to configure glance to use these images without adding a unique ID

I'm not sure if this is possible, or if this is a poor design choice.

Peter Borghard

Jay Pipes (jaypipes) said : #3

Peter, you can add the image (as shown in previous post) to Glance, and then on the second and N glance registry servers, you can add the:

 glance add id=<UUID_OF_FIRST_IMAGE> ...

to set the ID at time of adding. However, that said, your images will still have separate URIs, although the UUID will be the same, of course, as the glance API endpoints will be different, I assume :)


Can you help with this problem?

Provide an answer of your own, or ask Peter Borghard for more information if necessary.

To post a message you must log in.