Re: [Puppet Users] PE - installation error
Did you install puppet on that machine before? Bjørge On 03/21/2012 12:24 PM, Surendra Singhi wrote: > Hi, > > I am trying to install puppet enterprise on a fresh Debian Squeeze > machine, but I am getting an error midway with no information on what > went wrong. How do I troubleshoot or look for more debugging > information? > > This is what the screen output for installation is: > > thanks for your help in advance! > > Setting up pe-rubygem-fog (1.0.0e-1puppet2) ... > Setting up pe-cloud-provisioner (1.0.1-puppet1) ... > ## Setting up puppet master... > "/opt/puppet/share/puppet/modules" does not exist, creating. > Installed "puppetlabs-pe_accounts-1.0.2" into directory: pe_accounts > Installed "puppetlabs-pe_mcollective-0.0.39" into directory: > pe_mcollective > Installed "puppetlabs-pe_compliance-0.0.4" into directory: > pe_compliance > Installed "puppetlabs-stdlib-2.1.2" into directory: stdlib > ## Checking the agent certificate name detection... > ## Setting up puppet agent... > > == > > !! ERROR: Cancelling installation > > == > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
RE: [Puppet Users] Plugins and Hiera
Hi all,
I have thought myself of a #4 possibility, which could be defining the
hierarchy as:
- %{hostname}
- groups
- all
And then create a class called data::groups with a big IF/CASE inside:
class data::groups {
if 'green' in $::groups {
$var1 = 'whatever'
}
if 'blue' in $groups {
$var1 = 'happens'
} # and so on.
I would then have to define the $::groups variable somewhere, most likely in
the beginning of the default node, before any other Hiera() function is called.
The problem I have with this is that, when a machine belongs to more than one
group, some variables may be declared more than once, which will break the
compilation of the manifest. That's why I wanted Hiera for (and the
primary/secondary group hierarchy), so that I could do hiera_array() and add
values from all possible groups of machines.
The whole idea of this question is to keep the information of each node in the
minimum possible number of places. It is already awkward to have a "node"
section and a "data" (hiera) section, then having the group membership inside a
ruby script lost inside some module makes me feel bad about it. I would like to
have a reasonable way of managing groups of machines, where every group a
machine belongs to provides (adds) some information to the overall node state.
Adding values from inside the groups the machine belong to (for example,
authorized_keys or firewall rules, something easily done with arrays that can
be stacked with hiera_array()) should be easy.
Thanks!
Pablo
From: puppet-users@googlegroups.com [puppet-users@googlegroups.com] on behalf
of Gary Larizza [g...@puppetlabs.com]
Sent: Saturday, March 24, 2012 12:01 PM
To: puppet-users@googlegroups.com
Subject: Re: [Puppet Users] Plugins and Hiera
On second-thought, #3 would be out of the question if you wanted to use
%{primary_group} as a hierarchy level in Hiera. You will need to either write
a fact to determine the group based on something atomic about the system or do
something at provision time. Do you have this node-to-primary/secondary-group
mapping in a source of truth like a MySQL database? If so, then you could
utilize a Hiera backend to query this source of truth. There are Hiera-mysql
backends that will allow you to read from database tables, so this is also an
option. I would likely lean toward option #1, however.
Hope this helps.
On Sat, Mar 24, 2012 at 3:55 AM, Gary Larizza
mailto:g...@puppetlabs.com>> wrote:
On Fri, Mar 23, 2012 at 3:42 AM, Pablo Fernandez
mailto:pablo.fernan...@cscs.ch>> wrote:
Dear all,
This is a continuation of another thread, but I think the question diverged
enough to create a new one.
I have a hiera hierarchy like this:
:hierarchy:
- %{fqdn}
- %{secundary_group}
- %{primary_group}
- %{productname}
- all
And I need to define the secondary/primary groups as facts, on the nodes. Gary
has suggested me to use plugins, that they will provide the facts before puppet
runs... but I was thinking: for plugins to give facts, taken directly from
within the puppet code, puppet needs to run first, doesn't it?
So, I guess I could create a module and a ruby script:
- mygroups/lib/facter/addgroup.rb
And write some code in Ruby to call Facter.add(:primary_group).
My problem is (besides the fact that I know nothing about Ruby)... how do I
insert the values for primary_group and secondary_group inside that function,
within a simple puppet run?
I would ask how you could classify a node's primary or secondary group based on
looking at? Is there a file on disk that indicates its group? Will you use
its IP address? Hostname? Something like this?
It sounds like you want to use Puppet to place a file on the filesystem
indicating its primary_group, but that you want to Puppet to manage this file
(or you want to manage the data in Puppet itself). You have a number of
options here:
1. Use something atomic about the machine to determine its primary_group. If
you can say 'based on its IP address, it should be in this group' or 'based on
its hostname, it will be in THIS group', then write a fact to determine this
for you. Remember that in your custom fact you can do:
Facter.value(:ipaddress) or Facter.value(:hostname) to get a node's ipaddress
or hostname. This is the better method since it relies on something NOT
provided by Puppet to determine its group. The Facter fact would run before
the Puppet run, determine its group, and then you'd be fine. Most places I
visit do something like this.
2. Do something at provision-time. Do you already have a source of truth that
maps each node to a primary_group? In your kickstart before running Puppet you
could query this source of truth and create a file (to be read by a fact) that
would determine the primary_group.
3. Set it in the %{fqdn} level of the Hiera hierarchy. This is less-optimal
as you would need to create a YAML file for ever
Re: [Puppet Users] Plugins and Hiera
On 03/24/2012 10:58 AM, Fernandez Pablo wrote:
Hi,
That would define $primary_group as a variable, not as a fact. Indeed, what I
want to do is:
:backends: - puppet
:hierarchy: - %{primary_group}
:puppet:
:datasource: data
And that requires primary_group to be a fact.
No, that's not correct. From what I can gather, for your purposes,
primary_group can and should be a _variable_, not a fact. It seems there
is a common misconception that your hierarchy can only be facts or
calling_module/class. You don't even have to use the puppet backend to
get other variables to work.
I've been working with hiera integration into our env and this is the
general pattern I'm using:
https://gist.github.com/2197910
At first I thought I couldn't really use hiera at all as it seemed that
lookup variables were only fact based. That would make it possible for
any compromised puppet agent to alter what facts it sent and scope
around my data. Ouch! (I don't want my agents to be compromised of
course - anyhow I have to design to limit any damage done if it does happen)
Luckily that turned out not to be true and my integration work could
continue with a big smile on my face!
--
http://www.uib.no/personer/Jan.Ivar.Beddari
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] How can I get puppet onto a closed network ?
The EL5 repos on yum.puppetlabs.com should not require epel anymore. If it does, please file a bug. On Thu, Mar 22, 2012 at 5:27 PM, Aaron Grewell wrote: > I would install yum-utils and use reposync on a system with internet access > to create a local repo. Yum.puppetlabs.com has most of what you need, but > you may also need a copy of the epel repo. > > On Mar 22, 2012 4:42 PM, "Peter Bukowinski" wrote: >> >> I'd copy down from the yum.puppetlabs.com site all the packages in the >> products and dependencies repos and set up your own local repos. Point your >> rhel boxes at it and install that way. >> >> The repos would be easier to mirror locally if puppetlabs setup an rsync >> server for them, but right now scraping them with curl/wget or manually >> downloading is your only option. >> >> -- >> Peter >> >> On Mar 22, 2012, at 6:52 PM, BigCod wrote: >> >> > I've a network of RHEL5.3 servers with no internet acess that I'd >> > like to get puppet onto. >> > >> > All I have is the RHEL5.3 DVD media set up as a yum repo. >> > >> > Is there some way I can download puppet and all its dependencies so I >> > can bundle them together and install them on my closed network ? >> > >> > I'm thinking I could install centos on a machine with net access, >> > download and save all the puppet rpms to that ad copy accross to my >> > closed network, is this the correct method ? >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "Puppet Users" group. >> > To post to this group, send email to puppet-users@googlegroups.com. >> > To unsubscribe from this group, send email to >> > puppet-users+unsubscr...@googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/group/puppet-users?hl=en. >> > >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to puppet-users@googlegroups.com. >> To unsubscribe from this group, send email to >> puppet-users+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] How can I get puppet onto a closed network ?
Thanks Mike, it's great to see the improvements that have been made to the repos over the last few months. You guys have clearly been hard at work. On Mar 25, 2012 4:17 PM, "Michael Stahnke" wrote: > The EL5 repos on yum.puppetlabs.com should not require epel anymore. > If it does, please file a bug. > > On Thu, Mar 22, 2012 at 5:27 PM, Aaron Grewell > wrote: > > I would install yum-utils and use reposync on a system with internet > access > > to create a local repo. Yum.puppetlabs.com has most of what you need, > but > > you may also need a copy of the epel repo. > > > > On Mar 22, 2012 4:42 PM, "Peter Bukowinski" wrote: > >> > >> I'd copy down from the yum.puppetlabs.com site all the packages in the > >> products and dependencies repos and set up your own local repos. Point > your > >> rhel boxes at it and install that way. > >> > >> The repos would be easier to mirror locally if puppetlabs setup an rsync > >> server for them, but right now scraping them with curl/wget or manually > >> downloading is your only option. > >> > >> -- > >> Peter > >> > >> On Mar 22, 2012, at 6:52 PM, BigCod wrote: > >> > >> > I've a network of RHEL5.3 servers with no internet acess that I'd > >> > like to get puppet onto. > >> > > >> > All I have is the RHEL5.3 DVD media set up as a yum repo. > >> > > >> > Is there some way I can download puppet and all its dependencies so I > >> > can bundle them together and install them on my closed network ? > >> > > >> > I'm thinking I could install centos on a machine with net access, > >> > download and save all the puppet rpms to that ad copy accross to my > >> > closed network, is this the correct method ? > >> > > >> > -- > >> > You received this message because you are subscribed to the Google > >> > Groups "Puppet Users" group. > >> > To post to this group, send email to puppet-users@googlegroups.com. > >> > To unsubscribe from this group, send email to > >> > puppet-users+unsubscr...@googlegroups.com. > >> > For more options, visit this group at > >> > http://groups.google.com/group/puppet-users?hl=en. > >> > > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups > >> "Puppet Users" group. > >> To post to this group, send email to puppet-users@googlegroups.com. > >> To unsubscribe from this group, send email to > >> puppet-users+unsubscr...@googlegroups.com. > >> For more options, visit this group at > >> http://groups.google.com/group/puppet-users?hl=en. > >> > > -- > > You received this message because you are subscribed to the Google Groups > > "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users+unsubscr...@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/puppet-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] catalog format performance comparison
Hello, Changelog from 0.24.5 mentions a new format, "marshal", being very much faster than the previous default, "yaml". But the current default format is "pson". I can't find any comparison in performance to the other two. Is "pson" the new default because it fairs better than "marshal" ? -- Gabriel Filion -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Windows Puppet msi packages question
Anybody who can tell more about that? Is that the only way to get msi packages work with puppet? https://github.com/puppetlabs/puppet_for_the_win On 23 Mrz., 10:06, Jan Ivar Beddari wrote: > On 03/23/2012 08:24 AM, Jay Ze wrote: > > > Hi, > > > Can anybody here tell me what msi packages can be used with windows > > puppet? > > > Can I somehow create msi packages for puppet on my own? > > Yes, have a look here:https://github.com/puppetlabs/puppet_for_the_win > > You need a Windows box and puppetwinbuilder.zip .. I haven't done this > myself yet, someone else will most likely help out with more info. > > Jan Ivar Beddari > > --http://www.uib.no/personer/Jan.Ivar.Beddari -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Preparing Schema: Installing Dashboard
Error says it all:rack (~> 1.1.0) You have 1.4.1, which I believe is pulled in as a dependency, you need 1.1.0. gem install rack -v 1.1.0 gem uninstall rack -v 1.4.1 On Friday, March 23, 2012 1:49:38 PM UTC-5, Gmoney wrote: > > When I run this command:: > > rake RAILS_ENV=production db:migrate > > I get this error: > > Could not find rack (~> 1.1.0) amongst [actionmailer-3.2.2, > actionpack-3.2.2, activemodel-3.2.2, activerecord-3.2.2, > activeresource-3.2.2, activesupport-3.2.2, arel-3.0.2, builder-3.0.0, > bundler-1.1.2, daemon_controller-1.0.0, erubis-2.7.0, > fastthread-1.0.7, hike-1.2.1, i18n-0.6.0, journey-1.0.3, json-1.6.5, > mail-2.4.4, mime-types-1.18, multi_json-1.1.0, mysql-2.8.1, > passenger-3.0.11, polyglot-0.3.3, rack-1.4.1, rack-cache-1.2, rack- > ssl-1.3.2, rack-test-0.6.1, rails-3.2.2, railties-3.2.2, rake-0.9.2.2, > rdoc-3.12, sprockets-2.1.2, thor-0.14.6, tilt-1.3.3, treetop-1.4.10, > tzinfo-0.3.32] > > I have rack-1.4.1 gem installed. What am I missu=ing here? I am > attemptin gto install on Red hat 6. I installed ruby-enterprise-1.8.7 > from source and pulled the puppet-dashboard-1.2.0 tarball down to my > RH^ server. > > RubyGems Environment: > - RUBYGEMS VERSION: 1.8.15 > - RUBY VERSION: 1.8.7 (2012-02-08 patchlevel 358) [x86_64-linux] > - INSTALLATION DIRECTORY: /opt/ruby-enterprise-1.8.7-2012.02/lib/ > ruby/gems/1.8 > - RUBY EXECUTABLE: /opt/ruby-enterprise-1.8.7-2012.02/bin/ruby > - EXECUTABLE DIRECTORY: /opt/ruby-enterprise-1.8.7-2012.02/bin > - RUBYGEMS PLATFORMS: > - ruby > - x86_64-linux > - GEM PATHS: > - /opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8 > - /root/.gem/ruby/1.8 > - GEM CONFIGURATION: > - :update_sources => true > - :verbose => true > - :benchmark => false > - :backtrace => false > - :bulk_threshold => 1000 > - REMOTE SOURCES: > - http://rubygems.org/ > > Appreciate any help you can provide, thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/-BZ9i63pVf4J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
