Sessions update and folder hierarchy for housekeeping.

Signed-off-by: Nate B <[email protected]>

Author: nateynateynate

_community_members/bburkholder.md

@@ -0,0 +1,66 @@
+---
+#
+# 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: "bburkholder"
+
+# 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: "Bryan Burkholder"
+
+# The path to the community member's photo.
+photo: "/assets/media/community/members/bburkholder.png"
+
+# Used as the level 1 page header text.
+primary_title: 'Bryan Burkholder'
+
+# Used as the document title displayed in the browser title bar.
+title: 'OpenSearch Project Community Member: Bryan Burkholder'
+
+# Community member job title and company where they work.
+job_title_and_company: 'Staff Software Engineer at Slack'
+
+# 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:
+#  - '2024-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-north-america"
+    name: "Search"
+
+# URL for the community member profile.
+permalink: '/community/members/bryan-burkholder.html'
+
+# Array of community member user personas.
+# At this time, only conference_speaker, and author are defined.
+personas:
+  - conference_speaker
+#  - author
+
+# Array of conference IDs that the member is a speaker.
+conference_id:
+  - "2024-north-america"
+
+
+# Optional GitHub username
+#github: githubusername
+
+# Optional LinkedIn username
+#linkedin: linkedinusername
+
+# Optional Twitter username
+#twitter: twitterusername
+
+# Optional Mastodon server url, and username / handle.
+#mastodon:
+#  url: https://mastodon.social/@mastodonusername
+#  name: mastodonusername
+---
+
+Markdown or HTML content providing a user bio, or whatever is desired to describe their involvement in open source technology in general, and specifically how their work relates to the OpenSearch Project.

_community_members/kramasamy.md

@@ -0,0 +1,64 @@
+---
+#
+# 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: "kramasamy"
+
+# 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: "Karthikeyan Ramasamy"
+
+# The path to the community member's photo.
+photo: "/assets/media/community/members/kramasamy.png"
+
+# Used as the level 1 page header text.
+primary_title: 'Karthikeyan Ramasamy'
+
+# Used as the document title displayed in the browser title bar.
+title: 'OpenSearch Project Community Member: Karthikeyan Ramasamy'
+
+# Community member job title and company where they work.
+job_title_and_company: 'Sr Staff Software Engineer at Uber'
+
+# 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-north-america"
+    name: "Search"
+
+# URL for the community member profile.
+permalink: '/community/members/karthikeyan-ramasamy.html'
+
+# Array of community member user personas.
+# At this time, only conference_speaker, and author are defined.
+personas:
+  - conference_speaker
+#  - author
+
+# Array of conference IDs that the member is a speaker.
+conference_id:
+  - "2024-north-america"
+
+
+# Optional GitHub username
+#github: githubusername
+
+# Optional LinkedIn username
+#linkedin: linkedinusername
+
+# Optional Twitter username
+#twitter: twitterusername
+
+# Optional Mastodon server url, and username / handle.
+#mastodon:
+#  url: https://mastodon.social/@mastodonusername
+#  name: mastodonusername
+---

_community_members/milav-shah.md

@@ -0,0 +1,65 @@
+---
+#
+# 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: "milavshah"
+
+# 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: "Milav Shah"
+
+# The path to the community member's photo.
+photo: "/assets/media/community/members/milav-shah.png"
+
+# Used as the level 1 page header text.
+primary_title: 'Milav Shah'
+
+# Used as the document title displayed in the browser title bar.
+title: 'OpenSearch Project Community Member: Milav Shah'
+
+# Community member job title and company where they work.
+job_title_and_company: 'Engineering Leadership at Amazon'
+
+# 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-north-america"
+    name: "Operating OpenSearch"
+
+# URL for the community member profile.
+permalink: '/community/members/milav-shah.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-north-america"
+
+
+# Optional GitHub username
+#github: githubusername
+
+# Optional LinkedIn username
+#linkedin: linkedinusername
+
+# Optional Twitter username
+#twitter: twitterusername
+
+# Optional Mastodon server url, and username / handle.
+#mastodon:
+#  url: https://mastodon.social/@mastodonusername
+#  name: mastodonusername
+---
+

_community_members/rnair.md

