Hi Chris,
I think adding the owner is a good idea. However, the examples you provide
rely on the '/' separator, and currently that's a valid character for both
user and resource names.
This is our suggested syntax to implement this:
DISK = [ IMAGE= Ubuntu,
IMAGE_UNAME =
On Fri, Nov 04, 2011 at 07:00:21AM -0500, Carlos Martín Sánchez wrote:
Hi Chris,
I think adding the owner is a good idea. However, the examples you provide
rely
on the '/' separator, and currently that's a valid character for both user and
resource names.
This is our suggested syntax to
Hi Thomas,
Some users requested to let new resources use repeated names, see for
instance this thread [1]. This makes sense in deployments with a large
number of users, or in a multi-tenant scenario, where you don't want users
having to try a resource creation several times until they find a free
Hi, it's good to know the ONE developers are so open to feedback about
the way the system works. ONE seems great from what I've used so far.
The solution that you would propose would work fine for me, mostly
because it looks like that for a single user, the templating system
would work the same
This issue has caused myself much frustration as well. Personally I prefer the
suggestion of using both the owner and the resource name for specifying a
resource. That should work for just about any use case and allows names to be
used at any level with no confusion as to what resource is
In 2.2, in a VM template, I could specify an image for a disk that was
in the image repository by using IMAGE = name. This behavior appears
to have been removed in 3.0, in favor of using IMAGE_ID = id, where
id is an arbitrary number assigned by the opennebula system.
This change in behavior
