Re: [onap-discuss] [onap-tsc] Bridges for next week.

[Sabater, Susana, Vodafone Spain]

Hi Kenny,
Do we have the bridges set up? For Monday morning we expect to have some remote 
participants. Could you please confirm this will be possible?

Cheers
/Susana

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Kenny Paul
Sent: Thursday, December 7, 2017 7:26 PM
To: onap-discuss@lists.onap.org; onap-...@lists.onap.org
Subject: [onap-tsc] Bridges for next week.

Yes there will be dial-ins.
No, I have not set them up yet.
Yes, I will send mail when I’ve done so.

Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

[Sabater, Susana, Vodafone Spain]

Thanks Maopeng!
I was guessing that was the case when referencing IFA and not SOL specs. In any 
case, it will be good to update the links and make clear that VF-C does comply 
with NFV APIs and functionality, to avoid confusion as in this long thread.

Cheers!
/Susana

From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn]
Sent: Wednesday, November 15, 2017 8:32 AM
To: Sabater, Susana, Vodafone Spain <susana.saba...@vodafone.com>
Cc: jamil.cha...@orange.com; kp...@linuxfoundation.org; 
onap-discuss@lists.onap.org; onap-...@lists.onap.org; 
ajoship...@linuxfoundation.org; lcayw...@linuxfoundation.org
Subject: 答复: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide


Hi  Susana,



  VFC project in R1 includes NFVO and VNFM components, mainly 
focused on the NS LCM and VNFLCM.

 NSLCM  NBI and GVNFM NBI  please refer to 
https://wiki.onap.org/display/DW/VF-C+R1+Deliverables<https://wiki.onap.org/display/DW/VF-C+R1+Deliverables.>
  NSLCM API Specification 
v0.1<https://gerrit.onap.org/r/gitweb?p=vfc/nfvo/lcm.git;a=blob;f=lcm/swagger/vfc.nslcm.swagger.json;h=75cc6baba3d284df35102fb9fb41f10147f312a3;hb=refs/heads/master>.
  and GVNFM API Specification 
v0.1<https://wiki.onap.org/download/attachments/8230085/VNFM%20API-v0.1.pdf?version=1=150350606=v2>.

 As the project started, NSLCM and GVNFM mainly refer to IFA 
document and refer to the SOL Draft, because the SOL does not provide engough 
APIs and is not published at that time.

 Now SOL003 is published and SOL005 is still in the draft(almost 
stable), I compare the API of the SOL, the main flow is same and most of LCM 
interfaces be aligned.

 In the following release, VFC team will plan to align the SOL as 
needed and also consider the usecase requirements.

 In the R1, VFC has more work on the integration with other ONAP 
componenst. The document is not well formatted, we will try to do it in the 
next release.

 If interested about VFC projects, welcome to join, thanks.



BR

Maopeng
原始邮件
发件人： <susana.saba...@vodafone.com<mailto:susana.saba...@vodafone.com>>;
收件人： <jamil.cha...@orange.com<mailto:jamil.cha...@orange.com>>; 
<kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>>; 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>; 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>; 
<ajoship...@linuxfoundation.org<mailto:ajoship...@linuxfoundation.org>>; 
<lcayw...@linuxfoundation.org<mailto:lcayw...@linuxfoundation.org>>;
日 期 ：2017年11月14日 22:25
主 题 ：Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide


Hi,

Is it so that VF-C interfaces are not aligned with ETSI NFV ones? In the 
documentation of VF-C it appeared like aligned, but I observed  the reference 
is made to IFA007 and IFA008 and not to the published APIs, as opposed to 
referencing SOL005 for NS LCM.
In any case, it is difficult to find now the documentation of the VF-C; 
wouldn’t it be good to add relevant links to the modules, their  documentation, 
user guides, etc in the Amsterdam arch page?

Regards
/Susana

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of 
jamil.cha...@orange.com<mailto:jamil.cha...@orange.com>
Sent: Tuesday, November 14, 2017 10:41 AM
To: Kenny Paul <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>>; 
onap-discuss <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>; 
onap-tsc <onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>; Arpit 
Joshipura 
(ajoship...@linuxfoundation.org<mailto:ajoship...@linuxfoundation.org>) 
<ajoship...@linuxfoundation.org<mailto:ajoship...@linuxfoundation.org>>; Lisa 
Caywood <lcayw...@linuxfoundation.org<mailto:lcayw...@linuxfoundation.org>>
Subject: Re: [onap-tsc] Official ONAP Architecture Slide

Hello Kenny
I have a question on the ETSI aligned of VFC module, to my knowledge the VFC 
interfaces are not aligned with ETSI NFV.
I think we need to remove this term from VFC and to add that ONAP architecture 
is Functionally aligned with ETSI NFV..
Regards
Jamil

De : onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] De la part de Kenny Paul
Envoyé : mardi 14 novembre 2017 01:04
À : onap-discuss; onap-tsc
Cc : Lisa Caywood
Objet : [onap-tsc] Official ONAP Architecture Slide

As was pointed out in Paris there are too many variations of the Amsterdam 
architecture which is bad to say the least.
The officially approved image for the Amsterdam Architecture and be found here:
https://wiki.onap.org/download/attachments/1015842/ONAP%20Amsterdam%20arch.png?api=v2



