I’m thrilled to say that OpenSearch has reached general availability (GA) with the release of version 1.0. This release represents a significant milestone and noteworthy accomplishment for a new open source initiative that was only launched a few months ago. I vividly remember that moment at the beginning of the year when we all woke up to Elastic’s announcement that it would take Elasticsearch and Kibana off the Apache 2.0 OSS license.
OpenSearch is a community response to the recent relicensing of Elasticsearch as a non-Open Source platform. AWS, Logz.io, and a number of partners have been working for months not only to make this merely compatible with Elasticsearch as a functional replacement, but also seeking to create an independent project roadmap.
When the VMware Tanzu Community Engagement team assembled three years ago, we did so with the belief that strong, sustainable community engagement is a crucial component of successful open source projects. With a mission of helping to build up and improve communities, we set out to support several VMware-originated open source projects.
If you’re here you probably know the essence of open source already. To us, open source means more than just open source code – it’s also the ethics and the community feeling that goes along with that. For us it means that the people working on Icinga are more than just who we see in our office – Icinga lives from your ideas and contributions. And we want to invite you to join in on the fun!
Welcome to the second edition of Open Source Matters: our regular publication about the latest happenings in open source! Let’s dive into the news.
OpenSearch has been a buzz in DevOps over the first half of 2021. The project is moving forward, but understandably there are a lot of questions. This article will address some of those frequently asked questions, and will be updated to address more over time.
Last week Elastic.co started locking down its Beats OSS shippers such that they will not be able to send data to Elasticsearch 7.10 or earlier open source distros, or Non-Elastic distros of Elasticsearch. If you weren’t watching closely this might have slipped under your radar. Embedded within the Beats 7.13 minor release that was published over the weekend, a release note advised of a breaking change in which “Beats may not be sending data to some distributions of Elasticsearch”.
What an exciting episode of OpenObservability Talks it was! On May 27, I hosted Kyle Davis, Senior Developer Advocate for OpenSearch at AWS, for a chat about the OpenSearch project, where it stands and where it’s heading. I wanted to share with you some interesting insights from our chat. You’re more than welcome to check out the full episode.
In January 2021, we announced that starting with version 7.11, we would be changing the Apache 2.0 portions of Elasticsearch and Kibana source code to be dual licensed under Elastic License and SSPL, at the users’ discretion. As part of that change, we created Elastic License 2.0 (ELv2) as a permissive, fair-code license, which allows free use, redistribution, modification, and derivative works, with only three simple limitations, outlined in our original announcement.
Welcome to the first edition of Open Source Matters: our regular publication about the latest happenings in open source! Let’s dive into the news.
