Ok I've updated the model based on last week's discussions. Essentially
there are two changes:
1) I've added back the explicit associaton between Template and Service
-- it became clear in the ongoing discussion last week that most people
agreed that we needed this -- that the template builder should
_explicitly_ include a service when building -- where enable means
"install the packages and puppet scripts -- but not necessarily "enable"
or turn on (that's done at the deployable stage)
2) added a third level for service data. Services are defined in
templates by the template author, enabled (with some config parameters
defined) in deployables by the deployable author, and now I've added a
third: any configuration parameters that are omitted by the deployable
author are defined by the end-user when launching. This is for params
that are unique per instance.
I've attached the updated service AR model file (with more detailed
introductory text on the changes) and a diff from the prior version.
Scott