(I've added a third question, below -- resending on the hopes that we canb
cover them all in one go. Thanks again.)
While working on the IPMP Rearchitecture[1] code, I've hit upon a few
issues that need your input. Specifically:
1. Does Sun Cluster make use of either the IPMP query API
(PSARC/2002/615) or IPMP Asynchronous Events (PSARC/2002/137)?
(I know there is a contract, but I'm curious about shipping
code.) I ask because I've had to introduce some (compatible)
changes to these interfaces, but there are some incompatible
changes that I'd also like to make to simplify the code.
However, if Sun Cluster is using one or both of them, I'll
hold off on those incompatible changes.
2. I've had to rework the boot code such that in.mpathd starts
earlier in boot (as you may recall, currently it is delayed
via the SUNW_NO_MPATHD environment variable). If I'm reading
PSARC/2005/142 correctly, I believe the Sun Cluster IPMP SMF
service depends on the SUNW_NO_MPATHD behavior. As such, I
think we need to revisit the way the Sun Cluster IPMP SMF
service works, or introduce a full-fledged Solaris IPMP SMF
service to subsume the Sun Cluster one. (The latter has been
planned for some time, but I was hoping to avoid dragging it
into this already-massive project.) Thoughts?
3. Per PSARC/2002/763, Sun Cluster has a contract to use
SIOCSLIFGROUPNAME, SIOCGLIFGROUPNAME, lifr_groupname,
IFF_NOFAILOVER, IFF_STANDBY, IFF_FAILED, IFF_OFFLINE, and
IFF_INACTIVE. The semantics of several of these will be
changing. So, as above, does Sun Cluster have shipping code
that relies on the semantics of these interfaces? If so,
could you elaborate on the specific dependencies?
[1] The high-level design document hasn't yet been updated to cover all of
these issues. However, for general background, please see:
http://opensolaris.org/os/community/networking/ipmp-highlevel-design.pdf
--
meem
