I've brought this up a few times as well Sandor with the monitor example as well! :)
It won't be in 2.0, but its high up the roadmap for Canonical from my discussions with various people there. -------------- Director Meteorite.bi - Saiku Analytics Founder Tel: +44(0)5603641316 (Thanks to the Saiku community we reached our Kickstart <http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/> goal, but you can always help by sponsoring the project <http://www.meteorite.bi/products/saiku/sponsorship>) On 22 July 2016 at 10:45, Sandor Zeestraten <[email protected]> wrote: > That sounds great. Is this on the roadmap for the 2.0 release or a bit > further down the line? > > > Thanks, > Sandor > > On Fri, Jul 22, 2016 at 9:37 AM, Mark Shuttleworth <[email protected]> > wrote: > >> On 22/07/16 09:14, Sandor Zeestraten wrote: >> >> What are your thoughts on cross-model relations? Is this something that >> is compatible with the current design philosophy of Juju 2.0 or am I not >> understanding the model concept? >> >> Let's say you have a bunch of separate models with services that you'd >> like to monitor. Could you have one central monitoring service in a >> dedicated monitoring model that then has relations to the different models? >> Or do you need to deploy a monitoring charm in each model and then >> aggregate the results? >> >> Any thoughts or ideas on how to approach this? >> >> >> Yes, this is exactly what we'd like to do! All the pieces are now in >> place with multi-user multi-model controllers, we just need to connect the >> dots very carefully :) >> >> Mark >> > > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
