Wednesday, 2013-12-11

*** jcooley_ has quit IRC00:02
*** jcooley_ has joined #openstack-meeting00:02
*** lexx has quit IRC00:03
*** yamahata_ has quit IRC00:04
*** gokrokve has quit IRC00:04
*** fbo is now known as fbo_away00:04
*** gokrokve has joined #openstack-meeting00:05
*** pablosan has quit IRC00:05
*** jcooley_ has quit IRC00:07
*** epim has quit IRC00:07
*** lblanchard has quit IRC00:08
*** gokrokve has quit IRC00:09
*** epim has joined #openstack-meeting00:12
*** lblanchard has joined #openstack-meeting00:12
*** jcooley_ has joined #openstack-meeting00:13
*** jcooley_ has quit IRC00:13
*** jcooley_ has joined #openstack-meeting00:13
*** fnaval has quit IRC00:14
*** rudrarugge has joined #openstack-meeting00:15
*** samcdona has quit IRC00:16
*** jcooley_ has quit IRC00:18
*** MaxV has joined #openstack-meeting00:19
*** herndon has quit IRC00:21
*** rudrarug_ has joined #openstack-meeting00:24
*** rudrarugge has quit IRC00:24
*** otherwiseguy has quit IRC00:25
*** banix has quit IRC00:26
*** vkmc has quit IRC00:28
*** bdpayne has quit IRC00:30
*** salv-orlando has joined #openstack-meeting00:30
*** rakhmerov has joined #openstack-meeting00:30
*** MaxV has quit IRC00:31
*** bdpayne has joined #openstack-meeting00:31
*** rudrarug_ has quit IRC00:33
*** stevemar has joined #openstack-meeting00:34
*** sarob has joined #openstack-meeting00:34
*** hemna has quit IRC00:37
*** NehaV has joined #openstack-meeting00:37
*** hemna has joined #openstack-meeting00:41
*** lbragstad has joined #openstack-meeting00:42
*** hemna has quit IRC00:42
*** elo1 has quit IRC00:45
*** _ozstacker_ has joined #openstack-meeting00:45
*** cyeoh_ has joined #openstack-meeting00:46
*** cyeoh_ is now known as cyeoh00:46
*** epim has quit IRC00:46
*** dims has joined #openstack-meeting00:46
*** salv-orlando has quit IRC00:46
*** hemna has joined #openstack-meeting00:47
*** sarob has quit IRC00:48
*** ozstacker has quit IRC00:49
*** sarob has joined #openstack-meeting00:49
*** lbragstad has quit IRC00:49
*** gokrokve has joined #openstack-meeting00:49
*** electrichead has joined #openstack-meeting00:52
*** sarob has quit IRC00:53
*** lbragstad has joined #openstack-meeting00:54
*** yamahata_ has joined #openstack-meeting00:55
*** lbragstad has quit IRC00:55
*** yamahata_ has quit IRC00:55
*** yamahata_ has joined #openstack-meeting00:56
*** anniec has quit IRC01:03
*** rakhmerov has quit IRC01:04
*** venkatesh has joined #openstack-meeting01:04
*** bdpayne has quit IRC01:05
*** hemna is now known as hemnafk01:05
*** mrodden has joined #openstack-meeting01:05
*** jhenner has quit IRC01:07
*** sandywalsh_ has quit IRC01:09
*** julim has joined #openstack-meeting01:09
*** eharney has quit IRC01:15
*** oubiwan__ has joined #openstack-meeting01:17
*** samcdona has joined #openstack-meeting01:19
*** sandywalsh_ has joined #openstack-meeting01:21
*** dims has quit IRC01:21
*** SumitNaiksatam has quit IRC01:21
*** sarob has joined #openstack-meeting01:23
*** salv-orlando has joined #openstack-meeting01:25
*** s0mik has quit IRC01:26
*** s0mik has joined #openstack-meeting01:28
*** sarob has quit IRC01:28
*** salv-orlando has quit IRC01:28
*** nosnos has joined #openstack-meeting01:29
*** salv-orlando has joined #openstack-meeting01:29
*** otherwiseguy has joined #openstack-meeting01:32
*** yaguang has joined #openstack-meeting01:33
*** s0mik has quit IRC01:36
*** dims has joined #openstack-meeting01:36
*** julim has quit IRC01:40
*** IlyaE has quit IRC01:43
*** dguitarbite has joined #openstack-meeting01:44
*** SumitNaiksatam has joined #openstack-meeting01:45
*** michchap_ has quit IRC01:46
*** sarob has joined #openstack-meeting01:47
*** nermina has joined #openstack-meeting01:47
*** michchap has joined #openstack-meeting01:47
*** SumitNaiksatam has quit IRC01:55
*** bgorski has quit IRC01:57
*** banix has joined #openstack-meeting01:58
*** reed has quit IRC01:58
*** Jianyong has joined #openstack-meeting01:59
*** herndon has joined #openstack-meeting02:00
*** rakhmerov has joined #openstack-meeting02:00
*** rongze has joined #openstack-meeting02:01
*** AaronGr is now known as AaronGr_Zzz02:03
*** jcooley_ has joined #openstack-meeting02:04
*** rakhmerov has quit IRC02:05
*** zhikunliu has joined #openstack-meeting02:07
*** gokrokve has quit IRC02:08
*** gokrokve has joined #openstack-meeting02:08
*** nermina has quit IRC02:09
*** gokrokve has quit IRC02:13
*** ryanpetrello has quit IRC02:17
*** banix has quit IRC02:19
*** colinmcnamara has quit IRC02:20
*** colinmcn_ has quit IRC02:20
*** herndon has quit IRC02:20
*** gokrokve has joined #openstack-meeting02:21
*** banix has joined #openstack-meeting02:22
*** Mandell has quit IRC02:24
*** banix has quit IRC02:24
*** banix has joined #openstack-meeting02:25
*** comay has quit IRC02:26
*** topshare has joined #openstack-meeting02:27
*** ryanpetrello has joined #openstack-meeting02:28
*** sarob has quit IRC02:29
*** banix has quit IRC02:30
*** sarob has joined #openstack-meeting02:30
*** nermina has joined #openstack-meeting02:31
*** rongze has quit IRC02:31
*** banix has joined #openstack-meeting02:31
*** radsy has quit IRC02:33
*** radix_ has quit IRC02:33
*** sarob_ has joined #openstack-meeting02:34
*** sarob has quit IRC02:35
*** NehaV has quit IRC02:37
*** krotscheck has quit IRC02:37
*** maxdml has joined #openstack-meeting02:40
*** venkatesh has quit IRC02:40
*** hua has quit IRC02:42
*** zhhuabj has joined #openstack-meeting02:42
*** epico has joined #openstack-meeting02:42
*** zhhuabj has joined #openstack-meeting02:42
*** zhhuabj has quit IRC02:43
*** zhhuabj has joined #openstack-meeting02:43
*** jcooley_ has quit IRC02:43
*** saurabh_ has left #openstack-meeting02:44
*** fnaval has joined #openstack-meeting02:44
*** nermina has quit IRC02:45
*** rongze has joined #openstack-meeting02:46
*** paragan has joined #openstack-meeting02:47
*** SumitNaiksatam has joined #openstack-meeting02:49
*** lbragstad has joined #openstack-meeting02:49
*** cyclicflux has joined #openstack-meeting02:51
*** sarob_ is now known as sarob02:51
*** _ozstacker_ has quit IRC02:53
*** nati_ueno has quit IRC02:54
*** cyclicflux has quit IRC02:56
*** fnaval has quit IRC02:58
*** marun has joined #openstack-meeting03:00
*** rakhmerov has joined #openstack-meeting03:01
*** maxdml has quit IRC03:03
*** maxdml has joined #openstack-meeting03:05
*** ozstacker has joined #openstack-meeting03:05
*** zhikunliu has quit IRC03:05
*** sarob has quit IRC03:06
*** galstrom_zzz is now known as galstrom03:06
*** sarob has joined #openstack-meeting03:06
*** zhikunliu has joined #openstack-meeting03:07
*** topshare has quit IRC03:10
*** ryanpetrello has quit IRC03:11
*** sarob has quit IRC03:11
*** coolsvap has joined #openstack-meeting03:17
*** AaronGr_Zzz is now known as AaronGr03:19
*** markwash has quit IRC03:21
*** suo__ has joined #openstack-meeting03:23
*** lblanchard has quit IRC03:32
*** maxdml has quit IRC03:33
*** radsy has joined #openstack-meeting03:38
*** galstrom is now known as galstrom_zzz03:45
*** hill has joined #openstack-meeting03:48
*** hill is now known as Guest9562003:49
*** neelashah has joined #openstack-meeting03:49
*** haomaiwang has joined #openstack-meeting03:52
*** gyee has quit IRC03:55
*** stevemar2 has joined #openstack-meeting03:58
*** stevemar has quit IRC04:01
*** mdomsch has joined #openstack-meeting04:04
*** Guest95620 has quit IRC04:05
*** zhikunliu has quit IRC04:14
*** SergeyLukjanov has joined #openstack-meeting04:17
*** haomaiwa_ has joined #openstack-meeting04:20
*** haomaiwang has quit IRC04:20
*** SergeyLukjanov has quit IRC04:21
*** dstanek_afk has joined #openstack-meeting04:22
*** ItSANg___ has joined #openstack-meeting04:22
*** ArxCruz has quit IRC04:22
*** skraynev_ has joined #openstack-meeting04:24
*** ArxCruz has joined #openstack-meeting04:24
*** acoles has quit IRC04:24
*** markwash has joined #openstack-meeting04:24
*** hemna_ has joined #openstack-meeting04:24
*** ItSANgo has quit IRC04:24
*** skraynev has quit IRC04:24
*** zhhuabj has quit IRC04:24
*** yamahata_ has quit IRC04:24
*** hemnafk has quit IRC04:24
*** dstanek has quit IRC04:24
*** plomakin has quit IRC04:24
*** hemna_ has quit IRC04:24
*** hemna_ has joined #openstack-meeting04:24
*** acoles has joined #openstack-meeting04:25
*** plomakin has joined #openstack-meeting04:25
*** ItSANg___ has quit IRC04:26
*** dguitarbite has quit IRC04:27
*** SergeyLukjanov has joined #openstack-meeting04:27
*** yamahata_ has joined #openstack-meeting04:28
*** ssurana has joined #openstack-meeting04:28
*** anniec has joined #openstack-meeting04:28
*** benonsoftware has quit IRC04:29
*** ArxCruz has quit IRC04:29
*** dstanek_afk has quit IRC04:31
*** ArxCruz has joined #openstack-meeting04:32
*** changbl has quit IRC04:33
*** haomaiwa_ has quit IRC04:33
*** haomaiwang has joined #openstack-meeting04:34
*** anniec_ has joined #openstack-meeting04:35
*** anniec has quit IRC04:35
*** anniec_ is now known as anniec04:35
*** changbl has joined #openstack-meeting04:36
*** toanster has joined #openstack-meeting04:36
*** dstanek_afk has joined #openstack-meeting04:37
*** ItSANgo has joined #openstack-meeting04:37
*** zhhuabj has joined #openstack-meeting04:37
*** haomaiwa_ has joined #openstack-meeting04:39
*** haomaiwang has quit IRC04:39
*** cdub has quit IRC04:47
*** blamar has quit IRC04:47
*** zhikunliu has joined #openstack-meeting04:49
*** benonsoftware has joined #openstack-meeting04:49
*** rongze has quit IRC04:50
*** dstanek_afk is now known as dstanek04:52
*** AaronGr is now known as AaronGr_Zzz04:53
*** cdub has joined #openstack-meeting04:54
*** oubiwan__ has quit IRC04:56
*** ryanpetrello has joined #openstack-meeting04:58
*** brucer has joined #openstack-meeting05:04
*** SergeyLukjanov is now known as _SergeyLukjanov05:09
*** _SergeyLukjanov has quit IRC05:10
*** SergeyLukjanov has joined #openstack-meeting05:14
*** dolphm has quit IRC05:16
*** oubiwan__ has joined #openstack-meeting05:17
*** oubiwan__ is now known as oubiwann-lambda05:17
*** dolphm_ has joined #openstack-meeting05:18
*** boris-42 has joined #openstack-meeting05:18
*** sc68cal has quit IRC05:18
*** sc68cal has joined #openstack-meeting05:18
*** rongze has joined #openstack-meeting05:20
*** oubiwann-lambda has quit IRC05:23
*** ryanpetrello has quit IRC05:25
*** ryanpetrello_ has joined #openstack-meeting05:25
*** nosnos_ has joined #openstack-meeting05:31
*** jcooley_ has joined #openstack-meeting05:33
*** nosnos has quit IRC05:34
*** rongze has quit IRC05:35
*** anniec has quit IRC05:36
*** neelashah has quit IRC05:38
*** banix has quit IRC05:54
*** nelsnelson has quit IRC05:56
*** nelsnelson has joined #openstack-meeting05:56
*** venkatesh has joined #openstack-meeting05:56
*** juice has quit IRC05:57
*** devananda has quit IRC05:57
*** davidlenwell_ has joined #openstack-meeting05:57
*** devananda has joined #openstack-meeting05:57
*** nelsnelson has quit IRC05:57
*** Ghe_HPDiscover has quit IRC05:57
*** vipuls has quit IRC05:58
*** nelsnelson has joined #openstack-meeting05:58
*** nelsnelson has quit IRC05:58
*** davidlenwell has quit IRC05:58
*** NobodyCam has quit IRC05:58
*** IlyaE has joined #openstack-meeting06:02
*** rongze has joined #openstack-meeting06:03
*** juice has joined #openstack-meeting06:03
*** nosnos_ has quit IRC06:04
*** nosnos has joined #openstack-meeting06:05
*** markpeek has quit IRC06:05
*** mdomsch has quit IRC06:06
*** vipul has joined #openstack-meeting06:07
*** rongze has quit IRC06:07
*** venkatesh_ has joined #openstack-meeting06:07
*** vkozhukalov has quit IRC06:09
*** venkatesh has quit IRC06:10
*** NobodyCam has joined #openstack-meeting06:14
*** otherwiseguy has quit IRC06:15
*** rongze has joined #openstack-meeting06:15
*** radsy has quit IRC06:18
*** IlyaE has quit IRC06:18
*** SergeyLukjanov has quit IRC06:21
*** whenry has quit IRC06:24
*** coolsvap has quit IRC06:25
*** gongysh has joined #openstack-meeting06:28
*** topol has joined #openstack-meeting06:29
*** Ghe_HPDiscover has joined #openstack-meeting06:35
*** novas0x2a|laptop has quit IRC06:36
*** coolsvap has joined #openstack-meeting06:38
*** jcooley_ has quit IRC06:39
*** masayukig has joined #openstack-meeting06:40
*** denis_makogon has joined #openstack-meeting06:42
*** gokrokve has quit IRC06:43
*** gokrokve has joined #openstack-meeting06:43
*** ildikov has joined #openstack-meeting06:44
*** topol has quit IRC06:44
*** thomasbiege has joined #openstack-meeting06:45
*** ildikov_ has joined #openstack-meeting06:46
*** gokrokve has quit IRC06:48
*** ryanpetrello_ has quit IRC06:52
*** ryanpetrello has joined #openstack-meeting06:56
*** yfujioka has joined #openstack-meeting06:59
*** zhhuabj has quit IRC07:01
*** mdurnosvistov has joined #openstack-meeting07:02
*** dstanek has quit IRC07:02
*** sushils has quit IRC07:02
*** lifeless has quit IRC07:05
*** mdurnosvistov has quit IRC07:06
*** akuznetsov has quit IRC07:08
*** zhhuabj has joined #openstack-meeting07:08
*** jcooley_ has joined #openstack-meeting07:09
*** mrunge has joined #openstack-meeting07:13
*** topshare has joined #openstack-meeting07:13
*** sdake_ has quit IRC07:13
*** jcooley_ has quit IRC07:15
*** IlyaE has joined #openstack-meeting07:16
*** simon-AS559 has joined #openstack-meeting07:16
*** stevemar2 has quit IRC07:20
*** jtomasek has joined #openstack-meeting07:20
*** belmoreira has joined #openstack-meeting07:22
*** IlyaE has quit IRC07:22
*** simon-AS559 has left #openstack-meeting07:22
*** boris-42 has quit IRC07:22
*** venkatesh_ has quit IRC07:23
*** MaxV has joined #openstack-meeting07:23
*** jtomasek has quit IRC07:26
*** jtomasek has joined #openstack-meeting07:27
*** doron_afk has joined #openstack-meeting07:30
*** lexx has joined #openstack-meeting07:32
*** Joy has quit IRC07:32
*** nati_ueno has joined #openstack-meeting07:36
*** MaxV has quit IRC07:36
*** MaxV has joined #openstack-meeting07:37
*** thomasbiege has quit IRC07:37
*** MaxV has quit IRC07:41
*** coolsvap has quit IRC07:47
*** SergeyLukjanov has joined #openstack-meeting07:49
*** sarob has joined #openstack-meeting07:51
*** pnavarro has quit IRC07:54
*** DinaBelova has joined #openstack-meeting07:54
*** thomasbiege has joined #openstack-meeting07:55
*** ArthurBerezin has joined #openstack-meeting07:55
*** ArthurBerezin has left #openstack-meeting07:55
*** Abhishek_ has joined #openstack-meeting07:57
*** vkozhukalov has joined #openstack-meeting07:57
*** ildikov__ has joined #openstack-meeting07:59
*** ildikov_ has quit IRC08:02
*** masayukig has quit IRC08:03
*** jcoufal has joined #openstack-meeting08:04
*** jcoufal has quit IRC08:04
*** jcooley_ has joined #openstack-meeting08:05
*** jcoufal has joined #openstack-meeting08:05
*** pnavarro has joined #openstack-meeting08:07
*** jcooley_ has quit IRC08:09
*** flaper87|afk is now known as flaper8708:13
*** lexx has quit IRC08:15
*** ruhe has joined #openstack-meeting08:16
*** fbo_away is now known as fbo08:18
*** markwash has quit IRC08:21
*** ruhe has quit IRC08:21
*** ruhe has joined #openstack-meeting08:22
*** ruhe has quit IRC08:25
*** haomaiwa_ has quit IRC08:27
*** haomaiwang has joined #openstack-meeting08:27
*** henrynash has joined #openstack-meeting08:29
*** akuznetsov has joined #openstack-meeting08:31
*** markwash has joined #openstack-meeting08:32
*** topshare has quit IRC08:32
*** topshare has joined #openstack-meeting08:34
*** MaxV has joined #openstack-meeting08:34
*** radix_ has joined #openstack-meeting08:36
*** nati_ueno has quit IRC08:38
*** yassine has joined #openstack-meeting08:46
*** rongze has quit IRC08:46
*** rongze has joined #openstack-meeting08:47
*** nprivalova has joined #openstack-meeting08:52
*** sushils has joined #openstack-meeting08:52
*** akuznetsov has quit IRC08:54
*** egallen has joined #openstack-meeting08:59
*** marekd|away has left #openstack-meeting09:00
*** jcooley_ has joined #openstack-meeting09:00
*** jlibosva has joined #openstack-meeting09:01
*** afazekas has joined #openstack-meeting09:02
*** romcheg has joined #openstack-meeting09:04
*** jcooley_ has quit IRC09:04
*** lbragstad has quit IRC09:05
*** boris-42 has joined #openstack-meeting09:06
*** Abhishek_ has quit IRC09:08
*** lbragstad has joined #openstack-meeting09:10
*** egallen has quit IRC09:11
*** akuznetsov has joined #openstack-meeting09:14
*** Abhishek_ has joined #openstack-meeting09:17
*** avishayb has joined #openstack-meeting09:18
*** markwash has quit IRC09:20
*** brucer has quit IRC09:20
*** venkatesh has joined #openstack-meeting09:21
*** samcdona has quit IRC09:21
*** derekh has joined #openstack-meeting09:23
*** lintan has joined #openstack-meeting09:24
*** henrynash has quit IRC09:25
*** doron_afk is now known as doron09:27
*** mdurnosvistov has joined #openstack-meeting09:30
*** akuznetsov has quit IRC09:31
*** euanh has joined #openstack-meeting09:33
*** euanh has left #openstack-meeting09:33
*** henrynash has joined #openstack-meeting09:35
*** nosnos_ has joined #openstack-meeting09:36
*** doron is now known as doron_afk09:39
*** jooools has joined #openstack-meeting09:40
*** nosnos has quit IRC09:40
*** denis_makogon has quit IRC09:42
*** lifeless has joined #openstack-meeting09:43
*** jooools has left #openstack-meeting09:46
*** johnthetubaguy has joined #openstack-meeting09:56
*** lucas_midokura has joined #openstack-meeting09:58
*** jcoufal has quit IRC09:58
*** matiu has quit IRC09:58
*** lucas_midokura has left #openstack-meeting09:59
*** gongysh has quit IRC10:00
*** shardy_afk is now known as shardy10:01
*** matiu has joined #openstack-meeting10:02
*** matiu has joined #openstack-meeting10:02
*** katyafervent has joined #openstack-meeting10:03
*** safchain has joined #openstack-meeting10:03
*** ildikov__ has quit IRC10:05
*** ildikov_ has joined #openstack-meeting10:06
*** luQAs has joined #openstack-meeting10:10
*** jaimegil has joined #openstack-meeting10:11
*** doron_afk is now known as doron10:12
*** dguitarbite has joined #openstack-meeting10:13
*** rossella_s has joined #openstack-meeting10:14
*** Jianyong has left #openstack-meeting10:14
*** epico has quit IRC10:16
*** lbragstad has quit IRC10:16
*** doron is now known as doron_afk10:19
*** DinaBelova has quit IRC10:20
*** nprivalova has quit IRC10:20
*** SergeyLukjanov is now known as _SergeyLukjanov10:23
*** akuznetsov has joined #openstack-meeting10:24
*** venkatesh has quit IRC10:25
*** topshare has quit IRC10:25
*** doron_afk is now known as doron10:25
*** sarob has quit IRC10:26
*** sushils has quit IRC10:33
*** paragan has quit IRC10:34
*** venkatesh has joined #openstack-meeting10:37
*** sushils has joined #openstack-meeting10:37
*** akuznetsov has quit IRC10:45
*** akuznetsov has joined #openstack-meeting10:48
*** jd__ has quit IRC10:48
*** jd__ has joined #openstack-meeting10:48
*** bogdando has quit IRC10:51
*** tianst has joined #openstack-meeting10:55
*** nosnos_ has quit IRC10:57
*** nprivalova has joined #openstack-meeting10:57
*** nosnos has joined #openstack-meeting10:57
*** yaguang has quit IRC10:59
*** suo__ has quit IRC11:02
*** anniec has joined #openstack-meeting11:03
*** akuznetsov has quit IRC11:07
*** akuznetsov has joined #openstack-meeting11:09
*** nprivalova has quit IRC11:09
*** sarob has joined #openstack-meeting11:16
*** mdenny has quit IRC11:20
*** venkatesh has quit IRC11:20
*** ravikumar_hp has quit IRC11:21
*** rongze has quit IRC11:21
*** nati_ueno has joined #openstack-meeting11:21
*** rfolco has joined #openstack-meeting11:22
*** Abhishek_ has quit IRC11:23
*** MaxV has quit IRC11:24
*** jcoufal has joined #openstack-meeting11:24
*** MaxV has joined #openstack-meeting11:24
*** zhikunliu has quit IRC11:28
*** MaxV has quit IRC11:29
*** bogdando has joined #openstack-meeting11:33
*** yamahata_ has quit IRC11:33
*** nermina has joined #openstack-meeting11:35
*** doron is now known as doron_afk11:36
*** doron_afk is now known as doron11:36
*** jhenner has joined #openstack-meeting11:38
*** kmartin has quit IRC11:42
*** jcooley_ has joined #openstack-meeting11:43
*** anniec_ has joined #openstack-meeting11:43
*** rongze has joined #openstack-meeting11:44
*** anniec has quit IRC11:45
*** anniec_ is now known as anniec11:45
*** nermina has quit IRC11:46
*** jcooley_ has quit IRC11:47
*** sarob has quit IRC11:48
*** MaxV has joined #openstack-meeting11:57
*** DinaBelova has joined #openstack-meeting11:57
*** MaxV has quit IRC12:01
*** MaxV has joined #openstack-meeting12:03
*** nprivalova has joined #openstack-meeting12:04
*** MaxV has quit IRC12:05
*** MaxV has joined #openstack-meeting12:05
*** vkmc has joined #openstack-meeting12:08
*** stevemar has joined #openstack-meeting12:09
*** doron is now known as doron_afk12:09
*** SergeyLukjanov has joined #openstack-meeting12:10
*** [1]avishayb has joined #openstack-meeting12:11
*** adalbas has joined #openstack-meeting12:12
*** yfujioka has quit IRC12:12
*** [2]avishayb has joined #openstack-meeting12:12
*** sarob has joined #openstack-meeting12:13
*** avishayb has quit IRC12:13
*** [2]avishayb is now known as avishayb12:13
*** ildikov_ has quit IRC12:15
*** [1]avishayb has quit IRC12:15
*** luQAs has quit IRC12:15
*** ArthurBerezin has joined #openstack-meeting12:18
*** nprivalova has quit IRC12:21
*** nprivalova has joined #openstack-meeting12:26
*** doron_afk is now known as doron12:27
*** paragan has joined #openstack-meeting12:27
*** paragan has quit IRC12:28
*** paragan has joined #openstack-meeting12:28
*** jcoufal has quit IRC12:31
*** markvoelker1 has joined #openstack-meeting12:32
*** doron is now known as doron_afk12:38
*** henrynash has quit IRC12:41
*** nprivalova has quit IRC12:42
*** dcramer_ has quit IRC12:43
*** beagles has quit IRC12:44
*** sarob has quit IRC12:45
*** doron_afk is now known as doron12:47
*** tianst has quit IRC12:48
*** henrynash has joined #openstack-meeting12:50
*** nprivalova has joined #openstack-meeting12:51
*** jcoufal-mob has joined #openstack-meeting12:56
*** thomasbiege has quit IRC12:58
*** eharney has joined #openstack-meeting12:58
*** [1]avishayb has joined #openstack-meeting12:59
*** thomasbiege has joined #openstack-meeting13:00
*** vkozhukalov has quit IRC13:00
*** [2]avishayb has joined #openstack-meeting13:00
*** pdmars has joined #openstack-meeting13:01
*** avishayb has quit IRC13:02
*** [2]avishayb is now known as avishayb13:02
*** ArthurBerezin has quit IRC13:03
*** ArthurBerezin has joined #openstack-meeting13:03
*** [1]avishayb has quit IRC13:03
*** henrynash has quit IRC13:04
*** nprivalova has quit IRC13:04
*** nprivalova has joined #openstack-meeting13:05
*** [1]avishayb has joined #openstack-meeting13:06
*** sandywalsh_ has quit IRC13:07
*** ArthurBerezin has quit IRC13:07
*** slagle has quit IRC13:08
*** jcoufal-mob_ has joined #openstack-meeting13:08
*** avishayb has quit IRC13:09
*** [1]avishayb is now known as avishayb13:09
*** b3nt_pin has joined #openstack-meeting13:10
*** sarob has joined #openstack-meeting13:10
*** dprince has joined #openstack-meeting13:11
*** jcoufal-mob has quit IRC13:11
*** b3nt_pin has quit IRC13:12
*** b3nt_pin has joined #openstack-meeting13:12
*** ygbo has joined #openstack-meeting13:12
*** nprivalova has quit IRC13:17
*** lblanchard has joined #openstack-meeting13:17
*** maxdml has joined #openstack-meeting13:17
*** b3nt_pin is now known as beagles13:19
*** yaguang has joined #openstack-meeting13:20
*** sandywalsh_ has joined #openstack-meeting13:20
*** b3nt_pin has joined #openstack-meeting13:22
*** ArthurBerezin has joined #openstack-meeting13:22
*** lbragstad has joined #openstack-meeting13:24
*** b3nt_pin has quit IRC13:26
*** topshare has joined #openstack-meeting13:29
*** jcooley_ has joined #openstack-meeting13:30
*** ttrifonov is now known as ttrifonov_zZzz13:31
*** ttrifonov_zZzz is now known as ttrifonov13:34
*** dstanek has joined #openstack-meeting13:35
*** sarob has quit IRC13:35
*** jdob has joined #openstack-meeting13:35
*** jcooley_ has quit IRC13:35
*** luQAs has joined #openstack-meeting13:37
*** topshare has quit IRC13:37
*** safchain has quit IRC13:38
*** jorisroovers has joined #openstack-meeting13:39
*** ArthurBerezin has left #openstack-meeting13:39
*** doron is now known as doron_afk13:39
*** rdxc has joined #openstack-meeting13:42
*** gongysh has joined #openstack-meeting13:43
*** dstanek has left #openstack-meeting13:43
*** doron_afk is now known as doron13:43
*** banix has joined #openstack-meeting13:44
*** doron has quit IRC13:44
*** ttrifonov is now known as ttrifonov_zZzz13:45
*** banix has quit IRC13:47
*** dkranz has joined #openstack-meeting13:48
*** banix has joined #openstack-meeting13:48
*** ttrifonov_zZzz is now known as ttrifonov13:48
*** safchain has joined #openstack-meeting13:54
*** thomasbiege1 has joined #openstack-meeting13:54
*** thomasbiege2 has joined #openstack-meeting13:55
*** jaimegil has quit IRC13:56
*** thomasbiege2 has quit IRC13:57
*** DrBacchus has joined #openstack-meeting13:58
*** thomasbiege has quit IRC13:58
*** thomasbiege1 has quit IRC13:58
*** galstrom_zzz is now known as galstrom14:01
*** ArthurBerezin1 has joined #openstack-meeting14:02
*** NikitaKonovalov has joined #openstack-meeting14:02
*** slagle has joined #openstack-meeting14:05
*** sarob has joined #openstack-meeting14:06
*** DrBacchus has quit IRC14:06
*** nosnos has quit IRC14:06
*** DrBacchus has joined #openstack-meeting14:06
*** galstrom is now known as galstrom_zzz14:08
*** ryanpetrello has quit IRC14:09
*** banix has quit IRC14:09
*** ryanpetrello has joined #openstack-meeting14:09
*** dguitarbite has quit IRC14:11
*** thomasem has joined #openstack-meeting14:11
*** BrianB__ has joined #openstack-meeting14:13
*** sarob has quit IRC14:14
*** gongysh has quit IRC14:16
*** jasondotstar has joined #openstack-meeting14:17
*** jcoufal has joined #openstack-meeting14:17
*** NikitaKonovalov has quit IRC14:19
*** lblanchard has quit IRC14:23
*** michchap has quit IRC14:24
*** jcooley_ has joined #openstack-meeting14:25
*** jgrimm has joined #openstack-meeting14:27
*** jcoufal-mob_ has quit IRC14:27
*** sarob has joined #openstack-meeting14:27
*** weshay has joined #openstack-meeting14:29
*** jcooley_ has quit IRC14:29
*** eharney has quit IRC14:30
*** sarob has quit IRC14:32
*** nati_ueno has quit IRC14:33
*** [1]avishayb has joined #openstack-meeting14:34
*** rnirmal has joined #openstack-meeting14:34
*** neelashah has joined #openstack-meeting14:34
*** oubiwan__ has joined #openstack-meeting14:36
*** HenryG has quit IRC14:36
*** avishayb has quit IRC14:37
*** [1]avishayb is now known as avishayb14:37
*** mrodden has quit IRC14:39
*** terriyu has joined #openstack-meeting14:40
*** paragan has quit IRC14:40
*** jeckersb_gone is now known as jeckersb14:41
*** kevinconway has joined #openstack-meeting14:42
*** esker has joined #openstack-meeting14:47
*** jorisroovers has quit IRC14:49
*** mrodden has joined #openstack-meeting14:50
*** haomaiwang has quit IRC14:50
*** haomaiwang has joined #openstack-meeting14:51
*** yaguang has quit IRC14:51
*** ArthurBerezin1 has quit IRC14:52
*** marun has quit IRC14:53
*** dhellmann has joined #openstack-meeting14:53
*** ArthurBerezin has joined #openstack-meeting14:55
*** markpeek has joined #openstack-meeting14:55
*** ArthurBerezin has quit IRC14:56
*** Leon has joined #openstack-meeting14:56
*** ArthurBerezin has joined #openstack-meeting14:57
*** Leon is now known as Guest7548214:57
*** ArthurBerezin has quit IRC14:58
*** dandrushko has joined #openstack-meeting14:58
*** ArthurBerezin has joined #openstack-meeting14:58
*** jcoufal-mob has joined #openstack-meeting14:59
*** jdob has quit IRC15:00
*** euanh has joined #openstack-meeting15:01
*** euanh has left #openstack-meeting15:01
*** BrianB__ has quit IRC15:01
*** matiu has quit IRC15:01
johnthetubaguy#startmeeting XenAPI15:02
openstackMeeting started Wed Dec 11 15:02:15 2013 UTC and is due to finish in 60 minutes.  The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: XenAPI)"15:02
johnthetubaguyhello all15:02
openstackThe meeting name has been set to 'xenapi'15:02
johnthetubaguywho is around today?15:02
thouvenghi15:02
matelhi15:02
*** burt has joined #openstack-meeting15:03
johnthetubaguycool, so lets get cracking15:03
johnthetubaguy#topic Blueprints15:03
*** openstack changes topic to "Blueprints (Meeting topic: XenAPI)"15:03
*** BobBall has joined #openstack-meeting15:03
*** SergeyLukjanov_ has joined #openstack-meeting15:03
BobBallSorry guys15:03
johnthetubaguyanyone got anything to chat about blueprints?15:03
thouvengyes :)15:03
*** yaguang has joined #openstack-meeting15:03
johnthetubaguycool, fire away15:04
thouvengI added a link to an etherpad and I don't know if it is a good practice15:04
*** jecarey has joined #openstack-meeting15:04
BobBallCould you just link to the bp thouveng ?15:04
BobBallin here I mean15:04
*** kgriffs_afk is now known as kgriffs15:04
BobBallI'm being thick and can't find it15:04
thouvenghttps://blueprints.launchpad.net/nova/+spec/pci-passthrough-xenapi15:05
thouvengand the link to ehterpad is https://etherpad.openstack.org/p/pci-passthrough-xenapi15:05
BobBallPerfect15:05
BobBallthat's right isn't it johnthetubaguy ?15:05
johnthetubaguyyeah, that looks good15:05
*** jdob has joined #openstack-meeting15:06
thouvengok cool.15:06
*** SergeyLukjanov has quit IRC15:06
*** dandrushko has quit IRC15:06
johnthetubaguyare there any bits you want to discuss in that?15:07
johnthetubaguyor just get a general review?15:07
thouvengjust a general review for the moment15:07
*** vkozhukalov has joined #openstack-meeting15:07
*** boris-42 has quit IRC15:08
BobBallI think it LGTM - but that might be because we've discussed it outside of the BP15:08
johnthetubaguywhat is all the hiding of PCI devices?15:08
*** jcoufal has quit IRC15:08
johnthetubaguyI thought all the hiding is implemented inside nova?15:08
BobBallI'll let you answer thouveng - but if you want me to step in, let me know15:08
*** eharney has joined #openstack-meeting15:09
thouvengyes please go because I didn't get the question sorry15:09
*** sneelakantan_ has joined #openstack-meeting15:09
johnthetubaguythouveng: you say about passing a "hide" option to pciback module, why is that?15:09
BobBallIn order to do PCI pass through for PV guests in xen (and stably for HVM guests) the devices should use the pciback driver in dom0 to make sure dom0 doesn't use them for other things15:10
BobBallTherefore they need to be "hidden" from the normal kernel boot so pciback can collect them15:10
BobBallhence pciback.hide=(device_id) on the kernel command line15:10
*** gokrokve has joined #openstack-meeting15:10
*** jcoufal-mob has quit IRC15:10
*** SergeyLukjanov has joined #openstack-meeting15:10
*** sneelakantan_ has left #openstack-meeting15:11
BobBallthe KVM approach is to change the module dynamically but that's a little less stable - and yuo still have to enumerate the devices in nova.conf anyway15:11
BobBallso the two might as well be combined15:11
*** ivasev has joined #openstack-meeting15:11
*** NehaV has joined #openstack-meeting15:11
johnthetubaguyOK, so I am not sure I understand what is going there, I know there is a whilelist that tells nova which devices it can pass to a guest, and in the flavor we tell nova which devices to pass to a specific server15:12
*** SergeyLukjanov_ has quit IRC15:12
BobBallPost-whitelist, KVM will try to disconnect the device from dom0 and attach it to the KVM-equivalent of the pciback driver15:13
johnthetubaguyoh, I see15:13
*** HenryG has joined #openstack-meeting15:13
johnthetubaguyso we have to disconnect some set of device from dom0, and thats what we are updating?15:13
BobBallAll we're saying is we'll do that at boot time since that's better practice - particularly for xen15:13
*** pschaef has joined #openstack-meeting15:13
BobBallyes - but they are not "disconnected", just never connected to dom0, as it's a dom0 kernel option15:13
johnthetubaguyright15:14
johnthetubaguyso this is moving into host aggreates, and the config file is going away15:14
johnthetubaguydoes that create an issue?15:14
BobBallwhat is moving into host aggregates?15:14
*** safchain has quit IRC15:14
BobBalland what config file?  do you mean the whitelist option in nova.conf?15:15
BobBallbut no, I'm sure it won't create a problem15:15
thouvengthere are two different things to configure pci passthrough. The whitelist is just used bu the compute node.15:15
*** jcoufal has joined #openstack-meeting15:15
johnthetubaguyyes, the configuration in nova.conf is going into the DB15:16
BobBallwell - the compute node uses the whitelist to report to the scheduler what it can provide, right?15:16
thouvengso I think that it doesn't create any issue since we just replaced the white list by the boot command line detection.15:16
thouvengBobBall: yes15:16
johnthetubaguythat includes the white list I think15:16
BobBallthat won't be a problem15:16
BobBallI think :P15:16
johnthetubaguyerm, except the user now specifies the whitelist through an administration API?15:16
johnthetubaguyas in rest API15:16
BobBallThat won't be possible in the current thinking - and possibly isn't possible _at all_ with Xen15:17
johnthetubaguyhmm, so thats what we decided at the summit for PCI passthrough, oh dear...15:18
*** jcooley_ has joined #openstack-meeting15:18
johnthetubaguyso, its not all bad right… as long as you expose more PCI devices than you want in your nova based whitelist15:18
*** luQAs has quit IRC15:18
BobBalltrue15:18
BobBallso it migth need to be an intersection of the two15:18
BobBalli.e. you have to configure in dom0 to expose it15:19
johnthetubaguycool, I think we are good15:19
johnthetubaguyyeah, +115:19
BobBalland then nova can only use it if it's both there and in the whitelist15:19
johnthetubaguyexpose some in dom0, then you can configure some of those in the dymanic whitelist, it all wokrs15:19
johnthetubaguyyup15:19
johnthetubaguycool15:19
johnthetubaguyany more blueprint stuff?15:19
BobBallIt might be possible with newer versions of xen btw - so Augusta or beyond - which use Xen 4.2+15:19
BobBallbut not with existing versions (which don't have xl pci-set-assignable stuff)15:20
BobBall-xen +XenServer15:20
*** otherwiseguy has joined #openstack-meeting15:20
johnthetubaguyah, OK15:20
johnthetubaguygood to know15:20
thouvengnice15:20
*** litong has joined #openstack-meeting15:20
BobBallDoes that make sense thouveng?  I think that's right?15:20
thouvengyes I think so15:20
*** NehaV1 has joined #openstack-meeting15:21
johnthetubaguyI would just get in there, and throw up some code, and we can help you through it15:21
johnthetubaguyall sounding really good :)15:21
*** sarob has joined #openstack-meeting15:21
BobBallgood good15:22
johnthetubaguy#topic Docs15:22
*** openstack changes topic to "Docs (Meeting topic: XenAPI)"15:22
johnthetubaguyany news?15:22
johnthetubaguy#topic QA15:22
*** openstack changes topic to "QA (Meeting topic: XenAPI)"15:22
johnthetubaguymatel: want to update us on the tempest gate work?15:22
*** julim has joined #openstack-meeting15:23
matelYep, nodepool is not prepared for server restarts15:23
matelso I'm proposing a patch, so that this concept fits in.15:23
*** jcooley_ has quit IRC15:23
johnthetubaguyI am looking at the other side, so assuming we get nodepool sorted, and we have a VM setup, what can we do15:23
*** NehaV has quit IRC15:23
johnthetubaguyat the same time, going to see what I can do with config drive to get IPs into it, inside rax cloud15:23
matelIf that's ready, 2 more items left on the list: 1.) prepare the instance for snapshotting 2.) come up with a localrc.15:24
johnthetubaguyyep15:24
matelYes, config drive would save us some reboots15:24
*** NikitaKonovalov has joined #openstack-meeting15:24
johnthetubaguyI am kinda looking at (2), in theory anyways15:24
matelApart from that, an email will go to the infra list with our ideas.15:24
johnthetubaguybobball: how is making tempest stable going?15:24
matelHopefully today.15:25
johnthetubaguymatel: some fine work15:25
*** matrohon has joined #openstack-meeting15:25
*** topol has joined #openstack-meeting15:25
BobBallin the RS cloud just waiting for Mate to collect the logs so we can try and figure out why it's not working properly up there but it works better here15:25
BobBallanyway15:25
BobBallI've got a whole heap of changes stuck waiting for review needed to get tempest stable + fast enough15:25
johnthetubaguyBobBall: is that full tempest failing or smoke too?15:26
matelBob - what's up with changing to raring?15:26
*** sarob has quit IRC15:26
BobBallsmoke in RS cloud fails15:26
BobBallThat's what I was just going tos ay - but I want suacy15:26
BobBallsaucy*15:26
BobBallanyway - the hopefully last issue is a kernel bug in precise15:26
matelOh, so you say we should try saucy?15:26
BobBallwhich we've just confirmed as a kernel bug15:26
BobBallyeah15:26
BobBallsaucy is newer15:26
BobBallnew = good, right?15:26
johnthetubaguysomething like that15:27
matelI'm a bit confused, soucy is the latest?15:27
BobBallMaybe raring is good enough15:27
BobBallyes15:27
BobBallraring = 13.0415:27
matelIt's not true in the software world.15:27
BobBallsaucy = 13.1015:27
johnthetubaguymatel: what is in your XVA at the moment?15:27
matelA debootstrapped install.15:27
matelwait a sec...15:27
BobBallAnyway - the kernel bug in precise causes a semaphore to be held when the userspace program finishes15:27
*** sarob has joined #openstack-meeting15:27
BobBallcausing all sorts of things to fail randomly15:27
johnthetubaguynasty15:28
BobBalllike lsof or lvs or anything really15:28
johnthetubaguyeek, nice15:28
BobBallwhich in turn (very disappointingly) means that tempest fails15:28
mateljohn: which xva are you asking?15:28
mateljohn: gimme url.15:28
BobBallI thought all XVAs were precies?15:28
BobBallprecise*15:28
johnthetubaguymatel: the one in your script in gerrit?15:28
matelAh, OK, I thought that you are interested in the package list.15:28
matelSo yes, that's a precise.15:29
*** nermina has joined #openstack-meeting15:29
johnthetubaguyOK, so there is (3) update xva to latest ubuntu15:29
matelGuys, should we agree to go for saucy?15:29
johnthetubaguywe should go for whatever works for you locally at the moment15:29
BobBallanyway - the frustrating thing is that for some reason we don't seem to hit this kernel issue if we don't have one of my changes... but other things in tempest randomly fail without it15:29
johnthetubaguylol15:30
johnthetubaguythat sucks15:30
BobBall#link https://review.openstack.org/#/c/60253/ is the one that fixes some real nova failures and seems to somehow expose the kernel bug15:30
matelthat's not lol, Bob is loosing his hair.15:30
matelSo, Saucy?15:30
matelBob?15:30
BobBallIt's true.  I have pulled most of it out in the last week.15:30
BobBallI say yes matel15:31
BobBallno point sticking on precise IMO15:31
*** IlyaE has joined #openstack-meeting15:31
johnthetubaguyyou make it go so fast… you hit a kernel bug15:31
johnthetubaguyit happens to us all15:31
matelOkay, I will go for that as well.15:31
BobBalleither saucy or just say "sod it" and go for centos like the rest of the infra jobs ;)15:31
*** NehaV1 has quit IRC15:31
mateljohn - do you know if anyone is on saucy?15:31
BobBallbut that's a bigger change15:31
*** luQAs has joined #openstack-meeting15:31
BobBallI'm happy with trying raring if it's easier - e.g. exists in RS15:31
matelYep, I am afraid of the unknowns.15:31
johnthetubaguyI duno, can't remember what we use, don't think its ubuntu15:31
matelOkay, let's go with raring.15:32
*** sarob has quit IRC15:32
BobBallRS are standardising on Debian moving forward15:32
johnthetubaguyraring is fine for now15:32
matelwheezy?15:32
matelBob, do you think, wheezy would be a good option?15:32
BobBallnot sure which one matel ... antonym did tell me, but I can't remember15:32
johnthetubaguyBobBall: thats all I remember, debian15:32
BobBallbut debian vs ubuntu yes15:33
johnthetubaguybut some folks want centos, but hey15:33
matelI'm just afraid of being the only team on the edge.15:33
johnthetubaguyyeah, lets just pick something that works15:33
BobBallmaybe it was sid - Rackspace like being on the edge ;)15:33
johnthetubaguyif it falls over, we pick something else righ15:33
matelThe problem is the cost of these probes, John.15:33
matelIt's quite expensive, so thinking for a while is a good idea.15:34
johnthetubaguysure, but we know precise is broken, I would rather with pick an LTS, but whatever works for now15:34
BobBallCan we just remove the XVA and run a dozen or so smokes overnight to see if raring works?15:34
johnthetubaguyBobBall: +115:34
johnthetubaguyanyways15:34
johnthetubaguylets move on I think15:34
johnthetubaguynot precise as precise is broken for us, seems OK for now15:34
*** Fdot has joined #openstack-meeting15:34
johnthetubaguybut lets leave that for now15:35
*** oubiwan__ is now known as oubiwann-lambda15:35
johnthetubaguywe need the nodepool working first15:35
johnthetubaguylets get a failing test rather than no test15:35
matelwill add you to the reviewers.15:35
johnthetubaguycool, sounds good15:35
johnthetubaguyany bugs that people want to talk about?15:35
BobBallhttps://review.openstack.org/#/c/60808/ is always fun15:36
BobBallgot a very weird thing happening15:36
BobBallbut it's not the cause of the kernel bug15:36
BobBallbasically we get kernel messages15:36
*** zhaoqin__ has joined #openstack-meeting15:36
BobBallsaying the device is in use by nova when we're trying to unplug it15:36
BobBalland it leaks grant entries15:36
BobBallwhich isn't a "problem" - but something that's very weird15:37
BobBallthe device _does_ unplug15:37
BobBallbecause the next loop sees it as inactive then it's ok15:37
BobBallbut compounded it might cause a problem15:37
BobBallafter hundreds of the g.e.'s leak15:37
BobBallso I was trying to fix it with sync's and direct access to disks15:37
BobBallall of which should prevent it15:37
BobBallbut it's not :(15:37
johnthetubaguyyeah, might run out of handles or something...15:38
johnthetubaguyhmm15:38
BobBallnot handles - but Xen will get very unhappy15:38
BobBallI assert the changes I've made are good changes and worthwile to have15:38
BobBallwhich is why I haven't pulled them15:38
BobBallbut they haven't fully fixed the issue I'm seeing15:38
*** ArthurBerezin has quit IRC15:38
BobBalland I can't explain why because everything is so disconnected it's impossible to trace back to the nova code that's causing this15:38
BobBallAND it only happens in parallel tempest at random times too15:39
*** ArthurBerezin has joined #openstack-meeting15:39
johnthetubaguyyuck15:39
BobBallBut maybe it'll be fixed by upgrading to the latest version of Ubuntu15:39
BobBallAnd if it's not, we can just wait for 14.04 :)15:39
johnthetubaguyyeah, sounds nasty, would PVHVM be better?15:40
BobBallcan't run that in RS cloud15:40
*** jorisroovers has joined #openstack-meeting15:40
BobBallI assume you mean HVM rather than PVH15:40
johnthetubaguytrue, damm half working nested virt15:40
johnthetubaguyyeah, HVM with PV drivers, but we can't do that either, I assume15:41
BobBallPVH will be cool when it exists15:41
johnthetubaguy+115:41
johnthetubaguycool, so lets move on...15:41
johnthetubaguy#topic Open Discussion15:41
*** openstack changes topic to "Open Discussion (Meeting topic: XenAPI)"15:41
johnthetubaguyanything else for today's meeting?15:42
annegentleDoc Bug Day 12/20 -- next Friday15:42
annegentlefollow the sun!15:42
BobBallregarding direct IO for writing config drive you just commented John - I don't have a bug that I can say is fixed by this, which is why it doesn't have a link15:42
johnthetubaguyah, my last day at work, that sounds like a good time to help update docs, I will but that in my diary15:43
BobBallthe change is one that we should be doing, but the symptoms I saw weren't fixed by this15:43
annegentleIt would be great to clean up/consolidate the Xen doc bugs, I think they're mostly tagged accurately. https://bugs.launchpad.net/openstack-manuals/+bugs?field.tag=xen15:43
annegentlejohnthetubaguy: yeah the timing is pretty cool. My team is gonna put in a movie in the afternoon :)15:43
*** ArthurBerezin has quit IRC15:43
johnthetubaguy#action johnthetubaguy sort out doc bugs on doc day15:44
*** Mandell has joined #openstack-meeting15:45
johnthetubaguycool, so I guess we are all done?15:45
*** jorisroovers has quit IRC15:46
*** jroovers has joined #openstack-meeting15:46
*** changbl has quit IRC15:46
*** dims has quit IRC15:46
*** thingee has joined #openstack-meeting15:47
johnthetubaguy#endmeeting15:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:48
openstackMeeting ended Wed Dec 11 15:48:02 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-12-11-15.02.html15:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-12-11-15.02.txt15:48
openstackLog:            http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-12-11-15.02.log.html15:48
*** ndipanov has quit IRC15:48
*** dolphm_ is now known as dolphm15:50
*** s3wong has joined #openstack-meeting15:51
*** mdenny has joined #openstack-meeting15:53
*** caitlin56 has joined #openstack-meeting15:53
*** julim has quit IRC15:54
*** coolsvap has joined #openstack-meeting15:54
*** samcdona has joined #openstack-meeting15:55
*** bpoulos has joined #openstack-meeting15:56
*** wolsen has joined #openstack-meeting15:56
*** anniec has quit IRC15:57
*** banix has joined #openstack-meeting15:57
*** ArthurBerezin has joined #openstack-meeting15:57
*** BrianB__ has joined #openstack-meeting15:58
*** xyang__ has joined #openstack-meeting15:59
*** changbl has joined #openstack-meeting15:59
*** jorisroovers has joined #openstack-meeting15:59
*** jungleboyj has joined #openstack-meeting16:00
*** BobBall has left #openstack-meeting16:00
*** winston-d has joined #openstack-meeting16:00
*** zhiyan has joined #openstack-meeting16:00
*** mestery has quit IRC16:00
*** avishay has joined #openstack-meeting16:01
*** nermina has quit IRC16:01
*** dims has joined #openstack-meeting16:01
*** AaronGr_Zzz is now known as AaronGr16:02
*** jroovers has quit IRC16:03
*** jchan has joined #openstack-meeting16:03
*** japplewhite has joined #openstack-meeting16:03
*** haomaiwa_ has joined #openstack-meeting16:04
*** haomaiwang has quit IRC16:04
*** otherwiseguy has quit IRC16:05
*** SergeyLukjanov has quit IRC16:05
*** bswartz has joined #openstack-meeting16:05
*** NikitaKonovalov has quit IRC16:05
*** sneelakantan_ has joined #openstack-meeting16:05
*** afrittoli has quit IRC16:06
thingeewho wants to be in jgriffith's shoes for 55 mins?16:06
*** DinaBelova has quit IRC16:06
winston-dDuncanT: ?16:06
thingeeDuncanT?16:06
thingeeha16:06
*** andreaf has joined #openstack-meeting16:06
avishaythingee: ?16:07
avishay:)16:07
zhaoqin__thingee: you host the meeting today?16:07
caitlin56+1 thingee16:07
*** kmartin has joined #openstack-meeting16:07
avishaythingee: you're the only one on the agenda...does it make sense to discuss in a limited forum?16:07
winston-dthingee: +216:07
zhiyan+1 thingee16:07
jungleboyjWhere is everybody?16:08
avishayjungleboyj: beats me16:08
*** joel-coffman has joined #openstack-meeting16:09
*** fnaval has joined #openstack-meeting16:09
thingee#startmeeting Cinder16:09
openstackMeeting started Wed Dec 11 16:09:36 2013 UTC and is due to finish in 60 minutes.  The chair is thingee. Information about MeetBot at http://wiki.debian.org/MeetBot.16:09
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:09
jungleboyjavishay: Everyone is bailing out here for Christmas already.  Not be just an IBM thing.  :-)16:09
*** openstack changes topic to " (Meeting topic: Cinder)"16:09
openstackThe meeting name has been set to 'cinder'16:09
thingeehi all16:09
bswartzwoop16:09
xyang__hi16:09
joel-coffmanhey16:09
zhaoqin__hello16:10
jungleboyjHowdy!16:10
bswartzbetter late than never16:10
thingeeagenda today folks https://wiki.openstack.org/wiki/CinderMeetings16:10
avishaybswartz: not always :)16:10
winston-do/16:10
*** galstrom_zzz is now known as galstrom16:10
thingeethingee: you have the floor16:10
avishayhaha16:10
thingee#topic Ideas with extensions16:10
*** openstack changes topic to "Ideas with extensions (Meeting topic: Cinder)"16:10
thingee#link https://etherpad.openstack.org/p/cinder-extensions16:10
jungleboyjOh no, thingee is talking to himself.16:11
*** lbragstad has quit IRC16:11
avishaythingee: so an extension could add a new flow, or inject into existing flows, yes?16:11
*** jorisroovers has quit IRC16:11
thingeeinject into an existing flow16:12
avishayyes16:12
avishayor a new one, right?16:12
thingeeso that's debatable. I thnk things get more complex then.16:12
avishayi see16:12
kmartinso reading the etherpad, does multi-attach fall into core since its part of "attach it" basic function16:13
thingeebecause you could end up with different results16:13
zhiyankmartin: hehe i asked same question on the summit, but seems it isn't16:13
*** BrianB__ has quit IRC16:13
caitlin56If it is a new flow, how do users know when to invoke it and how? If you are modifying a flow, how do you allow two exensions to modify the same flow?16:13
*** hemna has joined #openstack-meeting16:13
avishaywhere would retype go?  it's related to types, but it has it's own flow.  where does migration go?  replication can definitely inject into create_volume.16:13
*** safchain has joined #openstack-meeting16:14
*** winston-1 has joined #openstack-meeting16:15
thingeecaitlin56: exactly. there maybe other extensions injecting to that flow...and then you got a whole mess if an extension just does a new flow.16:15
*** DrBacchus has quit IRC16:15
*** jcooley_ has joined #openstack-meeting16:15
thingeesorry guys, ym irssi session is really laggy atm16:15
winston-1i like the idea 'core feature should be avaiable (cannot be disabled/turned off) everywhere'.16:16
caitlin56thingee: that's my concern, the phrase "injection" brings back ancient memories of DOS TSR routines.16:16
*** mdomsch has joined #openstack-meeting16:16
*** doude has joined #openstack-meeting16:16
jungleboyj+1 winston-116:16
thingeewinston-d: +116:16
thingeeavishay: so I see migration as a new flow that could be registered with the manager.16:16
bswartzDOS TSR routines: -100016:17
*** pcm_ has joined #openstack-meeting16:17
*** rushiagr has joined #openstack-meeting16:17
avishaythingee: OK so that's what i meant by an extension adding a new flow16:17
rushiagrhey hi all!16:17
avishayrushiagr: hi16:17
*** hartsocks has joined #openstack-meeting16:17
*** DrBacchus has joined #openstack-meeting16:17
thingeeavishay: Thanks. I just need a good example to get to that point :)16:17
*** ozstacker has quit IRC16:17
avishaythingee: :)16:18
thingeeso harlowja and I have been talking about ways to inject beginning and end16:18
*** mrunge has quit IRC16:18
thingeethat's pretty simple16:18
avishayi like the idea in terms of code, the DB is where it gets tricky (and also conflicting extensions as caitlin56 mentioned)16:18
*** ozstacker has joined #openstack-meeting16:19
* DuncanT forgot the meeting, sorry16:19
thingeewhen you talk middle..I have this sort of silly idea that you take the the core tasks...whatever task is in the middle, you inject before that. I think this might lead to problems where the core tasks can change..and then extensions would break.16:19
avishayneed tempest tests that try all combinations?16:19
caitlin56avishay: we can learn from past mistakes, the key is to prevent extension X from modifying the chain as previously modified by extension Y while assuming it was unmodifed.16:19
*** radez_g0n3 is now known as radez16:19
thingeeYou have things like FC zone manager that'll basically need to change how attach/detach works.16:20
*** otherwiseguy has joined #openstack-meeting16:20
*** jcooley_ has quit IRC16:20
avishaycaitlin56: thingee: yep16:20
hemnathingee, do you have a wiki on what it means to be an extension and how one codes it up?   I'm not clear on the distinction.16:21
thingeeanyways, this is kind of what I've been throwing around.16:22
*** weshay has quit IRC16:22
rushiagrI agree, we don't have good docs to explain what an extension is16:22
thingeehemna: not yet. I wanted to start with just rexplaining my idea since there was a big disagreement at the summit16:22
caitlin56henma: there isn't anything I could find. That might be a first step -- fully document what is there today.16:22
thingeeI wanted to start with everyone agreeing what is core16:22
thingeeif we can agree on what core is, the rest are extensions to cinder.16:23
*** doude has left #openstack-meeting16:23
hemnawell I thought the real disagreement was simply around disallowing extensions to touch/change the db schema16:23
avishaythingee: your list of core seems good to me16:23
*** Mandell has quit IRC16:24
*** jbernard has joined #openstack-meeting16:24
caitlin56henma: with some solid examples on a wiki page there might be less opposition to specific restrictions. Show us how it would work with the restriction.16:24
thingeehemna: yeah and I just want people on the same page of what core is. I really see the future of cinder is mostly just talking about extensions. Very rarely does something new come into core..it's just improvements to core mostly.16:24
avishayhemna: i agree that it would be cool to not have them change schema, but i think we need a better alternative than joins or metadata16:24
hemnaavishay, +116:24
avishaynot that i have any bright ideas :)16:25
*** julim has joined #openstack-meeting16:25
hemnaheh16:25
hemnathe FC Zone Manager is a grey area16:25
hemnawhich makes it a good discussion point16:25
thingeeavishay: my only concern is when you have extensions changing the model schema to say volumes. What happens when that plugin gets disabled...16:25
*** reed has joined #openstack-meeting16:26
hemnathingee, could be a use at your own risk documentation issue16:26
thingeeNeutron is dealing with that right now since vendors dictate what the core table schemas look like.16:26
bswartzWhere can I read about why multi-attach can't be part of core?16:26
hemnathingee, disabling in that case breaks cinder16:27
hemnaonce you enable one of those plugins it can't get disabled, unless there is a migration that gets run on disable ?16:27
avishayis this blocking multi-attach?16:27
hemnapain16:27
thingeeavishay: no. This will not block anything because of how fast it's progressing. Extensions should continue with development.16:28
caitlin56One question I have: could you define an extension that made some new type of volume available where you could *only* access that volume with the extension?16:28
*** boris-42 has joined #openstack-meeting16:28
avishaythingee: ok good16:28
thingeeavishay: the problem will just get worse, but we'll get there when we get there.16:28
*** akuznetsov has quit IRC16:28
*** jcoufal has quit IRC16:28
avishaythingee: we have to rewrite all the code anyway for taskflow, and all the unit tests for mock :)16:29
thingeecaitlin56: I see that volume still part of the basic idea of what cinder thinks a volume is. it just has added information with it.16:29
thingeeif you cinder list, it shows up.16:29
thingeeyou do*16:29
caitlin56So you use extensions to add new operations/etc., not totally new things that surpass the base. That's livable, especially if well explained on a wiki page.16:30
jungleboyjThat makes more sense to me.16:30
thingeeok so it sounds like no one disagrees with this and I'm ok with continuing to spend time with find alternatives to joins, what to do with extensions that require a complete rewrite of a flow like FC zone manager attach/detach...and provide a useful example of how this all works.16:31
*** nelsnelson has joined #openstack-meeting16:31
*** venkatesh has joined #openstack-meeting16:31
avishaythingee: sounds good to me16:31
thingeethe persistent data thing I'm really unsure about atm.16:31
caitlin56at the summit avishay discussed the idea of having a new type of volume that would be the passive end of a mirrored relationship. Is that something that an extension could handle?16:31
DuncanTbswartz: That discussion about multi-attach being core has popped up many times, and come out with several different answers. Not sure the discussion has been documented anywhere. A big part of it not being core is that many installations might want to turn it off, since it is hard to use correctly and *will* generate support load and data corruption16:31
bswartzDuncanT: thanks for the explanation16:32
thingeeDuncanT: +116:32
*** cody-somerville has joined #openstack-meeting16:32
*** cody-somerville has quit IRC16:32
*** cody-somerville has joined #openstack-meeting16:32
avishaycaitlin56: the passive volume will not be visible to users, so maybe that will ease things?16:32
*** lbragstad has joined #openstack-meeting16:33
caitlin56avishay: interesting, I'd like to hear how you use it if it isn't visible, but after this topic is finished.16:33
*** hemna has quit IRC16:33
thingee#todo thingee needs to figure out 1) ext persistent data 2) work with ext that require redoing an entire flow 3) provide a useful example16:33
avishaycaitlin56: https://etherpad.openstack.org/p/icehouse-cinder-continuous-volume-replication-v216:33
thingeethanks folks for the input16:33
*** jcooley_ has joined #openstack-meeting16:33
avishaythingee: thanks for the effort16:34
*** yaguang has quit IRC16:34
thingeeif anyone is interested with working on this with me, please ping me16:34
winston-1another impact of extension is that they sometimes modified internal RPC APIs16:34
avishaywinston-1: mmm good point16:34
thingeewinston-1: yes good point. noted on the etherpad16:35
*** sacharya has joined #openstack-meeting16:35
thingee#topic icehouse-2 progress16:35
*** openstack changes topic to "icehouse-2 progress (Meeting topic: Cinder)"16:35
winston-1even if you can turn off some extension, but it already modified RPC APIs, which means backwards compatibility is messed up16:35
thingeeDuncanT: https://blueprints.launchpad.net/cinder/+spec/filtering-weighing-with-driver-supplied-functions16:35
thingeeI think you started on this from discussions yesterday?16:35
*** weshay has joined #openstack-meeting16:36
DuncanTthingee: Yup, I've got the evaluatior done, the filter itself seems to work. Unit test still need sorting, but I'm waiting for Avisay's branch to be merged since he re-wrote them all16:36
*** s0mik has joined #openstack-meeting16:36
rushiagrwinston-1: so should we just disallow extensions to make backward incompatible changes?16:37
thingeeDuncanT: do you mind marking that as started?16:37
*** haomaiwa_ has quit IRC16:37
DuncanTSure16:37
*** hemna has joined #openstack-meeting16:37
DuncanTDone16:37
*** haomaiwang has joined #openstack-meeting16:37
thingeethanks16:38
caitlin56rushiagr: extensions will need to *add* methods. And those methods would be disabled/disappaear when the extension is disabled. But they shouldn't *change* an existing method.16:38
thingeeavishay: you're waiting jenkins failures for https://review.openstack.org/#/c/44881/ ?16:38
thingeevolume retype16:38
*** venkatesh has quit IRC16:38
avishaythingee: just put up a new version that addressed all issues so far (i think).  yea, jenkins sucks today.16:38
*** colinmcnamara has joined #openstack-meeting16:38
*** colinmcn_ has joined #openstack-meeting16:38
rushiagrcaitlin56: oh16:38
avishaythingee: it works and is ready for re-review16:39
rushiagrcaitlin56: thats messy16:39
thingeegreat, so everyone should help out out on the retype review. :)16:39
thingee#link https://review.openstack.org/#/c/4488116:39
thingeeis Abhishek here?16:39
avishay:)16:39
rushiagrcaitlin56: err.. that can make things messy while disabling extensions16:40
avishaythingee: Refactor code for delete volume using TaskFlow 0.1 ?16:40
thingeeavishay: yes.16:40
thingeealright going to assume not16:41
jungleboyjthingee: avishay I will try to look at 44881 later today.16:41
avishaythingee: as far as i understood, all taskflow-related work is blocked on the create_volume patch currently in the queue16:41
avishayjungleboyj: thanks!16:41
thingeejungleboyj: thanks. I should too since I already went through it once and have an env ready16:41
thingee#Open topic16:41
thingee#topic open topic16:41
*** openstack changes topic to "open topic (Meeting topic: Cinder)"16:41
thingee:)16:41
thingeeso any bps people want to discuss?16:42
winston-1avishay: will review retype tomorrow, err, later today16:42
avishaywinston-1: thanks a lot16:42
*** haomaiwang has quit IRC16:42
winston-1thingee: https://blueprints.launchpad.net/cinder/+spec/deprecate-chance-and-simple-schedulers16:42
avishaywe should also give create_volume w/ taskflow a high priority.  it looks ok to me, but i'm not an expert.16:42
rushiagravishay: I'll have a look at it too. I always found reasons to skip reviewing it so far :)16:43
avishayrushiagr: awesome16:43
* jungleboyj needs to look at some of the longer patches soon.16:44
hemnaavishay, I reviewed the taskflow -> 0.1.1 yesterday and it looks good minus a few minor tweaks16:44
thingeewinston-1: looks like you were the one stopping it :) https://review.openstack.org/#/c/60690/16:44
winston-dthingee: i'm working on a patch to actually replace chance/simple scheduler with filter scheduler.16:45
avishayhemna: yep saw that16:45
thingeeoh ok16:45
hemnaI'll try looking at the retyping review today16:45
avishaywinston-d: is it clear which filters to use in those cases?  everything except capablities?16:45
winston-dthingee: not really sure if anyone still using chance/simple scheduler16:45
thingeewinston-d, avishay: I noticed the replace the schedulers isn't in I-216:46
avishaythingee: it is now :)16:46
*** afazekas has quit IRC16:46
winston-davishay: i think every filters in default filter list should be included, even capablities filter. it's about weigher16:47
hemnahas jgriffith mentioned when he is getting to the brick work ?16:47
DuncanTI'm going to make my usual point about back-compatibility here...16:47
avishayBTW, all, please stop rechecking...poor jenkins is broken, it won't help and only adds load16:47
thingeewinston-d, avishay: ok so this bp captures deprecating...is there another for replacing with filter?16:47
xyang__winston-d: do you know why the filters are in two different folders in cinder16:48
thingeehemna: I was wondering that myself...I have not heard anything on it yet16:48
avishaythingee: so winston-d's suggestion is not to deprecate, but replace them with filter scheduler under the covers16:48
avishayDuncanT: ^16:48
thingeeavishay: got it16:48
hemnaI spoke with him at the start of I-1, and he said he slated it for I-1, but I guess he got busy16:48
DuncanTavishay: That's fantastic, as long as running config don't stop running, I'm entirely happy16:49
avishayDuncanT: yea sounds good to me too16:49
winston-dxyang__: yes, i do. i can explain that offline in #openstack-cinder if you like16:49
xyang__winston-d: ok, thanks16:49
hemnaDuncanT, did you get a chance to write the BP on the scheduluer driver methods as discussed at HK ?16:49
thingeebswartz: do you need anything for https://blueprints.launchpad.net/cinder/+spec/multiple-capability-sets-per-backend ?16:49
DuncanThemna: https://blueprints.launchpad.net/cinder/+spec/filtering-weighing-with-driver-supplied-functions ?16:50
hemnanice16:50
hemnathanks16:50
winston-davishay, DuncanT replacing scheduler patches should be ready in a day or 2.16:50
*** japplewhite has quit IRC16:50
avishaybswartz: i like that BP16:50
*** rongze_ has joined #openstack-meeting16:51
DuncanTwinston-d: I've got patches in a holding pattern waiting on Avishay's unit test rewrite to land16:51
*** japplewhite has joined #openstack-meeting16:51
*** dcramer_ has joined #openstack-meeting16:51
avishaywinston-d: cool.  note also that 'chance' has that silly ignore_hosts thing...not sure if it needs to stay16:52
avishaythingee: since you're the resident mock expert, can you review that one and free up DuncanT ?16:52
thingeeavishay: are you going to pass the bp onto winston-d then?16:52
*** rongze__ has joined #openstack-meeting16:52
*** rongze has quit IRC16:52
thingeeavishay: sure16:53
avishaythingee: yep16:53
winston-davishay: i prefer no -> 'ignore_hosts', force_hosts16:53
avishaythingee: BTW, mock is a million times better than mox16:53
thingeeavishay: I think dosaboy has taught me a thing or two from previous reviews with mock, but I'll take it :)16:53
*** caitlin56 has quit IRC16:53
avishaythingee: :)16:53
thingeebswartz: ping me later about the bp? or jgriffith whenever he wakes up :)16:54
avishaythingee: reassigned to winston-d16:54
winston-dthingee, DuncanT, avishay, hemna do you guys really want to make scheduler aware pools inside one back-end?16:54
*** comay has joined #openstack-meeting16:55
*** Guest75482 has quit IRC16:55
bswartzthingee: sorry I got distracted16:55
avishaywinston-d: i think it will help scalability16:55
bswartzthingee: yes I'm working on that one16:55
*** caitlin56 has joined #openstack-meeting16:55
*** mestery has joined #openstack-meeting16:56
thingeewinston-d: I'm not sure I follow. Though I've worked / reviewed a little with scheduler.16:56
winston-dpools inside back-ends, small pools inside pools, smaller poools ...16:56
*** rongze_ has quit IRC16:56
*** japplewhite has quit IRC16:56
DuncanTwinston-d: I'm not sure of the point, but I do remember there being talk of it16:56
*** rgerganov has joined #openstack-meeting16:57
winston-dthingee: well, whether there's oone pool or multiple pools within a back-end, it's transparent to scheduler, for now.16:57
avishaybswartz: can you update the BP with its motivation please?16:57
bswartzwinston-d: almost16:57
bswartzavishay: yes16:57
winston-dDuncanT, bswartz do you remember if we have any consensus about that?16:57
thingeeavishay, bswartz: yeah I just want to know if its been started yet16:57
thingeeit was marked unknown16:57
*** mdenny has quit IRC16:57
*** mdenny has joined #openstack-meeting16:58
bswartzit's transparent until the scheduler picks the wrong backend and there's a failure16:58
*** garyk has joined #openstack-meeting16:58
hemnawinston-d, the pools are part of volume types for our backend16:58
*** ccorrigan has joined #openstack-meeting16:58
xyang__winston-d: one backend should be able to manage multiple pools16:58
winston-dxyang__: i'm fine with that, but not sure if pools should be expose to Cinder16:58
*** pnavarro has quit IRC16:59
bswartzhere's one motivation: suppose a backend has 2 pools with 50GB space each -- it reports 100GB capacity to the scheduler, if the scheduler sends a 100GB create request, it will fail. It would be better if the backend could just report that it has 2 pools of 50GB each16:59
thingeealright lets take the discussion for pools into #openstack-cinder17:00
thingeewe're out of time17:00
*** japplewhite has joined #openstack-meeting17:00
bswartzthat's a simple example, there are more complicated ones -- I'll update teh BP though17:00
thingee#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Wed Dec 11 17:00:08 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-12-11-16.09.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-12-11-16.09.txt17:00
thingeethanks all!17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-12-11-16.09.log.html17:00
winston-dthingee: thx!17:00
hemnabswartz, can't the scheduler send in the volume type in the request to the driver ?17:00
* hartsocks waves17:00
*** winston-d has left #openstack-meeting17:00
hartsocks#startmeeting VMwareAPI17:01
openstackMeeting started Wed Dec 11 17:01:07 2013 UTC and is due to finish in 60 minutes.  The chair is hartsocks. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: VMwareAPI)"17:01
*** tjones has joined #openstack-meeting17:01
*** skolathur has joined #openstack-meeting17:01
openstackThe meeting name has been set to 'vmwareapi'17:01
*** zhiyan has left #openstack-meeting17:01
*** jungleboyj has left #openstack-meeting17:01
hartsockswho's around?17:01
*** avishay has left #openstack-meeting17:01
garykhi17:01
tjoneshi17:01
*** skolathur has quit IRC17:01
tjonesnot to rub it in - but vmware has food trucks here this morning :-D17:01
rgerganovhello17:01
hartsocksheh.17:02
*** joel-coffman has quit IRC17:02
*** glucas has joined #openstack-meeting17:02
*** zhiyan has joined #openstack-meeting17:02
tjonesi should say vmware palo alto17:02
*** herndon has joined #openstack-meeting17:02
garyknice - was there one with potatoes on a stick?17:02
*** thingee has left #openstack-meeting17:02
tjonesnot that one17:02
garyk:)17:02
tjonesfrench toast, biscuits and grazy, egg sandwiches17:02
hartsocksI had food trucks come by my house sometimes, but my neighbors complained.17:03
*** greghill has joined #openstack-meeting17:03
hartsocks:-)17:03
tjonesnot to hijack the meeting17:03
*** n0ano has joined #openstack-meeting17:03
hartsocks*lol* s'okay17:03
*** mdenny has quit IRC17:04
hartsocksI've not posted the agenda in a while because it's always the same...17:04
hartsocks#link https://wiki.openstack.org/wiki/Meetings/VMwareAPI#Agenda17:04
hartsocksWe're in the part I call "salutations"17:04
*** mdenny has joined #openstack-meeting17:04
*** herndon has quit IRC17:04
hartsocksYou like that I officially made banter part of the official meeting agenda :-)17:04
tjoneslol17:04
dimso/17:04
*** HenryG has quit IRC17:04
*** dcramer_ has quit IRC17:05
*** jhenner has quit IRC17:05
*** markwash has joined #openstack-meeting17:05
garyk\o/17:05
*** HenryG has joined #openstack-meeting17:05
rgerganov\m/17:05
hartsocks(╯°□°)╯17:05
garykok, that wins.17:05
hartsocksI totally stole that one.17:06
*** bswartz has left #openstack-meeting17:06
hartsocksSo, we need to get any blueprints we want included in Icehouse-2 ready to go in the next 7 days.17:06
hartsocks#topic blueprints17:06
*** openstack changes topic to "blueprints (Meeting topic: VMwareAPI)"17:06
*** electrichead has left #openstack-meeting17:06
hartsocksI've been working on a list...17:07
hartsocksI've identified 4 bp for icehouse 2….17:07
hartsocksin no particular order...17:07
hartsocks#link https://blueprints.launchpad.net/openstack/?searchtext=vmware-image-cache-management17:07
*** jlibosva has quit IRC17:07
garykquick update on that one17:07
hartsocksgaryk: I think that's yours...17:07
hartsockscool17:08
*** kgriffs is now known as kgriffs_afk17:08
garykat the moment it is blocked. we are in the process of making the libvirt code generic and then hopefully that will free up this one17:08
garykit will require a rebase in a few days time and then it is ready for review17:08
*** slagle has quit IRC17:09
garykpatches are https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/vmware-image-cache-management,n,z17:09
*** dougshelley66 has joined #openstack-meeting17:09
zhiyanhello folks, this my first time to join vmwareapi weekly meeting. i'm very interesting to allow vmware driver support ova image, so can i get some time in open discussion part? i have some question around it to like get your inputs..thanks17:09
garykplease note that this is all based on https://review.openstack.org/#/c/52630/ (which has been in review for a very very very …very long time)17:09
garykzhiyan: wecome17:10
zhiyangaryk: sorry to interrupt your discussion, but i have one queston on image-cache17:10
zhiyangaryk: hello17:10
hartsockszhiyan: cool, we have open discussion every week at the last 10 minutes or so.17:10
garykzhiyan: sure, please ask17:10
zhiyanhartsocks: hello17:10
hartsockszhiyan: obviously go ahead if it's on topic.17:11
*** radu has joined #openstack-meeting17:11
zhiyangaryk: you know currently we see image always a file, but i see image it's resource17:11
*** rongze__ has quit IRC17:11
*** radu is now known as Guest8620117:11
*** pschaef has quit IRC17:11
*** safchain has quit IRC17:11
garykzhiyan: not sure i understand. can you please elaborate?17:11
zhiyangaryk: in libvirt's cache fetching and cache manger, we alway use "file" approach to do handle that, for example, release image just always means delete file17:12
*** mdenny has quit IRC17:12
garykah, ok. here is is similar17:12
*** MIDENN_ has joined #openstack-meeting17:12
*** Guest86201 has left #openstack-meeting17:12
*** Guest86201 has joined #openstack-meeting17:12
*** nprivalova has joined #openstack-meeting17:12
garykwhen a vm is spawned we check if the image is on a datastore. if not then we load it from glance. for example a linked clone image. the vm then uses this when it spawns17:13
*** akuznetsov has joined #openstack-meeting17:13
*** Guest86201 has quit IRC17:13
garykwhen these images are no longer used they should be aged similarly to those with libvirt - it ensures that these files do not checw up all of the disk on the datastore17:13
zhiyanbut maybe we need some handler to handle image fetching and release. for example, if we do some zero-copy approach to prepare template/cached image, we should using some particular approach to remove image from datastore17:14
*** pnavarro has joined #openstack-meeting17:14
garykthat is something which we are working on in glance at the moment17:14
*** resker has joined #openstack-meeting17:14
*** weshay has quit IRC17:14
hartsockszhiyan, garyk: maybe you guys could chat about this in #openstack-vmware or #openstack-nova later? This seems like implementation level discussion. I encourage it but we have 5 other BP I want to at least touch on today. :-)17:14
garyksure - please see https://review.openstack.org/#/c/58883/17:15
zhiyanhartsocks: sure :)17:15
*** esker has quit IRC17:15
hartsocksnp17:15
*** _radu has joined #openstack-meeting17:15
hartsocksTo recap the caching BP. I found 2 other BP with the keyword "cache" in the name. I think that probably causes some inquiries.17:16
hartsocksSo far I don't see these as related in any real way.17:16
*** weshay has joined #openstack-meeting17:16
*** DrBacchus has quit IRC17:16
*** caitlin56 has quit IRC17:16
hartsocksBut, we may have to clarify things to core-reviewers who are in a hurry, so be prepared.17:16
*** caitlin56 has joined #openstack-meeting17:17
*** rongze has joined #openstack-meeting17:17
*** glucas has left #openstack-meeting17:17
hartsocks#link https://blueprints.launchpad.net/nova/+spec/vmware-vsan-support17:17
hartsocksvuil: ping?17:17
tjonesif he's not here - i recall that at our last standup he said he is just adding tests17:17
*** vuil has joined #openstack-meeting17:17
hartsockscool.17:18
tjonesso it seems on track for i-217:18
garykat the moment Vui has posted a wip patch17:18
garykhttps://review.openstack.org/#/c/53976/17:18
garykthis is progressing nicely17:18
*** johnthetubaguy has quit IRC17:18
vuilsorry I just got in17:18
hartsocksWe just need the BP to be targeted and ready for review by next week.17:18
*** caitlin56 has left #openstack-meeting17:18
hartsocksThe patch can be WIP for a few more weeks.17:18
hartsocksvuil: talkin' about ya'17:18
garykhartsocks: not sure i understand. what needs to be ready for review?17:19
hartsocksThe BP17:19
vuilIsn't it approved?17:19
hartsocksWe need to have the Blueprints out of draft, approved, and in progress.17:19
*** thomasem has quit IRC17:20
hartsocksYep. This one is approved so we're in good shape there.17:20
*** wolsen has left #openstack-meeting17:20
hartsocksSounds like it's making good progress too.17:20
vuilyep17:20
*** SergeyLukjanov has joined #openstack-meeting17:20
hartsocksNext up...17:20
hartsocks#link https://blueprints.launchpad.net/oslo/+spec/pw-keyrings17:20
hartsockswhich is actually an Oslo BP...17:20
hartsocksWe were going to leverage this for getting our passwords out of the .conf files.17:21
hartsocksLooks like this is stalled.17:21
hartsocksWe will have to take over this BP or propose an alternate. I've put that on my plate to follow up on.17:21
tjonesohhh - what i said about you working with rado on sso was wrong oops.  2 diff issues17:21
tjonesi'll let him know17:21
tjonesgot confused17:22
hartsocksThere is an SSO thing over in keystone.17:22
tjonesyes i get it now17:22
rgerganovone way to avoid usernames/passwords in clear text is to use SSO tokens17:22
hartsocks2 approaches 1 problem...17:22
tjonesyes17:22
hartsocksrgerganov… yep… that's what the Keystone Federation thing is about...17:22
* hartsocks digs for link17:22
hartsocks#link https://wiki.openstack.org/wiki/Keystone/Federation/Blueprint17:23
dimshartsocks, python-openstackclient has keyring support, may be there's something can be extracted from there17:23
hartsocksThis is something I planned on coordinating for icehouse-3 at the soonest.17:23
hartsocksdims: cool!17:23
dolphm(that bp is probably going to be dropped as it's being replaced with several other blueprints with narrower scope)17:23
hartsocksFederation?17:23
dolphmyes17:23
rgerganovok, but we can add support for VMware SSO tokens before the federation happens, right?17:23
hartsocksWhat we need at the Nova driver level is to hook SAML tokens into the driver.17:24
rgerganovhartsocks, right17:24
hartsocks.. er… security context.17:24
*** MaxV has quit IRC17:24
hartsocksI had hoped to lift authentication concerns out of the driver altogether and do SSO "the right way"17:24
*** MaxV has joined #openstack-meeting17:25
hartsocks#action follow up on SSO with rgerganov, hartsocks, and dolphm17:25
*** SumitNaiksatam has quit IRC17:25
rgerganovhartsocks, ok we can continue the discussion after the meetings17:25
hartsockswe should probably chat and do an etherpad on this one. I'll document what I have so far.17:25
hartsocksI have 2 more Blueprints that I'm tracking...17:26
hartsocks#link  https://blueprints.launchpad.net/nova/+spec/autowsdl-caching17:26
hartsocksWhich I'm breaking into 2 phases… 1 will be a naive CLI tool17:26
hartsockswhich I'll post shortly.17:27
hartsocksPhase 2 will be the "auto" part which will make the WSDL repair seamless to the driver's admin.17:27
hartsocksBut I need to figure out how to work with Oslo for that (that's new for me).17:27
hartsocksLast up...17:28
hartsocks#link https://blueprints.launchpad.net/nova/+spec/config-validation-script17:28
tjonesis that for i-2?17:28
hartsockstjones: that's currently owned by you17:28
tjonesfeel free to take it :-D17:28
hartsocksah, nope...17:28
hartsocksit's i-317:28
tjonesyeah that's what i was thinking too17:28
hartsocksCould you assign it to me?17:28
hartsocksI currently have no privs on it.17:29
*** MaxV has quit IRC17:29
*** sushils has quit IRC17:30
hartsocksI did chat with ogelbukh last week.17:30
*** blamar has joined #openstack-meeting17:30
*** gyee has joined #openstack-meeting17:30
hartsocksThey are actually making a fair bit of progress on the static validation component.17:30
hartsocksThere will need to be a service-level validation component … that's left unimplemented and probably needs some discussion.17:30
*** jchan has quit IRC17:31
hartsocks#link https://etherpad.openstack.org/p/w5BwMtCG6z17:31
hartsocksSo… that's all the BP I'm currently tracking for the team.17:31
hartsocksDo we need to track others?17:31
*** reed has quit IRC17:32
hartsocksnice 30 minute mark and I managed to list all of them! Sorry for the rush.17:32
*** Fdot has quit IRC17:33
*** dims has quit IRC17:33
*** DrBacchus has joined #openstack-meeting17:33
tjonessursure17:34
tjonessure17:34
*** tjones has quit IRC17:34
garykhartsocks: i think that next week we should try and track the glance and cinder ones too - but we can take that offline17:34
*** bgorski has joined #openstack-meeting17:34
hartsocksokay cool. I know they have some things in progress but I've not researched them yet.17:34
hartsocksanything else before we move to bugs?17:34
hartsocks#topic bugs17:35
*** openstack changes topic to "bugs (Meeting topic: VMwareAPI)"17:35
hartsocksI have 7 bugs I'm tracking for the team that are at priority High or Critical...17:36
hartsocksheh… my report script links only reviews tho...17:36
*** kgriffs_afk is now known as kgriffs17:36
*** nprivalova has quit IRC17:36
hartsocks#link  https://review.openstack.org/5263017:36
hartsocks#link https://review.openstack.org/4327017:36
hartsocks#link https://bugs.launchpad.net/nova/+bug/118004417:37
uvirtbotLaunchpad bug 1180044 in nova "nova failures when vCenter has multiple datacenters" [High,In progress]17:37
*** bpoulos has quit IRC17:37
*** coolsvap has quit IRC17:37
hartsocksthere… I'll link the bugs in here.17:37
*** luQAs has quit IRC17:37
hartsocksgaryk: that's yours…17:37
garykyea, that one has been in review for a very long time… it is critcial for backports and sadly we missed the boat for the stable havana17:37
hartsocksbummer.17:38
*** winston-1 has left #openstack-meeting17:38
garykuoside is i get to rebase it once every week or so17:38
hartsocksI should be able to do more reviews now. I wanted to pull this one and do functional testing on it.17:38
*** nelsnelson is now known as nelsnelson_away17:38
*** dims has joined #openstack-meeting17:39
hartsocksBTW: I will do my bug reports once a week in conjunction with this meeting now. It's probably more topical that way.17:39
garykok17:39
*** akuznetsov has quit IRC17:39
hartsocksThis bug is so important it's actually listed twice on my report :-)17:39
hartsocks#link https://bugs.launchpad.net/nova/+bug/123004717:40
uvirtbotLaunchpad bug 1230047 in nova "VMware: spawning large amounts of VMs concurrently sometimes causes "VMDK lock" error" [High,In progress]17:40
*** oubiwann-lambda has quit IRC17:40
*** tjones has joined #openstack-meeting17:40
hartsocksgaryk: you *again* …17:40
tjonesim back - macbook crashed.17:40
tjonesyes i will transfer the BP to you - that;s the last thing i saw for me17:40
hartsockstjones: cool, I have no privs on that BP until you do so I can't alter it.17:41
*** ygbo has quit IRC17:41
tjoneshatsocks: i am sure you have moved on.  but could you spilt that into 2 BP?  Once for service validation and one for config validation?17:41
hartsockstjones: I'm listing the 6 tip priority bugs right now.17:41
*** sneelakantan_ has quit IRC17:41
*** chandankumar has quit IRC17:41
hartsockstjones: yeah, I'll do that and document BP dependencies once I can edit it.17:42
tjonesL0D17:42
tjones:-D17:42
hartsocks#link https://review.openstack.org/#/c/58598/17:42
*** BrianTorres-Gil has joined #openstack-meeting17:42
hartsocksthis concurrent downloads thing is just languishing… so I guess we all need to focus on this one a bit.17:43
*** nelsnelson_away has quit IRC17:43
*** thomasem has joined #openstack-meeting17:43
hartsocks#link https://bugs.launchpad.net/nova/+bug/124684817:43
uvirtbotLaunchpad bug 1246848 in nova "VMWare: AssertionError: Trying to re-send() an already-triggered event." [High,In progress]17:43
garyki have dealt with that (and it works pretty well). just need to get it reviewed….17:43
*** IlyaE has quit IRC17:43
garykthe concurrent downloads that is17:43
*** thomasem has quit IRC17:44
*** thomasem has joined #openstack-meeting17:44
hartsocksyeah, I think reviews are the #2 priority after getting any icehouse-2 BPs that are still un-approved marked as 'approved'17:44
hartsocksOr maybe these are both #1 priorities :-)17:45
*** NehaV has joined #openstack-meeting17:45
hartsocks#link https://bugs.launchpad.net/nova/+bug/125817917:45
uvirtbotLaunchpad bug 1258179 in nova "VMware: timeouts due to nova-compute stuck at 100% when using deploying 100 VMs" [High,In progress]17:45
tjoneshartsocks: this one is still stuch with -2 from russellb.  i've addressed the issues he raised but i need the -2 removed for people to review it https://review.openstack.org/#/c/56287/17:45
hartsocksugh.17:45
*** Shaan7 has joined #openstack-meeting17:46
*** Shaan7 has joined #openstack-meeting17:46
hartsocks#action ping russellb on bug/125102117:46
hartsocksI've got only 2 more "high" to us priority bugs… these are marked "medium" to the nova community...17:46
hartsocks#link https://bugs.launchpad.net/nova/+bug/125703817:47
uvirtbotLaunchpad bug 1257038 in openstack-vmwareapi-team "VMware: instance names can be edited, breaks nova-driver lookup" [High,In progress]17:47
*** SumitNaiksatam has joined #openstack-meeting17:47
hartsocksThat one needs reviews.17:47
hartsocksIt's a Nova to vCenter robustness issue… I filed it because right now we use the vCenter name for the VM to link the VM to Nova's control. That's fragile.17:48
garykthis one has actaully been addressed by https://review.openstack.org/#/c/60259/17:48
hartsocksFortunately the fix is nice and backwards compatible.17:48
garykthe patch proposed by sidarth closes a edge case when the value is not set. issue here is the cpu spike17:48
hartsocksWell, I took a moment to talk about this one here because I'm sure it's not clear what I'm complaining about in the bug.17:49
hartsocksThe "edge case" is what I'm complaining about.17:49
garykso https://review.openstack.org/#/c/59571/ make it really robust17:49
garykyup, agreed.17:50
hartsocksright.17:50
hartsocksactually, I feel I should never have approved the design we shipped in Havana. The vCenter name for an instance is a "vanity" kind of thing. It's far too easy to change and it makes vCenter hard to use.17:50
hartsocksbut that's a longer discussion.17:50
hartsocksI classed it as Medium, but I would like to see the change backported … it should be backportable all the way through Grizzly.17:51
tjonesyes!  and it's an easy one (for once)17:51
hartsocksIt's a longer range type of fix though and nobody's going to be unable to deploy OpenStack on vCenter without it.17:52
hartsockslast bug on my short list:17:52
hartsocks#link https://bugs.launchpad.net/nova/+bug/121326917:52
uvirtbotLaunchpad bug 1213269 in openstack-vmwareapi-team "_check_if_folder_file_exists only checks for metadata file" [High,In progress]17:52
hartsocks#link https://review.openstack.org/#/c/48544/17:53
tjonesi broke minesweeper17:53
tjoneswith that one17:53
hartsocksnice!17:53
tjonesi'll get back on it17:53
*** rushiagr has left #openstack-meeting17:53
tjonesyeah!  actually i was happy as it caught something my testing did not!17:53
*** pablosan has joined #openstack-meeting17:53
hartsocksSo that's all the bugs I have in priority order.17:53
tjonesany new ones to triage?17:54
*** ArthurBerezin has left #openstack-meeting17:54
*** vkmc has quit IRC17:54
*** bgorski has quit IRC17:54
zhiyanopen discussing? :)17:54
hartsocks#link  http://goo.gl/pTcDG17:54
hartsocksMan, I just cleaned up those triage area. I'll run triage later.17:55
tjones*answers my own question* #link https://bugs.launchpad.net/nova/+bug/125998117:55
uvirtbotLaunchpad bug 1259981 in nova "VMware: factor out the management of unit numbers" [Undecided,New]17:55
tjonesjust one17:55
hartsocksOkay.17:55
hartsocksLet's do triage outside the meeting this week.17:55
tjonesok17:55
hartsocks#topic opendiscussion17:55
*** openstack changes topic to "opendiscussion (Meeting topic: VMwareAPI)"17:55
*** sayali_ has joined #openstack-meeting17:56
hartsocksWe have #openstack-vmware for any other discussion that won't fit into the meeting BTW.17:56
zhiyanthanks hartsocks17:56
zhiyanhttps://etherpad.openstack.org/p/vmware-ova-support17:56
garykhow do we get the food trucks to my side of the world?17:56
*** SlickNik has joined #openstack-meeting17:56
zhiyanfor save time, i posted my text at there17:56
tjones:-D  i can send you a picture17:56
*** SlickNik has left #openstack-meeting17:56
*** derekh has quit IRC17:57
zhiyanthanks for your input!17:57
hartsockszhiyan: nice. Sorry to have cut the open discussion part short this week. We have a deadline next week.17:57
*** sayali_ has left #openstack-meeting17:57
zhiyanhartsocks: sure, np at all17:57
hartsocksJust a reminder if you have a BP that isn't *approved* for Icehouse-2 by this time next week you might not make it at all no matter how far along your code is.17:58
hartsocksI know there's a general policy to −2 anything that is milestone targeted but the BP isn't approved. So just watch for that, it can ruin your release cycle.17:58
*** SridarK has joined #openstack-meeting17:59
hartsockszhiyan: yeah, I think this is one of the glance BP that garyk mentioned … I should probably track those for the team too...17:59
hartsocksThis one isn't targeted for icehouse-2 either...18:00
hartsocksit is approved tho'18:00
hartsockswhoops… out of time.18:00
zhiyanhartsocks: yes, and i think this work should involve glance and nova both18:00
tjonesmoving to #openstack-vmware18:00
hartsocksWe're over in #openstack-vmware for anything you're not 100% belongs on #openstack-nova18:00
hartsocks#endmeeting18:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:01
openstackMeeting ended Wed Dec 11 18:01:00 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-12-11-17.01.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-12-11-17.01.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-12-11-17.01.log.html18:01
*** beyounn has joined #openstack-meeting18:01
*** yisun has joined #openstack-meeting18:01
*** olkonami has joined #openstack-meeting18:02
*** lexx has joined #openstack-meeting18:02
*** sdake_ has joined #openstack-meeting18:02
SumitNaiksatamhi!18:02
RajeshMohanHi18:02
SridarKhi18:02
yisunhi18:02
gduanHi18:02
*** japplewhite has left #openstack-meeting18:02
olkonamihi18:02
SumitNaiksatamSridarK, RajeshMohan yisun gduan olkonami: Hi18:02
SumitNaiksatamBrianTorres-Gil: there?18:03
BrianTorres-GilHi Sumit, yes I'm here.18:03
SumitNaiksatamgreat18:03
SumitNaiksatam#startmeeting Networking FWaaS18:03
openstackMeeting started Wed Dec 11 18:03:54 2013 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:03
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:03
openstackThe meeting name has been set to 'networking_fwaas'18:04
SumitNaiksatamthanks everyone for joining18:04
*** tjones has left #openstack-meeting18:04
*** hartsocks has left #openstack-meeting18:04
*** NehaV has left #openstack-meeting18:04
SumitNaiksatamthe main agenda for today's meeting was to sync up with the PTL, my understanding was that he was going to join this meeting18:04
SumitNaiksatamhowever, i don't see mark on IRC18:05
*** beyounn has quit IRC18:06
*** devlaps has joined #openstack-meeting18:06
SridarKHmm! should we wait for a bit to see if he will join18:06
*** reed has joined #openstack-meeting18:06
SumitNaiksatamyeah18:06
*** jbernard has left #openstack-meeting18:07
SumitNaiksatamso i just pinged the -neutron channel18:07
SumitNaiksatamdon't see him there either18:07
SumitNaiksatambummer :-(18:07
SumitNaiksatam#topic service_type framework18:07
*** openstack changes topic to "service_type framework (Meeting topic: Networking FWaaS)"18:07
*** bgorski has joined #openstack-meeting18:08
SumitNaiksatamhttps://review.openstack.org/#/c/60699/18:08
*** hemna has quit IRC18:08
gduanI submitted code review18:08
SumitNaiksatamgaryduan thanks for patch18:08
gduanworking on unit test18:08
SumitNaiksatamok great18:08
gduanI see tempest test are failing18:08
*** cody-somerville has quit IRC18:08
SumitNaiksatamok, tests are failing on what?18:09
gduanin fact, gate-neutron-python2718:09
gduanI guess it's unit test issue18:09
gduanI will fix it, no problem18:09
SumitNaiksatamok18:09
SumitNaiksatamits breaking existing UT?18:10
*** bswartz has joined #openstack-meeting18:10
gduanright18:10
SumitNaiksatamok, that should be easier than tempest :-)18:10
gduanseems like, I will double check18:10
SumitNaiksatamok thanks18:10
SridarKi heard from one of my colleagues (pcm_) that he was seeing a lot issues with tox (if he upped the memory to 8G on his VM) things were okay18:10
*** xyang__ has quit IRC18:10
SridarKperhaps something to check - not sure if u have the same issue18:11
SumitNaiksatamSridarK: yes, i was following that18:11
SumitNaiksatamSridarK: however, gduan's tests are failing in the gate18:11
SridarKok18:11
SumitNaiksatamSridarK: and that infra should be set up properly18:11
SridarKtrue, stand corrected18:11
SumitNaiksatamits a regression18:11
*** terryw has joined #openstack-meeting18:12
gduanwe need tempest on this review too, right?18:12
*** bswartz has left #openstack-meeting18:12
*** akuznetsov has joined #openstack-meeting18:12
SumitNaiksatamgduan: absolutely18:13
gduanok18:13
SumitNaiksatamgduan: we need it for existing resources and api, and anything new that we add18:13
SumitNaiksatamgduan: however, we have to first get the feature merged before the tempos tests can be merged18:13
SumitNaiksatamits a kind of a chicken and egg18:13
gduanok. I will add unit test first.18:14
*** rakhmerov has quit IRC18:14
SumitNaiksatamgduan: yeah, thats a good start (rather must :-P)18:14
*** otherwiseguy has quit IRC18:15
*** slagle has joined #openstack-meeting18:15
SumitNaiksatamokay, i was still hoping that mark would join before we go to the next item in the agenda18:15
SumitNaiksatam#topic Service Objects18:16
*** openstack changes topic to "Service Objects (Meeting topic: Networking FWaaS)"18:16
SumitNaiksatamyisun: how is this coming along?18:16
SumitNaiksatam#link https://blueprints.launchpad.net/neutron/+spec/fwaas-customized-service18:16
*** rgerganov has quit IRC18:16
yisunhad most code, but stuck on some db access issues18:16
SumitNaiksatamyisun: ok18:17
yisunstill trying to find out reason18:17
SumitNaiksatamyisun: do we still plan to target this for Icehouse?18:17
yisunI will try18:17
SumitNaiksatamok18:17
SumitNaiksatamyisun: the reason i ask is, the blueprint's series goal is not set18:17
yisunreally, I did it once18:18
yisunok, I will set it again18:18
SumitNaiksatamyisun: this will not show up on the PTL's radar if the series goal and milestone target is not set18:18
*** belmoreira has quit IRC18:18
SumitNaiksatamyisun: i had requested gduan to convey this to you last week18:18
yisunI will put I318:19
*** belmoreira has joined #openstack-meeting18:19
SumitNaiksatamyisun: ok18:19
SumitNaiksatamyisun: that said i am not trying to push you for this18:19
yisun:-)18:19
yisunBut I may need some help to fix the DB18:19
SumitNaiksatamyisun: since you wanted to get this in, i want to make sure that the procedural issues are taken care off correctly18:19
SumitNaiksatamyisun: and things don't slip through the cracks18:20
yisunno problem18:20
yisunMy current issue is that if the zone can not get in ice houst18:20
yisunthen we may have to push all to J18:20
SumitNaiksatamyisun: good segue18:20
SumitNaiksatam#topic zones18:20
*** openstack changes topic to "zones (Meeting topic: Networking FWaaS)"18:20
SumitNaiksatam#link https://blueprints.launchpad.net/neutron/+spec/fwaas-zones-api18:21
*** radez is now known as radez_g0n318:21
SumitNaiksatamyisun: per last meeting, general feeling was to keep this in discussion for I and target patch for merge in J18:21
yisunok18:22
SumitNaiksatamthis is so that we don't introduce too much feature churn, and avoid disrupting the ongoing efforts on Neutron stabilization and parity for nova networking18:22
*** nermina has joined #openstack-meeting18:22
SumitNaiksatamwe also need to do our bit in terms of tempest tests18:22
RajeshMohanSridar/others: Can we meet f2f on this?18:23
SumitNaiksatamBrianTorres-Gil: you were not in the meeting last time, hope you are in the loop on this18:23
RajeshMohanJust want to split the work so that I can start working on it18:23
*** belmoreira has quit IRC18:23
SridarKSumitNaiksatam: RajeshMohan: Hoping we can do this tomorrow on the tempest tests18:23
*** mdurnosvistov has quit IRC18:24
*** hemanthravi has joined #openstack-meeting18:24
RajeshMohanok18:24
RajeshMohanOr we can chat after the meeting18:24
SumitNaiksatamRajeshMohan: lets do it after this meeting18:25
RajeshMohanSridar: Any updates from last week?18:25
SumitNaiksatamokay, i guess BrianTorres-Gil is in silent agreement18:25
*** Mandell has joined #openstack-meeting18:25
RajeshMohanYou said that you were updating the document - any help on that?18:25
SumitNaiksatamRajeshMohan: i believe the plan was to discuss this week (but i will let SridarK respond)18:26
SridarKRajeshMohan: Still need to figure out on the dependencies - will sync with u18:26
RajeshMohanok, thanks.18:26
SridarKhopefully tomorrow we can get to more clarity18:26
BrianTorres-GilYea, works for me18:27
yisunSumit, sorry, I was driving, if we push zone to J, I may push service object to J too18:28
SumitNaiksatamBrianTorres-Gil: ok thanks, i was just going to say that you were in silent agreement :-)18:28
SumitNaiksatamyisun: okay, we can discuss18:28
*** DrBacchus has quit IRC18:29
*** cschwede has joined #openstack-meeting18:29
*** DrBacchus has joined #openstack-meeting18:29
yisunsummit, I'm not push it18:29
yisunWe do need to have tempest done fist18:29
yisunI agree with everyone on it18:30
yisunmaking the system stable is more important18:30
SumitNaiksatamyisun: great, glad that we all agree on that18:30
yisun:-)18:31
SumitNaiksatamthe other two items on the blueprint agenda were FWaaS service insertion, and apply/commit operation18:31
SumitNaiksatamthere is nothing new here that we have not discussed within the team yet18:32
SumitNaiksatamso this was mostly discussion with the PTL18:32
SumitNaiksatamany new developments/thoughts you want to add on this?18:32
RajeshMohanany updates on tempest?18:33
SridarKSumitNaiksatam: On Service insertion - have been in discussion with colleagues as well and we are on board18:33
*** pablosan has quit IRC18:34
*** d0ugal has quit IRC18:34
RajeshMohanSumit: last week you said you neeed some help18:34
SumitNaiksatamSridarK: thanks18:34
*** elo has left #openstack-meeting18:35
SumitNaiksatamRajeshMohan: yes, help always welcome :-)18:35
SumitNaiksatamlet's discuss18:35
*** Shaan7 has quit IRC18:35
RajeshMohanSumit: ok18:35
SumitNaiksatambtw, this patch was posted:18:35
SumitNaiksatamhttps://review.openstack.org/#/c/60190/18:35
SumitNaiksatamis gongysh around?18:35
SumitNaiksatamwe already have a blueprint for this activity, to incorporate service insertion (not just router binding)18:36
SumitNaiksatam#topic Service Insertion for Firewall18:37
*** openstack changes topic to "Service Insertion for Firewall (Meeting topic: Networking FWaaS)"18:37
SumitNaiksatam#link https://blueprints.launchpad.net/neutron/+spec/fwaas-service-insertion18:37
*** radez_g0n3 is now known as radez18:37
SumitNaiksatamso the patch https://review.openstack.org/#/c/60190/ will need to reconcile with this effort18:37
SumitNaiksatami think gongysh is not around18:37
SumitNaiksatamok moving on18:37
SumitNaiksatam#topic bugs18:38
*** colinmcn_ has quit IRC18:38
*** colinmcnamara has quit IRC18:38
*** openstack changes topic to "bugs (Meeting topic: Networking FWaaS)"18:38
*** pablosan has joined #openstack-meeting18:38
SumitNaiksatami just noticed this:18:38
SumitNaiksatamhttps://bugs.launchpad.net/neutron/+bug/125843818:38
uvirtbotLaunchpad bug 1258438 in neutron "Can't create a firewall per tenant" [High,Confirmed]18:38
SumitNaiksatamwe need to fix this asap18:39
SumitNaiksatamit seems that the bug reported has taken this up18:39
SumitNaiksatamakihiro has confirmed it18:39
*** nati_ueno has joined #openstack-meeting18:40
*** IlyaE has joined #openstack-meeting18:40
SumitNaiksatamdid anyone test with more than one tenant in their earlier tests?18:40
SumitNaiksatami have to go back and check if there wasn't a UT for this case18:40
SridarKSumitNaiksatam: I think Dan had done some of those tests18:41
*** blamar has quit IRC18:41
SumitNaiksatamSridarK: okay18:41
SumitNaiksatamanyone has time to confirm this?18:41
*** blamar has joined #openstack-meeting18:41
RajeshMohanI have tested with more than one client18:41
*** d0ugal has joined #openstack-meeting18:41
RajeshMohanInitially18:41
RajeshMohanmust be some new change18:41
SumitNaiksatamRajeshMohan: you mean, more than one tenant, right?18:41
RajeshMohanYes - I have demos working with more than one client - close to havana release though18:42
SumitNaiksatamRajeshMohan: i think the check for limiting to one firewall per tenant went in later (but in Havana)18:42
RajeshMohandid we add any code to restrict number of firewall recently18:42
SumitNaiksatamRajeshMohan: it was towards the end of havana18:42
RajeshMohanI must have missed that change18:43
SumitNaiksatamRajeshMohan: if this bug is correct, it was that code which introduced the issue18:43
SumitNaiksatamat any, rate any one have time to verify this (you can follow up with the fix as well)18:43
*** AaronGr is now known as AaronGr_afk18:43
RajeshMohanI will confirm today18:43
SumitNaiksatamRajeshMohan: great, thanks!18:44
SumitNaiksatamSridarK: any plans on this: https://bugs.launchpad.net/neutron/+bug/125084118:45
uvirtbotLaunchpad bug 1250841 in neutron "Move FWaaS Noop driver to unit tests directory" [Low,Triaged]18:45
SumitNaiksatamwe have this marked for I218:45
SumitNaiksatamwould be nice to get it out of the way18:45
SridarKSumitNaiksatam: will push a patch out soon18:45
*** rossella_s has quit IRC18:45
*** lexx has quit IRC18:45
*** dcramer_ has joined #openstack-meeting18:45
SridarKneeded a few clarifications b4 getting it out - will reach out to u18:45
SumitNaiksatamSridarK: thanks18:46
SumitNaiksatamSridarK: we also have: https://bugs.launchpad.net/neutron/+bug/122347218:46
uvirtbotLaunchpad bug 1223472 in neutron "firewall status does not become ACTIVE when  a router does not exist" [Undecided,Triaged]18:46
SumitNaiksatami believe we are waiting on the insertion to do this?18:46
*** mdomsch has quit IRC18:46
*** gokrokve has quit IRC18:47
*** rakhmerov has joined #openstack-meeting18:47
SridarKSumitNaiksatam: I think some clarification needed to be provided18:47
SumitNaiksatamSridarK: ok18:47
SridarKneed to jog my memory on this18:47
SumitNaiksatamSridarK: alright, lets track it for discussion next time18:48
SridarKwill update - i recall that this was not an issue but let me clarify and take care of this18:48
SumitNaiksatamgduan: https://bugs.launchpad.net/neutron/+bug/122296818:48
SridarKSumitNaiksatam: thanks18:48
uvirtbotLaunchpad bug 1222968 in neutron "Namespace handling is missing in vArmour's FWaaS agent and driver" [Medium,In progress]18:48
*** ivasev has quit IRC18:49
yisunI saw there is a fix18:49
yisunbut it has been pushed out from rc1 by mark18:49
SumitNaiksatamok18:50
*** sushils has joined #openstack-meeting18:50
yisunSumit, what should be do about it?18:50
SumitNaiksatamif this is fixed, then we should invalidate this bug18:50
*** cswartz has joined #openstack-meeting18:50
*** nelsnelson has joined #openstack-meeting18:50
*** anniec has joined #openstack-meeting18:50
*** ChristerThor has joined #openstack-meeting18:50
SumitNaiksatam#topic vendor plugins/drivers18:51
yisunGary submitted patch18:51
*** openstack changes topic to "vendor plugins/drivers (Meeting topic: Networking FWaaS)"18:51
SumitNaiksatam#undo18:51
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x39d5e10>18:51
yisunbut is was not merged to rc118:51
yisunand it is marked as back port potential18:51
gduanSumitNaiksatam: we can discard this bug18:51
*** colinmcnamara has joined #openstack-meeting18:51
*** colinmcn_ has joined #openstack-meeting18:51
SumitNaiksatamgduan: ok, you can invalidate it18:51
SumitNaiksatam#topic vendor plugins/drivers18:52
*** openstack changes topic to "vendor plugins/drivers (Meeting topic: Networking FWaaS)"18:52
gduanSumitNaiksatam: we will cover it with another BP18:52
*** colinmcn_ has quit IRC18:52
SumitNaiksatamgduan yisun SridarK RajeshMohan BrianTorres-Gil: anything we need to discuss regarding your plans18:52
*** colinmcnamara has quit IRC18:52
gduanWe have a BP for rework our fw driver as a plugin driver18:52
SumitNaiksatamis there any dependency or blocker for you to move forward?18:52
SumitNaiksatamgduan: ok, bp link?18:53
*** colinmcnamara has joined #openstack-meeting18:53
*** colinmcn_ has joined #openstack-meeting18:53
SridarKSumitNaiksatam: will need to push our BP out to J with a dependency on Zones18:53
gduanhttps://blueprints.launchpad.net/neutron/+spec/varmour-firewall-plugin18:53
SumitNaiksatamSridarK: okay, got it18:53
SumitNaiksatamgduan: thanks18:53
*** ivasev has joined #openstack-meeting18:54
gduanIt depends on the service type framework BP18:54
BrianTorres-GilWe are spinning our wheels a lot trying to figure out some of the code and structure of Neutron.  Still seeking a good developers guide.18:54
*** thomasem has quit IRC18:54
gduanMight also depend on Service Insertion18:54
SumitNaiksatamgduan: good, i think the PTL has also approved this for I3, so the loop is closed18:54
SumitNaiksatamBrianTorres-Gil: ok18:54
SumitNaiksatamBrianTorres-Gil: welcome to the world of open source :-P18:55
*** peluse has joined #openstack-meeting18:55
SumitNaiksatamBrianTorres-Gil: let the rest of the team know if you need help with anything particular18:55
SumitNaiksatamSridarK (and others in general): it will help to clearly state in your blueprint as to what the dependencies are18:56
SumitNaiksatamthat will help us to prioritize features accordingly, and make their case18:56
SridarKSumitNaiksatam: ok will update the dependency18:56
SumitNaiksatamSridarK: can you add a dependency to the zones bp if appropriate?18:56
SumitNaiksatamthanks18:56
SumitNaiksatamgduan: similar can you please put a dependency on the service type framework and service insertion blueprints18:57
gduanSumitNaiksatam: just added18:57
*** tomesh has joined #openstack-meeting18:58
SumitNaiksatamgduan: thanks, don't see the dependency on service insertion18:58
SumitNaiksatamanyway18:58
SumitNaiksatammoving on18:58
SumitNaiksatam#topic Open Discussion18:58
*** openstack changes topic to "Open Discussion (Meeting topic: Networking FWaaS)"18:58
SumitNaiksatamwe have a couple of mins18:58
gduantrying to find the BP :-)18:59
SumitNaiksatamanything to dicuss?18:59
*** portante has joined #openstack-meeting18:59
SumitNaiksatamgduan: https://blueprints.launchpad.net/neutron/+spec/neutron-services-insertion-chaining-steering18:59
gduanSumitNaiksatam: thanks18:59
SumitNaiksatamwe didn't touch on tempest today, since that is on top of the mind and we are trying to collectively figure our way out19:00
gduanSumitNaiksatam: it might not be a dependency though19:00
*** AaronGr_afk is now known as AaronGr19:00
SumitNaiksatambut that is being targeted with high priority19:00
SumitNaiksatamok, thanks everyone for attending19:00
*** asselin has joined #openstack-meeting19:00
SumitNaiksatamhave good one, bye19:00
SumitNaiksatam#endmeeting19:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:01
gduanbye19:01
openstackMeeting ended Wed Dec 11 19:01:07 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
RajeshMohanbye19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2013/networking_fwaas.2013-12-11-18.03.html19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2013/networking_fwaas.2013-12-11-18.03.txt19:01
SridarKbye19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2013/networking_fwaas.2013-12-11-18.03.log.html19:01
notmynameswift meeting time19:01
notmyname#startmeeting swift19:01
openstackMeeting started Wed Dec 11 19:01:27 2013 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: swift)"19:01
openstackThe meeting name has been set to 'swift'19:01
*** yisun has left #openstack-meeting19:01
notmynameagenda this week is light. https://wiki.openstack.org/wiki/Meetings/Swift19:01
*** shri has joined #openstack-meeting19:02
notmynamewho's here?19:02
pelusehola19:02
torgomaticavast, ye salty sea dog19:02
portanteo/19:02
acoleshere19:02
*** lincolnt has joined #openstack-meeting19:02
cschwedehere19:02
lincolnthere19:02
*** jdob has quit IRC19:03
notmynamecschwede: now that I know we're online at the same time, I had to add a .mailmap entry for you recently (you had multiple addresses). please review and offer a patch if I chose the wrong one19:03
notmynamegreat, let's get started19:03
notmyname#topic 1.11.0 status update19:03
*** openstack changes topic to "1.11.0 status update (Meeting topic: swift)"19:03
*** jdob has joined #openstack-meeting19:03
*** hemanthravi has quit IRC19:04
*** mrodden has quit IRC19:04
notmynameRC for 1.11.0 has been cut. tons of great stuff in it (See the changelog)19:04
notmynameit's currently living on the milestone-proposed branch19:04
portantegreat19:04
portantewill it be final tomorrow?19:04
notmynameif nothing comes up in the next ~20 hours, we'll have our final 1.11.0 release19:04
notmynamethe only thing that came up so far was the spninx versioning requirement change19:05
*** nati_uen_ has joined #openstack-meeting19:05
notmynamesince without it, new versions of sphinx (which -infra has installed) break19:05
*** dfg has joined #openstack-meeting19:05
notmynameanything else know about anything else for 1.11?19:06
portantenot from red hata19:06
portantes/a//19:06
notmynameacoles: cschwede: anything from our EU contingent? :-)19:07
portanteacoles: wake up!19:07
acolesno19:07
notmynameheh19:07
portantewe know its late. :)19:07
cschwedeno :)19:07
acolesthat was no to notmyname :)19:07
notmynameok. if anything sees anything troubling, please let me know ASAP19:07
*** terryw has quit IRC19:08
notmyname#topic python-swiftclient19:08
*** openstack changes topic to "python-swiftclient (Meeting topic: swift)"19:08
*** nati_ueno has quit IRC19:08
notmynamemoving on to the next thing...19:08
notmynamethe client has had some patches languish and needs some lovin19:08
notmynamethere are a couple of patches I'd like to see land in it https://wiki.openstack.org/wiki/Swift/PriorityReviews19:08
notmynamehere's the plan I'm working towards:19:09
*** kmartin has quit IRC19:09
notmyname(1) land those last 2 patches (2) cut the last 1.X rev (3) land the cert checking patch (4) cut the 2.0 rev19:09
*** zaitcev has joined #openstack-meeting19:09
notmynameas to the other patches outstanding for python-swiftclient, most are stylistic changes or py3k changes (neither of which I consider high priority)19:10
notmynameany objections to this plan?19:10
portantenone from red hat19:10
cschwedeI think https://review.openstack.org/#/c/59673/  (one of those 2 last patches) needs only another opinion from someone else, should be easy to merge.19:11
notmynameya, I think both are fairly easy patches to review19:12
notmynameI'll look for activity on these an start nagging if nothing has happened by the end of the week19:12
notmynameanything else on python-swiftclient?19:13
*** ivasev has quit IRC19:13
*** rongze has quit IRC19:13
notmynameok. moving on...19:13
*** mrodden has joined #openstack-meeting19:13
notmyname#topic get_diskfile19:14
*** openstack changes topic to "get_diskfile (Meeting topic: swift)"19:14
portanteis gholt here?19:14
notmynamethis is a change that portante has.19:14
notmynameportante: got a link?19:14
portantesec19:14
notmynamedoesn't look like it19:14
*** reed has quit IRC19:14
portantehttps://review.openstack.org/#/c/60629/19:14
notmynamethanks19:14
portanteI don't look like that link, but there it is19:14
*** ivasev has joined #openstack-meeting19:14
portantegholt has placed a -1 on that patch, are there any other concerns with it?19:15
*** colinmcn_ has quit IRC19:15
* torgomatic is entirely neutral19:15
*** colinmcnamara has quit IRC19:15
*** vuil has quit IRC19:15
*** rongze has joined #openstack-meeting19:15
*** colinmcnamara has joined #openstack-meeting19:15
*** vkmc has joined #openstack-meeting19:15
pelusenot sure I fully understand his concern19:15
torgomaticas long as storage policy index can make it down to the filesystem in a manner that nobody hates too much, I'm on board19:15
*** colinmcn_ has joined #openstack-meeting19:15
notmynameportante: to summarize what I've heard on it, the get_diskfile change is something that woudl be expected to move over time, so this isn't good or bad, per se19:16
portanteokay, but that is true for lots of the code19:16
notmynameportante: ie anyone writing a DiskFile would be expected to know what versions of swift they are compatible with19:16
notmynameportante: sure :-)19:16
zaitcevFrankly I don't see why an implementation cannot conform to the old style of parameters and then simply ignore device and partition.19:17
portantecertainly, that is true today19:17
*** jorisroovers has joined #openstack-meeting19:17
*** tsg has joined #openstack-meeting19:17
portanteit can, this is to line things up with twhat is coming with storage policies19:17
portanteso that new parameters from the environment that are implementation specific land as kwargs only19:17
peluseand BTW, I have the patch almost ready that removes DATADIR and replaces with method func that takes index in and returns obj dir19:17
portantethis is a very tight change, and one which all the other out of the tree consumers have to adjust to anyways today19:18
portantepeluse: great19:18
peluseyup19:18
peluseyup to your first comment, not the 2nd one :)19:18
*** zhiyan has left #openstack-meeting19:18
pelusedo we need to 'policiy'ize' ASYNCDIR as well?19:19
notmynamepeluse: before we get there, let's finish up with portante's patch19:19
peluseasyndir-1, asyncdir-2, etc19:19
pelusesorry, jumping ahead19:19
portantenotmyname: not much more we can discuss19:20
portantegholt is not here, so it is kinda mute19:20
portantemoot19:20
*** rakhmerov has quit IRC19:20
portanteI am happy to move on to the next topic and just work this as best we can via -swift19:20
*** crank_ has joined #openstack-meeting19:20
notmynameportante: I'm on board with a,c,o, **kwargs. seems like it needs to go through normal review and land when it gets 2 +2s19:20
*** dcramer_ has quit IRC19:21
*** crank_ has quit IRC19:21
notmynameok, moving on...to "open"19:21
notmyname#topic open discussion19:21
*** openstack changes topic to "open discussion (Meeting topic: swift)"19:21
notmynamepeluse: asyncdirs?19:21
peluseyes, question for portante mostly I guess, and torgomatic19:22
pelusejust one for all policies or a dir per policy like we are doing with objects19:22
lincolntWhat about the topic on the agenda: gatekeeper middleware (https://review.openstack.org/51228) ?19:22
portanteI don't think we need to do it for asyncdirs, or quarantine for that matter, as the hash will always be different19:22
*** rongze has quit IRC19:22
pelusecool19:22
torgomaticlincolnt: I snuck that in there at about UTC 16:59:59, so we can just do that in open discussion :)19:23
pelusemakes sense19:23
*** clayg has joined #openstack-meeting19:23
notmynamelincolnt: whoops. sorry. I didn't reload my agenda page :-)19:23
notmynamelincolnt: I'll come back to that19:23
torgomaticthere's plenty of time19:23
lincolntok19:23
zaitcevnotmyname: Do you think we need more reviewers and if yes, are there any good ideas. I basically do nothing while I'm working on mem_backend for a,c and I feel like reviews pile up.19:23
*** resker has quit IRC19:23
*** nelsnelson has quit IRC19:23
*** esker has joined #openstack-meeting19:23
notmynameok, let me organize this19:23
notmyname#topic async dirs19:24
*** nelsnelson has joined #openstack-meeting19:24
*** openstack changes topic to "async dirs (Meeting topic: swift)"19:24
pelusegot my answer already :)19:24
notmynamepeluse: clayg: torgomatic: peluse: any resolution here? yes or now?19:24
notmynameok19:24
peluseanswer is no (no need tomake changes there)19:24
notmynamepeluse: at least for now. they may be needed at a later time19:25
*** Mandell has quit IRC19:25
peluseI have it almost done so may submit with the patch and reviwers can decide, easy to back out19:25
notmynameok19:25
notmyname#topic review backlog19:26
*** openstack changes topic to "review backlog (Meeting topic: swift)"19:26
notmynamezaitcev: in general, ya, I'm somewhat worried about the review backlog19:26
*** mdurnosvistov has joined #openstack-meeting19:26
notmynamepart of that has to do with the amount of reviews being done19:26
notmynamehowever, we have seen some recent movement as some of the core devs who weren't participating as much in the past did some more reviews (swifterdarrell)19:27
torgomaticsomeone should set up a graph of review-queue depth19:28
portantebut for a healthy community we also need to be sure folks from different companies are reviewing others folks work19:28
torgomatic:)19:28
notmynameportante: yes, indeed19:28
portanteit is not just about review backlog, it is also about getting the community mind share on changes19:28
pelusehear that19:29
zaitcevI agree with portante in abstract, but it's a luxury for me. I just grab any reviews I can complete, grab next, and it never ends. Can't even think what company backs what.19:29
*** lblanchard has joined #openstack-meeting19:29
notmynameaside from one or two changes recently, I don't think this is actually a problem we face currently19:29
notmynameportante: do you disagree?19:29
portanteit would be nice to see the data on the commits and how they were approved19:30
*** nati_uen_ has quit IRC19:30
*** lexx has joined #openstack-meeting19:30
portantebut not that concerned right now19:30
notmynameok19:30
zaitcevI think the only case when out-of-band sit-in-same-building authority forced a dubious patch in was Alex's DB cursors thing... And even in that case I doubt anyone would've caught that. BTW, IIRC it was ultimately fixed by a dude from HP.19:31
*** Duane has joined #openstack-meeting19:31
portantewe have partners who are not participating in the swift community because they don't feel it is open enough19:31
notmynameif anyone has ideas on how to do reviews differently, please let me know. let's be free with trying new things19:31
portantewe are trying to change that19:31
pelusethat's funny - not participating because they don't think its open enough is kinda part of the problem19:32
notmynameportante: every time I hear that complaint I ask for data and I haven't gotten any yet19:32
*** pvaneck has joined #openstack-meeting19:32
notmynamepeluse: +119:32
*** dcramer_ has joined #openstack-meeting19:32
portanteagreed, but it is what it is19:32
zaitcevI do wonder if I could drum up more support or critique for the backends if I were physically in SF19:32
notmynameportante: I'd also be happy to talk to anyone about that if it would help19:33
zaitcevI used to work in RH office in Sunnyvale, which is somewhat close.19:33
*** colinmcn_ has quit IRC19:33
*** colinmcnamara has quit IRC19:33
portanteyes, and I have recommended that19:33
notmynamezaitcev: yes, we all need to get on your db backends reviews (myself included)19:33
*** 21WABWJ1B has joined #openstack-meeting19:33
*** colinmcnamara has joined #openstack-meeting19:33
zaitcevTangentially re. community, remember this dude who posted a Ceph back-end19:34
notmynameyes19:34
pelusenotmyname:  maybe a peridic 'review-fest' online event or something...19:34
claygzaitcev: I'm looking at the ceph one, but I'm not expert - it takes time19:34
*** ChristerThor has quit IRC19:34
zaitcevWe told him "go to a separate repo". I'm wondering if he understood it right re. making sure he uses stable APIs and like a welcome test case, and not just giving him a cold shoulder.19:34
claygzaitcev: same for db backends - I don't have a strong vision for what it *should* look like - everything you've got seems sane19:34
zaitcevhttps://review.openstack.org/60215 - Babu Shanmugam19:35
claygzaitcev: I think chmouel should be able to keep in on the right page19:36
cschwedezaitcev: i think chmouel is in contact with him19:36
pelusesame company right?19:36
claygcschwede: beat ya!19:36
claygenovance19:36
*** erwan_taf has quit IRC19:36
*** rnirmal has quit IRC19:36
zaitcevokay19:36
notmynameya, I'm happy that it came from a company that has already been very good at working with upstream swift19:36
*** erwan_ta- has joined #openstack-meeting19:37
notmynamebut it did get jumped on pretty quickly. not incorrectly, but it may have been seen as harsh or sudden. I'm glad to hear chmouel and cschwede can help guide it19:37
notmynameok, let's move on to lincolnt's topic19:37
notmyname#topic gatekeeper middleware19:38
*** openstack changes topic to "gatekeeper middleware (Meeting topic: swift)"19:38
torgomaticalright, so there's this patch here that adds a new, mandatory middleware: https://review.openstack.org/5122819:38
notmynamelincolnt: what do you have?19:38
lincolntWe just noticed it, wanted to discuss, might be related to our https://wiki.openstack.org/wiki/MetadataSearch topic19:38
tomeshso why this middlware must be the first one?19:38
acolesits my patch19:39
lincolnttomesh and I here, form HP19:39
lincolntfrom19:39
claygi thoguth it had to be the second after catch_errors19:39
notmynameoh, sorry, it is torgomatic's topic, not lincolnt19:39
tomeshsure, the second one sorry.19:39
torgomaticyeah, I should have put my name on it19:39
* torgomatic is lazy sometimes19:39
torgomaticanyhow, when the (mandatory) gatekeeper middleware isn't in the pipeline, this patch adds it19:40
tomeshmy concern is with the metadata search middleware19:40
torgomatictomesh: I don't think this is related to search, sorry19:40
*** nati_ueno has joined #openstack-meeting19:40
tomeshso we offer search on both custom metadata as well as system metadata19:40
lincolntWe will be capturing additional system metadata on requests to add to the TBD metadata DB for searching19:40
*** herndon has joined #openstack-meeting19:41
torgomaticand when gatekeeper isn't second in the pipeline, this patch moves it19:41
torgomaticthat's what I want to get thoughts on: the automatic moving of middlewares19:41
torgomaticIMO, if an operator writes their pipeline in a particular order, we should respect that19:41
tomeshI agree19:41
torgomaticlike if someone sticks mempeek at index 0 to look for memory leaks19:41
torgomaticbut I don't want to send acoles off on a snipe hunt if other folks think that gatekeeper should get relocated19:42
zaitcevtorgomatic: I still cannot find it, what's the review #19:42
*** Mandell has joined #openstack-meeting19:42
*** troytoman-away is now known as troytoman19:42
torgomaticzaitcev: https://review.openstack.org/5122819:42
clayg5122819:42
torgomaticthe code in question is in swift/proxy/server.py19:42
lincolnthttps://review.openstack.org/#/c/51228/19:43
*** erwan_ta- has quit IRC19:43
*** spzala has joined #openstack-meeting19:43
portanteI believe the proxy server, and really any WSGI servers needs control of the beginning and end of the pipeline19:43
torgomaticso basically what I'm after here is: should Swift re-order middleware or not?19:43
portantecatch_errors is the one that I think needs to be mandatory19:44
claygportante: i like to turn off catch_errors in dev sometimes (so lazy)19:44
portanteI don't think it should reorder middleware that is definable in the configuration file19:44
notmynametorgomatic: in some cases I can see that it should (eg cache after ratelimit)19:44
*** erwan_taf has joined #openstack-meeting19:44
portanteclayg: sure, so have a proxy-serves section switch for that19:44
notmynamein other cases, no. eg I have my own custom middleware where I want/need it19:44
acolesportante: sure, but if gatekeeper is config definable and someone screws up then sysmeta gets leaked19:44
claygI think that dynamic pipelines patch had a good idea in this regard - you can either ask for the pipeline to be auto ordered or you can say explicitly what you want19:45
lincolntSo, related to metadata search: How can new middleware like ours grab new system metadata like (say) x-container-sysmeta-target-container-pointer if it strips it off before our middleware later in the pipe sees it?19:45
notmynameya, I want alpha_ori to resurrect that patch19:45
portantebut I don't think we are talking about arbitrary middleware, we seem to be talking about how to define the environment that middleware lives in in a WSGI server for swift19:45
portanteso if we are trying to prevent headers, why wouldn't we foorce that to the beginning of the pipeline?19:46
acoleslincolnt: gatekeeper just strips from incoming client request (which is why it needs to be at start of pipe)19:46
torgomaticportante: because I might want to profile the whole middleware chain, including gatekeeper19:46
portanteand how would the administrator know their middleware isn't at the beginning>19:46
torgomaticand if you force gatekeeper in front of my profiler, I can't do that19:46
*** reed has joined #openstack-meeting19:46
portanteso then we need to do the profiling differently19:47
portantebut how many other middlewares will we want to force to the front there?19:47
portanteprofiling seems to be internal type stuff19:47
portanteso are we talking about internal mechanism or general middleware?19:47
torgomaticI'm talking about general stuff... if I type out a pipeline with a bunch of stuff in it in a particular order, I want the proxy to just do it19:48
portanteand it will19:48
torgomaticnot if we move gatekeeper around19:48
portantewhy think of it as middleware?19:49
notmynametwo modes: (1) explicit and warn if it's not up front and (2) auto-manage where it moves things19:49
portantetorgomatic: there is lots of code in WSGI handling that won't get profiled with profiling middleware19:49
torgomaticmore concretely, if I have "pipeline = thing-one thing-two catch_errors gatekeeper", the proposed patch will turn that into "pipeline = catch_errors gatekeeper thing-one thing-two"19:49
notmynamehow abotu that ^19:49
*** susaant has joined #openstack-meeting19:50
portantetorgomatic: in this proposed scenario catch_errors and gatekeeper are not middleware19:50
*** vuil has joined #openstack-meeting19:50
tomeshright. why does the getkeeper need to be second19:50
torgomaticnotmyname: Some people, when confronted with a problem, think "I'll make it configurable!" Now they have 2^N problems.19:50
portantethey would be part of WSGI19:50
*** troytoman is now known as troytoman-away19:50
notmynametorgomatic: sure sure :-)19:50
*** troytoman-away is now known as troytoman19:51
*** novas0x2a|laptop has joined #openstack-meeting19:51
portantetomesh: catch_errors is a generic error handling thing for the pipeline, also adds txid19:51
tomeshsure19:51
* clayg search for gatekeeper in pep33319:51
portantegatekeeper is about preventing user specified reserved headers from entering in to the WSGI handling19:51
tomeshmy question is why do we force getkeeper to be the second middleware19:51
tomeshI understand19:51
torgomaticportante: ...but they're not? WSGI stuff isn't usually subject to me goofing it up, but these modules are19:52
portanteso that catch-errors can be first19:52
tomeshand I support this functionality19:52
portantetorgomatic: what?19:52
tomeshbut why does it NEEDs to be second?19:52
notmynamemake gatekeeper first but let it whitelist earlier middleware?19:52
torgomaticportante: eventlet.wsgi or Apache or whatever is outside the scope of things I can fix by patching Swift, but gatekeeper isn't, so I want it to be examinable19:53
portantetomesh: so that no other middleware will be affected by user attempts to set reserved headers19:53
acolesnotmyname: worth considering, but issue concerns catch_errors too19:54
tomeshbut if we have a middleware that needs to see the reserved headers19:54
*** seiflotfy has quit IRC19:54
portantetomesh: the point is that those middlewares need to be assured that if a reserved header is present it cames from other middleware and not set by the user19:54
acolestomesh: the reserved headers should never be set by a clinet19:54
acolesclient19:54
portantetorogmatic: why isn't gatekeeper?19:55
lincolntWe want our metadata search middleware to be in front of gatekeeper so we catch system metadata that gatekeeper (with this patch) would strip off, e.g. the example x-container-sysmeta-target-container-pointer19:55
lincolnt (my name example)19:55
*** seiflotfy_ has joined #openstack-meeting19:55
torgomaticportante: because it lives in the Swift source tree, and gets packaged with Swift19:55
portantelincolnt: why?19:55
portantetorgomatic: how much of swift do you want examinable?19:56
portantejust gatekeeper?19:56
portantewhat about ther est of the wsgi code in common?19:56
*** andersonvom has joined #openstack-meeting19:56
*** arbylee has joined #openstack-meeting19:56
portantewhy would gatekeeper be any different from that19:56
lincolntIsn't it a use case that the general mecahnism being added, to store any new system metadata, might be metadata that someone could want to search on? Like custom metadata19:56
notmynameI don't think we've got a consensus here (or will get one in the next 4 minutes). so let's move the discussion to #openstack-swift and the patch review19:56
portanteokay19:56
torgomaticsure19:57
notmynamebut now we all know what's at stake, so go review the code :-)19:57
acolesok. btw thanks folks for the reviews and interest19:57
notmynameacoles: I think you've got a lot of interest :-)19:57
portanteand have done a good job with this19:57
notmyname#topic open discussion (redux)19:57
*** openstack changes topic to "open discussion (redux) (Meeting topic: swift)"19:57
notmynameanything else to bring up in the last 3 minutes?19:58
peluseEC19:58
notmynames/2/319:58
*** thomasem has joined #openstack-meeting19:58
*** lakshmi has joined #openstack-meeting19:58
pelusedoubt can do it in 3 min thogh :)19:58
notmynameheh19:58
*** AaronGr is now known as AaronGr_afk19:58
pelusewe can pick it up on regular IRC19:58
notmynameok19:58
tsgworks19:58
*** sdake_ has quit IRC19:58
notmynamenext meeting is scheduled for Dec 25. I propose we skip it19:58
pelusehow come?19:59
peluse:)19:59
*** sdake_ has joined #openstack-meeting19:59
notmynameany objections?19:59
torgomaticnone here19:59
pelusesounds good19:59
notmynameif so, have the meeting without anyone else ;-)19:59
portantenone here, so we'll need again in the new year, happy new year!19:59
zaitcevinternational audience19:59
*** randallburt has joined #openstack-meeting19:59
notmynameok, off to -swift and gerrit for EC and gatekeeper discussions19:59
notmynamethanks for coming19:59
*** dcramer__ has joined #openstack-meeting19:59
notmyname#endmeeting19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:59
openstackMeeting ended Wed Dec 11 19:59:55 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-12-11-19.01.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-12-11-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-12-11-19.01.log.html20:00
*** zaitcev has left #openstack-meeting20:00
*** ivasev has quit IRC20:00
stevebaker#startmeeting heat20:00
openstackMeeting started Wed Dec 11 20:00:08 2013 UTC and is due to finish in 60 minutes.  The chair is stevebaker. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
*** tims has joined #openstack-meeting20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: heat)"20:00
*** funzo has joined #openstack-meeting20:00
openstackThe meeting name has been set to 'heat'20:00
*** clayg has left #openstack-meeting20:00
stevebaker#topic rollcall20:00
*** openstack changes topic to "rollcall (Meeting topic: heat)"20:00
*** portante has left #openstack-meeting20:00
shardyo/20:00
bgorskio/20:00
randallburto/20:00
timso/20:00
arbyleeo/20:00
*** rpothier has joined #openstack-meeting20:00
andersonvomo/20:00
spzalahi20:00
*** tsg has left #openstack-meeting20:00
stevebakerdolphm: ping heat meeting20:00
sdake_o/20:00
*** jecarey has quit IRC20:00
SpamapS~o~20:00
*** pshchelo has joined #openstack-meeting20:00
dolphm\o/20:01
lakshmio/20:01
*** zaneb has joined #openstack-meeting20:01
asalkeldo/20:01
pshchelo\o/20:01
zanebit's bizarre having this meeting in the middle of the day20:01
*** kwhitney has joined #openstack-meeting20:01
sdake_are you in the us now zane?20:01
stevebakerzaneb: close the curtains20:01
pshchelono less bizzare at 10 pm20:01
zanebpshchelo: no, 10pm is normal for me20:02
*** jecarey has joined #openstack-meeting20:02
stevebaker#topic Adding items to the agenda20:02
*** openstack changes topic to "Adding items to the agenda (Meeting topic: heat)"20:02
*** SergeyLukjanov has quit IRC20:02
stevebakerhttps://wiki.openstack.org/wiki/Meetings/HeatAgenda20:02
stevebakershould we talk heat-core nomination? that seems to be the vigorous discussion of the week20:02
skraynev_hello all20:03
kebray\o20:03
*** 21WABWJ1B has quit IRC20:03
*** colinmcnamara has quit IRC20:03
sdake_might as well stevebaker20:03
*** dcramer_ has quit IRC20:03
*** colinmcnamara has joined #openstack-meeting20:03
*** colinmcn_ has joined #openstack-meeting20:03
stevebakershardy: if/when dolphm show up we can talk management-api dependencies20:04
*** keving1 has joined #openstack-meeting20:04
asalkeldI think we should at least periodically check to see if we need add/remove people20:05
dolphmstevebaker: o/20:05
*** adrian_otto has joined #openstack-meeting20:05
shardystevebaker: Ok, did I miss a discussion on that?20:05
*** prasadv has joined #openstack-meeting20:05
*** erwan_taf has quit IRC20:05
stevebakerspecifically https://blueprints.launchpad.net/keystone/+spec/service-scoped-role-definition20:05
shardyI thought we were going to use normal policy rules until the service scoped token stuff gets worked out20:05
stevebaker#topic management-api dependencies20:05
*** openstack changes topic to "management-api dependencies (Meeting topic: heat)"20:05
*** erwan_taf has joined #openstack-meeting20:05
*** keving1 has left #openstack-meeting20:05
zanebasalkeld: it's supposed to be reviewed once per cycle. we should be looking to add people more often than that though, I agree20:05
shardystevebaker: I got blocked on bug #1256983 but we're merging that now20:06
uvirtbotLaunchpad bug 1256983 in heat/havana "[OSSA 2013-035] Heat ReST API doesn't respect tenant scoping (CVE-2013-6428)" [Critical,In progress] https://launchpad.net/bugs/125698320:06
*** asselin has quit IRC20:06
*** scollier has joined #openstack-meeting20:06
stevebakershardy: that is what I thought too, but https://blueprints.launchpad.net/heat/+spec/management-api has https://blueprints.launchpad.net/keystone/+spec/service-scoped-role-definition as a dependency. It looks like we can remove that20:06
shardydolphm: How is the service scoped role stuff going, still in discussion AFAICT?20:06
*** m4dcoder has joined #openstack-meeting20:06
shardystevebaker: Ok, I think maybe I added that when we were working out the options20:07
*** herndon has quit IRC20:07
*** keving1 has joined #openstack-meeting20:07
dolphmshardy: yes. as always, there's several proposed solutions with contention among them20:07
stevebakerlol20:07
shardydolphm: Ok, so we shouldn't be blocking on it then, maybe plan to migrate to it for K?20:07
dolphmshardy: ++ definitely shouldn't be a blocker from developing new APIs20:08
shardydolphm: and use a policy rule which overrides the default scoping for Icehouse?20:08
dolphmshardy: i don't follow the question?20:08
dolphmshardy: if you want to be super-safe, i'd suggest publishing a policy for new APIs that simply deny all access, forcing deployers to utilize keystone broken approach, or wait for a better solution from keystone20:09
shardydolphm: I'm just explaining my proposed workaround, which is to define an "is service admin" policy rule, which enables a user to e.g list all stacks for all tenants20:09
shardythat might be "heat_admin" role in the "admin" tenant or somehting, configurable in the policy20:09
*** peluse has left #openstack-meeting20:09
dolphmshardy: ++20:09
*** dcramer___ has joined #openstack-meeting20:09
shardydolphm: Ok, cool, thanks20:09
stevebakerright20:10
shardystevebaker: Ok, so I can make progress on this now, as soon as https://review.openstack.org/#/c/61455/ lands20:10
dolphmshardy: i definitely encourage service-specific admin-style roles... nothing in policy prevents you from requiring such arbitrary roles20:10
stevebaker#topic Unassigned icehouse-2 blueprints20:10
*** openstack changes topic to "Unassigned icehouse-2 blueprints (Meeting topic: heat)"20:10
stevebaker#link https://launchpad.net/heat/+milestone/icehouse-220:11
stevebakerif you sort by assignee you'll see 7 unassigned bps for i-220:12
*** jroovers has joined #openstack-meeting20:12
*** jorisroovers has quit IRC20:12
stevebakerif there are no takers they will just be kicked to i-3 at some point20:13
*** thedodd has joined #openstack-meeting20:13
shardyand a critical unassigned bug, is that really critical sdake_ ?20:13
shardyI'd say "high" myself20:13
zanebhttps://blueprints.launchpad.net/heat/+spec/parameter-nested-schema <- maybe tspatzier wants that one? he is away atm but has been working on related stuff20:13
sdake_shardy seems like a security issue but if you want to make high thats fine with me20:13
*** dcramer__ has quit IRC20:13
stevebakerzaneb: we should wait until his return20:14
SpamapSCritical, to me, is "Heat's mission is compromised entirely by this bug."20:14
sdake_ya, when i see security problems, i see them as critical20:15
shardysdake_: If it's critical, someone needs to take it, but IMO it's not critical, as there are several workarounds, e.g re-enable selinux in the userdata20:15
sdake_so we have different defintions ;020:15
stevebakerasalkeld: is this a dupe of what has already been implemented? https://blueprints.launchpad.net/heat/+spec/notification-support20:15
asalkeldyeah20:15
sdake_shardy i'll change the prioirty20:15
*** afarrell has joined #openstack-meeting20:15
*** afarrell has quit IRC20:15
stevebakerto me, critical is heat is completely broken20:15
randallburtoh whoops. I just grabbed that one stevebaker asalkeld20:15
shardystevebaker: +120:15
*** afarrell has joined #openstack-meeting20:15
stevebakerif it is an actual security bug it should be flagged as such20:15
sdake_cves are always critical in the bug tracker20:15
randallburtbut if the works already done...20:15
SpamapSsdake_: security is orthogonal to importance.20:16
sdake_bug already changed to high stop beating up on me please ;)20:16
SpamapSI mean to clarify for all, not beat on you.20:16
*** mspreitz has joined #openstack-meeting20:16
stevebakerbut I'm wondering, should it be flagged as security?20:16
sdake_i dont think it should be flagged as security - since the vms don't work atall with selinux enabled ;)20:17
stevebakerok, fair enough20:17
*** rakhmerov has joined #openstack-meeting20:17
sdake_hard to have a security bug if it doesn't allow a vector of attack :)20:17
SpamapSsdake_: not working at all == 0 risk == security wins: fatality!20:17
asalkeldI think we need a bp for migrating to oslo.messaging ?20:18
*** terryw has joined #openstack-meeting20:18
sdake_asalkeld +120:18
*** mdomsch has joined #openstack-meeting20:18
*** terryw is now known as otherwiseguy20:18
stevebaker#action asalkeld to raise a bp for migrating to oslo.messaging20:18
SpamapSbp?20:19
SpamapSthat's a bug IMO20:19
SpamapSContinuing to use oslo-incubator stuff that has a real library is a bug.20:19
stevebakerI don't think it matters, just something to track it20:19
zanebSpamapS: the distinction is as spurious as ever20:19
stevebaker#topic Repurposing of the stack/resource status columns - related to stack convergence20:19
*** openstack changes topic to "Repurposing of the stack/resource status columns - related to stack convergence (Meeting topic: heat)"20:19
SpamapSbps have specs. That's the distinction.20:19
shardyThe advantage of bugs is they are allowable as backports to stable..20:19
stevebaker#link https://blueprints.launchpad.net/heat/+spec/stack-convergence20:19
shardysomething to bear in mind when deciding which to choose ;)20:20
sdake_we don't want to  backport oslo.messaging into stable!20:20
*** dcramer__ has joined #openstack-meeting20:20
stevebakerandersonvom: want to take this one?20:20
andersonvomstevebaker: sure20:20
shardysdake_: I'm not saying we do, just in general, consider if you might want to when deciding bp vs bug20:20
sdake_shardy ya that makes sense - just going off your original cue ;020:21
andersonvomso, the problem there is that when retrieving the current status of all resources, the 'status' attributes of stack and resources become ambiguous20:21
andersonvomand we end up having no proper place to store that information20:21
asalkeldSpamapS, i prefer bugs over bp too, but just too late (made the bp)20:21
*** rakhmerov has quit IRC20:21
zanebandersonvom: ambiguous in what way?20:21
*** vipul is now known as vipul-away20:21
*** vipul-away is now known as vipul20:21
SpamapSasalkeld: thats the other distinction.. "it was already done one of the two spurious ways. ;)"20:22
andersonvomzaneb: the current 'status' attributes of stack/resource is really in reference to the action, not the objects themselves20:22
shardyandersonvom: The stack status relates to the state of the stack, each resource has it's own status, which you're updating20:22
SpamapSandersonvom: why would we want to store the status that is already in the external resource?20:22
SpamapSandersonvom: it is out of date the moment we store it.20:23
shardythe combination of which might change the stack status (not action)20:23
asalkeldis there a way to delete a bp?20:23
*** dcramer___ has quit IRC20:23
zanebso, 'status' is that status of the last action20:23
zanebs/that/the/20:23
andersonvomshardy: true. but a similar problem happens there as well: after I complete all the syncing, the action completes, but we have no way of telling what the current stack "health" is20:24
stevebakerasalkeld: Definition -> Obsolete and remove the Milestone target20:24
andersonvomzaneb: yes!20:24
zanebI'm not clear what the issue is with that though20:24
*** afarrell has quit IRC20:24
* zaneb is way behind on ML posts, sorry :(20:24
shardyYeah, so if we allow e.g heat stack-update --check, the result would be UPDATE, FAILED if any resources are polled and found to be in a FAILED state20:25
randallburtasalkeld, stevebaker I superseded the duplicate notifications bp if that's what you're looking to do.20:25
asalkeldsure20:25
*** romcheg has left #openstack-meeting20:25
shardyandersonvom: I agree we *could* separate the last lifecycle action status from the last polled status, but I'm not sure what that gains us, if the polling is user initiated20:25
stevebakerrandallburt: so did I ;)20:25
randallburtdouble superseded!20:26
stevebakerlike betamax20:26
andersonvomshardy: we may want to have a background task constantly updating the stacks, for example20:26
andersonvomshardy: that way, it would be easy to spot when something fails20:26
shardyandersonvom: Ok, then you keep triggering an update and look for the result of that update20:26
SpamapSI do like the idea of a background updater that can be optimized using notifications.20:27
shardyandersonvom: The result is still either COMPLETE or FAILED20:27
SpamapSBut that info is _extremely_ different from the status of the actions requested by the user.20:27
randallburtandersonvom:  yuck. I would prefer this be part of the stack owner's monitoring tbh. we've had hard times with bg threads and it gets worse now that multi-engine is landing20:27
stevebakerlanded20:28
randallburtyup.20:28
randallburtjasond makes progress even when he's on vacation ;)20:28
zanebshardy++, randallburt++++++20:28
shardyrandallburt: +120:28
*** mspreitz has quit IRC20:28
*** vuil has quit IRC20:29
stevebakerso what is the resolution to this topic?20:29
shardyBut there is still a valid use case for the check-update, which is not continuous monitoring20:29
shardyit's to figure out what will happen if you do a converge20:29
*** vkozhukalov has quit IRC20:29
arbyleeshardy: If you run a stack update, it feels odd to see a stack's state as UPDATE_FAILED, when it successfully performed it's action.  An update was called and the latest resource status was retrieved and stored20:29
randallburtto be clear, though. I got no issue with an api method that says "check the status of the things and update stack state as a result"20:29
*** henrynash has joined #openstack-meeting20:29
*** dcramer___ has joined #openstack-meeting20:29
randallburtshardy:  yes, that.20:29
shardyarbylee: Ok, so maybe you have a new action called "CHECK", or something?20:30
shardyarbylee: what you call the action doesn't really matter, its the status you're interested in20:30
randallburtmy suggestion was to add a STATE attribute to resources and do "something better" in the v2 api20:30
*** mrodden has quit IRC20:30
*** aweiteka has joined #openstack-meeting20:30
SpamapShrm20:30
shardyrandallburt: So have state and status?  That seems confusing20:30
andersonvomshardy: I guess what arbylee is saying is that it becomes ambiguous in a sense that an actual failure of the action will also be represented as FAILED20:30
SpamapSSo I think background threads have been painted in a bad light for no good reason.20:31
arbyleeshardy: right, but the status column still seems to represent the status of the ACTION.  If I see CHECK_FAILED, or any other verb here, it's ambiguous whether the call itself failed, or a resource is down20:31
randallburtshardy:  well, kinda. to me, status was "how did the last operation go" and state would be a stop gap, so if, for v1 we just update status then I'm not too fussed as long as its documented.20:31
zanebrandallburt: that name would be problematic20:31
shardySpamapS: because they've regularly bitten us with horrible eventlet related bugs?20:31
*** mrodden has joined #openstack-meeting20:32
SpamapSshardy: that is a bug, yes. But there are really solid answers to that kind of problem.20:32
randallburtzaneb:  sure, just and example.20:32
*** akuznetsov has quit IRC20:32
randallburtcould be called "FOO", but the gist is that I think we need to separate operational status from downstream resource state in v220:32
SpamapSLike having the "stack crawler" just be a client.20:32
stevebakerwould this issue all go away if we just make check and converge part of the same action?20:32
*** akuznetsov has joined #openstack-meeting20:32
SpamapSA client that subscribes to notifications from external sources that have such things available, and otherwise polls.20:33
shardyrandallburt: I think nova does the opposite?  They have Status, then several States related to Task/Power20:33
zanebSpamapS: if the engine has multiple background threads then it needs to be scaled out differently. If we have to do that, we should either do it in a different binary or, preferably, punt it to something external20:33
randallburtstevebaker:  iIRC we discussed that a bit at the summit, but it was generally agreed that I wanted to be able to see state without converging20:33
SpamapSzaneb: yes I am saying do it in a different binary. But don't punt it.20:33
*** dcramer__ has quit IRC20:33
*** dcramer__ has joined #openstack-meeting20:33
randallburts/I/we20:33
SpamapSalso it is worth looking at what Curvature does20:34
SpamapSthough I suspect that just updates on user demand20:34
arbyleestevebaker: do you mean to only have a converge call?  What would trigger someone to call this action?  I saw check/sync as the indicator that a converge needs to occur20:34
andersonvomstevebaker: that may not be ideal since the user may not want to "fix" the stack immediately. or, in the case of bg proc, it may not be good to do converge it automatically20:34
andersonvoms/do converge/converge/20:35
SpamapSSo what if check is external and we have a place for external things to annotate resources?20:35
*** devlaps has quit IRC20:35
SpamapSBecause "converge" is going to go and poll reality anyway.20:35
shardyandersonvom: But why is it bad for a stack to go into a FAILED state, then be converged into COMPLETE again whenever the user chooses?20:35
timsSpamapS I would highly suspect Curvature just updates on user demand20:35
andersonvomshardy: I think that's what we want to do, right? ;)20:36
SpamapSCOMPLETE is a misnomer if there isn't an action to COMPLETE. Something else like STEADY would be more accurate.20:36
randallburtandersonvom, shardy yes, I think that's what we want to do, but this first step is letting me see if the stack and reality are different. I want the ability to know that and then *optionally* converge.20:37
shardyandersonvom: I'm saying I'm still not clear on why we need state and status20:37
andersonvomshardy: the only "problem" with failing a check (or whatever action) is that we will never know if the action itself failed, or just the resource was down or in an innapropriate state20:37
*** vipul is now known as vipul-away20:37
*** dcramer___ has quit IRC20:37
shardyWhen andersonvom Yes you do, by looking at the resource states, and by the reason provided20:37
randallburtandersonvom:  and for the v1 api, I think we can just use status and say "the last operation doesn't reflect reality anymore"20:37
shardys/^When//20:37
SpamapSshardy: I agree with Anderson. There is an action which we want to know the outcome of, and an overall resource status which has an entirely different set of data associated (like how fresh is that perceived status?)20:37
*** akuznetsov has quit IRC20:38
shardySpamapS: But it's the exact same data we use when declaring the outcome of a resource action20:38
shardye.g check_create_complete20:38
shardywe'll be polling the exact same thing20:38
*** dprince has quit IRC20:38
randallburtSpamapS:  +1 but dunno if we *have* to do that now, rather than get what we want within the confines of v1 and then expand that in v220:38
SpamapSshardy: it is the same data, but at a different time and in a different context.20:38
*** dcramer__ has quit IRC20:39
timsandersonvom: would there be different states possible more granular than "failed"?20:39
andersonvomtims: possibly. we may want to point out that a resource is misconfigured, for instance20:39
shardySpamapS: That's why I'm saying, if it's user initiated, it's in the context of the most recent user initiated action, which is to trigger syncing the world's state with the stack20:39
randallburts/what we want/something reasonably effective for the use case20:39
randallburtshardy:  so the proposal is (CHECK, FAILED)?20:40
SpamapSshardy: that makes sense, I agree they are only slightly different at any one time.20:40
zanebso wouldn't the check call just poll everything and return its results? why are we talking about having to store this in the DB where the state usually goes?20:40
shardyI guess it doesn't matter that much either way, but won't it be confusing if a resource is UPDATE_COMPLETE_FAILED?20:40
shardyrandallburt: No I'm saying just update the stack without changing the definition, but triggering the check_update_complete logic, then set UPDATE_FAILED20:41
SpamapSzaneb: I think it could work either way so we might want to try and fit it into use cases.20:41
*** keving1 has left #openstack-meeting20:41
shardyrandallburt: but if folks want the action named something other than update, fair enough20:41
shardyAll we are doing is updating, either the resource definition, state, or both20:41
andersonvomshardy: I'm fine with using UPDATE, since that's what it really is20:41
SpamapSThere's also a problem in that if we store it in the DB, then we can't run checks concurrent with creates / updates20:41
shardySpamapS: IMO, that is a good thing ;)20:42
andersonvomSpamapS: yes, but that's by design20:42
randallburtI disagree its an UPDATE in the current semantics, but we're close so I won't fuss ;)20:42
shardySpamapS: Everything will be serialized by the stack lock anyway won't it?20:42
*** sandywalsh_ has quit IRC20:42
SpamapSshardy: I have a user here at HP that spins up stacks that take 30 - 45 minutes to create.. it would be useful to start checking state before that completes.20:43
SpamapSshardy: only if we need to change the stack.20:43
*** oubiwan__ has joined #openstack-meeting20:43
SpamapSOtherwise let the DB present the consistent view of the stack to the check thread.20:43
*** jecarey has quit IRC20:43
zanebbtw the way we report states ('<ACTION>_<STATUS>') in the v1 API sucks, and I'd be all in favour of augmenting it in v1 and replacing it in v220:43
*** nermina has quit IRC20:43
randallburtzaneb:  ++20:43
stevebakercan we wind this topic up and move on? Maybe carry on in #heat after the meeting20:44
randallburtstevebaker:  good plan20:44
shardyzaneb: +120:44
zanebI blame cfn20:44
andersonvomshardy zaneb SpamapS: so, do we all agree that it's going to be UPDATE_FAILED with the appropriate reason?20:44
SpamapSI blame gnomes.20:44
shardyCan people add the v2 API related suggestions to the wiki please?20:44
stevebakerFOO_IN_PROGRESS is problematic in v120:44
SpamapSandersonvom: no, -> #heat post meeting. :-/20:44
*** radez is now known as radez_g0n320:44
stevebaker#topic heat-core nomination20:44
*** openstack changes topic to "heat-core nomination (Meeting topic: heat)"20:44
shardyhttps://wiki.openstack.org/wiki/Heat/Blueprints/V2API20:44
*** jecarey has joined #openstack-meeting20:45
stevebakerso I don't think we have a problem with evaluation criteria on who to nominate for core20:45
zanebnext topic!20:45
shardyha20:45
zaneb;)20:45
stevebakerbut we do need to increase the core team size, and that seems to come down to motivating people to do reviews20:46
shardystevebaker: So, I agree re *our* criteria, but the point of my ML thread was to communicate those to people working hard on reviews hoping to become core20:47
shardyI'd rather avoid a huge debate on that again now tho ;)20:47
zanebis the limiting factor really motivation?20:47
stevebakerits a project-wide problem, people have many intrinsic and extrinsic motivators for doing reviews20:47
zanebgetting up to speed with the whole codebase takes a long time and is really hard20:48
randallburtso given that we've discussed the criteria on the ML, I suppose the next step is take those and start looking for folks that meet or are soon to meet them and start getting nominations together?20:48
zanebI think that slows us down much more than people not being motivated to do reviews20:48
SpamapSVote the way you want. We don't have to debate it really.20:48
stevebakerzaneb: true20:48
zanebI think we're blessed with lots of really motivated contributors20:48
*** asselin has joined #openstack-meeting20:48
SpamapSJun Jie Nan btw, is my next suggestion for core.20:49
*** AaronGr_afk is now known as AaronGr20:49
SpamapS"nanjj"20:49
sdake_I'd like to point out our current criteria; https://wiki.openstack.org/wiki/Heat/CoreTeam20:49
stevebakerzaneb: btw you might want to make more of your +0 reviews -1 or +1. Apart from juking your stats, I often miss good comments from you because they are +0, not -120:49
shardyI think bgorski has been doing some excellent work too20:50
*** armax has joined #openstack-meeting20:50
stevebaker+1 on bgorski20:50
SpamapSwe can vote on ML, but just for sake of discussion, that's who I think will have the most positive impact20:50
zanebstevebaker: I like to bikeshed on the reviews, but I don't like to -1 unless there's a good reason20:50
shardynanjj has been doing a lot of reviews, but I'd like to see more non-cosmetic review comments20:51
*** lexx has quit IRC20:51
*** s3wong has quit IRC20:51
randallburtso nomination boils down to a ML post, yes? or do we need to discuss on IRC or something first?20:51
SpamapSzaneb: yes please, +0 is actually specifically "the bikeshed score" ;)20:51
stevebakeranyone in core can nominate anyone on the ML, then we vote20:51
bgorskishardy, stevebaker thx but I know I still needs to work harder to become the core20:51
asalkeldzaneb, +1 I like to leave comments with no +/- too20:51
zanebI actually feel like it would be better if 1 person were in charge of nominating, so they can co-ordinate feedback to prospective candidates20:52
*** nermina has joined #openstack-meeting20:52
randallburtso to bring this around to the topic at hand, does the action item boil down to "do an evaluation based on our criteria and bring forth candidates"?20:52
zaneb(PTL seems like the obvious choice for that)20:52
andersonvomzaneb: +1 on not −1'ing without a good reason20:52
shardyzaneb: I thought traditionally the PTL nominated, but I know anyone can if they want20:52
randallburtand/or get in touch with folks who have potential and give them feedback20:53
stevebakeranybody can, but I'll periodically review if anybody looks ready20:53
zanebshardy: well, we copied a wiki page from Nova that said anyone can do it20:53
stevebakerand I am keeping an eye on it20:53
*** armax has left #openstack-meeting20:53
SpamapSMy take on -1's (and I'm sure you all already feel this) is that a) It can be taken back, b) it can be overridden, and c) it forces more action than +0. So if there is any inkling that a patch can be made better without inserting one's opnions (actual facts needed please) then I -1.20:53
*** dfg has left #openstack-meeting20:54
shardyzaneb: Yeah, but isn't that an openstack wide convention?20:54
SpamapSvery cautious not to -1 for just my opinion though.20:54
sdakewithout a -1, nobody knows the patch needs more work when it may from the comments :)20:54
*** sandywalsh_ has joined #openstack-meeting20:54
zanebso, e.g. if I think somebody is a good candidate for core but needs to work on a particular area, I'd like to contact the PTL and tell them that so they can give feedback if appropriate, or go ahead if they think my opinion is not important ;)20:54
shardyzaneb: Seems like its good that any -core *could* nominate, but it may be more useful if nominally the PTL is the conduit20:54
randallburtzaneb:  +120:55
randallburtshardy:  +1 as well20:55
zanebwhat I don't want to do is contact everybody in core and say 'let's nominate so-and-so, but not yet'20:55
sdakeour current mechanism is any core member can suggest a new core member -seems to work well so far20:55
zanebshardy: every project is free to define their own process20:55
SpamapSI think holding a vote on somebody without discussing them with the rest of the dev community first (including that somebody) is also a mistake.20:55
*** anniec has quit IRC20:55
randallburtSpamapS:  very much so.20:55
SpamapSSo anyway, I think we all actually pretty much agree.20:56
asalkeldyip20:56
SpamapSOur criteria is a bit skewed, but that is o-k. Diverse opinions are a good thing.20:56
stevebakerfeel free to contact me privately so I can contact potential nominees.20:56
zanebok, so let's say anyone in core can nominate, but they should talk to the PTL first?20:56
stevebaker4 minutes20:56
stevebaker#topic open discussion20:56
*** openstack changes topic to "open discussion (Meeting topic: heat)"20:56
sdakewell if thats the new process, change the wiki please20:56
sdakealhtough my take is we don't need to single thread on the ptl20:56
stevebakeryou don't *have* to but you might want to20:57
stevebaker-1 votes might offend the nominee ;)20:57
*** topol_ has joined #openstack-meeting20:57
stevebakernot that that has happened yet20:58
zanebif there are -1 votes the process is broken IMO20:58
shardystevebaker: That is one of the main reasons I wanted to more openly discuss criteria, I don't want to be the one saying -1 when someone is nominated20:58
sdaketypically I wouldn't expect a core member to suggest a new core that would get a -1 vote ;)20:58
stevebakerits happened in other projects20:58
SpamapSshardy: why not?20:59
zanebstevebaker: every one I've seen later reversed their vote20:59
shardyI'd rather we align on what is expected, so we don't nominate folks who don't have consensus, and so folks who are candidates know what we expect20:59
SpamapSshardy: I value your -1 very much. :)20:59
*** topol has quit IRC20:59
zanebSpamapS: -1 on adding folks to core is a veto20:59
randallburtzaneb:  I disagree. The nomination shouldn't be a "formality" IMO. We should discuss candidates openly and if its −1, then why is it −1. That feedback is valuable.20:59
*** topol_ is now known as topol20:59
*** IlyaE has quit IRC20:59
shardySpamapS: Because I would prefer folks to get +1'd an in to core, when they are ready, without any confrontation or hurt feelings20:59
SpamapSright, none of us _wants_ to do that.20:59
sdakewell, the wiki should  be updated with whatever we want to use as a criteria - that way its written down and is a *commitment* to our criteria21:00
stevebaker#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Wed Dec 11 21:00:03 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-12-11-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-12-11-20.00.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-12-11-20.00.log.html21:00
stevebakerto the #heat cave!21:00
*** arbylee has left #openstack-meeting21:00
* SpamapS calls dibs on the pole slide21:00
*** randallburt has left #openstack-meeting21:00
*** tims has left #openstack-meeting21:00
*** pshchelo has left #openstack-meeting21:00
*** lakshmi has left #openstack-meeting21:01
*** andersonvom has left #openstack-meeting21:01
*** denis_makogon_ has joined #openstack-meeting21:02
*** aweiteka has left #openstack-meeting21:02
*** shri has quit IRC21:03
*** shri has joined #openstack-meeting21:04
*** m4dcoder has quit IRC21:05
*** susaant has quit IRC21:05
*** rpothier has left #openstack-meeting21:07
*** yassine has quit IRC21:08
*** ivasev has joined #openstack-meeting21:09
*** ivasev has joined #openstack-meeting21:09
*** denis_makogon_ is now known as denis_makogon21:11
*** epim has joined #openstack-meeting21:11
*** Leon has joined #openstack-meeting21:12
*** Leon is now known as Guest1977521:12
*** anniec has joined #openstack-meeting21:14
*** Guest19775 has quit IRC21:15
*** slagle has quit IRC21:15
*** rakhmerov has joined #openstack-meeting21:18
*** olkonami has left #openstack-meeting21:18
*** rfolco has quit IRC21:21
*** colinmcn_ has quit IRC21:22
*** colinmcnamara has quit IRC21:22
*** ItSANgo has quit IRC21:23
*** epim has quit IRC21:25
*** vipul-away is now known as vipul21:25
*** thomasem has quit IRC21:25
*** jecarey has quit IRC21:29
*** thomasem has joined #openstack-meeting21:30
*** thomasem has quit IRC21:31
*** epim has joined #openstack-meeting21:32
*** jtomasek has quit IRC21:32
*** anniec has quit IRC21:33
*** markpeek has quit IRC21:33
*** asselin has quit IRC21:33
*** jcooley_ has quit IRC21:34
*** mdomsch has quit IRC21:34
*** SridarK has quit IRC21:35
*** epim has quit IRC21:36
*** jcooley_ has joined #openstack-meeting21:39
*** jasondotstar has quit IRC21:41
*** anniec has joined #openstack-meeting21:42
*** fbo is now known as fbo_away21:43
*** ArxCruz has quit IRC21:46
*** pvaneck has quit IRC21:46
*** lexx has joined #openstack-meeting21:48
*** ItSANgo_ has joined #openstack-meeting21:49
*** lblanchard has quit IRC21:51
*** rakhmerov has quit IRC21:51
*** topol has quit IRC21:51
*** pvaneck has joined #openstack-meeting21:56
*** shri has left #openstack-meeting21:58
*** anniec has quit IRC22:00
*** jdob has quit IRC22:03
*** greghill has quit IRC22:04
*** IlyaE has joined #openstack-meeting22:05
*** jroovers has quit IRC22:06
*** pdmars has quit IRC22:07
*** esker has quit IRC22:08
*** Leon has joined #openstack-meeting22:09
*** Leon has quit IRC22:10
*** Leon has joined #openstack-meeting22:10
*** dkranz has quit IRC22:11
*** Leon is now known as Guest7559822:11
*** radsy has joined #openstack-meeting22:15
*** oubiwa___ has joined #openstack-meeting22:17
*** oubiwa___ is now known as oubiwann-lambda22:18
*** esker has joined #openstack-meeting22:18
*** esker has quit IRC22:19
*** oubiwan__ has quit IRC22:20
*** anniec has joined #openstack-meeting22:21
*** spzala has quit IRC22:22
*** resker has joined #openstack-meeting22:22
*** oubiwann-lambda has quit IRC22:24
*** dims has quit IRC22:26
*** esker has joined #openstack-meeting22:27
*** esker has quit IRC22:28
*** resker has quit IRC22:28
*** herndon has joined #openstack-meeting22:28
*** tomesh has quit IRC22:28
*** michchap has joined #openstack-meeting22:31
*** stevemar has quit IRC22:34
*** markpeek has joined #openstack-meeting22:36
*** henrynash has quit IRC22:37
*** scollier has left #openstack-meeting22:37
*** ryanpetrello has quit IRC22:39
*** dims has joined #openstack-meeting22:39
*** Duane has quit IRC22:41
*** Duane_ has joined #openstack-meeting22:43
*** Duane_ has quit IRC22:44
*** SumitNaiksatam has quit IRC22:45
*** anniec has quit IRC22:45
*** MaxV has joined #openstack-meeting22:46
*** anniec has joined #openstack-meeting22:47
*** prasadv has quit IRC22:47
*** rakhmerov has joined #openstack-meeting22:48
*** mdurnosvistov has quit IRC22:48
*** enikanorov__ has quit IRC22:49
*** litong has quit IRC22:51
*** mdomsch has joined #openstack-meeting22:52
*** mdomsch_ has joined #openstack-meeting22:52
*** rakhmerov has quit IRC22:53
*** pnavarro has quit IRC22:54
*** mdomsch has quit IRC22:54
*** mdomsch_ has quit IRC22:54
*** BrianTorres-Gil has quit IRC22:57
*** BrianTorres-Gil has joined #openstack-meeting22:59
*** jmontemayor has joined #openstack-meeting22:59
*** anniec has quit IRC23:01
*** colinmcn_ has joined #openstack-meeting23:02
*** colinmcnamara has joined #openstack-meeting23:02
*** s0mik has quit IRC23:04
*** thouveng has quit IRC23:05
*** pnavarro has joined #openstack-meeting23:06
*** thouveng has joined #openstack-meeting23:07
*** anniec has joined #openstack-meeting23:07
*** ivasev has quit IRC23:08
*** BrianTorres-Gil has quit IRC23:09
*** anniec has quit IRC23:10
*** BrianTorres-Gil has joined #openstack-meeting23:10
*** flaper87 is now known as flaper87|afk23:17
*** kevinconway has quit IRC23:19
*** galstrom is now known as galstrom_zzz23:21
*** SumitNaiksatam has joined #openstack-meeting23:21
*** herndon has quit IRC23:21
*** ozstacker has quit IRC23:22
*** ozstacker has joined #openstack-meeting23:22
*** ryanpetrello has joined #openstack-meeting23:22
*** MaxV has quit IRC23:23
*** thedodd has quit IRC23:24
*** MaxV has joined #openstack-meeting23:24
*** thedodd has joined #openstack-meeting23:24
*** brucer has joined #openstack-meeting23:25
*** s0mik has joined #openstack-meeting23:25
*** Guest75598 has quit IRC23:26
*** sacharya has quit IRC23:26
*** MaxV has quit IRC23:28
*** BrianTorres-Gil has quit IRC23:29
*** sushils has quit IRC23:29
*** thedodd has quit IRC23:30
*** terriyu has quit IRC23:32
*** sushils has joined #openstack-meeting23:32
*** jgrimm has quit IRC23:33
*** dims has quit IRC23:34
*** Adri2000 has quit IRC23:35
*** BrianTorres-Gil has joined #openstack-meeting23:36
*** Adri2000 has joined #openstack-meeting23:36
*** Adri2000 has quit IRC23:36
*** Adri2000 has joined #openstack-meeting23:36
*** s0mik has quit IRC23:39
*** blamar has quit IRC23:39
*** anniec has joined #openstack-meeting23:40
*** stevemar has joined #openstack-meeting23:40
*** huats_ has joined #openstack-meeting23:40
*** huats_ has quit IRC23:40
*** huats_ has joined #openstack-meeting23:40
*** huats has quit IRC23:40
*** ryanpetrello has quit IRC23:41
*** dougshelley66 has quit IRC23:41
*** neelashah has quit IRC23:42
*** ryanpetrello has joined #openstack-meeting23:44
*** radsy has quit IRC23:44
*** markpeek has quit IRC23:47
*** rakhmerov has joined #openstack-meeting23:49
*** jeckersb is now known as jeckersb_gone23:50
*** masayukig has joined #openstack-meeting23:51
*** rdxc has quit IRC23:51
*** vipul is now known as vipul-away23:52
*** adrian_otto has quit IRC23:55
*** lbragstad has quit IRC23:55
*** blamar has joined #openstack-meeting23:56
*** colinmcnamara has quit IRC23:59
*** colinmcn_ has quit IRC23:59

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