Openstack Charms and Juju Cross Model Relationship


We are trying to implement different Openstack regions for an end-to-end juju managed openstack installation, however we are stuck in Cross Model Relations and the “readiness” of keystone and openstack-dashboard charms described in this bug .

Given the fact that any direct edit of openstack configuration will be overwritten by juju, can someone suggest a workaround ?


Hi @soumplis, you might want to check out the other thread, Cross Model Relations and Openstack, from last month.


I have already checked it but unfortunately it cannot help / lead to a workaround for keystone and openstack-dashboard relation across models.


Alrighty. Then I’d ask the openstack charmers here or on IRC on openstack-charmers.