Anything to make this sort of stuff easier/more understandable has my
vote.
The creation of instances seem to be SSH-centric to me.
Yesterday I tried to create an instance on a different host and it was
pretty painful.
Is there a simple step-by-step for doing this basic thing?
QE/QA -- Please try out some scenarios...
On 8/25/2010 11:33 AM, Tom Mueller wrote:
> For the offline/manual sync usage, where SSH is not setup between
> nodes, the method for creating a cluster would be this:
>
> create-node-config --nodehost h1 n-h1
> create-node-config --nodehost h2 n-h2
> create-cluster c1
> create-instance --cluster c1 --node n-h1 i1
> (command prints failure message)
> create-instance --cluster c1 --node n-h2 i2
> (command prints failure message)
> export-sync-bundle --target c1 --retrieve=true c1.zip
> (copy c1.zip to h1 and h2)
> on h1:
> import-sync-bundle --file c1.zip i1
> on h2:
> import-sync-bundle --file c1.zip i2
>
> At this point the instances can be started.
>
> What I'm wondering is whether we should have an option for
> create-instance, something like --dasonly or --offline, that would
> tell create-instance to only do the part of the work that is for the
> DAS because the expectation is to use manual sync later or an explicit
> create-local-instance later. This would allow the create-instance to
> succeed and print out the port assignments in this case.
>
> Currently, the create-instance fails, and it doesn't print out the
> port assignments.
>
> Thoughts?
> Tom
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>
--
Byron Nevins - Oracle Corporation
Home: 650-359-1290
Cell: 650-784-4123
Sierra: 209-295-2188