[j-nsp] Feature idea: commit and-reboot

[Richard A Steenbergen]

While attempting to combine a software upgrade and reboot with a commit
change that would require a routing bounce (to minimize flaps obviously),
I noticed that there is no way to make a change which will take affect
after the reboot is complete.

If you wanted to, say, turn on graceful-restart, change the families you
negotiate on BGP sessions, or otherwise make a session-resetting (but not
so complex you need the safety net of commit confirmed) change while you
are upgrading or rebooting (the equiv of changing your startup-config
without changing your running-config), there doesn't seem to be any way to
do it (other than trying to be really fast :P) which won't result in two
bounces.

I know the Juniper philosophy is "always make the configured state the
current state", but perhaps a "commit and-reboot" type command could be
used to check the config, apply it in the appropriate databases for after
the reboot, and then begin the reboot without reloading the daemons with 
the new config?

-- 
Richard A Steenbergen <ras at e-gerbil.net>       http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)