...
Pictorial representation of Distributed KV Store with consuming services:
API Reference for the KV store:
| View file | ||||
|---|---|---|---|---|
|
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:
https://git.onap.org/music/distributed-kv-store/tree/src/dkv/api/endpointViews_test.go
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
...
Role | First Name Last Name | Linux Foundation ID | Email Address | Location |
|---|---|---|---|---|
| PTL | Shashank Kumar Shankar | shashank.kumar.shankar | shashank.kumar.shankar@intel.com | Portland, OR |
| Committers | Shashank Kumar Shankar | shashank.kumar.shankar | shashank.kumar.shankar@intel.com | Portland, OR |
| Contributors | ||||
Tracking Milestones:
https://wiki.onap.org/display/DW/Tracking+Milestones
API Reference:
https://git.onap.org/music/distributed-kv-store/tree/swagger.yaml
| View file | ||||
|---|---|---|---|---|
|
Testing and Integration:
The following type of tests are done in this release:
- Unit tests: Currently has around 50% unit test coverage as evidenced in the logs for the latest build: https://jenkins.onap.org/view/music/job/music-distributed-kv-store-master-merge-golang/lastBuild/consoleText
- Functional Test
...
- cases: Functional Tests run in CSIT tests.
Example test case: https://git.onap.org/music/distributed-kv-store/tree/src/dkv/api/configHandlers_test.go
Generate Code Coverage Report of source code for Golang applications:
$ go test -coverprofile=coverage.out$ go tool cover -html=coverage.out