8:23 a.m.
Hello there,
With oVirt 4.0 Release is running oVirt Node in a SD Card or USB Stick
supported where the system boots in memory and only writes configuration
changes to permanent storage similar to what VMware ESXi does ?
This is very useful and can save a significant amount on CAPEX and
running costs depending on the size of the cluster.
Thanks
Fernando
9:40 a.m.
oVirt node depends on the base OS support of the feature (Fedora\CentOS).
I have seen people do this online, but nothing official, so you can try it.
Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email: ydary(a)redhat.com
IRC : ydary
On Wed, Jul 6, 2016 at 3:23 PM, Fernando Frediani <
fernando.frediani(a)upx.com.br> wrote:
Hello there,
With oVirt 4.0 Release is running oVirt Node in a SD Card or USB Stick
supported where the system boots in memory and only writes configuration
changes to permanent storage similar to what VMware ESXi does ?
This is very useful and can save a significant amount on CAPEX and running
costs depending on the size of the cluster.
Thanks
Fernando
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
10 a.m.
This is a multi-part message in MIME format.
--------------060506060608040602080303
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi Yaniv,
I have already done a fair amount of tunning to run a minimal OS from a
USB stick and it seems to work reasonable well overtime, but nothing
rock solid and of course I wouldn't try it myself in a production oVirt
Node if that's not official.
Even if it's not running in memory it's just a question to create a
schema to avoid all unnecessary writes to permanent storage. Logs can be
limited to a short period in memory (in another Console) or sent to a
remote syslog server. It doesn't change much for the base OS to read
anything it needs.
I thought I had seen these years ago during the development of the first
versions of oVirt Node, but maybe I misunderstood or it was not
considered for newer versions.
Perhaps there is something around this on some roadmap. As I mentioned,
this is a significant saving for any platform not having to use any
disks in the Compute Nodes.
Regards,
Fernando
Em 06/07/2016 10:40, Yaniv Dary escreveu:
oVirt node depends on the base OS support of the feature
(Fedora\CentOS).
I have seen people do this online, but nothing official, so you can
try it.
Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem
Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9)
7692306 8272306 Email: ydary(a)redhat.com <mailto:ydary@redhat.com> IRC
: ydary
On Wed, Jul 6, 2016 at 3:23 PM, Fernando Frediani
<fernando.frediani(a)upx.com.br <mailto:fernando.frediani@upx.com.br>>
wrote:
Hello there,
With oVirt 4.0 Release is running oVirt Node in a SD Card or USB
Stick supported where the system boots in memory and only writes
configuration changes to permanent storage similar to what VMware
ESXi does ?
This is very useful and can save a significant amount on CAPEX and
running costs depending on the size of the cluster.
Thanks
Fernando
_______________________________________________
Users mailing list
Users(a)ovirt.org <mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
--------------060506060608040602080303
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Yaniv,<br>
<br>
I have already done a fair amount of tunning to run a minimal OS
from a USB stick and it seems to work reasonable well overtime, but
nothing rock solid and of course I wouldn't try it myself in a
production oVirt Node if that's not official.<br>
<br>
Even if it's not running in memory it's just a question to create a
schema to avoid all unnecessary writes to permanent storage. Logs
can be limited to a short period in memory (in another Console) or
sent to a remote syslog server. It doesn't change much for the base
OS to read anything it needs.<br>
I thought I had seen these years ago during the development of the
first versions of oVirt Node, but maybe I misunderstood or it was
not considered for newer versions.<br>
<br>
Perhaps there is something around this on some roadmap. As I
mentioned, this is a significant saving for any platform not having
to use any disks in the Compute Nodes.<br>
<br>
Regards,<br>
Fernando<br>
<br>
<br>
<div class="moz-cite-prefix">Em 06/07/2016 10:40, Yaniv Dary
escreveu:<br>
</div>
<blockquote
cite="mid:CACKMAy_UoMAPV=r+v-Lo4=fVAxn2yDp0WtsiUjFiVnJO29A4JQ@mail.gmail.com"
type="cite">
<div dir="ltr">oVirt node depends on the base OS support of the
feature (Fedora\CentOS).
<div>I have seen people do this online, but nothing official, so
you can try it.</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<pre cols="72"><span
style="font-family:arial,helvetica,sans-serif">Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email: <a moz-do-not-send="true" href="mailto:ydary@redhat.com"
target="_blank">ydary(a)redhat.com</a>
IRC : ydary</span></pre>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Wed, Jul 6, 2016 at 3:23 PM,
Fernando Frediani <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:fernando.frediani@upx.com.br"
target="_blank"><a class="moz-txt-link-abbreviated"
href="mailto:fernando.frediani@upx.com.br">fernando.frediani@upx.com.br</a></a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hello
there,<br>
<br>
With oVirt 4.0 Release is running oVirt Node in a SD Card or
USB Stick supported where the system boots in memory and
only writes configuration changes to permanent storage
similar to what VMware ESXi does ?<br>
<br>
This is very useful and can save a significant amount on
CAPEX and running costs depending on the size of the
cluster.<br>
<br>
Thanks<br>
Fernando<br>
_______________________________________________<br>
Users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Users@ovirt.org"
target="_blank">Users(a)ovirt.org</a><br>
<a moz-do-not-send="true"
href="http://lists.ovirt.org/mailman/listinfo/users"
rel="noreferrer"
target="_blank">http://lists.ovirt.org/mailman/listinfo/user...
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>
--------------060506060608040602080303--
2:02 p.m.
On Wed, Jul 6, 2016 at 5:00 PM, Fernando Frediani <
fernando.frediani(a)upx.com.br> wrote:
Hi Yaniv,
I have already done a fair amount of tunning to run a minimal OS from a
USB stick and it seems to work reasonable well overtime, but nothing rock
solid and of course I wouldn't try it myself in a production oVirt Node if
that's not official.
For production I'd use boot from SAN, either via FC or iSCSI (HW adapter
needed of course).
Even if it's not running in memory it's just a question to create a schema
to avoid all unnecessary writes to permanent storage. Logs can be limited
to a short period in memory (in another Console) or sent to a remote syslog
server. It doesn't change much for the base OS to read anything it needs.
I thought I had seen these years ago during the development of the first
versions of oVirt Node, but maybe I misunderstood or it was not considered
for newer versions.
Perhaps there is something around this on some roadmap. As I mentioned,
this is a significant saving for any platform not having to use any disks
in the Compute Nodes.
Yes, would be cool to run it from SD card - but indeed you can't store logs
there, as just the write speed alone will slow you down (write speed over
time will degrade significantly in SDs, due to garbage collection).
Writing logs to memory is a bit of a problem - when you'll have issues,
they might get lost. A better and more performant solution would be to
write them to a remote server (rsyslog or such).
But really, running off the smallest SSD (64-128GB) is not very expensive
(~50$ from ebay/amazon), fast and does not consume a lot of electricity.
Y.
Regards,
Fernando
Em 06/07/2016 10:40, Yaniv Dary escreveu:
oVirt node depends on the base OS support of the feature (Fedora\CentOS).
I have seen people do this online, but nothing official, so you can try it.
Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email: ydary(a)redhat.com
IRC : ydary
On Wed, Jul 6, 2016 at 3:23 PM, Fernando Frediani <
<fernando.frediani@upx.com.br>fernando.frediani(a)upx.com.br> wrote:
> Hello there,
>
> With oVirt 4.0 Release is running oVirt Node in a SD Card or USB Stick
> supported where the system boots in memory and only writes configuration
> changes to permanent storage similar to what VMware ESXi does ?
>
> This is very useful and can save a significant amount on CAPEX and
> running costs depending on the size of the cluster.
>
> Thanks
> Fernando
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
3096
days inactive
3096
days old
3 comments
3 participants
participants (3)
-
Fernando Frediani -
Yaniv Dary -
Yaniv Kaul