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

Release v2.1.0 of Ceph CSI driver. #806

Closed
12 of 14 tasks
humblec opened this issue Jan 22, 2020 · 20 comments
Closed
12 of 14 tasks

Release v2.1.0 of Ceph CSI driver. #806

humblec opened this issue Jan 22, 2020 · 20 comments

Comments

@humblec
Copy link
Collaborator

humblec commented Jan 22, 2020

status: Deferred to v3.0.0

@ntolia
Copy link

ntolia commented Feb 7, 2020

@humblec @Madhu-1 Will this release also include the following issues and will Ceph CSI RBD snapshots enter beta in this release?

@humblec
Copy link
Collaborator Author

humblec commented Feb 11, 2020

@ntolia planning to get these in next feature based release. Unless there is a concern from community about having features in minor release ( y release), this should be part of 2.1.0.

@ntolia
Copy link

ntolia commented Feb 11, 2020

Thanks @humblec. If we truly are following SemVer and not doing breaking changes (snapshots is alpha anyway and can be broken though), I think we should be good, right? Looking forward to 2.1.0!

@dillaman
Copy link

If we truly are following SemVer and not doing breaking changes (snapshots is alpha anyway and can be broken though), I think we should be good, right? Looking forward to 2.1.0!

Snapshots is beta in k8s v1.17 and cloning is beta in v1.16.

@ntolia
Copy link

ntolia commented Feb 12, 2020

If we truly are following SemVer and not doing breaking changes (snapshots is alpha anyway and can be broken though), I think we should be good, right? Looking forward to 2.1.0!

Snapshots is beta in k8s v1.17 and cloning is beta in v1.16.

@dillaman What I have found is that there is K8s snapshots support and then Ceph CSI snapshot support. The latter is still in alpha from what I can make out.

@humblec
Copy link
Collaborator Author

humblec commented Feb 12, 2020

Thanks @humblec. If we truly are following SemVer and not doing breaking changes (snapshots is alpha anyway and can be broken though), I think we should be good, right? Looking forward to 2.1.0!

Yeah, that is ( snapshot is still in alpha) our escape path :) , however couple of things around it like , having some responsibility for the code we have here, bringing or wiping all the instance of previous spec of snapshots from the code..etc need some thought. figuring out the same meanwhile,

@humblec
Copy link
Collaborator Author

humblec commented Feb 12, 2020

If we truly are following SemVer and not doing breaking changes (snapshots is alpha anyway and can be broken though), I think we should be good, right? Looking forward to 2.1.0!

Snapshots is beta in k8s v1.17 and cloning is beta in v1.16.

@dillaman What I have found is that there is K8s snapshots support and then Ceph CSI snapshot support. The latter is still in alpha from what I can make out.

True, thats correct.

@humblec
Copy link
Collaborator Author

humblec commented Mar 4, 2020

[Release call update]
There is a GA date change or slip of 2 weeks to accommodate couple of important features or bug fixes. We are also planning to release v2.0.1 in between.

@humblec
Copy link
Collaborator Author

humblec commented Mar 17, 2020

[Release call update]
The final decision here is to release v2.1.0 as planned with bug fixes/enhancements ..etc and defer couple of features ( snap/clone) from this release to v3.0.0 as we are currently revalidating the design/implementation of those features in depth to support some more use cases which have to be supported in near future.

@Madhu-1 please add details if I missed any.

@hoytk
Copy link

hoytk commented Mar 17, 2020

[Release call update]
The final decision here is to release v2.1.0 as planned with bug fixes/enhancements ..etc and defer couple of features ( snap/clone) from this release to v3.0.0 as we are currently revalidating the design/implementation of those features in depth to support some more use cases which have to be supported in near future.

@Madhu-1 please add details if I missed any.

@Mandu-1 @humblec Does this mean that 2.1.0 will not be able to create/delete RBD snapshots at all?
Per the struck out list above, looks like there will not be any snapshot support... Obviously need to know to evaluate the impact to my project.

@ntolia
Copy link

ntolia commented Mar 17, 2020

[Release call update]
The final decision here is to release v2.1.0 as planned with bug fixes/enhancements ..etc and defer couple of features ( snap/clone) from this release to v3.0.0 as we are currently revalidating the design/implementation of those features in depth to support some more use cases which have to be supported in near future.

@Madhu-1 please add details if I missed any.

What is the timeline for v3.0.0? And, given the previous slips, is there a risk that these features might not show up in 3.0 too? I understand this is a complex feature and just trying to get a timeline estimate to plan better on our side.

@Madhu-1
Copy link
Collaborator

Madhu-1 commented Mar 18, 2020

[Release call update]
The final decision here is to release v2.1.0 as planned with bug fixes/enhancements ..etc and defer couple of features ( snap/clone) from this release to v3.0.0 as we are currently revalidating the design/implementation of those features in depth to support some more use cases which have to be supported in near future.

@Madhu-1 please add details if I missed any.

LGTM

@Madhu-1
Copy link
Collaborator

Madhu-1 commented Mar 18, 2020

[Release call update]
The final decision here is to release v2.1.0 as planned with bug fixes/enhancements ..etc and defer couple of features ( snap/clone) from this release to v3.0.0 as we are currently revalidating the design/implementation of those features in depth to support some more use cases which have to be supported in near future.
@Madhu-1 please add details if I missed any.

What is the timeline for v3.0.0? And, given the previous slips, is there a risk that these features might not show up in 3.0 too? I understand this is a complex feature and just trying to get a timeline estimate to plan better on our side.

as more info about 3.0.0 is here #865

@lwj5
Copy link

lwj5 commented Mar 18, 2020

Will CephFS provisioning be going beta as planned?

@humblec
Copy link
Collaborator Author

humblec commented Apr 1, 2020

Will CephFS provisioning be going beta as planned?

Yeah, CephFS provisioning will be be moving to Beta with this release.

@humblec
Copy link
Collaborator Author

humblec commented Apr 7, 2020

[Release call update from 03-Apr-2020]

We have confirmed the release of 2.1.0 on 8-Apr-2020, unless there is a severity blocker issue which break the existing deployments..etc.

6 more important PRs to get in. Most of them are in final stage of review, so we should be able to release on time.

@Madhu-1 please add if I missed any.

@Madhu-1
Copy link
Collaborator

Madhu-1 commented Apr 7, 2020

[Release call update from 03-Apr-2020]

We have confirmed the release of 2.1.0 on 8-Apr-2020, unless there is a severity blocker issue which break the existing deployments..etc.

6 more important PRs to get in. Most of them are in final stage of review, so we should be able to release on time.

@Madhu-1 please add if I missed any.

we are good, we have one release blocker issue #904

@humblec
Copy link
Collaborator Author

humblec commented Apr 13, 2020

[Release call update]

Finally we are good to go! The release is expected to happen 14-Apr-2020 👍 , we are on final push .. thanks !

@Madhu-1
Copy link
Collaborator

Madhu-1 commented Apr 15, 2020

closing this issue as the release is out https://github.com/ceph/ceph-csi/releases/tag/v2.1.0

@Madhu-1 Madhu-1 closed this as completed Apr 15, 2020
@humblec
Copy link
Collaborator Author

humblec commented Apr 15, 2020

Thanks all who helped with this awesome release !! 💯

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants