Blazar client v2 API support
Summary
========
Support v2 API at Blazar client.
Problem description
================
Currently, the Blazar client supports only v1 API. It should be extended to support v2 API.
Related patch have been proposed but abandoned [2].
Use Cases
---------------
- TBD
Proposed change
==============
TBD
Alternatives
-----------------
TBD
Data model impact
-------
TBD
REST API impact
-------
TBD
Security impact
-------
TBD
Notifications impact
-------
TBD
Other end user impact
-------
TBD
Performance impact
-------
None.
Other deployer impact
-------
TBD
Developer impact
-------
TBD
Dependencies
===========
TBD
Testing
======
TBD
Documentation impact
==================
TBD
References
=========
[1] https:/
[2] https:/
Note: this form is based on the nova-specs template[1].
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Low
- Drafter:
- Christian Martinez
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
- Pierre Riteau
Related branches
Related bugs
Sprints
Whiteboard
History:
[cmart]: According to Sylvain, the v1 and v2 API versions are quite identical right now (except for the functionality to be added on the https:/
[cmart] Slow progress due to some discussion around REST API Versioning (http://
Gerrit topic: https:/
Addressed by: https:/
Modify endpoint for multiple version support
Work Items
Dependency tree
* Blueprints in grey have been implemented.
