| *** Syed__ has quit IRC | 01:25 | |
| *** VW has joined #craton | 02:26 | |
| *** VW has quit IRC | 02:30 | |
| *** rainya has joined #craton | 02:31 | |
| *** rainya has quit IRC | 02:31 | |
| *** tojuvone has quit IRC | 04:08 | |
| *** VW has joined #craton | 05:00 | |
| *** VW has quit IRC | 05:55 | |
| *** jovon has joined #craton | 06:14 | |
| *** tojuvone has joined #craton | 06:39 | |
| *** VW has joined #craton | 07:55 | |
| *** VW has quit IRC | 08:00 | |
| *** jovon has quit IRC | 08:40 | |
| *** VW has joined #craton | 14:45 | |
| *** VW has quit IRC | 14:48 | |
| *** VW has joined #craton | 14:48 | |
| *** Mudpuppy_ has joined #craton | 14:58 | |
| *** VW has quit IRC | 15:08 | |
| *** VW has joined #craton | 15:09 | |
| *** VW has quit IRC | 15:13 | |
| *** Mudpuppy_ has quit IRC | 15:13 | |
| *** VW has joined #craton | 15:13 | |
| *** Mudpuppy_ has joined #craton | 15:13 | |
| *** valw has joined #craton | 15:21 | |
| *** valw_ has joined #craton | 15:27 | |
| *** valw has quit IRC | 15:28 | |
| *** mudpuppy has quit IRC | 15:28 | |
| *** mudpuppy has joined #craton | 15:29 | |
| *** Syed__ has joined #craton | 15:53 | |
| *** valw_ has quit IRC | 16:08 | |
| *** valw has joined #craton | 16:09 | |
| *** valw has quit IRC | 16:30 | |
| *** valw has joined #craton | 16:36 | |
| *** valw has quit IRC | 16:59 | |
| *** VW has quit IRC | 17:10 | |
| *** VW has joined #craton | 17:11 | |
| *** VW has quit IRC | 17:16 | |
| *** VW has joined #craton | 17:22 | |
| *** VW_ has joined #craton | 17:48 | |
| *** VW_ has quit IRC | 17:49 | |
| *** VW_ has joined #craton | 17:49 | |
| *** VW has quit IRC | 17:51 | |
| *** VW_ has quit IRC | 18:20 | |
| *** VW has joined #craton | 18:22 | |
| *** VW has quit IRC | 18:22 | |
| *** VW has joined #craton | 18:23 | |
| *** valw has joined #craton | 18:33 | |
| sigmavirus | jimbaker: ping | 18:50 |
|---|---|---|
| *** hughsaunders has quit IRC | 19:36 | |
| *** d34dh0r53 has quit IRC | 19:36 | |
| *** hughsaunders has joined #craton | 19:36 | |
| *** d34dh0r53 has joined #craton | 19:36 | |
| *** valw has quit IRC | 19:36 | |
| *** valw has joined #craton | 19:37 | |
| jimbaker | sigmavirus, hey | 19:39 |
| sigmavirus | Have you looked at the spec that's up? | 19:45 |
| *** VW_ has joined #craton | 19:51 | |
| *** VW_ has quit IRC | 19:52 | |
| *** VW_ has joined #craton | 19:52 | |
| *** VW has quit IRC | 19:54 | |
| jimbaker | sigmavirus, i have | 19:54 |
| *** VW_ has quit IRC | 19:56 | |
| jimbaker | sigmavirus, so page/per_page or the similar limit/offset seems to correspond best to what sqlalchemy provides; i understand the motivation behind limit/marker, but i don't know how one implements the desired stability in general against our APIs without maintaining a cursor | 20:00 |
| jimbaker | so i'm certainly curious about that aspect | 20:01 |
| *** valw has quit IRC | 20:05 | |
| *** valw has joined #craton | 20:06 | |
| *** VW has joined #craton | 20:07 | |
| *** valw has quit IRC | 20:09 | |
| jimbaker | sigmavirus, here's one option, a project to help support limit/marker - https://github.com/djrobstep/sqlakeyset | 20:17 |
| jimbaker | checking if there's anything similar in oslo db | 20:17 |
| jimbaker | yes there is this: http://docs.openstack.org/developer/oslo.db/api/oslo_db.sqlalchemy.utils.html#oslo_db.sqlalchemy.utils.paginate_query | 20:18 |
| Syed__ | jimbaker: do you have some time to talk about oslo | 20:18 |
| jimbaker | sigmavirus, so my quick read here it is readily doable by working with arbitrary queries. nice. | 20:19 |
| jimbaker | Syed__, you mean olso.policy? | 20:19 |
| Syed__ | yeap for rbac support | 20:19 |
| sigmavirus | jimbaker: yeah, looks that way. Was researching it as we spoke | 20:19 |
| * sigmavirus knew it had to be in there somewhere | 20:19 | |
| jimbaker | got it. yeah, let me first get lunch | 20:19 |
| Syed__ | sure | 20:20 |
| Syed__ | thanks | 20:20 |
| jimbaker | so maybe we can discuss in about an hour. 2:30p MT? | 20:20 |
| Syed__ | Sounds good i.e. 3:30p SA time.. | 20:21 |
| Syed__ | sorry i really need to get the hang of mountain times, central times etc. | 20:21 |
| jimbaker | sigmavirus, cool. yeah i think that util function looks generally useful - we always have some guiding model we care about, vs some arbitrary vie | 20:21 |
| jimbaker | Syed__, yes, that's why we generally use UTC instead for open source ;) | 20:21 |
| jimbaker | then it complicates things for both parties, unless they live in iceland :_) | 20:22 |
| jimbaker | *arbitrary view* | 20:23 |
| jimbaker | ok, biab | 20:23 |
| sigmavirus | Syed__: yeah, we're 1hr ahead of mountatin time | 20:26 |
| *** VW has quit IRC | 20:26 | |
| sigmavirus | mountain time too ;) | 20:26 |
| *** VW has joined #craton | 20:27 | |
| *** valw has joined #craton | 20:47 | |
| jimbaker | Syed__, can we push this meeting out by an hour? my car was just fixed, and i want to get it home given the snow storm we are having | 21:27 |
| *** VW has quit IRC | 21:33 | |
| *** VW has joined #craton | 22:03 | |
| *** VW has quit IRC | 22:06 | |
| *** VW has joined #craton | 22:06 | |
| *** Mudpuppy_ has quit IRC | 22:17 | |
| Syed__ | sure, let me know whenever you are back jimbaker | 22:22 |
| *** VW has quit IRC | 22:40 | |
| *** valw has quit IRC | 22:42 | |
| *** VW has joined #craton | 22:44 | |
| *** VW has quit IRC | 22:51 | |
| *** VW has joined #craton | 22:51 | |
| *** openstack has joined #craton | 22:54 | |
| *** VW has quit IRC | 22:57 | |
| *** VW_ has quit IRC | 22:58 | |
| jimbaker | Syed__, back | 23:01 |
| jimbaker | Syed__, i love snow but it certainly delays things :) | 23:01 |
| Syed__ | haha, i hope you got your car back safe | 23:02 |
| jimbaker | just fine | 23:02 |
| Syed__ | jimbaker: yeap, so was going through http://docs.openstack.org/developer/oslo.policy/usage.html#migrating-to-oslo-policy | 23:03 |
| Syed__ | and making a policy file for oslo policy to be used for craton | 23:03 |
| jimbaker | ok | 23:03 |
| Syed__ | using this https://github.com/openstack/nova/blob/master/nova/policy.py as a reference | 23:03 |
| Syed__ | should we use nova to authenticate or how the authentication should be working is my question | 23:04 |
| jimbaker | Syed__, you mean keystone | 23:05 |
| Syed__ | and we also do need http://docs.openstack.org/kilo/config-reference/content/policy-json-file.html | 23:05 |
| Syed__ | oh sorry yeah keystone, so keystone is being used as authentication | 23:05 |
| jimbaker | Syed__, we can either use keystone or craton's authentication | 23:06 |
| Syed__ | Shouldn't we be using just keystone for this purpose ? | 23:06 |
| jimbaker | no, otherwise we don't have rbac for the scenario without keystone | 23:06 |
| jimbaker | that would be unacceptable imhop | 23:06 |
| jimbaker | imho | 23:06 |
| Syed__ | i see .. Okay so we need to make sure that authentication works with craton and keystone | 23:07 |
| jimbaker | yeah, this should be just fine | 23:07 |
| jimbaker | there's nothing in oslo.policy that depends directly on keystone | 23:07 |
| Syed__ | okay, and ones we have basic layout we can add user scenarios to test cases as they are in that blueprint | 23:07 |
| jimbaker | Syed__, i would look at the unit tests for oslo.policy in projects like cinder | 23:07 |
| Syed__ | Okay, yes i will go look that out right now | 23:08 |
| jimbaker | best bet: try stuff out in the python console | 23:08 |
| Syed__ | that is what i have been doing lately | 23:08 |
| jimbaker | you don't want anything that has more than a couple of imports | 23:08 |
| Syed__ | but thanks, will need to dig into how unit testing is done in other projects for oslo, will be doing that rn | 23:08 |
| jimbaker | want to make the scenario as simple as possible :) | 23:09 |
| Syed__ | cool, thanks | 23:09 |
| jimbaker | Syed__, i'm going to look at this with you a bit more today... one moment | 23:11 |
| Syed__ | should we hop into one of the vidyo rooms ? | 23:12 |
| *** VW has joined #craton | 23:14 | |
| jimbaker | Syed__, nahh, i think irc is much better here | 23:18 |
| *** VW has quit IRC | 23:18 | |
| jimbaker | video is overrated :) | 23:18 |
| jimbaker | much easier to discuss text when using text | 23:19 |
| Syed__ | i am looking at this https://github.com/openstack/cinder/blob/4962723c9a1da7d2a75e2b63eccb63619dac22b6/cinder/tests/unit/conf_fixture.py | 23:20 |
| jimbaker | Syed__, yeah, i'm looking for a better example | 23:21 |
| jimbaker | i should have made a better note of which test i found gave what i think is the best approach | 23:21 |
| jimbaker | i'm sure i will re-find momentarily! | 23:22 |
| jimbaker | Syed__, i guess it's in keystone after all. so take a look at https://github.com/openstack/keystone/blob/master/keystone/tests/unit/test_policy.py#L61 | 23:27 |
| jimbaker | despite being in keystone | 23:27 |
| jimbaker | 's test suite | 23:27 |
| jimbaker | it does not rely on any keystone setup | 23:27 |
| jimbaker | (after all, unit tests!) | 23:27 |
| Syed__ | looking | 23:28 |
| jimbaker | so some examples of rules, as set in self.rules | 23:28 |
| jimbaker | so may not be the best testing, because not comprehensive. it's possible that oslo.policy's own tests are better, but they are also fairly abstract about what is going on | 23:30 |
| jimbaker | but take a look at stuff like https://github.com/openstack/keystone/blob/master/keystone/tests/unit/test_policy.py#L118 | 23:31 |
| Syed__ | hmm | 23:31 |
| Syed__ | i looked into magnum policies as well, but i guess this is more helpful with what we want to be done | 23:34 |
| Syed__ | will be looking at this more | 23:34 |
| jimbaker | Syed__, so what you want to see here is: i have some credentials | 23:34 |
| jimbaker | and we forward chain to the desired target - or not | 23:38 |
| jimbaker | i guess the usual usage is http://docs.openstack.org/developer/oslo.policy/api/oslo_policy.html#oslo_policy.policy.Enforcer.authorize, but the tests here use enforce | 23:38 |
| jimbaker | probably no diff for unit testing | 23:38 |
| jimbaker | Syed__, i'm putting together a simple script based on what's in that keystone test | 23:49 |
| jimbaker | just so we can try things out without the distraction of keystone specifics | 23:50 |
| jimbaker | Syed__, one fun fact ;) is that the keystone.policy.backends.rules.enforce function switches the order of args compared to the method it wraps, oslo_policy.policy.Enforcer.enforce | 23:57 |
| jimbaker | just because it can... | 23:57 |
| jimbaker | no doubt keystone did it one way, and it just stuck | 23:58 |
| jimbaker | anyway, that's part of the simplification necessary here | 23:58 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!