Actions
Task #7992
closed
Document the process of migrating to a FIPS-enabled machine
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation
Sprint:
Sprint 104
Quarter:
Q3-2021
Description
Explain the following use case
- As a user, when I migrate from Pulp 2, I get the default set of checksums that I can then later modify
- In other words, we will migrate all of the checksum information from Pulp 2
And the steps user would need to perform if the system they migrate to has a non-default set of checksums allowed.
Updated by daviddavis over 3 years ago
Talked to ggainey and we decided we could detach this from the epic in order to close the epic out.
Updated by ttereshc about 3 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to ttereshc
- Sprint set to Sprint 104
Added by ttereshc about 3 years ago
Added by ttereshc about 3 years ago
Revision 67f7b502 | View on GitHub
Add a note about migrating to a FIPS machine.
Added by ttereshc about 3 years ago
Revision 67f7b502 | View on GitHub
Add a note about migrating to a FIPS machine.
Updated by ttereshc about 3 years ago
- Status changed from ASSIGNED to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp:pulp-2to3-migration|67f7b502a5755640fdf795f80885a6c1f1352f67.
Updated by pulpbot about 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
Add a note about migrating to a FIPS machine.
closes #7992 https://pulp.plan.io/issues/7992