Adnet Ghislain | 1 Oct 17:12 2006

Re: Facts load by puppet -factsync question

debug: Loaded state in 0.02 seconds
info: Retrieving facts
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: fact_collector/file=/usr/local/.aqadmin/puppet/var/facts: Changing checksum,mode
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: fact_collector/file=/usr/local/.aqadmin/puppet/var/facts/local.rb: Creating checksum {md5}ebb0e7db802c506bdcc054b48f95f311
debug: fact_collector/file=/usr/local/.aqadmin/puppet/var/facts: 2 change(s)
debug: fact_collector/file=/usr/local/.aqadmin/puppet/var/facts/checksum: Replacing /usr/local/.aqadmin/puppet/var/facts checksum {time}Sun Oct 01 13:30:33 +0200 2006 with {time}Sun Oct 01 17:08:49 +0200 2006
notice: fact_collector/file=/usr/local/.aqadmin/puppet/var/facts/checksum: checksum changed '{time}Sun Oct 01 13:30:33 +0200 2006' to '{time}Sun Oct 01 17:08:49 +0200 2006'
notice: fact_collector/file=/usr/local/.aqadmin/puppet/var/facts/mode: mode changed '700' to '755'
debug: Finishing transaction 76696960 with 2 changes
debug: Calling puppetmaster.getconfig
err: Could not retrieve configuration: Unknown class  in file /etc/puppet/manifests/./nodes/vpsv2nodes.pp at line 32
warning: Not using cache on failed configuration


here is the debug message i got on another box, the facts are here but they sems to be not loaded :(  The class name depend of a fact so it fails saying that the class does not exist.


Cordialement,
Ghislain
I just tested this again locally, since the whole point of factsync is that the facts get loaded before the config gets compiled, and it works fine for me. Can you post your client logs? You should see messages about downloading and loading facts before the 'Caching configuration' message. Do you?
Attachment (smime.p7s): application/x-pkcs7-signature, 4221 bytes
_______________________________________________
Puppet-users mailing list
Puppet-users <at> madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
Adnet Ghislain | 1 Oct 17:32 2006

Re: Facts load by puppet -factsync question

If i copy the local.rb file from where puppet download it and put it in a ffacter dir on ruby path then it works.

I use this command to initialize the beast:

mkdir -m 700 -p /usr/local/.aqadmin/puppet/conf/ssl; \
mkdir -m 700 -p /usr/local/.aqadmin/puppet/var/facts; \
mkdir -m 700 -p /usr/local/.aqadmin/puppet/log; \
mkdir -m 700 -p /usr/local/.aqadmin/puppet/run; \
mkdir -m 700 -p /usr/local/.aqadmin/puppet/state; \
puppetd --confdir=/usr/local/.aqadmin/puppet/conf \
--logdir=/usr/local/.aqadmin/puppet/log \
--rundir=/usr/local/.aqadmin/puppet/run \
--statedir=/usr/local/.aqadmin/puppet/state \
--lockdir=/usr/local/.aqadmin/puppet/run \
--vardir=/usr/local/.aqadmin/puppet/var --factsync \
--server=xxx.xxx.xxx.xxx --waitforcert 60 --test

Cordialement,
Ghislain
I just tested this again locally, since the whole point of factsync is that the facts get loaded before the config gets compiled, and it works fine for me. Can you post your client logs? You should see messages about downloading and loading facts before the 'Caching configuration' message. Do you?
Attachment (smime.p7s): application/x-pkcs7-signature, 4221 bytes
_______________________________________________
Puppet-users mailing list
Puppet-users <at> madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
Adnet Ghislain | 1 Oct 17:40 2006

41 server under puppet today

Hello there.

  Just to let you know i have just put in production mode puppet on 41 
freeBSD 4.7 virtual servers (yes not real servers but "jailed ones"). I 
had some little problems with facter at first but i have manualy  
upgraded the servers that where affected by the little "facter does not 
read his facts" problem i had. I should have missed something in my 
deploiement.

  All was fine except some server with very slow responses. Perhaps this 
is why facter had some issue:

notice: Finished configuration run in 1171.60 seconds
notice: Finished configuration run in 1905.57 seconds
notice: Finished configuration run in 1843.25 seconds
notice: Finished configuration run in 2371.23 seconds

The recipes i use on those box are quite simple and most of the time it 
takes only 10-20 seconds.
i had no errors at all and all went fine, i used ruby ssh module to 
launch the commands and setup the beast.

all is ok now  so i hope my life will be better now :)
Thanks Luke for the product !

