[TripleO] criteria for deprecating services

Emilien Macchi emilien at redhat.com
Mon Mar 4 14:02:24 UTC 2019

On Mon, Mar 4, 2019 at 8:17 AM Dan Prince <dprince at redhat.com> wrote:

> Agree the cost isn't zero. But it also isn't high. And there is value
> to a project having a deep bench of services from which to choose and
> try out. The existance of at least some "niche" services in TripleO
> provides some value to our users and perhaps even an argument to use
> TripleO as it would be considered a feature to be able to try out these
> services. Perhaps even partially implemented ones in some cases still
> have value (no HA support for example)

Maybe some middle ground here would be to move these services into
tht/deployment/unsupported (if our community decided to NOT deprecate them).
What do you think?

Again my goal isn't to block innovation but to let our team refocus on
other subjects that matter.
Emilien Macchi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190304/4d0f9191/attachment.html>

More information about the openstack-discuss mailing list