Hi Mageshwaran, SEGMENT_SIZE must be power of 2 in order to fit into max long (in case that message xid reaches 2^64). But that is just an implementation detail. Queue segments are arrays and amount

+openflowjava -- Thanks Anil

Hello, please see Openflow Protocol Library M4 status below. Openflowjava: 1. Please provide updates on any previously-incomplete items from prior milestone readouts. ​- None previously

Hi Muthukrishnan, there is no golden standard behind this value. Setting it to 100ms or even lower value will result into low latency system but this also decreases throughput of system. If you have

Dear Team , I have been working in Lithium and Boron Stable Version . Lets take Boron , In openflowplugin.cfg default timer for barrier message is 500ms is there any rational behind the same ? why

Thanks Vishal, It works with the new config files after changing TCP->TLS and removing the last line: <cipher-suites></cipher-suites> I just updated TLS

Hi Luis, Based off the patch, the file where you configure TLS is now different. The file location will be:

Actually, I think these are the patches that changed the TLS configuration: https://git.opendaylight.org/gerrit/#/c/45758/ https://git.opendaylight.org/gerrit/#/c/45839 Can anyone please explain how

I see something changed here: https://git.opendaylight.org/gerrit/#/c/46518/ https://git.opendaylight.org/gerrit/#/c/46519/ Can anyone explain how to configure TLS after these changes? BR/Luis

Yes - please open a bug. We can always increase or lower the priority later based on more investigations.

FYI, I have just tried this instruction below on Boron and it does not work (it works in Beryllium). Does anybody know if something changed Beryllium -> Boron with regards to TLS support or should I

​​Hi Everyone, I was googling for a while but was not successful to find a solid answer for my question, and I would greatly appreciate your comments. I was wondering to know what 'switch

Hi Michal, Thanks for your help on this. We have since tested the CSIT jobs with ODL distributions carrying the Bug 7071 fix and have not observed the “deserialization failed” WARN messages.

Hello, please see Openflow Protocol Library (Openflowjava) M3 status below: Functionality Freeze: 1. Final list of externally consumable APIs defined: Yes 2. Are all your inter-project dependencies

+netvirt-dev Sure, I just created one: https://bugs.opendaylight.org/show_bug.cgi?id=7591

Guy, Could you raise a bug for Netvirt too? OVSDB patch:https://git.opendaylight.org/gerrit/50643 Regards, Vishal.

I willJ was just waiting for your confirmation.

Sound good to me Vishal. Anybody planning to push a patch for this ? -- Thanks Anil

Hi Guy, Yes, you’re right. I was under wrong impression that inactivity_probe is configured as other_config so will be covered with existing yang. Just confirmed, we *will* need yang changes in

I mean the API that OVSDB is exposing to its clients (In this case Netvirt). It seems to me that OVSDB didn’t model the inactivity_probe in the YANG model itself. After it will be modeled, OVSDB