cloudstack marketplace v1.0
DESCRIPTION
TRANSCRIPT
CloudStack Marketplace v1.0Jie FengNovember 30th, 2012
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(free image, license can be enforced within
the image or application itself)SaaS/PaaS
CloudStack Marketplace Components
Apache Listing RepositoryConfig.js
Listing n.js
+
Supporting files
Listing 1Listing 2…Listing n
Listing n
CloudStack Instance Apache Listing Repository website
Admin Configure CloudStack MarketplaceThrough CloudStack Global Settings
Item Setting Default
Enable marketplace True or false True
Marketplace Listing Repositories
List of repositories Apache CloudStack List Repository location (enabled)
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
Access CloudStack MarketplaceFrom CloudStack UI After Login
Access CloudStack MarketplaceFrom URL: http://<cloudstack management server>/marketplace
Image
Product NameVendor
SaaS/PaaS Listing Admin View
ADMIN INSTRUCTION
ProductImage
Enable Service
SaaS/PaaS Listing User View
ADMIN INSTRUCTION
ProductImage
Use Service Vendor defined. Anything that can be launched by web browser.
Image Template Listing Admin View
TEMPLATES
ProductImage
Create Template• Template 1 (v1.0, XenServer)• Template 2 (v2.0, KVM)• Template 3 (v2.3, VMware)• …
TemplatesApplications
Admin Create TemplateThrough “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
Image Template Listing User View
TEMPLATES
ProductImage
Create Instance• Template 1 (v1.0, XenServer)• Template 2 (v2.0, KVM)• Template 3 (v2.3, VMware)• …
TemplatesApplications
User Create TemplateThrough “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
User Create Instance From Image TemplateThrough “Add Instance” CloudStack UI
Design Choices
Where to Host Apache Listing Repository?Pros Cons v1.0
ProposalCloudStack Source Code Tree (part of CloudStack distribution)
• Governed by the same Apache project process
• Listings are tested and verified to work with each CloudStack version (just like vendor plugins)
• Vendors need to sign Apache Contributor License Agreement (CLA)
• Vendors cannot make changes to listings off CloudStack release cycle
• New vendors and products have to wait for the next CloudStack release cycle
A Separate Listing Repository Hosted by The Community
• Vendors do not need to sign Apache CLA
• Vendors can add/update listings off CloudStack release cycles, with changes propagated to each CloudStack instance
• What about governance? If no governance, the listing might not work, or can even contain virus. To provide governance, need to create a whole new process and need people
No Apache Listing Repository
• Less work for the community • Relies on third party to provide this, which means we might end up with no listing repositories
√
Naming Options
Naming Options v1.0 Proposal
CloudStack Marketplace
Cloud Store
CloudStack App Store
CloudStack App Library
CloudStack App Catalog
√
Comments and Questions
• CloudStack wiki https://cwiki.apache.org/CLOUDSTACK/cloudstack-marketplace-proposal.html
• CloudStack dev mailing [email protected]
• Contact me [email protected]