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

leave FD unassigned in the launch instance call #351

Closed
QiangZhangO opened this issue Feb 27, 2024 · 0 comments · Fixed by #352
Closed

leave FD unassigned in the launch instance call #351

QiangZhangO opened this issue Feb 27, 2024 · 0 comments · Fixed by #352
Labels
enhancement New feature or request

Comments

@QiangZhangO
Copy link

What would you like to be added:
it looks CAPOCI set a random number for FD before launch a new instance https://github.com/oracle/cluster-api-provider-oci/blob/main/cloud/scope/machine.go#L203-L212. We'd like to know if it is feasible to leave FD unassigned

Why is this needed:
in PCA/C3 env, the number of compute nodes might be uneven across Fault Domain. It might happen that some FD is full, while there are resources on the other two FDs. Compute team suggests to launch instance without specifying the fault domain so that compute service will distribute VMs based on availability across all FDs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
1 participant