yahoo-eng-team team mailing list archive

[Haiyang DING <dinghaiyang@xxxxxxxxxx>]

Public bug reported:

When I try to create a new image with command "glance image-create", I
found that the name of an already existing image can be used to name the
new one. For example:

+--------------------------------------+---------------------------------+-------------+------------------+-----------+--------+
| ID                                   | Name                            | Disk Format | Container Format | Size      | Status |
+--------------------------------------+---------------------------------+-------------+------------------+-----------+--------+
| a52c2602-ff9f-471e-b414-52d2c967e728 | cirros-0.3.1-x86_64-uec         | ami         | ami              | 25165824  | active |
| 3c5974ba-5ff9-4d93-9e1f-e0489f1ca85f | cirros-0.3.1-x86_64-uec-kernel  | aki         | aki              | 4955792   | active |
| 793c880f-aeba-419a-b603-cc59959d4c4f | cirros-0.3.1-x86_64-uec-ramdisk | ari         | ari              | 3714968   | active |
| 366bd9e4-f696-46cd-85c4-5abbed492450 | F17-x86_64-cfntools             | qcow2       | bare             | 476704768 | active |
| 1a6588c1-282c-4b26-a5fb-82ccb12bf943 | precise-server-img              | qcow2       | bare             | 258277888 | active |
| 2320f9d3-74c3-410c-a80a-19278f67d67a | precise-server-img              | qcow2       | bare             | 258277888 | active |
| 3f3f7ca7-999d-497b-a97b-55b5d1d21103 | precise-server-img              | qcow2       | bare             | 258277888 | active |
+--------------------------------------+---------------------------------+-------------+------------------+-----------+--------+

I have seen a similar report at :
https://bugs.launchpad.net/glance/+bug/687949

The answer was "This is by design. We can't expect users to avoid other
user's image names..." which I totally agree: users should have their
freedom choosing names.

However, I think we can make it better since this has some negative
impacts on other actions. For instance,

1. "heat stack-create" requires the name of a image while duplicated image name(s) would cause an error. 
2. Inconvenience is also found when deleting such image(s), since one would have to use "ID" instead of "Name". 
3. Moreover when a user creates a image without checking if there is any duplicates, he would run into trouble afterwards since it requires some extra efforts to distinguish "his image" from the duplicated one(s).

So, I think we should at least warn the users when they try to create
image with existing image name(s) and (maybe) give them a chance to
rename the image before further action is actually carried out. Using
duplicated name is still allowed.

What do you think?

This is my first time proposing anything here. Any suggestion is
welcome.

Thank you.

Best regards.

** Affects: glance
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1310507

Title:
  Duplicated image names.

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  When I try to create a new image with command "glance image-create", I
  found that the name of an already existing image can be used to name
  the new one. For example:

  +--------------------------------------+---------------------------------+-------------+------------------+-----------+--------+
  | ID                                   | Name                            | Disk Format | Container Format | Size      | Status |
  +--------------------------------------+---------------------------------+-------------+------------------+-----------+--------+
  | a52c2602-ff9f-471e-b414-52d2c967e728 | cirros-0.3.1-x86_64-uec         | ami         | ami              | 25165824  | active |
  | 3c5974ba-5ff9-4d93-9e1f-e0489f1ca85f | cirros-0.3.1-x86_64-uec-kernel  | aki         | aki              | 4955792   | active |
  | 793c880f-aeba-419a-b603-cc59959d4c4f | cirros-0.3.1-x86_64-uec-ramdisk | ari         | ari              | 3714968   | active |
  | 366bd9e4-f696-46cd-85c4-5abbed492450 | F17-x86_64-cfntools             | qcow2       | bare             | 476704768 | active |
  | 1a6588c1-282c-4b26-a5fb-82ccb12bf943 | precise-server-img              | qcow2       | bare             | 258277888 | active |
  | 2320f9d3-74c3-410c-a80a-19278f67d67a | precise-server-img              | qcow2       | bare             | 258277888 | active |
  | 3f3f7ca7-999d-497b-a97b-55b5d1d21103 | precise-server-img              | qcow2       | bare             | 258277888 | active |
  +--------------------------------------+---------------------------------+-------------+------------------+-----------+--------+

  I have seen a similar report at :
  https://bugs.launchpad.net/glance/+bug/687949

  The answer was "This is by design. We can't expect users to avoid
  other user's image names..." which I totally agree: users should have
  their freedom choosing names.

  However, I think we can make it better since this has some negative
  impacts on other actions. For instance,

  1. "heat stack-create" requires the name of a image while duplicated image name(s) would cause an error. 
  2. Inconvenience is also found when deleting such image(s), since one would have to use "ID" instead of "Name". 
  3. Moreover when a user creates a image without checking if there is any duplicates, he would run into trouble afterwards since it requires some extra efforts to distinguish "his image" from the duplicated one(s).

  So, I think we should at least warn the users when they try to create
  image with existing image name(s) and (maybe) give them a chance to
  rename the image before further action is actually carried out. Using
  duplicated name is still allowed.

  What do you think?

  This is my first time proposing anything here. Any suggestion is
  welcome.

  Thank you.

  Best regards.

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