15:00:38 <jpena> #startmeeting RDO meeting (2016-02-03)
15:00:38 <zodbot> Meeting started Wed Feb  3 15:00:38 2016 UTC.  The chair is jpena. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:38 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:38 <zodbot> The meeting name has been set to 'rdo_meeting_(2016-02-03)'
15:00:42 <jschlueter> o/
15:00:48 <elmiko> o/
15:01:00 <jpena> #chair jschlueter elmiko trown
15:01:00 <zodbot> Current chairs: elmiko jpena jschlueter trown
15:01:04 <jpena> #topic roll call
15:01:26 <trown> o/
15:01:30 <imcsk8> o/
15:01:38 <chandankumar> o/
15:01:41 <jpena> #chair imcsk8
15:01:41 <zodbot> Current chairs: elmiko imcsk8 jpena jschlueter trown
15:02:06 <mflobo> o/
15:02:15 <jpena> #chair mflobo
15:02:15 <zodbot> Current chairs: elmiko imcsk8 jpena jschlueter mflobo trown
15:02:25 <chandankumar> #chair chandankumar
15:02:28 <jpena> #chair chandankumar
15:02:28 <zodbot> Current chairs: chandankumar elmiko imcsk8 jpena jschlueter mflobo trown
15:02:51 <jpena> apevec, number80, you around?
15:04:02 <jpena> ok, we'll start without them and they'll catch up later
15:04:08 <jpena> #topic Packaging Delorean
15:04:11 <apevec> o/
15:04:15 <jpena> #chair apevec
15:04:15 <zodbot> Current chairs: apevec chandankumar elmiko imcsk8 jpena jschlueter mflobo trown
15:04:19 <jpena> just in time :)
15:04:36 <apevec> yes, it's time to package delorean!
15:04:58 <jpena> so we are planning to create a Delorean package. It doesn't make a lot of sense not to package a packaging tool
15:04:59 <apevec> we just need to declare what do we want to have in 0.1 or 1.0
15:05:22 <apevec> until now Delorean didn't have any release yet!
15:05:35 <trown> I put https://review.gerrithub.io/#/c/254505 there, but I would not block release on it. it is just a feature I have wanted since starting to work on delorean
15:05:36 <apevec> so maybe 0.1 asap
15:05:45 <trown> +1 to 0.1
15:05:54 <jpena> also +1 to 0.1
15:05:57 <chandankumar> +1
15:06:09 <apevec> trown, I have that review on my list
15:06:20 <apevec> ok so 0.1 it will be
15:06:30 <trown> apevec: still have to solve jpena's concern
15:06:33 <apevec> there's one more feature open from flepied
15:06:33 <jpena> #agreed The first Delorean release will be 0.1
15:06:55 <apevec> what is jpena's concern?
15:07:13 <trown> gnocchi package is actually a good example of no explicit epoch, but requires on subpackages
15:07:13 <jpena> I'm doing some test package, so far I've found a couple issues, one of them specifically with python-sh
15:07:26 <apevec> ah yes, we need patched sh
15:07:46 <apevec> unless upstream merged Derek's patch
15:08:13 <jpena> apevec: it's a different issue. We have Derek's patch, and the fact that running sh.env() works in sh 1.11 (from pypi) but not in 1.08 (from Fedora package)
15:08:32 <jpena> I'm preparing a workaround for delorean, so it works on both
15:08:32 <apevec> .whoowns python-sh
15:08:32 <zodbot> apevec: grover
15:08:52 <jpena> btw, do we expect to support Delorean running on CentOS?
15:09:09 <apevec> jpena, let's talk to python-sh maintainers
15:09:21 <jpena> apevec: ack
15:09:24 <apevec> ralph from fedora infra is co-maint
15:10:15 <apevec> jpena, yes, delorean should run on centos
15:10:34 <apevec> what's breaking on centos?
15:10:48 <jpena> I'd expect the python-sh package is not any newer
15:11:15 <apevec> it's the same 1.08 in epel7
15:11:34 <apevec> but I don't see why maintainers wouldn't want to update it
15:11:45 <apevec> it's just been neglectware
15:11:59 <jpena> ok then
15:12:13 <jpena> #action jpena to follow-up with python-sh maintainers on version bump to 1.11
15:12:26 <apevec> jpena, best to prepare patch and put it in bz, to make it easy for them :)
15:12:41 <apevec> or even ask for commit in pkgdb
15:12:59 <jpena> mmm, that might work
15:13:01 <jpena> #undo
15:13:01 <zodbot> Removing item from minutes: ACTION by jpena at 15:12:13 : jpena to follow-up with python-sh maintainers on version bump to 1.11
15:13:25 <jpena> #action jpena to make sure python-sh is bumped to 1.11 and it includes Derek's patch
15:13:55 <apevec> #info Derek's sh patch == https://github.com/amoffat/sh/pull/237
15:13:59 <apevec> ^  not merged yet
15:15:19 <jpena> ok, I'll try to have a version to test later this week. Anything else to discuss here?
15:16:33 <trown> nice
15:17:23 <apevec> ok, for 0.1 we need topic:delorean-packaging
15:17:32 <apevec> Epoch: <timestamp>
15:17:50 <apevec> and Fred's --recheck and --status
15:18:15 <apevec> and yes, rdoinfo tags support from me (to be sent today)
15:18:24 <apevec> anything else?
15:18:52 <apevec> there are few older patches, but all need to be rebased so I'm ignoring them for now
15:19:15 <trown> oh ya, recheck would be great
15:20:01 <jpena> I think that's all
15:20:33 <jpena> moving on?
15:22:01 <apevec> yes
15:22:06 <jpena> #topic Migrate the f22 Delorean worker to f23
15:22:35 <jpena> So we spoke about it last week I think. I've started tests on a separate VM, it looks good so far
15:22:50 <jpena> http://209.132.178.4/f23/status_report.html
15:22:56 <apevec> host is still f22 ?
15:23:09 <jpena> yes, still f22
15:23:29 <jpena> I'm running delorean locally on my laptop with f23 and it goes just fine anyway
15:23:31 <apevec> ok, let's plan c7 for the next rebuild
15:23:56 <apevec> btw, what would be good timing for Delorean rebuild, using puppet-delorean?
15:24:21 <jpena> we did the last a week after summit (it's usually a quiet time)
15:24:35 <trown> hmm... we have a window nowish, but after that, I agree after summit
15:25:08 <apevec> yeah, after summit looks good
15:25:15 <trown> actually nowish is bad if something goes wrong since so much upstream is relying on delorean
15:25:48 <apevec> yes, now is probably not a good idea
15:26:00 <trown> I was thinking just in terms of RDO test days
15:26:00 <jpena> actually, I'm not going to Austin so we could do it *during* summit :)
15:26:39 <apevec> f22 eol is few weeks after f24 ga in June, so we're good to stay on it for a while
15:26:47 <apevec> for host
15:26:59 <apevec> I'd move replace f22 worker w/ f23 asap
15:27:27 <apevec> jpena, during summit is even better, provided you keep old running
15:27:30 <jpena> right, so once I finish all my checks, the next step will be to stop the f22 worker and create the f23 one in the Delorean instance
15:27:32 <apevec> then just switch IP
15:28:02 <jpena> apevec: yes, that's always the plan, only switch IP once the new one is ready
15:28:04 <apevec> jpena, in anycase, time to trello it, with a checklist
15:28:20 <jpena> ack
15:28:30 <flepied> I have a delorean instance running on centos if you need it
15:28:54 <jpena> flepied: cool! Any gotchas?
15:28:55 <apevec> jpena, that's a good point ^
15:29:18 <apevec> jpena, maybe we should consider moving to the minicloud where rpmfactory is running?
15:29:28 <apevec> flepied, is that where you have your Delorean?
15:30:20 <jpena> apevec: if we have resources, sure!
15:30:25 <flepied> apevec: yes http://46.231.133.253/delorean/status_report.html
15:31:38 <apevec> flepied, can you give access to jpena for testing there?
15:32:15 <flepied> apevec: yes but we need to coordinate as I'm experimeting patches there
15:32:40 <apevec> flepied, I mean cloud access, so he can setup new production delorean
15:33:28 <trown> is the "minicloud" able to handle the traffic load that our current delorean gets?
15:33:44 <apevec> that's what we need to test :)
15:34:22 <flepied> apevec: yes it can be done. I have an ansible script to reprovision a delorean instance when needed if you want.
15:34:26 <apevec> flepied, what size of internet pipe do those machines have?
15:34:47 <apevec> flepied, heh, and jpena just finished puppet-delorean ;)
15:34:58 <apevec> cfg warz...
15:35:29 <flepied> apevec: I don't know the details but it's a good network connection. I can get the details if you need.
15:36:07 <flepied> apevec: what do we do with the bootstraping issue?
15:37:13 <apevec> flepied, yeah, sphinx/debcollector... do we have more or only that one?
15:37:34 <flepied> apevec: I don't think so
15:38:10 <apevec> flepied, what about providing explicitly a list of packages which need to be built w/ bootstrap macro enabled?
15:38:24 <apevec> to avoid parsing spec
15:39:15 <apevec> btw tl;dr for others: we have build dep loop
15:39:16 <flepied> apevec: the problem like I said is to compute the right order we need to parse the spec files
15:39:57 <apevec> flepied, right and you ignore those explicitly specified and build dep first
15:40:02 <apevec> s/dep/them/ !
15:40:13 <apevec> e.g. python-oslo-sphxin with bootstrap 1
15:40:29 <apevec> after that you can compute order from the rest of the specs
15:40:54 <flepied> apevec: ok we can try something like that
15:41:23 <apevec> so this would one more Delorean fix before tagging 0.1 ?
15:42:00 <flepied> apevec: oh no I don't know. what's the target of 0.1?
15:42:20 <apevec> we didn't set ETA but soon
15:42:36 <flepied> I mean what's the objective?
15:42:39 <apevec> it was first topic today, we identified few patches to merge
15:42:44 <apevec> flepied, to get it packaged
15:43:20 <flepied> ok no needed to wait for this cycle issue if you need a package soon
15:43:34 <apevec> ok
15:43:53 <apevec> but knowing you, there'll be patch review ready in no time ;)
15:44:10 <apevec> jpena, sorry we went OT  !
15:44:27 <jpena> np, but we should move on. We have more topics and only 15 minutes to go
15:44:27 <apevec> put us back on track
15:44:41 <jpena> #topic Cleanup trello
15:44:52 <jpena> not sure who added this to the agenda
15:44:59 <apevec> that was number80's but he's on the bus to Brno
15:45:00 <dmsimard> number80: ^
15:45:01 <trown> number80 has been rocking that
15:45:12 <apevec> ack to all what he proposed:
15:45:17 <apevec> obsolete cards => delete
15:45:21 <apevec> cards without feedback => marked for deletion
15:45:25 <apevec> merge redundant cards
15:45:57 <jpena> ack. Who's going to do the effort?
15:46:01 <apevec> and yes, number80 already started pruning,
15:46:04 <apevec> I'll join that
15:46:16 <apevec> #action apevec to join trello prunning
15:46:29 <flepied> btw if you want the trello bot for this chan, EmilienM is running one for freenode
15:46:31 <apevec> #undo
15:46:31 <zodbot> Removing item from minutes: ACTION by apevec at 15:46:16 : apevec to join trello prunning
15:46:36 <apevec> #action apevec to join RDO trello pruning
15:46:49 <apevec> what is that bot doing?
15:46:59 <EmilienM> telling all actions on a trello board
15:47:10 <EmilienM> go on #rdo-puppet, you'll see
15:47:16 <dmsimard> apevec: abstract: http://paste.openstack.org/show/485861/
15:47:17 <apevec> ok, I'll have a look
15:47:24 <EmilienM> every action on a board is sent on IRC
15:47:30 <EmilienM> "bob commented on XX"
15:47:36 <EmilienM> "dan added bob to XX"
15:47:37 <EmilienM> etc
15:47:42 <apevec> hmm, that might be a bit too noisy
15:47:52 <EmilienM> yeah but I'm sure we can adjust it
15:47:54 <trown> not sure our trello is all that noisy :)
15:47:56 <apevec> but lemme watch it few days in #rdo-puppet to make up my mind
15:48:17 <jpena> it's usually not that much, although there are some noisy moments
15:48:34 <EmilienM> I'm sure we can add filters to the code
15:48:42 <EmilienM> so we can only see new/inprogress/close things
15:48:56 <apevec> ok, let's put that on the agenda next week
15:48:56 <jpena> that'd be great, I think
15:49:44 <jpena> ok, so let's move on
15:49:52 <jpena> #topic kilo 2015.1.3 rebase
15:50:18 <jpena> I think number80 added this one, too
15:50:20 <apevec> that's also number80 - afaik he did it and put on testing
15:50:55 <apevec> #action apevec send call-for-testing 2015.1.3 on rdo-list
15:51:20 <number80> only missing horizon for the rebase but needed to check w/ mrunge
15:51:43 <apevec> #action apevec to ping mrunge about 2015.1.3 rebase
15:51:46 <mrunge> number80, sorry, I what rebase?
15:51:51 <apevec> number80, or you grab him in Brno
15:51:56 <apevec> ah there he is
15:51:56 <number80> ack
15:52:00 * mrunge runs
15:52:13 <mrunge> :P
15:52:35 <apevec> mrunge, 2015.1.3 i.e. f23 branch for now
15:52:39 <apevec> (Kilo)
15:52:42 <mrunge> 2015.1.3 rdo?
15:52:46 <apevec> yes
15:52:55 <apevec> #undo
15:52:55 <zodbot> Removing item from minutes: ACTION by apevec at 15:51:43 : apevec to ping mrunge about 2015.1.3 rebase
15:53:03 <mrunge> sigh
15:53:45 <mrunge> kilo per se does not support django-1.8
15:53:48 <apevec> number80, anything else for 2015.1.3 ?
15:54:22 <apevec> mrunge, didn't you patch it in rdo?
15:54:50 <mrunge> yes, I did that, but honestly, I don't know the state in rdo
15:55:18 <apevec> rdo kilo is still f23 branch distgit
15:55:38 <mrunge> oh, ack. makes things way easier
15:55:39 <apevec> we just rebuild it from there in CBS
15:55:44 <mrunge> I can't
15:55:56 <mrunge> but I'll ping number80
15:56:10 <apevec> yep
15:56:30 <cdearborn> Hey folks, wondering if anyone knows how to determine which controller node is acting as the VRRP master in a 3 controller HA config
15:56:47 <apevec> mrunge, btw, you can apply for CBS account now - ask number80 for details
15:56:53 <jpena> cdearborn: please wait a few minutes, we are in the middle of a meeting
15:57:07 <apevec> there's accounts.centos.org
15:57:07 <mrunge> apevec, don't really know if I should
15:57:13 <number80> mrunge: we can sit down or do it half way, rebase the patch branch for me
15:57:13 <apevec> mrunge, up to you
15:57:23 <NelsonPR> cdearborn, the one who pings instances from router
15:57:25 <number80> (and i'll finish)
15:57:43 <mrunge> ack number80 , let's talk about this in Brno
15:58:03 <number80> yup, no pressure :)
15:58:40 <apevec> ok, done w/ rebase
15:58:49 <apevec> ?
15:59:06 <apevec> #topic open floor
15:59:18 <jpena> Any volunteer to chair the next meeting?
15:59:24 <apevec> flepied, re. your ansible for delorean - please check https://github.com/javierpena/puppet-delorean
15:59:48 <flepied> apevec: ok but I'm not a puppet guy ;-)
15:59:51 <apevec> flepied, do you have your playbook published ?
15:59:52 <number80> flepied would be perfect as a chair
15:59:58 * number80 runs
16:00:11 <apevec> jpena, flepied, let's decide which one to continue using
16:00:20 <apevec> maintaining both is probably a waste
16:00:32 <flepied> number80: I'm chairing enough meetings, thx but no.
16:00:39 <number80> :)
16:00:41 <trown> :)
16:01:02 <apevec> if no volunteer, I'll take it
16:01:19 <number80> ack, i'll take the following week
16:01:19 <chandankumar> apevec, i can volunteer for next meeting
16:01:41 <apevec> chandankumar, you get the 3rd :)
16:01:51 <apevec> thanks everyone!
16:01:51 <chandankumar> ack
16:01:55 <number80> o/
16:02:07 <jpena> if there's nothing else to discuss, we're out of time...
16:02:14 <jpena> 3
16:02:15 <jpena> 2
16:02:22 <jpena> 1...
16:02:25 <jpena> #endmeeting