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

    Air-gapped XOA Upgrade Process May Need Some Tweaking

    Scheduled Pinned Locked Moved Management
    5 Posts 2 Posters 157 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.
    • K Online
      kagbasi-ngc
      last edited by

      Good-day Folks,

      Happy Friday; I trust we're all in good health!

      BLUF: I believe the current XOA upgrade option for those of us whose environments fall under the Physical air gap only section of the Airgap support and deployment documentation, leaves us with a new appliance and no way to preserve the historical logs and/or artifacts of the existing AND approved XOA instance.

      In my environment, all hardware changes (i.e., new additions, modifications, removal, etc.) MUST go through a formal approval process - which almost always includes going through a Change Control Board (CCB) - yes, this includes any updates/upgrades to virtual machines. This process can often times take several days to weeks to complete. With the only upgrade option available, at this time, the imported VM is essentially a "new" virtual machine, thus, triggers the aforementioned CCB approval process. Additionally, I observed yesterday - after receiving an updated XOA image from support and importing it using the deploy script you provide - that although I was able to very easily export the XO-Config from the existing appliance and import it into the new appliance and essentially get back to the same configuration state (exception being some plugins had to be re-enabled), I was missing historical artifacts - most notably was the logs of the XOA appliance.

      Given the above explanation, is there any chance that Vates will consider providing a patching mechanism similar to how you handle XCP--ng (i.e., with an offline repo)? This way, we can download the relevant files, setup a repo on the air-gapped network, then patch the appliance - thus preserving it's historical artifacts AND identity, and most importantly, not triggering an approval process.

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

        Hi,

        Sure, we have plans to get offline patches ready, it's in our roadmap already. Pinging @julien-f so we are sure it could be prepared in the next months.

        It would be even better to make a support ticket because it will raise the priority 🙂

        K 1 Reply Last reply Reply Quote 0
        • K Online
          kagbasi-ngc @olivierlambert
          last edited by

          @olivierlambert Thanks for the response, that's good to know that you guys have this on the roadmap. I didn't raise a support ticket because I'm not a paying customer yet, so don't want to come off as exploiting resources that could be dedicated to your paying customers.

          That said, I will send this in via a support ticket. Thanks again.

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

            Without being a customer, you won't have access to the offline/airgap updates anyway. Anyway, this will come sooner than later, stay tuned!

            K 1 Reply Last reply Reply Quote 0
            • K Online
              kagbasi-ngc @olivierlambert
              last edited by

              @olivierlambert Aah, you got me there. Thanks for all the support thus far, really appreciate it.

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