15:02:42 #startmeeting RDO meeting (2016-03-16) 15:02:42 Meeting started Wed Mar 16 15:02:42 2016 UTC. The chair is dmsimard. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:42 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:02:42 The meeting name has been set to 'rdo_meeting_(2016-03-16)' 15:02:43 \o/ 15:02:47 \o/ 15:02:47 o/ 15:02:53 o/ 15:02:55 \o 15:02:55 roll call ! 15:02:56 /0/ 15:02:58 o\ 15:02:59 o/ 15:03:02 o/ 15:03:06 \o/ 15:03:08 that really blew up 15:03:33 #topic Setting up rsync server for trunk repositories 15:03:56 That came up last week I believe 15:04:09 #chair leanderthal dmsimard tosky rbowen jruzicka_ elmiko apevec elmiko 15:04:10 When someone wanted to access our trunk repositories over IPv6 and had to resort to dirty hacks 15:04:27 #chair leanderthal tosky rbowen jruzicka_ elmiko apevec elmiko chandankumar 15:04:28 Current chairs: apevec chandankumar dmsimard elmiko jruzicka_ leanderthal rbowen tosky 15:04:33 chandankumar: thanks :p 15:04:34 yep, and it came back this week during the DLRN instance outage, ccamacho mentioned it 15:05:13 so setting up a rsync server is fairly easy, the question is more do we have the resources/bandwidth for it 15:05:21 right 15:05:28 I don't think we want to set up the rsync server on the server where the build are taking place 15:05:33 as it can be fairly resource intensive 15:05:36 I'd suggested to export current-passed-ci only 15:05:41 +1 to that 15:06:00 apevec: for centos-master? 15:06:12 yes and stable branches 15:06:16 maybe current-tripleo could also be a good option? 15:06:32 not sure if that'd be worth, derekh ^ ? 15:06:48 unless you want to keep local mirror in tripleoci 15:06:52 derekh, dprince ^ 15:07:06 I think I saw somewhere that they eventually want to get rid of current-tripleo since the CI is getting better with oooq and stuff 15:07:08 trown: ^ 15:07:33 afaict there are different opinions in ooo community 15:07:40 :) 15:08:13 dmsimard: working on it :p 15:08:18 so arch would be to 2-level: 15:08:27 first sync to some other server than trunk.rdo 15:08:35 So, as I understand it, we should have a second server (let's call it mirror.trunk.rdoproject.org or something), this mirror syncs the current-passed-ci from the main trunk.rdoproject.org server and then exposes these through rsync 15:08:38 and run public rsync server there? 15:08:41 yeah 15:08:44 makes sense 15:08:50 I don't feel a whitelist is necessary 15:09:01 unless we see some malicious intent, this is a public and open mirror 15:09:09 ack, it is not w/ separate mirror server 15:09:14 I'm been thinking of keeping a mirror of current-tripleo on a server local to the tripleo ci rack, but no firm plans yet, we also use /curent for some packages, so we would still be hit by an outage 15:09:38 derekh: would exposing a rsync server on current-tripleo be helpful ? 15:09:45 but I was going to do a wget -m or somthing 15:09:54 rsync could be more efficient 15:09:58 We're trying to make it easy for people to sync., 15:10:11 so do where could we host mirror.rdo ? Same rcip cloud? 15:10:38 apevec: I'd ask for resources elsewhere, so we could use it as another backup in case of issues 15:10:47 or use proper CDN ? 15:10:48 jpena: +2 15:10:56 jpena, good point 15:11:01 +2 for hosting it elsewhere, hosting a mirror in the same place is kind of beyond the point 15:11:19 does anyone around have a public cloud with resources to share? 15:11:48 or can anyone give an estimate how much would it be to use real CDN, from RAX or elswhere? 15:12:00 other than os1 and trystack I don't know 15:12:14 trown, ^ you had some pricing for rax cdn iirc ? 15:12:31 We still have some free rax credits, right? 15:12:41 a rax cdn is not a rsync server 15:12:48 rax cdn perhaps for exposing the mirror through http 15:12:54 but you can't expose rsync over cdn o_O 15:12:57 This was from a while back, we took advantage of the free-for-opensource program they had? 15:13:16 rbowen, we never went to the bottom of that free-for-oss rax offer 15:13:24 Oh, ok. I couldn't remember how that panned out. 15:13:25 they're probably mutually exclusive, the question goes back to do we want 1) expose rsync 2) host trunk mirrors on cdn 15:13:36 iirc trown asked and there wasn't any answer 15:13:37 apevec: I tried to use RAX CDN for the undercloud image, but they never charged me 15:13:44 making use of a CDN may reduce the need for rsyc, less likely people will want to mirror if they arn't getting hit by outages 15:14:01 trown, that was your personal account? 15:14:09 apevec: ya I never got a response on the community account 15:14:56 Red Hat probably has a good connection with RAX, they support OSP and stuff now 15:15:00 We can dig 15:15:53 I'll ask around OSAS some, and see if other projects have a thing like that that we can get in on. 15:15:53 we could, but I'm not sure if that biz relationship extends into free accounts :) 15:16:09 apevec: well, not saying that 15:16:09 CentOS has a mirror network, too. It seems that we could tap into that. 15:16:10 rbowen, yeah, that must be a common topic 15:16:14 but knowing who to ask is a good first step 15:16:19 and we must have people that know who to ask 15:16:28 I would expect that CentOS is the right place to ask. 15:16:36 rbowen, we are using centos mirror for stable releases 15:16:57 which need to be CBS builds for centos to sign and distribute 15:17:01 this is for trunk.rdo 15:17:10 Sorry, I spaced out for a moment there. 15:18:11 ok, so actions? rbowen ask oass, me ask up to mgmt chain about rax relationship? 15:18:20 sounds good to me 15:18:24 oops, osas! 15:19:03 yep, sounds like a plan 15:19:05 #action apevec to ask around for a RAX contact for a community oss account 15:19:05 #action apevec to ask internally about rax cdn contacts 15:19:09 #undo 15:19:09 Removing item from minutes: ACTION by apevec at 15:19:05 : apevec to ask internally about rax cdn contacts 15:19:10 #undo 15:19:10 Removing item from minutes: ACTION by dmsimard at 15:19:05 : apevec to ask around for a RAX contact for a community oss account 15:19:13 lol 15:19:13 he 15:19:15 h 15:19:15 #action apevec to ask around for a RAX contact for a community oss account 15:19:27 :D 15:19:34 that was dramatic 15:19:36 rbowen: you going to ask osas about CDN stuff ? 15:20:05 do we have plan to use OpenStack Infra (one day) to build packages? It would help to have free hosting 15:20:06 Yes. 15:20:23 #action rbower to ask OSAS team about CDN usage 15:20:26 #undo 15:20:26 Removing item from minutes: ACTION by dmsimard at 15:20:23 : rbower to ask OSAS team about CDN usage 15:20:29 #action rbowen to ask OSAS team about CDN usage 15:20:33 #action rbowen to ask OSAS for other projects with CDN that we can share 15:20:35 oops 15:20:36 EmilienM: yes, eventually 15:20:37 #undo 15:20:37 Removing item from minutes: ACTION by rbowen at 15:20:33 : rbowen to ask OSAS for other projects with CDN that we can share 15:20:50 dmsimard: their cloud is very reliable 15:21:01 next topic 15:21:09 #topic Updates on openstack test subpackage 15:21:12 chandankumar: ^ ? 15:21:47 except openstack-sahara-tests, all openstack projects have now test subpackage 15:21:50 hey chandankumar ! thanks for your work here, puppet-tempest now installs the packages: https://review.openstack.org/#/c/292638/ 15:22:08 that's cool 15:22:25 sahara-tests package is blocked due to this review https://review.openstack.org/293258 15:22:35 EmilienM: slightly off topic but those package names should probably go in a ::params :p 15:22:40 I'm working on using Tempest plugins in Puppet CI now... but lot of blockers to make it work. Packaging was the first one, thanks a lot RDO for it. 15:22:46 EmilienM: oh wait they are, nm 15:22:52 once merged i will file a package review for sahara tests 15:22:55 dmsimard: they are https://review.openstack.org/#/c/292638/3/manifests/params.pp 15:23:00 that's it from my side 15:23:15 chandankumar: that patch has two +2's, do you know what's holding it back ? 15:23:16 chandankumar, good work! 15:23:18 EmilienM, you are welcome. :-) 15:23:21 chandankumar: the CI ? 15:23:26 dmsimard, yes 15:23:33 we'll also need tests in clients at least keystoneclient 15:23:50 apevec, i will be starting on clients from tomorrow 15:23:54 according to ayoung that's where keystone integration tests will be/are 15:24:04 FYI using tempest plugins will allow to increase testing coverage because plugins cover more than tempest tree tests. So thanks to chandankumar's packages, upstream CI will test more things 15:24:06 dmsimard: it was submitted (sahara_tests) few hours ago, give it some time 15:24:35 tosky: aye, was just wondering if two +2's wasn't enough :) 15:24:52 apevec, ++ 15:24:53 "my code is merging" https://xkcd.com/303/ 15:24:59 dmsimard: if they are not balanced, maybe not 15:25:23 there are couples of reviews with +2 but with failed CI 15:25:37 apevec: lol nice one 15:25:53 sounds good to me 15:25:55 great work chandankumar 15:25:57 chandankumar++ 15:25:58 dmsimard: Karma for chandankumar changed to 3 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:26:16 Anything else on the topic of test packages ? 15:26:26 not from myside 15:26:28 chandankumar++ 15:26:28 apevec: Karma for chandankumar changed to 4 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:26:55 #topic open floor 15:27:21 dmsimard, also we need to find chair for next meeting 15:27:27 * dmsimard nods 15:27:30 after open floor ! 15:27:41 I guess I can give a small update 15:27:44 regarding rdo-infra 15:27:53 #link https://github.com/rdo-infra 15:28:01 can we merge https://review.gerrithub.io/#/c/265812/ and fix the requirements in follow-up? 15:28:02 We've been trying to open up our infrastructure more 15:28:04 eggmaster: ^ 15:28:20 that is our only failure to build from source 15:28:22 So, basically stuff like playbooks to setup the website, modules for delorean, monitoring, stuff like that 15:28:35 trown: yeah, that's ok by me I guess 15:28:37 trown, I'll fix that, reqs is needed 15:28:42 although 15:28:43 rdo-infra can be seen as analogous to openstack-infra 15:28:59 I notice no os-testr in trunk latest build report 15:29:15 eggmaster, so is it dep or not? 15:29:18 it is 15:29:23 FYI RDO dev dashboard is back online: http://46.231.133.253:3030/rdo-dev 15:29:26 it used to be python-tempest-lib dep so idk how that was working 15:29:43 flepied, please add that to rdo-infra :) 15:30:00 #link http://46.231.133.253:3030/rdo-dev 15:30:05 apevec: ok how do I do that ? 15:30:07 there are a couple other Reqs, paramiko, jsonschema, that were python-tempest-lib deps 15:30:14 related to infra, has everyone seen rpmfactory status report from fbo ? 15:30:20 any questions/ concerns? 15:30:23 flepied: where is the repository for the code for that ? 15:30:27 dmsimard, SSL was fixed in the meantime 15:30:37 flepied: we have a rdo-infra organization now https://github.com/rdo-infra 15:30:42 apevec: I have spec change review queued up, shall I submit? 15:30:44 dmsimard: https://github.com/fredericlepied/rdo-dashboards 15:31:22 jpena: can you also consider moving puppet-dlrn to rdo-infra ? 15:31:37 dmsimard: sure, what do I need to do for that? 15:31:49 jpena: settings -> transfer ownership -> rdo-infra 15:31:57 easy enough :D 15:32:12 dmsimard, or not.. still HSTS issues w/ my Firefox on https://review.rdoproject.org/ :( 15:32:22 fbo, tristanC ^ 15:32:27 apevec: yeah, might need to clear cache or something on browser side 15:32:30 HSTS sticks client side 15:32:34 aah 15:32:40 I haven't cleared cache fwiw 15:33:00 dmsimard: I'll need admin rights in rdo-infra 15:33:10 basically HSTS is "don't ever visit this domain on non-https" 15:33:12 apevec: heh, I'm redeploying it as we speak 15:33:18 dmsimard: yes me too 15:33:22 FF say cert is sefl-signed, while it should be letsencrypt... 15:33:26 apevec: let'sencrypt certificate are not yet re-imported 15:33:33 ah ok 15:33:43 apevec: okay to send invites to jpena and flepied for rdo-infra ? 15:33:52 I redeployed it from scratch just to be sure the instance is clean 15:33:53 dmsimard, ack 15:34:19 invites sent 15:34:21 apevec: ^ 15:34:31 Okay, important next topic 15:34:35 #topic chair for next meeting 15:34:51 I can take next week 15:35:04 #action trown to chair next meeting 15:35:05 thanks trown 15:35:07 :D 15:35:18 thanks everyone for attending 15:35:34 #endmeeting