Hello,


I recently noticed that python-consul2 library[1], which is used by
the consul coordination driver in tooz, hasn't been updated for 3+ years.

Looking at issues in the project, there is an indication that the library
is not compatible with ACL API in consul >= 1.11[2]. There is another fork
created[3] and this includes fixes to support new API endpoints.

Although the driver in tooz does not directly use the feature, I think it's
better to discuss our plan to mitigate risks caused by the unmaintained library.


As far as I can think of, there are three options now

  1. Deprecate consul driver and remove it

  2. Keep using python-consul2 now. At least basic functionality is proven to
     work by our functional tests (Note that the tests do not cover all configuration
     patterns)

  3. Replace python-consul2 by py-consul


Before we start the overall discussions I'd like to ask a few questions to
the wider audience, as our inputs.

  - Is anyone using the consul coordination driver now ?

  - Does anyone have experience with python-consul2 and/or py-consul ?


Note that this discussion affects the http messaging driver[4] currently
proposed, because it also requires client library to communicate with Consul.
Actually I noticed the situation when I noticed that the requirement check
job is failing because the library is not part of global requirements list...


Thank you,
Takashi Kajinami


[1] https://github.com/poppyred/python-consul2
[2] https://github.com/poppyred/python-consul2/issues/42
[3] https://github.com/criteo-forks/py-consul
[4] https://review.opendev.org/c/openstack/oslo.messaging/+/912499


--
Takashi Kajinami
irc: tkajinam
github: https://github.com/kajinamit
launchpad: https://launchpad.net/~kajinamit