(Fairly new user of Kimchi, with first impressions)

Is there a good location for documentation?

It seems difficult to make a new ISO available, or I chose a poor way. - I downloaded from an FTP site requiring non-anonymous authentication - I scp'd it to root@host - I tried to use it from there, but I got permission denied "KCHISO0008E: The hypervisor doesn't have permission to use this ISO /root/..." - the message above recommends copying the file to /var/lib/libvirt, but I think you actually have to copy it to /var/lib/libvirt/images - you also need to "chown qemu" the ISO image After the above steps, it finally became visible and usable.

Further feedback: - The above error message appears as a bright pop-over with a nice 'X' for dismissing, but it automatically disappears so quickly, it's impossible to read the entire message

- in the "Edit Template" dialog, what is "CPU Number"? I presume that is "number of (virtual) processors"?

- in the "Edit Template" dialog, what are the units for "Memory"? It is apparently megabytes, but that should be noted

Regards, Paul Clarke, IBM _______________________________________________ Kimchi-devel mailing list Kimchi-devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel

On 6/5/2014 10:53 AM, Paul Clarke wrote: > (Fairly new user of Kimchi, with first impressions) > > Is there a good location for documentation? Global product 'help' and 'about' should be visible all the time at the header. Design should be changed as below and move 'help' and 'about' content below help menu. > > It seems difficult to make a new ISO available, or I chose a poor way. > - I downloaded from an FTP site requiring non-anonymous authentication > - I scp'd it to root@host > - I tried to use it from there, but I got permission denied "KCHISO0008E: The > hypervisor doesn't have permission to use this ISO /root/..." > > - the message above recommends copying the file to /var/lib/libvirt, but I > think you actually have to copy it to /var/lib/libvirt/images > > - you also need to "chown qemu" the ISO image > > After the above steps, it finally became visible and usable. For current kimchi security model design, root users on behalf of console administrator, they are responsible for 1. host setup for virtualization infrastructure and console administration 2. virtualization resources setup I think this process should be streamlined for better user experience. I recommend to make "chown qemu" transparent with kimchi to handle it automatically.

> > Further feedback: > - The above error message appears as a bright pop-over with a nice 'X' for > dismissing, but it automatically disappears so quickly, it's impossible to > read the entire message should be controlled by user. > > - in the "Edit Template" dialog, what is "CPU Number"? I presume that is > "number of (virtual) processors"? > > - in the "Edit Template" dialog, what are the units for "Memory"? It is > apparently megabytes, but that should be noted > > Regards, > Paul Clarke, IBM > > _______________________________________________ > Kimchi-devel mailing list > Kimchi-devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/kimchi-devel > _______________________________________________ Kimchi-devel mailing list Kimchi-devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel

>> It seems difficult to make a new ISO available, or I chose a poor way. >> - I downloaded from an FTP site requiring non-anonymous authentication >> - I scp'd it to root@host >> - I tried to use it from there, but I got permission denied "KCHISO0008E: The >> hypervisor doesn't have permission to use this ISO /root/..." >> >> - the message above recommends copying the file to /var/lib/libvirt, but I >> think you actually have to copy it to /var/lib/libvirt/images >> >> - you also need to "chown qemu" the ISO image >> >> After the above steps, it finally became visible and usable. > > For current kimchi security model design, > root users on behalf of console administrator, they are responsible for > 1. host setup for virtualization infrastructure and console administration > 2. virtualization resources setup > > I think this process should be streamlined for better user experience. > I recommend to make "chown qemu" transparent with kimchi to handle it automatically. The user also has to add "x" for QEMU on each level of the directory that contains the ISO image. Though this can be done by Kimchi automatically, it's possible that the user accidentally revokes the "x" from the directory and change the owner of the ISO image. The problem here is that the downloaded ISO is out of backend management. In this case, Kimchi is used as a desktop virtualization management soft. Libvirt already provides a "session" mode to solve desktop virtualization privilege problem. We can have the Kimchi backend create the VM in "session" mode, so that the VM gets the same privilege as the user, and it's able to read the ISO image. Another solution is that we provide an ISO upload interface to allow user to upload the image from his home directory to Kimchi backend. Then Kimchi store the image in /var/lib/libvirt/images and take over the control. This solution keeps Kimchi in the server virtualization way, which is its original orientation, to compete with XXWare server.

