Resource primary key should not be a UUID

[Zane Bitter]

We switched most database tables over to having auto-incrementing integers as primary keys. These are used for all references between tables in the database, while UUIDs are used for user-facing identification of objects. However the Resource table still uses a UUID as a primary key. We want to switch this to an auto-incrementing integer, while leaving the UUID column in place (it is used e.g. to generate physical resource names).

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/159741

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/159741
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=eb8c81f8db5b34c7574ed0faa549f608d159bd32
Submitter: Jenkins
Branch: master

commit eb8c81f8db5b34c7574ed0faa549f608d159bd32
Author: Angus Salkeld <email address hidden>
Date: Tue Mar 10 13:08:05 2015 +1000

    Create an integer id for the resource table

    Move the old uuid "id" to a new column "uuid". The migration
    script is largely copied from the event_uuid_to_id script.

    This is needed for https://review.openstack.org/#/c/156693/

    Change-Id: Idf7adc9d01425592ec174c373b1b03626c3a0a1d
    Closes-bug: #1415237