Re: [onap-tsc] ONAP deployment baseline

[Jim Baker]

Thanks Eric for adding more context around the OVP testing. To further
expound on the testing, there are 3 classes of testing:

   1. Compliance - is the VNF packaged to the standards that will allow it
   to integrated in the defined infrastructure?
   2. Verification - does the VNF behave correctly? (onboarding, lifecycle,
   orchestration, change mgmt, etc)
   3. Performance - how does the VNF perform against industry benchmarks?

#1 does not require a stood-up instance. #2 and #3 do... Since #1 is
available today, we are now looking to #2 for the OVP badging - hence
bringing ONAP deployment more into the workstream for VNF vendors.

On Thu, Apr 18, 2019 at 1:37 PM Eric Debeau  wrote:

> Hello Jim
>
>
>
> « Ease of Deployment » is important and OOM team (with the community) is
> working hard to ease the deployment.
>
>
>
> The first OVP Program step is only to validate the VNF package/descriptor.
> There is no need to deploy full ONAP for that.
>
> VNF Vendor just need to run VVP or VNFSDK to check their
> package/descriptor. It is an easy task.
>
> We have developed a portal for VVP and DT also proposed their portal to
> help any vendor to test their VNF using Heat descriptor.
>
>
>
> To fully test VNF within ONAP and to check the full onboarding,
> deployment, configuration and closed-loop, they need to deploy a full ONAP.
>
> I believe that all ‘main’ vendors have deployed ONAP in their labs.
>
>
>
> I agree that we must help ‘small’ VNF vendors with ONAP community
> solutions to avoid them to deploy a full ONAP or we must provide more
> adapted ONAP deployment to test their VNF managed by ONAP. That is why I
> advocated from Day0 to get a small footprint for ONAP. Within OOM project,
> we defined an override file to only deploy a subset of ONAP components to
> enable on-boarding and deployment.
>
>
>
> In addition, Orange OpenLab welcomes different VNF vendor that can test
> their VNF.
>
>
>
> Best Regards
>
>
>
> Eric
>
>
>
> *De :* onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] *De la
> part de* Jim Baker
> *Envoyé :* jeudi 18 avril 2019 20:04
> *À :* onap-tsc
> *Objet :* [onap-tsc] ONAP deployment baseline
>
>
>
> Greeting ONAP TSC,
>
> One of my areas of contribution within LFN is on the OVP program. As the
> OVP program seeks to attract a marketplace of verified VNFs, the developers
> of the VNFs have the task of completing testing using ONAP. Before they can
> begin the self-testing work required by the OVP, they need to have deployed
> ONAP and OpenStack before that
> 
> ...
>
>
>
> My question is: Is "ease of install" a system attribute that we have
> baselined AND improve upon?
>
>
>
> My desired outcome from raising this question is to accurately state for
> VNF developers an estimation of the process time required currently to
> deploy ONAP AND to understand the interest in the community of investing in
> "ease of deployment"  to improve the end-user experience.
>
>
>
> Thanks for sharing your thoughts!
>
>
>
> --
>
> Jim Baker
>
> Linux Foundation Networking - Technical Program Manager
>
> mobile: +1 970 227 6007
>
> _
>
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.
>
> 
>
>

-- 
Jim Baker
Linux Foundation Networking - Technical Program Manager
mobile: +1 970 227 6007

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4873): https://lists.onap.org/g/onap-tsc/message/4873
Mute This Topic: https://lists.onap.org/mt/31234067/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] ONAP deployment baseline

[Eric Debeau]

Hello Jim

« Ease of Deployment » is important and OOM team (with the community) is 
working hard to ease the deployment.

The first OVP Program step is only to validate the VNF package/descriptor. 
There is no need to deploy full ONAP for that.
VNF Vendor just need to run VVP or VNFSDK to check their package/descriptor. It 
is an easy task.
We have developed a portal for VVP and DT also proposed their portal to help 
any vendor to test their VNF using Heat descriptor.

To fully test VNF within ONAP and to check the full onboarding, deployment, 
configuration and closed-loop, they need to deploy a full ONAP.
I believe that all ‘main’ vendors have deployed ONAP in their labs.

I agree that we must help ‘small’ VNF vendors with ONAP community solutions to 
avoid them to deploy a full ONAP or we must provide more adapted ONAP 
deployment to test their VNF managed by ONAP. That is why I advocated from Day0 
to get a small footprint for ONAP. Within OOM project, we defined an override 
file to only deploy a subset of ONAP components to enable on-boarding and 
deployment.

