------=_Part_85_9819394.1369817960923
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Absolutely agree with you, planning is the best thing to do, but normally people want a
plug'n'play system with all included, because there is not much time to think and
planning, and there are many companies that know how to take advantage of this people
characteristics.
Any way, I think another solution for dedup is FreeNAS using ZFS.
Jose
----- Original Message -----
From: "Jiri Belka" <jbelka(a)redhat.com>
To: suporte(a)logicworks.pt
Cc: users(a)ovirt.org
Sent: Quarta-feira, 29 de Maio de 2013 7:33:10
Subject: Re: [Users] deduplication
On Tue, 28 May 2013 14:29:05 +0100 (WEST)
suporte(a)logicworks.pt wrote:
That's why I'm making this questions, to demystify some
buzzwords around here.
But if you have a strong and good technology why not create buzzwords to get into as many
people as possible? without trapped them.
Share a disk containing "static" data is a good idea, do you know from where I
can start?
Everything depends on your needs, design planning. Maybe then sharing
disk would be better to share via NFS/iscsi. Of course if you have many
VMs each of them is different you will fail. But if you have mostly
homogeneous environment you can think about this approach. Sure you have
to have plan for upgrading "base" "static" shared OS data, you have to
have plan how to install additional software (different destination
than /usr or /usr/local)... If you already have your own build host
which builds for you OS packages and you have already your own plan for
deployment, you have done first steps. If you depend on upgrading each
machine separately from Internet, then first you should plan your
environment, configuration management etc.
Well, in many times people do not do any planning, they just think some
good technology would save their "poor" design.
j.
------=_Part_85_9819394.1369817960923
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html><head><style type=3D'text/css'>p { margin: 0;
}</style></head><body><=
div style=3D'font-family: arial,helvetica,sans-serif; font-size: 10pt; colo=
r: #000000'>Absolutely agree with you, planning is the best thing to do, bu=
t normally people want a plug'n'play system with all included, because ther=
e is not much time to think and planning, and there are many companies that=
know how to take advantage of this people characteristics.<br>Any way, I t=
hink another solution for dedup is FreeNAS using
ZFS.<br><br>Jose<br><br><b=
r><hr id=3D"zwchr"><div style=3D"color: rgb(0, 0, 0);
font-weight: normal; =
font-style: normal; text-decoration: none; font-family: Helvetica,Arial,san=
s-serif; font-size: 12pt;"><b>From: </b>"Jiri Belka"
&lt;jbelka(a)redhat.com&=
gt;<br><b>To: </b>suporte(a)logicworks.pt<br><b>Cc:
</b>users(a)ovirt.org<br><b=
Sent: </b>Quarta-feira, 29 de Maio de 2013
7:33:10<br><b>Subject: </b>Re: =
[Users]
deduplication<br><br>On Tue, 28 May 2013 14:29:05 +0100 (WEST)<br>s=
uporte(a)logicworks.pt wrote:<br><br>> That's why I'm making this
question=
s, to demystify some buzzwords around here. <br>> But if you have a stro=
ng and good technology why not create buzzwords to get into as many people =
as possible? without trapped them. <br>> Share a disk containing
"static=
" data is a good idea, do you know from where I can start?
<br><br>Everythi=
ng depends on your needs, design planning. Maybe then sharing<br>disk would=
be better to share via NFS/iscsi. Of course if you have many<br>VMs each o=
f them is different you will fail. But if you have mostly<br>homogeneous en=
vironment you can think about this approach. Sure you have<br>to have plan =
for upgrading "base" "static" shared OS data, you have
to<br>have plan how =
to install additional software (different destination<br>than /usr or /usr/=
local)... If you already have your own build host<br>which builds for you O=
S packages and you have already your own plan for<br>deployment, you have d=
one first steps. If you depend on upgrading each<br>machine separately from=
Internet, then first you should plan your<br>environment, configuration ma=
nagement etc.<br><br>Well, in many times people do not do any planning, the=
y just think some<br>good technology would save their "poor"
design.<br><br=
j.<br></div><br></div></body></html>
------=_Part_85_9819394.1369817960923--