[Yahoo-eng-team] [Bug 1632054] Re: Heat engine doesn't detect lbaas listener failures

2016-12-05 Thread Michael Johnson
The neutron project with lbaas tag was for neutron-lbaas, but now that we have merged the projects, I am removing neutron as it is all under octavia project now. ** No longer affects: neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is

[Yahoo-eng-team] [Bug 1632054] Re: Heat engine doesn't detect lbaas listener failures

2016-12-01 Thread Zhixin Li
Doesn't it need to add an affected project for neutron-lbaas? We need to expose provisioning_status for all top level objects of lbaas. ** Also affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team,

[Yahoo-eng-team] [Bug 1632054] Re: Heat engine doesn't detect lbaas listener failures

2016-12-01 Thread Michael Johnson
The work in Octavia is complete for adding provisioning status to all of the objects. We just need to make sure that is available via the APISs and clients. Provisioning status work was done here: https://review.openstack.org/#/c/372791/ ** Project changed: neutron => octavia -- You received

[Yahoo-eng-team] [Bug 1632054] Re: Heat engine doesn't detect lbaas listener failures

2016-10-10 Thread Rabi Mishra
As mentioned in the mail thread you mentioned and confirmed by the lbaas team, this would probably need changes in lbaas first. - lbaas api should expose provisioning_status for all top level objects (ex. listener) api - The suggested status api('show-load-balancer-status-tree'), which could