Michael, were not IBM or Dell, were not as big as you think. Were just 4
guys that deployed and mantain our openstack private cloud. Yes just four
guys. Were always present at the summits or cons answering questions and
telling people how hard was moving into iaas how many time it takes to
deploy o
and identify yourselves as an OpenStack user!
>>
>> Jim
>>
>>
>> From: mailto:raja.me...@wipro.com>>
>> Date: Fri, 6 Apr 2012 11:43:41 +0000
>> To: Mark Collier
>> mailto:mark.coll...@rackspace.com>>,
>> mailto:saur...@safewla
On Thu, 2012-04-05 at 17:28 -0700, Michael March wrote:
> Pretty much everyone featured on that page are 'big' organizations and
> there really isn't any detail on their experiences of trying to deploy
> (and maintain) Openstack. There's definitely not stories that a
> mid-range sized IT shop could
gt;>,
> mailto:saur...@safewlabs.com>> Cc:
> mailto:openstack@lists.launchpad.net>>
> Subject: Re: [Openstack] OpenStack immaturity
>
> +2 , I go with Saurabh.
>
>
> Thanks
> Meena Raja
>
>
> From:
> openstack-bounces+raja.meena=wipro@lists.launchpad.
d up and identify yourselves as an OpenStack user!
>
> Jim
>
>
> From: mailto:raja.me...@wipro.com>>
> Date: Fri, 6 Apr 2012 11:43:41 +
> To: Mark Collier
> mailto:mark.coll...@rackspace.com>>,
> mailto:saur...@safewlabs.com>> Cc:
> mailto:ope
afewlabs.com>>
Cc: mailto:openstack@lists.launchpad.net>>
Subject: Re: [Openstack] OpenStack immaturity
+2 , I go with Saurabh.
Thanks
Meena Raja
From:
openstack-bounces+raja.meena=wipro@lists.launchpad.net<mailto:openstack-bounces+raja.meena=wipro@lists.launchpad.net>
[mailto
Subject: Re: [Openstack] OpenStack immaturity
+1 well said
Saurabh wrote:
Hey Guys
One of the user stories from my company. We are an SME and our customers are
SMEs too. We are working on releasing documents in detail as well as discussing
with the customers, for releasing the entire
+1 well said
Saurabh wrote:
Hey Guys
One of the user stories from my company. We are an SME and our customers are
SMEs too. We are working on releasing documents in detail as well as discussing
with the customers, for releasing the entire customizations to the community.
We are working on
Hey Guys
One of the user stories from my company. We are an SME and our customers
are SMEs too. We are working on releasing documents in detail as well as
discussing with the customers, for releasing the entire customizations to
the community. We are working on releasing all these in the form of a
I'm about to install OpenStack for a customer in a few days. It's an SME
and their first production cloud would be limited to a few hosts and
about 60 VMs. Do you feel it'd be worth getting their feedback about
deployment and usage?
yours,
michaël
Michaël Van de Borne
R&D Engineer, SOA team
I've been giving this thread some thought and it dawned on my that we need
to expand this page:
http://openstack.org/user-stories/
Pretty much everyone featured on that page are 'big' organizations and
there really isn't any detail on their experiences of trying to deploy (and
maintain) Openstack
+ ?
On 4/5/12 9:43 AM, "Jay Pipes" wrote:
+1.
On 04/04/2012 04:20 PM, David Kranz wrote:
> +1000
>
> I believe the nova team should make backporting essential bugs to a
> stable essex base and dealing with the upgrade issue the highest
> priority for the start (at least) of the Folsom cycle
+1.
On 04/04/2012 04:20 PM, David Kranz wrote:
+1000
I believe the nova team should make backporting essential bugs to a
stable essex base and dealing with the upgrade issue the highest
priority for the start (at least) of the Folsom cycle. We need people to
deploy real systems using Essex.
Another perspective worth considering is immaturity vs growth. Are
there enough progresses being made? When problems are identified, are
these solved swiftly and effectively? I think the people involved in
the OpenStack community do and have done a great job in this regard,
and should be praised ra
Maybe it would be more interesting, instead of getting on the defensive to
instead start asking what people think is broken or is immature and fix those
areas.
Push forward, get peoples feelings about it, and take it as constructive input.
If people think its immature, ask for why and then fix
+1000
I believe the nova team should make backporting essential bugs to a
stable essex base and dealing with the upgrade issue the highest
priority for the start (at least) of the Folsom cycle. We need people to
deploy real systems using Essex. With regard to smooth upgrades, they
won't happe
There are many projects rolled up into the thing called "OpenStack".
Nova is only one of them and is the one that most people are talking
about when they say "OpenStack". This does a huge disservice to the
other projects especially Swift.
It's very frustrating to see the other projects all paint
+tim.bell=cern...@lists.launchpad.net] On Behalf Of
Jan Drake
Sent: 04 April 2012 16:37
To: Razique Mahroua
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] OpenStack immaturity
H. While ease of deployment is definitely "an area of future strength" for
OS, the gap
> According to the statement of this article from Gartner
> group http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/ Openstack is a
> highly immature platform.
> But why? What's make Openstack so immature?
>
> Any comments on that?
>
> Th
On Wed, Apr 4, 2012 at 8:14 AM, Razique Mahroua
wrote:
> The "immaturity" being exposed here has nothing to do with neither
> stability nor bugs - in fact the angle is more about an ease of deployment.
> Such statements are not new, and well known from "enterprises" point of
> view.
> I remember s
H. While ease of deployment is definitely "an area of future strength" for
OS, the gap is closing rapidly and the reality for the enterprise is that
initial, comparable (apples to apples) VMWare installations all come with an
initial professional services engagement anyway.
Having just do
The "immaturity" being exposed here has nothing to do with neither stability nor bugs - in fact the angle is more about an ease of deployment.Such statements are not new, and well known from "enterprises" point of view.I remember same articles about Linux, few years back about Zimbra, few months ba
I believe this "Openstack is a highly immature platform." is referring
more to nova than swift. The simple reason for that is nova is more
focused on dev than ops but that is changing.In mature projects
the questions like "How do I run this reliably every day?" and "How
can I safely upgrade f
It depends on what you expect OpenStack to do for you. If you want
pre-packaged, click-to-install software, it is not there, yet. But if
you want to be able to influence the future of the project you want to
bet your business on, you have a much higher chance of doing that with
OpenStack than with
I think this news is good
Make us must work hard.
Time will tell
Like linux, now lead.
On Apr 4, 2012 5:57 PM, "Diego Parrilla Santamaría" <
diego.parrilla.santama...@gmail.com> wrote:
> Immaturity of a platform is something you can easily fix paying the right
> fee to your favorite analyst fir
Immaturity of a platform is something you can easily fix paying the right
fee to your favorite analyst firm.
Seriously, Openstack is an open platform and an open community. This means
problems and issues are open to discuss to everyone. Propietary platforms
issues are rarely disclosed, and they lo
Hi everyone,
According to the statement of this article from Gartner group
http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/
Openstack is a
highly immature platform.
But why? What's make Openstack so immature?
Any comments on that?
Th
27 matches
Mail list logo
