[RELEASE] Release version 2.13.0

[github-actions[bot]]

Release OpenSearch and OpenSearch Dashboards 2.13.0

I noticed that a manifest was automatically created in manifests/2.13.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

Criteria	Status	Description	Comments
Documentation draft PRs are up and in tech review for all component changes	:green_circle:
Sanity testing is done for all components	:green_circle:
~Code coverage has not decreased (all new code has tests)~			We do not have automated checker for this check yet
Release notes are ready and available for all components	:green_circle:
Roadmap is up-to-date (information is available to create release highlights)	:green_circle:
Release ticket is cut, and there's a forum post announcing the start of the window	:green_circle:
Any necessary security reviews are complete	:green_circle:

OpenSearch 2.13.0 exit criteria status:

Criteria	Status	Description	Comments
Performance tests are run, results are posted to the release ticket and there no unexpected regressions	:green_circle:		https://github.com/opensearch-project/opensearch-build/issues/4433#issuecomment-2024074140
No unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days	:green_circle:		We do have one medium and high CVE but waiting fix from upstream and yet to reach 60days mark.
Documentation has been fully reviewed and signed off by the documentation community.	:green_circle:
All integration tests are passing	:green_circle:
Release blog is ready	:green_circle:

OpenSearch-Dashboards 2.13.0 exit criteria status:

Criteria	Status	Description	Comments
Documentation has been fully reviewed and signed off by the documentation community	:green_circle:
No unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days	:green_circle:
All integration tests are passing	:green_circle:
Release blog is ready	:green_circle:

Preparation

• [x] Release manager assigned.
• [x] Existence of label in each component repo. For more information check the release-label section.
• [x] Increase the build frequency.
• [x] Release Issue.

Campaigns

• [ ] Component Release Issue.
• [ ] Release Campaigns.

Release Branch and Version Increment - 19th March, 2024

• [x] Core Release Branch.
• [x] Core Version Increment.
• [x] Components Release Branch.
• [x] Components Version Increment.

Feature Freeze - 19th March, 2024

• [x] OpenSearch / OpenSearch-Dashboards core and components teams finalize their features.

Code Complete - March 19th, 2024

• [x] Mark this as done once the Code Complete is reviewed.
• [x] Create/Verify pull requests to add each component to relase input manifests/2.13.0/opensearch-2.13.0.yml and manifests/2.13.0/opensearch-dashboards-2.13.0.yml.

Release Candidate Creation and Testing - March 27th, 2024

• [x] Generate Release Candidate.
• [x] Integ Test TAR.
• [x] Integ Test RPM.
• [x] Docker Build and Scan.
• [ ] Backwards Compatibility Tests.
• [x] Windows Integration Test.
• [x] Broadcast and Communication.
• [x] Release Candidate Lock.

Performance testing validation - March 27th, 2024

• [x] Post the benchmark-tests
• [ ] Longevity tests do not show any issues.

Pre Release - April 1st, 2024

• [ ] Release Labeled Issues.
• [x] Go or No-Go.
• [x] Promote Repos.
• [x] Promote artifacts.
• [x] Release Notes.

Release - April 2nd, 2024

• [x] Maven Promotion.
• [x] Docker Promotion.
• [x] Release Validation.
• [x] Collaboration with the Project Management Team.

Release Checklist.

Release Checklist

### Pre-Release activities - [ ] Promote Repos. - - [ ] OS - - [ ] OSD - [ ] Promote Artifacts. - - [ ] Windows - - [ ] Linux Debian - - [ ] Linux RPM - - [ ] Linux TAR - [ ] Consolidated Release Notes. ### Release activities - [ ] Docker Promotion. - [ ] Release Validation part 1. - - [ ] OpenSearch and OpenSearch Dashboard Validation. - - [ ] Validate the native plugin installation. - [ ] Merge consolidated release notes PR. - [ ] Website and Documentation Changes. - - [ ] Merge staging website PR. - - [ ] Promote the website changes to prod. - - [ ] Add website alert. - [ ] Release Validation part 2. - - [ ] Validate the artifact download URL's and signatures. - [ ] Release Validation part 3. - - [ ] Trigger the validation build (Search for `Completed validation for <>` in the logs). - [ ] Maven Promotion. - [ ] Publish blog posts. - [ ] Advertise on Social Media. - [ ] Post on public slack and Github Release issue. ### Post-Release activities - [ ] Release Tags. - [ ] Input Manifest Update. - [ ] Decrease the Build Frequency. - [ ] OpenSearch Build Release notes. - [ ] Retrospective Issue. - [ ] Helm and Ansible Playbook release. - [ ] Upcoming Release Preparation.

Post Release

• [x] Release Tags.
• [x] Input Manifest Update.
• [x] OpenSearch Build Release notes.
• [x] Decrease the Build Frequency.
• [x] Retrospective Issue.
• [x] Helm and Ansible Playbook release.
• [x] Upcoming Release Preparation.

Components

Replace with links to all component tracking issues.

OpenSearch

Component	Issues tagged with 2.13.0
https://github.com/opensearch-project/OpenSearch/issues/12264
https://github.com/opensearch-project/common-utils/issues/594
https://github.com/opensearch-project/k-NN/issues/1473
https://github.com/opensearch-project/geospatial/issues/627
https://github.com/opensearch-project/security/issues/4032
https://github.com/opensearch-project/cross-cluster-replication/issues/1326
https://github.com/opensearch-project/ml-commons/issues/2057
https://github.com/opensearch-project/neural-search/issues/599
https://github.com/opensearch-project/notifications/issues/856
https://github.com/opensearch-project/observability/issues/1799
https://github.com/opensearch-project/reporting/issues/964
https://github.com/opensearch-project/sql/issues/2518
https://github.com/opensearch-project/asynchronous-search/issues/535
https://github.com/opensearch-project/anomaly-detection/issues/1160
https://github.com/opensearch-project/alerting/issues/1417
https://github.com/opensearch-project/security-analytics/issues/849
https://github.com/opensearch-project/index-management/issues/1104
https://github.com/opensearch-project/performance-analyzer/issues/625
https://github.com/opensearch-project/flow-framework/issues/507
https://github.com/opensearch-project/skills/issues/218
https://github.com/opensearch-project/job-scheduler/issues/580
https://github.com/opensearch-project/custom-codecs/issues/114

