Maybe I wrong but when I tryed the 1. method. I could create template
and change permissions but I could not deploy it with other user than
oneadmin.
2012-05-07 23:06 keltezéssel, Ruben S. Montero írta:
Hi,
You can either
1.- Create the templates with oneadmin and set the permissions so
Thanks,
I didn't about the latter one, and will use it.
On Mon, 2012-05-07 at 23:06 +0200, Ruben S. Montero wrote:
Hi,
You can either
1.- Create the templates with oneadmin and set the permissions so
everybody or a set of users can use it (this way the template is
considered secure).
Hi
Bypassing the template checks for oneadmin (and oneadmin group)
templates is in 3.4, Are you trying with this version?
Cheers
Ruben
On Tue, May 8, 2012 at 9:07 AM, Guba Sándor gubasa...@gmail.com wrote:
Maybe I wrong but when I tryed the 1. method. I could create template and
change
As per redmine issue http://dev.opennebula.org/issues/1159 , it seems
that only oneadmin templates are not being checked.
In my scenario, users should be able to create their own templates (or
copy from oneadmin's) and fire up instances accessing CONTEXT/FILES.
I've granted:
15 @101
Hi,
You can either
1.- Create the templates with oneadmin and set the permissions so
everybody or a set of users can use it (this way the template is
considered secure). This can be done with onetemplate chmod or setting
up an ACL for more complex sharing needs.
2.- Remove CONTEXT/FILES as a
