Open Stack

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 <openstack at nemebean.com> wrote:
>
>
> 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 demonstrated that the tests were no longer passing and
>> fixing them is enough of a chore that I (at least temporarily)
>> marked one test as an expected failure.o
>>
>>      https://review.openstack.org/#/c/559717/
>>
>> The following projects appear to still use WSME:
>>
>>      aodh
>>      blazar
>>      cloudkitty
>>      cloudpulse
>>      cyborg
>>      glance
>>      gluon
>>      iotronic
>>      ironic
>>      magnum
>>      mistral
>>      mogan
>>      octavia
>>      panko
>>      qinling
>>      radar
>>      ranger
>>      searchlight
>>      solum
>>      storyboard
>>      surveil
>>      terracotta
>>      watcher
>>
>> Most of these are using the 'types' handling in WSME and sometimes
>> the pecan extension, and not the (potentially broken) Flask
>> extension, so things should be stable.
>>
>> However: nobody is working on keeping WSME up to date. It is not a
>> good long term investment.
>
>
> What would be the recommended alternative, either for new work or as a
> migration path for existing projects?
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev