SDD Implementation

Two sets of tools Authoring tools – SDD editor plug-in (not implemented) – Build time generator Runtime tools – Core runtime (analysis/resolution) – Operator – Registrar

Authoring tools Example RE Flow Build Systems DLL SO EXE JAR Packaging Systems Install Developer MSI ZIP RPM Build systems produce binary files from source. Install developers monitor build outputs, create installation code and push the installation code to packaging systems. Packaging systems create “artifacts” which can be used to perform installation.

Authoring tools Interface to BTG RDBMS MSI ZIP RPM SDD Data and/or artifacts Readers Build Time Generator SDD SPD Custom readers interrogate artifacts such as MSI or RPM files and normalizes that data as input to the BTG. The BTG then generates and aggregates SDDs based upon that data and the customizable “rules” within the BTG’s aggregator component.

Runtime Profile Runtime Artifact Handlers SDD SPD Runtime inputs Bootstrap Model builder Change resolver Handler Orchestrator Operator Registrar Install Uninstall SML MDR Other GUI CLI The bootstrap unpacks and initializes the runtime including the orchestrator and user interface. The model builder fires to un-marshall SDD and SPD to an internal object model. The change resolver then “walks” the model firing appropriate core or custom resolvers per resource types as defined in the profile. As operations come into scope the operator fires operations. Once operations are completed, the registrar registers the change in an SML MDR or other registry format. * This process is iterative and managed by the orchestrator.

Demos Build time generator Runtime w/ COSMOS example Q & A