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

    Task list enhancement

    Scheduled Pinned Locked Moved Xen Orchestra
    4 Posts 3 Posters 533 Views 1 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.
    • J Offline
      jrubenc
      last edited by jrubenc

      Hello,

      It would be great adding 2 items to the "Task" part:

      • Size/Destination of the VDI when moving. As of now, the shown information is:

        Pool Name
        VDI Name - SR Size
        VM Name (Host)

        What I propose is:

        Pool Name
        VDI Name - VDI Size
        Origin SR (Size) -> Destination SR (Size)
        VM Name (Host)

        I guess something similar could be applied to a VDI copy operation.

      • Elapsed time in the task. This is shown in XenCenter and XO should be able to show it also. Sometimes is really useful when you're performing migration tasks and need to extrapolate elapsed time in certain tasks.

      Also, the "Previous tasks" part, it's quite clogged with unuseful (99.99% of the times) information like:

      • "SR.scan"
      • VM.update_allowed_operations
      • host_call_plugin
      • VDI.db_introduce
      • Async.SR.update

      all of them items that only show the host where they are occurring (except "SR.scan" which shows which SR is being scanned) and nothing else. Maybe those can be useful to debug some situation, but not for a daily working mode. I don't know.. maybe with some filters where those tasks would be hidden by default?

      To me, a definition of "Task" is something started on-demand, and not internal operations of Xen.

      Thanks for the great job 🙂

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

        Hi,

        Sadly, a task doesn't contain a lot of useful information. However, let me ping @julien-f and/or @pdonias to think about how to improve this 🙂

        1 Reply Last reply Reply Quote 0
        • julien-fJ Offline
          julien-f Vates 🪐 Co-Founder XO Team
          last edited by

          We don't to do special cases for some operations in XO 5, we'll revisit this in XO 6 which will bring the notion of XO tasks in addition to XAPI tasks.

          But we'll probably display the elapsed and estimated duration of the task though 🙂

          Regarding previous tasks, why do you need to hide some of them? How do you use these previous tasks?

          J 1 Reply Last reply Reply Quote 0
          • J Offline
            jrubenc @julien-f
            last edited by

            @julien-f said in Task list enhancement:

            We don't to do special cases for some operations in XO 5, we'll revisit this in XO 6 which will bring the notion of XO tasks in addition to XAPI tasks.

            But we'll probably display the elapsed and estimated duration of the task though 🙂

            Regarding previous tasks, why do you need to hide some of them? How do you use these previous tasks?

            Hello Julien,

            Well, it's not really that I use them. It's just that being so filled with information not useful most of the times, it's quite unusable (with all due respect for your great job). Example of what for? To see how much it lasted an already finished VM moving/copy operation.

            Displaying elapsed (and estimated, and I know this won't be always 100% accurante, but will be under normal circumstandes tho) would be great. After all, knowing the size of the object that it's being copied/moved, you can always extrapolate how much is remaining knowing how much it's lasting at any given moment.

            Thanks!

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