-
Notifications
You must be signed in to change notification settings - Fork 11
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
Copyediting and URL updates #17
Conversation
Signed-off-by: Jorge O. Castro <[email protected]>
I will also feature bootable to awesome_atomic, see Malix-Labs/awesome_atomic#76 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cgwalters What do you think? I think you also had nuanced opinions about the word "immutable".
I'll merge tomorrow unless you have some more review points.
@@ -24,7 +25,7 @@ The system either uses the contents of the old system, or the new image; Never s | |||
Updates can be delayed or scheduled. | |||
This default behavior can be adapted or controlled by a larger management system. | |||
|
|||
1. If an update does not function correctly it is possible to roll back to the container image previously functioning before the update. | |||
1. If an update does not function correctly it is possible to roll back to the container image previously functioning before the update, or to any previously bootable version in the registry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@castrojo Is this really a roll back though? @cgwalters Can we roll back to another version in the registry, or only what's on the system?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're doing this in practice with our images but now that you bring it up I'm not sure how officially supported that is.
The use case is usually when people don't have a pinned snapshot or didn't realize they had a regression on something. The it's useful to be able to grab a remote older version to try to pin down where the regression happened.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
switch
and rollback
I think are 99% equivalent for this. (The difference is if there's any local changes in /etc
that were made between the operations)
See “Immutable” → reprovisionable, anti-hysteresis, (and other atomic blog and publications) |
Bootable containers are a modern opinionated way of deploying, configuring and managing immutable image based Linux systems. | ||
Bootable containers are a modern opinionated way of deploying, configuring and managing image based Linux systems. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing this!
It's a challenge since I think the usage of "immutable" is widespread in the industry still years later. My high level thoughts is that it's a word that is only useful at a very introductory level but once you get past the surface it can be more misleading than helpful.
So 👍 to dropping it here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, although I am not sure there is another word that is helpful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Atomic / Image-based Linux systems #17 (comment)
No description provided.