Tuesday, 2019-01-29

*** tetsuro has joined #openstack-meeting-alt00:15
*** macza has quit IRC00:20
*** sdake has quit IRC00:23
*** sdake has joined #openstack-meeting-alt00:24
*** hongbin has joined #openstack-meeting-alt00:27
*** jcoufal has quit IRC00:36
*** edleafe- has joined #openstack-meeting-alt00:39
*** edleafe has quit IRC00:39
*** edleafe- is now known as edleafe00:39
*** gyee has quit IRC00:51
*** masahito has joined #openstack-meeting-alt01:01
*** masahito has quit IRC01:05
*** yamamoto has joined #openstack-meeting-alt01:09
*** markvoelker has joined #openstack-meeting-alt01:10
*** macza has joined #openstack-meeting-alt01:10
*** markvoelker has quit IRC01:15
*** macza has quit IRC01:15
*** hongbin has quit IRC01:18
*** hongbin has joined #openstack-meeting-alt01:20
*** sdake has quit IRC01:28
*** bhavikdbavishi has joined #openstack-meeting-alt01:33
*** lbragstad has quit IRC01:35
*** TxGirlGeek has quit IRC01:40
*** bhavikdbavishi has quit IRC01:51
*** bhavikdbavishi has joined #openstack-meeting-alt01:51
*** yamamoto has quit IRC02:03
*** sdake has joined #openstack-meeting-alt02:31
*** sdake has quit IRC02:37
*** bhavikdbavishi has quit IRC02:37
*** whoami-rajat has joined #openstack-meeting-alt02:37
*** sdake has joined #openstack-meeting-alt02:38
*** yamamoto has joined #openstack-meeting-alt02:41
*** yamamoto has quit IRC02:46
*** armstrong has quit IRC02:57
*** sdake has quit IRC02:58
*** sdake has joined #openstack-meeting-alt02:59
*** iyamahat has quit IRC03:09
*** apetrich has quit IRC03:15
*** yamamoto has joined #openstack-meeting-alt03:25
*** sdake has quit IRC03:26
*** yamahata has quit IRC03:27
*** sdake has joined #openstack-meeting-alt03:29
*** yamamoto has quit IRC03:34
*** alex_xu has quit IRC03:40
*** sdake has quit IRC03:42
*** lbragstad has joined #openstack-meeting-alt03:47
*** bhavikdbavishi has joined #openstack-meeting-alt03:52
*** macza has joined #openstack-meeting-alt04:05
*** yamahata has joined #openstack-meeting-alt04:05
*** yamamoto has joined #openstack-meeting-alt04:06
*** igordc has quit IRC04:06
*** macza_ has joined #openstack-meeting-alt04:07
*** macza has quit IRC04:09
*** macza_ has quit IRC04:11
*** diablo_rojo has quit IRC04:12
*** macza has joined #openstack-meeting-alt04:21
*** macza has quit IRC04:25
*** bhavikdbavishi has quit IRC04:38
*** bhavikdbavishi has joined #openstack-meeting-alt04:39
*** sdake has joined #openstack-meeting-alt04:50
*** bhavikdbavishi has quit IRC05:27
*** jtomasek has joined #openstack-meeting-alt05:36
*** sdake has quit IRC05:41
*** radeks_ has joined #openstack-meeting-alt05:44
*** sdake has joined #openstack-meeting-alt05:50
*** bhavikdbavishi has joined #openstack-meeting-alt05:53
*** sridharg has joined #openstack-meeting-alt05:59
*** jtomasek has quit IRC06:02
*** markvoelker has joined #openstack-meeting-alt06:20
*** liuyulong has joined #openstack-meeting-alt06:20
*** hongbin has quit IRC06:21
*** igordc has joined #openstack-meeting-alt06:23
*** markvoelker has quit IRC06:24
*** strigazi has quit IRC06:42
*** strigazi has joined #openstack-meeting-alt06:43
*** ccamacho has quit IRC06:44
*** radeks_ has quit IRC07:01
*** ccamacho has joined #openstack-meeting-alt07:20
*** yamamoto has quit IRC07:28
*** igordc has quit IRC07:28
*** liuyulong has quit IRC07:29
*** yamamoto has joined #openstack-meeting-alt07:32
*** slaweq has joined #openstack-meeting-alt07:43
*** radeks_ has joined #openstack-meeting-alt07:49
*** e0ne has joined #openstack-meeting-alt07:59
*** iyamahat has joined #openstack-meeting-alt08:06
*** apetrich has joined #openstack-meeting-alt08:09
*** sdake has quit IRC08:11
*** kopecmartin|off is now known as kopecmartin08:19
*** markvoelker has joined #openstack-meeting-alt08:20
*** ttsiouts has joined #openstack-meeting-alt08:27
*** bnemec has joined #openstack-meeting-alt08:29
*** yamamoto has quit IRC08:35
*** yamamoto has joined #openstack-meeting-alt08:36
*** janki has joined #openstack-meeting-alt08:36
*** ttsiouts has quit IRC08:39
*** ttsiouts has joined #openstack-meeting-alt08:40
*** ttsiouts has quit IRC08:44
*** priteau has joined #openstack-meeting-alt08:54
*** markvoelker has quit IRC08:54
priteau#startmeeting blazar09:00
openstackMeeting started Tue Jan 29 09:00:10 2019 UTC and is due to finish in 60 minutes.  The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: blazar)"09:00
openstackThe meeting name has been set to 'blazar'09:00
priteau#topic Roll call09:00
*** openstack changes topic to "Roll call (Meeting topic: blazar)"09:00
priteauHello09:00
tetsuroHi09:00
priteauHi tetsuro09:01
*** masahito has joined #openstack-meeting-alt09:01
masahitoo/09:01
priteauHi masahito09:01
priteauShort agenda for today: stein-3 milestone and AOB09:02
*** ttsiouts has joined #openstack-meeting-alt09:02
priteau#topic stein-3 milestone09:03
*** openstack changes topic to "stein-3 milestone (Meeting topic: blazar)"09:03
priteauThe first blueprint on stein-3 is "API to query resource allocation"09:04
masahitoThanks for your reviewing :-)09:04
priteauMany patches have been merged, thanks Masahito for your code and Tetsuro for final review09:04
priteauWe still have to figure out why API tests are failing: https://review.openstack.org/#/c/586859/09:05
priteau#action Fix API tests in https://review.openstack.org/#/c/586859/09:05
masahitoyes. I'll work on the patch next.09:06
priteauThanks masahito!09:06
*** jtomasek has joined #openstack-meeting-alt09:06
priteauWe also have good progress on floating IP reservation, good job masahito09:07
masahitoThe main codes are already on the review board.09:07
priteauI have started reviewing. There are lots of patches! :-)09:08
masahitoThe rest of things to do are 1. add some LOG message, 2. check response codes, 3. write its release note.09:08
masahitopriteau: Thanks. Overall, the code is similar to your network reservation's code.09:09
masahitoI added some minor changes to make easy to add another plugin in the future.09:10
priteauGreat, I hope it was useful. I'll aim to rewrite my network plugin using your approach and submit on Gerrit in the coming weeks.09:11
masahitoI didn't change the db_api series because it makes another big changes.09:12
masahitoIMO, it's good for us to consider refactoring for the api in another cycle.09:13
priteauYou're right. I needed to have extra capabilities for networks, so it resulted in a lot of copy/paste. I am sure we can implement extra capabilities in a more abstract approach, so it can be applied to any kind of resource without code duplication.09:14
priteautetsuro: I am afraid I haven't had time yet to look at your placement patches, I am hoping to do this soon.09:16
*** sridharg has quit IRC09:16
tetsuronp09:16
priteauThanks for pushing a fix for the host creation bug that was reported09:17
tetsuroYes, that's priority than the affinity support patches.09:17
tetsuroThank you for this excellent catch. I've missed it.09:18
tetsurohttps://review.openstack.org/#/q/topic:bug/1813252+(status:open+OR+status:merged)09:18
tetsuroAh no not this one, sorry.09:19
priteauI checked the test output for https://review.openstack.org/#/c/633408/, it failed on another function than the one you changed09:19
tetsuroright.09:19
priteauI requested a recheck, but if it fails again it means there must be some side effect09:19
tetsurookay09:20
priteauWe can always revert to the sleep() cal09:21
priteaucall09:21
priteauThere are some easy patches we can merge as well09:22
priteauhttps://review.openstack.org/#/c/625607/09:22
priteauhttps://review.openstack.org/#/c/626669/109:23
priteauhttps://review.openstack.org/#/c/626731/09:23
priteauhttps://review.openstack.org/#/c/624367/09:23
*** yamahata has quit IRC09:24
priteauIt will make the queue a bit smaller09:24
priteautetsuro: If you have an existing +1 you can change it to +209:25
tetsuromasahito has +W`ed now I guess09:26
masahitoyup.09:26
masahitoI thought tetsuro's +1 is +2 because of no comment.09:26
tetsuronp09:26
priteauThanks!09:27
priteauAlso https://review.openstack.org/#/c/627664/ is quick to review09:27
*** panda is now known as panda|numb09:28
*** sridharg has joined #openstack-meeting-alt09:28
priteauAnother hacking one, a bit bigger: https://review.openstack.org/#/c/628469/09:29
priteauAnd another easy one: https://review.openstack.org/#/c/624348/309:31
priteauThanks for the reviews, it makes it easier to see what's left to merge09:32
priteauAnything else to discuss about stein-3?09:33
priteau#topic AOB09:34
*** openstack changes topic to "AOB (Meeting topic: blazar)"09:34
priteauAny other update?09:34
priteauIt's confirmed that I *won't* be in Denver for the Summit/PTG as I have a conflict due to a family event09:36
*** derekh has joined #openstack-meeting-alt09:36
priteauI hope we can still have a good project update thanks to tetsuro :-)09:37
tetsuroAye09:37
priteauAnything else? If not we can end early today.09:40
tetsuroCould you get me in https://launchpad.net/~blazar-core/+members ? Since it is also a bug supervisor list, I realized I can't update the bug importance in launchpad.09:40
masahitoNothing from my side.09:40
priteautetsuro: Sure. I forgot it wasn't automatically synchronized09:41
tetsurothanks.09:42
priteauI can't do it right now as I am not an admin, I will request admin rights.09:42
priteaubauzas: Good morning. Could you please give me admin rights in https://launchpad.net/~blazar-core/+members? Thanks!09:43
priteauWe should look at moving to Storyboard ;-)09:43
priteautetsuro: I will let you know when it's done09:44
tetsuroThanks!09:45
priteauIf there's nothing else, have a good week!09:45
priteau#endmeeting09:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:45
openstackMeeting ended Tue Jan 29 09:45:44 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/blazar/2019/blazar.2019-01-29-09.00.html09:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/blazar/2019/blazar.2019-01-29-09.00.txt09:45
openstackLog:            http://eavesdrop.openstack.org/meetings/blazar/2019/blazar.2019-01-29-09.00.log.html09:45
masahitobye09:46
tetsurohave a good week09:47
*** markvoelker has joined #openstack-meeting-alt09:51
*** carlos_silva has joined #openstack-meeting-alt09:53
*** ttsiouts has quit IRC10:02
*** ttsiouts has joined #openstack-meeting-alt10:02
*** ttsiouts has quit IRC10:07
*** masahito has quit IRC10:21
*** markvoelker has quit IRC10:24
*** rf0lc0 has joined #openstack-meeting-alt10:27
*** rfolco has quit IRC10:27
*** ttsiouts has joined #openstack-meeting-alt10:35
*** bhavikdbavishi has quit IRC10:45
*** masahito has joined #openstack-meeting-alt10:52
*** rf0lc0 has quit IRC10:53
*** masahito has quit IRC10:57
*** tssurya has joined #openstack-meeting-alt11:00
*** janki has quit IRC11:02
*** rfolco has joined #openstack-meeting-alt11:03
*** erlon has joined #openstack-meeting-alt11:12
*** yamamoto has quit IRC11:14
*** markvoelker has joined #openstack-meeting-alt11:21
*** masahito has joined #openstack-meeting-alt11:31
*** masahito has quit IRC11:36
*** bhavikdbavishi has joined #openstack-meeting-alt11:39
*** ttsiouts has quit IRC11:40
*** ttsiouts has joined #openstack-meeting-alt11:40
*** ttsiouts has quit IRC11:44
*** markvoelker has quit IRC11:53
*** yamamoto has joined #openstack-meeting-alt11:54
*** yamamoto has quit IRC12:04
*** ttsiouts has joined #openstack-meeting-alt12:11
*** liuyulong has joined #openstack-meeting-alt12:12
*** ttsiouts has quit IRC12:16
*** ttsiouts has joined #openstack-meeting-alt12:18
*** iyamahat has quit IRC12:18
*** yamamoto has joined #openstack-meeting-alt12:23
*** tetsuro has quit IRC12:28
*** markvoelker has joined #openstack-meeting-alt12:50
*** apetrich has quit IRC12:52
*** apetrich has joined #openstack-meeting-alt12:55
*** priteau has quit IRC13:04
*** priteau has joined #openstack-meeting-alt13:04
*** priteau has quit IRC13:12
*** e0ne has quit IRC13:13
*** markvoelker has quit IRC13:20
*** e0ne has joined #openstack-meeting-alt13:29
*** ttsiouts has quit IRC13:32
*** masahito has joined #openstack-meeting-alt13:32
*** ttsiouts has joined #openstack-meeting-alt13:33
*** ttsiouts has quit IRC13:37
*** masahito has quit IRC13:37
*** jcoufal has joined #openstack-meeting-alt13:44
*** bhavikdbavishi has quit IRC13:48
*** ttsiouts has joined #openstack-meeting-alt13:50
*** panda|numb is now known as panda13:56
*** yamamoto has quit IRC14:00
*** jcoufal has quit IRC14:07
*** efried has quit IRC14:15
*** efried has joined #openstack-meeting-alt14:15
*** jcoufal has joined #openstack-meeting-alt14:16
*** efried has quit IRC14:19
*** efried has joined #openstack-meeting-alt14:19
*** yamamoto has joined #openstack-meeting-alt14:23
*** SimAloo has joined #openstack-meeting-alt14:37
*** SimAloo has quit IRC14:37
*** dave-mccowan has joined #openstack-meeting-alt14:38
*** SimAloo has joined #openstack-meeting-alt14:40
*** dave-mccowan has quit IRC14:45
*** sdake has joined #openstack-meeting-alt14:50
*** bhavikdbavishi has joined #openstack-meeting-alt14:50
*** sdake has quit IRC14:51
*** e0ne has quit IRC14:51
*** sdake has joined #openstack-meeting-alt14:53
*** e0ne has joined #openstack-meeting-alt14:54
*** jrbalderrama has joined #openstack-meeting-alt15:00
*** hongbin has joined #openstack-meeting-alt15:13
*** yamamoto has quit IRC15:15
*** yamamoto has joined #openstack-meeting-alt15:16
*** yamamoto has quit IRC15:16
*** yamamoto has joined #openstack-meeting-alt15:17
*** ttsiouts has quit IRC15:23
*** yamamoto has quit IRC15:23
*** ttsiouts has joined #openstack-meeting-alt15:23
*** ttsiouts has quit IRC15:28
*** wxy| has joined #openstack-meeting-alt15:28
*** sdake has quit IRC15:32
*** masahito has joined #openstack-meeting-alt15:34
*** sdake has joined #openstack-meeting-alt15:35
*** masahito has quit IRC15:38
*** ttsiouts has joined #openstack-meeting-alt15:42
*** bhavikdbavishi has quit IRC15:43
*** ccamacho has quit IRC15:45
*** ccamacho has joined #openstack-meeting-alt15:46
*** liuyulong has quit IRC15:47
*** bhavikdbavishi has joined #openstack-meeting-alt15:55
lbragstad#startmeeting keystone16:00
openstackMeeting started Tue Jan 29 16:00:01 2019 UTC and is due to finish in 60 minutes.  The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: keystone)"16:00
openstackThe meeting name has been set to 'keystone'16:00
lbragstad#link https://etherpad.openstack.org/p/keystone-weekly-meeting16:00
lbragstadagenda ^16:00
lbragstado/16:00
*** jrbalderrama has quit IRC16:00
knikollao/16:00
wxy|o/16:00
cmurphyo/ dual meetings again16:00
* kmalloc drinks coffee.16:00
* knikolla finished coffee already but doesn't want to be hypercaffeinated. 16:01
lbragstadlooks like we have some good topics on the agenda - so let's get started16:01
lbragstad#topic previous action items16:01
*** openstack changes topic to "previous action items (Meeting topic: keystone)"16:01
vishakhao/16:01
lbragstadlast week we recapped the notes cmurphy put together for keystone's version of the technical vision statement from the TC and how we fit into that16:02
lbragstad#link https://etherpad.openstack.org/p/keystone-technical-vision-notes16:02
lbragstadi'm curious if anyone wants to take a stab at proposing whats in the etherpad for review to our contributor guide16:02
lbragstadwe can massage the wording and iterate using gerrit16:03
kmallocwhere do you see this documentation going?16:03
kmallocwithin our doc tree that is16:03
lbragstadhttps://docs.openstack.org/keystone/latest/contributor/index.html16:03
kmallocstraight on the index page then.16:03
lbragstadimo - it fits well with the contributor guide16:04
kmalloc[link that is]16:04
kmallocok16:04
lbragstadbut if folks have other suggestions as to where this should live, i'm curious to hear them16:04
kmalloci wasn't sure if there was a standard place or if it was per-project16:04
kmalloci was kindof hoping the TC had a direct/standard recommended.16:04
kmallocso fokls don't have to guess whereabouts for each service16:05
kmalloccontributor guide makes sense.16:05
lbragstadthe unofficial recommendation was to put it into the contributor guide16:05
lbragstadof each project16:05
lbragstadif there was additional detail or differences the projects had in vision with what the TC had outlined16:05
kmallocso, i do want to point out that the data in that etherpad is extremely rough. it probably has to be someone familiar/worked with keystone for a time to convert it into coherant words.16:06
cmurphythey are mostly my notes so I can put this on my backlog16:06
*** ayoung has joined #openstack-meeting-alt16:06
kmalloceven as a core, i am hesitant to volunteer to turn that into something polished -- it is very rough. if it can be made slightly less stream of consciousness i'd be happy to convert it to usable/polished words.16:07
lbragstadsounds good16:07
cmurphyyeah sorry this just started out as my random notes as i was reading16:08
kmallocno problem. I'm happy to help, it's very much as you said some random notes atm.16:08
lbragstadwhich i threw into the spot light immediately ;)16:08
ayoungcmurphy, post if for review on Gerrit and you know we'll all have lines to modify/contrib16:08
cmurphyayoung: will do16:09
* kmalloc votes lbragstad takes a pass at it... you know... being the person who put a spotlight on it :P16:09
lbragstadyeah - that's fair16:09
kmalloccmurphy: ^ trying to toss lbragstad under the doc bus for you :P16:09
cmurphylol16:09
lbragstadfwiw - if we put this in review i can tag-team it16:09
cmurphy++16:10
kmallocyeah. and i can def. help as well.16:10
cmurphyis there a timeline on this?16:10
lbragstadcool16:10
kmalloccmurphy: sometime before the U release (/s)16:10
lbragstadnot really - but this is the furthest we come to ever having a technical vision statement for the project16:10
lbragstadi just don't want it to get lost in the shuffle16:10
kmalloci'm guessing we should aim for sometime around when stein cuts RC.16:10
kmallocat the latest16:10
cmurphyI'll aim for having something rough up a few weeks before ptg16:10
lbragstadi like that idea16:11
kmallocit will inform some choices for train and beyond.16:11
lbragstadi can see this being useful at the forum/ptg16:11
lbragstadsounds like we have a plan16:12
lbragstadmoving on16:12
lbragstadthanks cmurphy16:12
lbragstad#topic Alembic instead of sqlalchemy-migrate16:12
*** openstack changes topic to "Alembic instead of sqlalchemy-migrate (Meeting topic: keystone)"16:12
lbragstadvishakha o/16:12
vishakhaI wanted to grab the attention of keystone team towards these migratons16:13
vishakhaSince the maintainer of sql aclchemy is deprecating this and wanted to move towards alembic16:13
kmallocthe only reason we have not made the move is bandwidth.16:13
kmallocit's been on our wishlist for a while.16:14
kmallocI support and will review anyone's code to make the conversion.16:14
cmurphycould someone tldr the reason to migrate for me?16:14
kmalloccmurphy: sql-alchemy-migrate is effectively a dead project16:14
kmallocit's been on life-support for a while.16:15
vishakhaYea even glance took two cycles to migrate16:15
cmurphygot it thanks16:15
vishakhaThere were two people involved in this16:15
kmallocmike bayer (zzzeek) maintains alembic directly for SQL-A as a first-party support. -- it's also generally better, but it takes some work to get moved over to it, and a slightly different workflow to make migrations.16:16
kmalloc:)16:16
cmurphymight be a good idea to revive our rolling upgrades testing before starting on a refactor16:16
lbragstad++16:16
kmallocas i recall, alembic should be mostly drop in.16:16
lbragstadwe need to revisit all that stuff anyway16:17
lbragstadthat stuff == how we approach upgrades and migrations16:17
kmallocs/drop in/fully capable of running the old migrations with some added tooling.16:17
kmallocwe need to re-work the rolling upgrades and very clearly line out the expected order and at least test that order [even if it ins't multi-node]16:18
ayoungSo....we would need to make a cut, and say all migrations from point X on forward are Alembic16:18
ayoungwe've discussed it before.16:18
kmallocayoung: that would be the plan, and that would come with a conversion to alembic in our tooling16:18
kmallocthe tooling cutover would be the point in which migrations would cut over16:18
ayoungCould we do a release where we say "only additive changes to SQL?"16:18
kmallocwe already did that16:19
ayounglike, no columns dropped etc16:19
kmalloclike.... ages ago16:19
ayounga release, not a phase16:19
kmallocit's the expand/migrate/contract bits16:19
ayoungwe are going to do expand contract16:19
kmalloci'd say no not a release.16:19
kmallocthere are reasons to have a contract phase.16:19
kmallocso not explicitly "only expand/migrate" release. but it might be there are no logical contracts for the release16:20
ayoungso  what if we did:16:20
ayoungfor each p[hase, first sqla, then alembic16:20
ayoungnah...16:20
ayoungI'm trying to think how not to logjam people on the cut over of mechanis16:20
ayoungm16:20
kmallocdb_sync will handle the change for users/deployers/operators16:21
kmallocjust like today16:21
kmallocdevelopers will need to make alembic migrations (minorly different)16:21
ayoungok...what if....16:21
ayounglets ssume we started in the middle of a release.  A bunch of SQL A migrations are already approved16:22
kmallocreally, the hardest part of alembic is knowing that by default the schema is not numbered, it has a uuid.16:22
ayoungbut there is an ordering, right?16:22
kmallocyes.16:22
ayoungits just like git, a hash of the previous...16:22
kmallocsortof?16:22
ayoungso...we think of it like a stack16:22
ayoungwe state that for all migrations, they are SQL A first, then Alembic16:23
kmallocyou're overthinking it :P16:23
kmallocdb_sync will be tooled to run them both.16:23
ayoungDo we just cut over at a release boundary?16:23
ayoungOh, I ghet that16:23
kmallocand we just cut over when the code is ready16:23
kmallocit should not be a ton of code.16:24
ayoungbut what about migrations in flight?16:24
kmallocif they are approved they land16:24
ayoungdo we let people submit them in both?16:24
kmallocif they are not, they get rebased.16:24
kmallocand need to get minor reworking...16:24
kmallocwe have almost no (any?) migrations in flight right now.16:24
kmallocstandard land-code-gate-process.16:24
kmallocwe could wait until feature-freeze to land alembic swap over16:25
kmallocbut really, it should be minimally invasive and no different than the other race-to-rebase that happens in the gate.16:25
kmallocvishakha: tl;dr - we should move to alembic :)16:26
ayoungI like the idea of doing it at feature freeze16:26
vishakhayeah :)16:26
kmallocwe can discuss timing outside of the meeting.16:26
lbragstadwe could also try and get it done first thing in the cycle, too16:26
vishakhasure. Thanks.16:26
kmalloclbragstad: i'd rather do it at the end of a cycle16:26
ayounglbragstad, that is why at feature freeze16:26
kmallocin case it bleeds over, then it can land first in T.16:26
ayoungits prepped and ready to go with all the previous changes16:26
kmallocjust hedging bets.16:27
lbragstadsounds like we still need to work out some technical details16:27
kmallocfor this one, i think code talks.16:27
ayoungyep.  But I'm in favor of the cut over16:27
kmallocwe should get a review up for the cut over16:27
kmallocit might just work(tm)16:27
lbragstadok - i guess we'll discuss technical details in the channel16:28
lbragstadif that's cool with everyone? but it sounds like we have consensus on the need to move to alembic16:28
lbragstaddoes anyone object?16:28
cmurphythanks for bringing it up vishakha16:28
knikolla++16:29
vishakhasure we can discuss on channel16:29
lbragstadthanks vishakha16:29
lbragstad#topic Next outreachy round16:29
*** openstack changes topic to "Next outreachy round (Meeting topic: keystone)"16:29
lbragstadcmurphy o/16:29
cmurphythis is just a short announcement16:29
cmurphythe outreachy people notified me that the project submissions are open for the next round16:30
cmurphy#link https://www.outreachy.org/communities/cfp/openstack/16:30
cmurphythey recommend submitting sooner rather than later because interns are going to start applying soon16:30
lbragstadsoon as in days? or weeks?16:31
*** e0ne has quit IRC16:31
cmurphyfebruary i think16:31
lbragstaddo we have anything we know we want to submit?16:32
cmurphyI don't plan on submitting a project myself or being a lead mentor but I can answer questions about the process if anyone is interested and I can be a comentor16:32
lbragstadack16:33
cmurphyI don't have any projects in mind personally, but wanted to raise it so that people can brainstorm16:33
lbragstadsounds good16:33
lbragstadthanks cmurphy16:33
cmurphynp16:33
lbragstad#topic x509 shtuff16:34
*** openstack changes topic to "x509 shtuff (Meeting topic: keystone)"16:34
lbragstadso - this was a fun puzzle16:34
lbragstad#link http://lists.openstack.org/pipermail/openstack-discuss/2019-January/002085.html16:34
lbragstadi attempted to summarize stuff in that post ^16:34
lbragstadi'm curious if folks have thoughts, or see themselves helping out with the refactor16:35
lbragstadsounds like penick has some resources that can help16:35
cmurphygyee is in a meeting right now but I think he was interested in digging in16:35
lbragstad++ that'd be good, because i'm certain he has context as the author that the rest of us don't16:36
cmurphyI'll try to look into it too16:37
lbragstadall in all - i think if we got this working as designed, there are a lot of things we could do with it that would be really cool16:37
lbragstadit would be easier to test federation in the gate for example16:37
lbragstadwhich would be a huge win16:37
vishakhaI will also look for it16:37
lbragstadwe would also have a path forward for fixing the bearer token problem we have in openstack16:38
lbragstadwhich would be pretty neat16:38
lbragstaddoes anyone have questions about that summary or the bugs we opened for x509/tokenless authentication last week?16:39
lbragstadwell if you do or something comes up, don't hesitate to ask16:42
lbragstadthat's all i ha16:42
lbragstadhad*16:42
*** TxGirlGeek has joined #openstack-meeting-alt16:42
lbragstad#topic open discussion16:42
*** openstack changes topic to "open discussion (Meeting topic: keystone)"16:42
lbragstadfloor is open16:42
lbragstaddoes anyone have comments, questions, or concerns they'd like to raise?16:42
* kmalloc dances on the open floor.16:42
lbragstadfwiw - i did go through a bunch of bug backlog yesterday16:43
lbragstadand i attempted to match up when bugs were fixed to the milestone they were fixed in16:43
lbragstadfor context16:44
lbragstadwe fixed 70 bugs in pike, 38 bugs in queens, 60 bugs in rocky, and we've fixed 36 so far in stein16:44
lbragstad(not that numbers are a great indicator)16:44
cmurphyI ran into a slight stumbling block in the app creds whitelist implementation, the spec says that ksm will check the service id but afaict ksm actually doesn't know its own identity, it can't know the service ID or even the service type of the service it's running in16:45
cmurphyfor now i have a new parameter in [keystone_authtoken] that gives the service type16:45
kmallocyeah that is a gap we've needed to fix for a LONG time.16:45
*** sdake has quit IRC16:46
kmallocyep, config value, possibly something that can be set by the service with a config_default thing.16:46
cmurphymmk16:46
kmalloci also recommend not using ID16:47
kmallocuse a human readable string, if we need to fix the spec we can16:47
kmallocuuids in config suck :P16:47
cmurphyyeah my wip patch has the human readable service type16:47
kmalloc++16:47
kmallocperfect :)16:47
cmurphywe could integrate os_service_types to let it use either service name or service type but eh16:48
kmallocfuture looking stuff16:49
kmallocstart easy, expand.16:49
cmurphy++16:49
lbragstadoh - i forgot to ask earlier16:50
lbragstaddoes anyone have reviews that need eyes?16:50
lbragstadi appreciate people taking a look at - https://review.openstack.org/#/q/status:open+project:openstack/keystone+branch:master+topic:implement-default-roles16:52
lbragstadstill a few patches up there if folks are looking for reviews16:53
cmurphyoh another announcement, one of our interns got their first patches merged and now the keystone devstack plugin supports centos :D16:53
knikolla\o/16:53
lbragstadnice!16:53
lbragstadalright - if there isn't anything else, looks like we can get a few minutes back16:55
lbragstadoffice hours is starting shortly16:55
lbragstadi appreciate y'all taking the time to be here16:55
lbragstad#endmeeting16:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:56
openstackMeeting ended Tue Jan 29 16:56:02 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-01-29-16.00.html16:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-01-29-16.00.txt16:56
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-01-29-16.00.log.html16:56
*** bhavikdbavishi has quit IRC16:58
*** wxy| has quit IRC16:59
*** gyee has joined #openstack-meeting-alt17:03
*** ttsiouts has quit IRC17:06
*** ttsiouts has joined #openstack-meeting-alt17:06
*** macza has joined #openstack-meeting-alt17:07
*** tssurya has quit IRC17:09
*** ttsiouts has quit IRC17:10
*** hongbin has quit IRC17:14
*** bhavikdbavishi has joined #openstack-meeting-alt17:16
*** sdake has joined #openstack-meeting-alt17:17
*** sdake has quit IRC17:18
*** iyamahat has joined #openstack-meeting-alt17:18
*** ccamacho has quit IRC17:18
*** yamamoto has joined #openstack-meeting-alt17:21
*** kopecmartin is now known as kopecmartin|off17:24
*** yamamoto has quit IRC17:27
*** bnemec has quit IRC17:27
*** masahito has joined #openstack-meeting-alt17:35
*** masahito has quit IRC17:40
*** sridharg has quit IRC17:44
*** sdake has joined #openstack-meeting-alt17:45
*** e0ne has joined #openstack-meeting-alt17:46
*** derekh has quit IRC18:01
*** diablo_rojo has joined #openstack-meeting-alt18:01
*** igordc has joined #openstack-meeting-alt18:03
*** jtomasek has quit IRC18:10
*** sdake has quit IRC18:10
*** iyamahat has quit IRC18:19
*** bhavikdbavishi has quit IRC18:20
*** iyamahat has joined #openstack-meeting-alt18:34
*** diablo_rojo has quit IRC18:35
*** sdake has joined #openstack-meeting-alt18:38
*** yamahata has joined #openstack-meeting-alt18:52
*** e0ne has quit IRC18:53
*** carlos_silva has quit IRC19:03
*** yamamoto has joined #openstack-meeting-alt19:04
*** whoami-rajat has quit IRC19:07
*** e0ne has joined #openstack-meeting-alt19:07
*** masahito has joined #openstack-meeting-alt19:36
*** masahito has quit IRC19:41
*** erlon has quit IRC19:58
*** yamamoto has quit IRC20:05
*** ttsiouts has joined #openstack-meeting-alt20:26
*** jtomasek has joined #openstack-meeting-alt20:41
*** e0ne has quit IRC20:42
*** SimAloo has quit IRC20:45
*** sdake has quit IRC20:45
*** SimAloo has joined #openstack-meeting-alt20:58
*** munimeha1 has joined #openstack-meeting-alt21:11
*** diablo_rojo has joined #openstack-meeting-alt21:31
*** masahito has joined #openstack-meeting-alt21:37
*** jcoufal has quit IRC21:39
*** masahito has quit IRC21:42
*** jtomasek has quit IRC22:01
*** sdake has joined #openstack-meeting-alt22:15
*** igordc has quit IRC22:21
*** TxGirlGeek has quit IRC22:32
*** igordc has joined #openstack-meeting-alt22:34
*** gyee has quit IRC22:35
*** slaweq has quit IRC22:36
*** munimeha1 has quit IRC22:43
*** SimAloo has quit IRC23:03
*** diablo_rojo has quit IRC23:07
*** radeks_ has quit IRC23:15
*** TxGirlGeek has joined #openstack-meeting-alt23:28
*** TxGirlGeek has quit IRC23:29
*** TxGirlGe_ has joined #openstack-meeting-alt23:29
*** sdake has quit IRC23:35
*** sdake has joined #openstack-meeting-alt23:37
*** masahito has joined #openstack-meeting-alt23:39
*** masahito has quit IRC23:43
*** rcernin has quit IRC23:53
*** sdake has quit IRC23:55
*** sdake has joined #openstack-meeting-alt23:56

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