--

-- 
Cordialement,
Ghislain
Attachment (smime.p7s): application/x-pkcs7-signature, 4221 bytes
_______________________________________________
Puppet-users mailing list
Puppet-users <at> madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
Luke Kanies | 1 Oct 23:21 2006

Re: 41 server under puppet today

On Oct 1, 2006, at 10:40 AM, Adnet Ghislain wrote:

> Hello there.
>
>  Just to let you know i have just put in production mode puppet on  
> 41 freeBSD 4.7 virtual servers (yes not real servers but "jailed  
> ones"). I had some little problems with facter at first but i have  
> manualy  upgraded the servers that where affected by the little  
> "facter does not read his facts" problem i had. I should have  
> missed something in my deploiement.
>
>  All was fine except some server with very slow responses. Perhaps  
> this is why facter had some issue:
>
> notice: Finished configuration run in 1171.60 seconds
> notice: Finished configuration run in 1905.57 seconds
> notice: Finished configuration run in 1843.25 seconds
> notice: Finished configuration run in 2371.23 seconds
>
> The recipes i use on those box are quite simple and most of the  
> time it takes only 10-20 seconds.
> i had no errors at all and all went fine, i used ruby ssh module to  
> launch the commands and setup the beast.

Ouch, those are unreasonably long runs.  You aren't seeing this most  
of the time, then?

I've always been somewhat concerned that there might be performance  
problems for large networks or large configurations, but I haven't  
heard any significant problems so far.

If you continue having very slow runs, I'd like to try to figure out  
what's taking so long.  It could be the packaging, but I don't  
remember if FreeBSD package operations tend to be slow -- if they do,  
then you could schedule them to happen only daily, instead of every run.

> all is ok now  so i hope my life will be better now :)
> Thanks Luke for the product !

Great, I'm glad to hear everything is working well to make your life  
easier.

--

-- 
Luke Kanies
http://madstop.com
Martin Vuk | 2 Oct 19:52 2006
Picon

New repo for suse packages

Hi,

I'm now  using suse build service to build suse packages for puppet
and facter. The packages can now be found at

http://software.opensuse.org/download/systemmanagement:/misc/

They are available for all suse versions now (but I tested them only
on opensuse 10.1 and factory). I will still leave old puppet packages
at the old location, but newer versions of puppet will only be
available at build service. BTW, this suse build service is really
nice.

Martin
Matthew Flanagan | 3 Oct 02:32 2006
Picon

Re: 41 server under puppet today

On 02/10/06, Luke Kanies <luke <at> madstop.com> wrote:
> On Oct 1, 2006, at 10:40 AM, Adnet Ghislain wrote:
>
> > Hello there.
> >
> >  Just to let you know i have just put in production mode puppet on
> > 41 freeBSD 4.7 virtual servers (yes not real servers but "jailed
> > ones"). I had some little problems with facter at first but i have
> > manualy  upgraded the servers that where affected by the little
> > "facter does not read his facts" problem i had. I should have
> > missed something in my deploiement.
> >
> >  All was fine except some server with very slow responses. Perhaps
> > this is why facter had some issue:
> >
> > notice: Finished configuration run in 1171.60 seconds
> > notice: Finished configuration run in 1905.57 seconds
> > notice: Finished configuration run in 1843.25 seconds
> > notice: Finished configuration run in 2371.23 seconds
> >
> > The recipes i use on those box are quite simple and most of the
> > time it takes only 10-20 seconds.
> > i had no errors at all and all went fine, i used ruby ssh module to
> > launch the commands and setup the beast.
>
> Ouch, those are unreasonably long runs.  You aren't seeing this most
> of the time, then?
>
> I've always been somewhat concerned that there might be performance
> problems for large networks or large configurations, but I haven't
> heard any significant problems so far.
>
> If you continue having very slow runs, I'd like to try to figure out
> what's taking so long.  It could be the packaging, but I don't
> remember if FreeBSD package operations tend to be slow -- if they do,
> then you could schedule them to happen only daily, instead of every run.
>
> > all is ok now  so i hope my life will be better now :)
> > Thanks Luke for the product !
>
> Great, I'm glad to hear everything is working well to make your life
> easier.
>
> --
> Luke Kanies
> http://madstop.com