@@ -0,0 +1,67 @@
+---
+#
+# 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: "rnair"
+
+# 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: "Rohit Nair"
+
+# The path to the community member's photo.
+photo: "/assets/media/community/members/no-image-available.svg"
+
+# Used as the level 1 page header text.
+primary_title: 'Rohit Nair'
+
+# Used as the document title displayed in the browser title bar.
+title: 'OpenSearch Project Community Member: Rohit Nair'
+
+
+# Community member job title and company where they work.
+job_title_and_company: 'Software Development Engineer'
+
+# 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-north-america"
+    name: "Operating OpenSearch"
+
+# URL for the community member profile.
+permalink: '/community/members/rohit-nair.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-north-america"
+
+
+# Optional GitHub username
+#github: githubusername
+
+# Optional LinkedIn username
+#linkedin: linkedinusername
+
+# Optional Twitter username
+#twitter: twitterusername
+
+# Optional Mastodon server url, and username / handle.
+#mastodon:
+#  url: https://mastodon.social/@mastodonusername
+#  name: mastodonusername
+---
+
+Markdown or HTML content providing a user bio, or whatever is desired to describe their involvement in open source technology in general, and specifically how their work relates to the OpenSearch Project.

_opensearchcon_sessions/2022-north-america-creating-the-opensearch-kubernetes-operator.md _opensearchcon_sessions/2022/north-america/2022-north-america-creating-the-opensearch-kubernetes-operator.md

@@ -1,30 +1,30 @@
----
-primary_presenter: 'jonahkowall'
-speaker_talk_title: '18 Months of Operating OpenSearch at Scale'
-primary_title: '18 Months of Operating OpenSearch at Scale'
-title: 'OpenSearchCon 2023 Session: 18 Months of Operating OpenSearch at Scale'
-breadcrumbs:
-  icon: community
-  items:
-    - title: OpenSearchCon
-      url: /events/opensearchcon/index.html
-    - title: 2023
-      url: /events/opensearchcon/2023/index.html
-    - title: North America
-      url: /events/opensearchcon/2023/north-america/index.html
-    - title: Session Summaries
-      url: /events/opensearchcon/2023/north-america/sessions/index.html
-speaker_twitter: "https://twitter.com/jkowall"
-speaker_github: "https://github.com/jkowall"
-speaker_linkedin: "https://linkedin.com/in/jkowall"
-session_time: "2023-09-28 - 11:30am - 12:10pm"
-session_room: "Ballroom CD"
-session_track: "Operating OpenSearch"
-permalink: '/events/opensearchcon/2023/north-america/sessions/18-months-of-operating-opensearch-at-scale.html'
-youtube_video_id: 'VYL69m82fDY'
-conference_id: '2023-north-america'
-presenters:
-  - jonahkowall
----
-
-Running an OpenSearch cluster in production presents unique challenges. At Aiven, we manage thousands of OpenSearch nodes for numerous customers across multiple clouds and regions. We'll share our experiences, discussing monitoring, resiliency, scaling, optimization, handling upgrades, and enabling customers to navigate releases. We'll also reveal the most adopted service integrations, versions, preferred clouds, and instance sizes. This session provides insights into managing OpenSearch at scale, useful for those running stable systems or looking to expand their OpenSearch usage.
+---
+primary_presenter: 'jonahkowall'
+speaker_talk_title: '18 Months of Operating OpenSearch at Scale'
+primary_title: '18 Months of Operating OpenSearch at Scale'
+title: 'OpenSearchCon 2023 Session: 18 Months of Operating OpenSearch at Scale'
+breadcrumbs:
+  icon: community
+  items:
+    - title: OpenSearchCon
+      url: /events/opensearchcon/index.html
+    - title: 2023
+      url: /events/opensearchcon/2023/index.html
+    - title: North America
+      url: /events/opensearchcon/2023/north-america/index.html
+    - title: Session Summaries
+      url: /events/opensearchcon/2023/north-america/sessions/index.html
+speaker_twitter: "https://twitter.com/jkowall"
+speaker_github: "https://github.com/jkowall"
+speaker_linkedin: "https://linkedin.com/in/jkowall"
+session_time: "2023-09-28 - 11:30am - 12:10pm"
+session_room: "Ballroom CD"
+session_track: "Operating OpenSearch"
+permalink: '/events/opensearchcon/2023/north-america/sessions/18-months-of-operating-opensearch-at-scale.html'
+youtube_video_id: 'VYL69m82fDY'
+conference_id: '2023-north-america'
+presenters:
+  - jonahkowall
+---
+
+Running an OpenSearch cluster in production presents unique challenges. At Aiven, we manage thousands of OpenSearch nodes for numerous customers across multiple clouds and regions. We'll share our experiences, discussing monitoring, resiliency, scaling, optimization, handling upgrades, and enabling customers to navigate releases. We'll also reveal the most adopted service integrations, versions, preferred clouds, and instance sizes. This session provides insights into managing OpenSearch at scale, useful for those running stable systems or looking to expand their OpenSearch usage.

