Project

Profile

Help

Task #3340

closed

Task #3291: Switch Pulp to AMQP 1.0

Testing of new Kombu stack

Added by bmbouter about 6 years ago. Updated about 5 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
Yes
Tags:
Pulp 2
Sprint:
Quarter:

Description

There are many feature aspects of the Qpid transport for Kombu that Pulp relies on. Recently this Qpid transport for Kombu was entirely rewritten. Before we enable it for either Pulp2 users ( issue 3134 ) or Pulp3 users ( issue 3292) we need to ensure that everything Pulp relies on is working.

As the author of the Kombu changes [0], I've already hand-tested all of this, so now it's time for independant testing. Here are all of the high level things that need to work:

Connect and Reconnect Testing

  • Verify that if Pulp is started but Qpid is stopped, that when Qpid does start and become available that Pulp connects and is fully working. A basic sync will prove the "fully working part".
  • Verify that "reconnect support" works. Have Pulp already connected to Qpid and functioning correctly. Then stop qpidd, but leave all Pulp processes running. After say

Authentication testing

  • Verify that if qpidd requires no authentication, that Pulp can connect to qpidd and function properly.
  • Verify that if qpidd requires SASL authentication, that Pulp can be correctly configured and function properly.
  • Verify that if qpidd requires the client to present a certificate via EXTERNAL auth that Pulp can be correctly configured to present that certificate, can connect, and can function properly.
  • Verify that the Pulp can be configured to require the server to present a trusted certificate. Specifically Pulp needs to be configured to trust the CA that qpidd is presenting. In this configuration verify that Pulp can function properly.
  • Verify that mutual authentication works. Specifically this is the client requiring a trusted cert from qpidd, and qpidd requiring a trusted cert from the client. These are the above two test scenarios only tested together.
  • Verify that an incorrect authentication configuration does not try to reconnect. Reconnecting with the same incorrect credentials needs to not happen.
  • Verify that when celery_require_ssl is False that Pulp can connect to qpidd without TLS
  • Verify that when celery_require_ssl is True that Pulp can not connect to qpidd without TLS

Queue, Exchange, and Bindings settings

  • Verify that all of the same queues are created and have identical properties when using the new Kombu transport versus the older one.
  • Verify that all of the same exchanges are created and have identical properties when using the new Kombu transport versus the older one.
  • Verify that all of the same bindings are created and have identical properties when using the new Kombu transport versus the older one.

[0]: https://github.com/celery/kombu/pull/810/files


Files

amqp_upgrade.txt (43.5 KB) amqp_upgrade.txt pthomas@redhat.com, 03/01/2018 06:30 PM

Also available in: Atom PDF