Tuesday, 2019-08-20

*** markvoelker has quit IRC00:01
*** jamesmcarthur has quit IRC00:23
*** gyee has quit IRC00:36
*** altlogbot_0 has quit IRC00:46
*** altlogbot_2 has joined #openstack-meeting-alt00:47
*** igordc has quit IRC01:11
*** hongbin has joined #openstack-meeting-alt01:24
*** dviroel_ has quit IRC01:42
*** markvoelker has joined #openstack-meeting-alt01:51
*** markvoelker has quit IRC01:55
*** apetrich has quit IRC02:10
*** diablo_rojo has joined #openstack-meeting-alt02:43
*** bhavikdbavishi has joined #openstack-meeting-alt03:08
*** bhavikdbavishi1 has joined #openstack-meeting-alt03:11
*** bhavikdbavishi has quit IRC03:13
*** bhavikdbavishi1 is now known as bhavikdbavishi03:13
*** hongbin has quit IRC03:51
*** janki has joined #openstack-meeting-alt05:10
*** links has joined #openstack-meeting-alt05:14
*** diablo_rojo has quit IRC05:27
*** links has quit IRC05:35
*** links has joined #openstack-meeting-alt05:37
*** kopecmartin|off is now known as kopecmartin05:37
*** persia has quit IRC05:49
*** markvoelker has joined #openstack-meeting-alt05:55
*** persia has joined #openstack-meeting-alt06:00
*** persia has quit IRC06:03
*** persia has joined #openstack-meeting-alt06:05
*** persia has quit IRC06:05
*** markvoelker has quit IRC06:05
*** persia has joined #openstack-meeting-alt06:05
*** markvoelker has joined #openstack-meeting-alt06:06
*** markvoelker has quit IRC06:10
*** tsmith2 has quit IRC06:11
*** tsmith2 has joined #openstack-meeting-alt06:11
*** rcernin has quit IRC06:35
*** hongbin has joined #openstack-meeting-alt06:52
*** hongbin has quit IRC06:56
*** ianychoi has quit IRC07:46
*** ianychoi has joined #openstack-meeting-alt07:47
*** jraju__ has joined #openstack-meeting-alt07:55
*** links has quit IRC07:56
*** priteau has joined #openstack-meeting-alt08:06
*** apetrich has joined #openstack-meeting-alt08:13
*** panda has quit IRC08:18
*** panda has joined #openstack-meeting-alt08:20
*** e0ne has joined #openstack-meeting-alt08:26
*** derekh has joined #openstack-meeting-alt08:28
*** jamesmcarthur has joined #openstack-meeting-alt08:28
*** tetsuro has joined #openstack-meeting-alt08:49
*** masahito has joined #openstack-meeting-alt08:49
*** jamesmcarthur has quit IRC08:57
*** jamesmcarthur has joined #openstack-meeting-alt08:59
priteau#startmeeting blazar09:00
openstackMeeting started Tue Aug 20 09:00:00 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
masahitoo/09:00
tetsuroo/09:00
priteauHi masahito and tetsuro!09:00
priteauDo you know if Bertrand is joining?09:02
tetsuroI have no idea09:02
priteauHe may be on holiday, so let's start09:04
priteauAgenda for today:09:04
priteau- Project update @ Shanghai Summit09:04
priteau- Activities @ Shanghai PTG09:04
priteau- Blazar client release09:04
priteau- Change of blazar-dashboard release model09:04
priteau- Code review priorities09:04
priteau- AOB09:05
priteau#topic Project update @ Shanghai Summit09:05
*** openstack changes topic to "Project update @ Shanghai Summit (Meeting topic: blazar)"09:05
*** jchhatbar has joined #openstack-meeting-alt09:06
priteauFor Shanghai, 40 slots are available for project updates.09:06
*** jchhatbar has quit IRC09:06
priteauSlots will be reserved on a first come, first served basis.09:06
*** jchhatbar has joined #openstack-meeting-alt09:07
priteauThis was notified a week ago so we should reply as soon as possible.09:07
*** janki has quit IRC09:07
*** jchhatbar has quit IRC09:07
*** janki has joined #openstack-meeting-alt09:08
priteauUnfortunately my (non-Blazar) talk was not accepted for the summit.09:08
*** jamesmcarthur has quit IRC09:08
*** jamesmcarthur has joined #openstack-meeting-alt09:09
priteauGiven that many placement / nova people are skipping this summit, I'm inclined to skip this one as well, as it's a lot of time spent on travel and logistics.09:09
priteautetsuro: Are you interested in giving a Blazar project update? You already gave one at last summit, so I understand if you don't feel like doing it again.09:10
masahitoI will be the summit.09:10
tetsuroI don't have any talk accepted, but I'm coming to Shanghai and it is already approved, and I can help to have the session.09:11
masahitos/be the summit/be in the summit/09:11
tetsurothe session <- I meant the project update session09:11
priteaumasahito: That's good news. Would you be happy to present the project update as well?09:11
priteauWe have a choice of 15 min or 40 min session. I think 15 min makes sense for us.09:12
masahitoI'm okay to present it if we need to have project update session.09:12
masahito15min makes sense to me.09:13
priteauEspecially since we don't yet have as many new features as previous release cycles.09:13
masahitoAgree09:14
priteauI'll include Bertrand as well, we can remove him later if he doesn't want / can't participate09:15
*** rcernin has joined #openstack-meeting-alt09:16
priteauI've just submitted the request now09:16
tetsuroThanks!09:16
priteauWe must also confirm one registration to the summit by Sunday September 29th at 7:00 UTC09:16
priteauIf either of you is already registered, I can send the confirmation09:17
tetsuroI am already registered.09:17
masahitoI haven't registered yet because of company reason.09:18
priteautetsuro: Thanks, I will confirm09:18
masahitoI'll check it tomorrow and will change email address in OpenStack ID09:18
priteauThanks.09:19
priteau#topic Activities @ Shanghai PTG09:19
*** openstack changes topic to "Activities @ Shanghai PTG (Meeting topic: blazar)"09:19
priteauWe've requested a Project Onboarding session at the PTG09:20
priteauWe'll have to decide how long would be the session and prepare materials.09:21
priteauI don't think I've ever been to a project onboarding session, but I saw slides online that we can use for inspiration.09:21
priteauThere is also the option of holding technical discussions in person at the PTG, if you are interested. We'll want to have a virtual PTG anyway, probably before the summit.09:23
*** apetrich has quit IRC09:25
priteauLet me know if you're interested in having some technical discussions. There will be less dedicated space at the PTG, so those discussions would likely be in the shared space and can be organised at the last minute.09:25
masahitoI think number of Blazar team member is not big. I'm okay not to have dedicated space.09:26
masahitoShared space is okay to me.09:27
*** bhavikdbavishi has quit IRC09:27
*** apetrich has joined #openstack-meeting-alt09:28
priteauDepends who joins the discussion. Last year in Denver we had quite a big attendance when we discussed with the placement people. But in Shanghai many will not be there.09:28
priteauEven if NTT Data people are joining, it will only be 5 or 6 people in total.09:29
priteauWe'll talk again about Project Onboarding in the coming weeks. Let's carry on with the agenda09:30
priteau#topic Blazar client release09:30
*** openstack changes topic to "Blazar client release (Meeting topic: blazar)"09:30
priteauWe were prompted to release python-blazarclient: https://review.opendev.org/#/c/675314/09:30
priteauI think there are some infra requirements meaning we need to release at least once in a cycle09:31
priteauThe good thing is we have a new feature to include: floating IP reservation.09:31
priteauI just want to include a little fix: https://review.opendev.org/#/c/676217/09:31
priteauThanks both for the review, I will create a bug in LP09:32
tetsuroThanks09:32
tetsuroI'm ready to +W if that is reported.09:32
priteauAfterwards I will update the release patch with the latest commit09:33
priteau#topic Change of blazar-dashboard release model09:34
*** openstack changes topic to "Change of blazar-dashboard release model (Meeting topic: blazar)"09:34
priteauThis one needs some discussion09:34
priteau#link https://review.opendev.org/#/c/675471/09:34
priteauIt was proposed to change blazar-dashboard to the cycle-with-rc model09:34
priteauThis has been proposed to other projects that haven't released yet in the Train cycle. Some have decided to move to cycle-with-rc, while other requested to stay on cycle-with-intermediary09:36
priteauI like the option of being able to release blazar-dashboard when we want, like with the python client09:37
masahitoI don't have an objection to move the release model.09:37
priteauBut we don't have much activity on blazar-dashboard at the moment09:38
priteauSo it will be difficult justifying stayin on cycle-with-intermediary09:38
priteauIf we move to cycle-with-rc, we will have to create an rc1 before Sep 23 - Sep 2709:40
priteauthen a final release by Oct 14 - Oct 1809:40
priteautetsuro: Any thoughts on this topic?09:41
*** jamesmcarthur has quit IRC09:41
tetsuroWhy has it been cycle-with-intermediary model?09:42
priteauI think it was the model used by most Horizon dashboards at the time09:42
tetsuroOh I see, if that is only the reason I don't think there are any blockers to move to cycle-with-rc model?09:43
priteauRight, there is no blocker. We lose some flexibility: for example if we had developers active on blazar-dashboard now, we could release a new version with floating IP support and, assuming that the Horizon API interface doesn't change, it could be deployed on OpenStack Stein .09:45
priteauI suppose we can move back to another model in the future if needed.09:45
tetsuroWait, is the python-blazarclient cycle-with-rc or cycle-with-intermediary09:46
priteaupython-blazarclient is cycle-with-intermediary09:46
tetsuroAh, I see.09:46
priteauWhich is why we can release now09:46
priteauBut we have people active on python-blazarclient, not so much on the dashboard.09:47
tetsuroGot it. Okay, then yeah, ideally we will want to come back to the intermediary model.09:48
priteauI'll ask if we can move back easily09:48
priteauI suppose we have until rc1 to decide.09:48
*** masahito has quit IRC09:49
*** masahito has joined #openstack-meeting-alt09:49
priteauI asked Kendall on Gerrit09:49
tetsuroIn this release we won't have many releases on dashboard.09:49
tetsuroThanks.09:50
priteauLet's revisit next week depending on her answer.09:50
priteauJust 10 minutes left09:50
priteau#topic Code review priorities09:50
*** openstack changes topic to "Code review priorities (Meeting topic: blazar)"09:50
priteauWe have some new patches to review09:50
priteauJake from Chameleon has submitted a spec for network reservation: https://review.opendev.org/#/c/674089/09:51
priteauI've already suggested some changes09:51
priteauI've got a placement bugfix that we really need to include in this release: https://review.opendev.org/#/c/671312/09:52
tetsuroAck. I'll have a look shortly09:55
priteauThank you. It's a very easy one09:55
priteauThere are also more patch from Jake: https://review.opendev.org/#/c/672994/ and https://review.opendev.org/#/c/672763/09:56
priteauAnd of course the patch series from Asmita09:56
priteau#topic AOB09:56
*** openstack changes topic to "AOB (Meeting topic: blazar)"09:56
priteauAnything else to mention before we end?09:56
masahitonothing from my side09:58
tetsuronothing09:58
priteauThanks a lot!09:59
priteaufor joining09:59
priteauTalk to you next week!09:59
priteau#endmeeting09:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:59
openstackMeeting ended Tue Aug 20 09:59:53 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/blazar/2019/blazar.2019-08-20-09.00.html09:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/blazar/2019/blazar.2019-08-20-09.00.txt09:59
openstackLog:            http://eavesdrop.openstack.org/meetings/blazar/2019/blazar.2019-08-20-09.00.log.html09:59
masahitothanks10:00
*** yamamoto has quit IRC10:00
tetsuroThanks110:01
*** tetsuro has quit IRC10:01
*** masahito has quit IRC10:05
*** jamesmcarthur has joined #openstack-meeting-alt10:16
*** priteau has quit IRC10:18
*** jamesmcarthur has quit IRC10:23
*** yamamoto has joined #openstack-meeting-alt10:23
*** rcernin has quit IRC10:28
*** dosaboy has quit IRC10:42
*** ganso has quit IRC10:42
*** tpsilva has quit IRC10:42
*** jamesmcarthur has joined #openstack-meeting-alt10:55
*** jamesmcarthur has quit IRC11:00
*** macz has joined #openstack-meeting-alt11:04
*** tesseract has joined #openstack-meeting-alt11:08
*** macz has quit IRC11:09
*** dave-mccowan has joined #openstack-meeting-alt11:20
*** ganso has joined #openstack-meeting-alt11:24
*** carloss has joined #openstack-meeting-alt11:25
*** tpsilva has joined #openstack-meeting-alt11:25
*** dosaboy has joined #openstack-meeting-alt11:28
*** markvoelker has joined #openstack-meeting-alt11:35
*** jamesmcarthur has joined #openstack-meeting-alt11:36
*** jamesmcarthur has quit IRC11:40
*** markvoelker has quit IRC11:40
*** jamesmcarthur has joined #openstack-meeting-alt11:43
*** bhavikdbavishi has joined #openstack-meeting-alt11:51
*** bhavikdbavishi1 has joined #openstack-meeting-alt11:54
*** bhavikdbavishi has quit IRC11:55
*** bhavikdbavishi1 is now known as bhavikdbavishi11:55
*** markvoelker has joined #openstack-meeting-alt11:57
*** raildo has joined #openstack-meeting-alt12:02
*** jamesmcarthur has quit IRC12:24
*** jamesmcarthur has joined #openstack-meeting-alt12:25
*** jamesmcarthur has quit IRC12:29
*** dviroel_ has joined #openstack-meeting-alt12:36
*** dviroel_ is now known as dviroel12:39
*** yamamoto has quit IRC12:47
*** jamesmcarthur has joined #openstack-meeting-alt12:52
*** yamamoto has joined #openstack-meeting-alt13:00
*** yamamoto has quit IRC13:04
*** yamamoto has joined #openstack-meeting-alt13:05
*** bhavikdbavishi has quit IRC13:24
*** yamamoto has quit IRC13:28
*** lseki has joined #openstack-meeting-alt13:39
*** janki has quit IRC14:04
*** liuyulong has joined #openstack-meeting-alt14:06
*** dave-mccowan has quit IRC14:12
*** yamamoto has joined #openstack-meeting-alt14:16
*** yamamoto has quit IRC14:16
*** yamamoto has joined #openstack-meeting-alt14:18
*** yamamoto has quit IRC14:20
*** yamamoto has joined #openstack-meeting-alt14:21
*** yamamoto has quit IRC14:22
*** yamamoto has joined #openstack-meeting-alt14:24
*** yamamoto has quit IRC14:35
*** yamamoto has joined #openstack-meeting-alt14:44
*** openstack has joined #openstack-meeting-alt15:03
*** ChanServ sets mode: +o openstack15:03
*** gagehugo has joined #openstack-meeting-alt15:10
*** yamamoto has quit IRC15:14
*** bhavikdbavishi has joined #openstack-meeting-alt15:16
*** bhavikdbavishi1 has joined #openstack-meeting-alt15:19
*** bhavikdbavishi has quit IRC15:20
*** bhavikdbavishi1 is now known as bhavikdbavishi15:20
*** dave-mccowan has joined #openstack-meeting-alt15:32
*** baojg has joined #openstack-meeting-alt15:36
*** baojg has quit IRC15:36
*** baojg has joined #openstack-meeting-alt15:37
*** baojg has quit IRC15:37
*** baojg has joined #openstack-meeting-alt15:38
*** baojg has quit IRC15:38
*** baojg has joined #openstack-meeting-alt15:39
*** baojg has quit IRC15:40
*** gyee has joined #openstack-meeting-alt15:45
*** macz has joined #openstack-meeting-alt15:51
cmurphy#startmeeting keystone16:00
openstackMeeting started Tue Aug 20 16:00:58 2019 UTC and is due to finish in 60 minutes.  The chair is cmurphy. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: keystone)"16:01
kmalloco/16:01
openstackThe meeting name has been set to 'keystone'16:01
cmurphy#link https://etherpad.openstack.org/p/keystone-weekly-meeting agenda16:01
vishakhao/16:01
cmurphyo/16:01
knikollao/16:01
gagehugoo/16:01
bnemeco/16:02
cmurphyhey everybody16:02
cmurphy#topic cmurphy on vacation16:03
*** openstack changes topic to "cmurphy on vacation (Meeting topic: keystone)"16:03
bnemecendmeeting? ;-)16:03
knikolla\o/ woohoo, haha16:03
cmurphylol16:03
cmurphyas an fyi I'll be away with no laptop and little cell service August 26-September 416:03
kmallocOK everyone, pack it up. we're done ;)16:03
kmalloc:P16:03
gagehugolol16:03
vishakhalol16:03
*** jamesmcarthur has quit IRC16:03
cmurphykmalloc: you don't get off the hook that easy :P16:03
cmurphykmalloc has agreed to step up as acting ptl while i'm gone16:04
cmurphy(thank you!)16:04
kmallochehe np16:04
knikollais doggo vice acting ptl?16:04
bnemecAlways16:04
kmallocfigure it's the least i can do, considering i'm going to be disappearing for Good Reasons(tm) soon16:04
*** jamesmcarthur has joined #openstack-meeting-alt16:05
cmurphyi'll be missing the next two meetings and office hours16:05
kmallocalso so cmurphy can get a well deserved break.16:05
*** prometheanfire has joined #openstack-meeting-alt16:05
cmurphykmalloc: and everyone, do you want to keep the next two meetings or cancel them?16:05
prometheanfirejust joined, is it open floor time?16:06
kmallochm. lets see.16:06
kmalloclets keep next meeting and we'll see if we want to skip the following one16:06
cmurphyprometheanfire: 6 minutes in? not yet :P16:06
cmurphykmalloc: sounds good16:06
kmallocif there is no agenda, we'll just start and let folks go early16:07
cmurphyhow about office hours? or do you want to wait to decide?16:07
* prometheanfire has one bug to bring up16:07
cmurphyprometheanfire: it's on the agenda already16:07
kmallocoffice hours i think we'll skip16:08
kmallocuniless there is a good reason to do them.16:08
kmallocmeeting check in is more important imo, office hours have been slow-ish anyway16:08
cmurphyagreed16:09
cmurphythanks again kmalloc16:10
cmurphy#topic oauthlib requirements fix16:10
*** openstack changes topic to "oauthlib requirements fix (Meeting topic: keystone)"16:10
cmurphyprometheanfire: this is what you wanted to talk about right?16:10
prometheanfirehttps://bugs.launchpad.net/keystone/+bug/183939316:10
openstackLaunchpad bug 1839393 in OpenStack Identity (keystone) "oauthlib===3.1.0 fails tests (requirements update)" [Low,Triaged]16:10
prometheanfirejust that freeze is coming up in a couple of weeks so it'd be nice to clear that out16:11
cmurphyI haven't looked at it but I'm hoping it will be easyish, any volunteers to take it?16:12
kmallocIf I wasn't swamped with resource options and ... doctor appointments, i'd offer16:12
vishakhaI can look inti it16:12
cmurphymaybe vishakha or gagehugo ? ;)16:12
cmurphyhaha ty16:12
prometheanfirethanks16:12
kmalloconce i'm done with resource options, etc, if no one else has looked, I'll try and throw something at it, but i think it would be better if I could review.16:13
vishakhayw :)16:13
kmallocso we can land it qu... yay vishakha !!! :)16:13
cmurphyprometheanfire: when's the deadline again?16:13
gagehugovishakha: ping me if you need any help with that16:13
prometheanfire13th iirc16:13
cmurphyalrighty16:14
vishakhagagehugo sure16:14
cmurphyanything else on that?16:14
prometheanfiresept 9-13 time16:14
prometheanfirehttps://releases.openstack.org/train/schedule.html16:14
vishakhaThanks prometheanfire  for the information16:15
cmurphy#info requirements freeze september 9-1316:15
cmurphy#action vishakha to look into https://bugs.launchpad.net/keystone/+bug/183939316:15
openstackLaunchpad bug 1839393 in OpenStack Identity (keystone) "oauthlib===3.1.0 fails tests (requirements update)" [Low,Triaged]16:15
cmurphy#topic Forum, pre-PTG and post-PTG planning16:16
*** openstack changes topic to "Forum, pre-PTG and post-PTG planning (Meeting topic: keystone)"16:16
cmurphyon this topic, I don't have anything solid to offer yet but wanted to get people thinking about it so we can start working out the details when I get back16:16
cmurphyeven if you don't plan on going to shanghai I'm hoping people can contribute ideas that they want to see discussed at the forum, I'll be happy to moderate them16:17
cmurphy#link https://etherpad.openstack.org/p/keystone-shanghai-ptg Shanghai PTG/Forum brainstorm16:17
*** markvoelker has quit IRC16:17
kmallocdo we know what the next cycle is going to look like, roughly? milestones, etc?16:18
kmalloctrying to gauge how much of the cycle i'm going to be missing while i am on leave.16:19
cmurphyat the moment I assume it's going to be a regular six-month cycle with the same milestone markers16:19
kmallocok, so, since i'm bad at math... when would you expect m1 to be?16:19
kmalloci can bug you out of the meeting on this.16:20
kmalloctable it.16:20
cmurphyyeah i would have to do some counting16:20
cmurphyanyone already have topic ideas they want to throw out there?16:21
bnemecoslo.limit16:21
cmurphythat's a good one16:21
bnemecI suppose I should just add that to the etherpad.16:21
cmurphy++16:21
bnemecI put it in both sections since I'm guessing there will be both cross-project and in-Keystone discussion needed.16:23
cmurphyyes probably16:23
bnemecMaybe the policy scope stuff for the forum?16:24
bnemecI know you're wrapping it up, but the other projects will probably need some guidance.16:24
cmurphyyep, hopefully we'll have our side done, maybe nova will also have part of theirs done16:24
cmurphyin which case we could start talking about making it a community goal16:25
*** e0ne has quit IRC16:25
bnemecLike the fuchsia etherpad color. :-)16:25
* bnemec has no idea if that's spelled right16:26
cmurphyfor the virtual PTG i think we decided to do both pre- and post- IRL ptg meetings16:26
cmurphywill the week before and after work for most people? ie sometime in oct 28-nov 1 and nov 11-1516:27
kmallocas a note, none of those work for me, but that is to be expected16:28
kmallocplease just expect i'll be missing the virtual ptg(s)16:28
kmallocI promise to share some photos in lieu of my joining the PTGs :)16:29
cmurphykmalloc: i'm guessing we won't easily be able to work around your time off16:29
cmurphyyay :)16:29
bnemecAn acceptable trade. :-)16:29
cmurphyhow many hours/days should we do for each meeting?16:32
*** markvoelker has joined #openstack-meeting-alt16:33
cmurphyokay well maybe please start adding topics to the etherpad for the ptgs and i'll try to come up with a plan that allows us to cover everything16:35
cmurphyand will send out a scheduling poll16:35
cmurphy#topic renewable group membership16:36
gagehugook16:36
*** openstack changes topic to "renewable group membership (Meeting topic: keystone)"16:36
cmurphyknikolla: all you16:36
knikollao/16:36
knikollaso i wanted some feedback on a few things16:36
knikollafirst: should these renewable group memberships appear in the API response for list groups in use and list users for group?16:37
knikollaShould they appear in a separate API or with a special flag? Or should they just be a backend thing and not really be exposed with listing.16:37
cmurphythe only way these users become members of groups is through mappings right?16:40
knikollayes16:40
knikollacreating these directly will not be supported, just through mappings.16:41
cmurphyhmm16:41
*** jraju__ has quit IRC16:41
cmurphyis there any need for a user to be able to view their own expiring group membership? or for admins to be able to see whose memberships are about to expire?16:42
kmalloci think it might be nice if a user could see it16:44
knikollajust for info, cause they won't be able to act on that info returned.16:44
kmallocbut ^ yeah, it's informational strictly16:44
knikollai was thinking of a include_expiring=True flag on listings16:44
kmalloc?include_expiring16:44
knikollayes16:44
kmallochm. sure16:45
kmallocfilter_by=expiring16:45
cmurphyif it's not too difficult to implement it doesn't seem like a bad idea16:45
knikollahmmm.... it does seem a bit of a lie if you "filter" by returning different content16:45
cmurphyotoh if it's a pain then we could keep it just on the backend for now and expose it later if we decide we need it16:46
kmalloc^16:46
knikolla++16:46
kmallocwfm16:46
kmallocexpose it unless it's a royal PITA then, expose it later if needed16:47
knikollasure16:47
knikollathe other point i had, is that the dependencies between identity backend and federation backend are growing stronger16:47
knikollaand if it makes sense to just merge the two together in a future cycle16:47
knikollaFederatedUser has a foreign key on IdentityProvider16:48
knikollaExpiringUserGroupMembership will have one as well16:48
kmalloc*shrug* they can merge.16:52
kmallocit's not really that big a deal imo.16:52
cmurphyI don't really think of idps/mappings/protocols as in the same category as users/groups16:52
cmurphyit would feel a little weird to me to merge them16:53
cmurphyalso - the federation stuff can't be backed by ldap16:53
knikollathat's all i had, we don't have to take a decision now16:54
knikollajust wanted to get an overall feeling16:54
* knikolla yields floow16:55
knikollafloor16:55
cmurphyknikolla: i guess my last message was more of a question - what happens when the identity backend is backed by ldap, if federation merges with it?16:56
kmalloci think with FKs, it kindof breaks as is16:56
knikollacmurphy: there shouldn't be any difference to how it works today.16:56
knikollaI think domain specific drivers would still be applicable.16:56
cmurphyhmm okay16:57
knikollaYou kinda have to use a shadow backend with sql anyway with ldap16:57
cmurphythat's true16:57
knikollathis was more of a realization that we've separated two things and required using them together16:58
*** diablo_rojo has quit IRC16:58
knikollai can propose a spec to backlog with a more argumentative problem description and gather feedback there.16:58
cmurphysounds good16:59
*** diablo_rojo has joined #openstack-meeting-alt16:59
kmallocwfm16:59
cmurphy#action knikolla propose spec to backlog about merging federation and identity backends16:59
cmurphy#topic open floor16:59
*** openstack changes topic to "open floor (Meeting topic: keystone)"16:59
*** derekh has quit IRC16:59
cmurphyi proposed an office hours topic to discuss the spec features in flight16:59
cmurphyand we're out of time17:00
cmurphy#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Tue Aug 20 17:00:17 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-08-20-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-08-20-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-08-20-16.00.log.html17:00
*** prometheanfire has left #openstack-meeting-alt17:01
*** jamesmcarthur has quit IRC17:04
*** gyee has quit IRC17:09
*** tesseract has quit IRC17:10
*** kopecmartin is now known as kopecmartin|off17:19
*** gyee has joined #openstack-meeting-alt17:22
*** bhavikdbavishi has quit IRC17:24
*** raildo has quit IRC17:25
*** bhavikdbavishi has joined #openstack-meeting-alt17:27
*** raildo has joined #openstack-meeting-alt17:32
*** jamesmcarthur has joined #openstack-meeting-alt17:38
*** tesseract has joined #openstack-meeting-alt17:45
*** igordc has joined #openstack-meeting-alt17:48
*** jamesmcarthur has quit IRC18:05
*** jamesmcarthur has joined #openstack-meeting-alt18:06
*** jamesmcarthur has quit IRC18:12
*** jamesmcarthur has joined #openstack-meeting-alt18:13
*** markvoelker has quit IRC18:34
*** gagehugo has left #openstack-meeting-alt18:52
*** jamesmcarthur has quit IRC18:58
*** ganso has left #openstack-meeting-alt19:02
*** jamesmcarthur has joined #openstack-meeting-alt19:28
*** e0ne has joined #openstack-meeting-alt19:32
*** jamesmcarthur has quit IRC19:59
*** jamesmcarthur has joined #openstack-meeting-alt20:00
*** diablo_rojo has quit IRC20:10
*** markvoelker has joined #openstack-meeting-alt20:15
*** markvoelker has quit IRC20:16
*** markvoelker has joined #openstack-meeting-alt20:16
*** diablo_rojo has joined #openstack-meeting-alt20:27
*** jamesmcarthur has quit IRC20:40
*** jamesmcarthur_ has joined #openstack-meeting-alt20:40
*** jamesmcarthur_ has quit IRC20:47
*** bhavikdbavishi has quit IRC20:47
*** e0ne has quit IRC20:50
*** jamesmcarthur has joined #openstack-meeting-alt20:55
*** jamesmcarthur has quit IRC20:58
*** jamesmcarthur has joined #openstack-meeting-alt20:58
*** jamesmcarthur has quit IRC21:04
*** markvoelker has quit IRC21:22
*** bnemec has quit IRC21:27
*** diablo_rojo has quit IRC21:31
*** tesseract has quit IRC21:32
*** markvoelker has joined #openstack-meeting-alt21:35
*** yamamoto has joined #openstack-meeting-alt21:38
*** raildo has quit IRC21:39
*** yamamoto has quit IRC21:39
*** markvoelker has quit IRC21:40
*** rcernin has joined #openstack-meeting-alt22:00
*** markvoelker has joined #openstack-meeting-alt22:10
*** markvoelker has quit IRC22:15
*** carloss has quit IRC22:21
*** markvoelker has joined #openstack-meeting-alt22:29
*** markvoelker has quit IRC22:48
*** markvoelker has joined #openstack-meeting-alt23:12
*** markvoelker has quit IRC23:22
*** tsmith2 has quit IRC23:41
*** tsmith2 has joined #openstack-meeting-alt23:41
*** macz has quit IRC23:48

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