|
|
| (8 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| | == Questions and Answers in the Tricircle Big Tent project application == | | == Questions and Answers in the Tricircle Big Tent project application == |
| | | | |
| − | === How much of the API specifics need to be reimplemented in the Cinder / Nova APIGW components ? How much maintenance is needed there in case of changes in the bottom APIs ? ===
| + | Tricircle Big-Tent application has been accepted, all questions and answers could be found in the application patch: https://review.openstack.org/#/c/338796/ |
| − | | |
| − | For VM/Volume related API(like VM/Volum/Backup/Snapshot...), no need to be re-implemented in Cinder/Nova APIGW, for the Tricircle just forwards the request. For those APIs which manage common attributes like Cinder Volume Type, Nova Flavor,quota which are only some objects in the databases, need to be re-implemented.
| |
| − | The maintenance for the change in the bottom APIs is quite small. The Tricircle reuses tempest test cases for Nova/Cinder/Neutron to guarantee if there is change in the bottom APIs, and the change has impact on the implementation of the Tricircle, then the check/gate test for each patch submitted in the Tricircle will be failed, so that the contributor can correct the Tricircle in time.
| |
| − | In this patch, the check and gate test has just been added to the patches(https://review.openstack.org/#/c/339332/), more test cases will be opened to cover the features coming in the Tricircle.
| |
| − | | |
| − | === You're using an independent release model, which means you do not follow the OpenStack development cycles. Nova, Cinder, Neutron and Keystone follow a cycle-based release model. How does the Tricircle release map to supported releases in bottom instances ? How does it map to the supported Keystone/Neutron implementations running in the top Tricircle instance ? ===
| |
| − | | |
| − | | |
| − | | |
| − | === Is Tricircle planning to be gateway for every OpenStack project? ===
| |
| − | No, Nova, Cinder , Neutron only, at most +Glance + Ceilometer, No more
| |
| − | | |
| − | === How can we verify the API's exposed by Tricircle are indeed identical to the service's ? ===
| |
| − | Have explained in the commit meesage and comment many time: reuse the tempest test cases of these services to test tricircle
| |
| − | | |
| − | === How does this impact defcore? ===
| |
| − | If tempest can pass, then defcore pass
| |
| − | | |
| − | === What happens if a cloud exposes Tricircle instead of exposing, say, nova directly? ===
| |
| − | Adding more cross OpenStack scheduling and netwroking automation capabibility,
| |
