Re: [openstack-dev] [Tatu][Nova] Handling instance destruction

I think it would simplify deployment a fair bit too -- a single API to provide instead of also having to setup a notification listener. I shall ponder and perhaps implement once I've finished the privsep stuff. Michael On Fri, Mar 16, 2018 at 5:49 PM, Juan Antonio Osorio

Re: [openstack-dev] [Tatu][Nova] Handling instance destruction

Having an interface for vendordata that gets deletes would be quite nice. Right now for novajoin we listen to the nova notifications for updates and deletes; if this could be handled natively by vendordata, it would simplify our codebase. BR On Fri, Mar 16, 2018 at 7:34 AM, Michael Still

Re: [openstack-dev] [Tatu][Nova] Handling instance destruction

Thanks for this. I read the README for the project after this and I do now realise you're using notifications for some of these events. I guess I'm still pondering if its reasonable to have everyone listen to notifications to build systems like these, or if we should messages to vendordata to

Re: [openstack-dev] [Tatu][Nova] Handling instance destruction

Hi Michael, Thanks for your message... and thanks for your vendordata work! About your question, Tatu listens to events on the oslo message bus. Specifically, it reacts to compute.instance.delete.end by cleaning up per-instance resources. It also listens to project creation and user role

[openstack-dev] [Tatu][Nova] Handling instance destruction

Heya, I've just stumbled across Tatu and the design presentation [1], and I am wondering how you handle cleaning up instances when they are deleted given that nova vendordata doesn't expose a "delete event". Specifically I'm wondering if we should add support for such an event to vendordata