This use story will update the existing solution for storing model/modules:

• Design and document new 'modules' table (namespace, revision, module, id, dataspace_id)
  See also note under. https://wiki.onap.org/pages/viewpage.action?pageId=92995793#CCSDK2756DM:[Spike]ProposeC&PSDataModel-2.2Genericschema(currentproposal)
• (update) Rest Endpoint org.onap.cps.rest.controller.RestController#uploadYangModelFile 
  • add dataspace parameter
  • follow new API structure
• (update) implementation in CPService  
• (update) implementation in Persistence Service using 'new' schema

API Structure : https://wiki.onap.org/display/DW/CCSDK-2870+DP%3A+CPS+REST+API+Documentation+-+PROPOSAL

Acceptance Criteria

1. Change OpenAPI to use Spring framework
2. Use the agreed URL structure: POST /dataspaces/{dataspace-id}/modules
   See https://wiki.onap.org/display/DW/CCSDK-2870+DP%3A+CPS+REST+API+Documentation+-+PROPOSAL
3. If the provided set of Yang modules contains any yang error the request will be rejected (HTTP Error 400)
4. if a new dataspace-id is provided a record will be created in the dataspace table
5. if a new namespace&revision is provided a new record will be created in the modules tale. 
6. Many modules can be added in one request
7. If any modules already exist the whole operation will be rejected and an HTP 400 error code will be returned.
8. we can run a SQL query to show all modules for a given dataspace (using SQL CLI tool)