<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="GENERATOR" content="GtkHTML/4.6.4">
</head>
<body>
tor 2013-09-05 klockan 09:30 +0200 skrev noc:
<blockquote type="CITE">
<pre>
On 2-9-2013 16:32, Itamar Heim wrote:
<font color="#737373">> On 09/02/2013 05:29 PM, NOC wrote:</font>
<font color="#737373">>> On 08/21/2013 12:11 PM, Itamar Heim wrote:</font>
<font color="#737373">>>> On 08/21/2013 02:40 AM, Joop van de Wege wrote:</font>
<font color="#737373">>>>></font>
<font color="#737373">>>>> What I would like to see in the ! next version is pxe boot of the </font>
<font color="#737373">>>>> nodes.</font>
<font color="#737373">>>>> Probably not easy to achieve because of dependency on dhcp.</font>
<font color="#737373">>>></font>
<font color="#737373">>>> Hi Joop,</font>
<font color="#737373">>>></font>
<font color="#737373">>>> can you please give a bit more information on the use case / how you</font>
<font color="#737373">>>> envision this?</font>
<font color="#737373">>>></font>
<font color="#737373">>>> current thinking around bare metal provisioning of hosts is to extend</font>
<font color="#737373">>>> the functionality around the foreman provider for this, but you may</font>
<font color="#737373">>>> have other suggestions?</font>
<font color="#737373">>></font>
<font color="#737373">>> I think Joop means to be able to add hosts (nodes) to a cluster by</font>
<font color="#737373">>> adding their MAC address to the dhcp list for PXE boot into ovirt-node</font>
<font color="#737373">>> and thus join the cluster. This would make it easy to add new physical</font>
<font color="#737373">>> nodes without any spinning disks or other local storage requirements.</font>
<font color="#737373">></font>
<font color="#737373">> we started adding foreman integration in 3.3:</font>
<font color="#737373">> <a href="http://www.ovirt.org/Features/ForemanIntegration">http://www.ovirt.org/Features/ForemanIntegration</a></font>
<font color="#737373">></font>
<font color="#737373">> adding ohad and oved for their thoughts on this.</font>
<font color="#737373">></font>
<font color="#737373">>></font>
<font color="#737373">>> I suppose this may not be easy with complex network connections (bonds</font>
<font color="#737373">>> on mgmt network, mgmt network on a tagged vlan, etc), but it should be</font>
<font color="#737373">>> possible if the management network interface is plain and physical.</font>
<font color="#737373">>></font>
<font color="#737373">>> /Simon</font>
<font color="#737373">>></font>
<font color="#737373">>> PS, Perhaps Joop can confirm this idea, we've talked about it IRL.</font>
<font color="#737373">>> _______________________________________________</font>
<font color="#737373">>> Users mailing list</font>
<font color="#737373">>> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a></font>
<font color="#737373">>> <a href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a></font>
<font color="#737373">></font>
This isn't about provisioning with Foreman. Its about having the compute
nodes NOT having any spinning disks. So the only way to start a node is
to pxeboot it and then let it (re)connect with the engine. Then it will
be identified by engine as either a new node or a reconnecting node and
it will get its configuration from the engine. For reference: thats how
VirtualIron works. It has a managment network, just like ovirt, and on
that it runs a tftp and dhcp server. Nodes are plugged into the
managment network, without disk, and then pxe booted after which they
appear in the webui as new unconfigured nodes. You then can set various
settings and upon rebooting the nodes will recieve these settings
because it is recognised by its mac address. The advantage of this
construct is that you can place a new server into a rack, cable it,
power on and go back to you office where you'll find the new node
waiting to be configured. No messing around with CDs to install an OS,
not being in the datacenter for hours on end, just in and out.
Yes, disks are cheap but they brake down, need maintenance, means
downtime and in general more admin time then when you don't have them. (
its a shame to have a raid1 of 2 1Tb disk just to install an OS of less
then 10G)
</pre>
</blockquote>
<br>
What about swap? Don´t they have any swap file, or partition at all? Swap-file over NFS must suck quite badly, no? We have bought semi-cheap SSD's for our Hosts to use as swap to get more out of them from memory overprovisioning.<br>
<br>
<blockquote type="CITE">
<pre>
Regards,
Joop
_______________________________________________
Users mailing list
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
<table cellspacing="0" cellpadding="0" width="100%">
<tbody>
<tr>
<td>-- <br>
<br>
Med Vänliga Hälsningar<br>
-------------------------------------------------------------------------------<br>
Karli Sjöberg<br>
Swedish University of Agricultural Sciences<br>
Box 7079 (Visiting Address Kronåsvägen 8)<br>
S-750 07 Uppsala, Sweden<br>
Phone: +46-(0)18-67 15 66<br>
<a href="mailto:karli.sjoberg@adm.slu.se">karli.sjoberg@slu.se</a> </td>
</tr>
</tbody>
</table>
</body>
</html>