Open Stack

On Fri, May 23, 2014 at 7:38 PM, Devananda van der Veen <
devananda.vdv at gmail.com> wrote:

> Hi all!
>
> This is a follow-up to several summit discussions on
> how-do-we-deprecate-baremetal, a summary of the plan forward, a call to
> raise awareness of the project's status, and hopefully gain some interest
> from folks on nova-core to help with spec and code reviews.
>
> The nova.virt.ironic driver lives in Ironic's git tree today [1]. We're
> cleaning it up and submitting it to Nova again this cycle. I've posted
> specs [2] outlining the design and planned upgrade process. Earlier today,
> we enabled voting in Ironic's check and gate queues for the
> tempest-dsvm-virtual-ironic job. This runs a tempest scenario test [3]
> against devstack, exercising Nova with the Ironic driver to PXE boot a
> virtual machine. It has been running for a few months on Ironic, and has
> been stable for more than a month. However, because Ironic is not
> integrated, we also can't vote in check/gate queues on integrated projects
> (like Nova). We can - and do - report the test result in a non-voting way,
> though that's easy to miss, since it looks like every other non-voting test.
>
> At the summit [4], it was suggested that we make this job report as though
> it were a third-party CI test for a Nova driver. This would be removed at
> the time that Ironic graduates and the job is allowed to vote in the gate.
> Until that time, I'm happy to have the nova.virt.ironic driver reporting as
> a third-party driver (even though it's not) simply to help raise awareness
> (third-party CI jobs are watched more closely than non-voting jobs) and
> decrease the likelihood that Nova developers will inadvertently break
> Ironic's gate.
>
> Given that there's a concrete plan forward, why am I sending this email to
> all three teams? A few reasons:
> - document the plan that we discussed
> - many people from infra and nova were not present during the discussion
> and may not be aware of the details
> - I may have gotten something wrong (it was a long week)
> - and mostly because I don't technically know how to make an upstream job
> report as though it's a third-party job, and am hoping someone wants to
> volunteer to help figure that out
>
>
Sounds like a great plan to me - this should help raise awareness in nova,
although I cannot speak to what is needed to make ironic vote the same way
a third party CI system does.



> Regards,
> Devananda
>
>
> 1: https://github.com/openstack/ironic/tree/master/ironic/nova/virt/ironic
>
> 2: https://review.openstack.org/95024 and
> https://review.openstack.org/95025
>
> 3:
> https://github.com/openstack/tempest/blob/master/tempest/scenario/test_baremetal_basic_ops.py
>
> 4: https://etherpad.openstack.org/p/juno-nova-deprecating-baremetal
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140527/48c98d17/attachment.html>