Hi Michael, We are planning to support both the manual import (steps 1-3 with uploading a CSAR) and the integration with the Marketplace (steps 4-6). The manual import is mandatory for R1, while the integration with the Marketplace is a stretch goal we would like to meet with the help of VNFSDK team.
Tal is currently working on the detailed onboarding flows and will present them on Monday. Thanks, David From: Michael Brenner [mailto:[email protected]] Sent: Tuesday, August 22, 2017 3:56 PM To: SHADMI, DAVID <[email protected]> Cc: Murali p <[email protected]>; Christopher Donley (Chris) <[email protected]>; HALFON, TAL <[email protected]>; LANDO, MICHAEL <[email protected]>; LU, TINGTING <[email protected]>; [email protected] Subject: Re: [onap-discuss] Clarifying VNFSDK<->SDC David, Very useful. Can you please clarify if those steps apply only to R1 or R2 or both, and if they apply both to the VNF Packages that are on-boarded as TOSCA CSAR or also to those that are on-boarded as Heat templates? Thanks, Michael B On Tue, Aug 22, 2017 at 4:48 PM, SHADMI, DAVID <[email protected]<mailto:[email protected]>> wrote: 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:[email protected]<mailto:[email protected]>] Sent: Tuesday, August 22, 2017 5:42 AM To: SHADMI, DAVID <[email protected]<mailto:[email protected]>>; Christopher Donley (Chris) <[email protected]<mailto:[email protected]>> Cc: Gaoweitao (Victor, MANO) <[email protected]<mailto:[email protected]>>; Vul, Alex <[email protected]<mailto:[email protected]>>; LU, TINGTING <[email protected]<mailto:[email protected]>>; LANDO, MICHAEL <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> 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:[email protected]] From: SHADMI, DAVID [mailto:[email protected]] Sent: 18 August 2017 23:50 To: Christopher Donley (Chris) <[email protected]<mailto:[email protected]>> Cc: Murali p <[email protected]<mailto:[email protected]>>; Gaoweitao (Victor, MANO) <[email protected]<mailto:[email protected]>>; Vul, Alex <[email protected]<mailto:[email protected]>>; LU, TINGTING <[email protected]<mailto:[email protected]>>; LANDO, MICHAEL <[email protected]<mailto:[email protected]>> 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:[email protected]] Sent: Friday, August 18, 2017 12:20 PM To: SHADMI, DAVID <[email protected]<mailto:[email protected]>> Cc: Murali p <[email protected]<mailto:[email protected]>>; Gaoweitao (Victor, MANO) <[email protected]<mailto:[email protected]>>; Vul, Alex <[email protected]<mailto:[email protected]>>; LU, TINGTING <[email protected]<mailto:[email protected]>> 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 _______________________________________________ onap-discuss mailing list [email protected]<mailto:[email protected]> https://lists.onap.org/mailman/listinfo/onap-discuss<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=NqDQ5KrVy6GSDRdpY2D6nuU38dEAeZhjBibMtnmUI8c&s=Hcaasr7Z-vHs0ftbPBySP0pYNuUIKkynfHfqN5HEMJc&e=> -- Michael Brenner, Chief Architect NFV [https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/-27020792c3e94269b883d9a828be029f56c08986b2ab208a46143b169592c35a.png] ________________________________ M: +1-732-895-5772 http://getcloudify.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__getcloudify.org-3Futm-5Fsource-3Dsignaturesatori-26utm-5Fmedium-3Demail-26utm-5Fcampaign-3DCloudify-25204.0-2520Webinar&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=NqDQ5KrVy6GSDRdpY2D6nuU38dEAeZhjBibMtnmUI8c&s=HxOGKYlOr7zu3xUb-6yPy4pUXkVxKEZj0pQZlcU_7lQ&e=> @cloudifysource [https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/2fb5e7413e7dbeee3e88676333b65c05237ec13d3512e4a63ebc1b5f85bfb917.png]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_CloudifySource&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=NqDQ5KrVy6GSDRdpY2D6nuU38dEAeZhjBibMtnmUI8c&s=L22B5K8fWYFBLiOlI6ZpzrkN8A8p4YAtNnrRgDk1xi4&e=> [https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/16b91ab7a91bb3a298f2a322640bebb3754357f93e9f20ff50d2c94bb82b1814.png] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company-2Dbeta_17918192_&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=NqDQ5KrVy6GSDRdpY2D6nuU38dEAeZhjBibMtnmUI8c&s=tH_KK6rvHbMyN1_LPU9849tVjctfUuxoz57vzmUZ-5c&e=> [https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/6f7421bc5b9a93a0649735bbc8589b200c678bf08af9d7e0cebf1b3cffcdac94.png] <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cloudify-2Dcosmo&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=NqDQ5KrVy6GSDRdpY2D6nuU38dEAeZhjBibMtnmUI8c&s=dgUm2PX0AcCFnQZULcEu3oAKMGqjQK0tIk9X5syl-sU&e=> [https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/4be4d1377f4c1afe70a25e78926b6aad4e0a4fb1d45a7727e31d5a807eb3aae7.png] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.youtube.com_cloudifysource&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=NqDQ5KrVy6GSDRdpY2D6nuU38dEAeZhjBibMtnmUI8c&s=gysCB8133VLSb8zqR6f2U_9_Pc6l3_bPEwpGLx27bcU&e=> [https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/-218433c43f71db1180fd27884e3650b01b94c578c594b32c6f49c3daa3151366.png]<https://urldefense.proofpoint.com/v2/url?u=http-3A__getcloudify.org_webinars_the-2Dnew-2Dcloudify-2D4.html-3Futm-5Fsource-3Dsignaturesatori-26utm-5Fmedium-3Demail-26utm-5Fcampaign-3DCloudify-25204.0-2520Webinar&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=NqDQ5KrVy6GSDRdpY2D6nuU38dEAeZhjBibMtnmUI8c&s=PL06NurKHbRNOVSKWD0Iq1wa7-JfcjOap0cjW3HW_aI&e=>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
