Page History

...

The listing repository contains a config.js file and vendor product folders. The config.js file contains an index of the listings, which will be read by the Marketplace UI to build the Marketplace Homepage. The Listing folders contain metadata and supporting files for each product listing, which will be read by the Marketplace UI to build the Details page for each product listing.

Vendors

For image templates and ISOs, vendors can contribute to the a product listing repository following these steps:

1. Create a listing folder for its product or servicein the listing repository.
2. Create and place a listing.js file and place it in the folder which . The listing.js file includes metadata for the listing. This metadata file will be read by the Marketplace UI and present to the admins and users.  :
   1. Product name
   2. Vendor name
   3. A brief description
   4. Location of the graphics
   5. Metadata for associated templates and ISOs. Templates and ISO metadata should include location of where the actual image template and ISO data file. Multiple template and ISO metadata can be included in the same product listing to cover multiple hypervisor support and multiple product versions. 
   6. Tags (TBD)
3. (Optional) Place any supporting files such as graphics and image template/ISO data files into the listing folder. Note that these files can be located in other places. In the case of the Apache Listing Repository, image template/ISO data files should be located outside of the listing repository and hosted by the vendor itself or third party.
4. Add an entry to the config.js file for the listing.

For PaaS/SaaS, vendors can contribute a service listing following these steps:

1. Create a listing folder for its service in the listing repository.
2. Create a listing.js file and place it in the folder. The listing.js file includes metadata for the listing:
   1. Service name
   2. Vendor name
   3. A brief description
   4. Location of the graphics
   5. (Optional) Admin instruction. Admin instruction are steps that admin needs to follow in order to set up services for users. It can be left blank if no initial set up is required.
   6. "use service" action. Vendor needs to specify what happens when user clicks on the action button "use service". It can lead to a URL or scripts that can be invoked by the web browser. 
   7. Tags (TBD)
3. (Optional) Place any supporting files including such as graphics and scripts into the listing folder. Note that these files can be located in other places. 
4. (Optional) Place any UI or regular plugins in the CloudStacplugin in the CloudStack source code repository plugin folder. If a plugin is required for the CloudStack, you can place it in the CloudStack plugin folder in the source code tree. Or you can store it externally and instruct admins how to download and install the plugin as part of the admin instruction.
5. Add an entry to the config.js file for its the listing.

Admins Install and Configure CloudStack Marketplace

...