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

Documents simpler upgrade testing workflow #227

Merged
merged 1 commit into from Jun 8, 2021

Conversation

conorsch
Copy link
Contributor

@conorsch conorsch commented May 24, 2021

Status

Ready for review

Description of Changes

Tracks changes in the provisioning/testing logic:

  • Removes maintenance of the custom VM images
  • Uses Molecule to manage prod VMs
  • Removes use of vagrant (prefer molecule)

Should be reviewed in tandem with freedomofpress/securedrop#5960, see test plan over there.

Testing

Consult test plan in freedomofpress/securedrop#5960

Release

Dev-only.

Checklist (Optional)

  • Doc linting (make docs-lint) passed locally
  • Doc link linting (make docs-linkcheck) passed
  • You have previewed (make docs) docs at http://localhost:8000

@conorsch conorsch marked this pull request as ready for review May 24, 2021 18:27
@conorsch conorsch added this to Ready for Review in SecureDrop Team Board May 24, 2021
Copy link
Contributor

@zenmonkeykstop zenmonkeykstop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple of small nits, but the process as documented works great!

You can use this scenario to test the upgrade process, using using either
locally-built .debs or packages from the FPF test repo at
https://apt-test.freedom.press/. Both options are described below.
The Molecule upgrade scenario sets up local apt server, to imitate
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: "sets up a local apt server"

https://apt-test.freedom.press/. Both options are described below.
The Molecule upgrade scenario sets up local apt server, to imitate
how new package versions will be installed in production. You'll need
to a virtualized Admin Workstation to configure the base server VMs
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: "you'll need to use a virtualized"

Tracks changes in the provisioning/testing logic:

  * Removes maintenance of the custom VM images
  * Uses Molecule to manage prod VMs
  * Removes use of `vagrant` (prefer `molecule`)
@conorsch
Copy link
Contributor Author

conorsch commented Jun 8, 2021

Thanks for the close read! Both comments now addressed.

@zenmonkeykstop zenmonkeykstop merged commit 4634592 into main Jun 8, 2021
SecureDrop Team Board automation moved this from Ready for Review to Done Jun 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

None yet

2 participants