Recently the TC has worked on determining the criteria for when an
OpenStack project should be retired[1]. During Victoria cycle,
there was not a PTL nominee for the Triccirle project, that triggered
the TC to review the project health. In TC meeting it was decided to
retire the Tricircle project and was announced in the
openstack-discuss mailing[2].
This commit retires the repository as per process and if anyone would
like to maintain Tricircle again, please revert back this commit and propose
the re-adding of Tricircle to governance.
The community wishes to express our thanks and appreciation to all of
those who have contributed to the Tricircle project over the years.
[1] https://governance.openstack.org/tc/reference/dropping-projects.html
[2] http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014338.html
Depends-On: https://review.opendev.org/#/c/728903/
Needed-By: https://review.opendev.org/#/c/731566/
Change-Id: Ide73af8b7dbbadb49f5d6a6bd068d5d42f501cca
This ensures that options loaded during any prior run of the
application are dropped before being added again during init_application.
Change-Id: I7e4f230b5e824d4aa072a2a18d0989e670eda77a
Add file to the reno documentation build to show release notes for
stable/ussuri.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/ussuri.
Change-Id: I8f479ae98fa8ac7b312247beb96bd68f92539967
Sem-Ver: feature
Without this patch, the branch newton-eol will be used for release notes.
That branch contains a duplicated release note with wrong formatting,
which we don't want.
Change-Id: I31f816b07debc7e4856eefea9c8e8e41d8aa172c
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Fix problems found.
Remove hacking and friends from lower-constraints, they are not needed
for installation.
Change-Id: I02169e2f5bba669182d41a25bef1057306f74be8
1.What is the problem ?
1) Lack of installation doc for multi-region container management.
2.What is the solution for the problem?
1) Use zun component to provide container computation and use kuryr component to provide container network.In a word, make zun and kuryr compatible with tricircle.
Change-Id: I7dd2ee04409eb20f2e4ad1e919d13cda1f7775a5
Signed-off-by: XuShimin <948026069@qq.com>
Add file to the reno documentation build to show release notes for
stable/train.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/train.
Change-Id: I70306ba5c3b6c976317f41b360a4b6a4f629b082
Sem-Ver: feature
we have these in our specs, clear these here.
Change-Id: Ia7c0ed7fc94d21f16ee23763d51cf2431873b26d
Signed-off-by: song baisen <songbaisen@szzt.com.cn>
Co-Authored-By: tangzhuo <ztang@hnu.edu.cn>, zhiyuan_cai <luckyvega.g@gmail.com>
The api documentation is now changed.
Update all links that are changed to the
right location.
Change-Id: I5df2cc540ae53f7f94d88ad2da90209f08c6faf3
Signed-off-by: song baisen <songbaisen@szzt.com.cn>
Co-Authored-By: tangzhuo <ztang@hnu.edu.cn>, zhiyuan_cai <luckyvega.g@gmail.com>
the tox version we used are too old.
Change-Id: I661918c66aca69d9e99732d0f5910687e39b8787
Signed-off-by: song baisen <songbaisen@szzt.com.cn>
Co-Authored-By: tangzhuo <ztang@hnu.edu.cn>, zhiyuan_cai <luckyvega.g@gmail.com>
Neutron master submit https://review.opendev.org/#/c/660174/
while this result SecurityGroupRule can not pass bug
This patch is to avoid the problem
Change-Id: I1b6eeab827019a3ac3fc7373e6288cf4467a002a
signed-off-by: zhangchi <zhangchi@szzt.com.cn>
co-Authored-By: tangzhuo <ztang@hnu.edu.cn>
1. What is the problem ?
Lack of implementation of container management in multi-region scenario.
2. What is the solution for the problem ?
Write this spec to discribe how to implement the container management in the Tricircle multi-region scenario.
Change-Id: Iec0102656168e2d721cf2c0ec6d776e3aed881d6
Signed-off-by: XuShimin <948026069@qq.com>
some unit tests can not been passed as stein version neutron refreshed.
this patch is to fixed some problems about the loading
network_segment_ranges db error and reverse other related unit tests.
Change-Id: I55448c9313e890d36e58e25077e4e00945f96ca9
signed-off-by: zhangchi <zhangchi@szzt.com.cn>
co-Authored-By: tangzhuo <ztang@hnu.edu.cn>
Temporay remove some relate test errors, because we
need to merge some import pr. after we fix the error
in this pr
https://review.openstack.org/#/c/642636/
I will rebase them.
Co-Authored-By: tangzhuo <ztang@hnu.edu.cn>
Change-Id: I32824c5e71916ed2cba31ee7f9232e088796983c
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I9aea50df0ab39ac0798bd59b9185142847684f80
1.What is the problem ?
1) Lack of installation doc for lbass with nova cell v2.
2.What is the solution for the problem?
1) Integrate LBaaS with nova cell v2 in the tricircle environment and
write this doc for lbaas with nova cell v2 installation.
Change-Id: I08e2985a4deb3bc9a3773d6b6adfe49a870cff52
Signed-off-by: XuShimin <948026069@qq.com>
Ghanshyam Mann
OpenStack Release Bot