-
Notifications
You must be signed in to change notification settings - Fork 256
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 EphemeralDisk to InstanceSpec #1640
Conversation
✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Hi @EmilienM. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: EmilienM The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
EphemeralDisk
to OpenStackMachineSpec
EphemeralDisk
to OpenStackMachineSpec
This is just a prototype for now. Also for some reasons I can't make the conversion working yet. |
EphemeralDisk
to OpenStackMachineSpec
/ok-to-test |
d4e1f62
to
665ef6b
Compare
/uncc seanschneeweiss jichenjc |
/cc pierreprinetti mdbooth dulek |
struggling a bit with the conversion & their tests... |
You might need to restore the value during up conversion like this PR #1517 |
for new spec I suggest create an issue to track the proposed change and create release notes for it... @EmilienM |
Couple of things to think about: There's prior art here: https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/e7773fe017f3493be65c3368808d726a6343911e/api/v1beta1/azuremachine_types.go#L77-L82 It might be worth considering using the same terminology unless there's a good reason to do otherwise. Also consider: how do I specify that I want a secondary disk and it's the nova local disk, vs it's a cinder disk? I suppose it might be neater to give the local disk a separate field in the API because there can only be one of them, vs any number of cinder disks. I believe the CAPZ folks have done the whole thing end-to-end, i.e. they're also able to mount the disk. Might be worth looking into how they did that. |
It occurs to me that to use a local disk as a data disk it could just be a flag. I'm not sure we need to specify the size of the local disk. We can just take whatever we're given by the flavor. It is possible to specify a smaller disk than the one the flavor gave you, but:
If we added to machine spec something like
Footnotes |
An additional block device can be attached to the instance. It won't be bootable and only optional. It can be added aside of a `RootVolume` or not. ```yaml apiVersion: infrastructure.cluster.x-k8s.io/v1alpha7 kind: OpenStackMachineTemplate metadata: name: <cluster-name>-controlplane namespace: <cluster-name> spec: ... ephemeralDisk: format: "ext4" size: 10 ... ``` The local disk will be deleted when the instance is removed.
/hold |
PR needs rebase. 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. |
What this PR does / why we need it:
An additional block device can be attached to the instance. It won't be bootable and only optional.
It can be added aside of a
RootVolume
or not.The local disk will be deleted when the instance is removed.
A use case is when having etcd running on machines that boot from volumes, you can now have a dedicated local disk with higher I/O for it.