Hi Sam, can you describe a little bit the issues that you experienced with the policy files, and how you fixed them? In my test env for the upgrade to Liberty and using the policy files from Kilo and I'm also seeing some problems. For example operations that are not allowed by policy (ex: resize) are only caught at child cell level and not in the top api. So, the user doesn't see that the operation is forbidden. I still didn't dig into the issue, but I'm assuming it's something related with v2.1. thanks, Belmiro On Thu, Jun 16, 2016 at 7:28 AM, Sam Morrison <sorrison at gmail.com> wrote: > Now that policy files in nova Liberty apparently work I’m going through > the stock example one and see that there are duplicate entries in the > policy.json like > > compute:create:forced_host > os_compute_api:servers:create:forced_host > > Which one do I use to change who can do forced_host? both or a specific > one? > > Anyone have any ideas > > Cheers, > Sam > > > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160616/e9757c83/attachment.html>