Page Comparison

...

Pictorial representation of Distributed KV Store with consuming services:

API Reference for the KV store:

View file

name	Distributed KV Store API reference.pdf
height	250

Scope:

Functionality :

Ability to store configuration settings using reliable and distributed KV storage systems.
Ability to provide leadership election among micro services.
Ability to provide semaphore across service instances of ONAP services.
Ability to modify the configuration settings
Ability to inform active ONAP services of configuration changes.
Ability to read the changed configuration
config-seed micro service to load default values of configuration settings, if settings are not present in the distributed KV storage.
Bootstrap phase functionality where each service upon startup reads the configuration settings from distribtued KV storage.

...

Distributed KV Store : https://github.com/hashicorp/consul
configuration-seed : https://github.com/edgexfoundry/core-config-seed (But suggest to implement this in golang, ideas can be taken from this project).

Link to tests:

...

.

...

Key Project Facts:

Primary contact : Srinivasa Addepalli, Shashank Kumar Shankar

Facts	Info
PTL (first and last name)
Jira Project Name	MUSIC
Jira Key	MUSIC
Project ID	org.onap.music.distributed-kv-store
Link to Wiki Space	Distributed KV Store (MUSIC sub-project)

Release Components Name:

Note: refer to existing project for details on how to fill out this table

...

Note 2: It is critical to complete all the information requested, that will help to fast forward the onboarding process.

Practice AreaCheckpointYes/NoEvidence - CommentHow to?Product Management

Are all provisional APIs interface (stub) been defined (at beta-quality level)?

Yeshttps://git.onap.org/music/distributed-kv-store/tree/swagger.jsonIs there a final list of externally consumable APIs available?Yeshttps://git.onap.org/music/distributed-kv-store/tree/swagger.json

For all completed Sprints, have Sprint Backlog Stories been marked as "Done" in Jira?

Yes

https://jira.onap.org/secure/RapidBoard.jspa?rapidView=113&view=detail&selectedIssue=MUSIC-9&quickFilter=273

Are all tasks associated with the completed Sprint Backlog Stories been marked as "Done" in Jira?

Yeshttps://jira.onap.org/secure/RapidBoard.jspa?rapidView=113&view=detail&selectedIssue=MUSIC-9&quickFilter=273If applicable to your project, has your team been able to clear the project' blockers? If not provide status on the plan to close the blocker(s).Yeshttps://jenkins.onap.org/view/music/job/music-distributed-kv-store-master-verify-golang/What new features or changes to existing features in this project scope need to be communicated to VNF Providers? List the changes in the Evidence tab.NAIf yes to the previous question, have these been communicated to the VNF Requirements project? NARelease Management
Have all source code files been updated with License Apache 2 header?YesSpecific rules and instruction are available in ONAP wiki.Has the year format in copyright header of all source code files been updated? (Rules for new files created in 2018 and existing files modified in 2018 are different)NAGuidance on year formatIn case source code can't be edited, has a "License.txt" file been placed at the root directory for which the license is applicable?NAGuidance for source code file that can't be edited(a) Has the Project Team added appropriate license and copyright notices to all ONAP source code and documentation files, where possible for the particular file format?Yes(b) Has the Project Team reviewed and understood the most recent license scan reports from the LF, for both (a) licenses within the codebase and (b) licenses for third-party build time dependencies?YesFor both (a) and (b) questions, have all high priority non-Project Licenses been either removed, planned for removal before code freeze, or escalated as likely exception requests?Yes

Have all API projects dependencies been captured?

Yes