Im not sure how feasible this would be, but there would be less impact on downstream projects if the OpenflowPlugin first supported listening to both the deprecated inventory data store and to the newer topology data store. That way downstream projects could migrate to the newer topology data store, and once they're all migrated, the OpenflowPlugin could stop supporting the deprecated inventory data store. This way no downstream projects would be impacted when the OpenflowPlugin switches over.
Regards, Brady -----Original Message----- From: Jozef Bacigál <[email protected]<mailto:jozef%20%3d%3fiso-8859-1%3fq%3fbacig%3de1l%3f%3d%20%[email protected]%3e>> To: Brady Allen Johnson <[email protected]<mailto:brady%20allen%20johnson%20%[email protected]%3e>>, [email protected] <[email protected]<mailto:%[email protected]%22%20%[email protected]%3e>>, [email protected] <[email protected]<mailto:%[email protected]%22%20%[email protected]%3e>> Subject: Re: [openflowplugin-dev] Status of removing usage of deprecated inventory NodeId classes Date: Wed, 8 Mar 2017 16:28:52 +0000 Tomorrow we got project community meeting, we will let you know about dates. Jozef ________________________________ Od: Brady Allen Johnson <[email protected]> Odoslané: 8. marca 2017 15:42 Komu: [email protected]; [email protected] Predmet: [openflowplugin-dev] Status of removing usage of deprecated inventory NodeId classes We would like to remove the usage of the deprecated inventory NodeId and related classes from SFC, but probably wont be able to until the OpenflowPlugin removes them. import org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.NodeId import org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.NodeConnectorId; What are the current plans in the OpenflowPlugin for removing them? Thanks, Brady
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
