Page Comparison

Lead Committer: Victor Gao

Reference Repo/Marketplace

Key Points:
1. Market place FE/BE will handle all the Pre-onboarding functionality and provides API and UI to VNF Vendors for package management.
2. Package can be a Heat file or CSAR package. Marketplace BE communicates with SDC to convert it to CSAR package.
3. Validation includes validating package structure, integrity and authenticity.
4. The functionality of managing license(atleast the user interface) should also be moved to market place as it logically fits there.(, Pre-Onboarding functionality).[This is a suggestion, please think about this] 5. Lifecycle test and function test would be attempted in future releases.
6. Finally validated CSAR would be pushed to  SDC catalogue

Difference between Catalog and Market place (Analogy)

Market Place:

• Farmer(VNF designers/Vendors)  push their produce to market.Market Vendors check the quality and display in their stalls.
• Consumer/Operators select the product based on quality, price and other factors and bring it to their home.
  
  
• Image Added  

Catalog:

• Consumers put their purchase in their fridge for consumption.
• Products in the fridge are consumed by variety of dishes (services). (Design tools)

Image Added

Scenario:

1. Vendor logs into the marketplace, upload the package and pass the tests in VNFSDK.
2. Marketplace show the packages which have already passed the test.
3. Operator logs into the marketplace, selects one package which they want, and push into SDC to do the service instantiation

Marketplace Users:

1. Vendor: Use VNFSDK tool chain to do validation/test, upload/download the package, package management(versioning notification...etc)
2. SDC(Operator) : Download/push package, get package at any time which is CI/CD(ONAP compliant) and moves to design services.

Functional Test Cases

1. Test the interface to upload the csar package from market place.
2. Test the interface to query VNF Information.
3. Test the interface to delete csar package from market place.
4. Test the interface to download csar package.
5. Test the interface to query csar package based on conditions.
   
   Note: 
   1. All the interfaces are present in API Documentation page.
   2. Each above test cases can contain more than one test cases including success and error cases.