diff --git a/.github/workflows/encoding-check.yml b/.github/workflows/encoding-check.yml
new file mode 100644
index 0000000000..ade95e5f37
--- /dev/null
+++ b/.github/workflows/encoding-check.yml
@@ -0,0 +1,27 @@
+name: Encoding Checker
+
+on: [pull_request]
+
+jobs:
+ encoding-checker:
+ runs-on: ubuntu-latest
+ steps:
+ - name: Checkout repository
+ uses: actions/checkout@v3
+ - name: Check for possible file that does not follow utf-8 encoding
+ run: |
+ set +e
+ IFS=$(echo -en "\n\b")
+ COUNTER=0
+ for i in `find . -type f \( -name "*.txt" -o -name "*.md" -o -name "*.markdown" -o -name "*.html" \) | grep -vE "^./.git"`;
+ do
+ grep -axv '.*' "$i"
+ if [ "$?" -eq 0 ]; then
+ echo -e "######################\n$i\n######################"
+ COUNTER=$(( COUNTER + 1 ))
+ fi
+ done
+ if [ "$COUNTER" != 0 ]; then
+ echo "Found files that is not following utf-8 encoding, exit 1"
+ exit 1
+ fi
diff --git a/.github/workflows/vale.yml b/.github/workflows/vale.yml
index 4089db4696..9d105ed11f 100644
--- a/.github/workflows/vale.yml
+++ b/.github/workflows/vale.yml
@@ -22,3 +22,4 @@ jobs:
filter_mode: added
vale_flags: "--no-exit"
version: 2.28.0
+ continue-on-error: true
diff --git a/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-docker-arm64.markdown b/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-docker-arm64.markdown
new file mode 100644
index 0000000000..396ea4a0c4
--- /dev/null
+++ b/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-docker-arm64.markdown
@@ -0,0 +1,21 @@
+---
+role: daemon
+artifact_id: opensearch
+version: 2.13.0
+platform: docker
+architecture: arm64
+slug: opensearch-2.13.0-docker-arm64
+category: opensearch
+type: docker
+inline_instructions:
+- label: "Docker Hub"
+ code: docker pull opensearchproject/opensearch:2.13.0
+ link:
+ label: View on Docker Hub
+ url: https://hub.docker.com/r/opensearchproject/opensearch/tags?page=1&ordering=last_updated&name=2.13.0
+- label: "Amazon ECR"
+ code: docker pull public.ecr.aws/opensearchproject/opensearch:2.13.0
+ link:
+ label: View on Amazon ECR
+ url: https://gallery.ecr.aws/opensearchproject/opensearch
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-freebsd-arm64.markdown b/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-freebsd-arm64.markdown
new file mode 100644
index 0000000000..8bf8e6c412
--- /dev/null
+++ b/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-freebsd-arm64.markdown
@@ -0,0 +1,12 @@
+---
+role: daemon
+artifact_id: opensearch
+version: 2.13.0
+platform: freebsd
+architecture: arm64
+slug: opensearch-2.13.0-freebsd-arm64
+category: opensearch
+type: system-package
+freebsd_package_name: opensearch
+link: https://www.freshports.org/textproc/opensearch
+---
diff --git a/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-linux-arm64-deb.markdown b/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-linux-arm64-deb.markdown
new file mode 100644
index 0000000000..296663f7fc
--- /dev/null
+++ b/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-linux-arm64-deb.markdown
@@ -0,0 +1,13 @@
+---
+role: daemon
+artifact_id: opensearch
+version: 2.13.0
+platform: linux
+architecture: arm64
+artifact_url: https://artifacts.opensearch.org/releases/bundle/opensearch/2.13.0/opensearch-2.13.0-linux-arm64.deb
+slug: opensearch-2.13.0-linux-arm64-deb
+category: opensearch
+type: deb
+guide: https://opensearch.org/docs/latest/opensearch/install/deb
+signature: https://artifacts.opensearch.org/releases/bundle/opensearch/2.13.0/opensearch-2.13.0-linux-arm64.deb.sig
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-linux-arm64-rpm.markdown b/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-linux-arm64-rpm.markdown
new file mode 100644
index 0000000000..3f7a966fc1
--- /dev/null
+++ b/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-linux-arm64-rpm.markdown
@@ -0,0 +1,13 @@
+---
+role: daemon
+artifact_id: opensearch
+version: 2.13.0
+platform: linux
+architecture: arm64
+artifact_url: https://artifacts.opensearch.org/releases/bundle/opensearch/2.13.0/opensearch-2.13.0-linux-arm64.rpm
+slug: opensearch-2.13.0-linux-arm64-rpm
+category: opensearch
+type: rpm
+guide: https://opensearch.org/docs/latest/opensearch/install/rpm
+signature: https://artifacts.opensearch.org/releases/bundle/opensearch/2.13.0/opensearch-2.13.0-linux-arm64.rpm.sig
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-linux-arm64-yum.markdown b/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-linux-arm64-yum.markdown
new file mode 100644
index 0000000000..c0017fca38
--- /dev/null
+++ b/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-linux-arm64-yum.markdown
@@ -0,0 +1,13 @@
+---
+role: daemon
+artifact_id: opensearch
+version: 2.13.0
+platform: linux
+architecture: arm64
+slug: opensearch-2.13.0-linux-arm64-yum
+category: opensearch
+type: yum
+guide: https://opensearch.org/docs/latest/opensearch/install/rpm
+artifact_url: https://artifacts.opensearch.org/releases/bundle/opensearch/2.x/opensearch-2.x.repo
+signature: https://artifacts.opensearch.org/releases/bundle/opensearch/2.x/opensearch-2.x.repo.sig
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-linux-arm64.markdown b/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-linux-arm64.markdown
new file mode 100644
index 0000000000..ba5541d5be
--- /dev/null
+++ b/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-linux-arm64.markdown
@@ -0,0 +1,13 @@
+---
+role: daemon
+artifact_id: opensearch
+version: 2.13.0
+platform: linux
+architecture: arm64
+artifact_url: https://artifacts.opensearch.org/releases/bundle/opensearch/2.13.0/opensearch-2.13.0-linux-arm64.tar.gz
+
+slug: opensearch-2.13.0-linux-arm64
+category: opensearch
+type: targz
+signature: https://artifacts.opensearch.org/releases/bundle/opensearch/2.13.0/opensearch-2.13.0-linux-arm64.tar.gz.sig
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-min-linux-arm64.markdown b/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-min-linux-arm64.markdown
new file mode 100644
index 0000000000..72e5f605b2
--- /dev/null
+++ b/_artifacts/opensearch-2.13/arm64/opensearch-2.13.0-min-linux-arm64.markdown
@@ -0,0 +1,15 @@
+---
+role: daemon
+artifact_id: opensearch-min
+version: 2.13.0
+platform: linux
+architecture: arm64
+slug: opensearch-2.13.0-min-linux-arm64
+category: opensearch
+type: targz
+
+artifact_url: https://artifacts.opensearch.org/releases/core/opensearch/2.13.0/opensearch-min-2.13.0-linux-arm64.tar.gz
+signature: https://artifacts.opensearch.org/releases/core/opensearch/2.13.0/opensearch-min-2.13.0-linux-arm64.tar.gz.sig
+security_warning: true
+indirect: true
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-docker-arm64.markdown b/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-docker-arm64.markdown
new file mode 100644
index 0000000000..465e23f248
--- /dev/null
+++ b/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-docker-arm64.markdown
@@ -0,0 +1,21 @@
+---
+role: ui
+artifact_id: opensearch-dashboards
+version: 2.13.0
+platform: docker
+architecture: arm64
+slug: opensearch-dashboards-2.13.0-docker-arm64
+category: opensearch-dashboards
+type: docker
+inline_instructions:
+- label: "Docker Hub"
+ code: docker pull opensearchproject/opensearch-dashboards:2.13.0
+ link:
+ label: View on Docker Hub
+ url: https://hub.docker.com/r/opensearchproject/opensearch-dashboards/tags?page=1&ordering=last_updated&name=2.13.0
+- label: "Amazon ECR"
+ code: docker pull public.ecr.aws/opensearchproject/opensearch-dashboards:2.13.0
+ link:
+ label: View on Amazon ECR
+ url: https://gallery.ecr.aws/opensearchproject/opensearch-dashboards
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-freebsd-arm64.markdown b/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-freebsd-arm64.markdown
new file mode 100644
index 0000000000..4b0dfa0512
--- /dev/null
+++ b/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-freebsd-arm64.markdown
@@ -0,0 +1,13 @@
+---
+role: ui
+title: OpenSearch Dashboards
+artifact_id: opensearch-dashboards
+architecture: arm64
+platform: freebsd
+type: system-package
+category: opensearch-dashboards
+slug: opensearch-dashboards-2.13.0-freebsd-arm64
+version: 2.13.0
+freebsd_package_name: opensearch-dashboards
+link: https://www.freshports.org/textproc/opensearch-dashboards
+---
diff --git a/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-linux-arm64-deb.markdown b/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-linux-arm64-deb.markdown
new file mode 100644
index 0000000000..3db29bcb02
--- /dev/null
+++ b/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-linux-arm64-deb.markdown
@@ -0,0 +1,14 @@
+---
+role: ui
+title: OpenSearch Dashboards
+artifact_id: opensearch-dashboards
+architecture: arm64
+platform: linux
+type: deb
+artifact_url: https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.13.0/opensearch-dashboards-2.13.0-linux-arm64.deb
+version: 2.13.0
+category: opensearch-dashboards
+slug: opensearch-dashboards-2.13.0-linux-arm64-deb
+signature: https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.13.0/opensearch-dashboards-2.13.0-linux-arm64.deb.sig
+guide: https://opensearch.org/docs/latest/opensearch/install/deb
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-linux-arm64-rpm.markdown b/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-linux-arm64-rpm.markdown
new file mode 100644
index 0000000000..c48b30f0a0
--- /dev/null
+++ b/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-linux-arm64-rpm.markdown
@@ -0,0 +1,14 @@
+---
+role: ui
+title: OpenSearch Dashboards
+artifact_id: opensearch-dashboards
+architecture: arm64
+platform: linux
+type: rpm
+artifact_url: https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.13.0/opensearch-dashboards-2.13.0-linux-arm64.rpm
+version: 2.13.0
+category: opensearch-dashboards
+slug: opensearch-dashboards-2.13.0-linux-arm64-rpm
+signature: https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.13.0/opensearch-dashboards-2.13.0-linux-arm64.rpm.sig
+guide: https://opensearch.org/docs/latest/opensearch/install/rpm
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-linux-arm64-yum.markdown b/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-linux-arm64-yum.markdown
new file mode 100644
index 0000000000..7b1306889c
--- /dev/null
+++ b/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-linux-arm64-yum.markdown
@@ -0,0 +1,14 @@
+---
+role: ui
+title: OpenSearch Dashboards
+artifact_id: opensearch-dashboards
+architecture: arm64
+platform: linux
+type: yum
+artifact_url: https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.x/opensearch-dashboards-2.x.repo
+version: 2.13.0
+category: opensearch-dashboards
+slug: opensearch-dashboards-2.13.0-linux-arm64-yum
+signature: https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.x/opensearch-dashboards-2.x.repo.sig
+guide: https://opensearch.org/docs/latest/opensearch/install/rpm
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-linux-arm64.markdown b/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-linux-arm64.markdown
new file mode 100644
index 0000000000..3f40ca6cbf
--- /dev/null
+++ b/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-linux-arm64.markdown
@@ -0,0 +1,14 @@
+---
+role: ui
+title: OpenSearch Dashboards
+artifact_id: opensearch-dashboards
+architecture: arm64
+platform: linux
+type: targz
+artifact_url: https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.13.0/opensearch-dashboards-2.13.0-linux-arm64.tar.gz
+version: 2.13.0
+category: opensearch-dashboards
+slug: opensearch-dashboards-2.13.0-linux-arm64
+signature: https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.13.0/opensearch-dashboards-2.13.0-linux-arm64.tar.gz.sig
+---
+
diff --git a/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-min-linux-arm64.markdown b/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-min-linux-arm64.markdown
new file mode 100644
index 0000000000..593eca5143
--- /dev/null
+++ b/_artifacts/opensearch-2.13/arm64/opensearch-dashboards-2.13.0-min-linux-arm64.markdown
@@ -0,0 +1,15 @@
+---
+role: ui
+title: OpenSearch Dashboards
+artifact_id: opensearch-dashboards-min
+architecture: arm64
+platform: linux
+type: targz
+artifact_url: https://artifacts.opensearch.org/releases/core/opensearch-dashboards/2.13.0/opensearch-dashboards-min-2.13.0-linux-arm64.tar.gz
+category: opensearch-dashboards
+slug: opensearch-dashboards-2.13.0-min-linux-arm64
+signature: https://artifacts.opensearch.org/releases/core/opensearch-dashboards/2.13.0/opensearch-dashboards-min-2.13.0-linux-arm64.tar.gz.sig
+version: 2.13.0
+security_warning: true
+indirect: true
+---
diff --git a/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-docker-x64.markdown b/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-docker-x64.markdown
new file mode 100644
index 0000000000..a9d3a29199
--- /dev/null
+++ b/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-docker-x64.markdown
@@ -0,0 +1,21 @@
+---
+role: daemon
+artifact_id: opensearch
+version: 2.13.0
+platform: docker
+architecture: x64
+slug: opensearch-2.13.0-docker-x64
+category: opensearch
+type: docker
+inline_instructions:
+- label: "Docker Hub"
+ code: docker pull opensearchproject/opensearch:2.13.0
+ link:
+ label: View on Docker Hub
+ url: https://hub.docker.com/r/opensearchproject/opensearch/tags?page=1&ordering=last_updated&name=2.13.0
+- label: "Amazon ECR"
+ code: docker pull public.ecr.aws/opensearchproject/opensearch:2.13.0
+ link:
+ label: View on Amazon ECR
+ url: https://gallery.ecr.aws/opensearchproject/opensearch
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-freebsd-x64.markdown b/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-freebsd-x64.markdown
new file mode 100644
index 0000000000..b546ef328f
--- /dev/null
+++ b/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-freebsd-x64.markdown
@@ -0,0 +1,12 @@
+---
+role: daemon
+artifact_id: opensearch
+version: 2.13.0
+platform: freebsd
+architecture: x64
+slug: opensearch-2.13.0-freebsd-x64
+category: opensearch
+type: system-package
+freebsd_package_name: opensearch
+link: https://www.freshports.org/textproc/opensearch
+---
diff --git a/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-linux-x64-deb.markdown b/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-linux-x64-deb.markdown
new file mode 100644
index 0000000000..7be2b1860b
--- /dev/null
+++ b/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-linux-x64-deb.markdown
@@ -0,0 +1,13 @@
+---
+role: daemon
+artifact_id: opensearch
+version: 2.13.0
+platform: linux
+architecture: x64
+artifact_url: https://artifacts.opensearch.org/releases/bundle/opensearch/2.13.0/opensearch-2.13.0-linux-x64.deb
+slug: opensearch-2.13.0-linux-x64-deb
+category: opensearch
+type: deb
+guide: https://opensearch.org/docs/latest/opensearch/install/deb
+signature: https://artifacts.opensearch.org/releases/bundle/opensearch/2.13.0/opensearch-2.13.0-linux-x64.deb.sig
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-linux-x64-rpm.markdown b/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-linux-x64-rpm.markdown
new file mode 100644
index 0000000000..2840f8ad6b
--- /dev/null
+++ b/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-linux-x64-rpm.markdown
@@ -0,0 +1,13 @@
+---
+role: daemon
+artifact_id: opensearch
+version: 2.13.0
+platform: linux
+architecture: x64
+artifact_url: https://artifacts.opensearch.org/releases/bundle/opensearch/2.13.0/opensearch-2.13.0-linux-x64.rpm
+slug: opensearch-2.13.0-linux-x64-rpm
+category: opensearch
+type: rpm
+guide: https://opensearch.org/docs/latest/opensearch/install/rpm
+signature: https://artifacts.opensearch.org/releases/bundle/opensearch/2.13.0/opensearch-2.13.0-linux-x64.rpm.sig
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-linux-x64-yum.markdown b/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-linux-x64-yum.markdown
new file mode 100644
index 0000000000..393a5f2ea1
--- /dev/null
+++ b/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-linux-x64-yum.markdown
@@ -0,0 +1,13 @@
+---
+role: daemon
+artifact_id: opensearch
+version: 2.13.0
+platform: linux
+architecture: x64
+slug: opensearch-2.13.0-linux-x64-yum
+category: opensearch
+type: yum
+guide: https://opensearch.org/docs/latest/opensearch/install/rpm
+artifact_url: https://artifacts.opensearch.org/releases/bundle/opensearch/2.x/opensearch-2.x.repo
+signature: https://artifacts.opensearch.org/releases/bundle/opensearch/2.x/opensearch-2.x.repo.sig
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-linux-x64.markdown b/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-linux-x64.markdown
new file mode 100644
index 0000000000..4c35043983
--- /dev/null
+++ b/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-linux-x64.markdown
@@ -0,0 +1,12 @@
+---
+role: daemon
+artifact_id: opensearch
+version: 2.13.0
+platform: linux
+architecture: x64
+artifact_url: https://artifacts.opensearch.org/releases/bundle/opensearch/2.13.0/opensearch-2.13.0-linux-x64.tar.gz
+slug: opensearch-2.13.0-linux-x64
+category: opensearch
+type: targz
+signature: https://artifacts.opensearch.org/releases/bundle/opensearch/2.13.0/opensearch-2.13.0-linux-x64.tar.gz.sig
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-min-linux-x64.markdown b/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-min-linux-x64.markdown
new file mode 100644
index 0000000000..0014484616
--- /dev/null
+++ b/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-min-linux-x64.markdown
@@ -0,0 +1,14 @@
+---
+role: daemon
+artifact_id: opensearch-min
+version: 2.13.0
+platform: linux
+architecture: x64
+artifact_url: https://artifacts.opensearch.org/releases/core/opensearch/2.13.0/opensearch-min-2.13.0-linux-x64.tar.gz
+slug: opensearch-2.13.0-min-linux-x64
+category: opensearch
+type: targz
+signature: https://artifacts.opensearch.org/releases/core/opensearch/2.13.0/opensearch-min-2.13.0-linux-x64.tar.gz.sig
+security_warning: true
+indirect: true
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-windows-x64.markdown b/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-windows-x64.markdown
new file mode 100644
index 0000000000..89a12c67fb
--- /dev/null
+++ b/_artifacts/opensearch-2.13/x64/opensearch-2.13.0-windows-x64.markdown
@@ -0,0 +1,12 @@
+---
+role: daemon
+artifact_id: opensearch
+version: 2.13.0
+platform: windows
+architecture: x64
+artifact_url: https://artifacts.opensearch.org/releases/bundle/opensearch/2.13.0/opensearch-2.13.0-windows-x64.zip
+slug: opensearch-2.13.0-windows-x64
+category: opensearch
+type: zip
+signature: https://artifacts.opensearch.org/releases/bundle/opensearch/2.13.0/opensearch-2.13.0-windows-x64.zip.sig
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-docker-x64.markdown b/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-docker-x64.markdown
new file mode 100644
index 0000000000..67f29df19c
--- /dev/null
+++ b/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-docker-x64.markdown
@@ -0,0 +1,21 @@
+---
+role: ui
+artifact_id: opensearch-dashboards
+version: 2.13.0
+platform: docker
+architecture: x64
+slug: opensearch-dashboards-2.13.0-docker-x64
+category: opensearch-dashboards
+type: docker
+inline_instructions:
+- label: "Docker Hub"
+ code: docker pull opensearchproject/opensearch-dashboards:2.13.0
+ link:
+ label: View on Docker Hub
+ url: https://hub.docker.com/r/opensearchproject/opensearch-dashboards/tags?page=1&ordering=last_updated&name=2.13.0
+- label: "Amazon ECR"
+ code: docker pull public.ecr.aws/opensearchproject/opensearch-dashboards:2.13.0
+ link:
+ label: View on Amazon ECR
+ url: https://gallery.ecr.aws/opensearchproject/opensearch-dashboards
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-freebsd-x64.markdown b/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-freebsd-x64.markdown
new file mode 100644
index 0000000000..0d514eeae7
--- /dev/null
+++ b/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-freebsd-x64.markdown
@@ -0,0 +1,13 @@
+---
+role: ui
+title: OpenSearch Dashboards
+artifact_id: opensearch-dashboards
+architecture: x64
+platform: freebsd
+type: system-package
+category: opensearch-dashboards
+slug: opensearch-dashboards-2.13.0-freebsd-x64
+version: 2.13.0
+freebsd_package_name: opensearch-dashboards
+link: https://www.freshports.org/textproc/opensearch-dashboards
+---
diff --git a/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-linux-x64-deb.markdown b/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-linux-x64-deb.markdown
new file mode 100644
index 0000000000..f7239f4ac8
--- /dev/null
+++ b/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-linux-x64-deb.markdown
@@ -0,0 +1,14 @@
+---
+role: ui
+title: OpenSearch Dashboards
+artifact_id: opensearch-dashboards
+architecture: x64
+platform: linux
+type: deb
+artifact_url: https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.13.0/opensearch-dashboards-2.13.0-linux-x64.deb
+version: 2.13.0
+category: opensearch-dashboards
+slug: opensearch-dashboards-2.13.0-linux-x64-deb
+signature: https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.13.0/opensearch-dashboards-2.13.0-linux-x64.deb.sig
+guide: https://opensearch.org/docs/latest/opensearch/install/deb
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-linux-x64-rpm.markdown b/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-linux-x64-rpm.markdown
new file mode 100644
index 0000000000..21be8c6c81
--- /dev/null
+++ b/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-linux-x64-rpm.markdown
@@ -0,0 +1,14 @@
+---
+role: ui
+title: OpenSearch Dashboards
+artifact_id: opensearch-dashboards
+architecture: x64
+platform: linux
+type: rpm
+artifact_url: https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.13.0/opensearch-dashboards-2.13.0-linux-x64.rpm
+version: 2.13.0
+category: opensearch-dashboards
+slug: opensearch-dashboards-2.13.0-linux-x64-rpm
+signature: https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.13.0/opensearch-dashboards-2.13.0-linux-x64.rpm.sig
+guide: https://opensearch.org/docs/latest/opensearch/install/rpm
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-linux-x64-yum.markdown b/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-linux-x64-yum.markdown
new file mode 100644
index 0000000000..ec8bb5db6c
--- /dev/null
+++ b/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-linux-x64-yum.markdown
@@ -0,0 +1,14 @@
+---
+role: ui
+title: OpenSearch Dashboards
+artifact_id: opensearch-dashboards
+architecture: x64
+platform: linux
+type: yum
+artifact_url: https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.x/opensearch-dashboards-2.x.repo
+version: 2.13.0
+category: opensearch-dashboards
+slug: opensearch-dashboards-2.13.0-linux-x64-yum
+signature: https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.x/opensearch-dashboards-2.x.repo.sig
+guide: https://opensearch.org/docs/latest/opensearch/install/rpm
+---
\ No newline at end of file
diff --git a/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-linux-x64.markdown b/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-linux-x64.markdown
new file mode 100644
index 0000000000..0585559dfb
--- /dev/null
+++ b/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-linux-x64.markdown
@@ -0,0 +1,14 @@
+---
+role: ui
+title: OpenSearch Dashboards
+artifact_id: opensearch-dashboards
+architecture: x64
+platform: linux
+type: targz
+artifact_url: https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.13.0/opensearch-dashboards-2.13.0-linux-x64.tar.gz
+category: opensearch-dashboards
+slug: opensearch-dashboards-2.13.0-linux-x64
+signature: https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.13.0/opensearch-dashboards-2.13.0-linux-x64.tar.gz.sig
+version: 2.13.0
+---
+
diff --git a/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-min-linux-x64.markdown b/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-min-linux-x64.markdown
new file mode 100644
index 0000000000..1fa04bc195
--- /dev/null
+++ b/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-min-linux-x64.markdown
@@ -0,0 +1,15 @@
+---
+role: ui
+title: OpenSearch Dashboards
+artifact_id: opensearch-dashboards-min
+architecture: x64
+platform: linux
+type: targz
+artifact_url: https://artifacts.opensearch.org/releases/core/opensearch-dashboards/2.13.0/opensearch-dashboards-min-2.13.0-linux-x64.tar.gz
+category: opensearch-dashboards
+slug: opensearch-dashboards-2.13.0-min-linux-x64
+signature: https://artifacts.opensearch.org/releases/core/opensearch-dashboards/2.13.0/opensearch-dashboards-min-2.13.0-linux-x64.tar.gz.sig
+version: 2.13.0
+security_warning: true
+indirect: true
+---
diff --git a/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-windows-x64.markdown b/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-windows-x64.markdown
new file mode 100644
index 0000000000..060593d47a
--- /dev/null
+++ b/_artifacts/opensearch-2.13/x64/opensearch-dashboards-2.13.0-windows-x64.markdown
@@ -0,0 +1,14 @@
+---
+role: ui
+title: OpenSearch Dashboards
+artifact_id: opensearch-dashboards
+architecture: x64
+platform: windows
+type: zip
+artifact_url: https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.13.0/opensearch-dashboards-2.13.0-windows-x64.zip
+category: opensearch-dashboards
+slug: opensearch-dashboards-2.13.0-windows-x64
+signature: https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.13.0/opensearch-dashboards-2.13.0-windows-x64.zip.sig
+version: 2.13.0
+---
+
diff --git a/_community_members/apaponaud.md b/_community_members/apaponaud.md
new file mode 100644
index 0000000000..31e6c6170f
--- /dev/null
+++ b/_community_members/apaponaud.md
@@ -0,0 +1,32 @@
+---
+short_name: "apaponaud"
+name: "Aline Paponaud"
+photo: '/assets/media/community/members/apaponaud.jpg'
+primary_title: "apaponaud"
+title: 'OpenSearch Community Member: Aline Paponaud'
+job_title_and_company: "CTO of Adelean"
+breadcrumbs:
+ icon: community
+ items:
+ - title: Community
+ url: /community/index.html
+ - title: Members
+ url: /community/members/index.html
+ - title: 'Aline Paponaud's Profile'
+ url: '/community/members/apaponaud.html'
+personas:
+ - conference_speaker
+permalink: '/community/members/apaponaud.html'
+keynote_speaker: false
+conference_id:
+ - "2024-europe"
+session_track:
+ - conference_id: "2024-europe"
+ - name: "Search"
+linkedin: "paponaud"
+twitter: "bootis"
+mastodon:
+ url: https://fosstodon.org/@bootis
+ name: "@bootis"
+---
+Works with many customers into implementing search engines, helping them improve efficiency and use it for various use cases from search to observability. CTO of [Adelean](https://adelean.com)
\ No newline at end of file
diff --git a/_community_members/arubin.md b/_community_members/arubin.md
index a15e43ac59..5a39814f05 100644
--- a/_community_members/arubin.md
+++ b/_community_members/arubin.md
@@ -1,9 +1,11 @@
---
-name: Anton Rubin
-short_name: arubin
+short_name: "arubin"
+name: "Anton Rubin"
photo: '/assets/media/community/members/arubin.jpg'
+primary_title: "Anton Rubin"
title: 'OpenSearch Community Member: Anton Rubin'
-primary_title: Anton Rubin
+
+
breadcrumbs:
icon: community
items:
@@ -15,10 +17,16 @@ breadcrumbs:
url: '/community/members/anton-rubin.html'
github: 'eliatra'
linkedin: 'anton-rubin-89a186150'
-job_title_and_company: 'technical support engineer at Eliatra'
+job_title_and_company: 'Technical Support Engineer at Eliatra'
personas:
- author
-permalink: '/community/members/anton-rubin.html'
+ - conference_speaker
+permalink: '/community/members/arubin.html'
+keynote_speaker: false
+conference_id:
+ - "2024-europe"
+session_track:
+ - conference_id: "2024-europe"
+ - name: "OpenSearch in Kubernetes: Helm Charts and Operator"
---
-
-Anton Rubin is a technical support engineer at [Eliatra](https://eliatra.com/){:target="_blank"}. Having worked on the front lines of Symantec and other large companies, Anton has developed a passion for security in distributed systems and search engines. Combined with strong desire to share knowledge, he is eager to make security simple to follow and implement across any OpenSearch environment
+Anton Rubin is a distinguished cybersecurity expert known for his proficiency in navigating intricate organizational frameworks and driving technological advancement. Graduating with a Class 1 Honours degree in Cyber Security and Digital Forensics, Anton embarked on his professional journey. He began by ensuring the quality of security content production, working with security giants like Symantec, where he honed his skills and expertise. Anton's journey further evolved as he transitioned into technical support roles across diverse environments, including his notable tenure as a Technical Support Engineer at Eliatra, where he is focusing on supporting OpenSearch project users. In this pivotal role, he provided crucial assistance to clients, troubleshooting complex issues and ensuring seamless operation of OpenSearch. Certified as a Kubernetes Administrator & Application Developer, he continually pursues excellence and innovation in the field, staying abreast of the latest technological trends and advancements. Passionate about continuous learning, Anton is dedicated to shaping the future of technology with his ingenuity and commitment.
\ No newline at end of file
diff --git a/_community_members/epugh.md b/_community_members/epugh.md
index ff9e193c59..18ad8fbe28 100644
--- a/_community_members/epugh.md
+++ b/_community_members/epugh.md
@@ -1,35 +1,29 @@
---
-# short_name: 'epugh'
-short_name: ericpugh
-name: 'Eric Pugh'
+name: "Eric Pugh"
+short_name: epugh
photo: '/assets/media/community/members/ericpugh.jpg'
-job_title_and_company: 'Co-founder and CEO of Open Source Connections'
-primary_title: 'Eric Pugh'
title: 'OpenSearch Community Member: Eric Pugh'
+primary_title: 'Eric Pugh'
breadcrumbs:
icon: community
items:
- - title: Community
- url: /community/index.html
- - title: Members
- url: /community/members/index.html
- - title: "Eric Pugh Profile"
- url: '/community/members/eric-pugh.html'
-# mastodon:
-# url: https://hachyderm.io/@flaxsearch
-# name: flaxsearch
+ - title: Community
+ url: /community/index.html
+ - title: Members
+ url: /community/members/index.html
+ - title: "Eric Pugh's Profile"
+ url: '/community/members/eric-pugh.html'
twitter: 'dep4b'
github: epugh
linkedin: 'epugh'
-session_track:
- - conference_id: "2024-europe"
- name: "Workshops"
permalink: '/community/members/eric-pugh.html'
+job_title_and_company: 'Co-founder and CEO of Open Source Connections'
personas:
- conference_speaker
- author
-conference_id:
- - "2024-europe"
----
+session_track:
+ - conference_id: "2024-europe"
+ name: "Search"
-**Eric Pugh** is the co-founder and CEO of OpenSource Connections. Today he helps OSC’s clients, especially those in the ecommerce space, build their own search teams and improve their search maturity, both by leading projects and by acting as a trusted advisor.
+---
+Eric Pugh is the co-founder of OpenSource Connections. Today he helps OSC’s clients, especially those in the ecommerce space, build their own search teams and improve their search maturity, both by leading projects and by acting as a trusted advisor.Fascinated by the craft of software development, Eric Pugh has been involved in the open source world as a tester, developer, committer and user for the past twenty years. He is a member of the Apache Software Foundation and co-authored the book Apache Solr Enterprise Search Server, now on its third edition. He stewards Quepid, an open source platform for assessing and improving your search relevance.OpenSource Connections mission to empower the world's search teams comes directly from Eric’s belief in the open source software movement, and the importance of educating people to succeed with it, so that people own their technology.When not thinking about search, Eric likes to get his hands dirty by building furniture. His next project is a reproduction Danish modern couch, using just hand tools!
\ No newline at end of file
diff --git a/_community_members/jbrand.md b/_community_members/jbrand.md
new file mode 100644
index 0000000000..47987d28a1
--- /dev/null
+++ b/_community_members/jbrand.md
@@ -0,0 +1,28 @@
+---
+short_name: "jbrand"
+name: "Jannik Brand"
+job_title_and_company: "Jannnik Brand"
+photo: '/assets/media/community/members/no-image-available.svg'
+primary_title: "Jannik Brand"
+title: 'OpenSearch Community Member: Jannik Brand'
+breadcrumbs:
+ icon: community
+ items:
+ - title: Community
+ url: /community/index.html
+ - title: Members
+ url: /community/members/index.html
+ - title: 'Jannik Brand's Profile'
+ url: '/community/members/jbrand.html'
+personas:
+ - conference_speaker
+permalink: '/community/members/jbrand.html'
+keynote_speaker: false
+conference_id:
+ - "2024-europe"
+session_track:
+ - conference_id: "2024-europe"
+ - name: "Search"
+---
+
+Jannik Brand
\ No newline at end of file
diff --git a/_community_members/luchoa.md b/_community_members/luchoa.md
index d5c1f6d766..196173e838 100644
--- a/_community_members/luchoa.md
+++ b/_community_members/luchoa.md
@@ -2,7 +2,7 @@
short_name: 'luchoa'
name: 'Laysa Uchoa'
photo: '/assets/media/community/members/luchoa.jpg'
-job_title_and_company: 'PyLadies Munich Leader, and Developer Advocate, Aiven Oy'
+job_title_and_company: 'PyLadies Munich Leader, and Developer Advocate, Aiven'
primary_title: 'Laysa Uchoa'
title: 'OpenSearch Community Member: Laysa Uchoa'
breadcrumbs:
@@ -21,5 +21,6 @@ personas:
- conference_speaker
conference_id:
- "2022-north-america"
+ - "2024-europe"
---
Laysa is a software developer and advocate, Head of Fullstack Events Association, and the Leader of PyLadies Munich. She is also an OSS contributor, organizer of OCPP communities, and a contributor to the OCPP Python package.
diff --git a/_community_members/macrakis.md b/_community_members/macrakis.md
index 8a70246aa3..de2e16ca50 100644
--- a/_community_members/macrakis.md
+++ b/_community_members/macrakis.md
@@ -17,8 +17,9 @@ github: macrakis
linkedin: macrakis
job_title_and_company: 'The senior technical product manager for OpenSearch'
personas:
+ - conference_speaker
- author
+
permalink: '/community/members/stavros-macrakis.html'
---
-
-**Stavros Macrakis** is the senior technical product manager for OpenSearch focusing on document and e-commerce search. He has worked on search for almost 20 years and is passionate about search relevance.
+Stavros Macrakis is the senior technical product manager for OpenSearch focusing on document and e-commerce search. He has worked on search for almost 20 years and is passionate about search relevance.
diff --git a/_community_members/nbandener.md b/_community_members/nbandener.md
new file mode 100644
index 0000000000..772e9bddcb
--- /dev/null
+++ b/_community_members/nbandener.md
@@ -0,0 +1,81 @@
+---
+#
+# Sample data for community members.
+#
+
+# The short name is used to identify related pieces of content in the site. For example it is used in the "authors" array of blog posts, and it is used in the "presenters" array for OpenSearch Conference sessions to identify who is speaking.
+# The format for existing values is not normalized. In some cases it is "first-initial-of-first-name" + "last-name", or matching a GitHub username, or something all together random. What is important is that it is unique within the system.
+short_name: "nbandener"
+
+# The member's full name, or otherwise meaningful preferred name. It is used in the templates for presenting content authors as well as the name of conference speakers.
+name: "Nils Bandener"
+
+# The path to the community member's photo.
+photo: "/assets/media/community/members/nbandener.jpg"
+
+# Used as the level 1 page header text.
+primary_title: 'Nils Bandener'
+
+# Used as the document title displayed in the browser title bar.
+title: 'OpenSearch Project Community Member: Nils Bandener'
+
+# Breadcrumbs specification.
+# The community icon is expected.
+# The breadcrumbs path structure is Communit -> Members -> First Last's Profile.
+breadcrumbs:
+ icon: community
+ items:
+ - title: Community
+ url: /community/index.html
+ - title: Members
+ url: /community/members/index.html
+ - title: "Nils Bandener's Profile"
+ url: '/community/members/nbandener.html'
+
+# Community member job title and company where they work.
+job_title_and_company: 'Freelance Software Architect'
+
+# Array of conference IDs for which the community member is a keynote speaker, if any, or boolean false otherwise.
+# This value is only relevant for member's with the "conference_speaker" user persona.
+#keynote_speaker:
+# - '2023-north-america'
+keynote_speaker: false
+
+# The conference topic track for the conference sessions that the user is a speaker. These are shaped as an array of value pairs mapping conference ID and name.
+# For example for the North American conference for the year 2023, and the "Community" track:
+session_track:
+ - conference_id: "2024-europe"
+ name: "Operating OpenSearch"
+
+# URL for the community member profile.
+permalink: '/community/members/nbendener.html'
+
+# Array of community member user personas.
+# At this time, only conference_speaker, and author are defined.
+personas:
+ - conference_speaker
+
+
+# Array of conference IDs that the member is a speaker.
+conference_id:
+ - "2024-europe"
+
+
+# Optional GitHub username
+#github: githubusername
+
+# Optional LinkedIn username
+linkedin: nils-bandener
+
+# Optional Twitter username
+#twitter: twitterusername
+
+# Optional Mastodon server url, and username / handle.
+#mastodon:
+# url: https://mastodon.social/@mastodonusername
+# name: mastodonusername
+
+---
+Nils Bandener
+
+Freelance software architect with long track record in security and infrastructure software. Interested in finding optimal solutions which combine broad functionality with a user-centric view. Track record of many years in security software via collaborations with Search Guard and Eliatra.
diff --git a/_community_members/pmele.md b/_community_members/pmele.md
new file mode 100644
index 0000000000..6c100af0c8
--- /dev/null
+++ b/_community_members/pmele.md
@@ -0,0 +1,40 @@
+---
+short_name: "pmele"
+name: "Pietro Mele"
+job_title_and_company: "Software Engineer at Adelean"
+photo: '/assets/media/community/members/pmele.jpg'
+primary_title: "pmele"
+title: 'OpenSearch Community Member: Pietro Mele'
+breadcrumbs:
+ icon: community
+ items:
+ - title: Community
+ url: /community/index.html
+ - title: Members
+ url: /community/members/index.html
+ - title: 'Pietro Mele's Profile'
+ url: '/community/members/pmele.html'
+personas:
+ - conference_speaker
+permalink: '/community/members/pmele.html'
+keynote_speaker: false
+conference_id:
+ - "2024-europe"
+session_track:
+ - conference_id: "2024-europe"
+ - name: "Search"
+#linkedin:
+#twitter:
+#mastodon:
+# url:
+# name:
+---
+Pietro Mele
+
+I'm Pietro, a highly motivated software engineer with a passion for developing cutting-edge search engine solutions. Throughout my career, I've had the privilege of working at Adelean and the INA (French media institution responsible for preserving and promoting French audio-visual heritage), where I've gained valuable experience and honed my expertise in utilizing Elasticsearch to deliver efficient and effective search results.
+
+My background encompasses a strong foundation in machine learning and computer vision, which allows me to incorporate intelligent algorithms into my work. I'm constantly driven to learn and expand my skillset, staying up-to-date with the latest advancements in the field.
+
+Outside of work, I find great pleasure in reading, engaging in sports activities, and even coding for fun. These hobbies not only help me relax and recharge but also provide me with opportunities to explore new ideas and experiment with different programming techniques.
+
+Overall, I am an enthusiastic and dedicated software engineer who thrives on solving complex problems and pushing the boundaries of what's possible in search engine development.
\ No newline at end of file
diff --git a/_community_members/ybarabash.md b/_community_members/ybarabash.md
new file mode 100644
index 0000000000..9c6e2e7c60
--- /dev/null
+++ b/_community_members/ybarabash.md
@@ -0,0 +1,30 @@
+---
+short_name: "ybarabash"
+name: "Yuliia Barabash"
+photo: '/assets/media/community/members/no-image-available.svg'
+primary_title: "ybarabash"
+title: 'OpenSearch Community Member: Yuliia Barabash'
+job_title_and_company: "Cloud Engineer @ Nordcloud"
+breadcrumbs:
+ icon: community
+ items:
+ - title: Community
+ url: /community/index.html
+ - title: Members
+ url: /community/members/index.html
+ - title: 'Yuliia Barabash's Profile'
+ url: '/community/members/ybarabash.html'
+personas:
+ - conference_speaker
+permalink: '/community/members/ybarabash.html'
+keynote_speaker: false
+conference_id:
+ - "2024-europe"
+session_track:
+ - conference_id: "2024-europe"
+ - name: "Search"
+linkedin: "https://www.linkedin.com/in/yuliia-barabash/"
+twitter: "yuliia_barabash"
+---
+Yuliia Barabash
+Cloud Engineer @ Nordcloud | Master's in Computer Science, AWS Expert
\ No newline at end of file
diff --git a/_events/2024-0409-dev-triage-ml-commons.markdown b/_events/2024-0409-dev-triage-ml-commons.markdown
new file mode 100644
index 0000000000..bb91b33b4f
--- /dev/null
+++ b/_events/2024-0409-dev-triage-ml-commons.markdown
@@ -0,0 +1,83 @@
+---
+calendar_date: '2024-04-09'
+eventdate: 2024-04-09 10:30:00 -0800
+primary_title: Development Backlog & Triage Meeting - ml-commons - 2024-04-09
+title: Development Backlog & Triage Meeting - ml-commons - 2024-04-09
+online: true
+signup:
+ url: https://www.meetup.com/opensearch/events/299165833
+ title: Join on Meetup
+
+---
+
+Join the OpenSearch ml-commons team for their next backlog & triage planning meeting.
+
+(hosts: [Yaliang Wu](https://github.com/ylwu-amzn), [Dhrubo Saha](https://github.com/dhrubo-os), [Jing Zhang](https://github.com/jngz-es), & [Xun Zhang](https://github.com/Zhangxunmt))
+
+---
+
+**Join Zoom Meeting**
+```json
+https://us02web.zoom.us/j/82164218920
+
+Meeting ID: 821 6421 8920
+Passcode: 259735
+
+---
+
+One tap mobile
++12532050468,,82164218920# US
++12532158782,,82164218920# US (Tacoma)
+
+---
+Dial by your location
+• +1 253 205 0468 US
+• +1 253 215 8782 US (Tacoma)
+• +1 346 248 7799 US (Houston)
+• +1 669 444 9171 US
+• +1 669 900 9128 US (San Jose)
+• +1 719 359 4580 US
+• +1 646 558 8656 US (New York)
+• +1 646 931 3860 US
+• +1 689 278 1000 US
+• +1 301 715 8592 US (Washington DC)
+• +1 305 224 1968 US
+• +1 309 205 3325 US
+• +1 312 626 6799 US (Chicago)
+• +1 360 209 5623 US
+• +1 386 347 5053 US
+• +1 507 473 4847 US
+• +1 564 217 2000 US
+• 877 853 5247 US Toll-free
+• 888 788 0099 US Toll-free
+
+Meeting ID: 821 6421 8920
+
+Find your local number: https://us02web.zoom.us/u/kcboT3QOI
+
+```
+
+---
+
+**Agenda:**
+
+**Triage issues** *(add the triaged label once reviewed/ready. They can be also labelled as sprint backlog if we are looking to queueing them up next, or good first issue / help wanted when appropriate.)*
+
+* [Backend ml-commons](https://github.com/opensearch-project/ml-commons/issues)
+* [Dashboards ml-commons](https://github.com/opensearch-project/ml-commons-dashboards/issues)
+
+**Sprint backlog** *(Examine if it still reflects the work that we are committing to doing and is it in the right priority order)*
+
+* [Backend ml-commons](https://github.com/opensearch-project/ml-commons/issues)
+* [Dashboards ml-commons](https://github.com/opensearch-project/ml-commons-dashboards/issues)
+
+**Backlog** *(anything we should move to sprint backlog? anything we should tag asking for help from the community?)*
+
+* [Backend ml-commons](https://github.com/opensearch-project/ml-commons/issues)
+* [Dashboards ml-commons](https://github.com/opensearch-project/ml-commons-dashboards/issues)
+
+
+***Please see Meetup link for URL and required passcode.***
+
+
+*By joining the Development Backlog & Triage Meeting, you grant OpenSearch, and our affiliates the right to record, film, photograph, and capture your voice and image during the Development Backlog & Triage Meeting (the “Recordings”). You grant to us an irrevocable, nonexclusive, perpetual, worldwide, royalty-free right and license to use, reproduce, modify, distribute, and translate, for any purpose, all or any part of the Recordings and Your Materials. For example, we may distribute Recordings or snippets of Recordings via our social media outlets.*
diff --git a/_layouts/opensearchcon_landing.html b/_layouts/opensearchcon_landing.html
index caa37eddea..f4380587e4 100644
--- a/_layouts/opensearchcon_landing.html
+++ b/_layouts/opensearchcon_landing.html
@@ -29,8 +29,6 @@
{{ page.content | markdownify }}
- {% include redesign_buttons.html name="opensearchcon-stay-informed" %}
-
What is OpenSearchCon?
OpenSearchCon is the annual conference for the OpenSearch Project community. OpenSearchCon brings the community together to learn, connect, and collaborate.
This annual event aims to educate and inspire with presentation sessions, participant-driven meetings, and exhibits and demonstrations from OpenSearch Project partners.
diff --git a/_opensearchcon_sessions/2024-europe-how-sap-analyzes-opentelemetry-signals-using-data-prepper.md b/_opensearchcon_sessions/2024-europe-how-sap-analyzes-opentelemetry-signals-using-data-prepper.md
new file mode 100644
index 0000000000..228ecac2ec
--- /dev/null
+++ b/_opensearchcon_sessions/2024-europe-how-sap-analyzes-opentelemetry-signals-using-data-prepper.md
@@ -0,0 +1,54 @@
+---
+primary_presenter: jbrand
+speaker_name_full: "Jannik Brand"
+speaker_talk_title: 'How SAP analyzes OpenTelemetry signals using Data Prepper'
+primary_title: 'How SAP analyzes OpenTelemetry signals using Data Prepper'
+title: 'OpenSearchCon 2024 Session: How SAP analyzes OpenTelemetry signals using Data Prepper'
+
+breadcrumbs:
+ icon: community
+ items:
+ - title: OpenSearchCon
+ url: /events/opensearchcon/index.html
+ - title: 2024
+ url: /events/opensearchcon/2024/europe/index.html
+ - title: Europe
+ url: /events/opensearchcon/2024/europe/index.html
+ - title: Session Summaries
+ url: /events/opensearchcon/2024/europe/sessions/index.html
+
+# The template logic expects the following format: YYYY-MM-DD - h:m(am|pm)-(h:m(am|pm))
+session_time: "time TBD"
+
+# Room of location where the talk will occur.
+session_room: "a room yet to be determined."
+
+# Session topic track.
+session_track: "Analytics, Observability, and Security"
+
+# URL permalink for the session.
+permalink: '/events/opensearchcon/2024/europe/sessions/how-sap-analyzes-opentelemetry-signals-using-data-prepper.html'
+
+# ID of the YouTube video of the session to embed in the page.
+# This is to be added after the conference and after the session recordings
+# are uploaded to YouTube.
+#youtube_video_id: 'SOME_YOUTUBE_VIDEO_ID'
+
+# Conference ID.
+# It is normative to use the format of 'YYYY-location-name', eg. '2023-north-america'.
+conference_id: "2024-europe"
+# Array of short_name values for the Community Members with the conference_speaker persona whom are presenting the session. This includes the primary_speaker indicated above and any other presenters (if any).
+presenters:
+ - jbrand
+ - dvenable
+
+
+---
+
+OpenTelemetry is the CNCF standard for observability providing simple code instrumentations and vendor neutrality while supporting logs, metrics, and traces. This increases the demand for observability backends supporting this format. Analyzing observability data is one of the main use cases for OpenSearch. The observability plugin enables powerful trace analytics amongst other things. Data Prepper closes the gap between OpenTelemetry-instrumented applications and OpenSearch by providing the required field mappings.
+
+The first part of the session provides a general overview of Data Prepper. We will discuss some of Data Prepper’s key offerings to help you ingest observability data into OpenSearch.
+
+In the second part, a productive use case within SAP will show how OpenTelemetry and OpenSearch come together. This is achieved by a managed Data Prepper component for ingestion and several predefined dashboards for analysis.
+
+We will show the working solution from SAP Cloud Logging and explain our Data Prepper based architecture and deployment. This will include operational challenges with Data Prepper running on Kubernetes, such as memory configuration and stability. An important aspect is ingestion performance, for which we present our load test setup and learnings.
\ No newline at end of file
diff --git a/_opensearchcon_sessions/2024-europe-implementing-an-open-source-rag-with-opensearch.md b/_opensearchcon_sessions/2024-europe-implementing-an-open-source-rag-with-opensearch.md
new file mode 100644
index 0000000000..006ce88cc3
--- /dev/null
+++ b/_opensearchcon_sessions/2024-europe-implementing-an-open-source-rag-with-opensearch.md
@@ -0,0 +1,50 @@
+---
+primary_presenter: apaponaud
+speaker_talk_title: 'Implementing an open-source RAG with OpenSearch'
+primary_title: 'Implementing an open-source RAG with OpenSearch'
+title: 'OpenSearchCon 2024 Session: Implementing an open-source RAG with OpenSearch'
+
+breadcrumbs:
+ icon: community
+ items:
+ - title: OpenSearchCon
+ url: /events/opensearchcon/index.html
+ - title: 2024
+ url: /events/opensearchcon/2024/europe/index.html
+ - title: Europe
+ url: /events/opensearchcon/2024/europe/index.html
+ - title: Session Summaries
+ url: /events/opensearchcon/2024/europe/sessions/index.html
+
+# The template logic expects the following format: YYYY-MM-DD - h:m(am|pm)-(h:m(am|pm))
+session_time: "time TBD"
+
+# Room of location where the talk will occur.
+session_room: "a room yet to be determined."
+
+# Session topic track.
+session_track: "Search"
+
+# URL permalink for the session.
+permalink: '/events/opensearchcon/2024/europe/sessions/implementing-an-open-source-rag-with-opensearch.html'
+
+# ID of the YouTube video of the session to embed in the page.
+# This is to be added after the conference and after the session recordings
+# are uploaded to YouTube.
+#youtube_video_id: 'SOME_YOUTUBE_VIDEO_ID'
+
+# Conference ID.
+# It is normative to use the format of 'YYYY-location-name', eg. '2023-north-america'.
+conference_id: "2024-europe"
+# Array of short_name values for the Community Members with the conference_speaker persona whom are presenting the session. This includes the primary_speaker indicated above and any other presenters (if any).
+presenters:
+ - apaponaud
+ - pmele
+
+
+---
+The RAG systems, such as Microsoft's Copilot and Google's Bard, are playing an increasingly crucial role in our digital daily lives, used every day by hundreds of millions of users.
+
+As these giants compete for supremacy in the field of artificial intelligence, is there an emerging path towards an open-source RAG system that respects data privacy?
+
+This presentation aims to answer this question by exploring the use of the Langchain library and OpenSearch as vector databases. We will begin with a quick analysis of the foundations of the RAG architecture. Then, we will focus on the implementation, also examining other alternatives to Langchain and OpenSearch. Finally, we will conclude by presenting the operation of a fully open-source and local RAG system within a concrete use case.
\ No newline at end of file
diff --git a/_opensearchcon_sessions/2024-europe-opensearch-in-kubernetes-helm-charts-and-operator.md b/_opensearchcon_sessions/2024-europe-opensearch-in-kubernetes-helm-charts-and-operator.md
new file mode 100644
index 0000000000..5d6f6c5454
--- /dev/null
+++ b/_opensearchcon_sessions/2024-europe-opensearch-in-kubernetes-helm-charts-and-operator.md
@@ -0,0 +1,57 @@
+---
+primary_presenter: arubin
+speaker_name_full: Anton Rubin
+conference_id: '2024-europe'
+speaker_talk_title: 'OpenSearch in Kubernetes: Helm Charts and Operator'
+primary_title: 'OpenSearch in Kubernetes: Helm Charts and Operator'
+title: 'OpenSearchCon 2024 Session: OpenSearch in Kubernetes - Helm Charts and Operator'
+
+breadcrumbs:
+ icon: community
+ items:
+ - title: OpenSearchCon
+ url: /events/opensearchcon/index.html
+ - title: 2024
+ url: /events/opensearchcon/2024/europe/index.html
+ - title: Europe
+ url: /events/opensearchcon/2024/europe/index.html
+ - title: Session Summaries
+ url: /events/opensearchcon/2024/europe/sessions/index.html
+
+# The template logic expects the following format: YYYY-MM-DD - h:m(am|pm)-(h:m(am|pm))
+session_time: "time TBD"
+
+# Room of location where the talk will occur.
+session_room: "a room yet to be determined."
+
+# Session topic track.
+session_track: "Operating OpenSearch"
+
+# URL permalink for the session.
+permalink: '/events/opensearchcon/2024/europe/sessions/opensearch-in-kubernetes-helm-charts-and-operator.html'
+
+# ID of the YouTube video of the session to embed in the page.
+# This is to be added after the conference and after the session recordings
+# are uploaded to YouTube.
+#youtube_video_id: 'SOME_YOUTUBE_VIDEO_ID'
+
+# Conference ID.
+# It is normative to use the format of 'YYYY-location-name', eg. '2023-north-america'.
+
+
+# Array of short_name values for the Community Members with the conference_speaker persona whom are presenting the session. This includes the primary_speaker indicated above and any other presenters (if any).
+presenters:
+ - arubin
+---
+
+Simplified OpenSearch Cluster Deployment on Kubernetes: Navigating Helm Charts and the OpenSearch Operator
+
+In the evolving landscape of cloud computing, the use of OpenSearch Clusters in Kubernetes has become increasingly prevalent. However, navigating this transition can be daunting, often fraught with complexities and challenges. This presentation aims to demystify the process by providing a comprehensive overview and practical demonstration of deploying OpenSearch Cluster to Kubernetes.
+
+The presentation will commence with an exploration of two distinct deployment approaches: the traditional method utilizing helm charts, and the newer approach employing the OpenSearch Operator. Through a step-by-step walkthrough, attendees will gain insights into the nuances of each method, enabling them to make informed decisions based on their specific use cases and requirements.
+
+As security remains a paramount concern in today's digital landscape, special emphasis will be placed on addressing the complexities surrounding security configurations. Attendees will be guided through easy-to-follow examples and configurations for securing OpenSearch Clusters deployed on Kubernetes. The presentation will cover a spectrum of security considerations, empowering users to fortify their deployments against potential threats.
+
+Throughout the presentation, emphasis will be placed on simplicity and accessibility. Complex concepts will be broken down into digestible chunks, ensuring that attendees—regardless of their level of expertise—can follow along and grasp the intricacies of deploying OpenSearch Clusters on Kubernetes. Real-world examples and use cases will be integrated to provide practical context, allowing attendees to envision how they can apply these techniques in their own environments.
+
+By the conclusion of the presentation, attendees will have gained a comprehensive understanding of the deployment process for OpenSearch Clusters on Kubernetes, armed with the knowledge and confidence to embark on their own deployment journeys. Whether they opt for the familiarity of helm charts or the cutting-edge capabilities of the OpenSearch Operator, attendees will be equipped to navigate the complexities of Kubernetes deployment with ease and proficiency.
\ No newline at end of file
diff --git a/_opensearchcon_sessions/2024-europe-search-solutions-with-opensearch-python-and-serverless.md b/_opensearchcon_sessions/2024-europe-search-solutions-with-opensearch-python-and-serverless.md
new file mode 100644
index 0000000000..411bc7a43a
--- /dev/null
+++ b/_opensearchcon_sessions/2024-europe-search-solutions-with-opensearch-python-and-serverless.md
@@ -0,0 +1,57 @@
+---
+primary_presenter: luchoa
+speaker_name_full: "Laysa Uchoa"
+speaker_talk_title: 'Search Solutions with OpenSearch, Python, and Serverless'
+primary_title: 'Search Solutions with OpenSearch, Python, and Serverless'
+title: 'OpenSearchCon 2024 Session: Search Solutions with OpenSearch, Python, and Serverless'
+
+breadcrumbs:
+ icon: community
+ items:
+ - title: OpenSearchCon
+ url: /events/opensearchcon/index.html
+ - title: 2024
+ url: /events/opensearchcon/2024/europe/index.html
+ - title: Europe
+ url: /events/opensearchcon/2024/europe/index.html
+ - title: Session Summaries
+ url: /events/opensearchcon/2024/europe/sessions/index.html
+
+# The template logic expects the following format: YYYY-MM-DD - h:m(am|pm)-(h:m(am|pm))
+session_time: "time TBD"
+
+# Room of location where the talk will occur.
+session_room: "a room yet to be determined."
+
+# Session topic track.
+session_track: "Search"
+
+# URL permalink for the session.
+permalink: '/events/opensearchcon/2024/europe/sessions/search-solutions-with-opensearch-python-and-serverless.html'
+
+# ID of the YouTube video of the session to embed in the page.
+# This is to be added after the conference and after the session recordings
+# are uploaded to YouTube.
+#youtube_video_id: 'SOME_YOUTUBE_VIDEO_ID'
+
+# Conference ID.
+# It is normative to use the format of 'YYYY-location-name', eg. '2023-north-america'.
+conference_id: "2024-europe"
+# Array of short_name values for the Community Members with the conference_speaker persona whom are presenting the session. This includes the primary_speaker indicated above and any other presenters (if any).
+presenters:
+ - luchoa
+ - ybarabash
+
+
+---
+
+Struggling with search capabilities in your production environment? You're not alone. The search function is crucial yet often problematic in real-world applications. OpenSearch, Python, and serverless architecture come together to offer a compelling solution. And yes, we'll dive into Pythonic libraries that make integration with OpenSearch a breeze.
+
+In our session, we are going to cover the following objectives such as:
+- Provide an overview of OpenSearch and its problem-solving capabilities for production search needs.
+- Discuss the most useful features of OpenSearch and demonstrate how they can be effectively used in various scenarios.
+- Introduce Python libraries that work well with OpenSearch.
+- Demonstrate how to combine Python and serverless architecture to power your search engine and use it in production.
+- Offer hands-on examples for crafting efficient queries by using Python libraries.
+
+By the end of this informative session, you'll have an understanding of how OpenSearch, Python, and serverless architecture can collectively resolve the challenges you face with search capabilities in production. Additionally, this talk will empower you with practical knowledge and hands-on examples. Whether you're a developer aiming to improve your application's search capabilities or an architect scouting for scalable, effective solutions, you'll find actionable insights and tools to elevate your approach to search and analytics in a production environment.
\ No newline at end of file
diff --git a/_opensearchcon_sessions/2024-europe-securing-opensearch.md b/_opensearchcon_sessions/2024-europe-securing-opensearch.md
new file mode 100644
index 0000000000..525102cd92
--- /dev/null
+++ b/_opensearchcon_sessions/2024-europe-securing-opensearch.md
@@ -0,0 +1,58 @@
+---
+primary_presenter: nbandener
+speaker_name_full: 'Nils Bandener'
+
+speaker_talk_title: 'Securing OpenSearch: Hints for avoiding common hassles'
+
+# Page level 1 header title.
+primary_title: 'Securing OpenSearch: Hints for avoiding common hassles'
+
+# Page document title displayed in the browser title bar.
+title: 'OpenSearchCon 2024 Session: Securing OpenSearch: Hints for avoiding common hassles'
+
+breadcrumbs:
+ icon: community
+ items:
+ - title: OpenSearchCon
+ url: /events/opensearchcon/index.html
+ - title: 2024
+ url: /events/opensearchcon/2024/index.html
+ - title: North America
+ url: /events/opensearchcon/2024/europe/index.html
+ - title: Session Summaries
+ url: /events/opensearchcon/2024/europe/sessions/index.html
+# Session date / time
+# The template logic expects the following format: YYYY-MM-DD - h:m(am|pm)-(h:m(am|pm))
+session_time: "time TBD"
+
+# Room of location where the talk will occur.
+session_room: "a room yet to be determined."
+
+# Session topic track.
+session_track: "Operating OpenSearch"
+
+# URL permalink for the session.
+permalink: '/events/opensearchcon/2024/europe/sessions/securing-opensearch.html'
+
+# ID of the YouTube video of the session to embed in the page.
+# This is to be added after the conference and after the session recordings
+# are uploaded to YouTube.
+#youtube_video_id: 'SOME_YOUTUBE_VIDEO_ID'
+
+# Conference ID.
+# It is normative to use the format of 'YYYY-location-name', eg. '2023-europe'.
+conference_id: '2024-europe'
+
+# Array of short_name values for the Community Members with the conference_speaker persona whom are presenting the session. This includes the primary_speaker indicated above and any other presenters (if any).
+presenters:
+ - nbandener
+---
+Getting your cluster properly secured is an essential part of moving it into production. If you have only one or two users and are not using OpenSearch Dashboards, it is likely a straightforward task. However with a larger user base - with different authorization levels - things can get more challenging, especially if OpenSearch Dashboards is involved. Integrating OpenSearch into an SSO environment further complicates matters.
+
+This has a number of reasons: First, OpenSearch security offers a number of features to simplify your configuration. But sometimes, these features are not too obvious. Second, there are some configuration choices which can actually make your life more difficult than necessary. And finally, it can be non-obvious to test the configuration and find out about the reasons for issues.
+In our presentation, we will cover:
+
+- Good ways to assign privileges to users
+- Getting a smooth OpenSearch Dashboards experience
+- Things to keep in mind when defining complex authentication configurations, especially involving SSO
+- Strategies to test configuration and diagnose issues
\ No newline at end of file
diff --git a/_opensearchcon_sessions/2024-europe-user-behavior-insights.md b/_opensearchcon_sessions/2024-europe-user-behavior-insights.md
new file mode 100644
index 0000000000..01d5dbf575
--- /dev/null
+++ b/_opensearchcon_sessions/2024-europe-user-behavior-insights.md
@@ -0,0 +1,56 @@
+---
+primary_presenter: eric-pugh
+speaker_name_full: Eric Pugh
+conference_id: '2024-europe'
+speaker_talk_title: 'User Behavior Insights'
+primary_title: 'User Behavior Insights'
+title: 'OpenSearchCon 2024 Session: User Behavior Insights'
+
+breadcrumbs:
+ icon: community
+ items:
+ - title: OpenSearchCon
+ url: /events/opensearchcon/index.html
+ - title: 2024
+ url: /events/opensearchcon/2024/europe/index.html
+ - title: Europe
+ url: /events/opensearchcon/2024/europe/index.html
+ - title: Session Summaries
+ url: /events/opensearchcon/2024/europe/sessions/index.html
+
+# The template logic expects the following format: YYYY-MM-DD - h:m(am|pm)-(h:m(am|pm))
+session_time: "time TBD"
+
+# Room of location where the talk will occur.
+session_room: "a room yet to be determined."
+
+# Session topic track.
+session_track: "Search"
+
+# URL permalink for the session.
+permalink: '/events/opensearchcon/2024/europe/sessions/user-behavior-insights.html'
+
+# ID of the YouTube video of the session to embed in the page.
+# This is to be added after the conference and after the session recordings
+# are uploaded to YouTube.
+#youtube_video_id: 'SOME_YOUTUBE_VIDEO_ID'
+
+# Conference ID.
+# It is normative to use the format of 'YYYY-location-name', eg. '2023-north-america'.
+conference_id: "2024-europe"
+
+# Array of short_name values for the Community Members with the conference_speaker persona whom are presenting the session. This includes the primary_speaker indicated above and any other presenters (if any).
+presenters:
+ - epugh
+ - macrakis
+---
+Every search professional needs data about users' behavior. Data is fundamental for analyzing user behavior and improving search relevance, both with manual tuning and with machine learning. User Behavior Insights system provides a standard way to do just that.
+Business product managers, UX designers, and relevance engineers need data to understand their users: What do they search for? What do they click on? What do they act on or buy? How do they use facets and filters? How do they refine their queries within a session? Engineers need data to improve search relevance and effectiveness, both manually and using AI/ML.
+
+But until now, collecting user behavior data has been haphazard. Proprietary SaaS search systems collect data but don't share it with their customers. Open-source systems simply don't offer data collection mechanisms. Third-party analytics systems are designed primarily to track page-to-page flow, and not the flow of search results through the system -- and often make it difficult to extract the raw granular data needed for model training. Consequently many search teams develop and maintain their own ad hoc data collection systems and analysis tools.
+
+Our open-source User Behavior Insights (UBI) system provides a client-side library for instrumenting web pages, a server-side library for collecting data, and analytical tools for understanding it. Critically, it defines a standard schema for behavior data so that the community can contribute additional analytical tools. We have also demonstrated its integration with personalization software.
+
+With the emergence of even more ways of generating and ranking search results -- neural dense search, neural sparse search, model fine-tuning, hybrid search, RAG. Choosing the best mix of approaches for your search application becomes even more critical.
+
+UBI is a call to action to the Search Relevance community to make it simpler to seamlessly track, in an ethical and safe manner, the steps of a user’s search journey in order to build the experiences that the future requires.
\ No newline at end of file
diff --git a/_partners/infino.md b/_partners/infino.md
new file mode 100644
index 0000000000..19edc9ef61
--- /dev/null
+++ b/_partners/infino.md
@@ -0,0 +1,26 @@
+---
+name: Infino
+name_long: 'Infino AI'
+logo: '/assets/media/partners/infino.png'
+link: 'https://infino.ai'
+logo_large: '/assets/media/partners/infino/infino_logo.png'
+description: 'Infino offers a schemaless, serverless managed OpenSearch service. Founded by former AWS OpenSearch engineers, we have replaced Lucene with a next-gen proprietary engine optimized for Observability use cases and internal developer platforms.
+
+We offer everything you have come to expect from OpenSearch except we are cheaper, faster, and with more observability features. Store logs, metrics, traces, code, tickets, etc. in one index. Query all your data at once via languages you know and love: Natural language, Query DSL, PromQL, SQL, PPL, etc. No snapshots, no mapping explosions, no astronomical bills, no slow aggregations, no cluster management, no minimum OCUs.
+
+Save money, save time, and keep your commitments to your customers.'
+business_type: ISV
+region: 'North America, South America, Europe, Middle East, Africa, Asia Pacific, Australia'
+contact: 'tech@infino.ai'
+opensearch_tech: 'Observability'
+industries: 'Software and Technology'
+main_office_location: |
+ Infino AI Inc.
+ 19266 Coastal Hwy
+ Unit 4-250
+ Rehoboth Beach, DE 19971
+products:
+ - url: 'https://infino.ai'
+ name: 'Infino AI'
+ description: 'Serverless, Schemaless OpenSearch for Observability'
+---
diff --git a/_partners/xoriant.md b/_partners/xoriant.md
new file mode 100644
index 0000000000..f6d2c74e09
--- /dev/null
+++ b/_partners/xoriant.md
@@ -0,0 +1,64 @@
+---
+# Partner name used on the partners collection page (/partners).
+name: Xoriant
+
+# name_long is used on the extended partner details page.
+name_long: 'Xoriant'
+
+# The partner logo is used on the partners collection page (/partners).
+# upload your logo to the following directory - must be square
+logo: '/assets/media/partners/xoriant.png'
+
+# URL to the partner's website.
+link: 'https://www.xoriant.com'
+
+# logo_large is used on the extended partner details page.
+# It is normative to upload all extended partner page images to a subdirectory of /assets/media/partners/ with the name of the partner as the directory name.
+# For example given a partner named "SampleCompany" the logo_large image would be uploaded to /assets/media/partners/samplecompany/logo_large.png
+logo_large: '/assets/media/partners/xoriant/xoriant.png'
+
+# Large image displayed in the top right of the extended partner details page.
+# product_image: '/assets/media/partners/xoriant/xoriant.png'
+# Partner company description used on the extended partner details page.
+description: Xoriant is a global digital engineering services company, enabling innovation & accelerating time to market for clients by building digital products and platforms. We are driven by our product engineering DNA, culture of innovation, and technology capabilities in Cloud, Security, Data & AI.
+
+
+# Comma delimited list of business types used on the extended partner details page in the side panel.
+business_type: OpenSearch Services
+
+# Comma delimited list of geographic regions used on the extended partner details page in the side panel.
+region: North America, Europe, Asia
+
+# Comma delimited list of one or more of email addresses, phone numbers, and web URLs that can be used to contat the partner.
+contact: info@xoriant.com
+
+# Comma delimited list of one or more feature areas of the OpenSearch platform that the partner specializes in.
+opensearch_tech: Search, Analytics, Observability, Migration
+
+# Comma delimited list of one or more industries that the partner specializes in serving.
+industries: Manufacturing and Automotive, Supply Chain, Consumer Services, Education, Energy and Utilities, Financial Services, Healthcare, Media and Entertainment, Public sector, Retail and e-commerce, Software and Technology
+
+# If the partner only has one office location then use the main_office_location key
+# otherwise use the multiple_office_locations key.
+# In the template rendering multiple_office_locations takes precedent,
+# and if both are used only the multiple_office_locations data will be rendered
+# in the template omitting the main_office_location data.
+main_office_location: |-
+ 1248 Reamwood Avenue
+ Sunnyvale, CA 94089
+ +1 408 743 4400
+
+# Collection of social links that the partner wishes to promote on their extended partner details page. Supported types are 'twitter', 'linkedin', 'facebook', and 'github'.
+social_links:
+ - url: 'https://twitter.com/xoriant'
+ icon: 'twitter'
+ - url: 'https://www.linkedin.com/company/xoriant'
+ icon: 'linkedin'
+ - url: 'https://facebook.com/Xoriant'
+ icon: 'facebook'
+
+
+# Collection of products that the partner wishes to promote on their extended partner details page. Each product should have a url, name, and description.
+# The product listing is rendered below the partner description on the extended partner details page and above the resources.
+
+---
diff --git a/_posts/2024-04-02-2.13-is-ready-for-download.md b/_posts/2024-04-02-2.13-is-ready-for-download.md
new file mode 100644
index 0000000000..2501ad1140
--- /dev/null
+++ b/_posts/2024-04-02-2.13-is-ready-for-download.md
@@ -0,0 +1,47 @@
+---
+layout: post
+title: "OpenSearch 2.13 is ready for download!"
+authors:
+ - jamesmcintyre
+date: 2024-04-02 14:05 -0700
+categories:
+ - releases
+meta_keywords: opensearch spark, opensearch agent, opensearch guardrails, opensearch memory, opensearch quantize vector, OpenSearch FAISS, OpenSearch 2.13, opensearch OpenAI, opensearch cohere, opensearch bedrock, opensearch assistant toolkit
+meta_description: OpenSearch 2.13 arrives with new machine learning tools to help you build AI-powered applications, along with upgrades that make it easier to access and analyze operational data and new ways to enhance the resiliency of OpenSearch clusters.
+---
+OpenSearch 2.13 is live and available for [download](https://opensearch.org/downloads.html)! The latest version of OpenSearch arrives with a range of machine learning (ML) tools to help you build AI-powered applications, along with upgrades that make it easier to access and analyze your operational data and new ways to enhance the resiliency of your OpenSearch clusters. To explore the release for yourself, visit [OpenSearch Playground](https://playground.opensearch.org/app/home#/). For a fuller view of what’s new, check out the [release notes](https://github.com/opensearch-project/opensearch-build/blob/main/release-notes/opensearch-release-notes-2.13.0.md).
+
+### Automate configurations for AI-powered search applications
+Introduced as experimental in the 2.12 release, the [flow framework](https://opensearch.org/docs/latest/automating-configurations/index/) is now generally available and ready for production. You can use this functionality to automate the configuration of search and ingest pipeline resources required by [advanced search features](https://opensearch.org/docs/latest/search-plugins/) like semantic, multimodal, and conversational search. This adds to existing capabilities for automating ml-commons resource setup, allowing you to package OpenSearch AI solutions into portable [templates](https://opensearch.org/docs/latest/automating-configurations/workflow-templates/). Additionally, we’ve added predefined templates to automate setup for models that are integrated through our [connectors](https://opensearch.org/docs/latest/ml-commons-plugin/remote-models/connectors/#supported-connectors) to APIs like OpenAI, Amazon Bedrock, and Cohere. We’ve also included templates to automate a variety of configurations for semantic, neural sparse, hybrid, and multimodal search. These templates simplify the multi-step configuration process by prescribing automation workflows that can be executed through a single API call using a higher-level declarative interface.
+
+### Build AI-powered workloads with updated connectors
+This release includes enhancements to OpenSearch’s AI [connectors](https://opensearch.org/docs/latest/ml-commons-plugin/remote-models/index/), which let you integrate OpenSearch with AI/ML services like OpenAI, Cohere, and Amazon SageMaker to build AI-powered workloads like semantic search. We’ve added new settings to allow users to configure timeouts and automatically deploy models, making it easier and more convenient to manage your AI integrations.
+
+### Reduce memory footprint for FAISS engine indexes
+With the 2.13 release, you’re now able to index [quantized vectors](https://opensearch.org/docs/latest/search-plugins/knn/knn-vector-quantization/) with FAISS-engine-based k-NN indexes. Instead of storing vectors that require 4 bytes per dimension, you can compress the dimensions down to 2 bytes (half-precision floating-point). This enables builders to reduce the index footprint of their k-NN indexes, offering the potential to reduce memory footprint by as much as 50 percent with minimal impact to accuracy and latency. Previously, vector quantization was only supported on Lucene-based k-NN indexes; now, you can also realize these benefits when using high-performance and scalable FAISS engine indexes.
+
+### Build user experiences powered by generative AI
+The [OpenSearch Assistant Toolkit](https://opensearch.org/docs/latest/ml-commons-plugin/opensearch-assistant/) is now generally available after being introduced as an experimental feature in OpenSearch 2.12. This toolkit equips developers to build interactive, AI-powered assistant experiences in OpenSearch that let users query their operational and security log data using natural language. When paired with a large language model (LLM), these AI assistants let users apply generative AI to identify operational issues quickly, without needing to be familiar with the OpenSearch Piped Processing Language (PPL) or their data schema and fields. For new or less experienced team members, this eliminates the hurdle of learning a new query language, while more experienced team members can save time by eliminating the need to look up the data schema when building queries. Instead, users can simply ask a question about their data, such as “How many 503 errors occurred in the payment service in the last hour?”, and OpenSearch automatically generates and runs the corresponding PPL query.
+
+### Add guardrails for LLM output
+OpenSearch provides the ability to integrate with LLMs to power generative AI use cases. LLMs can potentially generate harmful content, so for this release, the OpenSearch [agent framework](https://opensearch.org/docs/latest/ml-commons-plugin/agents-tools/index/) adds support for [user-defined regex rules](https://opensearch.org/docs/latest/ml-commons-plugin/remote-models/guardrails/) or word lists to filter inappropriate text generation that could be produced by integrated LLMs.
+
+### Apply aggregations to hybrid search results
+[Hybrid search](https://opensearch.org/docs/latest/search-plugins/hybrid-search/) combines results from lexical and neural search, providing more relevant results than either one separately. OpenSearch now offers the ability to [post-filter](https://opensearch.org/docs/latest/search-plugins/hybrid-search/#combining-hybrid-search-and-aggregations) the combined results and to apply aggregations to them to support use cases such as faceting.
+
+### Query and manage external data sources more efficiently
+OpenSearch community members looking to optimize costs can find themselves storing infrequently queried data outside of OpenSearch in object stores. In the 2.9 release, we introduced data sources, which allow you to create a new Apache Spark data source type to directly query object stores. For those who wanted to [increase query performance](https://opensearch.org/docs/latest/dashboards/management/accelerate-external-data/), we released skipping indexes (in the 2.9 release) to speed up direct queries as well as materialized views and covering indexes (both in the 2.11 release) to ingest data directly into OpenSearch indexes. In the 2.13 release, we’ve added a new skipping index type, [Bloom filter](https://opensearch.org/docs/latest/install-and-configure/configuring-opensearch/index-settings/), which is more efficient for data types like IP addresses and hostnames that have many different values that can be stored. In addition, we’ve made improvements to the [data sources experience](https://opensearch.org/docs/latest/dashboards/management/multi-data-sources/), where community members can now manage tables and accelerations visually instead of using SQL statements in [Query Workbench](https://opensearch.org/docs/latest/dashboards/query-workbench/). In upcoming releases, we will improve the querying experience as we merge observability logs functionality into [Discover](https://opensearch.org/docs/latest/dashboards/discover/index-discover/).
+
+Contributors to this feature are eager for community feedback. Learn more and share your input in [opensearch-spark](https://github.com/opensearch-project/opensearch-spark), [sql-plugin](https://github.com/opensearch-project/sql/tree/main/plugin), or [opensearch-dashboards](https://github.com/opensearch-project/OpenSearch-Dashboards).
+
+### Support resiliency with I/O-based admission control
+OpenSearch incorporates features like [search backpressure](https://opensearch.org/docs/latest/tuning-your-cluster/availability-and-recovery/search-backpressure/) and [shard-based indexing](https://opensearch.org/docs/latest/tuning-your-cluster/availability-and-recovery/shard-indexing-backpressure/) to help prevent a cluster from becoming overwhelmed by incoming requests. In addition to these reactive approaches to supporting cluster resiliency, OpenSearch 2.13 adds a proactive mechanism to protect a cluster from spikes or increases in capacity. With the addition of [I/O-based admission control](https://opensearch.org/docs/latest/api-reference/nodes-apis/nodes-stats), if a cluster’s I/O usage breaches a defined threshold, OpenSearch will begin rejecting requests until I/O utilization falls below the threshold. This adds another layer of resiliency to the cluster, separate from JVM- and CPU-based admission control.
+
+### Scale alerting across clusters
+OpenSearch community members who have large amounts of data may choose to store that data across clusters and nodes to meet requirements for scaling, compliance, or disaster recovery. Community members who store data across clusters can find it frustrating that they have to manage alerts for each cluster. In 2.13, we’ve introduced new cross-cluster monitors in the Alerting plugin. Cross-cluster monitors leverage OpenSearch’s cross-cluster search to execute alerting queries on remote clusters, making it easier to centrally manage your alerting infrastructure. If you want to scale alerting independently of indexing and querying, you can now set up a purpose-based alerting cluster that manages all alerting tasks. For more information on cross-cluster monitors, please review the [alerting documentation](https://opensearch.org/docs/latest/observing-your-data/alerting/index/), or create a [GitHub issue](https://github.com/opensearch-project/alerting) if you would like to propose additional functionality.
+
+### Get started with OpenSearch 2.13
+The latest version of OpenSearch is available for [download here](https://opensearch.org/downloads.html) in a range of distributions. You can find out more about these capabilities and many other new features in the [release notes](https://github.com/opensearch-project/opensearch-build/blob/main/release-notes/opensearch-release-notes-2.13.0.md), [documentation release notes](https://github.com/opensearch-project/documentation-website/blob/main/release-notes/opensearch-documentation-release-notes-2.13.0.md/), and [documentation](https://opensearch.org/docs/latest/), and [OpenSearch Playground](https://playground.opensearch.org/app/home#/) is kept current with the latest version so that you can explore the new OpenSearch Dashboards visualization tools. Please feel free to share your feedback on this release on our [community forum](https://forum.opensearch.org/)!
+
+### _OpenSearchCon Europe is coming soon!_
+_The OpenSearch Project is excited to host our first-ever [user conference in Europe](https://opensearch.org/events/opensearchcon/2024/europe/index.html) on May 6 and 7 in Berlin. You’re invited to join us as community members from across the region come together for two days of learning and community building. Organizers have received an overwhelming response to the call for presentations, and we’re looking forward to sharing the conference program soon. [Go here to reserve your seat](https://tickets.plainschwarz.com/opensearchconeu/) and take advantage of early-bird pricing through April 8._
\ No newline at end of file
diff --git a/_posts/2024-04-02-UsingDocumentationForUsabilityStudies.md b/_posts/2024-04-02-UsingDocumentationForUsabilityStudies.md
index 9daccad519..dd8a1ffc26 100644
--- a/_posts/2024-04-02-UsingDocumentationForUsabilityStudies.md
+++ b/_posts/2024-04-02-UsingDocumentationForUsabilityStudies.md
@@ -98,7 +98,9 @@ The following image shows instructions on how to use the toolkit.
Additionally, the following video walks you through the toolkit.
-[Embed https://youtu.be/06o1yActr7M]
+
+{% include youtube-player.html id="06o1yActr7M?si" %}
+
## References
diff --git a/_redesign_heros/1.md b/_redesign_heros/1.md
index e1357b12eb..10d04cbb03 100644
--- a/_redesign_heros/1.md
+++ b/_redesign_heros/1.md
@@ -32,7 +32,7 @@ images:
diff --git a/_versions/2024-04-02-opensearch-2.13.0.markdown b/_versions/2024-04-02-opensearch-2.13.0.markdown
new file mode 100644
index 0000000000..eb3dd95991
--- /dev/null
+++ b/_versions/2024-04-02-opensearch-2.13.0.markdown
@@ -0,0 +1,87 @@
+---
+date: "2024-04-02"
+product: opensearch
+version: '2.13.0'
+release_notes: https://github.com/opensearch-project/opensearch-build/blob/main/release-notes/opensearch-release-notes-2.13.0.md
+version_sort: 2.13.0-ga
+components:
+ - role: daemon
+ artifact: opensearch
+ version: 2.13.0
+ - role: ui
+ artifact: opensearch-dashboards
+ version: 2.13.0
+ - role: command-line-tools
+ artifact: opensearch-cli
+ version: 1.2.0
+ - role: ingest
+ artifact: data-prepper
+ version: data-prepper-2.7.0
+ platform_order:
+ - docker
+ - linux
+ - role: ingest
+ artifact: logstash-oss-with-opensearch-output-plugin
+ version: 8.9.0
+ - role: minimal-artifacts
+ artifact: opensearch-min
+ version: 2.13.0
+ - role: minimal-artifacts
+ artifact: opensearch-dashboards-min
+ version: 2.13.0
+ - role: drivers
+ artifact: opensearch-sql-odbc
+ version: 1.5.0.0
+ - role: drivers
+ artifact: opensearch-sql-jdbc
+ version: 1.4.0.1
+sections:
+ docker-compose:
+ explanation: "downloads/opensearch-docker.markdown"
+ opensearch:
+ role: daemon
+ artifacts:
+ opensearch:
+ explanation: "downloads/opensearch-daemon.markdown"
+ opensearch-dashboards:
+ role: ui
+ artifacts:
+ opensearch-dashboards:
+ explanation: "downloads/opensearch-ui.markdown"
+ data-ingest:
+ explanation: "downloads/opensearch-data-ingest.markdown"
+ role: ingest
+ artifacts:
+ data-prepper:
+ explanation: "downloads/data-prepper.html"
+ logstash-oss-with-opensearch-output-plugin:
+ explanation: "downloads/logstash-oss-with-opensearch-output-plugin.markdown"
+ command-line-tools:
+ role: command-line-tools
+ artifacts:
+ opensearch-cli:
+ explanation: "downloads/opensearch-cli.html"
+ drivers:
+ explanation: "downloads/drivers.markdown"
+ role: drivers
+ artifacts:
+ opensearch-sql-odbc:
+ explanation: "downloads/odbc.markdown"
+ opensearch-sql-jdbc:
+ explanation: "downloads/jdbc.markdown"
+ minimal:
+ explanation: "downloads/minimal-distributions.markdown"
+ role: minimal-artifacts
+ artifacts:
+ opensearch-min:
+ explanation: "downloads/opensearch-daemon-min.markdown"
+ opensearch-dashboards-min:
+ explanation: "downloads/opensearch-ui-min.markdown"
+pretty:
+ artifacts:
+ opensearch: ''
+ opensearch-min: 'OpenSearch Minimum'
+ opensearch-dashboards: ''
+ opensearch-dashboards-min: 'OpenSearch Dashboards Minimum'
+---
+OpenSearch is open source software that uses the Apache License version 2 (ALv2). ALv2 grants you well-understood usage rights; you can use, modify, extend, embed, monetize, resell, and offer OpenSearch as part of your products and services. The source for the entire project is available on [GitHub](https://github.com/opensearch-project/) and you're welcome to build from source for customized deployments. Downloadable artifacts for OpenSearch and OpenSearch Dashboards include plugins and tools, ready for you to use with minimal configuration.
diff --git a/assets/media/community/members/apaponaud.jpg b/assets/media/community/members/apaponaud.jpg
new file mode 100644
index 0000000000..c52778af49
Binary files /dev/null and b/assets/media/community/members/apaponaud.jpg differ
diff --git a/assets/media/community/members/nbandener.jpg b/assets/media/community/members/nbandener.jpg
new file mode 100644
index 0000000000..ee7215c3bb
Binary files /dev/null and b/assets/media/community/members/nbandener.jpg differ
diff --git a/assets/media/community/members/pmele.jpg b/assets/media/community/members/pmele.jpg
new file mode 100644
index 0000000000..8a8fb28120
Binary files /dev/null and b/assets/media/community/members/pmele.jpg differ
diff --git a/assets/media/partners/infino.png b/assets/media/partners/infino.png
new file mode 100644
index 0000000000..cb9a0203b1
Binary files /dev/null and b/assets/media/partners/infino.png differ
diff --git a/assets/media/partners/infino/infino_logo.png b/assets/media/partners/infino/infino_logo.png
new file mode 100644
index 0000000000..6cf1286a57
Binary files /dev/null and b/assets/media/partners/infino/infino_logo.png differ
diff --git a/assets/media/partners/xoriant.png b/assets/media/partners/xoriant.png
new file mode 100644
index 0000000000..058a44d5cc
Binary files /dev/null and b/assets/media/partners/xoriant.png differ
diff --git a/assets/media/partners/xoriant/xoriant.png b/assets/media/partners/xoriant/xoriant.png
new file mode 100644
index 0000000000..058a44d5cc
Binary files /dev/null and b/assets/media/partners/xoriant/xoriant.png differ
diff --git a/events/opensearchcon/2024/europe/index.md b/events/opensearchcon/2024/europe/index.md
index fb237815f3..adc756a5f6 100644
--- a/events/opensearchcon/2024/europe/index.md
+++ b/events/opensearchcon/2024/europe/index.md
@@ -60,9 +60,10 @@ Join us in Berlin on May 6 & 7 for OpenSearchCon Europe 2024!
The OpenSearch community continues to expand, always welcoming new individuals, organizations, and partners into the fold, and OpenSearchCon is where the community comes together.
-join us May 6 and 7 at Cafe Moskau in Berlin for OpenSearchCon Europe 2024. You can reserve your seat here: [Register Now](https://tickets.plainschwarz.com/opensearchconeu/).
+Join us May 6 and 7 at Cafe Moskau in Berlin for OpenSearchCon Europe 2024. You can reserve your seat here: [Register Now](https://tickets.plainschwarz.com/opensearchconeu/).
-As always, what makes OpenSearchCon a success are the compelling stories and educational insights shared by our community. The [Call for Presentations](https://pretalx.com/opensearchcon-europe-24/cfp) (CfP) for OpenSearchCon Europe is now open—go [here](https://pretalx.com/opensearchcon-europe-24/cfp) to learn more and propose your ideas.
+As always, what makes OpenSearchCon a success are the compelling stories and educational insights shared by our community. The Call for Presentations (CfP) for OpenSearchCon Europe is now closed.
Read more in the [announcement post](https://opensearch.org/blog/announcing-opensearchcon-europe-2024/)
+
diff --git a/events/opensearchcon/2024/europe/sessions/index.md b/events/opensearchcon/2024/europe/sessions/index.md
index 918a886b08..204d97bceb 100644
--- a/events/opensearchcon/2024/europe/sessions/index.md
+++ b/events/opensearchcon/2024/europe/sessions/index.md
@@ -17,5 +17,3 @@ conference_id: 2024-europe
permalink: /events/opensearchcon/2024/europe/sessions/index.html
---
-The [Call for Presentations](https://pretalx.com/opensearchcon-europe-24/cfp) (CfP) for OpenSearchCon Europe is now open—go [here](https://pretalx.com/opensearchcon-europe-24/cfp) to learn more and propose your ideas. We’ll close the CfP on March 25, so be sure to submit your proposals by this date.
-