<div dir="ltr"><div>Hi there Joe,</div><div><br></div><div>What we do with the notifications is read them from single queue defined by rabbit_notification_topic and then recreate the messages into unique queues for each individual glance-api node. This allows each glance-api node to sync images independently from one-another and should one node temporarily drop offline it'll just process any image.update or image.delete messages when it comes back online.</div>
<div><br></div><div style>You'd run into issues using glance-image-sync across several very busy glance-api nodes, but for smaller / quieter installations it should work OK.</div><div><br></div><div>Thanks,</div><div>
Matt</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 23, 2013 at 5:22 PM, Joe Topjian <span dir="ltr"><<a href="mailto:joe.topjian@cybera.ca" target="_blank">joe.topjian@cybera.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Matt,<div><br></div><div>This is pretty cool. I'm curious about the need to synchronize notifications?</div>
<div><br></div><div>On this same topic: Michael Still wrote a similar tool called glance-replicator (<a href="http://docs.openstack.org/trunk/openstack-compute/admin/content/replicating-images.html" target="_blank">http://docs.openstack.org/trunk/openstack-compute/admin/content/replicating-images.html</a>).</div>
<div><br></div><div><br></div><div>Thanks,</div><div>Joe</div></div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">On Tue, Apr 23, 2013 at 4:28 AM, Matt Thompson <span dir="ltr"><<a href="mailto:wateringcan@gmail.com" target="_blank">wateringcan@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">Hi Ad,</span><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">I echo what has already been said, but I did need something to replicate images on my glance nodes when using local file store and wrote a quick script at <a href="https://github.com/mattt416/glance-image-sync" target="_blank">https://github.com/mattt416/glance-image-sync</a> as a result. It's not ideal, but does get the job done for this specific situation.</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">Feel free to send issues/comments/pull requests via github if you find it of any use.</div><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">Thanks,</div><div style="font-family:arial,sans-serif;font-size:13px">Matt</div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>
On Mon, Mar 18, 2013 at 10:12 PM, Ahmad Ahmadi <span dir="ltr"><<a href="mailto:ahmadidamha@yahoo.com" target="_blank">ahmadidamha@yahoo.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div><div style="font-size:12pt;font-family:times new roman,new york,times,serif">Hi,<br>
<br>How can I have multiple glance nodes in a way that, when I
create an image from the controler, it would be coppied to all of the
glance nodes?<br>Now, when I define multiple glance endpoints in the controler (keystone), the images would only go to the first glance node.<br><br>I also want to avoid putting the name of all glance nodes in the nova nodes.<br>
<br>Thank you,<br>Ad<br><div><div><img> </div></div></div></div><br></div></div><div>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></div></blockquote></div><br></div></div>
<br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div></div></div><div class="im">-- <br>Joe Topjian<div>Systems Administrator</div><div>Cybera Inc.</div><div><br></div><div><a href="http://www.cybera.ca" target="_blank">www.cybera.ca</a></div>
<div><br></div><div><font color="#666666"><span>Cybera</span><span> is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure.</span></font></div>
</div></div>
</blockquote></div><br></div></div>