Re: [Puppet Users] Using file and mount more efficiently

2013-10-16 Thread jcbollinger
On Tuesday, October 15, 2013 3:21:42 PM UTC-5, Forrie wrote: Thanks for the reference, John. We need to ensure that these remote mounts are owned/grouped by specific UID/GID -- hence why I had ownership involved there. We could do this via UID/GID only (not name) if that works better?

Re: [Puppet Users] Using file and mount more efficiently

2013-10-15 Thread Forrie
Thanks for the reference, John. We need to ensure that these remote mounts are owned/grouped by specific UID/GID -- hence why I had ownership involved there. We could do this via UID/GID only (not name) if that works better? I don't understand how apply that ownership to /home/201301 would

Re: [Puppet Users] Using file and mount more efficiently

2013-09-24 Thread jcbollinger
On Monday, September 23, 2013 7:15:32 PM UTC-5, Forrie wrote: I've been playing around with this code and have encountered several errors. As noted below, there is going to be an issue with /home; however, I thought I could get around that by declaring that /first/, which won't work --

Re: [Puppet Users] Using file and mount more efficiently

2013-09-23 Thread Forrie
I've been playing around with this code and have encountered several errors. As noted below, there is going to be an issue with /home; however, I thought I could get around that by declaring that /first/, which won't work -- as it complains about duplicate declarations of /home. class

Re: [Puppet Users] Using file and mount more efficiently

2013-08-22 Thread maillists0
... and $name is the default variable given to you by puppet, so you don't have to define it. Works like $_ in perl. On Wed, Aug 21, 2013 at 7:18 PM, Peter Bukowinski pmb...@gmail.com wrote: You define an array-containing variable like this: $mounts = [ 'directory1', 'directory2',

[Puppet Users] Using file and mount more efficiently

2013-08-21 Thread Forrie
I have several NFS mounts to manage, on many systems. On each system, I must ensure that the root directory and path exist and have the correct permissions beforehand, then ensure they are mounted in Puppet. For each, I would normally do: file { /home/directory1:

Re: [Puppet Users] Using file and mount more efficiently

2013-08-21 Thread maillists0
You can fake interation. $name is a free variable for whatever you're passing in. I have NOT tested this, but it might look something like this: define my_mounts { mount { /home/$name: device = our-thumper.domain.com:/export/$name, atboot = yes,

Re: [Puppet Users] Using file and mount more efficiently

2013-08-21 Thread Forrie
So I would need to define $mounts, presumably as: $mounts = directory1 directory2 directory3 ? Where is $name being defined here. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from

Re: [Puppet Users] Using file and mount more efficiently

2013-08-21 Thread Peter Bukowinski
You define an array-containing variable like this: $mounts = [ 'directory1', 'directory2', 'directory3' ] You can also put newlines after the commas for easier reading. The following code should be functional: class test_case { $mounts = [ 'directory1', 'directory2',