Hi Florian,
Interesting post. I was planning the same sort of approach for apache
vhosts with hiera and create_resources. This is good proof that the
idea works.
Are you using this approach in other modules as well, if so which?
Regards,
Martin
2012/3/16 Gary Larizza g...@puppetlabs.com:
Ahh,
Hi Gary,
I'm trying to start sshd. But the command to start sshd is service ssh
start at least on the prompt line.
If I change it to 'sshd' on the params class it gives me the following
error:
err: /Stage[main]/Ssh::Service/Service[sshd]: Could not evaluate: Could not
find init script for
Yep,
Forgot that Ubuntu uses 'ssh' whereas CentOS uses 'sshd'.
Have you seen this bug --
https://projects.puppetlabs.com/issues/12773 May be appropriate here.
-Gary
On Fri, Mar 16, 2012 at 8:09 PM, Luis Festas Matos lufe...@gmail.comwrote:
Hi Gary,
I'm trying to start sshd. But the command
Hi Martin,
no currently only for the tomcat::instances.
we currently change our modules to hiera, so maybe i find other cases.
rgds Florian
Am Freitag, 16. März 2012 09:03:44 UTC+1 schrieb mawi:
Hi Florian,
Interesting post. I was planning the same sort of approach for apache
vhosts with
On 15 March 2012 22:39, Chris O'Donnell chodo...@gmail.com wrote:
With our current iptables rules, we implement the following in a script:
iptables -P INPUT DROP
iptables -P FORWARD DROP
iptables -P OUTPUT ACCEPT
Then the script continues on and does the rest of the rules. some custom
On Mar 15, 9:44 am, Kolesar asim.husano...@gmail.com wrote:
Hi All,
I'm absolutely beginner on puppet. For now, I have found one bug.
When I create one muster and one node
byhttp://www.youtube.com/watch?v=kBITFtHI8_Uhttp://www.youtube.com/watch?v=KLF1-i8RzGU
I do not view any log on my
The Core Types Cheat Sheet at
http://projects.puppetlabs.com/projects/puppet/wiki/Core_Types_Cheat_Sheet/
says:
The Trifecta
Package/file/service: Learn it, live it, love it. If you can only do this,
you can still do a lot.
package { 'openssh-server':
ensure = installed,
}
file {
Hi Florian. great and smart method. But I've found a problem. If i have a
hash with two dimensions I'm losing the information of the first dimension.
Explained:
yaml:
---
routers:
router1:
ip: 1.2.3.4
ports:
1:
foo: true
bar: false
2:
Figured this one out finally.
Some background first: The system in question is running the ISPManager
control panel is and is my shared hosting platform. I mention that because
apparently during the installation of ISPManager there are repos added to
the repo list by the ISPManager installer and
On Fri, Mar 16, 2012 at 9:21 AM, jimbob palmer jimbobpal...@gmail.com wrote:
The Core Types Cheat Sheet at
http://projects.puppetlabs.com/projects/puppet/wiki/Core_Types_Cheat_Sheet/
says:
The Trifecta
Package/file/service: Learn it, live it, love it. If you can only do this,
you can
On Mar 16, 2012, at 10:21 AM, jimbob palmer wrote:
The Core Types Cheat Sheet at
http://projects.puppetlabs.com/projects/puppet/wiki/Core_Types_Cheat_Sheet/
says:
The Trifecta
Package/file/service: Learn it, live it, love it. If you can only do this,
you can still do a lot.
On 16.3.2012 15:21, jimbob palmer wrote:
The Core Types Cheat Sheet at
http://projects.puppetlabs.com/projects/puppet/wiki/Core_Types_Cheat_Sheet/
says:
The Trifecta
Package/file/service: Learn it, live it, love it. If you can only do
this, you can still do a lot.
|package {
Would anyone please assist me on this one? This fact seems to work, but it
doesn't return when called directly via facter --puppet noop, but the
resulting facts end up in the reports.
I'm at wits end with this. Thanks!
snip
utc_hour = Facter::Util::Resolution.exec(%q/bin/date -u +%H).chomp
Hi all,
I am trying to understand how does hiera puppet backend work, so I created the
following example:
hiera.yaml has only:
---
:backends:
- puppet
---
And the node:
node 'testnode' {
$variable = 'kk'
$thing = hiera (variable)
notify { note: $thing: }
}
I
Try to add the 2 lines below inside your virtualhost
VirtualHost *:3000
SetEnv RAILS_ENV production
RackBaseURI /
...
/VirtualHost
Don't forget to restart apache.
[]s
Felipe
On Mar 9, 6:33 am, theirpuppet theirpup...@gmail.com wrote:
Hello all
Puppet, puppetmaster, ruby,
Hi! Does the following do what you might expect?
fact_name = 'noop'
Facter.add(fact_name) do
setcode do
utc_hour = %x{/bin/date -u +%H}.chomp.to_i
environment = Facter.value(:environment)
#puts env = #{environment}
if environment.match(test|dev|qa)
result = false
else
So far so good. In test environment it actually reports when I run it.
Thank you very much Guy. I'll let you know how it goes in the environments
which actually use noop.
Appreciate the help :)
Jordan
On Friday, March 16, 2012 12:26:23 PM UTC-4, Guy Matz wrote:
Hi! Does the following
I'm having difficulty determining the best course of action how to
implement /etc/resolv.conf on my RHEL5 hosts.
Here's my requirements, IN ORDER OF PRECEDENCE:
* All hosts, regardless of function, need /etc/resolv.conf
* Dependiing upon which environment the host lives in (i.e. Facture
So basically you want to avoid node config customization?
You want an ultimate resolv class which will decide everything without
you defining manually something in the node conf?
On 16 March 2012 16:52, chris_sny...@sra.com chris_sny...@sra.com wrote:
I'm having difficulty determining the best
In regard to: [Puppet Users] Need advice how to architect solution for...:
I'm having difficulty determining the best course of action how to
implement /etc/resolv.conf on my RHEL5 hosts.
Here's my requirements, IN ORDER OF PRECEDENCE:
* All hosts, regardless of function, need
On Friday, March 16, 2012 1:23:16 PM UTC-4, Peter Horvath wrote:
So basically you want to avoid node config customization?
You want an ultimate resolv class which will decide everything without
you defining manually something in the node conf?
What I *want* is this:
node basenode {
hi,
yes better depends on personal preferences
Am Freitag, 16. März 2012 17:27:41 UTC+1 schrieb Jan Ivar Beddari:
On 15. mars 2012 22:06, Florian Koch wrote:
Hi Dennis,
i have found a better solution via create_resources (look at my reply to
Gery)
Not neccessarily better in my mind
On Friday, March 16, 2012 1:36:23 PM UTC-4, Tim Mooney wrote:
In regard to: [Puppet Users] Need advice how to architect solution for...:
I'm having difficulty determining the best course of action how to
implement /etc/resolv.conf on my RHEL5 hosts.
Here's my requirements, IN ORDER OF
Hi,
this sounds this is a job for hiera:
http://puppetlabs.com/blog/the-problem-with-separating-data-from-puppet-code/
http://puppetlabs.com/blog/first-look-installing-and-using-hiera/
rgds Florian
Am Freitag, 16. März 2012 19:12:10 UTC+1 schrieb chris_...@sra.com:
On Friday, March 16, 2012
Hi,
There is also no need to call date from within the shell saving on
unnecessary fork, as Ruby can provide UTC time for you.
More concise version: https://gist.github.com/2051811
KW
On Friday, 16 March 2012 16:51:02 UTC, Jemmorey wrote:
So far so good. In test environment it actually
Julien C. wrote:
The dashboard integration part.
I ended up using yup.puppetlabs.com and it works fine :-)
Good to know. I wonder if the dashboard packages should require
puppet = 2.7.x ?
--
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
Well I've somehow managed to get it down to just the error on the
masterhttp.log file:
Could not prepare for execution: Got 1 failure(s) while initializing:
change from absent to file failed: Could not set 'file on ensure:
Permission denied - /var/log/puppet/masterhttp.log
There's obviously
I should imagine that if you wrote custom facts you'd get what you're
after. If my understanding is correct facts get shipped to the puppet
master as part of the inventory service.
Having said that puppet-dashboard will already show you what is in your
inventory for each node if you have the
On Fri, Mar 16, 2012 at 11:55 AM, Todd Zullinger t...@pobox.com wrote:
Julien C. wrote:
The dashboard integration part. I ended up using yup.puppetlabs.com and it
works fine :-)
Good to know. I wonder if the dashboard packages should require puppet =
2.7.x ?
You should be able to use a
On Mar 16, 2012, at 4:44 PM, Michael Stahnke wrote:
On Fri, Mar 16, 2012 at 11:55 AM, Todd Zullinger t...@pobox.com wrote:
Julien C. wrote:
The dashboard integration part. I ended up using yup.puppetlabs.com and it
works fine :-)
Good to know. I wonder if the dashboard packages
Finally found the answer in this thread:
http://groups.google.com/group/puppet-users/browse_thread/thread/5bc799ee96bf74bd?pli=1
On the puppet master server, /etc/puppet/rack/config.ru was owned by
root:root instead of puppet:puppet. My puppet class isn't enforcing that,
but hmm, that would be a
On 13.3.2012 00:22, vagn scott wrote:
On 03/12/2012 10:16 AM, Peter Bukowinski wrote:
Your master's version should always be equal to or greater than the
latest client version you're using. You can count on a newer master
working with older clients, but don't count on newer clients working
Markus, yes. As long as the master's version is equal to or greater than the
agents, it will work. I can't speak for future master releases, though.
-- Peter (from phone)
On Mar 16, 2012, at 5:42 PM, Markus Falb markus.f...@fasel.at wrote:
On 13.3.2012 00:22, vagn scott wrote:
On 03/12/2012
FYI, I downloaded the following branch this morning:
git clone -b ticket/10162-firewallchain_support_for_merge
git://github.com/kbarber/puppetlabs-firewall.git
and found a bug where the args for iptables were being fed to it in the
wrong order. I made the following patch, and emailed it to
Hi Pablo,
The Puppet backend accepts a 'datasource' parameter whose value will be the
class name for where it will look for Puppet variables. Take my hiera.yaml
for example:
---
:backends: - puppet
:puppet:
:datasource: data
I'm telling it to look for a modulename::data class, and to
HI Chris,
Awesome, +1 :)
KW
On Friday, 16 March 2012 22:09:34 UTC, Chris O'Donnell wrote:
FYI, I downloaded the following branch this morning:
git clone -b ticket/10162-firewallchain_support_for_merge git://
github.com/kbarber/puppetlabs-firewall.git
and found a bug where the args for
36 matches
Mail list logo
