15:00:07 #startmeeting craton 15:00:08 Meeting started Mon Dec 12 15:00:07 2016 UTC and is due to finish in 60 minutes. The chair is jimbaker. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:11 The meeting name has been set to 'craton' 15:01:21 sigmavirus, sulo, toan, o/ 15:01:47 git-harry, o/ 15:03:42 o/ 15:04:26 How goes it, jimbaker ? 15:05:03 sigmavirus, it is going very well, thanks. i had a nice weekend of hiking, some inside bouldering, and first attempt at slacklining 15:06:09 by next weekend, the snow depth should get high enough to start opening up a lot of skiing, just in time for vacation :) 15:06:19 sigmavirus, yourself? 15:06:40 Can't complain 15:06:41 and thanks for your spec review on url design 15:07:08 Syed__, hi 15:08:50 jimbaker: just trying to get something written down around that. We seem to be doing whatever strikes us as preferable at the moment, and I'd like that to stop because we seem to burn dev cycles that way 15:09:51 sigmavirus, i thought we had reached agreement based on what git-harry had proposed. (as in, keep it flat.) but writing it down is definitely the best 15:10:12 sulo, are you around? 15:11:28 jimbaker: you reached consensus in an unrecorded meeting without git-harry and myself (who seem to be the only people with differing opinions) so no justification was documented. Just the decision, in a gerrit comment, was written down somewhere 15:11:54 hi jim 15:11:54 I'm relitigating this only so we can document our justifications 15:12:21 sigmavirus, sure, and i have no problem with the religitation 15:13:27 I'm not as concerned with what we choose, so long as we can all agree on why :) 15:15:11 sigmavirus, i was always uncomfortable with the region_id being required. relaxing that constraint seemed to make a lot of sense. there is a natural hierarchy in terms of DC layout, but it's not necessary how one wants to get at things 15:15:32 jimbaker: let's keep the reasoning on the spec? 15:15:50 #link https://review.openstack.org/409281 15:15:51 sigmavirus, sure 15:16:21 and it can be done async as well, which is good considering we are missing git-harry, sulo this moment 15:16:27 #info That link is to a specification that will explain our choice of URL structure/semantics. Please review and contribute to the design and discussion 15:16:31 jimbaker: right 15:16:38 This is why I like gerrit specs :) 15:16:47 I'm here 15:17:12 sigmavirus, better process is a good thing 15:18:00 #topic week planning 15:18:12 i will go first 15:19:19 i have 3 blueprints i'm working on. rbac is more or less complete, but needs to move into the new gerrit review spec process. i also have some supporting code for implementing scoped role assignments, which is the key piece of the modeling that is craton specific 15:19:44 the other blueprints are for secrets and virtualized variables 15:21:22 re supporting code, i have done a bit of work also cleaning up the alembic migration so it has a more parallel implementation to the model code in models.py, which i think is important for helping keep things consistent/understandable 15:21:39 so that's what i'm working on. i have no blockers 15:22:09 Cool. 15:22:14 I will go next 15:22:21 Syed__, thanks 15:22:39 i have an review out there for network unit tests, whenever you guys get time kindly review that 15:23:11 will take more bugs from launchpad this week, 15:23:57 jimbaker: regarding rbac 15:24:27 ? 15:24:47 are we able to get oslo.policy rules set up in rbac, or is this more or less regarding enforcing key rules for accessibility 15:26:03 Syed__, so my expectation is that oslo.policy provides the logic that actually makes usable the scoped role assignments. nothing i'm doing should conflict 15:26:30 cool 15:26:44 waiting for that to be in the queue :) 15:26:47 unfortunately that is some serious handwaving. the real answer is 15:27:16 to demonstrate some appropriate integrating rules from oslo.policy 15:27:21 hmm 15:27:34 will be looking into it in depth 15:27:52 thats all from my side 15:28:09 remember: the whole point of the scoped role assignments is to keep in the database what should be in the db; and to minimize the overhead of setting up by using our exisitng support for scoping 15:28:25 Syed__, thanks 15:28:36 sigmavirus, you want to go next? 15:31:49 or we can just keep this meeting short 15:32:03 git-harry, any updates on your side? 15:32:36 sorry, had a heavy package arrive 15:32:59 not many updates on my side. I'll be pressing folks for justification on the URL spec and working on caching & client stuff 15:33:45 sigmavirus, sounds good. such discussion will sharpen our implementation 15:33:49 a lot of what I was doing is now blocked by the url spec, there are several dependant patches. I'm not going to try and unwind them, I'll just wait for the outcome of that spec. 15:34:14 I'll probably dig up something else to do in the meantime. 15:34:21 git-harry, ok, so we need to conclude soon that discussion 15:35:00 sigmavirus, i assume the spec + review is capturing the impact on the client, especially paging? 15:36:45 in the meantime, i will dive into the discussion 15:37:01 looks like we can have an early end for today's meeting. but first 15:37:58 git-harry, sigmavirus, will you be around on dec 19? we will not have a meeting on dec 26 regardless 15:38:09 I won't 15:38:58 ok, then let's cancel dec 19 as well 15:38:59 jimbaker: I think I will 15:39:02 wfm 15:39:08 jimbaker: want me to send that to the ML? 15:39:15 sigmavirus, sounds good 15:39:27 #action sigmavirus to send message to openstack-dev cancelling next two meetings 15:39:38 so today is the last irc meeting of the year. happy holidays everyone! 15:39:58 Happy New Year, y'all! 15:40:05 please take a look at the url spec discussion, and weigh in. especially if you have questions - i know i do! 15:40:26 #endmeeting