Comment 2 for bug 2032664

Revision history for this message
Galen Charlton (gmc) wrote :

I may be jumping the gun on the branch, but one thing that occurs to me is that making the new reporting sources dependent on assumptions about OU depth should be avoided: not every Evergreen system's OU hierarchy is set up so that each OU at depth 1 is a system.

Consequently, I am imagining sources that might do something like this:

[1] Count or list transits between the descendants of a pair of OUs. This would cover inter-system transits between any given pair of systems/super-systems regardless of their respective depths.
[2] Count or list transits between the descendants of one OU and every other OU in the system. This would cover reporting on inter-system transits when you don't immediately care what the other end of the transit is.

But like I said, I may well be jumping the gun and will now just await the branch. :)