-
Notifications
You must be signed in to change notification settings - Fork 277
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.2.0 #567
Comments
Created/updated a 1.2.0 label using meta from https://github.com/opensearch-project/opensearch-plugins
|
From Docker Release |
Note; we are tracking a OpenSearch-Dashboards blocker on #934 |
Nov 11th, End of day today all tests should have executed on build 964 or 364+ so we can be sure that all issues have been flushed out. Then we will begin taking a closer look at outstanding 1.2.0 issues and make sure they are burning down so we are on target for the release on Nov 16th. |
Release testing has resetWe have found a validation blocking bug and all testing needs to be reset unless you know distribution downloader is not used, #953. The distribution download was pulling snapshot artifacts that were 3 weeks old - before feature complete. The artifacts have been updated, but all testing needs to be reset. I will be updating build images shortly and also creating an office hours today for anyone to join with questions. This will slip the release by 2 days to give all teams time to restart testing, new release testing completion date is scheduled for Nov 15th. |
Release date - updateSince the testing process has slipped, we are pushing the release date out to Thursday, Nov18th. I'll be following day-by-day to make sure that everything is in alignment and be reaching out to release tickets. |
Release 1.2.0 is scheduled for 18th. Today all testing must be complete, we will be pushing to have all remaining issues marked for the release resolved as soon as possible. I am still waiting for confirmation that tests were rerun and completed for:
All release drivers, please drive down all open issues and check off all the completed work in the component specific issues. |
Current issues, from https://github.com/opensearch-project/opensearch-plugins via opensearch-project/opensearch-plugins open issues, labeled v1.2.064: Lower CI Java Version to Java 11 for all plugins and run integration tests on 8 enhancement meta v1.2.0 1 opensearch-project/alerting open issues, labeled v1.2.082: Alerts needs stricter ownership enhancement backlog v1.2.0 5 opensearch-project/asynchronous-search open issues, labeled v1.2.049: Typed Keys Response param added in Get Asynchronous Search API v1.2.0 ↑ opensearch-project/index-management open issues, labeled v1.2.0197: [Distribution Build] Integ-Test Failure RestDeleteTransformActionIT v1.2.0 1 @downsrob opensearch-project/job-scheduler open issues, labeled v1.2.0101: [BundleBuild] opensearch-job-scheduler-spi maven artifacts are not copied to the correct location bug v1.2.0 2 opensearch-project/k-nn open issues, labeled v1.2.0214: [IntegTest] knn.plugin.action.RestLegacyKNNStatsHandlerIT on distribution build v1.2.0 3 opensearch-project/sql open issues, labeled v1.2.0262: Release SQL Drivers and CLI OpenSearch 1.2 v1.2.0 @chloe-zh |
@peternied / @peterzhuamazon - can you confirm these artifacts are correct for 1.2.0? (this includes compatible but independently released OpenSearch stuff like cli, data-prepper. I assume no changes from 1.1.0, so just a glance would be good on those; Mostly concerned with the core artifacts/URLs)
|
@stockholmux That is really hard for my brain to process seems like a good opportunity for a tooling, do we have the current list for 1.1.0 that I could diff this against? |
@peternied It's just a updated text version of this: https://opensearch.org/artifacts/by-version/#v1-1-0 Otherwise, you can view my branch to see the new files. stockholmux/project-website@5451bba I'm not sure we can tool in an effective way since there is more fluidity than you would imagine between versions (e.g. 1.1.0 has FreeBSD but not yet for 1.2.0, we'll be adding additional artifacts soon, etc.) |
@stockholmux |
@peternied FreeBSD folks will take our released version and make the changes needed to FreshPorts (@smortex is a key contact). I've already pinged them in their discord. |
Tomorrow is the scheduled OpenSearch 1.2.0 release, if you were waiting for the last minute here it is! Track on #567 Urgent follow up needed
For all release owners, clean up any issues on this list [Query] and mark all Pre-Release and Release tasks complete by EOD otherwise you might hold up the release. As soon as that issues list has As always please use github release issues for questions. |
Moved to 1.3.
|
For the release process today the team is focusing in on OpenSearch 1.2.0 Performance regression of 10% compared to 1.1.0 opensearch-project/OpenSearch#1560 |
1.2 Update For investigating the removal of ShardIndexingPressure, we switched from using a CI build to both builds from the same dev box and the results were very close to identical. We have created a build removing ShardIndexingPressure via the CI system, to confirm the ~20% drop was configuration related. Those tests have been kicked off and will be validated tomorrow morning. Distribution testing showed more index latency degradation on arm builds, we will re-run tests from the 7 key dates on ARM to see if we can identify a smoking gun - long shot but doing our due diligence. Next steps: Review the test results after they come back, if we cannot reproduce the perf drop, we will start the final release process on Monday. Details: opensearch-project/OpenSearch#1560 |
Talked to @peternied will use the latest version built on Monday morning for integTest. |
We are using build# |
Retrospective is scheduled for Friday Dec 10th, published action items should be made available the following week. |
Release OpenSearch and OpenSearch Dashboards 1.2.0
I noticed that a manifest was automatically created in manifests/1.2.0. Please follow the following checklist to make a release.
How to use this issue
This Release Issue
This issue captures the state of the OpenSearch release, its assignee is responsible for driving the release. Please contact them or add a comment on this issue for help. There are linked issues on components of the release where individual components can be tracked.
Release Steps
There are several steps to the release process, these steps are completed as the whole release and components that are behind present risk to the release. The release owner completes the tasks in this ticket, whereas component owners resolve tasks on their ticket.
Steps have completion dates for coordinating efforts between the components of a release; components can start as soon as they are ready far in advance of a future release.
Component List
To aid in understanding the state of the release there is a table with status indicating each component state. This is manually updated based on the status of the component issues.
Preparation - Ends Oct 28th
Engine and Dashboard Development - Ends Nov 2nd
All Component Development - Ends Nov 8th
Release testing - Ends Nov 16th
Release -
Ends Nov 18thEnds Nov 23v1.2.0
in all projects have been resolved.Post Release
Components
Overall status: Post Release 1.2.0 has been released, all post release tasks should be worked on and component release tasks closed out.
Next Step: Closing this release task, ETA Dec 13th.
Legend
| Symbol | Meaning | | -------- | ---------- | | 🟢 | On track with overall release | | 🟡 | Missed last milestone | | 🔴 | Missed multiple milestones |
Issue tracking
Updated on 11/16 9:18a CST Query are accessible in the table headers
Campaigns
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
Use Docker-Compose to setup a cluster
docker-compose pull
docker-compose up
OpenSearch docker
docker pull opensearchstaging/opensearch:1.2.0 && docker run -it -p 9200:9200 -e "discovery.type=single-node" -e "DISABLE_SECURITY_PLUGIN=true" opensearchstaging/opensearch:1.2.0
curl https://localhost:9200
docker pull opensearchstaging/opensearch:1.2.0 && docker run -it -p 9200:9200 -e "discovery.type=single-node" opensearchstaging/opensearch:1.2.0
curl --insecure https://admin:admin@localhost:9200
OpenSearch-Dashboards docker
docker pull opensearchstaging/opensearch-dashboards:1.2.0 && docker run -it --network="host" -e "DISABLE_SECURITY_DASHBOARDS_PLUGIN=true" opensearchstaging/opensearch-dashboards:1.2.0
https://localhost:5601
docker pull opensearchstaging/opensearch-dashboards:1.2.0 && docker run -it --network="host" opensearchstaging/opensearch-dashboards:1.2.0
https://localhost:5601
Use TARs to deploy OpenSearch Manually (Updated 2021/11/22 11:00 PST)
OpenSearch - Build 1127
OpenSearch Dashboards - Build 512
From Docker Release
The text was updated successfully, but these errors were encountered: