Re: [openstack-dev] [all] [api] Re-Reminder on the state of WSME

ironic-inspector is using Flask, and it has been quite nice so far. On 04/11/2018 12:56 AM, Michael Johnson wrote: I echo Ben's question about what is the recommended replacement. Not long ago we were advised to use WSME over the alternatives which is why Octavia is using the WSME types and

Re: [openstack-dev] [all] [api] Re-Reminder on the state of WSME

On Wed, 11 Apr 2018, Michael Johnson wrote: I am willing to help with maintenance (patch reviews/gate fixes), but I cannot commit time to development work on it. Michael and I also spoke in IRC and he too is now a WSME core. Thanks to both of you for stepping up and being willing to help

Re: [openstack-dev] [all] [api] Re-Reminder on the state of WSME

I am willing to help with maintenance (patch reviews/gate fixes), but I cannot commit time to development work on it. Michael On Wed, Apr 11, 2018 at 6:21 AM, Chris Dent wrote: > On Wed, 11 Apr 2018, Dougal Matthews wrote: > >> I would like to see us move away from WSME.

Re: [openstack-dev] [all] [api] Re-Reminder on the state of WSME

On Wed, 11 Apr 2018, Dougal Matthews wrote: I would like to see us move away from WSME. I'm not sure I have time to drive an effort in finding a replacement (and migration path) but I would certainly like to help. Dougal and I talked about this in IRC and agreed that being able to merge

Re: [openstack-dev] [all] [api] Re-Reminder on the state of WSME

On 11 April 2018 at 11:39, Chris Dent wrote: > On Tue, 10 Apr 2018, Michael Johnson wrote: > > I echo Ben's question about what is the recommended replacement. >> > > It's a good question. Unfortunately I don't have a good answer. My > involvement in WSME is simply the

Re: [openstack-dev] [all] [api] Re-Reminder on the state of WSME

On Tue, 10 Apr 2018, Michael Johnson wrote: I echo Ben's question about what is the recommended replacement. It's a good question. Unfortunately I don't have a good answer. My involvement in WSME is simply the result of submitting some bug fixes in early 2015 and there being no one to review

Re: [openstack-dev] [all] [api] Re-Reminder on the state of WSME

I echo Ben's question about what is the recommended replacement. Not long ago we were advised to use WSME over the alternatives which is why Octavia is using the WSME types and pecan extension. Thanks, Michael On Mon, Apr 9, 2018 at 10:16 AM, Ben Nemec wrote: > > > On

Re: [openstack-dev] [all] [api] Re-Reminder on the state of WSME

On 04/09/2018 07:22 AM, Chris Dent wrote: A little over two years ago I sent a reminder that WSME is not being actively maintained: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088658.html Today I was reminded of this becasue a random (typo-related) patchset

[openstack-dev] [all] [api] Re-Reminder on the state of WSME

A little over two years ago I sent a reminder that WSME is not being actively maintained: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088658.html Today I was reminded of this becasue a random (typo-related) patchset demonstrated that the tests were no longer passing and