Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of runseb@gmail.com designates
 209.85.161.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <7A92FF96DF135843B4B608FB576BFC3E012D9C3244BF@SJCPMAILBOX01.citrite.net>
References: 
 <7A92FF96DF135843B4B608FB576BFC3E012D9C3244BF@SJCPMAILBOX01.citrite.net>
Date: Tue, 10 Jul 2012 03:49:21 -0400
Message-ID: 
 <CACZ5N2Ycc3DnJzZ_Seo2GotqF8RhqqX0wJoyG-hNpFJ5wHN=mg@mail.gmail.com>
Subject: Re: CloudStack Marketplace - need feedback
From: sebastien goasguen <runseb@gmail.com>
To: cloudstack-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Jie,

This sounds like a good idea, I know Opennebula has such a marketplace:
http://marketplace.c12g.com/appliance
It might be worth looking at their capabilities, and check if their
code is open source.

-Sebastien

On Mon, Jul 9, 2012 at 1:32 PM, Jie Feng <Jie.Feng@citrix.com> wrote:
> I would love to get folks' feedback on proposing a subproject under Apach=
e CloudStack, called MarketPlace. There are many ISVs, SaaS/PaaS vendors pr=
oviding value-added products and services on IaaS clouds. The goal is to ma=
ke their products more visible and easier to consume by anyone who deploys =
CloudStack.  It would also allow cloud admins to offer their own marketplac=
e to their users to get access to a variety of products and services that c=
an be used with CloudStack.
>
> Here is the idea:
> *             The subproject (let's call it MarketPlace for now) will con=
sist of source code for the CloudStack Marketplace user UI main page; a pro=
duct/service listing template; an admin portal; and a repository of listing=
. Both the source code and listings will be part of the CloudStack Marketpl=
ace distribution.
> *             Each listing will contain information about the product/ser=
vice, the user action needed to use the product/service, and instructions f=
or the admin to set up the product/service. Listings are contributed by sel=
lers (i.e. ISVs, SaaS/PaaS vendors). To include a listing in the CloudStack=
 MarketPlace distribution, the seller needs to place its XML files, graphic=
s 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 c=
an then choose which listings to enable for the users to see. The admin may=
 need to follow seller instructions to get products/services set up.
> *             This is not a global marketplace for every CloudStack user.=
 Each CloudStack instance will have its own marketplace if the admin choose=
s to install it. After CloudStack is installed, the admin should have the c=
apability to add, delete, enable, disable, and update the listings. If a se=
ller 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 l=
istings only: SaaS/PaaS services and free image templates. Even though the =
image template is free, the seller can still enforce licensing and charge a=
 fee within the application itself. To minimize product/service set up effo=
rt, in the case of image template, seller should provide a publicly accessi=
ble URL from which the image template can be downloaded.
>
> Future phases could include functions such as a seller listing publishing=
 portal, listing approval workflow, and usage reporting, etc.
>
> Jie


--=20
---
Sebastien Goasguen
Open Source Cloud Evangelist, Cloudstack
http://sites.google.com/site/runseb/