Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

NAMEGERRIT IDCOMPANYEMAILTIME ZONE
Toine SiebelinkToine SiebelinkEricssontoine.siebelink@est.techUTC+1Sandeep Shah
IBMTony FinnertyEricssontony.finnerty@ericsson.comUTC+1
Theodore Johnsontheodore johnsonAT&Tjohnsont@research.att.comUTC-4
Rishi ChailEricssonrishi.chail@est.techUTC+1
Niamh CoreNiamh CoreEricssonniamh.core@est.techUTC+1
Aditya PuthuparambilBell Canadaaditya.puthuparambil@bell.caUTC+1
Bruno Sakotouser-4e793Bell Canadabruno.sakoto@bell.caUTC-5










...

(Names and affiliations of any other contributors)

NAMEGERRIT IDCOMPANYEMAILTIME ZONE
Benjamin CheungBenjamin CheungNokiaben.cheung@nokia.comUTC-4
N. K. ShankarN.K. ShankaranarayananAT&Tshankar@research.att.comUTC-4
Marcin KrasowskiMarcin Sebastian KrasowskiSamsungm.krasowski@samsung.comUTC+2
Pawel SlowikowskiSamsungp.slowikows2@samsung.comUTC+2
Krystian Kedronuser-7f92dSamsungk.kedron@partner.samsung.comUTC+2
Carlos ManzanaresCarlos ManzanaresNokiaCarlos.Manzanares@nokia.comUTC+3
Fred FeisullinFred FeisullinVerizon WirelessFred.Feisullin@Verizon.comUTC-4
Sandeep ShahSandeep Shah IBMSandeep.Shah@ibm.com
Philippe Leger

Philippe Leger

BellPhilippe.Leger1@bell.caUTC-4














Other Contact People:

...

Next StepDescriptionResponse
1

1A. Name of the project is appropriate (no trademark issues etc.);



1B. Proposed repository name is all lower-case without any special characters

Official Name of the project will be CONFIGURATION PERSISTENCE SERVICE

Apache Geode is also using CPS, but it is not trademarked. Geode CPS

2Project contact name, company and email are defined and documented
3Description of the project goal and its purpose are definedThe goal and purpose are on the project proposal: Configuration Persistence Service Project Proposal (Oct 25 2019) 71834220
4Scope and project plan are well definedThe scope is defined in the project proposal: Configuration Persistence Service Project Proposal (Oct 25 2019) 71834220
5Resources committed and available (company commitments, all people)

These can be found here: Configuration Persistence Service Project Proposal (Oct 25 2019) 71834220

Repo TBD

6Contributors identified (people who add code) +2

These can be found here: Configuration Persistence Service Project Proposal (Oct 25 2019) 71834220

7Initial list of committer identified (elected/proposed by initial contributors) +1

These can be found here: Configuration Persistence Service Project Proposal (Oct 25 2019) 71834220

8Meets ONAP TSC Policies (NFR, GR, Code review, Testing, Audits, Documenting Interface)The C&PS team intends to follow all ONAP TSC Policies.
9Proposal has been socialized with potentially interested or affected projects (e.g. AAI, CDS, SO) and/or parties

TSC - TSC 2020-10-01

Requirement S/C - ONAP R8 Modeling High Level Requirements

Architecture S/C -

Modeling S/C - ONAP R7 Resource IM Call 2020-9-21

E2E Network Slicing (Requirements/Use Cases)

SON PCI (Requirement/Use Cases)

10Cross Project Dependencies (XPDs). In the case where a project will require changes in other projects, those projects are listed in the proposal, and a sponsoring developer in the project has been identified

There are no changes required upon other ONAP Platform component projects.

11

Tools have been identified and discussed with relevant partners (Linux Foundation, IT). Once the project pass the review:

  1. the tools chain must be  created within one week.
  2. Tools encompass Configuration Management, CI-CD,
  3. Code Review,
  4. Testing,
  5. Team Wiki,
  6. End Users documentation (not exhaustive)

1. Tool Chain: (action)

2. Tools: (action)

3. Code Review: using Gerrit for Code Review.

4. Testing: unit, integration test will be part of the developer work; ONAP goal for 55% testing code coverage. Will be using SonarQube.

5. Project Page: Configuration & Persistency Service R7

Developer page: Configuration & Persistency Service PoC
6. Documentation: (RST files will be in the CPS repo)

...