Great analysis Chris!
In terms of the blueprint model, I am also in favor of something simple.
CloudFormation can do what vApp is doing, and more. We only need to implement a
subset as a starter. For example, allow users to describe multiple VMs,
template ID for the VMs, and default service off
+1 on the feature and comments below.
> *As a core native format*, what do people think of Oasis TOSCA's XML
> vocabulary [1] ? I've worked with it for a while, and it has the right
> general
> concepts I think we'd need, done well, and in a way which won't bite us
> down the line. (Alex Huang,
I was out for a few weeks. I will update the wiki today to reflect the
discussion in the community. To clarify one point from an earlier post by
Sebastien, the marketplace code I am referring to is the client piece.
Jie
> -Original Message-
> From: Chip Childers [mailto:chip.child...@su
2 4:17 AM
> To: cloudstack-dev@incubator.apache.org
> Cc: Jie Feng; Sonny Chhen
> Subject: Re: [DISCUSS] Opennebula marketplace integration
>
>
> On Dec 19, 2012, at 12:11 PM, Pranav Saxena wrote:
>
> > Hi Sebastien ,
> >
> > The openNebula marketplace looks good .
> cloudstack listing repository" and "inclusion in source code" and geared more
> towards contributing a plugin that would enable cloudstack users to link to a
> third party marketplace if they so desired. Then this would be agreeable.
>
> I also believe this shoul
Citrix as an
example. All of our committers who work with CloudStack partners can bring in
our validated partner listings. I am simply trying to leverage what we are
already doing outside of the community and bring the benefits in.
>
> On Dec 12, 2012, at 5:09 PM, Jie Feng
> wrote:
>
&
David, your comments just inspired another idea.
Citrix has a Citrix Ready program where our partners are certified. I think
many other companies might have similar programs. And there are committers in
the CloudStack community working for these companies with the partners. At
least we are com
Great discussions! Here is my comments to a few points brought up by multiple
people. My other comments are inline below.
1. Marketplace code, listing repository, what is required, what is optional
[Jie] The Marketplace code is separate from the listing repository. Marketplace
is an optional
bably won't be able to implement
this in time. But I like to track that for future releases. I will file a
feature enhancement bug for Marketplace once we have the design done and
listing repository sorted out.
-Original Message-
From: Jie Feng [mailto:jie.f...@citrix.com]
Sent: W
Jie Feng created CLOUDSTACK-619:
---
Summary: CloudStack Marketplace
Key: CLOUDSTACK-619
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-619
Project: CloudStack
Issue Type: New Feature
, Jie Feng wrote:
> Any inputs from others in the community? I like to reach some consensus on
> where to host the Apache listing repository in the next couple of weeks
> (since if we go with option 1, we need to give vendors enough time to put
> listings in source code prior to code f
-Original Message-
From: Jie Feng
Sent: Monday, December 10, 2012 4:14 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: CloudStack Marketplace Update
Thanks Joe for the inputs! My comments inline. Chiradeep, thanks for the names!
You are sure more creative than I am :)
-Original
Update
I'll say this.. I wish the CloudStack UI looked like the marketplace proposal.
Very slick!
-kd
-Original Message-
From: Jie Feng [mailto:jie.f...@citrix.com]
Sent: Monday, December 10, 2012 4:14 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: CloudStack Marketplace U
: CloudStack Marketplace Update
On Mon, Dec 10, 2012 at 03:24:18PM -0800, Jie Feng wrote:
> It seems the image got stripped out by the Apache mail server. So I
> included text info instead. Sorry about the spam.
Probably just as well, some of us aren't using gui mail clients. ;-)
> We
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
Fixed the images. Not sure why it didn't work the first time.
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/confl
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 than
[
https://issues.apache.org/jira/browse/CLOUDSTACK-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510913#comment-13510913
]
Jie Feng commented on CLOUDSTACK-576:
-
Here is my take on Alex's questi
[
https://issues.apache.org/jira/browse/CLOUDSTACK-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509978#comment-13509978
]
Jie Feng commented on CLOUDSTACK-583:
-
Forgot to mention that service offerin
Jie Feng created CLOUDSTACK-583:
---
Summary: Expose Service Offerings and Zone options (including
UUID) to users in the CloudStack UI
Key: CLOUDSTACK-583
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-583
There seem to be a few places where new feature requests come up: CloudStack
user mailing list, CloudStack dev mailing list, the two sites Chiradeep
mentioned below, and JIRA. Is there a guideline for what to do if we have a new
feature request? Ideally, all the discussions for a specific reque
[
https://issues.apache.org/jira/browse/CLOUDSTACK-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478103#comment-13478103
]
Jie Feng commented on CLOUDSTACK-367:
-
+1 for having a good CLI.
>
+1 for having a good CLI.
From a CloudStack user perspective (not admin), I found that the UI does not
expose all the functions in the API. And it is not easy for a user to create
signed API calls. I have not used the existing CLI tool because it is only
referenced in docs, but unclear where t
This looks great! Thanks for the hard work, Joe! Just a few comments.
"feature-complete" is too strong a word. I suggest use words (or a combination
of words) such as "turnkey", "fully functional", and "feature rich".
The list of new features is interesting to folks who are familiar with pri
/multi_node_management_server.xml PRE-CREATION
docs/en-US/multi_site_deployment.xml PRE-CREATION
docs/en-US/separate_storage_network.xml PRE-CREATION
docs/en-US/small_scale_deployment.xml PRE-CREATION
Diff: https://reviews.apache.org/r/6881/diff/
Testing
---
passed publican build
Thanks,
Jie
In continuation to the discussion [1] and taken feedback from community
members, I am proposing a new component under Apache CloudStack, called
CloudStack Marketplace [2].
Per John and Chiradeep's suggestion, the Marketplace client piece is installed
with CloudStack, and it pulls listings from l
[mailto:chiradeep.vit...@citrix.com]
Sent: Wednesday, July 11, 2012 12:05 PM
To: CloudStack DeveloperList
Subject: Re: CloudStack Marketplace - need feedback
On 7/11/12 11:11 AM, "Jie Feng" wrote:
>Thanks John for the feedback. I looked at OpenNebula marketplace
>(thanks Sebastien
n the feed, there's some sort of voting process
(maybe moderate each seller until they've "proven" themselves over a release or
two?)
* Daily cron process generates the feed, places it somewhere accessible via http
John
On Jul 9, 2012, at 10:32 AM, Jie Feng wrote:
&
I would love to get folks' feedback on proposing a subproject under Apache
CloudStack, called MarketPlace. There are many ISVs, SaaS/PaaS vendors
providing value-added products and services on IaaS clouds. The goal is to make
their products more visible and easier to consume by anyone who deploy
29 matches
Mail list logo