Tuesday, 2016-04-19

*** raildo is now known as raildo-afk00:33
*** sdague has quit IRC00:59
*** ebalduf has quit IRC01:38
*** ninag has quit IRC02:19
*** ebalduf has joined #openstack-meeting-cp02:53
*** persia has quit IRC03:40
*** persia has joined #openstack-meeting-cp03:50
*** _amrith_ is now known as amrith03:58
*** sheel has joined #openstack-meeting-cp04:09
*** amrith is now known as _amrith_04:38
*** rakhmerov has joined #openstack-meeting-cp07:01
*** vilobhmm11 has joined #openstack-meeting-cp07:14
*** ebalduf has quit IRC07:20
*** Rockyg has quit IRC07:24
*** vilobhmm11 has quit IRC08:02
*** sheel has quit IRC08:55
*** vgridnev has joined #openstack-meeting-cp09:31
*** sdague has joined #openstack-meeting-cp10:08
*** markvoelker has joined #openstack-meeting-cp10:37
*** markvoelker has quit IRC10:42
*** markvoelker has joined #openstack-meeting-cp11:38
*** markvoelker has quit IRC11:42
*** mageshgv has joined #openstack-meeting-cp11:52
*** raildo-afk is now known as raildo11:58
*** _amrith_ is now known as amrith12:07
*** mtreinish has quit IRC12:18
*** markvoelker has joined #openstack-meeting-cp12:19
*** mtreinish has joined #openstack-meeting-cp12:21
*** xyang1 has joined #openstack-meeting-cp13:30
*** openstackstatus has joined #openstack-meeting-cp13:37
*** ChanServ sets mode: +v openstackstatus13:37
-openstackstatus- NOTICE: We have recovered one of our cloud providers, but there is a huge backlog of jobs to process. Please have patience until your jobs are processed13:40
*** sigmavirus24_awa is now known as sigmavirus2414:01
*** ebalduf has joined #openstack-meeting-cp14:26
*** jungleboyj has joined #openstack-meeting-cp14:36
*** sheel has joined #openstack-meeting-cp14:36
*** mageshgv has quit IRC15:18
*** mageshgv has joined #openstack-meeting-cp15:30
*** vgridnev has quit IRC15:38
*** Rockyg has joined #openstack-meeting-cp15:57
*** sdake has joined #openstack-meeting-cp16:14
*** mageshgv has quit IRC16:19
*** anteaya has quit IRC16:20
*** sdake_ has joined #openstack-meeting-cp16:25
*** sdake has quit IRC16:29
*** mageshgv has joined #openstack-meeting-cp16:35
*** mageshgv has quit IRC16:46
*** tyr_ has joined #openstack-meeting-cp16:55
*** vilobhmm11 has joined #openstack-meeting-cp16:55
vilobhmm11#startmeeting quotas-wg16:59
openstackMeeting started Tue Apr 19 16:59:15 2016 UTC and is due to finish in 60 minutes.  The chair is vilobhmm11. Information about MeetBot at http://wiki.debian.org/MeetBot.16:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:59
*** openstack changes topic to " (Meeting topic: quotas-wg)"16:59
openstackThe meeting name has been set to 'quotas_wg'16:59
vilobhmm11hello everyone16:59
*** mageshgv has joined #openstack-meeting-cp16:59
amrithhello everyone17:00
nikhilo/17:00
nikhilvilobhmm11: can you please highlight us on the channel, I've the courtesy reminder list added to the agenda etherpad.. thanks in advance!17:00
vilobhmm11hi so have updated the agenda for today17:00
nikhil#link https://etherpad.openstack.org/p/quotas-wg-meeting-agenda17:01
vilobhmm11sure17:01
vilobhmm11nikhil, vilobhmm, DuncanT, mc_nair, ninag, amrith17:01
vilobhmm11nikhil : thanks for the link17:01
nikhilyw!17:01
*** Qijing has joined #openstack-meeting-cp17:01
raildohey :)17:01
vilobhmm11will wait for few min17:02
vilobhmm11hey raildo17:02
amrithhello all17:02
nikhil:)17:02
vilobhmm11alrite lets start17:03
DuncanTHi17:03
vilobhmm11#topic Meetup at Summit17:03
*** openstack changes topic to "Meetup at Summit (Meeting topic: quotas-wg)"17:03
vilobhmm11Nikhil bought up a good point last meeting or an e-mail conversation that we should meetup on Monday17:04
vilobhmm11before we session on Tuesday 04/2617:04
nikhil#link http://doodle.com/poll/e4nq9tc77bdv8zwr17:05
vilobhmm11we can meet at room 4a reserved for brown bag17:05
DuncanTSeems like a good plan17:05
nikhilplease vote!17:05
vilobhmm11nikhil : thanks again ! :)17:06
nikhilnp17:06
amrithsorry, am timeslicing with a phone call17:07
vilobhmm11as per the timings on the doodle we won't be getting the room reserved for brown bag but we can all meet near that room and then find a common one17:08
vilobhmm11otherwise it would be very hard to find each other17:08
nikhilvilobhmm11: yeah, true17:08
*** Qijing_ has joined #openstack-meeting-cp17:09
nikhilwhat's the best mode of communication here? email?17:09
DuncanTEmail for me17:09
amrithemail works for me, IRC won't most of the time17:09
vilobhmm11nikhil : email works for me too17:09
nikhilcool17:09
*** Qijing_ has left #openstack-meeting-cp17:09
vilobhmm11so please vote on the doodle17:10
nikhilThanks all. will email then.17:10
vilobhmm11we can gather votes and find a good time that works for everyone17:10
vilobhmm11#topic Product group getting started with requirements. 17:10
*** openstack changes topic to "Product group getting started with requirements.  (Meeting topic: quotas-wg)"17:10
nikhil(it'd be great if harlowja can join us too given he is leading the CP session)17:11
DuncanTI've some substantial worries about this and scope creep17:11
nikhil:)17:11
vilobhmm11nikhil : he will join; we discussed and i will be leading the CP session17:11
*** vgridnev has joined #openstack-meeting-cp17:11
DuncanTThings like reserving quota for heat and similar - at least for cinder, that's pointless17:11
nikhilvilobhmm11: ah k, thanks for the update.17:11
vilobhmm11harlowja : ping17:12
nikhilDuncanT: reserving or enforcing ? :)17:12
nikhilor both17:12
vilobhmm11nikhil : did request sdauge to for an update on the chair for the quota session ; should see an update soon…17:12
nikhilvilobhmm11: excellent, thanks. I was about to ping you offline.17:13
DuncanTnikhil: what's the point of a reservation if it is anything other than enforcing?17:13
vilobhmm11DuncanT , nikhil : will come to reservation in a bit; its a long topic …lets cover smaller ones quickly…thanks!17:13
nikhilok17:13
vilobhmm11irc://irc.freenode.net:6667/#topic : Product group getting started with requirements.17:13
vilobhmm11irc://irc.freenode.net:6667/#topic Product group getting started with requirements17:13
DuncanTvilobhmm11: This isn't reservations in the currnet code sense :-)17:13
nikhilbut is this particular one tied to PW17:14
vilobhmm11ok :)17:14
vilobhmm11shamail and other have started gathering use-cases and requirement about how people use quota and do capacity management17:14
nikhilis there a reference document for the scope? and for worries from DuncanT?17:14
DuncanTWe've lots of terms beign thrown around, and we've still got no glossary - each mailing list thread picks its own terminology17:14
nikhila BIG +1 on "defining terms"17:15
vilobhmm11this will help to strengthen the use-cases problems with current quota mgmt17:15
DuncanT(please excuse my typing, I've substantial damage to two fingers and so it's rather tricky to type well and fast)17:15
nikhilactually, that can be the additional info section in the spec and people _should_ refer to it while emailing17:16
vilobhmm11coming back to nikhil and DuncanT :)17:16
DuncanTI'm a strong proponent of matching terms to existing usage, e.g. reservation should be the code construct we already have in three projects17:16
vilobhmm11#topic No reservation17:16
*** openstack changes topic to "No reservation (Meeting topic: quotas-wg)"17:16
vilobhmm11DuncanT : +117:16
DuncanTSo first question: what do we mean by 'reservation'?17:17
amrithI'm curious to know how we can handle quotas without reservations; the risk is that quotas are not a constraint if you don't have reservations (I THINK, AND MAY BE WRONG)17:17
amrithDuncanT, if that's a quesiton to me, I described it in my mail to the ML17:17
vilobhmm11having said that what it funcationaly translates to in every project and in delimiter can mean different things (if at all they are used)17:17
* amrith shamlessly plugs email to the ML :)17:17
nikhilheh17:17
DuncanTamrith: Got a link to your mail, please?17:18
vilobhmm11amrith : first of all thanks for the ML17:18
amrithhttp://openstack.markmail.org/thread/at3phitv3oupxupi17:18
amrithI got one comment from Jay, didn't realize it till now17:18
amrithhave to read it17:18
amrithhis comments are always very insightful17:18
vilobhmm11yup17:19
vilobhmm11they are17:19
vilobhmm11in short let me brief everyone17:19
vilobhmm11on why i am saying that even going with no-reservation can be an option17:19
nikhilI think the advantage (and consequential disadvantages for "the other set") is that reservation is super useful if your assets/resources "DO have" a task potentially in process that is not highly elastic or distributed.17:19
DuncanTI strongly disagree with Jay about rate limiting not being a quota thing, for the record. I'll write a reply to him soon17:19
amrithvilobhmm11, I'm going to wait to hear what you say about no-reservations and hold off on reading Jay's comments17:20
DuncanTIn the case of cinder, a reservation is just consumed quota attached to a request i nprogress.17:20
DuncanTin progress17:21
nikhilexactly DuncanT, it's the "in process" part that's significant17:21
nikhilbecause the race is outside of the DB17:21
vilobhmm11DuncanT : rate limiting or rate of request mgmt can be done even by external sources like repose http://www.openrepose.org/17:21
nikhilto elaborate on my point: Glance will not need reservation for storing images or number of images or members etc. I think the DB transaction semantics is enough.17:21
DuncanTnikhil: There shouldn't be a race17:21
vilobhmm11amrith : sure…in a min going through duncanT and nikhils comments17:22
DuncanTnikhil: Assuming the semantics are implemented without bugs, there are no race differences between getting a reservation and getting commited quota before returning from the create request17:22
nikhilI see17:23
nikhilso, we are talking about reservation vs. quota-commit+rollback17:23
nikhilthere's the third case17:23
DuncanTThe only difference between a reservation and a commited quota usage is that the reservation can be cancelled if the consuming process dies (plus they are handy for some debugging, though not as handy as they could be)17:23
nikhilthat involved simply quota-commit on success17:23
DuncanTYou need to(Semantically) quota commit before you create the resource, or the quota is useless against DoS and similar17:24
* amrith is having a hard time demultiplexing conversations17:24
nikhilDuncanT: not necessarily17:24
nikhilfor example: image-create call in glance17:25
*** ericksonsantos has joined #openstack-meeting-cp17:25
nikhilit's a simple record / row creation in the DB17:25
nikhilthe only thing that we need is:17:25
nikhil1. create a image , update quota table17:25
DuncanTPlus storage used....17:25
nikhil2. once quota is full, keep returning non availability to the users17:25
nikhilstorage is different resource17:26
nikhilso I am breaking things down for sanity sake17:26
nikhil1. # images17:26
nikhil2. amount of data stored for all images in a cloud account17:26
nikhil3. # members on an image / account (depending on usage)17:26
nikhilfor #1, all we need quota commit on success17:27
nikhil#2 is image upload for which it's a "task" or potentially long running process17:27
DuncanTnikhil: If I can create db resources (even db records, in principle) without quota check, then in theory I can bomb the system with parallel requests17:27
DuncanTnikhil: Glance is a pretty weird API, but the principle stands. If I have a quota of 10, it should be impossible for me to create more than 10 'things'17:28
DuncanTnikhil: I should never have got back a 200 or a 202 from the 11th request17:28
nikhilGlance API is that way as Nova needs it so17:28
DuncanTnikhil: I can strongly disagree with that, but this isn't the venue  -grab me over a beer17:29
nikhiland to your point of 10 resources, if we implement test and set for quota check in glance we don't need reservation (As the transaction can be limited to DB only)17:29
nikhilyeah, I don't know what you are referring to with the specifics of Glance API. If you ask me , cinder shouldn't be using glance (& use something like GLARE) in the first place but then again .. not the place for that :)17:30
vilobhmm11alrite first of all DuncanT : I agree with you on the point of *timelines for reservation and quota commit*  nikhil : just to elaborate more you can think of reservation and few quota related tables as *cache* tables for actual resource consumption. They are nothing more than that!17:31
vilobhmm11amrith : ^^17:31
nikhilvilobhmm11: exactly17:31
vilobhmm11reservation and few quota tables are cache tables17:31
nikhiland that's a race for glance17:31
amrithvilobhmm11, I've totally lost the train of the conversation17:32
vilobhmm11actual resource consumption happens in actual resource tables like nova.instances in nova or glance.images in glance17:32
DuncanTThe one thing about cinder and nova reservations currently is that they can auto-uncommit if the system breaks down and the creation request is  lost. That is badly done at the moment but might be a desirable property17:32
amrithI don't know who is replying to whom/what and I'm trying to untangle the threads17:32
DuncanTnikhil: Why is there a race?17:32
vilobhmm11amrith : just read my last comment you will get a gist of it17:33
amrithalso, I think we're talking about the specifics of a specific service or a set of services, rather than talking about what a generic set of requirements may be for a bunch of services.17:33
amrithvilobhmm11, I read it; I don't understand why we're talking about tables.17:33
amriththat's an implementation detail17:33
amrithwhat I want to understand is what we're going to QUOTA'ify.17:33
amrithis it (for example) some predetermined set of resources17:33
amrithor can each consumer of thelibrary define their own set of resources17:33
vilobhmm11amrith : for existing project there are well defined set of resources right17:34
DuncanTamrith: Consumers need to define their own resource set. That's a hard requirement for cinder17:34
amrithDuncanT, I'll let you respond to that point that Jay makes (a static set of resources)17:34
amrithok, then there's a question on the kinds of quotas we want17:34
DuncanTamrith: e.g. volume types (which are arbitrary in name and number) have individual quotas currently17:34
amrithupper bound17:34
vilobhmm11DuncanT : for existing projects too …like nova has ram, cpu, mem as resources17:34
amrithlower bound17:34
amrithrate17:34
vilobhmm11DuncanT : for existing projects too ?17:35
amriththen there's the question of what to do about resizes; should they be supported in the library or not17:35
DuncanTWe need to support all of the quota operations used in projects today, or we won't get adopted17:35
vilobhmm11amrith : let me go over jay's reply and get back17:35
amriththen, are these quotas to be multi-tenant or system wide17:36
amrithvilobhmm11, this isn't about jay's email17:36
vilobhmm11amrith, DuncanT, nikhil :strongly agree on getting the scope right for the lib17:36
amrithI haven't read it17:36
DuncanTResizes are supported in projects right now (e.g. cinder), ergo we need to wupport them17:36
nikhilvilobhmm11: yes, and we need to meet personally for that! :))17:36
vilobhmm11nikhil : ++17:36
amriththen there's the question of how we intend dealing with the use-case where a user (say me) may have a quota of 5 instances and comes and makes two concurrent requests for 3 instances each17:36
amriththe first one we look at says 3 < 5, great17:37
amrithbut since no instances have been actually created, the others says 3 < 5, great17:37
amrithand now we get 6 instances17:37
amrithand 6 > 517:37
amrithwe can figure out what we want to call it; reservations, preallocations, intents, ...17:37
DuncanTamrith: That is already handled - creating a reservation consumes quota. The first to grab the quota gets created, the second doesn't17:37
nikhilvilobhmm11: I need 5 mins for open discussion17:38
DuncanTamrith: We can't go backwards from that sematic (we can fix the races that each project has that break those semantics)17:38
vilobhmm11nikhil : sure17:38
amrithso DuncanT what you are saying is that this new library is constrained by what existing projects are doing?17:39
vilobhmm11the timeline when the reservation is commited and when the quota commit happens are the same…also the validation applies at both places…amrith : the use case you mentioned above17:39
DuncanTamrith: That semantic *can* be implemented without any kind of reservation though, as long as you're on a single DB. You put the thing in the DB table in some 'creating' state (cinder and nova already do that) and count those as existing for quota purposes17:39
amrithDuncanT, depending on the isolation level of your database, that may or may not work17:40
vilobhmm11DuncanT : yup +117:40
amrithsorry vilobhmm11, happy to sketch it out on a whiteboard and show you why not17:41
vilobhmm11amrith : question for you…what benefits you think that reservation is bringing right now and we might end up loosing it if it is removed ?17:41
vilobhmm11amrith : sure17:41
amrithI believe that the business that a service does is multi-step17:41
amrithand that is surely the case for something like trove17:41
amrithand therefore, being able to support multiple steps is essential17:42
amrithand having a database transaction be long lived and assuming that this will work is fraught with danger17:42
amrithso I'm viewing reservations as short lived database operations that help you break up the long lived database transaction17:42
DuncanTamrith: That is *not* what reservations (as the term is currently used in the code) is all about17:42
amrithok, what does a reservation mean in the current usage in code17:43
DuncanTamrith: reservations are not an externally visible thing17:43
DuncanTamrith: They're a handle on a block of consumed quota17:43
DuncanTThat's it17:43
amrithI think I'm describing the same thig17:43
amriththing17:43
amrithnot externally visible: yes17:43
amritha handle on a block of consumed quota: yes17:44
amrithsomething that is 'in flight'17:44
DuncanTOk, I'm just not understanding you then17:44
amrithto make a database instance I need an instance and a cinder volume17:44
amrithi make a reservation for cinder17:44
amriththen a reservation for an instance17:44
DuncanTNo.17:44
amrithif the latter fails, I release the former17:44
DuncanTDefinitely not.17:44
amrithsorry, I don't know what you mean by no; that's the use-case in Trove :)17:44
DuncanTThere is no concept of trove 'making a reservation' for cinder17:45
DuncanTCurrently17:45
DuncanTReservations are just a construct inside cinder - no external consumer sees them17:45
amrithactually there is, but ...17:45
amrithhere is what I mean17:45
amrithYou do what you wish in cinder, that's a black box to me17:45
DuncanTTrove asks cinder to create a volume. That's the only operation it has17:45
amrithhere are the limits that trove has17:45
amrithno user may have more than 10 db volumes17:46
amrithno user may have more than 10 db instances17:46
amrithremember that the user has a nova quota of 1000 instances17:46
amrithand a cinder quota of 500 volumes17:46
amrithtrove has its own limits ON CINDER RESOURCES17:46
amriththat Trove has to enforce17:46
DuncanTMY point being, the word 'reservation' has a meaning in the code now. You're using it to mean  something slightly different, and that is causing communication difficulties17:46
amrithsorry, I'm using it to mean the same thing17:47
amrithin the trove context17:47
amrithI need to make a reservaton for a cinder volume17:47
amrithand a reservation for an instnace17:47
amrithI don't tell cinder about it17:47
amrithyou don't know17:47
amrithI make my own reservations17:47
amrithonce I make my reservations and they all succeed, then it means the user has the quotas17:47
amriththen I go call cinder and ask for a volume17:47
amrithyou could still fail the request17:47
amrithno guarantees17:47
amriththen I go ask nova17:48
DuncanTGah, ok, so you're talking about trove's counting of cinder volumes? That was entirely not clear17:48
amrithit could succeed or fail17:48
amrithsorry17:48
amriththat was Trove's reservation for a cinder resource; not something cinder gets to know about17:48
amrithas I said in my email, "Such a hypothetical service may also consume resources from other services that it wishes to track, and impose limits on."17:48
DuncanTYou could just commit all those reservations in trove, and release them later in exactly the same way as a delete - there's no need for a reservation17:48
nikhilvilobhmm11: my point on defining terms  and the ill consequences of over use of the same word .. :) (in practice) (no offense to anyone, just pointing out example of mis communications)17:49
DuncanTJust consume the resource17:49
DuncanTBAcking out a reservation is semantically the same as deleting it17:49
vilobhmm11nikhil : sure…but few terms which come over time should def be documented in glossary..point noted will take care17:49
amrithSorry DuncanT how do you intend that I do that?17:50
amrith"just commit all those ..."17:50
DuncanTamrith: start transaction; count (volumes where tenant id = me); if count < quota insert into volumes table state = creating17:51
DuncanTThen do the same for the nova table17:51
amrithDuncanT, great17:51
amrithnow let me tell you why that won't work17:51
nikhilvilobhmm11: yes, agreed on glossary (true!, we can't really predict the future) :)17:51
amrithto begin, what's the database isolation level? I assume read-committed?17:51
amrithor would you like more than that?17:51
amrithwould you like repeatable read17:51
amrithor serializable?17:51
amrithtake your pick, let me know17:52
amrithI'm assuming read committed17:52
amrithdo we agree?17:52
* amrith waits17:52
DuncanTamrith: Honestly, I can only pick what is currently used in cinder, I've not looked the the terms for teh semantics I want for some time17:52
vilobhmm11amrith : read-commited means read whatever is written last right17:52
amrithNO17:52
amrithwhat ever was committed last17:52
amrithlet me explain17:52
amrithstarting state17:53
amrith0 instances17:53
amrith0 volumes17:53
amrithquota 5 of each17:53
vilobhmm11by written i mean commited17:53
amrithrequest 1: 3 instances17:53
vilobhmm11ok17:53
amrithbegin transaction request 117:53
amrithtransaction 1: how many instances: answer 017:53
amrith0 is less than 5, insert 3 in table17:53
amrithrequest 2: 3 instances please17:53
amrithbegin transaction request 217:53
amrithtransaction 2: how many instance?17:54
amrithanswer: 017:54
amrithplease give me 3 ...17:54
amrithinsert 3 in table17:54
amrithtransaction 1: do something about volumes17:54
amrithcommit17:54
amrithtranaction 2: do something about volumes17:54
amrithcommit17:54
amrithnet result17:54
amrith6 instances17:54
DuncanTamrith: It is my understanding that one of those transations should fail17:54
amrithnot if you run read committed17:54
DuncanTamrith: Or at least can be constructed that way17:54
amrithfor that you increase isolation level for the db17:55
amrithto repeatable read17:55
nikhilamrith: yes, that was the argument I was making earlier but in non-defined terms17:55
amrithor serializable17:55
vilobhmm11amrith : yes won't compare and swap or test and set happen at the db level17:55
amriththen performance issues begin17:55
DuncanTamrith: Ok, I now understand your point. Thank you.17:55
amrithvilobhmm11, yes, if you have the right isolation level17:55
DuncanTamrith: I also need to go examine some cinder db atomics code17:55
nikhilI think the openstack general rule on sql-like DBs is read committed17:56
amrithand please read: http://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-model.html17:56
nikhilbarring nova in some cases17:56
amriththe default is read-committed for mysql17:56
amrithyes, if you run in something more, be ready for deadlocks galore17:56
amrithanyway, I'll reply to jay on this aspect17:57
DuncanTamrith: So I think our best way forward is to define a python interface and its semantics and then figure out how to implement it (and stress test it)?17:57
nikhilamrith: in glance, we explicitly implemented test&set for some update operations17:57
vilobhmm11amrith : but in openstack context for now we are mostly concered about sql db only no *nosql* in openstack right…so sql based i.e. mysql is read-commited by default..17:57
nikhilnot sure how much of that is upstream (gah)17:57
*** tyr_ has quit IRC17:58
DuncanTnikhil: We have something similar, but I think they only operate on one table and use update...where in our case17:58
vilobhmm11alrite guys we are running out of time17:58
harlowjahowdy17:58
nikhil:)17:58
vilobhmm11hello harlowja…just wrapping up17:58
nikhilI need a few mins pls17:59
vilobhmm11#topic open discussion17:59
*** openstack changes topic to "open discussion (Meeting topic: quotas-wg)"17:59
harlowjai'm around :-P17:59
harlowjabut on phone, ha17:59
nikhilthanks17:59
vilobhmm11yes nikhil17:59
amrithnikhil gets 1 min17:59
nikhil:)17:59
harlowjaya, i'll lead, but u guys need to drive ;)17:59
harlowjapong17:59
vilobhmm11harlowja : np17:59
nikhilI was just thinking..17:59
nikhilglance midcycle is in boston/cambridge17:59
nikhiljune 15-1717:59
nikhilI know amrith is in that area (from twitter) ?17:59
nikhilwould it be possible for others to join17:59
nikhilmay be the 14th for quotas?18:00
amrithI will be happy to attend but 15-17 is ... I hae a board meeting on 15, I can do 16 and 1718:00
nikhilseems to me that summit will be too short for long discussions18:00
amrithI can do 14th18:00
amrithbut I'd prefer 16th or 17th18:00
DuncanTThat's a long flight for me, I'm unlikely to get funding18:00
nikhilumm, let me ask shamail too18:00
nikhilI can arrange for remote attendance18:01
nikhilall I need is your full attention for half a day18:01
DuncanTremote is certainly doable18:01
vilobhmm11nikhil : need to check about funding..otherwise can join via hangouts18:01
DuncanTIt will have to be morning though - I'm at GMT+2/318:01
amrithshould we move to #openstack-quota?18:01
nikhilsomething that you can block in your .cal and let mgmt know unavailability for that time18:01
nikhilsure18:01
vilobhmm11sure18:02
nikhilwe can discuss this at the summit18:02
nikhilfood for thought18:02
vilobhmm11lets move to #openstack-quota18:02
nikhilthanks all!18:02
vilobhmm11thanks!18:02
vilobhmm11#endmeeting18:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:02
openstackMeeting ended Tue Apr 19 18:02:15 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/quotas_wg/2016/quotas_wg.2016-04-19-16.59.html18:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/quotas_wg/2016/quotas_wg.2016-04-19-16.59.txt18:02
openstackLog:            http://eavesdrop.openstack.org/meetings/quotas_wg/2016/quotas_wg.2016-04-19-16.59.log.html18:02
DuncanTSure, I'll pencil in all three days for now18:02
*** mtreinish has quit IRC18:03
*** vilobhmm11 has quit IRC18:04
*** Qijing has left #openstack-meeting-cp18:06
harlowjalol18:07
harlowjavilobhmm11 i think my advice for all of this, is just start coding, don't get stuck in <architecture-perfectness> ;)18:08
harlowjau can end up in <architecture-perfectness> forever, lol18:08
*** mtreinish has joined #openstack-meeting-cp18:08
*** sdake_ has quit IRC18:41
*** tyr_ has joined #openstack-meeting-cp18:46
*** sdake has joined #openstack-meeting-cp18:48
*** tyr__ has joined #openstack-meeting-cp18:50
*** ebalduf has quit IRC18:52
*** tyr_ has quit IRC18:53
*** amrith is now known as _amrith_18:58
*** vilobhmm11 has joined #openstack-meeting-cp19:02
*** rocky_g has joined #openstack-meeting-cp19:03
*** sheel has quit IRC19:05
*** sigmavirus24 is now known as sigmavirus24_awa19:06
*** mc_nair has joined #openstack-meeting-cp19:27
*** mtreinish has quit IRC19:41
*** mtreinish has joined #openstack-meeting-cp19:42
*** mtreinish has quit IRC19:49
*** sigmavirus24_awa is now known as sigmavirus2420:06
*** _amrith_ is now known as amrith20:07
*** jungleboyj has quit IRC20:36
*** diablo_rojo has joined #openstack-meeting-cp20:43
*** xarses has joined #openstack-meeting-cp20:46
*** tristanC_ is now known as tristanC20:54
*** dims_ has joined #openstack-meeting-cp21:02
*** dims has quit IRC21:02
*** amrith is now known as _amrith_21:05
*** vilobhmm11 has quit IRC21:07
*** vilobhmm11 has joined #openstack-meeting-cp21:08
*** rocky_g has quit IRC21:11
*** xarses has left #openstack-meeting-cp21:14
*** sdake_ has joined #openstack-meeting-cp21:30
*** diablo_rojo has quit IRC21:31
*** sdake has quit IRC21:33
*** vilobhmm11 has quit IRC21:43
*** vilobhmm11 has joined #openstack-meeting-cp21:44
*** vilobhmm11 has quit IRC21:45
*** vilobhmm11 has joined #openstack-meeting-cp21:45
*** vilobhmm11 has quit IRC21:45
*** vilobhmm11 has joined #openstack-meeting-cp21:46
*** vilobhmm11 has quit IRC21:46
*** vilobhmm11 has joined #openstack-meeting-cp21:46
*** _amrith_ is now known as amrith21:50
*** vgridnev has quit IRC21:53
*** vilobhmm11 has quit IRC21:59
*** vilobhmm11 has joined #openstack-meeting-cp21:59
*** amrith is now known as _amrith_22:00
*** xyang1 has quit IRC22:01
*** sigmavirus24 is now known as sigmavirus24_awa22:02
*** mtreinish has joined #openstack-meeting-cp22:16
*** sdake_ is now known as sake22:26
*** vilobhmm11 has quit IRC22:32
*** vilobhmm11 has joined #openstack-meeting-cp22:32
*** vilobhmm11 has quit IRC22:33
*** vilobhmm11 has joined #openstack-meeting-cp22:33
*** vilobhmm11 has quit IRC22:40
*** persia has quit IRC22:46
*** mageshgv has quit IRC22:54
*** vilobhmm11 has joined #openstack-meeting-cp22:55
*** persia has joined #openstack-meeting-cp23:04
*** sdague has quit IRC23:07
*** mageshgv has joined #openstack-meeting-cp23:07
*** david-lyle_ has joined #openstack-meeting-cp23:14
*** david-lyle has quit IRC23:14
*** sake is now known as sdake23:22
*** vilobhmm11 has quit IRC23:49
*** vilobhmm11 has joined #openstack-meeting-cp23:49
*** david-lyle_ is now known as david-lyle23:57

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