19:01:13 <devananda> #startmeeting ironic
19:01:14 <openstack> Meeting started Mon Sep 15 19:01:13 2014 UTC and is due to finish in 60 minutes.  The chair is devananda. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:01:15 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:01:17 <Shrews> \o
19:01:18 <openstack> The meeting name has been set to 'ironic'
19:01:19 <NobodyCam> \o/
19:01:24 <adam_g> o/
19:01:24 <devananda> As usual - our agenda can be found here:
19:01:26 <devananda> #link https://wiki.openstack.org/wiki/Meetings/Ironic
19:01:45 <harshada_kakad> o/
19:01:54 <devananda> #chair NobodyCam
19:01:54 <openstack> Current chairs: NobodyCam devananda
19:02:05 <devananda> #topic announcements
19:02:14 <wanyen> hi
19:02:18 <devananda> a few quick reminders for folks, mostly about the release schedule
19:02:38 <devananda> we are in feature freeze right now, which also means string and dependency freezes
19:02:55 <devananda> also, the UEFI work landed on time -- that was our only feature freeze exception
19:02:58 <devananda> good job on that :)
19:03:03 <lucasagomes> nice
19:03:04 <jroll> \o
19:03:05 <NobodyCam> :)
19:03:09 <Shrews> devananda: just for clarity, can you define "string freeze" for me?
19:03:27 <devananda> Shrews: changes in translated strings (exception and log messages) should be avoided
19:03:29 * NobodyCam would assume anything translated
19:03:40 <devananda> #link https://wiki.openstack.org/wiki/StringFreeze
19:03:42 <Shrews> devananda: ok, that's what i assumed, but wanted to be sure
19:04:02 <rloo> does it really matter for us, since they aren't translating anything for ironic anyway?
19:04:10 <devananda> rloo: but they are
19:04:19 <rloo> really? cool!
19:04:29 <NobodyCam> I've seen translation patches
19:04:31 <Shrews> devananda: by that wiki, we can change _existing_ strings, but not add _new_ ones?
19:04:37 <lucasagomes> rloo, https://www.transifex.com/projects/p/ironic/ :)
19:04:38 <devananda> IIRC, there were two  >50% translated languages in Icehouse
19:04:52 <devananda> Shrews: correct. but we should try to minimize those changes too
19:04:57 <Shrews> gotcha
19:05:13 <devananda> also
19:05:19 <devananda> tomorrow is the second half of our graduation review
19:05:30 <devananda> there were only two (minor) objections last week, both of which have been (IMO) addressed
19:05:31 * NobodyCam will be in tc meeting
19:05:43 <wanyen> fyi- the ironic dib chagnes to support ilo virtual media driver https://review.openstack.org/#/c/114124/ landed in tripleo
19:05:59 <devananda> wanyen: thanks, but please save that for later in the meeting
19:06:10 <lucasagomes> is the wiki for migration finished? (/me will take a look)
19:06:13 <devananda> that's it for my announcemetns. NobodyCam - anything from you?
19:06:16 <adam_g> devananda, i was going to polish off the migration docs today. should those be proposed to the ironic docs or is a pad/wiki good enough?
19:06:34 <lucasagomes> #link https://wiki.openstack.org/wiki/Ironic/NovaBaremetalIronicMigration
19:06:41 <devananda> adam_g, lucasagomes: I'm currently assuming wiki is good enough until someone tells me otherwise
19:06:43 <NobodyCam> just maybe to get more eyes on https://wiki.openstack.org/wiki/Ironic/NovaBaremetalIronicMigration
19:07:02 <adam_g> oh! i didnt realize that was already there
19:07:05 <adam_g> cool
19:07:07 <devananda> adam_g: there is a patch from jroll to fix the bug you hit in the migration of a live instance
19:07:10 <NobodyCam> also thank you to all who have helped on that doc
19:07:13 <lucasagomes> yeah it looks good, I haven't seem it in a while
19:07:16 <rloo> devananda: what were the two minor objections by TC last week?
19:07:18 <lucasagomes> last time wasn't that complete
19:07:23 <jroll> adam_g: https://review.openstack.org/#/c/121615/
19:07:39 <devananda> rloo: api proxy in nova (NobodyCam wrote it, it is merged) and migration docs (wiki above)
19:07:51 <rloo> thx devananda
19:07:59 <adam_g> nice. the migration tool needs to be fixed as well, to properly populate the node instance_info
19:08:01 <NobodyCam> thank you to lucasagomes for the tests on the proxy patch
19:08:07 <lucasagomes> NobodyCam, yvw :)
19:08:40 <devananda> #info Last week, the TC raised two minor objections to our graduation: an API proxy in Nova (now merged) and migration docs (now written at https://wiki.openstack.org/wiki/Ironic/NovaBaremetalIronicMigration )
19:08:51 <devananda> #info Final graduation review for Ironic in Juno is tomorrow
19:08:52 <NobodyCam> oh would this be a good place to bring up the fact that we broke tripleo last week?
19:09:22 <devananda> NobodyCam: if there should be a discussion about that, perhaps save it for a bit later
19:09:23 <jroll> adam_g: there's also this fix, jfyi: https://review.openstack.org/#/c/121651/
19:09:27 <NobodyCam> ack
19:09:40 <devananda> #topic Juno RC progress
19:09:46 <devananda> #link https://launchpad.net/ironic/+milestone/juno-rc1
19:09:55 <adam_g> jroll, thanks
19:10:18 <devananda> we've got the one BP done, but there are still >15 bugs we've targeted to RC1
19:10:32 <dtantsur> 18 IIRC :)
19:10:38 <devananda> that should be the area of our focus in the next few weeks
19:10:50 <devananda> I'd like to take a few minutes in each weekly meeting to open the door
19:10:58 <devananda> for folks to call out bugs they think need extra attention
19:11:06 <devananda> of course, we should be doing that during the week too :)
19:11:22 <rloo> devananda: RC1 is Sept 25 (next THurs)
19:11:45 <devananda> rloo: right. not next few weeks. next 10 days
19:11:53 <devananda> #info RC1 is targeted to Sept 25 -- 10 days from now
19:12:00 <devananda> (thanks ...)
19:12:27 <wanyen> deva, when is document due? due at RC1?
19:13:12 <devananda> #info Juno release is targeted to Oct 16
19:13:26 <devananda> wanyen: the sooner the better. Please don't leave it until Oct 16
19:13:45 <wanyen> deva, sure.
19:14:17 <devananda> anyhow, I see a lot of bugs in progress
19:14:41 <NobodyCam> ahh so no need to bug folks about bugs
19:14:46 <NobodyCam> (yet)
19:14:48 <devananda> would folks prefer to walk through them now, or have a less formal meeting for that, say, on wednesday?
19:14:49 <NobodyCam> lol :-p
19:15:13 <rloo> on Wed
19:15:16 <jroll> let's have a bug day later
19:15:20 <jroll> I won't be here wed though :(
19:15:27 <devananda> maybe do a bug-squash-day on wed and fri, until we are comfortable with the release quality?
19:15:27 <dtantsur> I'm busy on Wed
19:15:28 <JayF> Nor will I
19:15:34 <devananda> ok - what's a better day :)
19:15:39 <lucasagomes> right, but can we make it a bit earlier than this meeting?
19:15:41 <NobodyCam> devananda: I would wed. so folks have to prep / finsh up
19:15:44 <devananda> lucasagomes: ++
19:15:56 <JayF> My requirement is pretty much not Weds or Fri if you want me there :)
19:15:58 <devananda> lucasagomes: i think we've usually done it around 8am PST
19:16:10 <lucasagomes> devananda, yeah, that's a good time
19:16:15 <dtantsur> For me Thu-Fri and yes, actually earlier
19:16:16 <lucasagomes> so, I'm in :)
19:16:17 <devananda> JayF: heh. ok. fwiw, friday is unofficial openstack bug day (in general, not just during RC)
19:16:26 <devananda> cool
19:16:45 <Shrews> is that "create new bug day", or "squash existing bugs day"   :)
19:17:05 <devananda> #info we're going to have volunteer bug squash days thu & fri at 8am PST this week
19:17:21 <devananda> Shrews: depends. probably both :)
19:17:48 <devananda> any one else want to call out any bugs in particular? dtantsur - if you want to give your report on bug stats, I know it's out of order, but might as well give it now
19:18:00 <dtantsur> right
19:18:07 <dtantsur> Open: 111 (-22). 6 new (-3), 36 in progress (-8), 1 critical (+1), 11 high (-3) and 5 incomplete (+1); juno-rc1: 18 (+3)
19:18:20 <dtantsur> we're better now, once some bugs moved to Nova
19:18:21 <devananda> Open -22 --- awesome!
19:18:29 <dtantsur> (also fixed a lot)
19:18:33 <lucasagomes> :)
19:18:35 <lucasagomes> great
19:18:47 <rloo> and how/should we track ironic-bugs-in-nova?
19:18:51 <dtantsur> but 18 for rc1 is a lot too (growed +3)
19:18:57 <dtantsur> rloo, tag 'ironic'
19:18:59 <Shrews> devananda: i think we're going to need to start paying more attention to the hash ring bugs greghaynes is working on. we'll need to test that stuff pretty well, IMO
19:19:08 <devananda> Shrews: ++
19:19:11 <rloo> Shrews: ++
19:19:22 <devananda> Shrews: at this point, it looks like a major functional change though
19:19:31 <Shrews> devananda: yeah, that was my next question
19:19:38 <devananda> Shrews: so I think we need a discussion on whether it's too big for this late in the cycle
19:19:45 <Shrews> devananda: i think so
19:19:50 <NobodyCam> devananda: ++
19:19:52 <Shrews> but, can discuss later
19:19:58 <lucasagomes> yeah it seems to be quite big/hard to test
19:20:13 <lucasagomes> Shrews, +1 to discuss later
19:20:22 <rloo> later == when?
19:20:31 <NobodyCam> paris?
19:20:32 <devananda> Shrews: if you have a grasp on the issue, can you raise it on the ML? I don't see greghanes here, or I'd ask him to weigh in
19:20:36 <lucasagomes> open topic :)
19:20:40 <lucasagomes> idk
19:20:50 <dtantsur> paris sounds like a good time :D
19:21:04 <rloo> so no fix in juno
19:21:05 <devananda> aiui, the problem -might- be big enough to warrant fixing now
19:21:09 <devananda> but I haven't dug in yet
19:21:10 <Shrews> devananda: i've been following one of his changes, but haven't looked at the second (or lifeless's change yet)
19:21:24 <Shrews> devananda: i'll catch up and start something though
19:21:25 <devananda> JayF: jroll: have ya'll been following the hash ring bug thread?
19:21:35 <NobodyCam> rloo: I think time is to short and change is to big for J
19:21:37 <JayF> devananda: honestly; no
19:21:39 <jroll> devananda: a bit, yeah
19:21:51 <devananda> are you affected by it // do you care about the fix?
19:22:04 <rloo> is ironic 'usable' w/o the change? rackspace knows?
19:22:28 <devananda> rloo: well. they are the only ones publicly discussing their in-production ironic service afaik
19:22:30 <jroll> devananda: we're affected less by hash ring rebalances, as the agent driver doesn't have any local state on the conductor
19:22:40 <devananda> jroll: ack. that's what I figured
19:23:15 <jroll> devananda: we do care about the fix from a "we are nerds interested in distributed systems" standpoint, but that might be it
19:23:36 <devananda> #info hash ring bug needs further discussion. May be a serious issue for PXE driver, but doesn't really affect IPA.
19:24:02 <devananda> thanks, all. going to move on so we have time for everything
19:24:13 <devananda> #topic Kilo summit planning
19:24:19 <devananda> so, a few things here
19:24:41 <devananda> first, assuming Ironic graduates, it'll get in the main track, and we can all enjoy the cross project track on the first day
19:24:46 <devananda> (that's still an assumption at this point)
19:25:02 <devananda> second, the neat website we've used in the past is -not- being used for planning purposes this time
19:25:23 <devananda> all projects are using etherpads, google docs, or carrier pidgeons for session planning
19:25:33 <devananda> I set this up last week -- should be open to everyone to edit
19:25:34 <devananda> #link https://docs.google.com/spreadsheets/d/1XBKdeDeGfaRYaThjIIoYRwe_zPensECnxsKUuqdoVmQ/edit#gid=0
19:25:46 <devananda> let's start throwing ideas up there now
19:25:52 <devananda> and we'll discuss as Paris approaches
19:26:07 <devananda> (by "now" i mean over the next month -- not this very minute)
19:26:17 * jroll watches everyone edit at once
19:26:27 <NobodyCam> lol
19:26:28 <lucasagomes> nice :)
19:26:38 <devananda> I also want to ask, if anyone has a strong objection to this format and would prefer etherpad (or carrier pidgeon)
19:26:44 <devananda> please speak up now
19:26:52 <devananda> before we get a lot of info in the gdoc
19:26:55 * NobodyCam votes gdoc!!!
19:27:06 <jroll> I like the spreadsheet
19:27:06 <dtantsur> pidgeon sounds fine!
19:27:12 <jroll> but pigeons are also fine with m
19:27:14 <jroll> e
19:27:15 <lucasagomes> I don't mind the spreadsheet
19:27:37 * NobodyCam has tooo many ehter pads open
19:27:39 <rloo> what is the Spec? column for? link to spec?
19:27:45 <devananda> rloo: yes, if there is one
19:28:01 <rloo> have we opened specs for kilo yet?
19:28:05 <devananda> rloo: that was a feature on the old planning site -- you could link to specs or BPs in the proposal
19:28:12 <NobodyCam> have we opened the "K" directory in the spec repo yet?
19:28:17 <devananda> rloo: no :) but that hasn't stopped folks from proposing them anyway
19:28:25 <rloo> ha ha
19:28:29 <lucasagomes> btw specs for K needs to adhere to the new format write?
19:28:49 <lucasagomes> we maybe need to make it more clear/update our wiki about it
19:28:58 <lucasagomes> write/right*
19:28:58 <JayF> I'd be very +1 to opening the kilo/ folder for ironic-specs, even if that means the specs proposed have to be rebased onto another template or can't be approved until officially opens
19:28:59 <NobodyCam> lucasagomes: ++
19:29:45 <jroll> heh
19:29:49 <devananda> JayF: I would rather not open it until, at the earliest, Sept 25 (when RC1 is tagged)
19:30:54 <jroll> devananda, JayF, I think things are fine as is, folks can rebase as needed if we reopen
19:31:09 <NobodyCam> who if anyone is going to port any J specs to K ? is that even a thing to be concerned about?
19:31:30 <NobodyCam> spec's that did not land
19:31:30 <devananda> NobodyCam: none of us should do that
19:31:50 <devananda> NobodyCam: the spec's author should rebase and repropose it -- this is also a way for us to see if they're still interested/committed to doing the work
19:32:07 <NobodyCam> so the spec review team should only look at k folder (once it opens)
19:32:17 <devananda> we should, after RC, open the Kilo folder and publish some guidelines (link to new spec format, etc)
19:32:23 <devananda> NobodyCam: yep
19:32:30 <NobodyCam> devananda: ack ... TY
19:33:03 <devananda> more questions on Kilo design summit today? (I'm sure we'll come back to it in two weeks)
19:33:19 <JayF> We have 4 design sessions, right?
19:33:33 <devananda> also - if any ATC did not get their access code, please ping me privately
19:33:43 <devananda> JayF: don't know yet. that depends on if ironic graduate
19:33:45 <jroll> JayF: I think it's unknown at this time
19:34:04 <lucasagomes> tomorrow is the day!
19:34:10 <NobodyCam> if we do not graduate we get two?
19:34:14 <devananda> oh - so, we will have a pod for Ironic all week
19:34:24 <devananda> we may only get a few "full" sessions
19:34:38 <devananda> but we can have our own unconference style thing
19:34:45 <devananda> use the google doc to organize
19:34:46 <devananda> or what ever
19:34:53 <devananda> that's up to us -- it just won't be in the published schedule
19:35:00 <NobodyCam> does the Ironic pod need to be man'd as a "both" would be
19:35:00 <devananda> also - that's how all the projects are being run this time
19:35:13 <devananda> NobodyCam: no. it's in the developer area, not public hall
19:35:20 <NobodyCam> :)
19:35:31 <devananda> it should probably have a sign and a schedule posted, or something
19:35:47 <devananda> ok - moving on :)
19:35:59 <devananda> #topic subteam status report - testing and CI
19:36:02 <devananda> adam_g: hi!
19:36:06 <adam_g> hey!
19:36:12 <devananda> you've done all the things! it's amazing! :)
19:36:26 <adam_g> not too much to report from last time. still waiting on getting all the grenade testing in place in our gate, a couple pending infra reviews still @ https://review.openstack.org/#/q/topic:ironic_infra,n,z
19:36:48 <devananda> I dont see a grenade test in that list?
19:37:28 <adam_g> devananda, there is already a check-grenade-dsvm-ironic-sideways, but it requires some of those changes in that topic to get it passing
19:37:34 <devananda> ahh ok
19:38:34 <adam_g> thats about it from me, not sure if others have more to report on the CI front
19:38:52 <devananda> cool. nothing more from me
19:39:16 <NobodyCam> thank you adam_g :) great work!
19:39:17 <devananda> i could say "thanks" several more times, though :)
19:39:27 <adam_g> np :)
19:39:43 <devananda> #topic oslo
19:39:46 <devananda> GheRivero: hi! around?
19:40:26 <GheRivero> just arrived, just caching up with everything
19:40:35 <GheRivero> so no news from my side
19:40:39 <devananda> ok, np. I'll summarize what I know of oslo status real quick, then
19:40:55 <devananda> I'm not expecting any big changse from oslo, aside from their publishing of Juno final versions of most of the libraries
19:41:09 <devananda> which should be this thursday, IIRC
19:41:21 <devananda> so we'll probably see one large patch to openstack-requirements from the bot
19:41:22 <dhellmann> I expect all of those to be re-versioned releases of things we have already released by thursday, fwiw
19:42:10 <devananda> should be trivial to land :)
19:42:24 <devananda> #topic drivers
19:42:41 <devananda> jroll, linggao, wanyen - anything to report on your various drivers?
19:42:47 <jroll> hi!
19:42:49 * devananda notes that linggao isn't here
19:42:56 <JayF> Would this be a good time to talk about IPA releasing/versioning for Juno?
19:42:58 <jroll> I have a few quick things
19:43:14 <lucasagomes> JayF, +1 I think so
19:43:16 <devananda> JayF: sure!
19:43:17 <jroll> JayF: I think so, let me quickly status update
19:43:42 <jroll> as usual, our semi-current status is always here:
19:43:44 <jroll> #link https://etherpad.openstack.org/p/ipa-todos
19:43:57 <jroll> currently working on getting CI running, the patches are listed in that etherpad
19:44:38 <jroll> we're also working on a lot of documentation-type things, JayF and I started writing docstrings for everything, there's a few patches up, would love for some folks that don't typically work on IPA to review them :)
19:45:03 <NobodyCam> I heard that we have our first thrid party CI up?
19:45:21 <jroll> we do! that's for ipminative
19:45:25 <devananda> NobodyCam: yep! check-ironic-xcat-third-party
19:45:33 <jroll> JayF: want to lead on the release/versioning stuff?
19:45:35 <NobodyCam> awesome!!!
19:45:37 <lucasagomes> nice, ibm is behind that right?
19:46:02 <JayF> So with regards to IPA, we've had some informal discussions about how IPA should be released for Juno
19:46:06 <devananda> yes - linggao is coordinating it, iirc
19:46:12 <JayF> when we originally added the project; it was going to be SEMVER similar to clients
19:46:29 <JayF> I wonder if that's the better approach vs blessing a release for Juno
19:46:38 <JayF> I don't know the right answer, and I'm not even sure I have good ideas
19:46:50 <JayF> So anyone willing to share their ideas, please do
19:47:23 <lucasagomes> JayF, I like cutting a version for it. But how we are doing it pip?
19:47:50 <devananda> the mechanics of getting something into pip or into the release aren't that complex -- i can walk (someone) through that
19:48:04 <devananda> but I think there are some important technical questions about which way it *should* be released
19:48:16 <devananda> if IPA is treated like a client lib,
19:48:20 <JayF> Yeah, I'm more concerned about how we should do it than the mechanics of doing whatever we decide
19:48:25 <devananda> - it is free to release often, on its own cadence
19:48:31 <JayF> I can figure out how to do anything that's been done before, and maybe even some new stuff soon :)
19:48:47 <devananda> - it can get an entry in global-requrieemnts, and Ironic can depend on a specific version of it (from pip or from packages)
19:49:03 <devananda> - downstream packagers (eg, deb & fedora) can pin it in their distros, too
19:49:07 <devananda> and can release updates as needed
19:49:26 <devananda> if on the other hand, IPA is treated like a project
19:49:36 <devananda> - it only gets released once every six months
19:49:47 <JayF> devananda: well, like I was saying earlier in IRC: IPA seems almost like something that a 'release' should be built images, not source
19:49:59 <JayF> devananda: similar to how ipxe and syslinux package images in distros
19:50:11 <JayF> but I don't think Openstack has something that models that way currently
19:50:12 <NobodyCam> fyi: ten minutes to go
19:50:14 <devananda> - the dependency between it and Ironic is a bit harder to enforce and test, since there are no packaged versions of it between releases
19:50:39 <jroll> JayF: the reason I disagree with releasing images, is then they are not customizable, which is almost a necessity
19:51:05 <devananda> JayF: I don't hear you saying that rackspace wants to start releasing and maintaining images of CoresOS + IPA
19:51:12 <JayF> if custom images are something someone wants/needs, I don't see the harm in having them pull it from git
19:51:31 <devananda> JayF: also, OpenStack is not in that business either
19:51:44 <JayF> devananda: We already tried; we were told to do it first-party in a post job that uploads to tarballs.openstack, which is what we're doing
19:52:05 <jroll> I don't think standard releases are very useful except for testing, but that might just be me
19:52:17 <devananda> JayF: yes. that is a tarball of the current build, useful by our CI systems
19:52:22 <jroll> and that may be me thinking ahead to more advanced features that we're using, current upstream might be useful
19:52:24 <devananda> JayF: to ensure that TIP of one project works with TIP of another
19:52:30 <devananda> there's no releasing, no versioning, no packaging there
19:53:13 <devananda> JayF: for example, two weeks after Kilo opens, how will you answer the request from a user who instaled Juno from deb packages
19:53:19 <devananda> who wants to download a build of IPA compatible with that
19:53:20 <devananda> ?
19:53:34 <jroll> I'm inclined to think we should release as a client, after hearing this stuff
19:53:45 <jroll> though I don't think distros should package it
19:53:47 <JayF> IPA should be compatible with any ironic, if it isn't we didn't version well, similar to how we do with the clients
19:53:53 <JayF> but I'm not sure we're good enough to do that ^ yet
19:53:58 <devananda> jroll: ++
19:53:59 <JayF> jroll probably has the most reasonable solution
19:54:17 <jroll> I think we are good enough to do that yet, but pinning a version can't hurt
19:54:36 <devananda> jroll: as I see it, that would mean someone who is using their distro's Juno Ironic would also install IPA from their distro (who presumably used the versionthat we pinned in the release of Juno) to build their images
19:55:08 <jroll> hrm, I don't think that's a good way to build images :|
19:55:12 <NobodyCam> 5 minutes
19:55:24 <devananda> I can help point ya'll at the process to make ^ happen -- basically means setting up a thing in pypi and a job in infra
19:55:38 <jroll> are you saying they should e.g. cp /usr/local/bin/ironic-python-agent /my/fancy/image/filesystem
19:55:44 <jroll> sounds... wrong
19:55:48 <jroll> btu that might just be me, dunno
19:55:49 <devananda> no
19:55:53 <jroll> we can talk about specifics later
19:55:54 <devananda> ok, we can continue this after the meeting
19:55:56 <devananda> :)
19:56:09 <devananda> #topic outstanding items for graduation
19:56:20 <devananda> lucasagomes: I think you posted this? afaik, we've already covered it -- and we should be good
19:56:20 <JayF> I think we'll want some wiki docs about how we expect people to use the pypi release to build their images
19:56:34 * NobodyCam updated the proxy line item color to blue
19:56:34 <lucasagomes> devananda, oh yeah we talked about it in the channel
19:56:40 <jroll> JayF: indeed
19:56:41 <lucasagomes> and here
19:56:46 <devananda> cool, skipping it
19:56:49 <devananda> #topic Open Discussion
19:56:56 <devananda> 3 minutes! go :)
19:57:13 * jroll runs around waving his hands wildly
19:57:15 <lucasagomes> devananda, can we make the ironic tempest jobs voting in Nova?
19:57:23 <lucasagomes> since now the driver is merged there
19:57:25 <devananda> lucasagomes: only when ironic graduates
19:57:34 <NobodyCam> ust a quick note we broke tripleo last week with a minor change to the virsh ssh commands. was fixed with https://review.openstack.org/#/c/120799
19:57:38 <lucasagomes> hmm
19:57:43 <devananda> lucasagomes: also there's a much longer conversation happening on the ML and amongst the TC about that sort of thing
19:57:47 <devananda> which I wont attempt to summarize now
19:58:13 <rloo> devananda: when were you going to do another CLI release?
19:58:13 <devananda> read the many threads on "future of the integrated release", "splitting out Nova", and so on ... and expect details in Paris
19:58:14 <lucasagomes> devananda, it's not the discussion about splitting the drivers out of the tree is it?
19:58:15 * NobodyCam crys after all that work done to land our driver
19:58:18 * lucasagomes needs to catch up with that thread
19:58:36 <devananda> rloo: probably tomorrow. definitely before thursday
19:58:49 <rloo> devananda: thx. I'd like a couple more changes in.
19:58:51 <devananda> NobodyCam: no no -- it's really good taht our driver landed.
19:58:59 <NobodyCam> is there anything we need for tomorrow in the last two minutes
19:58:59 <devananda> rloo: ok, please highlight them in channel post meeting
19:59:06 <rloo> devananda: will do
19:59:10 <devananda> NobodyCam: not that I know of. I think we're set for tomorrow
19:59:26 <NobodyCam> awesome work EVERYONE!!!!!!
20:00:04 <lucasagomes> +1
20:00:11 <NobodyCam> and thats time
20:00:13 <jroll> thanks everybdy :)
20:00:15 <JayF> ty
20:00:16 <dtantsur> thanks!
20:00:18 <NobodyCam> great meeting all TY
20:00:18 <lucasagomes> thanks
20:00:25 <devananda> cheers, thanks everyone!
20:00:31 <wanyen> thanks
20:00:33 <devananda> #endmeeting