Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of Jie.Feng@citrix.com
 designates 66.165.176.63 as permitted sender)
From: Jie Feng <Jie.Feng@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Mon, 9 Jul 2012 10:32:39 -0700
Subject: CloudStack Marketplace - need feedback
Thread-Topic: CloudStack Marketplace - need feedback
Thread-Index: Ac1d+KOHXn2TkywwR9ipd1F56RtXMA==
Message-ID: 
 <7A92FF96DF135843B4B608FB576BFC3E012D9C3244BF@SJCPMAILBOX01.citrite.net>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_7A92FF96DF135843B4B608FB576BFC3E012D9C3244BFSJCPMAILBOX_"
MIME-Version: 1.0

--_000_7A92FF96DF135843B4B608FB576BFC3E012D9C3244BFSJCPMAILBOX_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I would love to get folks' feedback on proposing a subproject under Apache =
CloudStack, called MarketPlace. There are many ISVs, SaaS/PaaS vendors prov=
iding value-added products and services on IaaS clouds. The goal is to make=
 their products more visible and easier to consume by anyone who deploys Cl=
oudStack.  It would also allow cloud admins to offer their own marketplace =
to their users to get access to a variety of products and services that can=
 be used with CloudStack.

Here is the idea:
*             The subproject (let's call it MarketPlace for now) will consi=
st of source code for the CloudStack Marketplace user UI main page; a produ=
ct/service listing template; an admin portal; and a repository of listing. =
Both the source code and listings will be part of the CloudStack Marketplac=
e distribution.
*             Each listing will contain information about the product/servi=
ce, the user action needed to use the product/service, and instructions for=
 the admin to set up the product/service. Listings are contributed by selle=
rs (i.e. ISVs, SaaS/PaaS vendors). To include a listing in the CloudStack M=
arketPlace distribution, the seller needs to place its XML files, graphics =
and code in the designated folder within the subproject.
*             When CloudStack is installed, the admin will have a choice to=
 install MarketPlace including all the pre-packaged listings. The admin can=
 then choose which listings to enable for the users to see. The admin may n=
eed to follow seller instructions to get products/services set up.
*             This is not a global marketplace for every CloudStack user. E=
ach CloudStack instance will have its own marketplace if the admin chooses =
to install it. After CloudStack is installed, the admin should have the cap=
ability to add, delete, enable, disable, and update the listings. If a sell=
er wants to add or update it listing for a specific CloudStack instance, s/=
he needs to go through the admin.

To keep it simple in the first phase, I propose to support two types of lis=
tings only: SaaS/PaaS services and free image templates. Even though the im=
age template is free, the seller can still enforce licensing and charge a f=
ee within the application itself. To minimize product/service set up effort=
, in the case of image template, seller should provide a publicly accessibl=
e URL from which the image template can be downloaded.

Future phases could include functions such as a seller listing publishing p=
ortal, listing approval workflow, and usage reporting, etc.

Jie

--_000_7A92FF96DF135843B4B608FB576BFC3E012D9C3244BFSJCPMAILBOX_--