Picon
Favicon

UI Proposal for XCF-1098

Hi guys,

I've attached to the JIRA issue XCF-1098 ( 
http://track.sipfoundry.org/browse/XCF-1098 ) the UI proposal for this 
feature.

I've chosen this look because I'm thinking a scheduled restart happens 
asynchronously. It's not something that happens every day or every week.

This is how I'm thinking it will work: the administrator modifies the 
phone profile, checks the phone and clicks "Send Profile". The page 
illustrated in Scheduled-restart-device2.jpg appears 
(http://track.sipfoundry.org/secure/attachment/13205/Scheduled-restart-device2.jpg). 
Here he has the option to restart the phone immediately or to plan a 
scheduled restart. He has to choose the day of the week and the hour for 
a scheduled restart.
After he clicks OK, the page illustrated in 
Scheduled-restart-device1.jpg 
(http://track.sipfoundry.org/secure/attachment/13204/Scheduled-restart-device1.jpg) 
appears.
Also, I'm thinking that "Send Profile " and "Send All Profiles" buttons 
should be renamed "Generate Profile" and "Generate All Profiles".

So, after the device is successfully restarted (either by hand or by a 
scheduled restart), there will be no "Scheduled Restart" for that device.
If a new scheduled restart is planned by the administrator, this will 
override the old one.
What I'm trying to say is that devices and scheduled restart(s) will be 
in a 1:1 relation.

I'm not very sure about this approach, since I'm not an administrator an 
I can only guess what happens in a real-world deployment of the sipx server.
So please have a look and post your comments.

Regards,
Andrei
Damian Krzeminski | 7 Dec 20:33

Re: UI Proposal for XCF-1098

Andrei Cristian Niculae wrote:
> Hi guys,
> 
> I've attached to the JIRA issue XCF-1098 ( 
> http://track.sipfoundry.org/browse/XCF-1098 ) the UI proposal for this 
> feature.
> 
> I've chosen this look because I'm thinking a scheduled restart happens 
> asynchronously. It's not something that happens every day or every week.

I like UI for dalayed restart. I do not like UI for cancelling delayed 
restart. I do not think we should even offer that option (please note 
that original issue did not ask for it). But if we do offer cancelling 
delayed jobs I would propose that it's being handled on the Jobs 
screens: admin sees the jobs in Scheduled phase and can click on them 
and cancel them. I think poluting Manage Phones with nontrivial and 
probably not very useful operation is not needed.

If people disagree with that I would like to ask that patch with 
cancelling delayed restarts is separate from the patch for delaying 
restart (which is non controversial and desired)

> 
> This is how I'm thinking it will work: the administrator modifies the 
> phone profile, checks the phone and clicks "Send Profile". The page 
> illustrated in Scheduled-restart-device2.jpg appears 
> (http://track.sipfoundry.org/secure/attachment/13205/Scheduled-restart-device2.jpg). 
> Here he has the option to restart the phone immediately or to plan a 
> scheduled restart. He has to choose the day of the week and the hour for 
> a scheduled restart.

Implementation question: so what we are really delaying is restarting of 
the device that needs a new profile and not generating this profile. Right?

> After he clicks OK, the page illustrated in 
> Scheduled-restart-device1.jpg 
> (http://track.sipfoundry.org/secure/attachment/13204/Scheduled-restart-device1.jpg) 
> appears.
> Also, I'm thinking that "Send Profile " and "Send All Profiles" buttons 
> should be renamed "Generate Profile" and "Generate All Profiles".

Well: "Send" is shorter than "Generate"... do you think people get 
confused by "Send"?

> 
> So, after the device is successfully restarted (either by hand or by a 
> scheduled restart), there will be no "Scheduled Restart" for that device.
> If a new scheduled restart is planned by the administrator, this will 
> override the old one.
> What I'm trying to say is that devices and scheduled restart(s) will be 
> in a 1:1 relation.

I think I understand: if admin schedules restart for mindnight and than 
thinks about it again and restarts at 6pm, then restart at midnight will 
not happen. Makes sense to me and I would think that's it is the way 
most people I talked to thing about restarting.

> 
> I'm not very sure about this approach, since I'm not an administrator an 
> I can only guess what happens in a real-world deployment of the sipx server.
> So please have a look and post your comments.
> 
> Regards,
> Andrei

Again: that would be a great addition to sipXconfig. Thanks!
D.

Picon
Favicon

Re: UI Proposal for XCF-1098

Damian Krzeminski wrote:
Andrei Cristian Niculae wrote:
Hi guys, I've attached to the JIRA issue XCF-1098 ( http://track.sipfoundry.org/browse/XCF-1098 ) the UI proposal for this feature. I've chosen this look because I'm thinking a scheduled restart happens asynchronously. It's not something that happens every day or every week.
I like UI for dalayed restart. I do not like UI for cancelling delayed restart. I do not think we should even offer that option (please note that original issue did not ask for it). But if we do offer cancelling delayed jobs I would propose that it's being handled on the Jobs screens: admin sees the jobs in Scheduled phase and can click on them and cancel them. I think poluting Manage Phones with nontrivial and probably not very useful operation is not needed. If people disagree with that I would like to ask that patch with cancelling delayed restarts is separate from the patch for delaying restart (which is non controversial and desired)
Honestly, I don't like the UI for canceling delayed restart either :) It's too big.
I just thought that if we offer the possibility to schedule a restart, we should offer
a possibility to cancel that restart. But we could just explain in the quick help  how this works
and how the admin can reschedule a restart by sending the profiles again.
One more method would be to make the Schedule Restart clickable, and this would take us to
a different page where the admin has the possibility to cancel or to reschedule the restart.
Anyway, for the moment I'll just focus on the delayed restart, as you suggested, and after I'm done,
we could furthermore discuss the canceling procedure, if we want to have one.
This is how I'm thinking it will work: the administrator modifies the phone profile, checks the phone and clicks "Send Profile". The page illustrated in Scheduled-restart-device2.jpg appears (http://track.sipfoundry.org/secure/attachment/13205/Scheduled-restart-device2.jpg). Here he has the option to restart the phone immediately or to plan a scheduled restart. He has to choose the day of the week and the hour for a scheduled restart.
Implementation question: so what we are really delaying is restarting of the device that needs a new profile and not generating this profile. Right?
Yes. The profile is generated immediately and if the phone is restarted manually, it will download the new configuration.
After he clicks OK, the page illustrated in Scheduled-restart-device1.jpg (http://track.sipfoundry.org/secure/attachment/13204/Scheduled-restart-device1.jpg) appears. Also, I'm thinking that "Send Profile " and "Send All Profiles" buttons should be renamed "Generate Profile" and "Generate All Profiles".
Well: "Send" is shorter than "Generate"... do you think people get confused by "Send"?
You're right, "Send" is shorter :) I was just thinking that we actually just generate the profiles and the phones pick them up, so we're not exactly sending them.
But I don't think people will get confused by this, and since the panel is already big, I guess "Send" is the best choice.

I'll update the pictures so they reflect what we've discussed here.

Regards,
Andrei

Gmane