Skip to content

feat: add migrate project from Renku V1 to Renku 2.0 #3527

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

Merged
merged 23 commits into from
Mar 17, 2025

Conversation

andre-code
Copy link
Contributor

@andre-code andre-code commented Feb 10, 2025

This PR introduces the ability for project owners to migrate their projects from Renku v1 to Renku 2.0.

Acceptance Criteria

  • The migration alert is shown only to project owners and for public projects.

  • The migration process will transfer:

    1. Code repository
    2. Container image (pinned images or the last built image)
    3. Resource class (based on project specifications or a default resource class if available)
    4. Project description
    5. Project keywords
  • The migration process will display what will not be migrated.

  • The project is migrated, and a new launcher is added in Renku 2.0.

  • Sessions should work if they worked in Renku v1 and used a public image.

  • If a project requires activation in Renku v1 for a session to work, migration is blocked until the project is updated.

  • Users can navigate from the original project in Renku v1 to the corresponding migrated project in Renku 2.0.

Migrating a project...

migrate metadata and launcher

Launching a session migrated project:
launch migrated session

/deploy renku=release-0.66.0 renku-data-services=andrea/add-projects-migrated renku-notebooks=master

@RenkuBot
Copy link
Contributor

You can access the deployment of this PR at https://renku-ci-ui-3527.dev.renku.ch

@andre-code andre-code force-pushed the andrea/migration-to-20 branch from 07d2242 to 38bf53f Compare February 19, 2025 11:07
@andre-code andre-code force-pushed the andrea/migration-to-20 branch from 38bf53f to 92943a0 Compare February 20, 2025 15:50
@andre-code andre-code temporarily deployed to renku-ci-ui-3527 March 3, 2025 16:41 — with GitHub Actions Inactive
@andre-code andre-code force-pushed the andrea/migration-to-20 branch from 2a3bf74 to 7407a57 Compare March 3, 2025 19:44
@andre-code andre-code temporarily deployed to renku-ci-ui-3527 March 3, 2025 19:44 — with GitHub Actions Inactive
… dev access, refactor migration to use useGetDockerImage in the modal
… to only display error messages when the data is fully loaded.
- add access to migrate projects to OWNERS and ADMINS
- use ExternalLinks component for Learn more buttons and links
- remove unnecessary typing
- fix copy in Error Alert
- use params to get url project URl
Copy link
Member

@leafty leafty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@andre-code andre-code merged commit 9729bc5 into main Mar 17, 2025
21 checks passed
@andre-code andre-code deleted the andrea/migration-to-20 branch March 17, 2025 15:04
@RenkuBot
Copy link
Contributor

Tearing down the temporary RenkuLab deplyoment for this PR.

leafty pushed a commit that referenced this pull request Apr 22, 2025
- Show migration alert only to project owners and for public projects  
- Migrate code repository, container image, resource class, description, and keywords  
- Indicate non-migrated elements during the process  
- Ensure sessions work if they used a public image in Renku v1  
- Block migration if session activation is required in Renku v1  
- Allow navigation from Renku v1 projects to their migrated versions in Renku 2.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants