[Puppet Users] Re: variable fact lookup

[Ohad Levy]

i think you can use something like "${macaddress}_${eth_name}"

On Sun, Sep 20, 2009 at 12:08 AM, sam  wrote:

>
> hi
>  is it possible to use a variable to name the fact I am after
> eg
>
> define config_net ($eth_name) {
>   $mac = $macaddress_$eth_name
> }
>
>
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Announcement: Foreman 0.1-1 is out

[Ohad Levy]

Hello All,

I'm happy to announce the next stable release of Foreman, main new features
include:

   - Integration of Puppet Reports, once enabled you would see a real time
   overview of all of yours hosts status.
   - Improved support for multiple Puppet Masters (e.g. import facts and
   reports from remote serves over http)
   - Simplified migration from existing external nodes setup, now its
   possible to import your existing classifier data into Foreman.

For a complete change log, please visit:
http://theforeman.org/projects/changelog/foreman
For feature requests, bugs, wiki etc, visit: http://theforeman.org

If you already have Foreman installed, make sure you go through
http://theforeman.org/wiki/foreman/Upgrade_instructions.

Cheers,
Ohad

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: cannot parse template when fact does not exist

[Chris Blumentritt]

On Fri, Sep 18, 2009 at 2:54 AM, David Schmitt  wrote:

>
> Chris Blumentritt wrote:
> > I receive the following error when trying to do the puppet below:
> > Failed to parse template s_apache_site/site.conf.erb: Could not find
> > value for 'ipaddress_eth0_0'
> >
> > As far as I can tell the ipaddress_eth0_0 fact has to exist on the
> > client before it will parse.  I was hoping that I could get the new ip
> > address in place thus creating the fact so that when the apache site is
> > created the information would be available.  Maybe all facts are
> > compiled at the when puppetd is run and there is no way to add facts
> > during the run of puppetd?
>
> puppet sends all facts to the server at the beginning of each run to
> receive an updated configuration. The configuration is compiled
> (functions run, templates expanded) on the server before passing it on
> to the client. The latter only receives a list of resources which it
> dutifully applies.
>
> Therefore it is impossible to "create" facts on the fly: the client
> doesn't have enough information to re-compile its manifests.
>
> This is one of the few cases (enabling providers is another major one)
> where you have to defer some resources until the next run, where you
> have the facts available.
>
> > The way I see around this is to first add the ip address with out
> > calling the apache::site definition and once the ip address gets on
> > there run puppet with apache::site definition.  There has got to be
> > better way, any suggestions
>
> If you really want to avoid the second run, you can refactor your
> manifest so you are not using a fact in you template, but directly the
> configuration information:
>
>
> node web1{
>$secondary_ip = xxx
>
>network::ip { $secondary_ip: }
>apache::site { blah: ip => $secondary_ip }
> }
>

How can I access the $secondary_ip variable from a class?  I have the
app_server class make the same site on more than one server and I do not
think I can more than once in the node.  Besides, defining the same site
more than one time seems bad.


>
>
> Regards, DavidS
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: cannot parse template when fact does not exist

[David Schmitt]

Chris Blumentritt wrote:
> node web1{
>$secondary_ip = xxx
> 
>network::ip { $secondary_ip: }
>apache::site { blah: ip => $secondary_ip }
> }
> 
> 
> How can I access the $secondary_ip variable from a class?  I have the 
> app_server class make the same site on more than one server and I do not 
> think I can more than once in the node.  Besides, defining the same site 
> more than one time seems bad.


The variables propagate through the included classes. That way you can 
use $secodary_ip everywhere.



Regards, DavidS


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: cannot parse template when fact does not exist

[Chris Blumentritt]

On Mon, Sep 21, 2009 at 10:03 AM, David Schmitt  wrote:

>
> Chris Blumentritt wrote:
> > node web1{
> >$secondary_ip = xxx
> >
> >network::ip { $secondary_ip: }
> >apache::site { blah: ip => $secondary_ip }
> > }
> >
> >
> > How can I access the $secondary_ip variable from a class?  I have the
> > app_server class make the same site on more than one server and I do not
> > think I can more than once in the node.  Besides, defining the same site
> > more than one time seems bad.
>
>
> The variables propagate through the included classes. That way you can
> use $secodary_ip everywhere.
>

