[openstack-dev] [oslo.messaging][feature freeze exception] Can I get an exception for AMQP 1.0?
Doug Hellmann
doug at doughellmann.com
Wed Sep 3 19:23:52 UTC 2014
On Sep 3, 2014, at 2:03 PM, Ken Giusti <kgiusti at gmail.com> wrote:
> Hello,
>
> I'm proposing a freeze exception for the oslo.messaging AMQP 1.0
> driver:
>
> https://review.openstack.org/#/c/75815/
>
> Blueprint:
>
> https://blueprints.launchpad.net/oslo.messaging/+spec/amqp10-driver-implementation
>
> I presented this work at the Juno summit [1]. The associated spec has
> been approved and merged [2].
>
> The proposed patch has been in review since before icehouse, with a
> couple of non-binding +1's. A little more time is necessary to get
> core reviews.
>
> The patch includes a number of functional tests, and I've proposed a
> CI check that will run those tests [3]. This patch is currently
> pending support for bare fedora 20 nodes in CI. I'm planning to add
> additional test cases and devstack support in the future.
>
> I'm in the process of adding documentation to the RPC section of the
> Openstack manual.
>
> Justification:
>
> I think there's a benefit to have this driver available as an
> _experimental_ feature in Juno, and the risk of inclusion is minimal
> as the driver is optional, disabled by default, and will not have
> impact on any system that does not explicitly enable it.
>
> Unlike previous versions of the protocol, AMQP 1.0 is the official
> standard for AMQP messaging (ISO/IEC 19464). Support for it is
> arriving from multiple different messaging system vendors [4].
>
> Having access to AMQP 1.0 functionality in openstack sooner rather
> than later gives the developers of AMQP 1.0 messaging systems the
> opportunity to validate their AMQP 1.0 support in the openstack
> environment. Likewise, easier access to this driver by the openstack
> developer community will help us find and fix any issues in a timely
> manner as adoption of the standard grows.
>
> Please consider this feature to be a part of Juno-3 release.
>
> Thanks,
>
> Ken
Ken,
I think we’re generally in favor of including the new driver, but before I say so officially can you fill us in on the state of the additional external libraries it needs? I see pyngus on pypi, and you mention in the “Request to include AMQP 1.0 support in Juno-3” thread that proton is being packaged in EPEL and work is ongoing for Debian. Is that done (it has only been a few days, I know)?
I would like to avoid having that packaging work be a blocker, so if we do include the driver, what do you think is the best way to convey the instructions for installing those packages? I know you’ve done some work recently on documenting the experimental status, did that include installation tips?
Thanks,
Doug
>
>
> --
> Ken Giusti (kgiusti at gmail.com)
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
More information about the OpenStack-dev
mailing list