magnum

History

Feilong Wang 16344a5a95 Add separated CA cert for etcd and front-proxy Support creating different for k8s, etcd and front-proxy for security hardening. We're following some best practices[1][2] but adjusted based on the current Magnum deployment approach. [1] https://kubernetes.io/docs/setup/best-practices/certificates/ [2] https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/ Task: 40687 Story: 2008031 Change-Id: I523a4a85867f82d234ba1f3e6fad8b8cd2291182		2021-04-01 17:31:34 +00:00
..
versions	Add separated CA cert for etcd and front-proxy	2021-04-01 17:31:34 +00:00
README	Remove downgrade from existing migrations	2015-03-28 10:27:53 +08:00
env.py	Copy Ironic's database model codebase	2014-12-02 15:04:31 -07:00
script.py.mako	Remove downgrade from existing migrations	2015-03-28 10:27:53 +08:00

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