peterzhuamazon
commented
2 years ago [Triage] @bbarani please advice on the release timing and I will then send out the release issues to plugin owners of 2.0.0.
Thanks.
Closed github-actions[bot] closed 2 years ago
peterzhuamazon
commented
2 years ago [Triage] @bbarani please advice on the release timing and I will then send out the release issues to plugin owners of 2.0.0.
Thanks.
bbarani
commented
2 years ago @peterzhuamazon Please start sending the release issues to the plugin owners repo as soon as possible as this is a Major release and its better to start building the distribution to surface any potential gaps.
peterzhuamazon
commented
2 years ago @peterzhuamazon Please start sending the release issues to the plugin owners repo as soon as possible as this is a Major release and its better to start building the distribution to surface any potential gaps.
Added now, thanks.
peternied
commented
2 years ago @peterzhuamazon I see a release issue created in my repos, but there are no dates on this issue for me to make sure we are aligning towards. The second preparation step is to confirm the dates and document them, can you complete that task and the other preparation items that should be completed before the component issues are cut?
kavilla
commented
2 years ago Hijacking this issue to highlight: https://github.com/opensearch-project/OpenSearch-Dashboards/issues/1206
The Node upgrade comes with breaking changes. OpenSearch Dashboards plugins owners should begin verifying their plugin can still build with OpenSearch Dashboards sooner than later. For the upgrade we did a quick verification and the impact was minimal but since then there have been numerous package upgrades to resolve CVEs.
If plugin owners run into any issues and need mitigation techniques please add to https://github.com/opensearch-project/OpenSearch-Dashboards/issues/1206.
peternied
commented
2 years ago Following up on https://github.com/opensearch-project/opensearch-build/issues/1624#issuecomment-1055588976
- Declare a pencils down date for new features to be merged. _REPLACE_RELEASE-minus-14-days is pencils down.
- Update the Campaigns section to include monitoring campaigns during this release.
- Update this issue so all __REPLACE_RELEASE-__ placeholders have actual dates.
@peterzhuamazon @bbarani I still don't see this items complete so I cannot take action on my component release issue. Please complete these preparation tasks to unblock teams.
amitgalitz
commented
2 years ago Hijacking this issue to highlight: opensearch-project/OpenSearch-Dashboards#1206
The Node upgrade comes with breaking changes. OpenSearch Dashboards plugins owners should begin verifying their plugin can still build with OpenSearch Dashboards sooner than later. For the upgrade we did a quick verification and the impact was minimal but since then there have been numerous package upgrades to resolve CVEs.
If plugin owners run into any issues and need mitigation techniques please add to opensearch-project/OpenSearch-Dashboards#1206.
Should we add verifying plugins work w/ Node.js upgrade as part of the 2.0.0 release campaign issues. Or is this only for campaigns that are also a part of Opensearch core and not dashboards.
peterzhuamazon
commented
2 years ago Hijacking this issue to highlight: opensearch-project/OpenSearch-Dashboards#1206 The Node upgrade comes with breaking changes. OpenSearch Dashboards plugins owners should begin verifying their plugin can still build with OpenSearch Dashboards sooner than later. For the upgrade we did a quick verification and the impact was minimal but since then there have been numerous package upgrades to resolve CVEs. If plugin owners run into any issues and need mitigation techniques please add to opensearch-project/OpenSearch-Dashboards#1206.
Should we add verifying plugins work w/ Node.js upgrade as part of the 2.0.0 release campaign issues. Or is this only for campaigns that are also a part of Opensearch core and not dashboards.
Added as part of the campaign now.
Thanks.
elfisher
commented
2 years ago @peterzhuamazon this says preview, but this is a release candidate. Can we update accordingly?
elfisher
commented
2 years ago For example the manifests say 'alpha' but it should say 'rc'.
bbarani
commented
2 years ago @dblock @elfisher Can you please confirm the naming convention for the release since it involves multiple changes? Can we change the qualifier to rc instead of alpha1? This also require changes to the plugin CI as they rely on the exact name (with the qualifier) so we need to finalize the qualifier as soon as possible.
elfisher
commented
2 years ago @dblock 'rc1' work for you?
dblock
commented
2 years ago @elfisher rc1 works for me
peterzhuamazon
commented
2 years ago @elfisher @dblock I change title back to preview, and add rc1 in the campaign section.
dblock
commented
2 years ago @elfisher @dblock I change title back to preview, and add rc1 in the campaign section.
We're calling it RC though, so I changed it back to RC :) We did agree to finish the alpha1 qualifier work, then increment to rc1 next.
peterzhuamazon
commented
2 years ago @elfisher @dblock I change title back to preview, and add rc1 in the campaign section.
We're calling it RC though, so I changed it back to RC :) We did agree to finish the
alpha1qualifier work, then increment torc1next.
Could you help change the title of all component issues to RC1 as well? Thanks @dblock
cliu123
commented
2 years ago Starting OpenSearch 2.0.0-alpha1 failed. This looks like pointing to the cluster.initial_master_nodes -> cluster.initial_cluster_manager_nodes renaming.
Even with cluster.initial_master_nodes: smoketestnode in opensearch.yml, still see the following error:
022-04-05T08:14:51,327][INFO ][o.o.n.Node ] [smoketestnode] initialized
[2022-04-05T08:14:51,327][INFO ][o.o.n.Node ] [smoketestnode] starting ...
[2022-04-05T08:14:51,435][INFO ][o.o.t.TransportService ] [smoketestnode] publish_address {192.168.1.70:9300}, bound_addresses {[::]:9300}
[2022-04-05T08:14:51,739][INFO ][o.o.b.BootstrapChecks ] [smoketestnode] bound or publishing to a non-loopback address, enforcing bootstrap checks
ERROR: [1] bootstrap checks failed
[1]: the default discovery settings are unsuitable for production use; at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_cluster_manager_nodes / cluster.initial_master_nodes] must be configured
ERROR: OpenSearch did not exit normally - check the logs at /Users/cgliu/git/opensearch-2.0.0-alpha1/logs/opensearch.log
[2022-04-05T08:14:51,746][INFO ][o.o.n.Node ] [smoketestnode] stopping ...
[2022-04-05T08:14:51,758][INFO ][o.o.n.Node ] [smoketestnode] stopped
[2022-04-05T08:14:51,758][INFO ][o.o.n.Node ] [smoketestnode] closing ...
[2022-04-05T08:14:51,766][INFO ][o.o.n.Node ] [smoketestnode] closed@cliu123 Open a bug on OpenSearch?
peterzhuamazon
commented
2 years ago 20220418:
Tar integTest Results:
2022-04-17 11:59:04 ERROR | alerting | with-security | FAIL | 1 |
2022-04-17 11:59:04 INFO | alerting | without-security | PASS | 0 |
2022-04-17 11:59:04 INFO | anomaly-detection | with-security | PASS | 0 |
2022-04-17 11:59:04 INFO | anomaly-detection | without-security | PASS | 0 |
2022-04-17 11:59:04 INFO | asynchronous-search | with-security | PASS | 0 |
2022-04-17 11:59:04 INFO | asynchronous-search | without-security | PASS | 0 |
2022-04-17 11:59:04 INFO | dashboards-reports | without-security | PASS | 0 |
2022-04-17 11:59:04 INFO | index-management | with-security | PASS | 0 |
2022-04-17 11:59:04 ERROR | index-management | without-security | FAIL | 1 |
2022-04-17 11:59:04 INFO | k-NN | with-security | PASS | 0 |
2022-04-17 11:59:04 INFO | k-NN | without-security | PASS | 0 |
2022-04-17 11:59:04 ERROR | ml-commons | with-security | FAIL | 1 |
2022-04-17 11:59:04 INFO | ml-commons | without-security | PASS | 0 |
2022-04-17 11:59:04 ERROR | notifications | with-security | FAIL | 1 |
2022-04-17 11:59:04 INFO | notifications | without-security | PASS | 0 |
2022-04-17 11:59:04 INFO | sql | with-security | PASS | 0 |
2022-04-17 11:59:04 INFO | sql | without-security | PASS | 0 |20220421: 2606 OS
2022-04-21 19:56:19 INFO | alerting | with-security | PASS | 0 |
2022-04-21 19:56:19 INFO | alerting | without-security | PASS | 0 |
2022-04-21 19:56:19 INFO | anomaly-detection | with-security | PASS | 0 |
2022-04-21 19:56:19 INFO | anomaly-detection | without-security | PASS | 0 |
2022-04-21 19:56:19 INFO | asynchronous-search | with-security | PASS | 0 |
2022-04-21 19:56:19 INFO | asynchronous-search | without-security | PASS | 0 |
2022-04-21 19:56:19 INFO | dashboards-reports | without-security | PASS | 0 |
2022-04-21 19:56:19 ERROR | index-management | with-security | FAIL | 1 |
2022-04-21 19:56:19 ERROR | index-management | without-security | FAIL | 1 |
2022-04-21 19:56:19 INFO | k-NN | with-security | PASS | 0 |
2022-04-21 19:56:19 INFO | k-NN | without-security | PASS | 0 |
2022-04-21 19:56:19 INFO | ml-commons | with-security | PASS | 0 |
2022-04-21 19:56:19 INFO | ml-commons | without-security | PASS | 0 |
2022-04-21 19:56:19 ERROR | notifications | with-security | FAIL | 1 |
2022-04-21 19:56:19 INFO | notifications | without-security | PASS | 0 |
2022-04-21 19:56:19 INFO | opensearch-observability | without-security | PASS | 0 |
2022-04-21 19:56:19 INFO | sql | with-security | PASS | 0 |
2022-04-21 19:56:19 INFO | sql | without-security | PASS | 0 |20220421: 2611 OS results:
IM with-security is flaky, same as without-security, tho we have both success results now.
2022-04-22 05:34:29 INFO | index-management | without-security | PASS | 0 |
2022-04-22 05:10:56 INFO | alerting | with-security | PASS | 0 |
2022-04-22 05:10:56 INFO | alerting | without-security | PASS | 0 |
2022-04-22 05:10:56 INFO | anomaly-detection | with-security | PASS | 0 |
2022-04-22 05:10:56 INFO | anomaly-detection | without-security | PASS | 0 |
2022-04-22 05:10:56 INFO | asynchronous-search | with-security | PASS | 0 |
2022-04-22 05:10:56 INFO | asynchronous-search | without-security | PASS | 0 |
2022-04-22 05:10:56 INFO | dashboards-reports | without-security | PASS | 0 |
2022-04-22 05:10:56 INFO | index-management | with-security | PASS | 0 |
2022-04-22 05:10:56 ERROR | index-management | without-security | FAIL | 1 |
2022-04-22 05:10:56 INFO | k-NN | with-security | PASS | 0 |
2022-04-22 05:10:56 INFO | k-NN | without-security | PASS | 0 |
2022-04-22 05:10:56 INFO | ml-commons | with-security | PASS | 0 |
2022-04-22 05:10:56 INFO | ml-commons | without-security | PASS | 0 |
2022-04-22 05:10:56 ERROR | notifications | with-security | FAIL | 1 |
2022-04-22 05:10:56 INFO | notifications | without-security | PASS | 0 |
2022-04-22 05:10:56 INFO | opensearch-observability | without-security | PASS | 0 |
2022-04-22 05:10:56 INFO | sql | with-security | PASS | 0 |
2022-04-22 05:10:56 INFO | sql | without-security | PASS | 0 |20220421: 3014 OSD errors:
Spec Tests Passing Failing Pending Skipped
plugins/observability-dashboards 17:11 27 19 8 - -
plugins/alerting-dashboards-plugin 01:36 3 2 1 - -
plugins/alerting-dashboards-plugin 00:20 4 - 1 - 3
plugins/anomaly-detection-dashboards 01:52 6 4 2 - - @peterzhuamazon can you help me get an issue triaged as we are past code freeze? Process from the expanded release definitions PR
There is an issue in security plugin https://github.com/opensearch-project/security/pull/1746 that we are considering to merge post code freeze. There has been a setting that was renamed as part of inclusive naming in opensearch core which is used in security plugin scripts.
Pros: New inclusive terms usage is in alignment within our release, its a focused change that is validated by CI checks before entering the distribution build. There is a minimal risk of destabilizing perf/stress tests in progress Cons: Additional inclusive terminology changes are not in for security plugin, and has no outward facing impact making it a good candidate for the next patch release.
CC: @dblock @davidlago @CEHENKLE
peternied
commented
2 years ago There is an issue in security plugin opensearch-project/security#1746 that we are considering to merge post code freeze. There has been a setting that was renamed as part of inclusive naming in opensearch core which is used in security plugin scripts. Pros: New inclusive terms usage is in alignment within our release, its a focused change that is validated by CI checks before entering the distribution build. There is a minimal risk of destabilizing perf/stress tests in progress Cons: Additional inclusive terminology changes are not in for security plugin, and has no outward facing impact making it a good candidate for the next patch release.
[Recapping offline conversation] While this change would be valuable, it does not meet the requirements for the 2.0.0-rc1 release. There are concerns about modifying the setup scripts late in the process. We will add this to the next release.
peterzhuamazon
commented
2 years ago Use Docker-Compose to setup a cluster
docker-compose pulldocker-compose upOpenSearch docker 22f3cf41b694 linux/amd64 496.83 MB 49e226490665 linux/arm64 490.38 MB
docker pull opensearchstaging/opensearch:2.0.0-rc1 && docker run -it -p 9200:9200 -e "discovery.type=single-node" -e "DISABLE_SECURITY_PLUGIN=true" opensearchstaging/opensearch:2.0.0-rc1curl https://localhost:9200docker pull opensearchstaging/opensearch:2.0.0-rc1 && docker run -it -p 9200:9200 -e "discovery.type=single-node" opensearchstaging/opensearch:2.0.0-rc1curl --insecure https://admin:admin@localhost:9200OpenSearch-Dashboards docker bec4d1d7e5ef linux/amd64 315.51 MB 6b9722c2823a linux/arm64 318.87 MB
docker pull opensearchstaging/opensearch-dashboards:2.0.0-rc1 && docker run -it --network="host" -e "DISABLE_SECURITY_DASHBOARDS_PLUGIN=true" opensearchstaging/opensearch-dashboards:2.0.0-rc1https://localhost:5601docker pull opensearchstaging/opensearch-dashboards:2.0.0-rc1 && docker run -it --network="host" opensearchstaging/opensearch-dashboards:2.0.0-rc1https://localhost:5601Use TARs to deploy OpenSearch Manually
RPM artifacts and YUM repo files (testing purposes, same build number above):
OpenSearch RPM
OpenSearch YUM
OpenSearch Dashboards RPM
OpenSearch Dashboards YUM
From Docker Release
CEHENKLE
commented
2 years ago We were delayed starting testing because of a couple of issues (like https://github.com/opensearch-project/notifications/pull/429). so I'd like to move the release from Tuesday 26th to Thursday 28th.
I've updated the dates in the description, but please let me know if you have any concerns.
Please do not add any additional changes to 2.0.0 -- we're holding for testing at this time.
kotwanikunal
commented
2 years ago Performance Test Results
| Product/ Version | Architecture |
Description | Instance Type | Workload Details | Index Latency (ms)**** p50 | **Index Latency (ms)** p90 | **Index Latency (ms)** p99 | **Index Latency (ms)** p100 | Index Throughput (docs/s) p0 | Index Throughput (docs/s)**** p50 | Index Throughput (docs/s)**** p100 | Index Throughput (docs/s)**** Ops Count | Index Operation Counts Op Error Count | Index Operation Counts**** Error Rate | Query Latency (ms)**** p50 | Query Latency (ms)**** p90 | Query Latency (ms)**** p99 | Query Latency (ms)**** p100 | **Query Throughput (docs/s)** p0 | **Query Throughput (docs/s)** p50 | **Query Throughput (docs/s)** p100 | **Query Operation Counts** Ops Count | **Query Operation Counts** Op Error Count | Error Rate**Query Operation Counts** | CPU (%) p50 | CPU (%) p90 | CPU (%) p99 | CPU (%) p100 | Memory (%) p50 | Memory (%) p90 | Memory (%) p99 | Memory (%) p100 | GC (ms) Old | GC (ms) Young |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| OpenSearch - 1.3.0 | X64 | With Security | m5.xlarge | nyc_taxis/ 2 warmupIterations/ 3 testIterations | 2,043.519 | 2,758.102 | 4,748.371 | 7,043.104 | 36,184.391 | 37,770.62 | 44,188.625 | 46,434 | 0 | 0 | 368.594 | 377.903 | 386.466 | 394.664 | 1.731 | 1.742 | 1.753 | 1,510 | 0 | 0 | 96 | 97 | 97 | 97 | 59 | 86 | 74.5 | 86 | 417,244 | 1,083,631 |
| OpenSearch - 1.3.0 | X64 | Without Security | m5.xlarge | nyc_taxis/ 2 warmupIterations/ 3 testIterations | 1,906.334 | 2,577.319 | 4,414.418 | 7,146.647 | 39,169.781 | 40,723.06 | 48,473.305 | 46,130 | 0 | 0 | 345.892 | 351.94 | 362.478 | 366.735 | 1.727 | 1.742 | 1.757 | 1,510 | 0 | 0 | 97 | 98 | 98 | 98 | 56 | 82.4 | 73 | 87 | 282,526 | 993,500 |
| OpenSearch - 1.3.0 | ARM64 | With Security | m5.xlarge | nyc_taxis/ 2 warmupIterations/ 3 testIterations | 1,826.75 | 2,528.959 | 3,840.279 | 6,118.669 | 40,652.949 | 41,847.641 | 48,189.52 | 46,151 | 0 | 0 | 470.154 | 478.125 | 487.114 | 501.449 | 1.713 | 1.738 | 1.75 | 1,510 | 0 | 0 | 94 | 96 | 96 | 96 | 58 | 81 | 74 | 84 | 362,323 | 858,253 |
| OpenSearch - 1.3.0 | ARM64 | Without Security | m5.xlarge | nyc_taxis/ 2 warmupIterations/ 3 testIterations | 1,579.35 | 2,270.458 | 3,543.64 | 6,652.866 | 47,181.598 | 48,635.408 | 56,767.453 | 45,527 | 0 | 0 | 446.884 | 455.503 | 461.76 | 549.725 | 1.705 | 1.731 | 1.753 | 1,510 | 0 | 0 | 94 | 96 | 97 | 97 | 55 | 82 | 73 | 84 | 237,532 | 813,487 |
| OpenSearch - 2.0.0-rc1 | X64 | With Security | m5.xlarge | nyc_taxis/ 2 warmupIterations/ 3 testIterations | 2,399.902 | 3,163.177 | 6,063.703 | 9,496.247 | 30,893.346 | 32,339.089 | 36,713.641 | 46,975 | 0 | 0 | 370.263 | 383.39 | 401.38 | 419.555 | 1.724 | 1.738 | 1.751 | 1,510 | 0 | 0 | 97 | 97 | 98 | 98 | 51.286 | 82.08 | 65 | 90 | 0 | 1,350,101 |
| OpenSearch - 2.0.0-rc1 | X64 | Without Security | m5.xlarge | nyc_taxis/ 2 warmupIterations/ 3 testIterations | 2,175.882 | 2,878.53 | 5,506.905 | 8,791.765 | 34,214.957 | 36,234.605 | 41,583.063 | 46,632 | 0 | 0 | 305.212 | 316.337 | 335.036 | 350.975 | 1.725 | 1.74 | 1.755 | 1,510 | 0 | 0 | 98 | 98 | 99 | 99 | 50 | 88.94 | 64.2 | 93 | 0 | 1,078,876 |
| OpenSearch - 2.0.0-rc1 | ARM64 | With Security | m5.xlarge | nyc_taxis/ 2 warmupIterations/ 3 testIterations | 1,776.195 | 2,401.923 | 4,413.643 | 7,251.982 | 38,401.723 | 40,637.955 | 88,181.68 | 46,451 | 10,107 | 0.218 | 409.277 | 433.882 | 448.196 | 464.916 | 1.701 | 1.739 | 1.761 | 1,510 | 0 | 0 | 96 | 97 | 97 | 97 | 51 | 83.32 | 65 | 95 | 0 | 896,256 |
| OpenSearch - 2.0.0-rc1 | ARM64 | Without Security | m5.xlarge | nyc_taxis/ 2 warmupIterations/ 3 testIterations | 1,683.128 | 2,225.32 | 3,944.289 | 6,205.784 | 44,341.988 | 46,226.943 | 50,816.52 | 45,957 | 0 | 0 | 327.017 | 335.359 | 339.613 | 343.388 | 1.728 | 1.741 | 1.755 | 1,510 | 0 | 0 | 96 | 97 | 98 | 98 | 48 | 90.91 | 63 | 95 | 0 | 837,830 |
dlvenable
commented
2 years ago Will the RC1 include a Maven artifact in https://aws.oss.sonatype.org/content/repositories/releases? The 1.3.1 client appears to be incompatible with 2.0.0.
peterzhuamazon
commented
2 years ago Will the RC1 include a Maven artifact in
https://aws.oss.sonatype.org/content/repositories/releases? The 1.3.1 client appears to be incompatible with 2.0.0.
Every official release we will have artifacts in https://repo1.maven.org/maven2/org/opensearch/.
Just use
repositories {
mavenLocal()
maven { url "https://aws.oss.sonatype.org/content/repositories/snapshots" }
mavenCentral()
maven { url "https://plugins.gradle.org/m2/" }
}That works even better! Thanks for confirming that.
peterzhuamazon
commented
2 years ago RPM:
opensearch.x86_64 2.0.0.rc1-1 opensearch-2.x
opensearch-dashboards.x86_64 2.0.0.rc1-1 opensearch-dashboards-2.xopensearch.aarch64 2.0.0.rc1-1 opensearch-2.x
opensearch-dashboards.aarch64 2.0.0.rc1-1 opensearch-dashboards-2.x$ sudo yum install opensearch
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
Resolving Dependencies
--> Running transaction check
---> Package opensearch.x86_64 0:2.0.0.rc1-1 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
============================================================================================================================================================================================================================================================================================================================
Package Arch Version Repository Size
============================================================================================================================================================================================================================================================================================================================
Installing:
opensearch x86_64 2.0.0.rc1-1 opensearch-2.x 393 M
Transaction Summary
============================================================================================================================================================================================================================================================================================================================
Install 1 Package
Total download size: 393 M
Installed size: 640 M
Is this ok [y/d/N]: y
Downloading packages:
warning: <>: Header V4 RSA/SHA1 Signature, key ID 9310d3fc: NOKEY7% [================================================================================================================================= ] 30 MB/s | 382 MB 00:00:00 ETA
Public key for opensearch-2.0.0-rc1-linux-x64.rpm is not installed
opensearch-2.0.0-rc1-linux-x64.rpm | 393 MB 00:00:13
Retrieving key from https://artifacts.opensearch.org/publickeys/opensearch.pgp
Importing GPG key 0x9310D3FC:
Userid : "OpenSearch project <opensearch@amazon.com>"
Fingerprint: c5b7 4989 65ef d1c2 924b a9d5 39d3 1987 9310 d3fc
From : https://artifacts.opensearch.org/publickeys/opensearch.pgp
Is this ok [y/N]: y
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : opensearch-2.0.0.rc1-1.x86_64 1/1
### NOT starting on installation, please execute the following statements to configure opensearch service to start automatically using systemd
sudo systemctl daemon-reload
sudo systemctl enable opensearch.service
### You can start opensearch service by executing
sudo systemctl start opensearch.service
### Create opensearch demo certificates in /etc/opensearch/
See demo certs creation log in /var/log/opensearch/install_demo_configuration.log
Verifying : opensearch-2.0.0.rc1-1.x86_64 1/1
Installed:
opensearch.x86_64 0:2.0.0.rc1-1$ sudo yum install opensearch
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
amzn2-core | 3.7 kB 00:00:00
Resolving Dependencies
--> Running transaction check
---> Package opensearch.aarch64 0:2.0.0.rc1-1 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
============================================================================================================================================================================================================================================================================================================================
Package Arch Version Repository Size
============================================================================================================================================================================================================================================================================================================================
Installing:
opensearch aarch64 2.0.0.rc1-1 opensearch-2.x 389 M
Transaction Summary
============================================================================================================================================================================================================================================================================================================================
Install 1 Package
Total download size: 389 M
Installed size: 614 M
Is this ok [y/d/N]: y
Downloading packages:
warning: <>: Header V4 RSA/SHA1 Signature, key ID 9310d3fc: NOKEY[==================================================================================================================================== ] 6.3 MB/s | 387 MB 00:00:00 ETA
Public key for opensearch-2.0.0-rc1-linux-arm64.rpm is not installed
opensearch-2.0.0-rc1-linux-arm64.rpm | 389 MB 00:00:30
Retrieving key from https://artifacts.opensearch.org/publickeys/opensearch.pgp
Importing GPG key 0x9310D3FC:
Userid : "OpenSearch project <opensearch@amazon.com>"
Fingerprint: c5b7 4989 65ef d1c2 924b a9d5 39d3 1987 9310 d3fc
From : https://artifacts.opensearch.org/publickeys/opensearch.pgp
Is this ok [y/N]: y
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : opensearch-2.0.0.rc1-1.aarch64 1/1
### NOT starting on installation, please execute the following statements to configure opensearch service to start automatically using systemd
sudo systemctl daemon-reload
sudo systemctl enable opensearch.service
### You can start opensearch service by executing
sudo systemctl start opensearch.service
### Create opensearch demo certificates in /etc/opensearch/
See demo certs creation log in /var/log/opensearch/install_demo_configuration.log
Verifying : opensearch-2.0.0.rc1-1.aarch64 1/1
Installed:
opensearch.aarch64 0:2.0.0.rc1-1
Hey. We discovered a problem last night with PA and RPM. We're currently evaluating, but if we need to rebuild, it would push us off Thursday as a release date to (likely Tuesday). Please feel free to chime in on the issue, and if we do move the date to accommodate, we'll update here.
peternied
commented
2 years ago @peterzhuamazon I've created https://github.com/opensearch-project/opensearch-build/issues/2046 for retro items
CEHENKLE
commented
2 years ago Based on the time needed to retest to fix https://github.com/opensearch-project/opensearch-build/issues/2043 we'll be moving the release date of 2.0 RC1 to Tuesday May 3rd (updating this ticket, roadmap and blog post now).
We may need to move out the full 2.0 release date if we think that's not going to be enough time to get feedback, so please let us know. Please leave your feedback here on that issue.
Thanks!
CEHENKLE
commented
2 years ago BTW for some context on the 2.0-RC and 2.0 window. With the RC date moved, but the full release not moved, things look like this:
| Version | Feature Freeze | Release Date |
|---|---|---|
| 1.3.2 | April 29 2022 | May 05 2022 |
| 2.0.0 RC | Core: March 21st | |
| Plugins and Clients: April 18th | ||
| 2.0.0 GA | May 2nd | May 12th |
| 1.3.3 | June 3rd | June 9th |
Moving the release date to for RC-1 to May 3rd puts the freeze date for GA the day BEFORE the release.
I propose we shift GA out a week to:
| Version | Feature Freeze | Release Date |
|---|---|---|
| 1.3.2 | April 29 2022 | May 05 2022 |
| 2.0.0 RC | Core: March 21st | |
| Plugins and Clients: April 18th | ||
| 2.0.0 GA | ||
| 1.3.3 | June 3rd | June 9th |
I've moved the Freeze Date out 15 days, and the release date out 12 days. I think having more time to have the RC out in the wild is more important than a longer freeze date. WDYT?
ananzh
commented
2 years ago dlvenable
commented
2 years ago @CEHENKLE , Data Prepper 1.4 is releasing on May 10 and it will need the 2.0.0-RC1 client to be compatible with OpenSearch 2.0 clusters. The May 3rd release date for 2.0.0 RC1 works for this, but pushing it back further would risk OpenSearch 2.0 compatibility in Data Prepper 1.4.
CEHENKLE
commented
2 years ago @dlvenable Sounds like you may need a 1.5?
dlvenable
commented
2 years ago @CEHENKLE ,
That may be necessary if the Maven artifacts are not available in time for our release. If the 2.0.0-rc1 client is available in Maven this week though, we can use it in Data Prepper for the 1.4 release.
Broadly speaking I was expressing a favorable vote for putting RC1 out sooner in response to:
I think having more time to have the RC out in the wild is more important than a longer freeze date. WDYT?
dlvenable
commented
2 years ago Data Prepper already has a 1.5 scheduled. But, we had hoped to have the 2.0.0 support available in 1.4 prior to the release of OpenSearch 2.0.0 GA.
peterzhuamazon
commented
2 years ago Native Plugins:
./opensearch-plugin install repository-s3
-> Installing repository-s3
-> Downloading repository-s3 from opensearch
[=================================================] 100%
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: plugin requires additional permissions @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
* java.lang.RuntimePermission accessDeclaredMembers
* java.lang.RuntimePermission getClassLoader
* java.lang.reflect.ReflectPermission suppressAccessChecks
* java.net.NetPermission setDefaultAuthenticator
* java.net.SocketPermission * connect,resolve
* java.util.PropertyPermission opensearch.allow_insecure_settings read,write
See http://docs.oracle.com/javase/8/docs/technotes/guides/security/permissions.html
for descriptions of what these permissions allow and the associated risks.
Continue with installation? [y/N]y
-> Installed repository-s3 with folder name repository-s3
% ./opensearch-plugin install repository-azure
-> Installing repository-azure
-> Downloading repository-azure from opensearch
[=================================================] 100%
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: plugin requires additional permissions @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
* java.lang.RuntimePermission accessDeclaredMembers
* java.lang.RuntimePermission setContextClassLoader
* java.lang.RuntimePermission setFactory
* java.lang.reflect.ReflectPermission suppressAccessChecks
* java.net.NetPermission getProxySelector
* java.net.NetPermission setDefaultAuthenticator
* java.net.SocketPermission * connect,resolve
See http://docs.oracle.com/javase/8/docs/technotes/guides/security/permissions.html
for descriptions of what these permissions allow and the associated risks.
Continue with installation? [y/N]y
-> Installed repository-azure with folder name repository-azureMaven Central Release:
https://repo1.maven.org/maven2/org/opensearch/opensearch/2.0.0-rc1
Release OpenSearch and OpenSearch Dashboards 2.0.0 (RC1)
I noticed that a manifest was automatically created in manifests/2.0.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 @mention them on this issue for help. There are linked issues on components of the release where individual components can be tracked. More details are included in the Maintainers [Release owner](https://github.com/opensearch-project/opensearch-build/blob/main/MAINTAINERS.md#release-owner) section. ## 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 in their repositories. 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 updated based on the status of the component issues.
Preparation
__REPLACE_RELEASE-__placeholders have actual dates.CI/CD (Feature Freeze) - 2022/03/21
Campaigns
Code Complete - 2022/03/22 - 2022/04/18
Release testing - 2022/04/19 - 2022/04/21
Performance testing validation - 2022/04/19 - 2022/04/22
- [ ] Longevity tests do not show any issuesRelease -
2022/04/25 - 2022/04/26~~ 2022/04/27 - 2022/04/28~~ 2202/5/02 - 2022/05/03v2.0.0in all projects have been resolved.Post Release
Components
Legend
| Symbol | Meaning | | -------- | ---------- | | 🟢 | On track with overall release | | 🟡 | Missed last milestone | | 🔴 | Missed multiple milestones |
Issue tracking (Updated 2022/05/02 17:42PST)
Issues:
Improvements: