Re: [openstack-dev] [oslo.messaging][feature freeze exception] Can I get an exception for AMQP 1.0?
On Sep 3, 2014, at 2:03 PM, Ken Giusti 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 Giusti (kgiu...@gmail.com) > This FFE was approved and the change linked above is currently in the merge queue. Doug ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo.messaging][feature freeze exception] Can I get an exception for AMQP 1.0?
On Sep 3, 2014, at 5:48 PM, Ken Giusti wrote: > On Wed Sep 3 19:23:52 UTC 2014, Doug Hellmann wrote: >> On Sep 3, 2014, at 2:03 PM, Ken Giusti wrote: >>> Hello, >>> >>> I'm proposing a freeze exception for the oslo.messaging AMQP 1.0 >>> driver: >>> >>> https://review.openstack.org/#/c/75815/ > >>> 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)? >> > > Hi Doug, > > Yes, AMQP 1.0 tech is pretty new, so the availability of the packages > is the sticking point. > > That said, there are two different dependencies to consider: > oslo.messaging dependencies, and AMQP 1.0 support in the brokers. > > For oslo.messaging, the dependency is on the Proton C developer > libraries. This library is currently available on EPEL for centos6+ > and fedora. It is not available in the Ubuntu repos yet - though they > have recently been accepted to Debian sid. For developers, the QPID > project maintains a PPA that can be used to get the packages on > Debian/Ubuntu (though this is not acceptable for openstack CI > support). The python bindings > that interface with this library are available on pypi (see the > amqp1-requirements.txt in the driver patch). This seems sufficient for now. We won’t list the dependencies directly for oslo.messaging, so the libs don’t necessarily need to be available as packages until we bring it out of “experimental” status (and that move will be blocked based on availability of the libs). > > Qpid upstream has been shipping with 1.0 support for awhile now, but > unfortunately the popular distros don't have the latest Qpid brokers > available. Qpid with AMQP 1.0 support is available via EPEL for > centos7 and fedora. RedHat deprecated Qpid on rhel6, so now centos6 is > stuck with an old version of qpid since we can't override base > packages in EPEL. Same deal with Debian/Ubuntu, though the QPID PPA > should have the latest packages (I'll have to follow up on that). > > >> 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? > > Not at present, but that's what I'm working on at the moment. I'll > definitely call out the installation dependencies and configuration > settings necessary for folks to get the driver up and running with a > minimum of pain. > > I assume I'll have to update at least: > > The wiki: https://wiki.openstack.org/wiki/Oslo/Messaging > The user manuals: > http://docs.openstack.org/icehouse/config-reference/content/configuring-rpc.html > > I can also add a README to the protocols/amqp directory, if that makes sense. Sounds good. Those updates should allow deployers who want to use the driver to find out what else they need to install, and how to get it for their platforms. Doug > >> >> Thanks, >> Doug > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [oslo.messaging][feature freeze exception] Can I get an exception for AMQP 1.0?
On Wed Sep 3 19:23:52 UTC 2014, Doug Hellmann wrote: >On Sep 3, 2014, at 2:03 PM, Ken Giusti wrote: >> Hello, >> >> I'm proposing a freeze exception for the oslo.messaging AMQP 1.0 >> driver: >> >> https://review.openstack.org/#/c/75815/ >> 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)? > Hi Doug, Yes, AMQP 1.0 tech is pretty new, so the availability of the packages is the sticking point. That said, there are two different dependencies to consider: oslo.messaging dependencies, and AMQP 1.0 support in the brokers. For oslo.messaging, the dependency is on the Proton C developer libraries. This library is currently available on EPEL for centos6+ and fedora. It is not available in the Ubuntu repos yet - though they have recently been accepted to Debian sid. For developers, the QPID project maintains a PPA that can be used to get the packages on Debian/Ubuntu (though this is not acceptable for openstack CI support). The python bindings that interface with this library are available on pypi (see the amqp1-requirements.txt in the driver patch). Qpid upstream has been shipping with 1.0 support for awhile now, but unfortunately the popular distros don't have the latest Qpid brokers available. Qpid with AMQP 1.0 support is available via EPEL for centos7 and fedora. RedHat deprecated Qpid on rhel6, so now centos6 is stuck with an old version of qpid since we can't override base packages in EPEL. Same deal with Debian/Ubuntu, though the QPID PPA should have the latest packages (I'll have to follow up on that). >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? Not at present, but that's what I'm working on at the moment. I'll definitely call out the installation dependencies and configuration settings necessary for folks to get the driver up and running with a minimum of pain. I assume I'll have to update at least: The wiki: https://wiki.openstack.org/wiki/Oslo/Messaging The user manuals: http://docs.openstack.org/icehouse/config-reference/content/configuring-rpc.html I can also add a README to the protocols/amqp directory, if that makes sense. > >Thanks, >Doug ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo.messaging][feature freeze exception] Can I get an exception for AMQP 1.0?
On Sep 3, 2014, at 2:03 PM, Ken Giusti 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 (kgiu...@gmail.com) > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [oslo.messaging][feature freeze exception] Can I get an exception for AMQP 1.0?
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 Giusti (kgiu...@gmail.com) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
