Versions Compared

Key

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

...

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

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 

see

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-1183
 

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

...