It seems practical to deploy parts of Openstack into separate models.
In theory, given Juju cross model relations AND given the Openstack charms, deploying Openstack in a cross model context seems reasonable.
Despite what I knew to be true, I have given deploying the Openstack components in a CMR fashion at multiple points in time; 1) Juju 2.3 (the dawn of CMR) - just about everything in the deploy seemed broken, 2) Juju 2.4 - far less brokeness, but many things still borked, 3) Juju 2.5 (congrats on the release today!) - juju status green across all models (first time an Openstack deploy has actually settled using CMR), some functionality is broken/missing.
My hope is that @rr-pdl and myself alongside some insight of others, can help get to the bottom of the issues that remain in CMR and thus also in CMR Openstack.
@rr-pdl and myself have attempted to create a POC of CMR Openstack using 3 separate models:
$ juju models Controller: maas-controller Model Cloud/Region Status Machines Cores Access Last connection ryan/ceph-storage pdl-maas available 12 336 admin 3 hours ago ryan/pdl-openstack* pdl-maas available 17 424 admin 16 minutes ago ryan/utilities pdl-maas available 6 104 admin 2 hours ago
$ for model in ryan/ceph-storage ryan/utilities ryan/pdl-openstack; do juju status -m $model --relations; done
Although we are applying the same relations between the same components we would be in a non-CMR style deploy, we are seeing missing ceph config where we would expect to see it amongst other things.
Possibly we can use the space below to enumerate the list of issues we are seeing in the cross model context and their associated logs and resources.