Re: [Puppet Users] external node classifier with a back-end

[Jason Antman]

So you're looking to put Puppet data and "other data" for other
applications in ONE database? That doesn't sound terribly safe...

How is this data getting into the database? What types of functionality
do you need? Just something like Dashboard with nodes and groups that
can have params and classes? Inheritance? Exclusions?

If all you want is a database that stores classes/params for nodes, and
uses them on a 1:1 basis, this is a trivial problem and is really just
an issue of writing a tool to get data into the database. The "hard"
part of an ENC is handling things like groups, multiple inheritance,
overrides, exclusions, etc.

I'm still not clear on the functionality and interface that you want for
this, and I'm also unclear on the distinction between what you call
"configuration data", "client data" and "node data".

-Jason

On 12/06/2013 12:59 PM, Stuart Cracraft wrote:
> HI Jason,
>
> No I have no hesitations at all and yes, I would enjoy seeing your
> Postgres code
> and learning from it and can share back.
>
> So the thought here is to have all the configuration data, client
> data, node data, in
> a Postgres database (the one on the Puppet Master) and used downline
> by all the various
> Linux apps which need it, including Puppet.
>
> I take it (hopefully) this is not too unusual and bizarre in the world
> of Puppet.
>
>
> On Thursday, December 5, 2013 4:16:10 AM UTC-8, Jason Antman wrote:
>
> PuppetDB isn't an ENC. PuppetDB does, however, use Postgres
> (unless you use the embedded database, which you shouldn't).
> Puppet Dashboard is an ENC, but ironically, uses MySQL not Postgres.
>
> Stuart,
>
> Starting *another* ENC thread a day later isn't likely to get you
> many more responses than the two to your last question. I assumed,
> given your lack of response to my reply, that you're not terribly
> interested in sharing what you need an ENC to do... As I
> mentioned, I'm working on getting a Python/Django
> (Postgres-backed) ENC ready for release... if you want to see the
> current code, that could be arranged, though it's not really up to
> the "just run this puppet module and it installs the ENC" stage yet.
>
> -jantman
>
> On 12/04/2013 05:10 PM, Stuart Cracraft wrote:
>> Hi Ygor/Dan,
>>
>> Postgres has better DR.
>>
>> We like Postgres.
>>
>> Stuart
>>
>> On Wednesday, December 4, 2013 2:03:10 PM UTC-8, Ygor wrote:
>>
>> Isn't that what PuppetDB is ?
>>
>> �Sometimes I think the surest sign that intelligent life
>> exists elsewhere in the universe is that none of it has tried
>> to contact us.�
>> Bill Waterson (Calvin & Hobbes)
>>
>> 
>> 
>> *From: *"Stuart Cracraft" 
>> *To: *puppet...@googlegroups.com
>> *Sent: *Wednesday, December 4, 2013 4:33:51 PM
>> *Subject: *[Puppet Users] external node classifier with a
>> back-end
>>
>>
>> Hi everybody!
>>
>> Anyone have a back-ended external node classifier to a
>> Postgres database
>> they could throw my way?
>>
>> Stuart
>>
>>
>> -- 
>> 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 view this discussion on the web visit
>> 
>> https://groups.google.com/d/msgid/puppet-users/7781bed3-7e5a-46e2-8949-e00bfac0fbd0%40googlegroups.com
>> 
>> .
>> 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...@googlegroups.com .
>> To view this discussion on the web visit
>> 
>> https://groups.google.com/d/msgid/puppet-users/c642f1be-1121-4ab9-b56a-29b54809140f%40googlegroups.com
>> 
>> .
>> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/1909c6a8-9dc8-48bf-a397-f975a82749ac%40googlegroups.com.
> For more options, visit https

[Puppet Users] Re: Unpleasant puppetlabs experience

[Fred Lifton]

As a member of the Puppet Labs docs team, I would like to second what Nick 
said. We are a small team with a big backlog and we could not get our jobs 
done if it were not for the engagement and and assiduousness of our users. 
Thanks for your help and your patience.

As we grow the team and move ahead, I'll look forward to getting your 
comments and feedback.

Fred Lifton

On Friday, December 6, 2013 1:24:53 PM UTC-8, Nick Fagerlund wrote:
>
>
>
>  Hi all, I'm the one who closed that ticket. Sorry, my bad.
>
> First off, WE STILL PLAN TO IMPROVE THE TYPE AND PROVIDER DOCS. They can & 
> should & will be better, and we don't consider the O'Reilly "Puppet Types 
> and Providers" book to be an acceptable replacement for free documentation 
> on our website.
>
> That's going to take a big chunk of time, though, and we (the Puppet Labs 
> docs team, hi) will have to schedule it as planned work.
>
> Anyway, here's what happened with that ticket:
>
>
>- We're moving ticketing systems. The new one will be publicly visible 
>at tickets.puppetlabs.com in a matter of days.
>- The docs team is already tracking work in the new system. We are not 
>tracking ANY work in Redmine. The stuff in Redmine is old and out of date.
>- So now I have to do a mass cleanup on the old stuff in Redmine in 
>preparation for the complete switch-over.
>   - Some things I'm fixing now, some things I'm making new tickets 
>   for, some things aren't relevant anymore, and some things are so 
> well-known 
>   in my team that we don't really need a ticket as a reminder; instead, 
> we'll 
>   be hashing them out in our planning sessions once we've dealt with the 
>   stuff we're currently working on (at which point they'll turn into like 
> a 
>   dozen related tickets). "Overhaul the type/provider docs" is in that 
> last 
>   group.
>- I marked some tickets as "rejected" that I should have marked as 
>"closed." (Since we're still planning to do the work, but we aren't 
>tracking it in that Redmine ticket anymore.) Sorry!
>- On some of those, I also made a note or two about related 
>developments that may have changed the relative priority of the issue. (In 
>this case, the fact that there's a good reference *somewhere* out there 
>means we have a small bit of breathing room, even though we still need to 
>improve our version.)
>- I *should* have also pasted in some boilerplate about WHY I was 
>closing 50 tickets at once, and what to do if you were following one of 
>them.
>
>
> So yeah, sorry for implying we weren't going to improve type/provider 
> docs; that's not what I was trying to say at all. Closing that ticket was 
> about housekeeping, not about rejecting the work it represented. There will 
> be a bit of an awkward stage as we switch ticketing systems; sorry about 
> that, and thank you for staying vocal about what needs work.
>
> NF
>
>

