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

split off sync clients from this repo #110

Open
stdweird opened this issue Dec 18, 2020 · 5 comments
Open

split off sync clients from this repo #110

stdweird opened this issue Dec 18, 2020 · 5 comments

Comments

@stdweird
Copy link
Member

Try to split off the sync clients from this repo, in particular to get rid of unnecessary dependencies and allow easier development
Eg. the slurm sync now pulls in ldap dependencies.

New repos can simply list vsc-administration as a dependency and there's no need for code changes.
However, once split, new packages will have to be installed on the relevant hosts to provide the sync clients

@stdweird
Copy link
Member Author

@wpoely86 @peterverraedt @backelj thoughts?
i can do this for the slurm code (making vsc-slurm or vsc-sync-slurm; not sure yet). as we don't use ldap in gent, it might be better that someone else takes this part over.

@itkovian
Copy link
Member

I am in favour.

@wpoely86
Copy link
Collaborator

How do you propose to split it? Everything in a separate repo?
I currently see:

  • slurm accounting sync
  • ldap account sync
  • mail sync (for slurm)
  • sync/create VSC account directories + quota

@stdweird
Copy link
Member Author

@wpoely86 yes, that would be ideal.
at the very least every clients that add dependencies (ldap for ldapsync and filesystems for user sync). because that complicates the deployment and development

@wpoely86
Copy link
Collaborator

OK, no issue for me.

I can have a look at the ldap bits but it's going to be for next year.

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

No branches or pull requests

3 participants