[openstack-dev] [oslo.messaging] ZeroMQ driver maintenance next steps

Denis Makogon dmakogon at mirantis.com
Mon Nov 17 18:39:23 UTC 2014

понедельник, 17 ноября 2014 г. пользователь James Page написал:

> Hash: SHA256
> On 17/11/14 09:01, Denis Makogon wrote:
> > I'm not sure I understand you statement about them not being
> > "gate"-able - the functional/unit tests currently proposed for the
> > zmq driver run fine as part of the standard test suite execution -
> > maybe the confusion is over what 'functional' actually means, but
> > in my opinion until we have some level of testing of this driver,
> > we can't effectively make changes and fix bugs.
> >
> > I do agree that there's a confusion what "functional testing"
> > means. Another thing, what the best solution is? Unit tests are
> > welcome, but they are still remain to be units (they are using
> > mocks, etc.) I'd try to define what 'fuctional testing' means for
> > me. Functional testing in oslo.messaging means that we've been
> > using real service for messaging (in this case - deployed 0mq). So,
> > the simple definition, in term os OpenStack integration, we should
> > be able to run full Tempest test suit for OpenStack services that
> > are using oslo.messaging with enabled zmq driver. Am i right or
> > not?
> 0mq is just a set of messaging semantics on top of tcp/ipc sockets; so
> its possible to test the entire tcp/ipc messaging flow standalone i.e.
> without involving any openstack services.  That's what the current
> test proposal includes - unit tests which mock out most things, and
> base functional tests that validate the tcp/icp messaging flows via
> the zmq-receiver proxy.  These are things that *just work* under a tox
> environment and don't require any special setup.
> Hm, I see what you've been trying to say. But unfortunately it breaks
whole idea of TDD. Why can't we just spend some time on getting non-voting
gates? Ok, let me describe what would satisfy all of us: Lest write up docs
that are describes how to setup(manually) environment to test out income

So, in any way. This topic is not for disagreement. It's for building out
team relationship.
I'd like to discuss next steps on developing zmq driver.

Kind regards,
Denis M.

> This will be supplemented with good devstack support and full tempest
> gate, but lets start from the bottom up please!  The work that's been
> done so far allows us to move forward with bug fixing and re-factoring
> that's backed up on having a base level of unit/functional tests.
> - --
> James Page
> Ubuntu and Debian Developer
> james.page at ubuntu.com <javascript:;>
> jamespage at debian.org <javascript:;>
> Version: GnuPG v1
> iQIcBAEBCAAGBQJUajaZAAoJEL/srsug59jDm2wP/1xW99gc/63CXnNowJLwgCAK
> AflhWs4SAUSF0VizOFoys6j1ApjAwWDG33B927REH/YDNwmAd7PgHRilgcaBjR5w
> pgaPRctCHPpWtJCWRCAmgkogqJotN3gTDKORxRNaWo9otzjQQbyPP5sEzuLl86/8
> 0n9KjwhjdJV42fcoKYvWt18uvz9yVOQLlPqj0WhAuzfpeP/5ZkXkd/dOvh6rwJnk
> wc+ZExPBhdeMNwaJFPZvle++Ki6tZCV8P8+Be5rqTZxdnGxoct72YnIohW48E9Nu
> 1sjdJCg42vxIMZi8NfkJDDfTBWzOmkab2jcViIJd9ycTn8CT/e62ZK8nN/hnIjla
> qU8pdRxNkY7xY3AuVoTWYRZGAon+Pp6Xw3J+lh7xUYukKtP/PaN+PjLCmVYrfca0
> JQnc8N5bLfcZkz/tx8R09hxqV7cpaRZh/lM6D62XEMRQJ7y9rcUIaJQnHbsmqLw9
> lwriXjNE/77eyttQlGnItyBZrTFjCFED9zg6ihK5w0DNXQr3CbIvlgCjiWkXfxDD
> 1QK05SbsukSlnO+Aqfs/HNICMdiZmqxcqcUcVs/XnKXf5Bi/Y/P0haLb43nFoa3E
> FaOYvY/T5HSJDvrFK6+kzPgT2zF3sWy4bZjRwKLl8GM8Mm7K65nfd5APhVCnQq5X
> yZOvpJehduiy6W/lQgzk
> =HAiM
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org <javascript:;>
> 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/20141117/a3be38a9/attachment.html>

More information about the OpenStack-dev mailing list