I thought that would be the case but it does not seem to be working.  I
dropped some notices to print the ip address in the log of the puppet master
and it is not printing anything.  I had to take it a step further where I
set another variable = to the secondary ip address so that I could use the
same erb file for multiple projects.  So I have it looking like this

node "app1" {
  $secondary_ip = "x.x.x.x"
}

class my_project::project_env {
  create_project { $project_fqdn:
name  => $project_name,
project_network_interface => $secondary_ip
  }
}

snip from erb:

:80>

My apache conf ends up with this:








>
>
> Regards, DavidS
>
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: cannot parse template when fact does not exist

[David Schmitt]

Chris Blumentritt wrote:
> 
> 
> On Mon, Sep 21, 2009 at 10:03 AM, David Schmitt  > wrote:
> 
> 
> Chris Blumentritt wrote:
>  > node web1{
>  >$secondary_ip = xxx
>  >
>  >network::ip { $secondary_ip: }
>  >apache::site { blah: ip => $secondary_ip }
>  > }
>  >
>  >
>  > How can I access the $secondary_ip variable from a class?  I have the
>  > app_server class make the same site on more than one server and I
> do not
>  > think I can more than once in the node.  Besides, defining the
> same site
>  > more than one time seems bad.
> 
> 
> The variables propagate through the included classes. That way you can
> use $secodary_ip everywhere.
> 
> 
> I thought that would be the case but it does not seem to be working.  I 
> dropped some notices to print the ip address in the log of the puppet 
> master and it is not printing anything.  I had to take it a step further 
> where I set another variable = to the secondary ip address so that I 
> could use the same erb file for multiple projects.  So I have it looking 
> like this
> 
> node "app1" {
>   $secondary_ip = "x.x.x.x"
> }
> 
> class my_project::project_env {
>   create_project { $project_fqdn:
> name  => $project_name,
> project_network_interface => $secondary_ip
>   }
> }
> 
> snip from erb:
> 
> :80>
> 
> My apache conf ends up with this:
> 
> 


Looks very good, but you also need to include my_project::project_env 
after defining the secondary_ip in the node.


Regards, DavidS

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: cannot parse template when fact does not exist

[David Schmitt]

Chris Blumentritt wrote:
> 
> 
> On Mon, Sep 21, 2009 at 10:03 AM, David Schmitt  > wrote:
> 
> 
> Chris Blumentritt wrote:
>  > node web1{
>  >$secondary_ip = xxx
>  >
>  >network::ip { $secondary_ip: }
>  >apache::site { blah: ip => $secondary_ip }
>  > }
>  >
>  >
>  > How can I access the $secondary_ip variable from a class?  I have the
>  > app_server class make the same site on more than one server and I
> do not
>  > think I can more than once in the node.  Besides, defining the
> same site
>  > more than one time seems bad.
> 
> 
> The variables propagate through the included classes. That way you can
> use $secodary_ip everywhere.
> 
> 
> I thought that would be the case but it does not seem to be working.  I 
> dropped some notices to print the ip address in the log of the puppet 
> master and it is not printing anything.  I had to take it a step further 
> where I set another variable = to the secondary ip address so that I 
> could use the same erb file for multiple projects.  So I have it looking 
> like this
> 
> node "app1" {
>   $secondary_ip = "x.x.x.x"
> }
> 
> class my_project::project_env {
>   create_project { $project_fqdn:
> name  => $project_name,
> project_network_interface => $secondary_ip
>   }
> }
> 
> snip from erb:
> 
> :80>
> 
> My apache conf ends up with this:
> 
> 


Looks very good, but you also need to include my_project::project_env 
after defining the secondary_ip in the node.


Regards, DavidS

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: cannot parse template when fact does not exist

[Chris Blumentritt]

On Mon, Sep 21, 2009 at 11:27 AM, David Schmitt  wrote:

