ba6705a731
Overview: MySQL requires indexes on foreign keys. Such an index is created on the referencing table automatically if it does not exist. Motivation: MySQL names foreign keys indexes differently dependent from itself version. Implicit fk indexes is MySQL specific behavior, so it should be ignored during comparision. We plan to use Alembic to compare models and migrations I0758c7e09d1d46ce870c3f94f76c2a177955e143. Alembic doesn't support 5.5 naming convention. So we need consistent index name for all MySQL versions to be easily ignored. Solution: A new migration script renames incorrectly named fk indexes on MySQL. Reproduction: Stop execution when foregn keys will be initialized. See schema with your MySQL shell client. With 5.5, indexes which was not named explicitly, will have a name such as <tablename>_<columnname>_fk, with 5.1 it will be <columnname>. Change-Id: I01ba0c8856afbda59394395ac319bf83a55ee2be Partial-Bug: #1292591 |
||
---|---|---|
bin | ||
doc | ||
etc | ||
examples/pki | ||
httpd | ||
keystone | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.testr.conf | ||
babel.cfg | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
openstack-common.conf | ||
README.rst | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
OpenStack Keystone
Keystone provides authentication, authorization and service discovery mechanisms via HTTP primarily for use by projects in the OpenStack family. It is most commonly deployed as an HTTP interface to existing identity systems, such as LDAP.
Developer documentation, the source of which is in
doc/source/
, is published at:
The API specification is available at:
The API documentation is available at:
The canonical client library is available at:
Documentation for cloud administrators is available at:
The source of documentation for cloud administrators is available at:
Information about our team meeting is available at:
Bugs and feature requests are tracked on Launchpad at:
Future design work is tracked at:
Contributors are encouraged to join IRC
(#openstack-keystone
on freenode):
For information on contributing to Keystone, see
CONTRIBUTING.rst
.