Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
stylesquare

References

Open Issues/Questions

Issue/QuestionDescriptionNotesResolution
new model
  • module name for the model that holds the augment statement


new module name = extended-dmi-registry

prefix = ext-dmi

Loading data with Liquibase

Dmi registry model is loaded via Liquibase which means that the content of the yang resource is already set 

  • will the new model need to be loaded 
  • how will the 'import' statement work to create a new model

New JIRA ticket created for this

see

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-1183
 

ODL Yang tool

what is needed to acknowledge the augment statement for a new model

  • the new model will contain a prefix of the module name

Overview

Currently, the published DMI-registry model shows the property 'additional properties' as shown on lines 32 to line 43 of the yang model below. This property is not queryable and therefore, is not recommended to be published to the public.

...

Successful Parsing of the models [dmi-registry-sample, extended-dmi-registry]



DescriptionNotes and Results
1Create Dataspacedataspace 'my-dataspace' created
  • dataspace table

Image Modified

2

Create schemaset with Zip File resource


201 created

'my-schema-set-2'

  • schema_set table

Image Modified


  • schema_set_yang_resources table

Image Modified


  • yang_resource table

Image Modified

3

Create Anchor

    • schema-set-name: my-schema-set-2

201 created

'my-anchor'

  • anchor table

Image Modified

4

Create Node

201 created

Image Modified

5

Get a schemaset

    • dataspace-name: my-dataspace
    • schema-set-name: my-schema-set-2
200

Image Modified

Open Issues/Questions

prefix is ignored by the yang parser currently used , this has been evident in CPS-870: Align CPS-Core output with SDN-C output
Issue/QuestionDescriptionNotesResolution
new model
  • module name for the model that holds the augment statement

new module name = extended-dmi-registry

prefix = ext-dmi

Loading data with Liquibase

Dmi registry model is loaded via liquibase which means that the content of the yang resource is already set 

  • will the new model need to be loaded 
  • how will the 'import' statement work to create a new model

New JIRA ticket created for this

see 

ODL Yang tool

what is needed to acknowledge the augment statement for a new model

  • new model will contain a prefix of the module name