6:31 a.m.
--Rzq/nSLlHy1djmXS
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi everyone!
There's a use case for the $subject that is really favorable for us (CI guy=
s)
and I want to ask you if it's possible, if it's viable and if not already t=
here
if I should open a rfe.
The case is when you want to spin up vms from a template, but use them only
once and remove them afterwards (for example, running tests), if you had the
option to have a shared storage where you store the templates, and then a l=
ocal
storage where you spin up the vms, that allows really fast (local) storage =
for
the vms and avoids you having to setup a clustered storage (gluster, etc) f=
or
those vms that do not need any of those features.
So is that already possible? (For other threads and what I've tested seems =
not)
Is that viable? Can it be implemented on ovirt?
Thanks!
--=20
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605
Email: dcaro(a)redhat.com
Web: www.redhat.com
RHT Global #: 82-62605
--Rzq/nSLlHy1djmXS
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJVTJ6ZAAoJEEBxx+HSYmnDAmUH/RuyeR/Vnt0+rQwaL0N31bk+
IYN0S9fvS30wPGs1hFeU/IDsz4DmfZkxwPXSYDEsr/zmTScETzEGw/uZi315qQJp
EiB13snemRQ5Plxr7NRGzcVS3hNJqQKqY5aDc6hcxPhARQibJkDzRWVlHmr3rqr0
r6IaIvn6352MRvn2/ifAZvjk4Si/MUlSzXWJVAM8MQAhwaovy9NZHWH1G1Hf9Q8C
VPfuj1EY/Z2Wd2x6COgWOeEIbA1EaVr1U72GIznI1SI/sUYfX5N5o9t2Cj/dmEyi
gwRoRhVv6at3nFaMneCj+mwWO2BrCQ9oJzUokk0uGKJMGaqypzKpf55EbAR0BKs=
=LnY+
-----END PGP SIGNATURE-----
--Rzq/nSLlHy1djmXS--
8:13 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/05/15 13:31, David Caro wrote:
Hi everyone!
There's a use case for the $subject that is really favorable for us
(CI guys) and I want to ask you if it's possible, if it's viable
and if not already there if I should open a rfe.
The case is when you want to spin up vms from a template, but use
them only once and remove them afterwards (for example, running
tests), if you had the option to have a shared storage where you
store the templates, and then a local storage where you spin up the
vms, that allows really fast (local) storage for the vms and avoids
you having to setup a clustered storage (gluster, etc) for those
vms that do not need any of those features.
So is that already possible? (For other threads and what I've
tested seems not) Is that viable? Can it be implemented on ovirt?
I guess you talk about this feature:
http://www.ovirt.org/Features/Mixed_Types_Data_Center
but imho the feature page is out of date
- --
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhaus
en
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad
Oeynhausen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJVTLZkAAoJEMby9TMDAbQRaK8P/3yYHeZRHPkzs72UnH8r2hCg
pu/95LIGIQHBrtbwUIJy86OBIFHXkx09x3jUk5wPFQCtdMPqUKcVq3YEqtQZy+aM
+zOlovhYFD16Wuatquz4903VkGJ1S1FnYN53eVrCKsXqREWCXjEHvyDlQyTxKNge
1oAw2qjcviWWwsf8RNk/0XOp7byiGoHxz87gbnqWiLrH6Hkgv7YJFz4bdXQKHQ2B
kC9du7MbBKSi980gyo4anNUzyUXeE/aVyLfLURKMEsjvE5Rs2zwL66Dxcanfgh0e
4p5gy+KqYa574Z37moBXdgLFeo0Z9im2q9pOGjiVsykvKyw4P7UyChMofPHMX9zF
0NR8Gw4it3+s3y5C300Rxo7INYBWGwN0YSVdiU6fHg/+Dcn99KnBRzl24ioM+rR3
Kc44KG9+H7N7QtULKGvePZIz5azhSBu8Qrd89WjbAz5DQeUHsm8IY/mkWBO/Zukh
sGcyyL9nRut2yyfQI7i5o4AyN9S3XZ4fKYvvr41p0WDgzWhxTqScyB7G4TSwxs27
SEb1uAnaWT73gg36qIB9YUItPFg3XKwceH5oxTAjeLWbTCgwvOin4w2cCp0YAcxH
NJJyCqrN6TPDvYJtP1DJxv1Yj8JGEYMrOJhjCn2pGW0SZKqE/s+ci4OLcrtr3WM0
yKfLdXlR+T1jqDOvN7Zn
=OqkY
-----END PGP SIGNATURE-----
12:22 p.m.
----- Original Message -----
From: "Sven Kieske" <s.kieske(a)mittwald.de>
Sent: Friday, May 8, 2015 9:13:08 AM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/05/15 13:31, David Caro wrote:
>
> Hi everyone!
>
>
> There's a use case for the $subject that is really favorable for us
> (CI guys) and I want to ask you if it's possible, if it's viable
> and if not already there if I should open a rfe.
>
> The case is when you want to spin up vms from a template, but use
> them only once and remove them afterwards (for example, running
> tests), if you had the option to have a shared storage where you
> store the templates, and then a local storage where you spin up the
> vms, that allows really fast (local) storage for the vms and avoids
> you having to setup a clustered storage (gluster, etc) for those
> vms that do not need any of those features.
>
>
> So is that already possible? (For other threads and what I've
> tested seems not) Is that viable? Can it be implemented on ovirt?
>
I guess you talk about this feature:
http://www.ovirt.org/Features/Mixed_Types_Data_Center
http://www.ovirt.org/Features/Mixed_Types_Data_Center is about being
able to mix different types of shared storage domains (NFS, iSCSI, FC,
...) within the same Data-Center.
We have this capability since oVirt 3.4 IIRC.
It is not related to mixing shared storage and local storage within
the same Data-Center, which is what David is asking here.
but imho the feature page is out of date
- --
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhaus
en
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad
Oeynhausen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJVTLZkAAoJEMby9TMDAbQRaK8P/3yYHeZRHPkzs72UnH8r2hCg
pu/95LIGIQHBrtbwUIJy86OBIFHXkx09x3jUk5wPFQCtdMPqUKcVq3YEqtQZy+aM
+zOlovhYFD16Wuatquz4903VkGJ1S1FnYN53eVrCKsXqREWCXjEHvyDlQyTxKNge
1oAw2qjcviWWwsf8RNk/0XOp7byiGoHxz87gbnqWiLrH6Hkgv7YJFz4bdXQKHQ2B
kC9du7MbBKSi980gyo4anNUzyUXeE/aVyLfLURKMEsjvE5Rs2zwL66Dxcanfgh0e
4p5gy+KqYa574Z37moBXdgLFeo0Z9im2q9pOGjiVsykvKyw4P7UyChMofPHMX9zF
0NR8Gw4it3+s3y5C300Rxo7INYBWGwN0YSVdiU6fHg/+Dcn99KnBRzl24ioM+rR3
Kc44KG9+H7N7QtULKGvePZIz5azhSBu8Qrd89WjbAz5DQeUHsm8IY/mkWBO/Zukh
sGcyyL9nRut2yyfQI7i5o4AyN9S3XZ4fKYvvr41p0WDgzWhxTqScyB7G4TSwxs27
SEb1uAnaWT73gg36qIB9YUItPFg3XKwceH5oxTAjeLWbTCgwvOin4w2cCp0YAcxH
NJJyCqrN6TPDvYJtP1DJxv1Yj8JGEYMrOJhjCn2pGW0SZKqE/s+ci4OLcrtr3WM0
yKfLdXlR+T1jqDOvN7Zn
=OqkY
-----END PGP SIGNATURE-----
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
10:58 a.m.
On 08-05-2015 8:31, David Caro wrote:
[...]
The case is when you want to spin up vms from a template, but use them only
once and remove them afterwards (for example, running tests), if you had the
option to have a shared storage where you store the templates, and then a local
storage where you spin up the vms, that allows really fast (local) storage for
the vms and avoids you having to setup a clustered storage (gluster, etc) for
those vms that do not need any of those features.
So is that already possible? (For other threads and what I've tested seems not)
Is that viable? Can it be implemented on ovirt?
Hi David,
You could use a local replica-1 gluster storage domain for this.
replica-1 => no split brains + local performance + no complexity + no
overhead + gluster benefits
It just works fine.
PS: I'm currently researching the best way to live replicate local
replica-1 volumes by using geo-replication, adding a replica-2 brick,
using libvirt blockcopy or oVirt API.
Best regards,
Christopher.
11:17 a.m.
--Q0rSlbzrZN6k9QnT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Thanks Christopher!
That will force me to have as many gluster storages as hosts? Or it will a=
llow
to have one gluster setup with each of the hosts accessing to the local sto=
rage?
I will investigate, but I'd prefer if I did not have to use any external
service at all (in the end, is just local storage)
On 05/11, Christopher Pereira wrote:
On 08-05-2015 8:31, David Caro wrote:
>[...]
>The case is when you want to spin up vms from a template, but use them o=
nly
>once and remove them afterwards (for example, running tests), if
you had=
the
>option to have a shared storage where you store the templates,
and then =
a local
>storage where you spin up the vms, that allows really fast
(local) stora=
ge for
>the vms and avoids you having to setup a clustered storage
(gluster, etc=
) for
>those vms that do not need any of those features.
>
>So is that already possible? (For other threads and what I've tested see=
ms not)
>Is that viable? Can it be implemented on ovirt?
=20
Hi David,
=20
You could use a local replica-1 gluster storage domain for this.
replica-1 =3D> no split brains + local performance + no complexity + no
overhead + gluster benefits
It just works fine.
=20
PS: I'm currently researching the best way to live replicate local replic=
a-1
volumes by using geo-replication, adding a replica-2 brick, using
libvirt
blockcopy or oVirt API.
=20
Best regards,
Christopher.
=20
--=20
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605
Email: dcaro(a)redhat.com
Web: www.redhat.com
RHT Global #: 82-62605
--Q0rSlbzrZN6k9QnT
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJVUNYcAAoJEEBxx+HSYmnD8RsH+wftaCbEIB7Bi0CyQwhztAKO
lH+Xa1WRSOqptdpaUVNIwneN0N7ruGjd603rrWIl9FznsDSFxZJU9W6456HkGgNX
FkWP+uy8mTGyhQgFwaZHgK3YTDmekwaawE4s69/X75p9O9G6h0eBdZSYpA+YIk9h
mleODcvU/CQnIJl4qkLeVumw4qj9SdK7subN8pq4L+K65LAlMKhNsg3M9V1uVZPr
Bg/2a/NgdwgPvnEuOR4utq9b/JPasKzmORCW55KpZDWawI2TSfehnV3youIpYr9r
2JwCaMf3nhgur6yY2deE9qg94BQl43yoe7DuEoN2lJDwZbNR2nUhS+KaasQmmH0=
=xQxO
-----END PGP SIGNATURE-----
--Q0rSlbzrZN6k9QnT--
11:33 a.m.
This is a multi-part message in MIME format.
--------------010709080006080305070302
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
On 11-05-2015 13:17, David Caro wrote:
Thanks Christopher!
That will force me to have as many gluster storages as hosts? Or it will allow
to have one gluster setup with each of the hosts accessing to the local storage?
You will need one volume (with 1 local brick) for each host that needs
local storage.
If you need this for many hosts, you could use a script for creating the
local volumes.
Something like this.
HOST=host1
VOL=local-$HOST
BRICK=/mnt/disk/gluster-bricks/$VOL
mkdir $BRICK
*chown vdsm:kvm *$BRICK
*gluster vol create $VOL* <localhost>:$BRICK
*gluster vol start $VOL
*Then *in oVirt engine, you add *this new**storage manually or use the
rest API to automate it.
Use appropriate volume names referencing the host.
I will investigate, but I'd prefer if I did not have to use any
external
service at all (in the end, is just local storage)
IMO, it's quite easy to
setup gluster (2 commands), it is well supported
by oVirt and it gives you many benefits you could use in the future like
migrating the VM to other host, create snapshots, geo-replicate the
storage, etc.
--------------010709080006080305070302
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11-05-2015 13:17, David Caro
wrote:<br>
</div>
<blockquote cite="mid:20150511161732.GD24123@brete.redhat.com"
type="cite">
<pre wrap="">Thanks Christopher!
That will force me to have as many gluster storages as hosts? Or it will allow
to have one gluster setup with each of the hosts accessing to the local
storage?</pre>
</blockquote>
You will need one volume (with 1 local brick) for each host that
needs local storage.<br>
<br>
If you need this for many hosts, you could use a script for creating
the local volumes.<br>
Something like this.<br>
<br>
HOST=host1<br>
VOL=local-$HOST<br>
BRICK=/mnt/disk/gluster-bricks/$VOL<br>
<meta charset="utf-8">
mkdir $BRICK<br>
<meta charset="utf-8">
<b style="font-weight:normal;"
id="docs-internal-guid-4b7e62b6-43c9-7949-bcd1-87d25ffc2ed1"><span
style="font-size:15px;font-family:Arial;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">chown
vdsm:kvm </span></b>$BRICK<br>
<meta charset="utf-8">
<b style="font-weight:normal;"
id="docs-internal-guid-4b7e62b6-43c9-e058-1522-5f8f6c2f42cd"><span
style="font-size:15px;font-family:Arial;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">gluster
vol create $VOL</span></b> <localhost>:$BRICK<br>
<b style="font-weight:normal;"
id="docs-internal-guid-4b7e62b6-43c9-e058-1522-5f8f6c2f42cd"><span
style="font-size:15px;font-family:Arial;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">gluster
vol start $VOL<br>
<br>
</span></b>Then <b style="font-weight:normal;"
id="docs-internal-guid-4b7e62b6-43c9-e058-1522-5f8f6c2f42cd"><span
style="font-size:15px;font-family:Arial;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">in
oVirt engine, you add </span></b>this new<b
style="font-weight:normal;"
id="docs-internal-guid-4b7e62b6-43c9-e058-1522-5f8f6c2f42cd"><span
style="font-size:15px;font-family:Arial;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">
</span></b>storage manually or use the rest API to automate
it.<br>
Use appropriate volume names referencing the host.<br>
<br>
<blockquote cite="mid:20150511161732.GD24123@brete.redhat.com"
type="cite">
<pre wrap="">I will investigate, but I'd prefer if I did not
have to use any external
service at all (in the end, is just local storage)</pre>
</blockquote>
IMO, it's quite easy to setup gluster (2 commands), it is well
supported by oVirt and it gives you many benefits you could use in
the future like migrating the VM to other host, create snapshots,
geo-replicate the storage, etc.<br>
<br>
</body>
</html>
--------------010709080006080305070302--
3272
days inactive
3275
days old
5 comments
4 participants
participants (4)
-
Christopher Pereira -
David Caro -
Einav Cohen -
Sven Kieske