_opensearchcon_sessions/2022-north-america-deploying-opensearch-solutions-on-hybrid-multi-cloud-environments.md _opensearchcon_sessions/2022/north-america/2022-north-america-deploying-opensearch-solutions-on-hybrid-multi-cloud-environments.md

@@ -1,29 +1,29 @@
----
-primary_presenter: 'amistrn'
-speaker_talk_title: '4 Very Different Ways to Migrate Your Data From One Cluster to Another'
-primary_title: '4 Very Different Ways to Migrate Your Data From One Cluster to Another'
-title: 'OpenSearchCon 2023 Session: 4 Different Ways to Migrate Data Between Clusters'
-breadcrumbs:
-  icon: community
-  items:
-    - title: OpenSearchCon
-      url: /events/opensearchcon/index.html
-    - title: 2023
-      url: /events/opensearchcon/2023/index.html
-    - title: North America
-      url: /events/opensearchcon/2023/north-america/index.html
-    - title: Session Summaries
-      url: /events/opensearchcon/2023/north-america/sessions/index.html
-speaker_twitter: "https://twitter.com/amitaistern"
-speaker_github: "https://github.com/AmiStrn"
-session_time: "2023-09-28 - 3:30pm-4:10pm"
-session_room: "Willow"
-session_track: "Operating OpenSearch"
-permalink: '/events/opensearchcon/2023/north-america/sessions/4-very-different-ways-to-migrate-your-data-from-one-cluster-to-another.html'
-youtube_video_id: 'SWjCq0xTN7w'
-conference_id: '2023-north-america'
-presenters:
-  - amistrn
----
-
-Data migration, an often encountered task in managing OpenSearch in production, can be complex when managing data at scale. This talk discusses four diverse methods to migrate data between clusters: Cross Cluster Replication, Snapshot/Restore, Reindexing, and a method known as “The Node Toss”. We explore what happens “under the hood”, weigh the pros and cons of each approach, and suggest when each method should be employed.
+---
+primary_presenter: 'amistrn'
+speaker_talk_title: '4 Very Different Ways to Migrate Your Data From One Cluster to Another'
+primary_title: '4 Very Different Ways to Migrate Your Data From One Cluster to Another'
+title: 'OpenSearchCon 2023 Session: 4 Different Ways to Migrate Data Between Clusters'
+breadcrumbs:
+  icon: community
+  items:
+    - title: OpenSearchCon
+      url: /events/opensearchcon/index.html
+    - title: 2023
+      url: /events/opensearchcon/2023/index.html
+    - title: North America
+      url: /events/opensearchcon/2023/north-america/index.html
+    - title: Session Summaries
+      url: /events/opensearchcon/2023/north-america/sessions/index.html
+speaker_twitter: "https://twitter.com/amitaistern"
+speaker_github: "https://github.com/AmiStrn"
+session_time: "2023-09-28 - 3:30pm-4:10pm"
+session_room: "Willow"
+session_track: "Operating OpenSearch"
+permalink: '/events/opensearchcon/2023/north-america/sessions/4-very-different-ways-to-migrate-your-data-from-one-cluster-to-another.html'
+youtube_video_id: 'SWjCq0xTN7w'
+conference_id: '2023-north-america'
+presenters:
+  - amistrn
+---
+
+Data migration, an often encountered task in managing OpenSearch in production, can be complex when managing data at scale. This talk discusses four diverse methods to migrate data between clusters: Cross Cluster Replication, Snapshot/Restore, Reindexing, and a method known as “The Node Toss”. We explore what happens “under the hood”, weigh the pros and cons of each approach, and suggest when each method should be employed.