XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Gracefully "Ask" XO to Reboot After Tasks Are Done

    Scheduled Pinned Locked Moved Xen Orchestra
    8 Posts 2 Posters 485 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • JSylvia007J Offline
      JSylvia007
      last edited by

      Howdy - So I schedule automated updates and reboots for my homelab early on Saturday mornings. I've seen some things that this could be dangerous as there are possibilities that XO might be running tasks that would die if the machine reboots under it.

      Is there a way to "ask" or inform XO that a reboot is required and to stop processing tasks until the system boots back up, or is it sufficient to just NOT schedule anything that could bump into that update/reboot timeframe?

      1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        Hi,

        Can you be more specific on how you schedule automated updates and reboots? (and what do you reboot exactly)

        JSylvia007J 1 Reply Last reply Reply Quote 0
        • JSylvia007J Offline
          JSylvia007 @olivierlambert
          last edited by

          olivierlambert - So I use Rundeck to schedule the commands apt-update, apt full-upgrade, apt autoremove, and then a vm reboot after that's all successfully completed. I have about a dozen VMs, and that's the process for all of them.

          I also don't have any tasks scheduled within XO (with the exception of XO pool metadata & XO Config). It runs everyday at 9am, so that wouldn't conflict.

          The Saturday update/reboot cycles start at around 3am, and take about an hour to complete through the 12 VMs.

          1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by

            Anything you do inside your "regular" VMs won't have any impact on XO. A reboot could cause maybe some wait for the VM to be actually snap before doing a backup, but no biggie.

            Are you talking about rebooting XO VM itself based on a schedule?

            JSylvia007J 1 Reply Last reply Reply Quote 0
            • JSylvia007J Offline
              JSylvia007 @olivierlambert
              last edited by

              olivierlambert said in Gracefully "Ask" XO to Reboot After Tasks Are Done:

              Are you talking about rebooting XO VM itself based on a schedule?

              Yes. All the other VMs are fine, but this is another VM just like the others that needs to be updated, patched, etc. So I want to add that to the automated updates, but I don't want to screw up XO in the process.

              1 Reply Last reply Reply Quote 0
              • olivierlambertO Offline
                olivierlambert Vates 🪐 Co-Founder CEO
                last edited by olivierlambert

                If you have running backups, yes, that will interrupt them. Otherwise, there's no risk to restart the VM with XO server running into it.

                JSylvia007J 1 Reply Last reply Reply Quote 1
                • JSylvia007J Offline
                  JSylvia007 @olivierlambert
                  last edited by

                  olivierlambert - Awesome! Thanks.

                  And Oliver, as a Founder and CEO, man are you connected to your product. Don't ever change!!

                  1 Reply Last reply Reply Quote 0
                  • olivierlambertO Offline
                    olivierlambert Vates 🪐 Co-Founder CEO
                    last edited by

                    That's how I can make the choices to improve it into the right direction 🙂

                    1 Reply Last reply Reply Quote 2
                    • First post
                      Last post