In addition, Orange OpenLab welcomes different VNF vendor that can test their 
VNF.

Best Regards

Eric

De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de Jim 
Baker
Envoyé : jeudi 18 avril 2019 20:04
À : onap-tsc
Objet : [onap-tsc] ONAP deployment baseline

Greeting ONAP TSC,
One of my areas of contribution within LFN is on the OVP program. As the OVP 
program seeks to attract a marketplace of verified VNFs, the developers of the 
VNFs have the task of completing testing using ONAP. Before they can begin the 
self-testing work required by the OVP, they need to have deployed ONAP and 
OpenStack before 
that...

My question is: Is "ease of install" a system attribute that we have baselined 
AND improve upon?

My desired outcome from raising this question is to accurately state for VNF 
developers an estimation of the process time required currently to deploy ONAP 
AND to understand the interest in the community of investing in "ease of 
deployment"  to improve the end-user experience.

Thanks for sharing your thoughts!

--
Jim Baker
Linux Foundation Networking - Technical Program Manager
mobile: +1 970 227 6007


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4872): https://lists.onap.org/g/onap-tsc/message/4872
Mute This Topic: https://lists.onap.org/mt/31234067/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Next week meeting and plan for El-Alto/Frankfurt

[Alla Goldner]

Hi all,

Next week's Usecase subcommittee meeting will be cancelled due to Passover 
holidays. Happy Holidays to all people celebrating it!!!

On the use cases/functional requirements preparation plan, Catherine will kick 
off voting within the TSC. Only after that we will be able to communicate a 
more detailed plan regarding the timelines and scope.

Beast Regards, Alla
This email and the information contained herein is proprietary and confidential 
and subject to the Amdocs Email Terms of Service, which you may review at 
https://www.amdocs.com/about/email-terms-of-service 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4869): https://lists.onap.org/g/onap-tsc/message/4869
Mute This Topic: https://lists.onap.org/mt/31224648/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] !!! ONAP Dublin - Call for Action !!!

[Catherine LEFEVRE]

Dear Use Case/Functional and Non-Functional Owners,

I want to inform you about a decision that the TSC took during the TSC call on 
4/18.

TSC agreed that, if no feedback provided to Jim by 4/22 EOD,  any requirement 
(use case, functional requirement, non-functional requirement), currently 
marked in yellow/(red), not due to testing blockers/issues,
will be moved to the Dublin POC section a.k.a no more be part of the official 
release.

Please take immediate action and talk to Jim - thank you !

Best regards
Catherine

[cid:image001.jpg@01D4F60A.B1947770]

Catherine Lefèvre
AVP Software Development & Engineering

AT Labs - Network Cloud & Infrastructure
D2 Platform & Systems Development
ECOMP/RUBY/SPP-NEAM-Appl. Servers/SIA
ONAP TSC Chair


Phone: +32 81 84 09 08
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING... It Can Wait

AT
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4868): https://lists.onap.org/g/onap-tsc/message/4868
Mute This Topic: https://lists.onap.org/mt/31224539/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Proposed Dublin Architecture Slides

[Stephen Terrill]

Hi Shankar,

As this should be a functional approach, terms like “growing set” etc “ little 
code development” should be avoided, the don’t really capture a functional 
description (which should address what it does or what its purpose).

I propose:

“
Provides optimization services for the optimization of the managed environment. 
 Optimization services covers capabilities such as, VNF placement, PNF 
selection, Self-Optimizing-Network (SON) support, change scheduling.”

BR,

Steve


From: onap-tsc@lists.onap.org  On Behalf Of Shankar 
Narayanan
Sent: Wednesday 17 April 2019 19:05
To: onap-tsc 
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve,

Can you please replace the description of OOF with the following, which also 
provides an intuition on the flavors of optimizations that can be supported by 
OOF.

Provides a growing set of core platform optimization services like, 
VNF/PNF/Service placement (HAS), SON optimization (PCI/ANR), Change Scheduling 
(CMSO) etc. OOF platform enables a model-driven approach to creation of new 
optimization services with minimal or little new code development.

Thanks,
Shankar.
--
Shankaranarayanan Puzhavakath Narayanan
Senior Inventive Scientist
Network and Cloud Systems Research
AT Labs Research


On Wed, Apr 17, 2019 at 11:41 AM Mandar Sawant 
mailto:ms5...@att.com>> wrote:
Hi Steve,

DMaaP is missing in the description slides.

Here’s the description from one of the previous ppt:

