I decided to try and modify an existing NFS module (puppet-nfs) from
GitHub to suit my needs (rather than reinvent the wheel). I'm stuck
on the "ensure" property of "file" -- there is some discussion on the
net (bug reports) that this does not recursively create the directory
structure... hence:
On Fri, Mar 04, 2011 at 07:42:22AM -0800, Forrie wrote:
> I manually created the mount points and incorrectly assumed the mount
> process would automatically create the point if it didn't exist.
Afraid it doesn't, they have to exist before hand.
> Can you explain the wrap you were talking about?
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 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
On Thu, Mar 03, 2011 at 07:38:28PM -0800, Forrie wrote:
> So are you saying for the "absent" items, we'll need to include a
> file{} directive to remove the mount point, too?
The mount handler won't go around deleting directories for you,
thankfully. (:
Do you create the mount point before you m
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 this and loop over it. But it's
not a big deal, I don't mind edit
On Thu, Mar 03, 2011 at 05:49:58PM -0800, Forrie wrote:
> I caught that, thank you -- I've wiped my glasses thoroughly ;-)
(:
> One other issue I'm running into is I would like the client to
> *create* (mkdir) the mountpoint with the correct permissions if it
> doesn't exist. I don't see a way
It looks like you can't change the definition of "ensure => mounted"
to "ensure => absent" and have it automatically remove the managed
resource (mount point).We have a series of directories that are
used for all three terms, after we're done, we don't need the NFS
mounts or directories present
I caught that, thank you -- I've wiped my glasses thoroughly ;-)
One other issue I'm running into is I would like the client to
*create* (mkdir) the mountpoint with the correct permissions if it
doesn't exist. I don't see a way that can be done within the mount
{} construct... is there a clever
11 matches
Mail list logo
