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
yaml.loader is unsafe from a security perspective. From the
documentation:
Warning: It is not safe to call yaml.load with any data received
from an untrusted source! yaml.load is as powerful as pickle.load
and so may call any Python function.
I am pretty sure we don't want k8s users calling any python function ;-)
Change-Id: I7d2bb64d7920f530657426d2a1dc5780ebb95a47
Paritally-Implements: blueprint gate-bandit
When resource pod/rc/service is created with no
manifest, 500 status is returned to user due to
unhandled exception. This patch make this resource
creation return 400 status to user when no manifest
is passed. Also added test for empty manifest.
Change-Id: I7f6edc5bc7f8d46ea0eb0b71e22d2b88b3482154
Closes-bug:#1429767
Closes-bug:#1430064
newer hacking has rules for the following:
H105 Don't use author tags
H238 old style class declaration, use new style (inherit from `object`)
W292 no newline at end of file
So we need to clean them up and stop ignoring them
Change-Id: I12b995cf87d6bc0938298f397b41a4693627bb4b
When creating a service/pod, Magnum needs its name and more additional
information to store database.
This parser allows it.
Change-Id: I6e2a028f0caa7dbbd3a6de20aa3c982fb870c24a
Davanum Srinivas
Steven Dake
Madhuri Kumari
OTSUKA, Yuanying