DO Ideas 2

At a specific, recurring, reliable date and time (say one day a week, or even a month) add the latest kernel to the list

At the moment updating a VM kernel is touch and go. DigitalOcean's boot manager limitations mean that you can't install a kernel and reboot the machine into it. Instead you have to install a kernel (that exactly matches one available in the list) then select it from the dropdown in the admin interface. Many CentOS users update using yum update and bring all packages, including the kernel, up to the latest version.

That would be manageable (for 10s of 100s of VMs) if the list was frequently updated, but it's sporadic. The support team are very helpful and will update the hypervisor manually, if you:

1. shutdown the VM
2. post the kernel name in a support ticket
3. wait an indeterminable amount of time
4. restart the machine

That's not workable for dozens of VMs and/or production servers.

Please commit to regular, publicised updated times so that sysadmins can plan around them.

  • Anonymous
  • Sep 11 2018
  • Attach files
  • Ben commented
    September 11, 2018 17:11

    Actually, as an Ubuntu user, I haven't had much trouble. When Ubuntu updates a kernel, DO typically has the updated kernel available on the list the next day. I typically go through the update, then make an entry in my todo list to check the DO kernel list the next day (it's OK to reboot, as Ubuntu normally leaves the old kernel still on the machine - you're rebooting into the same kernel as you had before). Next day I check if the new kernel is on DO's kernel list, and if so (almost always), for each machine:

    1. Do the 'change kernel' command in the DO console
    2. Power off the machine from the command line.
    3. Power up the machine from the DO console.

    No interminable wait, no waiting on a response to a support ticket.

    There once was a time when (at least for Ubuntu) it could be awhile after a vendor kernel update before that kernel showed up on DO's kernel list. Lately, they seem to have their act together - as I said, the vendor's updated kernel shows up on the DO list the next day.

    The real solution for this is being able to boot from the in-VM kernel.

  • Anonymous commented
    September 11, 2018 17:11

    Would really like this.
    Got the same on Ubuntu, only able to get to 3.13, while 3.18 is avaible.

    Must say the support changed it really quick, but still would like to change it myself so i can change any moment and dont need to ask the support for every droplet.