bc3c4b1699
1. What is the problem? Now Keystone uses uwsgi with proxy[1], and this is the default mode in DevStack. In this case, the original URL with 5000/35357 port can no longer be accessed, this change will lead to Trio2o gate/check test always failure if no adaption is made in Trio2o configuration. 2. What is the solution to the problem? Change Keystone public URL Trio2o uses from http://host:5000/v3 to http://host/identity and change Keystone admin URL Trio2o uses from http://host:35357/v3 to http://host/identity For tempest test, change http://host:5000/v2.0/ to http://host/identity and change identity version from 2 to 3 in post_test_hook.sh. In post_test_hook.sh, add admin_domain_name option. This patch also fixes a mistake which was hidden before this Keystone change. While generating Trio2o apache configuration file in our DevStack script, TRIO2O_BIN in the template is not replaced by the real value. So the directory access right is not correctly granted. Before this Keystone change, Keystone apache configuration file will grant right on the same directory, so we didn't notice this problem. 3. What features need to be implemented to the Trio2o to realize the solution? N/A [1] https://github.com/openstack-dev/devstack/commit/ 6ed53156b6198e69d59d1cf3a3497e96f5b7a870 [2] https://github.com/openstack/neutron/commit/ 46d1a890e700dfa6e921387569f87f793ca4e8e9 Change-Id: I4e1e38b1c07f453fcf2cfed39a16342f235c06b1
Trio2o
The Trio2o provides an OpenStack API gateway to allow multiple OpenStack instances, spanning in one site or multiple sites or in hybrid cloud, to be managed as a single OpenStack cloud.
The Trio2o and these managed OpenStack instances will use shared KeyStone (with centralized or distributed deployment) or federated KeyStones for identity management.
The Trio2o presents one big region to the end user in KeyStone. And each OpenStack instance called a pod is a sub-region of the Trio2o in KeyStone, and usually not visible to end user directly.
The Trio2o acts as OpenStack API gateway, can handle OpenStack API calls, schedule one proper OpenStack instance if needed during the API calls handling, forward the API calls to the appropriate OpenStack instance.
The end user can see avaialbility zone(AZ) and use AZ to provision VM, Volume, through the Trio2o. One AZ can include many OpenStack instances, the Trio2o can schedule and bind OpenStack instance for the tenant inside one AZ. A tenant's resources could be bound to multiple specific bottom OpenStack instances in one or multiple AZs automatically.
- Free software: Apache license
- Design documentation: Trio2o Design Blueprint
- Wiki: https://wiki.openstack.org/wiki/trio2o
- Installation with DevStack: https://github.com/openstack/trio2o/blob/master/doc/source/
- Trio2o Admin API documentation: https://github.com/openstack/trio2o/blob/master/doc/source/api_v1.rst
- Source: https://github.com/openstack/trio2o
- Bugs: http://bugs.launchpad.net/trio2o
- Blueprints: https://launchpad.net/trio2o