Re: [onap-tsc] Definition of Subcommittee Membership
Agreed, Steve. Perhaps, that makes ONAP the most active and growing community. One of my customers categorically mentioned this as the reason for which, they decided to place their bet on ONAP vis a’ vis ETSI OSM (they didn’t get required support from the community out there). thanks & regards, Dhananjay Pavgi +91 98220 22264 From: ONAP-TSC@lists.onap.org On Behalf Of Stephen Terrill Sent: Monday, August 27, 2018 12:51 PM To: ONAP-TSC@lists.onap.org Subject: Re: [onap-tsc] Definition of Subcommittee Membership Hi Kenny, I’ve struggled with this a little from the security sub-committee and decided not to focus on it, the reason comes down to what does it mean to be a member. - We have people actively participating (which is great) – and that is important irrespective of whether they are identified as members. I do hope that all active participants can identify themselves as members. - We have people listening in to the calls that may be normally quite. I do not, however know, what they are doing behind the scenes to connect the dots – and I wouldn’t want to project any view that they are not welcome join, or participate, or listen whether or not they identify themselves as a member or not. - We can have people that are formally identified as members, that don’t do the above. We could go down the path of “active membership”, however and have criteria like meeting attendance, wiki updates etc; but do we clearly gain when anyway at the end of the day the sub-committeess are advisory and work on rough consensus. BR, Steve From: ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> mailto:ONAP-TSC@lists.onap.org>> On Behalf Of Alla Goldner Sent: Monday, August 27, 2018 8:48 AM To: ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> Subject: Re: [onap-tsc] Definition of Subcommittee Membership Hi Kenny, As you mention below: As defined in 4.4.1.3Subcommittee Chair / Vice Chair Elections<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.4.1.3SubcommitteeChair/ViceChairElections> : The Chair or Vice-Chair will be elected by members of the subcommittee as of the date the nomination process starts for the election. Section 4.4.1.4Subcommittee Voter Eligibility<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.4.1.4SubcommitteeVoterEligibility> the criteria only defines: Voting for a Chair or Vice-Chair is not limited to ONAP member companies. However only 1 Subcommittee member from each company, or group of related companies may vote in the election. Therefore, at least my reading is that the problem you describe below may exist only if at least one of assigned voting members (max 1 per company or group of related companies) is not fully identified as a subcommittee member, as only they should be getting a ballot. Is it the case? Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image001.png@01D43E07.6ECF7590] From: ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> [mailto:ONAP-TSC@lists.onap.org] On Behalf Of Kenny Paul Sent: Sunday, August 26, 2018 11:37 PM To: onap-tsc mailto:ONAP-TSC@lists.onap.org>> Subject: [onap-tsc] Definition of Subcommittee Membership TSC Members, I have run into an issue I have a concern with the Subcommittee elections. I spent all day Saturday working this and I was going to make the call myself but after sleeping on it I decided that this really requires a decision from the TSC, not from the PM. I am going to hold off on balloting until I have received clear guidance. The primary membership criteria for most Subcommittees were established with an overly broad, “If you want to be a member, just add your name to the wiki” model. The result of this is basically unmanageable and has introduced a grey area that calls into question both the definition and validity of membership. In the crush to get ONAP off the ground this resulted in a flood of people adding themselves and then failing to participate. The membership lists have never been curated as far as I am aware, so there are a lot of "members" that have never been active. I have not yet looked into Security, Open Lab or University yet and Control-Loop isn't due for another couple months. However, for the "big three" here is the situation… Architecture Subcommittee: 108 members listed, 70 are actually subscribed to the Onap-arc mailing list Use case Subcommittee: 98 members listed, 49 are actually subscribed to the Onap-usecasesub mailing list Modeling Subcommittee: 84 members listed. It does not have its own mailing list and instead uses onap-discuss. Out of the 35 company representatives (as per section 4.4.1.4 of the Community Document), 9 of them are not subscribed to the mailing list. A few of these deltas can be attri
Re: [onap-tsc] [onap-discuss] [modeling] new proposal to change TSC report consensus slide wording
+1 thanks & regards, Dhananjay Pavgi +91 98220 22264 From: ONAP-TSC@lists.onap.org On Behalf Of Alex Vul Sent: Thursday, July 19, 2018 6:11 PM To: Andrei Kojukhov ; Andy Mayer ; onap-disc...@lists.onap.org; denghu...@huawei.com; ONAP-TSC@lists.onap.org Cc: Lingli Deng ; Mark Gibson ; 'eric.deb...@orange.com' ; WECHSLER, CHESLA C ; 'Mehmet Toy' ; 'Davis, Nigel' ; 'Ranganathan, Raghu' ; 'Priya TG' ; KATZMAN, ANATOLY ; LANDO, MICHAEL ; HALLAHAN, RYAN Subject: Re: [onap-tsc] [onap-discuss] [modeling] new proposal to change TSC report consensus slide wording +1 From: Andrei Kojukhov [mailto:andrei.kojuk...@amdocs.com] Sent: Thursday, July 19, 2018 05:06 To: Andy Mayer mailto:am8...@att.com>>; onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; denghu...@huawei.com<mailto:denghu...@huawei.com>; ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> Cc: Lingli Deng mailto:denglin...@chinamobile.com>>; Mark Gibson mailto:mar...@amdocs.com>>; 'eric.deb...@orange.com' mailto:eric.deb...@orange.com>>; WECHSLER, CHESLA C mailto:cw1...@att.com>>; 'Mehmet Toy' mailto:mehmet@verizon.com>>; Vul, Alex mailto:alex@intel.com>>; 'Davis, Nigel' mailto:nda...@ciena.com>>; 'Ranganathan, Raghu' mailto:rra...@ciena.com>>; 'Priya TG' mailto:priy...@netcracker.com>>; KATZMAN, ANATOLY mailto:ak4...@intl.att.com>>; LANDO, MICHAEL mailto:ml6...@intl.att.com>>; HALLAHAN, RYAN mailto:rh1...@att.com>> Subject: RE: [onap-tsc] [onap-discuss] [modeling] new proposal to change TSC report consensus slide wording +1 From: ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> mailto:ONAP-TSC@lists.onap.org>> On Behalf Of Andy Mayer Sent: Thursday, July 19, 2018 2:49 PM To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; denghu...@huawei.com<mailto:denghu...@huawei.com>; ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> Cc: Andrei Kojukhov mailto:andrei.kojuk...@amdocs.com>>; Lingli Deng mailto:denglin...@chinamobile.com>>; Mark Gibson mailto:mar...@amdocs.com>>; 'eric.deb...@orange.com' mailto:eric.deb...@orange.com>>; WECHSLER, CHESLA C mailto:cw1...@att.com>>; 'Mehmet Toy' mailto:mehmet@verizon.com>>; 'Alex Vul' mailto:alex@intel.com>>; 'Davis, Nigel' mailto:nda...@ciena.com>>; 'Ranganathan, Raghu' mailto:rra...@ciena.com>>; 'Priya TG' mailto:priy...@netcracker.com>>; KATZMAN, ANATOLY mailto:ak4...@intl.att.com>>; LANDO, MICHAEL mailto:ml6...@intl.att.com>>; HALLAHAN, RYAN mailto:rh1...@att.com>> Subject: Re: [onap-tsc] [onap-discuss] [modeling] new proposal to change TSC report consensus slide wording Modeling Team, I am concerned that the current wording of the Modeling Sub-committee meeting report is not extremely clear and may be confusing. Please +1 on this [Modeling] email thread if you support the more detailed description of the agreement. It would be good to have a clear statement to present to the TSC. If you would, please consider updating the wording to be more clear: • Agreement that the VNF Descriptor model for On-Boarding and the Internal ONAP models are distinct. • Acknowledgement that there are two Internal ONAP VNF Descriptor Data Models that will evolve where possible in a coordinated way in support of the Casablanca Use Cases § ONAP R2+ Design-Time Resource DM clean version enhancement for VoLTE, CCVPN, vCPEstretch goal § ONAP SDC TOSCA AID enhancement for vCPE • During the Casablanca cycle, begin a collaborative effort for creating a combined ONAP Internal VNF Descriptor Data Model representation for R4 and beyond (including continued alignment with the VNF Descriptor Information Model) • Engage impacted components for understanding data model impacts, and what is possible in Dublin and beyond (SDC, SO, VFC, A&AI, OOF, CLAMP) • The decision to support a transition to SOL001 as an ONAP on-boarding option is being deferred. Best Regards, Andy Andy Mayer, Ph.D. | PMTS, D2.0 Integration | AT&T Labs | Phone: +1 (732) 420-9945 | am8...@att.com<mailto:am8...@att.com> From: Lingli Deng [mailto:denglin...@chinamobile.com] Sent: Thursday, July 19, 2018 5:39 AM To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; denghu...@huawei.com<mailto:denghu...@huawei.com>; ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> Cc: MAYER, ANDREW J mailto:am8...@att.com>>; 'Andrei Kojukhov' mailto:andrei.kojuk...@amdocs.com>> Subject: RE: [onap-discuss] [modeling] new proposal to change TSC report consensus
Re: [onap-tsc] [Onap-release] [ptl][jira] Propose alignment on 1 Jira workflow
+1 thanks & regards, Dhananjay Pavgi +91 98220 22264 From: ONAP-TSC@lists.onap.org On Behalf Of Shankar Narayanan Sent: Thursday, July 12, 2018 10:26 PM To: Pamela Dragosh Cc: MAHER, RANDA ; onap-rele...@lists.onap.org; onap-tsc ; onap-disc...@lists.onap.org Subject: Re: [onap-tsc] [Onap-release] [ptl][jira] Propose alignment on 1 Jira workflow +1 Thanks, Shankar. On Thu, Jul 12, 2018 at 12:43 PM Pamela Dragosh mailto:pdrag...@research.att.com>> wrote: +1 Pam Dragosh ONAP Policy PTL From: mailto:onap-rele...@lists.onap.org>> on behalf of "MAHER, RANDA" mailto:rx1...@att.com>> Date: Monday, July 9, 2018 at 9:46 AM To: "onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>" mailto:onap-rele...@lists.onap.org>> Cc: onap-tsc mailto:onap-tsc@lists.onap.org>>, "onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" mailto:onap-disc...@lists.onap.org>> Subject: Re: [Onap-release] [ptl][jira] Propose alignment on 1 Jira workflow ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hello everyone, This topic was discussed on today’s PTL call. I am resending email so you don’t have to dig for it. Please provide your feedback if you’re in agreement or if you have any questions. The goal is to align on a single workflow in ONAP. Also, another topic raised during PTL call, but not part of the attached proposal, but I wanted to note it here: • We should align on the set of Jira issue types that will be used across the projects to ensure issues don’t fall through the cracks. • Today, most projects use: Epics, Stories (& sub-tasks available within story), Tasks, Bugs • There are some projects that also use New Feature • What is the set we want to support for ONAP projects? Thanks, Randa From: onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org> [mailto:onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>] On Behalf Of MAHER, RANDA Sent: Monday, June 25, 2018 9:30 PM To: onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org> Cc: onap-tsc mailto:onap-tsc@lists.onap.org>>; onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org> Subject: [Onap-release] [ptl][jira] Propose alignment on 1 Jira workflow ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Greetings PTLs, One of the items in the Beijing Retrospective was confusion over the two separate Jira workflows in play today. I would like to submit the following for consideration to align on ONE Jira workflow. This is low hanging fruit and an easy enough change to implement to progress on addressing one of the concerns raised during Lesson’s Learned discussions. I believe the attached workflow is flexible enough to handle the uniqueness of ONAP as well as not introduce overhead for teams. Please review attached slides and provide your +1 if you agree to the proposal. Thanks, Randa APPC PTL 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#3373): https://lists.onap.org/g/ONAP-TSC/message/3373 Mute This Topic: https://lists.onap.org/mt/23289820/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement
Concur with views below from Shankar. Why confuse by changing it to SDN-C when we know it's functionality quite "Radio" and wireless domain specific. thanks & regards, Dhananjay Pavgi +91 98220 22264 From: onap-tsc-boun...@lists.onap.org On Behalf Of SHANKARANARAYANAN, N K (N K) Sent: Thursday, May 17, 2018 8:39 AM To: Alla Goldner ; onap-usecase...@lists.onap.org Cc: onap-disc...@lists.onap.org; onap-tsc Subject: Re: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement Alla, I don't understand the decision to change the SDN-R term after the several discussions in the 5G and SDN-R groups using this term to describe the single ONAP OA&M controller persona (derived from CC-SDK) for mobility and wireless PNF/VNFs. The reasons were articulated in the discussions. There has been momentum in using the SDN-R term, and changing it to SDN-C now causes confusion. Regards, Shankar From: onap-usecasesub-boun...@lists.onap.org<mailto:onap-usecasesub-boun...@lists.onap.org> [onap-usecasesub-boun...@lists.onap.org] on behalf of Alla Goldner [alla.gold...@amdocs.com] Sent: Tuesday, May 15, 2018 4:21 AM To: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org> Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc Subject: [Onap-usecasesub] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement Hi all, Here is the summary of our yesterday's meeting. Thanks to all meeting participants! 1. We have fully endorsed the following use cases/functional requirements: a. OSAM b. Auto Scaling out c. Consistent representation and identification of a cloud region in ONAP d. Edge Automation through ONAP 2. 5G group of functional requirements is endorsed, with the following exceptions: a. Terminology of SDN-R will be replaced by SDN-C, while it will be clarified what is the functionality of the SDN-C sub-module (used to be called SDN-R) to cover necessary enhancements b. SON and slice optimization topics will be re-discussed till next Monday's Usecase subcommittee meeting by all interested parties. There are concerns expressed by Cisco (Vladimir Yanover) which require additional discussions. We will monitor their progress and see if consensus is achieved or this issue needs to be raised and decided by the TSC 3. Casablanca's HPA and Change Management authors - please upload your proposals under https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+endorsement<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Casablanca-2Buse-2Bcases-2Bproposals-2Bfor-2Bendorsement&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=3F6B_OfdEFaZplwZX72F9ItZySDTzOU-cPey8nzXnHA&m=0xTbqUdLR-851l7UAd83zDbYq3UV0fmlrYmnbjQLwow&s=f2cGhvhTgxPybLCBOP_WT5ljK9FymPHnXzRnM6kRavI&e=>. We will discuss them next Monday 4. Cross Domain and Cross Layer VPN Service was presented for the first time yesterday. Some comments were received. Team will update according to the comments received and we will continue our discussion next Monday as well. Also, the team has asked for additional volunteering companies to participate in this development (please approach Lingli and Lin in case of interest) Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image001.png@01D3EDC2.9180EBE0] 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=3F6B_OfdEFaZplwZX72F9ItZySDTzOU-cPey8nzXnHA&m=0xTbqUdLR-851l7UAd83zDbYq3UV0fmlrYmnbjQLwow&s=XxYSFDToxAXoSTjMATJ9oiE7C1VyCwK7AvEXwLLE-lY&e=> 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] TSC Members Composition Survey RFC - Respond by 18:00 Pacific time, May 7
Concur with Rajesh’s views over here. thanks & regards, Dhananjay Pavgi +91 98220 22264 From: onap-tsc-boun...@lists.onap.org On Behalf Of Gadiyar, Rajesh Sent: Friday, May 4, 2018 10:08 PM To: Kenny Paul Cc: onap-tsc Subject: Re: [onap-tsc] TSC Members Composition Survey RFC - Respond by 18:00 Pacific time, May 7 Hi Kenny: Never has a negative connotation. I am simply proposing an option where all LFN platinum members have a TSC membership (supplemented with a few exta seats for non platinum significant contributors). I am supportive of putting enough guardrails for the qualifications to be a TSC member and the contribution expectations. /R From: Kenny Paul mailto:kp...@linuxfoundation.org>> Date: Friday, May 4, 2018 at 8:10 AM To: Rajesh Gadiyar mailto:rajesh.gadi...@intel.com>> Cc: onap-tsc mailto:onap-tsc@lists.onap.org>> Subject: Re: [onap-tsc] TSC Members Composition Survey RFC - Respond by 18:00 Pacific time, May 7 Hi Rajesh, As this is a "when" question the implication of your suggested #4 is "Never". Am I understanding that correctly? Thanks! -kenny From: "Gadiyar, Rajesh" mailto:rajesh.gadi...@intel.com>> Date: Thursday, May 3, 2018 at 8:34 PM 1. When should the ONAP TSC move from “Startup” to “Steady” state operations at which point the TSC should be populated, not by Platinum Member designates, but instead by some other means, for which the TSC is responsible for defining? 1. As soon as the new method for populating the TSC is defined 2. After the Beijing Release 3. After the Casablanca Release 4. Keep the current TSC composition with Platinum members automatically get a TSC seat. 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
[onap-tsc] ONAP-University : Seek Help.
Dear All, Reaching out to you once again. We are driving ONAP experience sharing webinars through ONAP-University. We did first webinar about 10 days back. Prem P from this subcommittee team has been driving this effort and reaching out to PTLs individually as well as to the community. So far, we have commitment from Orange team for below webinar topics. Amdocs team has stepped up to help and we shall discuss on coming Monday ONAP-University weekly call on which topics Amdocs can possibly take up and contribute. Would like to appeal again to the wider community to help us broad base ONAP knowledge and learning to wider audience. Sl No Date Topic Topic Details Speaker Speaker Details Remarks 1 14 May ONAP Orange Open Lab How to use it and the toolings developed Morgan Richomme Senior network architect, Orange 2 4 June Connectivy service on-demand connectivy service PoC Abdelmuhaimen Seaudi Head of B2B Domain at Orange Labs Egypt thanks & regards, Dhananjay Pavgi +91 98220 22264 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] TSC MEMBERS Approval/Acknowledgment Needed- Requesting Nexus3 downtime
+1 thanks & regards, Dhananjay Pavgi +91 98220 22264 From: onap-tsc-boun...@lists.onap.org On Behalf Of Yunxia Chen Sent: Wednesday, May 2, 2018 6:42 AM To: Kenny Paul ; onap-tsc Cc: Jeremy Phelps ; Anil Belur Subject: Re: [onap-tsc] TSC MEMBERS Approval/Acknowledgment Needed- Requesting Nexus3 downtime (Nexus3 issue highly impacted the current ONAP pair wise testing and final integration testing: we need it get addressed asap. Please approve it). Regards, Helen Chen From: mailto:onap-tsc-boun...@lists.onap.org>> on behalf of Kenny Paul mailto:kp...@linuxfoundation.org>> Date: Tuesday, May 1, 2018 at 4:46 PM To: onap-tsc mailto:onap-tsc@lists.onap.org>> Cc: Anil Belur mailto:abe...@linuxfoundation.org>>, Jeremy Phelps mailto:jphe...@linuxfoundation.org>> Subject: [onap-tsc] TSC MEMBERS Approval/Acknowledgment Needed- Requesting Nexus3 downtime (bcc'd to onap-release to avoid cross posting) When: Requesting May 2nd, 6:00 am to 7:00 am Pacific, Alternative: May 3, 6:00 am to 7:00 am Pacific What: Increasing ONAP's Nexus3 server's heap size to 6 gig and enable additional logging Why: Based upon a meeting today between the Community and LFIT - Part of ongoing work to address performance issues pulling docker images Impact: Jenkins and Nexus3 will be unavailable during this time Risk: Low Background: Docker image pulls are subject to hanging in mid-stream for minutes at a time. A recent network fix on the part of our service provider has addressed bandwidth issues which were contributing to this behavior, however with one bottleneck removed a new issue has been identified. It is believed that the jobs are pausing whenever normal garbage collection tasks are triggered. The most likely cause of this is the result of the heap size being set to default values which is not taking full advantage of the memory available. This change will set the heap size to match what is currently in place for ONAP's Nexus2 server. During this down time logging will also be enabled to track additional system information in the event that the planned fix does not correct the problem. Alternative: Leave system as-is until after the release Best Regards, -kenny Kenny Paul, Technical Program Manager, The Linux Foundation kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>, 510.766.5945 San Francisco Bay Area, Pacific Time Zone 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] [onap-discuss] Action Plan towards Casablanca => ONAP introduction course
Thanks, Eric. Yes, this is foundational course from Linux Foundation. In addition, we have devised advanced ONAP training courses. Other than this formative educational thread; we discussed about webinars to broad base ONAP knowledge. Have also written to ONAP-TSC email alias. Seek help and ideas. PS. - Plan to announce first webinar of the series on Wednesday, 18th April. Please send your list of topic/s, speakers and proposed date. Suggest, we run these webinars on Wednesday. Basis # of topics; we can decide frequency. thanks & regards, Dhananjay Pavgi +91 98220 22264 From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of eric.deb...@orange.com Sent: Wednesday, April 4, 2018 5:49 PM To: onap-tsc@lists.onap.org Subject: [onap-tsc] [onap-discuss] Action Plan towards Casablanca => ONAP introduction course Hello A very good EdX course on ONAP introduction "Introduction to ONAP: Complete Network Automation" https://courses.edx.org/courses/course-v1:LinuxFoundationX+LFS163x+1T2018/course/ After reminding some basic NFV concepts, the course explains ONAP, the architecture, the main components and the use-case overview. A very good introduction for beginners with a large number of cool quizzes. A first answer for the topic "3. Broader learning and education of ONAP." Best Regards Eric _ 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. 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
[onap-tsc] ONAP-University : ONAP Webinars for experience/knowledge sharing.
Dear All, As discussed in TSC meeting last week at ONS; ONAP-University sub-committee will lead the effort to share ONAP experience/learnings. I will be in transit this Thursday and hence will have delegate attend TSC. However, would like to start the process of arriving at calendar/schedule. ONAP University subcommittee weekly call is scheduled Monday. Will announce revised timing through WiKi page of ONAP University. All those interested are requested to join this call on Monday, 9th April 2018 so that we can publish calendar/schedule in TSC meeting scheduled for Thursday, 12th April 2018. Look forward to work with you all. thanks & regards, Dhananjay Pavgi +91 98220 22264 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] Committer Promotion Request for [appc]
+1 Thanks & regards, Dhananjay Pavgi Tech Mahindra Ltd +91 98220 22264 -- Original message-- From: MAHER, RANDA Date: Fri, 12 Jan 2018 05:29 To: onap-tsc@lists.onap.org; Cc: onap-disc...@lists.onap.org; Subject:[onap-tsc] Committer Promotion Request for [appc] Dear TSC, Please consider request below for Committer Promotion for APPC project. https://wiki.onap.org/pages/viewpage.action?pageId=22251669 One of our existing committers has indicated that he will step down from Committer to Contributor role. Existing Committers have all voted +1 on Taka Cho promotion to Committer. Thanks, Randa APPC PTL 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC
Support Option 1; as TSC Chair for a particular stream has broader 360 view of the program including roadmap, priorities etc. thanks & regards, Dhananjay Pavgi +91 98220 22264 From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of HU, BIN Sent: Thursday, January 11, 2018 10:24 PM To: Phil Robb ; onap-tsc Subject: Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC Just FYI: - OPNFV TSC voted on Tuesday (Jan 9) to have TSC Chair to represent OPNFV in TAC - fd.io voted the same today to have TSC Chair represent fd.io in TAC, if I am not mistaken. Option 1 is used by both of our sister communities under the same LFN. Just an FYI. Thanks Bin From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil Robb Sent: Thursday, January 11, 2018 7:08 AM To: onap-tsc mailto:onap-tsc@lists.onap.org>> Subject: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC Hello ONAP TSC Members: Now that ONAP is a part of the Linux Foundation Networking (LFN) Directed Fund, we need to decide how we are going to populate our ONAP Representative in the LFN Technical Advisory Council (TAC). As a reminder, the Scope of the responsibilities of the TAC are: = •Scope of responsibility •Recommend acceptance or removal of projects under the Umbrella to be approved by the Governing Board •Focus on activities that drive collaboration and integration across projects (e.g. collaborative development, testing, etc) •Elected TAC Chair provides guidance to Governing Board on investment needs of the project communities = Some of the options for us to populate our representative include: 1) Just have the TSC Chair represent ONAP in the TAC 2) Have the TSC vote for some TSC member to represent ONAP in the TAC 3) Have the Committers vote for some Committer-At-Large to represent ONAP in the TAC ... etc. I will be setting up the first TAC meeting to occur somewhere in the last third of January and it would be good for the ONAP community to have representation from the start. I personally lean toward option #2 because a) it does not by default put more burden on the TSC Chair unless they choose to run for the position, and b) having the representative come from the TSC ensures that our representative is up to speed on all TSC conversations that have occurred. However, I certainly believe the other options are viable as well. Given our tight schedule during TSC meetings in the coming weeks, it would be nice if we can come to a decision on this topic via email. Please respond with your thoughts and opinions and based on the feedback received, I'll try to put together a vote on this topic in about a week. Thanks, Phil. -- Phil Robb VP Operations - Networking & Orchestration, The Linux Foundation (O) 970-229-5949 (M) 970-420-4292 Skype: Phil.Robb 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] ona-user mailing list?
Good idea, Kanagaraj. +1. thanks & regards, Dhananjay Pavgi +91 98220 22264 From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Kanagaraj Manickam Sent: Wednesday, November 22, 2017 1:48 PM To: onap-tsc@lists.onap.org Subject: [onap-tsc] ona-user mailing list? Dear TSC team, When user starts to use the ONAP Amsterdam version and they would need an forum to discuss among the user communities to discuss about ONAP usage related issues. So, shall we create new mailing list ‘onap-user’, to address it? This would be similar to onap-discuss, used by developers community. Thank you. Regards Kanagaraj M *** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！** *** This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! *** 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] ONAP TSC measures of success
Dear All, Couple of other measures that could be considered: 1. JUNit test coverage across LOC : Indicator of Code Quality (i.e. being unit tested) 2. Number of VNFs successfully on boarded and tested : Indicator of VNF adoption rate for ONAP 3. Number of Integration Test cases covered : Indicator of platform maturity for E-2-E use. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of GILBERT, MAZIN E (MAZIN E) Sent: Wednesday, September 13, 2017 10:26 PM To: onap-disc...@lists.onap.org; onap-tsc@lists.onap.org P Subject: [onap-tsc] ONAP TSC measures of success Dear ONAP Community, I want to start an email dialog which we will follow up in our Paris meeting on technical measures of success of the ONAP platform. What measures we should track and make publicly visible in PR events? I know LOC has been used already. This seems like one of 2-3 other measures we should be tracking. Those measures should be agnostic to any particular release and publicly recognized. Please share your thoughts and ideas. thanks! Mazin 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] Discussion on Policy hysteresis.
Hi Aayush, Quite an interesting question. View as below: Gating criteria evaluation placement in Architecture would be dependent on 1. Whether Policy is being applied at E-2-E service (e.g. vVoLTE, vVoWiFi) or 2. Service component (single VNF or VNF-C) level e.g. vIMS, vEPC or 3. Network component level e.g. SDN or 4. Cloud/Infrastructure level e.g. CPU, Memory etc. If it's 1. Above then it would make sense to have Centralized "Gating criteria". In all other cases, it would be de-centralized at that respective component level. Wonder if CLAMP project team could shed some more light on this. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of aayush.bhatna...@ril.com Sent: Tuesday, September 12, 2017 10:01 AM To: onap-tsc@lists.onap.org; onap-disc...@lists.onap.org Subject: Re: [onap-tsc] Discussion on Policy hysteresis. Not sure why it the mail below did not reflect on the onap-discuss mailing list. Re-posting here. Regards Aayush On 9 September 2017 at 09:04:14 IST, Aayush Bhatnagar mailto:aayush.bhatna...@ril.com>> wrote: There is one architectural doubt on Policy Enforcement, which is explained below - When we enforce a policy, we may have to define an associated hysteresis along with it. Consider the case for "auto scaling policies" for a VNF or even its VNF Component (VNF-C). The auto scaling policy may be based on CPU consumption thresholds, for example - A) Auto scale the VNF if the CPU consumption spikes and exceeds 70%, three times in any given hour (busy hour). B) Auto scale the VNF, if the CPU consumption exceeds 70% three times in a given 24 hour period (1 day). , and so on. Hence, unless the above hysteresis evaluates to "true", the policy for auto-scaling the VNF should not be enforced. In the current architecture, even though the policy rules are distributed to different ONAP sub-systems for enforcement - how do we plan to handle the "gating criteria" (hysteresis) for policies. Is it expected for individual ONAP subsystems to implement the gating criteria evaluation repeatedly for such cases? There is an element of data mining and time-series analytics involved here to evaluate the gating criteria. Or will this be centralised (Analytics?) and all ONAP subsystems are required to "consult" the central gating criteria before actually enforcing policies which need hysteresis? Clarifications will be helpful. Regards Aayush "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential and may be privileged. If you are not the intended recipient, you are hereby notified that any review, re-transmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment." 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] ONAP University subcommittee : proposed charter.
Thanks, Lingli for prompt response, appreciate it. Very valid and the most important point considering R1 timelines. Will have to chart out working plan for R1 with PTLs. Given paucity of time for R1; suggest we cover following topics at the minimum: 1. Architecture Enhancements from R1 2. New projects that fit MVP criteria for R1 3. Use Cases Suggested Format could be : White paper and webinar for 1. Above, Detailed project component description (sort of deep-dive component architecture/functional design) document for 2. Above and canned videos, README for 3. Above. We can package this; and work with Marketing steering committee to arrive at email teasers/campaigns/webinars around release date of R1. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 From: Lingli Deng [mailto:denglin...@chinamobile.com] Sent: Monday, September 11, 2017 1:09 PM To: Dhananjay Pavgi ; 'onap-tsc' Subject: RE: [onap-tsc] ONAP University subcommittee : proposed charter. Hi Dhanajay, Thanks for the well-prepared proposal. I have a quick question: As the document states, that the subcommittee and current proposals are not bounded to R1, I am wondering what is the working plan for R1. So far as I know, LF has contacted with PTLs preparing for similar material for R1 as part of M4. Thanks and Regards, Lingli From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Dhananjay Pavgi Sent: 2017年9月11日 15:10 To: onap-tsc mailto:onap-tsc@lists.onap.org>> Subject: [onap-tsc] ONAP University subcommittee : proposed charter. Dear All, As discussed in the TSC meeting last week; please find attached herewith proposed charter for ONAP University Subcommittee. Would like to seek your views. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> 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. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] Vote on Date & Location of Next ONAP Developer Face To Face
+1 thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of GILBERT, MAZIN E (MAZIN E) Sent: Thursday, August 03, 2017 10:18 AM To: Phil Robb Cc: onap-tsc Subject: Re: [onap-tsc] Vote on Date & Location of Next ONAP Developer Face To Face +1 Sent through AT&T's fastest network On Aug 3, 2017, at 12:49 AM, Phil Robb mailto:pr...@linuxfoundation.org>> wrote: Hello ONAP TSC Members: As was mentioned at the last TSC meeting, Nokia and Orange have offered to host the next ONAP Developer Face to Face meeting the week of September 25th, 2017 at the Nokia Paris-Saclay facility approximately 25 Kilometers south west of the Paris Orly airport. We will have access to an auditorium that holds 200 people along with several conference/break-out rooms. We are still finalizing the specific days of the event, but I would like to have the TSC approve this time/week, and location so that attendees who need visas can begin the process of getting them. Therefore, please provide your vote via email to the following resolution: Shall the TSC approve the next ONAP Developer Face to Face meeting to be held the week of September 25th, at the Nokia facility located in Paris-Saclay, France? +1, 0, -1 TSC Members, please provide your vote at your earliest opportunity. If we reach an affirmative vote on this prior to the TSC meeting tomorrow, we'll simply make that announcement during the meeting. If we do not reach an affirmative vote, we will discuss this topic and vote on it in the meeting tomorrow. Thanks in advance for your response. Best, Phil. -- Phil Robb Executive Director, OpenDaylight Project VP Operations - Networking & Orchestration, The Linux Foundation (O) 970-229-5949 (M) 970-420-4292 Skype: Phil.Robb ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=TZM9w1qxATWfADqCsoci5waP3EmT6jwXpm2l_lXNA-U&s=Uzo2tpo9-tLUljTDxnTLcnyLpB9Fl7IDVMpDrX7w9OI&e= 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP
+1 on Upstream first. Some views on ONAP’s adoption in production environments: 1. Regular Code Quality Analysis to be done. 2. Arrive at #TECHDEBT and have it tracked through Jira backlog 3. Every release plan MUST cover as to what % of #TECHDEBT would be addressed in that release. 4. #TECHDEBT to be tracked for each component and entire platform as such (imbibe Scrum of Scrum discipline) Afraid that we are too focused on functional aspects at the moment that are tracked through Jira user stories and Sprint plans. However, we are grossly ignoring #TECHDEBT. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Ed Warnicke Sent: Wednesday, August 02, 2017 10:42 PM To: Sauvageau, David Cc: onap-tsc@lists.onap.org Subject: Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP +1 Upstream first is crucial. Happy to share sane strategies I've seen work in the past if folks are interested. Ed On Wed, Aug 2, 2017 at 9:37 AM, Sauvageau, David mailto:david.sauvag...@bell.ca>> wrote: Hi TSC members, I would like to bring to our attention one major opportunity for improvement in the behaviour currently adopted by some of our community members. I am observing a big number of very large commits (10’s of thousands of lines of code in a single commit) which to me is a symptom of us not working well as a community yet. In order to be successful, I believe communities need to adopt an “Upstream first” approach, meaning that every single day, the new code is committed upstream. We need to avoid the “we’ll build it internally and then upstream the code” approach. This is the only way we’ll get traction as a community rather than allowing individual companies to push for internal agendas. With the current approach, it is very difficult for the community to start contributing to ongoing projects, or even to know what’s coming up on the projects as code is pushed by major chunks with no visibility on the roadmap. If we continue supporting such behaviour this will slow down the adoption of ONAP in production environments. I believe it is our responsibility as the TSC to change that behaviour, first by educating different organizations how open source should be handled, but probably also by putting technical mechanisms to prevent such a behaviour (e.g. Limit commit size; enforce multi-company reviews before merge, allow for unfinished code in the repo …, any suggestions welcome). I do not have a specific solution to propose, but I would ask the TSC to open up the dialogue on such behaviour. The Amsterdam release is quickly coming and I believe this needs to be addressed asap. I’d like to discuss the topic tomorrow during TSC. Comments, anyone? Thanks, ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> https://lists.onap.org/mailman/listinfo/onap-tsc 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] R2 use cases
Yes, Gaurav. Use cases are covered from functional features stand point. Non-functional are not thought about. As regards your question on vFW/vDNS use cases and the way it's structured (i.e. preconfigured with dummy VNF); even I am grappling to connect dots when it comes to lifecycle of service from VNF onboarding up to service instantiation. Would be of great help; if someone could shed some light on this. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: Gaurav Gupta (c) [mailto:guptagau...@vmware.com] Sent: Tuesday, July 25, 2017 8:33 AM To: Alla Goldner ; Dhananjay Pavgi Cc: onap-tsc Subject: Re: R2 use cases Dhananjay Good use cases but Hope you are thinking only at the functional interaction . You are not thinking about -- Performance and Capacity view . As I see the use case driving the Release Content and goal of ONAP . I had couple of question . Do we have any concrete definition w.r.t to a VNF . VNF to VF Relationship .( is it 1:n or m:n ) and VF to Controller Mapping .for example (SDNC and APPC/VNF-C) Why I am asking is For example for the demo use case of - vFW/vDNS - I am still not able to connect dots in terms of why some ONAP component interaction is needed when everything looks to be preloaded /preconfigured as per the Demo Flow . Thanks in advance to clarify . with best regards gaurav From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> mailto:onap-tsc-boun...@lists.onap.org>> on behalf of Alla Goldner mailto:alla.gold...@amdocs.com>> Sent: 21 July 2017 22:55 To: Dhananjay Pavgi; onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org> Cc: onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>; onap-tsc Subject: Re: [onap-tsc] R2 use cases Hi Dhananjay, Thanks for your inputs! Please provide your suggested use cases under https://wiki.onap.org/display/DW/Release+2+Use+Cases<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Release-2B2-2BUse-2BCases&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI&m=ATTgafIHYzOQf6JXLijsPu7rLnfRLJjkxWEUIpbraA4&s=I8WwmYUld5cA0UcFBfdgvVbpiMt2tZg5uEsW0aXHgr8&e=> For Enterprise vCPE use case extensions, I would suggest to work directly with Long (China Telecom) who provided the initial Enterprise vCPE use case proposal. Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image004.png@01D30594.0E2375E0] From: Dhananjay Pavgi [mailto:dp00476...@techmahindra.com] Sent: Friday, July 21, 2017 8:09 PM To: Alla Goldner mailto:alla.gold...@amdocs.com>>; onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org> Cc: onap-tsc mailto:onap-tsc@lists.onap.org>>; onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> Subject: RE: R2 use cases Thanks, Alla. Suggest that we consider following use cases : 1. Enterprise vCPE with integration with upstream BSS/Ordering system. [Note : we need to showcase as to how ONAP works with TMF Open APIs and also would be good to showcase Microservice Bus to accommodate existing BSS/OSS eco-system] 2. Consider one umbrella MPLS-VPN connectivity for Enterprise customer (something like BIS) as a Product and show how ONAP provides modularity and reusability at product component level. i. E.g. L2VPN : ELAN Port Based, ELAN VLAN Based, ELINE Port Based, ELINE VLAN Based. ii.L3VPN iii.Priority L2VPN (with QoS) iv.Priority L3VPN (with QoS) 3. Let us realize any of the use case in the list in below email (a thr' e) by having 2 or more VNFs residing across hybrid Telco Cloud e.g. one VNF on Mirantis Openstack and others on vanilla Opensack/VMWare etc. [Note : This will help us elucidate Multi-VIM support] thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI&m=ATTgafIHYzOQf6JXLijsPu7rLnfRLJjkxWEUIpbraA4&s=LVqDH8VSUH_7FBtaSauwOXAsp4e7u8UKuBYPHej-Twc&e=> Platinum Member. Visit : http://www.onap.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.onap.org_&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI&m=ATTgafIHYz
Re: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB
+1 thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Lingli Deng Sent: Monday, July 24, 2017 11:07 AM To: 'Kenny Paul' ; 'onap-tsc' Subject: Re: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB [VOTE] +1 Lingli From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Kenny Paul Sent: 2017年7月23日 2:49 To: onap-tsc mailto:onap-tsc@lists.onap.org>> Subject: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB As mentioned we have several repository requests queued up. Gildas has reviewed these and feels the requestors have done their due diligence regarding the data needed. Please vote for each one individually OR respond with a (+1, 0, -1) “ALL” to approve or reject all requests —— VOTE to approve the AAF Project's Requests for the creation of an incremental repository (+1, 0 -1) Components Name Components Repository name Maven Group ID Components Description luaplugin aaf/luaplugin org.onap.aaf.luaplugin A lua plugin to integrate AAF with MSB, which provides centralized auth features at the API Gateway. VOTE to approve the MSB Project's Requests for the creation of two incremental repositories (+1, 0 -1) Components Name Components Repository name Maven Group ID Components Description java-sdk msb/java-sdk org.onap.msb.sdk Provides a JAVA SDK for rapid microservices development, including service registration, service discovery, request routing, load balancing, retry, etc. swagger-sdk msb/swagger-sdk org.onap.msb.swagger-sdk Swagger sdk helps to generate swagger.json and java client sdk during the build time, it also helps to provide the swagger.json at the given URI in the run time. VOTE to approve the A&AI Project's Requests for the creation of two incremental repositories (+1, 0 -1) Components Name Components Repository Name Maven Group ID Components Discription esr-server aai/esr-server org.onap.aai.esr-server ESR backend, mainly include the function of external system reachable check and data pretreatment esr-gui aai/esr-gui org.onap.aai.esr-gui External system management ui VOTE to approve the Modeling Subcommittee’s requests for the creation of an incremental repository within the Modeling Project’s structure (+1, 0 -1) Components Name Components Repository name Maven Group ID Components Description modelspec modeling/modelspec org.onap.modeling.modelspec The repository for modeling specification published by modeling subcommittee Best Regards, -kenny Kenny Paul, Technical Program Manager kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org> 510.766.5945 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] R2 use cases
Thanks, Alla. Suggest that we consider following use cases : 1. Enterprise vCPE with integration with upstream BSS/Ordering system. [Note : we need to showcase as to how ONAP works with TMF Open APIs and also would be good to showcase Microservice Bus to accommodate existing BSS/OSS eco-system] 2. Consider one umbrella MPLS-VPN connectivity for Enterprise customer (something like BIS) as a Product and show how ONAP provides modularity and reusability at product component level. i. E.g. L2VPN : ELAN Port Based, ELAN VLAN Based, ELINE Port Based, ELINE VLAN Based. ii.L3VPN iii.Priority L2VPN (with QoS) iv.Priority L3VPN (with QoS) 3. Let us realize any of the use case in the list in below email (a thr' e) by having 2 or more VNFs residing across hybrid Telco Cloud e.g. one VNF on Mirantis Openstack and others on vanilla Opensack/VMWare etc. [Note : This will help us elucidate Multi-VIM support] thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner Sent: Friday, July 21, 2017 9:07 PM To: onap-usecase...@lists.onap.org Cc: onap-tsc ; onap-...@lists.onap.org Subject: [onap-tsc] R2 use cases HI all, Our major objective right now is to keep on track and finalize R1 use cases definitions. Having said that, I strongly believe we should work in parallel on R2 use cases. If you look on the flow below, ideally we should target completion of step 6 when Release starts, in order for project teams to deliver their functionality on time. That means we should be able to come up with our R2 use cases initial proposal by September f2f meeting - this would leave sufficient time to iterate with projects and, hopefully, enough time for architecture subcommittee for their related work. Please start including your R2 use cases proposals under https://wiki.onap.org/display/DW/Release+2+Use+Cases - we may have an opportunity to review them next week during our Virtual meeting. Right now, the list of potential proposals includes: * Network Function Change Management (agreed to reword as use case and move under R2) * Enterprise vCPE (agreed to move under R2, revision was presented during the last use case subcommittee meeting) * SD-WAN ? * SD-LAN ? * 5G ? i. RAN deployment ii. E2E Network Slicing iii. Mobile Edge Computing And proposal for usage of EPA technology across a different R2 use cases. Use case subcommittee flow: 1.Use case subcommittee discuses new use cases 2.Use case subcommittee produces use case flow diagrams, provides its view on the foreseen modules introductions/modifications and suggests potential PNFs / VNFs 3.Use case subcommittee gets feedback from the potentially effected projects including integration team on feasibility 4.Iterate back to 2 5.TSC approves the use case 6.In case a new modules or a new functionality to existing modules or a new APIs introduction is foreseen, architecture subcommittee defines the new/modified ONAP flows and the interfaces principles, based on the approved use cases (1) 7.Projects define their extended functionality and their external APIs, following those principles. 8.Detailed per-component flows are defined by the projects and projects write their user stories / implement them; Integration team continuously works with Use case subcommittee to accompany the use case development, review epics/user stories, answer questions, etc. Use case subcommittee behaves as system engineers for the use case through test start date 9.Integration team defines the gating use case based on step 8 and finalizes the PNFs / VNFs selection, with the help of use case subcommittee, architecture subcommittee, PTLs of a different ONAP projects 10. TSC approves the gating use case 11. Integration project leads (coordinates) effort to get the gating use case tested, repaired, and verified, and the results are documented. (1) The defined functional extensions should be as generic as possible to allow re-use of it by additional use cases. Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image004.png@01D3026C.5CA61C70] This message and the informatio
Re: [onap-tsc] TSC Members- Action Required Approval of changes to the Portal Platform Project
+1 thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner Sent: Monday, July 17, 2017 1:16 PM To: Lingli Deng ; 'Kenny Paul' ; 'onap-tsc' Cc: 'TATTAVARADA, SUNDER' Subject: Re: [onap-tsc] TSC Members- Action Required Approval of changes to the Portal Platform Project +1 Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image004.png@01D2FEFF.940978D0] From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Lingli Deng Sent: Monday, July 17, 2017 10:28 AM To: 'Kenny Paul' mailto:kp...@linuxfoundation.org>>; 'onap-tsc' mailto:onap-tsc@lists.onap.org>> Cc: 'TATTAVARADA, SUNDER' mailto:sta...@research.att.com>> Subject: Re: [onap-tsc] TSC Members- Action Required Approval of changes to the Portal Platform Project [VOTE] +1 Lingli From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Kenny Paul Sent: 2017年7月15日 8:05 To: onap-tsc mailto:onap-tsc@lists.onap.org>> Cc: TATTAVARADA, SUNDER mailto:sta...@research.att.com>> Subject: [onap-tsc] TSC Members- Action Required Approval of changes to the Portal Platform Project In an effort to try and minimize the level of email traffic on this list this approval was originally attempted this as a CIVS poll. Unfortunately quorum was not achieved. As such I’m falling back to an email vote to provide members that did not participate the opportunity to do so. From the TSC Charter: 3.2.2 CommitterLifecycle 3.2.2.1 Adding Committers * •Initial Committers for a project will be specified at project creation * Committer rights for a project are earned via contribution and community trust. Committers for a project select and vote for new Committers for that project, subject to TSC approval. * New Committers for a project should have a demonstrable established history of meritocratic contributions. TSC approval is requested for the following changes to the ONAP Portal Platform Project: https://wiki.onap.org/display/DW/Portal+Platform+Project - Add "Sunder Tatta”(sta...@research.att.com<mailto:sta...@research.att.com>) as a committer (Only a single committer currently on the project) - Add a new repository “portal/sdk” ACTION: I approve the committer addition (Vote +1, 0, -1) I approve the repository addition (Vote +1, 0, -1) Votes already cast are all in favor of approving both the committer and repository additions. mg1...@att.com<mailto:mg1...@att.com>: 1 jamil.cha...@orange.com<mailto:jamil.cha...@orange.com>: 1 meng.zhaoxi...@zte.com.cn<mailto:meng.zhaoxi...@zte.com.cn>: 1 aayush.bhatna...@ril.com<mailto:aayush.bhatna...@ril.com>: 1 stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com>: 1 ranny.ha...@nokia.com<mailto:ranny.ha...@nokia.com>: 1 Best Regards, -kenny Kenny Paul, Technical Program Manager kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org> 510.766.5945 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 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] TSC Meeting Minute Approvals
Please see inline. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: Kenny Paul [mailto:kp...@linuxfoundation.org] Sent: Thursday, July 06, 2017 4:59 PM To: Alla Goldner ; mg1...@att.com; Sauvageau, David ; Deng ; xiexj...@chinatelecom.cn; Ed Warnicke ; Stephen Terrill ; Amir Levy ; Christopher Donley (Chris) ; Jason Hunt ; rajesh.gadi...@intel.com; Haiby, Ranny (Nokia - US/San Jose USA) ; jamil.cha...@orange.com; aayush.bhatna...@ril.com; Dhananjay Pavgi ; Xinhui Li ; susana.saba...@vodafone.com; meng.zhaoxi...@zte.com.cn Cc: onap-tsc Subject: TSC Meeting Minute Approvals TSC Members: As agreed upon at last week’s TSC meeting we will pursue meeting minute approvals via email or a poll in order to maximize the amount of time available during the TSC meeting. Initially there are several weeks worth of meeting minutes that require approval. I have consolidated the approval requests into a single message in an effort to limit the volume of email generated. Going forward this will be done on a weekly basis. Please provide a response to each line with a +1, 0, -1 vote Approval of the TSC meeting minutes from June 29, 2017<http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-06-29-13.15.html> (Vote +1, 0 -1) : +1 Approval of the TSC meeting minutes from June 22, 2017<http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-06-22-12.49.html> (Vote +1, 0 -1) : +1 Approval of the TSC meeting minutes from June 15, 2017<http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-06-15-13.57.html> (Vote +1, 0 -1) : +1 Thank you. Best Regards, -kenny Kenny Paul, Technical Program Manager kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org> 510.766.5945 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] [onap-discuss] Tentative July ONAP Developers Face-to-Face Meeting
+1 thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Gadiyar, Rajesh Sent: Tuesday, June 13, 2017 9:12 AM To: GILBERT, MAZIN E (MAZIN E) ; Kenny Paul Cc: onap-disc...@lists.onap.org; onap-tsc Subject: Re: [onap-tsc] [onap-discuss] Tentative July ONAP Developers Face-to-Face Meeting +1 Good idea ☺ From: mailto:onap-tsc-boun...@lists.onap.org>> on behalf of "GILBERT, MAZIN E (MAZIN E)" mailto:ma...@research.att.com>> Date: Monday, June 12, 2017 at 2:01 PM To: Kenny Paul mailto:kp...@linuxfoundation.org>> Cc: "onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" mailto:onap-disc...@lists.onap.org>>, onap-tsc mailto:onap-tsc@lists.onap.org>> Subject: Re: [onap-tsc] [onap-discuss] Tentative July ONAP Developers Face-to-Face Meeting I was not present for this discussion. We need to have a meeting around the 3rd week of July to go through project by project progress. Phil and I discussed a virtual meeting since folks will be too busy to travel, and some may not be able to. Would like to get a sense from the TSC community if this is appropriate and more convenient while voting for dates. thanks Mazin On Jun 12, 2017, at 1:08 PM, Kenny Paul mailto:kp...@linuxfoundation.org>> wrote: Please respond to the doodle poll below no later than: Thurs. 01:00 PM UTC Thurs. 09:00 PM China Thurs: 09:00 AM Eastern Thurs: 06:00 AM Pacific https://doodle.com/poll/7zufivqebtnvrhdt<https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_7zufivqebtnvrhdt&d=DwMCAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=7n6f3RBF3LtkjuBpPhqrMbVfiHC_wqVOfDz5z3uutjM&s=W2yLAyRSo72NJJvcQibUZP8thCi407eXKwPoV15Q3N8&e=> Thank You. Best Regards, -kenny Kenny Paul, Technical Program Manager kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org> 510.766.5945 ___ onap-discuss mailing list onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=7n6f3RBF3LtkjuBpPhqrMbVfiHC_wqVOfDz5z3uutjM&s=8D2aZuG-pN820woJDvlHxyXQnkAsRt0bFjokAPWgc1E&e= 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] ONAP TSC Members - Are you Attending the China Face To Face Next Week?
-1 thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil Robb Sent: Friday, June 02, 2017 8:28 PM To: onap-tsc Subject: [onap-tsc] ONAP TSC Members - Are you Attending the China Face To Face Next Week? Please +1 or -1 if you are attending or not. Please respond ASAP so that we can know who can help facilitate different aspects of the event. Thanks! Phil. -- Phil Robb Executive Director, OpenDaylight Project VP Operations - Networking & Orchestration, The Linux Foundation (O) 970-229-5949 (M) 970-420-4292 Skype: Phil.Robb 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP R1 use cases, and open lab
+1. For lab having commercial ecosystem of VNFs; we may consider Tech Mahindra’s VNFXchange lab. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Gadiyar, Rajesh Sent: Friday, June 02, 2017 2:48 AM To: Hellmann, Gil (Wind River) ; onap-tsc@lists.onap.org Subject: Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP R1 use cases, and open lab +1 I was taking this as a given. We need a robust vendor/commercial ecosystem of VNFs and NFVI software, in addition to open source. I see that the vCPE and vVoLTE use case documents on the wiki already incorporate this; which I am supportive. From: mailto:onap-tsc-boun...@lists.onap.org>> on behalf of Gil Hellmann mailto:gil.hellm...@windriver.com>> Date: Thursday, June 1, 2017 at 2:08 PM To: "onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" mailto:onap-tsc@lists.onap.org>> Subject: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP R1 use cases, and open lab Dear TSC members, It is very exciting to see the great momentum and grow in the ONAP community, I hear that there is different opinion / debate with regard to whether release 1 of ONAP should be using commercial VNFs & NFVI+VIM’s solutions for the implementation of the proposed use cases and open lab / integration in release 1 or should it be strictly limited to use only open source. I would suggest that the TSC will consider the following before making a decision: As it was agreed by both the TSC and the wider ONAP community, using real life use case like the proposed VoLTE and vCPE use cases for release 1 is very important to ensure that ONAP is built from day 1 in a way that will provide close implementation to a real-life use case which can provide proper foundation to use ONAP in commercial deployment, and implementation of real life use case can have a great contribution to the success of this project. ONAP as orchestration / MANO project require NFVI+VIMs (clouds) to run on, and VNFs to run to create the services. The use of commercial NFVI+VIMs and VNFs for the use case implementation and open lab / integration can have a big positive impact on our ability to be as close as possible to a real-life usage scenario. Limiting the usage *to only open source* solutions will limit dramatically the ability to get there. Not saying we should not use open source VNFs and NFVI+VIMs, but I hope we wouldn’t limit ourselves to only open source VNFs & NFVI+VIM in the open lab / integration lab and for the release 1 use cases, same like we would not limit yourself to only use open source hardware. I hope this can be considered, and thanks for your consideration. Regards, Gil Hellmann, VP - Solutions Readiness direct 289.553.5815 mobile 905.409.6878 skype ID gil.hellmann [cid:image009.png@01D2DB86.AE5C4970]<http://www.windriver.com/email/sigs/blog-network.html> [cid:image010.png@01D2DB86.AE5C4970] <http://www.linkedin.com/company/wind-river> [cid:image011.png@01D2DB86.AE5C4970] <http://www.windriver.com/email/sigs/facebook.html> [cid:image012.png@01D2DB86.AE5C4970] <http://www.windriver.com/email/sigs/twitter.html> [cid:image013.png@01D2DB86.AE5C4970] <http://www.windriver.com/email/sigs/youtube.html> [cid:image014.gif@01D2DB86.AE5C4970]<http://www.windriver.com/> “If you will it, it is no dream.” Theodor Herzl “If you want to go fast, go alone. If you want to go far, go together.” An old African proverb “The only way to avoid making mistakes is not to do anything. And that.. will be the ultimate mistake” Goh Keng Swee 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] Release Naming
Suggest option 2. We are dealing with the domain of Orchestration :) and actually, much beyond. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of GILBERT, MAZIN E (MAZIN E) Sent: Wednesday, May 17, 2017 3:23 AM To: onap-tsc Subject: [onap-tsc] Release Naming Team, I have two proposals for release naming. One from Rueben Klein and the other from Gildas Lanilis. The first is famous cities belonging to platinum members, and the other is famous conductors in the domain of orchestrating:-) Both follow the alphabet style. Please review and share comments before our TSC meeting on Thursday. Thanks Mazin Option 1 Platinum Member Country<https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_Country&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=SzgbQMfNr3fZoBR_SjXxblyJEpSPOTDUI8MQquOqyzI&s=NSkr48qokE_fsPEScprurl5LH2_NnfUfZmYR9mXODiU&e=> Major Locations IBM US<https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_Peru&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=SzgbQMfNr3fZoBR_SjXxblyJEpSPOTDUI8MQquOqyzI&s=tQRfIQXJOYqhuK_mwy_BfjadPPlBsfUlcz_TOW5jKFo&e=> Armonk China Mobile/Telecom China Beijing Amdocs US Chesterfield AT&T US<https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_Egypt&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=SzgbQMfNr3fZoBR_SjXxblyJEpSPOTDUI8MQquOqyzI&s=kk5F5x3gUBkCCjG9y8SIy8CHLwUaoT14XoylofBH7-4&e=> Dallas Nokia Finland<https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_Vietnam&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=SzgbQMfNr3fZoBR_SjXxblyJEpSPOTDUI8MQquOqyzI&s=rk5QoP5ur9Gz8JIwa1htetsl01vE4BAxoR-MsGDsmuw&e=> Espoo VMWare US (IL) Herzliya Intel US Irvine Ericsson Sweden<https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_Pakistan&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=SzgbQMfNr3fZoBR_SjXxblyJEpSPOTDUI8MQquOqyzI&s=wZV79oAeqlvTzwKrdfMzRBOkqOBImNA9IPK0xny3bT8&e=> Kista Tech Mahindra India<https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_Canada&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=SzgbQMfNr3fZoBR_SjXxblyJEpSPOTDUI8MQquOqyzI&s=5m-snnD_j5tbPtS0MzIcGbAPrSurGg-G2kcPRYWsU_I&e=> Mumbai Gigaspaces US New York Bell Canada Canada<https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_Republic-5Fof-5FIreland&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=SzgbQMfNr3fZoBR_SjXxblyJEpSPOTDUI8MQquOqyzI&s=vTwVDfqRKekRqOgMvIDOcRKWVJ3NUJgEVnL92x4MeHU&e=> Ottawa Orange France<https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_France&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=SzgbQMfNr3fZoBR_SjXxblyJEpSPOTDUI8MQquOqyzI&s=1ZKIZT1nhfSal9pxJqMrR_Gy8JsJ9gc0q43FCPwNauM&e=> Paris Cisco US San Jose Huawei China<https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_Ukraine&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=SzgbQMfNr3fZoBR_SjXxblyJEpSPOTDUI8MQquOqyzI&s=0pSzLF1o46ZRle-UmWsashceiPTEt8NC1HQzmtPq1AA&e=> Shenzhen ZTE China Tianjin Option 2 Famous Conductors: As ONAP plays in the domain of orchestrating, we could use the name of famous conductors. Continuous Naming: Amadeus, Beethoven, Chopin, Debussy, Enescu, Foote, Gershwin, Handel, Ilyich, Johannes Non-Continuous naming: Amadeus, Beethoven, Chopin, Debussy, Gershwin, Liszt, Puccini, Ravel, Schubert, Tchaikovsky, Vivaldi, Wagner 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] Proposal for structuring Modeling projects
Hi Andrei, Valid point. There's certainly an overlap in multiple ONAP projects that deal with modelling. Option 1 sounds more logical. Would have all aspects of Design Time environment covered under one umbrella than having yet another umbrella project (as depicted in Option 2 and 3). thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Andrei Kojukhov Sent: Thursday, May 11, 2017 12:46 AM To: onap-discuss ; onap-tsc@lists.onap.org Subject: [onap-tsc] Proposal for structuring Modeling projects Dear all, Currently there are 6 draft projects in ONAP that deal with modeling, onboarding and certification. The below table summarizes the 6 initiatives and presents the feature coverage of each one of them. ONAP Project Features covered by the project VNF/Service Design VNF Guidelines VNF Certification VNFD/VNF package onboard Modeling - overall modeling issues V Incubation and Certification Entity (ICE) V V V Service Design and Create (SDC) v V V V VNF-SDK V V V CLAMP V Policy Framework V Besides an overlap in content and resources allocation of contributors, my expectation is that there will be issues with synchronization of requirements such as VNF guidelines and requirements derived from Use cases as well as maintaining open source. Therefore, I'm proposing to consider structuring the above described ONAP projects. One of possible umbrella projects may be SDC covering most if not all the design and onboarding related features. The Service Design and Create can be seen as one candidate as unified platform for * Validation and verification of VNF guidelines, * VNF/Service Design studio * Standard VNFD/VNF package onboarding platform based on ETSI NFV SOL001, SOL004 specifications leveraging TOSCA YAML modeling and CSAR packaging * Multilayered VNF Certification including VNF package integrity and authenticity validation, VNF deployment and running VNF tests verifying non-functional VNF KPI's that are currently specified in ETSI NFV EVE011 work, There may be different options of structuring all or part of the ONAP initiatives as shown in the following pictures. Option 1: SDC umbrella [cid:image003.png@01D2CCCE.8C1F8190] Option 2: "Design Automation" umbrella including on-boarding and certification [cid:image004.png@01D2CCCE.8C1F8190] Option 3: "Design Automation" umbrella excluding on-boarding and certification [cid:image005.png@01D2CCCE.8C1F8190] I would like to invite ONAP community members to provide their view on possible structuring. BR, Andrei Andrei Kojukhov, PhD Open Network Division Amdocs Technology [cid:image006.png@01D2CCCE.8C1F8190] 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 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] Proposal: Architecture Subcommittee
+1 for Architecture subcommittee. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Gadiyar, Rajesh Sent: Saturday, May 13, 2017 6:17 AM To: Alla Goldner ; Christopher Donley (Chris) ; SPATSCHECK, OLIVER (OLIVER) ; aayush.bhatna...@ril.com Cc: onap-tsc@lists.onap.org Subject: Re: [onap-tsc] Proposal: Architecture Subcommittee +1 for forming the Architecture Subcommittee; Also agree with Chris and Alla on the ‘advisory’ nature of the Architecture sub-committee, and the important overseeing role this committee needs to play to ensure the consistency across the ONAP modules, interfaces, contentious issues between projects etc. Leading upto the Middletown meetings, the effort that Vimal and Lingli had started with a small team on the ONAP architecture evolution and the architecture principles had made excellent progress. I like a small team approach for the Architecture Subcommittee (perhaps 1 participant nominated by each TSC member from their respective company) with a regular (monthly?) synch point with the larger technical community. Rajesh From: mailto:onap-tsc-boun...@lists.onap.org>> on behalf of Alla Goldner mailto:alla.gold...@amdocs.com>> Date: Friday, May 12, 2017 at 10:46 AM To: "Christopher Donley (Chris)" mailto:christopher.don...@huawei.com>>, "SPATSCHECK, OLIVER (OLIVER)" mailto:spat...@research.att.com>>, "aayush.bhatna...@ril.com<mailto:aayush.bhatna...@ril.com>" mailto:aayush.bhatna...@ril.com>> Cc: "onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" mailto:onap-tsc@lists.onap.org>> Subject: Re: [onap-tsc] Proposal: Architecture Subcommittee +1, as also provided by my previous response to Aayush. Architecture subcommittee, if created, should not deal with any specific architecture requirements, which are up to release/project to define. Architecture subcommittee should review interactions between a different components/modules per defined Release goals, i.e. be responsible to validate whether e2e architecture across all modules is correct, whether all necessary interactions are covered etc.. It may also propose a new project, if gaps are identified, but it will be up to community to create such a project and up to TSC to approve/reject it. Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image004.png@01D2CBD0.3A563510] From: Christopher Donley (Chris) [mailto:christopher.don...@huawei.com] Sent: Friday, May 12, 2017 8:38 PM To: SPATSCHECK, OLIVER (OLIVER) mailto:spat...@research.att.com>>; aayush.bhatna...@ril.com<mailto:aayush.bhatna...@ril.com> Cc: Alla Goldner mailto:alla.gold...@amdocs.com>>; Kanagaraj Manickam mailto:kanagaraj.manic...@huawei.com>>; bob.monk...@arm.com<mailto:bob.monk...@arm.com>; onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> Subject: RE: [onap-tsc] Proposal: Architecture Subcommittee +1. The architecture subcommittee should NOT put gating requirements on any projects. Projects should be responsible for their own release plans and resources. I want to stress that my proposal is for an advisory committee, not a controlling committee. Specifically, the architecture subcommittee doesn’t have the power to make decisions or vote. By Charter, that is solely the purview of the TSC. If decisions need to be made, such issues will be brought to the TSC. The architecture subcommittee is advisory by nature, and not authoritative. It may provide advice to projects and to the TSC, such as by providing a forum to help resolve architectural questions that may arise. The subcommittee should help to set a target functional architecture for the community (but not mandate it). That target may move over time, and it may take projects more than one release to catch up to it. Scoping would be the responsibility of each project. I also think there should be room for innovation. If a team has a good idea that would change the functional architecture, we may want to consider it. I believe having a consensus target and a defined forum helps facilitate those conversations. In the draft release plan, there is a checkpoint between functionality freeze and API freeze for an architecture check. I think that would be a good spot for the architecture subcommittee to schedule a walk-through with each project to discuss the handoffs between each component to identify any gaps so that teams have time to respond prior to API freeze. The subcommittee should be asking questions, not dictating answers. Chris From: SPATSCHECK, OLIVER (OLIVER) [mailto:spat...@res
Re: [onap-tsc] Project Proposal: ONAP CLI
Spot on, Brian. You got it. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: FREEMAN, BRIAN D [mailto:bf1...@att.com] Sent: Tuesday, May 09, 2017 10:55 PM To: Dhananjay Pavgi ; Kanagaraj Manickam ; t...@lists.onap.org Subject: RE: Project Proposal: ONAP CLI Scripting is useful but shell scripts that wrap curl functions are the method we are pushing folks towards. Separate CLI and REST API’s are generally a waste. With automation we see less pressure to have a CLI and more a need to be able to get the work done and CURL/POSTMAN are the tools of the new devops environment. Brian From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Dhananjay Pavgi Sent: Tuesday, May 09, 2017 6:32 AM To: Kanagaraj Manickam mailto:kanagaraj.manic...@huawei.com>>; t...@lists.onap.org<mailto:t...@lists.onap.org> Subject: Re: [onap-tsc] Project Proposal: ONAP CLI Thanks. Don’t agree with the comment on GUI can’t be used in DevOps. Wonder how CLI would be easier in any which ways to work with clumsy yaml/TOSCA files. CLI was good for short service commands. While it would still make sense to have it for VNFs; for some of the reasons sighted below. For Network Automation Platform like ONAP; still ponder over it’s necessity. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_&d=DwMFbw&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=ncRngcZpXka2jMSmL1oJGt4w1hL19yXmHBVERs05SNw&s=Zu_mS4NKhmNLm4tuW1BV3uizS5cAdpEYQkPdFGvAaVs&e=> Platinum Member. Visit : http://www.onap.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.onap.org_&d=DwMFbw&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=ncRngcZpXka2jMSmL1oJGt4w1hL19yXmHBVERs05SNw&s=FE7k_tXBoEXofY-ciKQkRTncgzJdWRKjiUxeeTE_3es&e=> From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com] Sent: Tuesday, May 09, 2017 7:37 PM To: Dhananjay Pavgi mailto:dp00476...@techmahindra.com>>; t...@lists.onap.org<mailto:t...@lists.onap.org> Subject: RE: Project Proposal: ONAP CLI Thanks for sharing your comments. Pls find my inputs below: CLI has its own advantages over GUI in following aspects: 1. ONAP Continuous integration (CI), where we want to perform various ONAP operations, CLI will be very handy option. This is applicable to 3rd party CI as well. 2. While GUI is the preferred interface for end-user, back-end operators and admin always prefer CLI (it’s an industry trend !) as its simpler, faster. 3. Installation scripting, VNF boot scripting with ONAP. 4. Dev testing … integration testing. 5. OSS/BSS products would want to perform any automation on top of ONAP, it could go either with CLI or SDK. In short, GUI can’t be used in devops environment, and CLI fills the gap. In addition, CLI provides an alternate option to GUI, for operating back ONAP functionalities. And to feel the importance of CLI, Pls refer some existing active automation projects in industry, given here: 1. OpenStack heat provides CLI ‘openstack stack’ 2. Cloudify provides CLI ‘cfy’ 3. ODL provides CLI with different commands So IMHO, - CLI does compliment GUI and does not defeat it. - Considering ONAP as platform, CLI should be part of it. Regards Kanagaraj M *** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！** *** This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! *** From: Dhananjay Pavgi [mailto:dp00476...@techmahindra.com] Sent: Tuesday, May 09, 2017 2:09 PM To: Kanagaraj Manickam; t...@lists.onap.org<mailto:t...@lists.onap.org> Subject: RE: Project Proposal: ONAP CLI Do we really need CLI. Defeats the
Re: [onap-tsc] Project Proposal: ONAP CLI
Thanks. Don’t agree with the comment on GUI can’t be used in DevOps. Wonder how CLI would be easier in any which ways to work with clumsy yaml/TOSCA files. CLI was good for short service commands. While it would still make sense to have it for VNFs; for some of the reasons sighted below. For Network Automation Platform like ONAP; still ponder over it’s necessity. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com] Sent: Tuesday, May 09, 2017 7:37 PM To: Dhananjay Pavgi ; t...@lists.onap.org Subject: RE: Project Proposal: ONAP CLI Thanks for sharing your comments. Pls find my inputs below: CLI has its own advantages over GUI in following aspects: 1. ONAP Continuous integration (CI), where we want to perform various ONAP operations, CLI will be very handy option. This is applicable to 3rd party CI as well. 2. While GUI is the preferred interface for end-user, back-end operators and admin always prefer CLI (it’s an industry trend !) as its simpler, faster. 3. Installation scripting, VNF boot scripting with ONAP. 4. Dev testing … integration testing. 5. OSS/BSS products would want to perform any automation on top of ONAP, it could go either with CLI or SDK. In short, GUI can’t be used in devops environment, and CLI fills the gap. In addition, CLI provides an alternate option to GUI, for operating back ONAP functionalities. And to feel the importance of CLI, Pls refer some existing active automation projects in industry, given here: 1. OpenStack heat provides CLI ‘openstack stack’ 2. Cloudify provides CLI ‘cfy’ 3. ODL provides CLI with different commands So IMHO, - CLI does compliment GUI and does not defeat it. - Considering ONAP as platform, CLI should be part of it. Regards Kanagaraj M *** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！** *** This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! *** From: Dhananjay Pavgi [mailto:dp00476...@techmahindra.com] Sent: Tuesday, May 09, 2017 2:09 PM To: Kanagaraj Manickam; t...@lists.onap.org<mailto:t...@lists.onap.org> Subject: RE: Project Proposal: ONAP CLI Do we really need CLI. Defeats the purpose of automation and GUI/Portals made available at each layer. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Kanagaraj Manickam Sent: Tuesday, May 09, 2017 6:36 PM To: t...@lists.onap.org<mailto:t...@lists.onap.org> Subject: [onap-tsc] Project Proposal: ONAP CLI Dear Team, In ONAP, Command-Line Interface (CLI) is not available. So I would like to propose the new project to provide ONAP CLI, by using model-driven CLI framework available in Open-O. Please find the proposal at https://wiki.onap.org/display/DW/ONAP+CLI And let me know your review comments. Thanks. Regards Kanagaraj M *** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！** *** This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other tha
Re: [onap-tsc] Project Proposal: ONAP CLI
Do we really need CLI. Defeats the purpose of automation and GUI/Portals made available at each layer. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Kanagaraj Manickam Sent: Tuesday, May 09, 2017 6:36 PM To: t...@lists.onap.org Subject: [onap-tsc] Project Proposal: ONAP CLI Dear Team, In ONAP, Command-Line Interface (CLI) is not available. So I would like to propose the new project to provide ONAP CLI, by using model-driven CLI framework available in Open-O. Please find the proposal at https://wiki.onap.org/display/DW/ONAP+CLI And let me know your review comments. Thanks. Regards Kanagaraj M *** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！** *** This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! *** 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
[onap-tsc] [onap-discuss] Modelling discussion on Friday May 5th
Great thought, Aayush. Agreed. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png at 01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-bounces at lists.onap.org [mailto:onap-tsc-bounces at lists.onap.org] On Behalf Of aayush.bhatna...@ril.com Sent: Thursday, April 27, 2017 12:18 PM To: michael at gigaspaces.com; denglingli at chinamobile.com Cc: rjana at research.att.com; onap-discuss at lists.onap.org; onap-tsc at lists.onap.org Subject: Re: [onap-tsc] [onap-discuss] Modelling discussion on Friday May 5th Dear Michael, Ling Li I have a suggestion here to move forward - We should indeed have a broader workflow discussion, and consider the end to end aspects (which would be ?realized? by ECOMP and Open-O merged at ONAP). All workflows should have a reference to the TOSCA declarative model-driven orchestration, so that we arrive at ?ECOMP Templates? for each of the workflows. Some of the workflows that we can take up are listed below as a suggestion (largely aligned to the ETSI MANO requirements): 1. Lifecycle Management workflows for VNFs (Onboarding, Packaging, Instantiation, Auto scaling and Termination) 2. Lifecycle Management workflows for Network Services (NS) on the same lines 3. Workflows for service creation through VNF FGs. 4. Onboarding of NFVI resources fulfilment (underlying hardware and virtualization to add resources to the pool) leading to resource discovery processes from a NFVO perspective (ECOMP AAI may play a role here). 5. Workflows for fault management and VNF shifting/migration 6. Other aspects ? I believe our joint objective should be to define the scope of these workflows and arrive at an agreeable set of flows which can be implemented / realized using ECOMP. BPMN based workflow implementations can also co-exist with the TOSCA model-driven graphs. However, we may discuss in more detail on how to move forward in this aspect. There would always still remain specific workflows for users of the ECOMP platform, which can be then be designed using the ECOMP design time framework and perhaps the ?learnings? can be contributed back to the community This can help us formally develop as a workflow design library for ECOMP, enabling VNF providers to quickly adopt the platform by using its templates and also contributing the learnings back to make it better. If all agree in principle, we can discuss and move forward. Regards Aayush Bhatnagar Reliance Jio From: onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Michael Brenner Sent: 26 April 2017 22:00 To: Lingli Deng Cc: onap-discuss; JANA, RITTWIK (RITTWIK); onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org> Subject: Re: [onap-tsc] [onap-discuss] Modelling discussion on Friday May 5th Lingli, all: I though we are now discussing ONAP and how to improve it, and not Open-O? Furthermore, ONAP is indeed using BPEL/BPMN workflows, but that is as part of the MSO. MSO may decide to delegate certain portion of the orchestration to a TOSCA-based orchestration engine, and what is delegated to such engine may have to use its own internal/native workflows. The real question here is: are we trying to leverage the best of all we have available, or are we trying to keep replicating the status-quo forever. Regardless of the answer, I find it that it is a very narrow perspective if we only want to discuss workflows in the context of what was implemented initially in Open-O or ECOMP, instead of opening a broader discussion of what makes sense where in the overall architecture. Best regards, Michael On Wed, Apr 26, 2017 at 2:10 AM, Lingli Deng mailto:denglingli at chinamobile.com>> wrote: Hi Michael, You may consult your gigaspace's colleage, as my recollection, native workflow proposed by gigaspaces was turned down by the consensus of the OPENO community, we decided to use BPMN/BPEL type of workflow, you can also find out the workflow in MSO /APPC of OPENCOMP are also using BPMN/DG Thanks, Lingli From: onap-discuss-bounces at lists.onap.org<mailto: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 Michael Brenner Sent: 2017?4?26? 11:09 To: denghui (L) mailto:denghui12 at huawei.com>> Cc: onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org>; JANA, RITTWIK (RITTWIK) mailto:rjana at research.att.com>>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Subject: Re: [onap-discuss] Modelling discussion on Friday May 5th But no TOSCA native workflows ... why? Michael On Tue, Apr 25, 2017 at 8:03 PM, denghui (L) mailto:denghui12 at huawe
[onap-tsc] Repo Question
+1 thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png at 01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-bounces at lists.onap.org [mailto:onap-tsc-bounces at lists.onap.org] On Behalf Of xiexj...@chinatelecom.cn Sent: Thursday, April 27, 2017 9:20 AM To: David Sauvageau ; Christopher.Donley Cc: SPATSCHECK, OLIVER \(OLIVER\) ; onap-tsc Subject: Re: [onap-tsc] Repo Question +1 Xiaojun From: Sauvageau, David<mailto:david.sauvag...@bell.ca> Date: 2017-04-27 06:48 To: Christopher Donley (Chris)<mailto:Christopher.Donley at huawei.com> CC: Phil Robb via onap-tsc<mailto:onap-tsc at lists.onap.org>; SPATSCHECK, OLIVER \(OLIVER\)<mailto:spatsch at research.att.com> Subject: Re: [onap-tsc] Repo Question +1 Envoy? de mon iPhone Le 26 avr. 2017 ? 18:36, Christopher Donley (Chris) mailto:Christopher.Donley at huawei.com>> a ?crit : +1 Chris From: onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner Sent: Wednesday, April 26, 2017 10:06 AM To: Ed Warnicke; SPATSCHECK, OLIVER (OLIVER) Cc: Phil Robb via onap-tsc Subject: Re: [onap-tsc] Repo Question +1 Alla Goldner Original Message Subject: Re: [onap-tsc] Repo Question From: Ed Warnicke mailto:hagb...@gmail.com>> Date: Apr 26, 2017, 7:34 PM To: "SPATSCHECK, OLIVER (OLIVER)" mailto:spatsch at research.att.com>> +1 Ed On Wed, Apr 26, 2017 at 8:14 AM, SPATSCHECK, OLIVER (OLIVER) mailto:spatsch at research.att.com>> wrote: Dear TSC, I think we have a little conundrum with the current code base repos. As you are likely aware the original code base we had released was matching our 1610 internal release. We have been busy the last few weeks uploading the delta to bring the public code base up to the current internal version to give the community the same view/code we use today. Now it turns out that our current internal code base requires some additional ?sub-repos? 3 under A&AI and one under SDC. Without those repos we can not complete the public code update by 5/5 as originally promised. The conundrum now is that we still don?t have a charter and no projects have been created yet. So there is no process for us to create those additional repos on LF servers. Therefore, I am requesting a one time waiver from the TSC allowing the LF to create those repos so we can complete the code base update in a timely manor. I don?t really think there is any substantial risk as the TSC can always decide to delete the repos again later if the TSC doesn?t like them. On the positive side it allows the community to see all the code in a timely manor. To be clear those are nor new functional components. Those repos only include improvements to the existing functional components in particular A&AI and SDC. Thx Oliver ___ ONAP-TSC mailing list ONAP-TSC at lists.onap.org<mailto:ONAP-TSC at lists.onap.org> https://lists.onap.org/mailman/listinfo/onap-tsc 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 ___ ONAP-TSC mailing list ONAP-TSC at lists.onap.org<mailto:ONAP-TSC at lists.onap.org> https://lists.onap.org/mailman/listinfo/onap-tsc 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <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/20170427/2d0a35a9/attachment-0001.html> -- next part -- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 4909 bytes Desc: image001.png URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170427/2d0a35a9/attachment-0001.png> -- next part -- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 7337 bytes Desc: image002.jpg URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170427/2d0a35a9/attachment-0001.jpg>
[onap-tsc] Updated TSC Charter
On MVP and text in below email from Bryan, Clarification as to what an MVP is as the target for the end of the incubation phase. Believe, that's where we need to some element of Product Management. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png at 01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-bounces at lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Stephen Terrill Sent: Thursday, April 20, 2017 12:32 AM To: SULLIVAN, BRYAN L ; Christopher Donley (Chris) ; onap-tsc at lists.onap.org Cc: Ed Warnicke Subject: Re: [onap-tsc] Updated TSC Charter Hi, Thanks for the comments Bryan. On responding comment in the "incubation" and MVP definition and that is on the proposed addition of "That is (or can be) used in a production environment". The use in a "production environment" is also subject to whatever additions and support is required. I can agree that MVP is subject to the same question in that its very subjective. Its not obvious to phrase in a non-subjective way, but we could remove MVP and go with "Project has resources, but is recognized to be in an early stage of development and not generally considered suitable to a production environment." I'm ok with the contributor clarification. Best Regards, Steve. From: onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of SULLIVAN, BRYAN L Sent: 19 April 2017 19:12 To: Christopher Donley (Chris) mailto:Christopher.Donley at huawei.com>>; onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org> Cc: Ed Warnicke mailto:eaw at cisco.com>> Subject: Re: [onap-tsc] Updated TSC Charter Chris, Not sure I can post to the TSC list, but here are some comments in the draft: * Each project will have its own code repositories (one or multiple),... o The concept of an umbrella project may address this, but that's an overhead that should be optional. It may be more effective in some cases for projects just to have multiple repos. * A Contributor is someone who contributes code or other artifacts to a project, and reviews the contributions of others. Contributors are not necessarily from Member companies. o We should encourage and recognize all forms of contribution, especially reviews. IMO contributors may provide *no* code but still contribute valuable advice on architecture, quality, testability, or other contributions of a non-code/artifact nature. * Committer rights for a project are earned via code contribution ... o The potential pool of committers should go beyond just code contribution, given the merit of their other types of contributions * (description of Incubation phase) Project has resources, but is recognized to be in early stages of development, having yet to achieve a MVP (Minimum Viable Product) that is (or can be) used in production environments. o Clarification as to what an MVP is as the target for the end of the incubation phase. * Other editorial items Thanks, Bryan Sullivan | AT&T From: onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Christopher Donley (Chris) Sent: Wednesday, April 19, 2017 8:45 AM To: onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org> Cc: Ed Warnicke mailto:eaw at cisco.com>> Subject: [onap-tsc] Updated TSC Charter Dear TSC, On behalf of the Charter drafting team, please find attached an updated version of the TSC Charter incorporating your suggestions and feedback from the last review. We have attempted to highlight the open issues that need a decision from the TSC. We are sending this draft with the intention that you review it in preparation for discussion and voting during our next TSC meeting. Chris, Steve, Ed, Lingli, Alla, and Phil 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <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/
[onap-tsc] Some questions regarding Controllers in ONAP Architecture
Can we then say, Network Controller is some sort of VIM and App Controller is sort of VNF-m. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png at 01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-bounces at lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of ROSE, DANIEL V Sent: Tuesday, April 18, 2017 9:33 PM To: HU, BIN ; onap-tsc at lists.onap.org; discuss at lists.onap.org Subject: Re: [onap-tsc] Some questions regarding Controllers in ONAP Architecture - SDN Agent: [1] was a proposal and not how it is implemented today so I will leave the discussion of that to someone else but my understanding is it would be in the open-o repo (if it exists at all today) - Infrastructure Controller: right now its openstack (not just nova) but I know we are adding more. MSO would have the multicloud logic (maybe via cloudify or something) to handle that. The code you should be looking for is the po adapters in MSO (https://gerrit.onap.org/r/gitweb?p=mso/libs.git;a=tree;h=refs/heads/release-1.0.0;hb=refs/heads/release-1.0.0). - Network Controller: SDN-GC is the network controller and is odl based. Check out https://wiki.onap.org/display/DW/Architecture for the architecture of each part. The extra logic we have like sli is a separate docker which is then called by odl at certain points. - App Controller: Has the same architecture as SDN-GC (ie is odl + sli based). It's basically different karaf plugins and you could run them on either platform - it is an architecture distinction more at this point I believe For either controller Brian freeman can go into more detail. Thanks, Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of HU, BIN Sent: Tuesday, April 18, 2017 11:53 AM To: onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org>; discuss at lists.onap.org<mailto:discuss at lists.onap.org> Subject: [onap-tsc] Some questions regarding Controllers in ONAP Architecture ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hello community, Reading current ONAP architecture [1] and tutorial of setting up the base ONAP stack [2], I have a few questions regarding those controllers: - SDN Agent: o What is the role, features and functions of SDN Agent? How is it different from Network Controller? o I couldn't find any code of SDN Agent in ONAP repo [3]. Does anyone know where it is? - Infrastructure Controller: o Is it OpenStack Nova? Or is it agnostic of any VIM and OpenStack is just one of the VIM? o If the intention is to be agnostic of VIM, and support other VIMs, where is a plugin/adaptor from architecture point of view? o I couldn't find code either in ONAP [3]. Does anyone know where it is? - Network Controller: o Is it OpenStack Neutron or ODL? Or Neutron with ODL as backend? o I found the code in [3], but it seems it only installs ODL there (correct me if I am wrong). o What is the primary role, features and functions of Network Controller other than those in ODL? - App Controller: o Are we using ODL too as App Controller? o Or Is it a container orchestrator or something else? Appreciate if someone can explain some details, or give the pointer to more detailed documentation. Thanks Bin [1] https://wiki.onap.org/display/DW/ONAP at ONS2017?preview=/3245268/3245303/ONAP%20Architecture%20Overview%20_Final-1.pdf<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_ONAP-40ONS2017-3Fpreview-3D_3245268_3245303_ONAP-2520Architecture-2520Overview-2520-5FFinal-2D1.pdf&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=3_AC6BGbT6uU35Nl7J2S5u7jo61YQjIHG11hEPv62EA&s=jRBZsDc2CyioeVWjhCRKHkPCIWewvBN-ob1eR-vvr1A&e=> [2] https://wiki.onap.org/display/DW/Tutorial%3A+Configuring+and+Starting+Up+the+Base+ONAP+Stack<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Tutorial-253A-2BConfiguring-2Band-2BStarting-2BUp-2Bthe-2BBase-2BONAP-2BStack&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=3_AC6BGbT6uU35Nl7J2S5u7jo61YQjIHG11hEPv62EA&s=2ECLYmyNHjMuNAksMX82uMlGnsn1yZWHQ2z1K80oUB8&e=> [3] https://git.onap.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=3_AC6BGbT6uU35Nl7J2S5u7jo61YQjIHG11hEPv62EA&s=xyj30pXIgxQyZunOXabVRS2Br7nc9M9jbO8-N7wrLi4&e=>
[onap-tsc] ONAP F2F TSC meeting minutes April 6
Also, from Tech Mahindra, it was myself and not Anit Lohtia. Needs a correction. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png at 01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-bounces at lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Gildas Lanilis Sent: Monday, April 10, 2017 8:31 PM To: onap-tsc at lists.onap.org Subject: Re: [onap-tsc] ONAP F2F TSC meeting minutes April 6 Meeting Minutes update: During our ONAP F2F meeting, Ning So (Ning.So at ril.com<mailto:Ning.So at ril.com>) representing Reliance Jio was present (he arrived just after the TSC Members roll call) . Thanks, Gildas Gildas Lanilis OPEN-O Release Manager gildas.lanilis at huawei.com<mailto:gildas.lanilis at huawei.com> Mobile: 1 415 238 6287 From: Gildas Lanilis Sent: Thursday, April 06, 2017 9:54 PM To: 'onap-tsc at lists.onap.org' Subject: ONAP F2F TSC meeting minutes April 6 Hi All, Please find below the IRC link toward the ONAP F2F TSC meeting minutes that took place at Santa Clara Convention Center on Thursday, April 6, 2017 from 3:30 pm PDT to 6:30 pm PDT. http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-04-06-22.42.html For those who are interested to access the email archives on all ONAP-TSC threads use this link<https://lists.onap.org/pipermail/onap-tsc/>. Once available, the link toward the Zoom recording will be shared. Participants: AMDOCS Alla Goldner AT&T Mazin Gilbert Bell Canada David Sauvageau China Mobile Lingli Deng China Telecom Mr. Xiaojun XIE Absent Cisco Ed Warnicke EricssonStephen Terrill Gigaspaces Amir Levy Huawei Chris Donley IBMJason Hunt Intel Rajesh Gadiyar NokiaRanny Haiby Orange Roberto Kung Reliance Jio Absent Tech Mahindra Anit Lohtia VMWare Xinhui Li ZTE Meng Zhaoxing proxied by Huabing Zhao Let me know if you have any questions. Thanks, Gildas [HuaweiLogowithName] Gildas Lanilis OPEN-O Release Manager gildas.lanilis at huawei.com<mailto:gildas.lanilis at huawei.com> Mobile: 1 415 238 6287 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <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/20170410/bef3f407/attachment-0001.html> -- next part -- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 4909 bytes Desc: image002.png URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170410/bef3f407/attachment-0002.png> -- next part -- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 7337 bytes Desc: image003.jpg URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170410/bef3f407/attachment-0001.jpg> -- next part -- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 2975 bytes Desc: image004.png URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170410/bef3f407/attachment-0003.png>
[onap-tsc] Charter
Agreed with Ning. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png at 01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-bounces at lists.onap.org [mailto:onap-tsc-bounces at lists.onap.org] On Behalf Of ning...@ril.com Sent: Monday, April 10, 2017 9:11 PM To: stephen.terrill at ericsson.com; onap-tsc at lists.onap.org Subject: Re: [onap-tsc] Charter My preference is "Technical Steering Committee Charter" to be consistent with the TSC name. "Technical Community Charter" can lead to confusions, as the charter itself is really about TSC's structures and roles. Ning From: onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Stephen Terrill Sent: Monday, April 10, 2017 1:36 PM To: onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org> Subject: [onap-tsc] Charter Hi All, In the F2F TSC regarding the charter, there as an item that we should take to the mailing list. Charter name: Should we call the charter "Technical Steering Committee Charter" or "Technical Community Charter". Note: The second option puts the emphasis on the community and the TSC is helping to ensure the operations for the community. Please, opinions welcome as we are drafting the updates during this week. Best Regards, Steve. [Ericsson]<http://www.ericsson.com/> STEPHEN TERRILL Technology Specialist DUIC, Systems and Technology Development Unit IP & Cloud Business Unit, IT & Cloud Products Ericsson Ericsson R&D Center, via de los Poblados 13 28033, Madrid, Spain Phone +34 339 3005 Mobile +34 609 168 515 Stephen.Terrill at ericsson.com<mailto:Stephen.Terrill at ericsson.com> www.ericsson.com<http://www.ericsson.com> [http://www.ericsson.com/current_campaign]<http://www.ericsson.com/current_campaign> Legal entity: Ericsson Espa?a S.A, compay registration number ESA288568603. This Communication is Confidential. We only send and receive email on the basis of the terms set out at www.ericsson.com/email_disclaimer<http://www.ericsson.com/email_disclaimer> "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential and may be privileged. If you are not the intended recipient, you are hereby notified that any review, re-transmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment." 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <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/20170410/9d661b15/attachment-0001.html> -- next part -- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 4909 bytes Desc: image001.png URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170410/9d661b15/attachment-0001.png> -- next part -- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 7337 bytes Desc: image002.jpg URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170410/9d661b15/attachment-0001.jpg>
