7:33 p.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--