cluther wrote: > The default "Stop Production State" for a maintenance window is Original. > This makes an attempt to set the production state of affected devices back to > what they were before the window. In the case of complex overlapping windows > you would probably be better off setting the stop production state to > Production.
This sounds like a good idea, but doesn't account for servers that have manually been set to a state other than Production. I tried this with Zenoss before it had the concept of the "Original" end state. The side-effect is that any server I have manually set to a production state other than "Production" will get their state reset to "Production" at the end of the maintenance window, which is definitely not the intended result. I have to assume that the scenario hasn't changed. If it is not possible to have overlapping maintenance windows at this point, is it something that is on the radar for a future release? Like I mentioned in my other post to the zenoss-dev list, I'd love to move Zenoss into a production environment but I need to get these kinks worked out first. jmp242 wrote: > Maybe you are moving to "Original" rather than Production? I'm not sure, may > just be unclear in your original message. I do have the end state set to Original, because I want my servers' state to return to what it was before the maintenance window, which may not always be the Production state if I have manually set a server or group of servers to Maintenance or Test or whatever. Thank you both for the quick responses! seth wright ([EMAIL PROTECTED]) windows engineer 540.568.2912 (office) james madison university -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=12556#12556 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
