Hey, guys! These days I'm keep on setting up my puppet automation
environment, but I got a problem that made me confused.
I have a define to add users ,which as follows :
define usermgr::add_user ($usershell='/bin/bash', $groups) {
4
5 file
6 { /home/$title:
7 owner
Hi everyone,
I’ve been working on getting puppet set up for our systems for the
past week, and all has gone well in learning about writing manifests,
but now that I’m ready to set it into production, I realize that it’s
still unclear to me exactly how that’s supposed to go.
For instance, during
Not sure how to do it, but what I would try: (see inline)
On 18.06.2010 13:46, daniel wrote:
Hey, guys! These days I'm keep on setting up my puppet automation
environment, but I got a problem that made me confused.
I have a define to add users ,which as follows :
define usermgr::add_user
On 20.06.2010 12:38, Christopher wrote:
Hi everyone,
I’ve been working on getting puppet set up for our systems for the
past week, and all has gone well in learning about writing manifests,
but now that I’m ready to set it into production, I realize that it’s
still unclear to me exactly how
I'm in the process of trying to convert our current node
implementation to external nodes. The definitions that we called from
our node manifests have been replaced by variables passed back to
classes in modules. When using definitions, we could set default
values in the definition, and therefore
On Sun, Jun 20, 2010 at 11:05 AM, Douglas Garstang
doug.garst...@gmail.comwrote:
I'm in the process of trying to convert our current node
implementation to external nodes. The definitions that we called from
our node manifests have been replaced by variables passed back to
classes in modules.
On 06/20/2010 12:10 PM, Silviu Paragina wrote:
Not sure how to do it, but what I would try: (see inline)
On 18.06.2010 13:46, daniel wrote:
Hey, guys! These days I'm keep on setting up my puppet automation
environment, but I got a problem that made me confused.
I have a define to add users
On Sun, Jun 20, 2010 at 11:10 AM, Dan Bode d...@puppetlabs.com wrote:
On Sun, Jun 20, 2010 at 11:05 AM, Douglas Garstang doug.garst...@gmail.com
wrote:
I'm in the process of trying to convert our current node
implementation to external nodes. The definitions that we called from
our node
On Sun, Jun 20, 2010 at 11:16 AM, Douglas Garstang
doug.garst...@gmail.com wrote:
On Sun, Jun 20, 2010 at 11:10 AM, Dan Bode d...@puppetlabs.com wrote:
On Sun, Jun 20, 2010 at 11:05 AM, Douglas Garstang doug.garst...@gmail.com
wrote:
I'm in the process of trying to convert our current node
Oh oh... This might be user error...
On Sun, Jun 20, 2010 at 11:31 AM, Douglas Garstang
doug.garst...@gmail.com wrote:
On Sun, Jun 20, 2010 at 11:16 AM, Douglas Garstang
doug.garst...@gmail.com wrote:
On Sun, Jun 20, 2010 at 11:10 AM, Dan Bode d...@puppetlabs.com wrote:
On Sun, Jun 20, 2010
You've got some problems that are caused because the packages didn't do things
you need done, and other problems that are unrelated.
On the clients, puppetd will automatically look for the server at puppet, and
should use the search domain. You really want to change DNS so that the
I think I have a misunderstanding of variable scope in classes.
Wy isn't tfel4_ClusterDbType set in the elements::tfel4::elements
class? It's set in elements::tfel4::defaults but then goes *poof* when
elements::tfel4::elements tries to access it.
class elements::tfel4::defaults {
if (
Anyone have any ideas on adding a default header to puppet managed
files and templates?
This might be tricky because of the different methods of adding
comments for different types of files but I'm certainly open to
suggestions that would enforce the existence of a header.
--
You received this
On 2010-06-20 14:55, Douglas Garstang wrote:
I think I have a misunderstanding of variable scope in classes.
Wy isn't tfel4_ClusterDbType set in the elements::tfel4::elements
class? It's set in elements::tfel4::defaults but then goes *poof* when
elements::tfel4::elements tries to access it.
On 2010-06-20 15:37, Psyber wrote:
Anyone have any ideas on adding a default header to puppet managed
files and templates?
This might be tricky because of the different methods of adding
comments for different types of files but I'm certainly open to
suggestions that would enforce the
On Jun 20, 2010, at 12:37 PM, Psyber wrote:
Anyone have any ideas on adding a default header to puppet managed
files and templates?
This might be tricky because of the different methods of adding
comments for different types of files but I'm certainly open to
suggestions that would enforce
On 2010-06-20 15:50, Patrick Mohr wrote:
On Jun 20, 2010, at 12:37 PM, Psyber wrote:
Anyone have any ideas on adding a default header to puppet managed
files and templates?
This might be tricky because of the different methods of adding
comments for different types of files but I'm
Hello there
I must be blind because i just can't find what i'm looking for
anywhere:
1) file_metadata - i get stacks and stacks of messages telling me:
Jun 21 07:49:46 tangelo puppetmasterd[29585]: Could not find
file_metadata for 'modules/redhat-monit/service_groups/etc/monit.d/
Joe is right, you need to generate the group(s), before you generate
the user(s), before you setup their homedirectory.
For example:
group
{ ldap:
gid = 294,
before= User[ldap],
}
user
{ ldap:
uid
On Jun 20, 2010, at 2:57 PM, chakkerz wrote:
2) searching for information on this i found references on auth.conf
which (because i deploy an RPM) is generated for me. However it is a
default file, and i'd love to know what to put in it. I can't find any
documentation on the subject. Anyone
Thanks for example.
Cheers,
On Jun 19, 12:31 am, spawn-pup...@adamsclan.org wrote:
As another option, I believe you can use:
file { /etc/abc.conf:
ensure = present
content = rundir= /central/$hostname/\nlogdir=
$hostname.log
}
- Jeff
On
I am having all the problems that the following two threads reported.
Like tomholl reported, I was finally able to get reporting to work by copying
the puppet_dashboard.rb file into the directory site_ruby/1.8/puppet/reports
And when I had previously attempted to specify libdir to be a colon
The example auth.conf that came with Ubuntu is 2.3k and very well commented.
Would posting that help?
If you've got one handy, yes :)
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to
On Jun 20, 2010, at 5:56 PM, chakkerz wrote:
The example auth.conf that came with Ubuntu is 2.3k and very well commented.
Would posting that help?
If you've got one handy, yes :)
# This is an example auth.conf file, it mimics the puppetmasterd defaults
#
# The ACL are checked in order
I believe you can do
class elements::tfel4::elements {
include elements::tfel4::jboss
include elements::tfel4::defaults
notice((2)tfel4_ClusterDbType = $
{elements::tfel4::defaults::tfel4_ClusterDbType})
}
On Jun 20, 2:48 pm, Gabriel Filion lelu...@gmail.com wrote:
On 2010-06-20
25 matches
Mail list logo