Luis, I thought that this was being handled by having in the integration cfg the jobs it depended on so it could run integration jobs like every other project does (see example of controller). I would

Hello, I am not sure I follow what exactly is the plan here. Is there going to be a centralized 'this is what integration looks like' job? Furthermore how does this interact

Hi all, I am pushing following patches to releng repo: https://git.opendaylight.org/gerrit/#/c/15689/ - yangtools https://git.opendaylight.org/gerrit/#/c/15691/ -

Hi Shuva, please have a look

Hi Shuva, basically there is a couple of wiki pages regarding vendor extensions: https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Backlog:Extensibility - mainly part Dependencies and

Hi all, Is there a way to implement vendor extensions without doing intrusive changes to the openflowplugin? If yes, what is the template regarding it Thanks Shuva

Thanks Anil

​As per my understanding base edition also supports of13, because openflowplugin project is also part of the base edition. ​Others please correct me if i am wrong. Ideally virtualization edition

Hi Anil Thanks The Hydrogen virtualization release supports OF1.3 and hydrogen base does not. However the issue what I'm facing with hydrogen virtualization using OF1.3 is that it it doesn't install

Yes, it does, but for that you will have to start the controller using ./run.sh -of13 flag. It will enable openflowplugin project that supports openflow 1.3 protocol. Thanks Anil -- Thanks Anil

Hi Anil Thanks.I'll try the above suggestion. One final question. Does the opendaylight hyrdogen release supports OF1.3?

I believe you can use YangUI tool in dlux gui to directly push the flow to the data store and that will eventually get install on switch. Hopefully following link can help

Hi Anil One more quiry.Is there any method to set flows from Helium Opendaylight Controller through GUI as in Hydrogen.

Hi Anil, Thank you for answering my question. The problem was a missing "setOrder" to the OutputAction. Thanks, Yair

​Hi Yair, Yes i believe this is the correct format of URI for node connector, assuming that OUTPUT_ENTIRE_PACKET enum is something that is defined in your application code. If it does, then can you

Hi, We started using Helium SR and we're having trouble with setting flows output to port actions. In Hydrogen we used OutputAction and setOutputNodeConnector using "openflow:switchId:portId" URI, for

Thanks. Otherwise, the stock netty LengthFieldBasedDecoder also contains a couple of checks for corrupted frames which are missing in the OFFrameDecoder. These can catch if someone feeds ODL a frame

Yes, I see. The problem is in controller features: No feature named 'odl-mdsal-common' with version '1.2.0-SNAPSHOT' available Those have been probably updated. I will try to investigate what happened

Removing jenkings-releng/Adding openflowjava-dev. OK. I will double check the error/exception handling code in LengthFieldBasedDecoder vs OFFrameDecoder. With the zero copy in place they are now

Hi Michal, Looks good on my end. Thanks! Thanh On 2 January 2015 at 16:34, Michal Rehak -X (mirehak - Pantheon Technologies SRO at Cisco) <mirehak@...> wrote: