Skip to content

Support VolumesV3 for OpenStack cloud Provider #52877

Closed
@FengyunPan

Description

Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature
/sig openstack
/assign

What happened:
Currently OpenStack support cinder v3 API,but OpenStack cloud Provider just support cinder v1 API and cinder v2 API. We konw that cinder v1 API and cinder v2 API have been deprecated. So it is necessary to support VolumesV3 for OpenStack cloud Provider.

cinder v1 API(deprecated):
https://specs.openstack.org/openstack/cinder-specs/specs/juno/deprecate_v1_api.html

cinder v2 API(deprecated):
https://developer.openstack.org/api-ref/block-storage/v2/

cinder v3 API(current):
https://developer.openstack.org/api-ref/block-storage/v3/

What you expected to happen:

  1. The Cinder V1 API has been deprecated long time as v2 has been developed back in Grizzly and stable, so deprecate VolumesV1 for OpenStack cloud Provider now.
  2. Many large OpenStack user also use LBaaSV2 in production, just keep it.
  3. Support VolumesV3

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:
We have talked loog time: #50239 #49318
I'd like to start this work now.

Environment:

  • Kubernetes version (use kubectl version): v1.7.3
  • Cloud provider or hardware configuration**:
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:

Metadata

Assignees

Labels

area/provider/openstackIssues or PRs related to openstack providerkind/featureCategorizes issue or PR as related to a new feature.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions