15:01:39 #startmeeting RDO meeting - 2017-07-26 15:01:40 Meeting started Wed Jul 26 15:01:39 2017 UTC and is due to finish in 60 minutes. The chair is number80. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:41 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:44 The meeting name has been set to 'rdo_meeting___2017_07_26' 15:01:47 #topic roll call 15:01:57 who's here and who's not here? 15:02:36 /o 15:02:41 present sir xD 15:03:11 \o 15:03:28 o/ 15:03:28 #chair ykarel chandankumar dmsimard amoralej 15:03:29 Current chairs: amoralej chandankumar dmsimard number80 ykarel 15:03:47 rbowen, Duck ? 15:03:59 jruzicka/ 15:04:36 Merged openstack/ceilometer-distgit ocata-rdo: Update to 8.1.0 https://review.rdoproject.org/r/7905 15:04:47 o/ 15:04:48 Ok, let's start with Software factory upgrade 15:05:07 #topic review.rdoproject.org has been upgraded to software factory 2.6 15:05:25 Sorry I'm late. I'm here. 15:05:33 #chair rbowen PagliaccisCloud 15:05:34 Current chairs: PagliaccisCloud amoralej chandankumar dmsimard number80 rbowen ykarel 15:05:39 dmsimard: ^ 15:05:54 Hi! 15:06:17 This is just to say that review.rdoproject.org has been successfully upgraded to the latest version of Software Factory, 2.6, last night 15:06:25 o/ 15:06:38 There is still some amount of issues related to the delivery of emails but this should be improving over time 15:06:48 #info review.rdoproject.org was successfully upgraded to Software Factory 2.6 last night 15:06:53 #chair jschlueter 15:06:54 Current chairs: PagliaccisCloud amoralej chandankumar dmsimard jschlueter number80 rbowen ykarel 15:06:59 good 15:07:03 Software Factory 2.6 brings a lot of cool things 15:07:08 At a high level overview 15:07:33 Nodepool and Shade have been largely updated which will yield more stability and less problems starting and destroying nodes 15:07:52 (You don't have to deal with that but I had to clean up stuff in nodepool almost every day) 15:08:07 o/ 15:08:14 Do we still have issues in used nodes cleaning? 15:08:17 We've also cherry-picked a patch which will allow us to use boot from volume in nodepool 15:08:20 #chair jruzicka 15:08:21 Current chairs: PagliaccisCloud amoralej chandankumar dmsimard jruzicka jschlueter number80 rbowen ykarel 15:08:27 number80: hard to tell for now, we will monitor how things are going 15:08:34 ack 15:08:52 dmsimard: any plan to integrate repoexplorer with r.o.o? 15:08:55 Using boot from volume through nodepool will allow us to launch "heavier" jobs against RDO cloud due to the disparity between ephemeral and volume storage 15:09:02 quakc o/ 15:09:27 chandankumar: repoexplorer is in software factory but not enabled right now, we can consider it after we've done things higher up in the priority 15:09:39 number80: sorry I'm late 15:09:41 dmsimard: ack, Thanks :-) 15:09:52 no worries 15:10:00 in the short to mid term, we'll implement ELK support in review.rdo so that logs are indexed, we can make dashboards and such 15:10:13 * number80 suggests to move to the next agenda item 15:10:15 we will also be able to have a grafana dashboard which will look like http://grafana.openstack.org/dashboard/db/nodepool 15:10:21 Sweet 15:10:36 Yay pretty graphs 15:10:40 it looks like a bowl of candies 15:10:42 and then we will also be officially migrating from jobs running on jenkins to zuul-launcher 15:11:09 I think that covers some of the highlights of the things this new version will allow us 15:11:46 The SF team has done awesome work so I'll extend my congrats and thanks to tristanC, fbo, mhu and nhicher for their excellent job 15:11:59 thanks, it looks a paving stone to the road to jenkins-less infra :) 15:12:06 next topic :) 15:12:16 dmsimard: Can you take all the things you just said and make a blog post out of them? 15:12:24 rbowen: sure 15:12:27 Thanks. 15:12:37 number80:can I haz a chair pleaze? 15:12:55 #action dmsimard and SF guys to write a blog post about SF 2.6 15:13:02 Duck: no 15:13:05 #topic Moving mailing lists to @rdoproject.org, status 15:13:08 #chair Duck 15:13:09 Current chairs: Duck PagliaccisCloud amoralej chandankumar dmsimard jruzicka jschlueter number80 rbowen ykarel 15:13:10 ;_; 15:13:31 rbowen, Duck (who has a seat now) ^ 15:13:40 Re: moving mailing lists, Duck/Misc have given me things for auth. I haven't done them yet. So it's waiting on me. 15:13:46 But we have mailinglists.rdoproject.org 15:14:01 lists.rdoproject.org rather 15:14:08 So you can see that progress has been made. 15:14:27 Hopefully I'll get my part done today and we can move to the next step soon. 15:14:31 That's all. 15:14:48 we're discussing the migration details 15:14:48 #info lists.rdoproject.org is up but not GA 15:15:11 And aurelian is working on the HK bug that was making migration a problem. 15:15:12 I'll be in DebConf soon, so we can test it and polish and schedule for after I'm back 15:15:12 #info RDO mailing lists migration details in discussion 15:15:25 I haven't followed status of that this week. So I don't know what progress has been made there. 15:16:40 rbowen: so I know what's wrong and it should be ok 15:16:46 oh, ok. 15:16:50 Good to know. 15:16:59 at the very worst we can rebuild the whole machine if needed 15:17:13 Duck: so no need to bribe Aurélien with food (can be expensive0 15:17:16 also the latest migration details for oVirt were all fine 15:17:25 Excellent. 15:17:43 well there's bugs or limitations and it would be nice to have them overcome one day 15:18:12 Can we do anything to help with that process? 15:18:36 not sure. abompard is working well but not 100% on it I presume 15:18:40 Well, I am assuming that the same people that are mods now will be mods on the new setup. 15:18:49 so pushing for more workforce would be nice 15:19:00 So I'll forward the auth instructions to that group, and if someone gets to that before I do, that would be great. 15:19:02 rbowen: please draft a list 15:19:08 Will do. 15:19:28 we need to have them login on the new system first, then list their handles and I can then add the rules for Ansible 15:19:36 s/rules/parameter/ 15:19:46 also 15:20:07 when up, please login with one external system, and if you wish link to another one 15:20:25 if you login on one and later the other because you do not remember, then you have two separate accounts 15:20:36 Ah. Good to know. 15:20:37 and there's yet no way to merge (already reported) 15:21:02 so in your account setting you can do the link 15:21:44 documenting all these pitfalls and procedures is in the TODOLIST 15:22:23 rbowen: did you see my reply around the other UI? 15:22:31 forgot the name 15:22:36 the Apache one 15:22:45 Apache PonyMail 15:22:52 yes :-) 15:22:58 cute name 15:23:02 I think you said it's a possibility later? 15:23:02 kawaii 15:23:14 that's how I see it yes 15:23:15 It's just a frontend, and can work on top of any archive, as I understand it. 15:23:22 no 15:23:27 it's THE archive 15:23:29 But it's still a very young project. Maybe let it bake for a while longer. 15:23:31 Oh, I see. 15:23:41 also because it's integrated with the search engine 15:23:43 The guy that wrote it actually set one up for us. 15:23:50 elasticsearch 15:23:58 http://rdo.fosslists.org/list.html?rdo-list@redhat.com 15:24:05 Although he turned it off, a year ago or so. 15:24:06 but I think migrating would be possible 15:24:17 But it can subscribe to any existing list, and be a secondary UI of sorts. 15:24:17 David Moreau Simard proposed rdo-infra/rdo-infra-playbooks master: First iteration of Sensu monitoring v2 https://review.rdoproject.org/r/7670 15:24:21 using the mbox files 15:24:32 http://rdo.fosslists.org/list.html?rdo-list@redhat.com:2016-10 for example 15:24:35 Anyways, details for later. 15:25:02 And, yes, it can import existing archives. That's what we did at Apache. 15:25:04 lists.apache.org 15:25:11 well it's important to see if the "later path" is possible or not, so that we do not end-up blocked on the current Ui forevet 15:25:13 r 15:25:37 * number80 suggests to keep discussion focused :) 15:25:37 nice presentation 15:25:37 lists.apache.org imported almost 20 years of archives, and works great. 15:25:46 Yes. Moving along. :-) 15:25:53 gogogo 15:26:03 #topic Update from EasyFix office hours 15:26:06 chandankumar: ^ 15:26:15 yup 15:26:23 a little background 15:26:57 few weeks back we have started easyfix project to collect easyfix issues so that we have lots of easy bugs to work 15:27:07 that will increase new contributors to RDO 15:27:23 here you can find the issues https://github.com/redhat-openstack/easyfix/issues 15:27:37 on Tuesday we have hosted RDO office hours 15:27:44 it was a good start 15:28:07 we are able to get more issues 15:28:17 I made a shortcut to the easyfix repo, so that it's easier to remember. rdoproject.org/easyfix 15:28:19 issues no: incresed from 8 to 15 15:28:37 here is the notes https://review.rdoproject.org/etherpad/p/rdo-office-hour-easyfixes 15:28:52 and minutes from office hour http://eavesdrop.openstack.org/meetings/rdo_office_hour_2017_07_25/2017/rdo_office_hour_2017_07_25.2017-07-25-11.31.log.html 15:29:12 So now it's comes the future questions and actions. 15:29:17 #info EasyFix office hour 1st edition 15:29:24 https://review.rdoproject.org/etherpad/p/rdo-office-hour-easyfixes 15:29:42 Do we want next 2nd office hour next tuesday in different time zone? 15:29:43 #info EasyFix office hour 1st edition minutes 15:29:56 http://eavesdrop.openstack.org/meetings/rdo_office_hour_2017_07_25/2017/rdo_office_hour_2017_07_25.2017-07-25-11.31.log.html 15:30:03 chandankumar: did we have request? 15:30:16 (I mean timeslots requests) 15:30:20 number80: currently no request we have received from anybody 15:30:59 number80: can we plan for next week also for the same time? 15:31:05 chandankumar: then, try to submit to find a suitable hour that works for you and someone else in the group for NA 15:31:19 (yes, you shouldn't be doing this alone) 15:31:30 The time this week was early for NA. But it worked ok. 15:31:31 otherwise, let's keep it same timeslot for the next one 15:31:49 number80: we want to include you 15:31:55 please propose a new time slot 15:32:30 chandankumar: the last one works for me (save for calls that I can't really predict) 15:33:07 rbowen: is the same time slot works for you? 15:33:29 Yes. 15:33:37 current time slot is 11:30 A.M. (UTC) 15:33:40 Probably not for anybody west of me, though. 15:33:47 dmsimard: jschlueter ^^ 15:33:56 That is 7:30am my time. 15:34:24 yea it's early for reliably being online but should be able to drop in 15:34:47 number80: rbowen i think we can move 2 hours ahead. 15:35:02 13:30 will be ideal for everybody may be? 15:35:07 wfm 15:35:09 chandankumar: when you get started can you ping me explicitly for the office hours? 15:35:17 wfm 15:35:20 jschlueter: yup sure 15:35:36 jschlueter: we'll schedule earlier reminders on the rdo-list 15:35:42 +1 15:35:57 The first one was a learning experience :) 15:36:16 #info new office hour timing from next week is 13:30 P.M. (UTC) 15:36:33 Moving to next question 15:36:50 same topic/ 15:36:52 ? 15:36:55 What kind of projects we include for RDO contributions. 15:36:58 number80: yes 15:37:06 okay 15:37:14 continue then 15:37:28 currently we have RDO packages issues, rdopkg, dlrn and packstack 15:37:28 * number80 asks for jruzicka to prepare for the next topic ;-0 15:37:39 chandankumar: docs ? 15:37:40 I'd say anything at all, although, as observed earlier, we need to be encouraging people to go upstream whenever relevant. 15:37:47 what other tools or projects we can include? 15:37:48 A couple of the items are docs, yes. 15:38:01 dmsimard: ah missed, rdo docs, 15:38:12 rbowen: can pkovar mentor documentation issues? 15:38:28 I think we can volunteer him, yeah. :-) 15:38:34 And me, too, for most things. 15:38:44 Good, important to have point of contacts 15:38:53 i'll help too, so long as they don't ask "how-2-github" questions 15:39:09 * number80 can be added to anything packaging or tooling tasks mentors list 15:39:10 Here is the list of mentors/contact points https://github.com/redhat-openstack/easyfix#mentors 15:39:11 * jruzicka is so ready 15:39:33 rbowen: what about moving this list https://github.com/redhat-openstack/easyfix#mentors to rdo website? 15:39:59 Sure. We could do that. 15:40:19 chandankumar: has larsks explicitly said that he'd be mentoring people? 15:40:27 number80: yes 15:40:34 would it be worth considering putting "labels" on the mentors ? 15:40:34 Just asking since he's still default assignee in bugzilla 15:40:36 ack 15:40:46 i was just about to ask that dmsimard 15:40:48 like, this person for this, that person for that 15:41:05 I mean, you can ask me packaging stuff but I'm no expert 15:41:31 putting mentors with labels is a good idea 15:41:36 dmsimard: as long as you can draw red lines with blue pens you'll be fine 15:42:10 kinda like this? https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute 15:42:36 hey that's pretty cool 15:42:38 didn't know that existed 15:43:09 Wow. That's awesome. I wasn't aware of that either. 15:43:10 let's create a list for the same. 15:43:25 who wants to take this task. 15:43:52 I would be glad to create the page(s). 15:44:03 Will of course need other folks to fill in details once it's up. 15:44:14 #action rbowen create a mentor page in RDO site 15:44:17 rbowen: yes sure, we can add the stuff later on. 15:44:17 sold 15:44:35 we were talking about projects to includes. 15:44:46 that leaves us 15 minutes so wrap up this topic 15:44:48 We have a page like that in the IRC section, though, and it's kind of sparse. 15:44:51 Probably combine the two. 15:44:54 +1 15:45:30 number80: can we talk about projects after the meeting? 15:45:34 sure 15:45:43 that's it from my side. 15:45:44 I want to leave some time for the rest of the agenda 15:45:46 Merged rdo-infra/rdo-infra-playbooks master: First iteration of Sensu monitoring v2 https://review.rdoproject.org/r/7670 15:45:58 #topic rdopkg-0.44.1 released 15:46:01 jruzicka: ^ 15:46:13 oh yes 15:46:32 #info changelog in commit message: https://softwarefactory-project.io/r/#/c/8987/2//COMMIT_MSG 15:47:12 you can put links right after, either use #link or raw url (nothing before) 15:47:34 Merged openstack/glance-distgit rpm-master: Load rootwrap filters from glance_store https://review.rdoproject.org/r/7858 15:47:46 b0rkage was already detected and fix proposed: https://softwarefactory-project.io/r/#/c/9075/ 15:48:00 but it's now stuck on CI rdopkg-unittests NOT_REGISTERED in 0s 15:48:24 yeah, i'm already talking with sf team 15:48:26 Yeah, i'd like to discuss counter-measure, like defining CI usage of rdopkg and try to come up with tests scenarios to cover them 15:48:27 about that 15:49:33 for that, I introduced new behavioral tests 15:49:42 which are well suited for defining requirements like this 15:50:11 Once we have stable working 0.44 release 15:50:18 Yup, but I'd like us to sprint on that during next office hours 15:50:29 number80: +1 15:50:47 behave ~= cucumber 15:50:55 focus will be on automated release using SF and improving all kinds of tests, mainly integration tests 15:51:06 Merged rdo-infra/weirdo master: Update Ansible to 2.3.1.0 https://review.rdoproject.org/r/7795 15:51:23 David Moreau Simard proposed rdo-infra/rdo-infra-playbooks master: Add missing zk01 node to review.rdo host inventory https://review.rdoproject.org/r/7892 15:51:24 Yup, but I would even encourage people to try trimming scenarios or even do PoCs in shell 15:51:33 So yeah, preventing these breakages is the main focus now. 15:52:01 what matters is that we proper material to build reliable tests suite and ensure that CI can use rdopkg w/o pinning 15:52:35 about half way there ;) 15:52:54 Maybe adding a gate with DLRN job could help? 15:52:59 amoralej, dmsimard ^ 15:53:10 can be non-voting at first 15:53:24 yes, i think that'd be good 15:53:27 yeah, there should definitely be better integration tests for rdopkg due to the potential widespread impact 15:53:44 okay, let's plan that 15:53:47 i use also rdopkg for diferent things from releng 15:53:53 not just for tripleo-ci, but for DLRN itself and everywhere else 15:54:02 that i'd like to ensure keep working 15:54:09 Adding DLRN is a first step 15:54:17 #action hguemar to create an easyfix ticket to improve rdopkg imtegration tests 15:54:30 Merged rdopkg master: Use absolute path for repo_path https://softwarefactory-project.io/r/9075 15:54:36 amoralej: then adding gating jobs for those should be considered too 15:55:16 are we good on that topic? 15:55:21 indeed, I tried hard so that adding any kind of test is easy 15:55:23 https://github.com/softwarefactory-project/rdopkg/blob/master/features/newversion.feature 15:55:34 jruzicka: let's share the load :) 15:55:44 we'll we release a new version once the patch is merged? 15:55:47 BDD was an excellent idea 15:56:15 amoralej: a 0.44.1 should come soon 15:56:27 0.44.1 is out since yesterday 15:56:30 no? :) 15:56:32 0.44.2 15:56:35 right 15:57:03 wasn't it 0.44.0? 15:57:18 #action jruzicka to prepare rdopkg 0.44.2 to integrate latest bugfixes 15:57:19 0.44.1 shortly after with few packaging fixes 15:57:30 ah, ok 15:57:42 number80, I'm ready to release as soon as the fix is merged 15:57:55 jruzicka: then you can start, it just got merged :) 15:58:02 yayz :) 15:58:06 #topic open floor discussions 15:58:13 last chance to raise a new topic 15:58:31 can I raise something quick? 15:58:35 go ahead 15:58:39 not sure if this is right venue 15:58:54 it would be good if the sample spec files could be updated with the new macros 15:59:01 (btw, if there are any volunteers to take the chair next week, just #action yourself directly) 15:59:02 just something I have come across with new packages 15:59:15 just a point of order, probably not relevant for this meeting 15:59:18 snecklifter: that's the right place and yes, it's good idea 15:59:24 number80: ah ok, thanks 15:59:34 yes, we need to update the examples 15:59:37 #action snecklifter submit patches to sample spec files 15:59:43 the macros are great but I have been missing them 16:00:04 * number80 is not pressuring people at all into doing things :o) 16:00:08 number80: ha, ok, will add to the list :) 16:00:15 i think examples repo is not in review.r.o ? 16:00:22 amoralej: not yet 16:00:27 snecklifter: https://github.com/openstack/rpm-packaging/tree/master/openstack/openstack-macros 16:00:36 snecklifter: here is the list of macros we use 16:00:56 chandankumar: ah ok, thanks I'll make a note 16:01:10 will help others coming along 16:01:15 thats it from me, thanks 16:01:21 snecklifter: spec file template https://github.com/openstack-packages/openstack-example-spec 16:01:42 chandankumar: yes, thats what Ive been using but out of date I think 16:01:52 yes, it is 16:02:00 David Moreau Simard proposed rdo-infra/rdo-infra-playbooks master: Add missing zk01 node to review.rdo host inventory https://review.rdoproject.org/r/7892 16:03:07 we are out of time but before closing the meeting let's celebrate success, we just got the first tripleo job passing in rdoinfo gate testing CBS builds https://review.rdoproject.org/jenkins/job/rdoinfo-tripleo-ocata-testing-centos-7-multinode-1ctlr-featureset005-nv/37/console 16:03:13 \o/ 16:03:40 amoralej: awesome 16:03:45 great work 16:03:56 so much great work happening everywhere in rdo 16:04:02 <3 everyone 16:04:19 no volunteers for next meeting? 16:04:30 amoralej: we should move the example-specs repo to rdo-infra or something 16:04:31 number80: i will take it 16:04:41 #action chandankumar to chair next meeting 16:04:42 amoralej: or redhat-openstack 16:04:50 okay, then see you next week 16:04:52 amoralej: and put it in review.rdo 16:04:53 #endmeeting