Right, currently, we have in New Template window: * Local ISO Image * "Provide a File Path for a specific ISO image:" [] * Local Image File * File Path: [] * Remote ISO Image BACKEND: The idea is change backend in order it is able to analyze the file passed (if it is ISO or a disk .img) and automatically proceed with right processes. FRONTEND: (Need to think better here) Merge both "File Path" inputs, maybe. Something like: * Distributions ISO Images: * Local: ** Only list all images, as-is (remove local iso path input) * Remote: ** List remote ISOS as-is * Provide local distro file (.ISO) or local disk Image File (.img) * File Path: [] Rodrigo Trujillo On 12/02/2015 10:49 AM, Ramon Medeiros wrote:

Hi,

we have a propose to change how templates are created by Kimchi. Today we do this way:

1) Specify if it's cdrom or disk 2) Pass image path

The new propose is: Kimchi will identify if the media is disk or cdrom. So, the user will just pass the media and let kimchi discover it.

The main argument of this change is that we won't have errors with users trying to add disks on cdrom template creation, for example.

What do you think guys?

On 12/02/2015 10:49 AM, Ramon Medeiros wrote:

Hi,

we have a propose to change how templates are created by Kimchi. Today we do this way:

1) Specify if it's cdrom or disk 2) Pass image path

The new propose is: Kimchi will identify if the media is disk or cdrom. So, the user will just pass the media and let kimchi discover it.

The main argument of this change is that we won't have errors with users trying to add disks on cdrom template creation, for example.

What do you think guys?

I think it would be better than what we have today. Go for it