15:00:31 #startmeeting RDO meeting - 2018-12-05 15:00:31 Meeting started Wed Dec 5 15:00:31 2018 UTC. 15:00:31 This meeting is logged and archived in a public location. 15:00:31 The chair is amoralej. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:31 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:31 The meeting name has been set to 'rdo_meeting_-_2018-12-05' 15:00:31 o/ 15:00:33 Meeting started Wed Dec 5 15:00:31 2018 UTC and is due to finish in 60 minutes. The chair is amoralej. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:34 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:36 The meeting name has been set to 'rdo_meeting___2018_12_05' 15:00:37 #topic roll call 15:01:07 o/ 15:01:13 #chair moguimar ykarel 15:01:13 Current chairs: amoralej moguimar ykarel 15:01:15 Current chairs: amoralej moguimar ykarel 15:01:55 o/ 15:02:09 o/ 15:02:37 #chair PagliaccisCloud mjturek 15:02:37 Current chairs: PagliaccisCloud amoralej mjturek moguimar ykarel 15:02:38 Current chairs: PagliaccisCloud amoralej mjturek moguimar ykarel 15:02:59 \o/ 15:03:07 #chair chandan_kumar 15:03:07 Current chairs: PagliaccisCloud amoralej chandan_kumar mjturek moguimar ykarel 15:03:09 Current chairs: PagliaccisCloud amoralej chandan_kumar mjturek moguimar ykarel 15:03:57 o/ 15:04:48 o/ 15:04:58 #chair jpena number80 15:04:58 Current chairs: PagliaccisCloud amoralej chandan_kumar jpena mjturek moguimar number80 ykarel 15:04:59 Current chairs: PagliaccisCloud amoralej chandan_kumar jpena mjturek moguimar number80 ykarel 15:05:19 let's start with first topic 15:05:22 #topic Altarch image building job for cico 15:05:40 #link https://review.rdoproject.org/r/#/c/17657/ 15:05:45 mjturek, your topic 15:05:46 hey! 15:06:00 basically it's the same idea as the tripleo containers job 15:06:04 for altarch\ 15:06:27 but this will build ipa, overcloud, undercloud images 15:06:43 it's still WIP but figured I'd point it out and see if anyone has advice 15:06:44 do we have the resources for that? 15:07:02 number80: cico should 15:07:03 Especially regarding storage 15:07:16 Good to know 15:07:36 number80: when you say especially regarding storage do you mean publishing wise? 15:07:47 building wise I think cico should have enough resources 15:08:27 Yes, I know we have had issues in the past concerning storage which is independent of cico 15:08:34 dmsimard, jpena ^ 15:09:00 mjturek: where are you planning to host the resulting images? 15:09:06 I can't tell from the review 15:09:34 jpena: we would hope to publish it to a place analogous to the x86_64 images 15:09:49 would that not be possible? 15:10:17 we'd need to make some numbers to figure out the expected storage usage 15:10:55 ahhh and images.rdoproject.org doesn't specify arch currently 15:11:52 so we'd need to do something like add an rdo_truck_altarch dir to it? 15:13:34 mjturek: yes, either we create an rdo_trunk_altarch under each release dir or we add a prefix. I don't have a special preference 15:13:51 the important bit is to try to predict the storage requirements and see if they fit 15:13:54 cool, jpena is there anything I can do to help figure out storage? 15:14:22 mjturek: if you can build some test images without uploading, and check the resulting size, we can make some numbers 15:14:24 I guess build the images and see how large they are, then see how many versions we'd store at once? 15:14:32 jpena very cool we can work on that 15:14:43 * jpena thumbs up 15:16:01 alright I'm good here if you'd like to move on amoralej ! 15:16:35 ok, thanks 15:16:46 #topic push mariadb 10.3.10 & galera in stein 15:16:51 dciabrin, are you around? 15:16:57 hey amoralej 15:17:02 sorry i got elsewhere 15:17:34 so yes, I'd like to move forward and push the new mariadb upstream for stein 15:17:50 I have a review upstream linked in the agenda which shows that it's passing both undercloud/overcloud and upgrades 15:18:13 which i believe was the thing I promised to apevec and number80 15:18:56 that was to let you guys know about my request 15:19:24 #link https://review.openstack.org/#/c/617355/ 15:20:21 good 15:20:34 amoralej: we're inprocess of backporting networking-ansible to queens, what's the process for me to get a queens branch on distgit to build from? 15:21:08 https://review.rdoproject.org/r/#/c/17680/1/rdo.yml 15:21:40 oh, sry if I'm interupting the meeting 15:22:01 number80, do we have build for that mariadb and galera versions? 15:22:15 Normally yes 15:22:22 amoralej, yes I've used number80's builds for the review's tests 15:23:10 ok 15:23:27 number, so, what we need is just to send a review to promote them to testing? 15:24:03 amoralej: yep, but up to dciabrin to do it :) 15:24:25 ok 15:25:48 dciabrin, is it https://review.rdoproject.org/r/#/c/16911/3/deps.yml ? 15:27:12 those are the builds? 15:29:25 we'll keep working on https://review.rdoproject.org/r/#/c/16911/ 15:29:26 ok 15:29:29 let's move on 15:29:49 #topic fedora clients sync 15:30:02 #link https://trello.com/c/wkifSL7A/659-fedora-clients-sync 15:31:39 number80, short term we need to remove python2 subpackages in all openstack packages in fedora 15:31:51 do you have the list of packages that we maintain in fedora? 15:31:57 first thing would be to get the list 15:32:52 Jon Schlueter created openstack/tripleo-heat-templates-compat-distgit rpm-master: sync missing Requires from rocky-rdo branch https://review.rdoproject.org/r/17695 15:32:53 I'll go throught that 15:33:06 #action number80 list packages maintained by openstack-sig 15:33:18 number80, maybe we could create a etherpad with the list and the status 15:33:28 we need to make sure that they have openstack-sig as admin 15:33:31 my concern is that automating fedora builds is not possible 15:33:42 amoralej: main-admin is not possible for sigs 15:33:47 right 15:33:59 well, add the group as comaintainer 15:34:42 Also an important thing is that we also have to monitor bugs so I suggest having an alias for that 15:34:44 number80, what's the blocker for automation? 15:34:51 number80, +1 15:35:22 amoralej: we do not have control over what happens in Fedora dist-git, so manual merges are often required 15:35:41 like 9 times out of ten 15:36:06 nothing difficult but not something that can be done a by bot safely 15:37:26 o/ 15:37:49 utc-- me-- 15:38:40 #chair leanderthal 15:38:40 Current chairs: PagliaccisCloud amoralej chandan_kumar jpena leanderthal mjturek moguimar number80 ykarel 15:38:42 Current chairs: PagliaccisCloud amoralej chandan_kumar jpena leanderthal mjturek moguimar number80 ykarel 15:40:30 number80, what'd be next steps? 15:40:48 list packages, add to openstack-sig, check which ones need python2 removal 15:40:56 we'll need all that before stein ga 15:41:01 Next immediate step is checking what we owns and have sig co-owning them 15:41:06 at stein ga maybe we can do a more automated sync 15:41:13 I'll ping apevec for an alias 15:41:20 and Duck 15:43:35 quack 15:44:31 I know nothing about openstack-sig, but if I may help… :-) 15:45:38 number80: mail alias? 15:45:42 Fabien Boucher proposed rdo-infra/rdo-infra-playbooks master: Add sf.io and koji.sf.io backup to the backup role https://review.rdoproject.org/r/17642 15:45:58 Duck: alias or list so we can track bugs in bugzilla 15:46:27 ok, just select the one you prefer and I can do that 15:47:00 \o/ 15:49:17 btw, ML phase 2 is being engaged… 15:49:53 number80, so, anything else about the topic? 15:50:05 next step is creating the list of openstack packages in fedora 15:50:12 will you create an ehterpad? 15:50:26 not anymore (yes for the etherpad) 15:50:44 ok 15:50:47 let's move on 15:51:03 #topic chair for next week 15:51:06 any volunteer? 15:53:30 I can do it next week 15:53:46 thanks number80 15:53:56 #action number80 will chair next week 15:54:00 #topic open floor 15:54:10 any other topic? 15:55:17 hum 15:55:28 amoralej: new ducks for events? 15:55:45 (and keeping one for me btw, so I can start a collection) 15:55:52 :) 15:56:41 of course I can help man a booth and quack, but I know barely nothing about OpenStack 15:57:01 so we need new rubber duckies 15:57:22 I guess that's a priority topic for the upcoming FOSDEM & co events 15:57:42 i guess that's something for leanderthal ^ 15:57:58 yes 15:58:08 leanderthal: don't forget to reply about the ML ;-P 15:58:43 we'll be doing ducks, yes, but only for openstack summits; at fosdem and devconf we're doing scarves 15:59:12 i will also need volunteers for the booths of both, so i'll need to put together a sign up page. 15:59:16 Because we're frozen there 15:59:21 yesssssss 15:59:37 maybe there will be snow ducks or something, but only if the budget remains 15:59:38 leanderthal: you can already sign me up for fosdem 15:59:45 number80, you're awesomeness 15:59:54 ooh scarves! 15:59:55 i'll make sign ups by next week 15:59:59 * number80 not going to Brno coz it;s too cold 16:00:06 it's so. freaking. cold. 16:00:21 i would make snow suit swag, if i had the money, i swear it. 16:00:26 omg legwarmers. 16:00:34 ahem. 16:00:37 but, yes. booths. 16:00:57 i'm wrapping up travel (six?!? events?!?) so that i know our budget for the last quarter. 16:01:35 leanderthal: think about face mask 16:01:46 i'm listening 16:02:01 one of those infinite scarves that can wrap around the head / neck 16:02:10 Merged rdopkg master: Add support for *info in clone command https://softwarefactory-project.io/r/14329 16:02:35 OOOH. TRAIN CON-DUCK-TORS 16:02:48 OMG YESSSSS 16:02:58 PagliaccisCloud, that's totally what we're doing for denver. DONE AND DONE. 16:03:18 yiss (insert Happy Gary) 16:03:32 Maybe we can wrap that discussion and have it next week ;-) 16:03:34 amoralej, we're over time; my apologies 16:03:39 no problem 16:03:50 (good to see you all again!) 16:03:50 yeah, i'll close 16:03:59 you can add the topic for next week 16:05:45 #endmeeting