| *** Yipei has joined #openstack-tricircle | 00:52 | |
| *** joehuang has joined #openstack-tricircle | 01:00 | |
| *** RongHui11 has joined #openstack-tricircle | 01:08 | |
| *** RongHui11 has quit IRC | 02:13 | |
| *** sapd_ has joined #openstack-tricircle | 02:45 | |
| joehuang | hello, sapd? | 06:13 |
|---|---|---|
| sapd_ | Hi joehuang | 06:15 |
| *** sapd_ has quit IRC | 06:15 | |
| joehuang | hi sapd, for trio2o, I have some idea to make it better, but we didn't do that yet | 06:15 |
| joehuang | I saw sapd_ leaving, are you still online? | 06:16 |
| sapd | yes. I'm still online | 06:16 |
| sapd | Can you share me your idea? | 06:16 |
| joehuang | ok | 06:18 |
| joehuang | As you know, currently Trio2o implement lots of tables which are duplicated with Nova/Cinder, and has to write API code to write these tables | 06:19 |
| sapd | Yes. | 06:20 |
| joehuang | This is not good, you have to implement flavor, volume type server group etc code | 06:20 |
| joehuang | and because these tables may be updated in each release, so the code in Trio2o has to be updated to make the API compatible too | 06:21 |
| joehuang | The idea is to simplify Trio2o as pure API redirection gateway | 06:22 |
| joehuang | the first idea is to specify one of OpenStack instance as these metadata proxy, all flavor/volumetype etc operation will be redirected to this OpenStack instance | 06:23 |
| joehuang | trio2o only forward the request to this openstack instance | 06:23 |
| joehuang | and no need to maintain API | 06:23 |
| joehuang | and in Trio2o, mapping and sync the flavor volume type to other openstack instance could be done | 06:24 |
| joehuang | The second idea is to install only Nova/Cinder API+ DB at the side of Trio2o | 06:25 |
| joehuang | for the metadata CRUD like flavor, volumetype, server group etc, will be forwarded to the Nova/Cinder API+ DB | 06:26 |
| joehuang | through both of these two method, we can keep consistency of flavor, volumetype, server group etc table definition and API processing | 06:27 |
| joehuang | Trio2o can focus its function on API redirection and openstack instance scheduling, but not to duplicate the code implementation | 06:28 |
| joehuang | sapd, am I clear? | 06:28 |
| sapd | yeah, I just take a rest. | 07:11 |
| sapd | joehuang, I think two method is possible to perform. | 07:12 |
| sapd | So, We will install nova/cinder - api at the central, every request are related to flavor/keypair/volume type we will redirect to these API, | 07:14 |
| joehuang | yes | 07:15 |
| sapd | But In nova local, We have to install nova-api it self. | 07:15 |
| sapd | When launch instance, They will call to this api, But it does not have these resource. | 07:16 |
| joehuang | then you can create resource mapping in Trio2o admin API, to sync flavor/volume type etc resource to regarding OpenStack instance | 07:18 |
| joehuang | because flavor, volumetype etc resource are not created frequently | 07:19 |
| joehuang | and most of them are managed by the admin | 07:19 |
| joehuang | so when adding new flavor, you can specify the flavor will be presented in which open stack instance | 07:20 |
| joehuang | and then sync and create regarding mapping relationship | 07:20 |
| joehuang | if no mapping releationship, that means the openstack instance doesn't support this flavor | 07:21 |
| sapd | We have talked about this idea before :D | 07:21 |
| sapd | The design is same to tricircle | 07:21 |
| joehuang | good! | 07:22 |
| sapd | The server already has resource mapppings. | 07:22 |
| sapd | s/mapppings/mappings | 07:22 |
| sapd | We can do it for flavor/keypair | 07:23 |
| *** sapd has left #openstack-tricircle | 07:23 | |
| *** sapd has joined #openstack-tricircle | 07:23 | |
| sapd | The difference is we don't have to implement tables for keypair/flavor, these resource will be save on nova-api / cinder-api DB at central | 07:24 |
| joehuang | yes, maintain the duplicated code is painful | 07:25 |
| sapd | But this design will have some issues about performance, We have to perform many requests. | 07:26 |
| joehuang | The performance impact is quite minor | 07:29 |
| joehuang | just one more http calling | 07:30 |
| joehuang | if not https used between Trio2o and "nova-api / cinder-api DB at central"(They are internal service, no need to expose to external world), the cost is < 20 ms | 07:32 |
| joehuang | human insensitive | 07:32 |
| joehuang | the cost is human insensitive | 07:33 |
| joehuang | you can test and verify it. | 07:34 |
| joehuang | I have to leave for a while, sapd, please send me mail if you have more comment | 07:42 |
| sapd | yes. I will try with flavor first, But recently I quite busy in my company. | 07:45 |
| *** joehuang has quit IRC | 07:47 | |
| *** dims has quit IRC | 09:28 | |
| *** dims has joined #openstack-tricircle | 09:58 | |
| *** Yipei has quit IRC | 13:06 | |
| *** catintheroof has joined #openstack-tricircle | 13:15 | |
| *** dims has quit IRC | 17:14 | |
| *** dims has joined #openstack-tricircle | 17:18 | |
| *** dims has quit IRC | 19:28 | |
| *** catintheroof has quit IRC | 19:28 | |
| *** dims has joined #openstack-tricircle | 19:31 | |
| *** catintheroof has joined #openstack-tricircle | 20:29 | |
| *** sapd has quit IRC | 21:26 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!