Re: [openstack-dev] [tripleo] Pike final release - blockers & priorities

On Sun, Sep 3, 2017 at 7:40 PM, Emilien Macchi wrote: > Here are the priorities and blockers so we can release final Pike. > If you have any question, or think I missed something, or have any > comment, please reply to this thread. > Also, your help is critical for TripleO

Re: [openstack-dev] [oslo][oslo.middleware] when will next release arrive

Hi YunJun, Oslo team hold the releases of oslo libraries for branch Pike(previous master) until we release Pike for service projects like Nova, Cinder. We can issue new release when Queens cycle is open. will confirm with release team today if we can do that in this week or next week.

[openstack-dev] [infra] Why Manila api-ref doc isn't published?

Hi, Since we merged many patches [1][2] about api-ref doc in manila 3 weeks ago. But it cannot display in the Manila developer doc [3]. Does anyone have any idea about this? Do we need to do anything else or just waiting for automatic update? Thanks in advance. [1]

Re: [openstack-dev] [all] Queens Goal for Kingbird

Hi joe, Good to hear from you and thanks for the wishes :) On Mon, 4 Sep 2017 at 5:52 AM, joehuang wrote: > Cool, looking forward to the dashboard plugin. > > Best Regards > Chaoyi Huang (joehuang) > -- > *From:* Goutham Pratapa

[openstack-dev] [tripleo] Pike final release - blockers & priorities

Here are the priorities and blockers so we can release final Pike. If you have any question, or think I missed something, or have any comment, please reply to this thread. Also, your help is critical for TripleO team to release the final version of Pike. I would like to set a target on Friday 8th

[openstack-dev] [oslo][oslo.middleware] when will next release arrive

Hi oslo cores, It has been more than one month since last release of oslo.middleware (3.30.0 on July 18th). I wonder when will next release arrive. I'm asking it because some bug fix[1] is depending the patch sets to be released[2]. [1]: https://review.openstack.org/#/c/487388/ [2]:

[openstack-dev] [tripleo] question about healthcheck

Can someone explain me (sorry for the dumb question) why do we force healthcheck to be positive when deploying TripleO containers? healthcheck: test: /bin/true https://github.com/openstack/tripleo-heat-templates/blob/master/docker/services/keystone.yaml#L180-L181 Instead of real checks? I

Re: [openstack-dev] [all] Queens Goal for Kingbird

Cool, looking forward to the dashboard plugin. Best Regards Chaoyi Huang (joehuang) From: Goutham Pratapa [pratapagout...@gmail.com] Sent: 01 September 2017 21:05 To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [all] Queens Goal for Kingbird Hi

Re: [openstack-dev] [neutron] mod_wsgi support (pike bug?)

On Sun, Sep 3, 2017 at 2:20 PM, Matthew Treinish wrote: > On Sun, Sep 03, 2017 at 01:47:24PM -0400, Mohammed Naser wrote: >> Hi folks, >> >> I've attempted to enable mod_wsgi support in our dev environment with >> Puppet however it results in a traceback. I figured it was

Re: [openstack-dev] [neutron] mod_wsgi support (pike bug?)

On Sun, Sep 3, 2017 at 3:03 PM, Mohammed Naser wrote: > On Sun, Sep 3, 2017 at 2:20 PM, Matthew Treinish wrote: >> On Sun, Sep 03, 2017 at 01:47:24PM -0400, Mohammed Naser wrote: >>> Hi folks, >>> >>> I've attempted to enable mod_wsgi support in our dev

Re: [openstack-dev] [neutron] mod_wsgi support (pike bug?)

On Sun, Sep 03, 2017 at 01:47:24PM -0400, Mohammed Naser wrote: > Hi folks, > > I've attempted to enable mod_wsgi support in our dev environment with > Puppet however it results in a traceback. I figured it was an > environment thing so I looked into moving the Puppet CI to test using > mod_wsgi

[openstack-dev] [neutron] mod_wsgi support (pike bug?)

Hi folks, I've attempted to enable mod_wsgi support in our dev environment with Puppet however it results in a traceback. I figured it was an environment thing so I looked into moving the Puppet CI to test using mod_wsgi and it resulted in the same error.

Re: [openstack-dev] [trove][tc][all] Trove restart - next steps

Tim, Sorry for the delay getting back to you. Different database vendors give you different levels of isolation within your database itself, and making a database truly multi-tenant was something that we did not want to get into. The discussion centered around the benefits of such a

Re: [openstack-dev] Future Trove development

Luke, please see inline below. -- Amrith Kumar mailto:amrith.ku...@gmail.com >From: Luke Browning [mailto:lukebrown...@us.ibm.com] >Sent: Thursday, August 31, 2017 1:00 PM >To: openstack-dev@lists.openstack.org >Subject: Re: [openstack-dev] Future Trove development > >Amrith, > >See answers

Re: [openstack-dev] [vitrage] Collectd - to - Vitrage setup issues

Hi Greg, You should access the vitrage-graph.log using journalctl: sudo journalctl --no-pager --unit devstack@vitrage-graph.service Best Regards, Ifat. From: "Waines, Greg" Date: Thursday, 31 August 2017 at 20:10 To: "Afek,