| *** mestery has quit IRC | 01:48 | |
| *** mestery has joined #openstack-relmgr-office | 03:41 | |
| *** mestery has quit IRC | 04:08 | |
| *** flaper87|afk is now known as flaper87 | 06:26 | |
| *** flaper87 is now known as flaper87|afk | 07:43 | |
| *** flaper87|afk is now known as flaper87 | 07:48 | |
| *** zz_johnthetubagu is now known as johnthetubaguy | 07:56 | |
| ttx | johnthetubaguy: ready when you are | 07:59 |
|---|---|---|
| johnthetubaguy | morning | 08:00 |
| ttx | #startmeeting ptl_sync | 08:00 |
| openstack | Meeting started Tue Sep 2 08:00:09 2014 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:00 |
| openstack | The meeting name has been set to 'ptl_sync' | 08:00 |
| ttx | #topic Nova | 08:00 |
| ttx | #link https://launchpad.net/nova/+milestone/juno-3 | 08:00 |
| johnthetubaguy | so, yeah, blueprints, yuck | 08:00 |
| ttx | #info 15 implemented, 45 in review | 08:00 |
| johnthetubaguy | so some improvements | 08:01 |
| ttx | That's only +7 in one week, and we have 0-2 days to go | 08:01 |
| johnthetubaguy | mikal has been pinging people directly to review the top few | 08:01 |
| johnthetubaguy | there are one or two almost there, the rest, well we probably should start to chop them I think | 08:01 |
| johnthetubaguy | I guess anything without a +2 at this point, is not going to make it, bar a miricle | 08:02 |
| ttx | Yes, we should allow the last 2 days for gate processing | 08:02 |
| johnthetubaguy | (+7 in one week is probably the best we have managed all release, buy yeah...) | 08:02 |
| johnthetubaguy | s/buy/but/ | 08:02 |
| ttx | So looking at the top ones... | 08:03 |
| ttx | https://blueprints.launchpad.net/nova/+spec/add-ironic-driver | 08:03 |
| johnthetubaguy | OK | 08:03 |
| *** mestery has joined #openstack-relmgr-office | 08:03 | |
| johnthetubaguy | I am told its closer than it looks | 08:03 |
| ttx | ok, so we keep it on the j3 list | 08:04 |
| johnthetubaguy | I think we have to, at this point | 08:04 |
| ttx | https://blueprints.launchpad.net/nova/+spec/compute-manager-objects-juno | 08:04 |
| ttx | This one we have to consider "complete at some point | 08:04 |
| johnthetubaguy | yeah, this one is ongoing, yeah | 08:05 |
| johnthetubaguy | I think thats probably today-ish | 08:05 |
| ttx | what's in-flight already approved for it ? | 08:05 |
| johnthetubaguy | I think some stuff was mostly with −1 from something on it | 08:05 |
| johnthetubaguy | but loads has merged | 08:05 |
| johnthetubaguy | https://review.openstack.org/#/q/topic:bp/compute-manager-objects-juno,n,z | 08:05 |
| johnthetubaguy | I will try catch dansmith when he comes online | 08:06 |
| johnthetubaguy | (and nikola) | 08:06 |
| johnthetubaguy | https://blueprints.launchpad.net/nova/+spec/vmware-spawn-refactor | 08:07 |
| ttx | yeah, ideally we would only pursue the ones that make it a bit more logicaly complete | 08:07 |
| johnthetubaguy | I approved a chuck of those yesterday | 08:07 |
| johnthetubaguy | ttx: yeah, good point, but not sure its really that neat right now, will check | 08:07 |
| ttx | i.e. what REALLY needs to merge so that Juno looks like something vs. what could merge | 08:07 |
| ttx | Is it all contained in ?ttps://review.openstack.org/#/q/topic:bp/vmware-spawn-refactor,n,z | 08:08 |
| ttx | Is it all contained in https://review.openstack.org/#/q/topic:bp/vmware-spawn-refactor,n,z ? | 08:08 |
| johnthetubaguy | well, probably nothing in here, it was more high priority because its blocking loads of the other vmware bits | 08:08 |
| johnthetubaguy | I think the answer is kinda of no, but it has the most important bits after the oslo patch, I think | 08:09 |
| johnthetubaguy | I think I probably block all the patches not on that list | 08:09 |
| ttx | basically, starting tomorrow morning I think we should defer everything that is not already approved and in-flight | 08:10 |
| johnthetubaguy | right | 08:10 |
| johnthetubaguy | thats a good line to draw | 08:10 |
| ttx | that leaves today for the last +2s | 08:10 |
| johnthetubaguy | sounds fair | 08:10 |
| johnthetubaguy | well, agreed that still makes it very tight | 08:10 |
| ttx | and to trace a line in the sand for ongoing stuff like the objects work | 08:10 |
| ttx | So for this morning I would defer/-2 everything that is just far from makign it | 08:11 |
| johnthetubaguy | yeah, stuff with −1s etc | 08:11 |
| ttx | only keep the stuff that is 80% there at least, and which could possibly be approved today | 08:11 |
| *** morganfainberg is now known as morganfainberg_Z | 08:12 | |
| johnthetubaguy | right, the lows I have no idea on right now, but the mediums are mostly not done, from what I saw yesterday | 08:12 |
| ttx | johnthetubaguy: want us to go through them ? | 08:12 |
| ttx | (the mediums) | 08:12 |
| johnthetubaguy | maybe pick some examples | 08:12 |
| johnthetubaguy | actually, not sure its worth it | 08:13 |
| johnthetubaguy | some have −2s with fix up this patch first, etc | 08:13 |
| ttx | hmm yeah | 08:13 |
| johnthetubaguy | they can go | 08:13 |
| ttx | wondering if https://blueprints.launchpad.net/nova/+spec/per-aggregate-disk-allocation-ratio is not completed | 08:14 |
| johnthetubaguy | some just have, sorry on holiday will fix this next week notices on them, but the boat has kinda sailed now | 08:14 |
| johnthetubaguy | oops, yeah, I merged that, so if its through the gate now, we should be good | 08:14 |
| johnthetubaguy | yep, done, thanks | 08:14 |
| johnthetubaguy | there some API ones that most people seem to have avoided reviewing, but will see how they are looking this morning | 08:16 |
| ttx | yeah, no other obvious candidate | 08:16 |
| johnthetubaguy | anyways, I think I know what we have to do I guess, just been putting off the mass −2 stuff | 08:16 |
| ttx | so yeah, we should probably communicate that anything that's not in-flight by tomorrow morning will be deferred | 08:17 |
| ttx | maybe I should just send that overall | 08:17 |
| johnthetubaguy | oh, that would be cool | 08:17 |
| ttx | Like, it's Juno feature day | 08:17 |
| johnthetubaguy | + stuff looking blocked at this point, will probably get deferred today, I guess | 08:17 |
| ttx | yep | 08:18 |
| johnthetubaguy | awesome | 08:18 |
| johnthetubaguy | at least it will feel consistently painful, if that makes sense | 08:18 |
| ttx | OK, I think we'll use the meeting today to go through the list again | 08:18 |
| ttx | so I won't ask for topics | 08:18 |
| ttx | :) | 08:18 |
| johnthetubaguy | ah, thats a good plan | 08:18 |
| johnthetubaguy | about summit stuff, when is that due to open up? | 08:19 |
| ttx | johnthetubaguy: anything else? | 08:19 |
| ttx | We still need to decide how we want to handle that part | 08:19 |
| johnthetubaguy | just saying, because we are thinking of requiring specs for feature like submitions | 08:19 |
| ttx | I feel like it's a bit unproductive to open a general CFP | 08:19 |
| ttx | I think teams working on etherpads can do a better job at it | 08:20 |
| johnthetubaguy | yeah, I guess we need to make that feel as open, and give people feedback somehow | 08:20 |
| ttx | but first I need to check if the space allows for the setup I proposed | 08:20 |
| johnthetubaguy | but maybe thats just a meeting | 08:20 |
| ttx | I should know about that today | 08:20 |
| johnthetubaguy | ah, cool | 08:20 |
| johnthetubaguy | anyways, I am sure you have that all in hand, just checking timescales really | 08:21 |
| ttx | well, the original plan was to open yesterday | 08:21 |
| ttx | but since we're talking about format changes | 08:21 |
| ttx | ... | 08:21 |
| johnthetubaguy | OK | 08:21 |
| ttx | ok, will send that email now | 08:21 |
| ttx | talk to you later? | 08:22 |
| *** mestery has quit IRC | 08:22 | |
| johnthetubaguy | later is fine | 08:22 |
| johnthetubaguy | yeah, I will trawl through the list, and see what I can do to tidy things up a bit | 08:22 |
| johnthetubaguy | thanks for the help, as always :) | 08:23 |
| *** mestery has joined #openstack-relmgr-office | 08:23 | |
| *** flaper87 is now known as flaper87|afk | 08:37 | |
| *** flaper87|afk is now known as flaper87 | 08:50 | |
| *** mestery has quit IRC | 08:52 | |
| *** mestery has joined #openstack-relmgr-office | 08:52 | |
| *** mestery has quit IRC | 10:15 | |
| *** mestery has joined #openstack-relmgr-office | 10:15 | |
| *** mestery has quit IRC | 10:21 | |
| *** mestery has joined #openstack-relmgr-office | 10:22 | |
| *** eglynn_ has joined #openstack-relmgr-office | 11:16 | |
| eglynn_ | ttx: knock, knock ... back to our usual 1:1 slot? | 11:45 |
| *** mestery has quit IRC | 11:46 | |
| ttx | yes | 11:46 |
| ttx | #topic Ceilometer | 11:46 |
| eglynn_ | BTW hat-tip to gordc for keeping on top of things while I was on vacation | 11:46 |
| ttx | #link https://launchpad.net/ceilometer/+milestone/juno-3 | 11:46 |
| ttx | yes, he did a very good job! | 11:46 |
| eglynn_ | LP doesn't quite capture the full status | 11:46 |
| eglynn_ | 4 of 11 BPs merged, but another 3 are approved and wending their way thru' the gate as we speak | 11:46 |
| ttx | which ones? | 11:46 |
| eglynn_ | which leaves 4 outsanding (1 high, 2 medium, 1 low) | 11:46 |
| eglynn_ | which ones are gating? | 11:47 |
| ttx | So like I said in a recent email to -dev, ideally startig tomorrow morning we would only keep the ones that are in-flight | 11:47 |
| ttx | yes, which ones are gating | 11:47 |
| eglynn_ | central-agent-partitioning, hash-based-alarm-partitioning, xenapi-support | 11:47 |
| ttx | because i expect it will take 1+ day to get approved stuff through, with the obvious retries | 11:47 |
| eglynn_ | yeap | 11:48 |
| eglynn_ | the high priority BP bigger-data-sql is a bit of a concern at this stage, as the review has stalled out on differing performance test results being seen | 11:48 |
| eglynn_ | (different mysql versions etc) | 11:48 |
| eglynn_ | I'll speak to gordc about that when he comes online (out for Labor Day yesterday) | 11:48 |
| eglynn_ | but, fair warning, I *may* be coming cap-in-hand looking for a FFE on bigger-data-sql to allow time to get more clarity on the performance improvement | 11:48 |
| eglynn_ | on the medium BPs ... | 11:49 |
| ttx | yeah, and that one isn't exactly the kind you would like to grant a Feature Freeze exception for | 11:49 |
| ttx | because it's potentially disruptive | 11:49 |
| eglynn_ | yeah, I'll have a better view later on today on whether that might be required | 11:49 |
| ttx | and affects existing functionality | 11:49 |
| eglynn_ | yeap, fair point | 11:49 |
| ttx | I mean, if it's just a couple extra days away, why not, but I suspect there is more | 11:50 |
| eglynn_ | fair enough, I'll bear that in mind | 11:50 |
| eglynn_ | on the mediums ... | 11:50 |
| eglynn_ | grenade-resource-survivability is still waiting on review attention from jogo & sdague | 11:50 |
| eglynn_ | (again, Labor Day yesterday not ideal) | 11:50 |
| eglynn_ | paas-event-format-for-ceilometer is documentation-only, but review has stalled so I'm prepared to bump it off the juno slate if necessary | 11:50 |
| ttx | eglynn_: but I think we said that one can merge post-j3 | 11:51 |
| ttx | (grenade one) | 11:51 |
| eglynn_ | cool | 11:51 |
| ttx | maybe we can push it to rc1 already | 11:51 |
| eglynn_ | yeah, that's fair | 11:51 |
| ttx | it's only extra tests, right ? | 11:51 |
| eglynn_ | exactly, tests only | 11:51 |
| eglynn_ | on paas-event-format-for-ceilometer, I've mailed Phil though to given him fair warning and an opportunity to close it out | 11:51 |
| ttx | ok, moving to RC1 | 11:51 |
| eglynn_ | on the low priority BP still outstanding ... | 11:52 |
| eglynn_ | ipmi-support has patches up, but not yet in a landeable state | 11:52 |
| eglynn_ | ... I'm not massively concerned about it missing tho, as it's just an alternative way of generating the same IPMI sensor data that Ironic already notifies us about | 11:52 |
| ttx | ok, shall be deferred tomorrow if it doesn't get approved today? | 11:53 |
| eglynn_ | yeah if not in flight by EoD, definitely a candidate for bumping | 11:53 |
| eglynn_ | on the j3 targetted bugs, I've bumped the higher priority bugs to RC1 that didn't look like they were going to make it | 11:53 |
| eglynn_ | cdent just did a trawl thru all the outstanding reviews for the lower-priority j3-targetted bugs | 11:54 |
| ttx | ok, we'll just bump to RC1 anything not fixcommitted by tag | 11:54 |
| eglynn_ | cool, that's reasonable | 11:54 |
| ttx | OK, you seem in good shape | 11:56 |
| eglynn_ | so what time on Thurs are you aiming to pull the trigger on the juno-3 tag? | 11:56 |
| ttx | 6 left, 3 in flight, 2 which might get bumped, 1 that you could ask FFE for | 11:56 |
| ttx | When all the features in the pipe land | 11:56 |
| eglynn_ | yep, that sums it up | 11:56 |
| eglynn_ | cool enough | 11:56 |
| ttx | ideally sometimes during the day :) | 11:57 |
| ttx | but highly dependent on gate load | 11:57 |
| eglynn_ | BTW cdent tells me he just got a +2 from Sean on the grenade patch | 11:57 |
| ttx | shall we bump to rc1 the doc-only one ? | 11:57 |
| eglynn_ | so we may be able to re-instate that to juno-3, as I think jogo is pretty much on board with the approach | 11:57 |
| eglynn_ | yeap, let's do that re. the paas-event-format | 11:58 |
| ttx | if it makes it we'll retroactively readd it to j3 | 11:58 |
| ttx | but in the meantime we should bump all the non-featury stuff | 11:58 |
| eglynn_ | cool | 11:58 |
| eglynn_ | cool paas-event-format-for-ceilometer bumped to rc1 | 11:58 |
| ttx | #info In flight: central-agent-partitioning, hash-based-alarm-partitioning, xenapi-support | 11:59 |
| ttx | #info Shall get bumped if not approved today: ipmi-support | 11:59 |
| ttx | #info Might get FFE-d if not approved today: bigger-data-sql | 12:00 |
| ttx | We'll update that picture at the meeting tonight | 12:00 |
| ttx | eglynn_: thx!: | 12:00 |
| ttx | SergeyLukjanov: around? | 12:01 |
| eglynn_ | #info may be reinstated if approved today: grenade-resource-survivability | 12:01 |
| SergeyLukjanov | ttx, yup | 12:01 |
| ttx | #topic Sahara | 12:01 |
| SergeyLukjanov | #link https://launchpad.net/sahara/+milestone/juno-3 | 12:01 |
| ttx | SergeyLukjanov: is that current ? Not a lot of progress since last week | 12:02 |
| SergeyLukjanov | hm, looks like it's a bit outdated | 12:02 |
| ttx | SergeyLukjanov: could you update it now? We can discuss it afterwards | 12:02 |
| SergeyLukjanov | we're moving two huge blueprints to K and adding one very small, already implemented | 12:03 |
| SergeyLukjanov | it's required for backward compat support between older versions | 12:03 |
| SergeyLukjanov | I'll update the lp page right now | 12:03 |
| ttx | SergeyLukjanov: let me know when you're done | 12:05 |
| SergeyLukjanov | ack | 12:05 |
| *** mestery has joined #openstack-relmgr-office | 12:06 | |
| SergeyLukjanov | ttx, good news - we've implemented integration w/ ceilometer (sending notifications), all user faced strings are now wrapped for translation using i18n and all sahara objects could be created using heat resources (it's in the gate now) | 12:07 |
| SergeyLukjanov | ttx, am I right that it's ok to work on docs, tests and critical bug fixes after the j3? | 12:09 |
| ttx | yes | 12:09 |
| ttx | You can actually push back doc-only and test-only blueprints to RC1 already | 12:09 |
| ttx | that would add clarity | 12:09 |
| SergeyLukjanov | ttx, ok | 12:11 |
| *** mestery_ has joined #openstack-relmgr-office | 12:12 | |
| ttx | SergeyLukjanov: are you done with the J3 status update? | 12:13 |
| *** mestery has quit IRC | 12:13 | |
| SergeyLukjanov | ttx, mostly yes | 12:14 |
| ttx | SergeyLukjanov: which, if any of those, is currently gating? | 12:15 |
| SergeyLukjanov | there are two bps - https://blueprints.launchpad.net/sahara/+spec/edp-swift-trust-authentication that is re-invented way for working with swwift data sources, it fix critical security issue re storing credentials | 12:15 |
| ttx | that one is gating ? ^ | 12:16 |
| SergeyLukjanov | and https://blueprints.launchpad.net/sahara/+spec/cluster-persist-sahara-configuration that is needed for backward compat, both could be moved to rc1 due to their "bugfix" nature | 12:16 |
| SergeyLukjanov | oh, sorry, it's not about gating | 12:16 |
| ttx | oh ok | 12:16 |
| SergeyLukjanov | no changes in gate right now | 12:17 |
| ttx | SergeyLukjanov: we would probably have to grant a FFE for the first one, but i wouldn't consider it a bugfix | 12:17 |
| SergeyLukjanov | we have a small rebase bomb exploaded | 12:17 |
| ttx | since you need new feature code to plug the hole | 12:17 |
| ttx | and probably for the second one too | 12:17 |
| ttx | but those would still be exceptions | 12:18 |
| SergeyLukjanov | ttx, yup, I meen that I'd like to ask for the FFE for this two bps because of their importance and "bugfix" *nature* | 12:18 |
| ttx | #info edp-swift-trust-authentication & cluster-persist-sahara-configuration still in progress, will probably require FFEs | 12:18 |
| SergeyLukjanov | for the second one code is ready and not approved only because of labor day in US :) | 12:18 |
| SergeyLukjanov | and spec isn't approved officially too (it was discussed on the last IRC meeting and we've agreed that we need it) | 12:19 |
| ttx | cluster-persist-sahara-configuration is not j3 | 12:19 |
| ttx | should it be added there ? | 12:19 |
| SergeyLukjanov | ttx, yup, but spec isn't approved | 12:19 |
| ttx | add it with "Blocked" status | 12:20 |
| SergeyLukjanov | ttx, ok, thx | 12:20 |
| SergeyLukjanov | ttx, done | 12:20 |
| ttx | if we know we'll require it, I prefer it tracked/Blocked | 12:20 |
| ttx | Of the 4 "needs code review", should they all just get deferred if they are not approved today? | 12:21 |
| SergeyLukjanov | ttx, I think so | 12:21 |
| ttx | ok | 12:22 |
| ttx | #info cluster-secgroups, swift-url-proto-cleanup-deprecations, ceilometer-integration, anti-affinity-via-server-groups to be edferred if they don't get required approvals today | 12:22 |
| ttx | SergeyLukjanov: OK, I think that's all | 12:23 |
| SergeyLukjanov | ok, thx | 12:23 |
| ttx | SergeyLukjanov: thx! | 12:23 |
| ttx | dhellmann: around? | 12:23 |
| dhellmann | ttx: here | 12:23 |
| ttx | #topic Oslo | 12:23 |
| dhellmann | the new project group looks good; we probably should have done this a while back | 12:24 |
| ttx | dhellmann: so the only unintended sideeffect of the oslo projectgroup transition so far seems to be the BP link hack in gerrit | 12:24 |
| dhellmann | yeah, is that something we can fix in gerrit, or should we link to our blueprints differently? | 12:24 |
| ttx | it's a bit tricky | 12:24 |
| ttx | the BP name is unique in a LP project namespace, not unique in general | 12:25 |
| ttx | so when you say "blueprint foo-bar", gerrit rseolves that to a search for blueprints names foo-bar in the openstack projectgroup namespace | 12:25 |
| ttx | Like https://blueprints.launchpad.net/openstack/?searchtext=ceilometer-integration | 12:26 |
| ttx | which was a suboptimal hack already | 12:26 |
| dhellmann | I would be ok if we had to say "blueprint oslo/foo-bar" and gerrit found that oslo prefix | 12:26 |
| ttx | we could fix that by making the link smarter | 12:27 |
| ttx | like if no project is specified, search in the smae project as the basename of the repo | 12:27 |
| dhellmann | interesting | 12:28 |
| ttx | so if a review for openstack/nova contains "blueprint foo-bar" you would look for nova/foo-bar | 12:28 |
| dhellmann | right | 12:28 |
| dhellmann | that would still make it possible for us to link to blueprints across projects, which is something we do when we submit changes to infra and the requirements project to add a new lib | 12:28 |
| ttx | and if a review for openstack-infra/config contains blueprint oslo.rootwrap/moo then you would look for oslo.rootwrap/moo | 12:28 |
| dhellmann | right | 12:29 |
| dhellmann | that seems like a good solution to me | 12:29 |
| ttx | I fear that the linkification code is pretty basic though | 12:29 |
| ttx | might be a basic pattern subst IIRC | 12:29 |
| ttx | so not sure you can feed it the repo name | 12:29 |
| dhellmann | probably, but we should be able to specify 2 patterns, I would think | 12:30 |
| dhellmann | if the bp name includes / do one thing, otherwise do what we're doing now | 12:30 |
| dhellmann | ah, true | 12:30 |
| ttx | oh, default to openstack namespace search | 12:30 |
| dhellmann | yeah | 12:30 |
| ttx | that would work, I guess | 12:30 |
| dhellmann | that way all of the old links work the same way | 12:30 |
| ttx | i should build an oslo library release script to handle Lp duties automatically | 12:31 |
| dhellmann | that would be great to have | 12:31 |
| ttx | one question: in every oslo lib, would you track only released versions ? or alphas as milestones as well? | 12:31 |
| ttx | i.e. for olso.rootwrap, would we have a1, a2 milestones ? | 12:32 |
| ttx | I think it would make sense for intra-cycle planning | 12:32 |
| ttx | BUt then I need to think twice about the meaning of fixReleased | 12:32 |
| ttx | We could track alphas, and then do consolidation like we do for the openstack integrated release | 12:32 |
| dhellmann | I created juno-3 and juno-rc1 milestones for all of them so far, but now that you mention it I think we agreed to just use "next" and rename them with a version number when we do the release | 12:32 |
| ttx | so.. finals only ? No way of knowing that a fix/feature is available in an alpha? | 12:33 |
| dhellmann | oh, no, I mean I would run something like "release_oslo_lib.sh oslo.rootwrap 1.0.0.0a3" and it would rename "next" to that version number | 12:33 |
| dhellmann | and fix up all of the commited bugs, etc. | 12:34 |
| ttx | ah I see | 12:34 |
| ttx | would you consolidate all alphas into a single final release page ? | 12:34 |
| dhellmann | we don't necessarily know in advance if the next release is an alpha or the final, since we might only cut one alpha during a cycle for example | 12:35 |
| ttx | i.e. when you do the final "release" you would move all alphas bugs and features to the final | 12:35 |
| *** mestery has joined #openstack-relmgr-office | 12:35 | |
| dhellmann | oh, hmm | 12:35 |
| *** mestery_ has quit IRC | 12:35 | |
| dhellmann | I don't know if we would want that or not | 12:35 |
| ttx | the way it's done in the integrated release is.. | 12:35 |
| ttx | you have -rcX | 12:35 |
| ttx | then you add a 2014.2 milestone | 12:35 |
| ttx | move over all juno-X and juno-rcX bugs/features to it | 12:36 |
| ttx | and mark that released | 12:36 |
| dhellmann | ok, I guess that makes sense then | 12:36 |
| ttx | that way during dev you know when something is available | 12:36 |
| ttx | but after dev you shall forget the alphas | 12:36 |
| dhellmann | we still have release notes to see when a fix actually went in, but if consolidating at the end of the cycle is the pattern used for the apps that's good | 12:36 |
| ttx | yes, git history still tracks what landed when if you really need to know | 12:37 |
| ttx | OK, so I might need to do two scripts, one for the "next" and one for the "final" | 12:37 |
| dhellmann | yeah | 12:37 |
| ttx | is the final aligned on the last alpha ? i.e. the same commit ends up tagged twice ? | 12:38 |
| ttx | release-candidate style ? | 12:38 |
| dhellmann | I would expect that to be the case, yes | 12:38 |
| ttx | ok, so one alpha-release script and one "promote-alpha" one | 12:38 |
| dhellmann | we do have some libs with versions < 1.0 that aren't alphas per-se, and I guess we would treat those the same way | 12:38 |
| dhellmann | we didn't use alpha tags for some technical reason having to do with the mirror syncing | 12:39 |
| ttx | yeah, it wouldn't be sensitive to the actual version number used anyway | 12:39 |
| dhellmann | yeah | 12:39 |
| ttx | OK, sounds like a plan | 12:39 |
| ttx | #link https://launchpad.net/oslo/+milestone/juno-3 | 12:39 |
| dhellmann | now, if that script could send email to the -dev list, that would save me an extra step, too :-) | 12:39 |
| ttx | we can work on that :) | 12:40 |
| ttx | Now I suspect a few of those should now move to their specific projects | 12:40 |
| ttx | https://blueprints.launchpad.net/oslo-incubator/+spec/rootwrap-daemon-mode -> oslo.rootwrap | 12:40 |
| ttx | will do that asap | 12:40 |
| dhellmann | yeah, I asked the library owners to clean up the bugs already via the ML | 12:41 |
| dhellmann | I don't remember if I asked for the bps too | 12:41 |
| ttx | first time I see this cross-project-sharing-same-milestone view. It's not bad | 12:41 |
| ttx | almost makes me want the libs to use the common milestones :) | 12:41 |
| dhellmann | hmm, the shared view is going to be harder if we use "next" instead of "juno-3" | 12:41 |
| dhellmann | heh | 12:42 |
| ttx | #link https://launchpad.net/oslo-incubator/+milestone/juno-3 | 12:42 |
| ttx | Let's look at that one instead ^ | 12:42 |
| dhellmann | k | 12:42 |
| ttx | Semantic version support for pbr -> pbr probably | 12:42 |
| dhellmann | yes | 12:43 |
| ttx | My question is... what on this list is still oslo-incubator work taht would be subject to FF | 12:43 |
| dhellmann | I put it in the incubator because of the specs2bp script, I think | 12:43 |
| ttx | the "graduate" stuff we already know is not affected | 12:43 |
| ttx | shall we move all the "graduate" ones to rc1 ? | 12:43 |
| dhellmann | yes, that's fair at this point | 12:44 |
| ttx | (if it makes it this week you can retroactively target it here) | 12:44 |
| ttx | ok, I'm on it | 12:44 |
| dhellmann | I think the concurrency and serialization ones are almost done, but we might as well move all of them | 12:44 |
| * dhellmann thinks about ff | 12:44 | |
| * ttx craetes "next" milestones for rootwrap and pbr so that we can move stuff there | 12:45 | |
| dhellmann | all of this work is actually happening in a library outside of the incubator | 12:45 |
| ttx | actually calling the milestone next-juno | 12:47 |
| dhellmann | not juno-next like the numbered ones? | 12:47 |
| dhellmann | I guess it doesn't matter | 12:48 |
| ttx | no, there already is a next-juno for.. swift iirc | 12:48 |
| ttx | OK, reload https://launchpad.net/oslo-incubator/+milestone/juno-3 | 12:48 |
| ttx | Is that all oslo-incubator work ? | 12:48 |
| dhellmann | the mysql one goes in oslo.db | 12:48 |
| ttx | Adoption of pylock file could move to RC1 too | 12:48 |
| dhellmann | the 2 owned by josh harlow go in taskflow | 12:49 |
| dhellmann | yes, we can move the adoption one to rc1 | 12:49 |
| dhellmann | the policy configuration directories is an incubator change | 12:49 |
| ttx | not sure I can update the taskflow stuff | 12:49 |
| ttx | also weird series there | 12:49 |
| ttx | oh, I can | 12:50 |
| dhellmann | yeah, josh has been using semver numbering. I need to get him to give me access there so I can update it | 12:50 |
| ttx | Looks liek we get power from the projectgroup | 12:50 |
| dhellmann | ah, ok | 12:50 |
| ttx | OK: https://launchpad.net/oslo-incubator/+milestone/juno-3 | 12:51 |
| ttx | and https://launchpad.net/oslo/+milestone/next-juno | 12:52 |
| *** eglynn_ has quit IRC | 12:52 | |
| ttx | oh, the mysql one | 12:52 |
| dhellmann | sec, brb | 12:53 |
| dhellmann | sorry, hungry cats don't understand "you need to wait a minute" | 12:54 |
| ttx | That leaves policy-configuration-directories | 12:54 |
| dhellmann | the policy stuff is in the incubator, so that's the right place for that one | 12:54 |
| dhellmann | should we move any of the closed items, or is that just going to end up being confusing? | 12:55 |
| ttx | Shall it get bumped to kilo if it fails to get reviewed/apprved today ? | 12:55 |
| * dhellmann looks at that changeset | 12:55 | |
| ttx | We should move the closed items yes | 12:55 |
| ttx | use-events-for-error-wrapping should be in oslo.db? | 12:55 |
| dhellmann | yes | 12:56 |
| ttx | ok, moving | 12:56 |
| ttx | Now, that's simpler | 12:56 |
| dhellmann | I moved the config bug | 12:57 |
| dhellmann | and the db bug | 12:58 |
| ttx | ok, good cleanup | 12:58 |
| ttx | one question this creates is... | 12:58 |
| ttx | shouldn't the libs also be feature frozen and get their final alphas soon ? | 12:58 |
| dhellmann | yes, probably so | 12:59 |
| dhellmann | anything that's already been released once this cycle, at least | 12:59 |
| ttx | Maybe we can address that next week | 12:59 |
| dhellmann | I have a couple of releases to do, I was going to put those off to monday to avoid issues this week | 12:59 |
| ttx | but you should issue a fair warning to lib people | 12:59 |
| dhellmann | yeah, I'll do that this morning | 13:00 |
| ttx | we cna have feature-"final" alphas | 13:00 |
| ttx | we shall have* | 13:00 |
| ttx | even if we can still work on bugfixes in the coming week(s) | 13:00 |
| dhellmann | right | 13:00 |
| ttx | we shoudl also probably target a date for final releases | 13:00 |
| ttx | ideally before RC1s | 13:01 |
| dhellmann | I was thinking sept 18 | 13:01 |
| ttx | so that we can have the requirements all set | 13:01 |
| ttx | Sept 18 would work | 13:01 |
| ttx | oslo.rootwrap is all set | 13:02 |
| ttx | (final feature alpha already out) | 13:02 |
| dhellmann | great! | 13:02 |
| ttx | dhellmann: ok, I think that's all I wanted to discuss | 13:02 |
| ttx | more later! | 13:02 |
| dhellmann | ok, tty this afternoon | 13:03 |
| *** flaper87 is now known as flaper87|afk | 13:06 | |
| dhellmann | ttx, still around? | 13:15 |
| ttx | dhellmann: yes | 13:16 |
| dhellmann | ttx: I forgot to ask about cutting stable/juno for the incubator early | 13:16 |
| ttx | when do you want to cut it ? | 13:16 |
| dhellmann | well, I had wanted to do it today but bnemec's comments on the ML thread made me reconsider -- did you see his reply? | 13:17 |
| ttx | yeah | 13:18 |
| ttx | I figured this could wait for a bit mre discussion | 13:18 |
| dhellmann | ok | 13:18 |
| dhellmann | ttx: I'm having second thoughts about consolidating the alpha milestones at the end of a cycle. If someone wants to see what was released in a version, can't they just look at the page for the whole series? | 13:24 |
| ttx | dhellmann: It's tricky. there is no single page for bugs in series for example | 13:28 |
| ttx | I mean bugs fixed in series | 13:28 |
| ttx | Only milsetone pages show the list of bugfixes and implemented features | 13:28 |
| *** eglynn_ has joined #openstack-relmgr-office | 13:29 | |
| ttx | jgriffith: i'm available if you are | 14:02 |
| dolphm | ttx: i also wouldn't mind going early; need to be on the road soonish | 14:02 |
| ttx | dolphm: ddeal | 14:04 |
| ttx | #topic Keystone | 14:04 |
| ttx | #link https://launchpad.net/keystone/+milestone/juno-3 | 14:04 |
| ttx | 2 left | 14:04 |
| ttx | https://blueprints.launchpad.net/keystone/+spec/keystone-to-keystone-federation | 14:04 |
| dolphm | that's going to be our next 48 hours ^ | 14:05 |
| dolphm | overview of pending changes: https://gist.github.com/dolph/651c6a1748f69637abd0 | 14:05 |
| dolphm | we landed the biggest patch for k2k last night, which was blocking the rest... and the rest are much simpler | 14:06 |
| ttx | dolphm: ok. The trick is you need to allow time for gate processing | 14:06 |
| dolphm | yeah :( | 14:06 |
| ttx | so ideally that would be all approved today :) | 14:06 |
| dolphm | that is my goal! | 14:06 |
| dolphm | and i think it's achievable | 14:06 |
| dolphm | the last patch for v3 api validation is basically a nice to have add-on. the rest of that bp is done | 14:06 |
| ttx | i suspect we would ask for FFE on the k2k stuff if it misses | 14:07 |
| ttx | What about the other ? | 14:07 |
| dolphm | for k2k, i would | 14:07 |
| dolphm | for v3 api validation, i'd just mark it as Implemented and file a wishlist bug for the remaining patch and move it to Kilo | 14:07 |
| ttx | ok | 14:07 |
| ttx | #info keystone-to-keystone-federation still pending some reviews, would require FFE if it misses | 14:08 |
| ttx | #info api-validation still pending some reviews, would defer to kilo the remaining items if it misses | 14:08 |
| ttx | I'll just defer all bugs that don't make it to RC1, too | 14:09 |
| ttx | I don't see any milestone-critical stuff there | 14:09 |
| dolphm | i also haven't triaged bugs in a week, so there might be some surprises in there. i'll review the new stuff as soon as we're gating the last change for k2k | 14:10 |
| ttx | OK, I think that is all. You can run! | 14:10 |
| dolphm | thank you :) | 14:10 |
| dolphm | ttyl | 14:10 |
| ttx | mestery: you can go early if you want | 14:21 |
| mestery | ttx: o/ | 14:21 |
| ttx | #tpoic Neutron | 14:21 |
| mestery | You caught me just after I got back from walking kids to school (first day here today) | 14:22 |
| ttx | #topic Neutron | 14:22 |
| *** david-lyle has joined #openstack-relmgr-office | 14:22 | |
| ttx | first day today too | 14:22 |
| mestery | Hey, congrats on the new role ttx! Well deserved. :) | 14:22 |
| ttx | mestery: thanks! | 14:22 |
| ttx | #link https://launchpad.net/neutron/+milestone/juno-3 | 14:22 |
| ttx | 19 implemented, +9 since last week | 14:23 |
| mestery | Yes, we should land a few more today yet, some are close | 14:23 |
| ttx | So the trick is, we need to allow for gate time | 14:23 |
| mestery | And the 3 big ones we're tracking (L3 HA, ipset, and security group refactor) are fairly close as well, looking like ipset may need an FFE, but the other 2 look good | 14:23 |
| mestery | ack on gate time | 14:24 |
| ttx | so ideally we'd get them approved today and wait until they navigate the gate tomorrow, in time for tagging Thursday | 14:24 |
| mestery | Yes | 14:24 |
| ttx | A bit concerned with all those "High" still up | 14:24 |
| ttx | since it sounds like a recipe for a lot of exceptions | 14:24 |
| mestery | The majority of those are all going to the incubator | 14:24 |
| mestery | So I've left them in Juno-3 for now but we will move them once the incubator is up | 14:25 |
| ttx | ah, hm. | 14:25 |
| mestery | Group Policy and LBaaS stuff | 14:25 |
| ttx | how could we... get them off the list somehow | 14:25 |
| mestery | Create a new milestone for the incubator perhjaps? | 14:25 |
| ttx | creating a launchpad project is a bit early | 14:25 |
| mestery | Would thatm ake sense? | 14:25 |
| ttx | yeah, i was thinking that would work | 14:25 |
| ttx | I can create a "incubator" target | 14:25 |
| mestery | Cool | 14:26 |
| mestery | Once you do, I'll move stuff out of J3 | 14:26 |
| ttx | and then we can move all the work that will escape FF there | 14:26 |
| ttx | ok, let's do that now | 14:26 |
| mestery | Awesome! | 14:26 |
| * mestery waits for it so he can migrate stuff in real time | 14:26 | |
| ttx | https://launchpad.net/neutron/+milestone/incubator | 14:26 |
| mestery | OK, I'll move things after we're done talking so I can focus here ;) | 14:27 |
| mestery | thanks! | 14:27 |
| ttx | hmm, actually it's hard to discuss unless I see what's left after the cleanup | 14:27 |
| mestery | OK doing it now ;) | 14:27 |
| ttx | awesome :) | 14:27 |
| *** mestery_ has joined #openstack-relmgr-office | 14:31 | |
| mestery_ | Sorry, connectivity issue there for a moment, but I am back now. | 14:32 |
| mestery_ | So, the list should be clean now of LBaaS and GBP BPs | 14:32 |
| mestery_ | The two testing BPs (https://blueprints.launchpad.net/neutron/+spec/retargetable-functional-testing and https://blueprints.launchpad.net/neutron/+spec/remove-unit-test-autodeletion) won't make Thursday and will need FFEs if we want them | 14:32 |
| mestery_ | The owners already pinged me on those, I'll move htem out for now as well. | 14:32 |
| *** mestery has quit IRC | 14:33 | |
| mestery_ | ttx: How does it look now? | 14:34 |
| ttx | are they testing-only ? | 14:34 |
| ttx | i.e. they only touch tests/ code ? | 14:34 |
| mestery_ | Yes, but the owner didn't want to use scarce infra resources this week, so an FFE would make al ot of sense | 14:35 |
| ttx | in which case they don't need FFE | 14:35 |
| mestery_ | Ah, ok, cool! Thanks! | 14:35 |
| ttx | It's fine to merge extra tests or doc | 14:35 |
| ttx | until RC1 | 14:35 |
| *** mestery_ is now known as mestery | 14:35 | |
| ttx | so you can move them to RC1 already | 14:35 |
| mestery | OK, thanks! | 14:35 |
| ttx | you should move them to RC1 actually | 14:35 |
| ttx | that will make the list more limited | 14:35 |
| mestery | Yes | 14:36 |
| mestery | It looks better now, I can likely clear a few more ones out today after talking to owners | 14:36 |
| ttx | Is there anything all-approved and in-flight already ? Or are those all waiting on extra reviews ? | 14:36 |
| mestery | Most of these have multiple patches, some approved and some in flight, and some waiting on approval | 14:36 |
| mestery | So, all over the board I guess :( | 14:37 |
| ttx | what about neutron-dvr-fwaas and ml2-hierarchical-port-binding ? | 14:37 |
| ttx | The other two "High" you said were in good shape | 14:38 |
| mestery | dvr-fwaas is ready for review, we'll need an FFE for it to make FWaaS work with DVR | 14:38 |
| mestery | ml2-hiearchichal-port-binding is also out, but I don't think that one qualifies for an FFE if it won't make it | 14:38 |
| mestery | ml2-hiearchical can likely wait for kilo if it won't make it, I'll talk to rkukura to verify that | 14:39 |
| ttx | Should ml2-hiearchichal-port-binding be meidum and security-group-rules-for-devices-rpc-call-refactor be high ? | 14:39 |
| ttx | Try to keep the ones you would ask FFE for as "High" | 14:39 |
| mestery | I think so, yes. | 14:39 |
| * mestery updates that now | 14:39 | |
| mestery | Done | 14:39 |
| ttx | so.. ideally if it's not fully approved and in-flight tomorrow morning, we shoudl defer it | 14:40 |
| mestery | Ack | 14:41 |
| ttx | at least for the medium/low ones | 14:41 |
| mestery | Agreed | 14:41 |
| ttx | OK, we'll talk again at the meeting and tomorrow morning | 14:41 |
| ttx | #info 33 blueprints still under review | 14:42 |
| mestery | Thanks! | 14:42 |
| ttx | #info Only the 4 Highs are likely to trigger FFEs | 14:42 |
| ttx | #info planning to defer what is not fully approved and in-flight tomorrow morning | 14:42 |
| ttx | mestery: thx! | 14:42 |
| mestery | ttx: Thank you too! Talk to you tomorrow. | 14:42 |
| ttx | david-lyle: ready when you are | 14:42 |
| david-lyle | ttx: ready | 14:43 |
| ttx | #topic Horizon | 14:43 |
| ttx | #info 20 implemented, +11 since last week | 14:43 |
| ttx | #info 18 blueprints left open | 14:43 |
| ttx | david-lyle: so the general idea would be to defer what is unlikely to be fully approved today | 14:44 |
| ttx | david-lyle: and tomorrow we defer anythign that is not fully approved and in-fliught in the gate | 14:44 |
| ttx | so that we have time for retries at the gate before the tag on Thursday | 14:44 |
| david-lyle | ttx: sounds good, we have a couple of potential FFEs that may not make Thurs | 14:45 |
| ttx | So that means working on final approvals today | 14:45 |
| david-lyle | sure | 14:45 |
| ttx | david-lyle: which ones for potential FFEs ? | 14:45 |
| david-lyle | the FFEs are mostly delayed due to other service dependencies | 14:45 |
| david-lyle | IPv6 support | 14:45 |
| ttx | that's a good reason for them | 14:45 |
| ttx | maybe we can mark them "High" priority to show that we'll likely FFE them | 14:46 |
| david-lyle | and there are a few around the new glance meta-data functionality | 14:46 |
| ttx | #info Likely FFEs for IPv6 support and a few around the new glance meta-data functionality | 14:47 |
| david-lyle | I'll bump them then | 14:47 |
| ttx | Are you OK in general for deferring stuff that won't be fully-approved and in gate hell tomorrow ? | 14:47 |
| david-lyle | yeah, I'll have a better idea after the Horizon meeting in an hour | 14:48 |
| ttx | ok | 14:48 |
| david-lyle | then I'll start deferring bps | 14:48 |
| ttx | OK, we'll be in touch again at the meeting, and tomorrow | 14:48 |
| david-lyle | I think 3-4 should still land without FFE | 14:48 |
| david-lyle | sound good | 14:49 |
| david-lyle | *sounds | 14:49 |
| ttx | david-lyle: ok, thx! | 14:49 |
| david-lyle | ttx: thanks | 14:50 |
| ttx | jgriffith: you can fit in 10 minutes now if you hurry up | 14:50 |
| *** markmcclain has joined #openstack-relmgr-office | 15:15 | |
| *** markmcclain has quit IRC | 15:16 | |
| *** markmcclain has joined #openstack-relmgr-office | 15:18 | |
| ttx | stevebaker: ready when you are | 15:42 |
| *** SlickNik has joined #openstack-relmgr-office | 15:49 | |
| ttx | SlickNik: ready when you are | 16:04 |
| SlickNik | ttx: here now | 16:04 |
| ttx | #topic Trove | 16:04 |
| ttx | #link https://launchpad.net/trove/+milestone/juno-3 | 16:04 |
| ttx | Still 4 to go | 16:04 |
| ttx | Are any of those already approved and in-flight ? | 16:05 |
| SlickNik | 2 of them have 1 +2, and are looking for another. | 16:05 |
| SlickNik | ANother one is really close to done, and I think I'm going to have to defer one of them. | 16:05 |
| ttx | So, tomorrow we'll just defer anything that is not in-flight | 16:06 |
| ttx | that leaves today for the last push | 16:06 |
| SlickNik | ttx: sounds good — I've already communicated that to the rest of the team. | 16:07 |
| SlickNik | I'll make sure to keep the status updated as thing are on the move. | 16:07 |
| ttx | Anything you'd request FFE for if it can't get the requires approvals in time ? | 16:07 |
| SlickNik | We have one FFE that will probably come in after. | 16:08 |
| SlickNik | Move to oslo.messaging. | 16:08 |
| ttx | hmm, ok. we'll discuss that then :) | 16:08 |
| ttx | that's all I had. Will be talking to you again tomorrow | 16:08 |
| SlickNik | Okay sounds good. Will keep working on getting the BPs reviewed and closed out. | 16:09 |
| SlickNik | Thanks! | 16:09 |
| *** morganfainberg_Z is now known as morganfainberg | 16:11 | |
| *** mestery_ has joined #openstack-relmgr-office | 16:16 | |
| ttx | OK, will be back at 18:30 UTC | 16:19 |
| ttx | stevebaker: maybe we cna talk then | 16:19 |
| *** mestery has quit IRC | 16:19 | |
| *** mestery has joined #openstack-relmgr-office | 16:26 | |
| *** mestery_ has quit IRC | 16:30 | |
| *** eglynn_ has quit IRC | 17:29 | |
| *** markwash__ has joined #openstack-relmgr-office | 17:49 | |
| *** mikal_ is now known as mikal | 17:50 | |
| markwash__ | ttx: ping | 17:52 |
| *** johnthetubaguy is now known as zz_johnthetubagu | 18:26 | |
| ttx | markwash__: pong? | 18:36 |
| markwash__ | pong, indeed | 18:36 |
| ttx | markwash__: ready for a glance status update? | 18:36 |
| markwash__ | ttx as ready as I'll ever be :-) | 18:36 |
| ttx | #topic Glance | 18:36 |
| ttx | #link https://launchpad.net/glance/+milestone/juno-3 | 18:37 |
| ttx | Is that current? | 18:37 |
| markwash__ | ttx I think there was some movement this past weekend I'm not certain about | 18:38 |
| markwash__ | I know the metadata definitions catalog has moved along nicely | 18:38 |
| markwash__ | it is probably "Implemented" at this point | 18:38 |
| markwash__ | async processing and "restrict users" are accurate tmk | 18:38 |
| ttx | markwash__: https://review.openstack.org/#/c/111483/ may still be needed for metadata def catalog | 18:39 |
| markwash__ | ah yes | 18:40 |
| markwash__ | but the prereqs have merged | 18:40 |
| ttx | markwash__: today is like the last day to approve features, starting tomorrow we'll cut what's not in flight and it will require FFE if you want it in Juno | 18:40 |
| markwash__ | yeah | 18:40 |
| ttx | so it migth be worth a few extra reviews to get them past the last hurdle | 18:41 |
| ttx | Anything you're likely to ask a FFE for ? | 18:41 |
| markwash__ | Actually, depending on the status, I will ask for an FFE for all of those save GPFS | 18:41 |
| ttx | OK, i'll bump restrict to Medium then | 18:42 |
| markwash__ | yeah that issue was in good shape except we hit some snags pulling in changes from oslo-incubator policy | 18:42 |
| markwash__ | had to cherry-pick oslo-incubator (effectively) to bring things to a workable state for juno | 18:43 |
| ttx | We'll do another status update tomorrow, and defer what won't land in time then | 18:43 |
| markwash__ | ttx: what time do you want? | 18:43 |
| ttx | and we'll discuss FFEs after J3 on Friday | 18:43 |
| ttx | markwash__: same as today? | 18:43 |
| markwash__ | should work | 18:43 |
| markwash__ | thanks | 18:43 |
| ttx | I'll try to be around | 18:43 |
| ttx | #info FFEs likely for everything but GPFS | 18:44 |
| ttx | markwash__: thanks for coming! | 18:44 |
| markwash__ | ttx: sorry I was late. . I got confused by the long weekend | 18:44 |
| ttx | that happens :) | 18:46 |
| *** flaper87|afk is now known as flaper87 | 18:49 | |
| ttx | stevebaker: around? | 19:18 |
| ttx | bah, I guess we'll sync during the release meeting then | 19:19 |
| ttx | #endmeeting | 19:20 |
| openstack | Meeting ended Tue Sep 2 19:20:00 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 19:20 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-09-02-08.00.html | 19:20 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-09-02-08.00.txt | 19:20 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-09-02-08.00.log.html | 19:20 |
| *** markwash__ has quit IRC | 19:22 | |
| *** markwash__ has joined #openstack-relmgr-office | 19:27 | |
| *** morganfainberg is now known as needs | 19:57 | |
| *** needs is now known as needscoffee | 19:57 | |
| stevebaker | ttx: \o | 19:59 |
| ttx | stevebaker: starting TC meeting, talk to you during release meeting in one hour ? | 19:59 |
| stevebaker | ttx: ok | 19:59 |
| *** dhellman_ has joined #openstack-relmgr-office | 20:39 | |
| *** mestery has quit IRC | 20:53 | |
| *** mestery has joined #openstack-relmgr-office | 20:55 | |
| *** needscoffee is now known as morganfainberg | 20:56 | |
| *** flaper87 is now known as flaper87|afk | 21:09 | |
| *** morganfainberg is now known as steve_notmorgan | 21:32 | |
| *** steve_notmorgan is now known as morganfainberg | 21:32 | |
| *** dhellman_ has quit IRC | 21:54 | |
| *** markwash__ has quit IRC | 22:33 | |
| *** markwash__ has joined #openstack-relmgr-office | 22:35 | |
| *** david-lyle has quit IRC | 23:02 | |
| *** markwash__ has quit IRC | 23:08 | |
| *** markwash__ has joined #openstack-relmgr-office | 23:10 | |
| *** markmcclain has quit IRC | 23:37 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!