>
> Chris Blumentritt wrote:
> >
> >
> > On Mon, Sep 21, 2009 at 10:03 AM, David Schmitt  > > wrote:
> >
> >
> > Chris Blumentritt wrote:
> >  > node web1{
> >  >$secondary_ip = xxx
> >  >
> >  >network::ip { $secondary_ip: }
> >  >apache::site { blah: ip => $secondary_ip }
> >  > }
> >  >
> >  >
> >  > How can I access the $secondary_ip variable from a class?  I have
> the
> >  > app_server class make the same site on more than one server and I
> > do not
> >  > think I can more than once in the node.  Besides, defining the
> > same site
> >  > more than one time seems bad.
> >
> >
> > The variables propagate through the included classes. That way you
> can
> > use $secodary_ip everywhere.
> >
> >
> > I thought that would be the case but it does not seem to be working.  I
> > dropped some notices to print the ip address in the log of the puppet
> > master and it is not printing anything.  I had to take it a step further
> > where I set another variable = to the secondary ip address so that I
> > could use the same erb file for multiple projects.  So I have it looking
> > like this
> >
> > node "app1" {
> >   $secondary_ip = "x.x.x.x"
> > }
> >
> > class my_project::project_env {
> >   create_project { $project_fqdn:
> > name  => $project_name,
> > project_network_interface => $secondary_ip
> >   }
> > }
> >
> > snip from erb:
> >
> > :80>
> >
> > My apache conf ends up with this:
> >
> > 
>
>
> Looks very good, but you also need to include my_project::project_env
> after defining the secondary_ip in the node.
>
I have a separate class that includes the my_project::project_env for all of
my app servers.  I can verify that it is working since the apache conf file
for site is there.  I have been banging my head on a wall with this one.  I
have been dropping notice functions all over the place to figure out what is
going on.

In my create_project define I have added the following notices:

notice("secondary ip address is ${secondary_ip}")
notice("project network interface is ${project_network_interface}")

and get the following output on the server:

notice: Scope(S_project[my_project-env]): secondary ip address is x.x.x.x
notice: Scope(S_project[my_project-env]): project network interface is

I guess I am running into a scope issue or something.  I have also tried to
move the assignment of project_network_interface in front of the "call" to
the create_project define.

Does the behavior I am seeing make sense?  I don't know what I can do
different.

Chris


>
> Regards, DavidS
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: cannot parse template when fact does not exist

[David Bishop]

On Mon, Sep 21, 2009 at 12:19:39PM -0500, Chris Blumentritt wrote:
>I have a separate class that includes the my_project::project_env for all
>of my app servers. �I can verify that it is working since the apache conf
>file for site is there. �I have been banging my head on a wall with this
>one. �I have been dropping notice functions all over the place to figure
>out what is going on. �
>In my create_project define I have added the following notices:
>notice("secondary ip address is ${secondary_ip}")
>notice("project network interface is ${project_network_interface}")
>and get the following output on the server:
>notice: Scope(S_project[my_project-env]):�secondary ip address is x.x.x.x
>notice: Scope(S_project[my_project-env]):�project network interface is
>I guess I am running into a scope issue or something. �I have also tried
>to move the assignment of�project_network_interface in front of the "call"
>to the create_project define.
>Does the behavior I am seeing make sense? �I don't know what I can do
>different.
>Chris

I'm having a very similar problem.  I have a couple custom facts, set
in a 'custom' module (as per the latest wiki docs), that I use in a
couple different modules (more coming).  However, it doesn't seem to
download the 'custom' module (thus inserting the facts) before the
modules that depend on it.  Commenting out the two templates, letting
puppet run, then uncommenting them works, but is obviously not the
solution.  Without uncommenting them, compiling the template fails, so
compiling the catalog fails, so the custom module is never pushed and
I'm caught in a catch-22...

In short, how do you declare one module dependent on another, to the
extent that the first needs to be "run" first?

David


signature.asc
Description: Digital signature

[Puppet Users] Re: cannot parse template when fact does not exist

[David Bishop]

Never mind. Figured out those clients didn't have the proper  
'pluginsync' lines in puppet.conf.

David Bishop


On Sep 21, 2009, at 1:38 PM, David Bishop   
wrote:

