© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
The alternative is on the nova side, we just construct a cinderclient Client object and use it's internal client (session) to make a request, or use a keystoneauth1 adapter to make the request. I'm not sure if all of the version negotiation checking that's happening in cinderclient is something we need to worry about, i.e. what happens in here:
https:/
That's just making sure that both the cinderclient and server support the microversion that nova cares about. Nova can control the minimum required version of cinderclient via requirements.txt, and could get the server version via keystoneauth1.