Cross-model integration

See also:

Before juju v.3.0 , ‘cross-model integrations’ (CMI) were called ‘cross-model relations’ (CMR). The ‘relation’ terminology is still around in commands such as remove-relation or options such as juju status --relations .

In Juju, a cross-model integration (CMI) is an integration that works across models, even across multiple controllers and clouds. Cross-model integrations enable, for example, scenarios where your databases are hosted on bare metal, to take advantage of I/O performance, and your applications live within Kubernetes, to take advantage of scalability and application density.

A cross-model integration between two models, say Model A and Model B, can be:

  • On the same cloud where the two models have the same controller, or
  • On the same cloud, but with separate controllers, or
  • On different clouds, where the controllers are also inherently separate (since a controller does not work with models across multiple clouds).

These three cases are illustrated below. The red line denotes the cross-model integration in each case.


Last updated a month ago.