rdo
MINUTES
15:01:06 <apevec> #startmeeting RDO meeting (2015-1-04)
15:01:06 <zodbot> Meeting started Wed Nov  4 15:01:06 2015 UTC.  The chair is apevec. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:06 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:01:26 <apevec> argh typo in title :)
15:01:31 <apevec> #chair trown
15:01:31 <zodbot> Current chairs: apevec trown
15:01:43 <apevec> #topic rollcall
15:01:45 <apevec> o/
15:01:49 <jpena> o/
15:01:51 <rbowen> !o!
15:01:53 <apevec> #info agenda at https://etherpad.openstack.org/p/RDO-Packaging
15:01:55 <dmsimard> \o
15:02:22 <number80> o/
15:05:01 <apevec> ok let's start
15:05:03 <apevec> #topic Mitaka Summit reports
15:05:19 <apevec> jpena, number80 - can you do quick summary?
15:05:32 <apevec> More details can be rdo-list post/blog
15:05:53 <jpena> sure. I was in the release mgmt session. The highlights were:
15:05:55 <apevec> what should we take into account for RDO Mitaka?
15:06:06 <jpena> Git tags will be used for versioning instead of setup.cfg
15:06:58 <apevec> yep, ^ that applies to stable/liberty too
15:07:28 <jpena> Some discussion on the "drop synced milestones" item. So there won't be a fixed day for Milestone 1,... instead there will be "suggested dates", which I understand as one week or so where projects will be releasing their versions
15:08:08 <dmsimard> I remember us agreeing on figuring out a way to make it easy to pull in patches (either between milestones or if an operator/vendor wants to build a package with their own patches), say, perhaps a jinja template that iterates across the patches in a directory or something like that
15:08:14 <jpena> There were some proposals not to tag betas at all. I stated that as a problem for distros (no way to have Beta X RDO Mitaka unless you chase each project individually)
15:09:04 <jpena> Also, stable branches for Liberty will happen on demand, without a synchronized release date
15:09:11 <apevec> jpena, yeah, no tag means no release
15:09:19 <rbowen> Note that in https://wiki.openstack.org/wiki/Mitaka_Release_Schedule there's now date ranges, not fixed dates.
15:09:38 <number80> which is fine with me
15:09:53 <jpena> unless some project slips the release range
15:10:05 <rbowen> Do we want to do test days before that, or after that?
15:10:24 <rbowen> Or both, I suppose, is another option, if we do them more frequently.
15:10:28 <apevec> rbowen, we should aim +1 week when tags are pushed
15:10:47 <apevec> with moar automation it should be doable
15:11:32 <apevec> dmsimard, we don't need a template, rdopkg could pull patches, we just need some tag as a base
15:11:56 <dmsimard> apevec: aye but I doubt SUSE uses rdopkg :p
15:11:58 <apevec> but let's first get automated distgit builds on tags
15:12:07 <trown> I think dmsimard is talking about the packaging-rpm session
15:12:08 <dmsimard> and we're converging on upstream /openstack rpm repos now I think
15:12:21 <apevec> ah that's next subtopic
15:12:32 <number80> yes, waiting for jpena to finish :)
15:12:32 <dmsimard> doh, sorry
15:12:38 <jpena> :)
15:12:39 <dmsimard> still jetlagged to death
15:12:44 <jpena> that was mostly it
15:12:53 <apevec> thanks!
15:12:59 <number80> thanks for replacing me on such short notice!
15:13:26 <number80> in // of the stable mgmt session, we had the rpm packaging fishbowl followed by a workshop
15:13:58 <number80> highlights were: 1. we agreed to continue the common packaging goal but accelerate the push of new spec files
15:14:18 <Humbedooh> rbowen: btw, I have cracked the Japanese syllable stress rules! stress is on the third last syllable, so mitaka was correctly pronounced ;)
15:14:24 <number80> 2. to reach that goal, we decided to add more core contributors (I nominated apevec and jruzicka)
15:14:38 <jruzicka> oh yes, I need core
15:14:50 <rbowen> Good to know.
15:14:52 <number80> 3. we managed to have a hallway agreement on pushing delorean for build automation upstream
15:14:58 <jruzicka> to release pymod2pkg https://review.openstack.org/#/c/241221/
15:15:20 <trown> number80: cool, I did not know about 3, that is awesome
15:15:43 <number80> trown: hallway discussion with Dirk and Igor about it
15:15:45 <dmsimard> re 3.: it was unclear where that system would live I think, we discussed either ci centos infra or openstack-infra (for gating)
15:16:03 <number80> btw, thanks to Derek and trown for attending the RPM packaging session
15:16:17 <trown> and dmsimard
15:16:25 <dmsimard> I don't count :p
15:16:52 <number80> both packaging groups (RPM and debian) attended each other sessions, and we found (not a surprise to me) that we have very similar issues and that we're at the same stage
15:17:12 <number80> dmsimard: you were compelled to attend!
15:17:41 <number80> Goal is to have some deliverables for Mitaka.
15:18:01 <dmsimard> I'm glad that the SUSE folks are very open to collaborating on this
15:18:07 <number80> We also had an informal hackfest on friday morning to review spec files
15:18:56 <number80> same goes for Mirantis folks
15:19:24 <apevec> ok, lemme try to summarize for the minutes
15:19:36 <number80> This is more interesting for RDO, but goal is at some point RPM packaging project replaces delorean
15:20:18 <apevec> #info release management session highlights - desynchronized Mitaka milestones and stable/liberty point releases
15:20:49 <apevec> #info upstream packaging-rpm get momentum - extend core, deliverables for Mitaka
15:21:21 <apevec> #info move Delorean into upstream infra, replaced by packaging-RPM at some point
15:21:29 <apevec> jpena, number80 ^ good enough?
15:21:49 <jpena> apevec: excellent!
15:21:58 <number80> we're not moving delorean exactly, just reusing delorean tool for upstream packaging
15:22:11 <apevec> ah then
15:22:13 <apevec> #undo
15:22:14 <zodbot> Removing item from minutes: INFO by apevec at 15:21:21 : move Delorean into upstream infra, replaced by packaging-RPM at some point
15:22:21 <apevec> number80, please correct me
15:23:06 <number80> #info use Delorean tool for upstream infra builds, packaging-RPM builds will replace RDO delorean at some point
15:23:32 <number80> that's something we tried to sell but it was not accepted by suse
15:23:35 <apevec> what is "infra builds" ?
15:23:46 <number80> packaging-RPM spec files builds
15:24:25 <number80> all the work we're doing in delorean, fixing specs would happen upstream, and RDO stable builds would derive from then
15:24:34 <EmilienM> apevec, number80: http://logs.openstack.org/58/239258/9/check/gate-puppet-openstack-integration-scenario001-dsvm-centos7/d0ca800/console.html#_2015-11-04_15_03_51_572
15:24:44 <EmilienM> /usr/bin/yum -d 0 -e 0 -y list openstack-trove' returned 1: Error: No matching Packages to list
15:24:46 <EmilienM> using GA repo
15:24:54 <apevec> EmilienM, yeah, not pushed yet
15:25:00 <number80> EmilienM: ack, we'll review that post-meeting
15:25:00 <apevec> also OT :)
15:26:07 <apevec> let's move on
15:26:12 <apevec> #topic RDO meetup
15:26:15 <apevec> rbowen, ^
15:26:16 <rbowen> We had roughly 70 people in attendance for the RDO meetup. I recorded everything, and am working on doing some transcribing. Please blog about your part if you presented, or attended and cared about a part of the conversation, as I'm sure I'll miss details.
15:26:35 <rbowen> The agenda of discussed topics is at https://etherpad.openstack.org/p/rdo-tokyo
15:27:03 <rbowen> We had some folks coming and going, so it was hard to get a count, but it was 70 at one point.
15:27:19 <apevec> #info 70 people at RDO meetup, minutes coming, please blog your views if you were there!
15:27:39 <number80> rbowen: some people told me that they couldn't find the room so we could have gotten slightly more people ;)
15:27:45 <apevec> rbowen, thanks for recording, I'm looking forward to review notes!
15:27:52 <rbowen> Yeah, the room wasn't exactly central.
15:28:10 <apevec> rbowen, get flashing lights next time :)
15:28:23 <rbowen> In Austin, we'll all be in the same building, which will help.
15:28:40 <apevec> "RDO meetup - we're OPEN"
15:28:47 <dmsimard> I thought the lunch was a bit awkward with no tables, I expected some sort of round table or multiple tables. It was all chairs :)
15:28:51 <rbowen> At least, I assume we will - the convention center is pretty huge.
15:28:56 <number80> rbowen: two hours would be nice to have
15:29:11 <trown> ya I think having it on top of lunch was not ideal
15:29:12 <rbowen> So, for Austin we need to start earlier in our quest for a room. There we very slim pickings this time.
15:29:17 <number80> or at least, keep some time for new faces to present themselves
15:29:33 <number80> cloudkitty folks were too shy to speak up :)
15:29:37 <rbowen> We'll also have more time at FOSDEM, but likely a different audience.
15:29:38 <dmsimard> I would have also liked to hear from users and operators more, their experiences - what they like, dislike, would like improved
15:29:50 <number80> (or we're too loud to let new faces to speak up)
15:30:09 <number80> dmsimard: good idea
15:30:21 <rbowen> Yeah, one hour is just not long enough.
15:30:47 <number80> I think that some CERN folks will be present at FOSDEM, they *should* submit a talk (and not just CERN btw)
15:30:50 <rbowen> Anyways, I'll try to get a blog post out this week, and others who spoke are encouraged to blog aobut their piece.
15:30:53 <jschlueter> #chair jschlueter
15:31:01 <number80> #chair jschlueter
15:31:14 <apevec> #chair rbowen number80
15:31:14 <zodbot> Current chairs: apevec number80 rbowen trown
15:31:20 <number80> #chair jschlueter
15:31:20 <zodbot> Current chairs: apevec jschlueter number80 rbowen trown
15:31:21 <apevec> #chair jschlueter
15:31:21 <zodbot> Current chairs: apevec jschlueter number80 rbowen trown
15:31:35 <trown> #chair jpena dmsimard
15:31:35 <zodbot> Current chairs: apevec dmsimard jpena jschlueter number80 rbowen trown
15:31:46 <number80> rbowen: I'll try to write at least a short one
15:32:03 <number80> #action number80 write blog post about summit
15:32:19 <trown> #action trown blog about summit from rdo-manager perspective
15:32:42 <apevec> #action rbowen start earlier our quest for RDO meetup room
15:33:09 <apevec> anything else?
15:33:25 <rbowen> No, I think that's done, until I get through the recording. Thanks.
15:33:36 <apevec> thank you!
15:33:39 <apevec> #topic RDO Mitaka themes
15:34:02 <apevec> this one should derive from the Summit themes
15:34:23 <apevec> I've notice few on upstream list and started opening tasks in trello
15:34:44 <apevec> there are also unfinished from previous cycle
15:34:52 <apevec> e.g.
15:34:55 <apevec> #info python3
15:35:24 <apevec> we have stopped that b/c it python guidelines changed late in Liberty cycle
15:35:32 <apevec> but now should start on that
15:35:42 <number80> yeah, right time to reboot that but at a slower rate so that we could review them properly
15:35:44 <apevec> one issue is switching db driver
15:35:49 <apevec> what else?
15:36:15 <jpena> Fedora 22 not having python 3.5?
15:36:27 <apevec> #info switch to PyMySQL https://trello.com/c/q0VoAYJq/89-migrate-mysql-python-to-pymysql
15:36:30 <number80> yeah, forgot that
15:36:49 <apevec> jpena, yeah, we'll need 2 delorean instances,
15:36:55 <number80> during cross-projects session, everyone agreed to support python35 as default python3 stack
15:36:57 <apevec> one for Fedora stable with py2 only
15:37:06 <apevec> and Rawhide/f24 with py3.5
15:37:23 <apevec> number80, is f24 going to have _only_ py3.5 ?
15:37:29 <apevec> or there'll be still python2.7 ?
15:37:37 <number80> f24 will have both
15:37:54 <Humbedooh> too much still depends on py27 methinks
15:37:54 <apevec> bah, that's silly, so we'll need all that python2-* mess
15:37:57 <number80> but it's time to consider having python35 in CBS
15:38:22 <apevec> number80, let's make it work on Rawhide first
15:38:25 <number80> ack
15:38:32 <apevec> imho python35 from epel will be pain
15:38:34 <jpena> ok, I'll try to include the rawhide worker in tomorrow's delorean rebuild
15:38:42 <apevec> b/c you'd have to rebuild every single python lib
15:38:54 <apevec> jpena, ack
15:39:04 <apevec> action yourself :)
15:39:17 <jpena> #action jpena to include fedora rawhide worker in delorean rebuild
15:39:57 <apevec> number80, do we have python3 trello card ?
15:40:13 <number80> apevec: nope
15:40:24 <number80> I was starting one :_
15:41:34 <apevec> ack, please add links to other cards like pymysql one
15:42:02 <apevec> moving on, another unfinished from L
15:42:19 <apevec> #info -tests subpackages and testdeps / enable %check
15:42:35 <apevec> not much to say, we just need to do it now
15:42:50 <apevec> I'll add card with checklists for tracking that
15:43:13 <apevec> #action apevec add card for tracking  -tests subpackages  / testdeps / enable %check progress
15:43:47 <number80> btw, tagging these card with Next Release label
15:44:21 <apevec> dmsimard, just one CI question - functional tests are now in projects, how will jobs include them?
15:44:49 <apevec> is it just matter of installing them and tempest picks them up?
15:45:06 <EmilienM> apevec, number80: same for Aodh: '/usr/bin/yum -d 0 -e 0 -y list openstack-aodh-common' returned 1: Error: No matching Packages to list -> in GA repo
15:45:15 <number80> ack
15:45:28 <EmilienM> it's blocking our CI to bump to GA and provide stable/liberty
15:45:33 <EmilienM> I thought GA repo would be ready
15:45:38 <EmilienM> any timeframe?
15:45:48 <dmsimard> apevec: what kind of functional tests ? can you link example ?
15:46:21 <dmsimard> Are they atomic in the sense that they only require their own package to run the tests ?
15:46:51 <apevec> e.g. https://github.com/openstack/neutron/tree/master/neutron/tests/functional
15:47:11 <apevec> iiuc those are moved out of tempest source tree ?
15:47:30 <apevec> but let's take this offline or list
15:47:38 <EmilienM> and manila is broken too: http://logs.openstack.org/42/241642/1/check/gate-puppet-manila-puppet-beaker-rspec-dsvm-centos7/ff9e318/logs/manila/api.txt.gz#_2015-11-04_15_33_58_303
15:47:54 <EmilienM> sorry, am I in the middle of a meeting?
15:47:56 <dmsimard> apevec: I have no clue - if these are standalone to the packages, I'd probably include them in the delorean ci gate
15:48:00 <number80> EmilienM: yes :)
15:48:13 <EmilienM> number80: I feel really dumb. sorry for that guys /quit
15:48:30 <number80> EmilienM: you're jetlagged like most of us
15:48:37 <jschlueter> related to ci will we have ci run more than just tempest smoke tests?
15:49:11 <apevec> jschlueter, let's have smoke first :)
15:49:13 <apevec> https://trello.com/c/pFBmc3rk/80-bump-rdo-liberty-ci-tests-from-minimal-to-smoke-tests
15:49:28 <dmsimard> jschlueter: I want to set the bar pretty high for CI - the first target is to have stable smoke tests. We're really close to that.
15:49:31 <jschlueter> apevec: noted ... good goal!
15:49:31 <trown> rdo-manager is running smoke
15:49:40 <dmsimard> trown: are you still skipping tests though ?
15:49:51 <dmsimard> (that's cheating :P)
15:50:15 <jschlueter> dmsimard: skipped tests why is that cheating?
15:50:15 <trown> lol, I think there are a couple skips with BZs
15:50:18 <apevec> half-smoke?
15:50:44 <olap> apevec: ping
15:50:45 <zodbot> olap: Ping with data, please: https://fedoraproject.org/wiki/No_naked_pings
15:50:51 <dmsimard> but yeah anyway, I eventually want to run full tempest and defcore
15:50:54 <apevec> olap, after meeting please
15:51:27 <olap> apevec: could you please approve me in th erdo mailing list?
15:51:30 <olap> apevec: kk
15:51:39 <olap> RDO
15:51:47 <apevec> let's move on, we have few more topics
15:51:47 <jschlueter> +1 on full tempest run
15:51:54 <apevec> #info DLM support
15:52:11 <apevec> I've posted on rdo-list, so this is just FYI - please reply there
15:52:26 <EmilienM> full tempest is not very useful for you I think
15:52:29 <trown> for rdo-manager, I brought it up in tripleo meeting yesterday, so it is on the radar
15:52:34 <EmilienM> in my experience, smoke + some other tests are useful
15:52:38 <apevec> I noticed it on upstream list as important for Mitaka
15:52:41 <EmilienM> they test the whole stack
15:52:51 <dmsimard> EmilienM: not for gating, but before a release
15:52:58 <EmilienM> you don't really need to test negative tests for Nova Aggregate tests
15:53:00 <dmsimard> smoke is fine for gating
15:53:19 <apevec> EmilienM, so there should be extened-smoke tag in tempest?
15:53:33 <EmilienM> apevec: not sure they would do that
15:53:52 <EmilienM> sorry, what are we testing? Packages? or code ?
15:53:53 <apevec> EmilienM, how to document " + some other tests" ?
15:54:09 <EmilienM> if you have specific patches in RDO packages that are not in OpenStack, +1 for Full Tempest run
15:54:33 <EmilienM> if you just want to test packages that are based on upstream only (like does delorean), Smoke + some tests (dashboard because not in smoke), etc
15:54:48 <chandankumar> o/
15:55:13 <apevec> ok, let's move that discussion to rdo-list, dmsimard ?
15:55:22 <dmsimard> sure
15:55:42 <apevec> moving quickly thru next few:
15:55:44 <apevec> #info more automation
15:56:00 <apevec> jruzicka, ^ we'll need more automagic :)
15:56:09 <dmsimard> CI Automation: More and better CI and also auto-promote is on the radar
15:56:20 <number80> and auto-build
15:56:28 <dmsimard> the auto promote job is already there but I want a smoke job before it
15:56:37 <apevec> cool
15:56:56 <jruzicka> always ready for mor automation ;)
15:57:04 <jruzicka> *m04r
15:57:05 <apevec> jruzicka, I'll file some rdopkg RFEs
15:57:16 <jruzicka> apevec, please do ;)
15:57:28 <apevec> #info rdo-manager quickstart
15:57:34 <apevec> trown, ^ ?
15:58:21 <trown> ya I have a working playbook to create an "undercloud" virtual appliance that fits into the khaleesi workflow
15:59:19 <trown> I would like to have that published with a successful promote, and use that for an rdo-manager quickstart
15:59:38 <trown> still quite a bit to do for it, but it is one of my main mitaka goals to polish that up
15:59:49 <apevec> sounds good!
16:00:07 <apevec> #topic FOSEDM event
16:00:09 <rbowen> RDO community day, January 29th, at the IBM building in Brussels, prior to FOSDEM
16:00:09 <rbowen> CFP at http://goo.gl/forms/oDjI2BpCtm and will be announced on rdo-list today
16:00:09 <rbowen> Distros and Virt/IaaS devrooms available. CFPs mentioned on rdo-list
16:00:25 <rbowen> That's really the whole story. I'll be emailing rdo-list with the details I have in just a moment.
16:00:28 <apevec> ack
16:00:42 <apevec> and last FYI:
16:00:46 <apevec> #topic Delorean instance rebuild on Nov 5
16:00:59 <apevec> rbowen, ^ jpena will need DNS change
16:01:11 <apevec> supposedly I should have access now?
16:01:14 <jpena> yes, just a reminder that tomorrow I will be rebuilding the instance.
16:01:23 <rbowen> ok. just send the info and I'll make it happen.
16:01:54 <apevec> #topic open floor
16:02:03 <apevec> overtime, so be quick :)
16:02:26 * number80 has none
16:02:31 <apevec> ok, thanks everyone!
16:02:33 <apevec> #endmeeting