OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sdd message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Groups - Action Item Modified: #0040 Create use case to associate wit...



OASIS Solution Deployment Descriptor (SDD) TC member,

Mr James Falkner has modified this action item.

Number: #0040
Description: Create use case to associate wit...
Owner: Mr James Falkner
Status: Closed
Due: 24 Feb 2006

Comments:
Ms. Julia McCarthy  2006-02-23 00:12 GMT
2.1.6.1  John disagreed. How can you have an upgrade that does not delete the old version? Others say that some software upgrades by installing new version then migrating data from old version. Old version may (or may not) then be deleted. This is a valid scenario, but is it an upgrade? Is there a UC that distinguishes this from 2.1.6? Not now  both list only UC9. Maybe there needs to be? Is this what marketing calls a live upgrade and technicians call a side install?
Motion: remove this until we come up with valid use case.  ACTION ITEM #0040: James: come up with valid use case. (If done by Friday this one will be in next survey, if not it will be removed from next survey.)

Mr James Falkner  2006-02-23 20:10 GMT
Specific use case: 

Customer is running particular customized version of software, including
custom data that was created after the initial install, and custom
configuration tuned for their environment.  This is running either
in a production environment or development environment, with high
availability requirements (i.e. can't be taken down except during
scheduled maintenance periods).

Customer obtains latest version of software, and would like to upgrade
to that version, with the ability to revert to the old version if the
new version does not operate as expected.

Customer installs the new version in a sandbox-type environment (i.e.
different directories/folders, different port numbers, etc) and must
now migrate user data and configuration from old to new version.  Customer
then tests that the new version works as expected, in this sandbox
environment.  If it does not, the current version continues to operate.
If it does, customer selects a convenient time to switch to the new
version, by disabling the old version, changing the new version to use
the standard external port numbers or other end user interfaces, and
finally uninstalls the old version.  This is a sidegrade.

Basically, supporting sidegrades are to 1) reduce the testing burden
by only requiring testing of the migration tools, 2) support revert
when things go wrong, and 3) minimize downtime. 

View Details:
http://www.oasis-open.org/apps/org/workgroup/sdd/members/action_item.php?action_item_id=1260



PLEASE NOTE:  If the above links do not work for you, your email application
may be breaking the link into two pieces.  You may be able to copy and paste
the entire link address into the address field of your web browser.

- OASIS Open Administration


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]