Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate from ElasticSearch 6.x to OpenSearch 1.2.x #2813

Closed
tas50 opened this issue Sep 17, 2021 · 3 comments
Closed

Migrate from ElasticSearch 6.x to OpenSearch 1.2.x #2813

tas50 opened this issue Sep 17, 2021 · 3 comments
Assignees
@vinay-satish
Labels
Aspect: Packaging Distribution of the projects 'compiled' artifacts. Aspect: Security Can an unwanted third party affect the stability or look at privileged information? Component: upgrade Epic

Comments

@tas50
Copy link
Contributor

tas50 commented Sep 17, 2021 •
edited by PrajaktaPurohit
Loading

User Story

As a Chef Infra Server admin, I require the latest version of dependencies
So that I can keep my Chef infrastructure and business secure

Acceptance Criteria

  • New installs run with external Opensearch work
  • Upgrading external elasticsearch to Opensearch is tested and documented
  • New internal opensearch installs work <- basic omnibus work
  • Upgrade internal opensearch installs work <- some more omnibus work around automating the manual steps in moving from es to opensearch
  • Test with standalone-fresh-install | standalone-upgrade | tiered fresh install and upgrade | external opensearch
  • New installs run on Opensearch 1.x
  • Existing Elasticsearch 6 installs are seamlessly migrated to Opensearch

Implementation Details

  • This work needs to be done in Q4 as the release of Elasticsearch 8 means 6.x stops receiving security updates.

Definition of Done

  • End to end testing is in place to validate the upgrade
  • Coordination has taken place with the Automate team to ensure integrated Chef Infra Server works with Opensearch in Automate
  • Release notes explain changes that may impact Automate admins such as URL/Path changes that may impact monitoring

Related automate issue: chef/automate#5744
@tas50 tas50 added the Status: Untriaged An issue that has yet to be triaged. label Sep 17, 2021
This was referenced Sep 17, 2021
Open
Closed
Closed
@tas50 tas50 added this to the Q4 2021 milestone Sep 20, 2021
@tas50 tas50 added Aspect: Packaging Distribution of the projects 'compiled' artifacts. Component: upgrade Aspect: Security Can an unwanted third party affect the stability or look at privileged information? and removed Status: Untriaged An issue that has yet to be triaged. labels Sep 20, 2021
@tas50 tas50 removed this from the Q4 2021 milestone Oct 6, 2021
@tas50 tas50 mentioned this issue Oct 11, 2021
Merged
5 tasks
@tas50 tas50 added the Epic label Oct 18, 2021
@vinay-satish vinay-satish self-assigned this Nov 19, 2021
@vinay-satish
Copy link
Contributor

Reference PR - #2933

@btm
Copy link
Contributor

btm commented Dec 16, 2021

https://opensearch.org/docs/latest/upgrade-to/upgrade-to/
image

@vinay-satish vinay-satish changed the title Migrate from ElasticSearch 6.x to OpenSearch 1.x Migrate from ElasticSearch 6.x to OpenSearch 1.2.x Dec 22, 2021
@PrajaktaPurohit
Copy link
Contributor

Currently in progress. https://chefio.atlassian.net/browse/INFS-29

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vinay-satish vinay-satish

Labels
Aspect: Packaging Distribution of the projects 'compiled' artifacts. Aspect: Security Can an unwanted third party affect the stability or look at privileged information? Component: upgrade Epic
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@btm @tas50 @PrajaktaPurohit @vinay-satish