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

WIP: Hypervisor per ESXI #423

Draft
wants to merge 4 commits into
base: stable/xena-m3
Choose a base branch
from
Draft

Conversation

fwiesel
Copy link
Member

@fwiesel fwiesel commented May 2, 2023

No description provided.

You can configure now
[vmware]
hypervisor_mode=<cluster,esxi_to_cluster,cluster_to_esxi>

to chose to expose the individual esxi hosts instead of the cluster.
It will only show the esxi-host, as hypervisor node, but will not
honour the node parameter for placeing the instance for instance-creation,
migration, etc...

Change-Id: I264fd242c0de01ae8442c03bc726a0abfbe176ef
The code assumes that there is a single compute-node per host,
which is incorrect for ironic. By summarising over all hosts,
we get a correct response also for compute-hosts with more than
one compute-node.

Change-Id: Iaf6e2a72f6649e234660de47bec8b1da1ea1571e
The driver and scheduler support conceptually multiple nodes
per compute host, but the resize api assumes a single node
per host as the only case of multiple nodes per host is ironic,
which does not support resizing or migration for obvious reasons.

This removes the assumption to fix resize/cold-migration on
hypervisors, which may support it (eventually vmware)

Change-Id: I9200dfea623458865f289c25fa5fb06a2140b1cb
Change-Id: I1f118e639e69d0556fbfb0980ff0340d7525a003
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.

1 participant