Re: [openstack-dev] [horizon] [devstack] horizon 'network create' panel does not distinguished

2018-03-12 Thread Xinni Ge
Hello Jaewook and everyone,

I tried to install upstream/master Horizon+Heat-dashboard, still could not
see the error.
Maybe a clean installation of devstack could fix the issue.

If you want to enable heat-dashboard in current working environment, you
can try to install it manually.
I share my manual installation steps here, and you could also use it to
switch to any version or apply a patch.

1. update heat-dashboard
cd ~/heat-dashboard;
# Choose the version wanted
# download a particular patch by:
# git review -d ;
# or switch to any branch e.g. master by:
# git checkout master;

2. install heat-dashboard
# not necessarily needed, check if heat-dashboard is installed with `pip
list`
sudo pip install -e .

2. copy heat-dashboard settings to horizon
cp -rv ~/heat-dashboard/heat_dashboard/enabled
~/horizon/openstack_dashboard/local/
cp ~/heat-dashboard/heat_dashboard/local_settings.d/_1699_
orchestration_settings.py
 ~/horizon/openstack_dashboard/local/local_settings.d/
cp ~/heat-dashboard/heat_dashboard/conf/heat_policy.json
 ~/horizon/openstack_dashboard/conf/

3. let horizon re-collect static files, and compress
python manage.py collectstatic --clear
python manage.py compress

4. restart apache server
sudo service apache2 restart


Best Regards,
Xinni


On Tue, Mar 13, 2018 at 10:40 AM, Xinni Ge  wrote:

> Hello Jaewook,
>
> Very glad to know it.
> I will add comments to the bug report, and continue to find a better
> solution to prevent the issue from happening.
>
> Best Regards!
> Xinni
>
> On Tue, Mar 13, 2018 at 10:34 AM, Jaewook Oh  wrote:
>
>> Hello, Xinni.
>>
>> I followed your description, and it worked properly :)
>>
>> Can you comment your description in the bug report?
>>
>> https://bugs.launchpad.net/bugs/1755140
>>
>> It would be very helpful for me or somebody else who doesn't know how to
>> restart the horizon independently!
>>
>> Best Regards,
>> Jaewook.
>>
>> 2018-03-13 9:45 GMT+09:00 Xinni Ge :
>>
>>> Hello, Jaewook and everyone
>>>
>>> It looks like the error is caused by some angular module of
>>> heat-dashboard not being loaded correctly.
>>>
>>> I tried to reproduce it in my devstack by installing stable/queens
>>> Horiozn/Heat-dashboard, but couldn't see the same error.
>>>
>>> Maybe you want to try the following steps to restart web server and see
>>> if the issue can be fixed.
>>> Of course you can also remove the troubled panel in heat-dashboard, I
>>> will also describe how to do it as follows.
>>>
>>> 1. remove heat-dashboard related settings
>>> rm horizon/openstack_dashboard/local/enabled/_16*   # (particularly try
>>> to remove _1650_project_template_generator_panel.py to fix it)
>>> rm horizon/openstack_dashboard/local/local_settings.d/_1699_orc
>>> hestration_settings.py*
>>> rm horizon/openstack_dashboard/conf/heat_policy.json
>>>
>>> 2. let horizon re-collect static files, and compress
>>> python manage.py collectstatic --clear
>>> python manage.py compress
>>>
>>> 3. restart apache server
>>> sudo service apache2 restart
>>>
>>> Hope the problem can be solved and everything goes well.
>>> And if anybody see the same error, please share more details about it.
>>>
>>> Best Regards,
>>> Xinni
>>>
>>> On Mon, Mar 12, 2018 at 9:55 PM, Jaewook Oh  wrote:
>>>
 Thanks for feedback!

 As you said, I got errors in the JavaScript console.

 Below is the error log :

 3bf910c7ae4c.js:652 JQMIGRATE: Logging is active
 fddd6f634ef8.js:2299 Uncaught TypeError: Cannot read property 'layout'
 of undefined
 at Object.25../arrows (fddd6f634ef8.js:2299)
 at s (fddd6f634ef8.js:2252)
 at fddd6f634ef8.js:2252
 at Object.1../lib/dagre (fddd6f634ef8.js:2252)
 at s (fddd6f634ef8.js:2252)
 at e (fddd6f634ef8.js:2252)
 at fddd6f634ef8.js:2252
 at fddd6f634ef8.js:2252
 at fddd6f634ef8.js:2252
 25../arrows @ fddd6f634ef8.js:2299
 s @ fddd6f634ef8.js:2252
 (anonymous) @ fddd6f634ef8.js:2252
 1../lib/dagre @ fddd6f634ef8.js:2252
 s @ fddd6f634ef8.js:2252
 e @ fddd6f634ef8.js:2252
 (anonymous) @ fddd6f634ef8.js:2252
 (anonymous) @ fddd6f634ef8.js:2252
 (anonymous) @ fddd6f634ef8.js:2252
 3bf910c7ae4c.js:699 Uncaught Error: [$injector:modulerr] Failed to
 instantiate module horizon.app due to:
 Error: [$injector:modulerr] Failed to instantiate module
 horizon.dashboard.project.heat_dashboard.template_generator due to:
 Error: [$injector:nomod] Module 'horizon.dashboard.project.hea
 t_dashboard.template_generator' is not available! You either
 misspelled the module name or forgot to load it. If registering a module
 ensure that you specify the dependencies as the second argument.
 http://errors.angularjs.org/1.5.8/$injector/nomod?p0=horizon
 .dashboard.project.heat_dashboard.template_generator
 at 

Re: [openstack-dev] [horizon] [devstack] horizon 'network create' panel does not distinguished

2018-03-12 Thread Xinni Ge
Hello Jaewook,

Very glad to know it.
I will add comments to the bug report, and continue to find a better
solution to prevent the issue from happening.

Best Regards!
Xinni

On Tue, Mar 13, 2018 at 10:34 AM, Jaewook Oh  wrote:

> Hello, Xinni.
>
> I followed your description, and it worked properly :)
>
> Can you comment your description in the bug report?
>
> https://bugs.launchpad.net/bugs/1755140
>
> It would be very helpful for me or somebody else who doesn't know how to
> restart the horizon independently!
>
> Best Regards,
> Jaewook.
>
> 2018-03-13 9:45 GMT+09:00 Xinni Ge :
>
>> Hello, Jaewook and everyone
>>
>> It looks like the error is caused by some angular module of
>> heat-dashboard not being loaded correctly.
>>
>> I tried to reproduce it in my devstack by installing stable/queens
>> Horiozn/Heat-dashboard, but couldn't see the same error.
>>
>> Maybe you want to try the following steps to restart web server and see
>> if the issue can be fixed.
>> Of course you can also remove the troubled panel in heat-dashboard, I
>> will also describe how to do it as follows.
>>
>> 1. remove heat-dashboard related settings
>> rm horizon/openstack_dashboard/local/enabled/_16*   # (particularly try
>> to remove _1650_project_template_generator_panel.py to fix it)
>> rm horizon/openstack_dashboard/local/local_settings.d/_1699_orc
>> hestration_settings.py*
>> rm horizon/openstack_dashboard/conf/heat_policy.json
>>
>> 2. let horizon re-collect static files, and compress
>> python manage.py collectstatic --clear
>> python manage.py compress
>>
>> 3. restart apache server
>> sudo service apache2 restart
>>
>> Hope the problem can be solved and everything goes well.
>> And if anybody see the same error, please share more details about it.
>>
>> Best Regards,
>> Xinni
>>
>> On Mon, Mar 12, 2018 at 9:55 PM, Jaewook Oh  wrote:
>>
>>> Thanks for feedback!
>>>
>>> As you said, I got errors in the JavaScript console.
>>>
>>> Below is the error log :
>>>
>>> 3bf910c7ae4c.js:652 JQMIGRATE: Logging is active
>>> fddd6f634ef8.js:2299 Uncaught TypeError: Cannot read property 'layout'
>>> of undefined
>>> at Object.25../arrows (fddd6f634ef8.js:2299)
>>> at s (fddd6f634ef8.js:2252)
>>> at fddd6f634ef8.js:2252
>>> at Object.1../lib/dagre (fddd6f634ef8.js:2252)
>>> at s (fddd6f634ef8.js:2252)
>>> at e (fddd6f634ef8.js:2252)
>>> at fddd6f634ef8.js:2252
>>> at fddd6f634ef8.js:2252
>>> at fddd6f634ef8.js:2252
>>> 25../arrows @ fddd6f634ef8.js:2299
>>> s @ fddd6f634ef8.js:2252
>>> (anonymous) @ fddd6f634ef8.js:2252
>>> 1../lib/dagre @ fddd6f634ef8.js:2252
>>> s @ fddd6f634ef8.js:2252
>>> e @ fddd6f634ef8.js:2252
>>> (anonymous) @ fddd6f634ef8.js:2252
>>> (anonymous) @ fddd6f634ef8.js:2252
>>> (anonymous) @ fddd6f634ef8.js:2252
>>> 3bf910c7ae4c.js:699 Uncaught Error: [$injector:modulerr] Failed to
>>> instantiate module horizon.app due to:
>>> Error: [$injector:modulerr] Failed to instantiate module
>>> horizon.dashboard.project.heat_dashboard.template_generator due to:
>>> Error: [$injector:nomod] Module 'horizon.dashboard.project.hea
>>> t_dashboard.template_generator' is not available! You either misspelled
>>> the module name or forgot to load it. If registering a module ensure that
>>> you specify the dependencies as the second argument.
>>> http://errors.angularjs.org/1.5.8/$injector/nomod?p0=horizon
>>> .dashboard.project.heat_dashboard.template_generator
>>> at http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7
>>> ae4c.js:699:8
>>> at http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7
>>> ae4c.js:818:59
>>> at ensure (http://192.168.11.187/dashboa
>>> rd/static/dashboard/js/3bf910c7ae4c.js:816:320)
>>> at module (http://192.168.11.187/dashboa
>>> rd/static/dashboard/js/3bf910c7ae4c.js:818:8)
>>> at http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7
>>> ae4c.js:925:35
>>> at forEach (http://192.168.11.187/dashboa
>>> rd/static/dashboard/js/3bf910c7ae4c.js:703:400)
>>> at loadModules (http://192.168.11.187/dashboa
>>> rd/static/dashboard/js/3bf910c7ae4c.js:924:156)
>>> at http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7
>>> ae4c.js:925:84
>>> at forEach (http://192.168.11.187/dashboa
>>> rd/static/dashboard/js/3bf910c7ae4c.js:703:400)
>>> at loadModules (http://192.168.11.187/dashboa
>>> rd/static/dashboard/js/3bf910c7ae4c.js:924:156)
>>> http://errors.angularjs.org/1.5.8/$injector/modulerr?p0=hori
>>> zon.dashboard.project.heat_dashboard.template_generator=
>>> Error%3A%20%5B%24injector%3Anomod%5D%20Module%20'horizon.
>>> dashboard.project.heat_dashboard.template_generator'%
>>> 20is%20not%20available!%20You%20either%20misspelled%20the%
>>> 20module%20name%20or%20forgot%20to%20load%20it.%20If%
>>> 20registering%20a%20module%20ensure%20that%20you%
>>> 20specify%20the%20dependencies%20as%20the%20second%
>>> 

Re: [openstack-dev] [horizon] [devstack] horizon 'network create' panel does not distinguished

2018-03-12 Thread Jaewook Oh
Hello, Xinni.

I followed your description, and it worked properly :)

Can you comment your description in the bug report?

https://bugs.launchpad.net/bugs/1755140

It would be very helpful for me or somebody else who doesn't know how to
restart the horizon independently!

Best Regards,
Jaewook.

2018-03-13 9:45 GMT+09:00 Xinni Ge :

> Hello, Jaewook and everyone
>
> It looks like the error is caused by some angular module of heat-dashboard
> not being loaded correctly.
>
> I tried to reproduce it in my devstack by installing stable/queens
> Horiozn/Heat-dashboard, but couldn't see the same error.
>
> Maybe you want to try the following steps to restart web server and see if
> the issue can be fixed.
> Of course you can also remove the troubled panel in heat-dashboard, I will
> also describe how to do it as follows.
>
> 1. remove heat-dashboard related settings
> rm horizon/openstack_dashboard/local/enabled/_16*   # (particularly try
> to remove _1650_project_template_generator_panel.py to fix it)
> rm horizon/openstack_dashboard/local/local_settings.d/_1699_
> orchestration_settings.py*
> rm horizon/openstack_dashboard/conf/heat_policy.json
>
> 2. let horizon re-collect static files, and compress
> python manage.py collectstatic --clear
> python manage.py compress
>
> 3. restart apache server
> sudo service apache2 restart
>
> Hope the problem can be solved and everything goes well.
> And if anybody see the same error, please share more details about it.
>
> Best Regards,
> Xinni
>
> On Mon, Mar 12, 2018 at 9:55 PM, Jaewook Oh  wrote:
>
>> Thanks for feedback!
>>
>> As you said, I got errors in the JavaScript console.
>>
>> Below is the error log :
>>
>> 3bf910c7ae4c.js:652 JQMIGRATE: Logging is active
>> fddd6f634ef8.js:2299 Uncaught TypeError: Cannot read property 'layout' of
>> undefined
>> at Object.25../arrows (fddd6f634ef8.js:2299)
>> at s (fddd6f634ef8.js:2252)
>> at fddd6f634ef8.js:2252
>> at Object.1../lib/dagre (fddd6f634ef8.js:2252)
>> at s (fddd6f634ef8.js:2252)
>> at e (fddd6f634ef8.js:2252)
>> at fddd6f634ef8.js:2252
>> at fddd6f634ef8.js:2252
>> at fddd6f634ef8.js:2252
>> 25../arrows @ fddd6f634ef8.js:2299
>> s @ fddd6f634ef8.js:2252
>> (anonymous) @ fddd6f634ef8.js:2252
>> 1../lib/dagre @ fddd6f634ef8.js:2252
>> s @ fddd6f634ef8.js:2252
>> e @ fddd6f634ef8.js:2252
>> (anonymous) @ fddd6f634ef8.js:2252
>> (anonymous) @ fddd6f634ef8.js:2252
>> (anonymous) @ fddd6f634ef8.js:2252
>> 3bf910c7ae4c.js:699 Uncaught Error: [$injector:modulerr] Failed to
>> instantiate module horizon.app due to:
>> Error: [$injector:modulerr] Failed to instantiate module
>> horizon.dashboard.project.heat_dashboard.template_generator due to:
>> Error: [$injector:nomod] Module 'horizon.dashboard.project.hea
>> t_dashboard.template_generator' is not available! You either misspelled
>> the module name or forgot to load it. If registering a module ensure that
>> you specify the dependencies as the second argument.
>> http://errors.angularjs.org/1.5.8/$injector/nomod?p0=horizon
>> .dashboard.project.heat_dashboard.template_generator
>> at http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7
>> ae4c.js:699:8
>> at http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7
>> ae4c.js:818:59
>> at ensure (http://192.168.11.187/dashboa
>> rd/static/dashboard/js/3bf910c7ae4c.js:816:320)
>> at module (http://192.168.11.187/dashboa
>> rd/static/dashboard/js/3bf910c7ae4c.js:818:8)
>> at http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7
>> ae4c.js:925:35
>> at forEach (http://192.168.11.187/dashboa
>> rd/static/dashboard/js/3bf910c7ae4c.js:703:400)
>> at loadModules (http://192.168.11.187/dashboa
>> rd/static/dashboard/js/3bf910c7ae4c.js:924:156)
>> at http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7
>> ae4c.js:925:84
>> at forEach (http://192.168.11.187/dashboa
>> rd/static/dashboard/js/3bf910c7ae4c.js:703:400)
>> at loadModules (http://192.168.11.187/dashboa
>> rd/static/dashboard/js/3bf910c7ae4c.js:924:156)
>> http://errors.angularjs.org/1.5.8/$injector/modulerr?p0=hori
>> zon.dashboard.project.heat_dashboard.template_generator&
>> p1=Error%3A%20%5B%24injector%3Anomod%5D%20Module%20'
>> horizon.dashboard.project.heat_dashboard.template_generator'%20is%20not%
>> 20available!%20You%20either%20misspelled%20the%20module%
>> 20name%20or%20forgot%20to%20load%20it.%20If%20registerin
>> g%20a%20module%20ensure%20that%20you%20specify%20the%2
>> 0dependencies%20as%20the%20second%20argument.%0Ahttp%3A%2F%
>> 2Ferrors.angularjs.org%2F1.5.8%2F%24injector%2Fnomod%3Fp0%
>> 3Dhorizon.dashboard.project.heat_dashboard.template_
>> generator%0A%20%20%20%20at%20http%3A%2F%2F192.168.11.187%
>> 2Fdashboard%2Fstatic%2Fdashboard%2Fjs%2F3bf910c7ae4
>> c.js%3A699%3A8%0A%20%20%20%20at%20http%3A%2F%2F192.168.
>> 11.187%2Fdashboard%2Fstatic%2Fdashboard%2Fjs%2F3bf910c7ae4
>> 

Re: [openstack-dev] [horizon] [devstack] horizon 'network create' panel does not distinguished

2018-03-12 Thread Jaewook Oh
Hello Xinni, 
Thanks for your kind help and information.

I'll try what you said soon :)

By the way, I reported this issue in the bug report,
if anybody interested in it, please visit

https://bugs.launchpad.net/bugs/1755140 


Best Regards,
Jaewook.

Jaewook Oh (오재욱)
IISTRC - Internet Infra System Technology Research Center
369 Sangdo-ro, Dongjak-gu,
06978, Seoul, Republic of Korea

> 2018. 3. 13. 오전 9:45, Xinni Ge  작성:
> 
> Hello, Jaewook and everyone
> 
> It looks like the error is caused by some angular module of heat-dashboard 
> not being loaded correctly.
> 
> I tried to reproduce it in my devstack by installing stable/queens 
> Horiozn/Heat-dashboard, but couldn't see the same error.
> 
> Maybe you want to try the following steps to restart web server and see if 
> the issue can be fixed.
> Of course you can also remove the troubled panel in heat-dashboard, I will 
> also describe how to do it as follows.
> 
> 1. remove heat-dashboard related settings
> rm horizon/openstack_dashboard/local/enabled/_16*   # (particularly try to 
> remove _1650_project_template_generator_panel.py to fix it)
> rm 
> horizon/openstack_dashboard/local/local_settings.d/_1699_orchestration_settings.py*
> rm horizon/openstack_dashboard/conf/heat_policy.json
> 
> 2. let horizon re-collect static files, and compress
> python manage.py collectstatic --clear
> python manage.py compress
> 
> 3. restart apache server
> sudo service apache2 restart
> 
> Hope the problem can be solved and everything goes well.
> And if anybody see the same error, please share more details about it.
> 
> Best Regards,
> Xinni
> 
> On Mon, Mar 12, 2018 at 9:55 PM, Jaewook Oh  > wrote:
> Thanks for feedback!
> 
> As you said, I got errors in the JavaScript console.
> 
> Below is the error log : 
> 
> 3bf910c7ae4c.js:652 JQMIGRATE: Logging is active
> fddd6f634ef8.js:2299 Uncaught TypeError: Cannot read property 'layout' of 
> undefined
> at Object.25../arrows (fddd6f634ef8.js:2299)
> at s (fddd6f634ef8.js:2252)
> at fddd6f634ef8.js:2252
> at Object.1../lib/dagre (fddd6f634ef8.js:2252)
> at s (fddd6f634ef8.js:2252)
> at e (fddd6f634ef8.js:2252)
> at fddd6f634ef8.js:2252
> at fddd6f634ef8.js:2252
> at fddd6f634ef8.js:2252
> 25../arrows @ fddd6f634ef8.js:2299
> s @ fddd6f634ef8.js:2252
> (anonymous) @ fddd6f634ef8.js:2252
> 1../lib/dagre @ fddd6f634ef8.js:2252
> s @ fddd6f634ef8.js:2252
> e @ fddd6f634ef8.js:2252
> (anonymous) @ fddd6f634ef8.js:2252
> (anonymous) @ fddd6f634ef8.js:2252
> (anonymous) @ fddd6f634ef8.js:2252
> 3bf910c7ae4c.js:699 Uncaught Error: [$injector:modulerr] Failed to 
> instantiate module horizon.app due to:
> Error: [$injector:modulerr] Failed to instantiate module 
> horizon.dashboard.project.heat_dashboard.template_generator due to:
> Error: [$injector:nomod] Module 
> 'horizon.dashboard.project.heat_dashboard.template_generator' is not 
> available! You either misspelled the module name or forgot to load it. If 
> registering a module ensure that you specify the dependencies as the second 
> argument.
> http://errors.angularjs.org/1.5.8/$injector/nomod?p0=horizon.dashboard.project.heat_dashboard.template_generator
>  
> 
> at 
> http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:699:8 
> 
> at 
> http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:818:59 
> 
> at ensure 
> (http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:816:320 
> )
> at module 
> (http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:818:8 
> )
> at 
> http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:925:35 
> 
> at forEach 
> (http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:703:400 
> )
> at loadModules 
> (http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:924:156 
> )
> at 
> http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:925:84 
> 
> at forEach 
> (http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:703:400 
> 

Re: [openstack-dev] [horizon] [devstack] horizon 'network create' panel does not distinguished

2018-03-12 Thread Akihiro Motoki
The detail of this issue is tracked in
https://bugs.launchpad.net/bugs/1755140 and it turned out that it is caused
by the older version of the enabled file of the template generator.

I strongly recommend to cover this in the release notes.

Akihiro

2018/03/13 午前9:45 "Xinni Ge" :

> Hello, Jaewook and everyone
>
> It looks like the error is caused by some angular module of heat-dashboard
> not being loaded correctly.
>
> I tried to reproduce it in my devstack by installing stable/queens
> Horiozn/Heat-dashboard, but couldn't see the same error.
>
> Maybe you want to try the following steps to restart web server and see if
> the issue can be fixed.
> Of course you can also remove the troubled panel in heat-dashboard, I will
> also describe how to do it as follows.
>
> 1. remove heat-dashboard related settings
> rm horizon/openstack_dashboard/local/enabled/_16*   # (particularly try
> to remove _1650_project_template_generator_panel.py to fix it)
> rm horizon/openstack_dashboard/local/local_settings.d/_1699_
> orchestration_settings.py*
> rm horizon/openstack_dashboard/conf/heat_policy.json
>
> 2. let horizon re-collect static files, and compress
> python manage.py collectstatic --clear
> python manage.py compress
>
> 3. restart apache server
> sudo service apache2 restart
>
> Hope the problem can be solved and everything goes well.
> And if anybody see the same error, please share more details about it.
>
> Best Regards,
> Xinni
>
> On Mon, Mar 12, 2018 at 9:55 PM, Jaewook Oh  wrote:
>
>> Thanks for feedback!
>>
>> As you said, I got errors in the JavaScript console.
>>
>> Below is the error log :
>>
>> 3bf910c7ae4c.js:652 JQMIGRATE: Logging is active
>> fddd6f634ef8.js:2299 Uncaught TypeError: Cannot read property 'layout' of
>> undefined
>> at Object.25../arrows (fddd6f634ef8.js:2299)
>> at s (fddd6f634ef8.js:2252)
>> at fddd6f634ef8.js:2252
>> at Object.1../lib/dagre (fddd6f634ef8.js:2252)
>> at s (fddd6f634ef8.js:2252)
>> at e (fddd6f634ef8.js:2252)
>> at fddd6f634ef8.js:2252
>> at fddd6f634ef8.js:2252
>> at fddd6f634ef8.js:2252
>> 25../arrows @ fddd6f634ef8.js:2299
>> s @ fddd6f634ef8.js:2252
>> (anonymous) @ fddd6f634ef8.js:2252
>> 1../lib/dagre @ fddd6f634ef8.js:2252
>> s @ fddd6f634ef8.js:2252
>> e @ fddd6f634ef8.js:2252
>> (anonymous) @ fddd6f634ef8.js:2252
>> (anonymous) @ fddd6f634ef8.js:2252
>> (anonymous) @ fddd6f634ef8.js:2252
>> 3bf910c7ae4c.js:699 Uncaught Error: [$injector:modulerr] Failed to
>> instantiate module horizon.app due to:
>> Error: [$injector:modulerr] Failed to instantiate module
>> horizon.dashboard.project.heat_dashboard.template_generator due to:
>> Error: [$injector:nomod] Module 'horizon.dashboard.project.hea
>> t_dashboard.template_generator' is not available! You either misspelled
>> the module name or forgot to load it. If registering a module ensure that
>> you specify the dependencies as the second argument.
>> http://errors.angularjs.org/1.5.8/$injector/nomod?p0=horizon
>> .dashboard.project.heat_dashboard.template_generator
>> at http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7
>> ae4c.js:699:8
>> at http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7
>> ae4c.js:818:59
>> at ensure (http://192.168.11.187/dashboa
>> rd/static/dashboard/js/3bf910c7ae4c.js:816:320)
>> at module (http://192.168.11.187/dashboa
>> rd/static/dashboard/js/3bf910c7ae4c.js:818:8)
>> at http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7
>> ae4c.js:925:35
>> at forEach (http://192.168.11.187/dashboa
>> rd/static/dashboard/js/3bf910c7ae4c.js:703:400)
>> at loadModules (http://192.168.11.187/dashboa
>> rd/static/dashboard/js/3bf910c7ae4c.js:924:156)
>> at http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7
>> ae4c.js:925:84
>> at forEach (http://192.168.11.187/dashboa
>> rd/static/dashboard/js/3bf910c7ae4c.js:703:400)
>> at loadModules (http://192.168.11.187/dashboa
>> rd/static/dashboard/js/3bf910c7ae4c.js:924:156)
>> http://errors.angularjs.org/1.5.8/$injector/modulerr?p0=hori
>> zon.dashboard.project.heat_dashboard.template_generator&
>> p1=Error%3A%20%5B%24injector%3Anomod%5D%20Module%20'
>> horizon.dashboard.project.heat_dashboard.template_generator'%20is%20not%
>> 20available!%20You%20either%20misspelled%20the%20module%
>> 20name%20or%20forgot%20to%20load%20it.%20If%20registerin
>> g%20a%20module%20ensure%20that%20you%20specify%20the%2
>> 0dependencies%20as%20the%20second%20argument.%0Ahttp%3A%2F%
>> 2Ferrors.angularjs.org%2F1.5.8%2F%24injector%2Fnomod%3Fp0%
>> 3Dhorizon.dashboard.project.heat_dashboard.template_
>> generator%0A%20%20%20%20at%20http%3A%2F%2F192.168.11.187%
>> 2Fdashboard%2Fstatic%2Fdashboard%2Fjs%2F3bf910c7ae4
>> c.js%3A699%3A8%0A%20%20%20%20at%20http%3A%2F%2F192.168.
>> 11.187%2Fdashboard%2Fstatic%2Fdashboard%2Fjs%2F3bf910c7ae4
>> c.js%3A818%3A59%0A%20%20%20%20at%20ensure%20(http%3A%2F%
>> 

Re: [openstack-dev] [horizon] [devstack] horizon 'network create' panel does not distinguished

2018-03-12 Thread Xinni Ge
Hello, Jaewook and everyone

It looks like the error is caused by some angular module of heat-dashboard
not being loaded correctly.

I tried to reproduce it in my devstack by installing stable/queens
Horiozn/Heat-dashboard, but couldn't see the same error.

Maybe you want to try the following steps to restart web server and see if
the issue can be fixed.
Of course you can also remove the troubled panel in heat-dashboard, I will
also describe how to do it as follows.

1. remove heat-dashboard related settings
rm horizon/openstack_dashboard/local/enabled/_16*   # (particularly try to
remove _1650_project_template_generator_panel.py to fix it)
rm
horizon/openstack_dashboard/local/local_settings.d/_1699_orchestration_settings.py*
rm horizon/openstack_dashboard/conf/heat_policy.json

2. let horizon re-collect static files, and compress
python manage.py collectstatic --clear
python manage.py compress

3. restart apache server
sudo service apache2 restart

Hope the problem can be solved and everything goes well.
And if anybody see the same error, please share more details about it.

Best Regards,
Xinni

On Mon, Mar 12, 2018 at 9:55 PM, Jaewook Oh  wrote:

> Thanks for feedback!
>
> As you said, I got errors in the JavaScript console.
>
> Below is the error log :
>
> 3bf910c7ae4c.js:652 JQMIGRATE: Logging is active
> fddd6f634ef8.js:2299 Uncaught TypeError: Cannot read property 'layout' of
> undefined
> at Object.25../arrows (fddd6f634ef8.js:2299)
> at s (fddd6f634ef8.js:2252)
> at fddd6f634ef8.js:2252
> at Object.1../lib/dagre (fddd6f634ef8.js:2252)
> at s (fddd6f634ef8.js:2252)
> at e (fddd6f634ef8.js:2252)
> at fddd6f634ef8.js:2252
> at fddd6f634ef8.js:2252
> at fddd6f634ef8.js:2252
> 25../arrows @ fddd6f634ef8.js:2299
> s @ fddd6f634ef8.js:2252
> (anonymous) @ fddd6f634ef8.js:2252
> 1../lib/dagre @ fddd6f634ef8.js:2252
> s @ fddd6f634ef8.js:2252
> e @ fddd6f634ef8.js:2252
> (anonymous) @ fddd6f634ef8.js:2252
> (anonymous) @ fddd6f634ef8.js:2252
> (anonymous) @ fddd6f634ef8.js:2252
> 3bf910c7ae4c.js:699 Uncaught Error: [$injector:modulerr] Failed to
> instantiate module horizon.app due to:
> Error: [$injector:modulerr] Failed to instantiate module
> horizon.dashboard.project.heat_dashboard.template_generator due to:
> Error: [$injector:nomod] Module 'horizon.dashboard.project.
> heat_dashboard.template_generator' is not available! You either
> misspelled the module name or forgot to load it. If registering a module
> ensure that you specify the dependencies as the second argument.
> http://errors.angularjs.org/1.5.8/$injector/nomod?p0=
> horizon.dashboard.project.heat_dashboard.template_generator
> at http://192.168.11.187/dashboard/static/dashboard/js/
> 3bf910c7ae4c.js:699:8
> at http://192.168.11.187/dashboard/static/dashboard/js/
> 3bf910c7ae4c.js:818:59
> at ensure (http://192.168.11.187/dashboard/static/dashboard/js/
> 3bf910c7ae4c.js:816:320)
> at module (http://192.168.11.187/dashboard/static/dashboard/js/
> 3bf910c7ae4c.js:818:8)
> at http://192.168.11.187/dashboard/static/dashboard/js/
> 3bf910c7ae4c.js:925:35
> at forEach (http://192.168.11.187/dashboard/static/dashboard/js/
> 3bf910c7ae4c.js:703:400)
> at loadModules (http://192.168.11.187/dashboard/static/dashboard/js/
> 3bf910c7ae4c.js:924:156)
> at http://192.168.11.187/dashboard/static/dashboard/js/
> 3bf910c7ae4c.js:925:84
> at forEach (http://192.168.11.187/dashboard/static/dashboard/js/
> 3bf910c7ae4c.js:703:400)
> at loadModules (http://192.168.11.187/dashboard/static/dashboard/js/
> 3bf910c7ae4c.js:924:156)
> http://errors.angularjs.org/1.5.8/$injector/modulerr?p0=
> horizon.dashboard.project.heat_dashboard.template_
> generator=Error%3A%20%5B%24injector%3Anomod%5D%
> 20Module%20'horizon.dashboard.project.heat_dashboard.
> template_generator'%20is%20not%20available!%20You%
> 20either%20misspelled%20the%20module%20name%20or%20forgot%
> 20to%20load%20it.%20If%20registering%20a%20module%20ensure%20that%20you%
> 20specify%20the%20dependencies%20as%20the%20second%20argument.%0Ahttp%
> 3A%2F%2Ferrors.angularjs.org%2F1.5.8%2F%24injector%2Fnomod%
> 3Fp0%3Dhorizon.dashboard.project.heat_dashboard.
> template_generator%0A%20%20%20%20at%20http%3A%2F%2F192.
> 168.11.187%2Fdashboard%2Fstatic%2Fdashboard%2Fjs%
> 2F3bf910c7ae4c.js%3A699%3A8%0A%20%20%20%20at%20http%3A%2F%
> 2F192.168.11.187%2Fdashboard%2Fstatic%2Fdashboard%2Fjs%
> 2F3bf910c7ae4c.js%3A818%3A59%0A%20%20%20%20at%20ensure%20(
> http%3A%2F%2F192.168.11.187%2Fdashboard%2Fstatic%2Fdashboard%2Fjs%
> 2F3bf910c7ae4c.js%3A816%3A320)%0A%20%20%20%20at%20module%20(
> http%3A%2F%2F192.168.11.187%2Fdashboard%2Fstatic%2Fdashboard%2Fjs%
> 2F3bf910c7ae4c.js%3A818%3A8)%0A%20%20%20%20at%20http%3A%2F%
> 2F192.168.11.187%2Fdashboard%2Fstatic%2Fdashboard%2Fjs%
> 2F3bf910c7ae4c.js%3A925%3A35%0A%20%20%20%20at%20forEach%20(
> http%3A%2F%2F192.168.11.187%2Fdashboard%2Fstatic%2Fdashboard%2Fjs%
> 

Re: [openstack-dev] [horizon] [devstack] horizon 'network create' panel does not distinguished

2018-03-12 Thread Jaewook Oh
Thanks for feedback!

As you said, I got errors in the JavaScript console.

Below is the error log : 

3bf910c7ae4c.js:652 JQMIGRATE: Logging is active
fddd6f634ef8.js:2299 Uncaught TypeError: Cannot read property 'layout' of 
undefined
at Object.25../arrows (fddd6f634ef8.js:2299)
at s (fddd6f634ef8.js:2252)
at fddd6f634ef8.js:2252
at Object.1../lib/dagre (fddd6f634ef8.js:2252)
at s (fddd6f634ef8.js:2252)
at e (fddd6f634ef8.js:2252)
at fddd6f634ef8.js:2252
at fddd6f634ef8.js:2252
at fddd6f634ef8.js:2252
25../arrows @ fddd6f634ef8.js:2299
s @ fddd6f634ef8.js:2252
(anonymous) @ fddd6f634ef8.js:2252
1../lib/dagre @ fddd6f634ef8.js:2252
s @ fddd6f634ef8.js:2252
e @ fddd6f634ef8.js:2252
(anonymous) @ fddd6f634ef8.js:2252
(anonymous) @ fddd6f634ef8.js:2252
(anonymous) @ fddd6f634ef8.js:2252
3bf910c7ae4c.js:699 Uncaught Error: [$injector:modulerr] Failed to instantiate 
module horizon.app due to:
Error: [$injector:modulerr] Failed to instantiate module 
horizon.dashboard.project.heat_dashboard.template_generator due to:
Error: [$injector:nomod] Module 
'horizon.dashboard.project.heat_dashboard.template_generator' is not available! 
You either misspelled the module name or forgot to load it. If registering a 
module ensure that you specify the dependencies as the second argument.
http://errors.angularjs.org/1.5.8/$injector/nomod?p0=horizon.dashboard.project.heat_dashboard.template_generator
at http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:699:8
at 
http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:818:59
at ensure 
(http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:816:320)
at module 
(http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:818:8)
at 
http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:925:35
at forEach 
(http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:703:400)
at loadModules 
(http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:924:156)
at 
http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:925:84
at forEach 
(http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:703:400)
at loadModules 
(http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:924:156)
http://errors.angularjs.org/1.5.8/$injector/modulerr?p0=horizon.dashboard.project.heat_dashboard.template_generator=Error%3A%20%5B%24injector%3Anomod%5D%20Module%20'horizon.dashboard.project.heat_dashboard.template_generator'%20is%20not%20available!%20You%20either%20misspelled%20the%20module%20name%20or%20forgot%20to%20load%20it.%20If%20registering%20a%20module%20ensure%20that%20you%20specify%20the%20dependencies%20as%20the%20second%20argument.%0Ahttp%3A%2F%2Ferrors.angularjs.org%2F1.5.8%2F%24injector%2Fnomod%3Fp0%3Dhorizon.dashboard.project.heat_dashboard.template_generator%0A%20%20%20%20at%20http%3A%2F%2F192.168.11.187%2Fdashboard%2Fstatic%2Fdashboard%2Fjs%2F3bf910c7ae4c.js%3A699%3A8%0A%20%20%20%20at%20http%3A%2F%2F192.168.11.187%2Fdashboard%2Fstatic%2Fdashboard%2Fjs%2F3bf910c7ae4c.js%3A818%3A59%0A%20%20%20%20at%20ensure%20(http%3A%2F%2F192.168.11.187%2Fdashboard%2Fstatic%2Fdashboard%2Fjs%2F3bf910c7ae4c.js%3A816%3A320)%0A%20%20%20%20at%20module%20(http%3A%2F%2F192.168.11.187%2Fdashboard%2Fstatic%2Fdashboard%2Fjs%2F3bf910c7ae4c.js%3A818%3A8)%0A%20%20%20%20at%20http%3A%2F%2F192.168.11.187%2Fdashboard%2Fstatic%2Fdashboard%2Fjs%2F3bf910c7ae4c.js%3A925%3A35%0A%20%20%20%20at%20forEach%20(http%3A%2F%2F192.168.11.187%2Fdashboard%2Fstatic%2Fdashboard%2Fjs%2F3bf910c7ae4c.js%3A703%3A400)%0A%20%20%20%20at%20loadModules%20(http%3A%2F%2F192.168.11.187%2Fdashboard%2Fstatic%2Fdashboard%2Fjs%2F3bf910c7ae4c.js%3A924%3A156)%0A%20%20%20%20at%20http%3A%2F%2F192.168.11.187%2Fdashboard%2Fstatic%2Fdashboard%2Fjs%2F3bf910c7ae4c.js%3A925%3A84%0A%20%20%20%20at%20forEach%20(http%3A%2F%2F192.168.11.187%2Fdashboard%2Fstatic%2Fdashboard%2Fjs%2F3bf910c7ae4c.js%3A703%3A400)%0A%20%20%20%20at%20loadModules%20(http%3A%2F%2F192.168.11.187%2Fdashboard%2Fstatic%2Fdashboard%2Fjs%2F3bf910c7ae4c.js%3A924%3A156)
at http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:699:8
at http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:927:7
at forEach 
(http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:703:400)
at loadModules 
(http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:924:156)
at 
http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:925:84
at forEach 
(http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:703:400)
at loadModules 
(http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:924:156)
at createInjector 
(http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:913:464)
at doBootstrap 
(http://192.168.11.187/dashboard/static/dashboard/js/3bf910c7ae4c.js:792:36)
at bootstrap 

Re: [openstack-dev] [Horizon] [Devstack]

2014-11-17 Thread Thiago Paiva

Hello everyone,

I have bumped into an article from one of the memcached creators where 
he discuss the use of memcached to store session data:


http://dormando.livejournal.com/495593.html

Maybe we need to take it into consideration. Maybe it'll bring more 
problems than solutions for a future, scallable HA environment.



Best regards,

On 24-10-2014 17:10, Gabriel Hurley wrote:

SQLite doesn't introduce any additional dependencies, memcached requires 
installation of memcached (admittedly it's not hard on most distros, but it 
*is* yet another step) and in most cases the installation of another python 
module to interface with it.

Memcached might be a good choice for devstack, but it may or may not be the 
right thing to recommend for Horizon by default.

 - Gabriel

-Original Message-
From: Yves-Gwenaël Bourhis [mailto:yves-gwenael.bour...@cloudwatt.com]
Sent: Friday, October 24, 2014 7:06 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Horizon] [Devstack]

Le 24/10/2014 13:30, Chmouel Boudjnah a écrit :

On Fri, Oct 24, 2014 at 12:27 PM, Yves-Gwenaël Bourhis
yves-gwenael.bour...@cloudwatt.com
mailto:yves-gwenael.bour...@cloudwatt.com wrote:
 memcache can be distributed (so usable in HA) and has far better
 performances then db sessions.
 Why not use memcache by default?


I guess for the simple reason that if you restart your memcache you
loose all the sessions?

Indeed, and for devstack that's an easy way do do a cleanup of old sessions :-)

We are well talking about devstack in this thread, where loosing sessions after 
a memcache restart is not an issue and looks more like a very handy feature.

For production it's another mater, and operators have the choice.

--
Yves-Gwenaël Bourhis

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


--
Thiago Paiva Brito
Software Engineer
Advanced OpenStack Brazil Team


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Horizon] [Devstack]

2014-10-24 Thread Yves-Gwenaël Bourhis
Le 23/10/2014 23:55, Gabriel Hurley a écrit :
 1)  If you’re going to store very large amounts of data in the
 session, then session cleanup is going to become an important issue to
 prevent excessive data growth from old sessions.
 
 2)  SQLite is far worse to go into production with than cookie-based
 sessions (which are far from perfect). The more we can do to ensure
 people don’t make that mistake, the better.

memcache can be distributed (so usable in HA) and has far better
performances then db sessions.
Why not use memcache by default?

Just a suggestion.

-- 
Yves-Gwenaël Bourhis

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Horizon] [Devstack]

2014-10-24 Thread Chmouel Boudjnah
On Fri, Oct 24, 2014 at 12:27 PM, Yves-Gwenaël Bourhis 
yves-gwenael.bour...@cloudwatt.com wrote:

 Le 23/10/2014 23:55, Gabriel Hurley a écrit :
  1)  If you’re going to store very large amounts of data in the
  session, then session cleanup is going to become an important issue to
  prevent excessive data growth from old sessions.
 
  2)  SQLite is far worse to go into production with than cookie-based
  sessions (which are far from perfect). The more we can do to ensure
  people don’t make that mistake, the better.

 memcache can be distributed (so usable in HA) and has far better
 performances then db sessions.
 Why not use memcache by default?


I guess for the simple reason that if you restart your memcache you loose
all the sessions?

Chmouel



 Just a suggestion.

 --
 Yves-Gwenaël Bourhis

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Horizon] [Devstack]

2014-10-24 Thread Yves-Gwenaël Bourhis
Le 24/10/2014 13:30, Chmouel Boudjnah a écrit :
 On Fri, Oct 24, 2014 at 12:27 PM, Yves-Gwenaël Bourhis
 yves-gwenael.bour...@cloudwatt.com
 mailto:yves-gwenael.bour...@cloudwatt.com wrote:
 memcache can be distributed (so usable in HA) and has far better
 performances then db sessions.
 Why not use memcache by default?
 
 
 I guess for the simple reason that if you restart your memcache you
 loose all the sessions?

Indeed, and for devstack that's an easy way do do a cleanup of old
sessions :-)

We are well talking about devstack in this thread, where loosing
sessions after a memcache restart is not an issue and looks more like a
very handy feature.

For production it's another mater, and operators have the choice.

-- 
Yves-Gwenaël Bourhis

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Horizon] [Devstack]

2014-10-24 Thread Gabriel Hurley
SQLite doesn't introduce any additional dependencies, memcached requires 
installation of memcached (admittedly it's not hard on most distros, but it 
*is* yet another step) and in most cases the installation of another python 
module to interface with it.

Memcached might be a good choice for devstack, but it may or may not be the 
right thing to recommend for Horizon by default.

- Gabriel

-Original Message-
From: Yves-Gwenaël Bourhis [mailto:yves-gwenael.bour...@cloudwatt.com] 
Sent: Friday, October 24, 2014 7:06 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Horizon] [Devstack]

Le 24/10/2014 13:30, Chmouel Boudjnah a écrit :
 On Fri, Oct 24, 2014 at 12:27 PM, Yves-Gwenaël Bourhis 
 yves-gwenael.bour...@cloudwatt.com
 mailto:yves-gwenael.bour...@cloudwatt.com wrote:
 memcache can be distributed (so usable in HA) and has far better
 performances then db sessions.
 Why not use memcache by default?
 
 
 I guess for the simple reason that if you restart your memcache you 
 loose all the sessions?

Indeed, and for devstack that's an easy way do do a cleanup of old sessions :-)

We are well talking about devstack in this thread, where loosing sessions after 
a memcache restart is not an issue and looks more like a very handy feature.

For production it's another mater, and operators have the choice.

--
Yves-Gwenaël Bourhis

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [Horizon] [Devstack]

2014-10-23 Thread David Lyle
In order to help ease an ongoing struggle with session size limit issues,
Horizon is planning on changing the default session store from signed
cookie to simple server side session storage using sqlite. The size limit
for cookie based sessions is 4K and when this value is overrun, the result
is truncation of the session data in the cookie or a complete lack of
session data updates.

Operators will have the flexibility to replace the sqlite backend with the
DB of their choice, or memcached.

We gain: support for non-trivial service catalogs, support for higher
number of regions, space for holding multiple tokens (domain scoped and
project scoped), better support for PKI and PKIZ tokens, and frees up
cookie space for user preferences.

The drawbacks are we lose HA as a default, a slightly more complicated
configuration. Once the cookie size limit is removed, cookie based storage
would no longer be supported.

Additionally, this will require a few config changes to devstack to
configure the session store DB and clean it up periodically.

Concerns?

David
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Horizon] [Devstack]

2014-10-23 Thread Gabriel Hurley
All in all this is been a long time coming. The cookie-based option was useful 
as a batteries-included, simplest-case scenario. Moving to SQLite is a 
reasonable second choice since most systems Horizon might be deployed on 
support sqlite out of the box.

I would make a couple notes:


1)  If you’re going to store very large amounts of data in the session, 
then session cleanup is going to become an important issue to prevent excessive 
data growth from old sessions.

2)  SQLite is far worse to go into production with than cookie-based 
sessions (which are far from perfect). The more we can do to ensure people 
don’t make that mistake, the better.

3)  There should be a clear deprecation for cookie-based sessions. Don’t 
just drop them in a single release, as tempting as it is.

Otherwise, seems good to me.


-  Gabriel

From: David Lyle [mailto:dkly...@gmail.com]
Sent: Thursday, October 23, 2014 2:44 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Horizon] [Devstack]

In order to help ease an ongoing struggle with session size limit issues, 
Horizon is planning on changing the default session store from signed cookie to 
simple server side session storage using sqlite. The size limit for cookie 
based sessions is 4K and when this value is overrun, the result is truncation 
of the session data in the cookie or a complete lack of session data updates.

Operators will have the flexibility to replace the sqlite backend with the DB 
of their choice, or memcached.

We gain: support for non-trivial service catalogs, support for higher number of 
regions, space for holding multiple tokens (domain scoped and project scoped), 
better support for PKI and PKIZ tokens, and frees up cookie space for user 
preferences.

The drawbacks are we lose HA as a default, a slightly more complicated 
configuration. Once the cookie size limit is removed, cookie based storage 
would no longer be supported.

Additionally, this will require a few config changes to devstack to configure 
the session store DB and clean it up periodically.

Concerns?

David


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [Horizon] Devstack fails to deploy it

2013-08-22 Thread Edgar Magana
Hi,

I just pulled devstack in a clean environment and I am seeing this error on
Horizon:

emagana@os-cont-pod-2:~/devstack$ cd /opt/stack/horizon  sudo tail -f
/var/log/apache2/horizon_error.log || echo horizon failed to start | tee
/opt/stack/status/stack/horizon.failure
[Thu Aug 22 18:46:01 2013] [error] import keyring
[Thu Aug 22 18:46:01 2013] [error]   File
/usr/local/lib/python2.7/dist-packages/keyring/__init__.py, line 9, in
module
[Thu Aug 22 18:46:01 2013] [error] from core import (set_keyring,
get_keyring, set_password, get_password,
[Thu Aug 22 18:46:01 2013] [error]   File
/usr/local/lib/python2.7/dist-packages/keyring/core.py, line 166, in
module
[Thu Aug 22 18:46:01 2013] [error] init_backend()
[Thu Aug 22 18:46:01 2013] [error]   File
/usr/local/lib/python2.7/dist-packages/keyring/core.py, line 58, in
init_backend
[Thu Aug 22 18:46:01 2013] [error] keyring = load_config()
[Thu Aug 22 18:46:01 2013] [error]   File
/usr/local/lib/python2.7/dist-packages/keyring/core.py, line 126, in
load_config
[Thu Aug 22 18:46:01 2013] [error] local_path =
os.path.join(os.getcwd(), filename)
[Thu Aug 22 18:46:01 2013] [error] OSError: [Errno 2] No such file or
directory

Has somebody already reported this?

Thanks,

Edgar


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev