Project

General

Profile

Actions

Feature #3048

closed

Pre-download packages to reduce downtime during upgrade process?

Added by Adam Thompson almost 11 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Upgrade
Target version:
Start date:
06/17/2013
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

Not sure if this is possible under the current system...
If it is possible to determine what version of [a] package[s] will likely be required post-reboot to complete the upgrade, would it be possible to download them and stage them on disk before rebooting? On a system with only two packages loaded, with a decent internet connection, it still takes ~5min to complete that part of the upgrade!
Coupled with issue #3013, this can make upgrading - even in a CARP environment - a painfully long outage. Pre-staging the packages would at least avoid the unexpected (if the upgrader is tired and hasn't done this for a while) delay in the middle of the upgrade.
Not quite an in-service upgrade a la Cisco or Juniper, but on a firewall with lots of installed packages, this could easily shave 45min off the total user-visible downtime.
Note that although core routing functionality is up and running quickly, some packages are critical to normal operation of the firewall, e.g. bgpd/ospfd, squid, etc.

Actions #1

Updated by Chris Buechler about 8 years ago

  • Status changed from New to Resolved
  • Target version set to 2.3

2.3 does this

Actions

Also available in: Atom PDF