Wednesday, 2012-10-24

*** patelna has quit IRC00:00
*** ryanpetr_ has joined #openstack-meeting00:07
*** ryanpetrello has quit IRC00:10
*** nati_ueno has quit IRC00:12
*** littleidea has quit IRC00:13
*** famao has quit IRC00:13
*** metral_ has joined #openstack-meeting00:13
*** littleidea has joined #openstack-meeting00:13
*** salv-orlando has quit IRC00:16
*** metral has quit IRC00:17
*** metral_ is now known as metral00:17
*** littleidea has quit IRC00:21
*** littleidea has joined #openstack-meeting00:22
*** littleidea has quit IRC00:27
*** littleidea has joined #openstack-meeting00:31
*** littleidea has left #openstack-meeting00:32
*** jaypipes has joined #openstack-meeting00:34
*** s0mik has quit IRC00:43
*** tgall_foo has quit IRC00:47
*** danwent has quit IRC01:01
*** danwent has joined #openstack-meeting01:01
*** danwent has quit IRC01:02
*** ogelbukh has quit IRC01:05
*** ogelbukh has joined #openstack-meeting01:05
*** ryanpetr_ has quit IRC01:07
*** jakedahn is now known as jakedahn_zz01:15
*** dendrobates is now known as dendro-afk01:18
*** dendro-afk is now known as dendrobates01:20
*** jog0 has quit IRC01:21
*** adjohn has quit IRC01:41
*** dolphm has joined #openstack-meeting02:03
*** dolphm has quit IRC02:05
*** anniec has quit IRC02:09
*** s0mik has joined #openstack-meeting02:11
*** AlanClark has quit IRC02:14
*** Gordonz has joined #openstack-meeting02:15
*** nati_ueno has joined #openstack-meeting02:20
*** Gordonz has quit IRC02:26
*** jdurgin has quit IRC02:30
*** maurosr has quit IRC02:30
*** Mandell has quit IRC02:30
*** hemna has quit IRC02:31
*** zhuadl has joined #openstack-meeting02:32
*** zhuadl has quit IRC02:32
*** sdague has left #openstack-meeting02:33
*** amotoki has quit IRC02:35
*** tgall_foo has joined #openstack-meeting02:44
*** ryanpetrello has joined #openstack-meeting02:48
*** mnewby has quit IRC02:49
*** dcramer_ has quit IRC02:59
*** ywu_ has quit IRC03:06
*** mnewby has joined #openstack-meeting03:10
*** danwent has joined #openstack-meeting03:14
*** dcramer_ has joined #openstack-meeting03:15
*** tgall_foo has quit IRC03:29
*** dcramer_ has quit IRC03:45
*** tongli has quit IRC03:58
*** littleidea has joined #openstack-meeting04:00
*** Mandell has joined #openstack-meeting04:07
*** ryanpetrello has quit IRC04:14
*** the8thbit has quit IRC04:15
*** s0mik has quit IRC04:38
*** oubiwann has quit IRC04:40
*** koolhead17 has quit IRC04:51
*** danwent has quit IRC04:52
*** jhenner has joined #openstack-meeting05:02
*** davidh_ has joined #openstack-meeting05:14
*** davidhadas has quit IRC05:14
*** danwent has joined #openstack-meeting05:21
*** garyk has quit IRC05:32
*** koolhead17 has joined #openstack-meeting05:40
*** ryanpetrello has joined #openstack-meeting05:41
*** adjohn has joined #openstack-meeting05:47
*** jakedahn_zz is now known as jakedahn05:48
*** ryanpetrello has quit IRC05:51
*** mnewby has quit IRC06:04
*** nati_ueno has quit IRC06:06
*** henrynash has joined #openstack-meeting06:11
*** afazekas has joined #openstack-meeting06:15
*** littleidea has quit IRC06:18
*** danwent has quit IRC06:28
*** afazekas has quit IRC06:36
*** jakedahn is now known as jakedahn_zz06:38
*** rafaduran has joined #openstack-meeting06:40
*** ttrifonov_zZzz is now known as ttrifonov06:54
*** henrynash has quit IRC07:02
*** mikal has quit IRC07:22
*** mikal has joined #openstack-meeting07:33
*** Dorogs has joined #openstack-meeting07:35
*** afazekas has joined #openstack-meeting07:39
*** salv-orlando has joined #openstack-meeting07:43
*** garyk has joined #openstack-meeting07:52
*** henrynash has joined #openstack-meeting08:00
*** EmilienM has joined #openstack-meeting08:00
*** salv-orlando_ has joined #openstack-meeting08:06
*** salv-orlando has quit IRC08:06
*** salv-orlando_ is now known as salv-orlando08:06
*** adjohn has quit IRC08:07
*** almaisan-away is now known as al-maisan08:20
*** blackninja has joined #openstack-meeting08:24
*** darraghb has joined #openstack-meeting08:31
*** henrynash has quit IRC08:33
*** salv-orlando_ has joined #openstack-meeting08:42
*** salv-orlando has quit IRC08:42
*** salv-orlando_ is now known as salv-orlando08:42
*** EmilienM has left #openstack-meeting08:45
*** salv-orlando has quit IRC08:47
*** EmilienM has joined #openstack-meeting09:08
*** EmilienM has left #openstack-meeting09:11
*** EmilienM has joined #openstack-meeting09:11
*** boden has joined #openstack-meeting09:26
*** koolhead17 has quit IRC10:00
*** henrynash has joined #openstack-meeting10:17
*** al-maisan is now known as almaisan-away10:39
*** ryanpetrello has joined #openstack-meeting10:51
*** maurosr has joined #openstack-meeting10:52
*** maurosr has quit IRC10:54
*** maurosr has joined #openstack-meeting10:55
*** arbrandes has joined #openstack-meeting11:06
*** littleidea has joined #openstack-meeting11:06
*** littleidea has left #openstack-meeting11:06
*** EugeneNikanorov is now known as enikanorov11:12
*** shang has joined #openstack-meeting11:21
*** shang_ has joined #openstack-meeting11:35
*** shang has quit IRC11:36
*** davidh_ has quit IRC11:38
*** davidhadas has joined #openstack-meeting11:39
*** shang_ has quit IRC11:39
*** littleidea has joined #openstack-meeting11:42
*** jamespage_ has joined #openstack-meeting11:44
*** jamespage_ has quit IRC11:45
*** salv-orlando has joined #openstack-meeting11:46
*** henrynash has quit IRC11:46
*** markvoelker has joined #openstack-meeting11:52
*** littleidea has left #openstack-meeting11:56
*** dolphm has joined #openstack-meeting12:02
*** almaisan-away is now known as al-maisan12:05
*** milner has joined #openstack-meeting12:18
*** ryanpetrello has quit IRC12:28
*** ryanpetrello has joined #openstack-meeting12:29
*** sandywalsh has joined #openstack-meeting12:32
*** rafaduran has left #openstack-meeting12:33
*** sandywalsh_ has joined #openstack-meeting12:35
*** sandywalsh has quit IRC12:36
*** rafaduran has joined #openstack-meeting12:36
*** rafaduran has left #openstack-meeting12:37
*** sandywalsh has joined #openstack-meeting12:44
*** sandywalsh_ has quit IRC12:44
*** FN-OS has joined #openstack-meeting12:44
*** anniec has joined #openstack-meeting12:57
*** anniec_ has joined #openstack-meeting12:58
*** anniec has quit IRC13:01
*** anniec_ is now known as anniec13:01
*** dprince has joined #openstack-meeting13:05
*** littleidea has joined #openstack-meeting13:07
*** FN-OS has quit IRC13:10
*** FN-OS has joined #openstack-meeting13:11
*** EmilienM has left #openstack-meeting13:16
*** EmilienM has joined #openstack-meeting13:16
*** blamar has joined #openstack-meeting13:19
*** jhenner has quit IRC13:22
*** roadTripper has joined #openstack-meeting13:25
*** blamar has quit IRC13:27
*** dendrobates is now known as dendro-afk13:27
*** dendro-afk is now known as dendrobates13:27
*** joesavak has joined #openstack-meeting13:28
*** markmcclain has joined #openstack-meeting13:29
*** tgall_foo has joined #openstack-meeting13:29
*** tgall_foo has joined #openstack-meeting13:29
*** EmilienM has quit IRC13:30
*** tgall_foo has quit IRC13:34
*** tgall_foo has joined #openstack-meeting13:35
*** tgall_foo has joined #openstack-meeting13:35
*** EmilienM has joined #openstack-meeting13:36
*** ryanpetr_ has joined #openstack-meeting13:41
*** tgall_foo has quit IRC13:43
*** dhellmann-afk is now known as dhellmann13:43
*** ryanpetrello has quit IRC13:44
*** ryanpetr_ has quit IRC13:46
*** dolphm has quit IRC13:47
*** tongli has joined #openstack-meeting13:50
*** dcramer_ has joined #openstack-meeting13:53
*** tgall_foo has joined #openstack-meeting13:54
*** jhenner has joined #openstack-meeting13:56
*** gallth has joined #openstack-meeting14:01
*** jhenner has quit IRC14:02
*** tgall_foo has quit IRC14:04
*** mtreinish has joined #openstack-meeting14:05
*** dkehn_afk is now known as dkehn14:06
*** dkehn has left #openstack-meeting14:06
*** boden has quit IRC14:19
*** blamar has joined #openstack-meeting14:22
*** dolphm has joined #openstack-meeting14:22
*** cp16net is now known as cp16net|away14:26
*** cp16net|away is now known as cp16net14:26
*** rafaduran has joined #openstack-meeting14:31
*** maurosr has quit IRC14:31
*** maurosr has joined #openstack-meeting14:31
*** maurosr has joined #openstack-meeting14:33
*** rnirmal has joined #openstack-meeting14:35
*** blamar has quit IRC14:36
*** joesavak has quit IRC14:37
*** Mandell has quit IRC14:37
*** joesavak has joined #openstack-meeting14:37
*** blamar has joined #openstack-meeting14:39
*** alexpilotti has joined #openstack-meeting14:41
*** cp16net is now known as cp16net|away14:44
*** al-maisan is now known as almaisan-away14:44
*** anniec has quit IRC14:53
*** cp16net|away is now known as cp16net14:53
*** anniec has joined #openstack-meeting14:53
*** anniec has quit IRC15:07
*** jsavak has joined #openstack-meeting15:10
*** dhellmann is now known as dhellmann-afk15:13
*** joesavak has quit IRC15:14
*** FN-OS has quit IRC15:15
*** henrynash has joined #openstack-meeting15:34
*** rnirmal has quit IRC15:34
*** rnirmal has joined #openstack-meeting15:34
*** jhenner has joined #openstack-meeting15:35
*** rnirmal_ has joined #openstack-meeting15:35
*** jhenner has quit IRC15:38
*** jhenner has joined #openstack-meeting15:38
*** rnirmal has quit IRC15:39
*** rnirmal_ is now known as rnirmal15:39
*** markmcclain has quit IRC15:44
*** blackninja has quit IRC15:53
*** jhenner has quit IRC15:55
*** jbrogan has joined #openstack-meeting15:58
*** jhenner has joined #openstack-meeting15:58
*** thingee_zz is now known as thingee16:00
*** winston-d has joined #openstack-meeting16:00
*** rongze has joined #openstack-meeting16:01
*** jhenner has quit IRC16:02
*** milner has quit IRC16:03
*** littleidea has quit IRC16:03
*** zhidong has quit IRC16:04
*** zhidong has joined #openstack-meeting16:04
*** dcramer_ has quit IRC16:05
*** bswartz has joined #openstack-meeting16:06
bswartzhey I'm here16:06
*** dricco has joined #openstack-meeting16:06
DuncanTMe too16:06
winston-d:)16:06
driccoi'm here16:06
thingeeo/16:06
bswartzoh good I'm not the only late one16:06
rnirmaljgriffith: ping16:07
*** alexpilotti has quit IRC16:08
*** huats has quit IRC16:08
*** spn_ has quit IRC16:08
*** kpepple_ has quit IRC16:08
*** sleepson| has quit IRC16:08
*** huats has joined #openstack-meeting16:08
*** huats has quit IRC16:08
*** huats has joined #openstack-meeting16:08
*** sleepson- has joined #openstack-meeting16:08
*** Dorogs has quit IRC16:08
rongzehi, every one16:08
*** kpepple has joined #openstack-meeting16:08
winston-drongze, hi16:09
rongzewinston-d :)16:09
*** jdurgin has joined #openstack-meeting16:10
rongzeI think john is too busy...16:10
bswartzdoes anyone else want to chair the meeting?16:11
*** littleidea has joined #openstack-meeting16:11
*** woodspa has joined #openstack-meeting16:11
*** davidhadas has quit IRC16:12
*** davidhadas has joined #openstack-meeting16:12
thingeewe should definitely set someone as a backup for such cases16:12
bswartzdoes the bot only recognize jgriffith?16:13
jgriffith:)16:13
thingeeoh ho16:13
jgriffithAm I late?16:13
bswartznot at all16:13
jgriffithLOL16:13
bswartzyou are exactly on time16:13
thingeewe know, you were in some nova session, it's alright16:13
jgriffith#start meeting cinder16:13
jgriffith#startmeeting cinder16:13
openstackMeeting started Wed Oct 24 16:13:58 2012 UTC.  The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot.16:13
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:13
openstackThe meeting name has been set to 'cinder'16:14
*** Mandell has joined #openstack-meeting16:14
jgriffithSorry for my tardiness16:14
jgriffithhave an agenda here: http://wiki.openstack.org/NovaVolumeMeetings16:14
jgriffithlet's get started16:15
jgriffith#topic Blue Prints16:15
*** openstack changes topic to "Blue Prints"16:15
jgriffithWe had some really good ideas come out of the summit16:15
jgriffithOver the course of the week I'd like to get these things transferred into blue-prints if we could16:15
jgriffithThen I can start going through and targetting against milestones16:15
winston-dsounds good16:16
jgriffithSome folks have already started (thank you) but there's a lot to add and I don't want to do it all myself :)16:16
jgriffithAll of the etherpads are accessible via http://wiki.openstack.org/Summit/Grizzly/Etherpads16:16
jgriffithSo grab your topics and start proposing if you could please!16:17
jgriffithI'd also like to see something more on island16:17
rongzehttps://github.com/freedomhui/cinder/16:17
jgriffithrongze: Excellent!  thanks16:17
rongzeisland is shared in github16:18
rongzeBut it have more work to do....16:18
*** flipfl0p has joined #openstack-meeting16:18
jgriffithWe should probably plan on spending some time picking through it with the Rax and HP folks and see what we come up with16:18
*** dcramer_ has joined #openstack-meeting16:18
jgriffithand of course anybody else that's interested, I just know there is some overlap between those groups16:19
*** danwent has joined #openstack-meeting16:19
jgriffithOk, DuncanT rnirmal if you get a chance to take a swag at your BP's that would be great16:19
jgriffithI'll hit up cthier and clayg when I see them16:19
rnirmaljgriffith: will do16:19
rnirmalthey will be a little busy this week16:20
jgriffith:)16:20
jgriffithfigured as much16:20
jgriffithI'll try to grab there's for them probably16:20
jgriffithProbably lump the API stuff all into one BP16:20
jgriffithwe'll see16:20
rnirmalwe need to decide may be next meeting... on how we are going to manage multiple api versions16:21
jgriffithAlright, any questions on the etherpad->blue-print work?16:21
DuncanTI'll find ours and see how up-to-date they are16:21
jgriffithrnirmal: yup, there's some precedence set that we can use as a guide I think though16:21
thingeernirmal: I've been looking into it. personally I like glance's approach.16:22
jgriffithDuncanT: thanks!16:22
jgriffiththingee: +116:22
rnirmalthingee: that's good.. since I didn't like the nova approach so much16:22
thingeev1 v2 directory, separate wsgi controllers and routes in each dir16:22
thingeeor v1.x....whatever you guys agree for version number :)16:23
jgriffiththingee: I'd like to model alot of the API stuff we do after Glance IMO16:23
creihtoh hai :)16:23
*** n0ano has quit IRC16:23
jgriffiththingee: That's where I started with the volume.class api stuff etc16:23
jgriffithcreiht: hola!16:23
creihtsorry... been a bit busy :)16:23
jgriffithcreiht: Just finishing up on my pleas to convert our summit etherpads to bp's16:24
creihtI hope to start going through the api stuff next week and start making bugs/blueprints16:24
jgriffithcreiht: understood... and congratulations :)16:24
creihtthanks! and yeah... been a bit busy :)16:24
*** spn_ has joined #openstack-meeting16:24
jgriffithcreiht: sounds good... some us can help as well and work off of the etherpad if you like16:24
*** gatuus has joined #openstack-meeting16:24
creihtcool16:24
thingeeI've been learning a lot in stepping through glances flow for this. I've successfully gotten requests to go to separate controllers, but I don't want to be holding back development since everyone needs this16:24
thingeeI was working on this over the summit, but haven't spent time since cause of the craziness of this month for myself.16:25
jgriffiththingee: I don't think you'd be holding anything back at all.  If you have the time to keep working on it and share your ideas (as far as the seperation etc)16:25
jgriffiththat would be great because it will probably be a week or two before we're ready to tackle the API changes16:26
jgriffitherrr... what I mean is as far as adding the *new* stuff16:26
jgriffiththingee: make sense?  Or am I incoherrent?  :)16:26
thingeecrystal clear! ok, how about we plan to have a framework of the separation of the apis to be available with v1 still intact of course.16:27
*** colinmcnamara has joined #openstack-meeting16:27
thingeewe = me and whoever wants to help!16:27
jgriffiththingee: Yup, I believe we have to provide that16:27
jgriffiththingee: and yes, I would hope we can get a couple of folks helping you on this16:28
jgriffithAlright... shall we move on to NFS?16:28
thingeev2 will also include taking out that still exception that gives 500 errors for everything. I'll be adjusting tests according to expect real helpful errors too16:28
jgriffiththingee: assumed :)16:28
thingeeor v1.x...what am I calling this thing heh16:28
jgriffiththingee: I would like to do v2 personally16:29
jgriffiththingee: Then do incrementals after Grizzly16:29
thingeesounds fine to me16:29
woodspaBefore we move on who is driving the QoS work?16:29
*** colinmcnamara1 has joined #openstack-meeting16:29
jgriffithwoodspa: I think we need to sort some more out on that16:30
jgriffithwoodspa: The general feel seemed to be that we could/should deal with that via volume_type/extra_specs16:30
jgriffithwoodspa: But not sure if we were really clear there or not?16:30
jgriffithLet's add it as a discussion point later if we have time ok?16:30
woodspasounds good16:31
jgriffithalright...16:31
jgriffith#topic NFS16:31
*** openstack changes topic to "NFS"16:31
jgriffithbswartz: Hope I wasn't too much of a PITA on this16:32
bswartzno, your concerns are totally understandable16:32
*** colinmcnamara has quit IRC16:32
jgriffithbswartz: cool16:32
bswartzby "NFS" do you mean the whole NAS thing? or the NFS drivers?16:32
jgriffithbswartz: The whole NFS proposal16:32
bswartzbecause the NAS enhancements cover both NFS and CIFS16:32
jgriffithOk.. sorry NAS16:33
bswartzalthough only crazy people use CIFS16:33
DuncanTFSaaS16:33
jgriffithBTW, that doesn't help alleviate my concerns :)16:33
jgriffithDuncanT: +116:33
* jgriffith updated the meeting page :)16:33
bswartzI realized that the link I provided in my etherpad was to the wrong branch16:33
bswartzthere 's another branch that does work in devstack16:34
jgriffithbswartz: ahh... cool16:34
bswartzand we'll be keeping it up to date and making a submission soon16:34
bswartzmy dev team is on vacation this week, unfortunately16:34
jdurgincould you add the etherpad links to the wiki?16:34
jgriffithSo my concerns are still there, but I don't want to dominate the conversation on this16:34
bswartzjgriffith: at the conference you alluded to some ideas that might make the submission less objectionable16:35
jgriffithbswartz: Yes, I'd like to see the etherpad added to the summit etherpad page and the updated github links16:35
jgriffithbswartz: Yes, but I'm still concerned about the scope and added work16:35
jgriffithbswartz: Take a look at the current bug list :(16:35
DuncanTI'd also suggest we want some input from the lustre guys trying ot do the same thing, see if the two approaches mesh16:36
jgriffithactaully... I was going to suggest:16:36
*** EmilienM has left #openstack-meeting16:36
jgriffithSending an email out to the user and dev list16:36
jgriffithI'd like to get more community input on this16:36
bswartzI'm going to get one of the developers on my team to join cinder core16:36
jgriffithAre we trying to solve a *real* problem16:36
bswartzand try to help with more things than just netapp stuff16:37
jgriffithbswartz: that would be very helpful16:37
jgriffithbswartz: Thoughts on the ML proposal?16:37
jgriffithor anybody else have thoughts on that?16:37
bswartzfwiw, a lot of people came up to me at the conference and said they our idea was a good one16:37
jgriffithbswartz: fair16:38
jgriffithso does that == "no" on the ML proposal?16:38
bswartzjgriffith: I think sending out something to the mail list would be beneficial, but I'm not sur what I would expect the happen as a result16:38
winston-di like the ML idea.16:38
bswartzI'll go ahead and do it16:38
jgriffithbswartz: thank you!16:39
*** EmilienM has joined #openstack-meeting16:39
bswartzso someone mentione lustre?16:40
*** FN-OS has joined #openstack-meeting16:40
winston-dduncan did16:40
bswartzI wasn't aware they were interested in NAS support in cinder16:40
*** rafaduran has left #openstack-meeting16:40
DuncanTThere were a bunch of lustre guys at the summiting looking at FSaaS too... I'll ping you if I can find some contact details16:40
bswartzor did I misunderstand?16:40
bswartzokay thanks16:40
DuncanTIt wasn't quite NAS but close enough that you guys should talk I think16:41
jgriffithOk, any other thoughts on FSaaS?16:41
* jgriffith thinks the name alone excludes it from BSaaS :)16:41
bswartznot from me16:41
bswartzhaha16:41
jgriffithSorry.... couldn't resist :)16:42
winston-dbswartz, do we need anything special fro celiometer for NAS?16:42
jgriffithAlrighty...16:42
bswartzwinston-d: I would expect that to come later16:42
winston-dok16:42
bswartzwinston-d: my first guess is that it would be much harder to do, unless we take advantage of hypervisor-based file-sharing technology16:42
jgriffithOk, let's move along if there are no objections16:43
winston-dsure.16:43
bswartzbut some customers will have no interest in that16:43
bswartzyes let's move on16:43
jgriffith#topic Fibre-Channel16:43
*** openstack changes topic to "Fibre-Channel"16:43
kmartinjgriffith: I'm here from HP and we have a meeting setup with the Brocade guys and us to decide if we want one blue print or two for FC. I suspect by next weeks meeting we would have one submitted16:44
jgriffithkmartin: Yay!16:44
jgriffithOne please :)16:44
jgriffithUnless they cover different aspects16:44
woodspakmartin: Did you connect with Dietmar Noll from IBM too?16:44
jgriffithkmartin: The sooner the better16:44
*** hemna has joined #openstack-meeting16:45
*** dendrobates is now known as dendro-afk16:45
kmartinyes I believe so Andre is setting up the meeting16:45
jgriffithkmartin: This is another one that I believe the scope is going to be more significant than what some initially may believe16:45
kmartinI agree16:45
jgriffithkmartin: So I'd like to get the ball rolling as soon as possible16:45
*** markmcclain has joined #openstack-meeting16:45
jgriffithkmartin: Keep in mind the implications for nova as well16:45
kmartinok...that's the plan, I believe the meeting is schedule for this friday16:46
jgriffithexcellent... keep me posted if you can16:46
kmartinwill do16:46
jgriffithkmartin: ping zykes- if you get a chance too16:47
jgriffithkmartin: He's been asking me about FC support so may have some helpful input16:47
kmartinok16:47
jgriffithalright... anything else on Fibre-Channel?16:47
*** colinmcnamara1 has quit IRC16:47
jgriffith#topic bugs16:48
*** openstack changes topic to "bugs"16:48
jgriffithhttps://bugs.launchpad.net/cinder/+bugs?orderby=status&start=016:48
kmartinwoodspa:  Dietmar is on the dist. list16:48
*** colinmcnamara has joined #openstack-meeting16:48
jgriffithI just wanted to remind folks to help keep an eye on things here16:48
jgriffithWe're in "ok" shape right now I think but I want to make sure we don't leave things sitting too long16:49
jgriffithRemember anybody can jump in there and take on a bug if they like16:49
zykes-oh16:49
woodspakmartin: not sure.  I just told him to contact you.16:49
zykes-here we are ;p16:49
jgriffithI'll try to make sure I keep on top of triage etc16:49
jgriffithzykes-: You missed it :)16:49
jgriffithzykes-: scroll up to see the conversation or check eavesdrop16:50
jgriffithkmartin: is from HP and is driving some of the effort16:50
*** colinmcnamara has quit IRC16:50
jgriffith#topic reviews16:50
*** openstack changes topic to "reviews"16:50
jgriffithAgain.. just a reminder as every week :)16:50
kmartinwoodspa: we have his contact info and he should of been notifed by Andre from Brocade, who is putting together this first meeting16:50
*** EmilienM has left #openstack-meeting16:51
jgriffithIf you have 10 minutes a day to spare just go here: https://review.openstack.org/#/q/status:open+cinder,n,z16:51
jgriffithand help out please :)16:51
*** colinmcnamara has joined #openstack-meeting16:51
woodspakmartin: perfect, thanks16:51
jgriffithEspecially my review: https://review.openstack.org/#/c/14266/16:51
jgriffith^^16:51
uvirtbotjgriffith: Error: "^" is not a valid command.16:51
jgriffithuvirtbot: whatevs16:51
uvirtbotjgriffith: Error: "whatevs" is not a valid command.16:51
thingeeheh16:52
jgriffithstupid uvirtbot16:52
jgriffithFinally... I get the last word16:52
bswartzuvirtbot: gdiaf16:52
uvirtbotbswartz: Error: "gdiaf" is not a valid command.16:52
jgriffithOk... finally16:52
jgriffith#topic core team status16:53
*** openstack changes topic to "core team status"16:53
jgriffithI don't see much reason to wipe out the core team and start over right now16:53
jgriffithWe could do some things like swap Rob and Ben16:53
*** krtaylor has quit IRC16:53
bswartzoh yes please16:53
jgriffithOr if Ben mentioned somebody else will be working on Cinder we can just wait16:53
bswartzI thought that was already done16:53
bswartzno it should be me16:54
jgriffithbswartz: No it wasn't :(16:54
jgriffithWell... then you have to do core duty stuff :)16:54
* jgriffith ropes bswartz into the muck16:54
bswartzI fully intend to16:55
jgriffithso just a reminder core means you're on IRC, you triage and fix bugs, do reviews etc etc16:55
jgriffithbswartz: excellent16:55
jgriffithIf there are no objections then I move we swap Rob with Ben?16:55
jgriffithGoing once...16:55
jgriffithGoing twice...16:55
jgriffithDone16:56
*** colinmcnamara has quit IRC16:56
jgriffithIn addition....16:56
jgriffithI'd like to formally propose a couple of new additions next week16:56
jgriffithMore to come on that, but if any of you have folks that you'd like to see nominated let me know16:56
jgriffithI'll probably put something together for next week16:57
*** danwent has quit IRC16:57
zykes-Can I have e-mails for people in the cinder team if possible to work on FC stuff ?16:57
zykes-I'm trying to pull in Dell folks as well on it16:58
jgriffithzykes-: I'll leave that to kmartin.  A PM might be a more appropriate method16:58
zykes-ok :)16:58
jgriffithelse we'll all spam kmartin to death!16:58
jgriffith:)16:58
jgriffithOh wait... that's what openstack-dev.lists does already :)16:58
jgriffithOk... two minutes left16:59
jgriffith#topic open-discussion16:59
*** openstack changes topic to "open-discussion"16:59
jgriffithanybody have anything?16:59
DuncanTYou threatened more on QoS if we had time?16:59
zykes-jgriffith: are you gonna pull in people on the compute side as well or for the FC stuff ?16:59
*** jog0 has joined #openstack-meeting16:59
jgriffithzykes-: Not yet but the folks drafting it up are aware that will be required17:00
*** lloydde has joined #openstack-meeting17:00
jgriffithDuncanT: Yup, if nobody else has anything?17:00
*** garyk has quit IRC17:00
*** clayg has joined #openstack-meeting17:00
zykes-jgriffith: who can I bug to ask about stuff there17:00
jgriffithzykes-: On nova?  Nobody yet :)17:01
jgriffithzykes-: Not sure they've been made aware of the idea yet17:01
zykes-aww ;p17:01
bswartz#openstack-nova maybe?17:01
winston-dor just ping vishy17:01
jgriffithalright... qos?17:01
claygjgriffith: i'm here, catching up on the back log17:01
jgriffithclayg: Howdy!17:01
claygyessir, been thinking alot about blueprints17:02
jgriffith:)17:02
bswartzIs "qos" really the best term to use? It's such a loaded acronym17:02
*** colinmcnamara has joined #openstack-meeting17:02
jgriffithbswartz: ?17:02
jgriffithquality of service ?17:02
jgriffithseems pretty straight forward to me17:02
bswartzI'm just saying that people think they know what QoS means -- and different people don't always agree17:03
jgriffithbswartz: ahhh... fair17:03
DuncanTAre we going to handle QoS specifically, or generic per-volume and per-volume-class attributes?17:03
jgriffithDuncanT: That's the million dollar question I think :)17:03
jgriffithDuncanT: My original intent was to actuall add a method to the API to make "special" settings to volumes17:04
DuncanTI'd prefer the later, but the former is better from a self-documenting / explorable API17:04
jgriffithDuncanT: ie "set_iops(min=x, max=y, burst=z)"17:04
jgriffithbut seemed like maybe that should be reserved to an extension17:05
*** colinmcnamara1 has joined #openstack-meeting17:05
jgriffiththen the other thing that came up was VT/ExtraSpecs17:05
*** danwent has joined #openstack-meeting17:05
clayg+1 qos core on types, with per volume qos as ext17:05
DuncanTI still don't understand extraspecs...17:05
jgriffithDuncanT: so here's an example17:05
claygextraspecs is reserved metadata on types ya?17:05
jgriffithclayg: yup17:06
jgriffithvolume_type=qos17:06
*** darraghb has quit IRC17:06
jgriffithextra_specs={min:x, max:y, burst:z, blue:whatevs}17:06
jgriffithThe downside in that it's a set and forget17:07
*** colinmcnamara has quit IRC17:07
jgriffithIt would be good to have an update handle17:07
DuncanTSo selecting a volume type tells you what per-volume metadata is valid at create?17:07
DuncanT(were per-volume metadata == the extra specs field)?17:07
jgriffithextra-specs aren't the same as volume_metadata17:07
*** colinmcnamara1 has quit IRC17:07
DuncanTYeah, I'm overloadign the term metadata, sorry17:08
*** colinmcnamara has joined #openstack-meeting17:08
jgriffithbut yes, kinda.  It's arbitrary, the admin can assign whatever they want there17:08
DuncanTPer-volume attributes17:08
jgriffithDuncanT: +117:08
winston-dattributes/properties..17:08
jgriffithSo following what clayg pointed out (I think)17:08
bswartzextra specs are additional information about the volume type that are available to the scheduler at scheduling time, and also available to the driver at create time17:08
claygcapabilities <- sorry just needed to throw that out there :P17:08
jgriffithYou get the best of both worlds17:08
winston-dbswartz, +117:09
claygbswartz: that's a great definition17:09
jgriffithYou can provide the extension to explicitily change/set it as well17:09
DuncanTTo rephrase 'extra-specs are per-volume attributes/properties. The set of valid keys is decided on a per-volumetype basis'?17:09
jgriffithbswartz: You da man!17:09
*** oubiwann has joined #openstack-meeting17:09
DuncanT(Looking at this as a user, not an implementer)17:09
*** troytoman-away is now known as troytoman17:09
jgriffithDuncanT: extra-specs wouldn't be visible to the user17:09
jgriffithDuncanT: Only the admin17:09
DuncanTAh, ok17:09
jgriffithUnless folks disagree with that?17:10
*** dendro-afk is now known as dendrobates17:10
winston-djgriffith, no, it is visible to end-user, i think.17:10
*** s0mik has joined #openstack-meeting17:10
*** hggdh has quit IRC17:10
claygjgriffith: I'm not sure that 100% nessecary, if some of the extraspec fields become common between backend impls they start to have meaning that may be relevant to an end user trying to select a type17:10
DuncanTSo basically they are just some stuff associated with a volumetpye by the admin?17:10
bswartzno, only the volume_type is visible to the end user, not the extra specs17:10
*** afazekas has quit IRC17:10
*** colinmcnamara has quit IRC17:10
claygit's not quite "RAM"  "CORES" - but things like min/max iops seem... sorta understood-ish?17:10
*** colinmcnamara has joined #openstack-meeting17:10
DuncanTIn that case I'm clear17:10
jgriffithbswartz: You and are in alignment I think17:11
claygok, i'm happy to be over-ruled on no extra specs are ever visable to the user ever17:11
jgriffithBut clayg17:11
jgriffithI'm *ok* with it being visible, just not modifiable by the user17:11
jgriffithIt's immutable for a user17:11
claygjgriffith: oh yes obviously17:11
jgriffithmutable for an admin17:11
winston-djgriffith, +1 for that17:11
claygjgriffith: totally clear, i don't really care if users can see them17:12
DuncanTI'm not sure it makes sense to the user17:12
jgriffithI point that out because I just thought my patch may be broken and not do that :(17:12
*** Gordonz has joined #openstack-meeting17:12
claygbut I think about people going to GOLD type at provider a to FAST type at provider b17:12
*** Gordonz has quit IRC17:12
bswartzthe danger with having it visible to the user is that the admin may want to modify the extra_specs for a volume type after some volumes have already been created, and such changes will not be retroactive17:12
winston-dsince volume_type is nothing but a name, expose extra_specs to end user can make things clear17:12
claygmaybe not of it means anything until you benchmark17:12
jgriffithOk... I move to have it be admin visible only to start17:12
jgriffithwe can change it over the next couple of weeks if we think of good reason?17:12
claygyeah, makes good sense17:13
*** Gordonz has joined #openstack-meeting17:13
*** kindaopsdevy has joined #openstack-meeting17:13
jgriffithwinston-d: But you may not want them to see that17:13
jdurginjgriffith: sounds good to me17:13
*** kindaopsdevy has left #openstack-meeting17:13
DuncanTBut the extra_specs is going to be full of back-end specific things17:13
jgriffithwinston-d: For example they select GOLD17:13
jgriffithIf they aren't using it, an admin can redefine what GOLD is :)17:13
jgriffithsneaky optimization/efficiencey tricks17:13
jgriffithLong explanation but there's some use cases that make having that hidden handy from an admins perspective17:14
*** cp16net is now known as cp16net|away17:14
jgriffithDuncanT: correct17:14
DuncanTMy vote is leaning heavily to not showing it to non-admin17:14
jgriffithDuncanT: +117:14
DuncanTThough one of the horizon guys suggested we might want to add a (free text) description field to each type17:14
woodspaDuncanT: +117:14
bswartzthere may also be value in have a "description" field for volume types that allows admins to write a fluffy description of what the volume type is -- that text could be displayed in horizon, for example.17:14
DuncanTbswartz: +1 ;-)17:15
*** cdub_ has joined #openstack-meeting17:15
*** adjohn has joined #openstack-meeting17:15
claygyeah, type description +117:16
winston-dmy concern is volume_type is just a _name_, at RAX, GOLD means SSD backed volume, but maybe somewhere else, GOLD means something bad, that's confusing. there should be some way to avoid such confusion.17:16
bswartzwinston-d: how about the description field, would that address your issue?17:16
*** hggdh has joined #openstack-meeting17:16
winston-dtype description is OK, i guess. at least it has potential to solve the problem i mentioned.17:17
bswartzput it to a vote!17:18
claygI think some extra_specs just won't be reasonable to expose to end user, so if even if we say we want to expose them directly, we'd have to solve "hiding" some... it just gets message - description seems like the easiest thing, I retract all previous comments about having extra_specs exposed :P17:18
clayg*exposed to user - types-manage ext has to expose them ;P17:18
claygs/message/messy17:18
claygwow17:18
jdurginI think a lot of extra_specs will end up being backend-dependent anyway, and even common ones won't necessarily be meaningful to a user's workload17:19
* clayg thinks jgriffith is looking up how to do voting :D17:19
jgriffithsorry17:19
jgriffithphone call17:19
DuncanTname & description only +117:19
claygname & description only +117:19
jgriffithSo I'm not going to put it to a vote17:19
woodspaDuncanT +117:19
jgriffithI'm going to make an exec decision :)17:20
claygPTL'IN LIKE A BOSS17:20
winston-dyeah, that makes sense. i'm fine with not exposing extra_specs to enduser, and +1 for description.17:20
jgriffith:)17:20
jgriffithit looks like everybody agrees anyway17:20
* clayg snickers - *this time*17:20
jgriffithextra_specs not exposed to end udser17:20
rongzename & description only +117:20
jgriffithclayg: if they didn't I'd do a vote... I'd just rig the results :)17:20
jgriffithAlright, let's go with that17:21
jgriffithif something scary comes up we can revisit :)17:21
jgriffithSo....17:21
jgriffithI think we go with clayg s recommendation17:21
jgriffithtype/extra-spec for quality settings17:21
claygwhay, wut?  I have only _bad_ ideas17:21
*** henrynash has quit IRC17:21
jgriffithand also provide an extension for direct access by and admin17:21
*** troytoman is now known as troytoman-away17:21
jgriffithclayg: :)17:21
DuncanTSo are we punting per-volume settings for now?17:22
claygi don't think that was my idea, but it sounds good17:22
kmartinis there a blue print for the volume type and extra specs?17:22
jgriffithclayg: I think that's what you said?17:22
jgriffithDoh17:22
*** jakedahn_zz is now known as jakedahn17:22
winston-dkmartin, volume type & extra specs are already there.17:22
jgriffithkmartin: Nope, it's something that's always been there17:22
claygyeah, i said that, but I thought I was rephrasing you :D17:22
jgriffithkmartin: just never used17:22
winston-dkmartin, just hasn't been utilized yet.17:22
kmartinok that's what I thought17:22
* jgriffith twists clayg 's statements around to his advantage17:23
jgriffithHow about I write it up and post it and you guys can all puke on it if you like :)17:23
jgriffithI'll put a wiki together before the next meeting?17:23
DuncanTSounds like a plan17:24
jgriffithcool17:24
jgriffithAlright, we're way over... and that silly sales guy is going to call me back17:24
jgriffithso I better get some coffeee beforehand :)17:24
jgriffithAs always you can catch me on IRC any time17:24
jgriffithAnd THANKS!!!17:24
*** colinmcnamara has quit IRC17:24
jgriffithI thought the summit went really well and think we've made great progress with Cinder!17:25
jgriffithOk... anything real quick before I cut this off!17:25
jgriffith#endmeeting cinder17:25
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"17:25
openstackMeeting ended Wed Oct 24 17:25:40 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:25
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2012/cinder.2012-10-24-16.13.html17:25
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2012/cinder.2012-10-24-16.13.txt17:25
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2012/cinder.2012-10-24-16.13.log.html17:25
*** bswartz has left #openstack-meeting17:26
*** thingee has left #openstack-meeting17:28
*** dendrobates is now known as dendro-afk17:31
*** colinmcnamara has joined #openstack-meeting17:31
*** nati_ueno has joined #openstack-meeting17:34
*** colinmcnamara has quit IRC17:34
*** colinmcnamara has joined #openstack-meeting17:35
*** nati_uen_ has joined #openstack-meeting17:36
*** krtaylor has joined #openstack-meeting17:37
*** nati_ueno has quit IRC17:40
*** AlanClark has joined #openstack-meeting17:42
*** dcramer__ has joined #openstack-meeting17:44
*** colinmcnamara has quit IRC17:44
*** dcramer_ has quit IRC17:46
*** littleidea has quit IRC17:46
*** woodspa has quit IRC17:47
*** troytoman-away is now known as troytoman17:51
*** afazekas has joined #openstack-meeting17:52
*** troytoman is now known as troytoman-away17:52
*** mnewby has joined #openstack-meeting17:53
*** gyee has joined #openstack-meeting17:54
*** lloydde has quit IRC17:56
*** cp16net|away is now known as cp16net17:56
*** mnewby has quit IRC17:57
*** mnewby has joined #openstack-meeting17:57
*** troytoman-away is now known as troytoman18:01
*** gyee has quit IRC18:01
*** garyk has joined #openstack-meeting18:06
hemnaany documentation on the volume types stuff?18:09
russellbhemna: should probably try #openstack for that.18:10
* hemna nods18:10
*** danwent has quit IRC18:11
*** gyee has joined #openstack-meeting18:12
*** gyee has quit IRC18:13
*** gatuus has quit IRC18:18
*** danwent has joined #openstack-meeting18:19
*** rongze has quit IRC18:19
*** danwent has quit IRC18:20
*** danwent has joined #openstack-meeting18:25
*** NaZZaX has joined #openstack-meeting18:29
*** FN-OS has quit IRC18:30
*** primeministerp has joined #openstack-meeting18:30
*** roampune has joined #openstack-meeting18:33
*** troytoman is now known as troytoman-away18:33
*** roampune has left #openstack-meeting18:33
*** colinmcnamara has joined #openstack-meeting18:40
*** notmyname has quit IRC18:41
*** salv-orlando has quit IRC18:41
*** notmyname has joined #openstack-meeting18:42
*** gallth is now known as tgall_foo18:45
*** tgall_foo has quit IRC18:45
*** tgall_foo has joined #openstack-meeting18:45
*** henrynash has joined #openstack-meeting18:45
*** woodspa has joined #openstack-meeting18:49
*** sandywalsh_ has joined #openstack-meeting18:54
*** sandywalsh has quit IRC18:54
*** gatuus has joined #openstack-meeting18:55
*** arbrandes has quit IRC19:00
*** woodspa has quit IRC19:00
*** stevebake has quit IRC19:00
*** stevebake has joined #openstack-meeting19:01
*** patelna has joined #openstack-meeting19:05
*** lloydde has joined #openstack-meeting19:07
*** Ravikumar_hp has joined #openstack-meeting19:09
*** s0mik has quit IRC19:09
*** lloydde has quit IRC19:11
*** dolphm has quit IRC19:13
*** cdub_ has quit IRC19:16
*** Razique has joined #openstack-meeting19:26
*** adjohn has quit IRC19:27
*** littleidea has joined #openstack-meeting19:29
*** EmilienM_ has joined #openstack-meeting19:30
*** danwent has quit IRC19:41
*** ayoung has quit IRC19:44
*** salv-orlando has joined #openstack-meeting19:45
*** kindaopsdevy has joined #openstack-meeting19:49
*** gyee has joined #openstack-meeting19:51
*** joesavak has joined #openstack-meeting19:52
*** jsavak has quit IRC19:54
*** salv-orlando has quit IRC19:54
*** salv-orlando_ has joined #openstack-meeting19:55
*** Ravikumar_hp has quit IRC20:03
*** anniec has joined #openstack-meeting20:06
*** maurosr has quit IRC20:08
*** stevebake has quit IRC20:09
*** troytoman-away is now known as troytoman20:11
*** troytoman is now known as troytoman-away20:13
*** dendro-afk is now known as dendrobates20:15
*** stevebake has joined #openstack-meeting20:20
*** dolphm has joined #openstack-meeting20:24
*** s0mik has joined #openstack-meeting20:26
*** EmilienM_ has left #openstack-meeting20:26
*** dolphm has quit IRC20:28
*** jhenner has joined #openstack-meeting20:31
*** colinmcnamara has quit IRC20:32
*** lloydde has joined #openstack-meeting20:35
*** adjohn has joined #openstack-meeting20:36
*** littleidea has quit IRC20:37
*** littleidea has joined #openstack-meeting20:38
*** dendrobates is now known as dendro-afk20:38
*** dendro-afk is now known as dendrobates20:38
*** cdub_ has joined #openstack-meeting20:40
*** danwent has joined #openstack-meeting20:40
*** jbrogan has quit IRC20:44
*** jog0 is now known as jogo020:47
*** eglynn_ has joined #openstack-meeting20:49
*** jogo0 has quit IRC20:49
*** jogo0 has joined #openstack-meeting20:49
*** jogo0 is now known as Guest1081920:49
*** dprince has quit IRC20:50
*** anniec has quit IRC20:50
*** anniec_ has joined #openstack-meeting20:50
*** Guest10819 has quit IRC20:50
*** anniec_ has quit IRC20:51
*** anniec has joined #openstack-meeting20:52
*** jog0 has joined #openstack-meeting20:52
*** jog0 has joined #openstack-meeting20:53
*** jog0 has quit IRC20:53
*** jog0 has joined #openstack-meeting20:54
*** jog0 has quit IRC20:54
*** jog0 has joined #openstack-meeting20:54
*** AlanClark has quit IRC20:55
*** aclark_ has joined #openstack-meeting20:55
*** jog0 has quit IRC20:56
*** DanD_ has joined #openstack-meeting20:56
*** jog0 has joined #openstack-meeting20:57
*** jog0 is now known as jogo20:58
*** jogo has quit IRC20:59
*** colinmcnamara has joined #openstack-meeting20:59
*** eglynn 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 Oct 24 21:00:07 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
dhellmann-afko/21:00
eglynno/21:00
asalkeldhi21:01
*** dhellmann-afk is now known as dhellmann21:01
*** jogo_ has joined #openstack-meeting21:01
nijabaok, let's start21:01
nijaba#topic actions from previous meeting21:01
nijaba--> skipping that topic as all action were completed prior to release21:01
*** openstack changes topic to "actions from previous meeting (Meeting topic: Ceilometer)"21:01
nijaba#topic Ceilometer is now an incubated project21:01
*** openstack changes topic to "Ceilometer is now an incubated project (Meeting topic: Ceilometer)"21:01
eglynnw00t!21:01
*** jogo_ has quit IRC21:01
nijabaCongratulations to all of us, Ceilometer was accepted as an incubated project at the first official TC meeting last night.  That's really a great news, but with incubation also comes new responsabilities: we need to adhere to milestone release, and at the latest the Grizzly-3 milestone.21:01
asalkeldwell done21:01
*** nachi has joined #openstack-meeting21:01
nijaba#link http://wiki.openstack.org/GrizzlyReleaseSchedule21:01
nijabaAs you can see, that's Feb 27th, or 3.5 month away.  Better get organized soon and define our priorities right...21:02
*** colinmcnamara has quit IRC21:02
*** jogo_ has joined #openstack-meeting21:02
*** jogo_ is now known as jog021:02
dhellmannI made a list of some suggested items at the bottom of http://wiki.openstack.org/EfficientMetering/RoadMap based on what I remembered from the summit21:02
dhellmannI'm sure there are more items to add to the list21:02
*** jog0 is now known as Guest8090621:02
nijabadhellmann: I was about to suggest, in the next topic, to have one volunteer per session to scrub the notes and add bugs and items to the roadmap21:03
*** colinmcnamara has joined #openstack-meeting21:03
*** jtran has joined #openstack-meeting21:03
nijabawould that make sense?21:03
dhellmannsure21:03
asalkeldyip21:03
*** colinmcnamara has quit IRC21:03
nijabawe could then work on prioritization during the next meeting21:04
dhellmannthat sounds like a good idea21:04
eglynnsounds like a plan21:04
*** Guest80906 has quit IRC21:04
dhellmannshould we set up an etherpad for drafting, and then move it to the wiki when we're happy?21:04
*** metral_ has joined #openstack-meeting21:05
nijabadhellmann: that could work nicely, indeed21:05
dhellmannok, I'll set that up, starting with a copy of the wiki page21:05
nijaba#link https://etherpad.openstack.org/grizzly-ceilometer-actions21:05
*** Razique has quit IRC21:05
nijaba#agreed use https://etherpad.openstack.org/grizzly-ceilometer-actions to capture actions from the summit sessions21:06
*** metral has quit IRC21:06
*** metral__ has joined #openstack-meeting21:06
*** markmcclain has quit IRC21:06
nijabaso, we had 4 sessions21:06
*** bo-2 has joined #openstack-meeting21:07
nijaba#link http://etherpad.openstack.org/grizzly-ceilometer-state-of-metering21:07
nijaba#link http://etherpad.openstack.org/grizzly-ceilometer-customizing21:07
nijaba#link http://etherpad.openstack.org/grizzly-ceilometer-beyond-metering21:07
nijaba#http://etherpad.openstack.org/ceilometer-design21:07
*** bo-2 has quit IRC21:07
nijaba#link http://etherpad.openstack.org/ceilometer-design21:07
*** bob__ has joined #openstack-meeting21:07
nijabawho wants to cover which?21:07
nijabaplease feel free to #action yourself21:07
krtaylorhi everybody, sorry joining late21:08
dhellmann#action dhellmann review state-of-metering notes for roadmap items21:08
DanD_I am on as well21:09
*** henrynash has quit IRC21:09
*** metral_ has quit IRC21:09
jd__hi21:09
eglynn#action eglynn distill roadmap items from ceilometer-design21:09
asalkeldI am looking at "plugins for places to send counters from agents"21:09
nijaba#action nijaba scrubs http://etherpad.openstack.org/grizzly-ceilometer-customizing21:09
*** mtreinish has quit IRC21:10
dhellmannasalkeld: I saw that you posted a link to a repo on github this morning, but haven't had a chance to look at the code yet21:10
asalkeldyea just a sand pit to plan in21:11
nijabaanyone wants to scrub grizzly-ceilometer-beyond-metering?21:11
*** lifeless has quit IRC21:11
asalkeldthat will probably be me21:11
jd__nijaba: anything21:11
nijabafirst to use #action wins ;)21:12
*** joesavak has quit IRC21:12
jd__#action jd__ scrub grizzly-ceilometer-beyond-metering21:12
nijabanice21:12
dhellmannasalkeld: jd__ , nijaba, and I discussed a slight change to the Counter class in https://bugs.launchpad.net/ceilometer/+bug/1070857 earlier today21:13
uvirtbotLaunchpad bug 1070857 in ceilometer "set default source to something meaningful" [Low,Triaged]21:13
nijaba#action everyone should feel free to complete our reviews of action on https://etherpad.openstack.org/grizzly-ceilometer-actions21:13
DanD_I would volunteer but with my tenuous grasp on where things are at I would probably cause more damage than good21:13
asalkeldso what was the intension of source21:13
nijabaasalkeld: to capture where the identity can be resolved21:14
eglynnasalkeld identify the orgin21:14
dhellmannnijaba: should we get someone to go through https://etherpad.openstack.org/grizzly-ceilometer-actions to mark completed items done (or just remove them)?21:14
nijabadhellmann: +121:14
eglynns/orgin/origin/21:14
asalkeldso like the project name?21:14
asalkeldvolume/compute21:14
eglynnI would think more like metering versus metrics etc.21:15
dhellmannasalkeld: nijaba suggested the keystone endpoint or similar *specific* place to look for project/account info21:15
nijabaasalkeld: I was thinking of the keystone API url21:15
dhellmannI like the idea of something shorter, though21:15
nijabaasalkeld: or something else21:15
asalkeldok21:15
dhellmannmaybe we could have a registry of short names to more details21:15
dhellmannthis obviously needs more thought :-)21:15
jd__but as I pointed out, a keystone proposing several isolated regions does not help as a source21:15
asalkeldso cloudwatch has NameSpace21:15
nijabathe idea being that other project running on top of openstack could use another identity provider21:15
asalkeldwe could have OS/cinder21:16
*** jhenner has quit IRC21:16
asalkeldor user data could have21:16
nijabaactually, anything that uses keystone as an IDP should have the same source21:16
asalkelduser/user_id21:16
*** jhenner has joined #openstack-meeting21:16
nijabaactually, anything that uses *THE SAME* keystone as an IDP should have the same source21:17
jd__nijaba: even if for examplesinstances are from different nova? how do you know which nova the resource id is tied to?21:17
dhellmannso source is tied to the user_id/project_id fields, not the meter name, volume, or resource?21:17
eglynnasalkeld: the other option would just re-use the AWS namespaces21:17
eglynn(given that say the nova EC2 largely apes the EC2 naming schemes)21:17
nijababut if one uses ceilometer to meter, let's say openshift, which could use another IDP, then the source  should be different21:17
nijabadhellmann: yes21:18
dhellmannnijaba: ok, that makes sense. so we may need to add something to handle the idea of "namespace" in AWS/CW21:18
asalkeldnijaba, then this is really trusted/not-trusted?21:18
jd__but why the IDP?21:19
nijabaasalkeld: no, just a way to have ceilometer be extended to other projects outside of openstack without risking collisions21:19
*** asalkeld has quit IRC21:19
*** asalkeld has joined #openstack-meeting21:19
dhellmannso instead of "source" we probably should have called that field "id_source"21:19
nijabadhellmann: that would work21:20
dhellmannjd__: what is "IDP"?21:20
jd__dhellmann: keystone21:20
jd__identity provider21:20
nijabaif you guys think that I am not smoking crack with this, that is21:20
dhellmannjd__: thanks21:20
asalkelddhellmann, we could just make a long name "os.cinder.<name>"21:20
jd__well, I don't think keystone is the best choice here because you can only link user and project id on this21:21
jd__if you use something unique among a region for example, you can link to the right nova cluster, and to the right keystone21:21
dhellmannasalkeld: that works. We're doing something like that for our router stuff "akanda.bandwidth.in.bytes"21:21
jd__which is far better for tracability21:21
asalkeldjust requires consistency21:21
nijabajd__: I am very open.  I just want to avoid future collisions21:22
dhellmannjd__: I don't like the idea of embedding the URL in the meter, but having a reference to something that the API knows about makes sense21:22
jd__nijaba: that, I agree :)21:22
jd__dhellmann: which API?21:22
nijabauser: aaa might be a very different person for project a and b21:22
dhellmannthe ceilometer api21:22
dhellmannso we would register sources with a name, URL, and maybe other metadata then the counters would just have the short name in them21:22
dhellmannthat21:22
dhellmann wa21:22
dhellmannthat way if the url changes, the old meter data is still valid21:23
jd__dhellmann: that I'd prefer21:23
nijabadhellmann: +121:23
jd__dhellmann: you want to be able to export metadata from a source IIUC?21:23
jd__s/form/for/21:23
jd__(via a configuration file or something)21:23
*** mtreinish has joined #openstack-meeting21:23
dhellmannI think the use case is that a client of the ceilometer API needs to be able to map the user/project for a meter to a user/project in another system21:24
dhellmannfor the DUDE we are doing that using our own database, updated when a DreamCompute user is created21:24
jd__+ resource ID21:24
*** mtreinish has quit IRC21:24
dhellmannif we start using ceilometer to meter DreamObjects, which has its own account info already, we would say the source is "DreamObjects" and stick a URL there to look up the project_id to get a DH account id (like we have for DreamCompute)21:25
nijabadhellmann: exactly!21:25
jd__dhellmann: ok, makes sense to me21:25
dhellmannthat way ceilometer doesn't have to care about who owns what, but clients can always look at a resource owner and work back to the account that should be charged21:25
jd__dhellmann: I just don't want to have only the link to the IDP in the source, we need an indirection level21:25
*** mtreinish has joined #openstack-meeting21:25
*** mtreinish has quit IRC21:25
* dhellmann *finally* understands this after talking to nijaba about it 1/2 dozen times21:25
jd__better late than never :)21:26
dhellmannjd__: exactly21:26
* nijaba feel sorry for not expressing this better21:26
jd__ok, so I'll propose I'll update the bug and will try to implement that21:26
eglynnis it fragile to embed a (presumably mutable) URL in the meter?21:26
eglynnwhy not just a region identifier (and find the actual URL is say config)?21:26
*** tgall_foo has quit IRC21:26
jtraneglynn:  +121:27
nijabaeglynn: this what dhellmann and jd__ are now proposing21:27
jd__eglynn: that's sort of what we're talking about, but at larger scale21:27
*** mtreinish has joined #openstack-meeting21:27
dhellmanneglynn: yes, the idea now is to let ceilometer (optionally) register a source "name" and "details" of some sort (to be worked out later)21:27
dhellmann21:27
dhellmanne me21:27
dhellmanner 21:27
dhellmannou21:27
jd__eglynn: region is openstack specific, dhellmann wants to use it for non-openstack projects :)21:27
dhellmannthe meter would include just the name21:27
DanD_by config you mean in the database or something seperate?21:27
eglynna-ha, gotcha21:27
jd__DanD_: yup21:27
dhellmannDanD_: I was thinking the db, but we could just as easily use a simple config file for this21:27
dhellmannin fact, for the first version, maybe that's all we need21:28
DanD_that aligns well with a email I just sent to the mailing list concerning the need for additional meta data in the data model21:28
* dhellmann took a sick day today and hasn't kept up with email21:28
DanD_dhellman: basically what we discussed at the summit21:28
jd__didn't had a chance to read it neither yet21:28
nijabaso I guess the action on this is for jd__ to propose an implementation and wait for our comments?21:29
* nijaba neither21:29
jd__agreed21:29
dhellmann+121:29
eglynnDanD_ old or new dev list?21:29
nijaba#action  jd__ to propose an implementation for source and wait for our comments21:29
jd__eglynn: just saw on old I think21:29
eglynnk21:29
nijabaconfirmed21:30
DanD_probably the old one21:30
nijabasent 20 min ago21:30
eglynncool, I see it now21:30
* eglynn wishes we just had one list ...21:30
eglynn(old one is v. slow ...)21:30
dhellmannthe state-of session didn't generate a lot of action items for grizzly, so I've added them to https://etherpad.openstack.org/grizzly-ceilometer-actions21:31
*** markvoelker has quit IRC21:31
nijabaok. so now that we are a bit more organized to prepare our prios for next week, should we change topic, or are we missing anything on that subject?21:33
dhellmann+121:34
*** mtreinish has quit IRC21:34
nijaba#topic Change of project scope21:34
nijabaAs you may know, we agreed during the summit to change the project scope to "The project aims to become the infrastructure for all measurements within OpenStack. "21:34
*** openstack changes topic to "Change of project scope (Meeting topic: Ceilometer)"21:34
nijabait seems that one of the remark we got from the TC, was that this maybe a little too broad21:35
eglynnnijaba: weak push-back on that from the TC yesterday?21:35
dhellmannperhaps we did not clearly differentiate between collecting the data and analyzing it?21:36
nijabadhellmann: I think that is a very good point21:36
dhellmannfor example, one goal is to eliminate duplicate agents collecting the same data21:36
asalkeldmonitoring and metering?21:36
nijabayes21:36
dhellmannwhen I talked to Vish about collecting info for the scheduler, I pointed out that we might just send the data from our agent to something else to hold on to it and let the scheduler ask questions, since our API wasn't really organized to answer the question the scheduler has21:37
*** anniec has quit IRC21:37
dhellmannhowever, that same information could be useful for general health monitoring21:37
dhellmannso if the agent sent it in a generic way, it could be consumed by other apps21:37
jd__can't we also enhance the API to satisfy the scheduler?21:38
jd__if that's not too complicated21:38
eglynnso there's always the presumtion that users are free to their own off-line analytics over the caputured data, no suggestion tha ceilo is prescriptive about that, right?21:38
dhellmannjd__: sure, that's possible, I don't know what sorts of questions it asks or how we could frame them21:38
jd__I dont't think we ever wanted to block anybody doing anything21:38
nijabaso proposing "The project aims to become the infrastructure to collect all measurements within OpenStack so that no two agent would need to written to collect the same data.  It's primary targets are monitoring and metering, but the framework should be easily expandable to collect for other needs."21:39
jd__dhellmann: me neither (:21:39
*** aclark_ has quit IRC21:39
dhellmanneglynn: it has always been my goal to make any piece of ceilometer swappable/replacable/optional21:39
dhellmannnijaba: I like that wording.21:39
jd__do we talk about storage too? I mean ceilometer collect, and stores also21:40
dhellmannnijaba: we could say something explicit about sharing collected data with a variety of consumers21:40
jtrandoes that mean there will still be a "heat", and a "stachtach" , etc, but they would simply be the analytical tools only and then would rely on ceilometer for the measurements?21:40
eglynnlike the wording, though maybe the 'all' in 'all measurements' is a tad exclusive?21:40
jd__jtran: I think that's the plan indeed21:40
jtranwhew21:40
jtranit'd be ugly otherwise , imo21:40
asalkeldI am ok with that21:41
jd__ok, not sure what 'wheh' meant :]21:41
jd__s/h/w/21:41
jtranwhew, like as in a relief21:41
dhellmannjtran: yes, although some of what tach reports requires instrumenting beyond an agent21:41
nijabaso proposing "The project aims to become the infrastructure to collect measurements within OpenStack so that no two agent would need to be written to collect the same data. It's primary targets are monitoring and metering, but the framework should be easily expandable to collect for other needs. To that effect, ceilometer should be able to shar collected data with a variety of consumers"21:42
asalkelddhellmann, well the instrumentation code can go in oslo21:42
eglynnhow about something slightly softer, e.g. '... the primary infrastructure for collecting measurements ...'21:42
dhellmannasalkeld: that would make sense21:42
eglynnactually cool, dropping the 'all' is sufficient21:42
dhellmannnijaba: "no two agent" -> "no two agents"21:42
dhellmann"shar" -> "share"21:42
dhellmannotherwise, +121:43
jtranone of my coworkers asked, well what's the diff between 2+ agents, since having an agent other than standard nova-compute is already "having 2 agents"21:43
nijabanew try: "The project aims to become the infrastructure to collect measurements within OpenStack so that no two agents would need to be written to collect the same data. It's primary targets are monitoring and metering, but the framework should be easily expandable to collect for other needs. To that effect, ceilometer should be able to share collected data with a variety of consumers"21:43
*** asalkeld has quit IRC21:43
nijabashall we vote?21:44
*** asalkeld has joined #openstack-meeting21:44
jd__+121:44
asalkeldgrr, keep pushing "ctrl-r" == disconnect21:44
eglynnjtran: idea would be to avoid say 2 separate agents polling the hypervisor on the cimpute node21:44
jtran+121:44
eglynn+121:44
nijaba#vote agree on new project objective statemment? yes, no, abstain21:44
nijaba#startvote agree on new project objective statemment? yes, no, abstain21:44
openstackBegin voting on: agree on new project objective statemment? Valid vote options are yes, no, abstain.21:44
openstackVote using '#vote OPTION'. Only your last vote counts.21:44
nijaba#vote yes21:44
eglynnyes21:44
jd__#vote yes21:44
asalkeld#vote yes21:45
dhellmann#vote yes21:45
jtraneglynn:  agreed but i think what he was getting at is that ideally if ceilometer was in incubation and instead core, it would make sense to not have any +1 agents and instead to fold it into nova-compute21:45
eglynn#vote yes21:45
DanD_#vote yes21:45
eglynnjtran: gotcha21:45
nijabawaiting 30s21:45
asalkeldbbl : I have to take kids to school21:45
jd__jtran: we all hope this time will come :-)21:45
krtaylor#vote yes21:45
eglynnjtran: I suspect over time it will evolve in that direction anyway21:45
eglynnjtran: yep, what you said ;)21:46
nijaba#endvote21:46
openstackVoted on "agree on new project objective statemment?" Results are21:46
openstackyes (7): krtaylor, DanD_, jd__, nijaba, eglynn, asalkeld, dhellmann21:46
nijabacool21:46
jd__isn't it21:46
nijabaok, last topic21:46
nijaba#topic open discussion21:46
*** openstack changes topic to "open discussion (Meeting topic: Ceilometer)"21:46
nijaba#action nijaba to update project objective on relevant pages21:47
jtrani meant to vote yes on the above, my bad.21:47
*** tongli has quit IRC21:47
nijabajtran: np21:47
jd__anything?21:48
jtranyes, one sec21:48
jd__ah :)21:48
jtranwhen are the new meeting times?21:48
jd__I think we're back on the double schedule21:49
nijabajtran: http://wiki.openstack.org/Meetings/MeteringAgenda21:49
jtranok thx21:49
nijabajd__: yes, as asalkeld is back from vacation21:49
*** henrynash has joined #openstack-meeting21:49
jd__I'm glad summer time ends21:50
eglynnjd__ I hear ya ;)21:50
krtaylorhas the tasks on https://etherpad.openstack.org/ceilometer-design from summit been discussed?21:50
eglynnkrtaylor: I was going to distill into roadmap items21:50
eglynndo you have input?21:50
nijabakrtaylor: not yet, we will do this during the next meeting21:50
mordredhey guys - we should coordinate a gerrit namespace change for you at some point, yeah?21:51
*** dcramer__ has quit IRC21:51
dhellmannhi, mordred, yeah it seems like doing that sooner rather than later would be a good idea21:51
nijabamordred: to specify "incubated"?21:51
dhellmannwe get to move from "stackforge" to "openstack" right?21:51
eglynnyep joining the big boy's club :)21:52
eglynnprobably should do that sooner rather than later, to underscore the change in project status21:52
dhellmannmordred: what do you need from us for that? just hold off on committing for a period of time?21:53
jd__do we need to approve what's in the queue now before?21:53
dhellmannwhile we wait, another topic: As one outcome of the WSGI session at ODS I was supposed to build a "real" API server using the tools I proposed. I would like to use the ceilometer API server as the first example. The new tools have better Python 3 support and would give us XML output "for free". Does anyone object in principle to moving away from Flask to Pecan and WSME?21:55
nijabamordred seems to have let us hanging?  Who feels like chasing him later today?21:55
nijabadhellmann: no opposition from me21:56
eglynndhellmann: have at it!21:56
dhellmannI will, of course, put the code up for review21:56
jd__dhellmann: sounds good21:56
mordredsorry21:56
mordredand yes - from stackforge to openstack21:56
mordredshall we try to do that this week?21:57
nijabamordred: do we need to clear the review queue?21:57
jd__I think so21:57
jtrandhellmann:  if we use flask, and nobody else in openstack core are using it, wouldn't that create an issue if and when we get out of incubation to core?21:57
eglynndhellmann: it would be great to have that proven out before we start craft any new services (e.g. a CW-api, if needed)21:57
mordred(also, I prefer anything with better python3 support)21:57
dhellmannwhat do you need from us to make it go smoothly?21:57
mordrednijaba: I do not believe so - I believe we can do a project rename ...21:57
dhellmannjtran: moving *away* from flask to the tools I proposed for new api development21:57
mordredbut it's going to be mildly wonky from the perspective of the devs21:57
nijabamordred: then I think it really is whenever you feel like it then, the sooner the better21:57
mordredbecause the upstream remote will change21:57
mordredcool21:57
jtranwhoops yes, i meant pecan, if nobody else using it..21:58
dhellmannjtran: so this is the proof-of-concept work (and we're already using tools no one else is using)21:58
jd__mordred: not a big problem :)21:58
mordredI have several project create things with gerrit I need to do this week, I'll try to batch them up and get them all done21:58
jd__mordred: thanks, ping us if you need anything21:58
mordredwho is the best person to ping when I'm ready to roll?21:58
jtrandhellmann: from that summit session it didn't sound like the other guys were too enthused about moving away from their custom wsgi21:58
jtranbut i'm all for pecan otherwise21:58
jd__mordred: me or dhellmann or nijaba21:58
mordredjd__: awesome21:58
jd__mordred: we're on #openstack-metering21:59
nijabamordred: agree with jd__ suggestion21:59
dhellmann+121:59
*** lloydde has quit IRC21:59
*** ayoung has joined #openstack-meeting22:00
nijabanot sure if there is another meeting afterward, but we are out of official time22:00
dhellmannjtran: they want proof that something different will make a difference. there were some other sessions on validation and serialization where the idea was met a little more warmly22:00
jtranthat makes sense22:00
jtranthat's right you now reminded me, that 'test case' they wanted for api on nova 'create' instance.22:00
dhellmannjtran: right, but I want to work on something I'm familiar with first :-)22:01
jd__so we provide first case for incubation/core, and soon first case for wsgi replacement22:01
dhellmannnijaba: do we need to wrap up?22:01
dhellmannj22:01
dhellmannd22:01
jtrangood move.  the contrib exts for the nova api is scaaaary22:01
dhellmannjd__: and for subscribing to notifications22:01
jd__dhellmann: yeah :)22:01
dhellmannjtran: I might want to pick your brain on those, if you have experience with them.22:01
jd__this sounds scary22:02
jtrandhellmann: sure , any way i can help .  i have worked on them before.22:02
dhellmannjtran: when I get there, I'll ping you22:02
dhellmannjd__: ?22:02
jd__dhellmann: brain picking22:02
dhellmannjd__: halloween is coming up soon22:02
nijabadhellmann: no one is complaining22:02
jd__haha22:02
*** afazekas has quit IRC22:02
dhellmannnijaba: ok, good22:03
dhellmannnijaba: so to make sure I'm ready, next week we will try to set priorities and a schedule?22:03
* nijaba seems to be experiencing a 60s lag22:04
nijabadhellmann: yes, that's the idea, but that should not prevent us to start working on real stuff too22:04
*** ywu_ has joined #openstack-meeting22:04
dhellmannnijaba: yep22:04
*** jog0 has joined #openstack-meeting22:05
*** jog0 is now known as jogo022:05
nijabaand if eglynn (or anyone else) want to propose a design for the new agents, he's welcome to propose that as a topic for next week22:05
*** jogo0 has joined #openstack-meeting22:06
eglynnnijaba: cool, will aim to have something for then (with asalkeld)22:07
nijabagreat22:07
nijabalooks like we ran out of topic for today?22:07
nijabaending the meeting in 30s if no one objects22:08
nijaba#endmeeting22:08
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:08
openstackMeeting ended Wed Oct 24 22:08:46 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:08
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-10-24-21.00.html22:08
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-10-24-21.00.txt22:08
openstackLog:            http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-10-24-21.00.log.html22:08
jd__thanks guys22:08
nijabaThanks everyone, great meeting, as always!22:09
dhellmannthanks everyone!22:09
eglynn'night all22:09
*** eglynn is now known as sleepy-eglynn22:09
*** littleidea has quit IRC22:10
*** littleidea has joined #openstack-meeting22:11
*** littleidea has left #openstack-meeting22:12
*** jtran has left #openstack-meeting22:12
*** krtaylor has quit IRC22:13
*** kindaopsdevy has quit IRC22:15
*** somik has joined #openstack-meeting22:17
*** DanD_ has quit IRC22:18
*** s0mik has quit IRC22:18
*** somik is now known as s0mik22:18
*** dhellmann is now known as dhellmann-afk22:22
*** jhenner has quit IRC22:23
*** s0mik has quit IRC22:31
*** s0mik has joined #openstack-meeting22:32
*** anniec has joined #openstack-meeting22:32
*** littleidea has joined #openstack-meeting22:37
*** littleidea has left #openstack-meeting22:38
*** littleidea has joined #openstack-meeting22:42
*** littleidea has left #openstack-meeting22:42
*** henrynash has quit IRC22:44
*** jaypipes has quit IRC22:44
*** nachi has quit IRC22:47
*** littleidea has joined #openstack-meeting22:48
*** rnirmal has quit IRC22:48
*** littleidea has left #openstack-meeting22:48
*** gatuus has quit IRC22:49
*** littleidea has joined #openstack-meeting22:53
*** littleidea has left #openstack-meeting22:53
*** winston-d has quit IRC22:59
*** s0mik has quit IRC23:01
*** s0mik has joined #openstack-meeting23:03
*** littleidea has joined #openstack-meeting23:04
*** salv-orlando_ has quit IRC23:05
*** littleidea has left #openstack-meeting23:05
*** stevebake has quit IRC23:10
*** cdub_ has quit IRC23:11
*** salv-orlando has joined #openstack-meeting23:11
*** ywu_ has quit IRC23:20
*** ywu_ has joined #openstack-meeting23:20
*** ywu_ has quit IRC23:35
*** ywu_ has joined #openstack-meeting23:35
*** jgriffith has quit IRC23:35
*** jgriffith has joined #openstack-meeting23:37
*** littleidea has joined #openstack-meeting23:38
*** littleidea has quit IRC23:39
*** anniec_ has joined #openstack-meeting23:39
*** littleidea has joined #openstack-meeting23:40
*** jakedahn is now known as jakedahn_zz23:41
*** anniec_ has quit IRC23:42
*** anniec_ has joined #openstack-meeting23:42
*** anniec has quit IRC23:43
*** anniec_ is now known as anniec23:43
*** jakedahn_zz is now known as jakedahn23:45
*** ywu_ has quit IRC23:50
*** ywu_ has joined #openstack-meeting23:50
*** nati_ueno has joined #openstack-meeting23:52
*** nati_uen_ has quit IRC23:53
*** nati_ueno has quit IRC23:54
*** nati_ueno has joined #openstack-meeting23:55

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