OpenStack versioned objects library
Go to file
James E. Blair ad5deec62c Zuul: Remove project name
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.

Change-Id: I2f94b6d0335e5452ef0bba3f2be3b1db442f8d79
2018-02-05 19:21:07 -08:00
doc Updated from global requirements 2018-01-18 03:25:08 +00:00
oslo_versionedobjects Remove log translations 2017-12-29 11:31:37 -06:00
playbooks/legacy/oslo.versionedobjects-src-grenade-devstack-multinode Migrate to zuulv3 - move legacy jobs to project 2017-10-16 08:40:11 +07:00
releasenotes Fix wrong indent of releasenotes 2018-01-03 07:46:22 +01:00
.coveragerc Fix coverage configuration and execution 2015-10-01 19:54:59 +00:00
.gitignore Add reno for release notes management 2016-11-03 14:43:46 +08:00
.gitreview apply oslo-cookiecutter template 2015-02-02 15:08:43 -05:00
.mailmap apply oslo-cookiecutter template 2015-02-02 15:08:43 -05:00
.testr.conf apply oslo-cookiecutter template 2015-02-02 15:08:43 -05:00
.zuul.yaml Zuul: Remove project name 2018-02-05 19:21:07 -08:00
babel.cfg apply oslo-cookiecutter template 2015-02-02 15:08:43 -05:00
CONTRIBUTING.rst rearrange existing documentation to fit the new standard layout 2017-07-01 21:02:49 +09:00
HACKING.rst Update URLs in documents according to document migration 2017-07-13 10:00:49 +08:00
LICENSE apply oslo-cookiecutter template 2015-02-02 15:08:43 -05:00
README.rst Update URLs in documents according to document migration 2017-07-13 10:00:49 +08:00
requirements.txt Updated from global requirements 2018-01-16 12:48:00 +00:00
setup.cfg Treat doc warnings as errors 2018-01-08 11:59:49 -06:00
setup.py Updated from global requirements 2017-03-03 00:03:27 +00:00
test-requirements.txt Updated from global requirements 2018-01-16 12:48:00 +00:00
tox.ini Treat doc warnings as errors 2018-01-08 11:59:49 -06:00

Team and repository tags

image

oslo.versionedobjects

Latest Version

Downloads

The oslo.versionedobjects library provides a generic versioned object model that is RPC-friendly, with inbuilt serialization, field typing, and remotable method calls. It can be used to define a data model within a project independent of external APIs or database schema for the purposes of providing upgrade compatibility across distributed services.