7ca32bb3e8
1. What is the problem? Both the blueprint and implementation of the resource routing API have been completed, so release notes are required for these new features. This patch adds the release notes for them. Moreover, the releasenotes test environment should be added to the tox.ini. The reno version should be given in test-requirements.txt. 2. What is the solution to the problem? Add release notes for the resource routing API in the new file releasenotes/notes/resource-routing-operation.yaml. Add the releasenotes test environment to file tox.ini and reno version to the test-requirements.txt. 3. What the features need to be implemented to the Tricircle to realize the solution? No new features. Change-Id: I23c9b3fb97b33f15a877eb2dbcabbb823c825d6d
23 lines
900 B
YAML
23 lines
900 B
YAML
---
|
|
features:
|
|
- |
|
|
Resource routing APIs add operations on resource routing
|
|
table. This makes it possible to create, show, delete
|
|
and update the resource routing entry in the resource
|
|
routing by cloud administrator for the maintenance and
|
|
emergency fix need. But the update and delete operations
|
|
on the entry generated by the Tricircle itself is not
|
|
proposed, because central Neutron may make wrong
|
|
judgement on whether the resource exists or not
|
|
without this routing entry. Moreover, related request
|
|
can not be forwarded to the proper local Neutron
|
|
either. So even though the update and delete operations
|
|
are provided, they are better not to be used in case of
|
|
causing unexpected problems.
|
|
|
|
* List resource routings
|
|
* Create resource routing
|
|
* Show resource routing details
|
|
* Delete resource routing
|
|
* Update resource routing
|