2:04 p.m.
Propose:
Unless has a set of distro isos, use an algorithm to query new ISOs from
repositories and display them when creating new templates.
Ways to implement it:
1) Add a script that queries the ISOS everytime we lookup at template
list. In the past, we've got a PoC from Cristian Viana, saying that it
could take a while
(https://github.com/kimchi-project/kimchi/issues/605#issuecomment-78279706).
2) We can run the script when starting wok, and write the output to a
dictonary. The only problem will be servers that did not reboot.
I would like to have a way that we can run the script in parallel, like
refreshing the cache between some periods.
--
Ramon Nunes Medeiros
Kimchi Developer
Linux Technology Center Brazil
IBM Systems & Technology Group
Phone : +55 19 2132 7878
ramonn(a)br.ibm.com
7:38 a.m.
I think you're referring to issue 611. 802 is marked as closed.
On 08/12/2016 04:04 PM, Ramon Medeiros wrote:
Propose:
Unless has a set of distro isos, use an algorithm to query new ISOs
from repositories and display them when creating new templates.
Ways to implement it:
1) Add a script that queries the ISOS everytime we lookup at template
list. In the past, we've got a PoC from Cristian Viana, saying that it
could take a while
(https://github.com/kimchi-project/kimchi/issues/605#issuecomment-78279706).
If you're referring to the remote template dialog then we can try to
work something
out. However we need to be careful about two things:
1 - Always ask the question "what if the host doesn't have internet
access?" when
thinking about this feature. Even in the remote template dialog there is
a fair use
without internet - a remote ISO can be hosted in an isolated network
for example.
2 - Don't be shady. We can't connect to Red Hat FTP and search for ISOS
without
the user knowledge.
2) We can run the script when starting wok, and write the output to a
dictonary. The only problem will be servers that did not reboot.
See (2). If you come up with a mechanism (config file is the only one I
can think
about now) to allow the user to enable this verification in boot time,
then I agree.
Of course that this verification would be disabled by default because,
again, we
can't impact the users that aren't interested in this feature.
I would like to have a way that we can run the script in parallel,
like refreshing the cache between some periods.
3025
days inactive
3028
days old
1 comments
2 participants
participants (2)
-
Daniel Henrique Barboza -
Ramon Medeiros