08:04:34 <anteaya> #startmeeting third-party
08:04:35 <openstack> Meeting started Tue Aug 25 08:04:34 2015 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:04:36 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:04:38 <openstack> The meeting name has been set to 'third_party'
08:04:42 <anteaya> hello
08:04:48 <eantyshev> hello!
08:04:54 <anteaya> hi eantyshev
08:04:58 <anteaya> how are you today?
08:06:12 <eantyshev> fine, but having problems getting my changes reviewed
08:06:24 <anteaya> yes I can understand that
08:06:34 <anteaya> what patches have you up?
08:06:43 <anteaya> can you link them here?
08:07:05 <eantyshev> https://review.openstack.org/211124 and https://review.openstack.org/215029
08:07:16 <anteaya> #link https://review.openstack.org/211124
08:07:24 <anteaya> #link https://review.openstack.org/215029
08:07:33 <anteaya> it works if you use the link syntax as well
08:07:42 * anteaya looks at the patches
08:07:55 <eantyshev> thank you, anteaya!
08:09:24 <anteaya> the -1 isn't helping, is abel lopez on irc that you have seen?
08:09:42 <anteaya> can you and ianw talk to this person at all?
08:10:37 <anteaya> derek higgins gave a second +2 on the patch, I am wondering why he didn't approve it
08:11:36 <anteaya> the cloudlinx patch
08:11:54 <anteaya> we don't tend to just add os.s to the gate
08:12:17 <anteaya> so perhaps an item added to the infra meeting agenda might be in order
08:12:35 <eantyshev> we have already 2 forks of devstack-gate, and that's odd
08:12:36 <anteaya> to tell folks why you think this is a good addition and helps openstack
08:12:54 <anteaya> I don't understand your last comment
08:13:02 <anteaya> what is odd?
08:14:03 <eantyshev> it's very inconvenient to maintain the forks of devstack-gate, as it changes frequently...
08:14:29 <anteaya> why are you forking devstack-gate?
08:15:01 <eantyshev> we use it in our CI, to run devstack on slaves
08:15:17 <anteaya> why not just run devstack-gate?
08:15:18 <eantyshev> and we have CloudLinux slaves
08:15:45 <anteaya> okay that won't be a compeling reason for infra to add an os
08:15:48 <eantyshev> obviously we need CloudLinux support in devstack-gate
08:15:54 <anteaya> no
08:16:06 <anteaya> that is not the conclusion infra will draw
08:16:19 <anteaya> adding an os to infra means infra has to support the os
08:16:31 <anteaya> maintenance, security
08:16:34 <anteaya> daily builds
08:16:42 <anteaya> odd packaging differences
08:17:09 <anteaya> you being frustrated, while important, and I care about your happiness
08:17:22 <anteaya> is not a compeling reason for infra to add another os to the gate
08:18:30 <anteaya> jhesketh: if you are about, can you take a look at https://review.openstack.org/#/c/211124/4 and possibly offer a review?
08:18:36 <eantyshev> okay, how do you like another way for us: apply this change to devstack-gate in a job?
08:18:54 <anteaya> well that is an interesting question
08:18:58 <jhesketh> anteaya: will do
08:19:03 <anteaya> jhesketh: thank you
08:19:25 <anteaya> jhesketh: and eantyshev is wondering how to address needing to use an unsupported os
08:19:40 <anteaya> jhesketh: if you have any thoughts on that, I would be interested to hear them
08:20:17 <anteaya> eantyshev: well creating a job is individual to a certain repo, so is much more likely to be accepted
08:20:31 <anteaya> eantyshev: however jobs use supported os.s
08:20:50 <anteaya> so I am at a loss as to how a job could be created to use an unsupported os
08:20:59 <jhesketh> anteaya, eantyshev: as in you need dib to support another os?
08:21:03 <eantyshev> that's not a problem, I'm talking about our private CI
08:21:19 <anteaya> jhesketh: context https://review.openstack.org/#/c/215029/1
08:21:20 * jhesketh is trying to get up to speed sorry
08:21:28 <anteaya> no no, thanks for being here
08:22:13 <anteaya> eantyshev: right if this change is for your private ci, it doesn't belong in upstream
08:22:14 * jhesketh is often lurking
08:22:21 <anteaya> jhesketh: :) thanks
08:22:43 <anteaya> eantyshev: but we certainly can discuss how you might approach it in your own ci
08:22:54 <anteaya> I've just never thought about it
08:23:27 <anteaya> eantyshev: so your fork of devstack-gate
08:23:54 <eantyshev> I have 2 choices: either I fork devstack-gate or I apply needed change to upstream devstack-gate in my private job
08:23:54 <anteaya> what would happen if you applied your patch 215029 to your clone of devstack-gate?
08:23:54 <patchbot> anteaya: https://review.openstack.org/#/c/215029/
08:24:19 <anteaya> hello patchbot pleasure to meet you
08:24:55 <anteaya> eantyshev: yeah I get that, I'm not feeling that upstream adding an os to accomodate your private ci is a compeling reason for infra
08:25:00 <eantyshev> anteaya: no, idea is to apply it to upstream devstack-gate, so I don't have to rebase
08:25:06 <anteaya> right
08:25:15 <anteaya> I'm saying chances are not good that will happen
08:25:38 <anteaya> and am asking if you are able to apply it to your clone of devstack-gate
08:25:42 <eantyshev> I understand, but the change will stay, won't it?
08:26:17 <anteaya> if you apply it to your clone you will need to check it every time you reclone
08:26:59 <anteaya> but unless that section of the file is changed if you pull down from master and fast forward your changes the change should stay in your clone
08:27:23 <eantyshev> if I choose to clone devstack-gate, I commit there what I want, and don't need the change
08:27:32 <anteaya> okay
08:27:44 <anteaya> that probably is your best way forward unfortunately
08:27:44 <jhesketh> anteaya: so I'm not familiar enough with grub to comfortably merge 211124. I'd like to see Ian's last question answered first at the very least
08:27:56 <anteaya> jhesketh: thank you for your review
08:28:12 <anteaya> jhesketh: and yes having an answer to ianw's question would be good to have
08:28:32 <eantyshev> but If the change will be available at review.o.o, I will apply it privately to upstream devstack-gate, and that will work for me
08:28:47 <anteaya> eantyshev: sure that works too
08:29:18 <anteaya> and probably a better way forward for you
08:29:35 <eantyshev> anteaya: this way I don't have to maintain a fork
08:29:46 <anteaya> not having a fork is a good thing
08:29:48 <anteaya> I agree
08:29:51 <anteaya> :)
08:30:11 <eantyshev> okay, that will comfort me :)
08:30:16 <anteaya> oh good
08:30:18 <anteaya> thank you
08:30:25 <anteaya> I'm glad we are in a happy place
08:30:34 <anteaya> what else shall we discuss today?
08:33:01 <eantyshev> I have no questions at the moment
08:33:04 <anteaya> great
08:33:15 <anteaya> any reason I should not close the meeting?
08:33:46 <anteaya> eantyshev jhesketh thanks for your participation today
08:33:55 <anteaya> always a pleasure to spend time with you
08:33:58 <anteaya> thank you
08:33:59 <jhesketh> no trouble, sorry I wasn't more helpful
08:34:05 <eantyshev> thank you!
08:34:20 <jhesketh> anteaya: I assume it's some ridiculous time for you. Go sleep!
08:34:20 <anteaya> jhesketh: I think that often myself, wish I was more helpful
08:34:22 <anteaya> :)
08:34:32 <anteaya> jhesketh: ha ha ha on my way back to bed
08:34:34 <jhesketh> you're always very helpful anteaya
08:34:36 <anteaya> night!
08:34:42 <anteaya> jhesketh: aw thanks Josh
08:34:43 <jhesketh> goodnight!
08:34:52 <anteaya> #endmeeting