Data movement as a platform (DMaaP) is a premier platform for high performing 
and cost effective data movement services that transports and processes data 
from any source to any target with the format, quality, security, and 
concurrency required to serve the business and customer needs.

Thanks,
Mandar

AT Proprietary (Internal Use Only)
Not for use or disclosure outside the AT companies except under written 
agreement

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Andreas 
Geissler
Sent: Wednesday, April 17, 2019 2:52 AM
To: onap-tsc@lists.onap.org
Cc: adetalhoue...@gmail.com; MALAKOV, YURIY 
mailto:ym9...@att.com>>
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve,

Just some short corrections and question:

  *   Slide 5: missing “c” in lifecyle
  *   Slide 7 SDNC:
In the Note should it be “In Dublin, CDS is a standalone …” and shouldn’t this 
be a note for SDC (Alexis, Yuriy?) ?

Best regards
Andreas

Von: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> Im Auftrag von 
Stephen Terrill
Gesendet: Mittwoch, 17. April 2019 09:21
An: onap-tsc@lists.onap.org
Betreff: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Eric,

Thanks for the feedback.

  *   POMBA and MUSIC are explained in slides 5-9.  If you mean expand it on 
the main slide – its more a slide real-estate limitation at the moment.

Regarding the colors.  The discussion that we had around them was to have the 
network interacting functions at the bottom and one color and the other 
(runtime) parts another color.  This could be changed of course, but then I 
would like more views as it would be going back on the conversation that we had 
in ArchCom.

BR,

Steve

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Eric 
Debeau
Sent: Wednesday 17 April 2019 08:45
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Stephen,

I believe that we should explain what POMBA and MUSIC are.

For color code, why Holmes is not as the same color as  DCAE ?

I would propose that we use the same color code in ONAP project for 
documentation and any other material

Blue for Design Time
Green for Run Time

  *   Dark Green for controller
  *   Light Green for Common Services

Exact color code should be based on the one used for the PPT template.

Best Regards

Eric

De : onap-tsc@lists.onap.org 
[mailto:onap-tsc@lists.onap.org] De la part de Stephen Terrill
Envoyé : mercredi 17 avril 2019 08:31
À : onap-tsc@lists.onap.org
Objet : Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi,

Please find an update incorporating updated text on the DCAE definition from 
Vijay.

Best Regards,

Steve

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Stephen 
Terrill
Sent: Tuesday 16 April 2019 23:39
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi All,

I missed a comment from Amy, please look at this version instead.

BR,

Steve

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On 

Re: [onap-tsc] Proposed Dublin Architecture Slides

[Stephen Terrill]

Hi Mandar,

I propose to include the following, which is a compression of what is in the 
component description for DMaaP.

"DMaaP provides data movement services that transports and processes data from 
any source to any target. This includes Message transfer services and data 
transfer services.  It provides further services such as filtering, 
compression, ..."

BR,

Steve

From: onap-tsc@lists.onap.org  On Behalf Of Mandar 
Sawant
Sent: Wednesday 17 April 2019 16:05
To: onap-tsc@lists.onap.org
Cc: adetalhoue...@gmail.com; MALAKOV, YURIY 
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve,

DMaaP is missing in the description slides.

Here's the description from one of the previous ppt:

Data movement as a platform (DMaaP) is a premier platform for high performing 
and cost effective data movement services that transports and processes data 
from any source to any target with the format, quality, security, and 
concurrency required to serve the business and customer needs.

Thanks,
Mandar

AT Proprietary (Internal Use Only)
Not for use or disclosure outside the AT companies except under written 
agreement

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Andreas 
Geissler
Sent: Wednesday, April 17, 2019 2:52 AM
To: onap-tsc@lists.onap.org
Cc: adetalhoue...@gmail.com; MALAKOV, YURIY 
mailto:ym9...@att.com>>
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve,

Just some short corrections and question:

  *   Slide 5: missing "c" in lifecyle
  *   Slide 7 SDNC:
In the Note should it be "In Dublin, CDS is a standalone ..." and shouldn't 
this be a note for SDC (Alexis, Yuriy?) ?

Best regards
Andreas

Von: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> Im Auftrag von 
Stephen Terrill
Gesendet: Mittwoch, 17. April 2019 09:21
An: onap-tsc@lists.onap.org
Betreff: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Eric,

Thanks for the feedback.

  *   POMBA and MUSIC are explained in slides 5-9.  If you mean expand it on 
the main slide - its more a slide real-estate limitation at the moment.

Regarding the colors.  The discussion that we had around them was to have the 
network interacting functions at the bottom and one color and the other 
(runtime) parts another color.  This could be changed of course, but then I 
would like more views as it would be going back on the conversation that we had 
in ArchCom.

BR,

Steve

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Eric 
Debeau
Sent: Wednesday 17 April 2019 08:45
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Stephen,

I believe that we should explain what POMBA and MUSIC are.

For color code, why Holmes is not as the same color as  DCAE ?

I would propose that we use the same color code in ONAP project for 
documentation and any other material

Blue for Design Time
Green for Run Time

  *   Dark Green for controller
  *   Light Green for Common Services

Exact color code should be based on the one used for the PPT template.

Best Regards

Eric

De : onap-tsc@lists.onap.org 
[mailto:onap-tsc@lists.onap.org] De la part de Stephen Terrill
Envoyé : mercredi 17 avril 2019 08:31
À : onap-tsc@lists.onap.org
Objet : Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi,

Please find an update incorporating updated text on the DCAE definition from 
Vijay.

Best Regards,

Steve

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Stephen 
Terrill
Sent: Tuesday 16 April 2019 23:39
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi All,

I missed a comment from Amy, please look at this version instead.

BR,

Steve

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Stephen 
Terrill
Sent: Tuesday 16 April 2019 23:23
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi All,

Thanks for the feedback, the good catches and comments are appreciated.

@Dan, I have added the note
@Ofir, @Seshu, apologies for the omission I have added entries for SO and SDC.

The update is attatched.

Best Regards,

Steve.

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Stephen 
Terrill
Sent: Monday 15 April 2019 13:35
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Proposed Dublin Architecture Slides

Hi,

Please find attatched the proposed Dublin architecture slides.  This is a 
reduced slide set compared to 

Re: [onap-tsc] Proposed Dublin Architecture Slides

[Stephen Terrill]

Hi Deng,

Then we could consider to put a TOSCA Parser as a common service.  I don’t 
think that the implementation consideration of whether it’s a mocroservice or 
not influences whether its is considered a commont service (that is the tail 
wagging the dog) or the common library from a *functional* perspective.  The 
consideration is whether it is considered to provide a function (functionality) 
serving other functions, or whether it provides something that is used “IN” 
other functions at this level.

BR,

Steve

From: onap-tsc@lists.onap.org  On Behalf Of denghui (L)
Sent: Thursday 18 April 2019 14:18
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve

Yang yan’s team is working on micro service based parser in R4 which will be 
used by VFC and UUI,
so maybe it have to  belong to both common library (NFV Parser from 
OPNFV/Openstack) and Common services.( Micro service based)

Thanks a lot for your reminder
Best regards,

DENG Hui

From: onap-tsc@lists.onap.org 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Stephen Terrill
Sent: Thursday, April 18, 2019 8:13 PM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Deng,

Modelling is the common libraries to capture it there, could you expand on why 
you feel it should be in the common services instead of the common library?

BR,

Steve

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of denghui 
(L)
Sent: Thursday 18 April 2019 05:13
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve

Could you kindly help to add “Modeling” into the “Common Services” of Dublin 
Architecture diagram.
Thanks a lot for  your help

DENG Hui

From: onap-tsc@lists.onap.org 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Shankar Narayanan
Sent: Thursday, April 18, 2019 1:05 AM
To: onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve,

Can you please replace the description of OOF with the following, which also 
provides an intuition on the flavors of optimizations that can be supported by 
OOF.

Provides a growing set of core platform optimization services like, 
VNF/PNF/Service placement (HAS), SON optimization (PCI/ANR), Change Scheduling 
(CMSO) etc. OOF platform enables a model-driven approach to creation of new 
optimization services with minimal or little new code development.

Thanks,
Shankar.
--
Shankaranarayanan Puzhavakath Narayanan
Senior Inventive Scientist
Network and Cloud Systems Research
AT Labs Research


On Wed, Apr 17, 2019 at 11:41 AM Mandar Sawant 
mailto:ms5...@att.com>> wrote:
Hi Steve,

DMaaP is missing in the description slides.

Here’s the description from one of the previous ppt:

Data movement as a platform (DMaaP) is a premier platform for high performing 
and cost effective data movement services that transports and processes data 
from any source to any target with the format, quality, security, and 
concurrency required to serve the business and customer needs.

Thanks,
Mandar

