V2.1 comp mode behavior should be fixed for diff of v2 and v2.1 APIs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Ghanshyam Mann | ||
openstack-api-site |
Fix Released
|
Undecided
|
Matt Riedemann |
Bug Description
There are some cases where v2.1 is different than v2.0 -
- VIF API - no net-id in v2.1
- rate limit bits - not present in v2.1
- extension info - namespace diff
For above cases, current v2.1 compatible mode behaves same as v2.1 not v2.
Failure in - http://
As v2.1 comp mode should behave same as v2 instead of v2.1, we should fix those cases to return same response as v2 APIs does.
I am not sure about rate limit and extension info things, should we fix those?
It was found when we start running v2.1 comp mode sample test against v2 sample files instead of v2.1 one. - https:/
Changed in nova: | |
assignee: | nobody → Ghanshyam Mann (ghanshyammann) |
Changed in nova: | |
milestone: | none → liberty-rc1 |
tags: | added: liberty-rc-potential |
Changed in nova: | |
importance: | Undecided → High |
tags: | added: api |
tags: | removed: liberty-rc-potential |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | liberty-rc1 → 12.0.0 |
For ratelimit, if user add the Ratelimit Middleware back, then the rate limits bits in the API will works, so we can fix it by add to api-paste.ini
For extension info, I think it's fine, the namespace is just for XML I think, so actually it is useless thing.
For VIF API, it is hard one. As we already remove the extension info API entry for extend-vif-net, so at least that won't break the user. /review. openstack. org/#/c/ 198944/ . So fix it in v2.1 isn't option, but we can fix it in v2.1 compat mode only.
And we decided we add those extend vif net atributes back with Microversions, and we already did that https:/