...
| Name | Interface | Description | Parameters | Return |
|---|---|---|---|---|
| Add model | CPS-E-01 | Add a YANG model to the CPS so that compliant data may be stored & retrieved |
| Some identifier |
| Remove model | CPS-E-01 | Mark a model for removal, and remove when no data remains that relies on the model |
| Success/Number of model instances still using model |
| Upgrade model | CPS-E-01 | T.B.D |
| - |
| Create model instance | CPS-E-02 | Prepare the underlying DB for the storage of data compliant to the model. |
| Model instance identifier |
| Delete model instance | CPS-E-02 | Remove the data and any artifacts from the underlying DB |
| Success/Failure |
| Create data | CPS-E-02 | [Validate &] Store data compliant to a model |
| Success/Failure |
| Replace data | CPS-E-02 | [Validate &] Store data compliant to a model in place of existing data |
| Success/Failure |
| Update data | CPS-E-02 | [Validate &] Update data that is (1) compliant to a model and (2) already stored |
| Success/Failure |
| Delete data | CPS-E-02 | Remove data from a model instance |
| Success/Failure |
| Data change notification | CPS-E-03 | Notify interested parties that data (marked as interesting by the model) has been modified |
| - |
Service Provider Interface (SPI)
T.B.D. An internal interface that defines how the CPS Core will interact with the DBMS. The design of the SPI will be informed by agreed CPS behavior and minimum requirements for the DBMS.
The SPI is required to ensure that different DB technologies can be used in different deployments.
Behavior
T.B.D.: Eventual consistency; Data integrity guarantees; Fast failure; Progress; Cancellation;
...