Hi The different users/roles will be supported in R1 I am not sure that it possible to customize the roles/user groups and their responsibilities during the process.
David Can you answer the second question? Best regards Tal Halfon Development Manager @ Amdocs P. +972 54 2213763 [cid:image001.png@01D2DC45.AD6F91B0] [ONAP_logo_Sig] From: Lingli Deng [mailto:denglin...@chinamobile.com] Sent: Wednesday, August 23, 2017 11:24 AM To: Halfon Tal <halfon....@amdocs.com>; 'SHADMI, DAVID' <ds2...@att.com>; 'Murali p' <mural...@huawei.com>; 'Christopher Donley (Chris)' <christopher.don...@huawei.com>; 'LANDO, MICHAEL' <ml6...@intl.att.com> Cc: 'LU, TINGTING' <tl2...@att.com>; onap-discuss@lists.onap.org Subject: RE: [onap-discuss] Clarifying VNFSDK<->SDC Hi Tal, In the Demo, there are different users/roles to collaborate in fulfilling the whole procedure in SDC. Designer, tester, governor, etc. Would it be the same for ONAP R1? Is it possible to customize the roles/user groups and their responsibilities during the process? Thanks, Lingli From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Halfon Tal Sent: 2017年8月23日 14:09 To: SHADMI, DAVID <ds2...@att.com<mailto:ds2...@att.com>>; Murali p <mural...@huawei.com<mailto:mural...@huawei.com>>; Christopher Donley (Chris) <christopher.don...@huawei.com<mailto:christopher.don...@huawei.com>>; LANDO, MICHAEL <ml6...@intl.att.com<mailto:ml6...@intl.att.com>> Cc: LU, TINGTING <tl2...@att.com<mailto:tl2...@att.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: Re: [onap-discuss] Clarifying VNFSDK<->SDC Hi For now the scenario we are going to support is the scenario below. We are working to see if we can change it but I am not sure it will be ready for R1 1. SDC user selects “Onboard” option (upper bar) and presented with Onboarding Workplace 2. SDC user will create Vendor license using Create VLM/ The user will need to insert only vendor name 3. SDC user selects “Create VSP” ( VSP: Vendor software product ) 4. SDC user will need to fill * Name * Vendor * Category * And to choose the onboarding procedure network package 5. SDC user selects to upload a VNF package 6. SDC will validate during the upload the CSAR and the descriptors 7. The VSP with all the VNF package data will be shown on the onboarding catalog/workspace ready to use Best regards Tal Halfon Development Manager @ Amdocs P. +972 54 2213763 [cid:image001.png@01D2DC45.AD6F91B0] [ONAP_logo_Sig] From: SHADMI, DAVID [mailto:ds2...@att.com] Sent: Tuesday, August 22, 2017 11:49 PM To: Murali p <mural...@huawei.com<mailto:mural...@huawei.com>>; Christopher Donley (Chris) <christopher.don...@huawei.com<mailto:christopher.don...@huawei.com>>; Halfon Tal <halfon....@amdocs.com<mailto:halfon....@amdocs.com>>; LANDO, MICHAEL <ml6...@intl.att.com<mailto:ml6...@intl.att.com>> Cc: Gaoweitao (Victor, MANO) <victor....@huawei.com<mailto:victor....@huawei.com>>; Vul, Alex <alex....@intel.com<mailto:alex....@intel.com>>; LU, TINGTING <tl2...@att.com<mailto:tl2...@att.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: Clarifying VNFSDK<->SDC Hi, I am adding Tal Halfon (Amdocs) who could provide more detailed information about the actual flows. Onboarding flow - Marketplace option (user scenario): 1. SDC user selects “Onboard” option (upper bar) and presented with Onboarding Workplace 2. SDC user selects “Onboard VNF” (new Option in R1) 3. SDC user selects either to upload a VNF package file or to “Browse Marketplace” 4. SDC user selects to “Browse Marketplace” and presented with a list of validated VNFs SDC user can search/sort Marketplace according to: * VNF Name * Vendor Name * Keywords 1. SDC user selects VNF and VNF information is presented 2. SDC user downloads VNF 3. SDC user is presented with a screen with the information from the VNF package (VNF Name, Vendor, Version) 4. SDC user adds service provider information (license model, category) to the VNF Steps 1-3 and 7-8 are the same for manual upload of VNF TOSCA package and would be implemented by Tal’s team. The integration between SDC and Market Place are steps 4-6 which include some UI development (can reuse some of SDC existing screens), integration with Market Place API, and integration with SDC import TOSCA API being implemented by Tal’s team. @Tal - could you please advise on the proposed flow and help the SDKVNF team with the code and information to implement the integration with the Market Place? @Michael - could you please help with SDC environment setup? Thanks, David From: Murali p [mailto:mural...@huawei.com] Sent: Tuesday, August 22, 2017 5:42 AM To: SHADMI, DAVID <ds2...@att.com<mailto:ds2...@att.com>>; Christopher Donley (Chris) <christopher.don...@huawei.com<mailto:christopher.don...@huawei.com>> Cc: Gaoweitao (Victor, MANO) <victor....@huawei.com<mailto:victor....@huawei.com>>; Vul, Alex <alex....@intel.com<mailto:alex....@intel.com>>; LU, TINGTING <tl2...@att.com<mailto:tl2...@att.com>>; LANDO, MICHAEL <ml6...@intl.att.com<mailto:ml6...@intl.att.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: Clarifying VNFSDK<->SDC David, Please clarify and guide us on the below integration of SDC and Market Place. Steps in current ONAP VF create: 1) Create License 2) Define VSP 3) Define VF ==> Import the VNF packages from Market place Market Place: 1) I find the below step is where we can download , query and search for VNF packages from Market place to SDC for onboarding. 2) All the information mentioned (Name, vendor, category, version is available ) along with CSAR. 3) Can somebody help to locate the code, where we can embed this functionality and how to set up development/debug environment for SDC at least for this functionality? 4) The functionality will be made optional by providing a check box “Import from Market Place”. User scenario: 1) User directly import VF -(CSAR file) (Step 3). 2) User click the check box (“Import from Market Place”) 3) SDC queries all or some VNF (based on search criteria) and display. 4) User can either select “Import or Download”. In both cases the package is downloaded along with required metadata field and passed to VF create API. [cid:image001.png@01D31B5E.6CDD8910] From: SHADMI, DAVID [mailto:ds2...@att.com] Sent: 18 August 2017 23:50 To: Christopher Donley (Chris) <christopher.don...@huawei.com<mailto:christopher.don...@huawei.com>> Cc: Murali p <mural...@huawei.com<mailto:mural...@huawei.com>>; Gaoweitao (Victor, MANO) <victor....@huawei.com<mailto:victor....@huawei.com>>; Vul, Alex <alex....@intel.com<mailto:alex....@intel.com>>; LU, TINGTING <tl2...@att.com<mailto:tl2...@att.com>>; LANDO, MICHAEL <ml6...@intl.att.com<mailto:ml6...@intl.att.com>> Subject: RE: Clarifying VNFSDK<->SO for R1 Hi Chris, We have this task in our backlog for R1. However, it is has lower priority compared to other tasks for SDC core development team and therefore I can’t guarantee it would get into R1. As I mentioned in one of the SDC calls, this task is open for anyone who would like to contribute, and we would provide the support. If someone from the VNFSDK team would like to volunteer and implement this functionality, it would be greatly appreciated. Thanks, David From: Christopher Donley (Chris) [mailto:christopher.don...@huawei.com] Sent: Friday, August 18, 2017 12:20 PM To: SHADMI, DAVID <ds2...@att.com<mailto:ds2...@att.com>> Cc: Murali p <mural...@huawei.com<mailto:mural...@huawei.com>>; Gaoweitao (Victor, MANO) <victor....@huawei.com<mailto:victor....@huawei.com>>; Vul, Alex <alex....@intel.com<mailto:alex....@intel.com>>; LU, TINGTING <tl2...@att.com<mailto:tl2...@att.com>> Subject: Clarifying VNFSDK<->SO for R1 Hi David, I wanted to check in on SDC/VNFSDK integration for R1. When we left things on Monday, I understood that VNF SDK would provide query/download APIs to SDC for TOSCA packaged VNFs, and SDC would implement the corresponding interfaces. I think this is your SDC-222 story. Would you confirm that you do plan to implement this in R1? There was some confusion on our team meeting today, where we weren’t sure whether you were treating this as required or optional. Thanks, Chris 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 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 onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
