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

    Still no new templates

    Scheduled Pinned Locked Moved News
    8 Posts 4 Posters 2.1k 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.
    • maxcernyM Offline
      maxcerny
      last edited by

      Re: XO Hub Template: what do you want next?

      Some new templates were promised quite a long time ago, any new info on this?

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

        fohdeesha is working on it

        1 Reply Last reply Reply Quote 0
        • fohdeeshaF Offline
          fohdeesha Vates 🪐 Pro Support Team @maxcerny
          last edited by

          maxcerny Indeed, the Ubuntu cloud-init template should be up by the end of this week (cloud-init has so many fun bugs to work around for these applications)

          maxcernyM 1 Reply Last reply Reply Quote 1
          • maxcernyM Offline
            maxcerny @fohdeesha
            last edited by

            fohdeesha great, any eta on debian 11 as well?
            btw, which bugs are you talking about? I had no trouble creating my own cloud-init images.

            fohdeeshaF 1 Reply Last reply Reply Quote 0
            • fohdeeshaF Offline
              fohdeesha Vates 🪐 Pro Support Team @maxcerny
              last edited by

              maxcerny I'm not sure on a debian 11 image, if it's been assigned to another team member it may be done very soon, if not I can probably get one created within the next week.

              As for bugs, take your pick. For a "vanilla" install it's not too bad, but a big can of worms gets opened when you add in an avenue to pass network information to the cloud-init instance - it either overriding your cloud-init.cfg and ignoring it, or not overwriting interfaces and just appending to it leaving a stale DHCP address and lease, not overriding resolvers that were set previously during the templating process, stuff like that. Then there's the fun stuff like /etc/cloud/cloud.cfg.d/99-installer.cfg and other files in this directory overriding the nocloud config even when explicitly commented out. Many of these things have been reported to the cloud-init project but it seems everyone has moved to Ignition (which I'd like to do in the future, but it would take a lot of rewriting on the XOA side). This GIST (not mine) sums up some of my feelings pretty well - https://gist.github.com/Informatic/0b6b24374b54d09c77b9d25595cdbd47

              ForzaF maxcernyM 2 Replies Last reply Reply Quote 0
              • ForzaF Offline
                Forza @fohdeesha
                last edited by Forza

                I'd like to see some new Alpine images 🙂 I find myself using Alpine more and more for VMs with single applications. This is partly because it is so lightweight on storage requirements (about 0.1GB for a fresh install with a small application) which makes managing it very easy, but also very simple start-up scripting with OpenRC. Alpine 3.15 is out since November 🙂

                1 Reply Last reply Reply Quote 0
                • maxcernyM Offline
                  maxcerny @fohdeesha
                  last edited by

                  fohdeesha I have also ran into a small issue even with the default install. The default cloudinit config doesn't include updating the /etc/hosts file with the local hostname.

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

                    There you go:

                    ubnttemp.png

                    It's available right now in your XOA, Hub section. Please test and report.

                    Note: there's a last thing we need to fix, but it's cosmetic only (VM/template name ends with "71" because we forgot to remove it before export)

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