[Ocfs2-users] Ocfs2-users Digest, Vol 65, Issue 3

[John McNulty]

The only thing I can think of would / could be to keep node specific  
copies of app files in a filesystem local to each node and then soft  
link to those from the OCFS2 filesystem.   For example:

-  assume you're going to install into /opt/application, create and  
mount an OCFS2 filesystem there.
-  install as normal on one node.
-  create a new [small] ext3 filesystem on each cluster member and  
mount to /local (or where ever you like)
-  assume files like /opt/application/etc/app.conf need to be unique  
to each cluster node
-  mkdir -p /local/application/etc
-  cp /opt/application/etc/app.conf  /local/application/etc   (repeat  
on each cluster node)
-  modify /local/application/etc/app.conf on each node to make it unique
-  rm /opt/application/etc/app.conf
-  ln -s /local/application/etc/app.conf /opt/application/etc/app.conf
-  Update fstabs accordingly

Would that do the trick for you?

Rgds,

John

On 17 Sep 2009, at 16:33, David Johle wrote:

> So here I am once again trying to eliminate the use of CDSLs so that
> I can upgrade past 1.2.x, and I'm finding myself stuck.
>
> I have made use of bind mounts for entire directories that were
> node-specific via CDSL.  However, I have yet to find an alternative
> for a CDSL that points at a single file.  I've been re-working
> applications configs and all to reduce depency on CDSL and/or bind
> mounts, but I've gotten down to only TWO files left which use a
> CDSL.  And, due to the nature of the application and configuration
> file I cannot figure a way around the CDSL.
>
> Has anyone else gone through this process of getting away from
> specific file CDSLs?  If so, what did you do?
>
> _______________________________________________
> Ocfs2-users mailing list
> Ocfs2-users at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-users