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

Start migration of retorch-orchestration tool #58

Open
augustocristian opened this issue Nov 13, 2024 · 9 comments · May be fixed by #65
Open

Start migration of retorch-orchestration tool #58

augustocristian opened this issue Nov 13, 2024 · 9 comments · May be fixed by #65
Assignees
@augustocristian

Comments

@augustocristian
Copy link
Contributor

I've reviewed the current status of the RETORCH orchestration tool, and I believe it’s almost ready to migrate the first version to this repository and make it publicly available. I’m beginning to outline the next steps we should take (tentative list):

  1. Create the module structure and organize different packages.
  2. Migrate the entity and phase packages (grouping, deployment, resource identification, scheduling), along with DTOs and base configuration files.
  3. Migrate the test cases and integrate them with GitHub Actions.
  4. Set up the repository to create the library and make it publicly accessible.
  5. Integrate the tool with the EshopContainer and Fullteaching repositories.

Let’s discuss any changes to these steps and how best to proceed, @javiertuya.
@augustocristian augustocristian self-assigned this Nov 13, 2024
@javiertuya
Copy link
Contributor

@augustocristian @ClaudiodelaRiva I think that a big-bang approach and let the tests for the end is not the best approach. Migration should be incremental, starting by the module with less dependencies (ochestration) as we discussed before, and including everything of it (code, tests, doc and packaging). After migrating everything, publish the release (v2.0.0)

@augustocristian augustocristian mentioned this issue Nov 14, 2024
Merged
@giis-qabot
Copy link
Contributor

@augustocristian This is a reminder about this issue because it has not been updated for 10 days

1 similar comment
@giis-qabot
Copy link
Contributor

@augustocristian This is a reminder about this issue because it has not been updated for 10 days

@javiertuya
Copy link
Contributor

javiertuya commented Dec 12, 2024 •
edited
Loading

@augustocristian @ClaudiodelaRiva Remember, after the orchestration module #59, the next to migrate is the generation of the jenkinsfile, just this, anything about profiles, costs, etc.

@augustocristian
Copy link
Contributor Author

The Generation of Jenkinsfiles is under migration in https://github.com/giis-uniovi/retorch/tree/ft_migrateschedulerorchestrator

@augustocristian augustocristian linked a pull request Dec 13, 2024 that will close this issue
Open
@augustocristian augustocristian linked a pull request Dec 13, 2024 that will close this issue
Migration of the scheduler and orchestrator packages #65
Open
@giis-qabot
Copy link
Contributor

@augustocristian This is a reminder about this issue because it has not been updated for 10 days

1 similar comment
@giis-qabot
Copy link
Contributor

@augustocristian This is a reminder about this issue because it has not been updated for 10 days

@augustocristian augustocristian mentioned this issue Jan 2, 2025
Open
@giis-qabot
Copy link
Contributor

@augustocristian This is a reminder about this issue because it has not been updated for 10 days

1 similar comment
@giis-qabot
Copy link
Contributor

@augustocristian This is a reminder about this issue because it has not been updated for 10 days

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

@augustocristian augustocristian

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Migration of the scheduler and orchestrator packages giis-uniovi/retorch
3 participants
@javiertuya @augustocristian @giis-qabot