See details on page https://wiki.onap.org/display/DW/CPS-391Spike%3A+Define+and+Agree+NCMP+REST+Interface

This is to support combination #6 in the 'Datastore, Paths and Format Combinations for Read Operations' table. 

expected format : application/yang-data+json
expected resource-path: NetConf compatible

Supported parameters (depending SND-C/ODL interface) 

• fields
• depth (not defined in REST interface)
• config (content=all depends on datastore, use cannot change)

NCMP 'selects' correct DMI-Plugin using DMI-Registry based on CmHandle

NCMP forwards as PUT request to (correct DMI Plugin instance)  and execute PUT REST request as define in example #7 and#8 detailed here: https://wiki.onap.org/display/DW/CPS-390+Spike%3A+Define+and+Agree+DMI+Plugin+REST+Interface#CPS390Spike:DefineandAgreeDMIPluginRESTInterface-DMIInventory,Model&DataSyncAPI

NCMP uses generic body:

• operation "read"
• do not set dataType 
• set "additional-properties" from data in registry for that CmHandle

 A/C

1. REST endpoint described/implemented using Open API
2. Update .rst (read-the-docs) to include a section about NCMP (in offered APIs see https://docs.onap.org/projects/onap-cps/en/latest/design.html#offered-apis) 
3. Can execute REST endpoint (might depend on CPS-486)
4. Error handling if no DMI available for CmHandle (agree response code, internal exception) document as needed (in new section) on https://wiki.onap.org/display/DW/CPS+Exceptions+and+REST+API+HTTP+Response+Codes
5. Handle Errors from SDN-C wrap in custom exception and document on https://wiki.onap.org/display/DW/CPS+Exceptions+and+REST+API+HTTP+Response+Codes
6. Demo using different parameters against simulator when CPS-486 is completed too