Leslie Keller - Serviceability Engineering wrote:
'racks' please ... not 'cabinets'.....
OK.
-Leslie
Russ McManus wrote:
Gavin Maltby wrote:
Eric Schrock wrote:
On Mon, Jan 07, 2008 at 04:17:32PM -0800, Richard Elling wrote:
I have some heartburn over this statement. I think it will be
confusing in thoses
cases where a set of domains may share the same physical chassis
(eg. blade
servers). Perhaps we need a different name, other than "chassis'?
Chassis is already an established term in the hc:/ topology, with
'systemboard' to differentiate between multiple domains. I don't see
any reason to deviate from the established convention, since the FMRIs
in this case are in fact associated with the chassis, not some other
construct.
The M9000 system with expansion cabinets and additional power cabinets
is a good test of the intended topology. The M9000 base chassis
contains some cpu/mem/IO as expected together with 15 PSUs in the
front and 12 fan trays in the back. You may then connect an
expansion cabinet that again has cpu/mem/IO and the same number
of PSUs and fan trays, and these are cabled together with some
giant cables that allow you to configure domains that span the
two cabinets (as far as I can tell). Finally, both the base
and expansion cabinet can be partnered by yet another
power cabinet that has another 15 PSUs. So in total there
are 4 chassis units all side by side, 2 of which are for power
only. I suspect the M9000 is not a target system for this
stage of the project, but we should plan to accomodate future
extended systems such as this.
So while the statement "only one chassis" may be problematic, I don't
see the use of the term "chassis" in an FRMI being so, or causing any
confusion. We should be able to enumerate the number of "cabinets"
and "chassis" and other components associated with each, presented by
the actual physical topology.
Cheers
Gavin
------------------------------------------------------------------------
_______________________________________________
fm-discuss mailing list
fm-discuss@opensolaris.org
--
Russ McManus
Principal Engineer
Chief Serviceability Architect
Global Customer Services, Serviceability and Readiness
NSH01
x29023 - 978-878-3201
------------------------------------------------------------------------
_______________________________________________
fm-discuss mailing list
fm-discuss@opensolaris.org
------------------------------------------------------------------------
_______________________________________________
fm-discuss mailing list
fm-discuss@opensolaris.org
--
Russ McManus
Principal Engineer
Chief Serviceability Architect
Global Customer Services, Serviceability and Readiness
NSH01
x29023 - 978-878-3201
_______________________________________________
fm-discuss mailing list
fm-discuss@opensolaris.org
