similar to: Remote site puppet infrastructure

# cat /etc/redhat-release CentOS release 6.4 (Final) # puppet --version 3.2.3 # rpm -q puppetdb puppetdb-1.3.2-1.el6.noarch I am now receiving "Not collecting exported resources without storeconfigs" for my opsview module. It was working fine on puppet 2.7 with Activerecord/MySQL. I am still new to puppetdb so maybe I am missing something. This is from puppet.conf: storeconfigs

All- Poking around in the bug database it looks like storeconfigs is being actively worked on. I am using 2.7.6 on my master as well as all the clients. I have clients boot , start puppet and get a signed cert via auto signing. The nagios module (and currently the only thing puppet does) complains a lot during compile time about not having storeconfigs enabled, which is not the case in my

Hi all, I currently am using puppet with storeconfigs and am quite happy with the results. I also see that there is now the option of having async_storeconfigs. What I''m wondering about is the following: 1. What benefit is there to running async_storeconfigs over storeconfigs? 2. In what scenario''s would async provide a benefit to standard storeconfigs? 3. What are the typical

Hello All, I don''t seem to be able to get reports to display on the foreman interface. I copied extras/puppet/foreman/files/foreman-report.rb to / usr/lib/ruby/site_ruby/1.8/puppet/reportsforeman.rb, instead of /usr/ lib/ruby/1.8/puppet/reports/foreman.rb. Config: Centos5.4, Apache/ Passenger, Puppet 0.25.4. The reports are coming from the clients, because I can see them in

I updated some of my gems, and I think it may be the reason I am getting the following error when the agents try to retrieve a catalog. err: Could not retrieve catalog from remote server: Error 400 on SERVER: The single-table inheritance mechanism failed to locate the subclass: ''Host::Managed''. This error is raised because the column ''type'' is reserved for

Hi, When I run puppet agent --test --environment 42A, I have the following warning : Warning: Local environment: "42A" doesn''t match server specified node environment "production", switching agent to "production". ... The puppet manifest for the environment "42A" isn''t applied. The puppet version is 3.3.1-1puppetlabs1 on agent and

Hello All, So I finally got around to start to cut over node definitions from standard flat files to external nodes (foreman), and getting error message: "Error 400 on SERVER: Could not find node ''nodename''; cannot compile" - So basically it can''t pick up the node from the external node config. When I test the fetching of the yaml file it seems to work

I''ve been trying to find information, suggestions, etc. for how to combine scaling Puppet with the use of management tools like Dashboard/Foreman and MCollective. Our current thinking for an initial deployment is two VMs as Puppet Master worker nodes fronted by a pair of NetScalers. However, I''m not sure how to go about implementing Dashboard or Foreman and MCollective servers in

Hello! I try to use foreman. It''s successfuly import current nodes from puppet storeconfig. Nodes hostname stored in short form, without domain. After that, i run puppet on newly created additional 5 nodes. They shows in foreman with full fqdn. Os, environment, architecture for this nodes not shown. How can i fix this issue? -- You received this message because you are subscribed to

Hi all, As I understand it, storeconfigs needs to be enabled on both the agent and the master to function ideally. I have a couple of questions: -> Can the various agents and the master safely share the same storeconfigs db (say, a postgresql server)? Is there any benefit to setting things up this way? -> Is there any benefit for an _agent_ to use an RDBMS vs sqlite for its

Hello All, I''m happy to announce the next stable release of Foreman, main new features include: - Integration of Puppet Reports, once enabled you would see a real time overview of all of yours hosts status. - Improved support for multiple Puppet Masters (e.g. import facts and reports from remote serves over http) - Simplified migration from existing external nodes setup,

PuppetDB, a component of the Puppet Data Library, is a centralized storage daemon for auto-generated data. This initial release of PuppetDB targets the storage of catalogs and facts: * It’s a drop-in, 100% compatible replacement for storeconfigs * It’s a drop-in, 100% compatible replacement for inventory service * It hooks into your Puppet infrastructure using Puppet’s pre-existing

I''m doing some testing with the puppetlabs/haproxy module on a vagrant box with puppet 3 set up. The module we use requires exported resources to be enabled in order to specify haproxy backends, but I don''t have it configured in puppet. I have our puppet repo checked out to the VM and am using puppet apply, pointed at the specific module path we use for development, to

Dear All, I know puppetDB its more faster than storeconfigs, but to replace storeconfigs with puppetDB into production server Its need more explanation than some link from puppetlabs, need prove to my bos and team. For testing i just have 1 puppetmaster and 1 and 2 puppet agent, how i can look different performance? Its that any idea / or complex puppet stanza to benchmark / compare this with

Hi all, hoping someone may have encountered a problem similar to this before: On my customer''s EC2 based infrastructure, we have implemented the nodeless, truth driven module outlined by Jordan Sissel here http://www.semicomplete.com/blog/geekery/puppet-nodeless-configuration. It''s quite an effective model, especially in the realm of EC2... we still have a puppetmaster

Hello, I have configured puppet and puppetdb (storeconfig) with postgresql and the service run and the collecting are good for example: I can make query with the next command and responds ok . [.........................] [root@master]# curl -X GET -H ''Accept: application/json'' http://127.0.0.1:8080/v2/facts --data-urlencode ''query=["=", "name",

I have a working configuration using external nodes, but when I enable storeconfigs using either Sqlite or MySQL, nodes no longer get assigned their classes from the external nodes script. I''m currently using the 0.25.4-2ubuntu6 packages from Ubuntu 10.4. Disabling storeconfigs and restarting puppetmaster causes nodes to be assigned classes from the external nodes script. I''ve

I am attempting to remove an old ssh host key from /etc/ssh/ssh_known_hosts. In my manifest, I have the following: # add keys @@sshkey { $hostname: ensure => present, type => "rsa", key => $sshrsakey, } # remove key @@sshkey { "foohost": ensure => absent, type => "rsa", } Sshkey <<| |>> But I get this error on

Hi all, I''m using the version 0.24.1 with strange problem: When I enable storeconfigs in puppetmaster (puppet.conf) I have the following error on clients debug: Finishing transaction -604715208 with 0 changes info: Loading fact hardware_platform info: Loading fact dmi debug: Retrieved facts in 2.12 seconds debug: Calling puppetmaster.freshness *err: Could not retrieve configuration:

I''m re-posting this because I''m not sure that it got through the first time. If someone could at least echo back that this is reaching the list, I''d appreciate it. (I''m new to the list.) Sometimes (with variable frequency) storeconfigs stores the wrong data in the fact_values table. This has the end result that exported resources, when collected, have