Re: [Puppet Users] dependencies

[Patrick]

How is that different from the example you're quoting?  Can't you just put 
whatever's in that as a global dependency for Package?

On Mar 17, 2010, at 4:35 PM, Christopher Johnston wrote:

> I guess my only gripe here is I have about 2 dozen modules most of install 
> some form of a pkg from yum.  So they all have a direct dependency on my yum 
> module to do the right thing.  I would hate to have to put a require in every 
> single instance that I call the method to install a pkg.  Any ideas on on how 
> to simplify this to ensure yum is the very first thing that gets configured 
> on my system?
> 
>require => [ Class["yum"],
> 
> On Tue, Mar 9, 2010 at 5:51 PM, Patrick  wrote:
> 
> On Mar 9, 2010, at 5:26 AM, Christopher Johnston wrote:
> 
> > For example I have a yum module that sets yum configs up, but obviously I 
> > have other modules that depend on the installation of that yum module in 
> > order to use it to install rpms.
> 
> I do the same thing with apt.  To solve this, I set the files that need to be 
> set at the global dependency for all packages.  Here's an example.
> 
> Package { require => Exec["post-proxy-update"] }
> 
>file { "/etc/apt/apt.conf.d/01proxy":
>owner   => root,
>group   => root,
>mode=> 644,
>source  => "puppet:///aptcacher-client/01proxy",
>}
> 
>exec { "/usr/bin/apt-get update":
>alias   => "post-proxy-update",
>subscribe   => [ File["/etc/apt/apt.conf.d/01proxy"], 
> File["/etc/apt/sources.list.d/simba.list"] ],
>require => [ File["/etc/apt/apt.conf.d/01proxy"], 
> File["/etc/apt/sources.list.d/simba.list"] ],
>refreshonly => true,
>}
> 
>file { "/etc/apt/sources.list.d/simba.list":
>owner   => root,
>group   => root,
>mode=> 644,
>source  => "puppet:///local-apt/simba.list",
>}
> 
> --
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@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-us...@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-us...@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] preseed/late_command

[Ohad Levy]

Hi Derek,

This is how its done in Foreman:

this is the preseed template:
http://theforeman.org/repositories/entry/foreman/app/views/unattended/preseed.rhtml

and this is the is the late command:
http://theforeman.org/repositories/entry/foreman/app/views/unattended/preseed_finish.rhtml

hope this helps,
Ohad

On Thu, Mar 18, 2010 at 9:39 AM, Derek Yarnell wrote:

> Hi,
>
> Anyone running puppetd --test in their preseed late_command?  I can't seem
> to get it working as the installer hangs forever in the late_preseed stage.
>
> This is what I am using,
>
> d-i preseed/late_command string chroot /target; mount /proc;
> /usr/sbin/puppetd --test --server puppetserver.my.domain
>
> If I run this in a virtual console it seems to work fine. Anyone doing this
> or have they gone another way?
>
> Thanks,
> derek
>
> --
> --
> Derek Yarnell
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@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-us...@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] preseed/late_command

[Derek Yarnell]

Hi,

Anyone running puppetd --test in their preseed late_command?  I can't 
seem to get it working as the installer hangs forever in the 
late_preseed stage.


This is what I am using,

d-i preseed/late_command string chroot /target; mount /proc; 
/usr/sbin/puppetd --test --server puppetserver.my.domain


If I run this in a virtual console it seems to work fine. Anyone doing 
this or have they gone another way?


Thanks,
derek

--
--
Derek Yarnell

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-us...@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] dependencies

[Christopher Johnston]

The only potential solution I see right now is to put the require in a  
define (which i have) that will do a require check on the class.  I  
would expect this would add some extensive overhead on ever package run.


Sent from my iPhone

On Mar 17, 2010, at 9:09 PM, Ashley Penney  wrote:

Put in a feature question for global dependencies like I hassle  
people about from time to time!  We really do need them for setting  
some site specific stuff.


