08:00:16 #startmeeting daisycloud 08:00:17 Meeting started Fri Nov 18 08:00:16 2016 UTC and is due to finish in 60 minutes. The chair is huzhj. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:20 The meeting name has been set to 'daisycloud' 08:00:35 #topic Roll Call 08:00:44 #info Zhijiang 08:00:50 #info zeyu 08:00:56 #info luyao 08:01:27 #topic OPNFV: Escalator Support 08:01:48 #info zhouya 08:02:50 We are not only integrating escalator but also implenting escalator now :) 08:03:30 good 08:03:32 sunjing: any statue update for this topic? 08:03:47 zhouya: also from your side 08:04:01 Do we have kongwei connected? 08:04:33 I have beginned to implement the escalator frame from daisy. 08:04:37 #info daisy team not only integrating escalator but also implenting escalator now 08:04:42 Sorry, kongwei is not in at the moment. 08:05:13 sunjing: Good 08:05:17 Now the escalator service is up. 08:05:32 I just read the code try to modify spec file and build a escalatorclient rpm 08:05:42 sunjing: as intaller we need to know how to intall escalator 08:06:07 zhouya: you mean you have got the latest code from sunjing? 08:07:17 Next step ,I will try to work on the interface about how to call escalator for upgrade openstack. 08:07:36 no,I just read the code myself 08:07:37 I havn't got the code, sunjing, could you please release it as early as possible? 08:07:51 so taht we can review 08:08:26 sunjing: please contact kongwei on what api need to be done 08:08:46 I do not think we need to impl upgrading api for this phase 08:08:51 OK,there ara still some issue need to be modify.I will commit the code after the modify asap. 08:09:03 great 08:09:35 and we can query the version now? 08:09:40 #info sunjing meet kongwei to discuss what api should be done for D release 08:09:44 To huzhj: OK. I will contact kongwei . 08:09:47 pbr problem has solved? 08:10:31 zhouya: query version is an easy api, we can do it first 08:10:40 We avoid the pbr problom. 08:10:46 yes 08:11:24 we now first query the escalator version or openstack version? 08:11:51 zhouya: escalator to call into daisy to query the openstack version 08:12:04 we need talk about these with kongwei,maybe. 08:12:46 So the next thing we need to do is to impl the api in daisy 08:13:04 exactly 08:13:11 escalator will call installer other than the opposite? 08:13:39 sunjing: yes, escalator call installer 08:13:42 @sunjing you mean installer call escalator? 08:13:51 escalator sits on the top of installers 08:13:55 OK.I got it. 08:14:10 OK 08:14:17 but escalator itself have to be installer by installer 08:14:26 but escalator itself have to be installed by installer 08:14:47 sounds odd 08:14:50 Get version from inside a container is not easy 08:15:10 Zeyu , are you there? 08:15:16 yes 08:16:02 Since you are working on kolla , may be you can ask them how to get openstack component version our from a running container or image 08:16:30 you know , the version info is wrapped by the container 08:17:00 maybe i can send email to the ptl of kolla to ask this quesstion 08:17:00 not easy to get them 08:17:12 the version cann't mapped to the outside of container? 08:17:51 great. beware there are two type of versions 08:18:07 one: version in a image, two: version in a running container 08:18:24 what do we need 08:18:30 two is easy, for example , we can get it by calling docker exec... 08:18:35 one is hard . 08:18:48 yes,if so,we can get the version from docker exec. 08:18:51 Zeyu: we may need them all 08:19:07 ok 08:19:23 just like rpm 08:19:55 no matter before or after installing a rpm , we can get its version 08:20:25 So I think kolla image need the same character 08:20:38 this is a new feature 08:20:46 totallu 08:20:48 totally 08:21:29 #action Zeyu will send email to kolla team about the how to get openstack component version our from a running container or a static image 08:22:10 For support escalator, if we can not wait for this new feature, then we can first make a fake one. 08:22:43 maybe fire a BP to kolla 08:23:00 Yes 08:23:17 OK, anything else for this topic? 08:23:32 no 08:23:33 no 08:23:38 no 08:23:48 #topic OPNFV: CI Progress 08:24:16 luyao and Zeyu , what is new from your side about this? 08:25:01 now I can use common config to deploy nodes auto 08:25:19 by call deploy.sh 08:25:22 i commit the deploy job to OPNFV releng 08:25:52 based on luyao's script 08:26:42 Good, so i think the rest thing is adding the virtual env to jenkins. 08:26:56 yes 08:27:10 This is an urgent task. as well as adding the bare metal env 08:27:31 you give me some advice about the deploy job, i have modified it 08:28:16 zeyu: you mean this one:? https://gerrit.opnfv.org/gerrit/#/c/24459/ 08:29:09 #info Zeyu commit the deploy job to OPNFV releng 08:29:11 yes 08:29:43 #info luyao confirm that we now can use common config file to deploy virtual nodes automatically 08:29:51 Zeyu: I have +1 08:30:44 I read the eamil sent by you about the functest, it seem that the functest job only runs in verify stage 08:31:05 Sorry Zeyu, I think you are also working on escalator jjb which belongs to the prev topic. 08:32:39 Yes, functest smoke test can be run on both verify and merge. We Just choose one for time being. in future, if the time for deploy/test is not too long then we can consider run them on both phase. 08:33:22 but JOSE say that FUNCTEST_SUITE_NAME is only used by verify jobs in CI 08:34:14 I guess his "verify" include both verify / merge 08:34:32 that is generalized verify 08:34:37 ok ,i konw 08:35:25 escalator jjb is still in modification, i am not sure about step 08:35:53 such as virtual deploy 08:36:04 Zeyu: OK, let's talk about escaltor jjb offline. I can help 08:36:15 thanks 08:37:04 luyao: could you please send email to Zhihui about adding virtual env to OPNFV after a successful deplyment? 08:37:50 We can show her the successful deployed env, the config file and the deply script. 08:38:09 To let her know taht we are ready 08:38:47 #action Zhijiang and Zeyu will working on impl jjb for escalator 08:38:55 yes 08:39:02 Great 08:39:13 #action luyao will send email to Zhihui about adding virtual env to OPNFV after a successful deplyment 08:39:14 I will sed email right now 08:39:21 Great 08:39:27 OK, anything else? 08:39:39 no 08:40:07 no 08:40:33 #topic Core Code Abstraction 08:41:39 zhouya: Seems the CCA is done right? 08:41:45 yes 08:41:56 the core code abstraction is ok 08:41:56 Excellent 08:42:15 good 08:42:17 I saw a new feature comes in 08:42:24 tempest and rebot has passed 08:42:27 config file auto backup 08:42:28 yes 08:42:36 daisy config file suto backup 08:42:41 auto backup 08:42:58 I have contact qilongzhao to modify this 08:43:08 Such task can be run by cron/logrotate sevice though. 08:43:19 and he will modify the code to kick out the code from API layer 08:43:32 The only reason they need it in daisy seems is to probide API 08:43:48 provide API 08:44:02 yes 08:44:09 Good 08:44:54 Let him commit code by him self. zhouya, do not be the proxy :) 08:45:03 yes 08:45:50 all Teamers of daisy need to understand the process of new core code CI 08:46:02 If currently he has problem about contributing code youcan help him 08:46:09 And next they will commit core code to opensource 08:46:10 Yes 08:46:47 Anything else? 08:46:52 no 08:47:06 #topic Newton 08:47:35 One thing comes to my mind , we need a CI environment dedicated to Newton 08:47:46 yes 08:48:36 If we are lake of env, then may be we need a script to switch infrastructrure 08:49:33 #info we need a CI environment dedicated to Newton or need a script to switch infrastructrure 08:50:39 If nothing else , then that is all for today 08:50:54 Let's warp up 08:51:14 wrap up 08:51:37 OK 08:51:43 Bye, guys 08:51:50 bye 08:52:23 by 08:52:28 bye 08:53:41 #endmeeting