Feature #3874

Sunstone: use image name instead of id for files datastore

Added by Laurent Grawet almost 6 years ago. Updated about 4 years ago.

Status:ClosedStart date:07/15/2015
Priority:NormalDue date:
Assignee:Abel Coronado% Done:

100%

Category:Sunstone
Target version:Release 5.4
Resolution:fixed Pull request:

Description

Hi,

It would be better to use image name instead of id for files datastore because every time you modify a file/upload it again, you have to modify all VM templates.

Thank you,

Laurent

Associated revisions

Revision 99fce5b3
Added by Abel Coronado about 4 years ago

F #3874 use image name instead of id (#279)

History

#1 Updated by Laurent Grawet almost 6 years ago

...and almost everything else uses names instead of ids!

#2 Updated by Ruben S. Montero almost 6 years ago

  • Tracker changed from Request to Backlog
  • Target version changed from Release 4.14 to Release 5.0

This makes sense in deed. We have re-designed the whole Sunstone interface, for this release we aim at stabilizing it an the new features we have added rather to introduce more changes. I'm moving this to the backlog for the next release.

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

  • Tracker changed from Backlog to Feature

#4 Updated by Ruben S. Montero over 5 years ago

  • Status changed from Pending to New

#5 Updated by Anonymous about 5 years ago

This is a great feature for small environments, but we have many context files from our users where we have duplicate filenames from groups who aren't working together. In general people are not really original when inventing names for files. How are you going to manage sanity for the people who operate this and prevent double names used?

#6 Updated by Laurent Grawet about 5 years ago

Like any other place in Sunstone, simply by matching NAME+USER.
This is already the case for network and image references for example...

This has to be consistent : either use IDs or NAME+USER everywhere.
Core team chose the second solution a while ago.

The use of IDs is very problematic in this case. If you use context.ps1 windows contextualisation script on 10 000 VMs, you will have to update 10 000 templates each time you update (=upload) context.ps1 script. I wouldn't call that a small environment ;-)

#7 Updated by Ruben S. Montero about 5 years ago

  • Tracker changed from Feature to Backlog

#8 Updated by Ruben S. Montero almost 5 years ago

  • Target version changed from Release 5.0 to Release 5.4

#9 Updated by OpenNebula Systems Support Team over 4 years ago

  • Assignee set to Abel Coronado

We are going to use the the user as namespace like it is done on DISKS

CONTEXT = [
FILES_DS = "$FILE[IMAGE_ID=11]",
NETWORK = "YES",
SSH_PUBLIC_KEY = "$USER[SSH_PUBLIC_KEY]" ]
DISK = [
IMAGE = "Ubuntu-14.04-KVM-nu-Context",
IMAGE_UNAME = "oneadmin" ]

to be

CONTEXT = [
FILES_DS = $FILE[IMAGE="test", IMAGE_UNAME="oneadmin" ],
NETWORK = "YES",
SSH_PUBLIC_KEY = "$USER[SSH_PUBLIC_KEY]" ]
DISK = [
IMAGE = "Ubuntu-14.04-KVM-nu-Context",
IMAGE_UNAME = "oneadmin" ]

#10 Updated by Abel Coronado about 4 years ago

  • % Done changed from 0 to 100

#11 Updated by Tino Vázquez about 4 years ago

  • Tracker changed from Backlog to Feature
  • Status changed from New to Closed
  • Resolution set to fixed

Also available in: Atom PDF