For Droplets still running with external kernels, we import new ones on a regular basis as they are released. If you happen to need one that hasn't been imported yet, just open a support ticket and the team will do so.
What's exactly does this mean? Could you please post the link to the documentation page that explains how?
Only some of the older images still use the old method of selecting the kernel from the Control Panel. The rest that Andrew mentioned use the bootloader and kernel from the droplet's image itself.
http://digitalocean.uservoice.com/forums/136585-digitalocean...
Far more egregious is that they silently drop port 25 on IPv6. This means that enabling IPv6 will cause mail problems for some destinations (destinations that support IPv6, like Google). When asked they say it's because a /64 is too much address space in the hands of potential (ab)users. This fails to understand that an IPv6 /64 is conceptually similar to an IPv4 /32. (In fact, there are pretty reasonable arguments for assigning IPv6 /56s or /48s with the same semantics as how IPv4 /32s are assigned.)
That is on circa 600,000 emails per month sent to gmail.
You are using your users' gmail credentials? Or are you simply delivering over 587 the same as you would over 25?
If you've got a DoS issue, you definitely need a 3rd party DoS protection service. Cloudflare free works pretty well
This is pretty bad compared to an AWS VPC -- you basically have to manage and sync your own iptables between all your nodes.
If you're doing that defense in depth on a physical network, I'm impressed by your dedication but would avoid your work for wasting resources.
Might be a good time to mention we're hiring network engineers as well:
https://www.digitalocean.com/company/careers#software-engine...
How many people run custom kernels?
I have used a kernel with realtime extensions enabled but that was a very special case and wouldn't run that in a VM anyway.
It's your virtual machine. You should be able to pick a kernel. This isn't for running Andrew Morton patches, as some of the comments imply.
Is there a good reason they can’t automatically add all new kernels from the major distributions?
I read "custom kernel" as in "replace distro-supplied kernel and compile your own with some custom flags and patches".
How many people want to run an updated kernel without known security vulnerabilities? Or with fixes to relevant issues?
How many people call that "a custom kernel"? Haven't heard anybody call an upstream distro kernel update a "custom kernel".
Is this a typical conversation people have?
"Hey Jim, did you update the servers to get the latest OpenSSL security fixes? - Yap, I compiled and installed a custom kernel".
Maybe they need to run a better distro with faster security update response?
That is what custom means in this context. "Not yours." Read accordingly; you've made the same flawed point at several spots in this thread.
I thought they used KVM for some reason... But I guess if they use Xen they yeah, they are stuck with whatever kernel they get.
It's no longer true that Xen needs to mean managing the kernel outside the VM. PVGRUB can be specified as the 'kernel' to boot, which will chainload a grub which can be managed inside the VM, which lets you run any kernel you wish and manage the boot process as you would on a non-virtualized system.
Amazon uses Xen for their EC2 product, and as I understand they too now set people up with pvgrub.
This is really the only part of the list that I think has merit. I love Digital Ocean in general, but my own gripe is with their API and its lack of proper automatic key management:
https://digitalocean.uservoice.com/forums/136585-digitalocea...
Right now, Debian 8, Ubuntu 15.04, Ubuntu 15.10, Fedora 23 and FreeBSD all allow you to control your kernel version. The next LTS release of Ubuntu in April, 16.04, will also allow you to customize your kernel.
Huh? I made a droplet just a week ago and it was assigned a whole /64. Maybe this is only a recent change, but you should know that it's here now.
> 1. Your private IP addresses are accessible by everyone in the same datacenter.
This is also the case at Linode. Besides AWS VPC, are there VPS providers that give your hosts their own private VLAN?
I have no affiliation with them.
With near-zero traffic on my interface - and for an internally facing VM, the IP address of which has never been published in any DNS, their DDoS 'protection' system decided I was under DDoS attack and blackholed my IP with their upstreams. I investigated and my conclusion is that the most likely cause was that their system mis-idenfied the overlay networking software I was using (which communicates over UDP) as DDoS traffic.
I raised this issue with support, who did not manage to help. Amongst other things, they told me that they didn't retain logs long enough to be helpful. I agreed that I would raise the issue with them again should it re-occur.
The second time they blackholed my IP, they didn't even bother telling me. And when I filed a support ticket, they took somewhere around an hour to even respond - during the time they've taken my system offline, I expect them to make themselves available.
When I tried calling their parent company on the phone, they were downright rude with me. I understand they don't usually do phone support, and that's fine, but if you've told me that (A) you can only help me resolve a problem during an incident because you don't keep logs, and (B) don't make yourself available to me through your regular support channels, don't get pissy with me for phoning you. And especially don't completely refuse to do anything remotely helpful.
I ended up terminating the VM and moving that workload elsewhere. I don't have time to be fixing other people's networks, especially when they can't be bothered to participate in the process.
It's a shame, because their BGP & AnyCast stuff looked really interesting, and I'd love to explore their offerings more. But I don't currently have confidence I can deploy anything with them in production, because when something goes wrong with their service, they don't appear competent at making themselves available to fix things.
(For the record, in some respects I consider one of my companies to be a competitor to both Digital Ocean & Vultr. But I like to be familiar with the competition, so I use them for some things. It also provides us a way to put workloads in locations we wouldn't otherwise be able to justify.)
No custom kernel support
1. Digital Ocean does not allow you to run your own kernel natively.
2. Digital Ocean droplet kernels are infrequently updated.
3. These kernels often contain relevant security vulnerabilities.
4. This has been a known issue since 2013.
5. You can kexec a kernel, but this is an annoying workaround.
https://www.digitalocean.com/community/questions/how-can-i-b...
Private networking is a joke
1. Your private IP addresses are accessible by everyone in the same datacenter.
https://www.digitalocean.com/community/tutorials/how-to-isol...
IPv6 support
1. Took forever to implement, and the timetable broke promises to customers.
2. Inferior. Digital Ocean still won't give you a /64 per standards.