AT Proprietary (Internal Use Only)
Not for use or disclosure outside the AT companies except under written 
agreement

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Andreas 
Geissler
Sent: Wednesday, April 17, 2019 2:52 AM
To: onap-tsc@lists.onap.org
Cc: adetalhoue...@gmail.com; MALAKOV, YURIY 
mailto:ym9...@att.com>>
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve,

Just some short corrections and question:

  *   Slide 5: missing “c” in lifecyle
  *   Slide 7 SDNC:
In the Note should it be “In Dublin, CDS is a standalone …” and shouldn’t this 
be a note for SDC (Alexis, Yuriy?) ?

Best regards
Andreas

Von: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> Im Auftrag von 
Stephen Terrill
Gesendet: Mittwoch, 17. April 2019 09:21
An: onap-tsc@lists.onap.org
Betreff: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Eric,

Thanks for the feedback.

  *   POMBA and MUSIC are explained in slides 5-9.  If you mean expand it on 
the main slide – its more a slide real-estate limitation at the moment.

Regarding the colors.  The discussion that we had around them was to have the 
network interacting functions at the bottom and one color and the other 
(runtime) parts another color.  This could be changed of course, but then I 
would like more views as it would be going back on the conversation that we had 
in ArchCom.

BR,

Steve

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> 

Re: [onap-tsc] Proposed Dublin Architecture Slides

[denghui (L)]

Hi Steve

Yang yan’s team is working on micro service based parser in R4 which will be 
used by VFC and UUI,
so maybe it have to  belong to both common library (NFV Parser from 
OPNFV/Openstack) and Common services.( Micro service based)

Thanks a lot for your reminder
Best regards,

DENG Hui

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Stephen Terrill
Sent: Thursday, April 18, 2019 8:13 PM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Deng,

Modelling is the common libraries to capture it there, could you expand on why 
you feel it should be in the common services instead of the common library?

BR,

Steve

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of denghui 
(L)
Sent: Thursday 18 April 2019 05:13
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve

Could you kindly help to add “Modeling” into the “Common Services” of Dublin 
Architecture diagram.
Thanks a lot for  your help

DENG Hui

From: onap-tsc@lists.onap.org 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Shankar Narayanan
Sent: Thursday, April 18, 2019 1:05 AM
To: onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve,

Can you please replace the description of OOF with the following, which also 
provides an intuition on the flavors of optimizations that can be supported by 
OOF.

Provides a growing set of core platform optimization services like, 
VNF/PNF/Service placement (HAS), SON optimization (PCI/ANR), Change Scheduling 
(CMSO) etc. OOF platform enables a model-driven approach to creation of new 
optimization services with minimal or little new code development.

Thanks,
Shankar.
--
Shankaranarayanan Puzhavakath Narayanan
Senior Inventive Scientist
Network and Cloud Systems Research
AT Labs Research


On Wed, Apr 17, 2019 at 11:41 AM Mandar Sawant 
mailto:ms5...@att.com>> wrote:
Hi Steve,

DMaaP is missing in the description slides.

Here’s the description from one of the previous ppt:

Data movement as a platform (DMaaP) is a premier platform for high performing 
and cost effective data movement services that transports and processes data 
from any source to any target with the format, quality, security, and 
concurrency required to serve the business and customer needs.

Thanks,
Mandar

AT Proprietary (Internal Use Only)
Not for use or disclosure outside the AT companies except under written 
agreement

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Andreas 
Geissler
Sent: Wednesday, April 17, 2019 2:52 AM
To: onap-tsc@lists.onap.org
Cc: adetalhoue...@gmail.com; MALAKOV, YURIY 
mailto:ym9...@att.com>>
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve,

Just some short corrections and question:

  *   Slide 5: missing “c” in lifecyle
  *   Slide 7 SDNC:
In the Note should it be “In Dublin, CDS is a standalone …” and shouldn’t this 
be a note for SDC (Alexis, Yuriy?) ?

Best regards
Andreas

Von: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> Im Auftrag von 
Stephen Terrill
Gesendet: Mittwoch, 17. April 2019 09:21
An: onap-tsc@lists.onap.org
Betreff: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Eric,

Thanks for the feedback.

  *   POMBA and MUSIC are explained in slides 5-9.  If you mean expand it on 
the main slide – its more a slide real-estate limitation at the moment.

Regarding the colors.  The discussion that we had around them was to have the 
network interacting functions at the bottom and one color and the other 
(runtime) parts another color.  This could be changed of course, but then I 
would like more views as it would be going back on the conversation that we had 
in ArchCom.

BR,

Steve

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Eric 
Debeau
Sent: Wednesday 17 April 2019 08:45
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Stephen,

