Tuesday, 2014-07-08

*** prad has joined #openstack-meeting00:01
*** ArxCruz has quit IRC00:02
*** acoles has quit IRC00:04
*** jang has joined #openstack-meeting00:04
*** yamahata has quit IRC00:05
*** Michalik_ has joined #openstack-meeting00:06
*** s3wong has quit IRC00:07
*** carl_baldwin has quit IRC00:10
*** leeantho has quit IRC00:13
*** prad has quit IRC00:13
*** sweston has joined #openstack-meeting00:17
*** sweston_ has joined #openstack-meeting00:18
*** mestery has joined #openstack-meeting00:20
*** MaxV has joined #openstack-meeting00:22
*** yingjun has joined #openstack-meeting00:22
*** IlyaE has quit IRC00:23
*** salv-orlando has quit IRC00:24
*** mestery has quit IRC00:25
*** imsurit has joined #openstack-meeting00:26
*** MaxV has quit IRC00:26
*** tsekiyam_ has joined #openstack-meeting00:26
*** gokrokve has quit IRC00:28
*** tsekiya__ has joined #openstack-meeting00:28
*** gokrokve has joined #openstack-meeting00:29
*** IlyaE has joined #openstack-meeting00:29
*** tsekiyama has quit IRC00:30
*** sarob has quit IRC00:30
*** zehicle has quit IRC00:30
*** zehicle_at_dell has quit IRC00:31
*** zehicle_at_dell has joined #openstack-meeting00:31
*** tsekiyam_ has quit IRC00:32
*** gokrokve has quit IRC00:33
*** padkrish has quit IRC00:34
*** trey_h has quit IRC00:35
*** trey_h has joined #openstack-meeting00:36
*** epico has joined #openstack-meeting00:36
*** ujuc has joined #openstack-meeting00:39
*** ujuc_ has joined #openstack-meeting00:40
*** ujuc has quit IRC00:40
*** trey_h has quit IRC00:40
*** ayoung_dad_mode is now known as ayoung00:40
*** hemna is now known as hemna_00:40
*** zehicle has joined #openstack-meeting00:44
*** dwalleck has joined #openstack-meeting00:44
*** padkrish has joined #openstack-meeting00:44
*** dwalleck_ has joined #openstack-meeting00:47
*** dwalleck has quit IRC00:47
*** ujuc_ has quit IRC00:48
*** mestery has joined #openstack-meeting00:49
*** IlyaE has quit IRC00:50
*** mestery has quit IRC00:51
*** jamiem has quit IRC00:51
*** Penick has joined #openstack-meeting00:52
*** VijayB has quit IRC00:52
*** otter768 has joined #openstack-meeting00:52
*** fifieldt has joined #openstack-meeting00:55
*** fawadkhaliq has quit IRC00:55
*** yamahata has joined #openstack-meeting00:55
*** asettle has quit IRC00:57
*** liusheng has quit IRC01:02
*** shashankhegde has quit IRC01:03
*** mattgriffin has joined #openstack-meeting01:06
*** amcrn has quit IRC01:07
*** tsekiya__ has quit IRC01:07
*** mberlin has joined #openstack-meeting01:07
*** shakamunyi has quit IRC01:08
*** MaxV has joined #openstack-meeting01:09
*** mberlin1 has quit IRC01:10
*** MaxV has quit IRC01:13
*** VijayB has joined #openstack-meeting01:14
*** tkay has quit IRC01:15
*** otter768 has quit IRC01:15
*** marcoemorais has quit IRC01:16
*** trey_h has joined #openstack-meeting01:17
*** vivek-ebay has joined #openstack-meeting01:23
*** mtanino has quit IRC01:24
*** Daisy has joined #openstack-meeting01:25
*** tomoe_ has joined #openstack-meeting01:26
*** jackib has joined #openstack-meeting01:28
*** ivar-lazzaro1 has joined #openstack-meeting01:28
*** jackib has quit IRC01:29
*** ivar-lazzaro has quit IRC01:30
*** liusheng has joined #openstack-meeting01:32
*** trey_h has quit IRC01:32
*** trey_h has joined #openstack-meeting01:33
*** otter768 has joined #openstack-meeting01:35
*** ivar-lazzaro1 has quit IRC01:35
*** trey_h has quit IRC01:37
*** ivar-lazzaro has joined #openstack-meeting01:39
*** vivek-ebay has quit IRC01:39
*** ivar-lazzaro1 has joined #openstack-meeting01:41
*** shakamunyi has joined #openstack-meeting01:41
*** shakamunyi has quit IRC01:42
*** nosnos has joined #openstack-meeting01:42
*** haomai___ has quit IRC01:42
*** mestery has joined #openstack-meeting01:42
*** mestery has quit IRC01:42
*** mestery has joined #openstack-meeting01:42
*** haomaiwa_ has joined #openstack-meeting01:42
*** ivar-lazzaro has quit IRC01:43
*** ivar-lazzaro has joined #openstack-meeting01:44
*** ivar-lazzaro1 has quit IRC01:45
*** mattgriffin has quit IRC01:46
*** boh_ricky has joined #openstack-meeting01:47
*** ivar-lazzaro1 has joined #openstack-meeting01:48
*** Mandell has quit IRC01:49
*** e-vad has joined #openstack-meeting01:50
*** ivar-lazzaro has quit IRC01:50
*** carl_baldwin has joined #openstack-meeting01:51
*** shakamunyi has joined #openstack-meeting01:51
*** Mandell has joined #openstack-meeting01:51
*** shakamunyi has quit IRC01:51
*** vivek-ebay has joined #openstack-meeting01:52
*** shakamunyi has joined #openstack-meeting01:52
*** shakamunyi has quit IRC01:52
*** ivar-lazzaro1 has quit IRC01:52
*** vivek-ebay has quit IRC01:52
*** shakamunyi has joined #openstack-meeting01:53
*** shakamunyi has quit IRC01:53
*** e-vad has left #openstack-meeting01:53
*** boh_ricky has quit IRC01:55
*** ivar-lazzaro has joined #openstack-meeting01:55
*** haomai___ has joined #openstack-meeting01:58
*** haomaiwa_ has quit IRC01:59
*** Mandell has quit IRC02:00
*** shakamunyi has joined #openstack-meeting02:02
*** zehicle_at_dell has quit IRC02:02
*** zehicle_at_dell has joined #openstack-meeting02:03
*** arnaud__ has quit IRC02:03
*** safchain_ has quit IRC02:07
*** zhiyan_ is now known as zhiyan02:08
*** ArxCruz has joined #openstack-meeting02:08
*** MaxV has joined #openstack-meeting02:10
*** fnaval has joined #openstack-meeting02:11
*** padkrish has quit IRC02:14
*** MaxV has quit IRC02:14
*** eghobo has quit IRC02:15
*** mestery has quit IRC02:15
*** stevemar has quit IRC02:17
*** jjmb has quit IRC02:23
*** trey_h has joined #openstack-meeting02:24
*** hrybacki has quit IRC02:27
*** trey_h has quit IRC02:28
*** adalbas has quit IRC02:31
*** hrybacki has joined #openstack-meeting02:33
*** manishg has joined #openstack-meeting02:34
*** novas0x2a|laptop has quit IRC02:34
*** jjmb has joined #openstack-meeting02:35
*** fnaval has quit IRC02:35
*** sweston has quit IRC02:36
*** sweston_ has quit IRC02:36
*** manishg_ has joined #openstack-meeting02:36
*** manishg_ has quit IRC02:36
*** ArxCruz has quit IRC02:36
*** manishg has quit IRC02:38
*** gokrokve has joined #openstack-meeting02:45
*** Edward-Zhang has joined #openstack-meeting02:45
*** SridharG has joined #openstack-meeting02:47
*** liusheng has quit IRC02:51
*** ramishra has joined #openstack-meeting02:52
*** liusheng has joined #openstack-meeting02:53
*** jckasper has joined #openstack-meeting02:56
*** gibi has joined #openstack-meeting03:00
*** jckasper has quit IRC03:01
*** jckasper has joined #openstack-meeting03:02
*** jjmb has quit IRC03:04
*** yisun has joined #openstack-meeting03:04
*** gokrokve has quit IRC03:05
*** sankarshan_away is now known as sankarshan03:06
*** fnaval has joined #openstack-meeting03:08
*** amcrn has joined #openstack-meeting03:08
*** paragan has joined #openstack-meeting03:08
*** paragan has joined #openstack-meeting03:08
*** MaxV has joined #openstack-meeting03:11
*** jjmb has joined #openstack-meeting03:12
*** SridharG has quit IRC03:13
*** rakhmerov has quit IRC03:13
*** mattgriffin has joined #openstack-meeting03:14
*** amotoki has joined #openstack-meeting03:14
*** IlyaE has joined #openstack-meeting03:15
*** MaxV has quit IRC03:15
*** otherwiseguy has joined #openstack-meeting03:16
*** chandan_kumar has joined #openstack-meeting03:17
*** gokrokve has joined #openstack-meeting03:18
*** rakhmerov has joined #openstack-meeting03:18
*** amcrn has quit IRC03:19
*** weshay has quit IRC03:22
*** nosnos has quit IRC03:22
*** dims has quit IRC03:24
*** gokrokve_ has joined #openstack-meeting03:25
*** mestery has joined #openstack-meeting03:26
*** Penick has quit IRC03:27
*** gokrokve has quit IRC03:28
*** mestery has quit IRC03:29
*** imsurit has quit IRC03:30
*** arnaud__ has joined #openstack-meeting03:30
*** Michalik_ has quit IRC03:32
*** Michalik_ has joined #openstack-meeting03:33
*** gokrokve has joined #openstack-meeting03:36
*** chandan_kumar has quit IRC03:36
*** chandan_kumar has joined #openstack-meeting03:36
*** armax has quit IRC03:38
*** gokrokve_ has quit IRC03:39
*** VijayB has quit IRC03:39
*** banix has quit IRC03:44
*** fnaval has quit IRC03:47
*** mattgriffin has quit IRC03:48
*** mattgriffin has joined #openstack-meeting03:48
*** marekd|away has quit IRC03:48
*** marekd|away has joined #openstack-meeting03:48
*** vjay has joined #openstack-meeting03:49
*** Leonr has joined #openstack-meeting03:52
*** coolsvap|afk is now known as coolsvap03:56
*** marcoemorais has joined #openstack-meeting03:57
*** marcoemorais has quit IRC03:57
*** hrybacki has quit IRC03:59
*** mestery has joined #openstack-meeting04:00
*** Edward-Zhang has quit IRC04:00
*** hemna__ has joined #openstack-meeting04:04
*** mestery has quit IRC04:05
*** gokrokve_ has joined #openstack-meeting04:07
*** blogan is now known as zz_blogan04:09
*** hemna__ has quit IRC04:11
*** MaxV has joined #openstack-meeting04:11
*** gokrokve has quit IRC04:11
*** rajeshr has joined #openstack-meeting04:13
*** otherwiseguy has quit IRC04:13
*** terryw has joined #openstack-meeting04:13
*** gokrokve_ has quit IRC04:14
*** gokrokve has joined #openstack-meeting04:15
*** otter768 has quit IRC04:16
*** MaxV has quit IRC04:16
*** pradipta_away is now known as pradipta04:17
*** vivek-ebay has joined #openstack-meeting04:18
*** gokrokve has quit IRC04:20
*** aswadr has joined #openstack-meeting04:20
*** IlyaE has quit IRC04:21
*** emagana has joined #openstack-meeting04:21
*** nosnos has joined #openstack-meeting04:25
*** shankar has joined #openstack-meeting04:26
*** eghobo has joined #openstack-meeting04:27
*** Sukhdev_ has joined #openstack-meeting04:28
*** gokrokve has joined #openstack-meeting04:30
*** Daisy has quit IRC04:30
*** Sukhdev_ has quit IRC04:33
*** Sukhdev_ has joined #openstack-meeting04:33
*** crc32 has quit IRC04:34
*** Daisy has joined #openstack-meeting04:35
*** ngoswami has joined #openstack-meeting04:36
*** dwalleck_ has quit IRC04:37
*** gokrokve_ has joined #openstack-meeting04:37
*** Edward-Zhang has joined #openstack-meeting04:38
*** gokrokve has quit IRC04:39
*** bdpayne has joined #openstack-meeting04:42
*** SridharG has joined #openstack-meeting04:45
*** rakesh_hs has joined #openstack-meeting04:46
*** imsurit has joined #openstack-meeting04:46
*** dwalleck has joined #openstack-meeting04:47
*** gokrokve has joined #openstack-meeting04:50
*** amitpp has joined #openstack-meeting04:50
*** gokrokve_ has quit IRC04:52
*** shankar has quit IRC04:54
*** dwalleck has quit IRC04:55
*** gokrokve_ has joined #openstack-meeting04:56
*** gokrokve has quit IRC04:57
*** dims has joined #openstack-meeting04:58
*** natarajk_ has joined #openstack-meeting04:58
*** chandan_kumar has quit IRC04:58
*** s3wong has joined #openstack-meeting04:58
*** dwalleck has joined #openstack-meeting04:59
*** natarajk has joined #openstack-meeting04:59
*** sweston has joined #openstack-meeting04:59
yamahatahello05:01
s3wonghi05:01
natarajkhi05:01
dougwigo/05:01
*** Mandell has joined #openstack-meeting05:01
yamahata#startmeeting servicevm-device-manager05:01
openstackMeeting started Tue Jul  8 05:01:38 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
*** mestery has joined #openstack-meeting05:01
yamahatawow so many people05:01
yamahata#topic Announcement05:02
*** openstack changes topic to "Announcement (Meeting topic: servicevm-device-manager)"05:02
yamahatatoday bob skips meeting unfortunately05:02
yamahataI pushed first code to gerrit system05:02
*** dims has quit IRC05:02
dougwiglink?05:02
yamahata#link https://review.openstack.org/#/q/status:open+project:stackforge/tacker+branch:master+topic:bp/tacker-api,n,z05:02
yamahata#link https://review.openstack.org/#/q/status:open+project:stackforge/python-tackerclient+branch:master+topic:bp/tacker-api,n,z05:03
yamahataAlthough it needs api review and code review,  obvious patch(removing neutron file, rename neutron -> tacker) can be merged at first.05:03
*** sankarshan is now known as sankarshan_away05:03
*** sankarshan_away is now known as sankarshan05:03
yamahataI marked it as obvious by adding my +1.05:03
*** chandan_kumar has joined #openstack-meeting05:04
yamahataIf you have any issues on those obvious patches,  please add -1 and push it back to me.05:04
*** chandan_kumar has quit IRC05:04
*** gokrokve has joined #openstack-meeting05:04
*** chandankumar has joined #openstack-meeting05:04
yamahataThe server can run as standalone server and provides its api.05:04
*** gokrokve has quit IRC05:05
yamahataThe next things to do is to refine API and implement l3-plugin with servicevm server.05:05
*** emagana has quit IRC05:05
yamahataI've uploaded a blueprint for l3-plugin with servicevm05:05
*** gokrokve_ has quit IRC05:05
*** mestery has quit IRC05:06
*** Mandell has quit IRC05:06
s3wongyamahata: link?05:06
yamahata#link https://review.openstack.org/#/c/105078/05:06
*** emagana has joined #openstack-meeting05:06
yamahataSo we show the roadmap for servicevm and Bob and Karthik can push their own specs/patches as in future it can be consolidated based on roadmap05:07
natarajkyamahata: thanks for links. I'll review this week.05:08
yamahataFor api review I've upload it to gerrit05:08
yamahata#link https://review.openstack.org/#/c/103724/05:08
yamahatathat's all from me to announce.05:09
yamahataanyone else to announce?05:09
*** Daisy has quit IRC05:09
*** shakamunyi has quit IRC05:09
yamahataseems nothing. let's move on05:10
*** emagana_ has joined #openstack-meeting05:10
*** pradipta is now known as pradipta_away05:10
*** emagana has quit IRC05:10
yamahata#topic Open Discussion05:10
*** openstack changes topic to "Open Discussion (Meeting topic: servicevm-device-manager)"05:10
yamahata#undo05:11
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x2c8c510>05:11
yamahata#topic servicevm spec review05:11
*** openstack changes topic to "servicevm spec review (Meeting topic: servicevm-device-manager)"05:11
yamahataDo we have anything to discuss with API now?05:11
yamahataThe detailed discussion can be done with gerrit.05:11
s3wongyamahata: sure05:12
yamahataAt least Bob gave his feedback on google-doc. So I'll address them.05:12
yamahataOkay seems nothing.05:12
*** MaxV has joined #openstack-meeting05:12
yamahata#topic Open Discussion05:12
*** openstack changes topic to "Open Discussion (Meeting topic: servicevm-device-manager)"05:12
yamahataDoes anyone have anything?05:13
*** Mandell has joined #openstack-meeting05:13
yamahataIf no, I'd like to discuss on dnrm.05:14
*** Mandell has quit IRC05:14
*** Mandell has joined #openstack-meeting05:14
yamahatanatarajk: So far I've thought on how to consolidate/integrate dnrm code.05:14
yamahatanatarajk: let me check my understanding.05:14
*** gyee has quit IRC05:14
*** emagana_ has quit IRC05:15
natarajkyamahata: sure, go ahead05:15
*** dwalleck has quit IRC05:15
yamahataAt first, the terminology is quite different.05:15
*** dwalleck has joined #openstack-meeting05:15
yamahataWith dnrm terminology, resource is ~= VM. it might be physical appliance or virtual appliance.05:16
natarajkYes05:16
yamahatawith servicevm terminology, it's hosting device. or simply device05:16
*** MaxV has quit IRC05:16
natarajkDo you mention the hosting device as "resource" in your spec ?05:17
yamahataDo you stick to "resource"? or is "hosting device" acceptable?05:17
yamahatanatarajk: yes.05:18
yamahataI think mostly same meaning.05:18
*** cjellick_ has quit IRC05:18
*** Mandell has quit IRC05:18
yamahataOr any better terminology?05:18
natarajkfor physical appliance, "hosting device" terminology might be confusing05:18
*** cjellick has joined #openstack-meeting05:19
*** bdpayne has quit IRC05:19
*** cjellick has quit IRC05:19
*** vivek-ebay has quit IRC05:19
*** cjellick has joined #openstack-meeting05:19
yamahataTo be honest, I don't care which terminology personally.05:20
*** changbl has quit IRC05:20
*** cjellick_ has joined #openstack-meeting05:20
yamahataBob introduced "hosting device".05:20
yamahataUnfortunately we don't have Bob today, let's continue at gerrit or next meeting05:20
yamahatacontinue the discussion05:21
natarajkOk. we need to find something common on for both virtual and physical appliance, i guess05:21
yamahataYes.05:21
natarajkif it's only virtual appliance, "hosting device" might be ok.05:21
yamahataOkay, then next termnology is "driver".05:22
natarajkwe can continue the discussion.05:22
yamahataI think "driver" in dnrm is the code to spin up/donw VM and so on.05:23
yamahataCorrect?05:23
*** cjellick has quit IRC05:23
natarajkYes. But we are open to common terms there05:24
natarajklet me read your specs in detail this week.05:24
yamahataI just confirmed to make sure. "driver" is common.05:24
*** cjellick_ has quit IRC05:24
yamahataThe dnrm code doesn't allow "template" in servicevm terminology.05:25
yamahatabasically "template" is "driver" name + parameters to nova client.05:25
*** gokrokve has joined #openstack-meeting05:25
yamahataSo i think "template" is superset of dnrm "driver"05:26
natarajkYes. Those were made as configurable in plugin configuration file05:26
yamahataIs it acceptalbe to use "template" instead of dnrm "driver"?05:27
*** bdpayne has joined #openstack-meeting05:27
yamahataFor dnrm driver, no parameter will be specified.05:27
*** gokrokve_ has joined #openstack-meeting05:27
natarajkthinking ...05:28
*** Sukhdev_ has quit IRC05:28
*** Daisy has joined #openstack-meeting05:28
yamahataAh, this is not a final call. We can discuss with actual code later.05:28
yamahataI'd like to check my direction with others.05:28
*** dwalleck_ has joined #openstack-meeting05:28
yamahatabefore starting actual coding.05:29
*** terryw has quit IRC05:29
s3wongyamahata: if the parameters are for provider (service drivers) to initialize, it is more commonly driver entry point, or in flavor framework it is metadata05:29
*** dwalleck has quit IRC05:29
yamahataMaybe I should write details it in spec.05:29
*** ildikov has joined #openstack-meeting05:30
swestonyamahata: we will need some time to review this.  May we sync up with you later in the week?05:30
yamahatas3wong: Agree. Later we can utilize flavor framework05:30
yamahatasweston: Sure.05:30
*** gokrokve has quit IRC05:30
s3wongyamahata: reminder: last week we agreed that this meeting will be 30 minutes :-)05:31
yamahataWe don't have to have conclusion now.05:31
swestonyamahata: thanks05:31
yamahatas3wong: thanks.05:31
yamahataanything else to discuss?05:31
yamahataokay thanks everyone. see you next week.05:32
s3wongthanks!05:32
natarajkthanks05:32
yamahata#endmeeting05:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:32
openstackMeeting ended Tue Jul  8 05:32:32 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-07-08-05.01.html05:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-07-08-05.01.txt05:32
openstackLog:            http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-07-08-05.01.log.html05:32
*** natarajk has left #openstack-meeting05:34
*** Michalik_ has quit IRC05:34
*** emagana has joined #openstack-meeting05:36
*** carl_baldwin has quit IRC05:37
*** dwalleck_ has quit IRC05:41
*** jtomasek has joined #openstack-meeting05:42
*** harlowja is now known as harlowja_away05:42
*** Longgeek has joined #openstack-meeting05:43
*** yingjun has quit IRC05:45
*** yingjun has joined #openstack-meeting05:45
*** emagana has quit IRC05:45
*** gokrokve has joined #openstack-meeting05:46
*** ItSANgo_ has quit IRC05:48
*** yingjun has quit IRC05:49
*** shashankhegde has joined #openstack-meeting05:50
*** gokrokve_ has quit IRC05:50
*** eghobo has quit IRC05:50
*** JRobinson__ has quit IRC05:51
*** eghobo has joined #openstack-meeting05:51
*** gokrokve_ has joined #openstack-meeting05:53
*** mrunge has joined #openstack-meeting05:53
*** ramishra has quit IRC05:55
*** gokrokve has quit IRC05:56
*** IlyaE has joined #openstack-meeting05:57
*** dims has joined #openstack-meeting05:58
*** epico has quit IRC06:00
*** mestery has joined #openstack-meeting06:02
*** dims has quit IRC06:03
*** ramishra has joined #openstack-meeting06:05
*** ItSANgo has joined #openstack-meeting06:05
*** mestery has quit IRC06:06
*** reed has quit IRC06:07
*** Michalik_ has joined #openstack-meeting06:07
*** oanufriev has quit IRC06:08
*** Macaveli has joined #openstack-meeting06:08
*** Mandell has joined #openstack-meeting06:10
*** gokrokve_ has quit IRC06:11
*** Michalik_ has quit IRC06:11
*** gokrokve has joined #openstack-meeting06:12
*** bdpayne has quit IRC06:12
*** MaxV has joined #openstack-meeting06:13
*** epico has joined #openstack-meeting06:13
*** sarob has joined #openstack-meeting06:15
*** gokrokve has quit IRC06:16
*** MaxV has quit IRC06:17
*** mattgriffin has quit IRC06:19
*** cjellick has joined #openstack-meeting06:21
*** zigo has quit IRC06:27
*** cjellick has quit IRC06:28
*** sweston has quit IRC06:30
*** sweston has joined #openstack-meeting06:31
*** emagana has joined #openstack-meeting06:31
*** zigo has joined #openstack-meeting06:31
*** emagana has quit IRC06:36
*** Nisha_ has joined #openstack-meeting06:38
*** shashankhegde has quit IRC06:42
*** shashankhegde has joined #openstack-meeting06:42
*** MaxV has joined #openstack-meeting06:44
*** epico has quit IRC06:46
*** sarob has quit IRC06:49
*** nacim has quit IRC06:51
*** __afazekas is now known as afazekas06:55
*** gokrokve has joined #openstack-meeting06:56
*** shashankhegde has quit IRC06:58
*** yingjun has joined #openstack-meeting06:59
*** dims_ has joined #openstack-meeting06:59
*** belmoreira has joined #openstack-meeting06:59
*** gokrokve has quit IRC07:01
*** jcoufal has joined #openstack-meeting07:01
*** IlyaE has quit IRC07:03
*** mestery has joined #openstack-meeting07:03
*** jgallard has joined #openstack-meeting07:03
*** dims_ has quit IRC07:04
*** Mandell has quit IRC07:06
*** Michalik_ has joined #openstack-meeting07:06
*** HenryG has quit IRC07:07
*** mestery has quit IRC07:08
*** gongysh has joined #openstack-meeting07:08
*** luqas has joined #openstack-meeting07:09
*** imsurit has quit IRC07:10
*** Michalik_ has quit IRC07:11
*** Fdot has joined #openstack-meeting07:12
*** s3wong has quit IRC07:13
*** epico has joined #openstack-meeting07:13
*** yamamoto has quit IRC07:15
*** haomai___ has quit IRC07:17
*** haomaiwang has joined #openstack-meeting07:18
*** iyozhikov is now known as IgorYozhikov07:20
*** shakamunyi has joined #openstack-meeting07:22
*** IlyaE has joined #openstack-meeting07:28
*** eguz has joined #openstack-meeting07:30
*** eguz has quit IRC07:31
*** eghobo has quit IRC07:32
*** phil has joined #openstack-meeting07:32
*** IlyaE has quit IRC07:33
*** haomai___ has joined #openstack-meeting07:33
*** jtomasek_ has joined #openstack-meeting07:34
*** haomaiwang has quit IRC07:35
*** nati_ueno has quit IRC07:37
*** Macaveli has quit IRC07:38
*** jamiem has joined #openstack-meeting07:40
*** jtomasek has quit IRC07:40
*** Mandell has joined #openstack-meeting07:42
*** rajeshr has quit IRC07:42
*** SefaKoc_ has joined #openstack-meeting07:43
*** safchain_ has joined #openstack-meeting07:43
*** yamamoto has joined #openstack-meeting07:44
*** yamamoto has quit IRC07:46
*** shakamunyi has quit IRC07:46
*** Mandell has quit IRC07:46
*** jamiem has quit IRC07:48
*** jamespage_ has joined #openstack-meeting07:52
*** akuznetsov has quit IRC07:54
*** akuznetsov has joined #openstack-meeting07:55
*** gokrokve has joined #openstack-meeting07:56
*** jlibosva has joined #openstack-meeting07:56
*** pradipta_away is now known as pradipta07:58
*** yamamoto has joined #openstack-meeting07:58
*** markvan_ has quit IRC07:58
*** nacim has joined #openstack-meeting08:00
*** gokrokve has quit IRC08:00
*** luqas has quit IRC08:01
*** luqas has joined #openstack-meeting08:03
*** mestery has joined #openstack-meeting08:04
*** Longgeek has quit IRC08:05
*** flaper87|afk is now known as flaper8708:06
*** Longgeek has joined #openstack-meeting08:06
*** ryansb has quit IRC08:06
*** Michalik_ has joined #openstack-meeting08:07
*** mestery has quit IRC08:09
*** IgorYozhikov is now known as iyozhikov08:09
*** IvanBerezovskiy has joined #openstack-meeting08:11
*** IvanBerezovskiy has left #openstack-meeting08:11
*** ttrifonov_zZzz is now known as ttrifonov08:11
*** Michalik_ has quit IRC08:11
*** hashar has joined #openstack-meeting08:12
*** Macaveli has joined #openstack-meeting08:12
*** derekh_ has joined #openstack-meeting08:16
*** yamamoto has quit IRC08:17
*** SefaKoc_ has quit IRC08:17
*** xianghui has joined #openstack-meeting08:18
*** ndipanov has joined #openstack-meeting08:19
*** emagana has joined #openstack-meeting08:19
*** Longgeek_ has joined #openstack-meeting08:21
*** ityaptin has joined #openstack-meeting08:21
*** idegtiarov has quit IRC08:22
*** ildikov has quit IRC08:23
*** emagana has quit IRC08:24
*** Longgeek has quit IRC08:24
*** julienvey has joined #openstack-meeting08:26
*** overlayer has joined #openstack-meeting08:26
*** emagana has joined #openstack-meeting08:27
*** ildikov has joined #openstack-meeting08:28
*** dims has joined #openstack-meeting08:28
*** oanufriev has joined #openstack-meeting08:28
*** yamamoto has joined #openstack-meeting08:28
*** radez_g0n3 is now known as radez08:30
*** ygbo has joined #openstack-meeting08:30
*** emagana has quit IRC08:31
*** yamamoto has quit IRC08:31
*** dims has quit IRC08:33
*** Longgeek_ has quit IRC08:35
*** Longgeek has joined #openstack-meeting08:36
*** _nadya_ has joined #openstack-meeting08:39
*** andreaf has quit IRC08:40
*** andreaf_ is now known as andreaf08:40
*** overlayer has quit IRC08:40
*** andreaf_ has joined #openstack-meeting08:40
*** igordcard has joined #openstack-meeting08:40
*** ramishra has quit IRC08:41
*** idegtiarov has joined #openstack-meeting08:42
*** luqas has quit IRC08:46
*** luqas has joined #openstack-meeting08:48
*** kayaliu_ has joined #openstack-meeting08:48
*** luqas has quit IRC08:50
*** sarob has joined #openstack-meeting08:50
*** sarob has quit IRC08:54
*** gokrokve has joined #openstack-meeting08:56
*** phil has quit IRC08:57
*** Longgeek_ has joined #openstack-meeting08:58
*** phil has joined #openstack-meeting08:59
*** rajeshr has joined #openstack-meeting08:59
*** gokrokve has quit IRC09:00
*** pradipta is now known as pradipta_away09:01
*** Longgeek has quit IRC09:01
*** yamamoto has joined #openstack-meeting09:02
*** pelix has joined #openstack-meeting09:03
*** yamamoto has quit IRC09:04
*** yamamoto has joined #openstack-meeting09:04
*** mestery has joined #openstack-meeting09:05
*** HenryG has joined #openstack-meeting09:05
*** Michalik_ has joined #openstack-meeting09:07
*** ildikov has quit IRC09:07
*** arnaud__ has quit IRC09:09
*** yamamoto has quit IRC09:09
*** mestery has quit IRC09:09
*** Michalik_ has quit IRC09:12
*** _nadya_ has quit IRC09:12
*** haomai___ has quit IRC09:13
*** haomaiwa_ has joined #openstack-meeting09:14
*** mrunge is now known as mrunge_bbl09:16
*** Longgeek_ has quit IRC09:18
*** Longgeek has joined #openstack-meeting09:19
*** emagana has joined #openstack-meeting09:21
*** Longgeek_ has joined #openstack-meeting09:25
*** emagana has quit IRC09:25
*** Longgeek has quit IRC09:25
*** _nadya_ has joined #openstack-meeting09:26
*** Daisy has quit IRC09:27
*** yingjun has quit IRC09:28
*** JRobinson__ has joined #openstack-meeting09:28
*** dims has joined #openstack-meeting09:29
*** Edward-Zhang has quit IRC09:29
*** oanufriev has quit IRC09:29
*** oanufriev has joined #openstack-meeting09:29
*** ildikov has joined #openstack-meeting09:30
*** haomaiw__ has joined #openstack-meeting09:30
*** luqas has joined #openstack-meeting09:30
*** haomaiwa_ has quit IRC09:32
*** dims has quit IRC09:33
*** _nadya_ has quit IRC09:35
*** imsurit has joined #openstack-meeting09:35
*** coolsvap has quit IRC09:37
*** ngoswami_ has joined #openstack-meeting09:40
*** coolsvap has joined #openstack-meeting09:41
*** amitpp has quit IRC09:41
*** ngoswami has quit IRC09:42
*** Mandell has joined #openstack-meeting09:43
*** Nisha_ has quit IRC09:43
*** _nadya_ has joined #openstack-meeting09:45
*** Mandell has quit IRC09:47
*** jcoufal has quit IRC09:48
*** jamespage_ has quit IRC09:50
*** tomoe_ has quit IRC09:52
*** jackib has joined #openstack-meeting09:53
*** shakamunyi has joined #openstack-meeting09:56
*** gokrokve has joined #openstack-meeting09:56
*** _nadya_ has quit IRC09:56
*** sankarshan is now known as sankarshan_away09:57
*** ryansb has joined #openstack-meeting09:57
*** haomaiw__ has quit IRC09:59
*** haomaiwang has joined #openstack-meeting09:59
*** _nadya_ has joined #openstack-meeting10:00
*** alexpilotti has joined #openstack-meeting10:00
*** alexpilotti has quit IRC10:00
*** ominakov has joined #openstack-meeting10:01
*** gokrokve has quit IRC10:01
*** yamahata has quit IRC10:02
*** yamamoto has joined #openstack-meeting10:03
*** _nadya_ has quit IRC10:04
*** kopparam has joined #openstack-meeting10:04
*** oomichi has quit IRC10:04
*** tomoe_ has joined #openstack-meeting10:07
*** tomoe_ has quit IRC10:07
*** yamamoto has quit IRC10:08
*** Michalik_ has joined #openstack-meeting10:08
*** Michalik_ has quit IRC10:13
*** _nadya_ has joined #openstack-meeting10:14
*** MaxV has quit IRC10:14
*** jgallard has quit IRC10:14
*** haomaiw__ has joined #openstack-meeting10:14
*** emagana has joined #openstack-meeting10:15
*** haomaiwang has quit IRC10:18
*** epico has quit IRC10:18
*** MaxV has joined #openstack-meeting10:19
*** emagana has quit IRC10:19
*** shakamunyi has quit IRC10:20
*** _nadya_ has quit IRC10:23
*** JRobinson__ has quit IRC10:25
*** yaguang has joined #openstack-meeting10:26
*** Leonr has quit IRC10:33
*** paragan has quit IRC10:35
*** alexpilotti has joined #openstack-meeting10:37
*** sankarshan_away is now known as sankarshan10:39
*** sankarshan is now known as sankarshan_away10:39
*** shankar has joined #openstack-meeting10:44
*** zhiyan is now known as zhiyan_10:46
*** zhiyan_ is now known as zhiyan10:47
*** hashar has quit IRC10:47
*** julienvey has quit IRC10:53
*** nacim has quit IRC10:53
*** jackib has quit IRC10:53
*** jcoufal has joined #openstack-meeting10:56
*** gokrokve has joined #openstack-meeting10:56
*** rajeshr has quit IRC10:57
*** kayaliu_ has quit IRC10:57
*** gokrokve has quit IRC11:01
*** dims_ has joined #openstack-meeting11:02
*** yamamoto has joined #openstack-meeting11:03
*** mestery has joined #openstack-meeting11:07
*** yamamoto has quit IRC11:08
*** Michalik_ has joined #openstack-meeting11:09
*** emagana has joined #openstack-meeting11:09
*** kayaliu_ has joined #openstack-meeting11:11
*** mestery has quit IRC11:11
*** emagana has quit IRC11:13
*** Michalik_ has quit IRC11:14
*** yaguang has quit IRC11:15
*** xianghui has quit IRC11:16
*** kayaliu_ has quit IRC11:16
*** tedross has joined #openstack-meeting11:17
*** nosnos has quit IRC11:23
*** julim has joined #openstack-meeting11:25
*** amitpp has joined #openstack-meeting11:25
*** coolsvap is now known as coolsvap|afk11:28
*** Macaveli has quit IRC11:33
*** adalbas has joined #openstack-meeting11:38
*** julienvey has joined #openstack-meeting11:39
*** mrunge_bbl is now known as mrunge11:40
*** jgallard has joined #openstack-meeting11:40
*** jamiem has joined #openstack-meeting11:41
*** julienvey has quit IRC11:43
*** Mandell has joined #openstack-meeting11:44
*** julienvey has joined #openstack-meeting11:48
*** Mandell has quit IRC11:48
*** radez is now known as radez_g0n311:49
*** emagana has joined #openstack-meeting11:49
*** emagana has quit IRC11:54
*** Longgeek_ has quit IRC11:54
*** gokrokve has joined #openstack-meeting11:56
*** aloga has quit IRC11:58
*** sweston has quit IRC11:58
*** aloga has joined #openstack-meeting11:58
*** ArxCruz has joined #openstack-meeting11:59
*** DuncanT- has quit IRC11:59
*** pelix has quit IRC12:00
*** SridharG has quit IRC12:00
*** Longgeek has joined #openstack-meeting12:00
*** vjay has quit IRC12:01
*** jdob has joined #openstack-meeting12:01
*** gokrokve has quit IRC12:01
*** yamamoto has joined #openstack-meeting12:03
*** weshay has joined #openstack-meeting12:03
*** Macaveli has joined #openstack-meeting12:05
*** salv-orlando has joined #openstack-meeting12:07
*** mestery has joined #openstack-meeting12:08
*** yamamoto has quit IRC12:08
*** eharney has joined #openstack-meeting12:08
*** aysyd has joined #openstack-meeting12:08
*** tomoe_ has joined #openstack-meeting12:09
*** Michalik_ has joined #openstack-meeting12:10
*** Sukhdev_ has joined #openstack-meeting12:11
*** markmcclain has joined #openstack-meeting12:11
*** mestery has quit IRC12:12
*** markmcclain1 has joined #openstack-meeting12:13
*** tomoe_ has quit IRC12:14
*** Michalik_ has quit IRC12:15
*** markmcclain has quit IRC12:16
*** bauzas has quit IRC12:17
*** dprince has joined #openstack-meeting12:17
*** Sukhdev_ has quit IRC12:19
*** kopparam has quit IRC12:23
*** yaguang has joined #openstack-meeting12:24
*** kopparam has joined #openstack-meeting12:25
*** luqas has quit IRC12:25
*** SefaKoc_ has joined #openstack-meeting12:25
*** dims_ has quit IRC12:26
*** dims_ has joined #openstack-meeting12:26
*** dims_ has quit IRC12:27
*** dims_ has joined #openstack-meeting12:28
*** nacim has joined #openstack-meeting12:30
*** bauzas has joined #openstack-meeting12:32
*** shakamunyi has joined #openstack-meeting12:37
*** kopparam has quit IRC12:37
*** xianghui has joined #openstack-meeting12:38
*** kayaliu_ has joined #openstack-meeting12:40
*** jgrimm has quit IRC12:42
*** hashar has joined #openstack-meeting12:42
*** SefaKoc_ has quit IRC12:44
*** morganfainberg is now known as morganfainberg_Z12:46
*** jackib has joined #openstack-meeting12:47
*** luqas has joined #openstack-meeting12:48
*** scott-millward has quit IRC12:49
*** pelix has joined #openstack-meeting12:50
*** xuhanp has joined #openstack-meeting12:53
*** yaguang has quit IRC12:54
*** Poornima has joined #openstack-meeting12:55
*** vjay has joined #openstack-meeting12:56
*** gokrokve has joined #openstack-meeting12:56
*** banix has joined #openstack-meeting12:56
*** cjellick has joined #openstack-meeting12:58
*** tedross has quit IRC13:01
*** gokrokve has quit IRC13:01
*** miqui has joined #openstack-meeting13:01
*** shakamunyi has quit IRC13:02
*** yamamoto has joined #openstack-meeting13:03
*** shankar has quit IRC13:04
*** yamamoto has quit IRC13:05
*** shakamunyi has joined #openstack-meeting13:05
*** shakamunyi has quit IRC13:05
*** yamamoto has joined #openstack-meeting13:05
*** markmcclain1 has quit IRC13:06
*** shakamunyi has joined #openstack-meeting13:06
*** mestery has joined #openstack-meeting13:08
*** tomoe_ has joined #openstack-meeting13:08
*** yamamoto has quit IRC13:09
*** Michalik_ has joined #openstack-meeting13:10
*** mestery has quit IRC13:13
*** bknudson has joined #openstack-meeting13:13
*** Michali__ has joined #openstack-meeting13:15
*** Michalik_ has quit IRC13:15
*** amitpp has quit IRC13:15
*** tedross has joined #openstack-meeting13:16
*** yaguang has joined #openstack-meeting13:17
*** HenryG has quit IRC13:17
*** jecarey has quit IRC13:23
*** amitpp has joined #openstack-meeting13:23
*** _nadya_ has joined #openstack-meeting13:24
*** oanufriev has quit IRC13:24
*** mestery has joined #openstack-meeting13:25
*** amitpp has quit IRC13:25
*** Adri2000_ is now known as Adri200013:27
*** andreaf has quit IRC13:28
*** _nadya_ has quit IRC13:28
*** Tross has quit IRC13:28
*** tbarron has joined #openstack-meeting13:29
*** DuncanT- has joined #openstack-meeting13:31
*** jang has quit IRC13:32
*** matiu has quit IRC13:33
*** ramishra has joined #openstack-meeting13:34
*** boh_ricky has joined #openstack-meeting13:36
*** oomichi has joined #openstack-meeting13:37
*** tedross has quit IRC13:37
*** jgrimm has joined #openstack-meeting13:38
*** mtanino has joined #openstack-meeting13:41
*** mattgriffin has joined #openstack-meeting13:42
*** matiu has joined #openstack-meeting13:45
*** SridharG has joined #openstack-meeting13:47
*** trey_h has joined #openstack-meeting13:49
*** yingjun has joined #openstack-meeting13:49
*** yamamoto has joined #openstack-meeting13:50
*** prad has joined #openstack-meeting13:52
*** tedross has joined #openstack-meeting13:53
*** yingjun has quit IRC13:53
*** IlyaE has joined #openstack-meeting13:56
*** gokrokve has joined #openstack-meeting13:56
*** hrybacki has joined #openstack-meeting13:57
*** BrianB_ has joined #openstack-meeting13:57
*** kakuma has quit IRC13:58
*** vjay has quit IRC13:59
*** zehicle_at_dell has quit IRC14:00
*** dane_leblanc has joined #openstack-meeting14:00
*** gokrokve has quit IRC14:01
*** jecarey has joined #openstack-meeting14:01
*** shakamunyi has quit IRC14:01
*** zehicle_at_dell has joined #openstack-meeting14:01
*** radez_g0n3 is now known as radez14:03
*** tomoe_ has quit IRC14:05
*** thangp has joined #openstack-meeting14:08
*** zul has quit IRC14:08
*** zul has joined #openstack-meeting14:08
*** ayoung has quit IRC14:09
*** gokrokve has joined #openstack-meeting14:10
*** yaguang has quit IRC14:11
*** gokrokve_ has joined #openstack-meeting14:11
*** flaper87 is now known as flaper87|afk14:11
*** gokrokve has quit IRC14:14
*** tomoe_ has joined #openstack-meeting14:15
*** gokrokve_ has quit IRC14:17
*** gokrokve has joined #openstack-meeting14:18
*** armax has joined #openstack-meeting14:19
*** vjay has joined #openstack-meeting14:19
*** david-lyle has joined #openstack-meeting14:19
*** ramishra has quit IRC14:20
*** mostly_d34dh0r53 is now known as d34dh0r5314:22
*** nelsnelson has joined #openstack-meeting14:22
*** gokrokve has quit IRC14:22
*** nelsnelson has quit IRC14:22
*** nelsnelson has joined #openstack-meeting14:23
*** vhoward- has joined #openstack-meeting14:23
*** Michali__ has quit IRC14:24
*** xuhanp has quit IRC14:28
*** ArxCruz has quit IRC14:28
*** ArxCruz has joined #openstack-meeting14:29
*** gongysh has quit IRC14:30
*** yaguang has joined #openstack-meeting14:31
*** vhoward- has left #openstack-meeting14:31
*** flaper87|afk is now known as flaper8714:34
*** sajeesh has joined #openstack-meeting14:36
*** markvan has joined #openstack-meeting14:37
*** gokrokve has joined #openstack-meeting14:37
*** vkmc has joined #openstack-meeting14:39
*** vkmc has quit IRC14:39
*** vkmc has joined #openstack-meeting14:39
*** jckasper has quit IRC14:40
*** mwagner_lap has joined #openstack-meeting14:42
*** rakesh_hs has quit IRC14:43
*** tonisbones has joined #openstack-meeting14:44
*** coasterz has joined #openstack-meeting14:45
*** otherwiseguy has joined #openstack-meeting14:45
*** ivasev has joined #openstack-meeting14:46
*** oomichi has quit IRC14:46
*** dane_leblanc has quit IRC14:47
*** thedodd has joined #openstack-meeting14:48
*** ericfriz has joined #openstack-meeting14:48
*** tonisbones has quit IRC14:48
*** coasterz has quit IRC14:49
*** lisaZ has joined #openstack-meeting14:49
*** gokrokve has quit IRC14:50
*** ramishra has joined #openstack-meeting14:51
*** coasterz has joined #openstack-meeting14:52
*** alexpilotti has quit IRC14:55
*** ramishra has quit IRC14:55
*** fnaval has joined #openstack-meeting14:57
*** coasterz has quit IRC14:57
*** Macaveli has quit IRC14:57
*** yingjun has joined #openstack-meeting14:58
*** kirankv has joined #openstack-meeting14:59
*** ildikov has quit IRC14:59
*** ildikov has joined #openstack-meeting14:59
*** tomoe_ has quit IRC14:59
*** Mandell has joined #openstack-meeting14:59
*** jckasper has joined #openstack-meeting14:59
*** coasterz has joined #openstack-meeting15:00
*** zhiyan is now known as zhiyan_15:00
*** imsurit has quit IRC15:00
n0ano#startmeeting gantt15:00
openstackMeeting started Tue Jul  8 15:00:38 2014 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: gantt)"15:00
openstackThe meeting name has been set to 'gantt'15:00
n0anoanyone here to talk about the scheduler?15:00
jaypipeso/15:00
bauzaso/15:00
bauzasuh, \o15:00
* n0ano mutters about lefties15:01
jaypipesheh15:01
*** mspreitz has joined #openstack-meeting15:01
mspreitzhi15:02
ericfrizhi15:02
lisaZhi15:02
n0anowell, we have 2 completely non-contentious items today, should be short :-)15:02
*** jckasper_ has joined #openstack-meeting15:02
n0ano#topic code forklift15:02
*** openstack changes topic to "code forklift (Meeting topic: gantt)"15:02
bauzasn0ano: don't promise that kind of thing :)15:02
n0anonote the smiley15:03
*** pballand has joined #openstack-meeting15:03
* bauzas has to learn bbcode15:03
*** yingjun has quit IRC15:03
*** Mandell has quit IRC15:03
*** nati_ueno has joined #openstack-meeting15:03
n0anoAs I read the email threads, the concensus seems to be...15:03
bauzasso I guess it's my turn ?15:03
n0ano1)  Clean up `all` of the nova APIs...15:03
n0ano2) Split out a fully functional gantt...15:04
bauzas3) Take a coffee and rest15:04
*** kirankv has quit IRC15:04
*** zehicle_at_dell has quit IRC15:04
n0ano3) Gantt immediately becomes the default scheduler15:04
bauzasindeed15:04
n0anowhat was your take bauzas15:04
*** jckasper has quit IRC15:04
bauzasyey, I thought about that15:05
bauzasI can understand the worries here15:05
bauzasso,15:05
bauzasI think the main difference is when we split15:06
*** nealph_ is now known as nealph15:06
*** changbl has joined #openstack-meeting15:06
jaypipesn0ano: it's step 1) that needs a lot of effort right now, IMO. 2) and 3) will naturally happen when the APIs are cleaned up.15:06
bauzasnot that much difference, because if Gantt code is 100% nova-scheduler, Tempest and CI would remain the same15:06
bauzasI'm just worried about 1)15:07
*** chandankumar has quit IRC15:07
bauzaswe need to get a consensus on them15:07
n0anojaypipes, I think 2) is harder than we think (based upon my experience the last time we tried to do the split), hence my perference (voted down) to do the split early rather than late15:07
*** Mandell has joined #openstack-meeting15:08
bauzasn0ano: I think you had difficulties because the code was not properly splitted15:08
n0anobauzas, the critical changes are the client library and the isolate db, both of which are being worked on15:08
jaypipesn0ano: the split will be much easier if 1) is done properly and fully.15:08
bauzasn0ano: yey, but for both of them, we don't have a full agreement over them15:08
bauzasn0ano: take your "delete aggregate" question15:09
bauzasn0ano: that's still something unmanaged15:09
*** Mandell has quit IRC15:09
n0anowell, it's pretty clear to me we're not going to make Juno so, as long as we stay focused on cleaning up the interfaces, we have time to do it right15:09
bauzasso, long story short, let's focus on 1)15:09
*** Poornima has quit IRC15:10
*** belmoreira has quit IRC15:10
*** gokrokve has joined #openstack-meeting15:10
*** coolsvap|afk is now known as coolsvap15:10
bauzasn0ano: that doesn't necessary mean we cannot work on updating Gantt as POC15:10
*** david-lyle has quit IRC15:10
jaypipesas an example, is it agreed that the new scheduler API will *fully own* the management of compute resources? I think the resource tracker should be moved entirely into the scheduler (it kind of already is with the HostStateManager) and the nova-compute workers should just call the scheduler API to update resource information15:10
*** david-lyle has joined #openstack-meeting15:11
bauzasjaypipes: the rationale behind the split was to be the less disruptive as possible15:11
n0anojaypipes, that sounds like a good idea to me, that should be more a code layout rather than an API change15:12
bauzasjaypipes: hence the idea of a scheduler library15:12
jaypipesbauzas: well, if we clean up the interface call signatures, don't you think a split would be less disriuptive?15:12
jaypipesn0ano: yes, agreed.15:12
bauzasis johnthetubaguy over here ?15:12
*** thinrichs has joined #openstack-meeting15:12
n0anobauzas, the client lib is still crucial, both for cleanly identifying the interface and for future users of gantt15:13
bauzasI still think the most crucial bp is how we isolate the scheduler15:14
*** vjay has quit IRC15:14
*** schwicke has joined #openstack-meeting15:14
n0anobauzas, +115:14
jaypipesn0ano: do we have a document somewhere that clearly lists all of the interfaces currently between nova-conductor and the scheduler and nova-compute and the scheduler (via the compute_node object, of course..)15:14
jaypipes?15:14
bauzasI mean, we can decide that ResourceTracker would be replaced by a new one, we would still have to manage a feature compatibility with the existing filters15:14
bauzasso we would still have to deal with aggregates or instance groups15:15
*** gokrokve_ has joined #openstack-meeting15:15
bauzasjaypipes: the spec I wrote about isolate-sched-db is the most effective one I thnik15:15
n0anobauzas, we're nt talking about a new ResourceTracker, just having the current code run in the gantt context15:15
jaypipesk15:15
*** vjay has joined #openstack-meeting15:16
*** nati_ueno has quit IRC15:16
bauzasn0ano: what do you mean by running in the gantt context ?15:16
*** carl_baldwin has joined #openstack-meeting15:17
*** gokrokve has quit IRC15:17
n0anoRT should be part of the scheduler (be it the current one or gantt), not part of nova15:17
*** nati_ueno has joined #openstack-meeting15:18
bauzasn0ano: well I can't see the whole interest of it15:19
bauzasn0ano: I mean if we say that RT would be owned by Gantt15:19
*** Michalik_ has joined #openstack-meeting15:19
*** tomoe_ has joined #openstack-meeting15:19
*** zehicle_at_dell has joined #openstack-meeting15:19
bauzasn0ano: what would be the interest of it?15:19
bauzasn0ano: the idea is that Gantt would provide a client that other projects could use15:20
*** reed has joined #openstack-meeting15:20
bauzasn0ano: so, to me, it's just saying that we could have a Resource API and a Schedule API15:20
bauzasI mean, whatever the project is, it updates the scheduler with its view of resources15:21
n0anoand part of that client interface would be resouce tracking, to me the resource API would just be a part of the scheduler api15:21
*** phil has quit IRC15:21
jaypipesagree with n0ano on this.15:21
*** nati_ueno has quit IRC15:22
n0anoI think we're in violent agreement, there15:22
n0anodidn't finish15:22
jaypipesbasically, part of the scheduler API should be "get me a set of claims that represent these requested sets of resources" and another part of the API should be "update your view of the state of resource usage on these resource providers"15:23
n0anojaypipes, +115:23
jaypipesthe claims piece is *currently* in the RT, not the scheduler, and that's what needs to be "cleaned up" in step 1), IMO.15:23
*** s3wong has joined #openstack-meeting15:24
bauzasjaypipes: well, I think I see a slight difference here15:24
jaypipesthe reason it's not as simple as just a layout change in the code is because the RT currently only handles claims for the nova-compute worker it is running in, whereas the moved claims code would need to handle all (or a subset) of compute nodes in the deployment15:24
*** nati_uen_ has joined #openstack-meeting15:24
bauzasjaypipes: to me, the resources are still owned by the project, but the project just reports use of the resources to the scheduler15:24
*** jrolson has joined #openstack-meeting15:25
jaypipesbauzas: I disagree (respectfully of course!). The resources are owned by the system (the scheduler), and are rented/leased to the project. The ultimate arbiter of resource usage and claims should always be the scheduler15:25
*** kebray has joined #openstack-meeting15:26
*** oanufriev has joined #openstack-meeting15:26
bauzasjaypipes: I see now your point15:26
bauzasjaypipes: that's what we tried to provide with Climate15:27
*** kebray has quit IRC15:27
n0anoI think I have to agree with jaypipes on this one15:27
bauzasjaypipes: the resources are owned by climate, but the execution is deferred to the project15:27
*** kebray has joined #openstack-meeting15:27
bauzasso that means we agreed on the fact that nova-computes are a scheduling resource, not a nova on15:28
bauzasone15:28
*** nealph_ has joined #openstack-meeting15:28
bauzaswoah, such a change, and we go back to what we discussed : compute_nodes should be a scheduler part15:29
bauzasjaypipes: so that also means that if you want to declare a new resource, it has to go to gantt, not nova15:29
n0anoI don't think it's that big a change, now the compute nodes send resource claim/usage to the scheduler, the way it should be done15:29
jaypipesn0ano: so, I agree with you that the nova-scheduler/gantt split will not happen in Juno. I think we should put together a doc on the existing "interfaces" between the nova-compute, nova-conductor, and nova-scheduler pieces, and clearly show what we'd like to change regarding the call signatures. I think that woudl be a good first building block. I think the isolate-db-scheduler blueprint would sort of naturally f15:30
jaypipesollow the completion of such a set of refactoring steps.15:30
jaypipesbauzas: yes, that is exactly correct.15:30
*** s3wong has quit IRC15:30
* bauzas is thinking that jaypipes has to see the Climate APIs...15:30
* jaypipes already knows the Climate APIs ;)15:31
bauzaswe defined a couple of time ago what we call a os-hosts api15:31
*** jlibosva has quit IRC15:31
jaypipesbauzas: they are on target for some things I'm talking about, but not other things... namely, the temporal aspect of the API reservations don't meet my needs.15:31
bauzasfor reserving hosts15:31
n0anothe good news is I don't think we need to change anything we are currently doing, just expand our scope a little bit15:32
*** ArxCruz has quit IRC15:32
*** nealph has quit IRC15:32
bauzasjaypipes: I'm not saying that Climate *is* Gantt15:32
jaypipesbauzas: oh, I know! I wasn't saying that either. :)15:32
bauzasjaypipes: I'm just saying that the concept of reserving a resource is close to schedule a resource :)15:32
jaypipesn0ano: s/expand/refine and expand/, but yeah.15:32
bauzaswoah, I still think that's a big change for nova, not just a refactoring thing15:33
jaypipesbauzas: well, it kind of is, but the additional aspect of date/time period (temporal) makes it more complicated than what needs to be in gantt..15:33
n0anowe have another topic today, let's think about what we're doing and try and clarify via email exactly what happens next15:33
*** emagana has joined #openstack-meeting15:33
* bauzas is just thinking about all the discussions he had with johnthetubaguy and a certain CRUD interface for Gantt...15:33
* jaypipes clearly lacks the historical context :(15:34
* johnthetubaguy felt that his name was called15:34
bauzasjohnthetubaguy: good to see you here :)15:34
johnthetubaguysorry, was in another meeting, but out of that now15:34
n0anojohnthetubaguy, might want to review the log but I want to move on to another topic now15:35
bauzasjohnthetubaguy: we're just discussing on the sched split, and jaypipes has an interesting PoV whose we agree15:35
johnthetubaguyn0ano: OK, will review the log15:35
n0anomoving on...15:35
n0ano#topic fair share scheduler15:35
*** openstack changes topic to "fair share scheduler (Meeting topic: gantt)"15:35
n0anolisaZ, still there?15:36
lisaZyes15:36
lisaZhi15:36
lisaZdid you receive our doc? any comments?15:36
n0anoI read your use case, looks interesting, how do you respond to the comment this this seems very similar to AWS spot intances?15:36
n0anos/intances/instances15:36
lisaZI already answered in the ML15:37
*** atiwari has joined #openstack-meeting15:37
bauzaslisaZ: and I did an update too15:37
lisaZour model is similar to the Amazon's spot instances model because both try to maximize the resource utilization. The main difference is the mechanism used for assigning resources to the users (the user's offer in terms of money vs the user's share). They differ even on how they release the allocated resources. In our model, the user, whenever requires the creation of a Type 3 VM, she has to select one of the possible types of "life time" (sho15:37
lisaZrt = 4 hours, medium = 24 hours, long = 48 hours). When the time expires, the VM is automatically released (if not explicitly released by the user).15:37
lisaZInstead, in Amazon, the spot instance is released whenever the spot price rises.15:37
n0anosorry, missed that15:37
*** yamamoto has quit IRC15:37
*** bknudson has quit IRC15:38
bauzaslisaZ: as I said, that's just a matter of stopping the instance on a certain event15:38
*** asettle has joined #openstack-meeting15:38
bauzaslisaZ: which can be triggered either by the price or whatever else15:38
*** jjmb has quit IRC15:38
johnthetubaguyinteresting, I assumed the user's VM could get evicted, if someone else who reserved the space wanted the slot you were "optimistically" allowed to take15:39
n0anoanyway, my concern is that, in many respects, your usage is more a data center use case rather than a cloud use case, do your needs really fit a cloud model15:39
johnthetubaguybut having all VMs leased for a specific amount of time is more like a batch processing system, and is an interesting alternative pattern15:39
*** sarob has joined #openstack-meeting15:39
*** changbl has quit IRC15:40
bauzasjohnthetubaguy: that's all the matter of guarantteing your lease or not15:41
*** gokrokve has joined #openstack-meeting15:41
johnthetubaguyyeah, its a grid computing view of the world, and really does change the meaning of the API, but I suspect we could do something for that use case, its just I expect the lease management will be outside of Nova for the moment15:41
*** Tross has joined #openstack-meeting15:41
*** changbl has joined #openstack-meeting15:41
johnthetubaguyand yeah, that sounds like some of what climate was looking at, but prehaps a little different15:41
johnthetubaguyI could see an API to request complete "slots" that is implemented by calling nova to create and delete servers15:42
*** igordcard has quit IRC15:42
*** nati_uen_ has quit IRC15:42
lisaZthe lease solves in part our problems15:42
*** shakamunyi has joined #openstack-meeting15:42
*** matiu has quit IRC15:42
*** s3wong has joined #openstack-meeting15:42
*** shakamunyi has quit IRC15:42
lisaZwe need a fair share algorithm which provides priorities on user requests15:43
*** Mandell has joined #openstack-meeting15:43
johnthetubaguylisaZ: would you idea work, if its something external to Nova, that just creates/deletes resources inside nova?15:43
*** gokrokve_ has quit IRC15:43
lisaZable to queue them if the resources are not available15:43
schwickeI think there is another difference: in Lisa's model requests which currently cannot be fulfilled because of lack of resources can be dispatched later on.15:43
schwickethat is a quite important as it helps a site to keep their resources busy15:44
bauzasschwicke: can't see why Climate couldn't handle that15:44
schwickethe idea of climate seems more like an advance reservation kind of scheduling, right ?15:45
lisaZClimate is not able to distinguish privileged users from the simple ones15:45
*** tedross has left #openstack-meeting15:45
lisaZClimate covers just one use case15:46
*** tsekiyama has joined #openstack-meeting15:46
*** amitpp has joined #openstack-meeting15:46
lisaZbut it is not enough15:46
johnthetubaguylisaZ: I would love if you thought about this as a separate API, and we work out what it does, then we can look at how to use bits of climate and nova to implement what you need15:47
bauzaslisaZ: that's what I called a best-effort mode for non-privileged users15:47
lisaZit is missing of the fair share algorithm15:47
*** vermarah_ has joined #openstack-meeting15:47
*** vermarah has joined #openstack-meeting15:47
lisaZcorrect15:47
lisaZfrom my point oh view15:48
*** markstur has joined #openstack-meeting15:48
lisaZblazar is a component above the scheduler15:48
bauzasjohnthetubaguy: +115:48
johnthetubaguyI see it almost like Heat, a description of things you want to create in Nova, but then there is some scheduling to give you the capacity you are allowed, balanced with other current requests in the system, rather than scaling up/down based on load15:48
bauzasright15:49
lisaZsuppose to replace the filter-scheduler with our fairsharescheduler15:49
lisaZin this scenario all our use case are implemented15:49
lisaZbecause blazar provides the missing15:49
lisaZfeature which is the advanced reservation15:49
johnthetubaguythe problem is the current nova API does not really model what you want to model15:49
lisaZwhy not?15:50
johnthetubaguyyou need uses to manage a queue of jobs, that may have an associated nova server15:50
lisaZit si just an advanced scheduler15:50
*** ArxCruz has joined #openstack-meeting15:50
*** ArxCruz has quit IRC15:50
lisaZa true scheduler a not just a matchmaker of resources15:50
johnthetubaguyits also a different concept of flavor, and has automatic deleteing, and I am sure other things will crop up15:51
bauzaslisaZ: at the moment, nova-scheduler is a resource placement engine15:51
johnthetubaguywe don't really have a scheduler, we just have a simple placement engine for requests that come in, if there is no space, the server build fails15:51
bauzaslisaZ: if you want to involve time-based decisions, nova-scheduler is not right for it15:51
*** beagles has quit IRC15:51
lisaZcorrect15:51
johnthetubaguythis changes the contract quite a lot, you end up having a queued state15:51
*** ramishra has joined #openstack-meeting15:51
johnthetubaguyfeels like that needs to be managed externally to Nova, if possible, at least for the moment15:52
bauzasat least until Nova uses an external scheduler :)15:52
johnthetubaguybauzas: its the nova API changes that worry me, it feels like a heat feature, in a way15:53
bauzasjohnthetubaguy: indeed, that's why we moved to a separate API for Climate15:53
*** hashar is now known as hasharMeeting15:53
bauzasjohnthetubaguy: formerly, we were planning to support reservation features in Nova15:53
bauzasjohnthetubaguy: but we moved to a separate project because of the API need15:54
johnthetubaguyright, same issue here15:54
lisaZlet me understand: which relationship there is between nova-scheduler and Gantt? Gantt will replace definitely nova-scheduler?15:54
bauzaslisaZ: that's the idea, yes15:54
lisaZok15:54
johnthetubaguylisaZ: short term, its a refactoring effort, to help scale out how the projects grow15:55
bauzasnova-scheduler will become deprecated once Gantt becomes fully operational15:55
lisaZour solution is between blazar and gannt15:55
n0anothink nova-volume to cinder, same idea15:55
lisaZwe need both15:55
bauzaslisaZ: I'm just saying that you can probably have some concepts in Blazar that you can make use, without redoing all the wheel15:56
*** ArxCruz has joined #openstack-meeting15:56
*** ramishra has quit IRC15:56
bauzasGantt is still under constructionhere15:56
lisaZthat's correct in fact I don't want redoing the well ;-)15:56
lisaZthat's correct in fact I don't want redoing the whell ;-)15:57
bauzasprobably in the future, Climate won't have any sense as a separate project - or not15:57
*** SumitNaiksatam has quit IRC15:57
bauzasjohnthetubaguy: have time for discussing with jaypipes and n0ano about what we discussed earlier ?15:58
bauzasafter the meeting I mean ?15:58
n0anobauzas, give me about 15 min. and I can join on the nova channel15:58
johnthetubaguylisaZ: if we agree the idea API, what it means, and how users use it, I think it will be much clearer about the best way forward15:58
johnthetubaguybauzas: sure15:59
bauzasjohnthetubaguy: cool, n0ano: sure15:59
*** Tross has quit IRC15:59
bauzaslisaZ: I think the first thing is to define the API interfaces for your needs15:59
*** ametts has left #openstack-meeting15:59
*** boltR has joined #openstack-meeting15:59
bauzaslisaZ: I mean the contract in between your user and the system15:59
jaypipesbauzas: unfortunately, I need to leave for the airport in a few minutes...16:00
n0anoapproaching the top of the hour, we'll have to continue this via email, let me know if you want to keep this subject on the agenda for next week.16:00
bauzasdammit16:00
n0anotnx everyone16:00
lisaZmeantime could you provide me some pointers to your new architecture?16:00
n0ano#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Tue Jul  8 16:00:30 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-07-08-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-07-08-15.00.txt16:00
bauzaslisaZ: which meeting ?16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-07-08-15.00.log.html16:00
bauzasoops16:00
bauzaswhich architecture ?16:00
lisaZGannt16:00
bauzasjaypipes: ok, we will discuss with n0ano then16:01
lisaZok thanks a lot16:01
bauzaslisaZ: there is no new architecture, just a refactoring effort at the moment16:01
schwickewould be great if you could send the pointer via e-mail16:01
*** jaypipes has quit IRC16:01
bauzasschwicke: at the moment, the Gantt API is still subject to debate :)16:02
*** jtomasek_ is now known as jtomasek16:02
mspreitzWasn't that the point of the first half of the meeting?16:02
schwickebauzas: great! that gives us a chance for changes ;-)16:02
schwicke:)16:02
bauzasmspreitz: ;)16:02
lisaZschwicke +116:02
schwickelisaZ: we should discuss via e-mail16:03
lisaZyes16:03
lisaZthanks ;-)16:03
schwickehave to leave, I'm being kicked out from here where I am16:03
* mspreitz goes AFK16:03
*** schwicke has left #openstack-meeting16:03
lisaZok thanks again16:03
lisaZbye16:03
*** dwalleck has joined #openstack-meeting16:04
*** lisaZ has quit IRC16:04
*** chuckC has quit IRC16:04
*** eghobo has joined #openstack-meeting16:04
*** eghobo has quit IRC16:05
*** eghobo has joined #openstack-meeting16:06
*** igordcard has joined #openstack-meeting16:06
*** yamamoto has joined #openstack-meeting16:06
*** leeantho has joined #openstack-meeting16:09
*** chuckC has joined #openstack-meeting16:09
*** vermarah has quit IRC16:09
*** vermarah_ has quit IRC16:09
*** asselin has joined #openstack-meeting16:12
*** vermarah has joined #openstack-meeting16:14
*** vermarah_ has joined #openstack-meeting16:14
*** SumitNaiksatam has joined #openstack-meeting16:16
*** jckasper_ has quit IRC16:16
*** chandankumar has joined #openstack-meeting16:17
*** asettle has quit IRC16:17
*** gyee has joined #openstack-meeting16:18
*** samcdona has quit IRC16:20
*** markwash has joined #openstack-meeting16:20
*** che-arne has joined #openstack-meeting16:21
*** asettle has joined #openstack-meeting16:21
*** asettle has quit IRC16:21
*** ildikov has quit IRC16:22
*** infotection has quit IRC16:23
*** chuckC has quit IRC16:23
*** chuckC has joined #openstack-meeting16:23
*** marcoemorais has joined #openstack-meeting16:23
*** Michalik_ has quit IRC16:24
*** hshah has joined #openstack-meeting16:24
*** hshah has left #openstack-meeting16:24
*** ominakov has quit IRC16:25
*** atiwari has quit IRC16:26
*** jtomasek has quit IRC16:26
*** alexpilotti has joined #openstack-meeting16:26
*** zz_blogan is now known as blogan16:27
*** ArxCruz has quit IRC16:28
*** yamamoto has quit IRC16:28
*** tkay has joined #openstack-meeting16:28
*** ArxCruz has joined #openstack-meeting16:28
*** aweeks_ is now known as aweeks16:29
*** ygbo has quit IRC16:29
*** atiwari has joined #openstack-meeting16:31
*** nati_ueno has joined #openstack-meeting16:31
*** jckasper has joined #openstack-meeting16:31
*** alexpilotti has quit IRC16:32
*** infotection has joined #openstack-meeting16:32
*** dwalleck has quit IRC16:33
*** yaguang has quit IRC16:35
*** Mandell has quit IRC16:36
*** beagles has joined #openstack-meeting16:36
*** asettle has joined #openstack-meeting16:36
*** yaguang has joined #openstack-meeting16:37
*** BrianB_ has quit IRC16:37
*** infotection has quit IRC16:39
*** tomoe_ has quit IRC16:39
*** bdpayne has joined #openstack-meeting16:40
*** jrolson has quit IRC16:41
*** nati_ueno has quit IRC16:41
*** nati_ueno has joined #openstack-meeting16:42
*** aswadr has quit IRC16:42
*** IlyaE has quit IRC16:42
*** jcoufal has quit IRC16:43
*** hemna has joined #openstack-meeting16:44
*** sweston has joined #openstack-meeting16:44
*** shashankhegde has joined #openstack-meeting16:44
*** arnaud__ has joined #openstack-meeting16:44
*** Ajaeger1 has joined #openstack-meeting16:46
*** k4n0 has joined #openstack-meeting16:48
*** hasharMeeting has quit IRC16:49
*** sarob has quit IRC16:50
*** luqas has quit IRC16:51
*** sarob has joined #openstack-meeting16:51
*** infotection has joined #openstack-meeting16:52
*** jgallard has quit IRC16:52
*** mkoderer has quit IRC16:52
*** _nadya_ has joined #openstack-meeting16:53
*** jlibosva has joined #openstack-meeting16:53
*** sweston has quit IRC16:55
*** dwalleck has joined #openstack-meeting16:55
*** sarob has quit IRC16:55
*** sweston has joined #openstack-meeting16:56
*** kayaliu_ has quit IRC16:57
*** roeyc has joined #openstack-meeting16:57
*** olkonami has joined #openstack-meeting16:58
*** _nadya_ has quit IRC16:58
*** hrybacki has quit IRC16:58
*** derekh_ has quit IRC16:58
*** sarob has joined #openstack-meeting16:58
*** salv-orlando has quit IRC16:59
*** vjay has quit IRC16:59
*** sweston has quit IRC16:59
*** che-arne|2 has joined #openstack-meeting17:00
*** vjay has joined #openstack-meeting17:00
*** flaper87 is now known as flaper87|afk17:00
*** amcrn has joined #openstack-meeting17:02
*** yaguang has quit IRC17:02
*** kayaliu_ has joined #openstack-meeting17:02
*** bdpayne has quit IRC17:03
*** shashankhegde has quit IRC17:03
*** che-arne has quit IRC17:03
*** Longgeek has quit IRC17:05
*** zdiN0bot has joined #openstack-meeting17:06
*** cjellick_ has joined #openstack-meeting17:06
*** salv-orlando has joined #openstack-meeting17:06
*** cjellick has quit IRC17:07
*** rediskin has joined #openstack-meeting17:07
k4n0#startmeeting Rally17:10
openstackMeeting started Tue Jul  8 17:10:23 2014 UTC and is due to finish in 60 minutes.  The chair is k4n0. Information about MeetBot at http://wiki.debian.org/MeetBot.17:10
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:10
*** openstack changes topic to " (Meeting topic: Rally)"17:10
openstackThe meeting name has been set to 'rally'17:10
*** VijayB has joined #openstack-meeting17:10
k4n0Lets start the Rally meeting17:10
*** mestery has quit IRC17:10
coolsvaphello17:10
olkonamihi!17:10
k4n0boris-42 wont be in meeting today17:10
k4n0who wants to start first?17:11
k4n0#topic Rally review updates17:12
*** openstack changes topic to "Rally review updates (Meeting topic: Rally)"17:12
*** pelix has quit IRC17:12
coolsvapk4n0, i have started working on https://blueprints.launchpad.net/rally/+spec/improve-unit-test-coverage-rally17:12
coolsvapsubmitted 3 patchsets for unit test coverage where its missing17:12
*** _nadya_ has joined #openstack-meeting17:13
k4n0great, thanks17:13
*** chandankumar has quit IRC17:13
k4n0olkonami, do you have any updates for the Stress runners ?17:14
*** acoles has joined #openstack-meeting17:14
k4n0ok, moving on17:14
k4n0oanufriev, Any updates since last meeting?17:15
*** gokrokve has quit IRC17:15
*** gokrokve has joined #openstack-meeting17:15
olkonamiabout stress runner, boris-42 asked me to modify ScenarioRunnerResult to store information about 1) failure_precent on iteration of scenario 2) was failure_precent > stop_on_failure_precent (at was what that level)17:15
olkonaminow I think how to do it17:16
k4n0olkonami, any more blockers ?17:16
k4n0rediskin, do you have any updates since last meeting?17:18
*** Fdot has quit IRC17:18
olkonamik4n0, no, I hope it last problem with stress runner17:18
*** yaguang has joined #openstack-meeting17:18
*** sballe has quit IRC17:18
*** sweston has joined #openstack-meeting17:18
rediskink4n0: i start work around reducing number of points in generated html charts17:18
rediskinthere is too much points sometimes17:19
rediskinalso plot.py need some refactoring17:19
rediskinpatch is coming soon17:19
*** k4n0_ has joined #openstack-meeting17:19
*** gokrokve has quit IRC17:19
k4n0_sorry, got disconnected17:20
*** DavidHu has joined #openstack-meeting17:20
rediskin[20:18:55] <rediskin> k4n0: i start work around reducing number of points in generated html charts17:20
rediskin[20:19:07] <rediskin> there is too much points sometimes17:20
rediskin[20:19:17] <rediskin> also plot.py need some refactoring17:20
rediskin[20:19:42] <rediskin> patch is coming soon17:20
k4n0_rediskin, do you have updates since last meeting?17:20
k4n0_rediskin, ahh , got it17:21
k4n0_rediskin, any blockers?17:21
*** gduan has quit IRC17:21
rediskink4n0_ no17:21
*** garyduan has joined #openstack-meeting17:22
*** thedodd has quit IRC17:22
k4n0_rediskin, any update on functional tests that we discussed last week?17:22
*** k4n0 has quit IRC17:22
*** DavidHu_ has joined #openstack-meeting17:23
*** k4n0_ is now known as k4n017:23
*** DavidHu_ has left #openstack-meeting17:23
rediskinabout functional tests: there is one tiny problem: html results are generated, but not published17:23
k4n0rediskin,  not published by the jenkins job?17:24
rediskini believe i fix it today17:24
rediskinby jenkins publisher. wrong path or something similar17:24
k4n0rediskin, ok cool, let us know if any blockers17:25
rediskinok17:25
k4n0I have been working on finishing unit tests for the final review in the rally-tempest integration patches17:25
*** jlibosva1 has joined #openstack-meeting17:25
k4n0Will complete it by tonite17:25
k4n0I am also working on increasing unit test coverage https://blueprints.launchpad.net/rally/+spec/improve-unit-test-coverage-rally17:26
k4n0I have to start working on this blueprint as well https://blueprints.launchpad.net/rally/+spec/collect-runtime-duration17:26
k4n0oanufriev is also working on first part of this blueprint https://blueprints.launchpad.net/rally/+spec/collect-runtime-duration17:27
coolsvapk4n0, I also noticed the centos gate is failing due to dependency issue, guys please let know if anyone else facing similar issues17:27
k4n0coolsvap, where is that?17:27
coolsvaphttps://review.openstack.org/#/c/105511/17:28
coolsvapi did recheck no bug, but still same issue persists17:28
*** bdpayne has joined #openstack-meeting17:28
*** andreaf has joined #openstack-meeting17:28
*** jlibosva has quit IRC17:28
k4n0coolsvap, ok thanks for heads up17:28
*** yaguang has quit IRC17:28
*** yamamoto has joined #openstack-meeting17:29
k4n0#action Check failing gate-rally-install-bare-centos617:29
rediskinit is not dependency issue, ist more looks like temporary network issues17:29
*** shashankhegde has joined #openstack-meeting17:29
*** harlowja_away is now known as harlowja17:29
rediskini saw the patch adding retries to apt-get/yum in devstack17:29
k4n0#info gate-rally-install-bare-centos6 failing due to temporary network issues (maybe)17:30
rediskinso mb we should add retries to install_rally.sh17:30
*** ngoswami_ has quit IRC17:30
coolsvaprediskin, yes, recheck no bug failed with connection reset to peer17:30
rediskinit is somewhere in yum configuration17:30
k4n0#info Try adding retries for apt-get/yum to solve failng centos6 gate17:30
*** bdpayne_ has joined #openstack-meeting17:30
k4n0rediskin, ok thanks, can you do that?17:30
rediskin2014-07-08 16:34:36.532 | Downloading/unpacking netaddr>=0.7.617:30
rediskin...17:30
rediskin2014-07-08 16:34:51.829 | SSLError: The read operation timed out17:30
coolsvapokay I will check in my patch17:31
*** xianghui has quit IRC17:31
k4n0#topic open discussion17:31
*** openstack changes topic to "open discussion (Meeting topic: Rally)"17:31
k4n0anything else left to discuss?17:31
rediskinrecently i heard about asynchronous collecting results17:31
*** kayaliu_ has quit IRC17:32
k4n0yes, Artem Borzilov is working on them17:32
k4n0https://review.openstack.org/10451817:32
rediskinoh, yes17:32
rediskinthank17:32
rediskinwe need to review it =)17:33
rediskinmore eyes -- less errors17:33
k4n0#action review https://review.openstack.org/10451817:33
k4n0rediskin, got it17:33
k4n0Anything else to discuss ?17:33
olkonamiI have a patch for plugins improvement17:34
*** bdpayne has quit IRC17:34
olkonamihttps://review.openstack.org/#/c/103145/17:34
olkonamiit makes possible to load plugins not only for scenarios, but also for runners and contexts17:34
rediskinnice17:34
k4n0#link https://review.openstack.org/#/c/10314517:34
olkonamiand plugins can be loaded from any subdirectories of plugins directories17:34
*** _nadya_ has quit IRC17:35
k4n0sounds great17:35
k4n0#action review https://review.openstack.org/#/c/103145/17:35
k4n0olkonami, nice work with the docs17:35
*** penguinRaider has joined #openstack-meeting17:36
*** yamamoto has quit IRC17:36
k4n0Anything else to discuss?17:36
olkonamik4n0, thanks17:36
*** nelsnelson has quit IRC17:36
*** prad has quit IRC17:37
*** gokrokve has joined #openstack-meeting17:37
k4n0ok , it seems we can end the meeting :)17:37
rediskinhttps://github.com/openstack-dev/devstack/commit/9ad8f9890198de0a3c124cea06d993c9f1939ea817:38
rediskinonly for apt17:38
rediskin>_<17:38
k4n0rediskin, can you send patch to our ci job script?17:39
k4n0#link https://github.com/openstack-dev/devstack/commit/9ad8f9890198de0a3c124cea06d993c9f1939ea817:39
rediskinwe should make patch for install_rally.sh17:39
*** igordcard has quit IRC17:39
rediskinand it should be for yum,not apt17:40
*** jmontemayor has joined #openstack-meeting17:40
k4n0rediskin, Yes, correct17:40
k4n0rediskin, since only centos6 is failing, but do you think we should put same change for ubuntu? So that it doesnt fail in future17:40
rediskinok, i gonna make patch soon17:40
k4n0rediskin, can you make for both gates, centos and ubuntu ?17:41
coolsvapk4n0, for ubuntu its there17:41
k4n0#action rediskin will make patch for fixing yum retry issue17:41
coolsvapwe need it for yum only17:41
rediskinthis change in install_rally.sh, so it automatically aplly for all gates17:41
k4n0coolsvap, ok thanks17:41
k4n0rediskin, thanks17:41
*** dims_ has quit IRC17:41
k4n0Shall we end the meeting?17:42
*** jprovazn has joined #openstack-meeting17:42
rediskinlets do it. there is #openstack-rally if anyone wants to continue17:43
k4n0ok, seems we dont have anything else to discuss, ending meeting17:43
k4n0Thanks everyone. We did meeting without boris-42 today :)17:43
k4n0#endmeeting17:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:43
openstackMeeting ended Tue Jul  8 17:43:40 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-07-08-17.10.html17:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-07-08-17.10.txt17:43
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-07-08-17.10.log.html17:43
*** overlayer has joined #openstack-meeting17:43
*** olkonami has left #openstack-meeting17:44
*** rediskin has left #openstack-meeting17:45
*** yyywu has joined #openstack-meeting17:46
*** vjay has quit IRC17:48
*** comay has quit IRC17:48
*** k4n0 has quit IRC17:50
*** kaitlin-farr has joined #openstack-meeting17:50
*** sbalukoff has joined #openstack-meeting17:50
*** cjellick_ has quit IRC17:50
*** cjellick has joined #openstack-meeting17:51
*** s3wong has quit IRC17:52
*** manishg has joined #openstack-meeting17:52
*** MarkAtwood has joined #openstack-meeting17:54
*** kaitlin-farr has left #openstack-meeting17:56
*** IlyaE has joined #openstack-meeting17:56
*** mrunge has quit IRC17:57
zdiN0botdoes anyone want to come rock climbing at mission cliffs this afternoon? ps - we're doing belay training at 4:15 outside the kitchen by the pull up bar.17:57
zdiN0botleaving around 5 to bus to mission cliffs.17:57
*** mrunge has joined #openstack-meeting17:58
zdiN0botmeet by foos table. at 5.17:58
*** DHU has joined #openstack-meeting18:01
*** leonchio_ has joined #openstack-meeting18:03
*** nati_ueno has quit IRC18:03
*** sarob has quit IRC18:04
*** sarob has joined #openstack-meeting18:04
*** Tross has joined #openstack-meeting18:05
*** che-arne|2 has quit IRC18:06
*** jckasper_ has joined #openstack-meeting18:07
*** dims_ has joined #openstack-meeting18:08
*** edhall has joined #openstack-meeting18:08
*** jckasper has quit IRC18:09
*** sarob has quit IRC18:11
*** prad has joined #openstack-meeting18:11
*** bdpayne_ has quit IRC18:12
*** jcoufal has joined #openstack-meeting18:12
*** dims_ has quit IRC18:12
*** bdpayne has joined #openstack-meeting18:13
*** nelsnelson has joined #openstack-meeting18:13
*** baoli has joined #openstack-meeting18:15
*** vivek-ebay has joined #openstack-meeting18:15
*** scinawa has joined #openstack-meeting18:16
*** dims_ has joined #openstack-meeting18:16
*** arnaud__ has quit IRC18:16
*** alexpilotti has joined #openstack-meeting18:18
*** kayaliu_ has joined #openstack-meeting18:19
*** _nadya_ has joined #openstack-meeting18:20
*** mkoderer has joined #openstack-meeting18:22
*** vijendar has joined #openstack-meeting18:24
*** thinrichs has quit IRC18:25
*** overlayer has quit IRC18:26
*** yamamoto has joined #openstack-meeting18:29
*** sarob has joined #openstack-meeting18:30
*** yamamoto_ has joined #openstack-meeting18:31
*** fnaval has quit IRC18:32
*** baoli has quit IRC18:32
*** Leonr has joined #openstack-meeting18:32
*** fawadkhaliq has joined #openstack-meeting18:33
*** kayaliu_ has quit IRC18:33
*** yamamoto has quit IRC18:33
*** shardy is now known as shardy_afk18:34
*** amitpp has quit IRC18:34
*** manishg has left #openstack-meeting18:34
*** dwalleck has left #openstack-meeting18:35
*** yamamoto_ has quit IRC18:35
*** emagana has quit IRC18:37
*** luqas has joined #openstack-meeting18:39
*** hashar has joined #openstack-meeting18:39
*** kevinbenton has quit IRC18:40
*** thedodd has joined #openstack-meeting18:41
*** akuznetsova has quit IRC18:41
*** _nadya_ has quit IRC18:46
*** _nadya_ has joined #openstack-meeting18:47
*** novas0x2a|laptop has joined #openstack-meeting18:48
*** penguinRaider has quit IRC18:48
*** akuznetsova has joined #openstack-meeting18:48
*** gothicmindfood has joined #openstack-meeting18:49
*** penguinRaider has joined #openstack-meeting18:49
*** roeyc has quit IRC18:51
*** IlyaE has quit IRC18:52
*** _nadya_ has quit IRC18:52
*** eankutse has joined #openstack-meeting18:52
*** kevinbenton has joined #openstack-meeting18:53
*** radez is now known as radez_g0n318:54
*** otherwiseguy has quit IRC18:54
*** padkrish has joined #openstack-meeting18:54
*** julienvey has quit IRC18:54
*** Penick has joined #openstack-meeting18:56
*** nati_ueno has joined #openstack-meeting18:56
*** radez_g0n3 is now known as radez18:57
*** markmcclain has joined #openstack-meeting18:59
*** mestery has joined #openstack-meeting18:59
*** mestery has quit IRC18:59
*** mestery has joined #openstack-meeting18:59
*** markmcclain1 has joined #openstack-meeting19:00
jeblairinfra folks around?19:00
fungidid rally switch time slots with keystone?19:00
fungihey-o!19:00
*** nati_ueno has quit IRC19:00
fungioh, rally's before keystone, and keystone took the day off19:00
anteayao/19:00
*** nati_ueno has joined #openstack-meeting19:00
zaroo/19:00
clarkbo/19:00
* SergeyLukjanov on PTO today, so, mostly lurking19:01
anteaya<-- has a ticket to see sarah maclaughlin tonight!!19:01
Ajaeger1Hi!19:01
*** novas0x2a|laptop has quit IRC19:01
*** novas0x2a|laptop has joined #openstack-meeting19:01
jeblairanteaya: you must be.. ecstatic!19:01
jeblair#startmeeting infra19:01
openstackMeeting started Tue Jul  8 19:01:41 2014 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
krtayloro/19:01
anteayaI am19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
jeblair#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:02
jeblair#link http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-07-01-19.02.html19:02
jeblairdrat, i think most of the agenda is left over from last week19:02
jeblair#topic  Actions from last meeting19:02
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:02
jeblairnibalizer and jeblair to spin up a puppet3 master19:02
jeblairthis did not happen19:02
pleia2o/19:02
jeblairseveral changes were still outstanding and needed to land19:03
*** eankutse has quit IRC19:03
jeblairnibalizer: i think they have landed now, and we're ready to actually try booting one?19:03
*** nati_ueno has quit IRC19:03
*** markmcclain has quit IRC19:03
*** salv-orlando has quit IRC19:03
*** nati_ueno has joined #openstack-meeting19:03
*** eankutse has joined #openstack-meeting19:04
*** eankutse has quit IRC19:04
jeblairthat's my story and i'm sticking to it19:04
jeblair#topic  Zanata/Pootle updates and time frame (pleia2)19:04
*** openstack changes topic to "Zanata/Pootle updates and time frame (pleia2) (Meeting topic: infra)"19:04
*** IlyaE has joined #openstack-meeting19:04
pleia2so I have a couple updates here19:04
pleia2I met with the translatiosn team at their meeting last week, they're still keen to try Zanata "soon" since they're having trouble with Transifex support (creating new projects is hard right now, takes a lot of time since they need to go to support)19:05
nibalizerjeblair: very quickly, yes we can, but im dealing with some other stuff right now, so  i'll emerge from the cloud... eventually19:05
nibalizercloud was perhaps not the right word in this context19:06
*** otherwiseguy has joined #openstack-meeting19:06
Ajaeger1pleia2: Here's an update from transifex: They fixed the problem, we can create new projects again!19:06
pleia2the Zanata folks told us 5-6 weeks before they have Zanata running on the WildFly application server, which we can run on Centos7 - no licenses19:06
* Ajaeger1 created 5+ new projects the last few days19:06
pleia2Ajaeger1: ah good, so less urgent :)19:06
Ajaeger1pleia2: exactly!19:06
Ajaeger1still, the long time it took to resolve this, means we have to switch eventually.19:07
jeblairpleia2: does wildfly have packages in centos?19:07
pleia2so we can set up basic Zanata + AS7 pre-packaged thing in the -infra so the Translations folks can test it + upgrade Pootle and schedule a demo with a Pootle contributor so they can compare side-by-side19:07
pleia2jeblair: no, it's still heavily in development19:07
*** Munish has quit IRC19:07
jeblairpleia2: how will be deploy wildfly?19:07
pleia2jeblair: it's pretty much jboss, we'd manage from tarballs, not awesome tbh :\19:07
*** ianw_pto has quit IRC19:08
jeblairpleia2: isn't that the same problem with jboss?19:08
*** arnaud has joined #openstack-meeting19:08
pleia2jeblair: jboss has that problem, plus the community version having known security problems and the enterprise version requiring a paid license19:09
pleia2so with wildfly we only solve the licensing issues19:09
*** jang has joined #openstack-meeting19:09
jeblairpleia2: wildfly community version is expected to get security updates?19:09
*** rockyg has joined #openstack-meeting19:09
pleia2jeblair: that's the plan19:09
*** wenlock has joined #openstack-meeting19:10
jeblairi have to admit, i'm extremely skeptical19:10
*** mrunge has quit IRC19:10
jeblairi believe redhat chooses to make jboss installation difficult as a business decison19:10
jeblairand i don't see why that would be different with wildfly19:10
pleia2as I understand it, it's not jboss, but it is a java application server that will have the ability to run zanata19:10
pleia2but this is all new to me :)19:10
jeblairnot to mention, the number of hoops we have to go through to manage installing software from tarballs19:10
*** samcdona has joined #openstack-meeting19:11
fungiwell, red hat traditionally made their linux distro security updates hard too, as part of their business model. hence centos. then they acknowledged that people want to run community versions of server things, so they absorbed centos19:11
zaropleia2: can't zanata run in tomcat?19:11
pleia2I also have very little expertise managing java/jboss applications, not sure how we're doing talent-wise with the rest of the team19:11
pleia2zaro: I don't think so19:11
clarkbI have never done jboss before either :)19:11
zaroi have *some* experience with jboss19:12
jeblairpleia2: i've only used tomcat, because, well, the R1 university i was at couldn't afford a jboss license.  :)19:12
*** carl_baldwin has quit IRC19:12
*** banix has quit IRC19:13
jeblairpleia2: so it seems like the plan is to set up both systems un-managed for further evaluation19:13
pleia2jeblair: yeah19:13
jeblairi think that the puppeting, etc, should be part of the evaluation19:13
clarkb++19:14
jeblairi don't think the systems are equivalent from an installation/upgrade/management pov19:14
pleia2agreed19:15
pleia2Carlos of the Zanata team sent me some incomplete puppet configs for zanata running on jboss+RHEL and they are keen to see improvements, so I'll take another look at those19:15
pleia2I added this topic for our sprint next week, so I'll do some prep for that19:15
fungii agree that the deployment automation of a system is part of that system from an evaluation perspective. if it runs well but is impossible to deploy, then it may be less preferable to something which runs okay and is easy to deploy19:15
*** SumitNaiksatam has quit IRC19:16
jeblairpleia2: would you be interested in working with the translation team on the evaluation, to make sure that these concerns are shared?19:16
pleia2jeblair: yeah, I'll handle that19:16
*** gyee has quit IRC19:16
pleia2the real concern for them is that if it's tough for us to maintain, it'll be a poor experience + have downtime as we upgrade, etc19:16
fungis/deploy/deploy and manage/g19:16
zaroIIRC deploying jboss and tomcat are pretty similiar. there's lots of automation around those19:16
jeblairzaro: deploying tomcat is "yum install tomcat"19:17
*** IlyaE has quit IRC19:17
*** zdiN0bot has quit IRC19:17
pleia2puppet require package :)19:17
*** carl_baldwin has joined #openstack-meeting19:17
jeblairpleia2: indeed; but i never would have gotten the rocketships aligned in irc :)19:18
pleia2hehe19:18
pleia2anyway, that's all I've got19:18
jeblaircool, thanks.  i'm happy to help out with any pootle hacking that needs doing too.19:18
pleia2great19:19
jeblair#topic  Replacement for docs.openstack.org (AJaeger)19:19
*** openstack changes topic to "Replacement for docs.openstack.org (AJaeger) (Meeting topic: infra)"19:19
*** Penick has quit IRC19:19
Ajaeger1This is a followup to the Atlanta summit session https://etherpad.openstack.org/p/summit-b301-ci-doc-automation19:19
Ajaeger1We talked briefly about the need to replace docs.openstack.org with another system - one of the issues was a system where we can actually delete files ;)19:20
*** carl_baldwin has quit IRC19:20
Ajaeger1I wanted to followup on this and see what the next steps are here.19:20
clarkbI think there are a few options open to us. like rsync or using 'slots' to host the content19:21
Ajaeger1jeblair: I took as note after the meeting "Jim Blair will brainstorm with team on how to do it best, will need at19:21
Ajaeger1least a month, so get back to him after mid-June." - and now I'm back ;)19:21
clarkbI briefly looked at read the docs but that is far too complicated for our needs19:21
jeblairAjaeger1: we may not need a terribly complicated system, possibly just a different way of copying them19:21
Ajaeger1jeblair: copying and deleting ;) yeah19:21
*** baoli has joined #openstack-meeting19:21
jeblairAjaeger1: yeah, i'd actually like to push that back another 2 weeks if we can... i'd like to do some brainstorming at our mid-cycle in germany19:21
Ajaeger1It's serving static pages, so shouldn't be something complicated.19:21
Ajaeger1jeblair: fine with me!19:22
fungiin particular, knowing what "features" of rackspace cloudsites the current docs hosting might be taking for granted would be helpful19:22
wenlock*for us19:22
Ajaeger1fungi: if you have some questions, I can figure them out with annegentle19:22
wenlockmt19:22
fungii suspect that just cramming those files onto an basic apache server may not get you everything you require. i know in the past there were content search libraries and other things provided by the cloudsites platform19:23
fungiso knowing what they are up front will help speed the design along19:23
*** hrybacki has joined #openstack-meeting19:23
Ajaeger1fungi: I can check, I'm not aware of these yet.19:24
jeblairhrm.  current search seems to use google19:24
fungithough with the docs-draft deployment we do at least serve up the basic content on a bog-standard apache server, so might just work19:24
*** garyduan has quit IRC19:24
fungijeblair: oh, they might have changed that19:24
*** SumitNaiksatam has joined #openstack-meeting19:24
Ajaeger1fungi: yeah, just see http://docs-draft.openstack.org/63/105263/4/check/gate-openstack-manuals-tox-doc-publish-checkbuild/94f3e9d/publish-docs/19:24
Ajaeger1works fine for publishing manuals...19:24
Ajaeger1just click on the link19:25
*** garyduan has joined #openstack-meeting19:25
*** SridharG has quit IRC19:25
jeblairyeah, i think the basic question is how to delete the files we want to (obsolete files), but not the ones we don't (files that come from a different build, eg, a stable branch)19:25
Ajaeger1jeblair: indeed.19:25
Ajaeger1we publish to single directories for each book19:26
Ajaeger1but only publish the changed manuals19:26
jeblairso we'll have a bunch of people in the room that understand what we're doing now, and what we're trying to do with swift, so i bet we can come up with something19:26
fungicool--all good stuff to discuss next week in darmstadt19:26
*** salv-orlando has joined #openstack-meeting19:27
Ajaeger1if you have questions for me, just ping me - I'm in Germany as well so in your timezone next week ;)19:27
*** markmc has joined #openstack-meeting19:27
jeblairAjaeger1: thanks, will do!19:27
fungithe search i was thinking of was the stuff like http://docs.openstack.org/admin-guide-cloud/content/#searchDiv btw19:27
Ajaeger1fungi: try http://docs-draft.openstack.org/63/105263/4/check/gate-openstack-manuals-tox-doc-publish-checkbuild/94f3e9d/publish-docs/high-availability-guide/content/index.html#searchDiv19:27
*** ildikov has joined #openstack-meeting19:28
Ajaeger1works on docs-draft as well19:28
*** gokrokve has quit IRC19:28
*** luqas has quit IRC19:28
Ajaeger1Thanks for putting this on the agenda for Darmstadt!19:28
*** gokrokve has joined #openstack-meeting19:28
*** julienvey has joined #openstack-meeting19:28
*** Penick has joined #openstack-meeting19:28
fungiright, dita but i forget what provides it19:28
jeblairAjaeger1: thank you!19:29
jeblairwhat a perfect transition...19:29
jeblair#topic Meetup19:29
*** openstack changes topic to "Meetup (Meeting topic: infra)"19:29
jeblair#link https://wiki.openstack.org/wiki/Qa_Infra_Meetup_201419:29
jeblairthat's next week19:29
jeblairwe're out of room and registration is closed19:29
clarkbyes I arrive sunday morning local time19:29
*** yamamoto has joined #openstack-meeting19:29
pleia2me too19:29
zaroclarkb is my flying buddy19:30
anteayame too19:30
pleia2I get in at 10:55am19:30
jeblairthere's a waitlist, so if anyone on the registration list is not going, please let me know19:30
jeblairalso, if you are only attending certain days, please annotate that in the comments section next to your name19:30
*** overlayer has joined #openstack-meeting19:30
fungilooks like i get to frankfurt at noon19:30
anteayaI will create an etherpad for commits to infra-manual, I'd like everyone to pick a section and offer at least one paragraph of content19:30
anteayaI'll link the etherpad to the wikipage19:31
jeblairanteaya: good one19:31
*** Penick has quit IRC19:32
*** SumitNaiksatam has quit IRC19:32
*** arnaud has quit IRC19:32
anteayaI also have assorted third party things for beer discussion19:32
*** jckasper__ has joined #openstack-meeting19:32
*** gokrokve has quit IRC19:33
fungithird-party beer19:33
pleia2and assorted beer for third party discussion19:33
pleia2(woo germany!)19:33
anteayaha ha ha19:33
clarkband world cup19:33
krtayloranteaya, take good notes on the third-party beer19:33
Ajaeger1No need to bring your own beer to Germany ;)19:33
*** yamamoto has quit IRC19:33
fungiAjaeger1: yeah, i expect to be able to find plenty there19:34
anteayakrtaylor: I will be able to tell many stories19:34
*** Mandell has joined #openstack-meeting19:34
anteayakrtaylor: I still want to you be there, but can't figure out how to shoe horn you in19:34
krtayloranteaya, it all good, I'll stay here and get some patches done19:35
anteayakk19:35
anteayayou can review many infra-manual patches19:35
anteayaand assorted others19:35
krtayloryep, that too19:35
anteaya:D19:35
*** markmcclain has joined #openstack-meeting19:36
*** jckasper_ has quit IRC19:36
jeblairanyone have anything else?19:36
clarkbI sort of do19:36
*** markmcclain1 has quit IRC19:37
*** Michalik_ has joined #openstack-meeting19:37
clarkbit being hosted at corporate land is there a secret handshake we need to use to get into the building?19:37
*** VijayB has quit IRC19:37
clarkblooks like we have an address to go to. And how early should we show up?19:37
jeblairbtw, i've been trying to avoid reviewing changes that don't have a +/-1 code review; so non-core infra reviewers, your help is much appreciated.  :)19:37
*** comay has joined #openstack-meeting19:38
*** vivek-ebay has quit IRC19:38
*** johnthetubaguy is now known as zz_johnthetubagu19:38
Ajaeger1clarkb: last time I visited Deutsche Telekom they had a reception where I just told them who I am and what I wanted.19:38
clarkbAjaeger1: perfect19:38
jeblairclarkb: i think the registration list is being used for that purpose19:38
anteayajeblair: I hear that19:38
Ajaeger1But there are many buildings of DT in Darmstadt...19:38
Ajaeger1Your host is Marc Koderer - remember his name ;)19:38
jeblairthe wiki page says " Mina-Rees-Str. 12"  hopefully that's specific enough :)19:39
fungiif i end up at the wrong building, i'll just recruit some new dt employees to work on infra for us19:39
*** ominakov has joined #openstack-meeting19:39
* Ajaeger1 just looks it up 19:39
anteayafungi: go you19:39
Ajaeger1The whole area is Telekom buildings, so take the proper entry ;)19:39
anteayawe need more eu representation19:39
* SergeyLukjanov hopes that will be able to participate somehow through irc19:40
clarkbI am guessing there will be enough of us weird people hanging around if we can't figure it out that someone will help us :)19:40
krtaylorSergeyLukjanov, I was hoping for some google hangouts19:41
wenlock+1 for a google hangout, but it's EU timezone eh?19:41
*** MarkAtwood has quit IRC19:41
Ajaeger1wenlock: yeah, UTC+219:41
Ajaeger1wenlock: there's more than one timezone in EU ;)19:41
* fungi was hoping to use free software, not google19:41
*** novas0x2a|laptop has quit IRC19:41
wenlock:D19:41
*** novas0x2a|laptop has joined #openstack-meeting19:42
wenlockfungi, would be nice for something that records the session19:42
fungiwenlock: for example, an irc bot!19:42
wenlockintreasting19:42
* fungi thinks we already have one in the #openstack-infra channel19:42
fungiand we should take good notes for the benefit of those not able to participate with us real-time19:43
anteayaetherpads will be created19:43
*** baoli has quit IRC19:43
pleia2if we do it summit-style, etherpads were sufficient for following up after the summit I missed19:44
anteayacool19:44
anteayaI don't think it will be a hardship for us to work summit style19:44
Ajaeger1great, thanks!19:44
wenlocktake your go-pros :D19:45
fungiyep. agreed, etherpads for taking notes19:45
anteayawe can add links to the sprint wikipage19:45
fungiperfect19:45
jeblairwenlock: now i'm going to search for "extreme daredevil hacking videos" on youtube19:45
wenlockjeblair haha19:46
pleia2hehe19:46
jeblairoh, one last thing...19:46
jeblairi reckon we should probably cancel this meeting next week :)19:47
anteayaha ha ha19:47
pleia2yeah19:47
fungii reckon so19:47
*** cjellick has quit IRC19:47
fungior, rather than cancel it, hold it in person, and hack on things during it19:47
jeblairshould we also cancel the week after (oscon)?19:47
*** cjellick has joined #openstack-meeting19:48
clarkbjeblair: possibly19:48
jeblairi honestly don't know what i'm going to be doing at that time19:48
clarkbI will be there as will you and fungi iirc19:48
*** cjellick has quit IRC19:48
pleia2I'm skipping oscon19:48
clarkbI won't be at oscon proper though19:48
*** cjellick has joined #openstack-meeting19:48
jeblairi think mordred will be in a board meeting...19:48
fungii think i can make the oscon week meeting, but it would be from a hotel room, or mobile modem or crappy conference wifi19:48
jeblaircome to think of it, that might be were some of us may be too19:48
fungioh, right19:48
fungii meant to show up for the board meeting too19:48
*** noslzzp has quit IRC19:48
clarkbfungi: we might need to do backyard hacking with kegerator19:48
clarkband non crappy wifi19:48
anteayaI'm not at oscon19:48
fungiclarkb: i'll be happy to help you hack on your kegerator19:49
*** jecarey has quit IRC19:49
fungiclearly it needs its own microcontrolled sensor array19:49
clarkbbrewpi is a thing19:49
clarkboccasionally I am tempted to do something like that19:49
clarkbbut then I would just worry about it more19:49
jeblairi think we may want to declare it an opportunistic meeting... if people show up and feel strongly about having a meeting, go for it.  but expect many absences, or no meeting at all.19:49
pleia2ok, between oscon and board things... next meeting on July 29th19:49
ttxo/19:49
clarkbjeblair: ++19:50
fungiwfm19:50
clarkbttx: ohai19:50
fungittx: talk went well?19:50
*** overlayer has quit IRC19:50
jeblair#agreed no meeting on July 22 due to in-person meetup19:50
*** tbarron has quit IRC19:50
pleia2jeblair: 15th19:50
jeblairoops19:50
jeblairis there an undo?19:50
pleia2#undo19:50
fungioho, neat!19:50
*** tbarron has joined #openstack-meeting19:50
jeblaircould that be more intuitive?19:51
fungii figured we were just going to have to #agree calendars are hard19:51
jeblair#agreed no meeting on July 15 due to in-person meetup19:51
jeblair#agreed possibly no meeting on July 22 due to oscon19:51
jeblair#agreed next scheduled meeting July 2919:51
ttxfungi: a bit empty room, but our numbers attracted the usual "wow"19:51
jeblairttx: what was the talk?19:52
ttxjeblair: infra, same as my oscon one19:52
jeblairttx: what event?19:52
ttxerr19:52
ttxfosdem one19:52
ttxwhich you attended19:52
ttxLibre software meeting19:52
jeblairoh cool19:52
*** coolsvap is now known as coolsvap|afk19:52
jeblairthat reminds me:  lca cfp closes soon.19:53
clarkbI still haven't come up with something good for that19:53
clarkbI should think harder19:53
* ttx still tries to find a way to jutify cfping for it19:53
ttx+s19:53
anteayajeblair: oh, thanks, I didn't know it was open19:53
fungido we have a nodepool presentation yet? i couldn't find one in the usual place19:53
fungiwould probably be something work knocking up if nobody's done one yet19:53
*** eglynn has joined #openstack-meeting19:53
clarkboh wow really soon19:54
fungis/work/worth/19:54
jeblairi'm going to submit some stuff about gertty and gear.19:54
*** SumitNaiksatam has joined #openstack-meeting19:54
jeblairfungi: i have not done one yet19:54
clarkbI had kciked around something along the lines of 100k changes there and back again19:54
*** ominakov has quit IRC19:54
clarkbbecause as you know those films were filmed in that country <_<19:54
jeblairclarkb: nice19:54
anteayaclarkb: ohhh, I like it19:54
clarkbmaybe I will go ahead and do that19:55
anteayayou are waxing poetic on the titles19:55
* clarkb does this19:55
anteaya:D19:55
*** coolsvap|afk is now known as coolsvap19:55
anteayawork ghost tooth into it19:55
*** sarob has quit IRC19:55
jeblairclarkb: statistically speaking, several people in the audience will have worked on those films.  :)19:55
clarkbjeblair: :)19:55
*** sarob has joined #openstack-meeting19:56
clarkbok I can't not submit that paper now19:56
jeblairi just hope we don't revert all 100k changes19:56
clarkbthat was my secret plan19:56
fungistatistically speaking, several people in the audience will have reverted some of those 100k changes19:56
jeblairi mean, i'm trying to :)19:56
clarkbno I wanted to look forward to the next 100k19:57
anteayaThis year the papers committee is going to be focused on open source in education -- hey I can talk about mentoring and mentoring mentors19:57
clarkbso a this is how we got here and it was crazy. This is how much crazier its going to be19:57
anteayaI wonder if they will like that proposal19:57
*** julienvey has quit IRC19:58
*** otherwiseguy has quit IRC19:58
jeblairwell, thanks everyone!  see many of you next week!19:58
Ajaeger1Have a good trip to Germany!19:58
*** ominakov has joined #openstack-meeting19:58
fungilooking forward to it!19:58
anteayathanks jeblair19:58
pleia2thanks jeblair19:58
krtaylorsafe travel everyone19:58
*** coolsvap1 has joined #openstack-meeting19:58
*** coolsvap is now known as coolsvap|afk19:58
jeblair#endmeeting19:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:58
openstackMeeting ended Tue Jul  8 19:58:48 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-07-08-19.01.html19:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-07-08-19.01.txt19:58
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-07-08-19.01.log.html19:58
*** Ajaeger1 has left #openstack-meeting19:58
jeblairpleia2: i don't think that undo worked19:59
pleia2jeblair: I think the chair has to do it :\19:59
jeblairdoh19:59
*** dprince has quit IRC19:59
*** coolsvap1 has quit IRC20:00
*** leonchio_ has quit IRC20:00
ttxAnyone here for the TC meeting ?20:01
russellb\o/20:01
*** sarob has quit IRC20:01
* ttx keeps an eye on the game20:01
markmchey20:01
dhellmanno/20:01
zehicleo/20:01
ttxHopes Brazil will avenge France20:01
russellbwhat is this sportsball that you speak of20:01
anteayao/20:01
ttxannegentle, mikal, mordred, devananda, vishy, markmcclain, jeblair, jaypipes, sdague: around ?20:01
devanandao/20:01
*** padkrish has quit IRC20:01
sdagueo/20:02
markmcclaino/20:02
ttxrussellb: a softball version of American Football20:02
vishyo/20:02
ttx#startmeeting tc20:02
openstackMeeting started Tue Jul  8 20:02:48 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
openstackThe meeting name has been set to 'tc'20:02
ttxOur agenda for today...20:02
mikalHi20:02
*** zdiN0bot has joined #openstack-meeting20:02
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:02
*** padkrish has joined #openstack-meeting20:03
ttx#topic Core Capabilities TC scoring20:03
*** openstack changes topic to "Core Capabilities TC scoring (Meeting topic: tc)"20:03
ttxWe still have to finalize our answer for the Havana core capabilities "TC" columns20:03
russellbi think we're about ready for another revision here.  dhellmann said he'd do it post meeting20:03
ttxok20:03
russellbzehicle: it might be worth reading over the comments ... there's a few issues with capability defitions20:03
russellbdefinitions that is20:03
dhellmannyeah, I have the update ready but thought I would make sure there wasn't other feedback first20:03
ttxI commented about the meaning of each column, based on Rob's post:20:03
ttx#link http://robhirschfeld.com/2014/05/01/defcore-capabilities-selection/20:04
ttx#info "Complete": 0 if the capability test is configuration-specific, 1 otherwise20:04
*** baoli has joined #openstack-meeting20:04
ttx#info "Stable": 0 if the capability has been there for less than 2 releases, 1 otherwise20:04
ttx#info "Future direction": 0 if we plan to deprecate that feature in the near future, 1 otherwise20:04
dhellmannthanks again to russellb for digging into the meanings on the capability names20:04
russellbdhellmann: np20:04
zehicleok20:04
ttxAny specific row you'd like to discuss here ?20:04
ttxor should we just iterate on hte review ?20:04
*** Michalik_ has quit IRC20:04
zehiclethere's some start-up wiggle that you have to accept20:05
*** pballand has quit IRC20:05
ttxReview link: https://review.openstack.org/10072220:05
zehiclewe wrote them as if it was a going thing and accepted that iteration 0 would have null for previous pointers20:05
russellbi think we can iterate on the review20:05
dhellmannzehicle: what's the process for removing a capability? when nova-network is deprecated, for example, some of the ones like compute-security-groups might change or go away. how does that work?20:05
*** nati_ueno has quit IRC20:05
*** shardy_afk is now known as shardy20:05
russellbs/when/if/20:05
russellb:)20:05
*** nati_ueno has joined #openstack-meeting20:05
sdaguedhellmann: realistically it probably doesn't change. We've said there needs to be parity for those interfaces to deprecate20:06
zehicleit should be marked as not future and then raised to defcore20:06
zehicleideally, we would not make things that are depricated core at all20:06
*** pballand has joined #openstack-meeting20:06
zehicleBUT we are trying for interop so stability is key20:06
russellbzehicle: capability issues i noticed: test for compute-auth doesn't actually test auth.  compute-security-groups includes a test not related to security groups.  compute-admin-fixed-ips i don't think is an admin API.20:06
zehiclepart of the rationale for a small set20:06
*** radez is now known as radez_g0n320:07
zehiclerussellb, ok20:07
russellbi didn't review all of them, just the ones we were tweaking20:07
dhellmannright, that's my point -- if we leave this in now, and decide later that it's silly to proxy requests to neutron through nova (as a technical decision) how hard does the capability make the change from a policy perspective?20:07
zehiclewe very very much want feedback about the tests & capabilities20:07
*** nati_ueno has quit IRC20:07
*** MaxV has quit IRC20:07
russellbdhellmann: this is updated on a per release basis is my understanding20:07
zehicleit was not our plan to have defcore own that - it feels like a technical item to me20:07
russellbdhellmann: this is havana, so don't think it's a big deal, since this trails the code20:07
zehicleBUT I've had that feeling before and found the TC did not agree20:07
dhellmannzehicle: but if the API that test is looking at goes away...20:07
dhellmannrussellb: I'm just trying to understand the process, and how long things are expected to stay around.20:08
*** MaxV has joined #openstack-meeting20:08
russellbdhellmann: ok20:08
zehiclethese are good questions20:08
*** vivek-ebay has joined #openstack-meeting20:08
dhellmannrussellb: I'm not arguing that we shouldn't mark those items 1 for now, just being careful :-)20:08
zehiclewe expect changes release to release20:08
zehiclewe;re not trying to make a lifetime standard20:08
dhellmannso we could say that icehouse doesn't have that feature at all, and no one would be upset?20:08
ttxOK, I think we have enough to iterate on the review -- we just need to go fast20:09
sdaguerussellb: further question, do we want admin APIs in defcore? I always get a mixed message on them from folks in terms of the guaruntees that come with them.20:09
zehicleideally, we should add more than remove20:09
*** vivek-ebay has quit IRC20:09
dhellmann(hypothetically)20:09
*** vivek-ebay has joined #openstack-meeting20:09
russellbsdague: they automatically exclude anything that is an admin API right now in their scoring20:09
dhellmannyes, well, adding is the easy case20:09
sdaguerussellb: ok20:09
zehiclesdague, no.  admin API are not considered core for now20:09
devanandasdague: that is an interesting question in teh context of our discussion about testing admin APIs with tempest last week20:09
devanandazehicle: good to know, thanks20:09
zehicle(which raises an issue since tempest requires admin access to test non-admin APIs)20:09
russellbsdague: i was saying something they called an admin api isn't one20:09
dhellmannI've updated the review with feedback from russellb and vishy20:09
sdaguedevananda: yep, that's what I wanted to bring it up.20:09
sdaguerussellb: sure20:09
russellbdhellmann: great thanks20:09
*** thedodd has quit IRC20:10
*** e0ne has joined #openstack-meeting20:10
sdaguerussellb: honestly, those sorts of issues are things we should probably fix in tempest as 'upstream' for this20:10
devanandazehicle: fwiw, that rules ironic out of defcore since it only presents an admin-facing api20:10
zehicledevananda, we are still trying to score the admin API because it's useful information20:10
ttxdamn germa s20:10
ttx+n20:10
devanandazehicle: ack20:10
russellband whether or not it's included really isn't our concern here20:10
zehicledevananda, there are several things that are out.  it;s about interop20:10
russellbwe're providing technical answers in this review20:11
devanandazehicle: indeed. just checking expectations :)20:11
zehicleif you cannot run both public and private using the core then it's not core (for this pass)20:11
*** nati_ueno has joined #openstack-meeting20:11
zehiclewe do expect that there will be broader sets in the future.  this pass is the min20:11
ttxok, shall we move on?20:11
zehiclethat's exactly why I want to make sure we keep scoring the admin apis20:11
dhellmannttx: that's all I had20:12
*** fnaval has joined #openstack-meeting20:12
russellb+1 on latest revision dhellmann just posted20:12
zehicleI'm happy to field questions on the defcore list or 1x1 as needed20:12
zehiclewe'll update the definitions to clarify if needed20:12
ttxzehicle: Once we are done with this cycle we'll discuss how to effectively do it for the others20:12
*** MaxV has quit IRC20:12
zehicle+120:12
ttxok, moving on20:12
ttx#topic Election behavior guidelines20:12
*** openstack changes topic to "Election behavior guidelines (Meeting topic: tc)"20:12
*** xianghui has joined #openstack-meeting20:12
ttxWe still have two proposals for addressing that issue:20:12
ttx* A resolution on standards of behavior during elections (https://review.openstack.org/100445)20:13
ttx* Adds a resolution addressing expected election behaviour (https://review.openstack.org/98675)20:13
* ttx quickchecks for recent changes20:13
ttxAt this point the main differences are:20:13
anteayamy understanding from last round was we were about to discuss to whom the tc wanted me to report20:13
ttxanteaya's proposal insists on the reporting procedure and spelling out the potential consequences20:13
anteayaand then we ran out if time20:13
ttxeglynn's proposal insists on the public call-out, includes a "pledge" part but also mentions the CCoC violation process as an in extremis solution20:13
ttxAt this point I could go with both -- I like that eglynn's proposal mentions both options, while I still dislike the pledge part20:14
ttxHowever I think they are using different words to express the same thing, at this point...20:14
markmcclainshould we try to converge on a single one this week?20:14
jeblairi'm strongly negative on the pledge part20:14
ttxor we should pick one depending on how strong we want our tone to be20:14
anteayafor those who don't know20:14
anteayaI have had to use a pledge in teh past20:14
anteayaand the pledge was in the person's own words, not mine20:14
anteayaand was in their handwriting, not copy/paste20:15
anteayathis was in the case of a lost ballot20:15
*** fifieldt has quit IRC20:15
ttxjeblair: could you explain why?20:15
anteayaand the person pledged to not vote twice if they got two ballots20:15
ttxI don't like it eiter but I think you'll have stronger arguments than I have20:15
dhellmannI like a lot of the preamble in eglynn's, but I agree with jeblair on the pledge and I don't think the "public shaming" aspect is going to be a good solution long-term.20:15
*** ominakov has quit IRC20:15
anteayaso I do use pledges, but boilerplate isn't helpful20:15
*** jecarey has joined #openstack-meeting20:16
markmcI'm strongly negative on quickly escalating outside of the technical community20:16
markmcand putting election officials in a very difficult position20:16
anteayamarkmc: to whom would you like me to report20:16
*** thedodd has joined #openstack-meeting20:16
*** penguinRaider has quit IRC20:16
markmcanteaya, eglynn's latest draft suggests that election officials should only be used for advice and guidance on how to resolve20:17
jeblairttx: we haven't seen any bad acting from candidates themselves, so i think it distracts from the actual problems we're responding to.  but also, i find forced pledges disingenous.  i find it distasteful that i might be required to say something i might not beleieve in.20:17
markmcresolution being discuss publicly or escalate to ED20:17
anteayaadvice and quidance to whom?20:17
markmcthe reporter20:17
anteayaI'm foggy20:17
dhellmannmaybe a version that had the good preamble, details about behavior for campaigners and candidates, and a reporting procedure to the TC (?) would be a reasonable compromise?20:17
anteayawho conducts an investigation?20:17
eglynnTBH the pledge isn't really the key aspect of my proposal, rather it's the promotion of a shared value-system in the community20:17
*** MarkAtwood has joined #openstack-meeting20:18
markmcanteaya, preferably an "investigation" isn't needed - if it is, it's the ED20:18
*** sarob has joined #openstack-meeting20:18
anteayawhat you also might not know was that I wanted to take this to the ml when it happened in the spring20:18
ttxeglynn: you could say the same thing without the "forced" pledge20:18
anteayathe person I talked to didn't want to do that20:18
ttxeglynn: saying that any candidate shall respect the expected behavior, or something20:18
anteayamarkmc: great, then that is what I'm for as well20:19
*** IlyaE has joined #openstack-meeting20:19
eglynnttx: sure, if the forced nature of the pledge raises freespeech hackles, I could work it out of the proposal20:19
anteayasince I didn't want to be the one getting the response from the person accussed of violations20:19
markmcanteaya, we'd now be setting the expectation that discussing publicly is the preferred first approach20:19
anteayathat was a comment on the patch I was asked to add20:19
anteayaI dis agree with taking it to the ml20:19
ttxI like that anteaya's proposal has a clear escalation procedure, but I can see how it can appear to ostrong as the only mechanism20:19
markmcclainI think that public discussion is a reasonable expectation20:20
anteayasince that might not bring a resolution in the time to retain the integrity of the election20:20
markmcclainI think that part of the problem in the spring is we didn't have anything documented20:20
*** VijayB has joined #openstack-meeting20:20
anteayaI suggested taking it ot hte ml20:20
anteayawhy was that not accepted then but is fine now20:20
ttxmarkmcclain: I expect any of the tewo proposals we have today to solve that20:20
anteayawhat has changed?20:20
markmcclainttx: agreed..writing something down is good20:21
markmcanteaya, what would have changed is that we'd have set the expectation that discussing publicly is the preferred first approach20:21
markmcat some point it has to become public20:21
anteayayes, it does20:21
dhellmannit should become public, but I don't think that's the *first* step, is it?20:21
markmcthat the issues last time around never became public is unsatisfactory20:21
ttxthey are getting pretty close. If anteaya adds public discussion and eglynn removes te pledge they would be pretty similar20:22
anteayaand if you want it happening during the election, that is up to the tc20:22
markmcfor genuine mistakes, I'd much rather a calm, adult conversation rather than the result of a formal investigation20:22
anteayaI see it potentially being disruptive to other elections running concurrently not involved in the event20:22
ttxdamn germans²20:22
eglynnttx: :)20:22
*** gyee has joined #openstack-meeting20:22
anteayabut that still doesn't solve markmc concern with mine20:22
dhellmannmarkmc: agreed - and a 1:1 with the election supervisor may be a better way to have that than posts to the ML20:23
anteayasince I am still reporting to the ED20:23
*** marun has quit IRC20:23
anteayaand I would like to hear whom I am to report to, if not the ED20:23
markmcclainmarkmc: I think that part of the problem with surfacing the issues publicly is that there wasn't any set expectation to protect either side20:23
jeblairyeah, honestly, if i got a weird campaign email, i'm not sure the first thing i'd want to do is post to the ml; i might want to chat with someone first20:24
markmcclainjeblair: +120:24
eglynnmarkmcclain: what sort of protection would be required, anonymity?20:24
*** ivasev has quit IRC20:24
dhellmannI have seen the negative effects on a community where taking grievances directly to the mailing list was considered normal. We do not want to do that.20:24
* ttx shall stop watching the game now20:24
markmcclaineglynn: mainly process20:24
anteayaand people did ask me questions, but I never got any facts20:24
anteayajust interpretation20:24
markmcjeblair, and if the sender apologized and you felt that had resolved the issue - why take it further?20:25
markmcclainboth sides should have an expectation of both behavior and ways to report20:25
anteayawithout being able to arrive at my own20:25
*** ivasev has joined #openstack-meeting20:25
markmcclainthe last thing we should do is to make things up on the fly20:25
markmcjeblair, which is what happened in the case I'm aware of20:25
markmcjeblair, I'm very afraid of turning that into a rapid escalation20:25
anteayawhy rapic20:25
anteayad20:25
anteayawhy do you think this would be rapid20:26
zanebttx: probably a good thing you stopped watching ;)20:26
*** MaxV has joined #openstack-meeting20:26
jeblairmarkmc: i'm not sure it's the sender i'd want to talk to.  i don't want to get on the bad side of someone who feels it's okay to send campaign spam.20:26
markmcanteaya, you're talking about a resolution before the election finishes, right?20:26
anteayamarkmc: or decison that sees an election ending and a new one starting20:26
markmcjeblair, meh; if we can't as a community reinforce our culture amongst ourselves ...20:27
anteayaif a decison can be reached in that time20:27
*** arnaud has joined #openstack-meeting20:27
*** arnaud__ has joined #openstack-meeting20:27
anteayabut if as you say this was a genuine mistake, with apology20:27
*** gyee has quit IRC20:27
anteayado you feel I would reach the same conclusion as yourself?20:27
anteayado you feel I can recongize a genuine mistake?20:27
markmcanteaya, let's not make it about you - I worry that not all election officials would be even-handed20:28
jeblairmarkmc: we're not all comfortable being confrontational.  and in public.  i'd like to keep the door open to people that might want to help our elections stay clean but whose first inclination is not to start a kerfufle on the mailing list :)20:28
dhellmannanteaya: you might not always be our election coordinator, so we shouldn't make this about *you* personally20:28
dhellmannjeblair: +120:28
*** fifieldt has joined #openstack-meeting20:28
ttxjeblair: +120:28
anteayamarkmc: fair enough but I would hope that future election pairs would be even-handed20:28
markmcsetting up a process which could turn a genuine mistake into a nasty situation ...20:28
*** safchain_ has quit IRC20:28
anteayadhellmann: no I agree, but future pairs of election officials20:29
dhellmannmarkmc: do you think it's more likely the TC could avoid that than an individual election official?20:29
markmcdhellmann, yes, very much so20:29
*** yamamoto has joined #openstack-meeting20:29
sdaguehonestly, I'm not sure I even have a strong lean at this point. I can see both of these approaches. I do get concerned though if we aren't actively reenforcing our culture, even if it means some conflict.20:29
markmcdhellmann, the only issue is the weird situation with half of the TC not having a mandate20:29
dhellmannok, so let's have the election official report to the TC and then issue a report to the ML20:29
anteayasdague: +120:29
anteayadhellmann: I can do that20:30
dhellmannmarkmc: true, but half does20:30
anteayaor half the tc20:30
anteayaor the tc delegation20:30
anteayaor however the tc wants to identify the group20:30
*** ivasev_ has joined #openstack-meeting20:30
anteayapersonally I would prefer it20:30
*** oanufriev has quit IRC20:30
*** denis_makogon has joined #openstack-meeting20:30
anteayathen if the tc wants, the tc can report to the ED20:31
dhellmannthe full tc, including those up for re-election, to avoid having 1/2 stage a coup :-)20:31
markmcand I'd hope the TC would use it as a "teachable moment" as eglynn puts it20:31
anteayadhellmann: I'm fine with that too20:31
markmceven if a mistake, discuss openly so everyone learns20:31
*** MaxV has quit IRC20:31
dhellmannyes, I would lean heavily toward dealing with it quietly unless it was an extreme case20:31
anteayadhellmann: I would just need timeframes, this group prior to this date, this group after this date20:31
markmcclaindhellmann: +120:31
dhellmannperhaps leaving names out of the public discussion, for example20:31
anteayaI'm for reduction of gossip20:32
markmcsuggest this at one point - http://paste.openstack.org/show/85709/20:32
*** mestery has quit IRC20:32
markmcin the review20:32
anteayaget to the facts, address the facts20:32
anteayagossip just hurts everybody20:32
*** gyee has joined #openstack-meeting20:32
dhellmannanteaya: the TC is the TC until the elections are complete, no?20:32
ttxmarkmc: sounds good20:33
ttxdhellmann: half of it is running for election though20:33
*** ivasev has quit IRC20:33
ttxso I like the idea that the half that still has 6 months to go would consider te complaint20:33
anteayadhellmann: yeah, see that is where I need some timeframes20:33
dhellmannttx: ok, I can go along with that20:33
*** jecarey has quit IRC20:33
anteayamarkmc: I'm fine with the paste20:34
*** sweston_ has joined #openstack-meeting20:34
dhellmannmarkmc: I like what you have in that pastebin20:34
*** padkrish has quit IRC20:34
*** dkranz has quit IRC20:34
dhellmannwho's going to work on bringing these 3 things together?20:34
anteayadhellmann: do you want to?20:34
*** yamamoto has quit IRC20:34
* dhellmann should have seen that coming20:34
dhellmannsure, if you like20:34
markmchehe20:34
anteayadhellmann: thanks20:34
*** samcdona_ has joined #openstack-meeting20:34
ttxheh20:35
markmcclaindhellmann: I can work with you too20:35
dhellmanndo we want a third proposal?20:35
dhellmannmarkmcclain: thanks20:35
*** overlayer has joined #openstack-meeting20:35
eglynnI like most of markmc's proposal, except for the optional redaction of names20:35
ttxdhellmann: or iterate on one of the others, your call20:35
markmcdhellmann, no harm in another proposal, bring elements of each together20:35
dhellmannok, I'll probably do a third just to keep it clear20:35
anteayadhellmann: do as you see fit, as long as someone is willing to report behaviour that is questionable so it doesn't perist, I'm happy20:35
ttxdhellmann: famous last words20:36
dhellmannttx: don't you have a game to watch?20:36
*** padkrish has joined #openstack-meeting20:36
zanebeglynn: because you don't want them redacted, or you don't want it to be optional?20:36
ttxdhellmann: somehow the germans stopped scoring at 5-020:36
*** leonchio_ has joined #openstack-meeting20:36
eglynnzaneb: both ... I'd prefer to avoid speculation and rumor as to who was involved20:36
*** thangp has quit IRC20:36
dhellmannttx: Je suis désolé20:36
ttxok, ready to move to next topic ?20:37
*** samcdona has quit IRC20:37
*** samcdona_ is now known as samcdona20:37
* markmc is 50/50 on redaction - wouldn't want "shaming", wouldn't want rumors, would hope we can be adults, yet names aren't required for it to be a teachable moment20:37
markmcclainttx: I think we've covered this one20:37
ttxok then20:38
ttx#topic Other governance changes20:38
*** openstack changes topic to "Other governance changes (Meeting topic: tc)"20:38
*** MaxV has joined #openstack-meeting20:38
ttx* Resolution requesting designated sections from projects (https://review.openstack.org/100675)20:38
ttxI suspect we should abandon this one now, let me know if you disagree20:38
ttx* Add translation support requirement (https://review.openstack.org/97872)20:38
*** baoli has quit IRC20:38
mikalI agree20:38
ttxThere seems to be some guidance needed as to the type of testing we require20:38
ttxI tried to comment to that effect20:39
dhellmannyes, do we need to write up the formal response or is the log from the last meeting enough?20:39
dhellmannoops, that was about the designated sections :-)20:39
*** novas0x2a|lapto1 has joined #openstack-meeting20:39
*** Mandell_ has joined #openstack-meeting20:39
markmcdhellmann, russellb's summary blog is plenty clear IMHO20:39
ttxdhellmann: I don't think we need to write up that we wn't make a resolution on something... But if you think that's useful, we could20:40
dhellmannmarkmc: ok, I think I missed that so I'll look for it.20:40
*** overlayer has quit IRC20:40
dhellmannttx: nah, I wasn't sure what the defcore committee wanted20:40
markmcunless anyone objects to how it characterizes what went on?20:40
russellbhttp://www.openstack.org/blog/2014/07/openstack-technical-committee-update-july-1/20:40
*** yamamoto has joined #openstack-meeting20:40
*** ttrifonov is now known as ttrifonov_zZzz20:40
ttxis sdague around?20:41
sdaguettx: yes20:41
markmc#link http://www.openstack.org/blog/2014/07/openstack-technical-committee-update-july-1/20:41
ttxsdague: it looks like Andreas and the i18n folks want more... precision of what kind of tests we want20:41
jeblairif there's a test, it should be a gate test, not a periodic one20:41
*** Mandell has quit IRC20:42
dhellmannrussellb: good write-up20:42
markmcjeblair, you basically need to run everything in every locale20:42
sdaguejeblair: I think that's probably a different discussion20:42
ttxI just want the blatant hole covered, but yeah, I agree that if it's not gating it's likely to be ignored20:42
russellbdhellmann: thank you20:42
*** novas0x2a|laptop has quit IRC20:42
markmcjeblair, running on just the translation import jobs might do it20:42
*** mkoderer has quit IRC20:42
jeblairsdague: sure, but it was a question actually asked in the review :)20:42
sdaguettx: the problem is, it's going to be ignored in the gate anyway20:42
sdaguepeople will recheck grind on it20:42
sdagueif it's not working20:43
russellbdhellmann: had review/editing help from ttx, markmc, sdague (at least, sorry if i forgot someone)20:43
*** jamespage_ has joined #openstack-meeting20:43
ttxsdague: except I suspect rechecking won't really help ?20:43
*** jamespage_ has quit IRC20:43
jeblairsdague: i think the case being considered is when translations actually just don't work, yeah20:43
ttxdoesn't seem like the type of test that would trigger rare issues20:44
*** Mandell_ has quit IRC20:44
jeblairmarkmc: that makes sense if it's the translation import that's most likely to break operation due to errors20:44
jeblairmarkmc: is that the case?20:44
ttxanyway, just wanted to attract your attention to the fact that they need some guidance there20:44
jeblairor is it the case that people could break things by changing some log format translation function call or something?20:44
markmcjeblair, I think so - struggling to concoct another case20:44
sdaguettx: sure, sorry, with all the gate stuff my queue of paying attention is sort of at overflow20:45
jeblair(i'm genuinely asking -- i'm not that familiar with the mechanisms here)20:45
dhellmannjeblair: it's possible someone could remove arguments to a message, and the existing translations would then expect a value that isn't present20:45
*** yamamoto has quit IRC20:45
jeblairdhellmann: and that would only be detected if you set a non-c locale?20:45
*** ttrifonov_zZzz is now known as ttrifonov20:45
dhellmannjeblair: yes, because the default message would be changed in place20:45
markmcjeblair, it's usually a format string that the translator has messed up such that we get format errors at runtime20:45
ttxmarkmc: there were unusable translatons shipped in releases in the past... would be good to look back at those cases ad see what made tem fail20:45
sdagueyeh, this is the thing where I'm sort of surprised the i18n team doesn't have an answer, because they know what's supposed to work in a real cloud. I'd kind of expect them to propose what they expect to work in such a situation.20:45
markmcjeblair, there is some automated checking of that with msgfmt -c, but it's not perfect AFAIR20:46
sdagueand then we go from there20:46
*** nati_ueno has quit IRC20:46
dhellmannOTOH, the Message class could be made to trap those formatting errors and return the original message20:46
markmcdhellmann, possible, yeah20:46
markmcclaindhellmann: that seems more elegant20:46
* dhellmann checks if that's already the case20:46
*** nati_ueno has joined #openstack-meeting20:46
ttxanyway, I think we can provide guidance on that review20:46
ttxno need to solve it now20:47
dhellmannI don't see it doing anything that smart. I'll open a bug for that.20:47
jeblairif we want more, due to the combinatorics inovlved, we may want to use static analysis20:47
jeblairttx: ack20:47
ttx* Modify Images mission to fit Artifact Repository (https://review.openstack.org/98002)20:47
*** ominakov has joined #openstack-meeting20:47
ttxI think we have a winner there20:47
ttxthe title change is still blocked on marketing feedback20:48
ttxdue next week.20:48
ttxso approving the mission change would effectively unblock glance20:48
*** vivek-ebay has quit IRC20:48
jeblairchanging the mission now and title later seems like a good path forward20:48
russellb+120:49
ttxwe can tweak the program name later when everyone is comfortable with it20:49
*** vivek-ebay has joined #openstack-meeting20:49
ttxcool, will approve when it gets 7 YES20:49
ttxif it hasn't already20:49
jeblairalso, if it completely fails to happen, we don't have egg on our faces.  :)20:49
russellbha, fair point20:49
ttx#topic Housekeeping changes (programs.yaml)20:49
*** openstack changes topic to "Housekeeping changes (programs.yaml) (Meeting topic: tc)"20:49
ttxThose changes will all be approved unless someone complains:20:49
ttx* Adding Horizon mission statement (https://review.openstack.org/102050)20:49
ttx* Rename security-guide to security-doc (https://review.openstack.org/104295)20:49
ttx* Add docs-specs repo to Documentation program (https://review.openstack.org/104293)20:50
ttx* add keystonemiddleware to keystone projects (https://review.openstack.org/102305)20:50
russellbstill a -1 from dhellmann on horizon mission statement20:50
ttxdhellmann: do you stand by it? Or is david-lyle reply acceptable to you ?20:50
*** Mandell has joined #openstack-meeting20:50
*** thinrichs has joined #openstack-meeting20:50
dhellmannI'll stick with my -1 but won't object if someone wants to vote to overrule me. I think it's a mistake to mix implementation requirements into the mission text.20:51
*** hashar has quit IRC20:51
ttxOK, I'll wendar ait for majority vote on that one then20:51
ttxerr20:51
ttxI'll wait for majority vote20:51
ttxtabfail20:51
*** xyhuang has joined #openstack-meeting20:52
ttx#topic Open discussion20:52
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:52
ttxLooks like we can get the K vote started20:52
russellbawesome!20:52
russellbhave the final list of candidates?20:52
ttxlet me see which options passed the checks20:52
ttxunfortunately Kepler didn't make it20:52
ttxso I asked that we add Kilo20:53
jeblair??20:53
ttxjeblair: Nvidia Kepler blame20:53
markmcpoor kepler, we barely knew him20:53
ttxGPUs for cloud computing20:53
* eglynn loses his bet on Kepler :(20:53
ttxjust a sec20:53
ttxfetching list20:53
ttxKeryado, Kleber, Kourou, and Kyoto + Kilo20:54
dhellmannKléber has a metro stop close by for photo ops.20:54
ttxWe can still remove a name from that list if we want to20:54
russellbKyoto and Kilo are separate options right?  :)20:54
jeblairkyoto is amusing from the standpoint of having chosen "havana" when we were in portland.  :)20:54
ttxKyoto is a bit disturbing since Place de Kyoto in Paris doesn't even show on Goog Maps20:55
markmcclainjeblair: was thinking the same thing20:55
dhellmannwe almost have to pick kyoto20:55
ttxI almost want to remove Keryado, since it's really small in Brittany, and not really a fun exception20:56
ttxbut then, we can keep them all20:56
ttxKourou is fun as well, since it's in South America20:56
ttxand is in the space theme20:56
*** mestery has joined #openstack-meeting20:56
markmckilo, less typing20:56
markmcwe should have a 4 letter limit20:57
mikalAlso, its time for openstack to go metric20:57
russellbi'd love a kilo of openstack right about now20:57
ttxanyway, I will start the public poll, probably thursday20:57
ttxAnd yes, I'll vote Kilo20:57
russellbtakes the edge off20:57
jeblairmarkmc: one letter limit!20:57
ttxIt's been named K for so long anyway20:57
ttxit has to stand for Kilo20:57
russellbyup20:57
zanebyah, in my head it's already Kilo20:57
ttxAnything else, anyone20:58
ttxzaneb: unfortunately devs are not the only ones to vote, so expect Kyoto to win20:58
zaneblol20:58
* zaneb thought Jeckyll was robbed20:58
* markmcclain agrees20:58
russellbzaneb: agreed20:58
jogottx: any thoughts of having the TC sort out API feature discoverability. several projects are independently looking into it20:59
zanebttx: maybe you should also send the announcement to openstack-dev? I usually miss it on the openstack list20:59
clarkbthere is a kyoto france?20:59
ttxclarkb: there is a place de Kyoto Paris (the icehouse exception)20:59
ttxjogo: which projects?21:00
ttxjogo: could be a good cross-project meeting topic / ML thread first21:00
russellbclarkb: http://fr.wikipedia.org/wiki/Place_de_Kyoto21:00
*** shakamunyi has joined #openstack-meeting21:00
jogottx: nova (indirectly) and trove21:00
ttxok, we are out of time21:00
jogottx: good point21:00
sdaguejogo: I think that's got to be ML thread21:00
markmcclainjogo: neutron too21:00
ttx#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Tue Jul  8 21:01:07 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-07-08-20.02.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-07-08-20.02.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-07-08-20.02.log.html21:01
clarkbrussellb: thanks21:01
ttxThanks everyone, good one21:01
ttxdhellmann, dolphm, notmyname, eglynn, markwash, jgriffith, mikal, zaneb, david-lyle, mestery, SlickNik, SergeyLukjanov: around ?21:01
*** jdob has quit IRC21:01
eglynno/21:01
dhellmanno/21:01
mesteryo/21:01
zanebo/21:01
david-lyleo/21:01
dolphmo/ for just a couple minutes21:01
notmynamehere21:01
ttxdidn't plan to have a meeting today, but mtreinish added an agenda item!21:02
SergeyLukjanovo/21:02
mikalHi21:02
mtreinishttx: heh, I'm not the only one21:02
markwasho/21:02
ttxand eglynn21:02
ttxdamn you all!21:02
eglynnsorry!21:02
ttx#startmeeting project21:03
openstackMeeting started Tue Jul  8 21:03:01 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
*** openstack changes topic to " (Meeting topic: project)"21:03
openstackThe meeting name has been set to 'project'21:03
* eglynn didn't realize the meeting was off21:03
ttxAgenda for today is available at:21:03
*** pballand has quit IRC21:03
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:03
ttx#topic Actions from previous meeting21:03
*** openstack changes topic to "Actions from previous meeting (Meeting topic: project)"21:03
ttxI documented SPD and SAD, in case you want to use them for Juno in your projects:21:03
ttx#link https://wiki.openstack.org/wiki/SpecProposalDeadline21:03
*** MaxV has quit IRC21:03
mesteryttx: Thanks!21:03
ttx#link https://wiki.openstack.org/wiki/SpecApprovalDeadline21:03
*** shakamunyi has quit IRC21: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
ttxThere were no 1:1 sync points today since I've been traveling21:03
ttxIf any of you has news items, just shout now21:03
ttxSwift 2.0.0 was out but I guess everyone noticed that21:04
ttx#topic Other program news21:04
*** openstack changes topic to "Other program news (Meeting topic: project)"21:04
dhellmannI'm starting work on cross-project unit test jobs (https://review.openstack.org/#/c/95885/) in the next couple of days.21:04
ttxInfra, QA, Docs... anything you'd like to mention ?21:04
ttxdhellmann: what is a cross-project unit test?21:05
* ttx follows link21:05
dhellmannttx: running unit tests for projects using master of oslo libraries, and vice versa21:05
ttxdhellmann: ah, ok21:05
zanebnifty21:06
dhellmannwe already have integration tests via d-g, but this will prevent breaking unit tests with new releases (we did that a couple of times last cycle)21:06
devanandadhellmann: ++21:06
*** shakamunyi has joined #openstack-meeting21:06
ttxany other news ?21:06
ttx#topic Neutron parallel gate job switchover (mtreinish)21:07
*** openstack changes topic to "Neutron parallel gate job switchover (mtreinish) (Meeting topic: project)"21:07
ttxmtreinish: floor is yours21:07
mtreinishttx: ok thanks21:07
*** markmcclain has quit IRC21:07
mtreinishso switching the neutron jobs over to parallel is going to happen soon21:08
mesterymtreinish: Yay!21:08
ttxmtreinish: didn't we do that once already ?21:08
mtreinishright now they're the only jobs that still run tempest serially in the gate21:08
mtreinishttx: not for the neutron jobs21:08
ttxok21:08
sdaguettx: no, we got really close, then the January massive gate wedge happened21:08
mtreinishwe've had a nonvoting job parallel job for a while21:08
mtreinishso the question I wanted to get opinions on was whether we make the switch everywhere21:09
mtreinishor we have an asymmetrical gate with neutron (ie switch it to gate parallel for neutron and leave it serial on all the other projects)21:09
mtreinishthe concern from salv-orlando and others was that the reliability of the jobs goes down slightly after switching to parallel21:10
russellbis neutron running all of tempest yet?21:10
mtreinishrussellb: this switch will include that more or less21:10
russellbi see.  ok21:10
mikalI feel like you should make it everywhere if you're going to do it21:10
mikalBut if its unreliable, probably shouldn't do it at all21:10
jogomtreinish: I think switching neutron first sounds good, so if things do go wrong they don't bring everything down.21:10
ttxmtreinish: did you quantify the difference in ... reliability ?21:10
mtreinishttx: salv-orlando's ML thread had some numbers21:11
mtreinishlet me pull up that link21:11
jogomtreinish: I am a fan of making changes like this slowly and carefully and not all at once21:11
sdaguemikal: well everything is unreliable to some degree. Nova fails unit tests in the gate some times. It's all a matter of degrees.21:11
mtreinish#link http://lists.openstack.org/pipermail/openstack-dev/2014-June/038496.html21:11
mikaljogo: I agree it should be rolled out in steps, but I thik the end goal should be consistency21:11
ttxjogo++21:11
jogomikal: yup21:11
mtreinishjogo: the concern with it being asymmetrical is that we will break the neutron gate at some point21:12
jogomtreinish: can we leave one serial job in neutron gate?21:12
jogojust to be safe21:12
devanandaso in a situation like this, i'd prefer to make it voting within the project but not elsewhere yet21:12
*** markmc has quit IRC21:12
mtreinishjogo: it's the reverse case21:12
sdaguejogo: that's not actually the concern21:12
devanandaprimarily to help developers within the project avoid introducing new issues that this would catch21:12
mikalSo... Making this change would triple the fail rate?21:12
mikalOr am I reading this wrong?21:13
jogosdague: what is the concern, sounds like i am missing something21:13
devanandamikal: taht's how I read it, too21:13
mikalTriple is a pretty big increase21:13
mikal(Noting that it might be telling us about actual neutron bugs though)21:13
sdaguejogo: in parallel things like hitting keystone and the rest of the services change dramatically21:13
sdagueif they change an access pattern that doesn't work for neutron, neutron is wedge, and they can't fix it21:13
devanandafrom ~10% to ~30%21:13
mtreinishmikal: it should only be about 2x21:14
mtreinishmikal: there are still some outstanding big bugs which is why we haven't switched yet21:14
mikalmtreinish: ahhh, at the end of the email he says 2x _if_ some bugs can be fixed21:14
sdagueactually, you have to compare the check queues21:14
*** arnaud__ has quit IRC21:15
*** arnaud has quit IRC21:15
mikal"Summarizing the only failure modes specific to the full job seem to be C &21:15
mikalD. If we were able to fix those we should reasonably expect a failure rate21:15
mikalof about 6.5%. That's still almost twice as the smoke job, but I deem it21:15
mikalacceptable for two reasons"21:15
jogosdague: right, but what is the risk of moving neturon to parallel before the rest?21:15
sdaguejogo: because this job doesn't just test neutron21:15
sdagueit's a configuration that includes neutron21:15
sdaguetesting everything21:15
jogosdague: ah right, so keystone may wedge neutron only21:15
sdagueyep21:15
devanandaso the summary at the end of that mail seems to support teh possibility of making it asymmetric initially21:15
mtreinishjogo: or more likely nova...21:15
jogoI think that risk is fairly small, while the risk of parallel neutron breaking everything is higher.21:16
*** e0ne has quit IRC21:16
sdaguejogo: honestly, with all the races in security groups in nova that we've been diving in, I'd actually say there is a pretty good chance we're going to 'fix' something and break neutron in the process.21:16
ttxmtreinish: I still tend to prefer enabling it for neutron only as a first step, but I'll happily defer to the gatemasters21:17
sdaguettx: honestly, I'm actually good with neutron first as well21:17
mtreinishttx: well I was initially opposed to that, but I don't really feel to strongly about it21:17
sdaguebut I did want to make sure the other side downfalls were clear21:17
jogosdague: that may be true. Sounds like we agree21:18
mtreinishas long as we keep our eyes open about the issues with doing it21:18
sdagueso it means if we do that, the core teams for other projects are going to have to sign up to moving on changes fast if they broke neutron21:18
ttxmtreinish: the goal being... to flesh out issues without breaking everyone else... and make it all parallel asap21:18
mtreinishdevananda: knows firsthand how much fun an asymmetrical gate is21:18
mesterymtreinish: ++21:18
*** zdiN0bot has quit IRC21:18
*** baoli has joined #openstack-meeting21:18
ttxok, anything else on that topic?21:18
devanandamtreinish: indeed ....21:19
jogomtreinish: you said this will enable full tempest too?21:19
mtreinishjogo: yes21:19
mtreinishalthough there are still a bunch of skip if neutrons in there because of api issues21:19
jogomtreinish: awesome then we can do https://review.openstack.org/#/c/100033/ after21:19
mtreinishttx: that's all I had, we've got a direction to move this forward when it's ready21:19
sdaguejogo: no, I really don't want to do that21:19
*** jprovazn has quit IRC21:20
ttxok, I think we can move on then21:20
ttx#topic Are we digging ourselves into a backporting hole with branchless Tempest? (eglynn)21:20
jogosdague: oh? lets talk after21:20
*** openstack changes topic to "Are we digging ourselves into a backporting hole with branchless Tempest? (eglynn) (Meeting topic: project)"21:20
eglynncontext is: in ceilo we're begining to see featureful backports to stable just to facilitate branchless Tempest21:20
ttxeglynn: here is the mike21:20
eglynnexample ... https://review.openstack.org/10486321:20
eglynnin this case it was a kinda featureful fix for a bug of *omission* ... i.e. ceilo wasn't handling the cinder notification at all21:20
ttxthey shall be rejected by the stable team, no?21:20
devanandai've been wondering when this would be brought up21:21
*** mspreitz has quit IRC21:21
devanandaironic hasn't hit it yet, but i've started to suspect we will hit this soon21:21
sdagueeglynn: so are notifications part of your API contract?21:21
eglynnttx: yep would be in the normal course of events21:21
eglynnsdague: so question is ... is leaving the backporting policy unchanged a goal of branchless tempest?21:21
sdagueeglynn: the point was to enforce published API contract21:21
sdaguebecause we were slipping it a lot21:22
eglynnso I guess the key problem is that some of these ceilometer tests are not strictly API tests21:22
*** sarob has quit IRC21:22
sdagueok, so then they probably shouldn't be in tempest21:22
eglynni.e. we want to assert that a certain notification emitted by another service is consumed by ceilometer and the expected metering datapoints appear in ceilometer21:22
*** rbowen has quit IRC21:23
eglynnsdague: do we have another integration tets harness for such tests to go to? ;)21:23
sdagueeglynn: nope21:23
dhellmannthis is a bit like saying "when we ask nova's API to launch an instance, it actually makes a usable instance"21:23
devanandaeglynn: what about if you add a certain notification, say during the Juno cycle, which wasn't in Icehouse, and want to test that?21:23
devanandaeglynn: is taht the situation you're in, or have i misunderstood?21:23
eglynndevananda: so basically the situation is a little like scenario #1 "New Tests for new features" in the BP21:23
sdaguedhellmann: so I consider a working compute part of the API contract21:23
eglynn#link https://github.com/openstack/qa-specs/blob/master/specs/implemented/branchless-tempest.rst21:24
*** vrovachev has joined #openstack-meeting21:24
mtreinishdevananda: https://github.com/openstack/tempest/blob/master/README.rst#1-new-tests-for-new-features21:24
eglynn... but without the obvious discoverability in this case21:24
dhellmannsdague: an ceilometer says that the events it collects will be returnable by the API, but the API itself does not specify what events are collected -- like nova doesn't specify which images are availble21:24
jeblairi'm sorely lacking in background here, but it seems like "datapoints appear in ceilometer" might be part of the api contract; similarly to a nova instace showing up21:24
devanandaright, without discoverability21:24
dhellmannsdague: because new event types can be created by end-users through the API, deployer custom code, etc. The API doesn't specify the event names.21:25
jogothis sounds like an issue in the ceilometer API itself21:25
eglynnjeblair: the API is the same ol' API, i.e. the query doesn't required a bump in the API version21:25
sdaguedhellmann: ok, then the tempest test proposed isn't valid21:25
sdaguebecause it makes too many assumptions on something not in the API21:25
eglynnjogo: I fear we may be bending the problem to fit the "solution"21:25
dhellmannsdague: so we don't want any tests that say that ceilometer does actually collect data from the other services?21:26
sdaguedhellmann: is it a required part of the API?21:26
jogoeglynn: ? can you elaborate. I  meant having an open ended API like that without discoverability is dangerous21:26
eglynnsounds way too restrictive for an integration test harness21:26
dhellmannI think we want that tested somewhere, even though the list of events isn't defined in the ceilometer API.21:26
eglynnso I was chatting with dkranz a bit about this earlier21:26
devananda"can I store arbitrary data in this API" vs "when cinder does $thing, did $value get stored in ceilometer" ?21:26
dhellmannsdague: yes, ceilometer says it will "collect events" but it doesn't say which ones21:26
eglynndkranz had the idea of micro-versioning the service (as opposed to the API)21:27
eglynn... so that a test can be skipped on the basis of whether a particular commit is available or not21:27
sdagueeglynn: how would that be reflected on a public cloud?21:27
eglynn... which gives fine-grained discoverability when tempest is run in-CI-gate21:27
*** baoli has quit IRC21:28
eglynnsdague: I was waiting for you to ask that ... it doesn't help in that case21:28
*** zaneb has quit IRC21:28
eglynn... it seems like forcing tempest to do double-duty in that regard will restrict what we put into tempest (in it's role as the integration testing harness for the CI gate)21:28
sdagueright, so I think this becomes one of those things where people keep throwing tests at tempest that aren't of the level of stability to really be part of it21:28
devanandaso is "able to collect data" the feature? or "ceilo actually collects data from $service"? If the latter is the feature being tested, then AIUI, it's not related to the API version at all21:29
devanandaeglynn: is ^ a fair summary of the question?21:29
*** yamamoto has joined #openstack-meeting21:29
dhellmannI don't see this as a "stability" question, though. The problem is the events collected actually depend on ceilometer's pipeline configuration file as much as code.21:29
eglynndevananda: yep, the latter21:29
devanandaeglynn: I feel like Ironic is bumping against a similar challenge with scenario testing21:29
*** arnaud has joined #openstack-meeting21:29
*** SlickNik has joined #openstack-meeting21:29
eglynnso do we need to split off the CI-focused and the public-cloud-capability-test-focused aspects of Tempest?21:29
sdagueyeh, I think what's emerging is that for a long time we basically had unit tests and tempest21:30
sdagueand I don't think that's the right approach going forward21:30
devanandaeglynn: because I actually want to test what /nova/ does, and even though it's API isn't changing, in a future version of OpenStack, it may be capable of doing more things with Ironic than it is today21:30
sdagueI think that projects really should have functional tests that run against a devstack just for their project which is in this middle ground21:30
devanandaeglynn: which sounds similar to you testing the cinder->ceilo messages, not ceilo's API itself21:31
eglynndevananda: yep, and would those extra things be externally discoverable?21:31
sdagueand Tempest needs to stay at the API stable boundary21:31
devanandasdague: ++21:31
devanandaeglynn: nope.21:31
devanandaeglynn: since Nova doesn't expose what driver is being used21:31
eglynndevananda: k, so same problem I think21:31
sdagueeglynn: right, because you actually want white box testing21:31
dhellmannsdague: those tests need to protect us so a project can't change the format of an event and that break ceilometer21:31
jeblairneutron has some functional testing along those lines21:31
dhellmannso we can't just run them against the project21:31
eglynnsdague: "projects really should have functional tests that run against a devstack just for their project" --> does that scale?21:32
devanandaso we definitely need integration tests for the various cross-project interactions like this21:32
*** Mandell has quit IRC21:32
sdagueeglynn: honestly, it scales better than the current model21:32
dhellmanndoes that mean another functional test suite that is not tempest?21:32
devanandawhich is what tempest originally provided, based on my limited understanding21:32
eglynn(scale in terms of the QA exterpise to build such a harness on a per-project basis)21:32
*** asettle has quit IRC21:32
clarkbswift does it too21:33
sdaguedhellmann: I actually think these are functional tests in the project itself21:33
eglynn(also in terms of CI resources to run all these seperate mini-tempests)21:33
sdagueceilometer owns ceilometers functional tests21:33
*** mestery has quit IRC21:33
dhellmannsdague: but ceilometer will be depending on information coming from other projects for these tests21:33
jogoshouldn't all cross-project interactions be versioned to help address this issue?21:33
*** mestery has joined #openstack-meeting21:33
jogowith tested APIs21:33
devanandasdague: so what if $otherproject breaks the APi contract between it and ceilo?21:33
eglynndevananda: exactly21:33
devanandasdague: ditto for eg. nova <-> ironic21:33
*** yamamoto has quit IRC21:33
dhellmannjogo: yeah, there's no contract on notification format at all right now, afaict21:34
sdaguedevananda: so I think we actually can solve that with things like the contract unit test job we put in nova21:34
devanandaor, for taht matter, any project and keyustoneclient21:34
mtreinishdhellmann: yeah and I think that's the crux of the issue here21:34
jogodhellmann: IMHO that is a bad21:34
eglynnso the contract around notifications is different to an API21:34
sdagueeglynn: there is no contract on notifications21:34
devanandaeglynn: eh?21:34
dhellmanntotally agree; and jd__  had a blueprint to work on it but didn't get much traction21:34
eglynnnotifications are versioned usually, for example21:34
dhellmanneglynn: rpc payloads are versioned, but are notifications?21:34
dhellmannthat might have changed since I was involved closely with this part of ceilometer...21:35
*** Sukhdev has joined #openstack-meeting21:35
eglynndhellmann: I mean *not* versioned21:35
dhellmannah21:35
eglynnFreudian slip :)21:35
jogoeglynn: heh21:35
sdagueso here is my point of view based on a month of trying to dig us out of current gate situations.21:35
*** ItSANgo has quit IRC21:35
sdagueI don't think the current model of pile more into tempest, and expand tempest scope, is helping21:35
sdaguebecause people aren't helping fix the issues21:36
sdaguethey are just recheck grinding21:36
sdagueso functional / grey / white box testing that people recheck grind on because their nova change is getting broken by a ceilometer test.... I'm not sure that's going to help us move forward21:37
jogos/tempest/OpenStack/ and that statement is still fairly true21:37
eglynnsdague: isn't there's also a strong incentive to pile more & more into tempest in terms of TC mandated requirements for tempest coverage?21:37
devanandajogo: exactly21:37
sdagueeglynn: there are API coverage needs21:37
devanandajogo: that's the crux of the problem, IMO, but also a different discussion21:37
sdaguebut testing the API, and doing functional testing of cinder notifications which were not provided by the API is different21:37
jogodevananda: agreed21:38
*** jackib has quit IRC21:38
vrovachevsdague: but these tests are good check compatibility projects21:38
*** jackib has joined #openstack-meeting21:38
*** rockyg has quit IRC21:38
dhellmannsdague: I agree with the need for separate tests. I don't agree that *all* of them can be project-specific.21:38
sdaguevrovachev: then they should be valid across an API21:38
jogosdague: can we redefine the question to, should this be an API discoverable thing?21:38
sdaguejogo: sure21:38
*** thinrichs has quit IRC21:39
*** acoles has quit IRC21:39
jogobecause this sounds like something that probably should be. If I am using a public ceilometer I want to know what it supports etc21:39
dhellmannjogo: We could add an API to ceilometer to discover what sort of data is being collected at all. But how do we version the response, if the deployer can change it.21:39
devanandasdague: in the case of ironic, the problem is the API being exercised is not the one being tested by tempest21:39
eglynnsdague: the interaction between ceilo and all services simply isn't API based in it entireity21:39
*** overlayer has joined #openstack-meeting21:39
*** jprovazn has joined #openstack-meeting21:39
jogoeglynn: I think thats one of the big issues here21:40
devanandaeglynn: in this situation, is the end-user communicating with ceilo, or is the notification API "hidden" behind other services?21:40
sdagueeglynn: right, I do get that. But I also get the scope problems we currently have.21:40
*** jprovazn has quit IRC21:40
vrovachevsdague: sdague: then it is necessary mock all API requests21:40
eglynndevananda: in this situation the end user snaphots a volume so they only interact with the cinder API21:40
sdagueeglynn: and you've caught me at a particular level of frustration, because realistically I've not been reviewing tempest code for the better part of a month now21:40
devanandaeglynn: i suspect again we're facing the same issue -- this isn't discoverable by tempest because tempest isn't talking to the API being tested21:41
sdaguebecause everyone wants to add new tests, no one wants to debug the fails we hit21:41
*** IlyaE has quit IRC21:41
vrovachevsdague: and this is tests to validate and not functional tests21:41
eglynndevananda: yes, in our case tempest talks to the ceilo API to check for a side effect of the interaction done via notifications21:41
devanandasdague: because there's a mandate that projects add more tests if they want to graduate / stay integrated21:41
*** zaneb has joined #openstack-meeting21:42
ttxOK, I think we should think a bit more about this and maybe discuss it n the list. Problem looks a bit more complex than we can solve in a one-hour IRC meeting21:42
sdaguedevananda: well, until we can dig out of the current fail pit, we can't really sort out the long term issues here.21:42
eglynnttx: I can bring the topic to the ML tmrw, if everyone is agreed to continue the discussion there?21:42
jogottx: ++21:42
sdagueeglynn: sure21:42
ttxeglynn: sounds good to me21:42
devanandaeglynn: ++21:43
eglynnsdague: cool thank you sir!21:43
ttxat least we established now that there is no easy way out21:43
SlickNikeglynn: Sounds good, thanks!21:43
ttx#topic Open discussion21:43
*** openstack changes topic to "Open discussion (Meeting topic: project)"21:43
ttxFeel free to continue discussing now :)21:43
ttxAnything else, anyone ?21:43
sdague:)21:43
ttxmeanwhile, in Brazil...21:43
markwashfor srs21:44
jeblairi haven't seen a gate status email to the dev list in a while21:44
jeblairdid i just miss it, or did folks stop sending those?21:44
* eglynn is running out of fingers to count the German goals ;)21:44
*** acoles has joined #openstack-meeting21:44
jeblairsdague, jogo, mtreinish: ^ ?21:44
sdaguejeblair: honestly, I ran out of energy to do them21:45
jogojeblair: I ahve been on vacation'21:45
ttxjeblair: do you miss them  / do you think they helped?21:45
jeblairit's apparent that sdague is frustrated, i just want to make sure everyone else actually knows that :)21:45
jeblairttx: i don't know.  from the sidelines, i thought they did21:45
*** shakamunyi has quit IRC21:45
jeblairi _personally_ found them helpful just to know what was going on21:46
jeblairthat's not a good enough reason to do them21:46
*** paulmo_ has joined #openstack-meeting21:46
*** shakamunyi has joined #openstack-meeting21:46
jeblairbut i did think that they usually got results for the top offending bugs21:46
sdaguejeblair: yeh, when it seemed like they were drawing more folks in, it was easier to get motived on them. But when the decision is 'do I write this up, or try to fix one of these' I've been opting for fixing21:46
dhellmannjeblair, sdague : I found them useful, too, to understand the state of what's being dealt with.21:47
mesterydhellmann: +1, I also found them interesting and useful as well.21:47
sdaguedhellmann: right, but did you find them useful enough to devote 3 days to fixing things :)21:47
*** Mandell has joined #openstack-meeting21:47
sdaguebecause being interesting isn't really the goal21:48
jeblairindeed21:48
*** vrovachev has quit IRC21:48
dhellmannsdague: if I had had 3 days, I might have, but I at least knew why my other patches weren't working and was less likely to recheck them as a result21:48
jeblairi'm not asking for myself, more thinking that if i'm surprised that sdague is frustrated by the gate status, perhaps other people who might be able to help would be as well21:48
sdagueso if I have commitments from people that me doing that will bring more people to fixing issues, that's an easy trade off21:48
dhellmannjeblair: right, I'm not asking sdague to keep it up, but I think it was valuable so maybe we need to find some community members who can take that task off his plate21:49
dhellmannnot everyone is going to be able to dive right in and debug, but summarizing the state of the most common gate failures doesn't require that level of expertise (at least I thin k not, maybe I'm wrong)21:49
*** arnaud has quit IRC21:50
jeblairdhellmann: i think you may be right; it probably requires paying some attention over time, but not huge expertise21:50
sdaguedhellmann: yeh, another volunteer to do that would be appreciated as well21:50
devanandajogo: sdague: any thoughts on what to use for white box integration testing as the scope of OpenStack continues to expand, and the gate becomes exponentially more complex?21:50
*** ItSANgo has joined #openstack-meeting21:51
*** leeantho has quit IRC21:51
sdaguedevananda: realistically, I think we need to reevaluate whether we think that's sustainable21:51
devanandathis is something we should probably start talking about since it seems to be on our minds already21:51
*** leeantho has joined #openstack-meeting21:51
ttxI think the gate news, IF relatively low cost, can help getting people interested21:51
*** jckasper__ has quit IRC21:51
*** Daisy has joined #openstack-meeting21:51
ttxAt least that gives me good posts to point people to when they ask "where should I help"21:51
devanandasdague: i don't think it is. I thought (and said) that over a year ago, fwiw21:52
dhellmannsdague: the board asked us at the summit how they can help, maybe we can take this specific request for volunteering to a few of them?21:52
sdaguedhellmann: sure21:52
*** zaneb has quit IRC21:52
sdagueI'd be more than happy to help bootstrap folks here21:52
jogodevananda: I agree with sdague on this one21:52
ttxOK, I think we can wrap up21:52
*** tbarron has quit IRC21:52
ttxbefore we kill the gate in frustration21:53
devanandajogo: i maen, i agree as well -- i don't think it's sustainable21:53
ttxwhen you think you had a bad day, consider Brazil's team day21:53
*** hrybacki has quit IRC21:53
jogoI fear OpenStack is facing feature sprawl without focusing on solidifying the foundations21:53
sdaguedevananda: realistically I think we need to be more surgical about this21:53
*** marun has joined #openstack-meeting21:53
sdaguebecause we can actually put contract points in, like we did with ironic on nova21:54
*** zaneb has joined #openstack-meeting21:54
*** vijendar has quit IRC21:54
ttxmaybe a topic for another meeting21:54
sdaguettx: sure :)21:55
devanandattx: yep21:55
ttxlast words ?21:55
*** rkukura has joined #openstack-meeting21:55
*** dims__ has joined #openstack-meeting21:55
sdagueyou just said it was open discussion21:55
ttxOK then, let's close it :)21:55
ttx#endmeeting21:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:55
openstackMeeting ended Tue Jul  8 21:55:37 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2014/project.2014-07-08-21.03.html21:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2014/project.2014-07-08-21.03.txt21:55
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2014/project.2014-07-08-21.03.log.html21:55
ttxThanks everyone!21:55
*** caleb_ has joined #openstack-meeting21:55
jeblairwhat ttx _meant_ was open discussion about the world cup ;)21:55
*** caleb_ has quit IRC21:55
ttxjeez, what a beating21:56
SlickNikThanks ttx!21:56
devanandajogo, sdague: will you be at oscon?21:56
sdaguedevananda: no21:56
*** dims_ has quit IRC21:56
jogodevananda: no, got enough traveling in the near future21:56
devanandahm, k. i feel like this is worth talking in high bandwidth about at some point before paris21:57
devanandajust not today :)21:57
devanandanova sprint?21:57
*** changbl has quit IRC21:58
jogodevananda: nova or germany  yeah21:58
clarkbI will be there ish21:58
jogosdague: what is your concern with https://review.openstack.org/#/c/100033/ ?21:58
*** denis_makogon has quit IRC21:58
jogoif neutron is running full tempest21:59
sdaguejogo: because it's different22:00
*** fnaval has quit IRC22:00
sdaguethere is a whole different network allocation set of paths in there22:01
sdaguecompletely different databases22:01
sdagueneutron is even talking about using a different mysql driver22:01
Daisyis this infrastructure meeting?22:01
clarkbDaisy: no we had our meeting 3 hours ago22:02
clarkbDaisy: but we are still hanging out in the infra channel if you want to chat22:02
*** Mandell has quit IRC22:02
*** ominakov has quit IRC22:02
Daisyok. I make mistake.22:02
DaisyThanks, clarkb22:02
*** Mandell has joined #openstack-meeting22:03
jogosdague: so that patch would drop neutron+mysql from the integrated gate, but it will still be tested in neutron. So is the concern here that we are sacrificing mysql coverage for postgres coverage? and we end up with sub-optimal coverge for both instead mysql and postgres?22:03
*** jcoufal has quit IRC22:03
Daisyclarkb: Just want to understand the translation platform discussion, I may contact with Elizabeth.22:03
jogoand you would rather see better mysql coverge and sacrifice postgres?22:03
*** pballand has joined #openstack-meeting22:04
sdaguejogo: yep22:04
Daisyjoin #openstack-infra22:04
sdaguejogo: because it's less different configs22:04
sdaguewhich I actually think means handling the race cases are easier22:04
jogosdague: yeah I buy that argument22:04
clarkband you can still test the nitty gritty postgres bits outside of tempest22:04
clarkbthat fact was really missed on the thread22:04
*** eglynn has quit IRC22:05
jogoclarkb: how can we do that?22:05
clarkbjogo: we already do it22:05
clarkbdatabase migrations are tested against myslq, postgres and sqlite22:05
jogoclarkb: oh right unit tests22:05
sdaguejogo: just stand up postgresql and run the db tests against it22:05
*** ivasev_ has quit IRC22:06
sdagueyeh, people are expecting too many magic bullets out of the tempest jobs22:06
jogoso now we just need to convince folks that we should drop all the postgres jobs22:06
sdagueit catches a ton of stuff22:06
*** fnaval has joined #openstack-meeting22:06
sdaguebut it can only reach so far into the workings, because it's black box22:06
sdagueso for white/grey box stuff closer to the projects is much better22:06
*** IlyaE has joined #openstack-meeting22:06
jogosdague: yeah I like that breakdown a lot22:07
*** jlibosva1 has quit IRC22:07
*** ivasev has joined #openstack-meeting22:07
*** sweston has quit IRC22:07
*** sweston_ has quit IRC22:07
*** ivasev has quit IRC22:08
*** Mandell has quit IRC22:09
*** ArxCruz has quit IRC22:11
*** Mandell has joined #openstack-meeting22:11
*** ArxCruz has joined #openstack-meeting22:11
*** xianghui has quit IRC22:12
*** jlibosva has joined #openstack-meeting22:15
*** garyduan has quit IRC22:15
*** marun has quit IRC22:16
*** andreaf has quit IRC22:18
*** shakamunyi has quit IRC22:20
*** shakamunyi has joined #openstack-meeting22:20
*** shakamunyi has quit IRC22:21
*** sarob has joined #openstack-meeting22:23
*** ArxCruz has quit IRC22:24
*** armax has quit IRC22:24
*** derekh_ has joined #openstack-meeting22:24
*** sarob_ has joined #openstack-meeting22:25
*** jlibosva has quit IRC22:26
*** rkukura has quit IRC22:26
*** atiwari has quit IRC22:27
*** Mandell has quit IRC22:28
*** sarob has quit IRC22:28
*** Mandell has joined #openstack-meeting22:28
*** shakamunyi has joined #openstack-meeting22:28
*** shakamunyi has quit IRC22:28
*** yamamoto has joined #openstack-meeting22:29
*** shakamunyi has joined #openstack-meeting22:29
*** zdiN0bot has joined #openstack-meeting22:30
*** atiwari has joined #openstack-meeting22:30
*** IlyaE has quit IRC22:32
*** IlyaE has joined #openstack-meeting22:32
*** jgrimm has quit IRC22:33
*** yamamoto has quit IRC22:33
*** thedodd has quit IRC22:36
*** sarob_ is now known as sarob22:36
*** Mandell has quit IRC22:38
*** asettle has joined #openstack-meeting22:40
*** Leon has joined #openstack-meeting22:44
*** Leon is now known as Guest7276922:44
*** dwalleck has joined #openstack-meeting22:44
*** dwalleck has quit IRC22:45
*** dwalleck has joined #openstack-meeting22:45
*** overlayer has quit IRC22:46
*** Mandell has joined #openstack-meeting22:47
*** JRobinson__ has joined #openstack-meeting22:47
*** Leonr has quit IRC22:47
*** Penick has joined #openstack-meeting22:55
*** Penick_ has joined #openstack-meeting22:56
*** bauzas has quit IRC22:58
*** Penick has quit IRC22:59
*** Penick_ is now known as Penick22:59
*** marcoemorais has quit IRC23:00
*** paulmo_ has left #openstack-meeting23:00
*** fnaval has quit IRC23:01
*** sweston has joined #openstack-meeting23:02
*** sweston_ has joined #openstack-meeting23:02
*** blamar_ has joined #openstack-meeting23:02
*** blamar has quit IRC23:04
*** blamar_ is now known as blamar23:04
*** marcoemorais has joined #openstack-meeting23:04
*** emagana has joined #openstack-meeting23:04
*** dwalleck has quit IRC23:06
*** VijayB_ has joined #openstack-meeting23:06
*** ttrifonov is now known as ttrifonov_zZzz23:08
*** VijayB has quit IRC23:09
*** Daisy has quit IRC23:10
*** shakamunyi has quit IRC23:10
*** sweston has quit IRC23:12
*** sweston_ has quit IRC23:12
*** trey_h has quit IRC23:13
*** hemna has quit IRC23:14
*** mattgriffin has quit IRC23:14
*** armax has joined #openstack-meeting23:14
*** zdiN0bot has quit IRC23:15
*** VijayB_ has quit IRC23:16
*** nelsnelson has quit IRC23:16
*** VijayB has joined #openstack-meeting23:16
*** fnaval has joined #openstack-meeting23:18
*** david-lyle has quit IRC23:19
*** cdub has joined #openstack-meeting23:20
*** kebray has quit IRC23:21
*** marcoemorais has quit IRC23:21
*** blogan is now known as zz_blogan23:22
*** bdpayne has quit IRC23:24
*** Guest72769 has quit IRC23:24
*** Leonr has joined #openstack-meeting23:25
*** IlyaE has quit IRC23:25
*** bdpayne has joined #openstack-meeting23:26
*** jmontemayor has quit IRC23:27
*** reed has quit IRC23:27
*** rkukura has joined #openstack-meeting23:27
*** reed_ has joined #openstack-meeting23:27
*** IlyaE has joined #openstack-meeting23:27
*** mwagner_lap has quit IRC23:28
*** xuhanp has joined #openstack-meeting23:28
*** reed_ is now known as reed23:28
*** reed has quit IRC23:29
*** reed has joined #openstack-meeting23:29
*** yamamoto has joined #openstack-meeting23:29
*** atiwari has quit IRC23:29
*** leonchio_ has quit IRC23:30
*** leonchio_ has joined #openstack-meeting23:31
*** amalagon has joined #openstack-meeting23:31
*** amalagon_ has quit IRC23:33
*** yamamoto has quit IRC23:33
*** MarkAtwood has quit IRC23:34
*** Sukhdev has quit IRC23:35
*** alexpilotti has quit IRC23:35
*** jamiem has quit IRC23:36
*** bdpayne has quit IRC23:37
*** derekh_ has quit IRC23:41
*** chuckC has quit IRC23:44
*** chuckC has joined #openstack-meeting23:45
*** IlyaE has quit IRC23:48
*** IlyaE has joined #openstack-meeting23:51
*** Sukhdev has joined #openstack-meeting23:51
*** vivek-ebay has quit IRC23:54
*** jackib has quit IRC23:59

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