Skip to content

Add Multinode CI job for intree cinder driver to CSI driver migration #342

@adisky

Description

@adisky

What is your focus?

  • Performance
  • Scale
  • Reliability
  • Resiliency
  • Integration
  • Multi-Cloud
  • Operational Tooling
  • Edge or IoT
  • Machine Learning
  • Artificial Intelligence
  • Application Ecosystem
  • Other

If this is for an open source project what is it?

cloud-provider-openstack

Brief project description

Is project code 100% open source? If so, what is the URL or URLs where it is located?

https://github.com/kubernetes/cloud-provider-openstack

What kind of machines (VMs or Baremetal) and how many do you expect to use?

VM's 3

What OS are you planning to use?

ubuntu-xenial

Any special network configuration you expect or anticipate implementing?

Any architecture or other specifications/requirements (CPU, RAM, GPU, etc)?

What testing are you planning to implement or need assistance implementing?

All intree volume driver would be eventually removed from Kubernetes, due to strict API policy of kubernetes,intree volume API's cannot be removed, to solve this, all api calls to intree volume API is migrated to corresponding Cinder Driver, to promote cinder migration to beta, we need to setup a consistent running CI jobs, with migration flags enabled
https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/20190129-csi-migration.md

How will this testing advance application and/or tooling built on-top of open infrastructure?

Will you publish blog or paper from your testing?

  • Yes
  • No - if no, how will you present your results?

Any other relevant details we should know about while preparing the infrastructure?

Metadata

Metadata

Labels

integration caseSomething want to test in OpenLab

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions