Horizon can handle multiple regions by adding AVAILABLE_REGIONS in local_settings.py. And the charm has ability to add regions through relation data.
However, if two keystones are on a separate Juju controller (it's typical in geographically separated multi-region story), we cannot add regions each other. It would be nice if the charm accepts additional region info from outside of the same Juju model/controller.
[templates/ocata/local_settings.py]
# For multiple regions uncomment this configuration, and add (endpoint, title).
#AVAILABLE_REGIONS = [
# ('http://cluster1.example.com:5000/v2.0', 'cluster1'),
# ('http://cluster2.example.com:5000/v2.0', 'cluster2'),
#]
{% if regions|length > 1 -%}
AVAILABLE_REGIONS = [
{% for region in regions -%}
('{{ region.endpoint }}', '{{ region.title }}'),
{% endfor -%}
]
{% endif -%}
OPENSTACK_HOST = "{{ service_host }}"
OPENSTACK_KEYSTONE_DEFAULT_ROLE = "{{ default_role }}"
{% if api_version == "3" -%}
OPENSTACK_KEYSTONE_URL = "{{ service_protocol }}://%s:{{ service_port }}/v3" % OPENSTACK_HOST
OPENSTACK_API_VERSIONS = { "identity": 3, }
OPENSTACK_KEYSTONE_MULTIDOMAIN_SUPPORT = True
OPENSTACK_KEYSTONE_DEFAULT_DOMAIN = "{{ admin_domain_id }}"
{% else -%}
OPENSTACK_KEYSTONE_URL = "{{ service_protocol }}://%s:{{ service_port }}/v2.0" % OPENSTACK_HOST
{% endif -%}
Thank you for your bug report.
In the long term I believe some modeling from the Juju side is required to solve this properly.
Support for cross-model (and indeed cross-controller) relationships is under development and indeed available for testing if you live on the bleeding edge. Have a look here: https:/
As some time will pass before this feature is readily available in stable environments and charms pick up support, could you share your sense of need and urgency for an eventual interim solution through charm configuration?