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

    XCP-ng 8.3 public alpha πŸš€

    Scheduled Pinned Locked Moved News
    264 Posts 43 Posters 179.3k Views 39 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.
    • olivierlambertO Offline
      olivierlambert Vates πŸͺ Co-Founder CEO @jameso
      last edited by

      @jameso said in XCP-ng 8.3 public alpha πŸš€:

      Installed. XCP-ng Center 20.04.01 not compatiable 😞

      It's not an officially supported client so it's normal, except if someone in the community make that change πŸ™‚

      1 Reply Last reply Reply Quote 0
      • stormiS Offline
        stormi Vates πŸͺ XCP-ng Team @AlexanderK
        last edited by

        @AlexanderK said in XCP-ng 8.3 public alpha πŸš€:

        @stormi we should inform cloudstack team about the upgrade.....

        Yes. Don't hesitate to contact them. I'm not sure they'll support an alpha release, but maybe they can be convinced to.

        1 Reply Last reply Reply Quote 0
        • AnonabharA Offline
          Anonabhar
          last edited by

          Ohh.. Cool.. If I upgrade my lab machine by ISO, will subsequent updates be done by yum or will I have to update by ISO again (and again) ?

          1 Reply Last reply Reply Quote 0
          • stormiS Offline
            stormi Vates πŸͺ XCP-ng Team
            last edited by

            You will be able to update with a simple yum update (and the usual toolstack restart or reboot depending on the updated components).

            1 Reply Last reply Reply Quote 0
            • stormiS Offline
              stormi Vates πŸͺ XCP-ng Team
              last edited by

              The only promise I can't make - though there's a high chance it will actually be possible - is that you won't have to use the ISO at all for upgrading to the final release.

              1 Reply Last reply Reply Quote -1
              • R Offline
                rRobbie
                last edited by

                Thanks for making compatible with NUC10, much appreciated 😊

                1 Reply Last reply Reply Quote 3
                • C Offline
                  cocoon XCP-ng Center Team
                  last edited by

                  Congratulations for your new release!

                  I am very interested in new features, still waiting for raw storage devices, new xo and hopefully the job where I could revert a VM always to its latest snapshot ^^

                  I had short time today to try an Upgrade of an old VM (could have still been 7.6 in Virtualbox) and the installation went OK.

                  But no https available. Quickly checked on the host with netstat, only :80 was used.

                  Had not much time today, but found out port 443 might be planned to be used by stunnel, I tried to manually run stunnel with the config in etc, but got an error about a too short key or something.

                  I will do a fresh installation next to it in a new vm and compare and troubleshoot tomorrow if possible.

                  1 Reply Last reply Reply Quote 1
                  • olivierlambertO Offline
                    olivierlambert Vates πŸͺ Co-Founder CEO
                    last edited by

                    Port 443 should work with XO Lite by default πŸ€”

                    C 1 Reply Last reply Reply Quote 0
                    • C Offline
                      cocoon XCP-ng Center Team @olivierlambert
                      last edited by cocoon

                      @olivierlambert
                      Yes that's what I expected because of course I wanted to try XO Lite, but had no chance to see it today.

                      Port 80 seems to automatically redirect to https if opened in a Browser, but I will analyse as soon as possible and report what I find.

                      1 Reply Last reply Reply Quote 0
                      • olivierlambertO Offline
                        olivierlambert Vates πŸͺ Co-Founder CEO
                        last edited by

                        There's no redirect for now in XCP-ng, are you sure it's the right IP address?

                        C 1 Reply Last reply Reply Quote 0
                        • C Offline
                          cocoon XCP-ng Center Team @olivierlambert
                          last edited by cocoon

                          @olivierlambert you're right, there was an error message, no redirect! Something like access denied or similar ...

                          1 Reply Last reply Reply Quote 0
                          • J Offline
                            jameso
                            last edited by

                            I did not know about XO Lite. Impressive.

                            1 Reply Last reply Reply Quote 1
                            • A Online
                              Andrew Top contributor @stormi
                              last edited by

                              @olivierlambert @stormi Thanks for the shot out in the blog post! I'm happy to help.

                              I think 8.3 has gone a little crazy with the purple theme... but that's not a functional issue.

                              ISO 8.3 installs/upgrades have worked fine so far on anything I have tried that ran XCP 8.2. I'll have some more time soon to do better testing.

                              Thanks for the ongoing quality work on open source software.

                              ajpri1998A 1 Reply Last reply Reply Quote 1
                              • ajpri1998A Offline
                                ajpri1998 @Andrew
                                last edited by

                                @Andrew said in XCP-ng 8.3 public alpha πŸš€:

                                I think 8.3 has gone a little crazy with the purple theme... but that's not a functional issue.

                                I wasn’t going to say it myself but I agree. Personally it doesn’t matter as long as it works… but it’s a LOT of purple.

                                1 Reply Last reply Reply Quote 0
                                • ForzaF Offline
                                  Forza
                                  last edited by

                                  Great to see the next iteration of XCP-ng πŸ™‚

                                  What is the status on the base OS choice for XCP-ng instead of CentOS?

                                  olivierlambertO 1 Reply Last reply Reply Quote 0
                                  • C Offline
                                    cocoon XCP-ng Center Team
                                    last edited by

                                    So still have the problem today on the upgraded VM that no https is available.

                                    I installed a new VM now and there it works and I found these differences, looks like the /etc/xensource/xapi-ssl.pem file is too old.

                                    FRESH NEW VM:
                                    new-vm-001.png
                                    new-vm-002.png

                                    UPGRADED VM:
                                    https-002.png
                                    https-003.png
                                    https-005.png

                                    psafontP 1 Reply Last reply Reply Quote 0
                                    • olivierlambertO Offline
                                      olivierlambert Vates πŸͺ Co-Founder CEO @Forza
                                      last edited by

                                      @Forza As explained in the blog post, no big change on that aspect so far. The goal is to build a new version that will be used as a base for more changes later. The biggest change is probably related to XAPI (huge bump)

                                      ForzaF 1 Reply Last reply Reply Quote 0
                                      • ForzaF Offline
                                        Forza @olivierlambert
                                        last edited by

                                        @olivierlambert OK thanks for the info. What is the plan for leaving the old CentOS 7?

                                        1 Reply Last reply Reply Quote 0
                                        • olivierlambertO Offline
                                          olivierlambert Vates πŸͺ Co-Founder CEO
                                          last edited by

                                          The plan is to first be able to use a more recent Xen version (matters the most), then to upgrade the kernel. CentOS 7 is indeed old, but only used for non-critical pieces. Remember, we do NOT use a kernel or Xen made by CentOS, but by XenServer and us.

                                          Also, before moving to something more recent in terms of distro, we have to finish to upgrade all the Python 2 code to Python 3 (among other thing). So it's kind of "hardest" task and lower priority vs "new Xen" and "new kernel" πŸ™‚

                                          R 1 Reply Last reply Reply Quote 1
                                          • psafontP Offline
                                            psafont @cocoon
                                            last edited by

                                            @cocoon
                                            The best thing we can do here is inspect the actual certificate:
                                            Please run openssl x509 -text -noout -in /etc/xensource/xapi-ssl.pem

                                            xenserver has generated host certificates with 2048-bit RSA keys for years, these should be able to be loaded by stunnel (through openssl) just fine.

                                            If the key is smaller that this then the fix is easy: generate a new certificate for that host: xe host-refresh-server-certificate host uuid=<>
                                            Be mindful that clients that trusted the previous certificate will need to trust the new one in order for the TLS connections to be established

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