Wednesday, 2014-11-26

*** banix has quit IRC00:00
*** Guest8043 has quit IRC00:02
*** rwsu has joined #openstack-meeting00:02
*** carl_baldwin has quit IRC00:04
*** shashankhegde has joined #openstack-meeting00:04
*** MIDENN_ has quit IRC00:04
*** dboik_ has quit IRC00:04
*** nealph has quit IRC00:05
*** Mandell has joined #openstack-meeting00:07
*** Mandell has quit IRC00:07
*** achanda has quit IRC00:08
*** daneyon_ has quit IRC00:09
*** padkrish has quit IRC00:10
*** henrynash has quit IRC00:10
*** Mandell has joined #openstack-meeting00:11
*** henrynash has joined #openstack-meeting00:12
*** natarajk has joined #openstack-meeting00:13
*** padkrish has joined #openstack-meeting00:14
*** eglynn has quit IRC00:14
*** emagana has joined #openstack-meeting00:16
*** IanGovett has quit IRC00:17
*** js1123 has quit IRC00:17
*** ChuckC_ has quit IRC00:18
*** SridharRamaswamy has quit IRC00:19
*** jorge_munoz has left #openstack-meeting00:19
*** Sukhdev has joined #openstack-meeting00:20
*** emagana has quit IRC00:23
*** HACKING-FACEBOOK has quit IRC00:23
*** emagana has joined #openstack-meeting00:23
*** ChuckC_ has joined #openstack-meeting00:25
*** achanda has joined #openstack-meeting00:26
*** emagana has quit IRC00:28
*** dims_ has quit IRC00:30
*** HACKING-FACEBOOK has joined #openstack-meeting00:32
*** Riddhi_ has joined #openstack-meeting00:32
*** emagana has joined #openstack-meeting00:35
*** emagana has quit IRC00:35
*** Mandell has quit IRC00:35
*** emagana has joined #openstack-meeting00:35
*** Riddhi has quit IRC00:35
*** adahms_ has joined #openstack-meeting00:37
*** achanda has quit IRC00:37
*** padkrish has quit IRC00:37
*** paragan has joined #openstack-meeting00:38
*** adahms has quit IRC00:39
*** julim has joined #openstack-meeting00:40
*** SridharRamaswamy has joined #openstack-meeting00:40
*** adahms_ is now known as adahms00:40
*** HACKING-FACEBOOK has quit IRC00:42
*** khaldrogox has quit IRC00:42
*** colinmcnamara has quit IRC00:42
*** yamamoto has joined #openstack-meeting00:44
*** adahms has quit IRC00:45
*** dsetia has quit IRC00:47
*** alexpilotti has quit IRC00:51
*** david-lyle is now known as david-lyle_afk00:51
*** colinmcnamara has joined #openstack-meeting00:52
*** yingjun has joined #openstack-meeting00:53
*** NobodyCam has quit IRC00:56
*** jjmb has joined #openstack-meeting00:56
*** baoli has joined #openstack-meeting00:56
*** achanda has joined #openstack-meeting00:57
*** emagana has quit IRC00:57
*** NobodyCam has joined #openstack-meeting00:58
*** adahms has joined #openstack-meeting00:58
*** juice has quit IRC00:58
*** shashankhegde has quit IRC00:58
*** emagana has joined #openstack-meeting00:58
*** balajiiyer has joined #openstack-meeting01:00
*** rmoe has quit IRC01:00
*** yamahata has joined #openstack-meeting01:01
*** juice has joined #openstack-meeting01:01
*** daneyon has joined #openstack-meeting01:02
*** ignacio-scopetta has quit IRC01:02
*** emagana has quit IRC01:02
*** zaneb has quit IRC01:03
*** hemna__ has quit IRC01:03
*** adahms has quit IRC01:03
*** stevemar has quit IRC01:05
*** matiu__ has joined #openstack-meeting01:06
*** gokrokve has quit IRC01:06
*** shashankhegde has joined #openstack-meeting01:06
*** hashar has quit IRC01:07
*** salv-orlando has quit IRC01:07
*** yamamoto has quit IRC01:08
*** amotoki has joined #openstack-meeting01:10
*** shashankhegde has quit IRC01:10
*** balajiiyer has quit IRC01:12
*** epico has joined #openstack-meeting01:12
*** adahms has joined #openstack-meeting01:16
*** rmoe has joined #openstack-meeting01:17
*** panbalag has joined #openstack-meeting01:18
*** Mandell has joined #openstack-meeting01:18
*** baoli has quit IRC01:19
*** mchalla has quit IRC01:19
*** leeantho has quit IRC01:20
*** tsekiyam_ has joined #openstack-meeting01:21
*** achanda has quit IRC01:22
*** tsekiyama has quit IRC01:23
*** tsekiyam_ has quit IRC01:25
*** mtanino has quit IRC01:27
*** paragan has quit IRC01:27
*** dimsum__ has joined #openstack-meeting01:30
*** baoli has joined #openstack-meeting01:30
*** achanda has joined #openstack-meeting01:31
*** MaxV_ has quit IRC01:31
*** scotm has joined #openstack-meeting01:33
*** otter768 has joined #openstack-meeting01:34
*** achanda has quit IRC01:35
*** dimsum__ has quit IRC01:36
*** dimsum__ has joined #openstack-meeting01:37
*** scotm has quit IRC01:38
*** otter768 has quit IRC01:38
*** dimsum__ has quit IRC01:41
*** haomaiwang has quit IRC01:43
*** scotm has joined #openstack-meeting01:46
*** scotm has quit IRC01:47
*** padkrish has joined #openstack-meeting01:47
*** shashankhegde has joined #openstack-meeting01:48
*** dane_leblanc has quit IRC01:49
*** mchalla has joined #openstack-meeting01:51
*** adahms has quit IRC01:51
*** xuhanp has joined #openstack-meeting01:51
*** wuhg has joined #openstack-meeting01:52
*** dimsum__ has joined #openstack-meeting01:53
*** marun has quit IRC01:55
*** mudassirlatif has quit IRC01:55
*** mchalla has quit IRC01:56
*** rwsu has quit IRC01:58
*** ignacio-scopetta has joined #openstack-meeting02:00
*** haomaiwang has joined #openstack-meeting02:01
*** ayoung-dad-mode is now known as ayoung02:01
*** oanufriev has quit IRC02:02
*** ebalduf has joined #openstack-meeting02:02
*** adahms has joined #openstack-meeting02:03
*** lhcheng has quit IRC02:04
*** emagana has joined #openstack-meeting02:06
*** emagana_ has joined #openstack-meeting02:07
*** yaguang has joined #openstack-meeting02:08
*** jjmb has quit IRC02:08
*** balajiiyer has joined #openstack-meeting02:08
*** mberlin has joined #openstack-meeting02:08
*** yaguang_ has joined #openstack-meeting02:09
*** kaisers1 has joined #openstack-meeting02:09
*** kaisers has quit IRC02:10
*** emagana has quit IRC02:10
*** mberlin1 has quit IRC02:10
*** Ark has joined #openstack-meeting02:11
*** Ark is now known as Guest3413802:12
*** yaguang has quit IRC02:12
*** Riddhi_ has quit IRC02:14
*** nosnos has joined #openstack-meeting02:14
*** colinmcnamara has quit IRC02:15
*** suro_ has quit IRC02:17
*** banix has joined #openstack-meeting02:18
*** Sukhdev has quit IRC02:20
*** colinmcnamara has joined #openstack-meeting02:20
*** Sukhdev has joined #openstack-meeting02:21
*** yamamoto has joined #openstack-meeting02:22
*** asettle is now known as asettle-optometr02:25
*** asettle-optometr is now known as asettle-glasses02:25
*** NobodyCam has quit IRC02:26
*** NobodyCam has joined #openstack-meeting02:27
*** MarkAtwood has quit IRC02:28
*** sdake_ has joined #openstack-meeting02:31
*** sdake_ has quit IRC02:31
*** sdake_ has joined #openstack-meeting02:31
*** MaxV has joined #openstack-meeting02:32
*** vipul has quit IRC02:33
*** padkrish has quit IRC02:35
*** Mandell has quit IRC02:37
*** MaxV has quit IRC02:37
*** vipul has joined #openstack-meeting02:37
*** MarkAtwood has joined #openstack-meeting02:38
*** SridharRamaswamy has quit IRC02:39
*** marrusl_ has joined #openstack-meeting02:39
*** shashankhegde has quit IRC02:49
*** natarajk has left #openstack-meeting02:49
*** gokrokve has joined #openstack-meeting02:52
*** gokrokve has quit IRC02:52
*** dimsum__ has quit IRC02:52
*** gokrokve has joined #openstack-meeting02:52
*** aleksandr_null has quit IRC02:52
*** scotm has joined #openstack-meeting02:53
*** gokrokve has quit IRC02:53
*** gokrokve has joined #openstack-meeting02:53
*** banix has quit IRC02:54
*** gokrokve has quit IRC02:54
*** gokrokve has joined #openstack-meeting02:55
*** sbalukoff has quit IRC02:57
*** gokrokve has quit IRC02:59
*** gokrokve has joined #openstack-meeting02:59
*** gokrokve has quit IRC02:59
*** MarkAtwood has quit IRC02:59
*** gokrokve has joined #openstack-meeting02:59
*** gokrokve has quit IRC03:00
*** gokrokve has joined #openstack-meeting03:00
*** nosnos has quit IRC03:01
*** fifieldt has joined #openstack-meeting03:01
*** Sukhdev has quit IRC03:01
*** padkrish has joined #openstack-meeting03:04
*** gokrokve has quit IRC03:05
*** gokrokve has joined #openstack-meeting03:05
*** banix has joined #openstack-meeting03:06
*** gokrokve has quit IRC03:06
*** gokrokve has joined #openstack-meeting03:07
*** gokrokve has quit IRC03:07
*** fnaval has quit IRC03:07
*** gokrokve has joined #openstack-meeting03:08
*** aleksandr_null has joined #openstack-meeting03:08
*** gokrokve has quit IRC03:08
*** vkmc has quit IRC03:12
*** gokrokve has joined #openstack-meeting03:12
*** nati_uen_ has joined #openstack-meeting03:15
*** novas0x2a|laptop has quit IRC03:16
*** gokrokve has quit IRC03:17
*** paragan has joined #openstack-meeting03:18
*** paragan has joined #openstack-meeting03:18
*** nati_ueno has quit IRC03:19
*** shwetaap has joined #openstack-meeting03:21
*** killer_prince has quit IRC03:23
*** fnaval has joined #openstack-meeting03:23
*** fnaval has quit IRC03:23
*** padkrish has quit IRC03:25
*** ptoohill_ has joined #openstack-meeting03:27
*** jjmb has joined #openstack-meeting03:27
*** padkrish has joined #openstack-meeting03:27
*** ptoohill_ has quit IRC03:28
*** ptoohill_ has joined #openstack-meeting03:28
*** harlowja is now known as harlowja_away03:29
*** adahms has quit IRC03:33
*** Leonr has joined #openstack-meeting03:34
*** otter768 has joined #openstack-meeting03:35
*** otter768 has quit IRC03:40
*** sarob has joined #openstack-meeting03:45
*** amcrn has quit IRC03:47
*** emagana_ has quit IRC03:48
*** padkrish has quit IRC03:48
*** emagana has joined #openstack-meeting03:48
*** emagana has quit IRC03:49
*** sarob has quit IRC03:49
*** emagana has joined #openstack-meeting03:50
*** adahms has joined #openstack-meeting03:50
*** mchalla has joined #openstack-meeting03:52
*** dimsum__ has joined #openstack-meeting03:52
*** noslzzp has quit IRC03:53
*** ivar-lazzaro has quit IRC03:53
*** noslzzp has joined #openstack-meeting03:56
*** mchalla has quit IRC03:56
*** dimsum__ has quit IRC03:57
*** noslzzp has quit IRC03:58
*** balajiiyer has quit IRC04:00
*** colinmcnamara has quit IRC04:01
*** jjmb has quit IRC04:03
*** Mandell has joined #openstack-meeting04:05
*** panbalag has quit IRC04:08
*** yingjun has quit IRC04:09
*** achanda has joined #openstack-meeting04:12
*** scotm has quit IRC04:13
*** zhhuabj_ has joined #openstack-meeting04:16
*** nosnos has joined #openstack-meeting04:16
*** JRobinson__ is now known as JRobinson__afk04:17
*** killer_prince has joined #openstack-meeting04:18
*** killer_prince is now known as lazy_prince04:18
*** zhhuabj_ has quit IRC04:18
*** zhhuabj has joined #openstack-meeting04:18
*** MaxV has joined #openstack-meeting04:22
*** panbalag has joined #openstack-meeting04:22
*** panbalag has quit IRC04:22
*** panbalag has joined #openstack-meeting04:22
*** panbalag has quit IRC04:23
*** panbalag has joined #openstack-meeting04:25
*** MaxV has quit IRC04:25
*** Sukhdev has joined #openstack-meeting04:26
*** AlexF has joined #openstack-meeting04:26
*** adahms has quit IRC04:27
*** emagana has quit IRC04:28
*** jjmb has joined #openstack-meeting04:30
*** achanda has quit IRC04:30
*** banix has quit IRC04:34
*** weshay has quit IRC04:37
*** Leonr has quit IRC04:38
*** ignacio-scopetta has quit IRC04:38
*** ignacio-scopetta has joined #openstack-meeting04:38
*** adahms has joined #openstack-meeting04:40
*** ignacio-scopetta has quit IRC04:43
*** jjmb has quit IRC04:43
*** padkrish has joined #openstack-meeting04:45
*** scotm has joined #openstack-meeting04:47
*** shashankhegde has joined #openstack-meeting04:49
*** scotm has quit IRC04:49
*** matiu__ is now known as matiu04:50
*** matiu is now known as Guest2139304:51
*** anish_ has joined #openstack-meeting04:54
*** kebray has quit IRC04:56
*** suro_ has joined #openstack-meeting04:56
*** henrynash_ has joined #openstack-meeting04:57
*** henrynash has quit IRC04:57
*** henrynash_ is now known as henrynash04:57
*** ayoung is now known as ayoung_ZZzz_zzZZ04:59
*** panbalag has quit IRC05:00
*** ptoohill_ has quit IRC05:00
*** adahms has quit IRC05:02
*** nellysmitt has joined #openstack-meeting05:03
*** AlexF has quit IRC05:04
*** nellysmitt has quit IRC05:08
*** garyh has quit IRC05:09
*** rushiagr_away is now known as rushiagr05:10
*** kopparam has joined #openstack-meeting05:11
*** stevemar has joined #openstack-meeting05:13
*** kopparam has quit IRC05:17
*** kopparam has joined #openstack-meeting05:17
*** haomaiwang has quit IRC05:18
*** adahms has joined #openstack-meeting05:18
*** haomaiwang has joined #openstack-meeting05:18
*** asettle-glasses is now known as asettle05:20
*** arnaud___ has quit IRC05:21
*** AlexF has joined #openstack-meeting05:21
*** JRobinson__afk has quit IRC05:21
*** JRobinson__afk has joined #openstack-meeting05:23
*** JRobinson__afk is now known as JRobinson__05:23
*** rakesh_hs has joined #openstack-meeting05:27
*** padkrish has quit IRC05:27
*** emagana has joined #openstack-meeting05:29
*** BharatK has joined #openstack-meeting05:30
*** ptoohill_ has joined #openstack-meeting05:30
*** ptoohill_ has quit IRC05:31
*** haomaiw__ has joined #openstack-meeting05:31
*** suro_ has quit IRC05:31
*** ItSANgo has quit IRC05:31
*** ebalduf has quit IRC05:32
*** haomaiwang has quit IRC05:34
*** padkrish has joined #openstack-meeting05:34
*** otter768 has joined #openstack-meeting05:36
*** SridharG has joined #openstack-meeting05:36
*** stevemar has quit IRC05:36
*** chandankumar has joined #openstack-meeting05:37
*** ptoohill_ has joined #openstack-meeting05:37
*** Longgeek has joined #openstack-meeting05:38
*** ujuc has joined #openstack-meeting05:39
*** neeti has joined #openstack-meeting05:39
*** otter768 has quit IRC05:40
*** garyh has joined #openstack-meeting05:41
*** SridharG has quit IRC05:43
*** Longgeek has quit IRC05:44
*** Guest34138 has quit IRC05:47
*** simon-AS559 has joined #openstack-meeting05:48
*** lpeer has quit IRC05:49
*** simon-AS5591 has joined #openstack-meeting05:50
*** gokrokve has joined #openstack-meeting05:50
*** henrynash has quit IRC05:51
*** gokrokve has quit IRC05:52
*** simon-AS559 has quit IRC05:53
*** ItSANgo has joined #openstack-meeting05:53
*** mchalla has joined #openstack-meeting05:54
*** ptoohill_ has quit IRC05:57
*** mchalla has quit IRC05:58
*** rushiagr is now known as rushiagr_away05:59
*** simon-AS5591 has quit IRC05:59
*** stevemar has joined #openstack-meeting06:01
*** Guest21393 is now known as matiu06:02
*** matiu is now known as Guest4334206:02
*** SridharG has joined #openstack-meeting06:03
*** k4n0 has joined #openstack-meeting06:03
*** Guest43342 has quit IRC06:08
*** Guest43342 has joined #openstack-meeting06:08
*** ppai has joined #openstack-meeting06:10
*** padkrish has quit IRC06:12
*** lpeer has joined #openstack-meeting06:13
*** Ark has joined #openstack-meeting06:17
*** Ark is now known as Guest541606:18
*** Masahiro has joined #openstack-meeting06:19
*** Mandell has quit IRC06:19
*** prydeep has joined #openstack-meeting06:20
*** Sukhdev has quit IRC06:22
*** Longgeek has joined #openstack-meeting06:22
*** mrmartin has joined #openstack-meeting06:23
*** mudassirlatif has joined #openstack-meeting06:23
*** Guest5416 has quit IRC06:26
*** Masahiro has quit IRC06:26
*** nati_uen_ has quit IRC06:26
*** nati_ueno has joined #openstack-meeting06:27
*** SridharG has left #openstack-meeting06:27
*** Masahiro has joined #openstack-meeting06:27
*** rajeshr has joined #openstack-meeting06:27
*** lpeer_ has joined #openstack-meeting06:28
*** Masahiro has quit IRC06:29
*** Masahiro has joined #openstack-meeting06:29
*** lpeer has quit IRC06:30
*** arnaud___ has joined #openstack-meeting06:30
*** ebalduf has joined #openstack-meeting06:33
*** stevemar has quit IRC06:34
*** suro_ has joined #openstack-meeting06:35
*** mrda is now known as mrda-away06:37
*** SumitNaiksatam has quit IRC06:38
*** ebalduf has quit IRC06:38
*** SumitNaiksatam has joined #openstack-meeting06:39
*** emagana has quit IRC06:43
*** emagana has joined #openstack-meeting06:43
*** adahms has quit IRC06:44
*** nshaikh has joined #openstack-meeting06:44
*** emagana has quit IRC06:48
*** ppai has quit IRC06:48
*** doron_afk has joined #openstack-meeting06:49
*** afazekas has joined #openstack-meeting06:50
*** garyk has joined #openstack-meeting06:56
*** mchalla has joined #openstack-meeting06:56
*** ppai has joined #openstack-meeting07:00
*** Shohei has quit IRC07:00
*** Shohei has joined #openstack-meeting07:00
*** mchalla has quit IRC07:01
*** SridharG has joined #openstack-meeting07:02
*** jprovazn has joined #openstack-meeting07:02
*** Masahiro has quit IRC07:02
*** aepifanov has joined #openstack-meeting07:03
*** Masahiro has joined #openstack-meeting07:03
*** Shohei has quit IRC07:03
*** mrunge has joined #openstack-meeting07:04
*** shankarprasad has joined #openstack-meeting07:04
*** nellysmitt has joined #openstack-meeting07:04
*** Masahiro has quit IRC07:05
*** suro_ has quit IRC07:05
*** ppai has left #openstack-meeting07:06
*** rushiagr_away is now known as rushiagr07:07
*** ajo has joined #openstack-meeting07:08
*** suro_ has joined #openstack-meeting07:08
*** nellysmitt has quit IRC07:09
*** mchalla has joined #openstack-meeting07:12
*** suro_ has quit IRC07:14
*** fifieldt has quit IRC07:16
*** Guest43342 is now known as matiu07:17
*** mchalla has quit IRC07:17
*** matiu is now known as Guest1580607:17
*** suro_ has joined #openstack-meeting07:17
*** kopparam has quit IRC07:19
*** suro_1 has joined #openstack-meeting07:19
*** suro_ has quit IRC07:22
*** henrynash has joined #openstack-meeting07:22
*** Mandell has joined #openstack-meeting07:24
*** suro_1 has quit IRC07:24
*** Masahiro has joined #openstack-meeting07:25
*** ItSANgo has quit IRC07:26
*** eglynn has joined #openstack-meeting07:26
*** simon-AS559 has joined #openstack-meeting07:28
*** ujuc has quit IRC07:30
*** colinmcnamara has joined #openstack-meeting07:31
*** achanda has joined #openstack-meeting07:31
*** JRobinson__ has quit IRC07:33
*** mchalla has joined #openstack-meeting07:36
*** achanda has quit IRC07:36
*** Masahiro has quit IRC07:36
*** otter768 has joined #openstack-meeting07:36
*** e0ne has joined #openstack-meeting07:38
*** penick has joined #openstack-meeting07:38
*** e0ne has quit IRC07:38
*** ildikov has joined #openstack-meeting07:39
*** otter768 has quit IRC07:41
*** mchalla has quit IRC07:41
*** evgenyf has joined #openstack-meeting07:43
*** alex_xu has joined #openstack-meeting07:44
*** henrynash has quit IRC07:46
*** SumitNaiksatam has quit IRC07:46
*** eglynn has quit IRC07:46
*** yingjun has joined #openstack-meeting07:46
*** AlexF has quit IRC07:47
*** SumitNaiksatam has joined #openstack-meeting07:49
*** jaypipes has quit IRC07:50
*** mitz- has joined #openstack-meeting07:51
*** mitz_ has quit IRC07:51
*** AlexF has joined #openstack-meeting07:54
*** colinmcnamara has quit IRC07:54
*** armax has quit IRC07:55
*** colinmcnamara has joined #openstack-meeting07:56
*** kopparam has joined #openstack-meeting07:57
*** nellysmitt has joined #openstack-meeting07:57
*** xuhanp has quit IRC08:01
*** salv-orlando has joined #openstack-meeting08:02
*** erikmoe has joined #openstack-meeting08:03
*** jtomasek has joined #openstack-meeting08:04
*** doron_afk is now known as doron_08:05
*** sergef has joined #openstack-meeting08:06
*** ildikov has quit IRC08:07
*** sergef_ has joined #openstack-meeting08:09
*** Shohei has joined #openstack-meeting08:11
*** sergef has quit IRC08:11
*** sergef_ is now known as sergef08:11
*** xuhanp has joined #openstack-meeting08:14
*** penick has quit IRC08:14
*** oomichi has quit IRC08:17
*** matrohon has joined #openstack-meeting08:17
*** zz_ttrifonov is now known as ttrifonov08:17
*** mudassirlatif has quit IRC08:17
*** yamahata has quit IRC08:18
*** Masahiro has joined #openstack-meeting08:18
*** ttrifonov is now known as zz_ttrifonov08:19
*** eglynn has joined #openstack-meeting08:19
*** lpeer_ is now known as lpeer08:20
*** oanufriev has joined #openstack-meeting08:20
*** lpeer_ has joined #openstack-meeting08:20
*** zz_ttrifonov is now known as ttrifonov08:20
*** ildikov has joined #openstack-meeting08:22
*** lpeer has quit IRC08:24
*** kopparam has quit IRC08:25
*** colinmcnamara has quit IRC08:26
*** SridharG1 has joined #openstack-meeting08:26
*** nadya has joined #openstack-meeting08:26
*** nadya is now known as Guest2838108:27
*** kopparam has joined #openstack-meeting08:28
*** SridharG has quit IRC08:29
*** jcoufal has joined #openstack-meeting08:29
*** achanda has joined #openstack-meeting08:33
*** matrohon has quit IRC08:33
*** mitz_ has joined #openstack-meeting08:34
*** andreykurilin_ has joined #openstack-meeting08:35
*** epico has quit IRC08:36
*** mitz- has quit IRC08:36
*** mchalla has joined #openstack-meeting08:38
*** MaxV has joined #openstack-meeting08:40
*** epico has joined #openstack-meeting08:41
*** yingjun has quit IRC08:41
*** mchalla has quit IRC08:42
*** bvandenh has joined #openstack-meeting08:43
*** jlanoux has joined #openstack-meeting08:44
*** AlexF has quit IRC08:45
*** shashankhegde has quit IRC08:47
*** achanda has quit IRC08:48
*** SumitNaiksatam has quit IRC08:51
*** SumitNaiksatam has joined #openstack-meeting08:52
*** ygbo has joined #openstack-meeting08:52
*** matrohon has joined #openstack-meeting08:53
*** safchain has joined #openstack-meeting08:54
*** erikmoe has quit IRC08:56
*** zz_avozza has quit IRC08:56
*** SumitNaiksatam has quit IRC08:56
*** zz_avozza has joined #openstack-meeting08:57
*** zz_avozza is now known as avozza08:57
*** berendt has joined #openstack-meeting08:57
*** andreykurilin_ has quit IRC08:58
*** andreykurilin_ has joined #openstack-meeting08:59
*** mpaolino has joined #openstack-meeting08:59
*** Fdot has joined #openstack-meeting08:59
*** SumitNaiksatam has joined #openstack-meeting09:00
*** jprovazn has quit IRC09:01
*** SridharG1 has quit IRC09:01
*** SridharG has joined #openstack-meeting09:02
*** doron_ is now known as doron_afk09:04
*** yingjun has joined #openstack-meeting09:08
*** yingjun has quit IRC09:08
*** amotoki has quit IRC09:11
*** doron_afk is now known as doron_09:12
*** derekh has joined #openstack-meeting09:12
*** Masahiro has quit IRC09:13
*** jprovazn has joined #openstack-meeting09:15
*** e0ne has joined #openstack-meeting09:16
*** zhhuabj has quit IRC09:18
*** ZiGMaX has joined #openstack-meeting09:19
*** Mandell has quit IRC09:19
*** zhhuabj has joined #openstack-meeting09:20
*** vigneshvar has joined #openstack-meeting09:20
*** Masahiro has joined #openstack-meeting09:23
*** sergsh_away is now known as sergsh09:25
*** alex_xu has quit IRC09:26
*** yamamoto has quit IRC09:32
*** afazekas has quit IRC09:33
*** xuhanp has quit IRC09:34
*** garyk has quit IRC09:35
*** ebalduf has joined #openstack-meeting09:36
*** otter768 has joined #openstack-meeting09:37
*** Longgeek_ has joined #openstack-meeting09:38
*** Longgeek has quit IRC09:39
*** anish_ has quit IRC09:39
*** ebalduf has quit IRC09:40
*** otter768 has quit IRC09:42
*** darvon has quit IRC09:43
*** darvon has joined #openstack-meeting09:43
*** francois has quit IRC09:43
*** yamahata has joined #openstack-meeting09:45
*** garyk has joined #openstack-meeting09:46
*** xuhanp has joined #openstack-meeting09:46
*** Ark has joined #openstack-meeting09:47
*** Ark is now known as Guest5539509:48
*** afazekas has joined #openstack-meeting09:48
*** lazy_prince has quit IRC09:48
*** tochi has quit IRC09:49
*** anish_ has joined #openstack-meeting09:51
*** epico_ has joined #openstack-meeting09:51
*** epico has quit IRC09:51
*** andreykurilin_ has quit IRC09:52
*** Guest55395 has quit IRC09:53
*** ItSANgo has joined #openstack-meeting09:54
*** erikmoe has joined #openstack-meeting09:56
*** jcoufal_ has joined #openstack-meeting09:57
*** pkoniszewski has joined #openstack-meeting09:59
*** jcoufal has quit IRC10:00
*** epico_ has quit IRC10:03
*** afazekas has quit IRC10:07
*** prydeep has quit IRC10:08
*** subscope has quit IRC10:08
*** avozza is now known as zz_avozza10:13
*** kopparam has quit IRC10:14
*** zz_avozza is now known as avozza10:15
*** Guest28381 has quit IRC10:20
*** ndipanov_gone is now known as ndipanov10:20
*** afazekas has joined #openstack-meeting10:21
*** kopparam has joined #openstack-meeting10:25
*** Masahiro has quit IRC10:25
*** kopparam has quit IRC10:26
*** andreykurilin_ has joined #openstack-meeting10:27
*** kopparam has joined #openstack-meeting10:27
*** evgenyf has quit IRC10:28
*** erikmoe has quit IRC10:28
*** nadya_ has joined #openstack-meeting10:29
*** scheuran has joined #openstack-meeting10:31
*** ZiGMaX has quit IRC10:33
*** paragan has quit IRC10:33
*** KanagarajM has joined #openstack-meeting10:34
*** subscope has joined #openstack-meeting10:34
*** nadya_ has quit IRC10:38
*** mchalla has joined #openstack-meeting10:39
*** zz_johnthetubagu is now known as johnthetubaguy10:41
*** yamahata has quit IRC10:43
*** mchalla has quit IRC10:43
*** yamahata has joined #openstack-meeting10:45
*** arnaud___ has quit IRC10:48
*** kopparam has quit IRC10:51
*** killer_prince has joined #openstack-meeting10:56
*** killer_prince is now known as lazy_prince10:56
*** kopparam has joined #openstack-meeting10:56
*** adalbas has joined #openstack-meeting10:58
*** Guest15806 has quit IRC11:00
*** matiu has joined #openstack-meeting11:01
*** matiu has joined #openstack-meeting11:01
*** rfolco has joined #openstack-meeting11:01
*** nadya_ has joined #openstack-meeting11:04
*** ildikov has quit IRC11:05
*** rfolco has quit IRC11:05
*** shwetaap has quit IRC11:05
*** doron_ has quit IRC11:06
*** evgenyf has joined #openstack-meeting11:06
*** adahms has joined #openstack-meeting11:07
*** shwetaap has joined #openstack-meeting11:09
*** asalkeld has joined #openstack-meeting11:09
*** haomaiw__ has quit IRC11:10
*** doron_ has joined #openstack-meeting11:10
*** shwetaap has quit IRC11:11
*** yingjun has joined #openstack-meeting11:13
*** simon-AS5591 has joined #openstack-meeting11:13
*** simon-AS559 has quit IRC11:16
*** moha_hunt has joined #openstack-meeting11:22
*** Masahiro has joined #openstack-meeting11:26
*** haomaiwang has joined #openstack-meeting11:29
*** salv-orlando has quit IRC11:29
*** Masahiro has quit IRC11:30
*** aysyd has joined #openstack-meeting11:31
*** vkmc has joined #openstack-meeting11:34
*** js1123 has joined #openstack-meeting11:36
*** gholler has joined #openstack-meeting11:37
*** rajeshr has quit IRC11:37
*** alex_xu has joined #openstack-meeting11:38
*** otter768 has joined #openstack-meeting11:38
*** avozza has left #openstack-meeting11:41
*** xuhanp has quit IRC11:41
*** otter768 has quit IRC11:43
*** inc0 has joined #openstack-meeting11:58
shardy#startmeeting heat12:00
openstackMeeting started Wed Nov 26 12:00:08 2014 UTC and is due to finish in 60 minutes.  The chair is shardy. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: heat)"12:00
openstackThe meeting name has been set to 'heat'12:00
*** panbalag has joined #openstack-meeting12:00
shardy#topic rollcall12:00
*** openstack changes topic to "rollcall (Meeting topic: heat)"12:00
asalkeldo/12:00
shardyHi all, who's around?12:00
*** cmyster has joined #openstack-meeting12:00
skraynevhi guys12:00
*** dulek has joined #openstack-meeting12:01
* cmyster nods12:01
inc0\o\ /o/12:01
asalkeldmight be a short meeting :-O12:01
skraynevI suppose, that pas-ha should be here too..12:01
shardyHeh, yeah12:01
*** Qiming has joined #openstack-meeting12:02
*** neeti has quit IRC12:02
*** ananta has joined #openstack-meeting12:02
shardy#topic Review actions from last meeting12:02
*** openstack changes topic to "Review actions from last meeting (Meeting topic: heat)"12:02
shardy#link http://eavesdrop.openstack.org/meetings/heat/2014/heat.2014-11-19-20.00.html12:02
shardyACTION: asalkeld to send out an announcement about the bug cleanup day12:02
asalkelddone12:02
asalkeldand the other email too12:02
shardy#info asalkeld sent out an announcement about the bug cleanup day12:02
skraynev2 December :)12:02
shardy#info asalkeld announced remote mid-cycle plan12:03
asalkeldwe should start thinking about how to actually do that12:03
shardyYeah, I think that's it from last week?12:03
*** kopparam has quit IRC12:03
shardy#topic Adding items to the agenda12:03
*** openstack changes topic to "Adding items to the agenda (Meeting topic: heat)"12:03
shardy#link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282014-11-26_1200_UTC.2912:03
shardyAnyone have anything to add?12:03
shardyI added a quick recap of the liason-all-the-things status12:04
asalkeldadd an item about approaching k112:04
shardyasalkeld: Ok, good point12:04
asalkeldk1 is 2014-12-1812:04
shardy#infp Additional topic: discuss approaching k1 milestone12:04
shardy#info Additional topic: discuss approaching k1 milestone12:05
shardyShall we do that first?12:05
anantaIn the end I would also like to discuss about convergence PoC if possible12:05
asalkeldshardy, sure12:05
skraynevshardy: +112:05
asalkeldananta, we will have heaps of time12:05
anantaasalkeld: ok, sounds great12:06
shardy#info Add topic discuss about convergence PoC12:06
*** dulek has quit IRC12:06
shardyOk lets do K1 first12:06
shardy#topic K1 milestone12:06
*** openstack changes topic to "K1 milestone (Meeting topic: heat)"12:06
asalkeldhttps://launchpad.net/heat/+milestone/kilo-112:06
*** dulek has joined #openstack-meeting12:06
asalkeldthis is just a reminder that k1 is approaching12:06
shardy#link https://launchpad.net/heat/+milestone/kilo-112:07
asalkeldso don't plan on squeezing big things in12:07
shardyHow's the bug backlog looking?12:07
* shardy looks12:07
asalkeldgood I think12:07
shardyYeah, all the High stuff is in-progress or committed :)12:07
asalkeldwe should review those bugs/blueprints above others12:08
asalkeldthat's all really12:08
asalkeldjust a heads up12:08
skraynevonly one bug without owner12:08
shardyI really need to revisit the decouple-nested patches12:08
shardyAll the easy ones have merged now, so I need to tackle the remaining test nightmare12:08
asalkeldzane set that12:08
shardyWill try to get that sorted next week12:09
* shardy has been saying that for a few weeks...12:09
skraynevok12:09
*** kopparam has joined #openstack-meeting12:09
shardyEverything else looks good I think modulo some review iterations :)12:09
*** baoli has quit IRC12:10
asalkeldyip12:10
shardyOk, shall we move on?12:10
asalkeldyip, move on12:10
skraynevgo12:10
shardy#topic Cross Project Liasons revisited12:10
*** openstack changes topic to "Cross Project Liasons revisited (Meeting topic: heat)"12:10
shardy#link https://wiki.openstack.org/wiki/CrossProjectLiaisons12:10
shardySo the only gap is the VMT liason12:11
*** ildikov has joined #openstack-meeting12:11
*** garyk1 has joined #openstack-meeting12:11
shardyDespite saying it was pointless last week, I can do that if nobody else wantst to12:11
asalkeldand randall has a question mark12:11
shardyYeah, did anyone check if he's happy to do that?12:11
shardyI can take an action to if not12:11
asalkeldthat's a good action to email him12:12
asalkeldi can do that12:12
shardy#action shardy to check with randallburt re Docs liason12:12
*** padiyar has joined #openstack-meeting12:12
shardy#action asalkeld to check with randallburt re Docs liason12:12
asalkeldor you:-)12:12
*** rakesh_hs2 has joined #openstack-meeting12:12
asalkelddoh12:12
shardyEither works ;)12:12
skraynevthat is all?12:12
*** rakesh_hs has quit IRC12:12
asalkeldskraynev, all others have names now12:12
shardyyup, I think we have all others covered12:13
skraynevok12:13
*** raildo has quit IRC12:13
shardyOk, I guess we can move on - asalkeld, shall I undo that last action before changing topic?12:14
asalkeldi have just emailed him12:14
asalkeldso you can12:14
shardy#undo12:15
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x1b164d0>12:15
shardyOk, thanks12:15
* shardy can't type in more than one window at once ;D12:15
*** garyk has quit IRC12:15
shardy#topic Convergence PoC status12:16
*** openstack changes topic to "Convergence PoC status (Meeting topic: heat)"12:16
asalkeldananta,12:16
anantawe have the poc at12:16
anantahttps://github.com/anantpatil/heat-convergence-poc12:16
shardy#link https://github.com/anantpatil/heat-convergence-poc12:16
anantaI would like to see some feedback so that we can take it forward12:16
shardyananta: So you've been collaborating with zaneb and inc0 re the test framework?12:17
inc0we haven't really decided on approach...12:17
anantaour poc started much before zaneb's12:17
anantaso we have changes on top of the heat engine12:17
shardyinc0: What I'm getting at is, are we collaborating effectively, or all working on separate PoC efforts12:17
padiyarIt would be great if we can feedback on the poc which built on top of heat code itself12:17
shardyI get the impression it's the latter, so it would be good to start working out how we change that :)12:18
asalkeldagree12:18
shardyananta, padiyar: OK, well thanks for the update12:18
shardylet's revisit this next week when Zane is around12:18
asalkeldthe main thing here is to talk to each other about the ideas12:19
asalkeldbut padiyar ananta , i'll look at the poc12:19
anantaasalkeld: sure12:19
asalkeldi have been looking at inc0 and zane's efforts12:19
padiyarwe are putting lot of effort on this so that we can make some decision.. it would really help to get some feedback and work on it if it required changes12:20
asalkeldsure12:20
anantaas long as we can convey the ideas it would be great ...12:20
*** salv-orlando has joined #openstack-meeting12:20
*** rpothier has joined #openstack-meeting12:20
anantaI also seek feedback on the persist-graph BP12:21
anantahttps://review.openstack.org/#/c/123749/12:21
anantaour PoC is based on that and I gues that is the case with zaneb's poc12:22
shardypadiyar, ananta: Do you have any thoughts on how we can improve the collaboration between folks interested in defining this design?12:22
padiyarDo we need a separate meeting to discuss only convergence poc? proabably a hagnout session?12:22
anantashardy: yes12:22
inc0we have these... just after heat meetings12:23
asalkeldpadiyar, i'd really like you guys and zane and inc0 in a hangout working together discussing pros/cons12:23
asalkeldtrying to zero in on a solution12:23
padiyarsure we will do that12:23
anantashardy, asalkeld: we do think of collaborating, now that the poc has taken a concrete shape12:24
inc0next week just after heat meetings ananta?12:24
*** rpothier has quit IRC12:24
inc0its ok with you?12:24
anantainc0: cant tell right now12:24
*** bvandenh has quit IRC12:24
anantawill communicate later12:24
shardy#action Convergence folks to organise call/hangout to define direction re various PoC efforts12:24
shardyOk, I'll leave you guys to discuss timing with Zane next week12:25
asalkeldguys one thing (inc and ananta) don't cling too hard to *your* design12:25
padiyarlets get a sync up on this over email12:25
shardyAnything else before we wrap up?12:25
inc0sure, just my humble request, lets try to organise it in some managable time for Euro;)12:25
asalkeldtry focus on finding the best solution, not *my* solution12:25
padiyaryes :) for sure12:26
*** raildo has joined #openstack-meeting12:26
asalkeldthat's all from me12:26
shardyOk then, thanks all!12:26
padiyarthank you12:26
shardy#endmeeting12:27
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"12:27
openstackMeeting ended Wed Nov 26 12:27:01 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:27
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2014/heat.2014-11-26-12.00.html12:27
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2014/heat.2014-11-26-12.00.txt12:27
*** cmyster has left #openstack-meeting12:27
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2014/heat.2014-11-26-12.00.log.html12:27
*** inc0 has left #openstack-meeting12:27
anantathanks all12:27
*** jjmb has joined #openstack-meeting12:28
*** padiyar has quit IRC12:28
*** KanagarajM has quit IRC12:28
*** erikmoe has joined #openstack-meeting12:30
*** kopparam has quit IRC12:33
*** asalkeld has quit IRC12:34
*** rpothier has joined #openstack-meeting12:34
*** ananta has left #openstack-meeting12:34
*** bvandenh has joined #openstack-meeting12:38
*** rpothier has quit IRC12:39
*** mchalla has joined #openstack-meeting12:41
*** anish_ has quit IRC12:41
*** rpothier has joined #openstack-meeting12:42
*** ChrisPriceAB has joined #openstack-meeting12:44
*** mchalla has quit IRC12:45
*** rushiagr is now known as rushiagr_away12:46
*** jcoufal_ has quit IRC12:47
*** doron_ is now known as doron_afk12:48
*** jcoufal has joined #openstack-meeting12:48
*** rpothier has left #openstack-meeting12:51
*** nati_uen_ has joined #openstack-meeting12:52
*** zhhuabj has quit IRC12:54
*** baoli has joined #openstack-meeting12:54
*** nati_ueno has quit IRC12:55
*** BillArnold has joined #openstack-meeting12:57
*** xuhanp has joined #openstack-meeting12:57
*** banix has joined #openstack-meeting13:01
*** paragan has joined #openstack-meeting13:02
*** banix has quit IRC13:04
*** noslzzp has joined #openstack-meeting13:04
*** shankarprasad has quit IRC13:07
*** zaneb has joined #openstack-meeting13:08
*** IanGovett has joined #openstack-meeting13:09
*** Longgeek_ has quit IRC13:11
*** jjmb has quit IRC13:12
*** Masahiro has joined #openstack-meeting13:14
*** yaguang_ has quit IRC13:19
*** julim has quit IRC13:19
*** Masahiro has quit IRC13:19
*** nosnos has quit IRC13:20
*** Mandell has joined #openstack-meeting13:20
*** alexpilotti has joined #openstack-meeting13:21
*** bswartz has quit IRC13:22
*** jjmb has joined #openstack-meeting13:23
*** Mandell has quit IRC13:24
*** francois has joined #openstack-meeting13:27
*** erikmoe has quit IRC13:27
*** MeganR has joined #openstack-meeting13:27
*** BharatK has quit IRC13:29
*** vigneshvar_ has joined #openstack-meeting13:31
*** weshay has joined #openstack-meeting13:31
*** alexpilotti has quit IRC13:32
*** bvandenh has quit IRC13:32
*** erikmoe has joined #openstack-meeting13:33
*** safchain has quit IRC13:33
*** safchain has joined #openstack-meeting13:33
*** colinmcnamara has joined #openstack-meeting13:33
*** vigneshvar has quit IRC13:34
*** jaypipes has joined #openstack-meeting13:36
*** mestery has quit IRC13:36
*** ildikov has quit IRC13:36
*** Longgeek has joined #openstack-meeting13:37
*** baoli has quit IRC13:37
*** otter768 has joined #openstack-meeting13:39
*** berendt has quit IRC13:40
*** BharatK has joined #openstack-meeting13:41
*** rushiagr_away is now known as rushiagr13:42
*** yingjun has quit IRC13:43
*** rakesh_hs2 has quit IRC13:43
*** otter768 has quit IRC13:44
*** baoli has joined #openstack-meeting13:44
*** lpeer_ has quit IRC13:45
*** bvandenh has joined #openstack-meeting13:47
*** yingjun has joined #openstack-meeting13:48
*** ildikov has joined #openstack-meeting13:48
*** julim has joined #openstack-meeting13:49
*** shwetaap has joined #openstack-meeting13:50
*** shwetaap has quit IRC13:50
*** Fdot_ has joined #openstack-meeting13:50
*** aepifanov has quit IRC13:50
*** shwetaap has joined #openstack-meeting13:50
*** yamahata has quit IRC13:50
*** dave-mccowan has joined #openstack-meeting13:51
*** dimsum__ has joined #openstack-meeting13:51
*** erw has quit IRC13:51
*** marrusl_ has quit IRC13:51
*** yamahata has joined #openstack-meeting13:51
*** marrusl_ has joined #openstack-meeting13:51
*** marrusl_ has quit IRC13:51
*** marrusl has quit IRC13:51
*** marrusl has joined #openstack-meeting13:51
*** panbalag has quit IRC13:52
*** beagles has quit IRC13:52
*** erw has joined #openstack-meeting13:53
*** BharatK has quit IRC13:53
*** phil_ has joined #openstack-meeting13:53
*** Fdot has quit IRC13:53
*** nadya_ has quit IRC13:54
*** marrusl has quit IRC13:54
*** marrusl has joined #openstack-meeting13:54
*** che-arn8 has joined #openstack-meeting13:54
*** che-arne has joined #openstack-meeting13:54
*** che-arn8 has quit IRC13:54
*** vigneshvar_ has quit IRC13:55
*** s0mik has quit IRC13:55
*** s0mik has joined #openstack-meeting13:56
*** colinmcnamara has quit IRC13:57
*** panbalag has joined #openstack-meeting13:57
*** colinmcnamara has joined #openstack-meeting14:00
*** xuhanp has quit IRC14:01
*** chandankumar has quit IRC14:02
*** jjmb has quit IRC14:05
*** mestery has joined #openstack-meeting14:05
*** irenab has joined #openstack-meeting14:06
*** jehb_ has joined #openstack-meeting14:07
*** pkoniszewski has quit IRC14:08
*** beagles has joined #openstack-meeting14:09
*** beagles is now known as Guest589914:09
*** jpich has joined #openstack-meeting14:09
*** gholler_ has joined #openstack-meeting14:09
*** shwetaap1 has joined #openstack-meeting14:09
*** nshaikh has quit IRC14:11
*** Guest5899 is now known as b3nt_pin14:12
*** moha_hunt has quit IRC14:12
*** b3nt_pin is now known as Guest4786014:12
*** gholler has quit IRC14:13
*** shwetaap has quit IRC14:13
*** gholler_ has quit IRC14:13
*** ameade_ has quit IRC14:18
*** johnbelamaric has joined #openstack-meeting14:19
*** ameade_ has joined #openstack-meeting14:20
*** johnbelamaric has left #openstack-meeting14:20
*** ayoung_ZZzz_zzZZ is now known as ayoung14:21
*** dave-mccowan_ has joined #openstack-meeting14:23
*** colinmcnamara has quit IRC14:24
*** dave-mccowan has quit IRC14:26
*** dave-mccowan_ is now known as dave-mccowan14:26
*** Qiming has quit IRC14:26
*** Ark has joined #openstack-meeting14:30
*** Ark is now known as Guest6203614:30
*** jgrimm is now known as zz_jgrimm14:32
*** dane_leblanc has joined #openstack-meeting14:32
*** Longgeek has quit IRC14:34
*** Guest62036 has quit IRC14:34
*** nadya_ has joined #openstack-meeting14:34
*** armax has joined #openstack-meeting14:36
*** Qiming has joined #openstack-meeting14:37
*** MeganR has left #openstack-meeting14:39
*** Longgeek has joined #openstack-meeting14:40
*** BobBall has joined #openstack-meeting14:41
*** Guest47860 has quit IRC14:41
*** mchalla has joined #openstack-meeting14:42
*** AlexF has joined #openstack-meeting14:44
*** che-arne has quit IRC14:46
*** mchalla has quit IRC14:47
*** mestery has quit IRC14:48
*** xuhanp has joined #openstack-meeting14:49
*** SridharG has left #openstack-meeting14:50
*** dkranz has joined #openstack-meeting14:50
*** balajiiyer has joined #openstack-meeting14:52
*** dboik has joined #openstack-meeting14:52
*** padkrish has joined #openstack-meeting14:55
*** che-arne has joined #openstack-meeting14:56
*** matel has joined #openstack-meeting14:56
*** markmcclain has joined #openstack-meeting14:58
*** Mandell has joined #openstack-meeting14:58
*** Qiming has quit IRC14:58
*** xingchao has joined #openstack-meeting15:01
*** Masahiro has joined #openstack-meeting15:03
*** wuhg has quit IRC15:05
*** wuhg has joined #openstack-meeting15:05
johnthetubaguy#startmeeting XenAPI15:06
openstackMeeting started Wed Nov 26 15:06:03 2014 UTC and is due to finish in 60 minutes.  The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot.15:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:06
*** openstack changes topic to " (Meeting topic: XenAPI)"15:06
johnthetubaguyhello folks15:06
openstackThe meeting name has been set to 'xenapi'15:06
johnthetubaguy#topic CI15:06
*** openstack changes topic to "CI (Meeting topic: XenAPI)"15:06
BobBallHowdy.15:06
matelHello15:06
johnthetubaguyBobBall: matel: hows things looking in CI land?15:06
BobBallGood... But...15:06
BobBallhttps://review.openstack.org/#/c/133975/15:06
BobBallDon't like that -115:07
BobBallI've not followed up on it and I need to I know15:07
BobBallbut it means I'm not happy to remove the restrictions yet15:07
BobBallthere are still some race conditions / circumstaces where some of the excluded tests will fail15:07
*** jpich has left #openstack-meeting15:07
matelthat's bad news15:08
*** Masahiro has quit IRC15:08
BobBallI did note that it's the same message we've seen many times... Details: {u'message': u'No valid host was found. There are not enough hosts available.', u'created': u'2014-11-19T16:57:33Z', u'code': 500}15:08
johnthetubaguylike 10% failure I guess15:08
matelWhat was the failure ratio?15:08
BobBallNo idea15:08
johnthetubaguyBobBall: that means you have too many instances running15:08
BobBallwe'd need maybe 100 runs to get a ratio15:08
BobBallYou think it's running out of RAM then?15:08
johnthetubaguyoh wait, maybe not...15:09
*** tbarron_out is now known as tbarron15:09
johnthetubaguywe need the other instance faults in the DB for that instance15:09
* BobBall checks screen-n-sch...15:09
matelIt's gonna be a hard nut to crack15:09
johnthetubaguyits possible it was retrying, and then runs out of hosts15:09
johnthetubaguythats more likely I guess15:09
*** Mandell has quit IRC15:09
BobBallscreen-n-sch is taking _ages_ to get from the CDN!15:10
*** beagles has joined #openstack-meeting15:10
*** jcoufal has quit IRC15:10
BobBallit's only 31k but has been downloading for over 60 seconds so far...15:10
*** beagles is now known as Guest7475215:10
* BobBall strums his fingers on the table15:10
johnthetubaguydoh15:11
BobBallLet's move on and see if that loads later.15:11
johnthetubaguyyeah15:11
johnthetubaguyany more for any more?15:11
*** ildikov has quit IRC15:11
*** MeganR has joined #openstack-meeting15:11
*** Guest74752 has quit IRC15:12
matelNeutron does not run in parallel for some reason.15:12
matelBut it ran in serial.15:12
matelLet me dig out the results.15:12
*** beagles_ has joined #openstack-meeting15:12
matelhttp://paste.openstack.org/show/137612/15:12
*** Youcef has quit IRC15:12
*** beagles_ is now known as b3nt_pin_nickles15:12
BobBall21 failures in parallel was that?  I don't remember15:13
BobBallor was that 21 failures when we went serial only?15:13
BobBallThat must have been serial only, sorry15:13
BobBallworker 0 only :)15:13
johnthetubaguyyeah, I have a feeling neutron broke in parallel15:13
BobBallWe got lots more failures running in parallel didn't we15:13
*** MeganR has quit IRC15:13
BobBallSure - but it's run in parallel for -infra15:14
johnthetubaguysome races still in iptables, I think I was told15:14
johnthetubaguyhmm, odd15:14
johnthetubaguyI guess it muss be now15:14
BobBallAh - that might not be using iptables15:14
johnthetubaguyanyways15:14
BobBallmatel: Which firewall was that with?15:14
matelWe are not using iptables either15:14
BobBallNow using noop?15:14
mately15:14
BobBallOK15:15
BobBallDo you know who might have more details on the races you're thinking of johnthetubaguy ?15:15
johnthetubaguyBobBall: trying to remember...15:15
johnthetubaguyBobBall: we don't have the neutron call back libvirt have implemented to avoid lots of those races, it probably related15:16
*** mestery has joined #openstack-meeting15:16
johnthetubaguylibvirt has instance events call back to say neutron has completed, or something like that15:16
johnthetubaguybasically there is a wait for event thing in libivrt15:16
BobBallI see15:17
BobBallSo what does that do?15:17
BobBallstop neutron from running things in parallel until libvirt has said that X has finished?15:17
johnthetubaguynot really15:17
johnthetubaguyit waits to start the VM until neutron has set everything up15:18
BobBallSo it's the nova driver _listning_ to the neutron event15:18
BobBallso if the issue is what you're thinking of we don't need the nova driver to emit events15:18
matelWe are experiencing failures with parallel runs15:19
matelIf we were missing something like what you said, we would see failures with serial as well, don't we?15:19
johnthetubaguyyes thats true15:19
BobBallNo - because neutron has slowness issues15:19
matelOr maybe the higher load...15:19
BobBallso races will become more visible in parallel15:19
johnthetubaguyBobBall: +115:20
johnthetubaguyyou typed it before I did15:20
matelBobBall said the magic word: race15:20
johnthetubaguyyeah, it is a race15:20
johnthetubaguyit might be ready when you start the VM, it might not15:20
BobBallLet's just add a sleep 60.15:21
*** lazy_prince is now known as killer_prince15:21
johnthetubaguyso libvirt waits till its ready15:21
BobBallSleep 60's always work.15:21
johnthetubaguyright...15:21
BobBall... if you have enough of them15:21
matelAnd they speed up the time it takes to run the tests.15:21
johnthetubaguywhat are the failures looking like?15:21
BobBallParadixically there matel ... :)15:21
*** balajiiyer has left #openstack-meeting15:21
*** Ark has joined #openstack-meeting15:21
*** irenab has quit IRC15:22
*** Ark is now known as Guest1052915:22
*** mtanino has joined #openstack-meeting15:22
matelgimme a sec15:22
mateltempest.api.compute.servers.test_attach_interfaces.AttachInterfacesTestJSON.test_create_list_show_delete_interfaces15:23
mateltempest.api.compute.servers.test_attach_interfaces.AttachInterfacesTestXML.test_create_list_show_delete_interfaces15:23
mateltempest.api.network.admin.test_quotas.QuotasTest.test_lbaas_quotas15:23
mateltempest.api.network.test_service_type_management.ServiceTypeManagementTestJSON.test_service_provider_list15:23
mateltempest.cli.simple_read_only.network.test_neutron.SimpleReadOnlyNeutronClientTest.test_neutron_lb_healthmonitor_list15:23
mateltempest.cli.simple_read_only.network.test_neutron.SimpleReadOnlyNeutronClientTest.test_neutron_lb_member_list15:23
mateltempest.cli.simple_read_only.network.test_neutron.SimpleReadOnlyNeutronClientTest.test_neutron_lb_pool_list15:23
mateltempest.cli.simple_read_only.network.test_neutron.SimpleReadOnlyNeutronClientTest.test_neutron_lb_vip_list15:23
mateltempest.cli.simple_read_only.network.test_neutron.SimpleReadOnlyNeutronClientTest.test_neutron_meter_label_list15:23
mateltempest.cli.simple_read_only.network.test_neutron.SimpleReadOnlyNeutronClientTest.test_neutron_meter_label_rule_list15:23
mateltempest.scenario.test_load_balancer_basic.TestLoadBalancerBasic.test_load_balancer_basic15:23
mateltempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_hotplug_nic15:23
mateltempest.scenario.test_security_groups_basic_ops.TestSecurityGroupsBasicOps.test_cross_tenant_traffic15:23
mateltempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest.test_compute_with_volumes15:23
*** zehicle has quit IRC15:23
johnthetubaguyI don't really mean that15:23
mateljohnthetubaguy: these are the failed ones with serial15:23
BobBalltest_hotplug_nic <-- we don't do that yet do we?15:23
johnthetubaguywhat sort of failures did those see?15:23
johnthetubaguyBobBall: I have code for that, but its not finished or merged15:24
*** ildikov has joined #openstack-meeting15:24
BobBallOK, great.15:24
johnthetubaguyare they ssh failure?15:24
BobBallWe might want to talk about that in the new year15:24
johnthetubaguyBobBall: put it up for review a year ago or so15:24
BobBall*nod*15:25
johnthetubaguycoded it in some airport after some US summit, while drinking something from starbucks15:25
johnthetubaguyanyways15:25
johnthetubaguyany more we want to debug now? or do this offline?15:26
BobBallSounds like it doesn't even need reviewing - just merge it :D15:26
BobBallThat's the perfect coding environment!15:26
BobBallNo, I don't think there is more to talk about on that front15:26
matelno15:26
johnthetubaguy#topic Open Discussion15:27
*** openstack changes topic to "Open Discussion (Meeting topic: XenAPI)"15:27
johnthetubaguyany more?15:27
matelnope15:28
*** david-lyle_afk is now known as david-lyle15:28
*** dimsum__ has quit IRC15:28
*** stevemar has joined #openstack-meeting15:28
BobBallyes15:28
BobBallmaybe15:28
BobBallshould we talk about DIB?15:28
*** dimsum__ has joined #openstack-meeting15:29
matelWe'll give a try to use DIB to create the domU's root filesystem15:29
matelSo something like this: You have a qcow2 with a XenServer inside, on the SR sits a vhd containing domU's virtual disk15:30
johnthetubaguyOK, yeah, they are having "fun" using that in rackspace mind15:30
johnthetubaguycrazy15:30
*** gokrokve has joined #openstack-meeting15:30
matel... Use tapdisk to mount the virtual disk..15:30
johnthetubaguyanyways, any more?15:30
matelNo, thanks, thanks.15:30
*** adahms has quit IRC15:30
*** Sukhdev has joined #openstack-meeting15:31
johnthetubaguythanks all15:31
johnthetubaguy#endmeeting15:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:31
openstackMeeting ended Wed Nov 26 15:31:07 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/xenapi/2014/xenapi.2014-11-26-15.06.html15:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/xenapi/2014/xenapi.2014-11-26-15.06.txt15:31
openstackLog:            http://eavesdrop.openstack.org/meetings/xenapi/2014/xenapi.2014-11-26-15.06.log.html15:31
BobBallbye bye.15:31
*** BobBall has left #openstack-meeting15:31
*** marun has joined #openstack-meeting15:31
*** radez is now known as radez_g0n315:32
*** xuhanp has quit IRC15:33
*** rwsu has joined #openstack-meeting15:34
*** doron_afk is now known as doron_15:34
*** matel is now known as matel_feeding15:34
*** ddieterly has joined #openstack-meeting15:36
*** xingchao has quit IRC15:37
*** xuhanp has joined #openstack-meeting15:37
*** alexpilotti has joined #openstack-meeting15:39
*** padkrish has quit IRC15:40
*** fnaval has joined #openstack-meeting15:40
*** otter768 has joined #openstack-meeting15:40
*** xuhanp has quit IRC15:43
*** BharatK has joined #openstack-meeting15:43
*** alex_xu has quit IRC15:44
*** yamamoto has joined #openstack-meeting15:44
*** otter768 has quit IRC15:44
*** chandankumar has joined #openstack-meeting15:45
*** zehicle has joined #openstack-meeting15:45
*** jcoufal has joined #openstack-meeting15:46
*** yingjun has quit IRC15:46
*** padkrish has joined #openstack-meeting15:48
*** thingee has joined #openstack-meeting15:49
*** TobiasE has joined #openstack-meeting15:49
*** colinmcnamara has joined #openstack-meeting15:50
*** matel_feeding is now known as matel15:51
*** js1123 has quit IRC15:52
*** ptoohill_ has joined #openstack-meeting15:53
*** js1123 has joined #openstack-meeting15:54
*** neeti has joined #openstack-meeting15:54
*** Yogi2 has joined #openstack-meeting15:55
*** aarefiev has joined #openstack-meeting15:55
*** tsekiyama has joined #openstack-meeting15:55
*** bswartz has joined #openstack-meeting15:56
*** js1123 has quit IRC15:56
*** cknight has joined #openstack-meeting15:57
*** js1123 has joined #openstack-meeting15:58
*** afazekas has quit IRC15:58
*** georgkunz has joined #openstack-meeting15:59
*** xyang1 has joined #openstack-meeting15:59
*** jbernard has joined #openstack-meeting15:59
*** BrianB_ has joined #openstack-meeting15:59
thingee#startmeeting cinder16:00
openstackMeeting started Wed Nov 26 16:00:02 2014 UTC and is due to finish in 60 minutes.  The chair is thingee. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** sarob has joined #openstack-meeting16:00
*** openstack changes topic to " (Meeting topic: cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
thingeehi all16:00
tbarronhi16:00
*** jseiler has joined #openstack-meeting16:00
jaypipeso/16:00
Yogi2Hello16:00
cknightHi16:00
*** BrianB_ has quit IRC16:00
TobiasEHi16:00
*** avishay has joined #openstack-meeting16:00
kaisers1hiya16:00
bswartzhey16:00
xyang1hi16:00
georgkunzhi16:00
thingeeagenda today is small, yay!16:00
avishayyoyoyo16:00
thingee#link https://wiki.openstack.org/wiki/CinderMeetings16:00
thingeejust a reminder because it has been coming up a couple of times, k-1 is the only time to get your new driver in16:01
*** smcginnis has joined #openstack-meeting16:01
DuncanTHey16:01
smcginniso/16:01
e0nehi16:01
*** dane_leblanc_ has joined #openstack-meeting16:01
*** akerr has joined #openstack-meeting16:01
*** rhe00 has joined #openstack-meeting16:01
thingeeyou can read more details here http://lists.openstack.org/pipermail/openstack-dev/2014-October/049512.html16:01
*** enikher has joined #openstack-meeting16:01
enikherhey16:01
*** flip214 has joined #openstack-meeting16:02
thingeeI will be sending out a reminder to all potential new driver maintainers that are already targeted for k-1 that they're making slow progress and that we're aiming to merge december 1816:02
thingeeOK, lets begin16:02
TobiasEThe blueprint is https://blueprints.launchpad.net/cinder/+spec/volume-status-polling.16:02
thingee#topic volume status poll16:02
*** openstack changes topic to "volume status poll (Meeting topic: cinder)"16:02
thingeeTobiasE: you're up16:02
thingee#link https://review.openstack.org/#/c/132225/16:02
thingeefor the cinder spec16:02
TobiasEthanks16:02
*** aepifanov has joined #openstack-meeting16:03
thingeeand for the nova spec:16:03
thingee#link https://review.openstack.org/#/c/135367/16:03
*** dimsum__ is now known as dims16:03
thingeeI'm assuming this is why I see a jaypipes in the audience this morning16:03
thingee:)16:03
jaypipesindeed :)16:03
thingeeTobiasE: go ahead16:03
TobiasEWe see some problems when running e.g. 100 attach16:04
*** mrunge has quit IRC16:04
*** dane_leblanc has quit IRC16:04
TobiasEThe idea is to implement async between nova and cinder16:04
avishayTobiasE: 100 simultaneous attach operations to VMs?16:04
*** Riddhi has joined #openstack-meeting16:04
*** Riddhi has quit IRC16:04
TobiasEyes, high load scenarios16:05
avishayOK16:05
*** Riddhi has joined #openstack-meeting16:05
enikherBut not the vm attachment is failing. it is the communication towards the storage backend16:05
TobiasEWe have timeouts on RPC or HA-proxy side16:06
enikherSince terminate and initialize_connection are calls not casts we face the rpc timeout here16:06
*** vhoward has joined #openstack-meeting16:06
*** Mandell has joined #openstack-meeting16:06
TobiasEAnd then inconsistencies between backend and Cinder DB16:06
*** padkrish has quit IRC16:07
thingeeok, so jgriffith raised the point that he would not want to see the timeouts raised. Which makes sense16:07
thingeeDuncanT would rather see timeouts raised16:07
DuncanTAPI load is already an issue, so I'm not sure I'd like every attach polling. Maybe a blocking call that ends with 'Now poll' if it times out?16:08
*** henrynash has joined #openstack-meeting16:08
thingeeI'm concerned you're going to see performance problems if you have a cinder volume polling, even with green threads16:08
*** bogdando has quit IRC16:09
avishaywhy poll?  no mechanism for callback?16:09
thingeethe only difference is you won't have something that times out16:09
DuncanTi.e. time out the API call slightly faster than the RPC timeout16:09
jaypipesis there a way to query the backend storage array for how many ongoing attach requests are underway, and place the request for a new attachment into a queue and then return a polling URI to the caller?16:09
TobiasEDuncanT: Catching Exeption and then start polling?16:09
DuncanTTobiasE: If we can16:09
*** vijendar has joined #openstack-meeting16:09
*** doron_ is now known as doron_afk16:09
thingeejaypipes: that's what I was thinking, but no we don't have something like that16:09
DuncanTjaypipes: That sounds plausible, but is a fairly big change16:10
flip214a callback would be the cleanest solution, I think16:10
* jaypipes personally has no problem with not having a timeout as long as there is some reliable way of knowing if the backend is actively working on (or has a queued) attachment reqyuest16:10
enikhera worker queue in the cinder-volume manger is also a good idea16:10
enikherbut does not solve the issue completly16:10
DuncanTThe load a backend can cope with varies massively though....16:10
thingeeenikher: there's a patch with that and state problems with that.16:10
jaypipesDuncanT: yes, I would suspect that.16:11
DuncanTflip214: A call back into nova?16:11
enikherThingee could you past the patch?16:11
jaypipesDuncanT, flip214: that is what neutron does for NIC attachment.16:11
*** bogdando has joined #openstack-meeting16:11
thingeeenikher: https://review.openstack.org/#/c/135795/16:11
flip214DuncanT: basically, "whereever you like" ... simply putting an URL into the request that is being called upon completion.16:12
thingeeflip214, jaypipes, TobiasE, DuncanT: makes sense to me16:12
thingeepolling is soooo four years ago16:12
avishayyes16:12
flip214or, perhaps, return OK if possible within one second; else say "later, will call URL"16:12
*** jnrao has joined #openstack-meeting16:12
*** Ark has joined #openstack-meeting16:12
avishayflip214: one code path is hard enough i think16:13
flip214there are HTTP codes for that, I believe.16:13
bswartzflip214: I like that idea, but it makes the API harder to use through a firewall, because the callback could get blocked16:13
jaypipesflip214: yes, that is what neutron does.16:13
*** Ark is now known as Guest863816:13
jaypipes202 Accepted.16:13
*** patrickeast has joined #openstack-meeting16:13
*** Guest10529 has quit IRC16:13
DuncanTbswartz: This is nova talking to cinder, so if you have a firewall there you have bigger problems16:13
flip214bswartz: in that case, the call has to be idempotent - and gets called until cinder says "done", every few seconds.16:13
thingeeDuncanT: +116:13
jaypipesDuncanT: right :)16:13
flip214with all the disadvantages.16:13
bswartznova isn't the only thing that does cinder volume attaches16:13
*** MarkAtwood has joined #openstack-meeting16:13
bswartzcinder is consumed by other clients too16:14
xyang1after cinder is done with initialize connection, nova side still need to discover the lun, etc.  so attach is not complete just after cinder completes initialize_connection16:14
flip214"discover"? isn't that passed from cinder to nova?16:14
DuncanTbswartz: Fair enough. I'd like to hear those usecases if there are specific ones, please?16:14
xyang1flip214: nova side has some work to complete after cinder returns16:15
xyang1flip214: that's why it waits currently16:15
DuncanTSo the callback would cause that step to happen16:15
flip214xyang1: yes, but I thought that cinder passes information like IP, LUN, etc back to nova.16:15
*** doron_afk has quit IRC16:15
bswartzblock storage as a service? that's not an obvious enough use case? some people like cinder but have problems with nova and choose to use something else, or they have something preexisting that they choose to use instead of noca16:15
jaypipesso, bottom line, is that the cinder+nova contributor communities need to settle on either supporting long polling or supporting push based notifications ala Neutron's NIC attachment APIs.16:15
DuncanTYou still need a timeout there though, to deal with stuck backends etc16:15
bswartzs/noca/nova/16:15
xyang1flip214: nova needs to make sure the lun is visible to the host16:15
*** drankis has joined #openstack-meeting16:16
thingeeTobiasE: can we see the spec redone with callback in mind?16:16
*** dsetia has joined #openstack-meeting16:16
TobiasEMight need some help with that16:16
DuncanTbswartz: I know the principle, if there are any concrete cases you know of then I'd like to hear about them. I want to write a bare metal attach; if somebody has already done it then it might same me making mistakes they've already avoided16:16
*** zigo has quit IRC16:16
thingeeTobiasE: seems like flip214 has some knowledge to help. :)16:17
jaypipesxyang1: it's the same problem domain for NIC attachment. Neutron sends information (the "port_binding" dict) to Nova when the NIC has been created inside the Neutron drivers, and Nova then uses the port_binding information to plug the VIF locally on the nova-compute node16:17
thingeeTobiasE: I would like to see things expanded with functional tests though.16:17
xyang1jaypipes: ok, then we should take a look of that implementation16:17
bswartzI'm not at liberty to speak about the case I'm aware of. In any case, I agree the firewall problems is an unlikely one -- just wanted to make sure it was considered.16:17
avishaybswartz: cinder already has calls to nova, so i don't think this adds new requirements16:17
thingeeTobiasE: also bring in the warnings that bswartz into the spec.16:18
TobiasEthingee: Testing is essential here16:18
jaypipesxyang1: yes, that is what I recommend as well, but it relies on the cinder+nova contrib communities getting aligned on that direction. thus, I'm here :)16:18
*** zaneb has quit IRC16:18
DuncanTbswartz: Fair enough16:18
thingeeTobiasE: absolutely, i just meant the current state of the spec doesn't explaining the testing plan well.16:18
xyang1jaypipes: ok thanks16:18
thingee#agreed cinder to do callback for attachments for clients to consume16:19
thingee#action TobiasE to update current spec with cinder doing callbacks for attachments16:19
thingeeanything else?16:19
DuncanTAre we going to allow polling as well?16:19
DuncanTi.e. what does nova get if it calls attach a second time?16:19
rushiagrhi!16:20
enikhernova will timeout in live-migration16:20
xyang1DuncanT: it still can be successful if it is already attached on the array16:20
enikhersince initialize_connection is then longer then expected16:20
jaypipesDuncanT: the second call should return a 409 Conflict, IMO.16:20
*** shashankhegde has joined #openstack-meeting16:21
DuncanTjaypipes: That makes things tricky if nova-compute got restarted or something....16:21
jaypipesDuncanT: because you don't want to create two callbacks inside Nova. only one.16:21
thingeeenikher, DuncanT: these details can be worked on the mailing list http://lists.openstack.org/pipermail/openstack-dev/2014-November/049756.html16:21
enikherWhat will happen if nova will not callback?16:21
thingeeI just wanted TobiasE to be able to move forward16:21
TobiasEOK16:21
thingeethanks for the help jaypipes!16:21
enikherstill we have the same timeout problem16:22
bswartznova still needs a timeout in case the callback never comes16:22
jaypipesDuncanT: if nova-compute gets restarted, the callback will have either been consumed from the MQ or not. If not, then the status of the volume attachment should be ERROR, and the user should be able to resubmit an attachment request.16:22
*** winston-d has joined #openstack-meeting16:22
DuncanTjaypipes: But cinder will never get told that nova didn't successfully attach16:22
enikherwe need that live-sign to see that the backend is still working16:22
jaypipesbswartz: cinder should be able to copy the same retry/timeout code from the neutron work.16:22
*** colinmcnamara has quit IRC16:23
jaypipesDuncanT: I don't see how that is a problem? Isn't the storage backend the source of truth for that type of information?16:23
flip214enikher: then just specify that the callback takes a parameter "in_progress=<step-number>"16:23
enikhernot an neutron expert could you paste the commit?16:23
DuncanTjaypipes: No. There's the cinder db, and the backend, and currently they can get out of sync16:24
xyang1jaypipes: currrently the state of the volume will be changed back to 'available' if timeout happens16:24
*** zhithuang has joined #openstack-meeting16:24
flip214well, I believe that the DB should always be the "should" state.16:24
xyang1even though the array may have finished the attach operation16:24
bswartzjaypipes: does that involve cinder storing more state? typically cinder backends try to be stateless16:24
*** zhithuang is now known as winston-d_16:24
*** ildikov has quit IRC16:24
DuncanTjaypipes: We can solve the current problem by making cinder queue a detach if it times out16:24
flip214and the reality has to match what's there.16:24
flip214so in case of conflict the attach operation needs to be re-doable on nova.16:25
jaypipesDuncanT: right, but how is that Nova's problem?16:25
*** matel is now known as matel_off16:25
DuncanTjaypipes: If nova thinks the attach is still happening, you get in a mess. The nova bdm is yet another piece of state that gets out of sync16:25
*** dulek has quit IRC16:26
TobiasEjaypipes: Haven't you worked on cleaning BDM up16:26
*** padkrish has joined #openstack-meeting16:26
DuncanTOne option rather than polling or callback is just for cinder to clean up better on timeout16:27
DuncanTAnd leave nova to clean itself up16:27
*** zigo has joined #openstack-meeting16:27
jaypipesDuncanT: ++16:27
enikherthen the user has to try again?16:27
winston-d_BDM shouldn't be considered as a place store volume attaching state, 'cos you can attach a volume to a 'stopped' instance, BDM still exists, and volume not attached.16:27
enikherthat is not good I think16:27
DuncanTThis would mean that some attach calls fail and have to be retried, but that is the cloud way sometimes16:27
jaypipesDuncanT: if nova can call cinder to get volume metadata, and considers cinder's response authoritative, that would be ideal.16:27
*** sarob has quit IRC16:28
flip214DuncanT: that means that on high load requests will fail, get requeued, and make still bigger load.16:28
DuncanTenikher: Sometimes it is better for the user to retry than to over complicate code - instance startup and volume create can fail and need retrying too16:29
DuncanTflip214: Hopefully the load spike will have passed by then16:29
bswartzflip214: there's a point at which any system will be overwhelmed -- at that point the caller must throttle his requests or expect failure16:29
flip214I'd prefer to go the callback route, without looking at timeouts for now. that solves the high-load issue.16:29
enikheryes but the user does not get enough information to know that the backend is just overloaded16:29
DuncanTBut the callbacks massively increase the odds of a 'stuck' system16:29
DuncanTWhich can only be fixed by admin16:30
*** nellysmitt has quit IRC16:30
enikherwith very slow backends we had problems to attach 10 volumes16:30
DuncanTRather than something the user can simple retry16:30
*** gokrokve_ has joined #openstack-meeting16:30
*** k4n0 has quit IRC16:30
enikherso that would mean the user has to do a lot of retries16:30
DuncanTenikher: Then buy a better backend IMO16:30
flip214"simply retry" - based upon what information? she won't know whether the load spike is done.16:30
DuncanTflip214: Not having any timeouts is a total none-starter16:30
*** georgkunz has quit IRC16:30
*** gokrokve has quit IRC16:31
DuncanTflip214: If the backend is broken then you end up with the user in an unfixable mess16:31
enikherActually what do you think about estimating the timeout16:31
flip214if the user can see the number of queued requests, and in which position some specific one is, she can see progress - or not.16:31
thingeeDuncanT: if this is just to fetch the initialize_connection, how do we end up in a stuck state? If nova never sets the volume to in-use, can't cinder just roll it back?16:31
*** zaneb has joined #openstack-meeting16:31
enikherif you want to have a short ha-proxy timeout the timeout will often occur16:31
DuncanTflip214: That is way more complex than just saying 'rety some time'16:31
DuncanTthingee: Once you've done the prep work in order to return the connection info, how do you know when to roll back?16:32
bswartzI agree -- you always need a timeout to deal with the case where cinder had a critical hardware failure and was forced to restart16:32
avishayhopefully being able to scale out cinder-volume will also help with higher loads, and yes, backends need to be sane - i would open a bug for a backend that was so inefficient (if it was something the driver could fix)16:32
thingeeDuncanT: that would be up to cinder.16:32
flip214http://ferd.ca/queues-don-t-fix-overload.html    - queues are good, but don't fix overload.16:32
enikherflip214: the backend is still working or not?16:32
flip214but at least they can be used to _show_ whether there's progress-.16:32
DuncanTbswartz: Or when rabbit lost a message due to restarting, or a cinder service got restarted, or whatever16:32
flip214having retries means (still) higher load, so I don't think the user should retry.16:33
*** jcoufal has quit IRC16:33
DuncanTflip214: Exposing queues to a cloud user is a nightmare16:33
thingeeso here's where I'm going with this. If nova does an initialize_connection request, cinder does a call back. If nova disappears, cinder should roll it back, unless nova later does something with the call back and tells cinder to set the volume to in-use16:33
DuncanTflip214: Rate limit the retries just like you have to rate limit everything else to avoid DoS16:33
enikherflip214: estimate the timeouts? so that the polling is not done so frequently?16:33
DuncanTthingee: If cinder has rolled it back, then the work needs to be done again, which means another callback... ad infinitum for a slow backend16:34
*** bill_az has joined #openstack-meeting16:34
thingeeDuncanT: there was no mention of another call back16:35
flip214enikher: estimating based upon what? that's another guess-game.16:35
thingeeupdate status is an api call, which just passes to cinder db16:35
winston-d_thingee: wait, what happen when a user attach a volume to a stopped instance, initialize_connection() can be called but the actual attach operation can be long after.16:35
avishayI agree with DuncanT - the spike should be over very quickly and the user can retry.  if the spike lasts a long time then it's not a spike and the cloud sucks16:35
*** Mandell has quit IRC16:35
thingeewinston-d_: exactly16:35
DuncanTavishay++16:35
*** sarob has joined #openstack-meeting16:35
*** shashankhegde has quit IRC16:36
winston-d_thingee: what i meant was in that cinder, cinder shouldn't rely on callback.16:36
winston-d_s/in that cinder/in that case/16:36
*** neeti has quit IRC16:36
DuncanTSo our number one support call for LVM is 'my volume is stuck in attaching/detaching' - this sounds like it will make that way worse16:36
thingeeHonestly I think if the backend is under load, cinder should rely on the call back. if it's not, it should continue behavior as normal16:37
winston-d_guitarzan: what do you think?16:37
thingeemajority of us apparently won't even notice different behavior because according to the feedback in the spec, we're all user super fast solutions that don't bog down on load.16:38
DuncanTTwo paths means more testing, more bugs and more failures16:38
*** eglynn is now known as eglynn-afk16:38
thingeeDuncanT: I know, extra work is a bummer.16:38
DuncanTIf most people don't use a code path, it /will/ end up weirdly broken over time16:38
*** mattgriffin has joined #openstack-meeting16:39
thingeeMy proposal went unanswered, so I'm going with that until someone responds. I'll raise it on the mailing list again though16:39
enikherSo callback does not seem to be helpful or?16:39
thingeethis topic is dead imo for this current meeting.16:39
*** shashankhegde has joined #openstack-meeting16:39
thingeeenikher: read my proposal I said twice in this meeting.16:39
thingee#topic Over-Subscription Alternative16:39
*** openstack changes topic to "Over-Subscription Alternative (Meeting topic: cinder)"16:39
thingeebswartz: you're up16:40
bswartzhey guys16:40
bswartz#link https://review.openstack.org/#/c/129342/16:40
bswartzI'm the lone voice of negativity here16:40
*** phil_ has quit IRC16:40
*** khaldrogox has joined #openstack-meeting16:40
thingeebswartz: not in this meeting :)16:40
bswartzbut I proposed an alternative to xyang's oversubscription proposal16:40
bswartzbasically I have 2 concerns16:41
xyang1thingee: everyone said we were all in agreement on this topic before the summit:)16:41
bswartz1) I don't think it's the right UI for administrators to put oversubscribe ratios in the cinder.conf file -- I think it's better to make them an aspect of the volume_type16:41
*** ebalduf has joined #openstack-meeting16:42
avishaybswartz: why?16:42
bswartz2) I think it's a bad idea to implement oversubscription by having the backends effectively lie to the scheduler about how much free space they have, I think the scheduler should know the true values and implement oversubscription itself16:42
xyang1bswartz: I think you can only calculcate over subscription ratio for a backend or a pool, not a volume type though16:43
bswartzavishay: thick provisioning (as opposed to thin) may be a value-add option you want to sell to users who are willing to pay more16:43
*** scheuran has quit IRC16:43
DuncanTbswartz: re 2) I sort of agree16:43
*** asselin_ has joined #openstack-meeting16:43
*** mattgriffin has quit IRC16:43
*** padkrish has quit IRC16:43
xyang1because a volume type can be associated with multiple backends, a single backend, or a backend can support multiple volume types16:43
DuncanTre 1) though, the problem is that if a backend fills up with bronze volumes then that doesn't help the gold volumes at all16:43
bswartzxyang1: I attempted to answer that question in my followup comment on the review16:44
xyang1I just can't see how the formula will work to compare capacities from a backend with a ratio of a type16:44
*** mchalla has joined #openstack-meeting16:44
asselin_\o16:44
winston-d_bswartz: my understanding is xyang1's proposal doesn't 'lie' to scheudler, it's a fact that right now, scheduler doesn't know the oversubscription ratio of backends, even though it knows actual/virtual provisioned capacity.16:44
jaypipesxyang1, TobiasE, enikher: https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L4453-L4526 <-- the relevant code for how NIC plugging events are handled.16:44
xyang1jaypipes: thanks!  we'll take a look16:44
bswartzDuncanT: so mixing gold and bronze on the same backend only works if the backend is enable to enforce that the gold volumes get all the space they're promised16:44
thingeebswartz: hasn't the backend been able to lie to cinder scheduler for a while?16:44
jaypipesxyang1, TobiasE, enikher: it's not pretty, but it works...16:44
thingeebswartz: infinite16:44
bswartzI proposed that backends also report a "space_reservation" capability16:45
DuncanTbswartz: Quite. I don't think most can do that16:45
*** zehicle has quit IRC16:45
*** gokrokve_ has quit IRC16:45
thingeejaypipes: thanks16:45
bswartzDuncanT: NetApp can do that -- I'm pretty sure EMC can do that -- LVM can do it16:45
TobiasEjaypipes: thanks16:46
thingeebswartz: WRT to #2, hasn't the backend been able to lie to scheduler for a while now? by saying "infinite"16:46
*** ebalduf has quit IRC16:46
DuncanTbswartz: LVM can? Ok. objection withdrawn16:46
bswartzIMO it's pretty dumb to implement thin provisioning if you don't have a way to exempt some things from the thin provisioning16:46
winston-d_bswartz: we have 'reserved_percentage' since filter_scheduler is introduced, but it's never used. what's the difference between this and 'space_reservation'?16:46
bswartzotherwise you're asking for disaster16:46
xyang1bswartz: is space_reservation actually a thick lun?16:47
*** jjmb has joined #openstack-meeting16:47
bswartzxyang1: yes -- it would be thick luns16:47
bswartzwinston-d: it's important that the reservation only applies to volumes for which the "gold" promise was made16:47
xyang1bswartz: you can still create thick luns. this proposal doesn't prevent that16:47
bswartza space reserve % is a blanker reserve across the whole backend16:47
bswartzblanket*16:47
*** padkrish has joined #openstack-meeting16:47
*** dane_leblanc_ has quit IRC16:48
jaypipesxyang1, TobiasE, enikher: https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L532 <-- the wait_for_instance_event() main method.16:48
*** suro_ has joined #openstack-meeting16:48
*** mchalla has quit IRC16:48
xyang1bswartz: there's already a used ratio that controls how much is really used16:48
flip214jaypipes: thank you.16:48
xyang1jaypipes: thanks!16:48
jaypipesno problemo :)16:48
bswartzanyways I'm not married to my proposal -- I think some middle ground can be found between what xyang proposed and what I proposed16:49
*** avishay has quit IRC16:49
bswartzI just wanted to raise those 2 concerns and suggest some ways to work around them16:49
*** khaldrogox has quit IRC16:49
thingeebswartz: the used ratio xyang1 mentioned doesn't help?16:49
DuncanTIf you really can do per-volume reservations and get accurate answers out of the backend summing them then that sounds preferable16:49
xyang1bswartz: so I think your driver can still calculate free space the way you described and send back to scheduler16:49
*** suro_1 has joined #openstack-meeting16:50
bswartzthe current proposal makes it impossible to mix "gold" and "bronze" storage on the same backend, assuming the admin wants gold to be thick and bronze to be thin16:50
DuncanTI think I'm starting to agree with Ben here16:50
*** daneyon has quit IRC16:51
thingeexyang1: do you have any plans to mix the different types?16:51
flip214bswartz: it's possible. you only have to do one thin pool per thin LV ;)16:51
*** colinmcnamara has joined #openstack-meeting16:51
*** ebalduf has joined #openstack-meeting16:51
bswartzflip214: are you referring to cinder pools?16:51
xyang1bswartz: there are unresolved issues with Ben's proposal, so I'm still not sure16:51
*** emagana has joined #openstack-meeting16:51
bswartzin priciple, a backend could have 2 pools, each with different oversubscribe amounts16:52
bswartzbut how would the admin enter that info into cinder.conf?16:52
*** Masahiro has joined #openstack-meeting16:52
thingeexyang1: what's what?16:52
xyang1thingee: the over subscription ratio should really be calculated for a pool or backend16:52
*** suro_ has quit IRC16:52
bswartzxyang1: did you read my followup comment that answers your question?16:53
xyang1it is the ratio of virtual capacity over total capacity16:53
bswartzI can write up a whole spec if I need to to spell out all the details16:53
xyang1bswartz: did you just update?16:53
bswartzbut I'd rather just adjust the existing spec16:53
*** ildikov has joined #openstack-meeting16:53
bswartzxyang1: like 2 hours ago16:53
thingeebswartz: xyang1 already replied back to you16:53
* jaypipes goes off hunting for lunch...16:53
winston-d_bswartz: the driver should expose some per-pool level config options to solve that problem - per pool overcommit amounts16:53
*** eghobo has joined #openstack-meeting16:54
DuncanTwinston-d_: Tricky with dynamic pools16:54
bswartzDuncanT: that's what I was thinking16:54
winston-d_DuncanT: unfortunately yes.16:55
bswartzif we can make new pools dynamically, then the driver will have to make up some value or use a default under the existing spec16:55
thingee5 minute warning16:55
bswartzI just have a feeling that the scheduler is in a better position than the backends to make decisions about where and when to oversubscribe, and if the scheduler needs more data from the backends to do so, then let's implement that16:55
* DuncanT would like to read some more details of bswartz' approach, if that is doable?16:55
flip214bswartz: +116:56
*** nati_uen_ has quit IRC16:56
*** changbl has joined #openstack-meeting16:56
*** oanufriev has quit IRC16:56
DuncanTIt feels like it better answers the questions like dynamic pools and mixing types16:56
xyang1so the problem is scheduler gets free capacity from  backend16:56
xyang1scheduler doesn't calculate free capacity for the backend16:56
winston-d_bswartz: i agree with your last statement, but i thought that was what xyang1's proposal plan to do?16:56
*** nati_ueno has joined #openstack-meeting16:56
*** Masahiro has quit IRC16:56
xyang1to do what bswartz suggested, it seems to be a big over haul of the scheduler16:57
*** s3wong has joined #openstack-meeting16:57
bswartzwinston-d: it's a step in the right direction, but I think we can do better16:57
xyang1bswartz: so the formula you provided to calculate free space, that should be executed by the driver and report back in stats16:57
xyang1the scheduler doesn't calculate that16:57
bswartzjust to be clear -- I'm not completely opposed to xyang's approach -- it's an improvement16:58
xyang1available_capacity16:58
bswartzI'm just worried that we're commiting ourselves to an interface that can't be improved on later16:58
bswartzDuncanT: I can write a whole new spec16:58
bswartzor a wiki or something16:58
bswartzmake a wall of text on the ML?16:59
bswartzs/make/maybe/16:59
winston-d_bswartz: thx, that'll be very helpful.16:59
DuncanTbswartz: It sounds like picking any one of those would be a good idea. Spec seems the most logical16:59
xyang1bswartz: so that is a problem because scheduler doesn't calculate available capacity for a backend16:59
*** padkrish has quit IRC16:59
thingeexyang1: +116:59
*** padkrish has joined #openstack-meeting16:59
bswartzxyang: looks like you and I will have to meet up again offline17:00
thingee#endmeeting17:00
xyang1bswartz: sure17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Wed Nov 26 17:00:08 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-26-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-26-16.00.txt17:00
*** jbernard has left #openstack-meeting17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-26-16.00.log.html17:00
*** akerr has left #openstack-meeting17:00
*** smcginnis has left #openstack-meeting17:00
*** pballand has joined #openstack-meeting17:00
*** Yogi2 has left #openstack-meeting17:00
thingeecontinuing on #openstack-cinder17:00
*** winston-d_ has left #openstack-meeting17:00
rushiagro/17:00
*** flip214 has left #openstack-meeting17:00
*** alop has joined #openstack-meeting17:00
*** vishwana_ has joined #openstack-meeting17:01
*** asselin_ has quit IRC17:01
*** SridharRamaswamy has joined #openstack-meeting17:01
*** vishwana_ is now known as vishwanathj_17:01
*** vishwanathj_ has quit IRC17:02
*** vishwana_ has joined #openstack-meeting17:02
*** jseiler has quit IRC17:02
*** vishwana_ is now known as vishwanathj_17:02
*** thingee has left #openstack-meeting17:03
*** hareeshp has joined #openstack-meeting17:03
*** TobiasE1 has joined #openstack-meeting17:03
*** TobiasE has quit IRC17:03
*** eghobo has quit IRC17:04
*** IanGovett has quit IRC17:04
*** jnrao has quit IRC17:04
*** suro_1 has quit IRC17:04
*** evgenyf has quit IRC17:05
*** mfedosin has quit IRC17:05
*** ChuckC_ has quit IRC17:05
*** ChuckC has joined #openstack-meeting17:06
*** chandankumar has quit IRC17:06
*** jlanoux has quit IRC17:06
*** rbak has joined #openstack-meeting17:06
*** MaxV has quit IRC17:07
*** eghobo has joined #openstack-meeting17:08
*** balajiiyer has joined #openstack-meeting17:08
*** patrickeast has quit IRC17:08
*** shashankhegde has quit IRC17:08
*** baoli has quit IRC17:08
*** eghobo has quit IRC17:09
*** nati_ueno has quit IRC17:11
*** aepifanov has quit IRC17:13
*** yamamoto has quit IRC17:13
*** b3nt_pin_nickles is now known as b3nt_pin17:14
*** nati_ueno has joined #openstack-meeting17:15
*** sergsh is now known as sergsh_away17:15
*** markstur has quit IRC17:15
*** mpaolino has quit IRC17:16
*** jorge_munoz has joined #openstack-meeting17:16
*** henrynash has quit IRC17:16
*** drankis has quit IRC17:17
*** mudassirlatif has joined #openstack-meeting17:20
*** vhoward has left #openstack-meeting17:20
*** jorge_munoz has quit IRC17:21
*** zehicle has joined #openstack-meeting17:22
*** Longgeek has quit IRC17:24
*** eglynn-afk is now known as eglynn17:25
*** khaldrogox has joined #openstack-meeting17:25
*** ttrifonov is now known as zz_ttrifonov17:26
*** jorge_munoz has joined #openstack-meeting17:27
*** TobiasE1 has quit IRC17:27
*** atan8 has joined #openstack-meeting17:27
*** alop has quit IRC17:28
*** e0ne has quit IRC17:28
*** balajiiyer has quit IRC17:29
*** marcusvrn has quit IRC17:29
*** chandankumar has joined #openstack-meeting17:31
*** ygbo has quit IRC17:31
*** drankis has joined #openstack-meeting17:32
*** paragan has quit IRC17:34
*** Sukhdev has quit IRC17:34
*** zul has quit IRC17:34
*** andreykurilin_ has quit IRC17:34
*** khaldrogox has quit IRC17:34
*** matrohon has quit IRC17:35
*** zul has joined #openstack-meeting17:35
*** daneyon has joined #openstack-meeting17:36
*** mudassirlatif has quit IRC17:38
*** leeantho has joined #openstack-meeting17:39
*** mfedosin has joined #openstack-meeting17:39
*** chandankumar has quit IRC17:39
*** gokrokve has joined #openstack-meeting17:39
*** baoli has joined #openstack-meeting17:40
*** rmoe has quit IRC17:40
*** jjmb has quit IRC17:41
*** otter768 has joined #openstack-meeting17:41
*** bdpayne has joined #openstack-meeting17:41
*** nati_uen_ has joined #openstack-meeting17:42
*** mudassirlatif has joined #openstack-meeting17:44
*** matel_off is now known as matel17:44
*** sbalukoff has joined #openstack-meeting17:45
*** mattgriffin has joined #openstack-meeting17:45
*** otter768 has quit IRC17:45
*** vishwanathj_ has quit IRC17:45
*** nati_ueno has quit IRC17:46
*** bvandenh has quit IRC17:46
*** nati_uen_ has quit IRC17:47
*** arnaud___ has joined #openstack-meeting17:48
*** IanGovett has joined #openstack-meeting17:51
*** derekh has quit IRC17:58
*** Fdot_ has quit IRC17:58
*** aloga has quit IRC17:59
*** rmoe has joined #openstack-meeting18:00
*** nadya_ has quit IRC18:00
*** pballand has quit IRC18:00
*** pballand has joined #openstack-meeting18:02
*** arnaud___ has quit IRC18:03
*** jjmb has joined #openstack-meeting18:03
*** safchain has quit IRC18:04
*** browne has joined #openstack-meeting18:04
*** harlowja_away is now known as harlowja18:04
*** BharatK has quit IRC18:04
*** ignacio-scopetta has joined #openstack-meeting18:05
*** simon-AS5591 has quit IRC18:05
*** garyk1 has quit IRC18:06
*** igordcard has joined #openstack-meeting18:11
*** mmedvede has quit IRC18:12
*** igordcard has quit IRC18:12
*** igordcard has joined #openstack-meeting18:12
*** e0ne has joined #openstack-meeting18:13
*** mmedvede has joined #openstack-meeting18:13
*** enikher has quit IRC18:14
*** baoli has quit IRC18:15
*** suro_ has joined #openstack-meeting18:15
*** nshaikh has joined #openstack-meeting18:16
*** rhe00 has left #openstack-meeting18:16
*** mchalla has joined #openstack-meeting18:18
*** e0ne has quit IRC18:18
*** harlowja has quit IRC18:18
*** ebalduf has quit IRC18:18
*** harlowja has joined #openstack-meeting18:19
*** gvernik has joined #openstack-meeting18:19
*** e0ne has joined #openstack-meeting18:20
*** padkrish has quit IRC18:21
*** padkrish has joined #openstack-meeting18:22
*** emagana has quit IRC18:23
*** emagana has joined #openstack-meeting18:23
*** emagana has quit IRC18:28
*** SridharRamaswamy has quit IRC18:29
*** e0ne has quit IRC18:29
*** padkrish has quit IRC18:30
*** nadya_ has joined #openstack-meeting18:30
*** vishwana_ has joined #openstack-meeting18:33
*** wuhg has quit IRC18:33
*** arnaud___ has joined #openstack-meeting18:34
*** emagana has joined #openstack-meeting18:34
*** pradk has joined #openstack-meeting18:35
*** ebalduf has joined #openstack-meeting18:35
*** nadya_ has quit IRC18:39
*** andreykurilin_ has joined #openstack-meeting18:39
*** e0ne has joined #openstack-meeting18:40
*** Masahiro has joined #openstack-meeting18:41
*** harlowja_ has joined #openstack-meeting18:41
*** ivar-lazzaro has joined #openstack-meeting18:43
*** changbl has quit IRC18:44
*** e0ne has quit IRC18:44
*** harlowja has quit IRC18:45
*** rushiagr is now known as rushiagr_away18:45
*** alop has joined #openstack-meeting18:46
*** Masahiro has quit IRC18:46
*** colinmcnamara has quit IRC18:49
*** rwsu has quit IRC18:50
*** jhenner has quit IRC18:50
*** SridharRamaswamy has joined #openstack-meeting18:56
*** aepifanov has joined #openstack-meeting18:56
*** pballand has quit IRC18:57
*** yamahata has quit IRC18:59
*** pballand has joined #openstack-meeting18:59
*** padkrish has joined #openstack-meeting18:59
*** acoles has joined #openstack-meeting18:59
*** kota_ has joined #openstack-meeting18:59
*** mahatic has joined #openstack-meeting18:59
notmynameswift meeting time19:00
notmyname#startmeeting swift19:00
openstackMeeting started Wed Nov 26 19:00:24 2014 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: swift)"19:00
openstackThe meeting name has been set to 'swift'19:00
notmynamehello, world19:00
notmynamewho's here for the swift meeting?19:00
kota_o/19:00
gvernikhello19:00
acoles\o19:00
*** johnthetubaguy is now known as zz_johnthetubagu19:01
mahatico/19:01
notmyname#link https://wiki.openstack.org/wiki/Meetings/Swift19:01
notmynamea few things to talk about today19:01
notmynameI know cschwede isn't around19:01
notmynamepeluse: are you here?19:02
notmyname(for later)19:02
*** reed has quit IRC19:02
*** cutforth has joined #openstack-meeting19:02
notmynameand I'm guessing the US thanksgiving is keeping others out19:02
cutforthhello19:02
notmyname#topic testing changes19:02
*** openstack changes topic to "testing changes (Meeting topic: swift)"19:02
* cutforth is glad i got daylight savings sorted out with UTC19:03
notmynamecutforth: :-)19:03
notmynameso...cool stuff in the openstack-infra world that affect us19:03
notmyname#link https://review.openstack.org/#/c/137184/19:03
*** Mandell has joined #openstack-meeting19:03
notmynametl;dr is that the tests run against swift patches should be reduced19:03
claygwhoa - i'm late19:03
*** Mandell has quit IRC19:04
notmynamein the commit message there's a link to the mailing list thread on it19:04
notmynamelooks like it hasn't landed yet, but I'm hoping it will soon19:04
*** Mandell has joined #openstack-meeting19:04
*** pballand has quit IRC19:04
mahaticcool19:04
notmynameI'm hoping this will reduce the chances for swift patches to fail in the check and gate queues. resulting in shorter times to land patches because of less need for "recheck"19:05
notmyname(also, torgomatic bot thanks for posting those comments all the time)19:05
torgomatichehe :)19:05
notmynameany questions about that change?19:05
*** whenry has quit IRC19:06
*** pballand has joined #openstack-meeting19:06
*** tdasilva has joined #openstack-meeting19:06
notmyname#topic swift CLI/SDK changes19:06
*** openstack changes topic to "swift CLI/SDK changes (Meeting topic: swift)"19:06
notmynamethis one is kinda big, and a follow up to what we talked about last week and at the summit19:06
*** pballand has quit IRC19:07
notmynameas a recap....well let me post the link19:07
notmyname#link https://etherpad.openstack.org/p/kilo-swift-swiftclient19:07
notmynamethe bottom of that etherpad is where we've been taking notes on what to do19:07
*** tab___ has joined #openstack-meeting19:07
notmynamethe general plan is to focus new client SDK dev work in openstack-sdk19:07
notmynameI've been talking with that team this week, and mentioned it to ttx yesterday.19:08
claygnotmyname: fwiw i haven't looked at the openstack sdk at all19:08
*** colinmcnamara has joined #openstack-meeting19:08
*** pballand has joined #openstack-meeting19:08
*** browne has quit IRC19:08
*** pballand has quit IRC19:08
notmynameclayg: I have a little. they're is very little there right now for swift19:08
*** jjmb has quit IRC19:08
*** browne has joined #openstack-meeting19:09
notmynamebriancurtin has been most responsive in #openstack-sdks19:09
*** penick has joined #openstack-meeting19:09
claygnotmyname: do they have something that looks like "def api_action(parts, of, the, request, as=parameters): ... return status, headers, body"19:09
claygk, i should hang out in there19:10
notmynameclayg: https://github.com/stackforge/python-openstacksdk/tree/master/openstack/object_store19:10
notmynamethey don't have much at all now19:10
*** pballand has joined #openstack-meeting19:10
claygnotmyname: k, that's probably for the best!19:11
*** pballand has quit IRC19:11
notmyname:-)19:11
claygoh, no, it's OO :\19:11
*** briancurtin has joined #openstack-meeting19:12
claygthat's at least one level too high for where we want to start ;)19:12
notmynamehi briancurtin :-)19:12
briancurtinhey19:12
*** pballand has joined #openstack-meeting19:12
notmynameclayg: I think they'd be happy for us to make it better. so far briancurtin et al have been very receptive to ideas. of course nobody has proposed code yet ;-)19:12
*** andreykurilin_ has quit IRC19:13
swestonasselin: mmedvede the next version of the script is posted.  will be testing it again today.  now, all of the subtree splits are done on a single cloned merge repo.  this will be much easier for us to track and update the history on the entire repository.19:13
claygnotmyname: ack, i should get on that!19:13
*** pballand has quit IRC19:13
claygnotmyname: be nice to get in there before things 1.0 on us19:13
notmynameAFAIK there isn't yet any high-level design for "here's what the SDK must look like". which is good19:13
notmynameclayg: +100019:13
briancurtinyep, not a whole lot is nailed down, it's all fairly malleable, especially at the higher-levels19:14
notmynamebriancurtin: is that true? any existing thing yet?19:14
sweston(sorry, guys, wrong room)19:14
claygsweston: it's cool - we're just hanging out19:14
*** pballand has joined #openstack-meeting19:15
notmynamebriancurtin: cool. great to hear19:15
*** erikmoe has quit IRC19:15
*** bdpayne_ has joined #openstack-meeting19:15
*** pballand has quit IRC19:16
notmynamewe haven't yet discussed how reviews will work for swift stuff in openstack-sdk. ie who reviews, who approves, etc. I want to figure that out when/if it becomes a problem19:16
notmynamebriancurtin: is there anything we should be aware of there?19:16
*** banix has joined #openstack-meeting19:16
claygnotmyname: let's start with patches.19:16
notmynameclayg: right. my thoughts exactly19:16
notmyname:-)19:16
claygk, enough on that then - unless we want to talk tatics of most important patches or design19:16
notmynameanyone else ahve any questions about it?19:17
briancurtinyeah there's not a lot of process here (yet), just want to enable19:17
*** pballand has joined #openstack-meeting19:17
*** pballand has quit IRC19:18
notmynameok, next topic19:18
notmynamethanks for saying hi, briancurtin!19:18
notmyname#topic EC status update19:18
*** openstack changes topic to "EC status update (Meeting topic: swift)"19:18
*** bdpayne has quit IRC19:19
*** briancurtin has left #openstack-meeting19:19
notmynamepeluse: clayg: torgomatic: what's going on with EC this week?19:19
notmynamewhat's top of the list to review?19:19
claygwell you merged the don't store errors in the ring, so we need to merge master and update the node index stuff19:19
torgomaticwell, the error-limiting patch just landed, so that'll make the plumbing better for indexes19:19
claygmerge master, fix node index19:19
torgomaticclayg++19:19
claygyay yay yay!19:19
notmynamegogogogogogogo!19:20
claygafter that sam is going to write a GET path and the whole world is going to change19:20
*** pballand has joined #openstack-meeting19:20
*** jprovazn has quit IRC19:20
*** SridharRamaswamy has quit IRC19:20
*** pballand has quit IRC19:20
torgomaticat a minimum, it'll rotate slightly slower19:20
*** ddieterly has quit IRC19:21
notmynameanyone have any questions on EC?19:21
*** colinmcnamara has quit IRC19:21
claygpeluse: notmyname: torgomatic: I'd acctually like to know how to do the master merge if someone could shoulder surf maybe?19:22
notmynameclayg: ya, I can do that with you today19:22
torgomaticclayg: sure, I'll head over once the meeting is done19:22
*** pballand has joined #openstack-meeting19:22
torgomaticthat's all I have about EC19:22
claygi'm sorta interested in doing more pushing ec refactors into master and merging them back in this round than we did with storage policies - it's something I feel like I could help with19:22
notmynamecool19:22
claygnotmyname: torgomatic: kk19:22
claygthat's it on EC from me19:22
*** pballand has quit IRC19:23
*** reed has joined #openstack-meeting19:23
notmynameok, thanks19:23
notmyname#topic priority reviews19:23
*** openstack changes topic to "priority reviews (Meeting topic: swift)"19:23
notmynameI wanted to ask about a couple19:23
notmynamewhat are we waiting on for fsync() dirs? https://review.openstack.org/#/c/126923/19:23
* clayg yawns19:23
notmynameacoles: tdasilva: ?19:23
acolesi had two queries...19:24
tdasilvanotmyname: ppai has been doing some research on the fsync tree question19:24
notmynameok19:24
*** pballand has joined #openstack-meeting19:24
claygOMG will this patch ever merged?!  https://review.openstack.org/#/c/131238/19:24
acoles1. do we need to run the fsync all the way up a new directory tree or is it sufficient to fysnc the leaf and assume the fs does the rest19:24
tdasilvabut so far he has only found out what i had already posted19:24
tdasilvaour understanding is that because of xfs journaling you only need to do on the leaf19:25
acoles2. is it ok to not worry so much about quarantined objects - proposal is to not fsync their dirs19:25
torgomaticclayg: my recheck-bot's persistence will get it in there eventually19:25
claygacoles: fsyncs are for suckers - we have three copies it'll be fine19:25
tdasilvamaybe torgomatic could also take a lok at that19:25
*** dboik has quit IRC19:25
notmynameclayg: in 3 buffers ;-)19:26
claygtdasilva: maybe *after* EC GET19:26
acolesclayg: lets rip em all out then!)19:26
claygnotmyname: exactly!19:26
* clayg is totally down19:26
*** MaxV has joined #openstack-meeting19:26
torgomaticacoles: I'm much less worried about losing a known-broken thing than a good one, especially if the consequence is that the broken guy stays put until the next auditor run and then gets removed19:26
torgomaticer, quarantined19:26
notmynameacoles: by gut reaction is that quarantines don't need dir fsyncs. they're already known bad19:26
acolestorgomatic: i put an example on the review where the known bad doesnt stay around19:27
acolestorgomatic: notmyname : i'm not digging in on the quarantines but wanted a discussion (so good we're having it)19:27
claygidk, i guess i've seen crazy looking directories that might have been the result of a missing fsync after a put, but it's more likely the missing fsync after a rsync19:27
torgomaticacoles: if the FS loses a file during a rename (using the rename() syscall), the FS is broken19:28
*** bitblt has joined #openstack-meeting19:28
*** banix has quit IRC19:28
torgomaticit's either got to move or not-move... isn't that one of those atomic things?19:28
claygtorgomatic: yeah!19:29
notmynametorgomatic: isn't that FS dependent? but for XFS that's supposed to be true19:29
claygwe could probably put it in and it'll turn out it's a noop that's like maginally more safe on some other filesystem19:29
*** changbl has joined #openstack-meeting19:29
claygacoles: tdasilva: torgomatic: notmyname: the only question is really the benchmark right?19:30
acolestorgomatic: its when you rename to another dir, then fsync the original dir (entry gone) then lose the destination dir19:30
claygwell I guess acoles has other questions19:30
*** bitblt has left #openstack-meeting19:30
notmynametdasilva: so ppai is still doing research?19:30
*** adalbas has quit IRC19:30
notmynameor is that already done and recorded in gerrit?19:30
claygacoles: why do we fsync the /tmp dir?!19:30
*** whenry has joined #openstack-meeting19:30
acolesclayg:?19:30
tdasilvanotmyname: I asked him to ping xfs guys on the question of going up the tree to fsync all the new dirs19:31
clayg.... i thought put's start out (orignal dir) in /tmp19:31
torgomaticacoles: right; I'm saying that if your FS code returns from that fsync() and the file doesn't have a directory entry *somewhere*, the FS is broken19:31
claygwell... /srv/node/sdX/tmp but w/e19:31
*** emagana has quit IRC19:31
tdasilvatorgomatic: yes, that's exactly what I heard from one of our xfs guys19:32
*** vishwana_ has quit IRC19:32
acolesclayg: ah, no the example i found was during replication and quarantining, not PUT path19:32
* clayg feels like he's never gone looking for "complete" uploads in /tmp19:32
tdasilvasame thing about the leaf dir19:32
*** emagana has joined #openstack-meeting19:32
claygreplication!?  I think that almost definately needs less fsyncing that the intial write - i.e. I didn't think a suffix rsync currently had any fsyncing'19:32
acolestorgomatic: what i have read is unclear on that19:32
torgomaticacoles: I see19:33
claygbah, if someone said it's best practice to fsync somewhere, and the code is already written, and we benchmark and it's fine we probably don't have much to argue on do we?19:33
acolesso backing up - the proposed change improves what we have at least! questions i have are whether more is needed19:34
*** AlexF has quit IRC19:34
notmynameacoles: :-)19:34
claygOTOH if we benchmark it and it *sucks* we're probably not going to do it without making it optional19:34
torgomaticacoles: hooray for shipping improvements! :)19:34
*** ddieterly has joined #openstack-meeting19:34
claygacoles: so are you +2 on the change as it stands?19:35
acolesclayg: like you said, some benchmark would be good first, but otherwise yes19:35
notmynamecan anyone else commit to reviewing it?19:36
notmynamehmm...looks like my name is already on it ;-)19:36
*** emagana has quit IRC19:36
*** banix has joined #openstack-meeting19:36
*** ebalduf has quit IRC19:36
notmynameother patch...19:37
notmynamereworking splice/tee https://review.openstack.org/#/c/135319/19:37
notmynamewhat's blocking on that?19:37
notmynametorgomatic: you're +2. so just another reviewer?19:37
notmynameswifterdarrell is on it, but he's out for the rest of the week19:38
* clayg yawns19:38
notmynamethe clayg yawn. kinda like the creiht sigh ;-)19:39
clayga) that's mean19:39
claygb) they're not the same19:39
notmynamelol19:39
clayg;)19:39
notmynametorgomatic: bueller?19:39
torgomaticnotmyname: nothing's blocking on it IIRC19:39
notmynameok, thnaks19:39
notmynameso for you non-USians, if you review it later this week, great! if not, we'll but darrell next week19:40
torgomaticit's a safety improvement; as it stands now, you can write a caller of splice() that scribbles on your process's memory in unexpected and exciting ways19:40
torgomaticwe don't *have* any, but someone could write one19:40
notmynameya, it's a Big Deal (tm) IMO19:40
*** dboik has joined #openstack-meeting19:40
notmynameok, last patch19:40
notmynamethis is FYI19:40
torgomaticso merge https://review.openstack.org/#/c/135319/ and footguns--19:41
notmynamethe defcore stuff has made some progress. this is what the foundation is using to determine what is openstack and what isn't.19:41
notmynamethere's a porposed patch for swift stuff. take a look if you are curious.19:41
notmynamehttps://review.openstack.org/#/c/136677/19:41
notmyname#topic open discussion19:42
*** openstack changes topic to "open discussion (Meeting topic: swift)"19:42
notmynameanything else you want to bring up?19:42
*** otter768 has joined #openstack-meeting19:42
*** mattgriffin has quit IRC19:42
claygnotmyname: it bugs me to know end I can't get probetsts to exit 0 when I have ssync on19:42
torgomaticyes... let me get the link19:42
*** emagana has joined #openstack-meeting19:42
torgomatichttps://review.openstack.org/13331519:43
*** shwetaap1 has quit IRC19:43
clayghttps://review.openstack.org/#/c/136548/19:43
claygoh yeah... that's a good one sam19:43
clayglooks like we need two - i'll take one19:43
torgomaticthere are bytestrings that (a) are invalid UTF-8, (b) py2 accepts them, but (c) py3 doesn't, making objects with those names bad news for Swift's hypothetical py3 future19:44
*** mrda-away is now known as mrda19:44
*** simon-AS559 has joined #openstack-meeting19:44
notmynametorgomatic: there's a whole lot of future. it might in fact have not-python2 in it19:44
claygtorgomatic: we're doing full py3 support right after we add the v1.1 api and rewrite the objet server in go right?19:44
notmynameclayg: sounds about right ;-)19:45
notmynameok, I'll review the unicode one too19:45
notmynameclayg: what do you need on the ssync test one? just another reviewer?19:45
torgomaticwell, when someone talks about rewriting Swift, my usual response starts with "go", so... maybe?19:45
notmynameso cschwede sent me a PM a while back: "Feel free to assign me tasks...."19:46
*** Sukhdev has joined #openstack-meeting19:46
*** simon-AS5591 has joined #openstack-meeting19:46
*** otter768 has quit IRC19:46
acolesnotmyname: yes, I'm already +2 on it (ssync probetest one)19:46
notmynameso, therefore, cschwede can you review https://review.openstack.org/#/c/136548/ please?19:46
notmyname;-)19:46
notmynameanything else to bring up in the meeting this week?19:47
claygnotmyname: yeah, if you use vagrant-swift-all-in-one (or try it out) it's easy enough to set your localrc file to build you an ssync saio and just run probetests on master then again on the patch19:47
tdasilvanotmyname: I also asked cschwede to review the fsync patch19:47
notmynamecschwede: can do all the reviews!19:47
*** colinmcnamara has joined #openstack-meeting19:48
tdasilva:-)19:48
notmynameclayg: cool. good info. thanks19:48
notmynameok, if nothing else, let's adjourn19:48
*** moha_hunt has joined #openstack-meeting19:48
*** simon-AS559 has quit IRC19:48
*** guimaluf has quit IRC19:48
tdasilvahappy thxgiving everyone19:48
notmynamethanks eveyone form attending. have a great rest of the week!19:48
notmyname#endmeeting19:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:48
openstackMeeting ended Wed Nov 26 19:48:52 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2014/swift.2014-11-26-19.00.html19:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2014/swift.2014-11-26-19.00.txt19:48
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2014/swift.2014-11-26-19.00.log.html19:48
*** kota_ has quit IRC19:49
*** clayg has left #openstack-meeting19:49
*** padkrish has quit IRC19:49
*** colinmcnamara has quit IRC19:50
*** mahatic has left #openstack-meeting19:50
*** padkrish has joined #openstack-meeting19:51
*** colinmcnamara has joined #openstack-meeting19:53
*** gvernik has quit IRC19:54
*** cretz has quit IRC19:54
*** rbak_ has joined #openstack-meeting19:55
*** dims has quit IRC19:56
*** ToMiles has joined #openstack-meeting19:56
*** rbak has quit IRC19:56
*** acoles is now known as acoles_away19:57
*** emagana has quit IRC19:59
*** emagana has joined #openstack-meeting19:59
*** radez_g0n3 is now known as radez20:01
*** crc32 has joined #openstack-meeting20:01
*** Mandell has quit IRC20:02
*** Mandell has joined #openstack-meeting20:02
*** emagana has quit IRC20:03
*** SridharRamaswamy has joined #openstack-meeting20:04
*** nadya_ has joined #openstack-meeting20:04
*** novas0x2a|laptop has joined #openstack-meeting20:05
*** b3nt_pin has quit IRC20:05
*** e0ne has joined #openstack-meeting20:06
*** Mandell has quit IRC20:07
*** aysyd has quit IRC20:07
*** penick_ has joined #openstack-meeting20:11
*** hashar has joined #openstack-meeting20:12
*** penick has quit IRC20:13
*** penick_ is now known as penick20:13
*** mchalla has quit IRC20:15
*** beagles has joined #openstack-meeting20:15
*** e0ne has quit IRC20:17
*** crc32 has quit IRC20:19
*** andreykurilin_ has joined #openstack-meeting20:20
*** pballand has quit IRC20:26
*** sarob has quit IRC20:28
*** obondarev has quit IRC20:28
*** enikanorov_ has quit IRC20:28
*** enikanorov_ has joined #openstack-meeting20:28
*** matrohon has joined #openstack-meeting20:29
*** sarob has joined #openstack-meeting20:29
*** obondarev has joined #openstack-meeting20:29
*** Masahiro has joined #openstack-meeting20:30
*** colinmcnamara has quit IRC20:33
*** sarob has quit IRC20:34
*** Masahiro has quit IRC20:34
*** AlexF has joined #openstack-meeting20:34
*** matel has quit IRC20:35
*** baoli has joined #openstack-meeting20:35
*** colinmcnamara has joined #openstack-meeting20:36
*** Mandell has joined #openstack-meeting20:36
*** penick has quit IRC20:37
*** andreykurilin_ has quit IRC20:37
*** ebalduf has joined #openstack-meeting20:37
*** moha_hunt has quit IRC20:37
*** henrynash has joined #openstack-meeting20:38
*** nadya_ has quit IRC20:39
*** ebalduf has quit IRC20:42
*** arunkant has quit IRC20:44
*** padkrish has quit IRC20:48
*** pballand has joined #openstack-meeting20:49
*** bswartz has quit IRC20:54
*** nadya_ has joined #openstack-meeting20:56
*** ajo has quit IRC20:58
*** fnaval has quit IRC20:58
*** AlexF has quit IRC21:01
*** baoli has quit IRC21:01
*** SridharRamaswamy has quit IRC21:01
*** SridharRamaswamy has joined #openstack-meeting21:02
*** baoli has joined #openstack-meeting21:02
*** AlexF has joined #openstack-meeting21:03
*** esker has joined #openstack-meeting21:04
*** esker has quit IRC21:04
*** esker has joined #openstack-meeting21:05
*** nshaikh has left #openstack-meeting21:05
*** ajo has joined #openstack-meeting21:05
*** atan8 has quit IRC21:05
*** tsekiyam_ has joined #openstack-meeting21:06
*** emagana has joined #openstack-meeting21:06
*** IanGovett has quit IRC21:07
*** ajo has quit IRC21:09
*** tsekiyama has quit IRC21:09
*** e0ne has joined #openstack-meeting21:09
*** atan8 has joined #openstack-meeting21:10
*** Sukhdev has quit IRC21:10
*** mtanino has quit IRC21:11
*** tsekiyam_ has quit IRC21:11
*** weshay has quit IRC21:12
*** e0ne has quit IRC21:13
*** sgordon_ has joined #openstack-meeting21:14
*** fnaval has joined #openstack-meeting21:15
*** achanda has joined #openstack-meeting21:15
*** mchalla has joined #openstack-meeting21:16
*** drankis has quit IRC21:16
*** radez is now known as radez_g0n321:17
*** mchalla has quit IRC21:17
*** matrohon has quit IRC21:17
*** jhenner has joined #openstack-meeting21:17
*** Sukhdev has joined #openstack-meeting21:17
*** mchalla has joined #openstack-meeting21:18
*** padkrish has joined #openstack-meeting21:19
*** andreykurilin_ has joined #openstack-meeting21:19
*** achanda has quit IRC21:20
*** pradk has quit IRC21:23
*** ptoohil__ has joined #openstack-meeting21:23
*** ptoohill_ has quit IRC21:23
*** baoli has quit IRC21:24
*** emagana has quit IRC21:24
*** atan8 has quit IRC21:24
*** baoli has joined #openstack-meeting21:24
*** emagana has joined #openstack-meeting21:24
*** nadya_ has quit IRC21:26
*** atan8 has joined #openstack-meeting21:27
*** emagana_ has joined #openstack-meeting21:27
*** emagana has quit IRC21:27
*** jrakerevelant has joined #openstack-meeting21:28
*** padkrish has quit IRC21:28
*** smazziotta has joined #openstack-meeting21:28
*** amitpp has joined #openstack-meeting21:30
*** zaneb has quit IRC21:31
*** emagana has joined #openstack-meeting21:31
*** emagana_ has quit IRC21:31
*** weshay has joined #openstack-meeting21:31
*** ebalduf has joined #openstack-meeting21:35
*** tdasilva has quit IRC21:36
*** dgollub1 has joined #openstack-meeting21:38
*** Riddhi has quit IRC21:40
*** tdasilva has joined #openstack-meeting21:41
*** jehb_ has quit IRC21:42
*** otter768 has joined #openstack-meeting21:43
*** ajo has joined #openstack-meeting21:44
*** Riddhi has joined #openstack-meeting21:45
*** colinmcnamara has quit IRC21:45
*** zaneb has joined #openstack-meeting21:45
*** Guest8638 has quit IRC21:46
*** ian_ott has joined #openstack-meeting21:46
*** tbarron has quit IRC21:46
*** otter768 has quit IRC21:48
*** achanda has joined #openstack-meeting21:48
*** achanda has quit IRC21:49
*** banix has quit IRC21:49
*** jungleboyj has quit IRC21:49
*** Riddhi has quit IRC21:49
*** hareeshp has quit IRC21:50
*** MaxV has quit IRC21:51
*** eglynn_ has joined #openstack-meeting21:51
*** tdasilva has quit IRC21:52
*** eglynn has quit IRC21:53
*** matt__ is now known as mattoliverau21:53
*** BillArnold has quit IRC21:54
*** ajo has quit IRC21:56
*** padkrish has joined #openstack-meeting21:57
*** mchalla has quit IRC21:57
*** amitpp has quit IRC21:58
*** ajo has joined #openstack-meeting21:59
*** Mandell has quit IRC21:59
sgordon_>.>21:59
*** amitry has joined #openstack-meeting22:00
*** ptoohil__ has quit IRC22:00
sgordon_#startmeeting telcowg22:00
openstackMeeting started Wed Nov 26 22:00:21 2014 UTC and is due to finish in 60 minutes.  The chair is sgordon_. Information about MeetBot at http://wiki.debian.org/MeetBot.22:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:00
*** openstack changes topic to " (Meeting topic: telcowg)"22:00
openstackThe meeting name has been set to 'telcowg'22:00
sgordon_#chair amitry22:00
openstackCurrent chairs: amitry sgordon_22:00
*** SridharRamaswam1 has joined #openstack-meeting22:00
sgordon_#topic roll call22:00
*** openstack changes topic to "roll call (Meeting topic: telcowg)"22:00
sgordon_hi all22:00
smazziottahi22:00
sgordon_who is around for the telco working group meeting22:00
ian_otthello...Ian here22:00
*** bertys has joined #openstack-meeting22:00
dgollub1hi22:00
sgordon_recognizing that many will already but off for thanksgiving22:00
*** mchalla has joined #openstack-meeting22:00
sgordon_*be off22:00
*** dgollub1 is now known as dgollub22:01
*** SridharRamaswamy has quit IRC22:01
amitrypresent22:01
*** lhcheng has joined #openstack-meeting22:01
jrakerevelanthi jannis here22:01
sgordon_#topic use cases22:01
*** openstack changes topic to "use cases (Meeting topic: telcowg)"22:01
ian_ottwere the logs from last week posted?22:01
sgordon_yes22:01
sgordon_http://eavesdrop.openstack.org/meetings/telcowg/2014/22:02
sgordon_i also sent them to the operators and developers list22:02
gokrokvehi22:02
*** aveiga has joined #openstack-meeting22:02
ian_ottk maybe the wiki needs an update22:02
*** adrian-hoban_ has joined #openstack-meeting22:02
*** lhcheng_ has joined #openstack-meeting22:03
*** adrian-hoban__ has joined #openstack-meeting22:03
sgordon_so22:03
sgordon_i did some work on the wiki22:03
sgordon_and moved use cases off to here: https://wiki.openstack.org/wiki/TelcoWorkingGroup/UseCases22:03
*** mudassirlatif has quit IRC22:03
sgordon_the current three are a little too mixed probably22:03
*** mudassirlatif has joined #openstack-meeting22:04
sgordon_two VNF use cases and one (vlan trunking) which is effectively a requirement rather than a use case22:04
*** ijw has joined #openstack-meeting22:04
sgordon_though the context the latter came up in was justifying that requirement for neutron22:04
*** ptoohill_ has joined #openstack-meeting22:04
sgordon_#link https://wiki.openstack.org/wiki/TelcoWorkingGroup/UseCases22:04
*** simon-AS5591 has quit IRC22:04
*** r-mibu has joined #openstack-meeting22:05
*** lhcheng has quit IRC22:05
sgordon_there was some discussion about this in #openstack-nfv earlier in the week but i am trying to gauge what level to target the use cases at22:05
sgordon_and how to come up with a meaningful template22:05
sgordon_at the moment what i have is pretty high level/generic to give some freedom:22:05
sgordon_* Title22:05
ian_otti think the wiki previously had the ETSI 8 use cases, the key is to make them relevant to the openstack community22:06
sgordon_* Description22:06
*** lhcheng_ is now known as lhcheng22:06
sgordon_* Characteristics22:06
sgordon_* Requirements22:06
ijwBear in mind use cases don't necessarily drive requirements individually, I think that's a problem we had with the old method - so it's fine to express a use case without trying to solve your openstack problems at the same time22:06
*** colinmcnamara has joined #openstack-meeting22:06
sgordon_right22:06
sgordon_and in fact arguably preferable22:06
aveiga+122:06
*** adrian-hoban_ has quit IRC22:06
aveigait's better for us to distill requirements at a baseline out of multiple use cases that to try to tailor your case to a specific technical function22:07
jrakerevelanta use case might even already possible to implement with openstack as is, correct?22:07
sgordon_part of the problem with the way the ETSI 8 use cases is that they were listed with a very brief one sentence22:07
sgordon_it wasn't really made relevant at all22:07
sgordon_it was just here are the ETSI use cases22:07
aveigajrakerevelant: absolutely22:07
ian_ottsgordon_: agree22:07
sgordon_if they can be made relevant, then i think that would be good22:07
jrakerevelantwe are currently onboarding a vEPC and i will see if there is a use case here22:08
ijwFrequently the changes to Openstack make a use case easier, or better (i.e. improving compute performance) but don't actualy enable it wholesale, I would say22:08
sgordon_right so i think broadly vEPC is a use case not covered in what we have documented today22:08
ijwDepends.  Mainly I'm saying don't write a blueprint in the form of a usecase22:08
aveigaI'd say for the ETSI cases we don't necessarily need them all in OpenStack, either22:08
sgordon_of course not all vEPC are created equal ;)22:08
sgordon_but got to start somewhere22:08
aveigasome of them belong here and some may not22:08
jrakerevelantsgordon_:  agrre22:08
jrakerevelantsgordon_:  agreed22:09
*** AlexF has quit IRC22:09
jrakerevelanti am still trying to figure out how a use case can be general enough, some of the things we encounter is rather: how can I abstract from things like DPDK and SRIOV22:10
sgordon_ijw, right - which i think is effectively what i did when i dumped your vlan trunking justification in as a a use case :/22:10
ijwBad sgordon_22:10
sgordon_:)22:10
sgordon_easily deleted! :P22:10
*** banix has joined #openstack-meeting22:10
*** obondarev has quit IRC22:10
ijwProbably wise, and I'll see if I can get the relevant team to write up the actual use case that justifies it from our perspective22:10
adrian-hoban__Also agree that ETSI-NFV defined use cases are very high level. Where is the link to them now for OpenStack folks if we need to refer back22:10
sgordon_i believe it's in references at the bottom22:11
sgordon_#link http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf22:11
*** obondarev has joined #openstack-meeting22:11
adrian-hoban__sgordon: Thanks, I missed the link22:12
*** banix has quit IRC22:12
*** alexpilotti_ has joined #openstack-meeting22:12
sgordon_jrakerevelant, to your point i think that is why there needs to be a high level description and coverage of characteristics of the workload22:12
*** Mandell has joined #openstack-meeting22:12
jrakerevelantis "virtualizing an IMS" really a use case for us though?22:13
sgordon_and even requirements at a high level22:13
*** dave-mccowan has quit IRC22:13
sgordon_well put it this way22:13
jrakerevelantits rather an application on top22:13
*** alexpilotti_ has quit IRC22:13
sgordon_im now down to two use cases22:13
sgordon_so if you want to cut more then we need people to contribute some ;)22:13
jrakerevelant:)22:13
amitrywe can work on adding some more22:13
sgordon_jrakerevelant, define on top?22:13
amitrymaking openstack suitable to run IMS22:13
jrakerevelantno i dont want to remove it i want know if it is asking the right question22:13
sgordon_from the discussion last week facilitating the workloads that run on top of openstack seemed to be the agreed focus22:13
sgordon_for phase 122:14
aveigasgordon_: I think it should be22:14
sgordon_perhaps i am mis-paraphrasing though22:14
jrakerevelantamitry: right, with clearwater as a reference?22:14
*** mchalla has quit IRC22:14
aveigawe need a target, rather than just to piecemeal implement t echnologies22:14
ijwLook - when it comes down to it a use case really needs to be described by either (a) a vendor with a widget who for whatever reason has some difficulty running it on stock openstack or (b) a telco who has a widget from somewhere and wants to describe what they would *like* to do with it rather than what's possible today22:14
sgordon_ijw, right22:14
sgordon_ijw, and i think both we have atm were cases of (a)22:14
ijwYup22:14
sgordon_which is perfectly fine22:14
ijwaveiga surely must have examples of b22:15
sgordon_but would be great to get a mix of (b)22:15
aveigaijw: we can bring that up a level, widget isn't always the only way to describe it :)22:15
sgordon_#info "ijw> Look - when it comes down to it a use case really needs to be described by either (a) a vendor with a widget who for whatever reason has some difficulty running it on stock openstack or (b) a telco who has a widget from somewhere and wants to describe what they would *like* to do with it rather than what's possible today"22:15
ijwThat's fine, I would expect an operator to have a picture in their mind of what they want to do with it and that's what you need to describe22:15
*** alexpilotti has quit IRC22:15
ijws/with it//22:15
aveigafor instance, I want  to provide X type of service with X technological method22:15
aveigamaybe managed VPNs where I pick MPLS22:16
sgordon_makes sense as a use case in this context i think22:16
aveigaor managed voice where I run a SIP gateway22:16
ijwYup - and use cases are 'I want to provide X type of service' and perhaps a worked example of how you might do it, but if that's the case I think we should expect other people to add to the worked examples or at least quibble with design choices22:16
aveigaI agree22:16
jrakerevelantmy main problem as a telco currently is that vendor X needs technology Y they say22:17
jrakerevelantand Y isnt easy to implement with vanilla openstack22:17
sgordon_i think that is everyone's problem currently :)22:17
ijwAre we good with that?  Stick the 'I want' on the wiki and let people argue the implementation at the bottom or at least pass comment in an etherpad?  Or we could even have a repo with this crap in22:17
aveigayup22:17
jrakerevelantso you start adding balconies that i dont want22:17
sgordon_ijw, right22:17
aveigaijw: I think that's the abstraction we want to start with22:17
sgordon_ijw, i did dig into storyboard a bit this week but for simplicity i would say keep it on the wiki *for now*22:17
ijwjrakerevelant: A fascinating expression, and in that case your use case would be 'a client says they need Y'22:17
aveigathen we can debate the merits of individual implementations at a second level22:18
ijwAt worst, and don't expect much sympathy if you put that in ;)22:18
sgordon_#info Start with "I want" use cases on the wiki and let people argue the implementation at the bottom or at least pass comment in an etherpad22:18
*** ajo has quit IRC22:18
ijwOr perhaps the wrong sort of sympathy ;)22:18
jrakerevelantijw: well, but i dont necessary want to provide Y but an abstraction layer to Y22:18
sgordon_aveiga, agree22:18
*** Masahiro has joined #openstack-meeting22:18
ijwjrakerevelant: Best expressed as 'I want to do Y' and then we can debate the merits of various solutions up to and including changing Openstack22:19
sgordon_right22:19
sgordon_openstack design tenets ultimately favor abstraction of implementation anyway where possible...22:19
ijwOpen source network architecture, this is going to be fun...22:19
jrakerevelantijw: yes probably22:20
sgordon_jrakerevelant, you mentioned a vEPC you are looking to set up earlier22:20
aveigathe basis of it is that either a) OpenStack can do it now with some tweaks, in which case we document the tweaks, b) OpenStack can be made to do it, in which case we write up a BP or c) OpenStack can't be made to do it because the vendor of Y did it wrong, in which case we can't do much about it other than recommend options?22:20
sgordon_jrakerevelant, would you be interested in trying to cover that use case?22:20
adrian-hoban__jrakerevelant: If you add why you need to do Y, then I think it will help folks to understand much more quickly the value22:20
sgordon_=122:21
jrakerevelantsgordon_:  maybe a few weeks in22:21
sgordon_+1 even22:21
ijwaveiga: Even that's useful, but 'it would be much easier if we changed X' is a fine answer to the problem and one we can target.  The 'openstack can do it with config tweaks' solutions tend to involve dedicating your whole cloud to a single application, which is bloody annoying22:21
aveigaijw: I agree, but it's always those damned snowflakes that hold the purse strings...22:21
jrakerevelantsgordon_: we are even struggling to find the most flexible way to integrate physical interfaces like eNode Bs22:21
*** markstur has joined #openstack-meeting22:22
jrakerevelantwe know how to do it in 3 different ways22:22
jrakerevelantbut they all dont feel natural to openstack22:22
ijwaveiga: I know, and true enough, but you're trying to help reduce their infrastructure cost, and they will agree with you after sufficient whisky22:22
*** banix has joined #openstack-meeting22:22
ijwjrakerevelant: Again - 3 solutions and the one you'd like is fine22:22
sgordon_ijw, right - i think documenting the config tweaks approach is more about illustrating how bad the current state is22:23
ijwEasier to pitch the change if there's background information22:23
aveigaijw: I find your ideas intrigueing and would like to subscribe to your newsletter22:23
*** colinmcnamara has quit IRC22:23
ijwaveiga: it's very expensive but comes with whisky22:23
*** Masahiro has quit IRC22:23
aveigajrakerevelant: put them up! No reason not to chat about them, because you may find someone knows a way to make more natural22:23
aveigaand if not, we can figure out which way is the most OpenStack-like (agnostic to forced solutions) and implement that22:24
sgordon_#action sgordon to add a section to top of https://wiki.openstack.org/wiki/TelcoWorkingGroup/UseCases with guidance from this discussion on how to frame use cases22:24
jrakerevelantaveiga: you mean as a use case?22:24
aveigajrakerevelant: absolutely22:24
sgordon_yeah22:24
aveigaone use case,and provide the 3 ways you think it can be done22:24
sgordon_you have an i want22:24
sgordon_:)22:24
ijwAbout time someone started making app design recommendations, in fact.  We kind of short change tenants in favour of cloud operators in the world of Openstack22:24
aveigaand we'll debate the 3 options22:24
adrian-hoban__When we get to BPs for these things, it will be good to document the alternatives too22:24
jrakerevelantsounds good22:24
aveigaadrian-hoban__: agreed22:24
aveigaI don't even think it's wrong to implement multiple methods if they are not mutually exclusive22:25
jrakerevelantput in an action item, i will try to do it until next wednesday22:25
aveigaoptions are good for everyone22:25
sgordon_#action jrakerevelant to document desire to integrate physical interfaces 'like eNode Bs' and current approaches as a use case22:25
sgordon_right i was going to say before22:25
sgordon_some of these things arent mutually exclusive22:25
*** banix has quit IRC22:25
ijwjrakerevelant: as an aside did you see the cloud edge BP?22:25
ijwjrakerevelant: if not go look it up, but we should probably take that out of this meeting22:26
sgordon_and at a high level may be expressed as i need to move packets at a certain rate or w/e22:26
sgordon_but there are different ways to achieve that22:26
jrakerevelantijw: no pleas msg the link, or i google :)22:26
ijwhttps://blueprints.launchpad.net/neutron/+spec/cloud-edge-networking22:26
sgordon_#link https://blueprints.launchpad.net/neutron/+spec/cloud-edge-networking22:26
jrakerevelantyupp found it22:27
jrakerevelantthanks22:27
sgordon_ok22:27
ijw#link https://review.openstack.org/#/c/136555/22:27
sgordon_so it's thanksgiving eve and i am not sensing a wealth of volunteers to throw up use cases22:27
jrakerevelanti just found out i know you ian22:27
sgordon_but i can call out via M/L again22:27
aveigasgordon_: I'll gladly do them, however I am on PTO for the next week...22:27
ijwjrakerevelant: Yeah, I worked out who you were a while back (but your name is a little more obvious ;)22:28
sgordon_#action sgordon to issue call for use cases via M/L once UseCases page updated22:28
sgordon_aveiga, np - it's more i want to make sure we capture a broad spectrum if possible22:28
aveigaabsolutely22:28
ijwOK, there are three BPs worth checking, that one and the revenge of VLANs22:28
*** sergef has quit IRC22:28
aveigaand once I'm back, someone gently nudge me with a big stick22:28
aveiga;)22:28
ijwWe having a section on that?22:28
jrakerevelantwhats the revenge of the vlans??22:28
sgordon_a new hope22:29
*** mrmartin has quit IRC22:29
ijwThat wasn't a sequel22:29
aveigaBOOOOO22:29
sgordon_ijw, the vlans?22:29
*** zaneb has quit IRC22:29
sgordon_sure why not22:29
*** colinmcnamara has joined #openstack-meeting22:29
sgordon_#topic vlan trunking redux22:29
*** openstack changes topic to "vlan trunking redux (Meeting topic: telcowg)"22:29
ijwhttps://blueprints.launchpad.net/neutron/+spec/nfv-vlan-trunks22:29
sgordon_#link https://blueprints.launchpad.net/neutron/+spec/nfv-vlan-trunks22:29
ijwhttps://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms22:30
sgordon_i briefly caught the discussion you had with amuller about it y'day in the neutron channel22:30
sgordon_#link https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms22:30
ijwHaven't checked the latter but I think Erik was facing Maru's -2 and Maru had somehow managed to miss that we want both to go through22:30
jrakerevelanti heard vlans are evil22:30
jrakerevelant;)22:30
ijwIt's a horror movie sequel22:30
*** jungleboyj has joined #openstack-meeting22:30
aveigaoh man am I in the wrong company22:30
* aveiga likes 802.1q22:31
*** ChrisPriceAB has quit IRC22:31
ijwaveiga: ipv6 is the answer, you know.  Now what's the question again?22:31
aveigaijw: it always is22:31
jrakerevelantijw: is it a requirement for legacy applications?22:31
ijwjrakerevelant: VLANs?22:31
* sgordon_ struggles to find the spec link for erics22:31
aveigajrakerevelant: no, there are soome newer things that need it too22:31
aveigai.e. MT-ISIS peers...22:31
ijwPartly yes, we expect to face VMs that like them, and partly no, we also and independently of NFV expect there to be VMs with lots and lots of network connections22:32
sgordon_#link https://review.openstack.org/#/c/136554/22:32
ijwThe former is more the VLAN trunk thing, the latter is more the port thing22:32
sgordon_urgh that's yours :)22:32
ijwBut the line is faint and easy to cross, in both directions22:32
aveigaijw: the latter is the one I expect to see as a big deal, but also in an addresses-per-port issue as well22:32
ijwYup, and Erik's spec addresses the port addressing22:33
ijwThe former annoys me more, but that's a matter of what I face more often.  We need both, that's all I'll say on the subject22:33
sgordon_#link https://review.openstack.org/#/c/94612/22:33
ijwI suspect when we have them we will want to tweak them, but this time we need to make a concerted effort - all of us - to keep on top of the specs, review and criticise them, and then do the same for the code.22:34
ijwI am as guilty as anyone of this, but fast turnarounds, please22:34
*** lhcheng has quit IRC22:34
sgordon_#info specs are up for review and need concerted review bandwidth and turnarounds22:35
jrakerevelanti think i am not the right person to judge if "we" need sth like that, so i trust in you guys22:35
sgordon_#action sgordon to ask maru about -2 on https://review.openstack.org/#/c/94612/22:35
ijwThe spec you don't have yet because I got a bit tied up in the details is the one for MTU specification and discovery - sorta kinda NFV related, for some applications (including one I have to deal with) and an annoyance to cloud users in general, too22:35
*** daneyon has quit IRC22:35
aveiga+122:35
adrian-hoban__Are these all captured on the wiki too?22:35
*** lhcheng has joined #openstack-meeting22:35
ijwjrakerevelant: read it anyway, the worst that will happen is you don't vote22:35
*** atan8 has quit IRC22:35
aveigaadrian-hoban__: no, because right now they're not use cases22:35
aveigathey're potential solutions22:36
aveigabut I intend to add some use cases that may need some of them22:36
sgordon_#info ijw working on spec for MTU specification and discovery22:36
ijwsgordon_: other than that I think there were about 5 or so libvirt/KVM BPs mentioned in the summit Nova session, and I admit I've not been following them too closely22:36
sgordon_yeah they are still progressing22:36
jrakerevelantijw: I'll lool into it22:36
sgordon_lot of back and forth about the data model22:36
sgordon_and still of course the issue of CI which i need to chase down22:36
sgordon_there seemed to be some indication we may in fact be able to demonstrate them on HP Cloud infra at least22:37
ijw... with me, I think, but I need to check with the opnfv guys about the hardware to be provided and bugger about with cobbler22:37
adrian-hoban__Intel reps are starting to engage with the Infrastructure team now to get our CI in place22:37
sgordon_yeah22:37
aveigathis is good news22:37
sgordon_seems to be lots of hardware22:37
ijwsgordon_: I think we want both physical and virtual but virtual would be a real win even if it's not perfect22:37
sgordon_trying to nail down a resource to "own" it22:37
sgordon_right22:37
sgordon_i still think we would need physical to demo the stuff adrian-hoban__'s team are working on with device locality22:38
sgordon_i could be wrong though22:38
*** mchalla has joined #openstack-meeting22:38
aveigaactually, that's a good point.  We should caveat that use cases asking for X performance rates may not be verifiable on all OpenStack CI systems22:38
jrakerevelantijw: what are the requirements on the virtual setup?22:38
aveigaand therefore YMMV22:38
sgordon_but being able to get some of the other stuff into the gate rather than third party would be win22:38
ijwvhostuser is still an issue, we need a spec in Neutron again to get the Nova guys to agree to use it, and for that we need a controller that causes it to be used (even if it's not gating)22:38
*** ebalduf has quit IRC22:38
adrian-hoban__sgordon: Yep, I think we need physical for a few of the items22:38
ijwjrakerevelant: Not the expert, but there's a ML thread with Dan Berrange that describes their thinking22:39
sgordon_#info use cases caveats need to be added around ability of OpenStack CI to measure certain performance rate requirements etc.22:39
jrakerevelantijw: could you dig up the link maybe?22:39
sgordon_jrakerevelant, basically you can actually expose a numa topology on libvirt/kvm22:39
adrian-hoban__ijw: we're working up some plans on the vhost-user. Watch this space22:40
sgordon_jrakerevelant, the key is whether we can orchestrate this on one of the clouds infra uses (or ideally both)22:40
ijwadrian-hoban__: Get it in, man ;)22:40
sgordon_grabbing link22:40
jrakerevelantsgordon_: ok22:40
sgordon_i actually have someone who can help with that if needed adrian-hoban__22:40
*** cutforth has left #openstack-meeting22:41
sgordon_though i think to ijw's point key is what if anything is done on the neutron side22:41
sgordon_to ensure we can test it22:41
ijwhttp://osdir.com/ml/openstack-dev/2014-11/msg00602.html is the thread for testing22:41
adrian-hoban__sgordon_: Would welcome that. Thanks22:41
jrakerevelantijw: awesome thanks22:41
*** zaneb has joined #openstack-meeting22:41
sgordon_#link http://lists.openstack.org/pipermail/openstack-dev/2014-November/050469.html22:41
sgordon_jrakerevelant, ^22:41
ijwthat too22:42
*** weshay has quit IRC22:42
ijwOK, so any more specs of interest right now?  I know what I know, other people must also have opinions22:42
*** banix has joined #openstack-meeting22:42
sgordon_#link https://review.openstack.org/#/c/128825/22:43
sgordon_this recently picked up a -2, trying to explain the logic atm22:43
sgordon_topic is optimizing virtio-net multiqueue usage22:43
ijw(virtio-net multiqueue - enhanced networking speed for supporting VMs)22:43
ijwWas that the one where Dan said that there's a limit on the number of queues per host, at the summit?22:44
ijwdanpb, that would be22:44
sgordon_per guest i think22:44
sgordon_but yeah22:44
adrian-hoban__ijw: Yep I think so22:45
aveigathat could get tricky at the scheduling level...22:45
ijwI wonder if that also aplies to singlequeue, in which case we probably have a repair job to do to the way nova schedules and should raise a bug22:45
sgordon_vladik wasn't actually at the summit so dan and i were trying to explain it on his behalf22:45
*** alexpilotti has joined #openstack-meeting22:45
*** Mandell has quit IRC22:46
ijwOK, can you get the details from Vladik?  Cos we should definitely check if that has wider implications, for starters22:46
*** EmilienM has quit IRC22:47
sgordon_mmm22:47
sgordon_are you saying in terms of it being a finite resource?22:47
sgordon_as my understanding is there is a limit of # of queues per guest22:47
sgordon_not a per host limit22:47
*** EmilienM has joined #openstack-meeting22:47
adrian-hoban__queues and MSIx22:48
sgordon_yeah22:48
sgordon_both guest side though afaik22:48
*** banix has quit IRC22:49
sgordon_while we're at it, and because i want aveiga to go on his PTO made with me22:49
*** SridharRamaswamy has joined #openstack-meeting22:49
sgordon_PXE boot was raised on the M/L again22:49
sgordon_#link http://lists.openstack.org/pipermail/openstack-dev/2014-November/051561.html22:49
*** SridharRamaswam1 has quit IRC22:49
sgordon_question is whether in a cloud world that makes sense versus a PXE image in glance22:50
*** achanda has joined #openstack-meeting22:50
*** stevemar has quit IRC22:50
*** ian_ott has quit IRC22:50
sgordon_monty also suggested on M/L that ironic already has PXE support (which im sure it does) that is driven by nova22:50
aveigaI still don't see a reason to do this22:50
ijwI don't have a use case, but we've used an iPXE image to boot a 'diskless' VM and that works just fine, albeit it has one disk.22:51
sgordon_it's unclear22:51
jrakerevelanti dont see the use case22:51
aveigaI mean, if you're going to PXE boot something *not* in OpenStack, ok...22:51
sgordon_i'd prefer to see a use case22:51
jrakerevelanti mean in a telco specific way22:51
sgordon_everyone i have talked to about it has ended up putting the image in glance and being fine with it22:51
ijwIronic is using PXE for entirely different and non-tenant-facing reasons and I don't think that's pertinent22:51
sgordon_ijw, yeah that was my thought....22:51
aveigaI can see needing to provide PXE services to outside devices22:52
sgordon_mmm22:52
sgordon_do we necessarily stop that though?22:52
aveigaI mean, booting a thin client farm that connects to a "remote desktop" farm?22:52
clarkbijw: I think its pertinent in that ironic could maybe boot your VMs for you (which may be what mordred was getting at)22:52
ijwI presume the request is 'I want a machine with 0 disks and for it to load all it state into a RAMdisk from a remote server' and you can take that as meaning that you the tenant will provide the server or you want the system to do it for you, I guess22:52
aveigasgordon_: yes, we block DHCP for good reason22:52
ijwI've done it with a tenant server.22:52
sgordon_aveiga, you are no fun at all today22:52
sgordon_;p22:52
aveigait's snowing here, so I'm passing along the pain :)22:53
ijwaveiga: Oh, god, the firewalling stuff, that's another can of worms we should at least mention so it's saved for next tie22:53
sgordon_ijw, yeah22:53
aveigaijw: +122:53
sgordon_in the simplest case the tenant imo22:53
sgordon_but still22:53
aveigathe implicit filtering stuff can be a pain for NFV uses22:53
* sgordon_ shelves that22:53
aveiganecessary for shared clouds though22:53
ijwsgordon_: let's get whoever it is to clarify their use case22:53
ijwaveiga: there are at least two BPs, hence can of worms22:53
sgordon_#info PXE, much confusion, need documented use case22:54
aveigaah22:54
sgordon_ok so i had three more items22:54
sgordon_i locked in the meeting time, obviously we're here so goodo22:54
ijwRun, Forrest, run!22:54
*** Riddhi has joined #openstack-meeting22:54
sgordon_jannis added a glossary22:54
sgordon_#link https://wiki.openstack.org/w/index.php?title=TelcoWorkingGroup/Glossary&action=edit&redlink=122:54
sgordon_or at least a placeholder for one22:55
sgordon_and finally last weeks hot topic22:55
ijwI like that glossary as it is22:55
sgordon_#topic orchestration22:55
*** openstack changes topic to "orchestration (Meeting topic: telcowg)"22:55
sgordon_mkoderer, still around22:55
sgordon_?22:55
ijwI think it sums up the problem nicely22:55
*** achanda has quit IRC22:55
sgordon_#link http://lists.openstack.org/pipermail/openstack-dev/2014-November/051473.html22:55
sgordon_ijw, it needs one of those mental puzzle images22:55
jrakerevelantsgordon_: yeah i didnt know what to put in there yer22:56
sgordon_mkoderer took an action to kick off a thread about orchestration and keep working on the etherpad last week22:56
sgordon_that happened22:56
aveigaI'm actually really curious as to where we think the line should be drawn for NFV orchestration within OpenStack22:56
sgordon_from a use cases perspective we determine that wasn't the initial focus22:56
*** hareeshp has joined #openstack-meeting22:56
sgordon_*determined22:56
sgordon_aveiga, right22:56
aveigaI mean, we don't expect OpenStack to orchestrate network gear outside of the stack, right?22:56
sgordon_aveiga, well - i dont22:56
*** Ark has joined #openstack-meeting22:56
aveigaI certainly don't want OpenStack (no offense) to manipulate my routers...22:56
sgordon_but i am but one man!22:56
ijwaveiga: Well, I think there are two questions, really22:56
sgordon_and what about tripleo...22:57
* sgordon_ ducks22:57
*** Ark is now known as Guest5107522:57
ijwaveiga: clearly, anything that is 'a part of the cloud' and not an individual device needs a cloud API, implying Openstack, to make it do stuff and things22:57
aveigathat's the point of heat22:57
sgordon_yeah22:57
ijwaveiga: that aside, how do you start and restart your VMs, configure them, etc?  That could be Heat or a similar aaS offering - which is not the very minimal core of Openstack, but it is Openstack - or it could be an application.  I suspect both cases are relevant and required22:58
sgordon_and i think zane or someone expressed interest from a heat perspective on the thread22:58
sgordon_like everyone they need use cases though22:58
ijwaveiga: it's not really - Heat tells other services what to do22:58
*** banix has joined #openstack-meeting22:58
aveigaijw: exactly.  What I'm getting at is we should provide an ETSI orchestration tool with the northbound interface of OpenStack22:58
ijwaveiga: so if I had some random (potentially virtualisable) network device that made my VNFs 10x sexier, then I would expect there to be some service - perhaps a new one - to orchestrate it, then I would expect Heat to boss it about22:59
aveigaI don't think we should be in the business of building the tools to orchestrate everything including the xternal systems22:59
*** JRobinson__ has joined #openstack-meeting22:59
ijwaveiga: +1, I totally agree with that22:59
aveigaijw: that's totally fine, but wouldn't that network device's interface to OpenStack bee a third party driver?22:59
aveigawe have ways of building those already22:59
ijwDepends what it does22:59
ijwIt may have a totally new and shiny API, in which case it's probably a new endpoint (which is also fine, imo)23:00
sgordon_the other project that came up on that thread was murano23:00
aveigayeah, but I have yet to see anything that requires that much more of OpenStack than we already provide23:00
*** Mandell has joined #openstack-meeting23:00
sgordon_but of course that is still very inwardly openstack-focussed23:00
sgordon_not external systems23:00
adrian-hoban__I agree from the perspective of offering the right level of configuration & control capabilities, but not necessarily innate knowledge of the service23:00
aveigawith the exception of being able to manipulate neutron for connecting to external netionworks in a custom fash23:00
aveigaadrian-hoban__: we need at least a little, otherwise you can't properly service chain23:00
ijwThe 'keep-your-app-running' element of orchestration definitely includes Murano23:00
*** ebalduf has joined #openstack-meeting23:00
*** hareeshp has quit IRC23:01
*** Guest51075 has quit IRC23:01
sgordon_#info defining what NFV orchestration really means in an openstack-specific way continues to be a challenge :)23:01
*** mchalla has quit IRC23:01
sgordon_ijw, +123:01
*** tsekiyama has joined #openstack-meeting23:01
aveigayup23:01
jrakerevelantagree23:01
sgordon_ok we're at time for today23:01
sgordon_those of you in the US enjoy your thanksgiving23:02
ijwI think I would at least split the definition into 'internal' and 'external' orchestration, for want of a better word.  One provides a cloud API to something that is not itself cloudy (a widget, a server) and one looks after applications23:02
sgordon_#info "ijw>  split the definition into 'internal' and 'external' orchestration, for want of a better word.  One provides a cloud API to something that is not itself cloudy (a widget, a server) and one looks after applications"23:02
ijw(via published APIs, generally)23:02
sgordon_i think that's accurate to the discussion we were having above23:02
*** jungleboyj has quit IRC23:03
sgordon_#endmeeting23:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:03
openstackMeeting ended Wed Nov 26 23:03:04 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/telcowg/2014/telcowg.2014-11-26-22.00.html23:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/telcowg/2014/telcowg.2014-11-26-22.00.txt23:03
openstackLog:            http://eavesdrop.openstack.org/meetings/telcowg/2014/telcowg.2014-11-26-22.00.log.html23:03
ijwDid we do stuff?23:03
ijwI think we may have done stuff23:03
sgordon_i *think* so23:03
*** jungleboyj has joined #openstack-meeting23:03
sgordon_:)23:03
jrakerevelantijw: i dont know23:03
sgordon_still the use case contribution is key to everything23:03
ijwJust +1 all my specs and I'll call it a win ;)23:03
jrakerevelanti will try my best23:03
sgordon_so i will try add some of the guidance we discussed23:03
sgordon_and send another email calling for contribs23:03
aveigathanks everyone23:03
smazziottabye23:03
jrakerevelantthanks23:03
adrian-hoban__Thanks folks23:03
aveigaI'm off (at a wedding) next week, so see you all in two23:04
ijwcheers23:04
amitrythanks, happy holidays to those who are celebrating23:04
ijwYeah, and at 6am I'm in bed23:04
ijw(thanks a lot, sgordon_)23:04
*** igordcard has quit IRC23:04
adrian-hoban__aveiga: Have fun!23:04
*** aveiga has left #openstack-meeting23:04
jrakerevelantit 6 am??23:04
ijwPST, yes23:04
jrakerevelantsomewhere in the world23:04
ijwCos sgordon_ hates me23:04
*** mchalla has joined #openstack-meeting23:04
ijwI can tell by that and the ninja assassings23:04
jrakerevelantah next wednesday you mean23:04
ijwyup23:05
*** amitry has quit IRC23:05
jrakerevelantijw: are u still working with DT?23:05
sgordon_all in favor of making the meetings earlier?23:05
sgordon_:P23:05
*** ebalduf has quit IRC23:05
ijwNot as much as I used to, but I do talk to you23:05
*** mchalla has quit IRC23:05
ijwor, them, or however you call it23:05
*** ddieterly has quit IRC23:05
jrakerevelant:)23:06
*** ddieterly has joined #openstack-meeting23:06
*** tab___ has quit IRC23:07
*** r-mibu has quit IRC23:07
*** MarkAtwood has quit IRC23:08
*** dgollub has left #openstack-meeting23:08
*** bertys has quit IRC23:09
*** ijw has quit IRC23:09
*** smazziotta has quit IRC23:10
*** SumitNaiksatam has quit IRC23:10
*** SumitNaiksatam has joined #openstack-meeting23:10
*** ddieterly has quit IRC23:11
*** suro_ has quit IRC23:11
*** mudassirlatif has quit IRC23:12
*** browne has quit IRC23:13
*** SridharRamaswamy has quit IRC23:14
*** mudassirlatif has joined #openstack-meeting23:15
*** colinmcnamara has quit IRC23:16
*** jrakerevelant has quit IRC23:17
*** Sukhdev has quit IRC23:17
*** mudassirlatif has quit IRC23:20
*** aepifanov has quit IRC23:20
*** andreykurilin_ has quit IRC23:22
*** adrian-hoban__ has quit IRC23:23
*** dboik has quit IRC23:24
*** padkrish has quit IRC23:25
*** adahms has joined #openstack-meeting23:26
*** gokrokve has quit IRC23:27
*** SridharRamaswamy has joined #openstack-meeting23:29
*** colinmcnamara has joined #openstack-meeting23:31
*** jungleboyj has quit IRC23:33
*** pballand has quit IRC23:35
*** mudassirlatif has joined #openstack-meeting23:36
*** resker has joined #openstack-meeting23:38
*** dave-mccowan has joined #openstack-meeting23:38
*** resker has quit IRC23:38
*** shashankhegde has joined #openstack-meeting23:41
*** banix has quit IRC23:42
*** esker has quit IRC23:42
*** SumitNaiksatam has quit IRC23:42
*** banix has joined #openstack-meeting23:42
*** otter768 has joined #openstack-meeting23:44
*** baoli has quit IRC23:44
*** tochi has joined #openstack-meeting23:44
*** baoli has joined #openstack-meeting23:45
*** colinmcnamara has quit IRC23:47
*** Mandell has quit IRC23:48
*** otter768 has quit IRC23:49
*** SumitNaiksatam has joined #openstack-meeting23:49
*** Mandell has joined #openstack-meeting23:49
*** tsekiyama has quit IRC23:52
*** hashar has quit IRC23:54
*** suro_ has joined #openstack-meeting23:55
*** banix has quit IRC23:56
*** Mandell has quit IRC23:57
*** marun has quit IRC23:57
*** colinmcnamara has joined #openstack-meeting23:58

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