← Back to team overview

openstack team mailing list archive

Re: Running code on instance start/terminate

 

I'm trying to find out information to make an application that consumes the
compute info, but I'm having some trouble. Is there a better documentation
I could follow and the precise details of the queue/exchange/routing_key
needed to take information at the end of each run-instance and
terminate-instance?

Also, I'm using amqplib and I saw that Openstack uses an internal library
named Carrot that uses amqplib. Would it be better to use it instead?

Em 27 de março de 2012 12:42, Sandy Walsh <sandy.walsh@xxxxxxxxxxxxx>escreveu:

> I believe '.exists' is sent via a periodic update in compute.manager.
>
>
>
> On 03/27/2012 12:08 PM, Leander Bessa wrote:
> > Hello,
> >
> > I've been following this topic and i've been trying to receive the
> > notifications directly from rabbitmq with python+pika. So i far
> > i've managed to receive the start/terminate events and everything in
> > between. What i am unable to find though is the topic regarding
> > _compute.instance.exists_
> > from http://wiki.openstack.org/SystemUsageData. Does this even exist, or
> > is there some extra configuration required with nova?
> >
> > Regards,
> >
> > Leander
> >
> > On Mon, Mar 26, 2012 at 4:54 PM, Russell Bryant <rbryant@xxxxxxxxxx
> > <mailto:rbryant@xxxxxxxxxx>> wrote:
> >
> >     -----BEGIN PGP SIGNED MESSAGE-----
> >     Hash: SHA1
> >
> >     On 03/26/2012 11:48 AM, Russell Bryant wrote:
> >     > On 03/26/2012 10:15 AM, Rogério Vinhal Nunes wrote:
> >     >> Hello,
> >     >>
> >     >> I'm developing a application to work along with openstack. My
> >     >> application needs to keep track of all instances being started
> >     >> or terminated such as feeding it information about the location,
> >     >> status and other information about launched and terminated
> >     >> instances. The current version makes timed queries to OpenStack
> >     >> database, but this is showing to be a little consuming and
> >     >> inefficient, so I would like to add a portion of code to make
> >     >> OpenStack actively feed my application information whenever an
> >     >> instance changes its status or location.
> >     >>
> >     >> What is the least intrusive way to do that? It would be very nice
> >     >> if OpenStack provided a way to run code on these situations
> >     >> without actually changing any code, such as defining a directory
> >     >> of scripts to run in every instance status change.
> >     >
> >     > Check out the notifications system:
> >     >
> >     > http://wiki.openstack.org/NotificationSystem
> >     >
> >
> >     That wasn't the page I thought it was ... I meant:
> >
> >        http://wiki.openstack.org/SystemUsageData
> >
> >     You can consume these events via AMQP if you configure nova to use
> the
> >     rabbit notifier.
> >
> >     - --
> >     Russell Bryant
> >     -----BEGIN PGP SIGNATURE-----
> >     Version: GnuPG v1.4.12 (GNU/Linux)
> >     Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> >
> >     iEYEARECAAYFAk9wkSgACgkQFg9ft4s9SAYFuACfUu23qtxiH6WLCJNyd9gBf8i1
> >     FwQAnifjwWkFHYxo+KhYt8TAWEzTaMYZ
> >     =UWlH
> >     -----END PGP SIGNATURE-----
> >
> >     _______________________________________________
> >     Mailing list: https://launchpad.net/~openstack
> >     Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> >     <mailto:openstack@xxxxxxxxxxxxxxxxxxx>
> >     Unsubscribe : https://launchpad.net/~openstack
> >     More help   : https://help.launchpad.net/ListHelp
> >
> >
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openstack
> > Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

Follow ups

References