15:05:04 #startmeeting third-party 15:05:05 Meeting started Mon Aug 31 15:05:04 2015 UTC and is due to finish in 60 minutes. The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:05:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:05:09 The meeting name has been set to 'third_party' 15:05:13 hello 15:05:49 some meetings do roll call prior to starting a meeting to figure out if they have quorum to hold the meeting 15:06:01 quorum isn't needed for these meetings 15:06:12 hello! 15:06:17 what shall we discuss today? 15:06:19 hello eantyshev 15:06:56 hi 15:06:59 I want to propose a solution for devstack-gate for those who run it on third-party distributions 15:07:01 for instance the tc meeting needs quorum of its members before it can be started 15:07:09 okay 15:07:16 shall we discuss that first? 15:07:20 +1 15:07:20 o/ 15:07:29 great, eantyshev take it away 15:08:23 There could be another variable, say, DEVSTACK_GATE_IS_FEDORA, which could be set to 1 is some rhel-based OS isn't supported upstream 15:09:12 so that is_fedora() will check it when it encounters somthing it doesn't know 15:09:24 that's it 15:09:27 eantyshev, can you explain the problem first? 15:10:21 o/ 15:10:38 we run our CI on CloudLinux, which is unsupported by devstack-gate, and I hope to get rid of local forks at last 15:10:58 https://review.openstack.org/215029 15:11:48 eantyshev and I talked at a prior third party meeting and I told him that it is highly unlikely CloudLinux will be supported upstream 15:11:48 Does anyone else in third-party uses anything apart from centos and fedora, BTW? 15:12:51 anteaya: Yes, so I decided we can customize is_fedora() to meet my needs, w/o specifying CloudLinux literally 15:14:13 eantyshev, you do that by redefining the function? 15:14:30 so you ask a good question, does anyone else have this use case in addition to yourself 15:14:51 not here 15:15:15 asselin__: no, but by modifying is_fedora() so that it will check for that variable if nothing else matches 15:15:53 wznoinsk: thank you 15:16:34 you do that with a fork or e.g. sed / inline update? 15:17:25 that function foes come from devstack, do you also need to update devstack? if so maybe we should see what they think? 15:17:50 pretty sure it does anyways 15:18:27 clarkb: devstack supports CloudLinux when FORCE=yes specified, we made appropriate change there 15:19:14 but here we cannot explicitly define CloudLinux, as this would mean it is supported in upstream 15:19:41 clarkb: and I'm going with no in terms of adding another infra supported os to the mix 15:20:13 asselin__: do you mean how I do it at the moment in my setup? I use local fork of devstack-gate 15:20:35 eantyshev, yes. 15:20:51 eantyshev, out of curiosity, what happens when you don't have that set? 15:21:19 o/ 15:21:49 asselin__: devstack-gate fails with OS undefined 15:24:55 okay so does anyone in addition to eantyshev have this issue? 15:25:25 is this something that needs a broad solution or something that eantyshev could use some support to figure out for his setup 15:25:34 eantyshev: I'm guessing you are male, yes? 15:25:36 eantyshev: you may want to check on mailing list to get ppl opinion 15:25:43 no, but we have othere issues. We just use inline sed changes to avoid a fork 15:26:21 asselin__: have you an example you can share in a paste? 15:26:27 sed -i '/^[ ]*_ping_check/d' functions.sh 15:26:35 sed -i '/^[ ]*_http_check/d' functions.sh 15:26:44 sed -i '/git_prune$/d' functions.sh 15:27:13 we skip those lines b/c they cause performance issues and are not relevant to our evn 15:27:33 asselin__: for one of our projects we just apply corresponding changes at review.o.o, which is almost the same as inline patching 15:28:19 anteaya: male, yeah 15:28:40 eantyshev, yes, we do that too for other projects, but only for stuff we expect to have merged eventually. 15:28:51 eantyshev: thanks 15:29:29 so some options to customize your scripts include sed and local patches, yes? 15:30:21 any more here? 15:30:24 anteaya: asselin__: I think that inline patching is not very stable, though 15:30:48 customization of any kind is usually a weak point, agreed 15:31:17 eantyshev, yes, it has it's own downsides, but we haven't had any issues with it (so far). 15:31:44 do we have more to discuss here? 15:31:54 Should I make the same proposal in openstack-dev? 15:32:15 you can if you wish 15:32:27 but keep in mind you seem to be the only person with this issue 15:32:49 so the likelyhood upstream will accept the patch (depending on the patch) is uncertain 15:32:58 but you are welcome to propose and have the discussion 15:33:14 ok, then I'll try it 15:33:21 no harm in that 15:33:30 shall we move on? 15:33:32 eantyshev, and imho your case is a simple one to use sed. you could even replace CentOS with CloudLinux 15:33:39 do we have anything else to discuss? 15:34:04 eantyshev, but if you can get it merged, then all the better 15:34:22 so I think it's reasonable to try that first 15:35:14 does anyone else have anything they would like to discuss today? 15:35:32 asselin__: then I should indeed try it first. Feel welcome to review: https://review.openstack.org/#/c/215029/ 15:35:47 eantyshev, done I like your approach 15:36:29 #link https://review.openstack.org/#/c/215029/ 15:36:50 * anteaya waits to see if there is more 15:37:58 is there more? 15:38:51 assuming there isn't any more on this topic, does anyone else have anything else to discuss today? 15:39:39 no 15:39:49 okay thanks 15:40:02 does anyone have any reason why I should not close this meeting? 15:40:38 thank you all for your kind attendance and participation 15:40:41 nothing from me, thanks for this discussion 15:40:43 I appreciate it 15:40:46 thanks anteaya 15:40:49 eantyshev: thank you 15:40:53 see you next week 15:41:02 enjoy the rest of the day/evening/night 15:41:05 #endmeeting