Public bug reported:
The nova instances table contains internal_id field, Looks like it is
always NULL and never referenced.
The ec2 API uses a variable with same name for snapshots and volumes,
but not for instance id.
For the ec2 id -> uuid mapping now a separated table is responsible:
instance_id_mappings which contains an id Integer for ec2 instance-000001
strings and referencing to the instances table with an uuid.
Instead of using instance_id_mappings the internal_id field could be
used.
Note.: The ec2 could use the instances.id, but the ec2 users does not
likes the random instance-id change, so it might need a special
handling.
** 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/1441242
Title:
instances internal_id attribute not in use
Status in OpenStack Compute (Nova):
New
Bug description:
The nova instances table contains internal_id field, Looks like it is
always NULL and never referenced.
The ec2 API uses a variable with same name for snapshots and volumes,
but not for instance id.
For the ec2 id -> uuid mapping now a separated table is responsible:
instance_id_mappings which contains an id Integer for ec2 instance-000001
strings and referencing to the instances table with an uuid.
Instead of using instance_id_mappings the internal_id field could be
used.
Note.: The ec2 could use the instances.id, but the ec2 users does not
likes the random instance-id change, so it might need a special
handling.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1441242/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
