08:00:19 #startmeeting third-party 08:00:20 Meeting started Tue Mar 24 08:00:19 2015 UTC and is due to finish in 60 minutes. The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:23 The meeting name has been set to 'third_party' 08:00:39 raise your hand if you are here for the third-party meeting 08:00:45 Hi 08:00:51 hello lennyb 08:01:08 have we worked together yet? 08:01:15 I'm not sure I know your nickname 08:02:44 anteaya, yeah, I accidentally added Nova CI for Mellanox as voting one 08:02:52 ah 08:03:05 thanks for attending a meeting 08:03:17 how is mellanox coming along? 08:04:14 anteaya, btw, we sent an email asking to add our Nova CI as non-voting, and did not receive any answer. 08:04:21 right 08:04:26 I'm not surprised 08:04:43 I had advised nurit to attend a nova meeting to ask 08:05:01 you sent an email during feature freeze time 08:05:10 I'm not suprised it was ignored 08:05:20 I again suggest you attend the nova meeting 08:05:26 and ask at the meeting 08:05:31 I now, I attended to the meeting, but probably at the wrong hour. 08:05:43 the nova meeting 08:05:50 it alternates 08:05:55 yeah, #openstack-nova 08:06:05 no they meet in this channel 08:06:25 the #openstack-nova channel is their discussion channel 08:06:36 when they meet they meet in this channel 08:06:42 ah, I didnt know. I will look in the wiki for the "openning hours" 08:06:46 do you know how to see all the meetings? 08:07:19 #link https://wiki.openstack.org/wiki/Meetings 08:07:25 this page has all our meetings 08:07:42 click on the link for openstack compute (nova) 08:07:47 thanks 08:07:59 #link https://wiki.openstack.org/wiki/Meetings#OpenStack_Compute_.28Nova.29 08:08:14 that takes you further down the page and more links 08:08:26 which take you here 08:08:29 #link https://wiki.openstack.org/wiki/Meetings/Nova 08:08:55 they have the agenda for last weeks meeting up 08:09:07 which means this weeks will be at the other time 08:10:08 make sense? 08:11:43 you mean, this Wednesday at 0400 UTC 08:12:27 sorry, I got it 08:12:58 no 08:13:11 1400 was last week's meeting 08:13:30 this week's meeting is at the other time option 08:13:33 2100 08:17:23 lennyb: can you see that? 08:19:03 anteaya, yes. thanks. 08:19:12 and they meet Thursday's not Wednesday's 08:19:21 hi, is there any topic currently being discussed, or can I ask a question here and now ? 08:20:10 yeas, I saw. I was looking at nova third party ci meeting from https://wiki.openstack.org/wiki/Meetings#OpenStack_Compute_.28Nova.29 08:21:42 jordanP: hi let's just finish with lennyb first 08:21:50 anteaya, sure 08:21:54 nova third party ci meeting? 08:22:31 nova doesn't have a third party ci meeting 08:23:57 lennyb: ? 08:24:14 anteaya, you are correct. 08:24:20 okay great 08:24:30 so what time and where is the next nova meeting? 08:24:36 just so I am sure you understand 08:25:25 thursday 2100 utc #openstack-meeting. next week 16:00utc 08:25:52 next week 1400 08:26:20 but you got this week's meeting day time and place accurate 08:26:23 so well done 08:26:32 let's move onto jordanP's question 08:26:35 jordanP: hello 08:26:40 jordanP: please go ahead 08:26:46 I am still young to learn new things :) 08:26:50 right, so 08:27:14 lennyb: good, keep sticking around and asking questions 08:27:15 I've sent an email 4 days ago 08:27:17 [third-party]Properly format the status message with gerrit trigger 08:27:27 I don't know wheter you read it 08:27:42 do you know how to link email posts? 08:27:48 go to lists.openstack.org 08:27:50 no, I don't 08:27:54 find the list 08:28:02 read the archive find the link to the post 08:28:05 post it here 08:28:11 can you do that now? 08:28:24 then we can all see the post you want to discuss 08:28:24 yep 08:28:27 thanks 08:28:38 http://lists.openstack.org/pipermail/openstack-dev/2015-March/059494.html 08:28:58 I'll leave you 2min, so can can just read :) 08:29:13 the question is simple: what's your opinion :) 08:30:50 my opinion is that many people use zuul 08:31:16 and those that don't are just beginning and don't have the confidence to speak up on the mailing list and reply to your post 08:31:39 so if you are looking for replies to your post I don't expect you to get any 08:31:44 I thought so... :) 08:31:59 as for reformatting I think you should go ahead and see what you can accomplish 08:32:13 and if you get anywhere post again to your own thread with your results 08:32:32 and thanks for caring enough to try to improve the experience for developers 08:32:32 IMO gerrit trigger is easy to setup, and looks less scary than zuul. Most of use are familiar with jenkins, so I think supporting gerrit trigger makes sense 08:33:24 my goal is to propose a patch to slightly change the regex used to "capture" the comments posted by third party CIs 08:33:30 I'll see how it goes 08:36:11 that sounds like a good way forward 08:36:18 thank you for being proactive here 08:36:28 I'm not sure if you are used to open source workflow 08:36:34 it seems that you are 08:36:44 and unfortunately most folks in this space are not 08:36:59 so the concept of replying to your email post is beyond them 08:37:06 which is sad 08:37:13 since you are doing everything right 08:37:16 thanks jordanP 08:37:24 anteaya, sure. Thanks 08:38:15 thank you 08:38:37 anything more on your mind right now? 08:38:59 me, no :) 08:39:06 thanks for speaking up 08:39:20 lennyb: anything more you want to talk about right now? 08:39:27 no. 08:39:31 okay 08:39:36 thanks 08:39:57 I'll wait a few more minutes and see if anyone else shows up 08:40:23 you are welcome to stick around if you like but it is not required 08:40:25 anteaya, is it easy/possible change gerrit account of CI ? 08:40:35 lennyb: it is possible 08:40:44 did you create it yourself? 08:41:14 #link http://ci.openstack.org/third_party.html#creating-a-service-account 08:41:36 great, we would like to change Cinder CI gerrit account. It's not mine, but I want to associate it with email alias 08:41:41 if you did follow these instructions to create the account you wish to change you have full access to the account and can do so 08:42:15 do you know if you created the account yourself as opposed to having the infra team create it for you 08:42:42 we created it ourself, I believe. 08:43:18 good 08:43:26 then you can edit it to suit yourself 08:43:42 the only part you can't change is the gerrit username 08:43:50 all else you can edit 08:43:55 and you can do so yourself 08:44:09 ok, we want to change only email 08:44:15 you can do that 08:47:40 jordanP, check this link http://ci.openstack.org/third_party.html#creating-a-service-account 08:48:08 jordanP, there is a section about jenkins gerrit trigger 08:48:38 lennyb, the problem is how the results are reported bad 08:48:55 lennyb: if you go to the top of the document, in the upper left corner there is a menu 08:48:58 my setup works but there's a regex so that CI account appear on top in the Gerrit UI 08:49:15 if you click a title on the menu you get a link to that section 08:49:17 like this 08:49:21 #link http://ci.openstack.org/third_party.html#the-jenkins-gerrit-trigger-plugin-way 08:49:34 so that a code submiter knows easily if his patch broke a 3rd party driver 08:50:08 anteaya, I see it, thanks. 08:50:16 well the actual point of a third party ci is for the driver operator to pay attention which patches are not compatible with their driver 08:50:19 atm, for my CI, one has to click on the "toggle CI" button at the bottom to see the results of my CI 08:50:31 and review the patch and suggest a fix that will work with the driver 08:50:43 jordanP: right 08:50:53 because your ci is commenting not voting 08:51:31 anteaya, I am not sure. for example here : https://review.openstack.org/#/c/165214/ 08:51:31 if your ci is stable and cinder agrees to allow you to vote verified on the patches your results will show up with the rest of the ci results 08:51:51 jordanP: which is your ci 08:51:52 some 3rd party CI are non-voting but they appear on the top left corner of the UI 08:51:55 scality 08:52:12 which are non-voting but appear in the top left corner? 08:52:16 anteaya, you have to click on the togger CI button to see it 08:52:26 give me the name of a ci account and I'll check 08:52:28 anteaya, top right, sorry 08:52:40 yes top right 08:52:52 which system is non-voting but appears on the top right? 08:53:08 gate-rally-dsvm-cinder 08:53:13 but it's not 3rd party :) 08:53:15 that is a job 08:53:29 gate rally dsvm cinder is a job, not a ci account 08:53:38 haha, I think you're right, it's just a non-voting issue 08:54:12 which makes it a non-issue, I just have to ask the fine guys from the cinder team then 08:54:16 right now on this patch, no systems are posting votes 08:54:37 anteaya, arf okay, so how come some system are in the top right corner ? 08:54:40 since you can see in the column marked verified only jenkins has a response 08:55:00 yep 08:55:35 in fact, it's not that important that my 3rd party CI vote, but I'd like to be listed in the top right corner.. 08:56:37 right 08:56:47 and you are correct it is formatting 08:56:58 the parser for that page looks for formatting in the comment 08:57:19 if the comment format is the same is what jenkins posts it will put the results in the top right 08:57:26 if it isn't it won't 08:57:39 yep, okay, it's good to have this confirmation 08:58:00 and I was wrong, these systems are not currently able to vote 08:58:11 they have to be listed in this group to be able to vote: https://review.openstack.org/#/admin/groups/508,members 08:58:26 I'll talk to thingee about that tomorrow 08:58:49 anteaya, well I am not sure making 3rd party CI to vote is a gread idea 08:58:59 it's too early 08:59:01 imo 08:59:02 jordanP: me either but that isn't my choice 08:59:06 yep 08:59:16 it is my job to support the choices ptl's make 08:59:35 so obviously I didn't do my job and tell him about this gerrit group 08:59:39 I understand 08:59:39 so I'll do that tomorrow 08:59:41 thanks 08:59:59 and we are at time 09:00:05 it has been a fun meeting 09:00:10 thanks lennyb and jordanP 09:00:16 nice to work with you 09:00:18 thanks anteaya 09:00:20 see you next week 09:00:24 eeah anteaya :) 09:00:26 yep 09:00:27 :) 09:00:32 #endmeeting