On 06/05/2014 03:36 AM, Zhou Zheng Sheng wrote: >>> It seems difficult to make a new ISO available, or I chose a poor way. >>> - I downloaded from an FTP site requiring non-anonymous authentication >>> - I scp'd it to root@host >>> - I tried to use it from there, but I got permission denied >>> "KCHISO0008E: The >>> hypervisor doesn't have permission to use this ISO /root/..." >>> >>> - the message above recommends copying the file to /var/lib/libvirt, >>> but I >>> think you actually have to copy it to /var/lib/libvirt/images >>> >>> - you also need to "chown qemu" the ISO image >>> >>> After the above steps, it finally became visible and usable. >> >> For current kimchi security model design, >> root users on behalf of console administrator, they are responsible for >> 1. host setup for virtualization infrastructure and console >> administration >> 2. virtualization resources setup >> >> I think this process should be streamlined for better user experience. >> I recommend to make "chown qemu" transparent with kimchi to handle it >> automatically. > > The user also has to add "x" for QEMU on each level of the directory > that contains the ISO image. Though this can be done by Kimchi > automatically, it's possible that the user accidentally revokes the "x" > from the directory and change the owner of the ISO image. The problem > here is that the downloaded ISO is out of backend management. > > In this case, Kimchi is used as a desktop virtualization management > soft. Libvirt already provides a "session" mode to solve desktop > virtualization privilege problem. We can have the Kimchi backend create > the VM in "session" mode, so that the VM gets the same privilege as the > user, and it's able to read the ISO image. > > Another solution is that we provide an ISO upload interface to allow > user to upload the image from his home directory to Kimchi backend. Then > Kimchi store the image in /var/lib/libvirt/images and take over the > control. This solution keeps Kimchi in the server virtualization way, > which is its original orientation, to compete with XXWare server. This may be complicated by limitations of HTTP. There may be some sort of maximum size permitted which is at or below the typical size of an Linux installation ISO image. I'm not knowledgeable in that area, but I've seen issues like that.

Regards, Paul Clarke _______________________________________________ Kimchi-devel mailing list Kimchi-devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel

The issues you mentioned are: 1. There is no convenient way to upload a image. 2. When image is uploaded, too complex to fix its permission and get it work. 3. Warning msg disappear too quickly to see. As 1 and 2 are related to a feature I'm working on, I want to share with you our proposal and see if you like it from view of user: 1. convenient way to upload image: (1) As flow of : ISO server--download-->your laptop--upload-->your server is too long, we will supply with a dialog to let users to fill a web link and kimchi server will downloaded from the ISO server. So the flow becomes: ISO server--download-->your virtualization server number of download sessions will be limited.

(2) An upload interface will also be provided if you want to upload ISO from your laptop. also number of sessions will be limited

2. complex permission fix problem: A dedicate directory will created for ISOs, and this directory will be monitored, if an ISO is scp to this directory, monitor will call a script to change permission.

and for 3, I think we can add a box to store historical error msg (10 items restored), so that user won't miss the latest ones.

(Fairly new user of Kimchi, with first impressions) Is there a good location for documentation? It seems difficult to make a new ISO available, or I chose a poor way. - I downloaded from an FTP site requiring non-anonymous authentication - I scp'd it to root@host - I tried to use it from there, but I got permission denied "KCHISO0008E: The hypervisor doesn't have permission to use this ISO /root/..." - the message above recommends copying the file to /var/lib/libvirt, but I think you actually have to copy it to /var/lib/libvirt/images - you also need to "chown qemu" the ISO image

After the above steps, it finally became visible and usable. Further feedback: - The above error message appears as a bright pop-over with a nice 'X' for dismissing, but it automatically disappears so quickly, it's impossible to read the entire message - in the "Edit Template" dialog, what is "CPU Number"? I presume that is "number of (virtual) processors"? - in the "Edit Template" dialog, what are the units for "Memory"? It is apparently megabytes, but that should be noted Regards, Paul Clarke, IBM _______________________________________________ Kimchi-devel mailing list Kimchi-devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel

Hi Paul, Thanks for feedback of these issues. The issues you mentioned are: 1. There is no convenient way to upload a image. 2. When image is uploaded, too complex to fix its permission and get it work. 3. Warning msg disappear too quickly to see. As 1 and 2 are related to a feature I'm working on, I want to share with you our proposal and see if you like it from view of user: 1. convenient way to upload image: (1) As flow of : ISO server--download-->your laptop--upload-->your server is too long, we will supply with a dialog to let users to fill a web link and kimchi server will downloaded from the ISO server. So the flow becomes: ISO server--download-->your virtualization server number of download sessions will be limited. (2) An upload interface will also be provided if you want to upload ISO from your laptop. also number of sessions will be limited 2. complex permission fix problem: A dedicate directory will created for ISOs, and this directory will be monitored, if an ISO is scp to this directory, monitor will call a script to change permission. and for 3, I think we can add a box to store historical error msg (10 items restored), so that user won't miss the latest ones. Aline, If we are good with my proposal, can I add it to the plan of next print?

On 2014年06月05日 10:53, Paul Clarke wrote: > (Fairly new user of Kimchi, with first impressions) > > Is there a good location for documentation? > > It seems difficult to make a new ISO available, or I chose a poor way. > - I downloaded from an FTP site requiring non-anonymous authentication > - I scp'd it to root@host > - I tried to use it from there, but I got permission denied > "KCHISO0008E: The hypervisor doesn't have permission to use this ISO > /root/..." > > - the message above recommends copying the file to /var/lib/libvirt, > but I think you actually have to copy it to /var/lib/libvirt/images > > - you also need to "chown qemu" the ISO image > > After the above steps, it finally became visible and usable. > > Further feedback: > - The above error message appears as a bright pop-over with a nice > 'X' for dismissing, but it automatically disappears so quickly, it's > impossible to read the entire message > > - in the "Edit Template" dialog, what is "CPU Number"? I presume that > is "number of (virtual) processors"? > > - in the "Edit Template" dialog, what are the units for "Memory"? It > is apparently megabytes, but that should be noted > > Regards, > Paul Clarke, IBM > > _______________________________________________ > Kimchi-devel mailing list > Kimchi-devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/kimchi-devel >