08:01:15 #startmeeting third-party 08:01:16 Meeting started Tue Mar 8 08:01:15 2016 UTC and is due to finish in 60 minutes. The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:01:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:01:19 The meeting name has been set to 'third_party' 08:01:38 hello 08:01:43 hi 08:02:19 hi lennyb__ 08:02:27 how are you today? 08:02:50 I am fine, fighting with Ironic:). how are you? 08:03:18 I'm fine, not fighting with ironic 08:03:20 :) 08:03:29 what are you doing with ironic? 08:04:23 we are working on some features over our hardware, so CI is a very important phase. But currently I am trying to get my ironic tempest pass 08:05:48 you are working on a ci for ironic? 08:05:58 eventually yes. 08:06:25 nice 08:06:43 do you have to meet their current deadlines? 08:06:56 I think their deadlines are for current drivers 08:08:15 I've noticed that there is only cisco CI as third party. I am not sure that we will meet the deadlines. 08:08:47 we are still working on solutions that will satisfy community and our HW :) 08:08:53 are you in conversation with ironic about the deadlines? 08:09:12 I'm sorry I didn't know earlier you were putting together an ironic ci 08:09:20 we could have talked about the deadlines 08:09:54 this round the deadline was basically create a gerrit account and have it report to the sandbox 08:10:13 you could have finished it in about 30 minutes 08:10:32 the report to the sandbox didnt' need to be automated that I saw 08:10:49 but the deadline for doing this was m3 which has passed 08:11:27 this deadline wasn't about having a system in place it was about interacting with the community 08:12:16 I see. There is always a newer version of openstack :). 08:12:26 yes 08:12:35 that is the point of our release cycle 08:12:45 we are always working on a release 08:13:26 btw, do I need a new gerrit account for Ironic CI or I can use 'one for all' ? 08:14:11 that is a question you would need to ask them 08:14:19 have you talked to anyone in ironic? 08:14:58 ok. not yet, I've talked to them about the issues I had. 08:15:29 oh? 08:15:35 I also cant 'ask' for CI yet, since our setup not working yet. 08:15:37 to whom did you speak? 08:15:45 that is not the point 08:16:06 the point of the ironic deadline was for you to interect with the ironic team 08:16:15 so they knew who you are and what you are doing 08:16:35 having a working setup is not the expectation at this point 08:16:47 ensuring ironic knows you exist is the point 08:17:14 I see. I asked questions in irc and got some answers. I did not introduce myself 'properly' 08:17:59 please introduce yourself 08:18:15 tell them who you are and what you are wanting to do 08:18:24 so they can know about you and tell you what you need 08:18:41 are you in the ironic channel? 08:19:11 yeap, 08:19:17 well that is good 08:19:23 I'm glad to hear that 08:19:57 well mrda is in the ironic channel, or was a short time ago 08:20:03 introduce yourself to him 08:20:16 his time zone would overlap yours 08:20:22 ok, thanks. 08:20:26 I'm sorry I didn't know this before 08:20:43 I would have encouraged you to contact them before the deadline 08:20:50 you couldn't we started to work on ironic only recently 08:21:10 oh you don't have a current driver in ironic? 08:22:24 we suppose to work with ironic 'as is' we have some patches to support our HW, but it's not 'baked' yet 08:23:07 I don't understand 08:23:17 do you have code in ironic master currently? 08:23:56 not yet 08:24:03 okay thank you 08:24:20 well in that case it might be that the current deadline doesn't apply to you 08:24:36 but make contact with ironic without delay and find out 08:25:04 ok 08:25:19 okay thanks 08:25:33 and I hope your testing goes well 08:25:41 thanks. 08:26:05 is there anything you would like to talk about today? 08:26:16 nope 08:26:30 okay 08:26:47 did you read the logs from the monday 15:00 utc meeting? 08:27:02 not yet, 08:27:13 we talked about ensuring operators read their email and reply in person to patches if need be 08:27:27 and we talked about a memory leak issue with zuul 08:27:33 do you run zuul? 08:27:50 I've seen email regarding zuul, yes I am running it 08:28:09 have you seen any memory leak issues? 08:28:48 no, but I also wasnt looking for it 08:29:14 what version of zuul are you running? 08:29:41 2.1.1.dev121 08:30:34 can you see how much memory it is using? 08:30:53 * lennyb__ checking 08:34:42 1872604 kb 08:35:40 wow 08:35:43 well done 08:36:18 what else can you tell me about your zuul setup 08:36:31 how often do you restart zuul? 08:36:54 looks like it was restarted recenly 08:36:58 oh 08:37:11 do you know how long ago it was restarted? 08:37:21 and have you any idea who restarted it? 08:37:32 how many people administer your ci system? 08:37:52 basically I restarted it once a week. Only me is working with it 08:38:05 how long ago did you restart it? 08:38:15 and why do you restart it once a week? 08:39:38 My manager can also work on CI in cases where I am not available. In cases that there are some failures and I am not sure what it is, I am stopping CI, debugging the issue and starting it again 08:40:48 what was happening that you started restarting zuul weekly 08:42:32 it is possible the zuul memory leak is affecting you 08:42:40 it's statistics. I am not 'schedule' this. and more like once every 2 weeks. I can 'check' if you are interested 08:42:54 I'm interested 08:42:59 you don't have to do it now 08:43:13 ok, 08:43:15 but yes we are gathering information from as many folks running zuul as wel can 08:43:31 because we still are trying to understand where the leak is happening 08:43:35 so thank you 08:43:55 np 08:44:06 if you are able to post to the mailing list thread about the zuul memory leak on the infra mailing list that would be wonderful 08:44:08 thanks 08:44:14 so that's all I have 08:44:22 any objection to me closing the meeting? 08:44:45 ok, no, have a good rest of the night 08:44:49 thanks 08:44:56 enjoy your day 08:45:02 see you next week 08:45:05 #endmeeting