Re: [openflowplugin-dev] Sending flow to switch but NOT the config database?
Yes, you wll have to use SalFlowService and it's not deprecated.
On Thu, Jul 12, 2018 at 1:52 PM M. Ranganathan wrote:
> Thanks, if I had to do this from within a Java app, I assume I'd have to
> use the SalFlowService. Is that not deprecated ? If so, what is the MdSal
> alternative?
>
> Regads,
>
> Ranga
>
> On Thu, Jul 12, 2018 at 4:45 PM, Luis Gomez wrote:
>
>> You can send openflow RPC like the example below:
>>
>> POST http://192.168.0.101:8181/restconf/operations/sal-flow:add-flow
>> {
>> "input": {
>>
>> "opendaylight-flow-service:node":"/opendaylight-inventory:nodes/opendaylight-inventory:node[opendaylight-inventory:id='openflow:1']",
>> "priority": 2,
>> "flow-name": "flow1",
>> "table_id": 0,
>> "hard-timeout": 0,
>> "instructions": {
>> "instruction": [
>> {
>> "order": 0,
>> "apply-actions": {
>> "action": [
>> {
>> "order": 0,
>> "output-action": {
>> "output-node-connector": "1"
>> }
>> }
>> ]
>> }
>> }
>> ]
>> },
>> "idle-timeout": 0,
>> "match": {
>> "ipv4-destination": "10.0.10.0/24",
>> "ethernet-match": {
>> "ethernet-type": {
>> "type": 2048
>> }
>> }
>> }
>> }
>> }
>>
>>
>>
>> > On Jul 12, 2018, at 12:09 PM, M. Ranganathan wrote:
>> >
>> > I am using OpendDaylight Nitrogen. In order to send a flow to the
>> switch, I write to the CONFIG database - which winds up sending the flow to
>> the switch. However, I want faster performance for ephemeral flows . How
>> can I send the flow to the switch without involving the CONFIG database?
>> >
>> > Thanks,
>> >
>> > Ranga
>> >
>> > --
>> > M. Ranganathan
>> >
>> > ___
>> > openflowplugin-dev mailing list
>> > openflowplugin-dev@lists.opendaylight.org
>> > https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
>>
>>
>
>
> --
> M. Ranganathan
>
> ___
> openflowplugin-dev mailing list
> openflowplugin-dev@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
>
--
Thanks
Anil
___
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
Re: [openflowplugin-dev] Sending flow to switch but NOT the config database?
You can send openflow RPC like the example below:
POST http://192.168.0.101:8181/restconf/operations/sal-flow:add-flow
{
"input": {
"opendaylight-flow-service:node":"/opendaylight-inventory:nodes/opendaylight-inventory:node[opendaylight-inventory:id='openflow:1']",
"priority": 2,
"flow-name": "flow1",
"table_id": 0,
"hard-timeout": 0,
"instructions": {
"instruction": [
{
"order": 0,
"apply-actions": {
"action": [
{
"order": 0,
"output-action": {
"output-node-connector": "1"
}
}
]
}
}
]
},
"idle-timeout": 0,
"match": {
"ipv4-destination": "10.0.10.0/24",
"ethernet-match": {
"ethernet-type": {
"type": 2048
}
}
}
}
}
> On Jul 12, 2018, at 12:09 PM, M. Ranganathan wrote:
>
> I am using OpendDaylight Nitrogen. In order to send a flow to the switch, I
> write to the CONFIG database - which winds up sending the flow to the switch.
> However, I want faster performance for ephemeral flows . How can I send the
> flow to the switch without involving the CONFIG database?
>
> Thanks,
>
> Ranga
>
> --
> M. Ranganathan
>
> ___
> openflowplugin-dev mailing list
> openflowplugin-dev@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
___
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
[openflowplugin-dev] Sending flow to switch but NOT the config database?
I am using OpendDaylight Nitrogen. In order to send a flow to the switch, I write to the CONFIG database - which winds up sending the flow to the switch. However, I want faster performance for ephemeral flows . How can I send the flow to the switch without involving the CONFIG database? Thanks, Ranga -- M. Ranganathan ___ openflowplugin-dev mailing list openflowplugin-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
Re: [openflowplugin-dev] OpenFlow 1.5 support
Hi Ranga, No, as of now openflowplugin supports openflow 1.0 and 1.3, but we do have implementation of some of the openflow 1.4 and 1.5 features in openflow 1.3 (They are approved extension for openflow 1.3). I believe we already have implementation of the the tcp.flag match implementation (ONF Ext-109) in the current implementation of OpenFlow1.3. Here is the related patch https://git.opendaylight.org/gerrit/#/c/42630/ Let me know if you are looking for some other feature. Thanks Anil On Thu, Jul 12, 2018 at 11:51 AM M. Ranganathan wrote: > Hello, > > I am interested in certain features of openflow 1.5 - in particular TCP > flags matching. Does opendaylight openflow plugin support Openflow 1.5 and > if so what version ? > > Thank you, > > Ranga > > -- > M. Ranganathan > > ___ > openflowplugin-dev mailing list > openflowplugin-dev@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev > -- Thanks Anil ___ openflowplugin-dev mailing list openflowplugin-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
[openflowplugin-dev] OpenFlow 1.5 support
Hello, I am interested in certain features of openflow 1.5 - in particular TCP flags matching. Does opendaylight openflow plugin support Openflow 1.5 and if so what version ? Thank you, Ranga -- M. Ranganathan ___ openflowplugin-dev mailing list openflowplugin-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
Re: [openflowplugin-dev] [netvirt-dev] ovs 2.8.2 does not work well in csit
On Thu, Jul 12, 2018 at 8:26 PM, Sam Hague wrote: > > > On Thu, Jul 12, 2018 at 10:04 AM Aswin Suryanarayanan > wrote: > >> >> >> On Thu, Jul 12, 2018 at 8:20 AM, D Arunprakash < >> d.arunprak...@ericsson.com> wrote: >> >>> Aswin, >>> >>> Could you please refer the attached packet-in dump, where there are new >>> ct fields (120, 121, 124, 125) in the match? >>> >>> >>> >>> So, if we use ct_clear in the flow, is it expected to clear the new ct >>> fields as well. I’m not much familiar with CT fields, could you please >>> check and let me know what we should do now? >>> >> >> ct_clear is expected to clear these , but it is more like workaround. Was >> this added by aclservice, does disabling port security solve the issue? if >> it helps ,I doubt if we have bug in ovs and that is the reason we are >> seeing these fields as aclservice is not using it. >> >>> >>> >>> Is the ct_clear bug present in ovs2.8 as well? >>> >> >> ct_clear works only in ovs2.9+. We are planning to move to ovs2.9 right? >> > We need to come up with a plan since we don't have anything beyond 2.7.2 > that works: 2.8.2 has issues and 2.9.0 has a group bug. So we need at least > 2.9.2 which we have been waiting for to get an rpm with patch [10]. So we > were just trying to find some way to test with something so we could get > some visibility. If we think 2.9.2 will fix everything then we should push > to get that in, but we also need the ofp nsh patches right? > if these headers were introduced by aclservice(I think yes, as we don't use anything related to NSH here), we do not require the nsh patches for fixing this. ct_clear should be removing them. > > [10] https://review.rdoproject.org/r/#/c/13839/ > >> >>> >>> >>> >>> Regards, >>> >>> Arun >>> >>> *From:* Aswin Suryanarayanan [mailto:asury...@redhat.com] >>> *Sent:* Wednesday, July 11, 2018 11:24 AM >>> *To:* D Arunprakash >>> *Cc:* Anil Vishnoi ; Jamo Luhrsen < >>> jluhr...@redhat.com>; openflowplugin-dev >> opendaylight.org>; Luis Gomez ; odl netvirt dev < >>> netvirt-...@lists.opendaylight.org> >>> >>> *Subject:* Re: [netvirt-dev] ovs 2.8.2 does not work well in csit >>> >>> >>> >>> >>> >>> >>> >>> On Wed, Jul 11, 2018 at 10:17 AM, D Arunprakash < >>> d.arunprak...@ericsson.com> wrote: >>> >>> Aswin, >>> >>> >>> >>> From http://www.openvswitch.org/support/dist-docs/ovs-ofctl.8.html, >>> ct_clear clears the following ct fields, >>> >>> >>> >>> ct_clear >>> >>> Clears connection tracking state from the flow, >>> zeroing >>> >>> ct_state, ct_zone, ct_mark, and ct_label. >>> >>> >>> >>> This action was introduced in Open vSwitch 2.6.90. >>> >>> >>> >>> But from the ovs2.8+, there are new CT fields introduced, will ct_clear >>> those as well? >>> >>> >>> >>> The ct_clear is intended to clear the states, I don't think (I could be >>> wrong) the other fields will be present in a packet submitted back from to >>> the pipeline from conntrack, they are used when we send the packet to >>> conntrack. >>> >>> In this case I think we need to identify who added these extra fields, >>> if it was due to acl service it should have been cleared by ct_clear. But >>> the ct_clear functionality was broken in the kernel datapath in the initial >>> ovs2.9 release and was addressed by [*]. We should have this fix for this >>> to work as expected. >>> >>> >>> [*]https://patchwork.ozlabs.org/patch/864353/ >>> >>> >>> >>> CONNECTION TRACKING FIELDS >>> >>>Summary: >>> >>>Name Bytes Mask RW? Prereqs NXM/OXM Support >>> >>> ── ─ >>> >>>ct_state 4 yesnonone OVS 2.5+ >>> >>>ct_zone 2 no nonone OVS 2.5+ >>> >>>ct_mark 4 yesyes none OVS 2.5+ >>> >>>ct_label 16 yesyes none OVS 2.5+ >>> >>>ct_nw_src 4 yesnoCTOVS 2.8+ >>> >>>ct_nw_dst 4 yesnoCTOVS 2.8+ >>> >>> >>> >>>ct_ipv6_src 16 yesnoCTOVS 2.8+ >>> >>>ct_ipv6_dst 16 yesnoCTOVS 2.8+ >>> >>>ct_nw_proto 1 no noCTOVS 2.8+ >>> >>>ct_tp_src 2 yesnoCTOVS 2.8+ >>> >>>ct_tp_dst 2 yesnoCTOVS 2.8+ >>> >>> >>> >>> >>> >>> Regards, >>> >>> Arun >>> >>> >>> >>> *From:* netvirt-dev-boun...@lists.opendaylight.org [mailto: >>> netvirt-dev-boun...@lists.opendaylight.org] *On Behalf Of *Aswin >>> Suryanarayanan >>> *Sent:* Tuesday, July 10, 2018 11:06 PM >>> *To:* Anil Vishnoi >>> *Cc:* Jamo Luhrsen ; openflowplugin-dev < >>> openflowplugin-dev@lists.opendaylight.org>; Luis Gomez ; >>> odl netvirt dev >>> >>> >>> *Subject:* Re: [netvirt-dev] ovs 2.8.2 does not work well in csit >>> >>> >>> >>> >>> >>> >>> >>> On Mon, Jul 9, 2018 at 11:25 PM, Anil Vishnoi >>> wrote: >>>
Re: [openflowplugin-dev] [netvirt-dev] ovs 2.8.2 does not work well in csit
On Thu, Jul 12, 2018 at 10:04 AM Aswin Suryanarayanan wrote: > > > On Thu, Jul 12, 2018 at 8:20 AM, D Arunprakash > wrote: > >> Aswin, >> >> Could you please refer the attached packet-in dump, where there are new >> ct fields (120, 121, 124, 125) in the match? >> >> >> >> So, if we use ct_clear in the flow, is it expected to clear the new ct >> fields as well. I’m not much familiar with CT fields, could you please >> check and let me know what we should do now? >> > > ct_clear is expected to clear these , but it is more like workaround. Was > this added by aclservice, does disabling port security solve the issue? if > it helps ,I doubt if we have bug in ovs and that is the reason we are > seeing these fields as aclservice is not using it. > >> >> >> Is the ct_clear bug present in ovs2.8 as well? >> > > ct_clear works only in ovs2.9+. We are planning to move to ovs2.9 right? > We need to come up with a plan since we don't have anything beyond 2.7.2 that works: 2.8.2 has issues and 2.9.0 has a group bug. So we need at least 2.9.2 which we have been waiting for to get an rpm with patch [10]. So we were just trying to find some way to test with something so we could get some visibility. If we think 2.9.2 will fix everything then we should push to get that in, but we also need the ofp nsh patches right? [10] https://review.rdoproject.org/r/#/c/13839/ > >> >> >> >> Regards, >> >> Arun >> >> *From:* Aswin Suryanarayanan [mailto:asury...@redhat.com] >> *Sent:* Wednesday, July 11, 2018 11:24 AM >> *To:* D Arunprakash >> *Cc:* Anil Vishnoi ; Jamo Luhrsen < >> jluhr...@redhat.com>; openflowplugin-dev < >> openflowplugin-dev@lists.opendaylight.org>; Luis Gomez ; >> odl netvirt dev >> >> *Subject:* Re: [netvirt-dev] ovs 2.8.2 does not work well in csit >> >> >> >> >> >> >> >> On Wed, Jul 11, 2018 at 10:17 AM, D Arunprakash < >> d.arunprak...@ericsson.com> wrote: >> >> Aswin, >> >> >> >> From http://www.openvswitch.org/support/dist-docs/ovs-ofctl.8.html, >> ct_clear clears the following ct fields, >> >> >> >> ct_clear >> >> Clears connection tracking state from the flow, >> zeroing >> >> ct_state, ct_zone, ct_mark, and ct_label. >> >> >> >> This action was introduced in Open vSwitch 2.6.90. >> >> >> >> But from the ovs2.8+, there are new CT fields introduced, will ct_clear >> those as well? >> >> >> >> The ct_clear is intended to clear the states, I don't think (I could be >> wrong) the other fields will be present in a packet submitted back from to >> the pipeline from conntrack, they are used when we send the packet to >> conntrack. >> >> In this case I think we need to identify who added these extra fields, if >> it was due to acl service it should have been cleared by ct_clear. But the >> ct_clear functionality was broken in the kernel datapath in the initial >> ovs2.9 release and was addressed by [*]. We should have this fix for this >> to work as expected. >> >> >> [*]https://patchwork.ozlabs.org/patch/864353/ >> >> >> >> CONNECTION TRACKING FIELDS >> >>Summary: >> >>Name Bytes Mask RW? Prereqs NXM/OXM Support >> >> ── ─ >> >>ct_state 4 yesnonone OVS 2.5+ >> >>ct_zone 2 no nonone OVS 2.5+ >> >>ct_mark 4 yesyes none OVS 2.5+ >> >>ct_label 16 yesyes none OVS 2.5+ >> >>ct_nw_src 4 yesnoCTOVS 2.8+ >> >>ct_nw_dst 4 yesnoCTOVS 2.8+ >> >> >> >>ct_ipv6_src 16 yesnoCTOVS 2.8+ >> >>ct_ipv6_dst 16 yesnoCTOVS 2.8+ >> >>ct_nw_proto 1 no noCTOVS 2.8+ >> >>ct_tp_src 2 yesnoCTOVS 2.8+ >> >>ct_tp_dst 2 yesnoCTOVS 2.8+ >> >> >> >> >> >> Regards, >> >> Arun >> >> >> >> *From:* netvirt-dev-boun...@lists.opendaylight.org [mailto: >> netvirt-dev-boun...@lists.opendaylight.org] *On Behalf Of *Aswin >> Suryanarayanan >> *Sent:* Tuesday, July 10, 2018 11:06 PM >> *To:* Anil Vishnoi >> *Cc:* Jamo Luhrsen ; openflowplugin-dev < >> openflowplugin-dev@lists.opendaylight.org>; Luis Gomez ; >> odl netvirt dev >> >> >> *Subject:* Re: [netvirt-dev] ovs 2.8.2 does not work well in csit >> >> >> >> >> >> >> >> On Mon, Jul 9, 2018 at 11:25 PM, Anil Vishnoi >> wrote: >> >> Sam, >> >> >> >> We are currently working on getting all the NSH related patches from >> jamie in, once we get those patches in, we can see if we see these other >> serialization issue. >> >> >> >> On Mon, Jul 9, 2018 at 8:24 AM Sam Hague wrote: >> >> Arun, Anil, >> >> >> >> thanks for merging [1]. There are other deserialization problems failing >> the tests. I filed [3] to track the issues. Can you take a look and see if >> more similar changes are needed? The
Re: [openflowplugin-dev] [netvirt-dev] ovs 2.8.2 does not work well in csit
On Thu, Jul 12, 2018 at 8:20 AM, D Arunprakash wrote: > Aswin, > > Could you please refer the attached packet-in dump, where there are new ct > fields (120, 121, 124, 125) in the match? > > > > So, if we use ct_clear in the flow, is it expected to clear the new ct > fields as well. I’m not much familiar with CT fields, could you please > check and let me know what we should do now? > ct_clear is expected to clear these , but it is more like workaround. Was this added by aclservice, does disabling port security solve the issue? if it helps ,I doubt if we have bug in ovs and that is the reason we are seeing these fields as aclservice is not using it. > > > Is the ct_clear bug present in ovs2.8 as well? > ct_clear works only in ovs2.9+. We are planning to move to ovs2.9 right? > > > > > Regards, > > Arun > > *From:* Aswin Suryanarayanan [mailto:asury...@redhat.com] > *Sent:* Wednesday, July 11, 2018 11:24 AM > *To:* D Arunprakash > *Cc:* Anil Vishnoi ; Jamo Luhrsen < > jluhr...@redhat.com>; openflowplugin-dev opendaylight.org>; Luis Gomez ; odl netvirt dev < > netvirt-...@lists.opendaylight.org> > > *Subject:* Re: [netvirt-dev] ovs 2.8.2 does not work well in csit > > > > > > > > On Wed, Jul 11, 2018 at 10:17 AM, D Arunprakash < > d.arunprak...@ericsson.com> wrote: > > Aswin, > > > > From http://www.openvswitch.org/support/dist-docs/ovs-ofctl.8.html, > ct_clear clears the following ct fields, > > > > ct_clear > > Clears connection tracking state from the flow, > zeroing > > ct_state, ct_zone, ct_mark, and ct_label. > > > > This action was introduced in Open vSwitch 2.6.90. > > > > But from the ovs2.8+, there are new CT fields introduced, will ct_clear > those as well? > > > > The ct_clear is intended to clear the states, I don't think (I could be > wrong) the other fields will be present in a packet submitted back from to > the pipeline from conntrack, they are used when we send the packet to > conntrack. > > In this case I think we need to identify who added these extra fields, if > it was due to acl service it should have been cleared by ct_clear. But the > ct_clear functionality was broken in the kernel datapath in the initial > ovs2.9 release and was addressed by [*]. We should have this fix for this > to work as expected. > > > [*]https://patchwork.ozlabs.org/patch/864353/ > > > > CONNECTION TRACKING FIELDS > >Summary: > >Name Bytes Mask RW? Prereqs NXM/OXM Support > > ── ─ > >ct_state 4 yesnonone OVS 2.5+ > >ct_zone 2 no nonone OVS 2.5+ > >ct_mark 4 yesyes none OVS 2.5+ > >ct_label 16 yesyes none OVS 2.5+ > >ct_nw_src 4 yesnoCTOVS 2.8+ > >ct_nw_dst 4 yesnoCTOVS 2.8+ > > > >ct_ipv6_src 16 yesnoCTOVS 2.8+ > >ct_ipv6_dst 16 yesnoCTOVS 2.8+ > >ct_nw_proto 1 no noCTOVS 2.8+ > >ct_tp_src 2 yesnoCTOVS 2.8+ > >ct_tp_dst 2 yesnoCTOVS 2.8+ > > > > > > Regards, > > Arun > > > > *From:* netvirt-dev-boun...@lists.opendaylight.org [mailto: > netvirt-dev-boun...@lists.opendaylight.org] *On Behalf Of *Aswin > Suryanarayanan > *Sent:* Tuesday, July 10, 2018 11:06 PM > *To:* Anil Vishnoi > *Cc:* Jamo Luhrsen ; openflowplugin-dev < > openflowplugin-dev@lists.opendaylight.org>; Luis Gomez ; > odl netvirt dev > > > *Subject:* Re: [netvirt-dev] ovs 2.8.2 does not work well in csit > > > > > > > > On Mon, Jul 9, 2018 at 11:25 PM, Anil Vishnoi > wrote: > > Sam, > > > > We are currently working on getting all the NSH related patches from jamie > in, once we get those patches in, we can see if we see these other > serialization issue. > > > > On Mon, Jul 9, 2018 at 8:24 AM Sam Hague wrote: > > Arun, Anil, > > > > thanks for merging [1]. There are other deserialization problems failing > the tests. I filed [3] to track the issues. Can you take a look and see if > more similar changes are needed? The conntrack fields overlapping with the > nsh fields definitely makes sense as the tests are conntrack based. > > > > Arun, Jaime, > > > > did you also try with ovs 2.9.x? I am guessing the same problems are there. > > > > Thanks, Sam > > > > [1] https://git.opendaylight.org/gerrit/#/c/73735/ > > [2] https://git.opendaylight.org/gerrit/#/c/72320/. > > [3] https://jira.opendaylight.org/browse/OPNFLWPLUG-1023 > > [4] https://logs.opendaylight.org/releng/vex-yul-odl- > jenkins-1/builder-copy-sandbox-logs/196/shague-queens-netvirt-csit-1node- > openstack-queens-upstream-stateful-fluorine/7/odl_1/odl1_karaf.log.gz > > > > On Mon, Jul 9, 2018 at 4:09 AM Jaime Caamaño Ruiz > wrote: > > Hello Sam > > This is most likely
