port Groups (Bonds) Configuration in Openstack Baremetal Provisioning.

Lokendra Rathour lokendrarathour at gmail.com
Sun Dec 13 04:39:46 UTC 2020


Thanks Julia,
My aim here to chk the for any kind of port binding or grouping inorder to
achived redundancy at the baremetal port level.
So scenarion as desired or which i am trying to bring up is :
I have an openstack controller computer setup(simple openstack)
On top of this I am provisioning baremetal node . On this baremetal node i
have one cable connected to one of the port from the switch. We inform
neutron about it before we go for server create. It works and we are able
to see the nodes getting added.
So on the same server we are trying to enable port binding , which we are
not able to do it.
If using cloud init which shall be passed during the server created then
what can be the standard configuration for it ? Or how to move forward?

-lokendra


On Sun, 13 Dec 2020, 05:28 Julia Kreger, <juliaashleykreger at gmail.com>
wrote:

> Greetings Lokendra,
>
> Portgroups are a bit of a complex item, unfortunately.
>
> They hold a dual purpose of representing what is desired and what exists.
> The delineation between those states largely being what tooling is being
> loaded into Neutron in the form of a portgroup supporting ML2 drivers. If
> portgroups are pre-configured on a switch side, they can be represented in
> Ironic and the virtual port (VIF) binding information can be transmitted to
> Neutron with this information. If an ML2 driver is loaded that understands
> the portgroup configuration, then it can also configure the switch to
> represent this port.
>
> I can't tell if you're asking about pre-configured bonds or if you're
> asking about ML2 enabled bonds. I don't know if StarlingX ships with/uses
> any of the Neutron ML2 which support such functionality, and that may be a
> good question for the StarlingX community specifically. If you're just
> trying to express pre-configured portgroups, it looks like Cloud-init since
> 0.7.7 has apparently supported parsing and setting up the portgroup within
> the deployed operating system. That is, if it is present in that operating
> system image you deploy. Please note, caution should be taken with LACP[0]
> and various switch configuration tunables. They make network booting a bit
> complicated and each switch vendor has somewhat different behavior and
> configuration available to help navigate such situations.
>
> -Julia
>
> [0]
> https://docs.openstack.org/ironic/latest/admin/troubleshooting.html#why-does-x-issue-occur-when-i-am-using-lacp-bonding-with-ipxe
>
> On Sat, Dec 12, 2020 at 11:28 AM Lokendra Rathour <
> lokendrarathour at gmail.com> wrote:
>
>> Hi ,
>> Any support here.
>> Any input would help.
>>
>> Best Regards,
>> Lokendra
>>
>> On Fri, 11 Dec 2020, 18:10 Lokendra Rathour, <lokendrarathour at gmail.com>
>> wrote:
>>
>>> Hello,
>>> I am trying to install a baremetal on existing openstack setup. During
>>> the time of installation, is it possible to have bonds already setup when
>>> the baremetal nodes comes up.
>>>
>>> I was trying to work on the :
>>> Port groups configuration in the Bare Metal service
>>>
>>> *Documents referred :*
>>>
>>>    1.
>>>    https://docs.openstack.org/ironic/pike/admin/portgroups.html#:~:text=A%20port%20group%20can%20also,attached%20to%20the%20port%20group
>>>    .
>>>    2.
>>>    https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/14/pdf/bare_metal_provisioning/Red_Hat_OpenStack_Platform-14-Bare_Metal_Provisioning-en-US.pdf
>>>
>>> *Setup used:*
>>> Baremetal on StarlingX Setup :
>>>
>>> https://docs.starlingx.io/deploy_install_guides/r4_release/bare_metal/ironic_install.html
>>>
>>> ΒΆ
>>> <https://docs.openstack.org/ironic/queens/admin/portgroups.html#port-groups-configuration-in-the-bare-metal-service>
>>>
>>> --
>>> ~ Lokendra
>>>
>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20201213/058542fc/attachment.html>


More information about the openstack-discuss mailing list