1. What is the problem
When we use admin role for demo project to retrieve jobs/routings
through Admin API, return results include admin project's
jobs/routings. The result should be only related to demo project.
2. What is the solution for the problem
Extract project ID from context and use it as filter. The project
ID filter in URL query string will be ignored, and only the project ID
in which the user is authorized will be used as the filter.
3. What the features need to be implemented to the Tricircle to
realize the solution
Choose project ID as mandatory filter for jobs/routings list operation.
Change-Id: I86778e0525c1fecf45bc473bd42e62909534778b
Closes-Bug: #1711001
Closes-Bug: #1711003
1. What is the problem?
Currently no doc about how to use Tricircle CLI.
2. What is the solution to the problem?
Add the simplest guide for Tricircle CLI, and check to see
whether the stable/pike branch can pass all tests or not.
3. What features need to be implemented to the Tricircle to realize
the solution?
None
Change-Id: Ic612ad6e8ca4a7993745a1da8e4cd3f1bcefcbf0
Signed-off-by: joehuang <joehuang@huawei.com>
1. What is the problem
Job pagination list operation supports pagination now, the
implementation patch is here [1]. We need to add documentation
for it.
2. What is the solution for the problem
Add documentation for pagination feature of the job list
operation.
3. What the features need to be implemented to the Tricircle to
realize the solution
None.
[1] https://review.openstack.org/480326
Change-Id: I6c8e007b6a7781b4102be4504e8f315147b33bfe
1. What is the problem
Tricircle directory doc/source has been refactored, some links in README
are disabled.
2. What is the solution for the problem
Update the links in README file to the latest.
3. What the features need to be implemented to the Tricircle to
realize the solution
None.
Change-Id: I1f94d0c6349b6e679214e6b0b1b4773d030abe17
1. What is the problem
Tricircle cli has been implemented and can be used instead of curl,
it's more user friendly and convenient.
2. What is the solution for the problem
Update curl command with tricircle cli.
3. What the features need to be implemented to the
tricircle to realize the solution
None.
Change-Id: Ib272c9cb53db06eb7185661953af1b46f54790d0
1. What is the problem
Doc migration requires that the installation, admin and configuration
guides have to be put into related directories.
2. What is the solution for the problem
Put configuration, install and admin guide into related sub-folders.
3. What the features need to be implemented to the
tricircle to realize the solution
None.
Closes-Bug: #1706190
Change-Id: I1e1909a373e92b29460b364de38cc25aba038776
1. What is the problem
Job list operation supports pagination now, it can be found here [1],
we need to add release note for it.
2. What is the solution for the problem
Add release note for job pagination feature.
3. What the features need to be implemented to the Tricircle to
realize the solution
None.
[1] https://review.openstack.org/480326
Change-Id: Icc90f39ee980d59539598ed711e629539bdd58d3
1. What is the problem
Smoke test engine has been implemented[1] and tests for single
north-south gateway topology and multiple north-south gateway
topology have been added. But we still lack test for service
function chain.
2. What is the solution for the problem
Define service function chain related test using YAML file.
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
[1] https://review.openstack.org/#/c/477500/
Implements: blueprint smoke-test-engine
Change-Id: I02a9bc8a6c7cebe166a633764e424e3812a9a042
1. What is the problem
The job list operations will retrieve all the items in
the database, which will consume too much memory and take long time
to response when the results are considerably large.
2. What is the solution for the problem
To reduce load on the service, list operations will return a maximum
number of items at a time by pagination. To navigate the collection,
the parameters limit and marker can be set in the URI. For example:
/v1.0/jobs?limit=2000&marker=500
The marker parameter is the ID of the last item in the previous list.
The limit parameter sets the page size. These parameters are optional.
If the client requests a limit beyond the maximum limit configured by
the deployment, the server returns the maximum limit number of items.
Pagination and filtering can work together for job list operations.
3. What the features need to be implemented to the Tricircle to
realize the solution
Add pagination feature for job list operations.
Change-Id: I95168a547ac88d8a680102acaac1bdda6dde0733
1. What is the problem
Smoke test engine has been implemented[1] and tests for single
north-south gateway topology and multiple north-south gateway
topology have been added. But we still lack test for trunk.
2. What is the solution for the problem
Define trunk related test using YAML file.
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
[1] https://review.openstack.org/#/c/477500/
Implements: blueprint smoke-test-engine
Change-Id: If9df9983350ea442dab6106cb58d49590c0677b1
1. What is the problem
There are some differences between available resource types [1] and resource
type validation table [2]. Some resources in [1] also need resource mapping
between central Neutron and local Neutron, but they are not added to resource
type validation table in [2].
2. What is the solution for the problem
Add some resource types to resource type validation table.
3. What the features need to be implemented to the tricircle to
realize the solution
None.
[1] https://github.com/openstack/tricircle/blob/master/tricircle/common/constants.py#L23
[2] https://github.com/openstack/tricircle/blob/master/tricircle/common/constants.py#L47
Change-Id: I6426964d5a83e4e18b462a2ab96af6d49883c9e2
1. What is the problem
In the recent unit test runs, sometimes test_routing.py fails with
error "duplicate option: bind_host".
2. What is the solution for the problem
Make RoutingControllerTest inherit from tricircle.tests.base.TestCase
because TestCase will resolve the conflict.
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
Change-Id: I5933e7fadd01c69ad9715813e8d347ac7ccba487
1. What is the problem
Smoke test engine has been implemented[1] and a smoke test for
single north-south gateway topology has also been added. But
we still lack test for multiple north-south gateway topology.
2. What is the solution for the problem
Define the test using YAML file.
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
[1] https://review.openstack.org/#/c/477500/
Implements: blueprint smoke-test-engine
Change-Id: Ied0693add47d479e7c6a01e09928d601635b1438
Depends-On: Ice098ce020c85f74d008c1952dd1dd36350dec1d
Openstack common has a wrapper for generating uuids.
We should use that function to generate uuids for consistency.
Change-Id: I916add29ddf3bec423db5c21e3c822a2f0b50da4
1. What is the problem
Resource routing list operation supports pagination now, the
implementation patch is here [1]. We need to add documentation
for it.
2. What is the solution for the problem
Add documentation for pagination feature of the routing list
operation.
3. What the features need to be implemented to the Tricircle to
realize the solution
None.
[1] https://review.openstack.org/475223
Change-Id: I6c3a51d1033e0ea8e83c2257c24c849c858f5041
1. What is the problem
Current smoke test needs improvement
2. What is the solution for the problem
Implement a task runner and a task engine. The implementation is
based on the specification document[1].
3. What features need to be implemented to the Tricircle to
realize the solution
Smoke test engine is added
[1] https://github.com/openstack/tricircle/blob/master/specs/pike/smoke-test-engine.rst
Implements: blueprint smoke-test-engine
Change-Id: Ice098ce020c85f74d008c1952dd1dd36350dec1d
1. What is the problem
Resource routing list operation supports pagination now,
we need to add release note for it.
2. What is the solution for the problem
Add release note for routing pagination feature.
3. What the features need to be implemented to the Tricircle to
realize the solution
None.
Change-Id: I889859f4fb0935763f5147fe7de4558263a5dc31
1. What is the problem
The segment ID of local type network is allocated in the local Neutron
server, so it's possible that segment IDs of bridge network and local
network conflict, which results to failure when creating bridge network.
2. What is the solution for the problem
Since network AZ is implemented, we can deprecate the "local" network
type and only create a local network by specifying AZ as region name.
Before such deprecation, we change local type as the last network type
candidate to avoid users create a local type network by mistake.
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
Change-Id: I55a1b6a93bd43e28c05530161e23de26a8bb8f60
Partial-Bug: #1692415
1. What is the problem
The resource routing list operations will retrieve all the items in
the database, which will consume too much memory and take long time
to response when the results are considerably large.
2. What is the solution for the problem
To reduce load on the service, list operations will return a maximum
number of items at a time by pagination. To navigate the collection,
the parameters limit and marker can be set in the URI. For example:
/v1.0/routings?limit=2000&marker=500
The marker parameter is the ID of the last item in the previous list.
A marker with an invalid ID returns a badRequest (400) fault.
The limit parameter sets the page size. These parameters are optional.
If the client requests a limit beyond the maximum limit configured by
the deployment, the server returns the maximum limit number of items.
Pagination and filtering can work together with routing's list operations.
3. What the features need to be implemented to the Tricircle to
realize the solution
Add pagination feature for resource routing list operations.
Change-Id: I05d1b30f502103d247d8be06c1e52fdcec42b41e
1. What is the problem
Problems in the current smoke test:
(1) Mix use of bash and python scripts
(2) Resources are not cleaned at the end of the test
2. What is the solution for the problem
A proposed solution is discussed in the spec. The basic idea is
to define tests using YAML and use a engine to parse YAML and
run tests.
3. What features need to be implemented to the Tricircle to
realize the solution
A task engine and a task runner.
Change-Id: Ib7ca2242529e147e9edd6292eec3003967ea83f0
1. What is the problem
OpenStack doc team is doing OpenStack manuals project migraion, we
need to finish some required actions.
2. What is the solution for the problem
As described in the specification[1], we need switch to use html
theme openstackdocstheme instead of oslosphinx.
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
[1] http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html
Change-Id: I678ab6d7682ba016c9e77434693658c25c5d9778
Depends-On: I27481d9d28875837c0bbb4aec89c42aa07027135
1. What is the problem
OpenStack doc team is doing OpenStack manuals project migraion, we
need to finish some required actions.
2. What is the solution for the problem
As described in the specification[1], we need to enable warning-is-
error in setup.cfg and fix errors if any.
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
[1] http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html
Change-Id: I27481d9d28875837c0bbb4aec89c42aa07027135
1. What is the problem
Resource attributes are moved from neutron.api.v2.attributes to
neutron-lib.callbacks.resources.
2. What is the solution for the problem
Use the resource definition in neutron-lib.callbacks.resources
module instead.
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
Change-Id: I44dd334e6fea19286fee9821183af8b6458ecb48
OpenStack Release Bot
Dongfeng Huang
joehuang
OpenStack Proposal Bot
Jenkins
zhiyuan_cai
Fangming Liu
Kiran_totad
rajat29
chenxing