deleted column type utils
Move and refactor methods from 152_migration that allows us to change type of deleted column to type of id. There are 2 methods: utils.change_deleted_column_type_to_id_type() method This method change type of `deleted` column from Boolean to type of `id`. This method allows us to do it in generic way for all backends. It fix problem with sqlite, that doesn't allow any operation with columns that have CheckConstraints. And columns with Boolean type have CheckConstraints (value in (0, 1)). So for sqlite it works through shadow tables. For others dbs it works though alter table. utils.change_deleted_column_type_to_boolean_type() methods This method allows us to revert result of previous method. Useful for downgrade. In global these methods could be very useful in olso for other projects. This is a first step that allows us to create unique constraints when we are using soft delete. (Create UC on (column, deleted)) Also it will be useful in nova to remove copy past from 179 migration. Add new migration that will fix also shadow_cells table. And also there are baremetal tables that should be also migrated. blueprint db-common-migration-and-utils Change-Id: Ie14351c52eb50182e6460c97e257395ce2adb8b0
OpenStack Nova README
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMware, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs.
OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities.
To keep updated with new developments in the OpenStack project follow @openstack on Twitter.
To learn how to deploy OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at:
Developers should also join the discussion on the mailing list, at:
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests. Further developer focused documentation is available at:
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.
-- End of broadcast