Denmat wrote:
Very high level but I would like to see the following:
• to be able to create roles such as viewer, editor, administrator
• these roles be ldap groups
Den, will you tell me more about roles being LDAP groups? To my
perception that could mean:
* Manually creating a role in Das
On Mar 4, 9:18 am, Dan Bode wrote:
> > What language is the compiled thing in? Ruby?
>
> The compiled artifact is not code, it is data that describes the desired
> state of your system, in the above chart, the artifact you are asking about
> is the catalog.
>
*nods.* The catalog is just a direc
Hi,
My site.pp:
[root@S manifests]# cat /etc/puppet/manifests/site.pp
import "nodes.pp"
[root@S manifests]#
I copied ntp.pp into init.pp as you've suggested:
[root@S manifests]# cp ntp.pp init.pp
[root@S manifests]# diff ntp.pp init.pp
[root@S manifests]#
I started the server as follows:
[root@
Hello.
I'm trying to make a dashboard package for mandriva linux, but I'm
having some issues with the private copy of rack ruby gem shipped with
dashboard.
When installed on the same host as the puppetmaster, running itself with
passenger, it conflicts with the system version of this gem, require
On 3/4/2011 12:23 AM, Alan Barrett wrote:
On Thu, 03 Mar 2011, Rich Rauenzahn wrote:
It seems someone got clever and decided to look at exec's and look
for managed filenames in argument lists and create implicit
dependencies from them? Argh!
Yes, the unwanted dependencies are very annoying.
Bill Proud wrote:
> Sorry Jed I didn't realise that you didn't know about .puppet
> directories. A .puppet directory is created in your home directory if
> you accidentally run puppet as yourself and not as root. The problem
> that I had was that sometimes puppetd was correctly reading SSL
> sett
On Fri, Mar 4, 2011 at 8:50 AM, Kevin Beckford wrote:
> Is the puppet dsl a complete Turing capable language?
>
Puppet is not a general purpose programming language, it is a tool that
manages infrastructure, you could probably mathematically prove that it is
Turing complete, but its end result i
On Fri, Mar 04, 2011 at 02:24:59AM -0800, aleksey_k wrote:
> On 4 мар, 13:08, Ben Hughes wrote:
> > On Thu, Mar 03, 2011 at 11:59:25PM -0800, aleksey_k wrote:
> > > > # puppet agent --test
> >
> > Throw a --debug on the end, and it should be a whole more talkative!
> >
> Outpu here -> http://paste
Is the puppet dsl a complete Turing capable language?
As I understand it, the chain is dsl -> compiled thing -> actions.
What language is the compiled thing in? Ruby?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, s
On Thu, Mar 03, 2011 at 07:38:28PM -0800, Forrie wrote:
> I'm trying to figure out how to manage the NFS mounts, then 'unmanage'
> them when we're done -- ie: remove the NFS mount (ensure => absent)
> and make sure the mount point on the client is removed.
>
> I thought for the mount{} portion of
I manually created the mount points and incorrectly assumed the mount
process would automatically create the point if it didn't exist.
Once a managed mount point is no longer needed, we want the NFS mount
its directory removed from the client -- if we need them again, I can
just keep them commente
Just take a look at example42's nfs module, it should already provide the
functionallity you are looking for.
Regards, Stefan.
On 04.03.2011, at 04:46, Ben Hughes wrote:
> On Thu, Mar 03, 2011 at 07:38:28PM -0800, Forrie wrote:
>
>> So are you saying for the "absent" items, we'll need to in
I have hit a similar issue. Does anybody know if this is going to be fixed
or some workaround present?
--
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
I manually created the mount points and incorrectly assumed the mount
process would automatically create the point if it didn't exist.
Once a managed mount point is no longer needed, we want the NFS mount
its directory removed from the client -- if we need them again, I can
just keep them commente
Hi Dan,
the puppetmaster daemon is not running as root, however I have other
modules running on this machine and a files directory in each that
all have the same exact ownership and permissions and are being shared
without any problems.
tim
On Fri, Mar 4, 2011 at 9:18 AM, Daniel Piddock
wrote
On 03/03/11 21:14, Tim Dunphy wrote:
> hello list!!
>
> I am having some trouble with a postfix module I am attempting to
> implement. as always, your input is extremely valuable and would be
> appreciated
>
>
> here's what's going on:
>
> ## errors
>
> err: //postfix/Package[postfix-pflogsum.x86_6
On Mar 4, 3:35 am, toneeeda...@googlemail.com wrote:
> On Fri, Mar 4, 2011 at 12:11 AM, Ben Hughes wrote:
> > On Thu, Mar 03, 2011 at 09:09:59AM -0800, toneee wrote:
>
> > > I have a small problem, I am creating users with ssh keys and this is
> > > working fine, the only problem I have is becau
On Mar 3, 10:38 pm, Ramin K wrote:
> source => "puppet:///postfix/aliases.db"; <--- I don't think you need
> the ; anywhere. You've got a a few of them.
They are not necessary in that context, but they are valid and
harmless. They are needed when you want to put multiple resources
into the sam
After completely deleting the node from the database's 'host' table and
resources that referenced its host_id, a following catalog run refreshed
the database, adding all facts with their current values...
Best regards,
Martijn.
On 04-03-11 12:43, Martijn Grendelman wrote:
> Hi,
>
> I run the Pu
Hi,
I run the Puppetmaster with
storeconfigs = true
thin_storeconfigs = true
dbadapter = mysql
So far, this has been working perfectly, but today I noticed something
odd. Yesterday, I upgraded one of my nodes from Ubuntu Jaunty to Lucid,
but the facts from this node aren't updated in the databas
On 03/04/2011 09:08 AM, Ben Hughes wrote:
> On Thu, Mar 03, 2011 at 11:59:25PM -0800, aleksey_k wrote:
>
>>> # puppet agent --test
>
> Throw a --debug on the end, and it should be a whole more talkative!
>
>> puppetmaster:
>> #grep -i keys node/test-nodes.pp
>> include "keys"
>
> You made a cla
Sorry Jed I didn't realise that you didn't know about .puppet
directories. A .puppet directory is created in your home directory if
you accidentally run puppet as yourself and not as root. The problem
that I had was that sometimes puppetd was correctly reading SSL
settings from /var/lib/puppet/ss
On 4 мар, 13:08, Ben Hughes wrote:
> On Thu, Mar 03, 2011 at 11:59:25PM -0800, aleksey_k wrote:
> > > # puppet agent --test
>
> Throw a --debug on the end, and it should be a whole more talkative!
>
Outpu here -> http://pastebin.com/0GHfkH63
> You made a class for it? As it sounds like it's not g
On Fri, Mar 4, 2011 at 12:11 AM, Ben Hughes wrote:
> On Thu, Mar 03, 2011 at 09:09:59AM -0800, toneee wrote:
>
> > I have a small problem, I am creating users with ssh keys and this is
> > working fine, the only problem I have is because i dont set a password
> > and only use sshkeys to login the
On Thu, 03 Mar 2011, Rich Rauenzahn wrote:
It seems someone got clever and decided to look at exec's and
look for managed filenames in argument lists and create implicit
dependencies from them? Argh!
Yes, the unwanted dependencies are very annoying. Using file
names like /dir/subdir/./file
On Thu, Mar 03, 2011 at 11:59:25PM -0800, aleksey_k wrote:
> > # puppet agent --test
Throw a --debug on the end, and it should be a whole more talkative!
> puppetmaster:
> #grep -i keys node/test-nodes.pp
> include "keys"
You made a class for it? As it sounds like it's not getting called at all
26 matches
Mail list logo
