Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Dell Dumps Its Public Cloud Offerings 56

itwbennett writes "Last week, Dell said that it would be 'refining' its OpenStack plans. Now we know that 'refining' means 'backing away from'. Although the company wouldn't answer direct questions on the subject, a press release spells it out like this: 'Sales of Dell's current in-house multi-tenant public cloud IaaS will be discontinued in the U.S. in favor of best-in-class partner offerings.' Interestingly, none of Dell's initial partners, including Joyent, ScaleMatrix and ZeroLag, have platforms built on OpenStack."
This discussion has been archived. No new comments can be posted.

Dell Dumps Its Public Cloud Offerings

Comments Filter:
  • by spacepimp ( 664856 ) on Monday May 20, 2013 @03:13PM (#43775687) Homepage
    This is what a two billion dollar cash infusion buys? They are the new Nokia apparently.
    • by Anonymous Coward

      Except that there is no mention of Microsoft. You'd think if there was a conspiracy by Microsoft to get Dell to drop OpenStack, you'd see Dell recommending Azure.

  • by Dunbal ( 464142 ) * on Monday May 20, 2013 @03:22PM (#43775757)
    Someone overheard part of the conversation which went something like "it turns out that people aren't as dumb as we though they were".
  • by Anonymous Coward
    Anybody else misread that as "Pubic Cloud"?
  • Hmmm, Dell provides a lot of hardware to Rackspace. Rackspace has an OpenStack implementation offering.
  • by applematt84 ( 1135009 ) on Monday May 20, 2013 @04:20PM (#43776227) Homepage
    Building and maintaining a public cloud offering is not cheap, nor is it easy. I was laid off from my last job due to the shortsightedness of the management staff. When I started asking for licensing and support from the vendors due to unforeseen issues, as well as additional equipment due to the growth rate, the management staff realized they couldn't do it as cheaply as they wanted. I have experience building an IaaS product, and that experience tells me to just let someone else deal with it that already has the issues figured out. Linode and Rackspace are great examples. In addition, if one wants to offer a custom portal for their clients, then I suggest you write an interface that uses your vendor's API and call it a day. 'nuff said.
    • by atom1c ( 2868995 )
      And for Dell's part, they also realized that cooking the books wouldn't help their overall financial position without pulling a CA-style fraud.

      After all, their OpenStack unit would have to buy equipment (presumably Dell servers), but that's just shuttling dollars from one P&L to another. They would surely need more customers footing that bill before rolling their own -- which, mark my words, is what they'll do once their P&L statements allow them.

      Until that time, they'll just let the partners
    • by mysidia ( 191772 )

      And if Linode/Rackspace's nearest datacenters are so far from your geography, that the latency is too high for internal business apps?

      • You have private clouds confused with public cloud offerings. You are thinking about a private cloud, not an IaaS public cloud. If you have the funds and resources, then by all means, build yourself a private cloud using VMware, XenServer or KVM. A public cloud offering IaaS product involves offering a web portal for your clients to build their own VMs ... like what Linode, Rackspace, etc. offer. If you are really concerned about latency then a private cloud would be the best solution. If you are using an a
        • by mysidia ( 191772 )

          If you are really concerned about latency then a private cloud would be the best solution.,

          Ah, but you see... It's not about private clouds... it's not me alone that is concerned about latency... it would be my customers that would be considering using a cloud service for their internal servers, because there are no big datacenters nearby, but my datacenter is nearby...

          The big cloud providers' datacenters are far-away net-wise, so I ought to be able to service some latency-sensitive workloads

          • I still think you have private and public clouds confused. A private cloud would be a single physical server on-premises, or uplinked to the clients office from a datacenter via MPLS circuit, that is managed by a single client like XenCenter (XenServer), vSphere (VMware) or System Center (HyperV). This allows one to spin up multiple VMs that would logically sit on their internal network and be perfect for low-latency, internal applications.

            A public cloud offering is where you have a scaleable cluster of
            • by mysidia ( 191772 )

              A private cloud would be a single physical server on-premises, or uplinked to the clients office from a datacenter via MPLS circuit

              The private/public distinction seems totally artificial then.

              Does it really matter whether their internet service is residing in a VRF, with IP space routed to a VLAN on the virtualization cluster, or whether the end user has a site-to-site VPN solution, as if a VPN suddenly makes it public?

              Is the distinction private/public not totally artificial?

              Of course there sh

  • by evilviper ( 135110 ) on Monday May 20, 2013 @06:11PM (#43776979) Journal

    Could it be that Dell discovered the hard way that their servers are, in-fact, too expensive? Companies like Dell and HP are seeing declining server sales due to projects like OpenCompute that are bypassing 1st tier vendors and going straight to ODMs for simpler, cheaper servers. Some of the companies buying these cheap servers include cloud service providers like Amazon.

    Obviously Dell can't do that with their own in-house offerings, so perhaps they just couldn't compete with vendors running on cheaper servers.

    • by eap ( 91469 )

      ...Obviously Dell can't do that with their own in-house offerings, so perhaps they just couldn't compete with vendors running on cheaper servers.

      Dell's public cloud problem wasn't hardware. Cloud providers buy hardware before building the service. Dell failed to stand up a live OpenStack public cloud. HP and Rackspace already have theirs running with real customers.

      Building a public cloud is hard. It takes either a big company with lots of resources, or a smaller dedicated company with good funding. Both require long term commitments.

  • by Anonymous Coward

    While I recognize that Dell's failure in the industry doesn't indict Openstack, it's really not that good.

    Every well known provider either doesn't use it, or at best uses it in a token fashion to appear 'open'. The reason is pretty straightforward, it's functional scope is sufficiently limited that each vendor is just as well off writing their own private solution. It actually takes less work to charge forward with your own implementation than go through the hoops of coordinating with a wider community c

  • So they've finally realized that OpenStack is just a death-knell for the IaaS industry. It commoditizes it and enables a race to the bottom, like it earlier happened with web hosting and later with individual VPS hosting. A couple of years from now and we're going to be swamped by small companies offering OpenStack-based clouds.

    And so instead of trying to capitalize on their own server production unit and compete on price, Dell's going to try and differentiate themselves using some half-assed proprietary
  • I was working with a company who signed a contract with dell to have people start implementing "private clouds" on the Microsoft platform. I think they realized that most organization need more control over their data due to regulations and solutions like this may not meet those needs.

It is not for me to attempt to fathom the inscrutable workings of Providence. -- The Earl of Birkenhead