OpenSearch Dashboards

Component	Issues tagged with 2.13.0
https://github.com/opensearch-project/OpenSearch-Dashboards/issues/5853
https://github.com/opensearch-project/opensearch-dashboards-functional-test/issues/1084
https://github.com/opensearch-project/dashboards-observability/issues/1425
https://github.com/opensearch-project/dashboards-reporting/issues/285
https://github.com/opensearch-project/dashboards-visualizations/issues/331
https://github.com/opensearch-project/dashboards-query-workbench/issues/263
https://github.com/opensearch-project/dashboards-maps/issues/583
https://github.com/opensearch-project/anomaly-detection-dashboards-plugin/issues/682
https://github.com/opensearch-project/ml-commons-dashboards/issues/303
https://github.com/opensearch-project/index-management-dashboards-plugin/issues/975
https://github.com/opensearch-project/dashboards-notifications/issues/155
https://github.com/opensearch-project/alerting-dashboards-plugin/issues/875
https://github.com/opensearch-project/security-analytics-dashboards-plugin/issues/876
https://github.com/opensearch-project/security-dashboards-plugin/issues/1774
https://github.com/opensearch-project/dashboards-search-relevance/issues/370
https://github.com/opensearch-project/dashboards-assistant/issues/142

Documentation

Component	Issues tagged with 2.13.0
https://github.com/opensearch-project/documentation-website/

Legend

| Symbol | Meaning | | -------- | ---------- | | :green_circle: | On track with overall release | | :yellow_circle: | Missed last milestone | | :red_circle: | Missed multiple milestones |

[peterzhuamazon]

Related Issues/PRs:

• OSD Single Version: https://github.com/opensearch-project/OpenSearch-Dashboards/pull/5675
  • https://github.com/opensearch-project/opensearch-build/pull/4468 (Might not need)
• k-NN: https://github.com/opensearch-project/k-NN/pull/1451 Mention on releasenotes
  • https://github.com/opensearch-project/k-NN/pull/1451
  • https://github.com/opensearch-project/k-NN/pull/1503
  • https://github.com/opensearch-project/k-NN/pull/1543
  • https://github.com/opensearch-project/documentation-website/pull/6249
• DEB/RPM https://github.com/opensearch-project/opensearch-build/issues/3815 Mention on releasenotes

  • 4043

  • 4534

  • 4536

  • https://github.com/opensearch-project/opensearch-build/pull/4539
  • https://github.com/opensearch-project/opensearch-build/pull/4546
  • https://github.com/opensearch-project/opensearch-build/pull/4548
  • https://github.com/opensearch-project/opensearch-build/pull/4553
  • https://github.com/opensearch-project/opensearch-build/pull/4557
• DEB/RPM https://github.com/opensearch-project/opensearch-build/issues/3891 Mention on releasenotes

  • 4530 (community contribution)

  • https://github.com/opensearch-project/documentation-website/pull/6720
• https://github.com/opensearch-project/opensearch-build/issues/4528
  • https://github.com/opensearch-project/opensearch-build/pull/4542
• Observability Query Assistant: https://github.com/opensearch-project/dashboards-observability/pull/1639
  • https://github.com/opensearch-project/opensearch-build/pull/4585
• https://github.com/opensearch-project/opensearch-ci/issues/412
  • https://github.com/opensearch-project/opensearch-ci/pull/413

[opensearch-ci-bot]

OpenSearch CommitID(after 2024-02-21) & Release Notes info

Repo	Branch	CommitID	Commit Date	Release Notes Exists
alerting	[2.13]	441f5ae	2024-03-19	True
anomaly-detection	[2.13]	aecf6d7	2024-03-18	True
asynchronous-search	[2.13]	563087a	2024-03-21	True
common-utils	[2.13]	937bc4e	2024-03-21	True
cross-cluster-replication	[2.13]	b64bd49	2024-03-19	True
custom-codecs	[2.13]	5c4e4cb	2024-03-19	True
flow-framework	[2.13]	1af14a0	2024-03-20	True
geospatial	[2.13]	106d1d6	2024-03-19	True
index-management	[2.13]	fa8d1b3	2024-03-20	True
job-scheduler	[2.13]	d2bb218	2024-03-20	True
k-NN	[2.13]	328f501	2024-03-19	True
ml-commons	[2.13]	eeba1c3	2024-03-21	True
neural-search	[2.13]	5279580	2024-03-19	True
notifications	[2.13]	63d6865	2024-03-19	True
opensearch-observability	[2.13]	36e4e52	2024-03-19	True
opensearch-reports	[2.13]	67db59f	2024-03-19	True
performance-analyzer	[2.13]	6863a65	2024-03-21	True
security	[2.13]	c160199	2024-03-20	True
security-analytics	[2.13]	d82094d	2024-03-19	True
skills	[2.13]	a7c8b44	2024-03-21	True
sql	[2.13]	0414b4b	2024-03-20	True

[opensearch-ci-bot]

OpenSearch Dashboards CommitID(after 2024-02-21) & Release Notes info

