Thanks very much for the message. We appreciate quick responses from opennebula developers..
Hyunwoo On Jul 3, 2012, at 11:12 AM, Carlos Martín Sánchez wrote: > Hi, > > Since OpenNebula 3.4 you can change the restricted attributes in oned.conf, > see [1]. > > If for any reason you can't upgrade, the only option you have left is to > modify the code. The list of restricted VM attributes is defined in > src/vm/VirtualMachineTemplate.cc, > VirtualMachineTemplate::RESTRICTED_ATTRIBUTES > > > Regards > > [1] > http://opennebula.org/documentation:rel3.4:compatibility#configuration_and_administration > -- > Carlos Martín, MSc > Project Engineer > OpenNebula - The Open-source Solution for Data Center Virtualization > www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula > > > > On Mon, Jul 2, 2012 at 11:39 PM, Hyun Woo Kim <hyun...@fnal.gov> wrote: > I am deploying OpenNebula 3.2 and I am observing a new feature different from > ONe 3.0. > > When a normal user in the "users" group wants to use the "files" attribute in > CONTEXT > and instantiate a new VM, we are getting the following error message; > [TemplateInstantiate] Error allocating a new virtual machine. VM Template > includes a restricted attribute CONTEXT/FILES. > > I know that if the normal user can belong to oneadmin group, this error does > not appear. > > If this is actually how ONe3.2 works, can we get around this and let normal > users use CONTEXT/FILES > without having to change the user's group to oneadmin? > > Thank you. > Hyunwoo > > > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
