Wednesday, 2015-06-10

*** bradjones has joined #openstack-meeting-300:00
*** bradjones has quit IRC00:00
*** bradjones has joined #openstack-meeting-300:00
*** dims has quit IRC00:03
*** dims has joined #openstack-meeting-300:03
*** stevemar has quit IRC00:05
*** bknudson has joined #openstack-meeting-300:07
*** marun has joined #openstack-meeting-300:08
*** Networkn3rd has quit IRC00:12
*** puranamr has quit IRC00:14
*** markvoelker has joined #openstack-meeting-300:21
*** Rockyg has quit IRC00:22
*** markvoelker has quit IRC00:26
*** Swami has quit IRC00:28
*** bryan_att has quit IRC00:43
*** zhenguo has joined #openstack-meeting-300:47
*** Sukhdev has quit IRC01:03
*** bpokorny has quit IRC01:11
*** alexsyip has quit IRC01:13
*** tobe has joined #openstack-meeting-301:18
*** markvoelker has joined #openstack-meeting-301:22
*** dims has quit IRC01:23
*** shwetaap has joined #openstack-meeting-301:26
*** markvoelker has quit IRC01:27
*** stanzgy has joined #openstack-meeting-301:40
*** esp has joined #openstack-meeting-301:42
*** zz_natorious is now known as natorious01:45
*** tqtran_ has quit IRC01:46
*** bknudson has quit IRC01:46
*** s3wong has quit IRC01:48
*** sarob has quit IRC01:50
*** shwetaap has quit IRC01:52
*** yamahata has quit IRC02:09
*** VW has joined #openstack-meeting-302:10
*** dims has joined #openstack-meeting-302:12
*** fitoduarte has joined #openstack-meeting-302:16
*** bryan_att has joined #openstack-meeting-302:16
*** dims has quit IRC02:23
*** fallenpegasus has quit IRC02:26
*** natorious is now known as zz_natorious02:26
*** fallenpegasus has joined #openstack-meeting-302:30
*** banix has quit IRC02:31
*** fallenpegasus has quit IRC02:32
*** fallenpegasus has joined #openstack-meeting-302:32
*** VW has quit IRC02:39
*** bradjones has quit IRC02:52
*** bradjones has joined #openstack-meeting-302:53
*** bradjones has quit IRC02:53
*** bradjones has joined #openstack-meeting-302:53
*** julim has joined #openstack-meeting-302:54
*** julim has quit IRC02:59
*** rushiagr_away is now known as rushiagr03:05
*** sridhar_ram has joined #openstack-meeting-303:07
*** markvoelker has joined #openstack-meeting-303:11
*** markvoelker has quit IRC03:16
*** rushiagr is now known as rushiagr_away03:25
*** sigmavirus24 is now known as sigmavirus24_awa03:32
*** puranamr has joined #openstack-meeting-303:37
*** coolsvap|afk is now known as coolsvap03:42
*** ivar-laz_ has quit IRC03:51
*** Sukhdev has joined #openstack-meeting-303:51
*** rushiagr_away is now known as rushiagr04:05
*** rushiagr is now known as rushiagr_away04:05
*** rushiagr_away is now known as rushiagr04:06
*** nelsnelson has joined #openstack-meeting-304:30
*** yushiro has joined #openstack-meeting-304:34
*** amotoki_ has joined #openstack-meeting-304:40
*** nelsnelson has quit IRC04:43
*** nelsnelson has joined #openstack-meeting-304:44
*** amotoki_ has quit IRC04:46
*** amotoki is now known as amotoki_04:46
*** amotoki_ has quit IRC04:49
*** amotoki has joined #openstack-meeting-304:49
*** sridhar_ram has quit IRC04:50
*** rushiagr is now known as rushiagr_away04:55
*** puranamr has quit IRC04:57
*** puranamr has joined #openstack-meeting-304:58
*** puranamr has quit IRC04:59
*** markvoelker has joined #openstack-meeting-305:00
*** puranamr has joined #openstack-meeting-305:03
*** markvoelker has quit IRC05:04
*** lazy_prince has joined #openstack-meeting-305:04
*** fallenpegasus has quit IRC05:08
*** wojdev has joined #openstack-meeting-305:09
*** yushiro has quit IRC05:15
*** rushiagr_away is now known as rushiagr05:25
*** nkrinner has joined #openstack-meeting-305:32
*** stendulker has joined #openstack-meeting-305:37
*** amotoki_ has joined #openstack-meeting-305:41
*** puranamr has quit IRC05:44
*** fitoduarte has quit IRC05:45
*** amotoki_ has quit IRC05:46
*** wojdev has quit IRC05:50
*** yamamoto has quit IRC05:50
*** Sukhdev has quit IRC05:51
*** yamamoto has joined #openstack-meeting-305:52
*** wojdev has joined #openstack-meeting-305:55
*** wojdev has quit IRC05:59
*** jtomasek has joined #openstack-meeting-306:00
*** belmoreira has joined #openstack-meeting-306:01
*** marun has quit IRC06:03
*** puranamr has joined #openstack-meeting-306:05
*** mrunge has joined #openstack-meeting-306:06
*** jcoufal has joined #openstack-meeting-306:08
*** puranamr has quit IRC06:10
*** scheuran has joined #openstack-meeting-306:17
*** yamamoto has quit IRC06:17
*** Sukhdev has joined #openstack-meeting-306:19
*** scheuran_ has joined #openstack-meeting-306:20
*** scheuran_ has quit IRC06:20
*** scheuran has quit IRC06:21
*** sahid has joined #openstack-meeting-306:22
*** lsmola has joined #openstack-meeting-306:27
*** Sukhdev has quit IRC06:33
*** amotoki_ has joined #openstack-meeting-306:41
*** yamamoto has joined #openstack-meeting-306:42
*** amotoki_ has quit IRC06:47
*** markvoelker has joined #openstack-meeting-306:49
*** markvoelker has quit IRC06:53
*** Ramanjaneya has joined #openstack-meeting-306:55
*** yuikotakada has joined #openstack-meeting-306:57
*** sahid has quit IRC07:00
*** marun has joined #openstack-meeting-307:00
*** sahid has joined #openstack-meeting-307:01
*** marun has quit IRC07:05
*** mwagner_afk has quit IRC07:06
*** sridhar_ram has joined #openstack-meeting-307:10
*** sridhar_ram1 has joined #openstack-meeting-307:15
*** sridhar_ram has quit IRC07:16
*** mwagner_afk has joined #openstack-meeting-307:18
*** armax has quit IRC07:26
*** sridhar_ram1 has quit IRC07:29
*** ajo has joined #openstack-meeting-307:39
*** amotoki_ has joined #openstack-meeting-307:43
*** safchain has joined #openstack-meeting-307:46
*** amotoki_ has quit IRC07:48
*** watanabe_isao has joined #openstack-meeting-307:50
*** ajo has quit IRC07:51
*** ajo has joined #openstack-meeting-307:51
*** ajo has quit IRC08:00
*** vkmc has quit IRC08:04
*** vkmc has joined #openstack-meeting-308:04
*** saju_m has joined #openstack-meeting-308:13
*** saju_m has quit IRC08:13
*** JeanBriceCombebi has joined #openstack-meeting-308:18
*** lsmola has quit IRC08:27
*** anusree has joined #openstack-meeting-308:27
*** woodster_ has quit IRC08:31
*** watanabe_isao has quit IRC08:33
*** lsmola has joined #openstack-meeting-308:34
*** markvoelker has joined #openstack-meeting-308:37
*** JeanBriceCombebi has quit IRC08:38
*** bradjones has quit IRC08:40
*** JeanBriceCombebi has joined #openstack-meeting-308:40
*** markvoelker has quit IRC08:42
*** bradjones has joined #openstack-meeting-308:42
*** bradjones has quit IRC08:42
*** bradjones has joined #openstack-meeting-308:42
*** amotoki_ has joined #openstack-meeting-308:44
*** vgridnev has joined #openstack-meeting-308:46
*** ajo has joined #openstack-meeting-308:47
*** amotoki_ has quit IRC08:48
*** JeanBriceCombebi has quit IRC08:49
*** JeanBriceCombebi has joined #openstack-meeting-308:49
*** devvesa has joined #openstack-meeting-308:50
*** vishwanathj has quit IRC08:51
*** yamahata has joined #openstack-meeting-309:07
*** shwetaap has joined #openstack-meeting-309:08
*** shwetaap has quit IRC09:13
*** dims has joined #openstack-meeting-309:27
*** dims has quit IRC09:31
*** fesp has joined #openstack-meeting-309:48
*** rushiagr is now known as rushiagr_away09:49
*** dims has joined #openstack-meeting-309:51
*** dims_ has joined #openstack-meeting-309:52
*** e0ne has joined #openstack-meeting-309:55
*** fesp has quit IRC09:55
*** dims has quit IRC09:56
*** e0ne is now known as e0ne_10:01
*** e0ne_ has quit IRC10:07
*** shwetaap has joined #openstack-meeting-310:09
*** jklare has quit IRC10:10
*** ajo has quit IRC10:13
*** shwetaap has quit IRC10:14
*** matrohon has joined #openstack-meeting-310:16
*** ajo has joined #openstack-meeting-310:16
*** ajo has quit IRC10:21
*** markvoelker has joined #openstack-meeting-310:23
*** sankarshan_ is now known as sankarshan_away10:23
*** wuhg has quit IRC10:24
*** yamamoto has quit IRC10:24
*** sankarshan_away is now known as sankarshan_10:24
*** markvoelker has quit IRC10:27
*** yamamoto has joined #openstack-meeting-310:28
*** cbader has quit IRC10:34
*** e0ne has joined #openstack-meeting-310:35
*** marun has joined #openstack-meeting-310:38
*** marun has quit IRC10:43
*** amotoki_ has joined #openstack-meeting-310:45
*** coolsvap is now known as coolsvap|afk10:45
*** amotoki_ has quit IRC10:50
*** yamamoto has quit IRC10:51
*** yamamoto has joined #openstack-meeting-310:51
*** JeanBriceCombebi has quit IRC10:52
*** stanzgy has quit IRC10:53
*** amotoki has quit IRC10:54
*** absubram has joined #openstack-meeting-310:59
*** jklare has joined #openstack-meeting-311:05
*** robcresswell has joined #openstack-meeting-311:06
*** yamamoto has quit IRC11:08
*** alexpilotti has joined #openstack-meeting-311:08
*** amotoki has joined #openstack-meeting-311:12
*** mwagner_afk has quit IRC11:12
*** stendulker has quit IRC11:14
*** yuikotakada is now known as yuikotak_dinner11:15
*** yamamoto has joined #openstack-meeting-311:21
*** Longgeek has joined #openstack-meeting-311:22
*** markvoelker has joined #openstack-meeting-311:24
*** amotoki has quit IRC11:25
*** Longgeek_ has joined #openstack-meeting-311:25
*** akrivoka has joined #openstack-meeting-311:28
*** markvoelker has quit IRC11:28
*** Longgeek has quit IRC11:28
*** yamamoto has quit IRC11:32
*** jcoufal has quit IRC11:44
*** tobe has quit IRC11:47
*** vgridnev has quit IRC11:49
*** vgridnev has joined #openstack-meeting-311:50
*** tsufiev has joined #openstack-meeting-311:51
*** baoli has joined #openstack-meeting-311:51
*** julim has joined #openstack-meeting-311:52
*** doug-fish has joined #openstack-meeting-311:53
*** markvoelker has joined #openstack-meeting-311:54
*** eandersson has joined #openstack-meeting-311:57
*** shwetaap has joined #openstack-meeting-311:57
david-lyle#startmeeting Horizon12:01
openstackMeeting started Wed Jun 10 12:01:15 2015 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.12:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:01
*** jcoufal has joined #openstack-meeting-312:01
*** openstack changes topic to " (Meeting topic: Horizon)"12:01
openstackThe meeting name has been set to 'horizon'12:01
david-lylewho's around?12:01
robcresswello/12:01
* doug-fish raises hand12:01
mrungeo/12:01
neillco/12:01
*** baoli_ has joined #openstack-meeting-312:01
tsufiev\o12:01
absubramo/12:02
*** shwetaap has quit IRC12:02
david-lyleok, let's get started12:02
akrivoka\o12:02
david-lyleFirst some follow up12:03
david-lyleI'm still working on pinning down a time and date for the midcycle12:03
david-lylewe had a bit of misdirection late last week that set back the process a bit12:03
*** baoli has quit IRC12:04
david-lylethat's cleared up and now we're still trying to coordinate with glance and searchlight to co-locate12:04
mrungedavid-lyle, is there an option to move it to September?12:04
david-lylehttps://docs.google.com/spreadsheets/d/1w0eI6SPCA2IrOyHiEYC2uDO3fbYGzahZRUQSva0UD3Y/edit#gid=012:04
david-lylemrunge: I suppose that's an option, but that feels a little late12:05
mrungeat least some folks will need a visa for US12:05
david-lyleunless we intend it as a cleanup item12:05
mrungeand July/August is main vacation time, that will hit one or the other12:05
robcresswellWe'll only need an ESTA, I thought, and the turnaround for those is very fast12:06
david-lylemrunge: honestly hadn't considered visas, TBH12:06
*** rushiagr_away is now known as rushiagr12:06
david-lyleif we do july, we're leaning toward the later date due to the delays in planning12:06
mrungerobcresswell, at least I heared about folks having an issue to get to Canada, which is more liberal with visa than US is12:06
mrungelater July is in parallel with Europython conference12:07
david-lylethe other option is we don't co-located with glance12:07
david-lylethat increases flexibility12:07
*** bethelwell has joined #openstack-meeting-312:08
robcresswellmrunge: I'm unsure, but I thought Germany was also able to get an esta under the visa waiver program,and that has a turnaround of.. hours, basically.12:08
david-lyleBTW, searchlight was voted into OpenStack yesterday \o/12:08
robcresswelloh awesome12:08
doug-fishcool12:08
neillcyay12:08
robcresswellcongrats to Trav then12:08
mrungerobcresswell, for Germany, it shouldn't be such an issue with Esta12:08
david-lyleand the overlap of people between glance and horizon was the reason for the co-location12:09
david-lylebut if searchlight midcycle is done online, it may not be an issue12:09
neillcsearchlight is the one I'm interested in :)12:09
bethelwello/ hope you dont mind me coming along to the meeting! New to contributing and code reviews but up for doing more for sure!12:09
robcresswellbethelwell: You are more than welcome :)12:10
david-lylewelcome bethelwell12:10
bethelwellthank you!!12:10
david-lyleok, summary midcycle still a WIP12:11
david-lylebut work is happening :)12:11
mrunge+2 great :D12:11
robcresswellAwesome. Thanks!12:11
absubramI like that Cambridge, MA is an option for location :)12:12
mrungeyes!12:12
david-lylenow looking at our top priority items for Liberty12:13
david-lyle#link https://etherpad.openstack.org/p/YVR-horizon-liberty-priorities12:14
david-lylethere is progress on all front on the technical debt section which is good12:14
david-lyleThai has a patch up for moving horizon translation to be babel based12:15
david-lyleI don't have the link handy, but more feedback on that would be great12:15
david-lylefor plugins12:15
david-lyleI'm working on that12:15
neillcbabel patch is https://review.openstack.org/#/c/188665/12:15
david-lyleI'm attempting to move sahara to /contrib and define a structure and testing strategy, it needs more work12:16
david-lylethanks neillc12:16
david-lyleI want to base the documentation off a working model12:16
neillcThere is a query from the trandlation team that could use an answer from someone more expert than me12:16
neillcdo we want openstack_dashboard and horizon i18n kept separate or can they be combined?12:17
*** ajo has joined #openstack-meeting-312:17
david-lylein theory they should stay separate, but I think we're drifting in an in separable horizon/openstack_dashboard with proposed reOrg changes12:18
robcresswellDo we gain anything from combining them? IMO we should just keep them apart, if we decide to seperate properly later on.12:18
neillctranslation team want them combined12:18
david-lyleso if we give up the idea of having any separability of the two sides, we could combine12:19
robcresswellInteresting. What was their reasoning?12:19
david-lylerobcresswell: we are different12:19
david-lyledifferent is hard12:19
neillc"Neill, there's no reason for the translators to translate separately. Merging it would be nice from a CI infra point of view. Let's bring this to Steve's attention who's currently working on these scripts for our move to Zanata."12:19
doug-fishwe're going to need at least to files anyway - one for js and one for python12:19
mrungedoug-fish, I think it should work with a single file12:20
mrungeat least it worked in the past12:20
david-lyledoug-fish: don't those get squashed currently12:20
mrungenot claiming, it will work with angular12:20
neillcI don't know enough to have a firm opinion, but I thought we would probably prefer to keep them separate12:20
doug-fishthat will make our js file much bigger than it needs to be12:20
robcresswellI'm inclined to say keep them apart, since at the moment there is a lot of work specifically targetted at splitting horizon and the dashboard JS12:21
*** mwagner_afk has joined #openstack-meeting-312:21
robcresswellIt seems counter productive to merge translations... but I am by no means an expert on this.12:21
mrungerobcresswell, for translation team, it seems to be counter productive to have 2 (or 4), when counting js, too12:22
neillcare there implications for third party customisations?12:22
bethelwelltrue but from what i can see is it not counter productive also to have fewer but bloated js files?12:22
robcresswellmrunge: This is true, but I'm unsure how much it alters their workload to combine12:22
mrungeI'd say: no. third party modules still should work12:23
*** JeanBriceCombebi has joined #openstack-meeting-312:23
*** janonymous_ has joined #openstack-meeting-312:23
david-lyleplease leave feedback on the review and we can continue the discussion there12:24
robcresswellWill do12:24
david-lylesession clean up is stalled I think12:25
david-lylewill reboot12:25
david-lylejscs enforcement is in progress as well (how is that a top priority)?12:26
david-lyleauto-collecting JS files has a patch up12:26
*** bradjones has quit IRC12:26
david-lylethere is also work on the webroot bug12:27
*** bradjones has joined #openstack-meeting-312:27
*** bradjones has quit IRC12:27
*** bradjones has joined #openstack-meeting-312:27
david-lyleso we are making progress12:27
david-lylelots to land though12:27
david-lyleI did make a change on the priority list12:27
david-lylethat I should discuss12:27
david-lyleI have moved the details views down in priority and wider coverage of angularized tables up12:28
david-lylewe're doing a tremendous amount of work to improve UX and scalability12:28
robcresswellSeems sensible12:28
david-lyleI would like us to realize those benefits in the most needed places first12:28
david-lyledetails views could be better, but much less overall improvement12:29
david-lyleplus too many different things in flight is just chaos12:29
david-lyleand I'm going nuts trying to track all of it12:29
robcresswelldavid-lyle: Anything we can do to help out?12:30
*** amotoki has joined #openstack-meeting-312:30
david-lylerobcresswell: I'm just trying to make sure we can land things12:31
bethelwellthat was what i was about to say. I am currently having a lot of downtime and some evenings free so if there are specific code reviews or FE things you need doing urgently feel free to ping me12:31
david-lyleif we split reviewers across too broad a spectrum we won't land much12:31
SergeyLukjanovdavid-lyle, re moving sahara to contrib/ how it'll help with reviews? dir-based core teams?12:32
bethelwelldavid-lyle: that makes sense. is there a priority order in place?12:32
*** marun has joined #openstack-meeting-312:32
robcresswellOh that reminds me. I have a small nag. Can people merging code please make sure to prioritise and target bugs? I think that makes it easier to see what is going on.12:32
robcresswellI've been going through anything commited and filling it in, but its not ideal to have just my opinion on its priority :/12:33
mrungerobcresswell, not everyone can target bugs and prioritize them12:33
robcresswellmrunge: I thought all cores could? And they will be the ones merging code?12:33
mrungerobcresswell++ thanks for doing that!12:33
david-lyleSergeyLukjanov: the idea is to allow for more impactful review from the sahara team itself12:33
mrungerobcresswell, yes, that's correct12:33
david-lyleif we isolate the sahara related changes, we can take service team voting to be one of the +2s12:34
david-lyleand then just have one horizon core +2 and +A12:34
david-lylethe idea is actually to speed up development12:34
SergeyLukjanovdavid-lyle, it'll be really great! because mostly all of our patches are now need to be on review for a few month to be merged :(12:34
david-lyleknowing that those reviews get starved12:34
david-lyleyes12:35
absubramdavid-lyle: would this be the goal for all the ‘plugins’?12:35
david-lyleSahara, Trove and Heat would all fall in the same model12:35
david-lylebut I picked Sahara to start because your team is very active with patches12:35
SergeyLukjanovdavid-lyle, so, you prefer the way to keep em in contrib/ ?12:35
david-lyleand I want that progress in tree12:35
SergeyLukjanovdavid-lyle, I mean comparing to external plugins for example12:36
david-lyleit's a way to isolate them for now12:36
david-lyleSergeyLukjanov: eventually we might want to move them out of tree, but that was more than I wanted to take on for Liberty12:36
SergeyLukjanovdavid-lyle, yeah, I think it could helps both of our teams a lot - to make sahara changes landing faster and to decrease number of reviews for horizon team12:36
david-lylethere are integration tests and other things that need to be worked out12:37
*** VW has joined #openstack-meeting-312:37
SergeyLukjanovdavid-lyle, yeah, integration tests are painful12:37
david-lylein tree for now makes the testing strategy much simpler12:37
SergeyLukjanovdavid-lyle, got the idea about contrib/ and looking forward for it, thank you!12:37
david-lyleSergeyLukjanov: thanks12:37
david-lyleabsubram: for things not in tree already, they are staying out of tree12:38
absubramdavid-lyle: can we granularize a little on what we are trying to accompolish via the plugins.. Rob and I were talking about this yesterday.. What would be the items that constitue a plugin firstly? You just mentioned Sahara, Trove and Heat.. would all of the networking components be their own plugin as well?12:38
david-lyledesignate and manila are a couple of examples12:38
david-lylemagnum will be another12:38
*** VW has quit IRC12:39
david-lyleabsubram: there's no reason we couldn't organize them as plugins, but I'm not looking to shift the networking part yet12:40
absubramok..12:40
*** VW has joined #openstack-meeting-312:40
*** qwebirc99779 has joined #openstack-meeting-312:40
robcresswellOne thing I wanted to clear up is whether the plugin work will include extending the levels at which plugins can insert code, so workflows etc12:40
absubramso no seperate plugins for launch instance or create networks :p12:40
david-lylethings like launch instance and topology views become terribly complex if you have separated code for networking and compyte12:40
tsufievdavid-lyle, what about murano-dashboard? From the view of ensuring things don't break with new horizon release it seems reasonable...12:40
absubramdavid-lyle: makes sense..12:41
*** JeanBriceCombebi has quit IRC12:41
absubramrobcreswell: +1.. it’s what I’d like to know too!12:41
tsufievI mean, placing it into contrib/ to run the tests against it12:41
david-lyletsufiev: well part of what I need to work to define is a testing strategy for plugins out of tree12:41
david-lyleeven if they are non-voting jobs on horizon tests12:42
david-lylerobcresswell: yes it should include that, but that's a bit off in the distance for now12:42
tsufievdavid-lyle, sure! I'll forward this concern to Murano team, perhaps could use their help12:43
david-lylemy first priority is remove horizon as the bottleneck for all ui code12:43
*** JeanBriceCombebi has joined #openstack-meeting-312:43
david-lylenext broaden what a plugin can do12:43
amotokidavid-lyle: I like your approach. We are taking the similar model as tempest tries to do.12:43
amotokias you may know,  tempest will have tests only for projects of core projects in "defcore" + neutron in Liberty.12:44
david-lyleamotoki: yes and devstack is making a similar move12:44
robcresswellYeah, biggest blocker to me ripping out all the cisco bits is that we can't make it pluggable yet. The router dashboard will be removed soon.12:44
robcresswellBut we have no mechanism for getting in the workflows without editing code, which will leave me in rebase-hell on an outside repo.12:44
amotokirobcresswell: I think we need to explore how we can define hooks or similar framework to support verndor specific logics.12:45
david-lylerobcresswell: if you would like to take a pass at that functionality of plugins, I don't think it would collide with what I'm doing12:45
amotokiwe can explore it during Liberty cycle :-)12:45
robcresswelldavid-lyle, amotoki: I'm more than happy to have a go at that. Will do once the router bit is in its own repo.12:45
*** salv-orlando has quit IRC12:45
absubramamotoki: robcresswell: +112:45
david-lylerobcresswell: thanks12:45
david-lyleI think we just covered the only agenda item :P12:46
david-lyleabsubram: was there more ?12:46
robcresswellIf anyone has suggestions, or had written similar functionality before, advice is welcome :)12:47
absubramdavid-lyle: haha yeah the hooks to the workflows was what I had wanted to bring up12:47
*** e0ne is now known as e0ne_12:47
absubramRegarding the vendor split - based on some of the feedback from the summit, we can do a neutron extension detection (very similar to what we already do for the firewall and vpn panels).. and if the extension is detected, which means the neutron vendor plugin is being used, the dashboard can be configured to have the specific vendor support…12:47
*** woodster_ has joined #openstack-meeting-312:48
absubramThe complication is in the workflow code that is being used in the existing launch instance and create networks and create firewalls.. the vendor stuff needs that code.. so the idea is to have a separate workflow that could perhaps be inherited by the common workflow when the extension is supported?12:48
absubramThen the vendor code could theoretically reside in it’s own separate bubble.. outside of the common workflow file.. there might still be some lines we need included to detect settings/configs etc for the vendors.. would that be ok?12:48
robcresswellabsubram: Is this the stevedore idea? Discovering plugins that are installed...12:48
absubramrob: not exactly.. stevedore in neutron directs the plugin packages12:49
robcresswellAh, sorry12:49
absubramI don’t think we should have a pip install <vendor-package>12:49
absubramin horizon for the small amount of vendor code :)12:49
absubramit’s like the firewalls panel12:49
tsufievrobcresswell, to me that is similar to the hooks idea12:49
amotokiabsubram: I think the discussion can be split into several parts: how to detect available features, how to customize horizon UI (insert something or change something).12:50
*** e0ne_ is now known as e0ne12:50
*** vgridnev has quit IRC12:50
absubramamotoki: sounds good12:50
amotokifor the first part, you can use vendor python package too, but the second point is more important.12:50
absubramI’ll bring up the discussions in the mailer?12:50
amotokii have no idea on a specific plan though.12:51
robcresswellamotoki: Agreed, they are seperate points.12:51
absubramamotoki: big +1.. that’s the part I don’t have any proper ideas on currently12:51
amotokiso that's the reason I said we can explore it in Liberty cycle :-)12:51
absubramlol yes12:51
robcresswellSo I have a few items first, like remove the existing dashboard, and sort out the angular docs. Then I will start looking into pluggable workflows, or something along those lines.12:51
*** jcoufal has quit IRC12:51
absubramthanks Rob!12:52
david-lylerobcresswell: sure, take all the easy stuff ;)12:52
absubramlol!12:52
*** jcoufal has joined #openstack-meeting-312:52
amotokirobcresswell: +112:52
david-lylethanks Rob!12:52
*** jcoufal is now known as Guest6217812:52
robcresswellhaha12:52
robcresswell:)12:53
david-lyleeven though I think we've been there for a while12:53
david-lyle#topic Open Discussion12:53
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"12:53
amotokidoes anyone have an interest to serve as oslo liaison in Liberty?12:53
*** bknudson has joined #openstack-meeting-312:53
amotokiI am afraid I cannot spend enough time for the liaison in Liberty cycle and there is a meeting time conflict between oslo and neutron-ironic integration.12:53
*** vgridnev has joined #openstack-meeting-312:53
amotokiI try to do my best but it is better if someone who has more time takes it.12:54
david-lyleamotoki: feel free to take you name off the wiki (if you haven't) and I'll work on finding someone12:54
robcresswellMay be worth asking Quality, I hear he loves liaison roles12:55
david-lylethanks for handling it in Kilo12:55
amotokidavid-lyle: thanks. will do.12:55
absubramwhat does it involve akihiro? afraid not suffcient knowledge of oslo on my part :(12:55
mrungeamotoki, thank you for your work on that liaison.12:55
*** Guest62178 has quit IRC12:55
amotokiabsubram: the main missions are to sync oslo libraries with our code base and to join oslo reviews.12:56
*** praveens has joined #openstack-meeting-312:56
amotokiand to raise alarms if we have a problem.12:56
david-lyleabsubram: we only use a small percentage of the oslo libraries in Horizon, so the exposure is less12:56
david-lylein theory12:56
david-lylebut still work to stay on top of12:57
*** sigmavirus24_awa is now known as sigmavirus2412:58
absubramhaha ok.. thanks.. will sync up with you outside of the meeting, if I think it’s doable..12:58
david-lylesure12:58
amotokiwe have many cross project liaisons. if you are interested, see https://wiki.openstack.org/wiki/CrossProjectLiaisons12:58
*** shwetaap has joined #openstack-meeting-312:58
*** yamamoto has joined #openstack-meeting-312:59
*** vgridnev has quit IRC12:59
*** JeanBriceCombebi has quit IRC12:59
*** JeanBriceCombebi has joined #openstack-meeting-312:59
david-lyleseems QA is available as well :)13:00
david-lyletimes up13:01
david-lylehave a great week everyone!13:01
absubramthanks all!13:01
david-lyle#endmeeting13:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:01
openstackMeeting ended Wed Jun 10 13:01:21 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-06-10-12.01.html13:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-06-10-12.01.txt13:01
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-06-10-12.01.log.html13:01
*** tsufiev has left #openstack-meeting-313:01
*** robcresswell has left #openstack-meeting-313:01
neillcbye o/13:01
qwebirc99779o/13:02
*** shwetaap has quit IRC13:03
qwebirc99779o/13:03
*** tariqkhp has joined #openstack-meeting-313:03
*** cbader has joined #openstack-meeting-313:03
*** vgridnev has joined #openstack-meeting-313:03
*** qwebirc99779 has left #openstack-meeting-313:06
*** janonymous_ has left #openstack-meeting-313:07
*** lblanchard has joined #openstack-meeting-313:11
*** praveens has quit IRC13:15
*** peristeri has joined #openstack-meeting-313:17
*** jcoufal_ has joined #openstack-meeting-313:19
*** rushiagr is now known as rushiagr_away13:20
*** singlethink has joined #openstack-meeting-313:23
*** jgrimm is now known as zz_jgrimm13:28
*** doug-fish has quit IRC13:29
*** VW_ has joined #openstack-meeting-313:30
*** VW has quit IRC13:31
*** jcoufal_ has quit IRC13:32
*** puranamr has joined #openstack-meeting-313:32
*** jcoufal_ has joined #openstack-meeting-313:33
*** jpomero has joined #openstack-meeting-313:34
*** tariqkhp has quit IRC13:35
*** pkarikh has quit IRC13:36
*** pkarikh has joined #openstack-meeting-313:36
*** vishwanathj has joined #openstack-meeting-313:37
*** vishwana_ has joined #openstack-meeting-313:39
*** vishwanathj has quit IRC13:42
*** puranamr has quit IRC13:43
*** puranamr has joined #openstack-meeting-313:44
*** Ramanjaneya has quit IRC13:46
mohankumarhi13:47
*** jcoufal_ has quit IRC13:49
*** eandersson has left #openstack-meeting-313:50
*** e0ne is now known as e0ne_13:51
*** Ramanjaneya has joined #openstack-meeting-313:52
*** Ramanjaneya has quit IRC13:52
*** matrohon has quit IRC13:53
*** rhagarty has quit IRC13:53
*** rhagarty_ has quit IRC13:54
*** rhagarty has joined #openstack-meeting-313:54
*** rhagarty__ has joined #openstack-meeting-313:54
*** cbouch has joined #openstack-meeting-313:54
*** devvesa has quit IRC13:55
*** igordcard_ has quit IRC13:56
*** igordcard_ has joined #openstack-meeting-313:57
*** puranamr has quit IRC13:57
*** ihrachyshka has joined #openstack-meeting-313:58
*** VW_ has quit IRC13:58
*** shwetaap has joined #openstack-meeting-313:59
ajohi :)13:59
ajoQoS meeting? :)13:59
*** e0ne_ is now known as e0ne13:59
*** Ramanjaneya has joined #openstack-meeting-314:00
*** irenab has joined #openstack-meeting-314:00
sc68calo/14:00
*** sfinucan has joined #openstack-meeting-314:00
*** moshele has joined #openstack-meeting-314:00
ajosc68cal, irenab, ihrachyshka , vhoward , moshele , hi! ;)14:00
moshelehi14:01
ihrachyshka\o14:01
irenabhi14:01
sfinucanhey14:01
RamanjaneyaHi ajo, I'm ramanajneya from vikram team..14:01
ajohi sfinucan  :)14:01
ajohi Ramanjaneya welcome :)14:01
ajo#startmeeting neutron_qos14:01
openstackMeeting started Wed Jun 10 14:01:37 2015 UTC and is due to finish in 60 minutes.  The chair is ajo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:01
openstackThe meeting name has been set to 'neutron_qos'14:01
ajo#topic Where are we?14:02
*** openstack changes topic to "Where are we? (Meeting topic: neutron_qos)"14:02
ajo#link https://etherpad.openstack.org/p/neutron-qos-jun-10-201514:02
mohankumarHi  Ajo .. Mohan here from vikram team14:02
ajoan interactive agenda ^14:02
ajohi mohankumar , welcome too14:02
ajoSo, past monday we got the feature branch setup14:02
ajoit's feature/qos14:02
ajohttps://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:feature/qos,n,z14:03
ajo#link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:feature/qos,n,z14:03
RamanjaneyaWe are doing neutron client changes...and posted qos policy cli cmds14:03
Ramanjaneyahttps://review.openstack.org/#/c/189655/14:03
Ramanjaneyaand we are working other neutron client commands too.14:03
ajoah, thanks Ramanjaneya , please note it on the etherpad I will make a comment when we get there :)14:03
ajothat's very nice! ;)14:03
*** shwetaap has quit IRC14:04
ajoany question about the feature branch thing?14:04
Ramanjaneyaok..sure14:04
sc68calCan we organize all our patches under one topioc?14:04
ajothere are some notes on the etherpad about what's the plan14:04
sc68cal*topic?14:04
ajosc68cal, do you mean, a general topic to aggregate client + api + everything?14:04
irenab=114:04
sc68calanteaya showed me something neat the other day, you can use git review -t <topic name> so you can keep everything organized14:05
ihrachyshkasc68cal, why not filtering using branch now that we have it?14:05
*** VW has joined #openstack-meeting-314:05
*** akrivoka has left #openstack-meeting-314:05
sc68calfor example: https://review.openstack.org/#/q/topic:neutron-linuxbridge,n,z14:05
irenablets have both14:05
ihrachyshkaah right, it's not just neutron14:06
irenabwe may switch branch to master at some point14:06
ajosounds good to me, we can try it14:06
ihrachyshka+ for both then14:06
ajoif it gets messy at some point, we can think of changing strategy, but I guess that won't happen :)14:06
ajo+114:06
ihrachyshkatopic:neutron-qos?14:06
sc68cal^ works for me14:06
ajoihrachyshka +1 wfm too14:06
ajook Ramanjaneya change the topic of your reviews when you can, I'll change mine, moshele , you too please :)14:07
mosheleajo: sure14:07
ajook, now that we are on a similar topic, I'm going to jump over it first14:08
ajo#topic CI cross/projects/feature branch14:08
*** openstack changes topic to "CI cross/projects/feature branch (Meeting topic: neutron_qos)"14:08
Ramanjaneyaok14:08
ajoI'm unsure how're we going to put together the changes to neutron-client + CI tests from the feature branch14:08
ajoshall we create separate CI jobs?14:08
ajowe need to enable: service_plugins=neutron.services.l3_router.l3_router_plugin.L3RouterPlugin,neutron_lbaas.services.loadbalancer.plugin.LoadBalancerPlugin,neutron.services.qos.qos_plugin.QoSPlugin14:09
ajofrom debstack14:09
ajodevstack O:)14:09
ajothe last bit: neutron.services.qos.qos_plugin.QoSPlugin14:09
ajootherwise neither our extension or plugin is loaded, and we can't test14:09
ajoand also, we have the same issue with neutron client14:09
ajowe need to investigate if your devstack initialization can be made (somehow) conditional on the feature branch14:10
ajoto set that14:10
sc68calwe can create experimental jobs14:11
ajoany comments or ideas about this? or shall I move one?14:11
sc68calcan take the similar approach to what we're doing now with the linux bridge testing initiative14:11
ajosc68cal, ahaa14:11
ajosc68cal, experimental are run on every patch?14:11
ajothen we could just skip it if branch is not "feature/qos"14:11
sc68calajo: no, you check with a special comment14:11
ajoand set the right neutron client when feature/qos is on14:11
ajoahh sc68cal , ack14:12
ajothat could work for me14:12
ajosc68cal, any link/review about how to setup an experimental CI job?14:12
ajoany volunteer? :)14:12
sc68calI can take it on - here's how I did it for LB - https://review.openstack.org/18483014:12
sc68calso it'll be similar14:13
ajo#link https://review.openstack.org/18483014:13
ajosc68cal, thank you very much14:13
*** jckasper has quit IRC14:13
ajo#action sc68cal to setup an experimental job for testing QoS plugin + ext14:13
ajo#topic poc mixin-less core resource extension in service plugin14:14
*** openstack changes topic to "poc mixin-less core resource extension in service plugin (Meeting topic: neutron_qos)"14:14
ajomore details on the etherpad14:14
ajobut basically14:14
ajo#link  https://review.openstack.org/#/c/189628/14:14
*** bethelwell has left #openstack-meeting-314:15
ajoI introduced the AFTER_READ callback notification in neutron/db/db_base_plugin_v2.py14:15
ajo14:15
dhruvAjo: can you post the etherpad link14:15
ajoand we register for it on the service plugin, being able to extend core resources (PORT in this case)14:15
ajosure dhruv : https://etherpad.openstack.org/p/neutron-qos-jun-10-201514:15
dhruvajo: thanks14:16
*** VW has quit IRC14:16
ajoI need to talk to armax to get some review on the way I did dit14:16
ajoI hope it looks reasonable14:16
*** amotoki has quit IRC14:17
ajoas a strategy, for example, you don't have control over how callbacks are called, so future dependent extensions using the same mechanism may need some way to handle that14:17
*** amotoki has joined #openstack-meeting-314:17
ajomoshele, do you want to jump on what you've been doing?14:18
*** amotoki has quit IRC14:18
irenabI wonder if the patch should be spli into few patches, to make it easier to review?14:18
*** puranamr has joined #openstack-meeting-314:18
irenab^ajo14:18
mosheleajo: I started on the agent extension driver14:18
irenabI think callbacks modification is self standing change14:19
ajoirenab, probably it could be split, yes... extension in one, service plugin in other,14:19
*** amotoki has joined #openstack-meeting-314:19
mosheleI talked to irenab an I need to some change current path14:19
ajoirenab, the callback notify in other14:19
irenabI think not too granular, but generic/versus qos specific14:19
ajoirenab, I can split, yes14:19
mosheleI mean patch14:20
ajomoshele, thanks :)14:20
*** ddepaoli_ has joined #openstack-meeting-314:20
*** amotoki has quit IRC14:20
moshelebasically I plan to add  L2Agent interface class14:20
ajoirenab, I can split now that the approach seems to work :)14:20
*** amotoki has joined #openstack-meeting-314:20
irenabajo: great14:20
irenabfollowing our discussion with moshele, some questions there regarding RPC between Server and agent14:22
ajoyes14:22
ajoI have some debt in that regard, I need to put a devref or devref+POC on a generic RPC mechanism14:22
irenabajo: do you have some details regarding generic RPC approach you mentioned last meeting?14:22
ajosadly not :( I invested all my time in the other patch14:22
*** puranamr has quit IRC14:23
ajomoshele, I can have something by tomorrow for review14:23
ajoto see if it does make sense14:23
moshelethat will be great14:23
ajo#action ajo write the generic RPC mechanism doc for review14:24
irenabas for the workflow between agent and server, I think we should discuss how its bound to the current L2 agent RPC calls if at all14:24
ajoirenab, those may be independent calls...14:24
ajoirenab, do you mean, current L2, or current on moshele's patch? (I didn't have time to review)14:25
irenabajo: current, we may still reuse the update_port and get_device_details14:25
*** Yi_ has joined #openstack-meeting-314:25
ajoirenab, I guess you're right14:25
irenabto add qos_policy_id, and qos_agent will have to query for details14:26
ajoI'd try to avoid cluttering get_device_info with more info14:26
irenabwe should try to keep number of RPC call to minimum14:26
ajoand probably include an alternate call to retrieve specific info + subscribe14:27
ajoirenab, yes, I agree on that, I guess it's my fault for not presenting my plan14:27
ajomy plan includes, later on in time, migrating security groups (the user of get_device_info) later to the new mechanism14:27
irenabajo: right, but probably need to go though generic loop to apply changes14:27
irenabajo: completely with you on this14:28
ajothe idea is that subscription via fanouts will distribute the info to the right extensions as the information changes...14:28
irenabwe need to define this part to make agent side refactoring14:28
ajoextensions : modular L2 agent extensions14:28
*** nkrinner has quit IRC14:29
ajoirenab yes14:29
ajook, I can push on that, while we get progress in the DB models, the neutron client, etc..14:29
irenabthere are two different types of updates, on on port level (update policy mapping) and other update of policy itself14:30
ajoirenab, correct14:30
irenabI guess the first one can be treated via update_port workflow14:30
ajocorrect14:30
ajoupdate_port shall provide the qos_profile_id14:30
ajoand then, the agent can subscribe to such profile_id14:30
irenabthe second is proposed RPC pub/sub14:30
ajocorrect14:30
irenabajo:+114:31
ajothen unsub when no port is ussing such qos_profile_id anymore in the host14:31
ajousing14:31
irenabget_device_details now is used for first time configuration, it maybe useful to propogate qos_policy there as well14:32
irenabthen agent will subscribe for updates14:32
ajowe need to explore that, yes14:32
ajoIMO I believe it's going to be more modulare if we can do it via the same pub/sub mechanism,14:32
ajosend the info on subscription14:33
ajothen we don't depend on two different RPC callbacks14:33
ajosorry calls14:33
ajowhen there are changes to make, or new pub/sub consumer extensions14:33
irenabthis may work, but need to synchronize the configuration on agent side14:34
irenabboth l2 connectivity and qos policy14:34
irenabto report device as UP14:34
ajoirenab, correct, as it happens now in the get_device_info, right? :)14:34
irenabyes14:34
mosheleyes14:34
ajowe'd just be doing one call per different resource type14:34
ajomay be that can be coalesced to one14:35
ajo(deferred subscription or something...)14:35
ajoall extensions come in at port creation... and subscribe what they need.... they finish, we do the whole subscription/info retrieval... we send the info back to all the extensions14:35
irenabI gues we agree on requiremetns, so lets just put down the RPC mech details and agent workflow14:36
*** ddepaoli_ has quit IRC14:36
ajoirenab, moshele , tomorrow I'll put my time on the rpc thing devref, and probably we can discuss on the review14:36
irenabajo: great14:37
ajook, shall we move on to the list of things we need progress on?14:37
*** zz_natorious is now known as natorious14:37
*** julim has quit IRC14:38
ajo#topic TO-DO14:38
*** openstack changes topic to "TO-DO (Meeting topic: neutron_qos)"14:38
ajoI'm afraid I lost almost everybody :D14:38
ajolol :)14:38
*** devvesa has joined #openstack-meeting-314:39
ajook, we need to advance on the ovs/sr-iov low level details, may be just as devref + code?14:39
ajomoshele ^ how does that sound?14:39
*** sbalukoff has quit IRC14:39
irenabajo: I am a bit oveloaded this week, but hope to get some work starting next week14:39
ajoirenab thanks :)14:40
mosheleI will try14:40
ajowe also have the neutron client: Ramanjaneya and mohankumar , thanks :)14:40
ihrachyshkaI started looking into supported qos rule type detection, not much done yet, but hopefully will have smth on Mon. not a prio, I know ;)14:40
ajokeep up the work on this, and ping me if you need any help14:40
mohankumar:)14:41
ajoihrachyshka: that will be very important at some point, thanks for working on this14:41
ajoWe need to progress on the DB models14:41
ajoVikram signed up for it, but afaik he's now on a 2-week PTO if I didn't get him wrong14:42
ajosomebody has time / can look into it?14:42
ajoI was thinking of using https://github.com/openstack/oslo.versionedobjects14:42
ajoeven if there is not too much doc on it14:42
ajowe could benefit from out of the box rpc serialization/deserialization that works across different versions of the models14:43
ihrachyshkaand you would work with objects, not dicts.14:43
ajoyey!14:43
ajothat's another nice advantage14:44
ihrachyshkato make it clear: do you anticipate it db side?14:44
ajoihrachyshka, what do you mean?14:44
ihrachyshkaI mean, how/when will you deserialize into sqla dict?14:45
ihrachyshkameh... better 'convert'14:45
ajoihrachyshka for the rpc pub/sub and the API calls I guess?, I still need to look into it14:46
ajoihrachyshka I just now the "wows" of versioned objects, but didn't dig into the details yet14:46
ajonow->know14:46
ihrachyshkaack, let's postpone14:47
ajook, if no volunteers, I will start looking into it if Vikram doesn't arrive first14:47
Ramanjaneyaajo: me and mohan work on behalf of vikram for DB model till he comes14:47
*** ajmiller has joined #openstack-meeting-314:47
ajoRamanjaneya, thanks, probably the best is to start by the db migrations, then we can look into the DB models with oslo.versionedobjects, let me find some references about it (I'll get to you with the link)14:48
*** fallenpegasus has joined #openstack-meeting-314:49
Ramanjaneyaok. thank you ajo14:49
ihrachyshkaajo, you still need to define models, so there is no change in that regard afaik14:49
ajoihrachyshka, they remain the same? I didn't know14:49
ajook, that's good, I guess14:50
ihrachyshkaI thought so! you define a middle layer that mostly reflects what is in schemas, but still14:50
ihrachyshkathat said, I may talk nonsense now, I will recheck better14:50
*** VW has joined #openstack-meeting-314:50
ajoihrachyshka, ack, we will recheck , np :)14:50
ajook14:50
ajoif somebody else has time, I may need to look into:  https://review.openstack.org/#/c/88599/14/specs/liberty/qos-api-extension.rst  L28314:51
ajoand replace that with something that really resembles our proposed API structure on the spec14:51
ajothis sets14:51
ajo  /v2.0/qos/qos-profiles14:51
ajoand /v2.0/qos/qos-bandwidthlimiting-rules14:52
ajoro something like that14:52
ajowhile we want: /v2.0/qos/rules/bandwidthlimiting14:52
ajo...14:52
ajoetc14:52
ajoI guess it's just not using the helper to create the resources and controller and do it yourself (probably talking nonsense here...)14:52
ajolast two days I've been wearing my "reverse-engineer" tshirt for a reason ;D, lot's of debugging and getting to know how the API is built in neutron14:53
ajoI shall change it now, but ... lot's of reverse engineering ahead ;D14:53
ajoif anybody has time to look at it while I wrap my head around RPC and VO's ^14:54
ajoit'd be great14:54
ajook, anything to add?14:55
ajoor shall I endmeeting/sleep ? :)14:55
ihrachyshkaprobably #endmeeting14:56
ajo#sleep14:56
ajohmm :D14:56
ajo#endmeeting14:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:56
openstackMeeting ended Wed Jun 10 14:56:44 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-06-10-14.01.html14:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-06-10-14.01.txt14:56
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-06-10-14.01.log.html14:56
*** belmoreira has quit IRC14:57
ajook guys/gals, nice to have you around14:57
*** devvesa has quit IRC14:59
*** shwetaap has joined #openstack-meeting-314:59
*** nfedotov has joined #openstack-meeting-314:59
*** nelsnelson has quit IRC15:01
*** jckasper has joined #openstack-meeting-315:03
*** dims_ has quit IRC15:03
*** sfinucan has quit IRC15:04
*** shwetaap has quit IRC15:05
*** dims has joined #openstack-meeting-315:08
*** dims has quit IRC15:08
*** dims has joined #openstack-meeting-315:08
*** natorious is now known as zz_natorious15:11
*** devvesa has joined #openstack-meeting-315:12
*** julim has joined #openstack-meeting-315:12
*** pballand has joined #openstack-meeting-315:14
*** iben has joined #openstack-meeting-315:15
*** ajo has quit IRC15:16
*** mikedillion has joined #openstack-meeting-315:16
*** mikedillion has quit IRC15:18
*** bpokorny has joined #openstack-meeting-315:20
*** vgridnev has quit IRC15:22
*** carl_baldwin has joined #openstack-meeting-315:22
*** MarkAtwood has joined #openstack-meeting-315:23
*** yamahata has quit IRC15:27
*** yamahata has joined #openstack-meeting-315:28
mesteryNeutron drivers meeting starting soon-ish15:30
* dougwig lines up his paint brushes and straight razors.15:30
mestery#startmeeting neutron-drivers15:30
openstackMeeting started Wed Jun 10 15:30:42 2015 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.15:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:30
*** openstack changes topic to " (Meeting topic: neutron-drivers)"15:30
openstackThe meeting name has been set to 'neutron_drivers'15:30
mestery#link https://wiki.openstack.org/wiki/Meetings/NeutronDrivers Agenda15:30
mestery#topic Action Item Review15:31
*** openstack changes topic to "Action Item Review (Meeting topic: neutron-drivers)"15:31
mesteryI had an action item to sort out Lt. vs. drivers. I'm still working on it :)15:31
mesteryI'll take that for next week too15:31
mestery#action mestery to sort out neutron-drivers vs. Lts. and the path forward15:31
mesteryHenryG: You had an item to bring up bug 1460720 in an L3 meeting and discuss with carl_baldwin, did that happen by chance?15:31
openstackbug 1460720 in neutron "Add API to set ipv6 gateway" [Undecided,New] https://launchpad.net/bugs/1460720 - Assigned to Abishek Subramanian (absubram)15:31
*** lazy_prince has quit IRC15:33
carl_baldwinmestery: It didn’t happen.15:33
mesterycarl_baldwin: :)15:33
mesterycarl_baldwin: OK, lets hope it does this week then.15:33
*** iben has quit IRC15:33
carl_baldwinI’ll keep it on the agenda.15:33
*** sdake has joined #openstack-meeting-315:33
mestery#action HenryG to make sure Bug 1460720 is discussed during an upcoming L3 meeting with carl_baldwin and team15:34
openstackbug 1460720 in neutron "Add API to set ipv6 gateway" [Undecided,New] https://launchpad.net/bugs/1460720 - Assigned to Abishek Subramanian (absubram)15:34
HenryGYeah, sorry abotu that. Will try again.15:34
mesteryHenryG: No worries :)15:34
mestery#topic Specific Spec Review15:34
*** openstack changes topic to "Specific Spec Review (Meeting topic: neutron-drivers)"15:34
mesteryLets see about this.15:34
mesteryI spent an hour going through specs this morning.15:34
mesteryYikes.15:34
mesteryThere is a LOT there.15:34
mesteryI only made it through maybe 15-20 specs.15:34
mesteryLets start with some specs from carl_baldwin :)15:34
mestery#link https://review.openstack.org/#/c/172244/ Routing Networks15:35
mesteryThis one is important because it satisfies the network segment RFE as well15:35
mesteryAnd operators really want that solved15:35
mesterycarl_baldwin: Thansk for the re-spin on this one!15:35
carl_baldwinmestery: I’m not sure it gets the whole network segment rfe but it gets much closer.15:35
carl_baldwinI hesitate to promise to deliver both15:36
*** iben has joined #openstack-meeting-315:36
mesterycarl_baldwin: If it moves us in that direction it's a win-win I think15:36
carl_baldwinBut, they have the ability to map to network segments which both can use.15:36
*** ihrachyshka has quit IRC15:36
mesteryI'd like to highlight that one for other drivers (amotoki dougwig marun) to review this week.15:36
mesterycarl_baldwin: ++15:36
amotokimestery: sure15:37
mesteryContinuing on our "carl_baldwin spec review path" :)15:37
mestery#link https://review.openstack.org/#/c/16961 Address Scopes15:37
mesterykevinbenton had some comments on this one carl_baldwin15:37
dougwigi think address scopes is ready, minus the name being non-intuitive.15:37
mesterydougwig: ++15:37
carl_baldwinmestery: Still going through those comments.  I was distracted by something else yesterday.15:37
mesterycarl_baldwin: Not a problem, I think once you address kevinbenton's comments dougwig and I can merge it and you can get rolling15:38
carl_baldwindougwig: Any better suggestions yet?15:38
*** davidmichaelkarr has joined #openstack-meeting-315:38
dougwigno, i keep thinking of the royal Network (used) or NetworkGroup (not any more intuitive.)15:38
marunlink looks wrong15:38
*** singlethink has quit IRC15:39
mestery#undo15:39
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x9a23150>15:39
mestery#link https://review.openstack.org/180267 Address Scopes15:39
mesterymarun: there it is15:39
marundanke15:39
mestery:)15:39
mesterymarun: I am here to serve ;)15:39
*** praveens has joined #openstack-meeting-315:40
mesteryNext up on the highlight list (and not a carl_baldwin spec):15:40
mestery#link https://review.openstack.org/#/c/94612/ VLAN Aware VMs15:41
*** devvesa has quit IRC15:41
mesteryI see russellb provided some recent comments on this one15:41
* carl_baldwin could’ve written that one.15:41
mesteryrofl15:41
*** sridhar_ram has joined #openstack-meeting-315:41
mesteryDoes anyone have objections to the main tenant of htis spec: the idea of subports15:42
dougwigdid this spec get updated with the sort of consensus from the summit?15:43
amotokiI have a bit different view on this. we can use the similar model for vlan aware VMs as L2GW if l2gw takes a logical port as a member.15:43
amotokibut it is just my thought at the moment.15:43
amotokiam looking through the spec now.15:43
mesteryamotoki: Interesting thought15:44
mesterydougwig: That's also unclear to me15:44
dougwigi'll take a look.15:44
dougwigtoo15:44
*** Yi_ has quit IRC15:44
mesterythanks dougwig15:45
mestery#link https://review.openstack.org/#/c/169612 Availability Zones15:45
mesteryThis one needs a little work yet, but seems like something worth pursuring15:46
*** Sukhdev has joined #openstack-meeting-315:46
mesteryThe current implementation patch is here:15:46
mestery#link https://review.openstack.org/#/c/183369 Availability Zones Implementation15:47
mesteryIt's not that huge15:47
mesteryAnd finally15:47
mestery#link https://review.openstack.org/#/c/184857/ Get Me a Network15:47
amotokithere are many/several use cases for AZ. The proposed spec has a limited scope, but we tend to see more by "AZ".15:47
mesteryamotoki: Agreed on both fronts15:48
dougwigis get me a network ready for review, or does it still need someone to own it?15:48
*** armax has joined #openstack-meeting-315:49
mesterydougwig: It still needs an owner, from the meeting Monday I thought someone had volunteered15:49
mesteryLet me look at the log15:49
mesterydougwig: armax had volunteered in the meeting I see15:50
amotokiin the spec review, mark, zzelle and vikram volunteered for contributing.15:51
mesteryI'll keep on that and ensure we do find an owner.15:51
mestery#action mestery to find owner for "Get Me a Network" spec15:51
mesteryamotoki: Yes! We need an explicit owner however :)15:51
amotokimestery: exactly :)15:51
*** sridhar_ram has quit IRC15:51
mesteryOK, anyone want to bringup another spec?15:51
* mestery waits for 60 seconds15:51
dougwigone.15:52
*** sridhar_ram has joined #openstack-meeting-315:52
*** moshele has left #openstack-meeting-315:52
*** zz_jgrimm is now known as jgrimm15:52
mesterydougwig: which one?15:53
dougwiglib split spec.  since it's now in-tree, and going to evolve, and the spec has objections that they want to see more of what it's going to be, would that make more sense to do with the new process?  document the use cases, and then show the files in the first commit/devref doc?15:53
dougwigi think it's probably the same work to work up the first lib patch than to rewrite that spec.15:53
mesterydougwig: I'm torn on this one. It's a lib-split, so I can see moving forward with the spec as-is, but devref doc may make sense too. I'd lean towards the latter rather than the former.15:53
mesterydougwig: Abandon and move on to a patch then?15:54
dougwighow about i vastly trim the spec, and move half into devref?15:54
mestery++15:54
dougwigi'll get a re-spin today.15:54
mesterythanks15:55
marun++15:55
*** mrmartin has joined #openstack-meeting-315:55
mesteryOK moving along15:56
mesteryI suggest we do RFE reviews offline unless anyone wants to discuss a specific one here. Thoughts?15:56
dougwigi assume most of them are non-contentious, e.g., this group doesn't want to see lbaas RFE's, so that's fine by me.15:57
mestery++15:57
mesteryDone!15:57
dougwigi do need a quick primer on what states/milestones you want things put into when they're approved, though.15:57
mesterydougwig: Don't do that, the new release process maps them after they merge15:58
mesteryLazy releases15:58
mesteryI mean, you can map them if you want, but don't have to15:58
dougwigright, but they have to go from NEW -> ?15:58
mesteryAh15:58
mesteryPing me and I'll take care of that for you15:58
mesteryOK, thanks folks!15:58
mestery#endmeeting15:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:58
openstackMeeting ended Wed Jun 10 15:58:52 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-06-10-15.30.html15:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-06-10-15.30.txt15:58
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-06-10-15.30.log.html15:58
*** ivar-lazzaro has joined #openstack-meeting-315:59
*** shwetaap has joined #openstack-meeting-316:00
*** singlethink has joined #openstack-meeting-316:01
*** john-davidge has joined #openstack-meeting-316:04
*** cbouch has quit IRC16:04
*** shwetaap has quit IRC16:05
*** rushiagr_away is now known as rushiagr16:06
*** Networkn3rd has joined #openstack-meeting-316:08
*** iben has quit IRC16:08
*** cbouch has joined #openstack-meeting-316:13
*** ivar-lazzaro has quit IRC16:14
*** vgridnev has joined #openstack-meeting-316:16
*** e0ne is now known as e0ne_16:25
*** e0ne_ is now known as e0ne16:25
*** iben has joined #openstack-meeting-316:25
*** mrmartin has quit IRC16:27
*** stevemar has joined #openstack-meeting-316:31
*** praveens has quit IRC16:33
*** hitalia has joined #openstack-meeting-316:36
*** Swami has joined #openstack-meeting-316:37
*** jckasper has quit IRC16:39
*** praveens has joined #openstack-meeting-316:41
*** nfedotov has quit IRC16:45
*** sahid has quit IRC16:46
*** cbouch has quit IRC16:46
*** sarob has joined #openstack-meeting-316:48
*** Networkn3rd has quit IRC16:51
*** JeanBriceCombebi has quit IRC16:52
*** ivar-lazzaro has joined #openstack-meeting-316:55
*** mfedosin has quit IRC16:55
*** iben has quit IRC16:55
*** cbouch has joined #openstack-meeting-316:57
*** marun has quit IRC16:58
*** e0ne has quit IRC17:11
*** puranamr has joined #openstack-meeting-317:11
*** shwetaap has joined #openstack-meeting-317:12
*** singleth_ has joined #openstack-meeting-317:16
*** shwetaap1 has joined #openstack-meeting-317:16
*** gsagie_ has joined #openstack-meeting-317:18
*** singlethink has quit IRC17:20
*** shwetaap has quit IRC17:20
*** safchain has quit IRC17:20
*** praveens has quit IRC17:23
*** yamamoto has quit IRC17:23
*** belmoreira has joined #openstack-meeting-317:30
*** Yi_ has joined #openstack-meeting-317:31
*** sdake has quit IRC17:31
*** sbalukoff has joined #openstack-meeting-317:32
*** yamamoto has joined #openstack-meeting-317:36
*** ivar-lazzaro has quit IRC17:37
*** krtaylor has quit IRC17:37
*** jckasper has joined #openstack-meeting-317:41
*** shwetaap1 has quit IRC17:41
*** yamahata has quit IRC17:42
*** mwang2_ has joined #openstack-meeting-317:44
*** mwang2 has quit IRC17:45
*** Sukhdev has quit IRC17:46
*** Sukhdev has joined #openstack-meeting-317:46
*** iben has joined #openstack-meeting-317:49
*** iben has quit IRC17:51
*** Yi_ has quit IRC17:53
*** MarkAtwood has quit IRC17:54
*** fallenpegasus has quit IRC17:55
*** marun has joined #openstack-meeting-317:56
*** krtaylor has joined #openstack-meeting-317:59
*** Yi_ has joined #openstack-meeting-318:00
*** marun has quit IRC18:01
*** s3wong has joined #openstack-meeting-318:06
*** anusree has quit IRC18:08
*** yamamoto has quit IRC18:09
*** stevemar has quit IRC18:10
*** john-davidge has quit IRC18:14
*** pkarikh has quit IRC18:14
*** vnod has joined #openstack-meeting-318:16
*** baoli_ has quit IRC18:17
*** yamahata has joined #openstack-meeting-318:20
*** zz_natorious is now known as natorious18:21
*** Sukhdev has quit IRC18:22
*** rushiagr is now known as rushiagr_away18:23
*** bradjones has quit IRC18:23
*** bradjones has joined #openstack-meeting-318:24
*** bradjones has quit IRC18:24
*** bradjones has joined #openstack-meeting-318:24
*** gsagie_ has quit IRC18:25
*** singlethink has joined #openstack-meeting-318:26
*** amotoki has quit IRC18:28
*** cbouch has quit IRC18:29
*** singleth_ has quit IRC18:29
*** ivar-lazzaro has joined #openstack-meeting-318:29
*** Networkn3rd has joined #openstack-meeting-318:30
*** ivar-lazzaro has quit IRC18:34
*** pc_m has joined #openstack-meeting-318:35
*** fallenpegasus has joined #openstack-meeting-318:38
*** cbader has quit IRC18:39
*** cbouch has joined #openstack-meeting-318:40
*** ivar-lazzaro has joined #openstack-meeting-318:40
*** jwy has joined #openstack-meeting-318:43
*** jwy has left #openstack-meeting-318:43
*** julim has quit IRC18:49
*** e0ne has joined #openstack-meeting-318:52
*** pc_m has left #openstack-meeting-318:52
*** rhagarty_ has joined #openstack-meeting-318:53
*** rhagarty_ has quit IRC18:54
*** e0ne has quit IRC18:57
*** nateziemann has joined #openstack-meeting-318:58
*** ajo has joined #openstack-meeting-319:00
*** e0ne has joined #openstack-meeting-319:00
*** Swami has quit IRC19:05
*** e0ne has quit IRC19:05
*** yamamoto has joined #openstack-meeting-319:10
*** Sukhdev has joined #openstack-meeting-319:14
*** yamamoto has quit IRC19:15
*** puranamr has quit IRC19:17
*** jtomasek has quit IRC19:24
*** amotoki has joined #openstack-meeting-319:29
*** mrunge has quit IRC19:29
*** puranamr has joined #openstack-meeting-319:30
*** ajo has quit IRC19:30
*** stevemar has joined #openstack-meeting-319:30
*** hitalia has quit IRC19:32
*** cbouch has quit IRC19:33
*** Yi_ has quit IRC19:34
*** amotoki has quit IRC19:34
*** baoli has joined #openstack-meeting-319:36
*** hitalia has joined #openstack-meeting-319:38
*** Aish has joined #openstack-meeting-319:41
*** sridhar_ram has quit IRC19:45
*** nateziemann has quit IRC19:47
*** lblanchard has quit IRC19:51
*** lblanchard has joined #openstack-meeting-319:53
*** fallenpegasus has quit IRC19:59
*** e0ne has joined #openstack-meeting-320:00
*** mwang2_ has quit IRC20:00
*** mwang2 has joined #openstack-meeting-320:01
*** crobertsrh has joined #openstack-meeting-320:01
*** puranamr has quit IRC20:03
*** julim has joined #openstack-meeting-320:04
*** mwang2_ has joined #openstack-meeting-320:05
*** sdake has joined #openstack-meeting-320:06
*** mwang2 has quit IRC20:08
*** fallenpegasus has joined #openstack-meeting-320:08
*** marun has joined #openstack-meeting-320:08
*** VW has quit IRC20:17
*** VW has joined #openstack-meeting-320:19
*** ajo has joined #openstack-meeting-320:21
*** ajo has quit IRC20:21
*** sridhar_ram has joined #openstack-meeting-320:21
*** marun has quit IRC20:22
*** ajo has joined #openstack-meeting-320:23
*** Yi_ has joined #openstack-meeting-320:24
*** VW has quit IRC20:24
*** sridhar_ram has quit IRC20:24
*** Yi__ has joined #openstack-meeting-320:25
*** sridhar_ram has joined #openstack-meeting-320:26
*** Yi_ has quit IRC20:29
*** VW has joined #openstack-meeting-320:30
*** julim has quit IRC20:33
*** baoli_ has joined #openstack-meeting-320:34
*** sridhar_ram1 has joined #openstack-meeting-320:35
*** e0ne has quit IRC20:35
*** ajmiller_ has joined #openstack-meeting-320:36
*** sridhar_ram has quit IRC20:36
*** sdake has quit IRC20:37
*** stevemar has quit IRC20:38
*** baoli has quit IRC20:39
*** ajmiller has quit IRC20:40
*** marun has joined #openstack-meeting-320:40
*** puranamr has joined #openstack-meeting-320:47
*** stevemar has joined #openstack-meeting-320:52
*** mwagner_afk has quit IRC20:53
*** ajo has quit IRC20:55
*** puranamr has quit IRC20:57
*** fallenpegasus has quit IRC20:58
*** puranamr has joined #openstack-meeting-320:58
bauzascells meeting mmm ?20:59
alaski#startmeeting nova_cells21:00
openstackMeeting started Wed Jun 10 21:00:07 2015 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: nova_cells)"21:00
openstackThe meeting name has been set to 'nova_cells'21:00
alaskio/21:00
bauzas\o21:00
melwitto/21:00
belmoreirao/21:00
dansmitho/21:00
*** crobertsrh is now known as _crobertsrh21:00
alaski#topic Tempest testing21:00
*** openstack changes topic to "Tempest testing (Meeting topic: nova_cells)"21:01
alaskimelwitt: the floor is yours21:01
melwittnothing new this week, logstash link for the job is http://goo.gl/b7R8wq21:01
melwittlooks to be in the same expected state, the patch for the undelete is still up at https://review.openstack.org/17651821:02
melwittthe other race condition patch https://review.openstack.org/188126 merged last night so that's cool21:02
alaskithere was some discussion at the end of that one21:02
alaskioh, nice21:02
alaskiare you good on https://review.openstack.org/176518, or still unsure about it21:03
bauzaswell21:03
*** belmoreira has quit IRC21:04
bauzasI'm +1 because the trade-off would look like more benefits than debt21:04
*** songole has joined #openstack-meeting-321:04
*** songole has left #openstack-meeting-321:04
melwittI guess overall, we can't get the same behavior it had, I think. it intended to create an instance row if there wasn't one found (because read_deleted="yes")21:04
*** belmoreira has joined #openstack-meeting-321:05
melwittit intended to ignore InstanceInfoCacheNotFound. now we have instance.save() doing a lot of things inside it, which can raise NotFound21:05
bauzasmelwitt: yup that's my point21:05
bauzasmelwitt: it could still be raising a NotFound, but I think it's okay21:05
alaskiis a create going to undelete something it shouldn't?21:06
bauzasbecause there is a big except exc.NotFound:21:06
alaskiif not then it seems fine as is21:06
*** Yi__ has quit IRC21:06
melwittI think my concern is around, if we get NotFound for something other than InstanceNotFound, we would instance.create(). I don't know if maybe it should be like catch InstanceNotFound, create if that, else if it's other NotFound, pass21:08
melwittI don't know if that can really happen, I haven't seen it21:08
bauzasmmm21:09
alaskiI like that approach21:09
melwittokay, I can do that.21:09
alaskicool, I just backed off to a +1 for now21:10
bauzasfair21:10
*** fallenpegasus has joined #openstack-meeting-321:10
melwittI'll update it in a few. that's all I have on the testing, once this patch merges I'll be watching for a drop in job failures, and if that continues X amount of time we'll make it vote?21:11
alaskiI noticed on the logstash link that failures are down to about 5 a day or less for the last 4 days21:11
alaskimelwitt: that's the plan21:11
melwittcool21:11
alaskithanks for the update21:12
alaski#topic Specs21:12
*** openstack changes topic to "Specs (Meeting topic: nova_cells)"21:12
alaskihttps://review.openstack.org/#/c/190209/21:12
alaskiI wrote up a devref change walking through how some things will work with cells v221:13
alaskiand included relevant specs for changes needed, and pointed out where specs are missing21:13
bauzasthat's a DNM ?21:13
alaskiit's subject to change based on spec feedback21:13
bauzasalaski: are you still -W it ?21:13
bauzasalaski: oh ok21:14
alaskiif it seems useful I'm not against it merging, but that wasn't my intention21:14
*** Sukhdev has quit IRC21:14
alaskiit was more an exercise for me to see the gaps in specs, and to point people to when they ask why a spec is proposing a thing21:15
bauzasfair point21:15
melwittcool, good to have21:16
*** VW has quit IRC21:16
alaskiand it's a good medium for feedback which is why I chose it over an etherpad21:16
*** lblanchard has quit IRC21:17
alaskibelmoreira: any updates on the specs you have been working on?21:17
belmoreiraalaski: not yet in that spec21:18
belmoreiratoday we proposed: https://review.openstack.org/#/c/190147/21:18
belmoreiraI added it to the meeting agenda21:18
alaskiahh, needed to refresh21:19
alaskiI added it to the priorities etherpad for visibility21:19
bauzasah21:20
bauzasflavors, mmm ? :)21:20
belmoreiragreat21:20
alaskinow that I have a list of gaps I'm going to go crazy proposing specs soon21:21
alaskiheads up21:21
alaskianything else on specs?21:21
*** ziemann has joined #openstack-meeting-321:21
alaski#topic Open discussion21:22
*** openstack changes topic to "Open discussion (Meeting topic: nova_cells)"21:22
alaskianyone have a topic for open discussion?21:22
*** Networkn3rd has quit IRC21:22
* bauzas was off for the last 2 days so pass21:22
*** singleth_ has joined #openstack-meeting-321:22
*** sdake has joined #openstack-meeting-321:22
*** asahlin is now known as asahlin_away21:23
alaskithe only spec approved right now is the host_mapping one so that limits the amount of coding for the moment21:23
alaskithere's also the persist request spec one I guess, but that's blocked atm I think21:23
alaskiso that just leaves specs to write, and docs21:24
alaskithat's it from me21:24
dansmithI did some review on one today21:24
dansmiththe flavors one21:24
alaskinice21:24
dansmithit punted on migration, but it seems like we might as well include that in the spec since it's critical21:24
alaskiI did set a precedent of splitting the table creation and migration21:25
belmoreiradansmith: yes, it's a fair point. The migration plan should be added21:25
alaskibut now that the database is in place that may not be the right path21:25
*** singlethink has quit IRC21:25
dansmithwell21:26
dansmithin this case I think it's important because we'll need to migrate them before we can switch over,21:27
dansmithwhere the instance mapping is kindof a cache at this point21:27
dansmithjust seems like this one should be "move flavors from here to there"21:27
alaskiyeah, I agree with that21:28
*** nortman has joined #openstack-meeting-321:28
alaskithere was a lot more about how to create the database in the first specs adding tables21:28
alaskinow that it's there, the interesting bit is moving data21:28
bauzasagreed21:28
belmoreirayes, I agree21:28
dansmithoh, also21:29
alaskicool.  I'll also take a look at the spec, but probably tomorrow21:29
dansmithI started on the patch to make devstack (and then grenade) create the api db21:29
dansmithit was failing on something, I haven't looked why,21:29
dansmithbut at least that is started21:29
dansmithhttps://review.openstack.org/19028921:30
dansmithgotta have that in devstack and then a change to grenade21:30
*** amotoki has joined #openstack-meeting-321:31
alaskivery nice21:31
bauzascool indeed21:31
dansmithoh, heh I just failed bashate21:31
dansmithI think I can handle that :D21:31
alaskiit's great to see more reviews up21:32
alaskianything else from anyone?21:32
alaski#endmeeting21:33
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:33
openstackMeeting ended Wed Jun 10 21:33:32 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-06-10-21.00.html21:33
alaskithanks all21:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-06-10-21.00.txt21:33
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-06-10-21.00.log.html21:33
*** peristeri has quit IRC21:33
*** nortman has left #openstack-meeting-321:34
*** amotoki has quit IRC21:36
*** singlethink has joined #openstack-meeting-321:38
*** baoli_ has quit IRC21:39
*** baoli has joined #openstack-meeting-321:39
*** Swami has joined #openstack-meeting-321:40
*** singleth_ has quit IRC21:41
*** vgridnev has quit IRC21:43
*** singlethink has quit IRC21:44
*** baoli has quit IRC21:46
*** baoli has joined #openstack-meeting-321:46
*** puranamr has quit IRC21:47
*** sridhar_ram1 is now known as sridhar_ram21:48
*** lsmola has quit IRC22:01
*** ivar-laz_ has joined #openstack-meeting-322:02
*** ivar-lazzaro has quit IRC22:05
*** salv-orlando has joined #openstack-meeting-322:05
*** stevemar has quit IRC22:06
*** Sukhdev has joined #openstack-meeting-322:07
*** fallenpegasus has quit IRC22:08
*** singlethink has joined #openstack-meeting-322:09
*** alexpilotti has quit IRC22:13
*** alexpilotti has joined #openstack-meeting-322:17
*** salv-orlando has quit IRC22:18
*** baoli has quit IRC22:28
*** stevemar has joined #openstack-meeting-322:29
*** amotoki has joined #openstack-meeting-322:32
*** s3wong has quit IRC22:34
*** jgrimm is now known as zz_jgrimm22:34
*** s3wong has joined #openstack-meeting-322:36
*** salv-orlando has joined #openstack-meeting-322:36
*** baoli has joined #openstack-meeting-322:36
*** shwetaap has joined #openstack-meeting-322:36
*** amotoki has quit IRC22:36
*** singlethink has quit IRC22:36
*** ziemann has quit IRC22:37
*** shwetaap1 has joined #openstack-meeting-322:42
*** shwetaap has quit IRC22:46
*** sigmavirus24 is now known as sigmavirus24_awa22:46
*** puranamr has joined #openstack-meeting-322:48
*** yamamoto has joined #openstack-meeting-322:48
*** baoli has quit IRC22:50
*** baoli has joined #openstack-meeting-322:51
*** puranamr has quit IRC22:53
*** yamamoto has quit IRC22:53
*** bknudson has quit IRC22:54
*** krtaylor has quit IRC22:54
*** neillc is now known as neillc_bf22:56
*** baoli has quit IRC22:58
*** puranamr has joined #openstack-meeting-323:01
*** nateziemann has joined #openstack-meeting-323:03
*** Aish has left #openstack-meeting-323:04
*** marun has quit IRC23:06
*** Piet has joined #openstack-meeting-323:08
*** natorious is now known as zz_natorious23:09
*** sdake has quit IRC23:10
*** Gavin_Pratt_HP has joined #openstack-meeting-323:13
*** Yi_ has joined #openstack-meeting-323:17
*** yamamoto has joined #openstack-meeting-323:17
*** Yi_ has quit IRC23:21
*** ivar-laz_ has quit IRC23:24
*** ivar-lazzaro has joined #openstack-meeting-323:25
*** yamamoto has quit IRC23:34
*** sridhar_ram has quit IRC23:38
*** shwetaap1 has quit IRC23:38
*** krtaylor has joined #openstack-meeting-323:38
*** david-lyle has quit IRC23:40
*** carl_baldwin has quit IRC23:42
*** Yi_ has joined #openstack-meeting-323:50
*** Gavin_Pratt_HP has quit IRC23:59

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