[OpenNESS-dev] Openvino application without hddl support

Mokhtar, Amr amr.mokhtar at intel.com
Wed Apr 29 05:25:33 UTC 2020


Hi Ashish,
Your setup is similar to openvino-sample-app, so please refer to the onboarding steps at https://github.com/open-ness/specs/blob/master/doc/applications-onboard/on-premises-applications-onboarding.md#onboarding-openvino-applications

-Amr

From: Ashish Saxena <Ashish.Saxena at hsc.com>
Sent: Wednesday 29 April 2020 12:43
To: Mokhtar, Amr <amr.mokhtar at intel.com>
Subject: RE: Openvino application without hddl support

Hi Amr,

Thank you very much  for the explanation.

However, I am not observing this behavior on my setup.
Following is my test setup:
[cid:image001.png at 01D61E29.A76F9B10]


I have applied traffic policy with destination ip of the container , and I am pinging that ip (192.168.10.25)from the upstream m/c.
I am able to see the icmp request and reply packets inside the container , but I am not getting the icmp reply msg back at the upstream m/c. Similarly, when I am pinging the upstream m/c ip , then also I am not receiving icmp request packets at the upstream m/c interface.

Can you please help me in debugging this connectivity issue?

Thanks and regards,
Ashish


From: Mokhtar, Amr <amr.mokhtar at intel.com<mailto:amr.mokhtar at intel.com>>
Sent: Monday, April 27, 2020 5:57 PM
To: Ashish Saxena <Ashish.Saxena at hsc.com<mailto:Ashish.Saxena at hsc.com>>
Subject: RE: Openvino application without hddl support


CAUTION:This email originated from an external organization
NTS learns the MAC addresses of the client-sim & the consumer-app at the initiation time. Therefore, when the app sends back the traffic, NTS uses the src & dst IP addresses in the pkt headers to translate the src & dst MAC addresses and accordingly routes the traffic back to client-sim.

From: Ashish Saxena <Ashish.Saxena at hsc.com<mailto:Ashish.Saxena at hsc.com>>
Sent: Monday 27 April 2020 12:39
To: Mokhtar, Amr <amr.mokhtar at intel.com<mailto:amr.mokhtar at intel.com>>
Subject: RE: Openvino application without hddl support

Hi Amr,

You understand my question correctly.
But I am not getting how the ip address of client-sim is known to consumer app .The rule applied for ingress traffic will allow the KNI interface to send the incoming traffic to the app , but how the reverse traffic is send back .
Can you please help me understand these doubts ?

Thanks and Regards,
Ashish

From: Mokhtar, Amr <amr.mokhtar at intel.com<mailto:amr.mokhtar at intel.com>>
Sent: Monday, April 27, 2020 4:41 PM
To: Ashish Saxena <Ashish.Saxena at hsc.com<mailto:Ashish.Saxena at hsc.com>>
Subject: RE: Openvino application without hddl support


CAUTION:This email originated from an external organization
I am not sure if I got your question correctly. But, generally the network policies are applied on ingress traffic.
The augmented video is transmitted from the openvino consumer app back to client-sim (which is its IP is known to the consumer app.)

From: Ashish Saxena <Ashish.Saxena at hsc.com<mailto:Ashish.Saxena at hsc.com>>
Sent: Monday 27 April 2020 11:40
To: Mokhtar, Amr <amr.mokhtar at intel.com<mailto:amr.mokhtar at intel.com>>
Subject: RE: Openvino application without hddl support

Hi Amr,

Thanks for the reply.

I am deploying the openvino app and trying to figure out how the client_sim is able to display the output as the traffic rule applied on consumer application is allowing only traffic in one direction (from clinet_sim to consumer container).Can you please help me understand how the output of openvino app is getting displayed at client_sim container?

Thanks and Regards,
Ashish

From: Mokhtar, Amr <amr.mokhtar at intel.com<mailto:amr.mokhtar at intel.com>>
Sent: Monday, April 27, 2020 2:41 PM
To: Ashish Saxena <Ashish.Saxena at hsc.com<mailto:Ashish.Saxena at hsc.com>>
Cc: developer at mail.openness.org<mailto:developer at mail.openness.org>
Subject: RE: Openvino application without hddl support


CAUTION:This email originated from an external organization
Hi Ashish,
Yes, you can. OpenVINO consumer app works in CPU-only mode by default.
https://github.com/open-ness/specs/blob/master/doc/applications/openness_openvino.md#openvino-producer-application<https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopen-ness%2Fspecs%2Fblob%2Fmaster%2Fdoc%2Fapplications%2Fopenness_openvino.md%23openvino-producer-application&data=02%7C01%7C%7C14465da3d5de4f484d1808d7eaa6543b%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637235872416386201&sdata=1yBpuJZKndBhpP3g0eTz%2FVdgf30IFGbknIk7Thcwtl0%3D&reserved=0>

-Amr

From: Ashish Saxena <Ashish.Saxena at hsc.com<mailto:Ashish.Saxena at hsc.com>>
Sent: Monday 27 April 2020 06:50
To: developer at mail.openness.org<mailto:developer at mail.openness.org>
Subject: Openvino application without hddl support

Hi Openness team.

Can we deploy openvino consumer application on the edgenode without hddl support ?

Thanks and Regards,
Ashish
DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.
DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.
DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.
DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.


More information about the Developer mailing list