Reviewed: https://review.openstack.org/360666 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=94d5c886ba2b19288276e517317fcd74cc8e4592 Submitter: Jenkins Branch: master
commit 94d5c886ba2b19288276e517317fcd74cc8e4592 Author: Pushkar Umaranikar <[email protected]> Date: Thu Sep 22 21:28:00 2016 +0000 Remove internal_id attribute from instances table internal_id attribute column from instances table is no longer used. This commit removes internal_id from object layer. In the later release, this can be removed from schema by adding migration script. Change-Id: Ia285a16a8fab38a61959df847d30bce2d60ad081 Closes-Bug: #1441242 ** Changed in: nova Status: In Progress => Fix Released -- 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): Fix Released 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 : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
