| 2015-02-10 05:16:04 |
Kanagaraj Manickam |
bug |
|
|
added bug |
| 2015-02-10 05:16:11 |
Kanagaraj Manickam |
heat: assignee |
|
Kanagaraj Manickam (kanagaraj-manickam) |
|
| 2015-02-10 05:19:39 |
Kanagaraj Manickam |
description |
Once heat is installed, admin runs "heat-manage db_sync" command, which will run all migration scripts (in ./heat/db/sqlalchemy/migrate_repo/versions) upto HEAD version. This is very much suitable for the upgrades/downgrades of heat versions.
But on the fresh installation, the db schema can be created directly instead of running through these migration scripts, which will speedup the operation and schema will be generated in single run.
This bug is filed to address it.
To fix, we could use following snippet of the code:
from sqlalchemy.ext.declarative import declarative_base
#engine = <create the engine here>
declarative_base().metadata.create_all(engine). |
Once heat is installed, admin runs "heat-manage db_sync" command, which will run all migration scripts (in ./heat/db/sqlalchemy/migrate_repo/versions) upto HEAD version. This is very much suitable for the upgrades/downgrades of heat versions.
But on the fresh installation, the db schema can be created directly instead of running through these migration scripts, which will speedup the operation and schema will be generated in single run.
This bug is filed to address it.
To fix, we could use following snippet of the code:
from sqlalchemy.ext.declarative import declarative_base
#engine = <create the engine here>
declarative_base().metadata.create_all(engine).
#stamp with head version |
|
| 2015-02-10 05:20:14 |
Kanagaraj Manickam |
description |
Once heat is installed, admin runs "heat-manage db_sync" command, which will run all migration scripts (in ./heat/db/sqlalchemy/migrate_repo/versions) upto HEAD version. This is very much suitable for the upgrades/downgrades of heat versions.
But on the fresh installation, the db schema can be created directly instead of running through these migration scripts, which will speedup the operation and schema will be generated in single run.
This bug is filed to address it.
To fix, we could use following snippet of the code:
from sqlalchemy.ext.declarative import declarative_base
#engine = <create the engine here>
declarative_base().metadata.create_all(engine).
#stamp with head version |
Once heat is installed, admin runs "heat-manage db_sync" command, which will run all migration scripts (in ./heat/db/sqlalchemy/migrate_repo/versions) upto HEAD version. This is very much suitable for the upgrades/downgrades of heat versions.
But on the fresh installation, the db schema can be created directly in sqlalchemy way, instead of running through these migration scripts, which will speedup the operation and schema will be generated in single run.
This bug is filed to address it.
To fix, we could use following snippet of the code:
from sqlalchemy.ext.declarative import declarative_base
#engine = <create the engine here>
declarative_base().metadata.create_all(engine).
#stamp with head version |
|
| 2015-03-25 23:52:51 |
Angus Salkeld |
summary |
on fresh installation, create schema directly instead of migration scripts |
Squash the havana migration scripts |
|
| 2015-03-25 23:55:16 |
Angus Salkeld |
heat: status |
New |
Triaged |
|
| 2015-03-25 23:55:21 |
Angus Salkeld |
heat: importance |
Undecided |
Low |
|
| 2015-03-25 23:55:27 |
Angus Salkeld |
heat: milestone |
|
liberty-1 |
|
| 2015-05-22 18:51:08 |
Kanagaraj Manickam |
heat: status |
Triaged |
In Progress |
|
| 2015-05-28 06:18:15 |
OpenStack Infra |
heat: assignee |
Kanagaraj Manickam (kanagaraj-manickam) |
Qiming Teng (tengqim) |
|
| 2015-06-23 21:42:02 |
Steve Baker |
heat: milestone |
liberty-1 |
liberty-2 |
|
| 2015-07-03 03:08:26 |
OpenStack Infra |
heat: status |
In Progress |
Fix Committed |
|
| 2015-07-31 07:13:34 |
Thierry Carrez |
heat: status |
Fix Committed |
Fix Released |
|
| 2015-10-15 10:23:52 |
Thierry Carrez |
heat: milestone |
liberty-2 |
5.0.0 |
|
