Closed github-actions[bot] closed 1 month ago
gaiksaya
commented
2 months ago Hey everyone! As the code cutoff date approaches, we will be cutting branches today at 5PM PST. We will be creating 2.17 branch based on 2.x branch. If you do not want the automation to create the branch for you, please create your own 2.17 branch as per your required commit before 5PM PST. Thanks!
gaiksaya
commented
2 months ago Successfully created missing 2.17 branches based on 2.x for all repos. See https://build.ci.opensearch.org/job/release-branch-creation/13/console All distribution builds will be using 2.17 branch now. Thanks!
gaiksaya
commented
2 months ago Hey everyone! Since too many PRs with too many commits are being submitted simultaneously at the last minute in OpenSearch repository, this lead to an edge case where scheduling gradle-check jobs is taking sometime (concurrent jobs max was set to 20 now to 30) and hence sending null to GHA marking the workflow run as failed. We are working on short-term fix to increase the timeout and get the jobs running. In order to accommodate this last minute bulk changes and requests from different maintainers and contributors, we are extending the code-freeze timeline to Sept 5, 11:00 am PST.
Please note this is the final extension, as we are already delayed by couple of days and cannot further extend this timeline without causing the delay in release date. Thanks!
opensearch-ci-bot
commented
2 months ago | Repo | Branch | CommitID | Commit Date | Release Notes Exists |
|---|---|---|---|---|
| OpenSearch | [6729220987d152270d1fce41689fdbf1e6165fd3] | 67292209 | 2024-09-07 | True |
| OpenSearch-Dashboards | [0d6c74b81f4353c411dec9ec63c3e1559cb0661b] | 0d6c74b | 2024-09-06 | True |
| alerting | [ccd279b946e2ba7d7dbf104d30daf81f1dc9a1c2] | True | ||
| alertingDashboards | [84722bca216f4ed18dcc50aa93cd59dfc8240817] | True | ||
| anomaly-detection | [47d159c71a3b935fe6c59f52b860a3bf54e5ea86] | True | ||
| anomalyDetectionDashboards | [c9a567f982db639d44500f7d873eed4dc60a36f4] | True | ||
| assistantDashboards | [361d5891c3b7e7329cf20a78450d492d1ce6d308] | 361d589 | 2024-09-06 | True |
| asynchronous-search | [5d1429275b74920dfd464fcfda6ce0c9693f230d] | True | ||
| common-utils | [15480c93af342cfcd5a5ac9c99de1ec364cdbd2c] | True | ||
| cross-cluster-replication | [0ebea49fd5dbc0977f9dd36c61fa0a8dfbe8af66] | True | ||
| custom-codecs | [d913b64e1f92cfc27e27b75a6705ec018f49d031] | True | ||
| customImportMapDashboards | [cc9b073e75123af75a33cdd4c29a65bb68242c9e] | True | ||
| flow-framework | [68e8973c04e6695ae336eac94137e339695bb1b9] | 68e8973 | 2024-09-06 | True |
| functionalTestDashboards | [2.17] | 20576000000000 | 2024-09-06 | False |
| ganttChartDashboards | [1357c301120e0c9053a9dbb1bf4cb2fe45fea303] | True | ||
| geospatial | [4ed00c4b524e1ceb9ee62aa9934b72a785f66088] | True | ||
| index-management | [56ea466d3978194448909bcf03699628ef4201e8] | True | ||
| indexManagementDashboards | [c488c3b556849758f3402e7850653ddde452d42d] | True | ||
| job-scheduler | [e4eba212afbfe08455630f4aadd46b498730a61f] | True | ||
| k-NN | [e111eb0ba8a3c88b1d141dcad2645bdc7f6ad631] | e111eb0 | 2024-09-06 | True |
| ml-commons | [5e6ac303d6217f13bc4d1837713da71d2a03922a] | 5e6ac30 | 2024-09-06 | True |
| mlCommonsDashboards | [63bb1e31d6b609cbc32e0e15c0b45e97af7275e5] | True | ||
| neural-search | [22f36c5f4f44d8efcd346f3cb7b40790e69dc4c8] | True | ||
| notifications | [bebea53ae6668bfc92a162b043de59e0613b03b2] | True | ||
| notifications-core | [bebea53ae6668bfc92a162b043de59e0613b03b2] | True | ||
| notificationsDashboards | [67cb2140c6bc762273739628557f72a47a376716] | 67cb214 | 2024-09-06 | True |
| observabilityDashboards | [0dca1ffb512c3667e54bcff5e9ec558c8a4a092d] | 0dca1ff | 2024-09-06 | True |
| opensearch-observability | [9d669cfe2a074bd6cfb405f46e979ea252102a24] | 9d669cf | 2024-09-06 | True |
| opensearch-reports | [a70ff96a32fa8b4939d8f74fabb49d8c9aeb1ecb] | True | ||
| opensearch-system-templates | [d709a0ca8151b79b7e4535b597f9457648baec76] | d709a0c | 2024-09-07 | True |
| performance-analyzer | [2302bb5b0a940b2f91b9912a365c78b834a71eb2] | 2302bb5 | 2024-09-06 | True |
| query-insights | [fb6afb2f7c051c1f08b6d4fe663679888b0b9e79] | True | ||
| queryWorkbenchDashboards | [6dc1030c27bf6152e273abe5cf64a7f3dcef3280] | True | ||
| reportsDashboards | [1aadb2e9a104b14954976410d43a638ee1b6c04f] | 1aadb2e | 2024-09-06 | True |
| searchRelevanceDashboards | [e1e8f7d1d51162b197cd3457e88fa4d70da9dba3] | e1e8f7d | 2024-09-05 | True |
| security | [aa0952c8e1382ad070f6f91b974a34fb4fea8800] | True | ||
| security-analytics | [9bea213aa85d77f02d143e0169178961522adbbf] | True | ||
| securityAnalyticsDashboards | [883ebdc324d2f2ec9e3b0d4f92ac4b20c35df1f2] | True | ||
| securityDashboards | [cc39b752d89237c1c1cdfe9e8e2979a985582554] | True | ||
| skills | [5e0fdf5bbba31a732a6c1d9bbbebf78448f6f595] | 5e0fdf5 | 2024-09-07 | True |
| sql | [7a641c07a835cb1248c1aa7d0411360e7df792c9] | 7a641c0 | 2024-09-06 | True |
harshavamsi
commented
2 months ago @gaiksaya @peterzhuamazon why is it that the CI does not create a PR like https://github.com/opensearch-project/opensearch-build/pull/4897, when 2.17 is cut? Can we automate this process once a branch is cut so that the BWC artifacts from main are built. Gradle checks on main are failing because 2.18 is the new version and there is no 2.17 artifact without the manifest update
gaiksaya
commented
2 months ago @gaiksaya @peterzhuamazon why is it that the CI does not create a PR like #4897, when 2.17 is cut? Can we automate this process once a branch is cut so that the BWC artifacts from main are built. Gradle checks on main are failing because 2.18 is the new version and there is no 2.17 artifact without the manifest update
The process goes like this: OpenSearch bumps version (Manually AFAIK) -> Build repo manifest workflow detects a new version -> Creates a new manifest -> The new manifest adds leads to snapshot creation of min and other artifacts
Manifest update that runs on schedule https://github.com/opensearch-project/opensearch-build/blob/main/jenkins/manifests-update.jenkinsFile#L17 since the it was not an urgent task. Is there any dependency on any artifact? I believe min snapshot? (Please correct if I am wrong) If there is any dependency on it, we can probably have a trigger based on version bump merge. Please feel free to add the item in retrospective issue https://github.com/opensearch-project/opensearch-build/issues/4909
harshavamsi
commented
2 months ago @gaiksaya @peterzhuamazon why is it that the CI does not create a PR like #4897, when 2.17 is cut? Can we automate this process once a branch is cut so that the BWC artifacts from main are built. Gradle checks on main are failing because 2.18 is the new version and there is no 2.17 artifact without the manifest update
The process goes like this: OpenSearch bumps version (Manually AFAIK) -> Build repo manifest workflow detects a new version -> Creates a new manifest.
Manifest update that runs on schedule https://github.com/opensearch-project/opensearch-build/blob/main/jenkins/manifests-update.jenkinsFile#L17 since the it was not an urgent task. Is there any dependency on any artifact? I believe min snapshot? (Please correct if I am wrong) If there is any dependency on it, we can probably have a trigger based on version bump merge. Please feel free to add the item in retrospective issue #4909
Thanks the cron update makes sense but I think it would be nicer to have a trigger. Will add to retrospective.
msfroh
commented
2 months ago I think our best bet for the future is to cut the release branch on core as the "freeze" trigger. Maybe core should freeze a couple of days before plugins?
Then backports to the release branch on core would only be for critical bug fixes. This would be in comparison to the past ~24 hours, where a flood of features get merged to main, backported to 2.x, and backported to release.
With the update to release+1 across main and 2.x, it would only disrupt merging of a small number of critical bug fixes (versus the current flood of last-minute features).
I'll bring it up in the retrospective.
kolchfa-aws
commented
2 months ago 
shiv0408
commented
1 month ago PRs approved for v2.17 but pending merge in main due to build failure since yesterday.
gargharsh3134
commented
1 month ago PR merged in main, but pending backport to 2.17: https://github.com/opensearch-project/OpenSearch/pull/15292
getsaurabh02
commented
1 month ago Maybe core should freeze a couple of days before plugins?
This is a valid point @msfroh and something we have been considering to have in place while announcing the schedule for next year releases.
SwethaGuptha
commented
1 month ago PR approved but pending merge: https://github.com/opensearch-project/OpenSearch/pull/15492
sachinpkale
commented
1 month ago PRs merged in main but pending backport to 2.17
PRs approved but pending merge to main (and pending backport to 2.17)
gaiksaya
commented
1 month ago Updating the release candidate status:
We did try to generate the RC and got a partial one. See OS: https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch/detail/distribution-build-opensearch/10269/pipeline OSD: https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch[…]il/distribution-build-opensearch-dashboards/7921/pipeline
Below plugins failed:
Release candidate creation was blocked until this was resolved. Since the fixes are now in, we have triggered RC again: OS: https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch/detail/distribution-build-opensearch/10271/pipeline OSD: https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch[…]il/distribution-build-opensearch-dashboards/7924/pipeline Thanks!
gaiksaya
commented
1 month ago
## RC 1 OpenSearch 10271 / OpenSearch Dashboards 7924 is ready for your test.
OpenSearch - [Build 10271](https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch/detail/distribution-build-opensearch/10271/pipeline)
OpenSearch Dashboards - [Build 7924](https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch-dashboards/detail/distribution-build-opensearch-dashboards/7924/pipeline)
- Use the following Docker-Compose to setup a cluster
docker-compose.yml
version: '3'
services:
opensearch-node1:
image: opensearchstaging/opensearch:2.17.0.10271
container_name: opensearch-node1
environment:
- cluster.name=opensearch-cluster
- node.name=opensearch-node1
- discovery.seed_hosts=opensearch-node1,opensearch-node2
- cluster.initial_cluster_manager_nodes=opensearch-node1,opensearch-node2
- bootstrap.memory_lock=true # along with the memlock settings below, disables swapping
- OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536 # maximum number of open files for the OpenSearch user, set to at least 65536 on modern systems
hard: 65536
volumes:
- opensearch-data1:/usr/share/opensearch/data
ports:
- 9200:9200
- 9600:9600 # required for Performance Analyzer
networks:
- opensearch-net
opensearch-node2:
image: opensearchstaging/opensearch:2.17.0.10271
container_name: opensearch-node2
environment:
- cluster.name=opensearch-cluster
- node.name=opensearch-node2
- discovery.seed_hosts=opensearch-node1,opensearch-node2
- cluster.initial_cluster_manager_nodes=opensearch-node1,opensearch-node2
- bootstrap.memory_lock=true
- OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536
hard: 65536
volumes:
- opensearch-data2:/usr/share/opensearch/data
networks:
- opensearch-net
opensearch-dashboards:
image: opensearchstaging/opensearch-dashboards:2.17.0.7924
container_name: opensearch-dashboards
ports:
- 5601:5601
expose:
- "5601"
environment:
OPENSEARCH_HOSTS: '["https://opensearch-node1:9200","https://opensearch-node2:9200"]'
networks:
- opensearch-net
volumes:
opensearch-data1:
opensearch-data2:
networks:
opensearch-net:
prudhvigodithi
commented
1 month ago
- Use the https://metrics.opensearch.org/_dashboards/goto/9ed74dd90eb31c7b83f3542e43328088?security_tenant=global.
- Filter by the
distribution_build_number. Use 10271 for OpenSearch and 7924 for OpenSearch Dashboards. Example when filtered with 10271 we can see all the passed/failed OpenSearch components.
Here is the direct dashboard link&_a=(description:'OpenSearch%20Release%20Build%20and%20Integration%20Test%20Results',filters:!(('$state':(store:appState),meta:(alias:!n,disabled:!f,index:'16f55f10-4977-11ef-8565-15a1562cd0a0',key:distribution_build_number,negate:!f,params:!('10271','7924'),type:phrases,value:'10271,%207924'),query:(bool:(minimum_should_match:1,should:!((match_phrase:(distribution_build_number:'10271')),(match_phrase:(distribution_build_number:'7924')))))),('$state':(store:appState),meta:(alias:!n,controlledBy:'1721852613904',disabled:!f,index:'16f55f10-4977-11ef-8565-15a1562cd0a0',key:version,negate:!f,params:(query:'2.17.0'),type:phrase),query:(match_phrase:(version:'2.17.0')))),fullScreenMode:!f,options:(hidePanelTitles:!f,useMargins:!t),query:(language:kuery,query:''),timeRestore:!t,title:'OpenSearch%20Release%20Build%20and%20Integration%20Test%20Results',viewMode:view)) filtered with 10271, 7924 to get the and integration test results.
Thank you
gaiksaya
commented
1 month ago
## RC 2 OpenSearch 10274 / OpenSearch Dashboards 7926 is ready for your test.
OpenSearch - [Build 10274](https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch/detail/distribution-build-opensearch/10274/pipeline)
OpenSearch Dashboards - [Build 7926](https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch-dashboards/detail/distribution-build-opensearch-dashboards/7926/pipeline)
- Use the following Docker-Compose to setup a cluster
docker-compose.yml
version: '3'
services:
opensearch-node1:
image: opensearchstaging/opensearch:2.17.0.10274
container_name: opensearch-node1
environment:
- cluster.name=opensearch-cluster
- node.name=opensearch-node1
- discovery.seed_hosts=opensearch-node1,opensearch-node2
- cluster.initial_cluster_manager_nodes=opensearch-node1,opensearch-node2
- bootstrap.memory_lock=true # along with the memlock settings below, disables swapping
- OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536 # maximum number of open files for the OpenSearch user, set to at least 65536 on modern systems
hard: 65536
volumes:
- opensearch-data1:/usr/share/opensearch/data
ports:
- 9200:9200
- 9600:9600 # required for Performance Analyzer
networks:
- opensearch-net
opensearch-node2:
image: opensearchstaging/opensearch:2.17.0.10274
container_name: opensearch-node2
environment:
- cluster.name=opensearch-cluster
- node.name=opensearch-node2
- discovery.seed_hosts=opensearch-node1,opensearch-node2
- cluster.initial_cluster_manager_nodes=opensearch-node1,opensearch-node2
- bootstrap.memory_lock=true
- OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536
hard: 65536
volumes:
- opensearch-data2:/usr/share/opensearch/data
networks:
- opensearch-net
opensearch-dashboards:
image: opensearchstaging/opensearch-dashboards:2.17.0.7926
container_name: opensearch-dashboards
ports:
- 5601:5601
expose:
- "5601"
environment:
OPENSEARCH_HOSTS: '["https://opensearch-node1:9200","https://opensearch-node2:9200"]'
networks:
- opensearch-net
volumes:
opensearch-data1:
opensearch-data2:
networks:
opensearch-net:
gaiksaya
commented
1 month ago Looking at this workflow run (tar x64) we have below plugins failing the integration tests for
gaiksaya
commented
1 month ago
## RC 3 OpenSearch 10284 / OpenSearch Dashboards 7931 is ready for your test.
OpenSearch - [Build 10284](https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch/detail/distribution-build-opensearch/10284/pipeline)
OpenSearch Dashboards - [Build 7931](https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch-dashboards/detail/distribution-build-opensearch-dashboards/7931/pipeline)
- Use the following Docker-Compose to setup a cluster
docker-compose.yml
version: '3'
services:
opensearch-node1:
image: opensearchstaging/opensearch:2.17.0.10284
container_name: opensearch-node1
environment:
- cluster.name=opensearch-cluster
- node.name=opensearch-node1
- discovery.seed_hosts=opensearch-node1,opensearch-node2
- cluster.initial_cluster_manager_nodes=opensearch-node1,opensearch-node2
- bootstrap.memory_lock=true # along with the memlock settings below, disables swapping
- OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536 # maximum number of open files for the OpenSearch user, set to at least 65536 on modern systems
hard: 65536
volumes:
- opensearch-data1:/usr/share/opensearch/data
ports:
- 9200:9200
- 9600:9600 # required for Performance Analyzer
networks:
- opensearch-net
opensearch-node2:
image: opensearchstaging/opensearch:2.17.0.10284
container_name: opensearch-node2
environment:
- cluster.name=opensearch-cluster
- node.name=opensearch-node2
- discovery.seed_hosts=opensearch-node1,opensearch-node2
- cluster.initial_cluster_manager_nodes=opensearch-node1,opensearch-node2
- bootstrap.memory_lock=true
- OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536
hard: 65536
volumes:
- opensearch-data2:/usr/share/opensearch/data
networks:
- opensearch-net
opensearch-dashboards:
image: opensearchstaging/opensearch-dashboards:2.17.0.7931
container_name: opensearch-dashboards
ports:
- 5601:5601
expose:
- "5601"
environment:
OPENSEARCH_HOSTS: '["https://opensearch-node1:9200","https://opensearch-node2:9200"]'
networks:
- opensearch-net
volumes:
opensearch-data1:
opensearch-data2:
networks:
opensearch-net:
gaiksaya
commented
1 month ago
## RC 4 OpenSearch 10288 / OpenSearch Dashboards 7935 is ready for your test.
OpenSearch - [Build 10288](https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch/detail/distribution-build-opensearch/10288/pipeline)
OpenSearch Dashboards - [Build 7935](https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch-dashboards/detail/distribution-build-opensearch-dashboards/7935/pipeline)
- Use the following Docker-Compose to setup a cluster
docker-compose.yml
version: '3'
services:
opensearch-node1:
image: opensearchstaging/opensearch:2.17.0.10288
container_name: opensearch-node1
environment:
- cluster.name=opensearch-cluster
- node.name=opensearch-node1
- discovery.seed_hosts=opensearch-node1,opensearch-node2
- cluster.initial_cluster_manager_nodes=opensearch-node1,opensearch-node2
- bootstrap.memory_lock=true # along with the memlock settings below, disables swapping
- OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536 # maximum number of open files for the OpenSearch user, set to at least 65536 on modern systems
hard: 65536
volumes:
- opensearch-data1:/usr/share/opensearch/data
ports:
- 9200:9200
- 9600:9600 # required for Performance Analyzer
networks:
- opensearch-net
opensearch-node2:
image: opensearchstaging/opensearch:2.17.0.10288
container_name: opensearch-node2
environment:
- cluster.name=opensearch-cluster
- node.name=opensearch-node2
- discovery.seed_hosts=opensearch-node1,opensearch-node2
- cluster.initial_cluster_manager_nodes=opensearch-node1,opensearch-node2
- bootstrap.memory_lock=true
- OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536
hard: 65536
volumes:
- opensearch-data2:/usr/share/opensearch/data
networks:
- opensearch-net
opensearch-dashboards:
image: opensearchstaging/opensearch-dashboards:2.17.0.7935
container_name: opensearch-dashboards
ports:
- 5601:5601
expose:
- "5601"
environment:
OPENSEARCH_HOSTS: '["https://opensearch-node1:9200","https://opensearch-node2:9200"]'
networks:
- opensearch-net
volumes:
opensearch-data1:
opensearch-data2:
networks:
opensearch-net:
jainankitk
commented
1 month ago I think our best bet for the future is to cut the release branch on core as the "freeze" trigger. Maybe core should freeze a couple of days before plugins?
@msfroh - I was discussing something very similar with @andrross offline. IMO, RC1 generation flow should cut the release branch for core and plugins, automatically serving as the "freeze" trigger. After that we can bump the versions for 2.x and main branches to avoid breaking build before the code freeze. But yeah, let us discuss further during the retrospective!
rishabh6788
commented
1 month ago No significant performance callouts for 2.17 release compared to 2.16. No notable regression or improvement detected in 2.17 compared to 2.16.
gaiksaya
commented
1 month ago
## RC 5 OpenSearch 10289 / OpenSearch Dashboards 7936 is ready for your test.
OpenSearch - [Build 10289](https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch/detail/distribution-build-opensearch/10289/pipeline)
OpenSearch Dashboards - [Build 7936](https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch-dashboards/detail/distribution-build-opensearch-dashboards/7936/pipeline)
- Use the following Docker-Compose to setup a cluster
docker-compose.yml
version: '3'
services:
opensearch-node1:
image: opensearchstaging/opensearch:2.17.0.10289
container_name: opensearch-node1
environment:
- cluster.name=opensearch-cluster
- node.name=opensearch-node1
- discovery.seed_hosts=opensearch-node1,opensearch-node2
- cluster.initial_cluster_manager_nodes=opensearch-node1,opensearch-node2
- bootstrap.memory_lock=true # along with the memlock settings below, disables swapping
- OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536 # maximum number of open files for the OpenSearch user, set to at least 65536 on modern systems
hard: 65536
volumes:
- opensearch-data1:/usr/share/opensearch/data
ports:
- 9200:9200
- 9600:9600 # required for Performance Analyzer
networks:
- opensearch-net
opensearch-node2:
image: opensearchstaging/opensearch:2.17.0.10289
container_name: opensearch-node2
environment:
- cluster.name=opensearch-cluster
- node.name=opensearch-node2
- discovery.seed_hosts=opensearch-node1,opensearch-node2
- cluster.initial_cluster_manager_nodes=opensearch-node1,opensearch-node2
- bootstrap.memory_lock=true
- OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536
hard: 65536
volumes:
- opensearch-data2:/usr/share/opensearch/data
networks:
- opensearch-net
opensearch-dashboards:
image: opensearchstaging/opensearch-dashboards:2.17.0.7936
container_name: opensearch-dashboards
ports:
- 5601:5601
expose:
- "5601"
environment:
OPENSEARCH_HOSTS: '["https://opensearch-node1:9200","https://opensearch-node2:9200"]'
networks:
- opensearch-net
volumes:
opensearch-data1:
opensearch-data2:
networks:
opensearch-net:
gaiksaya
commented
1 month ago OpenSearch - Build 10292 OpenSearch Dashboards - Build 7942
Use the following Docker-Compose to setup a cluster
version: '3'
services:
opensearch-node1:
image: opensearchstaging/opensearch:2.17.0.10292
container_name: opensearch-node1
environment:
- cluster.name=opensearch-cluster
- node.name=opensearch-node1
- discovery.seed_hosts=opensearch-node1,opensearch-node2
- cluster.initial_cluster_manager_nodes=opensearch-node1,opensearch-node2
- bootstrap.memory_lock=true # along with the memlock settings below, disables swapping
- OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536 # maximum number of open files for the OpenSearch user, set to at least 65536 on modern systems
hard: 65536
volumes:
- opensearch-data1:/usr/share/opensearch/data
ports:
- 9200:9200
- 9600:9600 # required for Performance Analyzer
networks:
- opensearch-net
opensearch-node2:
image: opensearchstaging/opensearch:2.17.0.10292
container_name: opensearch-node2
environment:
- cluster.name=opensearch-cluster
- node.name=opensearch-node2
- discovery.seed_hosts=opensearch-node1,opensearch-node2
- cluster.initial_cluster_manager_nodes=opensearch-node1,opensearch-node2
- bootstrap.memory_lock=true
- OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536
hard: 65536
volumes:
- opensearch-data2:/usr/share/opensearch/data
networks:
- opensearch-net
opensearch-dashboards:
image: opensearchstaging/opensearch-dashboards:2.17.0.7942
container_name: opensearch-dashboards
ports:
- 5601:5601
expose:
- "5601"
environment:
OPENSEARCH_HOSTS: '["https://opensearch-node1:9200","https://opensearch-node2:9200"]'
networks:
- opensearch-net
volumes:
opensearch-data1:
opensearch-data2:
networks:
opensearch-net:
docker-compose pull.docker-compose up.OpenSearch docker 2.17.0.10292
docker pull opensearchstaging/opensearch:2.17.0.10292 && docker run -it -p 9200:9200 -e "discovery.type=single-node" -e "DISABLE_SECURITY_PLUGIN=true" opensearchstaging/opensearch:2.17.0.10292curl http://localhost:9200/docker pull opensearchstaging/opensearch:2.17.0.10292 && docker run -it -p 9200:9200 -e "discovery.type=single-node" -e "OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!" opensearchstaging/opensearch:2.17.0.10292curl --insecure 'https://admin:myStrongPassword123!@localhost:9200/'OpenSearch-Dashboards docker 2.17.0.7942
docker pull opensearchstaging/opensearch-dashboards:2.17.0.7942 && docker run -it --network="host" -e "DISABLE_SECURITY_DASHBOARDS_PLUGIN=true" opensearchstaging/opensearch-dashboards:2.17.0.7942http://localhost:5601/docker pull opensearchstaging/opensearch-dashboards:2.17.0.7942 && docker run -it --network="host" opensearchstaging/opensearch-dashboards:2.17.0.7942http://localhost:5601/Use TARs to deploy OpenSearch Manually
Check how to install opensearch and dashboards on different platforms
Filter by the distribution_build_number. Use 10292 for OpenSearch and 7942 for OpenSearch Dashboards.
Example when filtered with 10292 we can see all the passed/failed OpenSearch components.
See results here&_a=(description:'OpenSearch%20Release%20Build%20and%20Integration%20Test%20Results',filters:!(('$state':(store:appState),meta:(alias:!n,controlledBy:'1721852613904',disabled:!f,index:'16f55f10-4977-11ef-8565-15a1562cd0a0',key:version,negate:!f,params:(query:'2.17.0'),type:phrase),query:(match_phrase:(version:'2.17.0'))),('$state':(store:appState),meta:(alias:!n,controlledBy:'1722482131538',disabled:!f,index:'16f55f10-4977-11ef-8565-15a1562cd0a0',key:rc_number,negate:!f,params:(query:6),type:phrase),query:(match_phrase:(rc_number:6))),('$state':(store:appState),meta:(alias:!n,disabled:!f,index:'23eb6520-4977-11ef-bbdd-39a9b324a5aa',key:distribution_build_number,negate:!f,params:!('10292','7942'),type:phrases,value:'10292,%207942'),query:(bool:(minimum_should_match:1,should:!((match_phrase:(distribution_build_number:'10292')),(match_phrase:(distribution_build_number:'7942'))))))),fullScreenMode:!f,options:(hidePanelTitles:!f,useMargins:!t),query:(language:kuery,query:''),timeRestore:!t,title:'OpenSearch%20Release%20Build%20and%20Integration%20Test%20Results',viewMode:view))
Find the list of the created AUTOCUT issues here https://github.com/issues?page=1&q=is%3Aopen+is%3Aissue+user%3Aopensearch-project+label%3Av2.17.0+label%3Aautocut+%5BAUTOCUT%5D+in%3Atitle.
Thank you
gaiksaya
commented
1 month ago Updating the status of 2.17.0 as per today Go/No-Go call: The decision for this call was a NO-GO based on below status:
gaiksaya
commented
1 month ago We have next RC which only contains OpenSearch Dashboards: https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch[…]il/distribution-build-opensearch-dashboards/7944/pipeline
We are still seeing the CVE in the scan. Working with the core team to see if is actually an issue or false positive.
gaiksaya
commented
1 month ago 2 components had to patch the software to resolve high CVEs. We have generated new RC with those changes. https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch-dashboards/detail/distribution-build-opensearch-dashboards/7946/pipeline/1392/
We will continue to run tests and try to meet the exit criteria. Thanks!
gaiksaya
commented
1 month ago All integration tests are passing for all components. Below are the final release candidates for the release.
gaiksaya
commented
1 month ago We unanimously received a GO for tomorrow’s 2.17.0 release in today's Go/No-Go call. We still have documentation PRs in review. However, documentation team is confident to get in before tomorrow’s release. Thanks!
prudhvigodithi
commented
1 month ago ./bin/opensearch-plugin install repository-s3
-> Installing repository-s3
-> Downloading repository-s3 from opensearch
[=================================================] 100%??
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: plugin requires additional permissions @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
* java.io.FilePermission config#plus read
* java.lang.RuntimePermission accessDeclaredMembers
* java.lang.RuntimePermission getClassLoader
* java.lang.RuntimePermission setContextClassLoader
* java.lang.reflect.ReflectPermission suppressAccessChecks
* java.net.NetPermission setDefaultAuthenticator
* java.net.SocketPermission * connect,resolve
* java.util.PropertyPermission aws.configFile read,write
* java.util.PropertyPermission aws.sharedCredentialsFile read,write
* java.util.PropertyPermission opensearch.allow_insecure_settings read,write
* java.util.PropertyPermission opensearch.path.conf 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-s3curl http://localhost:9200/_cat/plugins -u 'admin:myStrongPassword123@456'
opensearch opensearch-alerting 2.17.0.0
opensearch opensearch-anomaly-detection 2.17.0.0
opensearch opensearch-asynchronous-search 2.17.0.0
opensearch opensearch-cross-cluster-replication 2.17.0.0
opensearch opensearch-custom-codecs 2.17.0.0
opensearch opensearch-flow-framework 2.17.0.0
opensearch opensearch-geospatial 2.17.0.0
opensearch opensearch-index-management 2.17.0.0
opensearch opensearch-job-scheduler 2.17.0.0
opensearch opensearch-knn 2.17.0.0
opensearch opensearch-ml 2.17.0.0
opensearch opensearch-neural-search 2.17.0.0
opensearch opensearch-notifications 2.17.0.0
opensearch opensearch-notifications-core 2.17.0.0
opensearch opensearch-observability 2.17.0.0
opensearch opensearch-performance-analyzer 2.17.0.0
opensearch opensearch-reports-scheduler 2.17.0.0
opensearch opensearch-security 2.17.0.0
opensearch opensearch-security-analytics 2.17.0.0
opensearch opensearch-skills 2.17.0.0
opensearch opensearch-sql 2.17.0.0
opensearch opensearch-system-templates 2.17.0.0
opensearch query-insights 2.17.0.0
opensearch repository-s3 2.17.0GPG key validation looks good as well:
% gpg --verify opensearch-2.17.0-linux-x64.tar.gz.sig opensearch-2.17.0-linux-x64.tar.gz
gpg: Signature made Tue 17 Sep 2024 08:40:20 PM UTC using RSA key ID 542C03B4
gpg: Good signature from "OpenSearch project <opensearch@amazon.com>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: C5B7 4989 65EF D1C2 924B A9D5 39D3 1987 9310 D3FC
Subkey fingerprint: 2187 3199 B103 0FCD 49DA 83F8 C2EE 2AF6 542C 03B4🎉 OpenSearch and OpenSearch-Dashboards 2.17.0 have been release to the public. This release includes a host of new features, enhancements, and bug fixes. For detailed information, please check out the release notes and release blog.
For feedback and suggestions please see the retrospective issue: https://github.com/opensearch-project/opensearch-build/issues/4909
Closing this issue as post release activities are completed as well.
Release OpenSearch and OpenSearch Dashboards 2.17.0
I noticed that a manifest was automatically created in manifests/2.17.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 (Release Manager) 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. For more information check the the [Release Process OpenSearch Guide](https://github.com/opensearch-project/opensearch-build/wiki/Releasing-the-Distribution).
Please refer to the following link for the release version dates: Release Schedule and Maintenance Policy.
Entrance Criteria
OpenSearch 2.17.0 exit criteria status:
OpenSearch-Dashboards 2.17.0 exit criteria status:
Preparation
Campaigns
Release Branch and Version Increment - Ends Sept 03, 2024
Feature Freeze - Ends Sept 03, 2024
Code Complete - Ends ~Sept 04, 2024~ Sept 05, 2024
Release Candidate Creation and Testing - Starts Sept 04, 2024 at 4PM PDT
Performance testing validation - Ends Sept 11, 2024
Pre Release - _Ends _Sept 16, 2024
Release - Ends Sept 17, 2024
Release Checklist.
Release Checklist
### Pre-Release activities - [x] Promote Repos. - - [x] OS - - [x] OSD - [x] Promote Artifacts. - - [x] Windows - - [x] Linux Debian - - [x] Linux RPM - - [x] Linux TAR - [x] Consolidated Release Notes. ### Release activities - [x] Docker Promotion. - [x] Release Validation part 1. - - [x] OpenSearch and OpenSearch Dashboard Validation. - - [x] Validate the native plugin installation. - [x] Merge consolidated release notes PR. - [x] Website and Documentation Changes. - - [x] Merge staging website PR. - - [x] Promote the website changes to prod. - - [x] Add website alert. - [x] Release Validation part 2. - - [x] Validate the artifact download URL's and signatures. - [x] Release Validation part 3. - - [x] Trigger the validation build (Search for `Completed validation for <>` in the logs). - [x] Maven Promotion. - [x] Publish blog posts. - [x] Advertise on Social Media. - [x] Post on public slack and Github Release issue.
Post Release
Components
Replace with links to all component tracking issues.
OpenSearch Dashboards
Legend
| Symbol | Meaning | | -------- | ---------- | | :green_circle: | On track with overall release | | :yellow_circle: | Missed last milestone | | :red_circle: | Missed multiple milestones |