Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2B8AEDFC5 for ; Mon, 10 Dec 2012 23:05:48 +0000 (UTC) Received: (qmail 34015 invoked by uid 500); 10 Dec 2012 23:05:47 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 33978 invoked by uid 500); 10 Dec 2012 23:05:47 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 33969 invoked by uid 99); 10 Dec 2012 23:05:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 23:05:47 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=5.0 tests=HTML_IMAGE_RATIO_08,HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Jie.Feng@citrix.com designates 66.165.176.89 as permitted sender) Received: from [66.165.176.89] (HELO SMTP.CITRIX.COM) (66.165.176.89) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 23:05:41 +0000 X-IronPort-AV: E=Sophos;i="4.84,254,1355097600"; d="png'150?jpg'150,145?scan'150,145,208,217,150,145";a="179461" Received: from sjcpmailmx01.citrite.net ([10.216.14.74]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/RC4-MD5; 10 Dec 2012 23:05:17 +0000 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.72]) by SJCPMAILMX01.citrite.net ([10.216.14.74]) with mapi; Mon, 10 Dec 2012 15:05:16 -0800 From: Jie Feng To: "cloudstack-dev@incubator.apache.org" Date: Mon, 10 Dec 2012 15:05:15 -0800 Subject: CloudStack Marketplace Update Thread-Topic: CloudStack Marketplace Update Thread-Index: Ac3XKXKal9vLac86R0iv/+OqJ3yRlw== Message-ID: <7A92FF96DF135843B4B608FB576BFC3E012DA27F3E7B@SJCPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/related; boundary="_005_7A92FF96DF135843B4B608FB576BFC3E012DA27F3E7BSJCPMAILBOX_"; type="multipart/alternative" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_005_7A92FF96DF135843B4B608FB576BFC3E012DA27F3E7BSJCPMAILBOX_ Content-Type: multipart/alternative; boundary="_000_7A92FF96DF135843B4B608FB576BFC3E012DA27F3E7BSJCPMAILBOX_" --_000_7A92FF96DF135843B4B608FB576BFC3E012DA27F3E7BSJCPMAILBOX_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The CloudStack Marketplace Wiki https://cwiki.apache.org/confluence/display= /CLOUDSTACK/CloudStack+Marketplace+Proposal has been updated with the follo= wing: more details, design choices, link to the Collaboration Conference sl= ides, and feedbacks and questions I got from the conference. Many thanks to= those who attended my presentation and provided feedback. Some of feedback= s are still yet to be worked into the design (for example, the listing file= format will take into consideration of other open source cloud marketplace= s out there). We had some early discussions in the mailing list regarding where to host t= he Apache CloudStack listing repository and what to name this feature. I in= cluded 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 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Here are the Design Choices: Where to host Apache Listing Repository? There have been some discussions on the cloudstack-dev mailing list on wher= e to host the Apache Listing Repository a few months ago. Given that additi= onal 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 opti= on. 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 c= ontinue to update the image template off release cycle, option 1 (CloudStac= k source code tree) is fine. [cid:image001.jpg@01CDD6E7.C1481AD0] What should be the name of this new component? This has been discussed on the cloudstack-dev mailing list. There has not b= een overwhelming response to any of the names. "Marketplace" was proposed b= ecause it is well known and used by multiple commercial cloud providers, an= d this is different enough from "Template" in the left navigation so that n= o confusion will be caused. During the CloudStack Collaboration Conference,= "Catalog" was brought up as a potential alternative because there is curre= ntly no plan to handle $ transaction by the marketplace feature. [cid:image002.png@01CDD6E7.C1481AD0] --_000_7A92FF96DF135843B4B608FB576BFC3E012DA27F3E7BSJCPMAILBOX_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

The CloudStack M= arketplace Wiki https://cwiki.apache.org/confluence= /display/CLOUDSTACK/CloudStack+Marketplace+Proposal has been updated wi= th the following: more details, design choices, link to the Collaboration C= onference slides, and feedbacks and questions I got from the conference. Ma= ny 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 li= st regarding where to host the Apache CloudStack listing repository and wha= t to name this feature. I included various options in the wiki (also see be= low), my proposal for v1.0, and feedbacks I got from the Collaboration Conf= erence attendees. Comments, suggestions, flames?

 

Thanks.

 

Jie=

 

=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Here are the Design Choices:

Where to host Apache Li= sting Repository?

There have been some discussions on = the cloudstack-dev mailing list on where to host the Apache Listing Reposit= ory a few months ago. Given that additional resources will be required to c= reate 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 Collabo= ration Conference and feedback was that as long as the actual vendor softwa= re is not open source, and vendor can continue to update the image template= off release cycle, option 1 (CloudStack source code tree) is fine.

3D"Description:

What should= be the name of this new component?

This has been disc= ussed on the cloudstack-dev mailing list. There has not been overwhelming r= esponse to any of the names. "Marketplace" was proposed because i= t is well known and used by multiple commercial cloud providers, and this i= s different enough from "Template" in the left navigation so that= no confusion will be caused. During the CloudStack Collaboration Conferenc= e, "Catalog" was brought up as a potential alternative because th= ere is currently no plan to handle $ transaction by the marketplace feature= . 

3D"Description=

 

= --_000_7A92FF96DF135843B4B608FB576BFC3E012DA27F3E7BSJCPMAILBOX_-- --_005_7A92FF96DF135843B4B608FB576BFC3E012DA27F3E7BSJCPMAILBOX_--