Hi Alla, Thanks for putting this together.
Regarding support to ONAP reliability, I generally agree with your comment below: An instance of the complete "ONAP platform shall be configurable to be part of an "N+1" group of instances that operate in a specific, coordinated, controlled fail-over manner. This coordinated fail-over manner enables the operator to select an "the idle +1" instance in the group to functionally replace any of the operating, healthy, "N" instances of the group on demand, within a specified amount of time. This approach shall be used as a common method for surviving disaster, and also, the common approach to software upgrade distribution. I would complement it saying that failover doesn’t necessarily need to be always controlled. For example, if a component fails in the middle of a workflow, ONAP should be able to switch to another available instance of that component so as to terminate operations correctly, without involving humans in the loop. Situations like this happens all the time, it would be good to have automated solutions that would make ONAP more robust. Thanks, Marco From: <onap-tsc-boun...@lists.onap.org> on behalf of Alla Goldner <alla.gold...@amdocs.com> Date: Wednesday, September 20, 2017 at 5:39 AM To: "onap-tsc@lists.onap.org P" <onap-tsc@lists.onap.org>, "onap-disc...@lists.onap.org" <onap-disc...@lists.onap.org> Subject: [onap-tsc] R2 preparations: functional and non-functional requirements candidates Hi all, Here is the status of functional and non-functional requirements candidates for Beijing Release: 1. Table with merged functional requirements candidates: https://wiki.onap.org/display/DW/Merged+list+of+R2+functional+requirement+candidates<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Merged-2Blist-2Bof-2BR2-2Bfunctional-2Brequirement-2Bcandidates&d=DwMFJg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jlLKoKKs6km8ARBnZy1My5vXHRIGDT6Kk6WEzjo60eI&s=5u8vuUWEtx3FwX6-Hg1C1JQoqRXQbnTOYHAXx-AR2IQ&e=> 2. Non-functional requirements candidates https://wiki.onap.org/display/DW/R2+proposals+for+Non-functional+requirements<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_R2-2Bproposals-2Bfor-2BNon-2Dfunctional-2Brequirements&d=DwMFJg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jlLKoKKs6km8ARBnZy1My5vXHRIGDT6Kk6WEzjo60eI&s=yU9hoMDe5EtWyooGQ7UlxOwK76Hrfdc4UDwnL0GdNKU&e=> And…Chag Sameach and Shana Tova to all our Jewish colleagues! [ShanaTova from #Jewish Treats! #Ros] Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image002.png@01D331F0.469AD2A0] From: Alla Goldner Sent: Tuesday, September 19, 2017 5:21 PM To: 'onap-usecase...@lists.onap.org' <onap-usecase...@lists.onap.org> Cc: 'Kenny Paul' <kp...@linuxfoundation.org>; 'GILBERT, MAZIN E (MAZIN E)' <ma...@research.att.com>; Yoav Kluger <yoav.klu...@amdocs.com>; Andrei Kojukhov <andrei.kojuk...@amdocs.com>; 'onap-...@lists.onap.org' <onap-...@lists.onap.org> Subject: RE: Usecase subcommittee meeting 18/09/2017 - the summary Hi all, Please see table with merged requirements here: https://wiki.onap.org/display/DW/Merged+list+of+R2+functional+requirement+candidates<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Merged-2Blist-2Bof-2BR2-2Bfunctional-2Brequirement-2Bcandidates&d=DwMFJg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jlLKoKKs6km8ARBnZy1My5vXHRIGDT6Kk6WEzjo60eI&s=5u8vuUWEtx3FwX6-Hg1C1JQoqRXQbnTOYHAXx-AR2IQ&e=> 1. I marked all pages previously used for gathering of R2 functional requirements as OBSOLETE, as we want to have a single source now and update it accordingly Note: Non-functional requirement proposals for R2 remain untouched https://wiki.onap.org/display/DW/R2+proposals+for+Non-functional+requirements<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_R2-2Bproposals-2Bfor-2BNon-2Dfunctional-2Brequirements&d=DwMFJg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jlLKoKKs6km8ARBnZy1My5vXHRIGDT6Kk6WEzjo60eI&s=yU9hoMDe5EtWyooGQ7UlxOwK76Hrfdc4UDwnL0GdNKU&e=> 2. We (Alla, Yoav, Andrei) gathered all requirements into a single table with the information previously provided by the requirements authors, while adding on top of it: a. Agreed priority for R2 – this is something to be agreed by the whole group (empty for now) b. Proposed grouping/harmonization – this is our initial proposal of how those requirements may be grouped and this may be used for further requirements harmonization c. Proposed ownership – would be beneficial if each group/requirement gets under responsibility of a project (if it is a single project related) or person (i.e. proceeding with that group in the same way as was done with the specific use cases in R1) (empty for now) The AI are: 1. Requirements authors – please double check all initial information is present 2. Requirements authors – please introduce summary/link to some detail requirement description in case it is missing. This is needed 3. All – please review and provide your comments and suggestions for modifications/next step of our discussions, concentrating mostly on requirements harmonization/importance/relevancy for R2 goal of making ONAP Platform more stable 4. Luman – please extend this table with E-vCPE additional requirements as discussed yesterday Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image002.png@01D331F0.469AD2A0] From: Alla Goldner Sent: Monday, September 18, 2017 10:22 PM To: 'onap-usecase...@lists.onap.org' <onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>> Cc: 'Kenny Paul' <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>>; 'GILBERT, MAZIN E (MAZIN E)' <ma...@research.att.com<mailto:ma...@research.att.com>> Subject: Usecase subcommittee meeting 18/09/2017 - the summary Hi all, Thanks to all meeting’s attendants! Here is the summary: 1. All R2 use cases were updated with the list of their corresponding functional requirements – thanks a lot to the authors!!! Some of the requirements still need more explanation to be added though 2. Alla will merge all functional requirements into a single table by 19/09/2017, then we will work with it for: a. Removal of the same requirement appearing multiple times/extension of one requirement by functional modifications coming from another one b. Making a requirements generic i. We must target generic platform requirements (e.g. E-vCPE service onboarding, SDWAN service onboarding requirements transform to some generic onboarding functional requirement which is not supported by R1) c. Prioritization proposal of a different requirements for R2 3. Then, Luman will also add additional E-vCPE requirements discussed during the call to this table 4. Alla will check whether zoom connection is possible during next week meeting 5. Alex will check with Chris whether R2 architecture requirements will be included to guide us while prioritizing those functional requirements https://wiki.onap.org/display/DW/Architecture+Requirements+for+R2+use+cases<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Architecture-2BRequirements-2Bfor-2BR2-2Buse-2Bcases&d=DwMFJg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jlLKoKKs6km8ARBnZy1My5vXHRIGDT6Kk6WEzjo60eI&s=kykh0TcKioqaXdbpu_zSq0O4FmKjggJthzQvL5eNdmc&e=> 6. One of the action items to discuss during the next week joint meeting with the Architecture subcommittee is NAI/PCE coming from E-vCPE use case (in case Luman will be able to connect by zoom) 7. Non-functional requirements will be discussed jointly by the whole TSC (interested people) next week https://wiki.onap.org/display/DW/R2+proposals+for+Non-functional+requirements<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_R2-2Bproposals-2Bfor-2BNon-2Dfunctional-2Brequirements&d=DwMFJg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jlLKoKKs6km8ARBnZy1My5vXHRIGDT6Kk6WEzjo60eI&s=yU9hoMDe5EtWyooGQ7UlxOwK76Hrfdc4UDwnL0GdNKU&e=> Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image002.png@01D331F0.469AD2A0] From: Alla Goldner Sent: Thursday, September 14, 2017 11:58 AM To: 'onap-usecase...@lists.onap.org' <onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>> Cc: 'GILBERT, MAZIN E (MAZIN E)' <ma...@research.att.com<mailto:ma...@research.att.com>>; Yoav Kluger <yoav.klu...@amdocs.com<mailto:yoav.klu...@amdocs.com>>; Kang Xi <kang...@huawei.com<mailto:kang...@huawei.com>>; 'wangchen...@chinamobile.com' <wangchen...@chinamobile.com<mailto:wangchen...@chinamobile.com>>; 'Yang Xu (Yang, Fixed Network)' <yang....@huawei.com<mailto:yang....@huawei.com>>; 'emau...@research.att.com' <emau...@research.att.com<mailto:emau...@research.att.com>>; Long Wan <lw2...@nyu.edu<mailto:lw2...@nyu.edu>>; '王路曼' <wanglm....@chinatelecom.cn<mailto:wanglm....@chinatelecom.cn>>; Ievgen Zhukov <evgeniy.zhu...@netcracker.com<mailto:evgeniy.zhu...@netcracker.com>> Subject: Usecase subcommittee meeting 18/09/2017 - the agenda Hi all, Here is agenda for the next meeting. I am distributing it in advance, since this is the last meeting before our f2f meeting, and it is important to prepare all material towards it. 1. R1 use cases: Status and actions, required from Usecase subcommittee (vCPE, vVoLTE) (10 min) 2. R2 use cases status and progress of 3 R2 requirements categories (not supported by R1, new for R2, non-functional) (50 min) (for your reference, the status is below) a. Non-functional requirements category – was recently significantly extended and this work continues https://wiki.onap.org/display/DW/R2+proposals+for+Non-functional+requirements<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_R2-2Bproposals-2Bfor-2BNon-2Dfunctional-2Brequirements&d=DwMFJg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jlLKoKKs6km8ARBnZy1My5vXHRIGDT6Kk6WEzjo60eI&s=yU9hoMDe5EtWyooGQ7UlxOwK76Hrfdc4UDwnL0GdNKU&e=> b. R1 missing Platform capabilities. This lists requires more work https://wiki.onap.org/display/DW/Missing+Platform+capabilities<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Missing-2BPlatform-2Bcapabilities&d=DwMFJg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jlLKoKKs6km8ARBnZy1My5vXHRIGDT6Kk6WEzjo60eI&s=t0vVdegMi8TW10IuQ0lXsHASAsoj7VqaR9laZ_wNcxw&e=> . Use cases (R-vCPE, vVoLTE) said they will be able to extend/work on this list till the next week meeting c. R2 new requirements extracted from the new use cases proposals https://wiki.onap.org/pages/viewpage.action?pageId=13599574<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D13599574&d=DwMFJg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jlLKoKKs6km8ARBnZy1My5vXHRIGDT6Kk6WEzjo60eI&s=HvhB0fhRUAx46oIcLsZba1urb34wRYpzcgzChpHPYEc&e=> i. 5G task force has added table consisting of those requirements https://wiki.onap.org/display/DW/Summary+of+Functional+Platform+Requirements+arising+from+5G+Use+Case<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Summary-2Bof-2BFunctional-2BPlatform-2BRequirements-2Barising-2Bfrom-2B5G-2BUse-2BCase&d=DwMFJg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jlLKoKKs6km8ARBnZy1My5vXHRIGDT6Kk6WEzjo60eI&s=Y8GwijA9qgZEIh8p5lXWN0YfLqDeT2jmCyEDq1-UEi4&e=> ii. SD-WAN/Enterprise vCPE and ONAP Change Management task forces are committed to do the same till the next week meeting Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image002.png@01D331F0.469AD2A0] 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=DwMFJg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jlLKoKKs6km8ARBnZy1My5vXHRIGDT6Kk6WEzjo60eI&s=hZFdrBdzDsIhapNFWCAfmQvATt5PKWl1PH93n9ugPyU&e=>
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
