Skip to content

new feature qemu-scheduler #102

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

Merged
merged 15 commits into from
Oct 31, 2023
Merged

new feature qemu-scheduler #102

merged 15 commits into from
Oct 31, 2023

Conversation

sp-yduck
Copy link
Collaborator

@sp-yduck sp-yduck commented Oct 15, 2023

fix #101

To specify vmid range or node name, we can use certain annotation for it. for example

# ProxmoxMachine
apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
kind: ProxmoxMachine
metadata:
    name: sample-machine
    annotations:
        vmid.qemu-scheduler/range: 100-150 # this means your vmid will be chosen from the range of 100 to 150.

when you use MachineDeployment you can use spec.template.metadata.annotations since cluster api propagates this values to your ProxmoxMachine.

# MachineDeployment
apiVersion: cluster.x-k8s.io/v1beta1
kind: MachineDeployment
metadata:
  annotations:
    caution: "# do not use here, because this annotation won't be propagated to your ProxmoxMachine"
  name: sample-machine-deployment
spec:
  template:
    metadata:
      annotations:
        node.qemu-scheduler/regex: node[0-9]+ # this annotation will be propagated to your ProxmoxMachine via MachineSet

@sp-yduck sp-yduck marked this pull request as ready for review October 21, 2023 13:54
@sp-yduck sp-yduck mentioned this pull request Oct 21, 2023
@sp-yduck sp-yduck merged commit 483062e into main Oct 31, 2023
@sp-yduck sp-yduck deleted the feature/qemu-scheduler branch October 31, 2023 09:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support flexible vmid/node management solution
1 participant