<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
Hi All,<br>
<br>
(I am back \o/)<br>
<br>
I'd recommend to find a solution which affects as less as possible
the current design we have today as the community code freeze for
2.3 release is on next week.<br>
<br>
Said that, the solution we agree in this RFC will be specific for
s390x systems. Any problem on that?<br>
That means, that in the code we will need to check the system arch
to identify on which way to follow.<br>
<br>
For this storage pool specific issue, I'd say to have a
template.conf file for s390x systems and change the 'pool' parameter
for 'dirpath'<br>
<br>
Something like:<br>
<br>
[storage]
<br>
<br>
# Specify multiple [[disk.X]] sub-sections to add multiples disks to
guest <br>
# Each disk files will be created in respective storage pool
set <br>
[[disk.0]]
<br>
# Disk size in
GB <br>
#size =
10
<br>
<br>
# Disk
format
<br>
#format =
qcow2
<br>
<br>
<b># Directory to handle the guest
disk </b><b><br>
</b><b>#dirpath = /var/lib/kimchi/images</b><b><br>
</b><br>
When parsing the template.conf file, make sure to validate the data
according to system arch.<br>
if s390x:<br>
if not dirpath:<br>
raise InvalidOperation('You need to specify the directory to
handle the guest disk')<br>
elif not pool:<br>
raise InvalidOperation('You need to specify the pool to
handle the guest disk')<br>
<br>
That will imply in changing the way the templates and the guests are
created.<br>
Today we have the 'disks' parameter which also needs pool
information. Following the same approach, the pool information would
be replaced by dirpath only for s390x systems.<br>
<br>
What do you think about that?<br>
<br>
Maybe we need to think more about the details but the overall idea
is that.<br>
<br>
I will check the RFC about virtual networks and reply separated
there.<br>
<br>
Regards,<br>
Aline Manera<br>
<br>
<div class="moz-cite-prefix">On 08/10/2016 03:28 AM, Pooja Kulkarni
wrote:<br>
</div>
<blockquote cite="mid:57AAC972.3080501@linux.vnet.ibm.com"
type="cite">Hi All,
<br>
<br>
Since currently s390 does not support libvirt storage pools, we
propose to provide an additional parameter "path" in disks section
to specify the path for a default IMG file to be created in. if
"path" attribute is specified, size parameter should be mandatory.
<br>
<br>
Two possible ways to implement default values, keeping the current
option of 'pool' as well:
<br>
1. If both path and pool options are found in default config file,
path always takes higher precedence over pool irrespective of arch
(incase of s390 pool is ignored)
<br>
2. Have a different config file if arch is s390 where only default
path is found (no pool option).
<br>
<br>
Let me know what you think.
<br>
<br>
Regards,
<br>
Pooja Kulkarni
<br>
<br>
_______________________________________________
<br>
Kimchi-devel mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
<br>
<br>
</blockquote>
<br>
</body>
</html>