Hi all,
We are considering a new simple approach on this use-case, and we'd like to
hear your thoughts:
Resources could have two flags to let other users list/use them:
- shared: users in the resource's group.
- public: all users
This would make it easier to share resources with everybody
This seems a sensible approach to me. It's reminiscent of the unix
permission categories me, group and everyone.
2011/9/21 Carlos Martín Sánchez cmar...@opennebula.org:
Hi all,
We are considering a new simple approach on this use-case, and we'd like to
hear your thoughts:
Resources could
Hi Robert,
You are right about the meaning of public, its scope is the resource's
group.
Using ACLs, you can create a group (let's say shared), and allow everybody
to use and instantiate IMAGE and TEMPLATES in that group.
$ onegroup create shared
ID: 100
ACL_ID: 2
ACL_ID: 3
$ oneacl create *
Hi Carlos,
The workaround you describe will get us going, and we can enumerate
our temapltes and resources as needed for now.
The multiple groups idea is most likely the _right_ approach, but for
the time being perhaps also could be added a public flag to listing,
which lists all objects which
Hi Folks,
Is there some way to make images or templates completely public?
Currently, it looks like making an image or template public means
that anyone within your group can see and use that image or template.
It would be nice to also have the functionality where members of any
group can make
