Wednesday, 2016-11-16

*** luyao has joined #openstack-nimble01:23
*** yuntongjin has joined #openstack-nimble01:29
*** yuntongjin has quit IRC01:30
*** RuiChen has joined #openstack-nimble02:02
*** luyao has quit IRC02:13
openstackgerritliusheng proposed openstack/nimble: Add instance CURD related functional tests  https://review.openstack.org/39806803:46
*** luyao has joined #openstack-nimble04:04
zhenguoliusheng, shaohe_feng: I think the current functional tests should be moved to unit tests, wdyt? we can find another way for functional testing, maybe use nimbleclient04:27
zhenguoliusheng, shaohe_feng: FYI http://specs.openstack.org/openstack/keystone-specs/specs/kilo/functional-testing.html04:35
zhenguoliusheng, shaohe_feng: I find nova use gate-nova-tox-db-functional-ubuntu-xenial which doesn't require a dsvm04:51
*** luyao has quit IRC04:58
shaohe_fengzhenguo: I'm here04:58
zhenguoshaohe_feng: hi05:03
zhenguoshaohe_feng: nova functional tests doesn't rely on devstack env, and ironic doesn't have a functional test in gate05:04
zhenguoshaohe_feng: we setup a dsvm and hook script there, but in fact our functional tests now doesn't need devstack env at all @liusheng05:05
shaohe_fengzhenguo:  I have see your meesage. Yes, now our functional test use pecan.testing. It does not start a http server.05:07
shaohe_fengzhenguo: I think it is more like integration testing.05:07
shaohe_fengzhenguo: but in Openstack, seems only two type test, unit and functional05:08
zhenguoshaohe_feng:  yes, nova's functional tests is integration tests as well,05:08
shaohe_fengzhenguo: So I think the devstack is the real functional test.05:08
zhenguoshaohe_feng: nova moved integration tests to functional tests https://review.openstack.org/#/c/136772/05:09
zhenguoshoahe_feng: but the main project like nova, doesn't need devstack env, and ironic doesn't have functional tests05:09
shaohe_fengzhenguo: yes. I have see the patch. Nova  distinguished integration and functional tests in the beginnig05:14
shaohe_fengzhenguo: and then they remove the integration test. The patch not tell us the reason, but IMHO, it is more conveniece for code maangement.05:16
zhenguoshaohe_feng: yes, so currently we follow nova's way05:16
zhenguoshaohe_feng: we use pecan.testing which need to update our gate to remove dsvm05:17
zhenguoshaohe_feng: or move current functional tests to unit tests?05:17
shaohe_fengzhenguo: let me check the nova code, little minutes05:19
zhenguoshaohe_feng: ok, thanks05:19
zhenguoshaohe_feng: maybe this is helpful https://blueprints.launchpad.net/nova/+spec/functional-tests-for-nova05:20
shaohe_fengzhenguo: In my nova path, nova also have  regressions test  nova/tests/functional/regressions/05:24
zhenguoshaohe_feng: yes, seems nova have more tests05:25
zhenguoshaohe_feng: but as a new startup project, which way do you perfer? remove functional tests or keep the current implementation05:27
zhenguoshaohe_feng: nova unit tests also include api tests using fake_request which I think is similar to pecan.testing05:31
zhenguoshaohe_feng: ironic's pecan.testing part is in UT as well.05:32
*** yuntongjin has joined #openstack-nimble05:33
shaohe_fengzhenguo: I seen nova use  self.start_service  for functional test. I'm check whether it does start real server05:35
zhenguoshaohe_feng: we also start_service in ironic UT for conductor manager tests05:39
zhenguoshaohe_feng: which uses a fake topic05:40
* zhenguo brb05:43
shaohe_fengzhenguo: so we will move functional tests into unit?06:06
zhenguoshaohe_feng: I'm not sure,06:07
*** yuntongjin has quit IRC06:08
zhenguoshaohe_feng: maybe we need to invite more people to join this discussion06:08
shaohe_fengzhenguo: yes.06:09
zhenguoKevin_Zheng, liusheng, RuiChen, shaohe_feng, shihanzhang: let's talk about functional tests and unit tests06:09
zhenguoshaohe_feng: seems yuntongjin just quitted06:10
shaohe_fengzhenguo: yes, he is not in seat.06:12
shaohe_fengzhenguo: guess, he is smoking. :P06:13
zhenguoshaohe_feng: hah06:13
zhenguohi all, you can scroll back to see our discussion about functional tests, it's really need you all to help to decide what our functional tests would be like06:13
liushengseems different project have different definitions of functional tests :(06:16
zhenguoliusheng: that's true, but which way we should follow as a new startup project?06:18
liushengzhenguo: For Nova functional tests, it will also start a wsgi app in tests code06:20
zhenguoliusheng: yes, like what we do currently06:21
*** ChanServ sets mode: +o zhenguo06:36
* zhenguo brb06:41
openstackgerritliusheng proposed openstack/nimble: Add instance CURD related functional tests  https://review.openstack.org/39806807:32
zhenguoshoahe_feng: we will keep the current way to use functional tests and remove dependency on dsvm in our gate.07:35
zhenguoshaohe_feng: wdyt?07:35
*** luyao has joined #openstack-nimble07:38
RuiChendsvm waste so many time to build an whole devstack, we hope our patches can be verified and merged quickly, and acturally dsvm is not necessary for functional tests now07:38
openstackgerritliusheng proposed openstack/nimble: Add support for updating instance type  https://review.openstack.org/38643907:39
zhenguoyes, we will introduce tempest wih dsvm real env tests07:39
liushengzhenguo: tempest work item can be assigned to me :)07:43
zhenguoliusheng: ok, thanks very much :)07:43
liushengzhenguo: np :)07:44
shaohe_fengzhenguo: agree. at present our functional tests do not need dsvm07:56
zhenguoshaohe_feng: thanks07:57
*** yuntongjin has joined #openstack-nimble07:58
liushengzhenguo: Is this right ?   https://review.openstack.org/#/c/398176/08:22
zhenguoliusheng: already got a +2, haha08:25
liushengzhenguo: I am not very sure :P08:25
zhenguoliusheng: lol08:26
zhenguoliusheng: I think infra guys will be very happy if we can reduce the vm occupied time.08:27
liushengzhenguo: so they give +2 so quickly ? hah08:28
zhenguoliusheng: hah08:28
liushengzhenguo: and already got a +A...08:31
zhenguoliusheng:lol, so fast...08:31
RuiChencommunity think nimble is very very important project, everybody wait to review its patch :-)08:32
zhenguolol, I believe that's true...08:33
liushengmerged, let's try the new functional job08:36
openstackgerritliusheng proposed openstack/nimble: Remove the post_test_hook.sh script  https://review.openstack.org/39818408:36
openstackgerritZhenguo Niu proposed openstack/nimble: Follow up patch of bb68cb7b31ca4798ec4a55b25dd4ea66bf15a29b  https://review.openstack.org/39818508:38
*** luyao has quit IRC08:41
liushengseems the project config cannot become effective immediately08:50
zhenguoliusheng: yes, the gate check is not finished yet, should not be that long now08:54
openstackgerritShaoHe Feng proposed openstack/nimble: add PolicyFixture for functional test.  https://review.openstack.org/39819808:58
*** luyao has joined #openstack-nimble08:58
shaohe_fengliusheng: I add this patch. https://review.openstack.org/39819808:58
shaohe_fengliusheng: you can follow the commit message when you do you instance fucntonal test.08:59
shaohe_fengliusheng: for we have add authorization for instance functional test09:00
shaohe_fengzhenguo: do we need authorization for instance_type?09:01
zhenguoshaohe_feng, liusheng: IIRC, currently we don't have authorizaton in tests right?09:01
zhenguoshaohe_feng: yes,09:02
shaohe_fengzhenguo: yes. we have not authorizaton in tests. we need add it.09:02
zhenguoshaohe_feng: there's a instance_type_projects table in db, but not used09:02
liushengshaohe_feng: I used to think we can add some specific test for authorization, and the we don't consider auth for testing instance and instance type functionalities09:03
liushengshaohe_feng: reasonable ?09:03
shaohe_fengzhenguo: you need to add testcase list in your item, so we will not forget it. and we will add it after the fucntional tests are merged.09:03
zhenguoshaohe_feng: sure09:03
shaohe_fengliusheng: yes. agree. need specific test for authorization. and zhenguo will add this in testcase item list.09:05
shaohe_fengzhenguo: so what about instance_type_projects?09:05
liushengshaohe_feng: cool!09:05
shaohe_fengzhenguo: should we use  instance_type_projects for authorization?09:05
zhenguoshaohe_feng: instance_type is almost copied from volume_type09:05
zhenguoshaohe_feng: but we don't introduce projects09:06
zhenguoshaohe_feng: instance_type_projects makes it possible that you can specify which projects can use this type09:06
zhenguoshaohe_feng: projects or tenants :P09:07
liushengzhenguo: the new jenkins job config works :)09:07
zhenguoliusheng: hah09:07
shaohe_fengzhenguo: OK. So we need to record project_id in instance_type_projects?09:08
shaohe_fengliusheng: cool.09:08
zhenguoshaohe_feng: not sure, but we can copy volume type directly09:08
zhenguoshaohe_feng: need some volunteer to work on this09:08
shaohe_fengzhenguo: so let us read the cinder code.09:09
zhenguoshaohe_feng: ok09:09
shaohe_fengzhenguo: yes. OK. let me find a volunteer.09:09
zhenguoshaohe_feng: hah, thanks09:09
openstackgerritMerged openstack/nimble: Follow up patch of bb68cb7b31ca4798ec4a55b25dd4ea66bf15a29b  https://review.openstack.org/39818509:12
openstackgerritMerged openstack/nimble: Remove the post_test_hook.sh script  https://review.openstack.org/39818409:16
*** luyao has quit IRC09:23
zhenguoshaohe_feng: I added some checklist on our trello board tests subtasks card, not sure policy check should be in functional or unit tests09:30
*** tiantian has joined #openstack-nimble09:35
*** yuntongjin has quit IRC09:46
openstackgerritshihanzhang proposed openstack/python-nimbleclient: Support Instance Resource  https://review.openstack.org/39239910:13
*** liusheng has quit IRC10:29
*** liusheng has joined #openstack-nimble10:30
openstackgerritZhong Luyao proposed openstack/nimble: bug fix: delete instance correctly  https://review.openstack.org/39830611:38
openstackgerritZhong Luyao proposed openstack/nimble: bug fix: delete instance correctly  https://review.openstack.org/39830611:40

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