Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Upcoming KernelCare OpenVZ patch available: ms/hrtimer: Backport CLOCK_BOOTTIME feature ...
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Upcoming KernelCare OpenVZ patch available: ms/hrtimer: Backport CLOCK_BOOTTIME feature ...

FuslFusl Member
edited August 2015 in General

I have just been notified by Igor from KernelCare that a patch for backporting/implementing this

ms/hrtimer: Backport CLOCK_BOOTTIME feature, needed for latest systemd (#2937)

from the OpenVZ 042stab094.7 kernel will be released tomorrow and that this patch is available for testing by now already.

This patch essentially allows hardware nodes running an older version than 042stab094.7 to run OpenVZ containers with Debian 8 or Ubuntu 15.04 without issues.

Recent messages from Igor:

I am sorry about the delay -- it was very complex piece of code to patch, especially for older kernels, but it is ready now.

you can install it by running:

kcarectl --update --test

We should publish it to production by tomorrow.



Just in case, you might want to disable auto-update until tomorrow, so it wouldn't revert to the version in production (when we push it to production)

To do that, please edit:

/etc/sysconfig/kcare/kcare.conf

and change AUTO_UPDATE to False

Thanked by 2William Damian

Comments

  • Hey @Fusl

  • Awesome. We'll no longer need to migrate customers to newer servers to have their Ubuntu 15 or Debian 8 work.

    Thanked by 1Nick_A
  • @Damian said:
    Awesome. We'll no longer need to migrate customers to newer servers to have their Ubuntu 15 or Debian 8 work.
    @Damian said:
    Awesome. We'll no longer need to migrate customers to newer servers to have their Ubuntu 15 or Debian 8 work.
    @Damian said:
    Awesome. We'll no longer need to migrate customers to newer servers to have their Ubuntu 15 or Debian 8 work.

    Out of curiousity, wouldn't like 30min of planned downtime on your older nodes be better than manually migrating every customer that wants to run newer OS's?

  • wychwych Member

    @Jonchun said:
    Out of curiousity, wouldn't like 30min of planned downtime on your older nodes be better than manually migrating every customer that wants to run newer OS's?

    Not if that client has no interest in Ubuntu 15 or Debian 8.

  • sinsin Member

    Sweet!

  • DamianDamian Member
    edited August 2015

    Jonchun said: Out of curiousity, wouldn't like 30min of planned downtime on your older nodes be better than manually migrating every customer that wants to run newer OS's?

    We run Kernelcare on everything to keep them up to date. Regarding customers that want to run Debian 8 or Ubuntu 15, there's been very few, maybe one or two a day, and....

    wych said: Not if that client has no interest in Ubuntu 15 or Debian 8.

    Mr. Wych has it down: I'm not going to subject an entire node of content and happy clients to arbitrary downtime so one client can run a newer OS.

  • Nick_ANick_A Member, Top Host, Host Rep

    Damian said: Awesome. We'll no longer need to migrate customers to newer servers to have their Ubuntu 15 or Debian 8 work.

    This.

  • Damian said: I'm not going to subject an entire node of content and happy clients to arbitrary downtime so one client can run a newer OS.

    That's what the health sector thinks too - the result, many still use Java 1.5 and .Net 2.0.

  • FuslFusl Member

    Patch has just been officially released:

    New patchset adds kernel feature needed to boot up containers with Debian 8 for older VZ kernels.



    Systems with AUTO_UPDATE=True (DEFAULT) in /etc/sysconfig/kcare/kcare.conf will automatically update, and no action is needed for them.



    You can manually update the server by running:

    /usr/bin/kcarectl --update



    Changelog:



    PSBM-27933 proc: reject ve context change of perm of node's proc files

    Add support of CLOCK_BOOTTIME for clock_gettime. Required for systemd > 212, Debian 8 templates

Sign In or Register to comment.