Are we really bothering with CCC for V3?
Seems to me that it's such a major overhaul that simply documenting
the changes en-masse might be better...
Lloyd
On Mar 3, 2008, at 12:13 PM, Jennifer Chou wrote:
> Hi,
>
> I need to create an issue for changing start-database/stop-database
> from local to remote for ccc with the following info: Anything
> else I should add?
> which interfaces are being changed
> asadmin start-database, asadmin stop-database
> reason for change
> ease of use: allow the user to start database from a different
> machine.
> impact on other functional groups
> SQE will need to update test scripts.
> Docs will need to be updated.
> CTS may need to be updated
> Dev will need to change start/stop-database from a local to remote
> command. The server will need to start the process in a smart way
> so there are no deadlocks.
> customer impact and risks
> Scripts that call start-database before start-domain will not have
> the database started.
> migration for people who use the existing interface
> Change scripts to reverse order of start-database, start-domain.
> blurb for compatibility guide
> In V2 start-database and stop-database worked with or without the
> application server running. For V3 to allow for starting and
> stopping the database from a remote machine, the start-database and
> stop-database commands will only work on a running application server.
>
> Jennifer
>
---
Lloyd L Chambers
lloyd.chambers_at_sun.com
Sun Microsystems, Inc