Use openstack-tox-cover template, this runs the cover job as
non-voting in the check queue only.
Remove jobs and use template instead.
Change-Id: I347ba793764073f46731a8953030976188e1a1c4
see the below unit test error
neutron.common.exceptions.QoSRulesConflict:
Rule bandwidth_limit conflicts with rule
a7c31561-6918-4ab3-b72e-daf49aabf0de which
already exists in QoS Policy
4580b79c-f44c-4fa0-9321-105e4cc7fde9.
Signed-off-by: song baisen <songbaisen@szzt.com.cn>
Co-Authored-By: tangzhuo <ztang@hnu.edu.cn>, zhiyuan_cai <luckyvega.g@gmail.com>
Change-Id: Ib0244e5d6ce7e53a5274a541f990a29b972bdf37
1. What is the problem?
Now we use the restapi cmd to run ci.
2. What is the solution to the problem?
Change the restapi cmd to openstack api
3. What the features to be implemented in the Tricircle to realize the solution?
No
Signed-off-by: song baisen <songbaisen@szzt.com.cn>
Change-Id: Id591dc4795a4c543dd86ce75644c9f8806500339
Co-Authored-By: tangzhuo <ztang@hnu.edu.cn>, zhiyuan_cai <luckyvega.g@gmail.com>
This is a mechanically generated patch to switch the documentation
jobs to use the new PTI versions of the jobs as part of the
python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I1d4af86ab9245f6b42b456ed0994bba7da0fe19d
Story: #2002586
Task: #24340
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I87a1a0c27cfed6b517552d0428eab5de61fa8b4a
Story: #2002586
Task: #24340
1. What is the problem
In the current l3 networking model, the host route will be only valid
after DHCP lease time expired, and renewed.
2. What is the solution for the problem
To overcome the drawbacks, a new l3 netowrking model is introduced in
this spec.
3. What features need to be implemented to the Tricircle to
realize the solution
N/A
Change-Id: I963253e9ce325f4a94cfb69d482404dc2c12f34e
1. What is the problem?
Caused the policy to fail When use 'admin' role to create pod,
Error response is "Unauthorized to create pods".
2. What is the solution to the problem?
In context, the 'HTTP_X_ROLE' maybe include mutilple role, so use
'admin' in environ.get('HTTP_X_ROLE') to judge rather than equality.
Change-Id: If0a765603e56e0325a31f7a3e0202f52fd1cbe38
1. What is the problem?
in nova cell with tricircle, instances can not be create and delete sucessful
2. What is the solution to the problem?
fix the error in creaton and deletion of tricircle
3. What the features to be implemented in the Tricircle to realize the solution?
no
<Co-Authored-By: tangzhuo <ztang@hnu.edu.cn>>
Change-Id: If1ffdb245f0c03e11d0273b5e238c93c3f23bc8b
1. What is the problem?
the unit test can not pass.
2. What is the solution to the problem?
add the segmentation_id to the subnet.
3. What the features to be implemented in the Tricircle to realize the solution?
no
Signed-off-by: song baisen <songbaisen@szzt.com.cn>
Change-Id: I023a46af393b94cc3c4f2ec9f5636e740fa12224
Co-Authored-By: tangzhuo <ztang@hnu.edu.cn>, zhiyuan_cai <luckyvega.g@gmail.com>
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because of that
breaks the more specific versions used in default environments like
py35 and py36.
Depends-On: https://review.openstack.org/#/c/573012/
Change-Id: I71a6231832fc191633b15904246902a21f8a8130
1. What is the problem?
the unit test can not pass.
2. What is the solution to the problem?
after the devstac run export the OS_PASSWORD as
define in the devstack.
3. What the features to be implemented in the Tricircle to realize the solution?
I compare the faild and before passed local.conf they are all the same. so
it is look like a bug of devstack. later on I will pull a bug for this in
devstack bug list.wait on devstack to fix this bug.
Signed-off-by: song baisen <songbaisen@szzt.com.cn>
Co-Authored-By: tangzhuo <ztang@hnu.edu.cn>, zhiyuan_cai <luckyvega.g@gmail.com>
Change-Id: I0c004ca3a7f31159372ff69d6e7ea0dcede0e66a
pep8/flake8 complains under python 3 about the windows line endings in
these files. This change should merely change the line endings to use
the unix standard of \n instead of the windows standard of \r\n.
Change-Id: I5f4722b89964558b46cab3a3a6368d8b6c1f7c4a
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
1. What is the problem?
Keystone in Openstack devstack Master changed api for endpoint creation
while tricircle plugin present remains the old way
2. What is the solution to the problem?
change the service create to "openstack endpoint create name type"
3. What features need to be implemented to the Tricircle
to realize the solution?
installation for tricircle
Change-Id: Ic212f909cd27be232cae38b845f6d5e66dec998b
1. What is the problem
Tricircle does not support update for Service Function Chain
Smoke test failed
2. What is the solution to the problem
Add Service Function Chain update support
There are some problems with networking-sfc and fixed it
3. What the features need to be implemented to the Tricircle
None
Signed-off-by: chenyaguang <chenyaguang@szzt.com.cn>
Co-Authored-By:tangzhuo <ztang@hnu.edu.cn>, yinxiulin <yinxiulin@huawei.com>
Change-Id: I407cb21c298a433bd12b2032b2af28ca7ebb68f0
1. What is the problem?
In a non-local network, delete a vm from one reigon, and use its port to
create a vm in another region, the port in the original region is not
released.
2. What is the solution to the problem?
Release port to down when delete a vm from one region, and change shadow
port 'name' and 'device_id' and 'device_owner' value if shadow port exist.
In the update port, according to the update before the port and the
updated port to determine whether to notify the Central updates.
3. What the features to be implemented in the Tricircle to realize the solution?
Because port be cached in neutron-openvswitch-agent, not delete port
when delete a vm from one region.
Signed-off-by: zhang xiaohan <zhangxiaohan@szzt.com.cn>
Co-Authored-By: tangzhuo <ztang@hnu.edu.cn>
Change-Id: If6819bf67ea2d206cc735039d8c55733dae54ee9
To access neutron objects we're moving to a dynamic plugin approach as
shown in the depends on and related patches.
This patch removes the imports of neutron.objects and uses neutron-lib
to load them instead. The remaining base object import will be addressed
later.
It also bumps neutron-lib up to 1.14.0.
Change-Id: Ia0904a2c97749fb13604a44fee3c96c40588e0b2
Depends-On: https://review.openstack.org/#/c/570060/
According to [1], "auth_uri" has been deprecated.
This patch replace it by using "www_authenticate_uri" instead.
[1] https://review.openstack.org/#/c/508522
Change-Id: Ie87e1d4a202f30265c3a46037e20db9082292ca2
1. What is the problem?
The oslo.config support a 'mutable' parameter to Opts.
This is only respected when the new method mutate_config_files
is called instead of reload_config_files.so we need to enable
mutable config in tricircle.
2. What is the solution to the problem?
Depend on the two path in oslo.config which are
Icec3e664f3fe72614e373b2938e8dee53cf8bc5e and
I1e7a69de169cc85f4c09954b2f46ce2da7106d90 made the Tricircle
have the ability to mutable config.
3. What the features to be implemented in the Tricircle to realize the solution?
Further patches will be needed to make select config options be marked as
mutable. This change enables support for oslo provided config options
to be updated via SIGHUP such as log level.
Signed-off-by: song baisen <songbaisen@szzt.com.cn>
Co-Authored-By: tangzhuo <ztang@hnu.edu.cn>, zhiyuan_cai <luckyvega.g@gmail.com>
Change-Id: I7b42bfb75913190fa4bd0d892e72fec8f629d7a6
1. What is the problem?
A security group(sg) may map to several local sg in local neutron.
During the deletion of sg local neutron may recreate the sg if it
recieve a get-request of sg.
2. What is the solution to the problem?
The solution to resource deleting is covered in
specs/queens/resource deleting.rst
3. What the features to be implemented in the Tricircle to realize the solution?
No new features.
Change-Id: I37feacf93b1bde1459bfd8513c7860fe77c113a7