Adding observability team, although for initial reactions not sure if a separate ticket for infrastructure logs vs search code is the right approach...

This may affect plans to use the Elastic Common Schema for logging.

https://github.com/elastic/ecs still appears to be Apache 2.0 licensed. (But https://github.com/elastic/elasticsearch hasn't been updated either, so maybe a change is pending.) If we use ECS and its license changes to SSPL, that may create headaches for downstream users of MediaWiki.

(Legal can chime in, but copyrightability of a logging schema—and thus whether or not the license even matters—is probably directly dependent on the outcome of https://en.wikipedia.org/wiki/Google_LLC_v._Oracle_America,_Inc.)

Related: https://www.elastic.co/blog/why-license-change-AWS

Confluent did the same thing a few years ago: https://www.confluent.io/blog/license-changes-confluent-platform/
This has prevented us from using some of their free products, even though they were the best solutions.

OSI statement: https://opensource.org/node/1099

I 've marked T272111 as a parent of this task for greater visibility. This one seems more generic than the specific one to CirrusSearch hence this relationship, but feel free to undo.

Amazon has announced plans to fork Elasticsearch and Kibana under the original Apache 2.0 license (starting from ES 7.10)
https://aws.amazon.com/blogs/opensource/stepping-up-for-a-truly-open-source-elasticsearch/

Apparently there is a more community-oriented fork in the works, too: https://logz.io/blog/open-source-elasticsearch-doubling-down/

In T272238#6764574, @akosiaris wrote:

I 've marked T272111 as a parent of this task for greater visibility. This one seems more generic than the specific one to CirrusSearch hence this relationship, but feel free to undo.

Can't we just mark this as dupe? It's pretty clear there will be a viable fork, so it will "only" be a matter of picking a new upstream (or possibly joining the formation of one). Unless we end up with multiple incompatible upstreams (seems unlikely in the short term), I doubt we'd pick different ones for the various pieces of software.

In T272238#6771873, @Nemo_bis wrote:

In T272238#6764574, @akosiaris wrote:

I 've marked T272111 as a parent of this task for greater visibility. This one seems more generic than the specific one to CirrusSearch hence this relationship, but feel free to undo.

Can't we just mark this as dupe? It's pretty clear there will be a viable fork, so it will "only" be a matter of picking a new upstream (or possibly joining the formation of one). Unless we end up with multiple incompatible upstreams (seems unlikely in the short term), I doubt we'd pick different ones for the various pieces of software.

While that scenario may indeed (and I actually hope) pan out, assuming that it will without input from the respective teams would be presumptuous of me. I 'd much rather each interested party/team became aware of the issue, the potential solutions, benefits as well as concerns (pooling efforts and adopting the same solution, whatever that may be, is a very valid concern in my book and I guess yours as well) and came to a decision weighing all of those instead of just assuming from the beginning that 1 solution will be adequate for everyone.

We have as long as we want to figure out what to do next, I don't think the day they drop 7.11 changes anything. CirrusSearch doesn't even support 7.x today, other uses at WMF may differ.

Elastic does not announce release dates in advance.

CirrusSearch is still on ES 6, which will become EOL on 2020-11-20.
Production logging is on ELK 7.10 as of two weeks ago (T234854). It will become EOL on 2022-05-11, but won't be maintained after the 7.11 release.

It appears that the two groups that announced forks (AWS and logz.io) may end up are working together on the same fork (per https://logz.io/blog/truly-doubling-down-on-open-source-2/, https://twitter.com/horovits/status/1353780274686001152). Both have said that more details are coming "in the next few weeks".

https://aws.amazon.com/blogs/opensource/introducing-opensearch/

Today, we are introducing the OpenSearch project, a community-driven, open source fork of Elasticsearch and Kibana. We are making a long-term investment in OpenSearch to ensure users continue to have a secure, high-quality, fully open source search and analytics suite with a rich roadmap of new and innovative functionality. This project includes OpenSearch (derived from Elasticsearch 7.10.2) and OpenSearch Dashboards (derived from Kibana 7.10.2).
...
The entire code base is under the Apache 2.0 license, and we don’t ask for a contributor license agreement (CLA).