You can also use the ralsh command where the user is created as long
as puppet is installed. The command will spit out the complete user
dsl.
ralsh user student
Also, make sure the password is in single quotes so $ doesn't get
interpreted.
-John
--
You received this message because you a
Hey John,
I've been using environments quite some time with lots of success. I
love the idea of creating a bootstrap environment which I never
thought of.
This gave me an idea to address an issue I'm trying to tackle. A
client s using Puppet for their app setup/deployment. We provide the
sysop
Case 1:
I have gone to a model where I have a manifests/conf directory akin
to /etc which contains the configuration for each service and
application. In your case I would have a zabbix_conf class and in the
node, I would simple reference the var $zabbix_conf::server_ip.
The beauty of this is my
Hi,
This should answer your questions:
http://docs.puppetlabs.com/guides/configuring.html#autosignconf
You can only specify subdomains, not globs like you are trying to do.
Cheers,
Den
On 06/08/2011, at 5:33, newguy wrote:
> Hi guys I want to auto sign the clients coming in, in my autosign.c
On 08/05/2011 02:59 AM, dave-stfu wrote:
Hello
Recently, I've upgraded the Dashboard from 1.2rc3 to 1.2rc5. Now, the
delayed workers are dying right after I start them. The production.log
says:
Delayed::Backend::ActiveRecord::Job Update (0.0ms) Mysql::Error:
MySQL server has gone away: UPDATE
I can confirm the exact same issue.
--
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+unsubscr...@googlegroups.com.
For
Yes, the certname is 'dashboard' :
server:/var/lib/puppet # ll ssl/certs/
total 12
-rw-r--r-- 1 puppet root879 2011-07-07 11:03 ca.pem
-rw-r- 1 puppet root887 2011-08-05 10:05 dashboard.pem
server:/usr/share/puppet-dashboard # puppet cert --list --all
+ dashboard (BD:FC:15:2F:06:7D:43
Hi guys I want to auto sign the clients coming in, in my autosign.conf
file I tried * ( to allow all), it didnt worked, I also tried pattern
like: qa-abc-wrk*.com it also didnt worked.
Client says invalid pattern for qa-abc-wrk*.com.
Can any one please help me with this.
Thanks
--
You received
Hi guys I want to auto sign the clients coming in, in my autosign.conf
file I tried * ( to allow all), it didnt worked, I also tried pattern
like: qa-abc-wrk*.com it also didnt worked.
Client says invalid pattern for qa-abc-wrk*.com.
Can any one please help me with this.
Thanks
--
You received
On Fri, Aug 5, 2011 at 12:22 PM, Claude wrote:
> Using "allow dashboard" in /facts then facter data is not displayed in
> the dashboard (Could not retrieve facts from inventory service: 403
> "Forbidden").
>
Is your certname actually 'dashboard' or did you generate a different
certname?
>
> Al
Using "allow dashboard" in /facts then facter data is not displayed in
the dashboard (Could not retrieve facts from inventory service: 403
"Forbidden").
Also not using * in /file_bucket_file/md5 forbids clients from
uploading bucketed files.
Am I missing something here?
On 5 août, 15:09, Nigel K
On Fri, Aug 5, 2011 at 11:24 AM, Claude wrote:
> I finally made it working by modifying auth.conf like this :
>
> path /facts
> auth any
> method find, search
> allow *
>
> path /file_bucket_file/md5
> auth no
> method find, save
> allow *
>
That's going to allow everyone, and you really should
I finally made it working by modifying auth.conf like this :
path /facts
auth any
method find, search
allow *
path /file_bucket_file/md5
auth no
method find, save
allow *
On 5 août, 09:31, Nigel Kersten wrote:
> On Fri, Aug 5, 2011 at 5:14 AM, Claude wrote:
> > Here's what the log shows :
>
>
On 08/05/2011 01:18 PM, jcbollinger wrote:
On Aug 5, 9:38 am, vagn scott wrote:
I think one could make a case for getting rid of global variables entirely.
Sort of. There are alternatives that could fill the same role, such
as class variables of a class that every node includes, s
On Aug 5, 3:25 am, Thomas Rasmussen
wrote:
> Hi
>
> Thanks for the reply, that works, but I'd like to keep my include of
> the sudoers::config in my default node section, but if I do that, then
> I don't have the $sudoenv variable available at that time.
>
> Is there any way of overriding a prev
We completed a number of tasks that allow us to run the facter and spec
tests on Windows as part of our continuous integration system[1]. All of
the tests now pass on Windows Server 2008 R2, with exception of tests
that are marked as fails_on_windows. These tests are known to fail
because we have n
On Aug 5, 9:38 am, vagn scott wrote:
> I think one could make a case for getting rid of global variables entirely.
Sort of. There are alternatives that could fill the same role, such
as class variables of a class that every node includes, so yes, you
could dump global variables themselves, bu
vagn scott:
> I think one could make a case for getting rid of global variables
> entirely.
Functionally, this is common advice for avoiding the pitfalls of
puppet's peculiar dynamic scope. Newcomers are often advised to use
$::foo::bar::baz to avoid picking up data from unexpected places in the
Hello
Recently, I've upgraded the Dashboard from 1.2rc3 to 1.2rc5. Now, the
delayed workers are dying right after I start them. The production.log
says:
Delayed::Backend::ActiveRecord::Job Update (0.0ms) Mysql::Error:
MySQL server has gone away: UPDATE `delayed_jobs` SET locked_by =
null, locke
On Aug 5, 8:33 am, Nigel Kersten wrote:
> We have a bunch of problems people regularly run into with node inheritance,
> and it's something we'd like to find a better solution for.
>
> Is anyone using node inheritance and happy with how it works? If so, can you
> describe your setup briefly?
I
On Fri, Aug 05, 2011 at 03:51:36PM +0200, Andreas Kuntzagk wrote:
> Hi,
>
> I'm managing hosts ssh keys by using exported resources.
> I do this with this little config I found in the interWeb:
>
> ...
> @@sshkey { "$hostname,$ipaddress,$hostname-ext,$ipaddress_eth2": type => dsa,
> key => $sshd
On Fri, Aug 05, 2011 at 06:33:12AM -0700, Nigel Kersten wrote:
> We have a bunch of problems people regularly run into with node inheritance,
> and it's something we'd like to find a better solution for.
>
> Is anyone using node inheritance and happy with how it works? If so, can you
> describe yo
On 08/05/2011 10:21 AM, R.I.Pienaar wrote:
But also now I think $foo should be considered a top level variable in 2.7
when its not, making node variables more or less useless.
I like it that node variables are local and private.
node default {
$foo = "$backupdir/${hostname}"
- Original Message -
> On 08/05/2011 09:33 AM, Nigel Kersten wrote:
> > We have a bunch of problems people regularly run into with node
> > inheritance, and it's something we'd like to find a better solution
> > for.
> >
> Let me guess:
>
> - nodes are not classes
> - n
On 08/05/2011 09:51 AM, Andreas Kuntzagk wrote:
@@sshkey { "$hostname,$ipaddress,$hostname-ext,$ipaddress_eth2": type
=> dsa, key => $sshdsakey }
$hostname-ext < has a smell
Could you maybe help the parser out by throwing some braces in there?
--
vagn
--
You received this message bec
On 08/05/2011 09:33 AM, Nigel Kersten wrote:
We have a bunch of problems people regularly run into with node
inheritance, and it's something we'd like to find a better solution for.
Let me guess:
- nodes are not classes
- node scope is not global scope
Is there something else
Hi,
I'm managing hosts ssh keys by using exported resources.
I do this with this little config I found in the interWeb:
...
@@sshkey { "$hostname,$ipaddress,$hostname-ext,$ipaddress_eth2": type => dsa,
key => $sshdsakey }
...
Sshkey <<| |>>
Unfortunately the keys are duplicated every time pup
On 08/05/2011 04:25 AM, Thomas Rasmussen wrote:
Is there any way of overriding a previously include of a class?
Yes. See
http://docs.puppetlabs.com/guides/troubleshooting.html#class-inheritance-and-variable-scope
Something like (warning: untested):
Class["Sudoers::Config"] { env => 'c
We have a bunch of problems people regularly run into with node inheritance,
and it's something we'd like to find a better solution for.
Is anyone using node inheritance and happy with how it works? If so, can you
describe your setup briefly?
--
Nigel Kersten
Product Manager, Puppet Labs
*Join
On Fri, Aug 5, 2011 at 5:14 AM, Claude wrote:
> Here's what the log shows :
>
> Processing FilesController#show (for 10.10.10.1 at 2011-08-05
> 08:11:17) [GET]
> Parameters: {"action"=>"show", "controller"=>"files",
> "file"=>"70c1c6de6d4b1a02ec32b463e4d255b0"}
>
> Net::HTTPServerException (403
Here's what the log shows :
Processing FilesController#show (for 10.10.10.1 at 2011-08-05
08:11:17) [GET]
Parameters: {"action"=>"show", "controller"=>"files",
"file"=>"70c1c6de6d4b1a02ec32b463e4d255b0"}
Net::HTTPServerException (403 "Forbidden"):
/usr/lib64/ruby/1.8/net/http.rb:2105:in `erro
This might shed some more light for you:
http://docs.puppetlabs.com/guides/troubleshooting.html#node-inheritance-and-variable-scope
Maybe you can create another class that handles 'server default'. Or create a
custom fact that distinguishes these hosts from others.
I personally don't use my nod
Hi
Thanks for the reply, that works, but I'd like to keep my include of
the sudoers::config in my default node section, but if I do that, then
I don't have the $sudoenv variable available at that time.
Is there any way of overriding a previously include of a class? I
tried to 'sudoers::config': s
Hi,
You setting sudoenv to default in the default node. That is not overridden by
subsequent node declarations.
If you are using 2.6 and above I would pass a parameter to the sudoers class.
> class sudoers::config (env = 'default') {
> file { "/etc/sudoers":
>ensure => file,
>owner =>
Hi,
You can use facts supplied by facter to do the following (assuming you want to
do this for host with hostname host1).
> puppet:///files/configuration_files/${hostname}/mystuff/test.sh',
You can also assign variables easily like:
$host = 'host1'
And then use $host in your source statement.
Hi
I'm having some trouble with the following setup:
node 'serverA' inherits server-defaults {
include myApp::install
}
node 'server-defaults' inherits default {
$sudoenv = 'custom_server'
}
node default {
$sudoenv = 'default'
include sudoers::config
}
class sudoers::config {
file {
36 matches
Mail list logo
