Unmanaging a Node/Device

Question

Is this a bug?

When you want to schedule a node/device to be unmanage by Node Details >> Unmanage - you cannot specify any future date/time.  Even though it takes what was submitted.  It works only with current date/time.

For example...let say current date is Nov 7/08, time 10:30 AM - so I want to schedule this node/device to be unmanage at 10:35 AM; I enter the 11/07/2008 10:35 AM in the "Unmanage this device beginning" box and 11/07/2008 10:40 AM in the "Unmanage this device until" box.  I click OK to submit.  At 10:35 AM this node is supposed to be unmanage but nothing happens.

However, if I leave the date/time in the  "Unmanage this device beginning" box as is and just enter the new date/time in the  "Unmanage this device until" box - click OK to submit and it immediately goes into unmanage state.  When the "Unmanage this device until" date/time is reached it is manage again.

I always felt that the scheduling feature in Orion is very lacking to say the least - always promising but not delivering.

FormerMember · Answer

Is this a bug?

When you want to schedule a node/device to be unmanage by Node Details >> Unmanage - you cannot specify any future date/time.  Even though it takes what was submitted.  It works only with current date/time.

For example...let say current date is Nov 7/08, time 10:30 AM - so I want to schedule this node/device to be unmanage at 10:35 AM; I enter the 11/07/2008 10:35 AM in the "Unmanage this device beginning" box and 11/07/2008 10:40 AM in the "Unmanage this device until" box.  I click OK to submit.  At 10:35 AM this node is supposed to be unmanage but nothing happens.

However, if I leave the date/time in the  "Unmanage this device beginning" box as is and just enter the new date/time in the  "Unmanage this device until" box - click OK to submit and it immediately goes into unmanage state.  When the "Unmanage this device until" date/time is reached it is manage again.

I always felt that the scheduling feature in Orion is very lacking to say the least - always promising but not delivering.

Yes, that's a bug.  I'll add it to our database.

FormerMember · Answer

I would also agree and I seem to remember that down interface was promised for release in Ver 9 now we are on 9.1 SP1 and still waiting.

Dave, while that feature was certainly (and rightly!) discussed, I'm sure it was not promised.  I'm the designated promise-maker for Orion, and I think you'll find that I'm loathe to commit to which features are in the release until very shortly before we ship. That feature was not targeted for 9.0 or 9.1.

Marking interfaces as "unplugged" instead of "down" is something we are targeting for the next release; however, even now, I am not promising it.  Targeting means that we'll figure out a design and engineernig will estimate the size and we'll try very hard to get it into the release.  That said,  we're still too far out, and almost any feature could get cut during release because it turned out to be bigger than expected or somehow de-stabilizes the release.  This is a very highly-requested feature, and I'd be surprised if we had to cut it.

dave.woolterton · Answer

I would also agree and I seem to remember that down interface was promised for release in Ver 9 now we are on 9.1 SP1 and still waiting.