Remove deprecated MD-SAL APIs The APIs in controller have been deprecated for removal and cannot sustain an upgrade to Guava-28+. Remove them along with all supporting implementations. JIRA: CONTROLLER-1903 Change-Id: I213797b7045cfd7bef744e249614e2b1f6169c1c Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
Deprecate old MD-SAL APIs for removal These APIs are slated for removal in Aluminium, make sure our warning is more stern. JIRA: CONTROLLER-1917 Change-Id: Ib4f7dcfd5183b87dd10b9ce2b773a59a548892c9 Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
Deprecate all MD-SAL APIs These APIs have either been completely deprecated or have their replacements in the mdsal project. Mark all of them as deprecated, including their implementations. JIRA: CONTROLLER-1902 Change-Id: I903afcef57c70c1013ab479cfcf31a42f475dc0f Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
Bug 500: Updated data APIs with new concepts. - Logical Datastore Type idenfier - Asynchronous Data Broker contracts - some data broker contracts were synchronous which could misslead consumers of APIs - New Transaction subtypes with support for Asynchronous reads - read-only transaction - write-only transaction - read-write transaction - Scoped Data Change Publisher - client code is able to specify scope of changes and logical datastore type on which it is listening. Change-Id: I2367e7df633dd07b08550014bed7a35c3e88a7ba Signed-off-by: Tony Tkacik <ttkacik@cisco.com> Signed-off-by: Robert Varga <rovarga@cisco.com>
MD-SAL transaction chaining API This API complements the normal MD-SAL transaction API. Applications can use this API to maintain inter-transaction ordering and data consistency. Change-Id: Ia603f7dacf081fb1528d149f4635c2f22101a7a0 Signed-off-by: Robert Varga <rovarga@cisco.com>