Just curious. Would this make sense as an asadmin local subcommand
rather than introducing a new script? We already have a
"verify-domain-xml" command. We could have "verify-multicast".
Tom
On 7/28/2010 8:34 AM, Bobby Bissett wrote:
> Howdy,
>
> One of the deliverables for GMS is a tool for testing that multicast
> is working on the subnet where a cluster will run. I've implemented
> this as a tool inside shoal-gms-impl.jar, so we don't need to add
> another jar to the modules dir. But I do need to add the script/batch
> file to the workspace somewhere for running the tool.
>
> I was thinking of adding a new module v3/cluster/cluster-scripts to
> hold these (similar to v3/extras/upgrade/upgrade-scripts). Any
> objections/suggestions?
>
> Before you ask:
> 1) Why can't the scripts be in the shoal workspace? They're specific
> to GF, as in having a reference to
> $AS_INSTALL/modules/shoal-gms-impl.jar. So they could be in the shoal
> workspace, but they wouldn't make any sense there.
> 2) Why not v3/cluster/gms-scripts? I don't feel strongly about this,
> but the one script I want to add now is specifically for testing if
> multicast is available. While GMS relies on multicast, there's nothing
> about multicast that is gms-specific.
> 3) What's the script called? I was thinking mcastvalidator[.bat]. Am
> open to suggestions of course.
>
> 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
>