We’ll be talking about this on Monday. Jason Hunt is conducting a survey of where each component is along the S3P continuum. The goal of Beijing will be to improve on where we are, not necessarily to target a set level across the board. Aiming for a fixed target would jeopardize our six-month cadence, and a one-size fits all approach won’t fit all projects. For example, VNFSDK will get the biggest gain focusing on security and not scalability, whereas run-time components might want to focus more on resiliency or scalability.
We have been discussing some top-down solutions such as HA/geo-redundancy, too. We’ll see some new project proposals along those lines next week. Chris From: [email protected] [mailto:[email protected]] On Behalf Of Yunxia Chen Sent: Wednesday, December 06, 2017 9:16 PM To: Alla Goldner <[email protected]>; [email protected]; [email protected]; [email protected]; Philip Robb <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; Seshu m <[email protected]>; [email protected]; Eman Gil <[email protected]>; Casey Cain <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]; Mark Pond <[email protected]>; [email protected]; [email protected]; [email protected]; Kanagaraj Manickam <[email protected]>; [email protected]; [email protected]; [email protected]; denghui (L) <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; Gildas Lanilis <[email protected]>; [email protected] Subject: Re: [onap-tsc] Next week f2f meeting Hi, Alla & Chris, Another topic I suggest that we could discuss among Arch, Usecase and Integration, with the input from all other projects, is related to “carrier grade” requirement: 1. What’s the priority? (I really appreciate the material Lee presented in Arch meeting this Tuesday regarding the requirement from AT&T operational point of view) 2. What’s the benchmark? What’s our goal for Beijing? 3. Top down software solution for this? 4. Solutions in each project? 5. Tools? 6. Etc. And identify the responsibilities for execution, maybe let a small group of people to drive it. Regards, Helen Chen From: Alla Goldner <[email protected]<mailto:[email protected]>> Date: Monday, December 4, 2017 at 12:31 PM To: Kenny Paul <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, Dan Timoney <[email protected]<mailto:[email protected]>>, Phil Robb <[email protected]<mailto:[email protected]>>, Helen Chen 00725961 <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, Ram Koya <[email protected]<mailto:[email protected]>>, Seshu m <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "GILBERT, MAZIN E (MAZIN E)" <[email protected]<mailto:[email protected]>>, Casey Cain <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, Jimmy Forsyth <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, Mark Pond <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, LUSHENG JI <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, Kanagaraj Manickam <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, onap-tsc <[email protected]<mailto:[email protected]>>, "denghui (L)" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, Steven Wright <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, Amichai Hemli <[email protected]<mailto:[email protected]>>, Gildas Lanilis <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Cc: "GILBERT, MAZIN E (MAZIN E)" <[email protected]<mailto:[email protected]>> Subject: Next week f2f meeting Dear Chris, Helen, Hui Deng, PTLs, We will have Usecase subcommittee meeting next Wednesday, during the f2f meeting. There are 2 major objectives: 1. To discuss, along with the Integration team, our next steps in working on Beijing requirements, how we test and showcase those, responsibilities etc. 2. Gather inputs from the different PTLs on what they expect us to do during Beijing. We discussed it today during our regular call today with Helen, and we would like to invite Architecture and modelling subcommittees representatives also to this meeting, along with PTLs, to be able to gather all feedbacks and get maximal efficiency. Inputs provided in advance are more than welcomed, of course. What do you think? Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:[email protected]] 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 [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
