| *** tricircle has joined #openstack-tricircle | 00:07 | |
| tricircle | hello morning | 00:08 |
|---|---|---|
| *** tricircle is now known as joehuang | 00:08 | |
| joehuang | hello, morning | 00:08 |
| ronghui | morning | 00:26 |
| joehuang | hello, consider that TCs are worried about that Tricircle will leads different in OpenStack API, I have one idea | 00:49 |
| joehuang | One proposal to remove the worries and maintain single version of Nova/Cinder/Neutron API: provide plugin mechanism in Nova/Cinder API layer like what did in Neutron. Then no Nova API-GW/Cinder API-GW needs to be developed in Tricircle, just develope Tricricle Nova Plugin, Tricircle Cinder Plugin and Tricircle Neutron Plugin, and only single version of Nova/Cinedr/Neutron API will be | 00:49 |
| joehuang | developed, tested and maintained in Nova/Cinder/Neutron team. How do you think about this proposal? | 00:49 |
| joehuang | But this proposal will take at least one cycle to be introduced in Nova/Cinder | 00:51 |
| ronghui | ok | 00:55 |
| ronghui | i have no problem | 00:55 |
| ronghui | and i will discuss it with our team | 00:55 |
| joehuang | TCs also hope we continue our development, and at the same time discuss that in the architecture working group to get broad consensus | 00:56 |
| joehuang | this is only one proposal(plugin mechanism)to get consensus on the single API | 00:56 |
| joehuang | our development should not be impacted by the proposal before any consensus can be achieved | 00:57 |
| *** ronghui has quit IRC | 01:02 | |
| *** ronghui has joined #openstack-tricircle | 01:14 | |
| shinobu_ | i'm not completely clear about what "single api" means? the tricircle does not build any api for each component. the tricircle only makes use of api developped under each component, does it? | 02:09 |
| joehuang | yes | 02:11 |
| joehuang | but TCs still worried that Tricircle will touch and change the API | 02:11 |
| shinobu_ | no | 02:11 |
| shinobu_ | we will touch nothing | 02:11 |
| joehuang | I have explained many times that we use tempest to guarantee the API will not be changed | 02:12 |
| shinobu_ | we just will refer to each api. | 02:12 |
| shinobu_ | i must be honest here | 02:12 |
| joehuang | http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-07-26-20.02.log.html from 20:27:31 | 02:13 |
| shinobu_ | we do not touch, modified nothing, even any record in each component. | 02:13 |
| joehuang | the meeting logs of the last TC weekly meetnig | 02:13 |
| joehuang | 20:32:32 <dhellmann> | 02:14 |
| joehuang | 20:32:32 <dhellmann> joehuang : we are working very hard to establish a single openstack API even among the existing projects so that we can have deployment interoperability. Tricircle is a proxy layer on top of that with subtle differences, which means it is yet another API. That dilutes the mission. | 02:14 |
| shinobu_ | if that's true, no component should have api, shouldn't it? | 02:17 |
| shinobu_ | nova makes use of cinder api, for instance | 02:17 |
| shinobu_ | nova should not have api? | 02:17 |
| shinobu_ | that's not true. | 02:17 |
| joehuang | good reason :) | 02:18 |
| joehuang | so Sean said: 20:29:36 <sdague> I'm super not thrilled by the proxy API nature of this... especially as we've been deprecating the API proxies in Nova over this cycle | 02:18 |
| joehuang | They are deprecating the API proxies in Nova, for example Image-list, etc | 02:19 |
| joehuang | Most of APIs are forwarded to the bottom, there are little duplication implemention of APIs like Nova Flavor/Cinde VolumeType, which are not proxied to the bottom OpenStack directly, for they are some global objects. | 02:22 |
| shinobu_ | if there are any duplication in the tricircle, we should fix it out. otherwise, if anything happen, nobody know, decide, hey you're wrong. | 02:25 |
| joehuang | Already answered in the comment to Thierry in the https://review.openstack.org/#/c/338796/ | 02:27 |
| shinobu_ | if it's really really difficult to remove those kind of duplications regarding realize any feature in the tricircle, we might give up those kind of feature. | 02:27 |
| shinobu_ | but even it's not true and fair enough, if everyone is happy with their proposal, i would be able to agree with team decision democratically. | 02:34 |
| joehuang | Monty(one of TC) will help us to move forwad, waiting for his proposal. | 02:35 |
| joehuang | Flavor and VolumeType are some common attributes, there are should be a place to manage these attributes for multiple OpenStack instances | 02:39 |
| joehuang | That's why we re-implemented in Tricircle | 02:39 |
| *** joehuang has quit IRC | 04:47 | |
| *** ronghui has quit IRC | 05:02 | |
| *** ronghui has joined #openstack-tricircle | 05:14 | |
| *** saggi has joined #openstack-tricircle | 05:36 | |
| *** saggi has quit IRC | 05:38 | |
| *** joehuang has joined #openstack-tricircle | 06:13 | |
| *** gongysh has joined #openstack-tricircle | 06:42 | |
| *** shinobu_ has quit IRC | 07:51 | |
| *** gongysh has quit IRC | 07:53 | |
| *** gongysh has joined #openstack-tricircle | 08:50 | |
| *** ronghui has quit IRC | 09:01 | |
| *** ronghui has joined #openstack-tricircle | 09:14 | |
| *** joehuang has quit IRC | 09:52 | |
| *** gongysh has quit IRC | 10:18 | |
| ronghui | ` | 11:10 |
| *** ronghui has quit IRC | 13:02 | |
| *** ronghui has joined #openstack-tricircle | 13:14 | |
| *** ronghui has quit IRC | 17:01 | |
| *** ronghui has joined #openstack-tricircle | 17:15 | |
| *** ronghui has quit IRC | 21:01 | |
| *** ronghui has joined #openstack-tricircle | 21:13 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!