-- 
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/20738625-991e-4b8c-ba98-c0c56ebaffc1%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] puppet apply or puppet agent -t fails on razor installation. Need help on razor too.

[Arvind P R]

My puppet master server is working fine and i now installed razor module on 
the same server.

i downloaded the tar.gz from https://forge.puppetlabs.com/puppetlabs/razor and 
did the installation using 

puppet module install  --ignore-dependencies. 
i took care of all the dependencies too.

*My puppet server is behind a corporate authenticated proxy which prevents 
me from using "puppet module install". puppet bug!!*

post razor installation, I included the following lines in 

/etc/puppetlabs/puppet/manifests/site.pp

node puppet_master {
  include razor
}

now if i try to run the following commands:

puppet apply /etc/puppetlabs/puppet/manifests/site.pp
OR
puppet agent -t

on the same server, the commands hang

puppet apply hangs without any message while the following is shown on 
puppet agent -t

[root@centos-razor ~]# puppet agent -t
Info: Retrieving plugin
Info: Loading facts in 
/opt/puppet/share/puppet/modules/stdlib/lib/facter/puppet_vardir.rb
Info: Loading facts in 
/opt/puppet/share/puppet/modules/stdlib/lib/facter/facter_dot_d.rb
Info: Loading facts in 
/opt/puppet/share/puppet/modules/stdlib/lib/facter/root_home.rb
Info: Loading facts in 
/opt/puppet/share/puppet/modules/stdlib/lib/facter/pe_version.rb
Info: Loading facts in 
/opt/puppet/share/puppet/modules/postgresql/lib/facter/postgres_default_version.rb
Info: Loading facts in 
/opt/puppet/share/puppet/modules/concat/lib/facter/concat_basedir.rb
Info: Loading facts in 
/opt/puppet/share/puppet/modules/pe_common/lib/facter/windows.rb
Info: Loading facts in 
/opt/puppet/share/puppet/modules/pe_puppetdb/lib/facter/puppetdb_server_status.rb
Info: Loading facts in 
/opt/puppet/share/puppet/modules/auth_conf/lib/facter/custom_auth_conf.rb
Info: Loading facts in 
/opt/puppet/share/puppet/modules/firewall/lib/facter/ip6tables_version.rb
Info: Loading facts in 
/opt/puppet/share/puppet/modules/firewall/lib/facter/iptables_persistent_version.rb
Info: Loading facts in 
/opt/puppet/share/puppet/modules/firewall/lib/facter/iptables_version.rb
Info: Loading facts in 
/var/opt/lib/pe-puppet/lib/facter/puppetdb_server_status.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/puppet_vardir.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/facter_dot_d.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/windows.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/root_home.rb
Info: Loading facts in 
/var/opt/lib/pe-puppet/lib/facter/postgres_default_version.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/pe_version.rb
Info: Loading facts in 
/var/opt/lib/pe-puppet/lib/facter/ip6tables_version.rb
Info: Loading facts in 
/var/opt/lib/pe-puppet/lib/facter/iptables_persistent_version.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/concat_basedir.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/iptables_version.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/custom_auth_conf.rb
Info: Caching catalog for centos-razor.a100.lab
Info: Applying configuration version '1386442284'

the command does not complete!!

further i am looking for a simple installation guide with centos. i cant 
find one anywhere. most of the blogs and guides are for ubuntu.

what I need to know is the bunch of files and config files I have to keep 
on the tftp server for puppet/razor to work. if anyone can point me to 
that, it would be helpful.

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/9e7b9931-cd55-40d8-9212-77444b5f96e2%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] using mco to manage puppet resources by class

[Jay Christopherson]

Has anyone successfully use the class selectors for the puppet MCollective
plugin?

