Versions Compared

Old Version 2

changes.mady.by.user Lee Anjella Macabuhay

Saved on

compared with

New Version Current

changes.mady.by.user Toine Siebelink

Saved on

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 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

  • 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.

...

See brief on YANG language on Support for Yang Language

By using the keyword 'augment' on yang models, we are allowed to extend a data model i.e. add nodes to the current structure

...

 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 model

Image Added

Image Removed

Open Issues/Questions


...

Testing

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

Image Added


prefix is ignored by the yang parser currently used , this has been evident in CPS-870: Align CPS-Core output with SDN-C output

DescriptionNotes Resolutionnew model
  • module name for the model that holds the augment statement
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
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