Re: [Openstack-operators] Intro and Containerized Control Plane

[Fabian Zimmermann]

Hi,

we run completely in containers. I would recommend to take a look at how kolla 
is creating and managing the containers.

This should prevent you from the bigger pitfalls :)

If you have any specific questions. Don't hesitate to ask.

Fabian Zimmermann

Am 20. April 2018 17:22:46 MESZ schrieb Michael Damkot <mdam...@salesforce.com>:
>Hello Operators!!
>
>I wanted to say "Hello" to the community once again! I've come back
>into
>the OpenStack fold after my time as a former member of the Time Warner
>Cable Team.
>
>Salesforce is working toward greatly increasing the size and scale of
>our
>OpenStack use cases as well as our participation in the community.
>We're
>currently deep diving on a few things including containerizing a number
>of
>control plane components. Is anyone willing to share any hurdles or
>hiccups
>they've hit while exploring containerization? I didn't see much of
>anything
>in the archives but I know we aren't the only ones heading down this
>path.
>
>Thanks in advance!
>
>--
>Michael Damkot
>@mdamkot - twitter
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] sporadic missing vxlan-tunnel-port assignment

[Fabian Zimmermann]

Hi,

we currently see sporadic communication problems.

After some research we found out, that this is caused by missing 
tunnel-port assignments in table 21 of openvswitch.


Today we had the issue again and here the logs of the add_fdb_entries 
calls at the affected system:


neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent.OVSNeutronAgent 
method add_fdb_entries called with arguments (object at 0x7f7264509810>,) {u'fdb_entries': 
{u'cd2baf3d-427c-41be-be56-7cbb8176067f': {u'segment_id': 96, u'ports': 
{u'10.78.23.12': [[u'00:00:00:00:00:00', u'0.0.0.0'], 
[u'fa:16:3e:d0:a0:77', u'192.168.0.2']]}, u'network_type': u'vxlan'}}}


neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent.OVSNeutronAgent 
method add_fdb_entries called with arguments (object at 0x7f7264509bd0>,) {u'fdb_entries': 
{u'cd2baf3d-427c-41be-be56-7cbb8176067f': {u'segment_id': 96, u'ports': 
{u'10.78.23.11': [[u'00:00:00:00:00:00', u'0.0.0.0'], 
[u'fa:16:3e:29:0c:d5', u'192.168.0.3']]}, u'network_type': u'vxlan'}}}


neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent.OVSNeutronAgent 
method add_fdb_entries called with arguments (object at 0x7f7264509d90>,) {u'fdb_entries': 
{u'cd2baf3d-427c-41be-be56-7cbb8176067f': {u'segment_id': 96, u'ports': 
{u'10.78.12.101': []}, u'network_type': u'vxlan'}}}


neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent.OVSNeutronAgent 
method add_fdb_entries called with arguments (object at 0x7f7264627190>,) {u'fdb_entries': 
{u'cd2baf3d-427c-41be-be56-7cbb8176067f': {u'segment_id': 96, u'ports': 
{u'10.79.20.102': [[u'00:00:00:00:00:00', u'0.0.0.0']]}, 
u'network_type': u'vxlan'}}}


The missing tunnel-port is the connection to 10.78.12.101, it looks like 
the empty array/dict may cause this issue.


Any hints how to further debug the situation?

What may cause an empty dict in add_fdb_entries?

Thanks a lot,


 Fabian Zimmermann

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators