Thanks Deepthi! We are not using routed-rpc. This clarifies why we never hit this error before on 3 node.
But to me, why it works for netvirt l2/l3 is still not clear. Thanks, Faseela -----Original Message----- From: Deepthi V V Sent: Monday, July 09, 2018 2:19 PM To: Faseela K <[email protected]>; Robert Varga <[email protected]>; Vishal Thapar <[email protected]> Cc: [email protected]; [email protected]; [email protected]; Tom Pantelis <[email protected]>; [email protected] Subject: RE: [openflowplugin-dev] [mdsal-dev] IncorrectNestingException on SFC when sing OFP model Hi Robert, Just to clarify, IF getEgressActions RPC was a routed RPC implementation, the issue should have been visible earlier because it would go through DOM serialization process. Since it is a global RPC, the call/response always happened on the same node and because of the shortcut, there were no errors. Thanks, Deepthi -----Original Message----- From: [email protected] <[email protected]> On Behalf Of Faseela K Sent: Monday, July 09, 2018 1:36 PM To: Robert Varga <[email protected]>; Vishal Thapar <[email protected]> Cc: [email protected]; [email protected]; [email protected]; Tom Pantelis <[email protected]>; [email protected] Subject: Re: [openflowplugin-dev] [mdsal-dev] IncorrectNestingException on SFC when sing OFP model I understand that for the single node scenarios, there is a change introduced on June 26th, due to which this will fail now. But, are you saying for cross-node, this would have never worked even before? We have been using the same code on 3 node, from Beryllium timeframe. Thanks, Faseela -----Original Message----- From: Robert Varga [mailto:[email protected]] Sent: Monday, July 09, 2018 1:22 PM To: Faseela K <[email protected]>; Vishal Thapar <[email protected]> Cc: [email protected]; [email protected]; [email protected]; [email protected]; Tom Pantelis <[email protected]> Subject: Re: [mdsal-dev] [openflowplugin-dev] IncorrectNestingException on SFC when sing OFP model On 09/07/18 06:58, Faseela K wrote: > Also, what do you mean by " this code/model is broken and will not work > in an cross-node invocation and needs to be fixed." I did not understand > "cross-node" in this context, the failure is in 1 node SFC CSIT. The nicira extensions are augmentations, which are targeted at inventory datastore only, therefore their use in the output of the RPC is not valid: they are not port of the model in that place. As I explained, for single node scenarios, where the RPC invoker and RPC implementation are on the same node, this happened to work because of the shortcut I mentioned. As soon as the application invoking the RPC and the implementation are not on the same node this will not work, as the output must go through NormalizedNodes and there is no corresponding schema. Regards, Robert _______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev _______________________________________________ sfc-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/sfc-dev
