<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Thanks to all for answers!<br>
<br>
We will leave Fuel master node on a VM for our testing until some
specific cases will require it on a baremetal.<br>
Ironic looks like a good tool for PXE provisioning and manage other
baremetal slaves via IPMI, we will investigate how it could be used
in our testing tools later.<br>
<br>
<div class="moz-cite-prefix">On 02/10/2016 12:43 PM, Vladimir Kuklin
wrote:<br>
</div>
<blockquote
cite="mid:CAHAWLf0pDBUenuo6J-DpbpNHkQfRUiCqTqYw9st+G7sikiU=WQ@mail.gmail.com"
type="cite">
<div dir="ltr">Folks
<div><br>
</div>
<div>I think the easiest and the best option here is to boot
iPXE or pxelinux with NFS and put master node image onto an
NFS mount. This one should work seamlessly.</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Feb 10, 2016 at 1:36 AM, Andrew
Woodward <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:awoodward@mirantis.com" target="_blank">awoodward@mirantis.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Unless we hope to gain some insight and
specific testing by installing the ISO on a bare-metal
node (like UEFI), I'd propose that we stop testing things
that are well tested elsewhere (a given ISO produces a
working fuel master) and just focus on what we want to
test in this environment.
<div><br>
</div>
<div>Along this line, we cold</div>
<div><br>
</div>
<div>a) keep fuel masternode as a VM that is set up with
access to the networks with the BM nodes. We have a good
set of tools to build the master node in a VM already we
can just re-use time </div>
<div><br>
</div>
<div>b) use cobbler to control PXE based ISO boot/install,
then either create new profiles in cobbler for various
fuel nodes with different ISO or replace the single
download link. (Make sure you transfer the image over
HTTP as TFTP will be slow for such size. We have some
tools and knowledge around using cobbler as this is
effectively what fuel does its self.</div>
<div><br>
</div>
<div>c) fuel on fuel, as an extension of b, we can just
use cobbler on an existing fuel node to provision
another fuel node, either from ISO or even it's own
repo's (we just need to send a kickstart)<br>
</div>
<div><br>
</div>
<div>d) you can find servers with good BMC or DRAC that we
can issue remote mount commands to the virtual cd-rom</div>
<div><br>
</div>
<div>e) consider using live-cd approach (long
implmentation). I've been asked about supporting this in
product where we start an environment with live-cd, the
master node may make it's own home and then it can be
moved off the live-cd when it's ready
<div>
<div class="h5"><br>
<br>
<div class="gmail_quote">
<div dir="ltr">On Tue, Feb 9, 2016 at 10:25 AM
Pavlo Shchelokovskyy <<a
moz-do-not-send="true"
href="mailto:pshchelokovskyy@mirantis.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:pshchelokovskyy@mirantis.com">pshchelokovskyy@mirantis.com</a></a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div dir="ltr">Hi,<br>
<br>
Ironic also supports running it as standalone
service, w/o Keystone/Glance/Neutron/Nova etc
integration, deploying images from HTTP links.
Could that be an option too?<br>
<br>
BTW, there is already an official project
under OpenStack Baremetal program called
Bifrost [0] that, quoting, "automates the task
of deploying a base image onto a set of known
hardware using Ironic" by installing and
configuring Ironic in standalone mode.
<div><br>
<div>[0] <a moz-do-not-send="true"
href="https://github.com/openstack/bifrost"
target="_blank">https://github.com/openstack/bifrost</a></div>
<div><br>
</div>
<div>Cheers,</div>
</div>
</div>
<div dir="ltr">
<div>
<div><br>
<br>
<div class="gmail_quote">
<div dir="ltr">On Tue, Feb 9, 2016 at
6:46 PM Dennis Dmitriev <<a
moz-do-not-send="true"
href="mailto:ddmitriev@mirantis.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:ddmitriev@mirantis.com">ddmitriev@mirantis.com</a></a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">Hi all!<br>
<br>
To run system tests on CI on a daily
basis using baremetal servers<br>
instead of VMs, Fuel admin node also
should be bootstrapped.<br>
<br>
There is no a simple way to mount an
ISO with Fuel as a CDROM or USB<br>
device to a baremetal server, so we
choose the provisioning with PXE.</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote class="gmail_quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
It could be done in different ways:<br>
<br>
- Configure a libvirt bridge as
dnsmasq/tftp server for admin/PXE
network.<br>
Benefits: no additional services
to be configured.<br>
Doubts: ISO should be mounted on
the CI host (via fusefs?); a HTTP<br>
or NFS server for basic provisioning
should be started in the admin/PXE<br>
network (on the CI host);<br>
<br>
- Start a VM that is connected to
admin/PXE network, and configure<br>
dnsmasq/tftp there.<br>
Benefits: no additional
configuration on the CI host should be<br>
performed<br>
Doubts: starting the PXE service
becomes a little complicated<br>
<br>
- Use Ironic for manage baremetal
nodes.<br>
Benefits: good support for
different hardware, support for<br>
provisioning from ISO 'out of the
box'.<br>
Doubts: support for Ironic
cannot be implemented in short terms,<br>
and there should be performed
additional investigations.<br>
<br>
My question is: what other benefits
or doubts I missed for first two<br>
ways? Is there other ways to provision
baremetal with Fuel that can be<br>
automated in short terms?<br>
<br>
Thanks for any suggestions!<br>
<br>
<br>
--<br>
Regards,<br>
Dennis Dmitriev<br>
QA Engineer,<br>
Mirantis Inc. <a
moz-do-not-send="true"
href="http://www.mirantis.com"
rel="noreferrer" target="_blank"><a class="moz-txt-link-freetext" href="http://www.mirantis.com">http://www.mirantis.com</a></a><br>
e-mail/jabber: <a
moz-do-not-send="true"
href="mailto:dis.xcom@gmail.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:dis.xcom@gmail.com">dis.xcom@gmail.com</a></a><br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List
(not for usage questions)<br>
Unsubscribe: <a
moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a></a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
</div>
</div>
</div>
<div dir="ltr">-- <br>
</div>
<div dir="ltr"><span>Dr. Pavlo Shchelokovskyy</span>
<div>Senior Software Engineer</div>
<div>Mirantis Inc</div>
<div><a moz-do-not-send="true">www.mirantis.com</a></div>
</div>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for
usage questions)<br>
Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
</div>
</div>
</div>
</div>
<span class="HOEnZb"><font color="#888888">
<div dir="ltr">-- <br>
</div>
<div dir="ltr">--
<div>Andrew Woodward</div>
<div>Mirantis</div>
<div>Fuel Community Ambassador</div>
<div>Ceph Community </div>
</div>
</font></span><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">Yours Faithfully,<br>
Vladimir Kuklin,<br>
Fuel Library Tech Lead,<br>
Mirantis, Inc.<br>
+7 (495) 640-49-04<br>
+7 (926) 702-39-68<br>
Skype kuklinvv<br>
35bk3, Vorontsovskaya Str.<br>
Moscow, Russia,<br>
<a moz-do-not-send="true" href="http://www.mirantis.ru/"
target="_blank">www.mirantis.com</a><br>
<a moz-do-not-send="true" href="http://www.mirantis.ru/"
target="_blank">www.mirantis.ru</a><br>
<a moz-do-not-send="true"
href="mailto:vkuklin@mirantis.com" target="_blank">vkuklin@mirantis.com</a></div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Regards,
Dennis Dmitriev
QA Engineer,
Mirantis Inc. <a class="moz-txt-link-freetext" href="http://www.mirantis.com">http://www.mirantis.com</a>
e-mail/jabber: <a class="moz-txt-link-abbreviated" href="mailto:dis.xcom@gmail.com">dis.xcom@gmail.com</a></pre>
</body>
</html>