Feature #488

Let Objects (Images, VNets) repeat names

Added by Carlos Martín almost 10 years ago. Updated over 9 years ago.

Status:ClosedStart date:02/18/2011
Priority:NormalDue date:
Assignee:Carlos Martín% Done:

0%

Category:Core & System
Target version:Release 3.0
Resolution:fixed Pull request:

Description

Some users have asked to have different images with the same name.

We'll provide a generic approach for both Images and Virtual Networks:
Names can be repeated, but only if the collision is with an object of a different user.
i.e. a user can define only one Image or VNet with the same name.

When using an Image or VNet by name, the following precedence will be used:
  1. User's object
  2. Other user's public object

In case there are more than one public objects with the same name (from different users), OpenNebula should fail and ask the user to use the IMAGE_ID or VNET_ID.


Related issues

Related to Feature #539: Check Request consistency Closed 03/20/2011

Associated revisions

Revision a088af7d
Added by Carlos Martín over 9 years ago

Feature #487, #488: Templates now can't repeat name

Revision 1e4e4f2c
Added by Ruben S. Montero over 9 years ago

feature #523, #407, #488: Template is now part of base class PoolObjectSQL

Revision 82982a7a
Added by Ruben S. Montero over 9 years ago

feature #653, #488: Images can only be referenced by ID in DISKs. Names can now be repeated, even for the same user

Revision 88317546
Added by Ruben S. Montero over 9 years ago

feature #653, #488: Networks can only be referenced by ID in NICs. Names can now be repeated, even for the same user

Revision a5f31429
Added by Abel Coronado about 3 years ago

B #5388: Added capacity unit in disks (cloud view) (#488)

Revision e4614205
Added by Abel Coronado about 3 years ago

B #5388: Added capacity unit in disks (cloud view) (#488)

(cherry picked from commit a5f314298dbf431ca9001467ba6c3932201c3d6f)

History

#1 Updated by Ruben S. Montero almost 10 years ago

  • Target version deleted (Release 2.2)

#2 Updated by Ruben S. Montero over 9 years ago

  • Target version set to Release 3.0

Names will be only valid for your own resources, any other resource should be reference by its ID

#3 Updated by Ruben S. Montero over 9 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

Also available in: Atom PDF