Open Stack

Excerpts from Jim Rollenhagen's message of 2016-01-08 12:30:33 -0800:
> On Fri, Jan 08, 2016 at 03:13:15PM -0500, Doug Hellmann wrote:
> > Excerpts from Jim Rollenhagen's message of 2016-01-08 11:52:51 -0800:
> > > On Fri, Jan 08, 2016 at 02:08:04PM -0500, Jay Pipes wrote:
> > > > On 01/07/2016 07:38 PM, Jim Rollenhagen wrote:
> > > snippity snip snip
> > > 
> > > > >We haven't made it a dep for anything yet, only added to g-r.
> > > > 
> > > > According to Dims, not to g-r, but to u-c, right Dims? Not sure if that
> > > > makes functionally any difference, though (pun intended).
> > > 
> > > Both. https://review.openstack.org/#/c/220268/
> > > 
> > > This thread was originally about twisted, which is added to u-c with the
> > > introduction of mimic.
> > > 
> > > > >However, now that you mention that, a really ambitious goal would be to
> > > > >add a rabbit interface to mimic, and functionally test the API server
> > > > >(that it sends the right messages, etc). Another would be to mimic
> > > > >(Neutron, Glance) and test Ironic by itself.
> > > > 
> > > > So you would reimplement AMQP communication protocols using an in-memory
> > > > data store for queues. Sounds like an even greater surface area for bugs to
> > > > be introduced.
> > > > 
> > > > >Last, I frankly don't understand why there's
> > > > >such heavy opposition to the ironic team using an additional tool for
> > > > >testing.
> > > > 
> > > > Since you asked, I'll be blunt. This isn't a personal attack on you, Jim,
> > > > though.
> > > > 
> > > > a) Because it fractures the testing and QA processes used by upstream
> > > > contributors that work on OpenStack projects by requiring them to learn
> > > > another system -- and one that potentially would require them to understand
> > > > a whole new surface area for potential bugs
> > > 
> > > I don't think there's a large risk of needing to dig deep into mimic,
> > > and especially twisted. If this does prove to be a problem, I'm happy to
> > > remove it. However, we can't even explore what it would be like, or how
> > > hard we would depend on mimic, without mimic being in g-r.
> > > 
> > > > b) Because it represents yet another RAX-driven divergence in the QA space.
> > > > CloudCafe took essentially all of the RAX folks that were at one point
> > > > working on Tempest and upstream QA and siloed them into a totally different
> > > > organization, in true RAX fashion. Instead of pulling the OpenStack QA
> > > > community along together, RAX QA continues to just do its own thing and
> > > > there's still bitterness on the tips of tongues.
> > > 
> > > So, this isn't trying to replace anything. This is adding a different
> > > way to run functional tests, that is *much* faster than standing up a
> > > full ironic environment. This is helpful for developers that want to
> > > quickly run tests before posting them to gerrit, people that need to
> > > test in constrained environments, etc.
> > 
> > So it won't be used in the gate, just on local developer systems?
> 
> Initially, yes. I'd like to also add it to the gate at some point to
> make sure we don't break those interactions, though I could deal with a
> non-voting job just in case.

OK, if that's the case then although I share Jay's concerns about bug
surface area and keeping the APIs in sync, I think the risk is low
enough that it would only annoy developers and not actually allow bugs
to slip through testing. So, I'm OK with continuing with the experiment
in Ironic.

Doug