Re: [Puppet Users] undefined method `include?' for nil:NilClass
master and client using the same version On Wednesday, July 30, 2014 12:02:22 AM UTC+8, Gabriel Filion wrote: Hey there, On 29/07/14 01:11 AM, Peter Romfeld wrote: Hi, I don't know if it was exactly the same error but I was having something similar when using a puppet 2.7 client with a 2.6 master. make sure your client is not using a more recent version than your master. I get the following error: # puppet agent --trace -t info: Retrieving plugin info: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rb info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb info: Loading facts in /var/lib/puppet/lib/facter/puppi_projects.rb info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb info: Loading facts in /var/lib/puppet/lib/facter/last_run.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:168:in `is_http_200?' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:101:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:195:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:239:in `retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:509:in `thinmark' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:508:in `thinmark' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:238:in `retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:86:in `retrieve_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:112:in `retrieve_and_apply_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:152:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:43:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:23:in `lock' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:43:in `run' /usr/lib/ruby/1.8/sync.rb:230:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:43:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:95:in `with_client' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:41:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:172:in `call' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:172:in `controlled_run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:339:in `onetime' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:313:in `run_command' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:416:in `hook' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:407:in `exit_on_fail' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:69:in `execute' /usr/bin/puppet:4 err: Could not retrieve catalog from remote server: Error 400 on SERVER: undefined method `include?' for nil:NilClass on node warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run I tried to remove the ssl certs on master and agent and resigned a new one, but i get still this error. Other Instances are working just fine, I only have this error on one Instance so far # puppet --version 2.7.23 -- Gabriel Filion -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/2cb2fd9f-fb20-4a63-b06d-1679d3ca1dc2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] undefined method `include?' for nil:NilClass
Hi, I get the following error: # puppet agent --trace -t info: Retrieving plugin info: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rb info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb info: Loading facts in /var/lib/puppet/lib/facter/puppi_projects.rb info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb info: Loading facts in /var/lib/puppet/lib/facter/last_run.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:168:in `is_http_200?' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:101:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:195:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:239:in `retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:509:in `thinmark' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:508:in `thinmark' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:238:in `retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:86:in `retrieve_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:112:in `retrieve_and_apply_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:152:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:43:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:23:in `lock' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:43:in `run' /usr/lib/ruby/1.8/sync.rb:230:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:43:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:95:in `with_client' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:41:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:172:in `call' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:172:in `controlled_run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:339:in `onetime' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:313:in `run_command' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:416:in `hook' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:407:in `exit_on_fail' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:69:in `execute' /usr/bin/puppet:4 err: Could not retrieve catalog from remote server: Error 400 on SERVER: undefined method `include?' for nil:NilClass on node warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run I tried to remove the ssl certs on master and agent and resigned a new one, but i get still this error. Other Instances are working just fine, I only have this error on one Instance so far # puppet --version 2.7.23 Cheers, Peter -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/2aa026aa-7a0f-49fd-b04b-bc0c59622a4c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Facter on Amazon AMI with ruby2
Hi, I have problems to get facter running: OS: Amazon Linux AMI release 2014.03 Ruby: ruby 2.0.0p451 (2014-02-24 revision 45167) [x86_64-linux] I tried the amz provided facter package and also facter2.1 from puppetlabs repo, with both I have the same problem: /usr/share/ruby/vendor_ruby/2.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- facter/application (LoadError) from /usr/share/ruby/vendor_ruby/2.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/bin/facter:18:in `main' On other machines I can just reinstall ruby and use 1.8, but on one machine I have something else running that requires ruby2 Cheers, Peter -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/53C61C03.9090200%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] EC2 autoscaling reusing hostnames
hey, if you dont use cross aws/datacenter and only aws i would recommend to use use ops-works.. its chef based but for aws only its quite nice On Sunday, May 25, 2014 11:21:20 AM UTC-7, Jakov Sosic wrote: Can you somehow get list of active nodes from balancer? You could use that list in a daily cron to do a 'puppet cert clean' and remove all other certificates? I can get a list of active nodes in the constellation, the instances in the constellation have a constant embedded in the instance name that tells which constellation they belong to. That's how my Nagios instance works after all -- it queries AWS for the list of active nodes and reconfigures Nagios to look at the active nodes. Otherwise Nagios would be completely out of date after the first scaling event. I'm somewhat reluctant to embed AWS credentials into the puppetmaster though. The other thing that someone mentioned in another forum was to look for nodes reporting in the reports directory, and if a node hasn't reported for over an hour (mine are checking in every twenty minutes at a minimum so should have checked in by then) to do a 'puppet cert clean' on that node and then a 'puppet certificate_revocation_list destroy' just in case it comes back to life and checks in again. The other thing mentioned has been to change the hostname of the instances as part of their cloud_init stage to add the instance ID as well as the IP address as the hostname. That would actually work fairly well, I suspect, since the chance of both instance ID *and* the IP address being reused for the same instance are pretty much non-existent, and also gives me more information on my Splunk server about what Splunk event applies to what instance,but will require a lot of time to debug on my part because the only way to debug it is to run Cloudformation time... after... time... after... time... creating and destroying constellations until I get it right. I don't want to go to master-less configuration because I tweak constellations before rolling them into production, and it's easier to do that via a configuration master. For example, new constellations start out pointed at a testing database, and one of the things that happens when they're moved into production is that they get re-pointed at the production database. I might try migrating to a different configuration tool such as Chef in the future, but I have limited time to devote to this project. So right now the priority is just forcing Puppet to work the way it needs to work in the cloud, rather than the way the Puppet authors believe it should work, which is completely incompatible with cloud ops. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com mailto:puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/80ef1916-4434-4405-a357-62345d111618%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/80ef1916-4434-4405-a357-62345d111618%40googlegroups.com?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5384C4BA.9070704%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: continued deployment
Thanks for your answer! I read this book yesterday :) Right now I am adding logstash to my puppet config. Next I need to figure out the most fitting automated testing. It will be for a ejabberd/erlang plugin. Cheers, Peter On Mon, Feb 17, 2014 at 8:01 PM, JuanBrein juan.br...@gmail.com wrote: Have you read Continuous Delivery from Jez Humble? Is a great starting point covering main aspects. Look in youtube as well, there are plenty of videos from people implementing continuous delivery. Technology wise it is so wide that is difficult to find a single recipe. If you detail a bit more about your stack I could give you some hints. Now you mentioned continuous deployment and that as far as I understand is kind of a new area. If you are new to it you should first aim for continuous Delivery and then think on Continuous Deployment. Juan On Sunday, February 16, 2014 12:06:16 PM UTC, Peter Romfeld wrote: Hi, I got most of our infrastructure managed with puppet now. Now i want to learn about continued app deplyment with puppet.. So far my noob knowledge is I would use: manage directory recursive - notify exec command You have some some links or catchwords(google) for me to do this the proper way? Thanks, Peter -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/8e72e7e0-c207-4628-bfaf-ba2008443f38%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAKiz-NdLCBaY_V%2BR8B1C0EhUyDBSURX3%3DrKctiUcR7bwOzv4RQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] continued deployment
Hi, I got most of our infrastructure managed with puppet now. Now i want to learn about continued app deplyment with puppet.. So far my noob knowledge is I would use: manage directory recursive - notify exec command You have some some links or catchwords(google) for me to do this the proper way? Thanks, Peter -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAKiz-NcHF2m7RMYCQ0gKuA6a%3DemnUqfnkKMign4h5vReu5BS6Q%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Complex search on StoreConfigs resources is not supported
HI, I got the Error: Error 400 on SERVER: Complex search on StoreConfigs resources is not supported I cant find any information on this and dont know what could cause it. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAKiz-NcX-SSvi04BnADT3wNUfefxZL8%2B%3D%2BOx%3DnaMpch1EXUCgA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] problem with File[path]
hi,
i get the following error:
Parameter path failed on File[${nagiospluginsdir}/${pname}]: File paths
must be fully qualified, not '${nagiospluginsdir}/${pname}'
plugin.pp:
define nrpeplugins::plugin(
$nagiospluginsdir = $nrpeplugins::params::nagiospluginsdir,
$nrpepluginsdir = $nrpeplugins::params::nrpepluginsdir,
$nrpeservice = $nrpeplugins::params::nrpeservice,
$pname = $title
) {
file { '${nrpepluginsdir}/${pname}.cfg':
# file { 'newnrpe':
#path = '${nrpepluginsdir}/${pname}.cfg',
ensure = file,
owner = root,
group = root,
mode = '0644',
content = template('nrpeplugins/nrped.erb'),
notify = Service['${nrpeservice}']
}
file { '${nagiospluginsdir}/${pname}':
# file { 'newscript':
#path = '${nagiospluginsdir}/${pname}',
ensure = file,
owner = root,
group = root,
mode = '0755',
source = 'puppet:///modules/nrpeplugins/${pname}'
}
}
thanks,
peter
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAKiz-NeK2sHR7oCNdybEwxbwKx0M0n5bfk1mf%2BHnxScoq3bUHQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] problem with File[path]
wow thanks so much for the fast answer!
im used from python that single or double quote means the same :)
On Thu, Feb 6, 2014 at 12:47 PM, Peter Bukowinski pmb...@gmail.com wrote:
On Feb 5, 2014, at 11:39 PM, Peter Romfeld peter.romfeld...@gmail.com
wrote:
hi,
i get the following error:
Parameter path failed on File[${nagiospluginsdir}/${pname}]: File paths
must be fully qualified, not '${nagiospluginsdir}/${pname}'
plugin.pp:
define nrpeplugins::plugin(
$nagiospluginsdir = $nrpeplugins::params::nagiospluginsdir,
$nrpepluginsdir = $nrpeplugins::params::nrpepluginsdir,
$nrpeservice = $nrpeplugins::params::nrpeservice,
$pname = $title
) {
file { '${nrpepluginsdir}/${pname}.cfg':
# file { 'newnrpe':
#path = '${nrpepluginsdir}/${pname}.cfg',
ensure = file,
owner = root,
group = root,
mode = '0644',
content = template('nrpeplugins/nrped.erb'),
notify = Service['${nrpeservice}']
}
file { '${nagiospluginsdir}/${pname}':
# file { 'newscript':
#path = '${nagiospluginsdir}/${pname}',
ensure = file,
owner = root,
group = root,
mode = '0755',
source = 'puppet:///modules/nrpeplugins/${pname}'
}
}
thanks,
peter
You're getting the error because you've used single quotes in the file
definition. If you want puppet to interpret variables when it compiles the
catalog, you must use double quotes.
--
Peter Bukowinski
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/A2EE8146-86B7-4184-8C0D-919982890F0B%40gmail.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAKiz-NfZLtDOAufk3sgJ%3DvPmCrmXpU0c1GBxSWA%3DQv%3Dks4fh-g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] circular dependency between user/home and parent directory owned by that user
hi, im still new to puppet, but from linux logic cant you just first ensure
file is there with (deployment)-group permissions - create user (with same
group) - change permissions
On Fri, Jan 31, 2014 at 12:51 AM, David Portabella
david.portabe...@gmail.com wrote:
again,
it is a circular dependency.
what you are saying is to first create user and then file.
but to create the user, we need the file first also.
On Thursday, January 30, 2014 5:31:10 PM UTC+1, Arpin Dominique (Nter)
wrote:
Hi,
Simple :
User['david']-File['/haha']
Ref: http://docs.puppetlabs.com/learning/ordering.html
*Dominique Arpin*
Tél. Interne: 140-4156
Tél. 514 285.2929 Poste: 140-4156
*De :* puppet...@googlegroups.com [mailto:puppet...@googlegroups.com] *De
la part de* David Portabella
*Envoyé :* 30 janvier, 2014 11:28
*À :* puppet...@googlegroups.com
*Objet :* [Puppet Users] circular dependency between user/home and
parent directory owned by that user
For illustrating purposes,
I need a *david* user with home directory /haha/david,
and at the same time, the directory /haha also needs to be owned by
*david*.
this code does not work,
because user requires the /haha directory, and the /haha directory
requires the david user,
so we have a circular dependency,
and it seems that puppet does not know how to handle this.
user {'david':
ensure = present,
home= '/haha/david',
managehome = true
}
file {'/haha':
ensure = directory,
owner = 'david'
}
how to solve this?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/puppet-users/da03b929-db57-4964-acf9-060beec69d2c%
40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Mise en garde concernant la confidentialité : Le présent message,
comprenant tout fichier qui y est joint, est envoyé à l'intention exclusive
de son destinataire; il est de nature confidentielle et peut constituer une
information protégée par le secret professionnel. Si vous n'êtes pas le
destinataire, nous vous avisons que toute impression, copie, distribution
ou autre utilisation de ce message est strictement interdite. Si vous avez
reçu ce courriel par erreur, veuillez en aviser immédiatement l'expéditeur
par retour de courriel et supprimer le courriel. Merci!
Confidentiality Warning: This message, including any attachment, is sent
only for the use of the intended recipient; it is confidential and may
constitute privileged information. If you are not the intended recipient,
you are hereby notified that any printing, copying, distribution or other
use of this message is strictly prohibited. If you have received this email
in error, please notify the sender immediately by return email, and delete
it. Thank you!
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/021d8313-7665-44d3-82fd-fe9be08490c9%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAKiz-NfFhE-cq0QtUWCzD1puRxRg7v4qgOZGVRhGNubmKDF0gA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] dynamic /etc/hosts
yes. I have a cluster where all nodes must use hostnames, so we use /etc/hosts. I want to configure autoscaling for this cluster, but my biggest problem is the hosts file, so when a new node comes up all other nodes need to be notify that the hosts file changed, so the make pull the new file. Thanks for help, Peter -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAKiz-NfPesJ_a7QdasOF74iP4uYgmZm7TQmbQqCO-KY4gA3h%3DA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] dynamic /etc/hosts
well in the end i would have to add dns healthchecks too to the node spawning. The puppet /etc/hosts approach just looked nice and easy. I am on Amazon AWS, but i should be able to to it with nagios and some scripts On Tue, Jan 21, 2014 at 2:41 PM, Dirk Heinrichs d...@recommind.com wrote: Am 21.01.2014 03:37, schrieb Peter Romfeld: I have a cluster where all nodes must use hostnames, so we use /etc/hosts. I want to configure autoscaling for this cluster, but my biggest problem is the hosts file, so when a new node comes up all other nodes need to be notify that the hosts file changed, so the make pull the new file. Opposed to what Felix is thinking, my previous message was meant seriously. I don't see a trivial solution to your problem that involves Puppet and /etc/hosts. You'd need to: 1) Have the new node update the hosts file that Puppet delivers. What is two noeds come up at the same time? You'd need proper locking. 2) Puppet agents only run every 30 minutes, so you'll have a delay until all other nodes know the new one. 3) What happens when a node goes down? OTOH, what you want to do can be achieved with DHCP and DNS, such that the DHCP server updates DNS when a new client comes up. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com *Skype*: dirk.heinrichs.recommind www.recommind.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52DE1692.1060703%40recommind.com . For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAKiz-NcgayC4_RZHmBDsPqueE-8hT1HaUk8MftfjNxOmKKzULQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out. Logo.gif
[Puppet Users] dynamic /etc/hosts
Hi, I just started learning puppet, and still have problems understanding the advanced puppet language. I am using the puppet example42/hosts module to have a dynamic /etc/hosts file. Its working fine so far but i have one more requirement, i need to force update on all other nodes if one node changes or get added. Thanks, Peter -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAKiz-NeLF2tqATrJjbDDFYB9SbEWFjyZ27E3kMK9K9tx%2BJAOag%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] hiera
Hi, I just started learning puppet a few days ago.. I finished eBook Pro Puppet all the puppet e-courses and read quite a bunch about roles and so on... What i have not found so far is a Hiera tutorial I understand, i read through puppetlabs docu but i dont understand it. Maybe i should just start without hiera and after some useage it get clear to me.. But maybe there is a hiera tutorial for noobs? Cheers, your just-started-puppet-noob -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAKiz-Ne%3DKRZxJxTh1zUp2Pg55iyQnHJJQLhbfx6Ke%2BTsgpcxqw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
