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.

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

[release]: OpenSearch Migrations - v0.1.0 - Capture and Replay #4000

Closed
sumobrian opened this issue Sep 12, 2023 · 4 comments
Closed

[release]: OpenSearch Migrations - v0.1.0 - Capture and Replay #4000

sumobrian opened this issue Sep 12, 2023 · 4 comments
Labels

Comments

@sumobrian
Copy link

sumobrian commented Sep 12, 2023

Did you read the on-boarding document

I reviewed this document but not sure if the procedures apply in this the migrations repo is not a plugin.

What is the name of your component?

OpenSearch Migrations

What is the link to your GitHub repo?

https://github.com/opensearch-project/opensearch-migrations

Targeted release date

9/13 - Beta Release for Capture and Replay
9/27 - Beta Release for Historical Fetch with Capture and Replay updates
10/27 - Complete Migration Life Cycle
11/27 - AWS Solutions Library Release

Where should we publish this component?

At present, we release only tarballs and zip files for the migration repo. We would like these to be PGP signed, and for these artifacts to be referenced on this page: https://opensearch.org/downloads.html.

Ideally, there should be a mechanism that allows us to redirect users to the latest version of the tooling, as this tooling will not be tied to a specific OpenSearch release."

What type of artifact(s) will be generated for this component?

tgz and zip of repo.

Have you completed the required reviews including security reviews, UX reviews?

Security Review - Please update status here

Given that this tooling is command line driven no UX review is needed.

Have you on-boarded automated security scanning for the GitHub repo associated with this component?

Yes.

Additional context

We have a migrations release schedule for this week. It is a beta incremental release until we get to our 1.0 release (scheduled for 11/27) and it is not tied to any OpenSearch release. However, there are a few tasks we need to work through for this release:

  1. Putting the artifacts (zip/tgz) from github onto s3. I read through the steps here but noticed many do not apply to a release decoupled from OpenSearch release.
  2. Signing the artifacts - I can do this with pgp signer but need access to the role defined here
  3. Add a new migrations tools section here w/ references to the artifacts created in 1 and 2. https://opensearch.org/downloads.html
@sumobrian sumobrian added untriaged Issues that have not yet been triaged release labels Sep 12, 2023
@gaiksaya gaiksaya removed the untriaged Issues that have not yet been triaged label Sep 12, 2023
@gaiksaya
Copy link
Member

Hi @sumobrian ,

As discussed offline, we would need a week's time to on-board opensearch-migrations to one click release process: https://github.com/opensearch-project/opensearch-build/blob/main/ONBOARDING.md#onboarding-to-universal--1-click-release-process

@bbarani
Copy link
Member

bbarani commented Sep 18, 2023

Closing this as completed.

@bbarani bbarani closed this as completed Sep 18, 2023
@gaiksaya
Copy link
Member

Hi @bbarani We still to on-board this component to 1-click release process. Will we be using another issue for that?

@bbarani
Copy link
Member

bbarani commented Sep 18, 2023

Lets use another issue to track the release automation as this issue is specific to v0.1.0 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants