liusheng | zhenguo: awesome! | 00:57 |
---|---|---|
Kevin_Zheng | seems not the best time to send out nimble introduction email? | 01:16 |
Kevin_Zheng | most of developers are on vacation | 01:17 |
zhenguo | Kevin_Zheng: yes, and someone pointed out that Nimble is a company name | 01:46 |
zhenguo | liusheng: hah, all tests are green | 01:47 |
liusheng | zhenguo: so we need to rename ? | 01:56 |
zhenguo | liusheng: yes, but no rush | 01:57 |
zhenguo | liusheng: as someone already know nimble, we can change it later before the infra CI downtime window. | 01:58 |
liusheng | zhenguo: OK | 01:58 |
zhenguo | liusheng: do you have some suggestion about the new name? | 01:58 |
zhenguo | https://www.quora.com/Astronomy-Which-stars-have-the-highest-metallicities | 02:18 |
zhenguo | maybe we can choose a star name | 02:18 |
zhenguo | with rich metal | 02:18 |
liusheng | hah | 02:20 |
zhenguo | https://en.wikipedia.org/wiki/List_of_English_words_of_Chinese_origin | 02:23 |
zhenguo | or some chinese words | 02:23 |
zhenguo | how about longan? | 02:32 |
zhenguo | oh, longan is also a firm name | 02:37 |
liusheng | maybe a metal name is better :) | 02:38 |
zhenguo | liusheng: make sense | 02:43 |
liusheng | the most solid metal is chrome, lol | 02:43 |
zhenguo | liusheng: lol | 02:48 |
zhenguo | liusheng: how about choosing one from these http://www.chipsetc.com/valuable-metals-used-in-computers.html | 02:51 |
liusheng | zhenguo: does osmium available ? | 02:53 |
liusheng | zhenguo: seems it is also used | 02:53 |
zhenguo | liusheng: yes, it's used in pypi, https://pypi.python.org/pypi/osmium/2.10.2 | 02:55 |
openstackgerrit | Zhenguo Niu proposed openstack/nimble: Add availability zones API https://review.openstack.org/401997 | 04:06 |
openstackgerrit | Merged openstack/nimble: Update flake8 ignore list https://review.openstack.org/401823 | 04:28 |
*** RuiChen has quit IRC | 05:00 | |
openstackgerrit | Zhenguo Niu proposed openstack/nimble: Add availability zones API https://review.openstack.org/401997 | 05:08 |
openstackgerrit | liusheng proposed openstack/nimble: Remove the unused instance type projects table https://review.openstack.org/403321 | 06:37 |
zhenguo | liusheng: regarding instance type projects table, I plan to use it for specifying which tenants can use the type, wdyt? | 06:42 |
liusheng | zhenguo: can we add a column in instance_type table ? | 06:42 |
zhenguo | liusheng: in fact, it's copied from cinder volume type | 06:43 |
zhenguo | liusheng: you mean adding a projects column in types table? | 06:43 |
liusheng | zhenguo: hmm, you mean it is used for indicating which tenants to access the type ? | 06:46 |
zhenguo | liusheng: seems like that would not be indexable if we add all projects in a single column | 06:46 |
zhenguo | liusheng:yes | 06:46 |
liusheng | zhenguo: oh may I was wrong | 06:46 |
zhenguo | liusheng: we can copy all things from volume type, I think it's same with us | 06:46 |
liusheng | zhenguo: will the isntance_type have user_id and project_id attributes | 06:46 |
liusheng | ? | 06:47 |
zhenguo | liusheng: seems not needed | 06:47 |
liusheng | zhenguo: ok, got it | 06:47 |
liusheng | zhenguo: additionaly, I just want to chenge the uuid to be the primary key, what do you think ? | 06:49 |
liusheng | zhenguo: currently, the tables has an internal num as primary key | 06:50 |
liusheng | zhenguo: 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 |
zhenguo | liusheng: yes, and do you think we need to support specifying uuid when creating a type? | 06:52 |
liusheng | zhenguo: I don't think so | 06:52 |
zhenguo | liusheng: maybe you can help to refactor some parts of instance_type | 06:53 |
liusheng | zhenguo: yeah, I am glade to do :) | 06:53 |
liusheng | s/glade/glad/ | 06:54 |
zhenguo | liusheng: 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 uuid | 06:54 |
zhenguo | liusheng: their 'id' is same with our 'uuid' | 06:56 |
liusheng | zhenguo: yes, but the ID of cinder volume type is UUID | 06:56 |
zhenguo | liusheng: yes | 06:56 |
liusheng | zhenguo: so we don't need to support uuid in type creation, right ? | 06:56 |
zhenguo | liusheng: I think so, but not sure why they need this | 06:57 |
liusheng | zhenguo: I think the outher of these code also don't know why, lol | 06:59 |
zhenguo | liusheng: hah | 06:59 |
zhenguo | liusheng: yes, we can just remove it I think :P | 06:59 |
liusheng | zhenguo: OK, will do it | 06:59 |
zhenguo | liusheng: Thanks | 07:00 |
liusheng | zhenguo: and also, do you think we need a separated table to recode instance_type's extra_specs ? | 07:01 |
zhenguo | liusheng: seems yes, also it's better in indexable | 07:02 |
zhenguo | liusheng: seems all things in Nova are in separated tables. | 07:02 |
zhenguo | liusheng: I'm considering if we need to separate extra filed from instances as well :P | 07:03 |
liusheng | zhenguo: maybe it is reasonable, but I think it is a bit redundant to export separated APIs for extra_specs | 07:04 |
liusheng | zhenguo: :P | 07:04 |
zhenguo | liusheng: I also think it is :P | 07:04 |
liusheng | zhenguo: it is also copy from cinder :) | 07:07 |
zhenguo | liusheng: yes, all instance types things are volume types, hah | 07:08 |
zhenguo | liusheng: do you think we need to bump db migration version and API version if we need to update them currently | 07:09 |
zhenguo | liusheng: or after our first release? | 07:10 |
liusheng | zhenguo: maybe it is reasonable now | 07:11 |
zhenguo | liusheng: yes, but it's really tedious to maintain the versions | 07:12 |
zhenguo | liusheng: hah | 07:12 |
zhenguo | liusheng: maybe we can do some clean up for db and API before we use versions, wdyt? | 07:14 |
liusheng | zhenguo: cleanup for what ? | 07:14 |
zhenguo | liusheng: maybe there are some unneeded things | 07:15 |
zhenguo | liusheng: or maybe some absolutely issues | 07:15 |
liusheng | zhenguo: you mean we modify the table schemas in the initial version ? | 07:16 |
zhenguo | liusheng: hah, yes | 07:16 |
zhenguo | liusheng: we have modified the initial version many times, lol | 07:16 |
liusheng | zhenguo: yes, I think so | 07:16 |
liusheng | zhenguo: lol | 07:16 |
zhenguo | liusheng: I think the reason why we need to bump the db and api version is because someone maybe already deployed it | 07:17 |
liusheng | zhenguo: yes, but definitely there isn't :) | 07:18 |
zhenguo | liusheng: and this keeps old deployed env also works | 07:18 |
zhenguo | liusheng: yes | 07:18 |
liusheng | zhenguo: so lets modify the initial version | 07:18 |
zhenguo | liusheng: hah | 07:18 |
openstackgerrit | Zhenguo Niu proposed openstack/nimble: Add v1 API get method https://review.openstack.org/403332 | 08:17 |
zhenguo | liusheng: regarding availability zones, do you think we should use availability-zone or availabilityzones in the URL | 08:39 |
liusheng | zhenguo: or availability_zone ? | 08:46 |
liusheng | zhenguo: I am ok with your current sulution :) | 08:46 |
zhenguo | liusheng: I would like to change it to availabilityzones then we don't need _lookup | 08:47 |
liusheng | zhenguo: but availabilityzones seems is not very specifically | 08:50 |
zhenguo | liusheng: yes, Nova uses os-availability-zone | 08:50 |
liusheng | zhenguo: I am ok to use _lookup if it is easy to implement | 08:51 |
zhenguo | liusheng: ok, | 08:58 |
zhenguo | liusheng: maybe change it to availability_zones, as '-' is not allowable in a variable name , it's hard to use it | 09:36 |
openstackgerrit | Zhenguo Niu proposed openstack/nimble: Add availability zones API https://review.openstack.org/401997 | 10:05 |
liusheng | zhenguo: :(, the availability_zones is OK :P | 10:06 |
zhenguo | liusheng: ok, just updated | 10:07 |
openstackgerrit | Zhenguo Niu proposed openstack/nimble: Add v1 API get method https://review.openstack.org/403332 | 10:15 |
* zhenguo away | 10:15 | |
openstackgerrit | Merged openstack/nimble: Remove unneeded devstack gate hook script https://review.openstack.org/402168 | 10:44 |
*** kong_ has joined #openstack-nimble | 11:00 | |
openstackgerrit | Zhenguo Niu proposed openstack/nimble: Add v1 API get method https://review.openstack.org/403332 | 11:47 |
*** kong_ has quit IRC | 13:40 | |
*** kong_ has joined #openstack-nimble | 14:05 | |
*** kong_ has quit IRC | 17:00 | |
*** shaohe_feng has quit IRC | 17:37 | |
*** luyao has quit IRC | 17:38 | |
*** shaohe_feng has joined #openstack-nimble | 17:46 | |
*** luyao has joined #openstack-nimble | 17:51 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!