Hi Robert, Thank you for mail, we are going through all of them trying to understand more on Odl.
Regarding adding support for Yang 1.1 Action in RestConf please correct my understanding if its wrong as explained below, Going with you suggestion for "RESTCONF the wiring from HTTP to DOMActionService is missing (that would sit in restconf-nb-rfc8040)". Steps am following : 1. Inject service "DOMActionService" in Rfc8040RestConfWiring.java in restconf.nb.rfc8040 . 2. In ServicesWrapper under restconf.nb.rfc8040.services.wrapper calling domActionService.getExtensions().getInstance(DOMYangTextSourceProvider.class) here we need to add new interface in MD-SAL named : DOMYangActionTextSourceProvider extending DOMActionServiceExtension to support new yang Model supporting action, if that the case we need to add more code in MD-Sal is that am going in correct direction.? 3. If above understanding is correct few changes need to be added in mdsal-dom-sip in abstract class AbstractDOMSchemaService and more which I need to figure out. Regards, Ajay -----Original Message----- From: Robert Varga <n...@hq.sk> Sent: Thursday, April 25, 2019 4:48 PM To: Emmett Cox <emmett....@est.tech>; netconf-...@lists.opendaylight.org; controller-dev@lists.opendaylight.org; mdsal-...@lists.opendaylight.org Cc: Ajay Deep Singh <ajay.deep.si...@ericsson.com>; Mariusz Sobucki <mariusz.sobu...@est.tech> Subject: Re: [netconf-dev] Help regarding Yang 1.1 actions On 25/04/2019 12:11, Emmett Cox wrote: > > > Hi everyone, Hello, > > Myself and several members of my team are investigating what changes > we would need to implement to allow restconf, mdsal and netconf to > support Yang 1.1 actions, both in a clustered and non-clustered way. YANG Tools and MD-SAL support is there, on both DOM and Binding layers, supported by org.opendaylight.mdsal.dom.api.DOMActionService org.opendaylight.mdsal.dom.api.DOMActionProviderService org.opendaylight.mdsal.binding.api.ActionService org.opendaylight.mdsal.binding.api.ActionProviderService and their respective JVM-local implementations. > To that end we've been trying to find documentation or guides > regarding the various ODL modules relating to restconf, mdsal and > netconf and determine which modules we need to change to get our use case > working. > > Would any of you be able to point us in the direction of anything we > could use to understand the modules, and where we could make a start > regarding the changes we'll need to make? I am not sure about clustering support, that would be part of controller's sal-remoterpc-connector -- which needs to hook onto the DOMActionService/DOMActionProviderService instances available in Service Registry. I think the gossiping protocol should support advertizing actions without a change, but that needs to be checked out. For NETCONF, I think the only piece missing is the translator in ... sal-netconf-connector (and probably mdsal-netconf-connector, I always confuse the two). For RESTCONF, the old spec does not support actions, so there's nothing to be done for that. For the RFC8040 implementation, I think the wiring from HTTP to DOMActionService is missing (that would sit in restconf-nb-rfc8040). Regards, Robert _______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
