Re: [Openstack-operators] [openstack-dev] [neutron] heads up to long time ovs users...

ofctl", they will hit some packet losses when upgrading neutron to Stein. We have no actual data on large deployments so far and don't know how this change impacts real deployments. Your feedback would be really appreciated. Best regards, Akihiro Motoki (irc: amotoki) 2018年9月21日(金) 10:37 IWAMOTO

[Openstack-operators] [horizon][packaging] django-openstack-auth retirement

Hi, packaging teams and operators This mail is the announcement of retirement of django-openstack-auth python package in the Queens release. Horizon team merged the code of django-openstack-auth into the horizon repo mainly from the maintenance reason. For more detail, see the blueprint

Re: [Openstack-operators] Openstack operational configuration improvement.

Hi Flint, I have both hats as an operator of OpenStack and a horizon core. I understand that GUI support of OpenStack configuration is useful for some operators. I know several softwares support GUI-based configurations. However, I see several challenging points. First point is how to

Re: [Openstack-operators] [openstack-dev] [Neutron] Debug tool

Forwarding the mail to openstack-operator ML. I believe the operator list is a better to place to discuss this topic. This is about 'neutron-debug' command. https://github.com/openstack/neutron/blob/master/setup.cfg#L48 Thanks, Akihiro 2017-11-19 21:24 GMT+09:00 Gary Kotton

[Openstack-operators] Need feedback for horizon nova-network drop

Hi all, Horizon team is now thinking the drop of nova-network support in Pike. I would like to ask operators' feedback on this. Is it time to drop nova-network support? This means neutron will be a requirement if you enable 'compute' dashboard. The following describes the detail. This is due

Re: [Openstack-operators] need input on log translations

2017-03-14 0:15 GMT+09:00 Doug Hellmann : > Excerpts from Doug Hellmann's message of 2017-03-10 09:38:43 -0500: >> There is a discussion on the -dev mailing list about the i18n team >> decision to stop translating log messages [1]. The policy change means >> that we may be

Re: [Openstack-operators] [neutron] Liberty - Do Neutron Routers actually work?

When you are using ML2 with OVS driver and (in-tree) L3 router plugin, and if br-ex is used to connect to the external network, the gateway port of the router can be DOWN even if it does work. It seems you pinged from the root netns on your network node. In a normal setup with ML2 OVS driver and

[Openstack-operators] [log] LOG.exception should contain an exception message or not?

Hi, # cross-posting to -dev and -operators ML In the current most OpenStack implementation, when we use LOG.exception, we don't pass an exception message to LOG.exception: LOG.exception(_LE("Error while processing VIF ports")) IIUC it is because the exception message will be logged at the

Re: [Openstack-operators] Adding network node (Neutron agents) and test before deploying customer resource

/listinfo/openstack-operators -- Akihiro Motoki amot...@gmail.com ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators