Bug 1566203

Summary: [RFE] Spineleaf: Assigning ports to physical networks should occur automatically on undercloud.
Product: Red Hat OpenStack Reporter: Alexander Chuzhoy <sasha>
Component: openstack-tripleo-commonAssignee: OSP Team <rhos-maint>
Status: CLOSED WONTFIX QA Contact: Alexander Chuzhoy <sasha>
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: bfournie, chrisw, hjensas, mburns, mlammon, pweeks, slinaber, srevivo
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-08-17 20:15:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alexander Chuzhoy 2018-04-11 18:44:14 UTC
Currently deploying with multiple provisioning networks requires manually assigning ports to the respective leaf. It's done with:


Find out which baremetal ports are associated with which baremetal node. 
1. openstack baremetal node show <node-uuid>
2. openstack baremetal port show <port-uuid>
3. Set the node to maintenance mode
4. Then set the ``physical-network`` for the ports like below:
    openstack baremetal port set --physical-network <leaf> <port-uuid>

Would be nice if the above happens automatically based on the IP found on introspected nodes and the leaf range it was assigned from.

Comment 1 Harald Jensås 2018-04-16 12:02:45 UTC
In the Undercloud we currently always have a neutron provisioning network/subnet that we could use to resolve the physical_network based on the IP recieved during introspection. However -- Ironic and Ironic Inspector does not need to be configured this way. We may use a completely separate ip-subnet for introspection, and we may even run introspection on a different interface, e.g different physical_network. I can't see a sound way to implement this generically in Ironic Inspector in a way that would work for the diverse configurations.

I am not sure it is the best thing to go with the assumptions of Undercloud Ironic/Inspector configuration as it is today, and implement this in tripleo. What if we want to change Undercloud to allow more flexibility in the future? I am worried that this feature could complicate that, and we may end up with inconsistency where in some configurations the physical_network is automatically set, while in others it is not set.

Comment 4 pweeks 2021-08-17 20:15:53 UTC
no progress for 3 years
reduction in capacity impacting backlog priorities
closing wontfix
please reopen should this require attention.