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