[Puppet Users] Re: PuppetDB low catalog-duplication rate Puppet DB 4.3.0
Yes I am on V4 and the query just didn't return any results - no errors so I assume I am using the correct curl command. Thanks On Wednesday, June 28, 2017 at 2:11:17 PM UTC-4, Mike Sharpton wrote: > > Hey all, > > I am hoping there is someone else in the same boat as I am. We are > running Puppet 4.2.2, along with PuppetDB 4.3.0. I am seeing low > duplication rate which I think is contributing to our queuing problems in > PuppetDB. The queue will fluctuate from 0-100 queued, to up to 2000. We > have around 4500 nodes, and we are using 8 threads on our PuppetDB server. > I am seeing that the low duplication rate is caused by hashes not matching > and a full insert running which is expensive on the DB instead of just > updating the time stamp. I don't know why these would not be matching, and > may need help as far as how to find something like this. I see items in > PuppetDB3 for this, but not 4. I see that using timestamp and other items > which change each time will cause the catalog to never be the same, but I > would think we would have 0% duplication if this was the case. I am also > seeing that things are improved in 4.4.0 as far as performance and a > missing index is corrected that may speed things. I am wondering what > others have done/seen with this and whether upgrading to 4.4.0 would do me > good. I am thinking it would as many things appear to fixed around the > issues I am seeing. Thanks in advance, > > Mike > -- 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/d3b49873-5665-4286-bba2-b69ae304ae8e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: parameters and hiera
This is exactly how we use Foreman & Hiera in our installation... The key thing to set is when configuring the Puppet classes in Foreman, the 'Use Puppet Default' or 'Override' box needs to be checked. This means that if no values are stored in Foreman, then no value will be provided to Puppet, and Puppet will then use Hiera to look that value up. If you don't check that box, then you run the risk of providing empty strings to Puppet, thereby skipping the Hiera lookup :) HTH Gav On Monday, 10 July 2017 16:44:32 UTC+1, Salty Old Cowdawg wrote: > > In the shop that I code for these days we have The Foreman ENC set up and > running. I want to add hiera to the mix but allow our operations folks the > options the ability to change parameter values using the Foreman GUI. > Given the applications we are having Puppet manage this is rather mandatory > since the values in question get changed often enough to deal with changes > in the operational conditions as they change. Having operators edit hiera > YAML files is not a desired thing. > > I have some ideas for how to implement this but would like some input from > others that may have dealt with the same thing. What I'm looking for is a > coding pattern that says "if foreman is blank, use hiera and if hiera is > blank use this default." > > thoughts anybody? > > -- 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/311ba2bb-87a6-4c73-905b-339bed9dd779%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] parameters and hiera
In the shop that I code for these days we have The Foreman ENC set up and running. I want to add hiera to the mix but allow our operations folks the options the ability to change parameter values using the Foreman GUI. Given the applications we are having Puppet manage this is rather mandatory since the values in question get changed often enough to deal with changes in the operational conditions as they change. Having operators edit hiera YAML files is not a desired thing. I have some ideas for how to implement this but would like some input from others that may have dealt with the same thing. What I'm looking for is a coding pattern that says "if foreman is blank, use hiera and if hiera is blank use this default." thoughts anybody? -- 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/CAArvnv2hyXDTSvx_r3cdst78qy4fbG7M5bfCkJDXRMHr%2BTMwDg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: PuppetDB low catalog-duplication rate Puppet DB 4.3.0
If you are not on PuppetDB 4 the uri would be different is my guess. The v4 part specifically. I have still not had time to mess with this, but I was able to query via the uri that was given above. On Friday, July 7, 2017 at 7:03:12 AM UTC-5, Peter Krawetzky wrote: > > So I went to run the curl command listed below and it came back with > nothing. So I used pgadmin to look at the catalogs table and it's > completely empty. The system has been running for almost 24 hours after > dropping/creating the postgresql database. Any idea why the catalog table > would be empty? > > On Wednesday, June 28, 2017 at 2:11:17 PM UTC-4, Mike Sharpton wrote: >> >> Hey all, >> >> I am hoping there is someone else in the same boat as I am. We are >> running Puppet 4.2.2, along with PuppetDB 4.3.0. I am seeing low >> duplication rate which I think is contributing to our queuing problems in >> PuppetDB. The queue will fluctuate from 0-100 queued, to up to 2000. We >> have around 4500 nodes, and we are using 8 threads on our PuppetDB server. >> I am seeing that the low duplication rate is caused by hashes not matching >> and a full insert running which is expensive on the DB instead of just >> updating the time stamp. I don't know why these would not be matching, and >> may need help as far as how to find something like this. I see items in >> PuppetDB3 for this, but not 4. I see that using timestamp and other items >> which change each time will cause the catalog to never be the same, but I >> would think we would have 0% duplication if this was the case. I am also >> seeing that things are improved in 4.4.0 as far as performance and a >> missing index is corrected that may speed things. I am wondering what >> others have done/seen with this and whether upgrading to 4.4.0 would do me >> good. I am thinking it would as many things appear to fixed around the >> issues I am seeing. Thanks in advance, >> >> Mike >> > -- 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/bf2bfefb-7d91-49df-bdb7-c022a8092e96%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] does puppet have api to run and apply catalogs
Hi, I'm evaluating puppet and salt. salt has an api that helps us runs command and apply salt states (like catalogs) on the endpoints. is there any such alternative in puppet, an api that can help apply a catalog or a manifest on the agent via the puppet master. Thanks, Rahav -- 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/89ff4fad-7481-4f71-9a21-e8378f66940d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Compare node fact runs
Do you have a link to those posts Mike? On Thursday, July 6, 2017 at 12:54:37 PM UTC-4, Peter Krawetzky wrote: > > I'm seeing a lot of replace facts in the puppetdb server log. I googled > but can't find anything solid. > > Is there a way to compare facts for a node between runs? Our agents run > hourly. We are using open source PuppetDB 3.0.2. > > 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/ef0caed9-04f1-4977-afe9-deee1fc31db7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
