Jump to: navigation, search

Difference between revisions of "Barbican/ReleaseNotes"

(Liberty Milestone 1)
(Deployment Impact)
Line 10: Line 10:
 
===Deployment Impact===
 
===Deployment Impact===
 
* This release makes changes to the Model layer, which has the potential to disrupt multi-node deployments.  The Alembic migration has been separated to be able to do a zero-downtime update with the previous version.  Migrations should be applied in this order:
 
* This release makes changes to the Model layer, which has the potential to disrupt multi-node deployments.  The Alembic migration has been separated to be able to do a zero-downtime update with the previous version.  Migrations should be applied in this order:
    # Apply 1bc885808c76_add_project_id_to_secrets.py
+
# Apply 1bc885808c76_add_project_id_to_secrets.py
    # Apply 161f8aceb687_fill_project_id_to_secrets_where_missing.py
+
# Apply 161f8aceb687_fill_project_id_to_secrets_where_missing.py
    # At this point, new nodes can be put into rotation while old nodes are phased out
+
# At this point, new nodes can be put into rotation while old nodes are phased out
    # Apply 1bece815014f_remove_projectsecret_table.py
+
# Apply 1bece815014f_remove_projectsecret_table.py

Revision as of 18:42, 25 June 2015

Barbican Liberty Series

Liberty Milestone 1

The Liberty Milestone 1 release (Version 1.0.0.0b1) is mostly a maintenance release with 20 bugfixes, and 2 Blueprints. For detailed information on the bugfixes, see the launchpad milestone page:

https://launchpad.net/barbican/+milestone/liberty-1

New Features

  • This release includes an API change to the root resource. The new response is modeled after the response in Keystone, and makes the Barbican root "/" consistent with other OpenStack projects.

Deployment Impact

  • This release makes changes to the Model layer, which has the potential to disrupt multi-node deployments. The Alembic migration has been separated to be able to do a zero-downtime update with the previous version. Migrations should be applied in this order:
  1. Apply 1bc885808c76_add_project_id_to_secrets.py
  2. Apply 161f8aceb687_fill_project_id_to_secrets_where_missing.py
  3. At this point, new nodes can be put into rotation while old nodes are phased out
  4. Apply 1bece815014f_remove_projectsecret_table.py