<div>Hi,</div><div>I'd be happy to take a stab at that. I guess, the process would be to move the code that we have in glance to openstack-common and change glance accordingly. I would then have to modify nova to use code in openstack-common. Let mek know.</div>
<div> </div><div>thanks,<br>Venkat<br><br></div><div class="gmail_quote">On Tue, Mar 13, 2012 at 8:48 AM, Monsyne Dragon <span dir="ltr"><<a href="mailto:mdragon@rackspace.com">mdragon@rackspace.com</a>></span> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote"><div class="HOEnZb"><div class="h5"><br>
On Mar 12, 2012, at 11:33 AM, Jay Pipes wrote:<br>
<br>
> On 03/12/2012 11:56 AM, Johannes Erdfelt wrote:<br>
>> On Mon, Mar 12, 2012, Jay Pipes<<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>> wrote:<br>
>>> On 03/12/2012 09:33 AM, Swaminathan Venkataraman wrote:<br>
>>>> I've been playing around with openstack for a month now and was looking<br>
>>>> to see how I can contribute. I saw that nova and glance use different<br>
>>>> methods to send out notifications. It looked relatively straight forward<br>
>>>> to make them use one common library for notifications. That way, when we<br>
>>>> make changes or add new transports we do not have to do it twice (or<br>
>>>> more number of times depending on how other components of openstack do<br>
>>>> notifications). Let me know if someone is already working on this. If<br>
>>>> not, let me know if this makes sense and I can start by creating a<br>
>>>> blueprint. Also, is there any preference to use object oriented (or not)?<br>
>>><br>
>>> It is a surprise that the code is different for event notifications<br>
>>> between Nova and Glance. I believe the same developer (Johannes<br>
>>> Erdfelt) did them both. And I think his plan was to put the code<br>
>>> into the openstack-common library.<br>
>>><br>
>>> Johannes, thoughts?<br>
>><br>
>> I only did the work for Glance and it was based on the Nova code at the<br>
>> time. I guess the code has diverged in the 7 months since I did that<br>
>> work.<br>
><br>
> Ah, my mistake, thanks for the heads up.<br>
><br>
>> I'm fine with getting it into common code, but I have no plans to do it<br>
>> myself.<br>
><br>
> OK.<br>
><br>
> Yes, I too would be perfectly happy to see the code moved to openstack-common.<br>
><br>
> Anybody interested in taking on that task?<br>
><br>
<br>
</div></div>I did the nova notification framework, and much of the notifications. I've noticed that the glance notifications were not quite the same format as nova, and I've been doing work to fix that. IMHO, putting this in openstack.common is A Really Good Idea. I'd be happy to take on that task.<br>
<div class="im"><br>
<br>
> -jay<br>
><br>
> _______________________________________________<br>
> Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br>
</div>--<br>
Monsyne M. Dragon<br>
OpenStack/Nova<br>
cell 210-441-0965<br>
work x 5014190<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
</div></div></blockquote></div><br>