Thursday, 2012-05-24

*** lloydde has quit IRC00:02
*** gongys_ has quit IRC00:03
*** gongys_ has joined #openstack-meeting00:04
*** sdague has joined #openstack-meeting00:07
*** nati_ueno has joined #openstack-meeting00:07
*** sdague has quit IRC00:11
*** sdague has joined #openstack-meeting00:12
*** dwcramer has joined #openstack-meeting00:21
*** danwent has joined #openstack-meeting00:21
*** danwent has quit IRC00:21
*** dtroyer_zzz is now known as dtroyer00:23
*** sdague has quit IRC00:25
*** edygarcia has quit IRC00:28
*** edygarcia_ has joined #openstack-meeting00:28
*** sdague has joined #openstack-meeting00:29
*** gholt has joined #openstack-meeting00:46
*** edygarcia has joined #openstack-meeting00:49
*** edygarcia__ has joined #openstack-meeting00:50
*** edygarcia___ has joined #openstack-meeting00:51
*** edygarcia_ has quit IRC00:52
*** edygarcia has quit IRC00:53
*** edygarcia___ is now known as edygarcia00:53
*** edygarcia__ has quit IRC00:54
*** nati_ueno has quit IRC00:55
*** nati_uen_ has joined #openstack-meeting00:55
*** edygarcia_ has joined #openstack-meeting00:56
*** edygarcia has quit IRC00:57
*** edygarcia_ is now known as edygarcia00:57
*** edygarcia_ has joined #openstack-meeting01:05
*** gyee has joined #openstack-meeting01:07
*** edygarcia_ has quit IRC01:08
*** edygarcia has quit IRC01:08
*** edygarcia_ has joined #openstack-meeting01:08
*** edygarcia has joined #openstack-meeting01:09
*** aswadrangnekar has joined #openstack-meeting01:09
*** edygarcia__ has joined #openstack-meeting01:11
*** edygarcia__ has quit IRC01:12
*** edygarcia_ has quit IRC01:12
*** edygarcia_ has joined #openstack-meeting01:12
*** edygarcia has quit IRC01:15
*** aswadrangnekar has quit IRC01:17
*** edygarcia_ has quit IRC01:17
*** edygarcia has joined #openstack-meeting01:20
*** markmcclain has joined #openstack-meeting01:22
*** mattray has joined #openstack-meeting01:27
*** edygarcia_ has joined #openstack-meeting01:29
*** edygarcia_ has quit IRC01:30
*** edygarcia has quit IRC01:31
*** nati_ueno has joined #openstack-meeting01:35
*** nati_uen_ has quit IRC01:35
*** novas0x2a|laptop has quit IRC01:49
*** ewindisch has joined #openstack-meeting01:53
*** ozstacker has quit IRC02:00
*** littleidea has quit IRC02:06
*** ozstacker has joined #openstack-meeting02:07
*** ayoung has quit IRC02:09
*** littleidea has joined #openstack-meeting02:09
*** jd___ has quit IRC02:13
*** jd___ has joined #openstack-meeting02:14
*** joearnold has joined #openstack-meeting02:15
*** joearnold has quit IRC02:21
*** Mandell has quit IRC02:22
*** jgriffith_away has quit IRC02:23
*** dwcramer has quit IRC02:25
*** littleidea has quit IRC02:30
*** jgriffith_away has joined #openstack-meeting02:36
*** dwcramer has joined #openstack-meeting02:44
*** mnewby has quit IRC02:45
*** troytoman-away is now known as troytoman02:46
*** danwent has joined #openstack-meeting02:51
*** markmcclain has quit IRC03:00
*** nati_uen_ has joined #openstack-meeting03:02
*** dwcramer has quit IRC03:04
*** danwent has quit IRC03:05
*** nati_ueno has quit IRC03:05
*** littleidea has joined #openstack-meeting03:05
*** ryanpetrello has joined #openstack-meeting03:06
*** glenc_ has joined #openstack-meeting03:10
*** glenc has quit IRC03:12
*** joearnold has joined #openstack-meeting03:14
*** jdurgin has quit IRC03:17
*** mattray has quit IRC03:27
*** ryanpetrello has quit IRC03:29
*** danwent has joined #openstack-meeting03:29
*** dprince has quit IRC03:34
*** edygarcia has joined #openstack-meeting03:42
*** anderstj has joined #openstack-meeting03:43
*** gyee has quit IRC03:47
*** nati_uen_ has quit IRC03:57
*** Mandell has joined #openstack-meeting03:57
*** ewindisch has quit IRC03:57
*** milner has quit IRC03:58
*** ewindisch has joined #openstack-meeting04:00
*** jakedahn is now known as jakedahn_zz04:00
*** ewindisch has quit IRC04:01
*** dhellmann has joined #openstack-meeting04:07
*** dhellmann has quit IRC04:08
*** danwent has quit IRC04:09
*** milner has joined #openstack-meeting04:11
*** adjohn has quit IRC04:24
*** cdub has quit IRC04:30
*** cdub has joined #openstack-meeting04:30
*** edygarcia has quit IRC04:40
*** joearnold has quit IRC04:44
*** adjohn has joined #openstack-meeting04:48
*** jakedahn_zz is now known as jakedahn04:50
*** garyk has quit IRC04:53
*** ywu has quit IRC05:14
*** nati has quit IRC05:20
*** byeager has quit IRC05:43
*** troytoman is now known as troytoman-away05:55
*** joearnold has joined #openstack-meeting05:59
*** byeager has joined #openstack-meeting06:04
*** jd___ has quit IRC06:13
*** jd___ has joined #openstack-meeting06:15
*** littleidea has quit IRC06:17
*** joearnold has quit IRC06:22
*** bencherian has joined #openstack-meeting06:42
*** bencherian has left #openstack-meeting06:42
*** anderstj has quit IRC07:01
*** ttrifonov_zZzz is now known as ttrifonov07:04
*** rohitk has joined #openstack-meeting07:10
*** garyk has joined #openstack-meeting07:18
*** gongys_ has quit IRC07:34
*** sandywalsh has quit IRC07:34
*** Mandell has quit IRC07:56
*** byeager has quit IRC08:02
*** derekh has joined #openstack-meeting08:20
*** byeager has joined #openstack-meeting08:21
*** darraghb has joined #openstack-meeting08:34
*** adjohn has quit IRC08:48
*** ttrifonov is now known as ttrifonov_zZzz08:56
*** byeager has quit IRC09:08
*** lloydde has joined #openstack-meeting09:12
*** byeager has joined #openstack-meeting09:31
*** Semy_ has joined #openstack-meeting09:45
*** Semy_ has left #openstack-meeting09:46
*** rohitk has quit IRC10:28
*** rohitk has joined #openstack-meeting10:29
*** rohitk has quit IRC10:33
*** markmcclain has joined #openstack-meeting11:19
*** ttrifonov_zZzz is now known as ttrifonov11:22
*** markvoelker has joined #openstack-meeting11:23
*** lloydde has quit IRC11:27
*** markmcclain has quit IRC11:27
*** rohitk has joined #openstack-meeting11:43
*** byeager has quit IRC11:54
*** littleidea has joined #openstack-meeting12:00
*** dwcramer has joined #openstack-meeting12:03
*** littleidea has quit IRC12:08
*** dwcramer has quit IRC12:13
*** byeager has joined #openstack-meeting12:17
*** byeager has quit IRC12:32
*** sandywalsh has joined #openstack-meeting12:32
*** dwcramer has joined #openstack-meeting12:36
*** byeager has joined #openstack-meeting12:47
*** dwcramer has quit IRC12:49
*** littleidea has joined #openstack-meeting12:55
*** semy_ has joined #openstack-meeting12:58
*** semy_ has left #openstack-meeting13:03
*** rafaduran has joined #openstack-meeting13:03
*** sandywalsh_ has joined #openstack-meeting13:04
*** dprince has joined #openstack-meeting13:05
*** sandywalsh has quit IRC13:05
*** nati has joined #openstack-meeting13:11
*** semyazz has joined #openstack-meeting13:12
*** ayoung has joined #openstack-meeting13:13
*** glenc has joined #openstack-meeting13:13
*** edygarcia has joined #openstack-meeting13:16
*** glenc_ has quit IRC13:16
*** nati has quit IRC13:20
*** nati has joined #openstack-meeting13:20
*** edygarcia_ has joined #openstack-meeting13:25
*** edygarcia has quit IRC13:27
*** edygarcia_ is now known as edygarcia13:27
*** edygarcia_ has joined #openstack-meeting13:29
*** markmcclain has joined #openstack-meeting13:32
*** edygarcia has quit IRC13:33
*** edygarcia has joined #openstack-meeting13:35
*** edygarcia_ has quit IRC13:37
*** edygarcia_ has joined #openstack-meeting13:37
*** edygarcia__ has joined #openstack-meeting13:38
*** edygarcia has quit IRC13:41
*** edygarcia__ is now known as edygarcia13:41
*** edygarcia_ has quit IRC13:42
*** danwent has joined #openstack-meeting13:47
*** edygarcia_ has joined #openstack-meeting13:49
*** edygarcia__ has joined #openstack-meeting13:50
*** edygarcia has quit IRC13:51
*** edygarcia__ is now known as edygarcia13:51
*** edygarcia_ has quit IRC13:53
*** GheRivero_ has joined #openstack-meeting13:53
*** edygarcia_ has joined #openstack-meeting13:56
*** oubiwann1 has joined #openstack-meeting13:56
*** edygarcia has quit IRC13:56
*** edygarcia_ is now known as edygarcia13:56
*** rash has joined #openstack-meeting14:03
*** edygarcia_ has joined #openstack-meeting14:03
*** edygarcia__ has joined #openstack-meeting14:04
*** edygarcia has quit IRC14:05
*** edygarcia__ is now known as edygarcia14:05
*** edygarcia__ has joined #openstack-meeting14:07
*** edygarcia_ has quit IRC14:08
*** edygarcia_ has joined #openstack-meeting14:09
*** edygarcia has quit IRC14:10
*** edygarcia_ is now known as edygarcia14:10
*** Gordonz has joined #openstack-meeting14:11
*** edygarcia__ has quit IRC14:12
*** edygarcia_ has joined #openstack-meeting14:14
*** danwent has quit IRC14:17
*** edygarcia has quit IRC14:18
*** edygarcia_ is now known as edygarcia14:18
*** anderstj has joined #openstack-meeting14:19
*** asdfasdf has joined #openstack-meeting14:20
*** mdomsch has joined #openstack-meeting14:21
*** Gordonz has quit IRC14:21
*** Gordonz has joined #openstack-meeting14:22
*** nati has quit IRC14:23
*** rafaduran has quit IRC14:26
*** mattray has joined #openstack-meeting14:27
*** rafaduran has joined #openstack-meeting14:27
*** dwcramer has joined #openstack-meeting14:29
*** nati has joined #openstack-meeting14:30
*** asdfasdf has quit IRC14:32
*** edygarcia has quit IRC14:32
*** edygarcia_ has joined #openstack-meeting14:33
*** dtroyer is now known as dtroyer_zzz14:34
*** edygarcia has joined #openstack-meeting14:34
*** markmcclain has quit IRC14:37
*** edygarcia_ has quit IRC14:38
*** edygarcia has quit IRC14:39
*** markmcclain has joined #openstack-meeting14:40
*** markmcclain has quit IRC14:40
*** markmcclain has joined #openstack-meeting14:40
*** jgriffith_away has quit IRC14:42
*** edygarcia has joined #openstack-meeting14:46
*** edygarcia_ has joined #openstack-meeting14:47
*** edygarcia_ has quit IRC14:48
*** mdomsch has quit IRC14:48
*** edygarcia has quit IRC14:50
*** mattray has quit IRC14:55
*** davidkranz has joined #openstack-meeting14:57
*** oubiwann1 has quit IRC14:58
*** markmcclain has quit IRC14:58
*** edygarcia has joined #openstack-meeting14:59
*** markvoelker has quit IRC14:59
*** markmcclain has joined #openstack-meeting14:59
*** markmcclain has quit IRC15:00
*** davidkranz_ has quit IRC15:00
*** oubiwann1 has joined #openstack-meeting15:00
*** markmcclain has joined #openstack-meeting15:01
*** blamar has joined #openstack-meeting15:01
*** edygarcia_ has joined #openstack-meeting15:03
*** bencherian has joined #openstack-meeting15:03
*** bcwaldon has left #openstack-meeting15:03
*** edygarcia__ has joined #openstack-meeting15:04
*** cdub has quit IRC15:05
*** edygarcia has quit IRC15:05
*** edygarcia__ is now known as edygarcia15:05
*** edygarcia_ has quit IRC15:07
*** edygarcia has quit IRC15:12
*** rnirmal has joined #openstack-meeting15:13
*** anderstj has quit IRC15:14
*** anderstj has joined #openstack-meeting15:18
*** cdub has joined #openstack-meeting15:19
*** cdub has quit IRC15:27
*** markvoelker has joined #openstack-meeting15:29
*** dtroyer_zzz is now known as dtroyer15:31
*** cdub has joined #openstack-meeting15:34
*** anderstj has quit IRC15:35
*** reed has quit IRC15:37
*** jgriffith has joined #openstack-meeting15:42
*** matwood has joined #openstack-meeting15:44
*** clayg has joined #openstack-meeting15:45
*** cdub has quit IRC15:46
*** cdub has joined #openstack-meeting15:47
*** rash has quit IRC15:47
*** s0mik has joined #openstack-meeting15:51
*** danwent has joined #openstack-meeting15:53
*** winston-d has joined #openstack-meeting15:53
*** danwent has quit IRC15:53
*** joearnold has joined #openstack-meeting15:54
*** byeager has quit IRC15:55
*** rafaduran has quit IRC15:56
*** winston-d is now known as zhiteng15:56
*** jdurgin has joined #openstack-meeting16:01
*** flacoste has joined #openstack-meeting16:01
jd___#startmeeting16:01
jd___#meetingname ceilometer16:01
openstackMeeting started Thu May 24 16:01:08 2012 UTC.  The chair is jd___. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
jd___#link https://lists.launchpad.net/openstack/msg12156.html16:01
jd___16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
openstackThe meeting name has been set to 'ceilometer'16:01
jd___16:01
jd___#topic actions from previous meetings16:01
*** openstack changes topic to "actions from previous meetings"16:01
jd___16:01
*** sssssss has joined #openstack-meeting16:01
*** dhellmann has joined #openstack-meeting16:01
jd___flacoste: something to add for you action item from last meeting?16:01
jd___dhellmann: also ? :)16:01
dhellmannsorry I'm late16:02
jd___no problem16:02
flacostejd___: nope, comments sent to the list16:02
dhellmannif we have time at the end can we talk about a way to share experimental code?16:02
flacostejd___: and i think we reached agreement16:02
claygo/16:02
jd___dhellmann: yep16:02
dhellmannthanks16:02
jd___#info flacoste comments sent to the list16:03
jd___#topic messaging queue system to use16:03
*** openstack changes topic to "messaging queue system to use"16:03
jd___now let's discuss the real stuff :)16:03
dhellmann:-)16:03
*** thrawn01 has joined #openstack-meeting16:04
dhellmannas I think I mentioned on the list, we should try to avoid dictating a specific implementation and limit ourselves to basic requirements for a message bus16:04
jd___#link https://lists.launchpad.net/openstack/msg11937.html16:04
jd___dhellmann: is nova.rpc mechanism enough?16:04
*** sssssss has quit IRC16:04
jd___I like the idea of using it, personally16:04
dhellmannif I can get this "worker" change approved it should do exactly what we need16:04
*** edygarcia has joined #openstack-meeting16:05
dhellmannI posted a new patch today with qpid tests but I need to push for more reviews16:05
jd___well your change seems to be in on a good path16:05
jd___and I understood correctly we'll get qpid/zmq/rabbit for free by using nova.rpc so everybody is likely to be happy?16:05
dhellmannthat is also my understanding16:06
*** mattray has joined #openstack-meeting16:06
flacostesounds good16:07
jd___ok so is everybody happy to say that we agree to use nova.rpc mechanism and let the user choose the messaging bus he wants?16:07
dhellmannwith the stipulation that when nova.rpc moves into the common library we should actually use *that* version16:07
dhellmanndepending on the schedule, of course16:07
jd___yeah, obviously :)16:08
dhellmannok, I'm happy with that decision16:08
jd___#agreed use nova.rpc as a messaging bus and let the user chose what he wants behind (qpid, rabbit, zmq…)16:08
jd___#agreed use nova.rpc from openstack.common when it moves to this16:08
jd___anything else?16:09
dhellmanndo we need to make sure the requirements nick posted to the list are met by the systems supported by nova.rpc?16:09
dhellmannI think they are, but...16:09
flacostewell, not all of them are16:10
flacosteby all queues16:10
dhellmanntrue. if the user has persistent queues disabled in rabbit then we can't guarantee delivery.16:10
dhellmannflacoste, did you have another example?16:10
flacosteand the ha story of rabbit isn't that great, last i heard16:10
jd___well, if the user shoots himself in the foot… :)16:10
jd___what about zmq?16:10
flacosteit required shared storage16:10
dhellmannI keep hearing that, but no one has any details. I'm not an expert, so I don't know one way or the other.16:10
jd___hm I don't think zmq has persistence16:11
flacostemy understanding is that it's easier to build a ha message queue system with zmq16:11
flacostebut yeah, i think it lacks some other requirements16:11
dhellmannso maybe that delivery requirement shouldn't be *our* requirement, but it may be a *user* requirement that we should support16:11
claygwell zmq doesn't really have a "queue" (independent service that "stores" the messages)16:11
dhellmannright, clayg, that's my understanding16:11
jd___as nijaba wrote "Not sure this list is exhaustive or viable" so it's likely that you can't satisfy *every* point with only one message queue16:11
jd___you'll have to do tradeoff16:11
dhellmannsomeone could build a message queue server with zmq but it isn't one by itself16:11
dhellmannexactly16:12
jd___but I don't think we should decide which tradeoff to do for the user16:12
jd___so nova.rpc is a good call :)16:12
dhellmann+116:12
jd___anything else?16:13
claygjd___: where are you at on yoru nova branch to support an independent volume service?  Do the volume tables get ripped out?  Will nova-compute be the only component to talk to volumes?  What's the attach workflow?  Who keeps track of what's attached where?16:13
clayg^ any of those16:13
uvirtbotclayg: Error: "any" is not a valid command.16:13
claygwhoa...16:13
dhellmannis that work related to ceilometer?16:14
jd___clayg: I don't follow you here?16:14
*** edygarcia_ has joined #openstack-meeting16:14
*** cdub has quit IRC16:14
claygam I in the wrong meeting?16:14
dhellmannmaybe. :-) this is the metering group meeting16:15
claygwhen will nova be ready to consume an indepent volume service (e.g. cinder)16:15
claygI guess I am in the wrong meeting then :D16:15
jd___I think you're in the wrong meeting :D16:15
jd___ok, so, except volumes :D anything else? :)16:16
dhellmannexperimental branches?16:16
jd___ok let's change topic then16:16
jd___#topic message bus usage described in architecture proposal V116:16
*** openstack changes topic to "message bus usage described in architecture proposal V1"16:16
*** edygarcia has quit IRC16:16
*** edygarcia_ is now known as edygarcia16:16
jd___I don't think dhellmann has something to add about it :)16:16
dhellmannheh16:16
dhellmannI haven't worked out the implementation details of sending the actual metering messages, yet. Should those be cast() calls?16:17
jd___dhellmann: good question16:17
dhellmannor should we use a topic publisher like the notifications do?16:18
jd___I'm more in favor of copying notifications16:18
dhellmannit seems like metering messages are another case where we might want multiple subscribers to see all of the messages16:18
dhellmannyeah, I'm leaning that way, too16:18
*** bencherian has quit IRC16:18
jd___it's just messaging so…16:18
mnaserI understand that metering messages will be sent over a topic, but will it also be exposed/stored in a database?16:18
dhellmannmnaser, yes16:19
jd___mnaser: that's the job of the collector, yes16:19
mnaserFantastic, I've been working with the Nova notification system and it's much better to request information.16:19
*** zhiteng has quit IRC16:19
jd___dhellmann: we use only one topic?16:19
dhellmannthe collector will write the info to a database and the api service will allow for some basic queries16:19
*** byeager has joined #openstack-meeting16:19
dhellmannwe could do it like notifications do and publish multiple times to "metering" and "metering + counter_id"16:20
dhellmannso metering and metering.instance for example16:20
jd___makes sense16:20
dhellmannthat doubles the traffic, but the exchange should just discard the message if no one is listening16:20
jd___#info we could do it like notifications do and publish multiple times to "metering" and "metering + counter_id"16:21
*** dwcramer has quit IRC16:21
jd___anything else on this?16:22
jd___I find the current architecture good enough and clear so… :)16:22
jd___good work from dhellmann \o/ :)16:22
*** edygarcia_ has joined #openstack-meeting16:22
dhellmannthanks!16:23
mnaserThe backend storage, is there plans for usage of RRD or how exactly are you guys thinking of doing it?16:23
*** cdub has joined #openstack-meeting16:23
dhellmannwe haven't worked that out yet, I think that's the topic we need to discuss this week if I remember the meeting schedule correctly16:23
jd___mnaser: we don't know yet, there's a meeting for this later in June (see http://wiki.openstack.org/Meetings/MeteringAgenda)16:23
jd___#topic Open discussion16:23
*** openstack changes topic to "Open discussion"16:23
jd___free fight time16:24
jd___dhellmann: experimental branches then?16:24
*** zhiteng has joined #openstack-meeting16:24
dhellmannwe've had some trouble with sharing experimental code through gerrit because of the rules about test coverage16:24
mnaserI see.  I can try and figure that out, because we currently have a full collector service that uses nova (only works with XenServer driver) and also exposes data using REST API + keystone authentication .. I'll try to see how we can bring the java code to pytohn and maybe help16:24
mnaserWe are using RRD to store the data however16:24
dhellmannpersonally I think it's too early to be so strict with testing, but I'm OK with it if we can work out another way to share code16:24
*** zhiteng is now known as winston-d16:24
dhellmannmaybe just github branches?16:24
*** edygarcia has quit IRC16:25
*** edygarcia has joined #openstack-meeting16:25
dhellmannI'm worried that if we use separate branches we might end up with messy merges later, esp. with rebasing16:25
jd___mnaser: if you can share with us your experience we'd be glad indeed16:25
dhellmann+1, it would be great to hear about your experiences with that16:26
jd___dhellmann: I'm on your side on this but heh…16:26
*** Mandell has joined #openstack-meeting16:26
jd___I've already lost much time because of merges and rebase I had to do16:26
mnaserjd___: I'll be looking forward for future meetings, I'll be adding them to my calendar16:26
dhellmannlike I said, I'm OK with keeping the gerrit code "clean" and tested, but -- right16:26
jd___mnaser: great, thanks!16:26
dhellmannmaser good!16:26
*** edygarcia_ has quit IRC16:27
dhellmannjd___, maybe when we agree we like an experimental branch we rebase it and submit it, then delete the branch on github?16:27
dhellmannI guess we can just leave all of the experimental branches out there16:28
jd___the problem is that we can base code on something experimental16:28
dhellmannI don't know the best way to handle it16:28
dhellmannright16:28
jd___I mean rebasing on something that has been rebased is nightmare, even with git16:28
dhellmannwell, maybe we're reaching a point where this problem isn't going to be so severe16:28
jd___dhellmann: this is what I think16:29
jd___it has been a problem for one or two big commits16:29
*** joearnold has quit IRC16:29
dhellmannyeah, true16:30
jd___but the current architecture seems solid enough for now16:30
jd___I don't think we'll encounter the problem again16:30
dhellmannand if we think it might come up, we can have more discussions on the mailing list16:30
jd___yep16:30
dhellmannI wasn't looking for something formal, just some ideas16:30
dhellmannok, I'm happy with that16:30
dhellmannwhat else do we have?16:30
jd___:)16:30
mnaserDoes the project currently share the same OpenStack mailing list or has a specific one?  If it does, any tags in the subjects so I can have a filter on those?16:31
flacostemnaser: [metering] on the main list16:31
dhellmannwe use the main mailing list and messages are tagged with [metering] in the subject16:31
jd___dhellmann: do you have an idea on what you'll work in the next days, if you do work on that?16:31
mnaserPerfect, thank you.16:31
*** edygarcia has quit IRC16:31
dhellmannI am going to work on more notification converters16:31
dhellmannI have the branch with plugins for the polling agent, too16:32
jd___ok16:32
jd___I've pushed a plugin for floating IP today16:32
dhellmannour alpha 1 period ends next week and I need to try to get at least a branch going that logs events to the console, if not sending metering messages in some format16:32
dhellmannexcellent, I'll have a look after lunch16:32
jd___ok16:33
*** garyk has quit IRC16:33
dhellmannthe topic for next week is "API message format" but I'm going to just do something simple for now and plan to change it later if we don't like what I put together :-)16:33
jd___good :)16:33
dhellmannhow do we want to track to-do items? bugs in launchpad?16:34
dhellmannI feel like we're at the point where we could open some tickets for things like these plugins16:34
jd___sounds like a good idea16:34
jd___yep16:34
jd___#action jd___ open tickets in launchpad for plugins, etc…16:34
jd___I'll do so we can assign ticket and not duplicate the work16:35
dhellmanngood plan16:35
mnaserJust as a suggestion, would it be good to propose a nova API extension that provides metrics that Ceilometer can consume (and each driver can write their own code to provide those metrics)16:35
dhellmannthat's more or less what the plugins are for16:35
mnaserI see16:36
dhellmannyou can add code to the agent that polls, and the results are published so the collector can see them16:36
dhellmannand you can add listeners in the collector for events like notifications16:36
dhellmannone goal was to reduce the number of changes needed within the other projects16:36
dhellmannwe may need some, eventually, but we want as few as possible16:37
dhellmannjd___, we need tickets to have the collector listen for notifications from the services other than nova16:37
mnaserI see, so a dependency to go through another project is not something that is preferred in this case?16:37
dhellmannright, we only want to push changes into the other projects if there is no way to avoid it16:37
jd___#action jd___ open ticket to have the collector listen for notifications from the services other than nova16:38
dhellmannand we want those things to be as general as possible (so, having them send general notifications is OK but they should not send metering data directly)16:38
jd___dhellmann: you mean like glance I guess?16:38
dhellmannglance and quantum at least16:38
dhellmannmaybe swift?16:38
dhellmannwe might need to poll swift, I'm not sure16:38
mnaserI see, so for example, if we have some nova-compute nodes that are running XenServer, would we have to add them all individually to Ceilometer (forigve my silly questions)16:39
dhellmannbasically, for each counter we identified figure out which service has the data and make sure we are listening to its notification stream16:39
jd___I don't know quantum16:39
jd___swift does not use a RPC16:39
dhellmannmnaser, no need to apologize for asking questions!16:39
dhellmannquantum is the new networking stuff16:39
mnaserI feel like they're basic questions about the infrastructure of it so sorta "go read the arch docs" :)16:40
jd___dhellmann: I know what it is but not how it works ;)16:40
dhellmannmnaser, you might want to read over http://wiki.openstack.org/EfficientMetering/ArchitectureProposalV1 but we can still discuss here16:40
dhellmannah, ok, jd___16:40
dhellmannI don't either :-_16:40
dhellmann:-)16:40
jd___lol16:40
jd___anyway quantum is out of scope for now16:40
dhellmannok. I'm going to need it, but I can track that myself.16:41
jd___your call ;)16:41
jd___if you do more than what is planned it's good too I guess! :)16:41
*** clayg has left #openstack-meeting16:41
dhellmannmnaser a ceilometer agent runs on the compute node and polls the hypervisor for details through libvirt (or the other drivers) and we also catch notifications for events like creating or deleting instances16:41
mnaserGotcha, I see, I figured when reading.16:42
dhellmannjd___ we also need tickets for adding polling for hypervisor drivers that do not use libvirt16:42
mnaserIn that case, I can help write up the XenServer plugins/poller, as I already have most of the work done for it to be honest.16:42
jd___yeah, maybe mnaser will be able to help on that :)16:42
dhellmannexcellent!16:42
jd___#action jd___ we also need tickets for adding polling for hypervisor drivers that do not use libvirt16:42
dhellmannthat worked out nicely16:42
jd___mnaser: when the ticket will be opened feel free to at least describe what technique you did use to poll info for XenServer16:43
jd___it'd be awesome16:43
mnaserjd___: Will do, there are numerous ways as well so I'll bring up the options and then a decision can be taken16:43
jd___ mnaser: perfect16:43
dhellmannsounds like a good approach16:43
*** dwalleck has joined #openstack-meeting16:43
dhellmannthat's all I have for this week. is there anything else to discuss?16:43
jd___nothing for me16:44
jd___I'll close the meeting, mnaser feel free to join #openstack-metering if you want to discuss more with us16:44
mnaserIn there :)16:44
dhellmanngood meeting jd___16:44
dhellmannand mnaser16:44
jd___thanks guys!16:44
jd___#endmeeting16:45
dhellmannthank you!16:45
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"16:45
mnaserThanks, nice to speak with you guys16:45
openstackMeeting ended Thu May 24 16:45:00 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.html16:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.txt16:45
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.log.html16:45
*** dhellmann has quit IRC16:45
*** markmcclain has quit IRC16:45
*** Ravikumar_hp has joined #openstack-meeting16:46
*** markmcclain has joined #openstack-meeting16:46
*** edygarcia has joined #openstack-meeting16:47
*** donaldngo_hp has joined #openstack-meeting16:47
*** nati has quit IRC16:47
*** edygarcia_ has joined #openstack-meeting16:48
*** flacoste has left #openstack-meeting16:50
*** edygarcia__ has joined #openstack-meeting16:50
*** edygarcia has quit IRC16:51
*** edygarcia__ is now known as edygarcia16:51
*** derekh has quit IRC16:53
*** edygarcia_ has quit IRC16:53
*** danwent has joined #openstack-meeting16:54
*** joearnold has joined #openstack-meeting16:55
*** dhellmann has joined #openstack-meeting16:56
*** nati has joined #openstack-meeting16:58
*** oubiwann1 has quit IRC16:59
*** rafaduran has joined #openstack-meeting17:00
*** Sam___ has joined #openstack-meeting17:00
jaypipesgood afternoon QA team!17:00
jaypipes#startmeeting17:00
openstackMeeting started Thu May 24 17:00:38 2012 UTC.  The chair is jaypipes. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
dwalleckhey folks!17:00
*** garyk has joined #openstack-meeting17:00
rohitkhellooo17:00
jaypipes#link Agenda: http://wiki.openstack.org/Meetings/QATeamMeeting17:01
Ravikumar_hphi17:01
jaypipes#topic Awesomeness17:01
*** openstack changes topic to "Awesomeness"17:01
dwalleckWe've got a fresh one from the Rack. Sam___ just joined us17:01
*** markmcclain has quit IRC17:01
jaypipesw00t. welcome Sam___17:01
dwalleckHe does stuff with files and volumes and such. Smart fellow :)17:01
Sam___Hello Jay. Happy to be here.17:02
*** edygarcia has quit IRC17:02
jaypipesBefore we get to the real agenda, I wanted to give a big shout-out to rohitk, Ravikumar_hp and all the folks who have enabled the tempest test suite to reach nearly 260 tests!17:02
jaypipeshttps://jenkins.openstack.org/job/gate-tempest-devstack-vm/test/?width=1200&height=60017:02
*** JoseSwiftQA has joined #openstack-meeting17:02
dwalleckwoot!17:02
rohitkyay! Keep the bar green!!17:02
jaypipesI think back to just one month ago, and we've made a heck of a lot of progress in just 4 weeks.17:02
Ravikumar_hpThanks. It is collective joint effort. still more to come17:02
*** dhellmann has quit IRC17:03
jaypipesthx to fattarsi as well, for adding Identity API tests!17:03
jaypipeswe've been having some off and on failures in that gate job, but not due to tempest...17:03
fattarsithanks, great to see the progress on tempest as a whole17:03
jaypipesthe failures are due to some instabilty in the CI node providers.17:03
jaypipesfattarsi: indeed :)17:04
rohitkjaypipes: Special mention to NTT folks in Japan who have contribute many of these tests!17:04
rohitkcontributed*17:05
jaypipesthat stability I refer to is well represented in the following graph:17:05
jaypipeshttps://jenkins.openstack.org/job/gate-tempest-devstack-vm/834/testReport/history/17:05
*** edygarcia has joined #openstack-meeting17:05
jaypipesanyway, I'm going to work on diagnosing those instabilities with jeblair and the CI team, but in the meantime, let's keep up the code reviews and new test patches..17:06
jaypipesok, on to the main agenda17:06
jaypipes#topic Status of the smoke test merge proposal17:06
*** openstack changes topic to "Status of the smoke test merge proposal"17:06
jaypipesUnfortunately, I have not completed the changes from dwalleck's review. I should be able to get those done today, however.17:06
*** JoseSwiftQA_ has joined #openstack-meeting17:06
jaypipesSo the smoke refactor will have to be pushed out to status next week...17:06
JoseSwiftQA_blargh17:06
jaypipes#topic Status of the Swift test code reviews17:07
*** JoseSwiftQA has quit IRC17:07
*** openstack changes topic to "Status of the Swift test code reviews"17:07
jaypipesJoseSwiftQA_: perfect timing :)17:07
JoseSwiftQA_:D17:07
dwallecksounds good17:07
JoseSwiftQA_I've got some of the changes made already, and am getting the rest done as time permits.  Should be able to finish soon.17:07
jaypipesgood.17:08
jaypipesJoseSwiftQA_: any of the code review comments that you have questions about?17:08
JoseSwiftQA_Not really.  They're all fairly straight forward and good suggestions.17:08
*** zhiteng has joined #openstack-meeting17:09
jaypipescoolio.17:09
jaypipes#topic https://bugs.launchpad.net/tempest/+bug/1003741 is currently the only failing test on the devstack Tempest gate job and needs to be addressed17:09
*** openstack changes topic to "https://bugs.launchpad.net/tempest/+bug/1003741 is currently the only failing test on the devstack Tempest gate job and needs to be addressed"17:09
uvirtbotLaunchpad bug 1003741 in nova "Delete a flavor test fails" [High,Fix committed]17:09
jaypipesthat was the only blocker I saw. Looks like dprince has addressed the bug (in Nova).17:10
Ravikumar_hpjaypipes: joseSwiftQA: we will pick up some additional testcase once first batch of tests checked-in17:10
jaypipesRavikumar_hp: for swift?17:10
Ravikumar_hpyes17:10
jaypipeskk17:10
JoseSwiftQA_Sure.  I'll start adding the rest of the client functionality as well.17:10
rohitkjaypipes: did we have tempest job run after the Fix Commit?17:10
jaypipesso, that blocker is actually no longer blocking :) so, scratch that off the list ;)17:11
jaypipesrohitk: yup, and all tests passed.17:11
rohitkjaypipes: cool17:11
jaypipes#topic Outstanding code reviews17:11
*** openstack changes topic to "Outstanding code reviews"17:11
jaypipes#link https://review.openstack.org/#/q/status:open+project:openstack/tempest,n,z17:11
*** winston-d has quit IRC17:11
*** zhiteng is now known as winston-d17:11
*** carlos_swift has joined #openstack-meeting17:12
jaypipesWe've got quite a few outstanding reviews to get to. donaldngo_hp, I will get to those stable/essex ones today.17:12
jaypipessorry, stable/diablo.17:12
donaldngo_hpjaypipes++17:12
jaypipesI just need to spin up a diablo env...17:12
Ravikumar_hpjaypipes: Fixes bug 903875 – New tests for Volume Attachments - we will abandon for now17:13
uvirtbotLaunchpad bug 903875 in tempest "Write Testcases for Volume attachments" [Medium,In progress] https://launchpad.net/bugs/90387517:13
jaypipesIf everyone could go through all the merge proposals and provide a review, that would be appreciated!17:13
*** somik has joined #openstack-meeting17:13
jaypipesRavikumar_hp: yes, makes sense since the extension doesn't seem to be complete in Nova anyway :)17:13
rohitkjaypipes,dwalleck,dkranz: Thanks for reviewing our branches so meticulously, but how are we handling dependent branches?17:13
*** dprince has quit IRC17:14
rohitkif we have already submitted some code for review and another review is depended on the first review, how do we set the dependency?17:14
*** nati_ueno has joined #openstack-meeting17:14
jaypipesrohitk: depends :) if a branch is TRULY dependent on another, then if you do a git review, then the branch will be shown in DEPENDENT BRANCHES on the Gerrit review area17:14
dwalleckrohitk: Do we have dependent branches? I've been avoiding doing that to not have issues17:14
rohitkdwalleck: well, 'avoiding' is one way to handle it17:14
jaypipesrohitk: if the branch is not really a dependent branch (i.e. you are just waiting for someone else's stuff to go in before yours), then you need to write a comment saying so in the review.... ok?17:14
*** s0mik has quit IRC17:15
*** somik is now known as s0mik17:15
rohitkjaypipes: ok, for me it's important that the reviewers are in the know about dependent branches17:15
jaypipesrohitk: another strategy for branches like that is to use the DRAFT branch Gerrit feature, which pushes the branch up to Gerrit for you to review, but keeps it in a DRAFT status. Use git review -D for that.17:15
rohitkunless comments get overlooked17:15
dwalleckrohitk: I haven't found a reason to do it. I never know how much will change in a parent branch, so to avoid extra work, I get parent branches in first17:16
jaypipesrohitk: again, depends on what your definition of "dependent branch" is ;)17:16
rohitkdwalleck: I haven't looked into the true dependent branch model in gerrit, if that works while submitting a branch, that should do17:17
jaypipesalright, any more questions on that topic? Everybody please do code reviews as much as you can :)17:18
jaypipes#topic Assigning QA team members to adopt Folsom blueprints for Nova, Glance and Keystone to ensure a functional test plan is part of the blueprint and that the developer of any features for Folsom are collaborating with QA team members17:18
*** openstack changes topic to "Assigning QA team members to adopt Folsom blueprints for Nova, Glance and Keystone to ensure a functional test plan is part of the blueprint and that the developer of any features for Folsom are collaborating with QA team members"17:18
jaypipesOK, so Nayna, Ravikumar_hp and I had a chat yesterday about this...17:18
jaypipesbasically, we are going to propose that a QA team member be assigned to new Folsom blueprints in Nova to ensure a functional/integration test plan is put together in addition to unit tests17:19
jaypipesRavikumar_hp was going to come up with a blueprint we could use as an example.17:19
jaypipesRavikumar_hp: any progress on that?17:19
Ravikumar_hpjaypipes: will start today . Need to see if blueprint has enough details17:19
jaypipesah, ok.17:19
jaypipes#action Ravikumar_hp to find good example blueprint for QA functional test plan17:20
jaypipes#action jaypipes to write draft email to ML about QA team working with developers on functional test plans for all new feature blueprints.17:20
jaypipes#topic Assigning QA team members to address the increasing number of skipped tests; bugs uncovered in Nova should be tracked appropriately and the @skip decorators removed when the bug is fixed. Jay recommends having an agenda item on the weekly meetings where the skip count (and associated bug reports) are covered.17:20
*** openstack changes topic to "Assigning QA team members to address the increasing number of skipped tests; bugs uncovered in Nova should be tracked appropriately and the @skip decorators removed when the bug is fixed. Jay recommends having an agenda item on the weekly meetings where the skip count (and associated bug reports) are covered."17:20
jaypipesOK, so this is a topic I added to the agenda because I've been getting concerned about the increasing number of (valid) skips in Tempest17:21
dwalleckFor blueprints being dev'd within an org, would it make sense to assign those blueprints to some tester from that org?17:21
jaypipesWe need to ensure that skips only last as long as a bug is not fixed, and that the skip is removed when the fix goes into the upstream project17:21
jaypipesdwalleck: yes, it would indeed.17:21
rohitkjaypipes: ++17:22
fattarsijaypipes: agreed, but it is difficult to track, unless there is a frequent audit17:22
jaypipesWhat do y'all think about my proposal that we have an ongoing agenda item for tracking skips?17:22
rohitkit will be really hard to track bugs and remove those decorator17:22
jaypipesfattarsi: right, which is why I'm suggesting adding a piece to our weekly meeting to track progress..17:22
Ravikumar_hpjaypipes: makes sense since there is no automated way17:23
dwalleckWe could do something automated to check if a bug was fixed, but there's no guarentee the fix would be deployed to your test environment17:23
jaypipesthe only other thing I can think of is working with jeblair and mtaylor to put a Gerrit hook into the Ci system to notify QA team when a bug that is in our skip list is Fix Committed...17:23
Sam___I think an ongoing agenda item for tracking skips is a good fix short term17:23
*** joearnold has quit IRC17:24
Sam___longer term would be to automate a way to process the skips17:24
jaypipesdwalleck: well, for the gating job at least, it would be (since the devstack builder builds from the HEAD of all project trunks17:24
jaypipesSo, I've found that unless there is a person (or persons) responsible for tracking stuff like this, it rarely gets done...17:25
jaypipesAnd I think it would be useful to have a "Skip Captain" in the same way we have a QA Captain rotation for doing the agenda/summary of the meetings...17:25
rohitkjaypipes: Once the notifications are out, would it be helpful for the committer remove his own skip decorators?17:25
mtaylorjaypipes: you know where our puppet repo is ... ;)17:25
rohitkjaypipes: Skip Captain ++17:25
jaypipesmtaylor: :P17:25
JoseSwiftQA_heh... Skipper.17:26
dwalleckjaypipes: What we do internally is have a skipped test build17:26
jaypipesSo, basically the skip captain would be responsible for looking at the test result reports for skips and seeing if the associated bugs are in the project trunks17:26
*** GheRivero_ has quit IRC17:27
dwalleckIt runs our skipped tests daily and is inversed. If any test passes, the build fails17:27
jaypipesdwalleck: could you explain further?17:27
jaypipesdwalleck: ah, I see... so basically running nosetests --noskip?17:27
dwalleckWhich triggers an investigation and removal of the skip17:27
dwalleckyup17:27
jaypipesgotcha...17:27
jaypipesdwalleck: perhaps the skip captain could be responsible for checking the status of such a Jenkins jobs if I set one up and following up in the code for removing fixed bug skips?17:28
rohitkand have a periodic SkipSquash17:28
jaypipesdwalleck: I like automating as much as possible, but I think we really need a person/persons responsible for tracking of the skip stuff...17:28
jaypipesrohitk: every week... should have a "removed X number of bug fix skips" status report17:29
rohitkagreed17:29
jaypipesrohitk: my point is I really think somebody needs to have it as a weekly duty... nothing gets done if everyone assumes someone else is doing it ;)17:29
rohitkjaypipes: Rotation sounds good to me17:30
jaypipesso... a vote. Does anyone mind me creating a Skip Captain rotation in the same way as the http://wiki.openstack.org/QACaptainRotation17:30
dwallecksure17:30
Ravikumar_hpJaypipes: sure17:30
Sam___sure17:30
*** gyee has joined #openstack-meeting17:31
JoseSwiftQA_sounds like a plan17:31
jaypipesk, I will include more people and ensure the QA Captain and Skip Captain duties don't overlap17:31
jaypipes#action jaypipes to create Skip Captain duties wiki page and rotation17:31
Ravikumar_hphope skip captain does not skip the duty17:31
jaypipeslol :)17:32
jaypipes#topic Open discussion17:32
*** openstack changes topic to "Open discussion"17:32
Sam___I have a couple things I've been working on for lunr that might be vialble for a blueprint17:33
jaypipesSam___: cool.17:33
Sam___the main thing I'm thinking right now is that I have a wrapper class that functions as a client for the nova-client CLI process17:33
Sam___I needed it to test integration between nova and lunr17:33
Sam___It wouldn't take me long to put a blueprint together and tempest-ze the code.17:34
jaypipesSam___: does it use the CLI or the novaclient *library*?17:34
jaypipesIOW, out of process or in-process calls?17:34
Sam___It uses the acutal CLI client process17:35
jaypipesso it calls out to a subprocess and calls things like "nova server-list", etc?17:35
Sam___there is a generic command line connector that has a child wrapping biz logic for things like nova server-list17:35
jaypipesor instance-list, can never remember...17:35
Sam___then that is consumed by an abstracted client17:36
jaypipesSam___: hmm, ok...17:36
Sam___to deal with texts17:36
*** danwent has quit IRC17:36
Sam___it screen scrapes the prettytable and turns it into a domain object that is a child of prettytable and allows for searching the data17:36
*** Mandell has quit IRC17:36
Sam___I'm doing it on purpose because of a request to specifically test the CLI client17:37
jaypipesSam___: you might want to check this out as an alternative: https://review.openstack.org/#/c/7069/3/tempest/manager.py17:37
jaypipesSam___: uses the client programming interface instead of the CLI... but you get the picture.17:37
jaypipesSam___: we've had numerous debates about whether to test with novaclient or with a custom rest client that tempest uses. We've pretty much come to the conclusion that both are important to test with for different reasons, but I don't think we've had any agreement that testing using out-of-process CLI calls is any more useful than using the novaclient.Client classes in-process17:39
jaypipesdwalleck has some strong views on that I believe ;)17:39
Sam___sorry, was just looking at your manager.py class. It looks like an interesting start. I will dig into it more later.17:41
jaypipesSam___: yup, no worries! looking forward to your contributions!17:41
jaypipesAnybody else have stuff to bring up? Else I'll end the meeting...17:41
Ravikumar_hpnone17:41
dwallecknope17:41
rohitkjaypipes: Can we time our nosetests?17:41
jaypipesrohitk: I believe they already do?17:42
rohitkor I havent seen the jenkins console jobs yet17:42
dwalleckrohitk: Do you mean set limits per test? I believe there's a decorator for that17:42
rohitkoope, sorry :)17:42
Sam___I agree that that is a larger discussion in general. My personal (over-simplified) two cents is that we should have clients/adapters/etc... for anything that is delivered code. The real thought about the difference between the imported CLI and the actual from the command line CLI comes down to code path difference really. :-)17:42
rohitkjaypipes: gotcha17:42
jaypipesSam___: agreed.17:42
dwalleckThe xunit results should also show how long each test took if you just want tracking17:42
jaypipesdwalleck: right17:43
rohitkok17:43
jaypipesOK, let's wrap this baby up. I'll send a summary report by end of day.17:43
jaypipesthx all!17:43
jaypipes#endmeeting17:43
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"17:43
openstackMeeting ended Thu May 24 17:43:49 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-17.00.html17:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-17.00.txt17:43
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-17.00.log.html17:43
winston-drohitk, hey17:44
rohitkhey17:44
winston-dis it like almost 1 am in india?17:45
rohitknope, 11:15 p.m :)17:45
*** donaldngo_hp has quit IRC17:45
*** dwalleck has quit IRC17:46
*** rohitk has quit IRC17:46
*** JoseSwiftQA_ has quit IRC17:47
*** nati has quit IRC17:47
*** carlos_swift has quit IRC17:47
*** nati has joined #openstack-meeting17:48
*** dendro-afk is now known as dendrobates17:49
*** Sam___ has quit IRC17:52
*** mdomsch has joined #openstack-meeting18:03
*** Amw3000 has joined #openstack-meeting18:07
DuncanTAny volume people here?18:07
*** jog0 has joined #openstack-meeting18:08
rnirmalDuncanT: yeah..18:10
rnirmalso we moved the volume meeting to Wed 16:00 utc18:11
DuncanTI missed the meeting yesterday unfortunately18:11
jgriffithyo18:11
DuncanTI saw the logs18:11
jgriffithDuncanT: or lack thereof :)18:11
DuncanTI didn't get an email about the change though - is there some list I'm not on?18:11
rnirmalit was sent to the openstack list18:11
DuncanTOh, I just missed itthen :-(18:12
DuncanTI'll be there next week anyway... maybe a colleague or two as well18:12
rnirmalthat's great... we really need more participation in cinder :)18:13
DuncanTActually starting to do some work on cinder today18:13
jgriffithDuncanT: do tell?18:13
*** dendrobates is now known as dendro-afk18:13
DuncanTJust trying to port our driver to it... we never got the essex port finished so there are a few tweaks18:14
*** dprince has joined #openstack-meeting18:14
DuncanTCurrently I'm failing to understand keystone, but I've nearly hacked enough code out not to need it18:14
*** winston-d has left #openstack-meeting18:15
DuncanTHopefully tomorrow I'll have enough working to start trying to plumb it into nova18:15
jgriffithI gotta run, but I'll leave this to rnirmal :)18:16
*** edygarcia has quit IRC18:16
rnirmalDuncanT: are you talking about a volume driver.. why does it need keystone?18:17
DuncanTrnirmal: python-cinder-client needs an auth-url it seems?18:18
rnirmalah the client yes18:18
DuncanTEven if the cinder server is running no-auth18:18
rnirmalyeah that's kinda hard linked in the client18:18
*** anderstj has joined #openstack-meeting18:19
DuncanTI've hacked out most of the auth code in the client and seem to be getting somewhere... I'll revisit keystone shortly18:19
*** edygarcia has joined #openstack-meeting18:19
rnirmalok cool.. ping me if you have any questions or are blocked18:20
DuncanTCheers, will do18:20
*** s0mik has quit IRC18:23
*** s0mik has joined #openstack-meeting18:24
*** edygarcia_ has joined #openstack-meeting18:25
*** dwcramer has joined #openstack-meeting18:26
*** bencherian has joined #openstack-meeting18:28
*** darraghb has quit IRC18:29
*** edygarcia has quit IRC18:29
*** edygarcia_ is now known as edygarcia18:29
*** edygarcia_ has joined #openstack-meeting18:32
*** edygarcia has quit IRC18:35
*** edygarcia_ is now known as edygarcia18:35
*** Mandell has joined #openstack-meeting18:38
*** Mandell has quit IRC18:38
*** novas0x2a|laptop has joined #openstack-meeting18:38
*** Mandell has joined #openstack-meeting18:39
*** asdfasdf has joined #openstack-meeting18:42
*** edygarcia has quit IRC18:42
*** jgriffith has quit IRC18:43
*** nati has quit IRC18:44
*** jakedahn is now known as jakedahn_zz18:48
*** dhellmann has joined #openstack-meeting18:49
*** jgriffith has joined #openstack-meeting18:51
*** oubiwann1 has joined #openstack-meeting18:53
*** markmcclain has joined #openstack-meeting18:55
*** edygarcia has joined #openstack-meeting19:00
*** dprince has quit IRC19:03
*** semyazz has left #openstack-meeting19:05
*** dwcramer has quit IRC19:05
*** dwcramer has joined #openstack-meeting19:05
*** zul has quit IRC19:06
*** bencherian has quit IRC19:07
*** bencherian has joined #openstack-meeting19:07
*** zul has joined #openstack-meeting19:12
*** littleidea has quit IRC19:14
*** maoy has joined #openstack-meeting19:15
*** dendro-afk is now known as dendrobates19:22
*** edygarcia_ has joined #openstack-meeting19:22
*** danwent has joined #openstack-meeting19:23
*** edygarcia has quit IRC19:25
*** dendrobates is now known as dendro-afk19:26
*** edygarcia_ has quit IRC19:28
*** edygarcia has joined #openstack-meeting19:30
*** dprince has joined #openstack-meeting19:36
*** edygarcia has quit IRC19:36
*** dwcramer has quit IRC19:36
*** jakedahn_zz is now known as jakedahn19:42
*** littleidea has joined #openstack-meeting19:43
*** zul has quit IRC19:45
*** Amw3000 has quit IRC19:45
*** rnirmal has quit IRC20:00
*** n0ano has joined #openstack-meeting20:01
*** Gordonz has quit IRC20:01
*** liemmn has joined #openstack-meeting20:02
*** liemmn has quit IRC20:03
*** liemmn has joined #openstack-meeting20:04
n0anoanyone here for the orchestration meeting?20:07
maoyhey n0ano20:07
n0anomaoy, salud20:08
maoynot much to say. waiting for some feedback on my proposals..20:09
n0anonot much from me, I skimmed your proposal (I've been swamped trying to push a patch) but I didn't see anything problems with it.20:11
maoythat's good to hear20:11
maoyhopefully next week there will be some code with it too..20:11
*** nati_ueno has quit IRC20:17
*** edygarcia has joined #openstack-meeting20:18
*** edygarcia_ has joined #openstack-meeting20:19
*** edygarcia__ has joined #openstack-meeting20:20
*** edygarcia has quit IRC20:22
*** edygarcia__ is now known as edygarcia20:23
*** edygarcia_ has quit IRC20:24
*** jgriffith has quit IRC20:25
*** asdfasdf has quit IRC20:25
*** edygarcia_ has joined #openstack-meeting20:29
*** edygarcia has quit IRC20:30
*** edygarcia_ is now known as edygarcia20:30
*** jakedahn is now known as jakedahn_zz20:32
*** edygarcia has quit IRC20:36
*** jakedahn_zz is now known as jakedahn20:37
*** ohnoimdead has joined #openstack-meeting20:42
*** dwcramer has joined #openstack-meeting20:45
*** mestery_ has joined #openstack-meeting20:53
*** mestery has quit IRC20:57
*** dtroyer is now known as dtroyer_zzz21:02
*** ohnoimdead has quit IRC21:03
*** ohnoimdead has joined #openstack-meeting21:03
*** edygarcia has joined #openstack-meeting21:04
*** gyee has quit IRC21:08
*** ryanpetrello has joined #openstack-meeting21:15
*** edygarcia has quit IRC21:20
*** nati_ueno has joined #openstack-meeting21:22
*** dwcramer has quit IRC21:22
*** maoy has quit IRC21:35
*** anderstj has quit IRC21:37
*** anderstj has joined #openstack-meeting21:38
*** markvoelker has quit IRC21:40
*** ywu has joined #openstack-meeting21:43
*** mestery has joined #openstack-meeting21:43
*** mestery_ has quit IRC21:46
*** byeager has quit IRC21:49
*** dhellmann has quit IRC21:49
*** ayoung has quit IRC21:50
*** oubiwann1 has quit IRC21:50
*** markmcclain has quit IRC21:51
*** Ravikumar_hp has quit IRC21:51
*** jgriffith has joined #openstack-meeting21:53
*** ryanpetrello has quit IRC22:00
*** blamar has quit IRC22:01
*** nati_uen_ has joined #openstack-meeting22:01
*** dprince has quit IRC22:02
*** nati_ueno has quit IRC22:03
*** jakedahn is now known as jakedahn_zz22:04
*** rafaduran has quit IRC22:10
*** mattray has quit IRC22:14
*** nati_uen_ has quit IRC22:23
*** nati_ueno has joined #openstack-meeting22:24
*** devcamcar has left #openstack-meeting22:24
*** jakedahn_zz is now known as jakedahn22:25
*** nati_uen_ has joined #openstack-meeting22:27
*** nati_ueno has quit IRC22:28
*** Ravikumar_hp has joined #openstack-meeting22:33
*** danwent has quit IRC22:41
*** dtroyer_zzz is now known as dtroyer22:43
*** jakedahn is now known as jakedahn_zz22:49
*** jakedahn_zz is now known as jakedahn22:51
*** dtroyer is now known as dtroyer_zzz22:54
*** anderstj has quit IRC22:55
*** devcamcar has joined #openstack-meeting23:01
*** maoy has joined #openstack-meeting23:05
*** jdurgin has quit IRC23:06
*** adjohn has joined #openstack-meeting23:11
*** ywu has quit IRC23:17
*** ryanpetrello has joined #openstack-meeting23:22
*** Ravikumar_hp has quit IRC23:23
*** danwent has joined #openstack-meeting23:27
*** littleidea has quit IRC23:46
*** jgriffith has quit IRC23:47
*** Mandell_ has joined #openstack-meeting23:48
*** jakedahn is now known as jakedahn_zz23:48
*** Mandell has quit IRC23:50
*** dhellmann has joined #openstack-meeting23:52
*** n0ano has left #openstack-meeting23:53

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