On Wed, Mar 17, 2010 at 7:35 PM, Christopher Johnston > wrote:
I guess my only gripe here is I have about 2 dozen modules most of  
install some form of a pkg from yum.  So they all have a direct  
dependency on my yum module to do the right thing.  I would hate to  
have to put a require in every single instance that I call the  
method to install a pkg.  Any ideas on on how to simplify this to  
ensure yum is the very first thing that gets configured on my system?


   require => [ Class["yum"],

On Tue, Mar 9, 2010 at 5:51 PM, Patrick  wrote:

On Mar 9, 2010, at 5:26 AM, Christopher Johnston wrote:

> For example I have a yum module that sets yum configs up, but  
obviously I have other modules that depend on the installation of  
that yum module in order to use it to install rpms.


I do the same thing with apt.  To solve this, I set the files that  
need to be set at the global dependency for all packages.  Here's an  
example.


Package { require => Exec["post-proxy-update"] }

   file { "/etc/apt/apt.conf.d/01proxy":
   owner   => root,
   group   => root,
   mode=> 644,
   source  => "puppet:///aptcacher-client/01proxy",
   }

   exec { "/usr/bin/apt-get update":
   alias   => "post-proxy-update",
   subscribe   => [ File["/etc/apt/apt.conf.d/01proxy"], File["/ 
etc/apt/sources.list.d/simba.list"] ],
   require => [ File["/etc/apt/apt.conf.d/01proxy"], File["/ 
etc/apt/sources.list.d/simba.list"] ],

   refreshonly => true,
   }

   file { "/etc/apt/sources.list.d/simba.list":
   owner   => root,
   group   => root,
   mode=> 644,
   source  => "puppet:///local-apt/simba.list",
   }

--
You received this message because you are subscribed to the Google  
Groups "Puppet Users" group.

To post to this group, send email to puppet-us...@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-us...@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-us...@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-us...@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] dependencies

[Ashley Penney]

Put in a feature question for global dependencies like I hassle people about
from time to time!  We really do need them for setting some site specific
stuff.

On Wed, Mar 17, 2010 at 7:35 PM, Christopher Johnston wrote:

> I guess my only gripe here is I have about 2 dozen modules most of install
> some form of a pkg from yum.  So they all have a direct dependency on my yum
> module to do the right thing.  I would hate to have to put a require in
> every single instance that I call the method to install a pkg.  Any ideas on
> on how to simplify this to ensure yum is the very first thing that gets
> configured on my system?
>
>require => [ Class["yum"],
>
> On Tue, Mar 9, 2010 at 5:51 PM, Patrick  wrote:
>
>>
>> On Mar 9, 2010, at 5:26 AM, Christopher Johnston wrote:
>>
>> > For example I have a yum module that sets yum configs up, but obviously
>> I have other modules that depend on the installation of that yum module in
>> order to use it to install rpms.
>>
>> I do the same thing with apt.  To solve this, I set the files that need to
>> be set at the global dependency for all packages.  Here's an example.
>>
>> Package { require => Exec["post-proxy-update"] }
>>
>>file { "/etc/apt/apt.conf.d/01proxy":
>>owner   => root,
>>group   => root,
>>mode=> 644,
>>source  => "puppet:///aptcacher-client/01proxy",
>>}
>>
>>exec { "/usr/bin/apt-get update":
>>alias   => "post-proxy-update",
>>subscribe   => [ File["/etc/apt/apt.conf.d/01proxy"],
>> File["/etc/apt/sources.list.d/simba.list"] ],
>>require => [ File["/etc/apt/apt.conf.d/01proxy"],
>> File["/etc/apt/sources.list.d/simba.list"] ],
>>refreshonly => true,
>>}
>>
>>file { "/etc/apt/sources.list.d/simba.list":
>>owner   => root,
>>group   => root,
>>mode=> 644,
>>source  => "puppet:///local-apt/simba.list",
>> }
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To post to this group, send email to puppet-us...@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-us...@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-us...@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] Puppet Client using wrong environment.

[Rob McBroom]

How is the environment determined when you don’t specify one? On my systems, it 
seems that the `--environment` option is completely ignored. I imagine this is 
because the external information (from LDAP in my case) always takes precedence.

-- 
Rob McBroom


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Puppet Client using wrong environment.

[Tony G.]

Hi,

I exposed few days ago this situation on the IRC, but unfortunately I
haven't found a way to solve it yet.

I run the Puppet Master with multiple environments, and everything is
working good but a couple of nodes that are causing me some troubles.

These nodes are pointing to my production environment and I need to point
them back to development to grab some changes I made.

I usually follow these steps on the clients once I've tested in my own
environment:
1. Stop puppet daemon.
2. Test the new config pointing to development environment.
3. Run puppetd pointing to development.
4. Verify change.
5. Start Puppet.

This is a test I did with a similar node:

Testing pointing to *development*:

[app03 ~]# /usr/sbin/puppetd --test -vt --*environment*=*development*
--snip--
notice: Finished catalog run in 30.42 seconds
[app03 ~]# grep -m2 -P "/development/|/production/"
/var/lib/puppet/localconfig.yaml
  file: /opt/puppet/*development*/site.pp
file: /opt/puppet/*development*/modules/ntp/manifests/init.pp

 Testing now pointing to *production*:

[app03 ~]# /usr/sbin/puppetd --test -vt --*environment*=*production*
--snip--
notice: Finished catalog run in 30.55 seconds
[eapp03 ~]# grep -m2 -P "/development/|/production/"
/var/lib/puppet/localconfig.yaml
  file: /opt/puppet/*production*/site.pp
file: /opt/puppet/*production*/classes/puppet.pp


When doing the same on the node I see the strange behavior this is what I
get:

[app01 ~]# /usr/sbin/puppetd --test -vt --environment=*development*
--snip--
[app01 ~]# grep -m2 -P "/development/|/production/"
/var/lib/puppet/localconfig.yaml
file: /opt/puppet/*production*/classes/yumrepos.pp
file: /opt/puppet/*production*/classes/yumrepos.pp

I've tried:

   - Removing the cache in the server
   ($vardir/yaml/{node,facts}/app01.example.com.yaml) and puppetca --clean
   app01.example.com
   - Restarted the server(using passenger).
   - Removed the client $vardir/*
   - Reinstalled puppet client.

All of them with the *same result.*

The nodes with these issues are being hosted with a third party hosting
company, don't think there is any relationship with this as communications
are made between the client/server, but seems like I can't find any other.

Any suggestion is appreciated,  Thanks for reading this.

This is what I use:

PuppetMaster 0.24.8
Puppetclients 0.24.8
passenger (2.2.4)

puppet.conf:
---snippet---
environments = production,testing,development
manifest = /opt/puppet/production/site.pp
modulepath = /opt/puppet/production/modules

[production]
manifest = /opt/puppet/production/site.pp
modulepath = /opt/puppet/production/modules

[testing]
manifest = /opt/puppet/testing/site.pp
modulepath = /opt/puppet/testing/modules

[development]
manifest = /opt/puppet/development/site.pp
modulepath = /opt/puppet/development/modules

---snippet---


-- 
Tony

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] dependencies

[Christopher Johnston]

I guess my only gripe here is I have about 2 dozen modules most of install
some form of a pkg from yum.  So they all have a direct dependency on my yum
module to do the right thing.  I would hate to have to put a require in
every single instance that I call the method to install a pkg.  Any ideas on
on how to simplify this to ensure yum is the very first thing that gets
configured on my system?

   require => [ Class["yum"],

On Tue, Mar 9, 2010 at 5:51 PM, Patrick  wrote:

>
> On Mar 9, 2010, at 5:26 AM, Christopher Johnston wrote:
>
> > For example I have a yum module that sets yum configs up, but obviously I
> have other modules that depend on the installation of that yum module in
> order to use it to install rpms.
>
> I do the same thing with apt.  To solve this, I set the files that need to
> be set at the global dependency for all packages.  Here's an example.
>
> Package { require => Exec["post-proxy-update"] }
>
>file { "/etc/apt/apt.conf.d/01proxy":
>owner   => root,
>group   => root,
>mode=> 644,
>source  => "puppet:///aptcacher-client/01proxy",
>}
>
>exec { "/usr/bin/apt-get update":
>alias   => "post-proxy-update",
>subscribe   => [ File["/etc/apt/apt.conf.d/01proxy"],
> File["/etc/apt/sources.list.d/simba.list"] ],
>require => [ File["/etc/apt/apt.conf.d/01proxy"],
> File["/etc/apt/sources.list.d/simba.list"] ],
>refreshonly => true,
>}
>
>file { "/etc/apt/sources.list.d/simba.list":
>owner   => root,
>group   => root,
>mode=> 644,
>source  => "puppet:///local-apt/simba.list",
> }
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@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-us...@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] passenger errors

[Christopher Johnston]

Hmm I have rack installed, perhaps a broken RPM in the fedora repos.  I
upgraded to the latest 1.1.0 (via gem install rack).  Is there a version
requirement perhaps?

rubygem-rack-0.4.0-2.fc10.noarch


On Wed, Mar 17, 2010 at 4:21 PM, Ben Lovell wrote:

> On 17 March 2010 19:50, Christopher Johnston  wrote:
>
>> Hmmm I have all the goodies installed, rubygem-rails, rubygem-passenger,
>> mod_passenger, etc.  It looks like mod_passenger seems to be working
>> correctly (passenger-status reports good and I can see processes running).
>>  Sorry for my ignorance ruby and passenger is new to me, but I thought
>> mod_rails was passenger.
>>
>> # cat mod_passenger.conf
>>
>> LoadModule passenger_module modules/mod_passenger.so
>> PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5
>> PassengerRuby /usr/bin/ruby
>>
>> # find /usr -name mod_passenger.so
>> /usr/lib64/httpd/modules/mod_passenger.so
>>
>>
>
> You're missing the rack gem somehow.
>
> `gem install rack`
>
> And all will be well.
>
> Cheers,
> Ben
>
>
>>
>> On Wed, Mar 17, 2010 at 12:20 PM, Nigel Kersten wrote:
>>
>>> On Wed, Mar 17, 2010 at 9:16 AM, Christopher Johnston
>>>  wrote:
>>> > Has anyone seen this come up, I am using 0.24.8 version of puppet.  I
>>> > followed the directions on the wiki and installed passenger correctly
>>> from
>>> > what I can tell.
>>> >
>>> >
>>> > [Wed Mar 17 09:07:56 2010] [notice] Apache/2.2.14 (Unix) DAV/2
>>> > Phusion_Passenger/2.2.5 mod_python/3.3.1 Python/2.5.2 mod_ssl/2.2.14
>>> > OpenSSL/0.9.8g mod_perl/2.0.4 Perl/v5.10.0 configured -- resuming
>>> normal
>>> > operations
>>> > /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>>> > `gem_original_require': no such file to load -- rack (LoadError)
>>>
>>> It's not finding the rack install.
>>>
>>>
>>>
>>> > from
>>> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>>> > `require'
>>> > from
>>> >
>>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:26
>>> > from
>>> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>>> > `gem_original_require'
>>> > from
>>> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>>> > `require'
>>> > from
>>> >
>>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:157:in
>>> > `spawn_application'
>>> > from
>>> >
>>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:287:in
>>> > `handle_spawn_application'
>>> > from
>>> >
>>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
>>> > `__send__'
>>> > from
>>> >
>>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
>>> > `main_loop'
>>> > from
>>> >
>>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:196:in
>>> > `start_synchronously'
>>> > from
>>> >
>>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server:61
>>> > /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>>> > `gem_original_require': no such file to load -- rack (LoadError)
>>> > from
>>> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>>> > `require'
>>> > from
>>> >
>>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:26
>>> > from
>>> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>>> > `gem_original_require'
>>> > from
>>> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>>> > `require'
>>> > from
>>> >
>>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:157:in
>>> > `spawn_application'
>>> > from
>>> >
>>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:287:in
>>> > `handle_spawn_application'
>>> > from
>>> >
>>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
>>> > `__send__'
>>> > from
>>> >
>>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
>>> > `main_loop'
>>> > from
>>> >
>>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:196:in
>>> > `start_synchronously'
>>> > from
>>> >
>>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server:61
>>> > [ pid=5466 file=ext/apache2/Hooks.cpp:725 time=2010-03-17 09:08:30.832
>>> ]:
>>> >   Unexpected error in mod_passenger: Cannot spawn application
>>> > '/usr/share/puppet/rack/puppetmasterd': The spawn server has exited
>>> > unexpectedly.
>>> >   Backtrace:
>>> >  in 'virtual boost::shared_ptr
>>> > Passenger::ApplicationPoolServer::Client::get(const
>>> > Passenger::PoolOptions&)' (ApplicationPoolServer.h:471)
>>> >  in 'int Hooks::handleRequest(request_rec*)' (Hooks.cpp:521)
>>> > /usr/lib/ruby/site_ruby/1.8/rubygems

Re: [Puppet Users] Rio puppet meetup?

[Michael DeHaan]

On Wed, Mar 17, 2010 at 4:29 PM, Martin Englund  wrote:
> Oi Gente!
>
> I'm going to be in Rio (de Janeiro) in a couple of months and would
> love to have a good puppet talk if anyone is interested...
>
> cheers,
> /Martin

Can it be on the scale of "Rock in Rio" and have a DVD release?  :)

--Michael

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Rio puppet meetup?

[Martin Englund]

Oi Gente!

I'm going to be in Rio (de Janeiro) in a couple of months and would
love to have a good puppet talk if anyone is interested...

cheers,
/Martin

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] passenger errors

[Ben Lovell]

On 17 March 2010 19:50, Christopher Johnston  wrote:

> Hmmm I have all the goodies installed, rubygem-rails, rubygem-passenger,
> mod_passenger, etc.  It looks like mod_passenger seems to be working
> correctly (passenger-status reports good and I can see processes running).
>  Sorry for my ignorance ruby and passenger is new to me, but I thought
> mod_rails was passenger.
>
> # cat mod_passenger.conf
>
> LoadModule passenger_module modules/mod_passenger.so
> PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5
> PassengerRuby /usr/bin/ruby
>
> # find /usr -name mod_passenger.so
> /usr/lib64/httpd/modules/mod_passenger.so
>
>

You're missing the rack gem somehow.

`gem install rack`

And all will be well.

Cheers,
Ben


>
> On Wed, Mar 17, 2010 at 12:20 PM, Nigel Kersten  wrote:
>
>> On Wed, Mar 17, 2010 at 9:16 AM, Christopher Johnston
>>  wrote:
>> > Has anyone seen this come up, I am using 0.24.8 version of puppet.  I
>> > followed the directions on the wiki and installed passenger correctly
>> from
>> > what I can tell.
>> >
>> >
>> > [Wed Mar 17 09:07:56 2010] [notice] Apache/2.2.14 (Unix) DAV/2
>> > Phusion_Passenger/2.2.5 mod_python/3.3.1 Python/2.5.2 mod_ssl/2.2.14
>> > OpenSSL/0.9.8g mod_perl/2.0.4 Perl/v5.10.0 configured -- resuming normal
>> > operations
>> > /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>> > `gem_original_require': no such file to load -- rack (LoadError)
>>
>> It's not finding the rack install.
>>
>>
>>
>> > from
>> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>> > `require'
>> > from
>> >
>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:26
>> > from
>> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>> > `gem_original_require'
>> > from
>> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>> > `require'
>> > from
>> >
>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:157:in
>> > `spawn_application'
>> > from
>> >
>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:287:in
>> > `handle_spawn_application'
>> > from
>> >
>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
>> > `__send__'
>> > from
>> >
>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
>> > `main_loop'
>> > from
>> >
>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:196:in
>> > `start_synchronously'
>> > from
>> >
>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server:61
>> > /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>> > `gem_original_require': no such file to load -- rack (LoadError)
>> > from
>> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>> > `require'
>> > from
>> >
>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:26
>> > from
>> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>> > `gem_original_require'
>> > from
>> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>> > `require'
>> > from
>> >
>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:157:in
>> > `spawn_application'
>> > from
>> >
>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:287:in
>> > `handle_spawn_application'
>> > from
>> >
>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
>> > `__send__'
>> > from
>> >
>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
>> > `main_loop'
>> > from
>> >
>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:196:in
>> > `start_synchronously'
>> > from
>> >
>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server:61
>> > [ pid=5466 file=ext/apache2/Hooks.cpp:725 time=2010-03-17 09:08:30.832
>> ]:
>> >   Unexpected error in mod_passenger: Cannot spawn application
>> > '/usr/share/puppet/rack/puppetmasterd': The spawn server has exited
>> > unexpectedly.
>> >   Backtrace:
>> >  in 'virtual boost::shared_ptr
>> > Passenger::ApplicationPoolServer::Client::get(const
>> > Passenger::PoolOptions&)' (ApplicationPoolServer.h:471)
>> >  in 'int Hooks::handleRequest(request_rec*)' (Hooks.cpp:521)
>> > /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>> > `gem_original_require': no such file to load -- rack (LoadError)
>> > from
>> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>> > `require'
>> > from
>> >
>> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:26
>> > from
>> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in

Re: [Puppet Users] passenger errors

[Christopher Johnston]

Hmmm I have all the goodies installed, rubygem-rails, rubygem-passenger,
mod_passenger, etc.  It looks like mod_passenger seems to be working
correctly (passenger-status reports good and I can see processes running).
 Sorry for my ignorance ruby and passenger is new to me, but I thought
mod_rails was passenger.

# cat mod_passenger.conf

LoadModule passenger_module modules/mod_passenger.so
PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5
PassengerRuby /usr/bin/ruby

# find /usr -name mod_passenger.so
/usr/lib64/httpd/modules/mod_passenger.so





On Wed, Mar 17, 2010 at 12:20 PM, Nigel Kersten  wrote:

> On Wed, Mar 17, 2010 at 9:16 AM, Christopher Johnston
>  wrote:
> > Has anyone seen this come up, I am using 0.24.8 version of puppet.  I
> > followed the directions on the wiki and installed passenger correctly
> from
> > what I can tell.
> >
> >
> > [Wed Mar 17 09:07:56 2010] [notice] Apache/2.2.14 (Unix) DAV/2
> > Phusion_Passenger/2.2.5 mod_python/3.3.1 Python/2.5.2 mod_ssl/2.2.14
> > OpenSSL/0.9.8g mod_perl/2.0.4 Perl/v5.10.0 configured -- resuming normal
> > operations
> > /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> > `gem_original_require': no such file to load -- rack (LoadError)
>
> It's not finding the rack install.
>
>
>
> > from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> > `require'
> > from
> >
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:26
> > from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> > `gem_original_require'
> > from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> > `require'
> > from
> >
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:157:in
> > `spawn_application'
> > from
> >
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:287:in
> > `handle_spawn_application'
> > from
> >
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
> > `__send__'
> > from
> >
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
> > `main_loop'
> > from
> >
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:196:in
> > `start_synchronously'
> > from
> > /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server:61
> > /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> > `gem_original_require': no such file to load -- rack (LoadError)
> > from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> > `require'
> > from
> >
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:26
> > from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> > `gem_original_require'
> > from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> > `require'
> > from
> >
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:157:in
> > `spawn_application'
> > from
> >
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:287:in
> > `handle_spawn_application'
> > from
> >
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
> > `__send__'
> > from
> >
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
> > `main_loop'
> > from
> >
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:196:in
> > `start_synchronously'
> > from
> > /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server:61
> > [ pid=5466 file=ext/apache2/Hooks.cpp:725 time=2010-03-17 09:08:30.832 ]:
> >   Unexpected error in mod_passenger: Cannot spawn application
> > '/usr/share/puppet/rack/puppetmasterd': The spawn server has exited
> > unexpectedly.
> >   Backtrace:
> >  in 'virtual boost::shared_ptr
> > Passenger::ApplicationPoolServer::Client::get(const
> > Passenger::PoolOptions&)' (ApplicationPoolServer.h:471)
> >  in 'int Hooks::handleRequest(request_rec*)' (Hooks.cpp:521)
> > /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> > `gem_original_require': no such file to load -- rack (LoadError)
> > from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> > `require'
> > from
> >
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:26
> > from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> > `gem_original_require'
> > from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> > `require'
> > from
> >
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:157:in
> > `spawn_application'
> > from
> >
> /usr/lib/ruby/gems/1.8/gems/passe

Re: [Puppet-dev] Re: [Puppet Users] Using Puppet for application deployment

[Luke Kanies]

On Mar 16, 2010, at 4:07 AM, David Schmitt wrote:


[crossposting to puppet-dev, please trim follow-ups appropriately]

On 3/16/2010 11:52 AM, Jesús Couto wrote:



On Mon, Mar 15, 2010 at 3:18 PM, Michael DeHaan
mailto:mich...@reductivelabs.com>> wrote:

> that are very much procedural while Puppet manifest are more
> useful on a description of required software level.

   Sort of.

   The long story is that we don't have a really native feeling way  
to

   model multinode deployments and workflow now, but we can think of
   modeling it based on a set of checkpoint conditions.


On a complete pipe-dream, "I'm not the one with the skills to do  
this"
comment, I think it would be great to extend the Puppet language  
toward

"site" configurations. As exported resources, but more. If you could
define, say, an "application" resource that is not on a node but on
several nodes, that would model the application - this app is this  
and

this running on those 2 servers who are on loadbalancing and this and
that on those other 2, and the parts on the webservers requires the
parts on the appservers that requires the parts on the database
servers...dont know at what level could it be modeled to be flexible
enough and not one size "deploy" model for all, but the idea would  
be to
make it like Puppet goes from "let me script this" to "let me  
describe
how it should be", with you describing your application  
structucture and

relationships and such.




If you want to prototype something like this, you can use a define  
outside of a node in the site.pp and use checks against $fqdn to  
distribute resources among hosts.


Maybe even use the external_resource type that's currently floating  
around to sequence the deployment.



Which leads me to another idea: inter-node dependencies:

| node a { mysql_db { "foo": ... } }
|
| node b { app { "x": after => A>>Mysql_db["foo"]; } }


The external resource stuff does just about exactly this, except that  
it's not a special syntax.  It's not as manageable as I'd like --  
there's no way, for instance, to really understand the dependencies  
between hosts without reading all of the code -- but it's a good start  
and should help us set the model.


--
Seize opportunity by the beard, for it is bald behind.
-- Bulgarian Proverb
-
Luke Kanies  -|-   http://reductivelabs.com   -|-   +1(615)594-8199

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-us...@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] Using Puppet for application deployment

[Luke Kanies]

On Mar 11, 2010, at 12:53 PM, Julian Simpson wrote:

> They're two distinct areas of 'deployment'. Puppet is more like,  
systems

> deployment, cap is app or content deployment in my eyes.

Yes, I want to change that observation.


I use Puppet for deploying my blog.  It's a WordPress distro with a  
bunch of plugins, etc.  It was too slow.  I ended up inelegantly  
using rsync from puppet to push out the distro instead, which was  
insanely fast.  Even that didn't come for free as I'm not using a  
Puppetmaster at the moment, and paths got annoying.  (I do accept  
that's probably my issue, however).


Anyway, my point is that Puppet needs to give you a way to deploy a  
tree of files, fast.  If the new type mentioned above starts to give  
you that, so much the better: it gets tedious to push files to your  
version control system, ensure that your puppetmaster is up to date,  
and then invoke puppet on the node that you're deploying to.


What's appealing about some developer-style deploy tools is that you  
can push exactly what you're working on to one or more nodes and  
test it.  My experiences with Puppet suggest that it's not so  
convenient.  My 6 years as a build and release manager tell me that  
it's generally a poor idea to use two application deployment tools.   
Hmmm.



I essentially agree on both sides:  Puppet isn't yet that great at  
solving this problem, but using two tools sucks.


We're basically still in the formative stage of what we're going to do  
here, but we've got some pretty good ideas.  Mostly, it builds around  
a much more powerful data model in the catalog, combined with a  
centralized system that tracks inter-node dependencies.


Keeping in mind that this is all still a bit vague:

We'll be extending the data model to support service state  
dependencies and simple state machines, along with (probably) some  
kind of fill-in-the-value (which Markus insists on calling 'futures')  
catalog.  This, I think, gets us most of the way to what we need on a  
single machine:


If you have two services, where one service specifies that it being in  
a 'running' state requires that the other service must also be in a  
'running' state, when you got to restart the required service then the  
requiring service can automatically be brought down first.


If you have a single composite service (e.g., a "web app" composed of  
a db and apache), then you could have a specification that defines how  
it should behave depending on whether it should be running or not, and  
then external data that defines which value you want in a given case.


Once we start tracking resource collection as a dependency (because  
one host's configuration is now dependent on another's), plus a  
centralized database containing all compiled catalogs, we've basically  
got builtin node-order dependencies, all emergent rather than  
declared.  You could get dependencies through declaration, I think,  
but it doesn't scale as well.


The 'external_resource' module I sent in last week[1] is a good  
example of what the first bit will look like, but it has a lot of  
"here be dragons" associated with it.  To make it supportable in the  
long term, you need to add builtin interfaces for checking service  
state (probably with central correlation rather than direct  
connectivity) plus the inter-node dependency system needs to recognize  
this as a dependency.


Obviously, this is 80% theory, 15% plan, and 5% bs, but we do have  
ideas for how it'll work, and we're making baby steps toward getting  
some of it actually done.


In the meantime, I'd appreciate any results from people testing this  
external resource stuff.


1 - http://github.com/reductivelabs/puppet-external-resource

--
The Internet, of course, is more than just a place to find pictures of
people having sex with dogs. -- Time Magazine, 3 July 1995
-
Luke Kanies  -|-   http://reductivelabs.com   -|-   +1(615)594-8199

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-us...@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: Require a definition

[Mike]

Makes sense now. Got confused with definitions for some reason.
Thanks again.

On Mar 17, 9:32 am, David Schmitt  wrote:
> On 3/17/2010 3:56 PM, Mike wrote:
>
> > Thanks. That was what I was missing.  So apparently you need to "call"
> > a definition before you can require it.
>
> Almost. The proper wording of that statement would be: "You need to
> *manage* a *resource*, before you can require it."
>
> Regards, David
> --
> dasz.at OG              Tel: +43 (0)664 2602670     Web:http://dasz.at
> Klosterneuburg                                         UID: ATU64260999
>
>         FB-Nr.: FN 309285 g          FB-Gericht: LG Korneuburg

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Using Puppet for application deployment

[Luke Kanies]

On Mar 9, 2010, at 9:54 AM, Joe McDonagh wrote:


Michael DeHaan wrote:
On Mon, Mar 8, 2010 at 9:46 AM, Julian Simpson > wrote:


Given that there are so many ways to skin the same cat, I'm  
wondering
how others are doing their application deployments using Puppet.  
Or,

if you are using Puppet but do your app deployments via some other
mechanism, how do you do it, and why aren't you using Puppet to  
do it?


Pete




I use capistrano for application deployment.

I've managed to use both Puppet and Capistrano for deployment: Cap  
for the
business code, and Puppet to ensure that dependencies are met.   
Puppet was

called from Capistrano.
J.





Can you share some examples of where your dividing line is and some  
of

the tasks that are hard to handle in Puppet today?

Ideally I'd like to figure out how to incorporate more of that into
puppet-core.Bruce has been working on a version control type,  
that

could be used to check sources
out of version control and eliminate some packaging needs for hosted
apps, though I'm curious as to what other niches might not be  
covered.


--Michael



Example of what puppet can do best:

Configure a system with apache2, a basic security configuration,  
some enabled modules, a bunch of packages admins expect to have  
available (screen, irb, etc).


Example of what capistrano can do best:

A. Deploy your puppet manifests to your puppet server.
B. Deploy your web content out of svn onto your web server.

They're two distinct areas of 'deployment'. Puppet is more like,  
systems deployment, cap is app or content deployment in my eyes.



I would essentially agree with that, with one caveat - that's  
something Puppet's not very good at today, but I'm willing to make  
some bets (not promises, quite yet) about it being good at it within a  
year or so.


--
Fallacies do not cease to be fallacies because they become fashions.
--G. K. Chesterton
-
Luke Kanies  -|-   http://reductivelabs.com   -|-   +1(615)594-8199

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-us...@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] passenger errors

[Nigel Kersten]

On Wed, Mar 17, 2010 at 9:16 AM, Christopher Johnston
 wrote:
> Has anyone seen this come up, I am using 0.24.8 version of puppet.  I
> followed the directions on the wiki and installed passenger correctly from
> what I can tell.
>
>
> [Wed Mar 17 09:07:56 2010] [notice] Apache/2.2.14 (Unix) DAV/2
> Phusion_Passenger/2.2.5 mod_python/3.3.1 Python/2.5.2 mod_ssl/2.2.14
> OpenSSL/0.9.8g mod_perl/2.0.4 Perl/v5.10.0 configured -- resuming normal
> operations
> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `gem_original_require': no such file to load -- rack (LoadError)

It's not finding the rack install.



>         from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `require'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:26
>         from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `gem_original_require'
>         from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `require'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:157:in
> `spawn_application'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:287:in
> `handle_spawn_application'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
> `__send__'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
> `main_loop'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:196:in
> `start_synchronously'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server:61
> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `gem_original_require': no such file to load -- rack (LoadError)
>         from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `require'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:26
>         from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `gem_original_require'
>         from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `require'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:157:in
> `spawn_application'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:287:in
> `handle_spawn_application'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
> `__send__'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
> `main_loop'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:196:in
> `start_synchronously'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server:61
> [ pid=5466 file=ext/apache2/Hooks.cpp:725 time=2010-03-17 09:08:30.832 ]:
>   Unexpected error in mod_passenger: Cannot spawn application
> '/usr/share/puppet/rack/puppetmasterd': The spawn server has exited
> unexpectedly.
>   Backtrace:
>      in 'virtual boost::shared_ptr
> Passenger::ApplicationPoolServer::Client::get(const
> Passenger::PoolOptions&)' (ApplicationPoolServer.h:471)
>      in 'int Hooks::handleRequest(request_rec*)' (Hooks.cpp:521)
> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `gem_original_require': no such file to load -- rack (LoadError)
>         from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `require'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:26
>         from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `gem_original_require'
>         from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `require'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:157:in
> `spawn_application'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:287:in
> `handle_spawn_application'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
> `__send__'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
> `main_loop'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:196:in
> `start_synchronously'
>         from
> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server:61
> [ pid=5467 file=ext/apache2/Hooks.cpp:725 time=2010-03-17 09:08:30.959 ]:
>   Unexpected error in mod_passenger: Cannot spawn application
> '/usr/share/puppet/rack/puppetmasterd': The spawn server has exited
> unexpectedly.
>   Backtrace:
>      in 'virtual boost::shared_ptr
> 

[Puppet Users] passenger errors

[Christopher Johnston]

Has anyone seen this come up, I am using 0.24.8 version of puppet.  I
followed the directions on the wiki and installed passenger correctly from
what I can tell.



[Wed Mar 17 09:07:56 2010] [notice] Apache/2.2.14 (Unix) DAV/2
Phusion_Passenger/2.2.5 mod_python/3.3.1 Python/2.5.2 mod_ssl/2.2.14
OpenSSL/0.9.8g mod_perl/2.0.4 Perl/v5.10.0 configured -- resuming normal
operations
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require': no such file to load -- rack (LoadError)
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:26
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:157:in
`spawn_application'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:287:in
`handle_spawn_application'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
`__send__'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
`main_loop'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:196:in
`start_synchronously'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server:61
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require': no such file to load -- rack (LoadError)
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:26
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:157:in
`spawn_application'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:287:in
`handle_spawn_application'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
`__send__'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
`main_loop'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:196:in
`start_synchronously'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server:61
[ pid=5466 file=ext/apache2/Hooks.cpp:725 time=2010-03-17 09:08:30.832 ]:
  Unexpected error in mod_passenger: Cannot spawn application
'/usr/share/puppet/rack/puppetmasterd': The spawn server has exited
unexpectedly.
  Backtrace:
 in 'virtual boost::shared_ptr
Passenger::ApplicationPoolServer::Client::get(const
Passenger::PoolOptions&)' (ApplicationPoolServer.h:471)
 in 'int Hooks::handleRequest(request_rec*)' (Hooks.cpp:521)

/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require': no such file to load -- rack (LoadError)
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:26
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:157:in
`spawn_application'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:287:in
`handle_spawn_application'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
`__send__'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
`main_loop'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:196:in
`start_synchronously'
from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server:61
[ pid=5467 file=ext/apache2/Hooks.cpp:725 time=2010-03-17 09:08:30.959 ]:
  Unexpected error in mod_passenger: Cannot spawn application
'/usr/share/puppet/rack/puppetmasterd': The spawn server has exited
unexpectedly.
  Backtrace:
 in 'virtual boost::shared_ptr
Passenger::ApplicationPoolServer::Client::get(const
Passenger::PoolOptions&)' (ApplicationPoolServer.h:471)
 in 'int Hooks::handleRequest(request_rec*)' (Hooks.cpp:521)

/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require': no such file to load -- rack (LoadError)
f

Re: [Puppet Users] Choosing the web server

[Jeff McCune]

On Wed, Mar 17, 2010 at 11:39 AM, Nigel Kersten  wrote:
> When you have multiple mongrel backends with pound/nginx/apache in
> front of them, you're managing multiple processes and services, which
> I find annoying.

Exactly this reason for me too.  In addition, I really like the
simplicity of setting PassengerMaxRequests to something reasonable
which restarts the puppetmaster process for me on a periodic basis.

-Jeff

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Choosing the web server

[Christopher Johnston]

I just installed passenger from his repo, clean install thus far.

On Wed, Mar 17, 2010 at 11:42 AM, Todd Zullinger  wrote:

> Christopher Johnston wrote:
> > http://www.kanarip.com/custom/
> >
> > Someone pointed me to this repo the other day, havn't tested
> > anything in or know who is maintaining it though.
>
> Those packages are done by Jeroen van Meeuwen, the same fellow who's
> trying to get passenger into Fedora and EPEL.  Some might recognize
> the name from checking the Fedora/EPEL puppet package changelog too.
> He's the current maintainer for the puppet packages (which I help
> co-maintain). :)
>
> --
> ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
> ~~
> Even if you're on the right track, you'll get run over if you just sit
> there.
>-- Will Rogers
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Choosing the web server

[Todd Zullinger]

Christopher Johnston wrote:
> http://www.kanarip.com/custom/
>
> Someone pointed me to this repo the other day, havn't tested
> anything in or know who is maintaining it though.

Those packages are done by Jeroen van Meeuwen, the same fellow who's
trying to get passenger into Fedora and EPEL.  Some might recognize
the name from checking the Fedora/EPEL puppet package changelog too.
He's the current maintainer for the puppet packages (which I help
co-maintain). :)

-- 
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Even if you're on the right track, you'll get run over if you just sit
there.
-- Will Rogers



pgp2IsPcVbmQM.pgp
Description: PGP signature

Re: [Puppet Users] Choosing the web server

[Nigel Kersten]

On Wed, Mar 17, 2010 at 8:37 AM, Christopher Johnston
 wrote:
> Am I missing something with mongrel though?  It seemed straighfwd to me just
> a custom httpd.conf you add the puppetmaster ports you want it to proxy too
> and make sure the puppetmasters have the ports.
> Or is it they passenger is more flexible?

When you're running with Passenger, to start/stop the service you're
simply stopping/starting Apache.

When you have multiple mongrel backends with pound/nginx/apache in
front of them, you're managing multiple processes and services, which
I find annoying.


>
> On Wed, Mar 17, 2010 at 11:34 AM, Jeff McCune  wrote:
>>
>> Having used Webrick, Mongrel+(pound/nginx/apache) and Passenger+Apache
>> all in production on 100+ hosts, I definitely recommend passenger.
>> It's much easier to manage once it's up and running.
>>
>> On Wed, Mar 17, 2010 at 11:30 AM, Christopher Johnston
>>  wrote:
>> > http://www.kanarip.com/custom/
>> > Someone pointed me to this repo the other day, havn't tested anything in
>> > or
>> > know who is maintaining it though.
>> >
>> > On Wed, Mar 17, 2010 at 10:03 AM, Todd Zullinger  wrote:
>> >>
>> >> Michael DeHaan wrote:
>> >> > I'd like to push this through to Fedora review so we can get it built
>> >> > for EPEL (at least RHEL 5) and be available via yum.
>> >>
>> >> Passenger has been in the Fedora/EPEL review queue for a long time --
>> >> like a year and a half.  It's held up due to bundled libraries (a
>> >> similar theme among Rails folks, unfortunately).
>> >>
>> >> https://bugzilla.redhat.com/show_bug.cgi?id=470696
>> >>
>> >> --
>> >> Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
>> >> ~~
>> >> As long as people will accept crap, it will be financially profitable
>> >> to dispense it.
>> >>    -- Dick Cavett, in "Playboy", 1971
>> >>
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "Puppet Users" group.
>> > To post to this group, send email to puppet-us...@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-us...@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-us...@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.
>



-- 
nigel

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Choosing the web server

[Christopher Johnston]

Am I missing something with mongrel though?  It seemed straighfwd to me just
a custom httpd.conf you add the puppetmaster ports you want it to proxy too
and make sure the puppetmasters have the ports.

Or is it they passenger is more flexible?

On Wed, Mar 17, 2010 at 11:34 AM, Jeff McCune  wrote:

> Having used Webrick, Mongrel+(pound/nginx/apache) and Passenger+Apache
> all in production on 100+ hosts, I definitely recommend passenger.
> It's much easier to manage once it's up and running.
>
> On Wed, Mar 17, 2010 at 11:30 AM, Christopher Johnston
>  wrote:
> > http://www.kanarip.com/custom/
> > Someone pointed me to this repo the other day, havn't tested anything in
> or
> > know who is maintaining it though.
> >
> > On Wed, Mar 17, 2010 at 10:03 AM, Todd Zullinger  wrote:
> >>
> >> Michael DeHaan wrote:
> >> > I'd like to push this through to Fedora review so we can get it built
> >> > for EPEL (at least RHEL 5) and be available via yum.
> >>
> >> Passenger has been in the Fedora/EPEL review queue for a long time --
> >> like a year and a half.  It's held up due to bundled libraries (a
> >> similar theme among Rails folks, unfortunately).
> >>
> >> https://bugzilla.redhat.com/show_bug.cgi?id=470696
> >>
> >> --
> >> ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
> >> ~~
> >> As long as people will accept crap, it will be financially profitable
> >> to dispense it.
> >>-- Dick Cavett, in "Playboy", 1971
> >>
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Puppet Users" group.
> > To post to this group, send email to puppet-us...@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-us...@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-us...@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] Choosing the web server

[Jeff McCune]

Having used Webrick, Mongrel+(pound/nginx/apache) and Passenger+Apache
all in production on 100+ hosts, I definitely recommend passenger.
It's much easier to manage once it's up and running.

On Wed, Mar 17, 2010 at 11:30 AM, Christopher Johnston
 wrote:
> http://www.kanarip.com/custom/
> Someone pointed me to this repo the other day, havn't tested anything in or
> know who is maintaining it though.
>
> On Wed, Mar 17, 2010 at 10:03 AM, Todd Zullinger  wrote:
>>
>> Michael DeHaan wrote:
>> > I'd like to push this through to Fedora review so we can get it built
>> > for EPEL (at least RHEL 5) and be available via yum.
>>
>> Passenger has been in the Fedora/EPEL review queue for a long time --
>> like a year and a half.  It's held up due to bundled libraries (a
>> similar theme among Rails folks, unfortunately).
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=470696
>>
>> --
>> Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
>> ~~
>> As long as people will accept crap, it will be financially profitable
>> to dispense it.
>>    -- Dick Cavett, in "Playboy", 1971
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@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-us...@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] Re: Require a definition

[David Schmitt]

On 3/17/2010 3:56 PM, Mike wrote:

Thanks. That was what I was missing.  So apparently you need to "call"
a definition before you can require it.


Almost. The proper wording of that statement would be: "You need to 
*manage* a *resource*, before you can require it."



Regards, David
--
dasz.at OG  Tel: +43 (0)664 2602670 Web: http://dasz.at
Klosterneuburg UID: ATU64260999

   FB-Nr.: FN 309285 g  FB-Gericht: LG Korneuburg

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-us...@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] Re: config_version in template?

[Jeff McCune]

On Wed, Mar 17, 2010 at 5:17 AM, Daniel Kerwin  wrote:
> I want add the content of puppet.conf's variable config_version to a
> template. Currently I use a generate statement and it would be great
> to get rid of the duplicate code

You could search through through the source and see what object
instance is being used by the logging system then see if that instance
is in scope when your templates are compiled, but this doesn't sound
like a very clean or robust solution to me.

-Jeff

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Choosing the web server

[Christopher Johnston]

http://www.kanarip.com/custom/

Someone pointed me to this repo the other day, havn't tested anything in or
know who is maintaining it though.

On Wed, Mar 17, 2010 at 10:03 AM, Todd Zullinger  wrote:

> Michael DeHaan wrote:
> > I'd like to push this through to Fedora review so we can get it built
> > for EPEL (at least RHEL 5) and be available via yum.
>
> Passenger has been in the Fedora/EPEL review queue for a long time --
> like a year and a half.  It's held up due to bundled libraries (a
> similar theme among Rails folks, unfortunately).
>
> https://bugzilla.redhat.com/show_bug.cgi?id=470696
>
> --
> ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
> ~~
> As long as people will accept crap, it will be financially profitable
> to dispense it.
>-- Dick Cavett, in "Playboy", 1971
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Custom Provider with multiple default targets

[Jeff McCune]

On Wed, Mar 17, 2010 at 9:15 AM, Paul Seymour  wrote:
> If I have a custom provider which updates a file. How can I get it to write 
> to 2 files at the same time without coding 2 things within the manifest one 
> with target => and one without ?

Paul, I think you may receive a better response if you post this
question to the puppet-dev mailing list.

-Jeff

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Re: Package Providers for OD X Server

[Nigel Kersten]

On Wed, Mar 17, 2010 at 3:01 AM, donavan  wrote:
> At work we have three puppetmasters running on OSX 10.5. I hate to say
> it, but it came down to custom packages. We're using encap to deploy
> across 3 different OSs for all the site common bits.
>
> Other than the packaging the other bits of apple sauce to tackle were
> service management & bizzaro configs. We also have plenty of exec{}s
> to serveradmin, which I havent gotten back to. augeas should help
> tackle the misc configs.


How are you running the puppetmasters Donovan? Passenger?

I'd like us to have a nice simple install for people wanting to run
the server on OS X. I have a script around somewhere that will create
a Passenger pkg from the source tarball, and that seemed to work fine
with the built in Apache.

I'm not doing much OS X Server these days, but I wonder if there's any
hope of getting a decent serveradmin type together for OS X Server
management

>
> --
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@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.
>
>



-- 
nigel

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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: Require a definition

[Mike]

Thanks. That was what I was missing.  So apparently you need to "call"
a definition before you can require it.

On Mar 17, 4:57 am, David Schmitt  wrote:
> On 3/17/2010 12:59 AM, Mike wrote:
>
>
>
>
>
> > I am looking for a way to create a dependency that ensures that a
> > definition has been "called/executed/instantiated" with the "require"
> > or "before" parameter.
> > I realize there are several posts that confirm that this should be
> > possible:
>
> > define testdef {
> > }
>
> > file { "testFile":
> >        name =>  "/tmp/testFile",
> >        require =>  Testdef["test"]
> > }
>
> > However when I attempt to run it I get this:
> > err: Could not run Puppet configuration client: Could not find
> > dependency Testmodule::Testdef[test] for File[testFile] at /etc/puppet/
> > modules/testmodule/manifests/init.pp:33
>
> The error should vanish as soon as you add this:
>
>       testdef { "test: }
>
> Regards, David
> --
> dasz.at OG              Tel: +43 (0)664 2602670     Web:http://dasz.at
> Klosterneuburg                                         UID: ATU64260999
>
>         FB-Nr.: FN 309285 g          FB-Gericht: LG Korneuburg

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Choosing the web server

[Michael DeHaan]

On Wed, Mar 17, 2010 at 10:03 AM, Todd Zullinger  wrote:
> Michael DeHaan wrote:
>> I'd like to push this through to Fedora review so we can get it built
>> for EPEL (at least RHEL 5) and be available via yum.
>
> Passenger has been in the Fedora/EPEL review queue for a long time --
> like a year and a half.  It's held up due to bundled libraries (a
> similar theme among Rails folks, unfortunately).
>
> https://bugzilla.redhat.com/show_bug.cgi?id=470696

I see they forked a C++ library.   Yeah I agree with Toshio there,
that's dangerous.

On a semi-related note, I know it's new and so forth, but has anyone
tried unicorn?

http://github.com/blog/517-unicorn
http://labs.revelationglobal.com/2009/10/06/mongrel_passenger_unicorn.html

--Michael

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Choosing the web server

[Todd Zullinger]

Michael DeHaan wrote:
> I'd like to push this through to Fedora review so we can get it built
> for EPEL (at least RHEL 5) and be available via yum.

Passenger has been in the Fedora/EPEL review queue for a long time --
like a year and a half.  It's held up due to bundled libraries (a
similar theme among Rails folks, unfortunately).

https://bugzilla.redhat.com/show_bug.cgi?id=470696

-- 
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
As long as people will accept crap, it will be financially profitable
to dispense it.
-- Dick Cavett, in "Playboy", 1971



pgp5RsSIAjw0R.pgp
Description: PGP signature

Re: [Puppet Users] Choosing the web server

[Michael DeHaan]

> if anyone is looking for RPMS, I've created one for passenger (RHE5).
>


Sorry, missed this earlier.

Excellent.   Can you give me the URL to the source RPM, specfile, and tarball?

I'd like to push this through to Fedora review so we can get it built
for EPEL (at least RHEL 5) and be available via yum.

Getting that approved should also help with CentOS Extras, I'd imagine.

--Michael

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Choosing the web server

[Michael DeHaan]

On Wed, Mar 17, 2010 at 9:14 AM, Christopher Johnston
 wrote:
> Mongrel was very easy to setup as the packages are all available in Fedora.

The solution here seems to help packaging for Fedora (and EPEL, if
possible) along.

Has anyone attempted packaging it previously?

--Michael

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Choosing the web server

[Ohad Levy]

while i had monit babysitting mongrel, I've switched to passenger too.

the 2-5% performance lost (according to my own benchmarks) is acceptable
comparing the complexity of the setup.

if anyone is looking for RPMS, I've created one for passenger (RHE5).

my 2 cents,
Ohad

On Wed, Mar 17, 2010 at 9:38 PM, Nigel Kersten  wrote:

> On Wed, Mar 17, 2010 at 6:34 AM, Trevor Vaughan 
> wrote:
> > Passenger should be about 30% faster and has built-in memory
> > management via mod-rack.
> >
> > This is a huge plus if you have a lot of nodes or limited memory.
> >
> > Also, you stop having problems with Apache getting out of sync with
> > the puppetmaster if you restart the puppetmaster processes without
> > also restarting Apache.
>
> ++ I found it incredibly difficult to write robust babysitter
> processes for anything + multiple mongrels.
>
> It's much simpler to manage apache with passenger.
>
>
> >
> > Trevor
> >
> > On Wed, Mar 17, 2010 at 9:14 AM, Christopher Johnston
> >  wrote:
> >> Mongrel was very easy to setup as the packages are all available in
> Fedora.
> >>  I was able to fire up a puppetmaster on most of the cpu cores I have on
> my
> >> system to scale the load out a bit more. I have yet to try passenger.
>  But I
> >> think more importantly what is the "fastest" and most "scalable"
> solution.
> >>  I have heard/read that Mongrel (and older ruby) have had memory leaks,
> but
> >> not sure if thats still true today on current versions.
> >> -Chris
> >>
> >> On Wed, Mar 17, 2010 at 9:06 AM, Michael DeHaan <
> mich...@reductivelabs.com>
> >> wrote:
> >>>
> >>> On Tue, Mar 16, 2010 at 2:00 AM, Smain Kahlouch 
> >>> wrote:
> >>> > Hi everybody,
> >>> >
> >>> > I just want to know what is the best web server between passenger and
> >>> > mongrel.
> >>> > I don't understand what are the benefits of each solution.
> >>> >
> >>> > Do you have a part of the answer please?
> >>>
> >>> We seem to be directing folks to passenger if they are running a new
> >>> enough Puppet in the docs, yet this seems to conflict:
> >>>
> >>>
> http://www.mail-archive.com/puppet-users@googlegroups.com/msg04745.html
> >>>  (any updates on this?)
> >>>
> >>> I agree with the need to choose one performant "default suggestion"
> >>> and not leave someone with the task of evaluating/testing lots of
> >>> options.
> >>>
> >>> --Michael
> >>>
> >>> --
> >>> You received this message because you are subscribed to the Google
> Groups
> >>> "Puppet Users" group.
> >>> To post to this group, send email to puppet-us...@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-us...@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.
> >>
> >
> >
> >
> > --
> > Trevor Vaughan
> > Vice President, Onyx Point, Inc
> > (410) 541-6699
> > tvaug...@onyxpoint.com
> >
> > -- This account not approved for unencrypted proprietary information --
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> > To post to this group, send email to puppet-us...@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.
> >
> >
>
>
>
> --
> nigel
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@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-us...@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] Choosing the web server

[Nigel Kersten]

On Wed, Mar 17, 2010 at 6:34 AM, Trevor Vaughan  wrote:
> Passenger should be about 30% faster and has built-in memory
> management via mod-rack.
>
> This is a huge plus if you have a lot of nodes or limited memory.
>
> Also, you stop having problems with Apache getting out of sync with
> the puppetmaster if you restart the puppetmaster processes without
> also restarting Apache.

++ I found it incredibly difficult to write robust babysitter
processes for anything + multiple mongrels.

It's much simpler to manage apache with passenger.


>
> Trevor
>
> On Wed, Mar 17, 2010 at 9:14 AM, Christopher Johnston
>  wrote:
>> Mongrel was very easy to setup as the packages are all available in Fedora.
>>  I was able to fire up a puppetmaster on most of the cpu cores I have on my
>> system to scale the load out a bit more. I have yet to try passenger.  But I
>> think more importantly what is the "fastest" and most "scalable" solution.
>>  I have heard/read that Mongrel (and older ruby) have had memory leaks, but
>> not sure if thats still true today on current versions.
>> -Chris
>>
>> On Wed, Mar 17, 2010 at 9:06 AM, Michael DeHaan 
>> wrote:
>>>
>>> On Tue, Mar 16, 2010 at 2:00 AM, Smain Kahlouch 
>>> wrote:
>>> > Hi everybody,
>>> >
>>> > I just want to know what is the best web server between passenger and
>>> > mongrel.
>>> > I don't understand what are the benefits of each solution.
>>> >
>>> > Do you have a part of the answer please?
>>>
>>> We seem to be directing folks to passenger if they are running a new
>>> enough Puppet in the docs, yet this seems to conflict:
>>>
>>> http://www.mail-archive.com/puppet-users@googlegroups.com/msg04745.html
>>>  (any updates on this?)
>>>
>>> I agree with the need to choose one performant "default suggestion"
>>> and not leave someone with the task of evaluating/testing lots of
>>> options.
>>>
>>> --Michael
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Puppet Users" group.
>>> To post to this group, send email to puppet-us...@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-us...@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.
>>
>
>
>
> --
> Trevor Vaughan
> Vice President, Onyx Point, Inc
> (410) 541-6699
> tvaug...@onyxpoint.com
>
> -- This account not approved for unencrypted proprietary information --
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@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.
>
>



-- 
nigel

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Choosing the web server

[Trevor Vaughan]

Passenger should be about 30% faster and has built-in memory
management via mod-rack.

This is a huge plus if you have a lot of nodes or limited memory.

Also, you stop having problems with Apache getting out of sync with
the puppetmaster if you restart the puppetmaster processes without
also restarting Apache.

Trevor

On Wed, Mar 17, 2010 at 9:14 AM, Christopher Johnston
 wrote:
> Mongrel was very easy to setup as the packages are all available in Fedora.
>  I was able to fire up a puppetmaster on most of the cpu cores I have on my
> system to scale the load out a bit more. I have yet to try passenger.  But I
> think more importantly what is the "fastest" and most "scalable" solution.
>  I have heard/read that Mongrel (and older ruby) have had memory leaks, but
> not sure if thats still true today on current versions.
> -Chris
>
> On Wed, Mar 17, 2010 at 9:06 AM, Michael DeHaan 
> wrote:
>>
>> On Tue, Mar 16, 2010 at 2:00 AM, Smain Kahlouch 
>> wrote:
>> > Hi everybody,
>> >
>> > I just want to know what is the best web server between passenger and
>> > mongrel.
>> > I don't understand what are the benefits of each solution.
>> >
>> > Do you have a part of the answer please?
>>
>> We seem to be directing folks to passenger if they are running a new
>> enough Puppet in the docs, yet this seems to conflict:
>>
>> http://www.mail-archive.com/puppet-users@googlegroups.com/msg04745.html
>>  (any updates on this?)
>>
>> I agree with the need to choose one performant "default suggestion"
>> and not leave someone with the task of evaluating/testing lots of
>> options.
>>
>> --Michael
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To post to this group, send email to puppet-us...@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-us...@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.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvaug...@onyxpoint.com

-- This account not approved for unencrypted proprietary information --

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Custom Provider with multiple default targets

[Paul Seymour]

Hello,

If I have a custom provider which updates a file. How can I get it to write to 
2 files at the same time without coding 2 things within the manifest one with 
target => and one without ?

So multiple targets as the default_target

Cheers
Paul

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Choosing the web server

[Christopher Johnston]

Mongrel was very easy to setup as the packages are all available in Fedora.
 I was able to fire up a puppetmaster on most of the cpu cores I have on my
system to scale the load out a bit more. I have yet to try passenger.  But I
think more importantly what is the "fastest" and most "scalable" solution.
 I have heard/read that Mongrel (and older ruby) have had memory leaks, but
not sure if thats still true today on current versions.

-Chris

On Wed, Mar 17, 2010 at 9:06 AM, Michael DeHaan
wrote:

> On Tue, Mar 16, 2010 at 2:00 AM, Smain Kahlouch 
> wrote:
> > Hi everybody,
> >
> > I just want to know what is the best web server between passenger and
> > mongrel.
> > I don't understand what are the benefits of each solution.
> >
> > Do you have a part of the answer please?
>
> We seem to be directing folks to passenger if they are running a new
> enough Puppet in the docs, yet this seems to conflict:
>
> http://www.mail-archive.com/puppet-users@googlegroups.com/msg04745.html
>  (any updates on this?)
>
> I agree with the need to choose one performant "default suggestion"
> and not leave someone with the task of evaluating/testing lots of
> options.
>
> --Michael
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@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-us...@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] Choosing the web server

[Michael DeHaan]

On Tue, Mar 16, 2010 at 2:00 AM, Smain Kahlouch  wrote:
> Hi everybody,
>
> I just want to know what is the best web server between passenger and
> mongrel.
> I don't understand what are the benefits of each solution.
>
> Do you have a part of the answer please?

We seem to be directing folks to passenger if they are running a new
enough Puppet in the docs, yet this seems to conflict:

http://www.mail-archive.com/puppet-users@googlegroups.com/msg04745.html
 (any updates on this?)

I agree with the need to choose one performant "default suggestion"
and not leave someone with the task of evaluating/testing lots of
options.

--Michael

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Require a definition

[David Schmitt]

On 3/17/2010 12:59 AM, Mike wrote:

I am looking for a way to create a dependency that ensures that a
definition has been "called/executed/instantiated" with the "require"
or "before" parameter.
I realize there are several posts that confirm that this should be
possible:

define testdef {
}

file { "testFile":
   name =>  "/tmp/testFile",
   require =>  Testdef["test"]
}


However when I attempt to run it I get this:
err: Could not run Puppet configuration client: Could not find
dependency Testmodule::Testdef[test] for File[testFile] at /etc/puppet/
modules/testmodule/manifests/init.pp:33



The error should vanish as soon as you add this:

 testdef { "test: }


Regards, David
--
dasz.at OG  Tel: +43 (0)664 2602670 Web: http://dasz.at
Klosterneuburg UID: ATU64260999

   FB-Nr.: FN 309285 g  FB-Gericht: LG Korneuburg

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-us...@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] Require a definition

[Mike]

I am looking for a way to create a dependency that ensures that a
definition has been "called/executed/instantiated" with the "require"
or "before" parameter.
I realize there are several posts that confirm that this should be
possible:

define testdef {
}

file { "testFile":
  name => "/tmp/testFile",
  require => Testdef["test"]
}


However when I attempt to run it I get this:
err: Could not run Puppet configuration client: Could not find
dependency Testmodule::Testdef[test] for File[testFile] at /etc/puppet/
modules/testmodule/manifests/init.pp:33

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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: Package Providers for OD X Server

[donavan]

At work we have three puppetmasters running on OSX 10.5. I hate to say
it, but it came down to custom packages. We're using encap to deploy
across 3 different OSs for all the site common bits.

Other than the packaging the other bits of apple sauce to tackle were
service management & bizzaro configs. We also have plenty of exec{}s
to serveradmin, which I havent gotten back to. augeas should help
tackle the misc configs.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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: config_version in template?

[Daniel Kerwin]

I want add the content of puppet.conf's variable config_version to a
template. Currently I use a generate statement and it would be great
to get rid of the duplicate code



On 3/17/10, Christian Kauhaus  wrote:
> Am 16.03.2010 17:16, schrieb Daniel Kerwin:
>> is it possible to add a system variable like config_version to a template?
>
> I don't understand your question? What do you mean with "system variable"?
> Facts? Manifest variables?
>
> Do you want just to *use* variables in templates? Do you want to set them
> from templates (which would I consider as bad idea)?
>
> Cheers
>
> Christian
>
> --
> Dipl.-Inf. Christian Kauhaus <>< · mail/jabber: k...@gocept.com
> gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
> http://gocept.com · tel +49 345 1229889 11 · fax +49 345 1229889 1
> Zope and Plone consulting and development
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@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.
>
>

-- 
Sent from Google Mail for mobile | mobile.google.com


Cheers,

Daniel

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Using Puppet for application deployment

[David Schmitt]

On 3/16/2010 10:04 PM, Joe McDonagh wrote:

I don't immediately see it in my dev list, but I'll take your word for
it. I am with you on the inter-node dependencies.



Should have better checked. It was here:

  http://groups.google.com/group/puppet-users/msg/1d54d9db85dae153


Regards, David
--
dasz.at OG  Tel: +43 (0)664 2602670 Web: http://dasz.at
Klosterneuburg UID: ATU64260999

   FB-Nr.: FN 309285 g  FB-Gericht: LG Korneuburg

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-us...@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] Apps that are using facter as a library or shell out to facter?

[David Schmitt]

On 3/16/2010 10:15 PM, Michael DeHaan wrote:


Exactly, just add a "ttl-hint: 24" (hours) value to the JSON.


Hmm

I'd saw this as something that would be a property of the fact, rather
than the output of the fact.

That is, I didn't see a need for variable timeouts.

That being said, if we do the "fact.d" for plugins, those scripts will
want to also use this mechanism,
so perhaps those /do/ speak it in JSON.


If the only interface between a fact and facter is the JSON pipe, the 
TTL would have to be part of it. If it is a ruby interface, it'd 
probably be some kind of accessor which too could have a code block 
attached to make fancy calculations.


As alwas in IT (and elsewhere): just becaus you can (make variable 
timeouts) it doesn't mean it's a good idea.




Best regards, David
--
dasz.at OG  Tel: +43 (0)664 2602670 Web: http://dasz.at
Klosterneuburg UID: ATU64260999

   FB-Nr.: FN 309285 g  FB-Gericht: LG Korneuburg

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-us...@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] config_version in template?

[Christian Kauhaus]

Am 16.03.2010 17:16, schrieb Daniel Kerwin:
> is it possible to add a system variable like config_version to a template?

I don't understand your question? What do you mean with "system variable"?
Facts? Manifest variables?

Do you want just to *use* variables in templates? Do you want to set them
from templates (which would I consider as bad idea)?

Cheers

Christian

-- 
Dipl.-Inf. Christian Kauhaus <>< · mail/jabber: k...@gocept.com
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 11 · fax +49 345 1229889 1
Zope and Plone consulting and development

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.