Akihiro and James,
Thanks for your input.
I did suspect that “admin” role could be the issue, so I had tested that but
not in all ways. What I have found is this:
- Having a user that has had the admin role assignment but then the assignment
is removed, then using Horizon you will only see its own (and shared) networks.
But if you use the CLI (“openstack network list”) the list of presented
networks are still ALL.
- Creating a user from scratch without any admin role assignment, it will only
show its own (and shared networks) when using “openstack network list”. So
there seems to be some “caching” of the “role assignment”.
/Lars
On 2017-04-06, 22:48, "Akihiro Motoki" <amot...@gmail.com> wrote:
Do you use a user with admin role? If so this is the expected behavior
because Neutron returns all networks from all projects when admin role
is used.
2017-04-06 22:30 GMT+09:00 Lars-Erik Helander
<lars-erik.helan...@proceranetworks.com>:
> If I create networks in a project and define the networks to be
non-shared,
> I still can use these networks from other projects. Not via Horizon but
via
> the Openstack CLI commands (openstack, nova, neutron etc) and via Heat
(heat
> templates may refer to networks in other projects).
>
>
>
> Is this how it is supposed to be?
>
> Might I have misconfigured my Openstack in order to get this behaviour, if
> so any hints on where to look for the settings that causes the current
> behaviour?
>
>
>
> /Lars
>
>
> _______________________________________________
> Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
