Thursday, 2013-08-22

*** sarob_ has joined #openstack-meeting00:01
*** nati_uen_ has joined #openstack-meeting00:02
*** sarob has quit IRC00:04
*** nati_ueno has quit IRC00:05
*** michchap has joined #openstack-meeting00:05
*** hemna is now known as hemnafk00:06
*** markpeek has joined #openstack-meeting00:07
*** MarkAtwood has quit IRC00:12
*** jhenner has quit IRC00:17
*** vuil has quit IRC00:23
*** alexpilotti has quit IRC00:23
*** changbl has joined #openstack-meeting00:28
*** otherwiseguy has joined #openstack-meeting00:34
*** chmouel has quit IRC00:36
*** iccha has quit IRC00:36
*** westmaas has quit IRC00:36
*** iccha has joined #openstack-meeting00:36
*** westmaas has joined #openstack-meeting00:36
*** chmouel has joined #openstack-meeting00:37
*** GheRivero has quit IRC00:37
*** dtroyer has quit IRC00:37
*** juice has quit IRC00:37
*** GheRivero has joined #openstack-meeting00:37
*** dtroyer has joined #openstack-meeting00:37
*** jpeeler has quit IRC00:37
*** juice has joined #openstack-meeting00:38
*** jpeeler has joined #openstack-meeting00:38
*** Mandell has quit IRC00:40
*** herndon has quit IRC00:45
*** fnaval_ has joined #openstack-meeting00:47
*** fnaval_ has quit IRC00:47
*** fnaval_ has joined #openstack-meeting00:47
*** haomaiwang has joined #openstack-meeting00:48
*** spzala has joined #openstack-meeting00:50
*** sarob_ has quit IRC00:51
*** alexb_ has quit IRC00:51
*** schwicht has quit IRC00:52
*** elo has joined #openstack-meeting00:55
*** nati_uen_ has quit IRC00:55
*** jlucci has quit IRC00:56
*** nati_ueno has joined #openstack-meeting00:57
*** noslzzp has joined #openstack-meeting00:58
*** patelna has quit IRC01:04
*** feleouet has quit IRC01:06
*** reed has quit IRC01:06
*** nati_ueno has quit IRC01:07
*** markmcclain has quit IRC01:07
*** feleouet has joined #openstack-meeting01:09
*** haomaiwang has quit IRC01:13
*** haomaiwang has joined #openstack-meeting01:14
*** alexb_ has joined #openstack-meeting01:14
*** salv-orlando has quit IRC01:17
*** fifieldt_ has joined #openstack-meeting01:20
*** fifieldt has quit IRC01:20
*** smurugesan has quit IRC01:22
*** rods has quit IRC01:23
*** salv-orlando has joined #openstack-meeting01:23
*** sjing has joined #openstack-meeting01:24
*** comay has quit IRC01:28
*** Tross has quit IRC01:29
*** danwent has quit IRC01:34
*** gyee has quit IRC01:35
*** gongysh has quit IRC01:37
*** rwsu has quit IRC01:40
*** martine has joined #openstack-meeting01:40
*** martine is now known as Guest8101601:41
*** dhellmann is now known as dhellmann_01:48
*** gongysh has joined #openstack-meeting01:48
*** vkmc has quit IRC01:48
*** Tross has joined #openstack-meeting01:51
*** funzo has quit IRC01:51
*** esker has joined #openstack-meeting01:52
*** otherwiseguy has quit IRC01:57
*** yaguang has joined #openstack-meeting02:02
*** egallen has quit IRC02:03
*** Guest81016 has quit IRC02:16
*** Tross has quit IRC02:20
*** esker has quit IRC02:22
*** martine_ has joined #openstack-meeting02:23
*** rwsu has joined #openstack-meeting02:25
*** novas0x2a|laptop has quit IRC02:32
*** shang has joined #openstack-meeting02:35
*** stevemar has joined #openstack-meeting02:36
*** elo has quit IRC02:36
*** ftcjeff has joined #openstack-meeting02:38
*** esker has joined #openstack-meeting02:38
*** asalkeld is now known as asalkeld_lunch02:48
*** esker has quit IRC02:58
*** esker has joined #openstack-meeting02:59
*** markmcclain has joined #openstack-meeting03:00
*** esker has quit IRC03:03
*** yuan has quit IRC03:04
*** lpabon has quit IRC03:06
*** shang has quit IRC03:08
*** gongysh has quit IRC03:11
*** dcramer_ has joined #openstack-meeting03:16
*** blamar has quit IRC03:17
*** Tross has joined #openstack-meeting03:28
*** stevemar has quit IRC03:30
*** noslzzp has quit IRC03:37
*** feleouet has quit IRC03:40
*** yaguang has quit IRC03:42
*** nati_ueno has joined #openstack-meeting03:42
*** feleouet has joined #openstack-meeting03:44
*** nati_ueno has quit IRC03:44
*** Mandell has joined #openstack-meeting03:45
*** yaguang has joined #openstack-meeting03:45
*** gongysh has joined #openstack-meeting03:48
*** asalkeld_lunch is now known as asalkeld03:52
*** HenryG_ has joined #openstack-meeting03:54
*** cyeoh has quit IRC03:54
*** lexinator has joined #openstack-meeting03:54
*** soren has quit IRC03:54
*** soren has joined #openstack-meeting03:55
*** cyeoh has joined #openstack-meeting03:55
*** stevemar has joined #openstack-meeting03:56
*** HenryG has quit IRC03:57
*** anteaya has quit IRC04:03
*** eharney has joined #openstack-meeting04:03
*** danwent has joined #openstack-meeting04:07
*** thingee has left #openstack-meeting04:08
*** alexb_ has quit IRC04:13
*** dklyle has joined #openstack-meeting04:23
*** dtroyer has quit IRC04:23
*** dtroyer has joined #openstack-meeting04:23
*** david-lyle has quit IRC04:23
*** _cerberus_ has quit IRC04:23
*** samalba has quit IRC04:23
*** comstud has quit IRC04:23
*** mberwanger has joined #openstack-meeting04:24
*** comstud has joined #openstack-meeting04:25
*** _cerberus_ has joined #openstack-meeting04:26
*** samalba has joined #openstack-meeting04:27
*** hemna_ has quit IRC04:30
*** markmcclain has quit IRC04:33
*** markmcclain has joined #openstack-meeting04:33
*** MarkAtwood has joined #openstack-meeting04:35
*** boris-42 has joined #openstack-meeting04:36
*** eharney has quit IRC04:37
*** spzala has quit IRC04:39
*** rongze has quit IRC04:47
*** ftcjeff has quit IRC04:49
*** SergeyLukjanov has joined #openstack-meeting04:53
*** Tross has quit IRC04:55
*** alexb_ has joined #openstack-meeting04:55
*** nati_ueno has joined #openstack-meeting04:55
*** martine_ has quit IRC05:00
*** stevemar has quit IRC05:02
*** jhenner has joined #openstack-meeting05:05
*** danwent has quit IRC05:05
*** Tross has joined #openstack-meeting05:07
*** sacharya has quit IRC05:08
*** jhenner has quit IRC05:10
*** rongze has joined #openstack-meeting05:12
*** rongze_ has joined #openstack-meeting05:13
*** mberwanger has quit IRC05:16
*** rongze has quit IRC05:16
*** dcramer_ has quit IRC05:17
*** scott_da has quit IRC05:18
*** scottda has quit IRC05:18
*** primeministerp has quit IRC05:22
*** garyk has quit IRC05:24
*** primeministerp has joined #openstack-meeting05:29
*** gongysh has quit IRC05:30
*** markpeek has quit IRC05:32
*** scottda has joined #openstack-meeting05:32
*** scott_da has joined #openstack-meeting05:33
*** mrunge has joined #openstack-meeting05:34
*** vuil has joined #openstack-meeting05:35
*** gongysh has joined #openstack-meeting05:35
*** Mandell has quit IRC05:37
*** egallen has joined #openstack-meeting05:40
*** morganfainberg is now known as morganfainberg|a05:56
*** egallen has quit IRC05:58
*** dmakogon_ has joined #openstack-meeting05:58
*** feleouet has quit IRC05:59
*** feleouet has joined #openstack-meeting06:02
*** lexinator has quit IRC06:03
*** salv-orlando has quit IRC06:05
*** Mandell_ has joined #openstack-meeting06:06
*** jcoufal has joined #openstack-meeting06:07
*** garyk has joined #openstack-meeting06:07
*** MarkAtwood has quit IRC06:12
*** morganfainberg|a is now known as morganfainberg06:14
*** SergeyLukjanov has quit IRC06:15
*** dguitarbite has quit IRC06:21
*** HenryG_ has quit IRC06:30
*** mikal has quit IRC06:30
*** inkerra has quit IRC06:31
*** mikal has joined #openstack-meeting06:32
*** lexinator has joined #openstack-meeting06:33
*** lexinator has quit IRC06:40
*** pnavarro has joined #openstack-meeting06:44
*** ndipanov has joined #openstack-meeting06:47
*** gongysh has quit IRC06:50
*** sjing has quit IRC06:54
*** sjing has joined #openstack-meeting06:55
*** rongze has joined #openstack-meeting06:56
*** nati_ueno has quit IRC06:58
*** rongze_ has quit IRC06:58
*** doron_afk has joined #openstack-meeting07:01
*** shang has joined #openstack-meeting07:04
*** SergeyLukjanov has joined #openstack-meeting07:05
*** gongysh has joined #openstack-meeting07:06
*** egallen has joined #openstack-meeting07:09
*** markmcclain has quit IRC07:18
*** rongze has quit IRC07:29
*** rongze has joined #openstack-meeting07:29
*** vuil has quit IRC07:30
*** tkammer has joined #openstack-meeting07:33
*** lexinator has joined #openstack-meeting07:38
*** rongze_ has joined #openstack-meeting07:40
*** SergeyLukjanov has quit IRC07:40
*** rongze has quit IRC07:41
*** lexinator has quit IRC07:43
*** johnthetubaguy has joined #openstack-meeting07:45
*** johnthetubaguy1 has joined #openstack-meeting07:48
*** johnthetubaguy has quit IRC07:49
*** afazekas has joined #openstack-meeting07:52
*** egallen has quit IRC07:56
*** boris-42 has quit IRC07:58
*** johnthetubaguy1 is now known as johnthetubaguy08:05
*** _ozstacker_ has quit IRC08:10
*** ozstacker has joined #openstack-meeting08:10
*** feleouet has quit IRC08:13
*** fifieldt_ has quit IRC08:15
*** jaimegil has joined #openstack-meeting08:16
*** feleouet has joined #openstack-meeting08:17
*** sushils has quit IRC08:17
*** michchap_ has joined #openstack-meeting08:25
*** pnavarro has quit IRC08:26
*** dmakogon_ has quit IRC08:26
*** henrynash has quit IRC08:27
*** michchap has quit IRC08:27
*** jtomasek has joined #openstack-meeting08:27
*** ruhe has joined #openstack-meeting08:30
*** jhenner has joined #openstack-meeting08:33
*** lexinator has joined #openstack-meeting08:39
*** doron_afk is now known as doron08:39
*** sjing has quit IRC08:41
*** lexinator has quit IRC08:43
*** doude has left #openstack-meeting08:43
*** doron is now known as doron_afk08:47
*** kbs1 has quit IRC08:48
*** kbs has joined #openstack-meeting08:49
*** kbs1 has joined #openstack-meeting08:51
*** kbs1 has quit IRC08:52
*** kbs has quit IRC08:53
*** bgorski has joined #openstack-meeting08:59
*** xBsd has joined #openstack-meeting09:02
*** Kharec has quit IRC09:04
*** Tross1 has joined #openstack-meeting09:07
*** Tross has quit IRC09:08
*** sushils has joined #openstack-meeting09:09
*** Kharec has joined #openstack-meeting09:09
*** matiu has quit IRC09:17
*** michchap_ has quit IRC09:30
*** boris-42 has joined #openstack-meeting09:37
*** lexinator has joined #openstack-meeting09:39
*** lexinator has quit IRC09:44
*** enikanorov_ has joined #openstack-meeting09:47
*** rongze_ has quit IRC09:55
*** gongysh has quit IRC09:57
*** rongze has joined #openstack-meeting09:57
*** rongze has quit IRC10:05
*** rongze has joined #openstack-meeting10:05
*** afazekas has quit IRC10:07
*** thomasbiege has joined #openstack-meeting10:10
*** gongysh has joined #openstack-meeting10:13
*** ruhe has quit IRC10:15
*** feleouet has quit IRC10:17
*** feleouet has joined #openstack-meeting10:20
*** morganfainberg is now known as morganfainberg|a10:21
*** ruhe has joined #openstack-meeting10:26
*** thomasbiege has quit IRC10:28
*** ruhe has quit IRC10:30
*** thomasbiege has joined #openstack-meeting10:38
*** openstack has joined #openstack-meeting15:12
*** ChanServ sets mode: +o openstack15:12
jeblairjd__: all yours15:13
jd__#startmeeting ceilometer15:13
openstackMeeting started Thu Aug 22 15:13:08 2013 UTC and is due to finish in 60 minutes.  The chair is jd__. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:13
*** openstack changes topic to " (Meeting topic: ceilometer)"15:13
openstackThe meeting name has been set to 'ceilometer'15:13
jd__awesome thansk jeblair15:13
jd__#topic Review Havana-3 milestone15:13
*** openstack changes topic to "Review Havana-3 milestone (Meeting topic: ceilometer)"15:13
thomasmo/ again =]15:13
dragondmWhee :>15:13
jd__so there's only 2 weeks left to propose your patches15:13
*** reed has joined #openstack-meeting15:13
jd__and seeing how long and hard it is to get patches merged, you shouldn't wait for last minute clearly15:14
jd__we're in good shape I think now, eglynn's coming with some patches as soon as it comes back from vacation15:14
jd__terriyu made terrible progress on her blueprint15:14
jd__terrible as in awesome15:15
jd__(not sure that was clear? :)15:15
jd__sorry, french-ism15:15
terriyuI hope that's not a joke on my name :)15:15
*** obondarev has joined #openstack-meeting15:15
jd__haha, no I didn't notice15:15
jd__well, and the other blueprint are either low or needing code reviews15:15
terriyuyes, I'm working on the group by API blueprint15:16
jd__we have a long patch queue right now, it'd be good to have more review btw15:16
terriyuI'll try to keep the blueprint up-to-date15:16
terriyuso far I wrote the storage tests and jd did the SQL Alchemy implementation15:16
jd__and terriyu's patches are a good start for review indeed :)15:16
terriyuI just did the MongoDB implementation15:16
gordcwill start reviewing again now that i got my patch passing tests15:16
*** markvan has joined #openstack-meeting15:17
*** ruhe has quit IRC15:17
terriyuso all that's left is the API implementation15:17
terriyumight need your guys help on understanding the API15:17
llu-laptopI'm supposed to have more time for reviewing next week, since not many nova guys are reviewing our patches there. :(15:18
jd__no problem terriyu15:19
*** jmontemayor has joined #openstack-meeting15:19
jd__llu-laptop: cool, somehow15:19
gordcllu-laptop: our review page is pretty good once you look at nova's15:19
* dragondm will contribute +1's ;->15:20
herndonbut no -1's right? :p15:20
llu-laptopgordc: I just counted nova's reivew page, there are more than 400 pendings15:20
dragondmheh those too, as needed.15:20
gordcllu-laptop: another project branched off nova?15:20
*** tanisdl has quit IRC15:21
dragondmnova's sortof an amoeba, keeps dividing.15:21
dragondmbut gets bigger again afterword :>15:21
*** tanisdl has joined #openstack-meeting15:21
* sileht participes for the first time to the openstack freeze, the zuul queue and the reviews numbers is amazing15:22
*** complexmind has joined #openstack-meeting15:22
jd__#topic Open discussion15:22
*** openstack changes topic to "Open discussion (Meeting topic: ceilometer)"15:22
*** thomasbiege has quit IRC15:22
llu-laptopjd__: about the hosts configuration in the pipeline.yaml in patch #link
jd__yes, I didn't think it through yet15:23
*** lpabon has joined #openstack-meeting15:24
*** Nate1 has left #openstack-meeting15:24
*** thomasbiege has joined #openstack-meeting15:24
*** hemna has joined #openstack-meeting15:24
jd__I think it's on the good way but I don't like it as it is, I'd like something more generic if possible15:24
jd__and if I can't think about something, having another YAML file would be an option I guess15:24
llu-laptopsince those hosts configuration is only used by hardware agent, and is kind of independent of pollsters, i don't know how to put it into pipeline.yaml more nicely.15:24
llu-laptopI'm ok with another yaml file, it was my first thought.15:25
*** nwidell has quit IRC15:25
*** lpabon has quit IRC15:25
silehtllu-laptop, jd__ I prefer a other file too15:25
gordcllu-laptop: is there a list of hardware metrics that we are targeting? i have some ppl interested in hardware metering15:25
*** lpabon has joined #openstack-meeting15:25
*** matiu has joined #openstack-meeting15:26
*** matiu has joined #openstack-meeting15:26
llu-laptopI'm doing the upstream work based on the code Toni implemented, currently there are only a few metrics there, e.g. cpu utilizations, memory, disk, net, etc.15:27
gordcllu-laptop: ok, so whatever you have so far and we'll add stuff later if needed.15:28
*** matiu has quit IRC15:28
*** hemna has quit IRC15:29
jd__llu-laptop: what we may need is a new filter in pipeline for 'resource' so you can request some meter only for a particular resources15:29
*** hemna has joined #openstack-meeting15:29
jd__llu-laptop: that'd allow to use it to define which meter you want for which hosts15:29
*** jdurgin1 has joined #openstack-meeting15:29
*** haomaiwang has quit IRC15:29
jd__llu-laptop: now, for the inspectors to use for each host, I don't know how to / if we can put that into the pipeline15:29
*** matiu has joined #openstack-meeting15:29
*** matiu has joined #openstack-meeting15:30
*** haomaiwang has joined #openstack-meeting15:30
jd__llu-laptop: ah we could use an URL scheme for resources indicating the inspector maybe?15:30
*** ruhe has joined #openstack-meeting15:30
jd__llu-laptop: like I want the 'cpu' meter on resources 'snmp://foobar'15:30
* jd__ throws ideas15:30
*** vijendar has quit IRC15:31
*** matiu has quit IRC15:31
llu-laptopjd__: so you're saying adding parameters to the meter part of the pipeline?15:32
*** thomasbiege has quit IRC15:32
*** matiu has joined #openstack-meeting15:33
*** matiu has joined #openstack-meeting15:33
jd__llu-laptop: 'resources' could be at the same level as 'meters'15:33
*** lexinator has quit IRC15:33
*** haomaiwa_ has joined #openstack-meeting15:34
*** rods has quit IRC15:35
llu-laptopjd__: sorry, I don't catch what your mean by defining 'resources', what does it used for?15:35
jd__llu-laptop: indicating the host you want to poll for via, e.g. snmp15:35
*** markwash has quit IRC15:36
*** haomaiwang has quit IRC15:37
jd__ok I think I'll close the meeting if nobody has anything to say15:39
llu-laptopjd__: so does this mean we coudl use only one YAML file? But this may requires change the PublisherContext.15:39
jd__we can continue with llu-laptop on #openstack-metering15:39
jd__llu-laptop: yes that would allow us to have one file indeed15:39
llu-laptopjd__: ok, let's continue on ceilometer channel.15:40
*** openstack changes topic to "OpenStack Meetings ||"15:40
openstackMeeting ended Thu Aug 22 15:40:32 2013 UTC.  Information about MeetBot at . (v 0.1.4)15:40
openstackMinutes (text):
jd__thanks guys :)15:40
*** gyee has joined #openstack-meeting15:42
*** thomasm has left #openstack-meeting15:42
*** adrian_otto has joined #openstack-meeting15:43
*** gordc has left #openstack-meeting15:44
*** maksimov has quit IRC15:45
*** topol has quit IRC15:47
*** jlucci has quit IRC15:48
*** nwidell has joined #openstack-meeting15:48
*** whenry has quit IRC15:49
*** jlucci has joined #openstack-meeting15:49
*** lexinator has joined #openstack-meeting15:52
*** bdpayne has joined #openstack-meeting15:58
*** kebray has joined #openstack-meeting16:01
*** llu-laptop has quit IRC16:02
*** Mike656 has joined #openstack-meeting16:02
*** martine_ has quit IRC16:05
*** nwidell has quit IRC16:05
*** apioli has joined #openstack-meeting16:07
*** dkranz has quit IRC16:07
*** kgriffs has joined #openstack-meeting16:07
kgriffsPython3 meeting going on today?16:09
*** vijendar has joined #openstack-meeting16:09
*** zbitter has joined #openstack-meeting16:09
*** cppcabrera has joined #openstack-meeting16:10
kgriffsanybody here for the Python3 mtg?16:11
*** Mike656 has quit IRC16:11
*** alexpilotti_ has joined #openstack-meeting16:11
*** dklyle is now known as david-lyle16:11
*** ruhe has quit IRC16:11
*** zul has quit IRC16:12
kgriffshmm, guess not. :p16:12
cppcabreraI'm here for that meeting, kgriffs. :P16:12
kgriffsI was hoping to get a status update, and see what the Marconi team could do to help16:12
* kgriffs gives cppcabrera a McD apple pie16:13
*** zaneb has quit IRC16:13
*** zbitter is now known as zaneb16:13
*** alexpilotti has quit IRC16:13
*** alexpilotti_ is now known as alexpilotti16:13
*** elo has joined #openstack-meeting16:14
*** SergeyLukjanov has quit IRC16:14
*** bpb has joined #openstack-meeting16:17
*** elo has quit IRC16:19
*** ruhe has joined #openstack-meeting16:19
*** ruhe has quit IRC16:19
*** garyk has joined #openstack-meeting16:19
*** dkranz has joined #openstack-meeting16:25
*** kgriffs has left #openstack-meeting16:26
*** SergeyLukjanov has joined #openstack-meeting16:28
*** danwent has quit IRC16:29
*** salv-orlando has joined #openstack-meeting16:31
*** MarkAtwood has quit IRC16:35
*** mrodden has quit IRC16:35
*** zyuan_ has joined #openstack-meeting16:36
*** zyuan_ has left #openstack-meeting16:39
*** alexb_ has joined #openstack-meeting16:39
*** markwash has joined #openstack-meeting16:40
*** zul has joined #openstack-meeting16:41
*** morganfainberg|a is now known as morganfainberg16:44
*** mrodden has joined #openstack-meeting16:49
*** krtaylor has quit IRC16:50
*** lexinator has quit IRC16:50
*** lexinator has joined #openstack-meeting16:54
*** mkollaro has joined #openstack-meeting16:57
*** danwent has joined #openstack-meeting16:57
*** mlavalle has joined #openstack-meeting16:59
*** SergeyLukjanov has quit IRC17:00
mtreinishstartmeeting qa17:00
mtreinish#startmeeting qa17:00
openstackMeeting started Thu Aug 22 17:00:51 2013 UTC and is due to finish in 60 minutes.  The chair is mtreinish. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: qa)"17:00
openstackThe meeting name has been set to 'qa'17:00
mtreinishhi who's around for the meeting?17:01
mlavalleI am17:01
*** dkranz has quit IRC17:01
mtreinishok let's get started then17:01
mtreinishhere's the agenda:17:01
*** dkranz has joined #openstack-meeting17:01
mtreinishSo i'm up first on the agenda17:02
*** nati_ueno has joined #openstack-meeting17:02
mtreinish#topic testr-status17:02
*** openstack changes topic to "testr-status (Meeting topic: qa)"17:02
mtreinishSo I've been working through some of the bugs on parallel tempest17:02
mtreinishwe're in the home stretch17:02
mtreinishright now all that's left are the 3 bugs from last week17:03
mtreinishand neutron doesn't work at all in parallel right now17:03
mtreinishbut once I sort out the neutron fail we might be able to greenlight this17:03
mtreinishif we hit too many random fails we can alway just pull it out and go back to serial17:03
afazekasYes there is many nova-neutron   "race" issue ..17:04
mtreinishbut we've pretty much reached the point where this won't go any further unless we start gating on it17:04
mtreinishafazekas: well right now we don't run with tenant isolation on neutron17:05
mtreinishand also the neutron smoke run hits resource name conflicts and fails17:05
*** morganfainberg is now known as morganfainberg|a17:05
afazekasmtreinish: I would be very surprised if those would be tenant isolation related things .. (may be some of them)17:05
*** otherwiseguy has quit IRC17:05
*** SergeyLukjanov has joined #openstack-meeting17:05
mtreinishafazekas: I don't think the resource conflict is a tenant isolation thing. But we need it for the non neutron specific tests to pass17:06
afazekasmtreinish:  yes17:06
mtreinishok does anyone else have anything else about testr parallel?17:07
mtreinishok then before I move on I was just curious how many people are running with parallel?17:07
mtreinishor at least tried it17:07
afazekasmtreinish: sooner or later I try to split the test to more devstack node, can I add tox entry for that if it is necessary ?17:08
mtreinishafazekas: I'm not following. Split which tests?17:08
*** thomasbiege has joined #openstack-meeting17:08
afazekasAFAIK the subunit is able to distribute the test cases to multiple node,  sooner or later I will try is it working with tempest17:09
dkranzHere. Sorry I was in the wrong channel :(17:09
afazekasI think it will require multiple similar system to be installed17:10
mtreinishoh, yeah that's something we can look into down the road, but for right now we need to concentrate on getting parallel single node working17:10
mtreinishok then does anyone have anything else to add on testr parallel?17:11
*** Anju has joined #openstack-meeting17:12
mtreinishok then moving on.17:12
mtreinish#topic stress test status17:12
*** openstack changes topic to "stress test status (Meeting topic: qa)"17:12
mtreinishmkoderer told me he can't make today's meeting17:12
mtreinishso does anyone else have something they want to bring up about stress tests17:12
mtreinishotherwise we'll move on17:12
*** ericyoung has joined #openstack-meeting17:13
mtreinishok then let's move on17:14
mlavallemtreinish: I want to report on
mtreinish#topic Other blueprint status17:14
*** openstack changes topic to "Other blueprint status (Meeting topic: qa)"17:14
mtreinishmlavalle: ok go ahead17:14
*** nwidell has joined #openstack-meeting17:14
mtreinishwe really should add neutron testing status to the agenda for next week17:14
*** elo has joined #openstack-meeting17:14
mlavallemtreinish: achieving progress. Right now I am working on this bug
uvirtbotLaunchpad bug 1182384 in nova "SecurityGroups Tests : invalid id must be valid uuid " [High,In progress]17:15
afazekas#action Add the neutron status to the next meeting Agenda17:15
mlavallelast night I added a comment to this bug. I would like feedback from the team on that17:15
mlavalleit doesn't have to be in this meeting, but I need it to move ahead17:16
mtreinishmlavalle: ok looking at the bug it's more of the response code differences between nova network and neutron17:16
mtreinishor is there something more too it?17:16
mlavalleno, it is the response codes.17:17
mtreinishmlavalle: ok we can move this on to the qa channel after the meeting because I think there is a more detailed discussion to be had about this17:18
*** alexpilotti has quit IRC17:18
sileht /1717:18
mlavallethat's what I want17:18
mtreinishmlavalle: :)17:18
*** nwidell has quit IRC17:19
mtreinishok is there anything else on neutron?17:19
mlavallenot on my side17:19
mtreinishok then does anyone else have a blueprint they'd like to bring up17:19
*** thomasbiege has quit IRC17:20
*** MarkAtwood has joined #openstack-meeting17:21
mtreinishok let's go to the next topic then17:21
mtreinish#topic critical review17:21
*** openstack changes topic to "critical review (Meeting topic: qa)"17:21
mtreinishDoes anyone have any reviews that they would like to bring up17:21
*** MarkAtwood has quit IRC17:21
*** MarkAtwood has joined #openstack-meeting17:22
*** SergeyLukjanov has quit IRC17:22
dkranzmtreinish: It would be nice to get in17:22
afazekasIn the heat topic I have 317:22
dkranzmtreinish: Heat stuff waiting for +A17:22
*** svarnau has joined #openstack-meeting17:22
dkranzOK, wait for next topic.17:23
mtreinishdkranz: ok I'll take a look after the meeting17:23
mtreinishI really don't have much experience with heat though17:23
afazekas this is good according to the jenkins17:23
afazekas this will run with new job17:23
mtreinishafazekas: that doesn't get run with jenkins right now17:24
mtreinishbecause we exclude the slow tag17:24
afazekasthere is two change set17:24
*** boris-42 has joined #openstack-meeting17:25
dkranzmtreinish: I don't either.17:25
mtreinishafazekas: you pasted the same link as dkranz twice17:25
afazekasthe auto-scaling is not running as it submintted now17:25
afazekassorry copy paste issue :)17:25
mtreinishwell this segways into the next topic, so before that does anyone else have any non-heat related reviews to bring up?17:26
mtreinishok lets move on to the heat topic17:27
mtreinish#topic Heat test merge17:27
*** openstack changes topic to "Heat test merge (Meeting topic: qa)"17:27
mtreinishafazekas: take it away17:27
*** pcm_ has quit IRC17:28
afazekasSo there is 2 very old heat rlated changeset which is not merged since long, and did not get negative response as well17:28
*** venkatesh has joined #openstack-meeting17:29
mtreinishafazekas: those are the 2 you pasted before?17:29
*** morganfainberg|a is now known as morganfainberg17:29
*** svarnau has quit IRC17:29
afazekasand there is tox related change from dkranz17:29
*** svarnau has joined #openstack-meeting17:30
dkranzmtreinish: I am going to mark that last one not WIP.17:30
mtreinishafazekas: well I'd like to see dkranz get in before anything that uses the slow tag17:30
dkranzmtreinish: The issue was where we put the slow heat tests to be recognized .17:30
mtreinishso we can add a nonvoting (at first) slow tag job on the check queue17:30
afazekasdkranz: Imho you should remove the '\.orchestration' from the regexp17:30
dkranzmtreinish: I am going to push all the stuff for the slow heat job tomorrow.17:31
mtreinishdkranz: ok17:31
dkranzafazekas: But then we will get non-heat tests that happen to be marked slow17:31
mtreinishdkranz: do we have any of those?17:31
*** elo has quit IRC17:31
dkranzmtreinish: Not yet, but we don't want the slow heat job to start picking up new stuff by accident.17:32
dkranzmtreinish: I think we should put the slow heat scenario tests in their own subdir of scenario.17:32
*** elo has joined #openstack-meeting17:32
afazekasdkranz: will be on the slow job, I am not sure we want to prevent this in this way. Now non of the other test cases has the slow tag .17:32
*** pcm_ has joined #openstack-meeting17:32
mtreinishwell, I'm just wondering even if we have non slow heat jobs do we really want that to be a separate run17:32
mtreinishsorry, slow non-heat tests17:33
*** markmcclain has quit IRC17:33
afazekasdkranz: the auto-scaling test case not submited into the scenario/orchestration17:33
dkranzmtreinish: It is a problem to have a job that runs all slow tests that happen to show up.17:33
*** thomasbiege has joined #openstack-meeting17:33
dkranzafazekas: I know. I'm suggesting we change that.17:33
dkranzafazekas: sbaker was OK with that.17:33
dkranzafazekas: And then leave the regexp as is.17:34
*** xBsd has quit IRC17:34
dkranzI can't see any harm in that.17:34
mtreinishdkranz: ok, I'm fine with splitting it out as heat specific. We can always revisit the discussion when/if we have a non-heat slow test17:34
afazekasdkranz: for me both cases is ok, I just would like to see some progress17:34
dkranzAnd it dosn't leave bombs for the future.17:34
mtreinishdkranz: the other thing I suggest is that we default it to be parallel17:34
mtreinishI don't think we should add new jobs that aren't parallel17:35
dkranzmtreinish: OK.17:35
dkranzmtreinish: I'm still a slight bit concerned that tests only have to pass once in parallel to become part of the gate.17:35
dkranzmtreinish: But I guess that's where we are at this point.17:35
*** morganfainberg has left #openstack-meeting17:36
mtreinishdkranz: yeah, I mean once we move everything to parallel we'll have 3 runs of parallel17:36
mtreinishbut it's an issue17:36
*** venkatesh has quit IRC17:36
*** jlucci has quit IRC17:36
mtreinishwhich is why I want to get things merged soon(liek end of this week, first thing next week) for parallel17:36
*** morganfainberg has joined #openstack-meeting17:37
dkranzmtreinish: OK, I will change my regexp off of WIP, submit the slow test job stuff, and get sbaker to move the test to orchestration subdir.17:37
mtreinishdkranz: ok sounds good17:37
*** mrunge has quit IRC17:37
afazekasdkranz: I am also concerned about this kind of issues does not gets higher priority
dkranzmtreinish: There is already a slow job in api so it will run17:37
uvirtbotLaunchpad bug 1205344 in nova "mkfs error in test_stamp_pattern" [High,Confirmed]17:37
mtreinishok is there anything else to talk about on this topic?17:38
dkranzmtreinish: Don't think so.17:39
mtreinishok then let's move on17:39
mtreinish#topic Devstack independent tempest usage17:39
*** openstack changes topic to "Devstack independent tempest usage (Meeting topic: qa)"17:39
mtreinishafazekas: this one is yours too17:39
dkranzafazekas: Is this Tal's script?17:39
dkranzafazekas: The topic?17:39
*** svarnau has quit IRC17:39
afazekasLong time ago we discussed would be nice to add something for help use tempest for non-gating, with a not devstack installed openstack17:40
afazekasdkranz: yes17:40
*** svarnau has joined #openstack-meeting17:40
afazekasTal stated a script for helping
afazekasI would like craftily some details how to move forward17:41
tkammers/Tal/tkammer :)17:41
dkranzafazekas: Why did you +1 instead of +2?17:41
afazekasdkranz: I just wanted to discuss it first :)17:42
mtreinishafazekas: so I'm confused by the script it takes a tempest.conf to configure openstack? Isn't that the opposite of what we talked about before?17:42
*** svarnau has quit IRC17:42
afazekasmtreinish: it creates users for testing17:43
afazekasmtreinish: it will get options for more use cases17:43
mtreinishtempest already does that with tenant isolation17:43
afazekasmtreinish: does it in every case now ?17:44
tkammermtreinish, it uses both the tempest.conf file for "default" parameters such as the username/password (and more in the future if needed), and for other stuff it updates that conf file for later use of Tempest itself17:44
mtreinishafazekas: everything but keystone which needs some work17:44
*** bclifford has joined #openstack-meeting17:44
*** vkmc has quit IRC17:45
afazekasmtreinish: the script has options, and can be extended with more automation, or make optional some unwanted behavior17:45
*** SergeyLukjanov has joined #openstack-meeting17:46
mtreinishafazekas: ok, I'll need to take a more detailed look to get a better idea of what it's doing.17:46
afazekasmtreinish: So the question is , is the script in this form  got for merge and extending with futures when it is needed, or it should do little more ?17:46
mtreinishafazekas: well, I'm not exactly sure what it's doing now so I can't really answer that.17:47
*** thomasbiege2 has joined #openstack-meeting17:47
mtreinishhow about we defer this till next week so everyone can get a chance to look at it in detail?17:48
mtreinish(or maybe just me :) )17:48
*** ruhe has joined #openstack-meeting17:48
afazekasmtreinish: I think it should do just basic things first and evolve17:48
afazekasmtreinish: ok :)17:49
*** LuzCazares has joined #openstack-meeting17:49
mtreinish#action review for discussion during next week's meeting17:49
mtreinishok then let's move on17:49
mtreinish#topic Adding test plans for new features into the tempest repo17:50
*** openstack changes topic to "Adding test plans for new features into the tempest repo (Meeting topic: qa)"17:50
mtreinishmkollaro: this is you17:50
*** elo has quit IRC17:50
*** danwent has quit IRC17:50
mkollaroso, I was wondering if we could add test plans for the new features in some nice .rst or .md format to the tempest repo17:50
*** changbl has joined #openstack-meeting17:51
*** thomasbiege has quit IRC17:51
mkollarowould that be a problem?17:51
mtreinishmkollaro: what do you mean by test plans?17:51
*** jlucci has joined #openstack-meeting17:51
mkollaromtreinish: test #1, upload file to swift; test #2, remove file from swift17:51
mtreinishmkollaro: so you mean human readable descriptions of the tests?17:52
mkollaromtreinish: we are currently writing these kinds of test plans for the havanna release and we want to share them on upstream17:52
notmynamemkollaro: hopefully a little more detailed than that :-)17:52
mkollaromtreinish: yes, but only of new stuff (I wouldn't want to document those ~800 existing tests)17:52
mkollaronotmyname: of course :D17:52
mtreinishmkollaro: oh, so if it's only new tests then I'd say a blueprint is the right place for it17:53
mkollaromtreinish: yeah, but the interface to them sucks17:53
mtreinishyou can link the blueprint to a wiki page and include as much detail as you want on that17:53
*** jmontemayor has quit IRC17:53
mkollaromtreinish: git has a history and it's easy to work with multiple people17:53
mtreinishmkollaro: so do wikis17:54
mkollarowell, if you can recommend some place, sure...but simple .md files could be parsed and put into some systems that would make my manager happy :D17:54
mkollarowikis are a bit harder to parse17:54
mkollarotest plans are just pseudo code, it's better to use git for them17:55
mtreinishthat's fair, but our procedure for this kind of plan documentation is blueprints and if more detail or collaboration is needed we put it on the wiki17:55
mtreinishbut you can link to a git repo with your plan in .md17:56
mkollaromtreinish: what procedure? I barely ever see any test plans written in upstream17:56
mtreinishI'm just don't think this kind of thing should live in the tempest repo17:56
mkollaromtreinish: nobody wants to use that and so nobody uses that17:56
mkollaromtreinish: yeah, if tempest doesn't want it we'll put it into a separate github repo, but I guess it would be nicer to have it in tempest17:57
mtreinishmkollaro: so we're almost out of time (~3min) can we take this discussion to the -qa channel after the meeting17:57
mtreinish#topic open discussion17:57
*** vkmc has joined #openstack-meeting17:57
*** openstack changes topic to "open discussion (Meeting topic: qa)"17:57
*** rellerreller has joined #openstack-meeting17:57
mtreinishso in the last ~2min does anyone have anything else?17:57
dkranzmtreinish: Nothing from me.17:58
* afazekas nothing from my side, I will not be here after the meeting17:58
*** thomasbiege2 is now known as thomasbiege17:58
mtreinishok then I guess we'll end it here today17:59
mtreinishthanks everyone17:59
*** openstack changes topic to "OpenStack Meetings ||"17:59
openstackMeeting ended Thu Aug 22 17:59:27 2013 UTC.  Information about MeetBot at . (v 0.1.4)17:59
openstackMinutes (text):
*** mlavalle has left #openstack-meeting18:00
*** jmontemayor has joined #openstack-meeting18:00
bdpayne#startmeeting OpenStack Security Group18:00
openstackMeeting started Thu Aug 22 18:00:40 2013 UTC and is due to finish in 60 minutes.  The chair is bdpayne. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: OpenStack Security Group)"18:00
openstackThe meeting name has been set to 'openstack_security_group'18:00
bdpaynehi OSSG18:01
bdpaynewho's here today?18:01
bdpayneexcellent, let's get started18:02
thomasbiegebtw, seems to be down18:02
anteayait was restarted18:02
thomasbiegeah, ok18:03
bdpayneI only have a few things for the agenda, so let me know if you have others18:03
bdpayneI have:18:03
bdpayne1) discussing the new wiki page18:03
bdpayne2) discussing addressing security review requests18:03
*** joel-coffman has joined #openstack-meeting18:03
bdpayne3) discussing ongoing projects18:03
bdpayne4) discussing the logo effort18:03
*** gkotton has joined #openstack-meeting18:03
bdpaynewhat else would people like to talk about?18:04
thomasbiegemaybe there is an open action item from our ML18:04
thomasbiegethe common state of security slide deck is open AFAIK18:04
bdpayneoh, yes18:04
*** malini1 has joined #openstack-meeting18:04
*** WayneL has joined #openstack-meeting18:04
thomasbiegehi malini118:05
bdpaynehi, we're just discussing agenda items18:05
bdpayneok, I think I'm organized over here18:06
bdpaynewe can begin :-)18:06
bdpayne#topic new wiki page18:06
*** openstack changes topic to "new wiki page (Meeting topic: OpenStack Security Group)"18:06
*** garyk has quit IRC18:06
*** gkotton is now known as garyk18:06
bdpayneI've still been receiving nice feedback on the page.18:06
*** bgorski has quit IRC18:06
*** tkammer has quit IRC18:06
bdpayneOr rather the content that I want to put up18:06
bdpayneIs there anyone that hasn't seen it / commented yet?18:07
*** ivasev has quit IRC18:07
bdpayneok, I'll take that as a no18:07
joel-coffmanI've looked through it a couple of times, and it looks good to me18:07
bdpayneso, here's my plan on this18:07
bdpayne#action bdpayne will move ahead with making some edits and posting the wiki page this week18:08
*** sriramhere has joined #openstack-meeting18:08
bdpayneSince it is a wiki, we can always work together to improve it over time as well18:08
*** cppcabrera has left #openstack-meeting18:08
*** vfiduccia has joined #openstack-meeting18:08
bdpayneand getting something up as a starting place is useful18:08
sriramherehello all - sorry i was in the wrong channel.18:08
bdpaynehi sriramhere, welcome and glad you made it18:09
malini1:)Good work on the page18:09
bdpayneok, I think that's all about the wiki page18:09
bdpayneso I'll move foward18:09
bdpayne#topic security slide deck18:09
*** openstack changes topic to "security slide deck (Meeting topic: OpenStack Security Group)"18:09
bdpaynemalini1 you had volunteered to work on this, any updates?18:09
malini1I have a confession -- got started on it, checked the email thread, started, but not enough progress to share this week18:10
malini1was distracted by other deliverables at this end, sorry18:10
bdpaynenp, understandable18:10
sriramheremalini1 - if you want an extra hand on that, i can help. would like to contribute18:10
malini1:-) will rope you in sriramhere18:11
bdpayne@action @malini1 to continue work on slide deck, and will get help from sriramhere18:12
malini1late in the day question, how does one get from IM name to email?18:12
sriramheremy email is if it is easier for u. WHOIS might help18:12
malini1never mind sriramhere, have your email contact from a message from bdpayne18:13
*** dmakogon_ has joined #openstack-meeting18:13
bdpayne#topic security review requests18:13
*** openstack changes topic to "security review requests (Meeting topic: OpenStack Security Group)"18:13
malini1:)I did a couple of those!18:14
*** mrodden has quit IRC18:14
bdpayneQuestion for the group… are you on the openstack-security mailing list?18:14
thomasbiegeyes :)18:14
bdpayneso, if anyone is not please join
bdpaynethe volume is relatively low18:15
sriramhereare we tagging [ossg] to the subjects still?18:15
bdpayneas you guys have seen, we do get pinged semi-regularly for security review help18:15
sriramherein the emails i meant18:15
*** martine has joined #openstack-meeting18:16
bdpayne[OSSG] can go in subject on emails to openstack-dev, but not necessary on the openstack-security list18:16
*** martine is now known as Guest7502518:16
bdpaynefwiw, if you put [OSSG] in subject on opentack dev, my email client treats it as higher priority ;-)18:16
thomasbiegeI unsubscribed from openstack-dev18:16
bdpayneyeah, it's pretty high volume18:17
bdpayneanyway, my point is this18:17
bdpaynewe are being asked to review stuff18:17
bdpayneand often we are not following through18:17
bdpayneI would argue that these security reviews may be the single most useful thing we can do for the openstack community18:17
*** svarnau has joined #openstack-meeting18:17
bdpayneand it's a great way for people to get involved18:17
*** svarnau has left #openstack-meeting18:18
sriramhereok, n00b question - are the emails to openstack-security list our way to communicate such requests to the groups?18:18
bdpayneso… any suggestions for how we can encourage more to take part in this process?18:18
sriramhereor do we track them as bugs?18:18
*** kbs has quit IRC18:18
thomasbiegemaybe involve developers with interest in security. I don't have any python knowledge18:18
bdpaynesriramhere not sure I understand your question, but emails are sent to openstack-security mailing list when someone files a security bug or when someone marks a review as having securityimpact18:19
*** Mandell has joined #openstack-meeting18:19
bdpaynemore developers would be good18:19
malini1i will spread the word about the list at Intel to get my colleagues to participate. Some in China wanted to join this meeting, but it is hard, so i represent our team here18:19
joel-coffmananyway to find all Gerrit reviews that include "SecurityImpact"18:19
bdpayneOSSG has actually grown quite a bit18:19
*** kbs has joined #openstack-meeting18:19
sriramhereok that answers my question. thx18:19
*** neelashah has quit IRC18:19
thomasbiegemaybe some person are well known for their security knowledge, maybe calling for help on the next summit would help18:20
bdpaynewe actually have 74 people that are members of OSSG on launchpad18:20
thomasbiegeand only 20% are active I assume18:20
bdpayneand we tend to have about 5-8 in the weekly meetings18:20
joel-coffmanbased on some that I've seen, what we really need are developers who are already familiar with the project *and* have an interest in security18:20
bdpayneso, I'd like to explore tapping into that interest a bit more18:21
bdpaynejoel-coffman I agree18:21
*** Guest75025 is now known as martine_18:21
joel-coffmanI'm not familiar with enough of the code to be much good sometimes18:21
*** zul has quit IRC18:21
bdpayneI'm not sure, but I wonder how many people that are members of the group fit into that category18:21
bdpayneperhaps a simple email to the group would help18:21
bdpaynespecifically to the launchpad group18:21
thomasbiegewhat about goiing back to openstack-dev with the review request and asking for help there18:21
* joel-coffman will try to review more as time allows18:21
*** hemanth_ has quit IRC18:22
bdpaynegoing back to openstack-dev is kind of circular18:22
thomasbiege;) ok18:22
*** hemanth_ has joined #openstack-meeting18:22
bdpaynethey are basically the ones asking use for security help18:22
rellerrellerI think it would be better to be involved in the design phase then the code review.18:22
bdpayneyes, this is true too18:22
thomasbiegeyes, but maybe to the wrong ppl :)18:22
rellerrellerThat way if you don't know the code then it is easier to participate18:22
joel-coffmanrellerreller: agreed18:22
*** vuil has joined #openstack-meeting18:22
bdpaynethe design phase is hard with openstack18:23
bdpaynelots of back room discussions18:23
malini1that means tag blueprints as security-impact18:23
bdpaynemalini1 is that possible?18:23
thomasbiegemalini1: good idea18:23
sriramhere+1, but not sure if that would slow the design discussions18:23
malini1not today, but we could ask the Gods of opnestack to add such an alert?/tag?18:23
bdpayneslow is sometimes good18:23
joel-coffmanalso need to ensure sufficient information regarding the design is available18:23
bdpayneok, so I see a few separate things here18:24
joel-coffmanthree line blueprint with SecurityImpact won't be much help18:24
bdpaynefirst, we should email the launchpad group to see if there are people wanting to help with code reviews18:24
*** sushils has quit IRC18:24
bdpayneperhaps after the wiki page is posted18:24
bdpayneso we can refer people there18:24
bdpayne#action bdpayne to email launchpad group to attempt to spark interest in code reviews18:25
thomasbiegeome of my colleagues do code reviews that have sec impact… maybe I could ask them to get more invovled18:25
bdpaynesecond, we should see if there's a way to get a security impact tag on blueprints18:25
malini1joel-coffman -- 3 lines is another discussion, there was commentary on openstack mailing list about how sometimes code born first before blueprint (like a checkbox done)18:25
bdpaynethomasbiege that would be helpful, thanks18:25
sriramherebpayne - whom to ping on adding new tag to bps?18:25
joel-coffmanyes, just pointing out the difficultly given the *current* state of affairs18:26
bdpayneI'm not sure who to ask about the blueprint tagging18:26
malini1let us try theirry for tagging18:26
bdpayneperhaps start with Theirry18:26
bdpayneanyone want to take that on?18:27
sriramhereok, i can take that18:27
sriramhere#action sriramhere to ping Theirry on adding new security tag to blueprints18:27
bdpayne#action sriramhere will talk with Theirry about getting a SecurityImpact tag added to blueprints… net affect should be that it emails the openstack-security mailing list18:27
bdpayneheh, yeah that!18:27
bdpaynethird, of course, is to encourage better blueprints18:28
bdpaynethis is where I was making a reference to backroom discussions, and code before design and such18:28
bdpayneI think that there isn't too much we can do here18:28
bdpaynebut, one suggestion, is to be a little more strategic with how we attend the upcoming summit18:28
thomasbiegerelated to this, is there a howto to write blueprint?18:29
*** danwent has joined #openstack-meeting18:29
sriramherei was about to chime on that - when bps get reviews, we can raise security impact there18:29
bdpaynewe should coordinate to get good coverage of the design sessions and report back to OSSG on how we should engage with new ideas18:29
*** sarob has joined #openstack-meeting18:29
bdpaynethomasbiege there is, but I don't have it handy…see the openstack how to contribute guide18:30
malini1bdpayne -- excellent idea on coverage at summit18:30
bdpayne#topic Final Words18:30
*** openstack changes topic to "Final Words (Meeting topic: OpenStack Security Group)"18:30
thomasbiegebdpayne:  ok18:30
bdpaynelook at the time… we're about done here18:30
bdpayneone more quick note18:30
thomasbiegetoo bad18:30
e-vadblueprints -
bdpayneI have an artist lined up for working on the OSSG logo18:30
sriramherewoohoo, skulls/ eye patches :)18:31
*** sarob has quit IRC18:31
bdpaynewaiting on approval from the openstack people on the intial design before moving ahead with that18:31
*** alexpilotti has joined #openstack-meeting18:31
bdpayneso, hopefully I'll have something pretty to share next week18:31
bdpaynestay tuned18:31
*** rlp has joined #openstack-meeting18:31
*** sarob has joined #openstack-meeting18:31
bdpaynethanks eveyone, feel free to continue these and any other discussions on openstack-security mailing list18:31
*** openstack changes topic to "OpenStack Meetings ||"18:32
openstackMeeting ended Thu Aug 22 18:32:11 2013 UTC.  Information about MeetBot at . (v 0.1.4)18:32
openstackMinutes (text):
*** danwent has quit IRC18:32
*** rlp has quit IRC18:32
*** bclifford has left #openstack-meeting18:32
*** garyk has quit IRC18:32
*** MarkAtwood has quit IRC18:32
*** Anju has left #openstack-meeting18:34
*** joel-coffman has quit IRC18:34
*** sarob has quit IRC18:35
*** neelashah has joined #openstack-meeting18:36
*** rellerreller has quit IRC18:36
*** krtaylor has joined #openstack-meeting18:37
*** MarkAtwood has joined #openstack-meeting18:40
*** MarkAtwood has quit IRC18:40
*** MarkAtwood has joined #openstack-meeting18:40
*** alrs has joined #openstack-meeting18:43
*** danwent has joined #openstack-meeting18:47
*** Tross1 has quit IRC18:48
*** thomasbiege has quit IRC18:48
*** Tross has joined #openstack-meeting18:48
*** novas0x2a|laptop has joined #openstack-meeting18:48
*** salv-orlando has quit IRC18:49
*** salv-orlando has joined #openstack-meeting18:49
*** sriramhere has left #openstack-meeting18:56
*** ivasev has joined #openstack-meeting18:59
*** martine_ has quit IRC19:01
*** sarob has joined #openstack-meeting19:02
*** lbragstad has quit IRC19:03
*** Tross has quit IRC19:08
*** lbragstad has joined #openstack-meeting19:10
*** sarob has quit IRC19:10
*** jmontemayor has quit IRC19:11
*** Tross has joined #openstack-meeting19:14
*** MarkAtwood has quit IRC19:14
*** thomasbiege has joined #openstack-meeting19:21
*** SergeyLukjanov has quit IRC19:23
*** rlp has joined #openstack-meeting19:23
*** alexb_ has quit IRC19:24
*** thomasbiege has quit IRC19:27
*** ruhe has quit IRC19:27
*** xBsd has joined #openstack-meeting19:28
*** vipul is now known as vipul-away19:32
*** jmontemayor has joined #openstack-meeting19:34
*** xBsd has quit IRC19:35
*** HenryG has quit IRC19:36
*** sarob has joined #openstack-meeting19:37
*** sdake_ has quit IRC19:39
*** sarob has quit IRC19:41
*** vfiduccia has left #openstack-meeting19:42
*** emagana has joined #openstack-meeting19:43
*** eharney has quit IRC19:43
*** LuzCazares has quit IRC19:49
*** kbs1 has joined #openstack-meeting19:50
*** kbs has quit IRC19:50
*** SergeyLukjanov has joined #openstack-meeting19:51
*** adrian_otto has quit IRC19:51
*** spzala has joined #openstack-meeting19:55
*** martine has joined #openstack-meeting19:57
*** gyee has quit IRC19:57
*** martine is now known as Guest5244819:57
*** melnikov has joined #openstack-meeting19:58
*** alexb_ has joined #openstack-meeting19:58
*** Guest52448 has quit IRC20:00
harlowja#startmeeting openstack-state-management20:00
openstackMeeting started Thu Aug 22 20:00:11 2013 UTC and is due to finish in 60 minutes.  The chair is harlowja. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: openstack-state-management)"20:00
openstackThe meeting name has been set to 'openstack_state_management'20:00
*** sarob has joined #openstack-meeting20:00
*** pcm_ has quit IRC20:00
*** adrian_otto has joined #openstack-meeting20:00
harlowja /\20:00
changblhi there20:01
melnikovhi there20:01
harlowjaso lets get started!20:02
harlowja#topic status20:02
*** openstack changes topic to "status (Meeting topic: openstack-state-management)"20:02
harlowjaanything anyone wants to say about status items that they might be doing20:02
harlowjai've been in alot of meetings @ y! and am trying to rework a little of the cinder code i did, splitting it up into more files for easier maintaince for them20:02
harlowjaand readjusted the persistence layer and am updating the resumption logbook code to use it20:03
harlowjathats currently it from me, watching code reviews and helping there to :)20:03
harlowjaand talking to other people about integration20:03
jlucciYeah, I'm actually currently trying talk trove integration in their IRC20:04
jlucciThey're having a task scheduler meeting20:04
jlucciThat got postponed until about another 15 min, so that will wait a bit20:04
jlucciBut mostly I've been working on trove integration20:05
harlowjaya, same with me and glance, trying to do doulble-meetings, not so easy, ha20:05
kebrayhi, I'm present.20:05
jlucciAh, yeah20:05
harlowjahi kebray20:05
harlowjamelnikov and anastia i think are busy helping out make taskflow core be really good20:06
melnikovi've been working on pattern/engines stuff with akarpinska; then taskflow decorators came in the way, and i refactored them a bit20:06
*** sdake_ has joined #openstack-meeting20:06
*** sdake_ has quit IRC20:06
*** sdake_ has joined #openstack-meeting20:06
*** jmh_ has quit IRC20:06
jlucciYeah - I really liked your git-review for that melnikov20:06
jlucciForgot to comment on it and what not though. :x20:06
changblI read through the code in examples, and plans to read the persistence code when it is done by harlowja. Also people in my group are working a cloud QoS project and are very interested in taskflow .We probably will use the library.20:06
harlowjathx changbl !20:07
changblnp ~  thanks for making this great library, folks20:07
harlowjait will be super great soon to!20:08
*** rlp has quit IRC20:08
*** WayneL has quit IRC20:08
harlowjachangbl anything u think dislike/like maybe u have some thoughts on to, maybe can discuss later20:08
harlowjathe more feedback (good, bad, sucky) is useful always20:08
kebrayanytime someone pulls TaskFlow into a project, and if it's a positive experience, I'd love to see a shout out for it on the dev mailing list, or a link to a video demo showing the integration or a link to a blog article about how it's helped.   just saying :-)20:09
*** nati_uen_ has joined #openstack-meeting20:09
jlucciI just wow'd the trove room with my video. They're thinking about making a sock puppet version20:09
*** alrs has quit IRC20:10
jlucciBut yeah, +1 kebray. Happiness everytime someone pulls in taskflow. :P20:10
changbl+1 kebray20:10
harlowjacoolness this flows into a good next topic, unless other status anyone has?20:11
kebraytopic:  vote for presentation?20:11
harlowja#action harlowja make sock puppet video of taskflow too20:11
changblright now in the examples,  i feel a bit awkward to specify tasks: provides, requires, __call__, not sure how we can make it simpler, though. I will take a deep look at harlowja 's create_volume code in cinder20:11
harlowjachangbl yes, its a known contention point, the way to establish dependencies between tasks20:12
*** nati_ueno has quit IRC20:12
harlowjai'm not sure if melnikov wants to change that, or wait for that change, unsure20:12
harlowjalets hold on this discussion though20:12
harlowjakebray lets jump into one more topic before yours20:12
harlowja#topic coordination20:12
*** openstack changes topic to "coordination (Meeting topic: openstack-state-management)"20:12
ekarlso-I use billingstack :)20:13
harlowjaekarlso- +120:13
ekarlso-with TF20:13
*** vkmc has quit IRC20:13
harlowjaso with the ongoing work integrating and awareness of taskflow, and dev<->dev communication, its picking up steam, which is great20:13
harlowjai'm just wondering if we want to designate a person to do this nearly full-time, like talk to glance folks, talk to others about not recreating taskflow, but integrating with it instead20:14
harlowjaand getting concepts that they have that taskflow doesn't have (and which make sense) in taskflow20:14
harlowjasorta like a integration person if u will20:14
harlowjalooking for volunteers, i don't mind trying to do it also, but that means less time coding20:14
harlowjai just think the importance of reach-out is getting more important, trove, glance and others i think are recreating there own mini-task thingies20:15
harlowjaand if we educate/interact with them we can likely redirect there energy instead of creating there own20:15
harlowjai know we have docs, but not everyone reads them (so thats where the interaction comes into play)20:16
harlowjakebray adrian_otto maybe u have some thoughts releated to this, since u guys have more experience here20:16
harlowja*more experience than me20:16
kebrayharlowja I think we spread the work for now.. and, use this meeting to coordinate reach-out-efforts.  I spend most of my week on Heat.  adrian_otto has a bunch of other things he regularly works on.. but, we can all help.20:17
*** pnavarro has joined #openstack-meeting20:18
harlowjaok, maybe thats ok for now to20:18
kebrayIf you can make it your FT job, awesome!   FWIW, jlucci is 100% TaskFlow... so, I can help her connect with others too.20:18
adrian_otto(reading scrollback)20:18
harlowjalets see, i'm not sure about FT integration person yet, but maybe :)20:19
harlowjaif i need to do that, i will :-P20:19
* kebray thinks harlowja and jlucci will connect best with the other devs... and, myself can connect best with other engineering managers and product managers.20:19
adrian_ottoDocumentation should be out top priority20:19
harlowjaagreed, still though, people just don't read it, ha20:19
kebrayi.e. make it simple.20:19
adrian_ottoI'm happy to carry the evangelism role, which I intend to continue at the HKG summit20:20
adrian_ottobut if the docs are not awesome, it's going to fall to the devs with the first hand knowledge of the code20:20
harlowjai think kebray is a good idea, 2 types of evanagelism i think20:20
harlowjaagreed, adrian_otto the docs should be awesome20:20
harlowjai think i might spend a piece of my day tommorow scanning through them for improvements20:21
adrian_ottoin terms of answering the full time role, I doubt that's practical for this particular project20:21
harlowja#action harlowja scan through wiki, adjust and make better20:21
harlowjaadrian_otto well not full time, until critical mass though reachout seems like it would be a fulltime thing20:21
harlowjabut maybe not20:21
adrian_ottoI would prioritize making the solution compelling and helpful, and producing docs to match20:21
adrian_ottoall of the most successful open source projects had great documentaion20:22
adrian_ottobecause docs scale, where handholding does not.20:22
harlowjasure, maybe we can just continue managing both, code and docs and reachout, i think we've been doing it pretty well so far20:22
harlowjaagreed, handholding doesn't in the end20:22
*** patelna has joined #openstack-meeting20:22
adrian_ottowe should offer handholding to key groups in the beginning20:23
harlowjawell not just key groups, anyone and everyone i think :)20:23
*** stevemar has quit IRC20:23
adrian_ottoparticularly those projects that can really benefit from using the library20:23
adrian_ottowell, adoption is important, but having it adopted where it makes a meaningful difference counts more.20:24
jlucciFYI  guys - in the middle of trove IRC convincing them taskflow is awesome. If you need me, just @ me20:24
harlowjahmmm, that brings in the definition of 'meaningful'20:24
adrian_ottoyes, indeed.20:24
*** Chinmay_ has joined #openstack-meeting20:24
adrian_ottothat means that users of the end solution get something as a result… like a new feature, better performance **better relaibility**, crash recovery, etc. as a result of using Taskflow20:25
*** SergeyLukjanov has quit IRC20:25
adrian_ottothe story needs to be more than "I wrote less code using Taskflow"20:25
*** vkmc has joined #openstack-meeting20:25
*** vipul-away is now known as vipul20:25
harlowjaah, gotcha, i think i misread your line above20:25
harlowjayes, that makes sense20:25
adrian_ottobut that "I got crash recovery, and would never have attempted it otherwise"20:26
adrian_ottothat's what I eman when I refer to "meaningful"20:26
*** nati_uen_ has quit IRC20:26
harlowjaas long as 'meaningful' doesn't mean only the core projects of openstack, i think thats fine20:26
*** eharney has joined #openstack-meeting20:26
harlowjajust say no to discrimantion, ha20:26
adrian_ottoof course. Adoption is an indication of success, and we should enable it as best we can.20:27
harlowjasounds good, so for now, i think we can continue our reachout and coding and integration, as long as its not causing anyone problems20:28
adrian_ottoMaking OpenStack more resilient and reliable is a huge advancement, and one I think can be enabled with what we have started on here.20:28
adrian_ottothat meets my criteria of meaningful20:28
adrian_ottoparting thought on this subject: lets all kick up our effort level on docs by at least one notch.20:29
*** sarob_ has joined #openstack-meeting20:29
adrian_ottothat should pay off in spades20:29
harlowjasounds good, lets try to do that also20:30
*** sushils has joined #openstack-meeting20:30
harlowja#topic vote-for-presentation20:30
*** openstack changes topic to "vote-for-presentation (Meeting topic: openstack-state-management)"20:30
harlowjaso kebray what were u thinking of20:31
kebraymaking sure everyone has voted :-)20:31
kebrayAnyone active in this channel right now not voted for the presentation?20:31
* kebray searches around for link.20:32
changbllet me vote, link to the talk?20:32
harlowjaah, that vote20:32
*** sarob_ has quit IRC20:32
*** sarob_ has joined #openstack-meeting20:32
*** mkollaro has quit IRC20:33
*** sarob has quit IRC20:33
harlowjathx kebray , u found it before me20:33
harlowjadon't forget to vote folks, ha20:33
* harlowja durn why is picture still not there20:33
kebrayand tell your friends.20:33
harlowjayup, and tell your friends friends20:34
harlowjaok, lets open up for any further discussion20:34
*** sushils has quit IRC20:35
harlowja#topic open-discuss20:35
*** openstack changes topic to "open-discuss (Meeting topic: openstack-state-management)"20:35
harlowjaso changbl back to the question about provides/requires, melnikov are u still around20:35
harlowjamelnikov are u thinking about adjusting how that works, or not yet20:36
harlowjaprovides/requires connect into the concept of dependency chaining and how tasks transfer 'memory'20:36
harlowjachangbl would u prefer a more manual way of connecting them20:36
harlowjai think there is room for improvement, yes of course20:37
changblbasically what I can want is that i write very few and natural code when using the library20:38
changblright now, i think there are some overlap between declaring provides/requires and __call__20:38
harlowjayes, there is, __call__ args can be examined to find what is required20:39
melnikovas for __call__, akarpinska wanted to use simple execute(...)  method instead20:39
*** dscannell has joined #openstack-meeting20:39
*** sushils has joined #openstack-meeting20:39
melnikovi tend to agree, execute/revert make nice simmetry20:39
changblharlowja, yes, examining __call__  to find out what is required would be better20:40
changbl__call__ => execute, just renaming?20:40
melnikovchangbl, as a first step20:40
changblmelnikov, any more planned changes?20:41
harlowjaso the provides one are the weird part changbl, that one is hard to automatically determine, i think we could just switch to args examination (except if someone uses *args, **kwargs)20:41
jlucciHey guys - I have to run to my puppy class, but the Trove guys are definitely interested20:41
harlowjathx jlucci20:41
jlucciSorry for the interruption - I'll look back over the meeting notes later tonight. :D20:42
changblharlowja, ok, at least we can remove one overlap20:42
*** jlucci has quit IRC20:42
harlowjaalthough i think provides might be able to be somewhat removed also, it ties into the question of how much inference is useful/possible20:42
harlowjathe nice thing about the inference is that it allows us to easily reconnect all tasks on failure of whatever was running them20:43
harlowjaalthough if u think of a raw engine, u might not need the inference at all, the engine will just have enough state to continue running, not caring about the reconnect20:43
harlowjaex, a car engine doesn't care about the surronding system, it just will run if provided gas, something else gets the gas to it (gas == flow)20:44
*** woodspa has quit IRC20:44
harlowjacar engine analogy ftw20:44
*** nealph has quit IRC20:45
harlowjasomething to think about maybe :-P20:45
changblnot sure of the analogy on engine, melnikov is working on the engine code now? I can take a look20:45
melnikovyup, i'm working on separating flows on patterns and engines -- there's blueprint for that20:46
*** Mandell has quit IRC20:46
*** Mandell has joined #openstack-meeting20:46
harlowja#link ?20:46
melnikovthe code will be on review later, idk tomorrow or next week, stay tuned;)20:46
harlowjathx melnikov20:47
changblok, thanks melnikov20:47
*** jrodom has joined #openstack-meeting20:47
harlowjaso changbl i think it will get a little easier soon, i believe20:47
*** johnthetubaguy has quit IRC20:47
melnikovharlowja, yes, that bp20:47
changblharlowja, that's great20:47
*** jrodom has quit IRC20:48
harlowjait will be a balance though, making it to easy, and it just gets us back into writing python and the library doesn't offer what we are saying it, offer/change to much and it gets hard to use20:48
harlowja*saying it does20:48
harlowjaekarlso- yt20:48
changblharlowja, right, we should get more feedback from other users20:48
harlowjaekarlso- and i were talking about how async tasks can work in a flow20:49
harlowjawhich slightly connects into being a potential way to do this20:49
harlowjaalthough maybe after melnikov work we can revisit how this can be done20:49
harlowjai think ekarlso- wanted to fire off something, then have dependent tasks not activate until whatever that was fired returned20:50
*** dkranz has quit IRC20:51
harlowjaalthough i'm unsure of the reverting condition for such an async activity, is the revert fired after a timeout, idk20:51
changblthreaded graph flow is a great idea20:51
harlowjai think its useful for these types of situations (although one greenthread per-thread might start taxing the python memory usage)20:52
harlowjagreenthread per-task i mean20:52
changblwhy are you unsure of reverting condition? got a bit confused20:53
harlowjahmmm, maybe there isn't any problem now that i think about it20:54
harlowjai'll continue working with ekarlso- to understand what his usage is about20:54
harlowjain a typical linear flow, if one task blocks, then all do20:55
changblharlowja, all right20:55
changblBtw, do we have any status update on getting taskflow integrated into other openstack projects?20:55
harlowjathreaded flow, only those that have dependencies on the blocking task will block up20:55
harlowjatrove is underway via jessica, cinder i'm continuing with, also starting conversations with glance20:55
*** pnavarro has quit IRC20:55
harlowjaand i think a few others are popping up, ekarlso- is doing billingstack20:55
harlowjaglance i think could be another user, we'll see how the timelines match up20:56
changblok, cool. Very promising20:56
*** radez is now known as radez_g0n320:56
harlowjayup, cool20:57
harlowjaalright, any other stuff, 3 minutes!20:57
*** thomasbiege has joined #openstack-meeting20:57
harlowjaif not #openstack-state-management is where you'll find us (most of the time)20:57
*** mriedem has joined #openstack-meeting20:57
*** thomasbiege has quit IRC20:57
harlowjaok, thx for showing up folks :)20:58
harlowjatill next week20:58
*** openstack changes topic to "OpenStack Meetings ||"20:58
openstackMeeting ended Thu Aug 22 20:58:26 2013 UTC.  Information about MeetBot at . (v 0.1.4)20:58
openstackMinutes (text):
*** melnikov has left #openstack-meeting20:58
russellb#startmeeting nova21:00
openstackMeeting started Thu Aug 22 21:00:19 2013 UTC and is due to finish in 60 minutes.  The chair is russellb. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
russellbHello, everyone!21:00
*** openstack changes topic to " (Meeting topic: nova)"21:00
openstackThe meeting name has been set to 'nova'21:00
*** hartsocks has joined #openstack-meeting21:00
russellb#topic havana-321:00
*** openstack changes topic to "havana-3 (Meeting topic: nova)"21:00
russellbwe have reached the feature proposal freeze21:00
russellbfeature freeze (merge deadline) is in 2 weeks21:01
russellbthere is a _lot_ of stuff to review21:01
mikalHave we defined an exception process for the proposal freeze?21:01
russellbso, i'll go ahead and assume that everyone here would really like review attention on something :-)21:01
*** gyee has joined #openstack-meeting21:01
*** mkollaro has joined #openstack-meeting21:01
russellbif someone requests an exception, they, or someone, will probably have to make sure i see it21:01
russellbgiven the volume of stuff we have21:01
*** mrodden has joined #openstack-meeting21:02
*** kbs1 has quit IRC21:02
mikalThat's fair21:02
*** melwitt has joined #openstack-meeting21:02
*** henrynash has joined #openstack-meeting21:02
*** kbs has joined #openstack-meeting21:02
russellbother than "please please review my stuff", does anyone have any questions, or topics around havana-3 that you would like to go over?21:02
*** shanewang1 has joined #openstack-meeting21:02
mroddenis the crazy amount of weird gate failures going to affect any release timeline dates?21:03
russellbmy notes on the freeze from this morning:21:03
russellbmrodden: doubtful21:03
mroddenoh, didn't see that21:03
*** johnthetubaguy has joined #openstack-meeting21:03
russellbmrodden: the turbulance and risk approaching the freeze is pretty much expected21:04
russellbif something really really bad happens *right* before the freeze, it could get extended a day or something21:04
russellbbut i wouldn't expect any extensions21:04
russellbjust remember the next release is only 6 months later, not forever :-)21:04
*** alrs has joined #openstack-meeting21:05
russellbany other havana-3 related questions or concerns?21:05
russellb#topic sub-team reports21:06
*** openstack changes topic to "sub-team reports (Meeting topic: nova)"21:06
russellbany subteams have updates they'd like to provide?21:06
russellbhartsocks: go for it21:06
*** kbs has quit IRC21:07
johnthetubaguynothing much from xenapi, smokestack getting closer to being a gate, and progress towards a tempest gate21:07
hartsocksWe've got our 6 *priority* BP we're pushing for reviews amongst ourselves.21:07
russellbjohnthetubaguy: thanks!21:07
hartsocksThen I mail the list when we get things ready for core-review.21:07
hartsocksWe're just getting our CI stuff running but ...21:07
*** dims has joined #openstack-meeting21:07
hartsockswe're not ready to publish results just yet.21:08
*** sarob_ has quit IRC21:08
russellbplan is to eventually make it public though right?21:08
russellbwhat would be most awesome is acting like smokestack does today21:08
russellba 3rd party system providing test votes in gerrit21:08
hartsocksIn the interim while the CI team is nailing that down… we may post a −1 and a link to a cut-and-paste log.21:08
*** sarob has joined #openstack-meeting21:08
russellbsure, that works too21:09
russellbbaby steps :)21:09
dansmiththat's awesaome21:09
*** rods has joined #openstack-meeting21:09
hartsocksHopefully, we won't do that for long.21:09
dansmither, awesome even21:09
*** complexmind has quit IRC21:09
johnthetubaguy+1 sounds good21:09
russellbtest all the things!21:09
hartsocksThat's the big news for us.21:09
russellbgreat thanks!21:09
russellbany others?21:09
*** changbl has quit IRC21:10
russellb#topic open discussion21:10
*** openstack changes topic to "open discussion (Meeting topic: nova)"21:10
russellbfigured it might be quick today, busy review rush right now21:10
*** lblanchard has quit IRC21:10
russellbanything for open discussion?21:10
bpbrussellb: Cinder volume encryption is no longer blocked by Cinder change, so can the priority be moved back to high?
cyeohI typed too slow earlier - just wondering if you consider adding api samples for the v3 api to be a new feature or not?21:10
shanewang1russellb: regarding the timeline dates, we should have enough time when the patches are reviewed by nova cores, right?21:11
mikalcyeoh: I think missing API samples sounds like a bug...21:11
russellbyeah i think tests are fine ...21:11
russellbbpb: *looking*21:11
cyeohmikal, russellb: cool :-)21:12
russellbshanewang1: honestly, not everything is going to make it.  it's too much right here at the end.  it's not going to be possible.21:12
bpbrussellb:  Thanks!21:12
russellbbpb: done!21:12
johnthetubaguycyeoh: +1, well sounds like docs and that quite good to do post feature freeze, I guess?21:12
russellbbpb: really happy to see this progress21:12
russellbbpb: and your nova patch got reviewed by vish already, that's great21:12
russellbso should make it seems like21:12
*** sarob_ has joined #openstack-meeting21:12
*** sarob has quit IRC21:13
*** sarob_ has quit IRC21:13
bpbrussellb: Yes, lots of work and also support from others21:13
russellbbpb: ndipanov would be another good nova-core guy to review this21:13
*** sarob has joined #openstack-meeting21:13
cyeohjohnthetubaguy: I hope so, worst case we do something unofficial out of tree first for the v3 api first, but of course I'd prefer it merged asap.21:13
bpbrussellb: thanks21:13
russellbbpb: i added ndipanov to the review, i'll see if i can talk to him about reviewing it21:14
bpbrussellb: great!21:14
shanewang1yeah, I am worrying that there is no enough time to revise the patches. Only 2 weeks left. hopefully I am wrong, or the freeze date doesn't work if the patches are under revising:)21:14
russellbshanewang1: ideally it's close to ready and won't need much revising21:15
russellbif so, won't make it21:15
russellbhonestly, with or without a freeze, only leaving a couple weeks is a really high risk21:15
russellbi have code at risk too :-)21:15
russellbi'm just trying to set realistic expectations here21:15
shanewang1because my patch was there and has never been reviewed by cores, hopefully they are not a surprise to everyone:)21:16
shanewang1I understand.21:16
* russellb nods21:16
*** elo has joined #openstack-meeting21:16
russellbwhich one21:16
*** inkerra has joined #openstack-meeting21:16
shanewang1and,n,z, the latter looks better.21:18
russellbah yes21:18
shanewang1some cores are interested in them.21:18
russellbany other topics?  otherwise we'll get back to hacking/reviewing21:18
mriedemjan/feb meetup in minneapolis!21:18
mriedemdead of winter!21:19
russellbno promises on location21:19
russellbi have a potential offer for hosting21:19
russellbi won't out them yet21:19
russellbbut it'll be based on where we can get free space to do it21:19
mikalBeaches are free21:19
russellbmikal: that would be amazing, i've never been :-)21:19
yjiang5+1 for Hawaii21:19
mikalI am sure VMWare has an office in Hawaii...21:19
yjiang5it will be better if Havana release in Hawaii21:19
johnthetubaguylol, took the works out of my keyboard21:20
johnthetubaguydoh, words21:20
russellbif you're wondering what we're talking about21:20
hartsocksIf there's a VMware office in Hawaii it's a secret.21:20
russellbplease indicate your interest in a mid-cycle meetup there ^^^21:20
russellbi'm trying to get a rough feel if planning for ~100 people or less is sufficient21:20
russellbseems like it so far21:20
yjiang5how to define ATC?21:21
russellbActive Technical Contributor21:21
russellbfor nova it means, have you submitted patches that have been accepted21:21
yjiang5great, so I am :)21:22
*** vipul is now known as vipul-away21:22
russellbthe same rules used to define whether you're able to vote in nova elections21:22
dansmithyjiang5: objects contributors will get an extra prize21:22
russellbthe nova PTL election, or TC elections21:22
*** nati_ueno has joined #openstack-meeting21:22
yjiang5dansmith: lol21:22
mriedemdansmith: how about objects bug fixers? :)21:22
*** boris-42 has quit IRC21:23
russellbwe'll all be objects bug fixers soon enough, amiright?21:23
dansmithmriedem: sure, but powervm maintainers are penalized by funding the prize pool, so it's a wash for you :(21:23
russellbalright, thanks for coming by everyone21:23
*** henrynash has quit IRC21:23
russellbfeel free to continue chatting in #openstack-nova, as always21:23
*** openstack changes topic to "OpenStack Meetings ||"21:23
openstackMeeting ended Thu Aug 22 21:23:57 2013 UTC.  Information about MeetBot at . (v 0.1.4)21:23
openstackMinutes (text):
*** johnthetubaguy has left #openstack-meeting21:24
*** hartsocks has left #openstack-meeting21:24
*** Chinmay_ has quit IRC21:24
*** shanewang1 has quit IRC21:25
*** mriedem has left #openstack-meeting21:26
*** jasondotstar has quit IRC21:29
*** dprince has quit IRC21:30
*** henrynash has joined #openstack-meeting21:30
*** krtaylor has quit IRC21:31
*** henrynash has quit IRC21:31
*** tong|2 has joined #openstack-meeting21:32
*** lpabon has quit IRC21:32
*** jtomasek has quit IRC21:32
*** dscannell has quit IRC21:32
yjiang5does anyone know if we really need copy right at empty file? See  I got a -1 from Sean Dague for has copy right, I remove it, then I got a -1 from Boris for w/o it.21:32
*** litong has quit IRC21:32
*** herndon has quit IRC21:33
*** krtaylor has joined #openstack-meeting21:33
clarkbyjiang5: I believe current consensus is that empty fiels should not have a license or copyright header21:33
clarkbas there is ntohing there to license or copyright21:33
*** litong has joined #openstack-meeting21:34
*** litong has quit IRC21:34
dimsrussellb, objects should get into oslo :)21:36
*** fifieldt has joined #openstack-meeting21:37
*** tong|2 has quit IRC21:37
*** vijendar has quit IRC21:39
*** esker has quit IRC21:41
*** vipul-away is now known as vipul21:42
*** ftcjeff has quit IRC21:45
*** markvoelker has quit IRC21:50
*** markvan has quit IRC21:50
*** neelashah has quit IRC21:52
*** dmakogon_ has quit IRC21:54
*** mrodden has quit IRC21:58
*** bpb has quit IRC21:59
*** sdake_ has quit IRC21:59
*** wolfdreamer has quit IRC22:06
*** fifieldt has quit IRC22:12
*** mkollaro has quit IRC22:13
*** burt has quit IRC22:16
*** malini1 has quit IRC22:19
*** dvarga has quit IRC22:22
*** sacharya has quit IRC22:23
*** vkmc has quit IRC22:28
*** sushils has quit IRC22:32
*** adrian_otto has quit IRC22:35
*** lbragstad has quit IRC22:36
*** thang_ has quit IRC22:40
*** malini has joined #openstack-meeting22:49
*** ivasev has quit IRC22:51
*** sushils has joined #openstack-meeting22:51
*** mrodden has joined #openstack-meeting22:54
*** MarkAtwood has joined #openstack-meeting22:54
*** gpocentek has quit IRC22:55
*** otherwiseguy has joined #openstack-meeting22:55
*** gpocentek has joined #openstack-meeting22:55
*** vuil has quit IRC23:00
*** sushils has quit IRC23:02
*** rnirmal has quit IRC23:03
*** elo has quit IRC23:03
*** notmyname has quit IRC23:04
*** elo has joined #openstack-meeting23:04
*** notmyname has joined #openstack-meeting23:04
*** dcramer_ has quit IRC23:05
*** matiu has quit IRC23:05
*** notmyname has quit IRC23:08
*** matiu has joined #openstack-meeting23:09
*** matiu has joined #openstack-meeting23:09
*** notmyname has joined #openstack-meeting23:09
*** Tross has quit IRC23:10
*** sdake_ has joined #openstack-meeting23:12
*** fnaval_ has quit IRC23:13
*** gkleiman has quit IRC23:18
*** markwash has quit IRC23:19
*** mrodden1 has joined #openstack-meeting23:19
*** mrodden has quit IRC23:20
*** jmontemayor has quit IRC23:23
*** jmontemayor has joined #openstack-meeting23:24
*** sacharya has joined #openstack-meeting23:25
*** markpeek has quit IRC23:25
*** lexinator has quit IRC23:25
*** Adri2000 has quit IRC23:25
*** noslzzp has quit IRC23:25
*** lexinator has joined #openstack-meeting23:25
*** malini has quit IRC23:27
*** patelna has quit IRC23:29
*** jmontemayor has quit IRC23:31
*** Adri2000 has joined #openstack-meeting23:33
*** tanisdl has quit IRC23:34
*** kebray has quit IRC23:37
*** jmontemayor has joined #openstack-meeting23:42
*** shardy is now known as shardy_afk23:42
*** jmontemayor has quit IRC23:42
*** jmontemayor has joined #openstack-meeting23:44
*** sdake_ has quit IRC23:44
*** rods has quit IRC23:44
*** sushils has joined #openstack-meeting23:46
*** vuil has joined #openstack-meeting23:48
*** michchap has joined #openstack-meeting23:52
*** Adri2000 has quit IRC23:53
*** jmontemayor has quit IRC23:57
*** danwent has quit IRC23:58

Generated by 2.14.0 by Marius Gedminas - find it at!