Skip to content

Conversation

@bobfuru
Copy link
Contributor

@bobfuru bobfuru commented Jun 8, 2020

OSDOCS-1017
Adds 4.5 OCP Storage features to 4.5 Release Notes:
• CSI AWS EBS Operator (TP)
• CSI Inline Ephemeral Volumes (TP)
• CSI Manila Operator (GA)
• CSI Cloning GA

Also updates the TP tracker table

Preview build: http://file.rdu.redhat.com/bfuru/061120/OSDOCS-1017/release_notes/ocp-4-5-release-notes.html

@bobfuru bobfuru added this to the Next Release milestone Jun 8, 2020
@bobfuru bobfuru force-pushed the OSDOCS-1017 branch 4 times, most recently from fcdd1ed to 73a209f Compare June 8, 2020 18:39
@bobfuru
Copy link
Contributor Author

bobfuru commented Jun 8, 2020

@jsafrane and @qinpingli PTAL - links to docs for AWS EBS and Manila CSI Operators will be added in their related Release Notes entries when those Operator PRs are approved/merged for 4.5. Thanks!

@bobfuru
Copy link
Contributor Author

bobfuru commented Jun 8, 2020

@openshift/team-documentation PTAL

@bobfuru bobfuru added the peer-review-needed Signifies that the peer review team needs to review this PR label Jun 8, 2020
@bmcelvee bmcelvee added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Jun 8, 2020
@bmcelvee
Copy link
Contributor

bmcelvee commented Jun 8, 2020

LGTM

@qinpingli
Copy link

@bobfuru For External provisioner for AWS EFS feature, I can confirm this feature is dropped from 4.4. But there is a user story in 4.2, so I don't know if we should move this feature to "Table 1".

@bobfuru
Copy link
Contributor Author

bobfuru commented Jun 9, 2020

@bobfuru For External provisioner for AWS EFS feature, I can confirm this feature is dropped from 4.4. But there is a user story in 4.2, so I don't know if we should move this feature to "Table 1".

@qinpingli By "dropped", do you mean "deprecated" (not "removed")? Also, which user story are you referring to in 4.2?

Based on your suggestion, I moved it from Table 2 to Table 1, indicating that it was still TP in 4.3 but deprecated in 4.4 and 4.5. If that is correct, we should probably also update 4.4 Release Notes.

Also, step 1 in the Persistent storage using AWS EFS -> Create the EFS provisioner procedure includes the quay.io/external_storage/efs-provisioner:latest container image in the spec. Based on this change for EFS external provisioner, is this sample still correct?

@qinpingli
Copy link

@bobfuru For External provisioner for AWS EFS feature, I can confirm this feature is dropped from 4.4. But there is a user story in 4.2, so I don't know if we should move this feature to "Table 1".

@qinpingli By "dropped", do you mean "deprecated" (not "removed")? Also, which user story are you referring to in 4.2?

Based on your suggestion, I moved it from Table 2 to Table 1, indicating that it was still TP in 4.3 but deprecated in 4.4 and 4.5. If that is correct, we should probably also update 4.4 Release Notes.

Also, step 1 in the Persistent storage using AWS EFS -> Create the EFS provisioner procedure includes the quay.io/external_storage/efs-provisioner:latest container image in the spec. Based on this change for EFS external provisioner, is this sample still correct?

@bobfuru
This is another PR to follow this. #22524 (comment)

user story about efs: https://issues.redhat.com/browse/OSDOCS-306

@bobfuru
Copy link
Contributor Author

bobfuru commented Jun 10, 2020

@qinpingli Based on your comment in PR 22524, it sounds to me like EFS should be DEP in 4.2 and 4.3 because it wasn't tested, and - (Removed) in 4.4 and 4.5 because the image is not available for customers.
Two questions for you:

  1. Is this a correct assessment? If so, I'll work with Cody to accurately reflect this info in 4.2+ Release Notes tables.
  2. What does this mean for the 4.x EFS documentation (https://docs.openshift.com/container-platform/4.4/storage/persistent_storage/persistent-storage-efs.html)? Should all of it be removed starting from 4.4?

@codyhoag
Copy link
Contributor

codyhoag commented Jun 10, 2020

@bobfuru I synced with @huffmanca on this today. There should be clarifications coming for this soon. As I understand it, QE didn't test the AWS EFS provisioner for 4.x; however, I've heard it was still included in several versions of 4.x. Since it is TP, I don't think we can deprecate it in 4.2/4.3 because it was never supported. It would just go from TP → dropped.

@bobfuru
Copy link
Contributor Author

bobfuru commented Jun 10, 2020

Thanks, @codyhoag! Makes sense to move it from TP -> REM... seems that should be starting in 4.3.

@qinpingli
Copy link

qinpingli commented Jun 11, 2020

@qinpingli Based on your comment in PR 22524, it sounds to me like EFS should be DEP in 4.2 and 4.3 because it wasn't tested, and - (Removed) in 4.4 and 4.5 because the image is not available for customers.
Two questions for you:

  1. Is this a correct assessment? If so, I'll work with Cody to accurately reflect this info in 4.2+ Release Notes tables.

Thanks, Bob. the assessment lgtm.

  1. What does this mean for the 4.x EFS documentation (https://docs.openshift.com/container-platform/4.4/storage/persistent_storage/persistent-storage-efs.html)? Should all of it be removed starting from 4.4?

I agree with remove it starting from 4.4.

@bobfuru
Copy link
Contributor Author

bobfuru commented Jun 11, 2020

@qinpingli
Based on feedback from PM/Dev (#22524 (comment)), I'm going to leave the docs in 4.4 and @codyhoag will keep EFS as TP in the Release Notes for 4.2+. We can revisit when EFS is included in a CSI driver.

I've grouped all storage-related features in the same part of the Tech Preview Tracker table 2.

Can you please give it a final review and let me know if it looks good to you?

@jsafrane
Copy link
Contributor

@bobfuru lgtm

@bobfuru bobfuru merged commit 5e44283 into openshift:enterprise-4.5 Jun 15, 2020
@bobfuru bobfuru deleted the OSDOCS-1017 branch March 12, 2021 21:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.5 peer-review-done Signifies that the peer review team has reviewed this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants