On Thu, Jan 28, 2016 at 7:01 AM, M Vinoth <[email protected]> wrote:
> Hi Anil and openflowplugin-dev’s,
>
>
>
> Currently we facing 2 problem when we changing the lithium feature to
> helium feature in our task to NIC.
>
>
>
> Problem 1: Logging the flow statistics data
>
>
>
> The following code is working in lithium and but not in helium,
>
>
>
> InstanceIdentifier<FlowStatistics> path = InstanceIdentifier.
> *builder*(*Nodes*.*class*).
>
> child(*Node*.*class*, *new* NodeKey(nodeId)).
>
> augmentation(FlowCapableNode.*class*).
>
> child(Table.*class*, *new* TableKey(*TABLE_ID*)).
>
> child(Flow.*class*, *new* FlowKey(flowId)).
>
> augmentation(FlowStatisticsData.*class*).
>
> child(FlowStatistics.*class*).
>
> build();
>
> registration = *this*.dataBroker
> .registerDataChangeListener(LogicalDatastoreType.*OPERATIONAL*, path,
> *this*, DataBroker.DataChangeScope.*SUBTREE*);
>
>
>
> My understanding that helium won’t support the above API’s. it will
> support through RPC notification call.
>
>
>
> The below code will support in helium to get the flow statistics data
> information.
>
>
>
> *public* Future<RpcResult<*GetFlowStatisticsFromFlowTableOutput*>>
> getFlowStatisticsFromFlowTable(
>
> *final* *GetFlowStatisticsFromFlowTableInput* input) {
>
> *return* flowsInTable.handleAndNotify(input, notificationService);
>
> }
>
>
>
> Please confirm my understanding is correct or please share some additional
> information if this info is wrong.
>
Above code is listening for data change notification and there is no change
in that, irrespective of which plugin you use. Probably the issue is
whether stats are present for that specific flow or not. can you dump me
the flow for which stats are not present or reported by the data store
change notification?
>
>
> Problem 2: Finding the shortest path between SRC and DSC node ID’s by
> using graph service, and graph service is setting by topology links (which
> is shared in below code).
>
>
>
> We are listening the below topology and the same setting into our graph
> service.
>
>
>
> The below code is working in lithium but not in helium. And kindly suggest
> us how to make this code work in helium feature.
>
>
>
> /**
>
> * Creates an {@link InstanceIdentifier} for {@link Topology} with a
> key "flow:1".
>
> * *@return* InstanceIdentifier for Topology with key "flow:1"
>
> */
>
> *public* *static* InstanceIdentifier<Topology> getFlowTopologyII() {
>
> *final* TopologyKey key = *new* TopologyKey(*new* TopologyId(
> "flow:1"));
>
> *return* InstanceIdentifier
>
> .create(NetworkTopology.*class*)
>
> .child(Topology.*class*, key);
>
> }
>
>
>
This code just creates path Instance identifier for topology (flow:1), so
don't really dependent on plugin, you probably getting some issue in
topology events ?
>
>
> Regards,
>
> Vinoth
>
>
>
>
>
>
>
> ::DISCLAIMER::
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
> The contents of this e-mail and any attachment(s) are confidential and
> intended for the named recipient(s) only.
> E-mail transmission is not guaranteed to be secure or error-free as
> information could be intercepted, corrupted,
> lost, destroyed, arrive late or incomplete, or may contain viruses in
> transmission. The e mail and its contents
> (with or without referred errors) shall therefore not attach any liability
> on the originator or HCL or its affiliates.
> Views or opinions, if any, presented in this email are solely those of the
> author and may not necessarily reflect the
> views or opinions of HCL or its affiliates. Any form of reproduction,
> dissemination, copying, disclosure, modification,
> distribution and / or publication of this message without the prior
> written consent of authorized representative of
> HCL is strictly prohibited. If you have received this email in error
> please delete it and notify the sender immediately.
> Before opening any email and/or attachments, please check them for viruses
> and other defects.
>
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
--
Thanks
Anil
_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
