trio2o/trio2o
zhangxiaohan d2814db497 Trio2o work with the new OpenStack version
1. What is the problem?

Since trio2o stops updating after version M, it is adjusted accordingly
to adapt to the latest version openstack.

2. What is the solution to the problem?
Adjust the new compute and volume endpoint.
Add the server_external_event forward and os-service fetch.
Some bugs were fixed.

Change-Id: I9d0a1deb011a33750985e88c72fe4fad71a32be2
Signed-off-by: zhang xiaohan <zhangxiaohan@szzt.com.cn>
Co-Authored-By: tangzhuo <ztang@hnu.edu.cn>
2018-08-29 17:34:00 +08:00
..
api The framework of dynamic pod binding 2017-04-12 15:01:52 +08:00
cinder_apigw Trio2o work with the new OpenStack version 2018-08-29 17:34:00 +08:00
cmd [urgent]Adapt new Keystone URL 2017-05-15 19:08:53 +08:00
common Trio2o work with the new OpenStack version 2018-08-29 17:34:00 +08:00
db The framework of dynamic pod binding 2017-04-12 15:01:52 +08:00
nova_apigw Trio2o work with the new OpenStack version 2018-08-29 17:34:00 +08:00
tempestplugin Trio2o work with the new OpenStack version 2018-08-29 17:34:00 +08:00
tests Trio2o work with the new OpenStack version 2018-08-29 17:34:00 +08:00
xjob Remove networking related code from the Trio2o 2016-11-14 02:12:48 -05:00
__init__.py Remove networking related code from the Trio2o 2016-11-14 02:12:48 -05:00