[openstack-dev] [horizon] Augmenting openstack_dashboard settings and possible horizon bug

Timur Sufiev tsufiev at mirantis.com
Wed Jan 29 16:59:21 UTC 2014


Thanks to the Ana Krivokapic's comment in
https://bugs.launchpad.net/horizon/+bug/1271151 I've found a typo in my
code, so it's not Horizon's bug but mine. So, the original approach I used
for augmenting openstack_dashboard settings (which is described in the
initial letter of this thread) works fine, and it's still more flexible
than a new Horizon's mechanism for adding separate dashboards settings, so
we'll stick to our approach. Just to keep you informed :).

Also, the thing that bothered me most when I thought about how Murano could
use this new Horizon's config facility, is changing DATABASES parameter
(muranodashboard app needs it to be set) - and more generally, resolving
conflicts when different dashboards change some common parameters (such as
DATABASES or SESSION_BACKEND) affecting all Django applications. Current
algorithm of determining which dashboard sets the actual value of a
parameter such as DATABASES seems unreliable to me in sense that it can
break other dashboards which failed to set this parameter to the value they
needed.


On Thu, Jan 16, 2014 at 1:57 PM, Timur Sufiev <tsufiev at mirantis.com> wrote:

> Radomir,
>
> it looks interesting indeed. I think Murano could use it in case several
> additional parameters were added. I will submit a patch with my ideas a bit
> later.
>
> One thing that seemed tricky to me in your patchset is determining which
> dashboard will actually be the default one, but I have yet no clue on how
> it could be made simpler using pluggable architecture.
>
>
> On Wed, Jan 15, 2014 at 6:57 PM, Radomir Dopieralski <
> openstack at sheep.art.pl> wrote:
>
>> On 15/01/14 15:30, Timur Sufiev wrote:
>> > Recently I've decided to fix situation with Murano's dashboard and move
>> > all Murano-specific django settings into a separate file (previously
>> > they were appended to
>> > /usr/share/openstack-dashboard/openstack_dashboard/settings.py). But, as
>> > I knew, /etc/openstack_dashboard/local_settings.py is for customization
>> > by admins and is distro-specific also - so I couldn't use it for
>> > Murano's dashboard customization.
>>
>> [snip]
>>
>> > 2. What is the sensible approach for customizing settings for some
>> > Horizon's dashboard in that case?
>>
>> We recently added a way for dashboards to have (some) of their
>> configuration provided in separate files, maybe that would be
>> helpful for Murano?
>>
>> The patch is https://review.openstack.org/#/c/56367/
>>
>> We can add more settings that can be changed, we just have to know what
>> is needed.
>>
>> --
>> Radomir Dopieralski
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> --
> Timur Sufiev
>



-- 
Timur Sufiev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140129/09fcaa8d/attachment.html>


More information about the OpenStack-dev mailing list