Resource name update

[Belmiro Moreira]

When creating a resource (ex: instance, volume) the ec2-api project
first creates with the reservation name and then updates the name
with the ec2id (random generated) value.

(Example of an instance)
First the name is <ec2_reservation_id>-<launch_index>
and then is updated by i-xxxxxxxx

This is an issue for the deployments that don't allow resource
updates because the integration with external systems.

[Andrey Pavlov (apavlov-e)]

What is importance of this issue for you?

[Belmiro Moreira (moreira-belmiro-email-lists)]

Hi Andrey,
at CERN we don't allow users to update resources names,
because our OpenStack it's integrated with several external systems.
So, we block resources updates in the policy.

After creating resources the ec2api tries to update the name
(ex for VMs: i-xxxxxxxx).

At the moment I just commented the update.
Would be acceptable to disable updates with a configuration option?
I'm willing to implement it.

[Feodor Tersin (ftersin)]

Hi Belmiro

Sorry for the long silence. Is the problem still actual?