Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature : Automatic updates #814

Closed
tifredfr opened this issue Mar 13, 2016 · 11 comments
Closed

Feature : Automatic updates #814

tifredfr opened this issue Mar 13, 2016 · 11 comments
Assignees
Labels
feature Adding new functionality
Milestone

Comments

@tifredfr
Copy link

Hi,

To apply the days of automatic updates, be notified when an update is available, you can apply the updates if the reboot is not necessary …

System > Firmware > Auto updates

  • enabled
  • send notification if update available (required configured SMTP see System: Settings: Notifications)
  • define the verification period (check daily at 2H or check every Friday at 2H for exemple)
  • apply the updates if a restart is not required or apply all updates
  • send an update report if updates
@fraenki
Copy link
Member

fraenki commented Mar 14, 2016

I'd go a little further and add the following auto-upgrade settings. This would make the auto-upgrade usable to a wide range of users:

Check for Updates:
( ) Weekly
(*) Daily
( ) Hourly

Update Mode:
(*) Apply only minor updates {default}
( ) Apply minor and major updates
( ) Apply only security-related minor updates

Update Period:
(*) Install updates immediately (after a short random delay) {default}
( ) Only during specific times (cron-like pattern)

Automatic Reboot:
(*) Enabled (Required to install all updates) {default}
( ) Disabled (Warning: Some updates may not be installed)

Of course, auto-upgrades are a little risky, especially if many users make use of them. A critical bug may render a many systems unusable. A possible countermeasure: Maybe enabling auto-upgrade should require the automatic submission of crash reports (so that the developers may be able to remove a broken update rather sooner than later).

@tifredfr
Copy link
Author

Nice @fraenki

Indeed, one can also add a timeout.
For example : If update available, apply in X days. In general, critical problems after an update is corrected after a few days ...

@fichtner fichtner added the feature Adding new functionality label Apr 25, 2016
@fichtner fichtner added this to the 16.7 milestone Apr 25, 2016
@fichtner fichtner self-assigned this Apr 25, 2016
@fichtner
Copy link
Member

Some of this is already on -devel, with a cron job and auto-update. I'm a bit against further granularity. We can prevent the system from updating if it needs to reboot, but the reporting side will need more code that its worth. ;)

@fraenki
Copy link
Member

fraenki commented May 24, 2016

@fichtner I'm OK with the current state. The new auto-update command makes it easy to write a custom upgrade script.

@fichtner
Copy link
Member

You can use the cron page too. :) Will be available in the menu soon enough too. It's already on -devel or access directly via https://FIREWALL/ui/cron/

@fichtner
Copy link
Member

(Leaving this open, setting target to 17.1)

@fichtner fichtner modified the milestones: 17.1, 16.7 May 24, 2016
@tifredfr
Copy link
Author

Nice thx ;)

@fichtner
Copy link
Member

Time to review...

Check for updates: all done, can chose a cron pattern

Update mode: we could split reboot/non-reboot. Tricky are cases where we go from 16.1 -> 16.7, but we can find a mode there too. That's as far as I would like to go: no reboot, full reboot, major update. Ok?

Update period: cron pattern is enough here, marking it done...

Automatic reboot: taken care of in update mode.

@thelinuxfr @fraenki Does that sound reasonable?

fichtner added a commit that referenced this issue Jun 1, 2016
o Allow side-stepping flock(1) if not installed for rc script
o Pass arguments to subroutine script to allow passing modes
o Print a busy message when e.g. the GUI is running the upgrade
@fraenki
Copy link
Member

fraenki commented Jun 1, 2016

@fichtner Sounds reasonable, very satisfying results :)

@tifredfr
Copy link
Author

tifredfr commented Jun 3, 2016

@fichtner yes I'm fine, thank you for the work

@fichtner fichtner modified the milestones: 17.7, 17.1 Jan 23, 2017
@fichtner
Copy link
Member

fichtner commented Jan 25, 2017

I'm going to simplify this: update per cron works, reboots if necessary. major upgrades will not be available using a "normal" firmware update scheme so we don't have to protect against it. Closing. :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Adding new functionality
Development

No branches or pull requests

3 participants