Open Stack

On 2019-03-31 11:03:34 +0100 (+0100), Sean Mooney wrote:
[...]
> so on the stablity of nested virt jobs in general i think we
> should try to enable nested virt but perhaps make the jobs non
> voting in check and excluded nested jobs from gate. that way we
> get some testing for things we cant other wise test but if we hit
> kenel bugs its a non voting jobs so if it fails it wont break the
> zuul jobs.

Well, having these jobs non-voting means you aren't relying on them
to protect you from merging changes which might break nested
virtualization or fail to work with it. But that aside, to even have
a guarantee it would be available at all we'd need a separate node
label for all our images which is restricted to providers where we
can expect it. For example, I've heard that doing nested virt
acceleration for KVM guests in our Xen-based providers is a long way
from being possible.
-- 
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190331/5deb1bad/attachment.sig>