332e2b6fe4
We noticed that from the user perspective it is hard to know when a cluster_template provided by the cloud admin is mature enough for a production release. This field will allow the administrator to add an annotation to the cluster template like {deprecated, recommended, testing} giving further usefull information to the end user about the template's life cycle This patch adds the necessary database column and API objects to handle the new argument. story: 2007857 task: 40160 Change-Id: I5d1c4221f089bc5cd12b25f620aa01771a029df9 Signed-off-by: Diogo Guerra <diogo.filipe.tomas.guerra@cern.ch> |
||
---|---|---|
.. | ||
versions | ||
README | ||
env.py | ||
script.py.mako |
README
Please see https://alembic.readthedocs.org/en/latest/index.html for general documentation To create alembic migrations use: $ magnum-db-manage revision --message "description of revision" --autogenerate Stamp db with most recent migration version, without actually running migrations $ magnum-db-manage stamp head Upgrade can be performed by: $ magnum-db-manage upgrade $ magnum-db-manage upgrade head