Tuesday, 2014-08-12

*** MaxV has quit IRC00:00
*** vivek-ebay has quit IRC00:01
*** sdake_ has joined #openstack-meeting00:02
*** nati_ueno has quit IRC00:02
*** ianw has quit IRC00:02
*** esker has quit IRC00:03
*** e0ne has quit IRC00:06
*** MarkAtwood has quit IRC00:08
*** e0ne has joined #openstack-meeting00:10
*** otherwiseguy has joined #openstack-meeting00:11
*** ianw has joined #openstack-meeting00:11
*** e0ne has quit IRC00:13
*** fawadkhaliq has quit IRC00:13
*** fawadkhaliq has joined #openstack-meeting00:14
*** yingjun has joined #openstack-meeting00:14
*** baoli has joined #openstack-meeting00:16
*** funzo has quit IRC00:17
*** tomoe_ has quit IRC00:17
*** e0ne has joined #openstack-meeting00:17
*** tomoe_ has joined #openstack-meeting00:17
*** nati_ueno has joined #openstack-meeting00:18
*** nelsnelson has quit IRC00:18
*** yingjun has quit IRC00:19
*** yingjun has joined #openstack-meeting00:19
*** nelsnelson has joined #openstack-meeting00:22
*** shashankhegde has quit IRC00:23
*** gyee has quit IRC00:25
*** tsekiyam_ has joined #openstack-meeting00:28
*** zhhuabj has joined #openstack-meeting00:28
*** MaxV has joined #openstack-meeting00:31
*** JRobinson__ has joined #openstack-meeting00:31
*** tsekiyama has quit IRC00:31
*** armax has left #openstack-meeting00:32
*** yingjun has quit IRC00:33
*** mtanino has quit IRC00:33
*** e0ne has quit IRC00:33
*** vermarah_ has quit IRC00:34
*** vermarah has quit IRC00:34
*** gokrokve has quit IRC00:35
*** whenry has quit IRC00:35
*** MaxV has quit IRC00:36
*** fnaval has quit IRC00:39
*** fnaval has joined #openstack-meeting00:39
*** Rao has quit IRC00:41
*** nati_ueno has quit IRC00:42
*** tsekiyama has joined #openstack-meeting00:43
*** SumitNaiksatam has quit IRC00:43
*** fnaval has quit IRC00:44
*** banix has joined #openstack-meeting00:45
*** tsekiyam_ has quit IRC00:46
*** joesavak has joined #openstack-meeting00:46
*** marun has quit IRC00:46
*** eharney has joined #openstack-meeting00:46
*** marun has joined #openstack-meeting00:47
*** otter768 has joined #openstack-meeting00:49
*** joesavak has quit IRC00:51
*** ramashri has quit IRC00:52
*** joesavak has joined #openstack-meeting00:52
*** ominakov has joined #openstack-meeting00:56
*** jsavak has joined #openstack-meeting00:57
*** neelashah has joined #openstack-meeting00:57
*** leeantho has quit IRC00:58
*** bdpayne has quit IRC00:58
*** yaguang has joined #openstack-meeting00:59
*** joesavak has quit IRC00:59
*** IanGovett has quit IRC01:00
*** VijayB_ has quit IRC01:00
*** Ish__ has quit IRC01:00
*** SumitNaiksatam has joined #openstack-meeting01:02
*** amcrn has quit IRC01:02
*** jsavak has quit IRC01:04
*** Riddhi has joined #openstack-meeting01:06
*** epico has joined #openstack-meeting01:06
*** mchalla_ has quit IRC01:08
*** tbachman has left #openstack-meeting01:08
*** mchalla has joined #openstack-meeting01:09
*** moha_hunt has quit IRC01:09
*** fawadkhaliq has quit IRC01:10
*** hrybacki has quit IRC01:10
*** yingjun has joined #openstack-meeting01:10
*** eharney has quit IRC01:10
*** mlavalle has quit IRC01:11
*** mchalla has quit IRC01:11
*** mchalla has joined #openstack-meeting01:11
*** mchalla has quit IRC01:13
*** aysyd has quit IRC01:13
*** mchalla has joined #openstack-meeting01:13
*** rudrarugge has quit IRC01:15
*** baoli has quit IRC01:15
*** padkrish has quit IRC01:17
*** mchalla has quit IRC01:18
*** baoli has joined #openstack-meeting01:18
*** xianghuihui has quit IRC01:21
*** dsetia has quit IRC01:22
*** mberlin1 has joined #openstack-meeting01:25
*** tsekiyama has quit IRC01:25
*** comay has quit IRC01:25
*** mberlin has quit IRC01:26
*** xianghui has joined #openstack-meeting01:26
*** SumitNaiksatam has quit IRC01:28
*** Slower has quit IRC01:28
*** novas0x2a|laptop has quit IRC01:28
*** gokrokve has joined #openstack-meeting01:29
*** SumitNaiksatam has joined #openstack-meeting01:29
*** rossk has quit IRC01:29
*** esker has joined #openstack-meeting01:31
*** MaxV has joined #openstack-meeting01:32
*** Mandell has quit IRC01:33
*** yingjun has quit IRC01:33
*** rudrarugge has joined #openstack-meeting01:33
*** yingjun has joined #openstack-meeting01:34
*** xianghui has quit IRC01:34
*** Mandell has joined #openstack-meeting01:34
*** xianghuihui has joined #openstack-meeting01:34
*** aranjan_ has joined #openstack-meeting01:35
*** carl_baldwin has quit IRC01:35
*** Slower has joined #openstack-meeting01:36
*** SumitNaiksatam has quit IRC01:36
*** MaxV has quit IRC01:36
*** yamahata has joined #openstack-meeting01:37
*** SumitNaiksatam has joined #openstack-meeting01:38
*** Mandell has quit IRC01:38
*** aranjan has quit IRC01:38
*** marun has quit IRC01:38
*** aranjan_ has quit IRC01:39
*** marun has joined #openstack-meeting01:40
*** SumitNaiksatam has quit IRC01:40
*** banix has quit IRC01:42
*** nati_ueno has joined #openstack-meeting01:42
*** nosnos has joined #openstack-meeting01:43
*** nosnos has quit IRC01:45
*** nosnos has joined #openstack-meeting01:45
*** nosnos has quit IRC01:46
*** nosnos has joined #openstack-meeting01:47
*** vkmc has quit IRC01:47
*** neelashah1 has joined #openstack-meeting01:47
*** neelashah has quit IRC01:48
*** haomaiwang has joined #openstack-meeting01:50
*** haomaiwang has quit IRC01:50
*** lcheng has quit IRC01:51
*** haomaiwang has joined #openstack-meeting01:51
*** vjay has joined #openstack-meeting01:52
*** JRobinson__ has quit IRC01:53
*** fnaval has joined #openstack-meeting01:54
*** haomai___ has joined #openstack-meeting01:58
*** fawadkhaliq has joined #openstack-meeting02:00
*** SridharR_ has joined #openstack-meeting02:00
*** weshay has quit IRC02:01
*** trinaths has joined #openstack-meeting02:01
*** haomaiwang has quit IRC02:02
*** fnaval has quit IRC02:03
*** SridharRamaswamy has quit IRC02:04
*** SridharR_ has quit IRC02:05
*** spzala has quit IRC02:09
*** noslzzp has joined #openstack-meeting02:09
*** gokrokve has quit IRC02:14
trinathsHi all, Very Good Morning02:16
*** cody-somerville has joined #openstack-meeting02:16
*** eguz has joined #openstack-meeting02:17
*** eghobo has quit IRC02:18
*** amalagon_ has joined #openstack-meeting02:19
*** [1]trinaths has joined #openstack-meeting02:20
*** bdpayne has joined #openstack-meeting02:20
*** banix has joined #openstack-meeting02:20
*** Poornima has joined #openstack-meeting02:21
*** kentwu_ has quit IRC02:21
*** trinaths has quit IRC02:22
*** [1]trinaths is now known as trinaths02:22
*** fnaval has joined #openstack-meeting02:22
*** yingjun has quit IRC02:23
*** fawadkhaliq has quit IRC02:23
*** yingjun has joined #openstack-meeting02:23
*** sbalukoff has quit IRC02:23
*** VijayB_ has joined #openstack-meeting02:25
*** trinaths has quit IRC02:25
*** vivek-ebay has joined #openstack-meeting02:28
*** eghobo has joined #openstack-meeting02:29
*** eghobo has quit IRC02:29
*** amalagon_ has quit IRC02:30
*** novas0x2a|laptop has joined #openstack-meeting02:31
*** MaxV has joined #openstack-meeting02:33
*** adalbas has quit IRC02:33
*** eguz has quit IRC02:33
*** vivek-eb_ has joined #openstack-meeting02:35
*** vivek-ebay has quit IRC02:35
*** MaxV has quit IRC02:37
*** haomai___ has quit IRC02:38
*** haomaiwang has joined #openstack-meeting02:39
*** dane_leblanc has joined #openstack-meeting02:40
*** cody-somerville has quit IRC02:41
*** Slower has quit IRC02:44
*** david-lyle has joined #openstack-meeting02:44
*** mchalla has joined #openstack-meeting02:45
*** sdake_ has quit IRC02:47
*** mchalla has quit IRC02:49
*** Slower has joined #openstack-meeting02:54
*** stevelle has joined #openstack-meeting02:55
*** dpaterson has quit IRC02:55
*** stevelle has left #openstack-meeting02:55
*** haomai___ has joined #openstack-meeting03:00
*** yanghe has joined #openstack-meeting03:00
*** esker has quit IRC03:01
*** Riddhi has quit IRC03:02
*** baoli has quit IRC03:03
*** haomaiwang has quit IRC03:03
*** jgrimm has joined #openstack-meeting03:05
*** matiu has joined #openstack-meeting03:05
*** VijayB_ has quit IRC03:06
*** aranjan has joined #openstack-meeting03:09
*** funzo has joined #openstack-meeting03:10
*** JRobinson__ has joined #openstack-meeting03:12
*** ArxCruz has quit IRC03:12
*** aranjan has quit IRC03:12
*** esheffield has quit IRC03:12
*** aranjan has joined #openstack-meeting03:13
*** Riddhi has joined #openstack-meeting03:14
*** tomoe_ has quit IRC03:14
*** tomoe_ has joined #openstack-meeting03:14
*** Mandell has joined #openstack-meeting03:18
*** Riddhi has quit IRC03:18
*** johnpur has left #openstack-meeting03:20
*** nosnos has quit IRC03:22
*** paragan has joined #openstack-meeting03:23
*** paragan has joined #openstack-meeting03:23
*** haomai___ has quit IRC03:24
*** haomai___ has joined #openstack-meeting03:25
*** tomoe_ has quit IRC03:25
*** tomoe_ has joined #openstack-meeting03:25
*** yamamot__ has joined #openstack-meeting03:26
*** AlexF_ has joined #openstack-meeting03:27
*** yamamoto has quit IRC03:29
*** sdake_ has joined #openstack-meeting03:30
*** Poornima has quit IRC03:31
*** nati_ueno has quit IRC03:31
*** MaxV has joined #openstack-meeting03:33
*** MaxV has quit IRC03:38
*** rwsu has quit IRC03:38
*** SumitNaiksatam has joined #openstack-meeting03:38
*** crc32 has quit IRC03:41
*** mattgriffin has joined #openstack-meeting03:41
*** otter768 has quit IRC03:45
*** mchalla has joined #openstack-meeting03:46
*** mattgriffin has quit IRC03:47
*** yingjun has quit IRC03:47
*** yingjun has joined #openstack-meeting03:47
*** sdake_ has quit IRC03:49
*** banix has quit IRC03:50
*** mchalla has quit IRC03:50
*** chandankumar has joined #openstack-meeting03:55
*** yingjun has quit IRC03:55
*** Murali__ has joined #openstack-meeting03:57
*** rfolco has quit IRC03:58
*** Poornima has joined #openstack-meeting03:58
*** Murali_ has quit IRC03:59
*** noslzzp has quit IRC03:59
*** eghobo has joined #openstack-meeting04:03
*** david-lyle has quit IRC04:08
*** david-lyle has joined #openstack-meeting04:08
*** garyh has quit IRC04:09
*** david-lyle has quit IRC04:13
*** HenryG is now known as HenryG_afk04:14
*** carl_baldwin has joined #openstack-meeting04:17
*** marun has quit IRC04:17
*** ngoswami has joined #openstack-meeting04:17
*** chandankumar has quit IRC04:20
*** nshaikh has joined #openstack-meeting04:22
*** amalagon has joined #openstack-meeting04:23
*** nosnos has joined #openstack-meeting04:25
*** Murali__ has quit IRC04:26
*** nati_ueno has joined #openstack-meeting04:27
*** shankar has joined #openstack-meeting04:29
*** eghobo has quit IRC04:29
*** AlexF_ has quit IRC04:30
*** sbalukoff has joined #openstack-meeting04:30
*** nexusz99 has joined #openstack-meeting04:31
*** fnaval has quit IRC04:31
*** nati_ueno has quit IRC04:32
*** neelashah1 has quit IRC04:32
*** adahms_ has quit IRC04:33
*** MaxV has joined #openstack-meeting04:34
*** aloga has quit IRC04:34
*** eghobo has joined #openstack-meeting04:35
*** rajeshr has joined #openstack-meeting04:37
*** MarkAtwood has joined #openstack-meeting04:38
*** MaxV has quit IRC04:39
*** garyh has joined #openstack-meeting04:40
*** aloga has joined #openstack-meeting04:42
*** adiantum has joined #openstack-meeting04:42
*** trinaths has joined #openstack-meeting04:43
*** shankar has quit IRC04:46
*** mchalla has joined #openstack-meeting04:47
*** eghobo has quit IRC04:47
*** eghobo has joined #openstack-meeting04:47
*** shankar has joined #openstack-meeting04:48
*** adahms_ has joined #openstack-meeting04:49
*** nshaikh has quit IRC04:50
*** mchalla has quit IRC04:51
*** hichihara has joined #openstack-meeting04:56
*** ArxCruz has joined #openstack-meeting04:56
*** carlp has joined #openstack-meeting04:57
*** vishwanathj has joined #openstack-meeting04:59
yamahatahi05:00
vishwanathjhello05:00
yamahata#startmeeting servicevm-device-manager05:01
openstackMeeting started Tue Aug 12 05:01:24 2014 UTC and is due to finish in 60 minutes.  The chair is yamahata. Information about MeetBot at http://wiki.debian.org/MeetBot.05:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:01
*** openstack changes topic to " (Meeting topic: servicevm-device-manager)"05:01
openstackThe meeting name has been set to 'servicevm_device_manager'05:01
yamahataDo we have bob?05:01
yamahatagive him a minute05:01
*** kopparam has joined #openstack-meeting05:02
*** natarajk has joined #openstack-meeting05:02
*** ildikov has quit IRC05:03
yamahataHmm, Bob isn't here. Okay let's get started05:03
yamahata#topic Announcement05:03
*** openstack changes topic to "Announcement (Meeting topic: servicevm-device-manager)"05:03
yamahata#info l3_db refactoring patch was merged05:03
yamahata#link https://review.openstack.org/#/c/108728/ l3_db refactoring05:04
natarajkyamahata: good to know05:04
yamahata#info adding auto token to context is still under review.05:04
yamahataThe feedback is good. I expect the merge soon05:04
*** slong_ has joined #openstack-meeting05:05
yamahata#link https://review.openstack.org/#/c/111756/ adding auth token to context05:05
*** slong_ has quit IRC05:05
*** slong_ has joined #openstack-meeting05:05
yamahataMy progress is not much this week. I implemented a bit. The next mile stone is to implement guest agent for l3 and create guest image05:05
*** adahms has joined #openstack-meeting05:06
*** rajeshr has quit IRC05:06
yamahatathat's it from me05:06
*** slong_ has quit IRC05:06
yamahataanything else to announce?05:06
*** rajeshr has joined #openstack-meeting05:06
*** slong_ has joined #openstack-meeting05:06
*** bcrochet has quit IRC05:06
*** nexusz99 has quit IRC05:06
*** rajeshr has quit IRC05:06
*** slong_ has quit IRC05:06
*** rharwood has quit IRC05:07
*** slong_ has joined #openstack-meeting05:07
yamahata#topic Open Discussion05:07
*** openstack changes topic to "Open Discussion (Meeting topic: servicevm-device-manager)"05:07
yamahataanything to discuss?05:07
*** Longgeek has joined #openstack-meeting05:07
*** slong has quit IRC05:08
*** ianw has quit IRC05:08
yamahataNow I have feeling that vyatta implementation can be ported as driver.05:08
*** ianw has joined #openstack-meeting05:08
*** adahms_ has quit IRC05:08
*** adahms_ has joined #openstack-meeting05:08
yamahataBut I have still much to accomodate csr1kv case because it has many features.05:08
*** bcrochet has joined #openstack-meeting05:08
yamahataplugging driver abstraction is the first thing.05:08
natarajkyamahata: i briefly took a look at the implementation last week05:09
yamahataOh cool.05:09
natarajkyamahata: Looks like you have pre, post methods now05:09
natarajklike ML205:09
yamahatanatarajk: yes.05:09
*** shashankhegde has joined #openstack-meeting05:09
*** rharwood has joined #openstack-meeting05:09
natarajkyamahata: Will look into it in detail this week05:09
yamahatanatarajk: at the moment it's still experimental.05:10
*** adahms has quit IRC05:10
yamahatanatarajk: thanks. It is still subject to change.05:10
natarajkyamahata: Is pre method for db change and post method for device config ?05:10
yamahataThe issues is, such design can accomodate csr1kv case.05:10
*** enikanorov has quit IRC05:10
yamahatanatarajk: basically yes.05:11
*** enikanorov has joined #openstack-meeting05:11
yamahataI think vyatta case, just post method will be implemented05:11
natarajkyamahata: Ok.05:11
yamahataI suppose for vyatta, the next issue is how to implement dnrm feature in tacker server somehow.05:12
*** ngoswami has quit IRC05:12
yamahatanatarajk: It's my understanding. correct?05:12
*** asettle has quit IRC05:12
*** adiantum has quit IRC05:12
natarajkyamahata: we can introduce a resource manager05:13
*** asettle has joined #openstack-meeting05:13
yamahatanatarajk: yes05:13
*** carl_baldwin has quit IRC05:13
*** jaypipes has joined #openstack-meeting05:14
natarajkyamahata: i am planning to spend more time this week. Will have some comments for the next week meeting05:15
yamahatanatarajk: great.05:15
*** ramishra has joined #openstack-meeting05:15
yamahatanatarajk: do you have any plan to update vyatta plugin patch? I'm willing to review it.05:15
yamahataI mean https://review.openstack.org/#/c/102336/05:15
*** chandankumar has joined #openstack-meeting05:16
natarajkyamahata: Yes, in the next couple of days. Our CI is almost ready05:16
yamahatacool05:16
yamahataanything else to discuss?05:16
*** chandankumar has quit IRC05:17
natarajknothing from me05:17
*** chandankumar has joined #openstack-meeting05:17
*** ramishra has quit IRC05:17
yamahataseem nothing left05:17
*** ramishra has joined #openstack-meeting05:17
yamahatatodays meeting is short.05:17
*** shankar has quit IRC05:17
yamahatathank you. see you next week05:17
natarajkbye05:18
yamahata#endmeeting05:18
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:18
openstackMeeting ended Tue Aug 12 05:18:16 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:18
*** vishwanathj has quit IRC05:18
openstackMinutes:        http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-08-12-05.01.html05:18
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-08-12-05.01.txt05:18
openstackLog:            http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-08-12-05.01.log.html05:18
*** natarajk has left #openstack-meeting05:19
*** aleksandr_null has quit IRC05:20
*** aleksandr_null has joined #openstack-meeting05:21
*** s3wong has joined #openstack-meeting05:22
*** hichihara has quit IRC05:22
*** otherwiseguy has quit IRC05:22
*** otherwiseguy has joined #openstack-meeting05:23
*** amalagon_ has joined #openstack-meeting05:23
*** deepakcs has joined #openstack-meeting05:24
*** amalagon has quit IRC05:24
*** amalagon_ is now known as amalagon05:24
*** AlexF_ has joined #openstack-meeting05:25
*** nati_ueno has joined #openstack-meeting05:28
*** ramishra has quit IRC05:29
*** ramishra has joined #openstack-meeting05:30
*** eghobo has quit IRC05:31
*** eghobo has joined #openstack-meeting05:31
*** vivek-ebay has joined #openstack-meeting05:31
*** nati_ueno has quit IRC05:33
*** bdpayne has quit IRC05:33
*** ramishra has quit IRC05:34
*** vivek-eb_ has quit IRC05:34
*** MaxV has joined #openstack-meeting05:35
*** bdpayne has joined #openstack-meeting05:35
*** ramishra has joined #openstack-meeting05:35
*** vivek-ebay has quit IRC05:35
*** k4n0 has joined #openstack-meeting05:37
*** akuznetsov has quit IRC05:38
*** shankar has joined #openstack-meeting05:38
*** MaxV has quit IRC05:39
*** ianw has quit IRC05:42
*** slong_ has quit IRC05:42
*** adahms__ has joined #openstack-meeting05:42
*** ianw has joined #openstack-meeting05:42
*** ianw has quit IRC05:43
*** ianw has joined #openstack-meeting05:43
*** amalagon has quit IRC05:43
*** rharwood has quit IRC05:43
*** ianw has quit IRC05:43
*** ianw has joined #openstack-meeting05:44
*** ianw has joined #openstack-meeting05:44
*** bcrochet has quit IRC05:44
*** slong__ has joined #openstack-meeting05:44
*** jasondotstar has quit IRC05:45
*** ianw has quit IRC05:45
*** slong__ has quit IRC05:45
*** ianw has joined #openstack-meeting05:45
*** slong__ has joined #openstack-meeting05:45
*** adahms_ has quit IRC05:45
*** rharwood has joined #openstack-meeting05:45
*** adahms_ has joined #openstack-meeting05:45
*** slong__ has quit IRC05:45
*** ianw has quit IRC05:46
*** ianw has joined #openstack-meeting05:46
*** adahms_ has quit IRC05:46
*** slong__ has joined #openstack-meeting05:46
*** adahms_ has joined #openstack-meeting05:46
*** adahms__ has quit IRC05:46
*** jasondotstar has joined #openstack-meeting05:47
*** bcrochet has joined #openstack-meeting05:48
*** yingjun has joined #openstack-meeting05:48
*** ianw has quit IRC05:50
*** ianw has joined #openstack-meeting05:51
*** otherwiseguy has quit IRC05:53
*** ajo_ has quit IRC05:53
*** ajo__ has joined #openstack-meeting05:53
*** akuznetsov has joined #openstack-meeting05:54
*** JRobinson__ has quit IRC05:55
*** ildikov has joined #openstack-meeting05:56
*** kentwu_ has joined #openstack-meeting05:56
*** johnpur has joined #openstack-meeting05:57
*** bdpayne has quit IRC05:58
*** e0ne has joined #openstack-meeting05:58
*** eguz has joined #openstack-meeting05:59
*** e0ne has quit IRC06:00
*** s3wong has quit IRC06:00
*** slong has joined #openstack-meeting06:01
*** ianw has quit IRC06:01
*** adahms__ has joined #openstack-meeting06:01
*** slong__ has quit IRC06:01
*** tomoe_ has quit IRC06:01
*** kashyap has joined #openstack-meeting06:01
*** slong_ has joined #openstack-meeting06:01
*** reed has quit IRC06:01
*** tomoe_ has joined #openstack-meeting06:01
*** rharwood has quit IRC06:01
*** reed has joined #openstack-meeting06:02
*** e0ne has joined #openstack-meeting06:02
*** kashyap has left #openstack-meeting06:02
*** jasondotstar has quit IRC06:02
*** bdperkin has quit IRC06:02
*** bcrochet has quit IRC06:02
*** eghobo has quit IRC06:03
*** johnpur has quit IRC06:04
*** adahms_ has quit IRC06:04
*** gangil has joined #openstack-meeting06:05
*** slong has quit IRC06:05
*** eguz has quit IRC06:05
*** bcrochet has joined #openstack-meeting06:06
*** jasondotstar has joined #openstack-meeting06:06
*** bdperkin has joined #openstack-meeting06:07
*** rharwood has joined #openstack-meeting06:07
*** SumitNaiksatam has quit IRC06:07
*** evgenyf has joined #openstack-meeting06:07
*** shashankhegde has quit IRC06:08
*** SumitNaiksatam has joined #openstack-meeting06:08
*** jtomasek has joined #openstack-meeting06:09
*** nexusz99 has joined #openstack-meeting06:09
*** yamamoto has joined #openstack-meeting06:09
*** yamamo___ has joined #openstack-meeting06:10
*** kentwu_ has quit IRC06:10
*** _nadya_ has joined #openstack-meeting06:10
*** kentwu_ has joined #openstack-meeting06:11
*** e0ne has quit IRC06:11
*** yamamot__ has quit IRC06:12
*** _nadya_ has quit IRC06:14
*** yamamoto has quit IRC06:14
*** AlexF_ has quit IRC06:14
*** trinaths has left #openstack-meeting06:14
*** ArxCruz has quit IRC06:15
*** AlexF_ has joined #openstack-meeting06:15
*** _nadya_ has joined #openstack-meeting06:16
*** e0ne has joined #openstack-meeting06:16
*** oomichi has quit IRC06:16
*** jtomasek has quit IRC06:16
*** nati_ueno has joined #openstack-meeting06:17
*** e0ne has quit IRC06:17
*** slong_ has quit IRC06:18
*** Longgeek has quit IRC06:19
*** Longgeek has joined #openstack-meeting06:21
*** pradipta_away is now known as pradipta06:23
*** yanghe has quit IRC06:27
*** ildikov has quit IRC06:27
*** nexusz99 has quit IRC06:28
*** yamamo___ has quit IRC06:28
*** deepakcs has quit IRC06:29
*** yanghe has joined #openstack-meeting06:30
*** gangil has left #openstack-meeting06:31
*** akash has joined #openstack-meeting06:32
*** flaper87|afk is now known as flaper8706:33
*** stevemar has quit IRC06:34
*** e0ne has joined #openstack-meeting06:35
*** MaxV has joined #openstack-meeting06:35
*** nshaikh has joined #openstack-meeting06:36
*** akash has quit IRC06:37
*** e0ne has quit IRC06:40
*** ildikov has joined #openstack-meeting06:40
*** MaxV has quit IRC06:40
*** gangil has joined #openstack-meeting06:44
*** e0ne has joined #openstack-meeting06:44
*** gangil has quit IRC06:44
*** gangil has joined #openstack-meeting06:44
*** gangil has quit IRC06:45
*** gangil has joined #openstack-meeting06:45
*** e0ne has quit IRC06:46
*** nexusz99 has joined #openstack-meeting06:47
*** mchalla has joined #openstack-meeting06:48
*** denis_makogon_ has joined #openstack-meeting06:50
*** adahms__ has quit IRC06:50
*** e0ne has joined #openstack-meeting06:51
*** andreykurilin_ has joined #openstack-meeting06:51
*** AlexF_ has quit IRC06:51
*** mchalla has quit IRC06:52
*** kentwu_ has quit IRC06:56
*** e0ne has quit IRC06:56
*** yamamoto has joined #openstack-meeting06:58
*** MarkAtwood has quit IRC06:59
*** e0ne has joined #openstack-meeting07:00
*** ngoswami has joined #openstack-meeting07:00
*** ivar-lazzaro has quit IRC07:00
*** ivar-lazzaro has joined #openstack-meeting07:00
*** Mandell has quit IRC07:01
*** ivar-lazzaro has quit IRC07:02
*** ivar-lazzaro1 has joined #openstack-meeting07:02
*** ramishra has quit IRC07:02
*** ramishra has joined #openstack-meeting07:02
*** e0ne has quit IRC07:04
*** asettle has quit IRC07:05
*** _nadya_ has quit IRC07:06
*** rajeshr has joined #openstack-meeting07:06
*** ramishra has quit IRC07:07
*** e0ne has joined #openstack-meeting07:08
*** matrohon has joined #openstack-meeting07:08
*** yamamoto has quit IRC07:10
*** e0ne has quit IRC07:10
*** dbite has joined #openstack-meeting07:10
*** SridharG has joined #openstack-meeting07:12
*** Fdot has joined #openstack-meeting07:12
*** e0ne has joined #openstack-meeting07:14
*** e0ne has quit IRC07:16
*** e0ne has joined #openstack-meeting07:19
*** jcoufal has joined #openstack-meeting07:20
*** jgallard has joined #openstack-meeting07:20
*** nshaikh has quit IRC07:20
*** e0ne has quit IRC07:22
*** jgallard has quit IRC07:23
*** jgallard has joined #openstack-meeting07:23
*** MaxV has joined #openstack-meeting07:26
*** e0ne has joined #openstack-meeting07:26
*** ramishra has joined #openstack-meeting07:27
*** sballe has joined #openstack-meeting07:27
*** salv-orlando has quit IRC07:27
*** yamamoto has joined #openstack-meeting07:28
*** e0ne has quit IRC07:29
*** yamamoto has quit IRC07:31
*** afazekas has joined #openstack-meeting07:31
*** e0ne has joined #openstack-meeting07:34
*** deepakcs has joined #openstack-meeting07:34
*** _nadya_ has joined #openstack-meeting07:35
*** e0ne has quit IRC07:36
*** andreykurilin_ has quit IRC07:36
*** phil_ has joined #openstack-meeting07:38
*** rudrarugge has quit IRC07:40
*** e0ne has joined #openstack-meeting07:40
*** e0ne has quit IRC07:42
*** e0ne has joined #openstack-meeting07:46
*** jlanoux has joined #openstack-meeting07:46
*** e0ne has quit IRC07:48
*** mchalla has joined #openstack-meeting07:49
*** AlexF_ has joined #openstack-meeting07:49
*** mrda is now known as mrda-away07:49
*** denis_makogon_ has quit IRC07:49
*** e0ne has joined #openstack-meeting07:52
*** gangil has quit IRC07:53
*** gangil has joined #openstack-meeting07:53
*** mchalla has quit IRC07:54
*** s0nea has quit IRC07:54
*** Krast has joined #openstack-meeting07:54
*** shankar has quit IRC07:56
*** gangil has quit IRC07:58
*** e0ne has quit IRC07:58
*** gangil has joined #openstack-meeting07:58
*** gangil has joined #openstack-meeting07:58
*** ramishra has quit IRC07:58
*** yingjun has quit IRC07:58
*** yingjun has joined #openstack-meeting07:59
*** ramishra has joined #openstack-meeting07:59
*** fifieldt__ is now known as fifieldt07:59
*** Krast has quit IRC08:02
*** yamamoto has joined #openstack-meeting08:02
*** e0ne has joined #openstack-meeting08:02
*** yanghe has quit IRC08:03
*** ramishra has quit IRC08:03
*** decko has joined #openstack-meeting08:04
*** AlexF_ has quit IRC08:04
*** dosaboy_ has joined #openstack-meeting08:05
*** e0ne has quit IRC08:06
*** yamamoto has quit IRC08:06
*** Krast has joined #openstack-meeting08:06
*** jpich has joined #openstack-meeting08:07
*** shankar has joined #openstack-meeting08:09
*** e0ne has joined #openstack-meeting08:10
*** e0ne has quit IRC08:13
*** jlibosva has joined #openstack-meeting08:14
*** derekh has joined #openstack-meeting08:15
*** nshaikh has joined #openstack-meeting08:16
*** e0ne has joined #openstack-meeting08:17
*** yaguang has quit IRC08:19
*** yaguang has joined #openstack-meeting08:19
*** ndipanov_gone is now known as ndipanov08:20
*** andreaf_ has joined #openstack-meeting08:23
*** andreaf has quit IRC08:23
*** zhhuabj has quit IRC08:24
*** zhhuabj has joined #openstack-meeting08:25
*** yanghe has joined #openstack-meeting08:25
*** anand_ts has joined #openstack-meeting08:26
*** doron_afk has joined #openstack-meeting08:27
*** AlexF_ has joined #openstack-meeting08:27
*** yamamoto has joined #openstack-meeting08:28
*** ramishra has joined #openstack-meeting08:29
*** yanghe has quit IRC08:29
*** yamamoto has quit IRC08:33
*** nati_ueno has quit IRC08:33
*** ramishra has quit IRC08:34
*** nati_ueno has joined #openstack-meeting08:34
*** e0ne has quit IRC08:35
*** dosaboy_ has quit IRC08:36
*** drankis has quit IRC08:37
*** andreaf has joined #openstack-meeting08:37
*** tomoe_ has quit IRC08:38
*** tomoe_ has joined #openstack-meeting08:38
*** e0ne has joined #openstack-meeting08:39
*** Krast has quit IRC08:40
*** andreaf_ has quit IRC08:40
*** Krast has joined #openstack-meeting08:40
*** vjay has quit IRC08:40
*** AlexF_ has quit IRC08:41
*** jpich has left #openstack-meeting08:41
*** andreaf_ has joined #openstack-meeting08:42
*** andreaf has quit IRC08:45
*** dosaboy_ has joined #openstack-meeting08:46
*** dosaboy_ is now known as dosaboy-alt08:46
*** dosaboy-alt has quit IRC08:47
*** pradipta is now known as pradipta_away08:51
*** e0ne has quit IRC08:52
*** joa has left #openstack-meeting08:54
*** AlexF_ has joined #openstack-meeting08:55
*** zhhuabj has quit IRC08:56
*** yingjun has quit IRC08:56
*** zhhuabj has joined #openstack-meeting08:56
*** yingjun has joined #openstack-meeting08:56
*** e0ne has joined #openstack-meeting08:57
*** e0ne has quit IRC08:59
*** yingjun has quit IRC09:01
*** decko has quit IRC09:03
*** gangil has quit IRC09:03
*** e0ne has joined #openstack-meeting09:03
*** Hayim has quit IRC09:06
*** AlexF_ has quit IRC09:07
*** Hayim has joined #openstack-meeting09:07
*** e0ne has quit IRC09:07
*** AlexF_ has joined #openstack-meeting09:08
*** jtomasek has joined #openstack-meeting09:12
*** nati_ueno has quit IRC09:12
*** e0ne has joined #openstack-meeting09:13
*** e0ne has quit IRC09:15
*** yingjun has joined #openstack-meeting09:15
*** JRobinson__ has joined #openstack-meeting09:17
*** e0ne has joined #openstack-meeting09:19
*** dosaboy has quit IRC09:20
*** dosaboy has joined #openstack-meeting09:23
*** e0ne has quit IRC09:24
*** aranjan has quit IRC09:24
*** e0ne has joined #openstack-meeting09:26
*** evgenyf has quit IRC09:27
*** ramishra has joined #openstack-meeting09:28
*** yamamoto has joined #openstack-meeting09:29
*** ajo_ has joined #openstack-meeting09:29
*** e0ne has quit IRC09:30
*** AlexF_ has quit IRC09:32
*** samcdona has quit IRC09:32
*** ajo__ has quit IRC09:32
*** evgenyf has joined #openstack-meeting09:32
*** yamamoto has quit IRC09:34
*** e0ne has joined #openstack-meeting09:34
*** yingjun has quit IRC09:36
*** AlexF_ has joined #openstack-meeting09:36
*** pelix has joined #openstack-meeting09:38
*** e0ne has quit IRC09:39
*** andreaf has joined #openstack-meeting09:40
*** andreaf has quit IRC09:40
*** andreaf has joined #openstack-meeting09:41
*** andreaf_ has quit IRC09:42
*** e0ne has joined #openstack-meeting09:44
*** andreaf has quit IRC09:46
*** erw has quit IRC09:46
*** zhiyan has quit IRC09:47
*** simonmcc_ has quit IRC09:48
*** willroberts has quit IRC09:49
*** julienvey has joined #openstack-meeting09:49
*** ctracey has quit IRC09:49
*** CaptTofu_ has quit IRC09:49
*** kaydo has quit IRC09:50
*** skath has quit IRC09:50
*** sweston has quit IRC09:50
*** mchalla has joined #openstack-meeting09:50
*** aweeks has quit IRC09:51
*** marcusvrn has quit IRC09:51
*** jraim has quit IRC09:51
*** Michalik has quit IRC09:51
*** nexusz99 has quit IRC09:52
*** erw has joined #openstack-meeting09:52
*** novas0x2a|laptop has quit IRC09:52
*** zhiyan has joined #openstack-meeting09:52
*** willroberts has joined #openstack-meeting09:52
*** simonmcc_ has joined #openstack-meeting09:53
*** ctracey has joined #openstack-meeting09:53
*** erlon has quit IRC09:53
*** sweston has joined #openstack-meeting09:54
*** kaydo_ has joined #openstack-meeting09:54
*** skath has joined #openstack-meeting09:54
*** jraim has joined #openstack-meeting09:54
*** marcusvrn has joined #openstack-meeting09:54
*** aweeks has joined #openstack-meeting09:55
*** mchalla has quit IRC09:55
*** flaviof_zzz is now known as flaviof09:55
*** goodes has quit IRC09:57
*** zhiyan has quit IRC09:57
*** erw has quit IRC09:57
*** kaydo_ has quit IRC09:58
*** Michalik has joined #openstack-meeting09:59
*** goodes has joined #openstack-meeting09:59
*** AlexF_ has quit IRC09:59
*** erlon has joined #openstack-meeting09:59
*** zhiyan has joined #openstack-meeting09:59
*** MaxV has quit IRC09:59
*** kaydo_ has joined #openstack-meeting10:00
*** MaxV has joined #openstack-meeting10:00
*** CaptTofu_ has joined #openstack-meeting10:00
*** epico has quit IRC10:00
*** erw has joined #openstack-meeting10:01
*** andreaf has joined #openstack-meeting10:04
*** nexusz99 has joined #openstack-meeting10:04
*** MaxV has quit IRC10:04
*** e0ne has quit IRC10:06
*** nati_ueno has joined #openstack-meeting10:09
*** yaguang has quit IRC10:10
*** aranjan has joined #openstack-meeting10:11
*** alexpilotti has joined #openstack-meeting10:12
*** jgallard has quit IRC10:12
*** nati_ueno has quit IRC10:14
*** AlexF_ has joined #openstack-meeting10:21
*** aranjan has quit IRC10:24
*** yaguang has joined #openstack-meeting10:25
*** harshada has joined #openstack-meeting10:25
*** ajo__ has joined #openstack-meeting10:26
*** harshada has left #openstack-meeting10:27
*** ajo_ has quit IRC10:28
*** yamamoto has joined #openstack-meeting10:29
*** ajo_ has joined #openstack-meeting10:30
*** ajo__ has quit IRC10:30
*** jlanoux has quit IRC10:30
*** AlexF_ has quit IRC10:31
*** paragan has quit IRC10:31
*** yamamoto has quit IRC10:33
*** AlexF_ has joined #openstack-meeting10:34
*** andreaf_ has joined #openstack-meeting10:35
*** JRobinson__ has quit IRC10:36
*** JRobinson__ has joined #openstack-meeting10:36
*** andreaf has quit IRC10:37
*** rfolco has joined #openstack-meeting10:37
*** jhenner has joined #openstack-meeting10:38
*** doron_afk has quit IRC10:40
*** doron has joined #openstack-meeting10:43
*** andreaf_ has quit IRC10:43
*** sballe has quit IRC10:46
*** Krast has quit IRC10:50
*** aranjan has joined #openstack-meeting10:51
*** aranjan has quit IRC10:53
*** kopparam has quit IRC10:53
*** aranjan has joined #openstack-meeting10:53
*** aranjan has quit IRC10:54
*** aranjan has joined #openstack-meeting10:55
*** ramishra has quit IRC10:56
*** ramishra has joined #openstack-meeting10:57
*** reed has quit IRC10:58
*** aranjan has quit IRC11:00
*** andreaf has joined #openstack-meeting11:01
*** Hayim has quit IRC11:04
*** yingjun has joined #openstack-meeting11:04
*** andreaf_ has joined #openstack-meeting11:04
*** vijendar has joined #openstack-meeting11:06
*** andreaf has quit IRC11:08
*** doron is now known as doron_afk11:08
*** yamamoto has joined #openstack-meeting11:10
*** Longgeek has quit IRC11:10
*** Longgeek has joined #openstack-meeting11:10
*** nati_ueno has joined #openstack-meeting11:11
*** yamahata has quit IRC11:11
*** Longgeek has quit IRC11:14
*** nati_ueno has quit IRC11:15
*** yaguang has quit IRC11:15
*** jasondotstar has quit IRC11:18
*** ArxCruz has joined #openstack-meeting11:20
*** hashar has joined #openstack-meeting11:20
*** JRobinson__ has quit IRC11:23
*** flaviof is now known as flaviof_zzz11:23
*** kopparam has joined #openstack-meeting11:24
*** drankis has joined #openstack-meeting11:24
*** kopparam has quit IRC11:28
*** ramishra has quit IRC11:29
*** ramishra has joined #openstack-meeting11:30
*** Poornima has quit IRC11:31
*** willroberts has quit IRC11:33
*** Longgeek has joined #openstack-meeting11:34
*** ramishra has quit IRC11:34
*** willroberts has joined #openstack-meeting11:35
*** jab is now known as bradjones11:36
*** weshay has joined #openstack-meeting11:36
*** vkmc has joined #openstack-meeting11:37
*** vkmc has quit IRC11:37
*** vkmc has joined #openstack-meeting11:37
*** baoli has joined #openstack-meeting11:38
*** yingjun has quit IRC11:38
*** yingjun has joined #openstack-meeting11:38
*** AlexF_ has quit IRC11:40
*** jmh has joined #openstack-meeting11:41
*** yingjun has quit IRC11:43
*** andreaf_ has quit IRC11:45
*** andreaf_ has joined #openstack-meeting11:45
*** ramishra has joined #openstack-meeting11:48
*** DrBacchus has joined #openstack-meeting11:48
*** aswadr has joined #openstack-meeting11:50
*** BrianB_ has quit IRC11:51
*** mchalla has joined #openstack-meeting11:52
*** aranjan has joined #openstack-meeting11:53
*** mchalla has quit IRC11:56
*** aranjan has quit IRC11:57
*** s0nea has joined #openstack-meeting11:59
*** AlexF_ has joined #openstack-meeting12:04
*** nexusz99 has quit IRC12:04
*** IanGovett has joined #openstack-meeting12:05
*** jgallard has joined #openstack-meeting12:06
*** ominakov has quit IRC12:07
*** prad has joined #openstack-meeting12:07
*** akuznetsov has quit IRC12:09
*** dprince has joined #openstack-meeting12:10
*** salv-orlando has joined #openstack-meeting12:10
*** cjellick has joined #openstack-meeting12:15
*** adalbas has joined #openstack-meeting12:16
*** banix has joined #openstack-meeting12:17
*** AlexF_ has quit IRC12:17
*** cjellick has quit IRC12:18
*** cjellick has joined #openstack-meeting12:19
*** akuznetsov has joined #openstack-meeting12:22
*** paragan has joined #openstack-meeting12:23
*** paragan has quit IRC12:23
*** paragan has joined #openstack-meeting12:23
*** dkranz has joined #openstack-meeting12:24
*** dbite has quit IRC12:24
*** ominakov has joined #openstack-meeting12:24
*** kopparam has joined #openstack-meeting12:24
*** dbite has joined #openstack-meeting12:25
*** SridharG has quit IRC12:25
*** baoli has quit IRC12:26
*** aysyd has joined #openstack-meeting12:28
*** deepakcs has quit IRC12:30
*** yamamoto has quit IRC12:31
*** noslzzp has joined #openstack-meeting12:34
*** MaxV has joined #openstack-meeting12:34
*** neelashah has joined #openstack-meeting12:35
*** ramishra has quit IRC12:35
*** ramishra_ has joined #openstack-meeting12:36
*** kopparam has quit IRC12:36
*** rajeshr has quit IRC12:38
*** ominakov has quit IRC12:46
*** AlexF_ has joined #openstack-meeting12:48
*** mchalla has joined #openstack-meeting12:53
*** vijendar has quit IRC12:53
*** k4n0 has quit IRC12:53
*** aranjan has joined #openstack-meeting12:53
*** vhoward has left #openstack-meeting12:53
*** banix has quit IRC12:54
*** mchalla has quit IRC12:57
*** aranjan has quit IRC12:58
*** nati_ueno has joined #openstack-meeting12:58
*** AlexF_ has quit IRC13:00
*** DrBacchus has quit IRC13:00
*** jcoufal has quit IRC13:00
*** e0ne has joined #openstack-meeting13:01
*** HenryG_afk is now known as HenryG13:02
*** gentlesaurus is now known as annegentle13:02
*** andreykurilin has left #openstack-meeting13:03
*** jcoufal has joined #openstack-meeting13:03
*** julim has joined #openstack-meeting13:04
*** DrBacchus has joined #openstack-meeting13:05
*** ominakov has joined #openstack-meeting13:06
*** julim has quit IRC13:06
*** DrBacchus is now known as rbowen13:07
*** bknudson has quit IRC13:09
*** AlexF_ has joined #openstack-meeting13:10
*** flaper87 is now known as flaper87|afk13:10
*** SridharG has joined #openstack-meeting13:10
*** dkranz has quit IRC13:11
*** nosnos has quit IRC13:13
*** shashankhegde has joined #openstack-meeting13:13
*** shankar has quit IRC13:14
*** jgallard has quit IRC13:17
*** jtomasek_ has joined #openstack-meeting13:19
*** noslzzp has quit IRC13:19
*** ivar-lazzaro1 has quit IRC13:19
*** mrmartin has joined #openstack-meeting13:20
*** jtomasek has quit IRC13:21
*** changbl has quit IRC13:21
*** AlexF_ has quit IRC13:21
*** nati_ueno has quit IRC13:22
*** nexusz99 has joined #openstack-meeting13:23
*** julim has joined #openstack-meeting13:24
*** MarkAtwood has joined #openstack-meeting13:25
*** blogan has quit IRC13:27
*** ptoohill has quit IRC13:28
*** vjay has joined #openstack-meeting13:28
*** evgenyf has quit IRC13:29
*** balajiiyer has joined #openstack-meeting13:30
*** ivasev has joined #openstack-meeting13:30
*** jgallard has joined #openstack-meeting13:30
*** bknudson has joined #openstack-meeting13:30
*** AlexF_ has joined #openstack-meeting13:31
*** yamamoto has joined #openstack-meeting13:32
*** baoli has joined #openstack-meeting13:32
*** jasondotstar has joined #openstack-meeting13:32
*** esker has joined #openstack-meeting13:32
*** ayoung has joined #openstack-meeting13:32
*** ptoohill has joined #openstack-meeting13:33
*** blogan has joined #openstack-meeting13:33
*** yamamoto has quit IRC13:36
*** jecarey has joined #openstack-meeting13:36
*** dkranz has joined #openstack-meeting13:37
*** ptoohill has quit IRC13:39
*** blogan has quit IRC13:40
*** noslzzp has joined #openstack-meeting13:40
*** reaper has joined #openstack-meeting13:40
*** reaper has quit IRC13:41
*** esker has quit IRC13:42
*** ivar-lazzaro has joined #openstack-meeting13:43
*** MarkAtwood has quit IRC13:43
*** stevemar has joined #openstack-meeting13:44
*** ptoohill has joined #openstack-meeting13:45
*** blogan has joined #openstack-meeting13:46
*** balajiiyer has left #openstack-meeting13:46
*** trey_h has joined #openstack-meeting13:47
*** whenry has joined #openstack-meeting13:47
*** e0ne has quit IRC13:48
*** jprovazn has joined #openstack-meeting13:51
*** marun has joined #openstack-meeting13:51
*** absubram__ has joined #openstack-meeting13:52
*** flaviof_zzz is now known as flaviof13:53
*** aranjan has joined #openstack-meeting13:53
*** mchalla has joined #openstack-meeting13:53
*** evgenyf has joined #openstack-meeting13:53
*** ramishra_ has quit IRC13:54
*** ramishra has joined #openstack-meeting13:54
*** BrianB_ has joined #openstack-meeting13:55
*** FJB has joined #openstack-meeting13:55
*** pdmars has joined #openstack-meeting13:55
*** pdmars has quit IRC13:55
*** yingjun has joined #openstack-meeting13:55
*** pdmars has joined #openstack-meeting13:56
*** aveiga has joined #openstack-meeting13:56
*** aranjan has quit IRC13:57
*** julim has quit IRC13:58
*** mchalla has quit IRC13:58
*** doron_afk is now known as doron13:58
*** xuhanp has joined #openstack-meeting13:59
*** AlanClark has joined #openstack-meeting14:00
*** julim has joined #openstack-meeting14:01
*** thangp has joined #openstack-meeting14:02
sc68calhello all14:02
sc68cal#startmeeting neutron_ipv614:02
openstackMeeting started Tue Aug 12 14:02:35 2014 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: neutron_ipv6)"14:02
openstackThe meeting name has been set to 'neutron_ipv6'14:02
*** ramishra has quit IRC14:02
xuhanphello14:02
absubram__hi14:02
HenryGHi14:03
aveigao/14:03
*** vijendar has joined #openstack-meeting14:03
sc68calAgenda is pretty light today, I think most of the time can be for just coordinating code review14:03
*** doron is now known as doron_afk14:04
*** joesavak has joined #openstack-meeting14:04
*** vijendar has quit IRC14:04
*** vijendar has joined #openstack-meeting14:04
*** BrianB_ has quit IRC14:05
*** Riddhi has joined #openstack-meeting14:05
*** afazekas has quit IRC14:05
*** dkranz has quit IRC14:05
*** dane_leblanc has joined #openstack-meeting14:06
*** BrianB_ has joined #openstack-meeting14:06
*** samcdona has joined #openstack-meeting14:06
*** banix has joined #openstack-meeting14:06
sc68calxuhanp: how goes the stateful/stateless work?14:06
xuhanpsc68cal, I got some interesting comments from baoli14:06
baoliHi14:07
*** kevinconway has joined #openstack-meeting14:07
xuhanpone is that the extra options of dhcpv6 and dhcp are different, so I am thinking about how to let the code make sense.14:07
xuhanpbaoli, do you have any suggestions in mind?14:08
*** hashar has quit IRC14:08
baolixuhanp, I was thinking that there might be a couple of ways of dealing with it.14:08
*** vijendar has quit IRC14:08
*** flaper87|afk is now known as flaper8714:09
baolixuhanp: when user supplies the extra_dhcp_opts in the port API, is there any verification on if the option is valid?14:09
*** mtanino has joined #openstack-meeting14:09
baoliI mean existing verification14:09
xuhanpI don't see any verification currently.14:09
*** armax has joined #openstack-meeting14:10
*** jasondotstar has quit IRC14:10
xuhanpright now it's just name value pairs14:11
baoliIt used to be ok since it only deals with ipv4. With ipv6 added, would it make sense for the user to indicate if an option is meant for v4 or v6?14:11
xuhanpyeah. that will requires API change14:12
baoliIf you check the dnsmasq definition for the option name strings, same name may be used for both v4 and v6 if the option applies to both.14:13
baoliso I think that it will take some thoughts to get it right from user's point of view and implementation point of view14:14
xuhanpyep. but if the option involves with v4 or v6 address we should separate them.14:14
xuhanpmaybe we can think about it and discuss on mail list.14:14
*** jasondotstar has joined #openstack-meeting14:15
*** otherwiseguy has joined #openstack-meeting14:15
*** FJB has quit IRC14:15
*** joesavak has quit IRC14:16
baolixuhanp: sure14:16
*** hrybacki has joined #openstack-meeting14:16
xuhanpI think the difficult case here is when the port has both IPv4 and v6 address. otherwise, we can just simply use option or option6 for extra_dhcp_opts14:17
*** Murali_ has joined #openstack-meeting14:18
baolixuhanp, that's right. But subnet can alos be added after the port is created.14:18
xuhanpyep. that makes it even more complicated.14:18
*** FJB has joined #openstack-meeting14:19
*** FJB has quit IRC14:19
xuhanpmaybe we can change the format of extra_dhcp_opts name to option:XXX or option6:XXX14:19
baolimaybe we can use the name string like v[4|6]:<option-name>14:19
baolixuhanp, looks like we are on the same page14:19
*** anand_ts has quit IRC14:19
*** FJB has joined #openstack-meeting14:19
xuhanpbut we will need to make sure it's backward compatible.14:20
*** afazekas has joined #openstack-meeting14:20
baoliv[4|6]: is optional, and by default it's v4.14:20
*** dkranz has joined #openstack-meeting14:21
xuhanpsounds like a plan14:21
xuhanpI will send a email to list14:21
baoliin addition, verification may be needed to make sure that the user provides correct options14:21
*** e0ne has joined #openstack-meeting14:22
xuhanpyep14:22
baolicool14:22
*** simon-AS559 has joined #openstack-meeting14:22
baolidid you check the file dhcp_common.c? which should help a lot14:23
xuhanpnot yet. will do14:24
*** nelsnelson has quit IRC14:24
*** vijendar has joined #openstack-meeting14:25
*** jgallard has quit IRC14:25
*** vijendar has quit IRC14:25
*** vijendar has joined #openstack-meeting14:26
*** yingjun has quit IRC14:26
*** yingjun has joined #openstack-meeting14:26
sc68calVery cool.14:26
*** Riddhi has quit IRC14:26
*** david-lyle has joined #openstack-meeting14:26
*** Riddhi has joined #openstack-meeting14:27
sc68calI think that J-3 is going to have a lot of stuff trying to land14:27
sc68calso if possible let's try and keep the review cycles short on some of this stuff so we can get cores on it asap14:28
xuhanpsc68cal, sounds good. Maybe the extra_dhcp_opts validations stuff baoli and I discussed today can go to a separate patch, so we can get the major part landed first.14:30
aveiga+114:30
*** nelsnelson has joined #openstack-meeting14:30
sc68calYeah it sounds like there are lots of gotchas in that14:30
aveigasplitting it up makes it less likely for other parts to miss because of nits on one bit14:30
*** ildikov has quit IRC14:30
*** tongli has joined #openstack-meeting14:30
HenryGYes, I can see it being viewed as a separate bug14:31
*** yingjun has quit IRC14:31
baolisounds good to me14:32
*** yamamoto has joined #openstack-meeting14:32
baoliin that case, I'll +1 on this current patch14:32
*** salv-orlando has quit IRC14:33
sc68calvery cool14:33
xuhanpI will add a TODO or FIXME at your comment place14:33
baolixuhanp, thanks14:33
*** ivar-lazzaro has quit IRC14:35
sc68calxuhanp: I'll also test the patch in the lab at some point just to allay my fears about the host file. Your code looks fine, I just get a little feaful when someone is in that area of the dnsmasq code :)14:35
pcarver_The mention of a separate patch brings up a question I have. How are people keeping track of everything that's in flight and what pieces are needed in order to get various parts of IPv6 working?14:35
sc68calpcarver_: the specs that get merged in neutron-specs is what I use to track14:36
pcarver_There's a list of code reviews on https://wiki.openstack.org/wiki/Neutron/IPv6 but all the links are broken. Is that info no longer used?14:36
aveigapcarver_: that wiki is way out of date14:37
sc68calpcarver_: it's probably out of date, but it looks like the updated gerrit system broke links too :(14:37
*** yamamoto has quit IRC14:37
sc68calwhen they did the upgrade to gerrit14:37
*** jprovazn has quit IRC14:38
pcarver_Would it make sense to either delete it or update it? Right now it's the top Google hit for "neutron ipv6"14:38
pcarver_I'd be happy to update it if I knew what to update it to14:39
*** eankutse has joined #openstack-meeting14:39
pcarver_Are the list of reviews still accurate if I just search in Gerrit for the correct links?14:39
pcarver_Or have some of them been obsoleted and new ones needed that aren't on that list?14:40
*** esheffield has joined #openstack-meeting14:40
sc68calMany of those reviews did get merged, so I think we can remove that section14:41
sc68calIdeally we should add some docs to docs.openstack.org and link from the wiki14:41
*** SridharG has quit IRC14:41
*** tsekiyama has joined #openstack-meeting14:44
*** markmcclain has joined #openstack-meeting14:44
dane_leblancMaybe we'll eventually need separate sections for J-release blueprints and upcoming K-release blueprints.14:45
*** vivek-ebay has joined #openstack-meeting14:46
*** funzo has quit IRC14:47
*** funzo has joined #openstack-meeting14:48
*** mspreitz has joined #openstack-meeting14:49
pcarver_I'll see what I can do about cleaning up the links on the wiki. My problem is that I still feel kind of fuzzy on where we are at a high level. i.e. what user meaningful functionality we expect in J vs K14:49
*** esker has joined #openstack-meeting14:49
*** tianst has joined #openstack-meeting14:49
sc68calJ release will support *all* configurations for the ipv6 modes14:49
sc68calmeaning radvd and dnsmasq will be configured properly for v614:50
*** gokrokve has joined #openstack-meeting14:50
*** n0ano has joined #openstack-meeting14:50
sc68calbasically the following specs14:50
sc68calhttp://specs.openstack.org/openstack/neutron-specs/specs/juno/ipv6-provider-nets-slaac.html14:50
sc68calhttp://specs.openstack.org/openstack/neutron-specs/specs/juno/ipv6-dnsmasq-dhcpv6-stateless-stateful.html14:50
sc68calhttp://specs.openstack.org/openstack/neutron-specs/specs/juno/ipv6-radvd-ra.html14:51
*** AlexF_ has quit IRC14:52
pcarver_ok, I'll take a crack at updating the wiki and see how it goes.14:52
*** aranjan has joined #openstack-meeting14:53
sc68calpcarver_: thanks14:54
*** jmontemayor has joined #openstack-meeting14:54
*** hemna has joined #openstack-meeting14:54
sc68calDo we have any other business? Otherwise I'll give everyone back a couple minutes14:56
dane_leblancI put some code up for review.14:57
dane_leblanchttps://review.openstack.org/#/c/11333914:57
*** AlexF_ has joined #openstack-meeting14:57
dane_leblancBlueprint is still in limbo, not -1 or -2'd, but no response for feature exception freeze14:57
*** carl_baldwin has joined #openstack-meeting14:58
*** IanGovett has quit IRC14:58
*** nati_ueno has joined #openstack-meeting14:58
sc68calHaving the code posted, I think that'll help get it merged early in K14:58
*** yeungp has joined #openstack-meeting14:58
*** markmcclain1 has joined #openstack-meeting15:00
sc68calok everyone, till next week!15:00
*** IanGovett has joined #openstack-meeting15:00
*** aveiga has left #openstack-meeting15:00
*** markmcclain has quit IRC15:01
sc68calDoing great work, keep it up!15:01
sc68cal#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:01
openstackMeeting ended Tue Aug 12 15:01:05 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-08-12-14.02.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-08-12-14.02.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-08-12-14.02.log.html15:01
n0ano#startmeeting gantt15:01
openstackMeeting started Tue Aug 12 15:01:21 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
bauzas\o15:01
n0anoanyone here to talk about the scheduler?15:01
*** jlibosva has quit IRC15:01
mspreitzo/15:01
*** dane_leblanc has quit IRC15:01
tiansto/15:01
* n0ano refuses to jinx things by saying we have a short agenda15:02
n0ano#topic forklift status15:02
*** openstack changes topic to "forklift status (Meeting topic: gantt)"15:02
bauzassome people are most probably on PTO this week15:02
*** Yathi has joined #openstack-meeting15:03
*** nati_ueno has quit IRC15:03
n0anobauzas, good point, it's Aug., why aren't you on vacation?15:03
*** simon-AS559 has quit IRC15:03
bauzasn0ano: baby exception15:03
n0ano:-)15:03
n0anoAnyway, couple of things on the forklift, client library15:03
bauzasand August is rainy here so was a good choice anyway...15:03
bauzassure thing15:03
bauzasso15:04
n0anobauzas, looks like you've been rebasing a lot, what are the odds this is the last patch set15:04
*** radez_g0n3 is now known as radez15:04
*** jkremer has joined #openstack-meeting15:04
bauzasabout sched-lib, was based on ERT patch which was merged15:04
bauzasJenkins is poorly handling conflicts15:04
bauzasand here we were having one15:04
bauzasbut the code is 99.99% identical, except an unittest which needed to mock the call to ERT15:05
n0anolooks like it's all +1 so, hopefully, it's good to go15:05
bauzasthink so15:05
bauzasso now we need reviewers :)15:06
n0anomy +1 is there :-)15:06
bauzasunless ERT is reverted back again (but will discuss about it later... :) )15:06
n0anoI believe we have all 3 patches for isolating the DB posted, my bad I intend to review them today15:06
bauzasn0ano: so about isolate-sched-db, the proposal is still needing a second +215:07
*** aranjan has quit IRC15:07
n0anoI wanted to ask, did you ping dipanov?15:07
bauzasthe real problem is that it sounds not sexy at all15:07
bauzasn0ano: indeed15:07
*** hemna has quit IRC15:07
bauzasn0ano: ndipanov is not core on specs15:07
bauzasn0ano: but he was sponsor15:08
n0anobut he sponsored the exception, that wan't enough?15:08
bauzasn0ano: so his main concern is about the use of ERT15:08
*** dkranz has quit IRC15:08
n0anowhat's the concern, ERT is merged so, technically, we should use it15:08
bauzashis concerns about ERT are in this thread15:08
*** afazekas has quit IRC15:08
*** toan_tran|2 has joined #openstack-meeting15:09
bauzashttp://lists.openstack.org/pipermail/openstack-dev/2014-August/042709.html ERT revert or not ?15:09
*** toan_tran|2 has quit IRC15:09
bauzasn0ano: ERT code is not merged for scheduler consumes15:09
bauzasconsumers...15:09
ndipanovbauzas, sponsoring at that point meant tha tI will review the code as a core reviewer15:09
*** toan-tran has joined #openstack-meeting15:10
ndipanovbut yeah - I'd prefer not to depend on the current implementation of the ERT15:10
bauzasndipanov: agreed, I was just mentioning why we discussed about you15:10
*** matiu has quit IRC15:10
ndipanovbut that's just like... my opinion maaan15:10
bauzasbecause most of the people probably don't know why we mentioned you :)15:10
*** doron_afk has quit IRC15:11
bauzasanyway, as I said, folks, please take time for reading this email and replying if willing15:11
*** colinmcnamara has joined #openstack-meeting15:11
n0anobut wouldn't reverting ERT cause lots of problems?15:12
bauzasndipanov: yeah, that's why we probably need to think about a plan B15:12
Yathiregarding ndipanov's concern, anything like ERT, will involve users feeding a lot of info while scheduling an instance..15:12
*** dbite has quit IRC15:12
*** banix has quit IRC15:12
*** AlanClark has quit IRC15:13
bauzasn0ano: my main concern is that the scheduler side of ERT is not pushed yet15:13
Yathiso that is more like a we have to make it simpler from a scheduler perspective I guess.. if I got the concern correctly15:13
bauzasYathi: the current problem is about how we ensure that compute nodes can safely deny a request if scheduler made a wrong decision15:13
ndipanovYathi, the concern is that we are basing a plugin system on a bad/broken internal API (RT and Claims) that we are de facto making public15:14
*** absubram__ has quit IRC15:14
ndipanovthe reason for badness is that there is no reasonable way to incorporate user supplied data into it at present15:14
bauzasndipanov: by public, you mean entrypoints ?15:14
ndipanovyes15:14
bauzasndipanov: agreed, but that sounds to me a plain RT problem, not ERT15:15
Yathiok15:15
ndipanovwe don't really have a polcy for stability of those15:15
ndipanovbut if we are going to be breaking them15:15
ndipanovI question the usefulness of the whole thing15:15
bauzasI'm more concerned about the timings and wrt ERT, if it's good or no to depend on a patch which could probably not land by Juno15:15
ndipanovthem = 3rd party plugins15:15
*** ramishra has joined #openstack-meeting15:15
*** hemna has joined #openstack-meeting15:16
*** jlanoux has joined #openstack-meeting15:16
bauzasndipanov: ok, then I see why you dislike ERT15:16
*** MarkAtwood has joined #openstack-meeting15:16
ndipanovon top of the whole blobs thing that I didn't mention in the email15:17
bauzasndipanov: I just think we need to identify what's needed for the host to make decisions15:17
bauzasndipanov: replies are made for adding stuff you forget :)15:17
YathiI agree the internal APIs might need fixing.. but should that block this feature for now?15:17
bauzas(says the one who forgot to add 2 links...)15:17
ndipanovYathi, which feature?15:18
ndipanovERT?15:18
Yathindipanov: ERT, Gantt related patches15:18
ndipanovwell15:18
ndipanovI am not sure15:18
*** tbarron has joined #openstack-meeting15:18
ndipanovI am being defensive in saying - if we leave it like that - we will have to let bad code in too15:18
Yathindipanov: also Jay pipes has some proposal for rewriting claims15:18
ndipanovthat is not the only way forward of course15:19
Yathiwe agreed in the nova mid-cycle meetup to revisit after gantt15:19
ndipanovbut the fact that this is something you can write 3rd party pluggins against15:19
ndipanovand we will need to break them15:19
ndipanovmakes me think about the whole point of ERT15:19
ndipanovand that it may need to sit a while15:19
bauzasYathi: I can just propose another alternative without ERT15:20
bauzasYathi: we don't have too much dependency with ERT15:20
n0anobauzas, I was just going to ask how hard it would be to do that15:20
bauzasYathi: the real cool stuff of ERT for the isolate-sched-db are :15:20
Yathibauzas: I saw it is only the recent patches you got it.. to use ERT way of getting instances, flavors etc15:20
*** virmitio has joined #openstack-meeting15:20
*** ramishra has quit IRC15:21
bauzas#1 : possibility to add/remove plugins in a conf style15:21
bauzasie. only provide stats for what operator wants15:21
*** dkranz has joined #openstack-meeting15:21
*** ramishra has joined #openstack-meeting15:21
bauzas#2 : interfaces in RT have already been written (and unittests too) so that's really a quick addition to do15:21
*** afazekas has joined #openstack-meeting15:21
*** jckasper has quit IRC15:22
bauzasn0ano: so if we say we go without ERT, I just need to write an helper class for doing this (plus tests)15:22
bauzasI don't think it's huge thing15:22
*** mberlin1 has quit IRC15:22
bauzaswell, as ndipanov said, that's just matter of adding blobs into blobs...15:22
Yathibauzas: let's probably wait for it.. to see if ERT will stay or not15:23
bauzasYathi: I disagree with you15:23
n0anohmm, the tests would probably be close to the current RT tests so that shouldnt' be that big a deal, I think I like this as a plan B, even if it's more work for us15:23
bauzasYathi: Juno-3 is in less than one month15:23
bauzasn0ano: +115:23
Yathibauzas: oh sure.. I see the time crunch..15:23
bauzasn0ano: that's just removing the user-facing stuff (and plugins)15:23
*** vivek-eb_ has joined #openstack-meeting15:24
n0anoI agress with bauzas , the schedule is tight, waiting is not a good option15:24
*** changbl has joined #openstack-meeting15:24
bauzasthe proposal won't probably include #1 (configurability of plugins)15:24
bauzasie. instances and flavors will be provided15:24
n0anobauzas, I don't see that as a problem, that's a future enhancement15:25
*** ddutta has joined #openstack-meeting15:25
bauzasn0ano: it was my next phrase, stop reading in minds15:25
* n0ano fightening, we're beginning to sound like an old married couple :-)15:25
bauzasabout planning, I freed up my tasks because I delivered both plugins (except aggs but tianst is handing it)15:26
bauzasso I can handle that15:26
*** vivek-ebay has quit IRC15:26
*** eharney has joined #openstack-meeting15:26
bauzasI'll just be on PTO Thurs->Mon15:26
n0anosounds like a plan, just do it15:26
*** mberlin has joined #openstack-meeting15:26
bauzasbut that just means less time to work, not nothing :D15:26
n0anostill the question of the final +2 for the spec, should we ping jogo or someone?15:27
*** amotoki has joined #openstack-meeting15:27
Yathiyou can work in your PTO no ? bauzas :)15:27
bauzasn0ano: feel free to do so15:27
bauzasn0ano: my karma (and my politics skills) are not that good these days :p15:28
n0anoOK, I'll see if I can get his attention15:28
*** xuhanp has quit IRC15:28
bauzasn0ano: anyway, most of the cores are US based15:28
bauzasn0ano: so that sounds a better option15:28
*** dbite has joined #openstack-meeting15:28
bauzasn0ano: provided you feel enough comfortable for answering questions :)15:28
n0anobauzas, we'll find out15:28
bauzassweet15:29
n0anoOK, I think we know what we're doing here...15:29
bauzasindeed15:29
n0ano#topic opens15:29
*** openstack changes topic to "opens (Meeting topic: gantt)"15:29
bauzasabout aggregates, I saw tianst patch15:29
n0anoanyone have anything new15:29
bauzasI just advice him to wait for the new helper class15:29
bauzasthat's it, opens for me15:30
n0anobauzas, send him an email, should be OK15:30
*** BrianB_ has quit IRC15:30
tianstbauzas: i am here :)15:30
n0anoor talk to him now on IRC :-)15:30
bauzastianst: cool, we just agreed to implement a new helper class instead of basing on ERT15:30
tianstsome issue on my network:)15:30
bauzastianst: so I was saying that you just wait until I provide this class15:31
bauzasshouldn't be so long15:31
tianstbauzas: ok, I wiil wait you15:31
n0anoas agreed at the meetup, I'm sending an emal to all the PTLs letting know about Gantt and making sure they won't be surprised about it15:31
bauzason opens, I just saw that you n0ano sent an email :)15:31
bauzas(stop reading minds !)15:31
bauzaswe just had Swift's answer \o/15:32
Yathin0ano: that was a good email you sent today..15:32
n0anoit finally went through?  (I had too many CC addresses, it needed manual approval)15:32
*** FJB has quit IRC15:32
*** yamamoto has joined #openstack-meeting15:32
*** ddutta has quit IRC15:32
n0anoYathi, story of my life, good emails (bad code :-)15:32
Yathiwe need Cinder PTL to approve the story.. neutron has given us verbal vote already15:33
bauzasemailing is more complicated than writing code...15:33
bauzascode is logical, email replies are not15:33
n0anoYathi, +1, I think cinder has the closest requirements to Nova so they're a perfect test case15:34
bauzasSwift sounds interested in15:34
Yathibauzas: +1 emails that need to influence people to agree with you15:34
bauzasprovided we clear out what will be Gantt on a Program basis15:34
n0anoalso, again per the meetup, we need to come up with a rough roadmap for where we want Gantt to go post the split, everyone start thinking about that.15:35
*** afazekas has quit IRC15:35
*** rwsu has joined #openstack-meeting15:35
Yathin0ano: make Gantt the smartest thing on earth :)15:35
bauzasn0ano: I would love to see some people looking at other projects15:35
bauzasn0ano: by "some people", I don't exclude myself15:36
n0anoYathi, I just call that world domination15:36
bauzasn0ano: meaning that as other Shared Services projects, we need to know how other projects schedule their own bits15:36
Yathi:)15:36
notmynamebauzas: it was more of a question than saying we want swift to use it at this point (just to be clear)15:36
n0anobauzas, yes, cross project support is hard but crucial15:36
*** colinmcnamara has quit IRC15:36
bauzasnotmyname: my bad15:36
bauzasn0ano: so my question was15:37
n0anonotmyname, that's cool, I'm hoping that no one has a violent objection first15:37
*** mberlin has quit IRC15:37
bauzasn0ano: before doing roadmap and saying what we should do, should we take time to see where we should go ?15:37
*** yamamoto has quit IRC15:37
bauzasby where I mean at least looking at Neutron node and probably Cinder15:38
n0anobauzas, I would say that's part of the process, let's all think about it for now15:38
bauzass/node/code15:38
*** cdub has joined #openstack-meeting15:38
Yathireplacing Cinder scheduler should be easy I hope.. as they use similar constructs15:38
bauzasYathi: indeed, as Cinder just forked 4 or 5 releases ago15:39
Yathibut may need efforts similar to what is being done for Nova now15:39
n0anowe don't have to have a roadmap immediately, we might not create it until after Paris, but we can start thinking/looking at code now15:39
bauzasYathi: but I'm really unsure that Neutron has a ResourceTracker for example :p15:39
bauzasn0ano: that sounds a good plan15:39
Yathibauzas: need to spend time looking at the projects15:39
bauzasYathi: I already did :)15:40
*** mberlin has joined #openstack-meeting15:40
Yathibauzas: awesome!.. also I think we need to watch for the policy related projects..15:40
bauzasanyway, I think we need to take time to think about the abstractions we have15:40
Yathicreating quite a buzz everywhere.. including neutron..15:40
bauzasYathi: Congress sounds a good fit, but it's not yet incubated15:40
bauzas(already reviewed Congress too...)15:41
n0anoone administrivia, I'm at a conference next week, can I tag you bauzas to run the meeting15:41
bauzasand some bits of code are still needing refactoring before that IMHO15:41
bauzasn0ano: for sure15:41
*** joesavak has joined #openstack-meeting15:41
Yathibauzas: I have watched Congress too closely.. but inside the nova community there have been several policy related BPs15:41
bauzasn0ano: just mail me your thoughts15:41
Yathineed to revisit them too15:41
n0ano#action bauzas to chair meeting on 8/1915:42
bauzasYathi: my personal opinion is that we need an iterative approach15:42
Yathibauzas: +10015:42
n0anobauzas, no mail needed, we read our minds, remember :-)15:42
bauzasn0ano: cool, new discovery in science15:43
n0anoOK, silly time, unless someone has somethin substantive15:43
n0anothen I'll thank everyone and we'll talk again next week (minus me)15:44
n0ano#endmeeting15:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:44
openstackMeeting ended Tue Aug 12 15:44:42 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-08-12-15.01.html15:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-08-12-15.01.txt15:44
openstackLog:            http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-08-12-15.01.log.html15:44
*** johnpur has joined #openstack-meeting15:45
bauzasthanks15:45
*** lcheng has joined #openstack-meeting15:46
*** IanGovett has quit IRC15:48
*** ramishra_ has joined #openstack-meeting15:48
*** ramishra_ has quit IRC15:48
*** shashankhegde has quit IRC15:48
*** ramishra_ has joined #openstack-meeting15:48
*** Mandell has joined #openstack-meeting15:48
*** tianst has quit IRC15:48
*** FJB has joined #openstack-meeting15:49
*** ramishra has quit IRC15:51
*** jgallard has joined #openstack-meeting15:53
*** Yathi has quit IRC15:53
*** aranjan has joined #openstack-meeting15:53
*** ramashri has joined #openstack-meeting15:53
*** ivar-lazzaro has joined #openstack-meeting15:54
*** reed has joined #openstack-meeting15:54
*** emagana has joined #openstack-meeting15:55
*** mchalla has joined #openstack-meeting15:55
*** annegent_ has joined #openstack-meeting15:55
*** eghobo has joined #openstack-meeting15:56
*** IanGovett has joined #openstack-meeting15:58
*** aranjan has quit IRC15:58
*** IanGovett1 has joined #openstack-meeting15:58
*** matrohon has quit IRC15:59
*** banix has joined #openstack-meeting15:59
*** mchalla has quit IRC15:59
*** nati_ueno has joined #openstack-meeting15:59
*** jcoufal has quit IRC16:00
*** arnaud has joined #openstack-meeting16:00
*** nexusz99 has quit IRC16:00
*** vijendar has quit IRC16:01
*** grantbow has joined #openstack-meeting16:02
*** jgallard has quit IRC16:03
*** IanGovett has quit IRC16:03
*** vijendar has joined #openstack-meeting16:03
*** cbader has joined #openstack-meeting16:03
*** nati_ueno has quit IRC16:03
*** jckasper has joined #openstack-meeting16:04
*** toan-tran has quit IRC16:05
*** jtomasek_ has quit IRC16:06
*** jlanoux has quit IRC16:06
*** vijendar has quit IRC16:06
*** balajiiyer has joined #openstack-meeting16:06
*** joesavak has quit IRC16:08
*** tongli has quit IRC16:09
*** kashyap has joined #openstack-meeting16:10
*** vivek-ebay has joined #openstack-meeting16:10
*** vhoward has joined #openstack-meeting16:10
*** vermarah has joined #openstack-meeting16:11
*** vermarah_ has joined #openstack-meeting16:11
*** ajo__ has joined #openstack-meeting16:12
*** Mandell has quit IRC16:13
*** Mandell has joined #openstack-meeting16:13
*** vijendar has joined #openstack-meeting16:13
*** mpaolino has joined #openstack-meeting16:14
*** vivek-eb_ has quit IRC16:14
*** vivek-ebay has quit IRC16:14
*** jrolson has joined #openstack-meeting16:15
*** evgenyf has quit IRC16:15
*** ajo_ has quit IRC16:16
*** FJB has quit IRC16:16
*** SridharRamaswamy has joined #openstack-meeting16:16
*** vijendar has quit IRC16:17
*** vijendar has joined #openstack-meeting16:17
*** ajo_ has joined #openstack-meeting16:18
*** johnpur has quit IRC16:18
*** Mandell has quit IRC16:18
*** arnaud has quit IRC16:18
*** Fdot has quit IRC16:19
*** Fdot has joined #openstack-meeting16:20
*** ajo__ has quit IRC16:20
*** shashankhegde has joined #openstack-meeting16:22
*** Fdot has quit IRC16:23
*** sbalukoff has quit IRC16:25
*** grantbow has left #openstack-meeting16:26
*** leeantho has joined #openstack-meeting16:27
*** ildikov has joined #openstack-meeting16:27
*** pballand has joined #openstack-meeting16:28
*** yamamoto has joined #openstack-meeting16:32
*** kentwu_ has joined #openstack-meeting16:33
*** shashankhegde has quit IRC16:35
*** nshaikh has quit IRC16:36
*** chandankumar has quit IRC16:36
*** AlexF_ has quit IRC16:37
*** yamamoto has quit IRC16:37
*** _nadya_ has quit IRC16:38
*** vivek-ebay has joined #openstack-meeting16:40
*** derekh has quit IRC16:41
*** kentwu__ has joined #openstack-meeting16:41
*** bdpayne has joined #openstack-meeting16:41
*** ramishra_ has quit IRC16:41
*** markmcclain1 has quit IRC16:42
*** kentwu_ has quit IRC16:44
*** kentwu has joined #openstack-meeting16:45
*** mpaolino has quit IRC16:45
*** kentwu__ has quit IRC16:47
*** banix has quit IRC16:47
*** comay has joined #openstack-meeting16:47
*** banix has joined #openstack-meeting16:48
*** e0ne has quit IRC16:48
*** aranjan has joined #openstack-meeting16:48
*** ramishra has joined #openstack-meeting16:48
*** MaxV has quit IRC16:49
*** ramishra_ has joined #openstack-meeting16:50
*** ramishra_ has quit IRC16:51
*** ramishra_ has joined #openstack-meeting16:51
*** neelashah has quit IRC16:52
*** ramishra has quit IRC16:54
*** julienvey has quit IRC16:55
*** sandywalsh_ has quit IRC16:56
*** SumitNaiksatam has quit IRC16:56
*** olkonami has joined #openstack-meeting16:56
*** akuznetsov has quit IRC16:58
*** SridharG has joined #openstack-meeting16:59
*** ndipanov is now known as ndipanov_gone16:59
*** nati_ueno has joined #openstack-meeting17:00
*** bswartz has joined #openstack-meeting17:01
*** joesavak has joined #openstack-meeting17:01
*** johnpur has joined #openstack-meeting17:01
*** arnaud has joined #openstack-meeting17:01
*** marekd has left #openstack-meeting17:02
*** marekd has joined #openstack-meeting17:02
*** mestery has quit IRC17:02
*** grantbow has joined #openstack-meeting17:02
*** mestery has joined #openstack-meeting17:03
marekdo/17:03
*** shashankhegde has joined #openstack-meeting17:04
*** Ish__ has joined #openstack-meeting17:04
*** nati_ueno has quit IRC17:05
*** sandywalsh has joined #openstack-meeting17:06
*** mrmartin has quit IRC17:06
*** thangp has quit IRC17:08
*** k4n0 has joined #openstack-meeting17:08
*** paragan has quit IRC17:08
*** SridharG has quit IRC17:09
boris-42hi all17:11
boris-42#start meeting17:11
boris-42#startmeeting Rally17:11
openstackMeeting started Tue Aug 12 17:11:45 2014 UTC and is due to finish in 60 minutes.  The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot.17:11
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:11
*** openstack changes topic to " (Meeting topic: Rally)"17:11
openstackThe meeting name has been set to 'rally'17:11
*** balajiiyer has left #openstack-meeting17:11
*** virmitio has left #openstack-meeting17:12
boris-42marekd hi17:12
boris-42olkonami hi17:12
olkonamihi17:12
boris-42oanufriev hi17:12
*** SumitNaiksatam has joined #openstack-meeting17:12
boris-42coolsvap hi17:12
oanufrievboris-42 hi17:13
coolsvaphello17:13
boris-42k4n0 hi17:13
k4n0boris-42, hi17:13
boris-42rmk hi17:13
*** rediskin has joined #openstack-meeting17:14
*** tzabal has joined #openstack-meeting17:14
boris-42rediskin tzabal hi guys17:15
tzabalhello17:15
rediskinhi17:15
*** krtaylor has quit IRC17:15
boris-42Okay let's start from various updates17:15
*** lcheng has quit IRC17:15
boris-42#topic could you say about cleanup stuff that you are working on, what did you done and what you are going to do17:16
*** openstack changes topic to "could you say about cleanup stuff that you are working on, what did you done and what you are going to do (Meeting topic: Rally)"17:16
rediskinok cleanups17:16
rediskinwell17:16
*** hrybacki has quit IRC17:17
rediskinim start some refactoring around cleanups17:17
*** andreaf_ has quit IRC17:17
rediskinat first im doing cleanup rate limitting17:17
rediskinbecause currently rally is trying to delete objects too aggressively17:17
*** andreaf_ has joined #openstack-meeting17:17
rediskinit may broke cloud if there is a lots of objects to delete17:18
rediskinlater im going to start work on cleanup checks17:19
rediskincollect info about cloud before benchmarks, and after benchmarks17:20
*** jkremer has quit IRC17:20
rediskinand then compare it17:20
rediskinto determine which objects was not deleted17:20
*** andreaf has joined #openstack-meeting17:20
*** Ish__ has quit IRC17:20
rediskinor objects was deleted, but should not be deletet %)17:20
rediskinboris-42: ^17:21
boris-42rediskin so check will be in gates?17:21
*** Ish__ has joined #openstack-meeting17:21
*** igordcard has joined #openstack-meeting17:21
rediskinit not problem to do it in gates17:21
rediskinif it done at all %)17:21
boris-42rediskin cool17:21
boris-42any questions?17:21
boris-42tzabal coolsvap rmk olkonami ^17:22
*** andreaf_ has quit IRC17:22
k4n0nope17:22
boris-42ok great17:23
*** rmoe has quit IRC17:23
boris-42#topic benchmark context refactoring to support persitance context & LDAP17:23
*** openstack changes topic to "benchmark context refactoring to support persitance context & LDAP (Meeting topic: Rally)"17:23
rmkHello17:23
boris-42rmk hi there we have rally meeting)17:23
rmkyep Im here now17:23
boris-42So guys I am working mostly on refactoring benchmark context engine17:23
boris-42first of all we should make it possible to consume setup/cleaup methods of context separately17:24
boris-42This actually is already done and hope that will be soon merged17:24
boris-42https://review.openstack.org/#/c/104962/17:24
boris-42After that I am going to move creation of benchmark.context to level of benchmark.engine from scenario runner17:25
boris-42And refactor what we are storing in context shared object17:25
boris-42after this we can work on creating DB table for storing context17:26
k4n0Sounds great17:26
boris-42and creating CLI commands for create/deleting persistence context17:26
boris-42On another way I am going to extend existing deploy config17:26
*** SridharRamaswamy has quit IRC17:26
*** aranjan_ has joined #openstack-meeting17:26
boris-42so It will accept as well list of users17:26
boris-42and drop hardcoded "users" context requiremtns17:27
boris-42E.g. you are not able to run any of tasks, without this context17:27
*** SridharRamaswamy has joined #openstack-meeting17:27
*** mspreitz has quit IRC17:27
*** MaxV has joined #openstack-meeting17:27
*** MaxV has quit IRC17:27
*** SridharR_ has joined #openstack-meeting17:28
boris-42So LDAP clouds can be benchmark able as well17:28
boris-42rmk ^17:29
boris-42#topic Documentation17:29
*** openstack changes topic to "Documentation (Meeting topic: Rally)"17:29
*** KurtMartin has joined #openstack-meeting17:29
boris-42oanufriev hey there17:29
boris-42oanufriev update please status17:29
*** kmartin has quit IRC17:29
*** MaxV has joined #openstack-meeting17:30
*** MaxV has quit IRC17:30
*** kmartin has joined #openstack-meeting17:30
*** aranjan has quit IRC17:30
oanufrievi worked on appending Rally sphinx documentation with Rally wiky items17:31
*** aranjan_ has quit IRC17:31
oanufrievno it's merged17:31
*** SridharRamaswamy has quit IRC17:31
*** gyee has joined #openstack-meeting17:31
boris-42oanufriev ?17:31
*** Murali_ has quit IRC17:31
boris-42now it's merged?17:31
oanufriev*now*  and i've being working on scrips that properly append17:32
*** MarkAtwood has quit IRC17:32
oanufrievsamples and user stories to sphinx17:32
boris-42oanufriev could you provide links?17:32
*** yamamoto has joined #openstack-meeting17:32
oanufrievand integrate into tox17:32
*** MaxV has joined #openstack-meeting17:32
oanufriev*toc*17:32
oanufrievhttps://review.openstack.org/#/c/113454/17:32
*** ramishra has joined #openstack-meeting17:33
boris-42ok nice17:33
oanufrievplans^17:33
oanufriev*plans:* (sorry)17:33
boris-42k4n0 rediskin ^ we will need to analyze this17:33
k4n0yes17:34
*** stevemar has quit IRC17:34
boris-42Ok let's move to other topics17:34
boris-42#topic benchmarking in VM17:34
*** openstack changes topic to "benchmarking in VM (Meeting topic: Rally)"17:34
*** MaxV has quit IRC17:34
boris-42tzabal could you provide updates of you great work?17:34
*** gyee has quit IRC17:34
tzabalsure17:34
tzabalwell, i am working on the vm benchmarking17:35
tzabalright now i want to try the new vm benchmark scenario blogbench in gates17:35
*** Mandell has joined #openstack-meeting17:35
*** dwalleck has joined #openstack-meeting17:36
tzabali think that the whole thing works, at least in my local test environment, so i hope that this will be in gates too17:36
*** dwalleck has left #openstack-meeting17:36
*** ramishra_ has quit IRC17:36
tzabalthen we can review the patches for any code refactoring, and then i will add the unit tests17:36
*** emagana has quit IRC17:36
*** yamamoto has quit IRC17:37
tzabalany questions? :)17:37
*** emagana has joined #openstack-meeting17:37
*** esker has quit IRC17:38
*** rossk has joined #openstack-meeting17:39
*** vishwanathj has joined #openstack-meeting17:39
*** salv-orlando has joined #openstack-meeting17:40
*** ramishra_ has joined #openstack-meeting17:40
*** e0ne has joined #openstack-meeting17:40
boris-42tzabal nice work on this17:41
boris-42tzabal could you put links on your patches17:41
boris-42here17:41
tzabalhttps://review.openstack.org/113119 this one is about a new benchmark context, the benchmark_image that acts as a base for the other vm benchmark contexts17:42
*** ramishra has quit IRC17:42
tzabalhttps://review.openstack.org/#/c/98172/ this one is the "base" for the vm benchmark scenarios17:42
tzabalhttps://review.openstack.org/#/c/97030/ and this one is the benchmark blogbench17:43
*** neelashah has joined #openstack-meeting17:43
tzabaljust a note, they are not updated yet, i have made some modifications and they are currently only local, but i will update soon17:43
tzabalfor example, the "base" that i wrote above, seems to have in the latest patch set 0 files (shame), but i will fix it :)17:44
tzabalits files can actually be found in the benchmark blogbench review (vmtasks and utils)17:44
tzabalbut i have made some changes in the base.py of context, like defining the class as abstact17:45
tzabalthis will get up soon17:45
*** jsavak has joined #openstack-meeting17:45
*** ajayaa has joined #openstack-meeting17:46
boris-42tzabal ok nice17:46
boris-42tzabal I will try to get time and review your patches17:47
k4n0tzabal, thanks for the work17:47
*** sbalukoff has joined #openstack-meeting17:47
tzabalthanks17:48
tzabali hope that it will be stable :)17:48
*** ramishra_ has quit IRC17:49
*** joesavak has quit IRC17:49
boris-42#topic open discussion17:49
*** openstack changes topic to "open discussion (Meeting topic: Rally)"17:49
*** jsavak has quit IRC17:49
*** joesavak has joined #openstack-meeting17:49
boris-42k4n0 coolsvap could you please provide details about what you are working on17:50
boris-42and how that's go17:50
coolsvapI am working on couple of refactoring patches17:50
k4n0boris-42, I am working on adding --json, --pprint , --html flags, been a slow last week.17:50
k4n0Also working on adding metadata to task17:50
k4n0Unit tests coverage17:51
*** vishwanathj has left #openstack-meeting17:51
k4n0All tasks are slow, but i will pick up pace now17:51
coolsvapThe change sets are https://review.openstack.org/113011, [WIP] https://review.openstack.org/11198917:51
coolsvapI am getting some pace on blueprint https://blueprints.launchpad.net/openstack/?searchtext=add-rally-create-cli-command17:52
coolsvapsubmitted a patch https://review.openstack.org/#/c/98992/17:52
coolsvapThe unit test coverage blueprint I am working on is a bit slow17:52
coolsvapthats it from my side17:53
*** padkrish has joined #openstack-meeting17:53
boris-42k4n0 do you have any progress related to metadata ?17:55
k4n0boris-42, Not yet17:55
boris-42k4n0 if you will have any question just ping me17:55
k4n0boris-42, will get patches before end of week17:55
k4n0boris-42, sure17:55
*** xyang1 has joined #openstack-meeting17:55
boris-42coolsvap I'll try to review quotas benchmarks17:55
boris-42coolsvap /benchamrks/patch*17:55
coolsvapboris-42, sure thanks17:56
boris-42coolsvap and thanks for doing this17:56
boris-42k4n0 coolsvap  thanks for updates17:56
*** dbite has quit IRC17:56
*** Murali_ has joined #openstack-meeting17:56
k4n0thanks17:56
boris-42Do we have any questions?17:56
*** gyee has joined #openstack-meeting17:56
boris-42to dicsusss?17:56
*** mchalla has joined #openstack-meeting17:56
*** pdmars has quit IRC17:57
*** Riddhi has quit IRC17:57
boris-42Ok if somebody would like to disucss anything you are welcome to #openstack-rally17:57
coolsvapboris-42, regarding recent updates to trello17:57
boris-42#endmeeting17:57
olkonamiI fixed plugins patch to work with current code and updated context plugin sample17:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:57
openstackMeeting ended Tue Aug 12 17:57:54 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-08-12-17.11.html17:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-08-12-17.11.txt17:57
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-08-12-17.11.log.html17:58
boris-42coolsvap yep?17:58
*** jsavak has joined #openstack-meeting17:58
boris-42coolsvap I tried to refactor it17:58
*** k4n0 has quit IRC17:58
boris-42coolsvap to make it simpler and more clear for usage17:58
*** vhoward has left #openstack-meeting17:58
coolsvaplets catchup on #openstack-rally17:58
coolsvap:)17:58
*** jkremer has joined #openstack-meeting17:58
*** topol has joined #openstack-meeting17:59
*** mestery has quit IRC18:00
*** kwss has joined #openstack-meeting18:00
*** joesavak has quit IRC18:00
*** nati_ueno has joined #openstack-meeting18:01
*** VijayB has joined #openstack-meeting18:01
dolphmayoung, bknudson, dstanek, jamielennox, morganfainberg, stevemar, gyee, henrynash, topol, marekd, lbragstad, joesavak, shardy, fabiog, fmarco76, nkinder, lloydm, shrekuma, ksavich, hrybacki, rharwood, grantbow: https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:01
*** trey_h has quit IRC18:01
dstaneko/18:01
topolo/18:01
bknudsondolphm: hi18:01
lbragstaddolphm: hey18:01
marekdhello18:01
*** dhouck1 has quit IRC18:01
*** mchalla has quit IRC18:02
ayoungFirst squad all present and accounted for/18:02
dolphmapologies for dissappearing last week18:02
gyee\o18:02
dolphmalso, crazy long agenda today18:02
*** jsavak has quit IRC18:02
dolphmso, let's begin!18:02
dolphm#startmeeting keystone18:02
openstackMeeting started Tue Aug 12 18:02:38 2014 UTC and is due to finish in 60 minutes.  The chair is dolphm. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: keystone)"18:02
openstackThe meeting name has been set to 'keystone'18:02
dolphmreal quick...18:02
dolphm#topic Feature Proposal Freeze: August 21st18:02
*** openstack changes topic to "Feature Proposal Freeze: August 21st (Meeting topic: keystone)"18:02
dolphmthat's next week18:02
*** dhouck1 has joined #openstack-meeting18:03
*** mchalla has joined #openstack-meeting18:03
dolphmand it means your blueprints need to be feature complete, stable and in review by that day, else be bumped to kilo18:03
dolphmif you don't think something is going to make it, give me a heads up ASAP18:03
dolphmwe're definitely talking about the blocked ones later on the agenda18:03
dolphmso that is all, ping me later if you have questions :)18:04
gyeedolphm, both spec and impl needs to be up there by 8/21?18:04
*** andreykurilin_ has joined #openstack-meeting18:04
*** jckasper has quit IRC18:04
gyeeor just bp and spec18:04
*** pdmars has joined #openstack-meeting18:04
dolphmgyee: according to the rest of the community, your spec should have landed weeks ago to be considered for juno18:04
*** e0ne has quit IRC18:04
*** olkonami has left #openstack-meeting18:04
*** tzabal has left #openstack-meeting18:04
*** banix has quit IRC18:05
*** trey_h has joined #openstack-meeting18:05
dolphmgyee: i did a poor job of communicating that here, so i'm not considering that to be a strict rule18:05
dolphmif something looks stable, let's consider it18:05
dolphm#topic Cleanup / Abandonment of WIP and Lingering reviews in Keystone repositories18:05
*** openstack changes topic to "Cleanup / Abandonment of WIP and Lingering reviews in Keystone repositories (Meeting topic: keystone)"18:05
ayoung++18:05
lbragstadwill we be following that for Kilo?18:05
dolphmwe have a lot of old reviews that need to be pruned18:05
*** dwalleck has joined #openstack-meeting18:05
*** nati_ueno has quit IRC18:05
dolphmlbragstad: likely, yes18:05
dolphmlbragstad: the earlier specs land the better18:05
*** brich1 has joined #openstack-meeting18:06
lbragstadok, cool18:06
*** jckasper has joined #openstack-meeting18:06
dolphmon stale reviews: cores, feel free to abandon things that look like they aren't going to land. be sure to include an explanation18:06
dolphmabandoned reviews can be re-opened by the author, so it's not like a permament -2 or anything18:06
*** jamielennox has joined #openstack-meeting18:07
*** Mandell has quit IRC18:07
dolphmat the very least, if something is miserably failing gate jobs and needs some love, leave it as WIP until someone can tackle it18:07
dolphmmorganfainberg: anything else to add or are you afk?18:07
ayoungI'll probably do that with most of mine, and get people to focus only on the ones that are high priority18:07
* ayoung the worst offender for malingering reviews18:08
dstanekayoung: i was thinking the same thing18:08
dstanekfor mine i mean18:08
*** jedimike has joined #openstack-meeting18:08
ayoungYou meant for both.18:08
*** otherwiseguy has quit IRC18:08
dstaneksure, ok18:08
*** alkari has joined #openstack-meeting18:08
dolphmayoung: i'm far worse on allowing my reviews to stagnate!18:08
gyeeya'll get paid on number of reviews? :)18:08
dstanekgyee: are you offereing?18:09
* gyee hides18:09
dolphmdstanek: ++18:09
dstaneki just fix stuff as i see it in other people's reviews18:09
dolphmdstanek: ++18:09
dstanekor when poking around18:09
dolphmrenaming this on the agenda...18:09
*** penick has joined #openstack-meeting18:10
dolphm#topic Last specs for Juno18:10
*** openstack changes topic to "Last specs for Juno (Meeting topic: keystone)"18:10
*** leonchio_ has joined #openstack-meeting18:10
dolphmauth data https://review.openstack.org/#/c/107325/18:10
*** penick has quit IRC18:10
dolphmunscoped catalog https://review.openstack.org/#/c/107333/18:10
*** penick has joined #openstack-meeting18:10
jamielennoxyep, so hopefully everyone has seen this, we talked about it a few weeks ago18:10
dolphmgyee: did you have one for consideration? (that's nearly implemented?:)18:10
*** jorge_munoz has joined #openstack-meeting18:10
gyeedolphm, the x.509 auth depends on generic mapping18:11
jamielennoxneed to get some actual votes on it though if its going to go through18:11
gyeeI am working with Kristy on this to get the generic mapping working first18:11
morganfainbergdolphm, o/ here now18:11
marekdgyee: ++ cool18:11
dolphmgyee: ? https://blueprints.launchpad.net/keystone/+spec/generic-mapping-federation18:11
morganfainbergdolphm, but don't have anything to add to your comments18:11
dolphmgyee: whats your bp name, i'll link them18:12
gyeedolphm, https://review.openstack.org/#/c/105913/5/specs/juno/x509-ssl-client-cert-authn.rst18:12
dolphm#link https://review.openstack.org/#/c/107325/ auth data spec18:12
dolphm#link https://review.openstack.org/#/c/107333/ unscoped catalog spec18:12
gyeehttps://blueprints.launchpad.net/keystone/+spec/x509-ssl-client-cert18:12
gyee-authn18:12
gyee++ for auth data spec18:13
bknudsonis https://review.openstack.org/#/c/107325/6/specs/juno/auth-specific-data.rst proposing get rid of /v3/catalog?18:13
gyeeno sure about the unscoped catalog one though18:13
dolphmgyee: is there an implementation for the x509 spec somewhere?18:13
*** Mandell has joined #openstack-meeting18:13
gyeedolphm, no, there's an implemented based on auth plugin which I abandon https://review.openstack.org/#/c/103736/18:14
gyeebut I don't have one based on generic map yet18:14
*** eguz has joined #openstack-meeting18:14
dolphmgyee: are we likely to see one before next week?18:14
*** jrolson has quit IRC18:15
grantbowinteresting18:15
dolphmgyee: if not, we should plan this for kilo now18:15
gyeedolphm, lets do it for Kilo to be safe18:15
gyeeI need to get the generic map working18:15
gyeeright now its not truly "generic"18:15
dolphmgyee: awesome, i'd like some more focus there :)18:15
gyeemapping is only capable of mapping to user_id and group_id right now from what I can tell18:16
dolphmstevemar's not here, but open id connect support is in the same boat. blocked by generic mapping18:16
dolphmgyee: that's true (a list of groups)18:16
gyeeI need to get it to a point where we can map one set to another set of attributes18:16
marekdgyee: i think generic mapping/reeingeneered federation patch will also be posponed for K ?18:17
marekddolphm:  ^^18:17
dolphmmarekd: should it be postponed?18:17
gyeemarekd, we need it to be truly generic18:17
*** eghobo has quit IRC18:17
marekddolphm: it's still marked as WIP.18:17
*** ajo__ has joined #openstack-meeting18:17
dolphmmarekd: correct; do you think it needs more time?18:17
dolphmi don't know how far the implementation is behind the spec18:18
marekddolphm: i posted my comments a long time ago, and since then I haven't heard anything. gyee says he works with Kristy on that so he can answer whether it's far beyond the spec but AFAIR it needs more time.18:18
dolphmi'm going to bump all 3 to 'next' (kilo) for now, and if something changes this week, we can re-evaluate18:19
marekddolphm: great!18:19
*** krtaylor has joined #openstack-meeting18:19
*** padkrish has quit IRC18:19
*** eguz has quit IRC18:19
gyeedolphm, ++18:19
dolphmjamielennox: my impression of auth data and the unscoped catalog is that they can be ready for code review this week if the specs are approved - is that true?18:20
gyeesince they are all related18:20
marekdyeah18:20
*** padkrish has joined #openstack-meeting18:20
jamielennoxdolphm: i have a WIP for unscoped catalog18:20
jamielennoxdolphm: auth data should be fairly trivial but i haven't done it18:20
*** ajo_ has quit IRC18:20
*** padkrish_ has joined #openstack-meeting18:20
jamielennoxyou had a patch to move /catalog to /auth/catalog from memory18:20
*** marun has quit IRC18:21
dolphmthat's still up, somewhere18:21
*** stevemar has joined #openstack-meeting18:21
*** marun has joined #openstack-meeting18:21
stevemaro/18:21
*** markmcclain has joined #openstack-meeting18:21
jamielennoxdolphm: so yes, if we approve them i can have code ready in a day or two18:22
dolphmstevemar: fyi, bumping openid connect to kilo unless mapping gets some traction this week18:22
dolphmgeneric-mapping18:22
dolphmjamielennox: ack18:22
stevemardolphm, ok, did Henry give his opinion on the matter?18:22
*** SefaKoc has joined #openstack-meeting18:22
topoldolphm, what is the Aug 21 deadline again? blueprints or  code must be under review?18:22
dolphmstevemar: unavailable18:22
marekdtopol: code18:22
stevemartopol, the latter18:22
gyeetopol, the whole shebang18:22
dolphmtopol: stable code in review18:22
jamielennoxbnemec: sorry just saw comment from further back - it's proposing to move it to /auth/catalog not get rid of it18:22
ayoungthere are 3 reasons to have the unscoped catalog, BTW:  list projcts, list domains, exchage the unscoped token for a token18:22
jamielennoxoops bknudson ^ was for you18:23
bknudsonjamielennox: ok.18:23
*** rmoe has joined #openstack-meeting18:23
bknudsonwas just hoping that /v3/catalog could be made consistent with this18:24
dolphmbknudson: it would be18:24
gyeecatalog is optional anyway so I can the base auth plugin can handle that logic18:24
*** padkrish has quit IRC18:24
*** rmoe has quit IRC18:24
gyeeif catalog is absent, try to fetch it via the catalog api18:24
bknudsongyee: that's going to be /v3/auth/catalog and not /v3/catalog18:25
*** pelix has quit IRC18:25
dolphmassuming jamielennox's auth-data spec is approved18:25
bknudsonjust write your code to use JSON Home to find the resource and you won't have to worry about it18:25
dolphmbknudson: =)18:25
gyeeI am fine either way, just a matter of consistency18:26
*** rcarrill` has joined #openstack-meeting18:26
gyeeif everybody is going with JSON home, why not18:26
bknudsonIn K somebody can work on client support.18:27
dolphm#topic Keystone Weekly Bug Report18:27
*** openstack changes topic to "Keystone Weekly Bug Report (Meeting topic: keystone)"18:27
dolphmlbragstad: o/18:27
dolphmthis is new :)18:27
lbragstadhttp://pasteraw.com/b0r3xfk41debm0tdjwcewtmf9k2lf0f18:27
lbragstadso, just wanting to do a weekly bug round up18:27
lbragstadjust a quick 30 second "here are all the bugs that were opened against us in the last 7 days and their status"18:28
stevemarlbragstad, neat, thanks for this, helps for folks like me who don't look at launchpad often enough18:28
bknudson"ldap binary fields fail when code try to convert to utf8" is interesting... I thought we fixed it18:28
lbragstadI can do this for keystone, keystonemiddleware, and python-keystoneclient18:28
bknudsonbut then it also shows that we're using LDAP inefficiently and fetching more attrs than we need to18:28
morganfainberglbragstad, that would be awesome18:28
dolphmlbragstad: for future reference, you could use the wonderful launchpad api to query this stuff18:28
lbragstaddolphm18:29
lbragstadit's built on the api18:29
marekd:D18:29
dolphmlbragstad: win18:29
lbragstadhttps://github.com/lbragstad/openstack-infra-scripts18:29
morganfainbergdolphm, lbragstad, there is also the untriaged bot that triple-o is using, we might be able to use that and report in the channel at X interval what bugs are not looked at18:29
*** Haneef has joined #openstack-meeting18:29
lbragstadsome minor modifications I did to jogo's bug roundup infra scripts18:29
*** rmoe has joined #openstack-meeting18:29
lbragstadhopeing this will help up triage bugs a little faster, not saying it's not fast enough :)18:30
lbragstadhoping*18:30
dolphmlbragstad: well now you just need a more recent run - everything in the paste is out of date :P18:30
*** nonameentername has joined #openstack-meeting18:30
lbragstaddolphm: sounds good, I'll run this for keystone, keystonemiddleware, and python-keystoneclient before every meeting and paste the results18:31
*** vjay has quit IRC18:31
dolphmlbragstad: and if possible: openstack-api-site for bugs with the identity-api tag18:31
lbragstaddolphm: good point, I can built that in18:31
*** ajo__ has quit IRC18:31
dolphmi haven't worked with tags in the api, so i don't know how well that will go18:31
ayoungGotta drop.  Back on line in an hour-ish18:32
dolphmayoung: ack18:32
*** padkrish_ has quit IRC18:32
*** Longgeek has quit IRC18:32
*** yamamoto has joined #openstack-meeting18:32
*** crc32 has joined #openstack-meeting18:32
dolphmbug love appreciated :)18:32
*** padkrish has joined #openstack-meeting18:32
dolphm#topic What is a sane default cache timeout?18:32
*** openstack changes topic to "What is a sane default cache timeout? (Meeting topic: keystone)"18:32
dolphmdstanek: o/18:32
dolphm#link https://bugs.launchpad.net/keystone/+bug/135591918:32
uvirtbotLaunchpad bug 1355919 in keystone "By default when caching is enabled, objects will be cached forever" [Medium,In progress]18:32
dstanekso i want to get opinions from the group18:33
dstanekwhat would be a sane setting?18:33
morganfainbergdolphm, dstanek, that is the case for assignment, tokens have a default already18:33
bknudsonforever is an unreasonable default18:33
*** vjay has joined #openstack-meeting18:33
morganfainbergdstanek, dolphm, i think catalog is also affected by that bug (now)18:33
*** crc32 has quit IRC18:33
dolphmthere were a few cache_time options with no default18:33
dstaneki chose 10 minutes in my patch, but i would be open to discussion18:33
*** crc32 has joined #openstack-meeting18:34
dstanekassignment, catalog and token IIRC18:34
gyeedstanek, really? we cache the stuff *forever*?!!18:34
dolphmgyee: by default18:34
gyeeoh my18:34
dstanekgyee: there is code that will remove cached entries for some things18:34
bknudsonI thought we didn't cache anything by default18:34
morganfainbergdstanek, fairly certain token has a default18:34
dstanekbut as far as i can tell it's not everything18:34
dolphmdstanek: i was just going to suggest "minutes", so 10 fits my answer :)18:34
*** dbite has joined #openstack-meeting18:34
*** vivek-eb_ has joined #openstack-meeting18:34
morganfainbergor it used to18:35
morganfainbergvlah18:35
morganfainbergblah*18:35
*** e0ne has joined #openstack-meeting18:35
dstanekmorganfainberg: :-)18:35
morganfainbergbknudson, you have to turn on caching, the config is very deployment specific18:35
*** vivek-eb_ has quit IRC18:35
morganfainbergbknudson, but if you do turn it on, it caches forever (well barring an invalidation because of update, keystone is *good* about invalidating when things change)18:35
dolphmmorganfainberg: typo-correcting your frustration is either coincidental or ironic, i can't remember which18:36
*** ayoung has quit IRC18:36
*** novas0x2a|laptop has joined #openstack-meeting18:36
bknudson10 minutes seems reasonable to me.18:36
morganfainbergdolphm, both!18:36
*** vivek-eb_ has joined #openstack-meeting18:36
Haneefmorgon: I believe both global cache and token cache is disabled by default18:36
bknudsonkeystone doesn't know about users when you have them in ldap18:36
*** rudrarugge has joined #openstack-meeting18:36
*** yamamoto has quit IRC18:36
*** KurtMartin has quit IRC18:36
dstanekthe review itself it trivial if we agree on 10 minutes - https://review.openstack.org/#/c/11358618:36
bknudsonso if you enable caching for users then it won't notice a change for the cache time?18:37
*** padkrish_ has joined #openstack-meeting18:37
*** padkrish has quit IRC18:37
*** vivek-ebay has quit IRC18:37
*** KurtMartin has joined #openstack-meeting18:37
bknudson(read-only ldap)18:37
gyeebknudson, its a feature to cache LDAP lookups18:37
dolphmand it's dependent on an even more trivial review: https://review.openstack.org/#/c/113585/18:37
gyeeperformance gain18:37
morganfainbergbknudson, 10 mins works for me, may i suggest we do the same thing we do for the "enable" have a global default that can be overridded by the individual subsystem18:37
topol10 mins sounds good18:37
*** ivar-lazzaro has quit IRC18:37
gyeeright now we do 3 LDAP roundtrips with every auth18:37
dstanekmorganfainberg: that would be easy enough18:37
dolphmgyee: for extra security18:38
gyeehuh?18:38
bknudson3-factor authentication18:38
jamielennoxdolphm: ++18:38
morganfainbergdstanek, yah, and it means as we add more caching, people don't need to remember adding the default18:38
gyeeheh, I get the joke now18:38
*** gokrokve_ has joined #openstack-meeting18:38
dolphmwe need to have the openstack code proposal bot give us sample config updates daily <-- someone #action themselves thx18:38
morganfainbergdstanek, it would just be changing the lambdas18:38
morganfainbergdolphm, infra nixed that18:38
morganfainbergdolphm, when i proposed it -- or is that a joke18:38
*** alexpilotti has quit IRC18:39
dolphmmorganfainberg: i'm serious - why was it nixed?18:39
morganfainbergdolphm, because it "wasn't what they wanted" they want sample configs to be generated on release. - it was a lot of back and forth.18:39
morganfainbergdolphm, i'll revisit it, but it was pretty resounding "no, not the right answer"18:39
bknudsonwe never used the lockutils stuff... it was just pulled in via oslo-incubator.18:40
gyeecan't we automate the sample conf generation stuff in Jenkins?18:40
gyeelike some sort of hook?18:40
bknudsonnova doesn't have a sample config in git repo18:40
dolphmgenerated on release is dumb for the sake of docs18:40
morganfainberggyee, no, automation is not allowed to commit to a repo.18:40
dstaneki have a test i can commit that will break if the config isn't up to date - that may help a little18:40
gyeemorganfainberg, seem dump to having to manually generate it every time18:41
gyeedumb18:41
morganfainbergdstanek, i can add a simple non-voting job that tells us if it is out of date18:41
bknudsondstanek: we tried the test breaking on sample config and it was a disaster18:41
morganfainbergdstanek, infra wasn't opposed to that really18:41
morganfainbergbut we cant *gate* on it being up-to-date18:41
*** jmh has quit IRC18:41
*** ksavich has joined #openstack-meeting18:41
stevemardolphm, fyi updated meeting agenda18:41
*** gokrokve has quit IRC18:41
*** banix has joined #openstack-meeting18:41
dolphmmorganfainberg: that would be better than where we're at18:42
bknudsonhttp://git.openstack.org/cgit/openstack/nova/tree/etc/nova/README-nova.conf.txt18:42
dstanekbknudson: i didn't realize we had a test. i remember the issues generating the config18:42
morganfainbergi'll revisit proposal bot with them first.18:42
dolphmack18:42
bknudsonwe could just go with Nova's approach and not have a sample config in git18:42
dstanekanyway...i'll create a patch to have a global default cache_time18:42
morganfainbergbknudson, that is likely what we'll be told to do.18:42
dolphmbknudson: i think that's a terrible approach from the perspective of docs and new user experience. it's an unnecessary hurdle18:42
*** banix has quit IRC18:43
topoldolphm +++18:43
dolphmmorganfainberg: and i'm happy to argue against it18:43
*** gokrokve_ has quit IRC18:43
bknudsonI find the sample config in git handy18:43
morganfainbergdolphm, ++ i'll poke ya when we get there (later today)18:43
dolphmbknudson: i link people to it every couple days, for sure18:43
dolphmmorganfainberg: thanks18:43
dolphm#topic Attempt to assign a role to a non existent user should fail18:43
*** openstack changes topic to "Attempt to assign a role to a non existent user should fail (Meeting topic: keystone)"18:43
morganfainbergdolphm, if we go non-voting job, it'll be a check-only job18:43
morganfainberg(not run at gate time)18:43
dstanekbknudson: ++ i point people to it quite a bit18:43
dolphmi just wanted to bring this up again, because i'm the sole voice on this, along with everyone filing bugs18:43
dolphm#link https://bugs.launchpad.net/keystone/+bug/135565518:43
uvirtbotLaunchpad bug 1355655 in keystone "Attempt to assign a role to a non existent user should fail" [Undecided,Opinion]18:43
*** Guest60060 has joined #openstack-meeting18:44
morganfainbergi think the reason for that was federated users.18:44
dolphmi left it as opinion, but i really think we should 404 for invalid data. users will forever be confused18:44
*** banix has joined #openstack-meeting18:44
dolphmmorganfainberg: correct18:44
bknudsonthere have been arguments that we shouldn't 404 for this.18:44
bknudsonfor the case where you're using LDAP and for some reason the user hasn't been added yet18:45
bknudsonWe should get a use case that says why this must fail18:45
*** MaxV has joined #openstack-meeting18:45
morganfainbergbknudson, i'm not sure that is really a valid case. esp. with the user_id mapping stuff18:45
bknudsonthe complaint here is just that tempest fails.18:45
dstanekhow do you give roles to users in federation anyway? i thought they were always mapped to a group18:46
bknudsonwhat's the real issue?18:46
morganfainbergdstanek, they are.18:46
dolphmbknudson: user experience is the use case18:46
dolphmthe one that i see, anyway18:46
bknudsonok, but this bug report isn't about UX18:46
dolphmbknudson: agree/understood18:46
dolphmi'm just going to put it on the agenda everytime someone complains :)18:47
dolphm#topic notifications for role assignments18:47
*** openstack changes topic to "notifications for role assignments (Meeting topic: keystone)"18:47
dolphmstevemar: o/18:47
dstanekthe behaviour, i think, is not intutitive and will keep confusing people18:47
dolphm#link https://review.openstack.org/#/c/112204/18:47
stevemardolphm, hey18:47
morganfainbergi'm fine with 404ing in this case now since the user_id mapping happened18:47
stevemarthx18:47
dolphmdstanek: ++18:47
dolphmmorganfainberg: ++18:47
bknudsondstanek: test writers?18:47
morganfainbergdolphm, it changes the landscape some.18:47
stevemarso, i tossed up some code for emitting notifications for role_assignments18:47
stevemarhttps://review.openstack.org/#/c/112204/18:47
stevemari'd appreciate some reviews :)18:48
stevemarand for dolphm - do you want a spec/bp/bug for this?18:48
dolphmstevemar: no spec for weird public api notification format? :P18:48
stevemardolphm, it's not all that different18:48
dolphmi think notifications are a public api that is severely undocumented in openstack, i just want to make sure we're not contributing to that mess18:49
gyeestevemar, I thought you should get a purple heart for modifying the notification payload :)18:49
stevemargyee, hooray18:49
dolphmstevemar: weird = arbitrary and clients needs to understand it and for it to be stable18:49
stevemaryeah it was a mess earlier18:49
stevemardolphm, i agree the docs suck atm18:49
stevemardolphm, i was just going to add a small bit of info18:49
stevemardolphm, but if you want me to overhaul them, i cans18:50
dolphmstevemar: as long as we're documenting what we're doing and holding ourselves to it?18:50
gyeestevemar, but why stop at role assignment? it should be for any sort of updates18:50
*** ivar-lazzaro has joined #openstack-meeting18:50
lbragstadwe'll need a new notifications wrapper class for each kind of update?18:50
jamielennoxstevemar: i know there was compaints from jogo and nova that these notifications conform to a stable api18:50
dolphmgyee: role assigment is just an odd one, because there's not a resource entity in the picture18:51
stevemargyee, role assignments in particular were weird, cause it has multiple entities being affected18:51
gyeelbragstad, yes, right now we can't tell what's being updated18:51
stevemaryeah ^18:51
gyeeonly the resource ID  is not good enough18:51
stevemargyee, yeah, cause you don't know what the role is being assigned to, and on what project18:51
dolphmyou could almost emit 3 notifications :-/18:51
stevemar(or domain)18:51
stevemardolphm, nope!18:51
dolphmbut i'd rather bring it back to the use case - who's going to consume the notifications and what do they care about?18:52
gyeesay PATCH /users/user_id, how can we tell which fields are being updated?18:52
*** gokrokve has joined #openstack-meeting18:52
dolphmgyee: why do you need to know which fields were updated?18:52
HaneefWhich openstack service care about role assigments?  Are we concerned about delete role_assignment18:53
dolphmgyee: don't you just care about what the new entity looks like?18:53
stevemardolphm, for auditing i would think. it's one of those things an admin should be able to watch with ceilometer18:53
dolphmHaneef: delete assignment is sort of handled by token revocation events18:53
dolphmHaneef: but for auditing, crud all the assignments18:53
gyeedolphm, yes, even as simply as changing email cause a bunch of changes behind the scene18:54
dolphmstevemar: so let's write a short spec on the perspective that an auditor cares about?18:54
*** kentwu has quit IRC18:54
*** MarkAtwood has joined #openstack-meeting18:54
stevemardolphm, alright18:55
*** banix has quit IRC18:55
stevemardolphm et all, i'd still appreciate code reviews! :)18:55
dolphm#topic open discussion18:56
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:56
dolphmYAY 5 MINUTES LEFT18:56
*** Ajaeger has joined #openstack-meeting18:56
bknudsonI proposed a minor change to JSON Home spec based on Anne Gentle's feedback: https://review.openstack.org/#/c/113413/18:57
bknudsonthis is the location she suggested for the relationship link so that we could potentially publish something there18:57
dolphmbknudson: ++18:57
ajayaadolphm, What do I need to pay if I changed status of a bug by mistake?18:58
bknudsonit's not required by json home to have the links lead anywhere, but it's something we could do eventually18:58
*** ignacio-scopetta has joined #openstack-meeting18:58
dolphm'18:58
*** ignacio-scopetta has quit IRC18:58
topolbknudson thats a cool option to have18:58
*** ianw has joined #openstack-meeting18:58
*** vivek-eb_ has quit IRC18:58
* dolphm liquid-keyboard interaction incident18:58
*** ignacio-scopetta has joined #openstack-meeting18:58
topoldolphm any sparks???18:58
bknudsonso now I'm also working on refactoring the JSON Home code so that it's easy to change the relationship link18:59
bknudsonremoving duplication18:59
dolphmtopol: this isn't a thinkpad18:59
*** jtomasek_ has joined #openstack-meeting18:59
*** ianw has left #openstack-meeting18:59
*** ianw has joined #openstack-meeting18:59
stevemardolphm, thinkpads are bullet and water proof18:59
dstanekstevemar: that's because it's a brick19:00
*** brich1 has quit IRC19:00
*** penick has quit IRC19:00
bknudsonI'm guessing there won't be further oslo libs published in J19:00
*** trey_h has quit IRC19:00
bknudsonso the oslo.utils one is probably the last19:00
dolphmoop, time19:01
dolphm#endmeeting19:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:01
openstackMeeting ended Tue Aug 12 19:01:11 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-08-12-18.02.html19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-08-12-18.02.txt19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-08-12-18.02.log.html19:01
dolphmdstanek: ++++19:01
*** trey_h has joined #openstack-meeting19:01
*** jamielennox has left #openstack-meeting19:01
*** rockyg has joined #openstack-meeting19:01
*** wenlock has joined #openstack-meeting19:01
jeblairhello infra folks?19:02
fungihey-o!19:02
nibalizero/19:02
pleia2o/19:02
wenlockhi19:02
anteayao/19:02
SergeyLukjanovo/19:02
ianwo/19:02
emaganahi all.. new guy here!19:02
*** lsmola2 has joined #openstack-meeting19:02
*** MaxV has quit IRC19:02
nibalizerwelcome!19:02
pleia2welcome emagana :)19:02
jesusauruso/19:02
grantbowalso new here, hi19:02
jeblair#startmeeting infra19:02
openstackMeeting started Tue Aug 12 19:02: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:02
swestono/19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: infra)"19:02
openstackThe meeting name has been set to 'infra'19:02
*** johnpur_ has joined #openstack-meeting19:02
emaganathanks!19:02
pleia2welcome grantbow19:02
jeblair#link agenda: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:02
clarkbo/19:02
*** hashar has joined #openstack-meeting19:02
jeblair#link previous meeting: http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-08-05-19.02.html19:02
jeblair#topic Puppet module Split out (jesusaurus/nibalizer)19:03
*** openstack changes topic to "Puppet module Split out (jesusaurus/nibalizer) (Meeting topic: infra)"19:03
nibalizerokay so i guess we decided some stuff last time that i forgot19:03
*** ngoswami has quit IRC19:03
nibalizerbut sounds like step 1 is to split out a guniea pig19:03
nibalizerso i can do that with storyboard19:03
*** reed has quit IRC19:03
jeblairi probably should use the agree command more19:03
* krotscheck perks up.19:04
nibalizerjeblair: you had no chance, i had to do wedding stuff(not mine) last week so my brain was fried19:04
*** johnpur has quit IRC19:04
*** johnpur_ is now known as johnpur19:04
*** pdmars has quit IRC19:04
nibalizerkrotscheck: so yea your patches that haven't landed, we can pivot those to be applied to the new storyboard module19:04
pleia2nibalizer: btw, once the guinea pig is done, you're welcome to add me to people who can help with splitting out modules19:04
krotschecknibalizer: Works for me.19:04
nibalizerthe puppet-storyboard projcet has already been created so thats easy19:04
jeblairwe didn't land the big storyboard refactor?19:04
jesusauruspleia2: awesome :)19:04
krotscheckjeblair: We did.19:04
krotscheckjeblair: We’re now building on that.19:04
nibalizeri think we should have a little discussion about acls19:04
jeblairah cool19:04
nibalizerjeblair: ya krotscheck is a machine19:05
jedimikehi19:05
nibalizeri.e. does infra-core retain the +2+a on the modules19:05
swestonplease add me to the list of people who can help with the module split as well.19:05
nibalizeror do we give it krotchchek on the storyboard module?19:05
mordredyes19:05
*** SergeyLu_ has joined #openstack-meeting19:05
*** rcarrillocruz has joined #openstack-meeting19:05
*** SergeyLu_ is now known as SergeyLukjanov219:05
jeblairkrotscheck, nibalizer: does the new refactor work?  ie, is it stable enough for us to pivot to now?19:05
*** trey_h has quit IRC19:05
* SergeyLukjanov2 lurking19:05
krotscheckjeblair: It’s currently in use.19:05
krotscheckjeblair: But there’s one thing left that....19:06
nibalizerjeblair: that ^^19:06
*** marekd has left #openstack-meeting19:06
jeblaironce we approve https://review.openstack.org/#/c/99990/ we will make a story for each module19:06
*** igordcard has quit IRC19:06
jeblairand then all the folks that want to volunteer can assign that story to themselves19:06
krotscheckjeblair: Well, there’s one remaining patch that I want to land to make it “stable"19:06
pleia2jeblair: great19:06
jeblairs/that story/those stories/19:06
*** rcarrill` has quit IRC19:07
jeblairnibalizer: can we land that first, then focus on catching the external module up?19:07
krotschecknibalizer jeblair: This one - https://review.openstack.org/11361619:07
nibalizerjeblair: lets land krotchekcs patch for stability19:07
*** vjay has quit IRC19:07
nibalizerthen catch the external module up19:07
jeblair#agreed land https://review.openstack.org/113616 to internal storyboard module, then begin moving to external module19:07
*** mchalla has quit IRC19:08
nibalizerwoot19:08
anteayanice use of agreed19:08
*** mchalla has joined #openstack-meeting19:08
*** jkremer has quit IRC19:08
*** rcarrill` has joined #openstack-meeting19:08
jeblairanything else on this?19:09
zaroo/19:09
* krtaylor notices "agreed", hm I'll have to use that..19:09
nibalizerjeblair: acls?19:09
jedimikeo/19:09
jeblairheh, i guess we should expand on mordred's answer to that :)19:09
mordred:)19:10
*** kentwu has joined #openstack-meeting19:10
nibalizeroh did mordred say something?19:10
*** ksavich has quit IRC19:10
jeblairnibalizer: infra-core will have +2 on all openstack-infra/ projects (including these)19:10
nibalizeroh he said yes19:10
*** annegent_ has quit IRC19:10
anteayanibalizer: if you need help with the acl in the patch, let me know, I can help you19:10
nibalizeranteaya: okay19:10
nibalizeraight sweet then i think im good on this topic19:11
jeblairnibalizer: once they are split out, we can consider giving folks +2 on individual projects19:11
nibalizerjeblair: cool19:11
*** pdmars has joined #openstack-meeting19:11
*** rcarrillocruz has quit IRC19:11
*** jckasper_ has joined #openstack-meeting19:11
jeblairbut probably not right away, so for sanity sake, i'd just put infra-core in the acl files for now19:11
fungiwe generally accomplish that, as needed, by modifying the acl to use a new core reviewer group and have it include the infra-core group19:11
jeblairfungi: ++19:11
jeblair#topic Project renames (flaper87,jraim)19:12
*** openstack changes topic to "Project renames (flaper87,jraim) (Meeting topic: infra)"19:12
SergeyLukjanov2I'd like to do this renaming19:12
jeblairSergeyLukjanov2: i'd like that too! :)19:12
Ajaegerhttps://review.openstack.org/#/c/113614/ and https://review.openstack.org/#/c/111244/ are also renames19:12
fungiflaper87 wasn't going to be around for the meeting sounded like, but said something to the effect of "the sooner the better"19:12
AjaegerRename Marconi to Zaqar19:12
fungiAjaeger: yep19:13
*** mchalla has quit IRC19:13
Ajaegerand just pushed: Move openstack-security-notes to attic19:13
SergeyLukjanov2ack19:13
jeblairAjaeger: cool, can you add that to https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Project_Renames19:13
fungii tacked on jraim so we could get some clarification on whether the kite rename should also include python-kiteclient19:13
jeblairjraim: ping19:13
Ajaegerjeblair: will add directly19:13
jeblairfungi: i think i was catching us up to the governance repo19:14
fungibut wasn't able to get jraim's attention earlier, so he's probably also not around at the moment19:14
*** jckasper has quit IRC19:14
jeblairfungi: and kiteclient isn't in there19:14
fungijeblair: yep, i figured that out from the wiki history19:14
jeblairbug that sort of suggests the question of whether that was an omission from the gov repo19:14
fungimainly wanted to sync up on whether it should be, and whether we should delay the kite rename until it happens19:14
fungiso that they get renamed at the same time19:15
fungiso anyway, it sounds like maybe just the marconi and security notes renames are ready to go in near term19:15
SergeyLukjanov2yup19:16
*** kentwu has quit IRC19:16
jeblairyeah, let's keep trying to get clarification on that, and defer kite until we do19:16
clarkb++19:16
*** otherwiseguy has joined #openstack-meeting19:16
fungiwho has dates/times they really want to avoid? should we do friday pst afternoon? earlier?19:16
SergeyLukjanov2so, here is the guide for renaming - http://ci.openstack.org/gerrit.html?highlight=rename#renaming-a-project am I right?19:16
fungiSergeyLukjanov2: yep. it may or may not be 100% current, but it's close19:17
jeblairSergeyLukjanov2: yep; we'll make sure at least one other person is there with you to double check19:17
SergeyLukjanov2I'd like to avoid my sunday (your sat/sun night)19:17
jeblairwe keep finding that little things have changed19:17
SergeyLukjanov2I think there were no changes in gerrit since last renaming, so, it should be going good19:17
clarkbfriday is ard for me but early saturday morning pst should be ok19:17
fungiSergeyLukjanov2: generally we try to put together an etherpad with the timeline and cut+paste of the grittier commands so they can be peer reviewed19:18
*** trey_h has joined #openstack-meeting19:18
fungialso we want to make sure the pending rename commits are fully reviewed and current (not in need of rebases)19:18
jeblairSergeyLukjanov2: what's the latest time friday that would be okay for you?19:18
*** mrmartin has joined #openstack-meeting19:18
SergeyLukjanov2early sat morning is ok for me19:18
SergeyLukjanov2let me calc re friday19:18
SergeyLukjanov2so, I'm UTC-419:19
jeblairclarkb: 1600 utc saturday okay?19:19
* clarkb does math19:19
clarkbthat is 9am? that should work19:19
*** andreykurilin_ has quit IRC19:19
SergeyLukjanov2and 3 am is time when I'm falling asleep19:19
*** ngoswami has joined #openstack-meeting19:19
clarkbfungi: will you be around?19:19
SergeyLukjanov21600 utc saturday is ok for me too19:20
fungilooks like that's 8pm SergeyLukjanov2's time?19:20
* clarkb is wondering how many schedules we are trying to juggle?19:20
fungiclarkb: i'm fine with it19:20
SergeyLukjanov2correction: UTC+4 :)19:20
clarkbcool why don't we aim for then then?19:20
jeblair#agreed project renames 1600 utc aug 1619:20
SergeyLukjanov2ok, sounds like we agreed in 1600 utc saturday19:20
*** scottda__ has joined #openstack-meeting19:20
SergeyLukjanov2:)19:20
*** leonchio__ has joined #openstack-meeting19:21
jeblairdid i get that right? :)19:21
*** leonchio_ has quit IRC19:21
SergeyLukjanov2I'll prepare etherpad tomorrow and share with you folks19:21
SergeyLukjanov2jeblair, I think so ;)19:21
fungiSergeyLukjanov2: i can get you links to earlier ones if you need examples19:21
SergeyLukjanov2fungi, it'll be great, thanks!19:21
jeblair#topic Publish python-jenkins 0.3.3 (last release without pbr) tarball to pypi. (zaro)19:21
*** openstack changes topic to "Publish python-jenkins 0.3.3 (last release without pbr) tarball to pypi. (zaro) (Meeting topic: infra)"19:21
*** stevemar has quit IRC19:22
jeblairzaro: so 0.3.3 fixes the issues with 0.3.1?19:22
zaroyes, it does.19:22
jeblair#action jeblair Publish python-jenkins 0.3.3 (last release without pbr) tarball to pypi19:22
zarolast one without pbr19:22
fungithat's a manual upload too, right?19:23
jeblairfungi: yup19:23
jeblairprevious one had a bug, so sort of defeated the purpose :(19:23
jeblair(of having a published version before we went and changed _lots_ of stuff)19:24
zarocool, end of topic i guess.19:24
jeblair#topic  Administering third party ci gerrit accounts: setting http passwords (anteaya)19:24
*** openstack changes topic to "Administering third party ci gerrit accounts: setting http passwords (anteaya) (Meeting topic: infra)"19:24
*** e0ne has quit IRC19:24
anteayahi19:24
anteayaso there was an email thread19:25
jeblair#link19:25
jeblairhttp://lists.openstack.org/pipermail/openstack-infra/2014-August/001685.html19:25
anteaya#link http://lists.openstack.org/pipermail/openstack-infra/2014-August/001685.html19:25
anteayathanks19:25
jeblairnope, you got it right :)19:25
anteayaand there is the ability for gerrit admins to set an http password for third party cis19:25
anteayavmware would like a password19:25
jeblairwhy?19:25
anteayafrom the email: We are looking to use some of the Gerrit REST API operations that require authentication19:26
jeblairwhich ones?19:26
anteayathat is all I have for the why19:26
anteayaryan was going to try to be here at the meeting19:26
anteayaI have forgotten his irc nick19:26
anteayaI don't know which ones19:26
anteaya:(19:26
*** gokrokve has quit IRC19:26
*** mestery has joined #openstack-meeting19:27
zaroyou don't need admin to create http password.19:27
anteayafor third party ci?19:27
anteayawhich don't have gui access?19:27
zaroi believe account holder can do themself19:27
anteayavia ssh?19:27
*** johnpur_ has joined #openstack-meeting19:27
zaroohh, sorry. didn't realize no UI access.  then no they cannot.19:27
jeblairi don't think there's a good way for us to set those without actually knowing the passwords.  and i don't want us to become the password reset help desk any more than we already are.19:28
anteayaokay yes, so they can't by themselves19:28
anteayakk19:28
jeblairso i think there's a pretty high bar for deciding this is a good idea19:28
* anteaya nods19:28
fungiespecially when they can just use a normal account to make rest api queries19:28
SergeyLukjanov2++19:28
jeblairalso, third-party ci only needs to do two things authenticated, and ssh access permits both19:28
clarkband the ssh api exposes all the things too19:28
clarkbjeblair: ++19:29
*** vponomaryov1 has joined #openstack-meeting19:29
anteayaokay so I will share the meeting logs in response to the email and if he needs more air time hopefully he will attend in future19:29
anteayathanks19:29
anteayaI'm done19:29
jeblairanteaya: thank you!19:29
jeblair#topic  Bug Day proposal: August 19th, alt suggestions: August 26th, September 9th (pleia2)19:29
*** openstack changes topic to "Bug Day proposal: August 19th, alt suggestions: August 26th, September 9th (pleia2) (Meeting topic: infra)"19:29
*** johnpur has quit IRC19:30
*** johnpur_ is now known as johnpur19:30
pleia2so I noticed our bug numbers creeping up and tossed some dates out19:30
AjaegerFYI, September 9th the Documentation team will do a Bug day - but that's not a conflict IMHO19:30
pleia2(skipped labor day week)19:30
clarkbnext week is hard for me particularly with the trusty and tox switches coming up19:30
clarkbI would +1 the 26th19:30
fungi26th sounds great to me19:30
anteayaI'm better on the 26th19:31
jeblair++2619:31
pleia2great19:31
SergeyLukjanov2++2619:31
pleia2should we incorporate storyboard projects into this bug day?19:31
jeblairmordred: do you think we'll be able to import by then?19:31
pleia2I don't actually know anything about storyboard's API for writing a script (it has one, right? :))19:31
mordredyes19:31
mordredjeblair: I'm finishing off teh import script right now19:31
fungido we normally incorporate anything besides the openstack-ci project bugs?19:31
mordredhttps://review.openstack.org/113624 fwiw19:31
pleia2fungi: well, storyboard has some of our projects that were origially openstack-ci on launchpad19:32
fungipleia2: oh, yeah makes sense then19:32
clarkbit might be a good way to kick the tires on storyboard too19:32
*** annegent_ has joined #openstack-meeting19:32
pleia2clarkb: that's what I'm thinking19:32
*** yamamoto has joined #openstack-meeting19:32
pleia2I haven't actually done anything with storyboard aside from reading it :)19:32
*** aswadr has quit IRC19:32
*** ramashri has quit IRC19:32
fungistoryboard tire-kicking day ;)19:32
nibalizerpleia2: i created a test story19:33
mordredwell, krotscheck and I will both be not here19:33
nibalizerthen found out you cant delete them :/19:33
pleia2nibalizer: haha, oops19:33
rcarrill`nice19:33
anteayaoh yeah krotscheck will be honeymooning19:33
krtaylorthats good to know19:33
pleia2ok, so maybe bump storyboard tire kicking until next time19:33
krotscheckwhich is slightly different from mooninhoneys19:33
anteaya:D19:33
rcarrill`lulz19:33
pleia2krotscheck: also, congrats :)19:34
jeblairi think we can kick storyboard's tires19:34
rcarrill`yeah, congrats19:34
krotscheckWell, y’all can hit as many bugs as you want to, and file them as stories, just don’t expect much movement on them.19:34
fungii'm fine with it, as long as the tires don't kick back19:34
pleia2alright19:34
*** stevemar has joined #openstack-meeting19:34
jeblairi'm not interested in using launchpad anymore for infra bugs; it's time to start really using storyboard19:34
pleia2all the bugs for when krotscheck returns \o/19:34
mordredjeblair: script almost done!19:34
mordredkrotscheck: btw - I found a bug in StoryTags19:34
*** rediskin has left #openstack-meeting19:34
pleia2so is there a way to query storyboard from a script?19:35
clarkbjeblair: ++ we haev to switch at some point and every time I have used storyboard I have been happy19:35
rcarrill`curl?19:35
*** dwalleck has quit IRC19:35
jeblair#agreed bug day august 26 (and bugs will be imported into storyboard by then)19:35
*** SergeyLukjanov2 has quit IRC19:36
ttxpleia2: curl would work, although i would love if someone would work on python bindings19:36
mordredpleia2: python-storyboardclient is a TDL item19:36
pleia2ok19:36
pleia2well, I'll come up with something19:36
ttxcan't be worse than launchpadlib anyway :)19:36
rcarrill`haha19:36
rcarrill`indeed19:36
jeblairpleia2: thanks!19:37
krotscheckOh man, I’m glad I created a sorting patch :)19:37
mordredZOMG launchpadlib19:37
jeblair#topic Refactor of artifact upload scripts (rcarrillocruz)19:37
*** openstack changes topic to "Refactor of artifact upload scripts (rcarrillocruz) (Meeting topic: infra)"19:37
rcarrill`that's me19:37
ttxwell, to be fair launchpadlib is decent. It's launchpad APi that is horrible :P19:37
rcarrill`#link https://review.openstack.org/#/c/109816/19:37
rcarrill`i've been chatting with fungi and clarkb about this19:37
rcarrill`and also chatted with jeblair at mid-cycle sprint19:37
*** yamamoto has quit IRC19:37
rcarrill`i'd like to get consensus on the change19:37
rcarrill`should it be a refactor for just java things?19:38
rcarrill`or are we open to have a generic framework/script to uplod all sorts of artifacts?19:38
rcarrill`pypi19:38
rcarrill`wheels19:38
rcarrill`jenkins19:38
rcarrill`maven19:38
rcarrill`...19:38
jeblairrcarrill`: as i recall, it was mostly the java stuff that you needed to consolidate for your use-case, right?  so either will work for you?19:38
jeblairconsolidate and genericize19:39
rcarrill`yes, but clarkb says he's not very keen on having a monolithic script for all kind of artifacts19:39
rcarrill`i.e. not -t ARTIFACT_TYPE19:39
clarkbmy opposition to doing everything in a giant complicated script is that we have been very unixy so far and makinga one size fits all script is not how anything else works there19:39
*** _nadya_ has joined #openstack-meeting19:39
fungircarrill`: i think most of those other artifact types use widely varying tools/commands to prepare and upload, and the script wouldn't really do much in common ultimately19:39
jesusaurusi agree with clarkb that we should have the One Way to do maven, then a different One Way to do pypi19:39
jeblairclarkb: but there's some commonality in the download part yeah?19:40
fungifor most of them, the bulk of the duplication we'd avoid would be in the license boilerplate comment block19:40
jeblairclarkb: i'm guessing you'll say "have a download script, and N upload scripts" :)19:40
rcarrill`yes19:40
clarkbjeblair: yes, the download part has some commonality. the difference are in the upload to $repo19:40
clarkbjeblair: that would be fine19:40
*** ArxCruz has quit IRC19:40
rcarrill`to be fair, i think we could have a common artifact upload thingy , but bash is not the way to go19:40
AjaegerIs there a way to create a library that can be included for some common functions?19:40
rcarrill`so, imho we could just have my change for java stuff19:40
rcarrill`and then we can work on something on later that is more flexible than bash19:40
*** shashankhegde has quit IRC19:41
fungiyeah, it seems like maven nexus and jenkins-ci are probably similar enough that they benefit19:41
clarkbfungi: they are the same thing. the only differences are nexus location and filenames19:41
rcarrill`agreed on having the change on just nexus, and upload either java package OR jenkins package? that way no point of differentiating if the stuff is jenkins of java19:41
rcarrill`clarkb: ^, yup, i agree with you19:42
jeblairAjaeger: yes, that would be possible19:42
rcarrill`after our chat last week, i give you that19:42
jeblair(so the download part could be 'sourced')19:42
fungircarrill`: yeah, could probably branch on the filename extension and not need explicit artifact type parameters even19:42
zaronot exactly the same, jenkins-ci is artifactory while maven central is nexus.19:42
*** eglynn has joined #openstack-meeting19:42
rcarrill`but curl one-liner would work the same, not zaro?19:43
zarofor download only i think19:43
*** annegent_ has quit IRC19:43
zarofor maven central (nexus) they employ a two step upload process.19:43
rcarrill`zaro: could I work with you on that?19:43
zaroyes.19:43
rcarrill`it's a PITA to open an account myself for testing19:43
rcarrill`we could just use openstack-infra account for that19:44
*** _nadya_ has quit IRC19:44
zaroyou'll need the password.19:44
rcarrill`iirc, oss sonatype site requires an approval process to get an account19:44
rcarrill`it's not something immediate to get19:44
fungircarrill`: right, you have to open a jira ticket19:44
zarojust do it!19:44
fungiand then wait for them to process it19:45
rcarrill`anyways, overall the change looks good?19:45
rcarrill`pulling the -t switches19:45
fungi(not entirely unlike our third-party ci service account request workflow)19:45
rcarrill`and just copying .hpi / .jar artifacts19:45
rcarrill`?19:45
zaronow that i think about it. i don't think it will work for maven central.19:45
zaroyou need to upload then do another request to "approve" to actually publish it.19:46
*** AlanClark has joined #openstack-meeting19:46
zaroanyways. i'll review again.19:46
clarkbrcarrill`: ya overall it is fine. I think we should just rip out the branch logic19:46
*** ayoung has joined #openstack-meeting19:46
rcarrill`cool19:46
*** e0ne has joined #openstack-meeting19:46
jeblair#topic  Process to deprecate drivers/plugins and their corresponding CIs (emagana)19:47
*** openstack changes topic to "Process to deprecate drivers/plugins and their corresponding CIs (emagana) (Meeting topic: infra)"19:47
zaroohh, i agree with clark there as well.19:47
emaganahi19:47
rcarrill`we have a deal then19:47
emaganaJust wondering if there is a process in place to deal with the plugins/drivers that are being deprecated19:47
rcarrill`zaro: will make another patchset and ping you then19:48
emaganaas well as the process to deprecate them if they do not have a CI19:48
jeblairemagana: what plugins/drivers are being deprecated?19:48
emaganain Neutron: OVS, LB, NXOS19:48
fungiemagana: that's more a decision on the part of the projects in which those drivers exist or integrate19:48
emaganajeblair: maybe more19:48
fungiso in that case, neutron19:48
emaganafungi: understood!19:48
*** david-lyle has quit IRC19:49
fungiif there are third-party ci systems which correspond with them and are being taken offline as well, we appreciate a heads up so we can disable their service accounts19:49
jeblairyep, and the wiki pages for them should be updated too19:49
emaganafungi: That is the kind of guidence I am looking for19:49
*** david-lyle has joined #openstack-meeting19:49
emaganaI am planning to run an audit for the plugins/drivers CI19:49
emaganaI know, I will not have many friends19:50
*** marun has quit IRC19:50
emaganaThe idea is to be sure that all drivers/plugins are being tested properly19:50
clarkbemagana: ++19:50
*** marun has joined #openstack-meeting19:50
jeblairemagana: that would be awesome; thanks19:51
krtayloremagana, what is the output of the audit?19:51
*** vhoward has joined #openstack-meeting19:51
emaganaI will update NeutronPolicies for Plugin and Drivers with the results: https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers19:51
krtayloremagana, understood19:51
emaganakrtaylor: ensure quality! and deprecated anything that is not being properly tested19:52
krtayloremagana, feel free to bring this up in the next third-party meeting as well, we can spread the news19:52
*** david-ly_ has joined #openstack-meeting19:52
emaganaThanks!19:52
emaganaok, will provide results next week19:52
jeblair#topic  Open discussion19:52
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:52
emaganathat is all I wanted to share about this19:52
*** julienvey has joined #openstack-meeting19:52
jedimikeo/19:52
jeblairanteaya: what's the status of account renames?19:53
emaganajeblair: I have a question about Multi-node testing19:53
anteayaright now I am hoping either you or someone else can help me append CI to the end of them all19:53
*** dwalleck has joined #openstack-meeting19:53
jedimikeI have a small nodepool feature I'd like to run by you all19:53
anteayathen we can merge teh js patch19:53
jeblairanteaya: can you prepare an etherpad with a list of the names?19:53
anteayaafter I get gerrit permissions then go through them and chance the name19:53
*** david-lyle has quit IRC19:53
anteayajeblair: oh goodness I have been working on it for 3 months19:53
jeblairanteaya: yeah, that's too long.  i'm ready to just name them myself.19:54
clarkbanteaya: I think we need a clear old name to new name map19:54
anteaya#link https://etherpad.openstack.org/p/automated-gerrit-account-naming-format19:54
anteayajeblair: go for it19:54
clarkbthen whoever can do it.19:54
anteayaif you want it I will support you and clean up afterward19:54
jedimikeWe've been having some problems with nodepool and the ready-script recently. Our ready-scripts do some nice things like update git repos, set hostnames, but because we generate our images every night, they're not absolutely essential.19:55
jeblairi will tend to give them _very bad names_19:55
jedimikeSo we'd like to have an option that lets us tolerate errors in the ready-script, so if it fails to run, the node is still used.19:55
*** SumitNaiksatam has quit IRC19:55
*** esker has joined #openstack-meeting19:55
jeblairlike "Unknown Function Third Party CI"19:55
anteayajeblair: there are no names they will like19:55
clarkbjedimike: the whole point of a ready script imo is to make sure the node is ready. if it fails the node is not ready.19:56
clarkbjedimike: tolerating failures should happen in the script19:56
emaganajeblair: During the Neutron mid-cycle sprint in Minnesota, we discussed the need for having a Multi-node testing environment, specially for DVR (Distributed Virtual Router). So, I created a spec in Infra: https://review.openstack.org/#/c/106495/19:56
anteayajeblair: do it, they will yell at me and I will take it19:56
*** VijayB has quit IRC19:56
anteayaand I don't have to keep thinking about how to make everyone happy, because I can't19:56
jeblairjedimike: yeah, i think updating git repos is probably not something that should be in a ready script19:56
jedimikeclarkb, yes, but sometimes nodepool just isn't running the script, and because it doesn't log anything useful when it fails to run the ready script, we've had days where no jobs are running and we don't know why, and our scripts run fine as far as we can see19:57
emaganajeblair: I just wanted to know if you have this cover by a different spec.. anteaya recommended to bring this question here19:57
jedimikeI have a patch currently in review to fix that though, https://review.openstack.org/#/c/113287/19:57
*** resker has joined #openstack-meeting19:57
jeblairjedimike: well, "just not running the script" is a pretty clear bug :)19:57
fungijedimike: we do it in our prep scripts instead, and then pull whatever has changed that day at the start of jobs19:57
*** gokrokve has joined #openstack-meeting19:57
*** AlexF has joined #openstack-meeting19:57
*** esker has quit IRC19:57
fungirather than when the node goes ready19:57
jeblairjedimike:  part of the reasoning for that is that nodes can sit in ready state for a long time19:57
*** shashankhegde has joined #openstack-meeting19:57
*** esker has joined #openstack-meeting19:57
jedimikei see19:57
clarkbemagana: there isn't another spec. afazekas is just doing the work19:57
jeblairso if you want something to be current, doing it at the start of the job is the best place19:58
*** Haneef has quit IRC19:58
clarkbemagana: it is something that was made possible months ago by a new nodepool featuer and no one did anything with it until afazekas stepped up19:58
jeblairjedimike: ++ on better logging19:58
emaganaclarkb: should we abandon the spec that I created and just let the work continue?19:58
jedimikejeblair, yeah, it's caused headaches that the scripts look fine, run fine when we run them, but nodepool just threw away stdout and stderr so we can't see what happened19:59
emaganaclarkb: I think afazekas could point his work to this spec19:59
clarkbemagana: I don't necessarily thing it needs abandoning as it does spell out the neutron use case. But I don't think the spec was required to start the work19:59
clarkbemagana: yup19:59
jedimikeso, I'll make a note to look at our ready scripts and see if they can be more minimal too, thanks19:59
*** rcallawa has joined #openstack-meeting20:00
anteayatime20:00
*** wenlock has left #openstack-meeting20:00
jeblairthanks all!20:00
jeblair#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Aug 12 20:00:32 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
emaganaclarkb: Ok, then I will encourage the whole team to review it. link# https://review.openstack.org/#/c/106495/20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-08-12-19.02.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-08-12-19.02.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-08-12-19.02.log.html20:00
*** e0ne has quit IRC20:00
ttxAnyone here for the TC meeting ?20:00
*** markmc has joined #openstack-meeting20:01
eglynno/20:01
russellbhello20:01
markmchey20:01
devanandao/20:01
jeblairo/20:01
*** resker has quit IRC20:01
ttxannegentle, mikal, mordred, vishy, markmcclain, jaypipes, sdague, dhellmann : around ?20:01
markmcclaino/20:01
*** jckasper__ has joined #openstack-meeting20:01
ttxI think sdague is in vacation20:01
*** tkay has joined #openstack-meeting20:01
annegentleo/20:01
jaypipeso/20:02
*** bswartz1 has joined #openstack-meeting20:02
dhellmanno/20:02
*** gangil has joined #openstack-meeting20:02
*** gangil has joined #openstack-meeting20:02
ttxOK, we have quorum, let's start20:02
bswartz1hi20:02
ttx#startmeeting tc20:02
openstackMeeting started Tue Aug 12 20:02:14 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: tc)"20:02
bswartz1stupid wireless issues20:02
openstackThe meeting name has been set to 'tc'20:02
ttxThe agenda for today:20:02
*** amotoki has quit IRC20:02
eskervarious Manila interested parties here as well..20:02
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:02
ttxdolphm: around?20:02
ttx#topic Identity program scope and rename, take 220:02
*** openstack changes topic to "Identity program scope and rename, take 2 (Meeting topic: tc)"20:02
*** jedimike has quit IRC20:03
*** IanGovett1 has quit IRC20:03
ttxWe had that discussion two meetings ago, it's still a bit stalled20:03
ttxIt's in two parts20:03
ttx1. Expand scope of the Identity program to include auditing (https://review.openstack.org/109664)20:03
ttxSo this one hasn't reached the majority threshold yet, although it has enough votes to pass a simple vote20:03
*** lsmola3 has joined #openstack-meeting20:03
ttxIt's about moving pyCADF to keystone program and tweaking the mission to reflect that20:03
*** stevemar has quit IRC20:03
ttxThere haven't been enough votes cast on this one, but I don't feel we should block it any longer.20:03
*** bswartz has quit IRC20:03
ttxespecially with both PTLs involved approving it20:04
*** timcl has joined #openstack-meeting20:04
dhellmannyeah, the teams involved with that code agree to the move20:04
ttxSo I'm calling for final vote on that one -- Please vote on this, otherwise it will pass just because it has 5 +1s and more +1s than -1s20:04
devanandaI'm curious how this changes the requirement for projects to integrate with keystone20:04
*** jckasper_ has quit IRC20:04
*** bswartz1 is now known as bswartz20:04
*** MarkAtwood has quit IRC20:04
ttx(I probably won't pick up the votes before tomorrow though)20:04
devanandado all projects now have to integrate with pycadf, if it is part of keystone?20:04
russellbit's not part of keystone :)20:04
russellbit's part of the identity program (proposed)20:04
dhellmanndevananda: AIUI, some keystone middleware will use it20:05
ttxthey are just taking over maintenance20:05
zanebrussellb: "Identity:codename: Keystone"20:05
*** rkofman has joined #openstack-meeting20:05
russellbzaneb: heh, fair20:05
annegentledevananda: well, swift already has ways to be used without keystone20:05
ttxThe second part is: Rename the "Identity" program (https://review.openstack.org/108739)20:05
ttxNow this part is not nearly as popular.20:05
annegentledevananda: but yeah, it's a good question, are there dependencies inherited?20:05
ttxMy take on it is that it's encumbered with the various ways we reuse program names for the moment20:06
devanandaannegentle: right20:06
*** lsmola2 has quit IRC20:06
ttxSo I would rather table any program rename until we have come to a point where a program short name really no longer applies to a program20:06
ttxIn this case it's close enough, I think20:06
ttxand we have more pressing issues to address20:06
annegentleprogram renames are really tough for user-facing docs20:06
ttxSo I think it makes sense to abandon this one for the moment20:06
jaypipesttx: ++20:06
annegentleso I'm +120:06
dhellmannmaybe we should just use uuids instead of names20:06
annegentledhellmann: frowny!20:06
devanandattx: ++20:07
ttxso unless it magically gets 7 +1s oevrnight, i'll abandon this one20:07
*** ajayaa has quit IRC20:07
*** bswartz1 has joined #openstack-meeting20:07
mikalHi, sorry I'm here20:07
ttxother comments on that before we move on?20:07
annegentleI'm sorry you're here too :)20:07
zanebdhellmann: maybe we should just use the code names and stop with the parallel naming :)20:07
annegentlejust kidding mikal20:07
*** pdmars has quit IRC20:08
dhellmannzaneb: heh20:08
ttxzaneb: I'll work on that as soon as we have all the other problems in openstack solved20:08
ttxshould be sometimes next month20:08
annegentlezaneb: doit!20:08
annegentlettx: I like your timeline20:08
mordredo/20:08
ttxso, about that...20:08
ttx#topic Upcoming graduation reviews & future of the integrated release20:08
*** openstack changes topic to "Upcoming graduation reviews & future of the integrated release (Meeting topic: tc)"20:08
*** bswartz has quit IRC20:08
ttxwe have a busy schedule ahead, and I want to talk about how we can meet our deadlines20:08
ttxWe basically need to have Kilo contents wrapped up by September 16, so that we can plan the design summit AND get the official PTL election process started20:09
*** mchalla has joined #openstack-meeting20:09
ttxThat leaves 5 meetings to cover all graduation reviews. And one of them falls during Burning Man week20:09
ttxIf we don't count the recently-incubated projects and the current padawans, we have ironic, marconi, barbican to consider for addition20:09
*** SlickNik has joined #openstack-meeting20:09
*** dwalleck has quit IRC20:09
jeblairhow many people here will not be here during burning man week?20:09
ttxDuring the same time we have a couple of new program / incubation requests to wrap up (Rally, Manila)20:09
devanandattx: regarding that, this is my last TC meeting until 9/9. probably ditto for mordred.20:09
*** andreaf has quit IRC20:10
mordredyup20:10
ttxdevananda: so now it's burning man 3-week ?20:10
* anteaya notes the election process will start earlier than usual due to the new questions feature this round20:10
*** bswartz1 is now known as bswartz20:10
mordredttx: well, devananda and I go early and stay late because we feed people20:10
dhellmannanteaya: "questions"?20:10
devanandattx: yes. well. it's two weeks, but +travel and the meeting falling on tuesday20:10
ttxwe also need to have some serious discussion on what we want to do with the integrated release20:10
anteayabut timelines for nominations and so on will be teh same20:10
ttxand we may want to have that discussion *before* considering those graduations20:10
ttxDo you think we are on track, or do we need to add a few more meetings to clear things up ?20:11
jaypipes++20:11
devanandattx: I would *really* like to have that discussion without it side tracking to the (also very important) discussion on how to prioritize reviews20:11
anteayadhellmann: we talked aabout submission and curation of questions for tc candidates, for improved voter participation20:11
*** baoli has quit IRC20:11
dhellmannanteaya: ah, yeah, I just forgot20:11
mordreddevananda: ++20:11
anteayadhellmann: it is on my timeline to implment20:11
anteayadhellmann: np20:11
jaypipesttx: personally, the "wtf is the integrated release and why do we care so much about new programs" discussion needs to happen ASAP, IMO.20:11
mordredjaypipes: +20:11
mordred++20:11
mordredI mean20:11
ttxand I know mordred wants to be part of that one20:11
ttxso how do we solve this20:11
mordredthere are two different aspects - one of them is "how do we scale our resources" - but the other is "how do we ship good things"20:12
ttxI think it warrants its own meeting20:12
*** andreaf has joined #openstack-meeting20:12
markmcclainwould it make sense to call a single topic meeting?20:12
*** rcarrillocruz has joined #openstack-meeting20:12
russellbyes, its own meeting makes sense20:12
jaypipesttx: as do I. this week, preferably.20:12
mordredand I think they're both important, and I'm happy to show up at additional times myself20:12
*** kevinconway has quit IRC20:12
annegentledevananda: good point about separating20:12
*** vhoward has left #openstack-meeting20:12
ttxto discuss where we want to go and how much drastic measures are warranted20:12
markmcsingle topic meeting sounds good20:12
*** dwalleck has joined #openstack-meeting20:12
russellbthis week?20:12
dhellmann+1 to another meeting20:12
devananda++20:12
* dhellmann never thought he'd say that20:12
mordreddhellmann: right?20:12
annegentlenever hear me say this, but yes let's have an extra meeting20:12
*** kwss has quit IRC20:13
ttxmordred: if it's not this week, you will miss it?20:13
jaypipesrussellb: just cuz devananda and mordred are out until 9/920:13
jeblairi've been away for a few days; is there something very urgent i need to catch up on?20:13
russellbjaypipes: no no, i'm agreeing that let's knock it out asap20:13
ttxI guess I can find time out of my roof to make that happen this week20:13
jeblairi feel like the urgency of this topic is universally agreed to be high and i'm not sure why :)20:13
jaypipesjeblair: reading the whole "the future of the integrated release" ML thread...20:13
ttxotherwise monday sounded like a good idea20:13
annegentleI feel the urgency too20:13
markmcjeblair, I've been away too; just the thread AFAIK20:13
*** dwalleck has quit IRC20:13
jeblairjaypipes: thanks, i'll put at at the top of my list.20:13
mordredttx: deva and I could also figure something out if it's next monday, early next tuesday, or late the tuesday 3 weeks away20:13
annegentleand it's only Tues/Wed.20:13
jaypipesjeblair: it's a meaty one...20:13
*** MaxV has joined #openstack-meeting20:13
*** Ish__ has quit IRC20:14
russellbi just want it discussed and out of the way, so it doesn't get in the way of all of the project consideraions we need to do20:14
*** mchalla has quit IRC20:14
jaypipesrussellb: agreed.20:14
devanandaI would advise against late tuesday 3 weeks away20:14
ttxSo I'd propose 19:00 or 20:00 UTC, Monday. If that doesn't work, same hours, this Thursday20:14
dhellmannrussellb: +20:14
russellbi don't want several discussions stalled with "but we need to wait until we decide at the future of release discussion"20:14
mordredyes. that would be my least favorite choice20:14
devanandaif i'm doing aything, it'll be related to juno3 and feature freeze and nova integration20:14
devanandarussellb: ++20:14
*** rcarrill` has quit IRC20:14
mordredrussellb: ++20:14
ttxor we do Thursday and keep Monday as a backup extra session20:14
devanandattx: wfm20:14
dhellmannI like having a backup20:15
mordredit's POSSIBLE this one might be a longer discussion20:15
markmcclainThurs then Monday would be my preference20:15
russellbany time thursday is fine with me20:15
jaypipesme too.20:15
mordredthurs then monday ++20:15
* jaypipes will make time.20:15
jeblairthurs or mon is fine20:15
ttxI guess I can make Thursday work, but 19:00 UTC would have my preference then20:15
ttxbut I know thaat makes it difficult for mikal20:15
* mordred willing to show up whatever time is good for mikal and ttx20:15
russellbsame20:15
annegentleyeah me too20:15
ttxmordred: there is unfortunately no such good time20:16
mordredI know20:16
mikalI will come whenever20:16
mikalThis time is about the earliest I would voluntarily do20:16
markmcclainhappy show up when needed20:16
ttxit's either very early for him or very early for me :)20:16
mikal(Its 6:15am here)20:16
*** pdmars has joined #openstack-meeting20:16
ttxif there was a second "good time" we'd rotate :)20:16
anteayaWednesday at 1800 utc in this channel looks free20:16
* mordred hands mikal a recently blow-dried kitten20:16
russellbachievement unlocked: have a meeting about meetings20:16
mikalmordred: thanks?20:16
vishyo/20:16
ttx18.00 is really too early, not even convenient for me20:16
dhellmannrussellb: heh20:16
mikalSo yeah, this time slot on some other day of the week works20:16
markmcttx, do you have a sense of concrete suggestions from the thread that there might be reasonable consensus around?20:17
ttxThursday, 19:00 in #openstack-meeting-320:17
russellbmarkmc: i certainly don't20:17
*** MarkAtwood has joined #openstack-meeting20:17
markmcttx, agree with devananda that the thread seemed to have been derailed from issues directly related to adding new projects20:17
ttxmarkmc: not really. i want the first meeting to get people to shout problems and proposed solutions20:17
anteayathursday at 2000 utc all meeting channels open20:17
ttxthen use some time to digest them, and if we think there can be convergence, call another meeting to come up with something20:18
anteayawednesday at 2000 -alt and -3 open20:18
ttxeveryone OK for Thursday, 19:00 in #openstack-meeting-3 ?20:18
markmcttx, just wondering whether we can make real progress on list in preparation for the meeting20:18
annegentleis 19:00 UTC now?20:18
mordredwe may just have to bring our own brains20:18
* annegentle asks the dumb time questions20:18
mikalYep20:18
ttxannegentle: now is 20:18 UTC20:18
ttx20:1920:19
dhellmannannegentle: 3:00 Eastern20:19
ttx:)20:19
annegentleGot it, thanks20:19
jaypipes4 eastern.20:19
annegentleheh hm20:19
ttx#info Extra TC meeting on Thursday, 19:00 in #openstack-meeting-320:19
jaypipesoh, 1900UTC, yeah, 3 eastern20:19
devanandamarkmc: i think it was derailed from the topic of culling fail[ed/ing] projects, which is related to not adding new projects.20:20
ttx#info specific agenda: The need for change in integrated release for Kilo20:20
ttx(or absence thereof)20:20
ttxOK, next topic20:20
devanandamarkmc: and that the litmus we use when deciding to add new projects should be mroe than just "meets QA and release process standards"20:20
*** pdmars_ has joined #openstack-meeting20:20
russellbdevananda: the requirements list is already quite a bit more than that20:20
ttxFeel free to fire warning shots on that ML thread20:21
* dhellmann hopes anyone with specific goals makes them clear in that thread before thursday20:21
russellbi'd rather concrete suggestions / discussion than warning shots20:21
ttxalthough don't expect me to particiapte that much, I still need to rpetend I'm taking 3 days ofgf20:21
markmcdevananda, actually, that felt like a slight derailment from the original topic - that we're hitting scaling limits as we add new projects20:21
dhellmannrussellb: +120:21
ttxrussellb: yay, getting a bit more info on everyone's position on this could help20:22
*** pdmars has quit IRC20:22
ttxok, we need to move on20:22
ttx#topic Propose Manila for Incubation (initial discussion)20:22
*** openstack changes topic to "Propose Manila for Incubation (initial discussion) (Meeting topic: tc)"20:22
mordredmarkmc: I thought that the original topic presented the general issue in such a way that that seemed like the one and only topic at hand20:22
bswartzI'm still here -- wireless appears to have stabilized...20:22
mordredmarkmc: but I can try to express that better on the list20:22
ttxbswartz: o/20:22
ttxThe program application is at:20:22
*** Murali__ has joined #openstack-meeting20:22
ttx#link https://review.openstack.org/11114920:22
*** andreaf_ has joined #openstack-meeting20:23
ttxAnd the incubation application at:20:23
ttx#link https://review.openstack.org/#/c/113583/20:23
ttxManila was considered and application was rejected/delayed in the past20:23
*** flaper87 is now known as flaper87|afk20:23
*** Murali__ has quit IRC20:23
bswartzin November 2013 to be exact20:23
mikalttx: so, the disconnect here is strange to me. We have an issue of general policy (are we too big) which we've deferred, but we're not discussing an issue of specific policy (should we become bigger by adding a thing)20:23
mikalttx: shouldn't this conversation happen after the first one?20:23
ttxIncubation application has a pretty good account on what was said then20:23
ttxmikal: yes, at least final decision needs to20:24
mikals/not/now/20:24
*** Murali__ has joined #openstack-meeting20:24
devananda... what mikal said20:24
bswartzyeah we included an appendix in the incubation application answering questions raised last time20:24
ttxbut I figured we could still have a few early questions20:24
mikalNothing against Manilla20:24
ttxIf you feel like this is useless, we can skip though20:24
russellbthis is what i was afraid of ... deadlock until the other is resolved20:24
* jaypipes recommends skipping until we answer the bigger questions.20:25
mikalUseless is a bit strong20:25
mikalWell, we could talk it through but defer our decision20:25
eskerttx: the summary you'd issued from the November discussion on the topic "We would like to have Manila in OpenStack one day, needs more maturation, solve multi-tenant concerns and get devstack-gate integration before revisiting incubation request"20:25
mikalThat gives scope for if we have questions which need time to answer20:25
russellbwe need to move swiftly on the "big questions" so we don't leave all of these projects hanging though20:25
dhellmannwell, bswartz, how much code is manila still sharing with cinder? are you copying stuff back and forth there?20:25
russellbthat's not terribly fair to them20:25
*** Murali_ has quit IRC20:25
annegentleI do want to hear about cinder collab and so on20:25
ttxHow about bswartz quickly introduces the recent progress they made, but we don't judge yet, and move tyo next topic ?20:25
bswartzdhellmann: no, we don't copy anything -- the common stuff is in oslo20:25
annegentleis jgriffith around?20:25
ttxSo that he didn't come here for nothing ?20:25
bswartzleftover overlapping code is gradually being removed and replaced with oslo stuff20:25
*** andreaf has quit IRC20:26
dhellmannbswartz: so after that initial fork, you haven't updated anything based on ongoing work?20:26
russellbyes, i'd love to hear about progress20:26
bswartzdhellmann: no we're not messing with cinder code at all -- we have everything we needed from the original fork20:26
*** dprince has quit IRC20:26
dhellmannbswartz: that's not a bad thing, I'm just trying to understand the split, because a lot of the application emphasized how similar the architectures of the two projects were, and I wonder if there should be more code shared20:27
devanandabswartz: how much duplication of code is there now between cinder and manila? and what portion of that should be oslo'ified in the fullness of time?20:27
bswartzthe only sharing we envision at this time is through oslo20:27
bswartzwe'll push to move more common stuff into oslo ofc20:27
markmcdevananda, dhellmann, could ask the same question about cinder/nova20:27
eskerwith all due respect, we've engaged on a number of occasions in the past and made major changes to Manila in response... in good faith.  It seems poor form to change the game on us yet again.20:28
bswartzthe duplication is fairly low at this point -- mostly not we inherit the architecture, in terms of the services and their relationships20:28
dhellmannok, well, oslo isn't the only way for you to share code if it's just the 2 projects using it, so I'm worried that the oslo team will have to agree to adopt something that the 2 teams could be managing together without us20:28
bswartzmostly now*20:28
dhellmannmarkmc: yes, indeed20:28
*** ngoswami has quit IRC20:28
dhellmannbut it's good to know that oslo is on your radar, in any case :-)20:28
*** amcrn has joined #openstack-meeting20:28
*** mchalla has joined #openstack-meeting20:29
bswartzas for a general update on our progress, we have many more vendor involved now, and even more asking about how to get involved20:29
mikalDo those vendor drivers all implement a similar level of functionality?20:29
dhellmanndo you envision having third-party testing like some of the other vendor-heavy projects?20:29
bswartza good bit of work went into satisfying specific requirements  (like the gate integration, docs, etc) late last year20:29
mikalHow granular is the functionality in fact?20:29
russellb#link http://stackalytics.com/?release=all&project_type=all&module=manila20:29
bswartzsince then we've been working on new features and broader driver support20:29
jaypipesbswartz: Looks to me that https://github.com/stackforge/python-manilaclient's README is still referring verbatim to the cinderclient's README. Just FYI...20:29
*** julienvey has quit IRC20:30
bswartzregarding third-party testing, we plan to replicate the approach cinder is taking20:30
markmc#link http://stackalytics.com/?project_type=all&module=manila&release=all&metric=commits20:30
markmcrussellb, commits :)20:30
bswartzcinder is hitting some bumps in the road and we're learning a lot for free20:30
russellbmarkmc: d'oh, i keep forgetting the default change20:30
devanandabswartz: curious, how well does the manila API  abstract vendor differences20:30
mikalbswartz: have you considered at all what functionality to require as a minimum from drivers? That might save you some pain later.20:31
jeblairbswartz: what third-party drivers are you including?  what first-party drivers?20:31
bswartzdevananda: right now it does it very well because the API is quite lowest-common-denominator20:31
annegentlemarkmc: oh yeah good point20:31
dhellmannwow, 79% from the top company20:31
russellbcommits makes the project look a lot less diverse than i thought, though i think we've settled on that being primarily a graduation concern, not incubation20:31
devanandabswartz: nice. do you have auto-generated api docs?20:31
bswartzas we add more cool features keeping the API abstracted will be a challenge but no more than the challenge cinder faces doing this20:31
dhellmannmikal: +120:31
*** emagana has quit IRC20:32
ttxdhellmann: drops to 72% in Juno fwiw20:32
bswartzjeblair: the first-party driver we support is called "generic" and it's software only20:32
bswartzit layers on top of cinder and nova20:32
annegentledevananda: at the incubation request, our requirements for docs are only for contrib docs20:32
*** yamamoto has joined #openstack-meeting20:32
*** emagana has joined #openstack-meeting20:32
jeblairbswartz: what shared filesystem does it use?20:32
eskerNFS20:32
bswartzfor third party drivers we have netapp and glusterfs in tree20:32
annegentledevananda: would still like to know the answer, but just noting20:32
bswartzjeblair: ext420:33
eskerNFS for the generic driver20:33
*** ramashri has joined #openstack-meeting20:33
*** jkremer has joined #openstack-meeting20:33
bswartzand NFS for the sharing20:33
vponomaryov1 jeblair: nfs and cifs20:33
bswartzactually cifs too20:33
jeblairbswartz: does it provision its own nfs servers, like trove does for databases?20:33
devanandaannegentle: if they aren't able to autogenerate docs eg. with sphinxcontrib-pecanwsme, it's going to be more challenging later to retrofit that20:33
devanandaannegentle: but yes, i agree, not an incubation req20:33
bswartzand we have several more 3rd party drivers in development or waiting for merge20:33
vponomaryov1 jeblair: yes, depends on driver20:33
annegentledevananda: yes20:33
bswartzjeblair: yes20:34
russellbwhat's the mapping between VMs, cinder volumes, and NFS shares?20:34
jeblairbswartz: why is glusterfs considered 'third party'?20:34
rcallawarussellb: designate had 68% in juno timeframe as well - http://stackalytics.com/?project_type=all&module=designate-group&release=juno&metric=commits20:34
ttxbswartz: could you link to the nice incubation requirements table you prepared?20:34
bswartzwell it's maintained by redhat20:34
vponomaryov1russellb: nova creates VM with our image where nfs and cifs are preconfigured and uses cinder's volumes as devices for shares20:34
bswartz#link https://wiki.openstack.org/wiki/Manila/Graduation#New_Program_Requirements20:35
russellbok, so a VM and volume created per share?20:35
ttxbswartz: thx20:35
vponomaryov1russellb: volume per share, VM  not20:35
vponomaryov1russellb: VM per tenant network20:35
russellbk20:35
jeblairmakes sense20:35
russellbyep20:35
*** Ajaeger has quit IRC20:35
bswartzvponomaryov1: thanks for jumping in with answers , I can only read/type so fast..20:36
*** julim has quit IRC20:36
ttxOK, any more question for this first round ? We always do those reviews in two rounds fwiw, so this is not really special20:36
*** emagana has quit IRC20:36
*** yamamoto has quit IRC20:37
russellbfwiw, this still seems like useful functionality, and i'm hoping we can work through our growing pains without hurting the progress and momentum here20:37
jeblairbswartz: glusterfs seems like a useful bit of free software to support; so i think what i'm trying to get a handle on is how opinionated manila wants to be... what's your criteria for 'third party' drivers vs internal support20:37
ttxI think it gets the elephants out of the room20:37
jeblairrussellb: agreed20:37
bswartzwe don't want to be opinionated about drivers -- that should be the admins choice20:37
annegentleyep I think it's useful functionality20:37
dhellmannrussellb: +120:37
*** crc32 has quit IRC20:38
bswartzas PTL my goal is the make the project maximally useful -- not to promote particular backends20:38
*** Murali__ has quit IRC20:38
markmcagree this looks like a lot of promising progress, nice work20:38
jeblairi'm also wary of another neutron -- where all the "real action" happens with proprietary hardware and there's very little support for a fully open source solution20:38
ttxFrom an architecture/position standpoint it seems to fill the same spot as Trove or Designate, provision useful base services20:38
annegentlebswartz: what's your sense of vendor interest vs. user interest?20:38
mordredjeblair: ++20:38
*** Ish__ has joined #openstack-meeting20:38
dhellmannjeblair: +120:38
annegentlejeblair: yeah that's sort of what I mean too...20:38
*** Murali has joined #openstack-meeting20:38
bswartzannegentle: we're seeing a big spike in vendor interest, but user interest has been steadily high20:39
annegentlebswartz: ok good to see correct order of cart and horse20:39
jeblairso it's great to see nfs in there as the primary driver; i think exploring why glusterfs didn't make the cut will be interesting20:39
eskeruser interest has greatly outweighed vendor interest to date.20:39
markmcclainjeblair: +120:39
devanandabswartz: how are yhou planning to handle vendor differentiation?20:39
ttxbswartz: also you don't want to be another Cinder -- being the target of a zillion driver request is not that fun20:39
markmcannegentle, you know, that's a great question - I think user interest should be huge in this, but it isn't something other clouds offer ...20:39
bswartzttx: I actually think that's not unlikely, and we're prepared for it20:39
markmcannegentle, i.e. we can't just say "AWS has this and people use it a tonne"20:40
annegentlemarkmc: right20:40
markmcannegentle, I've heard people say they'd love AWS to have something like this though, but that's just anecdata20:40
ttxmarkmc: yeah. I found quite a number of people that were regretiing that AWS didn't have this though20:40
jeblairmarkmc, annegentle, bswartz: it's definitely the sort of thing we have often discussed would be useful in infra (putting on our "really big user" hats)20:40
vponomaryov1devananda: two types of drivers, where some, like gluster fs can not have network isolation20:40
eskerttx: in some ways that's exactly what end users have asked of Manila though.... a single, abstracted API for provisioning of shared file systems.  That almost certainly will invite vendor specific implementations behind it.20:40
markmcI wonder if we could get some sort of a question into the user survey about upcoming projects20:40
devanandavponomaryov1: i mean, where vendors want to add $special-feature20:40
markmc"which solve a real need you have?"20:41
dhellmannmarkmc: good idea20:41
russellbi feel like this has come up in conversations for me several times though20:41
bswartzOn the plus side we can follow the trail that the cinder project has blazed20:41
russellbbut it's just a gut feeling, i don't have data20:41
vishyso i have a small concern about knock-on features, let me see if I can express20:41
devanandaesker: users want the common abstraction, sure -20:41
vishycurrently cinder is lagging nova for some pretty significant features20:41
markmcrussellb, not saying lack of data is a blocker for me, have a gut feeling too - but could be easy to get and very interesting20:42
devanandaesker: but vendors will want to differentiate, leveragign some $special $feature, to increase sales of their hardware20:42
vishyin the past we had things like scheduler improvements, db races20:42
devanandaesker: and i'm curious how you plan to balance these two demands20:42
russellbmarkmc: indeed20:42
rcallawamarkmc: our overview session at the atlanta summit on manila was standing room only - as one indicator of interest20:42
vishycurrently it is the object model and rpc versioning20:42
russellbrcallawa: awesome20:42
markmcrcallawa, excellent20:42
vishyyou still can’t upgrade cinder versions without restarting20:42
*** dsetia has joined #openstack-meeting20:42
vishyso it seems that things go, make changes in nova, some get pulled into cinder20:43
vishyi’m concerned that since manila is a fork of cinder that adds another step in the trickle-down20:43
ttxtimeboxing to 5 more minutes20:43
eskerdevananda: Cinder is certainly instructive in this light... and it is ultimately a balance.  I think it also makes sense to acknowledge that of course vendors will want to put their best foot forward.20:43
bswartzvishy: manila is not as tightly coupled to nova as cinder is20:43
markmcvishy, conclusion? cinder should never have split out? more focus on cross-project/oslo sharing?20:43
vishyits not the coupling i’m concerned about20:43
vishyits that important features get pushed into nova20:43
vishyand then cinder gets them eventually20:43
bswartzin fact manila attempts not to involve nova at all (although we do have plans to support attach-by-instance-id)20:44
dhellmannvishy: the fact that the manila team seems to have a better attitude about working on sharing via oslo makes me think that will be less of a problem with them20:44
vishyif you are waiting on cinder to lead the way then there is a longer delay20:44
vishyi guess i’m suggesting that they should attempt to pull things more quickly from nova20:44
ttxvishy: I don't think they depend on cinder though20:44
vishylike the object model20:44
bswartzwe're not waiting for cinder -- it's just a reality that they are about 2 years more mature than us and they hit problems earlier than we do20:44
*** stevemar has joined #openstack-meeting20:44
ttxvishy: in my understanding they mostly use cinder as atemplate, rather han a fork20:44
vishylike filter_secheduler20:44
vishyetc.20:44
dhellmannvishy: yeah, I'd like that object code to go into the incubator next cycle to make that easier20:44
markmcah, I see - well, good advice for manila folks there - if you're syncing new features (like object model) don't wait for cinder to adopt first20:44
jgriffithmarkmc: hmm... merge cinder back in to Nova then?20:45
*** dsetia has quit IRC20:45
eskerjgriffith: seriously?20:45
bswartzmarkmc: thanks20:45
vishyi understand it was a template, but the reality is cinder often doesn’t know about improvements until nova makes tehm20:45
russellbdhellmann: fwiw, it was submitted before and denied :)20:45
dhellmannvishy: I've talked to dan about it, but we didn't get to it this time around20:45
vishyfor example retry_on_deadlock was only just added20:45
dhellmannrussellb: yep, that was me, and I've talked to dan about it20:45
russellbcool20:45
*** dsetia has joined #openstack-meeting20:45
dhellmannrussellb: just expect it to be fixed once it comes over :-)20:45
russellbheh, k20:45
vishyso concretely, my suggestion is parts of the code that were ultimately derived from nova20:45
ttxvishy: well, obviously adding another project (whichever it is) will increase the need for cross-project coordination20:45
vishytrack nova directly for changes20:46
*** rfolco has quit IRC20:46
markmcvishy, ironically, if manila had started from scratch we wouldn't really ask about this yet the problem would be same/worse20:46
vishylike the db layer stuff, the object model stuff etc.20:46
*** SefaKoc has quit IRC20:46
vishymarkmc: that is true, but might as well take advantage of the grandparent code in this case :)20:46
ttxvishy: oh, I see what you mean20:46
markmcvishy, yep, it's a good point20:47
dhellmannI see lots of oslo libs in the manila requirements already, which makes me happy. :-)20:47
devanandai think the point is, nova is leading several changes, and its better to be following that directly than following a follower20:47
eskervishy: not intention to follow Cinder, but rather to learn from it given common heritage20:47
vishycool20:47
ttxOK, we need to move on, we'll have another session on Manila in a future meeting.20:47
eskerthanks20:47
annegentlethanks bswartz and esker20:47
bswartzthanks guys20:47
ttxYou can continue those discussions on the Manila incubation ML thread20:48
ttxwhich didn't attract so much comments until now :)20:48
ttxeglynn: around?20:48
eglynnttx: o/20:48
ttx#topic Background information about Gnocchi project20:48
*** openstack changes topic to "Background information about Gnocchi project (Meeting topic: tc)"20:48
ttx#link http://lists.openstack.org/pipermail/openstack-tc/2014-August/000757.html20:48
ttxeglynn asked for some time to explain a few things about Gnocchi20:48
eglynn^^^ background on that ML thread20:48
ttxWe don't have that much time left, but since Eoghan will be in vacation soon, maybe a quick mention here can't hurt :)20:48
markmcare there TC-level concerns?20:49
eglynnyeah thanks for the opportunity ...20:49
* markmc thought the mail was a nice summary20:49
ttxI'm timeboxing this to 6 minutes so that we have time to cover the other changes20:49
russellbmarkmc: ++20:49
eglynnwell the intent is just to get TC folks caught up on what gnocchi is about20:49
markmccool20:49
russellbthanks for the ML post20:49
eglynnas there was an info deficit20:49
eglynnyep, so the TL;DR is ...20:49
eglynngnocchi is an arms-length project from ceilometer, in which we're exploring one option to pay down some architectural debt20:49
eglynnhappy to answer any questions is there's time20:50
mikalSo there are no plans to move to it at this time?20:50
eglynnI did go into a bit more detail in the thread on what it is, and what it ain't20:50
ttxi'm still a bit confused on the scope overlap between Gnocchi and InfluxDB20:50
mikalIts still an experiment?20:50
devanandaeglynn: did anyone look into existing time-series databases before implementing another one?20:50
russellbsounds like a nice way to try out a major improvement, without too much disruption to the project for now20:50
zanebeglynn: would it be fair to describe it as a branch that will eventually be merged back or not?20:50
*** SefaKoc_ has joined #openstack-meeting20:50
russellbseems reasonable20:50
ttxthere seems to be a layer that would be duplicated between them20:50
russellband something we should encourage20:50
*** rkofman has left #openstack-meeting20:50
eglynnmikal: timeline is kilo to swicth if it meets the grade20:50
eglynnzaneb: yep that's fair20:51
eglynndevananda: well we're not just reinventing20:51
mikaleglynn: how do you decide if it meets the grade? What's the process for that?20:51
devanandaeglynn: "not jsut reinventing" ?20:51
ttxdevananda: they can piggyback on a time-series DB, but yeah, it seems like they would reimplement some parts of it20:51
mikaleglynn: a summit session?20:51
eglynndevananda: ... there's a pluggable driver model that allows us to plug in InfluxDB etc. as the backend20:51
*** DuncanT has joined #openstack-meeting20:52
eglynnmikal: at the juno session, yes there was a session20:52
eglynnmikal: https://etherpad.openstack.org/p/ceilometer-tsdaas20:52
eglynnmikal: a-ha, you mean at the kilo summit?20:53
eglynnmikal: yes the process would include performance profiling and ensure a semantic match in the API20:53
ttxThe thread explains the sitiation pretty well, and it just gets started20:53
mikaleglynn: ok, cool20:53
ttxso I think discussion can continue there20:53
mikaleglynn: that's what I was asking about20:54
mordredI'm still very unclear as to why a new time-series anything needs to be written20:54
devanandaeglynn: I'm sure there's a reason why gnocchi didn't work with trove to provision influxdb instances?20:54
devanandamordred: as am I20:54
dhellmanngnocchi is also partially a response to all of the complaints about operators having to learn yet another new service, since can use swift for storage20:54
eglynnmordred: sandy raised a similar question on the ML, and I go into more detail there on the additional semantics20:54
mordredeglynn: ok. I'll go read that before I dive in more20:55
ttxyeah, I think the discussion can continue tere, we won't solve it in 4 minutes20:55
eglynnmordred: (i.e. above and beyond pure timeseries storage)20:55
mordredbut it seems very much like a description of carbon20:55
ttxThanks eglynn20:55
dhellmannmordred: apparently the carbon code is really ugly20:55
mordredwhich already exists and is in use at massive scale around the world and is in python20:55
mordred*meh*20:55
jeblairthat's clearly not stopped us before20:55
russellbworks > pretty :)20:55
mordredugly code is not a reason to write a new thing20:55
jeblairrussellb, mordred: ++20:56
dhellmannwell, from the perspective of it not quite doing what we want and also being hard to change, it might be20:56
markmcmordred, we could give the program the benefit of the doubt that they're not NIH for the sake of it20:56
*** rfolco has joined #openstack-meeting20:56
russellbyes, i think we should assume good faith on that ... but a summary about what was considered and why it didn't work out would be good20:56
mordredmarkmc: no, I don't think we have very good track record with that overall aroudn here20:56
mordredI don't assume bad faith20:56
mikalI feel like at this point we should let gnocci do its thing, and then ask for a merits based comparison with other options before its baked into ceilometer20:57
eglynnrussellb: I can dig out more detail on jd__'s analysis of the fit with carbon20:57
*** patelna has joined #openstack-meeting20:57
*** lsmola3 has quit IRC20:57
mikalIts not really fair comparing a half done thing with a finished thing20:57
*** jtomasek_ has quit IRC20:57
russellbeglynn: sounds like that'd be helpful20:57
jeblairagreed, i think we need to ask these questions, if for no other reason than people may simply not be aware of all the options.  we have things to offer other than just being grumpy.  :)20:57
eglynnrussellb: cool20:57
mordredmikal: I DO think it's fair20:57
eglynnmikal: fair point20:57
zanebmordred: I'm not sure that's true, although we definitely don't have a good track record of communicating why something is not NIH20:57
dhellmannjeblair: we got quite a lot of both at the summit in atlanta :-)20:57
russellbit's not comparing gnocci with carbon20:57
sandywalshmy only suggestion is the tsdb portion be one project and the abstraction layer be another (gnocchi proper)20:57
russellbit's comparing carbon to requirements20:57
mikalmordred: it sounds like other options were considered before they went down this path20:58
mordredmikal: and if that thing is intending to a substantial part of an integrated project, then I think it's worthwhile for us to get involved if we're going to be on the hook for maintaining a thing20:58
mikalmordred: I think we should leave second guessing them until they're done with their counter proposal20:58
ttxOK, let's continue that discussion (1) on the thread and (2) at the special meeting20:58
jeblairmikal: it also sounds like they weren't aware of influxdb at the time20:58
mordredmikal: ok. I'm just saying, I do NOT think we need to wait until the thing is finished to have discussions about whether doing the thing is a good idea20:58
ttxI'll use the last minute to cover the housekeeping changes20:58
devanandamordred: ++20:58
jeblair(i wasn't either -- that's not a judgement, just an illustration of why asking and discussing options early is good)20:58
ttx#topic Other governance changes20:59
*** openstack changes topic to "Other governance changes (Meeting topic: tc)"20:59
ttx* Move DevStack to QA program (https://review.openstack.org/112090)20:59
mordredjeblair: ++20:59
eglynnjeblair: InfluxDb is pretty new in fairness, but the discussion with the Influx devs started in ATL at the same time as gnocchi20:59
ttxIt looks like we are hugely in favor, but it needed a rebase last time I looked20:59
ttxwhich was posted... so please reapprove20:59
ttx* Add oslo.serialization to Oslo program (https://review.openstack.org/112996)20:59
*** emagana has joined #openstack-meeting20:59
ttxThis one now has dhellmann +1 so should be good to go, unless someone objects now20:59
ttx* Add oslo.middleware to the Oslo program (https://review.openstack.org/112395)20:59
ttxSame for this one, will approve after meeting unless someone objects now20:59
ttx* Add repository glance.store to glance (https://review.openstack.org/107585)20:59
ttxThis one is still missing Glance PTL's +1, markwash is in vacation right now21:00
ttx#topic Open discussion21:00
*** openstack changes topic to "Open discussion (Meeting topic: tc)"21:00
ttxAnd as usual, no time left for open discussion weeee21:00
* ttx could do with a meeting that finishes early21:00
annegentletoo late :)21:00
* dhellmann invites ttx to the oslo meetings21:01
ttxOK, so we'll all see each other on Thursday, 19:00 UTC on #openstack-meeting-321:01
markmcclainwell maybe we can try for thursday's to end early :)21:01
ttxmarkmcclain: haha21:01
ttxunlikely.21:01
ttx#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Tue Aug 12 21:01:39 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-08-12-20.02.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-08-12-20.02.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-08-12-20.02.log.html21:01
*** timcl has left #openstack-meeting21:01
*** markmc has quit IRC21:02
ttxdhellmann, dolphm, notmyname, eglynn, markwash, jgriffith, mikal, zaneb, david-lyle, mestery, SlickNik, SergeyLukjanov: around ?21:02
dhellmanno/21:02
mesteryo/21:02
zanebo/21:02
notmynamehere21:02
SergeyLukjanovo/21:02
*** VijayB has joined #openstack-meeting21:02
dolphmo/21:02
eglynno/21:02
jgriffitho/21:02
devanandao/ but lurking now21:02
SlickNiko/21:03
ttx#startmeeting project21:03
openstackMeeting started Tue Aug 12 21:03:15 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:03
*** kentwu_ has joined #openstack-meeting21:03
*** openstack changes topic to " (Meeting topic: project)"21:03
openstackThe meeting name has been set to 'project'21:03
ttxAgenda for today is available at:21:03
mikalHi21:03
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21: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
ttxWe covered all projects but Cinder this week (Cinder is having their midcycle meetup)21:03
ttxHere is the log:21:04
ttx#link http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-08-12-08.03.html21:04
ttxIn summary all projects are slightly behind schedule, and most of them will use FPF to drop stuff that is not proposed next Thursday21: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
annegentleo/21:05
*** jckasper_ has joined #openstack-meeting21:05
jeblairo/21:05
annegentleI have a quick psa that ties into the later agenda item; I can wait until then21:05
clarkbI will be switching everyone to trusty by default on the 20th and updating tox21:05
*** MarkAtwood has quit IRC21:05
mtreinishclarkb: nice21:06
*** fnaval has joined #openstack-meeting21:06
eglynnclarkb: trusty FTW! :)21:06
jeblairttx: we want to move stackforge/kite to openstack/kite since it was adopted by barbican21:06
*** VijayB has quit IRC21:06
*** jasondotstar has quit IRC21:06
jeblairttx: do you sync with jraim?21:06
ttxI can do thaht21:07
jeblairwe were also wondering about python-kiteclient21:07
ttxit should probably move as well21:07
ttxbut then it's not like an emergency repomove21:07
*** VijayB has joined #openstack-meeting21:07
dolphmthey should stay together, for sure21:08
ttxjeblair: won't be that much around in the coming days21:08
ttxjeblair: you got a repomove day planned?21:08
jeblairttx: yeah, saturday.  we'll try emailing him i guess :)21:09
*** pdmars_ has quit IRC21:09
ttxack, thx21:09
*** jckasper__ has quit IRC21:09
ttxok, moving on21:09
ttx#topic When to open Kilo specs (mikal)21:09
*** openstack changes topic to "When to open Kilo specs (mikal) (Meeting topic: project)"21:09
ttxmikal: ohai21:10
mikalHeya21:10
*** bradjones has quit IRC21:10
mikalSo... I'm receiving questions on when specs for K will open21:10
ttxI know mestery wanted to discuss that as well21:10
* mestery listens closely here.21:10
mesteryttx: ++21:10
dolphmwhy are specs not open now?21:10
mikalGiven we'd said that the specs process would be more synced between projects in K21:10
*** Murali has quit IRC21:10
mikalI feel like we should have a unified plan for this as well21:10
eglynnbump any still-open juno specs to kilo now?21:10
mikalWe'd felt that working on specs now was a distraction from landing J21:10
*** Ish__ has quit IRC21:10
ttxI think the main concern is the review overload. But then you could train reviewers to ignore Kilo specs until Kilo opens21:11
mikalHowever, I now realize the people writing specs have little interest in fixing J bugs21:11
*** Murali_ has joined #openstack-meeting21:11
mesterymikal: It's a tough nut to crack21:11
dolphmi don't have an example today, but if we had review bandwidth and a spec proposed to a kilo/ dir today, why not give it a review? is there reason to block it?21:11
mikali.e. the people wanting to do one now are people only interested in landing their feature21:11
ttxesepcially since they should not really be looking into *-specs at this point21:11
dolphmmikal: what are you trying to stop people from doing? proposing kilo specs? reviewing kilo specs? landing them?21:11
eglynnbut the fact that they can't propose to gerrit won't stop them working on their spec surely?21:12
mikalSo I guess this was more of an informational thing21:12
ttxdolphm: I think you don't have the same type of problems that Nova, Neutron (and possibly Cinder) have21:12
mikalWhat are other projects doign for this?21:12
ttxwhere the sheer noise is disturbing21:12
mikaldolphm: distracting reviewers, and attempting to redirect that effort into things we need for J21:12
annegentlepeople only want to write specs?21:12
dolphmttx: certainly!21:12
mikalannegentle: yes, some people21:12
annegentlemikal: or is it that they want assurance _all_ will land?21:12
ttxannegentle: but write them and reviewers will come21:12
dolphmmikal: can't reviewers just ignore kilo/ specs willingly?21:12
annegentlemikal: as in spec,code, everything?21:12
mikalWe have vendors who have little interest in fixing bugs, and only care about landing their feature21:12
*** pberis has joined #openstack-meeting21:13
eglynnmikal: I was thinking of just bumping all open juno specs to kilo and then asking the review team to use their judgement as to where to apply their review cycles21:13
mesteryIt's hard for us to focus on Kilo spec reviews when we're still trying hard to land Juno stuff.21:13
*** aysyd has quit IRC21:13
annegentlemikal: they'll write specs but not docs, and that needs to be nipped21:13
mikaldolphm: sure... its more the attempt to redirect the author's efforts that we were after21:13
devanandathe sheer noise is distracting <--- this21:13
eglynnmikal: ... with a heavy steer away from kilo specs, but not enforced21:13
devanandafolks show up in IRC pushing the "please review my spec" button over an over again21:13
mikalI don't think moving J specs to K is a good idea for nova21:13
*** vishwanathj has joined #openstack-meeting21:13
mikalWe have a lot of abandonded specs as well21:13
dolphmmikal: but like you said, certain spec authors couldn't care less about stabilizing the previous release, especially if they're feature isn't in it21:13
mesterydevananda: ++21:13
mikalRe-proposing is light weight21:13
mikaldolphm: sure, but I was trying to change their behaviour21:14
mikaldolphm: it didn't work21:14
eglynndevananda: I use a mental /ignore to filter those :)21:14
dolphmmikal: cats21:14
*** weshay has quit IRC21:14
mikalSo, it sounds like other people are allowing K specs now?21:14
devanandafor ironic, my plan is to -2 all open specs, then wait until some time (exactly when TBD) after FF before creating the /kilo directory, and then see who reproposes21:14
mesterymikal: Not Neutron.21:14
dolphmmikal: how about moving abandoned specs into an abandoned/ dir at the end of a release, all at once?21:14
mikaldolphm: we were just goign to -2 in gerrit like devananda21:15
mikaldolphm: moving them into a dir would require merging them21:15
mikalWhich would be a lot of reviews21:15
mikalUnless its one super review I suppose21:15
dolphmdevananda: design discussions should still go on - i don't think a -2 is particularly beneficial to anyone21:15
*** jtomasek_ has joined #openstack-meeting21:15
eglynnmikal: I'm not a huge fan of attempting to force the hand of developers, as they tend to just workaround the restriction in any case21:16
ttxannegentle: all those who write specs won't really be around to write docs :)21:16
mikaldolphm: the review needs to have its paths chagned, hence the procedural -221:16
dolphmmikal: you're talking about abandoned reviews then?21:16
mikaldolphm: yeah, largely21:16
ttxIt's tricky, you want to let the door open but clearly show that it's frowned upon21:16
mikaldolphm: we don't know what's abandoned at the moment, as spec review stopped a while ago21:16
devanandadolphm: that's exactly it. i DONT want design discussions happening between now and RC21:16
ttxso that people know they should be usig their time doing something else at this point in the cycle21:16
mikaldolphm: do asking people to rebase is a way they signal that they still care21:16
*** pberis has quit IRC21:16
devanandaat least not in as much as they take away from making a stable RC21:16
*** radez is now known as radez_g0n321:17
mikals/do/so/21:17
ttxdevananda: ++21:17
eglynnpositive steer beats negative restrictions, IMO21:17
devanandathere are seriously only two things in ironic that deserve an ongoing discussion with cores - and we already have that informally21:17
dolphmdevananda: that seems like you're shooting yourself in the foot21:17
*** yamamoto has joined #openstack-meeting21:17
*** grantbow has left #openstack-meeting21:18
dolphmdevananda: (trying to artificially inhibit design discussions)21:18
devanandadolphm: focusing on one thing for a short period of time means putting other things on the back burner21:18
devanandaI don't see how that's a bad thing21:18
ttxeglynn: how would you present it in a positive way while still discouraging out-of-sync actions like this? It's tricky21:18
*** vishwanathj has quit IRC21:18
*** mrda-away is now known as mrda21:18
dolphmdevananda: normally, what we're designing for and what we're doing are closely related21:19
devanandadolphm: we'll definitely have those design discussions with vendors and interested parties, after we do the work needed to get Juno out the door21:19
eglynnttx: the value proposition is making juno a release we can be proud of / can stand over etc.21:19
mikaleglynn: I haven't had a lot of joy with that sort of angle21:19
mikaleglynn: "do reviews, it will speed up your own review by making the queue smaller"21:19
*** sandywalsh has quit IRC21:19
mikaleglynn: zero reviews occur21:19
eglynnmikal: fair enough, much bigger and more diverse contributor base in the nova case21:19
eglynnmikal: ... social pressures easier to apply with a smaller group21:20
ttxeglynn: as someone who has been asking people to work on RC bugs for the last 9 releases, i would say that the beauty of the game is not a sufficient motivator21:20
*** emagana has quit IRC21:20
mikaleglynn: I think that's very true21:20
mikaleglynn: also, it seems projects with a vendor driver layer seem to have a harder time21:20
eglynnmikal: fair point21:20
*** noslzzp has quit IRC21:20
ttxit only touches a minority of contributors, the "strategic" ones21:20
*** rudrarugge has quit IRC21:21
eglynnttx: ... if all else fails, one can always try "guilting" them into doing it :)21:21
mikalI don't feel like we reached a concensus here21:21
*** emagana has joined #openstack-meeting21:21
ttxSo. solution one is to not prevent K specs from being submitted, and teach core reviewers to ignore them21:21
*** jkremer has left #openstack-meeting21:21
dolphmmikal: what was the question, again?21:22
ttxsolution 2 is to somehow prevent those from being filed until RC121:22
eglynnmikal: well a one-size-fits-all approach may not work across all the projects21:22
mikalttx: I am increasingly of the believe we should go with 121:22
ttxeglynn: it's definitely not a one-size-fits-all21:22
mikalYeah, agreed21:22
ttxit's finding a solution for the largest projects21:22
eglynnttx: that's fair21:22
mikaldolphm: whether opening K specs now is a mistake21:22
mesteryIgnoring specs has it's own issues, if that's a solution it's the wrong one.21:22
mesteryWe hit many issues with that in Neutron during Juno.21:22
ttxmikal: i prefer solution 1. Solution 2 is only pretending to fix the issue21:22
mikalttx: agreed21:23
mesteryIf anything, being more proactive about responding to specs is the right approach, but that requires time.21:23
mikalIts ok, K will be full of magical runways of awesome21:23
dolphmmikal: well then i vote that closing them was a mistake :)21:23
mikalWe just have to get there with no one getting murdered on the way21:23
ttxmestery: you think we can't just say "K specs will start getting reviewed when K development opens" ?21:23
ttxthat sounds like something that rings true, somehow21:24
mesteryttx: My experience shows people get angry when their specs are ignored.21:24
mikalttx: that's what nova originally said21:24
mesteryWhile it's a fair statement, not everyone will be happy with it.21:24
mikalttx: and what happens now is everyone pings me and says they're sulking21:24
dolphmmestery: when anything in gerrit is ignored21:24
mesterydolphm: ++21:24
mikalttx: and declines to work on bugs instead21:24
ttxsigh21:24
mesterymikal: I get that too21:24
*** yamamoto has quit IRC21:24
*** vponomaryov1 has left #openstack-meeting21:24
mikalI get a lot of very weird personal email21:24
ttxmikal: we should trade some21:25
*** scottda__ has left #openstack-meeting21:25
mikalttx: have a gallery of the best?21:25
mesterymikal: I bet not as weird as mine21:25
*** Riddhi has joined #openstack-meeting21:25
ttxsounds like a topic for a beer21:25
mikalMaybe neutron / cinder / nova should collude for a "big project plan"21:25
*** Riddhi has quit IRC21:25
*** dkranz has quit IRC21:25
*** ominakov has quit IRC21:25
mikalWe could have a quick chat when John gets back21:25
dolphmmikal: ttx: just reply on an mailing list21:25
mesterymikal: :)21:25
*** Riddhi has joined #openstack-meeting21:26
mikalIt seems like the big project concerns aren't shared by the smaller projects21:26
*** kevinconway has joined #openstack-meeting21:26
jgriffithI'm back :)21:26
dhellmanndolphm: I reply to a lot of email asking them to resend it to the -dev list21:26
mikalOh, that guy21:26
annegentlemikal: right that's my sense of it too21:26
dolphmdhellmann: i just do that for them :)21:26
ttxfrankly, I think if you have so many people that don't care about your project that you can't get enough "normal" work done, you have a separate problem21:26
dolphmdoesn't happen all that often to me though21:26
devanandamikal: i'm sort of surprised, given how much ironic's concerns overlap with nova's21:26
ttxthis K specs thing is just a symptom21:26
mikalttx: oh, agreed21:26
mesteryttx: ++21:26
devanandamikal: I don't consider us a large project, tho21:27
devanandattx: definitely21:27
mikalttx: is more about trying to push the distraction laser out of the path of the people who are part of the solution21:27
markmcclaincould we not just have a gerrit autoresponder for projects that want delay that includes a note of when the opening will occur?21:27
mikaldevananda: surprised that smaller projects seem less concerned you mean?21:27
ttxmikal: in the end, it's "how to avoid the PTl pain of dealing with unreasonable requests"21:27
dhellmannmarkmcclain: it wouldn't even need to be a bot, it could be a check job21:27
ttxI think jgriffith wrote a book on it21:27
mikalttx: I think that pain is unavoidable21:28
mikalttx: because we deal with humans'21:28
devanandamikal: surprised that smaller proejcts don't share the concerns of larger projects (+ ironic)21:28
ttxmikal: we could do a better job of communicating expectations though21:28
mikalttx: I tried building a core reviewer out of lego, it didn't work out so well21:28
mikalttx: well, we did announce that we would freeze specs, accept no K specs, and fix bugs21:28
mikalttx: people just don't like it so they complain and don't fix bugs21:29
devanandamikal: that's awesome21:29
ttxI think you do as much as you can, we (as in me) need to ramp up developer docs and training to match21:29
eglynnmikal: that would be my fear exactly21:29
*** padkrish_ has quit IRC21:29
dhellmannthere's a group working on getting corporate project managers more involved, maybe communicating these expectations is an area where that would be useful?21:29
mikaldhellmann: if I had a mailing list of corporate project managers I could email asks to, I would use it a lot21:30
dolphmttx: a big page that answers the question "as a contributor, what should i be working on this week?" would be dandy21:30
ttxmikal: at this point it's like they are just not contributing, so you shouldn't count on them for bugfixing21:30
mikaldhellmann: "please encourage your people to focus on bug fixes for now"21:30
ttxyou may have a smaller set of contributors than you think :)21:30
dolphmttx: and by big page, i mean like a giant link to gerrit21:30
mikalttx: agreed. I also don't love drive by features by the way.21:30
mesteryI think as PTLs we already act as project managers, I don't think developers would necessarily listen to other ones either.21:30
* eglynn thinks we've got to get out of the mindset that we can *tell* devs what to work on ... at most we can steer and incentivize IMO21:30
mikalttx: which is what a lot of this is.21:30
annegentlebug fixes and document the features that did land.21:30
dhellmannmikal: zehicle and sarob are involved in that, according to their blogs (also allison randall, but I don't know her irc handle)21:31
mikaleglynn: that's probably true, although I don't know how to get there from here (at least in nova)21:31
ttxmikal: once upon a time, everyone was attening the "project meeting" (this one) and just me shouting at people what enough to communicate cycle priorities21:31
*** padkrish_ has joined #openstack-meeting21:31
ttxs/what/was21:31
devanandadhellmann: wendar21:32
ttxwe grew to the point where only PTLs attend this meeting21:32
dhellmanndevananda: thank you21:32
ttxand they know the priorities21:32
annegentlettx: ah the good old days21:32
eglynndhellmann: these new corporate project managers would have how much leverage over the developer resources, do you think?21:32
* mordred didn't attend this meeting even back then21:32
* mestery reminisces.21:32
mikalSo, I feel like we should move on21:32
annegentlemordred: ha21:32
mikalThere are other things on the agenda21:32
mikalAnd this has stalled21:32
dolphmmikal: ++21:32
*** mrmartin has quit IRC21:32
ttx#action ttx to think about how to communicate cycle priorities in the thousand-contributors times21:33
mesterymikal: ++21:33
dhellmanneglynn: well, it wouldn't be a matter of saying "we need you to do X" at first, but a matter of saying "don't talk to us about new features for a few weeks, we have bugs to fix"21:33
dhellmanneglynn: setting expecatations at a different level in the organization21:33
*** lyxus has quit IRC21:33
*** marun has quit IRC21:33
eglynndevananda: yeah, cool enough if it's "soft steer" like that21:33
eglynndhellmann: ^^^21:33
*** ivar-lazzaro has quit IRC21:33
ttxmikal: in summary, i think you should keep K specs open. We need to communicate cycle priorities better, but that's a bigger issue21:33
eglynndarned tab completion!21:33
*** ivar-lazzaro has joined #openstack-meeting21:34
mikalttx: yeah, that's where I got ot as well21:34
*** topol has quit IRC21:34
mikalttx: I will discuss with John when he gets back from his cold meat themed music festival21:34
ttxthis meeting, and occasional ML rants are no longer enough21:34
* devananda disagrees, keeps K specs closed21:34
mikaldevananda: as is your right21:34
ttxdevananda: ftw21:34
ttxok next topic21:34
ttx#topic Clarification on documentation contrib workflow (eglynn/annegentle)21:34
*** openstack changes topic to "Clarification on documentation contrib workflow (eglynn/annegentle) (Meeting topic: project)"21:34
devanandai'll let ya'll know how it goes when we get to paris21:35
ttxHeavyweight XML-based docbook versus new lightweight RST-based model21:35
eglynnyeah, just something I wanted to raise on the PTLs' radar21:35
ttxFight!21:35
*** bknudson has quit IRC21:35
eglynnas it could save your team some learning curve21:35
annegentleheh no fight here21:35
eglynn(if your project has substantial docco contribution coming down the road)21:35
ttxeglynn: presented like this, i can't side with XML21:35
eglynnannegentle: agreed, all sweetness & light! :)21:35
eglynnttx: this is more in the line of a PSA21:35
mikalCould we perhaps use microsoft word for docs?21:36
*** crc32 has joined #openstack-meeting21:36
eglynnso basically there are now two separate contrib models for doc21:36
annegentlenext I will require video documentation21:36
* annegentle stabs mikal with a spork21:36
mikalHeh21:36
eglynnthe XML-based docbook has a significant learning curve21:36
eglynnbut the docs team is piloting a new lightweight option21:36
eglynnbased on RST that we all know and love :)21:36
dhellmannannegentle: sporks are too sharp21:36
*** rcallawa has quit IRC21:37
eglynnso given how enthusiastic devs are for writing kilo specs in RST21:37
dolphmxml used to be keystone's primary means of api docs, and we got less than zero community contribution. moving to MD/RST, we get quite a lot, although RST is still apparently a challenge to get even close to correct for most people21:37
annegentleeglynn: heh quite the tie in21:37
*** SefaKoc_ has quit IRC21:37
eglynnyep, seems that they should also be gunning to knock out the docco in the same format21:37
eglynnannegentle: have I represented all that correctly?21:38
ttxeglynn: now I'm disappointed. I'm addicted to conflict now21:38
eglynnttx: LOL :)21:38
annegentleyes, though currently we are doing a POC with Heat only21:38
annegentlepart of this psa is also that I've got patches removing WADL from the "long form" API documents21:38
annegentledolphm: https://review.openstack.org/#/c/112620/21:39
*** ominakov has joined #openstack-meeting21:39
*** neelashah has quit IRC21:39
annegentlethat helps with the problem of broken doc builds across repos (where the WADL breaking would break another repo's build)21:39
mikalIs someone going to move the existing XML docs to RST?21:39
annegentlewhat I'd like to do next is propose RST for the "long form" info that's left, like rate limiting, etc.21:39
mikalCause that person will look awesome on stackalytics21:39
ttxdie WADL die21:39
annegentlemikal: this is a phased approach21:39
*** vijendar has quit IRC21:40
annegentlemikal: well that person is me and I still won't match someone like Andreas Jaeger :)21:40
mikalHeh21:40
dolphmannegentle: my hero!21:41
*** Ish__ has joined #openstack-meeting21:41
annegentlemikal: the phases are: POC for Heat (HOT Template), WADL removal for only docs on http://docs.openstack.org/api/api-specs.html21:41
*** jorge_munoz has quit IRC21:41
annegentlethen RST proposal for API docs in each repo21:41
eglynnannegentle: so for kilo, will the RST model become the primary vector for doc contributions from the project teams, d'ya think?21:41
annegentleany questions?21:41
dolphmannegentle: so, related conversation... should identity-api still exist? or should it be somehow merged into keystone-specs?21:41
eglynn(or over a longer time horizon)21:41
annegentleWADL remains our only solution currently for http://developer.openstack.org/api-ref.html but I'd welcome ideas21:42
dhellmannannegentle: are you using sphinxcontrib-pecanwsme for API docs for new projects? should I get that moved to stackforge?21:42
annegentledolphm: I was going to propose it in keystone, but maybe in -specs is the better way?21:42
annegentledhellmann: I don't have a solution for extensible apis like nova neutron keystone right?21:42
dolphmannegentle: doing it in -specs allows us to see proposed API changes as part of the design process21:42
annegentledolphm: right but you're the only team doing that, so my thinking is that I shop it with patchsets21:43
annegentledolphm: or I guess I could do ML post prior to patchsets21:43
dhellmannannegentle: yeah, this would just be for new stuff, I'm just curious if you're actually using it in some way for non-developer docs since it's still under Dreamhosts' github account21:43
annegentleeglynn: as for "will the RST model become primary vector" -- I have a dependency on a page-based redesign21:43
dolphmannegentle: i'm asking selfishly here, knowing no one else uses keystone's process21:44
dolphmfor api documentation, anyway21:44
eglynnannegentle: fair enough21:44
annegentledhellmann: I really would prefer a single API reference "way" -- swagger, raml, wadl, whatever21:44
annegentledhellmann: how you generate it I don't care21:44
dolphmrst + jsonschema definitions :)21:44
annegentledhellmann: unless it's crappy21:44
dolphmor md21:44
dhellmannannegentle: ok, I wasn't pushing a solution, just wanting to make sure the tools you might be using were easily fixable as needed21:44
annegentledhellmann: seems like it21:45
dhellmannI suspect most projects are going to be using some JSONSchema thing anyway, so the wsme doc lib might not be as useful21:45
annegentledhellmann: it looks like that's the compute v3 api (jsonschema)21:45
dhellmannyeah21:45
annegentleright21:46
*** MaxV has quit IRC21:46
*** eankutse has quit IRC21:46
ttxok, I think the PSA is now emitted21:46
annegentleI still believe a lot of discussion about scope will help the docs program21:46
mikalThere is no v3 api by the way21:46
annegentlesince all of this overflow is in integrated projects21:46
mikalIt was a mirage21:46
annegentleoh yes v3 / v2.121:46
mikalTa21:46
ttxeglynn, annegentle ready to move to open discussion?21:47
annegentlehttps://review.openstack.org/#/c/85640/ for the curious/uninitiated21:47
annegentleI'm good-to-go if eglynn is21:47
eglynnttx: yep21:47
ttx#topic Open discussion21:47
eglynnannegentle: thanks for all the additional background detail21:47
*** openstack changes topic to "Open discussion (Meeting topic: project)"21:47
ttxAnything else, anyone ?21:47
*** hashar has quit IRC21:47
annegentlesomeone come up with something so ttx doesn't get an early meeting end! I kid, I kid.21:48
ttxtss21:50
ttx#endmeeting21:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:50
openstackMeeting ended Tue Aug 12 21:50:46 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2014/project.2014-08-12-21.03.html21:50
mikalYay!21:50
ttxwin!21:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2014/project.2014-08-12-21.03.txt21:50
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2014/project.2014-08-12-21.03.log.html21:50
ttxThanks everyone21:50
dolphm\o/21:51
ttxcome back next week for more adventures21:51
eglynn'night all!21:51
*** armax has quit IRC21:53
*** julienvey has joined #openstack-meeting21:54
*** eghobo has joined #openstack-meeting21:57
*** jckasper_ has quit IRC21:58
*** rockyg has quit IRC21:59
*** rcarrill` has joined #openstack-meeting21:59
*** yamamoto has joined #openstack-meeting21:59
*** Riddhi has quit IRC21:59
*** rcarrillocruz has quit IRC22:01
*** SridharRamaswamy has joined #openstack-meeting22:02
*** mtanino has quit IRC22:02
*** SlickNik has left #openstack-meeting22:02
*** bknudson1 has joined #openstack-meeting22:02
*** amotoki has joined #openstack-meeting22:03
*** kentwu__ has joined #openstack-meeting22:03
*** Sridhar__ has joined #openstack-meeting22:04
*** SridharR_ has quit IRC22:06
*** kentwu_ has quit IRC22:06
*** SridharRamaswamy has quit IRC22:06
*** banix has joined #openstack-meeting22:07
*** amotoki has quit IRC22:08
*** noslzzp has joined #openstack-meeting22:08
*** cjellick_ has joined #openstack-meeting22:10
*** yeungp has quit IRC22:11
*** cdub has quit IRC22:13
*** cjellick has quit IRC22:13
*** Riddhi has joined #openstack-meeting22:13
*** rcarrillocruz has joined #openstack-meeting22:14
*** cjellick_ has quit IRC22:14
*** trey_h has quit IRC22:15
*** rcarrill` has quit IRC22:16
*** emagana has quit IRC22:17
*** emagana has joined #openstack-meeting22:18
*** mchalla has quit IRC22:19
*** mchalla has joined #openstack-meeting22:19
*** Riddhi has quit IRC22:20
*** changbl has quit IRC22:21
*** jecarey has quit IRC22:22
*** emagana has quit IRC22:22
*** armax has joined #openstack-meeting22:22
*** mchalla has quit IRC22:24
*** Sridhar__ has quit IRC22:29
*** SridharRamaswamy has joined #openstack-meeting22:29
*** SridharR_ has joined #openstack-meeting22:32
*** emagana has joined #openstack-meeting22:33
*** dkranz has joined #openstack-meeting22:33
*** cody-somerville has joined #openstack-meeting22:33
*** emagana has quit IRC22:33
*** ivar-lazzaro has quit IRC22:33
*** ivar-lazzaro has joined #openstack-meeting22:34
*** emagana has joined #openstack-meeting22:34
*** SridharRamaswamy has quit IRC22:34
*** AlanClark has quit IRC22:34
*** weshay has joined #openstack-meeting22:34
*** weshay is now known as weshay_afk22:35
*** jaypipes has quit IRC22:36
*** penick has joined #openstack-meeting22:37
*** penick has quit IRC22:38
*** julienvey has quit IRC22:39
*** AlexF has quit IRC22:40
*** david-ly_ is now known as david-lyle22:41
*** cjellick has joined #openstack-meeting22:41
*** kentwu__ has quit IRC22:41
*** penick has joined #openstack-meeting22:41
*** shashankhegde has quit IRC22:42
*** banix has quit IRC22:44
*** prad has quit IRC22:44
*** carl_baldwin has quit IRC22:48
*** ivasev has quit IRC22:49
*** banix has joined #openstack-meeting22:49
*** cjellick has quit IRC22:50
*** shashankhegde has joined #openstack-meeting22:52
*** gokrokve_ has joined #openstack-meeting22:52
*** Murali_ has quit IRC22:53
*** emagana has quit IRC22:53
*** gokrokve has quit IRC22:56
*** julim has joined #openstack-meeting22:56
*** bdpayne has quit IRC22:57
*** IanGovett has joined #openstack-meeting22:58
*** bdpayne has joined #openstack-meeting22:58
*** shashankhegde has quit IRC22:59
*** julim has quit IRC23:00
*** bdpayne_ has joined #openstack-meeting23:01
*** DuncanT has quit IRC23:02
*** bswartz has quit IRC23:02
*** bdpayne has quit IRC23:04
*** kevinconway has quit IRC23:05
*** Ish__ has quit IRC23:06
*** KurtMartin has quit IRC23:06
*** whenry has quit IRC23:06
*** eharney has quit IRC23:06
*** patelna_ has joined #openstack-meeting23:06
*** Ish__ has joined #openstack-meeting23:07
*** hemna has quit IRC23:09
*** banix has quit IRC23:10
*** whenry has joined #openstack-meeting23:10
*** dbite has quit IRC23:10
*** patelna has quit IRC23:10
*** IanGovett has quit IRC23:10
*** colinmcnamara has joined #openstack-meeting23:12
*** eglynn has quit IRC23:13
*** emagana has joined #openstack-meeting23:15
*** colinmcnamara has quit IRC23:17
*** xyang1 has quit IRC23:17
*** mchalla has joined #openstack-meeting23:20
*** emagana has quit IRC23:20
*** jmontemayor has quit IRC23:20
*** mchalla has quit IRC23:21
*** mchalla has joined #openstack-meeting23:21
*** sdake_ has joined #openstack-meeting23:22
*** SridharRamaswamy has joined #openstack-meeting23:24
*** Sridhar__ has joined #openstack-meeting23:26
*** SridharR_ has quit IRC23:27
*** emagana has joined #openstack-meeting23:28
*** SridharRamaswamy has quit IRC23:28
*** reed has joined #openstack-meeting23:33
*** padkrish_ has quit IRC23:34
*** otoolee has quit IRC23:35
*** padkrish has joined #openstack-meeting23:35
*** cgoncalves has quit IRC23:36
*** cgoncalves has joined #openstack-meeting23:37
*** emagana has quit IRC23:39
*** noslzzp has quit IRC23:39
*** emagana has joined #openstack-meeting23:39
*** padkrish has quit IRC23:39
*** hrybacki has joined #openstack-meeting23:40
*** otoolee- has joined #openstack-meeting23:40
*** rfolco has quit IRC23:41
*** emagana has quit IRC23:42
*** Murali has joined #openstack-meeting23:42
*** emagana has joined #openstack-meeting23:43
*** noslzzp has joined #openstack-meeting23:43
*** nati_ueno has joined #openstack-meeting23:45
*** sdake_ has quit IRC23:45
*** Sridhar__ has quit IRC23:46
*** SridharRamaswamy has joined #openstack-meeting23:46
*** emagana has quit IRC23:47
*** Murali has quit IRC23:47
*** fnaval has quit IRC23:51
*** SridharRamaswamy has quit IRC23:51
*** fnaval has joined #openstack-meeting23:51
*** andreaf has joined #openstack-meeting23:53
*** otherwiseguy has quit IRC23:54
*** Ish__ has quit IRC23:54
*** rfolco has joined #openstack-meeting23:54
*** bdpayne_ has quit IRC23:54
*** andreaf_ has quit IRC23:56
*** fnaval has quit IRC23:56
*** bdpayne has joined #openstack-meeting23:56
*** andreaf has quit IRC23:56
*** andreaf has joined #openstack-meeting23:57
*** tsekiyam_ has joined #openstack-meeting23:59
*** fnaval has joined #openstack-meeting23:59

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