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  NSLCM API Specification 
v0.1.  and GVNFM API Specification v0.1.


             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>;
收件人: <jamil.cha...@orange.com>; <kp...@linuxfoundation.org>; 
<onap-disc...@lists.onap.org>; <onap-tsc@lists.onap.org>; 
<ajoship...@linuxfoundation.org>; <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] 
On Behalf Of jamil.cha...@orange.com
 Sent: Tuesday, November 14, 2017 10:41 AM
 To: Kenny Paul <kp...@linuxfoundation.org>; onap-discuss 
<onap-disc...@lists.onap.org>; onap-tsc <onap-tsc@lists.onap.org>; Arpit 
Joshipura (ajoship...@linuxfoundation.org) <ajoship...@linuxfoundation.org>; 
Lisa Caywood <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] 
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-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Reply via email to