01:00:09 #startmeeting tricircle 01:00:10 Meeting started Wed Oct 11 01:00:09 2017 UTC and is due to finish in 60 minutes. The chair is zhiyuan. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:00:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:00:14 The meeting name has been set to 'tricircle' 01:00:43 hello I am song from szzt. last week we fininshed the tricircle qos test case . and we have 01:00:43 pass all in ourself dev envirment.But we heared that the test envirment has some problem 01:00:43 so we do not push the pr until the test envirment is ok. 01:00:58 hello 01:01:27 morning 01:01:35 to song, yes, that's the first topic I would like to discuss 01:01:45 #topic zull v3 check 01:02:24 infra team is migrating zuul from v2 to v3, and it is not stable enough currently 01:03:10 but according to the message from the mail list, "It is however non-gating, in the sense that it will not attempt to 01:03:13 merge a change nor prevent it from merging. 01:03:14 " 01:03:50 so we push the qos test pr until it is stable enough,how about? 01:04:01 so I think if the patch passes the jenkins check pipeline, we just merge the patch? 01:04:47 Infra should provide a stage phase for zuul V2 01:04:51 like this patch: https://review.openstack.org/#/c/508496/ 01:04:56 agree with it 01:05:01 hi all sorry for late 01:05:46 the patch above also fix the configuration of rabbitmq, which affects the jenkins check 01:06:10 hello 01:06:31 hi joe 01:06:34 there are should be v2 and v3 job in paralell 01:06:53 and make sure v2 jobs are still working 01:07:07 and v3 jobs can be non-voting jobs 01:07:33 after v3 jobs and zuul v3 become stable, switch v2 jobs to v3 jobs 01:07:41 as the test result of patch 508496 shows, both jenkins and zuul pipeline are running 01:07:50 there does exist some problem with the configuration of rabbitmq, making the installation fail 01:08:07 yesterday, i tried to install tricircle with devstack, it fails 01:08:10 to yipei, yes, it's fixed in 508496 01:08:34 so we should merge 508496 anyway 01:08:50 yes 01:08:58 i think so, since zuul pipeline is non-gating 01:09:31 legacy-tricircle-dsvm-functional POST_FAILURE in 28m 53s 01:09:48 legacy-tricircle-dsvm-multiregion RETRY_LIMIT in 4m 04s 01:10:05 both these two jobs only in zuul v3 not working 01:10:40 ok, approve the patch to be merged first 01:10:55 yes, sometimes the ansible master fails to connect to other nodes so it fails to post the logs 01:12:36 it's also said that infra team is planning to roll forward out of the partial Zuul v3 rollback starting at 11:00 UTC on Wednesday October 11 01:12:57 so there wil be some CI downtime 01:13:38 that's too regretful 01:15:05 ok, the jenkins gate pipeline is working 01:15:12 from zuul.openstack.org 01:15:52 but i notice the python27 test fails :( 01:16:23 i will update the patch later 01:17:27 almost all failure. 01:18:25 The following packages have unmet dependencies: libcurl4-gnutls-dev : Depends: libcurl3-gnutls (= 7.47.0-1ubuntu2.2) but 7.47.0-1ubuntu2.3 is to be installed 01:18:46 maybe because some requirements update not merged 01:19:30 oops 01:19:54 or recheck 01:20:26 i just see the requirements update patch from OpenStack Proposal Bot, all failure 01:20:54 for dependency issue like this, I think the global requirement needs to be updated 01:21:39 you mean we should manual upgrade the global requirement? 01:24:15 oh, it seems that it's the dependency issue of app, not python library 01:25:06 ok 01:25:09 i will check the mail list to see if there's some discussion about this 01:25:58 #topic queens-1 plan 01:26:33 queens-1 deadline is from Oct16 to Oct20 01:27:10 i feel like we have risk to finish our plan for queens-1 01:28:31 lb, default group update, user distinguish are targeted in queens-1 01:28:42 For default security group update i havecommited the first version code. 01:29:17 i will submit the configuration guide this week, hope it can work in other environments 01:29:31 i see it. there may be several runs of modification for it 01:30:16 still don't know why the amphora doesn't work, very annoying 01:32:53 will test it 01:33:13 About tricircle client, new patch for job pagination is committed. 01:33:51 do we need to postpone lb to queens-2? 01:34:55 to zhiyuan, if the configuration guide works, i think don't need to postpone it 01:36:02 And there are some problems, i haven't find the solution. Waiting for your review 01:36:21 it may also be some midifications on the configuration guide 01:36:47 ok, i see, so we postpone it to queens-2 01:39:03 it seems that joe is temporary offline 01:39:47 hello, just come back 01:40:17 seems lots of our work were blocked by infra-issue 01:40:42 yes, so we are talking about that we may have risk to finish the queens-1 plan 01:41:39 we can move these to queens-2 01:42:26 tricircle is not strict mile-stone aligned project 01:42:52 we can adjust the milestone date if needed 01:43:18 https://releases.openstack.org/reference/release_models.html 01:43:51 our release model is "cycle-with-intermediary", https://releases.openstack.org/reference/release_models.html#cycle-with-intermediary 01:44:18 no need to strict follow community milestone date, sure it'll be better if we can. 01:44:37 ic, so do we tag queens-1 around Oct16 to Oct20? at least the integration test with nova cell v2 is done 01:45:28 of course we can, it's a great step to work with cells v2 01:46:15 ok, hopefully the py27 error can be fixed soon 01:47:02 hi,all.the qos test case are most made by szzt team xiaohan zhang and he is very family with the openstack especially with the openstack network.so what next plan we can do? 01:48:50 we have a schedule in this page: https://etherpad.openstack.org/p/tricircle-queens-ptg 01:50:00 what about this: Network deletion reliability 01:50:46 ok, we will see this detail after the meeting and choose one. 01:51:01 ronghui first would like to have a try but not confirmed yet, so there is a "TBD" 01:52:10 fine, we can talk about the detail offline 01:52:26 thank you. we will seen it after the meeting.and conform it a little later. 01:52:54 ok 01:53:08 I found the etherpad is not linked to wiki page, just working on it 01:53:28 thanks, joe 01:55:03 any other topic? 01:55:28 no for me 01:55:30 no for me 01:55:40 no for me 01:55:45 nor 01:55:47 no 01:55:48 no 01:56:04 no 01:56:35 ok, thanks for attending the meeting 01:56:39 #endmeeting