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

Hosted CE is listed as non-production, and not found for GRACC #1198

Open
djw8605 opened this issue Jun 3, 2020 · 8 comments
Open

Hosted CE is listed as non-production, and not found for GRACC #1198

djw8605 opened this issue Jun 3, 2020 · 8 comments
Assignees

Comments

@djw8605
Copy link
Member

djw8605 commented Jun 3, 2020

@efajardo @matyasselmeci

The hosted-ce34.grid.uchicago.edu is showing up in GRACC, a lot. But, it's listed as non-production in the topology, and therefore doesn't show up in the topology listing. Can we change this to production so the usage can be mapped?

@matyasselmeci
Copy link
Collaborator

Note that production/non-production is set on a per-ResourceGroup basis, so we would be changing the status of all the resources in that file. Is that OK?

@djw8605
Copy link
Member Author

djw8605 commented Jun 3, 2020

Unsure about the other resources. And edgar is out for a few days. But, we are missing usage!

@matyasselmeci
Copy link
Collaborator

If it's urgent then I can make the change; if it turns out to be wrong, Edgar can revert it when he gets back.

@djw8605
Copy link
Member Author

djw8605 commented Jun 3, 2020

Sounds good to me! Make the change.

@efajardo
Copy link
Contributor

efajardo commented Jun 8, 2020

I think there is something funky I thin that hostedCE is for actual production use from Comet but no the virtual cluster. So do I have to create another site? I think @mmascher set this up

@matyasselmeci
Copy link
Collaborator

You don't have to create an entire new site, just a new ResourceGroup (i.e. yaml file).

@matyasselmeci
Copy link
Collaborator

Just an explanation: Production: True/False converts to the GridType attribute in the XML, which is either "OSG Production Resource" i.e. it reports to the production collector, or "OSG Integration Test Bed Resource" i.e. it reports to the ITB collector (do we still have one?) It's per-ResourceGroup in the YAML because it's per-ResourceGroup in the XML.

@matyasselmeci
Copy link
Collaborator

Is this issue solved?

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