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.89 as permitted sender)
From: Jie Feng <Jie.Feng@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
CC: Pranav Saxena <pranav.saxena@citrix.com>
Date: Tue, 8 Jan 2013 11:05:01 -0800
Subject: RE: [DISCUSS] Opennebula marketplace integration
Thread-Topic: [DISCUSS] Opennebula marketplace integration
Thread-Index: Ac3t0XAM4VepRQNaTRi+WuReJf97YQAAV/dw
Message-ID: 
 <7A92FF96DF135843B4B608FB576BFC3E012DA300E31A@SJCPMAILBOX01.citrite.net>
References: <61ED7E4A-3544-46BE-83FC-5FB0075A0899@gmail.com>
	<67EF18FDCA335F489B366120481AB6C5F6B38A3CA6@BANPMAILBOX01.citrite.net>
	<AB3DC767-236C-4DBA-A557-C7C9A97E0865@gmail.com>
	<7A92FF96DF135843B4B608FB576BFC3E012DA2CF1BFF@SJCPMAILBOX01.citrite.net>
	<67EF18FDCA335F489B366120481AB6C5F6B38A4356@BANPMAILBOX01.citrite.net>
	<7C005DED-7361-41F1-954E-6FD8C13B8B4F@gmail.com>
	<67EF18FDCA335F489B366120481AB6C5F6B3E7C627@BANPMAILBOX01.citrite.net>
	<DF95B7BF-530A-4CEF-8321-A36B67517175@gmail.com>
	<67EF18FDCA335F489B366120481AB6C5F6B3E7C62E@BANPMAILBOX01.citrite.net>
	<CC515018-86BD-4211-BB0D-23BAADBA2D1F@gmail.com>
 <CA+96GG5X+oN+p7LB70zR4WTpQKT1chjzjOZRyPGE3OPH-nPVjw@mail.gmail.com>
In-Reply-To: 
 <CA+96GG5X+oN+p7LB70zR4WTpQKT1chjzjOZRyPGE3OPH-nPVjw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I was out for a few weeks. I will update the wiki today to reflect the disc=
ussion in the community. To clarify one point from an earlier post by Sebas=
tien, the marketplace code I am referring to is the client piece.

Jie

> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Tuesday, January 08, 2013 10:53 AM
> To: cloudstack-dev@incubator.apache.org
> Cc: Pranav Saxena
> Subject: Re: [DISCUSS] Opennebula marketplace integration
>=20
> On Mon, Jan 7, 2013 at 4:54 AM, Sebastien Goasguen <runseb@gmail.com>
> wrote:
> >
> > On Dec 27, 2012, at 3:32 PM, Pranav Saxena <pranav.saxena@citrix.com>
> wrote:
> >
> >> [Sebastien] - Was the page updated to take into account all the
> discussions that happened on the ML ?
> >>
> >> Also what is in this feature branch ? I believe it was created before =
we had
> all the discussions. Does it contain the core marketplace code and the re=
po
> listings components ? It should only contain the "client"/plugin side.
> >>
> >> [Pranav] -  Yes , Sebastien . So currently we just have a very basic c=
lient
> /plugin side code which creates a tab for marketplace tab on the cloudsta=
ck
> UI . Clicking on that would point to a new user interface which fetches t=
he
> content and images/thumbnails dynamically from dummy config files . You
> can imagine it as a tile-like structure displaying N number of applicatio=
ns
> uploaded by each user.  It does NOT  contain any core marketplace code.
> >>
> >
> > I created a sub-task of CLOUDSTACK-619:
> https://issues.apache.org/jira/browse/CLOUDSTACK-619 for the opennebula
> integration.
> >
> > Right now, I don't believe the wiki page has been updated to reflect al=
l the
> discussion on the ML, see:
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Mar
> k
> > etplace+Proposal
> >
> > My plan is to use the opennebula marketplace api to populate the "dummy
> config files". The marketplace server and api keys should probably be
> configured as global settings.
> >
> > Who is doing a separate marketplace repo using your own code (not the U=
I
> client code ) ?
> >
> > -Sebastien
> >
> >
> >
>=20
>=20
> Sonny, you are currently the assignee in CLOUDSTACK-619.  Do you think we
> can get the functional spec updated to reflect the list discussions on th=
is
> topic?
>=20
> The spec, as it currently stands, still reflects some of the concepts tha=
t I have
> a standing veto on.  I'd be very happy if we work around the issues that =
I
> (and others) have raised in the design and implementation.