Re: [Puppet Users] Re: Problems with require inside a definition

[Jason Koppe]

Thanks, that works as expected.

On Sun, Aug 8, 2010 at 4:58 PM, Peter Meier  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 08/07/2010 01:31 AM, Jason Koppe wrote:
> > I ended up getting this syntax to work:
>
> just  minor note:
>
>
> >   4 $id,
> >   5 $runlevels = '123456',
> >   6 $action = 'respawn',
> >   7 $process
> >   8 ) {
> >   9
> >  10 augeas {"inittab_$id":
> >  11 context => "/files/etc/inittab",
> >  12 force => "true",
> >  13 require => $require,
>
> you don't need to pass the require, the require to the define will
> automatically be passed to all it's containing resources.
>
> cheers pete
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkxfKHcACgkQbwltcAfKi3/JcACfeTWMlELe1ZQ7MZeXCUP4LCZe
> iLcAn3yLUEvX3JcF4O5WDo8BJscm2TOE
> =4yz3
> -END PGP SIGNATURE-
>
> --
> 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.
>
>


-- 
Jason Koppe
jason.robert.ko...@gmail.com
Cell (210) 445-8242

-- 
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] variable confusion

[David Schmitt]

On 8/9/2010 6:23 PM, Christopher Johnston wrote:

Why can't variables be reassigned with a setup like this?

node /.*mydomain.com/  {
   import mydomain.pp
}

node /*.yourdomain.com/  {
   import yourdomain.pp
}

In manifest mydomain.pp and yourdomain.pp I have variables that are
specific to that site that I want to import only for that site (ie,
dns_nameserver ldap_server).  I get errors that variable cannot be
reassigned.  My reasoning for wanting to separate everything into
separate site specific manifests is mostly because my nodes.pp is
getting way too cluttered and difficult to manage (over 1k lines of
code).  It looks like stuff is getting imported regardless of the node
type (case statements also show the same behavior).

err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Cannot reassign variable site_id at
/etc/puppet/manifests/nodes/mydomain.pp:5 on node host.yourdomain.com




Because, AFAIUI, imports are not constrained by their surrounding scope. 
That means that top-level variables in a file will always be added to 
the ::main scope, regardless of how they're imported.


Either put the nodes statement into the imported files too, or inline 
the imported files instead, or use a facility like extlookup, or use an 
external node classifier.



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] Puppet and Andorid

[Michael Gliwinski]

On Tuesday 10 Aug 2010 04:06:22 Rohan McGovern wrote:
> They need to be managed, just like everything else.

Yeah, I fully agree.  Especially since puppet can simply manage what needs to 
be managed and leave the rest alone, it's very useful to be able to "scale it 
down" and run on routers, tablets, phones, etc.


-- 
Michael Gliwinski
Henderson Group Information Services
9-11 Hightown Avenue, Newtownabby, BT36 4RT
Phone: 028 9034 3319

**
The information in this email is confidential and may be legally privileged.  
It is intended solely for the addressee and access to the email by anyone else 
is unauthorised.
If you are not the intended recipient, any disclosure, copying, distribution or 
any action taken or omitted to be taken in reliance on it, is prohibited and 
may be unlawful.
When addressed to our clients, any opinions or advice contained in this e-mail 
are subject to the terms and conditions expressed  in the governing client 
engagement leter or contract.
If you have received this email in error please notify 
supp...@henderson-group.com

John Henderson (Holdings) Ltd
Registered office: 9 Hightown Avenue, Mallusk, County Antrim, Northern Ireland, 
BT36 4RT.
Registered in Northern Ireland
Registration Number NI010588
Vat No.: 814 6399 12
*

-- 
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] "ensure => running" an init script that isn't actually a service ?

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

>> Which is what we want, but i'm curious as to _why_ this is so,
>> given (again) that we're talking about an init script, and not a
>> particular service that sits in memory.  Granted, the effects of
>> the script can be known - is puppet smart enough to figure out what
>> effect "service network *" ultimately has on the system, or is this
>> sort of a happy accident, or yet something else entirely ?
> 
> This is just guessing from behavior I’ve witnessed, but I think
> Puppet calls `service whatever status` and looks at the exit status.
> 0 means “running” and everything else means not running.
> 
> `service network status` exits with 0 on my RHEL5 systems.

exactly. that's the terminology (running) used for init.d scripts that
exit with 0.

cheers pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxhImUACgkQbwltcAfKi39bMwCfWh4pUk3/QHuoIuQVXEqXt5o4
EOEAni3a90LZLeAOFIpcnvBHRB/vix6C
=Gald
-END PGP SIGNATURE-

-- 
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] Installing packages that use dbconfig-common on Debian

[Craig Box]

I have been trying to use Puppet to install the Zabbix server, which uses
dbconfig-common to set up its database.

If you don't do anything more than package { "zabbix-server-mysql": ensure
=> installed }, then you end up with errors that look much like this
(snipped for brevity) :

err: //zabbix::server/Package[zabbix-server-mysql]/ensure: change from
purged to present failed: Execution of '/usr/bin/apt-get -q -y -o
DPkg::Options::=--force-confold install zabbix-server-mysql' returned 100:
Reading package lists...
Building dependency tree...
Reading state information...

Preconfiguring packages ...
.: 3: Can't open /usr/share/dbconfig-common/dpkg/config.mysql
zabbix-server-mysql failed to preconfigure, with exit status 2
Fetched 5659kB in 0s (9017kB/s)

Setting up zabbix-server-mysql (1:1.8.1-1ubuntu1) ...
dbconfig-common: writing config to
/etc/dbconfig-common/zabbix-server-mysql.conf

Creating config file /etc/dbconfig-common/zabbix-server-mysql.conf with new
version

Creating config file /etc/zabbix/zabbix_server.conf with new version
ERROR 2002 (HY000): Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2).
unable to connect to mysql server.
error encountered creating user:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2)
dbconfig-common: zabbix-server-mysql configure: aborted.
dbconfig-common: flushing administrative password
dpkg: error processing zabbix-server-mysql (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 zabbix-server-mysql
E: Sub-process /usr/bin/dpkg returned an error code (1)

In short, it's expecting that you have answered questions about its MySQL
root password.

If you install the package manually, the first question you are asked is
whether or not you want to use dbconfig-common, and a warning that if you
already have a database set up, you don't want to use it.  It seem to
influence the value for the dbconfig-install key.  Therefore, it stands to
reason that if I preseed this key:

   zabbix-server-mysql zabbix-server-mysql/dbconfig-install boolean false

then I should get what I want.  However, I don't - still prompted, still
fails to install silently, etc.

As this question probably comes up a lot for people installing software
through Puppet, has anyone come up with a satisfactory solution to tell
debconf/dbconfig-common to just get out of the way entirely?

Craig

-- 
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] Adding a new User

[parag(PK)]

Hey,

I tried to add a new user using puppet on my Ubuntu client,but i am
getting problems when i get logged in . i get a complete empty
desktop screen with an error ...
HELP!!

-- 
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] Adding a new User

[James Turnbull]

parag(PK) wrote:
> Hey,
> 
> I tried to add a new user using puppet on my Ubuntu client,but i am
> getting problems when i get logged in . i get a complete empty
> desktop screen with an error ...
> HELP!!
> 

So... How about the following information:

1.  Your Puppet version
2.  Your manifest
3.  Your Ubuntu version.
4.  The error you are getting.

Without these it's pretty tricky to debug your issue.

Regards

James Turnbull

-- 
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571

-- 
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: RHEL4 puppet-dashboard 1.0.3

[ScubaDude]

Packages I needed to get dashboard running on a RHEL4 Server:

>From the Extra Packages for Enterprise Linux repository:
http://fedoraproject.org/wiki/EPEL

32-bit: http://download.fedora.redhat.com/pub/epel/4/i386/repoview/
64-bit: http://download.fedora.redhat.com/pub/epel/4/x86_64/repoview/

augeas-0.7.2-1
augeas-libs-0.7.2-1
facter-1.5.7
ruby-augeas-0.3.0.1
ruby-mysql-2.7.3-1

The version of ruby provided with RHEL 4 is too old, a newer version
is available from the CentOS Testing repository, I couldn’t find a
RedHat equivalent:
http://dev.centos.org/centos/4/

ruby-1.8.5-5
ruby-docs-1.8.5.-5
ruby-irb-1.8.5-5
ruby-libs-1.8.5-5
ruby-rdoc-1.8.5-5

I installed the above rpm's before the following:

http://github.com/puppetlabs/puppet-dashboard/blob/master/README.markdown>
Install the gem package manager -- do not install RubyGems version
1.3.6 or newer because they are incompatible with the Ruby shipped
with CentOS 5.5:

URL="http://production.cf.rubygems.org/rubygems/rubygems-1.3.5.tgz";
PACKAGE=$(echo $URL | sed "s/\.[^\.]*$//; s/^.*\///")
pushd "/tmp"
  CACHE=`mktemp -d install_rubygems.XX`
  pushd "$CACHE"
wget -c -t10 -T20 -q "$URL"
tar xfz "$PACKAGE.tgz"
cd "$PACKAGE"
sudo ruby setup.rb
  popd
popd

Install the rubygem rake:

gem install rake


I tried to install the mysql gem the same way, but got errors because
ruby needed to be a higher revision.

http://rubyworks.rubyforge.org/redhat/4.9/RPMS/x86_64/
rubygem-mysql-2.7-2


Finally install puppet-dashboard from rpm:

http://yum.puppetlabs.com/base/
puppet-dashboard-1.0.3-3.norarch.rpm

--nodeps required. The package appears to use an rpm query to check
dependencies, the rake gem wasn’t installed as an RPM, neither was
rubygems so it fails.

rpm –Uvh --nodeps puppet-dashboard-1.0.3-3.norarch.rpm

-- 
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 and Andorid

[Disconnect]

Nothing that involves ruby counts as "scaling it down". At that point, you
have so much spare ram and cpu that you are trying to use it all up
somehow..

(That isn't a cut on ruby, although it does seem to be a little less
efficient than, say, perl. The same thing would apply to any large
interpreted language, and doubly so for something like puppet where you are
basically nesting interpreted environments inside each other...)

On Tue, Aug 10, 2010 at 4:53 AM, Michael Gliwinski <
michael.gliwin...@henderson-group.com> wrote:

> On Tuesday 10 Aug 2010 04:06:22 Rohan McGovern wrote:
> > They need to be managed, just like everything else.
>
> Yeah, I fully agree.  Especially since puppet can simply manage what needs
> to
> be managed and leave the rest alone, it's very useful to be able to "scale
> it
> down" and run on routers, tablets, phones, etc.
>
>
> --
> Michael Gliwinski
> Henderson Group Information Services
> 9-11 Hightown Avenue, Newtownabby, BT36 4RT
> Phone: 028 9034 3319
>
>
> **
> The information in this email is confidential and may be legally
> privileged.  It is intended solely for the addressee and access to the email
> by anyone else is unauthorised.
> If you are not the intended recipient, any disclosure, copying,
> distribution or any action taken or omitted to be taken in reliance on it,
> is prohibited and may be unlawful.
> When addressed to our clients, any opinions or advice contained in this
> e-mail are subject to the terms and conditions expressed  in the governing
> client engagement leter or contract.
> If you have received this email in error please notify
> supp...@henderson-group.com
>
> John Henderson (Holdings) Ltd
> Registered office: 9 Hightown Avenue, Mallusk, County Antrim, Northern
> Ireland, BT36 4RT.
> Registered in Northern Ireland
> Registration Number NI010588
> Vat No.: 814 6399 12
>
> *
>
> --
> 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] inventory of managed resources

[Adam Winberg]

i've tested the storeconfigs option but i'm not fully getting what i want
(do we ever..?).

i've got quite a lot of files i sync with my clients via puppets fileserving
capabilities. these files are tagged with different suffixes as labels,
like:
resolv.conf--serverA
resolv.conf--CLUSTER1
resolv.conf--GROUP2
my.cnf--DBGROUP1

and so forth (and for the record - the files above are only examples and i
do also use templates).

what i want to do is query my puppetmaster which files a specific node is
getting, from a fileserving point of view. if serverA is part of the
DBGROUP1 group then my query would result in a list of files:
my.cnf--DBGROUP1
resolv.conf--serverA

any ideas on how to accomplish this?

//Adam

On 10 July 2010 10:48, Adam Winberg  wrote:

> ah, good point! i will look into it, thank you.
>
> //Adam
>
>
> On 9 July 2010 09:23, David Schmitt  wrote:
>
>> On 7/7/2010 4:33 PM, Adam Winberg wrote:
>>
>>> Hi,
>>>
>>> are there any good ways of scripting an inventory of managed resources
>>> on all nodes? I've found the inventory script by R.I.Pienaar
>>> (
>>> http://www.devco.net/archives/2010/02/26/what_does_puppet_manage_on_a_node-2.php
>>> )
>>> which does what I want but only locally on each client. Is there any
>>> native way of syncing the client_yaml data centrally or any other way of
>>> doing this?
>>>
>>> I need a script-friendly way of checking which clients have this or that
>>> configuration, i.e. "which ip addresses are managed by puppet on client
>>> X" or "which files..." and so on.
>>>
>>
>> If you activate storedconfigs, puppet will keep a database of all
>> currently configured resources.
>>
>>
>> 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.
>>
>>
>

-- 
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: status of e-mail (Re: Re: [Puppet Users] Puppet and Andorid)

[Disconnect]

Enjoy your "off in the world", but how about not replying to list postings
with this spam..?

On Tue, Aug 10, 2010 at 10:34 AM, Joey B'Shalom wrote:

> Hey,
>
> I’m often out in the world and only able to check email a couple of times
> each day. I should be able to get back to you fairly soon, but if you need
> to get hold of me right away, you can reach me here:
>
> http://awayfind.com/joey
>
> Be sure to store this link with my contact information in case of an
> emergency.  Thanks.
>
> Joey
>
> --
>
> Opt out of future auto-replies:
> http://orchant.awayfind.com/oo?h=d10909ac&e=5f00af5f
>

-- 
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: Problems with require inside a definition

[Nigel Kersten]

Argh. Everyone is doing this require dance because of the docs on
definitions right?

http://docs.puppetlabs.com/guides/language_tutorial.html#definitions

We had a chat about that on the list a while ago and realized that was
horribly out of date, I'll try to get a patch in to fix it.



On Tue, Aug 10, 2010 at 12:31 AM, Jason Koppe
 wrote:
> Thanks, that works as expected.
>
> On Sun, Aug 8, 2010 at 4:58 PM, Peter Meier  wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 08/07/2010 01:31 AM, Jason Koppe wrote:
>> > I ended up getting this syntax to work:
>>
>> just  minor note:
>>
>>
>> >   4                 $id,
>> >   5                 $runlevels = '123456',
>> >   6                 $action = 'respawn',
>> >   7                 $process
>> >   8         ) {
>> >   9
>> >  10                 augeas {"inittab_$id":
>> >  11                         context => "/files/etc/inittab",
>> >  12                         force => "true",
>> >  13                         require => $require,
>>
>> you don't need to pass the require, the require to the define will
>> automatically be passed to all it's containing resources.
>>
>> cheers pete
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v1.4.10 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iEYEARECAAYFAkxfKHcACgkQbwltcAfKi3/JcACfeTWMlELe1ZQ7MZeXCUP4LCZe
>> iLcAn3yLUEvX3JcF4O5WDo8BJscm2TOE
>> =4yz3
>> -END PGP SIGNATURE-
>>
>> --
>> 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.
>>
>
>
>
> --
> Jason Koppe
> jason.robert.ko...@gmail.com
> Cell (210) 445-8242
>
> --
> 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] puppet (puppet apply) and reporting and fact sync

[Marc Zampetti]

 If I run in the disconnected mode using 'puppet' or 'puppet apply', is 
it possible to still have reports and facts synced to a central server? 
I've tried and it doesn't appear to be so, but I thought I would ask to 
make sure.


Marc Zampetti

--
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] Recipe for Debians MySQL

[Brent Clark]

Hiya

Would anyone have a recipe for Debian's MySQL. Thats to install and
configure (i.e. root password).

Kind Regards
Brent Clark

-- 
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] Facter does not recognise Xen HVM DomU

[Jean Baptiste FAVRE]

Hello everyone,

While discovering puppet, I just figured out that facter does not
recognise my server as Xen HVM DomU, at least not in virtual fact:

# facter
facterversion => 1.5.1
manufacturer => Xen
operatingsystem => Debian
operatingsystemrelease => 5.0.5
productname => HVM domU
puppetversion => 0.25.4
rubyversion => 1.8.7
type => Other
virtual => physical

My dom0 is ok: virtual => xen0

The problem is that I want to use virtual fact to manage grub menu.lst
options related to xen. For the moment, I'm trying to use virtual fact.

A quick look into virtual.rb, and a dirty hack later, I can see my HVM
domU as what they are. Now I wonder to know if I use the right fact ?

Regards,
JB


Here's my diff:
# diff -C 10 /usr/lib/ruby/1.8/facter/virtual.rb
/usr/lib/ruby/1.8/facter/virtual.rb.xen
*** /usr/lib/ruby/1.8/facter/virtual.rb 2010-08-07 14:20:31.0 +0200
--- /usr/lib/ruby/1.8/facter/virtual.rb.xen 2010-08-07
14:20:09.0 +0200
***
*** 34,53 
--- 34,54 
  end
  end

  if result == "physical"
  output = Facter::Util::Resolution.exec('lspci')
  if not output.nil?
  output.each_line do |p|
  # --- look for the vmware video card to determine
if it is virtual => vmware.
  # --- 00:0f.0 VGA compatible controller:
VMware Inc [VMware SVGA II] PCI Display Adapter
  result = "vmware" if p =~ /VM[wW]are/
+ result = "xenhvm" if p =~ /XenSource/
  end
  else
  output = Facter::Util::Resolution.exec('dmidecode')
  if not output.nil?
  output.each_line do |pd|
  result = "vmware" if pd =~ /VMware|Parallels/
  end
  else
  output = Facter::Util::Resolution.exec('prtdiag')
  if not output.nil?

-- 
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] networking on centos

[cola]

Hi All.

I'm new to puppet, just want to know which is the right way to
configure networking on centos (5).
Is there something built in, or should I use a module from puppet
forge ?

Following this thread :

http://groups.google.com/group/puppet-users/browse_thread/thread/44dfd59abfb6a87e/968ef27084259546?lnk=gst&q=network+centos#968ef27084259546

seems that there there isn't something built in, but that you have to
do it by hands. Is this the right way ?

I've puppet up running, and now the first thing I'm trying to achieve
is to configure the network interface ( /etc/sysconfig/network and /
etc/sysconfig/network.scripts/ifcfg-eth0 ) for a host as soon as it's
being provisioned.

Thanks, regards

-- 
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/OpenSUSE 11.3 and packages

[jose]

I'm looking at using puppet with OpenSUSE 11.3. I've been using it
happily with Centos 5 but am thinking of switching our lab clients to
the former. I'm having a little trouble getting packages to install.
Out of the box I get an error that "RPMs must specify a package
source". I found a puppet guide for SUSE which suggested installing
yum and pointing it at the SUSE repositories. This I did but I got the
error that it "cannot retrieve repository metadata (repomd.xml) for
repository". I did a little Googling and saw a post which suggested
that OpenSUSE no longer provide yum compatible repositories. I went
back to the puppet documentation and see that for SUSE the package
providers are rug, yum and rpm. I can't find any reference to rug in
OpenSUSE 11.3 (I'm guessing it's no longer used). I'm not too keen on
installing individual rpms by name.

Basically I was wondering what people are doing for package management
with Puppet on OpenSUSE 11.3?

Ta.

-- 
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] 403 after changing from webrick to mongrel

[Darren Worrall]

Hey folks,

We're on the verge of deploying puppet into production so have changed
from using webrick to mongrel with an apache reverse proxy. The nodes
were behind a NAT firewall under webrick but it didnt seem to mind,
however something isnt right with my reverse proxy configuration and I
cant figure out what.

Clients can connect, have their certificate signed ok, but when it
try's to retrieve the catalog we get:

 Error 403 on SERVER: Forbidden request: router.x.x.x(1.1.1.1) - IE,
the NAT device local to the puppetmaster, rather than the node name.

puppetmaster is configured with ssl_client_header = HTTP_X_CLIENT_DN,
and apache is setting that header to the S_DN (RequestHeader set X-
Client-DN %{SSL_CLIENT_S_DN}e ) - does the fact that the reverse
lookup of the nat router does not match the fqdn of the node matter in
this configuration? It didn't with webrick.

Cheers,

Darren

-- 
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: status of e-mail (Re: Re: [Puppet Users] Puppet and Andorid)

[Joey B'Shalom]

Gah. Sorry, everyone. Total faux pas on my part... I forgot to add
this list address to my "don't respond to this" filter for my
autoresponder. Mea maxima culpa. It's fixed now.

joey

On Tue, Aug 10, 2010 at 08:18, Disconnect  wrote:
> Enjoy your "off in the world", but how about not replying to list postings
> with this spam..?
>
> On Tue, Aug 10, 2010 at 10:34 AM, Joey B'Shalom 
> wrote:
>>
>> Hey,
>>
>> I’m often out in the world and only able to check email a couple of times
>> each day. I should be able to get back to you fairly soon, but if you need
>> to get hold of me right away, you can reach me here:
>>
>> http://awayfind.com/joey
>>
>> Be sure to store this link with my contact information in case of an
>> emergency.  Thanks.
>>
>> Joey
>>
>> --
>>
>> Opt out of future auto-replies:
>> http://orchant.awayfind.com/oo?h=d10909ac&e=5f00af5f
>
>



-- 
Joey - artist, riot nrrrd, and finder of lost earrings

I'm not so good with email. So if you need to reach me quickly, try
this link: http://awayfind.com/joey

-- 
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: RHEL4 puppet-dashboard 1.0.3

[Rein Henrichs]

Excerpts from ScubaDude's message of Tue Aug 10 06:58:53 -0700 2010:
> Packages I needed to get dashboard running on a RHEL4 Server:

Thanks for detailing your installation procedure. We'll add it to the
Dashboard instructions.
-- 
Rein Henrichs
http://puppetlabs.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-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] Facter does not recognise Xen HVM DomU

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

> A quick look into virtual.rb, and a dirty hack later, I can see my HVM
> domU as what they are. Now I wonder to know if I use the right fact ?

this could be a bug, actually a missing recognition due to the
difference of HVM domU (I guess). Can you file a bugreport?

thanks

pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxhkH4ACgkQbwltcAfKi38kqQCeL98TAoppPtxueNXNx2u9kxeA
mJkAn2TtCPPgM4cayG24A7l/dCb+3Yjq
=BEhX
-END PGP SIGNATURE-

-- 
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] Facter does not recognise Xen HVM DomU

[Rein Henrichs]

Excerpts from Jean Baptiste FAVRE's message of Sat Aug 07 05:46:12 -0700 2010:
> Hello everyone,
> 
> While discovering puppet, I just figured out that facter does not
> recognise my server as Xen HVM DomU, at least not in virtual fact:
> 
> [ snip ]
>
> A quick look into virtual.rb, and a dirty hack later, I can see my HVM
> domU as what they are. Now I wonder to know if I use the right fact ?

Hi Jean,

Thanks for reporting this. I've added a ticket [1] to our issue tracker
so we can follow up on this issue more easily. Your issue seems to be
related to (or possibly a duplicate of) some existing tickets. I've
listed them as related in the ticket itself. Would you mind taking a
look at those to see if your issue is a duplicate? If so, we can assign
it as such.

Thanks!

[1] http://projects.reductivelabs.com/issues/4508
-- 
Rein Henrichs
http://puppetlabs.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-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] networking on centos

[Jeff McCune]

On Mon, Aug 9, 2010 at 5:46 AM, cola  wrote:
> I've puppet up running, and now the first thing I'm trying to achieve
> is to configure the network interface ( /etc/sysconfig/network and /
> etc/sysconfig/network.scripts/ifcfg-eth0 ) for a host as soon as it's
> being provisioned.

Managing these two files works well and is something I do regularly myself.

Keep in mind puppet agent generates SSL certificates based on the
hostname of the machine by default.  If your hostname changes then
puppet will automatically re-generate certificates and issue a
certificate signing request to the certificate authority server.

-- 
Jeff McCune
http://www.puppetlabs.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-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: RHEL4 puppet-dashboard 1.0.3

[Igal Koshevoy]

On 08/10/2010 06:58 AM, ScubaDude wrote:
> Packages I needed to get dashboard running on a RHEL4 Server:
>   
Thanks for describing this, we'll incorporate these into a future
release of the Puppet Dashboard's documentation. I've added a feature
ticket for this at http://projects.puppetlabs.com/issues/4510

If you or others have other OS-specific instructions, please feel free
to submit a patch against the docs.

>   augeas-0.7.2-1
>   augeas-libs-0.7.2-1
>   facter-1.5.7
>   ruby-augeas-0.3.0.1
>   
The Puppet Dashboard doesn't require these packages -- I suspect these
were required as part of installing Puppet.

> From the Extra Packages for Enterprise Linux repository:
>ruby-mysql-2.7.3-1
> [...]
> I tried to install the mysql gem the same way, but got errors because
> ruby needed to be a higher revision. 
> [...]
> [Instead installed from]
>http://rubyworks.rubyforge.org/redhat/4.9/RPMS/x86_64/rubygem-mysql-2.7-2
The "ruby-mysql" package from EPEL is recommended by the documentation
for newer versions of CentOS and provides a pre-compiled library that's
tricky to to build otherwise. Did the EPEL package work for you? If so,
there shouldn't have been a need to install it via `gem install
ruby-mysql` or from rubyworks. If not, can you please summarize what
happened?

> Finally install puppet-dashboard from rpm:
>
> http://yum.puppetlabs.com/base/puppet-dashboard-1.0.3-3.norarch.rpm
>
> --nodeps required. The package appears to use an rpm query to check
> dependencies, the rake gem wasn’t installed as an RPM, neither was
> rubygems so it fails.
>
> rpm –Uvh --nodeps puppet-dashboard-1.0.3-3.norarch.rpm
>   
The packages assume you're running a newer version of CentOS. Your
`--nodeps` workaround for this is fine. Another approach would have been
to use a source-only version of the software downloaded from github.

Anyway, thank you for working through this and describing your experiences.

-igal

-- 
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: Puppet + OpenVZ

[Matthew Cluver]

Rein,

I'm not sure if you've seen the message on github, I wanted to respond
here to make sure that you'd seen it. I've tested and confirmed that
the patch Kai submitted will work correctly moving forward.

Regards,

Matt

On Aug 9, 4:20 pm, Rein Henrichs  wrote:
> Excerpts from Matthew Cluver's message of Mon Aug 09 11:42:12 -0700 2010:
>
> > Hi Rein,
>
> > I have been using the code above in the openvz module as it is working
> > for my needs (0.25.5-1) at the current moment. I have no problem using
> > the proposed patch, my main goal is to simply get a working and
> > dependable version into the next round of releases.
>
> > Matt
>
> Thanks, Matt. I updated the proposed patch to fix a spec it broke
> because of the new behavior. It's in my ticket/master/4156-openvz branch
> on my github (reinh). Would you mind testing this to see if it works for
> you?
>
> Rein
> --
> Rein Henrichshttp://puppetlabs.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-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/OpenSUSE 11.3 and packages

[Michael Knox]

 Jose,
rug disappeared from OpenSuSE about 11.1/11.2.
zypper as a package provider should be fully (thanks to patches #3802 & 
#1223) supported in puppet 2.6. I'm using 0.25.5 with those patches.


The other hassle which I've just been dealing with is repo definitions, 
you can use yumrepo but I think that process is fairly awkward on 
SuSE/OpenSuSE when you could use yast repo definitions.
The yumrepo type seems interesting, as it doesn't use providers, so I've 
copied it and hacked it to create a zypprepo type which generates zypp 
repo files instead. I'll share the type soon.


Cheers

On 11/08/10 2:10 AM, jose wrote:

I'm looking at using puppet with OpenSUSE 11.3. I've been using it
happily with Centos 5 but am thinking of switching our lab clients to
the former. I'm having a little trouble getting packages to install.
Out of the box I get an error that "RPMs must specify a package
source". I found a puppet guide for SUSE which suggested installing
yum and pointing it at the SUSE repositories. This I did but I got the
error that it "cannot retrieve repository metadata (repomd.xml) for
repository". I did a little Googling and saw a post which suggested
that OpenSUSE no longer provide yum compatible repositories. I went
back to the puppet documentation and see that for SUSE the package
providers are rug, yum and rpm. I can't find any reference to rug in
OpenSUSE 11.3 (I'm guessing it's no longer used). I'm not too keen on
installing individual rpms by name.

Basically I was wondering what people are doing for package management
with Puppet on OpenSUSE 11.3?

Ta.



--
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] inventory of managed resources

[Luke Kanies]

That really does seem like something storeconfigs can give you, at  
least if you write the query.


It's basically finding all files owned by the host in question.   
Something like (in ActiveRecord):


Puppet::Rails::Node.resources.find_all { |resource| resource.type ==  
"file" }.collect { |resource| resource.title }


That should return an array of file names.  Haven't tested it mind  
you, but something like that should work.


Another option involves client-side opening the catalog and reading  
the files.  I've written a script that does this for a bank that  
delivers its output to their auditors.  Ended up being very simple.


On Aug 10, 2010, at 7:34 AM, Adam Winberg wrote:

i've tested the storeconfigs option but i'm not fully getting what i  
want (do we ever..?).


i've got quite a lot of files i sync with my clients via puppets  
fileserving capabilities. these files are tagged with different  
suffixes as labels, like:

resolv.conf--serverA
resolv.conf--CLUSTER1
resolv.conf--GROUP2
my.cnf--DBGROUP1

and so forth (and for the record - the files above are only examples  
and i do also use templates).


what i want to do is query my puppetmaster which files a specific  
node is getting, from a fileserving point of view. if serverA is  
part of the DBGROUP1 group then my query would result in a list of  
files:

my.cnf--DBGROUP1
resolv.conf--serverA

any ideas on how to accomplish this?

//Adam

On 10 July 2010 10:48, Adam Winberg  wrote:
ah, good point! i will look into it, thank you.

//Adam


On 9 July 2010 09:23, David Schmitt  wrote:
On 7/7/2010 4:33 PM, Adam Winberg wrote:
Hi,

are there any good ways of scripting an inventory of managed resources
on all nodes? I've found the inventory script by R.I.Pienaar
(http://www.devco.net/archives/2010/02/26/what_does_puppet_manage_on_a_node-2.php 
)

which does what I want but only locally on each client. Is there any
native way of syncing the client_yaml data centrally or any other  
way of

doing this?

I need a script-friendly way of checking which clients have this or  
that
configuration, i.e. "which ip addresses are managed by puppet on  
client

X" or "which files..." and so on.

If you activate storedconfigs, puppet will keep a database of all  
currently configured resources.



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 
.





--
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 
.



--
Man is the only animal that can remain on friendly terms with the
victims he intends to eat until he eats them.
-- Samuel Butler (1835-1902)
-
Luke Kanies  -|-   http://puppetlabs.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] inventory of managed resources

[R.I.Pienaar]

- "Luke Kanies"  wrote:

> That really does seem like something storeconfigs can give you, at
> least if you write the query.
> 
> 
> It's basically finding all files owned by the host in question.
> Something like (in ActiveRecord):
> 
> 
> Puppet::Rails::Node.resources.find_all { |resource| resource.type ==
> "file" }.collect { |resource| resource.title }
> 
> 
> That should return an array of file names. Haven't tested it mind you,
> but something like that should work.
> 
> 
> Another option involves client-side opening the catalog and reading
> the files. I've written a script that does this for a bank that
> delivers its output to their auditors. Ended up being very simple.


I have a script like this at 
http://www.devco.net/archives/2010/02/26/what_does_puppet_manage_on_a_node-2.php

Not tested on 2.6 yet though.

-- 
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: Puppet + OpenVZ

[Rein Henrichs]

Excerpts from Matthew Cluver's message of Tue Aug 10 12:59:51 -0700 2010:
> I'm not sure if you've seen the message on github, I wanted to respond
> here to make sure that you'd seen it. I've tested and confirmed that
> the patch Kai submitted will work correctly moving forward.

Thanks Matt. I'm merging the ticket branch into next and marking the
ticket Ready for Check-in, meaning it will go into master and then an
upcoming release, possibly 1.5.8, when we can close it.
-- 
Rein Henrichs
http://puppetlabs.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-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] Facter does not recognise Xen HVM DomU

[Jean Baptiste FAVRE]

Hello Rein,
Strange, my mail took 3 days to be delivered :-/

By the way, I just had a look on the tickets you mentionned.

As far as I can see, they are not duplicates with mine: it's definitelyt
more dom0 detection failure related, not only domU.
In my case, dom0 is perfectly detected. I can't say for PV domU as I
don't use them but reading virtual.rb code, I guess they'll.

My problem is that xen domU detection is currently based on some /proc
or /sys files presence:
- /proc/sys/xen/independent_wallclock
- /sys/bus/xen

These pseudo files appear only in PV domU as they're kernel related. HVM
DomU does not know they're running in a virtualized environment.
Therefore, their kernel does not expose these pseudo-files.

I made few other modifications to virtual.rb so that I can use other
ways to detect xen HVM DomU (lspci, dmidecode) as it's done for other
virtualisation systems (all based on this page:
http://www.dmo.ca/blog/detecting-virtualization-on-linux/). Please
review my patch below (thanks to be indulgent, it's my first patch more
or less ;-) )

Regards,
JB



# diff virtual.rb.xen virtual.rb
44d43
< result = "xenhvm" if p =~ /XenSource/
51d49
< result = "xenhvm" if pd =~ /HVM domU/
77c75
< when "xenu", "openvzve", "vmware", "xenhvm"
---
> when "xenu", "openvzve", "vmware"



On 10/08/2010 19:58, Rein Henrichs wrote:
> Excerpts from Jean Baptiste FAVRE's message of Sat Aug 07 05:46:12 -0700 2010:
>> Hello everyone,
>>
>> While discovering puppet, I just figured out that facter does not
>> recognise my server as Xen HVM DomU, at least not in virtual fact:
>>
>> [ snip ]
>>
>> A quick look into virtual.rb, and a dirty hack later, I can see my HVM
>> domU as what they are. Now I wonder to know if I use the right fact ?
> 
> Hi Jean,
> 
> Thanks for reporting this. I've added a ticket [1] to our issue tracker
> so we can follow up on this issue more easily. Your issue seems to be
> related to (or possibly a duplicate of) some existing tickets. I've
> listed them as related in the ticket itself. Would you mind taking a
> look at those to see if your issue is a duplicate? If so, we can assign
> it as such.
> 
> Thanks!
> 
> [1] http://projects.reductivelabs.com/issues/4508

-- 
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 and Andorid

[Daniel Pittman]

Disconnect  writes:

> Nothing that involves ruby counts as "scaling it down". At that point, you
> have so much spare ram and cpu that you are trying to use it all up
> somehow..
>
> (That isn't a cut on ruby, although it does seem to be a little less
> efficient than, say, perl. The same thing would apply to any large
> interpreted language, and doubly so for something like puppet where you are
> basically nesting interpreted environments inside each other...)

That last isn't fair: Ruby on Android is native ARM code, talking to a
different display layer.  It should be no less efficient than Ruby without any
of the Android bits on ARM.

Daniel

-- 
✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155 707
   ♽ made with 100 percent post-consumer electrons

-- 
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 and Andorid

[Disconnect]

Looking at http://code.google.com/p/android-ruby/, it is an interpreted
language on top of a mix of bytecompiled and native code. (So, slightly
worse than other environments, where it is simply interpreted+native.)

Puppet, being an interpreter in it's own right written in ruby, adds another
layer of same..

Is there something I'm missing? (As an aside, 50 megs - only 3 shared -
seems to be fairly standard for memory use when idle. That -screams- "not
made for embedded" :) ..)

On Tue, Aug 10, 2010 at 7:19 PM, Daniel Pittman  wrote:

> Disconnect  writes:
>
> > Nothing that involves ruby counts as "scaling it down". At that point,
> you
> > have so much spare ram and cpu that you are trying to use it all up
> > somehow..
> >
> > (That isn't a cut on ruby, although it does seem to be a little less
> > efficient than, say, perl. The same thing would apply to any large
> > interpreted language, and doubly so for something like puppet where you
> are
> > basically nesting interpreted environments inside each other...)
>
> That last isn't fair: Ruby on Android is native ARM code, talking to a
> different display layer.  It should be no less efficient than Ruby without
> any
> of the Android bits on ARM.
>
>Daniel
>
> --
> ✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155
> 707
>   ♽ made with 100 percent post-consumer electrons
>
> --
> 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] Facter does not recognise Xen HVM DomU

[Rein Henrichs]

Jean,

Thanks for the info, I'll add it to the ticket.
-- 
Rein Henrichs
http://puppetlabs.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-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] Documentation contribution opportunity - Please help!

[James Turnbull]

Hi all

One of the big pieces of work we undertook earlier in the year was
migrating the wiki from Trac and establishing the Puppet Docs site at:

http://docs.puppetlabs.com

During this process we began doing a programmatic conversion of the
Restructured Text output from the automatically generated documentation
to Markdown.The conversion process is less than perfect and some of
the Markdown generated is not overly elegant - making some of our Docs
pages ugly and hard to read.

As a result we've decided to rewrite the internal documentation from
Restructured Text to Markdown (see
http://projects.puppetlabs.com/issues/4509).

This is largely:

1. The types and providers documentation (lib/puppet/types/typename.rb &
lib/puppet/providers/provider...)
2. The functions and metaparameter documentation
(lib/puppet/parser/functions/functioname.rb)
3. The configuration reference (lib/puppet/default.rb)
4. And the report, network and indirection references

Updating this documentation doesn't require any Ruby knowledge!  All you
need to be able to do is change the existing format into Markdown (both
are fairly simple markup formats).

So if you've ever wanted to contribute to Puppet's core and get some
commits on the board then this is the perfect opportunity.

All you need to go is clone the Puppet git repo and follow the
development life cycle documentation -
http://projects.puppetlabs.com/projects/puppet/wiki/Development_Lifecycle -
(or feel free to ask for help on #puppet on IRC or either list).

OR email me or anyone else from the team if you'd like to help.  Even a
small number of commits will assist us in migrating this documentation
and making the experience of using Puppet easier!

Cheers

James Turnbull

-- 
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571

-- 
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] puppetrun with --class argument not working, ver. 0.25.5

[alcy]

I am experiencing the behavior reported in another bug report (http://
projects.puppetlabs.com/issues/1006) in version 0.25.5, that is:

puppetrun --host xyz.def.com --class apache --debug --trace

gives this:

You must be using LDAP to specify host classes

My puppet.conf looks like this:

[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
factpath=$vardir/lib/facter
templatedir=$confdir/templates
[puppetmasterd]
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY
reports=log,foreman
node_terminus=ldap
ldapserver=192.168.1.214
ldapbase=ou=Hosts,dc=abc,dc=com
ldapuser=cn=admin,dc=abc,dc=com
ldappassword=secret

And a sample node entry like this:

dn: cn=xyz.def.com,ou=Hosts,dc=abc,dc=com
objectClass: device
objectClass: ipHost
objectClass: puppetClient
objectClass: top
cn: xyz.def.com
ipHostNumber: 192.168.1.158
puppetClass: dovecot
puppetClass: apache
puppetClass: imapproxy
environment: production

The above behavior is see only when mentioning a class explicitly,.
Without the —class argument, it works.

-- 
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: Problems with require inside a definition

[Jason Koppe]

Yes, that's part of the reason.  I was working on my module at an obscene
hour and that probably factors in to my extra require dance.

On Tue, Aug 10, 2010 at 10:39 AM, Nigel Kersten  wrote:

> Argh. Everyone is doing this require dance because of the docs on
> definitions right?
>
> http://docs.puppetlabs.com/guides/language_tutorial.html#definitions
>
> We had a chat about that on the list a while ago and realized that was
> horribly out of date, I'll try to get a patch in to fix it.
>
>
>
> On Tue, Aug 10, 2010 at 12:31 AM, Jason Koppe
>  wrote:
> > Thanks, that works as expected.
> >
> > On Sun, Aug 8, 2010 at 4:58 PM, Peter Meier 
> wrote:
> >>
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA1
> >>
> >> On 08/07/2010 01:31 AM, Jason Koppe wrote:
> >> > I ended up getting this syntax to work:
> >>
> >> just  minor note:
> >>
> >>
> >> >   4 $id,
> >> >   5 $runlevels = '123456',
> >> >   6 $action = 'respawn',
> >> >   7 $process
> >> >   8 ) {
> >> >   9
> >> >  10 augeas {"inittab_$id":
> >> >  11 context => "/files/etc/inittab",
> >> >  12 force => "true",
> >> >  13 require => $require,
> >>
> >> you don't need to pass the require, the require to the define will
> >> automatically be passed to all it's containing resources.
> >>
> >> cheers pete
> >> -BEGIN PGP SIGNATURE-
> >> Version: GnuPG v1.4.10 (GNU/Linux)
> >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> >>
> >> iEYEARECAAYFAkxfKHcACgkQbwltcAfKi3/JcACfeTWMlELe1ZQ7MZeXCUP4LCZe
> >> iLcAn3yLUEvX3JcF4O5WDo8BJscm2TOE
> >> =4yz3
> >> -END PGP SIGNATURE-
> >>
> >> --
> >> 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.
> >>
> >
> >
> >
> > --
> > Jason Koppe
> > jason.robert.ko...@gmail.com
> > Cell (210) 445-8242
> >
> > --
> > 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.
>
>


-- 
Jason Koppe
jason.robert.ko...@gmail.com
Cell (210) 445-8242

-- 
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] inventory of managed resources

[Adam Winberg]

i've tested the localconfig.yaml parser and it works well, but it only shows
which files puppet handles from a client point of view. i.e it shows that
puppet manages "/etc/my.cnf" for my client but i really want to see which
file it manages from a server point of view, i.e.
"/path/to/fileshare/etc/my.cnf--DBGROUP1".

as far as i can see, storeconfigs gives me about the same information as mr.
Pienaars localconfig-parserscript. That is, i can see that puppet manages
"/etc/my.cnf" for this client but i cant see from which source this file is
taken. If I'm wrong, I would be very grateful for an example query.

//Adam

On 10 August 2010 22:59, R.I.Pienaar  wrote:

>
> - "Luke Kanies"  wrote:
>
> > That really does seem like something storeconfigs can give you, at
> > least if you write the query.
> >
> >
> > It's basically finding all files owned by the host in question.
> > Something like (in ActiveRecord):
> >
> >
> > Puppet::Rails::Node.resources.find_all { |resource| resource.type ==
> > "file" }.collect { |resource| resource.title }
> >
> >
> > That should return an array of file names. Haven't tested it mind you,
> > but something like that should work.
> >
> >
> > Another option involves client-side opening the catalog and reading
> > the files. I've written a script that does this for a bank that
> > delivers its output to their auditors. Ended up being very simple.
>
>
> I have a script like this at
> http://www.devco.net/archives/2010/02/26/what_does_puppet_manage_on_a_node-2.php
>
> Not tested on 2.6 yet though.
>
> --
> 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] Facter does not recognise Xen HVM DomU

[Paul Nasrat]

On 11 August 2010 03:26, Rein Henrichs  wrote:
> Jean,
>
> Thanks for the info, I'll add it to the ticket.

Note that the "supported" way in terms of hardware is via the cpuid
Hypervisor present leaf and Hypervisor CPUID Information Leaf

See eg 
http://git.annexia.org/?p=virt-what.git;a=blob;f=virt-what-cpuid-helper.c;h=3024c375cb7b71142ded2a6a5836574d5b21f2f5;hb=HEAD

http://micky.ibh.net/~liske/imvirt.html

But that would involve making part of facter C and would probably
break jruby support, unless we used ffi somehow

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.