[RELEASE] Release version 1.3.8

[github-actions]

Release OpenSearch and OpenSearch Dashboards 1.3.8

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

• Assign this issue to a release owner.
• Declare a pencils down date for new features to be merged.
• Jan 26th is pencils down date for feature freeze.
• Update the Campaigns section to include monitoring campaigns during this release.
• Update this issue so all __REPLACE_RELEASE-__ placeholders have actual dates.
• Document any new quality requirements or changes.
• Finalize scope and feature set and update the Public Roadmap.
• Create a release issue in every component repo that links back to this issue, update Components section with these links.
• Ensure the label is created in each component repo for this new version, and the next minor release. Create a version label
• Ensure that all release issues created above are assigned to an owner in the component team.
• Increase the build frequency for the this release from once a day (H 1 * * *) to once every hour (H/60 * * * *) in jenkinsFile.

Campaigns

REPLACE with OpenSearch wide initiatives to improve quality and consistency.

Release Branch - 01/26/2023

• Component versions are auto-incremented to 1.3.8 version.
• Plugins team to ensure working CI in component repositories and merge the version increment PRs.
• OpenSearch / OpenSearch-Dashboards core cut branch <MajorVersion>.<MinorVersion> early.
• All component repos create <MajorVersion>.<MinorVersion> branch for the release.

Feature Freeze - 01/26/2023

• OpenSearch / OpenSearch-Dashboards core and components teams finalize their features.
• Create Jenkins workflows that run daily snapshot builds for OpenSearch and OpenSearch Dashboards.
• Make pull requests to add each component to manifests/1.3.8/opensearch-1.3.8.yml and manifests/1.3.8/opensearch-dashboards-1.3.8.yml with the corresponding checks.

Code Complete - 01/26/2023 - 01/27/2023

• Code Complete: Make sure that the code for this specific version of the release is ready and the branch corresponding to this release has been added to this release version manifest.
• Verify pull requests to add each component to manifests/1.3.8/opensearch-1.3.8.yml and manifests/1.3.8/opensearch-dashboards-1.3.8.yml have been merged.
• Gather, review and combine the release notes from components repositories.

Release testing - 01/27/2023 - 01/30/2023

• Declare a release candidate build, and provide the instructions with the release candidates for teams on testing (REPLACE_RELEASE-minus-8-days).
• Stop builds for this version of OpenSearch and/or OpenSearch Dashboards in order to avoid accidental commits going in unknowingly. Restart only if necessary else manually run the build workflow and declare new release candidate.
• After generate the release candidates, raise PR to lock input manifest refs of both OS and OSD builds with the commit ids from distribution manifest of the release candidates.
• Sanity Testing (REPLACE_RELEASE-minus-8-days - REPLACE_RELEASE-minus-6-days): Sanity testing and fixing of critical issues found by teams. Teams test their components within the distribution, ensuring integration, backwards compatibility, and perf tests pass.
• Publish all test results in the comments of this issue.

### Performance testing validation - Ends REPLACE_RELEASE-minus-6-days

- [ ] Performance tests do not show a regression.
- [ ] Longevity tests do not show any issues.

Release - 02/01/2023 - 02/02/2023

• Verify all issues labeled v1.3.8 in all projects have been resolved.
• Complete documentation for this release.
• Author blog post for this release.
• __REPLACE_RELEASE-minus-1-day - Publish this release on opensearch.org.
• __REPLACE_RELEASE-day - Publish a blog post - release is launched!

Post Release

• Create release tags for each component (Jenkins job name: release-tag-creation).
• Replace refs in manifests/1.3.8 with tags and remove checks.
• If this is a major or minor version release, stop building previous patch version.
• Generate distribution release notes reviewed by PM team for opensearch-build repository.
• Increment version for Helm Charts (sample PR) for the 1.3.8 release.
• Increment version for Ansible Charts (sample PR) for the 1.3.8 release.
• Prepare for next patch release by incrementing patch versions for each component.
• Update this template with any new or missed steps.
• Create an issue for a retrospective, solicit feedback, and publish a summary.

Components

Replace with links to all component tracking issues.

Component	On track	Release Notes
{COMPONENT_ISSUE_LINK}	{INDICATOR}}	{STATUS}

Legend

Symbol	Meaning
🟢	On track with overall release
🟡	Missed last milestone
🔴	Missed multiple milestones

[peterzhuamazon]

Adding DISTRIBUTION selector:

• Add distribution selector for distribution builds on Jenkins #3149

• Add distribution selector to promotion workflows artifacts #3175

• Add dist selection on the promotion workflow opensearch-build-libraries#122

• Add a comma to the workflow for artifacts uploads #3176

[Divyaasm]

Release testing

We have release candidates built and ready for testing.

---

OpenSearch Docker

