Hello Bill,
Thank you very much for the reply. Regarding your comments:
"Why wouldn't create-instance be usable to create additional instances
on that node?"
"Right, that shouldn't be the case. If that's the way it works now,
seems like something is wrong. "
It doesn't work such way now, but according to Joe it will work such way
at the future. Joe wrote in the bug
https://glassfish.dev.java.net/issues/show_bug.cgi?id=12846
"The scenario you described is not supported (using an auto-created-node
that was
created via create-local-instance with create-instance over SSH). We
have a bug
(issue 12694) for better detecting this condition. Once that is fixed it
will
always fail with a better error message.
For now please use only nodes created with create-node-ssh (or the localhost
node) with create-instance."
Also I forgot to mention that localhost node can not be deleted, i.e. we
have one more difference.
Personally, I would prefer that all nodes will be equal, independently
how they were created, like it was in v2. for nodeagent.
And the last, I don't understand why to the names of some remote
commands was add "ssh" and for other not, they all use ssh.
Thank you,
Elena
Bill Shannon wrote:
> Elena Asarina wrote on 08/04/2010 05:32 PM:
>> All,
>>
>> I would like to discuss the nodes creations in v3.1. I can count at
>> least four different types of nodes creations:
>> 1) Preconfigured node localhost on DAS machine.
>> 2) A default node with machine name that was created on remote
>> machine via create-local-instance.
>> 3) create-node-config
>> 4) create-node-ssh.
>>
>> The way how nodes were created, affected how instances later can be
>> created for that node. It means:
>> 1) if a node was created using create-node-config, then only
>> create-local-instance supposedly can be used (not sure only for first
>> instance for this node or for all instances for this node);
>
> I don't see why that should be so.
>
> You should be able to do a create-instance referencing that node,
> although it will be an "offline config" because it won't do anything
> to set up the remote machine. A later create-local-instance would be
> required on the remote machine.
>
>> 2) if a node was created on remote machine via
>> create-local-instance, then according to Joe, for that node the
>> instances always have to be created using create-local-instance command.
>
> Why wouldn't create-instance be usable to create additional instances
> on that node?
>
>> I believe that this picture is very confusing. For example, for node
>> that was created on remote machine via create-local-instance, how
>> users can remember that for that particular node instances can be
>> created only locally.
>
> Right, that shouldn't be the case. If that's the way it works now,
> seems like something is wrong.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>