Resource primary key should not be a UUID

Bug #1415237 reported by Zane Bitter on 2015-01-27
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Angus Salkeld

Bug Description

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).

Angus Salkeld (asalkeld) on 2015-02-03
Changed in heat:
milestone: kilo-2 → kilo-3

Fix proposed to branch: master

Changed in heat:
assignee: Tetiana Lashchova (tlashchova) → Angus Salkeld (asalkeld)
status: Triaged → In Progress
Changed in heat:
assignee: Angus Salkeld (asalkeld) → Oleksii Chuprykov (ochuprykov)
Changed in heat:
assignee: Oleksii Chuprykov (ochuprykov) → Angus Salkeld (asalkeld)

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

    Change-Id: Idf7adc9d01425592ec174c373b1b03626c3a0a1d
    Closes-bug: #1415237

Changed in heat:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2015-03-19
Changed in heat:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2015-04-30
Changed in heat:
milestone: kilo-3 → 2015.1.0
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers