Page History

Each component contains its own docker-compose file listing all the services required for the integration test. Eg : cps-temporal docker-compose would have services  from cps-temporal as well as cps-core

As all the services are included in the docker-compose of cps-temporal, CSIT test setup could directly trigger :

      docker-compose up

• Faster implementation

• Every change made in a single service would have to be duplicated in all the other files where the same service is used like addition of new environment variables.
• Harder to maintain

As cps-temporal is a client using cps-core, include steps to fetch the docker-compose of cps-core in the cps-temporal setup.sh file in CSIT as shown below:

      git clone https://github.com/onap/cps.git

Combine the docker-compose of cps-temporal and cps while executing 'docker-compose up' 

     docker-compose -f docker-compose.yml -f ../cps/docker-compose/docker-compose.yml up

Subsequent files override and add to their predecessors. For the CSIT test cps-temporal docker-compose could override the properties specified in cps-core docker-compose.

Eg : if the notification.data-updated.enabled=false by default in cps-core docker-compose. By adding the below code in cps-temporal, these values could be overriden

cps-and-ncmp:
   notification.data-updated.enabled: 'true'

• No need for code replication.
• docker-compose files specific to each component

• Cloning the dependent repo

• The configuration to run a test does not belong to the test itself anymore as it stays in another repo. 

Eg: cps-temporal CSIT would combine the docker-compose of cps-temporal and cps-core while executing 'docker-compose up' as below :

     docker-compose -f docker-compose.yml -f ../cps/docker-compose.yml up

• No need to replicate the docker-compose
• docker-compose files specific to each component maintained in different sub modules
• No cloning required for the dependent repo to run CSIT

• ci-management jobs will have to be created, hence time consuming for now
• Manageability of an additional repo .

1. Test Liveness Probe Endpoint
2. Test Readiness Probe Endpoint

CPS Admin Details Insert

1. Create Dataspace 
2. Create schema set from YANG file
3. Create Schema set with Zip file
4. Get schema set info
5. Create anchor
6. Get Anchor

To Be Updated

Get Anchor test to be included in the existing test.

1. Create Data Node for an anchor
2. Get Datanode by the dataspace, anchor and xpath
3. Update data node
4. Get Datanode by query

Done

1. Test Liveness Probe Endpoint
2. Test Readiness Probe Endpoint

1. Create Data Node using cps api 
2. Update the Data Node using cps api
3. Get the history of the anchor using cps-temporal api 

   /v1/dataspaces/{dataspace-name}/anchors/{anchor-name}/history

1. Test Liveness Probe Endpoint
2. Test Readiness Probe Endpoint

Model-Sync, Write & read data using datastore PassTrough

1. Create Data Node using cps api 
2. Notify NCMP DMI has new node 
   1. http://localhost:8783/dmi/api/v1/inventory/cmHandles
   2. This will kick off model sync as part of registation
3. wait till above method call completes and send a 2xx response
4. Use CPS endpoint that shows anchors & namespaces to conclude test completed