Tuesday, 2014-01-21

*** novas0x2a|laptop has quit IRC00:02
*** nelsnelson is now known as nelsnelson_away00:03
*** nelsnelson_away is now known as nelsnelson00:03
*** dcramer_ has quit IRC00:03
*** diogogmt has quit IRC00:04
*** IlyaE has quit IRC00:07
*** rakhmerov has quit IRC00:08
*** rakhmerov1 has joined #openstack-meeting00:08
*** oubiwann_ has quit IRC00:08
*** Longgeek has joined #openstack-meeting00:12
*** fnaval has quit IRC00:13
*** karthik has joined #openstack-meeting00:13
*** ryanpetrello has quit IRC00:13
*** julienvey_ has quit IRC00:13
*** rakhmerov1 has quit IRC00:14
*** markwash has quit IRC00:16
*** Longgeek has quit IRC00:18
*** markwash has joined #openstack-meeting00:18
*** safchain has quit IRC00:20
*** pvaneck has quit IRC00:24
*** svetlanad has quit IRC00:33
*** fnaval has joined #openstack-meeting00:33
*** svetlanad has joined #openstack-meeting00:34
*** novas0x2a|laptop has joined #openstack-meeting00:36
*** sandywalsh has quit IRC00:42
*** rnirmal has quit IRC00:45
*** radez_g0n3 is now known as radez00:45
*** natarajk has joined #openstack-meeting00:48
*** markmcclain has joined #openstack-meeting00:48
*** dcramer_ has joined #openstack-meeting00:51
*** cdub has joined #openstack-meeting00:52
*** natarajk has quit IRC00:54
*** karthik has quit IRC00:54
*** joesavak has joined #openstack-meeting00:55
*** jsavak has joined #openstack-meeting00:57
*** banix has joined #openstack-meeting00:59
*** joesavak has quit IRC01:00
*** topol has joined #openstack-meeting01:01
*** asalkeld has joined #openstack-meeting01:10
*** arosen1 has quit IRC01:14
*** cdub has quit IRC01:16
*** Longgeek has joined #openstack-meeting01:17
*** krotscheck has quit IRC01:17
*** arosen1 has joined #openstack-meeting01:19
*** dcramer_ has quit IRC01:19
*** Longgeek has quit IRC01:22
*** ddutta has quit IRC01:23
*** markmcclain has quit IRC01:25
*** jsavak has quit IRC01:28
*** elo has joined #openstack-meeting01:31
*** arosen1 has quit IRC01:33
*** svetlanad has quit IRC01:33
*** svetlanad has joined #openstack-meeting01:34
*** elo has quit IRC01:36
*** jaypipes has quit IRC01:37
*** galstrom_zzz is now known as galstrom01:38
*** galstrom is now known as galstrom_zzz01:39
*** xuhanp_ has joined #openstack-meeting01:41
*** neelashah has joined #openstack-meeting01:42
*** weshay has joined #openstack-meeting01:43
*** neelashah has quit IRC01:43
*** neelashah has joined #openstack-meeting01:44
*** bdpayne has quit IRC01:46
*** ddutta has joined #openstack-meeting01:47
*** arosen1 has joined #openstack-meeting01:48
*** MrJoshua has joined #openstack-meeting01:49
*** ddutta_ has joined #openstack-meeting01:49
*** krotscheck has joined #openstack-meeting01:50
*** ryanpetrello has joined #openstack-meeting01:50
*** coolsvap has quit IRC01:51
*** ddutta has quit IRC01:53
*** ddutta_ has quit IRC01:54
*** zhikunliu has joined #openstack-meeting01:56
*** krotscheck has quit IRC01:58
*** nosnos has joined #openstack-meeting01:59
*** otherwiseguy has quit IRC02:00
*** jrist has quit IRC02:01
*** yaguang has joined #openstack-meeting02:01
*** arosen1 has quit IRC02:04
*** ryanpetrello has quit IRC02:04
*** oubiwann_ has joined #openstack-meeting02:09
*** otherwiseguy has joined #openstack-meeting02:12
*** dcramer_ has joined #openstack-meeting02:12
*** morganfainberg|z is now known as morganfainberg02:13
*** jorisroovers has quit IRC02:18
*** arosen1 has joined #openstack-meeting02:23
*** oldfish has joined #openstack-meeting02:23
*** elo has joined #openstack-meeting02:26
*** colinmcnamara has quit IRC02:28
*** ArthurBerezin has joined #openstack-meeting02:28
*** yamahata has quit IRC02:29
*** colinmcnamara has joined #openstack-meeting02:29
*** svetlanad has quit IRC02:33
*** arosen1 has quit IRC02:33
*** svetlanad has joined #openstack-meeting02:33
*** oldfish has quit IRC02:34
*** ArthurBerezin has quit IRC02:34
*** elo1 has joined #openstack-meeting02:34
*** vkozhukalov has joined #openstack-meeting02:34
*** elo has quit IRC02:35
*** samcdona has quit IRC02:38
*** Jianyong has joined #openstack-meeting02:38
*** amcrn has joined #openstack-meeting02:40
*** sjing has joined #openstack-meeting02:40
*** jasondotstar has joined #openstack-meeting02:40
*** Mandell has quit IRC02:41
*** epico has joined #openstack-meeting02:42
*** Linz has quit IRC02:42
*** arosen1 has joined #openstack-meeting02:42
*** Linz has joined #openstack-meeting02:43
*** sadarar_ has joined #openstack-meeting02:43
*** dkranz has joined #openstack-meeting02:48
*** mrda_ is now known as mrda_away02:49
*** mrda_away is now known as mrda_02:49
*** sdake has quit IRC02:49
*** arosen1 has quit IRC02:51
*** asalkeld has quit IRC02:51
*** kbenton_ has joined #openstack-meeting02:53
*** markmcclain has joined #openstack-meeting02:57
*** slong has joined #openstack-meeting02:58
*** markmcclain1 has joined #openstack-meeting02:59
*** Sam-I-Am has joined #openstack-meeting02:59
*** markmcclain has quit IRC03:02
*** IlyaE has joined #openstack-meeting03:02
*** markmcclain1 has quit IRC03:03
loquacities#startmeeting DocTeamMeeting03:04
openstackMeeting started Tue Jan 21 03:04:38 2014 UTC and is due to finish in 60 minutes.  The chair is loquacities. Information about MeetBot at http://wiki.debian.org/MeetBot.03:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.03:04
*** openstack changes topic to " (Meeting topic: DocTeamMeeting)"03:04
openstackThe meeting name has been set to 'docteammeeting'03:04
loquacitieshey everyone, sorry for the late start :)03:05
Sam-I-Amno problem03:05
loquacities#topic Action items from last meeting03:05
*** openstack changes topic to "Action items from last meeting (Meeting topic: DocTeamMeeting)"03:05
*** rods has quit IRC03:05
*** dkranz has quit IRC03:05
*** weshay has quit IRC03:05
*** radez is now known as radez_g0n303:06
loquacitiesACTION: slong or chandankumar add WIP info to https://wiki.openstack.org/wiki/Documentation/HowTo#Reviewing_Documentation (annegentle, 14:04:41)03:06
loquacitiesslong: do you have an update on that?03:06
*** dnavale has joined #openstack-meeting03:06
Sam-I-Ami think chandan added it03:06
slongI saw that chandankumar wrote something, I gave him an edit, but03:07
slonghasn't been put in.03:07
loquacitiesoh cool03:07
loquacitiesexcellent03:07
slongLeft it with him.03:07
loquacitiesACTION: NickChase and carlp and Sam-I-Am to meet03:07
loquacitiesSam-I-Am?03:07
loquacitiesre:  installation guide changes for Icehouse03:07
Sam-I-Amwe met last wednesday and we're meeting again this thursday03:07
loquacitiescool, need anything?03:08
Sam-I-Amnick is putting together three blueprints for neutron... install guide reorg, cloud admin guide, and possibly a book03:08
loquacitiesoh, that is cool03:08
*** Linz has quit IRC03:08
Sam-I-Ami'm also trying to install icehouse in my lab to work on ML203:08
loquacitiesdefinitely all things i'm interested in :)03:08
loquacitiesACTION: NickChase to contact Edgar Magana on the neutron team to let him know the networking guide plan03:09
loquacitiesSam-I-Am: can you comment on that?03:09
Sam-I-Amegdar was pulled into the loop in some e-mails03:09
loquacitiesok, cool03:09
loquacitiesACTION: annegentle to email Nick and Edgar03:09
Sam-I-Ami think he's going to be on the meeting on thursday03:09
loquacities^^ probably the same answer, yeah?03:09
Sam-I-Amyeah03:10
loquacitiesACTION: NickChase to email openstack-docs mailing list with plan for networking guide03:10
Sam-I-Ami havent seen that one yet03:10
loquacitiesthere's been discussion, though, so i'm assuming we're well on the way03:10
*** Linz has joined #openstack-meeting03:11
loquacitiesok, that's it for action items03:11
loquacitiesany comment on those?03:11
Sam-I-Amyeah, most of it is around the neutron HA stuff03:11
loquacitiesyeah, i'm sorry i missed that convo03:11
loquacities#topic Report from Doc Bug Day Dec 2003:11
*** openstack changes topic to "Report from Doc Bug Day Dec 20 (Meeting topic: DocTeamMeeting)"03:11
Sam-I-Amthat was a blast03:11
loquacities#link http://bit.ly/1b32JM003:12
loquacitiesyeah, it was pretty awesome :)03:12
loquacitiessomething like 80 bugs, according to anne03:12
loquacities#topic Schedule January Monthly Google Hangout03:13
*** openstack changes topic to "Schedule January Monthly Google Hangout (Meeting topic: DocTeamMeeting)"03:13
loquacitiesso, anne and i have been going back and forth on this one, and there some chatter on the list too03:13
loquacitiesthe current date i have is 29 jan, 2000 UTC03:14
Sam-I-Amme too03:14
loquacitiesthat's not wonderful for us, but anne is trying to get europe in on this one03:14
loquacitiesthe stated point is that it's a good idea to just see each other and chat a bit every so often, although i think there'll be a loose agenda03:14
slonger, that's 6am?03:14
loquacitiesslong: yeah, she wants to move them around to give everyone a chance03:15
loquacitiesso this time we draw the short straw03:15
slongbelieve me 6 is better than 11/12pm.03:15
loquacitiesyeah, i agree FWIW03:15
*** suo__ has joined #openstack-meeting03:15
Sam-I-Amas long as there's coffee03:16
slong:)03:16
loquacitiesso anyway, is everyone cool with that day/time?03:16
*** dcramer_ has quit IRC03:16
slong+103:16
loquacities(acknowledging that it might be difficult for people in our tz)03:16
slongwill endeavor....03:16
loquacitiesawesome03:16
loquacitiesquiet meeting today03:16
Sam-I-Amfine here too03:16
slonglots of stuff going on. Harder to focus when you're at work :)03:17
loquacitiesawesome, thanks Sam-I-Am03:17
loquacitiesyeah, tell me about it ;)03:17
Sam-I-Amfifield is in the US03:17
loquacitiesoh, he's travelling?03:17
Sam-I-Amyeah03:17
loquacitiesok, i'll take that as a yes for the hangout, anyway03:17
Sam-I-Amsome sort of staff meeting03:17
loquacities#topic Webinar in February (date tbd) to update Icehouse doc/qa/infra plans03:17
*** openstack changes topic to "Webinar in February (date tbd) to update Icehouse doc/qa/infra plans (Meeting topic: DocTeamMeeting)"03:17
loquacitiesi haven't got any updated info on this other than what anne said in the meeting last week03:18
loquacities14:18:39 <annegentle> this summit, HK, they stopped having the PTLs give an update for plans during the Summit itself03:18
loquacities14:18:48 <annegentle> so, they're doing webinars after03:18
loquacities14:18:52 <annegentle> this is docs turn03:18
loquacities14:18:56 <annegentle> should be first week of Feb.03:18
loquacitiesso just a heads up for that03:18
slongInteresting03:18
loquacitiesyeah, i thought so too, slong :)03:19
loquacities#topic Done with backports to stable/havana03:19
*** openstack changes topic to "Done with backports to stable/havana (Meeting topic: DocTeamMeeting)"03:19
loquacitiesjust in case you didn't get that memo already03:19
Sam-I-Amthere's always one more03:19
slongquestion about backports...03:19
*** arosen1 has joined #openstack-meeting03:19
slongonly the Install Guide gets an actual branch, right?03:19
loquacitiesi believe so03:20
slongSo the other guides are continually integrated?03:20
loquacitiesyep03:20
slongAnd switching this week or next to Icehouse?03:20
loquacitiesthis week03:20
slongkk, just getting my head around the process.03:20
loquacitiesnp03:20
*** paragan has joined #openstack-meeting03:20
loquacities#topic Discuss any installation guide changes for Icehouse03:21
*** openstack changes topic to "Discuss any installation guide changes for Icehouse (Meeting topic: DocTeamMeeting)"03:21
loquacitiesthere was a fair bit of discussion around this at last week's meeting03:21
Sam-I-Amyes03:21
loquacitiesbut i think most of it has moved onto the mailing list now03:21
*** emagana has quit IRC03:21
*** Longgeek has joined #openstack-meeting03:21
Sam-I-Amneutron became a project by itself03:21
loquacitiesbasically, we're continuing with the manual install/choose your own adventure style, with the exception of networking03:22
loquacitiesyep03:22
*** AlanClark has quit IRC03:22
loquacitiesso there's a plan afoot for a new networking book, yeah?03:22
Sam-I-Amyeah03:22
Sam-I-Ami think we're leaning toward making the install guide "just work" for the most common cases03:22
Sam-I-Amthen move the more advanced things into other places03:22
loquacitiesi think that's sane03:23
loquacities#topic Doc tools update - release to support Japanese translation03:23
*** openstack changes topic to "Doc tools update - release to support Japanese translation (Meeting topic: DocTeamMeeting)"03:23
loquacitiesso i don't have a lot of info on this one03:23
Sam-I-Amme neither03:24
loquacitiesbut i believe that's all underway, and shouldn't particular impact our workflow03:24
*** elo1 has quit IRC03:24
loquacitiesok, i think that wraps up the agenda03:24
loquacities#topic Open discussion03:25
slongone thing.03:25
*** openstack changes topic to "Open discussion (Meeting topic: DocTeamMeeting)"03:25
slongThe ops guide sprint still happening this week?03:25
loquacitiesoh, i don't know03:25
loquacitiesi've been out of the loop a bit, sorry03:25
slongI've done the provisional neutron/HA architecture update, but it's still getting a tech review.03:26
loquacitiesand i can't see anything on the ML other than anne on the 14th03:26
slongHoping to have that done by tomorrow.03:26
loquacitiesok, sounds good03:26
slongOk, won't panic then. Anne had initially said 22.Jan03:26
loquacitiesyeah, that's the most recent email i can find03:26
loquacitiesnothing confirming that03:26
slongWell, will soldier on...03:26
loquacitieslove your work :)03:27
loquacitiesalso: i think we may be due to organise a BNE openstack writers meetup, yeah?03:27
*** colinmcnamara has quit IRC03:27
*** sbalukoff has quit IRC03:27
*** Longgeek has quit IRC03:28
*** dcramer_ has joined #openstack-meeting03:28
*** dguitarbite has joined #openstack-meeting03:28
loquacitiesslong: ^^ ?03:28
slongsorry, someone talking...03:29
loquacitiesnp03:29
slongYes, definitely :)03:29
Sam-I-Amtook me a while to figure out what 'bne' meant :/03:29
loquacitiesok, well, i'll send you an email and we can get that happening03:29
loquacitiesoh! sorry Sam-I-Am, it's the airport code for brisbane :)03:29
loquacitiesok, any other business?03:30
Sam-I-Amnothing from me03:30
*** reed has quit IRC03:30
loquacitiesslong?03:30
slongnope, all good03:30
loquacitiesawesome03:30
slongthanks for running things03:30
loquacitiessorry for missing last fortnight03:30
loquacitiesoh! that reminds me ... how do we feel about moving to wednesday meetings?03:31
slongI missed whether US was moving permanently?03:31
loquacitiesalso, while i'm on the topic: is this timing ok?03:31
loquacitiesyes, they are03:31
*** suo__ has quit IRC03:31
slong+1 on timing03:31
slong+1 on wednesday then03:31
loquacitiesok, so same time, but on wednesdays03:31
annegentleslong: yes, ops guide sprint still Thurs/Fri this week.03:31
loquacitiesi'll update the wiki03:32
Sam-I-Ami think i'm ok with wednesdays too03:32
loquacitiesoh hi annegentle :)03:32
* annegentle pops in 03:32
Sam-I-Amin this time zone i can usually make both meetings03:32
slongOk, will make sure the commit is there for the ops guide03:32
annegentleslong: I just got parts working today I think, a few more brushups on the toolside03:32
annegentleslong: thank you!03:32
Sam-I-Amhi anne!03:32
slong'parts'?03:32
annegentlealso chandankumar has one in the review queue03:32
*** yamahata has joined #openstack-meeting03:32
*** doug_shelley66 has quit IRC03:32
annegentleslong: so the editor keeps asking for two parts: architecture and operations03:32
annegentleslong: and it's sorta what we wanted in the first place also, but our tool couldn't output it03:33
*** svetlanad has quit IRC03:33
annegentleso now we can make o'reilly editors happy AND have our output nice :)03:33
slongoh, interesting.03:33
loquacitiesnice :)03:33
loquacitiesi'm a big fan of <part>s generally03:33
slongannegentle, this is the change: https://review.openstack.org/#/c/67763/03:34
annegentleloquacities: yeah once we get it working I'll send a note to the list - Cloud Admin Guide might like some parts03:34
loquacitiesi agree03:34
*** svetlanad has joined #openstack-meeting03:34
annegentleslong: great! I will take a look!03:34
slongIf my tech reviewer doesn't get back to me by this afternoon, just go ahead and take as is?03:34
slongI'll raise a bug for anything that comes up.03:34
annegentleslong: I think so03:35
Sam-I-Amslong: is this the active/active thing?03:35
slongAt least the sprint will have the bulk.03:35
slongha/neutron03:35
slongyes03:35
slongbut doesn't use that terminology, rather that everything is backing everything else up :)03:36
loquacitieslol03:36
slongyeah03:36
Sam-I-Ami c03:36
loquacitiesok, any other business?03:36
loquacitiesthanks everyone :)03:37
loquacities#endmeeting03:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"03:37
openstackMeeting ended Tue Jan 21 03:37:39 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docteammeeting/2014/docteammeeting.2014-01-21-03.04.html03:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docteammeeting/2014/docteammeeting.2014-01-21-03.04.txt03:37
openstackLog:            http://eavesdrop.openstack.org/meetings/docteammeeting/2014/docteammeeting.2014-01-21-03.04.log.html03:37
Sam-I-Amthanks!03:37
loquacitiesnp03:37
*** slong has left #openstack-meeting03:37
* Sam-I-Am returns to his regularly scheduled wandering aimlessly in icehouse03:38
loquacitiesthanks for pinging me on schedule, too, Sam-I-Am :)03:38
Sam-I-Amnp03:38
annegentlethanks loquacities!03:38
loquacitiesmy pleasure :)03:38
*** Sam-I-Am has left #openstack-meeting03:40
*** salv-orlando has quit IRC03:42
*** salv-orlando has joined #openstack-meeting03:42
*** asalkeld has joined #openstack-meeting03:45
*** samcdona has joined #openstack-meeting03:48
*** novas0x2a|laptop has quit IRC03:50
*** asalkeld has quit IRC03:52
*** dkranz has joined #openstack-meeting03:52
*** sankarshan_away is now known as sankarshan03:54
*** ryanpetrello has joined #openstack-meeting03:57
*** marun has joined #openstack-meeting04:00
*** ArthurBerezin has joined #openstack-meeting04:01
*** sadarar_ has quit IRC04:03
*** matiu has joined #openstack-meeting04:03
*** asalkeld has joined #openstack-meeting04:05
*** reed has joined #openstack-meeting04:08
*** ArthurBerezin has left #openstack-meeting04:10
*** marun has quit IRC04:12
*** marun has joined #openstack-meeting04:13
*** marun has quit IRC04:14
*** marun has joined #openstack-meeting04:16
*** mattgriffin has quit IRC04:17
*** krotscheck has joined #openstack-meeting04:19
*** elo has joined #openstack-meeting04:20
*** ArxCruz has quit IRC04:20
*** arosen1 has quit IRC04:20
*** elo has quit IRC04:24
*** krotscheck has quit IRC04:24
*** bdpayne has joined #openstack-meeting04:25
*** Longgeek has joined #openstack-meeting04:26
*** krotscheck has joined #openstack-meeting04:26
*** elo has joined #openstack-meeting04:27
*** elo has quit IRC04:29
*** elo has joined #openstack-meeting04:31
*** emagana has joined #openstack-meeting04:32
*** Longgeek has quit IRC04:32
*** svetlanad has quit IRC04:33
*** svetlanad has joined #openstack-meeting04:33
*** emagana has quit IRC04:37
*** arosen has joined #openstack-meeting04:38
*** coolsvap has joined #openstack-meeting04:38
*** ryanpetrello has quit IRC04:40
*** mattgriffin has joined #openstack-meeting04:40
*** asalkeld has quit IRC04:45
*** elo has quit IRC04:47
*** Mandell has joined #openstack-meeting04:57
*** ayoung is now known as ayoung-zZzZzZzZ04:58
*** arosen has quit IRC04:59
*** IlyaE has quit IRC05:04
*** SergeyLukjanov_ is now known as SergeyLukjanov05:06
*** marun has quit IRC05:08
*** elo has joined #openstack-meeting05:08
*** nshaikh has joined #openstack-meeting05:09
*** arosen has joined #openstack-meeting05:12
*** krotscheck has quit IRC05:12
*** chandankumar_ has joined #openstack-meeting05:14
*** bdpayne has quit IRC05:16
*** oubiwann_ has quit IRC05:20
*** matiu has quit IRC05:22
*** asalkeld has joined #openstack-meeting05:22
*** otherwiseguy has quit IRC05:23
*** matiu has joined #openstack-meeting05:23
*** matiu has quit IRC05:24
*** matiu has joined #openstack-meeting05:24
*** asalkeld has left #openstack-meeting05:24
*** IlyaE has joined #openstack-meeting05:26
*** crank has quit IRC05:28
*** crank has joined #openstack-meeting05:29
*** Linz has quit IRC05:32
*** markpeek1 has quit IRC05:32
*** IlyaE has quit IRC05:32
*** svetlanad has quit IRC05:33
*** svetlanad has joined #openstack-meeting05:34
*** Linz has joined #openstack-meeting05:36
*** banix has quit IRC05:36
*** garyk has quit IRC05:48
*** jasondotstar has quit IRC05:57
*** emagana has joined #openstack-meeting05:59
*** akuznetsov has quit IRC05:59
*** ildikov_ has quit IRC06:01
*** reed has quit IRC06:01
*** rakhmerov has joined #openstack-meeting06:03
*** nati_ueno has quit IRC06:06
*** elo has quit IRC06:06
*** SergeyLukjanov is now known as SergeyLukjanov_a06:12
*** SergeyLukjanov_a is now known as SergeyLukjanov_06:13
*** nshaikh has left #openstack-meeting06:14
*** bdpayne has joined #openstack-meeting06:16
*** zhikunliu has quit IRC06:18
*** Longgeek has joined #openstack-meeting06:19
*** nati_ueno has joined #openstack-meeting06:22
*** arosen has quit IRC06:22
*** nati_ueno has quit IRC06:23
*** nati_ueno has joined #openstack-meeting06:24
*** SumitNaiksatam_ has joined #openstack-meeting06:25
*** SumitNaiksatam has quit IRC06:25
*** SumitNaiksatam_ is now known as SumitNaiksatam06:25
*** akuznetsov has joined #openstack-meeting06:26
*** Longgeek has quit IRC06:26
*** svetlanad has quit IRC06:33
*** markvoelker has quit IRC06:33
*** svetlanad has joined #openstack-meeting06:34
*** haomaiwa_ has quit IRC06:36
*** haomaiwang has joined #openstack-meeting06:36
*** doug_shelley66 has joined #openstack-meeting06:36
*** akuznetsov has quit IRC06:37
*** akuznetsov has joined #openstack-meeting06:37
*** crank has quit IRC06:39
*** arosen has joined #openstack-meeting06:41
*** SergeyLukjanov_ is now known as SergeyLukjanov06:42
*** mrunge has joined #openstack-meeting06:43
*** mrunge has quit IRC06:44
*** mrunge has joined #openstack-meeting06:44
*** haomaiwa_ has joined #openstack-meeting06:45
*** vkozhukalov has quit IRC06:47
*** elo has joined #openstack-meeting06:47
*** haomaiwang has quit IRC06:48
*** elo has quit IRC06:49
*** crank has joined #openstack-meeting06:51
*** elo has joined #openstack-meeting06:51
*** egallen has joined #openstack-meeting06:51
*** arosen has quit IRC06:52
*** topol has quit IRC06:54
*** bdpayne has quit IRC06:55
*** garyk has joined #openstack-meeting06:56
*** dnavale has left #openstack-meeting06:56
*** haomaiwa_ has quit IRC06:56
*** haomaiwang has joined #openstack-meeting06:56
*** arosen has joined #openstack-meeting06:58
*** haomaiwa_ has joined #openstack-meeting06:59
*** haomaiwang has quit IRC07:01
*** crank has quit IRC07:02
*** crank has joined #openstack-meeting07:02
*** akuznets_ has joined #openstack-meeting07:05
*** arosen has quit IRC07:05
*** arosen has joined #openstack-meeting07:07
*** mrunge has quit IRC07:07
*** mrunge has joined #openstack-meeting07:08
*** akuznetsov has quit IRC07:08
*** doron_afk has joined #openstack-meeting07:12
*** nati_uen_ has joined #openstack-meeting07:12
*** nati_uen_ has quit IRC07:13
*** nati_uen_ has joined #openstack-meeting07:14
*** nati_ueno has quit IRC07:16
*** MaxV has joined #openstack-meeting07:23
*** sankarshan is now known as sankarshan_away07:26
*** sankarshan_away is now known as sankarshan07:27
*** mrda has quit IRC07:27
*** sankarshan is now known as sankarshan_away07:27
*** SergeyLukjanov is now known as SergeyLukjanov_07:29
*** IlyaE has joined #openstack-meeting07:30
*** nadya__ has joined #openstack-meeting07:31
*** svetlanad has quit IRC07:33
*** svetlanad has joined #openstack-meeting07:33
*** MaxV has quit IRC07:36
*** amotoki has joined #openstack-meeting07:38
*** ifarkas has joined #openstack-meeting07:41
*** belmoreira has joined #openstack-meeting07:43
*** amcrn has quit IRC07:45
*** NikitaKonovalov_ is now known as NikitaKonovalov07:45
*** ildikov_ has joined #openstack-meeting07:51
*** mattgriffin has quit IRC07:54
*** jtomasek has joined #openstack-meeting07:56
*** sdake has joined #openstack-meeting07:58
*** Longgeek has joined #openstack-meeting08:01
*** nati_ueno has joined #openstack-meeting08:02
*** nati_ueno has quit IRC08:02
*** nati_ueno has joined #openstack-meeting08:03
*** nati_uen_ has quit IRC08:05
*** Longgeek has quit IRC08:08
*** IlyaE has quit IRC08:10
*** evgenyf has joined #openstack-meeting08:10
*** _ruhe is now known as ruhe08:11
*** jcoufal has joined #openstack-meeting08:13
*** arosen has quit IRC08:13
*** flaper87|afk is now known as flaper8708:14
*** julienvey_ has joined #openstack-meeting08:19
*** mdurnosvistov has joined #openstack-meeting08:28
*** julienvey_ has quit IRC08:28
*** vkozhukalov has joined #openstack-meeting08:28
*** paragan has quit IRC08:33
*** SergeyLukjanov_ is now known as SergeyLukjanov08:37
*** mattgriffin has joined #openstack-meeting08:37
*** sjing has quit IRC08:39
*** _keyvan is now known as keyvan08:40
*** fbo_away is now known as fbo08:41
*** marekd|away is now known as marekd08:41
*** DinaBelova_ is now known as DinaBelova08:43
*** ilyashakhat has quit IRC08:43
*** safchain has joined #openstack-meeting08:43
*** ilyashakhat has joined #openstack-meeting08:43
*** yamahata has quit IRC08:45
*** paragan has joined #openstack-meeting08:46
*** comay has quit IRC08:46
*** yassine has joined #openstack-meeting08:47
*** nati_uen_ has joined #openstack-meeting08:51
*** ygbo has joined #openstack-meeting08:51
*** Mandell has quit IRC08:53
*** nati_ueno has quit IRC08:55
*** nati_uen_ has quit IRC08:56
*** doron_afk is now known as doron_08:56
*** markwash has quit IRC08:56
*** nati_ueno has joined #openstack-meeting08:57
*** dcramer_ has quit IRC08:59
*** mattgriffin has quit IRC09:00
*** boris-42 has quit IRC09:00
*** derekh has joined #openstack-meeting09:00
*** boris-42 has joined #openstack-meeting09:00
*** MaxV has joined #openstack-meeting09:01
*** sushils has quit IRC09:02
*** afazekas has joined #openstack-meeting09:03
*** evgenyf has quit IRC09:06
*** I159 has joined #openstack-meeting09:06
*** evgenyf has joined #openstack-meeting09:07
*** aignatov has joined #openstack-meeting09:10
*** doron_ is now known as doron_afk09:11
*** dcramer_ has joined #openstack-meeting09:11
*** jlibosva has joined #openstack-meeting09:12
*** mdbooth has joined #openstack-meeting09:32
*** minminren has joined #openstack-meeting09:33
*** lxsli has joined #openstack-meeting09:39
*** miarmak has joined #openstack-meeting09:47
*** nati_uen_ has joined #openstack-meeting09:50
*** nati_ueno has quit IRC09:54
*** salv-orlando has quit IRC09:55
*** salv-orlando has joined #openstack-meeting09:56
*** nati_uen_ has quit IRC09:57
*** nati_ueno has joined #openstack-meeting09:58
*** sushils has joined #openstack-meeting09:59
*** nshaikh has joined #openstack-meeting09:59
*** MaxV has quit IRC10:00
*** jasondotstar has joined #openstack-meeting10:00
*** scroiset has left #openstack-meeting10:05
*** johnthetubaguy has joined #openstack-meeting10:05
*** MaxV has joined #openstack-meeting10:08
*** coolsvap has quit IRC10:09
*** sileht has quit IRC10:11
*** coolsvap has joined #openstack-meeting10:12
*** rakhmerov has quit IRC10:12
*** ihrachys has quit IRC10:16
*** ihrachys has joined #openstack-meeting10:16
*** sileht has joined #openstack-meeting10:21
*** coolsvap has quit IRC10:23
*** coolsvap has joined #openstack-meeting10:27
*** paragan has quit IRC10:27
*** aignatov is now known as aignatov_10:29
*** dguitarbite has quit IRC10:29
*** dguitarbite has joined #openstack-meeting10:29
*** xuhanp_ has quit IRC10:29
*** lxsli has quit IRC10:33
*** uaberme has joined #openstack-meeting10:35
*** boris-42 has quit IRC10:38
*** asalkeld has joined #openstack-meeting10:38
*** yassine has quit IRC10:38
*** ruhe is now known as _ruhe10:39
*** Jianyong has quit IRC10:41
*** yassine has joined #openstack-meeting10:42
*** rakhmerov has joined #openstack-meeting10:42
*** IgorYozhikov has quit IRC10:44
*** IgorYozhikov has joined #openstack-meeting10:44
*** nati_uen_ has joined #openstack-meeting10:46
*** rakhmerov has quit IRC10:47
*** ArxCruz has joined #openstack-meeting10:48
*** nati_ueno has quit IRC10:49
*** Longgeek has joined #openstack-meeting10:50
*** yassine has quit IRC10:50
*** yassine has joined #openstack-meeting10:50
*** jroovers has joined #openstack-meeting10:52
*** jorisroovers has joined #openstack-meeting10:52
*** _ruhe is now known as ruhe10:54
*** jroovers has quit IRC10:56
*** yassine has quit IRC10:57
*** minminren has quit IRC10:57
*** jasondotstar has quit IRC11:01
*** aignatov_ is now known as aignatov11:01
*** jasondotstar has joined #openstack-meeting11:07
*** emagana has quit IRC11:07
*** yassine has joined #openstack-meeting11:10
*** epico has quit IRC11:13
*** jhenner has joined #openstack-meeting11:13
*** SergeyLukjanov is now known as SergeyLukjanov_11:15
*** jcoufal has quit IRC11:17
*** SergeyLukjanov_ is now known as SergeyLukjanov11:19
*** egallen has quit IRC11:20
*** yassine has quit IRC11:21
*** yassine has joined #openstack-meeting11:23
*** rfolco has joined #openstack-meeting11:32
*** emagana has joined #openstack-meeting11:38
*** jcoufal has joined #openstack-meeting11:42
*** rakhmerov has joined #openstack-meeting11:43
*** emagana has quit IRC11:46
*** rakhmerov has quit IRC11:48
*** Longgeek has quit IRC11:53
*** yaguang has quit IRC11:55
*** uaberme has quit IRC11:57
*** dguitarbite has quit IRC11:58
*** topol has joined #openstack-meeting12:00
*** dguitarbite has joined #openstack-meeting12:03
*** ruhe is now known as _ruhe12:05
*** boris-42 has joined #openstack-meeting12:05
*** paragan has joined #openstack-meeting12:09
*** paragan has joined #openstack-meeting12:09
*** _ruhe is now known as ruhe12:11
*** jorisroovers has quit IRC12:21
*** coolsvap has quit IRC12:22
*** b3nt_pin has joined #openstack-meeting12:23
*** b3nt_pin is now known as beagles12:23
*** andreaf has quit IRC12:25
*** madmike has quit IRC12:27
*** svetlanad has quit IRC12:28
*** nshaikh has quit IRC12:31
*** rdxc has joined #openstack-meeting12:35
*** jasondotstar has quit IRC12:36
*** DinaBelova is now known as DinaBelova_12:37
*** I159 has quit IRC12:44
*** rakhmerov has joined #openstack-meeting12:44
*** jroovers has joined #openstack-meeting12:45
*** jroovers has joined #openstack-meeting12:45
*** I159 has joined #openstack-meeting12:46
*** rakhmerov has quit IRC12:49
*** asalkeld has quit IRC12:51
*** xuhanp has joined #openstack-meeting12:52
*** jay-lau-513 has joined #openstack-meeting12:56
*** markmcclain has joined #openstack-meeting12:58
*** amotoki has quit IRC12:58
*** jorisroovers has joined #openstack-meeting12:59
*** jroovers has quit IRC12:59
*** egallen has joined #openstack-meeting12:59
*** yaguang has joined #openstack-meeting12:59
*** ericyoung has joined #openstack-meeting13:00
*** jhenner1 has joined #openstack-meeting13:01
*** jhenner has quit IRC13:02
*** SergeyLukjanov is now known as SergeyLukjanov_a13:02
*** markvoelker has joined #openstack-meeting13:03
*** SergeyLukjanov_a is now known as SergeyLukjanov_13:03
*** asalkeld has joined #openstack-meeting13:03
*** asalkeld has quit IRC13:04
*** afazekas has quit IRC13:04
*** jmh_ has joined #openstack-meeting13:05
*** DinaBelova_ is now known as DinaBelova13:07
*** Guest62400 has joined #openstack-meeting13:09
*** SergeyLukjanov_ is now known as SergeyLukjanov13:09
*** amotoki has joined #openstack-meeting13:14
*** pdmars has joined #openstack-meeting13:14
*** rods has joined #openstack-meeting13:17
*** afazekas has joined #openstack-meeting13:19
*** markmcclain has quit IRC13:22
*** ArthurBerezin has joined #openstack-meeting13:24
*** ArthurBerezin has left #openstack-meeting13:25
*** Guest62400 has left #openstack-meeting13:26
*** emagana has joined #openstack-meeting13:26
*** Linz has quit IRC13:29
*** nosnos has quit IRC13:30
*** Linz has joined #openstack-meeting13:30
*** jdob has joined #openstack-meeting13:31
*** nosnos has joined #openstack-meeting13:31
*** emagana has quit IRC13:31
*** thouvenin has quit IRC13:31
*** safchain has quit IRC13:32
*** sankarshan_away is now known as sankarshan13:33
*** jroovers has joined #openstack-meeting13:33
*** jorisroovers has quit IRC13:35
*** mfink has joined #openstack-meeting13:36
*** ayoung-zZzZzZzZ has quit IRC13:37
*** nosnos has quit IRC13:38
*** ruhe is now known as _ruhe13:42
*** _ruhe is now known as ruhe13:45
*** rakhmerov has joined #openstack-meeting13:45
*** dzyu has joined #openstack-meeting13:45
*** MaxV has quit IRC13:45
*** safchain has joined #openstack-meeting13:47
*** jasondotstar has joined #openstack-meeting13:47
*** safchain has quit IRC13:47
*** safchain has joined #openstack-meeting13:48
*** julim has joined #openstack-meeting13:49
*** uaberme has joined #openstack-meeting13:49
*** rakhmerov has quit IRC13:50
*** ryanpetrello has joined #openstack-meeting13:51
*** jhenner1 has quit IRC13:51
*** jhenner has joined #openstack-meeting13:51
*** doug_shelley66 has quit IRC13:51
*** thomasem has joined #openstack-meeting13:52
*** tongli has joined #openstack-meeting13:54
*** jjmb has joined #openstack-meeting13:54
*** jjmb has quit IRC13:54
*** vkmc has joined #openstack-meeting13:55
*** MaxV has joined #openstack-meeting13:55
sc68calHello everyone13:56
*** noslzzp has joined #openstack-meeting13:56
sc68calAgenda for the ipv6 meeting - https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam#Agenda_for_Jan_21st13:57
*** thuc has joined #openstack-meeting13:57
*** yaguang has quit IRC13:58
*** dcramer_ has quit IRC13:58
dzyuHi dzyu in here14:00
*** dprince has joined #openstack-meeting14:00
xuhanphello14:00
sc68cal#startmeeting neutron_ipv614:00
openstackMeeting started Tue Jan 21 14:00:08 2014 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron_ipv6)"14:00
openstackThe meeting name has been set to 'neutron_ipv6'14:00
sc68calHello everyone - thanks for being here14:00
*** lblanchard has joined #openstack-meeting14:00
*** coolsvap has joined #openstack-meeting14:00
sc68cal#topic recap previous meeting14:00
*** openstack changes topic to "recap previous meeting (Meeting topic: neutron_ipv6)"14:00
sc68calAgenda for the ipv6 meeting - https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam#Agenda_for_Jan_21st14:01
*** ivasev has joined #openstack-meeting14:01
sc68calLast week the only real action item we had was for shshang to send an e-mail to the mailing list about a new set of attributes14:01
sc68calhe does not appear to be on - so we'll have to see if he joins late14:02
xuhanpyep. I saw that one and your last comment about which commit it should go to.14:02
*** shshang has joined #openstack-meeting14:02
xuhanpthere is shshang14:03
sc68calshshang: welcome14:03
shshangGood morning! Good Night!14:03
*** jroovers has quit IRC14:03
*** jroovers has joined #openstack-meeting14:03
dzyuGood morning! shshang14:04
sc68calshshang: we had an action item last week for you - do you have any progress to share?14:04
sc68cal"14:04
sc68calshshang send e-mail to mailing list regarding new attribute14:04
sc68cal"14:04
shshangI did, but I am waiting for Anthony and Ian to confirm.....14:04
*** aveiga has joined #openstack-meeting14:05
shshangit is not the ultimate solution, but I think we can live with that in Icehouse release while waiting for API to settle down14:05
shshanglet me sent the email to the mailer, so everybody here can take a look14:06
*** dims has quit IRC14:06
sc68calIt's probably going to take a while to propogate, so can you share it here14:06
shshangAs we discussed last time, we need a pair of keywords14:07
shshangthe first one is to control whether RA is sent and which bits are set14:08
*** jdob_ has joined #openstack-meeting14:08
shshangthe second one is to control who manage the address assignment leverage DHCPv614:08
*** ryanpetrello has quit IRC14:09
*** jorisroovers has joined #openstack-meeting14:09
shshangBut since Neutron team want backward complaintability and a boolean value, and we are stuck to enable_dhcp.14:10
shshangthe table included in the email was created to see whether we can take advantage of what we have so far to move the needle forward14:10
shshangit is surely not the BEST solution, but before API decision is made, it is one of the alternate solutions.14:11
shshangDid you guys get the email?14:11
*** jrist has joined #openstack-meeting14:11
xuhanpnot yet14:12
sc68calnot yet - so we may need to move discussion to the ML14:12
dzyuis the link: http://lists.openstack.org/pipermail/openstack-dev/2014-January/024179.html?14:12
*** jrist has quit IRC14:12
shshanglet me verbally summarize it....14:12
*** jroovers has quit IRC14:12
shshangAnthony made an excellent point over and over again, which I overlooked before14:13
aveigaI did?14:13
shshangoh, you are HERE! I thought you are hidden. :D14:13
shshangaveiga, I think you can explain your thoughts better than me. :D14:14
aveigaI got in late14:14
aveigasome mixups with an exchange server :/14:14
*** jrist has joined #openstack-meeting14:15
sc68cal#topic blueprints14:15
*** openstack changes topic to "blueprints (Meeting topic: neutron_ipv6)"14:15
shshangyou want to explain to the crew members on the neutron+ipv6 boat?14:15
aveigaI think sc68cal is interesting in moving the topic14:15
aveigaand I'm not sure what you wanted to dicsuss14:15
sc68caljust keeping the topic current14:15
shshangOK, then we can discuss it further in ML14:15
*** vkmc has quit IRC14:15
aveigasorry, someone catch me up then14:16
sc68calOK - so there's a proposal to make additional attributes and replace the subnet_mode attribute14:16
shshangaveiga, would u plz do me a huge favor verifying the table included in the email to the ML?14:16
shshangI need your expertise there14:17
aveigashshang: when I receive it I will, the ML usually takes a good half hour to get to me14:17
sc68calIs the plan for this to be replacing our current code review, or an addition?14:17
*** changbl has quit IRC14:17
*** jrist has quit IRC14:17
sc68calI asked on the ML - http://lists.openstack.org/pipermail/openstack-dev/2014-January/024902.html14:17
aveigasc68cal: I think the idea was to change it from subneet_mode to addressing mode and routing mode14:17
aveigaotherwise, we would just have to make subnet_mode a full matrix of permutations14:18
*** jrist has joined #openstack-meeting14:18
sc68calIt sounds like the answer is "replace"14:18
aveigawith the intent to decouple them, as people have been seeing both in the IPv6 world and even in today's mail in the IPv4 world, sometimes you want an external system to handle certain bits14:18
aveigawe should be functional, but also be able to get out of t he way if another solution is brought in place14:19
aveigai.e. be modular14:19
*** dims has joined #openstack-meeting14:19
aveigaso if you're using a provider net router but want OpenStack to do addressing, we just need the address bit and no RA14:19
aveigaor if we want OpenStack to do the routing but we need a specific DHCPv6 server to comply with some policy, we could run just the routing bits and don't run addressing14:20
aveigahonestly, it's fine either way14:20
aveigait really becomes an implementation decision14:21
sc68calMy concern with this is that we're going to have to do a full 180* on this, so I don't know if we'll be able to make anything for Icehouse with this new proposal14:21
*** yassine has quit IRC14:21
aveigawhether you want to enumerate and loop through all the permutations or split the function and the parameters14:21
aveigawell, then keep it to the full list of permutations14:22
*** yassine has joined #openstack-meeting14:22
aveigaand leave some of them "cuirrently unimplemented"14:22
*** dvarga has joined #openstack-meeting14:22
*** yaguang has joined #openstack-meeting14:22
aveigabut there's the whole issue of folks wanting the enable_dhcp attribute to still be there14:22
aveigapersonally, t hat's a bad idea, as DHCPv6 isn't a binary on/off14:22
*** ijw has joined #openstack-meeting14:23
ijw2 weeks running, *sigh*14:23
aveigaand the permutation idea doesn't work unless the value of enable_dhcp actually matches14:23
aveigaor we ignore it14:23
ijwI'm going to jump in without the prior discussion on this - what the cores want from enable_dhcp is that, if it's false, nothing transmits DHCP *or* RAs14:23
aveigathat makes a little more sense14:24
aveigabasically disable the network management functions14:24
ijwSo I would use it as a global disable flag, and then use other flags (with defaults that match Neutron's current behaviour) for the specific choice of behaviour we want14:24
ijwyup14:24
xuhanpso what happen when enable_dhcp is true?  RA or DHCP?  or depends on the other attribute to decide?14:25
aveigayes, the other attribute becomes important14:25
aveigaand even then, it could still be disabled if the other attribute is set off/off14:26
aveigabut it passes control to the other attribute14:26
ijwYup, indeed14:27
xuhanpthen we probably should not allow that to be happen since it doesn't make sense to end user.14:27
aveigasc68cal: if we did the permutations as values, do you still think we'd delay past Icehouse?14:27
ijwenable_dhcp becomes a backward compatibility thing, really14:27
*** Mandell has joined #openstack-meeting14:27
*** vijendar has joined #openstack-meeting14:27
aveigaI'm still uncomfortable with one value to control multiple subsystems, but I'll accept it in the name of progress14:28
*** toan-tran has joined #openstack-meeting14:28
ijwaveiga: If we have a DHCPv6 server independent of an RA server, and we use something specifically RA-sending like RADVD so that we have the maximum of control over RAs, then can we implement the two attributes entirely independently of each other?14:28
aveigaijw: yes, but you joined after sc68cal mentioned that would push us out too far14:28
sc68calaveiga: we'd need to see the proposal to get a good idea. However, I'm very concerned about how it's now basically I-2 and we've got nothing off the ground, and now we're going to do a whole re-arch14:29
*** eharney has joined #openstack-meeting14:29
*** anniec has joined #openstack-meeting14:29
*** jpich has joined #openstack-meeting14:29
*** jjmb has joined #openstack-meeting14:29
dzyuthe other attribute should be what? boolean?14:29
shshanganother attribute is values14:29
aveigadzyu: nope, no booleans here14:29
sc68calI know that my change wasn't great- but it was proposed back in November - it's had a bit of time to bake and it still hasn't gone far14:30
shshangyou will see more details in the email. It listed all possible values14:30
*** thuc has quit IRC14:30
sc68calHas any code been written for this new proposal?14:31
*** joesavak has joined #openstack-meeting14:31
*** thuc has joined #openstack-meeting14:31
shshangI got most of the dnsmasq part of the code done with the exception of two scenarios. I am still researching on it.14:31
*** doug_shelley66 has joined #openstack-meeting14:31
shshangit is 75% complete14:31
shshangI should get it out by tomorrow14:31
shshangbut that is only 1 piece of the puzzle14:32
*** anniec_ has joined #openstack-meeting14:32
ijwaveiga: the bit I'm missing, I think, is what we could implement that we would be able to do in time and wouldn't have us screwed for backward compatibility14:32
sc68calOK - has anyone added the attribute to the API, and the db migration, as well as additions to the db_base_plugin_v2 ?14:32
*** banix has joined #openstack-meeting14:32
xuhanpdzyu and I can help with that if that's needed urgently14:33
dzyuYes14:33
xuhanpyou know, to speed up this14:33
ijwsc68cal: and that's important - if we do put this out and it's wrong we are stuck with it for at least a year till the v2 api goes away14:33
shshangxuhanp, and dzyu, that will be AWESOME!14:33
aveigawe need to get the attributes nailed down for that work to happen at all14:33
shshangyes14:34
sc68calIf you guys share the details - I can rework my piece to fit what you guys are proposing14:34
aveigaso one attribute or two?14:34
*** jdob_ has quit IRC14:34
xuhanpand will dzyu's address calculating code still be useful?14:34
shshangI vote for two14:34
aveigaxuhanp: yup14:34
*** anniec has quit IRC14:34
xuhanpwe get that based on Sean's current code now.14:34
*** anniec_ is now known as anniec14:34
shshangxuhanp, yes, that part is still valid14:34
ijwI think two and I think we have to write this in the BP so that everyone's clear what it is - we've been discussing it in private and that is, I suspect, not helpful sc68cal's opinion of us ;)14:35
sc68calNo - it has not made me happy14:35
aveiga+114:35
aveigaok, let's get the BP setup for the two attributes then14:35
*** thuc has quit IRC14:36
sc68calWho should I make responsible for that14:36
aveigawe can mostly ignore enable_dhcp except to say that if it's off, everything is disabled14:36
dzyuyes14:36
shshangcan everybody review the email in the ML, and then nail down the values first?14:36
shshangthen we can create BP?14:36
shshangand then we can code?14:36
xuhanpsure. then also talk about the code assignment in the ML?14:37
shshangYup14:37
shshangthat is the fastest way to get everybody aligned14:37
*** jbrogan has joined #openstack-meeting14:38
*** nermina has joined #openstack-meeting14:38
shshangI can set up a BP in the next 10 mins. Very simple. Just to capture the discussion with aveiga and ijw. It should be immediately available to everybody.14:39
shshanginstead of waiting for ML14:39
*** fnaval has quit IRC14:40
sc68cal#action shshang register new blueprint for IPv6 attributes14:40
sc68cal#action aveiga ijw shshang discuss new IPv6 attributes on ML14:41
sc68calEveryone else - please participate as well14:41
*** otherwiseguy has joined #openstack-meeting14:41
sc68calI spoke with core devs yesterday and they are looking out for e-mails regarding this14:41
*** SergeyLukjanov is now known as SergeyLukjanov_a14:42
sc68calI don't have anything else, so open discussion?14:42
xuhanpI have a bug opened by ijw which I want to have a quick talk.14:42
sc68calok - we can do that14:42
sc68cal#topic bugs14:42
*** openstack changes topic to "bugs (Meeting topic: neutron_ipv6)"14:43
sc68calhave a link handy?14:43
xuhanphttps://bugs.launchpad.net/neutron/+bug/126275914:43
xuhanpI was trying to help on this one since it's IPv6 related14:43
*** SergeyLukjanov_a is now known as SergeyLukjanov_14:43
xuhanpbut I have some confusion about it.14:43
sc68cal#link https://bugs.launchpad.net/neutron/+bug/1262759  ICMPv6 RAs should only be permitted from known routers14:43
ijwOK - the issue is that Linux will take an RA from anyone.  It's a tart, basically14:43
*** mdomsch has joined #openstack-meeting14:43
xuhanphttps://github.com/openstack/neutron/blob/master/neutron/db/securitygroups_rpc_base.py#L28414:43
xuhanpbut looking at the code here14:43
xuhanpI can see there is already some rules for tenant RA from dhcp port14:44
aveigaxuhanp: that's only part of the puzzle14:44
*** prad has joined #openstack-meeting14:44
aveigawe need to allow external gateways (provider networks) and advances services VMs as well14:45
xuhanpI know we are trying to separate the RA from dhcp, but is it missing other things?14:45
ijwHmm14:45
ijwyou know, I didn't know that was there14:45
*** coolsvap_away has joined #openstack-meeting14:45
xuhanpthat's sc68cal was trying to do in his patch: https://review.openstack.org/#/c/53028/914:45
xuhanpright?14:45
*** aignatov is now known as aignatov_14:45
xuhanpaveiga?14:45
*** trey_h has joined #openstack-meeting14:46
*** prad has quit IRC14:46
aveigayes, that was the intent14:46
aveigabut sc68cal basically opened up all RAs14:46
*** rakhmerov has joined #openstack-meeting14:46
*** gokrokve has joined #openstack-meeting14:46
aveigain the itnerest of working first, secured later14:46
aveigaideally, the admin should register these things as Routers in Neutron14:46
xuhanpaveiga, are you saying we need a config list to let admin/user specify the router address to allow only them?14:47
aveigaand we should accept all RAs from Routers14:47
sc68calI believe the fix is remove the RA from ICMPV6_ALLOWED_TYPES, then add a function similar to that function in security_groups_rpc that looks up the gateway and other services, and adds a rule that allows in the ICMPv6 type for RAs14:47
aveiga+1 to sc68cal14:47
aveigathat's the ideal way14:47
shshangagree14:47
*** coolsvap has quit IRC14:47
sc68calI have a patch that is WIP adding a function that does just that to security_groups_rpc14:47
ijwxuhanp: that original assumes RAs come from the DHCPv6 server and that would be the problem I think14:47
*** coolsvap_away is now known as coolsvap14:48
ijwIt should be operating on the list of known routers (which should include both internal and external ones)14:48
xuhanpsc68cal, when you say the gateway and other services, do you mean the provider network?14:48
xuhanpI mean the external ones?14:48
sc68calxuhanp: provider network sets the gateway - it's just an external gateway14:48
aveigaijw: actually, it would not impede it14:48
aveigaif you moved the RA to the router namespace, then the gateway rule would still allow the RA14:49
aveigait would just leave an opening for the DHCP namespace to also send one14:49
*** kevinconway has joined #openstack-meeting14:49
aveigawhich shouldn't happen if the implementation is intelligent enough to split the RA to the rotuer namespace anyway14:49
*** ayoung has joined #openstack-meeting14:50
*** tshirtman has quit IRC14:50
*** tshirtman has joined #openstack-meeting14:50
ijwaveiga: cross purposes, I think - I was talking about the current code that xuhanp pointed at14:50
aveigayep14:50
aveigaI get it knwo14:50
aveiganow*14:50
*** dcramer_ has joined #openstack-meeting14:50
*** changbl has joined #openstack-meeting14:50
*** SergeyLukjanov_ is now known as SergeyLukjanov14:50
*** rakhmerov has quit IRC14:50
shshanghttps://www.dropbox.com/s/kyh7vpty0nugaza/IPv6%20Two%20Modes.pdf14:51
shshangThis is the table in my email to the ML14:51
shshangI just uploaded to the dropbox14:51
xuhanpsc68cal, do you have a blueprint for that WIP code change?  Can I help on that too?14:51
*** armax has joined #openstack-meeting14:51
xuhanpjust a great opportunity to get familiar with these stuff.14:52
*** aignatov_ is now known as aignatov14:52
sc68calxuhanp: no bp for it, I was just going to add a Bug # to the commit message - but yeah I'll make sure to announce it on the ML and share the link next week worst case14:52
sc68calI'll probably get it posted to gerrit this week14:52
shshangsc68cal, here is the new BP I created. https://blueprints.launchpad.net/neutron/+spec/ipv6-two-attributes14:53
xuhanpsc68cal, OK. let me know what I can help here. Thanks14:53
shshangeverybody, please help review........14:53
sc68calso it's really only one *new* attribute14:53
shshangYUP14:53
aveigashshang: no, don't reference enable_dhcp14:53
aveigathat needs to be another attribute14:54
shshangOK!14:54
shshangI will change it14:54
aveigait's not dhcp14:54
aveigait's addressing14:54
*** boris-42 has quit IRC14:54
*** markpeek has joined #openstack-meeting14:55
sc68cal#topic open discussion14:55
*** openstack changes topic to "open discussion (Meeting topic: neutron_ipv6)"14:55
aveigaSLAAC is part of it, because if SLAAC is on we need to determine the EUI-64 address and provide it to Neutron14:55
shshangTrue14:55
*** amotoki has quit IRC14:55
shshangI am updating it now14:55
xuhanpshshang, is the PDF same with the email in ML?14:55
shshangthank you for pointing it out14:55
*** jbrogan has quit IRC14:55
*** dvarga is now known as dvarga|away14:55
shshangthe email included the same table as pic14:55
*** dvarga|away is now known as dvarga14:55
xuhanpgot it14:56
shshangThe PDF is also in my dropbox. I can send you the PDF if you need it.14:56
xuhanpyes, please. pengxuhan@gmail.com   Thank you14:56
*** terriyu has joined #openstack-meeting14:57
shshangPlease provide your feedback on ML, so we can capture them to finalize the BP14:57
sc68calmake sure that BP is linked to the IPv6 feature parity BP14:57
*** IlyaE has joined #openstack-meeting14:57
shshangsc68cal, yup, I am doing it no14:58
shshangnow14:58
*** jorisroovers has quit IRC14:58
shshangsc68cal, do you think we can nail down the attributes by tomorrow?14:58
shshangor in the next 48 hours?14:58
aveigadepends on the BP and the ML feedback14:58
aveigabut we should be able to14:58
sc68calif I've got good doc - I can rework my review to add the second attribute, and rename dhcp_modes to the first14:59
dzyuyes, it will be more easy than replace it14:59
*** trey_h_ has joined #openstack-meeting14:59
shshangsc68cal, linked it to your original BP15:00
sc68calyep - plus dzyu's logic for when to do SLAAC cn be reused15:00
shshangand I will put you as approvor15:00
sc68calalright everyone - to the mailing list!15:01
sc68cal#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:01
openstackMeeting ended Tue Jan 21 15:01:05 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-01-21-14.00.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-01-21-14.00.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-01-21-14.00.log.html15:01
*** mspreitz has joined #openstack-meeting15:01
n0ano#startmeeting gantt15:01
openstackMeeting started Tue Jan 21 15:01:19 2014 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: gantt)"15:01
openstackThe meeting name has been set to 'gantt'15:01
n0anoanyone hear to talk about the scheduler?15:01
garykhi15:01
toan-trani'm here, hi all15:01
*** doron_afk is now known as doron_15:01
doron_hi15:01
johnthetubaguyhi15:01
*** doron_ is now known as doron15:02
coolsvaphi15:02
*** oubiwann_ has joined #openstack-meeting15:02
alaskihi15:02
*** dzyu has left #openstack-meeting15:02
*** jcoufal has quit IRC15:02
mspreitzo/15:02
*** jcoufal_ has joined #openstack-meeting15:02
n0anoI wanted to talk about no db but boris doesn't seem to be on yet, let's go to the code forklift first15:02
*** shshang has quit IRC15:02
n0ano#topic code forklift15:02
*** openstack changes topic to "code forklift (Meeting topic: gantt)"15:02
n0anohopefully all have seen the email thread on the devel list...15:03
*** trey_h has quit IRC15:03
*** spzala has joined #openstack-meeting15:03
n0anowe've decided to get the new gantt tree working first, and then re-sync (probably by recreating the tree) to the nova tree15:03
n0ano(rather than trying to continuously keep in sync with the nova tree)15:04
n0anoto that effort, there are 3 primary top level goals:15:04
n0ano1)  integrate with devstack15:04
n0ano2) get the unit tests to work15:04
*** jroovers has joined #openstack-meeting15:04
n0ano3) integration tests working15:04
*** vkozhukalov has quit IRC15:04
garyksorry, not sure that i follow15:05
n0anoI've actually done task 1, the patches for devstack are posted and awaiting review15:05
garykinstead of running n-sched will we be running gantt on devstack?15:05
*** glikson has joined #openstack-meeting15:05
*** chmouel has quit IRC15:05
*** chmouel_ has joined #openstack-meeting15:05
*** jorisroovers has joined #openstack-meeting15:05
*** fnaval has joined #openstack-meeting15:05
alaskin0ano: do you have links for the devstack patches?15:06
garykthe review is https://review.openstack.org/#/c/67666/15:06
n0anogaryk, the idea is that you can ask devstack to include gantt rather than n-sch (the same way you can ask for neutron vs. n-net)15:06
*** chmouel_ is now known as chmouel15:06
garykn0ano: thanks15:06
*** PaulMurray has joined #openstack-meeting15:06
*** pnavarro has joined #openstack-meeting15:07
*** prad has joined #openstack-meeting15:07
n0anosurprisingly enought, asking for gantt rather than n-sch works (you wind up calling into nova code but it installs the gantt tree and starts things out from the top of the gantt tree)15:07
garykthanks, i will take alook at it. is the jenkins −1 due to the grumpy old man or a real issue?15:07
n0anogaryk, yep, grump old man (I think is the dsm which seems to always fail)15:07
*** Gordonz has joined #openstack-meeting15:08
*** Gordonz has quit IRC15:08
*** yassine has quit IRC15:08
*** emagana has joined #openstack-meeting15:08
*** vkmc has joined #openstack-meeting15:08
*** vkmc has quit IRC15:08
*** vkmc has joined #openstack-meeting15:08
n0anoso yeah, reviewing the devstack patches would be great, I'd love to get that in.15:08
*** Gordonz has joined #openstack-meeting15:08
*** yassine has joined #openstack-meeting15:09
n0anoI've looked at task 2 & 3 and they are not totally trivial15:09
garyki'll look at the devstack15:09
*** jroovers has quit IRC15:09
n0anofor 2, getting the service started has some futzy issues that need to be dealt with, I'm looking at it and not getting far...15:10
*** ryanpetrello has joined #openstack-meeting15:10
n0anofor 3, I'm missing something obivious, the testing harness won't allow includes from nova so you wind up pulling half the nova tree over, not what we want15:10
alaskiis #3 tempest tests, or something else?15:11
johnthetubaguybut surely, you don't need to change any of the tests?15:11
n0anojohnthetubaguy, I would hope the tests would only need a change to an import line at most, the body of the test wouldn't change15:12
johnthetubaguyah, sorry, I mean tempest tests15:12
johnthetubaguythey should just run as normal15:12
n0anoalaski, I believe that run_tests.sh calls testr (with a virtual environment) and that doesn't seem to allow imports from nova15:12
johnthetubaguyunit tests will take some care, mostly the whole DB hooks thing15:12
johnthetubaguyn0ano tox is used in the gate, but almost the same difference15:13
n0anojohnthetubaguy, true but we want to be just a drop in for now, utilizing code for things like DB access from nova should be fine15:13
*** emagana has quit IRC15:13
n0anojohnthetubaguy,  yeah, I did tox manually and, as I remember, I hit the same issue15:13
alaskiI think of run_tests.sh/tox as unit tests, and tempest as integration tests.  And integrating with devstack basically gives you integration for free15:14
toan-trann0ano so basically we can re-run tests with import gannt instead of nova?15:14
toan-trangantt15:14
johnthetubaguytempest talks directly to the nova cli, so shouldn't need any imports, the unit tests are how we test if we brake the dependence on nova I guess?15:14
n0anotoan-tran, sort of, we want to import scheduler code from gantt but nova specific code (like DB) should come from nova, we don't want to duplicate the nova tree15:14
johnthetubaguyseem like we would need to stop accessing the nova db, and copy the bits that the scheduler needs for its own db?15:15
johnthetubaguybut maybe I am complicating things?15:15
n0anojohnthetubaguy, not sure what you mean, all I know is many python files in gantt/tests import nova objects15:15
alaskiyeah, gannt right now needs pretty deep nova knowledge15:16
johnthetubaguyyeah, we only need to run the unit tests in the scheduler sub directory though15:16
n0anojohnthetubaguy, it's more than that, it's not just the DB, it things like objects and others15:16
johnthetubaguyOk, so its import nova, make it run, then cut the links I guess?15:16
johnthetubaguythats fair enough15:16
toan-tranjohnthetubaguy you're suggesting fork out db, which is no-db approach15:16
n0anojohnthetubaguy, +115:16
garykyup, at the moment it is solely dependant on nova na dwill most probaly need a complete overhaul when we start to add cross service support15:16
johnthetubaguytoan-tran: not really, its cut and paste db code, but importing nova will do the same for now15:17
n0anogaryk, +1 (that's all part of our wold domination plan :-)15:17
johnthetubaguyyeah, just not sure if the gate can deal with all this15:17
johnthetubaguywait, I guess it can, ignore me15:17
*** trey_h_ has quit IRC15:17
garykis there anyway to have a symbolic link to the nova master branch in git?15:17
alaskin0ano: adding nova to test-requirements isn't enough?15:17
*** trey_h has joined #openstack-meeting15:18
n0anoalaski, I might be an idiot, I didn't think of that, let me get back to you, this might be a simple problem.15:18
johnthetubaguywell, its a bit tricker, you need the version zuul wants to give you and is installed on that machine15:18
johnthetubaguyI guess requiirements file could link to src in /opt/stack/nova or something like that15:19
johnthetubaguycan't remember the details now15:19
n0anoI'm play with it (I've totally corrupted my working gantt tree for now, it'll take me a bit to try this but it sounds promising)15:19
n0anos/I'm/I'll15:20
*** mrunge has quit IRC15:20
n0anodoes anyone have any cycles to look at getting gantt to actually work?  e.g. deal with the process startup issues15:21
garyki may have next week. not sure at the moment though15:21
alaskin0ano: I don't this week, but I'd like to help so I'll stay hopeful for next week15:22
*** aveiga has left #openstack-meeting15:22
coolsvapn0ano: I can try this week15:22
garyksorry, but could not resists, do we have a gantt with what all of our resources are doing?15:22
n0anonot to worry, it'll probably take me most of this week to get the unit tests working, there'll be plenty of work still available next week.15:22
*** paragan has quit IRC15:22
toan-tranI have a question, stupid maybe,15:22
johnthetubaguyn0ano: another week it would be yes, sorry15:22
*** mattgriffin has joined #openstack-meeting15:23
n0anotoan-tran, go ahead15:23
toan-tranhow is that different from having nova-scheduler separated from other nova services, and gannt?15:23
toan-tranin code separation, I mean15:23
toan-tranwhen I install nova-scheduler separated from others, the nova code is duplicated15:24
n0anotoan-tran, not sure what your question is, what we need is the ability to start a sheduler from the gantt tree, have it call gantt `scheduler` code (calling nova code for DB, objects and what not is OK)15:24
toan-traninstalling gantt should be the same, no?15:24
toan-tranI mean, for now, as we have the same code in nova and in gantt15:25
n0anotoan-tran, currently most of the code in the gantt tree includes modules/classes from nova, some of those imports need to be from gantt, some need to remain nova15:25
toan-traninstalling gantt on another server is like installing nova-scheduler on it15:25
*** marun has joined #openstack-meeting15:25
*** sfineberg has quit IRC15:25
alaskitoan-tran: gantt needs to be able to use nova like a library for now, not have it in the source tree.  while nova-scheduler is installed with it all together15:26
*** uaberme has quit IRC15:26
johnthetubaguyalaski: +115:27
n0anoalaski, what he said15:27
toan-tranok, so basically we need to tell gantt to use nova code, not use its local lib15:27
toan-tranor import nova lib from somewhere else15:27
n0anotoan-tran, for nova things, for scheduler code we want gantt to include the gantt code15:27
*** stevemar has joined #openstack-meeting15:28
toan-trann0ano thanks15:29
n0anogaryk, in re a gantt of our gantt work - not yet, we at the stage where we don't even know what all the tasks are until we do the task...15:29
*** Linz has quit IRC15:29
n0anoafter we get the top 3 goals accomplished I think we can make a more detailed plan15:29
toan-tranwihch step intergrates gantt with nova/keystone?15:30
*** rnirmal has joined #openstack-meeting15:30
toan-tranI mean, for now nova list nova-scheduler in its service list, with host IP and all15:31
toan-tranbut gantt is outsider, so basically nova-conductor should contact keystone for its endpoint15:31
n0anowill be running the same code, whether from the gantt tree or the nova tree, so that should work the same15:31
*** nelsnelson is now known as nelsnelson_away15:32
*** nelsnelson_away is now known as nelsnelson15:32
n0anonote that n-sch already runs as a separate process, that doesn't change15:32
*** Linz has joined #openstack-meeting15:32
toan-trann0ano just tapping in the rabbitmq channel?15:32
*** elo has quit IRC15:32
n0anoshould do the same taps into the same channel15:33
*** minminren has joined #openstack-meeting15:33
*** minminren has quit IRC15:34
*** otherwiseguy has quit IRC15:34
*** nelsnels_ has joined #openstack-meeting15:34
n0anoI think that's about all on this subject for now, since boris isn't here johnthetubaguy  you wanted to talk about:15:35
n0ano#topic caching scheduler15:35
*** openstack changes topic to "caching scheduler (Meeting topic: gantt)"15:35
*** jecarey has joined #openstack-meeting15:35
*** yassine has quit IRC15:35
johnthetubaguyyeah, I have an idea/blueprint15:35
*** nelsnels_ has quit IRC15:35
*** yassine has joined #openstack-meeting15:35
johnthetubaguyhttps://blueprints.launchpad.net/nova/+spec/caching-scheduler15:35
*** fifieldt has joined #openstack-meeting15:35
*** dvarga is now known as dvarga|away15:35
*** dvarga|away is now known as dvarga15:35
johnthetubaguyI have a review up15:35
johnthetubaguygood to get your feedback15:36
*** nelsnels_ has joined #openstack-meeting15:36
johnthetubaguybasic idea15:36
johnthetubaguydo expensive things up front15:36
*** jjmb has quit IRC15:36
*** nelsnelson has quit IRC15:37
*** jchiles has joined #openstack-meeting15:37
*** tanisdl has joined #openstack-meeting15:37
n0anoone question, how does this fit with the current filters/weights, can you still specify a set of filters15:37
garykjohnthetubaguy: in certain cases we can cache things, but when there are changes to the system it becomes very difficult. do you have some doc describing what you are doing?15:38
johnthetubaguynot really, the idea is it responds to scheduler update in the cache15:38
johnthetubaguymy basic idea, lets try it15:38
gliksonjohnthetubaguy: interesting idea, will take a look15:39
toan-tranwhat kind of information/decision that you cache ?15:39
johnthetubaguyI hope we start having many drivers15:39
johnthetubaguythat get documented15:39
n0anogaryk, does raise a good question, what happens when your cache gets stale?15:39
johnthetubaguybasically cache chose hosts for specific partial request-specs15:39
*** nati_uen_ has quit IRC15:40
alaskiyeah.  I chatted with johnthetubaguy about this in person last week, and what I really like is starting to have differentiated scheduler drivers that may have different features/characteristics.15:40
toan-tranalaski: meaning ?15:40
garykalaski: if the work load are homogenous then that could be a nice solution.15:41
johnthetubaguyn0ano: it has a periodic task to keep the cache fresh15:41
alaskitoan-tran: something like, maybe I don't care about supporting affinity/anti-affinity so I can choose a driver that doesn't have it but is blazing fast.  Or maybe I dont' care about speed and can use a complex sat solver for all my placements, etc...15:42
*** emagana has joined #openstack-meeting15:42
gliksonregarding having different drivers -- do we also expect the user-facing APIs to be different? e.g., today's filters/hints?15:42
*** galstrom_zzz is now known as galstrom15:43
johnthetubaguyhopefully not15:43
alaskiglikson: I would expect some change eventually. but I think that should happen anyways.15:43
johnthetubaguyit might be some don't work15:43
*** nelsnels_ has quit IRC15:43
alaskischeduler hints are a poor api right now, because there's no feedback on whether or not they were used15:44
johnthetubaguythats very true15:44
*** nelsnelson has joined #openstack-meeting15:44
*** Linz has quit IRC15:45
gliksonone of the ideas we have been discussing internally was to separate the placement calcuation logic from the logic/API specifying 'inputs' (constraints, etc). right now the two are rather tightly coupled..15:45
johnthetubaguymy basic points are, lets don't be afraid to break things, try things, but do it in different drivers15:45
n0anoraising questions of latency and recovery from invalid cache entries, theoretically it could work but the devil is in the details.15:45
*** otherwiseguy has joined #openstack-meeting15:46
*** rakhmerov has joined #openstack-meeting15:46
alaskiglikson: I agree.  I think there's a layer of abstraction missing from scheduling15:46
*** samuelbercovici has joined #openstack-meeting15:46
*** jecarey has quit IRC15:46
*** emagana has quit IRC15:47
johnthetubaguyglikson: that makes sense15:47
gliksonhopefully having the code separately (whatever that means) would make it easier to evolve..15:47
toan-tranglikson +115:47
toan-tranthat's when i have to rethink of the gantt API15:48
toan-tran=))15:48
johnthetubaguytrue, when we have an gnatt API then it gets better15:48
*** lblanchard has quit IRC15:48
johnthetubaguydo people fancy giving this caching a go then?15:49
*** sandywalsh has joined #openstack-meeting15:50
toan-tranjohnthetubaguy count me in15:50
johnthetubaguyits going to be experimental in icehouse15:50
johnthetubaguybut its worth a whirl15:50
n0anojohnthetubaguy, sounds interesting to me, a proof of concept would be good15:50
garykjohnthetubaguy: i think that it is an intersting direction.15:50
coolsvapjohnthetubaguy: yes sounds interesting15:50
garykit is worth exploring and the fact that you have posted something gives us a way to play around with it15:50
johnthetubaguyI know the current stuff is quite broken right now15:51
johnthetubaguybut its gives you the idea15:51
garykcurrent schedulre or this :)15:51
*** lblanchard has joined #openstack-meeting15:51
*** NikitaKonovalov is now known as NikitaKonovalov_15:51
toan-tranit woud be greate if you have a google doc, not necessarity too detailed15:51
n0anotoan-tran, I'd prefer a wiki page, that's pretty standard for what we do.15:52
*** markwash has joined #openstack-meeting15:52
johnthetubaguyyeah, I can do something like that15:52
johnthetubaguyand attach to the blueprint15:52
n0anojohnthetubaguy, +115:53
johnthetubaguythe commit message and blueprint has all the data I have at the moment15:53
garykwould it be possible that people please take a look at the anti affinity patch with the instance groups.15:53
johnthetubaguybasically an idea, and I am testing it out15:53
garykhopefully this week there will be the API's for v2 and v3.15:53
n0anogaryk, are those APIs the last bits for this work?15:54
*** MaxV has quit IRC15:54
johnthetubaguygaryk: do we have those blueprints sponsored by anyone yet?15:54
garykjohnthetubaguy: they were approved in havana. we missed the dealine by a week. so it is just carried through. not sure who is sponsoring though15:54
johnthetubaguygaryk: I mean in terms of the nova blueprint process15:54
garyki do not think that anyone is sponsoring this at the moment.15:55
garykit was approved prior to the process discussed15:55
garykany takers?15:55
johnthetubaguyOK, not certain I have time, given all the other stuff, else I would offer, just wondered if anyone else was keen?15:55
gliksonif we are open for general discussion, I have similar request for the multi-sched patches..15:56
gliksonhttps://review.openstack.org/#/q/topic:bp/multiple-scheduler-drivers,n,z15:56
n0anoglikson, I pinged people for reviews at the last nova meeting, looks like that didn't have any impact :-(15:56
gliksonn0ano: thanks! we did have one new reviewer recently.15:57
gliksonbut the comments were mostly syntactical15:57
*** jcoufal_ has quit IRC15:57
*** SergeyLukjanov is now known as SergeyLukjanov_15:57
* n0ano strains to get hand to pat back :-)15:57
garykglikson: i have reviewed that pacth a number of times and it is starting to look good15:58
*** nshaikh has joined #openstack-meeting15:58
*** kebray_ has joined #openstack-meeting15:58
n0anocoming to the top of the hour, closing in 3...15:58
toan-tranglikson: i'll give it a try15:58
n0ano2...15:59
*** nshaikh has quit IRC15:59
mspreitzgaryk: which patch exactly?15:59
gliksongrayk: thanks. I hope that it is a matter of fixing small things, and we won't be surprised by major concerns few days/weeks before the feature-freeze..15:59
toan-tran the last time i saw it was not completed, so not sure what i've seen was kept ...15:59
gliksontoan-tran: thanks!15:59
n0ano116:00
n0anotnx everyone, talk to you next week.16:00
n0ano#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Tue Jan 21 16:00:19 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-01-21-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-01-21-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-01-21-15.01.log.html16:00
toan-tranbye16:00
*** jmontemayor has joined #openstack-meeting16:01
*** Leonr has joined #openstack-meeting16:01
*** ociuhandu has joined #openstack-meeting16:01
primeministerp#startmeeting hyper-v16:01
openstackMeeting started Tue Jan 21 16:01:47 2014 UTC and is due to finish in 60 minutes.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
*** jecarey has joined #openstack-meeting16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: hyper-v)"16:01
openstackThe meeting name has been set to 'hyper_v'16:01
*** colinmcnamara has joined #openstack-meeting16:01
primeministerphi everyone16:01
*** DinaBelova is now known as DinaBelova_16:02
*** boris-42 has joined #openstack-meeting16:02
*** alexpilotti has joined #openstack-meeting16:02
primeministerplet's wait a couple of minutes for the others to join16:02
pnavarrohi primeministerp !16:02
primeministerphi pedro16:03
alexpilottihi guys, my IRC client was off, sorry!16:03
primeministerpwondering if luis is coming16:03
*** toan-tran has quit IRC16:03
primeministerpok16:04
primeministerpguess we can begin16:04
*** thouveng has joined #openstack-meeting16:04
*** burt1 has joined #openstack-meeting16:04
primeministerp#topic CI16:04
*** openstack changes topic to "CI (Meeting topic: hyper-v)"16:04
primeministerpso some updates16:04
primeministerpwe've got everything running16:04
*** jieryn has joined #openstack-meeting16:05
*** jieryn has joined #openstack-meeting16:05
primeministerpand are currently finishing up some debugging after a rebalance of our resources16:05
*** glikson has left #openstack-meeting16:05
primeministerpwe have additionally complexity of having to use a combination of both iron and virtual resources for each test in our infra due lack of nesting support in hyper-v16:05
primeministerpociuhandu: how much more time until we fire the rest up?16:06
alexpilottiwe have some issues with Devstack BTW16:06
*** MaxV has joined #openstack-meeting16:07
primeministerpahh16:07
primeministerpalexpilotti: let's go through everything w/ the rest of the team after this meeting16:07
primeministerpas we have some overlap16:07
primeministerpin time and i'm not aware of those yet16:07
primeministerphad other fires this am16:07
ociuhanduprimeministerp: we're solving these now and we should go through all the remaining bits aftter the meeting, i think16:07
primeministerpociuhandu: perfect16:07
*** SumitNaiksatam has quit IRC16:07
*** nati_ueno has joined #openstack-meeting16:08
primeministerpso on that note there will be more to come16:08
primeministerp#topic heat16:08
*** openstack changes topic to "heat (Meeting topic: hyper-v)"16:08
primeministerpalexpilotti: you had some heat updates?16:08
alexpilottisure16:08
alexpilottiso, we have AD, MSSQL, Exchange and Sharepoint templates16:09
*** samuelbercovici has quit IRC16:09
*** xuhanp has quit IRC16:10
alexpilottiwe're now looking into all the Linux specific issues16:10
*** chandankumar_ has quit IRC16:10
alexpilottiwe need to work on the heat-cfntools to make them compatible with Windows16:10
alexpilotticloudbase-init works like a charm with heat16:11
*** cdub has joined #openstack-meeting16:11
*** mrodden has joined #openstack-meeting16:11
alexpilottiwe added also the management for reboots16:11
*** prad has quit IRC16:11
*** prad has joined #openstack-meeting16:12
primeministerpalexpilotti: execellent work16:12
alexpilottibasically if the userdata script returns with a given value, a reboot is triggered and the script gets re-executed on the next boot16:12
alexpilottithis way we can handle domain joins, etc16:12
alexpilottiHeat's waiting conditions work well for compelx scenarios16:12
alexpilottifor example waiting for an AD DC to be provisioned before installing Exchange16:12
primeministerpalexpilotti: windows is heavy on the "waiting conditions"16:13
alexpilottiwe're now looking into how to get cfn-hup to work for using stack-update in a useful way16:13
primeministerp;)16:13
alexpilottiI synced also with teh Heat guys, and got a BP for that:16:13
primeministerpalexpilotti: perfect16:14
primeministerpalexpilotti: do we have any new updates on ovs?16:14
alexpilotti#link https://blueprints.launchpad.net/heat/+spec/windows-instances16:14
alexpilottiyep, should we cange topic?16:14
primeministerp#topic openvswitch16:14
*** openstack changes topic to "openvswitch (Meeting topic: hyper-v)"16:14
alexpilotticool16:15
alexpilottiso OVS porting on Windows is geting close to completion16:15
*** hemna has joined #openstack-meeting16:15
alexpilottiwe have working GRE on the kernel vswitch extension16:15
*** markwash has quit IRC16:15
*** eharney has quit IRC16:15
alexpilottiand the userspace part is completed on teh stable branch of OVS16:16
primeministerpexecellent16:16
alexpilottipatch merging with the OVS community is also going on on the stable branch16:16
primeministerpbtw i believe they are starting to take presentation proposals for atlanta16:16
alexpilottiso, if somebody wants to be involved in the beta testing is a good moment :-)16:17
primeministerpwe should try to see if we can demo ovs16:17
primeministerpalexpilotti: you and I should sync on that16:17
primeministerpalexpilotti: we could beta on the sandbox16:17
alexpilottiyep, CFP ends on the 28th AFAIK16:17
primeministerpof jan?16:17
alexpilottiyep16:17
primeministerpkk16:17
alexpilottilet's sync offline!16:18
pnavarrome ! alexpilotti16:18
alexpilottipnavarro: ok! :-)16:18
*** topol has quit IRC16:19
*** gyee has joined #openstack-meeting16:19
*** trey_h has quit IRC16:19
pnavarroit's a pity VXLAN is not ready yet, because I have some vxlan deployment with ML2 plugin to test with16:19
alexpilottipnavarro: once we have GRE stable, adding VXLAN is going to be fairly easy16:21
alexpilottinow we have an annoying bug on IPv6 to get rid off, the rest works pretty well16:21
*** belmoreira has quit IRC16:22
primeministerpgrate16:23
primeministerper great16:23
primeministerpdoes anyone else have anything to add16:23
primeministerppnavarro: ?16:23
pnavarronothing to add, thanks16:24
primeministerpif not i"m going to end the meeting16:24
primeministerpthanks alexpilotti16:24
primeministerp#endmeeting16:24
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:24
openstackMeeting ended Tue Jan 21 16:24:35 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:24
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2014/hyper_v.2014-01-21-16.01.html16:24
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2014/hyper_v.2014-01-21-16.01.txt16:24
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2014/hyper_v.2014-01-21-16.01.log.html16:24
*** Leonr has quit IRC16:24
*** Leonr has joined #openstack-meeting16:25
*** Leonr has quit IRC16:29
*** ociuhandu has left #openstack-meeting16:30
*** mrodden has quit IRC16:30
*** dvarga is now known as dvarga|away16:30
*** dvarga|away is now known as dvarga16:30
*** aignatov is now known as aignatov_16:30
*** galstrom is now known as galstrom_zzz16:31
*** Leonr has joined #openstack-meeting16:31
*** SumitNaiksatam has joined #openstack-meeting16:32
*** DinaBelova_ is now known as DinaBelova16:33
*** eharney has joined #openstack-meeting16:33
*** sbalukoff has joined #openstack-meeting16:36
*** marekd is now known as marekd|away16:38
*** doron is now known as doron_afk16:38
*** mspreitz has left #openstack-meeting16:39
*** galstrom_zzz is now known as galstrom16:41
*** markwash has joined #openstack-meeting16:41
*** garyk has quit IRC16:41
*** sankarshan is now known as sankarshan_away16:42
*** Phil|2 has quit IRC16:44
*** vkmc has quit IRC16:44
*** thuc has joined #openstack-meeting16:45
*** Aarongr_afk is now known as AaronGr16:46
*** emagana has joined #openstack-meeting16:47
*** mdomsch has quit IRC16:47
*** pablosan has joined #openstack-meeting16:47
*** Mandell has quit IRC16:48
*** gokrokve has quit IRC16:49
*** ArthurBerezin has joined #openstack-meeting16:49
*** gokrokve has joined #openstack-meeting16:49
*** hartsocks has joined #openstack-meeting16:50
*** doron_afk has quit IRC16:50
*** mrodden has joined #openstack-meeting16:50
*** mdomsch has joined #openstack-meeting16:50
*** jmeridth has joined #openstack-meeting16:50
*** hartsocks has left #openstack-meeting16:51
*** gokrokve_ has joined #openstack-meeting16:51
*** topol has joined #openstack-meeting16:51
*** FallenPegasus has joined #openstack-meeting16:51
*** Duane_ has joined #openstack-meeting16:53
*** gokrokve has quit IRC16:54
*** yaguang has quit IRC16:55
*** fbo is now known as fbo_away16:55
*** MaxV has quit IRC16:56
*** fbo_away is now known as fbo16:57
*** doug_shelley66 has quit IRC16:57
*** DinaBelova is now known as DinaBelova_16:58
*** doug_shelley66 has joined #openstack-meeting16:58
*** bdpayne has joined #openstack-meeting16:58
*** neelashah has quit IRC16:58
*** neelashah has joined #openstack-meeting16:59
*** stanlagun has joined #openstack-meeting16:59
*** olkonami1 has joined #openstack-meeting17:00
boris-42#startmeeting Rally17:00
openstackMeeting started Tue Jan 21 17:00:55 2014 UTC and is due to finish in 60 minutes.  The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: Rally)"17:00
openstackThe meeting name has been set to 'rally'17:00
hughsaundershi boris-4217:01
boris-42hughsaunders hi17:01
boris-42who is here?)17:01
olkonami1hi all!17:01
miarmakhi17:01
stanniehi17:01
julienveyhi17:01
*** tnurlygayanov_ has joined #openstack-meeting17:01
*** I159 has quit IRC17:01
*** jbrogan has joined #openstack-meeting17:02
*** med_ has quit IRC17:02
boris-42oh seems I am not alone+) I should care what I am saying =)17:02
*** nati_uen_ has joined #openstack-meeting17:02
*** nati_uen_ has quit IRC17:02
boris-42topic HOT topics17:02
boris-42#topic HOT topics17:02
*** openstack changes topic to "HOT topics (Meeting topic: Rally)"17:02
hughsaundersboris-42: ~362 lurkers in this channel17:02
jieryn#17:03
*** nati_uen_ has joined #openstack-meeting17:03
tnurlygayanov_))17:03
*** medberry has joined #openstack-meeting17:03
*** medberry has joined #openstack-meeting17:03
boris-42lol=)17:03
*** nati_ueno has quit IRC17:03
boris-42So topic list:17:03
*** markwash has quit IRC17:03
*** neelashah has quit IRC17:03
boris-421) Rally & Tempest integrration17:03
boris-422) Rally & Running benchmarks against cloud (without admin endpoint)17:04
boris-423) Rally & Multihost deployments17:04
boris-424) Rally & Smart benchmark scenarios17:04
boris-42checkers17:04
boris-425) Rally as a Service17:05
boris-426) Improvements in Rally CLI17:05
boris-427) Rally & benchmarking performance of VMs17:05
*** hartsocks1 has joined #openstack-meeting17:06
boris-428) Rally use class instances for benchmark scenarions instead of class objects and classmethods17:06
*** fnaval_ has joined #openstack-meeting17:06
*** johnthetubaguy1 has joined #openstack-meeting17:06
boris-429) Rally measuring time of atomic actions17:06
*** hartsocks1 has left #openstack-meeting17:06
*** vkozhukalov has joined #openstack-meeting17:06
boris-42^ Thats all17:06
boris-42I will try to use this order in today meeting17:07
*** egallen_ has joined #openstack-meeting17:07
boris-42#topic Rally & Tempest integration17:07
*** openstack changes topic to "Rally & Tempest integration (Meeting topic: Rally)"17:07
boris-42miarmak pls could you share your results?17:07
*** yjiang5_1 has joined #openstack-meeting17:07
*** gokrokve_ has quit IRC17:08
boris-42(btw guys/girls if you are related to any of this parts prepare your updates)17:08
miarmakboris-42: unfortunately, situation has not changed from yesterday17:08
miarmakmain problem - conf generation17:08
*** saschpe has joined #openstack-meeting17:08
*** FallenPegasus has quit IRC17:08
*** mdbooth has quit IRC17:08
boris-42miarmak so you are not able to configure correct conf for tempest ^17:08
miarmakmaybe anyone know projects, that have smth same?17:08
boris-42probably sdague could help us? ^17:09
*** jbrogan has quit IRC17:09
*** julim has quit IRC17:09
*** johnthetubaguy has quit IRC17:09
*** niska has quit IRC17:09
*** alpha_ori has quit IRC17:09
*** saschpe_ has quit IRC17:09
*** dcramer_ has quit IRC17:09
*** egallen has quit IRC17:09
*** shadower has quit IRC17:09
*** Makdaam has quit IRC17:09
*** lifeless has quit IRC17:09
*** mrda_ has quit IRC17:09
*** shadower_ has joined #openstack-meeting17:09
*** mrda has joined #openstack-meeting17:09
*** lifeless1 has joined #openstack-meeting17:09
*** ArthurBerezin has quit IRC17:09
*** hemna has quit IRC17:09
*** fnaval has quit IRC17:09
*** afazekas has quit IRC17:09
*** matiu has quit IRC17:09
*** skraynev has quit IRC17:09
*** lijli has quit IRC17:09
*** yjiang5 has quit IRC17:09
*** jeblair has quit IRC17:09
*** skraynev has joined #openstack-meeting17:09
*** mdurnosvistov has quit IRC17:09
*** niska has joined #openstack-meeting17:09
*** afazekas has joined #openstack-meeting17:09
*** egallen_ is now known as egallen17:09
*** matiu has joined #openstack-meeting17:09
hughsaundersboris-42 mentioned that devstack configures tempest, so this may help: https://github.com/openstack-dev/devstack/blob/master/lib/tempest#L6617:09
*** lijli has joined #openstack-meeting17:09
*** alpha_ori has joined #openstack-meeting17:09
*** hemna has joined #openstack-meeting17:10
*** matiu has quit IRC17:10
*** matiu has joined #openstack-meeting17:10
boris-42hughsaunders ohhhh17:10
*** julim has joined #openstack-meeting17:10
*** dcramer_ has joined #openstack-meeting17:10
boris-42hughsaunders how much lines of code..17:10
*** jeblair has joined #openstack-meeting17:10
sdagueboris-42: if it's not a gate issue, I can't really help you this week17:10
boris-42sdague sure understand you, thank you for fixing gate!17:10
hughsaundersI'm going to attempt to chef-ify that for the stackforge chef cookbooks project17:10
boris-42hughsaunders how to generate proper config for tempest?17:11
*** morganfainberg has quit IRC17:11
*** morganfainberg has joined #openstack-meeting17:11
hughsaundersboris-42: yeah, not started yet, but planning to base it on that devstack function17:11
*** Makdaam has joined #openstack-meeting17:11
boris-42miarmak hughsaunders  could you probably collaborate around this?17:12
hughsaundersYeah, if I get anywhere I'll ping miarmak with a link17:12
boris-42hughsaunders nice17:12
boris-42#topic  Rally & Running benchmarks against cloud (without admin endpoint)17:12
*** openstack changes topic to "Rally & Running benchmarks against cloud (without admin endpoint) (Meeting topic: Rally)"17:12
miarmakok17:12
miarmakthanks17:12
boris-42So first of all17:13
boris-42#link https://blueprints.launchpad.net/rally/+spec/benchmarking-with-predefined-users17:13
boris-42^ bp17:13
boris-42#link https://review.openstack.org/#/q/status:open+project:stackforge/rally+branch:master+topic:bp/benchmarking-with-predefined-users,n,z17:13
boris-42patches on review ^17:13
*** jasondotstar has quit IRC17:13
boris-42The idea is simple17:13
boris-42Now Rally work in next way17:14
*** jbrogan has joined #openstack-meeting17:14
*** ivar-lazzaro has quit IRC17:14
*** dvarga is now known as dvarga|away17:14
*** dvarga|away is now known as dvarga17:14
boris-42get admin endpoints -> create admin clients -> create tmp tenants & users -> run from temp users benchmarks -> cleanup of cloud -> delete tmp users -> FINISH17:14
boris-42So it's work until we would like to test Public clouds17:15
boris-42where we don't have admin endpoints17:15
boris-42So we will add support of running benchmark from bunch of predefined users17:15
*** bdpayne has quit IRC17:15
*** jorisroovers has quit IRC17:16
boris-42input endpoints of non admin users -> create python clients -> run benchmarks -> make non admin cleanups17:16
*** neelashah has joined #openstack-meeting17:16
boris-42So if you will have some free time you can spend it reviewing that patches=)17:16
boris-42Does anybody has any questions?)17:16
hughsaundersseems like a good plan17:17
*** thuc has quit IRC17:17
boris-42stannie julienvey  thoughts?17:18
*** thuc has joined #openstack-meeting17:18
*** ildikov_ has quit IRC17:18
stannieseems good to me also17:18
boris-42okay nice then we will move just to next topic17:18
*** sushils has quit IRC17:18
boris-42#topic  3) Rally & Multihost deployments17:18
*** openstack changes topic to "3) Rally & Multihost deployments (Meeting topic: Rally)"17:18
*** MarkAtwood has joined #openstack-meeting17:18
boris-42#link https://blueprints.launchpad.net/rally/+spec/multihost-deploy17:19
boris-42bp ^17:19
boris-42#link https://review.openstack.org/#/q/status:merged+project:stackforge/rally+branch:master+topic:bp/multihost-deploy,n,z17:19
boris-42^ patches17:19
boris-42This work is already done17:19
boris-42and should be merged17:19
boris-42Idea is next17:19
boris-42we are deploying with separated deployers/provider controller and compute/cinder nodes17:20
*** garyk has joined #openstack-meeting17:20
boris-42so if we choose DevStack it will run N times .stacksh17:20
*** PaulMurray has left #openstack-meeting17:20
boris-42which will have bad perfromance17:20
*** Duane_ has quit IRC17:21
boris-42so we are deploying controller + N type of Nodes only 1 time17:21
boris-42(so N+1) call of stack.sh17:21
*** ArthurBerezin has joined #openstack-meeting17:21
boris-42and then copy pasting LXC containers17:21
*** Duane_ has joined #openstack-meeting17:21
boris-42which allows us to deploy 1 controller + 128 compute managers for just a 30 minutes17:21
*** fifieldt has quit IRC17:21
hughsaundersboris-42: on a single underlying node?17:22
*** SergeyLukjanov_ is now known as SergeyLukjanov17:22
boris-42it could use multiply nodes17:22
boris-42or even OpenStack provider17:22
*** thuc has quit IRC17:22
boris-42or even any other provider17:22
hughsaunderslike tripple-o undercloud17:23
boris-42hughsaunders but better=)17:23
boris-42it doesn't required OpenStack installation17:23
boris-42it will work with provider that you put17:23
boris-42Dummy/OpenStack/your_custom_cloud_provider17:23
hughsaundersso how do you determine in config how many lxc containers are created on each underlying node?17:24
boris-42hughsaunders here is the instruction how to try it http://paste.ubuntu.com/6792218/17:24
stannieon trello I saw you guys were thinking to integrate Docker, in this case it would simplify this usage. We wouldn't have to copy the LXC containers etc17:24
boris-42stannie we need17:24
*** lbragstad has joined #openstack-meeting17:24
boris-42stannie you should install from custom code your OpenStack installation17:25
*** nermina has quit IRC17:25
boris-42stannie with any of Deployers (e.g. DevStack/Anvil/Fuel)17:25
boris-42stannie and then copy/paste installed containers17:25
*** jasondotstar has joined #openstack-meeting17:25
boris-42stannie and then fix all copy/pasted lxc containers17:25
boris-42stannie there should be fix in nova.conf/cinder.conf/.… to add proper network information (IP/host_name)17:26
*** Duane_ has quit IRC17:26
boris-42stannie and run this components17:26
stannieye and that's can be done easily with Docker17:26
*** thuc has joined #openstack-meeting17:26
boris-42stannie but I don't see any problems to do it with lxc17:26
stannieok17:26
*** anniec has quit IRC17:26
*** jjmb has joined #openstack-meeting17:26
stannieit just asks a little more work17:26
boris-42stannie https://review.openstack.org/#/c/56222/17:26
boris-42stannie 150 lines of code17:27
*** thuc has quit IRC17:27
stannieok17:27
*** thuc has joined #openstack-meeting17:27
boris-42stannie but we are as well experimenting with docker17:27
boris-42stannie to make another future e.g. cloud deployment snaphsot17:27
boris-42stannie to share cloud+)17:27
boris-42feature&17:28
boris-42stannie that is the case where docker can help us17:28
*** rakhmerov has quit IRC17:28
boris-42stannie hughsaunders  so you can try as well to use this stuff https://review.openstack.org/#/c/56222/17:29
*** vkmc has joined #openstack-meeting17:29
boris-42stannie hughsaunders I will try to make installation today and merge it if it works=)17:29
boris-42we should move to the next topic17:29
boris-42#topic 4) Rally & Smart benchmark scenarios17:29
*** openstack changes topic to "4) Rally & Smart benchmark scenarios (Meeting topic: Rally)"17:29
boris-42#topic 4) Rally & Smart benchmark scenarios checkers17:30
*** openstack changes topic to "4) Rally & Smart benchmark scenarios checkers (Meeting topic: Rally)"17:30
boris-42olkonami1 could you pls share with your resuls17:30
boris-42olkonami1 seems like work is almost done17:30
olkonami1https://review.openstack.org/#/c/67157/17:30
olkonami1https://review.openstack.org/#/c/68055/17:30
*** comay_away has quit IRC17:30
*** comay_away has joined #openstack-meeting17:31
boris-42olkonami1 I mean could you expelling what have you done=)17:31
boris-42olkonami1 in human way=)17:31
boris-42olkonami1 btw you should make new blueprint17:31
*** egallen has quit IRC17:31
boris-42olkonami1 for your patches17:31
hughsaundersI really like the image_id validator, simple and effective17:32
boris-42hughsaunders yep there will be at least 2 more17:32
boris-42hughsaunders for flavor checking17:32
olkonami1I made decorator that add validators for scenario methods17:32
*** fifieldt has joined #openstack-meeting17:33
boris-42hughsaunders and checking that image could be use with flavor17:33
*** Leonr has quit IRC17:33
*** comay_away is now known as comay17:34
olkonami1and this validators should be called when runner starts17:34
stannieye that's great, we'll be able to add more validator without adding complexity in the method17:34
boris-42stannie yep and stop execution before starting it=)17:35
olkonami1now first validator for image_id is implemented17:35
*** afazekas has quit IRC17:35
boris-42so I hope we will merge this soon17:35
boris-42#topic 5) Rally as a Service17:36
*** openstack changes topic to "5) Rally as a Service (Meeting topic: Rally)"17:36
boris-42ogelbukh ping17:36
boris-42ogelbukh akscram  could you guys shares updates?17:36
*** Duane_ has joined #openstack-meeting17:36
*** msdubov has joined #openstack-meeting17:37
boris-42I will just make now some small introductions. We would like to support 2 versions of Rally in the same time17:37
boris-421 that is service (with deamons) and could be used by corporation to have 1 Rally installation integrated in QA process and simple WEB UI for all operations17:38
*** marun has quit IRC17:38
boris-42another one that is like now just CLI application17:38
boris-42so ogelbukh akscram are hard working around rally-python client and rally-as-a-service part17:38
boris-42#link https://review.openstack.org/#/q/status:open+project:stackforge/rally+branch:master+topic:bp/rally-service-api-v1,n,z17:39
boris-42and here is the first v.0.1 rally17:39
boris-42#topic http://docs.rallyapi.apiary.io/17:39
*** openstack changes topic to "http://docs.rallyapi.apiary.io/ (Meeting topic: Rally)"17:40
boris-42#topic  4) Rally & Smart benchmark scenarios checkers17:40
*** openstack changes topic to "4) Rally & Smart benchmark scenarios checkers (Meeting topic: Rally)"17:40
boris-42#topic     5) Rally as a Service17:40
*** openstack changes topic to "5) Rally as a Service (Meeting topic: Rally)"17:40
boris-42omg =)17:40
boris-42#link  http://docs.rallyapi.apiary.io/17:40
boris-42so if somebody is interstened you are welcome to describe API of Rally17:40
boris-42#topic  6) Improvements in Rally CLI17:41
*** openstack changes topic to "6) Improvements in Rally CLI (Meeting topic: Rally)"17:41
boris-42stannie julienvey could you share your work17:41
*** esker has joined #openstack-meeting17:41
julienveyi fixed a small bug on cli output17:42
julienveyand currently working on rally use command17:42
julienvey(trying to find the bp)17:42
*** egallen has joined #openstack-meeting17:42
*** Linz has joined #openstack-meeting17:42
*** MaxV has joined #openstack-meeting17:42
boris-42julienvey to find?17:43
julienveyhttps://blueprints.launchpad.net/rally/+spec/rally-use-command17:43
*** Linz has quit IRC17:43
*** gokrokve has joined #openstack-meeting17:43
*** asselin has joined #openstack-meeting17:43
julienveyi have had some problem with exporting env vars in python17:43
boris-42julienvey bp is approved17:43
*** gokrokve has quit IRC17:43
*** gokrokve has joined #openstack-meeting17:43
julienveyboris-42: it was just to share it :)17:43
boris-42julienvey =)17:43
boris-42julienvey so you are still working around ssh stuff17:44
*** fifieldt has quit IRC17:44
julienveyi should propose it to review tomorow, but i think it will need some rework17:44
*** marun has joined #openstack-meeting17:44
boris-42julienvey probably just call from python some bash command17:44
boris-42julienvey dirty but works=)17:44
julienveyactually it doesn't :(17:44
boris-42julienvey ah yes..17:44
boris-42julienvey there is another way via DB, but not sure that it's okay17:45
*** DinaBelova_ is now known as DinaBelova17:45
julienveyi went with the way proposed here https://bugs.launchpad.net/rally/+bug/1266439/comments/317:45
*** ArthurBerezin has left #openstack-meeting17:45
boris-42julienvey or some extra rally tmp fconfig17:45
*** Linz has joined #openstack-meeting17:46
julienveyuse .pam_environment file to store the env var17:46
boris-42julienvey yep something like that should work17:46
*** fifieldt has joined #openstack-meeting17:46
stannieI am going to work on "deployment check" subcommand. The subcommand will check keystone auth, get all available services and print names etc.17:46
stannie#link https://blueprints.launchpad.net/rally/+spec/deployment-check-subcommand17:47
boris-42stannie approved17:48
*** sarob has joined #openstack-meeting17:48
stanniethanks17:48
boris-42stannie julienvey  I will be waiting for your patches17:48
boris-42stannie julienvey as well it will be good to update/add some extra info on wiki page17:49
julienveyboris-42: yes, we have to :)17:49
boris-42oaky as we have only 10 minutes moving to next topic17:49
boris-42#topic  7) Rally & benchmarking performance of VMs17:50
*** openstack changes topic to "7) Rally & benchmarking performance of VMs (Meeting topic: Rally)"17:50
*** ildikov has joined #openstack-meeting17:50
boris-42msdubov & me are going to start working around this17:50
*** Leonr has joined #openstack-meeting17:50
boris-42I wrote some interesting document17:50
boris-42#link https://etherpad.openstack.org/p/Rally_VMs_Benchmarks17:50
boris-42The idea is actually as well pretty simple17:50
*** nati_ueno has joined #openstack-meeting17:51
*** nati_ueno has quit IRC17:51
boris-42using the same benchmark engine17:51
boris-42but in scenarios we will use heat & heat templates17:51
boris-42that will install HPCC, SPEC and other Benchamrks suits on VMs17:51
*** harlowja_away is now known as harlowja17:51
boris-42run them17:51
*** nati_ueno has joined #openstack-meeting17:51
boris-42then collect data17:51
boris-42and have for each such benchmark specific type of output data and data processing tool (viewer)17:52
boris-42that will show most important data + raw output of these benchmarks17:52
*** mrunge has joined #openstack-meeting17:53
*** rakhmerov has joined #openstack-meeting17:53
boris-42hughsaunders julienvey stannie  ^17:53
msdubovboris-42 How should we implement this viewer?17:53
*** cvbock has joined #openstack-meeting17:53
hughsaundersboris-42: so will your normalise data before it goes into DB?17:53
hughsaunders*you17:53
boris-42hughsaunders actually we will go to VMs17:54
boris-42hughsaunders then fetch data from bench suuit17:54
*** coolsvap is now known as coolsvap_away17:54
boris-42hughsaunders then store it in DB as is (but with some kind of marker e.g. specWEB2009)17:54
*** amcrn has joined #openstack-meeting17:54
boris-42hughsaunders and we will have viewer that can aggregate this date/or just display as is17:55
*** mestery has quit IRC17:55
*** nati_uen_ has quit IRC17:55
*** vkmc has quit IRC17:55
*** sarob_ has joined #openstack-meeting17:56
boris-42so I think that I will publish this to mailing list to get more attention17:56
boris-42there is a lot of for discussion17:56
boris-42#topic 9) Rally measuring time of atomic actions17:56
*** openstack changes topic to "9) Rally measuring time of atomic actions (Meeting topic: Rally)"17:56
*** marekd|away is now known as marekd17:56
boris-42Short introduction17:56
*** jlibosva has quit IRC17:56
*** sarob__ has joined #openstack-meeting17:57
*** ruhe is now known as _ruhe17:57
boris-42just use decorators e.g. @atomic_action("name_of_action")17:57
boris-42https://github.com/stackforge/rally/blob/master/rally/benchmark/scenarios/nova/utils.py#L2817:57
boris-42in such places ^17:57
boris-42this patch will measure time of call and put this time in special CLS dict17:57
*** sarob has quit IRC17:58
boris-42and scenario runner will add extra field https://github.com/stackforge/rally/blob/master/rally/benchmark/runner.py#L6017:58
*** sarob___ has joined #openstack-meeting17:58
boris-42^ here17:58
*** derekh has quit IRC17:58
boris-42and then improve CLI to display this data as well17:58
boris-42as I know stannie is interested in implementing this17:59
boris-42stannie  I right?17:59
*** jlibosva has joined #openstack-meeting17:59
boris-42am I right?*17:59
* hughsaunders has to go, laters17:59
boris-42we all have to go=)17:59
boris-42hughsaunders bye17:59
*** sarob has joined #openstack-meeting17:59
boris-42ok we can continue discussion in rally chat18:00
boris-42#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
stevemaro/18:00
openstackMeeting ended Tue Jan 21 18:00:10 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-01-21-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-01-21-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-01-21-17.00.log.html18:00
stannieok18:00
*** stanlagun has left #openstack-meeting18:00
*** sarob has quit IRC18:00
julienveyhave to go to, bye !18:00
*** msdubov has quit IRC18:00
*** sarob_ has quit IRC18:00
stevemarkeystoners, assemble!18:00
lbragstadhey18:00
*** henrynash has joined #openstack-meeting18:00
bknudsonhi18:00
dolphmbknudson: dstanek: jamielennox: morganfainberg: stevemar: gyee: henrynash: keystone!18:01
henrynashhowdy18:01
shardyo/18:01
morganfainbergdolphm o/18:01
dolphm#startmeeting keystone18:01
openstackMeeting started Tue Jan 21 18:01:43 2014 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 Meeting pings18:01
*** openstack changes topic to "Meeting pings (Meeting topic: keystone)"18:01
*** stevemar has left #openstack-meeting18:01
dolphmso i just had a dumb idea to make 10 seconds of my Tuesday easier18:02
*** sarob__ has quit IRC18:02
gyee\o18:02
*** stevemar has joined #openstack-meeting18:02
dolphmi'm going to put the above list (just keystone-core at the moment) onto https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:02
dolphmif you'd like to be pinged prior to our meetings, add your IRC name to the list and i'll just copy/paste it :)18:02
*** jamielennox has joined #openstack-meeting18:02
morganfainbergdolphm, copy/paste? ;)18:02
bknudson10 seconds will really add up over time.18:02
topolo/18:03
morganfainbergdolphm, you missed ayoung  in that list18:03
*** sarob___ has quit IRC18:03
topoldolphm can you add topol18:03
stevemarhehe18:03
ayoungI'm here18:03
*** fabio_ has joined #openstack-meeting18:03
marekdhello.18:03
*** fabio_ is now known as fabiog18:03
fabioghello18:04
*** olkonami1 has left #openstack-meeting18:04
*** bdpayne has joined #openstack-meeting18:04
dolphmlist is there now18:04
jamielennoxhi18:04
dolphm#topic icehouse-2 freeze18:04
*** openstack changes topic to "icehouse-2 freeze (Meeting topic: keystone)"18:04
dolphmso, ignoring gate woes for the moment, i bumped revocation-events and kds to i3, although i'd really rather not18:05
* ayoung frantically trying to keep up with bknudson reviews on revocation-events18:05
ayoungtis close18:05
dolphmwe have 3 hours to get things *gating* to call them icehouse-218:05
bknudsonfrantically trying to keep up with updates to review18:05
*** arnaud has joined #openstack-meeting18:05
*** arnaud__ has joined #openstack-meeting18:05
ayoungbknudson, any stop ships in that latest round?18:06
bknudsonayoung: in revocation events?18:06
ayoungyeah18:06
topoldolphm, anything that is priority to review now?18:06
henrynashi'll try and get list limiting fixed up - it was passing - only question is whether the 'next' pointer method is acceptable18:07
*** fifieldt has quit IRC18:07
dolphmi haven't kept up with reviews there at all -- could the patchset be broken down into something that can land today, with trickier bits landing in i3?18:07
bknudsonayoung: I didn't actually review it again. I just looked through my previous comments that weren't addressed in the latest patch18:07
bknudsonayoung: so I'll have to go through and do an actual review to know18:07
dolphmtopol: revocation-events, and mapping i'd say18:07
morganfainberghenrynash, did we determine 203 or in-json indicator?18:07
ayoungbknudson, OK18:07
dolphm#link https://review.openstack.org/#/c/55908/18:07
stevemarfyi mapping: https://review.openstack.org/#/c/60424/18:07
dolphm#link https://review.openstack.org/#/c/60424/18:07
jamielennoxdolphm: i'd like this one in i218:07
* stevemar pokes bknudson to review mapping :P18:07
jamielennox#link https://review.openstack.org/#/c/67785/18:07
henrynashmorganfainberg: the 203 looks dodgy….I think we were misinterpreting the spec18:08
morganfainbergonce the meeting is done, i'll jump on reviewing those links.18:08
*** egallen has quit IRC18:08
morganfainberghenrynash, ok fair enough.18:08
henrynashmorganfainber: so in-json seems to be the easiest18:08
bknudsonstevemar: https://review.openstack.org/#/c/60424/ depends on a change that's outdated.18:08
*** egallen has joined #openstack-meeting18:08
dolphmjamielennox: why is that citing a bug and not a blueprint :(18:08
dolphmi haven't tracked that at all18:08
stevemarbknudson, yeah, idp change just got pushed, so i'm rebasing18:08
marekdstevemar: i'd rather wait :P18:09
jamielennoxdolphm: does it warrant a blueprint?18:09
*** nadya__ has joined #openstack-meeting18:09
*** pcarver_ has joined #openstack-meeting18:10
dolphmjamielennox: it warrants milestone tracking of some kind, and it has none18:10
*** tnurlygayanov_ has quit IRC18:10
*** nkinder has joined #openstack-meeting18:10
*** evgenyf has quit IRC18:11
*** mdomsch has quit IRC18:11
jamielennoxdolphm: sorry, bug targetted to i218:12
*** safchain has quit IRC18:12
*** MaxV has quit IRC18:12
*** yamahata has joined #openstack-meeting18:13
*** sarob has joined #openstack-meeting18:13
dolphmif anyone is interested, i carried over our hackathon whiteboard, sort of, here: https://gist.github.com/dolph/852219118:14
jamielennoxgyee: thanks18:14
ayoungbknudson, only you could have 90 combined comments on a review and claim "I haven't reviewed it yet."18:14
bknudsonayoung: barely scratched the surface.18:15
*** markwash has joined #openstack-meeting18:15
dolphmayoung: it's a giant patchset :(18:15
*** Duane_ has quit IRC18:15
*** cvbock has quit IRC18:15
gyeelove the name Kite!18:16
topolI'm not buying anymore beers18:16
ayoungtopol, oh yes you are18:16
gyeetopol was buying beer?18:16
morganfainberggyee, ++18:17
*** dims has quit IRC18:17
ayoungGrowlers18:17
*** nermina has joined #openstack-meeting18:17
dolphmhmm18:18
*** nadya__ has quit IRC18:18
dolphmso, since transient gate failures are a hot topic18:19
*** aignatov_ is now known as aignatov18:19
dolphm#topic Default to listen on 127.0.0.1 instead of 0.0.0.018:19
*** openstack changes topic to "Default to listen on 127.0.0.1 instead of 0.0.0.0 (Meeting topic: keystone)"18:19
dolphmat bkhudson's request, i restored https://review.openstack.org/#/c/59528/18:19
bknudsonlet's be part of the solution for gate problems and not part of the problem.18:19
lbragstadbknudson: ++18:19
ayoungSo...does 127 makes things better?18:19
morganfainbergI really would rather this not be the default.  i'd _rather_ this change go into devstack.18:20
dolphmmorganfainberg: did we determine that this would fix the gate? or that the actual fix must be in devstack and this would just set the precedent18:20
dolphmmorganfainberg: downvote / -2 then18:20
shardyI still don't understand why things need to be defaulted in the config, and then again in eventlet_server.py18:20
morganfainbergdolphm, i wont block it if we really want to go forward with it18:20
morganfainbergdolphm, i18:20
*** fifieldt has joined #openstack-meeting18:20
dolphmmorganfainberg: i'm VERY torn on this :(18:20
*** cvbock has joined #openstack-meeting18:21
jamielennoxdolphm: 0.0.0.0 seems like a better default there18:21
dolphmhence i wanted to be the one to propose a solution rather than code review it :P18:21
ayoung0.0.0.0 means it can be called from off system, 127 does not18:21
morganfainbergdolphm, if we made devstack able to do in single-node mode 127.0.0.1 (and this is the "right fix"), and we still devault to 0.0.0.0 for default18:21
morganfainbergit doesn't present an insane default that every single deployer needs to change18:21
morganfainbergalternatively... make that default explode keystone18:21
bknudson0.0.0.0 also means that it will prevent an ephemeral port at 3535718:21
jamielennoxexactly - in almost every deployment call from anywhere is correct, this would mean deployers have to change this18:21
morganfainbergno default listen18:21
topolso its saves a very few amount of gate rechecks.  what was the downside again?18:21
morganfainbergyou must pick a listen, i'm ok with that as well.18:21
dolphmayoung: can you remove your approval on that, pending discussion18:22
ayoungdone18:22
jamielennoxmorganfainberg: i think you're right - surely this can be set in the devstack gate config18:22
ayoungwhat is the right behavior, devstack not withstanding?18:23
*** radez_g0n3 is now known as radez18:23
topolI thought the impact of this was small enough that fixing it was picking nits18:23
topol(on gate rechecks)18:23
*** aignatov is now known as aignatov_18:23
ayoungIf you spin up a Keystone instance, with or without SSL, should you be able to reach it from a remote system by default?18:23
topoljamielennox ++18:23
bknudsonget rechecks are very painful to the infra team.18:23
bknudsonthey affect all of openstack18:24
dolphmtopol: it's the highest priority transient error logged against keystone :)18:24
topoldolphm and the only one18:24
bknudsonand are the reason why things are taking 3 days to merge18:24
*** dims has joined #openstack-meeting18:24
dolphmtopol: shh (but GOOD WORK EVERYONE!)18:24
topolbknudson, dolphm said this one does not happen that often.18:25
bknudsonif it happens at all it's too often18:25
bknudsonbecause of the number of times the gate tests are run18:25
topolOK bknudson, you win!18:25
topollets fix this18:25
*** dvarga is now known as dvarga|away18:25
*** dvarga|away is now known as dvarga18:25
gyeeI am OK with the localhost fix18:26
* topol topol owes morganfainberg another beer18:26
dolphmtopol: fwiw, rechecks are fairly low-cost... it's gate failure & gate resets that are incredibly expensive18:26
ayoungWe should not be using IP addresses anyway.  Should be hostnames....18:26
topoldolphm, K18:26
bknudsonif this should be changed in some test config, then make the change there.18:26
morganfainbergbknudson, if devstack will accept the change, i'd much rather get it there.18:27
bknudsonWe've got this change and we can approve it right now to prevent us from being part of the gate problem.18:27
bknudsonwe can revert it later if there's another solution out there.18:27
dolphmdoes any other project default to listening on localhost?18:27
morganfainbergdolphm, afaik no18:28
topolbknudson is being very pragmatic on this18:28
dolphmi'd rather not be a surprise in that regard :-/18:28
lbragstadWe should update the commit message to state that it should be reverted if a devstack fix goes in18:28
*** wendar has quit IRC18:28
*** zhhuabj has quit IRC18:28
*** wendar has joined #openstack-meeting18:28
jamielennoxwhy is this just our problem and not suffered by the other services?18:28
jamielennoxis it just that the admin port is in the ephemeral range?18:29
ayoungwhy are we cahngein localhost to 127 in the doc?   127 should be localhost18:29
bknudsonjamielennox: do they use ports in the ephemeral range?18:29
topolisnt there enough runway before m3 that we would know if setting the new value will cause chaos?18:29
dolphmjamielennox: that's doc'd in the bug, but it's that we're using an IANA-assigned port, which falls in linux's ephemeral range (but not in the IANA-defined ephemeral range)18:29
*** dripton is now known as dripton_shovelin18:30
*** zhhuabj has joined #openstack-meeting18:30
jamielennoxisn't the solution then just to pick another port for devstack?18:31
ayounghow about 443?18:32
dolphmso, there's a lot of possible solutions with upsides/downsides18:32
dolphmayoung: that's one.18:32
gyeejamielennox, not really, unless you want to change the service catalog18:32
dolphm35357 can be an exception to the ephemeral range in linux18:32
dolphm35357 can be changed to something else in devstack, but that would be very odd and cause documentation / UX issues18:33
dolphmthe ephemeral range can be reduced, but that's just nasty18:33
dolphmespecially as a fix for something like this18:33
*** egallen has quit IRC18:33
ayoungOK...forgetting everything else,  should Keystone listen on 127.0.0.1 (localhost)by default?  It is not a production level default.  What is our stance?  Is Keystone ready for production out the gate, or do you need to customize?  I know we said we needed to customize the values in auth_token middleware in deployment.  Is this comparable?18:34
jamielennoxgyee: well devstack will provision the service catalog based on the port you give it18:34
bknudsonayoung: 0.0.0.0 isn't a production level default either.18:34
bknudsonthey'll need to configure the system for the interfaces they want to listen on.18:34
dolphmayoung: the rest of our keystone.conf is generally geared for minimally production-friendly defaults18:34
ayoungbknudson, its the only IP address based default that we can rely on.18:35
dolphmbknudson: keyword "minimally" ;)18:35
jamielennoxit just seems that having devstack use a different port is a way less surprising fix18:35
dolphmjamielennox: i think that would be *very* surprising to openstack manuals, all the blog authors out there, curl examples, our own docs, etc18:36
ayoungjamielennox, nah, that will mess people up, too, as the AUTH_URL is usually pre-canned with the Keystone port.18:36
*** Mandell has joined #openstack-meeting18:37
*** aepifanov has joined #openstack-meeting18:37
*** liuyu has joined #openstack-meeting18:37
*** ivar-lazzaro has joined #openstack-meeting18:37
jamielennoxbknudson: I also see no problem with 0.0.0.0 in production if you are running the services on a controller machine18:37
*** Duane_ has joined #openstack-meeting18:37
jamielennoxdolphm: it's set as an environment variable only in the gate - but i do get what you mean18:37
dolphmjamielennox: link?18:37
*** markwash has quit IRC18:38
ayoungSo, if Keystone were to listen on an known public IP address for the machine, would that still have the ephemeral problem?  I'm thinking it would18:39
ayoungproblem is that we have port 3535718:39
ayoungWe'd effectively break devstack's multi-node capability.  And the same would be true for anything taking its cue from Devstack18:39
bknudsonayoung: apparently the only time it has a problem with ephemeral ports (outbound) is when it's listening on 0.0.0.018:39
jamielennoxdolphm: https://github.com/openstack-dev/devstack/blob/master/lib/keystone#L6518:39
*** nati_uen_ has joined #openstack-meeting18:40
*** aepifanov has quit IRC18:40
dolphmjamielennox: what the hell is the next line? 35358?18:40
jamielennoxlol, i have no idea18:40
*** IlyaE has quit IRC18:40
* dolphm runs off to git blame18:40
jamielennoxoh, it's for tls-proxy18:40
*** markwash has joined #openstack-meeting18:41
jamielennoxif you enable tls-proxy it runs on 35357 and then redirects to a keystone running on 3535818:41
dolphmah18:41
*** jbrogan has quit IRC18:41
dolphm5000 and 5001 behave the same way18:41
ayoungcan't we "claim" an ephemeral port?18:41
morganfainbergas a deployer (and I also polled my coworkers) it's dumb to listen on 127.0.0.1 by default.  default should be minimally functional for general usecase18:41
*** galstrom is now known as galstrom_zzz18:42
*** Duane_ has quit IRC18:42
morganfainbergthey also said that they'd not mind if keystone exploded if you didn't set a bind (e.g. must pick in all cases)18:42
*** ildikov_ has joined #openstack-meeting18:42
dolphmayoung: ?18:42
morganfainbergbut changing to 127.0.0.1 would open the door for subtle broken behavior (can't access from another node by default)18:42
jamielennoxanyway so exporting KEYSTONE_AUTH_PORT=9999 (random value) in gate runs would solve this18:42
dolphmmorganfainberg: subtle for newbies is no fun18:43
morganfainbergdolphm, exactly18:43
*** mrunge has quit IRC18:43
jamielennoxanyone _relying_ on 35357 is wrong anyway18:43
*** nati_ueno has quit IRC18:43
dolphmjamielennox: explain?18:43
morganfainbergfigured i'd ask guys who run keystone every day their opinion18:43
*** miarmak has quit IRC18:43
ayoungjamielennox, yeah, but we'll still break the gate, which is not what we want to accomplish18:43
ayoungmorganfainberg, wouldn't that be the public IP of the Keystone server?18:44
dolphmthe gate fix is really on the devstack side; i saw https://review.openstack.org/#/c/59528/ as just a first step18:44
gyeemorganfainberg, we fronted Keystone with Apigee, LG, reverse proxies, etc in production :)18:44
jamielennoxwell everything does a first touch of keystone via 5000 to retrieve the auth_url, all we should need to do is set the admin url down into the non-ephemeral range18:44
gyeeLB18:44
dolphmgoing to abandon https://review.openstack.org/#/c/59528/ unless anyone is really in favor of it18:44
dolphmgyee: as you should18:44
morganfainberggyee, right, but that doesn't change 35357 issue18:44
jamielennoxayoung: why would it break the gate?18:44
ayoungis the problem that 0.0.0.0 somehow blocks the outgoing ports?  All Outgoing and incoming 0.0.0.0 come from the same pool?18:44
dolphmjamielennox: true for newer tools, for sure18:44
ayoungjamielennox, cuz someone somewhere is hard coding 3535718:45
morganfainbergayoung, basically... if something else is using 35357 as ephemeral, we don't start18:45
jamielennoxayoung: i'm only worried about the gate here18:45
morganfainbergayoung, it happens ~1 time a day in infra18:45
gyeemorganfainberg, dolphm, we run Keystone in dedicated boxes, I would imagine everyone does in production18:45
ayoungjamielennox, so am I18:45
ayoungcan we retry if 35357 is not available?18:45
gyeeso this is really a devstack gate fix18:45
morganfainberggyee, no, we use keystyone on shared boxes, not hypervisors18:45
jamielennoxif someone within the gate has hardcoded to 35357 then that's a bug to fix18:45
dolphmgyee: dedicated macbook pros all the way18:45
morganfainberggyee, but shared resources18:45
ayoungsleep 1; retry ;  sleep 5; retry; sleep 10; retry, give up?18:46
*** Alexei_987 has joined #openstack-meeting18:46
gyeeayoung, find the process using that port, kill it :)18:46
gyeethen retry18:46
morganfainbergayoung, depends on how long lived the use of the port is, but it should reduce the scope by some doing that18:46
ayounggyee, I don't want to give Keystone the power to kill other processes18:46
*** devoid has joined #openstack-meeting18:46
topol1 time a day.  For one time a day cant we wait till devstack fixes it?18:47
*** jprovazn has joined #openstack-meeting18:47
dolphmtopol: let's contribute the fix to devstack!18:47
morganfainbergi think the best bet is to make devstack force a listen on 127.0.0.1 in single node18:47
gyeeayoung, like stop squatting on my port!18:47
*** ildikov_ has quit IRC18:47
*** obondarev_ has joined #openstack-meeting18:47
topoldolphm, agreed18:47
ayoungmorganfainberg, nope18:47
*** nermina has quit IRC18:47
dolphmgyee: according to linux, it's not your port ;)18:47
morganfainbergayoung, no?18:47
ayoungdevstack doesn't know it is going to be single node18:47
dolphmayoung: why not?18:48
morganfainbergayoung, i think it does18:48
ayoungyou run an additional devstack on a second machine, and link it to the first18:48
*** lsmola has joined #openstack-meeting18:48
*** nermina has joined #openstack-meeting18:48
morganfainbergayoung, really? i thought it had more smarts than that *admittedly, i haven't tried*18:48
*** marun has quit IRC18:48
ayoungmorganfainberg, its one of the ways it can be run, and what I would expect most people to do:  set up a minimal install, make sure it runs, then add additional machines18:49
morganfainbergthis sounds like something that needs to be changed in the devstack-gate config then18:49
*** marun has joined #openstack-meeting18:49
morganfainbergand explicitly there.18:49
ayoungso, if my machine has a "public" ip of 10.10.2.12  can I listed on 10.10.2.12:35357 without conflicting on the ephemeral port?18:50
morganfainbergayoung, if nothing else is using it yes.  it doesn't matter18:50
gyeeaccording to bknudson, yes18:50
dolphmayoung: i think you'd be okay there unless something else explicitly was listening on the same interface + port18:50
morganfainbergdolphm, i believe that is how it wokrs18:50
ayoungwhat is it that we are tripping on that has the ephemeral port open in practice?18:50
morganfainbergayoung, anything.18:51
*** jroovers has joined #openstack-meeting18:51
ayoungin practice18:51
bknudsonayoung: it's just some random application opens a connection to something18:51
morganfainbergayoung, it's random, not consistent18:51
ayoungin devstack runs that fail?18:51
*** jorisroovers has joined #openstack-meeting18:51
ayoungthese are dedicated machines,  we should be able to tell18:51
morganfainbergayoung, could be apt, could be git, could be... uhm,, http?18:51
morganfainbergayoung, could be any request to an external place18:51
gyeeI blame pip18:52
morganfainbergayoung, and i think it isn't consistent.18:52
ayoungoutgoing requests should be separate from incoming, I thought18:52
*** jlibosva has quit IRC18:52
morganfainbergayoung, bi-directional, ephemeral ports are used for that18:52
lbragstadmorganfainberg: in which case wouldn't it be up to the administrator to decided how to solve best?18:52
*** fbo is now known as fbo_away18:52
morganfainberglbragstad, the easiest way is to change the ephemeral port range for the box to match the IANA numbers published18:52
morganfainberglbragstad, the "most correct way" that is18:53
morganfainberglbragstad, linux doesn't adhere to that RFC by default18:53
bknudsonanyone using the default config will wind up with keystone failing to start every once in a while because of this18:53
ayoungsudo  echo "49152 65535" > /proc/sys/net/ipv4/ip_local_port_range18:53
morganfainbergayoung, doesn't solve anything running before devstack starts18:53
morganfainbergayoung, which is why devstack ditched that18:53
ayoungthey can do it on the gate machines in rc.d18:54
*** dripton_shovelin is now known as dripton18:54
ayoungrc.local18:54
morganfainbergthat could.18:54
dolphmayoung: you can also just register a single exception (35357)18:54
morganfainbergthey could18:54
morganfainbergbut i think they were resistent to that change18:54
*** marun has quit IRC18:54
dolphmayoung: but, what morganfainberg said18:54
morganfainbergrequires custom images18:54
ayoung"we fear change:"18:54
morganfainbergayoung, "we fear changes we have to make every single time we update other things"18:55
ayounglets push for Devstack to run Keystone from HTTP using 44318:55
ayoungHTTPD18:55
*** jroovers has quit IRC18:55
dolphmayoung: it's not so much the change, so much as it becomes a hacky fix. devstack should on *any* supported image18:55
gyee443 is https18:55
ayounggyee, that is why I didn't say 8018:55
ayoung5 minutes left18:55
dolphmayoung: but you said http18:56
*** krotscheck has joined #openstack-meeting18:56
ayoungtwas a typo I corrected immediately after.18:56
topoldoesnt devstack have an apache running with swift and possibly using the http ports?18:56
gyeelets run devstack on windows :)18:56
ayoungtopol, that will work anyways18:56
bknudsonok, so we're not going to fix the gate problem we're causing?18:56
ayounghttp://wiki.openstack.org/URLs18:56
topolayoung, no conflict?18:56
ayoungnope18:56
*** pcarver_ has quit IRC18:57
ayoungSo long as the WSGI apps do something like /keystone vs /swift18:57
*** jcoufal-mobile has joined #openstack-meeting18:57
jamielennoxtopol: it has apache for keystone too but it defaults to running on 3535718:57
*** gothicmindfood has joined #openstack-meeting18:57
topoljamielennox, OK18:57
ayoungwhich is why we can't just change to listening on 443, we need to use Apache to manage between the WSGI apps18:58
*** jchiles has quit IRC18:58
*** akuznets_ has quit IRC18:59
*** lifeless1 is now known as lifeless18:59
* topol wonder what sdague thinks is the proper fix. He'll get to make the final decision anyway18:59
*** garyk has quit IRC18:59
* topol let him decide18:59
*** thuc has quit IRC18:59
ayoungI  think the retry18:59
bknudsonretry will mean it fails less often19:00
*** thuc has joined #openstack-meeting19:00
*** galstrom_zzz is now known as galstrom19:00
morganfainbergbknudson, short of abandoning the ephemeral port, there aren't good option here.19:00
ayoungfewest things changing, and it would be possible to layer another, more draconian fix on it later19:00
*** thuc has quit IRC19:00
topolthe transient gate fail will not have been officially removed19:00
*** thuc has joined #openstack-meeting19:01
jamielennoxthat's time guys19:01
*** IlyaE has joined #openstack-meeting19:01
lbragstadcontinue this in -dev?19:01
*** marekd is now known as marekd|away19:01
gyee++19:01
*** Alexei_987 has left #openstack-meeting19:02
*** shadower_ is now known as shadower19:02
*** mdomsch has joined #openstack-meeting19:02
pleia2dolphm: can you #endmeeting ?19:02
clarkbpleia2: you can do it after 60 minutes from start of meeting19:03
dolphm#endmeeting19:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:03
openstackMeeting ended Tue Jan 21 19:03:12 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-01-21-18.01.html19:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-01-21-18.01.txt19:03
dolphmpleia2: apologies!19:03
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-01-21-18.01.log.html19:03
pleia2thanks :)19:03
pleia2#startmeeting infra19:03
openstackMeeting started Tue Jan 21 19:03:23 2014 UTC and is due to finish in 60 minutes.  The chair is pleia2. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
*** openstack changes topic to " (Meeting topic: infra)"19:03
openstackThe meeting name has been set to 'infra'19:03
*** nkinder has quit IRC19:03
pleia2#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:03
*** fabiog has quit IRC19:03
pleia2#topic Actions from last meeting19:03
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:03
*** ivar-lazzaro_ has joined #openstack-meeting19:04
pleia2#link http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-01-14-19.02.html19:04
pleia2last meeting minutes, fungi had a number but he's on plane19:05
fungiaround-ish19:05
pleia2fungi: any updates from last meeting action items worth mentioning?19:05
*** lyxus has joined #openstack-meeting19:05
zaroo/19:06
pleia2zaro: as of this morning, I believe you and clarkb are still looking at the scp race condition issues?19:06
*** johnthetubaguy1 has quit IRC19:06
zaroyes, got a fix, just testing it now.19:06
pleia2mordred: any meeting-worth updates on manage-projects failures?19:06
pleia2zaro: great!19:06
*** ivar-lazzaro has quit IRC19:07
fungipleia2: i'd have to pull up the meeting minutes, so better to just assume i need most of those action items reapplied19:07
mordredpleia2: nope. I ran it several times by hand to try to catch a fail19:07
*** spzala has quit IRC19:07
mordredpleia2: so far, that has been unsuccessful19:07
pleia2mordred: still at "puppet is doing something weird to make it fail" then?19:07
*** sushils has joined #openstack-meeting19:07
mordredyeah. that's the current unproven working theory19:07
* pleia2 nods19:07
mordredI need to set up a new testbed thing that I can hammer on with a big hammer19:08
*** jamielennox has left #openstack-meeting19:08
pleia2ok, going to #action a bunch now, we can follow up next week on others that need to be removed when people are not so flying19:08
fungii did get mordred's creds reinstated19:09
pleia2#action reed to talk to smarcet and find a mentor to help him get through the CI learning curve faster19:09
mordred\o/19:09
fungiand there was one other on there... i got the trpleo credentials tested19:09
pleia2#action mordred to continue looking into manage-projects failures19:10
pleia2fungi, clarkb - thoughts on timing for -metering to -telemetry rename?19:10
jeblairmordred: your groups: http://paste.openstack.org/show/61640/19:10
pleia2#action fungi upgrade jenkins.o.o and jenkins01 to match 02-0419:11
fungiclarkb: how's this weekend?19:11
fungii'll be home friday night unless winter weather delays flights through chicago19:11
pleia2#action fungi move graphite whisper files to faster volume19:11
*** terriyu has quit IRC19:11
pleia2#action fungi prune obsolete whisper files automatically on graphite server19:11
*** julienvey_ has joined #openstack-meeting19:11
pleia2#action fungi request org.openstack group in sonatype jira for maven nexus19:11
clarkbfungi: mornings are fine19:12
*** markmcclain has joined #openstack-meeting19:12
fungithat one is back-burner as it turns out, since we don't need it (should also be org.stackforge instead)19:12
pleia2#undo19:12
*** topol has quit IRC19:12
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x3a8b6d0>19:12
pleia2#action clarkb to rename stackforge/cookbook-openstack-metering to -telemetry19:12
pleia2(had to give one to not fungi!)19:13
fungiwe can action it when the clouddocs-maven group decides how they're doing releases19:13
pleia2ok, great19:13
pleia2ok, that's it for action items from last meeting19:13
pleia2#topic Trove testing19:13
*** openstack changes topic to "Trove testing (Meeting topic: infra)"19:13
mordredjeblair: thanks!19:13
pleia2mordred, any updates? (I don't see hub_cap or SlickNik here)19:13
*** liuyu has quit IRC19:15
*** markpeek has quit IRC19:15
pleia2going to go with "no" or "check in with the others" so we can move along19:16
pleia2#topic Tripleo testing (lifeless, pleia2, fungi)19:16
*** openstack changes topic to "Tripleo testing (lifeless, pleia2, fungi) (Meeting topic: infra)"19:16
pleia2we had some -infra patches merged last week related to this (thanks fungi!)19:16
*** lbragstad has left #openstack-meeting19:16
*** julienvey_ has quit IRC19:16
pleia2not much else to report on the infra side right now I don't think19:17
pleia2lifeless: you have anything to add? (otherwise we just pick up the less-infra parts of this topic in the tripleo meeting)19:18
*** fifieldt has quit IRC19:18
fungii think he was working on some of the nodepoo prep scripts which needed tweaking still to get servers to build successfully19:19
funginodepool19:19
pleia2dependency-wise, right?19:19
mordrednodepoo19:20
fungii don't recall the details there19:20
mordredI'm a child19:20
lifelessfungi: pleia2 hi yes19:20
lifelesstheres a patch from deryck19:20
lifelessand we need to turn nodepool on19:20
lifelessthen we'll start to see how far it gets19:20
pleia2ok cool, I'll have a look at that in a bit19:21
gothicmindfoodmordred: you need to  make that tshirt for the next design summit19:21
lifelesshttps://review.openstack.org/#/c/67958/ and https://review.openstack.org/#/c/67685/19:21
lifeless^ neither should affect anyone else at all19:21
pleia2great19:22
*** krtaylor has quit IRC19:22
pleia2looks like next two agenda items it looks like we covered in action items review: Requested StackForge project rename (fungi, clarkb, zhiwei) & Ongoing new project creation issues (mordred)19:22
pleia2#topic Pip 1.5 readiness efforts (fungi, mordred)19:22
*** openstack changes topic to "Pip 1.5 readiness efforts (fungi, mordred) (Meeting topic: infra)"19:23
fungiyup19:23
mordred1.5.1 is out19:23
fungireqs integration jobs work again, as much as any jobs are working at the moment19:23
fungivirtualenv 1.11.1 was coming earlier than pip 1.5.1 i thought, but i haven't seen it yet19:24
fungimaybe that plan changed19:24
*** ayoung is now known as not-really-ayoun19:24
mordredfungi: 1.11.1 is on pypi19:24
*** not-really-ayoun is now known as ayoung-hiding19:24
*** ayoung-hiding is now known as ayoung19:24
fungiyup, just saw it19:24
fungislow browsing on the plane19:25
fungiso in theory we could lift our 1.10.1 pin when we're ready to babysit that19:25
fungimaybe that's an action item19:25
pleia2who wants that one?19:26
*** Mandell has quit IRC19:26
*** sarob has quit IRC19:26
pleia2ok, we can give it to mordred this week and reshuffle as needed :)19:27
pleia2#action mordred to lift virtualenv 1.10.1 pin when we're ready to babysit it19:27
mordred++19:27
*** vkozhukalov has quit IRC19:27
pleia2#topic OpenID provider project (fungi, reed)19:27
*** openstack changes topic to "OpenID provider project (fungi, reed) (Meeting topic: infra)"19:27
*** nati_ueno has joined #openstack-meeting19:27
*** gokrokve has quit IRC19:28
pleia2no reed here today19:28
fungii've got an action item to describe the bits of automation which are still mssing so that mrmartin can help smarcet get it done19:28
* pleia2 nods19:29
pleia2#topic Graphite cleanup (fungi)19:29
*** openstack changes topic to "Graphite cleanup (fungi) (Meeting topic: infra)"19:29
*** IlyaE has quit IRC19:29
pleia2we had to reaction a bunch of  graphite stuff, I assume "ongoing" here too?19:29
fungithis is still untouched. got too busy, though someone fixed it yesterday when it toppled over19:30
pleia2someone fixing it \o/19:30
fungias in got it running again19:30
clarkbit wasn't me. I was curious who that was as well. guessing jeblair19:30
pleia2yeah19:30
jeblairnope19:30
fungimust have been mordred19:30
anteayaan elf19:30
anteayawe have a helpful elf19:30
jeblairi logged in and everything looked normal.  busy but normal.19:30
mordredwasn't me19:30
fungihuh. weird19:31
jeblairalso, while i noticed a gap in some graphs, i did not see it in all19:31
jeblairpossibly a data reporting problem from one source?19:31
jeblairnetwork dropping udp packets?19:31
fungiokay, so whoever said it fell over and someone fixed it speculating19:31
*** nati_uen_ has quit IRC19:31
fungier, was speculating19:31
pleia2#topic Upgrade gerrit (zaro)19:32
*** openstack changes topic to "Upgrade gerrit (zaro) (Meeting topic: infra)"19:32
*** IlyaE has joined #openstack-meeting19:32
*** markmcclain has quit IRC19:32
zaroreview-dev.o.o has the upgraded gerrit (ver 2.8)19:32
zaroI believe I've also enbable all features requested in upgrade etherpad #link https://etherpad.openstack.org/p/gerrit-2.8-upgrade19:33
*** yamahata has quit IRC19:33
*** yamahata has joined #openstack-meeting19:33
zaroI've also created a semi-automated upgrade script #link https://etherpad.openstack.org/p/gerrit_upgrade_script19:33
zaroit's ready to go whenever we want to flip the switch.19:34
jeblairzaro: has it been tested with git-review and zuul?19:34
jeblairzaro: also, gerritbot and the jeepyb hooks?19:34
*** dvarga is now known as dvarga|away19:34
*** dvarga|away is now known as dvarga19:34
zaroi have been using git review and that seems fine. however i have not tested with zuul.19:35
jeblaircould switch zuul-dev to point at it19:35
zaroi have not looked into gerritbot nor jeepyb integrations.19:35
zaroi assumed a zuul was already pointing at gerrit-dev.  but it isn't?19:36
jeblairzaro: i think the last thing we did with zuul-dev was point it at prod gerrit to load test jenkins19:36
zarook. i'll put that on my tdl.  i'll also reveiw gerritbot and jeepyb integrations to see what to test there.19:37
pleia2#action zaro to point zuul-dev at gerrit-dev19:38
*** Mandell has joined #openstack-meeting19:38
*** fifieldt has joined #openstack-meeting19:38
pleia2#action zaro to review gerritbot and jeepyb integrations with new gerrit19:38
pleia2anything else?19:38
*** ildikov_ has joined #openstack-meeting19:38
clarkbyes, zuul changes last week19:39
*** egallen has joined #openstack-meeting19:39
clarkbjeblair: not sure if you caught this, but zuuls scratch git space is running on a tmpfs19:39
pleia2(I meant for this topic :))19:39
jeblairclarkb: (i saw; clever)19:39
clarkboh this topic, sorry I am bad at context switching right now19:40
pleia2#topic Private gerrit for security reviews (zaro, fungi)19:40
*** openstack changes topic to "Private gerrit for security reviews (zaro, fungi) (Meeting topic: infra)"19:40
zarothis is on hold, nothing new to report.19:40
pleia2I think we're still waiting on this for the 2.8 upgrade of regular gerrit19:40
*** ktbenton has quit IRC19:40
pleia2Savanna testing (SergeyLukjanov)19:40
pleia2#topic Savanna testing (SergeyLukjanov)19:40
*** openstack changes topic to "Savanna testing (SergeyLukjanov) (Meeting topic: infra)"19:40
*** Ajaeger1 has joined #openstack-meeting19:40
pleia2SergeyLukjanov: any updates here?19:40
SergeyLukjanovnothing realling interesting / new19:40
SergeyLukjanovstill waiting for review on patches for tempest19:41
pleia2#topic Jenkins SCP Plugin fix for Elastic Search (clarkb, zaro)19:41
*** openstack changes topic to "Jenkins SCP Plugin fix for Elastic Search (clarkb, zaro) (Meeting topic: infra)"19:41
pleia2mentioned this one earlier, testing is happening now19:41
*** kbenton_ has quit IRC19:41
*** mestery has joined #openstack-meeting19:41
SergeyLukjanovbtw, after the first savanna api tests will be merged into the tempest, I'd like to enable them for savanna as voting (https://review.openstack.org/#/c/68066/)19:41
clarkbafter updating the SCP plugin to handle new jenkins we realized it was done running jobs and emitting 0mq events that could be processed before console logs had even begun to start witing on the log server19:42
clarkbthis meant that the logstash machinery got 404s and those logs weren't processed. now we wait for the file to be created before continuing the job but there was a small bug in that that allowed jobs to get stuck (manually killing them fixes the problem)19:42
clarkbfix for latest bug is being tested now by zar19:42
*** novas0x2a|laptop has joined #openstack-meeting19:43
fungi(zar is pirate pizza)19:43
anteayaha ha ha19:44
pleia2ok, thanks clarkb and zaro19:44
pleia2#topic Open Discussion19:44
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:44
pleia2now, all the other things!19:44
mordredI had some lovely parsnips and brussels sprouts last night in a mustard sauce. is that off topic?19:45
fungimy flight is finally taking off. i will supposedly have 40 minutes to catch my connecting flight in vegas. no time for slot machines19:45
*** wenlock has joined #openstack-meeting19:45
pleia2while jeblair and I had an 8 hour layover in Auckland we finally got all those historic publications up on our site, yay! http://docs.openstack.org/infra/publications/19:45
*** aignatov_ is now known as aignatov19:45
mordredfungi: there are slot machiens in the airport - you can totally slot in 40 minutes19:45
fungi8 hour layover? crazy19:46
mordredpleia2: woot!19:46
*** mdurnosvistov has joined #openstack-meeting19:46
jeblairfungi: it was in the air new zealand lounge which had an automatic pancake making machine.  i'm not complaining.19:46
fungineat19:47
fungipancake dispenser19:47
pleia2it was pretty neat19:47
clarkbI do want to point out that the git operations that zuul does do seem to get slower over time19:47
pleia2maybe https://github.com/openstack-ci can go away now? :)19:47
clarkbthe tmpfs is definitely better, but I believe performance is degrading there too19:47
anteayaclarkb: :(19:47
mordredclarkb: that doesn't seem nice19:47
clarkband ideas on why that may happen? do we need to gc and pacl more often?19:47
*** sarob has joined #openstack-meeting19:47
anteayadid you upgrade git?19:47
clarkbanteaya: we did not, local very unscientific testing showed it would not help much19:48
anteayaI know you discussed upgrading git19:48
anteayaokay19:48
clarkbgranted that was some very simple cases being tested19:48
jeblairclarkb: sanity check that we're packing once/day?19:48
clarkbjeblair: /me checks19:48
clarkb7 4 * * 0 looks like it19:48
clarkboh wait19:49
clarkbahahahahahaha19:49
clarkbhrm that shouldn't matter19:49
anteayawhat?19:49
fungithat's weekly, yeah?19:50
clarkbits not providing a working dir for the git pack but git pack doesn't need one19:50
jeblairyeah, that is weekly19:50
clarkbyeah the 0 at the end19:51
clarkbshould we s/0/*/19:51
jeblairstill...19:51
clarkbjeblair: I think the thrash is a big part of it19:51
jeblairroot@zuul:/var/lib/zuul/git/openstack/nova/.git# ls -la packed-refs19:51
jeblair-rw-rw-rw- 1 zuul zuul 1856171 Jan 21 03:15 packed-refs19:51
jeblairroot@zuul:/var/lib/zuul/git/openstack/nova/.git# wc -l packed-refs19:51
jeblair19834 packed-refs19:51
jeblairroot@zuul:/var/lib/zuul/git/openstack/nova/.git# find refs/|wc -l19:51
jeblair285719:51
*** marun has joined #openstack-meeting19:51
clarkbjeblair: zuul is created hundres of refs * number of resets19:52
jeblairit seemed to pack refs this morning, and the bulk of the current refs are packed19:52
*** thuc has quit IRC19:53
jeblairi wonder if gitpython deals with large numbers of refs or objects particularly poorly.19:53
*** thuc has joined #openstack-meeting19:53
*** thuc has quit IRC19:54
*** thuc has joined #openstack-meeting19:54
clarkbwell change pushed, we can think over it in review19:54
*** ametts has joined #openstack-meeting19:55
*** ArxCruz has quit IRC19:55
fungiit did seem much snappier when zuul was operating on fresh clones, but i have no empirical evidence, just perception19:56
ttxmight be 2 min late for tc meeting, switching locations19:56
clarkbfungi: it was, the entire zuul git operations were sub 2 seconds then compared to 9-1519:56
clarkbfungi: it is now about 5 seconds19:56
*** markpeek has joined #openstack-meeting19:57
*** GheRivero has quit IRC19:57
*** GheRivero has joined #openstack-meeting19:58
*** gokrokve has joined #openstack-meeting19:58
*** KurtMartin has joined #openstack-meeting19:59
pleia2ok, sounds like we're done, thanks everyone19:59
pleia2#endmeeting19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:59
openstackMeeting ended Tue Jan 21 19:59:08 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-01-21-19.03.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-01-21-19.03.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-01-21-19.03.log.html19:59
*** Gordonz has quit IRC19:59
*** sarob has quit IRC20:00
*** gokrokve_ has joined #openstack-meeting20:00
*** sarob has joined #openstack-meeting20:00
*** hub_cap has joined #openstack-meeting20:01
*** nadya__ has joined #openstack-meeting20:01
ttxAnyone here for the TC meeting ?20:01
*** markmc has joined #openstack-meeting20:01
lifelessyes20:01
anteayao/20:01
lifelesssadly20:01
devanandao/20:01
markmchey20:01
lifelessthree hours of meeting wednesday20:02
ttxrussellb, annegentle, mikal, mordred, jgriffith, vishy, markmcclain, jeblair, sdague : around ?20:02
lifelessor is it four20:02
russellbo/20:02
sdagueo/20:02
mordredo/20:02
ttxat least you don't have asnowy, sunny mountain screaming a tyou you would be better off on the slopes20:02
annegentleo/20:02
lifelessttx: no, I have sunny water for boating...20:02
jeblairo/20:02
markmcboating vs skiing20:03
markmcthere's a choice20:03
ttxok, we are enough, let's do this20:03
markmcdepends on the boat20:03
ttx#startmeeting tc20:03
openstackMeeting started Tue Jan 21 20:03:07 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:03
*** openstack changes topic to " (Meeting topic: tc)"20:03
openstackThe meeting name has been set to 'tc'20:03
lifelesssailboat of course20:03
*** dguitarbite has quit IRC20:03
markmclifeless, of course :)20:03
ttxOur agenda for today:20:03
mikalHi20:03
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:03
ttx#topic Clarify "Project must be part of the integrated gate" as a graduation requirement20:03
*** openstack changes topic to "Clarify "Project must be part of the integrated gate" as a graduation requirement (Meeting topic: tc)"20:03
*** gokrokve has quit IRC20:03
ttxLast week during the incubation status review there was a lot of confusion around this requirement20:03
ttxMostly around a chicken-and-egg issue (project can't be a true part of integrated gate until it's actually integrated)20:03
ttxSo I would like us to clarify this requirement20:04
lifelesswhats confusing?20:04
ttxsdague: could you explain what you had in mind when you originally mentioned it ?20:04
*** rakhmerov has quit IRC20:04
sdaguettx: it's a graduation requirement20:04
*** malini has joined #openstack-meeting20:04
ttxlifeless: (project can't be a true part of integrated gate until it's actually integrated, so requiring it pre-graduation is a bit weird)20:04
sdagueso when we cut Juno20:04
*** alcabrera has joined #openstack-meeting20:04
*** sarob has quit IRC20:05
*** kgriffs has joined #openstack-meeting20:05
sdaguethe projects we say are in Juno would be sharing a gate job20:05
ttxgraduation to become part of Juno happens before we release Icehouse20:05
*** Gordonz has joined #openstack-meeting20:05
lifelessttx: the integrated gate isn't defined as 'the integrated API projects' is it? I thought it was 'the gate that zuul has that has all the symmetrically tested projects'20:05
*** gokrokve_ has quit IRC20:05
sdagueso graduation for Juno is actually Juno release day20:05
lifelessttx: and thus includes clients, helpers, oslo libraries and more20:05
sdaguein my terminology20:05
*** amitgandhi has joined #openstack-meeting20:05
sdaguenot attaining integrated status20:06
sdaguemaybe my wording was bad20:06
lifelessttx: so I think its a terminology issue20:06
ttxsdague: they graduate and undergo a full cycle of development before being included in a final release20:06
russellbi think that's what we're trying to clear up :)20:06
sdagueyeh, ok, pick a different word20:06
mordredI had understood this to mean that the project in question had a dvsm-tempest job that it gated on, so that we could verify that, on graduation, all we'd need to do to have them in the integrated gate would be to change some defaults in teh global gate20:06
lifelessrussellb: fair enough20:06
ttxhttps://wiki.openstack.org/wiki/Governance/NewProjects20:06
*** Duane_ has joined #openstack-meeting20:06
russellbmordred: that works20:06
sdagueif you are integrated by the time yuo get to the stable release with your inclusion, there are things yuo need to do20:07
*** mrodden1 has joined #openstack-meeting20:07
lifelessmordred: I think we should require symmetric gating20:07
vishyo/ sorry guys, last meeting went 5 min over20:07
mordredwe canont require symmetrical gating20:07
*** mrodden has quit IRC20:07
ttxmordred: yes, that would work for me20:07
*** Leonr has quit IRC20:07
mordredas a requirement to determine if we'll add you to the symmetric gate20:07
ttxjust wanted to make sure everyone is on hte same page20:07
lifelessmordred: not as a requirement to be added to the symmetric gate, but as a requirement for graduation20:07
sdaguettx: so what do we call the transition of a project to it's first stable release?20:07
ttxone of the first thing they add during that common dev cycle after they graduate is that gate integration20:07
mordredwe do not gate integrated projects on non-integrated projects20:07
mordrednor do I think we should20:08
russellb+120:08
lifelessmordred: we gate on projects that are not part of the integrated release20:08
ttxsdague: its first integrated development cycle ?20:08
mordredlifeless: no, we do not20:08
russellbi think a gate job for the project that clearly demonstrates that it'd be easy to flip the switch to have it in the integrated gate is enough20:08
lifelessmordred: so python-novaclient isn't gated on ?20:08
sdaguerussellb: +120:08
ttxmordred: would you care to suggest a wording to replace that line from the graduation-requirements doc ?20:08
devanandattx: "graduate and undergo a full cycle of development ..." -- this means projects which might graduate this cycle would NOT be included in Icehouse release. is taht correct?20:08
mordredlifeless: server projects20:08
*** DinaBelova is now known as DinaBelova_20:08
SergeyLukjanovrussellb, fwiw agreed20:08
jeblairrussellb: yes, that's what i was envisioning.20:09
ttxdevananda: yes20:09
mordredrussellb: ++20:09
russellbsdague: if that was the original intent, we just need to clarify the wording, and i think we're good ...20:09
devanandattx: k, thanks for clarifying that20:09
ttxprojects graduating at the end of the icehouse cycle are to be patr of the full Juno cycle20:09
annegentleI like the graduate plus undergo full cycle fwiw20:09
sdaguerussellb: yes, that was the original intent20:09
russellbcool20:09
ttxthat lets us catch up on all those things20:09
russellbI can propose an update if you want, or you can, whichever20:09
sdaguettx: ok, come up with a word for what Trove does when we get to Icehouse20:09
ttxand give them equal footing in summit/meetigs20:09
sdagueall we need is a word for that event20:09
sdaguethen this is clear20:09
ttxsdague: "makes its first integrated release"20:09
sdagueok, that's the word20:10
ttx"release" would be the word20:10
markmcyeah, the interesting part is the start of the cycle20:10
ttxas in "there is one full cycle beween graduation and release"20:10
ttxany volunteer to submit a wording clarification ?20:10
ttxmordred, sdague ?20:10
sdagueok, so I'm confused how people were reading the doc before. Because graduation == release to me. As there is a separate section on integration20:11
devanandasdague: taht was my reading as well20:11
mordredgraduation == "be accepted into the intgrated gate"20:11
ttxhttps://wiki.openstack.org/wiki/Governance/NewProjects has a diagram that should make it clear20:11
mordredrelease == "be released as part of the integrated release"20:11
markmclet's draft here: https://etherpad.openstack.org/p/graduation-gate-requirement20:11
hub_capinagural?20:12
* markmc copies and pastes20:12
devanandahence my confusion around testing Ironic this cycle. it sounds like we dont need to get all the testing up by Icehouse to graduate20:12
devanandawhich was part of the requirement, i thought20:12
mordreddevananda: you do20:12
devanandamordred: asymmetric?20:12
*** markwash has quit IRC20:12
mordreddevananda: yes20:12
russellbhttps://review.openstack.org/6822920:12
ttxbasically, once you graduate, we announce to the world you will be patr of the next openstack release20:12
devanandamordred: ah. that wasn't clear in the doc20:12
mordredthen we'll turn it symmetric when you graduate20:12
ttxit's not easy to back off frmo that20:12
ttxso we need to have as much as we can nailed by graduation time20:13
markmc"** Project must have a gate job running which can be added to the integrated gate after graduation" ?20:13
russellbmarkmc: ah sorry, missed that20:13
sdagueyeh, s/graduation/release/20:13
sdagueand you are +1 from me20:13
devanandamarkmc: sure, but that's not clearly asying an *asymmetric* job20:13
mordredsdague: no20:13
devanandaso I read it as "part of the gate"20:13
markmcrussellb, cool20:13
mordredsdague: graduation is correct20:13
russellbi had ... +** Project must have a devstack-gate job running, including functional tests, that demonstrates that it would be easy to add the project to the integrated gate after graduation.20:13
*** Leonr has joined #openstack-meeting20:13
mordredsdague: release comes 6 months after graduation20:13
ttxAlso note that we have "Project must have a basic devstack-gate job set up" as an INCUBATION requirement20:14
mordred++20:14
russellbbasic job (with nothing about what it actually does)20:14
*** nkinder has joined #openstack-meeting20:14
ttxis that too much for incubation ?20:14
russellbgraduation: job with real tests20:14
russellbbasic job, don't think so20:14
ttxrussellb: ok ++20:14
mordredI believe intent there was "devstack can install your project"20:14
mordredand things don't fall to pieces20:14
russellbfor incubation, a job that just starts the API service and that's it may be enough20:14
mordred++20:14
russellbjust get it installed and run it20:14
sdagueok. I'll trust you on this one mordred.20:15
ttxlike a job skeleton20:15
russellbyeah20:15
sdagueyep20:15
*** nadya__ has quit IRC20:15
russellbthere's a lot you have to get right to get that far, so it's valuable20:15
ttxmordred: you propose the wording change ? I think we have the direction clearly set now20:15
mordredttx: ok20:15
russellbi have a WIP -- https://review.openstack.org/6822920:15
ttxok, moving on then20:15
mordredrussellb: ++20:15
sdaguerussellb: looks good20:15
ttx#action mordred/russelb to suggest wording change for QA graduation requirement20:16
*** krtaylor has joined #openstack-meeting20:16
ttx#topic Mid-cycle incubation status review: Marconi20:16
*** openstack changes topic to "Mid-cycle incubation status review: Marconi (Meeting topic: tc)"20:16
*** prad_ has joined #openstack-meeting20:16
ttxLike last week, the idea here is to check the current state of the project w/ the graduation requirements20:16
kgriffso/20:16
ttx#link http://git.openstack.org/cgit/openstack/governance/tree/reference/incubation-integration-requirements#n5620:16
*** nati_uen_ has joined #openstack-meeting20:16
*** epim has joined #openstack-meeting20:16
flaper87o/20:16
* alcabrera listens in20:16
*** megan_w has joined #openstack-meeting20:16
russellbhave a handy page with notes on your status?20:16
kgriffsso, we have a few things20:17
kgriffsfirst, we have a tracking bp for graduation: https://blueprints.launchpad.net/marconi/+spec/graduation20:17
*** prad has quit IRC20:17
*** prad_ is now known as prad20:17
ttxkgriffs: You mentioned to me you might pass on graduation for Juno. Did you change mind ?20:17
*** dvarga is now known as dvarga|away20:17
*** dvarga|away is now known as dvarga20:17
kgriffsbefore I answer that, I need to clarify some things20:17
ttxkgriffs: we are listening20:18
*** jcoufal-mobile has quit IRC20:18
kgriffsfirst, if we wanted to graduate to be integrated in Juno, we would need to be ready when? i-3 ?20:18
kgriffsor sooner?20:18
ttxwe usually do the graduation review just before juno PTL election20:18
ttxso that would be sometimes in March20:19
kgriffsah, ok20:19
ttxpost i-320:19
kgriffsso, assuming we participate fully in i-2 and i-320:19
*** nati_ueno has quit IRC20:19
kgriffsand have all our code ready by i-320:19
kgriffswe could maybe have a few weeks extra to work on docs?20:19
ttxas far as release management goes if you get on board by i-2 you're golden20:19
*** egallen has quit IRC20:20
ttxkgriffs: sounds doable20:20
kgriffsok. If we can have until mid-march to get the docs requirement taken care of, then I would like to still try to graduate this cycle20:20
ttxkgriffs: so, what are the gaps ?20:21
markmcI honestly can't remember the feedback we gave marconi on incubation20:21
markmcright, the gaps :)20:21
kgriffsmarkmc: let me grab a link20:21
markmce.g. is falcon to pecan a requirement from the TC's perspective?20:21
*** balajiiyer has joined #openstack-meeting20:21
* ttx 's brain is a bit fried by jetlag. Or frozen.20:21
flaper87https://wiki.openstack.org/wiki/Marconi/Incubation/Graduation20:22
kgriffsso, it was not a requirement to swap it out20:22
markmcthanks flaper8720:22
ttxmarkmc: ISTR supporting pecan as an optoin was a requirement20:22
flaper87markmc: :)20:22
kgriffsthe requirement was that we do due diligence on evaluating pecan20:22
markmcok20:22
annegentlekgriffs: why the need for a few more weeks for docs? Just wondering20:22
kgriffswith the understanding that if it looks good, we would migrate to it, but that could happen post graduation20:22
kgriffsannegentle: we are short-handed20:22
ttxkgriffs: was that due diligence done yet ?20:22
kgriffsI am going to try to get everything done by i-320:23
*** gothicmindfood has left #openstack-meeting20:23
flaper87ttx: work in progress https://blueprints.launchpad.net/marconi/+spec/pecan-framework20:23
kgriffsbut docs may come in a bit late depending on if we can recruit some more folks or not20:23
flaper87ttx: there's 1 guy dedicated to that full time20:23
sdaguekgriffs: yeh, I think that due dilligence kind of needs to come first, because putting another web stack as an overall requirement for openstack integrated is kind of a big deal20:23
markmcinteresting that heat integration is a requirement20:24
kgriffsmarkmc: so, that is more of a "nice to have" I suppose20:24
ttxkgriffs: overall, that sounds like an impressive number of checkboxes to check given how much time and resources you have left, but it's still worth trying20:24
mordredhonestly - if I had to chose between you guys spending time on pecan dilligence and spending time on devstack/tempest integration testing ... I'd rather testing happen20:24
russellbsqlalchemy driver still a requirement, yes?20:24
kgriffsso, devstack/tempest is mostly done - we are waiting on reviews20:24
malinimordred: I already have some outsanding patches for devstack/tempest20:24
*** NikitaKonovalov_ is now known as NikitaKonovalov20:24
mordredmalini: awesome20:24
markmckgriffs, might be worth clarifying there which are requirements vs nice-to-haves20:24
kgriffsyes, sqlalchemy is a hard requirement20:24
russellbcool20:24
flaper87mordred: malini is working full time on that20:25
mordredI see sqlalchemy in the tree20:25
kgriffsthat work is in progress (sqlalchemy) - already had a few patches land for that20:25
flaper87sqlalchemy is moving a bit slow but we can speed that up. The structure is there, the implementation needs to be completed20:25
kgriffslet me clean up that wiki page - it isn't clear what is a hard grad req.20:25
kgriffsthe graduation bp is more accurate20:25
kgriffsflaper87: yep, we have already talked about getting another pair of hands on that to help speed up the work20:26
kgriffsok, refresh that wiki page20:27
*** pcarver has quit IRC20:27
flaper87FWIW, the client library is almost done. There's just 1 feature missing and we already released an alpha version of it: https://pypi.python.org/pypi/python-marconiclient/0.0.1a120:27
ttxkgriffs: what about the process requirements ? core team size, diversity ?20:27
kgriffsi don't think there were any changes we had to make20:28
kgriffswe already had good diversity20:28
kgriffsand the team has been steadily growing20:28
russellbreference: http://stackalytics.com/?release=icehouse&metric=commits&module=marconi20:28
ttxok, looks good20:28
kgriffsIBM has been ramping up20:28
ttxcomments anyone ? questions ?20:29
kgriffslooking forward to them taking a bigger slice of the pie20:29
flaper87to be more detailed: 3 core members (2 RAX, 1 RH) 2 more contributors from RH, 2 more from RAX, 1 guy from IBM and another guy from the community20:29
flaper87also Cindy from GOPW20:29
flaper87(re diversity)20:29
flaper87and the teams seems to keep growing, thankfully20:30
kgriffsI'm hoping to promote another core member within the next few months20:30
ttxso in summary, lots of work to do on the dev side, but no blocker so far20:30
kgriffs(probably from IBM)20:30
kgriffsttx: right20:30
*** fifieldt has quit IRC20:30
ttx#info Marconi looks good, lots of work to do on the dev side, but no blocker so far20:30
ttxkgriffs: we'll do the i-2 common release, too20:30
kgriffsyep20:31
flaper87thanks guys! :)20:31
* flaper87 STFU now20:31
ttxlast comments before we switch to nex ttopic ?20:31
annegentlekgriffs: people are asking good questions about marconi docs of me, so there's that :) But yes, get resources on it.20:31
ttxdamn sticky keys20:31
kgriffsttx: what is the cutoff for i-2? meaning, when does it get tagged/branched today (UTC)?20:31
*** jmh_ has quit IRC20:31
ttxkgriffs: next meeting. Normally yes.20:31
ttxbut these are exceptional times20:31
kgriffsannegentle: definitely - docs are a high priority, we are just looking for helping hands20:31
*** malini is now known as malini_afk20:31
ttxmikal: you around ?20:31
mikalYep20:32
ttx#topic Requirements for third party test systems20:32
*** openstack changes topic to "Requirements for third party test systems (Meeting topic: tc)"20:32
ttx#link http://lists.openstack.org/pipermail/openstack-tc/2014-January/000487.html20:32
ttxmikal: i'll let you introduce the topic20:32
*** ametts has left #openstack-meeting20:32
mikalCool20:32
*** balajiiyer has left #openstack-meeting20:32
mikalSo I think this is mostly informational unless we're really upset20:32
mikalI wanted the TC to be aware of the general push for third party CI which is happening at the moment20:32
*** gyee has quit IRC20:32
mikalIts causing some social problems, as these systems seem to be being built by people we didn't expect20:32
*** nati_uen_ has quit IRC20:33
mikali.e. ops people who are not ATCs and never use gerrit20:33
lifelessmikal: the spanish inquisition ?20:33
mikalanteaya has had problems with systems going rogue and leaving bad votes lying around all over the place for example20:33
anteayait just feels like the spanish inquisition20:33
mikalSo, there's a few things here20:33
lifelessanteaya: nobody expects...20:33
mikal - we need clearer expectations of these systems20:33
anteayamostly because I am a point of contact for the rogue20:33
mikal(which infra is working on already)20:33
jeblair#link https://review.openstack.org/#/c/63478/7/doc/source/third_party.rst20:33
sdaguemikal: one other thing I'd like to see is an output template for expected results20:34
mikal - PTLs need to be careful with the deadlines they set because of the load they place on anteaya / infra20:34
sdaguebecause that seems all over the board20:34
mikalsdague: yes, although I don't think I agree with the assumption that tempest should always be the test run20:34
sdaguemikal: agreed20:34
mikalsdague: that's true for driver authors, but not for meta testing20:34
jgriffithmikal: sdague why not?20:34
sdaguebut in the summery post20:34
jgriffithmikal: sdague if that's what we use to gate, why woulnd't it be the same?20:35
sdaguewe need some consistency on naming20:35
mikaljgriffith: why not tempest?20:35
mikaljgriffith: well, with db ci for example, tempest doesn't exercise what we're trying to test.20:35
mikaljhenner: or at least exercises way more than we need20:35
mikalsorry, jgriffith there20:35
jgriffithmikal: so I think we need to think about different projects/etc20:35
*** jdob has quit IRC20:35
sdaguemikal: you want output template suggestions in the same doc?20:35
jgriffithmikal: cinder for example "better" require tempest IMO20:35
mikalsdague: I think that makes sense20:36
lifelessjgriffith: tempest starts with a cloud, so anything meta is perhaps awkward20:36
*** jdob has joined #openstack-meeting20:36
sdaguemikal: ok, I'll submit something20:36
anteayaalso stackforge-fuel https://review.openstack.org/#/dashboard/897120:36
jgriffithlifeless: I don't even know what that means?20:36
mikaljgriffith: I think you should require tempest from _driver_ authors20:36
anteayatests only stackforge things20:36
jgriffithmikal: exactly.. yes20:36
mikaljgriffith: if someone wanted to test some non-driver thing, then that should be ok to be outside tempest20:36
mikaljgriffith: well, outside of tempest if it makes sense to be outside tempest20:36
sdaguejgriffith: we also have other 3rd party testing, like mikal's turbo-hipster which is a functional test for db performance on real data20:36
jgriffithmikal: I think we may be bighting off too big a piece of cake at once20:36
jgriffithsdague: ok20:37
*** amitgandhi has left #openstack-meeting20:37
ttxmikal: is this more for information, or do you need the TC to come up with some sort of decision here ?20:37
jgriffithsdague: I'm with you now20:37
devanandaassuming that different drivers have (nearly) the sme functionality, reusing existing tempest tests for a project seems logical.20:37
mikalWhat specifically caused me to want to talk about this was the neutron i-2 deadline20:37
devanandais that a false assumption?20:37
jgriffithsdague: mikal but I think there should be different docs/processes for the different types of testing20:37
anteayacurrent 3rd party testing accounts: https://review.openstack.org/#/admin/groups/91,members20:37
ttxmikal: because so far that sounds like something we could discuss on the cross-project meeting too20:37
mikalttx: well, if the tc is happy with that code review...20:37
devanandamikal: though i understand your pointthat non-driver third-party tests may not be suitable for tempest20:37
annegentleanteaya: thanks was just going to ask for a list20:37
mikalttx: then I just want PTLs to talk to infra before issuing deadlines in public20:37
anteaya:D20:38
mikalttx: so yeah, informational20:38
*** Ajaeger1 has left #openstack-meeting20:38
mikalAlso, anteya I suspect could do with more support from core devs20:38
*** mrunge has joined #openstack-meeting20:38
sdagueI think we should also all recognize this has been a learning experience20:38
anteayathe deadline email in question: http://lists.openstack.org/pipermail/openstack-dev/2013-November/019219.html20:38
mikali.e. help with cleaning up misvotes etc20:38
sdagueand that we might need to adapt as we go20:38
ttxmikal: given that PTLs != TC I think we should echo that discussion on the cross-project meeting too20:38
mordred++20:38
mikalttx: agreed20:38
NobodyCam-infra just a passing "Great Job guys!"20:38
anteayaalso markmcclain is doing the first day of hr at new job so he isn't here atm20:38
mikalttx: I wanted to make sure I was in alignment with the tc first thugh20:38
jeblairyes, we did not anticpate these problems but i think we can work through them and deal with them.20:39
mikalthough20:39
lifelessmore than just talking to infra; I think folk need to recognize it takes 6m+ for a testing system to get the bugs ironed out20:39
ttxmikal: I think more coordination cannot hurt20:39
anteayamore discussion is welcome20:39
lifelessrealistic deadlines...20:39
*** sarob has joined #openstack-meeting20:39
mikalttx: there was also talk about how we decide to grant voting rights to 3rd party testers20:39
mikalttx: that might be a tc thing if we want to get involved20:39
mikalttx: or we can leave it to the ptl20:39
mikalI don't have strong opinions there20:39
ttxmikal: can become a TC thing is that cannot be solved at a lower level20:40
mordredI think leave to ptl until it's an issue20:40
jgriffithmikal: I do :)20:40
ttxmordred: +120:40
*** alcabrera has left #openstack-meeting20:40
mikaljgriffith: what is your opinion?20:40
jeblairi think infra can do objective evaluation20:40
sdagueyeh, I'd say we can take this out of TC20:40
jgriffithmikal: external items I don't think should vote20:40
jeblairif voting rights is a subjective question, i'd like ptl involvement20:40
mikaljeblair: there was concern that puts infra "on the hook"20:40
jgriffithmikal: they're out of the control of infra/community20:40
jgriffithmikal: leaves us in a *bad* spot IMO20:41
jgriffithmikal: at least to start20:41
mikaljgriffith: I don't think there's concensus there20:41
anteayaalso in cross project testing like smokestack, which ptl's opinion breaks a tie?20:41
jgriffithmikal: if the tests are on our infra I'm all for it20:41
mikaljgriffith: oh, there is on "at the start"20:41
jgriffithmikal: if they're external I don't think they should vote20:41
mikaljgriffith:  the current proposal is you don't vote for like the fix 6 months or whatever20:41
markmcIMHO, V -/+1 votes aren't all that different from R -/+1 votes20:41
markmcyou learn to trust some and ignore others20:41
jgriffithmikal: I just envision gate clogging due to third party infra20:41
ttxanteaya: no need to vote. If there is no consensus, that can be brought to tc20:42
mordredjgriffith: I think when we say vote - we mean +1/-1 - never +2/-220:42
mikalmarkmc: the problem is devs who filter on verified status20:42
devanandamikal: I think non-voting until there is PTL confidence20:42
anteayattx k20:42
markmcso be permissive in giving rights20:42
jgriffithmordred: but what about -120:42
mikaldevananda: yeah, that's where we were going20:42
mordredjgriffith: it's non-blocking20:42
devanandamordred: i don't think -1 should be allowed until there is confidence in the third-party system being truthful about that -120:42
jgriffithmordred: ok, that's what I was getting at20:42
mikaljgriffith: well, we're talking check queue here, not gate queue20:42
jgriffithmordred: mikal sorry20:42
jgriffithcarry on :)20:42
mordreddevananda: ++ I do agree with that20:42
mikalIIRC infra already has a policy that gate checks must be run by infra20:42
sdagueso given the level of debate.... ML thread?20:42
*** spzala has joined #openstack-meeting20:42
sdagueI don't think this should be trapped in the tc20:42
ttxsdague: yep. And then cross-project meeting topic20:43
mikalWorks for me20:43
ttxok, moving on20:43
lifelessmikal: it does20:43
mikalNoting that the people we're trying to talk to don't read our mailing lists20:43
lifelessmikal: but things can change :P20:43
ttxmikal: too bad20:43
*** gokrokve has joined #openstack-meeting20:43
ttx#topic Recommendation to deprecate XML in new major API versions20:43
*** openstack changes topic to "Recommendation to deprecate XML in new major API versions (Meeting topic: tc)"20:43
ttx#link http://lists.openstack.org/pipermail/openstack-tc/2014-January/000494.html20:43
ttxSo I think it's definitely in our realm to make such a "recommendation"20:43
ttxWith the projects PTLs being the ultimate deciders on what they want to support or not, based on their project history and users20:43
sdagueright, so this thread is in a couple of different forums, -dev, general list, and -tc20:44
ttxsdague: could you sum up the reaction on the ML so far ?20:44
sdagueso far on the general thread the only opposition is pointing to the user survey20:44
sdagueand the 30% XML number20:44
sdaguehowever, it's not really clear to me how that number is possible20:44
ttxat the very least  ithink we could say "don't feel forced to support XML in future versions of your API"20:44
russellbwhich i think we should ignore for the most part20:44
sdaguerussellb: agreed20:44
ttxif that helps them say no20:44
mikalThere was some talk internal to Rackspace about getting usage numbers20:45
mikalBut it doesn't seem to have happened yet20:45
mikalWhich makes me sad20:45
sdagueI've asked user committee for some clarification, and better future questions20:45
russellbttx: +120:45
russellbbut really should be up to projects20:45
hub_capso what about current api's? could i, say, rip it out of trove if no one complains?20:45
markmcrussellb, ignore because you think it's unreliable data right?20:45
russellbmarkmc: yes20:45
markmcrussellb, (just wanna make sure you're not misinterpreted :)20:45
sdaguemarkmc: yes, it's suspect data20:45
russellbmarkmc: the question was quite poor for what we're trying to get at20:45
russellbmarkmc: thank you20:45
sdagueI think I had a general list post sort of discecting that20:45
devanandai have the same question as hub_cap -- we were discussing XML support in ironic today. it's currently broken, cause most of our work has been for the JSON API.20:45
hub_capmikal: i _know_ rax dbaas usage was like .2%20:46
hub_capfor xml20:46
sdagueright, so that's actually what I want to do20:46
devanandai'll happily just omit XML if there's broad support for not supporting it20:46
ttxsdague: so I think there is room for a governance repo change proposal with mild language like "don't feel forced to support XML in fuure major versons of your api"20:46
* mordred in favor of saing xml not required20:46
hub_capyea and ours is unused and id love to nuke it before my first integrated release :)20:46
russellbmarkmc: i really liked your input on the thread btw20:46
stevebaker(heat has no xml api and nobody has yet asked for one)20:46
markmcrussellb, thank you :)20:46
*** jorisroovers has quit IRC20:46
mordredstevebaker: ++20:46
sdaguettx: yes20:46
*** marun has quit IRC20:46
hub_capstevebaker: can i have a heat xml api?20:46
devanandastevebaker: good to know, thx20:46
markmcit's not that I'm trying to save XML support20:46
*** jmh_ has joined #openstack-meeting20:46
markmcbut let's not say "never"20:46
stevebakerhub_cap: noes20:46
hub_capnow u cant say that :)20:46
ttxsdague: that sounds pretty much consensual20:47
markmchigh bar, we've learned some lessons, etc.20:47
*** jroovers has joined #openstack-meeting20:47
sdagueor realistically just saying "openstack services need a stable JSON API"20:47
*** jdob has quit IRC20:47
ttxsdague: not sure it's really needed but if it makes some projects decisions easier...20:47
*** jdob has joined #openstack-meeting20:47
markmcsdague, speaking of which - I just proposed https://review.openstack.org/#/c/68258/20:47
markmcsdague, as a discussion starter20:47
annegentleI am sad with mikal20:47
sdagueI think realistically if we nudge that way, we'll drop most of the XML support in the next set of major releases on API20:47
mordredyah20:47
markmcmost likely20:47
*** gokrokve has quit IRC20:47
jeblairi think we've seen enough feedback right here from recent projects who would have done well to know that xml can be de-prioritized20:48
sdaguebecause I think that everyone is keeping it because they think someone told them they had to20:48
annegentlebut I do think we need to get a better finer set of questions in the survey so we might need to wait for an edict20:48
russellbmarkmc: if heat, how about horizon?20:48
mordredsdague: ++20:48
devanandasdague: ++20:48
markmcrussellb, will add20:48
sdagueand I want to tell them they don't20:48
sdaguethen let the cards fall where they may20:48
annegentlesdague: and your points about the downstream effects are well stated20:48
mordredyup. and if we get people screaing for us to add xml - then it'll be quite clear :)20:48
sdagueannegentle: thanks20:48
russellbon a fundamental point ... is it ever valuable to support multiple encodings, really?20:48
russellbseems silly20:48
sdaguerussellb: I don't think so20:48
mordredat this point, json is pretty darned ubiquitous20:49
russellbbut agree we should not say never20:49
sdaguewhich is why you better let me propose the commit to drop XML from v3 :)20:49
russellbright, json isn't niche or obscure or anything20:49
ttx#action sdague to propose a recommendation about XML not being required in future major versions of APIs20:49
mordredsdague: I will +1 that commit20:49
*** jorisroovers has joined #openstack-meeting20:49
*** mrda_ has joined #openstack-meeting20:49
sdaguettx: sure, I think markmc has beginning discussion review as well20:49
russellbyeah20:50
hub_capdo we need to add a note about current versions of the API if projects decide to drop it asap?20:50
hub_capcough, cough, trove20:50
markmcrussellb, yeah, it can be useful when consuming from different languages or frameworks - think Java EE stuff20:50
sdaguehub_cap: well, trove hasn't released as integrated yet20:50
ttxTrove being arguably "not released yet" I think you can do whatever you want20:50
*** fifieldt has joined #openstack-meeting20:50
sdagueI wouldn't complain if you used that as cover to drop20:51
markmcrussellb, oVirt API was JSON, XML and YAML at one point20:51
mordredmarkmc: I got feedback from corporate overlords today that json is just as easy for corporate java types these days20:51
vishymarkmc: those things are valuable if you are actually providing a wadl/wsdl20:51
vishyand the thing works20:51
russellbmarkmc: yeah, don't have first hand experience but i've heard that ... in the perfect world in my head all of these things have evolved good json support by now20:51
markmcmordred, vishy, fair points20:51
hub_capsweet sdague ttx20:51
*** jroovers has quit IRC20:51
ttxanything else on that subject ? we still have a couple items to cover20:51
vishyotherwise they have to write custom bindings anyway, and it isn't harder to write one talking to json20:51
sdaguevishy: right, but we haven't been doing that in a working way for a while20:51
mordredI think it was much more important when we started openstack than it is now20:51
mordredand even then I think it was tenuous20:51
markmcmaybe something will come along better than JSON :)20:52
markmc"never say never"20:52
sdaguettx: I'm good20:52
mordredmarkmc: protobuffer!20:52
russellbmarkmc: +120:52
ttx#topic Minor governance changes20:52
*** nermina has quit IRC20:52
*** openstack changes topic to "Minor governance changes (Meeting topic: tc)"20:52
ttxProgram/project mapping (https://review.openstack.org/#/c/65096) just needs more +1s I think20:52
russellbmarkmc: but in your patch "at least JSON" for now seems like a good statement for today20:52
ttxor do -1 with a comment if there is a reason you did not approve that one yet20:52
*** burt1 has quit IRC20:52
ttxMention scope expansion in incubation requirements (https://review.openstack.org/#/c/62612/)20:52
ttxSince this document represents consensual requirements, we originally rejected it because mordred & jgriffith and were -1 on the idea20:53
ttxmordred, jgriffith: did your position change on that subject ?20:53
annegentleI still need to send a ML post about a user program that contains horizon/cli rather than horizon being a program, to which list does that discussion need to go?20:53
ttxI see jgriffith +1ed20:53
* markmc will be lazy and paste his comments from gerrit20:53
markmcMain objection seems to be that this is a subjective requirement rather than an objective one. And also a lot of talk about "finite resources".20:53
markmcI don't see this being about "finite resources" but instead a "we're not going to add projects which would mean a crazy jump in OpenStack's scope". We're not going to add a gmail SaaS clone, for example.20:53
markmcYes, it's subjective ... but so is e.g. "large and diverse".20:53
markmcThe goal is twofold - (1) warn authors of new projects that this isn't a free-for-all, even if you tick all the other boxes then there will be a "does this increase of scope make sense?" discussion and (2) reassure those that worry about OpenStack's scope going crazy that we do actually think about this.20:53
russellbannegentle: openstack-dev i think20:53
russellbannegentle: but i don't think that reflects reality20:53
russellbmaybe if we have open discussion time ...20:54
annegentlerussellb: because there's no Dev Experience program? or. Yeah discussion time.20:54
*** egallen has joined #openstack-meeting20:54
*** jieryn has quit IRC20:54
ttxmarkmc: I agree with the goals and I'm ready to +1 the thing. The reason it wasn't approved originally was because jgriffith and mordred didn't like it, and this doc needs consensus20:54
mordredmarkmc: yeah - my concerns are purely that we make sure those goals, which are good, don't come across as prescriptive or legalistic checkboxes20:54
markmcttx, yeah, my reading of the discussion is that the intent was misunderstood20:54
*** markmcclain has joined #openstack-meeting20:54
ttxmarkmc: the discussion on reusing "mesaured growth" as a tool to adjust bandwidth for teams like docs is abit orthogonal yes20:55
markmcmordred, purely objective requirements are in danger of becoming a checkbox list though20:55
russellbi read this as adding "the scope shouldn't be some bonkers crap that came out of left field and is way off from the current scope"20:55
markmcmordred, "I ticked all the boxes! You have to take me!"20:55
markmcmordred, "uh, no - you're a github clone, that makes no sense"20:56
mordredmarkmc: maybe s/must/should/ and I'd be better20:56
mordredor something20:56
mordredor - screw it - I'm probably being too nitpicky here20:56
*** jasondotstar has quit IRC20:56
russellbheh20:56
mordredlet me just go back and vote properly in the thing20:56
ttxok, looks like we have a deal20:57
*** mdurnosvistov has quit IRC20:57
ttx#topic Open discussion20:57
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:57
ttxAnything else, anyone ?20:57
annegentleoo oo! Is there a user experience program need?20:57
russellbso annegentle ... we've talked a lot before about programs being about teams of people20:57
russellbi don't think the people working on all of the CLIs and horizon are a single group20:57
russellbso i don't think it makes sense to try to make that a program (right now anyway)20:57
annegentleso if the common cli starts to live in oslo, will that hamper progress due to the nature of the program they're under?20:58
russellbunless someone steps up to organize such an effort to pull all these things together20:58
markmcmordred, changed it to should20:58
annegentleor does it actually help the common CLI get more resources20:58
ttxrussellb: ++20:58
*** roaet has joined #openstack-meeting20:58
*** galstrom is now known as galstrom_zzz20:58
sdagueannegentle: honestly, I don't think a program declaration is going to get more resources on a thing. Get people working on a thing first20:58
ttxI thinnk UX needs some mileage20:59
russellbwhich btw ... i would love to see all the CLIs be pulled together under a team20:59
sdaguerussellb: +120:59
russellbbut someone (and a group) has to actually step up to do that20:59
russellbwe can't force it20:59
annegentlerussellb: ya ok20:59
*** obondarev_ has quit IRC20:59
russellbi've mentioned it to a few people as a possible area to step up and lead20:59
sdaguethe current ML thread (which is massively deep) has some good stuff on it21:00
russellbwe'll see21:00
ttxlooks like we are done21:00
russellbsdague: cool, that looked promising ... though i fell way behind on it21:00
sdaguejesse's direction I like21:00
ttx#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Tue Jan 21 21:00:25 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-01-21-20.03.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-01-21-20.03.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-01-21-20.03.log.html21:00
*** emagana has quit IRC21:00
*** emagana has joined #openstack-meeting21:00
*** mrodden has joined #openstack-meeting21:01
*** mrodden1 has quit IRC21:01
ttxdolphm, notmyname, jd__, markwash, jgriffith, russellb, stevebaker, david-lyle, markmcclain, hub_cap: around ?21:01
russellbo/21:01
*** tongli has quit IRC21:01
stevebakerO/21:01
david-lyleo/21:01
dolphmo/21:01
devananda\o21:01
markmcclaino/21:01
jd__o/21:01
*** madmike has joined #openstack-meeting21:02
ttxjeblair, mordred: will need you around for this one too21:02
jeblairo/21:02
*** ericyoung has quit IRC21:02
hub_capaye21:02
*** nermina has joined #openstack-meeting21:02
ttx#startmeeting project21:02
openstackMeeting started Tue Jan 21 21:02:33 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
lifelessttx: need me ? :)21:02
*** openstack changes topic to " (Meeting topic: project)"21:02
mordredo/21:02
openstackThe meeting name has been set to 'project'21:02
* flaper87 is here in case an update on oslo is needed21:02
sdagueo/21:02
mordredttx: bah. I don't believe in meetings21:02
ttxlifeless: you can have that hour of your life back21:02
hub_capso does the o/ actually do something bot related?21:02
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:02
ttxhub_cap: no21:03
ttxThe main topic of discussion for today is obviously the situation with the frozen gate and the consequences for icehouse-221:03
ttx#topic Frozen gate situation21:03
*** openstack changes topic to "Frozen gate situation (Meeting topic: project)"21:03
ttxso, on that topic...21:03
ttxFirst of all, I would like to discuss the current situation: flow rate, main causes21:03
ttxs othat everyone ois on the same page21:03
*** gokrokve has joined #openstack-meeting21:03
ttxsdague, jeblair, mordred: any volunteer to summarize the current state ?21:03
sdaguesure21:04
sdagueso we've got kind of a perfect storm of issues21:04
sdaguewe're hitting non linear scaling issues on zuul, because we're throwing so much at it21:04
sdagueand the gate queue is so long21:04
sdaguewe're in starvation for nodes in general21:04
sdagueour working set is much bigger than all the available nodes to us21:05
*** mfink has quit IRC21:05
sdagueand we've got a bunch of new gate reseting issues that cropped up in the last couple of weeks21:05
*** prad has quit IRC21:05
ttxis that node starvation due to lack of cloud resources ? Or something else ?21:05
*** lblanchard has quit IRC21:05
*** lyxus has quit IRC21:05
sdaguewhich we were blind to because we were actually loosing console logs to elastic search21:05
sdaguettx: lack of cloud resources21:05
sdaguebasically we're swapping21:06
ttxsdague: is that something we need to ask our kind sponsors to help with ?21:06
sdaguettx: it has been requested21:06
ttxsdague: ok21:06
russellbi think i saw mordred say he was asking21:06
*** zul has quit IRC21:06
sdagueyep, mordred is working that21:06
mordredyes. I have emailed rackspace about more nodes/quota21:06
ttxsdague, mordred: let me know if smoe kind of officioal foundation statement can help21:06
jeblairsdague: i don't want to contradict anything you have said, all of which are correct, but i don't think starvation is having a huge impact on throughput21:06
mordredpvo hasn't given a final answer back yet21:06
sdaguejeblair: that could be21:07
*** markwash has joined #openstack-meeting21:07
pvomordred: if you could take iad or dfw, that would be a huge help.21:07
pvois that possible?21:07
mordredhp's new cloud region is where new capacity comes from, and those nodes do not work well for us in the gate yet- so we're dependent on rax for additional node quota if we're getting any21:07
sdaguethough yesterday we were thrashing due to node starvation21:07
*** ivar-lazzaro_ has quit IRC21:07
mordredpvo: I believe so?21:07
sdaguein some interesting patterns21:07
mordredjeblair: thoughts on pvo's question?21:07
jeblairalso, it is worth mentioning that the reduction in tempest concurrency is likely affecting throughput21:07
*** oubiwann_ has quit IRC21:07
sdaguebut we can debate the subtleties later21:07
*** ildikov has quit IRC21:08
sdaguejeblair: well, it saw a noticable increase in reliability21:08
pvomordred: I can get the quotas raised there if that'll work for you. I"ve been going back and forth with our ops guys.21:08
ttxso what's the flow rate right now ? 20 changes per day ? more ? less ?21:08
sdagueso I think, on net, it's helping21:08
jog0https://github.com/openstack/openstack/graphs/commit-activity21:08
jog0flow21:08
jeblairpvo: absolutely21:08
*** Duane_ has quit IRC21:08
ttxjog0: awesome htx21:08
pvojeblair: mordred: cool. I'll try to get those changes done today.21:08
mordredpvo: thanks! I owe you much beer21:09
sdagueI've spent enough time looking at the perf data now, that I'm very much with russellb, 4x concurency puts the environment at such a high load for so long, we get unpredicable behavior21:09
russellb+121:09
mikalsdague: is there a guide to running tempest somewhere? I can't see one on the wiki and am ashamed to admit I've never run it in person.21:09
russellbit's just a non-starter right now21:09
ttxOK, do we have reasons to hope things will get back to a flow rate in the near future that would let us absorb that backlog ?21:09
pvomordred: np. whats the tenant id again?21:09
russellbpvo: thanks a ton21:09
*** julim has quit IRC21:09
pvocan private message that  if you want21:09
mikalSorry, wrong channel21:10
sdagueheh21:10
sdaguettx: without more people helping on the race fix side... no21:10
*** markwash_ has joined #openstack-meeting21:10
sdaguewe're going to mitigate some things, to make us thrash less21:11
sdaguebut we won't get back to normal flow until we aren't doing so many resets21:11
russellbi've had a fix for a huge offender up for 5 hours, but it's so behind we can't get it in21:11
*** doug_shelley66 has quit IRC21:11
ttxsdague: do we have a bug number for the key issue(s)21:11
russellbit hasn't shown up in check yet even21:11
sdaguettx: I put 2 on the list yesterday21:11
ttxsdague: ok, those two are still current21:11
russellbhttps://review.openstack.org/#/c/68147/3 ... fixes a bug with 340 hits in the last 12 hours21:12
sdaguepart of it is also discovering the resets21:12
*** markwash has quit IRC21:12
*** markwash_ is now known as markwash21:12
sdaguettx: yes, I had a morning update on list about it21:12
*** doug_shelley66 has joined #openstack-meeting21:12
ttxOK... As far as the icehouse-2 milestone goes, we need to decide if it makes sense to cut branches at the end of the day today, or if we should just delay by a week21:12
ttxOn one hand, a milestone is just a point in time, so we can cut anytime21:12
ttxOn the other hand, we want it to be a *reference* point in time, and here we have a lot of stuff in-flight... so cutting now is a bit useless21:13
sdaguehonestly, we're only at about an 80% characterization rate right now as well, so there could be killer bugs we haven't identified yet21:13
ttxDecision all depends on our confidence that adding a week will make a difference.21:13
ttxthat the currently in-flight stuff will make it.21:13
ttxwhich in turn depends on our ability to restore a decent flow rate to absorb the backlog.21:13
ttxI'm open to suggestions here21:13
annegentlettx: I do see people try to install milestone releases, so do wait if you think it would help21:13
ttxhttp://status.openstack.org/release/ should show how many bleuprints are stuck in queue for i221:14
*** marekd|away is now known as marekd21:14
*** oubiwann_ has joined #openstack-meeting21:14
sdaguemy instinct is cut what we have, the trees were always supposed to be shippable21:14
jog0ttx: I am not sure if waiting a week is enough TBH.  If we don't fix the gate a week won't help21:14
russellbsdague: same here21:14
sdaguemy concern is that if we delay i2, then all these people are going to rush the queue harder21:14
mordredyeah. we're not timed-based-releses for nothing round here21:14
russellbi say just cut21:14
jog0++21:14
russellbsdague: that's a very good point21:15
russellbwe don't need to encourage a gate rush right now21:15
russellbwe need people to chill out for a while21:15
annegentleyeah avoid gate rush. I'm just going back and forth here. I'll stop21:15
ttxsdague: I'm fine with cutting now if you PTLs are fine with that21:15
stevebakerI vote for doing a cut now21:15
ttxit will looks a bit empty but who cares21:15
russellbttx: sometimes we get to fail in public, and i think that's OK21:15
sdagueyeh, I already had one group ping me for a requirements review so they could land something in i2 this morning21:15
devanandawill this encourage folks whose changes are in-flight ut dont make it to delay them further, making a bigger rush for I3 ?21:16
hub_capif it will alleviate the mental push to help clean up the Q a bit, lets do it21:16
kgriffsI'm fine with a cut now, except there is one patch that I really need to land first that has been stuck for hours.21:16
sdaguedevananda: we're going to have a bigger rush in i3 regardless21:16
russellbif we weren't all so damn busy, we could write a book on all the amazing lessons we're learning along the way :)21:16
sdaguerussellb: ++21:16
ttxso.. let's say I'll cut early next morning, which gives a bit of time for things to land21:16
kgriffs+121:16
ttxthat would be like 7am MST21:16
david-lylehorizon may have a licensing issue if we cut now, may need to get a fix in21:16
*** mrda is now known as mrda__21:16
*** MarkAtwood has quit IRC21:16
*** mrda_ is now known as mrda21:16
ttxwould that work for everyone ?21:16
sdaguettx: good for me21:17
dolphmi'm fine with cutting now21:17
hub_cap++21:17
ttxand then tag the next morning same hour21:17
david-lylehttps://bugs.launchpad.net/horizon/+bug/127076421:17
ttxor even tag on the same day21:17
mordredttx: we may want to get ptls to indicate super-important must-land patches in case promoting them is necessary21:17
ttxit's not as if backpotrs would make it through anyway21:17
sdagueyeh, if there is a licensing patch, that would qualify21:18
ttxso... branch cut at 7am MST, tag toward the end of the afternoon21:18
dolphmmordred: i hope you're not referring to blueprints .. ?21:18
russellbworks for me21:18
stevebakerttx: This Critical fix needs to get in one way or another https://review.openstack.org/#/c/68135/21:18
russellbi dont' care about landing more features, i just want to help restore the gate :)21:18
russellbat this point21:18
sdaguerussellb: +121:18
ttxsdague: could you add it to your magic list of priority fixes ?21:18
mordreddolphm: nope. I just think there are a couple of things, like the license thing, that we should help land before the morning if we can21:18
mordredrussellb: ++21:18
markmcclainrussellb: ++21:18
ttxhttps://review.openstack.org/#/c/68135/21:18
dolphmrussellb: ++ please21:19
russellbtrying21:19
sdaguettx: so it has to have *some* recent test results21:19
ttxif we fail to land it today, we still have the backport option tomorrow21:19
sdaguebefore we promote21:19
*** madmike has quit IRC21:19
ttxsdague: ack21:19
mordredttx: I need to run - are we good on the portion of the meeting for which I'm useful?21:20
ttx#agreed I2 branch cut around 7am MST tomorrow. Tags expected toward the end of day21:20
*** dvarga has quit IRC21:20
ttxmordred: I think we cna handle it frmo here21:20
*** dvarga has joined #openstack-meeting21:20
ttxdamn it21:20
russellbsdague: nova fix is in the check queue now at least (no dsvm nodes yet)21:20
hub_capheh21:20
ttxmordred: I think we can handle it from here21:20
*** prad has joined #openstack-meeting21:20
sdaguerussellb: yeh, there is something else going on, like last week21:20
*** oubiwann_ has quit IRC21:20
markwash7 AM MST3K?21:21
sdaguetoo many meetings this afternoon to dive on it :)21:21
*** MaxV has joined #openstack-meeting21:21
markwashI'm down21:21
ttxsdague: let's make this one quick21:21
ttx#topic stable/havana situation (david-lyle)21:21
*** openstack changes topic to "stable/havana situation (david-lyle) (Meeting topic: project)"21:21
ttxSo stable/grizzly was broken a few weeks ago, which is turn paralyzed stable/havana (due to grenade trying to run stable/grizzly stuff)21:21
ttxMy understanding is that it's all put on the backburner until we get the master gate in order21:21
ttxand in hte mea ntim we should not approve stable/* stuf21:22
ttxmean time... stuff21:22
russellbseems stable +A was removed anyway :)21:22
sdagueyeh21:22
ttxhah21:22
ttxgood21:22
russellbsolves that.21:22
sdaguewe made an executive call on that on sunday21:22
ttxdavid-lyle: comment on that ?21:22
ttx(you raised that topic)21:22
david-lyleok, just checking.  I think queued up jobs are finally failing21:22
sdaguethe stable/grizzly fix is actually in the gate21:22
sdaguedavid-lyle: are there still stable jobs in the gate?21:23
*** nati_ueno has joined #openstack-meeting21:23
*** dprince has quit IRC21:23
sdagueI thought we managed to kick those all out21:23
david-lylewanted to verify21:23
*** markmcclain has quit IRC21:23
sdagueI believe - https://review.openstack.org/#/c/67739/ will make stable/havana work in the gate again21:23
david-lylesdague: I believe I saw a couple Horizon failures yesterday21:23
sdaguestable/grizzly is actually working again21:23
sdaguedavid-lyle: gate or check21:23
ttxok21:23
*** spzala has quit IRC21:23
ttxso this is actually being solved  too21:23
ttxdavid-lyle: anything more on that topic ?21:24
david-lylesdague: I think gate21:24
david-lylettx: no, I'm good21:24
*** oubiwann_ has joined #openstack-meeting21:24
ttx#topic common openstack client (markwash)21:24
*** openstack changes topic to "common openstack client (markwash) (Meeting topic: project)"21:24
sdaguedavid-lyle: so if there are any other stable/havana things in gate, we should remove them21:24
ttxmarkwash: floor is yours21:24
*** markmcclain has joined #openstack-meeting21:24
markwashokay, I was really just hoping to do a quick poll here21:24
david-lylesdague, ack21:24
markwashthe discussion in  openstack dev is about what kind of approach to take: many client projects, one client project21:25
ttxone21:25
*** beagles has quit IRC21:25
ttxoh21:25
markwashI'm interested especially because I want to make some changes to glanceclient, and would love to know where to put it21:25
*** b3nt_pin has joined #openstack-meeting21:25
*** b3nt_pin is now known as beagles21:25
ttxI'm more worried about MULTIPLE unified client projects21:25
markwashthere's also a difference between one CLI client and one library SDK21:26
ttxI thought openstackclient was the one but hte discussion seemed to point to something else (haven't read it in detail yet)21:26
sdaguemarkwash: my read of the thread is you should keep doing what you are doing now, I can't imagine this becomes reality pre icehouse21:26
*** dvarga is now known as dvarga|away21:26
*** dvarga|away is now known as dvarga21:26
markwashsdague: makes sense21:27
markwashIf no one else has anything they want to share re one vs many I'm good. . I just was hoping to hear from any PTLs who felt strongly21:27
jd__whatever works :)21:28
dolphmthis is in regard to one SDK, correct?21:28
dolphmnot another CLI?21:28
stevebakerI would be happy to get behind a unified client, but I've still not got around to integrating heat with python-openstackclient21:28
markwashdolphm: I think that's the key distinction, yeah. . not a lot of opposition in my mind to unifying the CLI21:28
ttxyeah, we really need someone to head that client projects division21:29
ttxand push things forward21:29
ttxin a coherent way21:29
sdaguehonestly, I'm very pro unified CLI and unified SDK. But I don't think this is an icehouse thing regardless21:29
markwashmy take is, programs should own their little part of the SDK within reason, but we can probably solve that regardless of how we structure the client repo(s)21:29
sdagueI'm happy that people are diving on it21:29
ttx#topic Red Flag District / Blocked blueprints21:30
*** openstack changes topic to "Red Flag District / Blocked blueprints (Meeting topic: project)"21:30
ttxAny inter-project blocked work that this meeting could help unblock ?21:30
dolphmmarkwash: ++21:30
ttxThough I suspect the gate is the common issue21:30
*** markmc has quit IRC21:30
*** ArthurBerezin has joined #openstack-meeting21:31
*** amcrn has quit IRC21:31
ttxOK, I guess none then21:31
ttx#topic Incubated projects21:31
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:31
*** ArthurBerezin has left #openstack-meeting21:31
SergeyLukjanovo/21:31
*** SumitNaiksatam has quit IRC21:31
devanandao/21:32
ttxdevananda, kgriffs, SergeyLukjanov: will cut your branches at the same time as the grown-up's21:32
devanandagreat :)21:32
SergeyLukjanovworks for me too21:32
SergeyLukjanovin savanna, we're only have 1 bp and 1 bug in flight21:32
SergeyLukjanovhttps://launchpad.net/savanna/+milestone/icehouse-221:32
devanandawe've got a bunch of bug-fixes in flight, stalled on the same slow gate that the grown-ups are stalled on.21:32
*** NikitaKonovalov is now known as NikitaKonovalov_21:32
ttxI will defer what's still open21:32
ttxso keep your blueprints status current21:33
ttx(and your bugs too)21:33
ttxany question on that process ?21:33
devanandaour BP status is correct (2 implemented) I've deferred the rest that were targeted previously21:33
*** amcrn has joined #openstack-meeting21:33
devanandaplease feel free to defer any still-open bugs when you cut. we'll land what we can in the meantime21:33
devanandano questions here21:34
ttx#topic Open discussion21:34
*** openstack changes topic to "Open discussion (Meeting topic: project)"21:34
*** Duane_ has joined #openstack-meeting21:34
ttxAnything else, anyone ?21:34
sdagueon the cross project front...21:34
sdagueif you are using eventlet.wsgi to log requests, please turn debug off21:34
sdaguehttps://review.openstack.org/#/c/67737/21:34
sdagueI proposed that to neutron and nova21:34
sdagueotherwise you get a ton of log spam21:34
ttx#info if you are using eventlet.wsgi to log requests, please turn debug off https://review.openstack.org/#/c/67737/21:35
devanandasdague: thanks for the pointer. I suspect we need to do taht, too21:35
ttxOK, back to useful work, then.21:35
SergeyLukjanovttx, are you planning to use 'proposed/icehouse-2' instead of mp branches for i3?21:35
ttxno, mp21:35
ttxthe change wasn't merged yet21:35
ttxwe migt try that for i-321:35
ttxanything else ?21:35
*** MaxV has quit IRC21:36
ttxok then21:36
ttx#endmeeting21:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:36
openstackMeeting ended Tue Jan 21 21:36:19 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2014/project.2014-01-21-21.02.html21:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2014/project.2014-01-21-21.02.txt21:36
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2014/project.2014-01-21-21.02.log.html21:36
ttx24min to do some useful work now21:36
*** MaxV has joined #openstack-meeting21:36
stevebakerw00t21:36
*** gyee has joined #openstack-meeting21:37
*** jprovazn has quit IRC21:37
*** SlickNik has joined #openstack-meeting21:38
*** nkinder has left #openstack-meeting21:40
*** beagles has quit IRC21:41
*** wenlock has left #openstack-meeting21:42
*** b3nt_pin has joined #openstack-meeting21:43
*** b3nt_pin is now known as beagles21:43
*** asalkeld has joined #openstack-meeting21:44
*** fifieldt has quit IRC21:47
*** beagles has quit IRC21:48
*** reed has joined #openstack-meeting21:52
*** jasondotstar has joined #openstack-meeting21:52
*** sarob_ has joined #openstack-meeting21:53
*** amitgandhi has joined #openstack-meeting21:54
*** sarob_ has quit IRC21:54
*** amitgandhi has quit IRC21:54
*** amitgandhi has joined #openstack-meeting21:54
*** sarob_ has joined #openstack-meeting21:55
*** peristeri has joined #openstack-meeting21:56
*** doug_shelley66 has quit IRC21:56
*** sarob has quit IRC21:56
*** jsavak has joined #openstack-meeting21:56
*** doug_shelley66 has joined #openstack-meeting21:56
*** jcoufal has joined #openstack-meeting21:56
*** sarob_ has quit IRC21:57
*** fifieldt has joined #openstack-meeting21:58
*** jdob has quit IRC21:58
*** joesavak has quit IRC21:59
*** dvarga has quit IRC22:00
*** sarob has joined #openstack-meeting22:00
*** sarob has quit IRC22:00
david-lyle#startmeeting Horizon22:01
openstackMeeting started Tue Jan 21 22:01:15 2014 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.22:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:01
*** openstack changes topic to " (Meeting topic: Horizon)"22:01
openstackThe meeting name has been set to 'horizon'22:01
*** roaet has left #openstack-meeting22:01
*** sarob has joined #openstack-meeting22:01
jomara_hola22:01
david-lylehello horizoners22:01
jtomasekhello22:01
lsmolahello22:01
jpichHey22:01
MaxVhey22:02
mrungehello o/22:02
david-lylehorizoneers?22:02
david-lylewe need something beter22:02
*** sarob_ has joined #openstack-meeting22:02
jomara_horizonistas22:02
david-lylebetter22:02
jcoufalo/22:02
jomara_^^^22:02
*** sarob_ has quit IRC22:02
*** lblanchard has joined #openstack-meeting22:02
*** Toshi has joined #openstack-meeting22:02
lblanchardo/22:02
lsmola:-)22:02
david-lyle#topic General22:03
*** openstack changes topic to "General (Meeting topic: Horizon)"22:03
david-lyleThe status of the gate is a very big problem and not likely to change very soon22:03
mrungecough22:03
*** ngb_ has joined #openstack-meeting22:04
mrungeis there anything we can do about this?22:04
lsmolapray?22:04
david-lyleThere was discussion of postponing i-2  to let more patches land, but people were not optimistic that would help22:04
david-lyleSo, here's the status, as I understand it22:04
david-lylestable/havana broken and on the back-burner22:04
mrungegrizzly is broken as well22:05
*** ngd has joined #openstack-meeting22:05
david-lylecore you should not be able to approve for that right now, and don't do rechecks/reverifies22:05
david-lylethat's on the back burner until trunk works22:05
MaxVmaybe a mail to avoid recheck reverify could be interesting22:06
david-lylefor trunk, two things may help a little, more capacity and less gate pressure with the milestone being passed22:06
*** sarob has quit IRC22:06
mrungeMaxV, at least stable maintainers got such a mail22:06
david-lylesome fixes are in the gate queue but are stuck as well for now22:07
david-lyleAnyway, i-2 will close in the morning22:08
david-lyleanything stuck in the queue will move to i-322:08
david-lylehttps://launchpad.net/horizon/+milestone/icehouse-222:09
*** sarob has joined #openstack-meeting22:09
david-lylelots of solid work has gone into i-2 and hopefully we can make better progress in i-322:10
david-lylelots left on the plate22:10
*** nati_ueno has quit IRC22:10
mrungequite impressing folks!22:10
*** doug_shelley66 has quit IRC22:10
david-lyleany questions before we move on to the agenda?22:11
*** tzumainn has joined #openstack-meeting22:11
*** nati_ueno has joined #openstack-meeting22:11
david-lyleok, https://launchpad.net/horizon/+milestone/icehouse-322:12
*** ngb_ has quit IRC22:12
*** esker has quit IRC22:12
jpichThat's one long list22:13
david-lyleis way to full.  I will start paring that down this week.  If you own something and it gets moved out.  If you complete it, we can move it back in22:13
david-lyles/to/too22:13
mrungesounds good to me22:13
*** amitgandhi has left #openstack-meeting22:14
david-lyleif you own something you know you won't have time for in the next 5-6 weeks let me know and I can move it22:14
*** harlowja is now known as harlowja_away22:14
david-lyle#topic jshint issue22:14
*** openstack changes topic to "jshint issue (Meeting topic: Horizon)"22:14
david-lyleso, we've recently determined we can't bundle jshint22:15
david-lyledue to licensing issues22:15
david-lylewe will remove it before the i-2 milestone is cut22:15
MaxVI think we are stuck with this silly sentence in the licence22:15
lsmola:-o22:16
mrungeyupp MaxV22:16
david-lylemrunge has a revert https://review.openstack.org/#/c/68268/ up for review22:16
mrungejslint upstream made it clear not to re-license that stuff22:16
mrungeand jshint still bases on jslint22:16
*** termie has quit IRC22:16
david-lyleunless someone tells me, the world's going to collapse if we revert, I will approve it after the meeting22:16
MaxVthe world will not collapse but it is like coding in python without pep822:17
*** termie has joined #openstack-meeting22:17
david-lylewhat we need to work toward is separating the js/css from horizon22:17
mrunge+122:17
david-lyleMaxV: understood22:17
mrungenothing prevents us from requiring separate libraries22:18
MaxVmaybe the separation needs to be made quickly, a lot of issues depend on it22:18
mrungebut we may not bundle libs22:18
david-lylemordred and krotscheck have some interesting things up for review  https://review.openstack.org/#/c/67729/ and https://review.openstack.org/#/c/67721/22:18
david-lylethis will install node in the venv using tox, by pulling it down.  I also does this on the gate servers22:19
david-lyles/I/It/22:19
mrungeouch22:19
*** vipul is now known as vipul-away22:19
david-lylethis would allow us to run node based tools in the gate jobs, but not bundle it, nor require it22:19
jcoufal+1 for separation js/css22:20
david-lylewe can leverage node, or not where applicable22:20
*** asalkeld has quit IRC22:20
MaxVdo we have a blueprint or a draft for this?22:20
david-lylethe split is part of the large split bp22:20
david-lyleI didn't get any opposition to the idea22:20
david-lylethe nodejs toolchain integration is not necessarily part of that change22:21
david-lylethe split is beneficial either way22:21
david-lyleI just wanted to point out that there will be options22:22
mrungeMaxV, for reference https://blueprints.launchpad.net/horizon/+spec/separate-horizon-from-dashboard22:22
david-lylethanks mrunge22:22
david-lyletoo many windows open for me22:22
*** pnavarro has quit IRC22:22
mrungeyeah. always the same...22:22
*** burt1 has joined #openstack-meeting22:23
*** oubiwann_ has quit IRC22:23
*** aignatov is now known as aignatov_22:23
david-lyleback to topic though, jshint is going for now22:23
*** yassine has quit IRC22:23
david-lyle#topic meeting-time22:23
*** openstack changes topic to "meeting-time (Meeting topic: Horizon)"22:23
*** vijendar has quit IRC22:24
david-lylehttps://review.openstack.org/#/c/67152/ is up for review and will add logging to a new meeting room22:24
*** nati_ueno has quit IRC22:24
david-lyleonce that's approved, we will move the meeting time.  Thanks everyone who is still dealing with terrible TZ differences for sticking with us until that happens22:24
*** vipul-away is now known as vipul22:25
david-lyleagain I will send an email to the ML when I can make it happen22:25
*** vipul is now known as vipul-away22:25
lblanchardthanks david-lyle!22:25
mrungedavid-lyle, thanks for tracking this change down for us!22:25
*** Duane_ has quit IRC22:25
david-lyle#topic Discuss integration of Tuskar UI22:26
*** openstack changes topic to "Discuss integration of Tuskar UI (Meeting topic: Horizon)"22:26
jcoufalthank you david-lyle22:26
david-lyleso we are closer here22:26
*** ayoung has quit IRC22:26
*** marekd is now known as marekd|away22:27
david-lylethe launchpad group is now owned by horizon-drivers22:27
*** prad has quit IRC22:27
david-lyleplease send a list of the current tuskar-ui core  and I will add those individually22:27
*** elo has joined #openstack-meeting22:28
*** bdpayne has quit IRC22:28
david-lylethe second part is https://review.openstack.org/#/c/68264/22:28
lsmoladavid-lyle, will send you the list tomorrow22:28
*** prad has joined #openstack-meeting22:28
*** ngd has quit IRC22:28
david-lylewhich will need to be approved before the gerrit part will be finalized22:28
*** ayoung has joined #openstack-meeting22:28
lsmoladavid-lyle, do I see only horizon-core can approve?22:31
*** thomasem has quit IRC22:31
*** dims has quit IRC22:31
david-lylelsmola: yes at this point. I think we need to add another gerrit group until tuskar is integrated22:31
david-lyleI need to work with infra on that22:31
lsmoladavid-lyle, or what is horizon-core group in this context?22:31
lsmoladavid-lyle, would be nice to do it before, so we can push patches in :-)22:32
jcoufaldavid-lyle: should that be a special group then?22:33
david-lylelsmola: understood.  TBH, I didn't know about the gerrit/acls files until about an hour ago22:33
lsmoladavid-lyle, ok, great22:33
david-lylejcoufal: I think so for now22:33
*** lcheng has joined #openstack-meeting22:33
*** asalkeld has joined #openstack-meeting22:33
lsmoladavid-lyle, yes, another group for us22:33
jcoufallsmola: we can write the names down and send them tomorrow22:34
*** ayoung has quit IRC22:34
lsmolayes22:34
david-lylejust wanted to let you know we're moving, just slowly like the gate :P22:34
lsmoladavid-lyle, hehe22:34
david-lyleit's contagious22:34
lsmoladavid-lyle, thank you for doing this :-)22:34
lsmolalol22:34
*** harlowja_away is now known as harlowja22:35
jcoufaldavid-lyle: thank you?22:35
jcoufal!22:35
*** stevemar has quit IRC22:35
david-lylesorry, it's taking so long.22:36
david-lylejcoufal: you're welcome?22:36
david-lyle:)22:36
jomara_jcoufal: say it like you mean it!22:36
lsmoladavid-lyle, I think it's going fast :-)22:36
david-lyle#topic Open Season22:36
*** openstack changes topic to "Open Season (Meeting topic: Horizon)"22:36
david-lyleI've been watching the tuskar-ui changes, is progress mostly gated by the API layer?22:37
david-lyleservice layer22:37
*** radez is now known as radez_g0n322:38
lsmoladavid-lyle, not sure what you mean, I am kind of lost in gates22:38
*** devoid has quit IRC22:38
david-lyletied to service layer implementation22:39
jtomasekdavid-lyle: we are mostly mocking data, so we dont depend on api too much with the UI implementation22:39
tzumainndavid-lyle, right now we're kind of developing independently of the api layer, although we communicate with them - we mock22:39
tzumainnoh, right, what jtomasek just said22:39
david-lyleok, thanks22:40
lsmoladavid-lyle, but tuskar API is only small part of what we use22:40
lsmoladavid-lyle, we use also APIs of heat, ironic, nova..22:40
*** doug_shelley66 has joined #openstack-meeting22:40
david-lyleright, makes sense22:41
*** egallen has quit IRC22:41
lsmoladavid-lyle, but right now the whole tuskar UI just call mocked API, yes22:41
*** yassine has joined #openstack-meeting22:41
*** IlyaE has quit IRC22:41
* david-lyle needs to dig in22:41
david-lylebut there's nothing blocking your progress other than Horizon, right?22:42
lsmoladavid-lyle, well yeah, and the APIs, cause we are usning features that don't exist yet22:42
*** krtaylor has quit IRC22:42
lsmoladavid-lyle, that is why we are mocking :-)22:43
david-lylebut the UI can move more quickly than the API22:43
lsmoladavid-lyle, so right now only Horizon22:43
david-lyleso mocks make sense22:43
tzumainndavid-lyle, exactly, that's how we've set up development22:43
david-lylehttps://launchpad.net/tuskar-ui/+milestone/icehouse-222:44
*** sarob has quit IRC22:45
*** dcramer_ has quit IRC22:45
*** sarob has joined #openstack-meeting22:45
*** radsy has joined #openstack-meeting22:45
david-lylesince you're not tied to the release schedule that seems to be fine22:45
*** dims has joined #openstack-meeting22:46
david-lyleok, </my detour>22:46
lsmoladavid-lyle, yes :-)22:46
jcoufaldavid-lyle: in icehouse-3 we are about to deliver the whole deployment management ;)22:46
lsmolahehe22:46
lsmolayes we can do it22:46
*** spzala has joined #openstack-meeting22:47
david-lylejcoufal: glad it's something small and manageable :)22:47
lsmolawith probability like 73 percent22:47
david-lyleI think your decimal place is off22:47
tzumainnlol22:47
david-lyle:)22:47
jcoufal73,9, don't be that pesimistic ;)22:47
lsmolahehe22:47
david-lyleother issues, topics, concerns?22:47
*** ivasev has quit IRC22:48
jpichA short note/PSA/request maybe :-)22:48
david-lyleabsolutely22:48
jpichI wanted to say a quick word about being careful about taking on bugs that are already assigned to someone else. If the bug had recent activity, consider being considerate (:-)) and ask the current assignee first if they're still working on it22:49
jpichIt can be pretty discouraging for people to see their efforts wasted, especially if they're new and/or only have limited time to give to the project (like volunteers contributing in their free time)22:49
jcoufal+1 for that22:50
david-lylejpich: good reminder22:50
mrungeyes!22:50
*** yamahata has quit IRC22:50
*** SergeyLukjanov is now known as SergeyLukjanov_a22:50
lblanchardagreed!22:50
*** yamahata has joined #openstack-meeting22:50
jpichCheers. I saw a few while catching up on my LP backlog, glad we seem to be on the same page :)22:50
*** SergeyLukjanov_a is now known as SergeyLukjanov_22:51
lsmoladefinitely22:51
david-lyleif the bug has an owner, please contact them directly if you feel you can help, or email me and I will contact them22:51
*** jmontemayor has quit IRC22:51
david-lylepeople do get pull away to other things, so it's perfectly fine to ask22:52
david-lyles/pull/pulled/22:52
david-lyleI need a language without tense22:52
david-lyleand spelling22:52
lsmolahehe22:52
lblanchardlol22:52
david-lyleor grammar and punctuation22:52
jpichHaha22:52
lblanchardwingdings?22:52
MaxVtelepathy could be a good solution22:52
lsmolaklingon?22:52
mrungelike simplified English?22:53
MaxVbut I do not think IRC channels exit for that22:53
david-lyleconsidering I haven't mastered my mother tongue, I don't think there's hope with a new language22:53
lsmolalol22:53
jpichI'm partial to speaking multiple languages badly :-)22:53
david-lylebuilt in benefit of the doubt there22:54
david-lylelittle status...  I'm about halfway done with the navigation changes. I hope to have it completed by the end of the week.22:55
jpichCool :)22:56
mrungeyupp, sounds interesting22:56
lsmolagreat22:56
*** prad has quit IRC22:56
david-lyleI imagine I will leave some of the finer stylings to someone in a subsequent patch22:57
jpich+1 to iterative approach22:57
david-lyleanyone else ? lsmola?22:57
david-lyle:)22:57
*** sarob has quit IRC22:58
lsmolahehe22:58
lsmoladavid-lyle, nope :-)22:58
david-lyle???22:58
lsmoladavid-lyle, nothing from me :-)22:58
lblanchardnothing here!22:59
*** mdomsch has quit IRC22:59
david-lyleAlright everyone, great job on i-2.  We have a lot to be proud of, and the items that missed we'll get in i-3.  Keep up the good work.22:59
lsmolayaaay22:59
jpichThanks, everyone!22:59
david-lyle#endmeeting22:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:59
openstackMeeting ended Tue Jan 21 22:59:55 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-01-21-22.01.html22:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-01-21-22.01.txt22:59
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-01-21-22.01.log.html23:00
lblanchardthanks all, have a great week23:00
mrungeyeah, thanks everyone!23:00
jcoufalsounds great23:00
jomara_thanks everyone23:00
lsmolahave a great night everybody23:00
jcoufalthanks david-lyle, all have a great day/night23:00
jtomasekgood night all23:00
*** jpich has quit IRC23:00
*** Gordonz has quit IRC23:01
*** lsmola has quit IRC23:01
*** peristeri has quit IRC23:02
*** neelashah has quit IRC23:02
*** mrunge has quit IRC23:02
*** sarob has joined #openstack-meeting23:03
*** kevinconway has quit IRC23:03
*** jaypipes has joined #openstack-meeting23:03
*** tzumainn has left #openstack-meeting23:03
*** rnirmal has quit IRC23:04
*** ryanpetrello has quit IRC23:04
*** jcoufal has quit IRC23:04
*** HenryG has quit IRC23:07
*** lblanchard has quit IRC23:07
*** sarob has quit IRC23:07
*** harlowja has quit IRC23:07
*** jsavak has quit IRC23:13
*** jecarey has quit IRC23:13
*** jay-lau-513 has quit IRC23:13
*** rdxc has quit IRC23:13
*** burt1 has quit IRC23:14
*** sushils has quit IRC23:17
*** sushils has joined #openstack-meeting23:19
*** jtomasek has quit IRC23:19
*** HenryG has joined #openstack-meeting23:19
*** jmh_ has quit IRC23:22
*** kgriffs is now known as kgriffs_afk23:27
*** neelashah has joined #openstack-meeting23:27
*** krtaylor has joined #openstack-meeting23:27
*** lblanchard has joined #openstack-meeting23:29
*** oubiwann_ has joined #openstack-meeting23:30
*** safchain has joined #openstack-meeting23:34
*** safchain has quit IRC23:34
*** eharney has quit IRC23:34
*** thuc has quit IRC23:35
*** thuc has joined #openstack-meeting23:36
*** Toshi has quit IRC23:38
*** ayoung has joined #openstack-meeting23:39
*** amcrn has quit IRC23:40
*** markmcclain has quit IRC23:41
*** banix has quit IRC23:45
*** MaxV has quit IRC23:46
*** MaxV has joined #openstack-meeting23:47
*** blamar has quit IRC23:47
*** Leonr has quit IRC23:48
*** thuc has quit IRC23:50
*** thuc has joined #openstack-meeting23:50
*** MaxV has quit IRC23:51
*** lblanchard has quit IRC23:52
*** thuc has quit IRC23:55
*** alexpilotti has quit IRC23:56
*** markpeek has quit IRC23:59

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