Release v2.1.0 of Ceph CSI driver.

[humblec]

• Define release process

  • Release doc would be a good start

• Define release deadlines

  • Code Freeze : 15-Mar-2020
  • RC : 22-Mar-2020
  • GA : 31-Mar-2020

• Define/list roadmap for v2.1.0

  • Proposed contents for v.2.1.0 release

• Dependency update to kube v1.17
  status: Completed

• Support Mountoptions in RBD
  status: Completed

• Migrate to go mode from dep
  status: Completed

• Update all sidecars to latest version
  status: Completed

• Refactor helm charts
  status: PR under review

• Snapshot/Cloning support for CephFS and RBD.
  Add snapshot creation, deletion and restore from snapshot, Clone from PVC support for CephFS volumes. #394
  create a bigger size volume from existing data source #258
  [CephFS] Support volume cloning #701
  [CephFS] Create a CSI volume from a snapshot #411
  [CephFS] Support Volume Snapshots #702
  Add support for smart cloning in rbd #675
  Add support for standalone snapshot creation and cloning support #693
  Add support for smart PVC cloning #695

status: Deferred to v3.0.0

• Topology Aware Provisioning.
  Make Ceph-CSI topology aware.  #440
  status: PR under review

• Native Client ( Go client) Support-
  Can the CSI RBD plugin catch up in terms of performance to native CLI calls? #449
  Status: CreateVolume support is completed, Delete Volume support is under review

• Locking support for RBD volumes which are RWO
  Add the ability to use exclusive RBD locking to prevent inadvertent multi-node access of an RWO image #578

• Release Team:
  @Madhu-1
  @humblec

  • The release blockers (issues/PRs) are labeled with release-2.1.0.

• Document features and announce the release.

[ntolia]

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

• Add support for smart cloning in rbd #675 (tagged with the 2.1.0 release label)
• Add support for standalone snapshot creation and cloning support #693 (linked from Add support for smart cloning in rbd #675 but not labeled)

[humblec]

@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]

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]

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]

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]

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]

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]

[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]

[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]

[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]

[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]

[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]

[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