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

Resource group or subscription? #2

Open
callaghanmt opened this issue May 21, 2019 · 2 comments
Open

Resource group or subscription? #2

callaghanmt opened this issue May 21, 2019 · 2 comments

Comments

@callaghanmt
Copy link
Collaborator

Should research groups/ RSE teams be given allocated a subscription or a resource group?
Are there advantages or disadvantages with each approach?

@callaghanmt
Copy link
Collaborator Author

Resource groups are very restrictive and although they might be the answer for simple projects, there are not the solution for complex projects. Particularly, they don't play nicely with Service Principals and Application Principals which many services require to themselves create resource. For example, CycleCloud is actually an orchestrator which creates resource itself. It needs to be given a Service Principal with the correct access roles to dynamically spin-up resources.

@callaghanmt
Copy link
Collaborator Author

The most flexible approach is to allocate subscriptions at the appropriate level within the organisation. This can be used in conjunction with Education Portal to manage allocating resource at a school/ course/ module level.

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

1 participant