*** mestery has quit IRC | 01:18 | |
*** mestery has joined #openstack-relmgr-office | 01:20 | |
*** mestery has quit IRC | 01:23 | |
*** mestery has joined #openstack-relmgr-office | 02:57 | |
*** david-lyle is now known as david-lyle_afk | 03:24 | |
*** mestery has quit IRC | 04:00 | |
*** mestery has joined #openstack-relmgr-office | 04:22 | |
*** mestery has quit IRC | 05:57 | |
*** russellb has quit IRC | 06:43 | |
*** russellb has joined #openstack-relmgr-office | 06:44 | |
*** SlickNik has joined #openstack-relmgr-office | 08:46 | |
SlickNik | ttx: around? | 08:47 |
---|---|---|
ttx | SlickNik: yes | 08:48 |
SlickNik | It looks like I'm double booked again for our 1:1 slot today. :( | 08:48 |
ttx | SlickNik: want to do it now ? | 08:48 |
SlickNik | Can we? That sounds good. | 08:49 |
ttx | #startmeeting ptl_sync | 08:49 |
openstack | Meeting started Tue Dec 9 08:49:03 2014 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:49 |
ttx | We can | 08:49 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:49 |
openstack | The meeting name has been set to 'ptl_sync' | 08:49 |
SlickNik | Thanks! | 08:49 |
ttx | #topic Trove | 08:49 |
ttx | So.. next week we have kilo-1 | 08:49 |
SlickNik | So I spent some time getting https://bugs.launchpad.net/trove/+milestone/kilo-1 in shape. | 08:49 |
ttx | The goal being to tag sometimes between the 16th and the 18th | 08:49 |
ttx | so on thos days, as soon as you're happy with the sahpe of master we can push the tag | 08:50 |
SlickNik | Yes. Working towards getting all the BPs that are on track reviewed and through. | 08:50 |
SlickNik | Soundsgood | 08:50 |
ttx | just send me a SHA and I'll make it happen | 08:50 |
ttx | https://launchpad.net/trove/+milestone/kilo-1 | 08:50 |
ttx | 7 in-progress blueprints to get in | 08:51 |
ttx | and 12 bugfixes still targeted | 08:51 |
ttx | next week we'll refine that list to cover true milestone blockers | 08:51 |
ttx | but the current list sounds reasonable to me | 08:51 |
SlickNik | Most of them are pretty close. | 08:52 |
SlickNik | Will sync with you on them again next week to check what we need to move out (if any). | 08:52 |
ttx | agreed | 08:52 |
ttx | No questions from me, you look in good shape | 08:52 |
SlickNik | Sounds good. That's pretty much all I had. | 08:53 |
SlickNik | Thanks for being flexible with the timing. | 08:53 |
ttx | no pb! | 08:54 |
ttx | talk to you next week | 08:54 |
SlickNik | Thank you — see you later at the x-project meeting. | 08:54 |
asalkeld | o/ | 08:55 |
ttx | asalkeld: o/ | 09:00 |
asalkeld | hi ttx | 09:00 |
ttx | #topic Heat | 09:00 |
asalkeld | #link https://launchpad.net/heat/+milestone/kilo-1 | 09:00 |
ttx | asalkeld: same comment, kilo-1 is next week, so the idea is to tag sometimes between the 16th and the 18th | 09:00 |
asalkeld | ok | 09:01 |
asalkeld | i might need to move one or two bp to k2 | 09:01 |
ttx | On those days, as soon as you're happy with the shape of master you send me a SHA and we can push the tag | 09:01 |
asalkeld | ok ttx sounds | 09:01 |
asalkeld | good | 09:01 |
ttx | (and defer the missed Bps to k2) | 09:01 |
asalkeld | sounds easy ;) | 09:01 |
ttx | it is easy | 09:01 |
ttx | especially since the milestone itself is not that important | 09:02 |
asalkeld | ok, yeah just intermediate | 09:02 |
ttx | the goal is just to avoid picking the wrong SHA, like if you wait for the last patch in a series implementing a feature, better wait a few more minutes :) | 09:02 |
asalkeld | sure, makes sense | 09:03 |
mikal | . | 09:03 |
ttx | https://blueprints.launchpad.net/heat/+spec/cinder-custom-constraints has no priority ? | 09:03 |
asalkeld | ttx, checking | 09:03 |
ttx | (is implemented already) | 09:04 |
ttx | and yes, depending how complex they are, decouple-nested lazy-load-outputs and multi-region-support might need to get pushed | 09:04 |
asalkeld | yeah, it was a very small bp | 09:04 |
asalkeld | decouple-nested - is looking big | 09:04 |
asalkeld | needs heaps of test code rework | 09:04 |
ttx | keep them in as long as you sincerely think they are likely to get in | 09:04 |
asalkeld | ok | 09:05 |
ttx | but defer them if you think they won't | 09:05 |
asalkeld | sure, makes sense | 09:05 |
ttx | Next week we'll refine again to only list milestone blockers | 09:05 |
ttx | so that we know what we are waiting on | 09:05 |
asalkeld | ok | 09:06 |
ttx | Do you need to merge anything more on the topic of env-nested-usability ? | 09:06 |
asalkeld | i just marked it done | 09:07 |
ttx | hah! | 09:07 |
ttx | alright then | 09:07 |
ttx | questions on your side ? | 09:07 |
asalkeld | no, all good | 09:07 |
asalkeld | thanks | 09:07 |
ttx | alright, have a good week! | 09:07 |
asalkeld | you too | 09:08 |
ttx | mikal: are you standing in for john, or should we just skip this week ? | 09:08 |
mikal | I am hot spare John | 09:09 |
mikal | Not that we've managed to overlap beforehand to brief | 09:09 |
mikal | But I am here for your release questioning needs | 09:09 |
ttx | let's try :) | 09:09 |
mikal | Also, I have questions about your bot | 09:09 |
ttx | #topic Nova | 09:09 |
ttx | ok let's start with the bot question | 09:09 |
mikal | Ok, so I approved four BPs Friday last week as part of our meeting | 09:10 |
mikal | I assigned a milestone etc | 09:10 |
ttx | did you set a priority ? | 09:10 |
mikal | And then your bot removed the milestone and slapped my wrist | 09:10 |
mikal | Obviously I've missed a step | 09:10 |
mikal | Ahhh, probably not? | 09:10 |
mikal | https://blueprints.launchpad.net/nova/+spec/hyperv-serial-ports is an example | 09:10 |
ttx | So the problem is... anybody can set a milestone. | 09:10 |
ttx | but only drivers can set a priority | 09:10 |
ttx | so we use the milestone+priority comboi to mean "approve" | 09:11 |
mikal | Fair enough | 09:11 |
ttx | and slap the wrists of anyone who dares to set milestone without priority | 09:11 |
mikal | I will retry with priorities set then | 09:11 |
ttx | it's an ugly workaround for Launchpad weird permission model around milestone targets | 09:11 |
ttx | I understand it can be surprising, that's why it's opt in and I explain it to people before they accept or reject it | 09:12 |
mikal | Ok, all fixed | 09:12 |
mikal | So all is well | 09:12 |
ttx | sorry about the "slap" | 09:12 |
mikal | Yeah, I think its because John has always done this for me | 09:12 |
mikal | I was just trying to help out while he was distracted | 09:13 |
mikal | Its all good, fixed now | 09:13 |
mikal | Next topic! | 09:13 |
ttx | https://launchpad.net/nova/+milestone/kilo-1 | 09:13 |
ttx | We'll tag kilo-1 between the 16th and 18th next week | 09:13 |
mikal | Yep | 09:13 |
ttx | so the list if probably a bit optimistic at this point | 09:13 |
mikal | A lot of that is going to get bumped I think | 09:13 |
mikal | Which is pretty normal | 09:13 |
ttx | it's good to refine it so that it represents your best guess as to what should make it | 09:14 |
mikal | We've also said that we will impose a spec approval deadline of kilo-1 as well | 09:14 |
ttx | but I expect John will do it | 09:14 |
mikal | So I need to remind people of that | 09:14 |
ttx | There are a few "unknown" status there that are probably not in good shape for next week | 09:14 |
mikal | I think if its not in "needs code review" or "implemented" its probably safe to bump | 09:14 |
mikal | But I will leave that to John | 09:14 |
ttx | yeah, usually at this point, not proposed = not in | 09:15 |
ttx | so I would remove at least 10 | 09:15 |
mikal | There's only 5 things in k-2 as well | 09:15 |
mikal | So being a bit more realistic there would be good | 09:15 |
ttx | and in the unlikely case they make it, we can put them back in k1 | 09:16 |
mikal | So, are things moved manually? | 09:16 |
mikal | Or is there a script for that? | 09:16 |
* mikal wonders if I should do some of it for John | 09:16 | |
ttx | I don't have a script for that. I could make one. But to be fair, only Nova has the volume of specs that makes such a "defer" script needed :) | 09:16 |
mikal | Heh, fair enough | 09:17 |
* mikal will move all the ones in "unknown" or "not started" as a first pass | 09:17 | |
ttx | well, horizon has an habit of targeting hundreds of bugs | 09:17 |
ttx | I may already have that script somewhere let me check | 09:17 |
ttx | hmm, no | 09:18 |
mikal | Its ok, I can just grind through | 09:18 |
mikal | Its only about ten | 09:18 |
ttx | last thing is https://bugs.launchpad.net/nova/+bug/1266262 | 09:18 |
ttx | targeted to k1 but no assignee | 09:18 |
ttx | probably unlikely to make it | 09:18 |
* mikal looks | 09:19 | |
ttx | but may be worth finding someone | 09:19 |
mikal | Sean Dague might have an opinion there | 09:19 |
mikal | I can ping him | 09:19 |
ttx | If you plan to try finding someone, you can keep it in | 09:19 |
ttx | we can clean up next week with "last minute blockers" | 09:20 |
mikal | Let's keep it for now | 09:20 |
mikal | Works for me | 09:20 |
ttx | vmware-vsan-support might be completed with https://review.openstack.org/#/c/74300/ | 09:20 |
* mikal looks | 09:21 | |
ttx | quiesced-image-snapshots-with-qemu-guest-agent might have been completed with https://review.openstack.org/#/c/72038/ | 09:21 |
mikal | How are you deciding which ones to call out like this? | 09:21 |
ttx | and hyper-v-smbfs-volume-support might have been completed with https://review.openstack.org/#/c/129235/ | 09:21 |
ttx | http://status.openstack.org/release/ | 09:21 |
ttx | I'm using this ^ | 09:21 |
ttx | shows merged reviews attached to blueprints. | 09:22 |
ttx | When one in-progress BP only shows merged stuff, I check the review to see if it looks like it's multipart of single-review | 09:22 |
ttx | or* | 09:22 |
mikal | Ok, well I shall ask people about those as well then | 09:23 |
ttx | In those cases those are recent merged, so might just be completed | 09:23 |
mikal | Cool | 09:24 |
mikal | What else do we need to cover tonight? | 09:24 |
ttx | Alright, I think we are good..; questions on your side ? | 09:24 |
mikal | Nup, I think I am good | 09:24 |
ttx | thx for stepping in! | 09:24 |
mikal | No problem! | 09:24 |
mikal | Cool, see you at the TC thing then! | 09:24 |
*** SergeyLukjanov has quit IRC | 10:48 | |
*** SergeyLukjanov has joined #openstack-relmgr-office | 10:50 | |
*** asalkeld has quit IRC | 11:28 | |
SergeyLukjanov | ttx, hello, /me ready when you are | 12:56 |
*** eglynn has joined #openstack-relmgr-office | 12:57 | |
ttx | SergeyLukjanov: will do eglynn first | 12:57 |
ttx | fwiw schedule is now at https://wiki.openstack.org/wiki/Release_Cycle_Management/1:1_Syncs | 12:57 |
SergeyLukjanov | ttx, yeah, just defining that I'm online :) | 12:57 |
ttx | eglynn: eady when you are | 12:58 |
ttx | +r | 12:58 |
eglynn | hey | 12:58 |
ttx | #topic Ceilometer | 12:58 |
eglynn | #link https://launchpad.net/ceilometer/+milestone/kilo-1 | 12:58 |
eglynn | I bumped the instance-restart BP to k2 due to lack of traction on the code reviews | 12:59 |
ttx | eglynn: we'll tag and publish kilo-1 next week, seomteimes between the 16th and 18th -- just give me a SHA when you're happy with the state of master | 12:59 |
eglynn | cool | 12:59 |
ttx | eglynn: those last 5 are still on track for k1 ? | 12:59 |
eglynn | only slight concern is declarative-http-tests since we've seen no code yet | 12:59 |
ttx | ok, defer it early if you learn more | 12:59 |
eglynn | I'll have a 1:1 with cdent later on today and make a call on whether it's still realistic | 13:00 |
eglynn | otherwise the rest are all on target | 13:00 |
ttx | next week we'll refien the list to only contain milestone blockers | 13:00 |
eglynn | cool | 13:00 |
ttx | OK, looks all good and reasonable | 13:00 |
ttx | questions on your side ? | 13:01 |
eglynn | nope all good ... I'll start populating the kilo-2 roster by EoW | 13:01 |
ttx | ack | 13:01 |
ttx | have a great day then | 13:01 |
ttx | SergeyLukjanov: ready? | 13:01 |
eglynn | you too ... thanks for your time! :) | 13:01 |
ttx | This is becoming too easy | 13:02 |
*** Kiall has quit IRC | 13:11 | |
*** Kiall has joined #openstack-relmgr-office | 13:11 | |
dhellmann | ttx: ready when you are | 13:11 |
ttx | dhellmann: ok, let's do it now | 13:12 |
ttx | #topic Oslo | 13:12 |
ttx | dhellmann: so next week we'll tag the incubator at some point and park kilo-1 over | 13:12 |
ttx | mark* | 13:12 |
dhellmann | k | 13:12 |
ttx | Just let me know of a time/SHA that seems appropriate, sometimes between the 16th and the 18th | 13:13 |
ttx | https://launchpad.net/oslo/+milestone/kilo-1 | 13:13 |
dhellmann | ok | 13:13 |
ttx | Are those two still in progress ? I think tooz is mostly done now, was renmaed | 13:14 |
*** eglynn is now known as eglynn-lunch | 13:14 | |
dhellmann | yeah, we need to update the review team settings in gerrit but that's it | 13:14 |
dhellmann | I'll get jd to do that today | 13:14 |
ttx | ok | 13:14 |
dhellmann | oh, and probably the launchpad settings, too | 13:14 |
ttx | what about the other one, graduate oslo.context ? | 13:14 |
dhellmann | dims is making good progress on that | 13:15 |
dhellmann | the code is ready, there are just a few release management things to do | 13:15 |
dhellmann | I think we can finish both by next week | 13:15 |
ttx | ack | 13:15 |
ttx | In other news, I reworked spec2bp to address your remarks, hopefully | 13:16 |
ttx | it's now oslo-projectgroup-aware | 13:16 |
dhellmann | ok, I'll take a look at the latest version | 13:16 |
ttx | and lets you specify the path to the spec when it's nonstandard and not stored in the UTL bp field | 13:16 |
ttx | URL* | 13:16 |
dhellmann | cool | 13:17 |
ttx | that's all I had I think -- questions on your side ? | 13:17 |
dhellmann | I added some stuff to the oslo-specs repo last week to refuse specs that don't have matching blueprints in launchpad | 13:18 |
dhellmann | so those names should always match now :-) | 13:18 |
ttx | oh, interesting. We could mention it at the specs cross-project meeting today | 13:18 |
dhellmann | sure | 13:18 |
dhellmann | I could put it in oslosphinx, to make it easier to share | 13:19 |
dhellmann | turn it on/off with some options | 13:19 |
ttx | OK, anything else ? | 13:19 |
dhellmann | nothing from me | 13:19 |
ttx | dhellmann: ok then, talk to you later! | 13:19 |
SergeyLukjanov | ttx, sorry, internet issue | 13:19 |
dhellmann | ttx: thanks! | 13:20 |
ttx | SergeyLukjanov: is it better now ? | 13:20 |
SergeyLukjanov | ttx, I hope so | 13:20 |
ttx | #topic Sahara | 13:20 |
ttx | SergeyLukjanov: so, same drill, k1 next week, tag between Tue and Thu | 13:20 |
SergeyLukjanov | ack | 13:20 |
SergeyLukjanov | #link https://launchpad.net/sahara/+milestone/kilo-1 | 13:20 |
* SergeyLukjanov going to cleanup plans before the 1-1 meeting next week | 13:21 | |
ttx | indirect-vm-access still likely to make it ? | 13:21 |
SergeyLukjanov | sounds like we have a few features that should be moved to k2 | 13:21 |
SergeyLukjanov | ttx, I think so, the spec was just approved | 13:21 |
SergeyLukjanov | ttx, moving to "needs code review" | 13:22 |
ttx | ok | 13:22 |
ttx | so we'll revisit the list next week to lmimit to last-minute milestone blockers | 13:22 |
SergeyLukjanov | ttx, yeah | 13:22 |
ttx | On the bugs side, would be good to refine the list at this point too | 13:23 |
ttx | Not enough assignees to make it | 13:23 |
SergeyLukjanov | ttx, yup, agree, will cleanup the list | 13:24 |
ttx | any reason why you use publish-to-pypi for sahara proper ? | 13:25 |
SergeyLukjanov | ttx, hm, I'm looking now | 13:25 |
SergeyLukjanov | ttx, actually I don't remember any objectives for it | 13:25 |
SergeyLukjanov | ttx, no py3X support, but it's like in all other projects :) | 13:25 |
ttx | ok, I'll propose a fix for it | 13:26 |
SergeyLukjanov | ttx, thanks | 13:26 |
ttx | hmm, what else... | 13:26 |
SergeyLukjanov | ttx, oh, one moment | 13:26 |
SergeyLukjanov | ttx, what's the issue of using publish-to-pypi? | 13:27 |
ttx | we only publish to pypi the libraries | 13:27 |
ttx | server code is signed/published to LP and tarballs.o.o | 13:28 |
SergeyLukjanov | ttx, okay, so, probably we should remove it from pypi | 13:28 |
ttx | so it's more a consistency thing | 13:28 |
ttx | thso that people don't start complaining about https://pypi.python.org/pypi/nova being stale | 13:28 |
SergeyLukjanov | ttx, we've been publishing sahara to pypi starting from the first release | 13:28 |
ttx | yes, was a convenient way to inherit the tarball jobs :) | 13:28 |
ttx | SergeyLukjanov: ok, that's all I had -- questions ? | 13:29 |
SergeyLukjanov | nope, thank you! | 13:29 |
ttx | cheers | 13:30 |
*** mestery has joined #openstack-relmgr-office | 13:59 | |
mestery | ttx: Just FYI, I'm in Utah this week for Neutron, I am planning to be at our 1:1, but if you're around now, I'm available now as well. | 14:14 |
mestery | For 10 minutes at least :) | 14:14 |
mestery | Otherwise, I'll catch you in 50 minutes | 14:15 |
ttx | mestery: o/ | 14:15 |
ttx | We can do it now | 14:15 |
mestery | Perfect! | 14:16 |
mestery | Thanks! | 14:16 |
ttx | #topic Neutron | 14:16 |
ttx | So we'll tag k1 next week, sometimes between the &6th and the 18th | 14:16 |
ttx | err 16th | 14:16 |
mestery | :) | 14:16 |
mestery | Excellent! | 14:16 |
ttx | just let me know when you're happy with the state of master | 14:16 |
mestery | YEs, we're at the sprint | 14:16 |
mestery | breaking services out this week | 14:16 |
mestery | I assume we'll tag those repositories too? | 14:17 |
mestery | It will be new for all of us | 14:17 |
ttx | so that's a good question | 14:17 |
mestery | Yes | 14:17 |
ttx | we can tag them alright. The question is more, what release model will apply to them | 14:17 |
ttx | is it more library like ? | 14:17 |
ttx | i.e. semver versioning, publish to pypi | 14:17 |
mestery | Yes, that's about right. They still depend on Neutron itself. | 14:18 |
ttx | or more companion tarballs | 14:18 |
mestery | Yes | 14:18 |
mestery | Let me think about this though | 14:18 |
mestery | I will figure it out today and let you know | 14:18 |
ttx | we need to check which jenkins jobs will apply to those, that's part of the split | 14:18 |
mestery | Yes, it's on our list of things to do today. | 14:19 |
mestery | And we need the co-gating jobs setup too, which will happen today as well | 14:19 |
ttx | From my perspective both options are on the table, we can certainly upload multiple tarballs in the "k1" milestone page on LP | 14:19 |
mestery | We have the new repos up with code, and reviews out to get them passing basic tests | 14:19 |
mestery | OK, cool | 14:19 |
ttx | and share versioning | 14:19 |
mestery | Excellent | 14:19 |
ttx | I think it boils down to how tightly integrated thsoe will be with neutron | 14:19 |
ttx | if they need synced releae, let's just share versioning and release all as components | 14:20 |
ttx | if the link between them is more loose... you could use a semver contract | 14:20 |
mestery | My gut feeling says lets do it that way for Kilo, post-Kilo we can think about separating them even more | 14:20 |
ttx | ok | 14:20 |
ttx | just keep me posted so that I can do a few checks in advance | 14:21 |
mestery | Ack, will do sir | 14:21 |
ttx | mestery: from a launchpad perspective, are those all tracked in same project, or different projects ? | 14:21 |
mestery | Same project, we're sharing both LP and neutron-specs for these | 14:22 |
ttx | ok, then it makes sense to share release | 14:22 |
mestery | Cool | 14:22 |
ttx | it's just a production artifact that they are released in separate tarballs instead of one | 14:22 |
ttx | at least for kilo. | 14:23 |
mestery | Yes, makes sense | 14:23 |
ttx | so yes, we'll tag them all, and should have -tarball jobs lined up to pick them up | 14:23 |
ttx | I'll check that my release scripts can handle that | 14:23 |
mestery | thanks! | 14:24 |
ttx | #action ttx to check that release scripts can handle the multi-tarball neutron split case | 14:24 |
ttx | https://launchpad.net/neutron/+milestone/kilo-1 | 14:24 |
ttx | 4 specs still in progress, all likely to make it by next week ? | 14:24 |
mestery | My guess is we land 4 of those, maybe 5, but next week. | 14:25 |
mestery | Sorry | 14:25 |
mestery | 2 of the 4 in progress, maybe 3 | 14:25 |
mestery | Total of 4-5 | 14:25 |
mestery | Also | 14:25 |
mestery | The split spec will be approved and done in K1 too | 14:25 |
ttx | OK, we'll refine the list next ween so that only last-minute milestone blockers are left | 14:25 |
mestery | It's a formality we need to get done today | 14:25 |
mestery | Cool | 14:25 |
ttx | ok, maybe add it to k1 as "Blocked" ? | 14:26 |
mestery | Yes, the sprint has been super useful this week with regards to getting coding done in person, thanks also to infra and QA over IRC! | 14:26 |
mestery | Will do | 14:26 |
ttx | OK, that's all the urgent stuff I had. Questions on your side ? | 14:26 |
mestery | Nothing else, the split was the main thing on my mind now. | 14:27 |
mestery | Thanks ttx! | 14:27 |
ttx | alright, have a good sprint! | 14:27 |
mestery | thanks! | 14:27 |
*** mestery has quit IRC | 14:29 | |
*** eglynn-lunch is now known as eglynn | 14:32 | |
dhellmann | ttx: +1 on the new spec2bp, thanks for making it work with oslo | 14:45 |
ttx | Cool, will let it bake for others comment for a few daysthen will merge it | 14:46 |
ttx | nikhil_k: around? | 15:20 |
nikhil_k | ttx: o/ | 15:20 |
ttx | #topic Glance | 15:20 |
ttx | nikhil_k: kilo-1 strikes next week | 15:20 |
nikhil_k | yeah! | 15:21 |
ttx | that means we'll push a k1 tag sometimes between the 16th and the 18th, whenevr you're happy enough with the state of master to send me a SHA | 15:21 |
*** david-lyle has joined #openstack-relmgr-office | 15:21 | |
ttx | https://launchpad.net/glance/+milestone/kilo-1 | 15:21 |
nikhil_k | ok, sounds good | 15:21 |
ttx | I see two "unknown" statuses there | 15:21 |
nikhil_k | ttx: they'r yet to be picked up | 15:22 |
ttx | nikhil_k: still likely to make it before next week ? | 15:22 |
nikhil_k | ttx: had given them a chance to get in k1. may be we can push them to k2 early next week | 15:22 |
nikhil_k | it's a small chance | 15:22 |
ttx | yes, we'll refine the list next week | 15:22 |
ttx | so that it only includes the last-minute milestone blockers | 15:23 |
nikhil_k | cool, that works! | 15:23 |
nikhil_k | ttx: was that all for me? | 15:25 |
ttx | sorry phone rang | 15:25 |
nikhil_k | ah k | 15:25 |
ttx | but sounds all good | 15:26 |
ttx | questions from you ? | 15:26 |
nikhil_k | had one smal one | 15:26 |
ttx | shall take a bit more time next week as we finally cull the list :) | 15:26 |
nikhil_k | what to do with the stable/icehouse review requests? | 15:26 |
ttx | nikhil_k: we'll set up the glance-stable-maint group tomorrow | 15:27 |
nikhil_k | ok nice | 15:27 |
ttx | so you shall be able to approve those yourself, as long as you follow stable policy | 15:27 |
nikhil_k | ah cool | 15:28 |
ttx | I'll keep you posted. We were waiting to get 2014.2.1 out of the way | 15:28 |
nikhil_k | gotcha | 15:28 |
ttx | I booked tomorrow afternoon with fungi to set that up | 15:28 |
nikhil_k | ttx: how is that group getting formed? | 15:28 |
ttx | starts with stable liaison | 15:28 |
nikhil_k | gotcha | 15:28 |
ttx | let me check the proposed group | 15:28 |
ttx | would be you and Erno | 15:29 |
ttx | to start | 15:29 |
nikhil_k | ttx: ok and we've liberty to add people | 15:29 |
nikhil_k | there are a few who we would like to be in there | 15:29 |
ttx | yes, the stable-maint-core group just needs to make sure they know stable policy before adding them | 15:30 |
ttx | so once we lectured them, we can add them | 15:30 |
nikhil_k | sounds good! | 15:30 |
ttx | reference: http://lists.openstack.org/pipermail/openstack-dev/2014-November/050390.html | 15:31 |
ttx | nikhil_k: note that there is a glance-oriented topic at meeting today | 15:31 |
ttx | osprofiler options naming | 15:31 |
nikhil_k | ttx: ah yes, I'd recommended that | 15:31 |
nikhil_k | will be there in the meeting | 15:32 |
ttx | alright | 15:32 |
ttx | nikhil_k: thx! | 15:32 |
ttx | thingee: around? | 15:32 |
nikhil_k | thanks too! | 15:32 |
thingee | ttx: o/ | 15:32 |
ttx | #topic Cinder | 15:32 |
ttx | So yeah, same warning... | 15:32 |
ttx | kilo-1 strikes next week | 15:32 |
ttx | that means we'll push a k1 tag sometimes between the 16th and the 18th, whenevr you're happy enough with the state of master to send me a SHA | 15:32 |
ttx | questions on that process ? | 15:33 |
thingee | ttx: a few of these are waiting for one more +2. I wasn't able to approve other merges since they were in bad shape for other reasons. | 15:33 |
thingee | ttx: nope | 15:33 |
ttx | https://launchpad.net/cinder/+milestone/kilo-1 | 15:33 |
ttx | cinder-drbd-volume-driver still likely to make it ? | 15:33 |
thingee | yes, just spoke with the assignee to have code for me today | 15:33 |
ttx | ok | 15:34 |
ttx | We'll refine the list next week so that only last-minute milestone tag blockers are left | 15:34 |
thingee | ttx: sure | 15:35 |
ttx | on the bugs side, one of them is targeted but not assigned: https://bugs.launchpad.net/cinder/+bug/1383460 | 15:35 |
ttx | Still liekly to make it ? | 15:35 |
ttx | I guess that's simple enough :) | 15:35 |
thingee | ttx: That can be closed likely. sample config is gone. | 15:35 |
thingee | ttx: I check it out | 15:35 |
thingee | i'll* | 15:35 |
ttx | ok, mark it invalid if that makes sense | 15:36 |
ttx | OK, looks all good. How is the "all drivers on k1" initiative working out so far ? | 15:36 |
thingee | great, I really do have code reviews for all and cert tests passing... drbd being my only special case :) | 15:37 |
ttx | ok | 15:37 |
ttx | Sounds all good to me. Questions on your side ? | 15:38 |
thingee | nothing. looking forward to core issues being taken care of in the next couple of milestones :) | 15:38 |
ttx | thingee: heh yes. | 15:38 |
ttx | thingee: ok then, have a good day! | 15:38 |
ttx | david-lyle: ready when you are | 15:38 |
thingee | ttx: have a good evening! | 15:39 |
david-lyle | ttx: ready | 15:39 |
ttx | #topic Horizon | 15:39 |
ttx | same warning about k1 striking next week | 15:39 |
ttx | https://launchpad.net/horizon/+milestone/kilo-1 | 15:39 |
david-lyle | We're in good shape for K-1 | 15:39 |
ttx | I see one "not started", still likely to make it ? | 15:40 |
ttx | https://blueprints.launchpad.net/horizon/+spec/mark-host-down-for-maintenance | 15:40 |
ttx | I guess https://review.openstack.org/#/c/103627/ makes it "started" at least | 15:40 |
david-lyle | It's ready for review actually | 15:40 |
ttx | ok, updating | 15:41 |
david-lyle | oops, stomped on your change I think | 15:41 |
ttx | those last 8 still stand a good chance of getting in before next week ? | 15:41 |
ttx | you win! | 15:41 |
david-lyle | put it as good progress, there's still a little discussion around the how | 15:42 |
david-lyle | I think we're in good shape | 15:42 |
ttx | OK, we'll readjust the list next week anyway so that it only contains the last-minute tag blockers | 15:42 |
ttx | On the bugs side, a couple unassigned targeted issues | 15:42 |
david-lyle | I won't block k-1 on any of them | 15:42 |
ttx | will you have people working on those, or is it better to just defer those to k2 now ? | 15:43 |
david-lyle | looking | 15:43 |
ttx | https://bugs.launchpad.net/python-keystoneclient/+bug/1282089 | 15:43 |
ttx | https://bugs.launchpad.net/horizon/+bug/1396194 | 15:43 |
david-lyle | let's move to k-2 | 15:44 |
david-lyle | I need to find owners | 15:44 |
ttx | ok, I'll let you do that | 15:44 |
david-lyle | sure | 15:44 |
ttx | alright, questions on your side ? | 15:44 |
david-lyle | no, I'm set | 15:45 |
ttx | cool, have a good day then, talk to you later! | 15:45 |
david-lyle | Sounds good, thanks! | 15:45 |
*** mestery has joined #openstack-relmgr-office | 15:55 | |
*** david-lyle has quit IRC | 16:20 | |
ttx | notmyname: ready when you are | 16:49 |
notmyname | ttx: good morning | 16:49 |
ttx | #topic Swift | 16:49 |
ttx | ohai | 16:49 |
notmyname | we're on track for the dates we discussed last week | 16:50 |
notmyname | tracking some things at | 16:50 |
notmyname | #link https://wiki.openstack.org/wiki/Swift/PriorityReviews | 16:50 |
notmyname | that's really all I've got | 16:50 |
ttx | 2.2.1 RC between dec 11 and 15 and final by the end of the week ? | 16:50 |
notmyname | yup | 16:50 |
ttx | nice long url | 16:51 |
notmyname | thank gerrit for that ;-) | 16:51 |
ttx | can I set up a 2.2.1 milestone in LP ? | 16:52 |
notmyname | yes | 16:52 |
notmyname | and I'll put stuff into it as we get closer | 16:52 |
ttx | ok doing it now | 16:52 |
ttx | You can start pushing stuff to it: https://launchpad.net/swift/+milestone/2.2.1 | 16:53 |
notmyname | thanks | 16:54 |
ttx | Alright, should be all set for next week | 16:54 |
ttx | notmyname: have a great day | 16:54 |
notmyname | you too | 16:54 |
ttx | Skipping keystone this week | 16:54 |
ttx | devananda: ready when you are | 17:03 |
devananda | ttx: hi! still working on my first cup of coffee | 17:04 |
devananda | ttx: so proceed at your own risk :) | 17:05 |
ttx | that... is fine | 17:05 |
* ttx treads carefully | 17:05 | |
ttx | #topic Ironic | 17:05 |
ttx | so... kilo-1 strikes next week | 17:05 |
devananda | we reviewed k1 plans last night | 17:05 |
ttx | that means we'll push a k1 tag sometimes between the 16th and the 18th, whenevr you're happy enough with the state of master to send me a SHA | 17:05 |
ttx | https://launchpad.net/ironic/+milestone/kilo-1 | 17:06 |
devananda | bumped one proposal, the rest are getting increased attentiona nd folks think they will make it | 17:06 |
ttx | what's up on new-ironic-state-machine ? | 17:06 |
devananda | also, the elephant from last week -- https://review.openstack.org/#/c/133828/ | 17:06 |
devananda | should be landing today | 17:06 |
devananda | that spec is representative of our -intention- | 17:06 |
devananda | not a specific piece of code | 17:06 |
ttx | so no real implementation yet ? | 17:06 |
devananda | I am doing the work, for now, of migrating the code to a state machine | 17:07 |
devananda | and then others will divy up the new aspects which that spec outlines | 17:07 |
ttx | OK, maybe you can close it as "informational" when done then, I think that communicates what it is quite well | 17:07 |
devananda | sounds good | 17:07 |
ttx | the other 3 are in good shape ? | 17:08 |
devananda | yup | 17:08 |
devananda | other news, I've been stalled a bit in planning our midcycle | 17:08 |
devananda | and need to get back on that this week | 17:08 |
devananda | i'll update the ML and wiki with details | 17:08 |
ttx | next week we'll refine the list to reduce it to milestone tag last minute blockers | 17:08 |
ttx | so should be slightly busier | 17:09 |
devananda | *nod* | 17:09 |
ttx | for today, nothing else from me. Questions from you ? | 17:09 |
devananda | nope | 17:09 |
devananda | cheers :) | 17:09 |
ttx | alright then, have a good day. Drink coffee | 17:10 |
ttx | that's all for today! | 17:10 |
ttx | #endmeeting | 17:10 |
openstack | Meeting ended Tue Dec 9 17:10:19 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:10 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-12-09-08.49.html | 17:10 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-12-09-08.49.txt | 17:10 |
openstack | Log: http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-12-09-08.49.log.html | 17:10 |
*** david-lyle_afk is now known as david-lyle | 17:58 | |
*** eglynn has quit IRC | 18:29 | |
*** eglynn has joined #openstack-relmgr-office | 18:48 | |
*** eglynn has quit IRC | 19:01 | |
*** eglynn has joined #openstack-relmgr-office | 19:26 | |
*** SlickNik has left #openstack-relmgr-office | 19:57 | |
*** asalkeld has joined #openstack-relmgr-office | 20:50 | |
*** mestery_ has joined #openstack-relmgr-office | 21:37 | |
*** mestery has quit IRC | 21:38 | |
*** mestery_ is now known as mestery | 21:51 | |
*** eglynn has quit IRC | 22:10 | |
*** asalkeld_ has joined #openstack-relmgr-office | 22:44 | |
*** asalkeld has quit IRC | 22:46 | |
*** asalkeld_ is now known as asalkeld | 23:07 | |
*** mestery has quit IRC | 23:50 | |
*** mestery has joined #openstack-relmgr-office | 23:59 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!