Tuesday, 2014-09-09

*** markwash__ has quit IRC01:07
*** markwash__ has joined #openstack-relmgr-office01:33
*** mestery has quit IRC01:57
*** mestery_ has joined #openstack-relmgr-office01:57
*** markwash__ has quit IRC02:04
*** arnaud has joined #openstack-relmgr-office02:53
*** Azher has joined #openstack-relmgr-office03:00
*** arnaud__ has joined #openstack-relmgr-office03:02
*** markwash__ has joined #openstack-relmgr-office03:04
*** markwash__ has quit IRC03:21
*** openstack has joined #openstack-relmgr-office03:41
*** sendak.freenode.net sets mode: +ns 03:41
*** sendak.freenode.net sets mode: -o openstack03:46
-sendak.freenode.net- *** Notice -- TS for #openstack-relmgr-office changed from 1410234112 to 138867215803:46
*** sendak.freenode.net sets mode: +ct-s 03:46
*** dolphm has joined #openstack-relmgr-office03:46
*** ttx` has joined #openstack-relmgr-office03:46
*** stevebak` has joined #openstack-relmgr-office03:46
*** flaper87 has joined #openstack-relmgr-office03:46
*** arnaud__ has joined #openstack-relmgr-office03:46
*** Azher has joined #openstack-relmgr-office03:46
*** arnaud has joined #openstack-relmgr-office03:46
*** mestery_ has joined #openstack-relmgr-office03:46
*** redrobot has joined #openstack-relmgr-office03:46
*** morganfainberg has joined #openstack-relmgr-office03:46
*** jgriffith has joined #openstack-relmgr-office03:46
*** dhellmann has joined #openstack-relmgr-office03:46
*** devananda has joined #openstack-relmgr-office03:46
*** zz_johnthetubagu has joined #openstack-relmgr-office03:46
*** jraim__ has joined #openstack-relmgr-office03:46
*** SlickNik has joined #openstack-relmgr-office03:46
*** zaneb has joined #openstack-relmgr-office03:46
*** russellb has joined #openstack-relmgr-office03:46
*** mattoliverau has joined #openstack-relmgr-office03:46
*** notmyname has joined #openstack-relmgr-office03:46
*** SergeyLukjanov has joined #openstack-relmgr-office03:46
*** sdague has joined #openstack-relmgr-office03:46
*** mikal has joined #openstack-relmgr-office03:46
*** dansmith has joined #openstack-relmgr-office03:46
*** Kiall has joined #openstack-relmgr-office03:46
*** anteaya has joined #openstack-relmgr-office03:46
*** mordred has joined #openstack-relmgr-office03:46
*** ChanServ has joined #openstack-relmgr-office03:46
*** sendak.freenode.net sets mode: +o ChanServ03:46
*** sendak.freenode.net changes topic to "OpenStack Release Managers office - Where weekly 1:1 sync points between release manager and PTLs happen - Logged at http://eavesdrop.openstack.org/irclogs/%23openstack-relmgr-office/"03:46
*** arnaud__ has quit IRC03:46
*** arnaud has quit IRC04:29
*** stevebak` is now known as stevebaker04:32
*** markwash__ has joined #openstack-relmgr-office04:38
*** arnaud has joined #openstack-relmgr-office04:43
*** flaper87 has quit IRC06:22
*** flaper87 has joined #openstack-relmgr-office06:22
*** arnaud has quit IRC06:42
*** markwash__ has quit IRC07:34
*** Azher has quit IRC07:46
*** zz_johnthetubagu is now known as johnthetubaguy08:06
*** ttx` is now known as ttx10:47
*** ttx has quit IRC10:48
*** ttx has joined #openstack-relmgr-office10:48
*** johnthetubaguy is now known as zz_johnthetubagu11:06
*** eglynn has joined #openstack-relmgr-office11:43
eglynnttx: knock, knock :)11:45
ttxeglynn: hola11:46
ttx#startmeeting ptl_sync11:46
openstackMeeting started Tue Sep  9 11:46:37 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.11:46
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.11:46
openstackThe meeting name has been set to 'ptl_sync'11:46
ttx#topic Ceilometer11:46
eglynn#link https://launchpad.net/ceilometer/+milestone/juno-rc111:46
ttxAre thos 3 blueprints the only FFEs you consider ?11:47
* ttx parses the ML for any request11:47
eglynnyes11:47
ttxok let's go through them, top to bottom11:47
ttxhttps://blueprints.launchpad.net/ceilometer/+spec/bigger-data-sql11:48
ttxhow far are we on this one?11:48
eglynnthe main patch to remornalize the resource schema is approved and working it way thru' the gate as we speak11:48
eglynn*remnormalize :)11:48
ttxok, found it11:48
ttxis there any followup patch?11:49
eglynnthe second patch to switch from sql-a ORM to sql-a core is still under review11:49
eglynnMike Bayer (sql-a author) has helpfully chimed into the discussion11:49
ttxthat would be https://review.openstack.org/#/c/113524/ ?11:49
eglynnyes11:50
ttx#info pending on https://review.openstack.org/#/c/113524/ and https://review.openstack.org/#/c/111313/11:50
eglynnwe need some further quantification of the performance gains, but it should be landable11:50
ttxhttps://blueprints.launchpad.net/ceilometer/+spec/paas-event-format-for-ceilometer11:50
ttxwhat about this one11:50
eglynnapproved, working its way thru the gain11:50
eglynn*thru the gate11:50
eglynnthat's documentation only, non-controversial11:51
ttxah ok11:51
ttx#info Doc-only11:51
ttxforgot about that11:51
ttxhttps://blueprints.launchpad.net/ceilometer/+spec/ipmi-support11:51
eglynnimpi-support is still the furthest away from landing11:51
eglynnEdwin is engaging with the reviews, but the TZ latency adds to the delay11:52
ttxthat's the two reviews at https://review.openstack.org/#/q/topic:bp/ipmi-support,n,z ?11:52
eglynnlast week I signalled that this one would be expected to land last of the 311:52
eglynnyes11:52
ttx#info https://review.openstack.org/#/q/topic:bp/ipmi-support,n,z -- a bit far away still11:52
ttxok, that looks in good shape11:52
ttxIdeally the SQL stuff would merge this week11:53
eglynnyep, agreed11:53
ttxthe IMI stuff can wait until next Tuesday11:53
ttxIPMI*11:53
eglynnyes, that's fair11:53
ttxthen we'll rediscuss it11:53
eglynndo you have a concrete date in mind for cutting RC1?11:53
eglynn... or driven by actual progress in landing stuff?11:54
ttxnot really... it's normally when you empty your release-critical bug list11:54
eglynnOK, got it11:54
ttxso you should target the "must fix before release" bugs to rc111:54
ttxthen depending on how fast you burn that list, we adapt11:54
ttxideally the RC1 would appear before the end of the month11:55
ttxbut if everything looks good and you have no bugs, then it could appear next week, I guess11:55
ttxeglynn: about the design summit, one question11:55
eglynnright, I'll give the currently targetted bug list another trawl and punt anything non-critical that doesn't look like it's getting traction11:55
eglynnshoot11:55
ttxIf we do meetup-style on the Friday, would you rather have one full day, or only half a day?11:55
ttxi.e. would half-a-day be sufficient ?11:56
eglynnI'd rather take the full day, even if folks are a bit zombie-ish by the afternoon11:56
ttxok11:56
eglynn(seeing as the pod-time will otherwise be limited)11:56
ttxtrying to do a trade-off between comfort and time11:56
eglynnis there an alternative event in mind for the Friday afternoon, or more an early finish?11:57
ttxyou can spend time in other meetup rooms, or leave early11:57
ttxthough some will get a Friday afternoon half-day, that's the nature of the game11:57
eglynnyeah, making it kinda optional like that would be fine11:57
ttxok. Anything you'd like to discuss at meeting today?11:58
eglynnnope, I'm good11:58
ttxeglynn: cool, talk to you later!11:58
eglynnthank you for your time!11:58
ttxSergeyLukjanov: ready when you are11:58
SergeyLukjanovttx, I'm here12:02
SergeyLukjanovttx, morning12:02
ttx#topic Sahara12:02
ttxhttps://launchpad.net/sahara/+milestone/juno-rc112:03
SergeyLukjanov#link https://launchpad.net/sahara/+milestone/juno-rc112:03
SergeyLukjanovoops12:03
ttxhttps://blueprints.launchpad.net/sahara/+spec/edp-swift-trust-authentication12:03
ttxIs that all contained in https://review.openstack.org/#/q/topic:bp/edp-swift-trust-authentication,n,z ?12:03
SergeyLukjanovttx, I think all CRs are on review for this blueprint12:03
SergeyLukjanovttx, I think so12:03
ttxand how is that going so far ?12:04
SergeyLukjanovttx, it's already working while manually testing12:04
SergeyLukjanovttx, and all patches have at least one +2 I think12:04
ttxso just needs to adjust tests ?12:04
SergeyLukjanovttx, yup12:05
ttx#info all in review @ https://review.openstack.org/#/q/topic:bp/edp-swift-trust-authentication,n,z -- needs some tests tweaks but in good progress12:05
ttxhttps://blueprints.launchpad.net/sahara/+spec/cluster-persist-sahara-configuration12:05
SergeyLukjanovtwo other blueprints are very small and easy and both are on review12:05
SergeyLukjanovthe last one is re docs12:05
ttxis there more to it than https://review.openstack.org/#/q/topic:bp/cluster-persist-sahara-configuration,n,z ?12:06
SergeyLukjanovnope12:06
ttx#info https://review.openstack.org/#/q/topic:bp/cluster-persist-sahara-configuration,n,z on track12:06
ttxhttps://blueprints.launchpad.net/sahara/+spec/move-rest-samples-to-docs12:06
ttx#info doc only12:06
SergeyLukjanovwe just need to persist some internal versions for validation, cluster-persist-sahara-configuration is about it12:06
ttxSergeyLukjanov: is that all your FFEs ?12:06
SergeyLukjanovyup12:06
ttxOK, so I think they should all land before next Tuesday12:07
SergeyLukjanovack, I think there will be no issues with it12:07
ttxideally the tust delegation part before end of week12:07
ttxbecause it's a bit more disruptive12:07
SergeyLukjanovdo we need some additional actions to obtain FFE or I could just mail to the ML with the list of granted FFEs?12:08
ttxno, you can email the list12:08
ttxso next question would be about the Design Summit -- would Sahara like to have a meetup-like thing on the Friday ?12:08
SergeyLukjanovttx, ack re FFEs12:09
ttxDo you think half-a-day would suffice ? Or would you rather have the full day ? Benefit to half-day is ability to participate to some others12:09
SergeyLukjanovttx, in addition to the slots on other day, or only friday slots/12:09
ttxin addition to slots on Wed/Thu12:09
SergeyLukjanovttx, half of day is enough for sahara12:09
ttxok, that way you can participate to the Infra/QA room12:10
ttx:)12:10
ttxSergeyLukjanov: Anything you want to add to meeting agenda for today?12:10
SergeyLukjanovjust to ack - sahara will have some slots on wed/thu + we could have half day meetup like on friday?12:11
ttxyes. Current plan would be to have cross-project stuff on Tuesday, traditional slots scheduled on Wed/Thu and meetups on Friday12:11
SergeyLukjanovttx, ok, thx12:11
ttxthere just will be less "traditional" slots available overall12:12
ttxsince we have two days for all rather than 312:12
SergeyLukjanovttx, so, I think it'll be cool to have something meetup-like for sahara at friday in addition to the traditional stuff12:12
SergeyLukjanovttx, yeah, I understand12:12
SergeyLukjanovand a few new projects12:12
ttxyes, and limited space !12:12
ttxmy puzzle for the week, see if it can all fit12:13
SergeyLukjanovheh, I'm sure you'll make the best schedule as always :)12:13
ttxSergeyLukjanov: so basically when brainstorming sessions you need to see which can have a clear slot and schedule presence, and which could be solved in the Friday informal discussion12:13
SergeyLukjanovttx, got it12:14
ttxusually the ones you want external feedback on are better as scheduled slots12:14
SergeyLukjanovyeah, to have them in publicly available schedule12:14
SergeyLukjanovand to have some fixed timing12:14
ttxproject internal policies otoh are a good fit for Friday12:14
SergeyLukjanovyup, I think we have several good topics for friday12:14
ttxalso release objectives setting isa good topic for the Friday12:15
ttxanyway, talk to you later!12:15
SergeyLukjanovthank you!12:15
ttxdhellmann: ready when you are12:15
SergeyLukjanovttx, oh, I have one more q.12:16
ttxSergeyLukjanov: sure, shhot12:16
ttxshoot*12:16
SergeyLukjanovttx, could we think oslo and migrate to oslo.XXX libs before the rc1?12:16
dhellmannttx: good afternoon12:17
ttxSergeyLukjanov: depends how disruptive the change is... it's generally a good thing to adopt a library before release... but some of those adoptions may refactor a bit too much code12:17
ttxso it's a case-by-case thing12:17
SergeyLukjanovttx, I think that's ok if it's mostly the import chaning CRs12:18
ttxdhellmann: opinion on that ^ ?12:18
dhellmannI would be conservative about that for now. Plan for K-1 adoptions of anything you aren't already using, unless you have a serious issue that means you need a fix in a lib.12:18
dhellmannand we do allow backporting fixes, too12:19
dhellmannto the incubator, that is12:19
ttxSergeyLukjanov: does that answer your question?12:19
ttx"only if you really need to" ?12:19
SergeyLukjanovack, for sahara we'll check do we really need to switch or sync oslo12:19
SergeyLukjanovttx, yup12:20
SergeyLukjanovttx, dhellmann, thx12:20
ttx#topic Oslo12:20
ttx#link https://launchpad.net/oslo-incubator/+milestone/juno-rc112:20
dhellmannSergeyLukjanov: some of the libs might be just as easy to adopt as a sync, if you have to do that anyway, so let's talk when you figure out how far out of date you are12:20
SergeyLukjanovdhellmann, ack12:21
ttxdhellmann: did we agree those graduate-* BPs should rather apear on the library project rather than on the -incubator?12:21
ttxIf yes I can move them12:21
ttxor at least try12:21
dhellmannyes, that makes sense12:21
dhellmannI can move them after breakfast, too12:21
ttxI'm on it12:23
ttxThat leaves us with... https://launchpad.net/oslo/+milestone/next-juno12:23
ttxSome of those should probably be kilo at this point, right?12:24
dhellmannttx: I set up the pylockfile project yesterday, too, so it looks like all of these blueprints can move out of the incubator project to their library project12:24
ttxdhellmann: ok, will do it once we are done12:24
dhellmannI'll talk to josh about the taskflow thing. The amqp 1 driver is in oslo.messaging now but there's work left to be done. I suppose we should split that one.12:25
ttxdhellmann: yeah12:25
ttxI should create kilo series and next-kilo there12:26
dhellmannthe mysql driver one is blocked on a review in sqlalchemy-migrate, let me find that link12:26
ttxso that stuff can be moved out12:26
dhellmannhttps://review.openstack.org/#/c/110611/12:26
dhellmannI'll put the semver work for pbr in kilo at this point12:27
dhellmannI suppose that means moving the spec in oslo-specs, too12:27
ttxdhellmann: I'll create the kilo series so that you can do the cleanup12:27
dhellmannok12:28
ttxany question on the juno release side ?12:28
ttxI think you have a good handle on all the lib releases now12:28
ttxdid you clarify when we could cut proposed/juno? there were some fixes pending iirc12:29
dhellmannyeah, we have a list of things we'd like to merge, and I haven't checked them yet this morning12:29
dhellmannshould be soon12:29
ttxdhellmann: ok, maybe track them using the -rc1 targeting12:30
ttxthat will let you have a clean list of targets you have to complete before rc112:30
dhellmannyeah, I'll make sure there are bugs for those12:30
ttxand remove what's not a "need to have" fro the list12:30
ttxdhellmann: ok, last question, about the design summit12:30
ttxI hadn't planned an Oslo meetup on the Friday, since I think you should be covered with the cross-project stuff and the scheduled sessions... but did you want one ?12:31
ttxit's tricky because you may want to visit the other rooms12:32
*** eglynn has quit IRC12:32
dhellmannyeah, we might use the pods that day12:32
dhellmannI think we'll have some things to decide that may take longer than the session slots12:32
ttxok, so a smaller space could be enough12:33
dhellmannyeah, we probably only need room for a few of the cores to sit down together for those discussions12:33
ttxdhellmann: ok, that's good feedback. I originally planned to recover pod space to make an additional meetup room, but it might make sense to keep some around and pack more than one project in12:33
dhellmannoh, yeah, I assumed they would be available that day12:34
ttxdhellmann: ok, anything for the meeting today ?12:34
dhellmannwe should tell folks that we're trying to have final library releases on 18 sept to give time for testing before the rest of the release candidates12:35
dhellmannI only really expect a couple of updates at this point12:35
ttx#info we're trying to have final library releases on 18 sept to give time for testing before the rest of the release candidates12:36
dhellmannotherwise, that's it12:36
ttxdhellmann: ok, maybe just re-mention it when I link to the log12:36
dhellmannok12:36
ttxdhellmann: ok, thanks and talk to you later!12:36
dhellmannhave a good afternoon!12:36
*** mestery_ is now known as mestery12:37
*** zz_johnthetubagu is now known as johnthetubaguy13:08
*** mestery has quit IRC13:17
*** mestery has joined #openstack-relmgr-office13:17
dhellmannttx: I think I have all of those bugs/bps updated13:21
* ttx quicklooks13:23
ttxhttps://launchpad.net/oslo/+milestone/next-juno13:23
ttxlooks good13:25
*** mestery has quit IRC13:34
*** mestery has joined #openstack-relmgr-office13:34
*** markmcclain has joined #openstack-relmgr-office13:38
mesteryttx: I have our Neutron meeting from 1400-1500UTC today, can we move our 1:1 to immediately after that?13:39
mesteryttx: I can ping you in-channel if the neutron meeting ends early.13:39
ttxmestery: I'll be on a call then13:40
ttxmestery: we can do it now if that works better for you13:40
mesteryttx: OK, then lets just do it at our normal time and I'll multitask :)13:40
mesteryttx: I am about to get on a call with markmcclain now :)13:40
ttxhheh13:40
mesteryttx: I'll multitask, no issues, thanks!13:41
ttxmestery: my call may end early too. So maybe around 15:1513:42
mesteryttx: Sure! Anytime after 1500 works for me, so ping me when you can. I've cleaned up RC1 LP now, it should be a quick sync.13:43
ttxjgriffith: around?14:07
ttxdolphm: ready when you are14:13
dolphmttx: o/14:15
ttx#topic Keystone14:16
ttxhttps://launchpad.net/keystone/+milestone/juno-rc114:16
ttxAll FFEs done I see14:16
dolphm\o/14:16
ttxyou win!14:16
ttx(at the same time it's pretty sane that keystone is feature-complete first)14:16
dolphmha, i'm not sure that's a good thing for the overall project14:16
ttxno other FFE request pending?14:17
dolphmwe have two wishlist bugs in there, but that's all14:17
dolphmwe're going to discuss in today's meeting if we want to pursue them in juno, or delay14:17
ttxok14:17
ttxso at this point it's pretty simple... compile a list of release-critical bugs, get them assigned and fixed.. and we can tag and open Kilo14:18
ttxhttps://launchpad.net/keystone/+milestone/juno-rc1 will be our target list. If you want to have "nice-to-haves" in the list, better use some tag14:19
dolphmwe're still seeing our bug count creep up with new bugs being opened though, so it's probably going to next week before we start counting in the right direction14:19
ttxlike "juno-rc-potential" or whatever14:19
dolphmalright, we have a lot of those :)14:19
ttxsure, the list should evolve over time anyway14:19
ttxyou can also just get the nice-to-have bugfixes in without necessarily make a list of them14:19
ttxok, questions on RC1?14:20
dolphmwhat's the target date for RC's?14:20
dolphmfinal RCs / release, i mean14:20
ttx"when the buglist is empty."14:21
ttxideally before the end of the month obviously14:21
ttxso we'll aggressively refine the list as we go14:21
dolphmack14:21
ttxI'd say two weeks from now is a good time14:21
ttxFor the design summit, as you know we are considering meetup-like space for the friday. Do you think you'll need half a day or would prefer to have a full day ?14:21
dolphmwould a half day be only afternoon?14:22
ttxyes, could be14:22
dolphmi'd be fine with a half day - i imagine we'll be doing more reviews than anything else14:23
ttxok14:23
dolphmi'm not strongly opinionated either way though14:23
dolphmsounds like a useful schedule change either way14:23
ttxI need to see how much spaces we need14:23
ttxso I can work on layout14:23
dolphmcool14:23
ttxso more people asking for half-days means better spaces :)14:24
ttxobviously big projects like Nova and Neutron wil use the full day anyway14:24
*** david-lyle has joined #openstack-relmgr-office14:25
ttxdavid-lyle: o.14:30
david-lylettx: o/14:31
ttx#topic Horizon14:31
ttxhttps://launchpad.net/horizon/+milestone/juno-rc114:31
ttxdavid-lyle: is that a complete list of the FFEs under consideration?14:32
* ttx crosschecks with ML14:32
david-lyleone was proposed on mailing list14:32
david-lylegoing to ask in an hour for another sponser14:32
ttx"Support of Cinder QOS Specs in Horizon" ?14:32
david-lyle1 owner, 1 sponsor so far14:32
david-lyleyes14:32
ttxlet's see if we have room for it14:33
ttxlet's go over those in your list14:33
ttxhttps://blueprints.launchpad.net/horizon/+spec/neutron-subnet-mode-support14:33
david-lylesure14:33
ttxhow is that one going?14:33
ttxall patches I can find seem merged14:33
david-lyleI need a status update, in an hour as to where support in the client is at14:34
ttxok, might just actually be finished?14:34
david-lyleand determine if we need a client release or not14:34
ttxhttps://blueprints.launchpad.net/horizon/+spec/tagging14:34
david-lylethere are 3 related bps14:35
david-lylethat is one of them14:35
david-lylearound the new meta-data catalog feature in glance14:35
ttx+  nova-metadata-flavors + nova-metadata-aggregates ?14:35
david-lyleyes14:35
david-lylethese are in good shape and have been previously reviewed14:36
ttxhow are they collectively coming up ? They sound a bit far away still14:36
ttxHow much time do you see them collectively take?14:36
david-lylewe were just waiting on the client to release and a requirements bump14:36
david-lylethat happened yesterday14:36
david-lyleI hope to start merging them later today14:36
ttx#info this one is related to nova-metadata-flavors and nova-metadata-aggregates14:37
david-lylethis one has been on our radar for a while and new we were going to be time constrained due to the larger process14:37
ttxdavid-lyle: ok, so ideally they would be all in by the end of the week?14:37
david-lyleI feel confident about them landing by sometime Fri14:37
ttx(all related 3)14:37
ttxok14:37
david-lyleyes14:37
ttxThat means you still have "room" for another one if you have core support for it14:38
david-lylethe QOS proposal contains 3 patches that haven't landed14:38
ttxwhat is their current state?14:38
david-lyleyeah, I need more core support14:38
david-lylethey have had a few reviews, but not the same level of scrutiny as the meta-data patches14:39
ttxhow about we add it to the RC1 list, as "Deferred", so that we keep track of it ? When you finally decide, you can either put status back to "Needs code review", or remove the milestone target14:39
david-lyleok14:39
ttxok, that looks good.14:40
ttxwe'll make more drastic cuts next week if any are still open14:40
david-lylesure14:40
ttxdavid-lyle: other questions on RC1?14:40
david-lyleestimate for a target date?14:41
ttxas soon as your targeted bug list is empty14:41
ttxideally in two weeks, in all cases before the end of the month14:41
david-lyleok, just wanted the window14:41
david-lylewe have a lot of it would be nice bugs, but less that we can't live without14:42
ttxthe window is already opened, but I don't see the first ones happening before mid-Sept14:42
david-lylesounds reasonable14:42
ttxdavid-lyle: about design summit -- we may be able to set up meetup-like space for the Friday. Would Horizon need a full day of informal discussions, or would half a day be enough ?14:43
ttx(so that you can actually participate a bit to others meetups if you want to see what is coming your way)14:43
david-lylethat would be in addition to how many more formalized slots?14:44
ttxthat would be in addition to "less" scheduled slots.14:44
ttxsince we would have two days instead of 3 for those14:44
* ttx checks numbers14:44
david-lyleI imagine a half-day would by enough, especially if we have the pods or other informal meeting areas14:45
ttxin ATL you had 7 sessions, so in Paris you would have 4-5 scheduled sessions and at least half a day of unscheduled time14:45
ttxto address "all other business"14:45
david-lylettx: that sounds good14:46
ttxcool. All depends how much time you need to reach alignment14:46
ttxI think Horizon team is pretty well aligned generally14:46
david-lyletypically14:47
ttxdavid-lyle: ok, that's all I had -- anything you want to discuss at meeting tonight ? Any red flag ?14:47
david-lyleI think we're set now that the glanceclient has released14:47
david-lyleno blockers14:47
david-lylethanks!14:48
ttxdavid-lyle: cool; thx14:51
ttxjgriffith: still not around?14:51
*** markmcclain has quit IRC15:05
mesteryttx: Ready and waiting, ping when your call is complete.15:05
ttxmestery: ack15:07
mesteryttx: \o/15:08
ttxmestery: probably in 10min15:09
mesteryttx: OK, ping me here, I may step out for a bit while waiting. We'll connect soon though :)15:09
*** david-lyle has quit IRC15:19
jgriffithttx: still here15:28
ttxmestery: I'll ping you when I have a hole in my schedule15:28
ttxjgriffith: ok, let me cover swift first15:28
mesteryttx: Ack15:28
ttxnotmyname: around?15:28
notmynamettx: hi!15:29
ttx#topic Swift15:29
ttxnotmyname: how is your next release coming up?15:29
notmynamettx: for project scheduling, we're still on for oct 6 for the RC, with the final on oct 16 for the integrated release15:30
ttxhttps://launchpad.net/swift/+milestone/next-juno15:30
notmyname#link https://wiki.openstack.org/wiki/Swift/PriorityReviews15:30
notmynamethat has a section for current open patches that I'm looking at to land for juno15:30
ttxI'm a bit worried on the timing15:31
notmynameoh yeah?15:31
ttxmaybe have a small safety buffer and plan RC earlier?15:31
notmynamebecause of the length of the RC or because of getting stuff in for the RC?15:32
ttxgetting stuff in on the RC15:32
ttxI guess we could shorten the RC baking period15:32
ttxi.e. if last patch lands on Oct 8 it's not really a showstopper15:33
notmynamewe've got four weeks until the RC. I'm not too worried abotu getting those listed patches in master in that timeframe. they've all been in progress for a while15:33
ttxnotmyname: ok, if it's not too busy, Iguess it works15:33
notmynameand, like you, I'm also ok with targeting the 6th and slipping a couple of days if necessary15:33
ttxI just want to avoid an unpleasant plan B where we'd ship the previous release in Juno final :)15:34
notmynameof course. I find that highly unlikely :-)15:34
ttxok!15:34
notmynameI'd prefer to cut a release sooner with some of those missing before doing that :-)15:34
ttxanything else you wanted to mention?15:35
notmynameany other thoughts on doing any gap analysis follow-up before paris?15:35
ttxnotmyname: maybe we could try to squeeze it in one of the last TC meetings before reelection15:36
notmynamealso, I'm not too happy that the defcore group asked for designated sections feedback, and I gave it, and they didn't update their proposed havana sections15:36
ttxnotmyname: you probably didn't give the right feedback!15:36
notmynameheh. I said their list was good!15:36
notmynamettx: ok, no real worries on the TC front. if there's time, I'd love to get a feel for things before paris, just to make sure the in-person things are time-efficient15:37
ttxthere are new meetings this week, if you want to get that remark on the record15:37
ttxnotmyname: I understand that15:37
ttxnotmyname: about design summit and the Friday meetup-like setup; would you rather have a full day or would a half-day be enough ?15:37
ttxIt's a bit of a two-edged sword15:38
notmynamethat meetup-like setup would be self-scheduled by who's there?15:38
ttxyes15:38
*** dhellmann is now known as dhellmann_15:38
notmynameie kinda like a mid-cycle meetup15:38
ttxyes15:38
notmynameis that the only time we'd have to meet as swift contributors?15:39
notmynameformally15:39
ttxthere would be pods, but I doubt we ca, make space for one pod per project15:39
ttxso the pods would be reusable15:39
notmynameok15:39
ttxi.e. you would claim a table as your pod by putting your sign on it15:40
ttxnot sure that will scale perfectly15:40
ttxin general, full day probably means less scheduled time, more unscheduled time.15:40
notmynameand the other scheduled sessions on wed and thurs are for cross-project stuff?15:40
ttxI still have to build a layout15:40
ttxno. Tuesday for cross project, wed.thu our traditional scheduled sessions (just less of them) and Friday unscheduled time15:41
ttx(will appear on schedule as "swift contributors meetup"15:41
notmynameah ok15:41
notmynameso does each program get some scheduled time on wed.thurs?15:41
ttxyes15:41
notmynameah ok15:41
ttxjust expect ~30% less, maybe more if you pick the full-day option15:42
notmynameobviously the less time at the summit makes mid-cycle meetups more important15:42
ttxagre15:42
ttxe15:42
notmynamebut it seems that if there are already some scheduled sessions, plus the ad-hoc pods, a half-day on friday would probably be a good place to start15:43
ttxyou don't have to decide now, I just want to build a proposal based on this informal poll15:43
ttx(proposal = room layout)15:43
ttxok, anything you want to discuss at meeting later today?15:44
notmynamemy cross-project questions are around defcore and gap analysis and paris scheduling. so no :-)15:44
ttxok, thanks!15:44
ttxzaneb: around?15:44
zanebhowdy15:44
ttx#topic Heat15:44
ttx#link https://launchpad.net/heat/+milestone/juno-rc115:45
ttxzaneb: hi! I'd like to have a quick look at the Heat FFEs15:45
zanebyes, good idea15:45
zanebwe seem to have rather a lot :/15:45
ttxzaneb: is the list on the rc1 page complete ?15:45
* ttx crosschecks with ML15:45
zanebI sure hope so :D15:45
zanebthere were none requested on the ML that I saw15:46
ttxok, so yes, 7 is a lot15:46
ttxespecially as none of those is finalized yet, so they were probably not "technical" FFEs that just needed a few more days to fight the gate15:46
ttxlet's visit them15:47
ttxhttps://blueprints.launchpad.net/heat/+spec/deployment-multiple-servers15:47
ttxall patches merged @ https://review.openstack.org/#/q/topic:bp/deployment-multiple-servers,n,z15:47
ttxanything more coming?15:47
zanebnot that I know of15:47
zanebI'd have to check with stevebaker why he hasn't marked it complete already15:48
zanebbut this one I'm pretty comfortable with as a FFE15:48
*** david-lyle has joined #openstack-relmgr-office15:48
ttxok15:49
ttxhttps://blueprints.launchpad.net/heat/+spec/cancel-update-stack15:49
ttxthis one seems to struggle a lot15:49
zanebyeah, this one is questionable15:49
zanebthe good news is that it's a new feature and won't break any other features if you don't use it15:50
ttxwhy is it something you really need to have in the release ?15:50
zanebbut I fear it will be buggy if merged15:50
zanebit's a big deal for e.g. TripleO15:50
ttxlooks like a good candidate for not having an FFE15:51
zanebyeah, I agree15:51
ttxwell, they can start using it early in kilo15:51
ttxthey are not bound by releases15:51
zanebyep, they are trunck chasing anyway15:51
zanebtrunk15:51
ttxso if tripleO is the main consumer, that can wait kilo alright15:51
ttxshall I target it to kilo-1 and shall you -2 those patches temporarily ?15:51
ttxthat will certainly increase the chances of the others ;)15:52
zanebyep, let's retarget it15:52
ttxok done15:53
ttxhttps://blueprints.launchpad.net/heat/+spec/action-aware-sw-config15:53
ttxhttps://review.openstack.org/#/q/topic:bp/action-aware-sw-config,n,z15:53
ttxalso a long patchseries -- any reason why we want it in release rather than after?15:53
zanebI'm not aware of a particular driver15:54
ttxI'm ok with it if you think it can fully merge by the end of the week15:54
zanebother than that this was supposed to be a major feature for Juno15:55
zanebI think that may be possible15:55
ttxyeah, which is why it needs some decent testing period15:55
ttxok, we'll revisit next week if it's not in yet15:55
zanebit mostly missed because Thomas was on vacation near the end of the cycle, and so not able to respond to some fairly minor comments15:55
ttxhttps://blueprints.launchpad.net/heat/+spec/troubleshooting-low-level-control15:55
zanebIIRC it looks pretty solid15:55
ttxhmm, not sure which review it hinges on15:56
ttxhttps://review.openstack.org/#/q/topic:bp/troubleshooting-low-level-control,n,z has 3 abandoned links15:56
zanebhttps://review.openstack.org/#/c/109284/ and https://review.openstack.org/#/c/109042/15:57
ttx,pt the others on https://review.openstack.org/#/q/topic:bug/1224828,n,z ?15:57
ttxnot*15:57
zanebthe others are the client support15:57
ttxah right15:57
zanebwhich are obviously necessary, but not tied to this release cycle15:58
ttxyes, looks pretty solid, let's give it a week15:58
zanebok15:58
ttximproving debuggability definitely helps15:58
zanebI'd say it's fairly solid but not critical for Juno15:58
ttxhttps://blueprints.launchpad.net/heat/+spec/functional-tests15:58
ttxthat's probably not affected by FFE, as it's only testing?15:58
zanebthis could almost be moved to ongoing15:59
ttxhmm, good idea15:59
ttxok moved15:59
ttxhttps://blueprints.launchpad.net/heat/+spec/implement-ec2eip-updatable15:59
ttxOnly https://review.openstack.org/#/c/118562/ left?16:00
zaneblooks like it, and it already got approved once16:01
ttxok, let's keep it then16:01
ttxhttps://blueprints.launchpad.net/heat/+spec/handle-update-for-security-groups16:01
ttx2 reviews left @ https://review.openstack.org/#/q/topic:bp/handle-update-for-security-groups,n,z16:02
ttxlooks pretty close too16:02
ttxlet's keep it for another week?16:02
zanebyep16:02
zanebagree16:02
ttxThose two "low" priority ones, would be better if they merged before the end of the week, rather than before next Tuesday16:02
ttxjust so that we get them off to testing16:03
zanebyeah, hopefully we can get them through the gate quickly16:03
zanebI will try to review them myself today16:03
ttxzaneb: I think Heat could use a full day of meetup-like space on the Design Summit Friday. Is that your opinion too ?16:03
zanebyeah, we would definitely use it if we can get it :)16:04
zanebplenty of things to talk about16:04
ttxyep16:04
ttxok, anything for the meeting later?16:04
zanebdon't think so16:04
ttxok, talk to you later then16:04
zanebthanks o/16:05
ttxjgriffith: still around?16:05
jgriffithttx: yup16:05
ttx#topic Cinder16:05
ttxhttps://launchpad.net/cinder/+milestone/juno-rc116:05
ttxSo I think I saw quite a few other requests on the list16:05
ttxthose are the ones we already granted on technicalities iirc16:05
jgriffithttx: you did, frankly my response has been pack sand16:05
ttxhow are those SMB ones going ?16:06
jgriffithttx: other core members however are a bit less jaded16:06
jgriffithI think they're going to finally go today16:06
jgriffithIf we can just get them through Gate16:06
jgriffithit's been a bit of a struggle16:06
ttxok, let's keep them then16:06
jgriffithyeah, I def feel fine with those16:06
* ttx has a quick look for the cinder FFE requests on the ML16:06
jgriffithttx: https://etherpad.openstack.org/p/juno-cinder-approved-ffes16:07
jgriffithttx: a "hopefully" consolidated list16:07
jgriffithAll vendor/driver *features*16:07
jgriffithI've been pretty harsh, maybe I shouldn't be16:07
ttxhow ready are they?16:08
jgriffithso to be fair their pretty close16:08
jgriffithand rather simple16:08
ttxI'm fine with 2/3 more if they can land this week16:08
jgriffiththe only one that's new is Duncan't backup state reset16:08
jgriffithttx: My cutoff is this week for features regardless16:08
jgriffithI seem to be much more literal about Freeze than anybody else16:09
ttxmaybe pick 2/3 that are self-contained16:09
ttxbackup state reset doesn't sound self-contained16:09
jgriffithyeah, that's the only "new" one16:10
jgriffithI suppose since he started that back in Aug I can have some sympathy, but I don't think it's that "important"16:10
ttxI'm fine with not accepting any, too. After all we had feature freeze and they missed it by more than a finger16:10
jgriffithI'll talk with Duncan and see why he ranks t16:10
jgriffithyeah, it's one thing when it's a day or two16:11
jgriffithbut we're defeating the point now :(16:11
jgriffithIMO16:11
jgriffithanyway....16:11
ttxnone of those *needs* to be in16:11
jgriffithNope, not a one16:11
jgriffithI'm fine with giving inflight items til Friday16:11
jgriffithto Merge16:12
jgriffithafter that I'm done16:12
ttxso I'm fine with 0-3, I'd prefer to stick to the self-contained ones, and in all cases Friday is the last day16:12
jgriffithI have features for my driver I'd love to put in, but ain't happening16:12
jgriffithttx: agreed, I'll have a look at backup state change and decide today16:12
jgriffithUnless there's feedback that alot of people are having "stuck" jobs I don't see it as justified16:13
ttxnext question - about the design summit Friday "contributors meetup" space. Would you rather have half a day of Cinder meetup (in addition to regular scheduled sessions), or a full day ?16:13
ttxjgriffith: some people have been complaining that Cinder is always on the last day, so those may prefer the half-day option16:13
jgriffithby Friday, probably a half day :)16:13
jgriffithyeah, I get a lot of feedback about the Friday thing for some reason16:14
ttxok, I'll try to place you in the morning, and give a decent number of "scheduled" slots16:14
jgriffithttx: let's do the 1/2 day option16:14
jgriffithok, great16:14
ttxanything to add to meeting agenda for tonight?16:14
jgriffithnope, just plugging along16:14
ttxjgriffith: awesome! thanks for your time.16:15
ttxSlickNik: around?16:15
SlickNiko/16:15
ttx#topic Trove16:15
ttxhttps://launchpad.net/trove/+milestone/juno-rc116:15
jgriffithttx: thank you!16:15
ttxis the oslo.messaging migration your last open FFE ?16:15
SlickNikYes, that's the only one we've got left.16:16
ttxhow is it going ?16:16
SlickNikChecked in with Sergey, and amrith and they're on track to get it done by end of this week.16:16
ttxSlickNik: ok, sounds good16:17
SlickNikI'll be checking in on the work again tomorrow to make sure things are going as planned (and to see where I can help as needed).16:18
ttxok. Any question on final release process ?16:19
SlickNikNope,16:21
SlickNikMentioned this to you last week, but just wanted to remind you: we'd like to use a specs repo going forward in Kilo, so I'm going to be doing the infra work to get that set up this week.16:21
ttxok16:22
ttxSlickNik: as far as design summit goes, I think Trove could opt for a half-day of contributors meetup16:22
ttxsince you aren't that many, convergence is not that hard to obtain?16:23
SlickNikttx: It depends on the issues, but a half day should be okay I think. How many sessions would that give us to work with?16:23
ttxI still have to check the numbers16:24
SlickNik(Some issues are more contentious than others)16:24
ttxthat would result in more time overall16:24
ttxyou would have anumber of scheduled slots, then a half-day for the more informal discussion16:24
SlickNikAh, gotcha. Yes, I think that would be fine.16:25
ttxSomething like 4 scheduled slots and a half-day of meetup16:25
ttxok, thanks16:25
ttxanything you want to discuss at cross-project meeting today?16:25
SlickNikNothing in particular — that's all I had.16:26
ttxmestery: would you be available around 19:30 UTC?16:26
* ttx could use a break now16:26
ttxSlickNik: thx!16:26
mesteryttx: Yes!16:26
mesteryttx: I'll be here, thanks!16:26
ttxmestery: ok, see you then :)16:26
SlickNikttx: thank you! Talk to you later. :)16:27
*** SlickNik has left #openstack-relmgr-office16:27
*** markmcclain has joined #openstack-relmgr-office16:30
*** markmcclain has quit IRC16:32
*** markmcclain has joined #openstack-relmgr-office16:33
*** david-lyle has quit IRC16:35
*** david-lyle has joined #openstack-relmgr-office16:36
*** arnaud__ has joined #openstack-relmgr-office16:49
*** mestery has quit IRC16:59
*** mestery has joined #openstack-relmgr-office17:00
*** johnthetubaguy is now known as zz_johnthetubagu17:05
*** markwash__ has joined #openstack-relmgr-office17:07
*** dhellmann_ is now known as dhellmann17:13
*** david-lyle has quit IRC17:50
*** mestery has quit IRC18:32
*** mestery has joined #openstack-relmgr-office18:32
*** markwash__ has quit IRC18:40
*** markwash__ has joined #openstack-relmgr-office18:43
*** markwash__ has quit IRC18:44
*** markwash__ has joined #openstack-relmgr-office18:47
ttxmestery: around?19:28
mesteryttx: o/19:28
ttx#topic Neutron19:28
ttxhttps://launchpad.net/neutron/+milestone/juno-rc119:28
ttx7 left open19:29
mesteryYes19:29
mesteryStatus on each one quickly perhaps?19:29
ttxyes please19:29
mesteryL3 HA is very close, I have at least two cores focused on it and they expect it to land before Friday.19:29
mesteryipset has two patches left, one of which is a functional test. I expect that one to land by Thursday19:30
mesteryretarbetable functional testing is being iterated tomorrow, the author thinks it can land soon as well. I tend to agree.19:30
mesteryFWaaS and DVR: 3 cores covering it, I believe it should be in the queue tomorrow as well.19:30
mesteryPlugin specific migrations: Realistically with this one we're going to land one of the patches there and then move it out of Juno and the rest can land in Kilo.19:31
mesteryL3 metering: This one should be in the queue tomorrow.19:31
mesteryResource autodeletion: It's in the queue now (may have merged, will check once status is done)19:31
mesteryAnd that's it.19:31
mesteryThe other 4 merged19:31
mesteryall low priority19:31
ttxhmm, ok. I think that's doable and will have limited impact19:32
mesteryCool!19:32
mesteryI've worked hard with the neutron cores to make it have as minimal distruption as possible19:32
ttxobviously next week we'd reconsider, in case they take longer than expected19:32
ttxbecause everybody needs to switch to bugfixes asap19:32
mesteryExactly19:33
mesteryWe're heavy on those as well19:33
ttxmestery: any topic for the meeting today?19:33
mesteryThe team has been working on bugs in paralle19:33
mesteryparallel19:33
mesteryNothing at this time no19:33
ttxok, I think you are covered then19:33
mesteryThanks ttx!19:33
ttxmarkwash__: around?19:33
markwash__ttx: ish!19:33
ttxmarkwash__: time for a quick Glance status?19:34
markwash__yup19:34
ttx#topic Glance19:34
ttxhttps://launchpad.net/glance/+milestone/juno-rc119:34
ttxSo that's two already on the map, from j319:34
ttx+ a boatload proposed on the ML19:34
markwash__yeah, but I think they landed19:34
* ttx cheks19:34
markwash__it looks like we're missing the two flavio did in that list (which also have landed)19:35
markwash__I think we're done with FFE once I update the list19:35
ttxasync-glance-workers seem to still be open19:35
ttxhttps://review.openstack.org/#/c/85211/ ?19:36
markwash__yeah I thought that one isn't really intended for juno at this point, however19:36
markwash__I'll clarify with the bp owner in a little bit19:36
ttxso there are two that are donce and should be added to list?19:37
ttxdone*19:37
markwash__yes, searching19:37
ttx[3] https://blueprints.launchpad.net/glance/+spec/create-store-package19:37
ttx[4] https://blueprints.launchpad.net/glance/+spec/restartable-image-download19:37
ttx?19:37
markwash__yes19:38
markwash__check juno-rc1 again19:38
markwash__at this point we're just down to bug fixes and cleanup, but none are specifically targeted yet19:39
ttxok19:39
markwash__we have a bug day on thursday19:39
markwash__that will focus on cleanup and triaging critical bugs19:39
ttxwhat about the FFEs requested for refactoring-glance-logging and use-common-service-framework ?19:39
ttxI think it's too late for refactoring personally19:39
markwash__use-common-service-framework was deferred19:39
markwash__ttx: the glance logging change seemed kind of minor to me19:40
ttxlooking into it19:40
markwash__it is basically just adjusting levels and using the correct internationalization routines in more places19:40
*** david-lyle has joined #openstack-relmgr-office19:40
markwash__ttx: but I"m not sure if that messes with string freeze ?19:40
ttxok, let's add it then19:40
markwash__+119:40
ttxdone19:40
ttxi'll let you reply to him19:41
ttxso async-processing, should we just move it out ?19:41
ttxyou said "that one isn't really intended for juno at this point"19:41
markwash__I'd like to pressure folks to split that bp into "what was done in juno" and what remains19:41
markwash__so that we have a clear picture19:42
ttxmarkwash__: ok, let's do that19:42
markwash__I think that means we can mark it as completed for juno-rc1 and open a new spec/bp for klieber19:42
ttx#info async-glance-workers to be split between completed and todo parts19:42
ttxok done19:43
ttxmarkwash__: that is all. talk to you later!19:43
markwash__great, thanks ttx!19:43
ttx#endmeeting19:45
openstackMeeting ended Tue Sep  9 19:45:57 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-09-09-11.46.html19:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-09-09-11.46.txt19:46
openstackLog:            http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-09-09-11.46.log.html19:46
ttxmikal, johnthetubaguy: how about we do our sync at 08:00UTC tomorrow? (mikal: that should be at the end of your today if my TZ math is correct)19:48
*** markwash__ has quit IRC19:53
*** markwash__ has joined #openstack-relmgr-office19:54
mikalttx: sure, I can do that19:59
*** markwash__ has quit IRC19:59
ttxmikal: ok, see you then19:59
ttxor maybe after the release meeting if it's cut short19:59
ttxand I have some energy left19:59
*** dhellman_ has joined #openstack-relmgr-office20:16
*** markwash__ has joined #openstack-relmgr-office20:34
mikalSure20:52
*** mestery has quit IRC20:57
*** mestery has joined #openstack-relmgr-office20:57
*** arnaud__ has quit IRC20:59
ttxmikal: got time now ?21:24
mikalYes21:24
ttx#startmeeting ptl_sync21:24
openstackMeeting started Tue Sep  9 21:24:51 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:24
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:24
ttx#topic Nova21:24
openstackThe meeting name has been set to 'ptl_sync'21:24
ttxhttps://launchpad.net/nova/+milestone/juno-rc121:24
ttxis that list complete with all approvals?21:25
mikalI beleive so21:25
mikalI ahven't checked in the last 24 hours, but it was before21:26
mikalIt should also be mostly accurate for implementation status too21:26
ttxand you set a deadline for those last Friday, so new ones should be ignored anyway21:26
ttxstill on track to close them all by Friday?21:26
mikalYep21:26
mikalIts hard to tell21:26
mikalThe gate is painful21:26
mikalI can see two which need more dev work21:26
mikalAnd the rest need the gate to agree21:26
mikalhttps://etherpad.openstack.org/p/juno-nova-approved-ffes is our summary of review state21:27
mikalSo, looking at that21:27
mikalvirt-driver-name-placement is at risk21:27
ttxmikal: if they are gating now and don't get in by Friday I'm fine with giving them extra time :)21:27
mikalAs is server-group-quotas21:27
mikalAnd SRIOV21:27
mikalttx: yeah, I figured we'd sneak them in21:27
ttxOK, if you see that they are not getting in in time, defer them early rather than late21:27
mikalSounds sensible21:28
ttxi.e. if they are not approved by Thursday... or gating by Friday...21:28
mikalIt is probably a good idea for me to email -dev and remind people to be focussing on these21:28
ttxprobably simpler to just defer them21:28
ttxbecause otherwise they will still be in progress by mid next-week21:28
mikalAgreed21:29
ttxespecially if some of those are patchseries21:29
ttxthose can take a long time21:29
mikalYeah, gating is painful for those21:29
ttxSo, we'll see how it goes at the end of the week21:30
ttxquick discussion on design summit21:30
mikalThere is also one important bug on my radar as I mentioned in email21:30
mikalThe ironic driver as landed does not work21:30
mikalThere is already a fix out for review21:30
ttxoh, ok21:30
mikalhttps://review.openstack.org/#/c/119944/21:30
mikalAhhh, it got approved while I slept21:30
mikalIn the gate now21:30
ttxI think you'll want a full day of meetup on the Friday21:30
mikalSorry, at the summit you mean?21:31
ttxyes21:31
mikalSo, there are four summit days, yes?21:31
ttxon the Tuesday you have cross-project stuff21:31
ttxthat leaves Wed/Thu21:31
mikalHow does that compare with Atlanta, its the same number of slots right?21:32
ttxwhere my original plan was to give you two full days of scheduled slots21:32
ttxyes21:32
mikalAhhh, two days not three?21:32
ttxwell, the third is replaced by the meetup, so same time together21:32
mikalHoldup21:32
mikalI'm confused now21:32
mikalWhat is the meetup?21:32
ttxok, /me rewinds21:32
ttxon the wed/Thu we'll have traditional slots21:33
mikalOk21:33
ttxi.e. 40-min, with a predetermiend theme and present on schedule21:33
ttxon the Friday, all teams will have a half-day or a full-day "contributors meetup"21:33
ttxthat's a big block of time that they can organize how they see fit21:34
ttxusually with an etherpad full of themes to discuss21:34
ttxmidcycle-meetup style21:34
ttxno "slots", no 40-min bell21:34
mikalAhhh, cool21:34
mikalOk21:34
mikalIn that case I've changed my mind21:34
mikalAnd I want all the slots I can get on the two non-meetup days21:34
ttxok21:34
mikalIf we didn't have the meetup I'd want to spread them out over the three days21:35
mikalBut that doesn't sound like an option here21:35
ttxIdeally you would use the Friday to get alignment on a Kilo plan21:35
ttxand solve "team problems"21:35
mikalI think that's a good idea21:36
ttxbut it's really up to you, and can change at last minute21:36
mikalI just somehow missed that it was the plan21:36
ttxlet's say it was just a thought, but I talked with our event partner and it may actually be possible21:36
ttxwe'll need to revamp the space between Thursday and Friday21:36
mikalAhhh yeah21:36
mikalTables and stuff instead of just 200 chairs21:36
mikalFair enough21:37
ttxso that there are a lot of parallel spaces, and tables21:37
ttxwe might have LCDs to be able to show up stuff21:37
ttxrather than prjector/screen combos21:37
mikalAnd whiteboards?21:37
mikalWhiteboards would be good21:37
ttxactually the paperboards double as whiteboards. I asked that we have several of them21:38
ttxso you could in theory build a large whiteboard21:38
mikalLOLK21:38
mikalOk21:38
ttxapparently large whiteboards would be difficult to se up21:38
ttxthey don't really come with wheels21:39
mikalI could bring some wheels?21:39
mikalBut either way, it sounds like we're agreed here and I should let you go home?21:39
ttxyou should let me jump into my bed yes21:39
ttxthanks for your time!21:39
ttx#endmeeting21:39
mikalNP21:39
openstackMeeting ended Tue Sep  9 21:39:57 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-09-09-21.24.html21:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-09-09-21.24.txt21:40
mikalThanks for staying up21:40
openstackLog:            http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-09-09-21.24.log.html21:40
*** dhellman_ has quit IRC21:48
*** flaper87 is now known as flaper87|afk22:03
*** markwash__ has quit IRC22:12
*** markwash__ has joined #openstack-relmgr-office22:39
*** david-lyle has quit IRC23:15
*** david-lyle has joined #openstack-relmgr-office23:34
*** markwash__ has quit IRC23:56

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!