Great suggestion! Shall we include it as part of the May hacfest?
Lingli From: onap-discuss-bounces at lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Anit Lohtia Sent: 2017?4?14? 20:45 To: denghui (L) <denghui12 at huawei.com>; FREEMAN, BRIAN D <bf1936 at att.com>; onap-discuss at lists.onap.org; onap-tsc at lists.onap.org; GILBERT, MAZIN E (mazin at research.att.com) <mazin at research.att.com> Subject: Re: [onap-discuss] More complex OPEN ECOMP demo Deng, Thanks for pulling this ?use-case? together. It will be an excellent demonstration of how all the components work together. Mazin, We can use this as part of the ONAP training that we were discussing on the TSC call yesterday (4/13). Thanks, Anit From: onap-discuss-bounces at lists.onap.org <mailto:onap-discuss-bounces at lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of denghui (L) Sent: Thursday, April 13, 2017 7:07 PM To: FREEMAN, BRIAN D <bf1936 at att.com <mailto:bf1936 at att.com> >; onap-discuss at lists.onap.org <mailto:onap-discuss at lists.onap.org> ; onap-tsc at lists.onap.org <mailto:onap-tsc at lists.onap.org> Subject: [onap-discuss] More complex OPEN ECOMP demo Hi Brian, After last week?s ONAP TSC meeting, we discussed extending the OpenECOMP demo to more fully demonstrate the functionality of the code you are contributing. You asked what we would find useful. After discussing it with our team, we would like to request that your kind help to extend the current use case to exercise all 8 OpenECOMP modules. It would be helpful if the demo would show both the creation of the overlay network and instantiation of the VNF ? ideally, across multiple data centers (although one is OK if multi-DC is too challenging), and using more than one VNF (see below). Specifically, we?d like to see how you: 1. Use ASDC to create all the TOSCA models and all the artifacts for the Use Case VNF 2. Demonstrate how the BPEL recipe was created and distributed 3. Show how the DG graph(s) for the Use Case is created and response for what 4. Create all the config filles and artifacts for Data Collection, Analytics and policy rules 5. Upload the DG, network topology files, Service topology files, YANG model, DG DCAE and policy files to ASDC 6. Distribute the all the above files and artifacts using ASDC to all the OpenECOMP components 7. Show how SDN-C creates/configures the network a. overlay (e.g., VXLAN, etc.) b. underlay 8. Show how the APP-C for the Use Case is created a. For more than one VNF 9. Show how the APP-C package is added to the Service catalog and how it I made available to the VID 10. Use VID to invoke the Use Case APP-C 11. Show how the Use Case VNF get orchestrated by doing the following: a. Update A&AI with the available resources b. Trigger MSO to execute the BPEL recipe c. Trigger SDN-C to create all the required network by executing the DG d. Update content in A&AI e. Create and Execute the HEAT template f. Verify that all the resources were inventoried successfully 12. Verify Data collection 13. Verify the analytics/policy 14. Demonstrate autoscaling and redundancy 15. Last but not least, execute the stop service command which should cleanly stop the VNF and reclaim all the resources including IP addresses and VMs and storage. If you can?t demonstrate all of these areas in the short-term, would you please clarify which ones you could? For example, if OpenECOMP can?t establish the underlay, would you please call that out, and we can set it up manually before we run the demo. Thanks again for your kind help Best regards, Deng Hui -----Original Message----- From: onap-discuss-bounces at lists.onap.org <mailto:onap-discuss-bounces at lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of FREEMAN, BRIAN D Sent: Friday, April 07, 2017 4:35 AM To: Alexis de Talhou?t; onap-discuss at lists.onap.org <mailto:onap-discuss at lists.onap.org> Subject: Re: [onap-discuss] Upgrade from ODL Beryllium to Boron Alexis, What would be the best mechanism to communicate this type of thing ? As we push our Feb and June 2017 code updates into ONAP repositories there will be more version changes of external open source ? Would a notice on this list be enough or should there be another tool/process used ? We are open to what would be better for the community ? Brian -----Original Message----- From: <mailto:onap-discuss-bounces at lists.onap.org> onap-discuss-bounces at lists.onap.org [ <mailto:onap-discuss-bounces at lists.onap.org> mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhou?t Sent: Thursday, April 06, 2017 3:49 PM To: <mailto:onap-discuss at lists.onap.org> onap-discuss at lists.onap.org Subject: [onap-discuss] Upgrade from ODL Beryllium to Boron Hello guys, I?ve seen that recently you?ve upgraded ODL?s version. APPC <https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Dappc.git-3Ba-3Dcommit-3Bh-3Da41533fb0a79e7399f7bf0ba53a1211c67e50d04&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=yqEiYEqq3lumI3bdXWz4Rxa5GynG3EX_2qUzZvFrOvo&e> https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Dappc.git-3Ba-3Dcommit-3Bh-3Da41533fb0a79e7399f7bf0ba53a1211c67e50d04&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=yqEiYEqq3lumI3bdXWz4Rxa5GynG3EX_2qUzZvFrOvo&e= <https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Dappc.git-3Ba-3Dcommit-3Bh-3Dda976a9c10cca4249e97f6629eb17cd52a7e4955&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=0xrdhJsf90kPIdSWhe-l0tULo2Ve3nyPyNnuVInmDRM&e> https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Dappc.git-3Ba-3Dcommit-3Bh-3Dda976a9c10cca4249e97f6629eb17cd52a7e4955&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=0xrdhJsf90kPIdSWhe-l0tULo2Ve3nyPyNnuVInmDRM&e= SDNC <https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_2905_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=vxs3n-9zqJjaSFCFICdqvEm505UT6YK3cOTbvS0bIvY&e> https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_2905_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=vxs3n-9zqJjaSFCFICdqvEm505UT6YK3cOTbvS0bIvY&e= <https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_2907_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=4p__SxAqsG_N6wlgXGfZdFX-A-DyYyBMymL6SqHJeXY&e> https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_2907_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=4p__SxAqsG_N6wlgXGfZdFX-A-DyYyBMymL6SqHJeXY&e= (plugins) <https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_2901_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=3588Z0vornh0qWGD9HcNrNdKafzbni2w6hTz6VAoyLM&e> https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_2901_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=3588Z0vornh0qWGD9HcNrNdKafzbni2w6hTz6VAoyLM&e= (core) ... This is great. But please, next time, do advertise change like this, so other don?t spend cycles looking into this? Also, if possible, write accurate commit message, so one can track changes from the git log. Regarding the commit message, here are awesome guideline: <https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opendaylight.org_view_BestPractices_Commit-5FMessages&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=-io3OaDPAIuXe_BguMJ_zalYEuzBS52c-BgL8i_q0MA&e> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opendaylight.org_view_BestPractices_Commit-5FMessages&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=-io3OaDPAIuXe_BguMJ_zalYEuzBS52c-BgL8i_q0MA&e= Thanks, Alexis _______________________________________________ onap-discuss mailing list <mailto:onap-discuss at lists.onap.org> onap-discuss at lists.onap.org <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=nzNqEfODOX4QdGrDp8w55SCZExDDcCFPTULEsVVF1fk&e> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=nzNqEfODOX4QdGrDp8w55SCZExDDcCFPTULEsVVF1fk&e= _______________________________________________ onap-discuss mailing list <mailto:onap-discuss at lists.onap.org> onap-discuss at lists.onap.org <https://lists.onap.org/mailman/listinfo/onap-discuss> https://lists.onap.org/mailman/listinfo/onap-discuss ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170416/4c8d0b73/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 42833 bytes Desc: not available URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170416/4c8d0b73/attachment-0001.png>