Repo	Branch	CommitID	Commit Date	Release Notes Exists
alertingDashboards	[2.13]	3a51e59	2024-03-20	True
anomalyDetectionDashboards	[2.13]	aa01139	2024-03-18	True
assistantDashboards	[2.13]	ab55500	2024-03-20	True
customImportMapDashboards	[2.13]	61e26c9	2024-03-18	True
functionalTestDashboards	[2.13]	b5ea5bd	2024-03-20	False
ganttChartDashboards	[2.13]	4f49ec5	2024-03-19	True
indexManagementDashboards	[2.13]	b2d90d9	2024-03-20	True
mlCommonsDashboards	[2.13]	1a5bfda	2024-03-19	True
notificationsDashboards	[2.13]	e7698f5	2024-03-19	True
observabilityDashboards	[2.13]	b17afd3	2024-03-20	True
queryWorkbenchDashboards	[2.13]	7dda568	2024-03-19	True
reportsDashboards	[2.13]	15862cf	2024-03-19	True
searchRelevanceDashboards	[2.13]	f330f4c	2024-03-19	True
securityAnalyticsDashboards	[2.13]	e80a4e8	2024-03-20	True
securityDashboards	[2.13]	9f2c18c	2024-03-20	True

[hdhalter]

Documentation update: RED for entrance criteria. We have 23 OPEN doc issues with 14 PRs. This means we need to have 9 additional PRs created by tomorrow to be green. 2 issues are DONE.

For the documentation status, see https://github.com/opensearch-project/documentation-website/issues?q=is%3Aissue+is%3Aopen+label%3Av2.13.0.

[gaiksaya]

Due to the misses in meeting the entry criteria (release notes, documentation PRs pending) we were not able to generate a viable release candidate even though we have successful builds for both OpenSearch and OpenSearch Dashboards . We have started the testing parallely and the failures should start creating autocut GitHub issues in respective repositories. We will try again tomorrow morning. Please get all the pending release notes and docs PR in by 10AM PST. You can find more details on this wiki for building, testing and release distributions. Thanks!

[gaiksaya]

Hello everyone, Due to the misses in meeting the entry criteria (release notes, documentation PRs pending) we were not able to generate a viable release candidate even today even though we have successful builds for both OpenSearch and OpenSearch Dashboards . Missing release notes components:

• OpenSearch
• ~asynchronous-search~
• common-utils
• performance-analyzer
• ~skills~

Documentation PRs in pending: https://github.com/opensearch-project/documentation-website/pulls?q=is%3Apr+is%3Aopen+label%3Av2.13.0 Also another critical issue: Also, performance-analyzer-rca does not have 2.13 branch as it is not a part of manifest automation. Can the maintainers take a look as performance-analyzer plugin uses this as dependency in their build.gradle and checkouts default branch as 2.x We will try again tomorrow morning. Please get all the pending release notes and docs PR in by 11AM PST. Thanks!

[dblock]

RCA release ticket is https://github.com/opensearch-project/performance-analyzer-rca/issues/537

[gaiksaya]

~## 1st RC OpenSearch 9634 / OpenSearch Dashboards 7537 - 03/21/2024.~ See edits for details

2nd RC OpenSearch 9634 / OpenSearch Dashboards 7537 - 03/22/2024.

OpenSearch - Build 9634 OpenSearch Dashboards - Build 7537

• Use the following Docker-Compose to setup a cluster

  docker-compose.yml

  
  version: '3'
  services:
  opensearch-node1:
    image: opensearchstaging/opensearch:2.13.0.9634
    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_JAVA_OPTS=-Xms512m -Xmx512m" # minimum and maximum Java heap size, recommend setting both to 50% of system RAM
    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.13.0.9634
    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_JAVA_OPTS=-Xms512m -Xmx512m"
    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.13.0.7537
    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:
  
  

  • Download the above docker-compose.yml on your machine.
  • Get latest image versions docker-compose pull.
  • Start the cluster docker-compose up.

• OpenSearch docker 2.13.0.9634

  • Start without security
    • Docker command docker pull opensearchstaging/opensearch:2.13.0.9634 && docker run -it -p 9200:9200 -e "discovery.type=single-node" -e "DISABLE_SECURITY_PLUGIN=true" opensearchstaging/opensearch:2.13.0.9634
  • Connect command curl https://localhost:9200/
  • Start with security
  • Docker command docker pull opensearchstaging/opensearch:2.13.0.9634 && docker run -it -p 9200:9200 -e "OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!" -e "discovery.type=single-node" opensearchstaging/opensearch:2.13.0.9634
  • Connect command curl --insecure https://admin:myStrongPassword123!@localhost:9200/

• OpenSearch-Dashboards docker 2.13.0.7537

  • Start without security
  • Docker command docker pull opensearchstaging/opensearch-dashboards:2.13.0.7537 && docker run -it --network="host" -e "DISABLE_SECURITY_DASHBOARDS_PLUGIN=true" opensearchstaging/opensearch-dashboards:2.13.0.7537
  • URL https://localhost:5601/
  • Start with security
  • Docker command docker pull opensearchstaging/opensearch-dashboards:2.13.0.7537 && docker run -it --network="host" opensearchstaging/opensearch-dashboards:2.13.0.7537
  • URL https://localhost:5601/

• Use below artifacts to deploy OpenSearch Manually

  • OpenSearch - Build 9634 (Note: Windows version does not have performance analyzer plugin)

  • arm64 [manifest] [tar] [rpm][deb]

  • x64 [manifest] [tar] [rpm] [deb] [windows]

  • OpenSearch Dashboards - Build 7537

  • arm64 [manifest] [tar][rpm][deb]

  • x64 [manifest] [tar][rpm] [deb] [windows]

Check how to install opensearch and dashboards on different platforms

Play with new features in nightly playground

We have also deployed the first RC on our newly launched nightly playground https://playground.nightly.opensearch.org/

Details

- _Where can I access it_: https://playground.nightly.opensearch.org/app/home - _What commit was used to build this distribution_: Every user has the read-only access to the cluster (this is just the start for now) The entire distribution manifest of the deployed artifact is index in the cluster as a part of the automation. Simply go to the dev-tools and run the below query: ``` GET opensearch/_doc/1 GET opensearch-dashboards/_doc/1 ``` This will give you components present in the deployed cluster along with the commit_id and the artifact location. - _Component missing from the cluster/distribution_: If a component is missing from the distribution, well because it failed to build and hence was not able to make the cut. Please go to the repository and search for build failure issues. Example: https://github.com/opensearch-project/security-analytics/issues/904 - _How to index data_: Since this endpoint is publicly accessible to everyone, we want to be sure any no the data being indexed is reviewed (for sensitive or customer data). Please feel free to raise a pull request with the data you want to index in the below mentioned link and the maintainers of the repo will take care of indexing it - _Codebase link_: https://github.com/opensearch-project/opensearch-devops/tree/main/nightly-playground

