Re: [Openstack] Notifiers
We have been investigating over nova notifications. I really like the Sandy Walsh implementation for Essex SystemUsage Blueprint http://wiki.openstack.org/SystemUsageData. You can see the code in Change I33cc9076 https://review.openstack.org/#change,4194. This could be an alternative to glance aproach. cheers Juan On 14/03/12 14:29, Eric Windisch wrote: To make the notifiers common, the QAL / RPC will also have to be made common. The Glance code for notifications currently implements queue/rpc-implementation specific notifiers, so this might not be a bad thing… If there is an effort to move the RPC into openstack.common, then I would like to be involved, if only as a reviewer to ensure the queue abstraction layer makes it over safely. [I still question if we need an rpc.notify()…] -- Eric Windisch On Wednesday, March 14, 2012 at 5:19 AM, Juan Antonio García Lebrijo wrote: Hi, we are thinking to contribute to increase the types of notifications (events) through the rabbit server. We are thinking to notify from each Openstack component (nova, glance, quantum in the future ...) We think that unify the code on the openstack-common stuff is a great idea. We are really interested to collaborate on this topic. Cheers, Juan On 12/03/12 14:33, Swaminathan Venkataraman wrote: Hi, I've been playing around with openstack for a month now and was looking to see how I can contribute. I saw that nova and glance use different methods to send out notifications. It looked relatively straight forward to make them use one common library for notifications. That way, when we make changes or add new transports we do not have to do it twice (or more number of times depending on how other components of openstack do notifications). Let me know if someone is already working on this. If not, let me know if this makes sense and I can start by creating a blueprint. Also, is there any preference to use object oriented (or not)? Cheers, Venkat ___ Mailing list:https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to :openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe :https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help :https://help.launchpad.net/ListHelp -- Juan Antonio García Lebrijo *CTO* *www.stackops.com* http://www.stackops.com/ *| * juan.lebr...@stackops.com mailto:juan.lebr...@stackops.com| skype:juan.lebrijo.stackops ADVERTENCIA LEGAL Le informamos, como destinatario de este mensaje, que el correo electrónico y las comunicaciones por medio de Internet no permiten asegurar ni garantizar la confidencialidad de los mensajes transmitidos, así como tampoco su integridad o su correcta recepción, por lo que STACKOPS TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias. Si no consintiese en la utilización del correo electrónico o de las comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro conocimiento de manera inmediata. Este mensaje va dirigido, de manera exclusiva, a su destinatario y contiene información confidencial y sujeta al secreto profesional, cuya divulgación no está permitida por la ley. En caso de haber recibido este mensaje por error, le rogamos que, de forma inmediata, nos lo comunique mediante correo electrónico remitido a nuestra atención y proceda a su eliminación, así como a la de cualquier documento adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o utilización de este mensaje, o de cualquier documento adjunto al mismo, cualquiera que fuera su finalidad, están prohibidas por la ley. * PRIVILEGED AND CONFIDENTIAL We hereby inform you, as addressee of this message, that e-mail and Internet do not guarantee the confidentiality, nor the completeness or proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does not assume any liability for those circumstances. Should you not agree to the use of e-mail or to communications via Internet, you are kindly requested to notify us immediately. This message is intended exclusively for the person to whom it is addressed and contains privileged and confidential information protected from disclosure by law. If you are not the addressee indicated in this message, you should immediately delete it and any attachments and notify the sender by reply e-mail. In such case, you are hereby notified that any dissemination, distribution, copying or use of this message or any attachments, for any purpose, is strictly prohibited by law. ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack
Re: [Openstack] Notifiers
Hi, we are thinking to contribute to increase the types of notifications (events) through the rabbit server. We are thinking to notify from each Openstack component (nova, glance, quantum in the future ...) We think that unify the code on the openstack-common stuff is a great idea. We are really interested to collaborate on this topic. Cheers, Juan On 12/03/12 14:33, Swaminathan Venkataraman wrote: Hi, I've been playing around with openstack for a month now and was looking to see how I can contribute. I saw that nova and glance use different methods to send out notifications. It looked relatively straight forward to make them use one common library for notifications. That way, when we make changes or add new transports we do not have to do it twice (or more number of times depending on how other components of openstack do notifications). Let me know if someone is already working on this. If not, let me know if this makes sense and I can start by creating a blueprint. Also, is there any preference to use object oriented (or not)? Cheers, Venkat ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Juan Antonio García Lebrijo *CTO* *www.stackops.com* http://www.stackops.com/ *| * juan.lebr...@stackops.com mailto:juan.lebr...@stackops.com| skype:juan.lebrijo.stackops ADVERTENCIA LEGAL Le informamos, como destinatario de este mensaje, que el correo electrónico y las comunicaciones por medio de Internet no permiten asegurar ni garantizar la confidencialidad de los mensajes transmitidos, así como tampoco su integridad o su correcta recepción, por lo que STACKOPS TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias. Si no consintiese en la utilización del correo electrónico o de las comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro conocimiento de manera inmediata. Este mensaje va dirigido, de manera exclusiva, a su destinatario y contiene información confidencial y sujeta al secreto profesional, cuya divulgación no está permitida por la ley. En caso de haber recibido este mensaje por error, le rogamos que, de forma inmediata, nos lo comunique mediante correo electrónico remitido a nuestra atención y proceda a su eliminación, así como a la de cualquier documento adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o utilización de este mensaje, o de cualquier documento adjunto al mismo, cualquiera que fuera su finalidad, están prohibidas por la ley. * PRIVILEGED AND CONFIDENTIAL We hereby inform you, as addressee of this message, that e-mail and Internet do not guarantee the confidentiality, nor the completeness or proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does not assume any liability for those circumstances. Should you not agree to the use of e-mail or to communications via Internet, you are kindly requested to notify us immediately. This message is intended exclusively for the person to whom it is addressed and contains privileged and confidential information protected from disclosure by law. If you are not the addressee indicated in this message, you should immediately delete it and any attachments and notify the sender by reply e-mail. In such case, you are hereby notified that any dissemination, distribution, copying or use of this message or any attachments, for any purpose, is strictly prohibited by law. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Notifiers
To make the notifiers common, the QAL / RPC will also have to be made common. The Glance code for notifications currently implements queue/rpc-implementation specific notifiers, so this might not be a bad thing… If there is an effort to move the RPC into openstack.common, then I would like to be involved, if only as a reviewer to ensure the queue abstraction layer makes it over safely. [I still question if we need an rpc.notify()…] -- Eric Windisch On Wednesday, March 14, 2012 at 5:19 AM, Juan Antonio García Lebrijo wrote: Hi, we are thinking to contribute to increase the types of notifications (events) through the rabbit server. We are thinking to notify from each Openstack component (nova, glance, quantum in the future ...) We think that unify the code on the openstack-common stuff is a great idea. We are really interested to collaborate on this topic. Cheers, Juan On 12/03/12 14:33, Swaminathan Venkataraman wrote: Hi, I've been playing around with openstack for a month now and was looking to see how I can contribute. I saw that nova and glance use different methods to send out notifications. It looked relatively straight forward to make them use one common library for notifications. That way, when we make changes or add new transports we do not have to do it twice (or more number of times depending on how other components of openstack do notifications). Let me know if someone is already working on this. If not, let me know if this makes sense and I can start by creating a blueprint. Also, is there any preference to use object oriented (or not)? Cheers, Venkat ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Juan Antonio García Lebrijo CTO www.stackops.com (http://www.stackops.com/) | juan.lebr...@stackops.com (mailto:juan.lebr...@stackops.com) | skype:juan.lebrijo.stackops ADVERTENCIA LEGAL Le informamos, como destinatario de este mensaje, que el correo electrónico y las comunicaciones por medio de Internet no permiten asegurar ni garantizar la confidencialidad de los mensajes transmitidos, así como tampoco su integridad o su correcta recepción, por lo que STACKOPS TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias. Si no consintiese en la utilización del correo electrónico o de las comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro conocimiento de manera inmediata. Este mensaje va dirigido, de manera exclusiva, a su destinatario y contiene información confidencial y sujeta al secreto profesional, cuya divulgación no está permitida por la ley. En caso de haber recibido este mensaje por error, le rogamos que, de forma inmediata, nos lo comunique mediante correo electrónico remitido a nuestra atención y proceda a su eliminación, así como a la de cualquier documento adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o utilización de este mensaje, o de cualquier documento adjunto al mismo, cualquiera que fuera su finalidad, están prohibidas por la ley. * PRIVILEGED AND CONFIDENTIAL We hereby inform you, as addressee of this message, that e-mail and Internet do not guarantee the confidentiality, nor the completeness or proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does not assume any liability for those circumstances. Should you not agree to the use of e-mail or to communications via Internet, you are kindly requested to notify us immediately. This message is intended exclusively for the person to whom it is addressed and contains privileged and confidential information protected from disclosure by law. If you are not the addressee indicated in this message, you should immediately delete it and any attachments and notify the sender by reply e-mail. In such case, you are hereby notified that any dissemination, distribution, copying or use of this message or any attachments, for any purpose, is strictly prohibited by law. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Notifiers
On 03/12/2012 09:33 AM, Swaminathan Venkataraman wrote: Hi, I've been playing around with openstack for a month now and was looking to see how I can contribute. I saw that nova and glance use different methods to send out notifications. It looked relatively straight forward to make them use one common library for notifications. That way, when we make changes or add new transports we do not have to do it twice (or more number of times depending on how other components of openstack do notifications). Let me know if someone is already working on this. If not, let me know if this makes sense and I can start by creating a blueprint. Also, is there any preference to use object oriented (or not)? It is a surprise that the code is different for event notifications between Nova and Glance. I believe the same developer (Johannes Erdfelt) did them both. And I think his plan was to put the code into the openstack-common library. Johannes, thoughts? -jay ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Notifiers
On Mon, Mar 12, 2012, Jay Pipes jaypi...@gmail.com wrote: On 03/12/2012 09:33 AM, Swaminathan Venkataraman wrote: I've been playing around with openstack for a month now and was looking to see how I can contribute. I saw that nova and glance use different methods to send out notifications. It looked relatively straight forward to make them use one common library for notifications. That way, when we make changes or add new transports we do not have to do it twice (or more number of times depending on how other components of openstack do notifications). Let me know if someone is already working on this. If not, let me know if this makes sense and I can start by creating a blueprint. Also, is there any preference to use object oriented (or not)? It is a surprise that the code is different for event notifications between Nova and Glance. I believe the same developer (Johannes Erdfelt) did them both. And I think his plan was to put the code into the openstack-common library. Johannes, thoughts? I only did the work for Glance and it was based on the Nova code at the time. I guess the code has diverged in the 7 months since I did that work. I'm fine with getting it into common code, but I have no plans to do it myself. JE ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Notifiers
On 03/12/2012 11:56 AM, Johannes Erdfelt wrote: On Mon, Mar 12, 2012, Jay Pipesjaypi...@gmail.com wrote: On 03/12/2012 09:33 AM, Swaminathan Venkataraman wrote: I've been playing around with openstack for a month now and was looking to see how I can contribute. I saw that nova and glance use different methods to send out notifications. It looked relatively straight forward to make them use one common library for notifications. That way, when we make changes or add new transports we do not have to do it twice (or more number of times depending on how other components of openstack do notifications). Let me know if someone is already working on this. If not, let me know if this makes sense and I can start by creating a blueprint. Also, is there any preference to use object oriented (or not)? It is a surprise that the code is different for event notifications between Nova and Glance. I believe the same developer (Johannes Erdfelt) did them both. And I think his plan was to put the code into the openstack-common library. Johannes, thoughts? I only did the work for Glance and it was based on the Nova code at the time. I guess the code has diverged in the 7 months since I did that work. Ah, my mistake, thanks for the heads up. I'm fine with getting it into common code, but I have no plans to do it myself. OK. Yes, I too would be perfectly happy to see the code moved to openstack-common. Anybody interested in taking on that task? -jay ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Notifiers
On Mar 12, 2012, at 11:33 AM, Jay Pipes wrote: On 03/12/2012 11:56 AM, Johannes Erdfelt wrote: On Mon, Mar 12, 2012, Jay Pipesjaypi...@gmail.com wrote: On 03/12/2012 09:33 AM, Swaminathan Venkataraman wrote: I've been playing around with openstack for a month now and was looking to see how I can contribute. I saw that nova and glance use different methods to send out notifications. It looked relatively straight forward to make them use one common library for notifications. That way, when we make changes or add new transports we do not have to do it twice (or more number of times depending on how other components of openstack do notifications). Let me know if someone is already working on this. If not, let me know if this makes sense and I can start by creating a blueprint. Also, is there any preference to use object oriented (or not)? It is a surprise that the code is different for event notifications between Nova and Glance. I believe the same developer (Johannes Erdfelt) did them both. And I think his plan was to put the code into the openstack-common library. Johannes, thoughts? I only did the work for Glance and it was based on the Nova code at the time. I guess the code has diverged in the 7 months since I did that work. Ah, my mistake, thanks for the heads up. I'm fine with getting it into common code, but I have no plans to do it myself. OK. Yes, I too would be perfectly happy to see the code moved to openstack-common. Anybody interested in taking on that task? 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. -jay ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Monsyne M. Dragon OpenStack/Nova cell 210-441-0965 work x 5014190 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Notifiers
Hi, 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. thanks, Venkat On Tue, Mar 13, 2012 at 8:48 AM, Monsyne Dragon mdra...@rackspace.comwrote: On Mar 12, 2012, at 11:33 AM, Jay Pipes wrote: On 03/12/2012 11:56 AM, Johannes Erdfelt wrote: On Mon, Mar 12, 2012, Jay Pipesjaypi...@gmail.com wrote: On 03/12/2012 09:33 AM, Swaminathan Venkataraman wrote: I've been playing around with openstack for a month now and was looking to see how I can contribute. I saw that nova and glance use different methods to send out notifications. It looked relatively straight forward to make them use one common library for notifications. That way, when we make changes or add new transports we do not have to do it twice (or more number of times depending on how other components of openstack do notifications). Let me know if someone is already working on this. If not, let me know if this makes sense and I can start by creating a blueprint. Also, is there any preference to use object oriented (or not)? It is a surprise that the code is different for event notifications between Nova and Glance. I believe the same developer (Johannes Erdfelt) did them both. And I think his plan was to put the code into the openstack-common library. Johannes, thoughts? I only did the work for Glance and it was based on the Nova code at the time. I guess the code has diverged in the 7 months since I did that work. Ah, my mistake, thanks for the heads up. I'm fine with getting it into common code, but I have no plans to do it myself. OK. Yes, I too would be perfectly happy to see the code moved to openstack-common. Anybody interested in taking on that task? 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. -jay ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Monsyne M. Dragon OpenStack/Nova cell 210-441-0965 work x 5014190 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
