Hi John,
On 04/13/2011 05:47 PM, jcbollinger wrote:
> Given my position that the good use cases for parameterized classes
> are specialized and few, I tend to agree about different uses. That
> parameterized and ordinary classes are different concepts appears to
> be more a de facto result than a
On 14/04/11 06:26, Giovanni Bordello wrote:
> I wonder if there is an easy way to change variables in the standard
> linux config files in /etc/sysconfig/* on RHEL or /etc/defaults/* on
> Debian.
>
> For instance I would like to set the host name in /etc/sysconfig/network
> with something like:
>
A lot of new options, congrats for the work. :)
Silviu
On 14.04.2011 06:53, Nigel Kersten wrote:
We're very excited to announce the first release candidate of a new
feature release, Puppet 2.7.0rc1, known up until know by the code name
"Statler".
There’s a lot here to read, and we’re covering
On 04/14/2011 12:41 PM, Brian Gupta wrote:
> Congratulations on this long awaited and momentous release. As a
> community member that "would prefer we stay on a GPLv2 or later
> license.", I have severe mixed feelings.
>
> On one hand I strongly respect all the work and code you (and your team)
>
i need link for download puppet for windows xp
regards
vijay
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubsc
Hi there,
Just started using Puppet since yesterday, so a totally newbie
question. I tried to search the answer by myself but none of the
suggestions actually worked. This is how my "modules" is laid:
|-- modules
| |-- mySudo
| | |-- files
| | | `-- sudoers
| | `-- manifests
|
On 04/14/2011 11:36 AM, Sans wrote:
> Hi there,
>
> Just started using Puppet since yesterday, so a totally newbie
> question. I tried to search the answer by myself but none of the
> suggestions actually worked. This is how my "modules" is laid:
>
>
> |-- modules
> | |-- mySudo
> | | |--
The package.pp file looks like this :
# Define a slackware package
define slpackage($package) {
file {
"/var/lib/slackware-packages/${package}":
ensure => file,
owner => root,
group => root,
Thanks Felix, for your reply.
I found this rather confusing. Just after posing my question, I
figured out that the ACTUAL problem was with file (i.e. sudoers)
ownership, not the path. For puppetmaster to be able to copy the file
to the client, the file must be readable by "puppet_user", which is
n
On 04/14/2011 03:00 PM, Sans wrote:
> Thanks Felix, for your reply.
>
> I found this rather confusing. Just after posing my question, I
> figured out that the ACTUAL problem was with file (i.e. sudoers)
> ownership, not the path. For puppetmaster to be able to copy the file
> to the client, the fi
On Apr 14, 2:24 am, Felix Frank
wrote:
> Hi John,
>
> On 04/13/2011 05:47 PM, jcbollinger wrote:
[...]
> > For instance, perhaps you
> > have a user::virtual class that on some nodes declares virtual LDAP
> > users, but on other nodes delares the same virtual users as local.
> > Such a class
Here is one idea I've had and tested ... but it has some obvious
drawbacks which I'll detail ... still wondering if there are others.
On the ca_server I did: puppetca --generate client
I then copied the following generated files:
ssl/private_keys/client.pem (certA)
ssl/ca/signed/client.pem (cert
On Thu, Apr 14, 2011 at 4:31 PM, Jake - USPS wrote:
> Also, what is foreman and how could it help. Not familiar with that
> product.
>
>
Foreman takes care for the entire process, things like provisioning, class
assignments and reportings are all done though it (and many many other
features).
se
Thanks for the reply. I'm just starting to understand puppet, so I
would like not to mess with that ... yet. It does look very
interesting though, so thanks for bringing that up.
Derek,
Thanks for the bug. That looks like it includes some things that I
would like ... like the allow duplicate c
Nevermind, looks like its in 2.7.0rc1
http://groups.google.com/group/puppet-users/browse_thread/thread/b3b50d3c4e449a60
cb01221 (#3360) Add an allow_duplicate_certs option
On Apr 14, 8:45 am, Jake - USPS wrote:
> Thanks for the reply. I'm just starting to understand puppet, so I
> would like n
Hello,
I'm using the following call in my default profile:
notify { "development":
message => "Puppet environment development",
loglevel => " info";
}
with similar entries in other environments.
This works as expected with one exception, the way
I saw this feature became available in 2.7.0rc1 and wanted to try it
out. I entered 'allow_duplicate_certs = true' on both my master and
agent systems in the puppet.conf (not sure if its need in both, saw it
in genconf for puppetd and puppetmasterd though ...). I also have
autosign.conf configure
On Thu, Apr 14, 2011 at 12:24 AM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> Hi John,
>
> On 04/13/2011 05:47 PM, jcbollinger wrote:
> > Given my position that the good use cases for parameterized classes
> > are specialized and few, I tend to agree about different uses. That
> > par
On Apr 14, 2011, at 3:41 AM, Brian Gupta wrote:
> Congratulations on this long awaited and momentous release. As a community
> member that "would prefer we stay on a GPLv2 or later license.", I have
> severe mixed feelings.
>
> On one hand I strongly respect all the work and code you (and your
jcbollinger:
> 1) The "include" statement expresses a requirement that the specified
> class be included in the resulting catalog, but it says nothing about
> the class's parameters.
>
> 2) If a class is named in at least one "include" statement that is
> executed while compiling a catalog, then t
I just recently learned about Puppet and was wondering if someone
could tell me if this would be a good fit for our environment.
We have 3 web servers (and will soon have 4). Here's the steps I
currently use to deploy:
# log on to production web server 1
> service httpd stop
> service tomcat5 st
Much to our chagrin we realized we missed an important new feature in
the release email last night - Network Management.
Based on an open-space discussion that happened at PuppetCamp EU in May
2010 Brice Figureau has implemented the start of a network management
solution. It's very early days for
Jake,
Can you please try the following step and see if these allows you to use
duplicates certs?
On your Puppet Master node:
- Stop the Puppet Master daemon.
- Restart your Puppet Master as follows:
puppet master --allow_duplicate_certs --certdnsnames="puppet:$(hostname
-s):$(hostname -f)" -
I'm looking to create a package provider. We have puppet installed in
a non-standard location
/puppet/puppet/*
The only way I can test the provider is putting the new provider on
the server and restarting puppet on the client. So a few questions.
Is there a way to install it locally so I don't h
On Thu, Apr 14, 2011 at 7:35 AM, JohnW wrote:
> Hello,
>
> I'm using the following call in my default profile:
>
>notify { "development":
>message => "Puppet environment development",
>loglevel => " info";
>}
>
> with similar entries in other envi
I can give that a try ... does that mean I wouldn't be able to use
passenger like I currently am to get this to work?
I'll let you know of my results shortly.
Regards,
Jake
On Apr 14, 11:35 am, Dominic Maraglia wrote:
> Jake,
>
> Can you please try the following step and see if these allows you
Here is the output:
eagnmnmbpe20:/etc/puppet # puppet certificate generate `hostname` --ca-
location remote --server eagnmnmbpe26.usps.gov --masterport 9443
notice: /Whit[completed_/etc/puppet/ssl]: Triggered 'refresh' from 1
events
notice: /Whit[completed_/etc/puppet/ssl/private]: Triggered 'refr
Jake,
We are investigating additional uses cases for "allow_duplicate_certs"
functionality; stay tuned for more information on this topic.
In the meantime, we'd be very interested in your test results and a bit
of information about your platform would be much appreciated at well.
Cheers,
D
Test results posted, you may have posted shortly after I did. ;)
We are using SLES 10. I'm not exactly sure what other information you
want ... here is some of the relevant packages we have installed:
usps-augeas-0.7.4-1.sles10
usps-ruby-gem-test-unit-2.1.2-1.sles10
usps-ruby-augeas-0.3.0-1.sle
Jake
The behavior in 2.7 when running the master with
--allow_duplicate_certs set is the same as in 2.6.x in that you can
manually (using something like curl or the new 'puppet certificate'
face) generate multiple certs with same CN name, but the agent errors
the same way regardless of the puppet v
Good people ~
I'm running through the Puppet DSL trying to understand it. Some
parts seem a little funky, like "import." Before I start forming any
silly opinions, tell me: what do you use "import" for? Does it serve
that purpose well, or do you grimace a little every time you type it?
Thanks
I use it to include files which, for whatever reason, won't be auto-imported.
Specifically, I use it to includes my nodes.pp and defines.pp files, since
neither of them define any classes, and I want my defines all in one place,
usable anywhere.
On Apr 14, 2011, at 11:05 AM, Randall Hansen wro
Thanks Matt. Just for clarification on why I'm trying to do this. We
often rebuild systems in our environment. Things are
'decommissioned', hostname 'released' and new system built with
previously used hostname for new purposes. This means currently (as I
understand it) part of our decom proces
I'd like to use Facter to determine how many cores or processors are
available and edit a property file accordingly. I run it on my Mac and get
sp_number_processors and on my Centos box, get processorcount.
Both are using facter 1.5.8
David
--
You received this message because you are subscribed
I wanted to test out running puppet under Passenger and setup a new
puppetmaster (brm-up-puppet-2) box to test on. I was seeing some
very odd error back from clients when testing:
err: Could not retrieve catalog from remote server: SSL_connect
returned=1 errno=0 state=SSLv3 read server certifica
Matt Robinson wrote:
> This release addresses issues with the Puppet 2.6.x series.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing.
Add the puppet.repo file from
On Thu, Apr 14, 2011 at 14:16, David Kavanagh wrote:
> I'd like to use Facter to determine how many cores or processors are
> available and edit a property file accordingly. I run it on my Mac and get
> sp_number_processors and on my Centos box, get processorcount.
> Both are using facter 1.5.8
H
Although I don't know the answer I'm curious as to why you're worried about
using HTTPS when you're sending the reports locally? There is no need to
encrypt the ports if you're just sending them to the same machine /
localhost.
--
You received this message because you are subscribed to the Goo
Any chance to address #6845 in this release (patch already sent to
puppet-dev)? The mountprovider is currently not working at all on
Solaris (the title »mount tmpfs on Solaris fail« is misleading).
-Stefan
On Wed, Apr 13, 2011 at 05:57:38PM -0700, Matt Robinson wrote:
> This release addresses iss
Also, watch out for casing of your module name. It appears that
'mySudo' works, but it is not recommended.
Recommended naming for Modules (and Classes): [a-z][a-z0-9]*
http://docs.puppetlabs.com/guides/modules.html#naming
I was caught by this issue when I named a module in a camel-cased
fashion:
Stefan Schulte wrote:
> Any chance to address #6845 in this release (patch already sent to
> puppet-dev)? The mountprovider is currently not working at all on
> Solaris (the title »mount tmpfs on Solaris fail« is misleading).
>
Stefan
I've been talking to Nigel. Answer shortly/tomorrow.
James
FWIW, I happened to try on OS X, but our target is many different linux
distros. As long as there's some consistency across those. Oh, soon, we'll
be supporting Windows server as well.
David
On Thu, Apr 14, 2011 at 6:20 PM, Daniel Pittman wrote:
> On Thu, Apr 14, 2011 at 14:16, David Kavanagh w
On Thu, Apr 14, 2011 at 4:41 PM, James Turnbull wrote:
> Stefan Schulte wrote:
>> Any chance to address #6845 in this release (patch already sent to
>> puppet-dev)? The mountprovider is currently not working at all on
>> Solaris (the title »mount tmpfs on Solaris fail« is misleading).
>>
>
> Stefa
Sure. but if you already configured access to puppetmaster on HTTPS,
it would be nice to use it, instead of adding and maintaining another
setup for HTTP access.
On Thu, Apr 14, 2011 at 6:54 PM, Cody Robertson wrote:
> Although I don't know the answer I'm curious as to why you're worried about
>
Has anyone implemented a kind of authorization framework in front of
puppet dashboard? Shibboleth is used extensively in our environment to
secure web applications and the like. Are there methods in place to
allow dashboard to continue to function (receiving reports, etc)
properly with some kind of
On 14/04/11 20:04, Dominic Cleal wrote:
> On 14/04/11 06:26, Giovanni Bordello wrote:
>> I wonder if there is an easy way to change variables in the standard
>> linux config files in /etc/sysconfig/* on RHEL or /etc/defaults/* on
>> Debian.
>>
>> For instance I would like to set the host name in /e
On Apr 14, 2011, at 3:54 PM, Cody Robertson wrote:
> Although I don't know the answer I'm curious as to why you're worried about
> using HTTPS when you're sending the reports locally? There is no need to
> encrypt the ports if you're just sending them to the same machine / localhost.
In my cas
My point exactly for now, though there are reasons to send reports over HTTPS
that I mentioned in my response.
On Apr 14, 2011, at 7:19 PM, Mohamed Lrhazi wrote:
> Sure. but if you already configured access to puppetmaster on HTTPS,
> it would be nice to use it, instead of adding and maintaining
On Apr 14, 2011, at 11:57 AM, Jake - USPS wrote:
> Thanks Matt. Just for clarification on why I'm trying to do this. We
> often rebuild systems in our environment. Things are
> 'decommissioned', hostname 'released' and new system built with
> previously used hostname for new purposes. This me
49 matches
Mail list logo
