Feature #1713

Support "Rename" for vnets, datastores and hosts

Added by Ricardo Duarte almost 8 years ago. Updated about 7 years ago.

Status:ClosedStart date:12/31/2012
Priority:NormalDue date:
Assignee:Carlos Martín% Done:

0%

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

Description

Currently, OpenNebula does not support rename of templates, vnets, datastores and hosts.
During an installation lifecycle, the initial names may need to be changed.
Say, for example, that a DS that was initially called "test" is reallocated to a "production" role. Currently, it is not possible to change the name to reflect that.

Associated revisions

Revision 17052e69
Added by Carlos Martín about 7 years ago

Feature #1713: Add host, ds and vnet rename actions

Revision 6641d154
Added by Carlos Martín about 7 years ago

Feature #1713: Add rename actions to sunstone

Revision a0e53831
Added by Carlos Martín about 7 years ago

Feature #1713: Add rename actions to Java OCA

Revision 8b3dd9f1
Added by Carlos Martín about 7 years ago

Feature #1713: New rename messages missing from translations

Revision 97d45b68
Added by Carlos Martín about 7 years ago

Feature #1713: Add host, ds & cluster name checks to fsck

Revision 33579df7
Added by Ruben S. Montero about 7 years ago

feature #1713: Deal with concurrent renames

History

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

  • Tracker changed from Request to Feature
  • Target version set to Release 4.0

This feature is partially implemented for 4.0 some objects can change their names. We are scheduling this for 4.0 to complete the set of resources.

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

  • Target version changed from Release 4.0 to Release 4.2

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

  • Category set to Core & System

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

  • Subject changed from Support "Rename" for templates, vnets, datastores and hosts to Support "Rename" for vnets, datastores and hosts
  • Priority changed from High to Low

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

  • Target version deleted (Release 4.2)

#6 Updated by Ruben S. Montero over 7 years ago

  • Priority changed from Low to Normal

#7 Updated by Ruben S. Montero over 7 years ago

  • Tracker changed from Feature to Backlog

#8 Updated by Ruben S. Montero over 7 years ago

  • Status changed from New to Pending

#9 Updated by Carlos Martín over 7 years ago

  • Assignee set to Carlos Martín

#10 Updated by Ruben S. Montero over 7 years ago

Vnets and templates can be renamed since 4.0. We'll implement rename for hosts, datastores and clusters. Objects in these resources will be updated also with the new name.

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

  • Tracker changed from Backlog to Feature
  • Status changed from Pending to New

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

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

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

  • Target version set to Release 4.4

Also available in: Atom PDF