In preparation for the release announcement here is what we are a

Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

[Sabater, Susana, Vodafone Spain]

And maybe it is wise to avoid making any statement that “ONAP is functionally 
aligned with ETSI NFV architecture”, since it will deeply confuse the audience 
trying to see the alignment.

Cheers
/Susana

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Lisa Caywood
Sent: Tuesday, November 14, 2017 4:19 PM
To: CHAWKI Jamil IMT/OLN 
Cc: onap-discuss ; onap-tsc 

Subject: Re: [onap-tsc] Official ONAP Architecture Slide

Jamil, we can not spell out the names of all of the components on the slide; 
there isn't room. It must be legible, including from a distance (eg in a public 
presentation).

Chris can answer #2.

Thanks, Lisa

On Tue, Nov 14, 2017 at 7:14 AM, 
> wrote:
Hello Kenny
Additional comments and proposals on this figure:

1- Remove ETSI NFV alignment from VFC and to replace it by a general note  
that ‘ONAP is functionally aligned with ETSI NFV architecture’

2- We need to remove AWS, Rackspace and Azure. Why Rackspace is listed and 
not WindRiver ?

3- MultiCloud Infrastructure Adaptation Layer => it is not an adaptation 
layer today. Replace it by Multi VIM/Cloud (official project name).

4- Replace SDN-C by SDN Controller, similar to Application Controller

5- VVP, VNF Requirements, Modelling, Testing & integration are not 
mentioned in the architecture

a. Proposals:

  i.To add Requirements and 
Validation with VNF SDK.

 ii.To add Modelling with CLAMP

iii.To add Test and Integration 
with OOM


6- We need to avoid the abbreviations like AAF, OOF …

a. Proposal to replace:

  i.SDC by Service Design Creation

 ii.Clamp by Closed Loop Design

iii.DMaaP by Data Movement

iv.A by Active & Available 
Inventory

 v.Holmes by Fault Correction

vi.DCAE by Data Collection 
Analytics and Events

   vii.AAF by Application Authorization 
Framework

  viii.CC SDK Common Controller SDK

ix.OOF by Optimization Framework


Regards
jamil


De : onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org]
 De la part de Kenny Paul
Envoyé : mardi 14 novembre 2017 01:04
À : onap-discuss; onap-tsc
Cc : Lisa Caywood
Objet : [onap-tsc] Official ONAP Architecture Slide

As was pointed out in Paris there are too many variations of the Amsterdam 
architecture which is bad to say the least.
The officially approved image for the Amsterdam Architecture and be found here:
https://wiki.onap.org/download/attachments/1015842/ONAP%20Amsterdam%20arch.png?api=v2



In preparation for the release announcement here is what we are asking in order 
of priority:

-If an archecture image is referecned in your official readthedocs 
documentation, please use this image

-If an archecture image is referenced in your wiki pages,  please add the URL 
above to reference the the image.

-If an archecture image is referecned in a presentation slide deck, please 
ensure you use this image.

I am intentionally NOT distributing it because that is how we ended up with so 
many versions in the first place. :-)

Thanks!



Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945


_



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.



--
__

Lisa Caywood
Director of Ecosystem Development

Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

[Sabater, Susana, Vodafone Spain]

Hi,

Is it so that VF-C interfaces are not aligned with ETSI NFV ones? In the 
documentation of VF-C it appeared like aligned, but I observed the reference is 
made to IFA007 and IFA008 and not to the published APIs, as opposed to 
referencing SOL005 for NS LCM.
In any case, it is difficult to find now the documentation of the VF-C; 
wouldn't it be good to add relevant links to the modules, their documentation, 
user guides, etc in the Amsterdam arch page?

Regards
/Susana

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of jamil.cha...@orange.com
Sent: Tuesday, November 14, 2017 10:41 AM
To: Kenny Paul ; onap-discuss 
; onap-tsc ; Arpit 
Joshipura (ajoship...@linuxfoundation.org) ; 
Lisa Caywood 
Subject: Re: [onap-tsc] Official ONAP Architecture Slide

Hello Kenny
I have a question on the ETSI aligned of VFC module, to my knowledge the VFC 
interfaces are not aligned with ETSI NFV.
I think we need to remove this term from VFC and to add that ONAP architecture 
is Functionally aligned with ETSI NFV.
Regards
Jamil

De : onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] De la part de Kenny Paul
Envoyé : mardi 14 novembre 2017 01:04
À : onap-discuss; onap-tsc
Cc : Lisa Caywood
Objet : [onap-tsc] Official ONAP Architecture Slide

As was pointed out in Paris there are too many variations of the Amsterdam 
architecture which is bad to say the least.
The officially approved image for the Amsterdam Architecture and be found here:
https://wiki.onap.org/download/attachments/1015842/ONAP%20Amsterdam%20arch.png?api=v2



In preparation for the release announcement here is what we are asking in order 
of priority:

-If an archecture image is referecned in your official readthedocs 
documentation, please use this image

-If an archecture image is referenced in your wiki pages,  please add the URL 
above to reference the the image.

-If an archecture image is referecned in a presentation slide deck, please 
ensure you use this image.

I am intentionally NOT distributing it because that is how we ended up with so 
many versions in the first place. :-)

Thanks!



Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945


_



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.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss