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

Merge with top-bdii package repo? #6

Open
brucellino opened this issue May 7, 2018 · 3 comments
Open

Merge with top-bdii package repo? #6

brucellino opened this issue May 7, 2018 · 3 comments
Assignees
Labels

Comments

@brucellino
Copy link
Member

This only runs on top-bdiis. I propose that it should be merged with the repo that contains the top-bdii package itself. Why does this script live all by itself?

@maarten-litmaath
Copy link

Merging makes sense to me.

@gwarf
Copy link
Member

gwarf commented Aug 24, 2018

I'm looking at this, so we don't really have (yet) a repo dedicated to the top-bdii package itself, we have a repo for metapackages that contains one spec for top-bdii and a repo for bdii-config-top.

The glite-info-update-endpoints is a requirement of the bdii-config-top package.
And the bdii-config-top package is a requirement of the emi-bdii-top pacakge.

So we could move the glite-info-update-endpoints stuff to the bdii-config-top repo, what do you think?

@gwarf gwarf assigned gwarf and unassigned maarten-litmaath Aug 24, 2018
@gwarf
Copy link
Member

gwarf commented Aug 24, 2018

In fact it may be appropriate to reorganize all the BDII-related repositories to simplify their management, and properly separate code from configuration.

@gwarf gwarf added this to To do in BDII support via automation Sep 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

3 participants