Start without security
Docker command docker pull docker pull opensearchstaging/opensearch:1.3.8.7019 && docker run -it -d -p 9200:9200 -e "discovery.type=single-node" -e "DISABLE_SECURITY_PLUGIN=true" opensearchstaging/opensearch:1.3.8.7019
Connect command curl http://localhost:9200

Start with security
Docker command docker pull opensearchstaging/opensearch:1.3.8.7019 && docker run -it -d -p 9200:9200 -e "discovery.type=single-node" opensearchstaging/opensearch:1.3.8.7019
Connect command curl --insecure https://admin:admin@localhost:9200

OpenSearch Dashboards Docker

Start without security
Docker command docker pull opensearchstaging/opensearch-dashboards:1.3.8.5411 && docker run -it -d --network="host" -e "DISABLE_SECURITY_DASHBOARDS_PLUGIN=true" opensearchstaging/opensearch-dashboards:1.3.8.5411
URL http://localhost:5601

Start with security
Docker command docker pull opensearchstaging/opensearch-dashboards:1.3.8.5411 && docker run -it -d --network="host" opensearchstaging/opensearch-dashboards:1.3.8.5411
URL http://localhost:5601

Use below artifacts to deploy OpenSearch and OpenSearch Dashboards on different platforms

OpenSearch - Build 7019

• x64 artifacts: [manifest] [tar] [rpm] [yum] [windows]

• arm64 artifacts: [manifest] [tar] [rpm] [yum]

OpenSearch Dashboards - Build 5411

• x64 artifacts: [manifest] [tar] [rpm] [yum] [windows]

• arm64 artifacts: [manifest] [tar] [rpm] [yum]

How to install via yum, tarball, windows etc?

[opensearch-ci-bot]

OpenSearch CommitID(after 2023-01-24) & Release Notes info

Repo	Branch	CommitID	Commit Date	Release Notes
OpenSearch	2ac1c13e3877692bc9cbbab4c796d7244fe8486a	2ac1c13	2023-01-26	False
common-utils	745bf040439394e4896030afda7a5b935944c4a5			False
job-scheduler	32523e02e8b25f5f2f2e0f636ed717173e8a0070			False
alerting	fe3d31153c1334e63103d534bb786a8f4f362357	fe3d311	2023-01-26	False
index-management	81d7b43f8e8bb73d0c73cb2713dd739e9effcd2a	81d7b43	2023-01-26	False
performance-analyzer	160ef9645a12b22d3912dfbde15f9e0a3abc2d30			False
opensearch-observability	cbef85651e23cacc01ae05b8771d0e2415195177	cbef856	2023-01-27	False
ml-commons	bf3df8b6fa21f8db4602341a721cea19dacb964b	bf3df8b	2023-01-26	False
asynchronous-search	d828398c1d40ac0fea67682f2154d109f84c8320	d828398	2023-01-26	False
sql	df51076b25dd8be9e65e38a6d94ee140a6286e1c			False
k-NN	5d5a70c4bbf42de271928ef9a7fc0827cb2677ee			False
cross-cluster-replication	da8da39cd0e84db11fb06a3b8c4171e8f8ece695			False
anomaly-detection	0773edf2d3bba57cc99f914982386e4f20c6e5cc	0773edf	2023-01-26	False
opensearch-reports	ea473423f0906772a39ea73dd3ef18ea5e0d0c73	ea47342	2023-01-26	False
security	7fabf39a82538aebea925f5ab901ffad2d1366a4			False

[opensearch-ci-bot]

OpenSearch Dashboards CommitID(after 2023-01-24) & Release Notes info

Repo	Branch	CommitID	Commit Date	Release Notes
OpenSearch-Dashboards	55783c976d503fc1de2611d1c56b967d453bbf27	55783c9	2023-01-26	False
functionalTestDashboards	bc232a82ebfeede6bfc5631d5d6538fb4bf69d81	bc232a8	2023-01-26	False
securityDashboards	8e101672d9e9c8bc0bb03d88c9aac7054a2f79e0	8e10167	2023-01-26	False
anomalyDetectionDashboards	c14b0ac43ee420cde284232478a0d8fd42226ccf			False
queryWorkbenchDashboards	fe619d21348e61205da00823a83e20c5143b2142	fe619d2	2023-01-27	False
ganttChartDashboards	aa38960a5d339091be36f1b87dad26e6f2e53201			False
observabilityDashboards	b6ed90fc99ad82333a74c2883fecf03a070ff110	b6ed90f	2023-01-26	False
alertingDashboards	c7e9c76527ec23720e99baf9ce87dd6575e9760e	c7e9c76	2023-01-26	False
indexManagementDashboards	ac5c375a6b19bf00eb79391920c3a7a792e86f01	ac5c375	2023-01-26	False
reportsDashboards	f6008d1902e2bce8f4ea63afa184ff48fcd3e2ab	f6008d1	2023-01-26	False

[Divyaasm]

Issues were created to bump the versions for all the involved components and for Retrospective.