You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Introduction

Although the PoC will only implement a few of the possible Java API methods it is important to have a good detailed view of the structure and naming of this interface going forward and document it.

Acceptance Criteria for Proposed Java Interface:

  1. Should follow ONAP or wider best practice
  2. Documented on ONAP Wiki
  3. Discussed and agreed within CPS Team
  4. Discussed and agreed with wider community


Currently we are considering 3 'separated' Java APIs or 'groups' of methods:

  1. Models (add, list)
  2. Data (CRUD)
  3. Queries

Jira Ticket:

CCSDK-2871 - Getting issue details... STATUS

Jira Backlog:

https://jira.onap.org/secure/RapidBoard.jspa?rapidView=223&view=planning.nodetail&selectedIssue=CCSDK-2912&issueLimit=100


Open Issues/Decisions

#

Description

Details

Decisions

1Should the java interface take in objects(like REST interface) or a few individual fields in a signature?



CPS provides the following interfaces:

Interface Name

Interface Definition

 Interface Capabilities

Consumed Models

Model InterfaceBehavior interface that provides the capability to access cps modules.
  • Create a module set
  • Read all modules
  • Validate the yang models
Yang models that are broken into fragments.
Data Interface

Behavior interface that represents CPS data.

  • Create a (root) node.
  • Delete a dataspace
  • Read an anchor
  • Read all anchors
  • Delete an anchor
  • Create a dataspace
  • Create an anchor point
  • Link a dataspace to an anchor?
  • Link a node to an anchor?

Query InterfaceProvides the capability to query CPS data.
  • Read a node.
  • Read all nodes.


  • No labels