Tuesday, 2016-03-29

*** harlowja has quit IRC00:16
*** vilobhmm11 has joined #openstack-meeting-cp00:29
*** sdake_ has joined #openstack-meeting-cp00:35
*** sdake has quit IRC00:38
*** angdraug has quit IRC00:40
*** sdake_ has quit IRC00:47
*** sdake has joined #openstack-meeting-cp00:47
*** harlowja has joined #openstack-meeting-cp00:51
*** _amrith_ is now known as amrith00:57
*** vilobhmm111 has joined #openstack-meeting-cp01:07
*** vilobhmm11 has quit IRC01:08
*** vilobhmm11 has joined #openstack-meeting-cp01:22
*** vilobhmm111 has quit IRC01:23
*** vilobhmm11 has quit IRC01:33
*** amrith is now known as _amrith_01:59
*** harlowja has quit IRC01:59
*** lifeless has quit IRC02:43
*** lifeless has joined #openstack-meeting-cp02:44
*** harlowja has joined #openstack-meeting-cp02:47
*** harlowja has quit IRC02:52
*** sheel has joined #openstack-meeting-cp02:54
*** _amrith_ is now known as amrith02:59
*** askb has joined #openstack-meeting-cp03:15
*** vilobhmm11 has joined #openstack-meeting-cp03:25
*** harlowja has joined #openstack-meeting-cp03:29
*** harlowja has quit IRC04:06
*** vilobhmm11 has quit IRC04:07
*** harlowja has joined #openstack-meeting-cp04:09
*** vgridnev has joined #openstack-meeting-cp04:48
*** vilobhmm11 has joined #openstack-meeting-cp05:30
*** sdake_ has joined #openstack-meeting-cp05:50
*** sdake has quit IRC05:52
*** vgridnev has quit IRC06:15
*** harlowja has quit IRC06:19
*** vgridnev has joined #openstack-meeting-cp06:20
*** markvoelker has joined #openstack-meeting-cp06:22
*** markvoelker_ has joined #openstack-meeting-cp06:23
*** vgridnev has quit IRC06:26
*** vgridnev has joined #openstack-meeting-cp06:27
*** markvoelker has quit IRC06:27
*** harlowja has joined #openstack-meeting-cp06:32
*** markvoelker_ has quit IRC06:43
*** markvoelker has joined #openstack-meeting-cp06:44
*** markvoelker has quit IRC07:12
*** vgridnev has quit IRC07:13
*** vgridnev has joined #openstack-meeting-cp07:18
*** askb has quit IRC07:20
*** pgreg has joined #openstack-meeting-cp07:21
*** sdake_ has quit IRC07:22
*** pgreg has quit IRC07:23
*** sdake has joined #openstack-meeting-cp07:25
*** pgreg has joined #openstack-meeting-cp07:27
*** bauwser is now known as bauzas07:47
*** markvoelker has joined #openstack-meeting-cp08:13
*** markvoelker has quit IRC08:17
*** dims has quit IRC08:26
*** dims has joined #openstack-meeting-cp08:31
*** lifeless has quit IRC09:39
*** lifeless has joined #openstack-meeting-cp09:40
*** pgreg has quit IRC10:04
*** sdake has quit IRC10:10
*** markvoelker has joined #openstack-meeting-cp10:14
*** vilobhmm11 has quit IRC10:15
*** markvoelker has quit IRC10:20
*** flaper87 has quit IRC10:36
*** flaper87 has joined #openstack-meeting-cp10:36
*** sdague has joined #openstack-meeting-cp11:12
*** markvoelker has joined #openstack-meeting-cp11:16
*** askb has joined #openstack-meeting-cp11:18
*** markvoelker has quit IRC11:21
*** vgridnev has quit IRC12:05
*** markvoelker has joined #openstack-meeting-cp12:17
*** raildo-afk is now known as raildo12:20
*** markvoelker has quit IRC12:22
*** annegentle has joined #openstack-meeting-cp12:52
*** ninag has joined #openstack-meeting-cp13:03
*** markvoelker has joined #openstack-meeting-cp13:18
*** markvoelker has quit IRC13:22
*** markvoelker has joined #openstack-meeting-cp13:23
*** markvoelker_ has joined #openstack-meeting-cp13:28
*** markvoelker has quit IRC13:32
*** amrith is now known as _amrith_13:35
*** sigmavirus24 has joined #openstack-meeting-cp14:08
*** markvoelker_ has quit IRC14:15
*** _amrith_ is now known as amrith14:24
*** sdake has joined #openstack-meeting-cp14:27
*** sdake_ has joined #openstack-meeting-cp14:30
*** sdake has quit IRC14:32
*** sdake_ is now known as sdake14:37
*** askb_ has joined #openstack-meeting-cp15:24
*** claudiub|2 has joined #openstack-meeting-cp15:25
*** askb has quit IRC15:28
*** harlowja has quit IRC15:41
*** angdraug has joined #openstack-meeting-cp15:46
*** askb_ is now known as askb16:17
*** harlowja has joined #openstack-meeting-cp16:29
*** annegentle has quit IRC16:47
*** harlowja_ has joined #openstack-meeting-cp16:58
*** harlowja has quit IRC17:00
*** docaedo has quit IRC17:07
*** melwitt has quit IRC17:07
*** sballe_ has quit IRC17:07
*** tpeoples has quit IRC17:07
*** adam_g has quit IRC17:07
*** dhellmann has quit IRC17:07
*** kfox1111 has quit IRC17:07
*** sigmavirus24 has quit IRC17:07
*** fungi has quit IRC17:07
*** cfouts has quit IRC17:07
*** sdake_ has joined #openstack-meeting-cp17:07
*** sdake has quit IRC17:07
*** gnarld_ has joined #openstack-meeting-cp17:07
*** kfox1111_ has joined #openstack-meeting-cp17:07
*** _sigmavirus24 has joined #openstack-meeting-cp17:07
*** kinrui has joined #openstack-meeting-cp17:07
*** adam_g` has joined #openstack-meeting-cp17:07
*** dhellmann has joined #openstack-meeting-cp17:07
*** kinrui is now known as fungi17:07
*** melwitt has joined #openstack-meeting-cp17:08
*** adam_g` is now known as adam_g17:08
*** adam_g has quit IRC17:08
*** adam_g has joined #openstack-meeting-cp17:08
*** _sigmavirus24 is now known as sigmavirus2417:14
*** sigmavirus24 has joined #openstack-meeting-cp17:14
*** tpeoples has joined #openstack-meeting-cp17:19
*** harlowja has joined #openstack-meeting-cp17:20
*** sballe_ has joined #openstack-meeting-cp17:21
*** sballe_ has quit IRC17:22
*** harlowja_ has quit IRC17:22
*** sballe_ has joined #openstack-meeting-cp17:23
*** askb has quit IRC17:24
*** amrith is now known as _amrith_17:29
*** docaedo_ has joined #openstack-meeting-cp17:30
*** docaedo_ is now known as docaedo17:30
*** sdake has joined #openstack-meeting-cp17:33
*** sdake_ has quit IRC17:34
*** annegentle has joined #openstack-meeting-cp17:48
*** sdake has quit IRC17:57
*** sdake has joined #openstack-meeting-cp18:02
*** sdake has quit IRC18:08
*** sdake_ has joined #openstack-meeting-cp18:08
*** ildikov has joined #openstack-meeting-cp18:15
*** _amrith_ is now known as amrith18:19
*** angdraug has quit IRC18:44
*** david-lyle has quit IRC18:45
*** david-lyle has joined #openstack-meeting-cp18:46
*** vilobhmm11 has joined #openstack-meeting-cp18:48
*** vilobhmm11 has quit IRC18:50
*** vilobhmm11 has joined #openstack-meeting-cp18:50
*** vilobhmm11 has quit IRC18:52
*** vilobhmm11 has joined #openstack-meeting-cp18:52
*** vilobhmm11 has quit IRC18:54
*** vilobhmm11 has joined #openstack-meeting-cp18:54
*** vilobhmm11 has quit IRC18:55
*** vilobhmm11 has joined #openstack-meeting-cp18:55
*** angdraug has joined #openstack-meeting-cp18:58
*** sdake_ is now known as sdake19:01
*** raildo is now known as raildo-afk19:12
*** raildo-afk is now known as raildo19:45
*** sdake_ has joined #openstack-meeting-cp19:55
*** sheel has quit IRC19:57
*** sdake has quit IRC19:58
*** sdake_ is now known as sdake20:02
*** samueldmq has joined #openstack-meeting-cp20:02
*** gordc has joined #openstack-meeting-cp20:08
*** diablo_rojo has joined #openstack-meeting-cp20:11
*** vilobhmm11 has quit IRC20:30
*** vilobhmm11 has joined #openstack-meeting-cp20:31
*** annegentle has quit IRC20:32
*** annegentle has joined #openstack-meeting-cp20:33
*** sigmavirus24 is now known as sigmavirus24_awa20:37
*** sigmavirus24_awa is now known as sigmavirus2420:37
*** raildo is now known as raildo-afk20:47
*** hongbin_ has joined #openstack-meeting-cp20:59
*** vilobhmm11 has quit IRC20:59
*** vilobhmm11 has joined #openstack-meeting-cp20:59
*** mriedem has joined #openstack-meeting-cp20:59
*** mc_nair has joined #openstack-meeting-cp21:00
mriedemis there a cp meeting today?21:00
diablo_rojomriedem: I thought there was21:01
thingeeyes21:01
nikhilo/21:01
vilobhmm11o/21:01
*** cdent has joined #openstack-meeting-cp21:01
nikhilhoping my nick is in the courtesy reminders!21:01
elmikoo/21:01
dimsit's happening now on the -meeting channel21:01
nikhilit is!21:01
*** tristanC has joined #openstack-meeting-cp21:01
thingeecourtesy ping for Qiming TravT gordc dirk mriedem SergeyLukjanov21:01
thingeecourtesy ping for daemontool jroll boris-42 redrobot flaper87 rhochmuth21:01
thingeecourtesy ping for fungi flwang dims vipul johnthetubaguy rakhmerov21:01
jrollohai21:01
thingeecourtesy ping for docaedo stevemar mtreinish bswartz adam_g adrian_otto21:01
thingeecourtesy ping for zigo Piet sdake mugsie sheeprine thinrichs21:01
thingeecourtesy ping for jklare loquacities smelikyan Daisy skraynev odyssey4me21:01
thingeecourtesy ping for samueldmq nikhil21:01
thingee#startmeeting cross-project21:02
openstackMeeting started Tue Mar 29 21:02:05 2016 UTC and is due to finish in 60 minutes.  The chair is thingee. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** openstack changes topic to " (Meeting topic: cross-project)"21:02
samueldmqhi all21:02
openstackThe meeting name has been set to 'cross_project'21:02
docaedoo/21:02
cdento/21:02
EmilienMo/21:02
mriedemo/21:02
samueldmqo/21:02
thingeehey everyone21:02
kencjohnstono/21:02
diablo_rojoHello :)21:02
thingeea lot to talk about today, let me tell ya21:02
*** dtroyer has joined #openstack-meeting-cp21:02
dimso/ we need to invite the incoming PTL(s)21:02
dhellmanno/21:02
sdakeyar21:02
dtroyero/21:02
nikhilo/21:02
thingeeagenda today https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda21:02
adam_go/21:02
thingee#topic Team announcements (horizontal, vertical, diagonal)21:02
fungii feel both incoming and outgoing21:02
*** openstack changes topic to "Team announcements (horizontal, vertical, diagonal) (Meeting topic: cross-project)"21:03
thingee#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/090737.html Changes to release ACLs for official projects in Newton21:03
thingeehi dhellmann21:03
dhellmannhi21:03
hongbin_o/21:03
mtreinisho/21:03
*** xarses has joined #openstack-meeting-cp21:03
david-lyleo/21:03
dhellmannthis is the next phase of the release automation work we're doing21:03
dimsfungi : ++21:03
xarseso/21:03
dhellmannfor newton, all official project teams will use the openstack/releases repo to request and document releases21:03
dhellmannsee the email thread for details, and the README in the repo, and then let me know if you have questions21:03
thingeedhellmann: while I have you here21:04
dhellmannmost of you have already been using it, so it won't really be a big change21:04
samueldmqdhellmann: so release notes don't go in individual prject repos, but in a centralized repo instead21:04
thingee#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/090517.html Release liaisons for newton21:04
EmilienMdhellmann: excellent. Does release tags matter?21:04
dhellmannsamueldmq : no, this is to request a tag for a release, not a release note21:04
samueldmqdhellmann: sure, I will look at the README and the eamil threads, sorry21:04
dhellmannah, yeah, thanks thingee21:04
dhellmannthe other thing we're changing next cycle is we want to have only one release liaison per project team21:04
EmilienMdhellmann: for example, Puppet OpenStack group is applying to some release tags with the goal to release our deliverables like other projects https://review.openstack.org/29738221:05
dhellmannwe had a few projects with lots of deliverables assign a different person per deliverable, and that turned out to be too much for us to keep up with21:05
dhellmannEmilienM : release:managed will stay around for now to indicate that we work really closely with the team, but it isn't required for use of openstack/releases21:05
EmilienMdhellmann: ack.21:05
thingeethanks dhellmann21:06
thingee#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/090659.html Oh Swagger, where art thou?21:06
dhellmannthanks, thingee21:06
thingeeannegentle: you around?21:06
annegentlehere!21:06
*** ninag has quit IRC21:06
thingeelooks like we have some changes coming in the swagger with some new approach coming soon?21:06
annegentlethanks for bringing it up21:06
annegentleyes, that email and sdague's follow up give a good overview21:07
annegentleI wanted to be sure to be available for any questions. We're making good progress with the proof of concept21:07
bknudsonis this going to apply to all projects?21:07
bknudsonor just nova?21:07
annegentlebknudson: yes, the POC is for nova but I'd like keystone to look early and often21:08
thingeelooks like sdague is spearheading this for nova21:08
*** Rocky_g has joined #openstack-meeting-cp21:08
thingeewith a new approach21:08
bknudsonis there a conversion tool like fairyslipper?21:08
annegentlebknudson: yes21:08
annegentlewadl2rst21:08
annegentle#link https://github.com/annegentle/wadl2rst21:08
annegentleit does migration and only migration, fairy-slipper has a migration portion and a display/ui portion21:09
jrollI assume the rest_* extension will be broken out to a separate project?21:09
annegentlejroll: sdague can comment on that, he's wrangling the extensions21:09
jrollsure21:10
thingeespeaking of sdague21:10
thingee#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/090754.html Service Catalog TNG work in Mitaka ... next steps21:10
* thingee looks to the left and looks to the right21:10
*** breton has joined #openstack-meeting-cp21:10
jrollthis is super neat overall, though, thanks annegentle and sdague for pushing on it :)21:10
annegentlemight be late for sdague21:10
cdentthe sctng message struck me as accurate and a good plan21:11
thingee#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/090546.html Kolla Deploying the big tent21:11
thingeesdake: ^21:11
bknudsonwe sure do have a lot of openstack deploy tools21:11
sdakemoment catching up21:12
thingeeit's just your announcement on needing help with kolla21:12
thingeeto the dev ml21:12
sdakeoh21:12
sdakeya it woudl be cool if new projects contirbuted21:13
sdakelike with the devstak plugin model21:13
sdakei'm going to try to get kolla cogating with compute-kit projects this cycle21:13
bknudsonwhat's compute-kit?21:13
sdakebecause nobody usess devstack in production21:13
sdakegnarld_ glance nova neutron kesytone and its deps21:14
mriedemand our ci system doesn't use kolla21:14
thingeebknudson: https://www.openstack.org/software/sample-configs/21:14
thingee"compute starter kit"21:14
jrollI'd be surprised if most teams have people with enough free time to contribute to kolla, personally21:14
sdakekolla is ci'ed but just barely21:14
jrollmaybe if there was a plugin model where I could have something in my tree21:14
sdakejroll we have discussed that but technically it is difficult21:15
EmilienMlike a tempest pluging?21:15
jrollsure21:15
mriedemjroll: but you wouldn't know if that works unless ironic had a kolla ci job that uses it21:15
sdakebordering on impossible21:15
jrollmriedem: yep21:15
dimsjroll : personally i want look at rabbitmq and keystone in kolla when i get a chance. though i understand those are already taken care of21:15
mriedemprojects have devstack plugins so they can run dsvm jobs using our infra model21:15
jrollanyway, what I'm trying to say is that (at least ironic) has plenty to do already without contributing to all of the various deployment projects21:16
dimssdake : how would one poke at just containers running stuff that's of interest to them?21:16
EmilienMpuppet modules have one module per component, why don't you follow this model?21:16
sdakejroll ironic is already implemented so your in the clear ;)21:16
jrollyay.21:16
dimslol21:16
thingeeand real quickly cause we have to move on...21:16
thingee#link https://etherpad.openstack.org/p/newton-cross-project-sessions cross-project summit sessions21:16
thingeesdague is asking for your sessions, get 'em in!21:16
sdakewt session on plugins21:16
sdakewe have all kinds of plugin patterns in openstack21:17
thingee#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/090606.html Austin Design Summit Track Layout21:17
sdakei know its unreasonable ot epect eveyrone to standardize on one21:17
sdakebut can we not make mroe ;)21:17
thingeethe layout for all official projects is out. review it. get back to ttx and I21:17
thingee#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/090422.html PTL Election Results21:17
thingeecongrats all!21:17
ttxplanning to officialize tomorrow, so last day for comments21:17
xarsesEmilienM: should we put the deployment orchestrator tool up?21:17
thingee#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/090421.html TC Nominations Start21:17
elmikodims: i found the kolla docs and install pretty approachable, and configurable. the team was awesome with questions too =)21:17
thingee#link http://www.openstack.org/blog/2016/03/openstack-developer-mailing-list-digest-20160318-2/ Dev Digest from last week21:18
thingeecatch up on the dev list reminder^21:18
thingeealright lets begin, whew21:18
sdakewhy thank you elmiko21:18
dimselmiko thanks!21:18
EmilienMxarses: it was not in the agenda, but if we have time why not.21:18
xarsesEmilienM: https://etherpad.openstack.org/p/newton-cross-project-sessions21:18
harlowjahello21:18
thingee#topic Add centralized configuration options specification21:18
*** openstack changes topic to "Add centralized configuration options specification (Meeting topic: cross-project)"21:18
thingee#link https://review.openstack.org/#/c/295543/ spec21:18
thingeesigmavirus24: hi21:18
sdakejroll just for reference my emali was directed mostly at new projects to openstack in liberty/mitaka, not projeects with a long histroy21:18
sigmavirus24Sorry I'm late :)21:19
thingeeyou're on time21:19
elmikothis seems like a nice idea21:19
jrollsdake: sure, just my 2c :)21:19
sdakejroll maye its not viable,but doens't hurt to ask :)21:19
nikhilwhat are we discussing on this topic?21:20
thingeesurfacing it up for more eyes. was giving the floor to sigmavirus24 to discuss21:21
mriedemit's probably already been pointed out that there has been a team of people in nova centralizing config options and upating help text since mitaka21:21
sigmavirus24thingee: ah, sorry, didn't realize that was my cue.21:21
bknudsonkeystone has all its config options in 1 module21:21
mriedemi see mzoeller is on the xp spec so that's good21:21
sigmavirus24So kencjohnston johnthetubaguy rosmaita and I have been talking about this for a while as a cross-project effort. kencjohnston wrote the original user story around categorizing and centralizing configuration options21:22
thingee#note nova has a team of people centralizing config options and updating help text since mitaka21:22
thingee#info nova has a team of people centralizing config options and updating help text since mitaka21:22
sigmavirus24johnthetubaguy: and I were talking earlier about making them two separate cross-project specs actually only because we think the categorization efforts that I started to outline in that spec is something we think will help operators and downstream redistributors more than the centralization which is in part more focused on helping developers21:23
bknudsonthis looks like it will improve usability21:23
mriedem#link nova spec from mitaka http://specs.openstack.org/openstack/nova-specs/specs/mitaka/approved/centralize-config-options.html21:23
elmikoi brought this up on the review, but i'd be curious to see patterns for improving config usage in libraries21:23
sigmavirus24That said, I think aspects of the centralization (including the work on each option's help text) will benefit more than just developers for reasons I've described in the spec21:23
mriedemsigmavirus24: sounds identical to http://specs.openstack.org/openstack/nova-specs/specs/mitaka/approved/centralize-config-options.html21:23
sigmavirus24mriedem: that was in fact the basis of the discussion that we all had ~2 weeks ago?21:24
mriedemelmiko: that should be included given the server projects import oslo lib options21:24
mriedemok, just hope the wheel doesn't get re-invented21:24
bknudsonsince the oslo options wind up in different projects highest impact is probably there.21:24
gordcis this a guideline?21:25
elmikomriedem: ok, just wanted to voice it since we ran into issues creating the config module for castellan21:25
nikhildidn't get a chance to look at the user story21:25
sigmavirus24gordc: some of the people listed were going to start working on bringing this work to other services so more of a spec21:25
nikhilis the objective to improve awareness and consumption of these options?21:26
cdentcan we use this as a chance to destroy globals ;)21:26
harlowja;)21:26
sigmavirus24nikhil: there are multiple objectives: - allow operators to generate a config that represents the bare minimum of what they need to set, with very well written coments for each option21:26
gordcsigmavirus24: kk. but the proposal is to move all conf options under <project>/conf/* location?21:27
elmikocdent: \o/21:27
mriedemnikhil: http://docs-draft.openstack.org/43/295543/4/check/gate-openstack-specs-docs/9e24dc4//doc/build/html/specs/categorized-and-centralized-configuration-options.html#proposed-change21:27
sigmavirus24gordc: that's *part* of the proposal21:27
gordcsigmavirus24: i see. glossed over too quickly21:27
samueldmqbknudson: ++21:27
sigmavirus24gordc: right, this is why johnthetubaguy was recommending I split that particular bit out into a separate guideline/spec21:27
mriedemwe wrestled with that split in nova too, we just kept it in the same spec21:28
mriedemi think people have just been updating help text as they move the options21:28
nikhiloh well, we just moved away in glance(1 or 2 cycles back) from nicely documented configs ..21:28
dimsETOOMANYOPTIONS21:28
nikhilanyways, thanks sigmavirus24 mriedem21:29
nikhildims: == openstack ?21:29
nikhil:)21:29
mriedemthingee: sigmavirus24: so this is just fyi right?21:29
mriedemor is there an action for this meeting?21:29
jrollnikhil: wait, glance deliberately stopped nicely documenting configs? please tell me I am misunderstanding :)21:29
thingeemriedem: well I think we want more eyes so we can move forward in some direction21:29
mriedemjroll: i reada that the same way :)21:30
bknudsonso this has been adopted for nova already and the proposal is for other projects to also adopt it?21:30
nikhiljroll: it was because people wanted to keep using oslo config generator instead21:30
nikhiland trust developers to do the documentation!21:30
Rocky_gglance gets a -1 from me21:31
sigmavirus24nikhil: developers were doing that documentation anyway and the example config was constantly diverging from reality21:31
jrollnikhil: oh, so glance stopped having the docs team document everything?21:31
thingeesigmavirus24: can we reup based on johnthetubaguy and others comments and gather votes to move forward?21:31
jrollanyway, that's a side conversation I guess, don't mean to distract here21:31
sigmavirus24thingee: I think rosmaita or johnthetubaguy are going to take the spec over from me. I've been moved off this internally and have too much else going on IRL to do this in my free time21:31
nikhiljroll: no, that's still there. the sample is gone, it used to have good documentation for operators.21:31
jrollnikhil: oh yeah, got it21:31
mriedemsigmavirus24: if not johnthetubaguy, markus_z might be willing to own it21:32
sigmavirus24thingee: I'll make sure they get this feedback though21:32
nikhilsigmavirus24: yeah, I get it I get it :)21:32
mriedemhe's leading the effort in nova21:32
thingeemriedem: that would be great.21:32
mriedem"might be willing"21:32
thingeemriedem: will you ask, or shall I?21:33
thingeeor sigmavirus24 :)21:33
mriedemnot it21:33
sigmavirus24hah21:33
thingeesigmavirus24: if you can just make sure someone owns it and let me know21:33
sigmavirus24I'll throw johnthetubaguy and marcus into an email together21:33
thingeeor indicate in the review.21:33
sigmavirus24thingee: will do21:33
thingeethanks21:33
thingee#action sigmavirus24 to hand off the spec to johnthetubaguy, marcus or someone!21:33
mriedemsince johnthetubaguy is no longer PTL he probably has nothing going on anyway... :P21:34
thingeeheh21:34
dimshaha21:34
thingee#topic Delimiter - Cross Project Quota Enforcement and Management21:34
*** openstack changes topic to "Delimiter - Cross Project Quota Enforcement and Management (Meeting topic: cross-project)"21:34
thingee#link https://review.openstack.org/#/c/284454/ spec21:34
jrollhe's probably sleeping til summit21:34
thingeenikhil: hi!21:34
harlowjaoh hi21:34
nikhilhey hey21:34
harlowjavilobhmm11 yt21:34
vilobhmm11hi21:34
nikhilI think vilobhmm11 is here who wants to take on this topic21:34
thingeeour quota friends have gone off into their cross-project meeting and have been making progress. wanting to make sure the general group is liking the direction21:34
harlowjak :)21:34
* harlowja back to support-mode21:34
vilobhmm11so in the spec21:35
vilobhmm11as we discussed in yesterdays cp-quotas meeting21:35
*** sdake_ has joined #openstack-meeting-cp21:35
vilobhmm11would like to propose delimeter as a library21:35
vilobhmm11which focus on transactional gurantees for quotas (including hierarchical as well as non-hierachal namespace)21:36
nikhil#link http://eavesdrop.openstack.org/meetings/quotas_wg/2016/quotas_wg.2016-03-28-21.00.log.html21:36
vilobhmm11the respective projects will still maintain the quotas related data21:36
vilobhmm11what delimeter provides #1. easy apis to interact with quotas like #1. check_quota #2. assign_quota and the engine can take care of rest and provide transactionl gurantees21:37
vilobhmm11please go through https://review.openstack.org/#/c/284454/8/specs/delimiter-cross-project-quota-enforcement.rst for details.21:37
thingeeI seem to remember someone from trove asking about cross-project transactional guarantees. I'm guessing this will not be in the scope.21:37
nikhilthingee: it was amrith who was at the quota wg meeting yday21:38
vilobhmm11for now any consumer who consumes resources from the IaaS layer say Trove, Magnum  etc21:38
*** sdake has quit IRC21:38
jrolldelimiter.QuotaEngine(project_name="foo", ...) <- makes me think that the implementation for each project will be in the delimiter tree, is that true? if not, how does e.g. magnum interact with nova quotas?21:38
vilobhmm11so thingee that still needs to be discussed21:38
vilobhmm11jroll : the way to enforce quota will be in delimeter21:39
dimsvilobhmm11 : did you figure out the database part? who owns it. especially migrations21:39
jroll(and if so, does that require magnum be able to use the nova db?)21:39
vilobhmm11dims : the respective projects own the data21:39
nikhilI think we agreed on projects doing the migrations21:39
* dims should really read the spec21:39
vilobhmm11and hence deleimiter need not worry about data migrations21:39
thingeesince we're going with services in things like headers, per direction of service catalog, we should probably be thinking service quota, not project quota.21:39
vilobhmm11dims : %%21:39
thingeenit pick maybe21:39
nikhilall data goes in the project scope!21:39
vilobhmm11dims : ^^21:40
dimsack this will be interesting to see how that would work21:40
dimseach project implements something that the library would call back21:40
nikhilthingee: I think it will be both (and project meaning tenant in this case)21:40
bknudsonthe versioning of the database and data models will be interesting21:40
jrollvilobhmm11: so this would be used by a project to say "does this thing have enough quota to do action? if so, reserve it?"21:41
vilobhmm11jroll : yes21:41
jrollok21:41
vilobhmm11this would gurantee if certain resource requirements can be satisfies ( considering both sequntial and concurrent requests)21:41
vilobhmm11jroll : ^^21:42
jrollyep21:42
thingeeI guess while we have people here, does anyone object to the current approach?21:42
jrolljust replacing the current engine21:42
thingeeor idea21:42
dims+1 thingee21:42
bknudsonlooks like keystone isn't involved yet21:42
nikhilI'd prefer for us to settle on library approach (which is getting more of a reality now) before the summit session21:42
vilobhmm11nikhil : +121:42
dimsvilobhmm11 : should be easy to get started (http://docs.openstack.org/infra/manual/creators.html) ping me if you need a hand with library creation steps21:43
mriedemis there a POC for this in any services that has quotas today, like nova or cinder?21:43
jrollassign_quota says "Commit or rollback quota for the specified resources", which sounds like it might suffer from the same problems nova currently has, no?21:43
thingeemriedem: the usuals21:43
thingeeheh21:43
vilobhmm11dims : sure21:43
jrollcommit, do stuff, rollback on failure21:43
jrollwe forget to call rollback in one place, we're out of sync21:43
mriedemhonestly i'm not interested in this until someone shows a POC and why it's helpful for nova21:44
jrollso it's unclear to me what this is solving21:44
mriedembecause we already have a house of cards for quotas21:44
thingeemriedem: rock paper scissors with smcginnis to see which project has to do it first21:44
mriedembut it's a house of cards that we've become slightly comfortable with21:44
* jroll == mriedem, I think21:44
mriedemthingee: has to do it?21:44
dimslol mriedem21:44
dimsknown devil21:44
nikhilthe spec is pulled out of cinder impl and then iterated upon21:44
thingeemriedem: which project does a POC21:44
mriedemi'd expect whoever is driving this to provide a POC21:44
mriedemnova has other priorities for newton which aren't this21:45
vilobhmm11nikhil : glance ?21:45
* thingee was mostly having fun21:45
nikhilthere's one spec for glance, there's no impl yet21:45
nikhilvilobhmm11: ^21:45
nikhiloh, the ask was for a POC21:45
mriedemneutron doesn't even have working quotas right? you can reserve but can't unreserve or some long-standing known issue?21:45
nikhilI don't know about glance willing to do a POC, we will need to chat at the summit21:46
nikhilI'd rather have the discussions on direction first, talk more at the CP session then the project session21:46
nikhilit's a sequential train21:46
thingeemriedem: wow, did not know that21:46
* jroll posts his thoughts on the spec21:46
nikhilthere can't be concurrent requests for openstack-projects, unfortunately!21:46
harlowjaya, i'd almost like to dive into why POC on a known-cp problem is so hard to get, but i'll refrain myself21:46
thingeeok sounds like a poc then is the current requests from cp-spec liaisons?21:47
vilobhmm11jroll : thanks..it moving too quickly hereā€¦not able to address everyone's questions21:47
jrollnp21:47
jrollthingee: my request is in the spec - why is this better than what nova currently has?21:47
vilobhmm11thingee : since we are talking about poc i assume the idea sounds fair to most of the members21:47
*** sigmavirus24 is now known as sigmavirus24_awa21:47
vilobhmm11just to confirm21:47
jrollbut I don't care about this too much as ironic doesn't have quotas today21:47
jrollpoc would be a good start, though, too21:48
bknudsondoes ironic have a need for quotas?21:48
nikhiljroll: it's more to do about getting quotas right and then implenting them right across openstack21:48
jrollbknudson: it may eventually, but I don't see anyone asking for it today21:48
nikhiljroll: I think that was the most widely given opinion on the ML thread21:48
diablo_rojoCinder is just starting to have working quota support.21:48
vilobhmm11nikhil : I agree21:48
jrollnikhil: yep, I want to see why this is "right" :)21:48
nikhiljroll: cool, so I think the point is take it from a project who has implemented and learnt from it21:49
jrollbecause it sounds like what nova does already, which I know is not right with my ops hat on21:49
thingeediablo_rojo: you mean for nested? it's had quotas for a while.21:49
nikhilright now the example given to me was cinder21:49
diablo_rojothingee: Ha ha yes. Nested quotas21:49
nikhiland we've 2 cinder folks contributing to the WG21:49
diablo_rojothingee: My bad.21:49
diablo_rojonikhil: Who has been helping out?21:49
mc_nairyea, but it's still race-ee21:49
thingeediablo_rojo: DuncanT21:49
nikhildiablo_rojo: DuncanT and mc_nair21:49
vilobhmm11nikhil : the problems mentioned in the spec are not particular to cinder they apply to nova as well21:50
nikhilplus vilobhmm11 himself21:50
diablo_rojothingee: Got it. I assumed mc_nair. Wondered who the other was.21:50
vilobhmm11or any other project to say21:50
DuncanTHi21:50
nikhilvilobhmm11: right, I was just saying which project is this thing most ahead. nested is only in cinder, iirc21:50
thingeeDuncanT: go back to sleep21:50
vilobhmm11nikhil : sure21:50
mc_nairvilobhmm11: right the problems aren't specific but I think the point is they'd like to see the problem solved one place before making it common21:51
DuncanTthingee: ok21:51
vilobhmm11mc_nair :so thats the question; which project is willing to try the POC ?21:51
thingeeok I'll defer to the wg discussing this. maybe on the ML21:51
nikhilopenstack-dev/sandbox (pfff) :/21:51
thingeesound good?21:52
nikhilyeah21:52
jrollvilobhmm11: the WG should be doing the POC, in whichever project they feel comfortable doing it in21:52
jrollimo21:52
mc_nairI'm not in a place to make that call but I will help with Cinder support. I don't think people would complain if we removed the races from the quota stuff21:52
DuncanTYou could put a WIP patch up for cinder - probably won't get merged any time soon, but it gives something to test against21:52
thingeeand something for mriedem to look at21:52
thingeenikhil: anything else?21:53
nikhilyes, I can assure to provide some reviews if WIP exists in GLance but can't commit to this being approved21:53
diablo_rojoDuncanT: +121:53
nikhilthingee: no, thank you.21:53
vilobhmm11thingee : yes as we are still in design phase; if the problem statement and the thing this library plans to solve seeming something useful - it would be nice for community members to give there feedback so that we can have a solid foundation till summit and then decide21:53
thingee#action nikhil and vilobhmm11 and folks to get a poc going21:53
thingeevilobhmm11: I think you're in shape for the summit discussion on this. of course that's up for the TC to decide21:53
vilobhmm11thingee : ok21:54
vilobhmm11thanks!21:54
thingeethanks21:54
thingee#topic Clarify Specifications21:54
*** openstack changes topic to "Clarify Specifications (Meeting topic: cross-project)"21:54
thingee#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/090156.html mailing list post21:54
thingee#link https://review.openstack.org/#/c/295940/ review21:54
thingeealright so I posted this and didn't get too much feedback aside from dhellmann21:54
jrollI don't see dhellmann on that review at all21:55
thingeejroll: errr thanks21:55
jrollthingee: you mean https://review.openstack.org/#/c/296571/ ?21:55
thingee#link https://review.openstack.org/#/c/296571/ spec/guideline separation21:55
thingeejroll: thanks again :)21:56
jrollheh21:56
*** gordc has left #openstack-meeting-cp21:56
cdentthingee: I meant to and then easter showed up, but it's in my queue. When I glanced at it before seemed sane21:56
thingeethis is going back to our last cross-project meeting of there being confusion in a guideline being given for rolling upgrades21:56
thingeesdague: dansmith ^21:57
jrollI like what andreas said about explaining what each are21:57
jrollotherwise seems fine21:57
thingeewhat about dhellmann's comment of it still being under specs.openstack.org?21:57
thingeeit's gotta live somewhere... I think it might be fine21:57
jrollI'm unopinionated there, personally, it seems fine21:57
thingeeto resolve with what the product working group wants, kencjohnston, I think it would be good for a follow-up on someone giving the guideline information based on the use cases that already exist in today's progress21:58
Rocky_gWell, if it's a guideline, couldn't it live there?21:58
thingeeas dansmith requested21:58
thingeeRocky_g: right it's about clarifying guidelines do live here21:59
thingeetoo21:59
jrollspecs.o.o/guidelines seems close enough21:59
thingeewhich we already have some in there.21:59
Rocky_gReally, in many ways, mos of the guideline type stuff is really OpenStack-wide devrefs21:59
jrollor whatever, specs.o.o/openstack/openstack-specs/guidelines21:59
thingee1 min21:59
thingee#action thingee to update spec/guideline separation with descriptions of each21:59
thingee#action thingee to send email to list of new PTLs making sure current cp-spec liaisons are accurate22:00
thingeethanks all!22:00
*** mriedem has quit IRC22:00
thingee#endmeeting22:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
openstackMeeting ended Tue Mar 29 22:00:38 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cross_project/2016/cross_project.2016-03-29-21.02.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cross_project/2016/cross_project.2016-03-29-21.02.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/cross_project/2016/cross_project.2016-03-29-21.02.log.html22:00
jrollthanks thingee :)22:00
elmikothanks thingee22:00
diablo_rojoThank you :)22:00
*** ninag has joined #openstack-meeting-cp22:00
*** hongbin_ has left #openstack-meeting-cp22:00
*** xarses has left #openstack-meeting-cp22:00
*** diablo_rojo has quit IRC22:03
EmilienMsdake_: big +1 on https://review.openstack.org/29827822:03
sdake_EmilienM thanks ;)22:04
EmilienMsdake_: we managed to release Mitaka this week, but it wasn't easy for the reasons you say22:05
sdake_we can tag on schedule but it will be broken22:05
*** cdent has quit IRC22:05
EmilienMsdake_: I also replied to your thread about kolla plugins, let me know your thoughts!22:06
sdake_will do - in midst of channel rename on kolla atm22:07
sdake_dealing with that fun :)22:07
*** markvoelker has joined #openstack-meeting-cp22:13
*** annegentle has quit IRC22:15
*** annegentle has joined #openstack-meeting-cp22:16
*** markvoelker has quit IRC22:20
*** markvoelker has joined #openstack-meeting-cp22:21
*** markvoelker_ has joined #openstack-meeting-cp22:22
*** markvoelker has quit IRC22:26
*** sdake has joined #openstack-meeting-cp22:26
*** sdake_ has quit IRC22:28
*** annegentle has quit IRC22:35
*** ninag has quit IRC22:38
*** markvoelker_ has quit IRC22:39
*** ninag has joined #openstack-meeting-cp22:41
*** annegentle has joined #openstack-meeting-cp22:44
*** annegentle has quit IRC22:45
EmilienModyssey4me: hijacking https://review.openstack.org/297285 to ask a question :-)22:47
*** sdague has quit IRC22:53
*** vilobhmm11 has quit IRC23:13
*** angdraug has quit IRC23:34
*** sdake has quit IRC23:43
*** sdake has joined #openstack-meeting-cp23:44
*** sdake has quit IRC23:44
*** sdake has joined #openstack-meeting-cp23:44

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