Open Stack

What I was doing was to replicate the glance database across sites. This has pros and cons.

Pro
Same glance UUID’s everywhere
One-stop updating of images

Cons
Requires db replication (we already had it in place)
initial caching of images is subject to your bandwidth between sites (image_locations table) - This can be mitigated with things like swift container sync

On May 20, 2014, at 2:41 PM, Scott Devoid <devoid at anl.gov> wrote:

> We have two glance instances in separate deployments (an essex deployment and a havana deployment) and we would like to synchronize images between the two.
> 
> Uploading the raw image data works fine with either the command line or the API, but making the metadata consistent is quite difficult. In the essex API I can't even find container_format or disk_format reported in the instance.
> 
> I also can't find a way with the client to affix the snapshot metadata on the Havana side other than through a direct HTTP PATCH request, and it is not very clear what headers that request is expecting. [1]
> 
> Another thought I had, since both instances of glance are using the Filesystem store (w/ separate NFS deployments) was to simply use the existing NFS in essex and inform the havana glance about the existence of an image through the --location tag. However this is intentionally blocked. [2]
> 
> Thank you in advance for the help,
> ~ Scott
> 
> [1] http://developer.openstack.org/api-ref-identity-v2.html
> [2] https://bugs.launchpad.net/glance/+bug/942118
> 
> 
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20140520/37cc0592/attachment.html>