Unfortunately this is not currently a configurable option, it is hard-coded
to 3 seconds. That is in horizon/static/framework/conf.js
On 22 September 2016 at 15:11, ankit agrawal
wrote:
> Hi,
>
> I am not much aware of the front-end part of Openstack. Is there a way to
> increase the window time
Hi,
I am not much aware of the front-end part of Openstack. Is there a way to
increase the window time of the green colored 'success message' that
appears in Horizon (at the end of a successful operation)?
Thanks,
Ankit Agarwal
___
Mailing list: http://
Hi,
an update from my-test , why even I empty group rule with no rule defined,
I still can reach (ping & ssh) my instance from outside ?
On Wed, Sep 21, 2016 at 5:18 PM, Adhi Priharmanto
wrote:
> Hi Huan Xie,
>
>
> Thanks for your fast response, I applied those patch into my Dom0 and DomU
> (no
What is the SHA? Sorry if I don't know it.
When I want to use the console Openstack says that it is not available and I
have this error in the n-spice log:
2016-09-21 12:17:35.734 INFO nova.console.websocketproxy [-] WebSocket
server settings:
2016-09-21 12:17:35.735 INFO nova.console.websocketp
2016-09-19 15:50 GMT+02:00 Silvia Fichera :
> Hi all,
> I'm installing Openstack Mitaka via Devstack.
> Since there is a bug in horizon (reported here
> https://bugs.launchpad.net/horizon/+bug/1622684 )
Well, the bug is in noVNC really, you can work around it by checking
out the SHA mentioned in t
Hi Huan Xie,
Thanks for your fast response, I applied those patch into my Dom0 and DomU
(nova-compute) , then restarting neutron-openvswitch-agent and nova-compute
service.
the error on neutron-openvswitch-agent doesn't appear anymore, now I'm
still try Security Group Rules variation for instanc
Hi Adhi,
1. From http://pastebin.com/gwf1wdEb, we can see you have set “conntrack”
command in netwrap, but seems the whole patch is not applied, I mean you need
apply the whole patch https://review.openstack.org/#/c/341304/ in neutron.
netwrap locates in Dom0 /etc/xapi.d/plugins
neutron-r
Also, if you haven't changed default parameter for token cache time then it
has 5 min of cache (you can increase this time if you want). So, your 15-16
machines (or less if some of them doesn't use keystone like swift object,
container, account nodes) will use requests to keystone only once in 5
mi
