-
Notifications
You must be signed in to change notification settings - Fork 261
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
🐛 Don't require cinder when not using volumes #1353
🐛 Don't require cinder when not using volumes #1353
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mdbooth The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
||
type volumeErrorClient struct{ error } | ||
|
||
// NewVolumeErrorClient returns a VolumeClient in which every method returns the given error. |
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.
I like the idea , create such error client should help abstract the error case
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.
I wanted to create a proper monad, but that's not ergonomic in Go. This seemed like a fairly neat alternative.
/lgtm |
/hold cancel |
088b615
to
8974455
Compare
Implement lazy initialisation of each in compute service.
8974455
to
68474a1
Compare
@jichenjc Had to fix a couple of merge conflicts, but nothing consequential. Appreciate it if you could have a look and restore your lgtm. |
/lgtm lgtm, hold this wait for CI and please unhold when you think it's ok after CI pass @mdbooth |
/hold cancel |
@tobiasgiese thanks :) |
…upport 🐛 Don't require cinder when not using volumes
/cherry-pick release-0.6 |
@jichenjc: #1353 failed to apply on top of branch "release-0.6":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
plan to cherry pick this for 0.6 but encounter many conflict ... |
What this PR does / why we need it:
The addition of multi-AZ volume support inadvertently added a hard requirement for Cinder. This change removes that requirement by:
If a machine definition does not use volumes the VolumeClient will not be initialised, meaning Cinder is no longer a requirement.
Which issue(s) this PR fixes:
Fixes #1345
Special notes for your reviewer:
It might be simpler to review these 2 commits separately. I pulled the first one out of one of my other outstanding PRs #1236. The separation of clients which I did in that PR for other reasons works very nicely for this, too.
The first commit is mostly code motion. The second commit implements the change.
/hold