To follow up on what others have said, the method described in the
command example
https://docs.puppetlabs.com/puppetdb/2.2/api/commands.html#examples-using-curl
will deactivate your node, which is different than what we call
"purging", whether or not you intended.
Deactivating a node will not purge it from the database, it will simply
mark it deactivated and cause it to be filtered from the output of most
queries. The node is actually purged from the database when it has been
deactivated for the length of time specified by the setting
node-purge-ttl, which is documented here:
https://docs.puppetlabs.com/puppetdb/latest/configure.html#node-purge-ttl
If you set this to 0m, nodes will be purged on the next garbage
collection (configurable by the gc-interval setting, 60 minutes by default.)
Wyatt
On 12/11/14 1:04 AM, Martin Alfke wrote:
Hi Matt,
On 09 Dec 2014, at 19:58, Matt Wise <m...@nextdoor.com> wrote:
We boot up/shut-down 50-100 hosts a day on average... we're exploring PuppetDB,
but I'm concerned about the model of just 'waiting' for hosts to be purged
based on some checkin time. Is there any way to have our hosts send a signal
through the puppet-masters (or directly to puppetdb?) to purge themselves when
they're being terminated?
You can use the puppetdb rest api:
https://docs.puppetlabs.com/puppetdb/2.2/api/index.html
In my actual project we disable hosts via VM management system using this API.
Works like a charm.
hth,
Martin
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/548A2797.10100%40puppetlabs.com.
For more options, visit https://groups.google.com/d/optout.
