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

move of osparc.io: Check Registry #1864

Open
mrnicegyu11 opened this issue Mar 17, 2025 · 2 comments
Open

move of osparc.io: Check Registry #1864

mrnicegyu11 opened this issue Mar 17, 2025 · 2 comments
Assignees
Labels
a:pipeline-services High Priority a totally crucial bug/feature to be fixed asap Maintenance Maintenance for CI
Milestone

Comments

@mrnicegyu11
Copy link
Member

@GitHK says it is possible that certain osparc dynamic services don't exist anywhere outside of the registry of osparc.io.

Please go through the registry and check that all services exist in registry-speag as well. Adjust the syncer accordingly.

A pruning of dyn-services, i.e. removal of those that are not used in any project, would be desireable.

@mrnicegyu11 mrnicegyu11 added a:pipeline-services High Priority a totally crucial bug/feature to be fixed asap Maintenance Maintenance for CI labels Mar 17, 2025
@mrnicegyu11 mrnicegyu11 added this to the The Awakening milestone Mar 17, 2025
@mrnicegyu11 mrnicegyu11 changed the title Move of osparc.io: Check Registry move of osparc.io: Check Registry Mar 17, 2025
@GitHK
Copy link
Contributor

GitHK commented Mar 19, 2025

I wrote some scripts that can generate the following lists (for any deployment:

  • all services that are used at least once in a project (these have to be synced)
  • all services that are not used in any project (these can be removed)
  • all services that the sync tool currently syncs to a deployment (allows us to track what we are syncing to each deployment's registry)

@GitHK
Copy link
Contributor

GitHK commented Mar 19, 2025

To answer the issue.

  • there are services which have no entry in the sync tool
  • we need to go though them one by one and figure out if we need them (might be deprecated or retire or not used by anybody or a legacy service)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:pipeline-services High Priority a totally crucial bug/feature to be fixed asap Maintenance Maintenance for CI
Projects
None yet
Development

No branches or pull requests

2 participants