Skip to content
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

CAPVCD failure zones / node placement #3798

Closed
gawertm opened this issue Dec 5, 2024 · 7 comments
Closed

CAPVCD failure zones / node placement #3798

gawertm opened this issue Dec 5, 2024 · 7 comments
Assignees
Labels
team/rocket Team Rocket

Comments

@gawertm
Copy link

gawertm commented Dec 5, 2024

We might have to look into this at some point.

Context: https://gigantic.slack.com/archives/CE92C4BST/p1727765125494859

@vxav vxav added this to Roadmap Oct 1, 2024
@gawertm gawertm converted this from a draft issue Dec 5, 2024
@gawertm gawertm moved this from Inbox 📥 to Backlog 📦 in Roadmap Dec 5, 2024
@gawertm
Copy link
Author

gawertm commented Dec 5, 2024

placement policy exists in VCD machine template.
also the maintainers starting to work on zones, but not sure where they left off when leaving the project.
We should evaluate if we can use some feature like that or how much effort it would be to finish this feature

@anvddriesch anvddriesch self-assigned this Dec 9, 2024
@anvddriesch anvddriesch moved this from Backlog 📦 to In Progress ⛏️ in Roadmap Dec 9, 2024
@architectbot architectbot added the team/rocket Team Rocket label Dec 9, 2024
@anvddriesch
Copy link

placementPolicy: We can define this for vcd machine templates. It refers to a vm placement policy that needs to exist in the organisation already.
It appears that these placement policies work by being linked to vm groups that have specific affinites defined and therefore will place the vms according to these affinities.

failureDomain we can define this for vcd machine templates as well. However, the value needs to match to an entry in the map failureDomains in the vcd cluster status which in turn comes from the zones field in the multiZoneSpec of the vcd cluster.
it looks as though multiZoneSpec is implemented since it's present in the CRD and throughout the code as well. However, there are still some TODOs referring to the topology part like this one
making it look like it's not finished. I could not see any open issues (or closed issues for that matter actually) given more insight on the status.
I think we can just test these fields ourselves.

@gawertm
Copy link
Author

gawertm commented Dec 11, 2024

@anvddriesch
Copy link

placementPolicy is supported in the chart and can be used.
Xavier will ask neoedge to create a placement policy for us that we can reference for testing.

@vxav
Copy link

vxav commented Dec 11, 2024

Loris got back to me and said they can't really do it because it would mess a bit with the sheduling of the workloads since the environment is shared.

I'll ask the customer tomorrow during the sync if they can create the DRS groups, rules and placement policy to test it with Glasgow or Tamarin.

@vxav
Copy link

vxav commented Dec 11, 2024

I created an issue in the customer board with details on how this works
https://github.com/giantswarm/telekom-panamax/issues/337

@vxav
Copy link

vxav commented Dec 16, 2024

The feature is there. We can close in favor of ☝

@vxav vxav closed this as completed Dec 16, 2024
@github-project-automation github-project-automation bot moved this from In Progress ⛏️ to Done ✅ in Roadmap Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team/rocket Team Rocket
Projects
Status: Done ✅
Development

No branches or pull requests

4 participants