Model level subordinates

Bug #1337318 reported by Kapil Thangavelu on 2014-07-03
34
This bug affects 5 people
Affects Status Importance Assigned to Milestone
juju
Wishlist
Unassigned
juju-core
Medium
Unassigned

Bug Description

Several of our IS models need on the order of 6-8 subordinates installed on every machine (some just for baremetal) as part of every model. Rather than being forced to relate the sub to everything. It would be better to allow for specifying this subordinate is a model level subordinate so that its related to all applications in the model. ie. generic use cases of logging, monitoring, ntp etc. all would want for this as subordinates typically represent cross cutting policy concerns across a model.

James Troup (elmo) on 2014-07-03
tags: added: canonical-is
tags: added: usability
Curtis Hovey (sinzui) on 2014-07-03
Changed in juju-core:
status: New → Triaged
importance: Undecided → Medium
tags: added: feature subordinate
Changed in juju-core:
status: Triaged → Won't Fix
Haw Loeung (hloeung) wrote :

In the multi-model world, I think we'd be interested in model-level.

summary: - Environment level subordinates
+ Model level subordinates
description: updated
Changed in juju:
status: New → Triaged
importance: Undecided → Wishlist
Haw Loeung (hloeung) wrote :

Our services all include the following subordinates:

basenode (IS specific bits like timezone etc.)
nrpe (monitoring)
hp-health (monitoring)
landscape-client
ntp
ksplice
(and a couple of others)

Haw Loeung (hloeung) wrote :

I think this also doesn't apply to IS, as other teams also have their own standard subordinates rolled out model-wide. For example, "oops".

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers