15:01:50 #startmeeting RDO Packaging Meeting (2015-09-30) 15:01:50 Meeting started Wed Sep 30 15:01:50 2015 UTC. The chair is jpena. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:50 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:02:04 #topic Roll Call 15:02:08 o/ 15:02:09 o/ 15:02:12 o/ 15:02:30 #chair trown dmsimard elmiko apevec 15:02:30 Current chairs: apevec dmsimard elmiko jpena trown 15:02:55 I'm just partially here 15:02:56 o. 15:03:01 o/ 15:03:04 #chair social eggmaster 15:03:04 Current chairs: apevec dmsimard eggmaster elmiko jpena social trown 15:03:35 apevec: lgtm 15:03:37 o/ 15:03:41 o/ (though trown has more current info than me) 15:03:47 #chair derekh mburned 15:03:47 Current chairs: apevec derekh dmsimard eggmaster elmiko jpena mburned social trown 15:04:11 jruzicka, number80 - are you at least partially here ? 15:05:33 apevec: o/ 15:05:43 #chair number80 15:05:43 Current chairs: apevec derekh dmsimard eggmaster elmiko jpena mburned number80 social trown 15:06:10 Agenda is at https://etherpad.openstack.org/p/RDO-Packaging, in case you need to add a last-minute topic 15:06:17 Completely off topic but I'd really love to have the time the page http://trunk.rdoproject.org/centos7/report.html was generated. I never know which timezone it's in. I think I'll put a review in 15:06:42 dmsimard: UTC 15:07:05 I plan to add some js in this page, after pushing jinja2 review 15:07:21 so... moving to the first topic? 15:07:23 but please keep it "some" :) 15:07:24 jpena: go 15:07:35 agenda is go 15:07:38 #topic stable/liberty Delorean 15:07:41 sorry for sidetracking 15:08:02 #link https://trello.com/c/VPTFAP4o/72-delorean-stable-liberty 15:08:12 so jpena has instance running 15:08:33 I'd like to switch centos7-liberty today 15:08:41 currently it's symlink to centos7 i.e. Trunk 15:08:47 I've set up a test env in http://209.132.178.247/liberty/status_report.html , using apevec's patch 15:09:14 #link https://review.gerrithub.io/248584 15:09:23 I'll switch khaleesi jobs to use centos7-liberty and open up mitaka jobs 15:09:28 dmsimard, as noted in trello card, we'll at first manually create current-passed-ci pointing to trunk 15:09:37 dmsimard, yes, that was next question :) 15:09:54 apevec: wait what 15:10:00 dmsimard, I think I saw current jobs use centos7-liberty already 15:10:25 dmsimard, lemme express myself in bash :) 15:10:25 apevec: there'll be current-passed-ci in centos7-liberty and one in trunk right 15:10:41 dmsimard, yeah, but we have current users already 15:10:52 e.g. openstack puppet upstream CI 15:11:07 using centos7-liberty/current-passed-ci (I hope they do!) 15:11:17 puppet CI uses current-passed-ci 15:11:18 (vs /current/) 15:11:20 cool 15:11:23 not sure if it uses centos7-liberty 15:11:24 apevec: they do 15:11:34 EmilienM, ^ 15:11:37 it uses centos7-liberty 15:11:41 excellent 15:11:41 good 15:11:58 he might want to have tests for mitaka too but let's chat with him later about that 15:12:18 ya, I wonder about how that will work... 15:12:22 mitaka could wait final release 15:12:46 dmsimard, so my idea is to keep centos7-liberyt/current-passed-ci -> 86/41/864181e522efefd96f367e3174a2a0e74123532e_764a3c59 15:13:05 i.e. latest from Sep 28 15:13:14 dmsimard, that was manually promoted right? 15:13:23 trown: gate against centos7-liberty/current-passed-ci in the stable/liberty branches of the puppet modules and then master against mitaka ? 15:13:30 dmsimard: we have a packstack job automatically updating that now? 15:13:32 apevec: automatically manually promoted 15:13:34 err wrong symlink 15:13:38 apevec, here, sorry, got lost in doc 15:13:42 apevec: as in, I manually promoted it with the promote script :p 15:13:58 dmsimard: ah ya, you could have a different acceptance test on the stable/liberty branch 15:14:10 I'll chat with EmilienM later 15:14:22 centos7-liberyt/current-passed-ci -> ../../../centos-master/86/41/864181e522efefd96f367e3174a2a0e74123532e_764a3c59 15:14:24 apevec: also yeah, that build from sep28 is good 15:14:46 apevec: only problem EmilienM reported was the selinux issue and o-s is from the common repo 15:14:48 until we have PASS using new liberty CI job 15:14:59 yep, new version is in -testing 15:15:48 dmsimard: what's up 15:16:14 EmilienM, we're switching centos7-liberty to actually build from stable/liberty 15:16:31 which was brached with RC1s 15:16:35 branched even 15:16:51 so we're taking care not to break your CI 15:17:54 ok, time to write down actions 15:19:01 #action dmsimard to ensure khaleesi/jenkins runs off centos7-libert 15:19:19 #action apevec/jpena switch centos7-liberty keeping Trunk current-passed-ci 15:19:28 oh wait, that *aas thing 15:19:56 EmilienM: do you have a stable/liberty branch yet ? 15:19:58 #action derekh to review https://review.gerrithub.io/248726 15:20:00 I will make sure the rdo-manager job will use that too 15:20:16 (ping me if needed, I'm getting side-tracked internally) 15:20:19 derekh, ^ we need that to fix version dep between neutron and *aas 15:20:24 dmsimard: no 15:20:36 dmsimard: we are actually waiting from you and UCA to provide stable packaging. 15:20:58 that's next item on agenda :) 15:21:07 (rc1 builds) 15:21:09 apevec: ack, will do 15:21:45 EmilienM: ok, when you create the stable/liberty branches, you'll want to keep gating against our centos7-liberty/current-passed-ci repo but the master branch will need to gate againsts centos7/current-passed-ci which will be mitaka 15:22:56 #action dmsimard to create the mitaka jenkins CI 15:23:29 re. rpm-liberty branches: we'll create them as late as possible 15:23:52 i.e. only when first incompatbile upstream change happens 15:24:01 new binary etc 15:25:01 apevec: rpm-liberty or rdo-liberty? 15:25:07 rpm-liberty 15:25:28 that's delorean spec for tracking stable/liberty 15:25:40 rdo-liberty is distgit for building packages in Koji 15:25:47 for those not in Fedora 15:26:42 aack 15:26:42 maybe I should've picked better name for distgit branch, suggestions welcome! 15:27:08 no, it's just sickness confusing my mind 15:27:33 next topic? 15:27:36 but it is confusing, I just could get better name :) 15:27:43 could NOT 15:27:48 jpena, yes 15:27:58 #topic RC1 in Rawhide/CBS cloud7-liberty TODAY Sep 30 15:28:06 #link https://trello.com/c/GPqDlVLs/63-liberty-rc1-rpms 15:28:15 apevec: your turn 15:28:47 right, so optimistic goal is to have all RC1 rebases in Rawhide and CBS Liberty today 15:28:50 apevec, there's bot r{pm,do}-liberty? 15:28:54 *both 15:28:55 now you tell me what's missing :) 15:29:03 jruzicka, yes, see above :) 15:29:09 * jruzicka facepalms 15:29:44 nvm, I'll get it in time :-p 15:29:57 apevec: ack 15:30:00 re. missing - checklists are in https://trello.com/c/GPqDlVLs/63-liberty-rc1-rpms 15:30:15 today finishes at 12am PDT ;) 15:30:29 number80, can you do RC1 for all storage services (glance, cinder etc) ? 15:30:34 yes 15:30:51 btw what is that aodh thing? 15:31:29 apevec: ceilometer extracted the alarm service in a separate project 15:31:44 new ceilometer tradition: a new service per release 15:31:49 wow spin-off craze continues 15:32:02 well, it all started from Nova 15:32:25 I'm waiting ceilometer to take over the whole openstack project 15:32:46 http://annawrites.com/blog/wp-content/uploads/2013/08/trouble-with-tribbles.jpeg 15:32:54 and then... it's gonna rename itself 15:32:56 lol 15:32:58 * elmiko chuckles 15:33:13 back to business gentlemen :) 15:33:23 * jruzicka looking very serious 15:33:43 anything else to discuss about RC1 in Rawhide? 15:33:48 yeah, let's distribute rc1 builds, I'll be adding @name 15:33:52 in the checklists 15:34:12 number80, ceilo is yours too or we have new maintainer? 15:34:38 trove rc1: vkmc ? 15:34:43 apevec: we have maintainer but for initial import, it's simpler that I do it 15:34:54 vkmc: ^ 15:35:11 sure 15:35:16 (aodh is not in fedora dist-git) 15:35:36 rhel osp? 15:35:40 ihrachys, can you do neutron RC1 in Rawhide? 15:35:44 vkmc, no, Rawhide 15:35:51 this is Liberty RC1 15:35:56 apevec, k, thanks 15:36:00 so services will be in rawhide? 15:36:35 I thought we were only doing clients and deps in fedora 15:36:43 trown, those which are already in Fedora 15:36:48 apevec: rawhide? really? 15:37:04 I thought we switch to rpm-liberty? 15:37:05 rdo-liberty, sorry 15:37:08 ah ok, so just not new stuff 15:37:26 ihrachys, yes, but not yet for those existing in Fedora 15:37:35 we'll rebase them then remove :) 15:37:41 how silly is that? 15:37:46 hehe 15:37:47 apevec: why 15:37:58 what's going on? who are all those people? 15:38:12 ihrachys, well, you can do RC1 rebase only in rdo-liberty 15:38:46 on my way, I presume. I don't build packages, right? just rebase 15:38:48 until we're ready to officially remove openstack-* I'll keep Fedora master in sync 15:38:53 ihrachys, yep 15:39:10 I'll take care of CBS builds once I see rebase in distgit 15:39:29 sick 15:39:43 yep that's me 15:39:46 * ihrachys on rc1 for rdo-liberty 15:40:12 next Heat: zaneb ryansb - can anyone of you do RC1 rebase today? 15:40:18 if not let me know! 15:40:34 Sahara - elmiko ? 15:40:47 ah no egafford ^ 15:40:53 do we need a rebase of sahara as well? 15:41:05 yes, all services we currently have 15:41:18 k, i'll talk with egafford 15:41:30 thanks 15:41:35 i'm not sure if we've cut the upstream rc1, i *think* we have 15:41:51 I think I saw it, lemme check 15:42:08 yea, it's up 15:42:17 https://launchpad.net/sahara/liberty/liberty-rc1/+download/sahara-3.0.0.0rc1.tar.gz 15:42:27 apevec: Hi there. 15:42:37 * elmiko waves at egafford 15:42:58 * egafford waves back. 15:43:34 anything else for RC1? 15:44:00 Heat 15:44:03 Ironic 15:44:17 who is the maintainer for Ironic? 15:44:21 and some clients 15:44:37 trown, rdoinfo says: - project: ironic 15:44:38 conf: core 15:44:38 maintainers: 15:44:38 - athomas@redhat.com 15:44:46 which I suspect is not accurate? 15:44:59 ya, that I can take that over 15:45:16 trown, please send rdoinfo PR 15:45:20 will do 15:45:48 trown: check the clients too 15:45:55 #action trown send PR to take over maintenance of Ironic 15:46:11 quite ironic, eh 15:46:48 ok, re. Heat I'll ping ryansb / zaneb later 15:47:18 #action apevec to ping missing mainters for RC1 rebases 15:47:39 ryansb is so good at rebases 15:48:01 lol 15:48:02 zaneb: good occasion to get better ;) 15:48:02 zaneb, my thinking as well :) 15:48:21 apevec: so how do I bump? rdopkg new-version apparently does not behave from rdo-liberty 15:48:34 jruzicka, ^ fix it :) 15:48:54 ihrachys, that's why I did rebase on master ;) 15:49:10 ihrachys, just rename it temp locally to "master" 15:49:12 apevec: that's bad excuse, especially for *aas that are not in fedora 15:49:13 to make rdopkg happy 15:49:28 rdopkg is easy to cheat 15:50:35 ihrachys, let jruzicka know how it breaks 15:50:50 jruzicka: reminds me we need a switch for projects that have no patches 15:51:12 (--no-patches-dont-ask-for-a-branch) 15:51:20 and add issue in https://github.com/redhat-openstack/rdopkg/issues/ 15:51:34 I already did ^^ 15:51:42 one week ago 15:52:00 number80, next are ping/bribe/send patch to jruzicka :) 15:52:08 whatever you prefer 15:52:36 we could make tooling topic for the next meeting 15:52:51 to collect RFE ideas and set priorities 15:52:55 jruzicka, ^ ? 15:52:56 yup 15:53:11 ok, getting off topic, let's move on 15:53:15 jpena, next please! 15:53:24 let's go 15:53:35 #topic Package needs version bump 15:53:43 oh yes 15:53:54 no patches branch, that's been on the table for quite some time 15:53:57 I think this topic was raised by chandankumar 15:54:33 * apevec looks 15:55:00 chandankumar is not around, but yeah that topic is clear, we need those bumps 15:55:19 os-brick is reviewed? 15:55:37 no, I'm working on it, number80 is reviewing 15:55:40 what is falcon? 15:55:55 wtf? 15:56:45 it's been built a month ago ... 15:56:45 I assume it is python-falcon 15:56:47 it's updated in Rawhide, I'll check CBS 15:57:21 yeah, needs update in cloud7-common 15:58:30 designateclient update - ihrachys ? 15:58:48 NB clients do stay in Fedora 15:58:56 apevec: this one is vkmc's 15:59:04 yeah ^ 15:59:10 ok 15:59:31 please add yourself as maintainers: in rdoinfo 15:59:31 apevec: meh. I think I will start to search for a replacement for myself in packaging world. I am depressed by it. 16:00:22 ihrachys, sorry to hear that, but anyone you recommend will be welcome 16:00:55 apevec: I just fail to keep up with all packages I got to maintain. 16:01:14 ihrachys, that does sound like too many packages, then ;) 16:01:16 those clients, I completely forgot about them. and I also have python-networking-* 16:01:52 jruzicka: or maybe there's too much process around RDO 16:02:30 ihrachys, lolno 16:02:44 there's too much change but that's unevitable 16:02:45 ihrachys, jruzicka is hard at working automating all that 16:03:07 few more years to stabilise, automate and mature, then you won't even know there's a process :-p 16:03:21 well, I understand the concern and I'd like to adress it but not the right time :( 16:03:21 :) 16:03:38 (but yes, automation is the answer) 16:03:53 let's finish the meeting first 16:03:55 yes, yes, you'll all get fired once I finish. 16:03:57 16:04:10 let's move on then 16:04:19 jruzicka, no, we'll get to debug your toolz 16:04:25 #topic New Package python-reno 16:04:33 apevec, that should be oh so pleasant :) 16:04:45 jpena: this is no requirements 16:04:46 chandankumar has started the review, https://bugzilla.redhat.com/show_bug.cgi?id=1267496 16:04:55 ah automated RElNotes 16:05:07 this will be used for upstream stable relnotes 16:05:17 so it's needed, isn't it? 16:05:19 and we should use it in our automation for stable updates 16:05:21 yes! 16:05:26 cool 16:05:32 btw, can we make a rule that every single review does not require a topic? 16:05:48 (or we'll end up with 3h meetings) 16:05:48 number80, ack - unless it's problematic 16:05:57 *mods* 16:06:14 but this was good to point out, as part of automation topic 16:06:18 yes 16:06:19 (which was offtopic :) 16:06:23 anyway 16:06:56 same for the next topic about SCM requests 16:07:14 that's part of normal procedure, nothing to discuss JFDI 16:07:22 +1 16:07:31 ok, nothing else to discuss about python-reno or SCM requests... We're almost there 16:07:37 yes 16:07:46 #topic chair rotation for next meeting 16:07:53 any volunteer? 16:07:55 I will take it 16:07:59 THANKS! 16:08:01 amen 16:08:10 #action trown to chair next meeting 16:08:19 thanks trown ;) 16:08:27 #topic open floor 16:08:28 thanks jpena for chairing today 16:08:34 +2 16:08:39 +V 16:08:48 Merge! 16:08:59 it's good to see some rotation 16:09:04 i'm curious about the state of barbican 16:09:37 is it still under review? 16:09:45 I have rdo-manager manually installing via delorean liberty packages, working on getting the khaleesi job working 16:09:51 i *thought* we had a good packages build 16:10:14 elmiko, it is in delorean trunk, yes 16:10:23 and builds there 16:10:28 trown, good news! 16:10:34 btw, barbican is failing on centos7-kilo 16:10:44 apevec: does that mean it's slated for release in rdo? 16:10:51 jpena: well that stinks =( 16:11:01 elmiko: http://trunk.rdoproject.org/kilo/centos7/64/67/6467361a5d5bd78203c70b3ac174a04870f17bbb_cfc0615c/rpmbuild.log 16:11:10 trown, dmsimard - would be good to include rdo-mgr to vote in delorean CI promotion job 16:11:14 jpena: thanks, i'll take a look 16:11:34 apevec: ya that would be the goal after getting a job up and passing 16:11:40 apevec: we're not quite there yet 16:11:47 apevec: it's in the todo, though 16:12:09 elmiko, if review has been done, then yes 16:12:27 apevec: ok, thanks 16:13:39 elmiko so looks like number80 finished pkg review https://bugzilla.redhat.com/show_bug.cgi?id=1190269 16:13:56 yea, i thought we had finished that portion 16:14:07 apevec, elmiko it's been imported 16:14:07 elmiko, next step is for Greg to do SCM request 16:14:18 number80, oh how? 16:14:32 I don't se SCM request 16:14:53 xaeth_afk: ^^ 16:14:57 review done Sep1 16:15:01 apevec: in github only 16:15:04 ping Sep 14 16:15:09 today Sep 30 16:15:20 bad email filtering? 16:15:28 BZ => spam 16:15:33 i'll follow up with xaeth (Greg Swift) about the scm req. 16:15:53 thanks 16:16:06 are we still in open floor, or should we end meeting? 16:16:06 #action elmiko follow up with xaeth (Greg Swift) about the scm req for openstack-barbican 16:16:17 uhm yes, we're overtime 16:16:20 so, if there is nothing left, we will end the meeting in 3... 16:16:21 jpena, let's close 16:16:31 sorry, but thanks for answering my questions =) 16:16:39 #endmeeting