Thursday, 2013-03-07

*** dontalton has quit IRC00:04
*** dwcramer has joined #openstack-meeting00:11
*** ladquin is now known as ladquin100:11
*** ladquin1 is now known as ladquin00:12
*** fifieldt_ has quit IRC00:13
*** gyee has quit IRC00:18
*** sandywalsh has quit IRC00:22
*** mrodden1 has quit IRC00:24
*** flaper87 has quit IRC00:25
*** gatuus has joined #openstack-meeting00:25
*** ladquin has quit IRC00:34
*** ladquin has joined #openstack-meeting00:34
*** sandywalsh has joined #openstack-meeting00:35
*** metral has quit IRC00:39
*** fifieldt_ has joined #openstack-meeting00:39
*** lcheng has joined #openstack-meeting00:40
*** gatuus has quit IRC00:45
*** markwash has quit IRC00:47
*** metral has joined #openstack-meeting00:48
*** otherwiseguy has quit IRC00:49
*** dolphm has joined #openstack-meeting00:52
*** vipul is now known as vipul|away00:54
*** vipul|away is now known as vipul00:54
*** mrodden has joined #openstack-meeting00:54
*** mrodden1 has joined #openstack-meeting00:56
*** markmcclain has quit IRC00:58
*** mrodden2 has joined #openstack-meeting00:59
*** mrodden has quit IRC00:59
*** mrodden1 has quit IRC01:01
*** dontalton has joined #openstack-meeting01:01
*** dolphm has quit IRC01:03
*** johnpur has quit IRC01:04
*** jaypipes has quit IRC01:04
*** gongysh has quit IRC01:05
*** vipul is now known as vipul|away01:09
*** pony has quit IRC01:11
*** dscannell has joined #openstack-meeting01:15
*** dolphm has joined #openstack-meeting01:17
*** sarob has quit IRC01:23
*** vipul|away is now known as vipul01:25
*** dolphm has quit IRC01:26
*** dscannell has quit IRC01:31
*** yaguang has joined #openstack-meeting01:36
*** bdpayne has quit IRC01:38
*** yamahata has quit IRC01:42
*** yamahata has joined #openstack-meeting01:48
*** sdake_ has quit IRC01:53
*** alexpilotti has quit IRC01:58
*** vkmc has joined #openstack-meeting01:58
*** johnpur has joined #openstack-meeting02:05
*** johnpur has quit IRC02:06
*** adjohn has quit IRC02:06
*** salv-orlando has quit IRC02:14
*** dontalton has quit IRC02:16
*** Mandell has quit IRC02:19
*** jog0 has quit IRC02:21
*** mestery has joined #openstack-meeting02:23
*** mestery has quit IRC02:23
*** mestery has joined #openstack-meeting02:23
*** nati_ueno has quit IRC02:31
*** nati_ueno has joined #openstack-meeting02:32
*** nati_ueno has quit IRC02:36
*** otherwiseguy has joined #openstack-meeting02:42
*** westmaas has quit IRC02:42
*** mikal has quit IRC02:43
*** jeblair has quit IRC02:43
*** westmaas has joined #openstack-meeting02:43
*** mikal has joined #openstack-meeting02:43
*** jeblair has joined #openstack-meeting02:44
*** spzala has joined #openstack-meeting02:53
*** esker has joined #openstack-meeting02:55
*** lloydde has quit IRC02:57
*** vipul has quit IRC02:59
*** vkmc has quit IRC03:01
*** vipul has joined #openstack-meeting03:02
*** sacharya has quit IRC03:07
*** henrynash has joined #openstack-meeting03:07
*** lloydde has joined #openstack-meeting03:12
*** carlp is now known as carlp-away03:16
*** danwent has quit IRC03:16
*** adjohn has joined #openstack-meeting03:17
*** adjohn has quit IRC03:22
*** lloydde has quit IRC03:26
*** mestery has quit IRC03:27
*** markmcclain has joined #openstack-meeting03:29
*** lloydde has joined #openstack-meeting03:31
*** dwcramer has quit IRC03:31
*** lloydde_ has joined #openstack-meeting03:35
*** lloydde__ has joined #openstack-meeting03:37
*** lloydde has quit IRC03:38
*** lloydde_ has quit IRC03:40
*** novas0x2a|laptop has quit IRC03:45
*** dwcramer has joined #openstack-meeting03:47
*** lloydde__ has quit IRC03:56
*** ivasev has joined #openstack-meeting03:59
*** asalkeld has quit IRC04:03
*** asalkeld has joined #openstack-meeting04:03
*** henrynash has quit IRC04:05
*** spzala has quit IRC04:09
*** adjohn has joined #openstack-meeting04:10
*** SpamapS has left #openstack-meeting04:11
*** gongysh has joined #openstack-meeting04:12
*** Mandell has joined #openstack-meeting04:13
*** dscannell has joined #openstack-meeting04:17
*** SergeyLukjanov has joined #openstack-meeting04:17
*** otherwiseguy has quit IRC04:24
*** yaguang has quit IRC04:30
*** maoy has quit IRC04:30
*** dscannell has quit IRC04:35
*** nati_ueno has joined #openstack-meeting04:48
*** esker has quit IRC04:55
*** anniec has joined #openstack-meeting05:02
*** vipul is now known as vipul|away05:03
*** danwent has joined #openstack-meeting05:18
*** vipul|away is now known as vipul05:22
*** esker has joined #openstack-meeting05:23
*** fnaval_ has joined #openstack-meeting05:24
*** esker has quit IRC05:24
*** SergeyLukjanov has quit IRC05:24
*** esker has joined #openstack-meeting05:25
*** fnaval has quit IRC05:26
*** adjohn has quit IRC05:26
*** fnaval_ has quit IRC05:31
*** fnaval has joined #openstack-meeting05:35
*** fnaval has quit IRC05:35
*** fnaval has joined #openstack-meeting05:36
*** sandywalsh has quit IRC05:42
*** garyk has quit IRC05:43
*** ivasev has quit IRC05:44
*** dwcramer has quit IRC05:46
*** resker has joined #openstack-meeting05:56
*** sandywalsh has joined #openstack-meeting05:58
*** markmcclain has quit IRC05:58
*** esker has quit IRC05:59
*** koolhead17 has joined #openstack-meeting06:00
*** adjohn has joined #openstack-meeting06:14
*** anniec has quit IRC06:29
*** nati_ueno has quit IRC06:31
*** garyk has joined #openstack-meeting06:41
*** nati_ueno has joined #openstack-meeting06:43
*** davidh_ has quit IRC06:45
*** reed has quit IRC06:46
*** danwent has quit IRC06:47
*** vipul is now known as vipul|away06:51
*** psedlak has joined #openstack-meeting07:04
*** koolhead17 has quit IRC07:05
*** mrunge has joined #openstack-meeting07:09
*** nati_ueno has quit IRC07:13
*** martine has quit IRC07:13
*** nati_ueno has joined #openstack-meeting07:14
*** jdurgin has quit IRC07:33
*** flaper87 has joined #openstack-meeting07:39
*** jd__ has quit IRC07:40
*** yaguang has joined #openstack-meeting07:41
*** flaper87 has quit IRC07:44
*** jdurgin has joined #openstack-meeting07:44
*** flaper87 has joined #openstack-meeting07:50
*** smoser has quit IRC07:59
*** rafaduran has joined #openstack-meeting08:00
*** smoser has joined #openstack-meeting08:02
*** dosaboy has quit IRC08:10
*** jd__ has joined #openstack-meeting08:15
*** egallen has quit IRC08:15
*** davidha has joined #openstack-meeting08:17
*** rafaduran1 has joined #openstack-meeting08:19
*** rafaduran has quit IRC08:19
*** egallen has joined #openstack-meeting08:20
*** afazekas has joined #openstack-meeting08:23
*** afazekas has quit IRC08:27
*** reed has joined #openstack-meeting08:29
*** afazekas has joined #openstack-meeting08:30
*** salv-orlando has joined #openstack-meeting08:32
*** arosen has quit IRC08:45
*** arosen has joined #openstack-meeting08:46
*** adjohn has quit IRC09:02
*** johnthetubaguy has joined #openstack-meeting09:09
*** tomoe_ has quit IRC09:10
*** tomoe_ has joined #openstack-meeting09:11
*** tomoe_ has quit IRC09:15
*** dosaboy has joined #openstack-meeting09:20
*** darraghb has joined #openstack-meeting09:34
*** fifieldt_ has quit IRC09:45
*** fnaval_ has joined #openstack-meeting09:54
*** SergeyLukjanov has joined #openstack-meeting09:56
*** fnaval has quit IRC09:58
*** adjohn has joined #openstack-meeting10:13
*** adjohn has quit IRC10:18
*** mrunge has quit IRC10:18
*** mrunge has joined #openstack-meeting10:21
*** derekh has joined #openstack-meeting10:35
*** pnavarro has joined #openstack-meeting10:39
*** davidha has quit IRC10:42
*** zaneb has left #openstack-meeting10:47
*** johnthetubaguy has quit IRC10:47
*** yaguang has quit IRC10:47
*** fnaval has joined #openstack-meeting10:51
*** fnaval_ has quit IRC10:53
*** devananda has quit IRC10:56
*** devananda has joined #openstack-meeting10:56
*** davidha has joined #openstack-meeting10:59
*** johnthetubaguy has joined #openstack-meeting11:01
*** vkmc has joined #openstack-meeting11:22
*** vkmc has quit IRC11:42
*** dosaboy has quit IRC11:46
*** vkmc has joined #openstack-meeting11:52
*** kashyap has joined #openstack-meeting11:54
*** sandywalsh has quit IRC11:56
*** shengjie has quit IRC11:57
*** dosaboy has joined #openstack-meeting11:58
*** alexpilotti has joined #openstack-meeting12:02
*** almaisan-away is now known as al-maisan12:07
*** sandywalsh has joined #openstack-meeting12:09
*** anniec has joined #openstack-meeting12:10
*** shengjie has joined #openstack-meeting12:10
*** anniec_ has joined #openstack-meeting12:13
*** anniec has quit IRC12:15
*** anniec_ is now known as anniec12:15
*** llu-laptop has joined #openstack-meeting12:20
*** nati_ueno has quit IRC12:30
*** nati_ueno has joined #openstack-meeting12:30
*** nati_ueno has quit IRC12:35
*** Razique has joined #openstack-meeting12:51
*** lbragstad has joined #openstack-meeting12:54
*** ayoung has quit IRC12:57
*** dscannell has joined #openstack-meeting13:08
*** mrunge has quit IRC13:12
*** vkmc has quit IRC13:13
*** martine has joined #openstack-meeting13:16
*** resker has quit IRC13:26
*** dscannell has quit IRC13:29
*** dolphm has joined #openstack-meeting13:36
*** dolphm has joined #openstack-meeting13:37
*** lbragstad has quit IRC13:39
*** eharney has joined #openstack-meeting13:42
*** eharney has joined #openstack-meeting13:42
*** salv-orlando has quit IRC13:45
*** anteaya has joined #openstack-meeting13:48
*** zehndton has joined #openstack-meeting13:58
*** dprince has joined #openstack-meeting14:01
*** Razique has quit IRC14:03
*** mkollaro has joined #openstack-meeting14:03
*** Razique has joined #openstack-meeting14:04
*** davidha has quit IRC14:05
*** andreaf has quit IRC14:11
*** andreaf has joined #openstack-meeting14:11
*** lbragstad has joined #openstack-meeting14:13
*** johnthetubaguy1 has joined #openstack-meeting14:13
*** SergeyLukjanov has quit IRC14:13
*** johnthetubaguy1 has quit IRC14:14
*** johnthetubaguy1 has joined #openstack-meeting14:14
*** johnthetubaguy has quit IRC14:15
*** dguitarbite has joined #openstack-meeting14:15
*** woodspa has joined #openstack-meeting14:24
*** dscannell has joined #openstack-meeting14:29
*** dscannell has quit IRC14:30
*** dolphm has quit IRC14:32
*** ayoung has joined #openstack-meeting14:34
*** sdake_ has joined #openstack-meeting14:35
*** dhellmann-afk is now known as dhellmann14:39
*** mestery has joined #openstack-meeting14:39
*** dolphm has joined #openstack-meeting14:41
*** radez_g0n3 is now known as radez14:42
*** SergeyLukjanov has joined #openstack-meeting14:44
*** gongysh has quit IRC14:44
*** sew has joined #openstack-meeting14:44
*** n0ano has joined #openstack-meeting14:48
*** topol has joined #openstack-meeting14:48
*** fnaval has quit IRC14:50
*** maksimov has joined #openstack-meeting14:50
*** eglynn has joined #openstack-meeting14:50
*** esker has joined #openstack-meeting14:51
*** chuck_ has joined #openstack-meeting14:51
*** zul has quit IRC14:53
*** mattray has joined #openstack-meeting14:54
*** jaypipes has joined #openstack-meeting14:56
*** epende has joined #openstack-meeting14:57
*** danspraggins has joined #openstack-meeting14:57
*** graflu0 has joined #openstack-meeting14:58
dhellmann#startmeeting Ceilometer15:00
openstackMeeting started Thu Mar  7 15:00:24 2013 UTC.  The chair is dhellmann. 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
dhellmann#meetingtopic Ceilometer15:00
*** openstack changes topic to " (Meeting topic: Ceilometer)"15:00
*** mtreinish has joined #openstack-meeting15:00
*** DanD has joined #openstack-meeting15:00
dhellmann#chair dhellmann15:00
openstackCurrent chairs: dhellmann15:00
dhellmann#link http://wiki.openstack.org/Meetings/MeteringAgenda15:00
dhellmannATTENTION: please keep discussion focused on topic until we reach the open discussion topic15:00
dhellmannPlease raise your hand if you are here for the ceilometer meeting.15:00
dhellmanno/15:00
eglynno/15:00
llu-laptopo/15:01
n0anoo/15:01
maksimovo/15:01
DanDo/15:01
zehndtono/15:01
graflu0o/15:01
danspragginso/15:01
*** gordc has joined #openstack-meeting15:01
dhellmannhi, gordc, are you here for the ceilometer meeting?15:01
dhellmannlet's get started15:01
dhellmann#topic Review last week's actions15:01
*** openstack changes topic to "Review last week's actions (Meeting topic: Ceilometer)"15:01
dhellmann#topic nijaba to check room allocation for ceilometer during summit15:01
*** openstack changes topic to "nijaba to check room allocation for ceilometer during summit (Meeting topic: Ceilometer)"15:01
gordchi dhellmann, yes. just checking in.15:01
dhellmanngreat, we're just getting going15:02
*** chuck_ is now known as zul15:02
dhellmannnijaba isn't able to make the meeting today, and I didn't get an update from him, so I will put this on the agenda for next week15:02
dhellmann#action nijaba to check room allocation for ceilometer during summit15:02
dhellmann#topic nijaba to start a brainstorm wiki for a tag line on the tshirt15:02
*** openstack changes topic to "nijaba to start a brainstorm wiki for a tag line on the tshirt (Meeting topic: Ceilometer)"15:02
dhellmann#link https://wiki.openstack.org/wiki/Ceilometer/TagLine15:02
sandywalsho/15:02
dhellmann#info done15:02
dhellmannif you have proposals for a tagline, please add them to that wiki page15:03
dhellmann#topic Bug day results15:03
*** openstack changes topic to "Bug day results (Meeting topic: Ceilometer)"15:03
sewo/15:03
dhellmannwe had our second bug squashing day on tuesday15:03
dhellmannit seemed to go well, there were a lot of changesets up for review15:03
dhellmanndid anyone count them?15:04
dhellmannok, perhaps not15:04
maksimovjd__: has been submitting like 5 at a time15:04
dhellmannwe should be able to get those stats15:04
*** nealph has joined #openstack-meeting15:05
dhellmannyes, he had several related changes stacked up :-)15:05
maksimovi opened a new bug instead of fixing any :P15:05
dhellmannmaksimov: we'll take it!15:05
dhellmanndoes anyone have comments about how to improve the process for next time?15:06
maksimovprobably a good idea to have a discussion a day earlier15:06
eglynnyep15:06
eglynntiming was definitely better this time round15:06
llu-laptopIs the bug squashing day target for take ownership of the bug or fix it on that day?15:06
dhellmannI tried to do a little triage work, but discussion would be good15:06
eglynn(in terms of closeness to a release deadline)15:06
dhellmannllu-laptop: both or either15:07
dhellmanneglynn: +115:07
dhellmannI think it also helped that we were in feature-freeze, so there was less temptation to work on new things. :-)15:07
llu-laptopsome bugs are not easy to do. Like the metaquery for sqlalchemy which jd took15:07
eglynntrue that15:07
dhellmannwhat do you think about introducing week-long bug sprints at a couple of spots in our schedule for H?15:08
dhellmannmaybe leading right up to milestones, for example?15:08
eglynnthe perfect bug for a day of squashing is bite-sized and self-contained15:08
eglynnwhich is limiting15:08
eglynnso yeah, a weak long bug sprint sounds ideal15:08
maksimovweek-long sprint is good15:08
llu-laptop+1 for week-long sprint15:09
dhellmannok, we'll leave that for our next PTL to organize, then :-)15:09
maksimovespecially for those who are not 100% devoted, but still want to participate15:09
eglynnit would also give folks the flexibility to dip in and out15:09
eglynnyep, exactly15:09
nealph+115:09
dhellmann#agreed introduce week-long bug sprints during the H cycle, details to be determined15:09
graflu0+115:09
dhellmannI believe quantum has a feature freeze ~1 week before each milestone, so maybe we can verify that and duplicate what their team is doing15:10
dhellmannok, moving on15:10
dhellmann#topic Removal of unactive core developers15:10
*** openstack changes topic to "Removal of unactive core developers (Meeting topic: Ceilometer)"15:10
dhellmannIt is proposed that we remove Loic Dachary, Francis J. Lacoste, and Graham Binns from the "core" team.15:10
dhellmannMy understanding is their status can easily be restored.15:10
eglynnwhat's our definition of inactive?15:10
ependeo/15:11
eglynnno patches in previous release cycle?15:11
eglynnor no reviews?15:11
dhellmannwell, I'm not sure that they have contributed during grizzly15:11
eglynnk15:11
dhellmannfor core, reviews are (IMO) the most important contribution15:11
*** fnaval has joined #openstack-meeting15:11
eglynndhellmann: agreed15:11
dhellmannI'm not 100% sure of the process for making the updates, but I think if everyone agrees we can leave it to nijaba to handle.15:11
sandywalshfor nova it's # reviews in 30 days15:11
dhellmannand, as I mentioned, their status can easily be reinstated by their asking15:12
sandywalsh(at least 10 required)15:12
eglynnthat's fair15:12
eglynnany objections? do we need to vote on it?15:12
dhellmannsandywalsh: we're smaller, so a lower threshold seems reasonable15:12
sandywalshdhellmann, sure15:12
dhellmannI'm not sure of the voting process for that15:12
dhellmannI don't think we have a quorum of core contributors today15:12
dhellmannif there are no strong objections, I propose we just say we've agreed and let nijaba handle the details when he gets back15:13
eglynnfair enough (I don't object to the removal, just wondering about the process ...)15:13
maksimovwhat's the benefit of removing? does this free up a quota for new core?15:13
maksimovor is there a quota15:13
*** mrunge has joined #openstack-meeting15:13
dhellmannmaksimov: no, there is no quota15:13
dhellmannbut if they are not contributing, I think we want them off of the core list so we know who *is* an active contributor15:14
*** dontalton has joined #openstack-meeting15:14
maksimovok so15:14
eglynnjust housekeeping really I guess, also ... pour encouragez les autres15:14
dhellmannright15:14
llu-laptopeglynn: is that latin?15:15
dhellmannyou know, I guess it makes voting in new core members easier, too, since the voting pool is limited to the active contributors15:15
*** ryanpetrello has joined #openstack-meeting15:15
dhellmannllu-laptop: french (to encourage the others)15:16
eglynnllu-laptop: French, I'm standing in as the token Frenchman today ;)15:16
maksimov:)15:16
*** sacharya has joined #openstack-meeting15:16
dhellmannso if there are no strong objections, I will mark us agreed and let nijaba take care of it?15:16
*** shanewang has joined #openstack-meeting15:16
llu-laptoplooks like I can learn my 2nd foreign language here. addtional benifit ;)15:16
llu-laptopagreed15:17
eglynn+115:17
sandywalshdhellmann, just so I'm clear, are you suggesting that only patches are meaningful vs. just reviewing?15:17
dhellmannsandywalsh: the opposite, for core15:17
eglynnthe opposite I thought15:17
eglynnyep15:17
sandywalshk, cool .. good15:17
dhellmannwell, not the opposite, but reviews are more important15:17
dhellmannpatches are definitely important, too!15:17
sandywalsh+115:18
dhellmann#agreed remove Loic Dachary, Francis J. Lacoste, and Graham Binns from the "core" team15:18
dhellmann#topic Release of python-ceilometerclient15:18
*** openstack changes topic to "Release of python-ceilometerclient (Meeting topic: Ceilometer)"15:18
llu-laptopjust wondering what's the task list for such a release?15:18
dhellmannWe need to prepare a release. I haven't had a chance to review the process for doing that. Is anyone else familiar with it?15:18
sandywalshnova allows a "fast track" for reinstated ... just start reviewing again regularly. No core vote required.15:18
dhellmannsandywalsh: right, I think we'd probably follow that process15:19
dhellmann#action dhellmann investigate the process for releasing a client library15:19
dhellmannI'm sure there's some automation around that, probably involving tagging15:19
eglynnpushing up to pypi also?15:20
dhellmannyeah, jenkins does that part15:20
eglynnk15:20
dhellmannI would like to propose that we use the semantic versioning scheme (1.0.0), rather than date-based (2013.1) because my understanding is the new  python packaging tools will eventually not work with date-based releases.15:21
dhellmannthere was some discussion of this related to oslo.config recently on the dev mailing list15:21
dhellmannit seems like, since this is our first release, we should try to start out down the right path, instead of having to change it later15:21
dhellmannany objections or questions?15:22
sandywalshdhellmann, better check with ttx on that one15:22
llu-laptopagreed. We don't want follow oslo.config.15:22
dhellmannsandywalsh: yeah15:22
eglynnI think the other python-*clients already go with x.y.z as opposed to YYYY.x15:22
ttxsemantic versioning is fine with python client libs15:23
dhellmanneglynn: a sample of size 1 says you may be correct15:23
dhellmannttx: thanks!15:23
llu-laptopShould the client follow the same milestone as the main project?15:23
*** al-maisan is now known as almaisan-away15:23
*** otherwiseguy has joined #openstack-meeting15:24
dhellmannllu-laptop: since it doesn't follow the same versioning scheme, and it is supposed to maintain backwards compatibility, I think the idea is to be able to release more frequently, as needed15:24
eglynnllu-laptop: they're decoupled for the other projects15:24
maksimovfor example i see python-swiftclient 1.3.0, python-novaclient 2.11.115:25
eglynnllu-laptop: sometimes causes an issue, e.g. when a new novaclient include calls that require new-ish support in nova core15:25
dhellmannare there any missing features that would preclude a release? or any critical bugs?15:25
eglynnalso another thing to note for the clients is that there's no stable branch15:26
eglynn(so any fixes wait for the next full release)15:26
*** Divakar has joined #openstack-meeting15:26
dhellmanneglynn: yes, but we can release whenever we need to, right?15:26
eglynndhellmann: yep15:27
*** lloydde has joined #openstack-meeting15:27
dhellmannso the "wait" may be until "tomorrow" :-)15:27
eglynnI guess :)15:27
*** davidha has joined #openstack-meeting15:27
gordcare there plans to merge the client into openstackclient or is ceilometer going to remain separate?15:27
*** markmcclain has joined #openstack-meeting15:27
dhellmanngordc: I plan to get them merged15:27
maksimovis this an old one? https://pypi.python.org/pypi/ceilometerclient/0.115:28
dhellmannmaksimov: yes, that was a prototype that we wrote at dreamhost15:28
sandywalshI always get confused between python-novaclient and novaclient ... is one pip and one distro?15:28
maksimovoic - 'pre-alpha'15:28
dhellmannit predates asalkeld's work on the official client15:28
dhellmannsandywalsh: I'm not sure I've see novaclient. I think the package name is python-novaclient15:29
*** Gordonz has joined #openstack-meeting15:29
dhellmannwell, the "dist" name is python-novaclient and the python package is novaclient15:29
dhellmannmaksimov: yes, a completely different (and now abandoned) code base15:29
*** Gordonz has quit IRC15:29
sandywalshok, there was two for a while, but I think they've cleaned that up15:29
dhellmannsandywalsh: ah15:29
maksimovthe whole list https://pypi.python.org/pypi?:action=browse&c=58315:30
dhellmannso, back to our client: does anyone have any bugs we definitely need to fix before a 1.0 release?15:30
*** Gordonz has joined #openstack-meeting15:30
dhellmannand, now that it comes up, should this be 1.0?15:30
dhellmannI think it should, but does anyone disagree?15:30
llu-laptopkeystoneclient is still 0.2.215:30
eglynnyolanda's https://review.openstack.org/23549 should probably go in15:30
dhellmanneglynn: yes, definitely15:31
sandywalshI don't think so ... I think we're going to have some big changes in the next release, but it's just a number15:31
dhellmannwe're just waiting for tests for that15:31
dhellmannsandywalsh: big changes in the client?15:31
maksimovcan we align 1.x vs 2.x with use of v1 vs v2 perhaps?15:31
dhellmannmaksimov: I don't think we need to do that15:31
dhellmannthe client we have already supports both apis15:32
maksimovwill it support both?15:32
sandywalshdhellmann, possibly all over (I'm thinking the new data types if we go that route)15:32
eglynnmaksimov: other clients support multple API versions at once15:32
maksimovoh ok15:32
eglynnmaksimov: e.g. glance --os-api-version 215:32
dhellmannsandywalsh: those sorts of changes would mean a v3 api, it sounds like. a client 2.0 could support the new api, right?15:32
sandywalshbut, we can't worry about what "might be coming" ... we just have to put a mark in the ground.15:32
dhellmannsandywalsh: +100015:32
sandywalshversion 1 to me says "it's ready for production"15:32
sandywalshis cm ready for production would you say?15:32
dhellmannthe client is as ready as the rest of it :-)(15:33
* dhellmann is channelling nijaba with typos today15:33
nealphI have a bug on the install...https://bugs.launchpad.net/bugs/111878015:33
uvirtbotLaunchpad bug 1118780 in python-ceilometerclient "The ceilometer python client fails install due to required packages" [Undecided,New]15:33
sandywalshI think that's core's call if it's ready for the big dance15:33
sandywalshversion 1 also means "we're locking stuff down"15:34
nealphAny chance to see that resolved before the rev to 1.0?15:34
dhellmannnealph: that looks like a bug in the ubuntu package of the client, not the client itself, right?15:34
dhellmannIOW, if we push a package to pypi, someone could install it from there15:34
nealphYep, I'd say.15:35
nealphWilling to try it there, sure.15:35
*** sacharya has quit IRC15:35
dhellmannok, so it sounds like we mostly agree to use 1.0 and we want to wait for yolanda's fix to be merged before the release15:36
eglynncool15:36
dhellmann#agreed we need https://review.openstack.org/23549 merged before releasing the client15:36
dhellmann#agreed use semantic versioning, starting with 1.0.015:36
dhellmann#topic Planning to attend the ODS15:37
*** openstack changes topic to "Planning to attend the ODS (Meeting topic: Ceilometer)"15:37
dhellmannso, who will be in portland in April?15:37
dhellmanno/15:37
eglynno/15:37
sandywalsho/15:37
n0anoo/15:37
eglynnasalkeld: o/15:37
llu-laptopI planned to, but waiting for my visa15:37
maksimovwhat's the sign for possibly?15:37
sandywalsh(and 3 more of us from RAX that are working on CM)15:37
Divakarwill be in portland in April15:38
dhellmannmaksimov: "possibly" :-)15:38
maksimovso that ^^15:38
dhellmannok, good15:38
dhellmannI think we talked last week about trying to get together for dinner one evening, and we're just waiting for the official schedule so we can decide which party to skip :-)15:38
DanDo/15:38
danspragginso/ for portland as well.15:39
nealphdidn't get approval to travel, so DanD will have to represent.15:39
shengjieo/15:39
dhellmannnealph: do you know if they're going to have webex and irc in the rooms again?15:39
* sandywalsh has to jump off ... good luck with the release all 15:39
eglynnthere are ~15 ceilo sessions proposed so far ... http://summit.openstack.org15:39
nealphHoping so...15:40
gordcpossibly... if budget gets approved... so in other words.. no.15:40
dhellmanngordc: :-(15:40
dragondmo/15:40
dhellmannok, let's talk sessions15:40
nealphBut not sure. Who can find out?15:40
eglynnso maybe we'll end up needing a second day ...15:40
dhellmann#topic Submitting ODS sessions & blueprints15:40
*** openstack changes topic to "Submitting ODS sessions & blueprints (Meeting topic: Ceilometer)"15:40
dhellmannPlease remember to submit summit sessions for any blueprints you want worked on during Havana15:40
dhellmann#link http://summit.openstack.org/15:40
dhellmannare there any topics that you think need to be discussed, but that you're not comfortable proposing as a session leader?15:41
*** tomoe_ has joined #openstack-meeting15:41
dhellmannFWIW, if you want a topic, that doesn't imply that you have a solution already15:41
DivakarI am submitting a session on ceilometer and healthnmon integration15:41
*** chunwang has joined #openstack-meeting15:41
dhellmannDivakar: excellent15:42
llu-laptopDivakar: looking forward to that15:42
shanewanghealthnmon for sure:)15:42
shengjieDivakar:this is a good one!15:42
n0anoDivakar, +115:42
Divakargreat15:42
ependeRegion and availability zone support15:42
dhellmannepende: I believe there is a session that covers those...15:42
llu-laptopnova-cell?15:43
eglynnthere's one on cells http://summit.openstack.org/cfp/details/6315:43
*** psedlak has quit IRC15:43
dhellmannthe blueprint for http://summit.openstack.org/cfp/details/75 mentions them15:44
*** mkollaro has quit IRC15:44
nealphepende: we also have a touch of that in our "advanced billing models" session http://summit.openstack.org/cfp/details/7915:44
shengjiecan someone remind me again the deadline for suggesting topics?15:45
eglynnend of moth15:45
eglynn*month15:45
dhellmannI did notice what I thought was a bit of overlap in some of the topic areas, so everyone please review the list with that in mind, too.15:45
eglynnshengjie: (but the sooner the better)15:46
shengjieeglynn: thanks15:46
dhellmannwe will have limited space and time, so if we can combine sessions that will help ensure everyone's ideas are heard15:46
*** dscannell has joined #openstack-meeting15:46
DanDwhat is the process for combining sessions when there is overlap?15:46
*** dscannell1 has joined #openstack-meeting15:46
eglynnPTL knocks heads together?15:47
dhellmannDanD: approach the other proposer and get agreement, then tell nijaba (or the new PTL)15:47
llu-laptopis zehndton around? Do you want to talk about the physical monitoring?15:47
zehndtonhere15:47
dhellmannI think the PTL has a way to either merge or close sessions in the tool15:47
dhellmannspeaking of merging sessions...15:47
dhellmann#topic Planning ODS sessions with other teams15:47
*** openstack changes topic to "Planning ODS sessions with other teams (Meeting topic: Ceilometer)"15:47
dhellmannI thought it would be a good idea to approach the documentation and QA teams for help getting started working with them, now that we are integrated. Any thoughts?15:48
Divakarhealthnmon covers the model and approach for physical server monitoring...15:48
eglynnyep, definitely a good idea to talk to the tempest folks15:48
shanewangintegrate ceilometer into tempest and CI?15:49
shanewangthat is a good idea, I think.15:49
dhellmannwe're already doing CI, but tempest, yes15:49
shengjieDivakar: monitoring wise, i meant to ask what's the stories with all the synaps bps ?15:49
llu-laptopI've created a bp https://blueprints.launchpad.net/ceilometer/+spec/more-qa-test, but no input there15:49
Divakarshengjie: got it15:49
dhellmannllu-laptop: do you want to propose a session, too?15:49
eglynnshengjie: we looking at a different mor elightweight approach that synaps15:50
* dhellmann reminds everyone that you must create a session proposal separately from the blueprint15:50
eglynns/that/than/15:50
llu-laptopI'm not confident holding the tempest session, i think we should contact the qa team first15:50
dhellmannllu-laptop: well, the idea would be to have that conversation there in the room together :-)15:50
dhellmannI can lead the session, if you would prefer15:50
llu-laptopdhellman: great15:51
dhellmann#action dhellmann propose an ODS session for tempest integration15:51
dhellmanndoes anyone want to approach the documentation team?15:51
shengjieeglynn:k, i'll take it offline with u :)15:51
dhellmannalso, do we want to see if the heat team would like to participate in these sessions?15:51
Divakarhealthnmon with tempest would that be of interest?15:52
eglynndhellmann: yep, we need to tie down the alarming/heat interaction model15:52
dhellmannDivakar: you can propose the session, but I suspect we'll want to wait until healthnmon is incorporated into ceilometer in some fashion to start doing that15:52
eglynn(though that may occur in adavnce of the summit)15:52
dhellmanneglynn: I mean specifically the doc and tempest sessions15:52
eglynndhellmann: a-ha, got it15:53
Divakardhellmann: sure15:53
dhellmannboth teams would benefit from the instruction, so save the doc and qa team's time15:53
eglynnagreed15:53
dhellmanneglynn: can you talk to heat?15:53
eglynndhellmann: yep15:53
dhellmann#action eglynn invite heat team to participate in doc and qa sessions at ODS15:53
dhellmann#action dhellmann approach documentation team about a joint session at ODS15:54
*** darraghb has quit IRC15:54
dhellmannOK, getting close to end of time15:54
dhellmann#topic PTL elections15:54
*** openstack changes topic to "PTL elections (Meeting topic: Ceilometer)"15:54
dhellmannWe have 2, I think, candidates now (jd__ and eglynn).15:54
dhellmannIf anyone else is planning to run, I think the deadline for announcing is coming up15:54
*** lloydde has quit IRC15:54
dhellmann#topic Open discussion15:55
*** openstack changes topic to "Open discussion (Meeting topic: Ceilometer)"15:55
nealphwho would know we will have webex or similar access to the ODS15:55
dhellmannnealph: ttx may know, but it might be too early to tell15:55
eglynnstefano perhaps?15:55
dhellmannlast time they did announce it on the mailing list, IIRC15:55
nealphokay, will be watching for it...will wait a couple of weeks before asking around.15:56
dhellmanngood plan15:56
dhellmannis there anything else for today?15:57
*** colinmcnamara has joined #openstack-meeting15:57
shanewangis there any daylight saving time in US since next week? any impact for meetings?15:57
dragondm3/1015:57
dragondmer 4/1015:57
*** darraghb has joined #openstack-meeting15:57
nealph3/10. Time changes for most US.15:57
* dragondm is confused15:57
dhellmannshanewang: the official meeting times are UTC, which doesn't have DST15:57
shanewangok15:57
dhellmannso, do the time conversion for the date of the meeting, and you *should* get the right answer :-)15:58
*** dwcramer has joined #openstack-meeting15:58
dhellmannI have 2 more things15:58
dhellmann1: Is anyone going to PyCon?15:58
dhellmannthat's PyCon US, next week15:58
dhellmann2: We have 13 changesets in the queue. Please review!15:58
llu-laptopi think most of them are blocked by the oslo.config15:59
*** markmcclain has quit IRC15:59
dhellmannllu-laptop: yeah, I think your fix will unblock that. did you see my comment?15:59
*** mkollaro has joined #openstack-meeting16:00
llu-laptopdhellman: I've updated patch 3.16:00
dhellmannllu-laptop: ok, I'll go look and fast-track approve it to unblock the queue16:00
* dhellmann is planning to help with the common requirements project next release to avoid these issues16:00
dhellmannso, nobody is going to pycon?16:00
eglynnnope, sadly ...16:00
dragondmalas.16:00
dhellmannah, well16:01
dhellmannok, I think our time is up16:01
*** dontalton has quit IRC16:01
*** john5223 has joined #openstack-meeting16:01
dhellmannthanks for a good meeting, everyone!16:01
maksimovthanks16:01
eglynnthanks all!16:01
graflu0thanks16:01
shanewangthanks and bye16:01
*** epende has quit IRC16:01
dhellmann#endmeeting16:01
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"16:01
openstackMeeting ended Thu Mar  7 16:01:46 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-03-07-15.00.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-03-07-15.00.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-03-07-15.00.log.html16:01
*** shanewang has left #openstack-meeting16:01
*** sew has left #openstack-meeting16:02
*** gordc has left #openstack-meeting16:02
shengjiecheers16:02
*** graflu0 has quit IRC16:02
*** danspraggins has quit IRC16:02
*** gyee has joined #openstack-meeting16:04
*** llu-laptop has left #openstack-meeting16:04
*** zehndton has left #openstack-meeting16:05
*** Razique has quit IRC16:06
*** sacharya has joined #openstack-meeting16:06
*** dscannell1 has quit IRC16:09
*** SergeyLukjanov has quit IRC16:09
*** Mandell has quit IRC16:10
*** tomoe_ has quit IRC16:10
*** tomoe_ has joined #openstack-meeting16:11
*** tongli has joined #openstack-meeting16:11
*** anniec has quit IRC16:15
*** tomoe_ has quit IRC16:15
*** hemna has joined #openstack-meeting16:16
*** koolhead17 has joined #openstack-meeting16:17
*** markmcclain has joined #openstack-meeting16:19
*** danwent has joined #openstack-meeting16:20
*** maksimov has left #openstack-meeting16:20
*** dani4571 has joined #openstack-meeting16:20
*** dolphm has quit IRC16:20
*** gary_th has joined #openstack-meeting16:23
*** dolphm has joined #openstack-meeting16:23
*** vipul|away is now known as vipul16:26
*** vipul is now known as vipul|away16:26
*** dripton_ has joined #openstack-meeting16:27
*** dripton has quit IRC16:27
*** dripton_ is now known as dripton16:31
*** dscannell has joined #openstack-meeting16:33
*** Divakar has quit IRC16:33
*** vipul|away is now known as vipul16:35
*** lloydde has joined #openstack-meeting16:43
*** garyk has quit IRC16:45
*** torandu has joined #openstack-meeting16:45
*** cameron has joined #openstack-meeting16:45
*** cameron has left #openstack-meeting16:45
*** davidha has quit IRC16:46
*** bdpayne has joined #openstack-meeting16:47
*** dwalleck has joined #openstack-meeting16:49
*** mestery has quit IRC16:51
*** vipul is now known as vipul|away16:56
*** vipul|away is now known as vipul16:56
*** donaldngo_hp has joined #openstack-meeting16:58
*** lloydde has quit IRC16:59
*** malini has joined #openstack-meeting17:00
*** mlavalle has joined #openstack-meeting17:00
jaypipes#startmeeting qa17:00
openstackMeeting started Thu Mar  7 17:00:19 2013 UTC.  The chair is jaypipes. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
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
jaypipesGood morning/evening QAers.17:00
mtreinishmorning17:00
mlavallehi17:00
andreafhi17:00
malinihello!17:00
dwalleckhowdy17:00
jaypipessorry for missing last week's meeting...17:01
jaypipesBeen pleased to see a bunch of progress in code reviews and new test pushes.17:01
jaypipesdavidkranz: around?17:01
davidkranzjaypipes: Just back.17:01
*** rohitk has joined #openstack-meeting17:01
jaypipessdague: around?17:01
*** stevemar has joined #openstack-meeting17:02
jaypipesrohitk: evening.17:02
rohitkjaypipes: morning :)17:02
jaypipesOK, so dhellmann mentioned a proposed design summit session that I thought was a great idea...17:02
sdaguejaypipes: yes17:02
donaldngo_hphello all17:02
jaypipes#topic Getting Started with Tempest design summit session17:02
*** openstack changes topic to "Getting Started with Tempest design summit session (Meeting topic: qa)"17:02
jaypipesdonaldngo_hp, sdague: mornin.17:03
sdagueoh, right meeting :)17:03
jaypipes#link https://etherpad.openstack.org/havana-adding-projects-to-tempest17:03
chunwanghi17:03
jaypipesBasic point of the session is to help Ceilometer and Heat folks get familiar with Tempest and help them start to add integration tests for Ceilo and Heat17:03
jaypipesWhich of course I think is a great idea!17:04
davidkranzjaypipes: Yes, looks good. But first *we* need to decide what a smoke test is :)17:04
jaypipesBut, naturally, there's a bit of a learning curve for new projects learning how Tempest does things, and this session should help in that regard17:04
jaypipesdavidkranz: lol, indeed. could have a whole sesion on that ;)17:04
rohitkand Tempest has been shaping up quite awesome in the last six months for more contributions17:04
donaldngo_hpjaypipes: would be good for new comers to tempest as well17:04
jaypipesFYI, design summit proposal is here:17:05
jaypipes#link http://summit.openstack.org/cfp/details/8717:05
jaypipesdonaldngo_hp: yup, totally.17:05
sdaguejaypipes: I agree, intro to tempest would be great17:05
*** ravikumar_hp has joined #openstack-meeting17:05
sdaguedo we have an idea on how long our track is going to be?17:05
sdagueor the track structures in general17:05
jaypipesdonaldngo_hp: and I think that it would be really useful to devote at least half the session time to the final bullet point on the page... a walk through of adding real test cases for Ceilo and Heat17:05
*** vkmc has joined #openstack-meeting17:06
jaypipesthat way we give those teams a good start17:06
jaypipesravikumar_hp: morning :)17:06
davidkranzsdague: "Intro to Tempest" could be on a non-design-summit track17:06
ravikumar_hpgood morning Jay17:06
sdaguedavidkranz: it could be, but that's closed17:06
jaypipessdague: no constraints, AFAIC17:06
donaldngo_hpjaypipes: yea maybe get a test checked in, reviewed, and merged into tempest if possible in that session17:06
sdaguejaypipes: ok cool17:07
sdagueit's been one of those weeks where I've not been able to spend any time doing "real work"17:07
jaypipesdonaldngo_hp: yup, we could even break things into a double session, with the first part a more formal walkthrough of the existing tempest layout and concepts and the following session be actually constructing the first couple test cases for each project.17:07
jaypipessdague: heh, understood :)17:07
donaldngo_hpjaypipes++17:08
mlavallejaypipes: ++17:08
sdaguecould we decide next week's QA meeting is a design summit planning one, and give everyone a couple of days to propose remaining ideas for it?17:08
andreafjaypipes: +1 it's a good idea to have a formal walkthrough17:08
sdaguethen we can figure out what's missing from the track that we really should have17:08
donaldngo_hpwe'll have to wait around for the jenkins run to complete 30-40 minutes17:08
jaypipesandreaf: yeah, I think so too, so we have at least some material to save and publish uip on openstack.org for interested parties in the future.17:08
jaypipessdague: yes, totally. I think that's a great idea.17:09
davidkranzsdague: Sounds good.17:09
jaypipes#action jaypipes to send out email to dev and QA list for input on QA track and pointing to next week as the meeting to finalize17:09
maliniPardon my ignorance..But is Tempest going to be/is the  framework for individual projects tests as well ?17:09
andreafjaypipes: do we have a starting point already for such documentation / session?17:09
jaypipesmalini: integration tests, not unit tests.17:09
jaypipesandreaf: https://etherpad.openstack.org/havana-adding-projects-to-tempest17:10
sdaguemalini: right, unit tests go back in the project trees directly17:10
rohitkjaypipes: I just added a section in there that I feel could be documented17:10
jaypipesrohitk: excellent, thx :)17:10
davidkranzjaypipes: I think malini question is relevant.17:10
davidkranzjaypipes: Most of the tempest tests are actually functional regression tests.17:10
davidkranzjaypipes: There is more overlap with unit tests than would be ideal.17:11
davidkranzI discussed this with ayoung in the context of new keystone tests.17:11
sdaguedavidkranz: yeh, well I think that's design summit topic material as well17:11
davidkranzsdague: Agreed.17:11
sdaguein reality new comers need to realize we haven't figured this all out yet :)17:11
jaypipesdavidkranz: I view them as functional integration tests because Tempest isn't mocking or assuming anything about the environment... it's just testing that the environment you run it against functions appropraiatyely.17:11
sdagueso we'll have some guidelines on the good kinds of stuff to day17:11
dwalleckjaypipes: ++17:12
sdagueto add... that should be17:12
jaypipesdavidkranz: I agree about the overlap of regression testing and unit tests, true.17:12
jaypipesdavidkranz: if you are referring to negative tests currently in tempest17:12
ayoungWe have a couple needs/process improvements we can do on this17:12
malinisdague: tht is good to know :) I am an openstack newbie & was having a hard time figuring out the Openstack way of doing QA17:12
davidkranzjaypipes: Yes, and also that as both unit tests and tempest tests try to become more complete there is potential wasted effort.17:13
jaypipesmalini: embrace the chaos :)17:13
sdaguemalini: yeh, we evolve it over time to get better on each release17:13
jaypipesdavidkranz: completely agreed.17:13
davidkranzjaypipes: I will put in a summit topic for this.17:13
jaypipesdavidkranz: I was going to recommend that, thank you.17:13
sdagueok, so lets table the rest of this for next week - for summit discussions17:13
jaypipes++17:13
jaypipessdague: you lead, sir.17:13
sdaguewhat about things we need to get on top of right now? like important reviews or bugs17:13
jaypipessdague: since I was absent last week, please go ahead and lead the meeting, since I've been away from reviews.17:14
jaypipessdague: sorry to put you on the spot :(17:14
donaldngo_hpcan we get this blueprint approved: https://blueprints.launchpad.net/tempest/+spec/update-expected-exception-tests17:14
sdagueoooff, as have I most of the week. :)  anyway... what about the v3 keystone tests?17:14
jaypipessdague: shall we consider donaldngo_hp's BP first?17:15
sdaguethere were some tests in the queue, but they changed v2 to v3, so dropped v2 testing17:15
sdaguesure17:15
jaypipesI personally have no problems supporting the BP. Glad to see agreement on doing exception assertions.17:15
sdagueI'm +1 on that blueprint17:15
ravikumar_hpsdague: we are following folders - V2 & v317:15
jaypipesOK, ghow about this... does anyone OBJECT to the above blueprint?17:16
jaypipes#link https://blueprints.launchpad.net/tempest/+spec/update-expected-exception-tests17:16
rohitkravikumar_hp: Is this also going to remove the usage of the exception decorators?17:16
jaypipesdonaldngo_hp: ^^17:16
sdaguerohitk: can you give an example?17:16
jaypipessdague: rohitk is asking whether the @raises decorator is going away.17:17
donaldngo_hpyea what would be an example17:17
rohitkjaypipes: right17:17
donaldngo_hpthis blueprint basically reduces 4+ lines of code into 117:17
mtreinishrohitk: do we have raises decorators in tempest?17:17
rohitkI was interested to know if we should follow a standard practice17:17
jaypipesdonaldngo_hp: nah... rohitk is asking about the third way we currently assert exceptions, which is using the @raises unittest2/nose decorator17:17
sdaguerohitk: is that used somewhere?17:18
rohitksdague: I haven't checked lately, but just recollecting, do correct me if they're already removed17:18
sdaguerohitk: they aren't in there that I can see17:18
davidkranzDitto.17:18
rohitksdague: that's great then, thanks for correcting17:18
sdagueI think donaldngo_hp's bp is a good cleanup17:18
rohitk+117:18
sdagueand the right direction17:18
donaldngo_hpmaybe we can enforce this through tox of having a singlular way of doing exception assertions?17:19
sdagueI could see us doing additional things after that, but let's get this cleanup done17:19
*** dontalton has joined #openstack-meeting17:19
jaypipesOK, sounds like an approve, then? shall I approve it?17:19
donaldngo_hpfor future code submissions17:19
sdaguejamespage: +217:19
sdaguejaypipes: +217:19
jaypipesdone.17:19
jaypipesdonaldngo_hp: go for it, man :)17:19
donaldngo_hpmy guys can take care of this please assign it to me17:19
donaldngo_hpcant seem to edit it17:20
sdaguedonaldngo_hp: yeh, lets focus on things that we can do near term. Too often we come up with bigger plans that don't get done, this one is really straight forward, which is nice17:20
*** adjohn has joined #openstack-meeting17:20
jaypipesdonaldngo_hp: done.17:20
donaldngo_hpcool17:20
jaypipes#topic Keystone tests v2/v317:20
*** openstack changes topic to "Keystone tests v2/v3 (Meeting topic: qa)"17:20
*** SergeyLukjanov has joined #openstack-meeting17:20
donaldngo_hpsdague: agreed17:20
jaypipessdague: you had a q for ravikumar_hp17:20
sdagueyeh, ravikumar_hp, you are going to redo the patches with supporting both versions of the api, right?17:21
sdaguethat was the major complaint on the previous versoin17:21
*** dripton_ has joined #openstack-meeting17:21
ravikumar_hpsdague: yes. Based on the review feedback , going to resubmit17:21
*** dripton has quit IRC17:22
sdagueok, great17:22
ravikumar_hpthat supports both V2 & v317:22
sdagueso I'm good on that, once we see the new reviews17:22
jaypipesalrighty.17:23
sdaguemaurosr / mtreinish: you guys have the link to the list of needed tests?17:23
mtreinishsdague: this one https://etherpad.openstack.org/MissingTempestTests17:23
mtreinish?17:23
sdagueyep17:23
dolphmi don't follow all the tempest reviews, but would appreciate being added to anything relevant :)17:23
sdaguethat's worth sharing around for people looking for easy stuff17:23
sdaguedolphm: awesome, will do17:23
*** rafaduran1 has left #openstack-meeting17:24
mtreinishsdague: I think everything currently on it is covered or invalid17:24
mtreinishexcept for some xml tests17:24
sdaguemtreinish: ok, I guess we need some more generation :)17:24
jaypipes++17:25
*** matelakat has quit IRC17:25
sdagueok, honestly, that was much topic list :) sorry for not being more organized this week17:25
mtreinishsdague: I put a link for a quick howto on the top of that page17:25
donaldngo_hpi thought there was going to be a write up on how to generate this document?17:25
jaypipesmtreinish: ty, very useful.17:25
mtreinishdonaldngo_hp: https://etherpad.openstack.org/CoverageAnalysisHowto it's on the top of that missing test list17:25
mtreinishdonaldngo_hp: honestly it's pretty straightforward, just a bit time consuming17:26
jaypipesWe need to do similar for Keystone and Quantum, IMHO... but I believe it would need to be manual, right mtreinish, since those projects do not include the coverage middleware, IIRC17:26
sdagueright, that's a good thing to float in maybe a cross project track at summit17:27
mtreinishjaypipes: yeah, the coverage extension is only on nova17:27
jaypipeskk17:27
donaldngo_hpmtreinish: thanks, I'll try to give it a go through and update the etherpad. how often should we do this?17:27
sdagueas it would be nice to get something like the coverage extension into the other projects for thiat17:27
jaypipesright17:27
mtreinishdonaldngo_hp: not very frequently, it shouldnt change that much once we get good coverage17:28
jaypipesmtreinish: lol, at the rate the upstream projects add new stuff... ;)17:28
sdagueheheh17:28
sdagueyeh, we only added 20 extensions to nova this cycle :P17:28
jaypipesright :)17:29
jaypipesthere are a bunch of quantum-related reviews in the queue..17:29
*** markwash has joined #openstack-meeting17:29
sdagueoh, quantum's a good topic. It would be nice if we could get some engagement from that team to get full tempest functional17:30
*** reed has quit IRC17:30
*** ivasev has joined #openstack-meeting17:30
jaypipessdague: I've seen a few folks talking -- mnewby and a few others -- but it still seems like full tests are a ways away.17:30
sdagueyeh17:30
*** dwalleck has quit IRC17:31
sdaguemaybe for summit we try to get a tempest session in the quantum track?17:31
sdaguedrive the conversation over there17:31
jaypipessdague: probably a good idea, yes.17:31
mlavallesdague: I attend the Quantum meeting every week. I will birng the proposal up next Monday17:31
sdaguemlavalle: thanks!17:32
jaypipesmlavalle: thx!17:32
jaypipesOK, well besides open reviews, which we all need to get to, are there any other open topics folks wish to discuss?17:32
jaypipes#topic Open discussion17:32
*** openstack changes topic to "Open discussion (Meeting topic: qa)"17:32
* jaypipes wonders how the runtime is doing?17:33
ravikumar_hpjaypipes: can we add tests for incubated projects17:33
ravikumar_hplike DbaaS17:33
sdaguejaypipes: on sec, I can tell you17:33
jaypipesravikumar_hp: DBaaS is incubated?17:33
ravikumar_hpof course separate folders .17:33
sdagueravikumar_hp: yeh, I don't think it's incubated17:33
sdagueso I'd say we stay away from that for now17:34
ravikumar_hpI am not sure . Reddwardf , and Atlas LbaaS17:34
jaypipesravikumar_hp: Atlas surely is not... it's essentially being replaced with Quantum LBaaS17:34
sdagueuntil it's in the incubation path formally, I don't think we should be putting things in tempest17:34
sdaguethere is only so much review time to go around17:34
davidkranzsdague: Agreed, unless a project member wants to step forward.17:34
jaypipesravikumar_hp: I'd say doing it for DBaaS would only be slightly easier since it is, AFAIK, able to be setup via Devstack.17:35
jaypipesravikumar_hp: that said, I don't really feel like making the undertaking on that until incubation is formal17:35
sdaguedavidkranz: even if they do, we have to put some bounds on it, because the core team still needs to take responsibility for code in tempest17:35
jaypipeslike sdague said, only so much time...17:35
ravikumar_hpokay . we will wait17:35
sdaguejaypipes: runtime is about the same 35 - 40 mins on the hp cloud nodes17:36
jaypipessdague: kk17:36
jaypipessdague: are we not yet doing parallel testr runs?17:36
mtreinishsdague: what about the rackspace cloud?17:36
sdaguewe are not17:36
jaypipeschris yeoh still working on that?17:36
sdaguemtreinish: rackspace isn't in the pool right now17:36
jaypipesmtreinish: it's similar it seems17:36
*** reed has joined #openstack-meeting17:36
jaypipessdague: no?17:37
jaypipesinteresting... when did that happen?17:37
mtreinishsdague: ok17:37
sdaguejaypipes: so in order to do tempest parallel sanely, we need to get to central resource management17:37
jaypipessdague: yup.17:37
sdagueso that's mostly going to be design summit discussions to figure out how we finish it17:37
jaypipessdague: ok.17:37
*** colinmcnamara1 has joined #openstack-meeting17:37
jaypipessdague: though having tests run entirely in their own tenant should enable parallel execution, no?17:38
sdaguebetween now and then we're trying to refactor so things like the create_server / create_image calls go to some central resource allocation / deallocation points17:38
sdaguejaypipes: it could, but it won't be faster17:38
jaypipessdague: how so?17:38
sdaguebecause of the amount of work we do in setUpClass17:38
*** saschpe has joined #openstack-meeting17:38
sdagueand testr splits at the test level, not the class level17:39
*** dragondm_ has joined #openstack-meeting17:39
jaypipessdague: right, I understand that part17:39
sdagueit's a devils in the details thing17:39
jaypipesya17:39
*** lbragstad1 has joined #openstack-meeting17:39
sdagueso if we do some progressive refactoring of the resource allocators, so we get them all to a couple of central points17:39
afazekasWe could give an additional chance to nose parallel.17:39
sdaguewe can then use those to build our own testr "scheduler"17:39
sdaguewhich will give us the optimizing we need17:40
jaypipesk17:40
sdaguewhich, honestly, is sane regardless, because we'll have central cleanup17:40
jaypipesafazekas: you are welcome to show a POC for that. I tried three times and ran into bugs in nose each time.17:40
sdagueyeh, the reality is moving the resource allocations to common paths will help any solution17:40
sdagueand then figured we could hash out the last bits in person at summit17:41
jaypipessure17:41
sdagueso, sadly, the promiss of having it for grizzly was not true17:41
afazekasjaypipes: Ok17:41
sdaguebut havana-1 seems doable17:42
jaypipessdague: underpromise... overdeliver.17:42
jaypipessdague: let's say Havana final ;)17:42
sdagueheh17:42
sdaguesure17:42
jaypipesOK, any other topics before we break?17:43
davidkranzjaypipes: Nope.17:43
sdaguenot from me17:43
jaypipesOK, folks have a good one. I'll start on the email about next week's meeting and the design summit.17:44
jaypipes#endmeeting17:44
ravikumar_hpnope17:44
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"17:44
openstackMeeting ended Thu Mar  7 17:44:07 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-03-07-17.00.html17:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-03-07-17.00.txt17:44
openstackLog:            http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-03-07-17.00.log.html17:44
*** rohitk has quit IRC17:44
*** jcooley_ has joined #openstack-meeting17:44
*** mlavalle has left #openstack-meeting17:44
*** chunwang has quit IRC17:45
*** dwcramer has quit IRC17:45
*** colinmcnamara has quit IRC17:45
*** lbragstad has quit IRC17:45
*** derekh has quit IRC17:45
*** saschpe_ has quit IRC17:45
*** jcooley has quit IRC17:45
*** kmartin has quit IRC17:45
*** dragondm has quit IRC17:45
*** spn_ has quit IRC17:45
*** dragondm_ is now known as dragondm17:45
*** jcooley_ is now known as jcooley17:45
*** donaldngo_hp has quit IRC17:46
*** estebang9 has joined #openstack-meeting17:47
*** thunquest has joined #openstack-meeting17:48
*** gary_th has quit IRC17:49
*** dscannell has quit IRC17:49
*** derekh has joined #openstack-meeting17:51
*** dwcramer has joined #openstack-meeting17:51
*** n0ano has quit IRC17:52
*** lglenden has joined #openstack-meeting17:52
*** n0ano has joined #openstack-meeting17:53
*** koolhead17 has quit IRC17:54
*** rellerreller has joined #openstack-meeting17:55
*** mestery has joined #openstack-meeting17:56
*** colinmcnamara1 has quit IRC17:56
*** bdpayne has quit IRC17:56
*** bdpayne has joined #openstack-meeting17:57
*** DanD has quit IRC17:57
*** derekh has quit IRC17:59
bdpayne#startmeeting OpenStack Security Group18:00
openstackMeeting started Thu Mar  7 18:00:06 2013 UTC.  The chair is bdpayne. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
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
bdpaynegood morning OSSG18:00
*** mtesauro has joined #openstack-meeting18:00
bdpayneUnfortunately, I've been sick this past week and didn't make progress on my action items from last week18:01
*** dscannell has joined #openstack-meeting18:01
bdpayneSo, I will take those as action items for next week… and hopefully actually get them done this time around18:01
bdpayneare there OSSG people present?18:03
mtesauroI'm not sure who else is here from OSSG but I posted a tool to help with API testing18:03
lglendenI'm here18:03
bdpayneexcellent, good morning guys (and gals)18:03
rellerrellerI'm sort of here.  Attending two meetings at once.18:03
*** eglynn has quit IRC18:03
bdpaynemtesauro can you tell us more about your tool?18:04
mtesauroIts a simple wrapper for curl which allows you to put common arguments and API endpoints into a config so you curl commands are WAY shorter.18:04
mtesauro+link https://github.com/mtesauro/jerry-curl18:04
estebang9good morning from cansec18:04
mtesaurothere are pre-compiled binaries for Linux, OSX, FreeBSD and Windows at http://appseclive.org/apt/jerry-curl/18:05
mtesauro32 and 64 bit18:05
bdpaynenifty… that looks nice18:05
bdpayneyou thinking of using that to stress test service endpoints?18:05
*** diogogmt has joined #openstack-meeting18:06
mtesauroI find myself doing doing 1 off API calls and got tired of all that typing.18:06
bdpayneha, yeah I agree18:06
mtesauro@stress-testing - you certainly could do that18:06
*** dolphm has quit IRC18:06
bdpayneI'll pass this around… I know others that might like it18:06
mtesauroFeel free to share as widely as you like18:06
*** annegentle has joined #openstack-meeting18:07
*** Mandell has joined #openstack-meeting18:07
*** koolhead17 has joined #openstack-meeting18:07
bdpayneestebang9 how is cansec?18:07
estebang9good stuff. there will be some interesting cloud sec talks later (Oded).18:07
bdpaynecool, perhaps you could give us a summary of the good stuff next week?18:08
noslzzpI'm here.18:08
bdpayneI bet that would be of general interest to the group here18:08
*** johnthetubaguy has joined #openstack-meeting18:08
estebang9definitely.18:08
bdpaynegreat, thanks18:08
bdpayne#action estebang9 to provide cansec summary to OSSG meeting on Mar 1418:09
estebang9:)18:09
bdpayneso, there's a few things worth discussing today18:09
bdpayneI'm thinking hardening guide and rbac… anything else?18:09
bdpayne#topic hardening guide18:10
*** openstack changes topic to "hardening guide (Meeting topic: OpenStack Security Group)"18:10
bdpaynethis will be a brief topic today18:10
bdpaynebasically, I'm supposed to convert the guide to markdown18:10
*** johnthetubaguy1 has quit IRC18:10
bdpayneI was curious if anyone could point me to a nice long doc written in markdown that I could use as a guide18:10
bdpayneor, alternatively, if there's someone that would be interested in doing the conversion18:11
*** dosaboy has quit IRC18:11
*** spzala has joined #openstack-meeting18:11
*** dosaboy has joined #openstack-meeting18:11
noslzzpi can help with the conversion.18:11
bdpaynenoslzzp thanks18:11
bdpaynethe content in there right now is basically just following the (old) outline18:12
bdpayneso perhaps a PR to move the repo to markdown with the new outline18:12
*** johnthetubaguy has quit IRC18:12
bdpayneseems like the right next step18:12
noslzzpIndeed.18:12
bdpayne#action noslzzp to put up PR for converting guide to markdown18:12
bdpaynebtw, did you guys see http://docs.openstack.org/ops/ ?18:12
bdpaynethey wrote a book in 5 days18:13
noslzzpYes.18:13
*** estebang9 has quit IRC18:13
noslzzpWhat's our problem? :)18:13
bdpayneheh, I know!18:13
bdpaynethis has actually motivated me a bit… I'm open to suggestions on how we might be able to move ahead like this18:13
bdpayneor even if a full out documentation sprint effort would be useful here18:14
bdpaynewould people be interested in taking a week to travel somewhere and focus exclusively on this hardening guide during that time to basically knock out v1?18:14
*** shengjie has quit IRC18:15
bdpayneI'll take the silence as a no18:15
*** esiely has joined #openstack-meeting18:15
*** johnthetubaguy has joined #openstack-meeting18:16
bdpaynebut I remain open to creative ideas here :-)18:16
bdpayneok… I'd like to chat about rbac a little too18:16
bdpayne#topic rbac18:16
*** openstack changes topic to "rbac (Meeting topic: OpenStack Security Group)"18:16
bdpayneLast week when I mentioned rbac, there seemed to be some interest18:16
bdpayneI wanted to pick your brains a little more18:16
bdpaynehow do you imagine rbac in openstack being useful to you?18:17
bdpayneI'd like to hear different takes to help define how we move forward here18:17
bdpayneI work primarily with private clouds… and I'm interested in RBAC for allowing for a smoother integration between the cloud and the existing enterprise… for example putting controls on which users can get certain floating IPs or which users can launch certain images, etc18:18
bdpaynewhat do you guys think about when you are thinking rbac?18:18
*** gary_th has joined #openstack-meeting18:19
*** darraghb1 has joined #openstack-meeting18:19
*** estebang9 has joined #openstack-meeting18:20
bdpayneany thoughts?18:20
*** mestery has quit IRC18:20
mtesauroIf you had a decent amount of cloud server spun up, you could have the "marketing" group manage one set, the "sales" group another...  I would allow handing out cloud resources to be more like normal IT18:20
*** darraghb has quit IRC18:20
*** DuncanT has quit IRC18:20
*** DuncanT1 has joined #openstack-meeting18:20
mtesauroSame for any part of OpenStack18:21
bdpayneso are you thinking of actually dividing up the physical compute nodes?18:21
bdpayneor just providing better isolation between projects?18:21
noslzzpmy thinking is more along the infrastructure and enforcing/restricting certain interactions.18:21
*** thunquest has quit IRC18:21
bdpaynenoslzzp can you be more specific?18:22
noslzzpmaybe.18:22
bdpayneheh18:23
mtesauroI assume it would be isolation - I saw the RBAC thing at the last OpenStack and that type of thing was what popped into my mind18:23
noslzzpFor example, if the hypervisor was secured, we could use RBAC to verify that the scheduler is authorized to talk to it and what functions are allowed to be invoked.18:23
*** ttrifonov is now known as ttrifonov_zZzz18:24
bdpayneinteresting18:24
bdpaynenoslzzp I think that bridges into some of the trusted compute pools work as well… certainly an area I like as well18:24
noslzzpyes.18:25
bdpayneanyway, this is all helpful18:25
bdpayneI'll continue trying to form some thoughts here and figure out how to best more forward in this space18:25
bdpayneas always, I'm open to suggestions / input18:25
bdpayneI'll try to have something more concrete by next week18:25
bdpayne#action bdpayne to continue work on rbac18:25
bdpayne#topic final words18:25
*** openstack changes topic to "final words (Meeting topic: OpenStack Security Group)"18:25
bdpayneany other thoughts for today?18:26
noslzzpyes..18:26
noslzzpI'm interested in the documentation sprint idea..18:26
noslzzpNothing more. :)18:26
bdpayneok, nice18:27
bdpaynewell, I'll explore that a bit more18:27
bdpayne#action bdpayne to explore documentation sprint idea18:27
lglendenthere's a thread on the dev mailing list on key management that may be of interest18:27
*** ttrifonov_zZzz has quit IRC18:27
lglenden#link http://lists.openstack.org/pipermail/openstack-dev/2013-March/006425.html18:27
mtesaurolink?18:27
mtesaurothanks18:27
bdpayneindeed, thanks lglenden18:27
annegentlebdpayne: I can talk a little bit about what it good to get the book sprint18:28
*** ttrifonov_zZzz has joined #openstack-meeting18:28
annegentleer good/took18:28
bdpayneannegentle thanks, I'll touch base via email18:28
annegentlebdpayne: sounds good18:28
bdpayneok, thanks everyone… I think that's all for today18:29
noslzzpthanks.18:29
bdpayne#endmeeting18:29
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"18:29
openstackMeeting ended Thu Mar  7 18:29:25 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-03-07-18.00.html18:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-03-07-18.00.txt18:29
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-03-07-18.00.log.html18:29
*** ttrifonov_zZzz has quit IRC18:30
*** otherwiseguy has quit IRC18:30
*** rellerreller has quit IRC18:30
*** ttrifonov_zZzz has joined #openstack-meeting18:30
*** mtesauro has left #openstack-meeting18:31
*** garyk has joined #openstack-meeting18:31
*** ttrifonov_zZzz has quit IRC18:32
*** esiely has quit IRC18:32
*** markmcclain has quit IRC18:34
*** johnthetubaguy has quit IRC18:34
*** gyee has quit IRC18:35
*** Manu has joined #openstack-meeting18:35
*** Manu is now known as Guest9340618:35
*** johnthetubaguy has joined #openstack-meeting18:35
*** Guest93406 has quit IRC18:35
*** johnthetubaguy has quit IRC18:36
*** colinmcnamara has joined #openstack-meeting18:36
*** lglenden has quit IRC18:36
*** ttrifonov_zZzz has joined #openstack-meeting18:37
*** ttrifonov_zZzz is now known as ttrifonov18:37
*** ttrifonov_zZzz has joined #openstack-meeting18:37
*** nati_ueno has joined #openstack-meeting18:37
*** maoy has joined #openstack-meeting18:47
*** lbragstad1 has quit IRC18:55
*** mestery has joined #openstack-meeting19:01
*** mdomsch has joined #openstack-meeting19:02
*** otherwiseguy has joined #openstack-meeting19:03
*** vipul is now known as vipul|away19:04
*** danwent has quit IRC19:04
*** danwent has joined #openstack-meeting19:06
*** ayoung has quit IRC19:11
*** MarkAtwood has joined #openstack-meeting19:15
*** dosaboy has quit IRC19:16
*** afazekas has quit IRC19:17
*** johnpur has joined #openstack-meeting19:18
*** lbragstad has joined #openstack-meeting19:19
*** gary_th has quit IRC19:20
*** mkollaro has quit IRC19:20
*** malini has left #openstack-meeting19:21
*** Mandell has quit IRC19:22
*** darraghb1 has quit IRC19:24
*** SergeyLukjanov has quit IRC19:27
*** agentle_ has joined #openstack-meeting19:30
*** MarkAtwood has quit IRC19:31
*** annegentle has quit IRC19:31
*** agentle_ is now known as annegentle19:31
*** Mandell has joined #openstack-meeting19:32
*** sandywalsh has quit IRC19:32
*** dscannell has quit IRC19:33
*** hemna has quit IRC19:34
*** hemna has joined #openstack-meeting19:34
*** sarob has joined #openstack-meeting19:35
*** boris-42 has joined #openstack-meeting19:36
*** markmcclain has joined #openstack-meeting19:43
*** sandywalsh has joined #openstack-meeting19:46
*** lbragstad has quit IRC19:46
*** dscannell has joined #openstack-meeting19:48
*** sandywalsh has quit IRC19:50
*** danwent has quit IRC19:54
*** lbragstad has joined #openstack-meeting19:54
*** woodspa has quit IRC19:56
*** egallen has quit IRC19:57
*** egallen_ has joined #openstack-meeting19:57
*** novas0x2a|laptop has joined #openstack-meeting19:58
*** danwent has joined #openstack-meeting19:59
*** Greg___ has joined #openstack-meeting19:59
*** dolphm has joined #openstack-meeting20:02
*** danwent has quit IRC20:04
*** MarkAtwood has joined #openstack-meeting20:05
*** spzala has quit IRC20:06
*** dguitarbite has left #openstack-meeting20:07
*** colinmcnamara has quit IRC20:08
*** lbragstad has quit IRC20:09
*** donaldngo_hp has joined #openstack-meeting20:09
*** egallen_ has quit IRC20:10
*** lcheng has quit IRC20:12
*** dwcramer has quit IRC20:14
*** egallen has joined #openstack-meeting20:16
*** egallen has quit IRC20:16
*** davidha has joined #openstack-meeting20:19
*** dripton_ is now known as dripton20:25
*** dwcramer has joined #openstack-meeting20:25
*** jog0 has joined #openstack-meeting20:29
*** ayoung has joined #openstack-meeting20:31
*** danwent has joined #openstack-meeting20:32
*** colinmcnamara has joined #openstack-meeting20:35
*** maoy has quit IRC20:36
*** estebang9 has quit IRC20:37
*** pnavarro has quit IRC20:38
*** enikanorov-w has quit IRC20:39
*** obondarev_ has joined #openstack-meeting20:42
*** enikanorov-w has joined #openstack-meeting20:42
*** obondarev has quit IRC20:42
*** topol has quit IRC20:42
*** bdpayne has quit IRC20:49
*** annegentle has quit IRC20:49
*** eglynn has joined #openstack-meeting20:51
*** sdake_ has quit IRC20:51
*** sdake has quit IRC20:52
*** sdake has joined #openstack-meeting20:53
*** dcramer_ has joined #openstack-meeting20:53
*** sdake_ has joined #openstack-meeting20:54
*** Vek has joined #openstack-meeting20:55
*** dwcramer has quit IRC20:57
*** colinmcnamara has quit IRC21:00
* russellb waves21:00
dansmithyo21:00
alexpilottihi guys21:00
driptonhi21:00
*** dcramer_ has quit IRC21:00
*** sarob has quit IRC21:00
boris-42Hi21:00
russellbvishy: around?21:00
* Vek yawns21:01
*** Kharec_ has joined #openstack-meeting21:01
*** dprince has quit IRC21:01
devananda\o21:02
*** annegentle has joined #openstack-meeting21:02
*** Kharec has quit IRC21:02
*** spzala has joined #openstack-meeting21:02
* beagles waves21:02
krtayloro/21:03
russellbhm, no vishy, guess we can start21:03
dansmithoye, are we going to discuss how to increase the number of hours in the day?21:03
dansmithI really want to get going on that21:03
russellbhopefully he can jump in :)21:03
russellbdansmith: +121:03
russellb#startmeeting nova21:03
openstackMeeting started Thu Mar  7 21:03:43 2013 UTC.  The chair is russellb. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:03
*** openstack changes topic to " (Meeting topic: nova)"21:03
openstackThe meeting name has been set to 'nova'21:03
russellb#chair vishy21:03
openstackCurrent chairs: russellb vishy21:03
russellb#link https://wiki.openstack.org/wiki/Meetings/Nova21:03
russellbas you can see on the link, we have no agenda \o/21:04
russellbnap time21:04
Vekdansmith: actually, that's easy; just move to a planet with a slower rotation rate...21:04
russellbI suppose topic of most immediate interest is grizzly-rc121:04
dansmithVek: can I ride with you?21:04
russellb#link https://launchpad.net/nova/+milestone/grizzly-rc121:04
*** READ10 has joined #openstack-meeting21:05
russellbOne thing worth mentioning is the backportable db migrations blueprint that we had on here, that has been removed21:05
russellbvishy realized there was a problem with the plan to merge blank migrations at the end of grizzly and that right thing to do was to merge the blank ones when havana opens21:05
Vekdansmith: If you'll buy the fuel, sure :)21:05
russellbso we just need to make sure we get his patch merged first in havana, before any other migrations21:05
vishyhi21:05
russellbvishy: hi!  was just trying to recap the migrations thing ... *hands it over*21:06
vishyno go ahead21:06
vishy:)21:06
Vekthe migrations thing makes me wish we had alembic in...21:06
*** eglynn has quit IRC21:06
russellbk, well i think that was about it, unless anyone wants to dive into why21:06
driptonVek +121:06
russellbyeah, but at least this gives us *something* for grizzly21:07
Vekoh, I'll grant you that21:07
driptonVek: I'm planning to shove Alembic down various throats at the summit.21:07
russellbha21:07
russellbdripton: didn't you have a patch that had it working or close to it?21:07
Vekdripton: cool :)21:07
Vekwish I could be there, especially now that there's sessions on quotas proposed :/21:07
russellbi guess what you had done was work on auto converting existing migrations?21:07
driptonrussellb: yes, but it's only a 90% solution.  The other 10% is a lot of work.21:08
russellbVek: duuuuuuude, you were missed last time, not going again?  :(21:08
Vekyeah, RS isn't sending me this time either.21:08
Vek(I don't like flying commercial anyway, but it's about a 14 hour trip if I try to fly it on my own...)21:09
russellbTo all employers: if you have someone on whatever-core, you need to send them to the design summit.  that is all.21:09
Vekheh.21:09
Vekto be fair, if I had proposed a session on quotas myself, they probably would have sent me.21:09
russellbVek: what if you propose a design summit session :)21:09
Vekheh :)21:10
russellbso rc121:10
russellbjust one critical bug and comstud is all over it21:11
russellbany other bugs worth discussing here?21:11
*** vipul|away is now known as vipul21:11
* Vek accidentally drops a pin21:12
russellb:)21:12
russellbso I guess we should just fix them all, and that's that21:12
Vekguess so :)21:13
russellbcool.21:13
russellbwell then ... anything else about anything?21:13
russellbmost eventful nova meeting ever21:13
boris-42I would like to move sqlalchemy.utils to common code should I write some blue print?21:13
boris-42blueprint*21:14
Vekboris: probably best, and of course that would be havana work...21:14
russellbto oslo-incubator?21:14
boris-42yeah21:14
* russellb agrees with Vek 21:14
driptonboris-42: Do other projects already use it?21:14
*** dhellmann is now known as dhellmann-afk21:14
* devananda agrees too21:14
devanandakeystone is about to add test_migrations, copied from an older nova version of it21:15
boris-42agrees to with Vek =) but I could write it now=) and do in Havana=)21:15
*** Mr_T has joined #openstack-meeting21:15
devanandaso that may also be worth porting to oslo21:15
driptondevananda: Did you succeed in hoisting a reusable superclass out of test_migrations when you were doing baremetal migrations?21:15
devanandadripton: yep21:16
devanandaboris and i both tackled that21:16
driptondevananda: cool, then we have an obvious candidate21:16
* devananda thinks boris should write up a BP for porting sqlalchemy.utils and migration testing to oslo :)21:18
russellbsounds good to me!21:18
boris-42One more thing. As you know test_db_api doesn't cover all methods...21:18
boris-42for example there is no tests for security_groups at all!21:18
devanandaindeed ....21:18
*** mrunge has quit IRC21:18
boris-42probably there should be also blueprint add missing tests for test_db_api21:18
devananda++21:19
russellbthere's a nova bug about that21:19
driptonthe kind of bug you can never close because you always need more tests21:19
russellbhttps://bugs.launchpad.net/nova/+bug/82863121:19
uvirtbotLaunchpad bug 828631 in nova "nova/db/* almost only tested indirectly" [Low,Confirmed]21:19
russellbopened in August of 201121:19
boris-42^_^21:19
uvirtbotboris-42: Error: "_^" is not a valid command.21:19
devanandano wonder i never saw that bug21:19
* devananda adds a "db" tag to it21:20
Vekheh21:20
boris-42Yeah I think that BP is better idea=)21:20
russellbyeah, maybe ... kind of in that blueprint <-> bug gray area to me21:20
russellbi guess it's not a bug, nothing is broken21:20
russellb:)21:20
russellbfor some definition of broken ...21:21
*** radez is now known as radez_g0n321:21
driptonyou don't know if anything is broken because you don't have a test for it.21:21
boris-42=))21:21
* devananda realizes a new way to eliminate bugs... just delete the tests!21:21
russellbin any case, if you open a bp let's close this bug21:21
boris-42Ok21:21
Vekdevananda: that would make the test suite run a whole lot faster, too!21:21
devananda;)21:21
driptonDo we have test coverage viewable somewhere out of Jenkins?21:22
russellbdripton: yes ..... somewhere ........21:22
boris-42eyes=)21:22
russellbrace to find it!21:22
russellbhttps://jenkins.openstack.org/job/nova-coverage/21:23
clarkblogs.openstack.org/shortsha/follow/the/path/to/nova-coverage21:23
*** dhellmann-afk is now known as dhellmann21:23
*** dhellmann is now known as dhellmann-afk21:24
russellbclarkb: it's like you have advanced IRC conversation highlighting to alert you when you need to appear with a -infra related link :)21:24
driptonI see that page but not any actual useful coverage results.  Maybe they're just hiding; maybe we need to install the cobertura plugin and do the right magic to convert Python test results to Java XML format so it can display them.21:24
boris-42oO21:24
boris-42https://review.openstack.org/#/c/23660/21:24
russellbexample: http://logs.openstack.org/e237698/post/nova-coverage/5635/cover/21:25
clarkbdripton: no, we actually stopped doing that with jenkins because jenkins uses too much resources to do it21:25
clarkbinstead we generate the html reports then copy them to the log server21:25
devananda#link http://logs.openstack.org/e237698/post/nova-coverage/5635/cover/nova_db_sqlalchemy_api.html21:25
driptonclarkb: makes sense, but it makes it hard to find them if you don't already know where to look21:26
russellboverall total: 80%21:26
boris-42I don't believe =)21:26
Vek80% is easy.  100% is difficult :)21:26
russellb88% for the db api :)21:26
clarkbdripton: ya21:26
dripton100% is unnecessary.  80% is actually pretty damn good.21:26
russellbdripton: but now you know where it is!21:26
driptonBookmarking...21:27
Vekheh.21:27
* devananda notices the number of exceptions not getting tested in db/api21:27
*** lbragstad has joined #openstack-meeting21:27
*** MarkAtwood has quit IRC21:27
russellbclarkb: is this just unit test coverage, or is this after running tempest too21:27
Vekthat would be an interesting statistic...21:28
clarkbrussellb: that is just unittest specific21:28
russellbcool21:28
clarkbthe tempest coverage is its own thing (a daily job iirc)21:28
russellbhttps://jenkins.openstack.org/job/periodic-tempest-devstack-coverage-vm-full/21:29
* russellb guesses that's it ...21:29
*** topol has joined #openstack-meeting21:29
clarkbyup that looks right21:29
russellbhttp://logs.openstack.org/periodic/21:30
russellbhttp://logs.openstack.org/periodic/periodic-tempest-devstack-coverage-vm-full/58/logs/coverage-report/21:30
russellbthat says 21%21:31
clarkbrussellb: I think it may only be able to collect nova-api coverage right now21:31
*** koolhead17 has quit IRC21:31
clarkb(but I may be mistaken)21:31
russellbclarkb: ok.  i know there was some work to support all services, don't remember status21:32
russellbdansmith: do you know?  wasn't that a coworker of yours?21:32
dansmithrussellb: mtreinish yeah21:32
driptonclarkb: it looks like it's crawling all the unit tests, not just the API21:32
clarkbits generating results for all of nova/ but at runtime only runs within nova-api21:33
driptonclarkb: ok, got it21:33
*** annegentle has quit IRC21:33
russellbso there's the long answer to "do we have code coverage reports"  :)21:34
*** MarkAtwood has joined #openstack-meeting21:34
russellbVek reminds us all that we need to help review python-novaclient patches, heh21:34
*** colinmcnamara has joined #openstack-meeting21:35
russellbthis URL is your friend for that: https://review.openstack.org/#/q/status:open+(project:openstack/nova+OR+project:openstack/python-novaclient)+branch:master,n,z21:35
Vek:)21:35
driptontwo bookmarks in one meeting21:35
russellbthat's productivity of some sort :)21:36
Vekheh21:36
russellbalso need to be looking at python-novaclient bugs21:36
russellband btw, if you want to close out some bugs and feel good, sort bugs by age and start at the oldest21:36
russellblots of stuff that's not even applicable anymore21:36
russellbthe cleaner the bug list, the more useful it is21:37
russellbanything else?21:37
Vek*nod*21:37
russellbguess we can close out then ... thanks everyone21:39
mtreinishclarkb, russellb: it covers all the services now21:39
russellbmtreinish: nice!21:39
russellbmtreinish: when looking at the coverage results, it looked like it did21:39
mtreinishbut there is still a bug with the coverage module and eventlet so some of the results look really weird21:39
Veklovely.21:40
russellbeventlet \o/21:40
* Vek used gevent for Tendril; that looks nice...21:40
mtreinishfor example: http://logs.openstack.org/periodic/periodic-tempest-devstack-coverage-vm-full/57/logs/coverage-report/nova_virt_libvirt_driver.html21:40
jog0russellb: are we gonna have a summit session on eventlet  and its future?21:40
russellbjog0: only if someone is motivated enough to make that a priority to work on21:41
russellbjust complaining about it isn't hugely useful :)21:41
russellbIMO ....21:41
driptonThere's no free lunch.  If you want to have asynchronous code that looks like synchronous code then you're going to have a 90% solution and 10% bugs.21:41
jog0russellb: there will be an  eventlet session at the conference that may be useful21:41
VekProbably for the 'i' or 'j' summits, we should be seriously thinking about how to support python3 (if not before then...)21:41
driptonIf you want the 100% solution you have to make it explicit and then your code will be ugly.21:41
jog0so gevent isn't a good option to discuss for H?21:42
russellbVek: indeed21:42
driptonIsn't gevent pretty much the same model as eventlet with slight differences under the hood?21:42
*** estebang9 has joined #openstack-meeting21:42
Vekdripton: it's forked from eventlet, in fact, IIRC21:42
VekI believe it has v6 support available, too, though eventlet is likely to add that before too much longer (if they haven't already)21:43
*** MarkAtwood has quit IRC21:43
russellbthere are some other ways we could approach this other than just forklifting eventlet21:43
Veklast I looked, though, the 1.x series was going to use a completely different core from the 0.x series...21:43
russellblike, say, try to convert only the nova-compute service to native threads21:44
jog0russellb: true21:44
russellbor nova-conductor21:44
russellbnova-conductor's entire job is db access ... which is kinda hacky with eventlet21:45
jog0also there is the sqlA discussion that ties in to this21:45
russellbyes21:45
* Vek nods21:45
russellbgood times21:45
jog0sorry for derailing the meeting21:46
russellbnah, we were pretty much done I think21:46
Veksounds like we have things to do well beyond the 'm' release :)21:46
russellbone last thing i want to mention ... mikal really wanted to be here, but couldn't because of orientation at RAX21:46
russellbso he's not just avoiding us :)21:46
Vek:)21:46
*** dscannell has quit IRC21:47
dansmithfor some reason,21:47
russellbalright, thanks everyone!21:47
*** markmcclain has quit IRC21:47
* russellb halts again21:47
dansmithwhen you said "orientation", all I could think of was that the aussie was upside down21:47
Vek*rotcl*21:47
devanandaheh21:47
*** gyee has joined #openstack-meeting21:47
Vekwe call it "rookieO", and you're probably right about it being upside down...21:47
russellbha, sounds like he's enjoying it21:48
russellbhe's actually on this side of the earth right now21:48
russellbk, bye!21:49
russellb#endmeeting21:49
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"21:49
openstackMeeting ended Thu Mar  7 21:49:11 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-03-07-21.03.html21:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-03-07-21.03.txt21:49
openstackLog:            http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-03-07-21.03.log.html21:49
* Vek waves21:49
*** Vek has left #openstack-meeting21:49
*** donaldngo_hp has quit IRC21:50
*** markmcclain has joined #openstack-meeting21:54
*** dcramer_ has joined #openstack-meeting21:58
*** estebang9 has left #openstack-meeting21:59
*** sdake has quit IRC21:59
*** dolphm has quit IRC21:59
*** dolphm has joined #openstack-meeting22:01
*** dscannell has joined #openstack-meeting22:04
*** dscannell1 has joined #openstack-meeting22:04
*** boris-42 has quit IRC22:05
*** boris-42 has joined #openstack-meeting22:06
*** mestery has quit IRC22:06
*** eglynn has joined #openstack-meeting22:09
*** dcramer_ has quit IRC22:09
*** dontalton has quit IRC22:10
*** spzala has quit IRC22:11
*** ryanpetrello has quit IRC22:12
*** markmcclain has quit IRC22:20
*** hemna has quit IRC22:23
*** ivasev has quit IRC22:23
*** hemna has joined #openstack-meeting22:23
*** topol has quit IRC22:23
*** eglynn has quit IRC22:26
*** john5223 has quit IRC22:27
*** mtreinish has quit IRC22:34
*** esker has quit IRC22:35
*** dolphm has quit IRC22:39
*** sdake_ has quit IRC22:40
*** colinmcnamara has quit IRC22:41
*** diogogmt has quit IRC22:44
*** kmartin has joined #openstack-meeting22:45
*** kmartin has quit IRC22:45
*** kmartin has joined #openstack-meeting22:45
*** markmcclain has joined #openstack-meeting22:48
*** sarob has joined #openstack-meeting22:52
*** terryg has joined #openstack-meeting22:54
*** zul has quit IRC22:55
*** zul has joined #openstack-meeting22:56
*** stevemar has quit IRC22:58
*** dontalton has joined #openstack-meeting22:58
*** pony has joined #openstack-meeting22:59
*** tomoe_ has joined #openstack-meeting23:02
*** dscannell1 has quit IRC23:04
*** sdake_ has joined #openstack-meeting23:05
*** cody-somerville has quit IRC23:05
*** woodspa has joined #openstack-meeting23:06
*** woodspa has quit IRC23:06
*** woodspa has joined #openstack-meeting23:08
*** markwash has quit IRC23:09
*** topol has joined #openstack-meeting23:11
*** Gordonz has quit IRC23:11
*** terryg has quit IRC23:12
*** terryg has joined #openstack-meeting23:12
*** sacharya has quit IRC23:13
*** dscannell has joined #openstack-meeting23:22
*** dscannell has quit IRC23:23
*** boris-42 has quit IRC23:32
*** fnaval has quit IRC23:33
*** tongli has quit IRC23:33
*** dontalton has quit IRC23:35
*** dolphm has joined #openstack-meeting23:39
*** cody-somerville has joined #openstack-meeting23:43
*** dolphm has quit IRC23:44
*** mattray has quit IRC23:45
*** colinmcnamara has joined #openstack-meeting23:45
*** reed has quit IRC23:45
*** thingee has joined #openstack-meeting23:49
*** thingee has left #openstack-meeting23:49
*** hemna has quit IRC23:52
*** hemna has joined #openstack-meeting23:52
*** fnaval has joined #openstack-meeting23:57
*** nati_ueno has quit IRC23:58

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