[gaiksaya]

Looks like most plugins are failing the integration tests. See run for OpenSearch tarball x64: https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test/detail/integ-test/8053/pipeline Regarding Dashboards looks like Dashboards core and security Analytics are failing: tarball x64: https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test-opensearch-dashboards/detail/integ-test-opensearch-dashboards/5716/pipeline

Please remember there are more distributions and architectures where failures happened. Please go through the issues created in the respective repos for details and logs and fix the code for the same. The GH issue contains the test-report.yml which has details to your plugin exclusive yml that contains links to all logs. Testing wiki.

We will generate the new RC at 4PM PST today again.

Since we locked the commits in our manifest files, we need to manually update them. Please ping in this thread informing us to update the commit for your repo. Thanks!

[bbarani]

@gaiksaya Looks like most of the tests are failing with below error message?

        Caused by:

        javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

OR.

{"error":{"root_cause":[{"type":"alerting_exception","reason":"Filter by user backend roles is enabled with security disabled."}],"type":"alerting_exception","reason":"Filter by user backend roles is enabled with security disabled.","caused_by":{"type":"exception","reason":"org.opensearch.OpenSearchStatusException: Filter by user backend roles is enabled with security disabled."}},"status":403

CC: @peternied @peterzhuamazon

[peternied]

It looks like many plugins are using certificates [1] that have expired leading to this error message. Recommendation is to have plugins upgrade their certificate configurations [2].

• [1] Slack thread https://opensearch.slack.com/archives/C0561HRK961/p1711394001609129
• [2] https://github.com/opensearch-project/anomaly-detection/pull/1163

[gaiksaya]

3rd RC OpenSearch 9647 / OpenSearch Dashboards 7541 - 03/25/2024.

OpenSearch - Build 9647 OpenSearch Dashboards - Build 7541

• Use the following Docker-Compose to setup a cluster

  docker-compose.yml

  
  version: '3'
  services:
  opensearch-node1:
    image: opensearchstaging/opensearch:2.13.0.9647
    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_JAVA_OPTS=-Xms512m -Xmx512m" # minimum and maximum Java heap size, recommend setting both to 50% of system RAM
    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.13.0.9647
    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_JAVA_OPTS=-Xms512m -Xmx512m"
    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.13.0.7541
    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:
  
  

  • Download the above docker-compose.yml on your machine.
  • Get latest image versions docker-compose pull.
  • Start the cluster docker-compose up.

• OpenSearch docker 2.13.0.9647

  • Start without security
    • Docker command docker pull opensearchstaging/opensearch:2.13.0.9647 && docker run -it -p 9200:9200 -e "discovery.type=single-node" -e "DISABLE_SECURITY_PLUGIN=true" opensearchstaging/opensearch:2.13.0.9647
  • Connect command curl https://localhost:9200/
  • Start with security
  • Docker command docker pull opensearchstaging/opensearch:2.13.0.9647 && docker run -it -p 9200:9200 -e "OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!" -e "discovery.type=single-node" opensearchstaging/opensearch:2.13.0.9647
  • Connect command curl --insecure https://admin:myStrongPassword123!@localhost:9200/

• OpenSearch-Dashboards docker 2.13.0.7541

  • Start without security
  • Docker command docker pull opensearchstaging/opensearch-dashboards:2.13.0.7541 && docker run -it --network="host" -e "DISABLE_SECURITY_DASHBOARDS_PLUGIN=true" opensearchstaging/opensearch-dashboards:2.13.0.7541
  • URL https://localhost:5601/
  • Start with security
  • Docker command docker pull opensearchstaging/opensearch-dashboards:2.13.0.7541 && docker run -it --network="host" opensearchstaging/opensearch-dashboards:2.13.0.7541
  • URL https://localhost:5601/

• Use below artifacts to deploy OpenSearch Manually

  • OpenSearch - Build 9647 (Note: Windows version does not have performance analyzer plugin)

  • arm64 [manifest] [tar] [rpm][deb]

  • x64 [manifest] [tar] [rpm] [deb] [windows]

  • OpenSearch Dashboards - Build 7541

  • arm64 [manifest] [tar][rpm][deb]

  • x64 [manifest] [tar][rpm] [deb] [windows]

Check how to install opensearch and dashboards on different platforms

Play with new features in nightly playground

We have also deployed the first RC on our newly launched nightly playground https://playground.nightly.opensearch.org/

Details

- _Where can I access it_: https://playground.nightly.opensearch.org/app/home - _What commit was used to build this distribution_: Every user has the read-only access to the cluster (this is just the start for now) The entire distribution manifest of the deployed artifact is index in the cluster as a part of the automation. Simply go to the dev-tools and run the below query: ``` GET opensearch/_doc/1 GET opensearch-dashboards/_doc/1 ``` This will give you components present in the deployed cluster along with the commit_id and the artifact location. - _Component missing from the cluster/distribution_: If a component is missing from the distribution, well because it failed to build and hence was not able to make the cut. Please go to the repository and search for build failure issues. Example: https://github.com/opensearch-project/security-analytics/issues/904 - _How to index data_: Since this endpoint is publicly accessible to everyone, we want to be sure any no the data being indexed is reviewed (for sensitive or customer data). Please feel free to raise a pull request with the data you want to index in the below mentioned link and the maintainers of the repo will take care of indexing it - _Codebase link_: https://github.com/opensearch-project/opensearch-devops/tree/main/nightly-playground

[gaiksaya]

4th RC OpenSearch 9652 / OpenSearch Dashboards 7543 - 03/26/2024.

OpenSearch - Build 9652 OpenSearch Dashboards - Build 7543

• Use the following Docker-Compose to setup a cluster

  docker-compose.yml

  
  version: '3'
  services:
  opensearch-node1:
    image: opensearchstaging/opensearch:2.13.0.9652
    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_JAVA_OPTS=-Xms512m -Xmx512m" # minimum and maximum Java heap size, recommend setting both to 50% of system RAM
    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.13.0.9652
    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_JAVA_OPTS=-Xms512m -Xmx512m"
    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.13.0.7543
    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:
  
  

  • Download the above docker-compose.yml on your machine.
  • Get latest image versions docker-compose pull.
  • Start the cluster docker-compose up.

• OpenSearch docker 2.13.0.9652

  • Start without security
    • Docker command docker pull opensearchstaging/opensearch:2.13.0.9652 && docker run -it -p 9200:9200 -e "discovery.type=single-node" -e "DISABLE_SECURITY_PLUGIN=true" opensearchstaging/opensearch:2.13.0.9652
  • Connect command curl https://localhost:9200/
  • Start with security
  • Docker command docker pull opensearchstaging/opensearch:2.13.0.9652 && docker run -it -p 9200:9200 -e "OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!" -e "discovery.type=single-node" opensearchstaging/opensearch:2.13.0.9652
  • Connect command curl --insecure https://admin:myStrongPassword123!@localhost:9200/

• OpenSearch-Dashboards docker 2.13.0.7543

  • Start without security
  • Docker command docker pull opensearchstaging/opensearch-dashboards:2.13.0.7543 && docker run -it --network="host" -e "DISABLE_SECURITY_DASHBOARDS_PLUGIN=true" opensearchstaging/opensearch-dashboards:2.13.0.7543
  • URL https://localhost:5601/
  • Start with security
  • Docker command docker pull opensearchstaging/opensearch-dashboards:2.13.0.7543 && docker run -it --network="host" opensearchstaging/opensearch-dashboards:2.13.0.7543
  • URL https://localhost:5601/

• Use below artifacts to deploy OpenSearch Manually

  • OpenSearch - Build 9652 (Note: Windows version does not have performance analyzer plugin)

  • arm64 [manifest] [tar] [rpm][deb]

  • x64 [manifest] [tar] [rpm] [deb] [windows]

  • OpenSearch Dashboards - Build 7543

  • arm64 [manifest] [tar][rpm][deb]

  • x64 [manifest] [tar][rpm] [deb] [windows]

Check how to install opensearch and dashboards on different platforms

Play with new features in nightly playground

We have also deployed the first RC on our newly launched nightly playground https://playground.nightly.opensearch.org/

Details

- _Where can I access it_: https://playground.nightly.opensearch.org/app/home - _What commit was used to build this distribution_: Every user has the read-only access to the cluster (this is just the start for now) The entire distribution manifest of the deployed artifact is index in the cluster as a part of the automation. Simply go to the dev-tools and run the below query: ``` GET opensearch/_doc/1 GET opensearch-dashboards/_doc/1 ``` This will give you components present in the deployed cluster along with the commit_id and the artifact location. - _Component missing from the cluster/distribution_: If a component is missing from the distribution, well because it failed to build and hence was not able to make the cut. Please go to the repository and search for build failure issues. Example: https://github.com/opensearch-project/security-analytics/issues/904 - _How to index data_: Since this endpoint is publicly accessible to everyone, we want to be sure any no the data being indexed is reviewed (for sensitive or customer data). Please feel free to raise a pull request with the data you want to index in the below mentioned link and the maintainers of the repo will take care of indexing it - _Codebase link_: https://github.com/opensearch-project/opensearch-devops/tree/main/nightly-playground

Docker scan for 2.13.0 4th RC:

OpenSearch: https://build.ci.opensearch.org/job/docker-scan/3130/artifact/scan_docker_image.txt/*view/ Dashboards: https://build.ci.opensearch.org/job/docker-scan/3129/artifact/scan_docker_image.txt/view*/

[gaiksaya]

RC4 integration test results

OpenSearch components integration test

Component Name	Debian X64	Debian ARM64	RPM X64	RPM ARM64	Tarball ARM64	Tarball X64	Windows x64
	URL	URL	URL	URL	URL	URL	URL
Alerting	Failed	Failed	Failed	Failed	Failed	Failed	Failed
Anomaly detection	Passed	Passed	Passed	Passed	Passed	Passed	Passed
Asynchronous Search	Passed	Passed	Passed	Passed	Passed	Passed	Passed
Cross Cluster Replication	Failed	Failed	Failed	Failed	Passed	Passed	Failed
Custom codecs	Passed	Passed	Passed	Passed	Passed	Passed	Passed
Flow framework	Passed	Passed	Passed	Passed	Passed	Passed	Passed
Geospatial	Passed	Passed	Passed	Passed	Passed	Passed	Passed
Index Management	Failed	Failed	Failed	Failed	Failed	Failed	Failed
k-NN	Passed	Passed	Passed	Passed	Passed	Passed	Passed
Ml-commons	Passed	Passed	Passed	Passed	Failed	Passed	Failed
Neural Search	Failed	Failed	Failed	Failed	Failed	Failed	Failed
Notifications	Failed	Failed	Failed	Failed	Failed	Failed	Failed
Observability	Passed	Passed	Passed	Passed	Passed	Passed	Passed
Reports	Passed	Passed	Passed	Passed	Passed	Failed	Passed
Security	Passed	Passed	Passed	Passed	Passed	Passed	Passed
Security-Analytics	Failed	Failed	Failed	Failed	Failed	Failed	Failed
Skills	Failed	Failed	Failed	Failed	Failed	Passed	Passed
SQL	Passed	Passed	Passed	Passed	Passed	Passed	Passed

OpenSearch Dashboards components integration test

Component Name	Debian X64	Debian ARM64	RPM X64	RPM ARM64	Tarball ARM64	Tarball X64	Windows x64
	URL	URL	URL	URL	URL	URL	URL
OpenSearch Dashboards	Failed	Failed	Failed	Failed	Failed	Failed	Passed
alertingDashboards	Failed	Failed	Failed	Failed	Passed	Passed	Passed
anomalyDetectionDashboards	Passed	Passed	Passed	Passed	Passed	Passed	Passed
assistantDashboards	Passed	Passed	Failed	Passed	Passed	Passed	Passed
customImportMapsDashboards	Passed	Passed	Passed	Passed	Passed	Passed	Passed
ganttChartDashboards	Passed	Passed	Failed	Passed	Passed	Failed	Failed
IndexManagmentDashboards	Passed	Failed	Passed	Passed	Passed	Passed	Failed
mlCommonsDashboards	Passed	Passed	Passed	Passed	Passed	Passed	Passed
notificationsDashboards	Passed	Passed	Passed	Passed	Passed	Passed	Passed
observabilityDashboards	Failed	Passed	Passed	Failed	Passed	Passed	Passed
queryWorkBench	Passed	Passed	Passed	Passed	Passed	Passed	Passed
reportsDashboards	Passed	Passed	Passed	Passed	Passed	Passed	Passed
searchRelevanceDashboards	Passed	Passed	Passed	Passed	Passed	Passed	Passed
securityAnalyticsDashboards	Passed	Passed	Passed	Passed	Passed	Passed	Passed
securityDashboards	Passed	Passed	Passed	Passed	Passed	Passed	Passed

[vibrantvarun]

As discussed offline, we are doing manual sign off for neural search plugin due to issue 596.

cc: @prudhvigodithi cc: @gaiksaya

[rishabh6788]

2.13.0 Performance comparison with 2.12.0

http_logs is seeing no significant improvement or regression in Indexing throughput or overall search latency compared to 2.120.

nyx_taxis is seeing no change in the indexing throughput but showing improvements in autohisto_agg (upto 35%) and date_histogram_agg (upto 40%) query latencies compared to 2.12.0

[manasvinibs]

For Dashboards core,

1. The shared link tests are failing which are expecting to fail ((with the security plugin changing the URL and we are comparing the urls. Everything is the same besides the security tenant). We have plans to fix this tests asap so it doesn’t depend on the URL comparison. These tests have a cascading effect on the errors.spec.js. Since those tests fail it doesn’t cause the eventual error we are expecting. We know there shouldn’t be a cascading failure but that means once we fix the shared link tests then the errors test should pass.

@kavilla @AMoo-Miki @ashwin-pc Are we good to give manual sign off on shared link tests?

2. For the visbuilder tests, I see those test passing in local and we still utilize the private tenant. However, from the previous release we added switching the tenant to the global tenant for the data explorer tests. So since the data explorer tests get executed before the vis builder and the tenancy is switching causing unexpected delays, the tests are failing when ran sequentially. However, running the vis builder tests by themselves all pass. We plan to manually sign off on this and then add the usage of the global tenant to the vis builder. @kavilla

Local testing Visbuilder

[gaiksaya]

5th RC OpenSearch 9659 / OpenSearch Dashboards 7548 - 03/27/2024.

OpenSearch - Build 9659 OpenSearch Dashboards - Build 7548

• Use the following Docker-Compose to setup a cluster

  docker-compose.yml

  
  version: '3'
  services:
  opensearch-node1:
    image: opensearchstaging/opensearch:2.13.0.9659
    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_JAVA_OPTS=-Xms512m -Xmx512m" # minimum and maximum Java heap size, recommend setting both to 50% of system RAM
    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.13.0.9659
    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_JAVA_OPTS=-Xms512m -Xmx512m"
    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.13.0.7548
    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:
  
  

  • Download the above docker-compose.yml on your machine.
  • Get latest image versions docker-compose pull.
  • Start the cluster docker-compose up.

• OpenSearch docker 2.13.0.9659

  • Start without security
    • Docker command docker pull opensearchstaging/opensearch:2.13.0.9659 && docker run -it -p 9200:9200 -e "discovery.type=single-node" -e "DISABLE_SECURITY_PLUGIN=true" opensearchstaging/opensearch:2.13.0.9659
  • Connect command curl https://localhost:9200/
  • Start with security
  • Docker command docker pull opensearchstaging/opensearch:2.13.0.9659 && docker run -it -p 9200:9200 -e "OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!" -e "discovery.type=single-node" opensearchstaging/opensearch:2.13.0.9659
  • Connect command curl --insecure https://admin:myStrongPassword123!@localhost:9200/

• OpenSearch-Dashboards docker 2.13.0.7548

  • Start without security
  • Docker command docker pull opensearchstaging/opensearch-dashboards:2.13.0.7548 && docker run -it --network="host" -e "DISABLE_SECURITY_DASHBOARDS_PLUGIN=true" opensearchstaging/opensearch-dashboards:2.13.0.7548
  • URL https://localhost:5601/
  • Start with security
  • Docker command docker pull opensearchstaging/opensearch-dashboards:2.13.0.7548 && docker run -it --network="host" opensearchstaging/opensearch-dashboards:2.13.0.7548
  • URL https://localhost:5601/

• Use below artifacts to deploy OpenSearch Manually

  • OpenSearch - Build 9659 (Note: Windows version does not have performance analyzer plugin)

  • arm64 [manifest] [tar] [rpm][deb]

  • x64 [manifest] [tar] [rpm] [deb] [windows]

  • OpenSearch Dashboards - Build 7548

  • arm64 [manifest] [tar][rpm][deb]

  • x64 [manifest] [tar][rpm] [deb] [windows]

Check how to install opensearch and dashboards on different platforms

Play with new features in nightly playground

We have also deployed the first RC on our newly launched nightly playground https://playground.nightly.opensearch.org/

Details

- _Where can I access it_: https://playground.nightly.opensearch.org/app/home - _What commit was used to build this distribution_: Every user has the read-only access to the cluster (this is just the start for now) The entire distribution manifest of the deployed artifact is index in the cluster as a part of the automation. Simply go to the dev-tools and run the below query: ``` GET opensearch/_doc/1 GET opensearch-dashboards/_doc/1 ``` This will give you components present in the deployed cluster along with the commit_id and the artifact location. - _Component missing from the cluster/distribution_: If a component is missing from the distribution, well because it failed to build and hence was not able to make the cut. Please go to the repository and search for build failure issues. Example: https://github.com/opensearch-project/security-analytics/issues/904 - _How to index data_: Since this endpoint is publicly accessible to everyone, we want to be sure any no the data being indexed is reviewed (for sensitive or customer data). Please feel free to raise a pull request with the data you want to index in the below mentioned link and the maintainers of the repo will take care of indexing it - _Codebase link_: https://github.com/opensearch-project/opensearch-devops/tree/main/nightly-playground

[CaptainDredge]

Giving manual signoff for index-management dashboard, we've had one test failure for which we've merged the fix today to decrease the probability of failure. The test failure can still occur intermittently but the functionality works fine and is manually tested. https://github.com/opensearch-project/index-management-dashboards-plugin/issues/1011#issuecomment-2024848863

[nisgoel-amazon]

Giving manual signoff for Cross Cluster Replication(CCR) plugin, There are failures in multiple distribution due to issue in creating remote clusters which we have recently introduced. Tracking the issue here. We have manually verified the test run by running them on debian distribution by creating domains via docker image, which is mentioned over here.

[VijayanB]

Giving manual signoff for geospatial . The test failure was due to random input to one of integration test. We raised PR today which will address that issue.

[Swiddis]

Signing off for observability dashboards on or after commit 06c7be88 which has an important bugfix.

Update: There's one more PR coming in, this is an important security fix https://github.com/opensearch-project/dashboards-observability/pull/1650. Getting review from security team at 1:30 before merging.

Failing test in FTR was flaky and we have a PR to fix it, functionality works manually. Not aware of any other blocking issues from the team. Tried checking the test manifest one more time to be sure that it's the same test failing, but it's saying "Status unavailable" for the observability tests -- Not sure what's up with that.

[vibrantvarun]

Adding to @VijayanB this is the PR https://github.com/opensearch-project/geospatial/commit/ab578ae4e49505fc31f5f445041c28d0e1b3a7b3 which got merged and backported to 2.x and 2.13

cc: @gaiksaya

[amitgalitz]

Adding new commit with a fix needed for consistent use case name in new feature: https://github.com/opensearch-project/flow-framework/commit/478bb7eae139064b41f5af15712022a2f5415dc7

[gaiksaya]

6th RC OpenSearch 9662 / OpenSearch Dashboards 7550 - 03/28/2024.

OpenSearch - Build 9662 OpenSearch Dashboards - Build 7550

• Use the following Docker-Compose to setup a cluster

  docker-compose.yml

  
  version: '3'
  services:
  opensearch-node1:
    image: opensearchstaging/opensearch:2.13.0.9662
    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_JAVA_OPTS=-Xms512m -Xmx512m" # minimum and maximum Java heap size, recommend setting both to 50% of system RAM
    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.13.0.9662
    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_JAVA_OPTS=-Xms512m -Xmx512m"
    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.13.0.7550
    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:
  
  

  • Download the above docker-compose.yml on your machine.
  • Get latest image versions docker-compose pull.
  • Start the cluster docker-compose up.

• OpenSearch docker 2.13.0.9662

  • Start without security
    • Docker command docker pull opensearchstaging/opensearch:2.13.0.9662 && docker run -it -p 9200:9200 -e "discovery.type=single-node" -e "DISABLE_SECURITY_PLUGIN=true" opensearchstaging/opensearch:2.13.0.9662
  • Connect command curl https://localhost:9200/
  • Start with security
  • Docker command docker pull opensearchstaging/opensearch:2.13.0.9662 && docker run -it -p 9200:9200 -e "OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!" -e "discovery.type=single-node" opensearchstaging/opensearch:2.13.0.9662
  • Connect command curl --insecure https://admin:myStrongPassword123!@localhost:9200/

• OpenSearch-Dashboards docker 2.13.0.7550

  • Start without security
  • Docker command docker pull opensearchstaging/opensearch-dashboards:2.13.0.7550 && docker run -it --network="host" -e "DISABLE_SECURITY_DASHBOARDS_PLUGIN=true" opensearchstaging/opensearch-dashboards:2.13.0.7550
  • URL https://localhost:5601/
  • Start with security
  • Docker command docker pull opensearchstaging/opensearch-dashboards:2.13.0.7550 && docker run -it --network="host" opensearchstaging/opensearch-dashboards:2.13.0.7550
  • URL https://localhost:5601/

• Use below artifacts to deploy OpenSearch Manually

  • OpenSearch - Build 9662 (Note: Windows version does not have performance analyzer plugin)

  • arm64 [manifest] [tar] [rpm][deb]

  • x64 [manifest] [tar] [rpm] [deb] [windows]

  • OpenSearch Dashboards - Build 7550

  • arm64 [manifest] [tar][rpm][deb]

  • x64 [manifest] [tar][rpm] [deb] [windows]

Check how to install opensearch and dashboards on different platforms

Play with new features in nightly playground

We have also deployed the first RC on our newly launched nightly playground https://playground.nightly.opensearch.org/

Details

- _Where can I access it_: https://playground.nightly.opensearch.org/app/home - _What commit was used to build this distribution_: Every user has the read-only access to the cluster (this is just the start for now) The entire distribution manifest of the deployed artifact is index in the cluster as a part of the automation. Simply go to the dev-tools and run the below query: ``` GET opensearch/_doc/1 GET opensearch-dashboards/_doc/1 ``` This will give you components present in the deployed cluster along with the commit_id and the artifact location. - _Component missing from the cluster/distribution_: If a component is missing from the distribution, well because it failed to build and hence was not able to make the cut. Please go to the repository and search for build failure issues. Example: https://github.com/opensearch-project/security-analytics/issues/904 - _How to index data_: Since this endpoint is publicly accessible to everyone, we want to be sure any no the data being indexed is reviewed (for sensitive or customer data). Please feel free to raise a pull request with the data you want to index in the below mentioned link and the maintainers of the repo will take care of indexing it - _Codebase link_: https://github.com/opensearch-project/opensearch-devops/tree/main/nightly-playground

[gaiksaya]

OpenSearch Integ-test results for 6th RC

Component Name	Comments	Debian X64	Debian ARM64	RPM X64	RPM ARM64	Tarball ARM64	Tarball X64	Windows x64
		URL	URL	URL	URL	URL	URL	URL
Alerting	Manually signed off by @praveensameneni	Failed	Failed	Failed	Failed	Failed	Failed	Failed
Anomaly detection		Passed	Passed	Passed	Passed	Passed	Passed	Passed
Asynchronous Search		Passed	Passed	Passed	Passed	Passed	Passed	Passed
Cross Cluster Replication	Manually signed off https://github.com/opensearch-project/opensearch-build/issues/4433#issuecomment-2025285794	Failed	Failed	Failed	Failed	Passed	Passed	Failed
Custom codecs		Passed	Passed	Passed	Passed	Passed	Passed	Passed
Flow framework		Passed	Passed	Passed	Passed	Passed	Passed	Passed
Geospatial		Passed	Passed	Passed	Passed	Passed	Passed	Passed
Index Management	Manually Signed off by @vikasvb90 @khushbr	Failed	Failed	Failed	Failed	Failed	Failed	Failed
k-NN		Passed	Passed	Passed	Passed	Passed	Passed	Passed
Ml-commons		Passed	Passed	Passed	Passed	Failed	Passed
Neural Search	Manually signed off https://github.com/opensearch-project/opensearch-build/issues/4433#issuecomment-2024020461	Failed	Failed	Failed	Failed	Failed	Failed	Failed
Notifications	Manually signed off by @praveensameneni	Failed	Failed	Failed	Failed	Failed	Failed	Failed
Observability		Passed	Passed	Passed	Passed	Passed	Passed	Passed
Reports		Passed	Passed	Passed	Passed	Passed	Passed	Passed
Security		Passed	Passed	Passed	Passed	Passed	Passed	Passed
Security-Analytics	Manually signed off by @praveensameneni	Failed	Failed	Failed	Failed	Failed	Failed	Failed
Skills		Failed	Failed	Failed	Failed	Failed	Passed	Passed
SQL		Passed	Passed	Passed	Passed	Passed	Passed	Passed

[gaiksaya]

OpenSearch Dashboards Integ-test results

Component Name	Comments	Debian X64	Debian ARM64	RPM X64	RPM ARM64	Tarball ARM64	Tarball X64	Windows x64
		URL	URL	URL	URL	URL	URL	URL
OpenSearch Dashboards	Manually signed off https://github.com/opensearch-project/opensearch-build/issues/4433#issuecomment-2024170687	Failed	Failed	Failed	Failed	Failed	Failed	Passed
alertingDashboards	Manually signed-off as per this comment	Passed	Passed	Failed	Passed	Passed	Passed	Passed
anomalyDetectionDashboards		Passed	Passed	Passed	Passed	Passed	Passed	Passed
assistantDashboards		Passed	Passed	Passed	Passed	Passed	Passed	Passed
customImportMapsDashboards		Passed	Passed	Passed	Passed	Passed	Passed	Passed
ganttChartDashboards	Manually signed-off as per this comment	Passed	Failed	Failed	Failed	Failed	Passed	Failed
IndexManagmentDashboards	Manually signed off https://github.com/opensearch-project/opensearch-build/issues/4433#issuecomment-2024853027	Passed	Passed	Passed	Passed	Failed	Failed	Failed
mlCommonsDashboards		Passed	Passed	Passed	Passed	Passed	Passed	Passed
notificationsDashboards		Passed	Passed	Passed	Passed	Passed	Passed	Passed
observabilityDashboards	Manually signed-off as per this comment	Passed	Passed	Failed	Passed	Passed	Passed	Passed
queryWorkBench		Passed	Passed	Passed	Passed	Passed	Passed	Passed
reportsDashboards	Manually signed-off as per this comment	Passed	Passed	Passed	Passed	Failed	Failed	Passed
searchRelevanceDashboards		Passed	Passed	Passed	Passed	Passed	Passed	Passed
securityAnalyticsDashboards		Passed	Passed	Passed	Passed	Passed	Passed	Passed
securityDashboards		Passed	Passed	Passed	Passed	Passed	Passed	Passed

[amsiglan]

Looking at the alertingDashboard test failure video for RPM X64 it looks like the monitor did not finish executing and all alerts couldn't be fetched before we checked for alerts from all monitors. I'm okay with manually signing-off for this test since we have seen it pass reliably in our repo CIs and also on the other platforms it works fine. Will look into making the test more robust

[ps48]

Giving Manual Sign-off for ganttCharts, observabilityDashboards and reportsDashboards.

For ganttCharts, I see that major failures are with-security We have a PR to make the tenant selection using URL: https://github.com/opensearch-project/opensearch-dashboards-functional-test/pull/1197. For observabilityDashboards and reportsDashboards I see the failures are coming from flaky tests on a couple of distributions.

[hdhalter]

Documentation is GREEN for the exit criteria. All 38 PRs for 2.13 are merged.

[gaiksaya]

RC6 has been finalized as the final RC for 2.13.0 release in today's Go/No-Go call. We will releasing in on 2nd April, 2024.

[gaiksaya]

Centralize release workflow run: https://build.ci.opensearch.org/blue/organizations/jenkins/central-release-promotion/detail/central-release-promotion/4/pipeline/714

Validation: https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-validation/detail/distribution-validation/304/pipeline/48/

[gaiksaya]

2.13.0 is released to the community now. 🎉 Please use https://github.com/opensearch-project/opensearch-build/issues/4602 for feedback/retrospective.

Thank you!