cluther wrote: > In short, yes. While embedded or nested maintenance windows do work as > expected, overlapping ones don't work intuitively if you set the stop > production state to original. > > In order to handle the overlapping maintenance windows with the stop > production state set to original we would need to maintain a stack of > production states as the device enters multiple maintenance windows so > that the stack could be walked out as the maintenance windows end. > This opens up all sorts of potentially weird behavior. For instance, > what should happen if someone manually changes the production state of > a device while it is in the middle of one or more maintenance windows?
Thanks for the reply. I guess I'll just have to take a hard look at all our our maintenance windows to see which ones can be consolidated, etc. I'll let you know if I find any more maintenance window oddities. Seth -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=12658#12658 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
