In release requirements page:

Frankfurt Release Requirements (TSC has already approved Green status for M1 U/C).

RTCfgDB U/C is

CCSDK, SDN-C - Dan Timoney MVP (min viab. product) discussed on SDN-C call. Req not totally clear, schema model. Take what is in ConfigDB; finalize the Data Model approach.

MEETING HELD 14 Nov 2019  - Yuriy Malakov Vimal Begwani Benjamin Cheung Joanne Liu Rudel  - discuss way forward, regarding the TSC M1 Score card problem 

08 Nov 2019 CCSDK, 06 Nov 2019 SDN-C call - ConfigDB is already part of DBaaS. Req not finalized. Data model already in use. and API creation. During the SDNC CCSDK weekly call.

Email from Dan Timoney 14 Nov 2019 

My understanding from Sandeep was that this work was very much a stretch for Frankfurt.  So, I’m okay with work starting in Frankfurt, as long as its structured so that it’s a separable component (i.e. as long as, if it’s not completed in Frankfurt, the platform is not fundamentally broken). I would NOT support creating a separate repository, since there is a fair amount of overhead involved in maintaining each repository on an ongoing basis – both machine and human resources.  The Linux Foundation itself has been pushing back on the number of repositories the ONAP projects have and there is now a new approval process needed in order to add new ones.  If a new repository is needed, then this team will need to convince me why no existing repository can be used AND will need to provide a resource who is willing to maintain that repository (i.e dealing with security vulnerabilities; policing code coverage ; doing release builds, etc).

•  ACTION: 10 Jan 2020 for Sandeep Shah / API Documentation - freeze, the schema for the RunTime DB needs to be defined. Sandeep Shah has indicated it is ready. Need to see code to that effect. Should be documented somewhere.
•  

  Status
  colour Yellow title YELLOW

  Stretch goal for CCSDK, SDN-C. How do we answer the TSC query - The team is saying we are going to do this, for the TSC purposes we can remove the stretch goal. ACTION: State that: Want SDKs in CCSDK to do a code drop a M3, Runtime DB wouldn't be part of that since it is new, we'll have code ready by M4, but not by API freeze. That should be ok because we don't have external dependencies. M2/M3 deliverables tracking in Jira need to document that we will document at Code Freeze M4. This is the Jira I was referring to re: early delivery of CCSDK -

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CCSDK-1963

  I added a comment to that Jira indicating that Runtime Config DB will not be part of early drop, but rather will be delivered at M4
  

Project as part of CCSDK

•  ACTION: Sandeep Shah Presentation of new architecture with CCSDK.
•  ACTION: 10 Jan 2020 Architecture Wiki for CCSDK to include the component. ARC Controller Component Description – Frankfurt added in Section 6 System deployment architecture. Separate container. Added to Diagram. Updated Section 7 New Release Capabilities & Linked to U/C page.