Something like:

$ mco puppet runonce --tags mysql::master

>From the docs:
*puppet_tags*
*===*

*Validates that a comma seperated list of tags are valid Puppet class names*

*  Author: R.I.Pienaar >*
* Version: 1.0*
* License: ASL 2.0*
* Timeout: 1*
*   Home Page: http://devco.net/ *

*   Puppet tags can be a comma seperated list of valid class names, for
details*
*   about valid class names please see the puppet_variable validator
documentation.*

*   An example of 2 tags would be:*

*   apache,mysql::master*


When I run that command, even though that class is only applied to a single
host, the list it compiles is all 43 of the hosts currently under mco
control:

$ mco puppet runonce --noop --tags mysql::master

 * [ > ] 43 / 43




Finished processing 43 / 43 hosts in 3720.64 ms

I've tried several variations and classes without success.  It always
processes the list of all servers.

-- 
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/CAFwM5Hwyg7_QM4TKWLHsVo-C1oSa4wH%3DF%3DGjcjwA2UKOwOU%2BoA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Provider not using command functions

[Jeff Bachtel]

The gem package provider pretty extensively reads from commands[] and does
its own execute calls instead of using the command functions provided. This
makes it impossible to create a child provider that points to a different
gem command.

Would this be considered a defect worthy of a bugrep, or is the choice to
use command function vice commands array a matter of personal preference?

Jeff

-- 
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/CAHahqg0btg-OLpjh9_426W-741_adhgRjckEVOnjkReSPv3cHQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] testing and exported (nagios) resources

[Jeff Bachtel]

Three thoughts. The first would be to have node definitions for monitor on
both dev and test environments, doing a minimal amount of work to generate
nagios host definitions in a disjoint directory that you include in your
nagios config.

So:
/var/lib/{puppet,puppet-dev,puppet-test}
/etc/{puppet,puppet-dev,puppet-test}
/etc/nagios/object/{dev,test}

To further isolate your nagios box from harm, dev and test environment runs
can be done from an unprivileged user and puppet agent runs can be tied to
host/service additions/removals in dev/test. I know this idea directly
violates you saying "So... setting up all 3 puppet stacks to export
resources that are realized somehow on the Nagios server isn't a
possibility, as bad manifests/modules could affect the monitoring of one of
the dev or test hosts." but it seems the least-harm least-gross way to do
this.

The other way that came to mind was an aperiodic dump/insert of relevant
postgresql tables relating to exported resources from dev/test into the
production postgresql puppetdb. This would require investigating the schema
in use, and cleanup could get tricky.

The third way that came to mind was to use the inventory service
http://docs.puppetlabs.com/guides/inventory_service.html to loop over
hostnames, GET'ing yaml from dev/test and PUT'ing it onto the production
server. I don't know how deletions would be handled, there, or even what
you'd want your failure mode to be.

Jeff



On Mon, Dec 2, 2013 at 8:39 PM, Jason Antman  wrote:

> Hello,
>
> I have 3 puppet stacks (master, puppetdb, enc) - dev, test/qa and prod.
> Dev is used for initial development and testing of code (including
> puppet), which is then promoted to test and then prod.
>
> I'd like to start using the nagios types to configure monitoring, via
> exported resources (yes I'm aware of the issues with the builtins, but
> they'll have to do for now). I only have one Nagios server, and I'd like
> to reliably monitor at least some stuff on the dev and test puppet
> nodes. So... setting up all 3 puppet stacks to export resources that are
> realized somehow on the Nagios server isn't a possibility, as bad
> manifests/modules could affect the monitoring of one of the dev or test
> hosts.
>
> What's the safe way to "freeze" exported resources, or prevent them from
> being changed? The best that I can come up with so far is to have the
> nagios server connected to the production puppetmaster, and when I want
> to update the (exported resource) monitoring configuration for one of
> the dev or test nodes, have to do a one-time run on each node in
> question against the prod puppet master.
>
> Any other thoughts or theories?
>
> Thanks,
> Jason Antman
>
> --
> 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/529D363C.4030202%40jasonantman.com
> .
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAHahqg0BadZAtitdE75A0QLqT7VDU5U_2mm5yHCWNxurwEVSxw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] The error we caught said '407 "authenticationrequired"' during module install behind proxy

[Arvind P R]

I read at a number of places that if my puppet master is behind a proxy 
which requires authentication 

puppet module command does not work

despite setting the global parameters 
http_proxy, https_proxy on bash the command throws an error

[root@centos-razor ~]# puppet module install saz/dnsmasq --force
Notice: Preparing to install into /etc/puppetlabs/puppet/modules ...
Notice: Downloading from https://forge.puppetlabs.com ...
Error: Could not connect to https://forge.puppetlabs.com
  There was a network communications problem
The error we caught said '407 "authenticationrequired"'
Check your network connection and try again


setting the values http_proxy_host and http_proxy_port inside puppet.conf 
doesnt help either, as there is a no way I can set username and password 
there.


Is there a workaround for this?

-- 
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/9b5d67f5-42d2-4a45-88be-cb4c0f49821e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.