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

    Manual snapshots retention

    Scheduled Pinned Locked Moved Solved Management
    45 Posts 5 Posters 639 Views 4 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
      last edited by olivierlambert

      Yes, I get it. But that explains why the message is generic for VM removal (because it's the same that's a VM with snapshot true or false).

      I agree this could improved, but I'm not sure this worth the effort vs moving forward on XO 6/XO Lite πŸ€”

      Tristis OrisT M 2 Replies Last reply Reply Quote 1
      • Tristis OrisT Offline
        Tristis Oris Top contributor @olivierlambert
        last edited by

        @olivierlambert but on vm page it works as should.
        7a8f6642-2549-4486-8e89-21c3cf857b27-ΠΈΠ·ΠΎΠ±Ρ€Π°ΠΆΠ΅Π½ΠΈΠ΅.png

        1 Reply Last reply Reply Quote 0
        • M Offline
          manilx @olivierlambert
          last edited by manilx

          @olivierlambert Now I know that there is no risk πŸ˜‰ BUT it got me scared definitely. And probably will others.

          Also it's just a changing of a string so it should be easy.

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

            Not necessarily that easy, especially on a "legacy" code base, I truly wonder if we should invest some time on this instead of XO 6?

            M Tristis OrisT 2 Replies Last reply Reply Quote 0
            • M Offline
              manilx @olivierlambert
              last edited by

              @olivierlambert Your call Β―_(ツ)_/Β― πŸ˜‰

              1 Reply Last reply Reply Quote 0
              • Tristis OrisT Offline
                Tristis Oris Top contributor @olivierlambert
                last edited by

                @olivierlambert release this year? (c)

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

                  I don't understand the question πŸ€” XO 6 is already here and takes 90% of our XO front team load. Anything on XO 5 will slow down the number of features available in XO 6.

                  Tristis OrisT 1 Reply Last reply Reply Quote 0
                  • Tristis OrisT Offline
                    Tristis Oris Top contributor @olivierlambert
                    last edited by

                    @olivierlambert we are waiting for release)

                    at least it needs to be fixed in xo6.

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

                      Waiting for what? Just add /v6 to access XO 6. The "release" is just having XO 6 by default, but it's not like "now it's available". It is already the case.

                      For XO 6, since it will be very different, you won't have exactly the same way of doing things than XO 5, but yes, it should be better in any way πŸ™‚

                      M 1 Reply Last reply Reply Quote 0
                      • M Offline
                        manilx @olivierlambert
                        last edited by

                        @olivierlambert This feature was added not long ago anyway. Pity the text was put in this way.... The "concern" that it might scare others (did us) is valid as 99% use XO5 today.
                        So, perhaps you might save on support calls? My 2 cents anyway

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

                          I will let XO PO to decide about this. Pinging @lsouai-vates

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