1. CloudStack Marketplace v1.0
Jie Feng
November 30th, 2012

2. CloudStack Marketplace
• Enables ISVs to make their products visible and easily consumable by any
CloudStack-based clouds
• Provides CloudStack admins and users a list of ready to consume products
Image Templates/ISOs
SaaS/PaaS (free image, license can be enforced within
the image or application itself)

3. CloudStack Marketplace Components

4. Apache Listing Repository
Config.js
Listing 1
Listing 2
…
Listing n
Listing n.js Supporting files
Listing n +
CloudStack Instance Apache Listing Repository website

5. Admin Configure CloudStack Marketplace
Through CloudStack Global Settings
Item Setting Default
Enable marketplace True or false True
Marketplace Listing List of repositories Apache CloudStack List Repository location (enabled)
Repositories
Each listing repository has a property: enabled/disabled
• Enabled: both admins and users can see listings from the repository
• Disabled: admins can see listings from the repository

6. Access CloudStack Marketplace
From CloudStack UI After Login

7. Access CloudStack Marketplace
From URL: http://<cloudstack management server>/marketplace
Image
Product Name
Vendor

8. SaaS/PaaS Listing Admin View
Image Product
ADMIN INSTRUCTION
Enable Service

9. SaaS/PaaS Listing User View
Image Product
ADMIN INSTRUCTION
Use Service
Vendor defined.
Anything that can
be launched by
web browser.

10. Image Template Listing Admin View
Applications Templates
Image Product
TEMPLATES
Create Template
• Template 1 (v1.0, XenServer)
• Template 2 (v2.0, KVM)
• Template 3 (v2.3, VMware)
• …

11. Admin Create Template
Through “Create Template” CloudStack UI
• Auto populated from vendor’s template
metadata (admin can overwrite)
ᵒName
ᵒDescription
ᵒURL
ᵒHypervisor
ᵒFormat
ᵒOS type
• Admin set
ᵒZone
ᵒExtractable
ᵒPassword enabled
ᵒPublic

12. Image Template Listing User View
Applications Templates
Image Product
TEMPLATES
Create Instance
• Template 1 (v1.0, XenServer)
• Template 2 (v2.0, KVM)
• Template 3 (v2.3, VMware)
• …

13. User Create Template
Through “Create Template” CloudStack UI
• Auto populated from vendor’s template
metadata (user can overwrite)
ᵒName
ᵒDescription
ᵒURL
ᵒHypervisor
ᵒFormat
ᵒOS type
• User set
ᵒZone
ᵒExtractable
ᵒPassword enabled
ᵒPublic

14. User Create Instance From Image Template
Through “Add Instance” CloudStack UI

15. Design Choices

16. Where to Host Apache Listing Repository?
v1.0
Pros Cons
Proposal
CloudStack Source • Governed by the same Apache • Vendors need to sign Apache Contributor
project process License Agreement (CLA)
Code Tree
(part of CloudStack
• Listings are tested and verified to
work with each CloudStack version
• Vendors cannot make changes to listings
off CloudStack release cycle
√
distribution)
(just like vendor plugins) • New vendors and products have to wait for
the next CloudStack release cycle
A Separate Listing • Vendors do not need to sign • What about governance? If no governance,
Apache CLA the listing might not work, or can even
Repository Hosted • Vendors can add/update listings off contain virus. To provide governance, need
by The Community CloudStack release cycles, with to create a whole new process and need
changes propagated to each people
CloudStack instance
No Apache Listing • Less work for the community • Relies on third party to provide this, which
means we might end up with no listing
Repository repositories

17. Naming Options
Naming Options v1.0 Proposal
CloudStack Marketplace √
Cloud Store
CloudStack App Store
CloudStack App Library
CloudStack App Catalog

18. Comments and Questions
• CloudStack wiki
https://cwiki.apache.org/CLOUDSTACK/cloudstack-marketplace-proposal.html
• CloudStack dev mailing list
cloudstack-dev@incubator.apache.org
• Contact me directly
jie.feng@citrix.com