DO Ideas 2

Implement OpenStack as backend

Cloudwatt, DreamCompute, eNocloud, HP, and Rackspace already implement it, It should be the the standard for cloud servers.

  • Jorge Sol√≥rzano
  • Sep 11 2018
  • Will not implement
  • Sep 11, 2018

    Admin Response

    Thanks for the suggestion, when we first started DigitalOcean we looked into the open source alternatives and didn't feel that they quite fit the bill for what we were creating. While OpenStack is great any large open source project also has its own set of issues and as a number of core contributors to OpenStack have openly discussed there are some issues with how the OpenStack project is being managed by Rackspace and the influence that they have over it. That was one of our initial concerns when we first started, that a competitor would have directional control over the open source project. We decided to build our own stack and we feel that it was the right choice for us. Thanks!
  • Attach files
  • Rene Ras commented
    September 11, 2018 19:27

    I sincerely believe in the philosophy of Digital Ocean. But by actually building your own closed-source API is not only forcing your customers to use a solution to your likings but furthermore it is a form of vendor lock-in. I didn't expect this from DO. I would greatly appreciate the reconsideration of providing DO customers with options instead of limitations.

  • Tom Fifield commented
    September 11, 2018 19:27

    Hi Moisey,

    OpenStack is actually managed by an non-profit Foundation that is a fully independent legal entity, with its own board of directors (all IP was transferred from RAX in 2012). The OpenStack Foundation is currently supported by more than 450 companies - only one of which is Rackspace - and its bylaws are designed such that it is not possible for one company to have undue influence over the governance or the software.

    Completely understand your investment in an underlying framework. Though, if you do ever get any time, the OpenStack community, would love to hear more about your experiences in designing cloud infrastructure. Regarding this specific request for an OpenStack-compatible API, there's also this working group set up recently to improve up the API that could really benefit from any feedback on what you look for in a decent API https://wiki.openstack.org/wiki/API_Working_Group

    - Tom@OpenStack

  • Brian Capouch commented
    September 11, 2018 19:27

    I am just now finding this thread and I think the time is perfect for DigitalOcean to consider the value of adopting OpenStack as primary to their custom API.

    Yesterday I was able to spin up a droplet with Vagrant managing all the configuration for me. In theory (not yet in practice) I have all the power of the Vagrant interfaces to provisioning agents to help me manage a cloud farm with your company. This is great because of your sophistication, easy administration, and especially extremely reasonable pricing model.

    I am in the early stages of honing my awareness of all the Xs and Os, but the enormous value of conforming to the OpenStack standardization efforts needs careful examination. I think it would be very good for your business as well as positioning you in front of a lot of potential customers who, like me, are committed to developing only according to open design and coding principles.

  • Rob Romano commented
    September 11, 2018 19:27

    Over time it seems harder and harder to run a custom stack. Many features will continue to bundle with OpenStack such as better security, object storage, attachable disks, etc. etc. I think you will have to convert over at some point. Yes, too early means unstable and hard to manage. Too late means more work and more servers to migrate or continue to support on the old platform.

  • Anonymous commented
    September 11, 2018 19:27

    how to convert the image GUID in eNoCloud to Amazone format of ami number like "ami-23454".

  • Moisey Uretsky commented
    September 11, 2018 19:27

    Hey James,

    Unfortunately being compatible with other APIs creates a bit of an overhead but there are a lot of great projects out there that wrap APIs and provide simple hooks to deploy to various clouds, and the developer adoption has been great so I'm sure someone will roll this out sooner or later :)

  • James Brechtel commented
    September 11, 2018 19:27

    If nothing else, an OpenStack compatible API would be great.

  • Jorge Sol√≥rzano commented
    September 11, 2018 19:27

    Is good to know that you are promoting data portability, but I really believe that following the principles of Open Source is a good choice even for the people behind Digital Ocean, just like the openstack page said:

    Why open matters: All of the code for OpenStack is freely available under the Apache 2.0 license. Anyone can run it, build on it, or submit changes back to the project. We strongly believe that an open development model is the only way to foster badly-needed cloud standards, remove the fear of proprietary lock-in for cloud customers, and create a large ecosystem that spans cloud providers.

    Yes, you can focus on running your own stack, but using openstack you can get a global community of developers and collaborate to grow the open compute/cloud initiative. Most people don't care much about the backend if you provide them with access to their data, but you can probably benefit of joining into a global collaborative ecosystem, and by that end, offer a better user service :-)

  • Moisey Uretsky commented
    September 11, 2018 19:27

    We looked into OpenStack but at the time it wasn't really production ready.

    It's developed a lot since then but we are running our own stack.

    We will be promoting the Open Compute/Cloud initiative by giving our customers direct access to their snapshots for download so they can have data portability at which point it doesn't really matter what stack is being run, as its their data / virtual servers that are the key.

    Much like with Facebook, them being Open isn't about open sourcing their code but about giving people access to their data, to export it easily, to destroy it easily, etc. and that's the direction we are looking to head.

    But we'd love to hear more on this.