Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It looks like Digital Ocean hopes to eventually support coreOS: http://digitalocean.uservoice.com/forums/136585-digital-ocea...

I can only find a tweet that linode is "considering" it: https://twitter.com/linode/status/488045339023532032

anyone have any other information re vps vendor support?



Vultr.com allows you to launch a VPS with your own uploaded ISO / image, so if you made one for CoreOS it'd probably work. They also support FreeBSD. I've been using them in their Los Angeles location for a while and have had no issues at all. Their costs are about the same as DO... basically a DO clone. I think there's an older hosting company behind them so it's not a basement operation.


We have some community contributed docs here: http://coreos.com/docs/running-coreos/cloud-providers/vultr


Just make sure you don't run into https://github.com/coreos/docs/issues/219 !


DO promises A LOT of features they do not deliver.


I personally think they will pull this one off, mainly because CoreOS will be providing support to the DO team and help however possible to make sure DO is added to the list of supported cloud vendors.


Ah yes, because FreeBSD hasn't offered their help already.


There's a big difference between a hope and a promise.


You can install CoreOS on Digital Ocean with the following script. https://github.com/ibuildthecloud/coreos-on-do


Don't get your hope up.

The #2 feature of all time requested is BSD support.

DO "started" this feature over a year ago.

http://digitalocean.uservoice.com/forums/136585-digitalocean...

Then on twitter recently they act like they aren't even working on BSD support.

https://mobile.twitter.com/digitalocean/status/4407445438564...

TLDR: DO over promises on features they will deliver

Edit: fixed link


You've read more into that tweet then I ever would, saying " we are a small startup with limited resources" doesn't really imply anything to me on whether they are or have been working on BSD support. Has DO made any promises about delivery date here? Did they imply anything that could be construed as "overpromising"? I mean any company or OS project has plenty of stuff they "have been working on" for many years, I wouldn't say they've overpromised on anything unless they made explicit commitments and failed to meet them.


When you official declare that you started a feature over 15 months ago and then provide no uodate on schedule or release - and this is just one if many times they so this, you begin to feel like these features they promise too will never happen.


> Alex Polvi stopped by our office a couple of weeks ago and we spoke about integrating CoreOS. He offered to provide a lot of additional support to get this rolled out including managing them images so that we can have official CoreOS images that are maintained by them when they are ready.

Given how their systems are laid out and spun up we discussed the changes that would be needed and it looks like the metadata service that we have begun writing solves a lot of the challenges.

> We’re moving this to planned stage, as soon as we finish the metadata service we can begin testing it internally around getting CoreOS as a supported distro in DigitalOcean.

Updated 15 July 2014

Looks pretty promising to me.


If anyone from Digital Ocean is reading this, please help if you can! A lot of developers really want to check out CoreOS, and having it supported on DO would help so much. Let us give you money!


Hey,

We are reading this and we will be helping soon. We met with Alex Polvi when he stopped our office a few weeks ago and we discussed integrating CoreOS.

Given how their file systems are laid out and a couple of other items on their side as well as that we are building out a metadata service that will be launching soon we thought it would be best to wait on the integration until after the metadata service was ready.

This way we could use it to integrate with CoreOS and make the deployment process a lot simpler.

Alex has been super helpful offering a lot of support to help us get this done and we are very excited to move forward, but we thought it would be better to do it right with the metadata service instead of launching it without that, knowing that we would have to rebuild the way the image was being provisioned and every early adopter of CoreOS would then need to redeploy their droplets.

Because we have a lot of projects in flight at the same time I don't have an ETA and we've certainly found it difficult to give product release estimates when we are also in high growth mode because there are always many interruptions and reprioritizations that happen on the fly every week but I'm hopeful that this one launching this quarter.

Thanks, Moisey




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: