-
Notifications
You must be signed in to change notification settings - Fork 687
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
Fedora Atomic as base OS for SD #3492
Comments
Apparently @kushaldas already has done work on this, so I'm just gonna stop and wait for him to get back. |
Would also love your input here: https://forum.securedrop.club/t/architecture-rfc-securedrop-server-operating-system-transition/721 |
@heartsucker I will pass you the details on how to use my PoC tree to deploy |
hey @kushaldas did you get a chance to share these details with @heartsucker ? |
Feature request
Description
Related to the #3204 (xenial) and #2966 (libostree), it may be easier for us to make packages and deploy using full OS like Fedora Atomic instead of use a minimal environment like Yocto and starting from scratch.
This issue is mostly a place for me to keep track of my investigation.
User Research Evidence
Admins don't do manual updates quick enough, and our configuration logic is complex enough that we need to be able deploy major changes without admin intervention.
User Stories
As SD, I don't want to delay changes because they wouldn't be covered by an unattended upgrade.
As an SD dev, I don't want my changes rolled out of a release.
As SD, we want robust upgrades, especially if an OS is EOL.
The text was updated successfully, but these errors were encountered: