It seems the image got stripped out by the Apache mail server. So I included text info instead. Sorry about the spam.
From: Jie Feng [mailto:jie.f...@citrix.com] Sent: Monday, December 10, 2012 3:05 PM To: cloudstack-dev@incubator.apache.org Subject: CloudStack Marketplace Update The CloudStack Marketplace Wiki https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Marketplace+Proposal has been updated with the following: more details, design choices, link to the Collaboration Conference slides, and feedbacks and questions I got from the conference. Many thanks to those who attended my presentation and provided feedback. Some of feedbacks are still yet to be worked into the design (for example, the listing file format will take into consideration of other open source cloud marketplaces out there). We had some early discussions in the mailing list regarding where to host the Apache CloudStack listing repository and what to name this feature. I included various options in the wiki (also see below), my proposal for v1.0, and feedbacks I got from the Collaboration Conference attendees. Comments, suggestions, flames? Thanks. Jie ========================================= Here are the Design Choices: Where to host Apache Listing Repository? There have been some discussions on the cloudstack-dev mailing list on where to host the Apache Listing Repository a few months ago. Given that additional resources will be required to create a separate governance body for a community managed listing repository, hosting the Apache Listing Repository within CloudStack source code tree for v1.0 seems to be a more viable option. The following is an analysis of pros and cons for each option. This was presented at the CloudStack Collaboration Conference and feedback was that as long as the actual vendor software is not open source, and vendor can continue to update the image template off release cycle, option 1 (CloudStack source code tree) is fine. * Option 1. CloudStack Source Code Tree (part of CloudStack distribution) -- proposed for v1.0 o Pros: Governed by the same Apache project process; listings are tested and verified to work with each CloudStack version (just like vendor plugins) o Cons: Vendors need to sign Apache contributor license agreement (CLA); vendors cannot make changes to listing files off CloudStack release cycle; new vendors and products have to wait for the next CloudStack release cycle to be added * Option 2. A separate listing repository hosted by the Apache CloudStack community o Pros: Vendors do not need to sign Apache CLA; vendors can add/update listing any time with changes propagated to each Cloudstack instance with Marketplace enabled o Cons: What about governance? If no governance, the listing might not work or can even contain virus. To provide governance requires us to create a whole new process and need people * No Apache listing repository o Pros: Less work for the community o Cons: No central place for the community to provide listings; relies on third party to provide this which means we might end up with no listing repositories What should be the name of this new component? This has been discussed on the cloudstack-dev mailing list. There has not been overwhelming response to any of the names. "Marketplace" was proposed because it is well known and used by multiple commercial cloud providers, and this is different enough from "Template" in the left navigation so that no confusion will be caused. During the CloudStack Collaboration Conference, "Catalog" was brought up as a potential alternative because there is currently no plan to handle $ transaction by the marketplace feature. * CloudStack Marketplace -- proposed for v1.0 * Cloud store * CloudStack app store * CloudStack app library * Cloudstack app catalog
