Jason Greene wrote:
In the discussion we had at the OA&M meeting with the JON folks, we thought that the AS perspective of management ends with the domain . "Multi-domain" management was something that JON would offer, as a compelling difference. So our admin console, cli, and domain.xml interfaces would be limited to a domain. I still think this is the "right" approach.
Yes, limiting to a domain seems the right approach. But are we sure that a domain should manage a heterogenous group?
Let's put it another way - should embedded jopr manage a heterogenous group? Where is the value addon from JON? How likely is it that you have multiple heterogenous configurations within a company? Isn't that just only a small percentage where you would need that?
Grouping obviously seems to be a important. Where having a heterogenous configuration within a domain, makes this quickly quite big and complex. Splitting that up in smaller "manageable units", which have more in common than "just" a domain name - with clearer boundaries/responsibilities could help to make it easier to understand and reduce overall complexity.