On Thu, Feb 5, 2015 at 11:37 AM, Andrey Kurilin akuri...@mirantis.com
wrote:
First results is https://review.openstack.org/#/c/152569/
- if os-compute-api-version is not supplied don't send any header at all
- it is probably worth doing a bit version parsing to see if it makes
sense eg of
First results is https://review.openstack.org/#/c/152569/
- if os-compute-api-version is not supplied don't send any header at all
- it is probably worth doing a bit version parsing to see if it makes
sense eg of format:
r^([1-9]\d*)\.([1-9]\d*|0)$ or latest
implemented
- handle
Thanks for the summary, I'll try to send first patch(maybe WIP) in few days.
On Mon, Feb 2, 2015 at 1:43 PM, Christopher Yeoh cbky...@gmail.com wrote:
On Sat, Jan 31, 2015 at 4:09 AM, Andrey Kurilin akuri...@mirantis.com
wrote:
Thanks for the answer. Can I help with implementation of
On Sat, Jan 31, 2015 at 4:09 AM, Andrey Kurilin akuri...@mirantis.com
wrote:
Thanks for the answer. Can I help with implementation of novaclient part?
Sure! Do you think its something you can get proposed into Gerrit by the
end of the week or very soon after?
Its the sort of timeframe we're
Thanks for the answer. Can I help with implementation of novaclient part?
On Wed, Jan 28, 2015 at 11:50 AM, Christopher Yeoh cbky...@gmail.com
wrote:
On Fri, 23 Jan 2015 15:51:54 +0200
Andrey Kurilin akuri...@mirantis.com wrote:
Hi everyone!
After removing nova V3 API from novaclient[1],
On Fri, 23 Jan 2015 15:51:54 +0200
Andrey Kurilin akuri...@mirantis.com wrote:
Hi everyone!
After removing nova V3 API from novaclient[1], implementation of v1.1
client is used for v1.1, v2 and v3 [2].
Since we moving to micro versions, I wonder, do we need such
mechanism of choosing api
Hi everyone!
After removing nova V3 API from novaclient[1], implementation of v1.1
client is used for v1.1, v2 and v3 [2].
Since we moving to micro versions, I wonder, do we need such mechanism of
choosing api version(os-compute-api-version) or we can simply remove it,
like in proposed change -
