iSCSI SBPS: Fallback to default IMS user policy for CPS #302
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…th IMS user policy - Disable mount_s3_images role for now in order to default to earlier s3fs mount of boot-images bucket with IMS user policy to allow CPS with write access to "/var/lib/cps-local/boot-images" mount path. We can enable this role once CPS is removed in USS-1.3.
ravikanth-nalla-hpe
requested review from
mharding-hpe,
dborman-hpe and
leliasen-hpe
mharding-hpe
approved these changes
Sep 12, 2024
4 tasks
leliasen-hpe
approved these changes
Sep 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary and Scope
CASMPET-7225: Fallback to default IMS user policy for CPS
We must have writable access to "/var/lib/cps-local/boot-images" mount directory of "boot-images" bucket order for CPS to function. CPS creates cos-config-data under "/var/lib/cps-local/boot-images"(information for the contents projected by DVS. User also need write access while removing cos-config-data under "/var/lib/cps-local/boot-images", when he wants to disable CPS.
Since for CSM-1.6 and USS-1.2 we are supporting CPS, we need to make it writable. When CPS will be removed in USS-1.3, we can fallback again to dedicated s3fs read-only policy.
Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.
<insert branch name here><insert PR URL here>Testing
bare metal cluster surtur
Tested on:
surtur
Test description:
Risks and Mitigations
None
Pull Request Checklist