Thursday, 2012-04-26

*** joearnold has quit IRC00:00
*** hggdh has quit IRC00:02
*** novas0x2a|laptop has quit IRC00:07
*** novas0x2a|laptop has joined #openstack-meeting00:07
*** novas0x2a|laptop has quit IRC00:08
*** novas0x2a|laptop has joined #openstack-meeting00:08
*** hggdh has joined #openstack-meeting00:08
*** blamar has joined #openstack-meeting00:11
*** littleidea has joined #openstack-meeting00:14
*** adjohn has quit IRC00:18
*** sandywalsh_ has quit IRC00:24
*** sandywalsh_ has joined #openstack-meeting00:37
*** dachary has joined #openstack-meeting00:41
*** s0mik has quit IRC00:45
*** ayoung has joined #openstack-meeting00:47
*** Yak-n-Yeti has quit IRC00:49
*** ayoung has quit IRC00:52
*** vladimir3p has joined #openstack-meeting00:55
*** vladimir3p has quit IRC01:02
*** littleidea has quit IRC01:09
*** Adri2000 has joined #openstack-meeting01:13
*** fattarsi has quit IRC01:15
*** ryanpetrello has quit IRC01:19
*** fattarsi has joined #openstack-meeting01:23
*** Yak-n-Yeti has joined #openstack-meeting01:28
*** troytoman-away is now known as troytoman01:31
*** adjohn has joined #openstack-meeting01:34
*** ywu has joined #openstack-meeting01:43
*** littleidea has joined #openstack-meeting01:46
*** gyee has quit IRC01:51
*** dcramer_ has joined #openstack-meeting01:56
*** Mandell has quit IRC02:20
*** mdomsch has joined #openstack-meeting02:29
*** dcramer_ has quit IRC02:36
*** Gordonz has joined #openstack-meeting02:41
*** mnewby_ has joined #openstack-meeting02:43
*** mnewby_ has quit IRC02:44
*** mnewby has quit IRC02:46
*** Gordonz has quit IRC02:49
*** novas0x2a|laptop has quit IRC02:53
*** troytoman is now known as troytoman-away02:54
*** jdurgin has quit IRC02:56
*** adjohn has quit IRC03:00
*** ywu has quit IRC03:04
*** ywu has joined #openstack-meeting03:05
*** adjohn has joined #openstack-meeting03:14
*** lloydde has joined #openstack-meeting03:14
*** ywu has quit IRC03:27
*** mnewby has joined #openstack-meeting03:33
*** shang has quit IRC03:41
*** shang has joined #openstack-meeting03:42
*** anderstj has joined #openstack-meeting03:48
*** vladimir3p has joined #openstack-meeting03:52
*** vladimir3p has quit IRC03:57
*** Mandell has joined #openstack-meeting03:57
*** Mandell_ has joined #openstack-meeting04:19
*** Mandell has quit IRC04:19
*** mnewby has quit IRC04:47
*** ravi has joined #openstack-meeting04:48
*** s0mik has joined #openstack-meeting05:04
*** Yak-n-Yeti has quit IRC05:31
*** dtroyer is now known as dtroyer_zzz05:42
*** s0mik has quit IRC05:56
*** littleidea has quit IRC06:00
*** GheAway is now known as GheRivero06:04
*** justinsb has quit IRC06:10
*** justinsb has joined #openstack-meeting06:11
*** Mandell_ has quit IRC06:19
*** anderstj has quit IRC06:29
*** derekh has joined #openstack-meeting08:00
*** ttrifonov is now known as ttrifonov_zZzz08:01
*** ttrifonov_zZzz is now known as ttrifonov08:02
*** darraghb has joined #openstack-meeting08:05
*** ttrifonov is now known as ttrifonov_zZzz08:05
*** ttrifonov_zZzz is now known as ttrifonov08:11
*** GheRivero_ has joined #openstack-meeting08:17
*** Daviey_ has joined #openstack-meeting08:18
*** dendro-afk has quit IRC08:20
*** Daviey has quit IRC08:20
*** GheRivero has quit IRC08:20
*** Daviey_ is now known as Daviey08:20
*** dendro-afk has joined #openstack-meeting08:21
*** mdrnstm has quit IRC08:34
*** jog0_ has joined #openstack-meeting08:34
*** jog0 has quit IRC08:34
*** jog0_ is now known as jog008:34
*** mdrnstm has joined #openstack-meeting08:34
*** Jacky is now known as JackyAlcine08:42
*** JackyAlcine is now known as Jacky08:46
*** ravi has quit IRC09:20
*** Jacky has quit IRC09:34
*** jalcine has joined #openstack-meeting09:35
*** jalcine has quit IRC09:35
*** byeager has quit IRC10:00
*** ravi has joined #openstack-meeting11:18
*** jalcine- has joined #openstack-meeting11:24
*** markvoelker has joined #openstack-meeting11:53
*** blamar has quit IRC12:00
*** dcramer_ has joined #openstack-meeting12:07
*** jalcine- has quit IRC12:15
*** Guest2615 has joined #openstack-meeting12:17
*** jacky has joined #openstack-meeting12:30
*** mdomsch has quit IRC12:30
*** dachary has quit IRC12:32
*** deshantm has joined #openstack-meeting12:35
*** dachary has joined #openstack-meeting12:42
*** blamar has joined #openstack-meeting13:00
*** littleidea has joined #openstack-meeting13:00
*** blamar has quit IRC13:02
*** blamar has joined #openstack-meeting13:03
*** ayoung has joined #openstack-meeting13:05
*** dcramer_ has quit IRC13:06
*** ravi has quit IRC13:08
*** dtroyer_zzz is now known as dtroyer13:14
*** deshantm_ has joined #openstack-meeting13:19
*** deshantm has quit IRC13:21
*** deshantm_ is now known as deshantm13:21
*** dprince has joined #openstack-meeting13:21
*** mdomsch has joined #openstack-meeting13:32
*** Gordonz has joined #openstack-meeting13:34
*** darraghb has quit IRC13:35
*** darraghb has joined #openstack-meeting13:35
*** Gordonz has quit IRC13:36
*** Gordonz has joined #openstack-meeting13:36
*** Yak-n-Yeti has joined #openstack-meeting13:45
*** mattray has joined #openstack-meeting13:49
*** edygarcia has joined #openstack-meeting13:50
*** markmcclain has joined #openstack-meeting13:52
*** dolphm has joined #openstack-meeting13:52
*** dcramer_ has joined #openstack-meeting13:52
*** Yak-n-Yeti has quit IRC13:53
*** AlanClark has joined #openstack-meeting13:57
*** markvoelker has quit IRC13:58
*** littleidea has quit IRC14:01
*** nijaba is now known as nijaba_tab14:12
*** nijaba_tab is now known as nijaba14:13
*** dtroyer is now known as dtroyer_zzz14:24
*** dtroyer_zzz is now known as dtroyer14:27
*** Yak-n-Yeti has joined #openstack-meeting14:28
*** rnirmal has joined #openstack-meeting14:30
*** edygarcia_ has joined #openstack-meeting14:39
*** dtroyer is now known as dtroyer_zzz14:40
*** Yak-n-Yeti has quit IRC14:41
*** Yak-n-Yeti has joined #openstack-meeting14:41
*** edygarcia has quit IRC14:42
*** edygarcia_ is now known as edygarcia14:42
*** dendro-afk is now known as dendrobates14:43
*** dendrobates has joined #openstack-meeting14:43
*** s0mik has joined #openstack-meeting14:44
*** dtroyer_zzz is now known as dtroyer14:52
*** sandywalsh_ has quit IRC14:58
*** s0mik has quit IRC15:01
*** sandywalsh_ has joined #openstack-meeting15:11
*** vladimir3p has joined #openstack-meeting15:14
*** markvoelker has joined #openstack-meeting15:21
*** markmcclain has quit IRC15:24
dacharyHi, http://wiki.openstack.org/Meetings/MeteringAgenda is scheduled in 28 minutes . That will be the first meeting I organize here. Are there any guidelines I should follow ? Thanks in advance :-)15:33
*** markmcclain has joined #openstack-meeting15:37
dhellmanndachary, I know there's a bot but I don't know how to trigger it15:40
notmyname#startmeeting15:41
chmoueldhellmann:  I think #startmeeting15:41
openstackMeeting started Thu Apr 26 15:41:21 2012 UTC.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.15:41
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.15:41
notmyname#endmeeting15:41
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"15:41
openstackMeeting ended Thu Apr 26 15:41:25 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-15.41.html15:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-15.41.txt15:41
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-15.41.log.html15:41
notmynamelike that15:41
dhellmanncool, thanks notmyname15:41
notmynamejust don't forget to endmeeting. only the person who starts it can end it, and no other meetings can start until the current one ends15:42
* dhellmann nods15:44
*** markmcclain has quit IRC15:45
*** lloydde has quit IRC15:50
dacharygreat, notmyname thanks ;-)15:50
dacharyopenstack: help15:51
*** ayoung is now known as ayoung-lunch15:52
*** littleidea has joined #openstack-meeting15:54
dacharychmouel: thanks and bonjour ;-)15:58
dachary#startmeeting16:00
openstackMeeting started Thu Apr 26 16:00:13 2012 UTC.  The chair is dachary. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.16:00
dachary#link http://wiki.openstack.org/Meetings/MeteringAgenda16:00
dacharynijaba: will join later, he is held up by a last minute interview16:01
dachary#topic Agree on the project objectives16:01
*** openstack changes topic to "Agree on the project objectives"16:01
dacharynijaba: proposed "The project aims to deliver a unique point of contact for billing  systems to aquire all counters they need to establish customer billing,  accross all current and future OpenStack components. The delivery of  counters must be tracable and auditable, the counters must be easily  extensible to support new projects, and agents doing data collections  should be independent of the overall system"16:02
dhellmannThat seems like a good start.16:02
dhellmannI'm not sure how the term "counter" is being used, though.16:03
dhellmannFor example, I may want to list on the bill all of the floating IPs a tenant is using, and how long they have had each of them (total and since the last billing cycle).16:03
dhellmannSo just knowing the number of floating IPs isn't enough.16:03
dhellmannIs that part of what you mean for how counters will work?16:03
dacharyI see a counter as "something that is billable" indeed16:04
dhellmannmaybe the floating IP counter measures hours/minutes per IP just as we do for compute for instance?16:04
*** jgriffith has quit IRC16:05
dhellmannI'm just trying to make sure I understand the framing16:05
dacharyfor IPs they tend to have a fixed cost but the cost may vary16:05
dhellmannwell, it's fixed over a period of time, right? so if I allocate one and then deallocate it later, I am only billed for the time I'm actually using it16:05
dacharyyes16:05
*** jgriffith has joined #openstack-meeting16:05
dhellmanngranted a tenant will tend to hold on to an IP for a long period of time16:05
dacharyIf you lease an IP at OVH it's not the same as if you least it from Hetzner for instance16:06
dhellmannsorry, are those providers?16:06
dacharyyes16:06
dhellmanngot it16:06
dhellmannso maybe my objection is just to the definition of that particular counter, and not to the idea of counters in general16:07
dacharyI should say : "someone from whom you lease a number of IP"16:07
dhellmannthat feels like a detail we can work out later16:07
dacharyright16:07
dacharythe level of detail is tricky16:07
dacharyfor instance regarding IPs16:07
dacharyIPv6 transit is free sometimes16:08
*** rnirmal has quit IRC16:08
dacharytherefore, although it's transit external to the OpenStack cluster, you may want to *not* bill it16:08
dacharyand the dinstinction between "extrenal" traffic and "internal" traffic may not be enough16:08
dhellmannthat's an issue for the billing calculation, not the metering, though, right? I may still want to show the customer how much IPv6 traffic they had at $0 so they know how much value they are getting :-)16:09
dacharyin which case you may want to add more counters but that may prove unpractical16:09
*** Aswad_ has joined #openstack-meeting16:09
*** Ravikumar_hp has joined #openstack-meeting16:09
dacharythe metering should provide dinstinctive counters at least. In the proposed table the external network traffic does not distinguish IPv6 and IPv416:10
dhellmannI agree, we need to allow for separate counters for those16:10
dhellmannI assume we will also need to have the counter be per object (per instance, per network, per VIF, etc.) and not global16:11
dacharyThe database schema meeting will be very much about the granularity of these "counters" or whatever agregated value is deemed useful to keep and expose.16:11
dhellmanncool, I can wait for that :-)16:11
dhellmannI don't see anything in the objective statement that I disagree with, then16:11
dacharyok.16:11
dhellmannthe short version is: We are collecting data for another system to use to calculate the bill for a tenant16:12
dhellmannwe aren't going to try to do the actually billing16:12
dacharyThat's also my understanding.16:12
*** s0mik has joined #openstack-meeting16:12
dhellmanngood, we are on the same page, then16:12
dacharyI've read carefully16:12
dachary#link https://lists.launchpad.net/openstack/msg10334.html16:12
dacharyand the part about the existing system in nova16:13
dachary#link http://wiki.openstack.org/SystemUsageData16:13
dacharykept me thinking for a while.16:13
dhellmannI have not had a chance to review that, yet16:13
*** ryanpetrello has joined #openstack-meeting16:14
dacharyIt actually makes the metering implemetation easier because Dragon is apparently willing to store and account for a lot of counters.16:14
dacharySo, instead of harvesting data on its own, the metering agent could query nova on the node itself. And getting the data (I/O for the root device for instance) could be done within the context of nova instead of outside nova.16:15
dacharyDragon made it clear that he wishes other OpenStack components also implement a similar metering logic. But it's not his focus and I don't think there is anything yet in swift.16:16
dhellmannthat seems like a good approach16:16
dhellmannhow much of that is already implemented?16:16
dacharyAnd I did not research what Quantum plans.16:16
dacharythat => http://wiki.openstack.org/SystemUsageData ?16:16
dhellmannyes, sorry16:16
dacharyall of it.16:16
dhellmannoh, wow16:17
dacharyIt's a good source of data.16:17
dhellmannoh, these are events not table definitions16:17
dacharyYes.16:17
dhellmannyeah, so we still need to monitor the events and log them16:17
* dhellmann is reading as we go16:17
chmoueldachary: I think the swiftstack were talking about an integrated version for metering swift (merging syn's https://github.com/pandemicsyn/swift-informant)16:18
dachary#link https://github.com/pandemicsyn/swift-informant16:19
dhellmannyes, this matches what I had been expecting to need to build: something that watches for events and logs them, possibly after post-processing to get data not in the event but needed for billing (like the definition of an instance type) and then a query API on top of it for the tool that extracts the data and aggregates it16:19
dacharychmouel: ok :-)16:20
dacharyAgents running on OpenStack nodes harvest data. The data from the existing agents is collected using a message queue. The data collected is made available thru APIs.16:20
dachary^ this is my onliner to describe the metering architecture.16:20
uvirtbotdachary: Error: "this" is not a valid command.16:20
dachary?16:20
dacharyhahaha I woke up a bot without knowing ;-)16:21
dhellmann:-)16:21
dacharyanyone has a say about the project objectives before we move to the next topic ?16:21
*** jayahn has joined #openstack-meeting16:21
dhellmann+1 to adopt those objectives16:22
dachary+116:22
dachary#topic Agree on a project name16:22
*** openstack changes topic to "Agree on a project name"16:22
dacharyMetering and FillBill are proposed16:23
dhellmannCeilometer16:23
dhellmann(an instrument for measuring cloud cover)16:23
*** nijaba_tab has joined #openstack-meeting16:23
* nijaba_tab waves. sorry for being late16:23
dacharynijaba_tab: we just agreed on project objectives16:24
dacharyand chosing a name16:24
dacharyCeilometer16:24
dacharywas proposed by dhellmann16:24
dacharyI actually like Ceilometer16:24
nijaba_tabgreat, thanks16:24
dhellmannsome other ideas on: http://en.wikipedia.org/wiki/Meteorological_instrumentation16:25
dacharynipper has been proposed on the list but I still prefer Ceilometer16:25
nijaba_tabCeilometer sounds cool16:25
jayahn+1 for ceilometer16:25
dhellmannRadiosondes may be easier to say out loud16:25
dachary+1 for ceilometer16:26
* littleidea wants something without 'meter' in the name16:26
dhellmann"A radiosonde (Sonde is French for probe) is a unit for use in weather balloons that measures various atmospheric parameters and transmits them to a fixed receiver."16:26
Aswad_+1 for ceilometer16:26
dacharylittleidea: when I apt-cache search meter I'd like it to show ;-)16:26
littleideadachary: easily solved16:27
nijaba_tabI had put fillbill on the wiki.... ;)16:27
*** edygarcia_ has joined #openstack-meeting16:27
*** rnirmal has joined #openstack-meeting16:28
dacharyunless there is another proposal shall we vote ?16:28
littleideadoes the name need to be decided in this meeting?16:28
*** joearnold has joined #openstack-meeting16:28
nijaba_tablittleidea: yes, this is blocking us to create the project on lp, have a ml, etc...16:29
dacharylittleidea: that's the idea, yes. And then it will be used to create projects, domains, lists etc.16:29
dhellmannI think the idea is to decide and get to work on implementation, because we need a name before the infrastructure can be set up16:29
dacharyVotes for "Metering" : (say +0 or +1)16:29
dachary+016:29
dhellmann+016:30
littleidea+016:30
jayahn+016:30
*** edygarcia has quit IRC16:30
*** edygarcia_ is now known as edygarcia16:30
Aswad_+016:30
nijaba_tab+016:30
*** jlebrijo has joined #openstack-meeting16:30
dacharyVotes for "FillBill" : (say +0 or +1)16:30
dhellmann+016:30
dachary+016:30
jayahn+016:30
Aswad_+016:30
nijaba_tab+1 just because I proposed it16:30
Aswad_:)16:30
dacharyVotes for "Nipper" : (say +0 or +1)16:31
dachary+016:31
dhellmann+016:31
*** flacoste has joined #openstack-meeting16:31
nijaba_tab+016:31
*** edygarcia_ has joined #openstack-meeting16:31
Aswad_+016:31
jayahn+016:31
dacharyVotes for "Ceilometer" : (say +0 or +1)16:31
dachary+116:31
dhellmann+116:32
Aswad_+116:32
jayahn+116:32
zul+116:32
nijaba_tab+116:32
dhellmannplease also record a +1 for me for "radiosonde" when that comes up, I have to leave.16:32
dacharyk16:32
dacharyVotes for "radiosondes" : (say +0 or +1)16:32
dachary+016:32
dacharydhellmann says : +116:33
Aswad_+016:33
littleidea+116:33
*** mnewby has joined #openstack-meeting16:33
nijaba_tab+016:33
littleideaand remember kids, apt-cache search matches descriptions16:33
nijaba_tabtrue16:34
flacoste+016:34
dacharylittleidea: yes but *many* descriptions match meter ;-)16:34
jayahn+116:34
littleideadachary: your point is searching for meter is useless anyway?16:34
*** edygarcia has quit IRC16:34
*** edygarcia_ is now known as edygarcia16:34
dacharyThat's all I have. We have a winner I think : "ceilometer".16:35
mnewbyapologies, what is being named?16:35
dacharymnewby: http://wiki.openstack.org/Meetings/MeteringAgenda16:35
littleideaa project to meter openstack services16:35
mnewbydanke :)16:35
Aswad_danke!16:36
dacharyUnless someone objects, I'll move on to the next topic.16:36
dachary#topic Agree on a project decision roadmap16:36
*** openstack changes topic to "Agree on a project decision roadmap"16:37
nijaba_tabyay for ceilometer16:37
*** edygarcia_ has joined #openstack-meeting16:37
nijaba_tabso loic and I made a proposal for this on the agenda16:37
nijaba_tabloic=dachary16:38
nijaba_tabI think these decision are a bit fundamental for the project, so I think having a week to consider each one is not too much16:38
nijaba_tabwhat do you think?16:39
* nijaba_tab blames 3G for the lag16:39
flacostewhere will discussion around these happens?16:39
flacosteon a mailing list, or on IRC during themeeting?16:39
flacostewould probably be good to discuss on a list before the meeting, no?16:40
nijaba_tabon the ml, during the week before the meeting, then validation on irc meeting?16:40
*** edygarcia has quit IRC16:40
dacharyIt would make sense to discuss before the meeting, I think.16:40
dacharyflacoste: so that the meeting is not about thinking of solutions but validating the solutions already proposed. Come to an understanding based on the work done during the week.16:41
flacosteagreed16:41
flacostewhere would that happen? the general openstack list? or a openstack-metering list?16:41
*** edygarcia_ has quit IRC16:41
nijaba_tabopenstack-ceilometer list16:42
dacharyI'd be tempted to start on the general mailing list because a *lot* of people have shown interest in the topic.16:42
nijaba_tablet's cross post at the beginning?16:42
dacharyok16:42
dacharyso that it can move to the specialized list of it's too much spam.16:43
nijaba_tab+1 for me16:43
dacharyHowever, these discussions are time boxed. 5 topics. 5 weeks.16:43
nijaba_tabyes!16:43
dacharyAfter that all is decided. It's a fairly simple project. Which is what I like about it ;-)16:43
nijaba_tabthe first one, for the next meeting, is which db to use16:43
jayahn(sorry if i miss this kind of discussion on the beginnig. but..) in the decision roadmap, i would like to see a kind of requirment gathering about what to count, especially for network traffic metering.16:44
nijaba_tabsimple, until you hit production16:44
littleideaI think it should be on the main list16:44
*** edygarcia has joined #openstack-meeting16:44
jayahni agree that it should be on the main list.16:44
dacharyjayahn: agree and I think that's part of the "schema choice".16:45
*** Gordonz_ has joined #openstack-meeting16:45
jayahni see.16:45
dacharys/agree/agreed/16:45
dacharyit's the most difficult part in my opinion16:45
*** donaldngo_hp has joined #openstack-meeting16:45
dacharydecided what to account for, what to aggregate or not.16:45
littleideadoes it have to be tied to a db?16:46
nijaba_tabjayahn, there is a proposal on the blueprint.  Feel free to add to it16:46
nijaba_tabon of the main idea is that we do not lock on counters, but on data model16:46
nijaba_tabso that anyone can add an agent to gather another counter that was not part of the original plan16:46
nijaba_taband each counter gathering is optional16:46
nijaba_tabthe schema should be flexible enough not to prevent adding counters16:47
dacharynijaba_tab: while this is an open ended definition, metering will define counters by default (the one in the table for instance). I think the core of the discussion will be about these counters.16:47
nijaba_tabok, let's get back on topic.  We have 3 proposal for discussion to take place16:48
dacharyThe default list of counters should be useful to most people and make sense to most usages. It's key to have a consensus on using the metering API.16:48
*** Gordonz has quit IRC16:48
*** markmcclain has joined #openstack-meeting16:49
*** jkoelker has quit IRC16:49
*** edygarcia has quit IRC16:49
dacharyI propose that we modify "Schema choice" for "Schema choice and counter definitions"16:49
nijaba_tab1/On the main mailing list16:49
nijaba_tab2/ on the ceilometer one16:49
nijaba_tab3/on both using cross posting16:49
nijaba_tabWho votes for 1?16:49
*** edygarcia has joined #openstack-meeting16:49
flacoste+116:49
littleidea116:49
jayahn116:49
dachary316:50
Aswad_116:50
*** ayoung-lunch is now known as ayoung16:50
dacharyI'll handle the votes because nijaba_tab lags ;-)16:50
*** edygarcia_ has joined #openstack-meeting16:50
* nijaba_tab does lagg badly16:51
*** jkoelker has joined #openstack-meeting16:51
nijaba_tabthanks dachary16:51
*** vladimir3p has quit IRC16:51
flacostedachary: i like your proposal (adding counter definitions to the schema topic)16:51
flacostedachary: but i think we should do that one before commiting to a database16:51
dachary#agreed discussions are On the main mailing list16:51
* nijaba_tab votes for 316:51
jayahni also like adding counter definitions to the schema.16:51
flacosteas the schema and counters we need is more likely to inform the db choice16:52
*** vladimir3p has joined #openstack-meeting16:52
flacostethen limiting our schema based on the db16:52
flacostes/then/rather than/16:52
dacharyflacoste: yes16:52
nijaba_tabSo the proposal is to a/ change the order between 1 and 2, b) to add counters to shcema.  works for me16:52
dachary#agreed meeting 2 is : Schema choice and counter definitions16:53
dacharymeeting 3 message queue choice16:53
*** dwalleck has joined #openstack-meeting16:54
flacosteor meeting 3 database choice?16:54
dacharyit's about chosing AMQP over RabbitMQ over ... etc16:54
*** edygarcia has quit IRC16:54
*** edygarcia_ is now known as edygarcia16:54
dacharyflacoste: I'm confused ? Meeting 1 is database choice or did I miss something ?16:55
littleideadachary: RabbitMQ is an implementation of AMQP16:55
nijaba_tabdachary: we should invert 1 and 216:55
dacharyok16:55
flacosteah, i was counting from this current meeting, but i guess we are using 0, traditional off by one error :-)16:56
dachary:-D16:56
dacharyI agree that database choice should come after16:56
dacharylittleidea: right ... :-D16:56
nijaba_tabso that we know th schema before choosing the db16:57
nijaba_tabc vs pascal...16:57
jayahndoes openstack already have16:57
jayahn.. oops.. mistyping.16:57
littleideaWhy do we need to choose a DB?16:57
*** Gordonz_ has quit IRC16:57
dacharylittleidea: we need to chose a storage system, definitely16:58
nijaba_tablittleidea: because of the massive amount of data we are going to collect16:58
*** Gordonz has joined #openstack-meeting16:58
littleideaseems like what we should define is a service interface and mechanisms for gathering the information16:58
flacostelittleidea: maybe the storage should be pluggable, but let's save that for the DB discussion :-)16:58
dacharyCurrent state: 1 schema and counter definitions, 2 storage system, 3 message queue choice, 4 API message format, 5, external API definition16:58
littleideanijaba_tab: then clearly the db should be cassandra16:58
dacharyflacoste: ok16:58
*** edygarcia_ has joined #openstack-meeting16:59
dacharylittleidea: I think that's exactly what the second meeting should be about, indeed ;-)16:59
nijaba_tabyes, but we could be limited by the type of db, so the reference implementation choice does matter16:59
*** mattray has quit IRC16:59
flacostedachary: does it make sense to discuss 4 and 5 after 1? because again, the message queue and storage might restrict these?16:59
dacharyCurrent state: 1 schema and counter definitions, 2 chose a plugable storage system, 3 message queue choice, 4 API message format, 5, external API definition16:59
* dachary thinking17:00
jaypipesdachary, LinuxJed, nijaba_tab: heya, the QA meeting starts now... in this channel :)17:00
flacostewe overran17:00
littleideato the extent schema is about defining the data we want to collect, that seems right, if schema is about creating tables in a relational model, I think we're going about this the wrong way17:00
*** mattray has joined #openstack-meeting17:00
jaypipesflacoste: no big deal :)17:00
LinuxJedijaypipes: ??17:00
vladimir3pjaypipes: I thought that we have a volume meeting at 10am PST17:00
*** mattray has quit IRC17:00
dacharyjaypipes: we'll cut short sorry about that17:00
*** edygarcia_ has quit IRC17:01
*** edygarcia has quit IRC17:01
dachary#endmeeting17:01
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"17:01
openstackMeeting ended Thu Apr 26 17:01:07 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-16.00.html17:01
nijaba_tabflacoste: good point on the order again17:01
* nijaba_tab wonders if there is another meeting taking place in here now17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-16.00.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-16.00.log.html17:01
jayahni agree with littleidea.17:01
flacostedachary: should we finish in #openstack-metering? or postpone to the next meeting17:01
*** edygarcia has joined #openstack-meeting17:01
*** mattray has joined #openstack-meeting17:01
jaypipesvladimir3p: http://wiki.openstack.org/Meetings17:01
jaypipesvladimir3p: now is 1700 UTC, yes?17:01
nijaba_tablet's move to -metering17:01
dacharyyep17:01
*** jakedahn_zz is now known as jakedahn17:02
Aswad_ok17:02
jaypipesvladimir3p: looks like Volumes is in 58 minutes. :)17:02
vladimir3pjaypipes: ok, sorry17:02
vladimir3pok17:02
jaypipesvladimir3p: no worries!17:02
jaypipesalright.. let's get this show on the road.17:02
jaypipes#startmeeting17:02
openstackMeeting started Thu Apr 26 17:02:55 2012 UTC.  The chair is jaypipes. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.17:02
davidkranzYo17:03
jaypipesdwalleck, davidkranz, fattarsi: afternoon!17:03
Ravikumar_hphi17:03
dwalleckhello!17:03
fattarsigood morning :)17:03
jaypipesRavikumar_hp: helolo!17:03
jaypipesRavikumar_hp: or Hello even :)17:03
jaypipesdwalleck: is Jose around?17:03
dwalleckhelolololololo :)17:03
jaypipesdwalleck: I know Nayna was interested in the status of the Swift tests...17:04
dwalleckjaypipes: I haven't seen him today. He might be out17:04
Ravikumar_hpJaypipes: Yes .17:04
dwalleckAs am I....I will ping his group17:04
jaypipesdwalleck: ok, if you could give yourself a quick action item to email Jose and Nayna about that?17:04
jaypipesdwalleck: cheers17:04
Ravikumar_hpJaypipes: we have only Nova tests , and keystone being added17:04
jaypipesRavikumar_hp: and Images API tests...17:04
dwalleckI know they were doing some major refactoring to be able to push a bunch of stuff at once, but just getting some basics in would be nice :)17:04
jaypipesdwalleck: indeed :)17:05
*** Mandell has joined #openstack-meeting17:05
dwalleckAnd Quantum (when I fix Jay's nits)17:05
fattarsidwalleck: thanks for the feedback on that review, I will do those changes today or tomorrow17:05
jaypipes#link https://jenkins.openstack.org/job/dev-gate-tempest-devstack-vm/337/testReport/?17:05
dwalleckfattarsi: awesome, sounds good17:05
jaypipesPlease see the above Jenkins report output. and thx to jeblair for putting the report together.17:05
dwalleckWooo!17:06
jaypipesWe have the Tempest devstack gate job running smoothly now. w00t.17:06
*** adjohn has joined #openstack-meeting17:06
jaypipesBut the two failures shown in the report are indeed consistent. I am working on fixing the volume one today.17:06
jaypipesThere is a bug logged about it already: https://bugs.launchpad.net/tempest/+bug/98385617:07
uvirtbotLaunchpad bug 983856 in tempest "volumes are not deleted in teardown" [High,In progress]17:07
jaypipesLooks like Sarad Patel has a code review up for it...17:07
*** rnirmal_ has joined #openstack-meeting17:07
* jaypipes will be focusing on outstanding tempest reviews today.17:08
jaypipesand also cleaning up our bug list, which is in some need of TLC17:08
*** rnirmal has quit IRC17:08
*** rnirmal_ is now known as rnirmal17:08
jaypipesdavidkranz: I'd like to also add a Jenkins job that fires the stress tests17:08
jaypipesdavidkranz: perhaps you and I could work on that late today or tomorrow?17:08
davidkranzjaypipes: OK. I am also working on more stress cases for floating ip, volume, etc.17:09
jaypipesdavidkranz: nice17:09
*** flacoste has left #openstack-meeting17:09
jaypipesdwalleck: so do you think you will have the base compute merge proposal done roday?17:09
davidkranzjaypipes: Is there some specific action you were thinking of to do with jenkins?17:09
jaypipesdavidkranz: I'd like to fire a job similar to the devstack tempest gate, but run the stress tests instead of the tempest API tests17:10
jaypipesdavidkranz: basic stress tests that are in tempest right now.... create/delete, reboot/resize, etc17:10
dwalleckjaypipes: I thought it was done....let me go back and look17:10
*** derekh has quit IRC17:11
*** lloydde has joined #openstack-meeting17:11
davidkranzjaypipes: Makes sense, but I am not sure where that code lives. Were you thinking I should check something in?17:11
jaypipesdwalleck: yes, it is, but we need more reviews...17:11
jaypipesRavikumar_hp, davidkranz: think you can review this one? https://review.openstack.org/#/c/5258/17:11
Ravikumar_hpjaypipes: ok17:12
jaypipesdavidkranz: no, I can do the jenkins stuff... just might want to chat with you a few minutes about how to fire off the stress tests and make sure everything gets cleaned up17:12
dwalleckjaypipes: gotcha. I'm trying to poke some of my Nova devs to chime in as well. westmaas and dprince are folks who probably have interest in what we're doing17:12
davidkranzRavikumar_hp: Are you going to pull the change and run it?17:12
jaypipesdwalleck: ++17:12
davidkranzjaypipes: OK, I will be here.17:13
jaypipesdavidkranz: I have already run that merge proposal locally and all is passing (except the known volume one)17:13
davidkranzjaypipes: Greast.17:13
Ravikumar_hp<davidkranz: yes.17:13
jaypipesall: I would *like* to get to the point by end of day that the devstack-tempest-gate-vm job is actually GATING the tempest trunk.17:13
jaypipesdoesn't have to gate the other core projects yet, but I'd like it to gate tempest.17:14
jaypipesmeaning that we wouldn't have to run everyone's branches locally first... since that would be gating anything going into trunk17:14
davidkranzjaypipes: That would be great and would take some effort off of some reviews.17:14
jaypipesdavidkranz: right.17:14
jaypipesdavidkranz: Which means getting those two remaining failures addressed...17:15
jaypipesdavidkranz: which I can certainly get done today.17:15
davidkranzCool!17:15
jaypipesalrighty... does anyone have anything specific to bring up? fattarsi, how's things going with your outstadning merge proposals?17:16
davidkranzjaypipes: Where is the jenkins code you are going to change? I would at least like to take a look at how that stuff works going forward.17:16
jaypipesfattarsi: last I checked we were pretty close with yours..17:16
*** Amw3000 has joined #openstack-meeting17:17
jaypipesdavidkranz: there's two parts. the first is the tools/configure_tempest.sh in the devstack project. the second is the devstack-gate project that is part of openstack-ci.17:17
fattarsiyes, I will incorporate the feedback and resubmit17:17
jaypipesfattarsi: awesome. love to get that in this week.17:17
davidkranzjaypipes: OK, thanks.17:17
jaypipesdavidkranz: https://github.com/openstack-ci/devstack-gate17:17
fattarsijaypipes: me too, I'd like to submit the keystone tests I have early next week17:18
jaypipesdavidkranz: and specifically: https://github.com/openstack-ci/devstack-gate/blob/4acf48ba874a5dee6d6548a2e2cc62ec868d6216/devstack-vm-gate-host.sh17:18
jaypipesfattarsi: rock on.17:18
*** nijaba_tab has quit IRC17:18
davidkranzjaypipes: Were you thinking of running stress tests against devstack?17:19
jaypipesdavidkranz: yes.17:19
jaypipesdavidkranz: you think that is a mistake?17:19
davidkranzjaypipes: Then we need to configure devstack so the stress tests can access the log files.17:19
davidkranzjaypipes: Not a mistake, but needs a little more work.17:20
jaypipesdavidkranz: OK, that's exactly the kind of feedback I needed from ya :)17:20
jaypipesdavidkranz: I'll ping you when ready to get going on that (want to get the tempest gate in place first)17:20
davidkranzjaypipes: k17:20
jaypipesAlso, all, please be sure to go through the list of abandoned merge proposals: https://review.openstack.org/#/q/status:abandoned+project:openstack/tempest,n,z17:21
jaypipesespecially after last week when so many in SFO17:21
jaypipesjust skim and make sure nothing important is abandoned...17:21
dwalleckwill do17:21
jaypipesI believe I contacted everyone with an abandoned branch needing restored, but just doubel-check17:21
jaypipes#topic Open Discussion17:22
*** openstack changes topic to "Open Discussion"17:22
jaypipesFeel free to discuss what's on your mind :)17:22
dwallecksleep :)17:22
*** littleidea has quit IRC17:22
jaypipeslol :)17:22
jaypipesAn AWESOME article from Sagar Nikam on running tempest inside devstack on TryStack: http://sagar-tech-gyan.blogspot.in/2012/04/testing-open-stack-with-devstack.html17:23
jaypipesit's a yo dawg within a yo dawg.17:23
dwalleckNo, just hoping to get some of my branches in so that I can push more of the Linux server validation/SSH code soon. We also have a good working Windows solution now as well, for those few folks who need it17:23
*** Aswad_ has left #openstack-meeting17:23
dwalleckHehe, I always blow people's minds when I show them Devstack running on a Cloud Server17:23
jaypipesdwalleck: :) then let's get those outstanding merges in, eh? :)17:24
dwalleckworking on it! :)17:24
jaypipesdwalleck: alright, before we break here, I know that a number of people were interested in having both a published agenda and a summary of the meeting/decisions put on the main mailing list.17:25
jaypipesdwalleck: I was hoping that between us all, we can split up that work and get into a regular cadence of communications17:25
*** anderstj has joined #openstack-meeting17:25
dwalleckjaypipes: ++ sounds like a good idea17:25
davidkranzGreat idea.17:25
jaypipesdwalleck, davidkranz, Ravikumar_hp: would you all be willing to do some sort of weekly rotation for that?17:26
dwalleckWhat would work best for this? Wiki page? Etherpad?17:26
dwalleckabsolutely17:26
jaypipesdwalleck: we can put the rotation on a wiki page like nove-core does for reviews...17:26
Ravikumar_hpsure17:26
davidkranzSure17:26
jaypipeshttp://wiki.openstack.org/Nova/ReviewDays17:27
jaypipessomething like that ^^17:27
dwalleckThat works17:27
jaypipesbut we'd be responsible for posting the agenda ahead of time and posting a summary the meeting and, say, outstadning pending reviews?17:27
davidkranzjaypipes: Did you mean the main "openstack" list or the qa list?17:28
*** gyee has joined #openstack-meeting17:28
jaypipesdavidkranz: main list17:29
jaypipesdavidkranz: though you could do both! :)17:29
jaypipesI'll do the first summary right now and put togther the schedule page...17:29
jaypipesI think it will be good to communicate more and better with the community about stuff we've been able to get done and things we need assistance with, etc17:30
dwalleckjaypipes: ++17:30
davidkranzThanks Jay. I can do one of the next two weeks but will be on vacation May14 through Memorial day.17:30
*** littleidea has joined #openstack-meeting17:30
jaypipesdavidkranz: good to know. I'll note that17:30
jaypipesalright guys! well, gonna end this if noone has anything else?17:31
davidkranzAdios.17:31
Ravikumar_hpbye17:31
jaypipesciao17:31
dwalleckthanks!17:31
jaypipes#endmeeting17:31
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"17:31
fattarsisee ya17:31
openstackMeeting ended Thu Apr 26 17:31:38 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-17.02.html17:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-17.02.txt17:31
*** dwalleck has quit IRC17:31
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-17.02.log.html17:31
*** jayahn has quit IRC17:32
*** jlebrijo has quit IRC17:34
*** donaldngo_hp has quit IRC17:35
*** adjohn has quit IRC17:37
*** adjohn has joined #openstack-meeting17:37
*** jdurgin has joined #openstack-meeting17:44
*** gyee has quit IRC17:49
*** rnirmal has quit IRC17:49
*** rnirmal has joined #openstack-meeting17:50
*** lloydde has quit IRC17:54
*** s0mik has quit IRC18:00
*** edygarcia_ has joined #openstack-meeting18:00
jgriffith#startmeeting18:02
openstackMeeting started Thu Apr 26 18:02:16 2012 UTC.  The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.18:02
jgriffithWho do we have for volume/cinder folks?18:02
*** dcramer_ has quit IRC18:02
vladimir3phere18:02
vladimir3phi18:02
rnirmalhey18:03
jdurginhowdy18:03
jgriffithexcellent...18:03
*** edygarcia has quit IRC18:03
*** edygarcia_ is now known as edygarcia18:03
jgriffithesker: you here?18:03
rnirmaljgriffith: great job getting all the project setup kicked off18:03
*** jbrogan has joined #openstack-meeting18:03
jgriffithrnirmal: thanks to you!!  I just followed your lead :)18:04
jgriffithOk... renuka is on vacation today so won't be here18:04
jgriffithWe should probably get started18:04
jgriffith#topic cinder update18:04
*** openstack changes topic to "cinder update"18:05
jgriffithSo, as nirmal pointed out we now have an official project in the openstack ecosystem  :)18:05
rnirmalhttps://launchpad.net/cinder18:05
vladimir3pcongrats!18:05
jgriffithI've added everybody that "volunteered" at the summit to the core team18:05
rnirmaland https://github.com/openstack/cinder18:06
jgriffithrnirmal: Thanks, I forget not everybody has seen all of those yet probably18:06
rnirmalhttps://launchpad.net/~cinder-core18:06
rnirmalyeah that's why I'm pasting those links here18:06
jgriffith:)18:06
rnirmalso anybody looking at the mins will have it18:06
jgriffithrnirmal: Excellent, THANKS!!18:07
jgriffithSo I believe as far as drivers team I'll have to figure out what we need to do there, elections etc18:07
jgriffithOr something else, just don't know.18:08
jgriffithBut....18:08
jgriffithIn the meantime, we have a repo18:08
jgriffithI don't know if anybody has had a chance to look at the break out I started:18:08
rnirmalhow abt cinder-bugs. should that be a moderated list?18:08
jgriffithhttps://github.com/j-griffith/cinder18:08
rnirmalsorry just wanted to complete that disucssion https://launchpad.net/~cinder-bugs18:09
jgriffithrnirmal: NP..18:09
jgriffithI believe that's typically moderated because of ranking/acceptance etc18:09
jgriffithI'll double check on those sorts of details and get things set up correctly18:09
rnirmalah ok just making sure.18:09
vladimir3prnirmal: is there any reason to make it moderated18:09
vladimir3pI'm fine with it either way18:10
rnirmalnot really for the bugs.. not sure if that's used for triaging etc.. but anyone should be able to do that18:10
jgriffithrnirmal vladimir3p: Give me a chance to figure out how it's "supposed" to be done and we can go from there18:10
vladimir3pgood, seems like you have your 1st action item18:10
jgriffith#action jgriffith figure out memeberships for various project pages18:10
jgriffithSo the next steps are getting some code going in the repo18:11
vladimir3pI would suggest 1st to understand what modules we would like to put there18:12
vladimir3pand how to re-use common parts18:12
vladimir3pthings like wsgi, etc.18:12
vladimir3punfortunately, there is no really nova-common today, correct?18:12
jgriffithvladimir3p: yes... that's covered18:12
rnirmalvladimir3p: there is a nova-common18:12
rnirmaland some of the wsgi stuff is already in there18:13
jgriffithvladimir3p: we're actually using openstack-common18:13
vladimir3plink?18:13
rnirmalsorry openstack-common18:13
rnirmalhttps://github.com/openstack/openstack-common18:13
jgriffithIt's in the repo already, that's what's cool about jeblairs project setup18:13
jgriffithWe actually have a framework18:13
jgriffithThe code in my personal repo https://github.com/j-griffith/cinder followed the same process18:14
vladimir3pvery good18:14
jgriffithI added more components to my config but don't know if they're all needed or not18:14
rnirmalsoren: jgriffith how are we going to move that code in the official repo18:14
jgriffithSo things like wsgi, some of the test infrastructure, utils etc we have18:14
jgriffithrnirmal: So I'm planning to do a commit and submit for review... at least the framework18:15
rnirmalgreat and we can slowly start moving in the pieces18:15
jgriffithI've put together some "stripped down" versions of things together to get a foundation that can work and run tests18:15
jgriffithrnirmal: exactly18:15
jgriffithThe only thing is I would like to get folks to at least take a brief look at what I have in my github before pushing to the official repo18:16
jgriffithI'd like to avoid having to make MAJOR changes to the layout or anything after we've got it in Gerrit and such18:16
jgriffithI probably need to take another turn on it this week but my goal is to have it up in the official repo this week-end18:17
jgriffithUnless folks are anxious to start writing some code before then :)18:17
vladimir3pok, a quick question - seems like I'm missing scheduler part18:17
jgriffithvladimir3p: in terms of what I have in my repo?  Yes, correct it's by NO means complete18:18
*** edygarcia_ has joined #openstack-meeting18:18
jgriffithThe idea was to get a minimal DB, Test infrastructure etc18:18
vladimir3pyep, justa placeholder will be great18:18
vladimir3plet's put there something like a simple or random scheduler18:18
jgriffithWhat I'd really like is some feedback on what I did with the drivers directory versus plugins etc18:19
*** edygarcia has quit IRC18:19
*** edygarcia_ is now known as edygarcia18:19
rnirmalyeah lets start with basic stubs.. easier to get things rolling18:19
jgriffithvladimir3p: random scheduler is fine with me.  Or even just an empty file18:19
jgriffith#action add scheduler stub before pushing to official repo18:19
*** edygarcia_ has joined #openstack-meeting18:20
jgriffith#idea I'll give folks a couple days to take a look at what's there, feel free to email suggestions, submit somehting of your own etc18:20
vladimir3pagree18:20
vladimir3pso, let's see what do we have and what we are missing ...18:20
jgriffithThen I'll try to get our first submission pushed in this week-end18:20
jgriffithMissing lots of stuff :)18:21
rnirmalsounds good.. yeah don't worry about the missing stuff18:21
vladimir3pI was thinking about cinder API (rest) level, volume APIs, DB, scheduler manager with drivers18:21
jgriffithSome things I'd like to consider before talking about missing stuff18:21
rnirmalas long as it has a basic api + service running18:21
vladimir3pthese seems to be main parts18:21
jgriffithrnirmal: +118:21
rnirmaland the framework for running the tests18:21
jgriffithrnirmal: +++++++++++118:21
jgriffith:)18:21
vladimir3p:-)18:21
jgriffithOk, so something else we need to talk about is flushing out the endpoint definitions18:22
jgriffithOr the api interface, however you want to look at it18:22
*** dolphm has quit IRC18:22
rnirmalI think it would be great to get a blueprint out for the api18:22
rnirmaland start by adding the existing definitions and refine on those18:22
*** edygarcia__ has joined #openstack-meeting18:23
jgriffithrnirmal: Agree, also might be helpful to leverage the work Vish did on the python-cinder-client18:23
jgriffith#link https://github.com/vishvananda/python-cinderclient.git18:23
*** edygarcia has quit IRC18:23
*** edygarcia__ is now known as edygarcia18:23
jgriffithWe should keep in mind that our first goal is to offer a functional equivalent to the existing nova-volume api18:23
vladimir3pjgriffith: what is the plan about plug-ins. How do you plan to use them?18:24
*** edygarcia_ has quit IRC18:24
jgriffithvladimir3p: The idea is this to behave sort of like what we do with extensions18:25
vladimir3pso, those will be API extensions?18:25
jgriffithI'm modeling more what quantum is doing here.18:25
jgriffithYes, with potential for other things in the future as well18:25
vladimir3psorry, not familiar with qunatum stuff18:25
rnirmalthis should be similar to the nova extensions too18:26
vladimir3pbecause if we are talking about just API extensions (a-la nova), it would be great to reuse their code18:26
vladimir3p(put it in common)18:26
rnirmalthere was a session on the extensions.. not sure what happened. there18:26
jgriffithAPI extensions wouldn't be common though...18:27
rnirmalI think common already has it18:27
jgriffithrnirmal: Yeah, I didn't make that session but I can track down folks and get mor einfo18:27
*** edygarcia_ has joined #openstack-meeting18:27
rnirmalhttps://github.com/openstack/openstack-common/blob/master/openstack/common/extensions.py ... we'll have to figure out what else is needed here.18:28
vladimir3pok, so the main comment on your branch - great stuff!!! If we could use openstack-common modules instead of what is there in common it will be even better18:28
rnirmalI'll be able to help setup the extensions part.. we just did that for reddwarf18:28
rnirmalusing openstack-common18:28
vladimir3pgreat!18:28
rnirmalvladimir3p: part of it will also be actually getting stuff into common18:29
jgriffithrnirmal: excellent18:29
vladimir3phow about volume types?18:29
vladimir3pif we are talking about volume separation - cut is pretty clear.18:29
jgriffith#action rnirmal look at setting up extension framework in new codebase18:29
vladimir3pnova knows only about volume uuid18:29
vladimir3pbut with volume types it is different ...18:29
rnirmalwouldn't just cinder need to know about volume types?18:30
vladimir3pfor sure management of all volume types (+extra specs for types) should be within cinder18:30
vladimir3pnova should also somehow be aware of them ...18:30
jgriffithvladimir3p: Yes there's going to be work in both nova and cinder to get all of this coordinated18:30
*** edygarcia__ has joined #openstack-meeting18:31
*** edygarcia__ has left #openstack-meeting18:31
jgriffithIt seems to me that maybe getting things somewhat structured in cinder then patching nova is the way to go about it18:31
*** edygarcia has quit IRC18:31
*** jog0 has left #openstack-meeting18:31
vladimir3pagree18:31
jgriffithAnybody have any concerns/disagreements?18:32
jgriffithWell, I'm sure we all have a few concerns  :)18:32
*** jakedahn is now known as jakedahn_zz18:32
*** dendrobates is now known as dendro-afk18:32
vladimir3pno concerns, only working items :-)18:32
jgriffithvladimir3p: So that brings me to the next point....18:33
*** edygarcia__ has joined #openstack-meeting18:33
jgriffithSounds like rnirmal is interested in looking at the extensions piece since he's already done a good bit of work there18:33
jgriffithAnybody have interests in starting to dig in on any other specific pieces?18:33
rnirmaljgriffith: if the api is not done... I'll pickup all the api pieces18:33
jgriffithrnirmal: Excellet!18:33
rnirmalmoving over the existing stuff etc18:34
*** edygarcia_ has quit IRC18:34
jgriffith#action rnirmal start working on api pieces18:34
*** edygarcia_ has joined #openstack-meeting18:34
jgriffithrnirmal: Perfect, yeah hopefully there can be alot of copy and paste at this stage18:34
vladimir3pI can take scheduler, but nothing will be done in the next week or so..18:34
vladimir3pit would be great if we could start with better separation between common and cinder part18:35
jgriffithvladimir3p: Should be fine, we'll probably need a mox or something basic to test as we go but that should work18:35
jgriffithvladimir3p: What do you mean exactly?18:35
*** edygarcia_ is now known as edygarcia18:35
rnirmalthere's still a lot of the pieces that are not in common18:35
rnirmalrpc for example18:36
vladimir3pto have clear dependency of openstack-common and remove all the code that is "common" from cinder18:36
vladimir3pbtw, why rpc will be different?18:36
rnirmalit won't be.. just that it's not in openstack-common yet18:36
rnirmalso we'll have to do copy pasta until it moves to common... or we take the effort to move it to common.. may be we don't need rpc at all?18:37
*** edygarcia__ has quit IRC18:37
jgriffithSo I'm hoping that as we write code and put it in we are careful enough to not dup what's in common.  That should go without saying18:37
jgriffithWRT rpc, that's a whole different topic. Can we get by with just rest endpoints?18:37
vladimir3pyeah, instead of copying to cinder it will be better to copy to common18:38
vladimir3phmm... how?18:38
vladimir3pwe have API --> scheduler --> manager18:38
vladimir3psomehow they must communicate18:38
jgriffithvladimir3p: If we can contribute to common we surely should18:38
jgriffithvladimir3p: Ahh, see what you're saying18:39
*** jacky has quit IRC18:39
vladimir3pif endpoint APIs will communicate directly with manager - it is s different story, but IMHO they must be different18:39
vladimir3pand cinder must be a scalable solution18:40
rnirmalyeah looks like we'll need it to start out. and I don't think we've had any proposals or ideas to do it differently18:40
*** edygarcia_ has joined #openstack-meeting18:41
*** edygarcia__ has joined #openstack-meeting18:42
*** edygarcia___ has joined #openstack-meeting18:42
*** edygarcia has quit IRC18:42
rnirmaldo we have anything else for this week? I think there's enough work set out for this week18:43
*** edygarcia has joined #openstack-meeting18:43
jgriffithI'm also trying to figure out if there's a clever way to have a somewhat "isolated" service18:44
jgriffithRegardless, I'd like to tackle some of the lower hanging fruit first (api's, db etc)18:44
jgriffithagreement?18:44
jgriffithAnybody here still?18:44
*** edygarcia____ has joined #openstack-meeting18:44
vladimir3pso, any volunteer to strip common code from john's repo?18:44
vladimir3pby irc behaves weird18:44
vladimir3p*my18:45
rnirmal+1 on low hanging fruit first18:45
*** edygarcia_ has quit IRC18:45
*** edygarcia__ has quit IRC18:46
vladimir3pok, need to go now18:46
vladimir3p+2 with everything what we've discussed18:46
vladimir3p;-)18:46
rnirmalok looks like jgriffith's network is down18:46
*** edygarcia___ has quit IRC18:47
vladimir3pyep18:47
vladimir3prnirmal: you mentioned that you already done the separation of common for reddwarf?18:47
vladimir3pwhere can I take a look at repo?18:48
*** edygarcia has quit IRC18:48
*** edygarcia____ is now known as edygarcia18:48
rnirmalwell not a complete separation18:48
rnirmalhttps://github.com/hub-cap/reddwarf_lite18:48
*** jakedahn_zz is now known as jakedahn18:48
rnirmalbut we atleast hit a few points where stuff needed to be in openstack-common but not there right now18:48
*** edygarcia_ has joined #openstack-meeting18:48
vladimir3pyes, thanks18:49
vladimir3pI suppose it will be way better to put as much as possible common code into openstack=common18:49
*** jgriffith has quit IRC18:49
vladimir3pand to avoid code replication18:49
rnirmalyes totally agree and we can concentrate on the pieces that matter18:49
vladimir3pgreat18:50
rnirmalcool is there anything else? looks like jgriffith won't be able to make it back..18:50
vladimir3pnope18:51
rnirmalif that's all we can end the meeting. not sure if I can do that18:51
vladimir3pany idea how to end the meeting?18:51
rnirmalbut going to give it a try18:51
rnirmal#endmeeting18:51
vladimir3p:_(18:51
rnirmalnope looks like I don't have the permissions to do that... that should have ended the meeting with meeting notes etc18:51
vladimir3pyeah, seems like only john can do it ...18:52
vladimir3pbut I might be wrong18:52
*** edygarcia has quit IRC18:52
rnirmalyeah I think it's configured.. I'll ask ttx if we can do it18:52
*** edygarcia has joined #openstack-meeting18:52
vladimir3p#endmeeting18:54
vladimir3p:-)18:54
rnirmalttx or vishy can one of you'll end this meeting? the moderator jgriffith got cut off.18:54
*** edygarcia_ has quit IRC18:55
rnirmalwell looks like it's going to be dangling till someone else can come and end the meeting :)18:55
vladimir3pok18:55
rnirmalanyways I gotta go. will meet up next week and hopefully have code in the official repo :)18:55
vladimir3pgreat18:55
vladimir3pbye18:55
rnirmalbye18:56
*** darraghb has quit IRC18:59
*** krymynalu has joined #openstack-meeting18:59
*** edygarcia_ has joined #openstack-meeting18:59
*** edygarcia has quit IRC19:03
*** edygarcia_ is now known as edygarcia19:03
*** jgriffith has joined #openstack-meeting19:06
*** edygarcia_ has joined #openstack-meeting19:07
*** edygarcia has quit IRC19:09
*** edygarcia_ is now known as edygarcia19:09
*** Yak-n-Yeti has quit IRC19:11
vishy#endmeeting19:11
vishynope :)19:11
*** Yak-n-Yeti has joined #openstack-meeting19:11
*** joearnold has quit IRC19:11
*** zykes-_ has joined #openstack-meeting19:11
*** s0mik has joined #openstack-meeting19:12
*** edygarcia_ has joined #openstack-meeting19:14
*** edygarcia has quit IRC19:17
*** edygarcia_ is now known as edygarcia19:17
*** edygarcia_ has joined #openstack-meeting19:18
*** edygarcia__ has joined #openstack-meeting19:20
*** edygarcia___ has joined #openstack-meeting19:21
*** edygarcia has quit IRC19:22
*** edygarcia____ has joined #openstack-meeting19:22
*** edygarcia_ has quit IRC19:23
*** edygarcia___ has quit IRC19:25
*** edygarcia__ has quit IRC19:25
*** markmcclain has quit IRC19:26
*** edygarcia has joined #openstack-meeting19:26
*** markmcclain has joined #openstack-meeting19:27
*** edygarcia____ has quit IRC19:28
*** joearnold has joined #openstack-meeting19:30
*** galstrom has joined #openstack-meeting19:30
*** galstrom has left #openstack-meeting19:31
*** adjohn has quit IRC19:33
*** edygarcia_ has joined #openstack-meeting19:35
*** edygarcia__ has joined #openstack-meeting19:37
*** edygarcia has quit IRC19:38
*** edygarcia_ has quit IRC19:40
*** edygarcia has joined #openstack-meeting19:40
*** edygarcia has joined #openstack-meeting19:40
*** edygarcia__ has quit IRC19:41
*** edygarcia_ has joined #openstack-meeting19:42
*** novas0x2a|laptop has joined #openstack-meeting19:43
*** edygarcia has quit IRC19:45
*** edygarcia_ has quit IRC19:46
*** lloydde has joined #openstack-meeting19:47
*** edygarcia has joined #openstack-meeting19:50
*** edygarcia_ has joined #openstack-meeting19:51
*** gyee has joined #openstack-meeting19:52
*** GheRivero has joined #openstack-meeting19:53
*** edygarcia has quit IRC19:54
*** maoy has joined #openstack-meeting19:55
*** edygarcia_ has quit IRC19:55
*** edygarcia has joined #openstack-meeting19:55
*** n0ano has joined #openstack-meeting19:59
maoyn0ano: greetings20:01
n0anomaoy, you survived the summit I see20:02
n0ano#startmeeting20:02
openstackn0ano: Error: Can't start another meeting, one is in progress.20:02
*** gyee has quit IRC20:03
maoyn0ano, yeah.20:03
maoyn0ano: how are you?20:03
n0anodid someone hijack our meeting, I can't start it another one is in progess20:03
maoyn0ano: i don't have much to say..20:03
*** gyee has joined #openstack-meeting20:03
n0anomaoy, major jet lagged, I got home at 2AM last night :-)20:03
vishythe last meeting was never ended20:03
maoyn0ano: a lot of catching up after a week of absence20:03
n0ano#endmeeting20:04
n0anohmm, I can't seem to end the last meeting, do we need an admin to do something?20:04
n0anomaoy, I don't have anything either, I just got back to the office this morning20:05
n0anoif sriram joins we can see if he has anything otherwise just meet up again next wee.20:05
n0anos/wee/seek20:05
maoysure.20:05
n0anos/seek/week20:05
* n0ano needs to get his coordination back20:05
maoySandyWalsh told me how to send in a work-in-progress branch20:06
maoybut i'm still unclear how to do feature branch20:06
*** adjohn has joined #openstack-meeting20:06
n0anoI don't know about those, are they maybe just the same thing by a different name?20:06
maoyno idea..20:07
n0anosounds like you need to talk to sandy again20:07
maoyvishy: is feature branch the same as work-in-progress branch in gerrit?20:07
vishythere is no support for feature branches yet20:07
*** dprince has quit IRC20:07
notmynamejgriffith: needs to #endmeeting20:07
vishyso WIP is the current method20:07
maoygot it20:08
*** sriramhere has joined #openstack-meeting20:09
sriramhereany nova-orchestration guys here?20:09
sriramheresorry i am late20:09
n0anosriramhere, yep, maoy & I are here but we don't have anything for today, do you?20:09
sriramherenope, just wanted to check for updates if any.20:11
sriramhereand generally say HI and good job on the presentation last week entire team!20:11
n0anoIndeed, tnx to both of you, you did the heavy lifting20:12
sriramheren0ano - to pick a bone with you that you didnt rig the raffle so that I can win :-)20:12
n0anowell, it's only one SSD drive so you couldn't split it with, not point in my rigging things :-)20:12
sriramhere:)20:12
maoylol20:13
sriramherethanks again guys, cya next week then...20:13
maoywhat's you guys launchpad accounts?20:13
maoybefore you go..20:13
n0anoI think we're good then (fortunately since we can't start the meeting) so we'll talk again next week (hopefully with something to say then).20:13
n0anomines the same, n0ano20:13
*** lloydde has quit IRC20:13
maoynoted20:14
sriramheresriramhere or sriram-x20:14
sriramheresriram-x20:14
maoyok20:16
*** littleidea has quit IRC20:16
*** ttrifonov is now known as ttrifonov_zZzz20:16
maoyc ya next week20:16
*** littleidea_ has joined #openstack-meeting20:16
*** lloydde has joined #openstack-meeting20:20
jgriffithvishy: Did you manage to end the meeting?20:29
jgriffithOr shall I try it now?20:29
vishygo20:29
vishyno one else can do it20:29
jgriffith#endmeeting20:30
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"20:30
openstackMeeting ended Thu Apr 26 20:30:09 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-18.02.html20:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-18.02.txt20:30
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-18.02.log.html20:30
jgriffithSorry everyone... send complaints directly to comcast20:30
*** littleidea_ is now known as littleidea20:30
*** sriramhere has quit IRC20:36
*** reed has joined #openstack-meeting20:38
*** GheRivero has quit IRC20:43
*** ttrifonov_zZzz is now known as ttrifonov20:46
*** ttrifonov is now known as ttrifonov_zZzz20:47
*** dendro-afk is now known as dendrobates20:48
*** joearnold has quit IRC20:50
*** anderstj has quit IRC20:50
*** n0ano has left #openstack-meeting20:55
*** dachary has quit IRC20:56
*** mdomsch has quit IRC20:58
*** littleidea has quit IRC20:59
*** AlanClark has quit IRC21:00
*** krymynalu has quit IRC21:01
*** littleidea has joined #openstack-meeting21:02
*** jalcine- has joined #openstack-meeting21:06
*** jalcine- has joined #openstack-meeting21:06
*** anderstj has joined #openstack-meeting21:10
*** joearnold has joined #openstack-meeting21:11
*** anderstj_ has joined #openstack-meeting21:11
*** jbrogan has quit IRC21:13
*** anderstj has quit IRC21:15
*** ttrifonov_zZzz is now known as ttrifonov21:17
*** ryanpetrello has quit IRC21:26
*** ttrifonov is now known as ttrifonov_zZzz21:30
*** markvoelker has quit IRC21:34
*** ttrifonov_zZzz is now known as ttrifonov21:35
*** Gordonz_ has joined #openstack-meeting21:36
*** jgriffith has quit IRC21:37
*** Gordonz has quit IRC21:39
*** dendrobates is now known as dendro-afk21:42
*** jgriffith has joined #openstack-meeting21:44
*** ttrifonov is now known as ttrifonov_zZzz21:45
*** Yak-n-Yeti has quit IRC21:45
*** rnirmal has quit IRC21:46
*** Gordonz_ has quit IRC21:58
*** anderstj_ has quit IRC22:05
*** anderstj has joined #openstack-meeting22:07
*** markmcclain has quit IRC22:07
*** anderstj has quit IRC22:09
*** maoy has quit IRC22:13
*** blamar has quit IRC22:14
*** mattray has quit IRC22:15
*** dtroyer is now known as dtroyer_zzz22:31
*** sandywalsh_ has quit IRC22:35
*** dachary has joined #openstack-meeting22:46
*** ryanpetrello has joined #openstack-meeting22:47
*** Yak-n-Yeti has joined #openstack-meeting22:52
*** edygarcia has quit IRC23:01
*** dtroyer_zzz is now known as dtroyer23:03
*** joearnold has quit IRC23:04
*** joearnold has joined #openstack-meeting23:11
*** ryanpetrello has quit IRC23:11
*** dachary has quit IRC23:11
*** sandywalsh_ has joined #openstack-meeting23:16
*** gyee has quit IRC23:22
*** novas0x2a|laptop has quit IRC23:31
*** lloydde has quit IRC23:31
*** novas0x2a|laptop has joined #openstack-meeting23:31
*** Mandell has quit IRC23:44
*** novas0x2a|laptop has quit IRC23:53

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