Recently in the Inria's Discovery initiative, we got in touch with
CockroachLabs guys with an idea: make Keystone supports CockorachDB. So
we give it a try and you can find a very first result on our GitHub.
The GitHub project consists of a Vagrant file that spawns a VM with a
CockroachDB database and then installs Keystone with Devstack using
CockroachDB as backend.
CockroachDB claims to support the PostgreSQL protocol. It also provides
support for SQLAlchemy that mostly inherits from the PostgreSQL one. So,
making Keystone working with CockroachDB should be easy peasy right?
Almost! The rest of this email describes what we have done, to make it
sqlalchemy-migrate doesn't work with CockroachDB
Keystone uses a database migration tool named sqlalchemy-migrate.
This tool is called during the deployment of Keystone to migrate the
database from its initial versions to its actual version.
Unfortunately, migration failed with the following (partial)
| DEBUG migrate.versioning.repository [-] Config:
OrderedDict([('dbsettings', OrderedDict([('name', 'dbsettings'),
('repositoryid', 'keystone'), ('versiontable', 'migrateversion'),
('requireddbs', ''), ('usetimestampnumbering', 'False')]))])
| INFO migrate.versioning.api [-] 66 -> 67...
| CRITICAL keystone [-] KeyError: 'cockroachdb'
| TRACE keystone visitorcallable = getenginevisitor(engine, visitorname)
| TRACE keystone File
line 47, in getenginevisitor
| TRACE keystone return getdialectvisitor(engine.dialect, name)
| TRACE keystone File
line 62, in getdialectvisitor
| TRACE keystone migratedialectcls = DIALECTS[sadialect_name]
| TRACE keystone KeyError: 'cockroachdb'
As we understand it, sqlalchemy-migrate contains dedicated SQL backend
codes and there is no such code for CockroachDB. As a workaround, we
have performed a second OS deployment with PostgreSQL as backend and
made a dump of the database after migrations. We then bypassed
migrations in our first deployment by setting up CockroachDB with the
dumped script. Note that we had to edit the pgdump script a little bit
because some features are missing in CockroachDB.
The workaround we have to go with represents an obstacle to test
CockroachDB with other OpenStack core services. We would be grateful
if some of you would help us with adding the support of CockroachDB in
oslo.db contains backend specific code for error handling
oslo.db' library contains one file with backend-specific codes
(oslodb/sqlalchemy/excfilters.py'). This file aims at
abstracting database exceptions that differ but target the same class
of error (because each backend produces a specific exception with a
specific error message). Intercepted exceptions are wrapped into a
common OS exception to abstract backend errors in the rest of
`oslo.db'. CockroachDB doesn't produce same errors than PostgreSQL, so
we have to update this class. Note that our POC is not exhaustive
since we only added error messages we saw during Tempest/Rally tests.
You can look at the differences between OpenStack/oslo.db/stable/pike
and our fork on GitHub. We only add two lines!
CockroachDB manages isolation without lock
CockroachDB lets you write transactions that respect ACID properties.
Regarding the "I" (Isolation), CockroachDB offers snapshot and
serializable isolation but doesn't rely on locks to do that. So every
time there is concurrent editing transactions that end in a conflict,
then you have to retry the transactions. Fortunately, `oslo.db'
already offers a decorator to do that automatically. But, based on
tests we run with Tempest/Rally, we figured out that some Keystone's
SQL requests needed the decorator.
You can look at the differences between OpenStack/keystone/stable/pike
and our fork on GitHub.
You can drop yourself on the VM as a stack user and run Rally tests
(see README). Tempest is disabled because we have an issue with its
installation. Note that modifications we made to make it works are
minimal. This is promising for the adoption of CockroachDB by other
core services. Nonetheless:
Fixing the problem with sqlalchemy-migrate will be helpful to ease
the deployment process. If you are willing to help, we will be
We have to look through the performance prism: Keystone over
CockroachDB vs. Keystone over Galera. This part may involve more
oslo.db'. One thing we have in mind is the
management of retrying transactions since CockroachDB's
documentation suggests an approach that doesn't match with actualoslo.db' implementation.
OpenStack Development Mailing List (not for usage questions)