[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [sdd] 2.1.4.3.1
I think we’re losing the point of the use case in
the wordsmithing. The objective is to have a way in the SDD to take a
captured complete configuration and reuse that configuration easily. So, I propose instead: 2.1.4.3.1 The SDD
specification must support definition of a configuration snapshot. And that we add to the section on solution instance
variability more specific requirements about how the SDD can define the use of
a configuration snapshot. 2.4.2 is somewhat related, if we can decide
what if anything differentiates a configuration snapshot from a “response
file”. I think that we might be able to simplify 2.4.9, because the
first part of the requirement – the ability (to capture - runtime /
tooling function, not a SDD requirement) and store (SDD requirement for
definition of configuration snapshot?) relevant parameters and selections
becomes a duplicate of 2.1.4.3.1, leaving instead the requirement that a configuration
snapshot can be identified for use in lifecycle operations on the same instance,
on another deployed instance, or in a new deployment. 2.4.9 The
SDD specification must support the use of a configuration snapshot in lifecycle
operations on a new or existing instance. Regards, Debra From: Robert
Dickau [mailto:rdickau@macrovision.com] A vote
for shorter Option 2. From: Julia
McCarthy [mailto:julia@us.ibm.com] Option 1) 2.1.4.3.1 The SDD specification must
support the ability for the author to define information about a snapshot
configuration. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]