> On Mon, Sep 21, 2009 at 12:19:39PM -0500, Chris Blumentritt wrote:
>>   I have a separate class that includes the my_project::project_env  
>> for all
>>   of my app servers. �I can verify that it is working since the ap 
>> ache conf
>>   file for site is there. �I have been banging my head on a wall w 
>> ith this
>>   one. �I have been dropping notice functions all over the place t 
>> o figure
>>   out what is going on. �
>>   In my create_project define I have added the following notices:
>>   notice("secondary ip address is ${secondary_ip}")
>>   notice("project network interface is ${project_network_interface}")
>>   and get the following output on the server:
>>   notice: Scope(S_project[my_project-env]):�secondary ip address i 
>> s x.x.x.x
>>   notice: Scope(S_project[my_project-env]):�project network interf 
>> ace is
>>   I guess I am running into a scope issue or something. �I have al 
>> so tried
>>   to move the assignment of�project_network_interface in front of  
>> the "call"
>>   to the create_project define.
>>   Does the behavior I am seeing make sense? �I don't know what I c 
>> an do
>>   different.
>>   Chris
>
> I'm having a very similar problem.  I have a couple custom facts, set
> in a 'custom' module (as per the latest wiki docs), that I use in a
> couple different modules (more coming).  However, it doesn't seem to
> download the 'custom' module (thus inserting the facts) before the
> modules that depend on it.  Commenting out the two templates, letting
> puppet run, then uncommenting them works, but is obviously not the
> solution.  Without uncommenting them, compiling the template fails, so
> compiling the catalog fails, so the custom module is never pushed and
> I'm caught in a catch-22...
>
> In short, how do you declare one module dependent on another, to the
> extent that the first needs to be "run" first?
>
> David

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: cannot parse template when fact does not exist

[Chris Blumentritt]

On Mon, Sep 21, 2009 at 12:19 PM, Chris Blumentritt wrote:

>
>
> On Mon, Sep 21, 2009 at 11:27 AM, David Schmitt  wrote:
>
>>
>> Chris Blumentritt wrote:
>> >
>> >
>> > On Mon, Sep 21, 2009 at 10:03 AM, David Schmitt > > > wrote:
>> >
>> >
>> > Chris Blumentritt wrote:
>> >  > node web1{
>> >  >$secondary_ip = xxx
>> >  >
>> >  >network::ip { $secondary_ip: }
>> >  >apache::site { blah: ip => $secondary_ip }
>> >  > }
>> >  >
>> >  >
>> >  > How can I access the $secondary_ip variable from a class?  I have
>> the
>> >  > app_server class make the same site on more than one server and I
>> > do not
>> >  > think I can more than once in the node.  Besides, defining the
>> > same site
>> >  > more than one time seems bad.
>> >
>> >
>> > The variables propagate through the included classes. That way you
>> can
>> > use $secodary_ip everywhere.
>> >
>> >
>> > I thought that would be the case but it does not seem to be working.  I
>> > dropped some notices to print the ip address in the log of the puppet
>> > master and it is not printing anything.  I had to take it a step further
>> > where I set another variable = to the secondary ip address so that I
>> > could use the same erb file for multiple projects.  So I have it looking
>> > like this
>> >
>> > node "app1" {
>> >   $secondary_ip = "x.x.x.x"
>> > }
>> >
>> > class my_project::project_env {
>> >   create_project { $project_fqdn:
>> > name  => $project_name,
>> > project_network_interface => $secondary_ip
>> >   }
>> > }
>> >
>> > snip from erb:
>> >
>> > :80>
>> >
>> > My apache conf ends up with this:
>> >
>> > 
>>
>>
>> Looks very good, but you also need to include my_project::project_env
>> after defining the secondary_ip in the node.
>>
> I have a separate class that includes the my_project::project_env for all
> of my app servers.  I can verify that it is working since the apache conf
> file for site is there.  I have been banging my head on a wall with this
> one.  I have been dropping notice functions all over the place to figure out
> what is going on.
>
> In my create_project define I have added the following notices:
>
> notice("secondary ip address is ${secondary_ip}")
> notice("project network interface is ${project_network_interface}")
>
> and get the following output on the server:
>
> notice: Scope(S_project[my_project-env]): secondary ip address is x.x.x.x
> notice: Scope(S_project[my_project-env]): project network interface is
>
> I guess I am running into a scope issue or something.  I have also tried to
> move the assignment of project_network_interface in front of the "call" to
> the create_project define.
>
> Does the behavior I am seeing make sense?  I don't know what I can do
> different.
>

Ok, the solution here is to define my ip address variables before I do my
includes in the node.  This is a bit annoying since I wanted to keep the
definition of the variable together with my module that sets up the ip
address on the server but at last it is working.

Chris


>
>
>>
>> Regards, DavidS
>>
>> >>
>>
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] puppet @openexpo in Switzerland

[Marc Fournier]

Hi,

Next wednesday and thursday, a few puppeteers will hold a small booth
at OpenExpo in Winterthur¹. If you're somewhere around northern
Switzerland/southern Germany/western Austria, you may want to drop by
and exchange a few ideas with us.

