Upcoming Maintenance Alert:

The UBNT Community will be upgraded at 5pm MDT on April 25th. During this time the community forums will be set to read-only status.

Learn more

×

Make multiple configuration changes - Reboot only once.

Submitted by -
Status: Implemented

When changes are made in the UniFi GUI, the AP's immediatly applies changes, causing a reboot/reprovision, usually of multiple access points.  Most of the time I find that I need to make multiple changes, which results in multiple reboots, most of the reboots could be avoided. 

I propose that configuration changes not be applied immediately but rather that the UI offer an APPLY CHANGES button.  Or even an option to apply changes in a rolling fashion or on a per-device basis, much like the existing "Upgrade" firmware option.  This would enable a minimum of disruption when configuring, especially in places where an AP client is covered by more than one AP.

 

 


Duplicates:

http://community.ubnt.com/t5/UniFi-Feature-Requests/changes-without-going-offline/idi-p/654507

Comments
by
on ‎10-23-2013 02:28 PM

Yep, the concept looks familiar to what I knew from some FC switches (FabOS) running or ... wait: Vyatta does that too (EdgeMAX!)

Yup, definitely would make sense to have that which would lead to a workflow: Change, hack, rerview, fix - finally: commit.

by
on ‎10-23-2013 05:34 PM

I think in addition to combining multiple config changes into one commit, we'd like that to include an option:

Wait until AP not in use (no client devices associated)

by
on ‎10-24-2013 05:45 PM
Most changes should be possible without an AP reboot. Sure, you might have to shut the radios down and kick all the clients off briefly, but it shouldn't take 3 minutes for the AP to change a WPA PSK, for instance. And in areas where multiple APs are deployed and a reboot is truly needed, it might be more useful to do so in small groups evenly distributed over the coverage area so that connected users can roam to different APs instead of losing connectivity altogether.
by
‎10-24-2013 05:52 PM - edited ‎10-28-2013 09:36 AM

I think for the purpose of this discussion, rebooting and reprovisioning are equivalent.  The discussion ends up being exactly the same irrespective of the technicalities behind the service interruption. 

by Ubiquiti Employee
on ‎11-05-2013 08:23 PM
Status changed to: Future Consideration
 
by
on ‎11-08-2013 10:24 AM

Yeah, AirOS get's this right.  We need a way to queue or pause provisioning and then commit changes.

by
‎11-10-2013 11:31 AM - edited ‎11-10-2013 11:31 AM

I agree, this would be nice. I would like to see two options:

1. Only reprovision if there are zero clients associated.

2. Mark each site or induvidual AP as "hold reprovisioning" and then get a button in the AP list similar to the "upgrade firmware", that would indicate there are pending changes that needs a round of provisioning. -A

by
on ‎11-18-2013 08:55 AM

I love this idea.

How about implementing it the same way you do for a firmware update, with rolling updates?

That way, even though every device would reboot, only one device would be unavailalbe at any one time.

Thanks!

by
on ‎11-29-2013 04:10 AM

Would absolutely agree - right now it feels very 'out of control'.  Let me make the number of changes I need, then make a positive decision to reboot/reprovision.  

 

Also, display something obvious in the admin UI to make it clear that there are 'unapplied changes' to me made...

by
‎12-08-2013 09:07 AM - edited ‎12-08-2013 09:07 AM

or at least sommething simple like apply change and reboot AP at : time picker.

So i can make all changes needed and schedule a 4 AM apply and reboot.