[Starlingx-discuss] AIO Duplex Setup with 2 NICs

Marc Ferland ferlandm at amotus.ca
Tue Jul 21 16:51:05 UTC 2020


On Mon, Jul 20, 2020 at 1:23 PM Pratik M. <pvmpublic at gmail.com> wrote:

> Hi,
> While I haven't tried it, I believe you can create VLAN based interfaces
> and assign them to data interfaces, based on:
>
> https://docs.starlingx.io/configuration/host_interface_network_config.html
>
> Try doing a  "system host-if-add controller-0 -V ...".
>
> But if you want to use SRIOV, I believe it might make more sense to assign
> entire NIC to DATA0IF and use VLAN intrrfaces for MGMT_IF and OAM_IF.
>
> Hope this helps.
>
> BR
>
> On Mon, 20 Jul, 2020, 21:55 Marc Ferland, <ferlandm at amotus.ca> wrote:
>
>> Hi everyone,
>>
>> Is it possible to setup an AIO Duplex (kubernetes + openstack)
>> configuration with servers that have only 2 NICs?
>>
>> I did a quick test last week and pointed the DATA0IF interface to the
>> same interface as mgmt and cluster-host but the installation failed. I seem
>> to lose connectivity with the 2nd controller while applying the
>> stx-openstack application charts.
>>
>> Would configuring some VLANs solve the problem? Or is this something that
>> is not currently supported?
>>
>> If it is indeed supported, do you have any pointers/recommendations?
>>
>
Thanks for the info.

Followed the guide and modified my VLANs config accordingly. DATA0IF now
has it's own dedicated interface. I reinstalled the OpenStack application
but it failed while installing the openstack-libvirt chart.

Install log: https://pastebin.com/FAdV3tMe

neutron-ovs-agent-controller-0-937646f6-dprsc_openstack_neutron-ovs-agent-init*.log
seems to also point to an error: https://pastebin.com/GcC2bjBj

I'm also seeing these messages appear periodically in dmesg:

[11998.657984] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[11998.658070] IPv6: ADDRCONF(NETDEV_UP): cali29ecf54f2e7: link is not ready
[11998.658073] IPv6: ADDRCONF(NETDEV_CHANGE): cali29ecf54f2e7: link becomes
ready
[11998.658079] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[11998.783788] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[11998.783869] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Any help appreciated,

Marc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20200721/7b1f90b9/attachment.html>


More information about the Starlingx-discuss mailing list