If you're new to puppet, we'll have a couple of demos running and will
be glad to explain how all this stuff works !

Hope to see you soon !

¹http://www.openexpo.ch/openexpo-2009-winterthur/open-source-projekte/#c1132



--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Puppet Camp Schedule Posted

[Andrew Shafer]

http://reductivelabs.com/home/community/puppetcamp/

There will be plenty of Puppet Tips, Tips and Best Practices, and that’s
just in the breaks and meals.

Come hear about some of the most advanced Puppet implementations and the
lessons learned along the way.

*Learn:*

   - How people are managing 1000s of machines across multiple data centers
   - Puppet development lifecycle
   - Test Driven System Information
   - Stored Configs
   - Puppet and JRuby

Hope to see you there!

(I'm working angles to see if we can get presentations streamed/recorded. So
if you have any resources/ideas, let me know)

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Puppet Camp Schedule Posted

[Marc Fournier]

> (I'm working angles to see if we can get presentations
> streamed/recorded.

+1 for this idea :-)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] How to tailor config. files for groups of hosts?

[tobyriddell]

Hi,

I'm trying to figure out the best way to generate tailored config.
files for several sets of hosts. Here's a concrete example with a
sudoers file:

class hostgroups {
$devhosts = [ "devhost1", "devhost2" ]
$prodhosts = [ "prodhost1", "prodhost2" ]
$ukhosts = $devhosts + $prodhosts
}

Template sudoers file:

<% if @devhosts.inclu...@hostname %>
# Allow developers root access on dev. boxes
user1 devhost1=(root) /bin/su -
user1 devhost2=(root) /bin/su -
<% end %>

<% if @prodhosts.inclu...@hostname %>
# Only admins get root on prod. boxes
admin1 prodhost1=(root) /bin/su -
admin1 prodhost2=(root) /bin/su -
<% end %>

I'm sure this is something that has been done before - am I doing it
the best way?

Thanks.

Toby

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Ruby on HP-UX B.11.11 (11iv1)

[Mark Nelson]

Hello

I am hoping to deploy Puppet 0.25.0  within our Unix infrastructure.  
One of our systems runs on HP-UX B.11.11 (HP-UX 11iv1), I am having 
trouble getting ruby to run on this platform.  The version of ruby that 
is available on the HP-UX Software Archive (http://hpux.connect.org.uk/) 
is 1.8.4, however puppet generates an error when it starts up.

 I have attempted to build 1.8.7 from source, ruby compiles 
successfully.  Puppet generates an SSL error when trying to start, 
unfortunately I am sending this mail from home and don't have a copy of 
the error messages.

Had anyone successfully deployed puppet,  either 0.25.0 or any other 
version on HP-UX B.11.11.  If so where did you get your ruby binary from.

Any help greatfuly received.

Mark.

-- 
---
Mark Nelson - m...@tardis.cx
This mail is for the addressee only



--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Remove user from a specific group?

[Jos Backus]

On Tue, Sep 15, 2009 at 12:41:16PM -0700, Jos Backus wrote:
> How do I tell Puppet to remove a user from a specific group?

Turns out `gpasswd -d user group' handles this on RedHat-based OSes. Would be
nice if the groupadd provider supported this. :-)

-- 
Jos Backus
jos at catnook.com

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Remove user from a specific group?

[James Turnbull]

2009/9/22 Jos Backus :
>
> On Tue, Sep 15, 2009 at 12:41:16PM -0700, Jos Backus wrote:
>> How do I tell Puppet to remove a user from a specific group?
>
> Turns out `gpasswd -d user group' handles this on RedHat-based OSes. Would be
> nice if the groupadd provider supported this. :-)
>

Can you open a ticket please Jos.

Thanks

James Turnbull

-- 
Author of:
* Pro Linux Systems Administration (http://tinyurl.com/linuxadmin)
* Pulling Strings with Puppet (http://tinyurl.com/pupbook)
* Pro Nagios 2.0 (http://tinyurl.com/pronagios)
* Hardening Linux (http://tinyurl.com/hardeninglinux)

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Remove user from a specific group?

[Jos Backus]

On Tue, Sep 22, 2009 at 09:35:55AM +1000, James Turnbull wrote:
> Can you open a ticket please Jos.

Filed as http://projects.reductivelabs.com/issues/2667. Thanks, James.

-- 
Jos Backus
jos at catnook.com

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---