yahoo-eng-team team mailing list archive

[Luca Cervigni <2056149@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description:
When creating an instance from volume, there are inconsistent behaviours and users usability issue. Using Yoga and confirmed it with older versions as well. It likely will be present on new versions too.

Cases:
- using the CLI and the --boot-from-volume flag:
  Naming: The instance gets created, and the volume does not get any name, it is just blank ""
  Problems: By default when instance deletion, the volume does not get deleted. If a user wants to reuse the root volume, finding the right volume is just impossible.
  Suggestion: it would be nice to call the volume "volume-$INSTANCEUUID" to have direct correspondency between a VM and its root volume.

- using Horizon and selecting the CREATE VOLUME button:
  Naming: The volume this time gets a name, that is equal to the volume UUID.
  Problems: The behaviour is different than the CLI and users (and admins) get confused.
  Suggestion: As above, to call the root volume when booting an instance from volume, to name it "volume-$INSTANCEUUID".

Overall it would be nice to an option to template the volume naming when
creating from volume, something like: boot_from_volume_naming_template:
volume-%UUID

The blank naming behaviour of case 1 should be fixed as a bug <---

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/2056149

Title:
  Inconsistent volume naming when create instance (from volume)

Status in OpenStack Compute (nova):
  New

Bug description:
  Description:
  When creating an instance from volume, there are inconsistent behaviours and users usability issue. Using Yoga and confirmed it with older versions as well. It likely will be present on new versions too.

  Cases:
  - using the CLI and the --boot-from-volume flag:
    Naming: The instance gets created, and the volume does not get any name, it is just blank ""
    Problems: By default when instance deletion, the volume does not get deleted. If a user wants to reuse the root volume, finding the right volume is just impossible.
    Suggestion: it would be nice to call the volume "volume-$INSTANCEUUID" to have direct correspondency between a VM and its root volume.

  - using Horizon and selecting the CREATE VOLUME button:
    Naming: The volume this time gets a name, that is equal to the volume UUID.
    Problems: The behaviour is different than the CLI and users (and admins) get confused.
    Suggestion: As above, to call the root volume when booting an instance from volume, to name it "volume-$INSTANCEUUID".

  Overall it would be nice to an option to template the volume naming
  when creating from volume, something like:
  boot_from_volume_naming_template: volume-%UUID

  The blank naming behaviour of case 1 should be fixed as a bug <---

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2056149/+subscriptions