Hi, The AMQP 1.0 blueprint proposed for oslo.messaging Juno [0] introduces dependencies on a few packages that provide AMQP functionality.
These packages are: * pyngus - a client API * python-qpid-proton - the python bindings for the Proton AMQP library * qpid-proton: the AMQP 1.0 library. pyngus is a pure-python module available at pypi [1]. python-qpid-proton is also available at pypi [2], but it contains a C extension. This C extension requires that the qpid-proton development libraries are installed in order to build the extension when installing python-qpid-proton. So this means that oslo.messaging developers, as well as the CI systems, etc, will need to have the qpid-proton development packages installed. These packages may be obtained via EPEL for Centos/RHEL systems (qpid-proton-c-devel), and via the Qpid project's PPA [3] (libqpid-proton2-dev) for Debian/Ubuntu. They are also available for Fedora via the default yum repos. Otherwise, the source can be pulled directly from the Qpid project and built/installed manually [4]. I'd like to get the blueprint accepted, but I'll have to address these new dependencies first. What is the best way to get these new packages into CI, devstack, etc? And will developers be willing to install the proton development libraries, or can this be done automagically? thanks for your help, [0] https://blueprints.launchpad.net/oslo.messaging/+spec/amqp10-driver-implementation [1] https://pypi.python.org/pypi/pyngus [2] https://pypi.python.org/pypi/python-qpid-proton/0.7-0 [3] https://launchpad.net/~qpid [4] http://qpid.apache.org/download.html -- Ken Giusti (kgiu...@gmail.com) _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev