Tuesday, 2013-12-17

*** markwash has joined #openstack-meeting00:01
*** jcooley_ has quit IRC00:02
*** thomasbiege has quit IRC00:02
*** dolphm has quit IRC00:05
*** Duane has joined #openstack-meeting00:05
*** jcooley_ has joined #openstack-meeting00:06
*** hemna is now known as hemnafk00:06
*** jcooley_ has quit IRC00:08
*** nermina has joined #openstack-meeting00:08
*** markwash has quit IRC00:09
*** Duane has quit IRC00:09
*** jcooley_ has joined #openstack-meeting00:10
*** fnaval_ has quit IRC00:10
*** Leo_ has quit IRC00:13
*** dougshelley66 has quit IRC00:14
*** samcdona has joined #openstack-meeting00:14
*** DennyZhang has joined #openstack-meeting00:14
*** eharney has quit IRC00:15
*** DennyZhang has quit IRC00:15
*** DennyZhang has joined #openstack-meeting00:16
*** rnirmal has quit IRC00:19
*** sacharya has joined #openstack-meeting00:20
*** amotoki has joined #openstack-meeting00:21
*** ryanpetrello has joined #openstack-meeting00:22
*** ryanpetrello has quit IRC00:23
*** rfolco has quit IRC00:24
*** Swaminathan has left #openstack-meeting00:24
*** dkranz has joined #openstack-meeting00:24
*** s0mik has quit IRC00:25
*** s0mik has joined #openstack-meeting00:26
*** nermina has quit IRC00:27
*** DennyZhang has quit IRC00:27
*** diogogmt has quit IRC00:29
*** Mandell has quit IRC00:31
*** marun has joined #openstack-meeting00:31
*** nelsnelson is now known as nelsnelson_away00:32
*** yamahata has joined #openstack-meeting00:33
*** Mandell has joined #openstack-meeting00:34
*** nermina has joined #openstack-meeting00:36
*** nelsnelson_away has quit IRC00:36
*** dims has quit IRC00:37
*** dcramer_ has quit IRC00:37
*** esker has quit IRC00:38
*** esker has joined #openstack-meeting00:38
*** dims has joined #openstack-meeting00:39
*** comay has quit IRC00:40
*** markwash has joined #openstack-meeting00:41
*** michchap has quit IRC00:42
*** michchap has joined #openstack-meeting00:42
*** sacharya1 has joined #openstack-meeting00:44
*** SridarK has quit IRC00:44
*** rakhmerov has joined #openstack-meeting00:44
*** pvaneck has quit IRC00:45
*** comay has joined #openstack-meeting00:46
*** elo has joined #openstack-meeting00:47
*** dims has quit IRC00:47
*** sacharya has quit IRC00:47
*** elo has quit IRC00:49
*** novas0x2a|laptop has quit IRC00:50
*** jcooley_ has quit IRC00:50
*** gduan has quit IRC00:51
*** jcooley_ has joined #openstack-meeting00:53
*** garyduan has joined #openstack-meeting00:54
*** nosnos has joined #openstack-meeting00:54
*** sarob has joined #openstack-meeting00:57
*** sacharya has joined #openstack-meeting00:58
*** markpeek has quit IRC00:59
*** kushi_ has quit IRC01:00
*** sacharya1 has quit IRC01:00
*** dims has joined #openstack-meeting01:02
*** nelsnelson has joined #openstack-meeting01:03
*** banix has joined #openstack-meeting01:04
*** mrodden has quit IRC01:04
*** dcramer_ has joined #openstack-meeting01:05
*** nosnos has quit IRC01:06
*** nosnos has joined #openstack-meeting01:06
*** sarob has quit IRC01:07
*** sarob has joined #openstack-meeting01:08
*** sarob has quit IRC01:12
*** kenhui has joined #openstack-meeting01:14
*** stevemar has joined #openstack-meeting01:15
*** sarob has joined #openstack-meeting01:17
*** rakhmerov has quit IRC01:18
*** kenhui has quit IRC01:18
*** nermina has quit IRC01:22
*** banix has quit IRC01:23
*** Jianyong has joined #openstack-meeting01:24
*** IlyaE has quit IRC01:29
*** suo has joined #openstack-meeting01:30
*** bdpayne has quit IRC01:34
*** colinmcnamara has quit IRC01:37
*** lbragstad has quit IRC01:40
*** yaguang has joined #openstack-meeting01:40
*** lbragstad has joined #openstack-meeting01:43
*** nermina has joined #openstack-meeting01:43
*** epim has quit IRC01:47
*** kui has joined #openstack-meeting01:48
*** dougshelley66 has joined #openstack-meeting01:48
*** oubiwann has joined #openstack-meeting01:49
*** s0mik has quit IRC01:50
*** shakayumi has joined #openstack-meeting01:51
*** mrodden has joined #openstack-meeting01:53
*** nermina has quit IRC01:54
*** mrodden1 has joined #openstack-meeting01:55
*** tanisdl has quit IRC01:55
*** sushils has quit IRC01:57
*** mrodden has quit IRC01:57
*** radix_ has quit IRC01:58
*** nati_ueno has quit IRC02:01
*** Hunner has quit IRC02:03
*** dolphm has joined #openstack-meeting02:04
*** jcooley_ has quit IRC02:08
*** karthik_ has quit IRC02:09
*** s0mik has joined #openstack-meeting02:10
*** banix has joined #openstack-meeting02:12
*** s0mik has quit IRC02:14
*** kenhui has joined #openstack-meeting02:14
*** rakhmerov has joined #openstack-meeting02:14
*** dcramer_ has quit IRC02:14
*** markvoelker1 has joined #openstack-meeting02:17
*** kenhui has quit IRC02:18
*** rakhmerov has quit IRC02:22
*** Daisy has joined #openstack-meeting02:24
*** nermina has joined #openstack-meeting02:24
*** markwash has quit IRC02:24
*** banix has quit IRC02:24
*** dcramer_ has joined #openstack-meeting02:27
*** nati_ueno has joined #openstack-meeting02:30
*** nermina has quit IRC02:31
*** Mandell has quit IRC02:32
*** fnaval has joined #openstack-meeting02:38
*** kui has quit IRC02:38
*** reed has quit IRC02:42
*** ayoung has quit IRC02:44
*** epico has joined #openstack-meeting02:44
*** coolsvap has joined #openstack-meeting02:47
*** vkozhukalov has joined #openstack-meeting02:48
*** fnaval has quit IRC02:49
*** dnavale has joined #openstack-meeting02:50
*** banix has joined #openstack-meeting02:50
*** dcramer_ has quit IRC02:51
*** fnaval has joined #openstack-meeting02:52
*** dims has quit IRC02:53
*** dims has joined #openstack-meeting02:53
*** brucer_afk is now known as brucer02:55
*** MirandaZhang has joined #openstack-meeting02:58
*** sgordon has joined #openstack-meeting02:58
*** Sam-I-Am has joined #openstack-meeting02:59
* fifieldt wanders in02:59
* Sam-I-Am too02:59
*** Sukhdev has quit IRC03:00
Loquacitiesheya everyone03:00
Sam-I-Amhowdy03:00
fifieldthi Loquacities03:00
Loquacitiesshall we get started?03:00
Loquacities#startmeeting DocTeamMeeting03:00
openstackMeeting started Tue Dec 17 03:00:58 2013 UTC and is due to finish in 60 minutes.  The chair is Loquacities. Information about MeetBot at http://wiki.debian.org/MeetBot.03:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.03:01
*** openstack changes topic to " (Meeting topic: DocTeamMeeting)"03:01
openstackThe meeting name has been set to 'docteammeeting'03:01
*** ctracey is now known as ctracey|away03:01
Loquacitiesagenda is here:03:01
Loquacities#link https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting03:01
Loquacities#topic Action items from the last meeting03:01
*** openstack changes topic to "Action items from the last meeting (Meeting topic: DocTeamMeeting)"03:01
Loquacitieschandankumar to update https://wiki.openstack.org/wiki/Documentation/HowTo#Reviewing_Documentation with note about WIP03:02
Loquacitieschandankumar isn't up yet, by the looks, so we can probably move right on03:02
*** NickChase has joined #openstack-meeting03:02
fifieldtwelcome NickChase03:02
Loquacities#topic Monthly Google Hangout starting Jan 201403:02
*** openstack changes topic to "Monthly Google Hangout starting Jan 2014 (Meeting topic: DocTeamMeeting)"03:03
Loquacitiesanne has agreed to start running these monthly, now03:03
Loquacitiesstarting in jan03:03
Loquacitiesany comments on that?03:03
Sam-I-Amsounds like a great idea03:03
Loquacitiesyeah, everyone seems very positive about it :)03:04
fifieldtit's continuing in line with our previous one, pretty much, isn;t it?03:04
*** slong has joined #openstack-meeting03:04
fifieldtwhich was pretty cool03:04
Loquacitiesyep, pretty much03:04
fifieldtcool, it's a good idea :)03:04
Loquacitiesalso, the office hours are officially dead now03:04
slongsorry, forgot to switch03:04
*** nermina has joined #openstack-meeting03:04
Loquacities#topic Operations Guide developmental edit03:04
*** openstack changes topic to "Operations Guide developmental edit (Meeting topic: DocTeamMeeting)"03:04
Loquacitiesi'm going to c&p some stuff from anne from the last meeting on this topic ...03:05
*** jeckersb is now known as jeckersb_gone03:05
fifieldtta03:05
Loquacities14:06:07 <annegentle> As most of you probably know, the Ops Guide is being edited by O'Reilly03:05
Loquacities14:06:34 <annegentle> We have our first set of comments, mostly high level, and next week we'll have annotaed PDFs of the first couple of chapters03:05
Loquacities14:06:43 <annegentle> I can't spell annotated apparently03:05
Loquacities14:07:14 <annegentle> then, by mid-January, we'll have edits of the entire book, and at the end of January we're doing a mini sprint in Boston with the original authors03:05
Loquacities14:07:46 <nermina> nice03:05
Loquacities14:07:49 <annegentle> I think Brian, the O'Reilly editor, can meet us those days since they're nearby03:05
Loquacities14:08:48 <annegentle> Some of the tasks: expand the preface to situate the Ops Guide in relation to the other guides, an intro chapter about OpenStack showing a high-level overview and emphasizing how components work together03:05
Loquacities14:10:43 <annegentle> Another interesting comment we're working through is that the book contains tactics but not a lot of strategy03:06
Loquacities14:10:53 <annegentle> My favorite is that it is quite "clean" heh03:06
Loquacities14:11:12 <annegentle> So we'll answer questions like, how does the cloud controller make your job easier? what do you need to be concerned about?03:06
*** thomasem has joined #openstack-meeting03:06
Loquacitiesi think that covers the highlights03:06
nerminahi all03:06
Loquacitiesany comments on that?03:06
Loquacitieshey nermina03:06
*** yamahata__ has quit IRC03:06
slonghi nermina03:06
*** yamahata__ has joined #openstack-meeting03:06
slongLoquacities,03:06
slongjust a question about timing for new info going in. Have a contributor.03:07
sgordonLoquacities, insert misgivings about annotated PDFs here03:07
sgordon;)03:07
Loquacitiessgordon: they're just for the review AIUI, what's the concern?03:07
Loquacitiesslong: i'm fairly certain we can't get any real new content into it at this stage03:07
Loquacitiesbut i'm happy to chase that up with anne03:07
Loquacitiescan you drop me an email?03:08
slongOk, will wait until after the January sprint perhaps.03:08
fifieldtdo we know what kind of content?03:08
sgordonLoquacities, having already been through the process of actioning such a review of one of the guides in the past i feel for whoever ends up doing the work03:08
Loquacitiesslong: i think that would be wise03:08
Loquacitiessgordon: ah, fair enough03:08
Loquacitiesconcern noted, in that case ;)03:08
slongfifieldt, rhel architecture, since it's pretty ubuntu-centric.03:08
fifieldtoh03:08
fifieldtright03:08
slongJust would like to get it in before the next release.03:09
Loquacitiesslong: it's needed, for sure03:09
fifieldtdo we know operators who have many months of experience running a production openstack cloud on rhel?03:09
*** oubiwan__ has joined #openstack-meeting03:09
sgordonfifieldt, is that a joke?03:09
sgordonyes03:09
Loquacitieslol03:09
sgordonthat was what the mailing list thread was about, we were asked to identify someone03:10
slongThe contributor is one such, Graeme Gillies (if I spelled it right).03:10
slongHe's volunteered to take a look.03:10
Loquacitiesnice03:10
fifieldtdoesn't look like a cloud operator to me ... ?03:10
sgordonfifieldt, how do you figure03:10
fifieldtlinkedin ?03:11
sgordonhe operates our internal openstack cloud03:11
fifieldta lab cloud, then03:11
*** oubiwann has quit IRC03:11
sgordonfifieldt, it's not a lab cloud03:11
Loquacitiesit's production03:11
*** NickChase has quit IRC03:11
fifieldtcool, well maybe writing up a description of that for the examples in the tail end of the book would be a good start03:12
Loquacitiesbut it's not like he's the only one, either03:12
*** thomasem has quit IRC03:12
slongJust have to start somewhere.03:12
fifieldtof course03:12
fifieldtjust want to avoid "vendor" labels03:12
Loquacitieslet's chat to anne about late additions03:12
slongDefinitely.03:12
Loquacitiesok, moving on03:12
sgordonfifieldt, given the way the book was set up that is a tad rich ;)03:12
Loquacities#topic Doc core can now set a patch to WIP03:13
*** openstack changes topic to "Doc core can now set a patch to WIP (Meeting topic: DocTeamMeeting)"03:13
fifieldtI'd be interested in knowing more sgordon, but let's do that in pm channel :)03:13
Loquacities14:13:03 <annegentle> This is just a public service reminder as a new part of our review process03:13
Loquacities14:14:03 <annegentle> Anyone up for updating the wiki with the new ability to set a patch as WIP?03:13
Loquacities14:14:19 <annegentle> I think it goes in https://wiki.openstack.org/wiki/Documentation/HowTo#Reviewing_Documentation03:13
sgordoni think the open question here is, when do we want to use this facility03:13
Loquacitiesso it doesn't look as though that's been updated yet03:14
Loquacitiessgordon: i confess, i'm not across this issue03:14
sgordongerrit will automatically abandon a patch that has been minused and not touched for two weeks03:14
sgordonbut we need to determine what makes a patch something we want to push to WIP03:14
*** paragan has joined #openstack-meeting03:14
*** paragan has joined #openstack-meeting03:14
fifieldtI have an example of a -core using WIP:03:14
fifieldthttps://review.openstack.org/#/c/61898/03:14
fifieldtsee this terrible patch and the change to WIP not done by mde03:14
fifieldtme*03:14
Loquacitieshrm, ok03:15
Loquacitiesseems sane03:15
Loquacitiesno other comments on that?03:16
Sam-I-Amwell, sort of...03:16
Loquacitiesgo ahead03:16
slongThere's nothing at all about WIP in the HowTo. Should be added for the normal user as well,or?03:17
Sam-I-Ami noticed that the associated launchpad bug will change to 'in progress' but only after i submit something for review.  would this set some sort of similar flag there?03:17
Loquacitiesyeah, good point slong03:17
Loquacitiesthe bug changes in response to the Partial-Bug flag in the commit message03:18
Loquacitiesslong: it's probably worth mentioning that core is able to do this03:18
slongYes, both,would say.03:18
Loquacitiesyep03:18
slongDidn't know to use WIP until fifieldt clued me in.03:18
Loquacitiesare you volunteering to update that, slong? ;)03:19
fifieldtyeah, would be good to put something in03:19
slongOn largish commits...03:19
fifieldtencouraging people to put stuff "up early"03:19
*** martinlo has joined #openstack-meeting03:19
*** rakhmerov has joined #openstack-meeting03:19
slongSure, but might have to wait a bit.03:20
sgordonyou can submit your own changes as WIP03:20
Loquacitiesslong: thanks03:20
Loquacities#action slong to update the HowTo to include WIP info03:20
Loquacities#topic Doc tools update - openstack-doc-tools repository03:21
*** openstack changes topic to "Doc tools update - openstack-doc-tools repository (Meeting topic: DocTeamMeeting)"03:21
* slong can never tell when sgordon is pulling a funny03:21
Loquacities14:15:54 <annegentle> Andreas has been working steadily at the new repo setup03:22
Loquacities14:16:10 <annegentle> Here's a link to the review queue03:22
Loquacities14:16:12 <annegentle> #link https://review.openstack.org/#/q/status:open+project:openstack/openstack-doc-tools,n,z03:22
Loquacities14:17:11 <annegentle> He's also working through the right way to get consistent gate checks on all the docs repos03:22
Loquacities14:17:43 <annegentle> This move also helps with building translated documents03:22
Loquacitiesthere was no further comment in last week's meeting03:22
Loquacitiesany comment from this side of the globe?03:22
Loquacitiesi'll take that as a no03:22
Loquacities#topic Doc Bug Day Dec 2003:22
*** openstack changes topic to "Doc Bug Day Dec 20 (Meeting topic: DocTeamMeeting)"03:22
Loquacitiesthat's this friday, folks03:23
fifieldtyay :)03:23
fifieldtcan I ask someone in .au to send a reminder when they wake up03:23
fifieldtto start the day03:23
slong4am work for you?03:23
Sam-I-Am00 utc to 00 utc?03:23
Sam-I-Ami should plan to be up 24 hours...03:23
fifieldtlol, nice early start there slong :D03:24
Loquacitiesfifieldt: i can try and make sure i put something in the irc chan in our tz, if you like03:24
fifieldtI'm thinking also the mailing list03:24
fifieldtjust replying to the post I have there03:24
Loquacitiesoh, that's a good idea too03:24
Loquacitiesit might also be a good idea to make some noise the day before, as well03:24
Loquacitiesjust so people don't forget03:24
*** shakayumi has quit IRC03:24
Loquacitiesok, that's all i have on the agenda03:25
Loquacities#topic Open discussion03:25
*** openstack changes topic to "Open discussion (Meeting topic: DocTeamMeeting)"03:25
Sam-I-Amso whats the game plan for these sprints?03:25
*** dolphm has quit IRC03:25
Loquacitiesfor the doc bug day?03:25
Sam-I-Amyeah03:25
Loquacitiesjust do as many bugs as you can :)03:25
Sam-I-Amany priorities? heat? age?03:26
Loquacitiesdocs!03:26
Loquacities;)03:26
fifieldt:D03:26
Sam-I-Amwhat about reviewing?  leave that until later?03:26
Loquacitiesjust get in an do what you can03:26
Loquacitiesand*03:27
Loquacitiesgood question03:27
Loquacitieswhat do you think fifieldt?03:27
Sam-I-Amalso wondering about working on the same thing someone else is working on03:27
fifieldtI think I'll switch between both reviewing and writing03:27
fifieldtmake sure you assign yourself straight away03:28
fifieldtdon't start writing until you do03:28
Loquacitiesfifieldt: yeah, i had vague plans of the same thing03:28
Loquacitiesand yes, change the bug owner to yourself before you start03:28
Sam-I-Amsure.  i've had them stolen before...03:28
fifieldtand triage before the day if you get  a chance03:28
Loquacitiesand make sure you hit refresh on the bug before you take it, too03:28
Sam-I-Amalso found cases of similar bugs being worked on by multiple people at the same time03:29
Loquacitiesyep, it happens03:29
Sam-I-AmLoquacities: is there any way to set 'in progress' in launchpad before the first submission for review?03:29
Loquacitiesyes, you can just change the status of the bug03:29
Sam-I-Ami dont think i can triage anything in lp03:30
fifieldtyes, all users have this feature03:30
Loquacitiesbut assigning it to yourself is the best way to indicate that you're working on it03:30
*** dolphm has joined #openstack-meeting03:30
Sam-I-Amok, i see now :)03:30
Loquacitiesawesome03:30
Loquacitiesany other business?03:30
*** gokrokve has quit IRC03:31
Loquacitiesoh, before i close the meeting, i wanted to reiterate anne's comment about the docs meeting ...03:31
Loquacitiesno one is expected to attend a docs meeting that is outside of their timezone03:32
Loquacitiestwo a month is plenty, so hopefully this mechanism of alternating each week will work for that03:32
nerminai'm just online all the time03:33
Sam-I-Amthis is way outside of my time zone, but more convenient03:33
Loquacitiesnermina: sleep is for the weak ;)03:33
slong:D nermina, you work slug03:33
LoquacitiesSam-I-Am: whatever tz works for you is fine :)03:33
nerminait's overrated03:33
Loquacitiesok, that's it folks ...03:33
Loquacities#endmeeting03:33
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"03:33
openstackMeeting ended Tue Dec 17 03:33:47 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docteammeeting/2013/docteammeeting.2013-12-17-03.00.html03:33
Sam-I-Amone day i hope to fix bugs in my sleep03:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docteammeeting/2013/docteammeeting.2013-12-17-03.00.txt03:33
openstackLog:            http://eavesdrop.openstack.org/meetings/docteammeeting/2013/docteammeeting.2013-12-17-03.00.log.html03:33
Loquacitiesthanks everyone :)03:34
*** gokrokve has joined #openstack-meeting03:34
fifieldtcheers Loquacities03:34
Sam-I-Amthanks!03:34
nerminathanks03:34
*** Sam-I-Am has left #openstack-meeting03:35
*** dnavale has left #openstack-meeting03:36
*** dougshelley66 has quit IRC03:37
*** gokrokve has quit IRC03:37
*** gokrokve has joined #openstack-meeting03:40
*** otherwiseguy has quit IRC03:40
*** rongze has joined #openstack-meeting03:40
*** martinlo has left #openstack-meeting03:43
*** slong has quit IRC03:44
*** arnaud has quit IRC03:51
*** arnaud__ has quit IRC03:51
*** jecarey has joined #openstack-meeting03:54
*** gokrokve has quit IRC03:58
*** gokrokve has joined #openstack-meeting04:00
*** mdomsch has joined #openstack-meeting04:01
*** gokrokve has quit IRC04:04
*** dolphm has quit IRC04:05
*** gokrokve has joined #openstack-meeting04:05
*** gokrokve_ has joined #openstack-meeting04:08
*** gokrokve has quit IRC04:09
*** gokrokve_ has quit IRC04:09
*** gokrokve has joined #openstack-meeting04:11
*** chandankumar has joined #openstack-meeting04:16
*** coolsvap has quit IRC04:17
*** DennyZhang has joined #openstack-meeting04:18
*** DennyZhang has quit IRC04:21
*** DennyZhang has joined #openstack-meeting04:22
*** Daisy has quit IRC04:22
*** DennyZhang has quit IRC04:23
*** DennyZhang has joined #openstack-meeting04:24
*** banix has quit IRC04:25
*** banix has joined #openstack-meeting04:29
*** DennyZhang has quit IRC04:29
*** coolsvap has joined #openstack-meeting04:30
*** rongze has quit IRC04:33
*** gokrokve has quit IRC04:37
*** gokrokve has joined #openstack-meeting04:37
*** DennyZhang has joined #openstack-meeting04:38
*** MirandaZhang has left #openstack-meeting04:40
*** gokrokve has quit IRC04:41
*** coolsvap has quit IRC04:42
*** Mandell has joined #openstack-meeting04:49
*** SergeyLukjanov has joined #openstack-meeting04:49
*** coolsvap has joined #openstack-meeting04:50
*** epico has quit IRC04:53
*** epico has joined #openstack-meeting04:53
*** rongze has joined #openstack-meeting04:55
*** sarob_ has joined #openstack-meeting04:56
*** sarob has quit IRC04:58
*** rongze_ has joined #openstack-meeting04:59
*** jecarey has quit IRC04:59
*** epico has quit IRC04:59
*** epico has joined #openstack-meeting05:00
*** rongze has quit IRC05:00
*** sarob_ has quit IRC05:01
*** rongze_ has quit IRC05:04
*** qs201 has joined #openstack-meeting05:05
*** qs201 has quit IRC05:07
*** samcdona has quit IRC05:08
*** DennyZhang has quit IRC05:09
*** coolsvap has quit IRC05:16
*** gokrokve has joined #openstack-meeting05:20
*** stevemar has quit IRC05:20
*** reed has joined #openstack-meeting05:21
*** sandywalsh_ has quit IRC05:23
*** banix has quit IRC05:25
*** reed has quit IRC05:26
*** cdub_ has quit IRC05:29
*** coolsvap has joined #openstack-meeting05:29
*** spzala_ has quit IRC05:32
*** sgordon has quit IRC05:33
*** haomaiwang has joined #openstack-meeting05:34
*** cdub has joined #openstack-meeting05:35
*** garyk has quit IRC05:35
*** sandywalsh_ has joined #openstack-meeting05:39
*** markpeek has joined #openstack-meeting05:40
*** coolsvap has quit IRC05:44
*** markwash has joined #openstack-meeting05:47
*** akuznetsov has quit IRC05:51
*** sgordon has joined #openstack-meeting05:52
*** markpeek has quit IRC05:53
*** gokrokve has quit IRC05:56
*** gokrokve has joined #openstack-meeting05:56
*** gokrokve has quit IRC06:01
*** coolsvap has joined #openstack-meeting06:01
*** edleafe- has quit IRC06:06
*** edleafe has joined #openstack-meeting06:06
*** adalbas has quit IRC06:12
*** bdpayne has joined #openstack-meeting06:12
*** gokrokve has joined #openstack-meeting06:13
*** rongze has joined #openstack-meeting06:15
*** sgordon has quit IRC06:17
*** DennyZhang has joined #openstack-meeting06:19
*** sacharya has quit IRC06:20
*** DennyZhang has quit IRC06:27
*** DennyZhang has joined #openstack-meeting06:28
*** gokrokve has quit IRC06:29
*** adalbas has joined #openstack-meeting06:29
*** DennyZhang has left #openstack-meeting06:30
*** niska has quit IRC06:32
*** akuznetsov has joined #openstack-meeting06:34
*** niska has joined #openstack-meeting06:35
*** sgordon has joined #openstack-meeting06:36
*** boris-42 has joined #openstack-meeting06:36
*** markvoelker1 has quit IRC06:36
*** markwash has quit IRC06:37
*** markwash has joined #openstack-meeting06:40
*** bdpayne has quit IRC06:42
*** harlowja is now known as harlowja_away06:43
*** HenryG has quit IRC06:43
*** SergeyLukjanov has quit IRC06:45
*** marun has quit IRC06:49
*** DennyZhang has joined #openstack-meeting06:51
*** elo has joined #openstack-meeting06:51
*** vkozhukalov has quit IRC06:51
*** AaronGr_Zzz is now known as AaronGr06:52
*** DennyZhang has left #openstack-meeting06:53
*** NikitaKonovalov has joined #openstack-meeting06:55
*** DennyZhang has joined #openstack-meeting06:56
*** garyk has joined #openstack-meeting06:56
*** thomasbiege has joined #openstack-meeting06:58
*** sgordon has quit IRC07:01
*** plomakin_ has quit IRC07:01
*** pnavarro has joined #openstack-meeting07:01
*** michchap has quit IRC07:02
*** michchap has joined #openstack-meeting07:03
*** neelashah1 has quit IRC07:03
*** jcooley_ has joined #openstack-meeting07:03
*** denis_makogon has joined #openstack-meeting07:05
*** pnavarro has quit IRC07:06
*** markwash has quit IRC07:06
*** Abhishek_ has joined #openstack-meeting07:07
*** jcooley_ has quit IRC07:07
*** jcooley_ has joined #openstack-meeting07:09
*** HenryG has joined #openstack-meeting07:10
*** resker has joined #openstack-meeting07:13
*** jcooley_ has quit IRC07:14
*** esker has quit IRC07:16
*** boris-42 has quit IRC07:21
*** fifieldt has quit IRC07:22
*** DennyZhang has quit IRC07:22
*** jlibosva has joined #openstack-meeting07:28
*** epico has quit IRC07:29
*** doron_afk has joined #openstack-meeting07:29
*** Abhishek_ has quit IRC07:30
*** nelsnelson has quit IRC07:31
*** AaronGr is now known as AaronGr_Zzz07:32
*** nelsnelson has joined #openstack-meeting07:32
*** epico has joined #openstack-meeting07:33
*** zul has quit IRC07:34
*** fifieldt has joined #openstack-meeting07:35
*** DennyZhang has joined #openstack-meeting07:35
*** dougshelley66 has joined #openstack-meeting07:35
*** afazekas has joined #openstack-meeting07:37
*** DennyZhang has quit IRC07:40
*** gokrokve has joined #openstack-meeting07:40
*** oubiwan__ has quit IRC07:42
*** lsmola_ has joined #openstack-meeting07:44
*** gokrokve has quit IRC07:44
*** flaper87|afk is now known as flaper8707:46
*** bgorski has joined #openstack-meeting07:47
*** egallen has joined #openstack-meeting07:51
*** akuznetsov has quit IRC07:56
*** mrunge has joined #openstack-meeting08:00
*** zhhuabj has joined #openstack-meeting08:04
*** Kharec_ is now known as Kharec08:06
*** ArthurBerezin has joined #openstack-meeting08:07
*** amotoki has quit IRC08:09
*** jorisroovers has joined #openstack-meeting08:15
*** rakhmerov has quit IRC08:17
*** ildikov_ has quit IRC08:21
*** vkozhukalov has joined #openstack-meeting08:26
*** dperaza1 has quit IRC08:26
*** denis_makogon has quit IRC08:26
*** jtomasek has joined #openstack-meeting08:28
*** avishayb has joined #openstack-meeting08:29
*** ildikov_ has joined #openstack-meeting08:31
*** ArthurBerezin has left #openstack-meeting08:31
*** zul has joined #openstack-meeting08:34
*** jcoufal has joined #openstack-meeting08:34
*** DennyZhang has joined #openstack-meeting08:37
*** marios has quit IRC08:37
*** DinaBelova has joined #openstack-meeting08:37
*** marios has joined #openstack-meeting08:38
*** DennyZhang has quit IRC08:41
*** fifieldt has quit IRC08:43
*** HenryG has quit IRC08:43
*** HenryG has joined #openstack-meeting08:44
*** ygbo has joined #openstack-meeting08:47
*** fbo_away is now known as fbo08:47
*** jaimegil has joined #openstack-meeting08:51
*** asalkeld has quit IRC08:51
*** thomasbiege has quit IRC08:52
*** asalkeld has joined #openstack-meeting08:53
*** thomasbiege has joined #openstack-meeting08:54
*** nermina has quit IRC08:56
*** elo has quit IRC08:57
*** salv-orlando has quit IRC09:00
*** ndipanov_gone is now known as ndipanov09:01
*** aepifanov has joined #openstack-meeting09:04
*** nosnos has quit IRC09:07
*** nosnos has joined #openstack-meeting09:07
*** derekh has joined #openstack-meeting09:07
*** SergeyLukjanov has joined #openstack-meeting09:08
*** NikitaKonovalov has quit IRC09:08
*** coolsvap has quit IRC09:08
*** SergeyLukjanov has quit IRC09:09
*** yassine has joined #openstack-meeting09:09
*** SergeyLukjanov has joined #openstack-meeting09:09
*** akuznetsov has joined #openstack-meeting09:13
*** johnthetubaguy has joined #openstack-meeting09:19
*** yamahata has quit IRC09:19
*** mrunge has quit IRC09:20
*** mrunge has joined #openstack-meeting09:21
*** coolsvap has joined #openstack-meeting09:22
*** aepifanov has quit IRC09:23
*** safchain has joined #openstack-meeting09:24
*** aepifanov has joined #openstack-meeting09:25
*** fifieldt has joined #openstack-meeting09:31
*** DennyZhang has joined #openstack-meeting09:32
*** vkozhukalov has quit IRC09:35
*** Abhishek_ has joined #openstack-meeting09:39
*** hnarkaytis has quit IRC09:40
*** nelsnelson has quit IRC09:41
*** nelsnelson has joined #openstack-meeting09:42
*** andreaf has quit IRC09:43
*** masayukig has quit IRC09:47
*** aepifanov has quit IRC09:47
*** aepifanov has joined #openstack-meeting09:47
*** bauzas has joined #openstack-meeting09:49
*** vkozhukalov has joined #openstack-meeting09:50
*** boris-42 has joined #openstack-meeting09:52
*** nati_ueno has quit IRC09:53
*** DennyZhang has quit IRC09:54
*** nati_ueno has joined #openstack-meeting09:55
*** rakhmerov has joined #openstack-meeting09:55
*** SergeyLukjanov has quit IRC09:55
*** SergeyLukjanov has joined #openstack-meeting09:57
*** rakhmerov1 has joined #openstack-meeting09:58
*** rakhmerov has quit IRC09:58
bauzaso/09:58
DinaBelovao/09:59
bauzasDinaBelova: you have 50 secs for opening the meeting :p09:59
SergeyLukjanovo/09:59
DinaBelova#startmeeting climate09:59
openstackMeeting started Tue Dec 17 09:59:39 2013 UTC and is due to finish in 60 minutes.  The chair is DinaBelova. Information about MeetBot at http://wiki.debian.org/MeetBot.09:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:59
*** openstack changes topic to " (Meeting topic: climate)"09:59
openstackThe meeting name has been set to 'climate'09:59
*** Nikolay_1t has joined #openstack-meeting09:59
Nikolay_1thola09:59
bauzaso/09:59
bauzas(again :D)10:00
Nikolay_1tyeap10:00
DinaBelovaMe and Sergey are also here10:00
DinaBelovaf_rossigneux_, scroiset_?10:00
f_rossigneux_Hi10:00
DinaBelovaOk, nice10:00
*** doron_afk is now known as doron10:00
DinaBelovascroiset_, are you here?10:00
bauzasscroiset is still on paternity leave :)10:00
DinaBelovaOk, forgot about it10:01
DinaBelovalet's start then10:01
bauzassure10:01
DinaBelovahttps://wiki.openstack.org/wiki/Meetings/Climate#Agenda_for_December_17_201310:01
DinaBelovait's our agenda10:01
DinaBelovafor today10:01
bauzaspretty busy agenda :)10:01
bauzaswe have to be quick :)10:01
DinaBelova#topic  Action items from the last meeting + reviews queries10:01
*** openstack changes topic to "Action items from the last meeting + reviews queries (Meeting topic: climate)"10:01
bauzasesp. there are quite chatty topics10:01
DinaBelovaAs for the actioan items from last session10:02
DinaBelova#link http://eavesdrop.openstack.org/meetings/climate/2013/climate.2013-12-09-20.01.html10:02
DinaBelovaLet's move through them quickly10:02
DinaBelovaNick, you had two of them10:02
bauzasI can't get the webpage, so I will only speak by mind10:02
DinaBelovabauzas, ok10:03
DinaBelovaNikolay_1t, as I see you have delivered new patchsets as discussed10:03
DinaBelovagreat10:03
Nikolay_1tyeap10:03
bauzasok, any reviews needed ?10:03
Nikolay_1tand also for vm_plugin10:03
DinaBelovaAs for my action item, I also reviewed it https://review.openstack.org/#/c/57200/10:03
bauzassaw it10:03
Nikolay_1tbauzas: yes, please10:03
bauzasok, which ones to be prioritized ?10:04
Nikolay_1ttoday we'll test all this stuff about vms10:04
Nikolay_1twell10:04
bauzasall of them ? :D10:04
DinaBelovabauzas, they are connected with each other10:04
Nikolay_1tyou were interested in openstack utils10:04
bauzassure, will do again10:04
DinaBelovathe last won't work without first two :)10:04
bauzasmy concern is just about time :)10:04
DinaBelovabauzas, they all are needed for the release 0.110:05
bauzasbecause I will be on holidays starting end of this week, until Jan 410:05
DinaBelovabauzas, we need to try review all of them10:05
DinaBelovaas yours ones10:05
Nikolay_1tutils-->trust-->plugin10:05
bauzasok, will do10:05
DinaBelovabecause in the other case we need to postpone release10:05
bauzasyup, that's something we need to discuss afterwards10:06
SergeyLukjanovdue to the holidays in FR and RU it sounds impossible to release 0.1 before the NY10:06
DinaBelovabauzas, you had two action items10:06
DinaBelovaSergeyLukjanov, looks so for me too10:06
SergeyLukjanovso, it sounds reasonable to move release to the mid-end Jan10:06
DinaBelova...10:06
Nikolay_1t...10:06
bauzaswhat are your vacancies ?10:06
DinaBelovaSergeyLukjanov, maybe that's a good point10:06
SergeyLukjanovme and Dina have 2w vacations around the NY10:07
bauzasok, let's discuss that on the next topic item10:07
DinaBelovaok10:07
bauzasso for my action items10:07
DinaBelovabauzas, you have two of them10:07
bauzasI had to fix a blueprint10:07
bauzasit's done10:07
DinaBelovagreat10:07
bauzassorry, can't give you the link :(10:07
DinaBelovathe next one was Agree on delivery date10:07
DinaBelovadon't worry, we'll find it10:08
bauzasyup, and as said, we're focusing on delivering the merge code by this week10:08
DinaBelovathe second one was about when you10:08
DinaBelova... will have all needed for hosts reservation implemented10:08
bauzasso I would say the prototype would be there, but it would still require reviews10:08
DinaBelovabauzas, ok, nice10:08
DinaBelovawe have the folowing open reviews now10:09
DinaBelova#link https://review.openstack.org/#/q/status:open+project:stackforge/climate,n,z10:09
DinaBelovachanges by Nikolay_1t are essential for the VM reservation10:09
bauzaswe're still missing a Climate filter for hosts reservations, but that's only for preventing other requests to be spawn on the hosts10:10
bauzasand we also need to hack the client10:10
DinaBelovaand we have 3 changes by bauzas and one by f_rossigneux_10:10
DinaBelovabauzas, as for client10:10
DinaBelovaI propose to merge first commit10:10
DinaBelovaafter some testing10:10
DinaBelovabecause we have large patchset really...10:10
bauzassure10:10
DinaBelovatoo large...10:11
bauzaswhich one is huge ?10:11
* SergeyLukjanov thinking about the pros/cons of weekly reviews sync10:11
bauzasclient CR ?10:11
DinaBelovain climate it's Francois's one10:11
DinaBelovaand in client it's my10:11
DinaBelovaI'll try to find way of splitting for both of them10:11
DinaBelovaI think we should move to next topic10:12
bauzassorry, can't get the point10:12
DinaBelovabauzas, they are too huge to be quick reviewed10:12
bauzasah ok10:12
DinaBelovaI think we should move to next topic, because we do not have much time10:12
f_rossigneux_My patchet could be splitted in two parts: the reservation plugin and the reservation algos.10:12
DinaBelovaf_rossigneux_, would be nice if you'll do it10:12
bauzasHost Admin Manager and Physical Host Reservation are the only ones scoped for 0.110:13
DinaBelovabecause it's almost impossible to review huve amount of code quickly10:13
bauzasthere will be a 3rd one10:13
DinaBelovahuge*10:13
DinaBelovabauzas, ok10:13
bauzasthe review will be the merge of all the code10:13
*** comay has quit IRC10:13
DinaBelovabauzas, can't get your point10:13
bauzassorry10:14
*** comay has joined #openstack-meeting10:14
bauzasI will provide another CR for merging both Francois and mine' code10:14
DinaBelovahm...10:14
DinaBelovathey are quite big10:14
DinaBelovathemselves10:14
bauzasyup10:14
DinaBelovaif there is possibility to stay for them separated10:15
bauzasyep10:15
DinaBelovait would be nice10:15
DinaBelovato review them in more comfortable way10:15
DinaBelovaok?10:15
DinaBelovaI think we have discussed also the second topic somehow :)10:15
bauzasthat's why I'm doing a merging CR, only for managing the few discrepancies10:15
bauzasbut let's discuss that offline10:15
DinaBelovaok10:15
bauzasbecause the automatic merge is failing on some patches10:16
DinaBelovaI think we may move to the Openstack new Program or not?10:16
DinaBelovabecause the second topic was also discussed10:16
DinaBelovaIs that ok for you?10:16
bauzaswhich date do we plan ?10:16
SergeyLukjanovJan 21/24 should work10:16
DinaBelovabauzas, I think that should be second half of the Jan10:17
bauzasagree10:17
DinaBelovabecause of all these holidays10:17
DinaBelovaok10:17
SergeyLukjanov21/2310:17
bauzasok10:17
bauzasDinaBelova: could you please raise that point ?10:17
DinaBelova#agreed New release date Jan 21/2310:17
DinaBelovaok10:17
SergeyLukjanov%(meeting_chair) please add info item10:17
SergeyLukjanovsee it ;)10:17
DinaBelovalet's move to the Openstack new Program or not? https://wiki.openstack.org/wiki/Governance/NewPrograms10:18
DinaBelovaok?10:18
SergeyLukjanovyup10:18
bauzassure, new topic ?10:18
bauzas:10:18
DinaBelova#topic Openstack new Program or not? https://wiki.openstack.org/wiki/Governance/NewPrograms10:18
bauzas:D10:18
*** openstack changes topic to "Openstack new Program or not? https://wiki.openstack.org/wiki/Governance/NewPrograms (Meeting topic: climate)"10:18
DinaBelovaok, as we want to be incubated somehow10:18
DinaBelovawe need to think about our program10:18
bauzasso, I don't feel quite comfortable with this10:18
DinaBelovathere are some existing ones10:18
DinaBelova#link https://wiki.openstack.org/wiki/Programs10:18
bauzasthat's something which is unclear, even for TC10:18
bauzaswe are a new team10:19
SergeyLukjanovit looks like there is now existing program fully compatible with project's scope/plans10:19
bauzass/now/no ?10:19
DinaBelovayep10:19
DinaBelova*no*10:19
SergeyLukjanovbauzas, yes10:19
SergeyLukjanovthere is no such program10:19
DinaBelovaSo I propose to heve new program like "Resource Reservation"10:19
DinaBelovaor something like this10:19
SergeyLukjanovor just reservations10:20
bauzasif we agree with that, we would need to ask for a mission statement10:20
DinaBelovaSergeyLukjanov, yes10:20
*** _jmp_ has quit IRC10:20
DinaBelovabauzas, so we need to create document, describing our project, our view on it10:20
SergeyLukjanovI think that we should start working on Incubation application without sending it10:20
DinaBelovaSergeyLukjanov,10:20
DinaBelova+110:20
SergeyLukjanovjust to be sure that everything is ok10:20
bauzasjust one comment, our current usecases could all fit under the Compute umbrella :)10:20
DinaBelovanot really...10:20
SergeyLukjanovbauzas, there are plans for supporting all other services/resources for reservations10:21
bauzaswell, reserving Nova resources could be seen as a feature of Nova :)10:21
SergeyLukjanovlike stacks, networks and etc.10:21
bauzasfloating IPs are Nova10:21
Nikolay_1tno10:21
bauzaswe need to provision routers10:21
DinaBelovabauzas, we have plans about new resources - Neutron's, Heat's10:21
Nikolay_1tIPs is neutron10:21
DinaBelovaand we were talking about reserving of storage nodes10:22
DinaBelovaand so on10:22
bauzasyup10:22
DinaBelovaso that's not about Nova10:22
Nikolay_1ton last summit they said that it's a good point to manage network resources using Neutron10:22
DinaBelovaCompute, sorry***10:22
bauzasI'm just speaking as Devil lawyer :)10:22
DinaBelovabauzas,10:22
DinaBelova:D10:22
DinaBelovaok, so agreed on creating new prorram10:22
bauzasbecause if we apply as new Program, there will be some contradictors10:22
bauzas#agreed ? :D10:22
DinaBelovabauzas, sorry10:23
DinaBelovalost your disagreements10:23
DinaBelovawhat kind of contradictors?10:23
SergeyLukjanovthere are still no programs with more than one project in it :)10:23
bauzasnah nah, I'm just saying I'm OK, but we need to prepare our mission statement10:23
DinaBelovabauzas, absolutely!10:23
bauzasprovisioning Neutron routers should be explicit10:24
SergeyLukjanovexcept maybe TripleO + Tuskar, but I don't know much about their relationship10:24
bauzasSergeyLukjanov: I could speak about them, but we would be running out of time :)10:24
DinaBelova#agreed Prepare new program's description and start working on incubation proposal with mission, etc.10:24
*** ArthurBerezin has joined #openstack-meeting10:24
DinaBelovaokay10:24
bauzasthese discussions should be public thanks to the ML10:25
SergeyLukjanovwriting new program application + incubation application will help us to analyze the gaps in scope/etc.10:25
DinaBelovaSergeyLukjanov, +110:25
DinaBelovabauzas, of course10:25
DinaBelovaare you ok with moving to the next topic?10:25
bauzasok, once we agreed that, we need to go to the next point10:25
bauzasbecause there is a consequence10:25
DinaBelova#topic PTL election questions10:25
*** openstack changes topic to "PTL election questions (Meeting topic: climate)"10:26
DinaBelovaI've asked Sergey to help us10:26
DinaBelovabecause he has much more experience :)10:26
bauzasjd__ could also help10:26
DinaBelovabauzas, of course10:26
SergeyLukjanovthere are many options on how to make it, but I think that the right approach for climate is to use the common OS process10:26
bauzassure10:26
SergeyLukjanov1w for proposing candidates10:26
bauzasa Condorcet election10:26
SergeyLukjanovself-propositions I mean10:26
SergeyLukjanov+ 1w for elections10:26
SergeyLukjanovyup http://civs.cs.cornell.edu10:26
bauzasyup, we need to formalize that10:27
SergeyLukjanov#info http://civs.cs.cornell.edu10:27
*** Shaan7 has quit IRC10:27
bauzasthere is a link for this10:27
bauzashold on10:27
SergeyLukjanovyup, process is well defined10:27
bauzasthat's on wiki10:27
bauzaswe just need to propose the process and vote for it10:28
*** doron is now known as doron_afk10:28
*** Jianyong has quit IRC10:28
SergeyLukjanovbauzas, I can do it for the next meeting10:28
SergeyLukjanovwe've done the same in Savanna10:28
SergeyLukjanovand I can find old etherpads10:28
DinaBelovaSergeyLukjanov, yes, I saw that10:28
*** ArthurBerezin has quit IRC10:29
SergeyLukjanovhttps://wiki.openstack.org/wiki/Election_Officiating_Guidelines10:29
bauzasthat's basically only matter of giving the wikipage, and asking for +1/-1 ?10:29
SergeyLukjanovsome info ^^10:29
*** Jianyong has joined #openstack-meeting10:29
bauzasso, we agree on the proposal, and then we go thru it10:29
*** epico has quit IRC10:29
SergeyLukjanovI think that the process is well defined, so, we just to agree on that by voting on the next meeting for example10:29
SergeyLukjanovthen wait foor candidates for a week10:29
bauzasexactly10:30
SergeyLukjanovand then setup condorset elections10:30
bauzasthat's what I was trying to sat :)10:30
bauzassay10:30
DinaBelovaand then have 1week lonf elections10:30
SergeyLukjanovI think that I now several questions10:30
bauzasit will be a little hard due to the vacancies10:30
SergeyLukjanovthat we'll need to discuss10:30
DinaBelovaSergeyLukjanov, what are they?10:31
DinaBelovabauzas, what do you mean?10:31
*** paragan has quit IRC10:31
SergeyLukjanov1. for which time range we'll elect ptl10:31
SergeyLukjanov2. how we'll collect ATCs list10:31
bauzas+110:31
DinaBelovaokay10:31
bauzas1. 6 months sound okay to me10:32
SergeyLukjanovso, for the #1 icehouse will be the best option10:32
SergeyLukjanovto be aligned with openstack elections10:32
bauzaswell, that's a good point10:32
SergeyLukjanovin savanna we've elected me for the end of current and next cycle10:32
SergeyLukjanovit works too :)10:32
DinaBelovaso we are speaking about time till the end of Icehouse release10:32
DinaBelovaam I right?10:33
bauzasyup10:33
*** jcooley_ has joined #openstack-meeting10:33
bauzas4 months10:33
bauzasand then we revote10:33
SergeyLukjanovIf we'll complete elections in mid-end Jan than it'll the mid Icehouse10:33
SergeyLukjanovlooks like that it's ok10:33
DinaBelovaok, nice10:33
SergeyLukjanovlet's setup voting right now?10:33
DinaBelovaNikolay_1t, are you ok with that?10:33
SergeyLukjanovit'll be better to have voting results for all our decisions10:33
DinaBelovaSergeyLukjanov, +110:34
Nikolay_1t+1 for icehouse PTL10:34
bauzas+1 for Icehouse timeframe10:34
DinaBelova#startvote Elect PTL for the Icehouse timeframe? Yes,No10:34
openstackBegin voting on: Elect PTL for the Icehouse timeframe? Valid vote options are Yes, No.10:35
openstackVote using '#vote OPTION'. Only your last vote counts.10:35
SergeyLukjanov#vote Yes10:35
bauzas#vote Yes10:35
DinaBelova#vote Yes10:35
f_rossigneux_#vote Yes10:35
Nikolay_1t#vote Yes10:35
bauzasok, we can close the vote :)10:36
SergeyLukjanovlooks like that's enough :)10:36
DinaBelova#endvote10:36
openstackVoted on "Elect PTL for the Icehouse timeframe?" Results are10:36
openstackYes (5): bauzas, f_rossigneux_, DinaBelova, SergeyLukjanov, Nikolay_1t10:36
SergeyLukjanovyay!10:36
DinaBelova:)10:36
SergeyLukjanovthe next question is about choosing electorate10:36
DinaBelovaso the next point was about how we'll collect ATCs list10:36
bauzasok, next question was : how we can find Climate ATCs ?10:36
SergeyLukjanovthe common practice is take all commiters10:37
bauzaseactly10:37
Nikolay_1tyeap, that's good10:37
SergeyLukjanovbut I have a concern that there was some initial code that was obsolete and removed afaiu10:37
DinaBelovabut the question is for what period10:37
bauzasdo we also take current reviews ?10:37
Nikolay_1twell10:37
DinaBelovaIcehouse? Or whenever>10:37
Nikolay_1twhy not?10:37
DinaBelova?10:37
SergeyLukjanovbauzas, in OpenStack only existing commits used10:37
Nikolay_1ton review I think10:37
Nikolay_1t:(10:37
Nikolay_1tokay10:37
*** jcooley_ has quit IRC10:38
* SergeyLukjanov looking for the doc10:38
bauzaswell, briefly checking at the git log10:38
DinaBelovaThat's for the Icehouse http://stackalytics.com/?release=icehouse&metric=commits&project_type=stackforge&module=climate&company=&user_id=10:38
SergeyLukjanovI have some scripts to build ATC list10:38
bauzaslet's vote then10:38
DinaBelovaThat's for all periods http://stackalytics.com/?release=all&metric=commits&project_type=stackforge&module=climate&company=&user_id=10:38
SergeyLukjanovare there any initial thoughts to exclude initial climate code?10:39
bauzasI don't think we have to exclude10:39
bauzasbecause any committed code is good for climate10:39
bauzaseven if that's useless now10:39
SergeyLukjanovbut it was replaced, isn't it?10:40
bauzasthat would send a bad signal10:40
SergeyLukjanovdoesn't really matter for me10:40
bauzasand that doesn't change10:40
bauzasthe list of ATCs10:40
*** vkozhukalov has quit IRC10:40
bauzasbut that would only be a terrible mistake in terms of communication10:40
SergeyLukjanovExcept otherwise-noted in the program description, the electorate for a given program PTL election are the Foundation individual members that are also committers for one of the program projects over the Grizzly-Havana timeframe10:40
bauzasgenerally speaking, a 2 cycle-period is a timeframe for electing ATCs10:41
SergeyLukjanovyup10:41
DinaBelovaAs i looked, the list of ATC will be the same anyway10:41
SergeyLukjanovok10:41
SergeyLukjanovso, let's vote to confirm it10:41
bauzasok10:41
*** ArthurBerezin has joined #openstack-meeting10:42
DinaBelova#startvote Use 2 OpenStack release cycles as a timeframe for electing ATCs? Yes,No10:42
openstackBegin voting on: Use 2 OpenStack release cycles as a timeframe for electing ATCs? Valid vote options are Yes, No.10:42
openstackVote using '#vote OPTION'. Only your last vote counts.10:42
bauzas#vote Yes10:42
DinaBelova#vote Yes10:42
SergeyLukjanov#vote Yes10:42
f_rossigneux_#vote Yes10:42
Nikolay_1t#vote Yes10:42
DinaBelova#endvote10:43
openstackVoted on "Use 2 OpenStack release cycles as a timeframe for electing ATCs?" Results are10:43
openstackYes (5): bauzas, f_rossigneux_, DinaBelova, SergeyLukjanov, Nikolay_1t10:43
bauzasok10:43
DinaBelovaokay10:43
SergeyLukjanovok10:43
SergeyLukjanovdo we have any other topics to discuss?10:43
bauzasa big one :(10:43
SergeyLukjanovexcept elections10:43
bauzasCafe10:43
DinaBelovaI think for this topic that's it10:43
DinaBelovalet's move to the next10:43
*** jcooley_ has joined #openstack-meeting10:43
SergeyLukjanovI need some time to think about other elections-related stuff10:43
DinaBelovaSergeyLukjanov, okay10:44
SergeyLukjanov#action SergeyLukjanov to prepare aggregated doc about Climate PTL elections10:44
DinaBelova#topic Cafe project https://wiki.openstack.org/wiki/Cafe10:44
*** openstack changes topic to "Cafe project https://wiki.openstack.org/wiki/Cafe (Meeting topic: climate)"10:44
bauzashow did you find them ?10:44
DinaBelovaOkay, today I found one email10:44
bauzasbecause I can't find any code on Stackforge10:44
*** sushil_ has joined #openstack-meeting10:44
DinaBelova#link http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg11857.html10:44
DinaBelovabecause they have not shared it yet10:44
Nikolay_1tjust from mailing list, yes10:45
DinaBelovaBut their initiative was after ours10:45
DinaBelovaAnd Nick and I wrote them to look on Climate10:45
bauzasmissed it ?!10:45
DinaBelovabauzas, looks so...10:45
bauzasok, anyway, let's wait for feedback10:46
bauzasthat's something we need to know10:46
DinaBelovabecause they definitely have overlaps with us....10:46
bauzaswhat's bad is that they did prototype without checking what's existing10:46
SergeyLukjanovoverlaps, or climate do the same?10:46
DinaBelovaSergeyLukjanov, not really a copy10:46
DinaBelovabut the most of things - yes10:46
bauzasok, then maybe that's good news then :)10:47
DinaBelovathe only thing they have different from us - they propose the users creating mechanism in the Cafe10:47
bauzasbecause if they have new usecases, then they could contribute to Climate10:47
SergeyLukjanovit'll be really cool to have one more team and usecases pack10:47
bauzas+110:47
*** mrunge has quit IRC10:47
DinaBelova+110:47
DinaBelovaso let's wait their reaction10:47
*** zul has quit IRC10:47
bauzassure10:47
*** jcooley_ has quit IRC10:48
bauzasanyway, we're pretty well implemented now10:48
bauzasso I'm not so worried10:48
*** jcooley_ has joined #openstack-meeting10:48
DinaBelovaand the thing is they did not share their code proposal...10:48
SergeyLukjanovbtw today will be tc meeting with the final barbician incubation discussions, so, it could be useful for you guys10:48
DinaBelovaso we know nothing about what do they relly implemented10:48
*** zul has joined #openstack-meeting10:48
bauzasClimate is already known by TC10:49
*** sushil_ has quit IRC10:49
DinaBelovaSergeyLukjanov, let's move it now to the open discussion10:49
DinaBelovabauzas, that's about incubaion process10:49
bauzasyup, followed ity10:49
DinaBelova#topic Open discussion10:49
*** openstack changes topic to "Open discussion (Meeting topic: climate)"10:49
SergeyLukjanovbauzas, I'm speaking not about talking about climate but listening about how other guys trying to become incubated ;)10:49
DinaBelovaok, so I think we may take a look on this process closer :)10:50
DinaBelovaSergeyLukjanov, yep10:50
bauzasSergeyLukjanov: yup yup10:50
DinaBelovaThey had problems10:50
DinaBelovawe may prevent them on our case10:50
bauzasSergeyLukjanov: I'm just saying that Climate is already known10:50
DinaBelova:)10:50
bauzascontrary to Cafe10:50
SergeyLukjanovyup and it's good10:50
SergeyLukjanovand that's cool that Tim B. points to climate in response to the cafe proposal10:51
bauzaswell, about holidays, maybe we should just share our periods10:51
DinaBelovaI was really impressed Tim Bell said about us :) We have met on Summit, but discussed another problem10:51
DinaBelovaSo I was glad he noticed our Climate thing10:51
DinaBelovaok, as for holidays10:51
bauzasI spoke with Tim Bell last week10:51
bauzasthat's why he knew it10:51
DinaBelovaok10:52
*** vkozhukalov has joined #openstack-meeting10:52
bauzasthis guy was leading the CERN summit where I presented Climate10:52
SergeyLukjanovlet's make one more vote to confirm how candidates for ptl elections will be choosen10:52
*** Jianyong has quit IRC10:52
bauzasand my team and I are planning to go back at CERN speaking about our usecases10:52
SergeyLukjanovI mean that anyone can self-nominate10:52
*** jcooley_ has quit IRC10:52
*** sushil_ has joined #openstack-meeting10:53
*** mrunge has joined #openstack-meeting10:53
SergeyLukjanovand I think that there is no need to make voting to confirm http://www.cs.cornell.edu/w8/~andru/civs/ as a tool and to confirm 1w elections duration10:53
*** jcooley_ has joined #openstack-meeting10:53
DinaBelova#startvote May the PTL candidate be self-nominated? Yes,No10:53
openstackBegin voting on: May the PTL candidate be self-nominated? Valid vote options are Yes, No.10:53
openstackVote using '#vote OPTION'. Only your last vote counts.10:54
bauzas#vote Yes10:54
SergeyLukjanovmay -> should10:54
DinaBelovaoh10:54
DinaBelovasorry10:54
DinaBelova#undo10:54
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x3963790>10:54
DinaBelovahm10:55
SergeyLukjanovhm, looks like there is no more open discussions :)10:55
bauzasclose the vote and reopen it10:55
DinaBelova#endvote10:55
openstackVoted on "May the PTL candidate be self-nominated?" Results are10:55
openstackYes (1): bauzas10:55
bauzasoops :)10:55
DinaBelova#startvote Should the PTL candidate be self-nominated? Yes,No10:55
openstackBegin voting on: Should the PTL candidate be self-nominated? Valid vote options are Yes, No.10:55
openstackVote using '#vote OPTION'. Only your last vote counts.10:55
bauzas#vote Yes10:55
DinaBelova#vote Yes10:55
SergeyLukjanov#vote Yes10:55
f_rossigneux_#vote Yes10:56
Nikolay_1t#vote Yes10:56
DinaBelova#endvote10:56
openstackVoted on "Should the PTL candidate be self-nominated?" Results are10:56
openstackYes (5): bauzas, f_rossigneux_, DinaBelova, SergeyLukjanov, Nikolay_1t10:56
bauzasok10:56
*** suo has quit IRC10:56
SergeyLukjanovit looks like all elections-related question are already discussed and we can send an announce 1w for self-nomination10:56
bauzas+110:57
DinaBelovaOk, so that's it :)10:57
DinaBelovabye, guys :)10:57
DinaBelova#endmeeting10:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"10:57
openstackMeeting ended Tue Dec 17 10:57:34 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:57
Nikolay_1tbye10:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/climate/2013/climate.2013-12-17-09.59.html10:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/climate/2013/climate.2013-12-17-09.59.txt10:57
openstackLog:            http://eavesdrop.openstack.org/meetings/climate/2013/climate.2013-12-17-09.59.log.html10:57
*** jaimegil has quit IRC10:57
SergeyLukjanovok, I'll aggregate info about elections and return back todays night with an email in ML10:57
*** jcooley_ has quit IRC10:58
*** jcooley_ has joined #openstack-meeting10:58
bauzasok10:58
*** SergeyLukjanov has quit IRC11:01
*** jcooley_ has quit IRC11:03
*** jcooley_ has joined #openstack-meeting11:04
*** pnavarro has joined #openstack-meeting11:04
*** egallen_ has joined #openstack-meeting11:06
*** flaper87 is now known as flaper87|afk11:07
*** egallen has quit IRC11:07
*** egallen_ is now known as egallen11:07
*** jcooley_ has quit IRC11:08
*** coolsvap has quit IRC11:08
*** ruhe has joined #openstack-meeting11:08
*** nati_ueno has quit IRC11:10
*** nati_ueno has joined #openstack-meeting11:11
*** DinaBelova has quit IRC11:11
*** nati_uen_ has joined #openstack-meeting11:12
*** safchain has quit IRC11:14
*** jcooley_ has joined #openstack-meeting11:14
*** nati_ueno has quit IRC11:15
*** marun has joined #openstack-meeting11:17
*** jcooley_ has quit IRC11:19
*** jcooley_ has joined #openstack-meeting11:19
*** rongze has quit IRC11:19
*** egallen has quit IRC11:20
*** kwhitney has quit IRC11:21
*** NikitaKonovalov has joined #openstack-meeting11:23
*** jcooley_ has quit IRC11:23
*** Haomeng has left #openstack-meeting11:24
*** jcooley_ has joined #openstack-meeting11:24
*** DinaBelova has joined #openstack-meeting11:25
*** SergeyLukjanov has joined #openstack-meeting11:26
*** fifieldt has quit IRC11:27
*** pnavarro has quit IRC11:28
*** salv-orlando has joined #openstack-meeting11:28
*** jcooley_ has quit IRC11:29
*** rdxc has joined #openstack-meeting11:29
*** jcooley_ has joined #openstack-meeting11:30
*** ArthurBerezin has left #openstack-meeting11:32
*** SergeyLukjanov has quit IRC11:34
*** jcooley_ has quit IRC11:34
*** jcooley_ has joined #openstack-meeting11:35
*** rfolco has joined #openstack-meeting11:36
*** SergeyLukjanov has joined #openstack-meeting11:37
*** jcooley_ has quit IRC11:39
*** jcooley_ has joined #openstack-meeting11:40
*** ruhe has quit IRC11:42
*** ruhe has joined #openstack-meeting11:43
*** akuznetsov has quit IRC11:43
*** rongze has joined #openstack-meeting11:44
*** zoresvit has joined #openstack-meeting11:45
*** jcooley_ has quit IRC11:45
*** rongze_ has joined #openstack-meeting11:45
*** ArxCruz has joined #openstack-meeting11:45
*** jcooley_ has joined #openstack-meeting11:46
*** salv-orlando has quit IRC11:47
*** jaimegil has joined #openstack-meeting11:47
*** ruhe has quit IRC11:48
*** rongze has quit IRC11:49
*** HenryG has quit IRC11:50
*** jcooley_ has quit IRC11:50
*** jcooley_ has joined #openstack-meeting11:51
*** chandankumar has quit IRC11:53
*** chandankumar has joined #openstack-meeting11:53
*** jcooley_ has quit IRC11:55
*** jcooley_ has joined #openstack-meeting11:56
*** jcooley_ has quit IRC12:01
*** jcooley_ has joined #openstack-meeting12:01
*** rongze_ has quit IRC12:03
*** akuznetsov has joined #openstack-meeting12:04
*** jcooley_ has quit IRC12:05
*** shakayumi has joined #openstack-meeting12:06
*** salv-orlando has joined #openstack-meeting12:10
*** salv-orlando has quit IRC12:10
*** jcooley_ has joined #openstack-meeting12:11
*** fifieldt has joined #openstack-meeting12:13
*** akuznetsov has quit IRC12:15
*** akuznetsov has joined #openstack-meeting12:15
*** msdubov has joined #openstack-meeting12:15
*** jcooley_ has quit IRC12:15
*** jcooley_ has joined #openstack-meeting12:16
*** akscram has quit IRC12:17
*** Abhishek_ has quit IRC12:17
*** jcooley_ has quit IRC12:21
*** jcooley_ has joined #openstack-meeting12:21
*** jaimegil has quit IRC12:22
*** ihrachyska has joined #openstack-meeting12:23
*** akuznetsov has quit IRC12:25
*** jcooley_ has quit IRC12:25
*** ArthurBerezin has joined #openstack-meeting12:26
*** jcooley_ has joined #openstack-meeting12:26
*** jaimegil has joined #openstack-meeting12:27
*** ArthurBerezin has left #openstack-meeting12:28
*** dolphm has joined #openstack-meeting12:29
*** jcooley_ has quit IRC12:30
*** jcooley_ has joined #openstack-meeting12:31
*** msdubov has quit IRC12:33
*** marios_ has joined #openstack-meeting12:33
*** marios_ has quit IRC12:33
*** yaguang has quit IRC12:33
*** paragan has joined #openstack-meeting12:33
*** rongze has joined #openstack-meeting12:34
*** jaimegil has quit IRC12:35
*** jcooley_ has quit IRC12:36
*** jcooley_ has joined #openstack-meeting12:37
*** jcooley_ has quit IRC12:37
*** jcooley_ has joined #openstack-meeting12:38
*** jorisroovers has quit IRC12:40
*** rongze has quit IRC12:42
*** jcooley_ has quit IRC12:42
*** jcooley_ has joined #openstack-meeting12:43
*** jcooley_ has quit IRC12:43
*** egallen has joined #openstack-meeting12:45
*** jcooley_ has joined #openstack-meeting12:49
*** nosnos has quit IRC12:51
*** jcooley_ has quit IRC12:54
*** andreaf has joined #openstack-meeting12:54
*** jcooley_ has joined #openstack-meeting12:54
*** akuznetsov has joined #openstack-meeting12:55
*** SergeyLukjanov has quit IRC12:56
*** SergeyLukjanov has joined #openstack-meeting12:58
*** jcooley_ has quit IRC12:59
*** jcooley_ has joined #openstack-meeting13:00
*** afazekas has quit IRC13:02
*** pdmars has joined #openstack-meeting13:03
*** jcooley_ has quit IRC13:04
*** jcooley_ has joined #openstack-meeting13:04
*** yassine has quit IRC13:06
*** nati_uen_ has quit IRC13:06
*** yassine has joined #openstack-meeting13:06
*** jcooley_ has quit IRC13:09
*** jcooley_ has joined #openstack-meeting13:10
*** shakayumi has quit IRC13:10
*** shakayumi has joined #openstack-meeting13:11
*** flaper87|afk is now known as flaper8713:13
*** jcooley_ has quit IRC13:14
*** jcooley_ has joined #openstack-meeting13:14
*** haomaiwang has quit IRC13:15
*** haomaiwang has joined #openstack-meeting13:15
*** shakayumi has quit IRC13:15
*** ruhe has joined #openstack-meeting13:16
*** yamahata has joined #openstack-meeting13:17
*** rongze has joined #openstack-meeting13:18
*** dolphm has quit IRC13:18
*** egallen has quit IRC13:18
*** mrunge has quit IRC13:19
*** jcooley_ has quit IRC13:19
*** jcooley_ has joined #openstack-meeting13:19
*** egallen has joined #openstack-meeting13:20
*** thomasem has joined #openstack-meeting13:21
*** haomaiwa_ has joined #openstack-meeting13:22
*** afazekas has joined #openstack-meeting13:22
*** dolphm has joined #openstack-meeting13:23
*** ilyashakhat has joined #openstack-meeting13:23
*** resker has quit IRC13:24
*** haomaiwang has quit IRC13:24
*** weshay has joined #openstack-meeting13:24
*** haomaiwa_ has quit IRC13:24
*** jcooley_ has quit IRC13:24
*** ilyashakhat_ has quit IRC13:24
*** jcooley_ has joined #openstack-meeting13:26
*** dolphm has quit IRC13:27
*** sandywalsh_ has quit IRC13:29
*** ruhe is now known as ruhe_13:29
*** jcooley_ has quit IRC13:30
*** ruhe_ is now known as ruhe13:31
*** haomaiwang has joined #openstack-meeting13:31
*** doron_afk is now known as doron13:31
*** jcooley_ has joined #openstack-meeting13:32
*** fifieldt has quit IRC13:33
*** jdob has joined #openstack-meeting13:35
*** jcooley_ has quit IRC13:36
*** boris-42 has quit IRC13:37
*** jcooley_ has joined #openstack-meeting13:37
*** Shaan7 has joined #openstack-meeting13:37
*** Shaan7 has joined #openstack-meeting13:37
*** ruhe is now known as ruhe_13:38
*** lblanchard has joined #openstack-meeting13:38
*** cl_ has joined #openstack-meeting13:39
*** Nikolay_1t has quit IRC13:39
*** ArthurBerezin has joined #openstack-meeting13:39
*** rongze_ has joined #openstack-meeting13:39
*** ruhe_ is now known as ruhe13:41
*** sandywalsh_ has joined #openstack-meeting13:42
*** jcooley_ has quit IRC13:42
*** jcooley_ has joined #openstack-meeting13:43
*** rongze has quit IRC13:43
*** cloudon1 has joined #openstack-meeting13:43
*** cl_ has quit IRC13:44
*** rongze_ has quit IRC13:48
*** jcooley_ has quit IRC13:48
*** jcooley_ has joined #openstack-meeting13:48
*** rongze has joined #openstack-meeting13:48
*** ArthurBerezin has left #openstack-meeting13:48
*** rongze_ has joined #openstack-meeting13:49
*** dolphm has joined #openstack-meeting13:49
*** dvarga has joined #openstack-meeting13:50
*** egallen_ has joined #openstack-meeting13:51
*** dolphm has quit IRC13:51
*** dolphm_ has joined #openstack-meeting13:51
*** afazekas has quit IRC13:51
*** dougshelley66 has quit IRC13:51
*** jcooley_ has quit IRC13:52
*** rongze has quit IRC13:53
*** egallen has quit IRC13:53
*** egallen_ is now known as egallen13:53
*** jeckersb_gone is now known as jeckersb13:53
*** shakayumi has joined #openstack-meeting13:54
*** dprince has joined #openstack-meeting13:54
*** jcooley_ has joined #openstack-meeting13:54
*** jcooley_ has quit IRC13:54
*** asselin has quit IRC13:55
*** asselin has joined #openstack-meeting13:55
*** DrBacchus has joined #openstack-meeting13:55
*** DrBacchus has quit IRC13:56
*** tris has quit IRC13:56
*** aepifanov has quit IRC13:56
*** thomasbiege has quit IRC13:56
*** DrBacchus has joined #openstack-meeting13:56
*** jcooley_ has joined #openstack-meeting13:56
*** rfolco has quit IRC13:56
*** lsmola_ has quit IRC13:56
*** thomasbiege has joined #openstack-meeting13:56
*** tedross has joined #openstack-meeting13:57
*** aepifanov has joined #openstack-meeting13:58
*** dolphm_ has quit IRC13:58
*** HenryG has joined #openstack-meeting14:00
*** whenry has quit IRC14:00
*** tedross has left #openstack-meeting14:00
*** jcooley_ has quit IRC14:01
*** jcooley_ has joined #openstack-meeting14:01
*** tris has joined #openstack-meeting14:01
*** yaguang has joined #openstack-meeting14:03
*** dolphm has joined #openstack-meeting14:03
*** jdob has quit IRC14:04
*** jdob_ has joined #openstack-meeting14:04
*** jcooley_ has quit IRC14:06
*** jcooley_ has joined #openstack-meeting14:07
*** dolphm has quit IRC14:08
*** rfolco has joined #openstack-meeting14:08
*** MaxV has joined #openstack-meeting14:09
*** lsmola_ has joined #openstack-meeting14:10
*** egallen has quit IRC14:10
*** jcooley_ has quit IRC14:12
*** kenhui has joined #openstack-meeting14:12
*** jcooley_ has joined #openstack-meeting14:13
*** akscram has joined #openstack-meeting14:13
*** oubiwann has joined #openstack-meeting14:14
*** eharney has joined #openstack-meeting14:15
*** jcooley_ has quit IRC14:17
*** jcooley_ has joined #openstack-meeting14:18
*** jcooley_ has quit IRC14:18
*** jdob_ has quit IRC14:18
*** jdob has joined #openstack-meeting14:18
*** nermina has joined #openstack-meeting14:19
*** jcooley_ has joined #openstack-meeting14:20
*** ijw has joined #openstack-meeting14:21
*** banix has joined #openstack-meeting14:22
*** whenry has joined #openstack-meeting14:22
*** afazekas has joined #openstack-meeting14:23
*** doron is now known as doron_afk14:23
*** jorisroovers has joined #openstack-meeting14:23
*** jcooley_ has quit IRC14:24
*** rossella_s has joined #openstack-meeting14:24
*** tris has quit IRC14:25
*** dolphm has joined #openstack-meeting14:25
*** jcooley_ has joined #openstack-meeting14:25
cloudon1ls -lrt14:25
*** tris has joined #openstack-meeting14:25
*** rossella_s has quit IRC14:26
*** radez_g0n3 is now known as radez14:26
*** KurtMartin has joined #openstack-meeting14:26
*** msdubov has joined #openstack-meeting14:27
*** yamahata__ has quit IRC14:27
*** yamahata__ has joined #openstack-meeting14:28
*** esker has joined #openstack-meeting14:28
*** jcooley_ has quit IRC14:29
*** n16483_ has quit IRC14:30
*** jcooley_ has joined #openstack-meeting14:30
*** n16483_ has joined #openstack-meeting14:30
*** egallen has joined #openstack-meeting14:30
*** andreaf has quit IRC14:31
*** julim has joined #openstack-meeting14:31
*** ruhe has quit IRC14:31
*** shakayumi has quit IRC14:31
*** yamahata has quit IRC14:32
*** markmcclain has quit IRC14:33
*** yamahata has joined #openstack-meeting14:34
*** jcooley_ has quit IRC14:34
*** jeckersb is now known as jeckersb_gone14:35
*** Shaan7 has quit IRC14:36
*** Shaan7 has joined #openstack-meeting14:37
*** davidhadas has joined #openstack-meeting14:39
*** jcooley_ has joined #openstack-meeting14:39
*** jeckersb_gone is now known as jeckersb14:41
*** bdperkin has joined #openstack-meeting14:43
*** jcooley_ has quit IRC14:44
*** ruhe has joined #openstack-meeting14:44
*** jcooley_ has joined #openstack-meeting14:45
*** tianst has joined #openstack-meeting14:45
*** n0ano has joined #openstack-meeting14:45
*** esker has quit IRC14:46
*** jasondotstar has joined #openstack-meeting14:46
*** esker has joined #openstack-meeting14:46
*** bdperkin has quit IRC14:48
*** burt has joined #openstack-meeting14:48
*** mtreinish has quit IRC14:48
*** alpha_ori has quit IRC14:48
*** jcooley_ has quit IRC14:49
*** topol has joined #openstack-meeting14:49
*** jcooley_ has joined #openstack-meeting14:51
*** mtreinish has joined #openstack-meeting14:51
*** alpha_ori has joined #openstack-meeting14:51
*** ayoung has joined #openstack-meeting14:51
*** bauzas has left #openstack-meeting14:54
*** markpeek has joined #openstack-meeting14:55
*** jcooley_ has quit IRC14:55
*** jcooley_ has joined #openstack-meeting14:55
*** jecarey has joined #openstack-meeting14:57
*** david-lyle_ has joined #openstack-meeting14:58
*** msdubov has quit IRC14:58
*** gokrokve has joined #openstack-meeting14:58
*** chandankumar has quit IRC14:59
n0ano#startmeeting scheduler15:00
openstackMeeting started Tue Dec 17 15:00:06 2013 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: scheduler)"15:00
openstackThe meeting name has been set to 'scheduler'15:00
n0anoanyone here for the scheduler meeting?15:00
*** jcooley_ has quit IRC15:00
*** MikeSpreitzer has joined #openstack-meeting15:00
*** markmcclain has joined #openstack-meeting15:01
*** ivasev has joined #openstack-meeting15:01
*** jgallard has joined #openstack-meeting15:01
*** gokrokve has quit IRC15:01
*** gokrokve has joined #openstack-meeting15:01
*** jcooley_ has joined #openstack-meeting15:02
garykhi15:02
MikeSpreitzerhello15:03
*** matiu has quit IRC15:03
n0anoI was beginning to think I had the wrong time or something :-)15:03
*** vijendar has joined #openstack-meeting15:03
*** dane has joined #openstack-meeting15:03
*** ryanpetrello has joined #openstack-meeting15:03
comstudo/15:05
n0anohmm, looks like the mirantis guys aren't here so can't talk about the nodb scheduler status15:05
*** davidhadas has quit IRC15:05
n0anoIn that case15:05
n0ano#topic scheduler code forklift15:05
*** openstack changes topic to "scheduler code forklift (Meeting topic: scheduler)"15:05
n0anoI can definitely report that we are making good progress on separating out the scheduler code...15:06
n0anowe have created two new repos, one for the scheduler and one for the client APIs...15:06
*** toan-tran has joined #openstack-meeting15:06
n0anoyou can get to these repos at...15:06
n0ano#link https://github.com/openstack/gantt15:07
n0ano#link https://github.com/openstack/python-ganttclient15:07
*** mattymo has joined #openstack-meeting15:07
*** matiu has joined #openstack-meeting15:07
*** doron_afk is now known as doron15:08
n0anoThey are not quite ready for prime time yet, I'm trying to do a simple patch (update the  readme file) and we're having issues with Jenkens...15:08
*** davidhadas has joined #openstack-meeting15:08
*** david-lyle_ has quit IRC15:08
n0anoonce we get that resolved the repos should be ready for normal updates & reviews15:08
*** david-lyle_ has joined #openstack-meeting15:08
garyki still have issues with the client - we have yet to even talk about interfaces.15:09
garykis the client here just a interface for the rpc?15:09
*** hnarkaytis has joined #openstack-meeting15:09
n0anothat's all that's there so far but I belive it should be extended to a restfull interface15:10
*** samcdona has joined #openstack-meeting15:10
garykok, thanks for the clarification15:10
n0anocan you articulate your issues with the client, are the architectural or implementation specific?15:10
n0anos/are the/are they15:11
garykjust one concern about the developments in 2 different trees - will the imports be the diffs?15:11
*** egallen has quit IRC15:11
n0anomy thought was, until we move to the new trees, the primary development is in nova and I can take on the task of mirroring changes to the new trees.15:11
garykn0ano: i am not sure why we need a client defined at the moment. the reason for that is there is no actual API defined.15:11
alaskio/15:11
*** aepifanov has quit IRC15:12
*** stevemar has joined #openstack-meeting15:12
n0anohopefully, there won't be too many changes before we can move to the new trees15:12
*** esker has quit IRC15:12
garykok. thanks for doing this.15:12
*** dane has quit IRC15:12
*** safchain has joined #openstack-meeting15:13
n0anogaryk I think that's a reasonable concern, we should discuss the actual API and define it, the real question will be who wants to take on the task of doing that (design by committee not one of my favorite modes)15:13
*** KurtMartin has quit IRC15:13
*** KurtMartin has joined #openstack-meeting15:14
*** egallen has joined #openstack-meeting15:14
*** KurtMartin has quit IRC15:14
*** dougshelley66 has joined #openstack-meeting15:14
garyki think that the ideal place for that would be the next summit. a few people in a room… only get out for beer when there is an API defined15:14
alaskiDo we have enough details to try to define the api yet?15:14
hnarkaytisupdate on memcached scheduler: devstack was broken last week, so still can't make end-to-end tests. Hopefully this will be completed on this week15:14
*** otherwiseguy has joined #openstack-meeting15:15
garykalaski: no, not yet15:15
n0anoalaski I don't so, not yet15:15
garykall we have decided on is the forklift. which is just moving code from a to b15:15
MikeSpreitzerIn what way was DevStack broken?  How would I know about this?  (Sorry for the newbie questions)15:15
n0anoI agree with garyk, a session in Atlanta would be appropriate but we still need one person to drive15:15
*** Yathi has joined #openstack-meeting15:16
alaskigaryk: thanks, just confirming15:16
*** kevinconway has joined #openstack-meeting15:16
garykMikeSpreitzer: www.devstack.org - this is used for the gating and helping one spin up a setup with openstack15:16
*** esker has joined #openstack-meeting15:16
garykit is used for testing and development15:16
MikeSpreitzerI know that much.  My question is about how I know about it being broken.15:16
hnarkaytiskvm crushes on attempt to start new VM15:17
n0ano#topic memcached base scheduler15:17
*** openstack changes topic to "memcached base scheduler (Meeting topic: scheduler)"15:17
MikeSpreitzerIs "devstack is broken" the same as "problem in the gate"?15:17
n0anoMikeSpreitzer, +115:17
garykMikeSpreitzer: over the last few weeks the gating has been broken every now and then. Last week it was due to some issues with Neutron15:17
hnarkaytisMikeSpreitzer: no, DevStack doesn't work locally15:17
hnarkaytisit is not a problem on a gate15:18
n0anoso the problem was your local development environment was broken - ick15:18
hnarkaytiscorrect15:18
n0anobut sounds like there are gate issues also, just to make life interesting15:19
n0anohnarkaytis, will the holidays slow you down?15:19
hnarkaytiswe are in Russia, so we will have holidays in Jan15:20
hnarkaytiswe will work till Dec 31st15:20
n0anocool, you work while we play :-)15:20
hnarkaytisI expect that end-to-end tests will be completed on this week15:20
n0anohnarkaytis, with patches up for review shortly afterwards?15:21
*** nelsnelson has quit IRC15:21
hnarkaytiscrushing KVM is the only problem. We spent Friday and Monday on this15:21
MikeSpreitzersounds violent15:21
*** nelsnelson has joined #openstack-meeting15:21
hnarkaytisI will alert all reviewers via gerrit15:22
n0anohnarkaytis, tnx for the effort, looking forward to the patches, any other questions on this subject?15:23
n0anoin that case, garyk did you want to talk about instance groups (I've kind of been ignoring you)15:23
garykn0ano: sure. just wanted to give a quick update15:25
n0ano#topic instance groups15:25
*** openstack changes topic to "instance groups (Meeting topic: scheduler)"15:25
*** neelashah has joined #openstack-meeting15:25
n0anogaryk, you have the floor15:25
garyk1. we have a scheduling patch in review https://review.openstack.org/#/c/33956/15:25
*** AlanClark has joined #openstack-meeting15:25
*** yamahata has quit IRC15:26
garyk2. we are currently working on the V2 and V3 API's - the code needs a little rafactor and hopefully we'll post it sooner than later15:26
garyk3. we have the client V2 support, need to add the V3 support15:26
garykthats about it at the moment. We are progressing slowly at the moment but hope to have it all done by I215:27
n0ano(great, first set of patches I need to mirror to the new tree :-)15:27
garykif not we should be tarred and featherd :)15:27
*** spzala has joined #openstack-meeting15:27
garykregarding the new tree - maybe we should have a script that notifies if one of the files in the scheduling directory or rpc interfaces are updated….15:27
n0anogaryk, that'd be great, otherwise I was just planning on monitoring things carefully, fortunately it's a relatively know set of files to monitor15:28
*** BillArnold has joined #openstack-meeting15:29
garykn0ano: i'll try and script something for that in the coming days15:29
*** dcramer_ has joined #openstack-meeting15:29
n0anogaryk, cool, let me know, we should be able to work it out15:29
*** IlyaE has joined #openstack-meeting15:29
garykok, will do.15:30
*** DinaBelova has quit IRC15:30
*** dcramer_ has quit IRC15:30
*** coolsvap has joined #openstack-meeting15:30
n0ano#topic administrivia15:30
*** openstack changes topic to "administrivia (Meeting topic: scheduler)"15:30
garyki guess that you can go to the next topic - nothing else to update regarding the instance groups15:30
garyk:)15:30
n0anoI'm going to be out the next two week (major holidays here), unless someone else wants to chair I propose we just cancel the next two meetings and start up again on 1/7/1415:31
*** dcramer_ has joined #openstack-meeting15:31
n0anowork can still progress (email is a wonderful thing)15:31
alaski+115:32
jgallard+115:32
toan-tran+115:32
n0anoI'll take that as unanimous consent :-)15:32
n0ano#topic opens15:32
*** openstack changes topic to "opens (Meeting topic: scheduler)"15:32
garyk+115:32
n0anoAnyone have anything new for today?15:33
garykwishing you all a merry xmas and happy new year (our side of the world it is business as usual till april :()15:33
n0ano+115:33
*** rnirmal has joined #openstack-meeting15:34
*** oubiwann has quit IRC15:34
*** ayoung has quit IRC15:34
n0anoOK, I'm hearing silence, tnx everyone and we'll meet here again next year15:34
n0ano#endmeeting15:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:35
openstackMeeting ended Tue Dec 17 15:35:16 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:35
alaskithanks15:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-12-17-15.00.html15:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-12-17-15.00.txt15:35
openstackLog:            http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-12-17-15.00.log.html15:35
*** MikeSpreitzer has quit IRC15:35
*** toan-tran has quit IRC15:35
*** jgallard has quit IRC15:35
*** luis_fdez has joined #openstack-meeting15:37
*** tanisdl has joined #openstack-meeting15:39
*** sarob has joined #openstack-meeting15:40
*** sarob has quit IRC15:40
*** sarob has joined #openstack-meeting15:40
*** reed has joined #openstack-meeting15:40
*** dcramer_ has quit IRC15:41
*** pcm has joined #openstack-meeting15:42
*** hnarkaytis has quit IRC15:42
*** DinaBelova has joined #openstack-meeting15:42
*** sarob has quit IRC15:43
*** sarob has joined #openstack-meeting15:45
*** Yathi has quit IRC15:46
*** jcoufal has quit IRC15:47
*** sarob has quit IRC15:48
*** sarob_ has joined #openstack-meeting15:48
*** SergeyLukjanov has quit IRC15:48
*** DinaBelova has quit IRC15:48
*** esker has quit IRC15:49
*** esker has joined #openstack-meeting15:50
*** NikitaKonovalov has quit IRC15:50
*** vkozhukalov has quit IRC15:51
*** fnaval has quit IRC15:51
*** ijw has left #openstack-meeting15:51
*** doron is now known as doron_afk15:52
*** sarob_ has quit IRC15:53
*** salv-orlando has joined #openstack-meeting15:53
*** alexpilotti has joined #openstack-meeting15:54
*** fnaval has joined #openstack-meeting15:56
*** jecarey has quit IRC15:56
*** dolphm is now known as dolphm_afk15:57
*** johnthetubaguy1 has joined #openstack-meeting15:57
*** johnthetubaguy has quit IRC15:58
*** boris-42 has joined #openstack-meeting15:59
jamespageo/16:00
jamespagegah - wrong -meeting :-)16:01
*** bdpayne has joined #openstack-meeting16:02
*** radez is now known as radez_g0n316:02
*** bnemec_ is now known as bnemec16:02
*** eharney has quit IRC16:03
*** eharney has joined #openstack-meeting16:03
primeministerphi all16:03
primeministerp#startmeeting hyper-v16:03
openstackMeeting started Tue Dec 17 16:03:54 2013 UTC and is due to finish in 60 minutes.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.16:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:03
*** openstack changes topic to " (Meeting topic: hyper-v)"16:03
openstackThe meeting name has been set to 'hyper_v'16:03
primeministerpquick meeting today just to catch up16:04
primeministerpmtaylor: ping16:04
*** ociuhandu has joined #openstack-meeting16:05
primeministerpalexpilotti: ping16:05
primeministerpalexpilotti: do you have anything to discuss today, I know we everyone is busy prior to the holidays16:05
*** tianst has quit IRC16:05
alexpilottiyep16:07
alexpilottiwe have new on cloudbase-init16:07
alexpilottipasswordless authentication16:07
primeministerpalexpilotti: nice16:08
primeministerpalexpilotti: anything else16:11
alexpilottiprimeministerp: sorry I was on the phone16:11
primeministerpalexpilotti: understood16:11
alexpilottiI'm going to follow up on the ML16:11
primeministerpalexpilotti: great16:11
alexpilottion the certificate auth16:11
primeministerpmtaylor: I need to follow up w/ you as well16:11
alexpilottias we need to figure auth how to handle teh certificates16:12
alexpilottiwhich IMO should be treated like the keypairs16:12
primeministerpalexpilotti: agreed16:12
*** Guest53164 is now known as antonym16:12
*** ryanpetrello has quit IRC16:12
primeministerpalexpilotti: ok then, i'm going to end the meeting16:12
primeministerpalexpilotti: we'll meet after the new year again16:13
alexpilottiok!16:13
primeministerp#endmeeting16:13
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:13
openstackMeeting ended Tue Dec 17 16:13:15 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:13
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-12-17-16.03.html16:13
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-12-17-16.03.txt16:13
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-12-17-16.03.log.html16:13
*** fnaval_ has joined #openstack-meeting16:13
*** akuznetsov has quit IRC16:13
*** rnirmal has quit IRC16:13
*** ryanpetrello has joined #openstack-meeting16:14
*** rnirmal has joined #openstack-meeting16:14
*** DennyZhang has joined #openstack-meeting16:14
*** HenryG has quit IRC16:14
*** fnaval has quit IRC16:14
*** HenryG has joined #openstack-meeting16:14
*** sacharya has joined #openstack-meeting16:16
*** markwash has joined #openstack-meeting16:16
*** ociuhandu has quit IRC16:16
*** garyk has quit IRC16:17
*** fnaval_ has quit IRC16:18
*** paragan has quit IRC16:21
*** mdomsch has quit IRC16:22
*** thomasbiege1 has joined #openstack-meeting16:23
*** DennyZhang has quit IRC16:24
*** ociuhandu has joined #openstack-meeting16:24
*** jecarey has joined #openstack-meeting16:24
*** DennyZhang has joined #openstack-meeting16:24
*** thomasbiege1 has quit IRC16:25
*** markmcclain has quit IRC16:26
*** thomasbiege has quit IRC16:26
*** jecarey_ has joined #openstack-meeting16:28
*** thomasbiege has joined #openstack-meeting16:28
*** jcooley_ has quit IRC16:30
*** jecarey has quit IRC16:31
*** luis_fdez has quit IRC16:31
*** DennyZhang has quit IRC16:33
*** doron_afk is now known as doron16:33
*** DennyZhang has joined #openstack-meeting16:33
*** ikhudoshyn has quit IRC16:33
*** MaxV has quit IRC16:34
*** ikhudoshyn has joined #openstack-meeting16:34
*** dolphm_afk has quit IRC16:35
*** herndon has joined #openstack-meeting16:35
*** ayoung has joined #openstack-meeting16:35
*** MaxV has joined #openstack-meeting16:37
*** Mandell has quit IRC16:37
*** adalbas has quit IRC16:41
*** fnaval has joined #openstack-meeting16:42
*** mrodden1 has quit IRC16:44
*** doron is now known as doron_afk16:44
*** hemna has joined #openstack-meeting16:45
*** bdperkin_gone has joined #openstack-meeting16:45
*** bdperkin_gone is now known as bdperkin16:45
*** bdperkin has quit IRC16:46
*** bdperkin has joined #openstack-meeting16:46
*** doron_afk has quit IRC16:48
*** yaguang has quit IRC16:53
*** rongze_ has quit IRC16:53
*** rongze has joined #openstack-meeting16:53
*** adalbas has joined #openstack-meeting16:54
*** SergeyLukjanov has joined #openstack-meeting16:54
*** egallen has quit IRC16:55
*** vijendar has quit IRC16:56
*** vijendar has joined #openstack-meeting16:56
*** esker has quit IRC16:57
*** afazekas has quit IRC16:59
*** msdubov has joined #openstack-meeting16:59
*** haomaiwang has quit IRC17:02
*** mrodden has joined #openstack-meeting17:02
*** haomaiwang has joined #openstack-meeting17:02
*** stevemar has quit IRC17:03
*** garyk has joined #openstack-meeting17:05
*** katyafervent has joined #openstack-meeting17:06
*** ayoung has quit IRC17:06
primeministerp#endmeeting17:06
*** DennyZhang has quit IRC17:07
*** Abhishek_ has joined #openstack-meeting17:07
*** haomaiwang has quit IRC17:07
*** jlibosva has quit IRC17:08
*** davidhadas has quit IRC17:09
*** reed has quit IRC17:09
boris-42#startmeeting rally17:10
openstackMeeting started Tue Dec 17 17:10:16 2013 UTC and is due to finish in 60 minutes.  The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot.17:10
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:10
*** openstack changes topic to " (Meeting topic: rally)"17:10
openstackThe meeting name has been set to 'rally'17:10
boris-42msdubov ping17:10
msdubovboris-42 hi17:10
boris-42jaypipes ping17:10
boris-42harlowja_away ping17:10
*** pablosan has joined #openstack-meeting17:11
*** Alexei_987 has joined #openstack-meeting17:11
boris-42Alexei_987 ping17:11
Alexei_987pong17:11
boris-42okay let's start17:12
*** redixin has joined #openstack-meeting17:12
boris-42#topic Benchmark periodic execution17:12
*** openstack changes topic to "Benchmark periodic execution (Meeting topic: rally)"17:12
jaypipeso/17:12
boris-42msdubov pls could you explain what you done and what is the goal and status17:12
*** sushil_ has quit IRC17:13
*** flaper87 is now known as flaper87|afk17:13
msdubovboris-42 Well the patch has been actually pending for review for quite a while, but I've rewritten it so that it now launches benchmark scenarios in separate threads and counts periods between two consecutive scenario STARTS, which is different from the previous implementation where the engine counted the period between the end of one scenario and the beginning of the next one17:14
*** kenhui has quit IRC17:14
*** jorisroovers has quit IRC17:14
msdubovBesides, threading allows the benchmark engine to be error-resistant17:14
msdubovso if one of the periodic launches fails, the work still continues17:15
boris-42msdubov could you share with url of patch?17:15
msdubovNow the patch has been tested on Servers.boot_and_delete()17:15
*** pablosan has quit IRC17:15
msdubovsure17:15
msdubovhttps://review.openstack.org/#/c/57628/17:15
boris-42msdubov did you try to set really small period?17:15
boris-42msdubov tol get a lot of threads ?17:15
*** saju_m has joined #openstack-meeting17:16
msdubovboris-42 Nope, I tested it with 30 seconds17:16
msdubovIs there a well-known boundary for the number of threads?17:16
Alexei_987^ unsigned int lol17:17
boris-42msdubov idk, but just try for example to run start_stop every 5 seconds17:17
*** thomasbiege has quit IRC17:17
boris-42msdubov 500times17:17
msdubovAlexei_987 in Python that shouldn't be a problem?17:17
msdubovboris-42 Ok thanks for the advice17:17
Alexei_987threads are OS dependent. anyway should be enough for us :)17:17
*** sushils has joined #openstack-meeting17:18
msdubovAlexei_987 Now I see17:18
boris-42redixin could you take a look at that patch also ^17:18
*** pablosan has joined #openstack-meeting17:18
msdubovboris-42 I think we could just increase the period programmatically to, say, 5 seconds, if it is set to 0.0001 for example17:18
*** ayoung has joined #openstack-meeting17:18
*** Shaan7 has quit IRC17:18
*** Shaan7 has joined #openstack-meeting17:18
boris-42msdubov okay17:18
msdubovto avoid such problems17:18
*** stevemar has joined #openstack-meeting17:19
boris-42#topic Stress tests17:19
*** openstack changes topic to "Stress tests (Meeting topic: rally)"17:19
boris-42#link https://blueprints.launchpad.net/rally/+spec/benchmark-stress-test-execution17:20
*** joel_c has left #openstack-meeting17:20
boris-42There is already blueprint about it17:20
msdubovThis is what I'm working on now17:20
*** gyee has joined #openstack-meeting17:20
boris-42So the idea is to simplify stress testing of OpenStack17:20
boris-42instead of writing each benchmark with specific "concurrency" we will have more compact record for this17:21
boris-42as in a description of BP17:21
*** ruhe has quit IRC17:21
boris-42msdubov are you going to finish it by the end of next week?17:21
msdubovboris-42 Yes17:22
boris-42msdubov okay nice17:22
boris-42msdubov so next time we will discuss it=)17:22
*** sushils has quit IRC17:22
boris-42#topic Fuel based deployer17:22
*** openstack changes topic to "Fuel based deployer (Meeting topic: rally)"17:22
boris-42redixin ping17:22
*** ruhe has joined #openstack-meeting17:22
boris-42redixin could you share with us about Fuel based deployer17:22
redixinthere is 2 patches17:22
redixinadd Fuel client https://review.openstack.org/#/c/59943/17:23
redixinadd Fuel engine https://review.openstack.org/#/c/61963/17:23
boris-42redixin does that work?17:23
boris-42=)17:23
redixinyep. with Fuel-4.0-dev17:23
*** sushils has joined #openstack-meeting17:24
redixinwhich isnt released yet17:24
boris-42redixin could you some details and limitations of Fuel deployer?17:24
boris-42redixin for example how long it takes to deploy 1 node OS17:24
boris-42redixin how long in takes to deploy multimode17:24
*** nermina has quit IRC17:24
redixinFuel is refusing to deploy 1 node OS. 2 nodes minimum17:25
redixinit takes about 30 min17:25
*** saju_m has quit IRC17:25
redixinthere is no limitations. only limitation is Fuel.17:25
boris-42redixin but we are not able to deploy OS from custom code?17:26
boris-42redixin I mean custom nova/cinder/..17:26
redixinyes. we can deploy with this provider only whay possible to do with Fuel itself17:27
*** ayoung has quit IRC17:27
boris-42redixin eh we will need to extend this17:27
redixinFuel can't do this, so FuelEngine also can't do that17:27
*** jswarren has joined #openstack-meeting17:27
redixinboris-42: indeed17:28
*** garyduan has quit IRC17:28
boris-42redixin so with Fuel Engine we are able to deploy on servers provided by any existing server provider multimode OpenStack installation in HA?17:28
redixinno17:28
*** ayoung has joined #openstack-meeting17:28
boris-42redixin so there are some limitation?17:28
boris-42limitations*17:28
redixinit can deploy on servers only provisioned by Fuel17:29
redixinI said only limitation is Fuel. We can only do things than can do Fuel itself17:29
redixinThis engine is just client for FuelWeb17:30
boris-42redixin but it is useless then, because developers don't have own baremetall servers17:30
redixinIt is not useless if they have17:30
boris-42redixin I thought that we are using only deploy part of FUEL17:30
boris-42redixin without provision17:30
redixinboris-42: not yet17:30
boris-42redixin what means "not yet"17:31
boris-42redixin it is the FUEL or our problem?17:31
*** DrBacchus has quit IRC17:31
redixinboris-42: theoretically Fuel api can do this, but I not tested it yet17:32
*** andreaf has joined #openstack-meeting17:32
boris-42redixin could you test it, because it is super interesting for developers17:33
boris-42redixin ?17:33
redixinboris-42: sure17:33
boris-42redixin thanks17:33
*** sayali has joined #openstack-meeting17:33
boris-42#topic Improvements in DevStack engine17:33
*** openstack changes topic to "Improvements in DevStack engine (Meeting topic: rally)"17:33
boris-42redixin I have couple of thoughts about current DevStack Engine17:34
boris-42redixin at this moment we are able to specify only the repository for devstack17:34
*** garyduan has joined #openstack-meeting17:34
boris-42redixin but it is extra useful to be able to specify something like take my NovaRepo and all others from current master17:35
boris-42redixin so you will be able to get clouds with your patches17:35
redixinboris-42: it is possible to build totally custom localrc17:35
redixinand in localrc we can specify NOVA_REPO17:35
boris-42redixin could you add tutorial/readme/samples about how to do it in rally17:36
boris-42redixin we should make it simpler & cleaner then now17:36
*** jpich has joined #openstack-meeting17:36
*** dolphm has joined #openstack-meeting17:36
*** Shaan7 has quit IRC17:37
*** ruhe has quit IRC17:37
boris-42redixin ok?17:37
redixinboris-42: it is already there AFAIR17:37
boris-42redixin where what how?17:37
boris-42redixin i see only samples/deployemnts/ directory17:38
redixinhttps://wiki.openstack.org/wiki/Rally/DeployEngines#Configuration_Example_217:38
boris-42redixin and there is nothing about custom Nova17:38
redixinsee NOVA_REPO in localrc17:38
*** marekd has joined #openstack-meeting17:38
boris-42redixin this should be in rally/doc/samples/deployments as well IMHO17:39
redixinboris-42: ok17:39
boris-42redixin okay it is nice that we have support of such functionallity17:39
boris-42redixin next topic17:39
*** rongze has quit IRC17:39
boris-42#topic OpenStack Server provider17:39
*** openstack changes topic to "OpenStack Server provider (Meeting topic: rally)"17:39
boris-42When I run e.g. DevStack Engine with OpenStack Server provider17:40
*** rongze has joined #openstack-meeting17:40
boris-42I saw that I don't have access to horizon17:41
boris-42neither via fixed neither via floating IP17:41
redixinboris-42: oh yes. it is caused by default access rules17:41
redixinonly port 22 is allowed by default17:41
*** d0ugal has quit IRC17:41
*** zoresvit has quit IRC17:41
*** MaxV has quit IRC17:41
boris-42redixin yep yep17:41
boris-42redixin so could we fix this? to make it work out of box?17:42
redixinboris-42: why dont you filed bug?17:42
boris-42redixin okay I will file it17:42
boris-42okay then next topic17:42
boris-42#topic Benchmarks for Keystone17:43
*** openstack changes topic to "Benchmarks for Keystone (Meeting topic: rally)"17:43
*** zoresvit has joined #openstack-meeting17:43
*** arnaud has joined #openstack-meeting17:43
*** arnaud__ has joined #openstack-meeting17:43
boris-42So there is a big interest in testing keystone performance with Rally17:43
*** jcooley_ has joined #openstack-meeting17:43
boris-42As we can see from this recent thread http://lists.openstack.org/pipermail/openstack/2013-December/003947.html17:44
*** hemna has quit IRC17:44
*** vkozhukalov has joined #openstack-meeting17:44
boris-42This wiki page https://blueprints.launchpad.net/rally/+spec/keystone-benchmark17:44
*** hemna has joined #openstack-meeting17:44
boris-42So it is reasonable to use for such things Rally17:44
boris-42instead of bash scripts17:44
boris-42So today we get new BP https://blueprints.launchpad.net/rally/+spec/keystone-benchmark17:45
*** atiwari has joined #openstack-meeting17:45
boris-42and I am working on INIT patches that will allow us to write benchmarks for keystone17:45
msdubovboris-42 You've probably posted a wrong link to wiki17:45
*** ygbo has quit IRC17:46
*** markwash has quit IRC17:46
boris-42msdubov this one https://wiki.openstack.org/wiki/KeystonePerformance17:46
boris-42so we should make a couple of thing to simplify this process17:46
boris-42Fix user_init methods17:47
boris-42Add admin_init mechanism17:47
*** dolphm has quit IRC17:47
*** sayali has left #openstack-meeting17:47
boris-42Add cleanups for keystone benchmarks (we should delete all created users/projects/...)17:47
msdubovboris-42 I'd suggest to leave init() methods named init(), not user_init()17:48
msdubovboris-42  Sad that we'll have to introduce additional cleanups17:48
msdubovThis will make everything more complex17:48
*** SumitNaiksatam has quit IRC17:48
boris-42msdubov I think that user_init() admin_init() will be much more simple for understaning17:48
boris-42msdubov we only need to improve generic cleanups17:48
*** reed has joined #openstack-meeting17:49
boris-42msdubov and add some rules about naming resources when we are testing keystone17:49
msdubovboris-42 We somehow now need to track created resources?17:49
boris-42msdubov like rally-keystone-<uuid>17:49
boris-42msdubov no I don't like idea of tracking created users17:49
msdubovboris-42 Ok just by using naming rules? That's an oprion17:49
*** zoresvit has quit IRC17:49
msdubov*option17:49
*** sarob has joined #openstack-meeting17:49
*** elo has joined #openstack-meeting17:49
boris-42msdubov yep and this hardcoded pattern will be in keystone utils17:49
boris-42msdubov so if you create keystone resources through it you don't have any problems17:50
boris-42with cleanups17:50
msdubovboris-42 I see17:50
boris-42msdubov so after this will be done we will be able to add keystone benchmarks17:50
boris-42okay seems enough for this topic17:50
boris-42#topic OpenStack Profiling17:51
*** openstack changes topic to "OpenStack Profiling (Meeting topic: rally)"17:51
*** sarob has quit IRC17:51
*** ndipanov has quit IRC17:51
boris-42Alexei_987 ping17:51
Alexei_987pong17:51
*** jcooley_ has quit IRC17:51
boris-42Alexei_987 could you share the latest thoughts and ideas about profiling17:51
*** sarob has joined #openstack-meeting17:51
Alexei_987well currently we have 2 patches: 1 in ceilometer and 1 in oslo waiting for review17:51
*** jcooley_ has joined #openstack-meeting17:51
Alexei_987meanwhile we are working on patches for clients and nova17:51
Alexei_987that add profiling capabilities17:52
boris-42Alexei_987 what about clients, when we could expect some patches?17:52
Alexei_987for clients we'll have to add something like an event framework17:52
boris-42Alexei_987 on review17:52
*** jlibosva has joined #openstack-meeting17:52
Alexei_987based on nova/hooks17:52
Alexei_987for this we'll move hooks nova -> olso -> clients17:53
*** radix_ has joined #openstack-meeting17:53
boris-42Alexei_987 so we should just move nova python clients hooks from it to oslo17:53
boris-42and then back17:53
Alexei_987yes17:53
boris-42to all clients17:53
boris-42Seems like not so super hard17:53
Alexei_987it's currently in progress17:53
boris-42So do we have already BP?17:53
boris-42could you share with link17:53
boris-42?17:53
Alexei_987I haven't created a BP for this yet17:53
*** rongze has quit IRC17:53
boris-42Alexei_987 okay pls could you creat it tomorrow at morning?17:54
*** rongze has joined #openstack-meeting17:54
Alexei_987ok17:54
boris-42Alexei_987 thanks17:54
Alexei_987and for nova I hope that you'll help me with proper patches architecture17:54
boris-42And also we have one more thing it is visualization of logs17:54
*** d0ugal has joined #openstack-meeting17:54
Alexei_987cause it requires some solution for dependency injection problem17:54
boris-42Alexei_987 ?17:55
Alexei_987tie all objects together :)17:55
*** d0ugal has quit IRC17:55
*** nermina has joined #openstack-meeting17:55
*** fabio_ has joined #openstack-meeting17:55
boris-42Alexei_987 objects?17:55
*** fabio_ is now known as fabiog17:55
Alexei_987profiler + client + other objects17:55
boris-42yep17:55
*** markmcclain has joined #openstack-meeting17:55
boris-42it is not simple task17:55
*** sarob has quit IRC17:55
boris-42So here is the part of Rally17:56
boris-42http://pavlovic.me/drawer.html17:56
boris-42visualisation17:56
*** tanisdl_ has joined #openstack-meeting17:56
*** jcooley_ has quit IRC17:56
boris-42I think during this week I will finish work around integrating it into Rally17:56
*** tanisdl has quit IRC17:56
*** tanisdl_ is now known as tanisdl17:56
boris-42So we will need only patches in clients17:56
boris-42patches for 2 core projects17:56
boris-42e.g. nova/glacne17:56
boris-42to show the demo17:56
boris-42Alexei_987 yep?17:56
*** nati_ueno has joined #openstack-meeting17:56
Alexei_987even 1 project should be enough for start17:57
Alexei_987glance is not required I guess :)17:57
boris-42Alexei_987 we need 217:57
*** elo has quit IRC17:57
Alexei_987ok17:57
boris-42Alexei_987 to show that cross projects requests works17:57
boris-42Alexei_987 not only cross nova services.17:57
*** stanlagun has joined #openstack-meeting17:57
Alexei_987well we'll be able to show it to display cross request rally -> nova17:57
*** d0ugal has joined #openstack-meeting17:58
*** d0ugal has joined #openstack-meeting17:58
boris-42Alexei_987 it is not enough for public=)17:58
boris-42okay seems like times come to the end17:58
*** ihrachyshka has joined #openstack-meeting17:58
boris-42#topic free discussions17:58
*** openstack changes topic to "free discussions (Meeting topic: rally)"17:58
*** d0ugal has joined #openstack-meeting17:58
*** d0ugal has joined #openstack-meeting17:58
boris-42Any questions/thougths?17:58
*** derekh has quit IRC17:58
*** safchain has quit IRC17:58
*** d0ugal has joined #openstack-meeting17:59
*** d0ugal has joined #openstack-meeting17:59
*** ihrachyska has quit IRC17:59
*** dolphm_afk has joined #openstack-meeting17:59
*** shardy has joined #openstack-meeting17:59
boris-42Ok if somebody have any questions just ask it in  #openstack-rally channel17:59
boris-42#endmeeting17:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:59
openstackMeeting ended Tue Dec 17 17:59:53 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2013/rally.2013-12-17-17.10.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2013/rally.2013-12-17-17.10.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2013/rally.2013-12-17-17.10.log.html17:59
morganfainbergo/18:00
dolphm_afko/18:00
*** dstanek has joined #openstack-meeting18:00
fabiogo/18:00
*** dolphm_afk is now known as dolphm18:00
*** zz_ajo is now known as ajo18:00
fabiogI guess this is the last meeting of the year ...18:01
dolphmayoung: gyee: bknudson: stevemar: o/18:01
lbragstadhey18:01
stevemaro/18:01
dolphmfabiog: ++18:01
ayoungw00t18:01
shardyo/18:01
marekdhi18:01
dolphmshardy: o/18:01
dstanekhi18:01
bknudsonhi18:01
ayoungmorganfainberg,18:01
gyee\o18:01
morganfainbergOMG MEEEETING TIME18:01
*** jecarey_ has quit IRC18:01
dolphm#startmeeting keystone18:01
openstackMeeting started Tue Dec 17 18:01:49 2013 UTC and is due to finish in 60 minutes.  The chair is dolphm. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: keystone)"18:01
openstackThe meeting name has been set to 'keystone'18:01
dolphm#topic Reminder: Hackathon January 15-17th @ Rackspace in San Antonio, TX18:01
*** openstack changes topic to "Reminder: Hackathon January 15-17th @ Rackspace in San Antonio, TX (Meeting topic: keystone)"18:02
*** nachi has joined #openstack-meeting18:02
dolphmfeel free to book flights :) sounds like a couple have already been done18:02
*** nati_uen_ has joined #openstack-meeting18:02
morganfainbergooh, on vacation starting next week.  (read: snowboarding trip!)18:02
*** Alexei_987 has left #openstack-meeting18:02
dolphmi'm curious if anyone has gotten a hotel in SA yet18:02
dolphmmorganfainberg: be careful! :P18:02
*** thomasbiege has joined #openstack-meeting18:02
topoldolphm, fly in the night before make the most sense?18:02
gyeedolphm, I'll know my status by end of the week18:02
dstanekdolphm: i have not, but i'm planning on just staying at the courtyard18:02
dolphmtopol: that's what i would do personally18:03
ayoungYeah there was one hotel walking distance to the office that seemed to make sense18:03
topoldolphm, stevemar and I are a GO!  Contingent on you giving us a personal tour of the Alamo18:03
*** jamielennox has joined #openstack-meeting18:03
topoldolphm, we will come in the night before18:03
dolphmtopol: i shall personally point you to it on a map18:03
morganfainbergi have not booked hotel, but courtyard seems like the best choice18:03
*** stanlagun has left #openstack-meeting18:04
dolphmvalencia is damned nice and downtown if you're into that, courtyard has free transport18:04
*** ociuhandu has quit IRC18:04
dolphmso, pick your poison18:04
topolcan we all pick the same hotel? Are we going with the courtyard?18:04
*** nati_uen_ has quit IRC18:04
morganfainbergdolphm, i'm leaning towards free transport since i'm still wokring on details to see if i am paying for this out of my own pocket18:04
dolphmtopol: courtyard is definitely the easier & slightly cheaper option18:04
*** nati_uen_ has joined #openstack-meeting18:04
morganfainbergdolphm, so les $ is my goal.18:05
topolmorganfainberg I'll have a car18:05
stevemarcheaper is good18:05
*** nati_uen_ has quit IRC18:05
dstaneki would be up for either - the only thing i don't like about the Valencia is that i'll need a car and you have to valet it18:05
dolphm#link https://gist.github.com/dolph/5cfa70c02f5b141060c518:05
morganfainbergdstanek, ++18:05
topolLet's agree on courtyard18:05
*** d0ugal has joined #openstack-meeting18:05
*** d0ugal has quit IRC18:05
*** d0ugal has joined #openstack-meeting18:05
*** nati_ueno has quit IRC18:05
*** nati_uen_ has joined #openstack-meeting18:05
*** ociuhandu has joined #openstack-meeting18:06
*** sushils has quit IRC18:06
morganfainbergtopol, sounds good to me.18:06
dstaneki'll be booking my travel tonight18:06
dolphmtopol: noted on the gist18:06
*** d0ugal has quit IRC18:06
*** weshay has quit IRC18:06
stevemarany international guests? henrynash or jamielennox ?18:07
dolphmif anyone has trouble booking at the discounted rate, chase me down18:07
*** d0ugal has joined #openstack-meeting18:07
*** d0ugal has joined #openstack-meeting18:07
topoldolphm, excellent18:07
dolphmi'm told there's not a group code, and that you have to call18:07
jamielennoxstevemar: a little hard to justify for a hackathon18:07
*** d0ugal has quit IRC18:07
ayoungany reason not to take the Pear Tree hotel?  Easy walk to the office18:07
*** brich has joined #openstack-meeting18:07
ayoung$80 / night18:07
dolphmjamielennox: frankly i wouldn't make the trip unless you're planning on staying longer than 3 days lol18:07
morganfainbergjamielennox, you know you want to hop on a ~19hr flight :P18:07
morganfainbergfor 3 days18:08
dolphmayoung: i'm not familiar with it18:08
*** jcooley_ has joined #openstack-meeting18:08
ayounghttps://plus.google.com/104227517689615970183/about?gl=us&hl=en18:08
jamielennoxdolphm:, morganfainberg: would end up just sleeping through the whole thing18:08
morganfainbergjamielennox, i hear ya man.18:09
ayoung 0.5 mi, 9 mins18:09
ayoungInterstate 35 Frontage Rd/NE18:09
*** d0ugal has joined #openstack-meeting18:09
morganfainbergayoung, either that or the shuttle from the courtyard, both seem reasonable and in the same-class of price18:09
morganfainbergfor the most part18:09
bknudsondolphm: it's next to the red lobster18:09
bknudsonby the home depot18:10
ayoungI hate waiting on shuttles.  We're coders...and I won;t have the kids to keep me on a regular schedule18:10
*** d0ugal has joined #openstack-meeting18:10
*** d0ugal has joined #openstack-meeting18:10
bknudsonwhat's Shoney's?18:10
ayoungSo we won't go hungry18:11
*** d0ugal has joined #openstack-meeting18:11
*** d0ugal has joined #openstack-meeting18:11
dolphmayoung: as i understand it, the shuttles have a regular schedule (they run 3 times a day each way) you just need to give the front desk a heads up that you'd like to be on it18:11
dolphmbknudson: a chain diner18:11
ayoungMarie Callendars18:11
*** d0ugal has joined #openstack-meeting18:11
*** d0ugal has joined #openstack-meeting18:11
dolphmthere's food within walking distance of rax, and we have vendors in house every day18:11
stevemartopol and i should have rentals - i think?18:11
*** d0ugal has joined #openstack-meeting18:12
*** d0ugal has joined #openstack-meeting18:12
topolyes we will!!!18:12
stevemarwe could car pool18:12
morganfainbergworks for me18:12
ayoungIs there any reason not to go to the PearTree?18:12
*** d0ugal has joined #openstack-meeting18:12
*** d0ugal has joined #openstack-meeting18:12
*** d0ugal has quit IRC18:12
*** markwash has joined #openstack-meeting18:13
topolIm fine with either. I need to check what options pop up in our hotel reservation tool. will do that now18:13
*** davidhadas has joined #openstack-meeting18:13
morganfainbergayoung, i think it is all personal preferance at this point18:13
ayoungIt would be good to all be at the same hotel18:13
ayoungmakes Logisitics easier18:13
*** jcooley_ has quit IRC18:13
stevemartopol, nothing pops up :(18:13
*** d0ugal has joined #openstack-meeting18:13
*** d0ugal has joined #openstack-meeting18:13
morganfainbergayoung, nod18:14
ayoungLink to the Courtyard?18:14
bknudsonmordred road. that's weird.18:14
dstanekayoung: i have heard that it's not a great hotel18:15
*** nkinder has joined #openstack-meeting18:15
topolwhats rackspace's address18:15
stevemarRackspace Hosting, 1 Fanatical Place, Windcrest18:15
stevemartopol ^18:15
stevemarpostal code 7821818:15
ayoung"1803 E Sonterra Blvd, San Antonio, TX 78259"  That Courtyard?18:16
dolphmstevemar: or 5000 Walzem Rd. (Fanatical Place was just built & named)18:16
dolphmayoung: definitely not18:16
*** jkyle_ is now known as jkyle18:16
dolphmayoung: that's near my house though lol18:16
dolphmayoung: http://www.marriott.com/hotels/travel/satca-courtyard-san-antonio-airport/18:16
ayoungso I could get a ride in18:16
*** jkyle is now known as Guest7516918:16
dolphmayoung: 8615 Broadway Street  San Antonio  Texas  78217  USA18:17
dolphmayoung: there's a damn good coffee shop right there...18:17
dstanekhttp://www.marriott.com/hotels/travel/satca-courtyard-san-antonio-airport/18:17
dolphmayoung: (on Sonterra Blvd)18:17
ayoungAfter the Summit I am sick of Airports....18:17
*** dhellmann is now known as dhellmann_18:17
topolstevemar, we can get an exception18:17
ayoungNever even made it past Kowloon18:17
dolphmayoung: lol18:17
*** jtomasek has quit IRC18:17
ayoungIs the courtyard the Hotel of choice then?  That alone is reason to book it18:18
topol99$ courtyard is within budget18:18
dolphmayoung: sounds like it18:18
*** rongze has quit IRC18:18
stevemartopol, i figured that, just never had the need to18:18
dolphmayoung: there are a couple definites for courtyard18:18
*** Guest75169 has quit IRC18:18
*** coolsvap has quit IRC18:18
dolphm#topic Next Keystone meeting: January 7th18:19
*** openstack changes topic to "Next Keystone meeting: January 7th (Meeting topic: keystone)"18:19
ayoung 6.2 mi, 2 hours 5 mins18:19
ayoungNE Interstate 410 Loop  That estimate seems long18:19
ayoungah, still set for walking18:19
dolphmanyone is welcome to use this time slot and have a meeting if you want, but i'll be AFK for most of the next two weeks18:19
topolAny hotels with a bedbug special???18:19
*** msdubov has left #openstack-meeting18:19
dolphmayoung: walking is slow in texas18:19
*** weshay has joined #openstack-meeting18:19
ayoungBiking route looks cool,18:19
ayoung7.8 ,moiles, 48 minutes, WTF?18:20
*** rfolco has quit IRC18:20
bknudsonit's hot there and people move slowly18:21
dolphmbknudson: ++18:21
ayoungDo they estimate based on a tricycle?18:21
dolphmcars ftw18:21
*** d0ugal has joined #openstack-meeting18:21
*** d0ugal has joined #openstack-meeting18:21
ayoungMy experience in TExas in January was that it is not hot....very not hot.18:21
*** rfolco has joined #openstack-meeting18:21
dolphmyeah, it'll be really nice18:21
*** SumitNaiksatam has joined #openstack-meeting18:21
morganfainbergdolphm, s/cars/cats <xkcd plugin />18:21
dolphmin the 55-70 F range at the moment18:21
dolphmmorganfainberg: lol18:22
*** d0ugal has joined #openstack-meeting18:22
*** d0ugal has joined #openstack-meeting18:22
* ayoung watches the snow fall outside18:22
dolphmk, let's move on to actually important things18:22
*** harlowja_away is now known as harlowja18:22
dolphmit's almost marekd's bed time18:22
topolstevemar, courtyard at the airport has an IBM negotiated rate. Is thatw here everyone is staying?18:22
dolphm#topic Leveraging mod_shib / mod_mellon to handle interaction with federated identity providers18:22
*** openstack changes topic to "Leveraging mod_shib / mod_mellon to handle interaction with federated identity providers (Meeting topic: keystone)"18:22
dolphmmarekd: o/18:22
marekddolphm: \o18:22
marekdstill awake18:23
dolphmtopol: yes18:23
ayoungmod_auth_mellon...I'll find the linlk18:23
dolphm#link https://code.google.com/p/modmellon/18:23
*** d0ugal has joined #openstack-meeting18:23
*** d0ugal has joined #openstack-meeting18:23
ayounganyone tried it out yet?  I know people in our IdM team have, but not me myself.18:24
marekdme, but not mod_mellon.18:24
marekdmod_shib.18:24
morganfainbergayoung, i haven't had a chance to yet.18:24
stevemarayoung, marekd tried it out: https://gist.github.com/zaccone/914822d37ac2eea420ce18:24
dolphmmod_mellon seems to be pretty well packaged (debian, centos, rhel)18:24
stevemarwe get a whole whack of stuff back18:24
*** davidhadas_ has joined #openstack-meeting18:24
bknudsonto use saml you need to run in apache?18:25
marekdyes.18:25
*** d0ugal has joined #openstack-meeting18:25
*** d0ugal has quit IRC18:25
*** d0ugal has joined #openstack-meeting18:25
ayoung#link reference http://www.explainxkcd.com/wiki/index.php/1218:_Doors_of_Durin18:25
dolphmbknudson: ++18:25
marekdanother this is: is relies on static config files18:25
marekdmod_mellon for 100% - asked on their mailing list.18:25
*** thomasbiege has quit IRC18:25
*** d0ugal has joined #openstack-meeting18:26
*** d0ugal has joined #openstack-meeting18:26
marekd(completely reasonable)18:26
*** vipul is now known as vipul-away18:26
dolphmbknudson: i'd rather not re-invent the wheel in the next few weeks, but we could implement the same in middleware eventually18:26
marekddolphm: ++18:26
dolphmmarekd: mod_mellon relies on static config?18:26
marekddolphm: yes.18:27
dolphmmarekd: does that imply that mod_shib doesn't?18:27
marekddolphm: mod_shib uses files too...18:27
marekdi just said i am 100% about mod_mellon, because I asked it's authors.18:27
bknudsonI assume that keystone is going to have to support more than just REMOTE_USER then?18:28
marekdhowever i have never seen any plugin for mod_shib + SQL/something.18:28
*** davidhadas has quit IRC18:28
dolphmmod_mellon is GNU GPL v218:28
*** d0ugal has joined #openstack-meeting18:28
*** d0ugal has joined #openstack-meeting18:28
*** d0ugal has quit IRC18:28
dolphmbknudson: ++, the federation middleware will have to read headers from the apache module18:28
ayoungbknudson, they should come through as additional env vars18:28
dolphmbknudson: see stevemar's link to marekd's example18:28
marekdbknudson: modules would do the job.18:28
*** blamar has quit IRC18:29
marekdbknudson: keystone would get set of parsed attributes.18:29
*** d0ugal has joined #openstack-meeting18:29
*** d0ugal has quit IRC18:29
marekdwhich is great, as I personally find SAML not very 'clean' atribute and would rather not write soft for parsing those all XMLs :-)18:29
topolGNU GPL v2.  Isnt that like buying a hot rolex?  A big no no?18:29
marekdtopol: why?18:30
bknudsonis it the ADFS_* attrs are the assertions?18:30
marekdyes18:30
marekdbknudson: ^18:30
dolphmtopol: considering the nature of our dependency on it, i don't know how much we need to care? worth asking the list18:30
dolphmbknudson: ++18:30
marekdand as a matter of fact YOU configure in the mod_ how to make a initial mapping.18:30
marekd#link https://gist.github.com/zaccone/021203cab26c9e4b0baf18:31
marekdhere is the code, that produced the output for my SP18:31
marekd(mod_shib)18:31
marekdbut mod_mellon would work pretty much the same way.18:31
ayoungreference link http://www.freeipa.org/page/Environment_Variables18:31
dolphmtopol: i'm looking for the license to mod_shib... can't find much18:31
ayoungSAML not yet made it in there, though18:31
fabiogtopol, I think it is complicated to re-package that code, you need to use the same licensing model18:32
*** d0ugal has joined #openstack-meeting18:32
ayounghttp://code.google.com/p/modmellon/wiki/GenericSetup#Retrieving_attributes_from_mod_mellon18:32
topolfabiog exactly18:33
dolphmfabiog: i believe it's okay for us to support it, as long as we don't have a hard dependency on it18:33
*** MaxV has joined #openstack-meeting18:33
marekdanyway, using mod_* implies static configuration. dolph said it should be generated manually, one day we could add some code -> keystone would generate config based on the data stored in it's backend.18:33
fabiogdolphm, we need to be careful, because even re-distributing it could be an issue outside GPL18:33
dolphmfabiog: +++18:33
topolfabiog exactly +++18:34
morganfainbergwhy can't everyone use ASLv2 these days18:34
*** ArthurBerezin has joined #openstack-meeting18:34
*** ArthurBerezin has left #openstack-meeting18:34
bknudsonso keystone would provide a way to map ADFS_* to roles?18:34
topolmorganfainberg, preaching to the choir!18:34
marekdyes, mapping.18:34
bknudsonand that's going to be some middleware?18:34
marekdbknudson: ^^18:34
*** DrBacchus has joined #openstack-meeting18:34
*** d0ugal has joined #openstack-meeting18:34
*** d0ugal has joined #openstack-meeting18:34
bknudsonis the config in a config file or in keystone db?18:34
ayoungASL?  American Sign Language?  Didn';t realize there was an updated version18:34
fabiogmorganfainberg, I think MIT License is also goo18:34
fabioggood18:34
marekdbknudson: what config?18:35
morganfainbergfabiog, prefer apache myself18:35
topolayoung, out in left field again :-)18:35
bknudsonor do we have something that translates ADFS_* to some keystone structure18:35
topolfabiog, we must have the same lawyers :-)18:35
marekdbknudson: mapping attributes, completely internal stuff, right stevemar ?18:35
dolphmbknudson: config for mod_mellon / mod_shib should be deployer-handled in icehouse18:35
ayoungAre we OK with mod_mellon as a starting point?  Not a hard dep, but a way to get things moving?  Put it to avote?18:35
marekddolphm: ++18:36
fabiogtopol, in reality lawyers are all the same ;-)18:36
dolphmbknudson: config for how keystone handles assertions is basically in SQL for us, as we're exposing it to the API18:36
*** vkozhukalov has quit IRC18:36
dolphmayoung: i'd like to answer that today, but can you find a license for mod_shib ?18:36
bknudsonI'm fine going with an apache/external auth method.18:37
topoldolphm, I think you should ask if any concerns on the dev list or the OpenStack gods18:37
jamielennoxis there a pros/cons for mellon vs shib? i've at least heard of mellon and i'm pretty sure it's packaged18:37
marekddolphm: one thing, not sure if it's relevant: mod_mellon is a pure apache module18:37
dolphmtopol: ++18:37
*** vkozhukalov has joined #openstack-meeting18:37
dolphmjamielennox: it's packaged18:37
bknudsonlooks like it will be a lot of work to reimplement all that ourselves.18:37
ayoungdolphm, I can., but I think we've found mellon is much more in line with what we are looking for.   Let me see18:38
marekddolphm: whereas shibboleth works slightly different: there is a standalone daemon, that does it's work, accessible on unix sockets or tcp, mod_shib actually is a frontend and communicates with shibd daemon18:38
jamielennoxi think the external approach is good, one mod vs the other is just selecting the better i think18:38
dolphmayoung: good to hear18:38
dolphmbknudson: ++18:38
*** Abhishek_ has quit IRC18:38
marekddolphm: on the other hand, i didn't find info about protocol for communicating between peers....18:38
*** d0ugal has joined #openstack-meeting18:38
*** d0ugal has joined #openstack-meeting18:38
ayounghttp://en.wikipedia.org/wiki/Shibboleth_%28Internet2%29#Development18:39
*** d0ugal has joined #openstack-meeting18:39
marekdguys, how determined are you to decide today?18:39
bknudsonsince there's potentially multiple providers, I think it makes sense to translate whatever they give us (ADFS_* attrs or whatever) to a keystone structure that keystone uses.18:39
*** blamar has joined #openstack-meeting18:39
topolayoung, yay that one is Apache 2 License18:40
dolphmmarekd: i'd like to know about blockers on one other the other today18:40
dolphmso it's GPL w/ easy deployments vs Apache 2 w/ complicated deployment18:40
*** d0ugal has joined #openstack-meeting18:40
*** d0ugal has joined #openstack-meeting18:40
marekddolphm: IdP discovery. i am not sure it's stararized and whether both modules will work in the same way...18:40
marekdhttps://wiki.shibboleth.net/confluence/display/SHIB2/IdPDiscovery18:41
*** d0ugal has joined #openstack-meeting18:41
*** d0ugal has joined #openstack-meeting18:41
marekdthis is for shibboleth (grep for From a Known Home)18:41
marekdhowever i couldn't make it work or my shib :P18:41
*** d0ugal has joined #openstack-meeting18:41
*** d0ugal has joined #openstack-meeting18:41
dolphmlol18:41
jamielennoxbknudson: ++ keep the provider specific interface to a minimum18:41
topolmarekd that joke went over my head18:42
ayoungThe Shibboleth License, Version 1.18:42
ayoung * Copyright (c) 200218:42
ayoung * University Corporation for Advanced Internet Development, Inc.18:42
ayoung * All rights reserved18:42
*** alexpilotti has quit IRC18:42
marekdtopol: hm?18:42
*** jcoufal has joined #openstack-meeting18:42
dolphmbknudson: sure, and you could probably abstract away the difference between _shib and _mellon eventually18:42
dolphmayoung: wtf lol18:42
ayoungdolphm, looking for a short link18:43
ayoungbut that was dated 200218:43
*** oubiwann has joined #openstack-meeting18:43
ayoungMIT cached version18:43
*** d0ugal has joined #openstack-meeting18:43
*** d0ugal has joined #openstack-meeting18:43
marekdth other thing i am worried veryy much is the client side.18:43
marekdwherever you google for SAML the use-case is a browser one.18:43
*** d0ugal has joined #openstack-meeting18:43
*** d0ugal has joined #openstack-meeting18:43
marekd'a client uses his WEB BROWSER and logs in'18:44
bknudsonwe're not going to have a library for python-keystoneclient to use?18:44
marekdbknudson: keystoneclient will be a big part in federation authn18:44
*** sarob has joined #openstack-meeting18:44
marekdhttps://developers.google.com/google-apps/sso/saml_workflow_vertical.gif18:44
*** jcooley_ has joined #openstack-meeting18:44
*** jcooley_ has quit IRC18:44
marekdbknudson: if that was your question :P18:45
dolphmbknudson: keystoneclient can't pretend to know how to auth with all existing IdP's though18:45
ayounghttps://github.com/sonian/shibboleth-sp2/blob/master/apache/mod_shib_20.cpp18:45
*** jcooley_ has joined #openstack-meeting18:45
*** d0ugal has joined #openstack-meeting18:45
bknudsonkeystone isn't going to provide saml assertions, only accept them18:45
marekdbknudson: correct.18:45
dolphmbknudson: correct18:46
*** jcooley_ has quit IRC18:46
jamielennoxmarekd: what are you expecting the client to have to do extra?18:46
bknudsonthat's like step 8 of https://developers.google.com/google-apps/sso/saml_workflow_vertical.gif18:46
*** jcooley_ has joined #openstack-meeting18:46
jamielennoxoh right, i know what you mean18:46
bknudsonit's like you need a token from idp to get a token form keystone18:46
*** d0ugal has joined #openstack-meeting18:46
*** d0ugal has joined #openstack-meeting18:46
marekdjamielennox: keep the session, handle HTTP redirects.18:46
*** vipul-away is now known as vipul18:46
marekdjamielennox: that's for sure.18:46
dolphmbknudson: ++18:46
dolphmbknudson: that's exactly how it works (SAML being the token)18:47
*** d0ugal has joined #openstack-meeting18:47
*** d0ugal has joined #openstack-meeting18:47
marekddolphm: to me SAML likes like a web-browser only protocol, seriously :(18:47
morganfainbergso we're using the standard SAML workflow instead of the EC or Proxy method?18:47
jamielennoxmarekd:  session and redirects are fine, i'm not sure if we can handle pointing keystoneclient at any random idp provider though18:47
bknudsonthe client need to get the "encoded SAML response" (step 6) and send it to keystone server18:47
morganfainbergsimply because EC / Proxy doesn't require redirects18:47
ayoungSo..before we run out of time...I'd like to suggest we discuss https://blueprints.launchpad.net/python-keystoneclient/+spec/endpoint-versioning18:47
dolphmmorganfainberg: ooh, what are the other two methods...18:47
marekdjamielennox: willing to talk after the meeting?18:47
jamielennoxmarekd: sure18:47
morganfainbergdolphm, Enhanced client and proxy.  but the details i've drummed up are light so far18:48
morganfainberglet me see if i can find that diagram18:48
bknudsonjamielennox: maybe if we had idp plugins in the client ?18:48
jamielennoxactually auth plugins will fix a lot of this anyway18:48
dolphmayoung: we've talked about that elsewhere, extensively18:48
*** rakhmerov1 has quit IRC18:48
marekdmorganfainberg: SP and IdP doen't require direct communication, it's client who transport requests/responses.18:48
morganfainbergmarekd, ah. i see.18:49
*** garyk has quit IRC18:49
*** d0ugal has joined #openstack-meeting18:49
*** garyk has joined #openstack-meeting18:49
ayoungdolphm, then it is OK if I go ahead an implement>18:49
*** rbowen has joined #openstack-meeting18:49
ayoung?18:49
marekdmorganfainberg: that's why keystoneclient will play a big role gere.18:49
*** d0ugal has quit IRC18:49
*** d0ugal has joined #openstack-meeting18:49
marekds/gere/here18:49
morganfainbergmarekd, that is standard, i think it's doable with EC or proxy though where SP -> idp is in direct communication18:49
morganfainbergmarekd, like i said, the info on EC / Proxy methods with saml seemed very light18:50
*** DrBacchus has quit IRC18:50
marekdmorganfainberg: standard direct communication between SP<->IdP?18:50
morganfainbergso might not be really usable.18:50
atiwarimarekd, direct communication will be needed for artifact profile18:50
dolphmayoung: no18:50
*** johnthetubaguy1 has quit IRC18:50
marekdatiwari: can you say more?18:50
atiwariwhen SP wants to pull the SAML from IdP18:50
*** jcooley_ has quit IRC18:50
dolphmayoung: absolutely not -- all the prior art and design direction directly conflicts with everything this blueprint describes18:50
ayoungdolphm, nope18:50
morganfainbergmarekd, http://appliedlife.blogspot.com/2007/06/saml-enhanced-client-or-proxy.html18:51
dolphmayoung: search on the mailing list for discovery18:51
*** d0ugal has quit IRC18:51
ayoungdolphm, so long as we don;t lock ourselves into requiring version, we should be OK18:51
*** jcooley_ has joined #openstack-meeting18:51
ayoungdolphm, without it, we are stuck on v218:51
atiwariIn the SAML artifact profile, artifact will not be provided to SP initially18:51
marekdatiwari: any links, docs for that? I never heard of that.18:51
atiwariartifact +> assertion18:51
*** MaxV has quit IRC18:51
ayoungdolphm, people are writing scripts etc and its all based around the current endpoints coming back from the Service Catalog18:51
*** pvaneck has joined #openstack-meeting18:52
dolphmayoung: which is a terribly broken approach that we need to rectify and not further18:52
ayoungwe just need to A)  work around it until the v2 is deprecated B) do discovery, and C) stop telling people to put versions on their endpoints18:52
shardyayoung: IMO all the client libs should be able to do version negotiation via an unversioned endpoint18:52
*** MaxV has joined #openstack-meeting18:52
dolphmayoung: the reason everyone else is writing broken code is because we've failed to set the example18:52
ayoungbut we need the workaround18:52
*** d0ugal has joined #openstack-meeting18:52
dolphmshardy: ++18:52
ayoungshardy, eys, but people can't change the endpoints that are in the SC18:52
atiwarimarekd, link: http://en.wikipedia.org/wiki/SAML_2.0#HTTP_Artifact_Binding but it is for the future18:52
ayoungI agree with all of this18:52
dolphmayoung: this is not a matter of deprecating v218:52
*** johnthetubaguy has joined #openstack-meeting18:53
ayoungbut still insist that we need a wrokaround or we are stuck18:53
atiwarimay be we can avoid it for now18:53
*** rpodolyaka1 has joined #openstack-meeting18:53
morganfainbergmarekd, dolphm, though it looks like ECP might preclude using the apache mod18:53
ayoungwreakaround?18:53
ayoungreakhavocaround18:53
*** docaedo has quit IRC18:53
*** greghill has joined #openstack-meeting18:53
bknudsonso identity providers have a standard for authenticating? (SAML SOAP binding?)18:53
ayounganyway, we need to assume that endpoints come back saying V2.0 at the end, or old clients are going to break18:53
fabiogdolphm, less than 10 min left ...18:53
*** MaxV has quit IRC18:53
*** nati_ueno has joined #openstack-meeting18:53
*** d0ugal has quit IRC18:54
*** d0ugal has joined #openstack-meeting18:54
ayoungcan we just be pragmatic here, so long as we avoid the pitfalls of the past?18:54
bknudsonfrom http://3.bp.blogspot.com/_Hu8FwD79TOo/RoK5RmNAebI/AAAAAAAAAA4/trnodJ9iZ9s/s1600-h/ecp-diagram.jpg18:54
dolphmayoung: you're proposing we regurgitate all the pitfalls of the past18:54
marekdmorganfainberg: to be honest, the more i read about saml, the more i ask aroung, the more i am convinced everybody has his standard :(18:54
*** MaxV has joined #openstack-meeting18:54
dolphmfabiog: not sure we're going to have time to discuss notifications, other than direct people to it18:54
*** SlickNik has joined #openstack-meeting18:54
marekdbknudson: i dont see direct arrows between SP & IdP.18:55
*** jeckersb is now known as jeckersb_gone18:55
morganfainbergmarekd, the arrow crosses the SP, SP is the Proxy via SOAP bindings18:55
jamielennoxfabiog: i like the idea - not every extension can be implemented purely in a pipeline18:55
dolphmbknudson: SP never talks to IdP directly18:55
morganfainbergand directs the request to the known IdP18:55
dolphmbknudson: afaik18:55
marekddolphm: ++18:55
*** jcooley_ has quit IRC18:55
morganfainbergin that diagram18:55
*** spzala has quit IRC18:56
morganfainbergwell, ECP being the "smart" proxy18:56
atiwaridolph, "SP never talks to IdP directly" is not correct18:56
fabiogjamielennox: and  currently the data is not in sync if there are any dependencies18:56
dolphmatiwari: feel free to correct me with an example18:56
marekdmorganfainberg: directs the requests mean directs the client to go there, right?18:56
jamielennoxfabiog: there are a bunch of extensions that i think will need to simply run and that shouldn't have a middleware component - is this how the other projects do it though?18:56
morganfainbergmarekd, as far as i can tell, yes18:56
jamielennoxnova must have this problem18:56
*** Mandell has joined #openstack-meeting18:56
atiwaribut yes not in post profile , it is correct18:56
marekdmorganfainberg: because i was referring to a direct TCP connection between IdP and SP18:56
morganfainberghttp://docs.oasis-open.org/security/saml/v2.0/saml-profiles-2.0-os.pdf 4.2.118:56
ayoungdolphm, no, I am proposing we ignore the versions on the URLs18:56
marekdmorganfainberg: and then i say : never heard about that (TCP conns)18:57
*** nati_uen_ has quit IRC18:57
morganfainbergerm 4.218:57
*** ociuhandu has left #openstack-meeting18:57
dolphmayoung: i got that much; don't do that18:57
ayoungwe need to do at least that in order to get v2 and v3 interop18:57
ayoungdolphm, we have to.18:57
fabiogjamielennox: this is only for registered Keystone extensions, if you want a generic notification you can re-use the rabbitmq model18:57
morganfainbergmarekd, i think this is super complex :P18:57
ayoungThis is the corner we;ve been painted into18:57
*** jeckersb_gone is now known as jeckersb18:57
ayoungversions in the URLS are stupid, I agree18:58
fabiogjamielennox: but for the extensions that are interested only in Keystone this will be very efficient and simple (I think)18:58
jamielennoxfabiog: yea i get that, i was just thinking that nova v3 is based around an extensions model and they must be doing notification like this18:58
bknudsonis PAOS the opposite of SOAP?18:58
ayoungand this is not something we can be a purist about, or we will not be able to get rid of them18:58
marekdmorganfainberg: i think this is overkill, seriously. i think i must check whether mod_shib, mod_mellon has ECP implemented.18:58
marekdbknudson: yes.18:58
marekdbknudson: whatever it means...18:58
dolphmayoung: we put ourselves here; version discovery in the clients will push deployers to revise their catalogs18:58
morganfainbergbknudson, lol18:58
*** MaxV has quit IRC18:58
morganfainbergbknudson, i never noticed that.18:58
marekdmorganfainberg: he is right :)18:58
morganfainbergmarekd, i know.18:59
dolphmayoung: have you seen the crap nova and cinder are doing? that's our fault too18:59
ayoungdolphm, Ifd we tell people to change the endpoints in their service catalog to either drop the version or have v3, it will break all of the v2 clients out there18:59
fabiogjamielennox: since I have extended the Oslo notification model, I believe it should be available to all the Openstack modules18:59
morganfainbergit makes sense, but i just... never connected it18:59
ayoungso discovery solves it in the future, but it doens't get the car out of the ditch18:59
atiwaridolphm, link:http://en.wikipedia.org/wiki/SAML_2.0#HTTP_Artifact_Binding has good desc of artifact binding18:59
dstanekayoung: can you just start accepting a version via HTTP headers and have the server redirect in the case where a version is in the url and a different one is requested?18:59
jamielennoxfabiog: ah, ok, that's fine, i agree with the approach was just interested to know if you were re-using the concept from other projects or if we were going out on our own here19:00
dolphmayoung: understood, but let's write the tools to make the problem non-existant rather than advocating a hacky approach that we've demonstrated is garbage19:00
ayoungdstanek, avoid using the word 'just' cuz  no solution here is going to be neat or easy19:00
morganfainbergmarekd, i wasn't saying ECP was required, just wanted to ask if we were looking at it vs the "browser" style SAML ("traditional web SSO") model)19:00
marekdmorganfainberg: ah, ok.19:00
dstanekayoung: s/just //19:00
fabiogjamielennox: no not reinventing the weel, just connecting it to the rods ;-)19:00
morganfainbergmarekd, and the reasoning is it _could_ support CLi nicely19:01
bknudsondid nova / cinder ever ask us if they should have new service for different versions?19:01
morganfainbergmarekd, but that is all speculation19:01
*** vipul is now known as vipul-away19:01
ayoungdolphm, the problem is the old tools19:01
ayoungnot new19:01
jamielennoxtime people19:01
atiwaritime is up19:01
ayoungwe go to great lengths to avoid breaking old clients19:01
dolphmjamielennox: ah, thanks19:01
dolphm#endmeeting19:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:01
openstackMeeting ended Tue Dec 17 19:01:28 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-12-17-18.01.html19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-12-17-18.01.txt19:01
ayoungwe need to include the endpoints from the SC in the def19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-12-17-18.01.log.html19:01
fabiogall: merry christmas and happy new year!19:01
morganfainbergfabiog, wantt o chat about notifcations19:01
jeblairhi infra folks19:01
anteayao/19:01
fungiheyhey kids!19:01
morganfainbergfabiog, -> -dev19:01
zaroo/19:02
pleia2o/19:02
clarkbo/19:02
*** jamielennox has left #openstack-meeting19:02
jeblair#startmeeting infra19:02
openstackMeeting started Tue Dec 17 19:02:31 2013 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: infra)"19:02
openstackThe meeting name has been set to 'infra'19:02
jeblair#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:02
jeblair#link http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-12-10-19.02.html19:02
*** jtomasek has joined #openstack-meeting19:02
*** fabiog has quit IRC19:02
fungijeblair: before you go reassigning the tarballs action items to yourself, don't. almost done...19:03
jeblairfungi: oh cool, thanks.  :)19:03
*** thomasm_ has joined #openstack-meeting19:03
clarkbninja fungi19:03
jeblairfungi: how's the quota increase request?19:04
jeblair#topic actions from last meeting19:04
*** openstack changes topic to "actions from last meeting (Meeting topic: infra)"19:04
SergeyLukjanovo/19:04
fungidone. our openstackci account can go up to 25tb in rackspace now, and up to 100 cinder volumes19:04
clarkbfungi: awesome19:04
jeblairfungi: yaaay!19:04
*** jcooley_ has joined #openstack-meeting19:04
*** nkinder has left #openstack-meeting19:04
anteayafungi: woohoo19:04
fungii've added a 200gb volume for tarballs on static.o.o19:04
fungirsync'd the contents in19:04
anteayawhat did you say in the request?19:05
fungichecked out the vhost19:05
fungilowered ttl on the dns record to 5 minutes19:05
fungione minor cosmetic issue outstanding... can't get the new filesystem usage to show up in cacti19:05
*** salv-orlando has quit IRC19:05
fungirestarted snmpd on static, re-ran the graph creation scripts on cacti manually, no good19:05
jeblairfungi: cool, so i think next maybe just put jenkins.o.o in shutdown mode so it doesn't generate new tarballs, then do an rsync/dns switch19:05
*** greghill has left #openstack-meeting19:06
fungiagreed. catch-up rsyncs are taking on the order of 10 seconds looks like, so should go quickly19:06
clarkb++19:06
fungi#action fungi move tarballs.o.o to static.o.o19:07
*** thomasem has quit IRC19:07
*** ihrachyshka has quit IRC19:07
fungisligtly closer to tearing down the old wiki server19:07
jeblairalmost there!19:07
jeblair#topic Tripleo testing (lifeless, pleia2)19:07
*** openstack changes topic to "Tripleo testing (lifeless, pleia2) (Meeting topic: infra)"19:07
jeblairpleia2: anything to coordinate on here?19:08
*** ArthurBerezin1 has joined #openstack-meeting19:08
pleia2I don't think so19:08
jeblaircool19:08
pleia2I now have derekh's setup to test, but that's more on my side than infra just yet19:08
*** jcooley_ has quit IRC19:08
*** ArthurBerezin1 has left #openstack-meeting19:09
*** oubiwann has quit IRC19:09
jeblairpleia2: do you know if anyone has volunteered/been assigned to do ipv6 nodepool/jenkins work?19:09
*** nati_ueno has quit IRC19:10
pleia2jeblair: afaik, no one yet19:10
jeblairk19:10
jeblair#topic Savanna testing (SergeyLukjanov)19:10
*** openstack changes topic to "Savanna testing (SergeyLukjanov) (Meeting topic: infra)"19:10
SergeyLukjanovhey19:10
jeblairSergeyLukjanov: anything new here?19:10
SergeyLukjanoveverything is ok, waiting for review for tempest patches19:10
SergeyLukjanovnothing new atm19:10
clarkbSergeyLukjanov: the jobs are running though correct?19:11
clarkbSergeyLukjanov: they just don't actually test much yet19:11
SergeyLukjanovyup!19:11
SergeyLukjanovonly api for node group templates19:11
SergeyLukjanovwaiting for review19:11
*** dvarga has quit IRC19:11
jeblairthat's the best way to go -- things will be self-testing as they go into tempest19:11
SergeyLukjanovand then will add test for the rest api edpoints19:11
SergeyLukjanovhope to receive some reviews this week19:12
SergeyLukjanovtempest guys are very busy as I see19:12
anteayatempest people19:12
*** rongze has joined #openstack-meeting19:13
jeblairSergeyLukjanov: cool, thanks19:13
SergeyLukjanovbtw we're starting using zuul+nodepool to run savanna-ci and I hope that will return back with some patches to support neutron in nodepool19:13
*** nati_ueno has joined #openstack-meeting19:13
jeblairSergeyLukjanov: yeah, that'd be great19:13
*** Mandell has quit IRC19:13
SergeyLukjanovchanges are pretty small atm19:13
*** Mandell has joined #openstack-meeting19:14
SergeyLukjanovand I'd like to start discussion about dib jobs19:14
SergeyLukjanovbut I'm not prepared atm, so, let's do it offline19:14
SergeyLukjanovI'll try to prepare some initial queestions19:14
jeblair(though i hope you don't have to run savanna-ci much longer as we move things into openstack)19:14
*** weshay has quit IRC19:14
SergeyLukjanovjeblair, we'll need it to run slow tests19:14
SergeyLukjanovlike sequential scaling of clusters19:15
jeblairwell, as much as we can :)19:15
SergeyLukjanovyep :)19:15
SergeyLukjanovwe'd like to have at least all tests in tempest19:15
*** dolphm has quit IRC19:16
SergeyLukjanovand run them if needed in savanna-ci but from tempest19:16
*** herndon has quit IRC19:16
* fungi imagines a 100-node hadoop cluster being spun up for each change19:16
*** dvarga has joined #openstack-meeting19:16
SergeyLukjanov:)19:16
jeblairfungi: we'll need you to write more nice quota requests19:16
SergeyLukjanovwe've tested 200 nodes clusters19:16
jeblair#topic  Trove testing (mordred, hub_cap)19:16
*** openstack changes topic to "Trove testing (mordred, hub_cap) (Meeting topic: infra)"19:16
hub_capheyo jeblair19:17
jeblairhub_cap: heya!19:17
hub_capso SlickNik has updates (hes working on the dib elements)19:17
SlickNikhey guys.19:17
hub_cap#link https://blueprints.launchpad.net/trove/+spec/trove-tempest19:17
*** sarob has quit IRC19:17
anteayapeople19:17
hub_capi think next hes going to work on the image caching, right SlickNik? ;)19:17
SlickNikI didn't have much of a chance to work on this last week, but I'm going to be working on this 100% this week.19:18
*** rongze has quit IRC19:18
SlickNikYup image caching and devstack-vm-gate changes to run the tests.19:18
*** gyee has quit IRC19:18
SlickNikA couple of other folks from the trove team signed on to get started moving trove integration tests to tempest.19:19
hub_capand we have some people from mirantis working on server side tests, and we have some client tests in a review (iirc) already19:19
*** gokrokve has quit IRC19:20
*** herndon has joined #openstack-meeting19:20
jeblairSlickNik, hub_cap: yes tarballs.o.o is where we will stick images we build19:20
SlickNikflying-bond (Debashish) and dlakunchikov (Dmitri)19:20
*** ihrachyshka has joined #openstack-meeting19:20
*** jcoufal-mob has joined #openstack-meeting19:20
*** akuznetsov has joined #openstack-meeting19:20
hub_caphorray for progress19:21
*** esker has joined #openstack-meeting19:21
jeblairhub_cap: sounds good; any questions or blockers atm?19:22
*** jcoufal-mob has quit IRC19:22
*** jcoufal-mob has joined #openstack-meeting19:22
hub_capnone from myself19:22
hub_cap<319:22
SlickNikjeblair: none at the moment. I'll likely be bugging people for reviews this week, so stay tuned!19:22
* hub_cap turns a prop radio nob19:22
*** akuznetsov has quit IRC19:22
jeblaircool, looking forward to it!19:22
jeblair#topic  Jenkins 1.540 upgrade (zaro, clarkb)19:23
*** openstack changes topic to "Jenkins 1.540 upgrade (zaro, clarkb) (Meeting topic: infra)"19:23
jeblairso that happened, briefly, then unhappened.19:23
*** jcooley_ has joined #openstack-meeting19:23
anteayathe reason for the unhappening was lost or truncated logs, was it not?19:23
*** ruhe has joined #openstack-meeting19:23
zaroso i'm trying to setup latest jenkins with scp plugin to see what happened there.19:23
clarkbya it was sad19:23
*** jcoufal has quit IRC19:23
jeblairzaro: cool.  clarkb and i have both worked on that plugin19:24
clarkbanteaya: correct, new version of jenkins didn't play nice with teh scp plugin console copying19:24
anteayaah19:24
anteaya:(19:24
*** johnthetubaguy has quit IRC19:24
jeblairzaro: i think if you write a job that emits 10 or 20k lines to the console, that will probably be enough to replicate19:24
*** troytoman-away is now known as troytoman19:25
zaroyeah i have it setup in my dev env now, but having difficulties even getting plugin to connect to a server.19:25
zarostill working on it.19:25
*** jcooley_ has quit IRC19:25
jeblair#topic Maven clouddoc plugin move (zaro, mordred)19:26
*** openstack changes topic to "Maven clouddoc plugin move (zaro, mordred) (Meeting topic: infra)"19:26
zaro#link https://etherpad.openstack.org/p/java-release-process19:26
*** Mandell has quit IRC19:26
zarohaven't heard from sharwell since last wedn. 12/11.19:26
*** MaxV has joined #openstack-meeting19:26
zaroshould we just go ahead with this? #link https://review.openstack.org/#/c/58349/19:27
fungiit looks like i need to go into the sonotype jira and open a case requesting a dedicated groupId, based on subsequent info from dcramer19:27
zarofungi: yes, that does need to happen19:28
fungizaro: so i think that brings us back to the etherpad i originally prepopulated with all the info they want in the jira ticket fields19:28
anteayaso is the situation that you were coordinating with someone and now someone else is involved in the process, with no access to the prior person?19:28
fungineed to figure out all the little details about our org.openstack.cloud.api19:28
*** rpodolyaka1 has left #openstack-meeting19:28
*** jasondotstar is now known as jclark_19:28
*** jcooley_ has joined #openstack-meeting19:28
*** jclark_ is now known as jasondotstar19:28
zarofungi: i think you'll need to coordinate with sharwell on those fields.19:29
*** sarob has joined #openstack-meeting19:29
zaroaccording to dcramer sharwell can provide access.19:29
fungiokay, i guess they need to match what's on org.rackspace.cloud.api?19:29
*** thomasem has joined #openstack-meeting19:29
fungier, com.rackspace19:29
*** Mandell has joined #openstack-meeting19:30
zaroohh, wait that's right this is a new groupId.19:30
fungii'll find out19:30
*** harlowja is now known as harlowja_away19:30
zarothen i think you can just make it your own.19:30
*** marekd is now known as marekd|away19:30
fungiyeah, we have to ask sonotype to create it in maven central19:30
zaroi mean create it like new.19:30
zaroyes, you can probably create without sharwell or dcramer input then.19:31
fungiokay. do we request org.openstack.cloud.api or just org.openstack and then get the ability to create sub-ids i wonder19:31
*** jcooley_ has quit IRC19:31
fungii'll check with them19:31
*** jcooley_ has joined #openstack-meeting19:31
zaroi think former.19:31
zaroohh definately former.  cannot create subs.19:32
jeblair#topic  Private gerrit for security reviews (zaro, fungi)19:32
*** openstack changes topic to "Private gerrit for security reviews (zaro, fungi) (Meeting topic: infra)"19:32
jeblair(the zaro-fungi part of the meeting continues)19:32
zarojust got good feedback from fungi on the change.19:32
*** thomasm_ has quit IRC19:32
zaroyes, nothing new ATM, just WIP19:33
fungisorry it's taken me so long to find time to go over it, but i think it's close to what we need19:33
zarogood to hear!19:33
*** colinmcnamara has joined #openstack-meeting19:33
fungiprobably worth bringing to the group is whether we want to start it on latest gerrit rather than giving ourselves yet one more gerrit to upgrade from 2.419:33
clarkbI would be all for starting it on new gerrit19:33
zaroi think fungi mentioned that we should wait until 2.8 upgrade.19:33
*** colinmcnamara has quit IRC19:33
zaroor after 2.8 upgrade19:34
fungiwell, or just build it on 2.8 (there's not a lot special it really needs for the workflow we outlined)19:34
zaroyeah, ++19:34
jeblairyeah, i think for the moment we can say we'll target the rollout of security after we deploy 2.819:34
fungibut i'm fine with prioritizing the upgrade project, given limited resources19:34
jeblairi don't think we should try to run it on 2.8 while we're running regular gerrit on 2.419:34
fungiyep, totally agree19:34
zaro++19:35
jeblairthough since we don't know for certain everything that will be involved in the 2.8 upgrade and timeline yet, we should feel free to revisit that...19:35
jeblairif it looks like it'll be 3 months till we upgrade and security is ready to go, it'd probabl be better to go ahead and deploy security on 2.4 and upgrade it too.19:36
fungiokay19:36
zarocool.19:36
jeblair#topic  Upgrade gerrit (zaro)19:36
*** openstack changes topic to "Upgrade gerrit (zaro) (Meeting topic: infra)"19:36
jeblairspeaking of19:36
*** markwash has quit IRC19:36
zaroBlueprint https://blueprints.launchpad.net/openstack-ci/+spec/gerrit-2.8-upgrade19:37
zaroEtherpad #link https://etherpad.openstack.org/p/gerrit-2.8-upgrade19:37
zarojeblair: had a question in there about alternative to WIP plugin.19:37
*** weshay has joined #openstack-meeting19:37
zaroalso I’m blocked waiting for approval on #link https://review.openstack.org/#/c/61542/19:38
jeblair_david_ wrote up some text about the upgrade, so i copied it into the etherpad19:38
jeblair#link https://etherpad.openstack.org/p/gerrit-2.8-upgrade19:38
jeblair#link https://blueprints.launchpad.net/openstack-ci/+spec/gerrit-2.8-upgrade19:38
jeblairand then annotated it with some of my thoughts19:38
jeblairfungi, clarkb: ^ that's probably worth a read over and your initial feedback too19:38
fungiadding to my list19:39
jeblairit has some deployment choices19:39
clarkbjeblair: ok bookmarking19:39
fungizaro: on 61542 i think we were waiting for mordred to chime in, but he's been absent for a few days19:39
*** rbowen has quit IRC19:39
jeblairyeah, if he doesn't vote this afternood, let's aprv19:39
jeblairafternoon19:39
clarkbwfm19:40
jeblairi'd like to continue the tradition of unanimous approvals of ssh access if we can.  :)19:40
fungiagreed19:40
jeblair#topic  Zuul release (2.0?) / packaging (pabelanger)19:41
*** openstack changes topic to "Zuul release (2.0?) / packaging (pabelanger) (Meeting topic: infra)"19:41
*** epim has joined #openstack-meeting19:41
jeblairthis might be stale...19:41
jeblairand pabelanger isn't here...19:41
jeblair#topic  Open discussion19:41
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:41
pleia2if I could get feedback here, that would be useful: http://lists.openstack.org/pipermail/openstack-infra/2013-December/000515.html19:41
zarocan we circle back to clouddocs?19:41
*** ayoung is now known as ayoung_xc-ski19:41
*** nayana has joined #openstack-meeting19:41
pleia2working through publications, but we need branch names that make sense19:41
*** colinmcnamara has joined #openstack-meeting19:41
jeblairpleia2: eek, i missed that mail, sorry.19:42
zaronot sure i got an answer whether we should just go ahead with  https://review.openstack.org/#/c/58349/19:42
*** sushils has joined #openstack-meeting19:42
jeblairzaro: i think we should sit on it for now.19:42
pleia2and I also confirmed that we have all history from https://github.com/openstack-ci/publications so it can be deleted19:42
zarojeblair: np19:42
fungipleia2: i think the concern originally expressed was that until we move those into branches in the new location (and out of old git commits in the history) they're not exposed anywhere easily consumable19:43
pleia2fungi: fair enough, so we'll have that problem solved soon19:44
jeblairyeah, so let's keep ci/pub around until we finish the other branches19:44
jeblairand then delete19:44
fungii think it's safe to hold off deleting from github until then19:44
*** nachi has left #openstack-meeting19:44
*** dprince has quit IRC19:44
jeblairso it turns out that crm114 adds enough time to log processing that the workers got backlogged19:45
*** olaph has joined #openstack-meeting19:45
jeblairi'm working on a logstash worker puppet module refactor that will let us colocate multiple logstash workers on a single host19:45
*** jlibosva has quit IRC19:45
*** dprince has joined #openstack-meeting19:45
jeblairto better utilize cpu there -- especially once we move the workers to rax performance nodes19:45
fungioh, one other thing which sprang to mind for the tarballs move. the target path changes slightly on the new server, so i'll need to tweak the publisher location on jenkins.o.o for it after it quiesces19:45
jeblairand we'll add some more nodes as well19:46
*** jlibosva has joined #openstack-meeting19:46
jeblairit would be swell if we could graph the gearman queue...19:46
jeblairclarkb: maybe we could have the log client splat that to statsd/graphite?19:46
clarkbjeblair: right I was thinking of adding that feature to geard directly19:47
clarkbjeblair: unless yo uthink that is better off living external19:47
*** nermina has quit IRC19:47
jeblairfungi: ok, is that a change to the publishers in jobs, or is it a change to the scp site in the global config?19:47
zarofungi: will all the jjb jobs refer to static instead of tarballs.o.o now?19:47
fungijeblair: the latter19:47
jeblairclarkb: hrm; adding it to geard has a certain elegance19:47
fungizaro: they won't. the jobs stay the same because the publisher target stays the same19:48
clarkbjeblair: yeah may be generally useful to other geard users19:48
fungizaro: jeblair: it's the "Root Repository Path" which i'll need to update19:48
jeblairclarkb: yep.  we probably _don't_ want it for zuul though.19:49
*** vedlad has joined #openstack-meeting19:49
*** yassine has quit IRC19:49
jeblairoh, and i've proposed two changes to zuul that should allow us to start using templates in layout.yaml will will make it much smaller19:49
jeblairhttps://review.openstack.org/#/q/status:open+project:openstack-infra/zuul,n,z19:49
fungisaw the titles, haven't had time to review yet but very excited by the promise they make19:50
zaroohh that would be nice!19:50
*** bgorski has quit IRC19:50
*** vedlad has quit IRC19:50
*** jcooley_ has quit IRC19:51
fungioh, and stable/havana backports of the tox.ini sync are proposed now... https://review.openstack.org/#/q/branch:stable/havana+topic:tox-sync,n,z19:51
*** jcooley_ has joined #openstack-meeting19:51
*** vipul-away is now known as vipul19:51
fungimostly working, sdague and mtreinish helped me on missing/broken prereqs in devstack and tempest19:52
*** jcoufal-mob has quit IRC19:52
jeblairfungi: cool19:52
*** IlyaE has quit IRC19:52
*** vipul-away has joined #openstack-meeting19:52
jeblairanyone have anything else?19:52
clarkbfungi: is grizzly affected?19:52
*** jtomasek has quit IRC19:53
*** atiwari has quit IRC19:53
fungiclarkb: grizzly affected grenade upgrades to the havana patches, so there was some involvement there19:53
fungifor tempest anyway19:53
clarkbthank19:54
*** bdpayne has quit IRC19:54
fungithough havana and grizzly stable branches of most of the servers are back to being testable again as of this week19:54
fungifinally19:54
clarkbI don't have anything else19:55
zaroyep, all done19:55
*** epim has quit IRC19:55
jeblairthanks all!19:55
funginothing else for me19:56
jeblair#endmeeting19:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:56
openstackMeeting ended Tue Dec 17 19:56:02 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-12-17-19.02.html19:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-12-17-19.02.txt19:56
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-12-17-19.02.log.html19:56
*** jcooley_ has quit IRC19:56
*** nermina has joined #openstack-meeting19:58
*** jcooley_ has joined #openstack-meeting19:59
*** MaxV has quit IRC19:59
*** dhellmann_ is now known as dhellmann19:59
*** dcramer_ has joined #openstack-meeting19:59
*** kanzaros has joined #openstack-meeting19:59
*** colinmcnamara has quit IRC19:59
*** nayana has quit IRC20:00
*** MaxV has joined #openstack-meeting20:00
ttxAnyone here for the TC meeting ?20:00
mikalHi20:00
dhellmanno/20:00
jeblairo/20:00
sdagueo/20:00
jraimI'm here for questions on Barbican20:00
* devananda lurks20:00
*** novas0x2a|laptop has joined #openstack-meeting20:00
*** jcooley_ has quit IRC20:00
ttxrussellb, markmc, annegentle, mordred/mtaylor, jgriffith, vishy, markmcclain, lifeless: around ?20:00
markmcclaino/20:01
russellbo/20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue Dec 17 20:01:30 2013 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: tc)"20:01
openstackThe meeting name has been set to 'tc'20:01
ttxLast meeting for 2013 !20:01
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:01
*** d0ugal has quit IRC20:01
ttx#topic Becoming a Program, before applying for incubation20:02
*** openstack changes topic to "Becoming a Program, before applying for incubation (Meeting topic: tc)"20:02
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2013-December/022202.html20:02
ttxLet's discuss this first, as suggested by sdague at last meeting20:02
*** d0ugal has joined #openstack-meeting20:02
*** d0ugal has joined #openstack-meeting20:02
ttxSo... the idea is to somehow bless the idea / scope / mission of a team or a project before it files for incubation20:02
ttxThat way it can actually attract enough contributors to pass our ever-higher technical barriers to entry20:02
*** d0ugal has joined #openstack-meeting20:02
*** d0ugal has joined #openstack-meeting20:02
*** d0ugal has quit IRC20:02
ttxWhich solves the chicken-and-egg problem we had with various recent incubation proposals20:02
lifelesso/20:02
ttxVarious solutions tossed in that thread:20:02
ttx1. Reuse "Programs" for that (original solution proposed on the thread)20:03
ttx2. Reuse "Programs" but make new ones go through a trial period ("emerging programs")20:03
ttx3. Bless teams/missions, but don't call them programs yet ("emerging efforts" badge)20:03
ttx4. Bless projects themselves rather than teams/missions ("emerging projects" badge)20:03
ttx5. Don't bless, just set up an "Emerging projects" page containing prose describing the TC feedback on it20:03
ttxComments / thoughts ?20:03
ttx(personally I'm hesitating between (3) and (5) at that point)20:03
dhellmannI'm starting to like 5 myself20:03
jeblairi think the suggestions on the thread to make this a very light-weight endorsement sound good.  i think we should hold programs to a high standard, but if indicating that we think a project is a good idea and we'd like to encourage it helps, i think that's worthwhile.20:03
jeblairso i think 5 fits the bill20:04
mtayloro/20:04
sdagueyeh #5 seems reasonable to me20:04
markmcclainI like 520:04
*** MaxV has quit IRC20:04
ttxI'm fine with trying (5) as a first incremental improvement. I fear that won't generate enough visibility to make them reach critical mass, but we can revisit later.20:04
russellbsure, it's a pretty light weight step in the direction20:04
russellbyeah, we could do #5 for now, and more later if we feel it's necessary and justified20:04
vishyo/20:04
*** jtomasek has joined #openstack-meeting20:04
*** d0ugal has joined #openstack-meeting20:05
*** d0ugal has joined #openstack-meeting20:05
lifelessI don't think blessing something without substantial momentum makes sense20:05
lifelesstripleo only applied for incubation when it was already attracting developers20:05
dhellmannthat's the difference between 3 and 5, right?20:05
dhellmann5 gives us a way to avoid having multiple groups going off and trying to do the same thing (ceilometer and healthnmon)20:05
lifelessoh god yes20:05
russellblifeless: tripleo applied to be a program, not incubation ;-)20:05
ttxdhellmann: yes, 3 in boolean, 5 is float20:06
*** ArxCruz has quit IRC20:06
markmcclain5 also doesn't necessarily pick a team only that the we like the direciton20:06
lifelessrussellb: actually, we started before programs existed; our application was part of the 'oh yeah, we should change this' discussion AIRI :)20:06
ttxOK, I'll work on documenting the process around (5)20:06
ttxAdditional question: should we still auto-create programs for incubated projects, or should we wait until they graduate to being part of the integrated release ?20:06
ttxIt affects ATC/voting rights on one side, and what level of commitment we want "program" to actually mean on the other.20:06
lifelessI don't think an incubated project without a program makes any sense20:07
*** radez_g0n3 is now known as radez20:07
dhellmannI agree20:07
russellbagreed20:07
lifelessif the project hasn't attracted the attention it needs to also qualify as a program, thats a red flag to me20:07
dhellmannthe question of which program the project will be in should be part of the application20:07
ttxstatus quo would be "you shoudl have a program attached, even if that means creating it at incubation request time"20:07
jeblairyeah, keep programs for incubated projects -- it makes sense -- they are actively working on a deliverable and making measurable progress!20:07
ttxOK, all clear to me20:07
ttxI'll propose a change which adds a reference/emerging-projects page full of prose that will be published somewhere20:08
*** kenhui has joined #openstack-meeting20:09
ttxanything else on that subject ?20:09
markmcclainso the program springs into existence when they project is incubated?20:09
markmcclainor is the program incubated too?20:09
* markmcclain isn't clear on the idea here20:10
ttxmarkmcclain: unless the project is already part of an existing program yes20:10
*** mdomsch has joined #openstack-meeting20:10
*** heckj has joined #openstack-meeting20:10
ttxwe'd not have an incubation state for programs. We'd remove the program if the project fails to incubate20:10
*** heckj has quit IRC20:10
*** olaph has left #openstack-meeting20:10
lifelessso what about20:10
markmcclainttx: thanks for the clarification20:11
lifelessincubation requires a program that has been around for > 3 months20:11
*** heckj has joined #openstack-meeting20:11
*** vkozhukalov has quit IRC20:11
lifelessgive the program time to get out of the float area and be real before incubating a project20:11
dhellmannI thought we just said we don't want programs without real projects? and "real" means incubated or graduated20:11
ttxlifeless: that means back to option (1) up there20:11
lifelessttx: does it?20:11
ttxwell 5+1 admittedly20:12
dhellmannwhere do programs without projects come from?20:12
lifeless09:03 < ttx> 5. Don't bless, just set up an "Emerging projects" page containing prose describing the20:12
lifeless             TC feedback on it20:12
lifelessoh, I see - emerging projects20:12
* lifeless sits to think for a sec20:12
ttxlifeless: you'd require that incubation wannabees ask for a program before filing for incubation20:12
ttxwhich is what the whole thread was about20:12
* mtaylor doesn't understand the point of emerging projects vs. programs20:13
mtaylorboth require the TC to say "yup, that workstream seems great"20:13
mtaylorso both are a blessing, and we'll wind up wanting critera20:13
mtaylorcriteria20:13
mtaylorwe already have programs, and programs do not require any projects in the program to be incubated yet20:13
ttxmtaylor: (5) is a feedback, not a blessing. It's not yes/no20:14
mtaylorit's a blessing20:14
mtaylorit will be seen as a blessing20:14
mtaylorbecause it's official feedback from us20:14
*** kenhui has quit IRC20:14
lifelessso - let me check constraints: programs that aren't /delivering/ something are problematic [what deliver means is open for debate]; new programs (implied by new projects) want blessing to ramp up interest faster; delivering something is then key; but we don't want to add things that aren't mature to incubation.20:14
*** kenhui1 has joined #openstack-meeting20:14
*** harlowja_away is now known as harlowja20:14
ttxmtaylor: except anyone can ask for that feedback and receive it20:14
dhellmannediting a wiki page isn't a blessing, is it?20:14
ttxmtaylor: see markmc's posts on the thread20:15
lifelessttx: ok so I think 5 is fine : it's enough recognition to help force a collapse of the wave function from multiples to one; and its where things stay until they are really mature enough for incubation.20:15
lifelessat the point they are that mature there should be enough interest and multi-vendor collaboration to make a program non contentious20:15
*** denis_makogon_ has joined #openstack-meeting20:16
ttxmtaylor: 5 is different from 1-4 because the feedback is in shades of grey rather than black or white20:16
mtaylorI think it's overhead with no benefit. but I don't feel strongly enough about it to hold this up20:16
dhellmannI don't even think the TC needs to do anything for 5 other than direct people to how to edit the right page to list themselves20:16
*** brich has quit IRC20:16
*** dolphm has joined #openstack-meeting20:17
ttxmtaylor: also in the thread there was the concern of making sure a "program" came with some reasonable expectation of staying there20:17
ttxso it should not be granted to lightly20:17
ttxtoo*20:17
mtaylorthe problem as I see it is that designate does things that we clearly want, and it works, and it's participating to a degree - but it's not quite ready for incubation20:17
*** alexpilotti has joined #openstack-meeting20:17
mtaylorso letting designate tell people that they're working on things solves nothing20:17
mtaylorand random feedback solves nothing20:18
ttxin the new world order, they would ask for feedback to the TC, which would be "very interesting, we want you, just mature a bit"20:18
sdaguemtaylor: it doesn't? you don't think it drives people over there20:18
dhellmannso this page wouldn't be something anyone could edit, then?20:18
*** gokrokve has joined #openstack-meeting20:18
mtaylorthe actual probelm is the chicken and egg problem of resources waiting for blessing and blessing waiting for resources20:18
russellba TC curated list of projects we like seems like a good page to be able to go to and see what's coming20:18
mtaylorsdague: no. I do not20:18
*** heckj has left #openstack-meeting20:18
lifelessbut there are two sorts of resources right?20:18
dhellmannI thought the problem was groups not having enough publicity to gain enough contributors to meet incubation requirements20:19
dhellmannwhat are we trying to solve?20:19
russellbTC curated meaning at least we're keeping it up to date, and it doesn't have stupid crap in it20:19
*** vipul-away is now known as vipul20:19
mtaylorI don't think it's publicity20:19
ttxmtaylor: I agree with you. I /fear/ that (5) won't give them the visibility they want either20:19
lifelessthere are volunteers and there are foundation sponsoed20:19
ttxbut i'm fine with giving it a try20:19
mtaylormost of our devs are corporate sponsored20:19
lifelesse.g. more people hacking vs -infra support when things go pearshaped20:19
*** markmc has joined #openstack-meeting20:19
ttxmarkmc: o/20:19
mtaylorwhich means that most of them come from product efforts - we want those to wind up in good openstack things20:19
*** denis_makogon_ is now known as denis_makogon20:19
lifelessto get more people hacking, as mtaylor says, it's a corporate engagement issue20:19
markmc(sorry, family stuff)20:19
mtaylorso if it's not "OpenStack" - the people providing the devs are less likely in some cases to pony up the people - I think we're seeing this more and more now that we have so many projects20:20
ttxmarkmc: mtaylor was unconvinced by your prose page, and thinks projects want to be blessed20:20
mtaylorhrm. why am I mtaylor?20:20
markmcsure projects want to be blessed :)20:20
ttxmtaylor: good question20:20
*** fnaval_ has joined #openstack-meeting20:20
*** mtaylor is now known as mordred20:20
lifelessmordred: I thought you were trolling us :)20:20
russellbmordred: thanks, i was worried about you20:20
markmcthere'll always be some point we're not prepared to bless them though20:20
* markmc likes the idea of giving concrete feedback rather than ever fine-grained levels of incubating status20:21
*** fnaval_ has quit IRC20:21
*** dolphm has quit IRC20:21
mordredso, if it's not a mechanism for us to 'bless' an effort or a direction, I think it's a waste and we should just do nothing because I dont' think it will appreciably change what's going on20:21
mordredand just adding overhead for the heck of it is the last thing we need20:21
*** fnaval_ has joined #openstack-meeting20:21
ttxmarkmc: like I said, i'm fine with giving it a try, just fearing it won't get the projects what they want, so they will continue to rush incubation requests20:22
markmcpeople want to know what we think of e.g. Designate20:22
markmcwhat's our answer?20:22
markmcgo read the irc logs ?20:22
ttxand preserve the chicken-and-egg issue we are trying to solve here20:22
markmcwe might invent a "promising" status to give them and every other nascent project?20:22
mordredI mean, hell - let's try it - I might be wrong - I just think it's not going to work any better than the last time we tried it20:22
lifelessI think the real question is:20:22
markmcpeople just want to know what we think of it, how it's likely to proceed, what we think it needs20:22
*** fnaval has quit IRC20:23
lifeless - do we want other companies to compete with e.g. designate or20:23
lifeless - do we want them to collaborate on e.g. designate20:23
mordredwe used to have a special category for ecosystem projects - atlas lb wound up there20:23
mordredlook at how that worked20:23
russellbis the "emerging projects" page proposed with #5 something maintained through the governance repo?20:23
annegentle_mordred: do you sense that designate is getting stalled because of the tc or other factors?20:23
russellbor is it just a random wiki page?20:23
ttxlifeless: the latter, at this point20:23
lifelessAnd and *what point* do we signal to other companies that we want this to happen.20:23
markmclifeless, whatever gets us a viable project, in the end20:23
lifelessBlessing is all about that.20:23
ttxrussellb: governance repo20:23
lifelessmarkmc: ttx: It was a rhetorical question meant to frame discussion :)20:24
*** IlyaE has joined #openstack-meeting20:24
russellbttx: if it's in our repo, then it's sure going to look like a blessing to some degree, right?20:24
annegentle_and I agree with lifeless's heart of the matter20:24
markmclifeless, rhetorical question means implied answer - you just got two different answers :P)20:24
*** ayoung_xc-ski is now known as ayoung20:24
lifelessmarkmc: :)20:24
ttxrussellb: maybe.20:24
lifelessSo actually I think that shows up the issue20:24
lifeless...20:24
ttxOK, let's try it20:24
lifelessthere are two big phases we go through for new projects20:24
markmclifeless, an issue, for sure20:24
lifelessthere is the thousand flowers blooming phase20:25
ttxnobody says it's wrong, seom people think it's not enough20:25
*** johnthetubaguy has joined #openstack-meeting20:25
russellbfair enough.20:25
ttxlet's try it and see20:25
markmcif we were sure designate was absolutely the way forward, why not incubate it?20:25
lifelesswhere there are lots of independent attempts, some proprietary, some open and unaffiliated, some affiliated with openstack20:25
sdaguettx: +1 - I say try, and try to fail quickly if it's wrong20:25
markmcwe're not - a community hasn't formed around it?20:25
lifelessand then we incubate one and it all changes - it's a phase transition20:25
lifelessI think the thing we're struggling with is just where we trigger the transition20:26
*** cloudon has joined #openstack-meeting20:26
ttxlet's go to practical exercise now, Barbican.20:26
lifelessAnd having reframed it this way, I'm now changing my opinion on what we should do :)20:26
*** cloudon1 has quit IRC20:26
ttxow.20:26
lifelessttx: go on, barbican ?20:26
ttx#topic Barbican incubation request20:27
*** openstack changes topic to "Barbican incubation request (Meeting topic: tc)"20:27
mordredmarkmc: how many of our projects formed a community pre-blessing?20:27
ttxlifeless: thought you were disagreeing with way forward20:27
mordredmarkmc: honestly20:27
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2013-December/020830.html20:27
lifelessttx: Oh I am20:27
ttx#link https://wiki.openstack.org/wiki/Barbican20:27
russellband20:27
dhellmannmordred: was there a blessing for ceilometer that I'm not aware of?20:27
russellb#link https://wiki.openstack.org/wiki/Barbican/Incubation20:27
markmcmordred, sure - that's what we want - and "blessing" becomes about recognizing that20:27
mordredmarkmc: I'm saying I think it might be unreasonable20:28
*** dolphm has joined #openstack-meeting20:28
ttxlifeless: so should we continue to discuss it ?20:28
markmcmordred, oh, I see - so, were we unreasonable not to bless designate?20:28
mordredmarkmc: no - I'm not saying that20:28
mordredI'm saying that we might have a expectation that projects are going to grow vibrant communities outside of our context, and I'm not sure we have much evidence that that ever happens20:29
mordredas we are a lovely incubator for community formation20:29
jeblairmordred: neutron, ceilometer, heat, trove, ironic, marconi, savanna, tripleo all formed communities before blessing.20:29
mordredjeblair: I disagree20:29
mordredjeblair: neutron was blessed by fiat back in the ppb days, heat was largely redhat, ironic was a nova splitout20:30
*** jlibosva has quit IRC20:30
ttxmordred: let's go back to this if there is tima at the end of meeting20:30
mordredok20:30
*** dolphm has quit IRC20:30
ttxso, second session on barbican20:31
ttxI don't think this week actually changed my view on this... quoting me from last week:20:31
*** epim has joined #openstack-meeting20:31
ttx<ttx> it looks like the scope of the project is well-defined and makes sense20:31
ttx<ttx> there are some concerns about team size/diversity and some work to be done before filling all the current requirements for incubation20:31
russellbthough +1 for the team working quickly on the incubation requirements in the last couple of weeks20:31
*** vipul is now known as vipul-away20:31
ttxI liked the recent discussions around whether it could belong to the Identity program or not -  really appreciated20:31
jraimAt this point, we've nailed down the technical reqs. Oslo.messaging has landed and after a rebase, pbr and global-reqs will land20:32
ttxultimately barbican / secrets management warrants its own program... separate from identity/auth.20:32
russellbjraim: devstack-gate still pending right?20:32
sdaguethe relatively concrete tasks on testing (testr & d-g jobs) aren't done yet20:32
jraimrussellb yeah, we needed pbr and globals first, which needed oslo20:32
jraimso a bit of a house of cards20:32
russellbk20:32
jraimtestr is done in branch, but we need to work through the implications on our existing testing20:33
*** rfolco has quit IRC20:33
jraimshould be soon (tm)20:33
*** johnthetubaguy has quit IRC20:33
*** jecarey has joined #openstack-meeting20:33
ttxif I were to write feedback in prose, I'd say "we want that, and really close to meet technical incubation requirements"20:33
*** mrunge has joined #openstack-meeting20:33
*** SumitNaiksatam has quit IRC20:34
ttxbut then, I have concerns with team diversity. And I fear not blessing them in any way won't give them an easy way to solve that one20:34
lifelessso this is the bit mordred is talking about20:34
lifelessand in a way me too20:34
jraimI did ask some people that have expressed interest to say so on the list20:34
jraimSo we saw some traffic from RedHat, HP and Nebula20:34
russellbit's cheap to express interest, though20:34
lifelessI think by saying 'you know, you're /nearly there/' we're well past the point where we want to see more competition20:34
russellbthat doesn't mean a whole lot20:34
sdagueso we just went through making technical requirements for the bar you had to pass to incubate20:34
ttxlifeless: yes, and why I think ultimately (5) won't give them enough visibility to reach critical mass20:34
jraimand we have an active contributor from eValut that strated recently20:34
mordredlifeless: ++20:35
lifelessI think we're into the 'we want collaboration' phase of the lifecycle.20:35
annegentle_the team diversity concern is why we are also discussing designate in a similar vein20:35
*** markwash has joined #openstack-meeting20:35
sdagueso I really think those a requirements to complete first, and the whole thing is sort of moot until that's checked off.20:35
lifelesssdague: some of our requirements are more social than technical20:35
russellbsdague: yeah but realistically they could have the rest of those requirements checked off by january20:35
mordredwe're not questioning if we want this thing, and I don't think we actually are afraid it's going to top having devs this instant - I _do_ think that we dont' want to graduate it without a bunch of things20:35
lifelesssdague: and the team can't do /those/ on their own.20:35
russellband then we're back to the team diversity questions20:35
markmclifeless, honestly, if we're past the point of wanting to entertain any competition - it's time to incubate20:35
jraimrussellb that's our plan20:35
sdaguelifeless: sure20:36
lifelessmarkmc: I agree20:36
mordredmarkmc: ++20:36
lifelessmordred: I was leading there gently ;)20:36
sdaguerussellb: also, sure, but if today is an incubation vote, then it should be a clear "no"20:36
russellbfair point20:36
lifelessbah20:36
lifelessmarkmc: ^20:36
russellbso maybe the team diversity question should be more about graduation than incubation?20:36
lifelessrussellb: yes!20:36
russellbsdague: yep, but might as well discuss20:36
jraimI think we would be fine picking this back up in Jan once we've merged the last technical bits20:36
ttxmarkmc, lifeless, mordred: so what you're saying is.. we should NOT have team diversity/size requirements in incubation requirements ?20:37
lifelessttx: Size yes, diversity no. IMO.20:37
sdaguejraim: yeh, realistically that's what I'm proposing.20:37
jraimBut as people have said, the team composition probably isn't going to change by then20:37
russellband add diversity for graduation, yes?20:37
mordredrussellb: ++20:37
russellbthat seems reasonable i think20:37
markmcclainI think diversity should be part of incubation20:37
ttxlifeless: could you expand on that in a way that would be fair to designate ?20:37
mordredit takes time to grow team, and it takes a decent investment by devs to earn that team status20:37
jeblairi think diversity is important for incubation and we should hold our standards there20:37
markmcdiversity is important, but more for graduation I think20:37
markmcclainotherwise we'll have large entities apply based on team size20:38
mikalHas anyone taken a look at if barbican is using all the bits of olso we think it should?20:38
lifelessttx: rationale: If a company sponsors a project that we are convinced makes sense for the project technically and scope wise, and they fund it to a sufficient degree... meet technical merits, and stability...20:38
russellbwell we'll have to look at relative contributions when looking at size20:38
jeblairincubation means devoting limited openstack-project-wide resources to a project20:38
jeblairand i don't think that's appropriate to do when a project has only managed to get contributors from one vendor20:38
ttxlifeless: i'm easily convinced in my evenings20:38
dhellmannjeblair: +120:38
sdaguejeblair: +120:38
markmcclainjeblair: +120:38
annegentle_ttx: must be the dinner wine20:39
ttxI'm with jeblair on that20:39
mikalHas anyone taken a look at if barbican is using all the bits of olso we think it should?20:39
mordredI think with some of the smaller projects we're not going to get contributors from other vendors until it's incubated20:39
lifelesswhy not? Ignore the single vendor aspect for a second20:39
lifelessIf:20:39
lifeless - we want the project20:39
markmcI think there's a point between "single company dominated and controlled project" and diverse project20:39
*** gyee has joined #openstack-meeting20:39
lifeless - we want collaboration at this point, not competition20:39
mordredand also - I argue all the time that nobody should care that I work for HP20:39
jraimmordred that's my concern20:39
lifeless - it's the only one being offered up to us20:39
markmci.e. a "totally open and meritocratic, in excellent shape, crying out for others to come along and play" project20:40
lifeless=> how is it inappropriate?20:40
markmclifeless, diversity is important for long-term viability, is the point20:40
jeblairlifeless: it could indicate a lack of viability20:40
ttxlifeless: I guess it boils down to: do we want 2 stages of incubation (tech + social requirements met) or just one20:40
lifelessmarkmc: totally agreed, but the chicken and egg problem ttx describes is /all about collapsing the competition function/20:40
jeblairit might suggest there's something about how the project is run so that others are having trouble participating; or it could mean no one outside of that company is interested20:41
*** dolphm has joined #openstack-meeting20:41
mordredHP funded infra single-handedly for a while - did that make any of us think that infra was somehow less OpenStack worthy?20:41
dhellmannright, if a project comes along in that state I wonder why that company hasn't *already* started trying to find other contributors20:41
mordredor did it mean that HP was the only one with a person who was fighting to put employees on it20:41
lifelessjeblair: it could, and thats the question. Monty doesn't see a lot - any - evidence that viability correlates with diversity pre-incubation20:41
lifelessin fact, I would point at neutron20:41
ttxmordred: I'd argue it's a bit of a corner case.20:41
markmclifeless, so, do we do that only after diversity is achieved or in order to encourage diversity - that's the question20:41
lifelessand say that diversity is at best a weak predictor of viability20:41
mordredttx: I wouldn't - geting FTEs on a project is hard20:41
* markmc is okay with using it to encourage diversity if everything else is in great shape20:42
mordredttx: it's even harder when companies do not see product potential20:42
lifelessmarkmc: yeah, thats where I have circled around to20:42
markmcand we believe the project is truly welcoming, meritocratic, etc.20:42
jeblairlifeless: monty struck a number of projects from my quick list, but not all of them20:42
lifelesswe shouldn't go light on /technical requirements/20:42
mordredand they have a BUNCH of openstack projects to contend with - so if they have to choose between putting people on barbican or on nova ...20:42
jeblairi think we've switched back to the other topic.20:42
*** epim has quit IRC20:42
ttxyes, let's stop for a sec20:43
ttxI think we owe barbical an answer20:43
ttxBarbican*20:43
lifelesslol20:43
lifelessI like the new name20:43
*** vipul-away is now known as vipul20:43
ttxand I think it should be: come back to us when all tefchnical checkboxes are crossed, which should be anytime now20:43
sdaguettx: +120:43
mikalttx: I'd like to dig into oslo and barbican a bit more if I could20:43
lifeless+120:43
jraimttx That's fine with us20:43
ttxrather than rush the decision today while they are not all crossed20:44
*** dolphm has quit IRC20:44
dhellmannis there an official checklist they are working from?20:44
jraimmikal If we take this back up in Jan, would that give you enough time to dig in a bit more?20:44
ttxjraim: hopefully we'll have gotten our mind together on the spcoam aspect in the mean time20:44
sdague#link https://wiki.openstack.org/wiki/Barbican/Incubation20:44
mikaljraim: sure20:44
sdaguedhellmann: ^^^20:44
dhellmannsdague: thanks20:44
mikaljraim: mostly I want to dicsuss it and reach a concensus20:44
sdaguetwards the bottom20:44
ttxs/spcoam/social20:44
mikaljraim: but that can wait, so long as we do it before voting...20:45
jraimmikal that's fine. We're on #openstack-barbican if you have questions20:45
ttx#topic incubation vs. recognition20:45
*** openstack changes topic to "incubation vs. recognition (Meeting topic: tc)"20:45
*** denis_makogon has left #openstack-meeting20:45
ttxok, back to the bazaar20:45
*** nelsnelson has quit IRC20:45
mikalHeh20:45
ttxso, like I said, it boils down to...20:45
*** nelsnelson has joined #openstack-meeting20:46
mordredtripleo was all HP when it got accepted, trove only picked up a second vendor because of internal herculean efforts by jcooley, savanna was questionable as to real diversity but we made a judgement call20:46
jeblairmordred: i'm sensitive to what you're saying about getting companies to contribuet fte to a project; maybe you can help me understand how incubation helps there -- how does that make them see product potential and devote fte?20:46
ttxshould we care about diveristy at incubation time20:46
lifelessmordred: we had sigificant rackspace and bluebox interest - even a couple patches IIRC20:46
mordredjeblair: yes, it does20:46
ttxjeblair says yes20:46
lifelessmordred: + some early redhat fixes20:46
ttxmordred says no20:46
lifelessmordred: but we didn't have any non-HP -core.20:47
mordredjeblair: because it makes them se that they're going to need to engage with the project coming down the pipeline20:47
markmccould we be more explicit about long term viability - e.g. identify things that could prevent diversity ?20:47
*** hartsocks has joined #openstack-meeting20:47
lifelessjeblair: I would say it doesn't help them see product potential.20:47
markmcrather than making it a numbers game20:47
mordredjeblair: also, it shows them that it's more costly to do internal private dev than to collaborate with openstack20:47
lifelessjeblair: it helps them see where they need to collaborate vs wrap20:47
*** sarob_ has joined #openstack-meeting20:47
jeblairmarkmc: a single vender changing their mind and retasking/laying off a team seems like a big risk20:47
mordredwithout that, it's the question of collaborating with 'random-open-source' - which does not carry the same weight right now20:47
ttxincubation triggers non-trivial support efforts from various programs in openstack... Should we require a minimum of diversity before granting those ?20:48
mordredjeblair: right. which is why I think it's _ESSENTIAL_ for graduation20:48
lifelessjeblair: the mindset many vendors have is 'we need X for our customers, is X part of OpenStack? No -> spin up a team and build it in-house. Yes? Collaborate'20:48
mordredlifeless: ++20:48
markmcjeblair, oh, it is - it's extremely important for graduation IMHO20:48
mordredI think there is no dissent that diversity is required for graduation, actually20:48
jeblairmordred: half of our development infrastructure is now devoted to helping new projects bootstrap themselves in our environment20:48
lifelessjeblair: some orgs build it in-house and open source it (which is how e.g. designate came about AIUI)20:49
sdagueso we should probably be giving our existing incubating projects a report card on how they are doing there20:49
mordredjeblair: that is true20:49
lifelessjeblair: others build it in-house and sell it as part of their offering.20:49
annegentle_I'm with jeblair on concerns about halving resources just to help out incubating projects20:49
*** epim has joined #openstack-meeting20:49
*** sarob has quit IRC20:49
lifelessjeblair: either way, the lack of a 'this is part of OpenStack' creates a void, which for some companies is an opportunity, for others a weakness20:49
* mordred still points out that other companies are welcome to contribute FTEs to Infra - which would help20:50
annegentle_we've seen difficulty with large projects like neutron getting vendor support but not core support, so there's some nugget of concern about too much diversity too.20:50
annegentle_jus' sayin'20:50
lifelessannegentle_: +1. Though I wouldn't say 'too much diversity', I would say thats a cultural norm issue.20:50
sdagueannashen: I think that's a different issue20:50
annegentle_I'm more leaning towards concerns about long term viability -- and user and operator uptake.20:50
lifelessannegentle_: We want a norm of 'we're all building this together' within teams.20:50
sdaguelifeless: +120:51
lifelessnot, a 'ok there is an API shuim and ALL MY GOODNESS IS PROPRIETARY'20:51
jeblairannegentle_: i agree, it does suggest that it's more than just numbers we need to consider20:51
annegentle_lifeless: yes I like collab models better than compete20:51
mordredjeblair: ++20:51
mordredor, annegentle_ ++ rather20:51
lifelessjeblair: so concretely, what I'm suggesting is tht when we - the TC - /want/ the project [vs it being pushed onto us]20:51
lifelessjeblair: that all the questions about infra resources etc are moot: we've already decided *we want it*20:52
ttxOne question is, would we punt projects from incubation because they fail to get more diverse ?20:52
lifelessthe questions that matter are:20:52
*** vipul is now known as vipul-away20:52
lifeless - is it technically viable - all the stuff we seem to agree on20:52
*** sarob_ has quit IRC20:52
lifeless - and some thorny social assessment, do we expect it to play well with others and have good norms20:52
lifelessAll I'm saying is that we can't really assess the second via a hard rule of 'X vendors involved' because of the dynamics of how vendors get involved.20:53
lifelessIt's the heart of the chicken and egg issue.20:53
ttxlifeless: would you say we rejected designate on a diversity argument, or a size argument ?20:54
ttxmordred: ^20:54
markmcI'd say both20:54
markmcdiversity definitely came into it, though20:54
markmcif it was a larger team, it might have been a good discussion as to whether we could have passed on diversity20:55
ttxOK, 5min left, we need to move on, let's push that to a thread20:55
ttxmordred, lifeless: and since you seem to care about it, please participate to it20:55
ttxbecause nothing in the thread posted last week actually let us anticipate your concerns20:56
markmcheh20:56
ttxsince you didn't post to it.20:56
jeblairlooking at barbican's irc meeting logs20:56
jeblairhttp://eavesdrop.openstack.org/meetings/barbican_weekly_meeting/2013/barbican_weekly_meeting.2013-12-05-20.01.log.txt20:56
jeblairthere are 78 lines20:56
ttx#topic J naming determination process20:56
*** openstack changes topic to "J naming determination process (Meeting topic: tc)"20:56
*** dolphm has joined #openstack-meeting20:56
ttx#link http://lists.openstack.org/pipermail/openstack-tc/2013-December/000444.html20:56
lifelessttx: I hadn't gotten to the heart of it before20:57
ttxUnless there are objections, I'll follow the SurveyMonkey route with the 10 candidates mentioned on:20:57
lifelessttx: before the meeting it all sounded plausible.20:57
jeblairhow do we determine the viabality of a community based on so little evidence20:57
*** jtomasek has quit IRC20:57
lifelessttx: then new data -> ideas -> changed opinion20:57
ttx#link https://wiki.openstack.org/wiki/ReleaseNaming20:57
lifelessjeblair: perhaps we don't; perhaps we make it easy to handle failures instead?20:57
sdaguettx: +1 survey monkey20:57
ttxlifeless: apology accepted :)20:57
mordredttx: ++20:57
annegentle_Survey monkey ftw20:57
dhellmannttx: +120:57
jeblairttx: wfm20:57
notmynamelet's please not name a release after other major open source projects (jekyll)20:57
lifelessJenkins!20:58
ttxnotmyname: I actually got the express authorization from Tom Preston-Warner20:58
ttxthat we can reuse jekyll in that context20:58
*** swifterdarrell has joined #openstack-meeting20:58
dhellmann#link http://jekyllrb.com/20:59
* dhellmann doesn't think there's anything static about openstack20:59
ttxNick Quaranto also agreed there was no namespace overlap20:59
*** jtomasek has joined #openstack-meeting20:59
ttxboth were fine with us reusing it for a release cycle naùe20:59
ttxname20:59
ttx#topic Other governance changes in progress20:59
*** openstack changes topic to "Other governance changes in progress (Meeting topic: tc)"20:59
ttxquickly20:59
lifeless60 seconds20:59
ttxProvide infrastructure for publishing docs to docs.openstack.org: https://review.openstack.org/#/c/61380/20:59
*** kgriffs has joined #openstack-meeting21:00
ttxThis one is more technical than governance, so I'm fine with approving it once infra / Anne vets it21:00
ttxAttach extra ATCs to programs: https://review.openstack.org/#/c/62009/21:00
annegentle_so I don't get it21:00
ttxThis one will be approved as soon as it reaches enough approvals21:00
ttxannegentle_: ask question21:00
annegentle_is the proposal to provide only sphinx/oslo infra for publishing docs? or to provide sphinx/oslo infa for publishing governance pages that are considered sources of truth?21:00
*** fnaval has joined #openstack-meeting21:01
jeblairannegentle_: one of the things we talked about when moving the tc motions into git was that we could publish what we produce21:01
ttxthe latter, I think21:01
annegentle_that's at the heart of my comment about the commit message possibly being misleading. It made me read it twice.21:01
sdagueannegentle_: it is providing infrastructure so that we can publish contents of the repository to the web21:01
annegentle_if it's the latter, then why not publish to the wiki?21:01
jeblairannegentle_: so essentially governance is a doc repo only21:01
jeblairannegentle_: so the latter21:01
sdaguevs. sending people to git urls21:01
sdaguewhich is what we do now21:01
ttxannegentle_: because it's not really simpler21:01
annegentle_I have concerns about publishing to docs.o.o: version tracking, keeping history, search capability, and where do bugs get tracked21:01
ttxok, time is up, move discussion to corresponding review.21:02
annegentle_git is a perfectly good publishing system21:02
sdagueand I'm -1 to publishing to wiki automatically anyway, because a wiki is a rw medium21:02
sdagueand this isn't21:02
*** epim has quit IRC21:02
ttx#endmeeting21:02
annegentle_wiki gives us the concerns addressed abo ve21:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:02
openstackMeeting ended Tue Dec 17 21:02:20 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-12-17-20.01.html21:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-12-17-20.01.txt21:02
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-12-17-20.01.log.html21:02
annegentle_ttx: where should I continue to discuss these concerns?21:02
*** markvoelker1 has joined #openstack-meeting21:02
ttxon the review, and in a -tc thread if that fails21:02
dhellmannannegentle_: this feels like a ML discussion to me21:02
annegentle_dhellmann: ok21:02
jeblairannegentle_: it'll take an infra review to actually happen as well.  you'll be on it.21:03
ttxdhellmann, dolphm, notmyname, jd__, markwash, jgriffith, russellb, stevebaker, david-lyle, markmcclain, hub_cap: around ?21:03
dhellmannannegentle_: I share some of your concerns, but I think we can address them by linking to git for the history21:03
notmynamehello21:03
dolphmo/21:03
jd__o/21:03
david-lyle_o/21:03
ttx#startmeeting project21:03
dhellmanno/21:03
markmcclaino/21:03
openstackMeeting started Tue Dec 17 21:03:32 2013 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:03
*** openstack changes topic to " (Meeting topic: project)"21:03
openstackThe meeting name has been set to 'project'21:03
devanandao/21:03
markwasho/21:03
ttxAgenda for today:21:03
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:03
kgriffso/21:03
stevebaker\o21:03
*** d0ugal has quit IRC21:03
russellbo/21:03
ttx#topic Icehouse-2 roadmap21:04
*** fnaval_ has quit IRC21:04
SergeyLukjanovo/21:04
*** openstack changes topic to "Icehouse-2 roadmap (Meeting topic: project)"21:04
*** d0ugal has joined #openstack-meeting21:04
*** radsy has joined #openstack-meeting21:04
ttxAll looks good from our 1:1s21:04
*** d0ugal has quit IRC21:04
*** d0ugal has joined #openstack-meeting21:04
ttxwe'll skip the next two meetings21:04
ttxand check back progress on the Jan 7th meeting21:04
hub_capbam21:05
ttx#topic Gate checks (notmyname)21:05
*** mdomsch has quit IRC21:05
*** openstack changes topic to "Gate checks (notmyname) (Meeting topic: project)"21:05
notmynamehello21:05
lifelesshello!21:05
ttxnotmyname: hi! care to introduce topic ?21:05
notmynamehere's where we start:21:05
notmynameI've been hearing (and experiencing) some major frsutration the the amount of effort it takes to get stuff through the gate queue21:05
notmynamein some cases, it takes days of rechecks. other times, it's merely a dozen hours or so21:06
*** sandywalsh_ has quit IRC21:06
notmynameso I started using the stats to graph out what's happening21:06
notmynamehttp://not.mn/gate_status.html21:06
*** topol has quit IRC21:06
notmynameand the end result, as shown on the graph above, is that we've got about a 60-70% chance of failure for gate jobs, just based on nondeterministic bugs21:07
jog0notmyname: we also wedged the gate twice in less then 3 months21:07
notmynamethis means that any patch that tries to land has a pretty poor chance of actually passing21:07
notmynamenote that over the last 14 days, there are 9 days where a coin flip would have given you better odds on the top job in the gate passing21:07
russellbI feel like folks like jog0 and sdague have done a nice job watching this status and raising extra awareness for important issues21:08
*** dims has quit IRC21:08
russellbthere's plenty of room for more attention to some of the bugs, though, for sure21:08
russellbnotmyname: but do you have anything in particular you'd like to propose?21:08
notmynameso I want to do 2 things21:08
notmyname(1) raise awareness of the issue (now with real data!)21:08
notmyname(2) propose some ideas to fix it21:08
russellbi feel like everyone has been very aware already  :-)  ... but your graph is neat21:09
notmynamewhich leads to other ideas, I hope21:09
*** dims has joined #openstack-meeting21:09
notmynameso for (1), I claim that a 60% pass chance for gate jobs is unacceptable21:09
dolphm++21:09
markwash+121:09
david-lyle_+121:09
*** portante has joined #openstack-meeting21:09
russellbi don't think anyone is going to argue with failures being bad21:10
notmynameand I have 3 proposals of how we can potentially still move forward with day-to-day dev work21:10
dolphmcan we gate on pass chance? :P21:10
*** yamahata has joined #openstack-meeting21:10
jog0russellb: I would disagree with me doing a good job of raising awareness and watching status. we haven't been able to get the base line low enough and getenough bugs fixed. wehave been able to track how bad it is and prioritize but that isn't enough21:10
russellbjog0: OK, well just trying to give props where it's due for those working extra hard on things21:10
sdaguedolphm: only if we can take people's +2 away from them for a week when they push a 100% guarunteed to fail change to the gate :)21:10
russellbyour reports help me21:10
dolphmsdague: where do we sign people up21:10
dhellmannjog0: yeah, +1 to what russellb said, don't knock yourself for not having super powers21:11
notmynamerussellb: yes, I agree that the -infra team has done a great job triaging things when they get critical. but let's not stay there (as we have been)21:11
sdaguewhich was actually a huge part of the issue the last 4 days with all the grizzly changes21:11
notmynamefirst idea: multi-gate-queue21:11
notmynamein this case, instead of having one gate queue, have 321:11
notmynameHave N gate queues (for this example, let's use 3). In gate A, run all the patches like today. In gate B, run all but the top patch. In gate C, run all but the top 2. This way, if gate A fails, you already have a head start on the rechecks (and same for B->C). If gate A passes, then throw away the results of B and C.21:11
notmynamethis is a pessimistic version of what we have today21:11
markwashsdague: I would love to drill down on that past your warranted frustrations21:12
notmynameidea two: cut down on what's tested21:12
*** vipul-away is now known as vipul21:12
jeblairnotmyname: i would be happy to have zuul start exploring alternate scenarios sooner, even ones heuristically based on observed conditions like job failure rates21:12
jeblairnotmyname: that's not a simple change, so it'd be great if someone wants to sign up to dev that.21:13
jog0proposal 1 doesn't help get things to merge, it just gets them to merge faster21:13
notmynamein this case, there is no need to test the same code for both postgress and mysql functionality (or normal and large ops) if the patch doesn't affect those at all21:13
jog0or fail faster21:13
notmynamejog0: correct. things eventually merge today21:13
jeblairjog0: i agree with that.21:13
notmynamewhere eventually is really long21:13
dolphmjog0: faster dev cycle is always appreciated, at least21:14
portanteand seems too long21:14
notmynamefor idea two, I'm proposing that the set of things that are tested are winnowed down21:14
russellbi'm -1 on testing things less in general ... if things fail, they're broken, and should just be fixed21:14
russellbi don't think the answer to failures is do less testing21:14
jog0notmyname: I am much more concerned about false gate failures then gate delay. if you fix false gate failure you fix gate delay too21:14
notmynameeg why test postgres and mysql functionality in neutron for a glance client test?21:14
jeblairnotmyname: one of the benefits of running extra jobs -- evon ones that don't seem to be needed (testing mysql/pg) is that we do hit nondeterministic failures more often21:14
markmcclainI think testing less items is bad idea too21:15
notmynamein all cases, the nondeterministic bugs need to be squashed21:15
mordredthe gate issues are actual openstack bugs21:15
jeblairnotmyname: neutron was in a bad state for a while because it only ran 1 test whereas everyone else ran 6; it was way more apt to fail changes21:15
jog0I would rather make it harder to get the gate to pass then have these nondetermistic failures leak out into the releases for users to experience21:15
sdaguenotmyname: yeh, we invented more jobs for neutron for exactly that case21:15
*** dcramer_ has quit IRC21:15
markwashto notmyname's point, though. . we just recheck through those failures of actual nondeterministic bugs mostly, do we not?21:16
dolphmjog0: so you're opposed to option 2?21:16
sdagueand I agree that race conditions need to be stompt out21:16
dolphmjog0: err, idea 221:16
markwashrechecking is just *slow* ignoring21:16
jog0dolphm: very much so, we need more tests21:16
notmynamebut the point is, if neutron jobs are still failing a lot, then they don't need to be run for every code repo21:16
notmynames/neutron/whatever/21:16
david-lyle_all projects are gated on those failures, related or not21:16
lifelessuhh21:16
jog0markwash: that is a problem21:16
lifelessI don't follow your logic21:16
sdaguemarkwash: you need to stop thinking about those as non deterministic, they are race conditions21:16
torgomaticit's not a matter of "run less things because they fail", it's a matter of "run less things because they're not needed"21:17
*** ZZelle has joined #openstack-meeting21:17
markwashsdague: agreed, both to me carry the same level of badness (high)21:17
jeblairnotmyname: neutron even got so bad that we pulled it out of the integrated gate -- it pretty much _instantly_ fully broke21:17
mordred++21:17
dolphmwhat's the realistic maximum number of changes openstack has ever seen merge cleanly in succession?21:17
notmynametorgomatic phrased it better than I was doing21:17
dolphm4? 5?21:17
sdaguedolphm: 20+21:17
dhellmanntorgomatic: but they *are* needed because the failures don't occur all of the time, so we need as many examples of failures as possible to debug21:17
jog0dolphm: I saw 10 recently21:17
torgomaticlike, does keystone really need the gate job with neutron-large-ops? I don't think you can break Keystone in such a way as to only hose the large ops jobs21:17
dolphmsdague: wow21:17
ttxdolphm: I witnessed 25 myself21:17
*** sandywalsh_ has joined #openstack-meeting21:17
lifelessnotmyname: if we don't run it, and there is any dependency in that thing on the other projects we let change, we have asymmetric gating.21:17
sdagueit's not been a good couple of weeks21:17
jeblairnotmyname: so we've learned that with no testing, real solid bugs (as opposed to transient ones) land almost immediately in repo.21:17
jog0torgomatic: yes it does21:17
sdaguewe also had a lot of external events in these 2 weeks21:18
lifelessnotmyname: asymmetric gating is a great way to wedge another project entirely, instantly.21:18
ttxdolphm: granted, it was full moon outside.21:18
sdaguesphinx, puppetlabs repo, jenkins splode21:18
jog0both nova and neutron use keystone so it can break neutron-large-ops21:18
mordredyup. we've seen that almost every time we've had assymetric gating21:18
torgomaticjog0: maybe a bad example, then, but there are other cases where the difference between two gate jobs has 0 effect on the patch being tested21:18
dhellmannI would rather spend the effort needed to figure out which subset of all our tests need to be run for any given change to fixing these race conditions themselves21:18
sdaguedhellmann: +121:18
russellbdhellmann: +10021:18
markmcclaindhellmann: +121:18
jeblairdhellmann: +121:19
jog0dhellmann: amen!21:19
* jd__ nods21:19
mordreddhellmann: ++21:19
notmynameok, so option 3: enforce strong SAO-style interaction between projects21:19
sdaguehey, look we even have a reasonable currated list - http://status.openstack.org/elastic-recheck/ - (will continue to try to make it better)21:19
markwashdhellmann: that's obviously better but I hope we *do* it21:19
notmynameEmbrase API contracts between projects. If one project uses another openstack project, treat it as any other dependency with version constraints and a defined API. Use pip or packages to install it. And when a project does gate checks, only check based on that project's tests.21:19
notmynameThis is consistent for what we do today for other dependencies. If there are changes, then we can talk cross-project. That's the good stuff we have, so let's not throw that out.21:19
dhellmannnotmyname: SOA?21:19
lifelessdhellmann: service orientated archivetture21:20
lifelessdhellmann: what we have21:20
notmynameservice oriented architecture. IOW, just have well defined APIs with the commitment to not break it and only use that21:20
lifelessbah, architecture21:20
dhellmannlifeless: I know SOA, I didn't know SAO21:20
jd__you typed SAO :)21:20
lifelessoh lol, my brain refused to notice that21:20
*** nati_ueno has quit IRC21:20
*** d0ugal has quit IRC21:20
russellbso, version pinning between openstack projects?21:20
notmynamesdague: the problem with elastic recheck (which it is good), is that it's hand-currated21:20
russellbseems like we'd just be kicking the "find the breakage" can down the road21:20
mordredrussellb: ++21:20
mordredin fact21:20
sdaguenotmyname: it's 54% of all the fails, and super easy to add another one21:21
mordredwhen you wanted to update the requirement, you would not have been testing the two together21:21
notmynamewell, what happens now for other dependencies? eg we don't run eventlet tests for every openstack patch and vice versa21:21
portanteso then why are we not pulling sphinx builds into our jobs?21:21
sdaguewe approve them super fast21:21
*** BillArnold has quit IRC21:21
markmcclainI don't think we can use pip packages otherwise for projects with strong integration we run into issues landing coordinated patches in the master branches21:21
notmynameor sphinx, as portante stated21:21
mordrednotmyname: those are libraries, not thigns that do SDN21:21
dhellmannthe whole point of gating on trunk is to ensure that trunk continues to work so we can prepare the integrated release, right?21:21
sdaguebecause sphinx isn't openstack21:21
notmynamemarkmcclain: that's exactly my point. it needs strong API contracts21:21
dhellmannfor other dependencies, we should be doing the same gate checks on the requirements project (if we're not already)21:21
mordredit's more tahn an API21:21
notmynamedhellmann: it still woiuld21:21
lifelessnotmyname: we want to run eventlet tests on upstream pull requests actually.21:21
markmcclainnotmyname: those contracts evolve21:22
lifelessnotmyname: thats a test-the-world concept that infra have been kicking around21:22
lifelessnotmyname: so that we're not broken by things like sphinx 1.221:22
notmynamemarkmcclain: of course, that's where deendency versions come from21:22
mordredthe longer we diverge between these projects, the harder re-aligning is going to be21:22
mordredit also makes it REALLY painful for folks running CD from master21:22
markmcclainwe do integrated releases so we should the tests should be intergrated21:23
ttxyes, it's not as if dependencies did not break us badly in the past21:23
russellbmordred: painful as in ... we stop testing that use case completely :(21:23
notmynamemordred: yes. integration is hard, so it needs to be continually done. if something breaks, fix it. what I'm suggesting is that treating the interdependencies as more dcoupled things21:23
mordredrussellb: yup21:23
jog0so one of the problems we have seen is that gate has so many false positives that its very easy for more to sneak in21:23
mordrednotmyname: but they're not21:23
lifelessmmm, from a CD perspective, I don't object to carefully versioned API transitions upstream21:23
jog0we have a horrible base line to compare against21:23
mordredthey're quire interrelated21:23
lifelessbut21:23
lifelessI strongly object to big step integrations21:23
mordredlifeless: ++21:23
portantemordred: how are they not?21:23
notmynamemordred: again, that's why I'm here talking about this today. we've got a problem, and I'm throwing out ideas to help resolve it21:23
mordredbecause these are things with side effects21:24
lifelessif we bump the API a few times a day, that would be fine with me21:24
lifelessbut more than that and we'll start to see nasty suprises I expect21:24
portantethings with side effects sounds kinda general, no?21:24
mordredthere is a reason that side effects are a bad idea in well constructed code - they aren't accounted for in the API21:24
*** zaitcev has joined #openstack-meeting21:24
mordredbut21:24
portantewould notmyname's idea really make things worse than what we have today?21:24
mordredsometimes they're necessary21:24
mordredwhich is why scheme isn't actually used21:24
mordredyes21:25
mordredit would make it worse21:25
mordredunless21:25
markmcclainportante: yes21:25
mordredyou happen to not care about integration21:25
portantehow will it make it worse from what we have today?21:25
mordredif you don't care about integration, it would make your experience as a developer better21:25
mordredportante: define "worse"21:25
notmynamemordred: I didn't see portante say anything about not caring about integration21:25
*** d0ugal has joined #openstack-meeting21:25
*** d0ugal has joined #openstack-meeting21:25
notmyname(ever in fact)21:25
russellbpoint is, that's the case it's not worse21:25
dhellmannrussellb: ?21:26
*** yassine has joined #openstack-meeting21:26
mordrednotmyname: I'm saying that delaying integration until we have larger sets of things to integrate is going to make it more likely to introduce isseus, and harder to track them down when they happen21:26
mordredI believe that will be worse21:26
russellbheh, mordred is saying it's worse, unless you don't care about integration21:26
jeblairnotmyname: because the proposal would mean we would perform integration testing less, essentially only once and on abi bumps.21:26
mordredhowever, doing such a delay21:26
jog0we rarely change APIs21:26
portanteintegration tests would still be run at the same rate21:27
mordredwill increase the pleasurability of folks doing development if those people are not concerned about the problems encountered in integration21:27
dhellmannportante: how so?21:27
mordrednot against combinations that would show you that a patch introduced an issue21:27
*** d0ugal has joined #openstack-meeting21:27
*** d0ugal has joined #openstack-meeting21:27
mordredwhich means that your patch against glance has no way of knowing that it breaks when combined with a recent patch to keystone21:27
mordredwhen neither patches have landed yet21:27
portantewe would still run the same job sets as we do today, that would not change, it just that we would be work with sets of changes from projects instead of individual commits21:27
mordredwhich means you have to BUNDLE all of the possible new patches until there is a new release21:27
mordredwhich means _hundreds_ of patches21:28
jeblairand then bisect those out when you have a problem21:28
*** d0ugal has joined #openstack-meeting21:28
*** d0ugal has joined #openstack-meeting21:28
jog0so I think this whole discussion is looking at things the wrong way. Gate is effectively broken, we don't trust it and its slowing down development.  The solution is to fix the bugs not find ways of running less tests21:28
mordredconsidering that it's hard enough to get it right when we're doing exact patch for patch matching21:28
*** nati_ueno has joined #openstack-meeting21:28
russellbjog0: +121:28
markmcclainjog0: +121:28
portantebut why would my patch break something else without also breaking the API contract?21:28
jeblairjog0: ++21:28
mordredthink about how much worse it will be when you only test every few huundred patches21:28
mordredjog0: ++21:28
dhellmannjog0: +121:29
mordredportante: because it can and will21:29
jog0one thing that would help, is make sure we are collecting good data against master all the time21:29
ttxjog0: I think notmyanme's point is that it cannot ever be fixed so you need new ideas21:29
mordredbecause that's the actual reality21:29
jog0so if we have free resources, run gate against it so we get more data to analyze and debug with21:29
*** d0ugal has joined #openstack-meeting21:29
*** d0ugal has quit IRC21:29
dolphmmordred: ++; it's happened plenty in our history21:29
sdaguejog0: +1 ... so basically the ask back is what do we do (me & jog0 ... as I'm signing him up for this) to get better data in elastic recheck to help bring focus to the stuff that needs fixing21:29
jog0ttx: I am not ready to accept that answer yet21:29
ttxjog0: do you think we can get to the bottom of those issues ?21:29
notmynamettx: no, not that it can't be fixed, per se. but that openstack has grown to a scale where perhaps existing methods aren't as valuable21:29
jog0ttx: yes, it may take a lot of effor but yes21:29
mordredI think the methods are fine21:29
mordredthe main problem is getting people to participate21:30
sdagueyeh, agree with mordred21:30
markwashI think we probably need some sort of painful freeze to draw attention to fixing these bugs21:30
mordredintroducing more slack into the system will not help that21:30
portanteit does not seem to be about adding more slack21:30
sdaguemarkwash: if only developers were feeling some pain.... ;)21:30
torgomaticmarkwash: more pain as the answer to gate pain?21:30
*** d0ugal has joined #openstack-meeting21:30
*** d0ugal has joined #openstack-meeting21:30
mordredthe fact that we al know that jog0 and sdague have been killing themselves on this21:30
mordredis very sad21:30
mordredand many people should feel shame21:30
*** colinmcnamara has joined #openstack-meeting21:30
markwashtorgomatic: yeah, in one big dose, to reduce future gate pain21:30
portantebut targetting a finite set of resources on the point of integration21:30
mordredbecause everyone should be21:30
*** dcramer_ has joined #openstack-meeting21:30
mordredportante: it's batching integration21:31
mordredportante: which is the opposite of continuous integratoin21:31
dolphmwas the idea of prioritizing the gate queue ever shot down? (landing [transient] bug fixes before bp's, for example) or was that just an implementation challenge21:31
mordredand which will be a step backwards and will be a nightmare21:31
portantemordred: if the current system causes developers to assemble large patches unbeknownst to you, isn't that the same thing?21:31
jeblairdolphm: we just added the ability to do that21:31
jog0so we are tracking 27 different bugs in http://status.openstack.org/elastic-recheck/ and that  doesn't cover all the failures. Fixing these bugs takes a lot of effort21:32
sdaguedolphm: we have manual ways to promote now. We've used it recently21:32
dolphmjeblair: oh cool - where can i find details?21:32
*** d0ugal has joined #openstack-meeting21:32
*** d0ugal has joined #openstack-meeting21:32
torgomaticit seems like we're saying that we can leave the gate as-is if we would just stop writing intermittent bugs21:32
jeblairdolphm: we've done it ~twice now; it's a manual process that we can use for patches that are expected to fix gate-blocking bugs, and are limiting it to that for now.21:32
notmynameportante: that's actually my biggest fear. that current gate issues encourage people to go into corners to contribute to forks. which is bad for everyone21:32
sdaguethis is the in progress data to narrow things down furthere - http://paste.openstack.org/show/55185/21:32
*** chistyakolya has joined #openstack-meeting21:32
torgomaticand if we can stop doing that, let's just stop writing bugs at all and throw the gate out21:32
mordrednotmyname: what forks?21:32
mordrednotmyname: what forks of openstack are there?21:32
dolphmjeblair: is the process to ping -infra when we need to land a community priority change then?21:33
mordrednotmyname: and which developers are hacking on them?21:33
jeblairdolphm: yes21:33
dolphmjeblair: sdague: easy enough, thanks!21:33
hub_capmordred: maybe internal "forks" cuz patches take a while to land?21:33
* hub_cap guesses21:33
markwashmordred: I guess many companies run private forks21:33
portantemordred: no names,  dont' want the nsa to take them out. ;)21:33
mordredportante: ;)21:33
notmynamehub_cap: yes. but to portante's point, it happens privately21:33
hub_capportante: the nsa knows already21:33
markwashguesses the nsa runs a fork :-)21:33
mordredwell, those companies usually learn pretty quickly21:33
portanteits does!?21:33
creihtwhat company doesn't have a fork of every openstack component as they try to get features in?21:33
russellbprivate forks seem natural21:33
torgomaticalternately, we can accept that bugs happen, including intermittent bugs, and restructure things to be less annoying when they do21:34
mordredthat getting out of sync signficantly is super painful21:34
* portante smashes laptop on the ground21:34
russellband honestly just seems like FUD21:34
notmynametorgomatic: yes!21:34
* jd__ smells FUD21:34
jog0many of the bugs we see in gate are really bad ones21:34
russellbjd__: jinx21:34
jd__raaah21:34
markwashportante: lol21:34
sdagueyeh, a lot of these races are pretty fundamental things21:34
* mordred hands portante a new laptop that he promises has no malware on it21:34
*** d0ugal has joined #openstack-meeting21:34
*** d0ugal has joined #openstack-meeting21:34
sdaguewhere compute should go to a state... and it doesn't21:34
* portante thankful for kind folks with hardware21:35
ttxthe tension is because some developers are slowed down by issues happening in other corners of the project and over which they have limited influence21:35
torgomaticto that end, I think notmyname's first two suggestions are both good ones21:35
russellbttx: and the dangerous response is to continue not to care what's happening in the other corners21:35
lifelesswe're all in this together :)21:35
jeblairttx: they don't have limited influence though21:35
russellblifeless: yes!21:35
portantecan we at least run experiments with the suggestions to play them out?21:35
*** d0ugal has joined #openstack-meeting21:36
*** d0ugal has joined #openstack-meeting21:36
sdaguehonestly, in the past we keep going in cycles where gate gets bad, pitch forks come out, people work on bugs, it gets better21:36
ttxbut if you take the viewpoint of openstack as a whole, some parts may be slowed down, but the result is better in the end21:36
sdaguethis time... the number of folks working these bugs isn't showing up21:36
russellbportante: which ones?  #2 and #3 there were fundamental disagreements from many people21:36
sdaguewhich is really the crux of the problem21:36
markwashone policy that might help: as we triage a race-condition based failure in the gate, we need to require unit / lower level / faster tests that reproduce those failures to land in the projects themselves and fail every time21:36
*** d0ugal has joined #openstack-meeting21:36
*** d0ugal has quit IRC21:36
*** d0ugal has joined #openstack-meeting21:36
jeblairi hit a transient bug on a devstack-gate change, and with some help from sdague we tracked it down to a real bug in keystone, i filed the bug, wrote an er query and moved on21:36
russellb#1 jeblair invited some help to zuul dev to add21:36
jeblairi think that was beneficial to the project21:36
lifelessso I proposed that gate affecting bugs be critical by default21:36
jog0markwash: that won't work many times we don't know why something is breaking21:37
*** d0ugal has joined #openstack-meeting21:37
*** d0ugal has joined #openstack-meeting21:37
lifelessI think the stats we have here suggest that perhaps that isn't a bad an idea as folk thought :)21:37
portanteit is okay to disagree, can't hurt to try a few things to see they pan out21:37
russellbcan someone ban d0ugal?  the join/parts are really annoying21:37
jeblairand i was glad i could help even though i knew that my shell script change to devstack-gate didn't cause it.21:37
ttxrussellb: I use them as a clock21:37
jog0take the http2 lib  file descriptor bug21:37
creihtwhat if we just turn off the gate for a specific project until they fix the bugs that are clogging it?21:37
markwashjog0: ah, okay. .yeah its only for bugs where we understand the race but its hard to fix21:37
dolphmttx: rofl. russellb: can your client hide join/parts?21:37
markwashcreiht: +121:37
*** chistyakolya has quit IRC21:37
russellbdolphm: probably, but i don't want to hide the non broken ones21:37
creihtwell prevent the project from any further patches until they fix gate critical bugs21:38
markmcclaincreiht: that is a bad idea… we've done this before and it caused more problems than it solved21:38
*** d0ugal has joined #openstack-meeting21:38
*** d0ugal has quit IRC21:38
*** d0ugal has joined #openstack-meeting21:38
*** d0ugal has quit IRC21:38
jeblairlifeless: ++critical21:38
creihtmarkmcclain: my first explanation wasn't as clear sorry21:38
russellbheh, and now we have a pile of critical bugs that the same small number of people are looking at21:38
dolphmcreiht: not sure i follow - block that project from being tested or block that project from landing irrelevant changes?21:38
russellbjust saying, that alone doesn't get people to work on them :)21:38
creihtblock from landing any changes until the critical bugs are fixed21:38
*** dprince has quit IRC21:38
lifelessrussellb: sure, but can't we also say 'when there are critical bugs, we won't be reviewing or landing anything else' ?21:38
lifelessrussellb: like, make it really crystal clear that these things are /what matters/21:39
*** d0ugal has joined #openstack-meeting21:39
*** d0ugal has joined #openstack-meeting21:39
russellblifeless: sure, something, just saying that labeling things critical doesn't do anything by itself21:39
ttxcreiht: I think we have that option, yes21:39
lifelessrussellb: ack, agreed.21:39
jeblairmarkmcclain: you've done that once or twice, right?  prioritized critical fixes to the exclusion of other patches?21:39
dolphmidea: can http://status.openstack.org/rechecks/ be redesigned so that you can see the most impactful bugs per project the associated bugs are tracked against?21:39
ttxcreiht: if we can really identify a project that doesn't play ball21:39
*** briancline has quit IRC21:39
russellbdolphm: have you seen http://status.openstack.org/elastic-recheck/ ?21:39
dolphmit's impossible for me to glance and that page and see where i can help21:39
sdaguedolphm: yes, moving towards eliminating it with the elastic recheck dashboard21:40
markmcclainjeblair: yes.. we blocked approvals until fixes landed21:40
jog0dolphm: keystone doesn't have any gate issues as far as I know21:40
*** d0ugal has joined #openstack-meeting21:40
*** d0ugal has joined #openstack-meeting21:40
dolphmrussellb: yeah, that's not what i want either21:40
sdagueit just... takes time21:40
dolphmjog0: understood, but still21:40
jeblairsdague, dolphm: ++21:40
clarkbjog0: it does21:40
clarkbthe port issue21:40
sdaguejog0: that's not true21:40
creihtttx: it isn't about playing ball... if there are critical bugs blocking the gate, then your project gets no new patches in until that bug is fixed21:40
jog0clarkb: link21:40
sdagueit bounced stuff this morning21:40
jeblairdolphm, jog0: and the keystoneclient issue we found yesterday21:40
dolphmjog0: actually we do have a couple issues ;)21:41
portantecreiht: if there are critical bugs blocking the gate from your project, then your project ....21:41
creihtyes21:41
jog0in that case I think most integrated projects have critical bugs21:41
jog0if not all21:41
portantegreat, so let's do that creiht thingy then21:41
creihtlol21:41
markwashI mean, maybe they all need to stop and fix those21:41
ttxcreiht: in some cases it's not as binary as that. Some bugs take time to investigate/reproduce, and blocking the project that makes progress on them is probably not very useful21:41
lifelessttx: so, I disagree21:42
torgomaticthat approach acknowledges that bugs happen, so it's got that going for it21:42
creihtttx: it seems more usefull then just letting status quo go on21:42
lifelessttx: when you make changes there is a chance you introduce new bugs right ?21:42
lifelessttx: or make the current ones worse!21:42
markwashrace condition bugs are a good situation for tough love21:42
portantenothing changes if nothing changes21:42
*** d0ugal has joined #openstack-meeting21:42
*** d0ugal has joined #openstack-meeting21:42
notmynamewell, that brings up another point. elastic-recheck doesn't do any alerting to a project. maybe that shoudl be added21:42
sdaguenotmyname: agreed21:42
lifelessttx: so if you have critical issues, changing things that aren't fixing that issue, is just fundamentally a bad idea.21:42
*** dvarga has quit IRC21:42
jeblairnotmyname: sounds like a good idea21:42
*** d0ugal has joined #openstack-meeting21:43
*** d0ugal has joined #openstack-meeting21:43
russellbor perhaps an openstack-dev email for each bug that gets added?  or would that be too much?21:43
portantepublic flogging?21:43
lifelessmight be too little21:43
russellbheh21:43
jog0notmyname: so one issue is many times we don't know which project the bug is in21:43
sdaguewe were talking about that, if we can determine the project, or set of projects where the bug is, it should alert those channels whenever it fails a patch21:43
ttxok, I think we are not maling anymore progress now21:43
ttxor making21:43
sdagueso people shamed into how often they are breaking things21:43
notmynameso what's next, then?21:44
notmynamettx: ^21:44
lifelessI don't think shame really helps21:44
creihtstatus quo!21:44
creiht:)21:44
lifelessnoone wanted to introduce these bugs21:44
markmcclainthe downside of public is shaming is that sometimes the initial point of fault could be incorrect21:44
russellbwhat's next?  how to get more people helping fix bus?21:44
russellbbugs*21:44
lifelessright!21:44
*** d0ugal has joined #openstack-meeting21:44
*** d0ugal has joined #openstack-meeting21:44
ttxpractical actions21:44
russellbcontinued work to raise awareness of the most impotant things is part of it21:44
jog0russellb: agreed21:44
markwashyeah, not about shame, just about how do we progress when there are criitcal bugs21:44
russellband i think some ideas are being tossed around for that right now21:44
lifelessis everyone raising their gate critical bugs in each weekly meeting ?21:45
russellband then what hammers are available when not enough progress is made, and when we do we use them21:45
ttxnotmyname: I think everyone agreed your suggestion 1 was interesting, just missing dev manpower to make it happen21:45
russellband i'm not sure we have good answers for that part yet21:45
*** d0ugal has joined #openstack-meeting21:45
*** d0ugal has quit IRC21:45
*** d0ugal has joined #openstack-meeting21:45
lifelessLike as a dedicated section? And getting volunteers to work on them ?21:45
ttx(the multigate thing)21:45
markmcclainlifeless: it's the 1st real item in our meeting each week21:45
torgomaticsome of us are giant fans of suggestion 2 as well21:45
*** neelashah has quit IRC21:45
*** d0ugal has quit IRC21:45
*** d0ugal has joined #openstack-meeting21:45
*** d0ugal has joined #openstack-meeting21:45
torgomatic(suggestion 2 is removing redundant gate jobs)21:46
*** d0ugal has quit IRC21:46
markmcclaintorgomatic: no the extra data points are very helpful for diagnosing some the race conditions21:46
lifelesstorgomatic: what redundant jobs?21:46
ttxI think that one was far from consensual21:46
*** d0ugal has joined #openstack-meeting21:46
markmcclainit also helps us to prioritize based on frequency21:46
markwashI think we should just have a post-gate master integration job that is wired up to a thermonuclear device. . when the failure rate hits 50% it blows21:46
*** thomasbiege has joined #openstack-meeting21:46
lifelessmarkwash: sweet21:46
russellbttx: if anything, more consensus on "no" for 2 and 3 IMO21:46
*** termie_ is now known as termie21:46
torgomaticlifeless: like running devstack 5 times against every project, when there's not always a way for that project's patches to break stuff21:47
*** termie has quit IRC21:47
*** termie has joined #openstack-meeting21:47
torgomaticwell, not only for one21:47
torgomaticI meant to say21:47
lifelesstorgomatic: yes, your analysis is missing something21:47
lifelesstorgomatic: which we disucussed21:47
jog0https://bugs.launchpad.net/openstack/+bugs?search=Search&field.importance=Critical&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress&field.status=Fix+Committed21:47
russellbdon't want to rehash it21:47
lifelesstorgomatic: whic his that the break relationship is often bidirectional, and transitive.21:47
torgomaticas in, I'm sure I can write a Swift patch that breaks devstack for everything, but I cannot write one that only breaks devstack-neutron-large-ops21:47
jog0117 critical bugs21:47
jog0torgomatic: yes you can21:47
torgomaticjog0: great, please provide an existence proof in the form of a patch21:48
lifelesslets get out of the rabbit hole21:48
jog0put some timeouts in swift to make things super slow for glance21:48
lifelessback to how do we get more people working on  critical bugs21:48
jeblairbtw, some projects have started tagging bugs with 'gate-failure' which can help folks searching for these bugs21:48
sdaguejog0: yuo probably want to remove git committed21:48
markwashs/git/fix/21:49
russellbwhich brings it to 4421:49
ttxlifeless: suggestions ?21:49
*** sayali has joined #openstack-meeting21:49
lifelessjog0: that includes non integrated project21:49
ttxWe shall soon move on to the rest of the meeting content21:49
*** d0ugal has joined #openstack-meeting21:49
jog0lifeless: yeah, do you have a better link?21:49
lifelessjog0: not in time for the meeting21:50
lifelessjog0: LP limittion21:50
ttxI see no reason why we can't continue to discuss this on the ML, btw21:50
ttxEveryone agrees it's an issue21:50
ttxJust absence of convergence on solutions21:50
russellblet's fix it, and not by doing less testing of the continuous or the integrated varieties.21:50
*** thomasbiege has quit IRC21:51
ttxexcept suggestion 1 which was pretty consensual21:51
ttxjust missing resources to make it happen21:51
*** jasondotstar has quit IRC21:51
sdagueyeh, that's going to require dev resources on zuul21:51
sdaguebut jeblair said he'd be happy to entertain those adaptive algorithms21:52
jeblairand it's worth remembering, that's just speeding up the failures.21:52
jog0so I am not too keen on the first idea21:52
jog0actually21:52
*** briancline has joined #openstack-meeting21:52
jog0I think we can use the compute and human resources much better21:52
russellbjog0: I don't think it hurts, while the others arguably do hurt21:52
jog0if we fix gate issue one goes away21:52
sdaguewell honestly, it also requires effort21:52
jeblairrussellb: ++21:52
sdagueso if someone is signing up for it, cool. If people are just "someone else should do it" then it won't happen21:52
*** MaxV has joined #openstack-meeting21:53
markwashit seems like idea #1 is just tuning the existing optimizations we have in place, not sure why it would be bad if someone showed up with a patch?21:53
russellblike most things :)21:53
ttxok, 7 minutes left let's move on21:53
*** bknudson has quit IRC21:53
*** rnirmal has quit IRC21:53
ttx#topic Red Flag District / Blocked blueprints21:53
*** openstack changes topic to "Red Flag District / Blocked blueprints (Meeting topic: project)"21:53
*** ryanpetrello has quit IRC21:53
russellbi like this new cross project meeting style :)21:53
russellbwe never had time for stuff like this before21:53
portanteexciting21:53
ttxNo blocked blueprint afaict21:54
ttxrussellb: yes, we used to put that dust under carpets21:54
ttxat least we now voice the anger21:54
*** bknudson has joined #openstack-meeting21:54
ttx"put the dead fish on the table"21:54
* markwash googles21:54
notmynamettx: I don't think "anger" is the right word21:54
* jeblair thinks a failed patch in the queue should be called a dead fish21:55
russellbjeblair: so the red circle in the zuul status page should be a dead fish instead?21:55
notmynameI think there is frustration, but there is quite a bit of grace given to the current state of things by those who are frsustrated21:55
ttxwe still have a conflict between heat and keystone around service-scoped-role-definition21:55
jeblairrussellb: with little stink lines21:55
ttxnotmyname: yes, frustration ius a better term, sorry21:55
ttxheat/management-api still needs keystone/service-scoped-role-definition21:56
*** ohnoimdead has joined #openstack-meeting21:56
ttxstevebaker, dolphm: did you solve it ?21:56
stevebakerttx: that dep should be removed21:56
dolphmi followed up on that last week - heat really shouldn't be blocked on that21:56
ttxstevebaker: ah, great21:56
dolphmalthough heat *could* take advantage of it- and i understand the desire to21:56
stevebakeri thought I did that21:56
creihtnotmyname: well said21:56
ttxstevebaker: yep it's removed now, thx21:57
*** kspear has joined #openstack-meeting21:57
ttxAny other blocked work that this meeting could try to help unblock ?21:57
ttxI'll take that as a "no"21:58
ttx#topic Incubated projects21:58
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:58
ttxdevananda, kgriffs, SergeyLukjanov: around ? any question ?21:58
*** tzumainn has joined #openstack-meeting21:58
SergeyLukjanovttx, I'm here21:59
SergeyLukjanovttx, no questions atm21:59
*** zaitcev has left #openstack-meeting21:59
kgriffsno questions here21:59
devanandaaside from wondering how much slower development on ironic will be when we get integration testing .... nope :)21:59
*** jcoufal has joined #openstack-meeting21:59
kgriffs+1 for raising the bar on code quality21:59
SergeyLukjanovttx, first working code of heat integration already landed, waiting for reviews on tempest patches21:59
ttxkgriffs: had a question for you about when you wanted to switch to release amnagement handling your milestones21:59
kgriffsah, great question22:00
kgriffstbh, I don't have a good feel for what that entails22:00
ttxI see your i1 is still open22:00
ttxkgriffs: we should talk. Will ping you tomorrow ?22:00
kgriffshmm. Thought I closed it.22:00
* kgriffs hides22:00
kgriffsttx: sounds good22:00
ttxkgriffs: it's inactive but it looks in progress :)22:00
kgriffsI've been trying to move closer to tracking the i milestones, so this is timely22:00
kgriffsttx: oic22:01
ttxkgriffs: awesome, talk to you tomorrow22:01
kgriffskk22:01
*** nati_uen_ has joined #openstack-meeting22:01
*** thingee has joined #openstack-meeting22:01
ttxand.. time is up22:01
ttx#endmeeting22:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:01
openstackMeeting ended Tue Dec 17 22:01:16 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2013/project.2013-12-17-21.03.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2013/project.2013-12-17-21.03.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2013/project.2013-12-17-21.03.log.html22:01
ttxThanks everyone22:01
*** portante has left #openstack-meeting22:01
david-lyle_#startmeeting Horizon22:02
openstackMeeting started Tue Dec 17 22:02:02 2013 UTC and is due to finish in 60 minutes.  The chair is david-lyle_. Information about MeetBot at http://wiki.debian.org/MeetBot.22:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:02
*** openstack changes topic to " (Meeting topic: Horizon)"22:02
openstackThe meeting name has been set to 'horizon'22:02
jcoufalo/ hi22:02
lsmola_hello22:02
david-lyle_Hello everyone22:02
jtomasekhi22:02
jpichhey22:02
kspearhowdy22:02
ohnoimdeado/22:02
lblanchardhi all22:02
MaxVhi22:02
mrungeo/22:02
tzumainnhiya22:02
*** Toshi has joined #openstack-meeting22:02
*** nati_uen_ has quit IRC22:03
david-lyle_full house today, excellent22:03
*** SumitNaiksatam has joined #openstack-meeting22:03
*** hewbrocca has joined #openstack-meeting22:03
ohnoimdeadwoot22:03
david-lyle_https://launchpad.net/horizon/+milestone/icehouse-222:03
*** branen has quit IRC22:03
*** nati_ueno has quit IRC22:03
*** nati_uen_ has joined #openstack-meeting22:03
david-lyle_just wanted take a quick look at the i-2 milestone22:03
*** kgriffs has left #openstack-meeting22:03
david-lyle_things are progressing well and most things seem to be on track22:04
*** thomasbiege has joined #openstack-meeting22:04
*** dstanek has quit IRC22:04
david-lyle_lots of review opportunities :)22:04
david-lyle_And things that have been merging have been slowed a bit by gate difficulties, so let's remain patient and work these items through22:04
david-lyle_Does any one have any concerns or questions re: i-222:05
david-lyle_?22:05
*** dougshelley66 has quit IRC22:05
*** colinmcnamara has quit IRC22:05
david-lyle_I'll take that as a no22:06
mrungeI see still a huge bunch of unreviewed patches22:06
mrungegah, too late ;-)22:06
david-lyle_no worries22:06
*** jroovers has joined #openstack-meeting22:06
*** pdmars has quit IRC22:06
ohnoimdeadgot through some reviews last week, will try to do more this week prior to holiday break22:06
lsmola_me too22:06
lsmola_we have to tame the review beast22:07
mrungeI'd like to encourage all of you to do more reviews!22:07
david-lyle_I think we have ~10 bps close to landing, just a few more iterations on reviews22:07
david-lyle_so let's keep on them22:08
*** jeckersb is now known as jeckersb_gone22:08
*** thomasbiege has quit IRC22:08
david-lyle_Speaking of review load, I officially added tmazur to the horizon core list and retained ohnoimdead, as he expressed a strong interest and started reviewing again.22:09
*** ArxCruz has joined #openstack-meeting22:09
david-lyle_So welcome tmazur and thanks ohnoimdead22:09
mrungewelcome both!22:09
jpichCool, thanks tmazur and ohnoimdead22:09
lsmola_welcome :-)22:09
mrunge*greatly appreciated*22:09
jcoufalwelcome ;)22:09
jpichIt's nice to also have people around with more historical knowledge of the code :)22:10
ohnoimdeadhella!22:10
*** markmcclain has quit IRC22:10
david-lyle_absolutely22:10
ohnoimdeadi'm old TT22:10
*** jdob has quit IRC22:11
jpichWise and experienced ;)22:11
lsmola_:-)22:11
david-lyle_ok, on to the planned agenda https://wiki.openstack.org/wiki/Meetings/Horizon22:11
david-lyle_#topic Meeting Time22:11
*** openstack changes topic to "Meeting Time (Meeting topic: Horizon)"22:11
david-lyle_So the was a thread on the dev mailing list about more diverse timezone friendly meeting times22:12
david-lyle_I know I have talked with some of you before about this22:12
mrungeyes...22:12
jpichWas that a horizon-meeting-specific thread?22:12
david-lyle_I think our core team now covers enough timezones that finding one ideal time is going to be impossible22:13
*** DennyZhang has joined #openstack-meeting22:13
mrungeif we could move the meeting one or two hours earlier, I suspect tmazur could make it easier22:13
david-lyle_jpich: no openstack-dev in general22:13
jcoufalwould be great if we can move times22:13
jpichdavid-lyle_:  ok, thanks, thought I missed it22:13
david-lyle_Then amotoki and kspear have no chance22:13
jpichmrunge: but then we lose APAC22:13
kspearit's 9am at the moment22:13
jcoufalhere it's 11pm22:14
kspearfor me, but daylight saving will make it earlier...22:14
lsmola_david-lyle: true, e.g. Ceilometer uses two times22:14
jpichI think it's at 6 or 7am for amotoki at the moment22:14
jcoufaldaylight will make it 00:00 for us :(22:14
*** davidhadas_ has quit IRC22:14
mrungejpich, imho that discussion was arount summit time...22:14
jpichOk22:14
mrungekspear, currently, it's 23:14 for me22:14
MaxVsame22:14
lsmola_same22:15
mrungeand summer time, it will move later22:15
david-lyle_so, I would be open to having a moving time or other suggestions22:15
jpichPersonally, at the moment the meeting time is ok for me but when DST is on again it's really harder22:15
david-lyle_I'm open to suggestions, because I have it the easiest right now22:15
lsmola_:-)22:15
mrungemoving 1 hour earlier will make this meeting collide with the general meeting....22:15
jcoufal2h earlier will be really hard for kspear22:16
jpichSounds like a discussion/vote to have on list :) So people who can't attend right now because the timing sucks can chime in22:16
david-lyle_1 hour earlier, I can't do22:16
lblancharddo we have any US West coasters?22:16
kspearcould we all add our tz to some online tool to get a better idea of things?22:16
lsmola_what about two times, repeating every two weeks?22:16
mrungeif we're up to move it earlier, then we need to pick another day22:16
david-lyle_lcheng is typically on the west coast22:16
mrungekspear, good idea22:16
*** d0ugal has quit IRC22:17
lblanchardwhat if we targeted morning time for EST like 9am…it would be 9pm-ish in APAC areas22:17
lblanchardah okay22:17
* kspear can't remember the name of any though22:17
lblanchardthat would be tough for west coasters :)22:17
jcoufalthen west coast is out22:17
*** ruhe has quit IRC22:17
markwashlblanchard: that's what glance does, it jsut means I have to get up at 6AM on standard time and 7AM on daylight savings22:17
jpichlsmola's and the ceilometer folks way to do it is probably the best, or would certainly be interesting to try (alternating meeting times)22:17
mrungelet's collect times, to get a better idea, and then take this to another meeting?22:18
lblanchardmarkwash: thanks! 6am is pretty darn early for me…but maybe it would work for some?22:18
lsmola_david-lyle: yep https://wiki.openstack.org/wiki/Meetings/MeteringAgenda22:18
*** markmc has quit IRC22:18
lblanchardmrunge: what is  that tool that alvaro has used?22:18
lblanchardjpich: ^22:18
jpichAgreed with mrunge, let's move it to the list, that won't be resolved here. Most people seem happy to consider a change22:19
david-lyle_mrunge, good idea, let's leave the meeting time topic on the agenda page and just have people add their tz there22:19
jpichdoodle?22:19
lsmola_david-lyle: this way all people can be here at least once in two weeks22:19
mrungelblanchard, on fedora, we took whenisgood, but doodle does the  jobs as well22:19
lblanchardyeah, I was thinking of this: http://www.doodle.com/22:19
david-lyle_or that works if someone will take the item to set it up22:19
lsmola_jpich: alternating seems like a good idea22:20
jcoufallet's start the thread in ML to gather timezones and then we can set up doodle with concrete proposals22:20
lblancharddavid-lyle: I can set up a doodle and share it with the ML22:20
mrungewould it be sufficient to check for 2 hour slots?22:20
*** pcm has quit IRC22:20
mrungelblanchard, thank you!22:21
david-lyle_thanks lblanchard22:21
lsmola_lblanchard: thank you :-)22:21
lblanchardnp!22:21
david-lyle_#topic Tuskar-ui Code Merge Plan22:21
*** openstack changes topic to "Tuskar-ui Code Merge Plan (Meeting topic: Horizon)"22:21
lsmola_so, I have sent 2 email with 2 plans22:22
david-lyle_lsmola sent a proposal that the tuskar-ui group created and then we readily stomped on it, discuss22:22
david-lyle_:)22:22
lsmola_:-)22:22
*** d0ugal has joined #openstack-meeting22:22
*** d0ugal has quit IRC22:22
lsmola_seems we are leaning to codebase merge22:23
lsmola_though we have some worries22:23
lsmola_do you want to sum it up jcoufal or should I?22:23
david-lyle_lsmola, is the main concern re: core and reviews?22:23
jcoufaldavid-lyle_: yeah22:23
jcoufalin few words22:23
lsmola_david-lyle: yeah, basically we need enough attention :-)22:23
david-lyle_that's how many I can understand22:24
jcoufaltuskar-ui needs to be developed quickly, we have only 2 motnhs and the goal is to deliver functional installer22:24
jcoufalwhich is lot of work22:24
jcoufalwhich we are willing to do22:24
david-lyle_ok, my thoughts are you are currently gated by horizon for the ui toolkit22:24
lsmola_david-lyle: lets say we have like 5 high priority tasks, that needs to be done by I3, so we have the deployment and manah=gement story upstream wants22:24
david-lyle_I think that part remains with either proposal for now22:25
*** d0ugal has joined #openstack-meeting22:25
*** d0ugal has joined #openstack-meeting22:25
lsmola_david-lyle: will it be possible to remain high priority also when we are in Horizon?22:25
david-lyle_I would be open to merging the core teams and letting the existing tuskar-ui core team +2 changes in that area of the code22:25
david-lyle_to begin with22:25
lsmola_david-lyle: ok that would be great22:26
david-lyle_I understand the need for agility in what is an incubating project, I don't see a need to block that22:26
tzumainndavid-lyle, so the two-company policy of approvals would be suspended for the tuskar-ui code?22:26
david-lyle_yes22:26
jtomasekdavid-lyle: how about the "multiple companies rule"?22:27
david-lyle_I think it has to be22:27
jcoufaldavid-lyle_: we would like to keep cross-company reviews, so the only concern is if we can get enough attention22:27
jtomasekok22:27
jpichPersonally I would have concerns about just merging the core teams. The first proposal suggested having a separate team to work on the tuskar-ui code, to begin with (if i understood correctly)22:27
david-lyle_I'm honestly not sure how to accomplish that jpich22:27
mrungejpich that would imply to have a separate code base22:27
*** yassine has quit IRC22:28
lsmola_jpich: yes22:28
lsmola_it would be only a small step forward22:28
david-lyle_I would like to get to the point of doing cross-company reviews for tuskar-ui, but I honestly don't feel comfortable enough at this point to place that requirement on me or other un-familiar cores22:28
jpichMy understanding of the first proposal was that tuskar-ui would be in its own repository like now, except under the Horizon program - I was told that there could be a core team just for this, to begin with22:28
mrungedavid-lyle, yes, I'd love to do that22:28
lsmola_jpich: yes22:28
mrungeor to see that22:29
jpichlsmola_: Thanks for confirming :-)22:29
jcoufaldavid-lyle_: it sounds reasonable if everybody agrees, we can move to cross-company reviews in time22:29
david-lyle_we could also do that, jpich.  I think the open question then for tuskarui is why move?22:29
*** boris-42 has quit IRC22:29
*** d0ugal has joined #openstack-meeting22:29
*** d0ugal has joined #openstack-meeting22:29
mrungedavid-lyle, I have discussed this with the tuskar guys earlier22:30
jpichTuskar is based on Horizon22:30
tzumainndavid-lyle, one reason might be - right now lifeless feels responsible for our code, but it's difficult for the tripleo cores to evaluate horizon-based code22:30
*** d0ugal has joined #openstack-meeting22:30
*** d0ugal has joined #openstack-meeting22:30
*** ZZelle has quit IRC22:30
jpichAnd when the project is integrated and has less of a requirement for turbo-velocity, we can work together on merging it into the main horizon codebase22:30
mrungeand I don't see a benefit for horizon nor for tuskar just to move to another separate repository22:30
tzumainnmrunge, regarding that, I should ask - our development is currently somewhat horizontal - starting at the api layer, and working its way up22:31
mrungejpich, that would mean just to keep it like it is right now22:31
lsmola_david-lyle: well It could be a blocker if cores won't approve our patch because, they can't setup dev env22:31
*** d0ugal has joined #openstack-meeting22:31
*** d0ugal has joined #openstack-meeting22:31
tzumainnthe code would probably run off mock data for the immediate future22:31
tzumainnis that sort of code acceptable within horizon?22:31
lsmola_mrunge: well that is the third and easiest plan to do :-D22:32
*** d0ugal has joined #openstack-meeting22:32
*** d0ugal has joined #openstack-meeting22:32
* david-lyle_ torn22:32
jpichmrunge: the benefit would be that it gives us time to get used to the code, and the tuskar team to get more used to what the horizon core folks look for in reviews (we've seen pretty strong disagreements on the general horizon direction before...)22:32
lsmola_:-)22:32
mrungejpich, honestly?22:32
mrungewho would do that?22:33
mrungeif we aren't forced to do so?22:33
lsmola_well22:33
jpichmrunge: It would be different because tuskar ui would be the responsibility of tuskar-ui core + horizon core, instead of  tuskar-ui core + tripleo core, which seems to be a better match22:33
lifelessFWIW if david-lyle_ and the existing horizon cores are happy with a single code base and merging -core I think thats fantastic22:33
mrungeso jpich, why don't merge?22:33
*** nermina has quit IRC22:33
*** elo1 has quit IRC22:33
*** d0ugal has joined #openstack-meeting22:34
*** d0ugal has joined #openstack-meeting22:34
*** elo has joined #openstack-meeting22:34
*** esker has quit IRC22:34
mrungeI'd love to see tuskar as tight as possible integrated into horizon codebase22:34
david-lyle_mrunge, I think the concern would be we'd be managing it a bit like two code bases at the beginning22:34
jcoufalPersonally I think it makes more sense to be part of one codebase22:34
lsmola_david-lyle: well the good thing about merge now is, it will be easy, we don't have almost any code after the cleanup22:34
david-lyle_using artificial means22:34
david-lyle_I think we're all capable of doing that22:35
jtomaseklsmola_: +122:35
mrungedavid-lyle, I'd rather treat tuskar as normal code, without any other *special handling* at all22:35
lsmola_david-lyle: true, it's undercloud vs. overcloud right now22:35
lsmola_david-lyle: so for the main functionality, the priorities wont be the same22:35
*** ItSANgo__ has quit IRC22:36
*** d0ugal has joined #openstack-meeting22:36
*** d0ugal has joined #openstack-meeting22:36
tzumainnmrunge, which brings me back to a question - is code that doesn't fully work okay to be accepted into horizon?22:36
jpichI think it makes sense to be part of one codebase once the project is integrated and we have similar requirements across the whole codebase (e.g. no more need for single company approval)22:36
kspearone issue is we're expanding horizon's scope to include incubated projects22:36
mrungetzumainn, I'd say: yes22:36
lsmola_mrunge: well you can see the infrastructure tab as a place where you manage a very special application you have deployed by heat22:36
mrungekspear, we did with trove22:36
kspearwhich means core has less time to spend on core projects22:36
*** dougshelley66 has joined #openstack-meeting22:36
kspearmrunge: and that didn't go well at all imo22:36
jpichmrunge: Trove was an exception because the code was all there and ready afaiui22:37
*** Toshi has quit IRC22:37
*** oubiwann has joined #openstack-meeting22:37
*** d0ugal has joined #openstack-meeting22:37
*** d0ugal has joined #openstack-meeting22:37
mrungekspear, trove didn't built on horizon22:37
mrungenor is it tightly integrated22:37
tzumainnI kinda agree with jpich - tuskar-ui is in a teardown and re-build state, and I feel like it'll be hard to evaluate for non-tuskar-ui people22:37
mrungebut agreed. it could have worked better22:37
jcoufaltzumainn: jpich: +122:38
lifelessI think the key question isn't about the code state; its about what works better for everyone22:38
*** nermina has joined #openstack-meeting22:38
mrungelifeless, +122:38
lsmola_lifeless: though seems like that is hard to find :-)22:38
mrungeok, when we don't merge more or less now, when do we have the next chance?22:38
jcoufalyeah, the only concern here is if we can get the code in quickly for tuskar-ui22:38
*** d0ugal has joined #openstack-meeting22:39
*** d0ugal has joined #openstack-meeting22:39
*** d0ugal has quit IRC22:39
mrungeand what will we get then?22:39
lifelesswhich david-lyle_ seemed ok to facilitate:)22:39
david-lyle_So the tuskarui folks think it's better to remain split, horizon-core seems split22:39
mrungea finished product?22:39
*** d0ugal has joined #openstack-meeting22:39
*** d0ugal has quit IRC22:39
*** d0ugal has joined #openstack-meeting22:39
jcoufaldavid-lyle_: I don't think that tuskarui folks think it's better to remain split22:39
david-lyle_I thought that was the proposal22:40
lsmola_david-lyle: well we would like to merge, though we need attention :-)22:40
jpichmrunge: The first proposal also said horizon core would be core for that project, it's up to us to get/keep up to date with it22:40
david-lyle_per dev ml22:40
jpichThere was a 2nd proposal sent about 12h ago as well22:40
lsmola_david-lyle: it would been healthier to build it under horizon cores eyes :-)22:40
* david-lyle_ throws hands up22:40
lsmola_hehe22:40
* jomara is late to the conversation22:41
tzumainnlsmola_, but if we aren't enforcing the multi-company reviewer rule, then what's the point?22:41
lsmola_tzumainn: well we are, that is why we need the attention22:41
tzumainnlsmola_, oh, are you saying you'd prefer a full merge, with the same reviewer rule that horizon uses, but we'd need a guarantee from horizon-cores that we'd get the appropriate attention?22:41
jtomaseklsmola_: tzumainn: I don't see what is the problem with what david-lyle offers22:42
david-lyle_how did I miss that email22:42
lsmola_tzumainn: yeah something like that I guess22:42
jpichI don't think anyone can reasonably guarantee that22:42
tzumainnjpich, yeah, I agree - which is why I don't think that plan will work22:42
lsmola_david-lyle: there is a lot of emails22:42
jcoufaldavid-lyle_: can we say that we merge, and we want to try to keep cross-company reviews? would it be possible? ask horizon-cores to keep eye on the code that it makes sense from horizon point of view (they don't have to check how it works in sense of tripleo from the beginning, but they will get there)22:42
tzumainnjcoufal, so are you okay if it turns out they don't have the bandwidth for those reviews?22:43
mrungeyes, I don't think there is a guarantee. on the other side, I don't see, how it could be so time-critical to get a patch in in e.g 4 hours22:43
lsmola_mrunge: well more like review22:43
mrungeit would be easier for core reviewers, if we get enough reviews on code at all22:44
*** kenhui1 has quit IRC22:44
jtomasekmrunge: exactly22:44
lsmola_mrunge: that means you will have several reviews in one day, and you can address a feedback quickly22:44
jpichIMO this needs more discussion on list to surface a consensus (if there is one to be found :-)), 12h isn't a lot of time...22:44
tzumainnmrunge, it's because we're building from scratch somewhat, so future patches are likely to depend on recent ones22:44
*** jmontemayor has joined #openstack-meeting22:44
*** sarob has joined #openstack-meeting22:44
tzumainnmrunge, also, I think some of our dependent libraries and apis may be in flux22:44
lsmola_jpich: sorry about that :-)22:44
jpichlsmola_: In an ideal world we want this for all the openstack patches22:44
*** DennyZhang has quit IRC22:44
mrungetzumainn, if you have dependent code, you could fetch it from gerrit22:45
jtomasekIf the patch has 5 +1's on it I don't see a lot of work for core to approve it22:45
jpichlsmola_: No worries!22:45
lsmola_jpich: yaaay lets build an ideal world :-)22:45
mrungejtomasek, exactly22:45
jcoufalhow many non-redhat core members horizon has?22:45
lsmola_jpich: can openstack buy some island?22:45
jpichlsmola_: I'll prepare a proposal for the foundation :)22:45
mrungejcoufal, 13 or so, if I'm not totally wrong22:46
lsmola_hehe22:46
david-lyle_~6 with varying levels of engagement22:46
mrungedon't we have more core reviewers?22:46
jcoufalso about 6-7 active cores?22:46
david-lyle_mrunge, cleaned up a little per ml outcome22:46
mrungeah, yes22:46
mrungeyou're right david-lyle_22:46
*** SergeyLukjanov has quit IRC22:46
david-lyle_mrunge, not enough reviewers in general, that's picked up lately22:46
david-lyle_but I think a track record needs to be established before moving people to core22:47
mrungewell we have here 5(?) new contributors....22:47
lsmola_622:47
mrungeand they should be able to do reviews as well, to help reducing the backlog22:48
jcoufalmy proposal would be to try to keep cross-company reviews, we (tuskar-ui) can help as much as possible to ease reviews and then ask outside company cross members to have a look on almost ready code to get in...22:48
jcoufalI think it can work22:48
tzumainnwhat is review latency like?22:48
david-lyle_jcoufal: I agree22:48
mrungecurrently, we're getting about 5-6 new patches per day22:48
*** ivasev has quit IRC22:48
jtomasekjcoufal: +122:49
jpichI think david's numbers were 18/day last week?22:49
tzumainnthe part I have trouble with is that a) tuskar-ui will require additional setup for reviewers, and b) tuskar doesn't have the documentation to ease reviewers' understanding of what's going on22:49
jcoufalcan we have fallback plan? if we find out that we can't move as quickly forward as we need to ask for exception for temporary 'one company' reviews?22:49
david-lyle_jpich: that may have been patchsets22:49
*** stevemar has quit IRC22:50
david-lyle_but those all require reviews22:50
jpichdavid-lyle: Most of them need reviews though :)22:50
jpichyeah22:50
mrungejpich, http://russellbryant.net/openstack-stats/horizon-reviewers-30.txt look at the bottom22:50
david-lyle_it's 19.9 now, btw22:50
*** troytoman is now known as troytoman-away22:50
jcoufaltzumainn: I don't think that horizon-core needs to ensure it works correctly from tripleo point of view - they can keep eye on if the code fits horizon way22:51
*** jmontemayor has quit IRC22:51
jcoufalat least from the beginning until they get more familiar with the code22:51
tzumainnhm, is that true?22:51
david-lyle_I think there is enough concern expressed here to put this on the mailing list for a little more fine tuning.22:51
* jcoufal thinks - so that's not assured :)22:51
david-lyle_I don't want to drag this out, but I don't think there's a concensus here22:52
jpichmrunge: Thank you for the link22:52
jpichAgreed22:52
jcoufaldavid-lyle_: agree on ML22:52
mrungeyupp, agreed22:52
*** thomasem has quit IRC22:52
lsmola_david-lyle: seems like it, though it looks like another very long thread :-D22:52
jcoufalwe can follow the new thread lsmola sent 12h ago22:52
tzumainnsounds like a plan to me : )22:52
lsmola_ok then22:53
jpichIs that email the new plan, or does a new-new plan needs to come out of this discussion first?22:53
jcoufalI'll write down some sort of summary or at least my point of view to kick this off22:53
jomarajcoufal: yes, reply to lsmola with it22:53
david-lyle_jcoufal: thanks22:53
jcoufalI just want to ask for one thing22:53
jcoufalcan we get attention to the ML to speed up the process of getting to consensus?22:53
lsmola_i think we can build a new plan based on the feedback :-)22:53
david-lyle_let's continue to work out the details.  I think this is the right fit, we just need the mechanics22:53
lsmola_david-lyle: so, talk about it again the next meeting?22:54
jcoufalnext meeting is christmas22:54
*** ItSANgo has joined #openstack-meeting22:54
jpichNext meeting is... next year?22:54
mrungenext meeting will be on the 24th?22:54
jcoufalI would like to get to consensus until the end of the week. if all possible22:54
lsmola_yes  I believe so22:54
jpichYes. We can work out a consensus on list22:54
david-lyle_yes, the next two weeks should be off from this meeting22:54
*** loq_mac has joined #openstack-meeting22:55
jpichThe meetings shouldn't be a requirement to making decision22:55
david-lyle_we can resolve this on the ml22:55
jpich*decisions22:55
david-lyle_#topic Open22:55
*** openstack changes topic to "Open (Meeting topic: Horizon)"22:55
mrungeso, next meeting will be on Jan 7th, david-lyle_ ?22:55
lsmola_ok, so let's make consensus on a list22:55
lsmola_jcoufal: not sure if we are able to do it til lthe end of the week, but it would be great22:55
jomara+1 to jan722:55
david-lyle_after short discussion of the agenda...22:55
jcoufaljpich, david-lyle_: thanks, tomorrow morning expect the starting e-mail22:55
lblanchardI just wanted to remind everyone that there is a Persona Working Group kickoff meeting tomorrow22:55
jpichjcoufal: Ok! Thanks22:56
david-lyle_mrunge, yes that's inline with the project meeting22:56
david-lyle_ml is always open for pressing issues in the interim22:56
jpichlblanchard: Thanks! Are there international numbers available?22:57
lblanchardjpich: great question!22:57
lblanchardjulim is running the meeting22:57
david-lyle_lblanchard: thanks for the reminder22:57
lblanchardI will follow up with her and cc you, jpich22:57
david-lyle_what was the flow there IRC then phone?22:57
*** sarob has quit IRC22:57
lblancharddavid-lyle: no problem. Yes, IRC and there is a conference call # in the invite22:57
jpichlblanchard: Ok, no problems. I think it would be useful to have it in the wiki and/or wherever else the meeting is announced :)22:58
lblanchardyes, good point. I will suggest this to Ju…I think maybe she will set up an etherpad early in the day and send that out to all22:58
lblanchardjpich: ^22:58
david-lyle_I see, that's an HP conference line, I'll see if I can dig up the international number for that22:58
jcoufallblanchard: +1 that would be great22:58
lblancharddavid-lyle: sounds great22:59
jpichlblanchard: Makes sense, cool22:59
lblanchardcool, catch those of you there who are interested :)22:59
*** johnthetubaguy has joined #openstack-meeting22:59
*** tims1 has joined #openstack-meeting23:00
david-lyle_Ok, thanks everyone.  Have a good couple of weeks and provider you tuskar-ui feedback on the ml.23:00
*** tims1 has left #openstack-meeting23:00
david-lyle_oh, and review :)23:00
david-lyle_#endmeeting23:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:00
openstackMeeting ended Tue Dec 17 23:00:48 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-12-17-22.02.html23:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-12-17-22.02.txt23:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-12-17-22.02.log.html23:00
jcoufalthanks everyone, it was great discussion23:00
kspearbye all23:00
jpichThanks! Happy end of year holidays23:01
tzumainnthanks all!23:01
jcoufaland reviews! :)23:01
*** dims has quit IRC23:01
lsmola_thanks everybody, have a beautiful holiday :-)23:01
mrungethanks and good night!23:01
jcoufalhave a great day/night23:01
jomaranight guys23:01
lblanchardthanks everyone! Good night!23:01
*** jcoufal has quit IRC23:01
*** MaxV has quit IRC23:01
*** jpich has quit IRC23:01
*** arnaud__ has quit IRC23:02
*** arnaud has quit IRC23:02
*** harlowja is now known as harlowja_away23:02
*** mrunge has quit IRC23:02
*** kspear has quit IRC23:02
jtomasekthanks all23:02
*** iccha_ is now known as iccha-dinner23:03
*** pablosan has quit IRC23:04
*** kevinconway has quit IRC23:04
*** MaxV has joined #openstack-meeting23:04
*** johnthetubaguy has quit IRC23:04
*** harlowja_away is now known as harlowja23:05
*** MaxV has quit IRC23:05
*** lsmola_ has quit IRC23:06
*** jtomasek has quit IRC23:07
*** eharney has quit IRC23:07
*** david-lyle_ has quit IRC23:10
*** dstanek has joined #openstack-meeting23:10
*** burt has quit IRC23:11
*** vijendar has quit IRC23:12
*** vijendar has joined #openstack-meeting23:13
*** nermina has quit IRC23:14
*** thomasem has joined #openstack-meeting23:15
*** dims has joined #openstack-meeting23:16
*** thomasem has quit IRC23:16
*** thomasem has joined #openstack-meeting23:16
*** vito-ordaz has joined #openstack-meeting23:19
*** yamahata has quit IRC23:20
*** vijendar has quit IRC23:20
*** reed has quit IRC23:22
*** thomasem has quit IRC23:23
*** sacharya has quit IRC23:24
*** dcramer_ has quit IRC23:24
*** MarkAtwood has joined #openstack-meeting23:24
*** weshay has quit IRC23:25
*** shardy is now known as shardy_afk23:26
*** gokrokve has quit IRC23:28
*** asalkeld has quit IRC23:29
*** radsy has quit IRC23:29
*** asalkeld has joined #openstack-meeting23:30
*** ItSANgo has quit IRC23:32
*** IlyaE has quit IRC23:33
*** jmontemayor has joined #openstack-meeting23:34
*** SlickNik has left #openstack-meeting23:35
*** elo has quit IRC23:35
*** jroovers has quit IRC23:36
*** elo has joined #openstack-meeting23:36
*** ItSANgo has joined #openstack-meeting23:36
*** branen has joined #openstack-meeting23:46
*** dolphm has quit IRC23:47
*** jmontemayor has quit IRC23:48
*** lblanchard has quit IRC23:49
*** dstanek has quit IRC23:51
*** fbo is now known as fbo_away23:55
*** SumitNaiksatam has quit IRC23:56

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