Hi Rein,
The patch that was presented by Kai I believe will work, I originally
missed where they continue to check after the original directory /proc/
vz check. Unfortunately, if this is the best that we can do using
native code, we might be stuck with it for now due to the limitations
of OpenVZ. My solution uses Exec which I know we are trying to get
away from using, it does resolve the question in one single statement
though.
(%x[cat /proc/self/status | awk ‘$1 == “envID:” {print $2}’]) ? result
= “openvzhn” : result =“openvzve”
I have been using the code above in the openvz module as it is working
for my needs (0.25.5-1) at the current moment. I have no problem using
the proposed patch, my main goal is to simply get a working and
dependable version into the next round of releases.
Matt
On Aug 6, 6:19 pm, Rein Henrichs <[email protected]> wrote:
> Excerpts from Matthew Cluver's message of Thu Aug 05 21:48:21 -0700 2010:
>
> > Hi Everyone,
>
> > I'm working on developing what would be an openly available module for
> > puppet, to allow for the development and manipulation of virtual
> > containers on OpenVZ host nodes.
>
> > Here it is on google code:http://code.google.com/p/puppet-openvz/
>
> > If you have been working on the same thing and have any code that
> > you'd like to contribute it would certainly be appreciated!
>
> > Cheers & best regards,
>
> > Matt
>
> Hi Matt,
>
> I see that you've commented on Facter bug #4156[1]. Is there any consensus
> on the correct way to fix this bug? I'd like to get it resolved for
> 1.5.8, especially if it's affecting your work on an OpenVZ module.
>
> [1]http://projects.reductivelabs.com/issues/4156
> --
> Rein Henrichshttp://puppetlabs.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
