Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FSunstone] multiple issues with image pool view #6380

Closed
3 tasks
dann1 opened this issue Nov 2, 2023 · 0 comments · Fixed by OpenNebula/docs#2803 or OpenNebula/docs#2804
Closed
3 tasks

[FSunstone] multiple issues with image pool view #6380

dann1 opened this issue Nov 2, 2023 · 0 comments · Fixed by OpenNebula/docs#2803 or OpenNebula/docs#2804

Comments

@dann1
Copy link
Contributor

dann1 commented Nov 2, 2023

Description
Given the following image list

root@ubuntu2204-kvm-qcow2-6-8-zm1vb-0:~# oneimage list
  ID USER     GROUP    NAME                                                                                                                  DATASTORE     SIZE TYPE PER STAT RVMS
   7 oneadmin oneadmin Windows 11                                                                                                            default        20G OS    No used    2
   3 oneadmin oneadmin Ttylinux - KVM                                                                                                        default       200M OS    No rdy     0
   0 oneadmin oneadmin alpine                                                                                                                default       256M OS    No rdy     0

FireEdge displays it like this

image

The problems are

  • none of the images are persistent
root@ubuntu2204-kvm-qcow2-6-8-zm1vb-0:~# oneimage show 0 | grep PERSISTENT
PERSISTENT     : No
root@ubuntu2204-kvm-qcow2-6-8-zm1vb-0:~# oneimage show 3 | grep PERSISTENT
PERSISTENT     : No
root@ubuntu2204-kvm-qcow2-6-8-zm1vb-0:~# oneimage show 7 | grep PERSISTENT
PERSISTENT     : No
  • the running VMs icon is displaying something/something like the 2/2 Windows image, when it should really be just an integer, ex. 2
  • Also maybe the image type (file for this images) could be displayed differently.
    • As it stands right now is displaying the type based on DISK_TYPES=%w{FILE CD_ROM BLOCK RBD}.
    • Instead it will probably be more informative to use IMAGE_TYPES=%w{OS CDROM DATABLOCK KERNEL RAMDISK CONTEXT BACKUP}
    • The problem is that there are FILE type images for FILE datastores, like the KERNEL and RAMDISK images. Having an icon mapping based on those will (most likely) result in a clearer example of what the image type actually is. The difference between FILE and RBD only matters to the hypervisor.

To Reproduce
View Image section under Storage section

Expected behavior

  • Persistency displayed based on image persistence
  • Running VMs should be just an integer
  • The image type icon displayed could be improved to avoid confusion

Progress Status

  • Code committed
  • Testing - QA
  • Documentation (Release notes - resolved issues, compatibility, known issues)
@dann1 dann1 added this to the Release 6.8.1 milestone Nov 2, 2023
@tinova tinova linked a pull request Nov 3, 2023 that will close this issue
@tinova tinova modified the milestones: Release 6.8.1, Release 6.8.2 Nov 21, 2023
dcarracedo added a commit to OpenNebula/docs that referenced this issue Jan 4, 2024
dcarracedo added a commit to OpenNebula/docs that referenced this issue Jan 4, 2024
@tinova tinova closed this as completed Jan 4, 2024
tinova pushed a commit to OpenNebula/docs that referenced this issue Jan 4, 2024
tinova added a commit to OpenNebula/docs that referenced this issue Jan 4, 2024
Signed-off-by: David Carracedo <[email protected]>
Co-authored-by: Tino Vázquez <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment