-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RELEASE] Release version 1.1.1 #870
Comments
This release's date is contingent on #567 completion, this is due to manual processes and the intention is to mitigate risk of accidentally including a 1.2.0+ changes in the 1.1.1 components. |
We should assemble a 1.1.1 manifest with all the components though earlier than later and include it in automated builds. |
@anirudha For this point release can you help me work back the dates that we are targeting? Roughing working off of @bbarani planning notes we had the following:
This isn't factoring in the time itself to make the actual fixes for the point release. Do we need additional time account before starting? Starting the day after the 1.2 release, Development starts on Nov 17th and +6 days is Release on the Nov 24th. This is a super tight window with Thanksgiving impacting team availability if there is any day/day slip |
I renamed the issue back or the bot keeps creating new ones. |
Stop being so helpful automation! |
Offline: @anirudha confirmed that are targeting the release on Nov 24th |
[Triage] Moved this to @bbarani to confirm the release dates and manage the work back schedule. Since this is a point release there is flexibility, but the more flexing that is done the more risk that is introduced to the schedule. |
1.1.1 is currently schedule for Nov 23 2021. Lets work backward from the release date to close out the preparation work. |
[Triage] @bbarani will be updating the final release date. |
We are targeting Dec 2 for 1.1.1 release. |
Hi @anirudha Would you mind confirming that we will only change dashboards-reports FrontEnd plugin? If so, we will only release OpenSearch-Dashboards Bundle 1.1.1 with TAR + Docker Images (x64 + arm64). Thanks, |
|
|
This release is postponed given the log4j RCE, we'll re-evaluate whether we do it at all. See #1290. |
Let's close all 1.1.1 issues since there will be no such thing? @peterzhuamazon |
Shall we just close all plugin repo issue 1 by 1 then close this one? |
Yes please, but we need a paragraph of why we're not releasing 1.1.1 from @bbarani. |
We will not be releasing 1.1.1 version of OpenSearch as we decided to prioritize the release of 1.2.x version of OpenSearch to fix critical log4j vulnerabilities. Please upgrade to the latest version of OpenSearch to take advantage of the new features along with multiple bug fixes and patches. |
Release OpenSearch and OpenSearch Dashboards 1.1.1
(As of 2021/11/17 We only make changes toOpenSearch-Dashboards
to 1.1.1, therefore,OpenSearch
stays 1.1.0.)(We will release both OpenSearch and OpenSearch-Dashboards 1.1.1 as both need changes to reports plugin BE/FE)
We are pausing 1.1.1 for now due to CVE-2021-44228.
Related to this:
https://discuss.opendistrocommunity.dev/t/log4j-patch-for-cve-2021-44228/7950
OpenSearch is actively working on a patch, will need to change our Ansible playbook to it once it is ready.
Please follow the following checklist to make a release.
This release is contingent on completion of #567
Preparation
RELEASE-
placeholders have actual dates.- [ ] Finalize scope and feature set and update the Public Roadmap.- [ ] Ensure that all release issues created above are assigned to an owner in the component team.CI/CD - 2021/12/06 - 2021/12/08
Release testing - 2021/12/09 - 2021/12/10
Release - 2021/12/13 - 2021/12/14
v1.1.1
in all projects have been resolved.Post Release
Patching Bugs
Components
Legend
Issue tracking
Release testing
To aid in release testing we are providing all teams with access to docker images of OpenSearch to aid in the rapid setup/tear down for testing, for additional discussion about test documentation see #933
All links and commands for testing will be available once the artifacts are ready.
Use Docker-Compose to setup a cluster
docker-compose pull
docker-compose up
OpenSearch docker
docker pull opensearchstaging/opensearch:1.1.1 && docker run -it -p 9200:9200 -e "discovery.type=single-node" -e "DISABLE_SECURITY_PLUGIN=true" opensearchstaging/opensearch:1.1.1
curl https://localhost:9200
docker pull opensearchstaging/opensearch:1.1.1 && docker run -it -p 9200:9200 -e "discovery.type=single-node" opensearchstaging/opensearch:1.1.1
curl --insecure https://admin:admin@localhost:9200
OpenSearch-Dashboards docker
docker pull opensearchstaging/opensearch-dashboards:1.1.1 && docker run -it --network="host" -e "DISABLE_SECURITY_DASHBOARDS_PLUGIN=true" opensearchstaging/opensearch-dashboards:1.1.1
https://localhost:5601
docker pull opensearchstaging/opensearch-dashboards:1.1.1 && docker run -it --network="host" opensearchstaging/opensearch-dashboards:1.1.1
https://localhost:5601
Use TARs to deploy OpenSearch Manually
OpenSearch - Build distribution 8
OpenSearch Dashboards - Build distribution 7
From Docker Release
The text was updated successfully, but these errors were encountered: