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

Update VO configuration Guide? #185

Open
sebastian-luna-valero opened this issue May 4, 2022 · 3 comments
Open

Update VO configuration Guide? #185

sebastian-luna-valero opened this issue May 4, 2022 · 3 comments

Comments

@sebastian-luna-valero
Copy link
Member

Short Description of the issue

Looking at this example:

https://github.com/EGI-Federation/fedcloud-catchall-operations/search?q=pangeo

Should we update the VO configuration guide in the docs?

https://docs.egi.eu/providers/cloud-compute/openstack/vo_config/#information-system

Environment

  • Operating System:
  • Other related components versions:

Steps to reproduce

Logs, stacktrace, or other symptoms

output

Summary of proposed changes

@enolfc
Copy link
Contributor

enolfc commented May 6, 2022

You mean we lack the vo-mappings and deploy/vos to be mentioned in the guide?

@sebastian-luna-valero
Copy link
Member Author

Yes, sorry for being unclear.

Actually, looking back to this, the Information system section does explicitly says which file needs to be updated (sites/<SITE>.yaml). Giving an example or providing further details would be great.

I haven't opened a PR myself since we discussed internally in one of our meetings and it wasn't entirely clear. Actually. I opened this issue as a result of that meeting.

Happy to submit the PR once we clarify the steps in this discussion.

@sebastian-luna-valero
Copy link
Member Author

sebastian-luna-valero commented May 6, 2022

Answer in our service review meeting on 6th May 2022:

  • From the site point of view, only adding sites/<SITE>.yaml is required.
  • From the EGI point of view, adding vo-mappings.yaml, deploy/vos.yaml and sites/<SITE>.yaml is the optimal solution.

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

2 participants