Open Stack

Thanks again. In kolla there is an option to completely disable Horizon’s Vitrage menu (in globals.yaml: enable_horizon_vitrage, which sets env variable disabling or enabling menu globally for all users), maybe policy will do the trick, but it requires a lot of testing, that’s why I was searching for quicker solution ;)

Best regards
Adam

> Wiadomość napisana przez Eyal B <eyalb1 at gmail.com> w dniu 27.04.2021, o godz. 09:26:
> 
> HI,
> 
> Vitrage is supposed to support multi-tenancy so the tenant in horizon should see only its own resources.
> Regarding horizon vitrage menu, I don't know, maybe you can write some code to horizon that can disable the vitrage menu for certain users. 
> You need to consult with the horizon guys for that if there is an option for that.
> 
> Eyal
> 
> On Tue, Apr 27, 2021 at 9:57 AM Adam Tomas <bkslash at poczta.onet.pl <mailto:bkslash at poczta.onet.pl>> wrote:
> Hi Eyal, thank you for your answer.
> So it’s pointless to install Vitrage in a region other than „parent” region :( Is there any way to prevent users (other than admin, let’s say with member role) from seeing „Vitrage” menu in Horizon?  If I put role:admin in horizon’s vitrage_policy.json file (for all options) would it make the Vitrage menu disappear for users other than admin?
> 
> Best regards,
> Adam
> 
>> Wiadomość napisana przez Eyal B <eyalb1 at gmail.com <mailto:eyalb1 at gmail.com>> w dniu 26.04.2021, o godz. 17:35:
>> 
>> Hi,
>> 
>> Currently Vitrage supports only one region to get the data from. The region is configured in vitrage.conf under section [service_credentials]
>> and is used by its clients to get the data
>> 
>> Eyal
>> 
>> On Mon, Apr 26, 2021 at 5:50 PM Adam Tomas <bkslash at poczta.onet.pl <mailto:bkslash at poczta.onet.pl>> wrote:
>> 
>> Hi,
>> after deploying Vitrage in multi region environment Horizon always uses first public Vitrage endpoint (I have one public endpoint in each region) regardless if I’m logged in first or second region. So in both regions I see exactly the same entity map, etc. (from the first region). When I disable this endpoint, Horizon uses next one - and again I see the same things in both regions but this time from the second region. Horizon should check in which region I’m logged in and display Vitrage data for that region - right? So what’s wrong?
>> 
>> Best regards
>> Adam Tomas
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210427/7d991c3d/attachment.html>