Skip to content

feat: creating neutron objects in openstack using ansible #936

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

haseebsyed12
Copy link
Contributor

@haseebsyed12 haseebsyed12 commented May 19, 2025

  1. openstack network segment ranges (check existing) and one segment range (just one for the whole fabric) for vxlan type segments
  2. subnet pool for the OUTSIDE networks.
  3. Baremetal nodes and their baremetal ports in ironic for the three "infra" nodes.
  4. Each of the nodes needs neutron ports, (trunks with sub-ports where required) associated with the appropriate networks.

configurations are in undercloud-deloy repo
output log for playbook openstack_network.yml
output log for playbook openstack_baremetal.yml

@haseebsyed12 haseebsyed12 force-pushed the ansible-network-infrastructure branch 4 times, most recently from 058c5f6 to f900e17 Compare May 20, 2025 12:05
Copy link
Contributor

@stevekeay stevekeay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this need to be different playbooks for neutron/ironic? Is that a technical limitation in ansible?

It seems like we would want all of this or none of this, I can't see a scenario where we would want to populate ironic but not neutron.

@haseebsyed12 haseebsyed12 force-pushed the ansible-network-infrastructure branch from f900e17 to beebc4a Compare May 22, 2025 17:37
@haseebsyed12 haseebsyed12 requested a review from stevekeay May 22, 2025 17:39
@haseebsyed12 haseebsyed12 marked this pull request as ready for review May 22, 2025 17:39
@haseebsyed12 haseebsyed12 requested a review from a team May 22, 2025 17:39
@haseebsyed12 haseebsyed12 force-pushed the ansible-network-infrastructure branch from beebc4a to 4f37012 Compare May 28, 2025 00:49
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.

2 participants