Skip to content

Conversation

@mandre
Copy link
Collaborator

@mandre mandre commented Jan 16, 2026

This changes the Port API to use a structured hostID field instead of a simple string, allowing users to specify the host ID either directly or by referencing a Server resource.

This changes the Port API to use a structured hostID field instead
of a simple string, allowing users to specify the host ID either
directly or by referencing a Server resource.
@github-actions github-actions bot added the semver:major Breaking change label Jan 16, 2026
@mandre
Copy link
Collaborator Author

mandre commented Jan 16, 2026

@winiciusallan I'd like your feedback on this. Related to my concerns in #626.

@winiciusallan
Copy link
Contributor

@mandre I have some questions just to clarify my thoughts and to ensure that we're on the same page.

Could you point out a use case where I would retrieve the host ID from a running server? Making some tests on my multinode environment, if I do:

create port A binded to host A -> create a server with port A into host B

Openstack will change the binding:host_id to the host B on port A, because to a port become UP as long as I know, it must be attached on the same host as the VM. So, now I'm wondering if we really want to expose this field and if a use case for that exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

semver:major Breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants