09:00:56 <ttx> #startmeeting ptl_sync
09:00:57 <openstack> Meeting started Tue Nov 25 09:00:56 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:00:58 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:01:00 <openstack> The meeting name has been set to 'ptl_sync'
09:01:04 <ttx> #topic Heat
09:01:17 <ttx> #link https://launchpad.net/heat/+milestone/kilo-1
09:01:44 <ttx> https://blueprints.launchpad.net/heat/+spec/lazy-load-outputs is marked "unknown" status -- should I consider that not started ?
09:02:07 <asalkeld> ttx, i need to check on that one
09:02:21 <asalkeld> i just noticed it myself
09:02:27 <ttx> asalkeld: ok, just set status when you know it -- "Not started" is fine :)
09:02:38 <asalkeld> it might be small
09:02:44 <ttx> Otherwise status looks good in general
09:02:54 <asalkeld> yeah, more action in k2
09:03:07 <ttx> do you expect much more stuff to get done for k1 ? Any work pending a spec approval ?
09:03:27 <asalkeld> i have 2 bp's with code ready
09:03:41 <asalkeld> but trying to get people happy with it
09:03:52 <asalkeld> either in fast or not
09:04:01 <ttx> asalkeld: would it make sense to track them in the milestone as "Blocked" ?
09:04:21 <ttx> at least people would know it's potentially coming ?
09:04:25 <asalkeld> maybe, I have them as k2
09:04:30 <asalkeld> just to be cautious
09:04:35 <ttx> ah, ok
09:04:45 <ttx> that's fione, you can move them if they are approved
09:04:51 <asalkeld> cool
09:05:21 <asalkeld> i would love a tool that would tell me what bp's i need to tweak
09:05:31 <ttx> So I have spec2bp v2 here: https://review.openstack.org/#/c/108041/
09:05:32 <asalkeld> i might as the nova guys
09:05:58 <ttx> still need to check with current users (dhellmann) if that's a welcome evolution
09:06:04 <ttx> but you can keep an eye on it
09:06:10 <asalkeld> thx
09:06:30 <ttx> asalkeld: it doesn't prevent you from having to file the blueprint manually
09:06:37 <ttx> but after that it aligns fiedl status
09:06:42 <ttx> field*
09:06:59 <asalkeld> that's fine, i wouldn't mind just a tool in our specs repo that i can run
09:07:17 <asalkeld> that says x,y and z have just been approved
09:07:26 <asalkeld> and need their status tweaking
09:07:32 <ttx> ok
09:07:44 <asalkeld> maybe i can come up with that
09:08:01 <asalkeld> i'll dig into your code
09:08:12 <ttx> did you have any question?
09:08:19 <asalkeld> all good
09:08:29 <ttx> alright then, have a good day!
09:08:32 <asalkeld> and 2 mins to go!
09:08:35 <asalkeld> you too
09:08:36 <ttx> woohoo
09:11:05 <ttx> mikal: shall we wait for John?
09:48:40 <ttx> johnthetubaguy, mika: around now ?
09:51:41 <johnthetubaguy> ttx: I am
09:51:54 <ttx> alright then, let's do this
09:51:57 <ttx> #topic Nova
09:52:17 <johnthetubaguy> so meeting time, 9am UTC tuesday?
09:52:20 <ttx> #link https://launchpad.net/nova/+milestone/kilo-1
09:52:29 <ttx> 9:10 UTC actually
09:52:33 <johnthetubaguy> yeah, its kicking out time I think
09:52:34 <johnthetubaguy> OK, cool
09:52:43 <ttx> Heat goes at 9
09:52:45 <johnthetubaguy> not got that in my calendar yet
09:53:19 <ttx> Looking at the kilo-1 page, there are a few unknown statuses to clarify, but otherwise looks good
09:53:39 <johnthetubaguy> yeah, the unknown usually means not started, but yeah
09:53:57 <johnthetubaguy> I am thinking we need to punt some stuff to kilo-2 soon/
09:54:00 <johnthetubaguy> ?
09:54:15 <ttx> yeah, as usual, the conversion rate is a bit slow
09:54:44 <ttx> maybe after thanksgiving, you can kick out not started ones to k2
09:54:52 <johnthetubaguy> yeah, that seems reasonable
09:55:03 <johnthetubaguy> I mean, I am thinking everything that is not fully up for review
09:55:11 <johnthetubaguy> so we have a smaller list to concentrate on
09:55:17 <ttx> it's easy to bring them back from k2 to k1 if a miuracle happens
09:55:25 <johnthetubaguy> yeah, very true
09:55:37 <johnthetubaguy> after thanksgiving it is
09:55:43 <ttx> do you expect a lot more stuff to show up on the k1 list ?
09:56:20 <johnthetubaguy> well, maybe
09:56:28 <johnthetubaguy> there are lots of specs that are close
09:56:37 <johnthetubaguy> but I am adding them to k-2 by default at this point
09:56:51 <johnthetubaguy> but thats just storing up problems for later in a way
09:57:08 <johnthetubaguy> we spoke at the summit about all non-priority stuff needing to be merged by the end of kilo-2
09:57:20 <johnthetubaguy> so I need to start making that clear I guess
09:57:29 <ttx> ok, makes sense
09:57:31 <ttx> Also note that Nova doesn't have a stable branch liaison yet, so mikal is the liaison by default. Would be great for him to find someone to represent there
09:57:49 <ttx> especially with a point release coming up soon
09:58:15 <ttx> johnthetubaguy: maybe mention that at the next Nova meeting?
09:58:48 <johnthetubaguy> yeah, I will just keep raising were I can I guess
09:59:08 <johnthetubaguy> ah, I will try to remember to ask about the sable branch
09:59:19 <johnthetubaguy> not really sure who is active there
09:59:29 <ttx> johnthetubaguy: let me check
09:59:54 <ttx> padraig, vish and russell would be the more active stable people
10:00:09 <ttx> and already part of stable-maint
10:00:16 <ttx> so..; good candidates
10:00:37 <johnthetubaguy> thats a good list to ask, cool
10:00:47 <ttx> johnthetubaguy: other questions ? topics for the cross-project meeting today?
10:01:03 <johnthetubaguy> ttx: I guess specs follow up stuff
10:01:18 <ttx> specs follow up stuff ?
10:01:22 <johnthetubaguy> we have tried to make changes to the template to make it clearer about the specs process
10:01:35 <johnthetubaguy> from the cross project summit session, basically
10:01:51 <ttx> oh, about converging multiple approaches ?
10:01:51 <johnthetubaguy> I need to review the wiki page we have, and I just haven't done that yet
10:01:56 <johnthetubaguy> yeah
10:02:10 <johnthetubaguy> right now we are trying to properly document the nova approach in kilo
10:02:19 <ttx> is it ready for discussion, or would you rather solidify your approach and present it to the others
10:02:26 <johnthetubaguy> its a bit distributed, but we seem to be getting closer
10:02:35 <johnthetubaguy> I think we should solidify ideas first
10:02:43 <johnthetubaguy> its more that, its not forgotton
10:02:48 <ttx> ideally you would set your process in stone and then present it for others to adopt and RFC on
10:03:03 <ttx> OK, maybe a theme for next week meeting
10:03:13 <ttx> rather than this week's
10:03:23 <johnthetubaguy> yeah, thats a good target, while the US folks are eating turkey, I might get time for that
10:03:54 <ttx> johnthetubaguy: ok then, ttyl!
10:04:07 <johnthetubaguy> ttx: thank you, as always!
12:55:19 <SergeyLukjanov> ttx, /me ready when you're
12:57:10 <ttx> SergeyLukjanov: your time is 13:10utc so eglynn will go first
12:57:46 <ttx> eglynn: o/
12:57:54 <eglynn> ttx: hey, ready when you are
12:57:59 <ttx> #topic Ceilometer
12:58:02 <eglynn> #link https://launchpad.net/ceilometer/+milestone/kilo-1
12:58:16 <eglynn> I've fleshed out the kilo-1 roster
12:58:26 <ttx> Looks good. All 4 blocked are pending specs ?
12:58:35 <eglynn> yep, I've include some "blocked" BPs as discussed last week
12:58:50 <ttx> I have spec2bp v2 here: https://review.openstack.org/#/c/108041/ which you might want to experiment with
12:58:53 <eglynn> only in the cases where I know some implementation work has been done
12:59:13 <eglynn> (e.g. a PoC or a patch already proposed, so likely to be landable for Dec 18th)
12:59:22 <eglynn> cool, I'll have a play with it
13:00:28 <ttx> progress looks good
13:00:40 <eglynn> yep
13:00:41 <ttx> you nominated a stable liaison (yourself)
13:00:47 <ttx> so I have all the bases covered
13:00:55 <ttx> anything you wanted to discuss ?
13:01:11 <eglynn> yep, I got no volunteer for stable-maint liaison (asked at a couple of meetings)
13:01:22 <eglynn> all other liaison positions covered though
13:01:30 <eglynn> nothing else on my end
13:01:43 <ttx> alright then, talk to you later!
13:01:52 <eglynn> cool, thanks for your time :)
13:01:57 <ttx> SergeyLukjanov: you can go now if you want
13:02:04 <SergeyLukjanov> ttx, /me ready
13:02:07 <ttx> #topic Sahara
13:02:17 <SergeyLukjanov> ttx, I forget about +10 mins ;(
13:02:24 <ttx> #link https://launchpad.net/sahara/+milestone/kilo-1
13:02:36 <SergeyLukjanov> so, I've cleaned up the milestone page
13:02:44 <ttx> nice progress. Exepcting a lot more to show up in that milestone before k1?
13:03:37 <SergeyLukjanov> ttx, yup
13:04:05 <SergeyLukjanov> ttx, I expect 2-3 more blueprints done in k1
13:04:22 <ttx> remember you can track blueprints lacking spec approval but likely to make it by k1 with the "Blocked" status
13:04:22 <SergeyLukjanov> ttx, in addition to the list if specs will be approved this week
13:04:42 <SergeyLukjanov> ttx, yup, I think I'll add them to k1 to add more info
13:04:53 <ttx> alright, that looks pretty sane
13:05:07 <ttx> and... You're the stable branch liaison for sahara
13:05:16 <SergeyLukjanov> ttx, exactly
13:05:31 <ttx> so everything looks good. Any question on your side ?
13:06:18 <SergeyLukjanov> I think nope, everything going very good, we have a lot of new contributors after the first integrated release
13:06:33 <ttx> nice
13:06:41 <SergeyLukjanov> ttx, and btw all other liaisons positions are covered now
13:07:00 <SergeyLukjanov> so, nothing more from my
13:07:02 <SergeyLukjanov> ttx, thx!
13:07:04 <ttx> awesome.
13:07:06 <ttx> SergeyLukjanov: thx!
13:07:23 <ttx> dhellmann: we can go whenever you're available
13:07:32 <dhellmann> ttx: ready
13:07:37 <ttx> #topic Oslo
13:07:57 <ttx> #link https://launchpad.net/oslo/+milestone/next-kilo
13:08:26 <ttx> feels like a lot more is going on than apparent here
13:08:44 <dhellmann> we have some specs up for review still where work has started, I think
13:08:56 <dhellmann> oh, and see:
13:08:57 <dhellmann> #link https://launchpad.net/oslo/+milestone/kilo-1
13:09:12 <dhellmann> the stuff in the incubator is still targeted at the regular milestones
13:09:37 <ttx> ah hm
13:09:59 <dhellmann> I guess I can move those things to "next-kilo" as well
13:10:14 <ttx> checking if we have another view that would work
13:10:45 <ttx> hmm, no per-projectgroup series view
13:10:49 <ttx> so probably not
13:10:57 <ttx> we can still check two places if that makes more sense
13:10:59 <dhellmann> I hate to put something like the namespace package change in next-kilo since we expect that to take quite a while.
13:11:22 <dhellmann> let's give it a week or two and see how it goes? I'm OK with merging them if we decide we need to do that
13:11:24 <ttx> I think oslo-incubator should keep kilo-X
13:11:28 <dhellmann> ok
13:11:44 <ttx> makes a lot more sense to be aligned with projects it's copy-pasted from/to
13:11:57 <dhellmann> right
13:12:25 <ttx> ok, you hjave a few "unknown" status that might be turned ito something more explicit, but otherwise looks good
13:12:28 <ttx> into*
13:12:56 <dhellmann> I'll work on updating those. I'm taking a sick day today, so it may be next week
13:13:06 <ttx> ow
13:13:41 <ttx> won't hold you away from bed then... just a couple things
13:13:56 <ttx> https://review.openstack.org/#/c/136820/ -- that's the oslo-enabled autokick.py
13:14:04 <dhellmann> nah, this is just an annoying cold, but it gives me an excuse to do some reading :-)
13:14:11 <ttx> if I ran it on oslo now it would do:
13:14:42 <ttx> (wait for it)
13:15:06 <ttx> http://paste.openstack.org/show/138167/
13:15:22 <ttx> SETGOAL is just setting the series goal according to target milestone
13:15:37 <ttx> CLEARGOAL is removing the series goal since there is no target milestone
13:15:50 <dhellmann> why are some of them being cleared? do those have kilo set as the series but the spec isn't approved?
13:15:53 <dhellmann> heh
13:16:08 <dhellmann> ok, I guess that looks right
13:16:11 <ttx> KICK would mean removing target milestone because no priority set, but you don't have one of those
13:16:36 <dhellmann> I sort of like having the option of adding a series goal but we can keep up with those items through the specs I guess
13:16:58 <ttx> yeah, the trick is, it can get confusing if you don't keep the two aligned
13:17:14 <dhellmann> true
13:17:22 <ttx> you can have blueprints showing up in series view but not in milestone views
13:17:28 <ttx> (and the other way around, damn LP
13:17:29 <ttx> )
13:17:32 <dhellmann> I don't think there's anything too destructive going on here, so you can run it on oslo when you're ready
13:17:47 <ttx> OK, will upgrade the version I use in my cron and run it for oslo
13:17:56 <dhellmann> yeah, having them in the series was a way I kept up with what we said we might do before we started using specs
13:17:58 <ttx> second review is the new spec2bp
13:18:03 <dhellmann> but specs give us that now
13:18:18 <ttx> since you are one of the few to actually use v1, I'd like to have an opinion if it's better/worse
13:18:27 <ttx> https://review.openstack.org/#/c/108041/
13:18:39 <ttx> the goal is to support blueprints for not-yet-approved specs
13:18:58 <ttx> so most of the logic around starting from the approved spec falls down
13:19:06 <ttx> and I rewrote it to take a blueprint as input
13:19:15 <ttx> (since those need to be craeted separately anyway)
13:19:16 <dhellmann> I was looking over that. I think in general it's good, but I'm worried about the specs repository name handling change.
13:19:35 <dhellmann> I was adding review comments when you pinged me
13:19:41 <dhellmann> I'll submit them....
13:19:44 <ttx> ok, just take your time
13:19:48 <ttx> just a heads-up
13:19:53 <dhellmann> ok
13:20:07 <ttx> questions ?
13:20:52 <dhellmann> no, I'll leave a couple of comments on that review but that's all I had today
13:21:04 <ttx> alright then, get well soon
13:21:17 <dhellmann> oh, sdague talked to you about the stable branch version caps, right? that's a topic for this afternoon?
13:21:22 <ttx> yes
13:21:23 <dhellmann> thanks
13:21:35 <ttx> it's on the agenda for the meeting today
13:21:57 <dhellmann> ok, good, he and I spoke yesterday and agree on what we need so if I can't make it this afternoon he will be representing both of us
13:22:13 <ttx> ok
15:05:26 <ttx> mestery: around?
15:05:34 <mestery> ttx: o/.
15:05:37 <ttx> #topic Neutron
15:05:50 <ttx> #link https://launchpad.net/neutron/+milestone/kilo-1
15:06:07 <ttx> Still feels very much partial to me
15:06:21 <mestery> Yes, I agree, we're reviewing specs but it's still very thin
15:06:46 <mestery> Also, did you see this: https://review.openstack.org/#/c/136514/
15:06:59 <mestery> Similar to Nova, I created a priorities spec for Neutron. Most of the things on that list are in review in neutron-specs
15:07:05 <ttx> feel free to add "blocked" specs if you expect stuff to be approved and implemented in time for k1
15:07:25 <mestery> Got it
15:07:35 <ttx> like one of those priorities
15:07:55 <mestery> Will do
15:07:59 * mestery makes a note to do that post-meeting with ttx
15:08:40 <ttx> also if you know what's going on there you can update the "unknown" statuses
15:09:00 <mestery> Yes, agreed. Are we also running your automatic pruning script now for neutron? I believe we are, just wanted to confirm.
15:09:07 <ttx> yes
15:09:17 <mestery> cool
15:09:35 <ttx> Looks like Ihar voluntered to do stable branch liaison for neutron too
15:09:56 <mestery> Yes, he's been doing a really good job there in fact!
15:10:04 <mestery> I am very thankful for that. :)
15:10:19 <ttx> we have arosen, markmcclain and garyk on the neutron-stable-maint future team at this point
15:10:37 <mestery> I think all three of those folks are good to have there.
15:10:50 <mestery> I may see if amotoki wants to join as well, he would be a good candidate there in addition.
15:10:55 <mestery> I'll ask him.
15:11:24 <ttx> ok, so for next week it would be good to beef up that k1 milestone if you expect other stuff to make it by Dec 18
15:11:31 <ttx> I guess that's all I had
15:11:34 <ttx> questions?
15:11:43 <mestery> Same for me, I just wanted to highlight the priorities BP and that's it.
15:11:48 <mestery> Nothing yet.
15:11:55 <mestery> Thanks ttx!
15:12:00 <ttx> no pb
15:12:15 * mestery is slowly ramping up more post fourth child birth.
15:12:16 <ttx> #info priorities for kilo at: https://review.openstack.org/#/c/136514/
15:12:21 <mestery> It's taking longer than I thought :)
15:12:54 <ttx> nikhil_k: ready when you are (if you are around)
15:15:26 <nikhil_k> ttx: o/
15:16:31 <ttx> #topic Glance
15:16:44 <ttx> #link https://launchpad.net/glance/+milestone/kilo-1
15:17:55 * ttx checks why that undefined spec was not autokicked out of milestone
15:18:24 <ttx> oh, the script is not really enabled for Glance yet
15:18:30 <nikhil_k> ttx: we want it in k1 though
15:18:35 <nikhil_k> ah ok
15:18:39 <ttx> ok, then that's fine.
15:18:55 <ttx> nikhil_k: just let me know if you want to switch to using that in the future
15:19:07 <ttx> you should still probably set a priority for that undefined spec
15:19:20 <nikhil_k> sounds good
15:19:31 <ttx> Are those the two things you expect to land before the k1 date ?
15:19:38 <nikhil_k> done
15:19:48 <nikhil_k> ttx: there are a couple more
15:19:50 <nikhil_k> https://review.openstack.org/#/c/124522/
15:20:01 * nikhil_k will ask for a bp to be created
15:20:20 <nikhil_k> there was a mis-communication that spec auto creates bp post approval
15:20:23 <ttx> yes, you can add a blueprint and set it to "Blocked" until the spec is approved
15:20:31 <nikhil_k> sure
15:20:42 <nikhil_k> there was one more communicated by another dev
15:20:42 <ttx> no, BP needs to be manually created (LP has no API for creatign blueprints)
15:20:47 <nikhil_k> he's still working on details
15:20:55 <ttx> then you can use a script of mine to update it if you want
15:21:06 <nikhil_k> noted
15:21:14 <ttx> in progress at https://review.openstack.org/#/c/108041/
15:21:31 <ttx> but in all cases you need a blueprint up and manually created
15:21:58 <nikhil_k> ah cool
15:22:00 <ttx> so for next week it would be great to see those blocked blueprints on the milestone map
15:22:15 <ttx> ping me if you have any question on how to achieve that
15:22:39 <ttx> Erno Kuvaja volunteered to be stable liaison for Glance, does that sound good to you ?
15:23:03 <nikhil_k> yeah, it was post communication from me
15:23:15 <nikhil_k> so you need me to send email or something to confirm that?
15:23:23 <ttx> no no, it's fine
15:23:26 <nikhil_k> s/so/do/
15:23:43 <ttx> ok, I think that's all I had, status looks generally good.
15:23:49 <ttx> Questions on your side ?
15:24:45 <nikhil_k> ttx: nothing this week :)
15:24:53 <ttx> ok then, talk to you later!
15:24:54 <nikhil_k> holiday week :))
15:25:00 <ttx> yep
15:25:02 <nikhil_k> sounds good
15:25:07 <ttx> thingee: ready when you are
15:25:43 <thingee> ttx: o/
15:25:54 <ttx> #topic Cinder
15:26:05 <ttx> #link https://launchpad.net/cinder/+milestone/kilo-1
15:26:15 <thingee> got our first blueprint done!
15:26:19 <ttx> yay
15:26:40 <thingee> started doing specs for k-2
15:26:50 <ttx> there are two specs without an assignee on that list... any chance some person (or group) actually signed up to do that one ?
15:27:02 <thingee> we have about four drivers that are just about ready to be approved. We'll see if that'll be possible this week.
15:27:44 <thingee> ah good catch. There are people for those already working on them
15:27:46 <thingee> I'll fix that
15:28:18 <ttx> cool, looks good (and ambitious) otherwise
15:28:49 <ttx> Cinder did not formally designate a stable branch liaison yet, which means it falls back on you
15:28:50 <thingee> I agree. For those drivers on the list that still have a 'not started' status right now, I'm a bit worried
15:29:06 <ttx> yes, starting next week you could defer not started stuff to k2
15:29:27 <ttx> Jay Bryant is on the stable-maint group, could be a good candidate
15:29:31 <thingee> that would be jay bryant. What should I update to make that so?
15:29:38 <thingee> oh heh
15:29:52 <ttx> thingee: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Stable_Branch
15:30:15 <thingee> I'll verify with him and update it
15:31:10 <ttx> ok, that's all I had I think
15:31:21 <ttx> questions at this point ?
15:31:25 <thingee> the problem is we can't defer drivers to k-2. The group has already agreed to leave k-2 and k-3 for other things than new drivers :(
15:31:44 <ttx> well, they should better get started then :)
15:31:53 <ttx> otherwise you'll be
15:31:57 <thingee> I'll reach out to them for good measure
15:32:01 <ttx> ...soon in exception hell
15:32:13 <thingee> :)
15:32:17 <thingee> thanks ttx!
15:32:23 <ttx> thingee: thx!
15:32:28 <ttx> david-lyle: ready when you are
15:32:41 <david-lyle> ttx: ready
15:32:44 <ttx> #topic Horizon
15:32:50 <ttx> #link https://launchpad.net/horizon/+milestone/kilo-1
15:33:14 <ttx> So... a few undefined priorities, a few unassigned blueprints, and a few unknown statuses
15:33:32 <ttx> Otherwise progress looks good
15:33:47 <david-lyle> I need to filter the new arrivals
15:33:53 <david-lyle> will work on that later today
15:34:03 <ttx> ack
15:34:09 <ttx> Horizon did not formally designate a stable branch liaison yet, which means it falls back on you
15:34:18 <ttx> anyone that would make a great choice ?
15:34:32 <ttx> We have Mathias Runge on the stable-maint list
15:34:39 <david-lyle> mrunge is the first that comes to mind
15:34:50 <david-lyle> yeah, same idea
15:34:52 <ttx> you may want to handle it too :)
15:34:59 <ttx> or not.
15:35:14 <david-lyle> I'll see if he's interested
15:35:26 <ttx> would be good to reach out to him. We plan to switch to new model in 10 days when 2014.2.1 is out
15:35:35 <ttx> ack
15:36:04 <ttx> ok, that's all I had at this early stage of the game. Questions on your side ?
15:36:33 <david-lyle> no, I'm set
15:36:45 <ttx> david-lyle: alright then. have a good day!
15:37:01 <david-lyle> ttx: you too
16:46:53 <notmyname> ttx: good morning
16:47:28 <ttx> #topic Swift
16:47:34 <ttx> notmyname: hi!
16:48:16 <ttx> what does the future hold for swift ?
16:48:43 <notmyname> hello
16:48:49 <notmyname> I have one big thing to chat with you about as an FYI
16:48:50 <notmyname> python-swiftclient
16:48:51 <notmyname> at the summit we talked about what's going on with swiftclient (we'd like to make big changes, but that's hard for compat reasons)
16:49:04 <notmyname> so what we agreed to at the summit was to focus new cSDK dev effort into openstack-sdk
16:49:09 <notmyname> https://etherpad.openstack.org/p/kilo-swift-swiftclient
16:49:16 <notmyname> see the bottom of that link
16:49:27 <notmyname> we'll keep developing CLI functionality in python-swiftclient
16:49:41 <notmyname> and of course we arent' throwing anything away or breaking anything for existing users
16:49:58 <notmyname> but we, as a dev group, want to focus new SDK feature dev work in openstack-sdk
16:50:27 <notmyname> ttx: what questions do you have?
16:50:36 <ttx> so the big changes you want to make are more client library than CLI ?
16:50:57 <notmyname> the big change is where dev effort for new stuff is focused
16:51:00 <ttx> and you'll use the existign python-swiftclient to handle compat ?
16:51:27 <notmyname> that's one possibility. I don't know the answer to that fully yet, since it's really early
16:51:40 <ttx> ok
16:51:48 <notmyname> ie there's a lot of work that has to be done in openstack-sdk before that even becomes realistic
16:52:23 <notmyname> the "Matt's plan" and my notes at the bottom of the etherpad are pretty much where we're at right now
16:52:50 <notmyname> and so I wanted to make sure you know early what we're talking about and panning
16:53:02 <notmyname> so realize this isn't anything that is close to done yet ;-)
16:53:20 <ttx> ok, all good
16:54:08 <ttx> do you plan a new version before end of year ? Or more next year at this point ?
16:54:09 <notmyname> please let me know what questions or advice you have :-)
16:54:18 <ttx> (on swift proper)
16:54:20 <notmyname> new version of swift? or SDK/CLI?
16:54:42 <ttx> SDK/CLI is obviously a bit further away :)
16:54:45 <notmyname> right
16:55:17 <notmyname> not sure about swift release yet. probably, but honestly I haven't looked at that yet
16:55:25 <notmyname> most swift effort is focused around EC right now
16:55:58 <ttx> notmyname: given that the end of year is really close now (if you count thanksgiving and the endof year holidays...) would be good to have a rough idea by next week ?
16:56:04 <notmyname> ya
16:56:13 <ttx> like "definitely not in December", or "maybe in December"
16:56:18 <notmyname> unfortunately I've got to run now. I have an online meetup starting in 4 minutes
16:56:22 <ttx> sure, no pb
16:56:24 <ttx> all I had anyway
16:56:29 <notmyname> ya, I'll have a better answer net week :-)
16:56:33 <notmyname> thanks
16:56:44 <ttx> morganfainberg: ready when you are
16:56:50 <morganfainberg> ttx o/
16:56:56 <ttx> #topic Keystone
16:57:24 <ttx> #link https://launchpad.net/keystone/+milestone/kilo-1
16:57:39 <ttx> Looks good to me. Expecting more to show up before k1 ?
16:57:54 <morganfainberg> i hope (if anything) just minor bugs that will get fixed along the way
16:58:00 <morganfainberg> but nothing major
16:58:18 <ttx> I see Dolph volunteered to handle stable branch liaison stuff
16:58:21 <morganfainberg> yeah.
16:58:29 <ttx> sounds good
16:58:37 <morganfainberg> makes my life easier :)
16:58:55 <ttx> we'll keep you in the future keystone-stable-maint team though :P
16:59:00 <morganfainberg> hehe.
16:59:18 <morganfainberg> i expect to jump through and do some stable reviews now that the cycle is getting under way
16:59:29 <ttx> ok, all lights seem to be green. Questions on your side ?
16:59:32 <morganfainberg> it's been a mad dash getting my feet under me as PTL.
17:00:01 <morganfainberg> the Cleanup token Providers might move to K2. but i think everything else is no questions
17:00:08 <morganfainberg> oh, i do have a question
17:00:13 <morganfainberg> your thoughts
17:00:51 <morganfainberg> python-keystoneclient, we'd like to do a rework of it - non-compatible, a v1.0.0 or v2 or whatever. Should this be a separate repository in that case?
17:01:11 <ttx> that sounds like a popular thing
17:01:37 <morganfainberg> yeah, there is a lot of potential cleanup that could be done, and we have a lot of tech debt (for compatibility reasons)
17:01:41 <morganfainberg> and CLI
17:02:03 <ttx> was discussing it with notmyname just before
17:02:39 <ttx> you can do the work in openstack-sdk and keep python-keystoneclient around for compat
17:02:43 <ttx> and CLI
17:02:53 <morganfainberg> yeah
17:03:06 <ttx> although if that gets more popular we could discuss it at a cross-project meeting
17:03:10 <morganfainberg> ++
17:03:15 <morganfainberg> thats it for me then.
17:03:21 <ttx> the agenda for today is a bit crowded, could that wait until next week ?
17:03:26 <morganfainberg> sure.
17:03:39 <ttx> ok, will add a note to remember it
17:03:46 <morganfainberg> this is a short week anyway, people are likely partially checked out in the US already
17:03:55 <ttx> right
17:04:55 <ttx> ok added
17:05:04 <ttx> morganfainberg: anything else ?
17:05:19 <morganfainberg> ttx, nope. will ping you if anything else comes up.
17:05:28 <ttx> morganfainberg: alrightn have a good day
17:05:37 <ttx> devananda: around ?
17:06:29 <devananda> ttx: hi!
17:06:37 <ttx> #topic Ironic
17:06:41 <ttx> #link https://launchpad.net/ironic/+milestone/kilo-1
17:07:03 <devananda> it's still a bit under-targeted - we've been doing a -lot- of spec work the last two weeks
17:07:03 <ttx> Those "unknown" statuses could be clarified, otherwise looks good
17:07:25 <devananda> there are now a lot more specs approved than are reflected on there, with a couple more big ones in the works
17:07:32 <ttx> devananda: don't forget you can add specs as "Blocked" if you want to track them as part of the milestone but they aren't approved specs yet
17:07:41 <devananda> refactoring our state machine is going to be, I hope, the largest change this cycle -- and several other things depend on that
17:07:54 <ttx> that conveys a more useful information than droping them from heavens on the last week :)
17:08:08 <devananda> ttx: ack. though at this stage, afaict, the majority of developers in Ironic are using specs, not LP
17:08:38 <ttx> devananda: I'd only track the ones that are team priorities
17:09:00 <ttx> craete a blueprint, then you can use https://review.openstack.org/#/c/108041/ to keep statuses up to date
17:09:20 <ttx> (still manual, but at least doesn't require to click on LP)
17:09:21 <devananda> oooh
17:09:28 <devananda> I'm using the old version (currently in tree)
17:09:50 <ttx> that new version (proposed) is compatible with not-yet-approved specs
17:09:53 <ttx> sets them to Blocked
17:10:08 <devananda> awesome. I'll pull that rev and try it today
17:10:15 <ttx> reveiws welcome
17:11:10 <devananda> other news ...
17:11:12 <ttx> in other news, adam_g is your stable liaison, but since Ironic wasn't part of the Juno release, you won't have point releases handled by the stable maint team anyway
17:11:24 <ttx> so I don't expect him to have a lot to do there
17:11:27 <devananda> we've changed our IRC meeting structure, and are starting to send weekly "status update" emails rather than take up meeting time with that
17:11:37 <ttx> he can still do backports and keep stable/juno sane I guess
17:11:50 <devananda> and we agreed to start alternating weekly meeting times
17:12:04 <ttx> sounds good
17:12:19 <devananda> ttx: great. also, I'm now auth'd for stable-maint team as well, so between adam_g and I, we can actually land fixes for stable/juno :)
17:13:31 <devananda> ttx: fwiw, time slots we agreed to are alternating between Monday 1700 UTC && Tuesday 0500 UTC
17:13:51 <devananda> i'll update the wiki today. do I have access to update the iCal feed, or is that something you still do?
17:14:04 <ttx> it's something someone volunteered to do
17:14:14 <ttx> he should track the wiki page changes
17:14:22 <ttx> will be a good test :)
17:14:27 <devananda> which someone? :)
17:14:36 <devananda> or just wait and see if he does?
17:14:50 <ttx> Tony Breeds
17:14:56 <ttx> no idea what's his irc nick was
17:15:04 <devananda> k k
17:15:22 <ttx> more questions ?
17:15:55 <devananda> nope
17:15:58 <ttx> alright then
17:16:07 <ttx> have a good day!
17:16:15 <devananda> you too!
17:16:39 <ttx> no Trove this week
17:16:42 <ttx> #endmeeting