7:20 a.m.
Hi guys,
Today when creating a Template all the default values come from Kimchi.
But in some cases, the user may want to change and persist them for next
interactions.
For example: change the disk size to 20G (instead of the default 10G),
change disk format, use Spice (instead of VNC), change storage pool and
network, etc.
My proposal is to have a configuration file
(/etc/kimchi/template.defaults) that will override Kimchi defaults
values so user can have some control on Template configuration according
to him/her proposals.
Let me know what you think about it.
Regards,
Aline Manera
9:46 a.m.
On 01-04-2015 08:20, Aline Manera wrote:
Hi guys,
Today when creating a Template all the default values come from Kimchi.
But in some cases, the user may want to change and persist them for
next interactions.
For example: change the disk size to 20G (instead of the default 10G),
change disk format, use Spice (instead of VNC), change storage pool
and network, etc.
My proposal is to have a configuration file
(/etc/kimchi/template.defaults) that will override Kimchi defaults
values so user can have some control on Template configuration
according to him/her proposals.
Let me know what you think about it.
+1
I'd suggest using an appropriate extension for the configuration file
(e.g. ".conf") instead of ".defaults".
Also, in the future, it'd be better to allow the user to change those
values in the UI, like having a checkbox "Remember this value for future
templates" when editing a template, or even having a dedicated settings
dialog. But having this as a config file is already very good for now.
3555
days inactive
3556
days old
1 comments
2 participants
participants (2)
-
Aline Manera -
Crístian Viana