| *** jeromatron has quit IRC | 00:02 | |
| *** charlesw has joined #magnetodb | 00:33 | |
| *** charlesw_ has joined #magnetodb | 01:43 | |
| *** charlesw has quit IRC | 01:43 | |
| *** charlesw_ is now known as charlesw | 01:43 | |
| *** jeromatron has joined #magnetodb | 01:51 | |
| *** jeromatron has quit IRC | 02:13 | |
| *** openstackgerrit has quit IRC | 02:58 | |
| *** vivekd has joined #magnetodb | 03:50 | |
| *** charlesw has quit IRC | 04:01 | |
| *** jeromatron has joined #magnetodb | 04:29 | |
| *** jeromatron has quit IRC | 04:31 | |
| *** jeromatron has joined #magnetodb | 05:24 | |
| *** rushiagr_away is now known as rushiagr | 05:26 | |
| *** ajayaa has joined #magnetodb | 05:27 | |
| *** achuprin_ has quit IRC | 05:39 | |
| *** romainh has joined #magnetodb | 05:52 | |
| *** k4n0 has joined #magnetodb | 06:34 | |
| *** jeromatron has quit IRC | 06:37 | |
| *** k4n0 has quit IRC | 07:24 | |
| *** k4n0 has joined #magnetodb | 07:28 | |
| *** ajayaa has quit IRC | 07:36 | |
| *** ajayaa has joined #magnetodb | 07:57 | |
| *** vivekd2 has joined #magnetodb | 11:20 | |
| *** isviridov_away is now known as isviridov | 11:40 | |
| *** k4n0 has quit IRC | 11:42 | |
| *** vivekd3 has joined #magnetodb | 11:42 | |
| *** vivekd2 has quit IRC | 11:42 | |
| vivekd | hi isviridov | 11:55 |
|---|---|---|
| vivekd | i saw the blueprint filed by ajayaa https://blueprints.launchpad.net/magnetodb/+spec/table-uuid | 11:55 |
| vivekd | i'd a chat with him and i'd like to work on it. | 11:56 |
| vivekd | isviridov: can we go ahead and implement that or do we need to have some more discussions? | 11:56 |
| isviridov | vivekd, hello | 11:56 |
| vivekd | hello | 11:56 |
| isviridov | vivekd, great to see your initative here | 12:03 |
| vivekd | isviridov: thanks! | 12:03 |
| isviridov | Currently we don't have an agreement about table-uuid and how it will impact current API | 12:07 |
| isviridov | I think it needs more discussion before implementation. | 12:09 |
| vivekd | by impact in the current API u mean we may have to change MDB resource url to use uuid instead of table name? | 12:10 |
| ajayaa | isviridov, Would it hurt to just add an UUID field for a table and expose an api to get the project and table name given then UUID. | 12:12 |
| ajayaa | *and not change anything else | 12:12 |
| *** vivekd3 has quit IRC | 12:12 | |
| *** vivekd2 has joined #magnetodb | 12:13 | |
| ajayaa | I am just trying to create a unique identifier for a table which could safely be used by external systems like ceilometer. | 12:13 |
| isviridov | I've seen it in your spec. But why do you need project and table name by uuid? | 12:14 |
| ajayaa | isviridov, If I aggregate usage data in ceilometer then to present this data in a meaningful way to end-user, we would need to know above info. | 12:15 |
| ajayaa | For e.g. It does not make sense to say that you used X byte in resource_id <UUID> | 12:16 |
| isviridov | vivekd, yes, also other's API calls | 12:16 |
| ajayaa | isviridov, For now I am just proposing to add a single api without bringing change in any other api. | 12:17 |
| isviridov | ajayaa, yes, and it looks like half baked solution now. | 12:18 |
| ajayaa | isviridov, If we decide to make all our api openstack style, it is half-baked. | 12:18 |
| isviridov | ajayaa, in current form it looks like better to leave projectid_tablename as identifier | 12:19 |
| isviridov | ajayaa, I agree | 12:20 |
| isviridov | ajayaa, but API is always thing to disput. It won't be easy just to add something | 12:24 |
| vivekd | isviridov: but still how will we solve the problem of a table deleted and recreated with same name in same project? | 12:24 |
| isviridov | vivekd, it will not | 12:24 |
| isviridov | vivekd, that is why I wan't to have uuid. We are just figuring out how to do it better | 12:25 |
| isviridov | *want | 12:26 |
| ajayaa | isviridov, +1. While proposing this spec, I was not aware that we have plans to make our apis openstack-style. | 12:26 |
| vivekd | isviridov: do u mean that the spec to add a table uuid should also have a proposal to change all our APIs openstack style? | 12:28 |
| vivekd | for the sake of completion | 12:29 |
| isviridov | ajayaa, in some way it will be opensyack-style | 12:30 |
| *** vivekd3 has joined #magnetodb | 12:31 | |
| *** vivekd2 has quit IRC | 12:31 | |
| isviridov | vivekd, not sure about it. Current API is used already. So, the changes should be not very critical, but consistent with other parts | 12:32 |
| isviridov | vivekd, anyhow it is v1 now, huge changes are possible only in next version only | 12:33 |
| *** ajayaa has quit IRC | 12:33 | |
| *** vivekd has quit IRC | 12:35 | |
| *** vivekd has joined #magnetodb | 12:37 | |
| *** vivekd3 has quit IRC | 12:37 | |
| *** vivekd2 has joined #magnetodb | 12:39 | |
| *** vivekd3 has joined #magnetodb | 12:41 | |
| *** vivekd2 has quit IRC | 12:41 | |
| *** vivekd has quit IRC | 12:42 | |
| *** vivekd3 has quit IRC | 12:46 | |
| *** rushiagr is now known as rushiagr_away | 12:55 | |
| *** romainh has left #magnetodb | 13:21 | |
| *** romainh has joined #magnetodb | 13:22 | |
| *** charlesw has joined #magnetodb | 13:32 | |
| *** rushiagr_away is now known as rushiagr | 13:44 | |
| *** openstackgerrit has joined #magnetodb | 14:17 | |
| openstackgerrit | A change was merged to stackforge/magnetodb: Code cleanup https://review.openstack.org/127442 | 14:38 |
| *** romainh has left #magnetodb | 16:15 | |
| *** jeromatron has joined #magnetodb | 16:25 | |
| *** jeromatron has quit IRC | 17:43 | |
| *** jeromatron has joined #magnetodb | 17:43 | |
| *** jeromatron has quit IRC | 18:04 | |
| *** openstackgerrit has quit IRC | 18:48 | |
| *** openstackgerrit has joined #magnetodb | 18:55 | |
| *** rushiagr is now known as rushiagr_away | 19:18 | |
| *** jeromatron has joined #magnetodb | 19:23 | |
| *** jeromatron has quit IRC | 21:55 | |
| *** jeromatron has joined #magnetodb | 21:55 | |
| *** charlesw has quit IRC | 21:57 | |
| *** jeromatron has quit IRC | 22:46 | |
| *** openstackgerrit has quit IRC | 22:54 | |
| *** jeromatron has joined #magnetodb | 23:03 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!