CPS-352 : Create yang-model for DMI-registry data

Addresses: CPS-352 - Getting issue details... STATUS

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.

Alternative 2 is suggested

Simplicity
Can be migrated to alternative 1 if needed
Unlikely Additional fields are ever required (the can be stored per cmHandle instead)

Yang Model

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";
  }

  container dmi-registry {

    list cm-handle {

      key "id";

      leaf id {
        type string;
      }

      leaf dmi-service-name {
        type string;
      }

      list additional-properties {

        key "name";

        leaf name {
          type string;
        }

        leaf value {
          type string;
        }
      }
    }
  }
}

Update October 2021

CPS-736 - Getting issue details... STATUS

Added dmi-data-service-name & dmi-model-service-name to allow separate DMI instances for each responsibility

October 2021 Updated Yang Model

module dmi-registry {

  yang-version 1.1;

  namespace "org:onap:cps:ncmp";

  prefix dmi-reg;

  revision "2021-10-20" {
    description
    "Added dmi-data-service-name & dmi-model-service-name to allow separate DMI instances for each responsabilty";
   }

  revision "2021-05-20" {
    description
    "Initial Version";
  }

  container dmi-registry {

    list cm-handles {

      key "id";

      leaf id {
        type string;
      }

      leaf dmi-service-name {
        type string;
      }

      leaf dmi-data-service-name {
        type string;
      }

      leaf dmi-model-service-name {
        type string;
      }

      list additional-properties {

        key "name";

        leaf name {
          type string;
        }

        leaf value {
          type string;
        }
      }
    }
  }
}