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

	Description	Notes and Results
1	Create Dataspace	dataspace 'my-dataspace' created	dataspace table Image Modified
2	Create schemaset with Zip File resource dataspace: my-dataspace Models used extended-dmi-registry.yang dmi-registry-sample.yang Zip file contains the two models used above dmiModels.zip	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 dataspace-name: my-dataspace anchor-name: my-anchor xpath: / dmiModelData.json	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/Question

Description

Notes

Resolution

new model

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

New JIRA ticket created for this

see

Jira

ODL Yang tool

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

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

...

Space shortcuts