So...am I doing something that Zenoss can't handle right now? I'd really like to get this resolved. If I can't set overlapping maintenance windows properly, or have servers marked as in "Maintenance Mode" and have that state persist through several scheduled maintenance windows, that is a bug to me. Chet, am I doing stuff that Zenoss just can't handle right now? And if so, is it something that is on the development radar (or can be put there) for 2.1.x or 2.2.0?
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?
_______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
