| *** hongbin has quit IRC | 00:16 | |
| *** macza has joined #openstack-meeting-alt | 00:37 | |
| *** macza has quit IRC | 00:42 | |
| *** tetsuro has joined #openstack-meeting-alt | 00:43 | |
| *** cloudrancher has quit IRC | 00:47 | |
| *** cloudrancher has joined #openstack-meeting-alt | 00:49 | |
| *** lhinds has quit IRC | 00:51 | |
| *** lhinds has joined #openstack-meeting-alt | 00:55 | |
| *** slaweq has joined #openstack-meeting-alt | 01:11 | |
| *** slaweq has quit IRC | 01:16 | |
| *** cloudrancher has quit IRC | 01:19 | |
| *** cloudrancher has joined #openstack-meeting-alt | 01:20 | |
| *** yamahata has quit IRC | 01:24 | |
| *** yamamoto has quit IRC | 01:41 | |
| *** yamamoto has joined #openstack-meeting-alt | 01:41 | |
| *** hongbin has joined #openstack-meeting-alt | 02:09 | |
| *** diablo_rojo has quit IRC | 02:17 | |
| *** cloudrancher has quit IRC | 02:44 | |
| *** cloudrancher has joined #openstack-meeting-alt | 02:45 | |
| *** macza has joined #openstack-meeting-alt | 02:55 | |
| *** macza has quit IRC | 02:59 | |
| *** bhavikdbavishi has joined #openstack-meeting-alt | 03:07 | |
| *** cloudrancher has quit IRC | 03:08 | |
| *** cloudrancher has joined #openstack-meeting-alt | 03:09 | |
| *** slaweq has joined #openstack-meeting-alt | 03:11 | |
| *** slaweq has quit IRC | 03:16 | |
| *** hongbin has quit IRC | 03:48 | |
| *** bswartz has quit IRC | 03:51 | |
| *** lpetrut has joined #openstack-meeting-alt | 03:52 | |
| *** bhavikdbavishi has quit IRC | 03:54 | |
| *** slaweq has joined #openstack-meeting-alt | 04:11 | |
| *** macza has joined #openstack-meeting-alt | 04:12 | |
| *** slaweq has quit IRC | 04:16 | |
| *** lpetrut has quit IRC | 04:34 | |
| *** bhavikdbavishi has joined #openstack-meeting-alt | 04:35 | |
| *** bhavikdbavishi has quit IRC | 04:52 | |
| *** bhavikdbavishi has joined #openstack-meeting-alt | 04:52 | |
| *** liuyulong has quit IRC | 04:58 | |
| *** tetsuro has quit IRC | 05:04 | |
| *** macza_ has joined #openstack-meeting-alt | 05:08 | |
| *** slaweq has joined #openstack-meeting-alt | 05:11 | |
| *** macza has quit IRC | 05:12 | |
| *** macza_ has quit IRC | 05:12 | |
| *** macza has joined #openstack-meeting-alt | 05:13 | |
| *** slaweq has quit IRC | 05:15 | |
| *** macza has quit IRC | 05:20 | |
| *** macza has joined #openstack-meeting-alt | 05:20 | |
| *** macza has quit IRC | 05:24 | |
| *** apetrich has quit IRC | 05:40 | |
| *** janki has joined #openstack-meeting-alt | 05:47 | |
| *** dpawlik has joined #openstack-meeting-alt | 05:55 | |
| *** dpawlik has quit IRC | 06:00 | |
| *** apetrich has joined #openstack-meeting-alt | 06:00 | |
| *** dpawlik has joined #openstack-meeting-alt | 06:11 | |
| *** slaweq has joined #openstack-meeting-alt | 06:11 | |
| *** dpawlik has quit IRC | 06:12 | |
| *** dpawlik has joined #openstack-meeting-alt | 06:12 | |
| *** slaweq has quit IRC | 06:16 | |
| *** apetrich has quit IRC | 06:23 | |
| *** rdopiera has joined #openstack-meeting-alt | 06:36 | |
| *** apetrich has joined #openstack-meeting-alt | 06:44 | |
| *** e0ne has joined #openstack-meeting-alt | 06:48 | |
| *** slaweq has joined #openstack-meeting-alt | 06:56 | |
| *** rcernin has quit IRC | 07:01 | |
| *** jtomasek has joined #openstack-meeting-alt | 07:05 | |
| *** bhavikdbavishi1 has joined #openstack-meeting-alt | 07:14 | |
| *** bhavikdbavishi has quit IRC | 07:16 | |
| *** bhavikdbavishi1 is now known as bhavikdbavishi | 07:16 | |
| *** lpetrut has joined #openstack-meeting-alt | 07:20 | |
| *** lpetrut has quit IRC | 07:25 | |
| *** markvoelker has quit IRC | 07:29 | |
| *** markvoelker has joined #openstack-meeting-alt | 07:29 | |
| *** ttsiouts has joined #openstack-meeting-alt | 07:30 | |
| *** bhavikdbavishi has quit IRC | 07:32 | |
| *** markvoelker has quit IRC | 07:34 | |
| *** yamahata has joined #openstack-meeting-alt | 07:41 | |
| *** bhavikdbavishi has joined #openstack-meeting-alt | 07:53 | |
| *** bhavikdbavishi has quit IRC | 08:14 | |
| *** bhavikdbavishi has joined #openstack-meeting-alt | 08:15 | |
| *** bhavikdbavishi has quit IRC | 08:19 | |
| *** tetsuro has joined #openstack-meeting-alt | 08:21 | |
| *** yikun has quit IRC | 08:22 | |
| *** bhavikdbavishi has joined #openstack-meeting-alt | 08:27 | |
| *** markvoelker has joined #openstack-meeting-alt | 08:30 | |
| *** priteau has joined #openstack-meeting-alt | 08:31 | |
| *** e0ne has quit IRC | 08:37 | |
| *** e0ne has joined #openstack-meeting-alt | 08:44 | |
| *** derekh has joined #openstack-meeting-alt | 08:52 | |
| *** bertys has joined #openstack-meeting-alt | 08:57 | |
| priteau | #startmeeting blazar | 09:00 |
|---|---|---|
| openstack | Meeting started Tue Oct 16 09:00:02 2018 UTC and is due to finish in 60 minutes. The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot. | 09:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 09:00 |
| *** openstack changes topic to " (Meeting topic: blazar)" | 09:00 | |
| openstack | The meeting name has been set to 'blazar' | 09:00 |
| priteau | #topic Roll call | 09:00 |
| *** openstack changes topic to "Roll call (Meeting topic: blazar)" | 09:00 | |
| tetsuro | o/ | 09:01 |
| priteau | Hi tetsuro | 09:01 |
| *** masahito has joined #openstack-meeting-alt | 09:01 | |
| masahito | o/ | 09:01 |
| priteau | Hi masahito | 09:01 |
| priteau | I also see bertys is online | 09:02 |
| priteau | Agenda for today: | 09:02 |
| priteau | 1. Project Update @ Berlin Summit | 09:03 |
| priteau | 2. Forum @ Berlin Summit | 09:03 |
| priteau | 3. Changes to release cycle process | 09:03 |
| bertys | o/ | 09:03 |
| priteau | 4. stein-1 milestone | 09:03 |
| priteau | 5. | 09:03 |
| priteau | AOB | 09:03 |
| priteau | Hi bertys | 09:03 |
| bertys | Hi all | 09:03 |
| *** markvoelker has quit IRC | 09:03 | |
| priteau | #topic Project Update @ Berlin Summit | 09:03 |
| *** openstack changes topic to "Project Update @ Berlin Summit (Meeting topic: blazar)" | 09:03 | |
| priteau | Our talk is taking shape | 09:04 |
| priteau | #link https://docs.google.com/presentation/d/1nsuiQe72E0cYELSI8qLmNwVm4SOXzuf01akzqKEZ1TE/edit | 09:04 |
| priteau | I added preliminary content for "What is Blazar?" and completed the Stein slide | 09:05 |
| priteau | Tetsuro wrote a slide on cross-project work with placement | 09:05 |
| tetsuro | :) | 09:05 |
| priteau | Bertrand wrote one on how to give feedback | 09:05 |
| priteau | Thank you both | 09:05 |
| priteau | masahito: Are you still planning to write content for the Rocky slide? If you don't have time, I can help | 09:06 |
| masahito | Sorry, I didn't have much time to write last week. I'll do this in this week. | 09:06 |
| *** yamahata has quit IRC | 09:06 | |
| priteau | That's fine. We started early, still almost a month :-) | 09:06 |
| priteau | Exactly four weeks actually | 09:07 |
| masahito | I uploaded the Vancouver summit's one. | 09:07 |
| priteau | I see it now, thanks! | 09:07 |
| priteau | Could you please also add a little bit of information about the NFV use case on the first slide? | 09:08 |
| priteau | Well, on slide #2 | 09:08 |
| masahito | got it. | 09:08 |
| priteau | Thanks! | 09:08 |
| priteau | I'll take care of the "Beyond Stein" slide. | 09:09 |
| priteau | bertys: Will you take care of the "How to contribute" slide as well? | 09:10 |
| bertys | priteau: yes, as agreed. | 09:10 |
| priteau | All looks good then, thanks everyone :-) | 09:10 |
| priteau | Any comment on this topic? | 09:10 |
| priteau | Let's move to the next one | 09:12 |
| priteau | #topic Forum @ Berlin Summit | 09:12 |
| *** openstack changes topic to "Forum @ Berlin Summit (Meeting topic: blazar)" | 09:12 | |
| priteau | The Forum schedule is now up: | 09:13 |
| priteau | #link https://www.openstack.org/summit/berlin-2018/summit-schedule/#track=262 | 09:13 |
| priteau | The two sessions we submitted have been accepted! | 09:13 |
| priteau | #link https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22807/extending-blazar-reservations-to-new-resource-types | 09:13 |
| priteau | #link https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22806/python-bindings-for-the-placement-api | 09:13 |
| priteau | Now is the time to check for any schedule conflict | 09:14 |
| priteau | A good thing is that our placement session is right after "Update on placement extraction from nova", in the same room | 09:15 |
| masahito | Both are accepted! Nice! | 09:15 |
| priteau | So we should have lots of people interested in placement attend! | 09:15 |
| *** panda|off has quit IRC | 09:15 | |
| masahito | sounds good. | 09:16 |
| priteau | The Summit schedule is now mostly complete. Apparently just some BoFs and WGs are not yet up. | 09:17 |
| tetsuro | Would you mind if I put some topics about the host-reservation with placement to that Forum if we have time? | 09:18 |
| *** panda has joined #openstack-meeting-alt | 09:18 | |
| masahito | I don't mind if the topics is needed for the Forum. | 09:19 |
| masahito | s/if/unless/ | 09:20 |
| priteau | tetsuro: Preferably only if we have time at the end of the session, as it is potentially of interest for lots of projects consuming placement (Neutron, Cinder, Cyborg), not just Blazar + Placement | 09:20 |
| tetsuro | Yup, that's fair. | 09:21 |
| priteau | We should start Etherpads for each Forum session | 09:22 |
| priteau | I will create one for Blazar reservations. tetsuro, can you do the placement one? | 09:23 |
| tetsuro | Sure. | 09:24 |
| priteau | #action Create Etherpads for Forum @ Berlin Summit | 09:24 |
| priteau | Anything else to say about this? | 09:25 |
| priteau | Moving on | 09:26 |
| priteau | #topic Changes to release cycle process | 09:26 |
| *** openstack changes topic to "Changes to release cycle process (Meeting topic: blazar)" | 09:26 | |
| priteau | You may have seen on the mailing list, there are some changes being made to the release process | 09:26 |
| *** persia has quit IRC | 09:27 | |
| priteau | The cycle-with-milestones model will stop tagging milestones (i.e. for stein-1, stein-2, stein-3) | 09:27 |
| priteau | #link http://lists.openstack.org/pipermail/openstack-dev/2018-October/135706.html | 09:27 |
| *** persia has joined #openstack-meeting-alt | 09:28 | |
| priteau | This has impact on people testing upgrades because of versioning between stable branch and master (more detailed in the email thread), so the proposed solution is to use PBR Sem-Ver tagging | 09:29 |
| priteau | A commit has been proposed on each project, here's ours: https://review.openstack.org/#/c/610568/ | 09:29 |
| priteau | It automatically bumps our version number to 2.1.0 | 09:30 |
| priteau | See pip2 freeze output of the Zuul job: http://logs.openstack.org/68/610568/1/check/blazar-devstack-dsvm/1ed406c/logs/pip2-freeze.txt.gz | 09:31 |
| priteau | Compared to before the PBR commit: http://logs.openstack.org/78/610678/1/check/blazar-devstack-dsvm/4bfb0fa/logs/pip2-freeze.txt.gz | 09:31 |
| priteau | If there's no objection I will approve this patch | 09:31 |
| priteau | There's also a proposed change for library releases | 09:33 |
| masahito | I missed the ML thread, so not fully understand yet. | 09:33 |
| bertys | I am also wondering if we need patch for blazar-dashboard? | 09:33 |
| priteau | bertys: blazar-dashboard is cycle-with-intermediary, not cycle-with-milestones | 09:34 |
| bertys | priteau: I see, thanks | 09:35 |
| priteau | See https://releases.openstack.org/reference/release_models.html#cycle-with-intermediary vs https://releases.openstack.org/reference/release_models.html#cycle-with-milestones | 09:35 |
| priteau | masahito: A short summary is: | 09:36 |
| priteau | To reduce release overhead, they propose to stop tagging milestones, instead tagging only RCs | 09:36 |
| priteau | This has an impact on people testing upgrades from Rocky release to Stein development, as the version number has not bumped and Rocky release is seen as newer | 09:37 |
| priteau | Solution is to bump the release number early in the cycle, this is done via PBR Sem-Ver tag in a commit | 09:37 |
| priteau | There's not much impact for us. We merge this patch and continue working on our milestones as usual. | 09:38 |
| masahito | Thanks the summary. I'm fine to the change. | 09:39 |
| priteau | There is also a proposed change for cycle-with-intermediary library | 09:39 |
| priteau | #link http://lists.openstack.org/pipermail/openstack-dev/2018-October/135689.html | 09:39 |
| priteau | They will force a release at each milestone if there are changes and a release has not been done already | 09:39 |
| priteau | We have a few changes in python-blazarclient, but only internal infra (Zuul job) to small README change | 09:41 |
| priteau | I am not sure if that will trigger a release, we'll see | 09:41 |
| priteau | They are also thinking of requiring a person for each team to add their name to a "manifest" of sorts for the release cycle. | 09:43 |
| priteau | "That "final release liaison" person would be the designated person to follow through on finishing out the releases for that team, and would be designated ahead of the final release phases." | 09:43 |
| priteau | It can be the PTL but it doesn't have to be. I am happy to take this role unless someone wants to do it. | 09:43 |
| priteau | That was a rather long "For Your Information" really. | 09:44 |
| priteau | We need to move on as we have just 15 minutes left | 09:44 |
| priteau | #topic stein-1 milestone | 09:44 |
| *** openstack changes topic to "stein-1 milestone (Meeting topic: blazar)" | 09:44 | |
| priteau | #link https://launchpad.net/blazar/+milestone/stein-1 | 09:45 |
| priteau | stein-1 is next week | 09:45 |
| priteau | There's lots to do that we won't be able to complete, so we'll have to move them to stein-2 | 09:45 |
| priteau | Let's focus on reviewing what's ready | 09:46 |
| masahito | +1 | 09:46 |
| priteau | I have these two patches ready to review: https://review.openstack.org/#/q/topic:bug/1797940+(status:open+OR+status:merged) | 09:46 |
| priteau | I also gave a +2 to masahito's patches for instance reservation scenarios, we need another review: https://review.openstack.org/#/q/status:open+project:openstack/blazar-tempest-plugin+branch:master+topic:bug/1714438 | 09:47 |
| priteau | I am hoping to review tetsuro's code soon | 09:47 |
| priteau | bertys: Would you be able to review masahito's tempest code? | 09:48 |
| tetsuro | I rebased it today | 09:48 |
| tetsuro | ^just FYI | 09:48 |
| masahito | For s-1 milestone 4 series of my patch are ready to review. | 09:49 |
| masahito | https://review.openstack.org/#/q/status:open+project:openstack/blazar+branch:master+topic:bug/1304435 | 09:49 |
| masahito | https://review.openstack.org/#/q/status:open+project:openstack/blazar+branch:master+topic:bp/resource-availability-api | 09:49 |
| masahito | https://review.openstack.org/#/q/status:open+project:openstack/blazar+branch:stable/queens+topic:bug/1786007-stable/queens | 09:49 |
| masahito | https://review.openstack.org/#/q/status:open+project:openstack/blazar+branch:master+topic:bp/basic-network-plugin | 09:49 |
| priteau | Thanks for the reminder masahito | 09:50 |
| masahito | Most of tetsuro's patches looks good to me. If there're no objection, I'd like to merge the patches. | 09:51 |
| bertys | priteau: ok, will do today or tomorrow on best effort basis. I am not available on Thursday / Friday | 09:52 |
| masahito | Especially, the patches under blazar.utils doesn't affect current Blazar code. | 09:52 |
| priteau | masahito: I'll try to take a look at tetsuro's code later today | 09:52 |
| priteau | masahito: Thanks for the floating IP spec. I left a comment on Gerrit, wondering if there's an approach that would allow users to still associate IPs via Horizon rather than updating reservation params | 09:55 |
| masahito | priteau: That's what I ask you. The another approach is creating external networks for each reservations, right? | 09:56 |
| masahito | meaning one reservation is mapped to one external network. | 09:58 |
| priteau | That's an alternative, but as you explain in the spec, it is complex to configure for operators. | 09:58 |
| masahito | right. | 09:58 |
| priteau | I was wondering if there was an approach that would take a floating IP out of a single external network and assign it to the project which made the reservation | 09:58 |
| priteau | Like we drafted in Dublin | 09:59 |
| priteau | It may need some advanced configuration of Neutron policies. I found an approach for VLANs where I can create networks as Blazar using trusts, which makes them owned by the reserving project. | 10:00 |
| *** markvoelker has joined #openstack-meeting-alt | 10:00 | |
| priteau | We're running out of time. I will share the details with you. | 10:00 |
| priteau | #topic AOB | 10:00 |
| masahito | priteau: do you have time after the meeting? I want to check my understand is correct. | 10:00 |
| *** openstack changes topic to "AOB (Meeting topic: blazar)" | 10:00 | |
| priteau | Any AOB? | 10:00 |
| priteau | masahito: Unfortunately I have to go in another meeting right after | 10:01 |
| masahito | Got it. I also checked your one, but hit an issue. I'll reply it on the gerrit. | 10:01 |
| priteau | I can be on IRC tomorrow morning or we can discuss by email. | 10:02 |
| masahito | thanks. | 10:02 |
| priteau | Thanks! | 10:02 |
| priteau | We need to end. Have a good rest of the week. | 10:02 |
| priteau | #endmeeting | 10:02 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 10:02 | |
| openstack | Meeting ended Tue Oct 16 10:02:38 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 10:02 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/blazar/2018/blazar.2018-10-16-09.00.html | 10:02 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/blazar/2018/blazar.2018-10-16-09.00.txt | 10:02 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/blazar/2018/blazar.2018-10-16-09.00.log.html | 10:02 |
| *** tetsuro has quit IRC | 10:03 | |
| masahito | bye | 10:04 |
| *** bertys has quit IRC | 10:04 | |
| *** erlon has joined #openstack-meeting-alt | 10:07 | |
| *** ttsiouts has quit IRC | 10:08 | |
| *** masahito has quit IRC | 10:13 | |
| *** tetsuro has joined #openstack-meeting-alt | 10:14 | |
| *** tetsuro has quit IRC | 10:16 | |
| *** ttsiouts has joined #openstack-meeting-alt | 10:29 | |
| *** markvoelker has quit IRC | 10:34 | |
| *** macza has joined #openstack-meeting-alt | 10:43 | |
| *** macza has quit IRC | 10:47 | |
| *** ttsiouts has quit IRC | 11:02 | |
| *** ttsiouts has joined #openstack-meeting-alt | 11:03 | |
| *** macza has joined #openstack-meeting-alt | 11:04 | |
| *** ttsiouts has quit IRC | 11:07 | |
| *** macza has quit IRC | 11:09 | |
| *** ttsiouts has joined #openstack-meeting-alt | 11:17 | |
| *** e0ne has quit IRC | 11:18 | |
| *** bhavikdbavishi has quit IRC | 11:23 | |
| *** markvoelker has joined #openstack-meeting-alt | 11:31 | |
| *** ttsiouts has quit IRC | 11:31 | |
| *** ttsiouts has joined #openstack-meeting-alt | 11:32 | |
| *** e0ne has joined #openstack-meeting-alt | 11:32 | |
| *** ttsiouts has quit IRC | 11:34 | |
| *** ttsiouts has joined #openstack-meeting-alt | 11:35 | |
| *** ttsiouts has quit IRC | 11:37 | |
| *** ttsiouts has joined #openstack-meeting-alt | 11:38 | |
| *** cloudrancher has quit IRC | 11:39 | |
| *** ttsiouts has quit IRC | 11:46 | |
| *** ttsiouts has joined #openstack-meeting-alt | 11:47 | |
| *** ttsiouts has quit IRC | 11:47 | |
| *** ttsiouts has joined #openstack-meeting-alt | 11:47 | |
| *** ttsiouts has quit IRC | 11:50 | |
| *** ttsiouts has joined #openstack-meeting-alt | 11:51 | |
| *** ttsiouts has quit IRC | 11:55 | |
| *** ttsiouts has joined #openstack-meeting-alt | 12:00 | |
| *** markvoelker has quit IRC | 12:04 | |
| *** yamamoto has quit IRC | 12:04 | |
| *** yamamoto has joined #openstack-meeting-alt | 12:05 | |
| *** yamamoto has quit IRC | 12:05 | |
| *** yamamoto has joined #openstack-meeting-alt | 12:05 | |
| *** dtrainor has joined #openstack-meeting-alt | 12:14 | |
| *** bhavikdbavishi has joined #openstack-meeting-alt | 12:17 | |
| *** e0ne has quit IRC | 12:24 | |
| *** e0ne has joined #openstack-meeting-alt | 12:27 | |
| *** ttsiouts has quit IRC | 12:32 | |
| *** raildo has joined #openstack-meeting-alt | 12:35 | |
| *** cloudrancher has joined #openstack-meeting-alt | 12:38 | |
| *** priteau has quit IRC | 12:39 | |
| *** priteau has joined #openstack-meeting-alt | 12:40 | |
| *** bhavikdbavishi has quit IRC | 12:49 | |
| *** macza has joined #openstack-meeting-alt | 12:53 | |
| *** macza has quit IRC | 12:58 | |
| *** efried has joined #openstack-meeting-alt | 13:10 | |
| *** yamamoto has quit IRC | 13:10 | |
| *** yamamoto has joined #openstack-meeting-alt | 13:11 | |
| *** e0ne has quit IRC | 13:12 | |
| *** dpawlik has quit IRC | 13:13 | |
| *** yamamoto has quit IRC | 13:15 | |
| *** e0ne has joined #openstack-meeting-alt | 13:16 | |
| *** dpawlik has joined #openstack-meeting-alt | 13:18 | |
| *** cloudrancher has quit IRC | 13:27 | |
| *** dpawlik has quit IRC | 13:30 | |
| *** dpawlik has joined #openstack-meeting-alt | 13:40 | |
| *** e0ne has quit IRC | 13:53 | |
| *** janki has quit IRC | 13:58 | |
| *** yamamoto has joined #openstack-meeting-alt | 14:00 | |
| *** yamahata has joined #openstack-meeting-alt | 14:01 | |
| *** e0ne has joined #openstack-meeting-alt | 14:01 | |
| *** hongbin has joined #openstack-meeting-alt | 14:05 | |
| *** dpawlik has quit IRC | 14:11 | |
| *** munimeha1 has joined #openstack-meeting-alt | 14:19 | |
| *** dpawlik has joined #openstack-meeting-alt | 14:46 | |
| *** dpawlik has quit IRC | 14:50 | |
| *** gagehugo has joined #openstack-meeting-alt | 14:56 | |
| *** ccamacho has quit IRC | 14:57 | |
| *** ccamacho has joined #openstack-meeting-alt | 15:00 | |
| *** SimAloo has joined #openstack-meeting-alt | 15:18 | |
| *** wxy| has joined #openstack-meeting-alt | 15:19 | |
| *** macza has joined #openstack-meeting-alt | 15:39 | |
| *** macza has quit IRC | 15:44 | |
| *** e0ne has quit IRC | 15:50 | |
| *** macza has joined #openstack-meeting-alt | 15:57 | |
| *** macza has quit IRC | 15:58 | |
| *** macza has joined #openstack-meeting-alt | 16:00 | |
| lbragstad | #startmeeting keystone | 16:00 |
| openstack | Meeting started Tue Oct 16 16:00:04 2018 UTC and is due to finish in 60 minutes. The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
| *** openstack changes topic to " (Meeting topic: keystone)" | 16:00 | |
| openstack | The meeting name has been set to 'keystone' | 16:00 |
| lbragstad | #link https://etherpad.openstack.org/p/keystone-weekly-meeting | 16:00 |
| knikolla | o/ | 16:00 |
| lbragstad | o/ | 16:00 |
| wxy| | o/ | 16:00 |
| gagehugo | o/ | 16:00 |
| lbragstad | we have a lot to get through today - so we'll get started in a minute | 16:01 |
| kmalloc | O/ | 16:01 |
| lbragstad | #topic Release status | 16:02 |
| *** openstack changes topic to "Release status (Meeting topic: keystone)" | 16:02 | |
| lbragstad | #info reminder that milestone 1 is going to be next | 16:02 |
| lbragstad | week | 16:02 |
| lbragstad | #link https://releases.openstack.org/stein/schedule.html | 16:02 |
| lbragstad | #info next weeks is the deadline for specification proposals | 16:03 |
| hrybacki | o/ (better channel) | 16:03 |
| lbragstad | (more onthat later) | 16:03 |
| *** ayoung has joined #openstack-meeting-alt | 16:03 | |
| lbragstad | also - it would be good to get as much community goal work squared away before next week as possibl e | 16:03 |
| lbragstad | #info mutable configuration goal implementation is up for review | 16:04 |
| lbragstad | #link https://review.openstack.org/#/c/585417/ | 16:04 |
| lbragstad | #info python3 first goal is nearly complete, and cmurphy is going to put the finishing touches on zuul changes so that keystone runs functional tests in python3 | 16:05 |
| lbragstad | #info the upgrade checker goal implementation is up for review | 16:05 |
| lbragstad | #link https://review.openstack.org/#/c/608785/ | 16:05 |
| ayoung | Do I need to go more official for my 2 Feature-Bugs for Domains and Federation? | 16:05 |
| ayoung | https://bugs.launchpad.net/keystone/+bugs?search=Search&field.assignee=ayoung | 16:06 |
| lbragstad | what's that ayoung? | 16:06 |
| ayoung | Is the bug report sufficient process, or do I need a spec? They seem small enough, and explainable enough to me, but then I am the author | 16:06 |
| lbragstad | um | 16:07 |
| ayoung | er | 16:07 |
| ayoung | sorry, thought that got the right set of bugs | 16:07 |
| ayoung | 1 sec | 16:07 |
| ayoung | https://bugs.launchpad.net/keystone/+bug/1794527 is right | 16:07 |
| openstack | Launchpad bug 1794527 in OpenStack Identity (keystone) "Allow domain creation with a specific ID" [Wishlist,Incomplete] - Assigned to Adam Young (ayoung) | 16:07 |
| ayoung | https://bugs.launchpad.net/keystone/+bug/1641639 is right | 16:07 |
| openstack | Launchpad bug 1641639 in OpenStack Identity (keystone) "use mapping_id for shadow users" [Wishlist,In progress] - Assigned to Adam Young (ayoung) | 16:07 |
| ayoung | yeah, those two | 16:07 |
| lbragstad | looks like https://bugs.launchpad.net/keystone/+bug/1794527 is going to be a spec anyway? | 16:07 |
| ayoung | lbragstad, I can. It just seems like busy work. | 16:08 |
| ayoung | I think I can explain it just as well in the bug | 16:08 |
| ayoung | But...I thought everyone understood the use case, and I'm more interested in making that the case | 16:08 |
| ayoung | a spec means spec approval process, etc | 16:09 |
| ayoung | and this is more like a tool that can be used for a larger use case, but not tied to it | 16:09 |
| lbragstad | since we've historically debated this case, i wouldn't mind a spec since it's more intuitive for discussion | 16:09 |
| ayoung | well, it really is just a dependency for the other one | 16:09 |
| ayoung | in my view | 16:09 |
| ayoung | "use mapping_id for shadow users" needs a common domain ID or the user ids change | 16:10 |
| lbragstad | yeah - that's understandable | 16:10 |
| lbragstad | i think specs work for this | 16:10 |
| kmalloc | i honestly am fine with a spec or a bug, if it is a spec, it will need a tracking bug anyway. | 16:10 |
| ayoung | these were designed to be as minimal as possible. Spec process means we don't get it this release. | 16:10 |
| lbragstad | as opposed to trying to debate the justification in bug comments and associating the two | 16:10 |
| ayoung | I mean...I could have tried to slip the domain_id change into the other bug, as that is really what is needed to fix it, just figured it was clearer to pull it out into its own | 16:11 |
| lbragstad | i think it should be it's own | 16:11 |
| *** cloudrancher has joined #openstack-meeting-alt | 16:11 | |
| ayoung | is everyone ok with these changes? Is there any real misunderstanding or objection? | 16:11 |
| lbragstad | i need to review it again | 16:12 |
| lbragstad | it's on my list | 16:12 |
| lbragstad | #topic specifications | 16:12 |
| *** openstack changes topic to "specifications (Meeting topic: keystone)" | 16:12 | |
| *** macza has quit IRC | 16:13 | |
| kmalloc | https://imgflip.com/i/2k8jz9 <--- OBJECTION | 16:13 |
| kmalloc | >.> | 16:13 |
| kmalloc | <.< | 16:13 |
| *** macza has joined #openstack-meeting-alt | 16:13 | |
| lbragstad | i would vote that we propose a specification for the domain id change, because that's always been a hot topic | 16:14 |
| lbragstad | and it affects the API | 16:14 |
| kmalloc | it's small enough i could see it being a bug alone. if it's a spec, i expect it to be very very empty | 16:14 |
| lbragstad | it's the discussion that i'd like to capture | 16:15 |
| kmalloc | and if people get too picky about the spec's contents, i'd be annoyed. | 16:15 |
| lbragstad | that and we have specification proposed for review that attempted to do something similar | 16:15 |
| kmalloc | so, ayoung can you propose a very light spec, anything that is "spec content" should be left to the side of the convo of if this is "good" | 16:15 |
| kmalloc | convo about merits of the change, not the spec content | 16:15 |
| kmalloc | and we should review that spec explicitly today/tomorrow | 16:15 |
| kmalloc | if we are making ayoung post it | 16:16 |
| ayoung | ok | 16:16 |
| kmalloc | ayoung: basic justification. | 16:16 |
| lbragstad | #action ayoung to propose https://bugs.launchpad.net/keystone/+bug/1794527 as a specification | 16:16 |
| openstack | Launchpad bug 1794527 in OpenStack Identity (keystone) "Allow domain creation with a specific ID" [Wishlist,Incomplete] - Assigned to Adam Young (ayoung) | 16:16 |
| kmalloc | please keep the bug as the tracker for it | 16:16 |
| ayoung | will do | 16:16 |
| lbragstad | thanks ayoung | 16:17 |
| kmalloc | and if folks do not register complaints about functionality in the next couple days, I warn you, it's going to be merged :) | 16:17 |
| lbragstad | if that's the case, socialize it on the mailing list so that it gets proper visibility | 16:17 |
| kmalloc | #action everyone review justification of ayoung's spec (please do not nit pick the content) | 16:17 |
| lbragstad | cmurphy is super busy this week | 16:17 |
| *** smyers has quit IRC | 16:18 | |
| kmalloc | right. this should be a quick review | 16:18 |
| kmalloc | and should be the core teams #1 review target for discussion | 16:18 |
| kmalloc | if there is discussion it can wait till S1 day | 16:18 |
| *** apetrich has quit IRC | 16:18 | |
| kmalloc | if there isn't active discussion/dissent we can merge it sooner | 16:18 |
| kmalloc | i expect this can land. | 16:18 |
| lbragstad | rememeber that specification freeze is january 11th | 16:19 |
| lbragstad | but - the earlier the better if we can helpit | 16:19 |
| kmalloc | exactly | 16:19 |
| knikolla | ++ | 16:19 |
| kmalloc | i expect there will be little dissent on this one | 16:19 |
| kmalloc | it is straightforward. | 16:19 |
| *** smyers has joined #openstack-meeting-alt | 16:19 | |
| kmalloc | so please review it this week. | 16:19 |
| lbragstad | ayoung outside of those two, do you have other specs to bring up? | 16:20 |
| kmalloc | lbragstad: also, holy crap jan 11 is a ways down the road for spec freeze :P long cycle is long | 16:20 |
| ayoung | I brought jamie's back to life, too | 16:20 |
| *** bhavikdbavishi has joined #openstack-meeting-alt | 16:20 | |
| lbragstad | yeah - this release is going to be a marathon | 16:20 |
| ayoung | https://review.openstack.org/#/c/607346/ | 16:20 |
| lbragstad | #link https://review.openstack.org/#/c/607346/ | 16:20 |
| kmalloc | unscoped catalog | 16:21 |
| *** d0ugal has quit IRC | 16:21 | |
| kmalloc | i would love to see this. | 16:21 |
| ayoung | that spec was approved, but then backlogged. I brought it back to the front. | 16:21 |
| ayoung | And its on the agenda for later, I think | 16:21 |
| kmalloc | just point blank. | 16:21 |
| ayoung | wanna talk it through now? | 16:21 |
| lbragstad | can we circle back if we have time? | 16:21 |
| ayoung | ++ | 16:21 |
| kmalloc | ++ | 16:21 |
| ayoung | just know that it is there | 16:21 |
| lbragstad | ok | 16:22 |
| lbragstad | ayoung looks like you have something for read-only role? | 16:22 |
| ayoung | so...sort of | 16:22 |
| ayoung | it is more than just that | 16:22 |
| kmalloc | quick backtrack, caching is questionable in a couple ways for py3 | 16:22 |
| kmalloc | just fyi | 16:22 |
| kmalloc | it will "work"... ish | 16:22 |
| kmalloc | i need to revisit pymemcache | 16:22 |
| *** d0ugal has joined #openstack-meeting-alt | 16:23 | |
| kmalloc | ok we can move on for read-only role. | 16:23 |
| ayoung | Actually, lets go in order | 16:23 |
| ayoung | unscoped token...short question | 16:23 |
| ayoung | I need to firgure out what to populate in that service catalog | 16:23 |
| ayoung | tests do all uuids, even for names, | 16:24 |
| *** yamahata has quit IRC | 16:24 | |
| ayoung | so I can't just strip out all but 'identity' service | 16:24 |
| ayoung | which is what I was origianlly planning on doing | 16:24 |
| ayoung | talked it over with jamie last night: | 16:24 |
| ayoung | we don't foresee anything in the catalog for unscoped tokens but the identity services | 16:24 |
| kmalloc | have services (e.g. nova) fixed thier requirement for a project id in the path? | 16:24 |
| kmalloc | because i know that was an initiative | 16:24 |
| kmalloc | for a while | 16:24 |
| lbragstad | i don't think nova uses the project id in the path anymore | 16:25 |
| ayoung | does that apply here? | 16:25 |
| lbragstad | cinder does though | 16:25 |
| lbragstad | wxy| opened a bug for that with system-scope | 16:25 |
| ayoung | this is unscoped catalog only, so no cinder or nova uin the catalog anyway | 16:25 |
| ayoung | different subject | 16:25 |
| ayoung | what I need to implement is the way to extend access to the catalog API to get the right catalog for unscoped tokens | 16:26 |
| kmalloc | right, but if we get to the point we're not substituting in projects into the catalog paths... | 16:26 |
| ayoung | I'd like it to be something cacheable, | 16:26 |
| kmalloc | we can render the same catalog | 16:26 |
| kmalloc | and not care. | 16:26 |
| ayoung | got it | 16:26 |
| kmalloc | :) | 16:27 |
| ayoung | so, I was thinking this might be a new (python) API call against the catalog backend | 16:27 |
| ayoung | but... | 16:27 |
| ayoung | we don't hardcode "identity" anywhere | 16:27 |
| ayoung | so...should that be a config option? | 16:27 |
| kmalloc | hm. no. | 16:27 |
| ayoung | like "unscoped_token_services": [identity] | 16:27 |
| ayoung | then...what is the "right" way in our world? | 16:28 |
| kmalloc | you can extend the service data in the api | 16:28 |
| kmalloc | and add "unscoped_token_service: true" as optional | 16:28 |
| ayoung | I can do that | 16:28 |
| kmalloc | this isn't config, this is system management | 16:28 |
| ayoung | I wonder.... | 16:28 |
| kmalloc | so it should be something done in the api | 16:28 |
| ayoung | so, I had a spec for "subcatalogs by id" | 16:28 |
| ayoung | could "unscoped" be an id | 16:29 |
| ayoung | and we define that as the identity services? | 16:29 |
| kmalloc | you could just use the current API | 16:29 |
| ayoung | https://review.openstack.org/#/c/160909/ | 16:29 |
| kmalloc | or you could add a new route, auth/catalog/unscoped | 16:29 |
| kmalloc | you will need to inspect endpoints and any endpoints that have project/other subst in them will be omitted from the catalog | 16:30 |
| kmalloc | but i think this is pretty straightforward | 16:30 |
| *** apetrich has joined #openstack-meeting-alt | 16:30 | |
| *** tssurya has joined #openstack-meeting-alt | 16:31 | |
| kmalloc | and we can start with the default (aka bootstrap) populating the unscoped flag for keystone | 16:31 |
| ayoung | OK I think I got it. I might add that approach to the spec | 16:31 |
| ayoung | we can discuss it there, as I think it will be a big enough change that will merit API level review | 16:32 |
| lbragstad | ++ | 16:32 |
| lbragstad | anything else on your specs ayoung ? | 16:32 |
| kmalloc | ++ | 16:32 |
| ayoung | lets move my policy stuff to the end | 16:32 |
| lbragstad | ok | 16:32 |
| lbragstad | #topic federated auto-provision improvements | 16:33 |
| *** openstack changes topic to "federated auto-provision improvements (Meeting topic: keystone)" | 16:33 | |
| kmalloc | yay! | 16:33 |
| ayoung | when is the edge call? | 16:33 |
| ayoung | I'll get it on my calendar | 16:33 |
| kmalloc | iirc 7am pacfic, so... 1400 utc? | 16:33 |
| *** diablo_rojo has joined #openstack-meeting-alt | 16:33 | |
| lbragstad | so - james penick (from oath) has clearance to open-source their federated auto-provisioning stuff | 16:33 |
| kmalloc | 10am eastern | 16:33 |
| kmalloc | i *think* | 16:34 |
| lbragstad | we were talking about it today on the edge call | 16:34 |
| kmalloc | woot. | 16:34 |
| lbragstad | #link https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings | 16:34 |
| kmalloc | that makes me happy | 16:34 |
| ayoung | yeah, 10 | 16:34 |
| lbragstad | yeah - no kidding | 16:34 |
| kmalloc | oath's approach is the correct direction to push | 16:34 |
| lbragstad | so - he asked if it would be ok if he wrote a spec highlighting the gaps between our implementation and theirs | 16:34 |
| kmalloc | this makes it much easier. | 16:34 |
| kmalloc | i would like that very much | 16:35 |
| kmalloc | we can evaluate from there how far we can push to that implementation without breaking API contracts | 16:35 |
| kmalloc | and what would need massaging | 16:35 |
| lbragstad | i think he wants some help with it and said that he can try and get something proposed this week | 16:35 |
| kmalloc | the spec is key, and as much detail as he can provide | 16:35 |
| ayoung | Probably worth making sure we are in sync going in to the summit, too | 16:35 |
| kmalloc | some of us can chip in for the code | 16:35 |
| lbragstad | but he was concerned that some of it would be "wrong" | 16:35 |
| lbragstad | or that we might reject parts of it | 16:36 |
| kmalloc | the only real rejection i would see is if it breaks API contracts | 16:36 |
| kmalloc | and we'd need to work around that in either case. | 16:36 |
| lbragstad | yeah - i'd just be curious to see the implementation and figure out the gaps, then go from there | 16:36 |
| kmalloc | based upon the edge work (and discussions), I can say I already err to the side of oath is doing it correctly | 16:37 |
| kmalloc | it is a question of how do we make it work without breaking anyone else [might be extended/new apis] in upstream | 16:37 |
| lbragstad | but - next week we're going to spend more time on it after james open-sources the code and proposes the specification | 16:37 |
| lbragstad | and that will happen during the edge call | 16:37 |
| kmalloc | cool. | 16:37 |
| kmalloc | i shall try to be there. | 16:37 |
| lbragstad | good deal | 16:37 |
| lbragstad | that's all i had for that topic | 16:37 |
| kmalloc | but 7am is rough because dogs/moring being started | 16:38 |
| lbragstad | any questions? | 16:38 |
| ayoung | I have the time blocked out. I'll also make sure the web meeting tool works | 16:38 |
| kmalloc | this is zoom, yes? | 16:38 |
| ayoung | yeah | 16:38 |
| lbragstad | correct | 16:38 |
| kmalloc | i think they finally have a web-only version | 16:38 |
| kmalloc | which works for me | 16:38 |
| kmalloc | vs segfaulting my browser | 16:38 |
| ayoung | Heh | 16:38 |
| ayoung | OK...policy? | 16:38 |
| lbragstad | yessir | 16:38 |
| lbragstad | #topic updated policy project | 16:39 |
| *** openstack changes topic to "updated policy project (Meeting topic: keystone)" | 16:39 | |
| kmalloc | my policy is i dislike policy | 16:39 |
| kmalloc | >.> | 16:39 |
| kmalloc | <.< | 16:39 |
| * kmalloc couldn't resist | 16:39 | |
| ayoung | Last week, we had a big internal RH conference, and I met a couple people that are doing custom policy for some of our customers | 16:39 |
| ayoung | specifically in search of a read only role. THey had it in an internal git repo. | 16:39 |
| ayoung | So...I had long had and idea like this on my todo list, but they actually did it. | 16:39 |
| ayoung | I want to make this project "short term official" | 16:40 |
| ayoung | meaning, eventually all the changes should make their way back to the proejcts | 16:40 |
| ayoung | but in the meanwhile, we should have a unified set of policy files that people can use to enforce best practices | 16:40 |
| lbragstad | does this conflict with the default roles work or system scope/ | 16:40 |
| ayoung | I think it complements it | 16:40 |
| lbragstad | or is it a bandaid until that problem is fully fixed? | 16:41 |
| ayoung | lbragstad, bigger than a band aid. More like an iron lung | 16:41 |
| ayoung | Lets call it a cast and crutches? | 16:41 |
| lbragstad | ok | 16:41 |
| ayoung | I want to get a set of policies that we can use with TripleO, but...I think this group understands policy better | 16:42 |
| ayoung | here is what I have so far: | 16:42 |
| ayoung | #link https://pagure.io/openstack-access-policy/tree/common-rules | 16:42 |
| ayoung | the master branch is what they have for osp13 | 16:43 |
| ayoung | I took that and put a mini build system that lets us manage common rules, and built the policy.yaml files with the common sections pre-pended | 16:43 |
| ayoung | It needs tests, like, desperately | 16:43 |
| ayoung | once I can confirm that we can change the structure of the tests, but still keep things functioning, I want to start working toward mitigation for but 968696 | 16:44 |
| ayoung | that means first is_admin_project support | 16:44 |
| ayoung | and then service scoping | 16:44 |
| kmalloc | so, i have a single concern | 16:44 |
| lbragstad | so - i'm already working on tests for system-scope and project-scope support | 16:45 |
| ayoung | I don't think we have service scoping in OSP 13. If we do, I'll skip is_admin_project | 16:45 |
| kmalloc | i dislike "official" projects that are just in place to be deconstructed and deleted long term | 16:45 |
| kmalloc | it's ... not a huge concern | 16:45 |
| ayoung | lbragstad, so, my idea here for tests is to use the oslopolicy-checker and a score card | 16:45 |
| kmalloc | just a "I don't like the hoops to just puill it apart" | 16:45 |
| hrybacki | I will confirm that casts have their place | 16:45 |
| ayoung | kmalloc, I hear you, but I also have no longer the will to try and get changes into every project out there | 16:46 |
| ayoung | this needs to happen in a much faster time line | 16:46 |
| kmalloc | and i am not saying i object to this project at all | 16:46 |
| ayoung | it will be an official project. Just..not sure who will hold the office | 16:46 |
| kmalloc | just voicing the general "this feels icky" concern. | 16:46 |
| ayoung | I can see there being a long term project for the common rules | 16:46 |
| kmalloc | which sometimes ick is needed to get from A to B | 16:46 |
| kmalloc | (just detouring a->i->c->k->y->b) ;) | 16:47 |
| ayoung | and, then the build system might be to pull the project specific rules from the projects to build the overall policy...or a common library that the projects pull in if we want them to have the definitiev rules in code | 16:47 |
| ayoung | this gives us a place to work | 16:47 |
| *** panda is now known as panda|off | 16:48 | |
| ayoung | actually, since we put the rules in code, we really should have a common python library for common rules | 16:48 |
| lbragstad | that would be oslo-policy imo | 16:48 |
| ayoung | not quite | 16:48 |
| ayoung | oslo-policy is a rules engine | 16:48 |
| ayoung | but , with the exception of the roles check, it is agnostic of content | 16:48 |
| *** cloudrancher has quit IRC | 16:48 | |
| ayoung | this would be oslo-rbac or something like that | 16:48 |
| kmalloc | this could be like the vendor data in sdk | 16:49 |
| ayoung | yep | 16:49 |
| kmalloc | something that could be extracted from policy eventually | 16:49 |
| kmalloc | it might belong in olso-policy to start, for ease of deployment | 16:49 |
| kmalloc | and access | 16:49 |
| kmalloc | that way it's available to everyone to start | 16:49 |
| ayoung | we should probably namespace the common rules, then | 16:49 |
| ayoung | common:is_admin etc | 16:49 |
| kmalloc | that is in line with the consistent policy names lbragstad has proposed | 16:50 |
| kmalloc | and i support namespacing common rules in a similar/consistent way | 16:50 |
| lbragstad | merged* | 16:50 |
| ayoung | https://bugs.launchpad.net/oslo.policy/+bug/1797739 | 16:51 |
| openstack | Launchpad bug 1797739 in oslo.policy "checker CLI does not enumerate all rules for glance" [Undecided,In progress] - Assigned to Adam Young (ayoung) | 16:51 |
| ayoung | that is what happens without namespacing | 16:51 |
| lbragstad | #link https://docs.openstack.org/oslo.policy/latest/user/usage.html#naming-policies | 16:51 |
| lbragstad | ayoung glance doesn't have policy in code | 16:51 |
| ayoung | thay also don' | 16:51 |
| ayoung | they also don't have namespacing of their rules. | 16:51 |
| lbragstad | #link https://review.openstack.org/#/c/501360/ needs to get picked back up | 16:52 |
| kmalloc | tl;dr: namespace is consistent with the new "policy" for naming-policies. common rules should also be namespaced | 16:52 |
| ayoung | so...I don't think this set of policy files/build belongs in oslo.policy, but I am willing to post it there if I get support for it from the rest of the team | 16:52 |
| kmalloc | my only reasoning is for initial accessibility to the data | 16:53 |
| *** yamahata has joined #openstack-meeting-alt | 16:53 | |
| kmalloc | if we are adding yet-another-thing, it is something that has to be added everywhere | 16:53 |
| kmalloc | just trying to make your life easier. | 16:53 |
| kmalloc | but if you want the harder route, by all means, propose it as a new thing :) | 16:54 |
| lbragstad | ^ that's why i suggested it being in oslo.policy :) | 16:54 |
| * kmalloc ^5's lbragstad ;) | 16:54 | |
| lbragstad | (five minutes remaining) | 16:54 |
| ayoung | ok...let me rethink how to structure it, so it fits in. I guess a subdir, parallel to oslo-policy named...examples? | 16:55 |
| ayoung | It feels wrong to call them examples, as they are supposed to be more production than that | 16:55 |
| lbragstad | is their main purpose to be referenced or consumed? | 16:55 |
| ayoung | consumed | 16:55 |
| lbragstad | +1 | 16:55 |
| ayoung | common? | 16:55 |
| kmalloc | i have one quick last thing before end of meeting | 16:55 |
| lbragstad | then i'd think it's a sub-dir in oslo | 16:55 |
| ayoung | OK...I'll try to come up with a name | 16:56 |
| lbragstad | but arguable within oslo.policy | 16:56 |
| lbragstad | kmalloc go ahead? | 16:56 |
| kmalloc | flask -> Final patches proposed. There are 3 more "change the code" and some moving data, and then a lot of deleting. Please review. it's all done except for merging the last ~10 patches | 16:56 |
| ayoung | w00T! | 16:56 |
| lbragstad | #topic open discussion | 16:56 |
| *** openstack changes topic to "open discussion (Meeting topic: keystone)" | 16:56 | |
| kmalloc | the last one is -1800+ lines. | 16:56 |
| kmalloc | yes it felt good. | 16:57 |
| gagehugo | lol | 16:57 |
| kmalloc | +240, -1829 | 16:57 |
| vishakha | lbragstad: since its a open discussion now. I have some queries regarding unified limits | 16:57 |
| lbragstad | vishakha go ahead | 16:57 |
| kmalloc | vishakha: 2min, if it doesn't sneak in we can discuss in -keystone right after | 16:57 |
| * lbragstad notes that it's super late in japan | 16:58 | |
| vishakha | lbragstad: I got your point for keeping -1 as min for limits | 16:58 |
| vishakha | lbragstad: what can be the max value set for default or resorce limit | 16:58 |
| lbragstad | i think that depends on the deployer | 16:59 |
| lbragstad | they should be able to set that to whatever they want | 16:59 |
| vishakha | lbragstad: if I tries to set limit for around 1000000000 it gives me 500 server error | 16:59 |
| lbragstad | so i'm not sure we should implement an upper bound, if that's what you're asking | 16:59 |
| vishakha | yes exactly | 16:59 |
| kmalloc | the upper bound should be defined as what we expect the column length to be | 16:59 |
| lbragstad | yeah - which would be an implementation detail of sql | 17:00 |
| kmalloc | so if we specify a unit32, it is the upper limit | 17:00 |
| kmalloc | so we specify the defined limit as what we use for storage in the initial impl | 17:00 |
| lbragstad | we can gracefully handle that, but that's about the best we could do i think | 17:00 |
| kmalloc | pick a number that is within the limit and mark it as upperlimit | 17:00 |
| kmalloc | 500 error is not correct behavior imo | 17:00 |
| vishakha | ok . So will raise a bug for it | 17:00 |
| kmalloc | yeah | 17:00 |
| lbragstad | vishakha anything else on limits? | 17:01 |
| kmalloc | should be a bug and Bad Request/Validation error if it exceeds the limit | 17:01 |
| vishakha | Yeah one last thing I can set anything for resource name also? | 17:01 |
| lbragstad | yes | 17:01 |
| *** jesusaur has quit IRC | 17:02 | |
| vishakha | I mean when II tries to list limit for invalid resource name it dont give any error | 17:02 |
| lbragstad | we don't implement a set of resource - those are open-ended for service developers and operators to define | 17:02 |
| vishakha | It lists all the limits | 17:02 |
| kmalloc | there is again a length max on that data | 17:02 |
| kmalloc | but otherwise no special nameing requirements | 17:02 |
| lbragstad | vishakha i believe that is a filtering bug with query parameters GET /v3/limits?resource_name=foobars | 17:03 |
| lbragstad | returns all limits | 17:03 |
| lbragstad | because the query parameter is ignored since it doesn't exist | 17:03 |
| vishakha | ok got it. Thanks this much for now in unified limits | 17:04 |
| kmalloc | and that is correct behavior in keystone. | 17:04 |
| lbragstad | vishakha thanks for jumping in and helping out | 17:04 |
| lbragstad | thanks for coming everyone, good discussions today | 17:04 |
| lbragstad | #endmeeting | 17:04 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 17:04 | |
| openstack | Meeting ended Tue Oct 16 17:04:18 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:04 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-10-16-16.00.html | 17:04 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-10-16-16.00.txt | 17:04 |
| kmalloc | well consistent behavior* | 17:04 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-10-16-16.00.log.html | 17:04 |
| *** kopecmartin|ruck is now known as kopecmartin|off | 17:05 | |
| *** wxy| has quit IRC | 17:07 | |
| *** e0ne has joined #openstack-meeting-alt | 17:08 | |
| *** munimeha1 has quit IRC | 17:10 | |
| *** panda|off has quit IRC | 17:24 | |
| *** panda has joined #openstack-meeting-alt | 17:27 | |
| *** rdopiera has quit IRC | 17:50 | |
| *** e0ne has quit IRC | 17:59 | |
| *** clone99 has joined #openstack-meeting-alt | 18:02 | |
| *** diablo_rojo has quit IRC | 18:03 | |
| *** SimAloo has quit IRC | 18:05 | |
| *** diablo_rojo has joined #openstack-meeting-alt | 18:10 | |
| *** bhavikdbavishi has quit IRC | 18:11 | |
| *** e0ne has joined #openstack-meeting-alt | 18:15 | |
| *** gyee has joined #openstack-meeting-alt | 18:19 | |
| *** e0ne has quit IRC | 18:22 | |
| *** tssurya has quit IRC | 18:52 | |
| *** tsmith_ has joined #openstack-meeting-alt | 19:12 | |
| *** tsmith_ has quit IRC | 19:12 | |
| *** tsmith2 has quit IRC | 19:14 | |
| *** tsmith2 has joined #openstack-meeting-alt | 19:17 | |
| *** weshay has joined #openstack-meeting-alt | 19:24 | |
| *** raildo has quit IRC | 19:46 | |
| *** rmart04 has joined #openstack-meeting-alt | 20:05 | |
| *** rmart04 has quit IRC | 20:06 | |
| *** macza has quit IRC | 20:25 | |
| *** macza_ has joined #openstack-meeting-alt | 20:25 | |
| *** macza_ has quit IRC | 20:28 | |
| *** macza has joined #openstack-meeting-alt | 20:29 | |
| *** macza has quit IRC | 20:31 | |
| *** macza has joined #openstack-meeting-alt | 20:32 | |
| *** slaweq has quit IRC | 20:33 | |
| *** gagehugo has left #openstack-meeting-alt | 20:46 | |
| *** jesusaur has joined #openstack-meeting-alt | 20:48 | |
| *** erlon has quit IRC | 20:48 | |
| *** priteau has quit IRC | 20:57 | |
| *** priteau has joined #openstack-meeting-alt | 21:01 | |
| *** munimeha1 has joined #openstack-meeting-alt | 21:05 | |
| *** clone99 is now known as SimAloo | 21:29 | |
| *** SimAloo has quit IRC | 21:34 | |
| *** lbragstad is now known as lbragstad-503 | 21:42 | |
| *** munimeha1 has quit IRC | 21:45 | |
| *** slaweq has joined #openstack-meeting-alt | 21:53 | |
| *** priteau has quit IRC | 22:03 | |
| *** slaweq has quit IRC | 22:09 | |
| *** slaweq has joined #openstack-meeting-alt | 22:11 | |
| *** timothyb89 has joined #openstack-meeting-alt | 22:30 | |
| *** pbourke has quit IRC | 22:35 | |
| *** pbourke has joined #openstack-meeting-alt | 22:35 | |
| *** slaweq has quit IRC | 22:44 | |
| *** rcernin has joined #openstack-meeting-alt | 22:49 | |
| *** macza has quit IRC | 23:01 | |
| *** hongbin has quit IRC | 23:07 | |
| *** slaweq has joined #openstack-meeting-alt | 23:11 | |
| *** slaweq has quit IRC | 23:44 | |
| *** erlon has joined #openstack-meeting-alt | 23:55 | |
| *** cloudrancher has joined #openstack-meeting-alt | 23:56 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!