[kolla-ansible][horizon][keystone] policy.yaml/json files
bkslash at poczta.onet.pl
Tue Mar 30 13:40:47 UTC 2021
(horizon)[root at controller1 /]# cd /etc/openstack-dashboard/
(horizon)[root at controller1 openstack-dashboard]# ls -la
drwxr-xr-x 1 horizon horizon 186 Mar 30 13:17 .
drwxr-xr-x 1 root root 59 Mar 30 12:56 ..
-rw-r--r-- 1 horizon horizon 8560 Feb 7 08:13 cinder_policy.json
-rw------- 1 horizon horizon 301 Mar 30 13:17 custom_local_settings
-rw-r--r-- 1 horizon horizon 1388 Feb 7 08:13 glance_policy.json
-rw-r--r-- 1 root root 4544 Feb 7 08:14 heat_policy.json
-rw-r--r-- 1 horizon horizon 10144 Feb 7 08:13 keystone_policy.json
-rw------- 1 horizon horizon 29710 Mar 30 13:17 local_settings
-rw-r--r-- 1 root root 395 Feb 7 08:14 masakari_policy.json
-rw-r--r-- 1 horizon horizon 12580 Feb 7 08:13 neutron_policy.json
drwxr-xr-x 2 horizon horizon 33 Feb 7 08:13 nova_policy.d
-rw------- 1 horizon horizon 269 Mar 30 13:17 nova_policy.json
-rw-r--r-- 1 root root 1268 Feb 7 08:14 senlin_policy.json
-rw-r--r-- 1 root root 1138 Feb 7 08:14 watcher_policy.json
(horizon)[root at controller1 openstack-dashboard]# cat nova_policy.json
So the file with overrides is properly placed inside horizon container. And the above policy should prevent non-admin user from starting/stopping instances and showing the console and… it does not work. Still as regular user I’m able to start and stop all instances in project from Horizon GUI. If the policy is in horizon configuration then it should work from horizon dashboard (without the same policy in nova it should be still possible to start/stop instances from CLI).
> Wiadomość napisana przez Mark Goddard <mark at stackhpc.com> w dniu 30.03.2021, o godz. 12:51:
> On Tue, 30 Mar 2021 at 10:52, Adam Tomas <bkslash at poczta.onet.pl> wrote:
>> thank you for the answers, but I still have more questions :)
>> Without any custom policies when I look inside the horizon container I see (in /etc/openstack-dashboard) current/default policies. If I override (for example keystone_policy.json) with a file placed in /etc/kolla/config/horizon which contains only 3 rules, then after kolla-ansible reconfigure inside horizon container there is of course keystone_police.json file, but only with my 3 rules - should I assume, that previously seen default rules (other than the ones overridden by my rules) still works, whether I see them in the file or not?
> I'd assume Horizon works in the same way as other services, and you
> only need to include changes. Please test and report back.
>> And another question - I need a rule, that will allow some „special” user (which I call project_admin) to see,create, update and delete users inside a project (but not elsewhere). How should the policy look like?
>> „project_admin_required”: „role:project_admin and default_project_id:%(target.project_id)s"
>> „identity:list_user”: „rule: admin_required or project_admin_required”
>> „identity:create_user”: „rule: admin_required or project_admin_required”
>> „identity:update_user”: „rule: admin_required or project_admin_required”
>> „identity:delete_user”: „rule: admin_required or project_admin_required”
> As I mentioned before, admin is global in OpenStack for now. There may
> be various ways to achieve what you want. One is to introduce a role,
> and use it in the rules. It's a bit of a can of worms though, since
> there are many API endpoints which might need to be updated to catch
> all corner cases. I added keystone to the subject, in case anyone from
> that team wants to comment.
>> Best regards,
>>> Wiadomość napisana przez Mark Goddard <mark at stackhpc.com> w dniu 30.03.2021, o godz. 11:05:
>>> On Tue, 30 Mar 2021 at 09:24, Mark Goddard <mark at stackhpc.com> wrote:
>>>> On Mon, 29 Mar 2021 at 15:36, Adam Tomas <bkslash at poczta.onet.pl> wrote:
>>>> Hi, Looks like we need some more/better docs on this in Kolla.
>>> Proposed some docs improvements:
>>>>> Im not quite clear about policy.yaml/json files in kolla-ansible. Let assume, that I need to allow one of project users to add other users to the project. So I create „project_admin” role and assign it to this user. Then I found /etc/kolla/keystone/policy.json.test file, which I use as template. There is rule „identity:create_credential” : „(role:admin and system_scope:all)” so I add „or role:project_admin” and put file in /etc/kolla/config/keystone/ and reconfigure kolla. And now few questions:
>>>>> 1. policy.json (or policy.yaml) always overwrite all default policies? I mean if I only add one rule to this file then other rules will „disappear” or will have default values? Is there any way to only overwrite some default rules and leave rest with defaults? Like with .conf files
>>>> For a few releases now, OpenStack supports policy in code. This means
>>>> that you only need to include the rules you want to override in your
>>>> JSON/YAML file.
>>>>> 2. what about Horizon and visibility of options? In mentioned case putting the same policy.json file in /etc/kolla/config/keystone/ and /etc/kolla/config/horizon/ should „unblock” Add User button for user with project_admin role? Or how to achieve it?
>>>> For keystone policy in horizon, you need to use:
>>>>> 3. does Horizon need the duplicated policy.json files from other services in it’s configuration folder or is it enough to write policy.json for services I want to change?
>>>> Only the ones you want to change.
>>>>> 4. when I assign admin role to a user with projectID (openstack role add —project PROJECT_ID —user SOME_USER admin) this user sees in Horizon everything systemwide, not only inside this project… Which rules should be created to allow him to see only users and resources which belongs to this project?
>>>> Currently admin is generally global in OpenStack. It's a known
>>>> limitation, and currently being worked on.
>>>>> Best regards
More information about the openstack-discuss