Monday, 2012-10-22

*** ywu has quit IRC00:00
*** ywu has joined #openstack-meeting00:00
*** tgall_foo has quit IRC00:08
*** ywu has quit IRC00:10
*** ywu has joined #openstack-meeting00:10
*** ywu has quit IRC00:13
*** ywu has joined #openstack-meeting00:14
*** ywu has joined #openstack-meeting00:14
*** ywu has quit IRC00:20
*** ywu has joined #openstack-meeting00:20
*** ywu has quit IRC00:29
*** ywu has joined #openstack-meeting00:29
*** ywu has quit IRC00:44
*** ywu has joined #openstack-meeting00:44
*** s0mik has joined #openstack-meeting00:47
*** adjohn has joined #openstack-meeting00:57
*** adjohn has quit IRC00:58
*** ywu has quit IRC00:59
*** ywu has joined #openstack-meeting00:59
*** reed has quit IRC01:00
*** Mandell has joined #openstack-meeting01:08
*** ywu has quit IRC01:13
*** ywu has joined #openstack-meeting01:14
*** ywu has joined #openstack-meeting01:14
*** mikal has quit IRC01:15
*** mikal has joined #openstack-meeting01:17
*** ywu has quit IRC01:18
*** ywu has joined #openstack-meeting01:18
*** littleidea has joined #openstack-meeting01:19
*** ywu has quit IRC01:20
*** ywu has joined #openstack-meeting01:20
*** littleidea has left #openstack-meeting01:21
*** ywu has quit IRC01:29
*** littleidea has joined #openstack-meeting01:29
*** ywu has joined #openstack-meeting01:29
*** dwcramer has joined #openstack-meeting01:34
*** littleidea has quit IRC01:41
*** davidh_ has joined #openstack-meeting01:50
*** davidhadas has quit IRC01:52
*** dwcramer has quit IRC01:56
*** oubiwann has quit IRC02:09
*** shang has joined #openstack-meeting02:17
*** s0mik has quit IRC02:18
*** s0mik has joined #openstack-meeting02:18
*** tgall_foo has joined #openstack-meeting02:20
*** tgall_foo has joined #openstack-meeting02:20
*** littleidea has joined #openstack-meeting02:37
*** Mandell has quit IRC02:43
*** dwcramer has joined #openstack-meeting02:45
*** SumitNaiksatam has joined #openstack-meeting02:47
*** SumitNaiksatam has quit IRC02:49
*** bencherian has joined #openstack-meeting03:07
*** bencherian has left #openstack-meeting03:08
*** jakedahn_zz is now known as jakedahn03:22
*** mikal has quit IRC03:26
*** mikal has joined #openstack-meeting03:27
*** ywu has quit IRC03:36
*** _ozstacker_ has quit IRC03:36
*** oubiwann has joined #openstack-meeting03:42
*** littleidea has quit IRC03:44
*** littleidea has joined #openstack-meeting03:46
*** tgall_foo has quit IRC03:51
*** oubiwann has quit IRC04:06
*** nijaba has joined #openstack-meeting04:34
*** nijaba has joined #openstack-meeting04:34
*** Mandell has joined #openstack-meeting04:59
*** dwcramer has quit IRC04:59
*** SumitNaiksatam has joined #openstack-meeting05:14
*** SumitNaiksatam is now known as SumitNaiksatam-a05:27
*** jamespage_ has joined #openstack-meeting05:33
*** jamespage_ has quit IRC05:33
*** littleidea has quit IRC05:36
*** jamespage_ has joined #openstack-meeting05:36
*** littleidea has joined #openstack-meeting05:39
*** jamespage_ has quit IRC05:40
*** huats has joined #openstack-meeting05:49
*** huats has quit IRC05:49
*** huats has joined #openstack-meeting05:49
*** jakedahn is now known as jakedahn_zz06:19
*** littleidea has quit IRC06:41
*** rafaduran has joined #openstack-meeting06:48
*** ttrifonov_zZzz is now known as ttrifonov06:55
*** rafaduran has quit IRC07:02
*** afazekas has joined #openstack-meeting07:26
*** Mandell has quit IRC07:37
*** EmilienM has joined #openstack-meeting07:42
*** EmilienM has quit IRC08:08
*** EmilienM has joined #openstack-meeting08:09
*** EmilienM has left #openstack-meeting08:10
*** EmilienM has quit IRC08:10
*** EmilienM has joined #openstack-meeting08:10
*** darraghb has joined #openstack-meeting08:20
*** almaisan-away has quit IRC08:23
*** almaisan-away has joined #openstack-meeting08:24
*** almaisan-away is now known as al-maisan08:24
*** EmilienM has quit IRC08:28
*** jhenner has joined #openstack-meeting08:28
*** EmilienM has joined #openstack-meeting08:28
*** jhenner has quit IRC08:41
*** henrynash has joined #openstack-meeting08:41
*** jhenner has joined #openstack-meeting08:41
*** garyk has joined #openstack-meeting08:45
*** EmilienM has quit IRC08:50
*** EmilienM has joined #openstack-meeting08:50
*** EmilienM has quit IRC08:54
*** henrynash has quit IRC08:55
*** henrynash has joined #openstack-meeting08:56
*** zhidong has quit IRC08:57
*** rafaduran has joined #openstack-meeting09:14
*** DuncanT has quit IRC09:16
*** yjiang5_ has joined #openstack-meeting09:20
*** rafaduran has quit IRC09:22
*** rafaduran has joined #openstack-meeting09:24
*** yjiang5_ has quit IRC09:28
*** jhenner1 has joined #openstack-meeting09:30
*** rafaduran has quit IRC09:31
*** jhenner has quit IRC09:31
*** afazekas has quit IRC09:32
*** rafaduran has joined #openstack-meeting09:42
*** afazekas has joined #openstack-meeting09:44
*** rafaduran has quit IRC09:46
*** afazekas has quit IRC09:54
*** jhenner1 has quit IRC09:56
*** rafaduran has joined #openstack-meeting10:07
*** jhenner has joined #openstack-meeting10:08
*** afazekas has joined #openstack-meeting10:10
*** goldfish has joined #openstack-meeting10:19
*** jamespage_ has joined #openstack-meeting10:28
*** littleidea has joined #openstack-meeting10:30
*** jamespage_ has quit IRC10:33
*** littleidea has quit IRC10:37
*** rafaduran has quit IRC10:42
*** maurosr has joined #openstack-meeting10:47
*** al-maisan is now known as almaisan-away10:57
*** guimaluf has joined #openstack-meeting11:04
*** davidh_ has quit IRC11:40
*** dhellmann has joined #openstack-meeting11:44
*** littleidea has joined #openstack-meeting11:46
*** markvoelker has joined #openstack-meeting11:46
*** dhellmann is now known as dhellmann-afk11:55
*** tgall_foo has joined #openstack-meeting11:55
*** tgall_foo has joined #openstack-meeting11:55
*** rafaduran has joined #openstack-meeting11:56
*** ttrifonov is now known as ttrifonov_zZzz12:02
*** ttrifonov_zZzz is now known as ttrifonov12:02
*** anniec has joined #openstack-meeting12:04
*** tgall_foo has quit IRC12:05
*** anniec_ has joined #openstack-meeting12:14
*** anniec has quit IRC12:16
*** anniec_ is now known as anniec12:16
*** almaisan-away is now known as al-maisan12:16
*** krtaylor has joined #openstack-meeting12:28
*** rafaduran has quit IRC12:30
*** ryanpetrello has joined #openstack-meeting12:39
*** milner has joined #openstack-meeting12:45
*** hggdh has joined #openstack-meeting12:47
*** rafaduran has joined #openstack-meeting12:48
*** nijaba has quit IRC12:59
*** nijaba has joined #openstack-meeting13:01
*** s0mik has quit IRC13:04
*** littleidea has quit IRC13:09
*** littleidea has joined #openstack-meeting13:10
*** davidha has joined #openstack-meeting13:11
*** ayoung has joined #openstack-meeting13:17
*** dprince has joined #openstack-meeting13:17
*** hggdh has quit IRC13:28
*** blamar has joined #openstack-meeting13:28
*** blamar_ has joined #openstack-meeting13:30
*** hggdh has joined #openstack-meeting13:32
*** blamar has quit IRC13:33
*** blamar_ is now known as blamar13:33
*** Mandell has joined #openstack-meeting13:33
*** dkehn has joined #openstack-meeting13:33
*** mtreinish has joined #openstack-meeting13:36
*** tongli has joined #openstack-meeting13:38
*** dhellmann has joined #openstack-meeting13:38
*** dhellmann has quit IRC13:38
*** al-maisan is now known as almaisan-away13:39
*** dhellmann-afk has quit IRC13:42
*** armycream has joined #openstack-meeting13:54
*** nijaba has quit IRC13:59
*** nijaba has joined #openstack-meeting14:01
*** dwcramer has joined #openstack-meeting14:01
*** armycream has quit IRC14:07
*** davidha has quit IRC14:09
*** davidhadas has joined #openstack-meeting14:12
*** ogelbukh has quit IRC14:17
*** matiu has quit IRC14:19
*** ogelbukh has joined #openstack-meeting14:20
*** hggdh has quit IRC14:28
*** hggdh has joined #openstack-meeting14:31
*** tgall_foo has joined #openstack-meeting14:32
*** dkehn is now known as dkehn_brb14:35
*** dkehn_brb is now known as dkehn14:37
*** ttrifonov is now known as ttrifonov_zZzz14:41
*** ttrifonov_zZzz is now known as ttrifonov14:41
*** jaypipes has joined #openstack-meeting14:43
*** davidhadas has quit IRC14:45
*** Razique has joined #openstack-meeting14:46
*** cp16net is now known as cp16net|away14:47
*** sandywalsh has joined #openstack-meeting14:49
*** Mandell has quit IRC14:54
*** matiu has joined #openstack-meeting14:58
*** matiu has joined #openstack-meeting14:58
*** nijaba has quit IRC15:00
*** nijaba has joined #openstack-meeting15:01
*** cp16net|away is now known as cp16net15:03
*** dwcramer has quit IRC15:04
*** metral has joined #openstack-meeting15:08
*** davidhadas has joined #openstack-meeting15:11
*** jamespage_ has joined #openstack-meeting15:17
*** dhellmann has joined #openstack-meeting15:20
*** maoy has joined #openstack-meeting15:26
*** jamespage_ has quit IRC15:27
*** rnirmal has joined #openstack-meeting15:29
*** ryanpetr_ has joined #openstack-meeting15:30
*** ryanpetrello has quit IRC15:34
*** Gordonz has joined #openstack-meeting15:37
*** dhellmann has quit IRC15:38
*** Razique has quit IRC15:41
*** milner has quit IRC15:42
*** dwcramer has joined #openstack-meeting15:42
*** s0mik has joined #openstack-meeting15:42
*** metral has quit IRC15:43
*** metral has joined #openstack-meeting15:44
*** dendrobates is now known as dendro-afk15:49
*** jamespage_ has joined #openstack-meeting15:50
*** jamespage_ has quit IRC15:52
*** nijaba has quit IRC16:00
*** dcramer_ has joined #openstack-meeting16:00
*** nijaba has joined #openstack-meeting16:02
*** nijaba has quit IRC16:02
*** nijaba has joined #openstack-meeting16:02
*** jhenner has quit IRC16:02
*** metral_ has joined #openstack-meeting16:02
*** rnirmal has quit IRC16:02
*** afazekas has quit IRC16:02
*** dwcramer has quit IRC16:03
*** metral has quit IRC16:06
*** metral_ is now known as metral16:06
*** arosen has quit IRC16:07
*** oubiwann has joined #openstack-meeting16:15
*** afazekas has joined #openstack-meeting16:18
*** davidhadas has quit IRC16:19
*** jhenner has joined #openstack-meeting16:19
*** p4tuxx has quit IRC16:25
*** littleidea has quit IRC16:27
*** Mandell has joined #openstack-meeting16:33
*** joesavak has joined #openstack-meeting16:33
*** oubiwann has quit IRC16:36
*** gyee has joined #openstack-meeting16:43
*** rnirmal has joined #openstack-meeting16:43
*** nijaba has quit IRC16:48
*** nijaba has joined #openstack-meeting16:50
*** nijaba has quit IRC16:50
*** nijaba has joined #openstack-meeting16:50
*** gatuus has joined #openstack-meeting16:51
*** nijaba has quit IRC16:53
*** nijaba has joined #openstack-meeting16:53
*** nijaba has quit IRC16:53
*** nijaba has joined #openstack-meeting16:53
*** dhellmann has joined #openstack-meeting16:54
*** colinmcnamara has joined #openstack-meeting16:55
*** rafaduran has quit IRC16:59
*** dhellmann_ has joined #openstack-meeting16:59
*** darraghb has quit IRC16:59
*** dhellmann has quit IRC17:00
*** dhellmann_ is now known as dhellmann17:00
*** nijaba has quit IRC17:00
*** gyee has quit IRC17:00
*** nijaba has joined #openstack-meeting17:00
*** nijaba has quit IRC17:00
*** nijaba has joined #openstack-meeting17:00
*** gatuus has quit IRC17:00
*** gyee has joined #openstack-meeting17:01
*** oubiwann has joined #openstack-meeting17:04
*** jhenner has quit IRC17:10
*** lloydde has joined #openstack-meeting17:11
*** jdurgin has joined #openstack-meeting17:11
*** afazekas has quit IRC17:11
*** jakedahn_zz is now known as jakedahn17:15
*** dendro-afk is now known as dendrobates17:16
*** garyk has quit IRC17:17
*** hemna has joined #openstack-meeting17:21
*** dhellmann has quit IRC17:22
*** gatuus has joined #openstack-meeting17:22
*** kindaopsdevy has joined #openstack-meeting17:23
*** dhellmann has joined #openstack-meeting17:24
*** ryanpetr_ has quit IRC17:26
*** ryanpetrello has joined #openstack-meeting17:27
*** kindaopsdevy has quit IRC17:29
*** metral_ has joined #openstack-meeting17:29
*** anniec has quit IRC17:30
*** metral has quit IRC17:32
*** metral_ is now known as metral17:32
*** metral_ has joined #openstack-meeting17:34
*** almaisan-away is now known as al-maisan17:35
*** al-maisan is now known as almaisan-away17:35
*** metral has quit IRC17:37
*** metral_ has quit IRC17:39
*** maurosr has quit IRC17:40
*** maurosr has joined #openstack-meeting17:41
*** s0mik has quit IRC17:46
*** dkehn is now known as dkehn_brb17:53
*** metral has joined #openstack-meeting17:53
*** metral has quit IRC17:55
*** metral has joined #openstack-meeting17:55
*** EmilienM has joined #openstack-meeting17:57
*** kindaopsdevy has joined #openstack-meeting17:57
*** russellb has quit IRC17:59
*** anniec has joined #openstack-meeting18:00
*** jog0 has joined #openstack-meeting18:00
*** nijaba has quit IRC18:00
*** nijaba has joined #openstack-meeting18:01
*** nijaba has quit IRC18:01
*** nijaba has joined #openstack-meeting18:01
*** Gordonz has quit IRC18:01
*** goldfish has quit IRC18:02
*** russellb has joined #openstack-meeting18:03
*** s0mik has joined #openstack-meeting18:03
*** mnewby has joined #openstack-meeting18:09
*** garyk has joined #openstack-meeting18:13
*** russellb has quit IRC18:14
*** rturk has quit IRC18:15
*** rturk has joined #openstack-meeting18:15
*** lloydde has quit IRC18:18
*** jakedahn is now known as jakedahn_zz18:20
*** jakedahn_zz is now known as jakedahn18:21
*** dolphm has joined #openstack-meeting18:25
*** kindaopsdevy has left #openstack-meeting18:35
*** dkehn_brb is now known as dkehn18:41
*** s0mik has quit IRC18:45
*** ayoung has quit IRC18:46
*** jcooley has joined #openstack-meeting18:50
*** mordred has quit IRC18:52
*** mordred has joined #openstack-meeting18:52
*** EmilienM has quit IRC18:53
*** novas0x2a|laptop has quit IRC18:55
*** dolphm has quit IRC19:00
*** nijaba has quit IRC19:01
*** nijaba has joined #openstack-meeting19:01
*** nijaba has quit IRC19:01
*** nijaba has joined #openstack-meeting19:01
*** jcooley has quit IRC19:03
*** nijaba has quit IRC19:05
*** nijaba has joined #openstack-meeting19:25
*** nijaba has quit IRC19:25
*** nijaba has joined #openstack-meeting19:25
*** lloydde has joined #openstack-meeting19:26
*** afazekas has joined #openstack-meeting19:28
*** novas0x2a|laptop has joined #openstack-meeting19:29
*** maurosr has quit IRC19:29
*** maurosr has joined #openstack-meeting19:29
*** dolphm has joined #openstack-meeting19:31
*** gatuus has quit IRC19:32
*** dendrobates is now known as dendro-afk19:32
*** dendro-afk is now known as dendrobates19:33
*** s0mik has joined #openstack-meeting19:33
*** metral_ has joined #openstack-meeting19:36
*** metral has quit IRC19:39
*** metral_ is now known as metral19:39
*** metral has quit IRC19:45
*** littleidea has joined #openstack-meeting19:46
*** littleidea has quit IRC19:46
*** littleidea has joined #openstack-meeting19:47
*** littleidea has left #openstack-meeting19:48
*** russellb has joined #openstack-meeting19:53
*** DuncanT has joined #openstack-meeting19:57
*** BradKlein has joined #openstack-meeting19:59
*** BradKlein has left #openstack-meeting20:01
*** nijaba has quit IRC20:01
*** maurosr has quit IRC20:01
*** nijaba has joined #openstack-meeting20:02
*** ayoung has joined #openstack-meeting20:02
*** nati_ueno has joined #openstack-meeting20:02
*** ayoung has quit IRC20:07
*** anniec_ has joined #openstack-meeting20:07
*** anniec has quit IRC20:10
*** colinmcnamara has quit IRC20:10
*** anniec has joined #openstack-meeting20:12
*** anniec_ has quit IRC20:12
*** anniec_ has joined #openstack-meeting20:14
*** davidhadas has joined #openstack-meeting20:15
*** anniec has quit IRC20:16
*** anniec_ is now known as anniec20:16
*** cp16net is now known as cp16net|away20:16
*** cp16net|away is now known as cp16net20:16
*** termie has joined #openstack-meeting20:18
*** ayoung has joined #openstack-meeting20:20
*** dprince has quit IRC20:21
*** jaypipes has quit IRC20:22
*** ywu has joined #openstack-meeting20:25
*** rkukura has joined #openstack-meeting20:25
*** dkehn is now known as dkehn_brb20:25
*** jcooley has joined #openstack-meeting20:26
*** nijaba has quit IRC20:29
*** dkehn_brb is now known as dkehn20:31
*** EmilienM has joined #openstack-meeting20:31
*** dendrobates is now known as dendro-afk20:33
*** jaypipes has joined #openstack-meeting20:33
*** nijaba has joined #openstack-meeting20:34
*** nijaba has quit IRC20:34
*** nijaba has joined #openstack-meeting20:34
*** nijaba has quit IRC20:34
*** joeswaminathan has joined #openstack-meeting20:35
*** gatuus has joined #openstack-meeting20:37
*** dolphm has quit IRC20:38
*** russellb has quit IRC20:41
*** markvoelker has quit IRC20:42
*** markvoelker has joined #openstack-meeting20:42
*** littleidea has joined #openstack-meeting20:43
*** littleidea has left #openstack-meeting20:43
*** vish1 is now known as vishy20:45
*** littleidea has joined #openstack-meeting20:48
*** littleidea has left #openstack-meeting20:48
*** oubiwann has quit IRC20:49
*** EmilienM has quit IRC20:50
*** colinmcnamara has joined #openstack-meeting20:51
*** oubiwann has joined #openstack-meeting20:51
*** SumitNaiksatam has joined #openstack-meeting20:52
*** jcooley has quit IRC20:52
*** nati_uen_ has joined #openstack-meeting20:52
*** salv-orlando has joined #openstack-meeting20:53
*** danwent has joined #openstack-meeting20:55
*** markmcclain has joined #openstack-meeting20:56
*** gongysh has joined #openstack-meeting20:56
*** nati_ueno has quit IRC20:57
*** jjm3lp has joined #openstack-meeting20:57
danwenthi folks!20:59
*** littleidea has joined #openstack-meeting20:59
markvoelkero/20:59
markmcclainhi20:59
danwentback to meeting in the virtual world :)20:59
salv-orlandohello people20:59
danwenti guess after the meeting we'll need to meet at a virtual bar and have virtual drinks… sounds like less fun20:59
*** nati_ueno has joined #openstack-meeting20:59
*** adjohn has joined #openstack-meeting20:59
gongyshhi20:59
nati_uenohi20:59
garykhi guys21:00
danwentok, let's get started, since we have a ton to cover21:00
gongyshhope all guys are back safe.21:00
*** amotoki has joined #openstack-meeting21:00
danwent#startmeeting quantum21:00
openstackMeeting started Mon Oct 22 21:00:46 2012 UTC.  The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
openstackThe meeting name has been set to 'quantum'21:00
danwentgongysh, did you or garyk get the award for longest distance traveled?21:01
danwentprobably garyk?21:01
gongyshno21:01
*** KurtMartin has joined #openstack-meeting21:01
garyki had 8 hours at heathrow :)21:01
danwenthaha21:01
*** EmilienM has joined #openstack-meeting21:01
danwent#link agenda: http://wiki.openstack.org/Network/Meetings21:01
*** sasha_ has joined #openstack-meeting21:01
rkukurahi21:01
amotokihi21:01
salv-orlandoI got flu on the plane :/21:01
danwentwe have a ton to cover, so let's get going21:01
sasha_hi21:01
danwentok, apologies for starting the discussion on who had the worst flight :P21:02
danwent#info Grizzly release schedule has been finalized http://wiki.openstack.org/GrizzlyReleaseSchedule21:02
garyki had the worst and the longest21:02
danwentthe big news is that there is no big news21:02
*** nati_uen_ has quit IRC21:02
danwentrelease schedule is following pretty much the same pattern as folsom21:02
danwentthree milestones, fairly long RC time.  two weeks between release and next summit.21:03
garykif possible we should also try and contain bugs21:03
danwentgaryk: ?21:03
danwentgaryk: sorry, don't understand the last statement21:04
garykdanwent: it seems like lately there are quite a few bugs opened. we should try and make sure that the open bugs stays low21:04
garykdanwent: does that make sense21:04
danwentgaryk: ah yes, in fact, we'll talk about that later down on the agenda21:04
garykok, sorry for the interruption21:04
danwentas I wanted to discuss the set of bugs open against folsom and when we should target a stable folsom update21:04
*** bencherian has joined #openstack-meeting21:04
danwentno worries21:04
danwent#topic Grizzly-121:05
*** openstack changes topic to "Grizzly-1"21:05
danwentso the Grizzly-1 date is actually just a month away21:05
*** dendro-afk is now known as dendrobates21:05
danwentso I wanted to spend a chunk of this meeting making sure we have blueprints created for key community tasks needed early in grizzly21:05
danwentas rkukura pointed out during the summit, there's a need for us to do a better job as a community creating blueprints21:06
gongyshagree21:06
*** metral has joined #openstack-meeting21:06
nati_ueno+121:06
danwenta blueprint should be good enough that a reveiwer can read it before reviewing the code and understand what you are trying to achieve, and roughly how you plan to achieve it21:06
*** zhuadl has joined #openstack-meeting21:06
garyk+121:06
*** bencherian has quit IRC21:07
markmcclain+121:07
garykit will certainly help the review process21:07
salv-orlandosalv_orlando: +1 (this also implies we as cores must review blueprints too)21:07
garykand documentation21:07
danwentlet's all hold each other to a higher standard.  If you go to review something that is bigger than a bug fix, and you find that the blueprint is not sufficient, moving forward we should as the feature creator to improve the blueprint before reviewing21:07
rkukuraearly feedback on the blueprints is also important, well before the review21:07
danwentgaryk: agreed.  one idea i had been thinking about was requiring docs along with a change-set, but that is hard in practice.21:07
danwentgaryk: but i'm open to ideas there… leaving all docs to the end of the release is bad21:08
garykdanwent: if we follow the suggestions for the detailed blueprints then it should be easier to port to docs later21:08
salv-orlandodanwent, garyk: that is feasible IMHO. Just a matter of establishing rules for things.21:08
garyksalv-orlando: agreed21:09
gongysha good spec is ok.21:09
salv-orlandoA desirable side effect would be avoiding feature creep21:09
danwentsalv-orlando: are you suggesting docs in the admin guide before code is committed, or just a blueprint that people thing is good enough to turn into docs?21:09
*** anniec_ has joined #openstack-meeting21:10
*** mtreinish has quit IRC21:10
*** anniec_ has quit IRC21:10
*** tgall_foo has quit IRC21:10
danwentthe issue is that often features arrive in several commits, making the former difficult.21:10
salv-orlandoIdeally one would like to have the documents before the code is merged. Then this could be evaluated case by case21:10
*** anniec has quit IRC21:10
salv-orlandodanwent: agree. Let's see what we can do offline21:11
*** anniec_ has joined #openstack-meeting21:11
*** maoy has quit IRC21:11
*** vbannai has joined #openstack-meeting21:11
danwentok.  salv-orlando, can you put together a proposal for this?  It sounds like something we should have on the quantum development wiki page for (how do i implement a feature?)21:11
*** russellb has joined #openstack-meeting21:12
*** vbannai has joined #openstack-meeting21:12
*** ijw1 has joined #openstack-meeting21:12
danwentgaryk: sounds like you're interested as well.  perhaps you and salv-orlando can coordinate21:12
garykdanwent: ok21:12
gongyshI will review. Haha21:12
salv-orlandodanwent: sure21:12
danwentgongysh: :)21:12
danwentOk, so i'm going to quickly move through some  of the quick community topics, to identify who will be putting blueprints together on the key community topics discussed at teh summit21:13
danwentCI gating (nati_ueno ?  mnewby ?)21:13
danwentdo we have a blueprint that we are using for this?21:14
nati_uenoI'm working on execise.sh to work21:14
mnewbydanwent: Not sure21:14
nati_uenodanwent: We can reuse this https://blueprints.launchpad.net/quantum/+spec/quantum-gate21:14
garykdanwent: dan prince is intersted in getting smokestack working with quantum21:14
nati_uenoPlease assign it to me21:14
danwentok, this will be the top focus of every quantum team meeting until we do.21:14
danwentor rather, until we have a gate running with quantum21:14
garyki think that we should maybe invest in the smokestack like nova.21:14
mnewbygaryk: What is smokestack executing?21:15
nati_uenogaryk: +1 for smokestack21:15
danwentnati_ueno: ok, updated the BP, assigned it to you, and updated other fields21:15
mnewbygaryk, nati_ueno: what is the relationship between smokestack and tempest?21:15
garykmnewby: as far as i understand it runs installation packages, puppet moduels etc. launches vm's and test traffic between them. i can ask dan for extra details21:15
nati_uenomnewby: Yes. It is another CI process.21:16
danwentwill smokestack continue to run even once we have full tempest integration?21:16
danwentI am not sure if they are duplicate efforts, or have different goals.21:16
mnewbyit sounds like duplicative21:16
garykhttp://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&ved=0CCsQFjAA&url=http%3A%2F%2Fwiki.openstack.org%2Fsmokestack&ei=ybeFUML3JI3LtAbfjICgBw&usg=AFQjCNGcZzE9UMz-BrrfJsR4-iWxGspmaQ21:17
mnewbyit's useful, but if developers can't run the tests themselves i question it's longterm value21:17
mnewbyOh well, I guess we do both.21:17
garyki think that i should be used for our gating.21:18
mnewbyI'm more interested in single-host (devstack) testing (at least initially), but for gating we'll need all of the aboev.21:18
danwentgaryk: can you ask dan prince about the long-term direction of the openstack community regarding tempest vs. smokestack?  What i've been told to date is that our efforts should be focused on tempest (though i'll be grateful for more testing, regardless of platform)21:20
garykdanwent: sure.21:20
mnewbyThe annoyance is that the tests are in ruby.21:20
*** jjm3 has joined #openstack-meeting21:20
mnewby(for smokestack)21:20
gongyshI need a facility that make sure each patch will not break our dear quantum in the end.21:20
*** littleidea has quit IRC21:20
*** ek6 has joined #openstack-meeting21:20
danwentgongysh: that is what gating does.  what i've been told so far is that the CI team is moving toward gating on tempest in the long-term21:21
danwentthough in the short-term they also gate on devstack exercise scripts + smokestack (I believe)21:21
danwentok, got to keep moving.  nati_ueno: any blockers in terms of gating?21:22
danwentjust fixing issues with exercise.sh?21:22
nati_uenoI think just debug exesice.sh21:22
nati_uenoYes21:22
nati_uenoI'll request merge for devstack until this week21:22
danwentdo you anticipate having that done soon?  I'd say to escalate any issues you're having to the entire core team, as its critical we get this going21:22
nati_uenoYes soon21:23
danwentok, garyk and I are both core devstack devs, so we should be able to review quickly.21:23
danwentok, next topick21:23
danwentrelated: tempest tests21:23
danwentnati_ueno, maru  blueprints here?21:23
danwentothers?21:23
nati_uenorelated https://blueprints.launchpad.net/quantum/+spec/quantum-system-test ?21:23
nati_uenoMaybe, we should have the blueprint in QA team project21:24
mnewbyI would agree21:24
nati_uenohttps://blueprints.launchpad.net/tempest21:24
danwentnati_ueno: yes, i'm fine with the BP being there, just really looking to make sure someone is working on it.21:24
nati_uenoOK I'll create one21:24
danwentok, please send it out to the team so we can track.  there was also someone from rackspace who said he would have developers for this.21:25
danwentanyone remember the name?  I'll have to look it up.21:25
mnewbydaryl21:25
danwenthe was at the meeting, sitting behind me.21:25
*** joesavak has quit IRC21:25
nati_uenodanwent: gotcha21:25
danwentmnewby: thx.  anyone know daryl's email or irc?21:26
danwentwas he on that old thread we had going?21:26
mnewbyDaryl Walleck <daryl.walleck@rackspace.com>21:26
danwentthx21:26
danwentOk, let's loop him into the discussion21:27
danwentmnewby: do you expect to create a BP, or just work with daryl + nachi?21:27
mnewbydanwent: I haven't really worked with BPs, what is requied?21:27
nati_uenoDone https://blueprints.launchpad.net/tempest/+spec/quantum-tempest21:28
danwentBPs are just a feature/bug-tracking tools where you describe a new capability you will be adding to the system.21:28
danwentas we mentioned above, for features, they should include use cases, design, and doc for configuring + using the feature.  Might be slightly different for test cases though.21:29
mnewbyOk21:29
danwentI think during the summit we agreed that this work would be discussed during the weekly temptest meetings, but it would be good if someone reported back progress to the quantum meeting21:30
danwentas having good system test is critical to the success of quantum long-term, especially as it grows in complexity.21:30
nati_uenoOK I'll attend both of meeting and report it21:30
danwentok, got to keep moving21:30
danwentnati_ueno: thx21:30
danwentdatabase upgrade: markmcclain , salv-orlando21:30
markmcclainI can help with it21:31
danwenthad a work item from summit that markmcclain was proposing a mechanism other than sqlalchemy-migrate21:31
salv-orlandoI haven't done anything beyond looking at how we can use alembic21:31
salv-orlandofor solving issue with plugin-specific upgrade paths21:31
danwentlet's get a BP together on this that describe the trade-offs and a design21:31
danwentwe need to get this infrastructure in before we start significantly changing the DB21:31
markmcclain+121:32
salv-orlandonp. markmcclain - I'll send you an email for stealing some of your time on IRC21:32
*** arosen has joined #openstack-meeting21:32
garykdanwent: salv-orlando: i was thinking that we have the user first upgrade to folsom and then convert to quantum. is this relevant21:32
danwentok, can one of you create a BP and assign to G-1 with essential priority?21:32
salv-orlandodanwent: sure21:32
danwentgaryk: you're talking about converting from nova-network to quantum?21:32
salv-orlandogaryk: we are looking at Quantum to Quantum upgrades at the moment21:32
danwentthat's slightly different, but also useful21:33
garykdanwent: yes. salv-orlando: ok21:33
salv-orlandoperhaps we can have a separate blueprints from nova-network to Quantum migration21:33
*** EmilienM has left #openstack-meeting21:33
danwenti had it on the agenda for today, but then took it off thinking we shouldn't have time.21:33
danwentbut if you want to create a nova-network conversion blueprint, i think that makes sense.21:33
*** nijaba has joined #openstack-meeting21:33
danwentgaryk: can you make a bp for this?  either way, its good to track it.21:34
*** anniec_ has quit IRC21:34
danwentnova gaps21:34
garykdanwent: sure21:34
danwentthree sub-topics21:34
danwentsecurity groups (arosen / nachi)21:34
*** anniec has joined #openstack-meeting21:34
danwentsecurity groups api is already in review, as it was a miss from folsom.21:34
gongyshwe have much talk for security groups in design summit session.21:35
danwentarosen, i haven't seen the blueprint, but probably a good idea to freshen it up, given the above conversation21:35
gongyshwe should have a   wrap up.21:35
arosendanwent:  will do21:35
danwentgongysh: let's have the discussion around the blueprint21:35
gongyshyes. pointint to the etherpad21:35
danwentaaron, i'm guessing the blueprint needs to be expanded to our new grizzly standards.21:35
amotokiI think https://blueprints.launchpad.net/quantum/+spec/quantum-security-groups is related to this.21:36
garykwith gongysh reviewing21:36
danwentnote: there is a ton of stuf we could do around firewalling and filtering.21:36
gongyshgaryk: haha. bad guy.21:36
danwentbut the most critical thing we HAVE to accomplish in grizzly is getting security groups in quantum with support for overlapping IPs.21:37
danwentthat was a black-eye for quantum in folsom.21:37
ijw1And for multiple interfaces in some sensible fashion.21:37
danwentijw1: agreed.  that's already tackled in aaron's proposal as well.21:37
danwentok, multi-host21:37
amotokiIt is a good idea to merge arosen's security group API first before moving the next.21:38
ijw1Where's Aaron's proposal?21:38
danwentamotoki: merge with what?21:38
amotokidanwent: the current patch under review from arosen21:38
danwentijw1: this was actually covered at the folsom summit for folsom, he can point to the preso21:38
danwentarosen: does BP link to dave's presentation?21:38
arosenijw1:  I'll put up the openstack-manual documentation i'm working on that should help shed some light as well.21:39
arosendanwent:  yes it does.21:39
danwentamotoki: ah, i agree.21:39
danwentI'd like to make sure the base security groups stuff is in very early, which is why arosen and nati_ueno are working on it already.21:39
arosenThis is the review:  https://review.openstack.org/#/c/14262/21:39
danwentok, only 20 mins left and much to cover :(21:39
danwentquickly, multi-host21:39
nati_uenoI didn't started yet. Just play with firewall.py21:40
danwentwhat is active blueprint for this, and who owns it?21:40
nati_uenoI updated bp for multi-host https://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp21:40
danwentnati_ueno: this is just for dhcp?21:40
gongyshhttps://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp21:40
nati_uenoNo not just dhcp21:40
nati_uenoI should update it21:40
danwentnati_ueno: i'm also a bit worried that you seem to be volunteering for all of the blueprints21:40
ijw1What of the routing aspects of multihost?21:40
ijw1Oh, sorry, bit late with that ;)21:40
danwentnati_ueno: can you update BP name to avoid confusion?21:41
nati_uenodanwent: I got it21:41
danwentgongysh: are you contributing to multi_host stuff as well?21:41
gongyshnati_ueno: don't u want me to do it?21:41
nati_uenodanwent: It seem I can't update bp id21:41
danwentah, launchpad...21:41
nati_uenogongysh: Ether way is OK :)21:41
nati_uenogongysh: Do you want to do this one?21:42
danwentnati_ueno: since you have so much on your plate, having gongysh head it up makes sense to me.21:42
nati_uenodanwent: I got it21:42
gongyshnati_ueno: I hope I can help u to do it.21:42
danwentnati_ueno: title of blueprint is good…, mentions both dhcp and L221:42
danwentL321:42
nati_uenoI updated whiteboard today21:43
danwenti updated the link: https://blueprints.launchpad.net/quantum/+spec/quantum-multihost21:43
danwentok, keep moving21:43
nati_uenoOhh It can be updated!21:43
danwentnova gaps, metadata. markmcclain, you or carlp handling this?21:43
markmcclainI'm working on metadata21:43
markmcclainI hoped to have code today… looks like tomorrow21:43
danwentgreat, this will be a huge help21:44
danwentwe already have a bp targeted for G-1 for that21:44
danwentgaryk: planning on creating a blueprint on the nova/quantum flow and vif-plugging stuff?21:44
garykdanwent: yes, i'll do it tomorrow21:44
danwentgaryk: cool.  for the LB plugin in particular, I see that as essential.21:45
garykdanwent: agreed21:45
ijw1garyk: drop me a mail when you've done it, ta21:45
garykijw1: will do21:45
garykijw1: as long as you do not heckle21:45
ijw1aww21:45
danwentsalv-orlando: are you creating blueprints around the API infrastructure for higher-level services like LBaaS?21:46
salv-orlandodanwent: yep21:46
danwentI think rkukura is likely interested in helping with API extension framework stuff as well.21:46
gongyshdoes the separate LBaas will use our API infra?21:46
*** arosen has quit IRC21:47
markmcclainI think it should21:47
danwentgongysh: higher level services will be able to be loaded and run indepdent of the main plugin, and that's something we don't really support now21:47
danwentroman (spelling?) from mirantis had a good slide that discussed this at the summit21:47
ijw1I think a LBaaS will plug into quantum as a client; I don't necessarily know that it's a part of the same API endpoint.21:47
*** arosen has joined #openstack-meeting21:47
gongyshthen what do we mean by API infrastructure for higher-level services like LBaaS?21:48
danwentijw1: current plan is same endpoint, though I'm not sure the discussion is final.21:48
salv-orlandoI think we talked about this a bit :)21:48
danwentgongysh: perhaps best to take a look at salv-orlando's blueprint, and at the sessions he and sasha presented21:48
salv-orlandosalv-orlando: I will start an email discussion offline once the blueprint is filed21:48
gongyshok. I will talk to salv offline.21:49
danwentanyway, we have 12 mins left in the meeting, so let's leave those details for offline discussion21:49
danwentthx21:49
danwentclient-lib + cli enhancements21:49
*** dolphm has joined #openstack-meeting21:49
danwenti assume gongysh and markmcclain will be coordinating here21:49
markmcclainyep21:49
gongyshsure.21:49
danwentnote, these should actually be created as blueprints in the python-quantumclient project21:49
markmcclainwill do21:49
danwentbut we will discuss them in this meeting21:50
danwenthorizon next steps.  amotoki, nati_ueno ?  filing these under horizon?21:50
amotokiBP is not filed yet.21:50
danwentbut please send a note to the quantum team or post the BPs next meeting so peopel are aware of them.21:50
nati_uenoI got it21:50
amotokidanwent: sure.21:50
danwentIPv6 stuff.  markmcclain, you will file?21:50
markmcclainyes21:51
amotokinati_ueno: I will send you a mail later.21:51
markmcclainand have a few folks who'd said that help with code21:51
nati_uenoamotoki: gotcha21:51
danwentOk.  rkukura where you planning on doing a BP for your modular plugin stuff in G-1?21:51
rkukurayes21:51
danwentOk, please create and target.21:51
rkukurafirst steps21:51
danwentI know there are other items that people want to do in G-1, and that's fine, I just wanted to cover key community wide topics here.  Are there other items that we think should be priority high or above for G-1?21:52
danwent(note: i'm leaving the LBaaS stuff out for now, as they are doing a separeate meeting)21:52
nati_uenoVPN stuff is not G1?21:52
nati_uenoand Service enhancement21:52
markmcclainVPN is a blueprint I'm going to write21:53
danwentnati_ueno: I figure we had a lot on our plate for G-1.  If mark things we can tackle in in G-1 as well, that's great21:53
amotokiregarind firewalling, i plan to write a document during G-1.21:53
danwentbut I was thinking other services would probably wait until G-2 before they were a major community focus.21:53
*** dolphm has quit IRC21:53
nati_uenodanwent:  I got it21:53
danwent#info: as a heads up for those interested in LBaaS.  they have a separeate weekly meeting on thursday mornings now, see: http://wiki.openstack.org/Quantum/LBaaS21:54
salv-orlandodanwent: my plea is for getting service insertion complete in G-1 before moving to the other services21:54
sasha_I will also write a blueprint for L3/services so that it is there for comments ... and also talk offline to Salvatore21:54
danwentsalv-orlando: that's a good point.21:55
markmcclain+1 to get service insertion in early21:55
garyk+121:55
danwentamotoki: feel free to put together a BP, but I want to make sure we have main service insertion stuff somewhat settled before we actually start coding on all types of higher-level services.21:55
danwentsalv-orlando: ok, let's jack up the priority of that BP for G-121:56
danwentand make sure we really focus effort there.21:56
amotokidanwent: I feel so too.21:56
danwentok, 4 minutes :(21:56
garykdanwent: lets talk about bugs next week21:56
danwentok, sounds like we'll need to leave the discussion of sub-teams to tomorrow, but I just wanted to send out this link with some of my thoughts: https://etherpad.openstack.org/grizzly-quantum-wrapup21:56
danwentgaryk: agreed, let's just highlight the list21:57
garykok21:57
nati_uenoWhere can I know sub-teams?21:57
danwent#info here is list of current bugs tagged for possible folsom-backport: https://bugs.launchpad.net/quantum/+bugs?field.tag=folsom-backport-potential21:57
danwentnati_ueno: all info i've put together so far is on that etherpad link.  feel free to comment there and we'll talk about it next week.21:57
danwentgaryk is our master of folsom stable21:57
garykdanwent: there is no beer team!21:57
nati_uenodanwent: I got it21:57
nati_uenolol21:58
salv-orlandodanwent: more than happy to start rolling on service insertion (and there goes my sleep)21:58
danwentplease help him out by making sure all bugs relevant to folsom are tagged with folsom-backport-potential21:58
danwentwe should also start thinking about a date for a folsom-stable release update21:58
danwentlet's nail that down next week, along with a list of bugs we think must be fixed in that release.21:59
danwentgaryk: sound reasonable?  anything to add?21:59
garykdanwent: not at the moment. tomorrow i'll go over the bugs etc.21:59
danwentgaryk: awesome21:59
danwent#topic open discussion21:59
*** openstack changes topic to "open discussion"21:59
danwentI will send an email to the list with my thoughts on how to handle possible influx of plugins + drivers from vendors in grizzly22:00
gongyshdanwent, nati: can u agree to assign multi-host to me?22:00
danwentso far we have had a policy that any plugin must has a core dev who offers to stand behind it22:00
danwentgongysh: yes, I will22:00
nati_uenogongysh: I agree22:00
*** littleidea has joined #openstack-meeting22:00
nati_uenogongysh: Thanks!22:00
gongyshU are welcome22:00
danwentok, anything else we need to discuss here before we sign off?22:00
gongyshgood nati_ueno.22:01
gongyshpagination?22:01
gongyshI hope pagination can get in for G122:01
*** markvoelker1 has joined #openstack-meeting22:01
danwentsalv-orlando: can you chat with gongysh about pagination after the meeting?  I know you had thoughts on nit.22:01
danwentit22:01
*** joeswaminathan has quit IRC22:01
danwentok, hope you all had a fun summit, now its back to work :)22:01
salv-orlandodanwent, gongysh: sure22:01
danwent#endmeeting22:01
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:01
openstackMeeting ended Mon Oct 22 22:01:55 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/quantum/2012/quantum.2012-10-22-21.00.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/quantum/2012/quantum.2012-10-22-21.00.txt22:01
*** nijaba has quit IRC22:02
openstackLog:            http://eavesdrop.openstack.org/meetings/quantum/2012/quantum.2012-10-22-21.00.log.html22:02
danwentthanks all22:02
danwentAh…. and please see salv-orlando's note about starting up review days again!22:02
markvoelker1Night all!22:02
garykthanks and good night22:02
danwentsalv-orlando: thanks for sending out that note22:02
salv-orlandogongysh: I am out for a coffee will be back in 5 minutes22:02
salv-orlandodanwent: np22:02
gongyshok. enjoy.22:02
*** markvoelker1 has quit IRC22:02
danwentgongysh: assigned to you https://blueprints.launchpad.net/quantum/+spec/quantum-multihost22:03
gongyshok, thanks22:04
*** markvoelker has quit IRC22:05
*** rnirmal has quit IRC22:08
*** ek6 has quit IRC22:09
gongyshsalv-orlando: https://blueprints.launchpad.net/quantum/+spec/support-pagination-in-api-v222:09
salv-orlandogongysh: about pagination, I think we should look at the problem from the server side first and then from the client side.22:12
gongyshyes.22:12
salv-orlandoTo give you the general picture, from the server-side other openstack project use initial_token and offset mechanism22:12
gongyshnova and glance both have a implementation.22:12
salv-orlandowhich works fairly well with db_queries22:13
*** russellb has quit IRC22:13
gongyshyes22:13
salv-orlandoon the other hand, I've heard people from Horizon complaining that this was not the best approach for them (perhaps you've heard them too).22:14
salv-orlandoIt seems they like the page_num + page_size approach22:14
gongyshI heard some.22:15
*** gyee has quit IRC22:15
*** nati_ueno has quit IRC22:15
ijw1Matter of taste, I'd argue; I prefer the proposed solution but being in step with everyone else is probably more valuable (if everyone else has, in fact, done it the other way)22:15
salv-orlandoAnd I am not sure we want to implement this kind of mechanism on the server. What are your thoughts? For the server side I would stick with token + offset22:15
*** russellb has joined #openstack-meeting22:15
salv-orlandoijw: I totally agree with you.22:16
salv-orlandotoken + offset if what nova and glance do22:16
ijw1salv-orlando: what do you mean by token + offset?22:16
gongyshI think we should use the same way nova and glance adopts.22:16
*** nati_ueno has joined #openstack-meeting22:16
salv-orlandoYou specificy the id of the first element you want to retrieve (the token) and the number of subsequent elements that should be returned22:16
ijw1so not offset but length then.22:16
ijw1(arguably)22:16
ijw1Well, I can see why you might want to do that but it's not terribly SQL-compatible.22:17
salv-orlandoijw: sorry my english skills drop a lot after 11PM22:17
ijw1SELECT * FROM TABLE OFFSET 10 LIMIT 10 (or whatever it is, and it varies slightly by backend) is the standard SQL statement I've seen22:17
gongyshit is mysql way.22:18
ijw1Does it also work efficiently in PgSQL?22:18
salv-orlandoI actually want to do whatever takes the minor toll on the db.22:18
gongyshI don't know, but I think the sqlalchemy will help us.22:18
gongyshit should hide the SQL dialect.22:19
salv-orlandoOn the token based approach, I do not see a solution that would prevent you from going through an awful lot of record each time22:19
salv-orlandobut that's probably me just being dumb22:19
danwentgongysh + salv-orlando: were both of you in horizon discussion when they talked about new pagination model?22:20
ijw1gongysh: I see nothing obvious in MySQL that says it works by key.  It seems to be LIMIT offset, length22:20
salv-orlandodanwent: I was there22:20
ijw1salv-orlando: I'm with you on that22:20
danwentsalv-orlando: ok, great, just wanted to make sure22:20
salv-orlandoit seems Horizon people would like the page size/page number approach22:20
ijw1I've done this sort of stuff many times before and key + length sounds bizarre to me, it's usually page + length or offset + length22:21
ijw1(plus ensuring that your sort includes the ID row)22:21
salv-orlandoijw1: I've always done it that way too22:21
ijw1I'm reasonably confident that the first option is really really slow and the latter two are supported directly by most DBs22:21
salv-orlandoactually I implemented pagination in the style currently used by nova for Essex - did not get merged for time constraints.22:22
salv-orlandoUnfortunately the code is now lost, I presume22:22
ijw1Does anything else do pagination at present?22:22
ijw1Or is it a good idea waiting to happen?22:22
salv-orlandonova definitely supports that for server list22:23
gongyshglance does well too.22:23
gongyshSo I think what we will do is to wrap up how they do this and learn from them.22:23
salv-orlandoanyway… is there any significant cons wrt adopting the page size + page number (i.e.: OFFSET + LIMIT) approach?22:24
salv-orlandoI don't see any, but perhaps gongysh might spent some time looking at existing implementations and compare them with the OFFSET/LIMIT approach22:24
ijw1I prefer object offset, personally, as it's a tiny bit more flexible (you can switch page size and you don't have to recalc the offset) but I would go with that method.  And nova is loading all items and doing the offset, checking the source22:25
gongyshsalv-orlando: do u want to implement it in a distinguished way in quantum?22:25
ijw1https://github.com/openstack/nova/blob/master/nova/api/openstack/common.py#L198 e.g.22:26
gongyshBUT maybe glance and nova are using different ways.22:26
salv-orlandonot unless we are able to prove that a different implementation will give an advantage22:26
gongyshok.22:26
ijw1I imagine it's possible to write a function that takes an SQL query and adds the limits to it, one that could even end up in openstack-common22:26
ijw1(certainly I could do this with the ORMs I've used before now)22:26
gongyshI will have a investigation and report to core team.22:27
salv-orlandoI think marker is actually the identifier of a token22:27
gongyshand then see what and how we will do.22:27
*** nati_ueno has quit IRC22:27
gongyshsalv-orlando: is that ok?22:28
*** sandywalsh has quit IRC22:28
salv-orlandogongysh: sounds good to me...22:28
ijw1gongysh :whatever you find ned to go to the mailing list because if it sucks for Quantum it sucks for everything.22:28
gongyshijw1: my bottom line is if it sucks for everything, it sucks for Quantum.22:29
gongyshWe will not allow Quantum  sucks first22:30
ijw1I just don't want to see other people wasting time, that's all22:31
gongyshsee u. back to bed22:31
gongyshI will send out to mailing list as well.22:31
*** nati_ueno has joined #openstack-meeting22:31
*** vbannai has quit IRC22:32
*** dcramer_ has quit IRC22:33
*** cp16net is now known as cp16net|away22:37
*** nati_ueno has quit IRC22:45
*** tongli has quit IRC22:46
*** cp16net|away is now known as cp16net22:48
*** nati_ueno has joined #openstack-meeting22:51
*** tgall_foo has joined #openstack-meeting22:56
*** salv-orlando has left #openstack-meeting22:56
*** dkehn is now known as dkehn_afk22:59
*** davidhadas has quit IRC22:59
*** zhuadl has quit IRC22:59
*** ywu has quit IRC23:00
*** ywu has joined #openstack-meeting23:00
*** markmcclain has quit IRC23:00
*** dhellmann has quit IRC23:01
*** sasha_ has quit IRC23:01
*** sandywalsh has joined #openstack-meeting23:05
*** nati_ueno has quit IRC23:07
*** jakedahn is now known as jakedahn_zz23:08
*** cp16net is now known as cp16net|away23:09
*** metral has quit IRC23:10
*** littleidea has quit IRC23:10
*** lloydde has quit IRC23:12
*** cp16net|away is now known as cp16net23:13
*** colinmcnamara has quit IRC23:26
*** jakedahn_zz is now known as jakedahn23:29
*** krtaylor has quit IRC23:31
*** dcramer_ has joined #openstack-meeting23:34
*** cp16net is now known as cp16net|away23:34
*** KurtMartin has quit IRC23:38
*** tgall_foo has quit IRC23:54
*** jakedahn is now known as jakedahn_zz23:58

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