Giles, Clayton thanks for your comments. 

Folks I added a page in cwiki where we can catalog stories like these. If you 
have a story to share please create a sub-page under 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Why+we+picked+CloudStack 
and put a link in this page.
 
> On Jan 23, 2013, at 9:18 PM, Giles Sirett <[email protected]> wrote:
> 
> > Animesh
> >
> > This is  a topic that we discuss a lot with customers. We have many
> customers who have evaluated both OS and CS and then choose CS.
> >
> > The customers that we work with like CS because it is a "product" that
> > has many real world deployments, as opposed to OS, which is (IMO) a
> > "code project"  only right now
> >
> > The way I see it at the moment is it is wholly dependant on use-case:
> >
> > If you are a major vendor (with a massive budget)  who wants to create a
> propriety stack of your own (abstracted from the underlying core code), then
> OS does offer a lot.  But it requires a lot of work to get it in a usable 
> state.
> Great if you want to make it your own thing, but not great if you have the
> usual, real world, time and cost constraints.
> >
> > However, many organisations (both public cloud providers such as telcos
> and private cloud operators) want something that they can lift "out of the
> box" quickly and easily. That's where CS wins hands down at the moment.
> >
> > One of the most interesting anecdotes that I have is a media company
> over here in UK. One of their lead architects is a OS guru (he wrote the
> "Openstack cookbook" and now works for Rackspace!) and tried for months
> and months to build them a small production cloud (including buying
> professional services to help). They eventually gave up, and we built them a
> CS cloud in a matter of days.
> >
> > We've got some case-studies coming out in the next few weeks which
> > we'd be happy to share with the community
> 
> Giles, Yes please. We need more case studies. In general, we need users of
> CS to more vocal about how they are using it.
> 
> I am happy to help anyone who wants to write  a case study and publish it
> openly.
> 
> -sebastien
> 
> >
> >
> > Kind Regards
> > Giles
> > @shapeblue
> >
> > D: +44 20 3603 0541 | M: +44 796 111 2055
> >
> >
> >
> >
> > -----Original Message-----
> > From: Animesh Chaturvedi [mailto:[email protected]]
> > Sent: 23 January 2013 19:11
> > To: [email protected]
> > Subject: RE: [DISCUSS] "Arming" cloudstack supporters in "stack war"
> bakeoffs....
> >
> >
> >
> >> -----Original Message-----
> >> From: Alex Huang [mailto:[email protected]]
> >> Sent: Wednesday, January 23, 2013 10:54 AM
> >> To: [email protected]
> >> Subject: [DISCUSS] "Arming" cloudstack supporters in "stack war"
> bakeoffs....
> >>
> >> Hi All,
> >>
> >> I like to discuss with the community how we can best "arm" cloudstack
> >> supporters in "stack war" bakeoffs.  This is due to Ilya's email
> >> thread.  I think his question and others like it will be repeated
> >> often.  The community suggested an objective process to evaluate the
> >> various stacks: bakeoffs, which I'm supportive of.  But it make sense that
> people don't just enter into
> >> these bake-offs blind.   We should provide them with the information,
> >> experience and process to properly conduct cloudstack in these bakeoffs.
> >> However, I'm not sure what's the right combination to provide.  So I
> >> like to start this topic to see what the community thinks.
> >>
> >> I asked this during cloudstack-meeting and Chip suggested Dave's
> runbook.
> >> That's a good starting point.  Is there any other suggestions?
> >>
> >> There's a top level section in our wiki that makes sense for this.
> >> After we come up with the right combination, we can update the wiki
> >> and continue to update the wiki with more information.
> >>
> >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Newbie
> >>
> >> Thanks.
> >>
> >> --Alex
> >
> > Folks wearing project management hats can you share any success stories
> and real customer experience and reasoning in choosing cloudstack
> publically?
> >
[Animesh>] 

Reply via email to