Re: [Puppet Users] Re: Need a solution for puppet node clean (puppet v3.0.2)
Perhaps you want to use 'puppet node deactivate' for now: http://docs.puppetlabs.com/puppetdb/1.1/maintain_and_tune.html#deactivate-decommissioned-nodes This will at least remove it from being collected immediately, but it leaves it in the database. So beyond that we are working on an automated clean mechanism in PuppetDB: https://projects.puppetlabs.com/issues/18682#change-82618 ... which as you can see is in code review right now. If all goes well this should be in a release coming to your cinemas soon ... :-). ken. On Wed, Feb 6, 2013 at 4:59 AM, David Kerr ker...@gmail.com wrote: On Tuesday, February 5, 2013 8:54:47 PM UTC-8, Josh Cooper wrote: Hi David, On Tue, Feb 5, 2013 at 7:44 PM, David Kerr ker...@gmail.com wrote: We upgraded to the new release of Puppet 3.1 and puppet node clean still doesn't work. I've found that the delete query comes back empty, but the node is still in the system. puppet node deactivate still works. -- 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...@googlegroups.com. To post to this group, send email to puppet...@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. Sounds like you're running into http://projects.puppetlabs.com/issues/15051 Josh -- Josh Cooper Developer, Puppet Labs ah, ok, i thought it was supposed to be fixed in 3.1 5 months old on the last update, any hope for a solution soon? thanks. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Need a solution for puppet node clean (puppet v3.0.2)
On Wednesday, February 6, 2013 6:06:49 AM UTC-6, Ken Barber wrote: Perhaps you want to use 'puppet node deactivate' for now: http://docs.puppetlabs.com/puppetdb/1.1/maintain_and_tune.html#deactivate-decommissioned-nodes This will at least remove it from being collected immediately, but it leaves it in the database. So beyond that we are working on an automated clean mechanism in PuppetDB: https://projects.puppetlabs.com/issues/18682#change-82618 ... which as you can see is in code review right now. If all goes well this should be in a release coming to your cinemas soon ... :-). ken. I would also take a look at https://ask.puppetlabs.com/question/88/how-can-i-purge-exported-resources-from-puppetdb/ which discusses this same issue and has a couple of alternatives, though YMMV, emptor caveat and all that type of thing. On Wed, Feb 6, 2013 at 4:59 AM, David Kerr ker...@gmail.com javascript: wrote: On Tuesday, February 5, 2013 8:54:47 PM UTC-8, Josh Cooper wrote: Hi David, On Tue, Feb 5, 2013 at 7:44 PM, David Kerr ker...@gmail.com wrote: We upgraded to the new release of Puppet 3.1 and puppet node clean still doesn't work. I've found that the delete query comes back empty, but the node is still in the system. puppet node deactivate still works. -- 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...@googlegroups.com. To post to this group, send email to puppet...@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. Sounds like you're running into http://projects.puppetlabs.com/issues/15051 Josh -- Josh Cooper Developer, Puppet Labs ah, ok, i thought it was supposed to be fixed in 3.1 5 months old on the last update, any hope for a solution soon? thanks. -- 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...@googlegroups.com javascript:. To post to this group, send email to puppet...@googlegroups.comjavascript:. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Need a solution for puppet node clean (puppet v3.0.2)
On Wednesday, February 6, 2013 5:40:41 AM UTC-8, llowder wrote: On Wednesday, February 6, 2013 6:06:49 AM UTC-6, Ken Barber wrote: Perhaps you want to use 'puppet node deactivate' for now: http://docs.puppetlabs.com/puppetdb/1.1/maintain_and_tune.html#deactivate-decommissioned-nodes This will at least remove it from being collected immediately, but it leaves it in the database. So beyond that we are working on an automated clean mechanism in PuppetDB: https://projects.puppetlabs.com/issues/18682#change-82618 ... which as you can see is in code review right now. If all goes well this should be in a release coming to your cinemas soon ... :-). ken. I would also take a look at https://ask.puppetlabs.com/question/88/how-can-i-purge-exported-resources-from-puppetdb/which discusses this same issue and has a couple of alternatives, though YMMV, emptor caveat and all that type of thing. Yes you sent me that before, earlier on the thread =) Those tips work just fine and I've baked them into my scripts. However I had read that puppet node clean was scheduled to be fixed in 3.1 and it isn't so I wanted to make sure I wasn't doing something else wrong. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Need a solution for puppet node clean (puppet v3.0.2)
Hi David, On Wed, Feb 6, 2013 at 9:01 AM, David Kerr ker...@gmail.com wrote: On Wednesday, February 6, 2013 5:40:41 AM UTC-8, llowder wrote: On Wednesday, February 6, 2013 6:06:49 AM UTC-6, Ken Barber wrote: Perhaps you want to use 'puppet node deactivate' for now: http://docs.puppetlabs.com/puppetdb/1.1/maintain_and_tune.html#deactivate-decommissioned-nodes This will at least remove it from being collected immediately, but it leaves it in the database. So beyond that we are working on an automated clean mechanism in PuppetDB: https://projects.puppetlabs.com/issues/18682#change-82618 ... which as you can see is in code review right now. If all goes well this should be in a release coming to your cinemas soon ... :-). ken. I would also take a look at https://ask.puppetlabs.com/question/88/how-can-i-purge-exported-resources-from-puppetdb/ which discusses this same issue and has a couple of alternatives, though YMMV, emptor caveat and all that type of thing. Yes you sent me that before, earlier on the thread =) Those tips work just fine and I've baked them into my scripts. However I had read that puppet node clean was scheduled to be fixed in 3.1 and it isn't so I wanted to make sure I wasn't doing something else wrong. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. This didn't make the 3.1 cut, but it's in our proposed for next iteration queue and should be resolved in the next release. Josh -- Josh Cooper Developer, Puppet Labs -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Need a solution for puppet node clean (puppet v3.0.2)
We upgraded to the new release of Puppet 3.1 and puppet node clean still doesn't work. I've found that the delete query comes back empty, but the node is still in the system. puppet node deactivate still works. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Need a solution for puppet node clean (puppet v3.0.2)
Hi David, On Tue, Feb 5, 2013 at 7:44 PM, David Kerr ker...@gmail.com wrote: We upgraded to the new release of Puppet 3.1 and puppet node clean still doesn't work. I've found that the delete query comes back empty, but the node is still in the system. puppet node deactivate still works. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. Sounds like you're running into http://projects.puppetlabs.com/issues/15051 Josh -- Josh Cooper Developer, Puppet Labs -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Need a solution for puppet node clean (puppet v3.0.2)
On Tuesday, February 5, 2013 8:54:47 PM UTC-8, Josh Cooper wrote: Hi David, On Tue, Feb 5, 2013 at 7:44 PM, David Kerr ker...@gmail.com javascript: wrote: We upgraded to the new release of Puppet 3.1 and puppet node clean still doesn't work. I've found that the delete query comes back empty, but the node is still in the system. puppet node deactivate still works. -- 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...@googlegroups.com javascript:. To post to this group, send email to puppet...@googlegroups.comjavascript:. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. Sounds like you're running into http://projects.puppetlabs.com/issues/15051 Josh -- Josh Cooper Developer, Puppet Labs ah, ok, i thought it was supposed to be fixed in 3.1 5 months old on the last update, any hope for a solution soon? thanks. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Need a solution for puppet node clean (puppet v3.0.2)
David, Are you using PuppetDB? There was a thread on this list recently about the same topic, and there was some example SQL that could be used in the short-term. We have a few open tickets around coming up with better solutions for this and we expect to be addressing them Very Soon Now. If you are using PuppetDB and you are interested in links (to either the tickets or the previous thread) let me know and I'll dig them up. Thanks! Chris On Thursday, January 31, 2013 10:26:18 AM UTC-8, David Kerr wrote: My environment heavily depends on exported resources to detect our mongo instances and to populate our haproxies. When we bring up and down nodes in AWS puppet node clean isn't cleaning up the exported resources so we get ghost machines loaded into those config files. Up until today I've attempted to limp along by doing: puppet node clean sudo puppet cert clean delete from catalog_resources where title like '%hostname%' delete from resource_params where value like '%hostname%' That's been pretty good, but today I ran into a problem where even that didn't work. I'm comfortable working in the DB, but what's tough is trying to match the hashed ID's across tables (the data model doesn't make it exactly clear what's going on) If someone's already tackled this beast and has a script that does it right, that would be fantastic. I also understand that this is solved in 3.1, but I'm not too keen on upgrading to an RC just to get exported resources working correctly. If someone has insight into the data model and can help me fill the gaps that would be wonderful Thanks. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Need a solution for puppet node clean (puppet v3.0.2)
I am using PuppetDB and I'd love the links, I did some searching and wasn't able to find the conversation. Thanks for the reply! On Thursday, January 31, 2013 12:55:54 PM UTC-8, Chris Price wrote: David, Are you using PuppetDB? There was a thread on this list recently about the same topic, and there was some example SQL that could be used in the short-term. We have a few open tickets around coming up with better solutions for this and we expect to be addressing them Very Soon Now. If you are using PuppetDB and you are interested in links (to either the tickets or the previous thread) let me know and I'll dig them up. Thanks! Chris On Thursday, January 31, 2013 10:26:18 AM UTC-8, David Kerr wrote: My environment heavily depends on exported resources to detect our mongo instances and to populate our haproxies. When we bring up and down nodes in AWS puppet node clean isn't cleaning up the exported resources so we get ghost machines loaded into those config files. Up until today I've attempted to limp along by doing: puppet node clean sudo puppet cert clean delete from catalog_resources where title like '%hostname%' delete from resource_params where value like '%hostname%' That's been pretty good, but today I ran into a problem where even that didn't work. I'm comfortable working in the DB, but what's tough is trying to match the hashed ID's across tables (the data model doesn't make it exactly clear what's going on) If someone's already tackled this beast and has a script that does it right, that would be fantastic. I also understand that this is solved in 3.1, but I'm not too keen on upgrading to an RC just to get exported resources working correctly. If someone has insight into the data model and can help me fill the gaps that would be wonderful Thanks. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Need a solution for puppet node clean (puppet v3.0.2)
On Thursday, January 31, 2013 3:10:12 PM UTC-6, David Kerr wrote: I am using PuppetDB and I'd love the links, I did some searching and wasn't able to find the conversation. Thanks for the reply! This may help. https://ask.puppetlabs.com/question/88/how-can-i-purge-exported-resources-from-puppetdb/ On Thursday, January 31, 2013 12:55:54 PM UTC-8, Chris Price wrote: David, Are you using PuppetDB? There was a thread on this list recently about the same topic, and there was some example SQL that could be used in the short-term. We have a few open tickets around coming up with better solutions for this and we expect to be addressing them Very Soon Now. If you are using PuppetDB and you are interested in links (to either the tickets or the previous thread) let me know and I'll dig them up. Thanks! Chris On Thursday, January 31, 2013 10:26:18 AM UTC-8, David Kerr wrote: My environment heavily depends on exported resources to detect our mongo instances and to populate our haproxies. When we bring up and down nodes in AWS puppet node clean isn't cleaning up the exported resources so we get ghost machines loaded into those config files. Up until today I've attempted to limp along by doing: puppet node clean sudo puppet cert clean delete from catalog_resources where title like '%hostname%' delete from resource_params where value like '%hostname%' That's been pretty good, but today I ran into a problem where even that didn't work. I'm comfortable working in the DB, but what's tough is trying to match the hashed ID's across tables (the data model doesn't make it exactly clear what's going on) If someone's already tackled this beast and has a script that does it right, that would be fantastic. I also understand that this is solved in 3.1, but I'm not too keen on upgrading to an RC just to get exported resources working correctly. If someone has insight into the data model and can help me fill the gaps that would be wonderful Thanks. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Need a solution for puppet node clean (puppet v3.0.2)
That does look like what i'm looking for, thanks! Dave On Thursday, January 31, 2013 1:24:06 PM UTC-8, llowder wrote: On Thursday, January 31, 2013 3:10:12 PM UTC-6, David Kerr wrote: I am using PuppetDB and I'd love the links, I did some searching and wasn't able to find the conversation. Thanks for the reply! This may help. https://ask.puppetlabs.com/question/88/how-can-i-purge-exported-resources-from-puppetdb/ On Thursday, January 31, 2013 12:55:54 PM UTC-8, Chris Price wrote: David, Are you using PuppetDB? There was a thread on this list recently about the same topic, and there was some example SQL that could be used in the short-term. We have a few open tickets around coming up with better solutions for this and we expect to be addressing them Very Soon Now. If you are using PuppetDB and you are interested in links (to either the tickets or the previous thread) let me know and I'll dig them up. Thanks! Chris On Thursday, January 31, 2013 10:26:18 AM UTC-8, David Kerr wrote: My environment heavily depends on exported resources to detect our mongo instances and to populate our haproxies. When we bring up and down nodes in AWS puppet node clean isn't cleaning up the exported resources so we get ghost machines loaded into those config files. Up until today I've attempted to limp along by doing: puppet node clean sudo puppet cert clean delete from catalog_resources where title like '%hostname%' delete from resource_params where value like '%hostname%' That's been pretty good, but today I ran into a problem where even that didn't work. I'm comfortable working in the DB, but what's tough is trying to match the hashed ID's across tables (the data model doesn't make it exactly clear what's going on) If someone's already tackled this beast and has a script that does it right, that would be fantastic. I also understand that this is solved in 3.1, but I'm not too keen on upgrading to an RC just to get exported resources working correctly. If someone has insight into the data model and can help me fill the gaps that would be wonderful Thanks. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Need a solution for puppet node clean (puppet v3.0.2)
I was searching about these some days ago and I found somewhere that the 'puppet node deactivate nodename' would do the tricky. I haven't tried it yet, so I can't confirm it works. On Thursday, January 31, 2013 12:55:54 PM UTC-8, Chris Price wrote: David, Are you using PuppetDB? There was a thread on this list recently about the same topic, and there was some example SQL that could be used in the short-term. We have a few open tickets around coming up with better solutions for this and we expect to be addressing them Very Soon Now. If you are using PuppetDB and you are interested in links (to either the tickets or the previous thread) let me know and I'll dig them up. Thanks! Chris On Thursday, January 31, 2013 10:26:18 AM UTC-8, David Kerr wrote: My environment heavily depends on exported resources to detect our mongo instances and to populate our haproxies. When we bring up and down nodes in AWS puppet node clean isn't cleaning up the exported resources so we get ghost machines loaded into those config files. Up until today I've attempted to limp along by doing: puppet node clean sudo puppet cert clean delete from catalog_resources where title like '%hostname%' delete from resource_params where value like '%hostname%' That's been pretty good, but today I ran into a problem where even that didn't work. I'm comfortable working in the DB, but what's tough is trying to match the hashed ID's across tables (the data model doesn't make it exactly clear what's going on) If someone's already tackled this beast and has a script that does it right, that would be fantastic. I also understand that this is solved in 3.1, but I'm not too keen on upgrading to an RC just to get exported resources working correctly. If someone has insight into the data model and can help me fill the gaps that would be wonderful Thanks. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
