Open Stack

Clark Boylan <cboylan at sapwetik.org> writes:

>>    The other thing is that we don't have the zuul code to vote with 
>>    a different account deployed/merged yet. So initially you could run
>>    your 
>>    job but it wouldn't vote against, say, cinder.»
> The stack that adds the necessary zuul stuff ends with
> https://review.openstack.org/#/c/121528/

I don't believe that we have any current plans to use that code in
infra.  I don't believe that it makes sense for us to create multiple
accounts in Gerrit for our single system.  It's quite a bit of overhead,
and I don't believe it is necessary.

To be clear, I think any policy that says that drivers must have
"third-party CI" is an oversight.  I believe that it's fine to require
them to have "CI", but if the CI can be provided by infra, it should be.
I believe this misunderstanding comes from the fact that most
out-of-tree drivers require specialized hardware, or non-free software,
that can not be run in our system.

As mentioned elsewhere, we're generally quite happy to have any open
source component tested in the upstream infrastructure.  Since this
qualifies, I think the quickest and simplest way to proceed is to create
a job that runs on the driver repo, and then create a non-voting version
to run on the cinder repo.

Additionally, if it proves stable, the Cinder developers could certainly
choose to gate on this job as well.  That's entirely up to them, but
there's no policy or technical reason it can not.

-Jim