<meta content="text/html; charset=ISO-8859-1"
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 12/09/2013 01:37 PM, Devananda van
der Veen wrote:<br>
<div class="gmail_quote">On Fri, Dec 6, 2013 at 2:13 PM, Clark
Boylan <span dir="ltr"><<a moz-do-not-send="true"
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="h5">On Fri, Dec 6, 2013 at 1:53 PM, David
Kranz <<a moz-do-not-send="true"
> It's great that tempest tests for ironic have
been submitted! I was<br>
> reviewing <a moz-do-not-send="true"
and noticed that the tests<br>
> do not actually run. They are skipped because
baremetal is not enabled. This<br>
> is not terribly surprising but we have had a
policy in tempest to only merge<br>
> code that has demonstrated that it works. For
services that cannot run in<br>
> the single-vm environment of the upstream gate we
said there could be a<br>
> system running somewhere that would run them and
report a result to gerrit.<br>
> Is there a plan for this, or to make an exception
> OpenStack-dev mailing list<br>
> <a moz-do-not-send="true"
> <a moz-do-not-send="true"
There is a change to openstack-infra/config to add
tempest jobs to test ironic. I think that change is close
ready, but I need to give it time for a proper review.
Once in that<br>
will allow you to test 48109 (in theory, not sure if all
the bits will<br>
just work). I don't think these tests fall under the
cannot run in a<br>
single vm environment umbrella, we should be able to test
baremetal code via the pxe booting of VMs within the
 <a moz-do-not-send="true"
<span class="HOEnZb"><font color="#888888"><br>
<div>We can test the ironic services, database, and the
driver interfaces by using our "fake" driver within a
single devstack VM today (I'm not sure the exercises for
all of this have been written yet, but it's practical to
test it). OTOH, I don't believe we can test a PXE deploy
within a single VM today, and need to resume discussions
with infra about this.</div>
<div>There are some other aspects of Ironic (IPMI, SOL
access, any vendor-specific drivers) which we'll need real
hardware to test because they can't effectively be
virtualized. TripleO should cover some (much?) of those
needs, once they are able to switch to using Ironic
instead of nova-baremetal.</div>
So it seems that the code in the submitted tempest tests can run in
a regular job if devstack is configured to enable ironic, but that
this cannot be the default. So I propose that we create a regular
devstack+ironic job that will run in the ironic and tempest gates,
and run just the ironic tests. When third-party bare-metal results
can be reported for ironic, tempest can then accept tests that
require bare-metal. Does any one have a problem with this approach?<br>