180f68eac8
1. What is the problem? Networking related code is still in the repository of the Trio2o project. 2. What is the solution to the problem? According to the blueprint for the Trio2o cleaning: https://blueprints.launchpad.net/trio2o/+spec/trio2o-code-cleaning Networking related code which is forked from the Tricircle repository should be removed from the Trio2o repository. After the cleanning, the Trio2o should be able to run independently. There are lots of things to clean and update, and have to do it in one huge patch, otherwise the code in Trio2o will not be able to run and tested properply: 1). Remove netwoking operaion from server controller 2). Update devstack script 3). Update installation guide 4). Update README 5). Remove network folder and network related unit tests 6). Rename Tricircle to Trio2o in all source code THE MEANING OF FILE OPERATION: D: delete a file R: rename a file to another name A: add a new file C: copy a file 3. What the features need to be implemented to the Tricircle to realize the solution? No new features. Change-Id: I0b48ee38280e25ba6294ca3d5b7a0673cb368ed4 Signed-off-by: joehuang <joehuang@huawei.com>
17 lines
442 B
Plaintext
17 lines
442 B
Plaintext
[DEFAULT]
|
|
output_file = etc/nova_apigw.conf.sample
|
|
wrap_width = 79
|
|
namespace = trio2o.nova_apigw
|
|
namespace = trio2o.common
|
|
namespace = trio2o.db
|
|
namespace = oslo.log
|
|
namespace = oslo.messaging
|
|
namespace = oslo.policy
|
|
namespace = oslo.service.periodic_task
|
|
namespace = oslo.service.service
|
|
namespace = oslo.service.sslutils
|
|
namespace = oslo.db
|
|
namespace = oslo.middleware
|
|
namespace = oslo.concurrency
|
|
namespace = keystonemiddleware.auth_token
|