It's been a bit since the summit but I believe this was also discussed at the Denver PTG as well: https://etherpad.openstack.org/p/oslo-ptg-queens
The keystoneauth stuff seems to be more from Sydney, but if I remember correctly, Castellan authenticates through keystoneauth and passes the session to barbicanclient. This is the only use of keystoneauth within Castellan, so one idea that was mentioned was to see if Castellan could simply pass the credentials to barbicanclient, which would auth through keystoneauth instead, removing the dependency from Castellan. On Tue, Dec 5, 2017 at 10:54 AM, Doug Hellmann <d...@doughellmann.com> wrote: > Excerpts from ARORA, ROHAN's message of 2017-12-05 14:37:49 +0000: > > So from my understanding now, we are wanting to remove the HARD > dependency on Keystoneauth, not to remove it completely since that would > break the barbican client. Currently seeing if we just remove the > dependency from requirements.txt, if that stops Keystoneauth from being > used until you try to use the barbican. > > There would need to be more changes than that, because we still need the > package to be installed for testing the Barbican driver. > > Maybe if someone could explain what the issue is, I can offer more > detailed advice. What is wrong with having the keystoneauth dependency? > Is it breaking something? Is it interfering with some other library? > > Doug > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
