Lars Marowsky-Bree wrote:
On 2006-01-10T11:08:47, Mark Fasheh <[EMAIL PROTECTED]> wrote:
4.) Follows logically from 3.: When the admin tries to mount a
filesystem which we don't know about yet (fsid not in our
configuration), we create the required object from a default template,
and then proceed as above. At this stage, mkfs/mount/umount will provide
the complete look & feel of a regular filesystem.
Except that you CANNOT mount, umount, or mkfs before the CRM starts.
This means you can't put it in fstab like people conventionally do.
(Unless of course, the CRM somehow gets started really early - this
would likely be messy)
Further options we might then explore, mostly optimizations:
5.) Right now, the OCFS2 is driven via the regular Resource Agent
mechanism. That implies calling (exec) out to an external agent;
ultimately, I'd like to have a "fast" RA interface talking to a
pre-loaded plugin for efficiency. Again this is mostly an internal
optimization and doesn't really affect the overall design.
Lars already knows this - but for the rest of you: This would be
relatively easily implemented in our current architecture. We already
have a special class of resource agent which does this (STONITH).
Adding a "general" one would be relatively easy. Just need to make sure
we design the API in an extensible way so we don't have a bunch of churn
later on.
--
Alan Robertson <[EMAIL PROTECTED]>
"Openness is the foundation and preservative of friendship... Let me
claim from you at all times your undisguised opinions." - William
Wilberforce
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
