-
Notifications
You must be signed in to change notification settings - Fork 657
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
Add CPI method for native disk update #2555
Conversation
Certain cloud providers offer the capability to modify disk attributes like IOPS and throughput directly, eliminating the need to create a new disk. To accommodate this, this change introduces a new CPI method called update_disk. Previously, adjusting disk properties required creating a new disk and transferring the data, a process that could be time-consuming for larger disks. Should the CPI not support this new method, BOSH will revert to the traditional approach of disk creation. Co-authored-by: MSSedusch <[email protected]>
@s4heid, is this still in progress or is it ready for review? |
@jpalermo, it's ready for review, except for the integration tests which I couldn't set up locally, yet. |
Yeah, don't worry about the integration tests. We don't know how to run those either 😄 We can let CI take care of them once it's merged and fix anything that breaks. |
ping @nader-ziada regarding review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. change makes sense and tests worked for me
it seems like this change may be breaking integration tests:
There are similar failures for the non-hotswap integration suites. |
What is this change about?
Certain cloud providers offer the capability to modify disk attributes (e.g. IOPS and throughput) directly, eliminating the need to create a new disk. To accommodate this, this change introduces a new CPI method called
update_disk
. Previously, adjusting disk properties required creating a new disk and transferring the data, a process that could be time-consuming for larger disks. Should the CPI not support this new method, BOSH will revert to the traditional approach of disk creation.Please provide contextual information.
What tests have you run against this PR?
update_disk
I couldn't get the integration tests running on my system (yet).
How should this change be described in bosh release notes?
Enables direct update of disk properties through the Cloud Provider if supported, significantly speeding up large disk updates.
Does this PR introduce a breaking change?
No, this change is compatible with older versions.
Tag your pair, your PM, and/or team!
@MSSedusch