Hi, Bobby.
Do you have equally good instructions for testing upgrade from 3.0.1
to 3.1?
I blindly tried to follow these same instructions but got into
trouble, I think because when I copied the 3.0.1 domain1 into the 3.1
domain1 area i pulled along the felix cache.
Anyway, I can figure this out but if you had a cheat sheet already
prepared I would take advantage of it.
Thanks.
- Tim
On Nov 3, 2010, at 7:47 PM, Bobby Bissett wrote:
> To module leads,
>
> I need your help doing some basic, one-time upgrade testing (though
> you're welcome to do more!). Since each module is responsible for
> its part of upgrade, you're the person who knows what to test.
> Without this, bugs in your area may not be found until it's too late
> to fix them. This shouldn't take much of your time, possibly half an
> hour (unless you don't have some way already to test your area), and
> it would be best if you could do this before next Monday evening,
> before the next promotion. We're running out of time to get a usable
> promotion for testing.
>
> Here are the steps:
>
> 1. (5-10 minutes) Download and install v2.1.1, developer profile,
> from https://glassfish.dev.java.net/downloads/v2.1.1-final.html
> 1a. The installer (the "java -jar ...." step) can take a while to
> run: ~4 minutes on my Mac before it starts unzipping the files.
> 1b. Before running the "ant -f setup*" step, zip up your glassfish
> dir. This will save you some time later.
>
> 2. Start up the server and do *something* related to your area:
> deploy an app, create resources, change settings, whatever. You're
> the expert in your area.
>
> 3. Stop the server.
> 3a. If you did anything in step 2 that involved a database, keep
> that same database running.
>
> 4. (1-2 minutes) Upgrade your v2.1.1 domain to your 3.1 build. For
> your copy/paste ease (edit of course for Windows), do the following:
> 4a. cd <path>/glassfish3/glassfish/bin
> 4b. rm -rf ../domains/domain1
> 4c. cp -R <path to v2>/glassfish/domains/domain1 ../domains/
> 4d. rm -rf ../domains/domain1/logs/* (not necessary, but will make
> it easier to read the log)
> 4e. ./asadmin start-domain --upgrade
> 4.f Watch the output of the upgrade step for any warning/severe
> level messages. There will be at least 3. If you don't see them,
> you're not paying attention.
>
> 5. Start up the 3.1 server. To really make sure you see all the
> output, "./asadmin start-domain --upgrade"
>
> 6. Now test whatever you did in step 2 to see if it's still working
> in the 3.1 server. Again, it's your discretion, but you're better
> off finding the bugs now.
>
> 7. If there were issues, file them and add the "3.1-upgrade"
> keyword. Also please add me (bbissett) to the cc list. Current
> issues: https://glassfish.dev.java.net/issues/buglist.cgi?keywords=3.1-upgrade
> If everything worked, send me or the dev list a short email and just
> tell me what you tested.
>
> 8. Repeat the procedure with a cluster. Now that you've already done
> this once, it should take ~10 minutes to do it again. The steps are
> all here, and you've done 2/3 of them already. Just replace steps 3
> and 7 in the wiki with whatever you already did:
> http://wikis.sun.com/display/GlassFish/V3.1ClusterUpgradeExample
>
> Currently there is no automated test for a cluster upgrade, but I'm
> working on that now. If you want to add what you've done to the dev
> profile upgrade test, you'll find it in the admin cli tests.
> Obviously it's a good idea to add a dev test if you can -- otherwise
> someone else might break what you just tested and you'll end up
> getting the bug first. More info:
> http://wikis.sun.com/display/GlassFish/AdminTests
>
> Thanks,
> Bobby
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>