Wednesday, 2012-11-07

*** jrd has joined #openstack-meeting00:01
*** cp16net|away is now known as cp16net00:12
*** sandywalsh has quit IRC00:18
*** markmcclain has quit IRC00:19
*** huats has quit IRC00:20
*** huats has joined #openstack-meeting00:20
*** huats has quit IRC00:20
*** huats has joined #openstack-meeting00:20
*** dendrobates is now known as dendro-afk00:22
*** mnewby has joined #openstack-meeting00:23
*** dendro-afk is now known as dendrobates00:24
*** mnewby_ has quit IRC00:25
*** samkottler|out is now known as samkottler00:27
*** sarob has quit IRC00:34
*** jrodom has quit IRC00:34
*** markwash has quit IRC00:36
*** metral has joined #openstack-meeting00:39
*** littleidea has quit IRC00:40
*** markwash has joined #openstack-meeting00:40
*** cp16net is now known as cp16net|away00:40
*** dolphm has joined #openstack-meeting00:41
*** reed has quit IRC00:42
*** littleidea has joined #openstack-meeting00:42
*** littleidea has left #openstack-meeting00:42
*** ryanpetr_ has joined #openstack-meeting00:42
*** rkukura has quit IRC00:44
*** ryanpetrello has quit IRC00:45
*** maurosr has joined #openstack-meeting00:45
*** metral has quit IRC00:48
*** shardy_afk has quit IRC00:49
*** dolphm has quit IRC00:49
*** maurosr has quit IRC00:50
*** cp16net|away is now known as cp16net00:56
*** maurosr has joined #openstack-meeting00:58
*** rkukura has joined #openstack-meeting01:00
*** mnewby has quit IRC01:03
*** mnewby has joined #openstack-meeting01:04
*** jog0 has joined #openstack-meeting01:06
*** patelna has quit IRC01:10
*** ryanpetr_ has quit IRC01:11
*** asalkeld has quit IRC01:15
*** sandywalsh has joined #openstack-meeting01:15
*** hemna_ has joined #openstack-meeting01:16
*** danwent has quit IRC01:18
*** hemna has quit IRC01:19
*** sandywalsh has quit IRC01:19
*** asalkeld has joined #openstack-meeting01:21
*** maurosr has quit IRC01:22
*** derekh has joined #openstack-meeting01:22
*** gyee has quit IRC01:23
*** eglynn__ has joined #openstack-meeting01:25
*** ryanpetrello has joined #openstack-meeting01:26
*** eglynn_ has quit IRC01:28
*** salv-orlando has quit IRC01:39
*** Shengjie_Min has quit IRC01:40
*** dwcramer has joined #openstack-meeting01:41
*** s0mik has quit IRC01:42
*** s0mik has joined #openstack-meeting01:43
*** maurosr has joined #openstack-meeting01:44
*** s0mik has quit IRC01:45
*** mnewby_ has joined #openstack-meeting01:45
*** anniec has quit IRC01:47
*** mnewby has quit IRC01:48
*** mnewby_ is now known as mnewby01:48
*** anniec has joined #openstack-meeting01:48
*** maurosr has quit IRC01:50
*** mnewby has quit IRC01:56
*** dolphm has joined #openstack-meeting01:57
*** jog0 has quit IRC02:02
*** littleidea has joined #openstack-meeting02:09
*** Gordonz has joined #openstack-meeting02:12
*** derekh has quit IRC02:13
*** asalkeld has quit IRC02:16
*** asalkeld has joined #openstack-meeting02:17
*** adjohn has quit IRC02:27
*** dwcramer has quit IRC02:29
*** dwcramer has joined #openstack-meeting02:42
*** cp16net is now known as cp16net|away02:44
*** anniec has quit IRC02:45
*** anniec has joined #openstack-meeting02:45
*** zbitter has joined #openstack-meeting02:48
*** sarob has joined #openstack-meeting02:48
*** mnewby has joined #openstack-meeting02:48
*** zaneb has quit IRC02:49
*** cp16net|away is now known as cp16net02:58
*** mnewby has quit IRC03:05
*** s0mik has joined #openstack-meeting03:18
*** jrodom has joined #openstack-meeting03:19
*** anniec has quit IRC03:26
*** gongysh has quit IRC03:37
*** matiu has quit IRC03:38
*** gongysh has joined #openstack-meeting03:49
*** markmcclain has joined #openstack-meeting03:58
*** littleidea has quit IRC03:59
*** rushiagr has joined #openstack-meeting04:06
*** rushiagr has quit IRC04:16
*** rushiagr has joined #openstack-meeting04:17
*** sarob has quit IRC04:18
*** littleidea has joined #openstack-meeting04:22
*** rushiagr has quit IRC04:26
*** matiu has joined #openstack-meeting04:27
*** matiu has joined #openstack-meeting04:27
*** dwcramer has quit IRC04:32
*** Gordonz_ has joined #openstack-meeting04:44
*** dwcramer has joined #openstack-meeting04:45
*** Gordonz has quit IRC04:47
*** koolhead17 has joined #openstack-meeting04:49
*** matiu_ has joined #openstack-meeting04:53
*** matiu_ has joined #openstack-meeting04:53
*** matiu has quit IRC04:53
*** ryanpetrello has quit IRC04:57
*** ryanpetrello has joined #openstack-meeting05:00
*** rkukura has quit IRC05:02
*** markwash has quit IRC05:09
*** littleidea has quit IRC05:18
*** littleidea has joined #openstack-meeting05:21
*** rkukura has joined #openstack-meeting05:21
*** Mandell has quit IRC05:22
*** garyk has quit IRC05:23
*** markwash has joined #openstack-meeting05:26
*** dolphm has quit IRC05:31
*** koolhead17 has quit IRC05:32
*** samkottler is now known as samkottler|out05:37
*** enikanorov_ has joined #openstack-meeting05:38
*** enikanorov has quit IRC05:39
*** dwcramer has quit IRC05:51
*** metral has joined #openstack-meeting05:54
*** lianhao has joined #openstack-meeting05:58
*** markmcclain has quit IRC05:58
*** ryanpetrello has quit IRC06:07
*** jrodom has quit IRC06:19
*** roadTripper has quit IRC06:41
*** roadTripper has joined #openstack-meeting06:41
*** markwash has quit IRC07:00
*** jfriedly has quit IRC07:02
*** novas0x2a|laptop has quit IRC07:04
*** garyk has joined #openstack-meeting07:05
*** adjohn has joined #openstack-meeting07:08
*** eglynn has joined #openstack-meeting07:09
*** ogelbukh has quit IRC07:10
*** ogelbukh has joined #openstack-meeting07:10
*** eglynn__ has quit IRC07:11
*** rushiagr has joined #openstack-meeting07:16
*** adjohn has quit IRC07:27
*** hemna_ has quit IRC07:39
*** davidha has quit IRC07:40
*** rafaduran has joined #openstack-meeting07:42
*** hemna_ has joined #openstack-meeting07:51
*** EmilienM has joined #openstack-meeting08:05
*** gabriel has joined #openstack-meeting08:08
*** salv-orlando has joined #openstack-meeting08:09
*** gabriel is now known as durian08:09
*** somik has joined #openstack-meeting08:11
*** afazekas has joined #openstack-meeting08:11
*** s0mik has quit IRC08:12
*** somik is now known as s0mik08:12
*** uncleofthestick has joined #openstack-meeting08:33
*** metral has quit IRC08:35
*** metral has joined #openstack-meeting08:35
*** littleidea has quit IRC08:37
*** davidha has joined #openstack-meeting08:38
*** metral has quit IRC08:43
*** metral has joined #openstack-meeting08:45
*** derekh has joined #openstack-meeting09:06
*** ttrifonov is now known as ttrifonov_zZzz09:10
*** ttrifonov_zZzz is now known as ttrifonov09:11
*** metral has quit IRC09:11
*** jfriedly has joined #openstack-meeting09:17
*** darraghb has joined #openstack-meeting09:21
*** afazekas has quit IRC09:33
*** zbitter has quit IRC09:35
*** jhenner has joined #openstack-meeting09:54
*** persia has joined #openstack-meeting09:54
*** davidhadas has joined #openstack-meeting10:05
*** davidha has quit IRC10:09
*** almaisan-away has quit IRC10:14
*** almaisan-away has joined #openstack-meeting10:15
*** almaisan-away is now known as al-maisan10:16
*** afazekas has joined #openstack-meeting10:16
*** al-maisan is now known as almaisan-away10:16
*** reed has joined #openstack-meeting10:22
*** roadTripper has quit IRC10:49
*** maurosr has joined #openstack-meeting10:49
*** alexpilotti has joined #openstack-meeting10:56
*** bourke has quit IRC11:02
*** bourke has joined #openstack-meeting11:03
*** egallen has joined #openstack-meeting11:04
*** davidha has joined #openstack-meeting11:09
*** davidhadas has quit IRC11:11
*** bourke has quit IRC11:19
*** bourke has joined #openstack-meeting11:20
*** afazekas has quit IRC11:23
*** Razique has joined #openstack-meeting11:24
*** rushiagr has quit IRC11:33
*** rushiagr1 has joined #openstack-meeting11:33
*** rushiagr1 is now known as rushiagr11:34
*** rafaduran has quit IRC11:37
*** rafaduran has joined #openstack-meeting11:40
*** afazekas has joined #openstack-meeting11:42
*** jaypipes has quit IRC11:50
*** milner has joined #openstack-meeting11:53
*** milner has quit IRC11:58
*** milner has joined #openstack-meeting11:59
*** koolhead17 has joined #openstack-meeting12:03
*** milner has quit IRC12:03
*** milner has joined #openstack-meeting12:04
*** boden has joined #openstack-meeting12:07
*** simonmcc has joined #openstack-meeting12:08
*** milner has quit IRC12:08
*** jaypipes has joined #openstack-meeting12:09
*** milner has joined #openstack-meeting12:09
*** milner has quit IRC12:14
*** milner has joined #openstack-meeting12:14
*** goldfish has joined #openstack-meeting12:15
*** davidhadas has joined #openstack-meeting12:18
*** milner has quit IRC12:19
*** milner has joined #openstack-meeting12:19
*** goldfish has quit IRC12:21
*** davidha has quit IRC12:21
*** milner has quit IRC12:24
*** milner has joined #openstack-meeting12:24
*** milner has quit IRC12:29
*** milner has joined #openstack-meeting12:29
*** milner has quit IRC12:34
*** milner has joined #openstack-meeting12:34
*** milner has quit IRC12:39
*** milner has joined #openstack-meeting12:40
*** milner has quit IRC12:44
*** milner has joined #openstack-meeting12:45
*** roadTripper has joined #openstack-meeting12:46
*** sandywalsh has joined #openstack-meeting12:48
*** milner has quit IRC12:49
*** rushiagr has quit IRC12:50
*** milner has joined #openstack-meeting12:50
*** rushiagr has joined #openstack-meeting12:51
*** tgall_foo has joined #openstack-meeting12:52
*** rushiagr has quit IRC12:52
*** dolphm has joined #openstack-meeting12:54
*** milner has quit IRC12:55
*** milner has joined #openstack-meeting12:55
*** egallen has left #openstack-meeting12:59
*** simonmcc has quit IRC12:59
*** milner has quit IRC13:00
*** milner has joined #openstack-meeting13:00
*** simonmcc has joined #openstack-meeting13:02
*** milner has quit IRC13:05
*** milner has joined #openstack-meeting13:05
*** tgall_foo has quit IRC13:07
*** Razique has quit IRC13:08
*** afazekas has quit IRC13:09
*** milner has quit IRC13:10
*** milner has joined #openstack-meeting13:10
*** milner has quit IRC13:15
*** milner has joined #openstack-meeting13:16
*** annegentle__ has joined #openstack-meeting13:16
*** littleidea has joined #openstack-meeting13:17
*** littleidea has quit IRC13:19
*** jrd has quit IRC13:19
*** annegentle__ has quit IRC13:20
*** dhellmann has quit IRC13:20
*** milner has quit IRC13:20
*** milner has joined #openstack-meeting13:21
*** rafaduran1 has joined #openstack-meeting13:21
*** rafaduran1 has left #openstack-meeting13:22
*** dprince has joined #openstack-meeting13:22
*** rafaduran has quit IRC13:22
*** afazekas has joined #openstack-meeting13:24
*** milner has quit IRC13:25
*** milner has joined #openstack-meeting13:26
*** jaypipes has quit IRC13:28
*** milner has quit IRC13:31
*** milner has joined #openstack-meeting13:31
*** samkottler|out is now known as samkottler13:31
*** simonmcc1 has joined #openstack-meeting13:34
*** milner has quit IRC13:36
*** milner has joined #openstack-meeting13:36
*** simonmcc has quit IRC13:36
*** milner has quit IRC13:41
*** milner has joined #openstack-meeting13:41
*** jrodom has joined #openstack-meeting13:42
*** Razique has joined #openstack-meeting13:46
*** milner has quit IRC13:46
*** milner has joined #openstack-meeting13:46
*** uncleofthestick has quit IRC13:47
*** milner has quit IRC13:51
*** milner has joined #openstack-meeting13:51
*** Gordonz has joined #openstack-meeting13:53
*** egallen has joined #openstack-meeting13:55
*** milner has quit IRC13:56
*** milner has joined #openstack-meeting13:56
*** ryanpetrello has joined #openstack-meeting13:57
*** Gordonz has quit IRC14:00
*** primeministerp has quit IRC14:00
*** Gordonz has joined #openstack-meeting14:00
*** milner has quit IRC14:01
*** milner has joined #openstack-meeting14:01
*** eglynn is now known as hungry-eglynn14:01
*** jrodom has quit IRC14:04
*** milner has quit IRC14:06
*** milner has joined #openstack-meeting14:06
*** anniec has joined #openstack-meeting14:07
*** jrd has joined #openstack-meeting14:07
*** koolhead17 has quit IRC14:09
*** milner has quit IRC14:11
*** anniec has quit IRC14:11
*** anniec has joined #openstack-meeting14:11
*** milner has joined #openstack-meeting14:12
*** tgall_foo has joined #openstack-meeting14:13
*** tgall_foo has joined #openstack-meeting14:13
*** jfriedly has quit IRC14:15
*** milner has quit IRC14:16
*** milner has joined #openstack-meeting14:16
*** milner has quit IRC14:21
*** milner has joined #openstack-meeting14:21
*** koolhead17 has joined #openstack-meeting14:22
*** milner has quit IRC14:26
*** milner has joined #openstack-meeting14:26
*** tgall_foo has quit IRC14:29
*** milner has quit IRC14:31
*** milner has joined #openstack-meeting14:31
*** simonmcc1 has quit IRC14:35
*** milner has quit IRC14:35
*** dwcramer has joined #openstack-meeting14:36
*** milner has joined #openstack-meeting14:36
*** hungry-eglynn is now known as eglynn14:38
*** dolphm has quit IRC14:39
*** milner has quit IRC14:40
*** milner has joined #openstack-meeting14:40
*** dtynan has joined #openstack-meeting14:43
*** davidhadas has quit IRC14:44
*** jfriedly has joined #openstack-meeting14:44
*** milner has quit IRC14:45
*** milner has joined #openstack-meeting14:46
*** milner has quit IRC14:50
*** jaypipes has joined #openstack-meeting14:50
*** milner has joined #openstack-meeting14:51
*** markvoelker has joined #openstack-meeting14:51
*** milner has quit IRC14:55
*** markmcclain has joined #openstack-meeting14:56
*** milner has joined #openstack-meeting14:56
*** ozstacker has quit IRC14:58
*** anniec has quit IRC15:00
*** john5223 has joined #openstack-meeting15:01
*** milner has quit IRC15:01
*** milner has joined #openstack-meeting15:01
*** tgall_foo has joined #openstack-meeting15:04
*** tgall_foo has joined #openstack-meeting15:04
*** mtreinish has joined #openstack-meeting15:05
*** milner has quit IRC15:06
*** milner has joined #openstack-meeting15:06
*** milner has quit IRC15:10
*** milner has joined #openstack-meeting15:11
*** ryanpetrello has quit IRC15:12
*** ryanpetrello has joined #openstack-meeting15:13
*** rnirmal has joined #openstack-meeting15:15
*** milner has quit IRC15:16
*** milner has joined #openstack-meeting15:16
*** maurosr has quit IRC15:16
*** markwash has joined #openstack-meeting15:16
*** ozstacker has joined #openstack-meeting15:20
*** milner has quit IRC15:20
*** milner has joined #openstack-meeting15:21
*** dolphm has joined #openstack-meeting15:22
*** frankireland_ has joined #openstack-meeting15:23
*** milner has quit IRC15:25
*** milner has joined #openstack-meeting15:26
*** gongysh has quit IRC15:26
*** samkottler is now known as samkottler|bbl15:27
*** maurosr has joined #openstack-meeting15:28
*** milner has quit IRC15:30
*** frankireland_ has left #openstack-meeting15:31
*** afazekas has quit IRC15:31
*** dolphm has quit IRC15:33
*** cp16net is now known as cp16net|away15:35
*** frankM__ has joined #openstack-meeting15:35
*** cp16net|away is now known as cp16net15:35
*** markwash has quit IRC15:36
*** rongze_ has joined #openstack-meeting15:40
*** gyee has joined #openstack-meeting15:43
*** ollie1 has joined #openstack-meeting15:50
*** durian has quit IRC15:54
*** winston-d has joined #openstack-meeting15:59
jgriffithlooks like folks are ready to go?16:00
jgriffith#startmeeting cinder16:00
openstackMeeting started Wed Nov  7 16:00:31 2012 UTC.  The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
openstackThe meeting name has been set to 'cinder'16:00
*** j_king has joined #openstack-meeting16:00
jgriffithwinston-d: rongze_ around?16:00
jgriffithrnirmal: creiht16:01
winston-djgriffith, should be, let me check16:01
rongze_hi16:01
rongze_no need check16:01
jgriffithrongze_: :)16:01
creihthowdy16:01
jgriffithcreiht: hey there!16:02
j_kinghello16:02
jgriffithj_king: howdy16:02
jgriffithalright, we're sure to have some stragglers but...16:02
jgriffithlet's get started16:02
jgriffith#topic gate tests16:02
*** openstack changes topic to "gate tests"16:02
*** lloydde has joined #openstack-meeting16:03
jgriffithFor those that didn't notice the past few days16:03
jgriffithWe had a non-deterministic failure in Cinder16:03
jgriffith401 error when talking to the client16:03
jgriffithGood news https://review.openstack.org/#/c/15541/16:04
jgriffithI went down  few rat hold with our old friend the zero out on delete :)16:04
jgriffithWhich brings me to the point16:04
jgriffithCurrently what's in the code regarding the secure erase:16:04
*** jrodom has joined #openstack-meeting16:04
*** dolphm has joined #openstack-meeting16:05
jgriffith1. A secure_delete FLAG was added defaulting to True16:05
*** dolphm has joined #openstack-meeting16:05
jgriffith2. Gate configs were changed to set the flag to False16:05
jgriffith3. I dropped the dm_mapper(remove) call (this was the cause of the IO errors in kern.log)16:05
*** jdurgin1 has joined #openstack-meeting16:05
*** dolphm has joined #openstack-meeting16:05
*** iccha has quit IRC16:06
jgriffithI'm not crazy about leaving the devstack gate configured the way it is right now16:06
jgriffithbut wanted thoughts from others?16:06
*** iccha has joined #openstack-meeting16:06
jgriffitham I being paranoid?16:06
winston-di'm fine16:06
*** dwn has joined #openstack-meeting16:06
jgriffithThe other side of it is I think I'm going to implement that differently anyway16:07
jgriffithEither a simple "cp /dev/zero /dev/mapper/d-n" or maybe something more sophisticated16:07
*** s0mik has quit IRC16:07
*** iccha has quit IRC16:07
jgriffithLike snapshot /dev/mapper/zero16:07
*** iccha has joined #openstack-meeting16:07
jgriffith(on volume create)16:07
*** hemna_ has quit IRC16:07
*** dhellmann has joined #openstack-meeting16:08
jgriffithIf anybody has any strong opinions/concerns lemme know16:08
*** iccha has quit IRC16:08
jgriffithOr if you have a *better* idea16:08
jgriffith#topic blueprint targetting16:08
*** openstack changes topic to "blueprint targetting"16:08
jgriffithI've been going through the bp's: https://blueprints.launchpad.net/cinder16:09
jgriffithtalked with rongze_ and winston-d last night on a couple16:09
jgriffithbut wanted to get some more feedback on the Grizzly ones16:09
jgriffithI'm proposing dropping shared-volume https://blueprints.launchpad.net/cinder/+spec/shared-volume16:10
*** dolphm has quit IRC16:10
winston-dagree16:10
*** dolphm has joined #openstack-meeting16:10
j_kingindeed16:10
jgriffithIt would be a nice feature but spanning it across multiple compute nodes would be a problem16:10
*** yamahata has quit IRC16:11
jgriffithparticularly since alot of targets don't support multi-initiator16:11
jdurgin1jgriffith: it can actually be very useful for sharing a large data set among many nodes (read-only)16:11
jgriffithOk... so if no objections, I'm going to drop that one16:11
*** iccha has joined #openstack-meeting16:11
jgriffithjdurgin1: agreed, completely16:11
jgriffithjdurgin1: but for the iscsi case it's a bit of an issue to implement16:11
jdurgin1I don't mind dropping it for grizzly if no one's interested in it16:12
*** yamahata has joined #openstack-meeting16:12
jgriffithjdurgin1: I'd like to see it, just priority wise, not sure16:12
jdurgin1yeah, that makes sense16:12
jgriffithjdurgin1: So I'll drop it from Grizz, and if we can get it great16:13
creihtjgriffith: yeah I'm fine with that16:13
jgriffithcool16:13
rongze_I agree16:13
jgriffithThe hard one: https://blueprints.launchpad.net/cinder/+spec/efficient-vm-boot-from-volume16:13
*** rushiagr has joined #openstack-meeting16:14
jgriffithI'd really like to get something concrete on this one16:14
jgriffiththe image read/write features get us part way there16:14
*** mattray has joined #openstack-meeting16:14
jgriffithbut we need to put some thought into how we can deal with the whole image transfer/caching etc16:15
jgriffithI'm thinking Island may help with this?16:15
rongze_It need tack a snapshot?16:15
dtynanwe did some stuff on this for QCOW bootable volumes, but it's still not particularly fast.16:15
creihtjgriffith: how much of that is backend dependent?16:16
jgriffithcreiht: That's kind of a problem actually16:16
jdurgin1I'm still confused about what this blueprint is proposing to implement16:16
winston-dit depends on glance as well16:16
*** jrodom has quit IRC16:16
jgriffithjdurgin1: yeah, I think the first step is to clean that up16:16
winston-djdurgin1, me too16:16
*** jrodom has joined #openstack-meeting16:16
jgriffithjdurgin1: The way I've interpretted it is:16:17
jgriffithAllows you to use the same back-end for glance as for your instance_storage16:17
winston-dVincent is not here16:17
*** ashwin has joined #openstack-meeting16:17
jgriffithso if a back-end can do things like fast cloning etc etc you can take advantage of it16:17
*** ashwin is now known as Guest6847316:18
jgriffithbut there's some other things that folks brought up at the summit that they'd like to see16:18
*** Guest68473 has left #openstack-meeting16:18
jgriffithUnfortunately NONE of them really articulated the problem they were trying to solve16:18
creihtjgriffith: also, aren't there similar issues for local storage?16:18
jdurgin1perhaps someone could write up a specification for that blueprint?16:19
winston-dcreiht, i think so16:19
jgriffithcreiht: which issues?16:19
jgriffithYou mean the cross node problem?16:19
jgriffithOr you mean solve it for local storage as well?16:19
creihtthe having to load images slowly to boot an instance16:19
winston-dno, compute node have to copy image from glance to local disk16:19
jgriffithcreiht: yes16:19
*** colinmcnamara has joined #openstack-meeting16:20
jgriffithcreiht: sorry, was just using the back-ends as an example16:20
jgriffithcreiht: That's actually the case that received the most attention at the summit16:20
creihtyeah16:20
jgriffithcreiht: and that's where i wonder if Island might have some ideas we can use16:21
creihtcool16:21
jgriffithsounds like we're all in the same boat on this blueprint.... needs some detail/direction16:21
winston-dhow did you do it in the solidfire presentation? i remember you were using solidfire for instance storage/glance as well as cinder back-end16:21
jgriffithI'll see what I can do for that, and I think I'll end up targetting G316:21
rongze_cool16:22
jgriffithwinston-d: a little bit of hacking :)16:22
jgriffithwinston-d: It wouldn't fit the *general* case though16:22
jgriffithwinston-d: It was specific for us16:22
*** samkottler|bbl is now known as samkottler16:22
winston-djgriffith, ok16:22
jgriffithwinston-d: Really we had the same problem with sucking images out of glance etc16:23
jgriffithwinston-d: But we use an SF volume for instance_path16:23
jgriffithwinston-d: our internals then do some cooll stuff to optimize... but anyway16:23
*** gatuus has joined #openstack-meeting16:23
winston-das long as nova/cinder has to talk to glance via api to get image, there should be a new API sort of stuff to allow nova/cinder to figure out what storage glance is using.16:24
jgriffithOk, I'll work on flushinng that bp out a bit16:24
*** davidhadas has joined #openstack-meeting16:24
jdurgin1winston-d: that was added in Folsom, it's how the rbd cloning to volume works in Folsom16:24
jgriffithjdurgin1: +116:24
jgriffithso in my view that was a first step16:25
winston-djdurgin1, sorry i missed that. mind give me pointer?16:25
jgriffithI think we can exploit that going forward16:25
winston-djgriffith, yes, please16:25
jgriffithThe only other two that we should probably talk about16:26
jdurgin1#link https://blueprints.launchpad.net/glance/+spec/api-v2-store-access16:26
jgriffithiscsi-chap and multi-backend16:26
*** danwent has joined #openstack-meeting16:26
jdurgin1#link https://blueprints.launchpad.net/cinder/+spec/effecient-volumes-from-images16:27
dtynanI'd also like to mention the Glance meta one.16:27
dtynanhttps://blueprints.launchpad.net/cinder/+spec/retain-glance-metadata-for-billing16:27
*** araveendrann has joined #openstack-meeting16:27
*** araveendrann has joined #openstack-meeting16:28
jgriffithdtynan: ahh yes16:28
dtynanwe've implemented that in our version of diablo and would like to get it upstream16:28
jgriffithdtynan: that's great with me16:28
dtynanwe're targetting G1... ;)16:28
jgriffithdtynan: if you can do it that's cool16:28
jgriffithdtynan: alright, I'll target it and assign to you16:28
winston-djdurgin1, thx!16:29
jgriffithdtynan: G1 is like two weeks away, sure you can hit that?16:29
*** jbrogan has joined #openstack-meeting16:29
dtynanwell....16:29
jgriffithdtynan: hmmmmm16:29
dtynanwe've been busy getting it into production here @ HP16:29
jgriffithdtynan: Yup, we're all busy :)16:29
dtynanso we know what the issues are...16:29
jgriffithdtynan: This is why I left it sitting16:30
jgriffithdtynan: So it's your call, and what you can commit to16:30
dtynanbut from an HP-diablo pov, it'll be in production imminently.16:30
dtynanyeah, nothing like a challenge, eh?16:30
jgriffithdtynan: My concernn is that it just sits there forever16:30
*** dolphm has quit IRC16:30
jgriffithdiablo haha16:30
dtynan:)16:30
jgriffithdtynan: so  tell me what you want to commit to?16:31
dtynanyes.16:31
*** rushiagr1 has joined #openstack-meeting16:31
jgriffithdtynan: dtynan yes?16:31
jgriffithdtynan: Is that yes  for G1, yes for sitting forever?16:31
jgriffith:)16:31
dtynanyes for G1.16:32
*** rushiagr2 has joined #openstack-meeting16:32
*** rushiagr1 has quit IRC16:32
jgriffithOkie Dokie... you're officially on thehook16:32
jgriffithOn to iscsi-chap16:32
jgriffithI propose ....16:32
*** rushiagr has quit IRC16:33
jgriffithwait, did I already bring that up16:33
jgriffiththink I did16:33
*** rushiagr2 has left #openstack-meeting16:33
jgriffithNo... I didn't16:33
jgriffithI propose that one is dropped16:33
jgriffithIt's been sitting for a long time and the reality is the back-ends immplement it16:33
jgriffithHaven't heard too much yelling forit16:34
jgriffithif vincent comes back and works on it fine, but we should remove the targetting16:34
jgriffithagree?16:34
j_kingsure16:34
jdurgin1fine with me16:35
winston-dagree16:35
jgriffithThe other big items are:16:35
jgriffithFibreChannel, multi-back-end and the API general bucket16:35
jgriffithAnyy of the folks from HP, IBM or Brocade here today?16:36
*** primeministerp has joined #openstack-meeting16:36
jgriffithOk... multi-backend16:36
jgriffithwe need to decide on how we want this16:36
*** rushiagr2 has joined #openstack-meeting16:36
jgriffithrnirmal: provided a working implementation16:36
*** rushiagr2 is now known as rushiagr16:37
jgriffithrnirmal: do we go that route or do we do multiple services/proceses on a single box16:37
dtynanHP.16:37
jgriffithdtynan: yeah, wrong HP group :)16:37
dtynan:)16:37
jgriffithas a refresher: https://review.openstack.org/#/c/11192/16:38
jgriffithThat's the proposal from rnirmal16:38
winston-djgriffith, i prefer multiple services/processes16:38
jgriffithwinston-d: That's the direction I'm leaning too16:38
*** dolphm has joined #openstack-meeting16:39
jdurgin1that seems a lot easier to configure16:39
jgriffithwinston-d: It solves some concerns that were raised by others16:39
jgriffithand let's us use the volume_type scheduler :)16:39
j_kingas long as there isn't a high level of co-ordination required, I'd be up for multiple processes16:39
*** alexpilotti has quit IRC16:39
*** ehm has joined #openstack-meeting16:39
jgriffithj_king: My initial thought is something like multiple managers running in their own process based on back-end16:39
*** xstatix has joined #openstack-meeting16:40
jgriffithuse all the same concepts we use today for multiple volume node configs16:40
jgriffithcreiht: thoughts?16:41
j_kingsounds good. I generally prefer the more simple implementation.16:41
creihtjgriffith: I don't have a strong opinion here16:42
jgriffithmy keyboard is going nuts here16:42
jgriffithcreiht: fair enough16:42
jgriffithOk, let's proceed with multi-proces16:42
rnirmaljgriffith: sorry came in late16:42
creihtbut your proposal seems reasonable16:42
jgriffithrnirmal: No prob16:43
jgriffithrnirmal: We were talking about the multi-back-end immplementation16:43
rnirmalso multi process within the same manager ?16:43
jgriffithrnirmal: I was actually thinking multiple managers16:44
rnirmalor multiple managers ?16:44
winston-dmulti processes in multi managers16:44
rnirmaljgriffith: well we don't have to do anything for it16:44
winston-deach manager has its own process16:44
jgriffith:)16:44
rnirmaland the whole reason for the multi-backend was to get away from having to run multiple managers16:44
rnirmalwinston-d: that's how it's right now16:44
jgriffithrnirmal: multiple managers on the same node16:45
winston-drnirmal, i thought your concern is too many volume service node to manage16:45
*** bswartz has joined #openstack-meeting16:45
rnirmalwinston-d: also services right... 20 or so init scripts for each one ?16:46
rnirmalI'd prefer a single configuration to load all the backends... if we do multiple processes within the same manager... that would be fine too16:46
winston-drnirmal, that can be changed, adding one new binary in bin/ can solve that problem.16:46
j_kingmanager could just load a backend in each process16:46
jgriffithTBH if you're looking at 20 back-ends I'd rather the init scripts that trying to get the config files correct16:47
j_kingjust have to config the manager16:47
rnirmaljgriffith: but why is a single config more harder than 20 configs ?16:47
jgriffithrnirmal: Why is having an init for each manager harder than 20 configs?16:48
rnirmaljgriffith: :) 20 log files to parse... 20 everything16:48
jgriffithrnirmal: just an example, maybe a poor one16:48
jgriffithrnirmal: hmmm... ok, you've got me there :)16:48
jdurgin1separate config files is generally easier for config management to deal with16:49
*** garyk has quit IRC16:49
winston-dthe complexity comes with a new layer 'backend' in single manager design.16:49
winston-di'd rather to have separate log files, IMHO16:49
jdurgin1winston-d: +116:50
rnirmalwinston-d: with what I proposed you can still do that16:50
rnirmalit gives the option to do both16:50
rongze_winston-d: +116:50
j_kingwinston-d: you still could with a single manager that manages several backend processes16:50
rnirmalyou are not tied to any particular way16:50
j_kingthe process just logs16:50
winston-drnirmal, it's true and i think multi manager design can also combine multi configuration files into one16:50
winston-dwithout adding complexity to introduce a new layer 'back-end'.16:51
rnirmalwinston-d: how would you distinguish 20 backends in the current design -> 'host' ?16:51
rnirmalthat's bad as is16:51
rnirmalirrespective we still need the concept of a 'back-end'16:52
winston-drnirmal, via volume-topic16:52
rnirmalmerely more than just a driver...16:52
*** lloydde has quit IRC16:52
rnirmalwinston-d: how?16:52
rnirmaldon't tell me run on multiple hosts16:52
rnirmalthat's how it's right now16:52
winston-das long as different back-end instance has it unique volume-topic, scheduler is able to find it.16:52
rnirmalhow is that more different than with a 'back-end'16:53
jgriffithOk, seems we have a bit to work through on this :)16:53
rnirmalthe scheduler either needs to know which 'volume-topic' or which 'backend'16:53
rnirmalwhich 'backend' seems more clearer than which 'volume-topic'16:54
jgriffithrnirmal: why?16:54
rnirmaljust canonically16:54
jgriffithmeh... maybe16:54
jgriffithSo here's the thing IMO16:54
jgriffithThere are advantages and disadvantages to both16:55
jgriffithWhat I'm trying to figure out is which is going to be more robust and supportable16:55
jgriffithwith an emphasis on robust16:55
*** thingee has joined #openstack-meeting16:56
winston-dand able-to-scale16:56
jgriffithwinston-d: true, but I think both can scale, just not as clean maybe16:56
winston-dright16:57
rnirmaljgriffith: I'm all for a better solution if we have one :)16:57
jgriffithrnirmal: well the problem is I think your solution is great16:57
jgriffithrnirmal: that being said I want to look at all possibilities16:58
jgriffithSo I think what needs to happen is we need to have some code to compare16:58
jgriffithso maybe an implementation using multiple managers that at least *functions* so we can look at the two together16:59
jgriffithsee what comes out of it?16:59
jgriffithseem reasonable?16:59
kmartinjgriffith: sorry, I'm here a hour late due to Daylight saving apparently.16:59
rnirmaljgriffith: sure.16:59
jgriffithkmartin: you and a few others :)16:59
kmartin;)16:59
rnirmalkmartin: got caught in daylight savings as well :)16:59
thingeeditto17:00
jgriffithanyway, I think there's enough interest and merit in the multi-manager approach that we should at least pursue it a bit17:00
rnirmaljgriffith: agreed17:00
jgriffithok, and we always have the first implementation that we can go with when it comes down to it17:01
jgriffithalright... pheww17:01
jgriffithUmmm... I wanted to save some time to see if folks had bp's they haven't gotten around to filing yet17:01
* jgriffith is looking at creiht 17:02
*** heckj has joined #openstack-meeting17:02
kmartinA far as the FC blueprint with details has made it's way through HP legal is now getting reveiwed by the entire team as we meet again tomorrow morning.17:02
jgriffiththingee: btw, wanted to see what your blockers are17:02
*** amotoki has quit IRC17:03
jgriffithkmartin: wow.. beuarocracy at it's finest :)17:03
*** littleidea has joined #openstack-meeting17:03
kmartinjgriffith: yep17:03
thingeejgriffith: my two bps list bootable vols and clearer error messages are blocked by my apiv2 bp17:03
thingeeshould make that more clear on the bps themselves17:03
jgriffiththingee: ahhh17:04
jgriffiththingee: yeah, we should mark them as such17:04
*** jrodom has quit IRC17:04
thingeefor apiv2 I've posted my github branch which basically has middleware separated out and other api common code. tests pass.17:04
jgriffiththingee: and maybe make dependencies instead of listing as blocked17:04
thingeeit's all in the bp17:04
thingeejgriffith: sounds good17:04
jgriffiththingee: yeah, was looking at that last night, looks good so far17:05
jgriffiththingee: Nice work on that for a week-end :)17:05
*** jrodom has joined #openstack-meeting17:05
jgriffiththingee: unless you were just hiding it prior to that :)17:05
*** gatuus has quit IRC17:05
thingeejgriffith: got about 26 tests failing atm for routing stuff. This is a bigger change that I was hoping and a bit of learning curve for me, but I've learned a lot about paste over the weekend and just gotta get things organized to model glance correctly17:06
jgriffiththingee: I hear ya17:06
ollie1@jgriffith I believe there are some folks here at HP planning to submit a bp around volume backup, to swift object store17:06
jgriffiththingee: make sure you get the fixes for the monkey patching before you try and run with real endpoints :)17:06
dtynanmeant to mention that volume-backup BP... ;)17:07
thingeejgriffith: I hear that17:07
jgriffithdtynan: ollie1 noted17:07
*** dhellmann has quit IRC17:07
jgriffithkeep in mind, there's some code in island that might be leveraged for this as well17:08
jgriffithand the Lunar folks have some interest so they should be updated as well17:08
dtynanthingee we did some stuff for list-bootable-volumes but it was through an hp-specific API hook (for now). I'd be interested in reading your BP. (and will do..)17:08
thingeedtynan: I grabbed it because it seemed doable for me, but I'll be honest, I haven't started yet with some of the other stuff on my plate.17:09
ollie1@jgriffith I'll pass that on17:09
thingeeI'll be focusing on apiv2 this week. would love to get to it next week if all goes according to plan (heh).17:10
dtynanthingee: cool. I'll take a look. we figured an hp-specific API was the best (short term) way of getting the functionality before it's in the mainstream.17:10
*** markmcclain has quit IRC17:10
*** lloydde has joined #openstack-meeting17:10
jgriffiththingee: If G1 is possible that would be ideal17:10
jgriffiththingee: we can of course add to it after that, but17:11
jgriffiththingee: we should have that in for things to build off of as you pointed out with your other BP's17:11
jgriffithkmartin: how are you guys feeling about the FC work?17:12
jgriffithkmartin: I know you're meeting tomororw,but what's the general feel so far?17:12
thingeejgriffith: definitely! I'll be focusing hard on making that happen.17:12
jgriffiththingee: great, thanks!17:12
kmartinjgriffith: the BP looks good and we're shooting for G217:12
jgriffithkmartin: G2?  Really?17:12
jgriffithkmartin: Awesome!17:12
kmartinthat the plan may slip into G317:13
jgriffithOk... we're over, anything else?17:13
jgriffithkmartin: haha17:13
jgriffithI'll target G3 :)17:13
*** Mandell has joined #openstack-meeting17:13
ollie1fyi we're also working the bp to extend volume usage stats: https://blueprints.launchpad.net/cinder/+spec/volume-usage-metering17:13
kmartinsounds safer :)17:13
winston-dif you guys have time, please take a look at here: https://etherpad.openstack.org/cinder-backend-capability-report17:14
jgriffithollie1: can you update the bp?17:14
winston-dthat's for back-end to report capability/capacity for scheduling purpose.17:14
jgriffithollie1: and what is your timeline?17:14
*** alexpilotti has joined #openstack-meeting17:15
jgriffithwinston-d: thanks for reminding me :)17:15
ollie1I'll check that out with the person on it and update the bp17:15
jgriffithwinston-d: looks like a good start17:15
dtynanthe guy who did the volume-usage-metering code is on vacation this week.17:15
*** hemna has joined #openstack-meeting17:16
jgriffithollie1: ok, just FYI I'm going to hack up blueprints tonight with prejudice :)17:16
jgriffithdtynan: ahhh17:16
winston-dthat's just some examples, we should have mandatory ones and optional ones to report.17:16
jgriffithalright, well no big deal.  We never stop accepting blue-prints17:16
dtynanwe'll round him up next week, and get him busy on the upstream work :)17:16
dtynanit's implemented internally.17:16
jgriffithwinston-d: yes, I'm with ya17:16
jgriffithwinston-d: it's a good model to start and see what we're doing though17:17
jgriffithalright.... i should probably wrap this up17:17
jdurgin1winston-d: just a heads up, I expect most of those to not make sense (and thus be optional) from a ceph perspective17:17
jgriffithjdurgin1: I think we'll tweak this a bit to make more sense, but...17:18
*** oubiwann has joined #openstack-meeting17:18
*** gatuus has joined #openstack-meeting17:18
jgriffithjdurgin1: I was thiking that for any we say are mandatory but they don't apply just set None?17:18
jgriffithjdurgin1: so *kinda* mandatory17:18
winston-djgriffith, jdurgin1, make sense17:18
jdurgin1jgriffith: might as well make them option imo, but we can discuss later17:19
jgriffithjdurgin1: The mandatory part is just that you can be queiried and return the field17:19
jgriffithjdurgin1: so maybe better language is that you have to implement the report_capabilities method17:19
*** Ahmed_ has joined #openstack-meeting17:19
winston-dmandatory is minimum set of capability that allow built-in filters to work, i think17:20
jgriffithjdurgin1: what you put in there has guidelines if yousupport17:20
jgriffithwe can hash it out17:20
*** jhenner has quit IRC17:20
jgriffithjdurgin1: but I think theres value in the function, and eve the basics like driver version etc17:21
*** markwash has joined #openstack-meeting17:21
jdurgin1that makes more sense, but we're over a bit already17:21
jgriffithwe're way over17:21
jgriffithalright17:21
jgriffiththanks everyone17:21
jgriffithdon't forget DST next week :)17:21
jgriffith#endmeeting17:21
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"17:21
openstackMeeting ended Wed Nov  7 17:21:50 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:21
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2012/cinder.2012-11-07-16.00.html17:21
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2012/cinder.2012-11-07-16.00.txt17:21
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2012/cinder.2012-11-07-16.00.log.html17:21
*** dtynan has left #openstack-meeting17:22
*** bswartz has left #openstack-meeting17:22
*** Ahmed_ has left #openstack-meeting17:22
*** thingee has left #openstack-meeting17:23
*** jrd has quit IRC17:25
*** ollie1 has left #openstack-meeting17:26
*** j_king has left #openstack-meeting17:27
*** rushiagr has left #openstack-meeting17:28
*** rongze_ has quit IRC17:29
*** anniec has joined #openstack-meeting17:32
*** gatuus has quit IRC17:32
*** garyk has joined #openstack-meeting17:33
*** gatuus has joined #openstack-meeting17:33
*** mnewby has joined #openstack-meeting17:37
*** frankM__ has quit IRC17:40
*** mattray has quit IRC17:40
*** metral has joined #openstack-meeting17:45
*** Razique has quit IRC17:45
*** Razique has joined #openstack-meeting17:45
*** s0mik has joined #openstack-meeting17:51
*** winston-d has quit IRC17:53
*** CaptTofu has joined #openstack-meeting17:58
*** jrodom has quit IRC17:58
CaptTofuhowdy all17:58
*** dprince has quit IRC17:59
*** simonmcc1 has joined #openstack-meeting17:59
zykes-aloha ;o17:59
KiallHiya18:00
CaptTofuhow goes over there weather wise?18:00
zykes-here ?18:00
KiallAnother min or two before we start the DNSaaS meeting - anyone else here yet?18:00
zykes-crap p18:00
*** adjohn has joined #openstack-meeting18:00
*** jcmartin has joined #openstack-meeting18:00
*** derekh has quit IRC18:00
CaptTofulooks like people are entering the room18:00
*** jrodom has joined #openstack-meeting18:00
jcmartinhi all18:00
*** jrodom has quit IRC18:01
*** jrodom has joined #openstack-meeting18:01
zykes-any of you from grid dynamics btw ?18:01
*** andrewbogott has joined #openstack-meeting18:01
CaptTofuKiall: ryan is not going to be here today?18:01
andrewbogottRyan is on holiday.18:01
CaptTofuI thought so.18:02
*** cp16net is now known as cp16net|away18:02
Kiall#startmeeting DNSaaS18:03
openstackMeeting started Wed Nov  7 18:03:08 2012 UTC.  The chair is Kiall. Information about MeetBot at http://wiki.debian.org/MeetBot.18:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:03
openstackThe meeting name has been set to 'dnsaas'18:03
KiallHi all!18:03
KiallEveryone had a chance to glance at the agenda? http://wiki.openstack.org/Meetings/DNSaaS18:03
*** jdurgin1 has quit IRC18:03
CaptTofuyes :)18:03
KiallSo - First things first - Stackforge18:04
KiallMoniker's code has been moved to Stackforge, meaning we now use the OpenStack Jenkins and Gerrit install.18:04
KiallAny contributions etc must come via Gerrit!18:05
*** winston-d has joined #openstack-meeting18:05
KiallAnd a launchpad project has been setup for bug tracking - https://launchpad.net/moniker18:05
KiallFile anything you find please!18:06
*** cp16net|away is now known as cp16net18:06
CaptTofuKiall: I wonder if it'd be a good question to ask who has tried out the code?18:06
KiallDoes everyone know how to handle code submissions via Gerrit?18:06
jcmartinWhat model do you want to use : one branch per bug/blueprint or one branch per feature/milestone ?18:06
KiallCaptTofu, yes.. that would be :)18:06
Kialljcmartin, gerrit somewhat pre-defines the meaning of branches18:07
*** littleidea has quit IRC18:07
KiallBasically - a branch is a series of related patch sets18:07
jcmartinI am not an expert, but recently other project have "feature" branches18:07
Kialleach patch in the set must be valid, and pass all tests etc18:07
Kialljcmartin, oh - I havent seen any of the OS projects using those18:07
Kiall#link http://wiki.openstack.org/GerritWorkflow18:08
jcmartinIt depends i guess if you want one level before to get to main, or two18:08
Kialljcmartin, I'll look into how they use them. But traditionally, Gerrit has had a standard flow that prevents long lived topic branches18:08
jcmartinthey call it topic branches18:08
zykes-correct18:09
zykes-though isn't that mostly for "big" things like big features?18:09
jcmartinthrough18:10
KiallSure - I've no idea how the others are using them - So I can't really comment on them (yet)!18:10
jcmartintrue18:10
*** sarob has joined #openstack-meeting18:10
KiallSo - CaptTofu had a good question re who has actually deployed and tested the code?18:10
KiallCan I get a show of hands?18:10
jcmartinnot deployed, but tested18:10
Kiall<- I obviously have18:10
Kiallwell -i meant started the whole thing up rather than in production :)18:11
simonmcc1the normal gerrit workflow is to create a local branch off the gerrit master head & work there, it's possible to still submit to the for-review master branch18:11
zykes-i'll do when the notification stuff is decided and I can put it to use Kiall :)18:11
* CaptTofu does18:11
simonmcc1I haven't started anything up yet :)18:11
KiallOkay - So a few - I love to hear feedback from others (maybe after the meeting?) to find out if anything is preventing them from doing so18:12
KiallI would*18:12
*** EmilienM has left #openstack-meeting18:12
KiallSo - Moving on - I expect this next one to take a while ;)18:13
Kiall#topic Notification Handling18:13
*** openstack changes topic to "Notification Handling"18:13
KiallSince the last meeting, I've implemented support for handling notifications from other OS services - eg nova/quantum18:13
KiallWhat's left to do there is decide on the appropriate actions to take upon receiving a notification18:14
jcmartinit was pretty fast, kudos18:14
KiallWe agreed last week to auto create records for both floating and fixed IPs as they are assigned to instances.18:14
KiallWhat we did not decide, was what those records would look like, or what domain they would be created it18:15
*** dolphm has quit IRC18:15
Kiallcreated in*18:15
andrewbogottKiall:  Can I ask which notification method you're listening for?18:15
*** mnewby_ has joined #openstack-meeting18:15
KiallI'd like to hear what people expect/want18:15
andrewbogott(Maybe there's only one notifier that's appropriate, I haven't looked at the options lately)18:15
*** mnewby__ has joined #openstack-meeting18:16
Kiallandrewbogott, It makes use of the openstack common RPC code18:16
Kiallalthough in a somewhat "unusual" way - I've borrowed the unusual code from Ceiliometer18:16
CaptTofuKiall: I haven't looked at that work, but is documentation there for how these notifications are put to use?18:16
jcmartinWith regard to the name of the record, we should make it configurable18:16
Kialland am hoping to get a proper well defined notification listener into OS Common - SandyWalsh recently wrote out a BP for just that18:17
andrewbogottKiall:  OK, sorry, I'm behind… this is using the rabbit_notifier driver, or...?18:17
Kialljcmartin, configurable is an option, but we are limited by the content of the notifications18:17
Kiallandrewbogott, ah yes. On the nova/quantum side - I've tested rabbit_notifier18:17
*** winston-d has quit IRC18:18
andrewbogottok.18:18
Kialland on the moniker side - i use the Kombu RPC client18:18
jcmartintrue, only few options will be possible18:18
*** mnewby has quit IRC18:18
*** mnewby__ is now known as mnewby18:18
KiallCaptTofu, Right now we're trying to figure out what to use them for :)18:18
CaptTofuKiall: also I'll put a plug for the fact for those interested, the REST API for Moniker is documented18:18
andrewbogottKiall:  So, I think we'd discussed having some sort of template system that modifies the tenant name and produces the DNS domain...18:18
andrewbogottAnd a similar system that modifies the instance name to produce DNS name18:18
jcmartinCaptTofu: can you post a link ?18:19
Kiallandrewbogott, can you go into some detail on the sort of modification that might be done?18:20
*** mnewby_ has quit IRC18:20
KiallAnd - would it be a global per-moniker option, or per tenant?18:20
andrewbogottIt could be done via  regexp or we could have a plugabble system that calls a function.18:20
andrewbogottI guess having it be pluggable is good, then the default can be regexp.18:20
Kialljcmartin, I'm uploading the latest now18:20
Kiall#link http://packages.python.org/moniker/18:20
*** markmcclain has joined #openstack-meeting18:21
Kiallandrewbogott, right - the implementation is pluggable via entry points - it should be trivial to add custom handlers18:21
andrewbogottKiall:  cool!  So you can just implement a reference plugin that does no transformation (tenant name -> dns domain)18:21
andrewbogottand leave the rest to users :)18:22
KiallThats certainly an option. I have a "toy" implementation here already: https://github.com/stackforge/moniker/blob/master/moniker/notification_handler/nova.py18:22
Kiallit creates an A record for $instance_id.$tenant_id.$preconfigured_domain18:22
*** dhellmann has joined #openstack-meeting18:22
KiallBut - I would prefer to have a more useful default handler included!18:23
CaptTofujcmartin: just check out moniker and build the sphinx docs18:23
*** darraghb has quit IRC18:23
Kialljcmartin, do you have any particular format for auto-generated records in mind?18:23
jcmartinCapTofu: will play with sphinx18:23
andrewbogottKiall:  That sounds pretty useful to me already.18:23
Kialljcmartin, also docs are uploaded to http://packages.python.org/moniker/18:24
andrewbogottKiall:  The next implementation might take a multistropt to map tenants to domains.18:24
jcmartinKiall: no specific format, and I can guarantee that anything we come up with will not work for some users18:24
araveendrannis hostname part of the message payload18:24
CaptTofujcmartin: for your convenience, you are welcome to browse my server: http://15.185.172.152/~ubuntu/18:25
*** dprince has joined #openstack-meeting18:25
Kiallaraveendrann, sadly - no!18:25
jcmartininstance name should be in some notification, no ?18:25
KiallFor reference a sample instance create end notification: https://github.com/stackforge/moniker/blob/master/moniker/tests/sample_notifications/nova/compute.instance.create.end.json18:25
andrewbogottKiall:  Wait, I think it is… isn't there a display_name field?18:25
zykes-CaptTofu: why that when there's moniker.rthfd.com ?18:25
zykes-CaptTofu: why that when there's moniker.rthfd.org sorry ?18:25
Kiallyes - display_name is present18:25
Kiallzykes-, because the RTFD hasnt updated ;)18:26
*** littleidea has joined #openstack-meeting18:26
andrewbogottdisplay_name seems sufficient, unless I misunderstand what it's for.18:26
KiallMaybe we can go display_name.$tenant_id.$preconfigured_domain18:26
KiallBut - reusing the same name twice might produce unexpected (or expected) behaviour .. ie a RR DNS record18:27
araveendrannbut is that field editable by the user, in which case we need to adjust for the new display name18:27
jcmartinyou might want to add indexes if you have multiple  ip, something maybe based on nic priority18:27
CaptTofuzykes-: thanks for pointing that out. I volunteer to make that happen whatever the case18:27
andrewbogottKiall:  Behold!  https://review.openstack.org/#/c/14833/18:27
Kiallaraveendrann, actually - your right. the display_name can be changed18:28
KiallSo using that might produce some unexpected results18:28
jcmartinwhat about just using some combination of the IP like comcast does and allow users to create cnames ?18:29
andrewbogottThat certainly solves the uniqueness problem.18:29
Kialljcmartin, thats actually not a bad option. using UUIDs makes the names "almost" useless18:29
andrewbogottIt would also not be hard to add hostname to the notification.  There's a lot in there aleady, I wouldn't think anyone would object to another field.18:29
jcmartinbased on our experience, you DON'T want to be in the business of defining hostnames for people18:30
Kiallandrewbogott, yea - I doubt anyone would18:31
jcmartinWhat we ended up doing is creating a default hostname/record with some internally useful name, and let users add/change it later18:31
andrewbogottKiall:  I'm happy to go do that right away, if we conclude that it's useful to us.18:31
Kialljcmartin that seems sane. Does anyone object to using the IP and a pre-defined provider domain as the stock handler?18:31
zykes-maybe we can make the dnsrecord templatable ?18:31
jcmartinthat works for me18:31
Kiallandrewbogott, it would certainly be useful for me :)18:31
zykes-instead18:31
*** colinmcnamara has quit IRC18:31
andrewbogottzykes-:  I think we've already agreed that there will be (is) a plugin system for customizing the dnsrecord, we're just picking a good default.18:32
andrewbogottKiall:  OK, noted.18:32
*** jfriedly has quit IRC18:32
andrewbogottAnd, +1 for jc's suggestion about using IPs for the first pass.18:32
araveendrannthis is how ec2 does it ec2-72-44-45-204.compute-1.amazonaws.com18:33
zykes-rip of ec2 then :)18:33
KiallOkay - So before we vote on the options (UUID's, IPs, display_name) does anyone have any other suggestions?18:33
andrewbogottKiall:  We barely need to vote, each of those is trivial to implement and you can just make it switchable :)18:34
zykes-#vote18:34
zykes-:p18:34
Kiall#startvote Default record format for auto-generated records: UUID, IPs, DisplayName18:34
Kiallandrewbogott, too late18:34
Kiall#startvote Default record format for auto-generated records? UUID, IPs, DisplayName18:34
openstackBegin voting on: Default record format for auto-generated records? Valid vote options are UUID, IPs, DisplayName.18:34
openstackVote using '#vote OPTION'. Only your last vote counts.18:34
Kiall#vote IPs18:34
zykes-#vote IPs18:35
jcmartin#vote IPs18:35
andrewbogott#vote IPs18:35
Kiall^ follow that "syntax" to vote :)18:35
araveendrann#vote IPs18:35
uvirtbot`Kiall: Error: "follow" is not a valid command.18:35
CaptTofu#vote IPs18:35
KiallHah - that was an easy decision so.18:35
KiallAny stragglers?18:35
*** littleidea has quit IRC18:35
KiallI guess not.18:35
Kiall#endvote18:35
openstackVoted on "Default record format for auto-generated records?" Results are18:35
openstackIPs (6): CaptTofu, araveendrann, jcmartin, zykes-, andrewbogott, Kiall18:35
CaptTofuKiall: I'll submit the patch for that. I need to put my DBA hat on and add any indexes missing18:35
KiallCaptTofu, great!18:35
Kiall#action CaptTofu to provide a patch for the switch to IP based auto generated records18:36
KiallAnything more on notification handling before I move on?18:36
Kiall#topic Python Client API and CLI18:37
*** openstack changes topic to "Python Client API and CLI"18:37
KiallOkay - So we currently have no usable python client API, or CLI. I have some horrible code that I could clean up, but that would basically be a rewrite anyway18:37
*** anniec has quit IRC18:38
KiallI was hoping to find a volunteer :)18:38
andrewbogottIt should use openstack-client...18:38
andrewbogottI'll volunteer if it can use openstack-client :)18:38
Kiallanderstj, when did that come out? Link? -_-18:38
andrewbogottUm… for CLI that is.18:38
Kiall#link https://github.com/openstack/python-openstackclient18:38
jcmartin#link http://blog.doughellmann.com/2012/10/cliff-command-line-interface.html18:39
jcmartinthis is not openstack vetted yet18:39
Kialljcmartin, the current skeleton CLI is using cliff18:39
Kiall(It used for database init and sync right now)18:39
jcmartincool18:39
KiallAnd it looks like python-openstackclient uses it to18:40
Kialltoo18:40
jcmartinthen it's vetted18:40
Kiallandrewbogott, willing to volunteer? :)18:40
KiallThe REST API is small, so the Python API and CLI should be fairly minimal18:40
andrewbogottKiall:  We're talking about the layer that implements a CLI and converts it to REST calls?  I'm happy to do that.18:40
CaptTofuI'll help certainly18:41
Kiallandrewbogott, yes - So a python lib that makes the API requests, and a CLI that wraps it18:41
andrewbogottYep, sounds good.18:42
zykes-converts it how ?18:42
CaptTofuadrewbogott: sounds pretty easy to use eh?18:42
andrewbogottUm… maybe my use of 'convert' was ill-conceived.  'relays'.18:42
KiallInterestingly, it looks like python-openstackclient only does the CLI part, and doesnt provide the a python API for the services18:43
Kiallandrewbogott, it's certainly worth looking at anyway!18:43
Kiall#action andrewbogott Look into python API and CLI18:43
Kiall#action CaptTofu  Look into python API and CLI w/andrewbogott18:43
CaptTofu#action CaptTofu add indexes18:44
KiallWe all expect results in the next 30 mins or so ;)18:44
KiallGet to it18:44
Kiall!18:44
CaptTofuhehe18:44
CaptTofuthat's funny18:44
KiallNext up is DevStack18:44
Kiall#topic DevStack18:44
*** openstack changes topic to "DevStack"18:44
KiallIt seems we can't just add support for Moniker straight to devstack unless we're officially an incubated project18:44
KiallSo - Even if we start that today, it will be a while before it's official.18:45
KiallI'm going to fork devstack and add moniker support there - I'll hopefully get it done before the next meeting18:45
Kiallthat should make things easier for all involved18:45
Kiall#action kiall Add moniker support to a DevStack fork18:45
KiallAnd - rushing over that last one - we move on to the last topic:18:46
jcmartinWhat backend should this include ?18:46
KiallHah - Almost ;)18:46
*** colinmcnamara has joined #openstack-meeting18:46
Kialljcmartin, I would like to see PowerDNS as its easier to get going than bind18:47
jcmartinmaybe you should implement the plugin model before18:47
andrewbogottI'll want to implement the pdns/ldap backend somewhat quickly.  But I'm not sure that helps anyone but me.18:47
jcmartinI mean for devstack, fake backend or dnsmasq ?18:47
Kialljcmartin, agreed, I've got the agent conversion to proper plugins half done18:48
andrewbogottA fake backend that basically just logs commands will be useful for development.  And quick to write.18:48
jcmartincan we configure dnsmasq to return host file like entries ?18:48
jcmartinfake backend would be good for now anyway18:49
*** simonmcc has joined #openstack-meeting18:49
*** simonmcc1 has quit IRC18:49
Kiallandrewbogott, good idea. I'll add it to my todo list. I've almost got the agent converted to a proper plugin system.. I'll add that once I'm done (or maybe someone can beat me to it? ;))18:49
*** simonmcc2 has joined #openstack-meeting18:49
CaptTofujcmartin: fake backend, what would that mean exactly?18:49
Kiall#action Kiall to complete agent conversion -> plugin system18:49
CaptTofujust logs commands, stubbed out18:49
CaptTofu?18:49
jcmartinyep18:49
Kiall#action Kiall (or someone!) to write a logging/fake agent18:49
zykes-so what, make 1 agent to rule them all via plugins ?18:50
Kialljcmartin, We can hace dnsmasq serve a hosts file18:50
Kiallhave*18:50
jcmartinplugin should not be in the agent in my opinion18:50
Kialljcmartin, any reason why not? (That is the route I've taken so far)18:51
jcmartinit means that you have to have the agent. Some DNS server already expose a rest api, why use an agent ?18:51
jcmartinor in the case of powerdns, the agent would just configure ldap/mysql18:52
CaptTofuzykes-: what do you mean 1 agent to rule them all via plugins?18:53
KiallThe main reason I chose to always have an agent (even for simpler agents) was to keep the clear separation, and avoid confusion over where the code that talks to the backend is executing18:53
jcmartinagent is useful if you have to update local files18:53
zykes-CaptTofu: as in 1 agent daemon that loads plugins18:53
CaptTofuah18:53
CaptTofuzykes-, Kiall, jcmartin: the agent code I think lends itself well to that18:53
jcmartinI agree to use RPC as an API, but it's not an agent, it's the server18:53
KiallThere is nothing preventing the agent from running alongside moniker-central18:54
Kialljcmartin, I'm not sure I understand?18:54
jcmartinTrue, it's more of a deployment decision18:54
jcmartinMy point is that the deployment will be driven by the type of plugin, which may be ok18:55
KiallIs the confusion is over the word "agent"? that the word agent lends itself to being co-located with the backend itself?18:55
KiallAnd with - say powerdns+ldap - that may not be the case18:55
Kiall(I'm speaking of my confusion BTW - Not yours :))18:55
jcmartinKiall: i think it's fine for now, but we may want to look at some DNS deployment model and see how this works18:56
zykes-I guess this is a 2 part question then18:56
Kialljcmartin, agreed.18:56
jcmartinI an volunteering to provide some blurb on that18:56
jcmartinand we can review18:56
KiallSo since we're almost out of time, and I believe this room is booked for18:56
Kiall19:00 (aka 2 mins)18:56
zykes-1 plugin side on the central18:56
zykes-1 plugin on the agent side18:57
Kialllets move onto the very last topic18:57
Kiall#topic Incubation18:57
*** openstack changes topic to "Incubation"18:57
CaptTofudo we vote on something?18:57
KiallCaptTofu, no need I think18:57
CaptTofuok18:57
Kiall#action jcmartin to look into incubation, the process, and the options.18:57
jcmartinagreed18:57
CaptTofuthat was easy18:57
KiallJC agreed earlier today to look into the incubation options for next weeks meeting18:58
CaptTofuthanks JC!18:58
jcmartinI'll take also the deployment option doc18:58
Kialljcmartin, great :)18:58
Kiall#action jcmartin to look into various deployment options18:58
*** jfriedly has joined #openstack-meeting18:58
jcmartinjust on time18:59
KiallOkay - thanks all. Times up!18:59
Kiall#endmeeting18:59
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"18:59
openstackMeeting ended Wed Nov  7 18:59:27 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dnsaas/2012/dnsaas.2012-11-07-18.03.html18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dnsaas/2012/dnsaas.2012-11-07-18.03.txt18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/dnsaas/2012/dnsaas.2012-11-07-18.03.log.html18:59
KiallI'll be in #openstack-dns for a while anyway..18:59
*** Shengjie_Min has joined #openstack-meeting18:59
KiallFeel free to nag me there ;)18:59
*** cp16net is now known as cp16net|away19:00
CaptTofuthanks all19:00
andrewbogottThanks Kiall.19:00
KiallThanks all - See you next week (or sooner in #openstack-dns )19:01
*** dwn has quit IRC19:02
*** jcmartin has left #openstack-meeting19:04
*** patelna has joined #openstack-meeting19:07
*** araveendrann has left #openstack-meeting19:08
*** jrd has joined #openstack-meeting19:12
*** dolphm has joined #openstack-meeting19:15
*** durian has joined #openstack-meeting19:15
*** dolphm has quit IRC19:19
*** koolhead17 has quit IRC19:28
*** dolphm has joined #openstack-meeting19:30
*** durian has quit IRC19:32
*** jfriedly has quit IRC19:32
*** jog0 has joined #openstack-meeting19:33
*** oubiwann has quit IRC19:34
*** metral has quit IRC19:44
*** novas0x2a|laptop has joined #openstack-meeting19:45
*** mattray has joined #openstack-meeting19:45
*** metral has joined #openstack-meeting19:50
*** annegentle__ has joined #openstack-meeting19:50
*** metral_ has joined #openstack-meeting19:54
*** metral_ has quit IRC19:56
*** sarob has quit IRC19:57
*** metral has quit IRC19:57
*** timjr has joined #openstack-meeting19:59
*** egallen has quit IRC20:00
*** maoy has quit IRC20:00
*** mattray2 has joined #openstack-meeting20:06
*** simonmcc2 has quit IRC20:06
*** mattray has quit IRC20:08
*** maurosr has quit IRC20:09
*** jfriedly has joined #openstack-meeting20:09
*** oubiwann has joined #openstack-meeting20:15
*** krtaylor has quit IRC20:16
*** metral has joined #openstack-meeting20:23
*** mattray2 is now known as mattray20:26
*** mattray has joined #openstack-meeting20:26
*** gatuus has quit IRC20:28
*** annegentle__ has quit IRC20:29
*** metral has quit IRC20:31
*** Razique_ has joined #openstack-meeting20:31
*** Razique has quit IRC20:31
*** Razique_ is now known as Razique20:32
*** gatuus has joined #openstack-meeting20:33
*** rhochmuth has joined #openstack-meeting20:37
*** dani4571 has joined #openstack-meeting20:40
*** jfriedly has quit IRC20:44
*** markwash has quit IRC20:47
*** littleidea has joined #openstack-meeting20:48
*** steved_ has quit IRC20:48
*** jbrogan has quit IRC20:49
*** tasdomas has joined #openstack-meeting20:50
*** salmon_ has joined #openstack-meeting20:55
*** simonmcc1 has joined #openstack-meeting20:55
*** simonmcc has quit IRC20:57
*** anniec has joined #openstack-meeting20:59
*** anniec_ has joined #openstack-meeting20:59
nijaba#startmeeting Ceilometer21:00
nijaba#meetingtopic Ceilometer21:00
nijaba#chair nijaba21:00
nijaba#link http://wiki.openstack.org/Meetings/MeteringAgenda21:00
openstackMeeting started Wed Nov  7 21:00:02 2012 UTC.  The chair is nijaba. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
openstackThe meeting name has been set to 'ceilometer'21:00
*** openstack changes topic to " (Meeting topic: Ceilometer)"21:00
openstackCurrent chairs: nijaba21:00
nijabaHello everyone! Show of hands, who is around for the ceilometer meeting?21:00
nijabao/21:00
dhellmanno/21:00
timjr\o21:00
eglynno/21:00
rhochmuth0/21:00
anniec_o/21:00
*** tgall_foo has quit IRC21:00
*** cp16net|away is now known as cp16net21:00
tasdomaso/21:01
nijaba#topic actions from previous meeting21:01
*** openstack changes topic to "actions from previous meeting (Meeting topic: Ceilometer)"21:01
*** jtran has joined #openstack-meeting21:01
nijaba#topic nijaba to send private email to all comitter to come vote on the etherpad in the next 24h21:01
*** openstack changes topic to "nijaba to send private email to all comitter to come vote on the etherpad in the next 24h (Meeting topic: Ceilometer)"21:01
nijabathat was done21:01
nijaba#topic nijaba to then update wiki page as follow: 3+ votes=high, 1or2 vote=medium, low for rest in terms of priorities21:02
*** openstack changes topic to "nijaba to then update wiki page as follow: 3+ votes=high, 1or2 vote=medium, low for rest in terms of priorities (Meeting topic: Ceilometer)"21:02
nijabaI updated the roadmap page, we'll discuss this a bit later21:02
nijaba#topic nijaba to prepare survey for ml next week21:02
*** openstack changes topic to "nijaba to prepare survey for ml next week (Meeting topic: Ceilometer)"21:02
nijabasome of view may have bee21:02
nijaba invited to check it out21:03
nijabawe'll discuss it in a bit21:03
nijaba#topic dhellmann update versioning in ceilometer repo to match openstack standards21:03
*** openstack changes topic to "dhellmann update versioning in ceilometer repo to match openstack standards (Meeting topic: Ceilometer)"21:03
*** anniec has quit IRC21:03
*** anniec_ is now known as anniec21:03
dhellmannI'm working on that right now.21:03
jd__(hi)21:03
dhellmannI think I've figured out what to do, so I expect to have the changes ready before our next meeting.21:03
nijabacool.  any issues?21:03
dhellmannit's confusing, but I'm working it out21:04
*** colinmcnamara has quit IRC21:04
dhellmannif I run into blockers, I know who to talk to for help21:04
*** ayoung is now known as ayoung-afk21:04
jd__isn't that just changing version to 2013.1 ?21:04
nijabaok, should we carry the action for next meeting?21:04
dhellmannjd__: no, there are some modules in common for keeping it up to date correctly21:04
dhellmannnijaba: yes21:04
jd__dhellmann: ok :)21:04
nijabajd__: dhellmann has to use a funky vresion generation script21:04
*** harlowja_ has joined #openstack-meeting21:05
nijaba#action dhellmann update versioning in ceilometer repo to match openstack standards21:05
dhellmannI've been trying to cargo-cult it from some changes proposed for quantum21:05
*** jeffreyb1 has joined #openstack-meeting21:05
nijaba#topic nijaba to add eglynn to ceilometer drivers on satureday if all goes well21:05
*** openstack changes topic to "nijaba to add eglynn to ceilometer drivers on satureday if all goes well (Meeting topic: Ceilometer)"21:05
dhellmannbut I guess I'm going to have to actually learn how this code works :-)21:05
nijabaeglynn is now a core dev for ceilometer. congrats!21:05
dhellmannwelcome!21:06
eglynnthanks!21:06
jd__\o/21:06
asalkeldgo eglynn21:06
nijabaasalkeld: you'll likely be next ;)21:06
dhellmannI've seen no objections for asalkeld's nomination. I need to go back and look at the date on that email. We wait 5 days, right?21:06
nijabaright21:07
nijabat21:07
nijabathat should be tomorrow21:07
*** harlowja_ is now known as harlowja21:07
dhellmannah, good21:07
nijaba#topic dhellmann update readthedocs copy of our docs21:07
*** openstack changes topic to "dhellmann update readthedocs copy of our docs (Meeting topic: Ceilometer)"21:07
dhellmannI believe that is done21:07
nijabanice, thanks21:08
zykes-(cøear21:08
nijabazykes-: ??21:08
nijaba#topic jd and nijaba to start preparing a video demo of ceilometer21:08
*** openstack changes topic to "jd and nijaba to start preparing a video demo of ceilometer (Meeting topic: Ceilometer)"21:08
zykes-nijaba: nothing :)21:08
nijabawe discussed it on monday night, and now have a plan!21:08
nijabajd__ and I are to start a script, but have not started on it yet21:09
nijabaso we'll carry it on21:09
jd__suggestions welcome :)21:09
nijaba#action jd and nijaba to start preparing a video demo of ceilometer21:09
dhellmannthis is an intro to ceilometer itself, right? not just for developers?21:09
nijabaright21:09
zykes-using horizon or ?21:10
harlowjavideo demo, nice21:10
nijabawe were thinking 5 min intro slides, then short demo21:10
nijabausing the den21:10
nijabadebug stuff jd__ wrote which is very nice to show activity21:10
dhellmannsounds like a good idea21:11
*** jamespage_ has joined #openstack-meeting21:12
nijaba#topic Review priorities as proposed on EfficientMetering/RoadMap21:12
*** openstack changes topic to "Review priorities as proposed on EfficientMetering/RoadMap (Meeting topic: Ceilometer)"21:12
harlowjai think timjr is doing some interesting stuff with visualizations21:12
harlowjamight be interesting also21:12
nijabaok, so I updated the page using the result from our "voting" for priorities21:12
nijabaharlowja: that would be welcome21:12
dhellmannnijaba: did we really get the sqlalchemy backend as "low" priority?21:12
nijabadhellmann: yep, so I think a few items need adjustement21:13
dhellmannindeed, that's a high priority for us at DH21:13
dhellmannjtran: what's the status of that driver, I haven't had a chance to look at it in a couple of days21:13
jtransorry, reading back..21:13
jtranoh sqlalchemy, i implemented the API methods for max and sum21:14
jtranI don't think there are anything left.21:14
*** jamespage_ has quit IRC21:14
jtranat least i didn't see any tickets in that regard21:14
dhellmannoh, good21:14
dhellmannI'll run some tests with it asap21:14
nijabanice21:14
timjroop, late to the party21:14
nijabajtran: should I mark it as done on http://wiki.openstack.org/EfficientMetering/RoadMap?21:15
timjryeah, so I'm currently screwing around with zipkin21:15
harlowjatimjr: signed u up for everything21:15
harlowjaha21:15
timjrdrat21:15
*** jamespage_ has joined #openstack-meeting21:15
jtrannijaba: to be safe i'd wait until dhellmann takes a quick test21:15
timjrzipkin is a scala implementation of dapper (googles "distributed tracing infrastructure").  it's open source, and it has some d3.js rendering in the front end21:15
nijabajtran: done but not tested is still done, I think ;)21:16
timjrI think that's a really nice system for understanding what your openstack cluster is up to... so I'm prototyping with it to see what's required21:16
jtrannijaba: in that case, yes ! ;)21:16
nijabatimjr: and you are basing it off the data we collect?21:17
timjrno21:17
eglynnnijaba: did a single vote translate to a "low" priority on the roadmap?21:17
nijabaeglynn: yep, that was what we agreed on, but need to tune now21:18
* eglynn thought he'd voted for the 'assess Synaps' task21:18
*** sarob has joined #openstack-meeting21:18
dhellmanntimjr: so this work is exploratory?21:18
timjryes21:18
nijabaeglynn: ah, right, my mistake there, should hvae been marked21:19
timjrwhatever I do for monitoring, I don't want to make it impossible to use it for dapper-style tracing21:19
timjrso this is an easy way to check :)21:19
eglynnnijaba: cool21:19
nijabaeglynn: fixed21:19
eglynnthanks!21:19
dhellmanntimjr: makes sense21:19
nijabaanyt21:19
nijabaanything else on the roadmap that does not make sens before I sort it?21:20
*** jamespage_ has quit IRC21:20
asalkeldhow long do we have to get features in?21:20
nijabaalso, if you know the bug # for the bugless tasks, feel free to complete21:20
dhellmannnijaba: we should take out the nova-volume item, since we decided not to do it21:21
nijabaasalkeld: until G3 for the base implementation21:21
dhellmannhttp://wiki.openstack.org/GrizzlyReleaseSchedule21:21
dhellmanng3 is feb 2121:21
nijabadhellmann: I just wanted to keep the decision documented...21:21
asalkeldthere is the monitoring blueprint21:22
dhellmannthat's going to be a bit of a challenge with the holiday season at the start of this cycle21:22
dhellmannnijaba: ah, ok21:22
asalkeldbut not sure it could land in time21:22
asalkeldhttps://blueprints.launchpad.net/ceilometer/+spec/monitoring21:22
asalkeldlots to do21:22
dhellmannasalkeld: the teambox link on that page gives me a 40421:22
jd__asalkeld: that should depends on multi-publisher blueprint I think, no?21:23
asalkeldyea, me too - I'll sort it21:23
*** esheffie1d has quit IRC21:23
asalkeldsure21:23
*** esheffield has joined #openstack-meeting21:23
jd__I'll add it then :)21:23
asalkeldsay, any reason why compute agent is in ceilometer and not in nova?21:24
asalkeldjust seems to make more sense there IMO21:24
jd__because we're not core I'd say21:24
dhellmannasalkeld: it depends on ceilometer code that was only in our project at the time, and we were trying to be "self contained" as much as possible for the last cycle21:24
nijabaasalkeld: simplicity, but we should push as much as possible to nova now that we are incubated21:24
asalkeldk21:24
asalkeldjust makes that whole db issue go away21:25
dhellmannyeah -- it would be nice if there was a way to have nova load extensions that wanted periodic tasks21:25
eglynnaren't we moving towards avoiding DB access by using the novaclient?21:25
dhellmannthen we could release it as a plugin21:25
eglynn(to list instances on a host etc.)21:26
dhellmanneglynn: yes, but we do still import nova's libvirt wrapper code, and it would be nice to get rid of that dependency, too21:26
asalkeldyea, dhellmann we could just have the same agent, but in nova21:26
jd__I think we could export the function we need over RPC21:26
dhellmannasalkeld: that might make sense21:27
nijabapollster for metering network bandwidth is marked as partially done.  Any plan from anyone to complete?21:27
jd__that's something that could be accepted21:27
dhellmannnijaba: I think that's done21:27
nijabadhellmann: ok, \i'll fix then21:27
jtrandhellmann: not external21:27
dhellmannthe associated bug is marked "fix released"21:27
jtrannijaba: not done21:27
dhellmannjtran: external traffic?21:27
jd__we only have VM vif counters21:28
jtranthe network bandwidth metering only implemented for internal network banadwidth21:28
nijabajtran: do you have a good solution to distinguis external traffic?21:28
nijabajtran: dhellmann used something totally differetn21:28
jtrannijaba: no.  i looked into that before using iptables accounting.  is not easy21:28
dhellmannjtran: I don't think there's any way for us to get external stats21:28
dhellmannwe're asking our router for those stats (each tenant has a software router)21:28
jtrandhellmann:  ok, if we are not considering external traffic, then please go ahead and mark it done21:28
nijabajtran: so I think we should mak it done even though we have limitatins21:28
*** mnewby_ has joined #openstack-meeting21:29
* jd__ agrees21:29
dhellmannI agree. Even if we find a better solution, we're likely to need a couple of implementations for different configurations.21:29
nijabaupdated21:29
salmon_I yhon you can get it from openvswitch21:30
salmon_*I think21:30
nijabaso, If you agree, I'll action myself to sort the list by prio, add bugs if none exist for each item on the list21:30
jtransalmon_:  i haven't looked at the openvswich/quantum implementation.   that's probably likely.21:30
jd__nijaba: don't hesitate to use blueprints also for changes/features :)21:31
nijababut I would need someone's help to give t-shirt size to features21:31
eglynnbacktracking to the ceilo-agent-moves-into-nova idea for a sec ...21:31
eglynnso that seems to leak some monitoring-related concerns into nova, frequency of the polling cycle etc.21:31
eglynnalso, can we rely on the timeliness of periodic tasks within a loaded nova compute agent?21:31
*** krtaylor has joined #openstack-meeting21:31
asalkeldhave as a seperate daemon21:31
asalkeld(as now)21:31
asalkeldand same/simerlar config options21:32
*** mnewby has quit IRC21:32
*** mnewby_ is now known as mnewby21:32
eglynnwould that defeat the purpose slightly?21:32
nijabaeglynn: and keep it under our responsability to maintain it21:32
dhellmannwhat would be the point of moving it to another git repo, then?21:32
eglynn(i.e. to simplify the deployment, one fewer worker etc.)21:32
asalkeldeglynn, it's to make accessing the data easier21:32
asalkeldnot having to import nova stuff from ceilometer21:33
harlowjaeglynn: if celiometer provides a library, could then we ask the nova people to write hookins to that library, idk21:33
eglynnyep, it would allow 'private' APIs to be used freely21:33
harlowjamore libraries maybe21:33
asalkeldyar21:33
asalkeld(just an idea)21:33
jd__so we make nova import ceilometer stuff instead?21:33
eglynnother option though would be for nova to export a stable public API for ceilo to use21:33
asalkeldjd__, yes but minimal stats_send() api21:34
*** vds has joined #openstack-meeting21:34
*** jrodom has quit IRC21:34
dhellmanneglynn: I like that better. How practical is it?21:34
asalkeldnot really21:34
timjrif it exposes an API, wouldn't you have to poll?21:34
*** colinmcnamara has joined #openstack-meeting21:34
asalkeldwe do anyway21:34
eglynntimjr: yep, as now21:34
asalkeldproblem is nova is only one project21:34
jd__poll a stable API exported via RPC providing CPU time, IO, etc for all virt supported by nova21:34
asalkeldthen to do the same for all projects?21:35
timjrthat sounds reasonable to me21:35
jd__that's something looking doable and acceptable for nova21:35
nijabaOk, it seems that we have a good discussion topic here.  Should we action someone to think up a proposal to be debated next week?21:35
harlowjahmmm, ya, so polling is one way, the monitoring stuff seems like it would be the push part though21:35
jd__monitoring stuff?21:35
nijabaany volunteer?21:35
timjrharlowja: I think it's fine to have a queryable API for system stats like cpu time and so on21:36
*** sandywalsh has quit IRC21:36
eglynnnijaba: I can work up a proposal for discussion21:36
asalkeldI can help21:36
jd__I can comment :p21:36
eglynnasalkeld cool21:36
harlowjabut should nova be doing that, or should it just be broadcasting and letting some other system provide the query ontop of that raw data21:36
jeffreyb1timjr: not really so nice polling large clusters21:36
*** mnewby_ has joined #openstack-meeting21:36
nijaba#action eglynn to writup a nova integration proposal to be discussed next week21:37
timjrjeffreyb1: we would likely not use it for production monitoring21:37
timjrjeffreyb1: but there's no harm having it21:37
jeffreyb1timjr: famous last words21:37
asalkeldproblem is it uses rpc21:37
timjrjeffreyb1: could be convenient: hit a little status URL to find out what a node thinks it's doing, instead of going off to your monitoring dashboard21:37
harlowjatimjr: harm being code confusion21:37
jeffreyb1timjr: yup, def convenient but not a good way to go long term IMO21:38
nijabaOk, so could you all please take a few moment today or tomorrow to help me fill the roadmap with the valid links?  That would help a lot21:38
nijabaand t shirt sizes21:38
timjrwell, you've got to gather all the stats anyway, putting up the polling API is mostly about keeping a local buffer of stat values21:38
harlowjaXXXXXXX-small21:38
jd__nijaba: how you want to proceed?21:38
harlowjatimjr: agreed21:38
jeffreyb1timjr: those stats are good for r/t monitoring but the polling will get out of hand21:38
*** mnewby has quit IRC21:39
*** mnewby_ is now known as mnewby21:39
timjrjeffreyb1: again, I would not use polling for actual monitoring21:39
harlowjatimjr: simplicity though, start simple no?21:39
*** dwcramer has quit IRC21:39
nijabaI'd suggest each one have a pass at it for the action they care about in the next 24h21:39
eglynnjeffreyb1: by out of hand, too frequent?21:39
timjrharlowja: I don't plan to implement it at present, but if ceilometer wants it, I don't see any conflict with our needs21:39
jeffreyb1timjr: so a different mechanism for monitoring of the same stats?21:39
harlowjadon't do local buffering, have simple broadcasting, get as far as u can with that, then add in local buffering, polling21:39
*** colinmcnamara has quit IRC21:39
jd__nijaba: ack21:39
dhellmannnijaba: ack21:39
jeffreyb1eglynn: thinking of polling large clusters, 1000s of machines, kind of a pain21:40
timjrjeffreyb1: yeah.  hadoop does that, for example.21:40
jd__shall we move on?21:40
asalkeldyes21:40
nijabasorry to be a pain, but could we please keep on the agenda until the open discussion?21:40
jeffreyb1eglynn: rather see fire and forget, let the collector deal with it21:40
jeffreyb1nijaba: sure21:40
nijabaok, I think we are ready to move to the next topic21:41
eglynnjeffreyb1: re. scale, a local agent would just be polling the instances local to each compute node21:41
eglynnnijaba: k21:41
nijaba#topic Review survey prepared by nijaba21:41
*** openstack changes topic to "Review survey prepared by nijaba (Meeting topic: Ceilometer)"21:41
nijabaif you had the chance to review it, any comments about it?21:41
nijabado you think it is ready to be shared widely?21:42
nijabameaning the opnestack ml21:42
eglynnnijaba: do you have a link handy?21:42
jtrannijaba:  i tried submitting my survey and it says "requires input" ...21:43
jd__reviewed21:43
nijaba#link http://www.surveymonkey.com/s/SY55BHR21:43
jtraneven tho i made sure all fields had an order #.21:43
jtran'this question requires an answer'21:43
nijabajtran: really?  I did not have this issue... :(21:43
jtrani reproduced it right now21:44
jtransurvey questions numbered 1-16.  then i even put something in question #2.  click submit and that's what i get.  using chrome on osx21:44
jtran1-14 i meant21:44
nijabajtran: yep, I just had the same pb.  Did not use to have it.  I'll disable the check for now, but will need to figure out what is going on21:45
nijabaok, I removed the restriction21:46
asalkeldsorry guys, I need to take kids to school be back in ~15min21:46
nijabaasalkeld: we'll be around :)21:47
*** metral has joined #openstack-meeting21:47
*** DanD has joined #openstack-meeting21:47
dhellmannwhat's next?21:47
eglynnone general point on the survey, how are we  gonna set expectations in terms of being bound by the result?21:47
nijabaso anyone against us sharing the survey widely?21:48
eglynn(e.g. for guidance only?)21:48
*** markwash has joined #openstack-meeting21:48
nijabaeglynn: just a poll, not commitment21:48
*** mnewby_ has joined #openstack-meeting21:48
eglynnnijaba: sounds fair21:48
nijabait's really to make sure we are not too far off our potential users21:48
nijabadhellmann: since you suggested it, what's your pov?21:49
*** mnewby_ has joined #openstack-meeting21:49
*** esheffield has quit IRC21:49
dhellmannwe should stress those expectations in the email we send to the list21:49
dhellmannin the invitation, I mean21:49
nijabadhellmann: +121:49
eglynncool21:50
dhellmannI'm not sure how to ask for input without asking for input. ;-)21:50
*** annegentle__ has joined #openstack-meeting21:50
*** mnewby has quit IRC21:50
*** jog0 has quit IRC21:50
nijabaeglynn: asalkeld: do you mind if I remove the qpid and zeromq items from the list.  It seems the issues comes from having more than 14 items in the list21:50
eglynnnijaba: fair enough21:51
nijabaand eglynn I think qpid will be a req for rhat in any case, right?21:51
dhellmannnijaba: let's keep those and remove some of the internal architectural stuff21:51
eglynn(I think Rh has sufficient interest in qpid to test anyway)21:51
dhellmannlike removing nova imports21:51
*** dolphm has quit IRC21:51
nijabadhellmann: that would work too21:51
* dhellmann can't see the list any more because he submitted answers to the survey21:51
dhellmann"remove db access" looks like another "features" users won't care about and that we're going to do anyway21:52
nijabadhellmann: I'll remove the nova import and the sqlalchemy and it should work. thanks21:52
dhellmannok21:52
nijabaok, fixed now21:54
nijabaso, I'll action myself to send the email tomorrow, unless someone is against that21:55
dhellmann+121:55
nijaba#action nijaba to send an invite to fill t21:55
zykes-what's the whole survey stuff ?21:55
nijaba#action nijaba to send an invite to fill the survey21:55
*** colinmcnamara has joined #openstack-meeting21:56
nijaba#topic Open Discussion21:56
*** openstack changes topic to "Open Discussion (Meeting topic: Ceilometer)"21:56
nijabazykes-: not sure I understand your question21:56
eglynndid folks get a chance to review sandywalsh's unification write-up?21:56
eglynn#link http://wiki.openstack.org/UnifiedInstrumentationMetering21:56
jtranyes21:56
dhellmannzykes-: we are soliciting input from potential users about what features they consider important21:56
jtrangood stuff21:56
dhellmannunfortunately, no21:56
jeffreyb1yes, i read it21:57
*** sarob has quit IRC21:57
harlowjait seems complicated though21:57
harlowjabut i think the right direction, i think we are working on unifying the bottom layer21:57
harlowjatimjr: mainly21:57
eglynnyep, agreed21:58
jeffreyb1really struggling with the reliance on rabbit21:58
eglynnI wasn't sure tho' about the "Remove the Compute service that Ceilometer uses ..." suggestion21:58
eglynnkinda ties in with the earlier discussion on moving stuff into nova21:58
*** patelna_ has joined #openstack-meeting21:58
harlowjatach is one way, but i don't think the only way21:58
harlowjahttp://wiki.openstack.org/InstrumentationMetricsMonitoring is the other one that is more 'low level'21:58
timjrwell, I don't mind if people want to use amqp to send around messages, but I would consider that a configuration option21:58
timjrthe notification system already does21:58
asalkeldback21:58
harlowjatimjr: sure21:59
*** tgall_foo has joined #openstack-meeting21:59
*** metral has quit IRC21:59
*** jog0 has joined #openstack-meeting21:59
*** metral has joined #openstack-meeting21:59
eglynnjeffreyb1: is the reliance on rabbit still a huge problem for you if sufficiently partitioned from the prod message bus?21:59
eglynn(e.g. a separate rabbit broker/cluster)22:00
timjreglynn: anything other than a simple point-to-point communication has many of its own failure modes that you would want to monitor22:00
dhellmannI thought we already agreed we would support multiple publishing methods.22:00
jeffreyb1eglynn: as tim alluded to, so long as it is a config option and pluggable to use something else then it is not a prob22:00
eglynndhellmann: yep22:01
* nijaba let us run overtime as I do not think th22:01
eglynnjeffreyb1: cool22:01
jeffreyb1btw, vish closed the BP and marked it as 'obsolete'22:01
* nijaba let us run overtime as I do not think there is another meeting after us22:01
*** patelna has quit IRC22:01
jeffreyb1he suggested we put it in openstack-common or "external"22:01
timjryeah, i think that means somehow it wasn't clear enough :)22:01
nijabadhellmann: yep, that was acted for me too22:01
timjrthe functions you call can be in a separate library, but the calls will have to land in nova and other components...22:02
asalkeldsure22:02
asalkeldseems not everyone wants a single library to emit the stats22:02
asalkeldmight need to have tracing and metering/monitoring22:03
timjrum... well, I guess there's no accounting for taste22:03
asalkeldas seperate entities22:03
*** salv-orlando_ has joined #openstack-meeting22:03
asalkeldI am not fussed22:03
dhellmannfwiw, I've been looking at https://github.com/BrightcoveOS/Diamond/ this week and it has some of the stuff we've discussed doing with different polling rates and publishing methods already22:03
*** danwent_ has joined #openstack-meeting22:03
timjrasalkeld: I would hope that the API is good enough that switching from two libraries to one is a simple matter of refactoring22:04
asalkeldcool looking22:04
*** Mandell_ has joined #openstack-meeting22:04
dhellmannwe're going to be using it for monitoring here at DH, so I wrote a ceph plugin for it. pretty easy. could use some polish, but maybe we can steal ideas or even collaborate22:04
timjrdhellmann: that's an interesting link22:04
eglynndhellmann: interesting ...22:04
dhellmannI'm not super happy with the "scan a directory for plugins" approach they took, and the packaging is rough, but all the pieces seem to be there.22:05
*** nijaba_ has joined #openstack-meeting22:05
*** harlowja_ has joined #openstack-meeting22:05
dhellmannthey're focusing on monitoring, of course22:05
dhellmannI'm not sure if you can specify that the same data goes to different sources at different rates.22:05
dhellmannsorry, different destinations not sources22:06
asalkeldyip22:06
* nijaba_ was temporarily disconnected :(22:06
eglynnthat would be fairly crucial22:06
dhellmanneglynn: yeah, definitely22:06
dhellmannthey've been very welcoming of patches this week, even without me contacting them directly, so that might be worth a go22:06
asalkeldclass Metric(object):22:06
asalkeld    def __init__(self, path, value, timestamp=None, precision=0):22:06
asalkelddon't see how we can add more info22:07
*** boden has quit IRC22:07
*** novas0x2a|lapto1 has joined #openstack-meeting22:07
asalkelduser/resource info22:07
dhellmannyeah, it's definitely not good enough for billing22:07
*** mnewby_ has quit IRC22:07
dhellmannalthough the publisher pulls data out of the Metric, so if we change that class we could add data that is only used by some publishers22:07
asalkeldthe just need **kwargs22:08
nijaba_dhellmann: and the ncome the transport issue...22:08
dhellmannI'm not necessarily suggesting we use their daemon instead of ours, but we might get some ideas about, for example, how to configure things22:08
*** danwent has quit IRC22:08
*** Mandell has quit IRC22:08
*** nijaba has quit IRC22:08
*** salv-orlando has quit IRC22:08
*** novas0x2a|laptop has quit IRC22:08
*** danwent_ is now known as danwent22:08
*** salv-orlando_ is now known as salv-orlando22:08
*** nijaba_ is now known as nijaba22:08
eglynndefo worth a sniff around22:08
dhellmannnijaba_: some of that didn't come through, I think, I'm not sure what you mean22:08
timjrso would a set of arbitrary ket/value pairs be sufficient for billing purposes?22:08
timjrkey/value, even22:08
dhellmanntimjr: no22:08
*** nijaba has quit IRC22:08
*** nijaba has joined #openstack-meeting22:08
timjrdhellmann: what else do you need?22:08
dhellmannwe need timestamps, for one22:09
dhellmannmessages need to be signed for auditing purposes22:09
timjroh, sure22:09
asalkeld, timestamp=None22:09
timjrthat's an interesting one22:09
asalkeldthey have that22:09
nijabaand counters for auditability22:09
dhellmannwe need the metadata so consumers can compute rates based on properties of the instance22:09
asalkeldwell we write the handler22:09
*** harlowja has quit IRC22:09
*** harlowja_ is now known as harlowja22:09
timjrnijaba: you mean unique message IDs?22:09
dhellmannand we need to know the owner22:09
nijabatimjr: no, incremental counters22:09
nijabatimjr: so that you can dtect missing or inserted messages22:10
timjrI see22:10
jeffreyb1so that is like a stateful metric?22:10
dhellmannnijaba: did counters make it onto the priority list for grizzly? :-)22:10
asalkeldsequenced metric22:10
jeffreyb1hmm22:11
nijabawe don't really care a22:11
nijabaabout the order22:11
nijabamore about tempering22:11
timjrnod22:11
timjrthat makes sense22:11
*** metral_ has joined #openstack-meeting22:12
asalkeldwell worth a look22:12
*** gatuus has quit IRC22:12
nijabashould we action something here?22:12
timjrI think if tampering were to become an issue, you've got some fundamental access control problems on your openstack cluster22:12
dhellmannnijaba: I'm not sure what that action would be.22:13
timjr... but I can see being paranoid where billing is concerned22:13
*** mtreinish has quit IRC22:13
nijabatimjr: yep, that's something people tend to become paranoid about22:13
* dhellmann needs to leave soon22:13
* nijaba too22:13
asalkeld"investigate diamond for use to generate stats"22:14
*** andrewbogott is now known as andrewbogott_afk22:14
*** metral_ has quit IRC22:14
nijabashould we end the meeting for now?22:14
asalkeldyip22:14
zykes-btw22:14
eglynnk22:14
dhellmannok22:14
nijabaasalkeld: care to take that action?22:14
asalkeldsure22:14
zykes-for chargeback >> bufunfa uses ceilometer22:14
zykes-for people that care22:15
*** markvoelker has quit IRC22:15
nijaba#action asalkeld investigate diamond for use to generate stats22:15
*** maurosr has joined #openstack-meeting22:15
nijaba#endmeeting22:15
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:15
openstackMeeting ended Wed Nov  7 22:15:32 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:15
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-11-07-21.00.html22:15
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-11-07-21.00.txt22:15
openstackLog:            http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-11-07-21.00.log.html22:15
*** jeffreyb1 has left #openstack-meeting22:15
nijabaThanks everyone22:15
zykes-noone cares ;p22:15
eglynn'night all22:15
*** metral has quit IRC22:15
tasdomasgood night22:15
asalkeldnight22:15
jtranquick question off topic can i close https://bugs.launchpad.net/ceilometer/+bug/1053514 as invalid or 'wont fix'22:16
uvirtbot`Launchpad bug 1053514 in ceilometer "Pollster for external network traffic" [Wishlist,Confirmed]22:16
jtransince we won't be doing external network pollster22:16
*** patelna has joined #openstack-meeting22:16
dhellmanngood night!22:16
dhellmannjtran: yeah, I think so22:16
jtranok22:16
dhellmannwe can reopen later22:16
*** rhochmuth has quit IRC22:16
dhellmannttyl22:16
*** dhellmann has quit IRC22:17
*** novas0x2a|lapto1 has quit IRC22:17
*** jtran has left #openstack-meeting22:17
*** novas0x2a|laptop has joined #openstack-meeting22:17
*** nealph has joined #openstack-meeting22:17
timjrciao22:17
*** timjr has left #openstack-meeting22:18
*** metral has joined #openstack-meeting22:18
*** lloydde has quit IRC22:18
*** lloydde_ has joined #openstack-meeting22:18
*** maurosr has quit IRC22:20
*** novas0x2a|laptop has quit IRC22:22
*** novas0x2a|laptop has joined #openstack-meeting22:24
*** salmon_ has left #openstack-meeting22:25
*** nealph has left #openstack-meeting22:27
*** DanD has quit IRC22:28
*** nealph has joined #openstack-meeting22:28
*** s0mik has quit IRC22:29
*** metral has quit IRC22:32
*** metral has joined #openstack-meeting22:32
*** danwent has quit IRC22:36
*** s0mik has joined #openstack-meeting22:36
*** gyee has quit IRC22:40
*** tgall_foo has quit IRC22:43
*** adjohn has quit IRC22:44
*** krtaylor has quit IRC22:46
*** Razique has quit IRC22:48
*** clarkb has quit IRC22:49
*** tgall_foo has joined #openstack-meeting22:50
*** tgall_foo has joined #openstack-meeting22:50
*** dwcramer has joined #openstack-meeting22:52
*** heckj has quit IRC22:52
*** annegentle__ has quit IRC22:53
*** metral_ has joined #openstack-meeting22:54
*** metral_ has quit IRC22:55
*** dolphm has joined #openstack-meeting22:56
*** gongysh has joined #openstack-meeting22:56
*** metral has quit IRC22:57
*** jcooley has joined #openstack-meeting22:57
*** dani4571 has quit IRC23:00
*** dwcramer has quit IRC23:02
*** jcooley has quit IRC23:02
*** patelna__ has joined #openstack-meeting23:02
*** jfriedly has joined #openstack-meeting23:03
*** patelna_ has quit IRC23:05
*** patelna_ has joined #openstack-meeting23:06
*** patelna has quit IRC23:06
*** tgall_foo has quit IRC23:06
*** john5223 has quit IRC23:07
*** adjohn has joined #openstack-meeting23:07
*** ryanpetr_ has joined #openstack-meeting23:08
*** colinmcnamara has left #openstack-meeting23:10
*** ryanpetrello has quit IRC23:11
*** adjohn has quit IRC23:14
*** adjohn has joined #openstack-meeting23:15
*** ryanpetr_ has quit IRC23:23
*** simonmcc has joined #openstack-meeting23:25
*** anniec has quit IRC23:28
*** markmcclain has quit IRC23:29
*** s0mik has quit IRC23:32
*** cp16net is now known as cp16net|away23:34
*** cp16net|away is now known as cp16net23:37
*** krtaylor has joined #openstack-meeting23:38
*** dolphm has quit IRC23:42
*** metral has joined #openstack-meeting23:45
*** mattray has quit IRC23:48
*** s0mik has joined #openstack-meeting23:49
*** dwcramer has joined #openstack-meeting23:53
*** metral_ has joined #openstack-meeting23:55
*** metral has quit IRC23:55
*** metral_ is now known as metral23:55
*** mnewby has joined #openstack-meeting23:59

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