Thursday, 2013-12-12

*** pcm_ has quit IRC00:00
*** vipul-away is now known as vipul00:00
*** mrodden has quit IRC00:01
*** BrianTorres-Gil has quit IRC00:06
*** denis_makogon has quit IRC00:07
*** BrianTorres-Gil has joined #openstack-meeting00:07
*** kgriffs is now known as kgriffs_afk00:10
*** dcramer_ has joined #openstack-meeting00:12
*** banix has quit IRC00:13
*** BrianTorres-Gil has quit IRC00:13
*** dcramer_ has quit IRC00:16
*** sacharya has joined #openstack-meeting00:17
*** rakhmerov has quit IRC00:22
*** nelsnelson has quit IRC00:24
*** fifieldt has joined #openstack-meeting00:25
*** fnaval has quit IRC00:27
*** kgriffs_afk is now known as kgriffs00:27
*** AaronGr is now known as AaronGr_afk00:28
*** herndon has joined #openstack-meeting00:30
*** lexx has quit IRC00:33
*** pablosan has quit IRC00:35
*** eharney has quit IRC00:36
*** epico has joined #openstack-meeting00:37
*** vipul is now known as vipul-away00:39
*** MIDENN_ has quit IRC00:40
*** branen_ has joined #openstack-meeting00:41
*** MIDENN_ has joined #openstack-meeting00:41
*** zhaoqin__ has quit IRC00:41
*** dims has joined #openstack-meeting00:43
*** Adri2000 has quit IRC00:44
*** branen has quit IRC00:45
*** yamahata_ has joined #openstack-meeting00:45
*** hemna_ is now known as hemnafk00:47
*** sdake_ has quit IRC00:49
*** mdomsch has joined #openstack-meeting00:50
*** weshay has quit IRC00:53
*** yamahata_ has quit IRC00:59
*** yamahata_ has joined #openstack-meeting01:00
*** RajeshMohan has quit IRC01:00
*** RajeshMohan has joined #openstack-meeting01:01
*** anniec has quit IRC01:01
*** Adri2000 has joined #openstack-meeting01:02
*** banix has joined #openstack-meeting01:03
*** SumitNaiksatam has quit IRC01:05
*** kgriffs is now known as kgriffs_afk01:05
*** neelashah has joined #openstack-meeting01:06
*** pvaneck has quit IRC01:09
*** vipul-away is now known as vipul01:10
*** jcooley_ has quit IRC01:12
*** anniec has joined #openstack-meeting01:15
*** rakhmerov has joined #openstack-meeting01:19
*** IlyaE has quit IRC01:20
*** sushils has quit IRC01:20
*** mdomsch has quit IRC01:21
*** salv-orlando_ has joined #openstack-meeting01:24
*** salv-orlando has quit IRC01:27
*** sushils has joined #openstack-meeting01:27
*** salv-orlando has joined #openstack-meeting01:27
*** IlyaE has joined #openstack-meeting01:27
*** salv-orlando_ has quit IRC01:28
*** IlyaE has quit IRC01:30
*** salv-orlando_ has joined #openstack-meeting01:33
*** jcooley_ has joined #openstack-meeting01:33
*** salv-orlando_ has quit IRC01:34
*** salv-orlando__ has joined #openstack-meeting01:34
*** nosnos has joined #openstack-meeting01:35
*** zhikunliu has joined #openstack-meeting01:36
*** salv-orlando has quit IRC01:36
*** salv-orlando__ is now known as salv-orlando01:36
*** jmontemayor has quit IRC01:37
*** SumitNaiksatam has joined #openstack-meeting01:38
*** lbragstad has joined #openstack-meeting01:38
*** yaguang has joined #openstack-meeting01:39
*** yaguang has quit IRC01:44
*** dkranz has joined #openstack-meeting01:46
*** Jianyong has joined #openstack-meeting01:46
*** dcramer_ has joined #openstack-meeting01:46
*** nermina has quit IRC01:47
*** huats_ has quit IRC01:47
*** markpeek has joined #openstack-meeting01:48
*** suo__ has joined #openstack-meeting01:51
*** rakhmerov has quit IRC01:52
*** rongze has joined #openstack-meeting01:52
*** DennyZhang has joined #openstack-meeting01:53
*** gongysh has joined #openstack-meeting01:55
*** kgriffs_afk is now known as kgriffs01:57
*** Mandell has quit IRC01:58
*** yaguang has joined #openstack-meeting02:01
*** huats has joined #openstack-meeting02:09
*** huats has quit IRC02:09
*** huats has joined #openstack-meeting02:09
*** anniec has quit IRC02:22
*** jcooley_ has quit IRC02:24
*** bgorski has quit IRC02:24
*** ryanpetrello has quit IRC02:24
*** rongze has quit IRC02:28
*** fnaval has joined #openstack-meeting02:28
*** rongze has joined #openstack-meeting02:29
*** nermina has joined #openstack-meeting02:32
*** zhikunliu has quit IRC02:33
*** kgriffs is now known as kgriffs_afk02:36
*** ildikov has quit IRC02:37
*** vkozhukalov has joined #openstack-meeting02:38
*** vkmc has quit IRC02:47
*** reed has quit IRC02:48
*** rakhmerov has joined #openstack-meeting02:49
*** eharney has joined #openstack-meeting02:51
*** rakhmerov has quit IRC02:53
*** dcramer_ has quit IRC02:54
*** julim has quit IRC02:57
*** BrianTorres-Gil has joined #openstack-meeting02:58
*** radsy has joined #openstack-meeting03:10
*** bogdando has quit IRC03:12
*** rpodolyaka has quit IRC03:12
*** ikhudoshyn has quit IRC03:12
*** ikhudoshyn has joined #openstack-meeting03:12
*** bogdando has joined #openstack-meeting03:13
*** rpodolyaka has joined #openstack-meeting03:13
*** ayoung has quit IRC03:13
*** esker has joined #openstack-meeting03:13
*** paragan has joined #openstack-meeting03:13
*** paragan has joined #openstack-meeting03:13
*** esker has quit IRC03:14
*** paragan has quit IRC03:19
*** jcooley_ has joined #openstack-meeting03:20
*** jcooley_ has quit IRC03:26
*** kgriffs_afk is now known as kgriffs03:27
*** novas0x2a|laptop has quit IRC03:30
*** epico has quit IRC03:32
*** rakhmerov has joined #openstack-meeting03:33
*** rongze_ has joined #openstack-meeting03:33
*** bgorski has joined #openstack-meeting03:34
*** paragan has joined #openstack-meeting03:35
*** rongze has quit IRC03:36
*** anniec has joined #openstack-meeting03:37
*** DennyZhang has quit IRC03:37
*** anniec has quit IRC03:42
*** haomaiwang has joined #openstack-meeting03:48
*** epico has joined #openstack-meeting03:49
*** haomaiwang has quit IRC03:50
*** haomaiwang has joined #openstack-meeting03:51
*** markpeek has quit IRC03:51
*** matiu has joined #openstack-meeting03:56
*** matiu_ has joined #openstack-meeting03:56
*** sushils has quit IRC03:58
*** haomaiwang has quit IRC03:58
*** sushils has joined #openstack-meeting04:00
*** sarob has joined #openstack-meeting04:03
*** sdake_ has joined #openstack-meeting04:05
*** sarob has quit IRC04:05
*** kgriffs is now known as kgriffs_afk04:05
*** sarob has joined #openstack-meeting04:06
*** sarob has quit IRC04:06
*** marun has joined #openstack-meeting04:06
*** haomaiwang has joined #openstack-meeting04:07
*** AaronGr_afk is now known as AaronGr04:08
*** AaronGr is now known as AaronGr_Zzz04:09
*** fifieldt has quit IRC04:11
*** adalbas has quit IRC04:11
*** BrianTorres-Gil has quit IRC04:17
*** mdomsch has joined #openstack-meeting04:18
*** sarob has joined #openstack-meeting04:24
*** radix_ has quit IRC04:25
*** banix has quit IRC04:27
*** sarob has quit IRC04:28
*** matiu has quit IRC04:28
*** chandankumar has joined #openstack-meeting04:36
*** sushils has quit IRC04:36
*** anniec has joined #openstack-meeting04:37
*** anniec_ has joined #openstack-meeting04:41
*** anniec has quit IRC04:41
*** anniec_ is now known as anniec04:41
*** anniec has quit IRC04:50
*** rongze_ has quit IRC04:52
*** herndon has quit IRC04:54
*** terriyu has joined #openstack-meeting04:55
*** kgriffs_afk is now known as kgriffs04:57
*** sarob has joined #openstack-meeting04:57
*** gyee has quit IRC04:58
*** epico has quit IRC04:59
*** galstrom_zzz is now known as galstrom05:02
*** nati_ueno has quit IRC05:03
*** neelashah has quit IRC05:09
*** sarob has quit IRC05:10
*** sarob has joined #openstack-meeting05:10
*** sarob has quit IRC05:11
*** garyk has quit IRC05:14
*** SergeyLukjanov has joined #openstack-meeting05:17
*** fifieldt has joined #openstack-meeting05:20
*** rongze has joined #openstack-meeting05:22
*** sarob has joined #openstack-meeting05:23
*** galstrom is now known as galstrom_zzz05:24
*** sarob has quit IRC05:25
*** sarob has joined #openstack-meeting05:26
*** galstrom_zzz is now known as galstrom05:26
*** sarob has quit IRC05:26
*** galstrom is now known as galstrom_zzz05:27
*** afarrell has joined #openstack-meeting05:27
*** rongze has quit IRC05:27
*** sdake_ has quit IRC05:32
*** SergeyLukjanov is now known as _SergeyLukjanov05:33
*** _SergeyLukjanov has quit IRC05:33
*** dougshelley66 has joined #openstack-meeting05:33
*** kgriffs is now known as kgriffs_afk05:35
*** enikanorov_ has quit IRC05:37
*** enikanorov has joined #openstack-meeting05:37
*** afarrell has quit IRC05:38
*** coolsvap has joined #openstack-meeting05:42
*** shanewang has quit IRC05:43
*** dougshelley66 has quit IRC05:44
*** galstrom_zzz is now known as galstrom05:44
*** coolsvap has quit IRC05:45
*** radsy has quit IRC05:45
*** coolsvap has joined #openstack-meeting05:45
*** Mandell has joined #openstack-meeting05:46
*** haomaiwa_ has joined #openstack-meeting05:49
*** otherwiseguy has quit IRC05:50
*** haomaiwang has quit IRC05:51
*** SergeyLukjanov has joined #openstack-meeting05:51
*** coolsvap has quit IRC05:53
*** coolsvap has joined #openstack-meeting05:53
*** galstrom is now known as galstrom_zzz05:55
*** garyk has joined #openstack-meeting05:56
*** sacharya has quit IRC06:00
*** radix_ has joined #openstack-meeting06:06
*** markpeek has joined #openstack-meeting06:06
*** jcooley_ has joined #openstack-meeting06:06
*** bgorski has quit IRC06:10
*** markvoelker1 has quit IRC06:13
*** SergeyLukjanov has quit IRC06:17
*** rongze has joined #openstack-meeting06:20
*** nermina has quit IRC06:21
*** vipul has quit IRC06:22
*** vipul has joined #openstack-meeting06:23
*** ArthurBerezin has joined #openstack-meeting06:24
*** MaxV has joined #openstack-meeting06:25
*** kgriffs_afk is now known as kgriffs06:27
*** ArthurBerezin1 has joined #openstack-meeting06:28
*** mdomsch has quit IRC06:29
*** jcooley_ has quit IRC06:30
*** jcooley_ has joined #openstack-meeting06:30
*** ArthurBerezin has quit IRC06:30
*** jcooley_ has quit IRC06:31
*** DinaBelova has joined #openstack-meeting06:31
*** jcooley_ has joined #openstack-meeting06:31
*** stevemar has quit IRC06:31
*** DinaBelova has quit IRC06:33
*** kgriffs is now known as kgriffs_afk06:37
*** markpeek has quit IRC06:41
*** vuil has joined #openstack-meeting06:42
*** lifeless has quit IRC06:48
*** dougshelley66 has joined #openstack-meeting06:51
*** vkozhukalov has quit IRC06:51
*** jlibosva has joined #openstack-meeting06:52
*** ildikov has joined #openstack-meeting07:06
*** gongysh_ has joined #openstack-meeting07:13
*** lifeless has joined #openstack-meeting07:15
*** gongysh has quit IRC07:16
*** gongysh_ has quit IRC07:16
*** gongysh has joined #openstack-meeting07:16
*** fifieldt has quit IRC07:17
*** jcooley_ has quit IRC07:18
*** haomaiwa_ has quit IRC07:21
*** jcooley_ has joined #openstack-meeting07:22
*** jcoufal has joined #openstack-meeting07:27
*** NikitaKonovalov has joined #openstack-meeting07:27
*** kgriffs_afk is now known as kgriffs07:28
*** MaxV has quit IRC07:28
*** MaxV has joined #openstack-meeting07:29
*** MaxV has quit IRC07:33
*** lucas__ has joined #openstack-meeting07:36
*** kgriffs is now known as kgriffs_afk07:37
*** cdub has quit IRC07:40
*** boris-42 has quit IRC07:43
*** Loquacities has quit IRC07:44
*** jcooley_ has quit IRC07:46
*** jcooley_ has joined #openstack-meeting07:50
*** nati_ueno has joined #openstack-meeting07:52
*** pnavarro has quit IRC07:55
*** Loquacities has joined #openstack-meeting07:55
*** mkoderer has quit IRC07:55
*** coolsvap has quit IRC07:56
*** belliott has quit IRC07:56
*** belliott has joined #openstack-meeting07:57
*** mkoderer_ has joined #openstack-meeting07:57
*** jcooley_ has quit IRC07:58
*** vuil has quit IRC08:00
*** rongze has quit IRC08:02
*** suo__ has quit IRC08:02
*** ArthurBerezin1 has quit IRC08:02
*** Jianyong has quit IRC08:02
*** gongysh has quit IRC08:03
*** gongysh has joined #openstack-meeting08:05
*** Jianyong has joined #openstack-meeting08:06
*** rongze has joined #openstack-meeting08:06
*** safchain has joined #openstack-meeting08:08
*** lexx has joined #openstack-meeting08:08
*** mengxd has joined #openstack-meeting08:10
*** mrunge has joined #openstack-meeting08:10
*** rongze has quit IRC08:11
*** belmoreira has joined #openstack-meeting08:12
*** belmoreira has quit IRC08:12
*** belmoreira has joined #openstack-meeting08:12
*** belmoreira has quit IRC08:14
*** pnavarro has joined #openstack-meeting08:16
*** enikanorov_ has joined #openstack-meeting08:18
*** denis_makogon has joined #openstack-meeting08:19
*** lexx has quit IRC08:24
*** suo__ has joined #openstack-meeting08:26
*** vkozhukalov has joined #openstack-meeting08:28
*** ArthurBerezin has joined #openstack-meeting08:30
*** ArthurBerezin has left #openstack-meeting08:31
*** haomaiwang has joined #openstack-meeting08:34
*** jhenner has joined #openstack-meeting08:37
*** fbo_away is now known as fbo08:42
*** ygbo_ has joined #openstack-meeting08:46
*** ygbo has joined #openstack-meeting08:46
*** nprivalova has joined #openstack-meeting08:46
*** henrynash has joined #openstack-meeting08:46
*** mengxd has quit IRC08:48
*** fifieldt has joined #openstack-meeting08:49
*** afazekas has joined #openstack-meeting08:51
*** belmoreira has joined #openstack-meeting08:53
*** Fdot has joined #openstack-meeting08:54
*** MaxV has joined #openstack-meeting08:56
*** henrynash has quit IRC08:59
*** yassine has joined #openstack-meeting08:59
*** pnavarro has quit IRC08:59
*** akuznetsov has joined #openstack-meeting09:00
*** terriyu has quit IRC09:01
*** henrynash has joined #openstack-meeting09:03
*** topshare has joined #openstack-meeting09:04
*** salv-orlando has quit IRC09:05
*** derekh has joined #openstack-meeting09:05
*** pnavarro has joined #openstack-meeting09:14
*** ekarlso has quit IRC09:17
*** ekarlso has joined #openstack-meeting09:17
*** yassine has quit IRC09:21
*** yassine has joined #openstack-meeting09:22
*** yassine has quit IRC09:22
*** haomaiwang has quit IRC09:22
*** yassine has joined #openstack-meeting09:23
*** jorisroovers has joined #openstack-meeting09:23
*** yassine has quit IRC09:23
*** MaxV has quit IRC09:24
*** yassine has joined #openstack-meeting09:24
*** yassine has quit IRC09:25
*** MaxV has joined #openstack-meeting09:25
*** yassine has joined #openstack-meeting09:26
*** jorisroovers has quit IRC09:27
*** kgriffs_afk is now known as kgriffs09:30
*** lucas__ has quit IRC09:33
*** marun has quit IRC09:36
*** topshare has quit IRC09:37
*** marun has joined #openstack-meeting09:37
*** flaper87|afk is now known as flaper8709:40
*** kgriffs is now known as kgriffs_afk09:40
*** fifieldt has quit IRC09:40
*** denis_makogon has quit IRC09:44
*** henrynash has quit IRC09:46
*** henrynash has joined #openstack-meeting09:48
*** johnthetubaguy has joined #openstack-meeting09:52
*** johnthetubaguy1 has joined #openstack-meeting09:54
*** johnthetubaguy has quit IRC09:57
*** lucas__ has joined #openstack-meeting10:02
*** MaxV has quit IRC10:03
*** MaxV has joined #openstack-meeting10:03
*** chandankumar_ has joined #openstack-meeting10:05
*** jtomasek has joined #openstack-meeting10:05
*** zhhuabj has quit IRC10:05
*** MaxV_ has joined #openstack-meeting10:06
*** MaxV has quit IRC10:07
*** chandankumar has quit IRC10:08
*** gongysh has quit IRC10:10
*** AlexF has joined #openstack-meeting10:14
*** haomaiwang has joined #openstack-meeting10:15
*** nosnos_ has joined #openstack-meeting10:15
*** nosnos_ has quit IRC10:16
*** nosnos_ has joined #openstack-meeting10:16
*** suo__ has quit IRC10:16
*** ndipanov has joined #openstack-meeting10:17
*** nosnos has quit IRC10:17
*** SergeyLukjanov has joined #openstack-meeting10:17
*** kwhitney has quit IRC10:17
*** ndipanov has quit IRC10:18
*** f_rossigneux has quit IRC10:18
*** f_rossigneux_ has joined #openstack-meeting10:19
*** ndipanov has joined #openstack-meeting10:19
*** nosnos_ has quit IRC10:20
*** ndipanov has quit IRC10:20
*** MaxV_ has quit IRC10:21
*** MaxV has joined #openstack-meeting10:22
*** MaxV has quit IRC10:23
*** MaxV has joined #openstack-meeting10:24
*** nprivalova has quit IRC10:28
*** AlexF has quit IRC10:28
*** kgriffs_afk is now known as kgriffs10:31
*** salv-orlando has joined #openstack-meeting10:34
*** zhhuabj has joined #openstack-meeting10:35
*** sushil_ has joined #openstack-meeting10:35
*** paragan has quit IRC10:36
*** rongze has joined #openstack-meeting10:41
*** salv-orlando has quit IRC10:42
*** NikitaKonovalov has quit IRC10:42
*** nprivalova has joined #openstack-meeting10:45
*** rongze has quit IRC10:46
*** johnthetubaguy1 is now known as johnthetubaguy10:47
*** Jianyong has left #openstack-meeting10:51
*** akuznetsov has quit IRC10:55
*** nprivalova has quit IRC10:57
*** akuznetsov has joined #openstack-meeting10:58
*** yamahata_ has quit IRC10:58
*** kgriffs is now known as kgriffs_afk11:09
*** MIDENN_ has quit IRC11:16
*** boris-42 has joined #openstack-meeting11:17
*** ArthurBerezin has joined #openstack-meeting11:19
*** akuznetsov has quit IRC11:19
*** akuznetsov has joined #openstack-meeting11:22
*** MaxV has quit IRC11:23
*** ndipanov has joined #openstack-meeting11:26
*** branen_ has quit IRC11:28
*** anniec has joined #openstack-meeting11:33
*** rossella_s has joined #openstack-meeting11:34
*** rdxc has joined #openstack-meeting11:35
*** adalbas has joined #openstack-meeting11:36
*** anniec_ has joined #openstack-meeting11:37
*** anniec has quit IRC11:37
*** anniec_ is now known as anniec11:37
*** vkmc has joined #openstack-meeting11:38
*** salv-orlando has joined #openstack-meeting11:43
*** salv-orlando has quit IRC11:43
*** slagle has joined #openstack-meeting11:49
*** zaneb has quit IRC11:51
*** weshay has joined #openstack-meeting11:58
*** kgriffs_afk is now known as kgriffs12:01
*** ArthurBerezin has left #openstack-meeting12:01
*** zaneb has joined #openstack-meeting12:04
*** ArxCruz has joined #openstack-meeting12:09
*** rfolco has joined #openstack-meeting12:23
*** enikanorov has quit IRC12:24
*** zhikunliu has joined #openstack-meeting12:24
*** enikanorov has joined #openstack-meeting12:24
*** ndipanov has quit IRC12:27
*** ArthurBerezin has joined #openstack-meeting12:28
*** pnavarro has quit IRC12:30
*** lucas__ has quit IRC12:30
*** rongze has joined #openstack-meeting12:37
*** ArthurBerezin has left #openstack-meeting12:39
*** kgriffs is now known as kgriffs_afk12:40
*** dims has quit IRC12:41
*** rongze has quit IRC12:41
*** dims has joined #openstack-meeting12:41
*** MaxV has joined #openstack-meeting12:42
*** masayukig_mobi has joined #openstack-meeting12:52
*** SergeyLukjanov is now known as _SergeyLukjanov12:54
*** _SergeyLukjanov has quit IRC12:54
*** yamahata_ has joined #openstack-meeting12:55
*** masayukig_mobi has joined #openstack-meeting12:55
*** masayukig_mobi has quit IRC12:55
*** sdake_ has joined #openstack-meeting12:58
*** yamahata_ has quit IRC13:02
*** yamahata_ has joined #openstack-meeting13:04
*** pdmars has joined #openstack-meeting13:05
*** NikitaKonovalov has joined #openstack-meeting13:06
*** pdmars has quit IRC13:07
*** jcoufal_ has joined #openstack-meeting13:08
*** yamahata_ has quit IRC13:09
*** ndipanov has joined #openstack-meeting13:09
*** jcoufal has quit IRC13:10
*** pdmars has joined #openstack-meeting13:11
*** rongze has joined #openstack-meeting13:12
*** zhikunliu has quit IRC13:14
*** egallen has joined #openstack-meeting13:14
*** dims has quit IRC13:17
*** Abhishek_ has joined #openstack-meeting13:17
*** galstrom_zzz is now known as galstrom13:19
*** dims has joined #openstack-meeting13:19
*** paragan has joined #openstack-meeting13:21
*** paragan has joined #openstack-meeting13:21
*** thomasem has joined #openstack-meeting13:22
*** galstrom is now known as galstrom_zzz13:22
*** SergeyLukjanov has joined #openstack-meeting13:23
*** yaguang has quit IRC13:24
*** yamahata_ has joined #openstack-meeting13:24
*** enikanorov__ has joined #openstack-meeting13:26
*** chandankumar_ has quit IRC13:29
*** ndipanov has quit IRC13:30
*** chandankumar has joined #openstack-meeting13:30
*** ndipanov has joined #openstack-meeting13:30
*** nprivalova has joined #openstack-meeting13:33
*** yamahata_ has quit IRC13:35
*** lblanchard has joined #openstack-meeting13:37
*** dkranz is now known as dkranz-in-transi13:38
*** yamahata_ has joined #openstack-meeting13:40
*** jdob has joined #openstack-meeting13:40
*** dkranz-in-transi has quit IRC13:41
*** kevinconway has joined #openstack-meeting13:41
*** MaxV has quit IRC13:43
*** nprivalova has quit IRC13:46
*** chuck_ has joined #openstack-meeting13:49
*** MaxV has joined #openstack-meeting13:49
*** enikanorov__ has quit IRC13:50
*** dougshelley66 has quit IRC13:53
*** yamahata_ has quit IRC13:54
*** yamahata_ has joined #openstack-meeting13:54
*** venkatesh has joined #openstack-meeting13:56
*** venkatesh_ has joined #openstack-meeting13:56
*** pnavarro has joined #openstack-meeting13:56
*** yamahata_ has quit IRC13:57
*** yamahata_ has joined #openstack-meeting13:57
*** henrynash has quit IRC13:58
*** yamahata_ has quit IRC13:58
*** katyafervent has quit IRC13:58
*** yamahata_ has joined #openstack-meeting13:59
*** nprivalova has joined #openstack-meeting13:59
*** Vijay_ has joined #openstack-meeting14:00
*** enikanorov__ has joined #openstack-meeting14:00
*** enikanorov__ has quit IRC14:00
*** enikanorov__ has joined #openstack-meeting14:01
*** dprince has joined #openstack-meeting14:01
enikanorov__hi14:01
Vijay_Hi14:01
obondarevhi folks14:01
*** rongze_ has joined #openstack-meeting14:01
*** henrynash has joined #openstack-meeting14:01
*** blamar has quit IRC14:01
*** pcm_ has joined #openstack-meeting14:01
enikanorov__letf wait for 2 more minutes14:02
enikanorov__*lets14:02
*** s3wong has joined #openstack-meeting14:02
*** eharney has quit IRC14:03
enikanorov__hi s3wong14:03
*** chuck_ has quit IRC14:03
s3wongHello14:03
*** songole has joined #openstack-meeting14:03
enikanorov__#startmeeting neutron lbaas14:03
openstackMeeting started Thu Dec 12 14:03:31 2013 UTC and is due to finish in 60 minutes.  The chair is enikanorov__. Information about MeetBot at http://wiki.debian.org/MeetBot.14:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:03
*** openstack changes topic to " (Meeting topic: neutron lbaas)"14:03
openstackThe meeting name has been set to 'neutron_lbaas'14:03
*** adalbas is now known as adalbafk14:03
enikanorov__#topic announcements14:03
*** openstack changes topic to "announcements (Meeting topic: neutron lbaas)"14:04
*** jeckersb_gone is now known as jeckersb14:04
*** rongze has quit IRC14:04
*** luQAs has joined #openstack-meeting14:04
enikanorov__yesterday agent unification patch was merged14:04
enikanorov__which means that any vendor plugin driver that want's to use agent should do it with our framework14:05
*** evgenyf has joined #openstack-meeting14:05
*** henrynash has quit IRC14:05
enikanorov__HAProxy driver is the one and only plugin driver at the moment, which utilizes that14:05
evgenyfHi All14:05
enikanorov__but it should be fairly easy now to ad drivers for similar solutions like nginx14:06
enikanorov__hi evgenyf14:06
enikanorov__any questions on unified agent?14:07
*** ymht has joined #openstack-meeting14:07
*** lbragstad has quit IRC14:07
enikanorov__ok, lets move on to the next topic14:08
enikanorov__#topic third party testing14:08
*** openstack changes topic to "third party testing (Meeting topic: neutron lbaas)"14:08
songoleWould the agent be doing appliance VM instantiation in future?14:08
enikanorov__songole: it is possible14:09
*** julim has joined #openstack-meeting14:09
enikanorov__ok, so back to the testing, we have 2 tempest scenarios on review that we hope will land soon14:09
enikanorov__they already could be used to perform end-to-end testing of the service14:10
enikanorov__and actually helper us to identify the issues with our patches14:10
enikanorov__does anyone want to update on integration with jenkins? evgenyf?14:10
*** dougshelley66 has joined #openstack-meeting14:11
Vijay_I have Eugene14:11
Vijay_One question regardin Testing infra setup. We were able to subscribe to events inspect the files on the patch submitted.14:11
enikanorov__the deadline for this was I-2, but i don't see much activity on vendor side14:11
evgenyfWe are working on OpenStack testing env. establishment14:11
evgenyfWill update about the Jen. integration in a minute14:11
*** yamahata_ has quit IRC14:12
enikanorov__Vijay_: so what's the question?14:12
*** yamahata_ has joined #openstack-meeting14:13
Vijay_Will just refreshing fetching latest Neutron code and re-starting neutron service will do to refresh the code14:13
Vijay_or is it advisable to run "stack.sh" and do the setup again?14:13
enikanorov__Vijay_: yeah, stack.sh should be run. fetaching and restarting the service is not sufficient14:14
Vijay_We are halfway through, next week we will have more progress.14:14
enikanorov__good14:14
obondarevBTW are you guys aware of today's meeting on third party testing at 17 UTC?14:14
evgenyfenikanorov__, What you mean by integration with Jenkins?14:14
obondarevI believe similar questions will be discussed there14:15
enikanorov__evgenyf: your system should post back the testing result, as far as i understand the requirement14:15
Vijay_ok. will try to join. Thanks obondarev.14:15
*** jprovazn has joined #openstack-meeting14:16
*** berlin has joined #openstack-meeting14:16
evgenyfWe are not there yet, Working on environment and running tests14:16
enikanorov__ok, good14:16
enikanorov__did you try those tempest scenarios in your lab yet?14:17
Vijay_We will try it next week and update.14:18
enikanorov__ok14:18
evgenyfenikanorov__, Not yet. BTW, as far as I know, we should push results back to gerrit, right? not Jenkins.14:18
enikanorov__any queestions on testing?14:18
enikanorov__evgenyf: oh right, mistyped my thought :)14:19
*** wwallnrr__ has joined #openstack-meeting14:19
*** changbl has quit IRC14:19
evgenyfenikanorov__, ok , good14:19
Vijay_No we can move on14:20
enikanorov__ok14:20
*** rongze has joined #openstack-meeting14:20
enikanorov__#topic L7 rules14:20
*** openstack changes topic to "L7 rules (Meeting topic: neutron lbaas)"14:20
enikanorov__evgenyf: any update?14:20
enikanorov__i saw avishay has pushed some patch on gerrit, but have not yet looked at it14:21
*** berlin has quit IRC14:21
evgenyfenikanorov__, Avishay will not join today. He asked me to update that he pushed first patch, inluding data layer modifications14:21
enikanorov__i see. in order to add this feature we'll need consistent patches: API change+ model change+ migration+ ut's14:22
enikanorov__so it seems like lot of work yet to be done14:22
*** Manur has joined #openstack-meeting14:22
evgenyfOK. Will tell him14:22
enikanorov__also there should be cli for that and tempest API tests (at least)14:23
*** sandy__ has joined #openstack-meeting14:23
enikanorov__so any major feature require lots of work...14:23
enikanorov__ok, lets moe to the next one then14:23
enikanorov__loadbalancer instance14:23
*** rongze_ has quit IRC14:24
enikanorov__#topic loadbalancer instance14:24
*** openstack changes topic to "loadbalancer instance (Meeting topic: neutron lbaas)"14:24
*** sandywalsh_ has quit IRC14:24
enikanorov__the initial implemetation is on review. the patch is not fully ready, but it passes gate tests including tempest API tests14:24
*** ayoung has joined #openstack-meeting14:25
enikanorov__which means that new API is fully backwards compatible14:25
Vijay_cool!14:25
enikanorov__cli-side is also on the gerrit14:25
enikanorov__now i'm working on tempest API tests for the new resource14:25
enikanorov__that's all on loadbalancer instance at the moment14:26
enikanorov__any questions?14:26
*** berlin has joined #openstack-meeting14:26
enikanorov__ok14:27
*** dkranz-in-transi has joined #openstack-meeting14:27
enikanorov__lets move to SSL14:27
s3wongenikanorov: this is the reivew, right? https://review.openstack.org/#/c/60207/14:27
enikanorov__#topic SSL termination14:27
*** openstack changes topic to "SSL termination (Meeting topic: neutron lbaas)"14:27
*** dkranz-in-transi is now known as dkranz14:28
enikanorov__s3wong: right14:28
evgenyfVijay commented my WIKI updates14:28
evgenyfModified it accordingly. Waiting for you review guys14:29
enikanorov__ok14:29
evgenyfWill try to catch Mark just to be sure the direction is good14:30
evgenyfAll these new entities etc..14:30
enikanorov__ok, good14:30
*** sdake_ has quit IRC14:30
*** jasondotstar has joined #openstack-meeting14:30
enikanorov__would be good to see any implementation proposal in I-214:31
Vijay_Hi Evg, default policy is not a UI only feature right?14:31
enikanorov__or most certainly it will not land in icehouse14:31
evgenyfVijay, No14:31
Vijay_ok thanks!14:31
evgenyfI mean, right:)14:31
Vijay_?? :-(14:32
evgenyfI'm working on it. Will push initial work soon.14:32
enikanorov__ok, cool14:32
evgenyfJust want to be sure Mark is aware of the design14:32
enikanorov__yeah, that is a good approach14:33
evgenyfVijay, It's not onlu UI feature14:33
*** otherwiseguy has joined #openstack-meeting14:33
enikanorov__ok, another topic i would like to discuss is a various HA proposals we had14:33
enikanorov__obondarev: could you update?14:33
obondarevsure14:33
obondarevHA for agents is on review14:34
*** jdob has quit IRC14:34
obondarevhttps://review.openstack.org/#/c/59743/14:34
obondarevstill struggling with random unit test failures14:34
*** jdob has joined #openstack-meeting14:34
obondarevthere is a race I guess14:34
obondarevneed to add some more unit tests and fix the race14:35
Vijay_Evg: In that case, lets add the default policy description in the "Resources change" title in the place where we are describing "SSL policy "14:35
obondarevthis patch only works for plugins that are not host specific14:35
enikanorov__i still think the design could be different for the case when agent manages the device and not the process14:35
obondarevenikanorov__: can you please clarify?14:36
enikanorov__as we discussed, it could be solved with a common queue instead of scheduling14:36
evgenyfVijay, will do14:36
obondarevenikanorov__: yeah, I put some thoughts on it to the bp description14:37
enikanorov__I'd sent an email to oos-dev wtih those two options14:37
enikanorov__and ask for opinions14:37
*** banix has joined #openstack-meeting14:37
obondarevthere is a common problem with common queue14:37
enikanorov__which one?14:37
obondarevnot specific for lbaas even14:38
obondarevthat some action should be processed consequntly14:38
obondarevactions*14:38
enikanorov__can you give an example?14:38
*** lincolnt has quit IRC14:38
obondarevwith many agents listening to one queue there might be races14:39
enikanorov__not really14:39
obondarevnot sure I'm ready with an example now14:39
enikanorov__it is not different as with 1 agent14:39
obondarevwe discussed it with sgran14:39
enikanorov__which processes messages in multithreading fashion14:39
*** yaguang has joined #openstack-meeting14:40
enikanorov__ok, lets discuss it offline14:40
*** lbragstad has joined #openstack-meeting14:40
obondarevok , I agree second approach is possible, need to collect pros and cons14:41
*** nprivalova has quit IRC14:41
enikanorov__ok, another topic is ha for haproxy14:41
obondarevyeah14:41
obondarevnot started yet thiugh14:41
enikanorov__do you have a design in mind?14:42
obondarevI look toward haproxy + keepalived approach14:42
*** eharney has joined #openstack-meeting14:42
*** herndon has joined #openstack-meeting14:42
*** neelashah has joined #openstack-meeting14:42
s3wongI can look into HA for haproxy, since it should be done via haproxy + keepalived14:42
obondarevthat is what I was plannin to start tomorrow or next week14:42
*** rongze_ has joined #openstack-meeting14:43
enikanorov__ok, no hurry i think14:43
*** dcramer_ has joined #openstack-meeting14:43
enikanorov__but anyway, keepalived approach seems to me quite complex, considering os environment14:43
*** kgriffs_afk is now known as kgriffs14:43
enikanorov__whoever takes care of that, don't forget to write a wiki page with the design14:44
obondarevsure14:44
*** rongze has quit IRC14:44
*** adrian_otto has joined #openstack-meeting14:44
enikanorov__any other items to discuss?14:45
*** berlin has quit IRC14:45
Vijay_i have one quick quesetion regarding testing.14:45
Vijay_You said that I-2 is the deadline14:45
Vijay_this is for what?14:45
*** blamar has joined #openstack-meeting14:45
*** nprivalova has joined #openstack-meeting14:46
enikanorov__this is to provide a system for testing vendor plugins14:46
enikanorov__that is integrated with gerrit14:46
enikanorov__if your plugin is not yet in the tree, than you don't need to hurry14:46
Vijay_ok14:47
*** oubiwan__ has joined #openstack-meeting14:47
*** eglynn has joined #openstack-meeting14:48
Vijay_anything else?14:48
enikanorov__not from my side14:48
enikanorov__i think we can end the meeting14:48
Vijay_ok. Bye Everyone!14:48
s3wongThanks! Bye!14:48
*** Vijay_ has quit IRC14:48
enikanorov__thanks for joining14:48
enikanorov__#endmeeting14:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:48
openstackMeeting ended Thu Dec 12 14:48:59 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_lbaas/2013/neutron_lbaas.2013-12-12-14.03.html14:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_lbaas/2013/neutron_lbaas.2013-12-12-14.03.txt14:49
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_lbaas/2013/neutron_lbaas.2013-12-12-14.03.log.html14:49
*** Akhil has joined #openstack-meeting14:49
*** s3wong has quit IRC14:49
evgenyfbye14:49
*** egallen has quit IRC14:49
*** ArthurBerezin has joined #openstack-meeting14:50
*** ArthurBerezin has left #openstack-meeting14:50
*** pcm_ has left #openstack-meeting14:50
*** gordc has joined #openstack-meeting14:52
*** markpeek has joined #openstack-meeting14:52
*** enikanorov__ has quit IRC14:53
*** sayali_ has joined #openstack-meeting14:54
*** sayali_ has left #openstack-meeting14:54
*** Alexei_987 has joined #openstack-meeting14:55
*** wherebot has joined #openstack-meeting14:56
*** gibi has joined #openstack-meeting14:56
*** wherebot has quit IRC14:57
*** ymht has left #openstack-meeting14:57
*** jecarey has joined #openstack-meeting14:58
*** wherebot has joined #openstack-meeting14:59
*** bill_az has joined #openstack-meeting14:59
*** fnaval has quit IRC15:00
*** nealph has joined #openstack-meeting15:00
jd__#startmeeting ceilometer15:01
openstackMeeting started Thu Dec 12 15:01:11 2013 UTC and is due to finish in 60 minutes.  The chair is jd__. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: ceilometer)"15:01
openstackThe meeting name has been set to 'ceilometer'15:01
dragondmo/15:01
silehto/15:01
thomasemo/15:01
herndono/15:01
*** wherebot has quit IRC15:01
ildikovo/15:01
eglynno/15:01
Alexei_987\o/15:01
sandy__o/15:02
*** llu-laptop has joined #openstack-meeting15:02
gordco/15:02
eglynnjd__: I just update the agenda15:02
llu-laptopo/15:02
eglynn#link https://wiki.openstack.org/wiki/Meetings/Ceilometer#Agenda15:02
*** nermina has joined #openstack-meeting15:02
eglynn(... was last week's previously)15:02
dperazao/15:02
nealpho/15:02
nprivalovao/15:02
*** absubram_ has joined #openstack-meeting15:02
*** BrianB_ has joined #openstack-meeting15:02
jd__#topic Models validation (Alexei_987)15:03
*** openstack changes topic to "Models validation (Alexei_987) (Meeting topic: ceilometer)"15:03
jd__go ahead Alexei_98715:03
Alexei_987I have a patch with a draft proposal https://review.openstack.org/#/c/60885/15:03
*** s3wong has joined #openstack-meeting15:04
Alexei_987dhellmann says that that's should not happen cause we already have validation in WSME + possibly nova-objects15:04
Alexei_987my reasoning is the following: storage/models is the middleware between different application layers - API, storage15:04
*** jcooley_ has joined #openstack-meeting15:05
Alexei_987this is the exact place validation should be15:05
*** jtomasek has quit IRC15:05
eglynnfrom the gerrit comment trail doesn't sound dhellmann is ruling your approach out15:05
*** Manur has quit IRC15:05
Alexei_987we discussed it a little bit in chat yesterday15:05
eglynn... more just taking the conversative "let's see if anything we have already can do the job" approach, no?15:05
dragondmYah, I looked at that earlier. Using __slots__ for that is an interesting idea (I've done the same for an ORM I wrote awhile back for some internal Rackspace stuff), but yah, I think we just need to agree on a direction here.15:06
dperazaAlexei_987: maybe a blueprint linked to patch explaining the validation benefits will help15:06
*** songole has quit IRC15:06
eglynnAlexei_987: did dhellmann come down more firmly against your approach in your IRC discussion?15:06
dperazathat way we can all pitch in help with review15:06
Alexei_987ok in such case I'll have to create a comparison of existing validation scenarios15:07
*** evgenyf has left #openstack-meeting15:07
eglynnAlexei_987: that sounds reasonable to me15:07
Alexei_987to create an overview of possible options15:07
*** thouveng has quit IRC15:07
*** fnaval has joined #openstack-meeting15:07
jd__eglynn: you got this right15:07
Alexei_987ok I guess we all agreed on this15:08
jd__the point dhellmann raised and I agree, is that we shouldn't write another set of code of does validation15:08
*** lsmola has quit IRC15:08
*** troytoman is now known as troytoman-away15:08
jd__we should leverage something else, that something else being to be determined, I'm working on that15:08
*** rajdeep has joined #openstack-meeting15:08
Alexei_987yeah but still I insist that we should use slots and have the validation in models15:09
Alexei_987this will allow us to remove duplication of logic in API and storage15:09
Alexei_987related to query processing15:09
*** lsmola has joined #openstack-meeting15:09
* dhellmann apologizes for arriving late15:10
* jd__ fires dhellmann 15:10
jd__Alexei_987: again, we're not against validating, we're against writing code that does the validation15:10
dperazaAlexei_987: how will that look at the API layer15:10
*** s3wong has quit IRC15:10
dhellmannthe issue I have with the patch is not *where* the validation is being done, it is with the fact that it creates another framework for declaring classes, types, and validators15:11
Alexei_987on API layer we'll reuse models to do the validation of incoming parameters15:11
dperazais there work needed on API to catch exception and raise the right http error code15:11
Alexei_987dhellmann: it's not a framework. it's a tiny piece of code that does it15:11
dperazaor will that show as 500 on client side15:11
Alexei_987dperaza: it will catch exception and fire a 400 code with description from exc message15:12
dhellmannAlexei_987: that "tiny bit of code" is completely different from the 2-3 other ways we do the same thing elsewhere, so it doesn't matter how big it is15:12
Alexei_987true but we don't have nova objects :)15:12
Alexei_987and WSME validation won't do on models layer15:12
dperazaAlexei_987: will this validate metadata too15:12
Alexei_987dperaza: it depends on our needs. it can be extended to do different kind of things15:13
*** mcpierce has joined #openstack-meeting15:13
Alexei_987my main goals - simple type validation, referential integrity control for storage15:13
dperazaright now metadata validation is a gap I see15:13
dperazaI think it is bacause metadata is meant to be free form, but some folks see different15:14
*** mdurnosvistov has joined #openstack-meeting15:14
dhellmannwe have to be very careful about the validation we do, so we don't introduce "rules" that prevent us from collecting data that is "true" even if it looks like it might be bad15:14
dhellmannthe storage models are used to save the data that comes directly from notifications, and we can't necessarily restrict what the other services are telling us15:15
dhellmannthat's why we focused most of the validation on the models in the API layer, because those come from users, not services15:15
dperazadhellmann: I lean to agree with that15:15
Alexei_987dhellmann: I cannot agree with the last one15:15
dhellmannthe same applies to metadata -- we don't know what rules to enforce about metadata15:15
Alexei_987dhellmann: API layer is not the place to validate incoming data15:16
dhellmannwe tried to create a completely agnostic system that would store whatever metadata was coming to us15:16
dhellmannAlexei_987: we *CANNOT* reject data from notifications just because it doesn't look right to us -- we don't make the rules for what goes into notifications15:16
thomasemAlexei_987, Ceilometer isn't the source of truth in this whole architecture. If we start putting rules around what a notification should look like, we may lose data that we actually want, even if it's incorrect.15:17
Alexei_987dhellmann: I'm not telling to reject it15:17
*** prad has joined #openstack-meeting15:17
dperazaso we have not way to distiguish from "bad" queries and querries that simply does not match15:17
dhellmannthomasem: exactly my point15:17
Alexei_987we don't have to validate free for meta15:17
dperazawhat i hear is that this is by design15:17
thomasemThe source of truth is each component pushing the notifications, and that's the only communication we have.15:17
*** mdomsch has joined #openstack-meeting15:17
Alexei_987but we need to make sure that basic data is valid15:17
Alexei_987timestamp, etc.15:17
thomasemAlexei_987, What would we do if the timestamp is incorrectly formatted?15:17
thomasemfrom, say, a Glance notification?15:17
eglynnand if it fails validation, discard?15:18
eglynnthomasem: snap!15:18
nprivalovafix it :)15:18
Alexei_987for timestamp - replace with current datetime15:18
*** sdake_ has joined #openstack-meeting15:18
thomasemAnd scramble the event stream?15:18
thomasemSo we can't recreate for audits?15:18
sileht /6015:18
dragondmFile a bug w/ the source project, methinks..15:18
dperazahttps://github.com/openstack/ceilometer/blob/master/ceilometer/api/controllers/v2.py#L34315:18
dperazathat one validates queries comming from client15:19
dhellmannno, replacing the timestamp would completely invalidate any audit trail15:19
thomasemWhat if we have a request that sends 10 notifications, and one of those timestamps happens to be poorly formatted and we replace with utcnow()? Then we can't ensure the integrity of that. We lost the integrity in trying to validate something we're not responsible for.15:19
eglynnbetter to preserve even the apparent wrongness AND file a bug with the originating service?15:19
dhellmanneglynn: yes15:19
thomasem^^15:19
Alexei_987well we can't do that15:19
Alexei_987for example MySQL needs to have valid input15:19
*** jtomasek has joined #openstack-meeting15:20
dragondmTrue, if the timestamp is garbage, we might not event be able to store the data.15:20
dperazaI do think that validation on V2 API should be move to more common code15:20
Alexei_987so it has to receive valid date15:20
thomasemAlexei_987, That's actually a problem in and of itself. We're enforcing relationships and datatypes on things we're not responsible for the relationship or datatype of.15:20
*** fnaval has quit IRC15:20
thomasemIt's not our data. It's Nova's, Glance's, Swift's.15:21
thomasemWe're just persisting it for auditing, metering, monitoring...15:21
Alexei_987again - we should only validate essential fields that are required by ceilometer and we may not validate free form data15:21
thomasemAnd hoping it's correct15:21
nprivalovabtw, if timestamp is incorrect Ceilometer will not be able to take this Sample into account, right?15:21
eglynnyeap, the timestamp is garbage, the sample can't be aggregated15:22
thomasemThat's true15:22
dragondm(not to mention it'd be a violation of the spec such as it is, on a notification. )15:22
Alexei_987the same goes if we'll create reference id's to missing resources15:22
nprivalovaso we put it into db but actually do not look at it in most cases15:22
thomasemdragondm, yep, that's true too hehe15:22
dhellmannwe will have a lot of resource ids in our database that don't exist anywhere else in openstack15:23
dhellmannobjects are deleted all the time, but we still need to record their history15:23
dhellmannand we designed the schema to let us record data about resources that are not even in openstack at all15:23
Alexei_987ok agreed15:23
jd__good point dhellmann15:23
dragondmYup.15:23
dhellmannwhat's the adage about being liberal in what you accept but conservative in what you send?15:24
eglynnBTW what's motivating this validation requirement?15:24
eglynni.e. do we have a history of garbage fields being emitted by the OS services in real notifications?15:24
dhellmannthe best way to ensure good data in the notifications, including our own format, is to provide a library that's easy to use to generate them15:24
sandy__by this logic though, validation should occur in the schema of the notification generation and all downstream services should assume them to be gospel (or share the same validation code as the generator)15:24
eglynnor is it more of a theorectical what-if scenario?15:24
dhellmannoslo.messaging (or oslo rpc) includes that for standard notifications, and jd__'s work on notification schemas will take it even further15:25
*** jgrimm has joined #openstack-meeting15:25
thomasemYeah15:25
dperazaI agree with a validation library15:25
dhellmanneglynn: good question15:25
dhellmannAlexei_987: have you seen bad data in production?15:25
*** sushil_ has quit IRC15:25
sandy__we have15:25
thomasemyeah15:26
dhellmannwhich services generated the notifications?15:26
Alexei_987no.. my motivation is improving internal code logic15:26
Alexei_987and reducing duplication15:26
sandy__glance, sending a list instead of a dict payload15:26
Alexei_987so only code improvement15:26
sandy__for error events15:26
*** sacharya has joined #openstack-meeting15:26
*** AlexF has joined #openstack-meeting15:26
dhellmannsandy__: a list of …?15:26
dhellmannerror messages?15:27
dragondmsandy__: We filed a glance bug on that?15:27
apmelton1dhellmann: sandy__: it was actually a string15:27
nprivalovaoh, I have so many questions about Glance nnotifications today…15:27
apmelton1it was just a string message about the error15:27
*** sushils has joined #openstack-meeting15:27
sandy__dhellmann, things ... just the consumer always assumed payloads are dicts, so get() failed15:27
dhellmannapmelton1: ah15:27
silehtglance doesn't use oslo incubator for rpc/notification so ....15:27
sandy__apmelton1, sorry, thanks ... same problem15:27
*** hvp has joined #openstack-meeting15:27
dhellmannsandy__: ok, that's a bug in ceilometer, I think15:27
dragondmpayloads *should* always be dicts :-P15:27
apmelton1sileht: I think they just switched to oslo messaging15:27
dhellmannbecause we don't get to dictate the notification body or payload format15:27
dhellmanndragondm: I'd like that, too. :-)15:28
sandy__dragondm, yeah, until they're not15:28
thomasemdragondm, optimism, I like it.15:28
silehtapmelton1, good news15:28
apmelton1definitely15:28
dhellmannsileht: yet, right? :-)15:28
nprivalovasileht, apmelton1, yes, they did15:28
dhellmannapmelton1: oh, good news indeed15:28
nprivalovano :)15:28
silehtdhellmann, I have fight and fail to get oslo-incubator in glance for havana15:28
*** IlyaE has joined #openstack-meeting15:28
sandy__so, I guess my only concern with this discussion is similar to one we always have in openstack ...15:29
sandy__"I need X"15:29
dperazabtw I think there is work schedule on glance to support oslo notification15:29
*** suo has quit IRC15:29
sandy__"well, we're working on a thing to handle X, somewhat"15:29
dperazatrying to find the link15:29
jd__Alexei_987: does that cover enough of your initial question?15:29
dragondmdhellmann: we don't get to dictate what keys are  in the payload. It should be a dict. We don't have much of a spec for notifications, but that's in what we have.15:29
sandy__"but it's not ready and will be a big change"15:29
sandy__"so, wait until it's ready and use it"15:29
Alexei_987well I think we are agreed that validation is needed :)15:29
dhellmanndragondm: it sounds like that will be fixed in glance in I, then?15:29
sandy__... meanwhile, innovation suffers and nothing gets done15:29
Alexei_987but not agreed about how to do it15:29
nprivalovadperaza, please! We are digging the new Glance code but cannot make notification work15:30
*** suo has joined #openstack-meeting15:30
Alexei_987but again I'll make a blueprint for this stuff15:30
Alexei_987so partially covered15:30
dperazahold on15:30
sandy__we're left, sitting at the end of pipe, waiting for a library to come out ... vs, solving the problem, moving on and refactoring commonality later15:30
sandy__we're so afraid of duplication that movement forward suffers15:31
thomasemAlexei_987, It's in contracts. Each component must use X notification format, and that's all we can rely on. Payloads are relatively freeform, but the envelope (things like 'generated') we need to be able to rely on. If we can't trust these components, then we'll spend all day validating and slow the system to a halt at scale.15:31
dhellmannsandy__: I'm not sure what you're talking about here. I asked Alexei_987 to use an existing library instead of making a new one, and to not enforce rules that are wrong by rejecting data at the wrong level.15:31
dperazawow15:31
dperazahttps://bugs.launchpad.net/glance/+bug/102074915:31
uvirtbotLaunchpad bug 1020749 in glance "Use Openstack-Common notifier" [Wishlist,Won't fix]15:31
dperazawon't fix15:31
dperazathat sucks15:31
thomasemyouch15:32
nprivalovaoh no...15:32
dperazawhat about that last comment though15:32
eglynnwon't because it already uses olso.messaging, no?15:32
jd__they moved to oslo.messaging AFAIK, no?15:32
silehtyes15:32
gordchttps://review.openstack.org/#/c/57678/15:32
silehtI have checked15:32
* jd__ high fives eglynn 15:32
thomasemAlexei_987, But that's just my thoughts on it. :)15:32
eglynnjd__: :)15:32
thomasemsentiment, more or less15:32
* Alexei_987 sigh15:33
dhellmanndperaza: if you look, it is "wont fix" because the dev wants to use oslo.messaging instead of the incubator version of the code, which is the right approach now that it is released15:33
nprivalovajd__, the did! I saw this code in master. today :) but...15:33
Alexei_987openstack contribution can be such a pain sometimes15:33
*** eharney_ has joined #openstack-meeting15:33
jd__I think we are diverging so I'll move to the next topic15:33
jd__#topic First stable/hava release immenent (eglynn)15:33
*** openstack changes topic to "First stable/hava release immenent (eglynn) (Meeting topic: ceilometer)"15:33
*** kgriffs has left #openstack-meeting15:33
eglynnjust a quick heads-up that the first realse off stable is about to fly15:33
dperazaok and 57678 is merged so can we assume glance does support oslo notifications now?15:34
eglynnhttps://launchpad.net/ceilometer/+milestone/2013.2.115:34
eglynn... and a plea to get more folks involved in stable-maint15:34
sandy__dhellmann, and that's fine, so long as the library does what Alexei_987 needs ... otherwise it can turn into yak shaving to do something relatively simple.15:34
*** mdomsch has quit IRC15:34
nprivalovadperaza, I cannot prove it works15:34
*** eharney has quit IRC15:34
dhellmanneglynn: what's the status with that sphinx issue? did that have any impact on us?15:35
dperazanprivalova: sounds like a bug15:35
nprivalovadperaza, old code works ok but when switch to master no notification comes15:35
eglynndhellmann: which sphinx issue do you mean?15:35
eglynn... in any case 2013.2.1 is well frozen at this stage15:36
sandy__nprivalova, the new notification system uses entry points, so the configs have to change15:36
nprivalovadperaza, I'm trying to talk to glance guys in irc but no answer yet15:36
dhellmannwasn't there a problem with a new release of sphinx breaking builds on stable branches?15:36
eglynn... so I don't think it'll be getting in15:36
dragondmwas that the version issue ?15:36
dhellmannfolks, please, we've changed topics15:36
silehtdhellmann, the new 1.2 version15:36
*** haomaiwa_ has joined #openstack-meeting15:36
dhellmannright ^^15:36
dhellmanneglynn: if you don't know about it, I assume it didn't break our stable builds :-)15:36
llu-laptophttps://launchpad.net/bugs/1259511, is this the sphinx issue dhellman mentioned?15:36
uvirtbotLaunchpad bug 1259511 in openstack-ci "sphinx docs gating jobs are broken (source_dir must be a directory)" [Critical,Fix released]15:36
dhellmannyes15:37
dperazanprivalova: if you open a bug I can help you get to glance folks15:37
dhellmannthanks, llu-laptop15:37
dragondmYah, I saw the requirements change for that.15:37
*** haomaiwang has quit IRC15:37
*** luQAs has quit IRC15:38
nprivalovasandy__, if you have an example or a link to docs about new configs please share15:39
llu-laptopThis seems only affect test-requirement15:39
eglynnllu-laptop: yeap, just about to say that15:39
jd__eglynn: what's required to get involved in stable-maint?15:39
eglynnwill look into it further after this meeting15:40
*** ivasev has joined #openstack-meeting15:40
eglynnjd__: preparedness to spread the backporting religion ;)15:40
*** galstrom_zzz is now known as galstrom15:40
eglynnjd__: nah, it's mainly just reviewing patches proposed to stable/havana15:40
jd__eglynn: ok :)15:41
eglynnjd__: and trawling the bugs fixed on master for backporting candidates15:41
sandy__nprivalova, sec15:41
*** fnaval has joined #openstack-meeting15:41
jd__make sense15:41
eglynnand that second task is the one I'd like push onto the original bug fixer15:41
*** rnirmal has joined #openstack-meeting15:41
jd__eglynn: we should imaginate an automatic system to help with that I think15:41
eglynnif poss, to at least tag good backporting candidates15:41
*** stevemar has joined #openstack-meeting15:42
*** garyk has quit IRC15:42
*** sacharya has quit IRC15:42
eglynnjd__: yeah, that would be cool ... once the fix lands on master, some prompt or cue to consider for backporting15:42
jd__eglynn: yes, not sure how it could be done, but let's keep that in mind, it'd even serve all projects15:43
sandy__nprivalova, same flags, but names are now entry points: https://github.com/openstack/oslo.messaging/blob/master/setup.cfg#L45-L5015:43
eglynnyep, it's a neat idea15:43
rajdeepresolution to sphinx issue https://github.com/openstack/nova/blob/master/tox.ini#L915:43
jd__anything else on that matter eglynn or should I move on?15:43
eglynnjd__: fire away!15:43
jd__#topic Release python-ceilometerclient?15:43
*** openstack changes topic to "Release python-ceilometerclient? (Meeting topic: ceilometer)"15:43
eglynnno need that I'm aware of15:44
jd__cool then15:44
jd__#topic Open discussion15:44
*** openstack changes topic to "Open discussion (Meeting topic: ceilometer)"15:44
dperazaI have something realted to validation15:44
dragondm^ Not til' the event api lands, anyway.15:44
dperazatrying to handle this bug15:44
rajdeepi had a question on integrating vCenter integration into ceilometer15:45
llu-laptopeglynn: one question for you, about https://bugs.launchpad.net/ceilometer/+bug/1260176, which method you think I should take?15:45
uvirtbotLaunchpad bug 1260176 in ceilometer "different behavior of alarm creation on different DB backend" [Undecided,New]15:45
dperazahttps://bugs.launchpad.net/ceilometer/+bug/124536715:45
uvirtbotLaunchpad bug 1245367 in ceilometer "Doing non-existing metadata property filter can not get expected error prompts" [Medium,Triaged]15:45
eglynnllu-laptop: looking15:45
rajdeepwe are trying to map the measurements between ceilometer and vsphere15:45
*** luQAs has joined #openstack-meeting15:46
dperazamy take on 1245367 is that there is no way to differentiate from a query with bad metadata fild and a query with valid field that simply does not match15:46
*** nermina has quit IRC15:46
rajdeepQuestion : what is the guideline to add hypervisor specific metrics15:46
ityaptinjd__, I've question about change  https://review.openstack.org/#/c/59214/.15:47
dperazaI gather that is as design in ceilometer15:47
eglynnllu-laptop: so are the foreign constraints actually serving any real purpose if we ensure that they're always satisified by creating the user and project IDs if absent?15:47
Alexei_987dperaza: I'm afraid that we cannot do much here. since there is no way to determine is meta filter valid15:47
dperazain both cases they return 20015:47
gordcllu-laptop:  i added a comment to that bug15:47
nprivalovaand I'm looking for one core reviewer more for https://review.openstack.org/#/c/52670/15:47
jd__ityaptin: shoot15:47
*** adrian_otto has quit IRC15:48
eglynnllu-laptop: I don't think a constraint that we ensure is always met really adds any value TBH, or?15:48
jd__rajdeep: do you have an example?15:48
dperazaAlexei_987 so you agree with me on do nothing here?15:48
rajdeepyes cpu.usagemhz.average metric in vsphere15:49
jd__dhellmann: I think you should take a look at https://review.openstack.org/#/c/52670/ for nprivalova15:49
rajdeepthere is not corresponding metric in nova15:49
llu-laptopeglynn: agree15:49
jd__rajdeep: just create a new meter for that then15:49
* dhellmann dutifully clicks on the link from jd__ 15:49
rajdeepanother example power.energy.summation15:49
*** mrunge has quit IRC15:49
jd__dhellmann: I re-hire you then! :)15:49
thomasemdperaza, Alexei_987: I suppose that's an unfortunate case for arbitrary metadata items, huh? :(15:49
eglynnllu-laptop: coo, so method 1 looks more sensible to me15:49
gordcdperaza: i think it's working as designed. that 500 error is wrong though i think.15:49
rajdeepok and for metrics which are non existing in vsphere i am assuming we leave them blank15:50
dhellmannjd__: woo!15:50
Alexei_987thomasem: yes15:50
eglynnllu-laptop: I'll add a comment on LP to that effect15:50
dperazaI think 500 is wrong too gordc15:50
jd__500 is always wrong, isn't it?15:50
dperazaI added a note that what i see for no-metadata fields is a 40015:50
gordcjd__: comments on https://bugs.launchpad.net/ceilometer/+bug/1245367 (since it's marked as a backport potential)15:50
*** nelsnelson has joined #openstack-meeting15:50
uvirtbotLaunchpad bug 1245367 in ceilometer "Doing non-existing metadata property filter can not get expected error prompts" [Medium,Triaged]15:50
dperazajd_: +115:50
llu-laptopeglynn: should it be method 1+2? because we need to create for un-exsiting project_id/user_id15:50
eglynnllu-laptop: won't we create when we see an actual sample with the previously unknown project/user ID?15:51
rajdeep -->For metrics which are non existing in vsphere i am assuming we leave them blank, please confirm15:51
eglynnllu-laptop: (as opposed to when we create an alarm)15:51
*** vkozhukalov has quit IRC15:51
Alexei_987jd__: a proposal for the next meeting is to think about the following - we should change data structure for MongoDB in such a way that we don't have do aggregation for realtime queries15:52
thomasemdperaza, Do we spit back out the query for human intervention?15:52
thomasemSince that's something we can't really assess, a human can.15:52
*** MaxV has quit IRC15:52
jd__llu-laptop: eglynn: I hope I'm not saying something wrong, but in the case where we would envision to split the sample and alarm database storage, dropping the foreign key makes even more sense15:52
thomasem"Nothing found for <query>, are you sure this is correct?"15:52
jd__Alexei_987: I don't think it's a subject for a _meeting_, sounds like you want to write a blueprint + wiki page spec and discuss that on the mailing list15:53
gordcquick q, anyone know status of alembic migrations? we ever going to move to them? we might need to decide how to handle our existing alembic migrations.15:53
ityaptinIt's required run unit tests with Postgresql environment like https://review.openstack.org/#/c/59489/. I want add unit tests with postgresql with dependence on your change request and suggest my fix without these tests.15:53
Alexei_987jd__: Ok15:53
ityaptin_jd It's required run unit tests with Postgresql environment like https://review.openstack.org/#/c/59489/. I want add unit tests with postgresql with dependence on your change request and suggest my fix without these tests.15:53
*** yaguang has quit IRC15:53
jd__gordc: I think we lost everybody on that, you can be my hero if you take this over15:54
eglynnjd__: yeap, it would be more flexible that way (... tho' I'm not sure such a split is on the cards, at least in the short to medium term, or?)15:54
ityaptinjd__ It's required run unit tests with Postgresql environment like https://review.openstack.org/#/c/59489/. I want add unit tests with postgresql with dependence on your change request and suggest my fix without these tests.15:54
*** ildikov_ has joined #openstack-meeting15:54
dperazathomasem: do you mean in the response15:54
gordcjd__: ok i'll post on mailing list to get a good direction.15:54
llu-laptopeglynn: for sample, we create new user/project id if they're not not existed. Should we do this for alarm creation too? and drop the foreign key constaits?15:54
*** antonym has quit IRC15:54
*** katyafervent has joined #openstack-meeting15:54
dperazaeven if query is bad it looks like not matching query15:54
*** topol has joined #openstack-meeting15:54
herndongordc I'm happy to help out with that15:54
hvphave a question on https://blueprints.launchpad.net/ceilometer/+spec/central-agent-improvement15:54
thomasemdperaza, Sure. So, it's just an idea, but returning the query back to the client will allow it to be assessed.15:55
jd__eglynn: just thinking out loud, but as anyway user are just id, there even shouldn't be a user table anyway so I think dropping the key and the table is the way to go15:55
silehtllu-laptop, mongo doesn't have this constraint15:55
gordcherndon: cool. let's discuss it.15:55
jd__eglynn: I meant the foreign key reference15:55
dperazabut the client just build the query, right15:55
eglynna-ha I see15:55
dperazanot sure we gain much sending back same query15:56
dperazaall we can do is what we do now15:56
*** oubiwan__ has quit IRC15:56
jd__hvp: ?15:56
hvpIs this blueprint also considering a multi-datacenter active/active central agent polling multiple sources (openstack endpoints) ?15:56
thomasemdperaza, Agreed. Sorry, I was just thinking of another alternative to validation. :)15:56
dperazaright, there is not match it is up to client to then check is a good query before trying again then15:57
nealphhvp: IIRC, the summit conversation did include that aspect.15:57
*** s3wong has joined #openstack-meeting15:58
hvpwe have multiple openstack endpoints in different data centers and having a unified ceilometer infrastructure would be ideal15:58
hvpnealph, sorry i joined late15:58
eglynnllu-laptop: ok, is the reason we ensure the user & project ID exist on alarm creation is just to fullfil the foreign key constraint, or because we feel "it's the right thing to do"?15:58
thomasemOkay. I think it'd be awesome for us to call out that limitation in our documentation. That we can't validate arbitrary fields like that.15:58
thomasemThen clients can approach with a more accurate expectation.15:58
dperazathomasem: I will handle that15:58
eglynnllu-laptop: and if we're keeping the logic to ensure the user & project ID, exist ... why drop the FK constraint?15:59
dperazagood sugestion15:59
jd__hvp: nop, that'd be another blueprint I think15:59
thomasemdperaza, Thank you! :)15:59
*** paragan has quit IRC15:59
*** gordc has quit IRC15:59
jd__eglynn: llu-laptop: drop it! drop it all!15:59
nealphjd__: certainly the task distribution part of the BP is related?15:59
silehteglynn, the mongodb backend doesn't ensure that15:59
jd__nealph: that'd be all I think15:59
hvpjd_, so it will still have some dependencies on the central agent improvements15:59
*** Guest53164 has joined #openstack-meeting15:59
jd__hvp: like nealph said :)16:00
eglynnsileht: yep, so say we change mongo to do what sqlalchemy does16:00
jd__that'd be terrible! :)16:00
eglynnsileht: ... in that case, why also drop the FK constraint?16:00
llu-laptopeglynn: Aah, you're right. Seems there is no need to make sure the user/project_id existing in alarms perspective?16:00
*** otherwiseguy has quit IRC16:00
*** MaxV has joined #openstack-meeting16:00
jd__it's time to wrap up guys16:00
*** otherwiseguy has joined #openstack-meeting16:01
nprivalovajd__, please take a look on ityaptin's question later16:01
silehteglynn, the question is what is the purpose of project/user storage API, samples only or everything in ceilometer ?16:01
eglynnllu-laptop: that's what I'm thinking, so either drop the auto-create AND the FK constraint, or else get mongodb to auto-create also16:01
* dhellmann goes back to his sick-bed16:01
nealphhvp: in our experience, active/active is possible with some massaging of configs. curious if you have specific issues....ping me offline.16:01
*** oubiwan__ has joined #openstack-meeting16:01
*** gordc has joined #openstack-meeting16:01
hvpthx nealph.. will do16:02
*** gordc has left #openstack-meeting16:02
*** kgriffs has joined #openstack-meeting16:02
jd__nprivalova: thanks I missed it16:02
jd__ityaptin: I'll answer on #openstack-ceilometer16:02
jd__#endmeeting16:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:03
openstackMeeting ended Thu Dec 12 16:02:59 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-12-12-15.01.html16:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-12-12-15.01.txt16:03
openstackLog:            http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-12-12-15.01.log.html16:03
thomasemThanks everyone. Have a great day!16:03
thomasemor night.16:03
eglynnsileht: good question, I guess for alarms there are two purposes ... 1. segregating visiblility onto samples and 2. potentially billing for alarm-hours16:03
dragondmHave good one, all.16:03
*** absubram_ has quit IRC16:03
eglynnyep, see y'all!16:03
*** adalbas has joined #openstack-meeting16:04
*** greghill has joined #openstack-meeting16:04
*** adrian_otto has joined #openstack-meeting16:04
*** oubiwa___ has joined #openstack-meeting16:04
silehteglynn, so some piece of code is missing in mongo db :)16:04
eglynnsileht: yep, I'm tending to the same conclusion16:05
eglynnsileht: ... the opposite of what I said earlier ;)16:05
*** bgorski has joined #openstack-meeting16:05
*** greghill has quit IRC16:06
*** oubiwan__ has quit IRC16:06
*** greghill has joined #openstack-meeting16:06
silehteglynn, I think if we drop the v1 api, this can be a driver detail16:07
*** llu-laptop has quit IRC16:07
*** ywu has joined #openstack-meeting16:07
*** yamahata_ has quit IRC16:07
eglynnsileht: yeah, that'll a bit down the road though before we can unshackle ourselves from v116:07
*** Guest53164 has quit IRC16:07
*** gkleiman has joined #openstack-meeting16:09
*** gkleiman_ has joined #openstack-meeting16:09
*** gkleiman_ has quit IRC16:09
*** nealph has quit IRC16:09
*** ArthurBerezin has joined #openstack-meeting16:09
*** dhellmann is now known as dhellmann_16:10
*** Leo_ has joined #openstack-meeting16:11
*** galstrom is now known as galstrom_zzz16:12
*** colinmcnamara has joined #openstack-meeting16:12
*** galstrom_zzz is now known as galstrom16:12
*** colinmcn_ has joined #openstack-meeting16:12
*** herndon has quit IRC16:14
*** sacharya has joined #openstack-meeting16:14
*** ArthurBerezin has left #openstack-meeting16:14
*** soren has quit IRC16:15
*** markmcclain has joined #openstack-meeting16:16
*** soren has joined #openstack-meeting16:16
*** rakhmerov has quit IRC16:18
*** rakhmerov has joined #openstack-meeting16:20
*** eharney_ is now known as eharney16:20
*** neelashah has quit IRC16:21
*** BrianB_ has quit IRC16:21
*** NikitaKonovalov has quit IRC16:21
*** SergeyLukjanov has quit IRC16:21
*** mrodden has joined #openstack-meeting16:22
*** changbl has joined #openstack-meeting16:22
*** oubiwa___ has quit IRC16:22
*** jtomasek has quit IRC16:24
*** nprivalova has quit IRC16:24
*** rakhmerov has quit IRC16:24
*** hvp has left #openstack-meeting16:26
*** MaxV has quit IRC16:27
*** rajdeep has quit IRC16:27
*** MaxV has joined #openstack-meeting16:27
*** MaxV has quit IRC16:28
*** MaxV has joined #openstack-meeting16:28
*** matiu_ has quit IRC16:28
*** adalbafk has quit IRC16:29
*** colinmcn_ is now known as colinmcnamara_16:29
*** acfleury has joined #openstack-meeting16:30
*** pablosan has joined #openstack-meeting16:30
*** spzala has joined #openstack-meeting16:30
*** oubiwan__ has joined #openstack-meeting16:31
*** belmoreira has quit IRC16:31
*** acfleury has quit IRC16:32
*** adalbas has quit IRC16:32
*** oubiwan__ has quit IRC16:32
*** adalbas has joined #openstack-meeting16:32
*** s0mik has joined #openstack-meeting16:33
*** AaronGr_Zzz is now known as AaronGr16:33
*** tristanC has joined #openstack-meeting16:33
*** markmcclain has quit IRC16:33
*** garyk has joined #openstack-meeting16:38
*** Abhishek_ has quit IRC16:38
*** herndon has joined #openstack-meeting16:39
*** otherwiseguy has quit IRC16:40
*** otherwiseguy has joined #openstack-meeting16:40
*** branen has joined #openstack-meeting16:41
*** jtomasek has joined #openstack-meeting16:42
*** flaper87 is now known as flaper87|afk16:42
*** Guest53164 has joined #openstack-meeting16:43
*** henrynash has joined #openstack-meeting16:44
*** Abhishek_ has joined #openstack-meeting16:45
*** Fdot has quit IRC16:45
*** venkatesh_ has quit IRC16:47
*** venkatesh has quit IRC16:47
*** jtomasek has quit IRC16:47
*** colinmcnamara has quit IRC16:47
*** boris-42 has quit IRC16:48
*** colinmcnamara_ has quit IRC16:48
*** colinmcnamara has joined #openstack-meeting16:48
*** avishayb has quit IRC16:48
*** colinmcnamara has quit IRC16:48
*** SumitNaiksatam has quit IRC16:48
*** 77CAAS3HQ has joined #openstack-meeting16:48
*** 65MAAD7S9 has joined #openstack-meeting16:48
*** 65MAAD7S9 is now known as colinmcnamara16:49
*** ekarlso has quit IRC16:50
*** diogogmt has joined #openstack-meeting16:50
*** ekarlso has joined #openstack-meeting16:51
*** gyee has joined #openstack-meeting16:53
*** henrynash has quit IRC16:53
*** luQAs has quit IRC16:54
*** comay has quit IRC16:55
*** comay has joined #openstack-meeting16:55
*** henrynash has joined #openstack-meeting16:55
*** AlanClark has joined #openstack-meeting16:56
*** Akhil has quit IRC16:56
*** haomaiwa_ has quit IRC16:58
*** emagana has joined #openstack-meeting16:58
*** jtomasek has joined #openstack-meeting17:00
*** adrian_otto has quit IRC17:00
*** pcm_ has joined #openstack-meeting17:00
*** anniec has quit IRC17:01
*** greghill has left #openstack-meeting17:01
*** pcm_ has left #openstack-meeting17:01
*** rongze_ has quit IRC17:01
*** Ravikumar_hp has joined #openstack-meeting17:02
*** adrian_otto has joined #openstack-meeting17:02
*** kwhitney has joined #openstack-meeting17:02
*** henrynash has quit IRC17:02
*** Ravikumar_hp has quit IRC17:02
*** Ravikumar_hp has joined #openstack-meeting17:03
*** safchain has quit IRC17:03
*** mdurnosvistov has quit IRC17:05
*** SumitNaiksatam has joined #openstack-meeting17:05
*** MaxV has quit IRC17:06
*** chanthru has joined #openstack-meeting17:06
*** s3wong has left #openstack-meeting17:06
*** jhenner has quit IRC17:06
*** afazekas has quit IRC17:10
*** jcoufal_ has quit IRC17:10
*** amotoki has joined #openstack-meeting17:13
*** giulivo has joined #openstack-meeting17:13
*** rudrarugge has joined #openstack-meeting17:13
*** SergeyLukjanov has joined #openstack-meeting17:14
*** jtomasek has quit IRC17:15
*** NikitaKonovalov has joined #openstack-meeting17:18
*** lsmola has quit IRC17:18
*** garyk has quit IRC17:21
*** gkleiman has quit IRC17:21
*** BillStokes has quit IRC17:25
*** BillStokes has joined #openstack-meeting17:26
*** chanthru has quit IRC17:26
*** Ravikumar_hp has quit IRC17:27
*** Ravikumar_hp has joined #openstack-meeting17:27
*** garyk has joined #openstack-meeting17:28
*** jaypipes has quit IRC17:28
*** AlexF has quit IRC17:29
*** adrian_otto has left #openstack-meeting17:31
*** doug_shelley66 has joined #openstack-meeting17:32
*** blamar has quit IRC17:33
*** dougshelley66 has quit IRC17:33
*** samcdona has quit IRC17:34
*** beyounn has joined #openstack-meeting17:34
*** nati_ueno has quit IRC17:34
*** elo1 has joined #openstack-meeting17:37
*** elo1 has quit IRC17:40
*** Mandell has quit IRC17:40
*** NikitaKonovalov has quit IRC17:41
*** hemnafk is now known as hemna17:41
*** beyounn has quit IRC17:42
*** amotoki has quit IRC17:42
*** NikitaKonovalov has joined #openstack-meeting17:43
*** emagana has quit IRC17:46
*** dkranz is now known as dkranz_at_lunch17:48
*** crank has quit IRC17:49
*** oubiwan__ has joined #openstack-meeting17:49
*** sriramhere has joined #openstack-meeting17:49
*** crank has joined #openstack-meeting17:50
*** Ravikumar_hp has quit IRC17:50
*** IlyaE has quit IRC17:51
*** hyakuhei_ is now known as hyakuhei17:51
*** elo has joined #openstack-meeting17:51
*** Ravikumar_hp has joined #openstack-meeting17:51
*** reed has joined #openstack-meeting17:51
*** markpeek has quit IRC17:52
*** rossella_s has quit IRC17:52
*** markpeek has joined #openstack-meeting17:52
*** eharney has quit IRC17:54
*** crank has quit IRC17:56
*** samcdona has joined #openstack-meeting17:56
*** stevemar has quit IRC17:57
*** yassine has quit IRC17:58
*** bdpayne has joined #openstack-meeting17:58
*** derekh has quit IRC17:58
*** 77CAAS3HQ has quit IRC17:59
*** colinmcnamara has quit IRC17:59
*** crank has joined #openstack-meeting17:59
*** burt has quit IRC17:59
*** bknudson has joined #openstack-meeting18:00
*** nati_ueno has joined #openstack-meeting18:00
bdpayne#startmeeting OpenStack Security Group18:01
openstackMeeting started Thu Dec 12 18:01:22 2013 UTC and is due to finish in 60 minutes.  The chair is bdpayne. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: OpenStack Security Group)"18:01
openstackThe meeting name has been set to 'openstack_security_group'18:01
bknudsonhi18:01
bdpayne#topic Rollcall18:01
*** openstack changes topic to "Rollcall (Meeting topic: OpenStack Security Group)"18:01
bknudsonpresent18:01
bdpayneHi everyone, please checkin if you're here for the OSSG meeting18:01
hyakuheiGood morning/afternoon/evening from Rob @ HP18:01
sriramheremorning18:02
tristanCHello folks!18:02
*** nkinder has joined #openstack-meeting18:02
nkindero/18:02
*** ygbo_ has quit IRC18:02
*** malini1 has joined #openstack-meeting18:02
bdpayneexcellent, looks like we have a nice group18:02
*** paulmo has joined #openstack-meeting18:02
bdpayne#topic Agenda18:02
*** openstack changes topic to "Agenda (Meeting topic: OpenStack Security Group)"18:02
malini1good morning, back from all my travels18:03
paulmoPaul Montgomery here a bit late18:03
*** malini has joined #openstack-meeting18:03
bdpayneSo for today I wanted to mention one thing that I've just started working on (a new wiki page)18:03
bdpayneAnything else people want to discuss?18:03
*** NikitaKonovalov has quit IRC18:03
*** Swami has joined #openstack-meeting18:03
hyakuheiOSSNs at some point18:03
bdpayneok, noted on OSSNs18:04
sriramhereI wanted to update on the meeting with OSSG editors18:04
bdpaynesounds good18:04
bdpayneok, so we'll just take these from top to bottom18:04
nkinderbdpayne: I'm also working on a new wiki page for OSSNs18:04
bdpayne#topic Wiki Pages18:04
*** openstack changes topic to "Wiki Pages (Meeting topic: OpenStack Security Group)"18:04
bdpaynenkinder you have the link?18:04
nkinderbdpayne: https://wiki.openstack.org/wiki/Security_Notes18:05
bdpayneexcellent18:05
nkinderI only have one OSSN posted thus far, but I'm going through all of the older ones18:05
bdpayneSo I wanted to mention that I have just started putting together a wiki page to list the various projects people in OSSG are working on18:05
*** NikitaKonovalov has joined #openstack-meeting18:05
bdpaynehttps://wiki.openstack.org/wiki/Security/Projects18:05
bdpayneI listed the book editors as an example18:05
bdpayneBut would like to see this filled out with other security projects18:06
bdpayneI know there are many, so I'll go back and check my notes18:06
bdpayneMy goal is for this to serve 2 purposes18:06
bdpayne1) To help advertise the work that's happening and perhaps draw in more people to participate18:06
bdpayne2) To bring these efforts more formally into the group18:06
*** bpb has joined #openstack-meeting18:07
*** eharney has joined #openstack-meeting18:07
hyakuheiI like it, nkinder shouldn't take long to add in the other OSSNs :)18:07
bdpayneOn (2), I'll be aiming to have the project leads checkin at this meeting from time to time18:07
hyakuheiObvious things would be the VMT involvement (which needs to be pushed)18:07
hyakuheiand the threat analysis work18:07
bdpayneyeah18:07
*** eglynn has quit IRC18:07
bdpayneso, I encourage anyone in OSSG to edit this page and add in other projects18:07
bdpaynetry to use the same template that I've put together18:08
bdpaynejust to keep it looking clean18:08
*** asselin has joined #openstack-meeting18:08
bdpayneany thoughts / questions on that?18:08
hyakuheiLooks good thus far18:08
nkinderyeah, sounds like a good idea18:08
sriramherebryan - just to be clear, this will be the landing projects for all the little projects OSSG is involved18:08
sriramherelike editing, OSSN, threat analysis etc18:08
bdpaynelanding page, yeah18:08
bknudsona project I've been thinking about is a tempest scenario test that configures the system securely18:09
bdpayneexactly18:09
nkinderWe should add a link from the OSSG team page on launchpad18:09
bdpayneyeah, once this is fillout out some more, I'd like to link to it from a variety of places18:09
sriramhereOSSG page already exists rr?18:09
sriramherehttps://launchpad.net/~openstack-ossg18:09
hyakuheibknudson: A secure distribution?18:09
hyakuheisriramhere: yeah but putting it on the wiki is a better idea imho18:10
bknudsonhyakuhei: not sure what would be the way to do it, but I think tempest uses devstack... so it would involve making sure devstack can configure system18:10
tristanC+1 for a landing page, it's isn't easy to understand what is the OSSG (beside the launchpad page)18:10
bknudsonconfigure a system with SSL everywhere.18:10
sriramheresorry, i mistook that you wanted a new opage in launchpad18:11
nkinderbdpayne: I'll work on filling in the cross-project security guidelines placeholder18:11
bdpaynenkinder great, thanks18:11
bdpayne#topic OSSNs18:11
*** openstack changes topic to "OSSNs (Meeting topic: OpenStack Security Group)"18:11
hyakuheibknudson: For that to be a useful project you really need a lot of moving pieces that aren't part of the standard distro (like a CA) I think perhaps looking at releasing hardened chef recipies or something might actually have move value18:11
hyakuheiRight18:11
hyakuheiWe have two open OSSNs18:12
hyakuheisriramhere and nkinder assigned18:12
hyakuheiNeither have drafts yet, guys is there anything you need?18:12
hyakuheiEditing / Research etc?18:12
nkinderhyakuhei: yeah, I just grabbed that Keystone one the other day.  I need to start researching it.18:12
*** vkozhukalov has joined #openstack-meeting18:12
nkinderhyakuhei: I was wrapping up the glance one I sent out yesterday first.18:12
bdpayneJust a comment on the OSSNs...18:13
hyakuheiok cool, if you need help feel free to post on the OSSG ML.18:13
bdpayneI think that running the drafts by the PTLs should be the policy18:13
nkinderbdpayne: +118:13
bdpayneWe got some very good feedback by doing that with the Glance one18:13
hyakuheiMakes sense18:13
bdpayneand it's just good politics too18:13
nkinderbdpayne: I want to document a list of how to write a OSSN on the wiki18:13
hyakuhei+118:13
sriramhereno, i will work on sending the draft for review before next meeting. Fallen back due to thanksgiving break18:13
*** pvaneck has joined #openstack-meeting18:13
nkinderSo template, where to publish, who to contact for reviews18:13
*** johnthetubaguy has quit IRC18:13
hyakuheisriramhere: great :)18:14
hyakuheibdpayne: I'll take that action18:14
bdpaynecool18:14
nkinderI think a review by PTL and one peer from OSSG is a good idea.18:14
bdpayneyeah18:14
hyakuheiI've been thinking do we want some sort of numbering for them too?18:14
nkinderhyakuhei: Yes, agreed18:14
nkinderhyakuhei: even date based18:14
sriramherenumbering? you mean +1 -1?18:14
sriramhereor order?18:14
hyakuheiNo I mean OSSN-2013-22...18:14
bdpaynelike the CVE numbering scheme?18:15
hyakuheiYeah18:15
sriramhereok, good18:15
nkindersriramhere: VMT numbers OSSA's IIRC18:15
hyakuheiindeed they do18:15
nkinderYeah, we should be in-line with what they do18:15
hyakuheiOk so I think we can keep on top of this as a manual process for now18:15
nkinderI think this is important if we start publishing using a structured format like CVRF as well.18:15
hyakuheiI'll continue to 'manage' the OSSNs, help where editing etc is required and I'll get that wiki page thrown together18:15
*** rakhmerov has joined #openstack-meeting18:16
nkinderhyakuhei: should we retroactively number the previous OSSNs?18:16
hyakuheinkinder: yeah. I'm not sure a structured format is as important for OSSN vs OSSA but I have no objection to adopting it either18:16
sriramherebug ids wont suffice for now?18:16
hyakuheinkinder: Probably. However, as we're about to go into 2013, we've got a natural brake line18:17
bdpayneI think using a common structured format for both OSSN and OSSA would be useful18:17
hyakuheisriramhere: Having an ID makes it easier when people start discussing which OSSNs apply where.18:17
*** ayoung is now known as Ed_Gruberman18:17
hyakuheiThinking ahead to when we have one per week (potentially)18:17
hyakuheibdpayne: yeah, I've got no big objection to using CVRF18:17
nkinderbdpayne: It would also allow us to generate the other published formats (wiki, e-mail, etc.)18:17
sriramhereok coo. just it is 2014 not 2013 :)18:18
hyakuheipffft18:18
hyakuheioff by ones happen!18:18
bdpaynestill 2013 where I'm sitting :-)18:18
hyakuheiok cool, so what did I just agree to do.18:18
hyakuheiI'll put together a wiki page, describing how I think the process should look in the future18:18
bdpayne#action hyakuhei to fix everything18:18
hyakuheiand we can go over it next week18:18
hyakuheiincluding numbering and format etc18:18
bdpayne:-)18:18
hyakuheiwow, just like being at work18:19
bdpayneyeah, that sounds reasonable18:19
*** andreaf has quit IRC18:19
nkinderhyakuhei: let me know if you want a review or any help on it before then18:19
hyakuheiCheers :)18:19
bdpayne#topic Book Editors18:19
*** openstack changes topic to "Book Editors (Meeting topic: OpenStack Security Group)"18:19
*** Ed_Gruberman is now known as Mr_Barnard_Rm_1218:19
bdpaynesriramhere you wanted to discuss this?18:19
sriramhereupdate: David Mortman, Bryan and Myself synced up earlier this week on what are the steps here18:20
hyakuheiI've done a bunch of editing and I'd like to do more. I just need to get better at wranging my inbox to see when things come up.18:20
sriramhereOnce Ben is back from conference next week, we are going to start diving up to start style/ grammatical fixes first18:20
sriramherewe will firs come up with a plan/ schedule and publish it to the team and go from there18:20
sriramherehoping to get hold of Ben before next thurs18:21
hyakuheiSeems reasonable. I wonder how much technical-proof readers charge.18:21
bdpayneSo we do have this team of three editors to help drive the effort... but anyone is welcome to continue making contributions18:21
hyakuheioh, teams! I like teams, they feel so inclusive!18:21
sriramhererob - you are on fire tooday!18:21
bdpaynehyakuhei I could actually find out the answer to that question (cost for technical editors)18:22
bdpaynebut does anyone actually have $$ for that?18:22
*** Mr_Barnard_Rm_12 is now known as ayoung18:22
* hyakuhei has had a long week18:22
hyakuheibdpayne: depends on the cost, it's worth having some idea of the cost18:22
sriramherei thought thtat was a fun question -18:22
hyakuheibecause, if we're collectively burning FTE that could be more easily purchased by someone else...18:22
sriramherei have some friends in publishing (non--tech) industry18:23
sriramherecan find out.18:23
bdpayneI'll explore too18:23
bdpayne#topic Open Discussion18:23
*** openstack changes topic to "Open Discussion (Meeting topic: OpenStack Security Group)"18:23
sriramhereas of now, it was volunteer/ interest18:23
bdpayneAnything else people would like to discuss today?18:23
paulmoI had a few quick things18:23
sriramherewho runs http://www.secstack.com/?18:23
paulmoI'm not sure if anyone has seen these automated database exploitation tools but they may be useful in OpenStack: https://github.com/tcstool/NoSQLMap and http://sqlmap.org/18:24
bdpayneWorth mentioning that Barbican is trying to get incubated http://lists.openstack.org/pipermail/openstack-dev/2013-December/020830.html18:25
hyakuheisriramhere: Matt Joyce18:25
sriramherethanks Rob18:25
bknudsondoes anyone here know of a good static analysis tool for python?18:25
hyakuheiSuch things do not really exist...18:25
paulmoI think pylint is about as good as it gets from what I've found18:25
hyakuheiFortify has _some_ support18:25
bknudsonhyakuhei: that is my guess18:25
clarkbbknudson: yes, there is one laying around that I was playing with recently18:25
clarkbnow I have to find it and remember what it was called18:26
nkinderI've also been doing a lot of review on the KDS side of things for Keystone.18:26
*** crank has quit IRC18:26
bknudsonThere's a tool called RATS that we (IBM) ran recently18:26
hyakuheibut applying SA to a language like Python is always going to be tricky, there are some interesting, if immature, DA projects though - making use of various introspection capabilities18:26
*** ndipanov has quit IRC18:26
bdpaynenkinder good to know on the KDS stuff18:26
bknudsonand we wound up opening a few bugs18:26
hyakuheibknudson: any good?18:26
bdpaynethey need eyes there!18:26
bknudsonhyakuhei: I was not impressed.18:26
hyakuheiKDS is scary looking18:26
hyakuheiI've asked Jeff to have a look into it18:26
nkinderbdpayne: I've been looking at the API side of things mostly at this point.18:27
clarkbbknudson: https://pypi.python.org/pypi/radon18:27
hyakuheinkinder: makes sense18:27
nkinderhyakuhei: ok, I have a pretty good understanding of the approach, so I can help answer any questions.18:27
*** salv-orlando has joined #openstack-meeting18:27
bknudsonclarkb: thanks!18:27
hyakuheiGoes without saying but if anyone needs compute resource to run tools like this, I'll hook you up on the HP Cloud.18:27
morganfainbergclarkb, Oh nice! ++ on the thanks.18:27
bdpayneok, I think that about wraps it up for today18:28
tristanCalso, I didn't introduced myself, I joined the OSSG group today so hi folks :)18:28
hyakuheiNicely timed meeting, thanks bdpayne18:28
hyakuheiWelcome tristanC !18:28
bdpayneoh welcome!18:28
sriramherehi tristan18:28
bdpaynebrief intro tristanC?18:28
hyakuheiGood meeting to attend!18:28
tristanCthanks, nice to meet you18:29
nkindertristanC: welcome!18:29
tristanCI work at eNovance, and I should specialise on open stack security matters18:29
bdpaynegreat, glad to have you on board18:29
hyakuhei+118:29
sriramhere+118:29
bdpayneperhaps chat on the ML about your interests so we can help you find ways to get involved18:29
*** elo1 has joined #openstack-meeting18:29
*** dkranz_at_lunch is now known as dkranz18:30
bdpayneok, thanks all... have a good week18:30
bdpayne#endmeeting18:30
morganfainbergbdpayne, is this the normal time for the meeting?  I have been meaning to start attending, so i'll toss it on my calendar.18:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:30
openstackMeeting ended Thu Dec 12 18:30:24 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-12-12-18.01.html18:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-12-12-18.01.txt18:30
sriramherebye all, good week!18:30
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-12-12-18.01.log.html18:30
*** jeckersb is now known as jeckersb_gone18:30
bdpaynemorganfainberg yes, this is the normal time18:30
bdpayne1800 UTC on Thursdays18:30
tristanCI was thinking I could help on reviewing (like testing patch) on that page: https://bugs.launchpad.net/ossad18:30
morganfainbergbdpayne, awesome.  thanks ... now if i could only convince google calendar to do meetings in UTC...18:31
*** jeckersb_gone is now known as jeckersb18:31
*** bgorski has quit IRC18:31
morganfainbergbdpayne, see ya here next week then :)18:31
tristanCbut maybe you need help elsewhere, I will write a mail to the ML18:31
*** mdenny has joined #openstack-meeting18:32
*** nkinder has left #openstack-meeting18:32
*** paulmo has left #openstack-meeting18:34
*** bdperkin is now known as bdperkin_gone18:35
*** sarob has joined #openstack-meeting18:36
*** Alexei_987 has quit IRC18:36
*** crank has joined #openstack-meeting18:37
*** bdperkin_gone has quit IRC18:40
*** malini1 has quit IRC18:41
*** bgorski has joined #openstack-meeting18:43
*** neelashah has joined #openstack-meeting18:45
*** eglynn has joined #openstack-meeting18:46
*** nati_uen_ has joined #openstack-meeting18:46
*** nati_ueno has quit IRC18:49
*** rakhmerov has quit IRC18:49
*** _ozstacker_ has joined #openstack-meeting18:51
*** ozstacker has quit IRC18:51
*** Shaan7 has joined #openstack-meeting18:51
*** Shaan7 has quit IRC18:51
*** Shaan7 has joined #openstack-meeting18:51
*** gyee has quit IRC18:52
*** nati_uen_ has quit IRC18:54
*** nati_ueno has joined #openstack-meeting18:55
*** s0mik has quit IRC18:59
*** blamar has joined #openstack-meeting18:59
*** Ravikumar_hp has quit IRC19:02
*** Ravikumar_hp has joined #openstack-meeting19:03
*** vuil has joined #openstack-meeting19:03
*** jgrimm has quit IRC19:03
*** s0mik has joined #openstack-meeting19:06
*** lblanchard has quit IRC19:07
*** k4n0 has joined #openstack-meeting19:08
*** Abhishek_ has quit IRC19:08
*** dstanek has joined #openstack-meeting19:08
*** NikitaKonovalov has quit IRC19:12
*** _radu has quit IRC19:13
*** NikitaKonovalov has joined #openstack-meeting19:14
*** NikitaKonovalov has quit IRC19:15
*** iv_m has joined #openstack-meeting19:23
*** bdperkin_gone has joined #openstack-meeting19:26
*** vipul is now known as vipul-away19:30
*** bdperkin_gone has quit IRC19:32
*** dims has quit IRC19:33
*** dims has joined #openstack-meeting19:34
*** salv-orlando has quit IRC19:36
*** salv-orlando has joined #openstack-meeting19:36
*** gokrokve has joined #openstack-meeting19:40
*** SergeyLukjanov_ has joined #openstack-meeting19:40
*** lblanchard has joined #openstack-meeting19:44
*** Mandell has joined #openstack-meeting19:44
*** vipul-away is now known as vipul19:44
*** SergeyLukjanov has quit IRC19:46
*** SergeyLukjanov_ is now known as SergeyLukjanov19:46
*** rakhmerov has joined #openstack-meeting19:46
*** SergeyLukjanov_ has joined #openstack-meeting19:47
*** SergeyLukjanov has quit IRC19:47
*** SergeyLukjanov_ has quit IRC19:48
*** SergeyLukjanov has joined #openstack-meeting19:48
*** novas0x2a|laptop has joined #openstack-meeting19:48
*** akuznetsov has quit IRC19:49
*** s0mik has quit IRC19:50
*** mspreitz has joined #openstack-meeting19:50
*** rakhmerov has quit IRC19:51
*** jprovazn has quit IRC19:58
*** jlibosva has quit IRC19:59
*** spredzy has joined #openstack-meeting20:00
harlowja#startmeeting state-management20:00
openstackMeeting started Thu Dec 12 20:00:55 2013 UTC and is due to finish in 60 minutes.  The chair is harlowja. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: state-management)"20:00
openstackThe meeting name has been set to 'state_management'20:01
harlowjahi folks!20:01
iv_mhi there20:01
harlowjahi hi20:01
k4n0hi20:01
harlowjajust got out of sprint meeting, let me update agenda20:01
*** ArxCruz has quit IRC20:01
harlowja*internal y! sprint stuff...20:01
mspreitzhi20:02
*** spredzy has quit IRC20:02
*** Ravikumar_hp has quit IRC20:02
*** stanlagun has joined #openstack-meeting20:02
harlowjahi mspreitz iccha k4n020:02
harlowjaok, updated20:02
harlowja#link https://wiki.openstack.org/wiki/Meetings/StateManagement#Agenda_for_next_meeting20:02
*** Ravikumar_hp has joined #openstack-meeting20:02
harlowjaguess lets do a quick last-action-items overview20:03
harlowja#topic action-items20:03
*** openstack changes topic to "action-items (Meeting topic: state-management)"20:03
harlowja#link http://eavesdrop.openstack.org/meetings/state_management/2013/state_management.2013-12-05-20.00.html20:03
harlowjaso i haven't caught up with boris yet (will try to do today)20:03
harlowjaas for little zookeeper example (to help out with review)20:03
*** akarpinska1 has joined #openstack-meeting20:04
harlowjapaste.openstack.org/show/54861/ is my current incarniation of that20:04
harlowjasteps at top should help20:04
harlowja#action harlowja really catchup with boris this time!20:04
iv_mif u want i can try to catch him in skype20:05
harlowjai can usually catch him on IRC, just i totally forget to ask him :-)20:05
harlowjaif i don't iv_m then lets skype20:05
harlowja*hopefully today, if he's still on20:06
harlowjaor tommorow20:06
*** spredzy has joined #openstack-meeting20:06
harlowjathx iv_m20:06
harlowjaiv_m any update on the snapshot nova flow and work?20:06
*** spredzy has quit IRC20:07
iv_mso, i failed my action item -- we are working on it, and came to some conclusion, and started to code it -- but no docs yet, sorry20:07
*** troytoman-away is now known as troytoman20:07
harlowjanp iv_m  :)20:07
*** IlyaE has joined #openstack-meeting20:07
harlowjastill being worked on, thats fine with me :)20:07
*** markmcclain has joined #openstack-meeting20:07
*** tsufiev_ has joined #openstack-meeting20:07
* iv_m just needs to write everything down20:08
harlowja:)20:08
*** denis_makogon_ has joined #openstack-meeting20:08
harlowja#action iv_m write all the things down!20:08
harlowjaha20:08
harlowjaall the things please :-P20:08
harlowjaha20:08
*** Ravikumar_hp has quit IRC20:08
iv_mwell, that'll need a lot of space down there20:09
harlowja:)20:09
*** Ravikumar_hp has joined #openstack-meeting20:09
harlowjaand alot of time20:09
iv_mbut i'll try to do my best anyway20:09
harlowjahaha, sweet20:09
harlowja#topic current integration work20:09
*** openstack changes topic to "current integration work (Meeting topic: state-management)"20:09
*** akuznetsov has joined #openstack-meeting20:09
*** elo1 has quit IRC20:09
harlowjaso i think we covered one of the current integration work that is ongoing (nova)20:10
*** cdub has joined #openstack-meeting20:10
harlowjaakarpinska1 is nearly there with the basic cinder work (thx akarpinska1 !)20:10
*** denis_makogon_ is now known as denis_makogon20:10
harlowjaalthough i think that one might be hitting some other major gate bugs20:11
harlowja#link https://review.openstack.org/#/c/58724/20:11
harlowjano so easy to tell20:11
iv_mya, looks like figting through gating bacame harder lately20:12
*** rfolco has quit IRC20:12
*** oubiwan__ has quit IRC20:12
*** kgriffs is now known as kgriffs_afk20:12
harlowjaya20:12
harlowja#link http://lists.openstack.org/pipermail/openstack-dev/2013-December/022052.html20:12
akarpinska1is it necessary to do rechecks until I get +1 from Jenkins?20:12
*** dcramer_ has quit IRC20:12
iv_myup20:12
harlowjaakarpinska1 if there is an active gate bug that is being fixed, then u can sorta wait till its fixed20:12
*** burt has joined #openstack-meeting20:12
harlowjabut ya, in general, jenkins needs to +1 it (which means the gate must not be broke)20:13
harlowjathe #openstack-infra team might have an idea whats going on (seems to change daily)20:13
*** vipul is now known as vipul-away20:13
*** vipul-away is now known as vipul20:13
harlowjaakarpinska1 so close though! :)20:13
harlowjai think other folks that are getting involved with taskflow + cinder very much appreciate your work :)20:14
*** vladikr has joined #openstack-meeting20:14
harlowjaanyone that is also working with cinder & taskflow want to add any questions/other (think there are others out there somewhere)20:14
*** jcoufal has joined #openstack-meeting20:14
*** stevemar has joined #openstack-meeting20:15
*** Ravikumar_hp has quit IRC20:15
harlowjaok, well don't be shy folks :)20:15
*** reed has quit IRC20:15
* akarpinska1 doing recheck20:15
harlowjathx akarpinska120:15
harlowjaas for other integration work, i think boris-42 is still experimenting with rally + taskflow20:16
harlowjaand same with mistral project20:16
harlowjaas usual20:16
harlowja#link https://etherpad.openstack.org/p/TaskflowIcehouseWhoWhatWhereWhy20:16
harlowja*where i track most of this20:17
*** bdperkin_gone has joined #openstack-meeting20:17
harlowjaalright, keep up the integration work folks, slowly but surely :)20:17
harlowja#topic new-use-cases20:18
*** openstack changes topic to "new-use-cases (Meeting topic: state-management)"20:18
*** bdperkin_gone is now known as bdperkin20:18
*** Ravikumar_hp has joined #openstack-meeting20:18
*** bdperkin has quit IRC20:18
*** bdperkin has joined #openstack-meeting20:18
harlowjaso any new issues or use-cases people want to talk about for taskflow20:18
*** Ravikumar_hp has quit IRC20:19
harlowjai started a little document that helps explain some of the mind-set change that taskflow might make happen20:19
harlowjareleated slightly to use-cases20:19
harlowja#link https://wiki.openstack.org/wiki/TaskFlow/Best_practices#Mind-Altering_Substances20:19
*** Ravikumar_hp has joined #openstack-meeting20:19
harlowja*no real substances there20:19
harlowjanice little place to gather common ideas, patterns, and such20:19
harlowjaas for other new-uses, iv_m  and akarpinska1 and a few others have been continuing to work on the 'worker' engine model20:20
harlowjawhich should enable some more neat use-cases20:21
harlowjaalso i expect https://review.openstack.org/#/c/60499/ (the tooz project) when combined with taskflow will also add even more20:21
harlowja#link https://github.com/stackforge/tooz20:21
*** crank has quit IRC20:22
harlowjaanyways, lots of room for new usage :)20:22
harlowja#action harlowja describe jobboard mindset change on best practices page20:22
*** dcramer_ has joined #openstack-meeting20:22
*** crank has joined #openstack-meeting20:22
*** cdub has quit IRC20:23
harlowjacool, anyways, feel free to bring new usecases and patterns :)20:23
harlowjaalways will to discuss them with folks20:24
harlowja#topic open-discuss20:24
*** openstack changes topic to "open-discuss (Meeting topic: state-management)"20:24
harlowjaiv_m do u want to give a little overview of the changes in the executor (futures) that u are thinkign about?20:24
* harlowja needs to get around to reviewing the changes that u did 20:24
harlowjaor maybe still to early for said discussion (which is fine)20:25
*** ryanpetrello has joined #openstack-meeting20:26
iv_mwell, the general idea is to have special entity that will know how to take task, its arguments, and apply one to another20:26
*** tsufiev_ has quit IRC20:26
iv_mit should have closer scope than current TaskAction, wich knows about storage and manages task state changes and suchlike20:26
harlowjasure, makes sense, to more focus just on executing, not the rest of the stuff20:27
iv_mso, #link https://blueprints.launchpad.net/taskflow/+spec/task-executor20:27
harlowjaah, thx for sharing20:27
harlowjagood description there20:28
*** otherwiseguy has quit IRC20:28
*** MaxV has joined #openstack-meeting20:28
*** vipul is now known as vipul-away20:28
iv_mnext step is to allow task executor to run task asynchronously20:29
harlowja:)20:29
iv_mthat's what worker-based engine will need to do, for example20:29
*** colinmcnamara has joined #openstack-meeting20:29
*** colinmcn_ has joined #openstack-meeting20:29
harlowjaright20:30
iv_mso, the executor should return future that will in order return task result (or task reversion result) and some metadata20:30
harlowjacool20:30
harlowjawhat are u thinking about for the metadata?20:30
iv_mwell, in my experimental code it's task instance itself and what happend (was it reverted or executed)20:31
*** krtaylor has quit IRC20:32
*** zaneb has quit IRC20:32
iv_msomething like that so that engine does not have to have some sophisitacted data structure to find out where result returned by future belongs20:32
harlowjak20:32
*** reed has joined #openstack-meeting20:32
harlowjain experimental code, i guess listeners that are watching the state transitions still operate as before20:33
iv_mof course20:33
harlowjaneats20:34
iv_mthen, the plan is to create new graph action that will be able to schedule all the tasks with task executor and wait on returned futures while tasks are executed (maybe in parallel), using no more than one thread20:34
*** herndon has quit IRC20:35
akarpinska1I'm not shure it is possible to do in one thread20:35
akarpinska1because of feature implementation20:36
iv_mhey, i almost already done that20:36
akarpinska1do you implement your own feature?20:36
iv_mno, i use concurrent.futures.Future in my code20:37
akarpinska1but it waits until result is set20:37
harlowjainteresting20:37
iv_mu can wait for several futures at once with concurrent.futures.wait()20:38
iv_mwich makes everything really simple20:39
*** Ravikumar_hp has quit IRC20:39
harlowjasomething though blocks right? so for something to block u need something to block on (another thread?) - so that means 2 threads?20:39
harlowjaanyways, techinical detail, lol20:39
*** Ravikumar_hp has joined #openstack-meeting20:40
harlowja*this might of been what akarpinska1 was asking (not sure)20:40
*** dcramer_ has quit IRC20:40
*** vuil has quit IRC20:40
*** malini is now known as malini_afk20:41
harlowjaoh ya, other thing i was going to bring up20:41
harlowja#link https://etherpad.openstack.org/p/async-taskflow-tasks20:41
harlowjai think with iv_m  work here, #3 becomes more natural (although #0 still seems like it would also be fine)20:42
harlowjaso i can try out #3 when iv_m executor stuff in place20:42
harlowjasee how that goes20:42
iv_myup20:42
harlowjamight not be so bad, not so sure yet20:42
harlowjathat will make mistral folks use-case work better (maybe?)20:43
harlowjawhat else, oh ya, nearly forgot, changbl i think wasn't able to make it today, but he said offline that he is working on the zookeeper stuff (ongoing)20:44
harlowjaand getting closer!20:44
harlowjawill keep all of us posted20:44
harlowja*changbl will20:44
*** dcramer_ has joined #openstack-meeting20:44
*** otherwiseguy has joined #openstack-meeting20:44
*** mdomsch has joined #openstack-meeting20:44
iv_mgreat20:45
harlowja:)20:45
* harlowja needs to track down some more of the cinder folks doing taskflow integration, see where that is at20:46
*** cdub has joined #openstack-meeting20:46
harlowja#action harlowja see if can track them any of those folks down (to see if they are doing ok)20:46
harlowjai know they exist somewhere :-P20:46
iv_m)20:47
*** rakhmerov has joined #openstack-meeting20:47
harlowjawill see if i can fire some folks an email that might know20:47
*** doug_shelley66 has quit IRC20:48
harlowjaanything else people want to talk about, i think i'm all good20:48
*** dougshelley66 has joined #openstack-meeting20:48
*** vipul-away is now known as vipul20:49
harlowjagoiinnng once20:49
*** jcooley_ has quit IRC20:49
harlowjagoinnng twice20:49
harlowjagoing thriceeee20:50
harlowjasold to iv_m for 500$20:50
harlowjaha20:50
iv_mnp, but what did i get?20:50
harlowjaha20:50
harlowjasecret prize20:50
harlowjaanyways #openstack-state-management for any further questions, issues, problems, q/a, chit-chat, prizes...20:51
harlowjauntil next time folks, and thanks for coming for those that did :)20:51
k4n0thanks guys20:52
harlowjanp :)20:52
harlowja#endmeeting20:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:52
openstackMeeting ended Thu Dec 12 20:52:22 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/state_management/2013/state_management.2013-12-12-20.00.html20:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/state_management/2013/state_management.2013-12-12-20.00.txt20:52
openstackLog:            http://eavesdrop.openstack.org/meetings/state_management/2013/state_management.2013-12-12-20.00.log.html20:52
*** k4n0 has left #openstack-meeting20:52
*** iv_m has left #openstack-meeting20:53
*** reed has quit IRC20:53
*** mspreitz has quit IRC20:53
*** kgriffs_afk is now known as kgriffs20:54
*** troytoman is now known as troytoman-away20:56
*** akarpinska1 has left #openstack-meeting20:57
*** mriedem has joined #openstack-meeting20:58
*** ijw has joined #openstack-meeting20:58
*** henrynash has joined #openstack-meeting20:58
*** melwitt has joined #openstack-meeting21:00
russellb#startmeeting nova21:00
openstackMeeting started Thu Dec 12 21:00:14 2013 UTC and is due to finish in 60 minutes.  The chair is russellb. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: nova)"21:00
openstackThe meeting name has been set to 'nova'21:00
russellbhello, everyone!21:00
mriedemhi21:00
n0anoo/21:00
alaskihi21:00
driptonhi21:00
melwitthi21:00
cyeohhi21:00
russellb#topic general21:00
mesteryo/21:01
*** openstack changes topic to "general (Meeting topic: nova)"21:01
*** yjiang5 has joined #openstack-meeting21:01
russellbonly one thing for this section today from me ... meeting time21:01
russellbi'm going to start a thread about starting to alternate the time to allow more people to attend21:01
russellbno need to get into the specific time too much now because the people it helps the most aren't here :)21:01
*** s0mik has joined #openstack-meeting21:01
*** hartsocks has joined #openstack-meeting21:01
dansmitho/21:01
russellbso we'll meet at this time every 2 weeks21:01
hartsocks\o21:01
russellbdetails TBD ...21:02
russellb#topic sub-teams21:02
russellbhartsocks: well hello!21:02
*** openstack changes topic to "sub-teams (Meeting topic: nova)"21:02
* n0ano scheduler21:02
* melwitt novaclient21:02
arosenhi21:02
lifelesso/21:02
hartsocksrussellb: sorry running late.21:02
* russellb expects he may have caught hartsocks off guard21:02
russellbn0ano: you can go :)21:03
n0anoright, make me go first :-)21:03
n0anotalked at the meeting about no-db and the forklift...21:03
russellbsome good scheduler forklift progress this week21:03
*** boris-42 has joined #openstack-meeting21:03
n0anothe no-db has about 2 patches left, once they are submitted (within about a week) it should all be under review...21:03
russellbis anyone committed to keeping the forklift repo in sync while it's in progress?21:04
russellbyou?  someone else?21:04
russellband are you looking at stackforge now?21:04
lifelesswe have the volunteers, I think we should submit the repo to gerrit asap21:04
n0anofor the forklift, I've created the base scheduler tree, we should be about ready to create a stackforge project, lifeless should know if any other administrivia is needed21:04
*** gyee has joined #openstack-meeting21:04
lifelessprobably need the client tree to, I sucked this week21:05
russellbok cool21:05
lifelessI will get it done today21:05
*** vuil has joined #openstack-meeting21:05
n0anolifeless, I created the bare bones client tree and added it to the config file21:05
russellbok, client is easier21:05
*** rwsu has quit IRC21:05
*** mspreitz has joined #openstack-meeting21:05
lifelessn0ano: oh cool, ok21:05
russellbi think it's still included in the repo n0ano just did21:05
lifelessso lets get infra on that21:05
*** reed has joined #openstack-meeting21:05
russellboh nice, you did that too?21:05
russellbis it just nova/scheduler/rpcapi.py ?21:05
n0anoI'm an animal, what can I say :-)21:06
russellband the associted test file21:06
lifelessplus setup.py/.cfg etc machinery?21:06
n0anorussellb, even less, just the top level text files (licensing and what not), the rest will be new files, should be created though the gerrit process21:06
*** Ravikumar_hp has quit IRC21:06
comstudo/21:06
russellbhmm, no21:07
*** Ravikumar_hp has joined #openstack-meeting21:07
russellbi think we need to keep the history of rpcapi.py21:07
russellbthat's the client code21:07
* beagles slinks in late21:07
*** shanewang has joined #openstack-meeting21:07
*** yassine has joined #openstack-meeting21:07
n0anohmm, is that file already in the server tree?  If not, I can add it to the client tree21:07
*** jasondotstar has quit IRC21:07
russellbyes, it's in the server tree now probably21:07
*** henrynash has quit IRC21:07
lifelessit shouldn't be though, should it?21:08
russellbbut it's the client code everything else uses to talk to the scheduler21:08
russellbi didn't catch that before, sorry21:08
russellbnot a huge deal if we just git rm it from the server tree21:08
n0anoremember, it's all scripted, NP - so you want to remove that file from the server tree and make it part of the client tree21:08
lifelessplease21:08
russellbyeah21:08
russellbthanks a bunch for doing this :)21:09
lifelessthe goal is two trees; one with the client, one the server both can run their own unit tests21:09
*** epim has joined #openstack-meeting21:09
n0anoNP, the config file changes stay the same, I'll let lifeless know when the trees are ready21:09
russellbi expect we'll have some work to do to get the tests running again21:09
russellbbut we're close to the right base to start with21:09
lifelessif they can't run unit tests we'll make all the jobs nonvoting so we can iterate21:09
russellbworks for me21:09
russellbso good progress on two major things in scheduler land21:10
russellbanything else for today?21:10
n0anothat's it for now21:10
russellbgreat thanks!21:10
russellbmelwitt: hi!21:10
russellbspeaking of clients, novaclient!21:10
melwitthi all, I have the novaclient report for this week:21:10
melwittopen bugs, 118 !fix released, 77 !fix committed21:10
melwitt20 new bugs21:10
melwitt0 high bugs21:10
melwitt31 patches are up, 7 WIP, everything been pretty active -- prompt reviews and approvals, lots of v3 api activity.21:10
comstudlet's have one21:10
russellbsounds like great progress all around21:11
russellbmore progress on bug triage i see, thanks a bunch21:11
russellbany major concerns?21:11
melwittno, I think things are going pretty well21:12
russellbso the 77 !fix committed number21:12
russellbdoes that mean there are 77 bug fixes that haven't been released?21:12
russellbor?21:12
russellbseems high since we did a release around the havana release21:12
melwittah, no. I wasn't sure how to represent "open" bugs. 77 is the number of bugs that are neither fix committed nor fix released21:12
russellbok21:13
russellbso we have 118 total open, 77 after you take out the ones with fixes committed?21:13
melwittright21:13
russellbgot it21:13
melwittI consider those like "fixed"21:13
russellbfixed but not released, yeah21:13
shanewangmelwitt: did you have any link to query "fix released", "fix committed"?21:13
russellbso 41 fixes not released then21:13
russellbsomething like that21:13
russellbbtw, timing of novaclient releases since i've been doing them has been roughly ... when someone asks for it21:14
russellbso if you have better ideas, let me know, heh21:14
*** dkranz is now known as dkranz_in_transi21:14
melwitthaha ok21:14
*** AlexF has joined #openstack-meeting21:14
russellbanything else?21:14
melwittI think that's it. I'll continue going through the bugs, try to trim all that down21:15
russellbthanks!21:15
russellbhartsocks: you're up21:15
hartsockscool21:15
hartsocksSo, we have 2 BP for Icehouse already approved and ready to go.21:15
russellbwoo21:15
hartsocksI've got one on my plate that I need to finish.21:15
russellbhow's the minesweeper21:16
hartsocksI'll have to solicit some help on that later today or tomorrow if someone's got time/interest.21:16
russellbwhat kind of help?21:16
*** Ravikumar_hp has quit IRC21:16
hartsockson that topic, I just need to figure out how best to work with the oslo component I want to tie in with.21:16
russellbok21:17
*** Ravikumar_hp has joined #openstack-meeting21:17
hartsocksthat's a bit of a can-o-worms so I'll just leave it.21:17
russellbk :)21:17
russellbhartsocks: see my minesweeper question?21:17
hartsocksWe have a small patch in flight related to CI stability…21:17
russellbOK, patch to nova?21:18
hartsocksI *could* call it out …21:18
russellbor something else?21:18
russellbyeah now is a good time to call out high priority things, especially like that21:18
*** drake__ has joined #openstack-meeting21:18
hartsocksugh. Taking too long for me to hunt up the link.21:18
*** drake__ has left #openstack-meeting21:18
russellbok, feel free to bring it to open discussion then21:18
russellbanything else you wanted to mention?21:18
hartsocksWe do have 7 high priority bugs. I spammed that out yesterday.21:18
*** dkranz_in_transi has quit IRC21:19
hartsocksthat's all for now.21:19
russellbyep, appreciate the reports21:19
russellbk, thanks!21:19
russellb#topic bugs21:19
*** openstack changes topic to "bugs (Meeting topic: nova)"21:19
russellbhow bad is the nova bug queue this week?21:19
russellblifeless: any bug topics?21:19
lifelesshi yes21:19
lifelessso I will have an email out later today21:19
russellblooks like there's been some triage progress in the last week21:19
lifelessabout what I want to do to the bug triage process21:19
russellbcool21:19
russellban do you think we need a bug day to play catchup?21:19
lifelessbug basically it has way to much double handling21:20
lifelessso it's super inefficient - it's boiling the ocean21:20
lifelesscan I run a high level replacement past the meeting?21:20
russellbsure21:20
*** stanlagun has left #openstack-meeting21:20
*** rakhmerov has quit IRC21:20
*** Ravikumar_hp has quit IRC21:20
*** vuil has quit IRC21:20
lifelessMy idea is that triage only  touches an untriaged bug once: we do everything we can do it and then either:21:21
lifelessA) leave it incomplete [pending user input]21:21
*** Ravikumar_hp has joined #openstack-meeting21:21
lifelessor B) leave it triaged [coarse priority set]21:21
lifelessor C) we bounce it to ask.openstack.org21:21
lifelessthe only time we touch it twice would be if it goes into A)21:21
mriedem(c) would be like usage help questions?21:21
lifelessyeah21:21
mriedemthat we mark as invalid and send them to the ML now21:22
*** oubiwan__ has joined #openstack-meeting21:22
russellbthe idea with the tagging was just that there are lots of people qualified to triage subsets of the bugs21:22
lifelessthe list? Ok sure21:22
mriedemso we have to repost it to ask.openstack.org or make the reporter do it?21:22
lifelessrussellb: so I've been poking around21:22
*** MaxV has quit IRC21:22
russellbnot sure that's been happening in reality21:22
lifelessrussellb: and I don't see at the level of 'assess importance' that we need deep plumbing in each hypervisor21:22
mriedemwhen i do triage i definitely tag stuff, but i don't know if they get love after that21:23
lifelesswe only get ~ 10 new bugs a day.21:23
lifelesslook ^ stats21:23
russellbonly 10 a day, heh21:23
*** MaxV has joined #openstack-meeting21:23
lifelessso - the goals:21:23
lifeless - ensure users don't get stuck in limbo - they either get told 'its a real bug' or21:23
lifelessits a usage question'21:24
lifeless - we create a pool of low hanging fruit21:24
lifeless - vendor teams have bugs routed to them21:24
*** IlyaE has quit IRC21:24
mriedemhmmm, determining if something is a real bug could be hard w/o an env to recreate on21:24
*** kmartin has joined #openstack-meeting21:25
lifelessthere's a bunch of bug management stuff we've been categorising as triage - like aging out bugs - that isn't triage - I want to build a separate process for that21:25
*** krtaylor has joined #openstack-meeting21:25
russellbok21:25
lifelessmriedem: so thats where you make a judgement call21:25
cyeohso I do see a reasonable steady stream of bugs tagged api but not triaged. If we say that people have to triage at the same time as tag and they're not able to, they might just get left in limbo21:25
*** IlyaE has joined #openstack-meeting21:25
*** bpokorny has joined #openstack-meeting21:25
russellbwell i'm happy to try whatever right now21:25
*** Ravikumar_hp has quit IRC21:25
russellbwhatever helps engage more people to get things touched21:25
*** Ravikumar_hp has joined #openstack-meeting21:26
lifelessok, so I'll have a draft of what I'd like to try up to the list today21:26
*** vuil has joined #openstack-meeting21:26
russellbok sounds good21:26
lifelesstldr;:21:26
*** jhenner has joined #openstack-meeting21:26
lifeless - much simpler /triage/ process and a group focused on making that really work21:26
mriedemqa team might have good input on this since they have to do this all the time for code they don't work on21:26
russellbk, will look out for the post21:26
lifeless - a separate maintenance process for aging out / reviewing idle-assigned etc.21:26
russellbanother bug thing i wanted to bring up was the gate affecting stuff21:27
russellbthere's been some ML posts on it the last couple days21:27
russellbalso if you look at https://bugs.launchpad.net/nova/+bugs, look at everything marked CRITICAL21:27
*** MaxV has quit IRC21:27
russellbif anyone has cycles, we could use some help on those things21:27
lifelessI did want to ask about this though:21:27
lifeless '21:27
lifelessIf the bug contains the solution, or a patch, set the bug status to Triaged '21:27
lifelessI just can't understand how that makes sense; it doesn't fit any definition of triage I've ever encountered21:28
mriedemwell it's either triaged or confirmed at that point by the reporter21:28
mriedemwhy they don't push the patch makes me wonder sometimes21:28
lifelessmore context21:28
*** colinmcn_ has quit IRC21:28
*** colinmcnamara has quit IRC21:28
*** jhenner has quit IRC21:29
lifelessthe 'BugTriage' page treats Triaged as 'has a patch'21:29
lifelessfor instance - 'We should review if the patch looks indeed like a patch, and if yes, set the bug status to Triaged to show that it comes with a likely solution, ready to be implemented. '21:29
lifelessI just wanted to see if the nova folk share that understanding, or if it's a surprise :)21:29
mriedempersonally i don't have the bug triage wiki page memorized21:30
lifelessThe outside-openstack understanding of triaged is 'the urgency is known'21:30
lifelessI want to make sure I'm solving the actual problem21:30
* russellb hasn't really used triaged much, just confirmed21:30
*** sarob_ has joined #openstack-meeting21:30
devanandaso, my interpretation -- which doesn't match the wording well, but makes more sense to me -- has been confirmed = "yep, it's a bug!" vs. triaged = "AND here's a reasonable proposal on how to solve it"21:30
mriedemyeah, i don't use triaged much21:30
*** jdurgin has quit IRC21:30
russellbdevananda: +121:30
lifelessdevananda: thats not what triaged means in LP though21:30
lifelessdevananda: it means 'importance has been assessed'21:30
*** banix has quit IRC21:31
lifelessbasically the standard emergency ward definition21:31
russellbheh just don't think we've used it that way21:31
*** SergeyLukjanov is now known as _SergeyLukjanov21:31
lifelessok, so we may end up ratholing around that a little on the list. Thanks.21:31
*** lbragstad has quit IRC21:31
*** mrda has joined #openstack-meeting21:31
russellbalright, let's move on21:31
russellb#topic blueprints21:31
*** openstack changes topic to "blueprints (Meeting topic: nova)"21:31
devanandalifeless: that is redundant. [confirmed, no pri] vs [confirmed, has a priority] is sufficient triage. there is no need for a ternary state21:32
russellbgeneral announcement, if you have blueprints targeted to icehouse-2, please check their status and make sure they are approved21:32
shanewanglifeless: is triaged "confirmed by the supervisor"?21:32
russellbif not, they may be waiting on your feedback21:32
russellbI'm going to move everything not approved to icehouse-3 a week from today21:32
russellbmore details here:21:32
russellb#link http://lists.openstack.org/pipermail/openstack-dev/2013-December/021820.html21:32
russellbone blueprint i wanted to bring up is the GCE API21:33
russellb#link http://lists.openstack.org/pipermail/openstack-dev/2013-December/021469.html21:33
russellbI've recommended that they work on getting it into its own stackforge project for now, because i'm sensing very little support for this21:33
*** sarob has quit IRC21:33
russellband in that message linked above, i'm asking for anyone that wants this in nova to speak up21:34
russellbi think we as a team need to be on board with maintaining this, at a minimum from a review perspective21:34
russellbpoint of bringing it up today was to raise awareness of the fact that i want that feedback21:34
*** sarob_ has quit IRC21:34
russellbanyone have thoughts on that right now?21:35
mriedem+1 to stackforge, i think that's going to be the route for most new stuff like new drivers21:35
cyeohas I sort of mentioned in that thread, I don't think they've come up with a good reason for it needing to be in the Nova tree.21:35
mriedemthen you get 3rd party CI going and prove it and incubate before getting promoted21:35
russellbi wouldn't say that as a blanket statement to all new things21:35
*** oubiwan__ is now known as oubiwann-lambda21:35
russellbmriedem: oh, right21:35
lifelessdevananda: right, this is an open bug on LP21:35
cyeohsince they're saying it can just sit on top of the nova rest api21:35
russellbcyeoh: they even agreed that the other way was better21:35
russellbso not making a good case :)21:35
*** nati_ueno has quit IRC21:36
*** IlyaE has quit IRC21:36
mriedemrussellb: stackforge for anything new that requires 3rd party CI, maybe that makes more sense21:36
russellbso regardless of whether it ends up in nova, stackforge + CI is a good start21:36
russellbmriedem: +121:36
russellbbut right now i'm not sensing much support of it ending up in nova in the near term21:36
russellbany other blueprints folks want to discuss today?21:36
russellb#link https://launchpad.net/nova/+milestone/icehouse-221:36
russellb92 blueprints targeted to icehouse-2 right now :)21:37
lifelessshanewang: yes, bug supervisor == triager21:37
*** spzala has quit IRC21:37
russellbonly 4 that reviewers have committed to21:37
russellbthe core sponsorship thing doesn't really seem to be taking off21:37
russellbi still like the idea though21:37
russellbmaybe it'll just take longer for us to get used to it21:38
dansmithhas anyone other than john and I signed up for one?21:38
alaskiI have a couple21:38
dansmithmaybe we just need to be a little more vocal with the core folks21:38
dansmithalaski: ah, right21:38
russellbi have a couple21:39
devanandarussellb: i'd like to bring up the deprecate-baremetal BP briefly21:39
russellbsome that i have signed up for have just 1 though21:39
russellbdevananda: sure21:39
devanandarussellb: with the BP-needs-a-reviewer-signup thing, we don't have one yet :)21:39
russellbdo you expect the driver to be ready for merging in icehouse-2?21:39
devanandarussellb: also, I'd like some guidance on how ya'll would like the patch broken up. adding a new driver is, well, a lot of code to review at once21:40
devanandarussellb: it should be functional by then21:40
russellbnot sure how to break it up really ...21:40
russellbunless you did it by features21:40
devanandarussellb: i'm not sure whether it'll be polished and all by end of jan, though21:40
mriedemnew driver?21:40
devanandaironic21:41
russellbpolished by end of jan puts it in icehouse-321:41
devanandasupplanting baremetal driver21:41
russellbshould we retarget?21:41
devanandarussellb: deadline is jan22, no?21:41
russellbfor merging21:41
russellbyeah21:41
russellbhopefully ready for review a little sooner21:41
mriedemso should a nova ironic driver start in stackforge to get CI going first?21:41
russellbwe can leave it for now21:41
russellbi don't want to commit to reviewing for icehouse-2 if you're telling me it'll be ready for review the day before :)21:41
devanandaheh, fair21:42
russellbbased on that timeline, i'd sponsor for icehouse-321:42
devanandaso it may be ready for some reviews now -- it's already ~ 700 LOC21:42
devanandaand not feature complete yet ...21:42
russellbmriedem: good question on CI21:42
mriedemthis also reminds me, we don't have a core set of required APIs for virt drivers...21:42
devanandathus my question about how / whether to break it up21:43
russellbdevananda: how does CI look for this driver?21:43
mriedemso if you stagger in the reviews for a new virt driver and they don't all make core for the release, do you drop the entire driver?21:43
russellbmriedem: yes.  we need one.21:43
*** sarob has joined #openstack-meeting21:43
devanandarussellb: current CI for this is "none" because Ironic is still workin gout the deployment API21:43
* russellb nods21:43
russellbso ... we have this requirement for the release, that CI exists or the driver gets pulled21:44
mriedemhmm, so then how does that fit into the i2 driver deprecation plan?21:44
devanandarussellb: unless some mirantis folks really work quickly, I don't think we'l lhave the level of CI I want until after icehouse release21:44
*** jdurgin has joined #openstack-meeting21:44
devanandaunfortunately21:44
devananda(or someone else steps up to do it)21:44
russellbOK, that could realistically mean the driver slips to Jeckyll21:44
dansmithmriedem: this has been coming for a while, and replaces the baremetal driver, which we're eager to drop21:44
mriedemdansmith: yeah, but it still requires CI to live right?21:44
mriedem3rd party CI if community infra doesn't host that?21:44
*** rnirmal has quit IRC21:45
*** jecarey has quit IRC21:45
devanandamriedem: this would mean an Icehouse release without either baremetal or ironic support .....?21:45
*** cdub has quit IRC21:45
dansmithmriedem: I think it will get a little slack on the deadline, I'm guessing21:45
mriedemso are we talking double standards here?21:45
*** SergeyLukjanov has joined #openstack-meeting21:45
dansmithmriedem: we can't drop both21:45
russellbargh, i don't like the idea of not having either21:45
mriedemslippery slopes...21:45
russellbmaybe we grant ironic an exception given the awkward timing for the transition21:45
dansmithI think the assumption is that ironic/BM is a key feature for openstack,21:45
dansmithand we're in a sticky situation right now so it has to get a little bit of a pass for the time being21:46
devanandamriedem, russellb -- if you consider tripleo's testing as "third party ci" then maybe that is sufficient21:46
russellbdevananda: yes, i do21:46
devanandathat's all based on nova-baremetal today21:46
russellbi think we would consider that significant enough CI progress to not drop it21:46
devanandagreat21:46
mriedemok, i guess in general i'm interested in where the vmware, xenapi, docker, and hyperv teams are with CI21:46
mriedemmaybe that's for open discussion21:46
devanandaAIUI, lifeless plans to switch tripleo to use the ironic driver as soon as it works (where works == does everything baremetal does for tripleo)21:47
russellbvmware has minesweeper that they're actively building up21:47
lifelessyeah21:47
dansmithrussellb: until it's reporting on each nova patch, I don't think the tripleo testing should "count" but I also think we have to consider this an exception :)21:47
russellbxenapi has some good progress integrating into upstream CI21:47
russellbdocker and hyperv, haven't actually seen anything yet21:47
lifelessalso we hope to bring up tempest tests against ironic clouds asap21:47
devanandarussellb: so the ironic driver will get third-party CI at that point in time21:47
lifelessseparate to tripleo switching21:47
russellbdansmith: fair21:47
mriedemrussellb: but xenapi is using smokestack right?21:47
russellbmriedem: right now, but they're working on changing that21:47
russellbintegrating into infra21:48
lifelesswhen the redhat region comes in, we should be able to get 'check' status tests infra - not thirdparty.21:48
mriedemok, because smokestack doesn't run tempest afaik21:48
*** sarob has quit IRC21:48
russellbmriedem: yep21:48
mriedemand vmware has to run on all patches per the requirements21:48
russellbyes21:48
*** marun has quit IRC21:48
*** sarob has joined #openstack-meeting21:48
mriedems/vmware/vmware, hyperv, docker, xenapi, everything/21:49
russellbyes yes21:49
russellb:)21:49
russellbany other blueprints?21:49
lifelessbaremetal-preserve-ephemeral21:49
lifelesswe have a sketch of all the bits up in gerrit21:49
lifelesswould love someone to cast an eye over the code and comment on general direction21:49
*** jdurgin has quit IRC21:50
russellb#link https://blueprints.launchpad.net/nova/+spec/baremetal-preserve-ephemeral21:50
lifelessmaybe someone has since I asked about this on IRC yesterday - if so great,a nd sorry for the repeated q ;)21:50
russellbi'll sponsor that21:50
russellbif it's pretty far along already21:50
*** jdob has quit IRC21:50
lifelessyeah21:50
russellbassuming it's in the right direction, not a whole bunch left to do?21:50
lifelesswe need comment on the driver API change21:51
lifelesswe need to know if the HTTP API change is ok as is or needs to be a new extension21:51
*** sarob has quit IRC21:51
russellbfor v2, without even looking, probably a new extension21:51
russellballows you to discover that the feature is present21:51
lifelessnot a change to the rebuild extension?21:52
russellbwell, the code could be a change to rebuild, where it checks to see if this other extension is loaded21:52
russellbsearch for extended-services (i think)21:52
cyeohlifeless: for v2 its normally a dummy extension (no content)21:52
russellbfor an example of where the "extension" is just an empty dummy thing21:52
russellband then some other code does something like ... if extension_is_loaded('my-thing'): support_my_thing()21:52
*** jdurgin has joined #openstack-meeting21:53
lifelessI will look and see what we've got, but if one of you could comment directly on the review that would be awesomer21:53
russellbk21:53
cyeohlifeless: do you have a link to which review?21:53
russellbhttps://review.openstack.org/#/q/topic:bp/baremetal-preserve-ephemeral,n,z21:54
russellbis the series ...21:54
cyeohthx!21:54
lifelesshttps://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/baremetal-preserve-ephemeral,n,z21:54
russellbi can't find the API patch in there though21:54
lifelesshuh, it was21:54
russellbanyway21:55
russellbwe'll sort it :)21:55
*** sushils has quit IRC21:55
russellb#topic open discussion21:55
*** openstack changes topic to "open discussion (Meeting topic: nova)"21:55
russellb5 minutes!21:55
*** MaxV has joined #openstack-meeting21:55
lifelessI will find it and link in -nova21:55
russellbsounds good21:55
cyeohjust a reminder if people could remember to look at python-novaclient patches too? (And I'm not just saying that because I have a bunch of patches with one +2 sitting in there :-)21:55
mroddeni (and some others at IBM) are sponsoring a senior project team a university, and I was looking for idea of blueprints in OpenStack that would be good to have them work on21:56
mroddenat a university even...21:56
russellbmrodden: can it be ... fix a bunch of bugs?  :-p21:56
russellbbut that's cool21:56
mroddenthat will probably be the first phase yes21:56
mrodden:)21:56
mriedemi suggested infra/qa stuff21:56
mriedembut that's a bit dirty probably21:56
mroddenwas looking for something that would be achievable as i don't know how familiar with python or openstack they will be21:57
mriedemunless it's some neato gadget for helping automate something with bugs21:57
russellbcyeoh: indeed ... also, pro tip ... set up a "my review queue" bookmark... example: https://review.openstack.org/#/q/project:openstack/nova+OR+project:openstack/python-novaclient,n,z21:57
russellbbut with all the projects and branches you care to review21:57
*** mlavalle has joined #openstack-meeting21:57
*** dkranz_in_transi has joined #openstack-meeting21:57
russellbmriedem: thierry just posted an infra project idea to the -infra list21:58
*** dkranz_in_transi is now known as dkranz21:58
lifelessrussellb: cyeoh: Id33d5d4107f89814842a3f0b7f33690dd7e3aadc21:58
mriedemmrodden: have the interns automate the release process :)21:58
lifelessbah, echannel21:58
mriedemno more MP branch21:58
russellbmriedem: the idea was infra-izing the schedule of #openstack-meeting and #openstack-meeting-alt21:58
russellbshould check it out21:58
mriedemmrodden: ^ :)21:59
* mrodden shuffles through -infra mail21:59
russellbmriedem: mrodden http://lists.openstack.org/pipermail/openstack-infra/2013-December/000517.html21:59
mroddensweet thx21:59
*** neelashah has quit IRC21:59
mriedemwith more projects moving to adjust for all timezones that could help a lot21:59
*** AlexF has quit IRC22:00
russellbwe're out of time, off to #openstack-nova if anyone still wants to chat22:00
russellbthanks everyone!22:00
russellb#endmeeting22:00
*** lbragstad has joined #openstack-meeting22:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
*** mriedem has left #openstack-meeting22:00
openstackMeeting ended Thu Dec 12 22:00:23 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-12-12-21.00.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-12-12-21.00.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-12-12-21.00.log.html22:00
*** sandy__ has quit IRC22:00
*** hartsocks has left #openstack-meeting22:00
*** neelashah has joined #openstack-meeting22:00
*** vladikr has left #openstack-meeting22:01
mtreinish#startmeeting QA22:02
openstackMeeting started Thu Dec 12 22:02:35 2013 UTC and is due to finish in 60 minutes.  The chair is mtreinish. Information about MeetBot at http://wiki.debian.org/MeetBot.22:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:02
*** openstack changes topic to " (Meeting topic: QA)"22:02
openstackThe meeting name has been set to 'qa'22:02
*** shanewang has quit IRC22:02
SergeyLukjanovo/22:02
mtreinishhi who's here today at our new time?22:02
*** changbl has quit IRC22:03
*** ryanpetrello has quit IRC22:03
dkranzo/22:03
maurosr\o22:03
masayukighi22:03
mlavalleI am22:03
giulivohi22:03
*** AlexF has joined #openstack-meeting22:03
rahmuo/ first time22:03
cyeohhi!22:03
giulivocyeoh !! :)22:03
cyeohfirst time for me too :-)22:03
sdagueoh right -522:03
mtreinishtoday's agenda: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting22:03
sdagueI really thought this was another hour :)22:03
cyeohguitarzan: :-)22:03
mtreinishsdague: yeah I was thrown too I assumed the same thing :)(22:03
cyeohits kind of nice having it straight after the Nova meeting22:04
sdagueyeh22:04
mtreinishlet's get started then22:04
mtreinish#topic Blueprints22:04
*** openstack changes topic to "Blueprints (Meeting topic: QA)"22:04
*** dougshelley66 has quit IRC22:04
sdagueso giulivo has done an awesome job on clean up here22:04
mtreinishgiulivo: since you're taking the charge of blueprint clean up is there anything to report?22:04
*** ken1ohmichi_ has joined #openstack-meeting22:05
giulivosure so firstly, please not I sent you an email with comments about a few bp22:05
*** julim_ has joined #openstack-meeting22:05
*** s0mik has quit IRC22:05
giulivo*note22:05
giulivounless you disagree those will be closed/approved accordingly to the comments in the email22:05
*** malini_afk has quit IRC22:05
giulivoif you disagree, please reply22:05
sdaguegiulivo: sounds great22:05
*** mdomsch has quit IRC22:06
sdaguegiulivo: there are also a ton of "new" blueprints at the bottom22:06
sdagueyou going to purge those as well?22:06
mlavallegiulivo: is there a deadline to reply to the email?22:06
*** DrBacchus has quit IRC22:06
giulivowell this was a topic I'd wanted to discuss22:06
sdagueI think anything in new & unknown state should just be marked invalid22:06
*** AlexF has quit IRC22:07
giulivosome are basically asking for more tests to cover one or another functionality, what shall we do with these? ideas?22:07
giulivoI'd close these too22:07
*** julim has quit IRC22:07
*** markmcclain has quit IRC22:07
mtreinishgiulivo: so basically how do we track new tests?22:07
mtreinishor new test development22:07
sdaguegiulivo: so if people are actually targeting them to milestones, I think we can leave them22:08
dkranzor new anything22:08
giulivosome instead are asking for new tests to cover components we don't have the services for and I'd actually approve these22:08
*** topol has quit IRC22:08
*** malini_afk has joined #openstack-meeting22:08
giulivomtreinish, indeed that was my point of concern, I think the easiest way for that is just a wiki page, maybe organized by component22:08
*** malini_afk is now known as malini22:08
mtreinishcyeoh: well you said a google doc spreadsheet works well for this right?22:08
giulivoI can't think of anything else, but I'm obviously open to input22:09
*** AlanClark has quit IRC22:09
cyeohyea a spreadsheet works really well for api tests22:09
*** s0mik has joined #openstack-meeting22:09
sdagueI guess I'd take a step back22:09
cyeohif we really want to we can have a blueprint point to the appropriate spreadsheet. But a bp is in general a really cumbersome way of tracking progress for that sort of thing22:09
giulivobut wouldn't that force people to have a google account? what would be the benefits compared to the wiki?22:09
*** melwitt has left #openstack-meeting22:09
sdaguebasically: what is a blueprint useful for22:09
dkranzsdague: Avoiding duplication22:10
sdagueit's useful if a person is committing to deliver a thing by a milestone so we can ensure it gets review eyeballs22:10
sdaguedkranz: sure, but that again needs both an owner and a milestone22:10
dkranzsdague: Yes.22:10
sdagueand regularly updated status on it22:10
dkranzIf we simply insisted that new blueprints had an owner and milestone it would to a long way22:11
dkranzgo22:11
*** pdmars has quit IRC22:11
sdagueand the reason we go to the effort of that is to ensure that we prioritize reviews for it22:11
*** boris-42 has quit IRC22:11
sdagueand if you have a blueprint, I also expect you to come to this meeting, or provide regular updates22:12
sdaguein some other way22:12
sdagueso I think doing the giant purge that giulivo is doing is great22:12
*** sandy__ has joined #openstack-meeting22:12
giulivosdague, I totally agree with that, but I still wouldn't apply this to "we need tests for cinder backup" type of blueprints22:12
*** sriramhere has quit IRC22:12
sdaguegiulivo: agreed22:13
sdagueespecially as there are already at least 3 bugs I duped together on that today :)22:13
*** banix has joined #openstack-meeting22:13
*** jasondotstar has joined #openstack-meeting22:13
sdagueok, giulivo I think you can probably triage out 75% of the blueprints with the feedback you gathered so far right?22:14
giulivoyes22:14
sdaguethen maybe next week we cycle again on what's left22:14
sdagueto handle any sticky issues around them22:14
giulivobut one thing, probably not on topic, remains open and that is how we track the actual tests people want to add22:14
cyeohmaybe we should also write it down in a wiki what sort of things we want blueprints for, and what we don't (and how people should handle it instead)?22:14
sdaguegiulivo: can we circle to that at the end?22:14
giulivosdague, indeed not on topic, agree on that22:15
sdaguecyeoh: so, I'm actually becoming more a fan that we should do that in the tempest docs tree22:15
mtreinishsdague: it is the last topic on the agenda :)22:15
*** vkozhukalov has quit IRC22:15
sdaguemtreinish: great :)22:15
sdagueok22:15
cyeohsdague: yep, that'd be fine with me22:15
sdague#action giulivo to do the great blueprint purge22:15
sdagueand there was much rejoicing!22:15
mtreinishok is there anything else that needs to be discussed about blueprints?22:16
*** lblanchard has quit IRC22:16
mtreinishotherwise let's move on to the next topic22:16
giulivomlavalle, one thing22:16
*** jasondotstar has quit IRC22:16
giulivoI noticed a blueprint where we suggest to have tests for different network topologies in neutron22:16
mlavallegiulivo: listening...22:16
giulivoI wonder if that is at all feasible with our infra?22:17
*** rakhmerov has joined #openstack-meeting22:17
*** jasondotstar has joined #openstack-meeting22:17
giulivohttps://blueprints.launchpad.net/tempest/+spec/quantum-basic-api22:17
*** jasondotstar has quit IRC22:17
mlavalleI think it is…. the question is to prioritize that development with thereat of things I am doing for Neutron22:17
sdaguegiulivo: I think we should gather more details on that, it's really more of an openstack-ci item22:17
mlavallewe can talk after the meeting22:18
mtreinishmlavalle: yeah I think right now there are other priorities for neutron testing22:18
giulivook for me22:18
mtreinishwhich is a good segway into the next topic22:18
mtreinish#topic Neutron testing22:18
*** openstack changes topic to "Neutron testing (Meeting topic: QA)"22:18
mtreinishmlavalle: you're up22:18
mlavalleso in the api testing fron I didi 3 things this week22:19
*** samcdona has quit IRC22:19
mlavallenumber 1 I created a wiki page with a How To for API tests development for Neutron https://wiki.openstack.org/wiki/Neutron/TempestAPITests22:19
mlavallenumber 2 I sent a message to the ML recruting developers and pointing to the wiki page22:20
mlavallenumber 3 I kept adding to the gap analysis in https://etherpad.openstack.org/p/icehouse-summit-qa-neutron22:20
mlavalleat this point I have completed L2, L3, extensions management and provider networks22:21
mlavalleI will keep going through the API spec and hope to be finished by next week22:21
*** rakhmerov has quit IRC22:21
mlavalleat that point I will just start developing tests22:21
mlavallefrom the list22:22
*** dprince has quit IRC22:22
mtreinishmlavalle: ok as we were talking about a min. ago it might be useful to put that list into a spreadsheet somewhere22:22
mtreinishthat seems to work really well for splitting up api tests22:22
mlavallesure…… is that a Google spreadsheet?22:23
mtreinishespecially because it's getting kind of length22:23
anteayalet's also acknowledge that EmilienM's patch merged and neutron grenade tests now run, though they don't yet test anything22:23
mtreinishmlavalle: sure I guess, I don't think we have openstack infra cloud spredsheet22:23
cyeohmlavalle: yea we've used a google spreadsheet in the past, but anything really like that would be fine22:24
*** eharney has quit IRC22:24
cyeohthis is an example: https://docs.google.com/spreadsheet/ccc?key=0AmYuZ6T4IJETdEVNTWlYVUVOWURmOERSZ0VGc1BBQWc#gid=022:24
mlavallecool…. I'll move it to a spreasheet22:24
cyeohit allows for really fine grained self allocation of work22:24
mlavalleany other questions / observations on this regard?22:25
sdagueanteaya: yep, thankful for EmilienM's work there22:25
sdaguewhat about the SSH bug? Anyone have any news on that22:26
anteayawe need some devs coming forward to write some of those tests on the list22:26
*** troytoman-away is now known as troytoman22:26
anteayaso far, no volunteers22:26
anteayaso if any happen by22:26
anteayapoint them to -neutron and to mlavalle and myself22:26
anteayathey don't need to commit much22:26
anteayaany help appreciated22:26
anteayasalv-orlando just came online22:27
anteayaand has 2 hours to dig into it22:27
anteayaI will give him his time and get a report from him before he goes offline22:27
anteayahopefully to hand the baton to someone else22:27
anteayamy problem is that there seem to be many error messages captured by that logstash fingerprint22:27
anteayaso in my work I am having a hard time22:28
anteayabut my logstash foo is weak22:28
anteayathat is all I have on the ssh bug22:28
sdagueanteaya: thanks22:28
mtreinishok is there anything else to discuss on the neutron testing front?22:28
mtreinishok then let's move on22:29
mtreinish#topic Bug status22:29
*** openstack changes topic to "Bug status (Meeting topic: QA)"22:29
mtreinishso adalbas said he couldn't make it today22:30
sdagueso, we started the day at 276 ?22:30
mtreinishbut he wanted to thank everyone who contributed to the bug triage day today (or yesterday for some people :)22:30
*** thomasem has quit IRC22:30
mtreinishsdague: he put some notes up here: https://etherpad.openstack.org/p/tempest-bug-triage22:30
mtreinish#link https://etherpad.openstack.org/p/tempest-bug-triage22:30
*** thomasem has joined #openstack-meeting22:31
sdaguehttp://status.openstack.org/bugday/tempest.html - cron was broken earlier in the day, so it doesn't have full progress22:31
sdaguebut I just got us to 9722:31
sdaguelast check22:31
* sdague still triaging 22:31
mtreinishwow that's a big drop22:31
sdagueso thanks much to everyone22:31
*** thomasem has quit IRC22:31
sdaguehuge amount of work there, and it helps in getting patterns out of it22:31
sdaguelike the fact that there are a ton of nova state transition bugs that get filed in piecemeal22:32
sdaguewhich makes me think we actually need a new tempest test(s) that just do large_ops style run the state engine and try to break nova22:32
*** herndon has joined #openstack-meeting22:33
mtreinishsdague: something like the stress tests with a fake virt driver?22:33
mtreinishsdague: we were talking about something like that in HK22:33
*** denis_makogon has quit IRC22:33
*** noslzzp has quit IRC22:33
sdaguemtreinish: yeh, that would probably be a starting point22:33
sdaguehonestly I don't know if these are nova-compute bugs, or virt layer bugs with libvirt22:34
giulivoI would actually +1 the idea of using fake drivers for the api/gate tests and keep the real drivers for the periodic jobs22:34
sdaguegiulivo: I think we need real drivers in the gate22:34
mtreinishyeah if they're libvirt bugs we won't catch them with the fake driver22:34
giulivobut at gate we're not testing libvirt22:34
giulivonor lvm22:34
dkranzAnd we need to ssh22:34
sdaguegiulivo: ?? we are testing those things today22:35
dkranzWe need the gate jobs to be "real"22:35
sdaguedkranz: so this class of bugs doesn't need ssh22:35
sdagueright, agreed, I think that's a distraction22:35
sdagueI'm not trying to remove anything22:35
dkranzsdague: I was referring to the comment about gate jobs22:35
sdagueyep22:35
mtreinishsdague: well I can push out a new jjb job for running stress with a fake virt driver for like 20min22:36
giulivoheh okay I see I'm a minority here, will try to bring it up again differently not during the meeting :)22:36
sdaguestaying on topic-ish, I think nova state bugs are huge class of issues today, and we should try to figure out how to make them more frequent22:36
mtreinishthat should be straightforward22:36
mtreinishwe can do it nonvoting to see what it turns up22:36
sdaguemtreinish: actually, I think we need to think through this further22:36
ken1ohmichi_one question, can we get libvirt log on the gate?22:36
giulivobut the thing is I don't think at gating we should actually be testing if libvirt behaves correctly, but if the api behaves correctly22:36
sdaguebecause I actually expect this might be very surgical22:36
sdagueken1ohmichi_: you know where it's logging to?22:37
giulivolibvirt is a subset of the nova drivers and , maybe just because it is the most common , we pick it for the "real" periodic jobs22:37
sdaguegiulivo: I disagree :)22:37
ken1ohmichi_sdaue: log files under /var/log/libvirt/22:37
mtreinishgiulivo: how about we save that discussion for after the meeting22:37
sdagueken1ohmichi_: we could definitely add it22:37
ken1ohmichi_sdague: thanks, will check the way.22:38
sdagueken1ohmichi_: get with me in -qa after the meeting, and I'll give yuo the pointers as to where to do that22:38
*** krtaylor has quit IRC22:38
ken1ohmichi_sdague: great, will catch you:-)22:38
maurosrone more thing related to the triage, I saw sdague and dkranz talking about it all day, so should we have guidelines to bug report? cause those tracebacks don't really help us, people are just trying to use bugs in tempest to rechecks22:38
sdaguemaurosr: yes, definitely22:39
mtreinishmaurosr: yeah we need better triage guidelines22:39
mtreinishI think that is something adalbas was planning to work on moving forward22:39
*** neelashah has quit IRC22:39
sdaguedo we want to do that now? or discuss in a review? I was going to propose something into the docs tree about triage and good bugs22:39
dkranzmtreinish: My patch to send non-whitelisted errors to the log on failure will help22:40
mtreinishsdague: yeah I think doing it in a review would be fine22:40
dkranzmtreinish: It will then be easy to get the error from the log and not just the backtrace, if there is one22:40
mtreinishdkranz: the d-g one?22:40
dkranzmtreinish: Yes, but I don't know how to write shell script so it is not working22:40
mtreinishdkranz: ok I'll take a look after the meeting22:41
anteaya will you post you "good bugs guidelines" to the ml? I need to read them22:41
*** neelashah has joined #openstack-meeting22:41
anteayaor a link to the ml22:41
*** sushils has joined #openstack-meeting22:41
*** troytoman is now known as troytoman-away22:41
dkranzmtreinish: Help appreciated since I didn't understand Clark's comment22:41
sdaguedkranz: where's the review?22:41
*** herndon has quit IRC22:41
clarkbdkranz: I am happy to clarify :)22:41
mtreinishsdague: https://review.openstack.org/#/c/61850/22:41
sdagueanteaya: I think we'll handle it in a review in tempest doc tree22:41
dkranzclarkb: ok, I'll ping you later, thanks22:42
anteayasdague: I will look there22:42
*** banix has quit IRC22:42
mtreinishWe've still got 4 topics on the agenda, so is there anything else to discuss on bugs?22:42
dkranzsdague: https://review.openstack.org/#/c/61850/1/devstack-vm-gate.sh,unified22:42
mtreinishdkranz: a good segway :)22:43
mtreinish#topic Critical Reviews22:43
*** openstack changes topic to "Critical Reviews (Meeting topic: QA)"22:43
mtreinishso does anyone have any reviews that they would like to bring up22:43
mtreinishthat they think need attention22:43
*** neelashah has quit IRC22:44
dkranzmtreinish: I proposed we give some priority to heat and ceilo reviews22:44
sdagueactually, the review queue is pretty short right now22:44
sdagueit's pretty nice22:44
mtreinishdkranz: that's the next topic22:44
dkranzmtreinish: ok :)22:44
mtreinishI actually have 222:44
rahmuI have a question about this review: https://review.openstack.org/#/c/59759/22:44
mtreinish#link https://review.openstack.org/#/c/60866/22:44
rahmuwhich I guess could be added to the conf file cleanup bp22:44
mtreinishand22:44
mtreinish#link https://review.openstack.org/#/c/60578/22:45
sdaguerahmu: fire away22:45
rahmuhave we settled on a way to skip a test if a middleware (in the case of swift) is not installed?22:45
rahmuthere was some talks on the ml http://lists.openstack.org/pipermail/openstack-dev/2013-December/thread.html#2112122:45
rahmuand sdague said that a decorator on setupclass would be okay22:45
mtreinishrahmu: so I've been working on an approach with the extensions22:45
mtreinishrahmu: actually using decorators for something that depends on a config variable isn't going to work22:46
mtreinishyou need to do it inside the function22:46
mtreinishsomething I figured out a couple of days ago, I can give you hand with it after the meeting22:46
sdaguerahmu: so I'd say follow mtreinish's lead on how he's tackling the compute extensions22:47
rahmuokay thanks. I'll ping you later mtreinish22:47
mtreinishrahmu: ok cool22:47
sdaguemtreinish: +2 to both of your reviews22:47
mtreinishsdague: sweet thanks22:47
*** kevinconway has quit IRC22:48
sdaguehttps://review.openstack.org/#/c/61873/ - easy, and probably closes a bug :)22:48
mtreinishok, are there any other reviews anyone would like to bring up?22:48
mtreinish#link https://review.openstack.org/#/c/61873/22:48
mtreinishI'll +2 it, I just want to dig a little bit more in why it's there22:49
mtreinishbecause it's a little strange looking22:49
*** banix has joined #openstack-meeting22:49
giulivoand I don't understand why it would be failing anyway22:49
mtreinishok, lets move on22:49
cyeohmtreinish: possibly someone was thinking of checking server status22:49
dkranzmtreinish: I believe that line was recently added to *avoid* a race condition. I'll track it down.22:49
mtreinishcyeoh: yeah, I had a couple of ideas22:50
mtreinish#topic We should consider putting a fast-track on heat and ceilometer tests since they are integrated but lacking. (dkranz)22:50
*** openstack changes topic to "We should consider putting a fast-track on heat and ceilometer tests since they are integrated but lacking. (dkranz) (Meeting topic: QA)"22:50
dkranzcyeoh: That method now checks server status too I believe22:50
dkranzcyeoh: As of a recent change22:50
dkranzmtreinish: Any dissenters?22:50
cyeohdkranz, ah ok22:50
mtreinishdkranz: this lengthy topic is yours...22:50
*** MaxV has quit IRC22:50
mtreinishdkranz: no I'm fine22:50
mtreinishmy only concern is heat tests don't work and we have no way to verify them22:50
dkranzmtreinish: Some of them do work.22:51
sdagueyeh, we're basically wedged on getting infrastructure up for the slow tests22:51
dkranzmtreinish: I don't know what to do about the others22:51
sdagueI've been trying to review the other ones22:51
dkranzsdague: right22:51
*** radsy has joined #openstack-meeting22:51
*** ivasev has quit IRC22:51
sdaguebut I think that is fine as priorities go22:51
dkranzsdague: At this point I think it would do more good than harm to review things even if they don't run. Just for this special case.22:52
*** dcramer_ has quit IRC22:52
sdaguedkranz: it would be good to get folks working on those into the -qa channel as well on a regular basis22:52
anteayais there a rep from heat and from ceilometer in this meeting?22:52
dkranzYes22:52
sdagueso we can give more specific feedback22:52
dkranzstevebaker:  ^^^22:52
dkranzI think we can move on22:52
sdaguestevebaker has been great22:52
sdaguebut we need a ceilo person22:52
sdaguedkranz: can you take a todo to recruit one22:53
*** s0mik has quit IRC22:53
sdague?22:53
dkranzsdague: Sure22:53
mtreinish#action dkranz to recruit a ceilo core to be focal point on ceilo tempest tests22:53
mtreinishok let's move on22:53
sdaguethanks mtreinish22:53
mtreinish#topic Should we have more specialization on the Core review team? e.g. I am comfortable with the nova v3 patches, but no where on neutron. (dkranz)22:53
*** openstack changes topic to "Should we have more specialization on the Core review team? e.g. I am comfortable with the nova v3 patches, but no where on neutron. (dkranz) (Meeting topic: QA)"22:53
mtreinishdkranz: another lengthy topic22:54
anteayathe topics passed pep8 apparently22:54
dkranzmtreinish: This is really a question of whether we should all review everything scattershot or each take an area to hit first when reviewing22:54
dkranzDoesn't mean we are limited to one area22:55
dkranzBut I found reviewing the nova v3 changes got easier after I had done a bunch22:55
sdagueso I was looking at some neutron tests recently22:55
*** troytoman-away is now known as troytoman22:56
sdagueand I asked in the review for a link to the API docs for that section22:56
sdaguewhich was provided in a comment by lifeless22:56
sdagueand it was incredibly useful22:56
cyeohwell I'd agree there is definitely a big learning curve to be able to review changes for a new api/project22:56
mtreinishsdague: so your saying you want links to api specs in commit messages for new tests now?22:56
sdagueso I kind of wonder if we should ask that of at least API tests22:56
sdaguemtreinish: or in a comment22:56
giulivosdague, I would put these links in the aforementioned wiki page were we track api tests22:57
cyeohsdague: I think that's a good idea, though admittedly for the v3 api we don't really have a spec document yet22:57
sdaguegiulivo: or there22:57
sdaguecyeoh: yeh, so it's hard to validate API tests for an API with no docs :)22:57
sdagueso it seems like we've got a cart / horse problem there22:57
dkranzsdague: I asked for that fot nova v3 and was pointed to a diff with v2 which was what was needed.22:57
anteayaI think it is a reasonable request22:57
cyeohsdague: yea we only have v2/v3 diff document which is still buggy22:58
*** s0mik has joined #openstack-meeting22:58
sdaguecyeoh: well as dkranz said, it was useful22:58
*** neelashah has joined #openstack-meeting22:58
sdaguebut, yeh, some easier way of pointing reviewers to the spec would just expedite reviews22:58
anteayaexactly22:58
dkranzI think the issues is that when we started, there were a few projects/apis and we all knew all of them22:59
cyeohagreed.22:59
dkranzBut I have not been able to keep up with all the new apis and projects22:59
dkranzI was suggesting we divide and conquer for that22:59
*** henrynash has joined #openstack-meeting22:59
*** neelashah has quit IRC22:59
*** rudrarug_ has joined #openstack-meeting23:00
giulivodkranz, maybe we could put a couple of nicks next to each component telling people to add those as reviewers *if* in need ?23:00
dkranzBut not in a rigid way. Let me think a little more and propose something23:00
mtreinishdkranz: well, we're out of time23:00
dkranzNot right now23:00
sdaguedkranz: cool23:00
giulivo(I mean that in the tempest docs)23:00
sdagueyeh, I think we need to give up the room23:00
mtreinishgiulivo: sorry we couldn't get to your topic23:00
mtreinishwe'll save it for next week23:00
mtreinish#endmeeting23:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:00
openstackMeeting ended Thu Dec 12 23:00:37 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-12-12-22.02.html23:00
sdaguethanks everyone23:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-12-12-22.02.txt23:00
openstackLog:            http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-12-12-22.02.log.html23:00
*** rudrarug_ has quit IRC23:01
*** rudrarugge has quit IRC23:02
*** bpokorny has quit IRC23:03
*** Ravikumar_hp has quit IRC23:04
*** ken1ohmichi_ has quit IRC23:04
*** mlavalle has left #openstack-meeting23:04
*** eglynn has quit IRC23:05
*** dkranz is now known as dkranz_dinner23:08
*** bknudson has left #openstack-meeting23:08
*** SumitNaiksatam has quit IRC23:09
*** mspreitz has quit IRC23:10
*** jcoufal has quit IRC23:12
*** yassine has quit IRC23:12
*** burt has quit IRC23:12
*** jgrimm has joined #openstack-meeting23:14
*** rakhmerov has joined #openstack-meeting23:18
*** fifieldt has joined #openstack-meeting23:18
*** vkmc has quit IRC23:19
*** vuil has quit IRC23:20
*** sacharya has quit IRC23:22
*** ryanpetrello has joined #openstack-meeting23:23
*** ijw has left #openstack-meeting23:25
*** dougshelley66 has joined #openstack-meeting23:26
*** herndon has joined #openstack-meeting23:27
*** lbragstad has quit IRC23:28
*** lbragstad has joined #openstack-meeting23:30
*** pablosan has quit IRC23:30
*** lbragstad has quit IRC23:35
*** dstanek has quit IRC23:35
*** kgriffs is now known as kgriffs_afk23:35
*** dstanek has joined #openstack-meeting23:42
*** diogogmt has quit IRC23:43
*** samcdona has joined #openstack-meeting23:43
*** IlyaE has joined #openstack-meeting23:44
*** sarob has joined #openstack-meeting23:44
*** ayoung has quit IRC23:46
*** galstrom is now known as galstrom_zzz23:46
*** otherwiseguy has quit IRC23:47
*** prad has quit IRC23:47
*** bdpayne has quit IRC23:48
*** rakhmerov has quit IRC23:52
*** dkranz_dinner is now known as dkranz23:56
*** SergeyLukjanov has quit IRC23:57
*** yamahata_ has joined #openstack-meeting23:58
*** salv-orlando has quit IRC23:58

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