Re: [openstack-dev] [mistral] PTG Summary

On 7 Mar 2018, 16:29 +0700, Dougal Matthews , wrote: > Hey Mistralites (maybe?), > > I have been through the etherpad from the PTG and attempted to expand on the > topics with details that I remember. If I have missed anything or you have > any questions, please get in touch.

Re: [openstack-dev] [kolla][vote] core nomination for caoyuan

sorry for a typo. The vote is open for 7 days until Mar 19th. On Mon, Mar 12, 2018 at 10:06 AM, Jeffrey Zhang wrote: > ​​Kolla core reviewer team, > > It is my pleasure to nominate caoyuan for kolla core team. > > caoyuan's output is fantastic over the last cycle. And

[openstack-dev] [kolla][vote] core nomination for caoyuan

​​Kolla core reviewer team, It is my pleasure to nominate caoyuan for kolla core team. caoyuan's output is fantastic over the last cycle. And he is the most active non-core contributor on Kolla project for last 180 days[1]. He focuses on configuration optimize and improve the pre-checks feature.

Re: [openstack-dev] [horizon] [heat-dashboard] Horizon plugin settings for new xstatic modules

Hi, Akihiro Thanks for the quick reply. I agree with your opinion that BASE_XSTATIC_MODULES should not be modified. It is much better to enhance horizon plugin settings, and I think maybe there could be one option like ADD_XSTATIC_MODULES. This option adds the plugin's xstatic files in

Re: [openstack-dev] [tricircle] Nominate change in tricircle core team

+1. Baisen has contributed lots of patches in Tricircle. Best Regards Chaoyi Huang (joehuang) From: Vega Cai [luckyveg...@gmail.com] Sent: 12 March 2018 9:04 To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [tricircle]

[openstack-dev] [tricircle] Nominate change in tricircle core team

Hi team, I would like to nominate Baisen Song (songbaisen) for tricircle core reviewer. Baisen has actively joined the discussion of feature development and has contributed important patches since Queens, like resource deletion reliability and openstack-sdk new version adaption. I really think his

Re: [openstack-dev] [nova] [placement] placement update 18-10

# Questions > What's the status of shared resource providers? Did we even talk > about that in Dublin? In terms of bug fixes related to allocation candidates, I'll try to answer that question :) Most of the bugs that have been reported in https://bugs.launchpad.net/nova/+bug/1731072 are sorted

Re: [openstack-dev] [keystone] Keystone failing with error 104 (connection reset by peer) if using uwsgi

On 03/11/2018 08:12 PM, Lance Bragstad wrote: > Hey Thomas,  > > Outside of the uwsgi config, are you following a specific guide for your > install? Under the packages that I maintain in Debian, there's nothing more to do than "apt-get install keystone", reply to a few Debconf questions, and you

Re: [openstack-dev] [Senlin] Nominate changing in Senlin core team

+1 to both! Ethan > On 9 Mar 2018, at 5:28 PM, liu.xuefe...@zte.com.cn wrote: > > > > Hi team, > > I would like to propose adding chenyb and DucTruong to the Senlin core > team. > > Chenyb has been working on Openstack more than 3 years, with the > responsibility of intergation Nova,

Re: [openstack-dev] [keystone] Keystone failing with error 104 (connection reset by peer) if using uwsgi

Hey Thomas, Outside of the uwsgi config, are you following a specific guide for your install? I'd like to try and recreate the issue. Do you happen to have any more logging information? Thanks On Mar 11, 2018 06:10, "Thomas Goirand" wrote: > Hi, > > I've attempted to switch

[openstack-dev] [openstack][charms] Openstack + OVN

Hi, I had previously put in a mail about the development for openstack-ovn charm. Sorry it took me this long to get back, was involved in other projects. I have submitted a charm spec for the above charm. Here is the review link : https://review.openstack.org/#/c/551800/ Please look in to it

[openstack-dev] [keystone] Keystone failing with error 104 (connection reset by peer) if using uwsgi

Hi, I've attempted to switch Keystone to using uwsgi instead of Apache in the Debian packages for Queens. Unfortunately, I had random failure with error 104 in both output of the client and keystone logs. 104 is in fact "TCP connection reset by peer" (and this shows in the logs). So I've switched