1. What is the problem?
Tricircle now don't support QoS service, we should add QoS
servicesupporting.
2. What is the solution to the problem?
We implement Tricircle QoS service by inherit neutron QoS plugin.
For QoS automation deployment in local, we should implement QoS xjob
jobs.
Change-Id: Ifbf453b57f7e18919318e1dae2ca2849e149a29b
Signed-off-by: xiaohan zhang <zhangxiaohan@szzt.com.cn>
1. What is the problem?
Our l3 unit test fails because of a patch[1] that migrates to use OVO
model for subnet and the model validates whether the ipv6_ra_mode and
ipv6_address_mode fields are set as the enumeration values.
2. What is the solution to the problem?
Set ipv6_address_mode and ipv6_ra_mode as "slaac" to meet the requirement.
3. What features need to be implemented to the Tricircle to realize
the solution?
N/A
[1] af00cbc3d2
Change-Id: Icaaaf7fc08eb689dbf4437da9fe0714fcdedc250
1. What is the problem?
Currently when users update the default security group it
will raise an exception. So we can't update default security
group. When we create or delete rules it uses a synchronous way to
create or delete the related rules in bottom pod. In order
to accelerate response we need to use an asynchronous way.
2. What is the solution to the problem?
Enable default security group to support add rules and
delete rules. Using Xjob to create or delete related rules
in bottom pod.
3. What the features need to be implemented to the Tricircle
to realize the solution?
Allow users to update default security group.
Change-Id: Ibf896f15390b656bda6d438bd3176e4b15dd359c
Commit I81748aa0e48b1275df3e1ea41b1d36a117d0097d added the l3 extension
API definition to neutron-lib, commit
I2324a3a02789c798248cab41c278a2d9981d24be rehomed the l3 exceptions and
Ifd79eb1a92853e49bd4ef028e7a7bd89811c6957 shims the l3 exceptions in
neutron.
This patch consumes the l3 API definition from neutron-lib
in prep for If2e66e06b83e15ee2851ea2bc3b64ad366e675dd
Change-Id: Ia63996c641de43472445f6e8ebdb259f89e2b10c
1. What is the problem?
Trunk test only covers create and delete
2. What is the solution to the problem?
Add add/remove sub-port scenario for the trunk test
3. What the features need to be implemented to the Tricircle
to realize the solution?
No new features.
Change-Id: Ic4cab8c6e41933ebad8cac6116bb35fc75759306
Signed-off-by: Yaguang Chen <chenyaguang@szzt.com.cn>
1. What is the problem
Both unit test and smoke test for sfc feature fail because changes
in neutron and networking-sfc project.
2. What is the solution for the problem
(1) Modify sfc unit test to correctly construct object model.
(2) Temporarily disable sfc smoke test because of a sfc bug[1].
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
[1] https://bugs.launchpad.net/networking-sfc/+bug/1730076
Change-Id: Iefa6810c48cbbc6171a8e02ea19429c8bdb2e366
1. What is the problem?
When adding a member for a load balancer, neutron lbaas checks whether
the members subnet exists. If it does not exist, local neutron creates
one. Currently, local neutron creates subnet with assuming that the
network already exists, leading failure of creating subent.
2. What is the solution to the problem?
Before creating a subnet, local neutorn checks whether the network
exist. If not, creating the network, then the subnet.
3. What the features need to be implemented to the Tricircle
to realize the solution?
No new features.
Change-Id: I276445e53a1c35de9263c8c871e5bf3723b4bcfb
The ml2 plugin driver API was rehomed into neutron-lib with commit
Ifc829953ef4d5859c3475903965dc08aba42fd9c and the API was shimmed in
neutron with I86a10091b55d1123e8d16f16155e0312bb10e54c. In prep for
neutron consumption Ice49572e217eeaf820e48d40f2251d08766490b5 this
patch switches over to lib's version of the respective code.
Change-Id: If6e20cf90cdf61a05a499f1251376db498e5e7c0
1. What is the problem
A new change Icd4bf90d54f4edb443467b192e4e639fde749d4e is merged in
networking-sfc, making unit tests fail.
2. What is the solution for the problem
Add an attribute "tap_enabled" for PortPairGroup in the unit tests
for sfc, and set it as False.
3. What features need to be implemented to the Tricircle to
realize the solution
N/A.
Change-Id: I0e92117be9a2beed809538412832c6a884fa1b55
The external network extension's API definition was rehomed into
neutron-lib with I9933b91d1e82db3891b3b72f06e94316e56a4f15. This patch
consumes it, switching over to neutron-lib's modules in prep for
I696b52265b9528082cd2524f05febe2338376488
Change-Id: Id1dfe8cf0ec50f1206dd997c9303756683ab5e00
1. What is the problem
A new patch [1] is merged in neutron, making unit tests fail.
2. What is the solution for the problem
Use runtime instead of neutorn_lib.
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
[1] I47ef642fcb3c8ded5eb7ed0a637033c7bcb3632b
Change-Id: I5a546d0538f35509fe1fc4d3197325d9f62bfc03
Commit I1d4ded9959c05c65b04b118b1c31b8e6db652e67 rehomed the
availability zone extension's API definition into neutron-lib and
I761381de0d6e26a0380386700e7921b824991669 will consume it in neutron.
This patch switches the relevant code over to use neutron-lib rather
then neutron.
Change-Id: I9e42623d3b3be4e9332ecd28fd63be583c0801ef
1. What is the problem
Trunk test has been disabled because of a neutron bug.
2. What is the solution for the problem
The neutron bug has been fixed, we need to reenable the test.
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
Change-Id: I8f4111a0cdf679da8ba79f4db7019d066a8545df
The policy-and-docs-in-code Queens goal outlines the work required
for projects to move policy into code and document the operations
and defaults.
This commit replaces occurrences of RuleDefault with
DocumentedRuleDefault where appropriate, which requires additional
attributes when used that supply more documentation in rendered
policy files.
Using DocumentedRuleDefault produces more descriptive generated
policy descriptons in 'configuration' section of tricircle docs.
Change-Id: I5be169e996066ff66d165731cf2bf12aaff38fd4
1. What is the problem
Smoke test tries to modify tempest config file but gets a
"permission deny" error.
2. What is the solution for the problem
Since we don't need tempest, we just remove the config.
Also temporarily skip trunk smoke test because of neutron
bug 1722967
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
Change-Id: I8489a797fbd3b584dc2b8556df5e50dd0b6133bd
1. What is the problem
Smoke test fails because openstack sdk fails to get authentication.
2. What is the solution to the problem?
Add domain information to the authentication parameters.
3. What the features need to be implemented to the Tricircle
to realize the solution?
N/A
Change-Id: I32f0f4c9608bdeec637f23962471f634617ec465
1. What is the problem
After the Pike release, systemd becomes the only runner for
services, also more services adopt the mod_wsgi way to start
their API server. As a result, our plugin.sh script and
document for cellv2 integration don't work now.
2. What is the solution for the problem
Update plugin.sh and document to adapt the changes.
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
Change-Id: I34843e1f765e8b0e64f68f0d89fe9e63106b60e4
1. What is the problem
The patch that refactors neutron ml2 config opts to be in
neutron/conf/plugins/ml2 is merged [1], making unit tests fail.
2. What is the solution for the problem
Delete the line which import neutron.plugins.ml2.config
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
Change-Id: Ia4c8de9ac0dc66541c194588a8c51a489078d909
1. What is the problem
OpenStack client will read "tags" field for network creation command,
but create_network in central plugin doesn't return this field.
2. What is the solution for the problem
Fill "tags" field in the returned body
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
Change-Id: I2537bcc9e61dc95a6cfb9e2853c8a2ea32310eb2
Closes-Bug: #1715103
1. What is the problem
Neutron community removes exceptions in neutron, and use
neutorn-lib's OVO exceptions instead [1].
2. What is the solution for the problem
Use neutron-lib's OVO exceptions.
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
[1] https://review.openstack.org/#/c/487959/
Change-Id: I8115f4f58aea97de24d70ca757125334098cb4f8
1. What is the problem
We lack detailed explaination about keystone url options auth_uri,
auth_url and identity_url. These options can easily make users confused.
2. What is the solution for the problem
Add some words to explain these options.
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
Change-Id: I1f3ddbbdc04287ad6f80ad98d36e3283bd8d101d
1. What is the problem
After the change of OpenStack document structure, some of our links in networking
guide are invalid.
2. What is the solution for the problem
Correct the link
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
Change-Id: I5ed943317d2136de374d7e3b900a62c2313bc0e4
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