I believe that we should explain what POMBA and MUSIC are.

For color code, why Holmes is not as the same color as  DCAE ?

I would propose that we use the same color code in ONAP project for 
documentation and any other material

Blue for Design Time
Green for Run Time

  *   Dark Green for controller
  *   Light Green for Common Services

Exact color code should be based on the one used for the PPT template.

Best Regards

Eric

De : onap-tsc@lists.onap.org 
[mailto:onap-tsc@lists.onap.org] De la part de Stephen Terrill
Envoyé : 

Re: [onap-tsc] Proposed Dublin Architecture Slides

[Stephen Terrill]

Hi Deng,

Modelling is the common libraries to capture it there, could you expand on why 
you feel it should be in the common services instead of the common library?

BR,

Steve

From: onap-tsc@lists.onap.org  On Behalf Of denghui (L)
Sent: Thursday 18 April 2019 05:13
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve

Could you kindly help to add “Modeling” into the “Common Services” of Dublin 
Architecture diagram.
Thanks a lot for  your help

DENG Hui

From: onap-tsc@lists.onap.org 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Shankar Narayanan
Sent: Thursday, April 18, 2019 1:05 AM
To: onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve,

Can you please replace the description of OOF with the following, which also 
provides an intuition on the flavors of optimizations that can be supported by 
OOF.

Provides a growing set of core platform optimization services like, 
VNF/PNF/Service placement (HAS), SON optimization (PCI/ANR), Change Scheduling 
(CMSO) etc. OOF platform enables a model-driven approach to creation of new 
optimization services with minimal or little new code development.

Thanks,
Shankar.
--
Shankaranarayanan Puzhavakath Narayanan
Senior Inventive Scientist
Network and Cloud Systems Research
AT Labs Research


On Wed, Apr 17, 2019 at 11:41 AM Mandar Sawant 
mailto:ms5...@att.com>> wrote:
Hi Steve,

DMaaP is missing in the description slides.

Here’s the description from one of the previous ppt:

Data movement as a platform (DMaaP) is a premier platform for high performing 
and cost effective data movement services that transports and processes data 
from any source to any target with the format, quality, security, and 
concurrency required to serve the business and customer needs.

Thanks,
Mandar

AT Proprietary (Internal Use Only)
Not for use or disclosure outside the AT companies except under written 
agreement

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Andreas 
Geissler
Sent: Wednesday, April 17, 2019 2:52 AM
To: onap-tsc@lists.onap.org
Cc: adetalhoue...@gmail.com; MALAKOV, YURIY 
mailto:ym9...@att.com>>
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve,

Just some short corrections and question:

  *   Slide 5: missing “c” in lifecyle
  *   Slide 7 SDNC:
In the Note should it be “In Dublin, CDS is a standalone …” and shouldn’t this 
be a note for SDC (Alexis, Yuriy?) ?

Best regards
Andreas

Von: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> Im Auftrag von 
Stephen Terrill
Gesendet: Mittwoch, 17. April 2019 09:21
An: onap-tsc@lists.onap.org
Betreff: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Eric,

Thanks for the feedback.

  *   POMBA and MUSIC are explained in slides 5-9.  If you mean expand it on 
the main slide – its more a slide real-estate limitation at the moment.

Regarding the colors.  The discussion that we had around them was to have the 
network interacting functions at the bottom and one color and the other 
(runtime) parts another color.  This could be changed of course, but then I 
would like more views as it would be going back on the conversation that we had 
in ArchCom.

BR,

Steve

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Eric 
Debeau
Sent: Wednesday 17 April 2019 08:45
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Stephen,

I believe that we should explain what POMBA and MUSIC are.

For color code, why Holmes is not as the same color as  DCAE ?

I would propose that we use the same color code in ONAP project for 
documentation and any other material

Blue for Design Time
Green for Run Time

  *   Dark Green for controller
  *   Light Green for Common Services

Exact color code should be based on the one used for the PPT template.

Best Regards

Eric

De : onap-tsc@lists.onap.org 
[mailto:onap-tsc@lists.onap.org] De la part de Stephen Terrill
Envoyé : mercredi 17 avril 2019 08:31
À : onap-tsc@lists.onap.org
Objet : Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi,

Please find an update incorporating updated text on the DCAE definition from 
Vijay.

Best Regards,

Steve

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Stephen 
Terrill
Sent: Tuesday 16 April 2019 23:39
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi All,

I missed a comment from Amy, please look at this version instead.