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

[Self] Force automatic sharing #3948

Closed
pdonias opened this issue Feb 7, 2019 · 8 comments
Closed

[Self] Force automatic sharing #3948

pdonias opened this issue Feb 7, 2019 · 8 comments
Assignees

Comments

@pdonias
Copy link
Member

pdonias commented Feb 7, 2019

See support#1251
Related to #3908

@pdonias
Copy link
Member Author

pdonias commented Feb 7, 2019

Maybe add an option in the Self Service to either:

  • disable VM sharing
  • let the self users share their VMs
  • always automatically share the VMs

@julien-f @olivierlambert

@julien-f
Copy link
Member

julien-f commented Feb 7, 2019

Let's keep in mind that a VM is being shared during the creation and that new users/groups added in the self service afterward will not have access to this VM.

@julien-f
Copy link
Member

julien-f commented Feb 7, 2019

About your suggestion I agree it would be nice to be able to set this for the whole self service, maybe simply the ability to set the shared default value.

@pdonias
Copy link
Member Author

pdonias commented Feb 7, 2019

This could be a thing but the main idea was to prevent Self users from creating non shared VMs.

@julien-f
Copy link
Member

julien-f commented Feb 7, 2019

I don't think so, as I understand it, the user simply do not want to rely on the users explicitly sharing their VMs.

@MattM3542
Copy link

Hi i put this support tick in, i new to Xen Orchestra( think it's a great product) but if you could create a ACL that give you the ability to choose the "Resource set name" as a object in the rule. I guess this would achieve what i was trying to do.

@pdonias
Copy link
Member Author

pdonias commented Feb 11, 2019

Hi @MattM3542! So you'd want to assign ACLs for resource sets, is that correct? Could you tell us why you'd want to do that? Also, if it's not related to this issue, please open a new one :)

@pdonias
Copy link
Member Author

pdonias commented Jun 15, 2023

Fixed by #6838

@pdonias pdonias closed this as completed Jun 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants