Linux

48083 readers

776 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

How to stagger automated upgrade? (lemmy.ml)

submitted 3 months ago* (last edited 3 months ago) by remram@lemmy.ml to c/linux@lemmy.ml

62 comments fedilink hide all child comments

I am using unattended-upgrades across multiple servers. I would like package updates to be rolled out gradually, either randomly or to a subset of test/staging machines first. Is there a way to do that for APT on Ubuntu?

An obvious option is to set some machines to update on Monday and the others to update on Wednesday, but that only gives me only weekly updates...

The goal of course is to avoid a Crowdstrike-like situation on my Ubuntu machines.

edit: For example. An updated openssh-server comes out. One fifth of the machines updates that day, another fifth updates the next day, and the rest updates 3 days later.

you are viewing a single comment's thread
view the rest of the comments

[–] GravitySpoiled@lemmy.ml 6 points 3 months ago (2 children)

You don't need the staggered rollout since it won't boot into a broken image and you can boot easily into an old one if you don't like the new one. E.g. fedora atomic.

I'm not up to date with vanilla os for the debian world if it is on par with fedora.

[–] remram@lemmy.ml 4 points 3 months ago (1 children)

I am not worried about upgrades so bad that they literally don't boot. I am worried about all the possible problems that might break my service.

[–] GravitySpoiled@lemmy.ml 4 points 3 months ago (1 children)

You also roll back package versions. I'm not sure what problems could arise.

[–] remram@lemmy.ml 3 points 3 months ago (2 children)

I can roll back with APT too, my question is how to do the staggered rollout.

[–] GravitySpoiled@lemmy.ml 2 points 3 months ago (1 children)

You have to reboot for an image update. Hence, you can update the computers at different times and days.

[–] remram@lemmy.ml 3 points 3 months ago

This doesn't seem to enhance my workflow at all. Seems I now would have to reboot, and I still need to find a separate tool to coordinate/stagger updates, like I do now. Or did I miss something?

[–] GravitySpoiled@lemmy.ml 0 points 3 months ago* (last edited 3 months ago) (1 children)

If the os works always (atomic image based distro), and the docker container work, and both can roll back easily. What else could go wrong?

Don't overthink it :)

[–] remram@lemmy.ml 1 points 3 months ago

I am not sure what you are taking about. My question is about APT.

[–] umami_wasbi@lemmy.ml 2 points 3 months ago

No, OP absolutely still need staggered rollout. Immutable distros are a blue-green deployment self-contained. Yet, all the instance can upgrade and switch all at once and break all of them. OP still need some rollout strategy externally to prevent the whole service being brought down.