Thursday, 2013-05-30

*** sushils has quit IRC00:00
*** sdake_ has joined #openstack-meeting00:04
*** sdake_ has quit IRC00:04
*** sdake_ has joined #openstack-meeting00:04
*** openrk has left #openstack-meeting00:06
*** sdake_ has quit IRC00:10
*** sdake_ has joined #openstack-meeting00:10
*** sdake_ has joined #openstack-meeting00:10
*** colinmcnamara has quit IRC00:13
*** gongysh has joined #openstack-meeting00:16
*** tanisdl has quit IRC00:16
*** nachi has quit IRC00:28
*** bdpayne has quit IRC00:29
*** fnaval has quit IRC00:30
*** reed has quit IRC00:48
*** ladquin is now known as ladquin_afk00:49
*** seanrob_ has quit IRC00:51
*** sdake has quit IRC00:51
*** jogo has joined #openstack-meeting00:55
*** sdake_ has quit IRC00:56
*** lbragstad has joined #openstack-meeting01:00
*** jogo has quit IRC01:03
*** jog0 has joined #openstack-meeting01:03
*** beagles has quit IRC01:03
*** mrutkows has quit IRC01:03
*** dolphm has quit IRC01:05
*** ryanpetrello has joined #openstack-meeting01:07
*** dolphm has joined #openstack-meeting01:07
*** litong has quit IRC01:07
*** gyee has quit IRC01:09
*** sdake has joined #openstack-meeting01:12
*** sdake has quit IRC01:12
*** sdake has joined #openstack-meeting01:12
*** ssurana has left #openstack-meeting01:17
*** jog0 has quit IRC01:20
*** ladquin_afk has quit IRC01:20
*** ryanpetrello has quit IRC01:31
*** terryg_ has quit IRC01:34
*** yaguang has joined #openstack-meeting01:36
*** markpeek has joined #openstack-meeting01:40
*** Mandell has quit IRC01:40
*** fnaval has joined #openstack-meeting01:46
*** zaneb has joined #openstack-meeting01:50
*** zb has joined #openstack-meeting01:52
*** otherwiseguy has joined #openstack-meeting01:55
*** zaneb has quit IRC01:55
*** radez_g0n3 is now known as radez02:02
*** sandywalsh_ has quit IRC02:03
*** zb has quit IRC02:04
*** anniec has quit IRC02:05
*** ayoung_ is now known as ayoung02:06
*** zb has joined #openstack-meeting02:06
*** martine has joined #openstack-meeting02:07
*** zbitter has joined #openstack-meeting02:08
*** Tross has joined #openstack-meeting02:08
*** zb has quit IRC02:11
*** dosaboy has quit IRC02:13
*** zb has joined #openstack-meeting02:18
*** zbitter has quit IRC02:18
*** dosaboy has joined #openstack-meeting02:20
*** vkmc has quit IRC02:23
*** spzala has quit IRC02:28
*** schwicht has quit IRC02:30
*** schwicht has joined #openstack-meeting02:30
*** sandywalsh has joined #openstack-meeting02:37
*** sdake_ has joined #openstack-meeting02:38
*** xBsd has joined #openstack-meeting02:40
*** dolphm has quit IRC02:42
*** SergeyLukjanov has joined #openstack-meeting02:45
*** lpabon has joined #openstack-meeting02:49
*** ewindisch has quit IRC02:49
*** sdake_ has quit IRC02:51
*** sdake_ has joined #openstack-meeting02:53
*** bradjones|away has quit IRC02:55
*** bradjones|away has joined #openstack-meeting02:57
*** ewindisch has joined #openstack-meeting03:01
*** martine has quit IRC03:01
*** MarkAtwood has joined #openstack-meeting03:03
*** zbitter has joined #openstack-meeting03:04
*** zb has quit IRC03:06
*** zb has joined #openstack-meeting03:07
*** zbitter has quit IRC03:09
*** SergeyLukjanov has quit IRC03:10
*** xBsd has quit IRC03:12
*** SergeyLukjanov has joined #openstack-meeting03:12
*** adrian_otto has joined #openstack-meeting03:13
*** novas0x2a|laptop has quit IRC03:16
*** ryanpetrello has joined #openstack-meeting03:17
*** sushils has joined #openstack-meeting03:21
*** dstanek has joined #openstack-meeting03:22
*** Mandell has joined #openstack-meeting03:25
*** sdake_ has quit IRC03:25
*** haomaiwang has joined #openstack-meeting03:27
*** markpeek has quit IRC03:34
*** markpeek has joined #openstack-meeting03:34
*** MarkAtwood has quit IRC03:36
*** ewindisch has quit IRC03:40
*** dolphm has joined #openstack-meeting03:41
*** zbitter has joined #openstack-meeting03:41
*** zb has quit IRC03:44
*** stevemar has joined #openstack-meeting03:47
*** dstanek has quit IRC03:47
*** sdake_ has joined #openstack-meeting03:57
*** sdake_ has quit IRC03:57
*** sdake_ has joined #openstack-meeting03:57
*** HenryG has quit IRC03:59
*** shang has quit IRC03:59
*** zb has joined #openstack-meeting04:02
*** zbitter has quit IRC04:04
*** bdpayne has joined #openstack-meeting04:05
*** lastidiot has quit IRC04:16
*** sungju has joined #openstack-meeting04:17
*** bdpayne has quit IRC04:19
*** rostam has quit IRC04:20
*** jgriffith has quit IRC04:20
*** bdpayne has joined #openstack-meeting04:20
*** jgriffith has joined #openstack-meeting04:22
*** glikson has joined #openstack-meeting04:22
*** rostam has joined #openstack-meeting04:22
*** koolhead17 has joined #openstack-meeting04:27
*** koolhead17 has joined #openstack-meeting04:27
*** garyk has quit IRC04:32
*** rushiagr has joined #openstack-meeting04:35
*** rushiagr has left #openstack-meeting04:35
*** sdake_ has quit IRC04:36
*** kebray has joined #openstack-meeting04:36
*** dcramer__ has quit IRC04:41
*** sdake has quit IRC04:45
*** zbitter has joined #openstack-meeting04:49
*** zb has quit IRC04:50
*** Mandell has quit IRC04:50
*** zb has joined #openstack-meeting04:50
*** dcramer__ has joined #openstack-meeting04:53
*** zbitter has quit IRC04:53
*** sdake has joined #openstack-meeting04:56
*** stevemar has quit IRC04:57
*** glikson has quit IRC04:58
*** lloydde has joined #openstack-meeting04:59
*** schwicht has quit IRC05:02
*** adrian_otto has quit IRC05:05
*** ryanpetrello has quit IRC05:07
*** bdpayne has quit IRC05:08
*** sushils has quit IRC05:18
*** otherwiseguy has quit IRC05:22
*** sushils has joined #openstack-meeting05:22
*** ndipanov has joined #openstack-meeting05:23
*** sushils has quit IRC05:24
*** yonglihe__ has quit IRC05:27
*** shang has joined #openstack-meeting05:27
*** glikson has joined #openstack-meeting05:28
*** garyk has joined #openstack-meeting05:30
*** mrunge has joined #openstack-meeting05:30
*** sdake_ has joined #openstack-meeting05:32
*** sdake_ has quit IRC05:32
*** sdake_ has joined #openstack-meeting05:32
*** SergeyLukjanov has quit IRC05:37
*** egallen has joined #openstack-meeting05:43
*** adrian_otto has joined #openstack-meeting05:44
*** lpabon has quit IRC05:48
*** reed has joined #openstack-meeting05:50
*** reed has quit IRC05:54
*** adrian_otto has quit IRC05:57
*** egallen has quit IRC06:04
*** egallen has joined #openstack-meeting06:08
*** koolhead17 has quit IRC06:08
*** haomaiwang has quit IRC06:10
*** egallen has quit IRC06:10
*** kebray has quit IRC06:13
*** lloydde has quit IRC06:18
*** markpeek has quit IRC06:20
*** IlyaE has joined #openstack-meeting06:20
*** haomaiwang has joined #openstack-meeting06:20
*** boris-42 has joined #openstack-meeting06:30
*** jcoufal has joined #openstack-meeting06:33
*** BobBallAway has joined #openstack-meeting06:36
*** boris-42 has quit IRC06:38
*** sdake_ has quit IRC06:38
*** belliott has quit IRC06:39
*** belliott has joined #openstack-meeting06:40
*** boris-42 has joined #openstack-meeting06:43
*** gongysh has quit IRC06:46
*** boris-42 has quit IRC06:51
*** egallen has joined #openstack-meeting06:58
*** Mandell has joined #openstack-meeting06:59
*** dkehn has joined #openstack-meeting07:01
*** haomaiwang has quit IRC07:04
*** haomaiwang has joined #openstack-meeting07:08
*** sushils has joined #openstack-meeting07:18
*** salv-orlando has joined #openstack-meeting07:25
*** dkehn has quit IRC07:26
*** lloydde has joined #openstack-meeting07:29
*** jdurgin has quit IRC07:29
*** lloydde has quit IRC07:33
*** IlyaE has quit IRC07:35
*** IlyaE has joined #openstack-meeting07:37
*** IlyaE has quit IRC07:38
*** xBsd has joined #openstack-meeting07:39
*** reed has joined #openstack-meeting07:46
*** boris-42 has joined #openstack-meeting07:49
*** skraynev has joined #openstack-meeting07:55
*** johnthetubaguy has joined #openstack-meeting07:59
*** sungju has quit IRC08:03
*** jang has quit IRC08:05
*** jang has joined #openstack-meeting08:10
*** BobBallAway has quit IRC08:11
*** xBsd has quit IRC08:14
*** BobBallAway has joined #openstack-meeting08:19
*** dolphm has quit IRC08:24
*** BobBallAway has quit IRC08:24
*** ndipanov has quit IRC08:26
*** BobBallAway has joined #openstack-meeting08:26
*** Yada has joined #openstack-meeting08:29
*** jang has quit IRC08:38
*** BobBallAway has quit IRC08:47
*** xBsd has joined #openstack-meeting08:51
*** jhenner has joined #openstack-meeting08:51
*** johnthetubaguy1 has joined #openstack-meeting08:53
*** jang has joined #openstack-meeting08:54
*** derekh has joined #openstack-meeting08:54
*** xBsd has quit IRC08:55
*** johnthetubaguy has quit IRC08:56
*** zb is now known as zaneb08:57
*** SergeyLukjanov has joined #openstack-meeting09:04
*** xBsd has joined #openstack-meeting09:06
*** Yada has quit IRC09:09
*** cian_ has left #openstack-meeting09:15
*** leizhang has joined #openstack-meeting09:19
*** dkehn has joined #openstack-meeting09:21
*** leizhang has quit IRC09:30
*** leizhang has joined #openstack-meeting09:31
*** flaper87 has joined #openstack-meeting09:34
*** xBsd has quit IRC09:37
*** Yada has joined #openstack-meeting09:37
*** xBsd has joined #openstack-meeting09:50
*** Yada has quit IRC10:06
*** Yada has joined #openstack-meeting10:09
*** Yada has quit IRC10:14
*** gongysh has joined #openstack-meeting10:15
*** markmcclain has joined #openstack-meeting10:39
*** mrunge has quit IRC10:39
*** zaneb has quit IRC10:41
*** zaneb has joined #openstack-meeting10:41
*** ttrifonov is now known as ttrifonov_zZzz10:44
*** dstanek has joined #openstack-meeting10:44
*** ttrifonov_zZzz is now known as ttrifonov10:45
*** mrunge has joined #openstack-meeting10:46
*** zaneb has quit IRC10:46
*** yaguang has quit IRC10:54
*** jhenner has quit IRC10:55
*** jhenner has joined #openstack-meeting10:55
*** dprince has joined #openstack-meeting10:59
*** boris-42 has quit IRC11:00
*** ayurchen has quit IRC11:02
*** psedlak has joined #openstack-meeting11:04
*** jhenner1 has joined #openstack-meeting11:08
*** jhenner has quit IRC11:09
*** jcooley has quit IRC11:10
*** jcooley has joined #openstack-meeting11:10
*** ayurchen has joined #openstack-meeting11:11
*** beagles has joined #openstack-meeting11:20
*** Tross has quit IRC11:29
*** ryanpetrello has joined #openstack-meeting11:34
*** dstanek has quit IRC11:40
*** jhenner1 has quit IRC11:42
*** jhenner has joined #openstack-meeting11:42
*** leizhang has quit IRC11:43
*** nimi1 has joined #openstack-meeting11:44
*** nimi has quit IRC11:44
*** dkehn has quit IRC11:45
*** ayurchen has quit IRC11:45
*** jmh_ has quit IRC11:53
*** markmcclain has quit IRC11:53
*** martine_ has joined #openstack-meeting11:58
*** pcm__ has joined #openstack-meeting12:01
*** martine_ has quit IRC12:01
*** ewindisch has joined #openstack-meeting12:03
*** egallen has quit IRC12:05
*** ayoung has quit IRC12:05
*** sandywalsh has quit IRC12:07
*** HenryG has joined #openstack-meeting12:12
*** fnaval_ has joined #openstack-meeting12:15
*** mrunge has quit IRC12:15
*** fnaval has quit IRC12:17
*** sandywalsh has joined #openstack-meeting12:20
*** garyk has quit IRC12:20
*** ewindisch has quit IRC12:24
*** johnthetubaguy1 has quit IRC12:27
*** johnthetubaguy has joined #openstack-meeting12:29
*** schwicht has joined #openstack-meeting12:32
*** lbragstad has quit IRC12:38
*** johnthetubaguy1 has joined #openstack-meeting12:38
*** dcramer__ has quit IRC12:41
*** johnthetubaguy has quit IRC12:41
*** stevemar has joined #openstack-meeting12:41
*** garyk has joined #openstack-meeting12:47
*** ijw has quit IRC12:55
*** lorin1 has joined #openstack-meeting12:55
*** ijw has joined #openstack-meeting12:58
*** ewindisch has joined #openstack-meeting12:59
*** ayoung has joined #openstack-meeting13:03
*** lbragstad has joined #openstack-meeting13:06
*** Yada has joined #openstack-meeting13:06
*** ewindisch has quit IRC13:09
*** jhenner has quit IRC13:09
*** jmh_ has joined #openstack-meeting13:10
*** Yada has quit IRC13:11
*** jhenner has joined #openstack-meeting13:15
*** psedlak_ has joined #openstack-meeting13:17
*** psedlak has quit IRC13:18
*** dcramer__ has joined #openstack-meeting13:19
*** markpeek has joined #openstack-meeting13:19
*** changbl has quit IRC13:20
*** dprince has quit IRC13:21
*** ijw has quit IRC13:23
*** vkmc has joined #openstack-meeting13:25
*** vkmc has joined #openstack-meeting13:25
*** markmcclain has joined #openstack-meeting13:28
*** ozstacker has quit IRC13:29
*** ewindisch has joined #openstack-meeting13:29
*** woodspa has joined #openstack-meeting13:32
*** mrunge has joined #openstack-meeting13:34
*** gongysh has quit IRC13:35
*** egallen has joined #openstack-meeting13:36
*** dolphm has joined #openstack-meeting13:39
*** dcramer__ has quit IRC13:42
*** salv-orlando has quit IRC13:44
*** dkehn has joined #openstack-meeting13:45
*** zehndton has joined #openstack-meeting13:46
*** chuckieb has joined #openstack-meeting13:48
*** dstanek has joined #openstack-meeting13:49
*** ivasev has joined #openstack-meeting13:50
*** tongli has joined #openstack-meeting13:51
*** otherwiseguy has joined #openstack-meeting13:51
*** ndipanov has joined #openstack-meeting13:51
*** mrunge has quit IRC13:52
*** llu-laptop has joined #openstack-meeting13:52
*** fnaval_ has quit IRC13:54
*** dprince has joined #openstack-meeting13:54
*** boris-42 has joined #openstack-meeting13:55
*** ozstacker has joined #openstack-meeting13:57
*** ladquin has joined #openstack-meeting13:58
*** markmcclain has quit IRC13:58
*** xBsd has quit IRC14:01
*** reed has quit IRC14:01
*** tongli has quit IRC14:02
*** shengjie has joined #openstack-meeting14:03
*** mrodden has joined #openstack-meeting14:04
*** dhellmann-away is now known as dhellmann14:05
*** psedlak__ has joined #openstack-meeting14:06
*** shengjie has quit IRC14:09
*** psedlak_ has quit IRC14:10
*** jhenner has quit IRC14:11
*** shengjie has joined #openstack-meeting14:12
*** BobBallAway has joined #openstack-meeting14:12
*** zehndton has left #openstack-meeting14:13
*** zehndton has joined #openstack-meeting14:13
*** fnaval has joined #openstack-meeting14:15
*** eharney has joined #openstack-meeting14:16
*** eharney has joined #openstack-meeting14:16
*** adalbas has joined #openstack-meeting14:16
*** salv-orlando has joined #openstack-meeting14:19
*** cp16net|away is now known as cp16net14:20
*** shengjie has quit IRC14:22
*** tanisdl has joined #openstack-meeting14:23
*** jhenner has joined #openstack-meeting14:24
*** adrian_otto has joined #openstack-meeting14:25
*** ozstacker has quit IRC14:26
*** zehndton has quit IRC14:28
*** eglynn has joined #openstack-meeting14:32
*** lpabon has joined #openstack-meeting14:32
*** adrian_otto has quit IRC14:37
*** garyk has quit IRC14:39
*** kchenweijie has joined #openstack-meeting14:40
*** adrian_otto has joined #openstack-meeting14:42
*** egallen has quit IRC14:42
*** egallen has joined #openstack-meeting14:43
*** IlyaE has joined #openstack-meeting14:44
*** xingzhou has joined #openstack-meeting14:45
*** lloydde has joined #openstack-meeting14:47
*** lloydde has quit IRC14:47
*** spzala has joined #openstack-meeting14:48
*** kchenweijie has left #openstack-meeting14:49
*** lloydde has joined #openstack-meeting14:49
*** BobBallAway has quit IRC14:50
*** dcramer__ has joined #openstack-meeting14:51
*** lastidiot has joined #openstack-meeting14:51
*** mrutkows has joined #openstack-meeting14:53
*** egallen has quit IRC14:54
*** egallen has joined #openstack-meeting14:55
*** xBsd has joined #openstack-meeting14:55
*** Guest58831 has joined #openstack-meeting14:56
Guest58831o/14:56
*** Guest58831 is now known as thomasem14:56
*** garyk has joined #openstack-meeting14:57
*** mjmulloc has joined #openstack-meeting14:57
*** nealph has joined #openstack-meeting14:58
*** gordc has joined #openstack-meeting14:58
*** markvan has joined #openstack-meeting15:00
jd__#startmeeting ceilometer15:00
openstackMeeting started Thu May 30 15:00:48 2013 UTC.  The chair is jd__. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: ceilometer)"15:00
openstackThe meeting name has been set to 'ceilometer'15:00
sandywalsho/15:01
dragondmo/15:01
nealph\o'15:01
eglynno/15:01
mjmulloco/15:01
llu-laptopo/15:01
dhellmanno/15:01
gordco/15:01
jd__hey everyone15:01
mrutkowso/15:01
*** xBsd has quit IRC15:01
nijabao/15:01
n0anoo/15:01
*** pcm__ has quit IRC15:02
jd__let's go!15:02
jd__#topic Last week action: jd__ and dhellmann to write formal statement about limiting support for pre-grizzly versions of ceilometer15:02
*** openstack changes topic to "Last week action: jd__ and dhellmann to write formal statement about limiting support for pre-grizzly versions of ceilometer (Meeting topic: ceilometer)"15:02
* jd__ whispers15:02
dhellmannThe ceilometer team has limited capacity to provide support for older versions of the project. Because the project graduated from incubation around the time of the grizzly release, that is the first version for which we will provide regular ongoing support following the standard deprecation cycle for OpenStack. The grizzly version of ceilometer is cannot be installed on the same server with earlier versions of OpenStac15:02
dhellmannbecause of conflicting package requirements, but is API compatible with the folsom release if installed separately.15:02
*** Matty has joined #openstack-meeting15:03
*** kebray has joined #openstack-meeting15:03
*** 50UAAAVJ3 has joined #openstack-meeting15:03
eglynnnitpick: s/ceilometer is cannot be/ceilometer cannot be/15:03
eglynnotherwise looks good to me!15:04
dhellmanncorrected15:04
jd__where should we publish that?15:04
dhellmannsomewhere in our docs?15:04
dhellmannmaybe in the installing section?15:04
dhellmannand also probably to the openstack mailing list15:04
nealphhow about in the readme?15:05
eglynnshould we mention the stable/grizzly branch explicitly, or is that implicit in "ongoing support"?15:05
*** BrooklynChen has joined #openstack-meeting15:05
eglynnactually, yeah, I think it probably is implicit ...15:05
*** 50UAAAVJ3 has quit IRC15:05
dhellmannI think that's implicit?15:05
eglynnyep, agreed15:05
dhellmannif there's a link to that policy, I can include a link when I add this to the docs15:06
nealphi.e, in the root code directory..15:06
dhellmannnealph: we have a lot of people trying to install from tarballs, so I'm not sure they will see it in the readme :-/15:06
jd__I was typing that15:06
jd__the doc that is online is probably the most read, so let's go with that15:07
eglynndhellmann: by "that policy", do you mean the overall stable branch policy? i.e. as expressed on https://wiki.openstack.org/wiki/StableBranch15:07
jd__who wants to take the #action to make a patch?15:07
dhellmannyeah15:07
dhellmannI'll do it15:07
eglynncool15:07
nealphwas thinking 'in addition to' online...15:07
gordcreadme is pretty empty, i'm not sure anyone uses it... it does point to http://launchpad.net/ceilometer15:07
nealphbut that said, I agree with the tarball comment.15:07
llu-laptopI don't think it hurts to put in readme, as an addition though15:08
*** pcm_ has joined #openstack-meeting15:08
*** DanD has joined #openstack-meeting15:08
* nealph tends to look there first15:08
*** gongysh has joined #openstack-meeting15:09
sandywalshnealph, +115:09
jd__so anyone up to the task?15:09
eglynnon sending to the mailing list ... the dev list is good, but should we also consider openstack-announce?15:09
jd__we can ask ttx for -announce I guess15:10
eglynn(i.e. much less volume, reserved for important announcements etc, might hit a different audience ...)15:10
nealphI will15:10
eglynncool15:10
dhellmannjd__: I'm working on a patch now15:10
gordcfair enough. i guess since we don't need to update statement that often it isn't a concern having it in multiple places.15:10
nealphsorry, regarding readme.15:10
jd__dhellmann: great15:10
jd__#action dhellmann make a patch on Ceilometer documentation to include the statement about Grizzly support15:11
dhellmann#link https://review.openstack.org/3106215:11
llu-laptopso fast15:11
jd__cool15:12
dhellmann#action dhellmann to send email to the openstack list about the support policy15:12
dhellmannoh, do you guys think we need to use the announce list?15:12
jd__dhellmann: maybe, ask ttx for his opinion and permission15:12
dhellmannthat feels a little formal, but I can talk to ttx if you want15:12
dhellmannok15:12
*** rscottcoyle has joined #openstack-meeting15:13
*** hemna has joined #openstack-meeting15:13
jd__moving on then :)15:13
jd__#topic Review Havana-2 milestone15:13
*** openstack changes topic to "Review Havana-2 milestone (Meeting topic: ceilometer)"15:13
jd__#link https://launchpad.net/ceilometer/+milestone/havana-215:13
jd__if you're not aware h1 is on its way today15:13
jd__so we should focus on delivering h2 now15:14
*** tanisdl has quit IRC15:14
*** tanisdl has joined #openstack-meeting15:15
jd__this time every blueprint has a owner, which is great :)15:15
*** leizhang has joined #openstack-meeting15:15
jd__think about updating the status of your blueprint as you work on them15:15
jd__I don't have much comment on this for this week anyway; any question?15:16
sandywalshRoland has prepared a spec for https://blueprints.launchpad.net/ceilometer/+spec/specify-event-api ... but had to do it as a new BP. Can I merge that with my previous spec?15:17
sandywalshbtw> dhellmann, you should give that a peek. In your wheelhouse.15:17
dhellmannsandywalsh: it's on my list :-)15:17
sandywalsh:)15:17
jd__sandywalsh: yes, do you need me to do anything?15:18
*** gongysh has quit IRC15:18
sandywalshjd__,  not sure. I could just point my spec to his wiki page. But is there a way I can give him the ability to change the BP directly? Perhaps assign him as the assignee or drafter?15:19
dhellmannthe bps are linked already, do they need to be "merged"?15:19
dhellmannI'm not objecting, just asking...15:20
sandywalshyeah, he had to create a new one because it wouldn't let him assign the spec himself15:20
jd__sandywalsh: maybe, I'm not LP expert :)15:20
sandywalshk, we'll mess with it and clean it up15:20
jd__but I can do assignment of bp of things like that if needed15:20
sandywalshthat's all from me :)15:21
*** seanrob has joined #openstack-meeting15:22
*** xBsd has joined #openstack-meeting15:22
jd__#topic blueprint discussion: support for auditing event - mrutkows, gordc15:22
*** openstack changes topic to "blueprint discussion: support for auditing event - mrutkows, gordc (Meeting topic: ceilometer)"15:22
jd__#link https://blueprints.launchpad.net/ceilometer/+spec/support-standard-audit-formats15:22
mrutkowshi everyone15:22
jd__mrutkows, gordc floor is yours15:22
*** xBsd has quit IRC15:22
mrutkowsstill kinda new to Ceilomter, but over last month been working hard to learn code and come up to speed15:23
mrutkowsbasically what we are trying to do with this blueprint, is establish a configurale audit path that leverages ceilometer architecture and features, but can be used to create/log records that have normative data that can be attested to by an auditor15:23
dhellmannthis sounds similar to the work sandywalsh is doing with recording notifications15:24
jd__I've read through the proposal, and it seems like a good idea to me15:24
mrutkowsi have more of a security standards background... and it came to my attention that people wanted to code special logging for Nova15:24
jd__dhellmann: yes, but based on standards15:24
* dhellmann hasn't had a chance to read the whole thing, so may be misunderstanding15:24
mrutkowsand we thought leveraging Ceilometer was a better path15:24
*** changbl has joined #openstack-meeting15:24
jd__dhellmann: but the idea behind is really the same15:24
sandywalshthis would be easy to implement on the nova side to make a notification driver that would output in this "standard" format. There would have to be a corresponding parser on the CM side. If it's optional on both sides, I think it's a nice addition. Keeps the enterprise customers happy.15:25
mrutkowswe want the path to supprt std. formats for normative comparison15:25
jd__mrutkows: something I don't get, is how you want to store your CADF data?15:25
mrutkowsso we proposed it be a configurable path15:25
dhellmannI love the idea of standardizing. We did have a few people object to the idea of requiring ceilometer for deploying nova, for example, but that was related to the scheduler. This could be less tightly coupled, so shouldn't be an issue.15:25
sandywalshmrutkows, my apologies for not formally responding before this meeting.15:25
mrutkowswell, for now as metadata as this is the path thats easy for now15:25
gordcdhellmann, is there a bp sandywalsh work?15:25
sandywalshgordc, our approach has been to use the existing nova notification format15:26
mrutkowshi Sandy, yes I have seen many things in blueprints and other topics that we may have alignment in many ideas15:26
dhellmanngordc: several :-)15:26
jd__mrutkows: ok, I see this in your WIP code indeed, but this seems under efficient, you're using counters but you don't really count anything15:26
jd__mrutkows: what sandywalsh is working on will be much more useful I think15:26
*** seanrob has quit IRC15:27
sandywalshI don't think they're mutually exclusive. We're really just talking about the wire format, yes?15:27
jd__mrutkows: in the end I think you want a notification driver for Oslo that emits CADF and a collector that registers CADF data in a well-designed db15:27
mrutkowsjd: ive been hoping to align with Sandy's proposals,  notification path (filter) seems correct path (push)15:27
sandywalshjd__, +115:27
mrutkowsjd: i agree15:27
jd__mrutkows: which in the end is orthogonal to Ceilometer functionnalities, even if you use the same wire15:28
mrutkowsit seemed that starting within Ceilometer and then promoting to OSLO after proven seemed best15:28
jd__whereas I see event recording as sandywalsh is working a leverage for us to build more counters15:28
*** jcoufal has quit IRC15:28
sandywalshjd__, except we can use the existing Event/Trait model to store the event as per normal. The incoming collector translator would just be different15:28
dhellmannis the point to get CADF data into ceilometer, or to get it out?15:28
*** leizhang has quit IRC15:28
jd__dhellmann: to get it in, but there's no value for ceilometer15:28
jd__mrutkows: I actually think you should start a side project on this15:29
mrutkowsPrimarily get it in, getting out would be a conversation for another day, as long as we can store it for now then im happy15:29
mrutkowsCADF does have a query syntax15:29
mrutkowsbut that is something of a pipe dream at this stage15:29
jd__you'd call it "OpenStack Audit Service" :)15:29
dhellmannwould it make more sense to add a new query API that used the CADF format for queries and responses and accessed the ceilometer database?15:30
mrutkowsOpenStack can brand it sure =)15:30
*** mrunge has joined #openstack-meeting15:30
mrutkowsdellmann: your my hero15:30
dhellmannI need to read more. I'm not sure why the wire format between nova and ceilometer needs to change.15:30
*** mrodden has quit IRC15:31
dragondmHmmm... Y'know there is a side project already out there designed to take OS notifications and translate them to different formats...15:31
sandywalshwe haven't defined a robust query api for Events yet, might be something worth considering (so long as it's not bloated api-by-committee :)15:31
mrutkowsdhellmann: would make myself and any info available to you15:31
jd__dhellmann: yeah, but I really thinks it's a whole different set of functionnality at this stage15:31
jd__audit isn't metering15:31
dhellmannjd__: sure15:31
dragondmit's called Yagi.15:31
*** epende has joined #openstack-meeting15:31
sandywalshdhellmann, I assume it's if the endpoint isn't CM15:31
dhellmannbut it does seem like it goes towards our revised goal of providing the data we collect for lots of purposes15:31
dhellmannthis could be our first API extension :-)15:32
dhellmannalthough I don't see an issue with making it a first class part of the API, if it's just returning data in a different format15:32
jd__anyway even if we keep this into ceilometer, this is going to need a new collector and/or db schema IMHO15:32
mrutkowsjd: there is a relationship between metering and auditing15:32
mrutkowsthe cadf spec. acks. this fact if your interested in reading15:33
dhellmannjd__: well, no, that was my point -- if they're just mapping events/counters to these new record types, couldn't we do that with the existing data?15:33
jd__dhellmann: I've a tendency to think "audit" means "store raw stuff that we are sure nobody messed with"15:33
*** lloydde has quit IRC15:33
dhellmannsuch as the notification events sandywalsh is adding support for?15:34
nijabajd__: I tend to agree with your view15:34
jd__dhellmann: yes15:34
mrutkowsdhellmann: perhaps, but the CADF data model assures all info needed for ISO, NIST, COBIT etc are in the record in a normative way15:34
jd__or one solution would be to twist sandywalsh's work to use CADF format instead15:34
nealphmrutkows: in the the record, or in the api response?15:34
mrutkowsperhaps we can use this exercise to identify what the essential data is so any format could map15:34
dhellmannmrutkows: ok, well, using CADF format throughout does make it seem like a bigger project15:34
mrutkowsnealph: in the record,the record eventually has to be immutable and even signed15:35
mrutkowsnealph: audit records cannot be created on demand15:35
sandywalshjd__, how it's stored in the db shouldn't really matter. It's how it appears on the wire and how it's published that really matters.15:35
dhellmannnotifications aren't signed now, but that would be a straightforward addition15:35
sandywalshdragondm, do you think the right approach would be to translate in Yagi or via a specific notification driver?15:36
jd__sandywalsh: for audit purpose, I'm not really sure15:36
mrutkowssandy: yes consider it a wire format, but if we can allow it to also be signed and stored in a format a customer needs, that is better15:36
dragondmhmm.....15:36
*** mkollaro has joined #openstack-meeting15:36
sandywalshmrutkows, customers shouldn't be hitting the CM db directly anyway15:36
*** Mandell has quit IRC15:36
dragondmit might depend on their requirements.  A driver would be simpler.15:37
nealphdragondm: +115:37
mrutkowssandy: auditors want to grab logs eventually and a format has to be one that can be relied upon (and better a standard format)15:37
sandywalshdragondm, that's what I'm thinking. No need to stand up another server15:37
sandywalshmrutkows, but couldn't they do that from the raw events? Why do they have to use the logs?15:38
mrutkowssandy: ideally customers should not15:38
*** egallen has quit IRC15:38
sandywalshmrutkows, we wouldn't want to dump raw events in the logs if they contain sensitive info15:38
*** mrodden has joined #openstack-meeting15:38
mrutkowssandy: we have lots to talk about i can see =)15:38
sandywalsh:)15:38
mrutkowssandy: the companies that worked on CADF know that dumping raw events are not enough15:39
mrutkowssandy: background and discussion would take many beers15:39
sandywalshI'll reread and give proper feedback. I don't think there's anything in there that worries me. I think it call all be done as drivers/plugins and as optional components.15:39
sandywalshs/call/can/15:39
mrutkowssandy: thanks )15:40
nealphmrutkows: points for a nice BP though. :)15:40
mrutkowsnealph: thanks much15:40
jd__sounds great :)15:41
mrutkowsjd: thanks for allowing us to discuss today15:41
sandywalshmrutkows, mailing list or wiki markup for comments? What's best for you?15:42
mrutkowswiki markup seems to be more robust15:42
* dhellmann likes the ceilometer architecture diagram in the wiki page15:42
jd__dhellmann: yeah me too15:42
sandywalshmrutkows, will do15:42
jd__mrutkows: would be a good idea to use your ceilometer diagram from the wiki in our doc actually15:43
*** ewindisch has quit IRC15:43
gordcjd__, was just going to suggest the same15:43
mrutkowsjd: that would be great15:44
*** ewindisch has joined #openstack-meeting15:44
mrutkowsjd: I can provide the powerpoint originals if needed or tweak as needed15:44
dhellmannmrutkows: original files would be good, too, for updates later15:44
mrutkowsjd: i am actually working on another level of the diagram, to show an overlay of what major files comprosie each box15:45
mrutkowscomprise15:45
sandywalshyou can add the original ppt as an attachment to the wiki page. That's what I usually do.15:45
mrutkowsdhellmann: ok will post to wiki15:45
nealphI think there is a diagram update in the pipeline now...15:45
*** ewindisch has quit IRC15:45
* nealph searching for the changeid15:46
eglynnhttps://review.openstack.org/#/c/27835/15:46
eglynnnealph: ^^^ it that the one you mean?15:46
mrutkowsGordon will be helping me to review WIP code and with my first check in15:46
dhellmannnealph: there is, but we've been having some trouble communicating the useful bits of the architecture to include15:46
nealphyep :)15:46
*** ndipanov has quit IRC15:46
*** boris-42 has quit IRC15:47
mrutkowsnealph: Tong Li works in my group15:47
mrutkowsnealph: I can work with him to see if he can make use of mine15:48
nealphgreat...maybe merge the text updates from that change and leverage this diagram?15:48
mrutkowsnealph: will read the patch comments15:49
mrutkowsand see if I can address with Tong15:49
*** markmcclain has joined #openstack-meeting15:49
nealphk. will add that suggestion to patch comments.15:50
jd__#topic Open discussion15:50
*** openstack changes topic to "Open discussion (Meeting topic: ceilometer)"15:50
jd__if you want to address something else or continue :)15:50
dhellmannttx suggested that we just send the support announcement to the main mailing list, so I will do that15:51
eglynnreminder: the freeze for 2013.1.2 is today (release due on June 6th)15:51
eglynnso if you've anything you think should be in the second release off stable/grizzly, please tag and/or backport15:51
eglynn(I'll do a trawl thru' the git log in any case before EoD today)15:51
*** kmartin has quit IRC15:52
*** timello has quit IRC15:52
*** TravT has quit IRC15:52
dhellmanneglynn: is that schedule published somewhere?15:52
*** seanrob has joined #openstack-meeting15:52
eglynndhellmann: one sec, I'll dig it out ...15:52
nijabahttps://wiki.openstack.org/wiki/Havana_Release_Schedule ?15:54
eglynn#link http://lists.openstack.org/pipermail/openstack-stable-maint/2013-April/000479.html15:54
*** adrian_otto has quit IRC15:54
eglynnscroll down to "Finally, future stable/grizzly releases will be ..."15:54
dhellmannthanks15:54
dhellmannI think I joined the stable team after that list was established15:55
eglynna-ha, cool15:55
dhellmannI'm still getting set up with notifications and such :-)15:55
*** ozstacker has joined #openstack-meeting15:55
BrooklynChenjd__: is there a bp for non-admin user authentication?15:56
*** colinmcnamara has joined #openstack-meeting15:56
*** seanrob has quit IRC15:57
jd__BrooklynChen: there was, this is already implemented15:57
*** adrian_otto has joined #openstack-meeting15:58
jd__#endmeeting15:59
*** openstack changes topic to "OpenStack meetings"15:59
openstackMeeting ended Thu May 30 15:59:54 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-05-30-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-05-30-15.00.txt15:59
jd__thanks guys15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-05-30-15.00.log.html16:00
*** mjmulloc has left #openstack-meeting16:00
*** llu-laptop has quit IRC16:00
*** torandu has joined #openstack-meeting16:00
*** mrutkows has quit IRC16:00
BrooklynChenjd__:  oh… great. thanks I will check that.16:00
*** haomaiwang has quit IRC16:00
jd__BrooklynChen: if you need help, come and ask on #openstack-metering :)16:00
BrooklynChenjd__:  OK ;)16:01
*** seanrob has joined #openstack-meeting16:01
*** haomaiwang has joined #openstack-meeting16:01
*** bdpayne has joined #openstack-meeting16:02
*** adrian_otto has quit IRC16:03
*** mkollaro has quit IRC16:03
*** mkollaro1 has joined #openstack-meeting16:03
*** kchenweijie has joined #openstack-meeting16:03
*** timello has joined #openstack-meeting16:04
*** mkollaro has joined #openstack-meeting16:04
*** kmartin has joined #openstack-meeting16:06
*** lloydde has joined #openstack-meeting16:07
*** nealph has quit IRC16:07
*** psedlak__ has quit IRC16:07
*** SergeyLukjanov has quit IRC16:08
*** FallenPegasus has joined #openstack-meeting16:10
*** p4tux has joined #openstack-meeting16:11
*** colinmcnamara has quit IRC16:12
*** seanrob has quit IRC16:12
*** jhenner has quit IRC16:12
*** seanrob has joined #openstack-meeting16:12
*** xingzhou has quit IRC16:12
*** glikson has quit IRC16:19
*** rostam has quit IRC16:20
*** shengjie has joined #openstack-meeting16:20
*** seanrob_ has joined #openstack-meeting16:21
*** dstanek has quit IRC16:21
*** seanrob has quit IRC16:22
*** seanrob_ has quit IRC16:22
*** seanrob has joined #openstack-meeting16:22
*** rostam has joined #openstack-meeting16:23
*** garyk has quit IRC16:26
*** krtaylor has joined #openstack-meeting16:26
*** alexheneveld has joined #openstack-meeting16:27
*** schwicht has quit IRC16:27
*** schwicht has joined #openstack-meeting16:29
*** colinmcnamara has joined #openstack-meeting16:29
*** ndipanov has joined #openstack-meeting16:30
*** glikson has joined #openstack-meeting16:31
*** mdomsch has joined #openstack-meeting16:31
*** bpb has joined #openstack-meeting16:31
*** joshuamckenty has joined #openstack-meeting16:32
*** vladimir3p has joined #openstack-meeting16:32
*** shengjie has quit IRC16:33
*** BobBallAway has joined #openstack-meeting16:33
*** IlyaE has quit IRC16:33
*** epende has quit IRC16:38
*** garyk has joined #openstack-meeting16:40
*** glikson has quit IRC16:43
*** koolhead17 has joined #openstack-meeting16:46
*** koolhead17 has joined #openstack-meeting16:46
*** jasondotstar has joined #openstack-meeting16:47
*** BrooklynChen has left #openstack-meeting16:49
*** jlucci has joined #openstack-meeting16:51
*** BobBallAway has quit IRC16:53
*** krtaylor has quit IRC16:53
*** boris-42 has joined #openstack-meeting16:54
*** Randy_Perryman has joined #openstack-meeting16:54
*** mpavlase has joined #openstack-meeting16:55
*** dstanek has joined #openstack-meeting16:56
*** anniec has joined #openstack-meeting16:56
*** rscottcoyle has quit IRC16:57
*** joshuamckenty has left #openstack-meeting16:59
*** malini1 has joined #openstack-meeting16:59
*** mkollaro has quit IRC17:00
*** vladimir3p has quit IRC17:00
*** lcheng has joined #openstack-meeting17:00
sdagueok, who's around for qa meeting?17:01
sdagueanyone....17:02
*** hemna has quit IRC17:03
*** hemna has joined #openstack-meeting17:03
sdaguehmm... lacking any additional voices I think we'll call it a day without a meeting17:03
*** vladimir3p has joined #openstack-meeting17:03
*** DanD has quit IRC17:03
mpavlasesdague: hi, I'm interested in QA17:04
mpavlase* on QA17:04
sdaguehey, well we seem to be very light on attendees17:04
sdagueso given that, perhaps it's better to just take any conversation to the main irc channel17:05
sdaguelet me at least make a note of it17:05
sdague#startmeeting qa17:05
openstackMeeting started Thu May 30 17:05:19 2013 UTC.  The chair is sdague. Information about MeetBot at http://wiki.debian.org/MeetBot.17:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:05
*** Shree-HP has joined #openstack-meeting17:05
*** openstack changes topic to " (Meeting topic: qa)"17:05
openstackThe meeting name has been set to 'qa'17:05
mpavlasesure17:05
*** dhellmann is now known as dhellmann-away17:05
sdague#info due to light attendance, qa meeting cut short, all attendees encouraged to discuss on #openstack-qa17:05
sdague#endmeeting17:05
*** openstack changes topic to "OpenStack meetings"17:05
openstackMeeting ended Thu May 30 17:05:55 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:05
openstackMinutes:        http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-05-30-17.05.html17:05
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-05-30-17.05.txt17:06
openstackLog:            http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-05-30-17.05.log.html17:06
*** dkehn has quit IRC17:06
sdaguempavlase: you on #openstack-qa? I don't see you there17:06
*** terry7 has joined #openstack-meeting17:06
mpavlaseooh, I will fix it, mmt17:06
*** Shree-HP has quit IRC17:06
*** dkehn has joined #openstack-meeting17:07
*** krtaylor has joined #openstack-meeting17:07
*** xBsd has joined #openstack-meeting17:08
*** kchenweijie has quit IRC17:09
*** lloydde has quit IRC17:12
*** vladimir3p has quit IRC17:12
*** SergeyLukjanov has joined #openstack-meeting17:18
*** derekh has quit IRC17:18
*** malini has joined #openstack-meeting17:20
*** eglynn has quit IRC17:23
*** sushils has quit IRC17:23
*** sushils has joined #openstack-meeting17:26
*** adrian_otto has joined #openstack-meeting17:28
*** tanisdl has quit IRC17:28
*** mrunge has quit IRC17:29
*** sushils has quit IRC17:29
*** otherwiseguy has quit IRC17:31
*** jhenner has joined #openstack-meeting17:31
*** HenryG_ has joined #openstack-meeting17:31
*** HenryG has quit IRC17:32
*** jhenner has quit IRC17:35
*** jhenner has joined #openstack-meeting17:35
*** shardy is now known as shardy_afk17:36
*** vladimir3p has joined #openstack-meeting17:37
*** nachi has joined #openstack-meeting17:41
*** ivasev has quit IRC17:41
*** lloydde has joined #openstack-meeting17:42
*** glikson has joined #openstack-meeting17:45
*** eglynn has joined #openstack-meeting17:46
*** pekowski1 has joined #openstack-meeting17:48
*** vladimir3p has quit IRC17:49
*** huseyin has joined #openstack-meeting17:50
*** markwash has joined #openstack-meeting17:50
*** pekowski1 has left #openstack-meeting17:50
*** eglynn has quit IRC17:51
*** dstanek has quit IRC17:52
*** dguitarbite has joined #openstack-meeting17:53
*** pekowski1 has joined #openstack-meeting17:53
*** johnthetubaguy1 has quit IRC17:54
*** ravikumar_hp has joined #openstack-meeting17:55
*** markmcclain has quit IRC17:55
*** FallenPegasus is now known as MarkAtwood17:56
*** mpavlase1 has joined #openstack-meeting17:56
*** pekowski1 has left #openstack-meeting17:57
*** ewindisch has joined #openstack-meeting17:58
*** jhullinge has joined #openstack-meeting17:58
*** mpavlase has quit IRC17:59
*** chair6 has joined #openstack-meeting18:01
*** jlucci has quit IRC18:01
*** ivasev has joined #openstack-meeting18:01
*** pekowski1 has joined #openstack-meeting18:01
*** garyk has quit IRC18:02
*** kchenweijie has joined #openstack-meeting18:02
*** lcheng has quit IRC18:02
*** mpavlase1 has quit IRC18:02
*** glikson has quit IRC18:03
bdpayne#startmeeting OpenStack Security Group18:03
openstackMeeting started Thu May 30 18:03:48 2013 UTC.  The chair is bdpayne. Information about MeetBot at http://wiki.debian.org/MeetBot.18:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:03
*** openstack changes topic to " (Meeting topic: OpenStack Security Group)"18:03
openstackThe meeting name has been set to 'openstack_security_group'18:03
bdpaynegood morning / afternoon / evening everyone18:04
*** vkmc has quit IRC18:04
bdpayneBryan Payne from Nebula here.. do we have others joining the meeting?18:04
*** schwicht has quit IRC18:04
*** lloydde has quit IRC18:04
bpbafternoon, this Bruce18:04
*** shardy_afk is now known as shardy18:04
*** schwicht has joined #openstack-meeting18:04
bdpaynehi bruce18:05
bdpaynenormally we have a few more… it was quiet last week too18:05
*** pekowski1 has left #openstack-meeting18:06
*** pekowski1 has joined #openstack-meeting18:06
bdpaynewell, we can walk through a few items18:06
bdpayne#topic Doc Sprint Update18:06
*** openstack changes topic to "Doc Sprint Update (Meeting topic: OpenStack Security Group)"18:07
bdpayneThe doc sprint will be happening at the end of June in Annapolis18:07
bdpayneWe have around 15 people attending18:07
bdpayneShould be a good event18:07
*** pekowski1 has quit IRC18:07
*** nicolae_ has joined #openstack-meeting18:08
bdpaynebpb there may be opportunities during that week to grab a meal with APL folk, if you guys are interested in come out to Annapolis… I'm not sure yet but let me know if that's of interest18:08
bdpayneI'm sure we'll keep a pretty tight schedule though18:08
bdpayne#topic New people18:09
*** openstack changes topic to "New people (Meeting topic: OpenStack Security Group)"18:09
*** mtesauro has joined #openstack-meeting18:09
bdpayneWe've had several new people join the group recently18:09
bdpayneNext task is to convert those people into productive / contributing members18:09
bdpayne:-)18:10
bdpayneI'm starting with work with a few people to plan out some longer term goals and course of actions for OSSG18:10
bdpayneif you're interested in contributing to that, let me know18:10
bdpayne#topic Ongoing Efforts18:10
*** openstack changes topic to "Ongoing Efforts (Meeting topic: OpenStack Security Group)"18:10
nicolae_is there a list of activities where a member could contribute?18:10
bdpayneI saw that the volume encryption code dropped recently18:11
bdpayneBut we need to make that public to allow for people to review it18:11
bdpaynebpb is that something you could talk with Joel about?18:11
bpbThat was dropped, but we're having some limited initial review by some key management folks before we open this up furhter18:12
bdpaynenicolae_ Hi!  Rob and I had a list of such things in our presentation at the summit, but I need to get that online as well18:12
*** markmcclain has joined #openstack-meeting18:12
bdpaynein the mean time, feel free to send me an email18:12
nicolae_cool, thanks; I'll drop you an email too18:13
*** lorin1 has left #openstack-meeting18:13
*** HenryG_ has quit IRC18:13
bdpaynebpb Ok, that makes sense18:14
*** joel-coffman has joined #openstack-meeting18:14
bdpaynethe good news is that the securityimpact tag works… lots of people got emails this morning to go look at that code :-)18:14
bpbRight now, the updates shouldn't be visible.  Is that the case?18:15
bdpayneyes, that is the case18:15
*** glikson has joined #openstack-meeting18:15
bdpayne#topic Open Discussion18:15
*** openstack changes topic to "Open Discussion (Meeting topic: OpenStack Security Group)"18:15
bdpayneThat's about all that I have for today… it goes quick when there's a small group18:16
bdpayneAnything else that people would like to discuss?18:16
bpbRe- the volume encryption code update, sorry that the changes can't be seen, but this will be visible within a few days.  Sponsor issue ...18:17
bdpayneno worries18:17
bdpayneI think it causes a little confusion this morning18:17
bdpayneperhaps a quick email to the openstack security mailing list would be helpfu;18:18
joel-coffmansorry about that18:18
joel-coffmanI'll send something later today18:18
bdpaynesorry, my typing is poor right now18:18
bdpaynesounds good18:18
*** HenryG has joined #openstack-meeting18:18
bdpayneok, then I think that's all for today18:19
bdpayneplease use the mailing list if issues come up during the week18:19
*** garyk has joined #openstack-meeting18:19
bdpaynecheers!18:19
*** jhullinge has quit IRC18:20
*** chair6 has left #openstack-meeting18:20
bdpayne#endmeeting18:21
*** openstack changes topic to "OpenStack meetings"18:21
openstackMeeting ended Thu May 30 18:21:13 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:21
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-05-30-18.03.html18:21
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-05-30-18.03.txt18:21
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-05-30-18.03.log.html18:21
*** joel-coffman has quit IRC18:22
*** huseyin has quit IRC18:23
*** IlyaE has joined #openstack-meeting18:25
*** mtesauro has left #openstack-meeting18:25
*** salv-orlando has quit IRC18:25
*** ravikumar_hp has quit IRC18:27
*** lastidiot1 has joined #openstack-meeting18:28
*** lastidiot has quit IRC18:31
*** seanrob has quit IRC18:33
*** Tross has joined #openstack-meeting18:37
*** tanisdl has joined #openstack-meeting18:37
*** jpeeler has quit IRC18:38
*** gordc has left #openstack-meeting18:39
*** jpeeler has joined #openstack-meeting18:46
*** jpeeler has joined #openstack-meeting18:46
*** otherwiseguy has joined #openstack-meeting18:46
*** Mandell has joined #openstack-meeting18:46
*** lastidiot has joined #openstack-meeting18:47
*** lastidiot1 has quit IRC18:47
*** boris-42 has quit IRC18:48
*** krtaylor has quit IRC18:49
*** fesp has joined #openstack-meeting18:50
*** flaper87 has quit IRC18:51
*** fesp is now known as flaper8718:51
*** BobBallAway has joined #openstack-meeting18:52
*** dstanek has joined #openstack-meeting18:54
*** numero8 has joined #openstack-meeting18:54
*** elo has joined #openstack-meeting18:55
*** sdake_ has joined #openstack-meeting18:56
*** sdake_ has quit IRC18:56
*** sdake_ has joined #openstack-meeting18:56
driptonDB meeting in 1 minute18:59
driptonIs anyone here for the DB meeting?19:00
driptonWorld's Shortest Meeting19:00
*** chuckieb has quit IRC19:01
*** mdomsch_ has joined #openstack-meeting19:04
*** markwash is now known as markwash-away19:10
*** vipuls is now known as vipuls|away19:11
*** vipuls|away is now known as vipuls19:11
*** elo has quit IRC19:12
*** jhenner has quit IRC19:13
*** nicolae_ has quit IRC19:16
*** joshuamckenty has joined #openstack-meeting19:17
*** joshuamckenty has quit IRC19:19
*** eglynn has joined #openstack-meeting19:20
*** jdurgin1 has quit IRC19:22
*** jdurgin has joined #openstack-meeting19:23
*** ayoung has quit IRC19:25
*** novas0x2a|laptop has joined #openstack-meeting19:25
*** markwash-away is now known as markwash19:25
*** malini1 has quit IRC19:26
*** vipuls is now known as vipuls|away19:26
*** HenryG has quit IRC19:27
*** dstanek has quit IRC19:31
*** malini1 has joined #openstack-meeting19:32
*** cp16net is now known as cp16net|away19:35
*** cp16net|away is now known as cp16net19:35
*** stevebaker has joined #openstack-meeting19:35
*** stevebaker is now known as stevebaker__19:35
*** garyk has quit IRC19:35
*** shardy is now known as shardy_afk19:36
*** krtaylor has joined #openstack-meeting19:37
*** sdake_ has quit IRC19:37
*** spzala has quit IRC19:43
*** sandywalsh has quit IRC19:44
*** jhenner has joined #openstack-meeting19:45
*** alexpilotti has joined #openstack-meeting19:45
*** dprince has quit IRC19:46
*** eharney has quit IRC19:46
*** noslzzp has quit IRC19:46
*** stevebaker__ has quit IRC19:53
*** noslzzp has joined #openstack-meeting19:55
*** sandywalsh has joined #openstack-meeting19:55
*** otherwiseguy has quit IRC19:58
harlowja#startmeeting state-management20:00
openstackMeeting started Thu May 30 20:00:10 2013 UTC.  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:00
harlowjaHi all, rollcall if anyone is interested :)20:00
*** flaper87 has quit IRC20:00
changblharlowja, hello there20:00
harlowjahowdy!20:00
alexpilottiHo20:01
* harlowja give others a few minutes20:02
harlowja#link https://wiki.openstack.org/wiki/Meetings/StateManagement#Agenda_for_next_meeting20:02
*** ehudtr has joined #openstack-meeting20:02
*** anniec has quit IRC20:02
*** flaper87 has joined #openstack-meeting20:02
*** andrew_plunk has joined #openstack-meeting20:02
adrian_ottohi20:02
*** sandywalsh has quit IRC20:02
*** cp16net is now known as cp16net|away20:02
*** cp16net|away is now known as cp16net20:02
harlowjahey20:03
*** vipuls|away is now known as vipuls20:03
harlowjaso seems like we have enough people20:03
harlowjacan start off with a little status of the library (from what i know)20:03
harlowja#topic status20:03
*** openstack changes topic to "status (Meeting topic: state-management)"20:03
harlowjaanyone that has done anything with the library feel free to let others know :)20:04
changblLooks like you guys have some good progress, I am still trying to catch up with you folks20:04
harlowjai've been adding more decorators in, helping rackspace folks get there changes in for the db 'backend'20:04
harlowjachangbl thx!20:04
changblharlowja, the code is mainly in TaskFlow right?20:04
changblnot NovaOrc?20:05
harlowjacorrect20:05
harlowja#link https://github.com/Yahoo/TaskFlow20:05
changblok, I will check taskflow20:05
harlowjathats current location until the stackforge move finishes20:05
changblso we are moving taskflow to stackforge?20:05
harlowjaya, so that its not just a yahoo (aka me) thing :)20:06
harlowjaand we can use the review system that everyone involved in openstack knows20:06
harlowjaand all that20:06
kebrayhello.20:06
changblsure20:06
harlowjahi kebray20:06
*** markmcclain has quit IRC20:07
harlowjakebray and updates from your side, just going through a little status of 'the world;20:07
harlowja^any20:07
uvirtbotharlowja: Error: "any" is not a valid command.20:07
changblharlowja, do I need to check anything on NovaOrc?20:07
*** ayurchen has joined #openstack-meeting20:07
harlowjachangbl if u just want to see how some of the nttdata folks and i started shifting code around in nova, then its useful20:07
kebrayNo updates from me other than I know Jessica was reworking her code…20:07
harlowjakebray thx20:08
*** xBsd has quit IRC20:08
changblharlowja, ok20:08
kebrayshe has an idea for distributed task flow management, but the first path she went down didn't pan out.. but, she's reworking it.20:08
harlowjaall good :)20:08
kebrayShe's out of office today.20:08
*** ameade is now known as no20:09
harlowjanp20:09
changblkebray, is Jessica working on ZK backend now?20:09
*** ayoung has joined #openstack-meeting20:09
*** no is now known as ameade20:09
kebraychangbl.  not at the moment… last I heard from her I think she said someone else is working on that.  maybe you?20:09
*** thomasem has left #openstack-meeting20:10
kebrayShe is working on distributed state management, using celery I believe.20:10
*** ozstacker has quit IRC20:10
harlowja#topic whose-working-on-what20:10
*** openstack changes topic to "whose-working-on-what (Meeting topic: state-management)"20:10
kebrayas opposed to linear/sequential state management.20:10
changblkebray, I had a very busy week... but I plan to work on ZK backend20:10
*** noslzzp has quit IRC20:10
harlowjachangbl i think thats still an open item20:10
kebraychangbl: excellent.  We have an interest. so happy to hear that.20:10
changblkebray, sounds good20:11
harlowjabtw i'm working on plugging cinder in (and just the general library goodness)20:11
harlowjai think kevin and jessica (from rackspace) are doing the distributed states (with celery) + db backend20:11
kebrayharlowja:  where is the code living now?  Is it on stackforge?20:11
*** alexpilotti has quit IRC20:11
kebrayharlowja:  correct about kevin and Jessica.20:11
harlowjakebray so its almost to stackforge, i think jessica has to do one more review commit :)20:12
harlowja#link https://review.openstack.org/#/c/30789/20:12
harlowjasomeone complained about whitespace :(20:12
*** maurosr- has joined #openstack-meeting20:12
changbllol20:12
changblquite some effort to put a project on stackforge20:12
harlowjadef20:12
*** maurosr has quit IRC20:13
alexheneveldhowdy -- sorry i'm late20:13
changblone questions, what is the diff between zk backend and celery?20:13
harlowjai believe another guy is involved might also be looking in the ZK stuff as well changbl , haven't heard much though, can connect u 220:13
changblharlowja, sure20:14
*** lloydde has joined #openstack-meeting20:14
changbllet me know20:14
harlowjacool20:14
harlowjahi alexheneveld20:14
harlowja*we are just going over who is doing what as of right now :)20:14
adrian_ottoalexheneveld: hi20:14
harlowjawhich does bring up a good point about how putting stuff on say launchpad might help it become more clear20:14
harlowjabut maybe after the stackforge move we can do that?20:14
harlowjalike launchpad/~taskflow or something20:15
*** pcm_ has quit IRC20:15
changblharlowja, one question, what is the diff between ZK backend and celery? I see a celery folder in backends/ in Taskflow20:15
harlowjaits a good question, and comes down to what do we want the ZK backend to do :)20:15
harlowjacelery is more of a way to run tasks, ZK wouldn't neccasarily be a 'running mechansim'20:15
harlowjadoes that make sense?20:16
harlowja#link http://www.celeryproject.org/20:16
changblI once used ZK to implemented a distributed queue20:16
alexheneveldthx harlowja hi adrian_otto - we've been spiking it (samc)20:16
changblyes, checking their website20:16
alexheneveldcelery supports ZK as a transport20:16
alexheneveldnot used it tho20:16
alexheneveldTBH i think since we have a DB that is a logical choice20:16
alexheneveldcool as ZK is of course :)20:17
harlowjaagreed, so ZK can be a 'storage' backend20:17
*** kmartin has quit IRC20:17
harlowjabut it also provides the other more interesting part of 'job transfer'20:17
harlowjaexample20:17
alexheneveldnot sure if celery supports all the mutexes/alarms we need but that should be an abstract service20:17
changblharlowja, what do we use ZK to store?20:17
adrian_ottowe'll likely need a combination of both20:17
harlowjaconductor A gets job to do Y, conductor A claims job Y via ZK, conductor A does 1/2 of the task required for job A, conductor A dies20:18
*** anniec has joined #openstack-meeting20:18
harlowjanow with ZK u can transfrer job Y from A -> conductor B when u notice it dies20:18
*** vipuls is now known as vipuls|away20:18
*** cp16net is now known as cp16net|away20:18
adrian_ottoassuming it rolls back and restarts from the beginnning?20:19
harlowja#topic details20:19
*** openstack changes topic to "details (Meeting topic: state-management)"20:19
changblharlowja, you mean leader election via ZK?20:19
harlowjaadrian_otto well rolling back may be appropriate in some of the workflows, but not all, some u may just be able to resume where conductor A left off20:20
adrian_ottook20:20
harlowjachangbl so if u think of each job as having an owner, it maps to the concept of ZK locks and ZK watches20:20
*** malini has left #openstack-meeting20:20
*** therve has joined #openstack-meeting20:21
changblharlowja, yes, I used that before20:21
harlowjawhen owner (conductor A) dies, ZK releases lock, then conductor B gets a notification via its watch on said lock, and then conductor B can attempt to acquire it20:21
harlowjaso then that brings up the question of what is stored to be able to allow conductor B to resume (or rollback) job Y20:22
changblharlowja, make sense, that means ZK stores that info?20:22
changbli mean from where to resume20:23
harlowjaright, each task/flow that composes job Y creates some result, that resulted is stored 'somewhere' and that result set can be referenced later for rollback or resuming20:23
harlowjaso ZK can be one such place to store, or a DB can20:23
harlowjakevin from rackspace is working on the DB place to store that20:23
harlowjawhich started to showup this week (in the db backend)20:24
*** blallau has joined #openstack-meeting20:24
harlowjaan example of how said storage might look like (when printed), was showing this to john griffith (the cinder PTL)20:24
harlowja#link http://paste.openstack.org/show/37929/20:24
harlowja*just an example*20:24
*** woodspa has quit IRC20:24
jgriffitho/20:24
harlowjasaid information could be exposed as 'what did my job do' API20:25
harlowja*if desired*20:25
harlowjachangbl does that all make sense? :)20:25
*** esker has joined #openstack-meeting20:26
changblharlowja, yes. Just wonder, do you have any code on this that I can check out?20:26
harlowjafor the ZK backend?20:26
harlowjaor the code that produced the above paste?20:26
changblThe code which defines what to store, and how they call APIs20:27
*** jcoufal has joined #openstack-meeting20:27
harlowjaso right now that is20:27
harlowja#link https://github.com/yahoo/TaskFlow/blob/master/taskflow/logbook.py20:27
ehudtrso except locking you may like ZK also to keep the workflow state? why both db and ZK?20:27
*** jcoufal has quit IRC20:28
kebraysome folks are opposed to zookeeper… also, it'll be good to have a lightweight db implementation for devstack me thinks.20:28
harlowjayes, but if someone wants to work on a ZK 'storage' backend, then that seems fine no?20:29
kebrayYes!20:29
kebrayagreed20:29
kebrayI'm not opposed to Zookeeper.   I'm pro modularity and plugable backend implementations.20:29
harlowjawhich does bring up the good question of ZK ;)20:29
harlowja#topic locks20:30
*** lloydde has quit IRC20:30
*** openstack changes topic to "locks (Meeting topic: state-management)"20:30
harlowja#link https://wiki.openstack.org/wiki/StructuredWorkflowLocks20:30
harlowjaso if u guys want to check that out, its my idea of something that taskflow could provide20:30
*** jcoufal has joined #openstack-meeting20:30
harlowjaalthough maybe not at stage 1.020:30
harlowjawhen i was reading the google chubby paper, they say that not even googles own developers do locking right, so thats why they made chubby, so it'd be nice to offer a api that can help get it *somewhat* right20:31
*** jog0 has joined #openstack-meeting20:31
harlowja#link http://research.google.com/archive/chubby-osdi06.pdf20:31
*** otherwiseguy has joined #openstack-meeting20:32
harlowjai just think that resource level locking will come up pretty quick, especially after talking to devananda  about ironic20:32
*** sandywalsh has joined #openstack-meeting20:32
harlowja#link https://wiki.openstack.org/wiki/StructuredWorkflowLocks#Ironic_.28WIP.2920:32
*** gyee has joined #openstack-meeting20:33
devanandao/20:33
harlowjaha, just talking about locking :-P20:33
*** shardy_afk is now known as shardy20:33
harlowjai think its something we should try to offer, but offer it 'very carefully'20:33
harlowjathoughts?20:33
devananda#link https://github.com/openstack/ironic/blob/master/ironic/manager/task_manager.py#L2020:33
devanandais what i put together for ironic20:33
harlowjathx devananda20:34
devanandanova alrady does this is a fairly poor way, IMHO20:34
devanandawith 'task_state'20:34
devanandavery easy to get out of sync // lost20:34
harlowjayup, nova confuses a task_state with a lock20:35
harlowjawhen task_state should just be that, a task state :-P20:35
devanandajust look at "nova reset-state"20:35
devanandathat that even exists says bad things20:35
harlowjaya :-/20:35
harlowjado others think it'd be useful for taskflow to provide something like that locking API in the above wiki, or at least something like it20:36
harlowja*backed by 1 or more implementations20:36
kebrayharlowja  will have to wade through some of those links before I have feedback.20:37
harlowjanp20:37
adrian_ottoregarding the lock wiki reference from above, in section "Filesystem" under Drawbacks, it reads "Does not release automatically on lock holder failure (but timeouts on locks are possible)."20:37
alexheneveldyes, a generic locking service would be good20:37
harlowjaadrian_otto does that make sense, i could word it better?20:37
adrian_ottothat's not true, depending on what you define as failure20:38
adrian_ottoif the caller holding an advisory lock goes away, then the lock is automatically released by the kernel.20:38
harlowjaadrian_otto true, good point20:38
adrian_ottogo away = process terminates for any reason20:38
harlowjaalexheneveld its just when we give a locking api thingy, then people have to be prettty aware of how to acquire those locks 'sanely'20:39
harlowja*ordering issues become a big problem, lol20:39
alexheneveldis there a good one we could reuse however?20:39
harlowjaalexheneveld none afaik20:39
devanandafilesystem locks should, IMO, call out a draback that it's not distributed20:39
harlowjadevananda sure20:39
alexheneveldshame.  it's hard to get right!  people will just keep asking for new use cases otherwise.20:39
harlowjai was reading about stuff like http://linux.die.net/man/3/dlm_lock, ibms vms and such20:40
alexheneveldit might be an idea to aim for a higher-level model20:40
adrian_ottodevananda: you still could use a multiplicity of filesystems as a backing store for locks if you were inclined to make a networked lock service built that way.20:40
harlowjadlm_lock and such stuff i didn't find much info on though, except that glusterfs i think uses its :-p20:40
alexheneveldas in you are locking lifecycle of a server20:41
harlowjaalexheneveld agreed, i think this is why chubby (the google zookeeper) provides only coarse grained locking20:41
harlowjaand i think if we can be pretty coarse, we will also be fine, its just defining 'coarse' isn't so easy, ha20:42
alexheneveldpeople should be discouraged from low-level locking operations tho i accept they may need to be available20:42
devanandaadrian_otto: true, but with a SPoF on the network FS. or a consistency problem if using a distributed FS20:42
alexheneveldharlowja: makes a lot of sense (re chubby)20:42
*** flaper87 has quit IRC20:42
changblharlowja, one question, why do we have so many (6) providers for locking? plan to implement all of them?20:42
harlowjachangbl it was more of just a survey of ones i could think of20:43
changbloh, ok20:43
harlowjai think redis, filesystem, ZK might be a good 320:43
*** SergeyLukjanov has quit IRC20:43
harlowjaor just redis + filesystem to start20:44
*** cp16net|away is now known as cp16net20:44
harlowja*so as not to scare people with ZK20:44
*** numero8 has quit IRC20:44
changblI can take ZK20:44
changblfor both storage and locking, i guess here?20:44
harlowjathat'd be cool20:45
harlowja#link http://openreplica.org/faq/ was another interesting one, that has something like ZK in python20:45
harlowjadidn't investigate much more though20:45
devanandathough i don't usually recommend it, i suspect innodb+galera would actually be a good fit here20:45
devanandaNDB would be another, but very complex to set up20:46
changblnever used OpenReplica before20:46
changblZK + Kazoo seems work nice20:46
harlowjachangbl ya, it shouldn't be that hard to connect it to the taskflow api20:47
devanandaAIUI, galera, with the proper settings, will do distributed lock before committing a write. min 3 servers, so partitioning is less of an issue20:47
harlowjadevananda intereting, didn't know that :)20:47
*** jhenner has quit IRC20:47
*** lloydde has joined #openstack-meeting20:47
harlowja*interesting20:47
adrian_ottoOpenReplica looks interesting.20:47
*** BobBallAway has quit IRC20:48
harlowjaadrian_otto ya, i'm not sure how mature it is though, didn't mess around with it that much20:48
devanandafrom the little reading on openreplica i did, it's aimed at geographic distribution20:48
harlowjawith some underlying paxos concoord thing20:49
adrian_ottodevananda: do you have a documentation pointer to galera re: locking? Where did you learn about that behavior?20:49
*** xBsd has joined #openstack-meeting20:49
devanandalemme see if i can find it20:49
devanandaadrian_otto: learned about it while working at percona ... :)20:49
harlowjachangbl if u want to work on the ZK stuff that'd be really neat, i think we can keep in the back of our mind how 'job/workflow' transfer can occur with ZK20:50
devanandaadrian_otto: http://www.codership.com/wiki/doku.php?id=mysql_options_0.8 -- wsrep_causal_reads, IIRC20:51
adrian_ottomost of what I found when I looked for that is actually about table locking limitations in Master:Master setups20:51
adrian_ottoaha20:51
changblharlowja, sure20:52
adrian_ottoread committed isolation level might actually work well enough for what we need.20:52
adrian_ottoand assuming that works equally well in a 3 node arrangement, that might actually be one of the best ZK alternatives.20:52
*** ecarlin has joined #openstack-meeting20:52
devanandabetter link / explanation20:53
adrian_ottowe could deploy/configure it using a HOT in a well automated way too, I expect.20:53
devananda#link http://www.percona.com/doc/percona-xtradb-cluster/wsrep-system-index.html#wsrep_causal_reads20:53
devanandaadrian_otto: and yes, galera is designed to require min 3 nodes. it wont start with 220:53
devanandabut will continue to run if a 3-node degrades to 220:53
harlowjadevananda for ironic, do u have any thoughts on what u'd like for say when the thing using your context manager crashes (without releasing)?20:53
harlowjamanual recovery at that point to release? time based release?20:54
devanandaharlowja: eventually, time-based release-wipe-set-to-error or something20:54
harlowjak20:54
*** blallau has quit IRC20:55
adrian_ottousing a Galera cluster also solves a multi-tenancy concern as well, which may of the other options don't address.20:55
adrian_otto(if any)20:55
adrian_ottos/may/many/20:55
harlowjaZK has namespaces afaik ;)20:55
adrian_ottowith related auth?20:55
harlowja*unsure*20:56
harlowjaalright, 4 minutes20:56
*** dolphm has quit IRC20:57
harlowjaadrian_otto it might be interesting to see if the hortonworks people (that i think are doing hadoop) have thought about how ZK and openstack20:57
*** lloydde has quit IRC20:57
harlowjaand especially the tenant issue20:57
*** ecarlin has quit IRC20:57
*** woodspa has joined #openstack-meeting20:58
adrian_ottoSavanna is actually Mirantis, not Hortonworks20:58
harlowjaah20:58
adrian_ottowe know them, so I could ask20:58
*** xBsd has quit IRC20:58
harlowjaah, either way20:58
harlowjai thought hortonworks, guess i was mistakened20:58
harlowja*which we know :-P20:58
*** hemna has quit IRC20:58
harlowjaanyways, that'd be neat to see what they think20:58
*** andrew_plunk has left #openstack-meeting20:59
*** hemna has joined #openstack-meeting20:59
harlowjacool, well times up folks!20:59
harlowjaemail, or irc, or more email for anything else :)20:59
harlowja#endmeeting20:59
*** openstack changes topic to "OpenStack meetings"20:59
alexheneveldbfn all20:59
openstackMeeting ended Thu May 30 20:59:45 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/state_management/2013/state_management.2013-05-30-20.00.html20:59
*** joel-coffman has joined #openstack-meeting20:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/state_management/2013/state_management.2013-05-30-20.00.txt20:59
openstackLog:            http://eavesdrop.openstack.org/meetings/state_management/2013/state_management.2013-05-30-20.00.log.html20:59
*** Mr__T has joined #openstack-meeting21:00
*** melwitt has joined #openstack-meeting21:00
*** ecarlin has joined #openstack-meeting21:00
*** ehudtr has quit IRC21:01
russellb#startmeeting nova21:01
openstackMeeting started Thu May 30 21:01:29 2013 UTC.  The chair is russellb. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: nova)"21:01
russellbhello!21:01
openstackThe meeting name has been set to 'nova'21:01
russellbwho's here?21:01
driptonhi21:01
devananda\o21:01
melwitthi21:01
n0anoo/21:01
cyeohhi!21:01
cburgesspresent21:01
russellb#link https://wiki.openstack.org/wiki/Meetings/Nova21:01
alaskio/ and at an OS meetup so may be spotty21:02
dansmitho/21:02
russellb#topic blueprints21:02
*** openstack changes topic to "blueprints (Meeting topic: nova)"21:02
russellbso, havana-1 was released today!21:02
russellb#link https://launchpad.net/nova/+milestone/havana-121:02
*** geekinutah has joined #openstack-meeting21:02
russellb16 blueprints and 214 bugs closed21:02
*** xBsd has joined #openstack-meeting21:03
russellb:-)21:03
russellbso now our next milestone is havana-2, with a target of July 1821:03
comstudo/21:03
russellb#link https://launchpad.net/nova/+milestone/havana-221:03
*** kchenweijie has left #openstack-meeting21:03
russellbso, total 100 havana blueprints right now, 16 in havana-2, and 69 targeted to havana-221:03
russellbprobably optimistic :-)21:03
jog0o/21:04
russellbbut take a look, see what you have on here, make sure it's still current21:04
russellband if anything is missing, let's get it filed21:04
russellba lot got pushed from havana-1 to havana-2, so there are a lot already up for review21:04
russellbany particular blueprints anyone wants to dicuss?21:04
russellbor process questions?21:04
*** tpatil has joined #openstack-meeting21:05
comstudcrickets21:05
russellbalrighty!21:05
russellb#topic bugs21:05
*** openstack changes topic to "bugs (Meeting topic: nova)"21:05
russellb#link https://wiki.openstack.org/wiki/Nova/BugTriage21:05
comstudI need to re-open that sys_meta not being deleted bug21:05
russellbso, as discussed over the last couple weeks, we've started a slightly modified process for triage21:05
comstudor should I file a new one?21:05
russellbto help distribute the load21:06
comstud(since I reverted the previous fix)21:06
*** ecarlin has quit IRC21:06
russellbcomstud: good question ... re-open i guess?21:06
comstudi thought re-open21:06
*** Randy_Perryman has quit IRC21:06
* russellb nods21:06
comstudbut i dunno :)21:06
comstudok21:06
russellbyeah, works for me21:06
russellbso if you take a look at the Nova/BugTriage page, we still have some holes in the sign-up list.21:06
russellbcould use some more people to take ownership of triage for a given tag21:06
*** xBsd has quit IRC21:07
jog0russellb: yeah, what review times21:07
jog0were the numbers you posted accurate in the end?  And how do we do a better job?21:07
*** sandywalsh has quit IRC21:07
russellbjog0: yeah, the numbers are pretty accurate now ... current numbers here: http://russellbryant.net/openstack-stats21:07
russellbso if we look at ... http://russellbryant.net/openstack-stats/nova-openreviews.txt21:08
russellbI think we are keeping up overall ... people seem to agree that < 4 days is a very good goal, and we're meeting that21:08
russellbwe obviously have some that seem to get neglected and wait much longer21:08
russellbdolphm wrote a nice 'next-review' tool that helps pick a review to do, giving priority based on age, but filtering out stuff you've already looked at and such21:09
russellbso that's worth looking at ...21:09
jog0not sure how this factors into the numbers but I have seen several patches expire with +1s etc21:09
russellbyeah, that's not good21:09
russellbactually, do reviews really expire even with no negative feedback?21:09
russellbthat doesn't seem ideal.21:09
driptonthe submitter can always revive them so it's not a *huge* deal21:10
dansmithyeah, I didn't think they would21:10
jog0https://review.openstack.org/#/c/23207/21:10
russellbugh21:10
devanandawow...21:10
jog0not sure if that only happens on stable21:10
comstudi think it happens everywhere21:10
* jog0 just restored teh patch from the dead.21:11
russellb#action need to follow up on whether it makes sense to expire changes with no negative feedback21:11
*** vipuls|away is now known as vipuls21:11
devanandamight explain why the "oldest review" has been stable just under 14 days21:11
russellbIMO that should only happen for reviews with -1/-2 and no updates for X days21:11
russellbso i'll follow up on that ...21:11
cyeohthere are reviews which are older than that around, just that someone has commented on it in the last 2 weeks.21:12
russellbprobably just post to the ML21:12
*** schwicht has quit IRC21:12
russellbcyeoh: the script shouldn't reset the timer because of a comment21:12
russellbcyeoh: only if you got a -1/-221:12
cyeohrussellb: yea agreed21:12
russellbotherwise it's time since (roughly) when you submitted it21:12
russellbthe other tool to use to help pick reviews is reviewday21:13
*** hartsocks has joined #openstack-meeting21:13
russellbhttp://status.openstack.org/reviews/21:13
russellbthat helps prioritize things based on other criteria ... test results, bug/blueprint priority21:13
russellbso basically, using one of these tools instead of going after low hanging fruit will help smooth things out21:14
jog0russellb: can we get that to personalize?21:14
*** tpatil has quit IRC21:14
russellbit's all open source :)21:14
russellbbut reviewday, not right now21:14
russellbnext-review is personalized21:14
*** zzs has joined #openstack-meeting21:14
russellbbased on what you've already commented on and such21:14
russellbhttps://github.com/dolph/next-review21:15
russellbfeel free to hack on it ... i submitted some tweaks today21:15
*** sdake_ has joined #openstack-meeting21:15
*** sdake_ has quit IRC21:15
*** sdake_ has joined #openstack-meeting21:15
jog0sounds good, I will redirect my rantings to the ML as this isn't nova only21:15
russellbk :-)21:15
russellbbut yeah, i'm all for improvement in this area21:15
russellbi ended up going on quite the stats kick this week ...21:15
cyeohI think it would help if we made a concious effort to do extra review effort about 2 weeks out from H2. To help reduce the last minute rush21:16
russellbbecause it was killing me not having good data on how well we were keeping up with reviews21:16
russellbcyeoh: +121:16
russellbwith all that said ... the review burden for nova vs other projects is *considerably* higher, so kudos for at least doing as well as we have :)21:16
russellbbut more to do ...21:17
russellbalright, let's jump to subteam reports21:17
russellb#topic sub-team reports21:17
*** openstack changes topic to "sub-team reports (Meeting topic: nova)"21:17
russellbwho's here to give a report?  raise hand and i'll call on you to go21:17
driptondb21:17
n0anoscheduler21:17
devanandabaremetal21:17
russellbdripton: alright, you're up21:17
*** kmartin has joined #openstack-meeting21:17
driptondb meeting failed to happen today.  But we got a bunch of good commits in this week.21:18
driptonboris's db-improve-archving commits all went in21:18
russellbyeah, db-improve-archiving got finished up21:18
harlowjataskflow21:18
russellb:)21:18
driptonand Roman and Sergei got some extra tests in21:18
russellbgreat21:18
driptonthat's all21:18
russellbkthx!21:19
russellbn0ano: scheduler!21:19
n0anogood discussion on whole host allocation (allocating all of a host to one VM, not bare metal but related a little)21:19
n0anoexpect to see more on that in the future21:19
russellbcool21:19
n0anono one appeared to talk about host directory service, I'm still curious on what exactly that is21:19
n0anothat was pretty much it for this week, as always, check the logs for details.21:20
russellbcool thanks21:20
russellbdevananda: baremetal / ironic!21:20
devanandapasting a bunch (i actually prepraed something!)21:20
devanandatwo open-critical bugs in baremetal, both waiting for reviews:21:21
devananda#link https://bugs.launchpad.net/nova/+bug/117809221:21
uvirtbotLaunchpad bug 1178092 in nova "second boot during baremetal deploy does not configure netboot : will hang unless the machine attempts PXE automatically" [Critical,In progress]21:21
devananda#link https://bugs.launchpad.net/nova/+bug/118017821:21
uvirtbotLaunchpad bug 1180178 in nova "Instance IP addresses are re-used even when previous instance could not be powered off" [Critical,In progress]21:21
devanandaSeveral bugs may be related / consolidated into this one:21:21
devananda#link https://bugs.launchpad.net/nova/+bug/118444521:21
russellbshould target them against havana-221:21
uvirtbotLaunchpad bug 1184445 in tripleo "deploy / delete fragility" [High,Triaged]21:21
devanandak, will target :)21:21
devanandaIronic is continuing to move forward. More folks are welcome, we've been discussing how to better split up the work21:22
devanandaand we have an API spec now \o/21:22
russellbgetting reasonable amount of help/participation?21:22
devanandaredhat's contributed 2 guys to the API so that is moving well21:22
russellboh, cool, i should have known that, lol.21:22
devanandaand we (HP) are mostly taking the internal bits21:23
devanandathere's some work refactoring nova/cinder's glance-client and image manipulation21:23
devanandainto oslo21:23
devanandabeing tracked here21:23
devananda#link https://blueprints.launchpad.net/ironic/+spec/image-tools21:23
devanandathat's about it!21:23
russellbcool, sounds like lots of good activity and progress!21:24
russellbharlowja: taskflow!21:24
harlowjayo yo!21:24
*** sandywalsh has joined #openstack-meeting21:24
harlowjathanks to devananda21:25
harlowja"Taskflow is continuing to move forward. More folks are welcome, we've been discussing how to better split up the work."21:25
harlowja:-P21:25
devanandahehe21:25
harlowjahaha, just continuing onwards, db & distributed backend getting done by a couple rackspace folks,21:25
harlowjamore testing, stackforge nearly there21:25
harlowjafiguring out new use-cases in ironic and nova, and seeing how taskflow can help there21:26
harlowja*and cinder*21:26
harlowjamore people getting involved with different backends21:26
harlowjaso all good21:26
harlowjathats about its :) more nova folks always welcome ;)21:27
russellbcool stuff, and meeting is just before this one if anyone is interested21:27
harlowjayuppers21:27
russellbannnnnnnnd... hartsocks: vmware!21:27
hartsockshey21:27
*** glikson has quit IRC21:27
hartsocks#link http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-05-29-17.01.html21:27
hartsocksSo we've got 2 blueprints targeted for H-221:27
hartsocksAnd we have about 4 "critical" bugs/patches we did not make for H1 that will get pushed to H2 now.21:28
*** jmh_ has quit IRC21:28
russellbbtw, on reviews on that driver ...21:28
hartsocksWe're also getting more blueprints in from other folks out side of the regular crowd.21:28
*** Trozz has joined #openstack-meeting21:28
russellbi mostly don't touch it if i see you haven't touched it yet21:28
russellbwould like to see your +1 first21:29
hartsocksThanks.21:29
hartsocksI am humbled by your trust21:29
russellbif there's others I should consider the "maintainer" like that, let me know21:29
* hartsocks bows21:29
russellbdoesn't mean I blindly +2 after that :-p21:29
*** jlucci has joined #openstack-meeting21:29
hartsocksGood to know. :-)21:29
russellbjust saying there was at least one waiting over a week, but i hadn't reviewed because i was hoping you would first21:29
*** markvan has quit IRC21:29
hartsocksI will try and cycle through the reviews faster.21:30
russellball good ... just letting you know how i think, i guess21:30
russellband the one i was thinking about you have reviewed already now21:30
hartsocksI've also worked through the bug lists and prioritized most stuff.21:31
*** sdake_ has quit IRC21:31
russellbtarget bugs to havana-2 if you want to try to get them in21:31
russellbawesome, much appreciated21:31
*** elo has joined #openstack-meeting21:31
hartsocksSo, VMware stuff is starting to pick up steam here.21:31
hartsocksI should have a few new developers coming on line in the next few weeks from our VMware team too. (just BTW)21:32
russellbcool, good to hear21:32
russellbi like maintained code :)21:32
hartsocksyep.21:32
russellbanything else?21:32
hartsocksThat'll cover it. :-)21:32
russellbthanks!21:32
russellb#topic open discussion21:32
*** openstack changes topic to "open discussion (Meeting topic: nova)"21:32
russellbany misc topics?21:33
*** jasondotstar has quit IRC21:33
cyeohyep!21:33
*** sdake_ has joined #openstack-meeting21:33
*** sdake_ has joined #openstack-meeting21:33
cyeohI'd like to talk about trying something to make reviewing all the ported v3 API extension changesets about to come through easier21:33
russellbcool, have an idea?21:34
cyeohat the moment the changesets look pretty big because although a lot of the code is the same as in V2 its a new file and so the diff looks large21:34
*** lcheng has joined #openstack-meeting21:34
cyeohso what I'd like to do for the remaining extensions in contrib (and there are about 60!) is to do a giant copy of paste from contrib to plugins/v321:35
*** shardy is now known as shardy_afk21:35
*** lpabon has quit IRC21:35
russellbso how long should we be supporting v2?21:35
cyeohthe code would essentially be "dead" in there. as neither the v2 nor v3 extension code will attempt to load them21:35
* russellb is thinking about the cost/benefit to any refactoring to cut down on copy/paste21:35
cyeohrussellb: I guess for at least one full cycle21:35
dansmithcyeoh: so one big copy/paste that doesn't work,21:35
dansmithcyeoh: then a bunch of small patches with just deltas for v3-ness?21:36
cyeohdansmith: yes21:36
dansmithand we just "ignore" the big ugly first one?21:36
russellbso ... if we "completed" v3 in havana ... could have it removed in I, ok ...21:36
russellbthat's actually pretty clever, heh21:36
dansmithcyeoh: that's an interesting appraoch21:36
cyeohyep and similarly for the tests too because they have a similar review issue21:36
russellbmakes the reviews sound much more pleasant (after that)21:36
russellbthough I would feel so so so dirty approving that first one21:36
cyeohyea I realise its rather ugly and will probably need some updates when people update the V221:37
dansmithcyeoh: could we try it with a couple of extensions first?21:37
dansmithlike, get three patches up, the big one, plus two conversions on top of it so we can see?21:37
cyeohdansmith: sure21:37
russellband if that works21:37
dansmithI'm +1 for that21:37
russellbcould do 1 at a time21:37
russellbso each conversion is just 2 changes21:37
dansmithwell,21:37
russellb1 copy/paste that isn't used yet ... another that converts it21:37
russellbwould help prevent things from getting too out of sync21:38
dansmithwe could do that too, I guess21:38
dansmithyeah21:38
dansmithand we rubber stamp the first in each pair, if we approve the second?21:38
comstudI'd be +1 on that approach21:38
russellband also doesn't leave dead code in the tree for longer than <gate job time> or whatever21:38
cyeohyep, I'm happy to do that too.21:38
dansmithcool21:38
dansmiththen I can feel like less of a slackass21:38
russellb:)21:38
*** cp16net is now known as cp16net|away21:38
cyeohI'm just aware that 60 or so reviews in the next 6 weeks is actually adding a reasonable amount of review load so want to make it as easy as possible :-)21:39
russellbsame here ... i didn't start looking at v3 patches until it was too late for havana-1 ... sorry21:39
russellbway too many reviews out there21:39
russellb(or so I feel)21:39
russellbcyeoh: much appreciated21:39
cyeohheh np. They're starting to flow in now :-)21:39
russellbcyeoh: let's see how it goes on the first couple21:39
russellband then adjust the approach if needed21:39
*** Matty has quit IRC21:39
russellbit sounds like it'll make it pretty easy to review these21:39
jog0cyeoh: do you have a doc on the high level changes in V3 that dives into the details to? so we know what to look for during a reviwe21:40
cyeohjog0: Mauro posted a link to a wiki page a couple of weeks ago. I'll have to go dig it up21:40
russellbhttps://wiki.openstack.org/wiki/NovaV3API21:41
russellb?21:41
russellbthat's just from google, heh21:41
*** nsavin has joined #openstack-meeting21:41
melwittI found this in ML: https://etherpad.openstack.org/api-v3-review-guide21:41
russellbmelwitt: nice21:41
cyeohmelwitt: yea, thats it. We need to add a few other things.21:42
*** cp16net|away is now known as cp16net21:42
cyeoheverything that is intentionally changed (like return codes) should be explicitly stated in the changeset comment, but would also help to have a separate list of things we're meant to consider during the port (like json/xml inconsistencies for example)21:43
jog0cyeoh: ahh21:43
cyeohgiven the number of different blueprints which can apply to the same extension there may be multiple passes though.21:43
russellbcyeoh: random thing ... there is a versions.py in the api code that lists the APIs we're serving up ... v3 isn't in there yet, will need to be added, and have its status set to something that indicates its a WIP21:44
cyeohI don't want anyone to consider the v3 API to be in anyway "fixed" until late in the H cycle21:45
russellbyep21:45
russellbso not even making it discoverable (even if marked as WIP) until later probably isn't bad21:45
cyeohrussellb: yea I have been holding off on the versions stuff because of the discussion around discoverability21:45
russellbis v3 configurable?21:45
russellbas in, can it be disabled?21:45
russellbshould do that too if not already21:45
russellband maybe even have it disabled by default until it's "done"21:45
cyeohhrm do you want a config option because you can just remove it from the paste file21:45
*** ecarlin has joined #openstack-meeting21:46
russellbyeah, a config option i think ... because ideally we don't want anyone to have to edit the paste files21:46
cyeohfrom /etc/nova/api-past.ini21:46
russellbpaste files are more like code than config IMO21:46
russellbglance had (has?) a similar option for the v2 API21:46
cyeohok. I'll add something to disable it by default for now21:46
russellbcool21:46
russellbi *usually* don't like having to develop a "feature" in tree like this ... but this is so massive, don't see any other way21:47
russellba well justified exception, i think21:47
cyeohyea keeping in sync with V2 changes is a bit of work as it is.21:48
* russellb nods21:48
*** lloydde has joined #openstack-meeting21:48
russellbso, we have a plan then?21:48
russellbfor now at least?  :)21:48
cyeohyep, thanks! That's it from me :-)21:48
russellbcool!21:49
russellbanything else?21:49
jog0cyeoh: will you be addressing http://www.mail-archive.com/openstack@lists.launchpad.net/msg23320.html in v3? are those the JSON/XML issues you mentioned?21:49
cyeohjog0: that's the kind of thing we need to catch. If you could file a bug report or add an entry to the blueprint for those that you are aware of, that would really help.21:51
*** enikanorov-w has quit IRC21:52
jog0cyeoh: I will add an entry in the BP, sadly I am not aware of how often/where this happens21:52
cyeohthere are a few cases where JSON does one thing and xml does something different  too21:52
cyeohjog0: yea, ivanzhu is doing a scan to try to pick up as many as possible, but its an easy enough thing to miss21:53
jog0cyeoh: which blueprint would this  go under  https://blueprints.launchpad.net/nova/+spec/v3-api-inconsistencies ?21:53
cyeohjog0: yea, that will do21:53
*** enikanorov-w has joined #openstack-meeting21:53
russellbalright, thanks everyone ... more discussion in #openstack-nova is welcome as always21:54
russellbjog0: cyeoh: let's just continue over there if needed21:54
russellbbye!21:54
russellb#endmeeting21:54
*** openstack changes topic to "OpenStack meetings"21:54
openstackMeeting ended Thu May 30 21:54:41 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-05-30-21.01.html21:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-05-30-21.01.txt21:54
openstackLog:            http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-05-30-21.01.log.html21:54
*** markmcclain has joined #openstack-meeting21:55
*** joel-coffman has quit IRC21:55
*** mkollaro has joined #openstack-meeting21:58
*** markmcclain has quit IRC21:59
*** markwash has quit IRC21:59
*** IlyaE has quit IRC22:03
*** markwash has joined #openstack-meeting22:03
*** Mr__T has left #openstack-meeting22:04
*** colinmcnamara has quit IRC22:04
*** otherwiseguy has quit IRC22:07
*** ecarlin has quit IRC22:07
*** ivasev has quit IRC22:08
*** sdake_ has quit IRC22:08
*** geekinutah has left #openstack-meeting22:11
*** ryanpetrello has quit IRC22:11
*** maurosr- is now known as maurosr22:11
*** mkollaro has quit IRC22:13
*** ecarlin has joined #openstack-meeting22:18
*** changbl has quit IRC22:26
*** novas0x2a|laptop has quit IRC22:29
*** torgomatic has quit IRC22:32
*** novas0x2a|laptop has joined #openstack-meeting22:33
*** lloydde has quit IRC22:33
*** salv-orlando has joined #openstack-meeting22:33
*** bpb has quit IRC22:37
*** vipuls is now known as vipuls|away22:40
*** novas0x2a|laptop has quit IRC22:41
*** jcoufal has quit IRC22:41
*** novas0x2a|laptop has joined #openstack-meeting22:41
*** jrodom has joined #openstack-meeting22:44
*** lbragstad has quit IRC22:45
*** esker has quit IRC22:48
*** gongysh has joined #openstack-meeting22:48
*** markwash has quit IRC22:48
*** gyee has quit IRC22:53
*** vipuls|away is now known as vipuls22:53
*** torgomatic has joined #openstack-meeting22:55
*** fnaval has quit IRC22:56
*** zzs has left #openstack-meeting22:59
*** matiu has quit IRC23:06
*** Trozz has quit IRC23:07
*** kebray has quit IRC23:07
*** dolphm has joined #openstack-meeting23:09
*** alexheneveld has quit IRC23:17
*** eharney has joined #openstack-meeting23:19
*** ryanpetrello has joined #openstack-meeting23:19
*** melwitt has left #openstack-meeting23:21
*** lloydde has joined #openstack-meeting23:23
*** haomaiwang has quit IRC23:23
*** dolphm has quit IRC23:24
*** stevemar has quit IRC23:24
*** mrodden has quit IRC23:26
*** stevemar has joined #openstack-meeting23:26
*** stevemar has quit IRC23:28
*** stevemar2 has joined #openstack-meeting23:28
*** fnaval has joined #openstack-meeting23:29
*** anniec has quit IRC23:30
*** jlucci has quit IRC23:31
*** ryanpetrello has quit IRC23:35
*** lastidiot has quit IRC23:36
*** hemna has quit IRC23:36
*** torandu has left #openstack-meeting23:40
*** changbl has joined #openstack-meeting23:44
*** krtaylor has quit IRC23:46
*** cp16net is now known as cp16net|away23:47
*** dolphm has joined #openstack-meeting23:47
*** jrodom_ has joined #openstack-meeting23:47
*** jrodom_ has quit IRC23:49
*** vipuls is now known as vipul23:51
*** jrodom has quit IRC23:51
*** anniec has joined #openstack-meeting23:51
*** dolphm has quit IRC23:54
*** ecarlin has quit IRC23:54
*** noslzzp has joined #openstack-meeting23:54
*** MarkAtwood has quit IRC23:55
*** adrian_otto2 has joined #openstack-meeting23:55
*** adrian_otto has quit IRC23:57
*** ryanpetrello has joined #openstack-meeting23:57
*** tanisdl has quit IRC23:58

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