I have to ask: Is anyone running puppet in a large environment? i.e.
between 100 and 1000 hosts?

While I have toyed with puppet in a small lab environment, I'd hate to
start seeing scaling issues once I'd deployed to only 10% of my
install base.

regards

matthew
Matt Palmer | 3 Oct 05:59 2006

Re: 41 server under puppet today

On Tue, Oct 03, 2006 at 10:32:53AM +1000, Matthew Flanagan wrote:
> I have to ask: Is anyone running puppet in a large environment? i.e.
> between 100 and 1000 hosts?

I'd probably have that many running around by now.  No issues with
increasing size, either technical or social, thus far.

- Matt
Adnet Ghislain | 3 Oct 10:19 2006

Re: 41 server under puppet today


Ouch, those are unreasonably long runs. You aren't seeing this most of the time, then? I've always been somewhat concerned that there might be performance problems for large networks or large configurations, but I haven't heard any significant problems so far.
is there any way to "profile" the things or to have puppet print some time information after each actions in the output of the logs so we can see which parts are taking time ?
those servers are limited in ressources and ruby is quite slow to startup and memory ungry  at least this is what it seems when i look at ps and top output :)

regards,
Ghislain.
Attachment (smime.p7s): application/x-pkcs7-signature, 4221 bytes
_______________________________________________
Puppet-users mailing list
Puppet-users <at> madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
José González Gómez | 3 Oct 10:32 2006
Picon

Re: 41 server under puppet today



2006/10/3, Matt Palmer <mpalmer <at> hezmatt.org>:
On Tue, Oct 03, 2006 at 10:32:53AM +1000, Matthew Flanagan wrote:
> I have to ask: Is anyone running puppet in a large environment? i.e.
> between 100 and 1000 hosts?

I'd probably have that many running around by now.  No issues with
increasing size, either technical or social, thus far.

I'm curious about this, do they run from the same puppet server? Have you seen any type of scaling issue there? I've been thinking about the possibility of having kind of a tree setup, where you have a puppet "metaserver" (a puppet server able to configure child puppet servers) and then a number of puppet servers with their corresponding clients... what do you think of this?

Best regards
Jose
_______________________________________________
Puppet-users mailing list
Puppet-users <at> madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
Matthew Palmer | 3 Oct 12:03 2006

Re: 41 server under puppet today

On Tue, Oct 03, 2006 at 10:32:53AM +0200, José González Gómez wrote:
> 2006/10/3, Matt Palmer <mpalmer <at> hezmatt.org>:
> >
> >On Tue, Oct 03, 2006 at 10:32:53AM +1000, Matthew Flanagan wrote:
> >> I have to ask: Is anyone running puppet in a large environment? i.e.
> >> between 100 and 1000 hosts?
> >
> >I'd probably have that many running around by now.  No issues with
> >increasing size, either technical or social, thus far.
> 
> I'm curious about this, do they run from the same puppet server?

Yes.

> Have you seen any type of scaling issue there?

"No issues with increasing size, either technical or social, thus far."

> I've been thinking about the possibility of having kind of a tree setup,
> where you have a puppet "metaserver" (a puppet server able to configure
> child puppet servers) and then a number of puppet servers with their
> corresponding clients... what do you think of this?

You'll probably have to have separate CAs, and you'll lose a lot of the
advantages of object export and collection.  There's also the issue of
getting the manifests out to all of the "end" servers, although that's
pretty simple to solve.

- Matt

--

-- 
"You keep using that word.  I do not think it means what you think it means."
	-- Inigo, The Princess Bride

Gmane