New Features¶

• Fixed theOS::Heat::UpdateWaitConditionHandle resource type, whichcaused stack update to fail consistently.

New Features¶

• Heat policies have been modified to isolate the system and project levelAPIs policy. Because of this change, system users will not be allowed toperform any operations on project level resources.

Upgrade Notes¶

• The following resources types are now hidden. Neutron LBaaS v2 was alreadyretired thus these resource types can no longer be used.

  • OS::Neutron::LBaaS::LoadBalancer

  • OS::Neutron::LBaaS::Listener

  • OS::Neutron::LBaaS::Pool

  • OS::Neutron::LBaaS::PoolMember

  • OS::Neutron::LBaaS::HealthMonitor

  • OS::Neutron::LBaaS::L7Policy

  • OS::Neutron::LBaaS::L7Rule

• The database migration engine has changed fromsqlalchemy-migrate toalembic. For most deployments, this should have minimal to no impactand the switch should be mostly transparent. The main user-facing impact isthe change in schema versioning. While sqlalchemy-migrate used a linear,integer-based versioning scheme, which required placeholder migrations toallow for potential migration backports, alembic uses a distributed versioncontrol-like schema where a migration’s ancestor is encoded in the file andbranches are possible. The alembic migration files therefore use aarbitrary UUID-like naming scheme and theheat-managedb_sync commandnow expects such an version when manually specifying the version that shouldbe applied. For example:

  $ heat-manage db_sync c6214ca60943

  Attempting to specify an sqlalchemy-migrate-based version will result in anerror.