Dear Alla

Yes. We can support other use cases.
If we get UI requirements of additional use cases, I'd like to discuss them
with ONAPers.

Best regards,
Tao


-----邮件原件-----
发件人: Alla Goldner [mailto:[email protected]] 
发送时间: 2017年8月16日 20:50
收件人: shentao; 'GILBERT, MAZIN E (MAZIN E)'
抄送: [email protected]
主题: RE: [onap-discuss] [DCAE] DCAE questions from Usecase UI

Hi Tao,

So, I guess, we resolved one outstanding issue for vVoLTE support!

One question - with this design in place, I guess, it will not be difficult
to support additional use cases UI, am I right?

 Best regards, 

Alla Goldner

Open Network Division 
Amdocs Technology





-----Original Message-----
From: shentao [mailto:[email protected]] 
Sent: Wednesday, August 16, 2017 2:12 PM
To: 'GILBERT, MAZIN E (MAZIN E)' <[email protected]>; Alla Goldner
<[email protected]>
Cc: [email protected]
Subject: 答复: [onap-discuss] [DCAE] DCAE questions from Usecase UI

Hi, Mazin and Alla

I have discussed this issue with Lusheng and reached an agreement.
The solution is that Usecase UI will get alarm and performance data via
Dmaap and support data storage.
So it isn't difficult to display alarm and performance data by UI.
Thanks for your attention.

Best regards,
Tao


-----邮件原件-----
发件人: [email protected]
[mailto:[email protected]] 代表 GILBERT, MAZIN E (MAZIN E)
发送时间: 2017年8月14日 23:02
收件人: Alla Goldner
抄送: [email protected]
主题: Re: [onap-discuss] [DCAE] DCAE questions from Usecase UI

I would like to understand how much of the work is app specific to VoLTE. We
really should leverage any UI across all use cases especially if it is
generating custom platform work. I will wait for the PTLs to share more
info.

Thanks
Mazin 

Sent through AT&T's fastest network 

> On Aug 14, 2017, at 5:43 AM, Alla Goldner <[email protected]> wrote:
> 
>  



This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer
<https://www.amdocs.com/about/email-disclaimer>



_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to