Addresses:
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | CPS-352 |
|---|
|
PLease note further update on CPS-872 CM Handle State: define and agree new dmi-registry yang model supporting States
Problem description
Yang model need to be created in CPS to persist relationship between DMI-plugin and CM-handle. Also, DMI-plugin connection data and additional parameters needed to be persisted.
Under this ticket, we need to create yang-model for above statements and persist that into cps repository.
Proposal
Please find below yang-model for above problem, also a new dataspace will be added named dmi-registry. Using liquibase db changes will be done.
...
- Simplicity
- Can be migrated to alternative 1 if needed
- Unlikely Addiotnal Additional fields are ever required (the can be stored per cmHandle instead)
| Code Block |
|---|
| theme | Emacs |
|---|
| title | Yang Model |
|---|
| linenumbers | true |
|---|
| collapse | true |
|---|
|
module dmi-registry {
yang-version 1.1;
namespace "org:onap:cps:ncmp";
prefix dmi-reg;
organization "Ericsson Software Tech.";
contact "rahul.tyagi@est.tech";
revision "2021-05-20" {
description
"Initial Version";
}
groupingcontainer targetdmi-registry {
leaflist addresscm-handle {
typekey string;"id";
leaf id {
description "Target IPtype address"string;
}
} containerleaf dmi-service-registryname {
type string;
}
list cmadditional-handleproperties {
key "idname";
leaf idname {
type string;
}
leaf namevalue {
type string;
}
leaf dmi-plugin}
}
}
}
|
Update October 2021
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | CPS-736 |
|---|
|
Added dmi-data-service-name & dmi-model-service-name to allow separate DMI instances for each responsibility
| Code Block |
|---|
| theme | Emacs |
|---|
| title | October 2021 Updated Yang Model |
|---|
| linenumbers | true |
|---|
| collapse | true |
|---|
|
module dmi-registry {
yang-version 1.1;
type leafref {
namespace "org:onap:cps:ncmp";
prefix dmi-reg;
revision "2021-10-20" {
description
path "/Added dmi-registry/dmi-plugin/iddata-service-name & dmi-model-service-name to allow separate DMI instances for each responsibility";
}
}revision "2021-05-20" {
description
"Initial Version";
}
container dmi-registry {
list additionalcm-propertieshandles {
key "name";
id";
leaf id {
type string;
}
leaf dmi-service-name {
type string;
}
}
leaf dmi-data-service-name {
leaf valuetype {string;
}
type string; leaf dmi-model-service-name {
} type string;
} }
list dmiadditional-pluginproperties {
key "idname";
leaf idname {
type string;
}
leaf namevalue {
type string;
} }
uses target;}
}
}
}
|