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
Tricircle does not support Service Function Chain
2. What is the solution to the problem
Add Service Function Chain support
3. What the features need to be implemented to the Tricircle
Add create, delete support
Change-Id: I4bbe169040c17d202410bb5a649aca4df8464c3c
1. What is the problem
Tricircle does not support VLAN aware VMs
2. What is the solution to the problem
Add VLAN aware VMs support
3. What the features need to be implemented to the Tricircle
Add VLAN aware VMs support
Implements: blueprint vlan-aware-vm-support
Change-Id: Ieed7ead2be3b152228fd11c454f2db1b640820c2
1. What is the problem
The documentation build does not generate any module index.
2. What is the solution to the problem
Remove the link to the page because documentation build does
not generate any module index.
3. What the features need to be implemented to the Tricircle
to realize the solution
None
Change-Id: I15cfd22f8fea85e80b5e021789ac2b43d7896151
1. What is the problem
Currently all networking scenarios were put in one page
http://docs.openstack.org/developer/tricircle/networking-guide.html.
This is inconvinent for readers to navigate the content of different
scenarios.
At the same time, the configuration of service_plugins is missing
in local Neutron installation configuration items.
2. What is the solution to the problem
Add one more level, to make each networking scenario being rendered
in different page. This adjustment will also lead to the title level
adjustment of installation-manual.
Add the service_plugins configuration item in
installation_manual.rst.
3. What the features need to be implemented to the Tricircle
No new features
Change-Id: I84a95abfea6aa023c8958d520c4fce028bd10e17
Signed-off-by: joehuang <joehuang@huawei.com>
1.What is the problem?
If end user or upstream developer wants to learn how to use
Tricircle after it was being deployed, there is no documentation
on how to create different networking topology.
2.What is the solution to the problem?
Documentations on networking guide are provided. Using CLI
commands to show how to create different networking topology.
3.What the features need to be implemented to the Tricircle
to realize the solution?
No new feature
Change-Id: Id87a562309467924460e8416aa1deaa22db7e29e
Signed-off-by: joehuang <joehuang@huawei.com>
1. What is the problem
Currently no configuration guide in the Tricircle.
2. What is the solution to the problem
This patch adds configuration guide for the Tricircle. Only the
configuration items of Tricircle will be described here. Logging,
messaging, database, keystonemiddleware etc configuration which are
generated from OpenStack OSLO libary, will not be described here.
3. What the features need to be implemented to the Tricircle
to realize the solution
None
Change-Id: I73c972c60ef43f8cca394af6a1b52cd5751a0f8b
Closes-Bug: #1652738
1.What is the problem?
All links in the README must be under openstack.org not github.com
or google.com
2.What is the solution to the problem?
We fix the README.rst and index.rst
3.What the features need to be implemented to the Tricircle
to realize the solution?
No new features.
Change-Id: I9f9e8f8334c93a11826d7fdf50d8c9fea86502a9
Closes-Bug: #1605188
1.What is the problem
An OpenStack project should be created based on the template
generated by cookiecutter: http://docs.openstack.org/infra/manual/creators.html#preparing-a-new-git-repository-using-cookiecutter
There are some files missing in the Tricircle compared to
the files generated by cookiecutter template.
2.What's need to be fixed:
This patch sets is to amend this missing files.
Moreover, README.md was renamed to README.rst, and the installation
part with devstack was moved to doc/source/installation.rst according
to the cookiecutter generated template. The README.rst in the
Tricircle root folder was updated accordingly, and only the description
of the Tricircle was remained.
3.What is the purpose of this patch set:
To make the Tricircle follow other OpenStack project folder structure
template which could be generated by cookiecutter to keep consistency.
Change-Id: I65d4c376a87eccded12bd3f08bcd9ee89def95d4
Signed-off-by: Chaoyi Huang <joehuang@huawei.com>
Change the gate to OpenStack infrastrcuture and update the README.md
to reflect the work on the stateless design proposal and branch.
BP: https://blueprints.launchpad.net/tricircle/+spec/new-design
Change-Id: I51accdf33d8d9e50774c16d7649975ca91c2f5ec
Signed-off-by: Chaoyi Huang <joehuang@huawei.com>
Dongfeng Huang
xiulin yin
avnish
joehuang
CR_hui