Hi, I copied the simplified yamls to an etherpad: https://etherpad.opendev.org/p/Trunk_creation_with_resourceGroup We tried to move the nested stack (subports.yaml) into stack.yaml but we were not able to solve the problem so I believe the issue is not coming from the "nestedness" of the resourceGroup. Thanks in advance for the help. Lajos Katona (lajoskatona) Takashi Kajinami <kajinamit@oss.nttdata.com> ezt írta (időpont: 2024. márc. 25., H, 5:46):
Do you mind sharing your (partial) template so that I can dig into it ? (It'd be nice if you can open a bug in storyboard[1])
[1] https://storyboard.openstack.org/#!/project/openstack/heat
I've not tried the said use case really by my self. As far as I remember we had a similar requirement in TripleO (though we didn't use trunk resource) but used jinja2 template and render the template contents in client side.
Hi, With Hot templates we run into a scaling issue with Neutron trunk subports. The task is to create Neutron trunks with "vlan_count" number of subports, and with stack update be able to add or remove subports of the created trunk. We tried with resourceGroup, and that works well if we increase the number of subports. The problem comes with decrease, as with resourceGroups I can't (my lack of knowledge) tell heat_engine that first update the trunk and remove the subport and after
On 3/23/24 00:35, Lajos Katona wrote: that delete the port.
And Neutron API gives back conflict as the port which heat_engine tries to delete is still used by the trunk.
Do you know a way to accomplish such an operation with Hot templates?
Thanks in advance for the help. Best wishes Lajos Katona (lajoskatona)