Versions Compared

Old Version 4

changes.mady.by.user Lee Anjella Macabuhay

Saved on

compared with

New Version 5

changes.mady.by.user Lee Anjella Macabuhay

Saved on

Key

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

...

 Using pyang tool, these two models were validated to confirm that the resulting schema tree module model includes the nodes that were intended to be added on to the dmi-registry modelImage Removed

Image Added


Testing

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

Image Added



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

Image Added

2

Create schemaset with Zip File resource


201 created

'my-schema-set-2'

  • schema_set table

Image Added


  • schema_set_yang_resources table

Image Added


  • yang_resource table

Image Added

3

Create Anchor

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

201 created

'my-anchor'

  • anchor table

Image Added

4

Create Node

201 created

Image Added

5

Get a schemaset

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

Image Added

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


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

...