88ab9369e3
Cells currently keeps all inter-cell communication data, including
usernames and passwords, in the database. This is undesirable and
unnecessary, since cells data isn't updated very frequently. This
change allows cells data to be drawn from a JSON file specified via
a new [cells]cells_config option. When specified, the database is
no longer consulted when reloading cells data.
Implements blueprint eliminate-clear-passwords-from-cells-table.
DocImpact: Cells may now optionally be configured through a JSON-
formatted file. The file will need the columns present in the Cell
model (excluding common database fields and the 'id' column). The
queue connection information must be specified through a
'transport_url' field, instead of 'username', 'password', etc. The
transport_url has the following form:
rabbit://<username>:<password>@<hostname>:<port>/<virtual_host>
The scheme may be either 'rabbit' (shown above) or 'qpid'.
Change-Id: I7046ce55a0a294293c1b1a5fb0f092aeb891ee01
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