Talk:COSMOS Bug Design 209248

Do we have a complete list of the Muse annotations? It would be good if we had an “Management Annotations Reference Page” on the wiki--a glossary of annotations if you will. It would be good to indicate the annotations that affect an external interface, e.g. “ManagedResourceCapability” vs. one that supports the framework “Autowire”. Can we java doc this and just use that?

Why does the ManagedResourceCapability need to know if it’s composable or not? There could be situations where the capability can be used in either way. DataBroker may be an example. The DataBroker is essentially composing in a custom DataBroker capability with Service Groups. However, there could be another DataBroker that does not use service groups. Given this, why do we have to know? Why not just always make it composable?

Will the Muse resource router implement the ComposableManagedCapabilitySet interface? It might be a good fit to introduce an annotated router that does the composition.

Will you elaborate on the “singleton requirement for CMDBf”? I’m not sure I’m following what you are referring to. We will have more than one MDR in the systems, so making that a singleton does not make sense? I suppose it’s conceivable that we would have multiple federating CMDBs in a system as well (although this does seem much less likely).

Is there a way to get to the Muse deployment descriptor? Are there options available in this that we might want to expose. Maybe a combination of an autowire target and a factory....

When & where do the binding rules apply? Are they used by the factory?

Can we follow on this doc with a very simple example of the things that we talk about?