Saturday, 2016-11-26

liushengzhenguo: awesome!00:57
Kevin_Zhengseems not the best time to send out nimble introduction email?01:16
Kevin_Zhengmost of developers are on vacation01:17
zhenguoKevin_Zheng: yes, and someone pointed out that Nimble is a company name01:46
zhenguoliusheng: hah, all tests are green01:47
liushengzhenguo: so we need to rename ?01:56
zhenguoliusheng: yes, but no rush01:57
zhenguoliusheng: as someone already know nimble, we can change it later before the infra CI downtime window.01:58
liushengzhenguo: OK01:58
zhenguoliusheng: do you have some suggestion about the new name?01:58
zhenguohttps://www.quora.com/Astronomy-Which-stars-have-the-highest-metallicities02:18
zhenguomaybe we can choose a star name02:18
zhenguowith rich metal02:18
liushenghah02:20
zhenguohttps://en.wikipedia.org/wiki/List_of_English_words_of_Chinese_origin02:23
zhenguoor some chinese words02:23
zhenguohow about longan?02:32
zhenguooh, longan is also a firm name02:37
liushengmaybe a metal name is better :)02:38
zhenguoliusheng: make sense02:43
liushengthe most solid metal is chrome, lol02:43
zhenguoliusheng: lol02:48
zhenguoliusheng: how about choosing one from these http://www.chipsetc.com/valuable-metals-used-in-computers.html02:51
liushengzhenguo: does osmium available ?02:53
liushengzhenguo: seems it is also used02:53
zhenguoliusheng: yes, it's used in pypi, https://pypi.python.org/pypi/osmium/2.10.202:55
openstackgerritZhenguo Niu proposed openstack/nimble: Add availability zones API  https://review.openstack.org/40199704:06
openstackgerritMerged openstack/nimble: Update flake8 ignore list  https://review.openstack.org/40182304:28
*** RuiChen has quit IRC05:00
openstackgerritZhenguo Niu proposed openstack/nimble: Add availability zones API  https://review.openstack.org/40199705:08
openstackgerritliusheng proposed openstack/nimble: Remove the unused instance type projects table  https://review.openstack.org/40332106:37
zhenguoliusheng: regarding instance type projects table, I plan to use it for specifying which tenants can use the type, wdyt?06:42
liushengzhenguo: can we add a column in instance_type table ?06:42
zhenguoliusheng: in fact, it's copied from cinder volume type06:43
zhenguoliusheng: you mean adding a projects column in types table?06:43
liushengzhenguo: hmm, you mean it is used for indicating which tenants to access the type ?06:46
zhenguoliusheng: seems like that would not be indexable if we add all projects in a single column06:46
zhenguoliusheng:yes06:46
liushengzhenguo: oh may I was wrong06:46
zhenguoliusheng: we can copy all things from volume type, I think it's same with us06:46
liushengzhenguo: will the isntance_type have user_id and project_id attributes06:46
liusheng?06:47
zhenguoliusheng: seems not needed06:47
liushengzhenguo: ok, got it06:47
liushengzhenguo: additionaly, I just want to chenge the uuid to be the primary key, what do you think ?06:49
liushengzhenguo: currently, the tables has an internal num as primary key06:50
liushengzhenguo: I have found a problem, since it allow specifying uuid when creating a type, I can specifying duplicated uuid to create two types, and the name cannot be duplicated. it is strange!06:51
zhenguoliusheng: yes, and do you think we need to support specifying uuid when creating a type?06:52
liushengzhenguo: I don't think so06:52
zhenguoliusheng: maybe you can help to refactor some parts of instance_type06:53
liushengzhenguo: yeah, I am glade to do :)06:53
liushengs/glade/glad/06:54
zhenguoliusheng: you can refer to volume type including db, objects and API, and I find in volume type db they just use id column, but we have both id and uuid06:54
zhenguoliusheng: their 'id' is same with our 'uuid'06:56
liushengzhenguo: yes, but the ID of cinder volume type is UUID06:56
zhenguoliusheng: yes06:56
liushengzhenguo: so we don't need to support uuid in type creation, right ?06:56
zhenguoliusheng: I think so, but not sure why they need this06:57
liushengzhenguo: I think the outher of these code also don't know why, lol06:59
zhenguoliusheng: hah06:59
zhenguoliusheng: yes, we can just remove it I think :P06:59
liushengzhenguo: OK, will do it06:59
zhenguoliusheng: Thanks07:00
liushengzhenguo: and also, do you think we need a separated table to recode instance_type's extra_specs ?07:01
zhenguoliusheng: seems yes, also it's better in indexable07:02
zhenguoliusheng: seems all things in Nova are in separated tables.07:02
zhenguoliusheng: I'm considering if we need to separate extra filed from instances as well :P07:03
liushengzhenguo: maybe it is reasonable, but I think it is a bit redundant to export separated APIs for extra_specs07:04
liushengzhenguo: :P07:04
zhenguoliusheng: I also think it is :P07:04
liushengzhenguo: it is also copy from cinder :)07:07
zhenguoliusheng: yes, all instance types things are volume types, hah07:08
zhenguoliusheng: do you think we need to bump db migration version and API version if we need to update them currently07:09
zhenguoliusheng: or after our first release?07:10
liushengzhenguo: maybe it is reasonable now07:11
zhenguoliusheng: yes, but it's really tedious to maintain the versions07:12
zhenguoliusheng: hah07:12
zhenguoliusheng: maybe we can do some clean up for db and API before we use versions, wdyt?07:14
liushengzhenguo: cleanup for what ?07:14
zhenguoliusheng: maybe there are some unneeded things07:15
zhenguoliusheng: or maybe some absolutely issues07:15
liushengzhenguo: you mean we modify the table schemas in the initial version ?07:16
zhenguoliusheng: hah, yes07:16
zhenguoliusheng: we have modified the initial version many times, lol07:16
liushengzhenguo: yes, I think so07:16
liushengzhenguo: lol07:16
zhenguoliusheng: I think the reason why we need to bump the db and api version is because someone maybe already deployed it07:17
liushengzhenguo: yes, but definitely there isn't :)07:18
zhenguoliusheng: and this keeps old deployed env also works07:18
zhenguoliusheng: yes07:18
liushengzhenguo: so lets modify the initial version07:18
zhenguoliusheng: hah07:18
openstackgerritZhenguo Niu proposed openstack/nimble: Add v1 API get method  https://review.openstack.org/40333208:17
zhenguoliusheng: regarding availability zones, do you think we should use availability-zone or availabilityzones in the URL08:39
liushengzhenguo: or availability_zone ?08:46
liushengzhenguo: I am ok with your current sulution :)08:46
zhenguoliusheng: I would like to change it to availabilityzones then we don't need _lookup08:47
liushengzhenguo: but availabilityzones seems is not very specifically08:50
zhenguoliusheng: yes, Nova uses os-availability-zone08:50
liushengzhenguo: I am ok to use _lookup if it is easy to implement08:51
zhenguoliusheng: ok,08:58
zhenguoliusheng: maybe change it to availability_zones, as '-' is not allowable in a variable name , it's hard to use it09:36
openstackgerritZhenguo Niu proposed openstack/nimble: Add availability zones API  https://review.openstack.org/40199710:05
liushengzhenguo: :(,   the availability_zones is OK :P10:06
zhenguoliusheng: ok, just updated10:07
openstackgerritZhenguo Niu proposed openstack/nimble: Add v1 API get method  https://review.openstack.org/40333210:15
* zhenguo away10:15
openstackgerritMerged openstack/nimble: Remove unneeded devstack gate hook script  https://review.openstack.org/40216810:44
*** kong_ has joined #openstack-nimble11:00
openstackgerritZhenguo Niu proposed openstack/nimble: Add v1 API get method  https://review.openstack.org/40333211:47
*** kong_ has quit IRC13:40
*** kong_ has joined #openstack-nimble14:05
*** kong_ has quit IRC17:00
*** shaohe_feng has quit IRC17:37
*** luyao has quit IRC17:38
*** shaohe_feng has joined #openstack-nimble17:46
*** luyao has joined #openstack-nimble17:51

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!