openstack
/
magnum
Code Issues Proposed changes
magnum/magnum/objects
History
Davanum Srinivas bf42ec94ef Setup for translation 
To start translation, we need to initially import the
translation file - and place it at the proper place so that
the usual CI scripts can handle it.

The proper place is for all python projects
$PROJECT/locale/$PROJECT.pot - see setup.cfg.

Note that we were using _i18n.py from openstack/common
which is likely to go away, so created our own i18n.py
module per best practices:
http://docs.openstack.org/developer/oslo.i18n/usage.html#creating-an-integration-module

Further imports will be done by the OpenStack Proposal bot.

implements blueprint magnum-i18n-support
Change-Id: Ib34bfbe1ae47e077e92a4262642842c845d1a5d6
 		2015-05-24 03:13:55 +00:00
..
__init__.py Objects changes for horizontal-scale support 2015-04-11 16:29:30 +00:00
base.py Remove unused methods and functions 2015-05-21 10:33:59 +02:00
bay.py Move VersionedObject registration to the new scheme 2015-05-11 12:05:15 +02:00
baylock.py Move VersionedObject registration to the new scheme 2015-05-11 12:05:15 +02:00
baymodel.py Move VersionedObject registration to the new scheme 2015-05-11 12:05:15 +02:00
container.py Add support for container status 2015-05-12 13:52:36 +08:00
fields.py Make MagnumObject a subclass of Oslo VersionedObject 2015-05-11 11:46:49 +02:00
node.py Move VersionedObject registration to the new scheme 2015-05-11 12:05:15 +02:00
pod.py Move VersionedObject registration to the new scheme 2015-05-11 12:05:15 +02:00
replicationcontroller.py Move VersionedObject registration to the new scheme 2015-05-11 12:05:15 +02:00
service.py Move VersionedObject registration to the new scheme 2015-05-11 12:05:15 +02:00
utils.py Setup for translation 2015-05-24 03:13:55 +00:00