tricircle/tricircle
Victor Morales a367814ad2 Enable tricircle commands
1. What is the problem?
There is no direct way to call tricircle commands.  In consequence,
every command has to be consumed thru python interpreter.
  e. g. python cmd/manage.py etc/api.conf

2. What is the solution to the problem?
The solution is to list the new commands in the pbr configuration
file. The pdr configuration requires a valid python modules, but
given that they have implementated in *cmd* directory(instead of
*tricircle/cmd*) is required to move them. As initial phase
commands will be copied, once there is no reference to the old ones
it's possible to proceed to deprecate them.

3. What the features need to be implemented to the Tricircle to
realize the solution?
Replace calls to duplicate module and deprecate the old one.

Change-Id: I6a27d990803e928151ca424f47564b6626c8e99b
2016-12-19 15:58:20 -06:00
..
api Remove logging import unused 2016-11-28 14:59:11 +07:00
cmd Enable tricircle commands 2016-12-19 15:58:20 -06:00
common Remove logging import unused 2016-11-28 14:59:11 +07:00
db ID should be biginteger in resource routing table 2016-12-08 15:58:19 +08:00
network PEP8 failed when import i18n more than one 2016-12-02 03:12:44 +00:00
tempestplugin Fix typos 2016-12-16 11:40:06 +08:00
tests Merge "Fix typos" 2016-12-16 23:49:14 +00:00
xjob PEP8 failed when import i18n more than one 2016-12-02 03:12:44 +00:00
__init__.py networking-tricircle core plugin and security group 2015-08-05 14:49:24 +03:00