Tuesday, 2014-09-02

*** padkrish has quit IRC00:00
*** lsmola has quit IRC00:00
*** salv-orlando has quit IRC00:02
*** haomaiwang has joined #openstack-meeting00:02
*** mchalla has joined #openstack-meeting00:10
*** asettle is now known as alexandra00:11
*** asettle has joined #openstack-meeting00:11
*** alexandra has quit IRC00:12
*** yaja_ has quit IRC00:12
*** lsmola has joined #openstack-meeting00:12
*** Mandell has joined #openstack-meeting00:14
*** mchalla has quit IRC00:15
*** haomaiwang has quit IRC00:16
*** otter768 has joined #openstack-meeting00:19
*** Mandell has quit IRC00:19
*** haomaiwang has joined #openstack-meeting00:23
*** padkrish has joined #openstack-meeting00:23
*** padkrish has quit IRC00:23
*** padkrish has joined #openstack-meeting00:24
*** yamamoto has quit IRC00:24
*** yingjun has joined #openstack-meeting00:24
*** otherwiseguy has quit IRC00:25
*** _nadya_ has quit IRC00:25
*** yamamoto has joined #openstack-meeting00:25
*** otter768 has quit IRC00:25
*** otter768 has joined #openstack-meeting00:28
*** marun is now known as marun_afk00:30
*** haomaiwang has quit IRC00:30
*** haomaiwa_ has joined #openstack-meeting00:30
*** haomaiwa_ has quit IRC00:41
*** marun_afk is now known as marun00:42
*** emagana has joined #openstack-meeting00:43
*** haomaiwa_ has joined #openstack-meeting00:43
*** kebray has joined #openstack-meeting00:44
*** mchalla has joined #openstack-meeting00:45
*** js1123 has quit IRC00:46
*** emagana has quit IRC00:47
*** dims has joined #openstack-meeting00:47
*** mchalla has quit IRC00:48
*** changbl has joined #openstack-meeting00:48
*** mchalla has joined #openstack-meeting00:48
*** gokrokve_ has joined #openstack-meeting00:50
*** mchalla has quit IRC00:50
*** SridharRamaswamy has joined #openstack-meeting00:51
*** gokrokve has quit IRC00:52
*** _nadya_ has joined #openstack-meeting00:52
*** yamahata has quit IRC00:55
*** gokrokve_ has quit IRC00:55
*** gokrokve has joined #openstack-meeting00:56
*** adahms__ has joined #openstack-meeting00:57
*** rick_ has joined #openstack-meeting00:57
*** rick_ has quit IRC00:58
*** yamamoto has quit IRC00:59
*** emagana has joined #openstack-meeting00:59
*** adahms_ has quit IRC01:00
*** gokrokve has quit IRC01:00
*** emagana has quit IRC01:04
*** kebray has quit IRC01:08
*** adahms_ has joined #openstack-meeting01:09
*** adahms has joined #openstack-meeting01:10
*** brucer__ has joined #openstack-meeting01:11
*** padkrish_ has joined #openstack-meeting01:12
*** padkrish_ has quit IRC01:12
*** adahms__ has quit IRC01:12
*** padkrish_ has joined #openstack-meeting01:13
*** adahms_ has quit IRC01:13
*** adahms__ has joined #openstack-meeting01:13
*** padkrish has quit IRC01:15
*** adahms has quit IRC01:15
*** brucer_ has quit IRC01:15
*** ajo__ has quit IRC01:18
*** padkrish_ has quit IRC01:24
*** hrybacki has quit IRC01:25
*** amotoki has joined #openstack-meeting01:26
*** marun is now known as marun_afk01:26
*** gokrokve has joined #openstack-meeting01:26
*** gokrokve has quit IRC01:27
*** brucer__ has quit IRC01:27
*** brucer__ has joined #openstack-meeting01:28
*** adahms has joined #openstack-meeting01:28
*** gokrokve has joined #openstack-meeting01:28
*** dims has quit IRC01:28
*** Mandell has joined #openstack-meeting01:30
*** amotoki has quit IRC01:31
*** daneleblanc has joined #openstack-meeting01:31
*** adahms__ has quit IRC01:31
*** gokrokve has quit IRC01:32
*** mberlin1 has joined #openstack-meeting01:32
*** dane_leblanc has quit IRC01:33
*** mchalla has joined #openstack-meeting01:33
*** mberlin has quit IRC01:34
*** haomaiw__ has joined #openstack-meeting01:39
anteayalifeless: if you are about, any percieved naming overlap with tripleo and a fledgling stackforge project entitlied tricircle? https://review.openstack.org/#/c/117939/01:39
*** gokrokve has joined #openstack-meeting01:40
*** haomaiwa_ has quit IRC01:40
anteayad'oh01:40
*** mitarun has joined #openstack-meeting01:43
*** vkmc has quit IRC01:44
*** baoli has joined #openstack-meeting01:44
*** gokrokve has quit IRC01:44
*** mestery has quit IRC01:48
*** jjmb has joined #openstack-meeting01:48
*** mitarun has quit IRC01:48
*** nosnos has joined #openstack-meeting01:48
*** mitarun has joined #openstack-meeting01:48
*** baoli has quit IRC01:49
*** baoli has joined #openstack-meeting01:49
*** marun_afk has quit IRC01:50
*** baoli has quit IRC01:50
*** haomaiw__ has quit IRC01:50
*** baoli has joined #openstack-meeting01:51
*** stevemar has joined #openstack-meeting01:53
*** mitarun has quit IRC01:53
*** yamahata has joined #openstack-meeting01:53
*** baohua has joined #openstack-meeting01:53
*** emagana has joined #openstack-meeting01:53
*** baohua has quit IRC01:54
*** baoli has quit IRC01:55
*** baohua has joined #openstack-meeting01:55
*** haomaiwang has joined #openstack-meeting01:56
*** jjmb has quit IRC01:57
*** emagana has quit IRC01:57
*** alexpilotti has quit IRC01:57
*** amotoki has joined #openstack-meeting02:00
*** haomaiwang has quit IRC02:01
*** matiu has joined #openstack-meeting02:01
*** haomaiwang has joined #openstack-meeting02:02
*** yamamoto has joined #openstack-meeting02:02
*** matiu_ has joined #openstack-meeting02:05
*** matiu_ has joined #openstack-meeting02:05
*** xuhanp has joined #openstack-meeting02:06
*** matiu has quit IRC02:06
*** otherwiseguy has joined #openstack-meeting02:07
*** zul has quit IRC02:08
*** brucer_afk has joined #openstack-meeting02:09
*** adahms_ has joined #openstack-meeting02:10
*** otherwiseguy has quit IRC02:11
*** brucer__ has quit IRC02:13
*** adahms has quit IRC02:13
*** baoli has joined #openstack-meeting02:13
*** mchalla has quit IRC02:16
*** mitarun has joined #openstack-meeting02:16
*** Poornima_ has joined #openstack-meeting02:17
*** miqui has joined #openstack-meeting02:19
*** mitarun has quit IRC02:24
*** padkrish has joined #openstack-meeting02:24
*** mitarun has joined #openstack-meeting02:24
*** padkrish has quit IRC02:27
*** padkrish has joined #openstack-meeting02:27
*** padkrish has quit IRC02:28
*** eghobo has joined #openstack-meeting02:28
*** padkrish has joined #openstack-meeting02:29
*** mitarun has quit IRC02:29
*** asettle has quit IRC02:33
*** nibalize1 is now known as nibalizer02:39
*** gokrokve has joined #openstack-meeting02:40
*** haomaiwang has quit IRC02:42
*** rbowen has joined #openstack-meeting02:45
*** padkrish has quit IRC02:45
*** gokrokve has quit IRC02:45
*** rbowen has quit IRC02:45
*** emagana has joined #openstack-meeting02:47
*** haomaiwang has joined #openstack-meeting02:48
*** adahms__ has joined #openstack-meeting02:48
*** brucer_lvl1 has joined #openstack-meeting02:48
*** brucer_meeting has joined #openstack-meeting02:48
*** adahms has joined #openstack-meeting02:49
*** alex_xu has joined #openstack-meeting02:49
*** imsurit has quit IRC02:50
*** epico has joined #openstack-meeting02:51
*** brucer_afk has quit IRC02:51
*** mspreitz has joined #openstack-meeting02:51
*** adahms_ has quit IRC02:52
*** brucer_lvl1 has quit IRC02:52
*** adahms__ has quit IRC02:52
*** emagana has quit IRC02:52
*** matiu_ is now known as matiu02:54
*** Riddhi has joined #openstack-meeting02:54
*** yingjun has quit IRC02:55
*** yingjun has joined #openstack-meeting02:55
*** xuhanp_ has quit IRC02:58
*** yingjun has quit IRC03:00
*** zz_naotokl is now known as naotok03:00
*** brucer_wfh has joined #openstack-meeting03:01
*** adahms_ has joined #openstack-meeting03:01
*** brucer_training has joined #openstack-meeting03:01
*** primemin1sterp has quit IRC03:03
*** brucer_meeting has quit IRC03:04
*** padkrish has joined #openstack-meeting03:05
*** adahms has quit IRC03:05
*** padkrish has quit IRC03:05
*** brucer_wfh has quit IRC03:05
*** padkrish has joined #openstack-meeting03:05
*** sankarshan_away is now known as sankarshan03:10
*** yingjun has joined #openstack-meeting03:11
*** epico has quit IRC03:11
*** epico has joined #openstack-meeting03:15
*** haomaiw__ has joined #openstack-meeting03:15
*** mchalla has joined #openstack-meeting03:16
*** eghobo has quit IRC03:17
*** paragan has joined #openstack-meeting03:17
*** paragan has joined #openstack-meeting03:17
*** haomaiwang has quit IRC03:19
*** SridharR_ has joined #openstack-meeting03:20
*** mchalla has quit IRC03:21
*** Mandell has quit IRC03:23
*** SridharRamaswamy has quit IRC03:23
*** SridharR_ has quit IRC03:23
*** padkrish has quit IRC03:23
*** Mandell has joined #openstack-meeting03:24
*** SridharRamaswamy has joined #openstack-meeting03:24
*** amotoki_ has joined #openstack-meeting03:27
*** haomaiw__ has quit IRC03:27
*** otherwiseguy has joined #openstack-meeting03:27
*** haomaiwang has joined #openstack-meeting03:28
*** alex_xu has quit IRC03:28
*** SridharRamaswamy has quit IRC03:28
*** natarajk has joined #openstack-meeting03:30
*** amotoki_ has quit IRC03:31
*** kebray has joined #openstack-meeting03:32
*** natarajk has quit IRC03:35
*** mitarun has joined #openstack-meeting03:38
*** padkrish has joined #openstack-meeting03:38
*** padkrish has quit IRC03:39
*** baoli has quit IRC03:39
*** xianghuihui has joined #openstack-meeting03:39
*** alex_xu has joined #openstack-meeting03:39
*** padkrish has joined #openstack-meeting03:39
*** gokrokve has joined #openstack-meeting03:40
*** mestery has joined #openstack-meeting03:41
*** mitarun has quit IRC03:41
*** emagana has joined #openstack-meeting03:41
*** mitarun has joined #openstack-meeting03:42
*** xianghui has quit IRC03:42
*** kebray has quit IRC03:42
*** kebray has joined #openstack-meeting03:43
*** nosnos has quit IRC03:44
*** nosnos has joined #openstack-meeting03:45
*** gokrokve has quit IRC03:45
*** alex_xu has quit IRC03:45
*** mitarun has quit IRC03:46
*** emagana has quit IRC03:46
*** brucer has joined #openstack-meeting03:47
*** adahms has joined #openstack-meeting03:47
*** adahms__ has joined #openstack-meeting03:48
*** brucer_ has joined #openstack-meeting03:48
*** nosnos has quit IRC03:49
*** brucer_training has quit IRC03:50
*** adahms_ has quit IRC03:50
*** adahms has quit IRC03:52
*** brucer has quit IRC03:52
*** haomaiwang has quit IRC03:52
*** haomai___ has joined #openstack-meeting03:52
*** xuhanp_ has joined #openstack-meeting03:57
*** alex_xu has joined #openstack-meeting03:58
*** yingjun has quit IRC03:58
*** yingjun has joined #openstack-meeting03:58
*** mitarun has joined #openstack-meeting04:00
*** xuhanp has quit IRC04:02
*** yingjun has quit IRC04:03
*** novas0x2a|laptop has joined #openstack-meeting04:05
*** mitarun has quit IRC04:05
*** mitarun has joined #openstack-meeting04:05
*** mestery has quit IRC04:08
*** chandankumar has joined #openstack-meeting04:11
*** otter768 has quit IRC04:11
*** xuhanp_ has quit IRC04:13
*** eghobo has joined #openstack-meeting04:14
*** brucer__ has joined #openstack-meeting04:14
*** adahms_ has joined #openstack-meeting04:14
*** brucer_afk has joined #openstack-meeting04:15
*** adahms has joined #openstack-meeting04:16
*** nosnos has joined #openstack-meeting04:17
*** adahms__ has quit IRC04:18
*** brucer_ has quit IRC04:18
*** xianghuihui has quit IRC04:19
*** adahms_ has quit IRC04:19
*** brucer__ has quit IRC04:19
*** dbite has joined #openstack-meeting04:19
*** xianghui has joined #openstack-meeting04:20
*** kebray_ has joined #openstack-meeting04:20
*** rajeshr has joined #openstack-meeting04:20
*** kebray has quit IRC04:23
*** carl_baldwin has joined #openstack-meeting04:24
*** shankar has joined #openstack-meeting04:25
*** ngoswami has joined #openstack-meeting04:29
*** ildikov_ has quit IRC04:33
*** nikunj2512 has joined #openstack-meeting04:33
*** emagana has joined #openstack-meeting04:36
*** chandankumar has quit IRC04:38
*** emagana has quit IRC04:40
*** Mandell has quit IRC04:45
*** mchalla has joined #openstack-meeting04:46
*** cody-somerville has joined #openstack-meeting04:47
*** gokrokve has joined #openstack-meeting04:48
*** padkrish has quit IRC04:49
*** Riddhi has quit IRC04:49
*** eghobo has quit IRC04:50
*** mchalla has quit IRC04:50
*** eghobo has joined #openstack-meeting04:50
*** chandankumar has joined #openstack-meeting04:51
*** gokrokve has quit IRC04:52
*** nati_ueno has joined #openstack-meeting04:53
*** s3wong has joined #openstack-meeting04:56
*** vishwanathj has joined #openstack-meeting04:58
*** natarajk has joined #openstack-meeting04:59
*** yingjun has joined #openstack-meeting04:59
yamahatahello05:00
natarajkhi05:00
vishwanathjHello05:00
yamahata#startmeeting servicevm-device-manager05:00
openstackMeeting started Tue Sep  2 05:00:36 2014 UTC and is due to finish in 60 minutes.  The chair is yamahata. Information about MeetBot at http://wiki.debian.org/MeetBot.05:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:00
*** openstack changes topic to " (Meeting topic: servicevm-device-manager)"05:00
openstackThe meeting name has been set to 'servicevm_device_manager'05:00
yamahataDo we have bob?05:01
yamahatalet's give him minutes.05:01
s3wonghello05:01
yamahatas3wong: hello05:01
s3wongyamahata: it is a US holiday today - though bmelande isn't in US :-)05:02
yamahatalabour day?05:02
*** ngoswami has quit IRC05:02
vishwanathjyes05:02
yamahataseems he's absent today. let's begin05:03
yamahata#topic Announcement05:03
*** openstack changes topic to "Announcement (Meeting topic: servicevm-device-manager)"05:03
yamahataneutron feature freeze Sep 9.05:03
*** yingjun has quit IRC05:03
s3wongyes05:04
*** alex_xu has quit IRC05:04
yamahataCSR1kv patch is merged. congrats to Bob.05:04
yamahatavyatta vrouter patch is still under review05:04
yamahata#action everyone review vrouter patch05:04
yamahata#link https://review.openstack.org/#/c/102336/ Implementation of Brocade Vyatta vRouter L3 Plugin05:04
s3wongunfortunately the service insertion patch got a -2 from markmccclain...05:05
*** rushiagr_away is now known as rushiagr05:05
*** natarajk_ has joined #openstack-meeting05:05
yamahataNeutron blueprint for Kilo will be open after RC105:05
yamahataSo I'd like to have working reference implementation at that time. and update l3 routervm plugin. I hope.05:05
yamahatas3wong: that's bad. service insertion is really wanted.05:06
*** _nadya_ has quit IRC05:06
*** Mandell has joined #openstack-meeting05:06
yamahataI uploaded WIP patch at gerrit05:06
yamahata#link https://review.openstack.org/#/c/116773/ WIP: router vm l3 plugin/driver/agent05:06
s3wongyamahata: according to enikanorov_ during last week's adv service meeting, flavor is unlikely to make it neither05:06
*** natarajk has quit IRC05:06
*** xuhanp has joined #openstack-meeting05:07
yamahataOh, flavour framework too.05:07
*** shankar has left #openstack-meeting05:07
s3wongyamahata: spec was never approved05:07
natarajk_i had few questions on what was discussed last week05:07
*** Mandell has quit IRC05:07
yamahatanatarajk_: sure.05:07
s3wongnatarajk_: sorry for hijacking the meeting :-)05:08
yamahataBefore that I'd like to announce I'll be absent next week sep 9.05:08
natarajk_there was some mention on integrating route vm with l3 agent05:08
natarajk_can you clarify05:08
yamahataIf someone is willing to chair this meeting, please go ahead. otherwise it will be cancelled on sep 9.05:08
yamahata#topic integrating routervm with l3 agent05:09
*** openstack changes topic to "integrating routervm with l3 agent (Meeting topic: servicevm-device-manager)"05:09
yamahataWhat I have in mind is to integrate config agent with l3 agent.05:09
yamahatavyatta routervm case, it doesn't use any agent.05:10
*** Mandell has joined #openstack-meeting05:10
natarajk_config agent model followed by cisco's team ?05:10
yamahataI suppose, for fwaas, agent will be used. correct?05:11
yamahatanatarajk_: Yes.05:11
natarajk_for fwaas, firewall agent is coupled with l3 agent05:11
natarajk_so we use the firewall agent05:11
yamahataAt this point, I'm not sure it will make sense to consolidate l3 agent with config agent.05:11
yamahataI'm playing with the code. I haven't concluded it personally. Off course discussion is welcome. I'm open.05:12
*** padkrish has joined #openstack-meeting05:12
*** padkrish has quit IRC05:12
*** kopparam has joined #openstack-meeting05:13
yamahataThe current model of l3 agent is tied to network node.05:13
*** padkrish has joined #openstack-meeting05:13
*** gokrokve has joined #openstack-meeting05:13
natarajk_can you explain who creates the linux routers when we have config agent05:13
*** penick has joined #openstack-meeting05:14
yamahatanatarajk_: do you mean reference l3 (legacy, non-DVR) agent case?05:14
natarajk_yes05:14
*** xuhanp_ has joined #openstack-meeting05:14
yamahataIn that case, neturon router is on network node.05:15
yamahataWhen neutron router is created, l3 agent is chosen = network node is chosen.05:15
*** carl_baldwin has quit IRC05:15
natarajk_i understand that, but with config agent integration will anything change there ?05:15
yamahataThen RPC is sent to the l3 agent which creates router on that networn node.05:15
natarajk_So, config agent integration is only for router vm cases ?05:15
*** kebray_ has quit IRC05:16
yamahataThe difference is that cfg agent isn't tied to network node.05:16
natarajk_ok05:16
yamahatanatarajk_: Yes. or Xaas VM case.05:16
yamahatalike FWaaS05:16
yamahataAt this point, Bob has only routervm case, but I guess they will propose fwaas one for Kilo cycle.05:17
*** haomai___ has quit IRC05:17
*** otherwiseguy has quit IRC05:17
yamahataIn order to generalize, driver architecture will be introduced to allow any service05:17
natarajk_ok05:18
*** cody-somerville has quit IRC05:18
*** gokrokve has quit IRC05:18
*** s3wong has quit IRC05:18
*** s3wong has joined #openstack-meeting05:19
yamahataIf you want your own agent, it's not prophibited.05:19
yamahatanatarajk_: If it's allowed, I'd like to see your fwaas agent implementation05:20
yamahataanyway you don't have to use config agent. you can use your own agent.05:20
*** xuhanp_ has quit IRC05:21
*** natarajk has joined #openstack-meeting05:21
*** s3wong has quit IRC05:21
natarajkhaving some IRC connectivity issues05:22
*** mrmartin has joined #openstack-meeting05:22
*** s3wong has joined #openstack-meeting05:22
*** natarajk_ has quit IRC05:22
natarajki'll look into config agent code in cisco's plugin05:22
natarajkto get more details05:22
yamahatagreat05:22
*** ildikov has joined #openstack-meeting05:23
yamahataIt just offload api call for vm from neutron server to agent.05:23
*** alex_xu has joined #openstack-meeting05:23
natarajkok05:23
yamahataany other topic?05:23
*** haomaiwa_ has joined #openstack-meeting05:24
yamahata#topic Open Discussion05:24
*** openstack changes topic to "Open Discussion (Meeting topic: servicevm-device-manager)"05:24
*** rakesh_hs has joined #openstack-meeting05:24
yamahata#action yamahata announce cancellation of Sep 9 meeting05:24
natarajki had question on jenkins errors05:25
natarajkfor the transient issues, do we just run "recheck no bug"05:25
natarajkit triggers all the CIs05:26
natarajkis there a way to just recheck jenkins ?05:26
yamahatanatarajk: Unfortunately I don't know.05:26
natarajkok05:26
yamahatabasically each thirdparty CI provides their own way to recheck, like recheck-vmware05:27
*** nshaikh has joined #openstack-meeting05:27
natarajkyes, but recheck no bug triggers everything05:27
*** amotoki_ has joined #openstack-meeting05:28
*** haomaiwa_ has quit IRC05:28
*** haomaiwang has joined #openstack-meeting05:28
yamahataany other topic?05:28
yamahataokay, thank you everyone. and sorry for my absence next week. see you two weeks later.05:29
s3wongsee you05:29
yamahata#endmeeting05:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:30
openstackMeeting ended Tue Sep  2 05:30:05 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-09-02-05.00.html05:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-09-02-05.00.txt05:30
openstackLog:            http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-09-02-05.00.log.html05:30
*** natarajk has quit IRC05:30
*** vishwanathj has quit IRC05:30
*** eghobo has quit IRC05:30
*** eghobo has joined #openstack-meeting05:30
*** emagana has joined #openstack-meeting05:31
*** amotoki_ has quit IRC05:33
*** xuhanp_ has joined #openstack-meeting05:33
*** asettle has joined #openstack-meeting05:33
*** nikunj2512 has quit IRC05:34
*** nikunj2513 has joined #openstack-meeting05:34
*** juice has quit IRC05:35
*** emagana has quit IRC05:36
*** juice has joined #openstack-meeting05:36
*** haomaiwang has quit IRC05:37
*** nati_ueno has quit IRC05:38
*** nati_ueno has joined #openstack-meeting05:38
*** _nadya_ has joined #openstack-meeting05:38
*** mitarun has quit IRC05:38
*** mitarun has joined #openstack-meeting05:39
*** xuhanp_ has quit IRC05:40
*** mitarun has quit IRC05:40
*** gokrokve has joined #openstack-meeting05:40
*** mitarun has joined #openstack-meeting05:40
*** nati_ueno has quit IRC05:43
*** haomaiwa_ has joined #openstack-meeting05:43
*** nikunj2513 has quit IRC05:44
*** nikunj2513 has joined #openstack-meeting05:45
*** gokrokve has quit IRC05:46
*** changbl has quit IRC05:46
*** yaguang has joined #openstack-meeting05:49
*** doron_afk has joined #openstack-meeting05:50
*** xuhanp_ has joined #openstack-meeting05:50
*** adahms_ has joined #openstack-meeting05:50
*** brucer_afk has quit IRC05:50
*** haomaiwa_ has quit IRC05:51
*** brucer_afk has joined #openstack-meeting05:51
*** penick has quit IRC05:52
*** mspreitz has quit IRC05:53
*** adahms has quit IRC05:54
*** adahms_ has quit IRC05:55
*** peoplemerge_ has quit IRC05:56
*** xuhanp_ has quit IRC05:57
*** xuhanp_ has joined #openstack-meeting06:00
*** yingjun has joined #openstack-meeting06:01
*** mrmartin has quit IRC06:04
*** JRobinson__ has quit IRC06:04
*** alex_xu has quit IRC06:04
*** yingjun has quit IRC06:06
*** k4n0 has joined #openstack-meeting06:06
*** s3wong has quit IRC06:08
*** xuhanp_ has quit IRC06:08
*** zhhuabj has quit IRC06:10
*** zhhuabj has joined #openstack-meeting06:10
*** _nadya_ has quit IRC06:24
*** alex_xu has joined #openstack-meeting06:24
*** yingjun has joined #openstack-meeting06:24
*** dbite has quit IRC06:25
*** emagana has joined #openstack-meeting06:26
*** flaper87|afk is now known as flaper8706:26
*** mrunge has joined #openstack-meeting06:28
*** yingjun has quit IRC06:29
*** dbite has joined #openstack-meeting06:29
*** emagana has quit IRC06:30
*** rm_work|away is now known as rm_work06:32
*** alex_xu has quit IRC06:34
*** yingjun has joined #openstack-meeting06:36
*** ndipanov has joined #openstack-meeting06:40
*** alex_xu has joined #openstack-meeting06:47
*** mchalla has joined #openstack-meeting06:47
*** mitarun has quit IRC06:48
*** salv-orlando has joined #openstack-meeting06:48
*** mitarun_ has joined #openstack-meeting06:50
*** pkoniszewski has joined #openstack-meeting06:51
*** mchalla has quit IRC06:52
*** brucer_lvl1 has joined #openstack-meeting06:52
*** shankar has joined #openstack-meeting06:52
*** ildikov has quit IRC06:54
*** brucer_afk has quit IRC06:55
*** simon-AS559 has joined #openstack-meeting06:57
*** yamamoto has quit IRC06:58
*** kopparam has quit IRC07:00
*** kopparam has joined #openstack-meeting07:00
*** chandankumar has quit IRC07:01
*** doron_afk is now known as doron07:01
*** mitarun_ has quit IRC07:03
*** ildikov has joined #openstack-meeting07:04
*** mitarun has joined #openstack-meeting07:04
*** dbite has quit IRC07:05
*** dbite_ has joined #openstack-meeting07:05
*** kopparam has quit IRC07:05
*** _nadya_ has joined #openstack-meeting07:06
*** jtomasek has quit IRC07:06
*** nikunj2513 has quit IRC07:07
*** nikunj2513 has joined #openstack-meeting07:07
*** mitarun has quit IRC07:08
*** dbite_ has quit IRC07:09
*** mpaolino has joined #openstack-meeting07:09
*** linuxnewb2 has quit IRC07:09
*** padkrish has quit IRC07:10
*** matrohon has joined #openstack-meeting07:13
*** jcoufal has joined #openstack-meeting07:13
*** julienvey has joined #openstack-meeting07:16
*** Longgeek has joined #openstack-meeting07:20
*** emagana has joined #openstack-meeting07:20
*** Longgeek has quit IRC07:20
*** jlanoux has joined #openstack-meeting07:22
*** Longgeek has joined #openstack-meeting07:23
*** emagana has quit IRC07:24
*** afazekas has joined #openstack-meeting07:28
*** amotoki_ has joined #openstack-meeting07:28
*** stevemar has quit IRC07:29
*** luqas has joined #openstack-meeting07:29
*** yamamoto has joined #openstack-meeting07:30
*** naotok is now known as zz_naotok07:33
*** amotoki_ has quit IRC07:33
*** pkoniszewski has quit IRC07:34
*** pkoniszewski has joined #openstack-meeting07:34
*** MaxV has joined #openstack-meeting07:38
*** Mandell has quit IRC07:38
*** doron is now known as doron_afk07:38
*** gokrokve has joined #openstack-meeting07:40
*** gokrokve has quit IRC07:42
*** gokrokve has joined #openstack-meeting07:42
*** flaper87 is now known as flaper87|afk07:43
*** haomaiwang has joined #openstack-meeting07:45
*** gokrokve has quit IRC07:46
*** asettle has quit IRC07:47
*** pkoniszewski has quit IRC07:48
*** pkoniszewski has joined #openstack-meeting07:48
*** yamamoto has quit IRC07:48
*** flaper87|afk is now known as flaper8707:48
*** yamamoto has joined #openstack-meeting07:49
*** yamamoto has quit IRC07:49
*** kopparam has joined #openstack-meeting07:49
*** yamamoto has joined #openstack-meeting07:49
*** eghobo has quit IRC07:50
*** padkrish has joined #openstack-meeting07:52
*** safchain has joined #openstack-meeting07:52
*** salv-orlando has quit IRC07:52
*** julienvey has quit IRC07:53
*** andreykurilin_ has joined #openstack-meeting07:55
*** zz_johnthetubagu is now known as johnthetubaguy07:56
*** dims has joined #openstack-meeting07:56
*** ygbo has joined #openstack-meeting07:56
*** padkrish has quit IRC07:57
*** _nadya_ has quit IRC07:58
*** derekh has joined #openstack-meeting07:58
*** dims has quit IRC08:00
*** acoles_away is now known as acoles08:01
*** mestery has joined #openstack-meeting08:03
*** afazekas has quit IRC08:05
*** linuxnewb2 has joined #openstack-meeting08:05
*** afazekas has joined #openstack-meeting08:06
*** brucer_lvl1 has quit IRC08:07
*** morganfainberg is now known as morganfainberg_Z08:12
*** yamamoto has quit IRC08:13
*** pnavarro has joined #openstack-meeting08:14
*** yamamoto has joined #openstack-meeting08:14
*** matiu_ has joined #openstack-meeting08:14
*** matiu_ has joined #openstack-meeting08:14
*** emagana has joined #openstack-meeting08:14
*** matiu has quit IRC08:16
*** nikunj2513 has quit IRC08:17
*** emagana has quit IRC08:19
*** matrohon has quit IRC08:19
*** mestery has quit IRC08:22
*** mestery has joined #openstack-meeting08:23
*** yingjun has quit IRC08:25
*** pelix has joined #openstack-meeting08:29
*** matrohon has joined #openstack-meeting08:32
*** doude has joined #openstack-meeting08:37
*** flaper87 is now known as flaper87|afk08:37
*** jlibosva has joined #openstack-meeting08:38
*** nsaje_ is now known as nsaje08:39
*** gokrokve has joined #openstack-meeting08:40
*** infotection has quit IRC08:41
*** ildikov_ has joined #openstack-meeting08:44
*** ngoswami has joined #openstack-meeting08:45
*** gokrokve has quit IRC08:46
*** infotection has joined #openstack-meeting08:46
*** andreaf has joined #openstack-meeting08:47
*** ildikov has quit IRC08:47
*** mchalla has joined #openstack-meeting08:49
*** flaper87|afk is now known as flaper8708:50
*** mestery has quit IRC08:52
*** mestery has joined #openstack-meeting08:52
*** ociuhandu has quit IRC08:53
*** andreykurilin_ has quit IRC08:53
*** mchalla has quit IRC08:53
*** mitarun has joined #openstack-meeting08:54
*** mrunge_ has joined #openstack-meeting08:56
*** dtantsur|afk is now known as dtantsur08:57
*** mrunge has quit IRC08:57
*** mflobo_ has joined #openstack-meeting08:58
*** mflobo has quit IRC09:01
*** zul has joined #openstack-meeting09:02
*** pelix has quit IRC09:03
*** pelix has joined #openstack-meeting09:03
*** mwagner_lap has joined #openstack-meeting09:04
*** e0ne has joined #openstack-meeting09:06
*** alexpilotti has joined #openstack-meeting09:08
*** emagana has joined #openstack-meeting09:08
*** luqas has quit IRC09:09
*** emagana has quit IRC09:13
*** alexpilotti has quit IRC09:15
*** mflobo has joined #openstack-meeting09:22
*** mflobo_ has quit IRC09:25
*** alex_xu has quit IRC09:25
*** mflobo_ has joined #openstack-meeting09:26
*** che-arne has joined #openstack-meeting09:26
*** salv-orlando has joined #openstack-meeting09:28
*** mflobo has quit IRC09:29
*** jlanoux_ has joined #openstack-meeting09:29
*** yingjun has joined #openstack-meeting09:29
*** amotoki_ has joined #openstack-meeting09:29
*** jlanoux has quit IRC09:30
*** yamamoto has quit IRC09:30
*** mflobo has joined #openstack-meeting09:32
*** yingjun has quit IRC09:34
*** amotoki_ has quit IRC09:34
*** trinaths has joined #openstack-meeting09:35
*** mflobo_ has quit IRC09:36
*** rm_work is now known as rm_work|away09:37
*** wuhg has joined #openstack-meeting09:38
*** Mandell has joined #openstack-meeting09:38
*** jlanoux has joined #openstack-meeting09:39
*** luqas has joined #openstack-meeting09:40
*** gokrokve has joined #openstack-meeting09:40
*** jlanoux_ has quit IRC09:42
*** Mandell has quit IRC09:43
*** gokrokve has quit IRC09:45
*** toan-tran has joined #openstack-meeting09:48
*** yamamoto has joined #openstack-meeting09:49
*** jtomasek has joined #openstack-meeting09:49
*** cipcosma has joined #openstack-meeting09:49
*** ociuhandu has joined #openstack-meeting09:50
*** yamamoto has quit IRC09:54
*** paragan has quit IRC09:57
*** doude has quit IRC09:58
*** baohua has quit IRC09:58
*** rm_work|away is now known as rm_work09:59
*** doude has joined #openstack-meeting09:59
*** zhhuabj has quit IRC10:01
*** emagana has joined #openstack-meeting10:02
*** emagana has quit IRC10:06
*** xuhanp has quit IRC10:08
*** mitarun has quit IRC10:09
*** mitarun has joined #openstack-meeting10:10
*** trinaths has left #openstack-meeting10:11
*** doude has quit IRC10:12
*** e0ne has quit IRC10:12
*** rm_work is now known as rm_work|away10:13
*** doude has joined #openstack-meeting10:14
*** mitarun has quit IRC10:14
*** e0ne has joined #openstack-meeting10:15
*** mestery has quit IRC10:15
*** mestery has joined #openstack-meeting10:15
*** Poornima_ has quit IRC10:16
*** mestery has quit IRC10:21
*** mestery has joined #openstack-meeting10:22
*** mitarun has joined #openstack-meeting10:23
*** IanGovett has joined #openstack-meeting10:23
*** mitarun has quit IRC10:26
*** mitarun has joined #openstack-meeting10:27
*** mitarun has quit IRC10:32
*** jlanoux_ has joined #openstack-meeting10:32
*** evgenyf has joined #openstack-meeting10:33
*** jlanoux has quit IRC10:35
*** yamahata has quit IRC10:36
*** gokrokve has joined #openstack-meeting10:40
*** alexpilotti has joined #openstack-meeting10:42
*** gokrokve has quit IRC10:44
*** yaguang has quit IRC10:45
*** dims has joined #openstack-meeting10:46
*** yamamoto has joined #openstack-meeting10:49
*** jlanoux has joined #openstack-meeting10:49
*** epico has quit IRC10:50
*** dims has quit IRC10:50
*** sankarshan is now known as sankarshan_away10:50
*** mchalla has joined #openstack-meeting10:51
*** yamamoto_ has joined #openstack-meeting10:51
*** jlanoux_ has quit IRC10:52
*** jab has quit IRC10:53
*** yamamoto has quit IRC10:54
*** yamamoto_ has quit IRC10:56
*** mchalla has quit IRC10:56
*** emagana has joined #openstack-meeting10:57
*** emagana has quit IRC11:01
*** mrunge_ is now known as mrunge11:09
*** marun_afk has joined #openstack-meeting11:14
*** amotoki_ has joined #openstack-meeting11:15
*** marun_afk is now known as marun11:16
*** daneleblanc has quit IRC11:18
*** e0ne has quit IRC11:19
*** amotoki has quit IRC11:22
*** amotoki_ is now known as amotoki11:22
*** mwagner_lap has quit IRC11:25
*** paragan has joined #openstack-meeting11:27
*** oanufriev has quit IRC11:29
*** dbite has joined #openstack-meeting11:35
*** gokrokve has joined #openstack-meeting11:40
*** dims has joined #openstack-meeting11:42
*** rajeshr has quit IRC11:45
*** gokrokve has quit IRC11:45
*** mestery has quit IRC11:46
*** k4n0 has quit IRC11:46
*** js1123 has joined #openstack-meeting11:46
*** baoli has joined #openstack-meeting11:48
*** dane_leblanc has joined #openstack-meeting11:48
*** alex_xu has joined #openstack-meeting11:48
*** yamamoto has joined #openstack-meeting11:50
*** emagana has joined #openstack-meeting11:51
*** wuhg has quit IRC11:52
*** yamamoto has quit IRC11:55
*** emagana has quit IRC11:55
*** mrunge has quit IRC11:56
*** weshay has joined #openstack-meeting11:56
*** toan-tran has quit IRC11:58
*** mmedvede has joined #openstack-meeting11:58
*** toan-tran has joined #openstack-meeting11:58
*** jtomasek has quit IRC11:59
*** vkmc has joined #openstack-meeting12:00
*** vkmc has quit IRC12:00
*** vkmc has joined #openstack-meeting12:00
*** flaviof_zzz is now known as flaviof12:00
*** mrunge has joined #openstack-meeting12:03
*** jtomasek has joined #openstack-meeting12:03
*** dpaterson has joined #openstack-meeting12:05
*** mestery has joined #openstack-meeting12:06
*** mpaolino has quit IRC12:06
*** doron_afk is now known as doron12:06
*** doron is now known as doron_afk12:07
*** dims has quit IRC12:08
*** dims has joined #openstack-meeting12:08
*** mestery_ has joined #openstack-meeting12:12
*** mestery has quit IRC12:13
*** toan-tran has quit IRC12:14
*** Guest26899 is now known as b3nt_pin12:18
*** b3nt_pin is now known as beagles12:18
*** jckasper_ has quit IRC12:19
*** doron_afk is now known as doron12:20
*** mmedvede has quit IRC12:20
*** eharney has joined #openstack-meeting12:21
*** mpaolino has joined #openstack-meeting12:21
*** rushiagr is now known as rushiagr_away12:22
*** aysyd has joined #openstack-meeting12:24
*** adalbas has joined #openstack-meeting12:25
*** beagles is now known as beagles_brb12:26
*** mwagner_lap has joined #openstack-meeting12:29
*** alex_xu has quit IRC12:29
*** yamamoto has joined #openstack-meeting12:31
*** mmedvede has joined #openstack-meeting12:33
*** Mandell has joined #openstack-meeting12:33
*** kopparam has quit IRC12:34
*** mestery has joined #openstack-meeting12:35
*** kopparam has joined #openstack-meeting12:35
*** mestery_ has quit IRC12:35
*** Mandell has quit IRC12:38
*** baohua has joined #openstack-meeting12:38
*** pnavarro has quit IRC12:39
*** beagles_brb is now known as beagles12:39
*** e0ne has joined #openstack-meeting12:39
*** pnavarro has joined #openstack-meeting12:40
*** shankar has quit IRC12:40
*** kopparam has quit IRC12:40
*** zhhuabj has joined #openstack-meeting12:41
*** masayukig has quit IRC12:44
*** emagana has joined #openstack-meeting12:45
*** emagana has quit IRC12:49
*** jckasper has joined #openstack-meeting12:50
*** masayukig has joined #openstack-meeting12:51
*** dprince has joined #openstack-meeting12:51
*** jckasper_ has joined #openstack-meeting12:51
*** xuhanp has joined #openstack-meeting12:52
*** jckasper has quit IRC12:55
*** dbite has quit IRC12:59
*** tongli has joined #openstack-meeting13:00
*** ildikov_ has quit IRC13:04
*** kenhui has joined #openstack-meeting13:06
*** flaper87 is now known as flaper87|afk13:06
*** ildikov has joined #openstack-meeting13:07
*** ivasev has joined #openstack-meeting13:07
*** mitarun has joined #openstack-meeting13:09
*** Guest44661 is now known as hartsocks13:14
*** rbowen has joined #openstack-meeting13:14
*** ayoung has joined #openstack-meeting13:14
*** schwicht has joined #openstack-meeting13:16
*** sankarshan_away is now known as sankarshan13:20
*** jecarey_ has quit IRC13:21
*** zz_jgrimm is now known as jgrimm13:22
*** xuhanp has quit IRC13:23
*** bknudson has joined #openstack-meeting13:23
*** colinmcnamara has joined #openstack-meeting13:24
*** _nadya_ has joined #openstack-meeting13:25
*** annegent_ has joined #openstack-meeting13:26
*** rushiagr_away is now known as rushiagr13:27
*** dkehn_ has joined #openstack-meeting13:27
*** rharwood has joined #openstack-meeting13:30
*** julim has joined #openstack-meeting13:32
*** thangp has joined #openstack-meeting13:35
*** dkranz has quit IRC13:37
*** jjmb has joined #openstack-meeting13:39
*** emagana has joined #openstack-meeting13:39
*** dkehn_ is now known as dkehnx13:39
*** gokrokve has joined #openstack-meeting13:40
*** jasondotstar has joined #openstack-meeting13:41
*** jswarren has joined #openstack-meeting13:41
*** mitarun has quit IRC13:41
*** tbarron has joined #openstack-meeting13:41
*** mitarun has joined #openstack-meeting13:42
*** emagana has quit IRC13:44
*** gokrokve has quit IRC13:45
*** mitarun has quit IRC13:46
*** timello_ has joined #openstack-meeting13:48
*** neelashah has joined #openstack-meeting13:51
*** dbite has joined #openstack-meeting13:52
*** julienvey has joined #openstack-meeting13:54
*** ityaptin has quit IRC13:54
*** xuhanp has joined #openstack-meeting13:54
sc68cal_hello all13:54
*** sc68cal_ is now known as sc68cal13:55
*** aveiga has joined #openstack-meeting13:55
*** jjmb has quit IRC13:55
xuhanpsc68cal, hello13:56
*** gokrokve has joined #openstack-meeting13:56
*** BrianB__ has joined #openstack-meeting13:58
*** marun has quit IRC13:59
*** sandywalsh has joined #openstack-meeting13:59
sc68cal#startmeeting neutron_ipv613:59
openstackMeeting started Tue Sep  2 13:59:31 2014 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.13:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:59
*** spzala has joined #openstack-meeting13:59
*** openstack changes topic to " (Meeting topic: neutron_ipv6)"13:59
openstackThe meeting name has been set to 'neutron_ipv6'13:59
*** dtantsur has left #openstack-meeting14:00
*** john-davidge has joined #openstack-meeting14:00
sc68calThe only thing I have for discussion today is the progress on the Horizon patch, so if anyone else has things they'd like to discuss please do!14:01
*** marun has joined #openstack-meeting14:01
*** nelsnelson has joined #openstack-meeting14:01
*** john-davidge_ has joined #openstack-meeting14:02
xuhanpsc68cal, do we need to change our meeting time since the WL meeting will start next week?14:03
*** doron is now known as doron_afk14:03
sc68calxuhanp: are they starting next week? I was under the impression is was going to be after the summit?14:03
xuhanpI think I saw one email today saying so but not 100% sure14:04
*** stevemar has joined #openstack-meeting14:04
*** john-davidge has quit IRC14:04
sc68calyep, you are right. Just looked at the ML14:04
*** _d34dh0r53_ is now known as d34dh0r5314:04
*** jjmb has joined #openstack-meeting14:04
baolixuhanp, what is the WL meeting?14:05
xuhanpsorry, typo.14:05
xuhanpthe weekly neutron meeting14:05
*** rbak has joined #openstack-meeting14:06
*** chuckC has quit IRC14:06
*** amotoki has quit IRC14:07
*** haleyb has joined #openstack-meeting14:07
*** prad has joined #openstack-meeting14:07
baolixuhanp, I see. thanks.14:07
*** bcrochet has quit IRC14:07
*** topol has joined #openstack-meeting14:07
xuhanpso I guess we will need to change time if we still want IPv6 meeting to be hold?14:07
sc68calI was going to wait to the summit, but lately I wonder if the subteam and meeting needs to continue - we've got a lot of things done this dev cycle, and we had a lot of consensus to build. Perhaps with the work we've gotten in, it may not need to be a weekly meeting in the future?14:08
*** jjmb1 has joined #openstack-meeting14:08
*** jjmb has quit IRC14:09
BrianB__I think a weekly meeting is still good14:09
*** cdub has joined #openstack-meeting14:09
xuhanpI think it will be great if we have a meeting to discuss what's the next steps14:10
HenryGHow about moving it one hour earlier?14:10
*** jcoufal has quit IRC14:11
baoliit will be conflicting with sr-iov meeting which I need to attend14:11
BrianB__HenryG:that conflicts with sr-iov14:11
sc68calI'm glad people want it to continue - I'll keep running it as long as people attend :)14:11
xuhanphow about one hour later?14:12
*** jjmb has joined #openstack-meeting14:12
xuhanpit's good to keep meetings at one day14:12
*** jjmb1 has quit IRC14:12
*** mitarun has joined #openstack-meeting14:12
sc68calI'm ok with an hour later... although that's pretty brutal for you xuhanp?14:12
xuhanpthat's fine for me too :-)14:12
baolithat sounds good to me14:13
sc68calyeah the upside is it gives the US west coast people a break ;)14:13
*** jcoufal has joined #openstack-meeting14:13
*** jjmb1 has joined #openstack-meeting14:14
sc68calLet me just see if we conflict with anything at 1500 UTC14:14
xuhanpif there is no room for this time in openstack-meeting or openstack-meeting-alt, there is openstack-meeting-314:14
sc68calxuhanp: cool, thanks for checking.14:15
sc68calhmm14:15
sc68caloops, no that's thursday14:16
*** jjmb has quit IRC14:16
sc68calok, so openstack-meeting-3 on tuesdays at 1500UTC?14:16
*** mitarun has quit IRC14:17
sc68calI'll put something on the ML to let everyone check and make sure that works14:17
aveigasounds good14:17
xuhanpsounds great14:17
sc68calxuhanp: I saw you still had some q's from the HA thread on the ML?14:18
xuhanpyep.14:18
*** haleyb_ has joined #openstack-meeting14:18
*** bcrochet has joined #openstack-meeting14:18
baoliactually, it seems that tuesdays utc1500 is open on openstack-meeting-alt14:18
*** otherwiseguy has joined #openstack-meeting14:18
xuhanpbut I just left a new thought today. so I guess I will leave some time for everyone to check it out.14:19
baolixuhanp, right now, the garp is sent to router ports, gateway port, etc.14:19
sc68calHmmm - I think I found a bug in the mailing list software14:19
sc68calhttp://lists.openstack.org/pipermail/openstack-dev/2014-August/044340.html14:19
baolixuhanp, for vrrp to work, would it make sense for it to send the garp to the ports that are configured for vrrp?14:20
sc68calThat e-mail is from xuhanp but it has aveiga as the from in the archive.14:20
aveigasc68cal: nice catch, as I didn't send that14:20
xuhanpsc68cal,  you should search for Sep 114:20
xuhanpI sent it today.14:21
sc68calah ok,14:21
sc68calhttp://lists.openstack.org/pipermail/openstack-dev/2014-September/044602.html14:21
xuhanpthat one should came from aveiga, only he is replying inline so mixed with mine14:21
aveigaI think the issue at hand should really be which method(s) do we want to support for HA14:21
aveigado we want VRRP? Do we just want standby RAs?14:21
aveigado we want options?14:21
*** david-lyle has joined #openstack-meeting14:22
sc68calI know there is some work for vrrp in Neutron - I'd have to do research14:22
xuhanpin the latest code of L3 HA, when HA is enable, keepalived is used to send out GARP. When is not, GARP is sending out by neutron code.14:22
xuhanpjust checked today.14:22
aveigaxuhanp: is that using VRRP for IPv4?14:23
aveigaand is that the only mode supported?14:23
xuhanpI think so since there is no special treat for IPv6.14:23
xuhanpalthough keepalived supports IPv6 VRRP14:23
baolixuhanp, I think that we need to separate the discussion between garp on router ports, and garp on gateway port14:23
aveigaok, so the question is do we want to do just VRRP for IPv6?14:24
xuhanpbaoli, right.14:24
*** johndavidge has joined #openstack-meeting14:24
xuhanpaveiga, I think we need to support HA like IPv4, but it's debatable if VRRP is used.14:25
xuhanpI just use that as an example of not using two LLA for subnet14:25
aveigaxuhanp: I don't question the need for HA, just asking about the methods14:25
aveigaand yes, that makes it easier14:25
aveigahaving only one LLA14:25
xuhanpsince keepalived with VRRP is used for IPv4, I think it's convenient to use for IPv614:26
aveigaI agree14:26
*** john-davidge_ has quit IRC14:26
baolixuhanp, the point I want to make is that garp for router port should be controlled by the higher prototol.14:26
*** mrodden has quit IRC14:26
*** mrodden has joined #openstack-meeting14:27
xuhanpbaoli, so do you understand why currently GARP is used for IPv4 routers?14:27
xuhanpI am confused by that part from the beginning14:27
*** john-davidge has joined #openstack-meeting14:27
*** emagana has joined #openstack-meeting14:27
baolixuhanp, garp for the gateway port is for NAT, I believe, but garp for the router ports, I'm 100% sure.14:27
baolisorry, not 100% sure14:28
xuhanpI thought it's for bridge learning14:28
xuhanpsince the router node changed14:28
xuhanpwe need to update the learning table cache14:28
*** johndavidge has quit IRC14:28
baolixuhanp, yes, that's possible for quick convergence. But the VM sends ARP anyway14:29
xuhanpVM don't need to update ARP if the router IP is not changed, right?14:30
aveigaxuhanp: has the MAC changed?14:30
xuhanpin VRRP, no. The virtual MAC is used.14:30
xuhanpbut in other case, maybe14:30
baolixuhanp, so router ports' ip address changed but mac remains unchanged, it maybe a good thing to send garp, I guess.14:31
*** andreaf has quit IRC14:31
*** emagana has quit IRC14:31
*** mestery_ has joined #openstack-meeting14:31
baoliright now, it seems to be sending it regardless.14:31
*** yamahata has joined #openstack-meeting14:31
aveigabaoli: is it harming anything to send it?14:31
aveigaat the worst, you get a packet that confirms what you already know14:32
aveigaat best, it reconverges on the proper gateway14:32
*** alex_xu has joined #openstack-meeting14:32
baoliaveiga, I don't think it hurts anything14:33
xuhanpmaybe we should talk to the HA code owner to understand more.14:33
*** mestery has quit IRC14:33
xuhanpI see the code change around GARP in the HA code.14:33
*** Mandell has joined #openstack-meeting14:34
*** SridharG has joined #openstack-meeting14:34
xuhanpIf there is a gap to support IPv6 HA, we can fix that.14:34
*** sballe has joined #openstack-meeting14:35
*** mestery_ is now known as mestery14:35
baolixuhanp, maybe it's worthwhile to see the packets while RA is enabled on a router port. We can better understand if garp is needed for router port for ipv614:36
xuhanpbaoli, if we go that way, then there will be two LLA when router failover.14:37
xuhanpVM need to switch to the backup's LLA as route14:37
xuhanpIn VRRP, the previous LLA is used.14:37
*** Leonr has joined #openstack-meeting14:38
baolixuhanp, I'm still thinking about normal case. For HA, I'm thinking that keepalived will do the right thing.14:38
*** Mandell has quit IRC14:38
*** pkoniszewski has quit IRC14:38
xuhanpbaoli, OK14:38
aveigabaoli: yeah, VRRP is fine and normal case will judst need a new RA14:38
aveiganeed to keep valid lifetimes low though14:39
*** thangp has quit IRC14:39
baoliaveiga, good point.14:39
xuhanpaveiga, I think too low increases the overhead?14:40
aveigaxuhanp: it does, but too high means outages during failover14:41
xuhanpexactly14:41
aveigait's a tradeoff14:41
*** dkranz has joined #openstack-meeting14:41
aveigabut RAs aren't that expensive14:41
*** mspreitz has joined #openstack-meeting14:41
*** john-davidge_ has joined #openstack-meeting14:41
xuhanpaveiga, so you are saying since failover causes the new router to send out RA anyway, we don't need additional steps here?14:42
*** sandywalsh has quit IRC14:42
aveigaxuhanp: if you're triggering the standby to become active14:42
aveigait will have to send RAs anyway to be a router14:42
aveigaso yeah14:42
aveigawe should spin up radvd on it and fire away14:43
xuhanpso we need the VM to wait for the last RA to expire and receive the new one?14:43
xuhanpand change it's route to the new LLA?14:43
aveigaxuhanp: that depends on the guest, sadly14:43
aveigasome of them will take the new RA immediately14:44
*** garyh has joined #openstack-meeting14:44
*** kakuma has quit IRC14:44
aveigasome might need to wait for the timeout14:44
baoliit's also possible to deprecate the old RA by sending its lifetime to be 014:44
*** john-davidge has quit IRC14:44
aveigabaoli: spoof send it?14:44
*** jswarren has quit IRC14:45
aveigawe'd haveto have the failover router send it from the old router's LLA14:45
xuhanpthe old route is already dead, so how to do it.14:45
*** wuhg has joined #openstack-meeting14:45
xuhanpthen it falls into the VRRP way.14:45
*** ildikov_ has joined #openstack-meeting14:46
xuhanpin VRRP the new router just send out the old LLA in RA14:46
aveigaxuhanp: we're talking about a non-VRRP mode14:46
*** mitarun has joined #openstack-meeting14:46
xuhanpyes. but we are making the process more and more like VRRP process14:46
xuhanpsince it's invented to solve the same problems here14:47
aveigaxuhanp: this would potentially let you go to DVR on the fly though :-P14:47
xuhanp:-)14:47
aveigajust spin up all the local gateways and take over the RA :)14:47
*** shakamunyi has joined #openstack-meeting14:48
*** jecarey has joined #openstack-meeting14:48
*** n0ano has joined #openstack-meeting14:48
*** ildikov has quit IRC14:49
aveigaso this is a good conversation and all, but is any of this work tied to  a specific blueprint with a timeline?14:49
xuhanpno. it's triggered by a bug14:49
xuhanpsince ARP doesn't work for IPv6.14:49
aveigaah, ok14:49
baolixuhanp, so are we saying that garp on router port will be taken care of by the higher level protocol? In other words, l3 agent doesn't need to send garp blindly.14:50
baolifor ipv614:50
xuhanpfor IPv4 I think that's useful14:50
aveigawell, there's no garp for v614:50
xuhanpbut for IPv6, seems not14:50
aveigaso it's either a new RA or unsolicited NA14:50
xuhanpyep14:51
baoliaveiga, that's what I mean.14:51
aveigaif it's an RA< then radvd does it normally14:51
aveigaif it's NA, then we have to manually craft the packet14:51
xuhanpunsolicited NA is useful if the LLA is not changed.14:51
*** eharney has quit IRC14:51
xuhanpit will have the same benefit as GARP.14:51
aveigaif the LLA is not changed, then why do we need anything?14:51
aveigathe MAC and the LLA aren't changing, so the route should still work14:52
aveigathe DAD packet will update the switches14:52
xuhanpthe port could changed, so we need that for switch learning?14:52
*** nshaikh has quit IRC14:52
xuhanpthat's my thoughts not 100% sure14:52
aveigaunless we aren't waiting to instantiate the listener on the failover router14:53
aveigain which case, yes an NA is needed14:53
xuhanpaveiga, yes.14:53
*** mdenny has joined #openstack-meeting14:53
*** padkrish has joined #openstack-meeting14:53
xuhanpif LLA is changed, the unsolicited NA is useless after all, right?14:54
*** Riddhi has joined #openstack-meeting14:55
aveigaif LLA is changed, then a new RA is required14:55
xuhanpyep14:55
aveigawhich will cover for the NA as well14:55
*** Riddhi has quit IRC14:55
*** carl_baldwin has joined #openstack-meeting14:56
*** Riddhi has joined #openstack-meeting14:56
xuhanpI can leave these comments in code review and see other's opinions14:56
*** chuckC has joined #openstack-meeting14:56
aveiga+114:56
*** mpaolino has quit IRC14:56
baolixuhanp, there is ra dump facility you can use to see what would happen with the scenairos you mentioned, also tshark can help find out the packets sent to the network14:56
xuhanpbaoli, good to know. I will try that.14:57
baolixuhanp, that will help figured out if NA is needed14:57
xuhanpbaoli, ok14:58
*** jtomasek has quit IRC15:00
sc68calCool stuff everyone15:00
sc68calthanks for coming!15:00
*** atiwari has joined #openstack-meeting15:00
sc68caluntil next week!15:00
sc68cal#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Tue Sep  2 15:00:36 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-09-02-13.59.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-09-02-13.59.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-09-02-13.59.log.html15:00
n0ano#startmeeting gantt15:01
openstackMeeting started Tue Sep  2 15:01:02 2014 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: gantt)"15:01
openstackThe meeting name has been set to 'gantt'15:01
n0anoanyone here to talk about the scheduler?15:01
bauzas_\o15:01
mspreitzyes15:01
*** bauzas_ is now known as bauzas15:01
*** john-davidge_ has quit IRC15:01
*** aveiga has left #openstack-meeting15:01
n0anobauzas, you're supposed to catching up on sleep since you don't get any for about the next 6 months :-)15:02
bauzasn0ano: eh15:02
*** mtanino has joined #openstack-meeting15:02
bauzasn0ano: last night was pretty good for me, not for my wife ;)15:02
n0anoin my family bad night for one pretty much meant a bod night for the other15:03
*** itzikb has joined #openstack-meeting15:03
*** yamahata has quit IRC15:03
bauzasbut just coming back from 3 days PTO :)15:03
bauzasn0ano: :)15:03
n0anoanyway, let's get started...15:03
bauzasjaypipes seems to be not around15:04
n0anooccurs to me I put the items in the wrong order so let's start with15:04
n0ano#topic next steps15:04
*** yamahata has joined #openstack-meeting15:04
*** openstack changes topic to "next steps (Meeting topic: gantt)"15:04
bauzaseh eh15:04
n0anoas everyone should be aware the isolate scheduler DB bp was rejected for Juno...15:04
*** marekd is now known as marekd|away15:04
n0anoI've started a thread to address what I think are problems with the current approval process...15:04
bauzasn0ano: yeah, thanks for raising up the discussion in the list15:04
*** gongysh has joined #openstack-meeting15:04
n0anoignoring that, what do we do to keep momentum for gantt going...15:05
bauzasn0ano: as I'm the proposer, I was expecting to not reply on that specific problem15:05
bauzasn0ano: here, the problem was about the -2 going one week before FPF15:06
n0anomy thought is that this is a bump but not a major blockage, as soon as Kilo opens up we will just re-propose the BP, hopefully get it approved as people have more time to think about it, and we still do the split early in the Kilo cycle15:06
bauzasn0ano: so I guess that discussion is related to all the ones about how we can improve design summits, reviewing slots etc.15:06
*** nosnos has quit IRC15:06
bauzasn0ano: well, that's not that easy15:06
bauzasn0ano: the concerns were good15:06
bauzasn0ano: I mean, we were having a dependency on ERT15:07
*** nosnos has joined #openstack-meeting15:07
bauzasn0ano: and the current interface is not so good15:07
*** shakamunyi has quit IRC15:07
bauzasn0ano: so, I'm thinking about proposing a new iteration as we discussed last week15:07
n0anobauzas, I'm hoping ERT will be resolved this week and then we can fix our BP, with or without ERT as appropriate15:07
bauzasn0ano: oh, you didn't catch them15:07
*** alex_xu has quit IRC15:08
*** sballe_ has joined #openstack-meeting15:08
bauzasn0ano: ERT revert patch is abandoned, but Scheduler related one has been -2 today15:08
*** xuhanp has quit IRC15:08
n0anoI was kind of fixated on the BP review process, what did I miss15:08
*** sballe has quit IRC15:08
bauzasn0ano: and today is FF, so that means the scheduler side won't be there until Kilo opens15:08
bauzasn0ano: one sec, giving you the reviews15:09
*** flaviof is now known as flaviof_zzz15:09
* bauzas is coming back from vacation but still on page, eh ;)15:09
n0anobauzas, that's a given so, as I said, we get prepared and re-propose our BP as soon as Kilo opens15:09
*** gongysh has quit IRC15:09
*** rakesh_hs has quit IRC15:10
bauzashttps://review.openstack.org/#/c/61773/ ERT scheduler side has been -2 for Junoi15:10
bauzasn0ano: that's what I'm saying, I think we need to look at other ways to do the bp15:10
n0anobauzas, question is, what are the odds that they will re-propose ERT?15:10
bauzasn0ano: for both the reasons that ERT won't be there when Kilo opens, and also because the concerns were good15:11
bauzasn0ano: I guess Paul will ask for a FFE or resubmit it for Kilo15:11
*** julienvey has quit IRC15:11
*** yamahata has quit IRC15:11
bauzasn0ano: but I can't speak on behalf of it15:11
*** shakamunyi has joined #openstack-meeting15:11
*** nosnos has quit IRC15:11
n0anoso the question is should we wait for Paul to resolve ERT or should we just work around it15:12
bauzass/it/him (Paul is not an object, although he's working on some patches about them...)15:12
bauzasn0ano: as we discussed last week, I will propose another way15:12
*** julienvey has joined #openstack-meeting15:12
bauzasn0ano: the idea is to pass Objects from RT to Sched15:12
n0anopersonally, I would prefer to not wait, I would prefer to work around it and, if need be, redo things when/if ERT is finalized.15:12
*** mspreitz_ has joined #openstack-meeting15:12
n0anobauzas, that works for me15:13
bauzasn0ano: well, the design is really different if we don't go with ERT15:13
*** kevinconway has joined #openstack-meeting15:13
bauzasn0ano: and IMHO, that's more "resilient" in terms of community approval :)15:13
n0anoyeah but I don't feel we should wait on it, deal with ERT only when it's finalized15:13
*** pberis has quit IRC15:13
bauzasn0ano: agreed that's top prio, but we need to sort some things previously15:14
*** markmcclain has joined #openstack-meeting15:15
bauzasn0ano: seriously, the current way is pretty crap...15:15
n0anoso, if I understand, you're going to update the current BP and then we can look at implementing based upon that new design - right?15:15
*** gokrokve has quit IRC15:15
bauzasn0ano: yeah15:16
*** markmcclain has quit IRC15:16
*** mspreitz has quit IRC15:16
bauzasn0ano: I was just expecting more support from others than just you and me15:16
bauzas:)15:16
bauzasn0ano: ie. I need to discuss with jay first15:16
n0ano#action bauzas to update the isolate scheduler DB BP15:16
bauzasthanks :)15:16
bauzaswill mark it as WIP, until Kilo spec template is there15:17
bauzasbecause there are chances that the template will change15:17
n0anowe're in agreement, getting some sort of concensus from Jay would be good but I'm willing to push through others if that's a problem.15:17
bauzasn0ano: indeed15:17
bauzasn0ano: hence I'm waiting to see what will be the Kilo process for blueprints15:17
n0anobauzas, I doubt the template will change dramitically, just a tweak or two15:18
bauzasn0ano: because atm that's unclear15:18
n0anos/dramit/dramat15:18
bauzasn0ano: I'm not really waiting for the template, I'm waiting for big decisions like runways and design summit reboot15:18
* n0ano needs to work on spellin skills15:18
*** markmcclain has joined #openstack-meeting15:18
* n0ano and typing skills15:18
*** flaviof_zzz is now known as flaviof15:19
bauzasn0ano: the design summit format will change for Paris15:19
bauzasn0ano: and the cores's reviewing process will probably change for Kilo15:19
*** yeungp has joined #openstack-meeting15:19
*** gokrokve has joined #openstack-meeting15:19
n0anothe format will change but we will still push for gantt no matter what the procedure we have to follow15:20
*** matrohon has quit IRC15:20
*** ominakov has joined #openstack-meeting15:20
n0anoas I've said in the past, no one has objected to gantt, the only issues have been how & when15:20
bauzasn0ano: of course, but coming from a patch where 54 iterations were necessary for having merged it, I can just say that sometimes, you need to have visibility before doing anything15:20
*** zhhuabj has quit IRC15:21
n0anobauzas, completely agree (don't know whether to laugh or cry over that)15:21
bauzasn0ano: the "how" is sometimes requiring more than 3 months for getting it done15:21
n0anoremember, I started the gantt work over a year ago and we're still debating it15:21
bauzasn0ano: the golden rule for Nova is patience15:21
bauzasn0ano: indeed, I was sitting 2 rows behind you in HKG :)15:22
*** Murali has joined #openstack-meeting15:22
n0anoHKG, I started this before Portland :-)15:22
bauzasthen that's not 1 year... :)15:22
*** jecarey_ has joined #openstack-meeting15:23
bauzasanyway, reviewing the NUMA patches was pretty worth it15:23
bauzasI now totally understand ndipanov's concerns15:23
*** jcoufal has quit IRC15:24
n0anoOh, you're right, I can't count, it was after Grizzly I started (I think, too long ago)15:24
*** eharney has joined #openstack-meeting15:24
mspreitz_bauzas: can you explain briefly? I have not been following the NUMA stuff15:24
bauzasatm, RT is pretty good for consuming CPUs and memory, but very bad at counting more complex objects15:24
n0anoanyway, bottom line is you get to redo the BP and I get to needle the powers that be over review process15:24
*** esker has joined #openstack-meeting15:24
*** che-arne has quit IRC15:24
bauzasmspreitz_: well,  the problem is really about details15:24
bauzasmspreitz_: like what you get is not typed15:24
bauzasmspreitz_: so you have to doublecheck what you get15:25
*** BrianB__ has quit IRC15:25
bauzasmspreitz_: you also have to do some extra calls for getting some info15:25
mspreitz_bauzas: are you explaining the NUMA concerns?15:25
bauzasmspreitz_: yeah, all the fixme stuff these folks were doing15:25
mspreitz_OK, thanks.15:26
bauzasmspreitz_: I can just summarize that the problem is that you're providing non-typed and non-validated dictionaries15:26
bauzasmspreitz_: and based on where you look at these bits, they are either serialized or not15:26
mspreitz_I have to admit I have not been following the details, since it became clear a while ago that it would take a long time to get progress here15:26
*** simon-AS559 has quit IRC15:27
bauzasmspreitz_: seriously, I understand15:27
*** emagana has joined #openstack-meeting15:27
bauzasmspreitz_: here the problem with isolate-sched-db is that we're not counting cpus or ram, but apples and bananas15:27
*** baohua has quit IRC15:27
bauzasmspreitz_: I mean, real complex objects15:27
bauzasso we kinda need some formalization15:28
*** emagana has quit IRC15:28
bauzasand as I said last week, we *already* have the toolbox for it, that's called.... objects15:28
*** emagana has joined #openstack-meeting15:28
mspreitz_thanks15:29
bauzasanyway, I'll have to leave earlier today, we can maybe move on ?15:29
mspreitz_yes15:29
n0anobauzas, fer sur15:29
n0ano#topic opens15:30
*** openstack changes topic to "opens (Meeting topic: gantt)"15:30
*** kmartin has joined #openstack-meeting15:30
n0anoanyone have anything new for today?15:30
*** SridharG has quit IRC15:30
bauzasI'm glad to say scheduler-lib is merged15:30
n0ano+115:30
* bauzas silently says hurrah15:30
* n0ano vocally says hurrah15:30
bauzasthat will ease the next steps discussed previously15:31
n0anoanything else?15:31
bauzasyup15:31
bauzashttps://review.openstack.org/#/c/117042/ that's something prerequisite for the work15:32
*** nelsnelson has quit IRC15:32
bauzasthe idea discussed previously is to provide ComputeNode objects to Scheduler15:32
*** annegentle has quit IRC15:32
*** mattgriffin has joined #openstack-meeting15:32
bauzasbut unfortunately, ComputeNode is having a FK on Services for the bad or the good15:32
bauzasso we need to do some prework about that, and this patch is doing that15:33
bauzasbecause that makes no sense to give to Scheduler something having a dependency on anything else15:33
*** mspreitz has joined #openstack-meeting15:33
n0anohow does this relate to the change to not send those updates unless something changes, there's no longer an update every 60 secons15:33
*** pnavarro has quit IRC15:33
*** mspreitz_ has quit IRC15:34
*** dbite_ has joined #openstack-meeting15:34
bauzasn0ano: this is not related, here is the patch is about creating the DB entry at startup15:34
bauzasbut the updates are still done the same way, ie. checking if updated or not15:34
*** dbite_ has quit IRC15:34
*** dbite_ has joined #openstack-meeting15:35
bauzasn0ano: the problem was that we were looking the existence of an object every 60 secs15:35
bauzasn0ano: your check is not before that, but after IIRC15:35
bauzasn0ano: ie. before updating the DB15:36
*** rkofman has joined #openstack-meeting15:36
n0anoI though the DB entry was already created at startup15:36
bauzasn0ano: nope15:36
bauzasn0ano: not exactly15:36
*** colinmcnamara has quit IRC15:36
bauzasn0ano: the update_avail_resource method was called when nova-compute was booting15:37
bauzasn0ano: because of a post-hook mechanism15:37
*** dbite has quit IRC15:37
bauzasn0ano: but the check was still done every 60 secs15:37
bauzasn0ano: here we refactor where we look at services table, that's really helpful15:38
n0anoI have to study the code, I don't understand, let me try and understand this first15:38
*** primeministerp has joined #openstack-meeting15:38
*** primemin1sterp has joined #openstack-meeting15:38
*** changbl has joined #openstack-meeting15:38
*** primemin2sterp has joined #openstack-meeting15:38
*** otoolee has quit IRC15:39
bauzasn0ano: sure15:39
bauzasthat's it for me15:39
n0anoOK, unless there's anything else15:39
n0anoI'll thank everyone and we'll talk next week.15:40
n0ano#endmeeting15:40
mspreitzthanks15:40
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:40
openstackMeeting ended Tue Sep  2 15:40:08 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-09-02-15.01.html15:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-09-02-15.01.txt15:40
openstackLog:            http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-09-02-15.01.log.html15:40
bauzasthanks15:40
*** mitarun has quit IRC15:42
*** cjellick has joined #openstack-meeting15:43
*** kebray has joined #openstack-meeting15:43
*** mitarun has joined #openstack-meeting15:43
*** padkrish has quit IRC15:44
*** jjmb1 has quit IRC15:44
*** rmoe has quit IRC15:45
*** evgenyf has quit IRC15:45
*** gyee has joined #openstack-meeting15:45
*** shakamunyi has quit IRC15:46
*** mflobo has quit IRC15:46
*** primemin2sterp has quit IRC15:46
*** primemin1sterp has quit IRC15:47
*** primeministerp has quit IRC15:47
*** haleyb_ has quit IRC15:47
*** mflobo has joined #openstack-meeting15:48
*** primeministerp has joined #openstack-meeting15:48
*** primemin1sterp has joined #openstack-meeting15:48
*** mitarun has quit IRC15:48
*** primemin1sterp has quit IRC15:49
*** ominakov has quit IRC15:49
*** primeministerp has quit IRC15:49
*** primeministerp has joined #openstack-meeting15:49
*** radez_g0` is now known as radez15:49
*** AlkaD has joined #openstack-meeting15:50
*** comay has joined #openstack-meeting15:50
*** acoles has quit IRC15:51
*** devlaps has joined #openstack-meeting15:53
*** lazy_prince has joined #openstack-meeting15:54
*** Longgeek has quit IRC15:54
*** ominakov has joined #openstack-meeting15:54
*** ominakov has quit IRC15:54
*** sleipneir012 has joined #openstack-meeting15:54
*** marun_ has joined #openstack-meeting15:54
*** lcheng has joined #openstack-meeting15:55
*** padkrish has joined #openstack-meeting15:56
*** padkrish has quit IRC15:56
*** rkofman has quit IRC15:56
*** andreaf has joined #openstack-meeting15:57
*** marun has quit IRC15:57
*** padkrish has joined #openstack-meeting15:57
*** sballe_ has quit IRC15:58
*** rkofman has joined #openstack-meeting15:58
*** afazekas has quit IRC15:59
*** simon-AS559 has joined #openstack-meeting15:59
*** oanufriev has joined #openstack-meeting16:00
*** dane_leblanc has quit IRC16:01
*** yamamoto has quit IRC16:01
*** simon-AS5591 has joined #openstack-meeting16:01
*** mitarun has joined #openstack-meeting16:01
*** acoles has joined #openstack-meeting16:01
*** julim has quit IRC16:01
primeministerp#startmeeting hyper-v16:02
openstackMeeting started Tue Sep  2 16:02:08 2014 UTC and is due to finish in 60 minutes.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: hyper-v)"16:02
openstackThe meeting name has been set to 'hyper_v'16:02
primeministerphey everyone16:02
lazy_princehi all..16:02
alexpilottihi there16:02
primeministerpalexpilotti: hey now16:02
primeministerpociuhandu: hi tavi16:03
primeministerpluis_fdez: hi luis16:03
*** yamamoto has joined #openstack-meeting16:03
alexpilottiprimeministerp: lazy_prince is interested in how to test the Windows disk image builder16:03
primeministerpo nice16:03
primeministerpwe can discuss that too16:03
*** andreaf has quit IRC16:04
primeministerpalexpilotti: do we want to start there?16:04
alexpilottijust started the conversation on #openstack-hyper-v and the timing was perfect for bringing it to the attention at the meeting16:04
*** Murali has quit IRC16:04
*** shakamunyi has joined #openstack-meeting16:04
lazy_princewell.. we can discuss that at the end.. after all formal agenda is done..16:04
alexpilottiI suggest so16:04
primeministerplazy_prince: we can start here16:04
*** eghobo has joined #openstack-meeting16:04
*** ominakov has joined #openstack-meeting16:04
*** Murali has joined #openstack-meeting16:04
primeministerp#topic windows-disk-image-builder16:04
*** openstack changes topic to "windows-disk-image-builder (Meeting topic: hyper-v)"16:04
*** simon-AS559 has quit IRC16:04
*** sballe has joined #openstack-meeting16:04
primeministerpalexpilotti: is the discussion still at "where it should ruN"16:05
*** rmoe has joined #openstack-meeting16:05
lazy_princeokay.. so right now, openstack is resisting the tool bcoz we dont have testing framework for wordows related stuff there..16:05
primeministerplazy_prince: understood, it's kinda required16:05
primeministerplazy_prince: so you'd like us to pick up those tests in our ci?16:06
*** julienvey has quit IRC16:06
lazy_princeso i checked with google and there were some linux alternatives available for DISM, WIM etc.. but could not find anything for powershell...16:06
*** jjmb has joined #openstack-meeting16:06
*** eghobo has quit IRC16:06
primeministerpmeaning if you wanted to run the image creation on linux only16:06
alexpilottilazy_prince: there are a bunch of alternatives, but those won’t have MSFT support, which might be a concern16:07
lazy_princeyes. i guess, then only openstack will agree for its adoption..16:07
lazy_princeale: yup. i agree16:07
*** dhu_ has quit IRC16:08
*** yamamoto has quit IRC16:08
lazy_princebut i wanted to have minimal tests in openstack CI using linux tools and a full fleged tests using HyperV ci..16:08
*** sleipneir012 has quit IRC16:08
*** davidlenwell_ is now known as davidlenwell16:08
*** itzikb has quit IRC16:08
lazy_princeso that it gets adopted as well as tested too..16:09
lazy_princedoes it makes sense..?16:09
primeministerpyeah thinking16:09
primeministerpso do you know what will be needed to adquately test it?16:10
*** otoolee- has joined #openstack-meeting16:10
*** dane_leblanc has joined #openstack-meeting16:11
primeministerplazy_prince: ^16:11
*** ominakov has quit IRC16:11
*** padkrish has quit IRC16:11
*** morganfainberg_Z is now known as morganfainberg16:11
lazy_princeyup.. we currently plan to put the code on stackforge. I hope that should not be an issue for integrating with HyperV CI..16:11
lazy_princeand so we just need the tool to create a basic image for now and then test it on a VM..16:11
lazy_princelater on, we can extend the tests as and when we extend the tool..16:12
*** natarajk has joined #openstack-meeting16:12
lazy_princenow the question is where do i start..16:13
*** annegent_ has quit IRC16:13
*** annegent_ has joined #openstack-meeting16:14
*** simon-AS5591 has left #openstack-meeting16:14
primeministerplazy_prince: so my only issue here16:14
primeministerpis that we currently already have a set of tools which create windows images16:14
primeministerpfor anything16:15
primeministerpwhich we currently consume16:15
*** davidlenwell is now known as meatpopcicle16:15
*** meatpopcicle is now known as davidlenwell16:15
primeministerpand would ideally need to test w/in our ci first16:15
primeministerplazy_prince: would it make sense to discuss combining our efforts there?16:15
lazy_princeaha.. thats okay.. i am not asking to update your tests..16:16
primeministerplazy_prince: it's not a matter of updating our tests16:16
lazy_princebut all i am asking it to test it..16:16
primeministerpwe already have stuff for creating windows images16:16
*** jmontemayor has joined #openstack-meeting16:16
primeministerpi.e. a windows-image-builder16:16
*** mestery_ has joined #openstack-meeting16:16
primeministerpnow we create images as virtual16:17
primeministerpbut they can be preped for physical w/ the exact same code we already ahve16:17
*** sballe has quit IRC16:17
*** samcdona has joined #openstack-meeting16:17
lazy_princeok i get it..16:17
*** andreaf has joined #openstack-meeting16:17
primeministerplazy_prince: I'm looking at it from the perspective it makes sense to collaborate around the one tool which we already use in our ci16:18
*** jdurgin has joined #openstack-meeting16:18
primeministerplazy_prince: and not duplicate efforts16:18
*** andreaf has quit IRC16:18
lazy_princeI can take a look at it if there is a public repo available..16:18
*** samcdona has quit IRC16:18
primeministerpyes there is16:18
*** andreaf has joined #openstack-meeting16:18
*** sbalukoff1 has quit IRC16:18
lazy_princehowever, my goal was to create a tool to generate Image without standing up a VM..16:19
alexpilottilazy_prince: https://github.com/cloudbase/windows-openstack-imaging-tools16:19
primeministerpalexpilotti: do you mind sending it to them16:19
primeministerplazy_prince: how?16:19
alexpilottiprimeministerp: ^16:19
*** emagana has quit IRC16:19
primeministerplazy_prince: that's practically impossible16:19
*** padkrish has joined #openstack-meeting16:19
*** AlkaD has quit IRC16:19
*** padkrish has quit IRC16:19
*** mestery has quit IRC16:19
primeministerplazy_prince: you'd have to dd it off the hw16:19
lazy_princeusing powershell DISM16:19
*** emagana has joined #openstack-meeting16:19
*** padkrish has joined #openstack-meeting16:20
lazy_princewe can create a vhd and then layoff everything on it using DISM..16:20
*** samcdona has joined #openstack-meeting16:20
*** shakamunyi has quit IRC16:20
primeministerplazy_prince: i'm thinking about the process16:20
lazy_princewe have tested it and it is definately possible...16:20
alexpilottilazy_prince: would you mind pasting the link to the repo w your tool?16:20
lazy_princesure.. give me a sec..16:21
primeministerplazy_prince: i'm trying to understand where in the process you are creating an image16:21
alexpilottilazy_prince: it is possible, it’s using standard DISM tools, so it’s all ok16:21
primeministerpalexpilotti: on the backside of an unattended install16:21
alexpilottilazy_prince primeministerp we tested it as well16:21
*** MaxV has quit IRC16:21
primeministerp^?16:21
lazy_princehttps://github.com/slokesh184/windows-diskimage-builder.git16:22
lazy_princethats great...16:22
primeministerplazy_prince: reading now16:23
*** hrybacki has joined #openstack-meeting16:23
*** nelsnelson has joined #openstack-meeting16:23
lazy_princefrom testing perspective, it should be fairly simple.. I think, everyone may need time to go through the tool, experiment with it..16:23
*** rushil has joined #openstack-meeting16:24
lazy_princeand then probably, we can discuss about it in the next meeting.16:24
lazy_princeis that okay..?16:24
*** Riddhi has quit IRC16:24
*** sbalukoff has joined #openstack-meeting16:24
*** Riddhi has joined #openstack-meeting16:25
primeministerplazy_prince: that's fine too16:25
*** jlanoux has quit IRC16:25
lazy_princethe future goal is to bring the tool on par with linux diskimage-builder..16:25
primeministerplazy_prince: let's setup a call if possible to discuss16:25
primeministerplazy_prince: but we'll need to take a look at it first16:26
lazy_princethat should be fine with me..16:26
*** mestery has joined #openstack-meeting16:26
primeministerplazy_prince: perfect, if you want send some times which work for you at ppouliot@microsoft.com16:26
primeministerpok16:27
primeministerplet's move on16:27
primeministerp#topic development updates16:28
*** openstack changes topic to "development updates (Meeting topic: hyper-v)"16:28
lazy_princesure.. I will check with my team and will send the timings to you.. do you have any prefered time that you want us to consider..?16:28
*** ominakov has joined #openstack-meeting16:28
primeministerplazy_prince: EST is best for me16:28
primeministerpI'm on the east coast16:28
primeministerpalexpilotti: updates?16:28
lazy_princeokay.. well I am on IST..16:28
primeministerplazy_prince: hmm16:29
primeministerplazy_prince: we'll figure something out16:29
primeministerplazy_prince: send some options16:29
alexpilottilazy_prince: are you coming to Paris by any chance?16:29
*** mestery_ has quit IRC16:30
*** marun_ has quit IRC16:30
*** padkrish has quit IRC16:30
*** ngoswami has quit IRC16:30
*** marcoemorais has joined #openstack-meeting16:31
lazy_princeyup.. will do do.. I cant say now, if I will be coming to paris.. but if I or anyone from my team travels, i will ask them to talk to you16:31
*** pnavarro has joined #openstack-meeting16:31
*** rushiagr is now known as rushiagr_away16:32
*** cdub has quit IRC16:32
alexpilottiok tx!16:32
*** vijendar has joined #openstack-meeting16:32
alexpilottisome quick updates, since we started the topic16:32
alexpilottiNova blueprints are all in16:33
alexpilottiwe have one relatively new one, which is the sofy shutdown16:33
alexpilotti*soft shutdown16:33
alexpilottiit merged recently for KVM and we sent the patch for Hyper-V16:34
*** safchain has quit IRC16:34
alexpilottishould hopefully merge today16:34
alexpilottihttps://review.openstack.org/#/c/111291/16:35
alexpilottiwaiting for CI votes16:35
*** padkrish has joined #openstack-meeting16:35
alexpilottion the CInder side, we were blocked by a refactoring patch which merged last Friday16:36
alexpilottiwe rebased the patches and today they are under review16:36
alexpilottihttps://review.openstack.org/#/c/106046/16:37
alexpilotti#link https://review.openstack.org/#/c/106057/16:37
alexpilotti(the latter must be rebased on top of the first one)16:37
alexpilottifor the rest all teh Tempest and Devstack patches merged16:37
primeministerpalexpilotti: awesome16:37
alexpilottiwe have a new one for Tempest (neutron)16:37
alexpilottihttps://review.openstack.org/#/c/118167/16:38
*** ildikov_ has quit IRC16:38
alexpilottibut for Tempest we have no issues with code freeze16:38
primeministerp#link https://review.openstack.org/#/c/111291/16:38
*** leeantho has joined #openstack-meeting16:38
alexpilottiso it’s on a lower priority compared to the remaining BPs16:38
primeministerp#link https://review.openstack.org/#/c/118167/16:38
*** yamamoto has joined #openstack-meeting16:38
primeministerpalexpilotti: ok16:39
*** otherwiseguy has quit IRC16:39
*** jlibosva has quit IRC16:39
alexpilottiI’ll add a full report on the bug fixes on teh next meeting16:39
primeministerpalexpilotti: also I'm hoping we can light up the livemigration tests next week16:39
*** colinmcnamara has joined #openstack-meeting16:39
alexpilottiyep, all teh Tempest work can be used right away in the CI since it merged16:39
primeministerpociuhandu: anything to add?16:39
primeministerpluis_fdez: ?16:39
primeministerpif not I think we're good for now16:40
primeministerplazy_prince: thanks for participating I look for forward to our followon16:40
primeministerp#endmeeting16:40
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:40
openstackMeeting ended Tue Sep  2 16:40:39 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2014/hyper_v.2014-09-02-16.02.html16:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2014/hyper_v.2014-09-02-16.02.txt16:40
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2014/hyper_v.2014-09-02-16.02.log.html16:40
*** rushil has left #openstack-meeting16:41
*** andreykurilin_ has joined #openstack-meeting16:42
*** e0ne has quit IRC16:42
*** yamamoto has quit IRC16:43
*** padkrish has quit IRC16:43
*** pballand has joined #openstack-meeting16:44
*** ociuhandu has left #openstack-meeting16:45
*** s3wong has joined #openstack-meeting16:45
*** gokrokve has quit IRC16:47
*** jtomasek has joined #openstack-meeting16:48
*** varora has left #openstack-meeting16:48
*** ygbo has quit IRC16:49
*** ivar-lazzaro has joined #openstack-meeting16:52
*** beagles is now known as beagles_brb16:52
*** paragan has quit IRC16:52
*** doron_afk has quit IRC16:53
*** matiu_ has quit IRC16:54
*** derekh has quit IRC16:55
*** luqas has quit IRC16:55
*** sballe has joined #openstack-meeting16:55
*** SumitNaiksatam has quit IRC16:56
*** amcrn has joined #openstack-meeting16:58
*** rkofman has left #openstack-meeting16:58
*** olkonami has joined #openstack-meeting16:58
boris-42#startmeeting Rally16:59
openstackMeeting started Tue Sep  2 16:59:30 2014 UTC and is due to finish in 60 minutes.  The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot.16:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:59
*** sballe_ has joined #openstack-meeting16:59
*** openstack changes topic to " (Meeting topic: Rally)"16:59
openstackThe meeting name has been set to 'rally'16:59
*** colinmcnamara has quit IRC16:59
*** RainbowBastion has joined #openstack-meeting16:59
*** mattgriffin has quit IRC16:59
*** rkofman1 has joined #openstack-meeting16:59
*** reed has joined #openstack-meeting16:59
*** colinmcnamara has joined #openstack-meeting16:59
boris-42olkonami andreykurilin_ marcoemorais RainbowBastion coolsvap hi guys16:59
RainbowBastionhi there17:00
andreykurilin_hi!17:00
*** lazy_prince is now known as killer_prince17:01
boris-42let's wait a bit for others17:01
andreykurilin_ok:)17:02
msdubovhi!17:02
*** sballe has quit IRC17:03
boris-42msdubov oh hi there17:03
*** bdpayne has joined #openstack-meeting17:04
*** harlowja has joined #openstack-meeting17:04
boris-42harlowja hi there17:04
*** cody-somerville has joined #openstack-meeting17:04
*** sballe has joined #openstack-meeting17:04
harlowjaboris-42 yo yo17:04
harlowjasup dawg17:04
*** Mandell has joined #openstack-meeting17:04
boris-42okay i think we can start17:05
*** MaxV has joined #openstack-meeting17:05
olkonamihi17:05
*** Mandell has quit IRC17:06
boris-42#topic @Validation refactoring17:06
*** openstack changes topic to "@Validation refactoring (Meeting topic: Rally)"17:06
boris-42Okay yesterday we merged quite big patch17:07
boris-42https://review.openstack.org/#/c/111989/717:07
*** rushiagr_away is now known as rushiagr17:07
*** Mandell has joined #openstack-meeting17:07
boris-42that fixes tons of bugs & improves usability of validation17:07
boris-42woot17:07
*** cdub has joined #openstack-meeting17:07
boris-42#topic Benchmarking with already existing users17:07
*** openstack changes topic to "Benchmarking with already existing users (Meeting topic: Rally)"17:07
*** skata has joined #openstack-meeting17:07
*** sballe_ has quit IRC17:07
boris-42me and RainbowBastion are working on this topic17:07
boris-42feature request is https://github.com/stackforge/rally/blob/master/doc/feature_request/LDAP_support.rst17:08
boris-42and there are 2 patches on reviwe17:08
boris-42https://review.openstack.org/#/c/117302/17:08
boris-42this and17:08
boris-42https://review.openstack.org/#/c/116766/17:08
boris-42it's just first part17:08
boris-42that will allow to extend deployments (to make them contain as well users)17:09
*** yamamoto has joined #openstack-meeting17:09
boris-42after that we will need to rework a bit benchmark.engine and probably create (existing_users context)17:09
boris-42and that's all17:09
boris-42so we are quite close to this finishing this task17:09
boris-42any questions?17:10
*** SumitNaiksatam has joined #openstack-meeting17:10
*** rediskin has joined #openstack-meeting17:10
RainbowBastionI just need to fix up some the test_engine unit tests in order for it to pass Jenkins and it should be done on my end.17:10
msdubovShouldn't one of those patches be "needed" by the other?17:11
*** SridharG has joined #openstack-meeting17:11
*** hrybacki_ has joined #openstack-meeting17:11
boris-42msdubov not they are quite independent17:11
*** SridharG has quit IRC17:11
*** cody-somerville has quit IRC17:11
msdubovboris-42 Okay just to make sure17:12
boris-42RainbowBastion actually you'll need to do a bit more cleanup17:12
*** skata has quit IRC17:12
RainbowBastionboris-42 okay, we can discuss that after the meeting17:12
boris-42RainbowBastion ya I'll left some comments17:12
*** _nadya_ has quit IRC17:13
boris-42RainbowBastion actually it's very simple (you just don't need to initialize with users scenario runner)17:13
boris-42RainbowBastion https://github.com/stackforge/rally/blob/master/rally/benchmark/runners/base.py#L15717:13
boris-42RainbowBastion you don't need endpoints anybmore17:13
*** hrybacki has quit IRC17:13
*** yamamoto has quit IRC17:13
*** mattgriffin has joined #openstack-meeting17:13
boris-42okay let's move to next topic17:14
*** rook has joined #openstack-meeting17:14
boris-42#topic Refactoring ReadTheDocs17:14
*** openstack changes topic to "Refactoring ReadTheDocs (Meeting topic: Rally)"17:14
boris-42msdubov could you provide some details why and what we are going to do17:14
msdubovFirst, we want to make the docs much simpler to get through for newcomers17:15
rookrook here =)17:15
msdubovTo achieve that, we've analyzed what different groups of users might wish to see here17:15
boris-42rook hi there17:16
*** cdub has quit IRC17:16
*** Gamekiller77 has joined #openstack-meeting17:16
msdubovAnd also boris-42 and me had a discussion on how to organize the contents of these docs17:16
boris-42msdubov could you share documents?17:16
msdubovThe core of these new docs will be a kind of tutorial though rally17:16
*** eharney has quit IRC17:16
msdubovboris-42 just a moment17:16
*** akuznetsov has quit IRC17:16
msdubovHere is the description of different user groups and of what they expect to find in our docs https://docs.google.com/a/mirantis.com/document/d/18wmAZA5_qC1PuQsHOTDVBnVS9VSi0hAdjIJ9EI5-z58/edit17:17
*** bnemec has quit IRC17:17
msdubovBelow, you can find a high-level structure of the docs.17:18
*** baoli has quit IRC17:18
*** changbl has quit IRC17:18
msdubovSo, the "Install & Use" section will guide the user through Rally with a series of lessons on how to use it17:18
*** bnemec has joined #openstack-meeting17:18
msdubovThey will get more complicated as the user reads further17:18
msdubovAnd also these tutorials hopefully will be the basics for the upcoming videos17:19
*** ignacio-scopetta has joined #openstack-meeting17:19
msdubovSo I expect to have the first version to share and to discuss till the end of this week17:19
msdubovAnother point is that we'll remove all the stuff from our WIki17:19
*** julienvey has joined #openstack-meeting17:19
msdubovSo ReadTheDocs will be the only centralized place to find all relevant infos17:20
*** padkrish has joined #openstack-meeting17:20
*** sballe has quit IRC17:20
*** tkay has joined #openstack-meeting17:21
*** emagana has quit IRC17:21
*** emagana has joined #openstack-meeting17:22
boris-42msdubov great17:22
boris-42msdubov thanks for update17:22
*** emagana has quit IRC17:22
boris-42Does anybody want to help msdubov  to provide better docs?17:22
boris-42RainbowBastion ?^17:22
*** emagana has joined #openstack-meeting17:23
RainbowBastionboris-42 Yeah, I'll work on it after I finish my prior refactoring17:23
*** sballe has joined #openstack-meeting17:24
*** marcoemorais has quit IRC17:24
*** marcoemorais has joined #openstack-meeting17:24
msdubovRainbowBastion, be sure to contact me at any time17:25
*** hrybacki_ has quit IRC17:25
boris-42msdubov RainbowBastion  so actually you can collaborate on that google docs17:26
*** mtanino has quit IRC17:26
RainbowBastionmsdubov I'll let you know when I finish up the refactoring.17:26
*** Riddhi has quit IRC17:26
boris-42great17:26
boris-42okay let's move on next topic17:26
RainbowBastionCould I get a link to the Google docs?17:26
msdubovRainbowBastion, https://docs.google.com/a/mirantis.com/document/d/18wmAZA5_qC1PuQsHOTDVBnVS9VSi0hAdjIJ9EI5-z58/edit17:26
RainbowBastionmsdubov Thanks!17:27
boris-42okay next topic17:28
boris-42#topic Week of CLI improvments17:28
*** openstack changes topic to "Week of CLI improvments (Meeting topic: Rally)"17:28
*** slagle_ is now known as slagle17:28
*** mitarun has quit IRC17:28
boris-42The idea is that CLI should and can be better much better17:28
boris-42*) Auto completion17:28
*** mitarun has joined #openstack-meeting17:28
boris-42*) rally info / rally deployment / rally task / rally validation17:29
boris-42should show by default Information about this command17:29
*** MaxV has quit IRC17:29
*** colinmcnamara has quit IRC17:29
*** baoli has joined #openstack-meeting17:30
boris-42*) Any command with wrong or missing arguments should show more user friendly message17:30
boris-42*) Some unification between commands are required17:30
boris-42*) Writing missing tests17:30
rediskinboris-42: do you mean cli functional tests?17:30
boris-42rediskin I was talking about unit tests at that point17:31
boris-42*) Writing functional tests for CLI17:31
boris-42so and other stuff17:31
*** eharney has joined #openstack-meeting17:31
boris-42RainbowBastion rediskin rook andreykurilin_ ^17:31
*** mitarun has quit IRC17:31
boris-42olkonami ^17:32
*** mitarun has joined #openstack-meeting17:32
*** sballe_ has joined #openstack-meeting17:32
boris-42Gamekiller77 ping*17:32
* boris-42 Gamekiller77 we are here17:32
*** sballe_ has quit IRC17:32
*** dane_leblanc has quit IRC17:32
boris-42so any thoughts?17:33
Gamekiller77yes just got back from PTO so doing work stuff17:33
rookwhile i haven't had many problems with the CLI with Rally - the one thing that bugs me is rally task results vs rally task detailed ... I feel like those are backwards, Results should be the pretty output, where detailed should be the JSON17:33
*** dbite_ has quit IRC17:33
rookjust a nit pick17:33
*** dbite_ has joined #openstack-meeting17:34
boris-42rook no any nit pick will be important next week17:34
*** natarajk has quit IRC17:34
boris-42rook so I know Rally CLI is consumable (but It's far from that I can say nice CLI)17:34
boris-42like "git" has17:34
*** thangp has joined #openstack-meeting17:36
*** e0ne has joined #openstack-meeting17:37
boris-42Okay any questions?17:37
boris-42any thoughts?17:37
andreykurilin_boris-42, maybe we should create some document in google docs with all nits related to cli?17:38
boris-42andreykurilin_ going to that17:38
boris-42andreykurilin_ rook Gamekiller77  https://docs.google.com/a/mirantis.com/document/d/1iZa9V8C3Z09JTC3x2MGpBq-FEszwRmVCYoxCbN1zHgo/edit17:39
boris-42RainbowBastion rediskin ^17:39
andreykurilin_good)17:40
rediskintrello?17:40
boris-42rediskin what about trello?17:40
boris-42rediskin we need to make document first17:40
rediskinok17:40
boris-42rediskin like brainstorm17:40
boris-42rediskin probably first day of next week17:40
andreykurilin_rediskin, it seems to me, we should use documents for discussion and than move tasks to trello17:41
rediskinimo trello+irc much better17:41
*** SridharG has joined #openstack-meeting17:41
rediskinor whatever+irc17:42
*** dencaval has joined #openstack-meeting17:42
boris-42andreykurilin_ +117:42
*** wuhg has quit IRC17:42
boris-42rediskin first document and then trello17:43
*** markwash__ has joined #openstack-meeting17:43
boris-42rediskin as a result17:43
boris-42rediskin of brainstorm17:43
*** _nadya_ has joined #openstack-meeting17:43
*** natarajk has joined #openstack-meeting17:44
*** dane_leblanc has joined #openstack-meeting17:44
boris-42#topic Generic cleanup17:44
*** openstack changes topic to "Generic cleanup (Meeting topic: Rally)"17:44
boris-42rediskin could you share some information about your work?17:44
*** otherwiseguy has joined #openstack-meeting17:45
rediskinI still waiting on review and finishing tests https://review.openstack.org/#/c/116269/17:45
andreykurilin_rediskin boris-42, i will have more free time for review after thursday17:46
rediskinboris-42: ^17:46
boris-42rediskin soo17:47
boris-42rediskin imho you should provide commit message17:47
boris-42rediskin that describes what you've done17:47
rediskinboris-42: ok17:47
*** penick has joined #openstack-meeting17:48
*** e0ne has quit IRC17:48
boris-42rediskin I'll try to understand your pach=)17:48
boris-42#topic Plugins17:48
*** openstack changes topic to "Plugins (Meeting topic: Rally)"17:48
boris-42olkonami what are you working on?17:49
*** mikal_ is now known as mikal17:50
*** amcrn has quit IRC17:51
boris-42olkonami around?17:51
*** arborism has joined #openstack-meeting17:52
*** devlaps has quit IRC17:52
*** arborism is now known as amcrn17:52
*** e0ne has joined #openstack-meeting17:52
*** akuznetsov has joined #openstack-meeting17:52
*** jang2 has joined #openstack-meeting17:53
olkonamihi, yes17:54
*** julienvey has quit IRC17:55
olkonamiI am fixing last comments now17:55
andreykurilin_olkonami, link17:56
andreykurilin_please)17:56
*** mchalla has joined #openstack-meeting17:56
olkonamihttps://review.openstack.org/#/c/103145/17:56
boris-42olkonami so now plugins are for everything?17:56
boris-42olkonami not only scenarios ?17:56
*** colinmcnamara has joined #openstack-meeting17:56
*** beagles_brb is now known as beagles17:57
olkonamiyes17:57
boris-42olkonami okay I'll review that patch17:57
*** emagana has quit IRC17:57
boris-42okay it's quite close to the end of this meeting17:57
*** grantbow has joined #openstack-meeting17:58
boris-42so let's continue in rally chat if somebody has something to ask17:58
boris-42#endmeeting17:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:58
openstackMeeting ended Tue Sep  2 17:58:06 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-09-02-16.59.html17:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-09-02-16.59.txt17:58
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-09-02-16.59.log.html17:58
*** mattgriffin has quit IRC17:58
*** alkari has joined #openstack-meeting17:58
*** hrybacki has joined #openstack-meeting17:58
*** olkonami has left #openstack-meeting17:58
*** RainbowBastion has left #openstack-meeting17:59
*** baoli has quit IRC17:59
*** raildo1 has joined #openstack-meeting17:59
*** hrybacki has quit IRC17:59
*** miqui has quit IRC18:00
*** bobt has joined #openstack-meeting18:00
dolphmayoung, bknudson, dstanek, jamielennox, morganfainberg, stevemar, gyee, henrynash, topol, marekd, lbragstad, joesavak, shardy, fabiog, fmarco76, nkinder, lloydm, shrekuma, ksavich, hrybacki, rharwood, grantbow, vdreamarkitex, raildo, rodrigods: https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:00
*** coolsvap has quit IRC18:00
grantbowo/18:00
raildo1\o18:00
morganfainberg\o\18:00
ayoungI'm here.18:00
stevemaro/18:00
dstaneko/18:00
*** SridharG has left #openstack-meeting18:00
dolphmayoung: yay! welcome back18:00
topolo/18:00
lbragstadhi18:00
bknudsonhi18:00
gyee\o18:00
*** mchalla has quit IRC18:01
*** rediskin has left #openstack-meeting18:01
rharwood\o18:01
*** bdpayne has quit IRC18:01
*** rodrigods has quit IRC18:01
*** ominakov has quit IRC18:01
*** doude has quit IRC18:01
dolphm#startmeeting keystone18:01
openstackMeeting started Tue Sep  2 18:01:49 2014 UTC and is due to finish in 60 minutes.  The chair is dolphm. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
*** bdpayne has joined #openstack-meeting18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: keystone)"18:01
openstackThe meeting name has been set to 'keystone'18:01
dolphm#topic Feature freeze September 4th18:01
*** openstack changes topic to "Feature freeze September 4th (Meeting topic: keystone)"18:01
morganfainbergoh we got oslofmt again i think for devstack + apache now.18:01
*** kebray has quit IRC18:01
*** rodrigods has joined #openstack-meeting18:02
*** rodrigods has joined #openstack-meeting18:02
dolphmso we're at the final countdown to feature freeze on thursday, and we're facing a 9 hour gate which is rapily growing18:02
*** markstur has joined #openstack-meeting18:02
dolphmby my count, we have about 8 patches targeting juno-3 left to land, plus endpoint grouping18:03
dolphm#link https://gist.github.com/dolph/651c6a1748f69637abd018:03
topolI assume we only are gonna worry on the hottest potatoes at this point18:03
*** kebray has joined #openstack-meeting18:03
topolerr worry about18:03
*** gothicmindfood has quit IRC18:03
dolphmon endpoint grouping, we approved the spec, and then it totally slipped off my radar until steve noticed the implementation floating around in gerrit last week18:03
dolphmso, i apologize for that :(18:03
dstanekdolphm: did you star that one?18:04
stevemardolphm, star it!18:04
dolphmdstanek: i have not18:04
dstanektopol: most of the reviews are really close18:04
*** gothicmindfood has joined #openstack-meeting18:04
*** rm_work|away is now known as rm_work18:04
stevemardolphm, it's been through a lot of reviews18:04
topoldstanek+++18:04
dolphmbobt: morganfainberg: ^18:04
*** e0ne has quit IRC18:04
morganfainbergbobt, take it.18:05
*** emagana has joined #openstack-meeting18:05
bobtHopefully, it's good to go. Needs some further love from core.18:05
morganfainberg:)18:05
*** ominakov has joined #openstack-meeting18:05
*** markstur_ has quit IRC18:05
dolphmstevemar: how close is it to being +A'd now, by your estimation?18:05
gyeeit was loved and unloved, but I think its all love now :)18:05
stevemardolphm, fairly close, i haven't looked at the last few patch sets18:05
stevemarbeen busy with other things :)18:06
dolphmstevemar: we all have!18:06
*** Gamekiller77 has left #openstack-meeting18:06
dstanekbobt: thx for adding the patch to listen to delete notifications18:06
stevemarstress levels are high all around yay18:06
dolphmlbragstad: you just got a pep8 fail on https://review.openstack.org/#/c/104066/18:06
*** mspreitz_ has joined #openstack-meeting18:07
dstaneklbragstad: ugg...sorry. i ran the tests after you pushed, but not pep818:08
lbragstaddolphm: respinning18:08
*** changbl has joined #openstack-meeting18:08
lbragstaddstanek: no worries18:08
*** marcoemorais has quit IRC18:08
*** mspreitz has quit IRC18:08
*** marcoemorais has joined #openstack-meeting18:08
dolphmit looks like stevemar, dstanek and gyee have been fairly active on the endpoint grouping impl, so thanks! https://review.openstack.org/#/c/111949/18:09
*** jamielennox|away has joined #openstack-meeting18:09
*** yamamoto has joined #openstack-meeting18:09
gyeedolphm, keep an eagle eye on it :)18:09
*** jamielennox|away is now known as jamielennox_18:09
*** Haneef has joined #openstack-meeting18:09
dolphmif ya'll approve it today, i'll try to make sure it lands for j318:10
*** jtomasek has quit IRC18:10
stevemaroh, just got an email from henry nash, he's traveling and will miss the meeting18:10
dolphmgate woes and whatnot18:10
dolphmstevemar: ack18:10
dolphmjamielennox_: o/18:10
dolphmjamielennox_: good morning!18:10
dstanekdolphm: i think that one looks good - just have to +2 it18:10
*** pelix has quit IRC18:11
* jamielennox_ yawns18:11
dolphmjamielennox_:  we need your follow up on https://review.openstack.org/#/c/113998/ which is sort of blocking the implementation i just approved on https://review.openstack.org/#/c/114138/18:11
dstanekdolphm: there is also a follow up patch to it for adding delete notifications18:11
dolphmdstanek: good to hear!18:11
dolphmdstanek: part of the bp?18:12
dstanekdolphm: it's not in the commit message, but it should be https://review.openstack.org/#/c/117723/18:12
*** e0ne has joined #openstack-meeting18:12
*** harlowja has quit IRC18:12
*** coolsvap has joined #openstack-meeting18:12
*** harlowja has joined #openstack-meeting18:13
raildo1about hierarchical  multitenancy , we are keeping our patches on this branch18:13
raildo1#https://review.openstack.org/#/q/status:open+project:openstack/keystone+branch:feature/hierarchical-multitenancy+topic:bp/hierarchical-multitenancy,n,z18:13
*** mspreitz_ has quit IRC18:13
raildo1#link https://review.openstack.org/#/q/status:open+project:openstack/keystone+branch:feature/hierarchical-multitenancy+topic:bp/hierarchical-multitenancy,n,z18:13
dolphmraildo1: perfect, thank you!18:13
*** rm_work is now known as rm_work|away18:14
*** yamamoto has quit IRC18:14
stevemarbknudson, i have a new patch for marek's stuff coming up, mind taking a look?18:14
raildo1dolphm: but we have a question,what is the  better way to keep it updated with the master?18:14
bknudsonstevemar: just send a link18:14
raildo1dolphm: We want to commit our code, but it shows that will commit all the other changes together. (as you can see here: http://paste.openstack.org/show/104791/)18:15
dstanekraildo1: are you checking out your branch and committing to that?18:15
jamielennox_dolphm: removed  -118:16
dolphmraildo1: there's a wiki page that carefully documents the process to keep feature branches up to date18:16
*** jdurgin1 has joined #openstack-meeting18:16
dolphmraildo1: doing it wrong causes infra terrible pain, so let's walk through that after the meeting18:16
jamielennox_dolphm: i disagree but a day before feature freeze is not the time for me to suddenly notice something like this and hold things up18:16
raildo1dolphm: ok18:16
raildo1dstanek: yes18:17
ayoungjamielennox_, of course not.  That's my job.18:17
dolphmjamielennox_: your point is certainly valid :(18:17
ayoungNot really18:17
*** e0ne has quit IRC18:17
jamielennox_do we expect the bulk of k2k to be ready and released for Juno?18:18
jamielennox_if it's going to slip it's something i would like to change18:18
jamielennox_that and the regions are suddenly a scoping concept18:19
*** mchalla has joined #openstack-meeting18:19
bknudsonwhen I looked at it I wondered about the scope to a region.18:20
jamielennox_bknudson: so i added this to the meeting agenda as again i only discovered it last night18:20
jamielennox_adding a URL to a region and expecting that to double as a SP is a bad idea IMO18:20
dolphmjamielennox_: the last few changes for k2k are much simpler than the first patch. i think we have a solid chance of seeing them all gating today18:20
jamielennox_(these are all things that are apparently discussed at the midcycle :( )18:21
dolphmbut:18:21
dolphm#topic Overloading regions with federated auth urls is a bad idea18:21
*** openstack changes topic to "Overloading regions with federated auth urls is a bad idea (Meeting topic: keystone)"18:21
stevemarjamielennox_, i think you preferred adding os-federation/sp/{sp} rather than overloading regions18:21
*** itzikb has joined #openstack-meeting18:21
*** jtomasek has joined #openstack-meeting18:21
jamielennox_i'm concerned what having the URL on region and then having it available as a scope in the federated case - what does this imply for the non-federated18:21
dolphmfor a touch of background, hierarchical regions were initially proposed by jaypipes to include an auth_url -- essentially the endpoint of a remote keystone for that region18:22
jamielennox_why should those two things be differnt18:22
*** _nadya_ has quit IRC18:22
dolphmwe dropped the attribute before merging since it was a little ahead of the curve18:22
jamielennox_is that still the intention?18:22
*** spzala has quit IRC18:22
*** _nadya_ has joined #openstack-meeting18:22
*** matrohon has joined #openstack-meeting18:23
jamielennox_because that is a fairly major change to what we consider a region to be today18:23
dolphmjamielennox_: well, the problem with regions has always been that everyone has a slightly different interpretation of the concept :-/18:23
ayoungare regions fundamental here, or are they a "we can do that too" concept?18:24
*** mattgriffin has joined #openstack-meeting18:24
* ayoung hasn't refreshed on the patch yet18:24
*** itzikb has quit IRC18:24
jamielennox_dolphm: i don't disagree, i've always considered that a failing of ours - but do you think that us suddenly trying to define them like this will improve that situation?18:24
dolphmstevemar: the patch already merged to both the API and for the implementation for region URLs, right?18:25
jamielennox_as i see it now a region is just a filter, you get a service catalog and you pick one of many18:25
stevemardolphm, yes18:25
dolphmjamielennox_: i'm going to turn the question around, and ask how it's might make it worse?18:25
dolphms/it's/it/18:25
*** mtanino has joined #openstack-meeting18:25
ayounghttps://review.openstack.org/#/q/status:merged+project:openstack/keystone,n,z18:25
dolphmso, regions now have an optional "url" attribute in core identity api https://github.com/openstack/identity-api/blob/master/v3/src/markdown/identity-api-v3.md#regions-v3regions18:26
dolphmas part of v3.318:26
*** johnthetubaguy is now known as zz_johnthetubagu18:26
jamielennox_if i have arbitrary labels on my existing endpoints, i get a k2k token - why should i suddenly have my endpoints restrictd18:26
jamielennox_s/labels/regions - but they are the same thing18:26
*** jjmb1 has joined #openstack-meeting18:26
*** esker has quit IRC18:26
jamielennox_in this case why should me having a federated token change the experience to me having a regular token18:27
*** Riddhi has joined #openstack-meeting18:27
ayoungjamielennox_, yeah...SAML should only be considered a marshalling format18:27
*** julim has joined #openstack-meeting18:27
*** novas0x2a|laptop has quit IRC18:28
*** Ajaeger1 has joined #openstack-meeting18:28
jamielennox_and even with hierarchical i'm not really sure what having the auth_url on a region would be used for18:28
dolphmjamielennox_: regions are really just an organizational tool to facilitate discovery in a complex environment, right?18:28
*** jjmb2 has joined #openstack-meeting18:28
topoldolphm +++18:29
jamielennox_i'm concerned that we bled extension concepts over into the core API because we didn't want to add a couple of hundred lines of controllers for a new resource type18:29
jamielennox_dolphm: sure18:29
*** jjmb has quit IRC18:29
dolphmjamielennox_: if it was region["OS-FEDERATION:url"], would that be more sane in your eyes?18:30
jamielennox_dolphm: it would at least remove it from the regular pool - i'm just not sure why it's not it's own resource18:31
ayoungleaving SAML out of it for a moment, though, does having distinct Auth URLS in the same service catalog make any sense?  I always thought "domain" would be the reasonable fissure, not reagion, for the span of control of a KEystone server18:31
*** jjmb1 has quit IRC18:31
ayoungor, really, whatever we call the "assignment domain"18:31
ayoungRegion is not that18:31
jamielennox_ayoung: i don't think so18:32
ayoungall this Auth Url would be is "here is a closer keystone server"18:32
dolphmayoung: region URLs don't appear in the service catalog18:32
dolphmit's sort of a meta-catalog18:32
dolphmand potentially cross-cloud18:32
jamielennox_dolphm: so another question - how do i list all the auth_urls that i can get to with this token?18:32
jamielennox_is that some sort of filter on a region list operation?18:32
ayoungdolphm, region is the wrong abstraction18:32
*** ominakov has quit IRC18:33
ayoungregion is not a security namespace.  Domain is a secuiryt namespace.18:33
*** emagana has quit IRC18:33
jamielennox_yea, but domain doesnt fit here18:33
*** rushiagr is now known as rushiagr_away18:33
dstanekthe reason i thought regions needed to grow the auth_url was that the EAST region may be from cloud provider 1 an the WEST region from cloud provider 218:34
*** emagana has joined #openstack-meeting18:35
dolphmdstanek: ++ that's the use case we discussed. it's also obviously one of federation in that example, so i'm inclined to buy the argument that it should have been an OS-FEDERATION extension attribute.18:35
*** marcoemorais1 has joined #openstack-meeting18:35
jamielennox_dstanek: wouldn't access to them be controlled by seperate service catalogs/tokens?18:35
dolphmdoes the core API have a use case for region URL's without consideration for OS-FEDERATION?18:35
dstanekjamielennox_: my understanding is separate token, but same catalog18:36
ayoungwow....Um, that is really diffferent from how I understood regions18:36
stevemardolphm, doubtful18:36
*** bobt has quit IRC18:36
*** davidlenwell has quit IRC18:36
dolphmdstanek: that point has proponents on both sides18:36
*** jjmb has joined #openstack-meeting18:36
jamielennox_dstanek: why would be share a catalog between different tokens?18:36
*** jjmb2 has quit IRC18:36
*** marcoemorais has quit IRC18:36
*** MaxV has joined #openstack-meeting18:36
*** davidlenwell has joined #openstack-meeting18:36
*** thangp has quit IRC18:36
jamielennox_if you can't access the resource with the current token it should not be in the service catalog18:36
dolphmstevemar: what's the cost to hackishly move region.url to be an OS-FEDERATION attribute in the implementation?18:37
ayoungjamielennox_, ++18:37
jamielennox_also unless we start listing the auth_url for that region in the service catalog there is no way for existing services to know they need a new token before accessing it18:37
dstanekjamielennox_: in some cases the internal cloud may not want the customer to directly care that the region is from a different provider18:37
*** mitarun has quit IRC18:38
jamielennox_dstanek: but it's not so much the customer - if we need a new token how do the developers know they need to do that?18:38
dolphmjamielennox_: i'd assume (perhaps wrongly, and i know others disagree) that if a region appears with a URL, then i'm not going to have it's endpoints in my service catalog. i'd have to go auth (somehow) with that endpoint to get a new catalog18:38
*** mitarun has joined #openstack-meeting18:38
*** esker has joined #openstack-meeting18:39
dolphmpeople fuss too much over obscuring endpoints from their own users, that i can't see any deployments willing to expose & maintain a complete catalog of their own services in multiple clouds18:39
dstanekjamielennox_: someone mentioned (maybe at the hackathon) that the client could take care of negotiating for new token to be used in the other could - transparently to the user18:39
*** Mandell has quit IRC18:40
jamielennox_so i think this was discussed in the talk at atlanta and it was a question from the audience about getting a catalog full of endpoints for other cloud providers18:40
*** afazekas has joined #openstack-meeting18:40
*** padkrish has quit IRC18:40
bknudsonwhat client?18:40
*** jjmb has quit IRC18:40
jamielennox_and chadwick stood up (and we all agreed) that no, you would be able to get a listing of other providers and then if you went and got a token from them you could get the endpoints you could access with that token in that new cloud18:40
jamielennox_that stuffing every possible endpoint into the one token was not the way to do this18:41
jamielennox_s/one token/one catalog18:42
ayoungjamielennox_, ++18:42
dstanekjamielennox_: i thought that was one of the reasons to break remove the catalog from the token18:42
dstanekbknudson: the keystone client or any other thridparty clients18:42
jamielennox_dstanek: on client i don't think that's going to be backwards compatible18:43
stevemardolphm, removing url from region isn't too bad, just don't know where to add it to18:43
dstanekmy understanding may be outdated and stevemar/marek may have new ideas18:43
jamielennox_dstanek: i think we are a long way from removing the catalog from the token though18:43
topoldstanek +++ I thought it was a reason to break the catalog from the token as well18:43
*** mitarun has quit IRC18:43
*** padkrish has joined #openstack-meeting18:43
jamielennox_stevemar: i think OS-FEDERATION/sp is as good as any18:44
dolphmstevemar: for juno, i don't want to break a bunch of stuff. if renaming region.url to region.OS-FEDERATION:url is something we need to consider for juno though, i want to take the shortest, least risky path to make that happen18:44
dstanekjamielennox_: why not? get a 403 saying federation is possible and do the magic - old clients don't do the magic and old servers won't say they support the magic18:44
*** gokrokve has joined #openstack-meeting18:44
jamielennox_i even see it reasonable to list available service providers as a field in the token response so that you don't need to query that as an additional step18:44
*** adam_g` is now known as adaM_g18:44
*** padkrish has quit IRC18:44
*** adaM_g is now known as adam_g18:44
ayoungshall we vote on it?18:46
*** doude has joined #openstack-meeting18:46
dolphmayoung: we don't have a code review to vote on :)18:46
*** otherwiseguy has quit IRC18:46
*** ominakov has joined #openstack-meeting18:46
ayoungdolphm, is it the  right approach?18:46
jamielennox_dstanek: fair it will just fail, though in reality what will happen is that getting a 401/403 from a response will make the client dump its existing token reauthenticate with keystone (because the only reason it knows to get blocked from an endpoint in it's catalog is that it has been revoked or something else) and try the request again - but it will fail out after that18:47
dolphmjamielennox_: ++18:47
jamielennox_also i would be interested in what we were thinking about in terms of "breaking out the service catalog"18:48
ayoungI'm most concerned with sticking the Federation Endpoints in the Service catalog.18:48
ayoungthat is a commitment we can't break lightly18:49
jamielennox_it's been a long held theoretical belief - but not one i've seen come even close in practice18:49
jamielennox_ayoung: ++18:49
dolphmstevemar: jamielennox_: let's look at the API impact after the meeting, and see if anyone wants to volunteer to write a patch for juno18:49
jamielennox_ayoung: that's a really bad idea IMO18:49
*** flaper87|afk is now known as flaper8718:49
*** jjmb has joined #openstack-meeting18:49
jamielennox_however i'm more concerned that is it the only thing that's going to otherwise prevent us from landing all the k2k work in juno?18:50
stevemarayoung, it wouldn't be an endpoint, it's just an auth url18:50
ayoungjamielennox_, so we are agreed that K2K Federation should not use the Auth URL for a region.  I think Region specifc auth urls are suspect18:50
dolphmjamielennox_: that's just something we've put little effort into18:50
ayoungstevemar, doesn't matter what you call it, it matters that it is in the service catalog18:50
dolphmayoung: we're agreed that it's suspect, i think. that's all18:50
stevemarbut it's one url vs many18:50
dolphmbknudson: is your JSON home #topic for juno or kilo?18:51
jamielennox_stevemar: so the catalog would contain 'auth_url' rather than public/internal/admin?18:51
bknudsondolphm: well, I was hoping to discuss it for juno, if possible18:51
dolphmbknudson: alright, then let's do it18:51
dolphm#topic JSON Home for /, /v2.018:52
*** openstack changes topic to "JSON Home for /, /v2.0 (Meeting topic: keystone)"18:52
dolphmbknudson: o/18:52
jamielennox_bknudson: sorry, take it away18:52
*** changbl has quit IRC18:52
bknudsonso the discussion is, do we want to be able to have json home for /, too18:52
bknudsonI did some experimenting over the weekend and it turned out I could use webob to request the /v318:52
*** jjmb has quit IRC18:52
bknudsonand then all that needs to happen is change the URLs in the v3 JSON home and now / returns the JSON Home18:52
bknudsonthis seems useful because then a client can get JSON Home from / or /v318:53
* ayoung likes that18:53
topolbknudson, very cool!18:53
bknudsonso no need to do version discovery18:53
stevemarbknudson, seems like a no brainer18:53
ayoungI think that is the right approach....so long as /v3 in this case implies "latest"18:53
dolphmi'd really like that!18:53
jamielennox_bknudson: for existing clients i've always assumed that the response from / and from /vX is the same18:53
ayoungbut we are a long way from /v418:53
bknudsonon top of that, can do /v2.0 and have it also return the /v3 JSON Home18:53
topolbknudson, do you have a review link?18:53
jamielennox_obviously not the same, but that i don't need to query both18:54
*** novas0x2a|laptop has joined #openstack-meeting18:54
bknudson#link https://review.openstack.org/#/c/118240/18:54
bknudsonthis is a WIP since I didn't do tests18:54
*** jckasper has joined #openstack-meeting18:54
bknudsonand also the wacky Version controllers don't make this easy18:54
*** jckasper_ has quit IRC18:55
topolbknudson the /v2.0 returns JSON for v2 correct/18:55
dolphmbknudson: i don't follow the /v2.0 comment18:55
bknudsonso I'll work on this and I should be able to get it done in a couple hours.18:55
topoldolphm, me iether18:55
*** changbl has joined #openstack-meeting18:55
jamielennox_bknudson: you would return the v3 urls for Get /v2.0?18:55
bknudsonGET /v2.0 w/ Accept: application/json-home will return a JSON Home document that has relationships / links to the v3 resources18:55
*** ianw has joined #openstack-meeting18:55
bknudsonso if you've got /v2.0 in your catalog, you'd have links to the v3 resources.18:56
dolphmbknudson: that sounds slighly scary, but i know some rest api's basically do that18:56
bknudsonI'll split it out18:56
jamielennox_bknudson: i'm not sure the way i've been thinking about discovery with json home will work with that18:56
topolhow does crossing those two ghostbuseter streams not lead to toruble?18:56
jamielennox_(which is probably a problem with my thinking)18:56
dolphmbknudson: support on / is super nice to have, support on /v2.0 is way down my personal wishlist18:56
bknudsonthe relationship links are always the same18:56
bknudsonso you've got a relationship that says http://identity/v3/auth_tokens18:57
ayoung3 minutes left18:57
dolphmayoung: thanks18:57
dolphmand yikes18:57
*** rockyg has joined #openstack-meeting18:57
bknudsonwhen the client needs to get the URL to v3 auth tokens it looks for that relationship18:57
bknudsonand then follows the link for that relationship18:57
*** mattgriffin has quit IRC18:58
dolphmbknudson: in reality, are we going to have any JSON-Home aware clients interacting with v2?18:58
jamielennox_dolphm: yes18:58
jamielennox_dolphm: keystoneclient18:58
bknudsonas long as people have /v2.0 in their catalog18:58
dolphmjamielennox_: i mean, with *only* v218:58
jamielennox_dolphm: not particularly because i want it for v2 but i want the flow to be the same for v2 and v318:58
dolphmjamielennox_: but this flow won't work on, say, icehouse, so you'll never have the same flow all the time anyway18:59
dolphmjamielennox_: have to account for it not existing18:59
*** jtomasek has quit IRC18:59
dolphm(1 min)18:59
jamielennox_dolphm: but it's how you stack your accept headers, we will always need to fall back to current discovery18:59
*** sweston_ is now known as sweston18:59
dolphmjamielennox_: you wouldn't rather just always fallback to current discovery for v2, instead of introducing and supporting a new thing?19:00
*** ndipanov is now known as ndipanov_gone19:00
jamielennox_moving to channel19:00
lbragstadtime19:00
bknudsonthanks19:00
dolphm\o/19:00
dolphm#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Sep  2 19:00:45 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-09-02-18.01.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-09-02-18.01.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-09-02-18.01.log.html19:00
jeblairhowdy infra folks19:01
pleia2o/19:01
grantbowo/19:01
ianwo/19:01
fungihey-o19:01
anteayao/19:01
*** ekhugen has joined #openstack-meeting19:01
jeblair#startmeeting infra19:01
openstackMeeting started Tue Sep  2 19:01:44 2014 UTC and is due to finish in 60 minutes.  The chair is jeblair. 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
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:01
jeblair#link last meeting http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-08-26-19.01.html19:01
krtayloro/19:01
clarkbo/19:01
*** johnpur has joined #openstack-meeting19:01
jeblair#topic  Actions from last meeting19:02
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:02
jeblair anteaya invite third-party email addrs from gerrit to announce list19:02
anteayadone19:02
jeblairanteaya: did that happen?19:02
anteayayes19:02
jeblairneato19:02
swestono/19:02
jeblairi should subscribe to those lists now :)19:02
anteayaif you like19:02
*** otherwiseguy has joined #openstack-meeting19:02
anteayayou are clear to post to announce19:02
*** pballand has quit IRC19:02
fungiooh, good idea ;)19:02
anteayaas is clarkb fungi and SergeyLukjanov19:02
anteayadid I miss anyone?19:02
anteayalyz is already an admin19:03
jeblairanteaya: what's the uptake like on the announce list?19:03
anteayagood19:03
*** marekd|away is now known as marekd19:03
*** stevelle has joined #openstack-meeting19:03
krtayloranteaya, do third-party chairs count?19:03
anteaya59 I think?19:03
anteayakrtaylor: you are already subscribed19:03
pleia265 now19:03
krtaylorI thought you were saying it was post moderated19:03
pleia2much better than request, which has 1819:04
anteayapleia2: yes19:04
anteayakrtaylor: let me check19:04
jeblairkrtaylor: oh, yes it is.  i expect the use to be for broadcast messages to third-party operators, most of which would be from infra (announcing changes to the system, etc)19:04
SergeyLukjanovo/19:04
krotschecko/19:05
*** jamielennox_ has left #openstack-meeting19:05
jeblairkrtaylor: i think if you have something to announce, we can still use it for that19:05
fungi(meeting minutes?)19:05
anteayakrtaylor: let's get it underway and then look at permissions19:05
fungi(for teh third-party meetings)19:05
jeblairkrtaylor: just check with one of the moderators to make sure it's appropriate, and/or go ahead and send the message and they can let it through19:05
anteayafungi: possibly19:05
krtaylorsounds good19:05
jeblairfungi: i think low-traffic would be good19:06
krtayloragreed19:06
fungiyeah19:06
anteayajeblair: the last item on today's agenda will probably the first post to -announce19:06
jeblairfungi: i want something that no one has any excuse to ignore :)19:06
anteayajeblair: right19:06
jeblairanteaya: yeah, i think we may be thinking along the same lines :)19:06
anteayagood19:06
anteayabest chance of success19:06
fungiwell, a weekly link to the third-party irc meeting minutes seems relatively low-volume, and makes for a good ping19:06
*** hashar has joined #openstack-meeting19:06
anteayafungi: I'll consider the thought19:07
anteayalet's get the other things in shape first19:07
jeblairfungi: hrm.  that's the sort of thing that causes me to create a mail filter so that they go into a folder that i never read19:07
fungijeblair: ahh, yep. fair enough19:07
krtaylorwell, we also post highlights to the weekly newsletter19:07
anteayakrtaylor: that is a better place19:07
*** Haneef has quit IRC19:08
krtaylorI'd vote keep it low volume19:08
*** whenry has joined #openstack-meeting19:08
*** marun_ has joined #openstack-meeting19:08
jeblaircool19:08
jeblair pleia2 send the email to -infra announcing the new lists/policies after 116989 merges19:08
jeblairi think i saw this :)19:08
anteayait happened, yes19:08
zaroo/19:08
jeblairas a followup, are we ready to ask people to take some topics to the request list?19:09
nibalizero/ im hello hello19:09
*** yamamoto has joined #openstack-meeting19:09
jeblairi think we're finishing up some account re-enabling mails that originally went to the infra list19:09
anteayaI haven't seen any new requests to redirect yet19:09
jeblairand i think it's fine to not be too particular about those19:09
pleia2yeah, I've been hoping the current ones just finish up on -infra19:09
anteayayes, and I don't know as any of the account requests outstanding from last week were fulfilled19:10
jeblairbut probably if we get too many more, we should start asking people to use the new list19:10
pleia2+119:10
anteayayup19:10
anteayaI asked SergeyLukjanov in channel but didnt' get an answer19:10
anteayaif someone can help me with cleanup after the meeting19:10
jeblairokay, we may have another week of overlap then19:10
SergeyLukjanovI've not read the channel logs yet19:10
SergeyLukjanovsorry19:10
*** Mandell has joined #openstack-meeting19:10
SergeyLukjanovanteaya, I'll read it now and answer19:11
anteayaSergeyLukjanov: the outstanding account creation requests from last week19:11
clarkbI can take a stab at helping with creating accounts if SergeyLukjanov wants help19:11
anteayaSergeyLukjanov: thanks19:11
*** julienvey has joined #openstack-meeting19:11
anteayaclarkb: thanks19:11
SergeyLukjanovanteaya, oh, sure, I'll cover accounts creation tomorrow19:11
jeblaircool, once that's done we can probably at least redirect new account requests19:11
*** markmc has joined #openstack-meeting19:11
clarkbSergeyLukjanov: let me know if there is a group you want me to do19:11
anteayayes19:11
clarkbhappy to help19:11
*** jecarey has quit IRC19:12
jeblair#topic Priority Specs (jeblair)19:12
*** openstack changes topic to "Priority Specs (jeblair) (Meeting topic: infra)"19:12
SergeyLukjanovclarkb, thx19:12
jeblair#link https://review.openstack.org/#/c/100363/19:12
jeblairthis had 2x+2s and got an update19:12
jeblairi think it was a minor update, so we can probably get those back pretty quickly19:12
anteayayes, minor update19:13
*** AlkaD has joined #openstack-meeting19:13
jeblairso consider this a last call.  i'll aprv it tomorrow morning assuming it has at least 2x+2s.19:13
anteayaI asked for some expantions so the third party folks could see themselves in the mirror19:13
anteayayesterday I learned they don't understand how the current infra work will benefit them19:13
jeblairanteaya: oh, thank you for that.19:13
anteayathey think it is for infra19:14
jeblairthis is, i think very important.  :)19:14
*** yamamoto has quit IRC19:14
anteayaextremely19:14
krtaylorwell, partially because the commit message wasnt exactly clear to that point19:14
anteayaso at least a few people understand now, hopefully the share19:14
pleia2maybe see about getting hashar's input too19:14
*** dteselkin has quit IRC19:14
anteayakrtaylor: all that was missing was third-party in the commit message19:14
pleia2he's been using our infra probably the longest19:14
*** emagana has quit IRC19:14
*** _nadya_ has quit IRC19:14
anteayaapparently if they dont' see third-party they don't see the benefit to them19:15
*** padkrish has joined #openstack-meeting19:15
krtayloranteaya, I always like commit messages that say why and to what benefit19:15
jeblairyeah, this and the next one are all about modularizing how we run things to make the tools easier for other people to use19:15
*** emagana has joined #openstack-meeting19:15
anteayadownstream consumers apparently doesn't ahve the same ring to it19:15
*** Mandell has quit IRC19:15
*** jtomasek has joined #openstack-meeting19:15
jeblairfor instance, we don't all need our own puppet modules for zuul19:15
jeblairbut we do need our own zuul layout19:16
*** julienvey has quit IRC19:16
jeblairor, more to the point for this one, we may want to share the list of packages we're installing on build workers without also configuring my ssh key for login :)19:17
jeblairmoving on to https://review.openstack.org/#/c/99990/19:17
*** esheffield has joined #openstack-meeting19:17
clarkbjeblair: you don't like getting root on mystery boxes?19:17
nibalizeryea19:18
anteayaha ha ha19:18
*** dteselkin has joined #openstack-meeting19:18
nibalizeri got focused on the tech side and not the big picture19:18
clarkb99990 has a lot of positive feedback19:18
*** emagana has quit IRC19:18
clarkbI am ready to go on that one19:18
jeblairdoes anyone have a reason i shouldn't +3 this one now?19:18
anteaya+319:18
*** emagana has joined #openstack-meeting19:18
hasharpleia2: I am on parental leave for 2 weeks but feel free to drop an email, I might be able to process it :]19:18
fungigo for it19:18
nibalizerjeblair: doet19:18
anteayahashar: congratulations19:19
jesusaurusyay \o/19:19
pleia2hashar: congrats :)19:19
anteayahashar: hopefully the leave is new baby and not sick child19:19
grantbowcongratulations19:19
jeblairhashar: yes, congratulations! :)19:19
hashar(meeting has been hijacked by a 2 days old baby) :D19:19
krtaylorhehheh, congrats!19:19
fungioh! a new proto-hashar. awesome19:19
*** kojack has joined #openstack-meeting19:19
anteayathat is their job19:19
anteayahijack all the things19:20
jeblairhashar: and that's just the beginning :)19:20
*** rook has quit IRC19:20
Ajaeger1hashar: it will get worse ;) Congratulations!19:20
pleia2haha19:20
jeblairhttps://review.openstack.org/#/c/110730/19:21
nibalizerjeblair: i think we need an #agreed for harshar's baby19:21
*** padkrish_ has joined #openstack-meeting19:21
*** dane_leblanc has quit IRC19:22
hasharwife + baby are all fine.  Meanwhile if there is any change that can use a review please shout :]19:22
jeblair#info Congratulations to hashar on his new baby!19:22
*** annegent_ has quit IRC19:22
anteayahashar: best kind of news19:22
hasharhehe19:22
*** markwash__ has quit IRC19:22
pleia2hashar: dropped you an email, take your time :)19:22
jeblairso on https://review.openstack.org/#/c/110730/ i pushed a new patchset this morning that adds some files and drops any reference about puppet templates19:23
hasharand thank you for your kind words everyone!19:23
anteayaif the group thinks I could do it 110730 will be a great learning experience for me19:23
jeblairjesusaurus pointed out that using puppet templates outside of a module context can be complicated19:23
*** kojack1 has quit IRC19:23
clarkbjeblair: I will rereview19:23
anteayabut if the volume of dumb questions to work accomplished is too much, I understand if someone else wants to do it19:23
*** padkrish has quit IRC19:24
jeblairand none of the files currently under consideration for that repo use templates, so i think it's best to just define it out of scope for now, unless we need to figure something else out later19:24
*** che-arne has joined #openstack-meeting19:24
jeblairhonestly, most of the files i think are good candidates for the project-config repo are generally not templates anyway, so it should be okay19:24
fungii think those become todo items for figuring out how to template and configure separately or something19:24
jeblair(scripts, zuul layout, jjb, etc)19:24
pleia2anteaya: if you want to learn more about puppet, it's a nice opportunity, at least on the review side19:24
*** ametts has joined #openstack-meeting19:25
pleia2I think we'll really need folks reviewing the changes in a test env19:25
anteayapleia2: well I was thinking more about my comfort with jjb and layout.yaml and so on19:25
jeblairwe might want to put the nodepool config itself in there, which is currently a puppet template.  but i think we can change nodepool to put the secrets in another file19:25
*** AlkaD has quit IRC19:25
pleia2ah, ok :)19:25
anteayapleia2: oh well I'm not good at setting up puppet in a test env, so perhaps I should withdraw my offer19:25
pleia2I've been working with jedimike to make it easier19:26
fungijeblair: yeah, those sorts of refactoring, which probably are a one-by-one bug list19:26
anteayapleia2: I believe you have, but whether it actually makes it easier, I will hold me evaluation for a while19:26
jeblairbut we'll get a huge immediate gain just with the files already in the list19:26
fungimight make for a good set of low-hanging fruit bugs19:26
pleia2anteaya: maybe you can be our guinea pig :)19:26
jeblairanteaya: also, becoming comfortable with that process would not be time wasted :)19:26
anteayapleia2: I'm willing to try19:27
pleia2\o/19:27
clarkbjeblair: agreed the initial list is quite good19:27
fungii'm running some stats over the entire config repo to see the change frequebcy on individual files, whichi should identify any we might be missing19:27
anteayajeblair: I was hoping for something that would give my confidence a shot in the arm19:27
jeblairfungi: excellent idea!19:27
*** noslzzp has quit IRC19:27
*** markwash__ has joined #openstack-meeting19:27
anteayajeblair: yes, I hear that I need to improve my puppety skills19:27
fungii'll update the list in the spec with any others i find, and a potential todo list for things which are more embedded data lists in puppet manifests or templates which could stand to get split19:28
nibalizersome of which, i would argue, goes in hiera19:28
fungithough the todo list is probably best left to follow-on specs19:28
fungior just bugs/stories19:28
jeblairnibalizer: quite possibly19:28
hasharat wikimedia we have a jenkins job that let one compile catalog against list of nodes and do the diff of catalogs between the patchset and parent one19:28
hasharthat sometime help :D19:28
*** erlon has joined #openstack-meeting19:29
nibalizerthats a cool idea!19:29
jeblairso that one probably has at least a few days left in review19:29
jesusaurusnibalizer: agreed, but if we cant put templates in the new project then we have to do one or the other, we cant mix hiera and these files19:29
jeblairhttps://review.openstack.org/#/c/110793/19:30
jeblairis docs publishing19:30
jeblairi think it's up to date, except we're still a little vague on what we'll do with openstack-manuals19:30
jeblairi think there was some general support for doing option 1 -- build all the manuals in the openstack-manuals repo every time19:31
clarkbright, we were going to see if Ajaeger1 could quantify it for us19:31
Ajaeger1jeblair: I think we can figure out some stuff, once we have the first steps done19:32
*** Mandell has joined #openstack-meeting19:32
Ajaeger1clarkb: what exactly to quantify?19:32
clarkbAjaeger1: the cost of building all the docs each time19:32
*** Mandell has quit IRC19:32
jeblair(in openstack-manuals)19:32
clarkbfrom a cpu time perspective19:32
Ajaeger1clarkb: that's not too expensive - compared to what a nova jobs costs right now ;)19:32
Ajaeger1clarkb: 30 mins or so19:32
*** Mandell has joined #openstack-meeting19:32
jeblairokay, cool.  yeah, i think we have enough options with openstack-manuals that we can go ahead and get started on the rest of this and leave a final decision on openstack-manuals until later.19:33
jeblair(since at least no one is saying "none of those 3 options will work")19:33
Ajaeger1note that we build in parallel...19:33
*** dbite_ has quit IRC19:33
fungimy feel is that premature optimization is best avoided for now19:34
fungisimplicity first19:34
*** dbite_ has joined #openstack-meeting19:34
* Ajaeger1 can easily change the scripts for the simple way and we can optimize from there...19:34
*** whenry has quit IRC19:34
*** Mandell has quit IRC19:35
fungiyeah, optimizing where we see clear performance impact later makes sense19:35
jeblaircool.  so i'll check in on this one again tomorrow, hopefully we can aprv before next meeting19:35
fungi(especially of "optimizing" means "afs")19:35
fungier, if19:35
jeblairfungi: indeed :)19:35
jeblair#topic  Manila project renaming (fungi, bswartz)19:35
*** openstack changes topic to "Manila project renaming (fungi, bswartz) (Meeting topic: infra)"19:36
Ajaeger1I'd like to have an +1 from annegentle on the docs repo and will ping her19:36
jeblairAjaeger1: okay, we can wait for that19:36
fungithis was a placeholder. bswartz doesn't seem to hang out in irc much. i reached out to vponomaryov earlier today but haven't heard anything19:36
jeblair:(19:36
fungimainly just wanting to be aware that their program application was approved last week, and they have a couple of projects currently in the stackforge namespace19:37
jeblairisn't "have some folks on irc" one of the things the tc asks for in a project?19:37
*** dprince has quit IRC19:37
*** marcoemorais1 has quit IRC19:37
fungiwell, i also could have thought to pester people in #openstack-manila. i'll give that a shot after the meeting19:37
*** whenry has joined #openstack-meeting19:37
jeblairfungi: okay, let me know how that goes19:37
*** AlkaD has joined #openstack-meeting19:38
fungianyway, no need to belabor this topic19:38
jeblairotherwise, we'll just rename their project and tell them that we totally mentioned it on irc. ;)19:38
fungiha19:38
*** marcoemorais has joined #openstack-meeting19:38
jeblair#topic  Fedora/Centos testing updates (ianw 02-09-2014)19:38
*** openstack changes topic to "Fedora/Centos testing updates (ianw 02-09-2014) (Meeting topic: infra)"19:38
Ajaeger1vponomarov is in Russia AFAIK - should be late for her...19:38
*** marcoemorais has quit IRC19:38
ianwhi19:38
ianwa few updates on this19:38
ianw1) the nodepool allocation issues -- i think everyone is happy we got to the bottom of this?19:39
*** marcoemorais has joined #openstack-meeting19:39
jeblairyep, thanks!19:39
ianwthere was some talk of alternative allocators, other than "round-robin-at-full-capacity", which is pretty much always19:39
jeblairyour original analysis was correct (and we came up with a way to reproduce the problem that verifies this)19:39
fungii'm getting back around to rereviewing the nodepool update stack for those now19:40
ianwis that going to be a blocker, or are people happy with the current behavior?19:40
fungithe sooner we get that implemented the better, i thinkl19:40
ianwi think it's better than waiting a very long time for f20 nodes19:40
fungi(and py33 nodes, and precise nodes, and...)19:40
jeblairianw: i don't think it needs to block; at least, i think we agreed that this approach sounds better than what we have now, and i'm not a fan of changing the goal posts like that19:40
*** miqui has joined #openstack-meeting19:40
ianwi was thinking that some sort of parallel execution environment might be good longer term for testing changes19:41
clarkbyup I think we explored future improvements but they don't need to be done before current improvements go in19:41
jeblairianw: so i'm happy to try this out, and barring unforseen highly negative effects, stick with it for a bit19:41
ianwthat is something i will think about19:41
jeblairianw: problem is that we don't have the resources to test at scale19:41
jeblairianw: (i mean, if we had 2x nodes, we'd use them all for real :)19:41
*** mattgriffin has joined #openstack-meeting19:42
jeblairianw: and small-scale testing is something that most of us should be able to do on our own19:42
jeblairianw: along with large-scale fake testing19:42
*** Mandell has joined #openstack-meeting19:42
jeblairso when i'm making a nodepool change and i want to know how it's going to look with 1000 servers, i run it locally with a fake config and tell it to spin up 1000 fake servers19:43
ianwjeblair: yeah, i hadn't thought it through too much.  but it's quite scary to deploy any changes in this area, as it seems like anything other than perfection brings down all forward progress for openstack19:43
*** rushiagr_away is now known as rushiagr19:43
*** oanufriev has quit IRC19:43
jeblairand when i want to make sure it actually works against a real cloud, i use a real account and have it spin up 1 or 2 real servers19:43
jeblair(also, having that config handy is really nice when i want to test a devstack-gate change -- i mean there's a daemon running that keeps making new devstack servers for me :)19:44
ianwok, i think we can all agree that more testing won't hurt in general :)19:45
jeblairianw: but i agree that it's a problem.  i think the best thing we can do is continue to enhance the in-tree testing19:45
jeblairsince the manual test process is slow and involved; automating that would be great19:45
ianwi also have a couple of minor nodepool changes out, in the agenda19:45
jeblairoh before we move on to those19:45
ianwi know that minor reviews are not high on priority list19:45
jeblairwe should get your first two changes merged soon...19:46
ianwbut it would be nice if things got cleared19:46
jeblairfungi: mentioned he wantod to review them soon19:46
jeblairassuming they merge in a small number of days from now19:46
jeblairwhen should we restart nodepool to pick them up?19:46
fungiyep, i have them up in a tab--just trying to get through the rest of the cloner/puppet integration series first19:46
*** dbite_ has quit IRC19:46
clarkbyup on my list too19:47
ianwi also have reviews out for f20-bare nodes -- is there any philosophical objection to this?19:47
*** pballand has joined #openstack-meeting19:47
clarkbjeblair: considering FF is happening maybe we can shoot for a friday restart? that will let it ramp up more slowly19:47
ianwit requires one change i found to pull in some more recent postgresql puppet modes19:47
ianwmodules19:47
fungii think as soon as there are at least a couple of us on hand to babysit and revert if needed. shouldn't do much more than delay the gate worst case19:47
clarkbjeblair: otherwise it iwll just be full speed ahead during FF19:47
jeblairclarkb: well, if we do it friday, it should be early friday; i don't want to find problems over the weekend.19:48
fungiand has the chance to significantly increase our test volume/throughput19:48
jeblairor rather, other people to find problems, since i won't be around ;)19:48
clarkbjeblair: :) agreed19:48
clarkbor maybe we can try to get it done early tomorrow?19:49
clarkbI can review the changes today19:49
jeblairassuming it works, it should not actually be disruptive19:49
clarkbjeblair: good point19:49
jeblaironly if it breaks would it be noticed19:49
clarkband it has been tested :)19:49
clarkbok I am less worried about it now19:49
fungisince we've been using the check pipeline as a barrier to entry for the gate pipeline recently-ish, starvation in check is effectively limiting the rate at which changes can get tacked onto the gate (plus it slows down iteration there in general if devs/reviewers are waiting for test results)19:49
fungii'm a fan of early tomorrow (where early is that at least one of you are up, not just me)19:50
clarkbfungi: that is early :)19:50
jeblairokay, so we'll restart nodepool early morning the day after those changes merge19:50
clarkbjeblair: sounds good19:50
jeblairf20-bare nodes19:50
*** Mandell has quit IRC19:50
fungii'm hoping to finish reviewing the series this evening19:50
*** Mandell has joined #openstack-meeting19:51
*** reed has quit IRC19:51
ianwjeblair: f20-bare nodes ^19:52
jeblairi don't have a philosophical objection to them (which was your question)19:52
*** annegent_ has joined #openstack-meeting19:52
*** padkrish_ has quit IRC19:52
jeblairi think it's probably just worth reminding folks that the fedora support cycle is shorter than the openstack support cycle19:52
jeblair(as is ubuntu non-lts)19:53
ianwjeblair: yep, anyone i interact with who is interested in f20 i'm making sure to tell them they're signing up to move to f2119:53
jeblairso we still need to focus the bulk of our testing on centos/lts, but we can opportunistically test things in master on newer distros19:53
ianwwhich brings me to centos7 ...19:53
ianwfor long term testing19:53
ianwwe have rackspace images and an experimental job19:53
ianwmy request for hp cloud people to contact me about their support didn't get a response19:54
jeblairoh i thought someone said they were handling it19:54
*** jasondotstar has quit IRC19:54
ianwbut i found the main person generating upstream centos7 images, who has contacts within hp19:54
jeblairyeah, that's what i was remembering19:54
ianwjeblair: sorry, yes, no response from HP as such19:54
*** kgriffs has joined #openstack-meeting19:55
ianwanyway, i would like to bring up centos7 there to bridge the gap before d-i-b support is fully deployed19:55
*** whenry has quit IRC19:55
ianwi don't want to complicate the already complex d-i-b deployment with another new architecture at this stage19:55
*** baoli has joined #openstack-meeting19:55
jeblairianw: are you satisfied with karanbir's response, or would you like me to chase down people at hp for you?19:55
clarkbianw: ++ I think the easiest dib thing is to convert an existing image at a small scale19:56
ianwjeblair: karanbir's response is fine, and i'm working with him now, so all good there19:56
jeblairokay good19:56
clarkbianw: rather than mixing new image with dib at least until we are completely dib19:56
clarkbor nearly there19:56
ianwi am keeping up centos7 support within d-i-b in the background and as new images are released19:56
ianwhttps://review.openstack.org/#/c/118246/19:57
ianwso i hope that this will ease the eventual transition there19:57
*** morganfainberg is now known as needs19:57
*** needs is now known as needscoffee19:57
jeblaircool.  i think we may be ready to re-review the dib in config patches19:57
jeblairso hopefully we can start exercising that soon19:57
ianwbut that is my general plan.  i am told hp should have images "soon", so probably expect to see changes from me in that regard soon+a few days :)19:57
jeblairsounds good19:58
*** doude has quit IRC19:58
ianwthat is all i have, thanks19:58
jeblair#topic  The infra-manual is somewhat blocked on the Style Guide (pleia2)19:58
*** openstack changes topic to "The infra-manual is somewhat blocked on the Style Guide (pleia2) (Meeting topic: infra)"19:58
*** doude has joined #openstack-meeting19:58
pleia2real quick, if anyone has opinions, please dig back into July archives and say so, otherwise I plan to chat with anne about her thoughts19:59
pleia2#link http://lists.openstack.org/pipermail/openstack-infra/2014-July/thread.html#159119:59
*** jasondotstar has joined #openstack-meeting19:59
anteayathis came from a patch which used bold frequently19:59
anteayapleia2 felt it was overused19:59
Ajaeger1far too frequently - less is more with bold ;)19:59
anteayawe have no consensus on how often to use bold19:59
jeblairyeah.  i forget the rst syntax frequently19:59
anteayaright , so we need it written down20:00
anteayaand if using what docs have works, that works for me20:00
jeblairso having a style guide and making sure that we start out with a good consistent style will help20:00
* pleia2 nods20:00
jeblair(once the doc exists and uses conventions, it's much easier for follow-on edits to keep the same style)20:00
clarkbcan we use a template like for specs?20:00
jeblairand yeah, less is more with bold.  :)20:00
anteayahard to template if you look at teh patch offered20:00
jeblairand i think we're at time20:01
*** earnThis has joined #openstack-meeting20:01
annegent_pleia2: sure happy to give input, we have an entire tagging guide, but RST is quite the non-semantic beast20:01
*** penick has quit IRC20:01
jeblairanteaya: maybe let's just send a reminder to third-party folks about the wiki thing for now20:01
pleia2annegent_: thanks, I'll be in touch once I collect thoughts from the team :)20:01
annegent_jeblair: and exclamation marks!!! :)20:01
jeblairand discuss more next time20:01
anteayajeblair: will do20:01
fungiwe're at (over!) time20:01
jeblairthanks everyone !!!1one!20:01
jeblair#endmeeting20:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:01
openstackMeeting ended Tue Sep  2 20:01:52 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-09-02-19.01.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-09-02-19.01.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-09-02-19.01.log.html20:01
*** pballand has quit IRC20:02
*** penick has joined #openstack-meeting20:02
*** grantbow has left #openstack-meeting20:02
*** SumitNaiksatam has quit IRC20:02
ttxAnyone here for the TC meeting ?20:02
flaper87o/20:02
*** hashar has quit IRC20:02
vkmco/20:02
*** marcoemorais has quit IRC20:02
annegent_here20:03
markmchey20:03
jeblairo/20:03
ttxrussellb, mikal, mordred, devananda, vishy, markmcclain, jaypipes, sdague, dhellmann : around ?20:03
dhellmanno/20:03
vishyo/20:03
sdagueo/20:04
markmcclaino/20:04
*** pballand has joined #openstack-meeting20:04
mikalHi20:04
*** marcoemorais has joined #openstack-meeting20:04
mikalI need to bail out in about 30 minutes though to go to the airport20:04
ttxok quick then20:04
ttx#startmeeting tc20:04
openstackMeeting started Tue Sep  2 20:04:46 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:04
ttxOur agenda for today:20:04
*** openstack changes topic to " (Meeting topic: tc)"20:04
openstackThe meeting name has been set to 'tc'20:04
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:04
ttx#topic Final selection of our User Committee nominee20:05
*** openstack changes topic to "Final selection of our User Committee nominee (Meeting topic: tc)"20:05
*** pballand has quit IRC20:05
ttxThis is in replacement of Ryan Lane.20:05
ttxI got your suggestions and reached to them. The following people confirmed:20:05
ttxAndrew Mitry, Beth Cohen, Chet Burgess, Jacob Walcik, Jonathan Proulx20:05
ttxI set up a Condorcet poll so that we designate someone during this meeting20:05
ttxSending links now.20:05
dhellmanndo we have advocates who want to speak for these candidates? I don't actually know any of them.20:05
ttxOK sent. Please vote before the end of the meeting !20:05
ttxYes, any quick support  ?20:06
sdagueyeh, these folks are largely unknown to me as well, might be nice to get some statements from folks about them to help with the decision, otherwise I feel it will basically be random20:06
annegent_these are all great candidates, I'm happy to talk through support20:06
markmcyeah, I'm a bit stuck too20:06
annegent_and it's great we have more than before :)20:06
mikalChet is a nova dev, he's the only one I know20:07
ttxJon Proulx did some doc work20:07
annegent_Beth worked on the Architecture Design Guide and has been operating OpenStack clouds since pre-grizzly.20:07
ttxAndrew Mitry is the Comcast architect20:07
dhellmannis the candidate meant to be a user, or just represent technical folks on the user council?20:07
*** ekhugen has left #openstack-meeting20:07
annegent_Jacob Walcik helped me write the diablo install guide, ha ha. He is a Rackspace private cloud engineer who supports a ton of private clouds20:07
mikalChet's stackalytics: http://stackalytics.com/?release=all&user_id=cfb-n20:08
sdagueso we have affiliateion for those besides Jacob and Andrew? Curious what the rest's roles are wherever they happen to work20:08
jeblairsdague: ++ i don't feel i have enough information to make a recommendation20:08
jeblairsdague: that was to your previous point about getting statements from these folks20:08
annegent_Jonathan Proulx was an author on the Ops Guide and runs an OpenStack cloud at MIT and is very active on the operators mailing list. He tests upgrade instructions and most recently wrote a network troubleshooting section.20:08
mikalChet works for metacloud IIRC20:09
*** afazekas has quit IRC20:09
ttxAndrew is Comcast, Jon Proulx is MIT20:09
annegent_Beth works for verizon now, has worked for Cloud Technology Partners20:09
*** yamamoto has joined #openstack-meeting20:09
*** raildo1 has left #openstack-meeting20:09
sdagueannegent_: cool, thanks20:09
annegent_and to quantify "a ton" I think three digits?20:09
annegent_really they're all great candidates and I'd love to find ways to get them all involved regardless of an "appointment"20:10
ttxOK, we can close the vote tomorrow if you'd like time to research them more20:10
dhellmannindeed, it hardly feels right to choose if we have volunteers willing to serve (how often does *that* problem come up?)20:10
*** julim has quit IRC20:11
ttxthey are a limited crew dut to the NDA on the user survey though20:11
* russellb just joined, sorry for being late20:11
ttxso we have to pick20:11
russellb(plane, etc.)20:11
annegent_right dhellmann my thoughts exactly20:11
markmcyeah, the NDA thing makes this weird20:11
dhellmannttx: wow, ok, I didn't realize that was the constraint20:11
jeblairi love that we have an nda20:11
markmcalso means that ideally you don't want to be changing the people very often20:11
*** rushiagr is now known as rushiagr_away20:12
ttxok, how about we let that vote open until tomorrow night20:12
dhellmannsounds good20:12
annegent_that works20:12
ttxthat gives you time to do reasearch. You can also vote all equal20:13
ttxand defer to those with an opinion20:13
ttx#topic Graduation review: Zaqar (ex-Marconi) (part 1)20:13
*** openstack changes topic to "Graduation review: Zaqar (ex-Marconi) (part 1) (Meeting topic: tc)"20:13
ttxflaper87: o/20:13
*** julim has joined #openstack-meeting20:13
ttxAt every end of cycle we look at currently-incubated projects, discuss progress20:13
jeblairdid those who nominated these people have statements with them?20:13
flaper87o/20:13
ttxand see if any are ready to be made a part of the next OpenStack integrated release development cycle20:13
*** malini1 has joined #openstack-meeting20:13
ttxjeblair: no, we nominated them :)20:13
ttxWe did Barbican two weeks ago. Today (and possibly next week) we'll do Zaqar20:14
jeblairttx: i mean, did "we" include statements as to why? :)20:14
ttxThen we'll do Ironic next week (and possibly the next) when Deva is back from vacation20:14
ttxjeblair: anne nominated like almost all of them :)20:14
dhellmannjeblair: I saw names, but nothing very formal20:14
*** yamamoto has quit IRC20:14
ttxNB: kgriffs has recently moved to another position, so he designated flaper87 as his permanent delegate until the September election20:14
ttxLet me summarize the last Marconi graduation episode...20:14
*** rms_13_ has joined #openstack-meeting20:14
ttxAt the graduation review last cycle, I think the concerns fell into three broad categories20:14
ttx1. Pecan vs. Falcon, and more generally lack of alignment with the rest of OpenStack20:15
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2014-March/030385.html20:15
jeblairokay, so next time, we should ask for a narrative along with the nominating statement, because i have no basis for making the decision and have no avenues for any real research before tomorrow20:15
*** padkrish has joined #openstack-meeting20:15
ttx2. Data-plane vs. Control-plane approach20:15
ttxjeblair: +120:15
ttx3. Questionable backends (MongoDB/AGPL issue, SQLA db-as-a-queue antipattern)20:15
ttxboth exposed in that thread:20:15
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2014-March/030367.html20:15
ttxThen the graduation request was withdrawn:20:16
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2014-March/030638.html20:16
ttxfast-forward to today20:16
ttxflaper87: what would be your assessment of the current state of Zaqar in incubation?20:16
*** sballe has quit IRC20:16
*** jtomasek has quit IRC20:16
russellbflaper87: and thanks for joining to represent the project20:17
*** cipcosma has quit IRC20:17
flaper87So, we've addressed the missing pieaces we had since last graduation evaluation. 2 points remain to be discussed. The point w.r.t pecan vs falcon and the one with data-plane vs control-plne20:17
*** malini1 has quit IRC20:17
flaper87russellb: my pleasure :)20:17
*** malini1 has joined #openstack-meeting20:17
russellbthe data-plane vs control-plane thing is incredibly unfortunate, IMO, as it has been completely clear to me what zaqar was trying to be from the beginning20:17
flaper87As for #3, we've added (thanks to one very helpful GSoC mentee) a redis driver20:17
russellbas in, SQS like data API20:17
*** alkari has quit IRC20:18
flaper87russellb: +120:18
jeblairrussellb: i'm not sure i follow what you're saying20:18
russellbi'm saying it's unfortunate that the debate came up20:18
jeblairrussellb: thanks, that clarifies20:18
russellbit doesn't make sense to me20:18
flaper87What we've done for that matetr is to communicate and share as much as possible the project's goals20:18
russellbcool20:18
markmc#link https://wiki.openstack.org/wiki/Zaqar/Frequently_asked_questions#Is_Zaqar_a_provisioning_service_or_a_data_API.3F20:18
* markmc likes that summary of the data-orientated position of the team20:19
markmcthe API requirements, particularly20:19
russellbi guess we should go over each of the concerns ttx mentioned20:19
jeblairrussellb: i think, if i'm understanding it correctly, the relevance here though is not that it is implementing SQS, but rather that it is doing it from scratch rather than re-using existing queuing technologies20:19
russellband we've sort of already started on #220:19
jeblair(whew, i'm still on topic :)20:20
russellbjeblair: :)20:20
russellbjeblair: perhaps, though that wasn't the context of the debate as i understood it20:20
flaper87that wasn't the context20:20
russellbmore that folks fundamentally disagreed with an SQS like API in the first place20:20
markmcjeblair, I don't think I've ever seen a plausible description of how you'd implement a multi-tenant SQS-like REST API using existing queuing technologies20:20
flaper87the context was why the project is not providing, say, rabbitmq as a service20:20
russellbright, i think i've seen some pretty good analysis on that from zaqar, and they felt it didn't make sense20:21
markmcjeblair, e.g. using RabbitMQ as a backing for something like that seems bizarre to me20:21
sdagueso where I remain conflicted is whether SQS is essential infrastructure to OpenStack, vs. being a useful part of the ecosystem.20:21
russellbdoesn't mean the backends they have are the best approach, of course20:21
stevebakerfwiw heat will be using zaqar as an option regardless of integrated status, since it solves a real problem for us20:21
jeblairokay, so i guess there's two levels of potential objection -- that it does not use (eg) rabbit internally to back its api, and that it does not simply provision/expose (eg) rabbit20:21
jeblairit sounds like the data/control plane debate mostly focused on the second20:22
markmcyeah, exactly20:22
*** ominakov has quit IRC20:22
russellbthe first debate is really more about #3 in ttx's list20:22
russellberr20:22
vishythere is also the issue that if it really is just the second it shouldn’t be a service20:22
sdagueflaper87: are any openstack integrated projects besides heat looking at zaqar to fill some need?20:22
mikaljeblair: its certainly my recollection that people were upset / confused that rabbit was being reimplemented in mysql20:23
russellbi mean, should it use rabbitmq, or something else other than what it has today20:23
flaper87sdague: Trove and Swift20:23
russellbmikal: but it's not rabbit at all20:23
flaper87and horizon20:23
russellbit's very different20:23
flaper87sdague: ^20:23
sdagueflaper87: interesting, what's the swift use case?20:23
mikalrussellb: sure, but that's what people were saying last cycle20:23
russellbi know, and i think that's silly :)20:23
sdagueflaper87: or are those up there anywhere20:23
flaper87sdague: I still have to write swift's ones down because they came up in a quick chat with notmyname20:23
sdagueflaper87: ok20:24
annegent_mikal: yeah people are hearing queues and thinking amqp20:24
*** mrunge has quit IRC20:25
annegent_flaper87: it wasn't so much a swift use case as a heat use case?20:25
annegent_flaper87: iirc?20:25
flaper87annegent_: there are 4 projects that I've talked to and they've shared ideas and needs for zaqar: Horizon, Heat, Trove and swift20:25
flaper87I've started putting those use cases here: https://etherpad.openstack.org/p/zaqar-integrated-projects-use-cases20:26
sdagueflaper87: great20:26
*** kebray has quit IRC20:26
flaper87since mose of them happened on informal chats and talks at the ATL summit and during Juno20:26
* mikal looks20:26
flaper87s/mose/most/20:26
*** sballe has joined #openstack-meeting20:26
flaper87Trove's use case is to communicate with guest-agents20:27
ttxThe data-plane vs. control-plane discussion is somethign Zaqar has little leverage about -- if we decide we don't want to add data-plane stuff anymore, there is littlethey can do on their side20:27
ttxWhat about the other 2 concerns ?20:27
*** GheRivero_afk is now known as GheRivero20:27
mikalflaper87: how does ironic talk to its guest agent? Is that a use case as well?20:27
ttxI think the addiiton of Redis solves #320:27
*** thangp has joined #openstack-meeting20:28
flaper87mikal: I don't know how they do it but I think it might make sense for Ironic too20:28
ttxwe are no longer implementing a queue on top of SQL or AGPL20:28
gokrokveMurano is using MQ based agent too20:28
ttxIt's a bit toung though20:28
flaper87ttx: yup20:28
ttxflaper87: is it landed yet ? the redis support?20:28
ekarlso  sahara too no ?20:28
flaper87ttx: yup, yday20:28
ttxok20:28
ekarlsoprobably other projects as well just to budge in :p20:28
flaper87(phew)20:28
dhellmannwhich driver runs in the gate now?20:29
sdaguedhellmann: mongo20:29
ttxwhat about #1, alignment with the rest of openstack?20:29
dhellmannsdague: thanks20:29
russellbdhellmann: any comments on oslo integration?20:29
flaper87We've been adopting oslo libraries as they're released20:29
ttxi suspect it's tied to dataplane/controlpane discussion too, i.e. falcon justification is mostly that it's more dataplane-oriented than pecan20:29
flaper87and keeping the files coming from the incubator updated20:29
*** eglynn_ has joined #openstack-meeting20:30
*** mrodden has quit IRC20:30
dhellmannit looks like they have several of the low level libraries in their requirements file.20:30
dhellmannflaper87: are you the liaison, or is someone else doing that?20:30
russellbi don't think i've seen a whole lot of falcon discussion since the last round20:30
* mikal needs to drop off now for a flight, laters20:30
flaper87dhellmann: I am20:30
russellbwas there that i've forgotten?20:30
jrollmikal: not to derail, but ironic doesn't have a guest agent20:30
dhellmannrussellb: it hasn't come up again20:30
flaper87russellb: there hasn't been20:30
*** mrodden has joined #openstack-meeting20:30
russellbok, so a concern ... but i'd really hate for *that* to be the only blocker20:30
russellbi probably wouldn't block if that was the only thing personally20:31
russellbthat's still fixable, if the project commits to re-starting work there20:31
*** marcoemorais has quit IRC20:31
*** Ajaeger1 has quit IRC20:31
flaper87TBH, we focused on making v1.1 consistent and cleaning it up20:31
flaper87I think a better time to discuss a migration to Pecan would be v2 when it comes20:31
*** marcoemorais has joined #openstack-meeting20:32
annegent_russellb: yes, seems like our gap-analysis-style workflow would work for any sort of pecan<>flask work20:32
markmcflaper87, I saw that v2 is when you're planning on removing the lookup-message-by-ID thing?20:32
markmcflaper87, when do you think that work will happen?20:32
ttxflaper87: anything worty of note in https://wiki.openstack.org/wiki/Zaqar/Incubation/Graduation ?20:33
sdagueso from a deployment perspective if zaqar is in, that means operators have to deploy and maintain a nosql infrastructure20:33
russellbsdague: required?20:33
russellbit's all optional now right?20:33
*** ominakov has joined #openstack-meeting20:33
flaper87markmc: We're planning to start discussing it at the Kilo summit and we'll probably decide there if it makes sense to give the community a chance to digest v1.1 before start working on v2 or if we should probably just go for it20:33
sdaguerussellb: there is no real sqla backend20:33
*** rfolco has quit IRC20:33
russellbas in, only if you want zaqar for your tenants20:33
sdagueand we're talking about heat and other services requiring it20:33
russellbright, because we determined that was an anti-pattern, right?20:33
russellbi think other services using it should be optional, that's a scope jump20:34
russellbshould discuss that more20:34
russellbbecause originally this was a "tenant only" service in my view20:34
russellbnot infrastructure20:34
annegent_my sense is this project has a tenant only scope20:34
flaper87ttx: we've put lots of efforts on integrating with the whole OpenStack ecosystem and also on having a complete documentation for users and developers20:34
dhellmannthe heat use case is to communicate with tenants, though, right?20:34
*** julim has quit IRC20:34
sdagueannegent_: stevebaker just said heat was going to use it20:34
*** schwicht has quit IRC20:34
sdaguewhether or not zaqar is integrated20:34
*** julim has joined #openstack-meeting20:35
russellbstevebaker: could use some more detail on that i think20:35
russellbout of meeting perhaps20:35
*** zehicle has joined #openstack-meeting20:35
*** rfolco has joined #openstack-meeting20:35
stevebakerIt would be our prefered method for heat/server interaction, with a fallback to swift TempURLs if not available20:35
jeblairthe faq says it's very much over-cloud, so we're getting mixed messages here20:35
ekarlsoheat is gonna use what? sorry for not cathcing that20:35
sdagueputting zaqar in definitely has some implications for what infrastructure is expected to be maintained20:35
annegent_sdague: heat also was going to rely solely on keystone v3 when it wasn't widely deployed :)20:36
*** emagana has quit IRC20:36
annegent_stevebaker: ah there's the tie-in I was trying to recall, you have a method and a fallback20:36
stevebakerwe still support v2. This is different though, since the template author chooses what transport method they will use20:37
*** emagana has joined #openstack-meeting20:37
annegent_stevebaker: ok, that's a good point20:37
stevebakerthere is no magic, an explicit choice is always made20:37
sdagueit's really unfortunate that we're in a state where projects are only considered successful if they are granted integrated status, because to me zaqar feels like a solid part of the ecosystem, but I'm not sure I believe SQS is essential infrastructure.20:38
*** eghobo has joined #openstack-meeting20:38
russellbok, so if it's an optional tenant initiated thing, that seems reasonable to me20:38
ttxSo at this point I hear "operational infratsructure extra burden (due to NoSQL deploy)" and "should we really reinvent a queue system rather than piggyback on one"20:38
ttxanything else ?20:39
*** dhellman_ has joined #openstack-meeting20:39
russellbttx: and "API stability" i think, since they're already planning v2 things20:39
markmcclainrussellb: +120:39
ttxrussellb: ++20:39
*** otherwiseguy has quit IRC20:39
*** colinmcnamara has quit IRC20:39
*** julim has quit IRC20:39
sdaguedo we have information from deployers beyond rax? Is this seeing adoption in the community already?20:40
notmynameFYI I'd like scalable, durable, ha queues for internal swift (ie to more efficiently implement swift features20:40
flaper87russellb: not really planing v2, we want to give the community and ourselves enough time to use the existing API, which we consider stable20:40
russellbnotmyname: it's probably worth exploring that in more detail ... as it sounds like it's in conflict with what other projects use for "infrastructure" queues20:40
ttxI'm fine with keeping them in incubation over Api stability and freshness of Redis driver... but i don't want to keep them incubating if we don't believe deploying NoSQL is acceptable, or if we prefer control-plabe to data-plane. Because there is little short of rewriting all that they can fix that20:40
russellbas in, if what you're talking about isn't optional tenant initiated features, then i think it's out of the scope i had in mind20:40
sdaguenotmyname: do you see zaraq providing that better than an amqp bus?20:40
flaper87sdague: catalyst will (is?) use zaqar too20:41
russellbttx: yeah that makes sense20:41
markmcttx, agree20:41
*** emagana_ has joined #openstack-meeting20:41
annegent_My sense is that it's super useful for cloud tenants and would be great for our cloud providers to have it at the ready. And other integrated projects want this ability. They did a great job of writing docs too for multiple audiences.20:41
ttxso in all cases we need to make up our minds on those (is deploying NoSQL acceptable, is inventing our own queue acceptable, is data-plane acceptable)20:41
*** emagana has quit IRC20:41
flaper87FWIW, I think v1.1 is a stable API. It has things that some folks don't like but I wouldn't consider it unstable because of that20:41
*** otherwiseguy has joined #openstack-meeting20:41
ttxbecasue if we answer no, there is no need to keep them on the wire20:42
*** spzala has joined #openstack-meeting20:42
annegent_so from a docs perspective I won't cry "too heavy integration burden" - this team has done well.20:42
russellbflaper87: maybe a detailed response to each identified concerns before next week would assist20:42
flaper87russellb: +120:42
markmcttx, agree - they're the key questions; and sound more like incubation questions ... not that we can't revisit, though20:42
ttxmarkmc: I agree it would be unfortunate to reject on those architectural grounds, but if we don't believe that is accepatble, i prefer we reject late than we accept20:43
annegent_markmc: agreed20:43
russellbdefinitely need to resolve them, it's no fair to keep them on the wire20:43
jrollif no projects *require* zaqar, than why would deploying nosql be acceptable?20:43
russellbjroll: did you mean not acceptable?20:43
*** colinmcnamara has joined #openstack-meeting20:43
markmcttx, they're not so much architectural concerns as scope concerns, but yeah20:43
jrollrussellb: yes, sorry20:43
ttxI know mordred has a strong opinion on the dataplane vs. controlplane thing20:43
*** torgomatic has joined #openstack-meeting20:44
ttxhe should be coming back really soon now20:44
russellbjroll: i tend to agree with that, fwiw, though the increased burden should still not be taken lightly20:44
ttxI have a strong opinion that we should piggyback on domain specialists where we can20:44
ttxi.e. not reinvent queues20:44
jeblairi believe we can expect mordred and devanand1 back for next weeks meeting20:44
ttxunless we really really can't work with the existing ones20:44
russellbbut can we in this case?  more than they've done with redis?20:44
jrollrussellb: I'm always skeptical about deploying more services :)20:44
russellbrabbit isn't the answer, imo20:44
russellbfar from it20:44
flaper87re backing zaqar with rabbit: http://blog.flaper87.com/post/marconi-amqp-see-you-later/20:45
notmynamezaqar isn't reinventing queues. as in, it's offering things that don't currently existing with stuff like amqp. one example is that zaqar's queues are durable.20:45
markmcagree, I think we've chased that rabbit down the wrong hole20:45
vkmcIMO it's a different service, we shouldn't compare with Rabbit or AMQP20:45
*** atiwari has quit IRC20:45
russellbmarkmc: ++20:45
notmynamevkmc: ++20:45
vkmcwe are covering the cases that Amazon SQS/SNS cover20:45
ttxnotmyname, vkmc: good point20:46
ekarlsokinda like magneto db, would you call it that they are offering something that a layer ontop of cassandra has vs trying to cover features of say a google compute service or aws ?20:46
annegent_right, that's my thinking as well20:46
ttxflaper87: I think that's enough for this meeting, we'll continue next week. Anything we can discuss on the mailing-list between now and then will help clarify20:47
ttxflaper87: you got the list of "concerns" ?20:47
annegent_thanks flaper87 for taking up the ptl role20:47
*** AlkaD has quit IRC20:47
flaper87ttx: It'd be nice if we can summarize it now before you change topic20:47
flaper87annegent_: my pleasure!20:47
ttxok, let me try20:47
flaper87ttx: just to make sure we're on the same page20:48
*** AlkaD has joined #openstack-meeting20:48
ttx#info concern on operational burden of requiring NoSQL deploy expertise to the mix of openstack operational skills20:48
ttx#info concern on should we really reinvent a queue system rather than piggyback on one20:48
ttx(that one can be debunked by explaining the SQS case, durable queues, etc)20:49
ttx#info concern on dataplane vs. controlplane, should we add more dataplane things in the integrated release20:49
*** pballand has joined #openstack-meeting20:49
ttx#info concern on API v2 being already planned20:49
*** colinmcnamara has quit IRC20:50
markmcthat's an odd summary of the conversation, fwiw20:50
ttx#info concern on the maturity of the NoQSL not AGPL backend (Redis)20:50
markmcmakes it sound like all concern, no support20:50
*** colinmcnamara has joined #openstack-meeting20:50
jeblairmarkmc: it's not a summary of conversation, it's a summary of concerns :)20:50
ttxmarkmc: i'm trying to list the concerns for flaper87 to consume20:50
flaper87I'll put those concerns in an etherpad and answer them before next week20:50
markmcI honestly think they've addressed many of these20:50
*** AlkaD_ has joined #openstack-meeting20:51
*** AlkaD has quit IRC20:51
flaper87markmc: +120:51
ttxmarkmc: i'm not saying they didn't20:51
* flaper87 hides20:51
flaper87:D20:51
markmcand we're not doing a very good job of explaining why they're still a concern20:51
markmcit's like, "here guys, have another go on the merry-go-round"20:51
ttxI'm just trying to summarize what points are the potential pain points20:51
markmcsure20:51
ttxflaper87: does that work ? May I switch topic ?20:52
*** colinmcnamara has quit IRC20:52
*** eguz has joined #openstack-meeting20:52
flaper87ttx: go ahead, I got the list and I'll work on those before next week20:52
flaper87thanks everyone!20:52
russellbflaper87: thanks!20:52
ttxflaper87: you might want to push a governance change to support your graduation, too20:52
*** eguz has quit IRC20:52
ttxflaper87: contact me if you have doubts on how to do that20:52
ttx#topic Other governance changes20:52
*** openstack changes topic to "Other governance changes (Meeting topic: tc)"20:52
flaper87ttx: it will be my pleasure :)20:52
*** neelashah has quit IRC20:52
ttx* Propose guidelines for adopting new official projects (https://review.openstack.org/116727)20:52
ttxDiscussion is still on-going on this one.20:53
ttxI wonder if we can really adopt those before we discuss the future of Programs though20:53
*** mestery has quit IRC20:53
*** mwagner_lap has quit IRC20:53
ttxlike whether the current program team really takes responsibility over the adopted project or not20:53
ttx* Add reference to neutronincubator project (https://review.openstack.org/117000)20:53
ttxOn this one there is clear disagreement from Infra on the approach chosen in Neutron20:53
ttxjeblair started a thread at:20:53
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2014-August/044125.html20:53
ttxNot really sure it went anywhere though, and we need to make progress fast here20:53
ttxjeblair: how is that discussion going ?20:54
*** andreaf has quit IRC20:54
markmcclainttx: so we're tweaking the incubator proposal20:54
ttxmarkmcclain: to something that would work better for infra?20:54
markmcclainitems targeted for spinout will go into separate repo and items targeted to merge back into the main tree will look at feature branch20:54
ttxok20:55
anteayausually a patch to governance to add a repo doesn't happen until after the repo exists20:55
markmcclainthat should align and address jeblair's concerns20:55
*** SlickNik has joined #openstack-meeting20:55
ttxjeblair: remove your -1 when you're convinced20:55
jeblairmarkmcclain, ttx: i think those two directions are good20:55
*** mrodden has quit IRC20:55
*** mestery has joined #openstack-meeting20:55
ttx* Add a Mission Statement for Orchestration (Heat) (https://review.openstack.org/116703)20:55
markmcclainanteaya: wanted to discuss concept w/TC before adding workload to infra :)20:55
annegent_I'm trying to run through the guidelines for say, the training project20:55
ttxThis one is still ongoing20:55
ttx* Add oslo.log to the Oslo program (https://review.openstack.org/116994)20:56
*** mrodden has joined #openstack-meeting20:56
ttxThis one is a no-brainer, will approve post-meeting unless someone objects20:56
*** needscoffee is now known as morganfainberg20:56
ttx* Add oslo.concurrency to the Oslo program (https://review.openstack.org/117345)20:56
anteayamarkmcclain: kk, for the benefit of anyone wondering where the repo is20:56
*** eghobo has quit IRC20:56
ttxSame for this one20:56
ttx* The Oslo program is adopting pylockfile (https://review.openstack.org/117622)20:56
*** rushiagr_away is now known as rushiagr20:56
ttxThere is some discussion over this one, like *why* we are doing this20:56
ttxso i'll let it cook until next week20:56
ttx#topic Open discussion20:57
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:57
ttxjogo: want to mention your thread ?20:57
ttxAnything else, anyone?20:57
jogottx: sure20:57
*** eghobo has joined #openstack-meeting20:58
jogothread: http://lists.openstack.org/pipermail/openstack-tc/2014-September/000777.html20:58
sdagueI think jogo's idea was a pretty interesting one. I think if people came up with top 5 items that would be pretty interesting, and provide some feedback into what the cross project sessions should be20:58
jeblairjogo: ++20:58
*** marcoemorais has quit IRC20:58
jogosdague: yeah, right now I am more interested to see what the different lists are then figuring out what do do with the results20:59
*** marcoemorais has joined #openstack-meeting20:59
jogoas I am not sure what to expect20:59
*** marcoemorais has quit IRC20:59
jeblairwe've talked about the desirability of this, and jogo's suggestion gives us some concrete structure for how to get started20:59
*** marcoemorais has joined #openstack-meeting20:59
dhellmannshould we hold that discussion on the -dev list, or the tc list?20:59
ttxok, post them on the -dev list20:59
russellbi think it's a useful exercise20:59
*** baoli has quit IRC20:59
russellbi think it's also worth making sure we all agree on what problem we're trying to solve with the exercise20:59
dhellmannjogo, maybe you can start a thread on the -dev list then for us to reply to?21:00
ttxdhellman_: I wanted us to agree that it was a good idea first, but yes, the posts themselves should be on -dev21:00
russellbincreased focus is definitely good, though i think the bigger pain (that leads to people thinking about focus) is just our review bottleneck problems21:00
*** baoli has joined #openstack-meeting21:00
ttxjogo: sounds like the go-ahead you've been waiting for21:00
dhellmannttx: makes sense21:00
russellboverall project throughput21:00
jogottx dhellmann: great I will start a -dev ML thread for folks to respond to21:00
russellband also talk about what the expected consumption of this list would be in the end21:00
dhellmannrussellb: perhaps we should be thinking about ways to train more reviewers, then21:00
jogoI will focus the thread on TC memebers but leave it open for anyone to respond to21:00
*** IanGovett has quit IRC21:01
russellbas in, is it just a sync exercise?  or is it intended to go into saying "no" more?  or?21:01
anteayaalso I think it will be good as a focusing excerise for the driver writers to recognize what *is* important to the community as a whole21:01
*** jjmb has joined #openstack-meeting21:01
dhellmannrussellb: I would like for us to pick 1-2 items from the list and put together a "task force" or whatever to actually work on them21:01
* russellb nods21:01
russellbyeah that's all good stuff21:01
*** marcoemorais has quit IRC21:01
anteayathey might be surprised that it isn't *their* plugin21:01
jeblairto provide ptls/core teams some coverage in setting individual project priorities21:01
dhellmannrussellb: the example I gave in another thread was sdague's log standardization, and notification standardization would be another21:01
jogorussellb: I was envisioning this as just an exercise to see where we stand21:01
annegent_review bottleneck and scope widening are hand-in-hand from my view21:01
sdaguehonestly, right now, I'm mostly interested in figuring out how my view of the world with what I think is critical aligns with other people in the community21:01
*** emagana_ has quit IRC21:01
ttxok, time is up21:01
*** marcoemorais has joined #openstack-meeting21:02
jogosdague: ++ thats the idea21:02
russellbcool, yeah, that sounds useful21:02
ttxThanks everyone21:02
russellbthanks everyone!21:02
ttx#endmeeting21:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:02
openstackMeeting ended Tue Sep  2 21:02:15 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-09-02-20.04.html21:02
dhellmannsdague: that would be useful, too21:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-09-02-20.04.txt21:02
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-09-02-20.04.log.html21:02
ttxdhellmann, dolphm, notmyname, eglynn, markwash, jgriffith, mikal, zaneb, david-lyle, mestery, SlickNik, SergeyLukjanov: around ?21:02
david-lyleo/21:02
dhellmanno/21:02
*** emagana has joined #openstack-meeting21:02
eglynn_o/21:02
mestery\o/21:02
SergeyLukjanovo/21:02
notmynamehere21:02
ttxstevebaker is standing in for zaneb21:02
markwash__o/21:02
stevebaker\o21:02
*** lsell has joined #openstack-meeting21:02
*** markmc has quit IRC21:02
ttx#startmeeting project21:02
openstackMeeting started Tue Sep  2 21:02:55 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** openstack changes topic to " (Meeting topic: project)"21:02
openstackThe meeting name has been set to 'project'21:03
ttxOur agenda for today:21:03
*** emagana has quit IRC21:03
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:03
*** emagana has joined #openstack-meeting21:03
*** rossk has joined #openstack-meeting21:03
ttx#topic News from the 1:1 sync points21:03
*** openstack changes topic to "News from the 1:1 sync points (Meeting topic: project)"21:03
ttxHere is the log:21:03
ttx#link http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-09-02-08.00.html21:03
*** esker has quit IRC21:03
ttxWe missed Cinder and Heat, will cover those later in this meeting21:03
ttxSwift released 2.1.0 on Monday and was excused21:03
ttxThe general idea is that today is the last day to approve stuff for juno21:03
ttxTomorrow we'll defer stuff that's not approved yet21:04
ttxand then we'll wait for the gate to catch up and retry stuff21:04
ttxIn time for tagging J3 on Thursday21:04
ttxso that means today is really last review day21:04
ttx#topic Other program news21:05
*** openstack changes topic to "Other program news (Meeting topic: project)"21:05
ttxAny other program with a quick announcement ?21:05
mtreinishttx: nothing from me this week21:05
*** eghobo has quit IRC21:05
ttxjeblair: ?21:05
*** eghobo has joined #openstack-meeting21:05
jeblairttx: nak21:06
ttxok, skipping to design summit discussion while we have everyone21:06
ttx#topic Design Summit session scheduling21:06
*** openstack changes topic to "Design Summit session scheduling (Meeting topic: project)"21:06
ttxI'm considering dropping the "session suggestion" website in favor of self-organization within teams (like etherpads and ML discussions)21:06
ttxThe idea being we'll likely have a lot less slots for scheduled sessions, so rather than denying a lot more (which is negative), we should encourage people to join schedule discussions (which is positive)21:06
ttxWe'd only use the session suggestion website for "other" projects and for the final scheduling step21:06
mestery++ to that idea!21:06
ttxWould anybody regret the open "suggestion" thing ?21:07
mesteryI think this is a very productive way for teams to work together on proposing relevant sessions.21:07
jeblairttx: wfm21:07
david-lyle+121:07
eglynn_ttx: why are we likely have a lot less slots for scheduled sessions this time round?21:07
ttxI think we need to make sure we reach out to operators so that they participate in that per-program topic scheduling activity21:07
mtreinishttx: +121:07
*** pballand has quit IRC21:07
ttxeglynn_: because we are likely to use Friday for contributors gatherings21:07
ttxthat's one day left21:08
ttxless*21:08
SlickNikttx: I like the idea self-organization idea as well. So +1 from me.21:08
eglynn_a-ha, k21:08
ttxSo that it works, you'll have to be very inclusive21:08
eglynn_I'm open to open scheduling, for the Juno summit we did it a collaborative exercise among the ceilometer core team21:08
ttxbut overall I think it should yield better results21:08
eglynn_"very inclusive" == "include a wider group than the core team"?21:09
*** malini1 has left #openstack-meeting21:09
ttxyes, and reach to operators ion their list21:09
*** flaper87 is now known as flaper87|afk21:09
*** yamamoto has joined #openstack-meeting21:09
ttxmake sure you have a list of topics and all the data you need to choose21:09
ttxwe'll likely have scheduled slots and the "gathering" thing21:09
dhellmannwe've started an etherpad for oslo: https://etherpad.openstack.org/p/kilo-oslo-summit-topics21:09
ttxthe idea is to use scheduled slots for the stuff you want extra input in21:10
ttxsince it will appear on the schedule21:10
*** ametts has quit IRC21:10
*** aysyd has quit IRC21:10
eglynn_do we have an expectation that the proposer of a session is intending to drive the actual implementation of related BP(s) in Kilo?21:10
ttxwhile team-specific issues can be covered on ML,; spec or the Friday thing21:10
*** timello_ has quit IRC21:10
eglynn_as opposed to ... "this is something I'd love to see somebody else implement"21:10
SergeyLukjanovfwiw +1 on self org21:10
ttxeglynn_: no general expectation, but feel free to have a local one21:11
anteayattx not sure where to ask so I'll just interrupt, where do you want any third party discussions?21:11
dolphmeglynn_: i don't see much room for "session proposers" anymore. it's the community recognizing a need together.21:11
notmynamettx: I don't follow that last part. so each program still needs to come up with their list of "sessions"?21:11
dhellmanneglynn_: my etherpad template separates the "driver" from "interested" parties21:11
notmynamettx: and then schedule them?21:11
notmynamettx: or are programs assigned a block and they manage whatever in it?21:11
ttxnotmyname: yes, you'll still have a number of scheduled slots, in addition to the informal thing on Friday21:11
*** Leo_ has joined #openstack-meeting21:12
ttxnotmyname: on the Wednesday the conference is still running, so alignement has /some/ value21:12
*** spzala has quit IRC21:12
eglynn_dhellmann: OK so the proposer doesn't have to be the actual driver, but surely there must be an identified driver at some point? (preferably in advance of the design session occurring)21:12
ttxif really the 40-min step is a problem for you we could discuss non-alignment on the Tursday (since the conference will be over)21:13
notmynamettx: but instead of the webapp sessions suggestion, we have to get everyone together on an etherpad to choose the things to be talked about?21:13
dhellmanneglynn_: right, but if the proposer isn't the driver and no one picks it up, we probably won't talk about it21:13
dhellmanneglynn_: that still gives the community a way to ask us to work on something, though21:13
eglynn_dhellmann: yep, that's fair enough21:13
ttxnotmyname: yes, and which ones should have scheduled slots, and which ones should be kept for the Friday21:13
*** Leonr has quit IRC21:13
dolphmthe logical conclusion to this is using gerrit to manage sessions. just sayin'21:14
ttxI still have to check feasibility of the Friday thing wrt. the location21:14
ttxI'm visiting there on Monday21:14
*** annegent_ has quit IRC21:14
ttxso we should have a final plan next week21:14
*** yamamoto has quit IRC21:14
ttxi'll keep you all posted21:14
ttxok, moving on21:14
notmynameI guess I don't see the advantage of scheduling on an etherpad vs suggestion and scheduling via the webapp21:14
*** rushiagr is now known as rushiagr_away21:14
mesterynotmyname: To that point, I agree, the webapp has some advantage there.21:15
ttxit's a way to choose more collectively, and to avoid crazy proposals21:15
ttxI think eterpad is easier to mix and merge and discuss21:15
ttxthan the webapp with all its limitations21:15
*** Mandell has quit IRC21:15
notmynamehow are they mutually exclusive? suggest things on the webapp and then, if necessary, use an etherpad during a team meeting21:16
ttxit's just a bit more painful to merge sessions etc21:16
dolphm++21:16
*** Mandell has joined #openstack-meeting21:16
ttxalso there is less frustration about your proposal being "rejected"21:16
stevebakerwe transferred everything to an etherpad anyway21:16
ttxshould cut down my hate mail in half21:16
eglynn_notmyname: yep, that kinda how we did for the ceilo track in Juno ... except with s/etherpad/googledoc/21:16
SlickNikstevebaker / ttx: That's what we ended up doing as well21:17
anteayattx +21:17
SlickNik(transferring to etherpad)21:17
ttxnotmyname: if you want to use the webapp as your etherpad, we can do that for you21:17
ttxthe site will run for "other projects" track anyway21:18
notmynamettx: no, I'm not trying to do something different. I'm trying to figure out what problem is being solved. I never had too many issues with the existing tool21:18
ttxbut i figured removing the parallel CFP completely would just be clearer21:18
*** mattgriffin has quit IRC21:18
*** atiwari has joined #openstack-meeting21:18
ttxnotmyname: so issues: parallel CFp confusing the hell out of people, hate mail when people see their session rejected21:19
ttxvs. collaborative schedule editing in a friendly atmosphere.21:19
dhellmannnotmyname: we are trying to make the summit planning a discussion among the core team rather than a free-for-all21:19
notmynamewhat parallel CFP? between conference and summit? or between differetn programs?21:19
ttxnotmyname: between conference and summit.21:19
notmynameok21:19
eglynn_ttx: what approx timeline is envisaged for this design session proposal gathering?21:19
ttxnotmyname: also additional benefit of not ahving to parse crazy proposals from non-contributors21:20
ttxmid Sept-mid-Oct21:20
dolphmttx: and one line proposals21:20
eglynn_k, thanks21:20
ttxok, moving on21:20
ttx#topic Early Kilo deferrals21:20
*** openstack changes topic to "Early Kilo deferrals (Meeting topic: project)"21:20
ttxI'd like to look at stuff that just can't make it at this point and which should be deferred at this point21:20
*** jasondotstar has quit IRC21:20
*** nelsnelson has quit IRC21:20
*** weshay has quit IRC21:21
ttxIf you have stuff that is missing so many reviews it can't possibly make it now, you should defer it to kilo by marking in Deferred on your j3 plan21:21
*** adahms has joined #openstack-meeting21:21
dhellmannI went ahead and moved a few things to a kilo series already. Should I move those back?21:21
stevebakerttx: what is the FFE process?21:21
eglynn_can't possibily make it even with an FFE?21:22
SlickNikttx: how should we handle BPs that we anticipate getting an FFE for?21:22
ttxdhellman_: no, kilo is fine21:22
* mestery has been moving things out of Juno but not into Kilo yet.21:22
*** Murali has quit IRC21:22
ttxSlickNik: you could move them to RC1 and we'll review them friday21:22
*** atiwari has quit IRC21:22
SlickNikttx: okay, sounds good.21:22
ttxstevebaker: Starting friday we'll start ML threads for every exception21:22
*** Murali has joined #openstack-meeting21:23
stevebakerttx: ok, thanks21:23
*** otherwiseguy has quit IRC21:23
ttxand you can push the candidates to the RC1 milestone21:23
*** atiwari has joined #openstack-meeting21:23
*** otherwiseguy has joined #openstack-meeting21:23
ttxi'll talk to you all tomorrow to cut down the list to in-flight stuff21:24
*** andreykurilin_ has quit IRC21:24
ttxAny question on that before we sync specifically on heat and Cinder ?21:24
ttxmestery: any progress today?21:25
mesteryttx: Some progress yes, still looking at needing a few FFEs post Thursday, but trying to minimize.21:25
* mestery has been working the review board, LP, the phone, and email all day trying to wrangle things together.21:25
ttxdavid-lyle: how about you ? your list is pretty large too21:26
david-lylecutting it down now21:26
david-lylea couple are close to inflight as well21:26
ttxok, we'll sync tomorrow on progress21:27
ttxkeep the gate busy tonight21:27
ttx#topic Heat status21:27
*** openstack changes topic to "Heat status (Meeting topic: project)"21:27
ttxstevebaker: around?21:27
stevebakery21:27
ttxyou still have 11 in progress21:27
ttxstevebaker: which ones are you likely to require FFE for ?21:28
ttxthe 3 remaining "high" ones ?21:28
stevebakermaybe some of the mediums too21:28
stevebakersome just need reviews and may just miss the deadline21:29
*** tbarron has quit IRC21:29
ttxany chance you could get a few more approved before they require exceptions?.21:29
*** emagana has quit IRC21:29
ttxexceptions create disruption, so we need to minimize them21:29
*** doude has quit IRC21:30
*** emagana has joined #openstack-meeting21:30
stevebakeryes, will drum up reviews today. there are quite a few low-risk changes too, which may help their FFE case21:30
stevebakerI don't see any bugs which must be in j-321:30
ttxstevebaker: when can I talk to you tomorrow to finalize the list (keep only in-flight stuff in) ?21:30
ttx19:00 UTC ?21:31
stevebakerttx: this time tomorrow?21:31
ttxthat's a bit late for me21:31
*** mmedvede has quit IRC21:31
*** thangp has quit IRC21:31
stevebakerttx: I'll ping you when I'm concious enough to form words21:31
ttxstevebaker: how early can you make it?21:31
*** Mandell has quit IRC21:32
*** samcdona has quit IRC21:32
ttxhm, ok I'll try to keep an eye on IRC21:32
*** morganfainberg is now known as steve_notmorgan21:32
stevebaker~1900UTC21:32
ttxjgriffith: around?21:32
jgriffithttx: present21:32
ttxstevebaker: i'll be back online around 19:00 utc tomorrow21:32
ttx#topic Cinder status21:32
stevebakerttx: ok21:32
*** openstack changes topic to "Cinder status (Meeting topic: project)"21:32
*** steve_notmorgan is now known as morganfainberg21:32
ttx#link https://launchpad.net/cinder/+milestone/juno-321:33
ttxjgriffith: 6 still up21:33
jgriffithttx: so I believe I'll be dumping the following:21:33
jgriffithttx: secure NFS21:33
*** Sukhdev has joined #openstack-meeting21:33
*** jjmb has quit IRC21:33
jgriffithttx: Cisco device FC zone lifecycle21:33
jgriffithttx: the others are "close"21:33
ttxok21:34
jgriffithttx: and would be willing to do exceptions for21:34
jgriffithttx: the smb stuff is locked up with dependencies on other issues21:34
ttxi'll be in touch tomorrow so that we defer/FFE everything that's not in-flight by then21:34
*** emagana has quit IRC21:34
jgriffithttx: ok21:34
ttxso approve as much as you can today21:34
*** kgriffs has left #openstack-meeting21:34
ttxjgriffith: will be pinging you in your morning :)21:35
jgriffithttx: :)21:35
*** changbl has quit IRC21:35
*** vkmc has quit IRC21:35
*** ominakov has quit IRC21:36
ttx#topic Open discussion21:36
*** openstack changes topic to "Open discussion (Meeting topic: project)"21:36
ttxAnything else, anyone ?21:36
notmynamettx: I still dont' get the summit scheduling21:37
notmynamettx: but we can address that on the ML if necessary21:37
*** penick has quit IRC21:37
*** emagana has joined #openstack-meeting21:37
*** dkranz has quit IRC21:37
ttxnotmyname: oops, replied on -dev to you21:38
notmynameis there one big collaborative list of proposed sessions for all programs?21:38
notmynameor is it still a per-program list?21:39
*** mitarun has joined #openstack-meeting21:39
ttxnotmyname: at this point, per-program lists21:40
ttxsome on etherpads, some on whatever21:41
ttxmost often on etherpads21:41
ttxannounced on -dev threads recently21:41
notmynameok21:41
*** vivek-ebay has joined #openstack-meeting21:41
ttxok, let's close this one21:42
stevebakernotmyname: its up to you whether you have strict 40 minute slots, or larger chunks with topic themes21:42
eglynn_BTW wouldn't the timing be likely to push the summit scheduling into the new PTLs' terms?21:42
eglynn_... not that it's unlikely a lot of existing PTLs will retain their positions21:42
eglynn_... just I guess we shouldn't be making any assumptions about the election outcomes, right?21:42
stevebakereglynn_: it always has been the new PTL21:42
*** jckasper has quit IRC21:42
notmynameeglynn_: new PTLs always do the summit sessions21:42
*** jgrimm is now known as zz_jgrimm21:42
notmyname"new"21:42
ttxeglynn_: yes, final stuff is definitely in the future PTLs hands21:42
eglynn_stevebaker, notmyname, ttx: yep, so we shouldn't be deciding now how they might want to play this, or?21:43
ttxeglynn_: unfortunately some things need to be decided before21:43
ttxlike the format21:43
mesteryttx: ++21:43
ttxwhich is what we discuss now21:43
stevebakereglynn_: I'm sure some pre-planning could be done though21:43
eglynn_fair nuffski21:44
ttxalso, brainstorming themes can start now21:44
ttxI doubt the new PTL would object to open brainstorming21:44
ttx"new"21:44
*** mitarun has quit IRC21:44
eglynn_ttx: yep, that's a fair point21:44
eglynn_open-ness == "motherhood and apple pie" :)21:45
*** earnThis has left #openstack-meeting21:45
ttxok, really closing now21:45
ttxthanks everyone21:45
ttx#endmeeting21:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:45
openstackMeeting ended Tue Sep  2 21:45:35 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2014/project.2014-09-02-21.02.html21:45
eglynn_g'night all21:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2014/project.2014-09-02-21.02.txt21:45
SergeyLukjanovttx, thx21:45
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2014/project.2014-09-02-21.02.log.html21:45
SlickNikThanks ttx21:45
SlickNikTalk to you tomorrow.21:45
mesterybye!21:45
*** rodrigods has quit IRC21:46
*** Mandell has joined #openstack-meeting21:47
*** sdake has joined #openstack-meeting21:49
*** sdake has quit IRC21:49
*** sdake has joined #openstack-meeting21:49
*** sballe_ has joined #openstack-meeting21:49
*** mchalla has quit IRC21:50
*** masayukig has quit IRC21:52
*** annegent_ has joined #openstack-meeting21:53
*** sballe has quit IRC21:53
*** ayoung has quit IRC21:54
*** dhellman_ has quit IRC21:54
*** padkrish has quit IRC21:55
*** alexandra_ has joined #openstack-meeting21:56
*** emagana has quit IRC21:57
*** alexpilotti has quit IRC21:57
*** emagana has joined #openstack-meeting21:57
*** masayukig has joined #openstack-meeting21:57
*** pnavarro has quit IRC21:58
*** ominakov has joined #openstack-meeting21:58
*** roshanagr has joined #openstack-meeting21:58
*** JRobinson__ has joined #openstack-meeting21:59
*** annegent_ has quit IRC21:59
*** emagana_ has joined #openstack-meeting22:00
*** emagana has quit IRC22:00
*** roshanagr has left #openstack-meeting22:02
*** annegent_ has joined #openstack-meeting22:02
*** asalkeld has joined #openstack-meeting22:03
*** asalkeld has left #openstack-meeting22:03
*** mchalla has joined #openstack-meeting22:03
*** bknudson has quit IRC22:05
*** vivek-ebay has quit IRC22:05
*** vivek-ebay has joined #openstack-meeting22:07
*** dims has quit IRC22:07
*** dims has joined #openstack-meeting22:08
*** emagana_ has quit IRC22:08
*** emagana has joined #openstack-meeting22:09
*** yamamoto has joined #openstack-meeting22:09
*** dpaterson has quit IRC22:11
*** dims has quit IRC22:12
*** jpeeler has quit IRC22:12
*** emagana has quit IRC22:13
*** Murali has quit IRC22:13
*** yamamoto has quit IRC22:14
*** emagana has joined #openstack-meeting22:14
*** atiwari has quit IRC22:14
*** annegent_ has quit IRC22:15
*** annegentle has joined #openstack-meeting22:15
*** colinmcnamara has joined #openstack-meeting22:16
*** rockyg has quit IRC22:16
*** kebray has joined #openstack-meeting22:16
*** matrohon has quit IRC22:17
*** ominakov has quit IRC22:19
*** stevemar has quit IRC22:21
*** kenhui has quit IRC22:21
*** jecarey_ has quit IRC22:21
*** eglynn_ has quit IRC22:23
*** aloga has quit IRC22:25
*** ominakov has joined #openstack-meeting22:25
*** ominakov has quit IRC22:26
*** marcoemorais has quit IRC22:26
*** marcoemorais has joined #openstack-meeting22:27
*** ildikov has joined #openstack-meeting22:28
*** vkmc has joined #openstack-meeting22:30
*** vkmc has quit IRC22:30
*** vkmc has joined #openstack-meeting22:30
*** bdpayne has quit IRC22:31
*** bdpayne has joined #openstack-meeting22:32
*** aloga has joined #openstack-meeting22:32
*** markwash__ has quit IRC22:33
*** AlkaD_ has quit IRC22:34
*** markwash__ has joined #openstack-meeting22:35
*** prad has quit IRC22:36
*** esheffield has quit IRC22:39
*** mchalla has quit IRC22:42
*** emagana has quit IRC22:45
*** emagana has joined #openstack-meeting22:45
*** pballand has joined #openstack-meeting22:48
*** emagana has quit IRC22:50
*** nijaba_ has quit IRC22:51
*** jjmb has joined #openstack-meeting22:53
*** stevemar has joined #openstack-meeting22:54
*** samcdona has joined #openstack-meeting22:54
*** haleyb_ has joined #openstack-meeting22:56
*** colinmcnamara has quit IRC22:58
*** rbak has quit IRC22:58
*** MaxV has quit IRC22:59
*** colinmcnamara has joined #openstack-meeting23:01
*** vivek-ebay has quit IRC23:01
*** david-lyle has quit IRC23:02
*** ivasev has quit IRC23:04
*** Leo_ has quit IRC23:04
*** vijendar has quit IRC23:05
*** baoli has quit IRC23:05
*** mdenny has quit IRC23:06
*** ignacio-scopett1 has joined #openstack-meeting23:06
*** emagana has joined #openstack-meeting23:07
*** eharney has quit IRC23:07
*** marcoemorais has quit IRC23:07
*** ignacio-scopetta has quit IRC23:07
*** penick has joined #openstack-meeting23:08
*** markwash__ has quit IRC23:08
*** marcoemorais has joined #openstack-meeting23:08
*** pballand has quit IRC23:09
*** marcoemorais has quit IRC23:09
*** yamamoto has joined #openstack-meeting23:09
*** marcoemorais has joined #openstack-meeting23:09
*** haleyb_ has quit IRC23:10
*** markwash__ has joined #openstack-meeting23:10
*** pballand has joined #openstack-meeting23:11
*** carl_baldwin has quit IRC23:11
*** IanGovett has joined #openstack-meeting23:11
*** vivek-ebay has joined #openstack-meeting23:12
*** natarajk has left #openstack-meeting23:12
*** haleyb_ has joined #openstack-meeting23:12
*** whenry has joined #openstack-meeting23:14
*** yamamoto has quit IRC23:14
*** rm_work|away is now known as rm_work23:16
*** tongli has quit IRC23:16
*** tongli has joined #openstack-meeting23:16
*** pballand has quit IRC23:17
*** Mandell has quit IRC23:17
*** adahms has quit IRC23:17
*** Mandell has joined #openstack-meeting23:17
*** ianw has quit IRC23:17
*** adahms has joined #openstack-meeting23:17
*** ianw has joined #openstack-meeting23:18
*** Riddhi has quit IRC23:20
*** gokrokve has quit IRC23:23
*** gokrokve has joined #openstack-meeting23:23
*** topol has quit IRC23:24
*** ivar-lazzaro has quit IRC23:26
*** ignacio-scopett1 has quit IRC23:26
*** ignacio-scopetta has joined #openstack-meeting23:27
*** bdpayne has quit IRC23:27
*** vivek-ebay has quit IRC23:31
*** penick has quit IRC23:31
*** vivek-ebay has joined #openstack-meeting23:32
*** haleyb_ has quit IRC23:32
*** bdpayne has joined #openstack-meeting23:32
*** kevinconway has quit IRC23:32
*** marcoemorais has quit IRC23:33
*** haleyb_ has joined #openstack-meeting23:33
*** marcoemorais has joined #openstack-meeting23:33
*** penick has joined #openstack-meeting23:33
*** Sukhdev has quit IRC23:33
*** alex_xu has joined #openstack-meeting23:33
*** marcoemorais has quit IRC23:34
*** marcoemorais has joined #openstack-meeting23:34
*** stevemar has quit IRC23:35
*** oomichi has quit IRC23:35
*** nelsnelson has joined #openstack-meeting23:37
*** markmcclain has quit IRC23:37
*** emagana has quit IRC23:37
*** haleyb_ has quit IRC23:38
*** haleyb_ has joined #openstack-meeting23:38
*** padkrish has joined #openstack-meeting23:39
*** padkrish has quit IRC23:42
*** flaviof is now known as flaviof_zzz23:43
*** gokrokve has quit IRC23:44
*** oomichi has joined #openstack-meeting23:45
*** gokrokve has joined #openstack-meeting23:45
*** ivar-lazzaro has joined #openstack-meeting23:46
*** reed has joined #openstack-meeting23:46
*** yamamoto has joined #openstack-meeting23:46
*** jmontemayor has quit IRC23:47
*** brucer has joined #openstack-meeting23:48
*** gokrokve has quit IRC23:49
*** emagana has joined #openstack-meeting23:50
*** n0ano has quit IRC23:51
*** nijaba has joined #openstack-meeting23:53
*** nijaba has quit IRC23:53
*** nijaba has joined #openstack-meeting23:53
*** johnpur has left #openstack-meeting23:54
*** bdpayne has quit IRC23:55
*** alex_xu has quit IRC23:56
*** Riddhi has joined #openstack-meeting23:56
*** alexandra_ is now known as asettle23:56
*** whenry has quit IRC23:56

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