Tuesday, 2013-10-22

*** danwent has joined #openstack-meeting00:00
*** bpokorny has joined #openstack-meeting00:00
*** spzala has joined #openstack-meeting00:00
*** rongze has quit IRC00:01
*** radsy has joined #openstack-meeting00:01
*** tomoe_ has quit IRC00:02
*** jamespage_ has quit IRC00:04
*** gyee has quit IRC00:05
*** arosen1 has quit IRC00:08
*** vipul-away is now known as vipul00:10
*** SergeyLukjanov is now known as _SergeyLukjanov00:10
*** _SergeyLukjanov has quit IRC00:11
*** btorresgil has quit IRC00:12
*** SergeyLukjanov has joined #openstack-meeting00:15
*** arosen1 has joined #openstack-meeting00:16
*** SergeyLukjanov is now known as _SergeyLukjanov00:16
*** IlyaE has quit IRC00:19
*** markmcclain has joined #openstack-meeting00:19
*** novas0x2a|laptop has quit IRC00:21
*** matsuhashi has joined #openstack-meeting00:21
*** novas0x2a|laptop has joined #openstack-meeting00:21
*** thomasm has joined #openstack-meeting00:22
*** SergeyLukjanov has joined #openstack-meeting00:22
*** thomasm is now known as Guest3058000:22
*** SumitNaiksatam has quit IRC00:25
*** rakhmerov has joined #openstack-meeting00:25
*** sarob has joined #openstack-meeting00:26
*** SridarK has quit IRC00:27
*** Guest30580 has quit IRC00:27
*** HenryG_ has joined #openstack-meeting00:29
*** rakhmerov has quit IRC00:30
*** sarob has quit IRC00:31
*** HenryG has quit IRC00:31
*** zul has quit IRC00:34
*** MarkAtwood has left #openstack-meeting00:34
*** beagles has quit IRC00:35
*** beagles has joined #openstack-meeting00:35
*** yogeshmehra has quit IRC00:35
*** shakayumi has quit IRC00:36
*** arosen1 has quit IRC00:36
*** markpeek has joined #openstack-meeting00:37
*** jaypipes has quit IRC00:38
*** zhhuabj_home has quit IRC00:39
*** markmcclain has quit IRC00:39
*** sushils has quit IRC00:39
*** spzala has quit IRC00:40
*** jrodom has quit IRC00:41
*** SvenDowideit has joined #openstack-meeting00:41
*** oubiwann_ has joined #openstack-meeting00:42
*** shakayumi has joined #openstack-meeting00:42
*** reed has quit IRC00:43
*** reed has joined #openstack-meeting00:44
*** garyduan has joined #openstack-meeting00:45
*** tanisdl has quit IRC00:46
*** oubiwan__ has joined #openstack-meeting00:46
*** oubiwann_ has quit IRC00:46
*** sacharya has quit IRC00:48
*** pauli has quit IRC00:48
*** sacharya has joined #openstack-meeting00:48
*** zehicle has joined #openstack-meeting00:51
*** adalbas has quit IRC00:52
*** nosnos has joined #openstack-meeting00:52
*** nermina has quit IRC00:52
*** sarob has joined #openstack-meeting00:53
*** jrodom has joined #openstack-meeting00:53
zehicleOpenStack Core discussion starting in 5 minutes, hangout URL https://plus.google.com/hangouts/_/4661a0dc1ea9e2127f00a97cd86fe68d017aae46?authuser=0&hl=en00:55
*** oubiwan__ has quit IRC00:57
mikalI'll be there00:57
clarkbwill the discussion happen here or must we join the hangout? I am a little confused as to why both things are happening00:57
*** nati_ueno has quit IRC00:57
*** oubiwann_ has joined #openstack-meeting00:57
*** sarob has quit IRC00:57
*** zul has joined #openstack-meeting00:57
*** nermina has joined #openstack-meeting00:58
*** ujuc has joined #openstack-meeting00:58
mikalclarkb: I think its just that the URL needed to be announced00:59
mikalThe meetup itself is in hangouts00:59
clarkb:/00:59
*** radez_g0n3 is now known as radez01:01
zehicleI'd like to use the IRC for questions and discussion01:01
mikal#startmeeting OpenStack core meetup01:01
openstackMeeting started Tue Oct 22 01:01:58 2013 UTC and is due to finish in 60 minutes.  The chair is mikal. Information about MeetBot at http://wiki.debian.org/MeetBot.01:01
*** arosen1 has joined #openstack-meeting01:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:02
*** openstack changes topic to " (Meeting topic: OpenStack core meetup)"01:02
openstackThe meeting name has been set to 'openstack_core_meetup'01:02
clarkb++ to using irc for questions and discussion01:02
mikal#info The hangouts URL is https://plus.google.com/hangouts/_/4661a0dc1ea9e2127f00a97cd86fe68d017aae46?authuser=0&hl=en01:02
zehiclereference material http://robhirschfeld.com/2013/08/13/openstack-core-positions/01:03
mikalclarkb: I am not sure that's a battle I can win...01:03
mikalBut you can ask questions here if you want and I will try and relay to hangouts01:03
reedit's noisy in my room01:04
clarkbmikal: zehicle mentioned using IRC for questions and discussion01:04
clarkbin any case I will follow along best I can here01:05
*** markpeek has quit IRC01:05
*** ujuc_ has joined #openstack-meeting01:05
*** markpeek has joined #openstack-meeting01:05
*** ujuc has quit IRC01:06
mikalclarkb: fair enough01:06
*** zul has quit IRC01:06
*** yaguang has quit IRC01:08
mikalRob is jsut doing an intro at the moment01:08
*** haomaiwang has joined #openstack-meeting01:12
mikalQueued question: why do we need core at all? What do core projects get? What does it mean to be core?01:12
*** rkukura has left #openstack-meeting01:12
*** neelashah has joined #openstack-meeting01:16
*** mrodden has quit IRC01:16
clarkbI am curious about what "designated code frameworks" are and how they differ from the open reference implementations01:17
*** jamespage_ has joined #openstack-meeting01:17
lifelessclarkb: AIUI its a circuitous way of saying 'whats in the openstack/' git trees01:18
lifelessclarkb: but we should get clarification of that :)01:18
lifelessmikal: ^01:18
*** jamespage_ has quit IRC01:20
*** markwash has quit IRC01:23
*** sjing has joined #openstack-meeting01:24
*** dims has quit IRC01:26
*** SergeyLukjanov is now known as _SergeyLukjanov01:26
*** rakhmerov has joined #openstack-meeting01:26
*** HenryG_ has quit IRC01:26
*** _SergeyLukjanov has quit IRC01:27
*** rongze has joined #openstack-meeting01:28
mikalQueued question: how do we handle vendor patchsets on top of "designated code"?01:28
*** ItSANgo has quit IRC01:29
*** fnaval_ has joined #openstack-meeting01:29
*** danwent has quit IRC01:30
*** arosen1 has left #openstack-meeting01:30
mordredzehicle: I can't join the hangout - non-free software, laptop that needs to be secure for openstack-infra purposes ... BUT01:30
*** rakhmerov has quit IRC01:30
lifelessmordred: wintendo VM !01:30
mordredzehicle: I do still want clarification on the point you've got up in there about alternate implementations01:30
lifelessmordred: can you hear us?01:31
zehiclecan you hear?01:31
mordredzehicle: which I _believe_ you intend to be referring to the plugin architecture without saying plugin01:31
mordredI cannot01:31
mordredis there a dial-in number?01:31
lifelessmordred: how are you aware of whats being shown ?01:31
mordredI know zehicle's material :)01:31
clarkbfor the recent queued question why wouldn't vendor patchsets go through the normal code review process?01:31
mordredlifeless: and http://robhirschfeld.com/2013/08/13/openstack-core-positions/01:31
zehiclehttps://secure.join.me/876-719-30101:32
zehicletry this01:32
mordredzehicle: thanks!01:32
*** ryanpetrello_ has joined #openstack-meeting01:32
mordredzehicle: but it reads to me still like you're suggesting that someone can reimplement the API completely clean01:32
mordredths is in response to "Vendors may substitute alternate implementations"01:33
mordredother than that - I love it01:33
*** ryanpetrello has quit IRC01:33
*** ryanpetrello_ is now known as ryanpetrello01:33
*** IlyaE has joined #openstack-meeting01:37
mikalSo to summarize that tangent, "required code" would be somehting like the nova core code, and replacable bits are things like nova hypervisor drivers.01:37
mikalie. you might be required to run nova-api, nova-scheduler, etc, etc but with your choice of hypervisor01:37
*** rongze has quit IRC01:37
*** jrodom has quit IRC01:38
*** tomoe_ has joined #openstack-meeting01:38
*** esker has joined #openstack-meeting01:38
lifelessmikal: AIUI yes.01:38
*** SergeyLukjanov has joined #openstack-meeting01:38
lifelessmikal: but are you running nova-api if you patch it?01:38
mikalI think we dig into that later in the meeting, hence the queued question bit01:39
lifelessmikal: I know :)01:39
*** SergeyLukjanov has quit IRC01:39
*** haomaiwang has quit IRC01:39
mordredmy god. now I'm looking at your faces01:42
*** dims has joined #openstack-meeting01:43
*** mrodden has joined #openstack-meeting01:44
*** KC-Wang has quit IRC01:54
*** dims has quit IRC01:55
*** suo has joined #openstack-meeting01:57
*** sacharya has quit IRC01:58
clarkbbefore I forget, I think it is also worth mentioning that 6.B while noble doesn't seem enforceable01:58
*** novas0x2a|laptop has quit IRC01:59
zehiclethere's an expectation that the market will punish people02:00
*** beagles has quit IRC02:00
*** radsy has quit IRC02:01
*** stevemar has joined #openstack-meeting02:02
*** haomaiwang has joined #openstack-meeting02:06
*** 17WAAEJ0O has quit IRC02:06
*** twoputt has quit IRC02:07
zehicledesignated upsteam code02:12
*** asalkeld_lunch is now known as asalkeld02:14
*** radez is now known as radez_g0n302:16
*** btorresgil has joined #openstack-meeting02:17
*** stevemar has quit IRC02:22
reedI need to go in 3 min02:25
*** rongze has joined #openstack-meeting02:26
*** rakhmerov has joined #openstack-meeting02:26
*** sacharya has joined #openstack-meeting02:30
*** rakhmerov has quit IRC02:31
*** asalkeld has quit IRC02:32
*** asalkeld has joined #openstack-meeting02:37
*** asalkeld has left #openstack-meeting02:37
*** reed has quit IRC02:38
*** nermina has quit IRC02:44
*** SumitNaiksatam has joined #openstack-meeting02:46
*** rongze_ has joined #openstack-meeting02:47
*** sjing has quit IRC02:48
*** rongze has quit IRC02:49
*** suo has quit IRC02:50
*** suo has joined #openstack-meeting02:50
*** Shaan7 has quit IRC02:52
*** oubiwann_ has quit IRC03:02
*** colinmcnamara has joined #openstack-meeting03:02
*** markwash has joined #openstack-meeting03:07
*** colinmcnamara has quit IRC03:08
*** colinmcnamara has joined #openstack-meeting03:09
*** ujuc_ has quit IRC03:09
*** SvenDowideit has quit IRC03:12
*** SvenDowideit has joined #openstack-meeting03:13
*** colinmcnamara has quit IRC03:13
*** SvenDowideit has quit IRC03:16
*** SvenDowideit has joined #openstack-meeting03:16
*** stevemar has joined #openstack-meeting03:17
*** s1ko has joined #openstack-meeting03:21
*** ujuc has joined #openstack-meeting03:23
*** rakhmerov has joined #openstack-meeting03:27
*** rakhmerov has quit IRC03:32
*** esker has quit IRC03:45
*** rakhmerov has joined #openstack-meeting03:50
*** IlyaE has quit IRC03:50
zehicle#end03:50
*** comay has quit IRC03:51
*** asalkeld has joined #openstack-meeting03:52
*** jecarey has quit IRC03:53
*** comay has joined #openstack-meeting03:57
*** chandankumar has joined #openstack-meeting04:05
*** haomaiwang has quit IRC04:07
*** haomaiwang has joined #openstack-meeting04:08
*** ArxCruz has quit IRC04:10
mikal#endmeeting04:12
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"04:12
openstackMeeting ended Tue Oct 22 04:12:27 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:12
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_core_meetup/2013/openstack_core_meetup.2013-10-22-01.01.html04:12
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_core_meetup/2013/openstack_core_meetup.2013-10-22-01.01.txt04:12
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_core_meetup/2013/openstack_core_meetup.2013-10-22-01.01.log.html04:12
mikal(Sorry I forgot to do that before)04:12
*** haomaiwang has quit IRC04:12
*** IlyaE has joined #openstack-meeting04:14
*** sacharya has quit IRC04:16
*** neelashah has quit IRC04:19
*** sarob has joined #openstack-meeting04:22
*** akuznetsov has joined #openstack-meeting04:25
*** tomoe_ has quit IRC04:29
*** rongze_ has quit IRC04:31
*** rongze has joined #openstack-meeting04:32
*** doron_afk is now known as doron04:34
*** rongze has quit IRC04:37
*** sarob has quit IRC04:45
*** sarob has joined #openstack-meeting04:45
*** scott__ has quit IRC04:47
*** markpeek has quit IRC04:48
*** ArxCruz has joined #openstack-meeting04:49
*** sarob_ has joined #openstack-meeting04:50
*** sarob has quit IRC04:50
*** sarob_ has quit IRC04:51
*** sarob has joined #openstack-meeting04:51
*** sarob has quit IRC04:56
*** afazekas has quit IRC04:58
*** haomaiwang has joined #openstack-meeting05:01
*** matsuhashi has quit IRC05:01
*** matsuhashi has joined #openstack-meeting05:02
*** matsuhashi has quit IRC05:02
*** scott__ has joined #openstack-meeting05:02
*** matsuhashi has joined #openstack-meeting05:03
*** haomaiwang has quit IRC05:03
*** boris-42 has joined #openstack-meeting05:04
*** thomasbiege1 has joined #openstack-meeting05:04
*** Loquacity has quit IRC05:06
*** comay has quit IRC05:06
*** haomaiwang has joined #openstack-meeting05:11
*** dcramer_ has quit IRC05:11
*** afazekas has joined #openstack-meeting05:20
*** dcramer_ has joined #openstack-meeting05:24
*** vipul has quit IRC05:25
*** vipul has joined #openstack-meeting05:26
*** nadya has joined #openstack-meeting05:26
*** thomasbiege1 has quit IRC05:27
*** sushils has joined #openstack-meeting05:29
*** akuznetsov has quit IRC05:31
*** asalkeld has quit IRC05:33
*** asalkeld has joined #openstack-meeting05:33
*** s1ko has quit IRC05:34
*** matsuhashi has quit IRC05:35
*** akuznetsov has joined #openstack-meeting05:35
*** matsuhashi has joined #openstack-meeting05:36
*** matsuhashi has quit IRC05:36
*** matsuhashi has joined #openstack-meeting05:37
*** thomasbiege1 has joined #openstack-meeting05:37
*** haomaiwang has quit IRC05:39
*** haomaiwa_ has joined #openstack-meeting05:39
*** ryanpetrello has quit IRC05:40
*** jtomasek has joined #openstack-meeting05:41
*** thomasbiege1 has quit IRC05:46
*** yogeshmehra has joined #openstack-meeting05:46
*** reed has joined #openstack-meeting05:49
*** nadya has quit IRC05:50
*** btorresgil has quit IRC05:51
*** akuznetsov has quit IRC05:52
*** jtomasek has quit IRC05:56
*** mrunge has joined #openstack-meeting05:56
*** Loquacity has joined #openstack-meeting05:57
*** doron is now known as doron_afk05:57
*** haomaiwang has joined #openstack-meeting05:57
*** haomaiwa_ has quit IRC06:00
*** vipul is now known as vipul-away06:00
*** sarob has joined #openstack-meeting06:02
*** yogeshmehra has quit IRC06:04
*** vipul-away is now known as vipul06:05
*** sarob has quit IRC06:07
*** anniec has quit IRC06:08
*** thomasbiege1 has joined #openstack-meeting06:11
*** markwash has quit IRC06:12
*** bmelande_ has quit IRC06:13
*** akuznetsov has joined #openstack-meeting06:14
*** yamahata has quit IRC06:15
*** ujuc has quit IRC06:15
*** yogeshmehra has joined #openstack-meeting06:16
*** sushils has quit IRC06:16
*** haomaiwa_ has joined #openstack-meeting06:17
*** markwash has joined #openstack-meeting06:18
*** haomaiwang has quit IRC06:21
*** SergeyLukjanov has joined #openstack-meeting06:21
*** yamahata has joined #openstack-meeting06:22
*** anniec has joined #openstack-meeting06:23
*** jcoufal has joined #openstack-meeting06:25
*** eglynn has joined #openstack-meeting06:29
*** anniec_ has joined #openstack-meeting06:30
*** egallen has joined #openstack-meeting06:31
*** anniec has quit IRC06:32
*** anniec_ is now known as anniec06:32
*** eglynn has quit IRC06:35
*** amotoki has joined #openstack-meeting06:36
*** boris-42 has quit IRC06:38
*** markwash has quit IRC06:40
*** amotoki has quit IRC06:42
*** doron_afk has quit IRC06:44
*** akuznetsov has quit IRC06:48
*** haomaiwang has joined #openstack-meeting06:48
*** jlibosva has joined #openstack-meeting06:48
*** ttrifonov_zZzz is now known as ttrifonov06:49
*** imsurit has joined #openstack-meeting06:49
*** haomaiwa_ has quit IRC06:52
*** yamahata has quit IRC06:53
*** kpepple has quit IRC06:57
*** IlyaE has quit IRC06:58
*** rongze has joined #openstack-meeting06:58
*** kpepple has joined #openstack-meeting06:58
*** rongze has quit IRC06:58
*** suo has quit IRC06:58
*** tnurlygayanov has quit IRC06:59
*** rongze has joined #openstack-meeting06:59
*** rongze has quit IRC06:59
*** rongze has joined #openstack-meeting06:59
*** imsurit has quit IRC07:06
*** cdub_ has quit IRC07:06
*** belmoreira has joined #openstack-meeting07:08
*** stevemar has quit IRC07:15
*** MadOwl has quit IRC07:16
*** sjing has joined #openstack-meeting07:21
*** ociuhandu has joined #openstack-meeting07:22
*** belmoreira has quit IRC07:26
*** belmoreira has joined #openstack-meeting07:26
*** shardy_afk is now known as shardy07:27
*** jtomasek has joined #openstack-meeting07:30
*** anniec has left #openstack-meeting07:36
*** SergeyLukjanov is now known as _SergeyLukjanov07:37
*** bgorski has joined #openstack-meeting07:37
*** _SergeyLukjanov has quit IRC07:37
*** davidhadas has quit IRC07:40
*** doron_afk has joined #openstack-meeting07:45
*** SergeyLukjanov has joined #openstack-meeting07:46
*** katyafervent has quit IRC07:46
*** sushils has joined #openstack-meeting07:49
*** haomaiwang has quit IRC07:54
*** SergeyLukjanov is now known as _SergeyLukjanov07:55
*** yogeshmehra has quit IRC07:57
*** Fdot has joined #openstack-meeting07:58
*** Mandell has quit IRC07:59
*** Mandell has joined #openstack-meeting07:59
*** boris-42 has joined #openstack-meeting08:01
*** eglynn has joined #openstack-meeting08:03
*** SergeyLukjanov has joined #openstack-meeting08:03
*** Mandell has quit IRC08:04
*** doron_afk is now known as doron08:08
*** SergeyLukjanov has quit IRC08:10
*** SergeyLukjanov_ has joined #openstack-meeting08:10
*** yassine has joined #openstack-meeting08:11
*** alexpilotti has joined #openstack-meeting08:18
*** fbo_away is now known as fbo08:19
*** yamahata has joined #openstack-meeting08:22
*** cdub_ has joined #openstack-meeting08:22
*** rongze has quit IRC08:25
*** inkerra has quit IRC08:26
*** derekh has joined #openstack-meeting08:26
*** SergeyLukjanov_ has quit IRC08:28
*** rongze has joined #openstack-meeting08:29
*** enikanorov_ has joined #openstack-meeting08:31
*** SergeyLukjanov has joined #openstack-meeting08:33
*** SergeyLukjanov has quit IRC08:35
*** sergmelikyan has quit IRC08:37
*** sjing has quit IRC08:38
*** davidhadas has joined #openstack-meeting08:43
*** thomasbiege1 has quit IRC08:47
*** terriyu has quit IRC08:50
*** terriyu has joined #openstack-meeting08:51
*** thomasbiege1 has joined #openstack-meeting08:52
*** thomasbiege1 has quit IRC08:58
*** jhenner has joined #openstack-meeting09:01
*** thomasbiege1 has joined #openstack-meeting09:02
*** Fdot_ has joined #openstack-meeting09:02
*** Fdot has quit IRC09:05
*** doron is now known as doron_afk09:08
*** yamahata has quit IRC09:08
*** reed has quit IRC09:11
*** enikanorov_ has quit IRC09:12
*** marun_ has joined #openstack-meeting09:13
*** beagles has joined #openstack-meeting09:14
*** marun has quit IRC09:14
*** marun_ is now known as marun09:14
*** thomasbiege1 has quit IRC09:20
*** cdub_ has quit IRC09:27
*** cdub_ has joined #openstack-meeting09:28
*** doron_afk is now known as doron09:29
*** haomaiwang has joined #openstack-meeting09:33
*** akuznetsov has joined #openstack-meeting09:33
*** thomasbiege has joined #openstack-meeting09:34
*** suo has joined #openstack-meeting09:36
*** cdub_ has quit IRC09:38
*** ociuhandu has quit IRC09:44
*** haomaiwang has quit IRC09:44
*** egallen has quit IRC09:46
*** cdub_ has joined #openstack-meeting09:47
*** egallen has joined #openstack-meeting09:48
*** doron is now known as doron_afk09:51
*** radez_g0n3 is now known as radez10:00
*** egallen has quit IRC10:02
*** ccorrigan has quit IRC10:06
*** ccorrigan has joined #openstack-meeting10:07
*** thomasbiege has quit IRC10:11
*** thomasbiege has joined #openstack-meeting10:13
*** doron_afk has quit IRC10:17
*** thomasbiege has quit IRC10:18
*** yamahata has joined #openstack-meeting10:19
*** adalbas has joined #openstack-meeting10:24
*** ociuhandu has joined #openstack-meeting10:25
*** slong has joined #openstack-meeting10:26
*** slong has quit IRC10:28
*** ociuhandu has quit IRC10:32
*** yamahata has quit IRC10:39
*** fallenpegasus has joined #openstack-meeting10:42
*** doron_afk has joined #openstack-meeting10:50
*** yamahata has joined #openstack-meeting10:51
*** fallenpegasus has quit IRC10:51
*** cdub_ has quit IRC10:53
*** MadOwl has joined #openstack-meeting10:54
*** rongze has quit IRC10:54
*** rongze has joined #openstack-meeting10:55
*** doron_afk has quit IRC10:57
*** yamahata has quit IRC10:58
*** rongze has quit IRC10:59
*** haomaiwang has joined #openstack-meeting11:00
*** dims has joined #openstack-meeting11:00
*** ItSANgo_ has joined #openstack-meeting11:02
*** jcoufal has quit IRC11:04
*** radez is now known as radez_g0n311:14
*** davidhadas_ has joined #openstack-meeting11:20
*** sjing has joined #openstack-meeting11:21
*** egallen has joined #openstack-meeting11:22
*** mrunge has quit IRC11:26
*** thomasbiege has joined #openstack-meeting11:37
*** rakhmerov has quit IRC11:44
*** toan-tran has joined #openstack-meeting11:49
*** ygbo has joined #openstack-meeting11:50
*** yamahata has joined #openstack-meeting11:51
*** pcm_ has joined #openstack-meeting11:51
*** HenryG has joined #openstack-meeting11:52
*** thomasbiege has quit IRC11:56
*** thomasbiege has joined #openstack-meeting11:58
*** Kharec has quit IRC11:58
*** jcoufal has joined #openstack-meeting12:00
*** dkranz has joined #openstack-meeting12:01
*** jhenner1 has joined #openstack-meeting12:03
*** pdmars has joined #openstack-meeting12:03
*** jhenner has quit IRC12:03
*** afazekas has quit IRC12:05
*** Kharec has joined #openstack-meeting12:08
*** ygbo has quit IRC12:13
*** yamahata has quit IRC12:13
*** galstrom_zzz is now known as galstrom12:13
*** galstrom is now known as galstrom_zzz12:14
*** sarob has joined #openstack-meeting12:18
*** weshay has joined #openstack-meeting12:19
*** dcramer_ has quit IRC12:19
*** afazekas has joined #openstack-meeting12:21
*** sarob has quit IRC12:25
*** sarob has joined #openstack-meeting12:26
*** nosnos has quit IRC12:27
*** nosnos has joined #openstack-meeting12:28
*** haomaiwa_ has joined #openstack-meeting12:28
*** thomasm has joined #openstack-meeting12:30
*** thomasm is now known as Guest7048212:30
*** sarob has quit IRC12:30
*** rakhmerov has joined #openstack-meeting12:31
*** haomaiwang has quit IRC12:31
*** nosnos has quit IRC12:32
*** colinmcnamara has joined #openstack-meeting12:33
*** rongze has joined #openstack-meeting12:35
*** colinmcnamara has quit IRC12:35
*** doron_afk has joined #openstack-meeting12:35
*** colinmcnamara has joined #openstack-meeting12:36
*** marekd|away is now known as marekd12:40
*** colinmcnamara has quit IRC12:40
*** anteaya has joined #openstack-meeting12:40
*** bpokorny has quit IRC12:42
*** zhhuabj_home has joined #openstack-meeting12:49
*** NickChase has joined #openstack-meeting12:49
*** ayoung has quit IRC12:51
*** lblanchard has joined #openstack-meeting12:53
*** AJaeger has joined #openstack-meeting12:55
*** kevinconway has quit IRC12:56
*** dianefleming has joined #openstack-meeting12:57
*** dianefleming has left #openstack-meeting12:57
*** dianefleming has joined #openstack-meeting12:57
*** topol has joined #openstack-meeting12:58
*** thomasbiege has quit IRC12:58
*** DennyZhang has joined #openstack-meeting12:59
dianefleminggood morning!12:59
*** afazekas has quit IRC12:59
AJaegerGood morning!12:59
*** dguitarbite has joined #openstack-meeting12:59
annegentleOk moving over here!12:59
annegentleIt's my birthday! Yay!13:00
dianeflemingwhere the cool kids are13:00
annegentle:) dianefleming13:00
dianeflemingHAPPY BIRTHDAY ANNE13:00
dianeflemingyou don't look a day over 3213:00
* AJaeger sings Happy Birthday, dear Anne, happy Birthday to you...13:00
annegentlethat's right! I'm going to leave it as, I'm a child of the 80s :)13:00
annegentleThanks AJaeger13:00
annegentleOk, let's kick this meeting off13:01
annegentle#startmeeting docteammeeting13:01
openstackMeeting started Tue Oct 22 13:01:15 2013 UTC and is due to finish in 60 minutes.  The chair is annegentle. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: docteammeeting)"13:01
openstackThe meeting name has been set to 'docteammeeting'13:01
annegentleThe agenda is at http://wiki.openstack.org/Meetings/DocTeamMeeting, feel free to add to it.13:01
*** suo has quit IRC13:01
annegentleMost of you know this, We use "MeetBot" for IRC meeting note-taking, see http://meetbot.debian.net/Manual.html for a reference for the different hashtags used.13:01
EmilienMhello :) and happy birthday Anne !! (joyeux anniversaire in french)13:01
NickChaseHey, happy birtheday, Anne!13:02
annegentle#link https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting13:02
annegentleThanks NickChase and EmilienM!13:02
chandankumarannegentle, Happy Birthday ANNE. :)13:02
dguitarbitehappy b'day ANNE13:02
annegentle:)13:02
*** dkranz has quit IRC13:02
*** DandyPandy has joined #openstack-meeting13:02
annegentleSo I think all the Actions should be easy to run through.13:02
annegentleACTION: shaunm_ testing nova-network on Fedora, DONE13:02
annegentleAt least I think so. Shaun's not here13:03
annegentleACTION: AnneGentle to email the openstack list asking for help, DONE -- got a good response too!13:03
annegentleAnd that was it for actions13:03
annegentleNext up13:04
annegentle#topic Bug report, DocImpact state13:04
*** openstack changes topic to "Bug report, DocImpact state (Meeting topic: docteammeeting)"13:04
*** dprince has joined #openstack-meeting13:04
annegentleSo, I think that dianefleming has been moving havana bugs to icehouse when they apply to icehouse, like v3 Compute API13:04
dianeflemingyes13:04
annegentleThere are a lot of bugs and comments for the install guide, which are havana.13:05
*** kevinconway has joined #openstack-meeting13:05
annegentle#link https://bugs.launchpad.net/openstack-manuals/+milestone/havana13:05
*** bpokorny has joined #openstack-meeting13:05
annegentleBut I don't think our havana numbers will go down noticeably until say XenAPI gets revisions, that kind of grouping is what I'm seeing.13:05
dianeflemingi can  take on moving all the bugs if you want (havana bugs) and noting to backport to havana13:05
AJaegerShould we discuss the Install Guide as extra topic?13:05
annegentledianefleming: I think what the code projects do is move them wholesale through the Launchpad API, but I don't yet know exact details13:06
*** DandyPandy has left #openstack-meeting13:06
annegentledianefleming: so we might save you some clicks if we can figure out the API way?13:06
dianeflemingawesome!13:06
annegentleAJaeger: yes let's have the install guide as another topic13:06
*** jhenner1 has quit IRC13:06
* AJaeger adds it to AGenda13:06
*** jhenner has joined #openstack-meeting13:06
annegentleI also think there are keystone doc bugs and vmware doc bugs13:07
annegentleI sense that there are big groups of doc bugs13:07
annegentleJust noting that, not saying we have to take a specific action13:07
annegentleAJaeger: perfect, thanks13:07
*** neelashah has joined #openstack-meeting13:08
annegentleThere are definitely doc bugs that could be easily picked up, triaged, and might already be fixed, such as Nova CLI has new IP parameter, neutron-debug is not documented, Add swift_store_ssl_compression param, those all seem fixable13:08
annegentleSo my note on the bug report is to keep fixing doc bugs :)13:08
*** fnaval_ has quit IRC13:09
annegentleAnd, I've been entering doc bugs for the install guide when comments indicate a doc bug13:09
annegentleAnything else on doc bugs?13:09
annegentleOk, next topic13:09
*** fnaval_ has joined #openstack-meeting13:09
* annegentle hits refresh13:09
annegentle#topic Install Guide13:09
*** openstack changes topic to "Install Guide (Meeting topic: docteammeeting)"13:09
annegentleAJaeger: just saw your new bug from your QA input, that's good to get, want to discuss?13:10
annegentle#link https://bugs.launchpad.net/openstack-manuals/+bug/124313113:10
uvirtbotLaunchpad bug 1243131 in openstack-manuals "Comments on Neutron" [High,New]13:10
*** ItSANgo_ has quit IRC13:10
AJaegerJust an info: I have one of our QA guys going through the document - and sending me emails with things that are wrong...13:10
annegentleAJaeger: that's great.13:11
*** ociuhandu has joined #openstack-meeting13:11
AJaegerI see a lot of patches for the Install Guide and would ask to review these quickly to avoid conflicts13:11
annegentleThe comments have been very useful too13:11
annegentleAs is the doc bug link13:12
NickChasethey seem like pretty straightforward corrections.13:12
AJaegerShould we mark these patches in a special way?13:12
NickChasevery helpful13:12
annegentleNickChase: yeah some markup stuff, some duplications13:12
AJaegerThe doc bug link is GREAT!13:12
*** dguitarbite has quit IRC13:12
annegentleAJaeger: Just with backport: stable/havana13:12
annegentleAJaeger: yes!13:12
AJaegerI meant something like say "Install Guide" in the commit header...13:12
NickChaseLOVE that you get the source file where the problem is13:12
annegentleAJaeger: yes I agree on reviewing install guide patches quickly, and backporting as soon as they merge13:12
*** dguitarbite has joined #openstack-meeting13:12
annegentleAJaeger: oh that would be good, sorry I hadn't used that the last few patche13:13
annegentlepatches13:13
* AJaeger didn't use it either13:13
annegentle#agreed Use Install Guide in the commit header when patching the Install Guide so that reviewers can make those patches a priority13:13
*** nermina has joined #openstack-meeting13:13
annegentleAnyone else have input on install guides? I wish Shaun was online13:14
*** fnaval_ has quit IRC13:14
annegentleI don't know when his contract is up13:14
nerminahello all13:14
annegentleDoes anyone else want to be a moderator on install guide comments? For Ubuntu it's me, EmilienM, Tom, and Lorin I think.13:14
annegentlehi nermina!13:14
nerminasorry, two different school dropoffs13:15
*** doron_afk has quit IRC13:15
*** jhenner has quit IRC13:15
*** jhenner1 has joined #openstack-meeting13:15
annegentleI'm a little irritated with Disqus for forcing loging to see the feed of comments on a particular guide13:15
annegentleI hope to replace Disqus with ask.openstack.org Real Soon Now.13:15
dianeflemingyes!13:15
annegentleloging should be logging in13:15
dianeflemingwhat's the blocker from doing it asap?13:15
AJaegerwith the bug links, we could also remove everything...13:16
*** sgordon has joined #openstack-meeting13:16
*** esker has joined #openstack-meeting13:17
annegentlesorry just got interrupted in person :)13:18
NickChaseHow dare they. :)13:18
annegentledianefleming: it's really just getting that redesign done, from Todd Morey13:19
dianeflemingok!13:19
koolhead17hi all13:19
annegentleI've got a blueprint now for the redesign: https://blueprints.launchpad.net/openstack-manuals/+spec/redesign-docs-site13:19
annegentlehey koolhead1713:20
koolhead17EmilienM: thanks for the tip. birthday wishes annegentle13:20
annegentleand I've asked Todd if he can have a demo ready by the summit13:20
annegentlekoolhead17: hee hee thanks!13:20
koolhead17annegentle: awesome!!13:20
annegentlekoolhead17: yes I have high hopes, Todd is incredible13:20
*** ben_duyujie has joined #openstack-meeting13:21
annegentleOk, I definitely want to emphasize speedy attention on the install guide bug reports13:21
annegentleLet's move the agenda around a bit to give sarob a chance to join in13:21
annegentle#topic Backports13:21
*** openstack changes topic to "Backports (Meeting topic: docteammeeting)"13:21
*** dvarga has joined #openstack-meeting13:22
AJaegerI put this on the agenda since dianefleming did a great rework of one my backports.13:22
annegentleWe have a nice addition/explanation for backports on the wiki now13:22
annegentleAJaeger: oh nice!13:22
AJaegerI'm under the impression that backports should be cherry-picks (plus resolving conflicts) only13:22
*** ozstacker has quit IRC13:22
dianeflemingphew! glad it was ok @AJaeger13:22
annegentle#link https://wiki.openstack.org/wiki/Documentation/HowTo#Git_commit_messages_and_backports13:22
AJaegerSo, I split out dianefleming'S patch into a separate patch.13:22
dianeflemingthanks!13:22
annegentleAJaeger: yeah, that makes sense to me as a reviewer, otherwise the merging might get too hard13:23
AJaegerdianefleming, text was great - but not as part of the backport13:23
*** afazekas has joined #openstack-meeting13:23
dianeflemingyeah, I didn't notice it was a backport until i was in too deep - sorry about that13:23
*** julim has joined #openstack-meeting13:23
AJaegerdianefleming, easy to solve, still we have to be carefull13:23
annegentledianefleming: heh :)13:23
*** anniec has joined #openstack-meeting13:23
annegentledianefleming: no worries13:23
AJaegerDo we need the usual 2 approvals for simple backports?13:24
dianeflemingi wish there was a way to auto-backport - seems like we do too much work on those13:24
AJaegerOr do we want to do them quicker?13:24
dguitarbitecherry picks +1 easier to avoid accidents13:24
annegentleAJaeger: no, I think we should make it a policy that if the backport merged into master, only one core needs to review it for backport13:24
chandankumardianefleming, actually how backporting is done, so that i cna help.13:25
chandankumar*can13:25
annegentleAJaeger: we're a little different from other projects in that we don't have a stable team13:25
annegentlededicated stable team13:25
annegentleso I think core is our dedicated stable team and we can make fast merges13:25
AJaegerchandankumar, see the link above by annegentle13:25
*** blamar has joined #openstack-meeting13:25
AJaegerSo, if I propose a backport, somebody else give the +2/approval?13:26
annegentleThere is a blueprint for automating backports: https://blueprints.launchpad.net/openstack-manuals/+spec/attempt-backport-by-commit-message13:26
annegentleAJaeger: yes that seems safe and sane to me, anyone else think that's crazy?13:26
dianeflemingsounds good to me - the +2 approval on backports13:26
dguitarbiteannegentle: safer and easier for newbies/non-git-gerrit geeks13:26
annegentleI think backports fade out over time, but yeah, we do a LOT of them especially on install guide13:27
NickChaseI'm all for the automated backport13:27
AJaegerIt'S only install guide and config reference - and Install Guide needs a bit more testing and fixing13:27
annegentleNickChase: I'm just not convinced it can ever be automated, those have rebase conflicts all the time13:27
annegentleAJaeger: yeah true that13:27
*** anniec_ has joined #openstack-meeting13:27
AJaegerright now I'm checking that patches get proposed for the guides and propose some myself to avoid conflicts13:28
*** anniec has quit IRC13:28
*** anniec_ is now known as anniec13:28
NickChaseannegentle:  I'm not a git expert, but seems to me that if it works it'd be helpful, but for those cases where it doesn't we haven't lost anything.13:28
annegentleNickChase: yeah true13:28
annegentleOk still no sarob but we can start talking about rst to xml so nermina has an idea of where they are13:28
NickChaseplus there are people (like myself, admittedly) who just don't know how to do it, but we CAN mark whether it should be done13:29
annegentleNickChase: yep, and that helps too13:29
dianeflemingautomation would save a lot of time - even if we have to manually merge13:29
annegentle#topic devref rst to xml conversion13:29
*** openstack changes topic to "devref rst to xml conversion (Meeting topic: docteammeeting)"13:29
NickChaseand it forces people to think about whether a patch should be backported; I suspect there are  lots of changes that should have gone back to grizzly but didn't because people just didn't htink of it13:29
*** ItSANgo_ has joined #openstack-meeting13:29
annegentleNickChase: you know, that's true too13:29
annegentledianefleming: yeah automating some steps helps13:29
annegentleis that even grammatically correct? Anywho13:30
annegentleWe can talk more about automation!13:30
AJaegerNickChase, That's why we demand the "backport: havana" or "backport: none" now for all changes that target guides that we do separately for havana13:30
annegentleSo we had several concerns with their original patch13:30
annegentleoh maybe I should back up even further13:30
AJaegerAt least it's now a concise decision and not neglect13:30
annegentleThe goal for the training manuals is to reuse all they can to reorganize the content into training guides13:30
dguitarbiteare you guys working on rst to xml? I believe that sarob is working on it as of now13:30
nerminawas that the original patch you sent me, annegentle13:31
nermina?13:31
*** shaunm has joined #openstack-meeting13:31
AJaegerannegentle, I agree with your proposal moving forward.13:31
chandankumarannegentle, we can do rst to xml conversion by using rst2xml package provided by docutils.13:31
annegentlenermina: the patch I sent was their attempt at automation manually, bringing in content they felt was missing13:31
AJaegerThe question to me is whether we should ask the projects like nova to remove patches and point to the documentation that we write?13:31
annegentlechandankumar: yes that's their patch13:31
annegentle#link http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/training-guide13:31
nerminathat's what i thought, annegentle13:32
*** stevemar has joined #openstack-meeting13:32
annegentleThe training manuals have four personas in mind: associate, operator, developer, architect13:32
*** yamahata has joined #openstack-meeting13:32
nerminaok13:32
*** Fdot_ has quit IRC13:32
annegentle#link https://review.openstack.org/#/c/50509/13:32
shaunmannegentle: are there write-ups of those personas yet?13:32
*** Shaan7 has joined #openstack-meeting13:33
dguitarbitesarob is working on it, here is the link for it : https://github.com/sarob/openstack-sarob13:33
nerminaannegentle, is the audience documented somewhere?13:33
annegentleshaunm: I'm looking13:33
dguitarbiteaudience in d sense for the associate, operator .. ??13:34
annegentleOk, so if you look at "what does this book intend to teach" like http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/training-guide/bk004-ch001-architect-what-does-this-book-intend-to-teach.xml13:34
annegentleyou see the idea behind their guide13:34
annegentlealso13:35
annegentle#link https://blueprints.launchpad.net/openstack-manuals/+spec/training-manuals13:35
*** Ska_ has joined #openstack-meeting13:35
dguitarbiteheras of now its there on the wiki https://wiki.openstack.org/wiki/Training-manuals13:35
annegentle#link https://wiki.openstack.org/wiki/Training-manuals13:35
dguitarbiteits a tricky thing to get it sorted13:35
annegentleThe idea from our perspective (docs) is that we'd offer them guidance, avoidance of pitfalls, a process and tools13:35
annegentleSort of like incubation within the Docs program, until they can have their own program13:35
dguitarbitewe are working on the official version for the intended audience13:35
annegentledguitarbite: my understanding is that Associates is the first course13:36
nerminathanks, dguitarbite13:36
dguitarbitenps13:36
annegentledguitarbite: and not devs yet13:36
*** Shaan7 has quit IRC13:36
*** Shaan7 has joined #openstack-meeting13:36
dguitarbiteyes13:36
annegentlenermina: but apparently they discovered missing info and wanted to bring it in from dev guides13:37
nerminaright13:37
dguitarbiteannegntle: associate is the first one, we plan to get the alpha version out before end of this year13:37
annegentleso my suggestion is that the info that's missing should find a place in openstack-manuals13:37
annegentlenermina: I think it's great if you can help them, because it'll make the docs better13:37
nerminaannegentle, could i get a week to analyze this and come up with some recommendations?13:37
annegentleAJaeger: I'm glad you can double-check my sanity, thanks13:38
annegentlenermina: absolutely fine by me, and if dguitarbite knows their timeline, then it sounds like a week is good13:38
AJaegercan we somehow sync on a common set of persons between training and doc?13:38
nerminaannegentle, i'll match it up against the guides13:38
annegentleAJaeger: htinking13:38
annegentleAJaeger: so, the user committee has personas, to me those match more with docs13:38
nerminaand see how they can be interlinked, annegentle13:38
annegentleAJaeger: training is more about "what job can I get after completing this"13:39
annegentlenermina: yes... pondering13:39
*** burt has joined #openstack-meeting13:39
AJaegerI see13:39
nerminawe could do a blueprint, annegentle13:39
annegentleI'm not sure I'd make a 1:1 match, honestly, because of the "jobs jobs" focus of training13:39
dguitarbiteAJaeger: Training will also have quizes, PPT generators etc. etc. which you would not prefer to keep in the manuals13:39
*** yamahata has quit IRC13:40
nerminano, i meant to see how they can relate, annegentle13:40
nerminasynchronize, if you will13:40
AJaegerdguitarbite, I agree - but the more we align our goals, the easier we can share.13:40
annegentlenermina: well, I made Sean do a blueprint for automation, and his training manuals, so I don't know if another blueprint is necessary, but it would certainly help if you can study their blueprint13:40
annegentlenermina: and perhaps update their blueprint13:40
*** markpeek has joined #openstack-meeting13:41
*** yamahata has joined #openstack-meeting13:41
annegentlenermina: for exapmle, their Book structure section13:41
nerminaannegentle, no problem, that sounds good13:41
annegentlenermina: ok, excellent13:41
dguitarbiteAJaeger: I have proposed this to sean for reusing the training manuals, thats the reason we spent time on xpath ... the basic goal is to reuse as much openstack-manuals as possible13:41
annegentleAJaeger: yeah I agree with goal alignment to a point, but if the goal is to let them eventually run their own program, do we all align with the user committee personas as an overarching organizer?13:42
annegentleAJaeger: and that might just be an academic question more than pragmatic, not sure yet13:42
nerminaannegentle, ajaeger, i think their set is more specific and defined within practices13:42
AJaegerannegentle, as far as it makes sense. If we can agree on three out of four it would be better than on none. Might indeed be academic...13:42
*** thomasbiege has joined #openstack-meeting13:43
AJaegernermina, in that case let's move on and ignore me ;)13:43
annegentleHee13:43
annegentleIt's ideal to collaborate and understand each other as much as possible!13:43
nerminai agree annegentle13:43
nerminai see your point too ajaeger13:43
annegentledguitarbite: I really don't want to slow your progress, and I do think all the docs will be better after this analysis13:44
*** lbragstad has joined #openstack-meeting13:44
nerminai feel like the training team is closer to the user community13:44
nerminaand they know their needs13:44
annegentlenermina: yes, I think so too, they are doing working sessions at user groups, which is really cool13:44
dguitarbiteannegentle: agree13:45
*** dkranz has joined #openstack-meeting13:45
annegentleOk, I think that's it for topics, how about open discussion13:45
*** jecarey has joined #openstack-meeting13:45
annegentle#Open discussion13:45
annegentleI finally got the sitemap.xml ready, thanks to dwcramer for the help with the XSLT13:45
NickChaseDid you want to talk about the licensing thing?13:46
annegentleThis is the first release I couldn't do it all manually13:46
annegentleNickChase: yes!13:46
nerminahappy birthday, annegentle!13:46
annegentlenermina: thanks!13:46
NickChaseannegentle: cool on the sitemap.xml13:46
dianefleming@annegentle - two topics - 1) automation of command ref and 2) removal of API references and introduction of API guide13:46
annegentledianefleming: sure13:46
*** fnaval_ has joined #openstack-meeting13:46
NickChaseso regarding the licensing, we have the doc from the lawyer13:46
*** afazekas has quit IRC13:47
annegentleOk NickChase first13:47
NickChase(sorry, didn't mean to jump in and be rude!)13:47
dianeflemingI wrote a blueprint on 2) but I need to write a blueprint on 1) - my main question is, who needs to review/approve the blueprints?13:47
*** sacharya has joined #openstack-meeting13:47
NickChasethe trouble is that the license for the docs is specified in the CLA13:48
NickChaseso if we are going to change the license, we need a way for people to acknowledge that change.  basically...13:48
NickChasewe have to get their agreement that changes they submit are now under this new license.13:48
NickChaseFor a small team, that's not a big deal; we could conceivably do it manually13:48
NickChasebut if we change the CLA, that's a big, big deal.13:49
*** ayoung has joined #openstack-meeting13:49
NickChaseAlso, we need to define "attribution" and what we want people to do with our books if they reuse them (ie, keep attribution, remove it, etc.)13:49
NickChaseSo those are the basic issues.  Do we need to actually DO anything or are we going to let the board just make some decisions and THEN talk about it?13:50
annegentleNickChase: we're going to let the board churn on it :)13:51
*** zehicle has quit IRC13:51
annegentleNickChase: that's a great report, thanks for the leg work!13:51
NickChaseannegentle: sounds like a plan. :)13:51
NickChasemy pleasure13:51
annegentleOk, dianefleming you're up13:51
dianeflemingok!13:51
dianeflemingfor the command ref automation (actually command ref content in the user guides), i need to write a blueprint - who needs to review/approve it?13:52
annegentledianefleming: I found this: https://pypi.python.org/pypi/sphinxcontrib-programoutput13:52
dianeflemingfor the api refs removal and addition of the api guide, can I assume that's approved or do I need to pass that by dev?13:52
annegentledianefleming: it's implementation detail, but found it does mean a change to requirements.txt, which would have to go through ci core approval I believe13:53
annegentledianefleming: so, for automation of command ref output, it might be a blueprint within ci? I dont' mind it being in openstack-manuals though13:53
*** sarob has joined #openstack-meeting13:53
dianeflemingok13:53
sarobSarob here13:53
dianeflemingi can put command ref blueprint in ci13:53
annegentlehey sarob!13:53
dianefleminghi sarob13:53
NickChasehi sarob13:54
sarobSorry late13:54
sarobJust hit sfo13:54
annegentledianefleming: I can give you more details after the meeting about requirements.txt13:54
annegentlewelcome sarob13:54
sarobThx13:54
*** dims has quit IRC13:54
dianeflemingthanks - i'll be in the office around 11am13:54
nerminahi sarob13:54
annegentlesarob: you'll see the discussion in the notes, but the gist of it is nermina is going to take this week to analyze the content13:54
dguitarbitehi saob13:54
dguitarbite*sarob13:55
dianeflemingas for api ref/api guide, it means removing the repos for the api refs, which would impact dev - right?13:55
annegentledianefleming: cool13:55
dianeflemingso they should approve/reject that blueprint?13:55
annegentledianefleming: yeah that part is really tough to say how the individual projects would react13:55
annegentledianefleming: it's nearly a TC level question, since it affects all projects13:55
annegentledianefleming: I'm averse to removing them, honestly13:55
dianeflemingokay, i'll talk to you about that when I come into office13:55
annegentledianefleming: ok13:55
*** dguitarbite has quit IRC13:55
dianefleminghmmm - let's talk13:55
sarobI late but13:56
*** dguitarbite has joined #openstack-meeting13:56
annegentledianefleming: not sure if it's just because I created them due to some conflict coming out among core members of nova13:56
*** enikanorov has quit IRC13:56
sarobCan we move the devref project rst as well then?13:56
*** enikanorov has joined #openstack-meeting13:56
*** IlyaE has joined #openstack-meeting13:56
*** dcramer_ has joined #openstack-meeting13:56
sarobOr discuss with TC at the same time?13:56
*** sacharya has quit IRC13:57
sarobCause doing one page move at a time is going to kill our project13:57
*** radez_g0n3 is now known as radez13:58
annegentlesarob: pretty sure we're not trying to kill your project :)13:58
sarobNope I don't think that13:58
annegentlesarob: it's not one page at a time, it's looking at your larger outline and ensuring the pieces fit13:58
annegentlesarob: is this all content needed for associates?13:58
*** jhenner has joined #openstack-meeting13:59
*** thomasbiege has quit IRC13:59
annegentlesarob: we also talked about persona alignment13:59
sarobMany pages yeas13:59
*** sandywalsh has joined #openstack-meeting13:59
*** thomasbiege has joined #openstack-meeting13:59
*** thedodd has joined #openstack-meeting14:00
annegentlesarob: I think nermina will have a good handle on 4-5 patches (just guessing) that will need to come in14:00
*** jhenner has quit IRC14:00
sarobIt is more straightforward to mass convert while still developing the documentation14:00
sarobAnd flow14:00
nerminasarob, i'll see how the content is organized and how it can communicate with the user guides14:00
*** markvan has joined #openstack-meeting14:01
*** noslzzp has joined #openstack-meeting14:01
annegentlesarob: I think you'll get conversion but probably not as big as https://review.openstack.org/#/c/50509/ ended up14:01
*** jhenner1 has quit IRC14:01
annegentlesarob: and I do think some of it is developer, not associate14:01
*** vijendar has joined #openstack-meeting14:01
sarobTrue14:01
annegentlesarob: do you you have a timeline?14:01
sarobIt will land in the same place14:02
*** davidhadas__ has joined #openstack-meeting14:02
annegentlesarob: dguitarbite was saying by Dec.14:02
*** davidhadas___ has joined #openstack-meeting14:02
sarobYes14:02
annegentlewow it's after 914:02
annegentleOk, I'm going to end this meeting, but please continue in #openstack-doc14:02
annegentle#endmeeting14:03
*** markvan_ has joined #openstack-meeting14:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:03
openstackMeeting ended Tue Oct 22 14:03:01 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docteammeeting/2013/docteammeeting.2013-10-22-13.01.html14:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docteammeeting/2013/docteammeeting.2013-10-22-13.01.txt14:03
openstackLog:            http://eavesdrop.openstack.org/meetings/docteammeeting/2013/docteammeeting.2013-10-22-13.01.log.html14:03
*** jhenner has joined #openstack-meeting14:03
*** NickChase has left #openstack-meeting14:03
dguitarbitesarob: we have training-manuals meeting14:03
*** HenryG has quit IRC14:04
*** thomasbiege has quit IRC14:04
*** davidhadas_ has quit IRC14:04
*** yamahata has quit IRC14:04
*** davidhadas has quit IRC14:05
*** ociuhandu has quit IRC14:05
*** changbl has quit IRC14:06
*** dianefleming has left #openstack-meeting14:06
*** shaunm has left #openstack-meeting14:06
*** markvan has quit IRC14:07
*** markvan_ is now known as markvan14:07
*** zehicle_at_dell has joined #openstack-meeting14:07
*** sarob has quit IRC14:07
*** dims has joined #openstack-meeting14:07
*** johnthetubaguy has joined #openstack-meeting14:09
*** yamahata has joined #openstack-meeting14:10
*** ben_duyujie has quit IRC14:11
*** dguitarbite has quit IRC14:13
*** HenryG has joined #openstack-meeting14:13
*** dguitarbite has joined #openstack-meeting14:13
*** dguitarbite has quit IRC14:14
*** dguitarbite has joined #openstack-meeting14:14
*** yamahata has quit IRC14:15
*** dguitarbite has quit IRC14:16
*** dguitarbite has joined #openstack-meeting14:16
*** sarob has joined #openstack-meeting14:16
*** yamahata has joined #openstack-meeting14:17
*** egallen has quit IRC14:17
*** dkehn has quit IRC14:17
*** sjing has quit IRC14:19
*** ygbo has joined #openstack-meeting14:20
*** jamespage_ has joined #openstack-meeting14:20
*** egallen has joined #openstack-meeting14:21
*** egallen has quit IRC14:21
*** Ska_ has quit IRC14:22
*** AJaeger has quit IRC14:22
*** egallen has joined #openstack-meeting14:24
*** eharney has joined #openstack-meeting14:25
*** ben_duyujie has joined #openstack-meeting14:25
*** SergeyLukjanov has joined #openstack-meeting14:26
*** ozstacker has joined #openstack-meeting14:26
*** jamespage_ has quit IRC14:27
*** egallen has quit IRC14:28
*** markpeek has quit IRC14:28
*** markpeek has joined #openstack-meeting14:28
*** doron_afk has joined #openstack-meeting14:29
*** oubiwann_ has joined #openstack-meeting14:29
*** reed has joined #openstack-meeting14:30
*** egallen has joined #openstack-meeting14:30
*** kersten has joined #openstack-meeting14:31
*** doron_afk is now known as doron14:32
*** ozstacker has quit IRC14:33
*** rongze has quit IRC14:34
*** dcramer_ has quit IRC14:34
*** rongze has joined #openstack-meeting14:34
*** dcramer_ has joined #openstack-meeting14:35
*** dkranz has quit IRC14:37
*** zhhuabj_home has quit IRC14:38
*** doron is now known as doron_afk14:38
*** doron_afk is now known as doron14:38
*** ryanpetrello has joined #openstack-meeting14:39
*** rongze has quit IRC14:39
*** dguitarbite has quit IRC14:39
*** sacharya has joined #openstack-meeting14:40
*** dguitarbite has joined #openstack-meeting14:42
*** sgordon has left #openstack-meeting14:42
*** bmelande has joined #openstack-meeting14:42
*** dkehn has joined #openstack-meeting14:43
*** jaypipes has joined #openstack-meeting14:43
*** tsufiev has quit IRC14:49
*** danwent has joined #openstack-meeting14:49
*** mestery has quit IRC14:49
*** dkranz has joined #openstack-meeting14:49
*** chandankumar has quit IRC14:50
*** chandankumar has joined #openstack-meeting14:51
*** dguitarbite has quit IRC14:54
*** bmelande has quit IRC14:54
*** thomasbiege has joined #openstack-meeting14:55
*** bmelande has joined #openstack-meeting14:55
*** dscannell has joined #openstack-meeting14:57
*** thomasbiege has quit IRC14:57
*** garyk has joined #openstack-meeting14:57
*** thomasbiege has joined #openstack-meeting14:58
*** matsuhashi has quit IRC14:58
*** matsuhashi has joined #openstack-meeting14:59
*** chandankumar has quit IRC15:00
*** topol has quit IRC15:00
*** cody-somerville has quit IRC15:01
alaskigaryk: ping15:01
garykanyone around for the scheduler15:01
*** amotoki has joined #openstack-meeting15:01
garykalaski: hi15:01
garykyou want to run it or should i?15:01
alaskigo ahead.  Just making sure you were here15:02
garykyeah, thanks for taking care of last week15:02
*** chandankumar has joined #openstack-meeting15:02
*** sarob has quit IRC15:02
alaskisure, np15:02
garykeveryone ready to start15:02
garyk#startmeeting scheduler15:02
openstackMeeting started Tue Oct 22 15:02:59 2013 UTC and is due to finish in 60 minutes.  The chair is garyk. Information about MeetBot at http://wiki.debian.org/MeetBot.15:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
*** openstack changes topic to " (Meeting topic: scheduler)"15:03
openstackThe meeting name has been set to 'scheduler'15:03
*** Yathi has joined #openstack-meeting15:03
*** eharney has quit IRC15:03
garyksorry about not making it last week15:03
*** matsuhashi has quit IRC15:03
garykdo we have any open issues regarding the summit sessions?15:03
YathiWhat is the final list?15:03
*** mspreitz has joined #openstack-meeting15:03
*** chandankumar has quit IRC15:04
alaskiThe list isn't final yet15:04
YathiLast week we decided to merge API + smart resource placement sessions into one15:04
alaskibut we're looking at 4 slots right now15:04
Yathiafter some discussion other pieces were taken out15:04
alaskiso API and smart resource placement should get their own sessions15:04
alaskiinstance group api15:04
*** chandankumar has joined #openstack-meeting15:04
Yathioh that is sweet15:04
*** jmontemayor has joined #openstack-meeting15:04
mspreitzSo we got 4 slots?15:04
*** SergeyLukjanov is now known as _SergeyLukjanov15:05
*** ivasev has joined #openstack-meeting15:05
*** whenry has joined #openstack-meeting15:05
garykis there an updated list of the latest session topics15:05
*** _SergeyLukjanov has quit IRC15:05
alaskimspreitz: yes15:05
mspreitzgreat15:06
*** sushils has quit IRC15:06
Yathiare we documenting this final list some where ?15:06
alaskigaryk: not yet, some have been refused and preapproved but a lot aren't touched yet15:06
garykalaski: ok, thanks15:06
alaskibut the ones that were discussed last week are looking good for approval15:07
garykgreat. thanks!15:07
alaskirethinking scheduler design, extensible metrics, instance group api, amrter resource placement15:07
alaskismarter15:07
garykok cool.15:07
garyki have concerns with the metrics15:08
alaskirethinking design is taking over for performance since boris didn't propose a session15:08
alaskiand they seem to have some overlap15:08
garyknot really regarding the session but issues that i stumbled on a few days ago15:08
garyki think that is logical. i guess that the design considerations should take the performance and scale into account15:09
alaskigaryk: are you going to be at the summit?15:09
*** sushils has joined #openstack-meeting15:09
garykalaski: are you familiar with the15:09
*** tanisdl has joined #openstack-meeting15:09
garykalaski: yes, i will be at the summit15:09
mspreitzBTW, what is the format of the design summit sessions going to be?  I heard a suggestion of text chat only.15:10
alaskigaryk: okay, it will be good if you can voicethe issue in person15:10
garykalaski: understood.15:10
alaskimspreitz: it's a discussion, with notetaking in etherpads15:10
mspreitzthanks15:11
*** radez is now known as radez_g0n315:11
garykjust wanted to ask about the resource tracking - it just seems to ignore all used statistics form the hypervisor15:11
mspreitzgaryk: examples?15:11
garykthat is, the hypervisor returns used disk and used memory15:11
mspreitzgaryk: no good to ignore, IMHO15:12
*** devios_Lang has joined #openstack-meeting15:12
garykthe scheduler is not aware of these as the resource tracker calculate the used memeory and disk by itself15:12
*** changbl has joined #openstack-meeting15:12
*** boris-42 has quit IRC15:12
garykmspreitz: that is my concern too15:12
mspreitzDo we have evidence of whether or not that dead reckoning falls short in practice?15:12
*** RajeshMohan has quit IRC15:12
Yathidon't we update the host metrics after a scheduling is done15:12
YathiI am surprised15:13
mspreitz(I have evidence from other systems that it will)15:13
garykmspreitz: i am not sure.15:13
*** doron is now known as doron_afk15:13
garykmy concern is that the scheduler may think that there is enough disk space but a cinder volume may take up space and the resource tracker may not be aware of this15:14
*** radez_g0n3 is now known as radez15:14
garykthat is just one case.15:14
mspreitzYow, that's a really simple example.15:14
mspreitzIf it can fail that way, won't we already have reports of problems?15:14
garyki guess that i need to go back and do my homework15:14
*** RajeshMohan has joined #openstack-meeting15:15
Yathiwell scheduler has this notion of retries..15:15
*** jlucci has joined #openstack-meeting15:15
toan-tranI have a problem of updating too15:15
*** thomasbiege has quit IRC15:15
YathiI am guessing that is how it works now.. if something is not really available15:15
toan-tranwhenI create multiples VMs15:15
toan-tranI got that they are not registered immediately15:15
garykplease look at the comment - https://github.com/openstack/nova/blob/master/nova/compute/resource_tracker.py#L57615:15
garyktoan-tran: not sure i understand your comment. what do you mean by regsitered15:16
toan-tranmeaning the scheduler sheduling the second VM does not know see the first in DB15:16
toan-transorry, register = update DB15:16
*** eharney has joined #openstack-meeting15:17
toan-tranI made a simple weigher that looks for number of VMs in a host instead of available Ram15:17
Yathigaryk: now it makes sense, probably it is just taking into consideration the current instance15:17
*** vkmc has joined #openstack-meeting15:17
*** vkmc has quit IRC15:17
*** vkmc has joined #openstack-meeting15:17
alaskitoan-tran: yeah, there's definitely a race condition with muiltiple instances being scheduled in quick succession15:17
Yathiand not the actual hypervisor's state15:17
toan-tranthen I found out that DB is not updated among multiple VMs15:17
garykYathi: but the hyperviosr has the true picture of the actual state of the host - that is, the actual amount of free memory and disk space.15:18
mspreitzThis is one reason I keep talking about scheduling against the union of observed and target state.15:18
*** cdub_ has joined #openstack-meeting15:18
alaskiSo there was a session proposed about cleaning up the resource tracker.  We're passing it over based on there being no contention about cleaning it up.15:19
Yathisomething still needs to be done for race conditions I guess, when multiple scheduling calls in parallel or quick succession15:19
*** doron_afk is now known as doron15:20
alaskiThere are likely to be issues with it but I don't think there's resistance to fixing it up15:20
mspreitzYeah.  Take the union of plans and effects as the current usage.15:20
toan-tranYathi: +115:20
*** dprince has quit IRC15:20
garykalaski: i am in favor of fixing it up.15:21
Yathiwhich of our planned sessions covers the resource tracking topic - enhanced metrics ?15:21
*** SergeyLukjanov has joined #openstack-meeting15:21
mspreitzI think the other one... that's Boris' topic, right?15:21
garykalaski: i just think that it would be nice if there were considerations to the actual usage on the hyperviosr15:21
alaskigaryk: agreed15:21
Yathigaryk: +115:21
mspreitzalaski, garyk: agree.  Union the actual usage and the planned usae.15:22
*** zul has joined #openstack-meeting15:22
Yathihow often do we update the db to get the latest hypervisor states.. that matters I guess here15:22
alaskiYathi: enhanced metrics has some overlap with resource tracking concerns15:23
mspreitzIf you use the union, latency only affects speed with which you can reclaim freed space15:23
toan-trangaryk: +115:23
alaskibut overall resource tracking issues are non contentious.  the work just needs to be done15:23
garykresource tracker - http://docs.openstack.org/developer/nova/api/nova.compute.resource_tracker.html15:24
toan-tranYathi: if I'm not wrong, once per several seconds at best15:25
toan-tranYathi: if I'm not wrong, once per several seconds at best15:25
mspreitzMaybe somebody could spell out those two current session proposals in a bit of detail, so we know what goes in which?15:25
garykmspreitz: as far as i recall the one was about ceilometer/accessing the resources directly15:25
Yathiwhat is part of the "rethinking design" session15:26
*** rnirmal has joined #openstack-meeting15:26
garyki thin line 63 - https://etherpad.openstack.org/p/IceHouse-Nova-Scheduler-Sessions15:26
*** thomasbiege has joined #openstack-meeting15:26
toan-tranthere is a blueprint on real resource usage: https://blueprints.launchpad.net/nova/+spec/utilization-aware-scheduling15:27
*** thomasbiege has quit IRC15:27
garykalaski: Yathi: who will be leading the "rethinking" session?15:28
*** thomasbiege has joined #openstack-meeting15:28
Yathiwhere is the "rethinking" session in our etherpad?15:28
*** doron is now known as doron_afk15:29
garykYathi: I do not think that it appears.15:29
alaskigaryk: I believe it's Mike Wilson(?)15:29
alaskigoes by geekinutah in irc, but doesn't appear to be on15:29
*** imsurit has joined #openstack-meeting15:30
alaskiYathi: it's not in the etherpad, but it took the place of scheduler performance15:30
alaskisince there's no propsed session there15:30
garykalaski: thanks.15:30
*** doron_afk has quit IRC15:31
mspreitzI thought Boris was going to propose a session?15:31
*** johnthetubaguy1 has joined #openstack-meeting15:31
alaskiand it's looking to address similar concerns15:31
alaskimspreitz: I thought so to, but he didn't15:31
*** SergeyLukjanov is now known as _SergeyLukjanov15:31
*** egallen has quit IRC15:31
garyki guess that we should try and sync on this topic so that we can be most affective when we meet up15:31
*** anniec has quit IRC15:31
*** _SergeyLukjanov is now known as SergeyLukjanov15:32
*** SergeyLukjanov is now known as _SergeyLukjanov15:32
*** _SergeyLukjanov is now known as SergeyLukjanov15:32
*** topol has joined #openstack-meeting15:32
mspreitzgaryk: sounds good, but what does that mean?15:32
*** johnthetubaguy has quit IRC15:32
YathiCan someone please point me to any written description of this "rethinking" session?15:32
alaskiYathi: http://summit.openstack.org/cfp/details/3415:33
Yathialaski: Thanks15:33
garykmspreitz: i am not sure. i think that we need to have boris and theguyfromutah talk15:33
mspreitzSession 34 is different from Boris' topic15:33
mspreitzgaryk: if we can do that, it would be great15:34
*** ben_duyujie has quit IRC15:34
*** haomaiwa_ has quit IRC15:34
YathiThere are some overlaps in the "rethinking" session to our "smart resource placement" ideas15:34
garyk#action try and get some talk about ideas of the rethinking prior to the summit15:35
mspreitzYathi: yes.  Smart has to be "good enough"15:35
*** rongze has joined #openstack-meeting15:35
Yathimspreitz: yeah the smart need to always wait for the most optimal solution15:35
Yathibut it need not15:35
mspreitzYou mean NOT always wait15:35
Yathiyeah NOT always wait.. sorry15:36
*** belmoreira has quit IRC15:36
mspreitzOptimization problems are usually NP hard, you never expect to find the true optimum15:36
Yathithere has to be a cut off as to when to stop the minimization or maximization,  as long as the constraints are satisfied,  you are good..15:37
mspreitzSo, yeah, I think going smart implies doing what session 34 asks for.15:37
mspreitzyathi: exactly15:37
garykat the moment i feel that people are dealing with a lot of issues: placement, processing, interactions with databases etc.15:37
*** johnthetubaguy1 is now known as johnthetubaguy15:38
garyki am not sure that we have one topic or idea that covers it all.15:38
*** HenryG has quit IRC15:38
YathiI think our idea for the smart placement involves this one piece of a smart resource placement - constraint solver, along with the other aspects15:38
alaskisession 34 is also dealing with performance.  geekinutah is dealing with a >1000 node cluster iirc and they've had performance issues they want to address15:38
*** HenryG has joined #openstack-meeting15:38
mspreitzI did not think smart was only for small systems15:39
*** rongze has quit IRC15:39
Yathiother aspects I mean - common db that covers cross services, suitable for high scale, improved performance over filter scheduling,15:39
garykalaski: is there any mention of the number of schedulers they are using?15:40
Yathiwell we have a bunch of sessions with overlapping concerns15:40
*** enikanorov1 has joined #openstack-meeting15:40
mspreitzyathi: yes15:40
alaskigaryk: it may have come up before but I don't recall, might be 1 though15:40
garykok, thanks15:41
*** enikanorov1 has quit IRC15:41
mspreitzHis etherpad explicitly suggests parallel schedulers15:41
*** enikanorov has quit IRC15:41
*** enikanorov_ has joined #openstack-meeting15:41
toan-tranis SovlerScheduler in smarter placement ?15:41
*** blamar has quit IRC15:42
*** btorresgil has joined #openstack-meeting15:43
Yathitoan-tran - SolverScheduler is one aspect of the smarter placement, but involves other aspects too15:43
*** jcoufal has quit IRC15:43
toan-tranYathi: thanks15:43
*** cdub_ has quit IRC15:43
Yathitoan-tran: See line 53 in https://etherpad.openstack.org/p/IceHouse-Nova-Scheduler-Sessions15:44
toan-tranI'm just curious about the choice of LinearProgram15:44
toan-tranis it a little time-consuming?15:44
*** litong has joined #openstack-meeting15:44
garykthe idea proposed is intersting15:45
YathiThe idea is a pluggable constraints-based solver framework.. so any pluggable solvers can be included15:45
garyki think that the pain points will arise when it comes to the messaging15:45
garykthat is, we need some kind of p2p messaging.15:46
mspreitzgaryk: for what?15:46
toan-tranYathi: ok, so not necessary LP, thanks15:46
garykfor the "rethinking"15:46
mspreitzI'm lost.15:46
*** marekd is now known as marekd|away15:46
mspreitzp2p = peer to peer15:46
mspreitz?15:46
Yathiare we talking some kind of mapreduce kind of scheduling ?15:46
garykmspreitz: i am going over what is written in https://etherpad.openstack.org/p/RethinkingSchedulerDesign15:47
Yathidistributed15:47
mspreitzYou mean offline one-on-one discussions?15:47
*** yaguang has joined #openstack-meeting15:47
mspreitzthat etherpad ends with a long list of alternatives15:47
mspreitzone of which is optimization orientation15:47
*** doron_afk has joined #openstack-meeting15:48
garyki have to go over it in more detail. i am just concerned that the current infrastructure that we have may not be suited for something like this. i guess that when we discuss it we can see what is required, what is missing and then address.15:49
Yathigaryk: mspreitz: if that etherpad has a bunch of alternatives, what is it mainly trying to achieve ? - performance ?15:49
mspreitzgaryk: there are many "it" there.  My group has done some investigation of some of them.15:49
mspreitzFirst two bullets say "scalability" to me15:50
garykbut maybe i am being a little conservative - that is, if we are unable to get very simple things in then how can we do something that is non trivial15:50
mspreitzscalability in cloud size, request rate15:50
Yathinot very clear - there could be several alternatives possible that way15:50
mspreitzI would also say we should be explicit about request size15:50
*** Guest70482 has quit IRC15:50
mspreitzwhen request is for a whole pattern, not a single resource15:51
*** blamar has joined #openstack-meeting15:51
*** KC-Wang has joined #openstack-meeting15:51
garykyes, a request should be a whole pattern, only the scheduler can know how to place a collection or resources most optimally15:51
mspreitzWe had a summer student with an economics background investigate a bidding approach that can solve joint problems with things like bidding.  Takes several rounds of bidding to sort of converge.15:52
mspreitzI mean problems with affinity15:52
*** imsurit has quit IRC15:52
mspreitzResult was not strong enough to make us take that approach.15:53
Yathigaryk:  is it now related to instance group apis + the smarter placement taking the whole picture into consideration15:53
garyki guess that we can all agree - it will be challenging and interesting :)15:53
*** cdub_ has joined #openstack-meeting15:53
Yathicross-services scheduling is key15:53
*** Shaan7 has quit IRC15:53
garykagreed15:54
Yathiwe made some progress - combining cinder into nova to schedule based on volume affinity15:54
*** Shaan7 has joined #openstack-meeting15:54
mspreitzAgreed too.  but it also has the problems in "rethinking"15:54
*** imsurit has joined #openstack-meeting15:54
garykyup, i do not think that it was even addressed in the etherpad (but may be wrong here)15:54
garykare there any additional issues that we would like to address?15:55
mspreitzright now or at the summit?15:55
garyknow - we have ~4 min left15:56
mspreitzI'd like to plead for progress on the API issues before the summit.15:56
*** markwash has joined #openstack-meeting15:56
mspreitzNo time to do anything now,15:56
garykmspreitz: +115:56
mspreitzbut maybe we can agree to do something inML?15:56
garykmspreitz: that would be great.15:57
garykmaybe if the sessions are closed then next week we can start with discussing the API's15:57
Yathigaryk: mspreitz:  I guess the API work we have made significant progress already15:57
Yathiwe agreed on the model15:57
Yathileaving certain minor implementation specifics aside15:58
Yathinow it is about how the list of APIs to support..15:58
Yathiand what the payload will be like15:58
mspreitzright.  My group is implementing right now, I am hoping for convergence15:58
Yathimspreitz:  Good,  Debo and I are planning to push updates for the already committed instance group API code15:59
Yathibut this is planned for Icehouse, and not planned to complete before the summit15:59
*** ociuhandu has joined #openstack-meeting16:00
garykok. i really hope we can get this in in Icehouse and do not miss this opportunity16:00
garyki guess time is up.16:00
mspreitzIt's all provisional, which is why I am concerned about convergence16:00
garykchat to you guys next week16:00
mspreitzthanks16:00
Yathiok thanks16:00
*** devios_Lang has quit IRC16:00
garyk#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Tue Oct 22 16:00:50 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-10-22-15.02.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-10-22-15.02.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-10-22-15.02.log.html16:00
primeministerp#startmeeting hyper-v16:01
openstackMeeting started Tue Oct 22 16:01:11 2013 UTC and is due to finish in 60 minutes.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.16: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
primeministerphi everyone16:01
*** toan-tran has quit IRC16:01
primeministerpalexpilotti: hi alessandro16:01
alexpilottihello guys!16:01
ociuhanduhi all16:01
primeministerphmm no luis16:01
alexpilottiwho's around today?16:02
primeministerpnot many16:02
primeministerpno luis or pedro16:02
primeministerpI have only a few things to cover16:02
primeministerpone being the puppet bits16:02
primeministerpconsidering there's no luis16:02
primeministerpi'll followup w/ him directly16:03
primeministerpso16:03
primeministerpon that note16:03
primeministerplet's quickly talk about the other two items16:03
primeministerp#topic havana release16:03
*** openstack changes topic to "havana release (Meeting topic: hyper-v)"16:03
*** davidhadas___ has quit IRC16:03
primeministerpalexpilotti: you had some things to add on the topic?16:03
alexpilottiit's a quick one16:04
*** davidhadas__ has quit IRC16:04
*** tristanC has joined #openstack-meeting16:04
alexpilottitoday we'll have the installer out for Hyper-V16:04
*** mspreitz has left #openstack-meeting16:04
alexpilottia few bugs needs to be added from master16:04
alexpilottias discussed ectensively on the list lately16:04
*** hemna has joined #openstack-meeting16:04
*** Yathi has quit IRC16:05
primeministerpalexpilotti: ok16:05
primeministerpalexpilotti: anything more to add here that wasn't already on the list?16:05
alexpilottiso if anybody plans to roll out Hyper-V from the bits available on launchpad / git, please mind this16:05
*** sandywalsh has quit IRC16:05
alexpilottino, all good :-)16:05
*** iben has joined #openstack-meeting16:05
alexpilottiunless anybody has questions, that's it16:06
*** cdub_ has quit IRC16:06
*** gyee has joined #openstack-meeting16:06
*** luis_fdez has joined #openstack-meeting16:06
primeministerpluis_fdez: hi luis_fdez16:06
luis_fdezhi primeministerp16:06
primeministerpwe didn't have much to talk about today but I wanted to touch base on the puppet bits16:07
*** markwash has quit IRC16:07
primeministerp#topic puppet16:07
*** openstack changes topic to "puppet (Meeting topic: hyper-v)"16:07
*** DennyZhang has quit IRC16:07
luis_fdezok16:07
primeministerpluis_fdez: i've had vijay validate all the changes16:07
*** yamahata has quit IRC16:07
luis_fdezis all ok?16:07
primeministerpluis_fdez: to the dependancies16:07
primeministerpluis_fdez: so far16:07
primeministerpluis_fdez: he had a couple of patches16:07
*** yamahata has joined #openstack-meeting16:07
*** DennyZhang has joined #openstack-meeting16:07
primeministerpluis_fdez: all the hyper-v stuff seemed to work16:07
*** lsmola has quit IRC16:07
primeministerpluis_fdez: there is work being done to add the domain controller bits, and domain member bits to windows common16:08
luis_fdezyeps, I saw nick PR16:08
primeministerpluis_fdez: i know you commented on nick's works16:08
primeministerpluis_fdez: i haven't checked the new pull request yet16:08
luis_fdezok16:08
primeministerpluis_fdez: do you have any outstanding pull requests?16:08
luis_fdezno, last week I was patching other module (puppet-concat) I need for managin our infras16:09
luis_fdezto support windows16:09
luis_fdezI want to take a look this week to:16:09
luis_fdezadding NTP to windows common and16:10
primeministerpluis_fdez: so i have the existing bits16:10
luis_fdezimproving the way we handle differente openstack releases on the openstack_hyper_v module16:10
primeministerpluis_fdez: we had talked about moving it to puppetlabs-ntp16:10
luis_fdezyes16:10
*** imsurit has quit IRC16:10
primeministerpluis_fdez: do you want to move it to windows_common for the short terms16:10
primeministerpluis_fdez: the windows ntp bits?16:11
luis_fdezyes, it can be an options, but I'd to improve the puppetlabs-ntp... but I think it's thought for unix os16:11
*** jlucci has quit IRC16:11
primeministerpluis_fdez: we don't have to push everything into single modules16:12
primeministerpluis_fdez: if it doesn't make sense too16:12
primeministerpluis_fdez: let's put it in the windows common for now16:12
luis_fdezprimeministerp, I agree :)16:13
primeministerpluis_fdez: is there anything else that you know of that needs to be addressed other than the ntp bits16:13
luis_fdezI think we have all the critical parts managed16:13
luis_fdezwell... I didn't take a look to the firewall related modules16:14
primeministerpluis_fdez: they just disable the firewall16:14
primeministerpluis_fdez: not actually manage it like a proper type/provider16:14
luis_fdezanother one I think you want to improve is the configuration of RDP16:14
*** devios_Lang has joined #openstack-meeting16:15
primeministerpluis_fdez: i've started looking at that16:15
primeministerpluis_fdez: for alternative ways to config it w/o using that 3rd party powershell16:15
primeministerpluis_fdez: i've already updated the existing to use the registry module16:15
primeministerpluis_fdez: we need to address the config for older rdp clients16:15
luis_fdezgood, I think that one is useful :)16:15
primeministerpluis_fdez: i was using that 3rd party powershell for that16:16
primeministerpluis_fdez: need to find an alternative16:16
*** cdub_ has joined #openstack-meeting16:16
primeministerpluis_fdez: ok then, let's continue on the existing path16:17
luis_fdezwhat's the functionality more difficut to automate without that 3rd party tool?16:17
luis_fdezok, let's continue :)16:17
primeministerpluis_fdez: yes, that powershell module basically creates an easy way to configure it16:17
luis_fdezok16:18
primeministerpluis_fdez: that's all i have16:18
primeministerpluis_fdez: anything else?16:18
primeministerpalexpilotti: anything else from your side?16:18
luis_fdeznothing :)16:18
alexpilottiI'd introduce quickly the first round of BPs16:19
primeministerpok thx luis_fdez16:19
primeministerpok guys i'm going to end it early16:19
primeministerpluis_fdez: did you email me your address?16:19
alexpilottiI mean the Icehouse ones :-)16:19
luis_fdezwhat?16:19
primeministerpluis_fdez: can you email your address, i have something to send you16:19
luis_fdezuooou... ok, I will :)16:20
*** yassine has quit IRC16:20
primeministerpalexpilotti: do you want to do that now?16:20
primeministerpalexpilotti: before I end it16:20
alexpilottiwell, yes :-)16:20
alexpilottias the objective is to record it in the minutes16:20
*** cdub_ has quit IRC16:20
alexpilottiso that if anybody wants to check it later it's there16:20
*** zul has quit IRC16:20
alexpilottican you plz change the topic? :-)16:21
primeministerp#topic icehouse blueprints16:21
*** openstack changes topic to "icehouse blueprints (Meeting topic: hyper-v)"16:21
alexpilottitx16:21
*** mrodden has quit IRC16:21
alexpilottiSo just a quick rundown:16:22
alexpilottinot many as the main focus this time is going to be the CI16:22
*** radez is now known as radez_g0n316:22
alexpilottiso16:22
alexpilottiRDP16:22
*** nermina has quit IRC16:22
alexpilottihttps://blueprints.launchpad.net/python-novaclient/+spec/hyper-v-rdp-console16:22
*** radez_g0n3 is now known as radez16:23
alexpilottibits are up for review since, well Havana16:23
*** KJ_ has joined #openstack-meeting16:23
alexpilottithis time the Nova guys should have more time to look at it16:23
alexpilottihttps://blueprints.launchpad.net/nova/+spec/hyper-v-remotefx16:23
alexpilottisame discussion for remoteFX16:23
*** KJ_ has left #openstack-meeting16:24
alexpilottiforgot the link command, sorry16:24
alexpilottia new one is support for Generation 2 VMs16:24
alexpilottia feature introduced in 2012 R216:24
alexpilottiok. That's basically it for now!16:24
alexpilottiif anybody has some feature request to add, this is a good moment!16:25
*** spzala has joined #openstack-meeting16:25
alexpilottiprimeministerp: IMO we can close it here :-)16:26
*** mriedem has joined #openstack-meeting16:27
*** btorresgil has quit IRC16:27
primeministerpok16:27
primeministerp#endmeeting16:27
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:27
openstackMeeting ended Tue Oct 22 16:27:53 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:27
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-10-22-16.01.html16:27
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-10-22-16.01.txt16:27
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-10-22-16.01.log.html16:27
*** mriedem has left #openstack-meeting16:28
alexpilottibye!16:28
ociuhandubye all16:28
*** tristanC has left #openstack-meeting16:28
*** bmelande has quit IRC16:30
*** btorresgil has joined #openstack-meeting16:30
*** hemna has quit IRC16:31
ibenbye bye16:33
*** hemna has joined #openstack-meeting16:33
*** doron_afk has quit IRC16:34
*** hartsocks has joined #openstack-meeting16:34
*** adalbas has quit IRC16:34
*** rakhmerov has quit IRC16:34
*** rongze has joined #openstack-meeting16:36
*** mrodden has joined #openstack-meeting16:36
*** ociuhandu has left #openstack-meeting16:39
*** anteaya has quit IRC16:40
*** rongze has quit IRC16:40
*** jlibosva has quit IRC16:40
*** ygbo has quit IRC16:40
*** adalbas has joined #openstack-meeting16:42
*** yamahata has quit IRC16:43
*** derekh has quit IRC16:44
*** fbo is now known as fbo_away16:44
*** mestery has joined #openstack-meeting16:46
*** markwash has joined #openstack-meeting16:46
*** thomasbiege has quit IRC16:47
*** rnirmal has quit IRC16:48
*** amotoki has quit IRC16:50
*** DennyZha` has joined #openstack-meeting16:53
*** ozstacker has joined #openstack-meeting16:53
*** jcoufal has joined #openstack-meeting16:53
*** DennyZhang has quit IRC16:53
*** zul has joined #openstack-meeting16:54
*** btorresgil has quit IRC16:55
*** davidhadas has joined #openstack-meeting16:56
*** davidhadas_ has joined #openstack-meeting16:56
*** Mandell has joined #openstack-meeting16:58
*** comay has joined #openstack-meeting16:59
*** anteaya has joined #openstack-meeting17:00
*** joesavak has joined #openstack-meeting17:00
*** ozstacker has quit IRC17:00
*** twoputt has joined #openstack-meeting17:03
*** twoputt_ has joined #openstack-meeting17:03
*** julim has quit IRC17:03
*** whenry has quit IRC17:03
*** iben has quit IRC17:06
*** thomasbiege has joined #openstack-meeting17:06
*** julim has joined #openstack-meeting17:06
*** DennyZha` has quit IRC17:06
*** nermina has joined #openstack-meeting17:07
*** eglynn has quit IRC17:07
*** boris-42 has joined #openstack-meeting17:08
*** markmcclain has joined #openstack-meeting17:11
*** davidhadas has quit IRC17:12
*** davidhadas_ has quit IRC17:12
*** davidhadas has joined #openstack-meeting17:13
*** yogeshmehra has joined #openstack-meeting17:14
*** sandywalsh has joined #openstack-meeting17:17
*** anteaya has quit IRC17:17
*** jlucci has joined #openstack-meeting17:18
*** davidhadas has quit IRC17:18
*** colinmcnamara has joined #openstack-meeting17:18
*** rudrarugge has joined #openstack-meeting17:19
*** devios_Lang has quit IRC17:19
*** SergeyLukjanov has quit IRC17:22
*** akuznetsov has quit IRC17:22
*** sushils has quit IRC17:24
*** pauli1 has joined #openstack-meeting17:26
*** thomasbiege has quit IRC17:27
*** jlucci has quit IRC17:28
*** colinmcnamara has quit IRC17:28
*** btorresgil has joined #openstack-meeting17:28
*** rakhmerov has joined #openstack-meeting17:29
*** rakhmerov has quit IRC17:29
*** dscannell has quit IRC17:33
*** zul has quit IRC17:34
*** dscannell has joined #openstack-meeting17:34
*** SergeyLukjanov has joined #openstack-meeting17:35
*** markpeek has quit IRC17:35
*** markpeek has joined #openstack-meeting17:36
*** rongze has joined #openstack-meeting17:36
*** inkerra has joined #openstack-meeting17:37
*** IlyaE has quit IRC17:37
*** ItSANgo_ has quit IRC17:39
*** davidhadas has joined #openstack-meeting17:43
*** zehicle_at_dell has quit IRC17:44
*** dhellmann-afk is now known as dhellmann17:45
*** rongze has quit IRC17:47
*** jlucci has joined #openstack-meeting17:49
*** SumitNaiksatam has quit IRC17:51
*** zul has joined #openstack-meeting17:53
*** jlucci has quit IRC17:53
*** atiwari has joined #openstack-meeting17:54
*** SergeyLukjanov_m has joined #openstack-meeting17:54
*** RajeshMohan has quit IRC17:54
*** luis_fdez has quit IRC17:55
*** dolphm_ has joined #openstack-meeting17:57
*** IlyaE has joined #openstack-meeting17:58
stevemaro/17:58
*** nikhil is now known as nikhil|afk17:58
stevemaris it keystone time?17:58
*** nkinder has joined #openstack-meeting17:58
dolphm_\o/ anyone able to run the meeting? I'm afk / on my phone for a few minutes17:58
*** inkerra has quit IRC17:58
stevemarim sure ayoung will17:58
dolphm_just want to run through conference schedule17:59
dolphm_not sure what else was added to the agenda17:59
stevemarhttps://wiki.openstack.org/wiki/Meetings/KeystoneMeeting17:59
stevemarmore migration numbers and some code review requests17:59
gyee\o18:00
*** dstanek has joined #openstack-meeting18:00
*** bknudson has joined #openstack-meeting18:00
stevemar\o/18:00
bknudsonhi18:01
atiwarihi18:01
dolphm_I'm tempted to try this from my phone lol18:01
*** jamielennox has joined #openstack-meeting18:01
*** anteaya has joined #openstack-meeting18:01
joesavak\hi/18:01
gyeephone?18:01
dstanekhello18:01
dolphm_I'm afk18:01
dstanekdolphm_: good luck18:01
*** SergeyLukjanov_m has quit IRC18:01
topolhi, sorry for missing past two weeks.  I was at conferences giving shout outs to dolphm, and ayoung to folks from their companies18:01
morganfainbergo/18:01
stevemardolphm is sorta pre-occupied, any takers for chairing the meeting?18:01
jamielennoxhi18:02
dolphm_topol o/18:02
joesavak#start-meeting keystone18:02
*** bklei has joined #openstack-meeting18:02
joesavakhmm - i don't remember...18:02
stevemar#startmeeting keystone18:02
openstackMeeting started Tue Oct 22 18:02:42 2013 UTC and is due to finish in 60 minutes.  The chair is stevemar. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
*** nachi has joined #openstack-meeting18:02
dolphm_lol honorable attempt18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: keystone)"18:02
openstackThe meeting name has been set to 'keystone'18:02
gyeewe usually turn the meeting into a beer bash if the chair is not around18:02
morganfainbergstevemar, haha i was typing that as you did it.18:02
stevemar#link https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:03
dolphm_success18:03
stevemar#topic Reserved migration numbers for havana18:03
*** openstack changes topic to "Reserved migration numbers for havana (Meeting topic: keystone)"18:03
stevemarlooks like it's continuing from last week18:03
ayoungKEYSTONE!18:03
dolphm_p.s. everyone's homework was to read up on reserved migrations18:03
joesavakwhoops.18:04
dolphm_have we had any migrations merge since last week?18:04
morganfainbergdolphm_, don't think so18:04
stevemardont think so18:04
bknudsonwhat would require a migration?18:04
dolphm_slash, since rc118:04
ayounglooking18:04
bknudsonI thought morganfainberg had some late fixes to migrations...18:05
dolphm_if we've had anything merge, this this topi is moot18:05
dolphm_topic*18:05
*** hartsocks1 has joined #openstack-meeting18:05
gyeesince most new features start out as extensions, there should be very little migration if any18:05
morganfainbergbknudson, that was logic to a migration that was already there18:05
morganfainbergbknudson, for sqlite18:05
morganfainbergno new migration(s)18:05
*** aguzikova_home has joined #openstack-meeting18:05
dolphm_gyee: interesting point- we'd need reserved migrations for extensions as well18:06
*** SergeyLukjanov_m has joined #openstack-meeting18:06
gyeedolphm_, wait, I thought extensions are different18:06
morganfainberggyee, if we're putting in reserves for one, we should for the other.18:06
stevemaragreed18:06
*** hartsocks has quit IRC18:06
ayoungdolphm_, we could do them like BASIC programs, and number them 5, 10, 15...18:06
*** hartsocks1 is now known as hartsocks_18:06
morganfainbergayoung, i.. i.. i have no words18:06
gyeek, I am fine with reservation18:07
ayoungthen if we need to instert a migration between 10 and 15 make it 1218:07
dolphm_ayoung: they need to be sequential18:07
morganfainbergayoung, brilliant!18:07
ayoungpoke 53280,118:07
morganfainbergunfortunately, what dolphm_ said18:07
gyeelow hanging fruit18:07
joesavak1, 2, 3 - then if we need to insert one; 1.1?18:07
morganfainbergdolphm_, how many reserved numbers do you think we need?18:07
joesavak;)18:07
stevemarjoesavak, if only18:07
bknudsonlooks like Nova had placeholders in grizzly and never wound up using them.18:07
dolphm_3 in extension repos, 5-10 in core?18:07
ayoungdolphm_, what if we have a separate repo for back fixes?18:07
*** zul has quit IRC18:08
morganfainbergayoung, how would that work?18:08
dolphm_ayoung: that wouldn't be tranparent18:08
*** anteaya has quit IRC18:08
bknudsonI don't think it'll hurt anything to add the placeholders, and could potentially come in handy, so why not?18:08
dolphm_is anyone strongly opposed to reserved migrations?18:08
*** SergeyLukjanov_m has quit IRC18:09
morganfainbergdolphm_, not opposed.18:09
stevemarnot i18:09
dolphm_bkhudson: agree18:09
morganfainbergi'd say 3 in extensions, 5 in main max though18:09
stevemarsounds like they'll be handy18:09
topolsounds good18:09
ayoungor...beter yet, a separate repo for Icehouse fixes18:09
ayoungso once we backport a fix to Havana, we adjust the fixes in the Icehouse repo to account for them....just a thought18:09
morganfainbergnova _never_ used them.  i don't really think we're going to, but they are mostly harmless if they exist.18:09
gyeeI see *each* extension have their own migration_repo dir18:09
gyeeso we are saying, 3 reservations per repo?18:10
morganfainberggyee, i would say at most.18:10
morganfainberg3.18:10
gyeek18:10
*** anteaya has joined #openstack-meeting18:10
ayoungI think reservations is the wrong approach.  I have a thought...let me collect it and write it up18:10
dolphm_that works18:10
morganfainbergayoung, ok.18:10
stevemarayoung, sure send it to ML18:11
stevemarso that gets chalked up as an action item?18:11
ayoungyeah18:11
morganfainbergdolphm_, slightly related, we doing a collapse of the migrations this time around? or?18:11
stevemarany volunteers? :)18:11
*** thomasm has joined #openstack-meeting18:11
ayoung#action ayoung write up approach to backporting migrations using separate repo18:11
gyee#action ayoung to turn on his light bulb on migration reservation?18:11
dolphm_I'll do the reservations18:11
*** thomasm is now known as Guest2505118:11
*** SumitNaiksatam has joined #openstack-meeting18:12
dolphm_if someone wants to do the work of collapsing, go for it18:12
stevemar#action dolphm to look at reservations18:12
stevemarnext topic, way more fun18:12
morganfainbergdolphm_, i'll see if I can make that happen.18:12
dolphm_stevemar: what's next?18:12
stevemar#topic Reviewing design summit schedule18:12
*** openstack changes topic to "Reviewing design summit schedule (Meeting topic: keystone)"18:12
stevemar#link http://summit.openstack.org/18:12
*** elo has quit IRC18:12
stevemarfor my topic18:12
morganfainberg#action morganfainberg look into collapsing migrations18:12
stevemarerr, sort*18:12
stevemarsort by topic ... sigh18:12
dolphm_I left comments on a bunch of sessions18:12
ayoungdolphm_, reservations are not going to work.  When the repo says wee are at revsion X we need to know what that means....18:12
gyeedolphm_, session on fixing service catalog?18:12
stevemardolphm_ how many session spots do we have?18:13
*** Mandell has quit IRC18:13
dolphm_918:13
gyeethe remaining 20 will be conducted in a pub18:13
dolphm_I'd like to split federation and the client session18:13
dolphm_gyee: ++18:13
*** vito-ordaz has joined #openstack-meeting18:13
*** Mandell has joined #openstack-meeting18:13
morganfainberggyee, ++++++++18:13
stevemarcurrently there are 11 proposed sessions, so lets try to find some that can be consolidated18:14
ayoungfederation and client should be separate.  Very different topics18:14
gyeestevemar, we can also try unconference18:14
stevemargyee: yup, but that gets busy too; and there might be some sessions that are closely related18:15
*** elo has joined #openstack-meeting18:15
morganfainbergif we can set a goal for the extensions one it can be merged with Internal API stabilization topic18:15
ayoungHTML is refused...that gets us down to 1018:15
stevemardolphm, i see you refused 2 sessions already18:15
morganfainbergthey are both code management / approach18:15
ayoungExtension mechanisms can hang on something else18:15
dolphm_i think i refused domain scoped tokens18:15
stevemarayoung: yeah, V3 API Domain Scoped Tokens and HTML for Keystone have been refused18:15
dolphm_if not, it can be18:16
ayoungmorganfainberg, that was my thought as well18:16
dolphm_we've gotten bugs to simply doc that better18:16
morganfainbergayoung, 100% agree with it.18:16
ayoungbut lets leave it as is unless any more topics come in18:16
morganfainbergright.18:16
*** anteaya_ has joined #openstack-meeting18:16
stevemarokay, if need be, we can merge those 2 sessions, Internal API Stabilization and Extension Mechanisms18:17
*** johnthetubaguy has quit IRC18:17
*** fabio_ has joined #openstack-meeting18:18
stevemaronly as a last resort :)18:18
*** fabio_ is now known as fabiog18:18
gyeethere are other session which will have Keystone impacts, i.e. killing pagination18:18
topolDid  Auditing AuthN, AuthZ and Policy Decisions get accepted?18:18
stevemartopol, not yet18:18
dolphm_the client session description is way too big for a single session18:18
*** Mandell has quit IRC18:18
morganfainbergdolphm_, perhaps we should expand the client one to 2 sessions and collapse the extensions and API stabilization ones to a single one?18:19
*** anteaya has quit IRC18:19
stevemardolphm_ suggest merging (internal API stabilitaion and extension) to get another client session?18:19
stevemarmorganfainberg +118:19
morganfainbergstevemar, ++18:19
gyeedolphm_, that's because we have too many client issues to fix :)18:19
dolphm_sounds good18:19
ayoungworks for me18:19
morganfainbergi'll update mine and incorporate the extension stuff ayoung,18:20
*** brich1 has joined #openstack-meeting18:20
dolphm_the "ignoring the API, what should the client look like" is perfect for the summit18:20
stevemar#action dolphm, refuse one of the sessions, update the comments and create a new session for client18:20
dolphm_that should be its own session18:20
*** Mandell has joined #openstack-meeting18:20
ayoungSounds good.  morganfainberg once you do, tag my session and I'll drop it18:20
bknudsonit should be async!18:20
morganfainbergayoung, will be done today.18:20
stevemarawesome18:20
ayoungbknudson, so keystone should respond to AMQP?18:21
stevemardo we need 2 sessions for federation?18:21
ayoungNo, one session for federation18:21
ayoungif it is going to take more than one, it is not going to be done in 2 either18:21
jamielennoxdolphm_: i'm not sure how much of that client stuff we'll need to cover but i don't mind a seconds session18:21
dolphm_there's a LOT of material there18:21
morganfainbergstevemar, i think one session should be enough.  we can unconference anything else that comes up18:21
stevemari think if we can schedule it at the end of the day, we can take up any arguments at a pub later :)18:21
gyeeyes sir18:22
jamielennoxdiscovery is happening already, everyone hates auth_token, APIClient and Versioning are my two main ones18:22
*** dolphm has joined #openstack-meeting18:22
morganfainbergdolphm_, i think it'll be more about chopping things and slating for J if we're _that_ full of federation stuff.18:22
dolphm\o/ desk!18:22
morganfainbergdolphm, yay!18:22
ayoungWe have an approach, and we are, I think tracking.  Federation session should be level setting so that we can continue any long term discussions after the conference.  But I thik we are finally positioned to implement Federation in the context of the other parts of Keystone, something that was not true until Havana18:22
joesavakayoung +118:22
ayoungWhat about globally unique IDs, though18:23
ayoungthat is not really Federartion, but came up in the context of LDAP18:23
ayoungdo we need an LDAP session?  Henrynash is not here, topol ?18:23
bknudsonsounds like federation.18:23
ayoungbknudson, nope18:23
joesavakfederation handles it by user-passed-in-assertion@trusted-idp18:24
topolLDAP seems pretty much under control now from my view18:24
ayoungbknudson, similar, but this is for the case where we have a user store managed by Keysteon as well as a multiple LDAP stores.  It ties in with henrynash's assignmnet API talk, though18:24
morganfainbergayoung, i don't think we will ever have a lack of LDAP stuff to talk about, but not sure if we need a session.18:24
stevemarmorganfainberg ++18:24
bknudsonLDAP could be refactored into a read-only / read-write / ActiveDirectory implementations.18:25
stevemardolphm_ sorry, the people have spoke, 1 session for federation18:25
*** lsmola has joined #openstack-meeting18:25
ayoungdolphm, will get to talk about "The state of Keystone" as the PTL, and can level set on where LDAP is and is going to the community18:25
topolmultiple LDAP stores are really cool. but do we need enough steering ont hat to merit a session?18:25
bknudsoncould also do connection pooling.18:25
gyeeagreed, I think we have enough on LDAP already, let the consults make money off integration :)18:25
morganfainbergbknudson, that actually would be a good approach.18:25
gyeeconsultants18:25
stevemar#action everyone to read the sessions over and provide some comments :)18:25
morganfainberggyee, lol18:25
ayoungtopol, we need a way to figure out which backend to look at for a given user id18:25
dolphmstevemar: i think 1 session is crazy for such a big topic18:25
topolI would +1 gyee statement but then would need to go take a shower18:26
ayoungits a generic problem, but driven home by LDAP18:26
ayoungbut Federation will have the same issue18:26
dolphmit'll definitely be the single biggest change for icehouse18:26
joesavak+1 topol's statement18:26
ayoungWe can try to cover it in Federation, but I'm afraid it would get lost18:26
joesavak;)18:26
gyeeayoung, leave some money on the table for the consultants18:26
morganfainbergdolphm, i am not opposed to 2 sessions, but i think we will mostly be level setting for J if we have more than 118:26
morganfainbergdolphm, just unlikely that we'll see all the change by I2.18:27
morganfainbergdolphm, there is likely to be value in level setting the federation direction though18:27
dolphmmorganfainberg: i'm thinking with two sessions to help get everyone on the same page concerning the work that's been done and what we want to accomplish, we're more likely to see it done by i218:27
morganfainbergdolphm, fair enough, so 2 client, 2 federation, and collapse 2 of the other sessions?18:28
stevemarthen we need another volunteer to combine a session18:29
ayoungExtensions goes into API stabilization18:29
stevemaryup18:29
morganfainbergayoung, right, if we expand to a 2nd federation session, we need to collapse another set18:29
*** shardy is now known as shardy_afk18:29
stevemarwas centralized quota storage already talked about last summit?18:29
ayoungDo wereally need a Quota talk?  I thought that was a done deal?18:30
*** rakhmerov has joined #openstack-meeting18:30
stevemarayoung, yap18:30
ayoungWe are doing quotas, it just is not done yet18:30
ayoungdesign was signed off on,  just the develpoer got stuck in the review process18:30
morganfainbergyeah that seems redundant to do that in two subsequent sessions18:30
dolphmayoung: agree18:30
morganfainbergerm summits18:30
morganfainbergso, we can drop that one.18:30
dolphmayoung: we weren't quick enough to respond to their patchsets either18:30
aguzikova_homeayoung, we have https://review.openstack.org/#/c/37545/ also for quotas18:31
morganfainbergok so as long as we get quota stuff reviewed and accepted, we shouldn't need a session on it.18:31
gyeedolphm, ayoung, I think there were some unfinished business with quota, the usage aggregation part18:31
*** SergeyLukjanov has quit IRC18:31
aguzikova_homenot just domaint quota management18:31
stevemaryeah, it seems generally accepted18:31
gyeebut I am not sure if it really belong to keystone anyway18:31
morganfainbergaguzikova_home, ah.18:31
ayounggyee, but it would be really cool if Keystone tokens had the quotas signed in them.18:32
stevemarsounds like the axe is falling on this session topic18:32
*** mrunge has joined #openstack-meeting18:32
morganfainbergstevemar, sounds like18:32
*** nachi1 has joined #openstack-meeting18:32
*** ozstacker has joined #openstack-meeting18:32
dolphmi'm pushing sessions around now, btw18:32
*** nachi has quit IRC18:32
bknudsonare the sessions all on one day?18:32
ayoungyeah, tell them to have a quota unconference and work out the last remaining issues.18:32
*** IlyaE has quit IRC18:33
bknudsonwasn't there a security track last time?18:33
morganfainbergayoung, ++18:33
gyeeayoung, sounds good18:33
aguzikova_home+118:33
stevemar#action dolphm to refuse quota session18:33
morganfainbergbknudson, i think so… i don't remember18:33
dolphmstevemar: done18:33
morganfainbergsounds like we're doing 2 federation sessions then18:33
dolphmis the Assignments session good as is?18:33
dolphmthere's three topics there -- i'm not sure the second one is worthy of summit time18:34
bknudsonis there any real argument about what needs to be done for assignments?18:34
dolphmthat's just a "yes, we need to clean up the sql impl"18:34
gyeebknudson, lots18:34
ayoungI'll do an unconference on the HTML thing.  I really just want a chance to demo it and don't currently have public hosting available.  Need to set up one of those Rackspace developer accounts.18:34
morganfainbergpretty much we need to cleanup interfaces controllers, etc18:34
dolphmbknudson: henrynash wants a whole new HTTP API for assignments18:34
gyeelike role-service18:34
dolphmgyee: no18:34
morganfainbergdolphm, wouldn't that be API version increment?18:34
*** rakhmerov has quit IRC18:35
morganfainbergor is he saying as an extension?18:35
gyeedolphm, we still have use cases with role assignment need to solve18:35
dolphmmorganfainberg: if you're dropping support for something, yes18:35
gyeewe also need to simplify assignment APIs18:35
dolphmgyee: i'm more interested in the new use cases18:35
ayoungassignments will have enough trickiness in it that it should have its own session, but maybe that can be combined with Federation.18:35
bknudsonwe also need to simplify identity APIs18:35
morganfainbergayoung, nah.18:35
dolphmif there's a use case for having metadata on an assignment, then a first class collection makes sense18:35
ayoungIt really is the ID/Assignment split that allows Federation to work18:36
morganfainbergayoung, don't combine it18:36
stevemari thought we're good, no need to continue trimming sessions18:36
*** dscannell has quit IRC18:36
dolphmayoung: -- for combining with federation18:36
*** dscannell1 has joined #openstack-meeting18:36
stevemarif we cut domain, then we have room for federation pt 218:36
atiwariGuys, I appreciate your focus on #link https://review.openstack.org/#/c/37141 again, as the solution proposed by ayoung is not addressing all use case.18:36
gyeedolphm, ayoung, yes, assignment will be heavily impacts with federation as well18:36
gyeeespecially on the mapping18:36
stevemarugh, i meant quota18:36
morganfainberggyee, dolphm, ayoung, the assignment one should just be scheduled around the federation ones… so we are in the same mindset if we can18:37
gyeemorganfainberg, sure18:37
ayoungatiwari, we're discussing session for the summit...we'll address that in a few...18:37
dolphmcreated a placeholder18:37
dolphmhttp://summit.openstack.org/cfp/details/34618:37
topolmorganfainberg +118:37
*** markmcclain has quit IRC18:38
gyeealso, the auditing part will be very interesting, especially with mapping18:38
atiwariayoung, thanks18:38
morganfainbergso back to the original question, dolphm, i think assignment one is good.18:38
ayounggyee, yeah, but auditing actually is tied with  policy , which is not even a Keystone project, and if it were, would be part of the client18:38
ayoungfor audit what tokens a user requested is not nearly so important as figuring out what they did with them18:39
gyeeayoung, no, like given a user, tell me what he can do18:39
ayoungmorganfainberg, we can add atiwari '18:39
gyeeor given a resource, tell me who can do what to it18:39
morganfainbergdolphm, ack, you pre-approved the API one, i can't edit it now18:39
ayoungs concerns to the assignments session18:40
*** thomasm_ has joined #openstack-meeting18:40
topolayoung, doesnt auditing need to be done on the server to make sure we catch everything?18:40
ayoungatiwari, are you going to the summit18:40
dolphmmorganfainberg: crap18:40
atiwariyes18:40
gyeetopol, percisely18:40
ayoungtopol, auditing needs to be done on each machine, not just Keystone18:40
morganfainbergdolphm, lol can you set it back to unreviewed, i'll get the exention stuff added to it and ping you shortly?18:40
dolphmmorganfainberg: fixed18:40
morganfainbergk18:40
topolayoung, both Im thinking18:40
dolphmi'll stop pre-approving stuff lol18:41
stevemardolphm: that is probably a good thing :)18:41
*** dscannell1 has quit IRC18:41
stevemarso, there sounds like there is interest in auditing18:41
jamielennoxdolphm: if you unset the client i'll remove some of those points - there's really just the two in there now i really want at summit the others can be later18:41
jamielennoxclient summit session18:41
gyeestevemar, the auditing aspect is generally missing :)18:42
ayoungatiwari, we have a session for assignments   http://summit.openstack.org/cfp/details/131  please add your topic to that.  I think that it is the right place to discuss it18:42
stevemar#link https://etherpad.openstack.org/p/keystone-sessions-icehouse something i quickly wrote up18:42
*** dscannell has joined #openstack-meeting18:42
atiwariayoung, sure18:42
stevemarwe have 9 spots, and 9 currently proposed sessions... i think we're good assuming no one is against any session in particular18:43
dolphmjamielennox: working on it18:43
*** Guest25051 has quit IRC18:43
*** rongze has joined #openstack-meeting18:43
ayoungif anything else comes up, schedule unconference sessions for it.  Everyone should sign up for a twitter account, as that was really useful for tracking who was where at the summit, and posting unofficial announcements18:44
stevemarayoung +118:44
dolphmk, everything is unreviewed or refused18:44
ayoungOg..and everyone make sure your shots are up to date18:44
topolayoung +118:44
ayoungHep A and Typhoid18:44
morganfainbergayoung, yes18:44
atiwariayoung and dolphm, this may also be a good topic for session? #link https://blueprints.launchpad.net/keystone/+spec/attribute-access-privilege-based-on-role18:44
ayoungand flu18:44
gyeeunreviewed for unconference18:44
jamielennoxayoung: twitter?.... :(18:44
topolayoung, really???18:44
ayoungatiwari, in the policy session, I think18:44
topolthat wasnt in my brochure18:44
atiwariok18:44
morganfainbergjamielennox, welcome to the new internet18:44
ayoungtopol, according to the CDC18:45
dolphmatiwari: has there been disagreement on the approach?18:45
ayoungget an appointment at a travel clinic.18:45
ayoungAND EVERYONE CHECK YOUR PASSPORTS!18:45
atiwarinot yet :)18:45
*** DandyPandy has joined #openstack-meeting18:45
dolphmatiwari: then i don't think we need a session18:45
gyeeand bring enough cash to buy your way out if you wonder into the wrong hood :)18:46
atiwaridolphm, I don't think someone has looked in to it yet :)18:46
dolphmjamielennox: want to propose the second client session and break down the descriptions?18:46
ayoungatiwari, that should be discussed here: http://summit.openstack.org/cfp/details/86  I think.  It is not Audit specific, but all of that is based on the policy mechanism18:46
*** vipul is now known as vipul-away18:46
topolgyee, do you know where I can get Louis Vutton knockoff wallets? My mom keeps asking :-)18:46
dolphmatiwari: i've had several people mention it actually18:46
morganfainbergtopol, lol18:46
stevemari think everyone seems to be fine with the sessions topics .. next topic?18:47
gyeetopol, I know a place18:47
dolphmstevemar: ++18:47
dolphmo18:47
ayoungatiwari, I have, and, while I like the concept, I think only LDAP really has the mechanism to enforce an attribute level  approach.18:47
stevemarya know, before we get off-topic!18:47
topolgyee++ hook me up18:47
stevemar#topic Code reviews for icehouse blueprints18:47
*** openstack changes topic to "Code reviews for icehouse blueprints (Meeting topic: keystone)"18:47
dolphmi'll follow up with people submitting sessions after the meeting18:47
stevemar#link https://review.openstack.org/#/c/40692/ KDS service18:47
bknudsonIs this implementing a PKI server? Why wouldn't we use an existing one? If it's not PKI, why not use PKI?18:48
ayoungdolphm, so different from the Grizzly Summit, when it was You, me and heckj doing all the sessions. I could get used to this level of participation18:48
*** rongze has quit IRC18:48
ayoungbknudson, long discussion on that18:48
jamielennoxbknudson: no it's symettric18:48
fabiogguys, can we please move forward with the shared-secret?18:48
*** lbragstad has quit IRC18:48
fabiog#link https://review.openstack.org/#/c/46771/18:48
ayoungnot PKI, but symetric crypto18:48
stevemarthanks fabiog, that is for shared secret?18:48
ayoungsharing symetric keys for high through put messaging18:49
fabiogstevemar, yes18:49
*** ozstacker has quit IRC18:49
fabiogI think we should be close on that one18:49
stevemaryeah, we're close on it18:49
atiwariayoung, thanks. I think it not going to so complex to implement in Keystone (or Oslo) out of the box18:49
fabiogI did all the requested changes so far :-)18:49
jamielennoxbknudson: there was much discussion over the design for KDS, eventually it went symmetric mostly for the speed18:50
gyeeayoung, so once KDS is in, you expect default bind token?18:50
ayoungfabiog, why should shared secret be stored in the clear?18:50
bknudsonI thought TLS/etc work by generating symmetric keys after PKI18:50
ayounggyee, completely different issues18:50
jamielennoxgyee: no KDS has nothing to do with binding18:51
morganfainbergayoung, http://summit.openstack.org/cfp/details/255  did I cover everything?18:51
ayoungbind token will require Kerberos or X509 support on the remote services, so it will be a rolling implementation18:51
jamielennoxbknudson: it does18:51
jamielennoxbknudson: the KDS design tracks closer to what kerberos does18:51
gyeebut KDS an implementation of Kerberos no?18:51
jamielennoxgyee: no, just same principals18:51
ayoungbknudson, that is at transport layer, which MQ can use, but this is end to end message validity and then possibly encryption18:52
ayounggyee, no, it is like Kerberos, but Kerberos does much more.18:52
*** yaguang has quit IRC18:52
ayoungIt would have been easier to user Kerberos but that was deemed to high a bar to set for OpenStack undercloud setup18:52
bknudsonand PKI is too slow for end-to-end message validity and encryption?18:52
*** sushils has joined #openstack-meeting18:53
*** anteaya_ is now known as anteaya18:53
morganfainbergdolphm, if ayoung is happy with my edits it can be moved back to approved. [post meeting likely]18:53
dolphmmorganfainberg: ack18:53
ayoungmorganfainberg, looks good to me. dolphm +118:53
gyeebknudson, I was thinking SMIME18:53
ayounggyee, that is what we use for PKI tokens18:53
dolphmmorganfainberg: i didn't realize about the no edits policy, i'll review each individually as i schedule them18:53
ayoungCMS is basically another term for SMIME18:53
gyeeayoung, right, SMIME is for message security18:54
morganfainbergdolphm, hehe. i wouldn't have guessed except it was the way it worked.  maybe you can edit them?  not sure.18:54
*** yaguang has joined #openstack-meeting18:54
gyeeyou mentioned securing MQ18:54
gyeethat's why I was thinking SMIME18:54
ayoungbknudson, topic has been hashed over fairly thoroughly.  THere is an etherpad off the blueprint worth reading through18:54
jamielennoxbknudson: the other problem with PKI is we would have to manage all those certificates and do signing, revocation, updating etc18:54
stevemarlets all take another look at fabiog shared secret, it's close to being done18:55
bknudsonwhy would we manage them? there's already tools for it.18:55
*** jlucci has joined #openstack-meeting18:55
gyeejamielennox, we are doing it for PKI tokens18:55
gyeeat least we should be18:55
*** derekh has joined #openstack-meeting18:55
jamielennoxgyee: no, in that case we only manage one cert18:55
jamielennoxthe one that does the signing18:55
dolphmp.s. i discovered this recently https://wiki.openstack.org/wiki/KeystoneUseCases18:55
*** Loquacities has joined #openstack-meeting18:55
jamielennoxthis would need to manage a certificate for every host that issues a message18:55
stevemardolphm, wow18:56
ayoungbknudson, https://wiki.openstack.org/wiki/MessageSecurity#A_Key_Distribution_Server_in_Keystone18:56
*** bpb has joined #openstack-meeting18:56
dolphmthat would be fun to version control18:56
*** dolphm_ has quit IRC18:56
stevemar#topic open discussion18:56
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:56
stevemaronly a few minutes left18:56
dolphmcode review use case -> code review api (if necessary) -> code review implementation of new feature :P18:56
topoldolphm isnt that way out of date18:56
dolphmtopol: very18:56
dolphmbased on what's written, i'm guessing it was from spring 201218:57
dolphmmost of it, anyway18:57
dolphm~essex18:57
ayoungpredates me.18:57
topolsounds about right. take it to the pawnstars show to get a history lesson on it18:58
morganfainberglol18:58
gyeejamielonnx did someone request Keystone to run CA service from the ML?18:58
dolphmi don't know how to get the history out of the wiki, if there is any18:58
jamielennoxdolphm, bknudson: i've added the strings only interface to API discovery, can you have another look: https://review.openstack.org/#/c/38414/18:58
stevemardolphm, i was trying to do that, but i think the wikis have migrated right18:58
jamielennoxeveryone else as well ^ but we were discussion this yesterday18:58
*** jrodom has joined #openstack-meeting18:58
ayounggyee, I think for a dev CA we can look into using certmaster18:58
ayounghttps://fedorahosted.org/certmaster/18:58
ayoungwouldn't use it in production, I'd recommend dogtag for that18:59
jamielennoxgyee: it has been suggested in the past, i don't like it without a REALLY good reason18:59
bknudsonit would be interesting to have certmaster configured by devstack18:59
jamielennoxi'd prefer to see barbican do that18:59
ayoungbknudson, we are working toward that, jamielennox and I18:59
*** jlucci has quit IRC18:59
*** Loquacity has quit IRC18:59
bknudsonrather than pki_setup18:59
*** jlucci1 has joined #openstack-meeting18:59
bknudsonand ssl_setup18:59
ayoungbknudson, I want certmonger as the the essential piece18:59
stevemar#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Oct 22 19:00:02 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-10-22-18.02.html19:00
ayounghttps://fedorahosted.org/certmonger/19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-10-22-18.02.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-10-22-18.02.log.html19:00
stevemarand we're done19:00
joesavak<clap>19:00
fungiinfra peoples unite!19:00
anteayao/19:00
*** fabiog has quit IRC19:00
pleia2o/19:00
*** jamielennox has left #openstack-meeting19:00
*** brich1 has quit IRC19:00
fungi#startmeeting infra19:01
openstackMeeting started Tue Oct 22 19:01:00 2013 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:01
fungi#link http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-10-15-19.02.html19:01
clarkbo/19:02
fungi#topic Actions from last meeting19:02
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:02
anteayazaro around today?19:02
clarkbI think he is travelling to jenkins conf19:02
anteayaah19:02
fungijeblair move tarballs.o.o and include 50gb space for heat/trove images19:02
*** lbragstad has joined #openstack-meeting19:03
krtayloro/19:03
fungii assume that will remain in progress for a bit while jeblair is travelling, lest someone else has time to do it sooner19:03
*** eglynn has joined #openstack-meeting19:03
fungithat's all we had on action items19:03
fungi#topic Trove testing (mordred, hub_cap)19:04
*** openstack changes topic to "Trove testing (mordred, hub_cap) (Meeting topic: infra)"19:04
fungihub_cap said he knows how it's going to work and someone else is going to do it rsn19:04
*** dmakogon has joined #openstack-meeting19:04
*** markmcclain has joined #openstack-meeting19:04
fungibut that he's on a call right now, so not making the meeting19:04
clarkband that he wouldn't make it to the meeting to talk about it otherwise :) but excited that there is a plan somewhere :)19:04
anteayayay for a plan19:05
fungi#topic Tripleo testing (lifeless, pleia2)19:05
*** openstack changes topic to "Tripleo testing (lifeless, pleia2) (Meeting topic: infra)"19:05
fungiyou have the floor19:05
pleia2we have a super basic experimental test now19:05
* anteaya applaudes19:05
pleia2it just runs a simple echo script on a tripleo cloud system19:05
*** dmakogon has left #openstack-meeting19:05
*** novas0x2a|laptop has joined #openstack-meeting19:06
fungithose new images worked out for you then?19:06
clarkbit would be great if https://bugs.launchpad.net/openstack-ci/+bug/1217815 could be updated. I want to say that tripleo still wants to use toci as it will test different things than the upstream integrated tests19:06
uvirtbotLaunchpad bug 1217815 in openstack-ci "Tripleo ci service account in gerrit" [Undecided,New]19:06
pleia2fungi: yes! thank you19:06
clarkbfungi: pleia2 lifeless ^ but I am not sure of all the details19:06
pleia2I'm going through this https://etherpad.openstack.org/p/tripleo-test-cluster - so iteration 1 is completed, and I'm working on 2 now19:07
fungi#link https://etherpad.openstack.org/p/tripleo-test-cluster19:07
*** nachi1 has left #openstack-meeting19:07
pleia2lifeless: I don't know the status on https://bugs.launchpad.net/openstack-ci/+bug/1217815 - any insights?19:07
uvirtbotLaunchpad bug 1217815 in openstack-ci "Tripleo ci service account in gerrit" [Undecided,New]19:07
fungimaybe he's sleeping in the middle of the night for a change19:08
pleia2he's running the tripleo meeting in -alt :)19:08
anteayahe is chairing in the other channel19:08
fungioh, or that :/19:08
pleia2maybe we come back to this bug later/after meeting19:08
pleia2that's all the updates I have19:08
anteayagreat work, pleia219:09
fungiyeah, no worries. i don't think it's a direct action item from this topic, but an update from someone in the bug would be swell19:09
fungi#topic Wsme / pecan testing (sdague, dhellman)19:09
*** openstack changes topic to "Wsme / pecan testing (sdague, dhellman) (Meeting topic: infra)"19:09
lifelesspleia2: clarkb made one.19:10
fungii know a little about this, but would be better if one of them wants to go into detail19:10
pleia2lifeless: bug done?19:10
clarkbI didn't make an account19:10
pleia2saw a the review for this trickle in this morning https://review.openstack.org/#/c/53136/19:10
lifelesspleia2: oh, then mordred did19:10
lifelessclarkb: ^19:10
clarkbthanks I will update the bug19:10
lifelessanyhow, bug can be closed, we have a suitable account.19:10
lifelesstripleo-cd-bot IIRC.19:10
fungiokay, well, in absence of sdague and dhellmann, i'll attempt a tl;dr on the current topic19:11
*** SergeyLukjanov has joined #openstack-meeting19:12
fungibasically, there is a desire to more tightly couple wsme and pecan gating into devstack, so changes to them can avoid breaking the projects which depend on them19:12
*** KC-Wang1 has joined #openstack-meeting19:12
fungisome of it is in progress already... making devstack use the git master branches of those instead of pypi released versions, and adding the devstack/tempest jobs to those projects19:13
*** bklei has quit IRC19:13
sdagueoh, sorry, stepped out for a sec19:13
fungithere is an additional desire to gate them against stable branches of devstack-integrated projects to avoid breaking stable released versions19:13
fungioh! sdague can take over19:13
sdaguewell, I think you are basically completely on target19:14
*** SumitNaiksatam has quit IRC19:14
fungidhellmann was also talking about maybe figuring out how to integrate the unit tests of other projects as part of the gating for pecan and wsme, but that would need a little additional engineering design19:14
*** markmcclain has quit IRC19:15
*** markmcclain has joined #openstack-meeting19:15
sdagueI think that once we have this - https://review.openstack.org/#/c/53136/ we can fix it on the devstack / devstack-gate side19:15
*** bknudson has left #openstack-meeting19:15
sdaguethat will make pecan / wsme part of the big happy family19:15
clarkbI am excited for what comes out of this. Is there any concern that we are massively overengineering the whole thing?19:15
fungi#link https://review.openstack.org/#/c/53136/19:16
fungiprobably special versions of the unit test runner which would munge the requirements and override the target branch (to support backward-compat runs)19:16
sdagueI did however also propose a session about a bigger vision19:16
*** KC-Wang has quit IRC19:16
sdaguehttp://summit.openstack.org/cfp/details/34019:16
fungi#link http://summit.openstack.org/cfp/details/34019:16
fungiexcellent19:16
sdaguebecause I think we might want to build something to more generically attack this for libraries beyond our control19:16
sdaguebut that's summit material19:16
*** bklei has joined #openstack-meeting19:17
*** nadya has joined #openstack-meeting19:17
fungii hope it makes it into the schedule, because i want to talk about it too19:17
sdaguehonestly once https://review.openstack.org/#/c/53136/ is approved, we can probably pull the rest together within a day or two19:17
fungianything else on the current topic then?19:17
*** bklei has quit IRC19:17
sdaguenot from me19:17
clarkbyes19:17
clarkbis the plan to make gating mutual or just one direction? I think one problem that we will run into is openstack breaking wsme19:18
clarkbbut we shouldn't be gating openstack on wsme19:18
clarkbsomething to think about at least19:18
sdagueclarkb: how would openstack break wsme?19:18
*** shakayumi has quit IRC19:18
sdagueI actually think there is a direction flow in dependencies19:18
*** otherwiseguy has joined #openstack-meeting19:19
sdagueso I'm not actually concerned that we could break wsme19:19
*** ozstacker has joined #openstack-meeting19:19
clarkbsdague: if openstack were to continue using deprecated interfaces then wsme can't deprecate them and so on19:19
fungii think this is at least a little better than the horizon/keystone auth plugin where we had openstack depending on not-openstack depending on openstack (thankfully resolved now)19:19
sdaguesymetric gating wouldn't solve that though19:19
clarkbsdague: right I think they are both wrong :)19:20
clarkbbut need to think about it more19:20
sdagueyeh, I think we should do this thing, to solve a problem we know we have, then if we create a new problem, solve that later19:20
clarkbwfm19:20
fungiwfm19:20
fungianything else on the current topic then?19:21
sdagueI think the emergent behavior of these interconnections has shown we often poorly predict the future problems :)19:21
*** shakayumi has joined #openstack-meeting19:21
sdagueI'm good19:21
fungisolving future problems is akin to premature optimization, agreed19:21
fungi#topic New etherpad.o.o server and migration (clarkb)19:21
*** openstack changes topic to "New etherpad.o.o server and migration (clarkb) (Meeting topic: infra)"19:21
clarkbohai19:21
fungithat happened, ja?19:22
clarkbit did19:22
fungiany new fun there?19:22
pleia2it's working great19:22
clarkbwe are now running etherpad.o.o and etherpad-dev.o.o on almost the latest versions of etherpad-lite with the latest nodejs stable release on 2GB nodes using trove as the backend19:22
pleia2clarkb: I do have some bugs in the bug day list that I need your eyeballs on related to this (I bolded your nick in the etherpad)19:23
clarkbpleia2: I will look19:23
pleia2just one for etherpad :)19:23
clarkbbut yes overall the move went smoothly and we did an emergency nodejs upgrade Friday night as well19:23
fungiclarkb: and the old etherpad server still exists for the moment, right?19:23
clarkbyes it does, because it has old DB backups that I didn't want ot have to juggle. I plan on deleting the old servers after the summit19:24
*** huats has quit IRC19:24
fungi#action clarkb decommission old etherpad server eventually (after the summit)19:25
*** dcramer_ has quit IRC19:25
clarkbplease let us know if you see etherpad acting weird, but it seems to have done just fine19:25
fungijust so we don't frget19:25
fungii've been using it fairly heavily for things since the upgrade, no sign of broken19:25
*** shakayumi has quit IRC19:26
fungii wish the etherpad the foundation uses for staff meetings were so nice and responsive as this one19:26
sdaguefungi: their pads > 700 lines?19:26
sdaguethat's been an issue for me on my installation, and a know bug19:26
fungisdague: we need to truncate the main one we use, but almost certainly19:26
*** thomasm_ has quit IRC19:26
sdagueyeh, we rotate out pads every couple of weeks for that reason, keep them < 700 lines19:27
*** cody-somerville has joined #openstack-meeting19:27
fungithough i also discovered that part of the issue i was having with theirs was due to timeouts reaching google analytics (gag)19:27
sdaguealso big +1 for ep_headings add by clarkb :)19:27
*** jlucci1 has quit IRC19:28
sdaguehttps://etherpad.openstack.org/p/icehouse-qa-session-planning - example19:28
clarkbsdague: I like the headings plugin too, wish I had dealt with it sooner :)19:28
sdagueheh19:28
fungi#link https://etherpad.openstack.org/p/icehouse-qa-session-planning19:28
anteayanice19:28
*** ozstacker has quit IRC19:29
fungiare we all set on etherpad talk for the moment? anyone have anything else for that?19:29
*** nkinder has left #openstack-meeting19:29
fungi#topic Third-party documentation editors (fungi)19:30
*** openstack changes topic to "Third-party documentation editors (fungi) (Meeting topic: infra)"19:30
*** SumitNaiksatam has joined #openstack-meeting19:30
fungijust a quick update from a call i had with annegentle and a group of editors from o'reilly press19:30
*** rakhmerov has joined #openstack-meeting19:30
fungithe foundation has a contract, as i understand it, to get one or more of the manuals bookified19:30
fungiso we're trying to figure out a workflow feedback loop between their editors and our authors19:31
fungicurrent plan is that they're going to clone from git branch tip and at the same time the docs program will announce a freeze19:32
*** gyee has quit IRC19:32
fungitentative schedule for the first iteration is to freeze from october 28 through november 519:32
clarkbfungi: what will the pushes back to gerrit look like?19:32
fungithey will publish their edits in a git repo which we can import and turn into a gerrit review19:32
fungithat can either happen manually initially or we can script it19:33
fungii wanted to bring it up here mostly to talk through possible implementation details on our end19:34
*** adalbas has quit IRC19:34
fungithey are open to evolving the process over time as well, so none of this is set in stone19:34
*** rakhmerov has quit IRC19:35
clarkbworth mentioning the reason that they don't use gerrit directly is they haev their own set of tools backed by git for editing things19:35
*** nikhil|afk is now known as nikhil19:35
fungithe main issue we were worried about was merge conflicts, but annegentle felt that the documentation community would be amenable to a periodic freeze on specific documents19:35
clarkbso they will edit in that world then push changes back to us19:35
fungiright19:35
anteayasounds like a very interesting direction19:36
fungiit's called "atlas" but since it's proprietary and we won't need to interact with it (per the current plan) that's somewhat immaterial19:36
clarkbso the freeze period is to avoid merge conflicts? do we think that manually resolving the conflicts will be too difficult?19:36
anteayawill they be joining us in -infra and asking questions?19:36
anteayaso I can recognize them and get a sense of how to help?19:36
fungiclarkb: apparently they feel that the way docbook/xml works, diffs become massively painful to properly resolve merge conflicts on19:37
fungianteaya: probably not, but you never know19:37
clarkbfungi: well, maybe we should be arguing for sane markup >_>19:37
anteayaokay, just if I get a brand new question, it helps to have context19:37
clarkbfungi: but that is a different battle. If the doc team is ok with freezing content I am fine with it19:37
clarkbI think it is a lot easier on them now that they are further ahead of the releases19:38
fungiclarkb: yeah, for the time being i think the desire is to try this out and see where it leads, then adjust if necessary, refine, and semi-automate19:38
clarkbwfm19:38
anteayaI think it is a great idea19:39
fungimy remaining concern is that they heavily use github19:39
fungiit sounds like they're going to want to push to a private github fork (to avoid spiders picking up their edits and making them look official when they're not), so automation will probably mean authenticating to github to pull their patch or patch series, at least at first19:40
clarkbuhm, hmm19:40
dhellmannare they going to want to preserve the history of those imports? or are they going to squash the commits?19:41
fungii'd love to push them in a direction along the lines of pushing directly to gerrit, but that's probably a down-the-road thing since they want to get rolling on this asap19:41
clarkbprivate github repos aren't very open...19:41
clarkband while APL2 doesn't prevent it :/19:41
fungidhellmann: i suspect a squashed commit will be fine in this case since it's work for hire19:41
clarkbmaybe push to a dev branch instead of master? in any case we can let it evolve. I think the important bit is getting something working19:42
dhellmannok19:42
fungiclarkb: yes, my concerns as well. however on the call it sounded like they had existing automation around github (its no more proprietary than their editing system after all) and they need t publish their commits somewhere19:42
clarkbparticularly with the freeze coming up so quickly19:42
*** jlucci has joined #openstack-meeting19:43
fungiso while i don't like the thought of depending on github for this, we're also depending on their proprietary commercial editing services for this work anyway19:43
*** sushils has quit IRC19:44
clarkbfungi: its less the proprietary stuff and more that the dev is closed19:44
*** rongze has joined #openstack-meeting19:44
dhellmannit's open to the dev team, right?19:44
dhellmannI mean the docs team19:44
dhellmannit's just not open to the world?19:44
clarkbI assume it depends on how the repo is configured19:45
clarkbor org, I am not super familiar with github ACLs19:45
dhellmannpresumably the doc folks are going to need to send them changes19:45
dhellmannbut in any case, the publishing toolchain is going to turn into a black box at some point, so I'm not sure it matters whether github is involved or not19:45
dhellmannusing it should actually  make it easier to have a few people with access to pull changes back out19:46
fungithe end result will land in gerrit. i don't think the interim state where it happens to be temporarily published to $some_proprietary_system will necessarily be accessible except to the editors at o'reilly and automation or whoever's grabbing the patch to stuff into gerrit19:46
dhellmannand put them into our open system19:46
dhellmannhow will they be handling copyedits?19:46
*** thomasm has joined #openstack-meeting19:46
*** thomasm is now known as Guest5616919:47
fungiheh. i live with a copyeditor and i still don't understand your question ;)19:47
fungiiterative work?19:47
dhellmannyes19:47
fungithe idea is that by the end of the freeze their change is reviewed and merged19:48
dhellmannthe o'reilly editors and compositors are going to want to make changes to the text (typos, phrasing, formatting, whatever)19:48
*** sushils has joined #openstack-meeting19:48
dhellmannmerged into our upstream repo?19:48
fungiyes19:48
*** asalkeld has quit IRC19:48
*** rongze has quit IRC19:48
fungiand then the document is unfrozen and docs editors go into authorship phase for a period before the next freeze19:49
fungiat which point o'reilly updates their clone and starts editing again19:49
dhellmannso oreilly will work in the private repo and something/one will push the changes back upstream19:49
dhellmannok, I think I've got it19:49
fungiright19:49
fungithis way we can reintegrate their edits19:50
dhellmannok, this sounds better than what I had to go through with my book :-)19:50
fungii can only imagine19:50
dhellmannI still have a bunch of latex files with changes I need to merge by hand. So I'm +1 on this plan. ;-)19:50
clarkbYa I think it will work out and the proposed plan seems like a good place to start. I am just brainstorming around the trouble spots :)19:50
fungianything else on this? i think dhellmann wanted to come back to pecan/wsme testing during the open discussion portion of the meeting19:50
fungiand we're running tight already19:51
*** btorresgil has quit IRC19:51
dhellmannI don't have much19:51
fungi#topic Open discussion19:51
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:51
fungiand before i forget19:51
fungi#action jeblair move tarballs.o.o and include 50gb space for heat/trove images19:51
pleia2bug day continues, don't fall asleep :) https://etherpad.openstack.org/p/cibugreview-october201319:51
pleia2at the top of the file I included a link to New bugs that should be triaged19:52
clarkbquick FYI I upgraded logstash to 1.2.1 and elasticsearch to 0.90.3 yesterday after a week of planning :) and nothing seems to have fallen over. These upgrades better future proof us against the direction es and logstash are moving19:52
dhellmannI just wanted to address the bi-directional gating (I think that's not needed) and mention that we're also going to add test config to pecan and wsme to let us test locally (in addition to the gates)19:52
pleia2started the day with 190 bugs, down to 185, I'm hoping we can do better19:52
clarkbpleia2: I am slowly working through that :) I am amazed at how much harder this is when jeblair, mordred, and jog0 are busy with other stuff19:52
anteayagood work on bugs pleia219:52
*** weshay has quit IRC19:53
pleia2clarkb: yeah, jeblair always did a lot :)19:53
anteayaclarkb: did anything on this https://etherpad.openstack.org/p/elasticsearch-optimization-suggestions help or was it just noise?19:53
clarkbdhellmann: cool thanks19:53
dhellmannryan has some changes in process to let us test the openstack incubated and integrated projects that use pecan already19:53
fungiyeah, i feel bad that i've not contributed as much to today's bugtrawl as i had wanted19:53
anteayaI couldn't pass up three experts on elasticsearch19:53
clarkbanteaya: a lot of it was stuff that I already sorted out19:54
anteayak19:54
anteayathat's good19:54
*** asalkeld has joined #openstack-meeting19:54
clarkbanteaya: I think a lot of people don't quite understand the restrictions we have when it comes to available hardware, security model, and the amount of data we want to index19:54
anteayayes19:54
anteayathat was what I kept hitting, because I don't have all that info either19:55
anteayajust small pieces19:55
*** weshay has joined #openstack-meeting19:55
clarkbanteaya: I can update that etherpad at some point for completeness with things like we already do X and can't do Y for reason Z19:56
anteayasure19:56
anteayasince honza and alexb also have that url19:56
anteayaso may respond if they have something to respond to19:56
clarkbcool19:56
clarkbfungi: we forgive you, I may roll bug stuff over into tomorrow depending on how the rest of today goes19:57
clarkb:)19:57
pleia2oh, I owe some nodepool documentation updates for running a dev version, need to bootstrap sphinx on the nodepool repo19:57
*** SergeyLukjanov is now known as _SergeyLukjanov19:57
fungioh, don't forget i'm semi-afk the next couple days at the all things open conference19:57
fungibut back in full force on friday of course19:57
anteayacool, happy open conference19:57
clarkbhave fun19:57
anteayais that in raliegh?19:58
fungi(that rhymed!)19:58
*** _SergeyLukjanov has quit IRC19:58
fungiyeah19:58
anteayahence why mordred is going there after chicago19:58
anteayagreat meeting, fungi19:59
*** ozstacker has joined #openstack-meeting19:59
pleia2thanks fungi19:59
fungia-the-a-the-a-the-a-that's all, folks!19:59
fungi#endmeeting19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:59
openstackMeeting ended Tue Oct 22 19:59:55 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-10-22-19.01.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-10-22-19.01.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-10-22-19.01.log.html20:00
clarkbfungi: thanks20:00
*** luis_fdez has joined #openstack-meeting20:01
*** HenryG has quit IRC20:01
*** pcm_ has quit IRC20:03
ttxPSA: No TC meeting this week20:03
*** jcoufal has quit IRC20:03
*** changbl has quit IRC20:04
*** ozstacker has quit IRC20:05
anteayattx does TC meet next week?20:05
*** julim has quit IRC20:05
*** vkmc has quit IRC20:05
ttxanteaya: ..maybe20:06
anteayaokay, I will stand by20:06
*** topol has quit IRC20:08
*** SergeyLukjanov has joined #openstack-meeting20:08
*** SergeyLukjanov has quit IRC20:09
*** scott__ has quit IRC20:10
*** dolphm has quit IRC20:11
*** jhenner has quit IRC20:14
*** jlucci has quit IRC20:14
*** beagles has quit IRC20:17
*** sarob has joined #openstack-meeting20:18
*** bgorski has quit IRC20:19
*** changbl has joined #openstack-meeting20:19
*** zul has joined #openstack-meeting20:19
*** sandywalsh has quit IRC20:20
*** nadya has quit IRC20:25
*** stevemar has quit IRC20:26
*** dcramer_ has joined #openstack-meeting20:27
*** ociuhandu has joined #openstack-meeting20:29
*** vipul-away is now known as vipul20:31
*** rakhmerov has joined #openstack-meeting20:31
*** asalkeld has quit IRC20:32
*** jtomasek_ has joined #openstack-meeting20:33
*** dvarga has quit IRC20:34
*** ayoung has quit IRC20:34
*** rakhmerov has quit IRC20:36
*** jtomasek has quit IRC20:36
*** doron_afk has joined #openstack-meeting20:41
*** galstrom_zzz is now known as galstrom20:41
*** ociuhandu has left #openstack-meeting20:42
*** radez is now known as radez_g0n320:42
*** gyee has joined #openstack-meeting20:43
*** dcramer_ has quit IRC20:43
*** galstrom is now known as galstrom_zzz20:44
*** rongze has joined #openstack-meeting20:45
*** Guest56169 has quit IRC20:45
*** ozstacker has joined #openstack-meeting20:46
*** vuil has joined #openstack-meeting20:49
*** vuil has quit IRC20:49
*** rongze has quit IRC20:50
*** vijendar has quit IRC20:51
*** changbl has quit IRC20:52
*** asalkeld has joined #openstack-meeting20:52
*** litong has quit IRC20:53
*** SergeyLukjanov has joined #openstack-meeting20:53
*** mestery has quit IRC20:53
*** julim has joined #openstack-meeting20:54
*** mestery has joined #openstack-meeting20:54
*** vkmc has joined #openstack-meeting20:55
*** gabrielhurley has joined #openstack-meeting20:55
*** dolphm has joined #openstack-meeting20:55
*** julim has quit IRC20:55
*** Guest56169 has joined #openstack-meeting20:56
*** Guest56169 has quit IRC20:56
*** ozstacker has quit IRC20:56
*** atiwari has quit IRC20:58
*** mestery has quit IRC20:58
*** sarob has quit IRC20:59
*** gyee has quit IRC21:00
ttxhm.21:00
*** markpeek has quit IRC21:00
ttxdhellmann, dolphm, notmyname, jd__, markwash, jgriffith, russellb, stevebaker, gabrielhurley, markmcclain, dtroyer, SergeyLukjanov, annegentle, sdague, lifeless, devananda, hub_cap, jeblair, kgriffs: around ?21:01
markwasho/21:01
sdagueo/21:01
stevebaker\o21:01
russellbo/21:01
notmynamehere21:01
*** spzala has quit IRC21:01
*** markpeek has joined #openstack-meeting21:01
*** jcoufal has joined #openstack-meeting21:01
devananda\o21:01
dtroyero/21:01
dolphmo/21:01
eglynno/ (deputizing for jd__ ... he's on vacation this week)21:01
SergeyLukjanovo/21:01
gabrielhurley\o21:01
*** Guest56169 has joined #openstack-meeting21:01
hub_caphowdy21:01
lifelessttx: hi21:01
soren>-|o21:01
ttx#startmeeting project21:01
openstackMeeting started Tue Oct 22 21:01:56 2013 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: project)"21:01
openstackThe meeting name has been set to 'project'21:02
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:02
ttxA special meeting today, focused on the design summit scheduling21:02
lifelessdum dum dum duuuuuuh21:02
russellbevery meeting is special.21:02
annegentlehere21:02
ttxBut first we'll do a quick release postmortem21:02
lifelesslike raindrops falling from the sky21:02
ttx#topic Havana release postmortem21:02
*** openstack changes topic to "Havana release postmortem (Meeting topic: project)"21:02
ttxSo... last week we released Havana21:02
ttxIn general I think it went well21:02
ttxAll processes worked as planned21:03
ttxWe were a little too late for my taste21:03
ttxi.e. we didn't switch to anal-rentention mode early enough21:03
*** mestery has joined #openstack-meeting21:03
ttxI intend to discuss ways to mitigate that during the release schedule session in HK21:03
jgriffithhey21:03
eglynnalso IIRC seemed to be slowness/breakages creeping into the gate towards the end21:03
russellbseemed to happen < 1 week before release?21:03
*** changbl has joined #openstack-meeting21:03
*** gyee has joined #openstack-meeting21:03
eglynn(which slowed down the merge rate significantly)21:04
*** pdmars has quit IRC21:04
*** cody-somerville has quit IRC21:04
ttxrussellb: we did some RC2s two weeks before final that were still a bit too significant21:04
sdaguewell the breakages were all bugs in core projects, it did take a while to nail down those races21:04
annegentlePeople who followed prior releases of OpenStack said these release notes were good.21:04
ttxFor a primer you can read http://fnords.wordpress.com/2013/10/18/getting-to-havana/21:04
annegentleI can't take credit for them, but docs writers did some real digging to compile those.21:04
annegentlewith the ptls21:05
ttxI think we lost a week at the beginning recovering from the intense feature freeze week21:05
*** julim has joined #openstack-meeting21:05
russellbannegentle: yep i got a lot of help, it was great21:05
ttxso we either need to make it less intense, or add a week21:05
russellbttx: +1, i was fried after that21:05
annegentleI'm not sure you can decrease the intensity, deadlines kind of do that to humans?21:05
*** sacharya has quit IRC21:05
dhellmanno/21:06
eglynnre. lateness and heavy RCs, reasonable flexibility was shown with FFEs IMHO21:06
ttxDo you have any issue with the release process, or another FAIL to report while you still remember it ?21:06
sdagueright, so move the freeze back a week. The mad rush definitely burns up reviewers21:06
eglynn... said as a benificiary of one of those FFEs ;)21:06
ttxsdague, russellb: that's one of the options yes21:06
*** KC-Wang1 has quit IRC21:07
gabrielhurleyfrom the Horizon side, I'd just like to encourage PTLs of other projects to communicate their "banner features" for a release early and often to the Horizon team so we can plan our integration accordingly21:07
sdaguettx: I think my only regret is we didn't get parallel testing in until right near H3, and it shook out a lot of bugs, but would have been nicer earlier21:07
markwashttx: one improvement, we need to get you a desk so you don't have to fill out your checklists on rocks any longer21:07
*** KC-Wang has joined #openstack-meeting21:07
russellbgabrielhurley: good point21:07
*** yamahata has joined #openstack-meeting21:07
annegentlegabrielhurley: +121:07
*** lblanchard has quit IRC21:07
*** julim has quit IRC21:07
ttxgabrielhurley: we might change the format of this meeting to make that more efficient21:07
gabrielhurleyttx: any changes you think would help are welcome21:08
russellbi guess that could help docs, too21:08
ttxgabrielhurley: as in, we might just sync most of the release status offline at some other pre-arranged hour21:08
*** mrunge has quit IRC21:08
stevebakergabrielhurley: actually same goes for heat, regarding banner features and integration21:08
ttxthen use the meeting to communicate about cross-project21:08
ttxand make that part short21:08
gabrielhurleystevebaker: +121:08
dolphmand python-openstackclient21:09
gabrielhurleythis really goes for all the top-of-stack programs21:09
*** IlyaE has joined #openstack-meeting21:09
ttxmost of what happens in this meeting could happen in a 1:1 discussion between me and ptl21:09
annegentlerussellb: yep sure would21:09
ttxand then the critical need for cross-project communication is a bit buried in it21:09
annegentlettx: I like that reformat of the project meeting21:09
sdaguettx: +121:09
russellbyeah, sounds interesting21:09
ttxannegentle: I intend to polish a proposal and present it in the release schedule/process session21:09
gabrielhurley+1, I look forward to this proposal21:10
russellbttx: know when that's going to be yet?21:10
ttxno point in me preparing remarks all day and pasting them in channel while we have everybody's attention21:10
ttxrussellb: probably last day, before last slot21:10
ttxlast slot would be "the future of design summits"21:10
russellbah, k21:11
russellbso 2nd to last slot21:11
*** julim has joined #openstack-meeting21:11
ttxOK... we also have a number of known issues to backport to stable/havana21:11
ttxI know of bug 124285521:11
uvirtbotLaunchpad bug 1242855 in keystone "Removing role adds role with LDAP backend" [Critical,Fix committed] https://launchpad.net/bugs/124285521:11
ttxAny other really embarrassing bug that crept in ?21:11
annegentlettx: I have a question about bugs post-release21:11
ttxas in, if it had been discovered last week you would have asked for a new RC to cover for it21:12
ttxannegentle: ask21:12
annegentlettx: do you mark bugs that didn't get fixed in havana as icehouse targeted? Or untarget them completel?21:12
*** markvan has quit IRC21:12
annegentlettx: looking at nova, I think you mass-target to next-release21:13
ttxannegentle: err... what do you mean by icehouse-targeted ?21:13
annegentlettx: Milestone21:13
annegentlettx: sorry21:13
ttxicehouse1-milestone-targeted ?21:14
annegentlettx: right21:14
ttxyou mean, bugs that were havana-rc-potential that didn't get fixed ?21:14
annegentlettx: looking at https://wiki.openstack.org/wiki/BugTriage, it doesn't say if any particular thing happens at release21:15
ttxnothing particular happens at release21:15
*** huats has joined #openstack-meeting21:15
ttxyou can target some of the deferred fixes to your next milestone21:15
ttxbut that would be a manual thing21:15
annegentlettx: and looking at https://wiki.openstack.org/wiki/Bugs it looks like a judgement call, Milestone21:15
ttxthe only thing I do is untag havana-rc-potential and make them havana-backport-potential21:16
annegentlettx: ok, so you're not using the launchpad API for moving bugs around?21:16
ttxannegentle: no21:16
annegentlettx: got it, thanks21:16
*** sarob has joined #openstack-meeting21:16
ttxIf you have embarassing bugs in havana, would be great to document them all in the Release Notes so that the early upgraders know about all of them.21:16
annegentle#link https://wiki.openstack.org/wiki/ReleaseNotes/Havana21:17
ttxand yes, bug 1242855 counts as embarassing :)21:17
*** jhenner has joined #openstack-meeting21:17
uvirtbotLaunchpad bug 1242855 in keystone "Removing role adds role with LDAP backend" [Critical,Fix committed] https://launchpad.net/bugs/124285521:17
ttxanything to add about havana ?21:17
gabrielhurleyI find that bug hilarious :-)21:17
annegentlegabrielhurley: any specific examples for banner features?21:17
* dolphm ++21:17
ttxgabrielhurley: hiilarious bugs are also release notes material :)21:17
*** jtomasek_ is now known as jtomasek21:18
russellbi don't think i have anything hilarious, or severely depressing, but I think that's good21:18
gabrielhurleyannegentle: the one that brought this to the forefront of my mind in Havana was miscommunication around the VPNaaS and FWaaS between myself and the Neutron guys that led to some FFEs and long nights for folks to get them in21:18
gabrielhurleythey did a great job getting that done, btw21:18
gabrielhurleyprops to the devs who worked on those21:18
ttxrussellb: that would be one of the first release without a OMG bug discovered +1week21:18
gabrielhurleybut we shouldn't have needed to do that21:18
markmcclaingabrielhurley: +1 those sub teams did a great job21:18
ttxOK, time to talk Hong-Kong21:19
annegentlegabrielhurley: good, I think you're ahead of docs there, people do seem confused about VPNaaS and FWaaS docs21:19
ttx#topic Design Summit scheduling21:19
eglynnwhat's the deadline for PTLs to review and reject/accept design session proposals?21:19
*** openstack changes topic to "Design Summit scheduling (Meeting topic: project)"21:19
ttxeglynn: We are trying to produce a schedule before the end of the week.21:19
ttxDoes that sound doable for everyone ?21:19
sdaguegood for me21:19
SergeyLukjanovfor me too21:19
annegentlesure21:20
ttxThen we use the following days to fix conflicts21:20
russellbgood for me, mostly done (in an etherpad, not on the site yet)21:20
eglynnttx: well jd__ is on vacation this week, not sure how off-grid he is though21:20
ttxeglynn: all week ?21:20
ttxdamn the french with all their vacation time21:20
sdagueheh21:21
eglynnttx: hmm, not 100% sure on that, may only be the the 1st half of the week21:21
annegentleoui oiu21:21
eglynnhe's defo out tmrw also21:21
annegentlewah21:21
*** zul has quit IRC21:21
ttxeglynn: if not I could give you the keys if necessary21:21
lifelesshow do we check conflicts?21:21
eglynnttx: fair enough21:21
lifelessI mean, do I click 'push to sched' and then ???21:21
*** weshay has quit IRC21:21
russellblifeless: manually and then hope for the best i think21:21
ttxlifeless: we can anticipate them using comments that may have been left by people. Otherwise we just post and wait for complaints21:22
sdaguettx: so how soon will things be in place for us to start pushing things out? I'm mostly done on our schedule, and it would be good to have it out there before the QA meeting on Thurs so we can adjust21:22
lifelessrussellb: sure, but I mean in a little more detail...21:22
*** joesavak has quit IRC21:22
eglynnBTW is it clear yet approx. how many sessions will be available to each track?21:22
eglynn(modulo horse-trading or whatever ...)21:22
lifelesseglynn: nowhere near enough!21:22
ttxlifeless: also we can't please everyone, so pleasing all the PTLs as a first step is good21:22
dhellmanncan we push to sched more than once, if we do change the schedule?21:22
*** luis_fdez has quit IRC21:22
lifelessthere needs to be a PTL FAQ for this I think ;>21:22
ttxsdague: we need to solve the sched question first. I'll come to it21:22
russellbdhellmann: yep (or i was able to last time)21:22
ttxEveryone: Do you have sessions in your "topic" that you think belong to another ?21:22
dhellmannrussellb: cool, I expected as much but wanted to be sure #n00b21:23
notmynamedhellmann: yes, and in the past you can update the schedule even during the event21:23
jeblairttx: yes21:23
devanandaI had one, already re-proposed it to Ceilometer21:23
*** yamahata has quit IRC21:23
stevebakernot really21:23
sdaguettx: I mostly kicked those out with comments21:23
markwashttx: one maybe21:23
russellbjust some that we recommended to unconference, mostly21:23
markwash(http://summit.openstack.org/cfp/details/220)21:23
dhellmannttx: I've already dealt with that, so not any more21:23
lifelessttx: I do21:23
ttxjeblair: you can use this meeting to trade21:23
ttx(or try to)21:23
SergeyLukjanovttx, nope21:23
jeblairmarkmc is not around; is there an oslo ptl proxy here?21:24
dhellmannI'm here :-)21:24
sdaguedhellmann's the ptl now :)21:24
ttxjeblair: that would be dhellmann21:24
dolphmhaha21:24
jeblairgah21:24
jeblairwrong wiki page.  ;)21:24
dhellmannnot a big deal21:24
lifelessmarkmcclain: ttx: http://summit.openstack.org/cfp/details/31421:24
dhellmannoh, which one do I need to update?21:24
lifelessmarkmcclain: I'm gonig to chat with snaiksnat once my run of meetings are done21:25
markmcclainok21:25
ttxlifeless: you scheduled it so i suspect you found room for it ?21:25
markwashrussellb: do you have any interest in this? http://summit.openstack.org/cfp/details/220 I think the right technical solution is a nova change rather than a glance change. I'm okay with giving it a glance slot but would love to have relevant nova folks there21:25
jeblairdhellmann: if i deep link to http://summit.openstack.org/cfp/details/124 can you see that?21:25
dhellmannrussellb: I suggested that boris-42 submit some of the db changes he wants to make in the nova track, did you get those?21:25
lifelessttx: I'm oversubscribed by about 3:1 :P21:25
dhellmannjeblair: yes21:25
jeblairi never know what access people have in the summit app21:25
jeblaircoll21:25
dhellmannjeblair: reading21:25
russellbmarkwash: we'd probably reject it as something we could probably cover on the ML21:25
dolphmjeblair: ++21:25
sdagueactually, russellb, this one seems mostly about nova unit tests - http://summit.openstack.org/cfp/details/31721:25
lifelessttx: but we'll muddle through21:25
boris-42dhellmann what?)21:26
russellbdhellmann: didn't get that, no, i don't think21:26
ttxlifeless: welcome to hell21:26
dhellmannjeblair: oh, man, why rebuild chef, puppet, etc.?21:26
boris-42dhellmann we have only one DB session21:26
jeblairdhellmann: and http://summit.openstack.org/cfp/details/31821:26
lifelessttx: heh, so to me the value is not in the discussion but in the face to face21:26
dhellmannboris-42: maybe roman was going to do it? we agreed some of the sub-topics needed a different audience21:26
lifelessttx: plans don't survive more than a few weeks post summit anyhow21:26
dhellmannboris-42: let's discuss later, if we need to21:26
lifelessttx: but thats a meta discussion21:26
russellbdhellmann: yeah, though i suppose it applies to some other projects ... but don't think I'd give it nova track time.  it's not terribly controversial or anything, and is already well in progress21:26
boris-42dhellmann Okay21:26
jeblairoh! i can change the topic by clicking on it in the list21:27
dhellmannrussellb: ok, I thought the soft delete thing in particular might spark some discussion, since it wants to have nova depend on ceilometer21:27
jeblairso the ui paradigm is 'click on the hyperlink for the aspect of the proposal you want to change'21:27
lifelessmarkmcclain: so #openstack-neutron after this I guess :)21:27
*** twoputt_ has quit IRC21:27
*** twoputt has quit IRC21:27
*** thingee has joined #openstack-meeting21:27
ttxsdague: you're not suposed to come up with exciting titles, otherwise you'll attract the crowd (re: "Preemptively Integrate the Universe")21:27
markwashrussellb: hmm. . this is just sort of a long-term standstill so far :-(21:27
sdagueheh21:27
sdaguewell I'll let jeblair make the title boring21:28
russellbdhellmann: oops, that was meant for sdague21:28
dhellmannjeblair: I guess http://summit.openstack.org/cfp/details/318 could fit with oslo21:28
russellbdhellmann: don't think i've seen a session related to what you're saying21:28
markmcclainlifeless: sounds good21:28
gabrielhurleyttx: where would you suggest that up-and-coming Programs (I'm specifically looking at the proposed UX Program) get time allotted to them in the scheduling process?21:28
sdaguerussellb: heh, yeh honestly, I think 317 doesn't really need a session21:28
dhellmannrussellb: I'll leave it for boris-42 to submit21:28
russellbsdague: agreed21:28
russellbdhellmann: ok21:28
sdaguebut I figured I'd let you know before I punted it entirely in case you disagreed21:28
russellbboris-42: if you are submitting anything, please do it asap21:28
russellbsdague: sure, appreciated21:28
boris-42russellb okay21:28
ttxgabrielhurley: they don't, unless they are invited by an existing topic -- we can't provide room for all wannabees and the line has to be drawn somewhere21:29
boris-42russellb 30 min ok?21:29
russellbsdague: unless you think there's some controversy or important discussion to have around it21:29
russellbboris-42: from now?  yes21:29
lifelessttx: so I clicked on push to sched21:29
dhellmannjeblair: did you want me to take http://summit.openstack.org/cfp/details/124 over? I don't expect I would approve of a system like that21:29
boris-42russellb yeah from now-)21:29
ttxgabrielhurley: there is an unconference room for random things21:29
jeblairdhellmann: 318 bumped to oslo21:29
lifelessttx: and it said21:29
jeblairdhellmann: let's ask lifeless21:29
ttxlifeless: that should fail21:29
lifelessWould have pushed to sched.org:21:29
sdaguerussellb: not really, it's just a getting stuff done thing I think21:29
lifelessttx: ok21:29
gabrielhurleyttx: I see. Way to make me choose, since http://summit.openstack.org/cfp/details/111 is submitted to the Horizon track...21:29
jeblairlifeless: want http://summit.openstack.org/cfp/details/124 ?21:29
russellbsdague: ok agreed21:29
ttxlifeless: until the sched API key field is filled21:29
lifelessttx: so I'm confused about how we collaborate ;P21:29
*** nermina has quit IRC21:29
sdaguelifeless: via IRC, like always :)21:29
ttxlifeless: we need to solve the one sched / two sched question first21:29
*** twoputt has joined #openstack-meeting21:29
*** twoputt_ has joined #openstack-meeting21:30
*** bpb has quit IRC21:30
jeblairdhellmann, lifeless: because i'm not likely to accept 124 in infra)21:30
ttxlifeless: then I'll enter the corresponding sched.org APi key21:30
lifelessjeblair: sheese yeah.21:30
russellbyeah doesn't seem infra related really, heh21:30
dhellmannjeblair: yeah, it doesn't fit there21:30
ttxlifeless: havign a "private" sched would let us push early, push often21:30
lifelessjeblair: uhm, I think there are good aspects to having live configuration21:30
lifelessjeblair: but it's a) not openstack-infra21:30
sdaguejeblair: any idea who the proposer for 124 is? honestly the last time that came up on the ML there was some talk about it being a keystone thing21:31
russellbooh ooh, what's b)21:31
lifelessjeblair: and b) not a library problem per se - there's lots of consequences that that proposal doesn't think about21:31
lifelesslike graceful operation in mixed version clouds21:31
dolphmsdague: joe brue21:31
dolphmbreu*21:31
jeblairlifeless: oh, yeah, agreed.  i'm not evaluating the merits.  i'm just saying it's not infra.21:31
*** rackerjoe has joined #openstack-meeting21:31
*** rakhmerov has joined #openstack-meeting21:31
russellbcan reject it saying "consensus is we hate it"21:31
lifelessdhellmann: oslo is as good a place as any; it's not a deployment problem per se: I think oslo is a decent place to start the discussion21:32
devanandajeblair: reminds me of issues with the central config mgmt of NDB cluster ...21:32
lifelessdhellmann: deployment can certainly inform the discussion (but so can all the API services)21:32
ttxAnother question: is there anyone who has TOO MANY SLOTS and wants to give them out to their neighbour ?21:32
dhellmannlifeless: ok, I'm running out of space but we'll see21:32
lifelessttx: HAHAHAHAHAHAHAHAHAHAHAHA21:32
ttxlifeless: last summit we had Glance and Horizon giving some slots out :)21:32
lifelessttx: http://summit.openstack.org/scheduling/13 btw21:32
devanandadevstack has only 2 proposals?21:33
sdaguedevananda: it only has 2 slots21:33
devanandaah :)21:33
dhellmannjeblair: I can't edit 124, but if you want to put it in oslo I'll deal with it21:33
ttxlifeless: busy :)21:33
jeblairdhellmann: ok, will punt to you for now then.  you can punt it to lifeless later i guess.  :)21:33
ttxlifeless: you can edit the common title of those merged sessions fwiw21:33
dhellmannjeblair: hehe21:33
ttxlifeless: see "Help" at the bottom of the page21:33
lifelessdevananda: where do you see devstacks sessions ?21:34
sdagueit's conference hot potato21:34
devanandalifeless: http://summit.openstack.org/ and click 'topic' to sort21:34
*** dkranz has quit IRC21:34
rackerjoerussellb: http://summit.openstack.org/cfp/details/124 would probably make more sense in oslo and not infra21:34
jeblairrackerjoe: it just got moved to oslo21:34
rackerjoecool21:34
jeblairrackerjoe: (for consideration, not approved)21:35
rackerjoejeblair: understood21:35
* ttx likes the session trading fair21:35
lifelessdevananda: thanks21:35
dhellmannrackerjoe: I'll see if I can find space for it, but I was already full21:35
devanandaeglynn: since jd__ isn't here, i'd like to point out http://summit.openstack.org/cfp/details/19721:35
devanandaeglynn: moved from ironic track after talking offline with jd__ about it21:36
devanandaeglynn: at the time, you guys still had some free slots :)21:36
*** rakhmerov has quit IRC21:36
eglynndevananda: yep, I noticed that, we definitely need to discuss those topics in detail21:36
devanandacool21:36
*** jhenner has quit IRC21:36
eglynndevananda: (so it were up to me, that would be a shoo-in ...)21:36
lifelessttx: thanks!21:37
devanandarussellb: anything in the nova track on baremetal? (i'm skimming right now)21:37
*** vipul is now known as vipul-away21:37
*** zehicle_at_dell has joined #openstack-meeting21:37
ttxPlease continue the session trading fair, but we'll address the question of one or two scheds in parallel21:37
ttx#topic Separate or same sched.org ?21:37
russellbdevananda: nothing21:37
*** openstack changes topic to "Separate or same sched.org ? (Meeting topic: project)"21:37
jeblairttx: #vote separate21:38
ttxWe need to decide this ASAP, since we want to start pushing stuff before the end of week21:38
russellb#vote separate21:38
sdague#vote separate21:38
dhellmann#vote separate21:38
stevebaker#vote separate21:38
ttxSo far, 9 of you said they preferred 2 scheds, and 3 of you preferred one (notmyname, annegentle, SergeyLukjanov)21:38
dolphm#vote separate21:38
markwash#vote separate21:38
gabrielhurley#vote separate21:38
dtroyer#vote separate21:38
eglynn#vote separate21:38
ttx1021:38
hub_cap#vote separate21:38
ttx1221:38
annegentle#vote oneschedtorulethemall21:38
devananda#vote separate21:38
jgriffith#vote separate21:38
jeblairannegentle: why rule only the mall?21:38
lifelessok http://summit.openstack.org/scheduling/13 seems sanish now21:39
SergeyLukjanov#vote oneschedtorulethemall21:39
annegentlejeblair: hee hee21:39
lifeless#vote separate21:39
dolphmjeblair: annegentle: castle?21:39
gabrielhurleyjeblair: that's where the cinnabon is21:39
ttxSergeyLukjanov, annegentle, notmyname: would separate scheds work for you, or you prefer to die before we do it ?21:39
ttxannegentle voted separate above21:39
notmynamewhy separate? only to discourage looky-loos from coming by? isn't the whole point to have users and devs come together?21:39
russellbdevananda: you want to lead one?  could do it on Friday, when we're doing other hypervisor sessions ... up to you.  don't mind not having it if nobody wants to talk about it ...21:39
*** vipul-away is now known as vipul21:39
lifelessnotmyname: not 5000 of them21:39
notmynamettx: yes, we should have either separate or a unified sched21:39
russellbdevananda: maybe it makes sense that all the relevant chat is about Ironic21:39
dolphmlifeless: not sure who that link was intended for, but i get a 40321:40
SergeyLukjanovttx, sure, it'll work but it doesn't look very useful for attendees21:40
*** davidhadas has quit IRC21:40
lifelessdolphm: its the deployment schedule, I don't know who can look at it21:40
*** Guest56169 has quit IRC21:40
devanandarussellb: i think it makes sense to keep it all in ironic, and i've only got one or two to merge so far21:40
russellbdevananda: OK, sounds good21:40
lifelessdolphm: ttx: if only ttx + me can, I think that suggests a summit bug21:40
devanandarussellb: with the plan of 'stop adding things to noa-baremetal and deprecate it', i think it 's fine not to have a sessiona bout it21:40
russellbdevananda: ack21:40
dhellmannnotmyname: having separate schedules does not in any way prevent people from coming to the summit sessions, but it does make it easier for ATCs to find summit sessions21:41
annegentleI won't fight long or hard for it but I hate to ask that much work of people this late. It's a known problem, we try to solve it with different solutions, why rush around this week on a second sched.org21:41
ttxnotmyname: benefits for separate is: weeding out people, abilityt o use colors to difefrentiate design summit topics, and ability to push schedule early for final tweaking without messing with the "official" one21:41
*** MarkAtwood has joined #openstack-meeting21:41
dolphmmore summit.openstack.org pages need more read-only visibility21:41
notmynamedhellmann: hmm...I didn't think the ATC discovery issue was the problem being solved21:41
lifelessdevananda: we've got a couple of small things still to go, but then it really should be stoppable.21:41
ttxnotmyname: drawback being obviously having to juggle21:41
dhellmannttx: can we not use separate colors if we have a single sched?21:41
devanandalifeless: bug fixes notwithstanding :)21:41
sdaguedhellmann: you run out of useful colors pretty quick21:42
dolphmdhellmann: can, but colors alone won't be effective21:42
ttxdhellmann: that would make a lot of undistinguishable colors21:42
lifelessdevananda: supporting ephemeral partitions for instance; arguable on the wire but really need it :)21:42
devanandaand some of us don't see colors the same way ....21:42
lifelesswhat are colours ?21:42
sdaguealready 18 used on - http://openstacksummitnovember2013.sched.org/21:42
dolphmttx: i did like the "warm colors for technical topics, and cool colors for everything else" thing you suggested21:42
ttxsdague: that would make 38 colors21:42
annegentleyeah I think solving the colors issue just for ATCs is a LOT of work for just colors and just ATCs21:42
lifeless /lots/ of people are partially color blind21:42
dolphmbut everyone will quickly look past that21:42
dolphmlifeless: +++21:42
* russellb doesn't feel *that* strongly ... just want to make sure we have the right people, and more importantly, not the wrong people in the room21:43
russellbso if a separate sched helps that, then +++21:43
sdaguehonestly, the big issue is what we saw with nova on day one last year21:43
devananda++ not the wrong people ...21:43
annegentlettx: have you re-evaluated the time sink a second sched.org is and come up with it's really not bad?21:43
russellbbecause it can seriously kill productivity21:43
lifelessthere will be about 500 colour blind people in HK21:43
markwashoptimize colors for tetrachromats21:43
ttxlifeless: yes, only admins and topic leads can see the scheduling screen21:43
devanandarussellb: it wasn't jsut on day one ...21:43
russellbi really don't see why it's painful to have a separate21:43
russellbdevananda: ++21:43
ttxannegentle: it's not really long to set up21:44
* notmyname will use whatever is provided21:44
ttxannegentle: especially if you borrow the artwork from the first one21:44
ttxannegentle: there is a cost though21:44
lifelessso there are many people that are not actually interested in directly contributing to the design work21:44
lifelessthey are usually first-time attendees - 2.5K *new* folk this time21:44
lifelessthe challenge isn't 'keep people out' it's - help the several thousand new attendees get to things that actually help them21:44
ttxsdague: the space in HK is physically separated from the conference, requires a "full access" pass and the design summit starts on the same day as the conference, so I don't expect that many bystanders21:45
sdaguedo we know what the physical layout is going to be?21:45
russellbcost of 2nd sched <<<<< cost of disrupted sessions by having the room full of the wrong people21:45
notmynameI don't really think it's an argument worth having. I'd prefer a unified schedule for the appearance of unity, if nothing else. I'll use whatever, and it seems that the majority wants separate schedules21:45
ttxphysically as in 500 meters away21:45
* notmyname is used to being in the minority ;-)21:45
lifelessttx: wow21:45
markmcclainsdague: layout isn't really important… its the titles and topics that attract21:45
ttxlifeless: not the same building, afaik21:45
* hub_cap converts that to ft21:45
devanandattx: nice. except for when we need to run between them due to scheduling conflicts ;)21:45
annegentlettx: ok if it's really not hard, it's worthwhile to try to somewhat obfuscate the ATC schedule, but I worry about our "open" claim being a bit disingenous21:45
dolphmwith two schedules, i'm still slightly worried that people will come across the "wrong" schedule for them21:45
dhellmannthis second sched won't be private or hidden, right? so people can still find the summit21:45
lifelessttx: I'm so going to be rushing from A to B on tuesday21:46
lifelessOTOH the rest of the week can be drinking 101, so \o/21:46
jeblairannegentle: wow, i don't think this makes ANYTHING less open21:46
markwashhub_cap: technically its 100 rods, but was rounded21:46
devanandagiven that it's apparently a separate building (!!) then a separate sched makes even more sense to me.21:46
markmcclainmy preference is one schedule21:46
hub_capmarkwash :)21:46
dolphmto rule the mall21:46
russellbvote and move on?21:46
ttxyeah21:46
annegentlemust rule the mall21:46
lifelesswe did...21:46
russellbheh21:47
jeblairannegentle: we're doing everything possible to avoid having to do something that does physically prevent over-attendance21:47
ttx#startvote How many scheds? One, Two21:47
openstackBegin voting on: How many scheds? Valid vote options are One, Two.21:47
openstackVote using '#vote OPTION'. Only your last vote counts.21:47
hub_capmaybe we need a vote to change the previous vote?21:47
russellb#vote Two21:47
gabrielhurley#vote Two21:47
markmcclain#vote One21:47
SergeyLukjanov#vote One21:47
markwash#vote Two21:47
devananda#vote two21:47
stevebaker#vote Two21:47
eglynn#vote Two21:47
*** rongze has joined #openstack-meeting21:47
sdague#vote Two21:47
jeblairannegentle: i think that shows quite a commitment to being open21:47
lifeless#vote One21:47
lifelesserm21:47
dolphm#vote Two21:47
hub_cap#vote Two21:47
lifeless#vote Two21:47
jeblair#vote Two21:47
dtroyer#vote Two21:47
*** lblanchard has joined #openstack-meeting21:47
dhellmann#vote two21:47
annegentle#vote One21:47
* dolphm unsure of case sensitivity21:47
ttxOh, I forgot the abstain option21:47
jgriffith#vote Two21:47
dhellmann#vote Two21:48
notmyname#vote one21:48
jgriffithI vote no more abstain votes21:48
notmyname#vote One21:48
ttx30 more seconds, you might want to vote with the right capitalization, not sure how dumb the bot is21:48
annegentlejeblair: I didn't realize it's a separate building too?21:48
devananda#vote Two21:48
markwashit complains about invalid votes usually I think?21:48
jeblairannegentle: i belive that was by design to cut down on unintended crossover21:48
dhellmannjgriffith: +121:48
ttxreed: around ?21:49
ttx#endvote21:49
openstackVoted on "How many scheds?" Results are21:49
reedyep21:49
openstackTwo (14): stevebaker, dhellmann, jeblair, eglynn, russellb, devananda, markwash, sdague, lifeless, gabrielhurley, dolphm, jgriffith, dtroyer, hub_cap21:49
openstackOne (4): annegentle, markmcclain, notmyname, SergeyLukjanov21:49
gabrielhurleyttx: so, should we not push the "push to sched" button right now? I have my sessions laid out basically how I like, but want to make sure they go to the right place...21:49
*** julim has quit IRC21:49
ttxreed: how far is the design summit from the rest of the conference ?21:49
reedupstairs?21:49
ttxreed: ISTR it's a separate building21:50
*** jpich has joined #openstack-meeting21:50
*** julim has joined #openstack-meeting21:50
hub_capgabrielhurley: he said he'd be configuring the proper sched after the vote21:50
* ttx tries to access maps21:50
reedlet me check21:50
hub_capi guess its sometime after that we can push21:50
sdaguettx: I didn't think there were that many buildings on that part of the island21:50
gabrielhurleyhub_cap: thanks, I missed that21:50
ttxgabrielhurley: pushing the button will do nothing at this point except show you URLs it would call if only it had an API key21:50
gabrielhurleylol21:51
gabrielhurleyokay21:51
dolphmi'd like to start seeing other track's schedules as soon as possible, to try and avoid competing for audience in the same time slot21:51
* gabrielhurley pushes it just to be ornery21:51
ttxI'll try to get the sched set up tomorrow, but will depend how fast Lauren can pay for one21:51
reedcan't find the maps :(21:51
ttxdolphm: yeah, that's actually a benefit of "Two sched", being able to push WIP21:51
* reed digging deeper21:52
*** ryanpetrello has quit IRC21:52
ttxsince we don't have to make that URL very well known just yet21:52
*** zul has joined #openstack-meeting21:52
* ttx looks21:52
*** ivasev has quit IRC21:52
ttxyou can continue trading sessions while I look for conference maps21:53
*** rongze has quit IRC21:53
SergeyLukjanovttx, I have a question about empty slots21:54
SergeyLukjanovdue to the https://docs.google.com/a/mirantis.com/spreadsheet/ccc?key=0AmUn0hzC1InKdDdPRXFrNjV4SW91SWF5N2gwYnRHYWc&usp=drive_web#gid=121:54
SergeyLukjanovthere is an empty slot after savanna slots, currently we have about 14 proposals, I'm merging them now, but it'll be great to have one more slot to cover more questions21:54
SergeyLukjanovif it's still empty :)21:55
russellbhow about we auction off the free slots21:55
ttxSergeyLukjanov: it is. i don't want to make any jealous though :)21:55
dolphmrussellb: for what, bug fixes? dev time on bp's? what can you offer21:56
russellbany last trading talk with nova?  i really need to go by end of hour21:56
hub_caplets draw straws!21:56
russellbdolphm: heh i don't know'21:56
markwashI could probably keep a slot free for. . other. . considerations21:56
lifelesslol21:56
reedttx, the sessions will be under the same roof, different floors from the rest of the Summit21:56
*** lbragstad has quit IRC21:56
ttxreed: where can you see that ?21:56
*** gabrielhurley has quit IRC21:57
*** ayoung has joined #openstack-meeting21:57
hub_capreed: one floor for all summit sessions as well? you say different floors..21:57
reedttx, checked with Lauren :) she saw that21:57
dhellmanneglynn: do you know if we have room for http://summit.openstack.org/cfp/details/318 in the ceilometer track?21:57
ttxreed: ah. ok21:57
reedhub_cap, one floor for the Summit, one for the Design sessions21:57
hub_capawesome21:57
reedhttps://www.dropbox.com/s/at4wj81f84jfaqh/May%202013%20Marketing%20Meeting.pptx slides 5 and 621:57
dhellmanneglynn: I want to make sure it's discussed, but I think it makes sense to continue the work they started in ceilometer before bringing it into oslo21:57
sdagueso the first QA slot we're going to actually all pile into the Neutron room to do Neutron / QA crossover, so that will be physically available as long as no one schedules something that would draw QA folks21:58
eglynndhellmann: I don't know21:58
dhellmanneglynn: I'll email jd__21:58
reed#link https://www.dropbox.com/s/at4wj81f84jfaqh/May%202013%20Marketing%20Meeting.pptx21:58
eglynndhellmann: (but agreed it would be preferable)21:58
*** eharney has quit IRC21:58
*** jcoufal has quit IRC21:59
reed#info the Design summit will have its own floor with restaurant in the same building as the rest of the Summit though21:59
russellbreed: thanks!21:59
reed#info slides 5 and 6 have the floorplan21:59
russellbOK, I have to go.  ping me via email or on irc tomorrow if anyone needs to chat about nova sessions21:59
dolphmanyone know if we can edit session titles / descriptions after pushing to sched22:00
russellbdolphm: you can re-push later22:00
eglynndhellmann: currently 14 proposals for 11 ceilo slots, but with some obvious opportunities for merging proposals22:00
*** jcoufal has joined #openstack-meeting22:00
dolphmi discovered that once you set pre-approved, session proposers are no longer able to edit anything22:00
*** vipul is now known as vipul-away22:00
reed#info  its a good 8-10 minute walk from the design summit to the breakout rooms in SkyCity Marriot, and about a 5 minute walk from the Design Summit to the Expo Hall which is also where 2 of the largest breakout rooms are located (we built these rooms inside the hall)22:00
eglynndhellmann: (so there may be some scope ...)22:00
dhellmanneglynn: ok, thanks, I emailed jd__22:00
reed#info it's a huge huge space, get ready to walk a lot or pack a scooter22:00
ttxreed: so it's the same roof, but a very large roof22:01
sdaguedolphm: you have to pop it back off the schedule, or click the pencil22:01
reedttx, as far as I understand it, yes22:01
*** burt has quit IRC22:01
reedwe really need a scooter22:01
sdagueedit modes seem to be a bit interesting22:01
devanandareed: distance between breakout rooms in the Marriot and the Expo Hall?22:02
hub_capmaybe they have moving walkways like in airports22:02
ttxok we need to leave room22:02
jgriffithpneumatic transport tubes22:02
markwashmortars and trampolines22:03
reedhub_cap, nope :( chmouel will be able to train for the marathon in there22:03
ttxwe can continue this in #openstack-dev if necessary22:03
ttx#endmeeting22:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:03
hub_capthx ttx22:03
openstackMeeting ended Tue Oct 22 22:03:14 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2013/project.2013-10-22-21.01.html22:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2013/project.2013-10-22-21.01.txt22:03
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2013/project.2013-10-22-21.01.log.html22:03
SergeyLukjanovttx, thx22:03
david-lyle#startmeeting Horizon22:03
openstackMeeting started Tue Oct 22 22:03:37 2013 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.22:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:03
*** openstack changes topic to " (Meeting topic: Horizon)"22:03
openstackThe meeting name has been set to 'horizon'22:03
david-lyle#topic Overview22:03
lsmolahello22:03
*** openstack changes topic to "Overview (Meeting topic: Horizon)"22:03
david-lyleHello everyone22:03
jtomasekhi22:03
lblanchardhi all!22:03
jpichhey22:03
david-lyleGabriel's tied up again this week, so I return22:04
*** hartsocks_ has quit IRC22:04
*** ruhe has joined #openstack-meeting22:04
* david-lyle promises to stay on target22:04
jcoufalo/22:04
julimhi22:04
david-lyleHorizon RC3 published on Wed.  Fixing22:04
david-lyle #link https://bugs.launchpad.net/horizon/+bug/123989622:04
lchenghi22:04
uvirtbotLaunchpad bug 1239896 in horizon "Launching Instance Boot from image (creates a new volume)" [Critical,Fix released]22:04
david-lyleThanks to all who participated in getting that one escalated, fixed and merg    ed. Just made the deadline -- well, sort of. That bug was a fairly serious r    egression in instance launch, so I'm really glad it made it in.  And now Hav    ana is officially released.  Now, we need to consider if bugs have backport     potential and tag them havana-backport-potential. Also, major regressions th    at would be RC worthy that we f22:04
david-lyleind now may have time to be documented still.     I haven't seen anything that alarming.22:04
jpichCool22:05
david-lylelots of spaces22:05
david-lyleAnyone seen any other issues that would be RC worthy, that need to be documented?22:05
*** dolphm has quit IRC22:06
david-lyleI'll consider that a no, for now.  Bring them up if you think of any as we move on.22:07
*** timductive has joined #openstack-meeting22:07
david-lyleThe summit is coming up quickly, just 2 away. Design Summit topics22:07
*** dscannell has quit IRC22:07
david-lyle#link http://summit.openstack.org/22:08
*** ruhe has quit IRC22:08
*** rockyg has joined #openstack-meeting22:08
david-lyleWe had 9 proposals for 8 slots.22:08
david-lylegabrielhurley is finalizing the schedule. There shouldn't be any topics that need to be excluded. And jcoufal is going to move the OpenStack UX session to an unconference session and advertise it in the Horizon sessions.22:08
*** aguzikova_home has quit IRC22:08
david-lyleis that your understanding jcoufal?22:09
jcoufaldavid-lyle: exactly22:09
*** sarob has quit IRC22:09
david-lyleexcellent22:09
david-lyleIf I understood the program meeting before this, there was a vote on having a separate schedule for the design summit sessions.. So the pretty color blob schedule would have one for the main conference and one for the design summit part. One of the driving factors is that will reduce the number of non-participants that get lured by a fancy topic name. I know the nova sessions last summit were especially hard hit on the first da22:10
david-lyley. Making the actual design work harder to do. Getting the tooling up for a second schedule will be some work.22:10
*** Guest56169 has joined #openstack-meeting22:10
*** harlowja_ has joined #openstack-meeting22:10
david-lyleshould also be easier to find the more important sessions for ATCs22:11
*** yogeshmehra has quit IRC22:11
*** harlowja has quit IRC22:11
david-lyleLast piece of general info22:11
david-lyleUX22:12
*** vipul-away is now known as vipul22:12
david-lylejcoufal has been busy getting the OpenStack Program up and running. While, not officially blessed by the TC, he's been getting the tools in place and discussions started. In case you missed it on the mailing list:22:12
david-lyle#link http://lists.openstack.org/pipermail/openstack-dev/2013-October/017163.html22:12
david-lyleThanks jcoufal for your hard work there.22:12
jcoufalthanks david-lyle for bringing this up22:13
*** blamar has quit IRC22:13
jcoufalwe are in pretty good shape with tools, the only missing tool is git repo and processes around that which might take a bit (but it's not that urgent)22:13
david-lyleI think it will take a little time to transition completely from the G+ group, but should be an improvement.22:13
lblanchardone question I have for people…do people feel like it's a good idea to split UX out from Horizon? I'm very used to working closely with developers while I work on UX so I want to be sure we remain in close contact with all of the UX work that is happening.22:14
lblanchardmy main concern is blueprints and conversations via meetings…do we need something to make sure we stay in sync?22:14
jcoufaljust a note, having UX separate program doesn't mean us being distant from Horizon development22:15
*** doron_afk is now known as doron22:15
lblanchardagreed, I definitely want to stay as close as possible to Horizon dev :)22:15
david-lyleI think it's important to keep the ties close, but UX reaches beyond just Horizon.22:15
*** jecarey has quit IRC22:15
lblanchardagreed.22:15
lsmolalblanchard, blueprint should have a link to conversation about UX22:16
jcoufalwant to discuss the best way of being in sync with devel teams at summit22:16
lblanchardjcoufal: sounds good22:16
jcoufalbut as lsmola said, I see it similar way22:16
david-lyleI definitely think there will be some blueprint overlap, but with slightly different focus22:16
lblanchardokay sounds great, thanks for the thoughts…we can also do a retrospective after a few months or something22:17
lblanchardsee what is working and what could be improved22:17
david-lylesounds great to me22:17
jcoufal+122:17
julim+122:18
lsmola+222:18
david-lyle#topic Bugs22:18
*** openstack changes topic to "Bugs (Meeting topic: Horizon)"22:18
*** timductive has left #openstack-meeting22:18
*** thingee has left #openstack-meeting22:18
*** dstanek has quit IRC22:19
david-lyleI want to remind reviewers that if you haven't yet, you'll need to set up a watch on openstack/django_openstack_auth22:20
*** dims has quit IRC22:20
david-lylenothing overly long in the tooth there, but just a PSA22:20
*** bpokorny has quit IRC22:21
david-lyleany bugs we should talk about?22:21
david-lyleI do want to mention one review22:22
david-lyle#link https://review.openstack.org/#/c/51234/22:22
*** Guest56169 has quit IRC22:22
lchengIn openstack_auth, we fetch the Project List for each request. https://bugs.launchpad.net/django-openstack-auth/+bug/124183822:22
uvirtbotLaunchpad bug 1241838 in django-openstack-auth "Project list is fetched from Keystone for each request" [Undecided,New]22:22
lchengNot sure why are we doing it, planning to cache the project list per token.22:23
lchengLet me know if anyone has concerns of caching it.22:23
*** sarob has joined #openstack-meeting22:23
*** rudrarug_ has joined #openstack-meeting22:23
david-lyleif the openstack/requirements review ever hits that bumps the troveclient version, currently in recheck spin.  If that hits, Horizon tests will be broken until the above review lands in some form.  So just a timing issue.22:24
*** jlucci has joined #openstack-meeting22:24
*** zul has quit IRC22:24
david-lylelcheng: as long as the cache gets updated on each token rescope, I think it should be fine22:24
lsmolalcheng, seems like a good idea22:24
*** rackerjoe has left #openstack-meeting22:25
*** ozstacker has joined #openstack-meeting22:25
lsmolalcheng, seems like it will invalidate the cache correctly22:25
david-lyleyour local keystone servers thank you22:25
*** rudrarugge has quit IRC22:26
lchengwhen the user logout the entry in the cache will be invalidated.22:26
david-lyleSeeing as the summit's around the corner and hopefully we'll talk blueprints there...22:26
david-lyle#topic Open Discussion22:26
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"22:26
jtomasekI'd like to bring up the issue with Lesscpy not being able to compile bootstrap 322:26
*** neelashah has quit IRC22:26
jtomasekThis blocks https://blueprints.launchpad.net/horizon/+spec/bootstrap-update and it's dependent22:26
jtomasekblueprints.22:26
jtomasekI have sent latest info here today: http://lists.openstack.org/pipermail/openstack-dev/2013-October/017155.html22:27
*** zul has joined #openstack-meeting22:27
jtomasekbasically I'd like to ask If there is anyone willing to help with getting lesscpy up to speed with bootstrap 3, it would be awesome22:28
*** zehicle_at_dell has quit IRC22:28
david-lylejtomasek, it was unclear, to me, from the email is the lesscpy project active and open to the pull requests or is the process stalled out?22:28
*** scott_ has joined #openstack-meeting22:28
*** scott_ is now known as Guest3444822:29
jcoufalyeah, I have to second that, if there is anybody who can help to move lesscpy to support bootstrap syntax compilation, would be very helpful to join this effort22:29
jtomasekdavid-lyle: there has been some activity from saschpe, but honestly it is not as frequent... also there are no pull requests from him to original repository22:29
jcoufaldavid-lyle: should be active and open, but not that much activity22:30
jcoufalsry jtomasek :)22:30
jtomasekand the founder of the lesscpy seems not to respond to issues at all22:30
lsmola:-)22:30
david-lylejtomasek: if there other maintainers then?22:31
david-lyles/if/are/22:31
jtomasekdavid-lyle: I am not aware of any. https://github.com/robotis/Lesscpy lists just 2 of them afaik22:31
jcoufaldavid-lyle: honestly that's what a bit worries me, that we moved to library which seems not to have very strong support in the background22:32
*** rakhmerov has joined #openstack-meeting22:32
*** radsy has joined #openstack-meeting22:33
*** zul has quit IRC22:33
david-lylethat is concerning, but it looks like  saschpe has has serveral pull requests merged22:34
*** zul has joined #openstack-meeting22:34
david-lylewe may have to revisit, but hopefully we can get there22:35
*** harlowja_ has quit IRC22:35
*** harlowja has joined #openstack-meeting22:35
jtomasekdavid-lyle: I'd really like to see saschpe's view on this, but it is quite hard to get his attention lately22:35
*** derekh has quit IRC22:36
*** rakhmerov has quit IRC22:36
*** yaguang has quit IRC22:36
david-lylelet's take this up at the summit and hope more interested parties are present22:37
*** dims has joined #openstack-meeting22:37
lsmoladavid-lyle, I have just quick one22:37
david-lylethe current alternative to falling back to node-less will not be popular22:37
jtomasekdavid-lyle: would be great thanks! maybe somebody willing to help wouls show up22:37
jcoufaldavid-lyle: I can mention lesscpy topic in my session22:37
david-lylejcoufal: that would be great and probably the best audience22:38
david-lylelsmola: sure22:38
lsmoladavid-lyle, I need to pick some library for unit-conversions https://blueprints.launchpad.net/horizon/+spec/ceilometer-api-statistics-decorators-and-convertors22:38
*** rudrarug_ has quit IRC22:38
david-lylejtomasek: thanks for you continued efforts on updating bootstrap22:39
*** rudrarugge has joined #openstack-meeting22:39
lsmolaso if anybody have any experience with unit conversion in python.. please help me pick :-)22:39
david-lylelsmola: might be a good thing to ask on openstack-dev22:40
jtomasekdavid-lyle: np!22:40
*** changbl has quit IRC22:40
lsmoladavid-lyle, ok, will do22:40
*** jrodom has quit IRC22:40
jpichFYI, OpenStack will be participating again in the Outreach Program for Women in December, there are a few applicants showing an interest in contributing to Horizon. They might pop by the horizon channel, please say hi :-)22:42
jpichSee https://wiki.openstack.org/wiki/OutreachProgramForWomen for more info, if you're curious or potentially interested in mentoring22:42
lblanchardyay!!22:43
lsmolayaaay22:43
david-lylejpich: that's great22:43
jcoufaljpich: nice:)22:43
*** rudrarugge has quit IRC22:43
*** Loquacity has joined #openstack-meeting22:43
david-lylejpich: how long is the program? and much time do they invest?22:44
jpichlsmola: Thanks for your help finding project ideas with horizon+ceilometer :-)22:44
* david-lyle promises to read link after meeting22:44
lsmolajpich, you are welcome22:44
jpichdavid-lyle: It's a 3 months internship meant to be full time (~40h/week), especially meant to help people starting out contributing to open-source22:45
jpichpart of the application involves fixing a small bug and submitting a patch so if you see easy tasks, please tag them as low-hanging-fruit :) They're hard to find22:45
lblanchardthere could be some small UX things...22:46
* jcoufal is also searching for some design topics for interns22:46
jpichvkmc participated in the December round last year with Horizon, you may have worked with her and/or met her in Portland22:46
lblanchardjpich: I'm happy to help out again in the UX area as I did with vkmc22:46
*** markpeek has quit IRC22:46
jpichlblanchard: That'd be awesome! Re: small UX improvements + helping out in general :)22:46
*** esker has quit IRC22:46
*** markpeek has joined #openstack-meeting22:46
jpichjcoufal: Thanks!! Non-coding tasks are also welcome22:47
jpichI believe there's funding confirmed for 3 interns atm (for the whole of openstack, not just horizon)22:47
david-lyleand they pick their area of interest once accepted?22:48
jpichdavid-lyle: There's a list of project ideas on the wiki, they should pick one and get in touch with the mentor22:48
jpichThe mentor will help them find a suitable small task for the application + work out a rough timeline together for the main task22:48
lsmolahttps://wiki.openstack.org/wiki/OutreachProgramForWomen/Ideas22:49
david-lyleok, so the mentor and intern are linked before acceptance into the program22:49
*** rongze has joined #openstack-meeting22:50
jpichdavid-lyle: Yes, exactly22:50
jpichThere's a #openstack-opw channel if you're interested in helping out people interested in OpenStack in the context of OPW, help troubleshoot first devstack woes, send urls to the appropriate wiki pages etc :)22:51
jpichIn any case, if you have questions or project ideas or want to chat about it, feel free to get in touch :) I mentored vkmc as part of OPW earlier in the year22:52
*** blamar has joined #openstack-meeting22:52
* terriyu was an OpenStack intern this past summer and even though jpich wasn't her official mentor, terriyu says she rocks22:53
jpich:D Thanks terriyu22:54
lsmola:-) agree22:54
*** rongze has quit IRC22:54
*** mrodden has quit IRC22:54
david-lylejpich:  Thanks for bringing this up.  Sounds like a great program.  I'll see what ideas we have.22:54
jpich:-)22:54
jpichdavid-lyle: Cool! There's a summer and winter round, hopefully openstack will continue participating22:55
*** jlucci has quit IRC22:55
david-lyleLast call...22:55
* lsmola prepares his another 100 topics22:56
*** oubiwann_ has quit IRC22:56
lblanchardheh22:56
david-lylelsmola: it's about time :_22:56
*** doron is now known as doron_afk22:56
david-lyle:)22:56
lsmolahehe22:56
lblanchard4 minutes might not be enough for lsmola :)22:57
lsmola:-)22:57
*** harlowja_ has joined #openstack-meeting22:57
jpich\o\ /o/22:57
david-lyleI could talk policy :P22:57
jcoufaldavid-lyle: close it until you have a chance, when lsmola starts it never ends :)22:57
jtomaseki can confirm that^ :D22:58
lsmolatrue that22:58
lblanchardlol22:58
*** MadOwl has quit IRC22:58
david-lyleAlright.  Havana's released with awesome updates to Horizon that we can all be very proud of.  Thanks for all the hard work and we'll chat next week.22:58
david-lyle#endmeeting22:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:58
openstackMeeting ended Tue Oct 22 22:58:45 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-10-22-22.03.html22:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-10-22-22.03.txt22:58
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-10-22-22.03.log.html22:58
jcoufalthanks all22:58
jpichYay. Thanks everyone, have a good day/night22:58
lchengthanks22:59
lsmolathank you all, good night22:59
lblanchardthanks all! Great job on the Havana release!22:59
jtomasekthanks all, bye!22:59
*** yaguang has joined #openstack-meeting22:59
*** jpich has quit IRC22:59
*** harlowja has quit IRC22:59
*** thomasm has joined #openstack-meeting23:00
*** thomasm is now known as Guest5589023:01
*** asalkeld is now known as asalkeld_lunch23:01
*** vuil has joined #openstack-meeting23:02
julimthanks all, bye.23:02
*** Guest55890 has quit IRC23:03
*** jtomasek has quit IRC23:03
*** kjiang has joined #openstack-meeting23:04
*** kjiang has left #openstack-meeting23:04
*** KC-Wang has left #openstack-meeting23:04
*** lsmola has quit IRC23:04
*** lblanchard has quit IRC23:05
*** rudrarugge has joined #openstack-meeting23:09
*** rudrarugge has quit IRC23:09
*** rudrarugge has joined #openstack-meeting23:10
*** dcramer_ has joined #openstack-meeting23:11
*** jrodom has joined #openstack-meeting23:11
*** markpeek has quit IRC23:12
*** reed has quit IRC23:15
*** MadOwl has joined #openstack-meeting23:16
*** reed has joined #openstack-meeting23:16
*** julim has quit IRC23:17
*** rudrarugge has quit IRC23:18
*** termie_ is now known as termie23:18
*** jcoufal has quit IRC23:18
*** rudrarugge has joined #openstack-meeting23:19
*** dkranz has joined #openstack-meeting23:21
*** doron_afk is now known as doron23:22
*** MarkAtwood has quit IRC23:24
*** MarkAtwood has joined #openstack-meeting23:24
*** rockyg has quit IRC23:25
*** rockyg has joined #openstack-meeting23:25
*** termie has quit IRC23:25
*** termie has joined #openstack-meeting23:25
*** jmontemayor has quit IRC23:28
*** rockyg has quit IRC23:30
*** dcramer_ has quit IRC23:30
*** sushils has quit IRC23:31
*** rakhmerov has joined #openstack-meeting23:32
*** vito-ordaz has quit IRC23:33
*** garyduan has quit IRC23:34
*** fnaval_ has quit IRC23:34
*** jodom has joined #openstack-meeting23:34
*** jodom has quit IRC23:34
*** rakhmerov has quit IRC23:37
*** jrodom has quit IRC23:39
*** Loquacity has quit IRC23:40
*** Loquacity has joined #openstack-meeting23:42
*** dcramer_ has joined #openstack-meeting23:43
*** changbl has joined #openstack-meeting23:46
*** lblanchard has joined #openstack-meeting23:47
*** cody-somerville has joined #openstack-meeting23:47
*** sarob has quit IRC23:47
*** sarob has joined #openstack-meeting23:47
*** yogeshmehra has joined #openstack-meeting23:48
*** rongze has joined #openstack-meeting23:50
*** vipul is now known as vipul-away23:51
*** matsuhashi has joined #openstack-meeting23:53
*** tanisdl has quit IRC23:54
*** rongze has quit IRC23:55
*** vipul-away is now known as vipul23:57
*** dstanek has joined #openstack-meeting23:58

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