Hi Michael & David & Yan,





I refesh the questions, and hope the SDC team can give some answers. I also 
think we need an meeting to discuss these issues. Thanks.







In SDC API document, we didn’t see the registration and notification API ,can 
you provide this API for us.


[Maopeng ]   thanks for micheal share the document, 
https://wiki.onap.org/pages/viewpage.action?pageId=11929307 


                     we will review it and It is very complicated api document.


                     If Micheal can give an example to the VFC team,  it will 
be great for the whole team.






How does the SDC Resource / Service Categories fits to the VoLTE case? for 
exmaple spgw/ims etc in which Categories/subCategory?


[Maopeng ]  Service categories can be defined by the administrator via the GUI. 
 I think if we need new categories or subcategories, we can add it via the GUI. 
Right? 






2.       VNF package


We want to know the VNF CSAR package format exported from SDC, can you give us 
an example, we want to confirm whether the package has some format restrictions.


[Maopeng ] In the R1,  VNFSDK bundles a VNF package, and import to the SDC. VFC 
get the VNF package from the SDC catalog.


                   Is the VNF package defined in the VNFSDK or SDC for R1? 
What's the VNF package format for VFC in R1?          






     2.  NS package


       Whether to support ELAN VL, which can be shared among VNFs.


          [Maopeng ] now the SDC supports VL, but it is automatically produced. 
 Now I can design the Eline type VL, but for the VoLTE case , we need multiple 
VNFs share one VL.


                              what's the automatic rule of VL creating? How to 
design it? could you show with us. thanks.






       Whether the metadata can be extended, from VF-C side we need some fields 
,such as controlinfo, vnfminfo,..etc, so we want to know Whether SDC support 
metadata extension   


          [Maopeng ] In VoLTE case we need the conrollerinfo in service to 
identify the NS and need the VNFM info in VF to identify the SVNFM.


                             If the SDC team can add the parameter in the 
metadata, it will be useful for the VFC  team. 


                             In the meeting of SO and SDC, DAVID suggests use 
the category parameter of metadata.  It can work, but not clear for user.






Best Regards


Maopeng



原始邮件



发件人: <yangya...@chinamobile.com>
收件人: <ml6...@intl.att.com>张茂鹏10030173 <denglin...@chinamobile.com>孟照星10024238 
<onap-discuss@lists.onap.org>
日 期 :2017年08月08日 18:13
主 题 :[sdc][vfc] SDC questions from VF-C







Hi Michael,


    VF-C team has some issues that need to be confirmed by SDC team.


1.       About SDC API(This has been listed in the blokers wiki page)


In SDC API document, we didn’t see the registration and notification API ,can 
you provide this API for us.


How does the SDC Resource / Service Categories fits to the VoLTE case? for 
exmaple spgw/ims etc in which Categories/subCategory?


2.       VNF package


We want to know the VNF CSAR package format exported from SDC, can you give us 
an example, we want to confirm whether the package has some format restrictions.


     2.  NS package


       Whether to support ELAN VL, which can be shared among VNFs.


       Whether the metadata can be extended, from VF-C side we need some fields 
,such as controlinfo, vnfminfo,..etc, so we want to know Whether SDC support 
metadata extension   


          Whether the NS package exported from SDC support TOSCA simple profile 
and standard, we want to confirm that these packages can be handled by parsers.


       


Hopefully we can get feedback from SDC team asap. If you want to know more 
details about these questions, we can also set a conf call. I suggest one time 
on Wednesday UTC 12:00/China 20:00. If you think it’s ok, I will send an 
invitation to you.


 


 


Best Regards,


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

Reply via email to