Hi Jim, I can't think of a supported way to do custom event-driven hooks as you describe, but that sounds like a very useful enhancement.
If you don't want to poll the API, I would suggest monitoring /var/log/maas.log. You'll be able to tell when a machine changes state, such as by looking for the following log messages: Feb 1 19:09:34 maas maas.node: [info] pxe1: Status transition from NEW to COMMISSIONING Feb 1 19:11:36maas maas.node: [info] pxe1: Status transition from COMMISSIONING to READY Feb 1 19:12:05 maas maas.node: [info] pxe1: Status transition from READY to ALLOCATED Feb 1 19:12:05 maas maas.node: [info] pxe1: Status transition from ALLOCATED to DEPLOYING Feb 1 19:16:05 maas maas.node: [info] pxe1: Status transition from DEPLOYING to DEPLOYED Feb 1 19:16:15 maas maas.node: [info] pxe1: Status transition from DEPLOYED to RELEASING Feb 1 19:16:19 maas maas.node: [info] pxe1: Status transition from RELEASING to READY Regards, Mike On Wed, Feb 1, 2017 at 9:44 AM, Jim Tilander <[email protected]> wrote: > Hi, > > I’ve got puppet hooked up to the images we deploy with maas and need some > way to cleanup the nodes that we “release” from puppet. I’m wondering if > there are some hooks on the maas server itself that fire when you click > “Release” in the webUI, alternatively react to any released node with > appropriate metadata so one can perform some cleanup? > > Cheers, > Jim > -- > Maas-devel mailing list > [email protected] > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/maas-devel >
-- Maas-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/maas-devel
