Bravo, Elena,
This is a great list. I agree completely that this needs to be covered
in the docs (in whatever section). As I've been setting up a cluster do
to scalability testing with SSH, your list concisely summarized the
issues that I faced.
Thanks.
Tom
On 8/11/2010 8:34 PM, Paul M Davies (Oracle) wrote:
> Hi Elena,
>
> No, please do not open a doc bug. Instead, please review the SSH
> provisioning doc plan
> <http://wikis.sun.com/display/GlassFish/GlassFishV3.1SSHProvisioningDocPlan>
> and if you think that any topics that should be covered are missing
> from this plan, please add a comment to the plan stating which
> additional topics should be covered.
>
> I would say that most of the issues that you raised should be
> addressed not in a troubleshooting section but in a section that
> clearly explains the use cases and which commands to use in these use
> cases. The aim of this documentation should be to keep the user out of
> trouble in the first place. That's certainly what I'm planning to do.
> For example, you ask how to upgrade an object to use the "remote"
> command. This use case is covered in the task "Upgrade a non-SSH node
> to an SSH node" which, as you'll see in the plan, is planned to be
> added to Chapter 8, Configuring GlassFish Server Nodes in the HA Admin
> Guide.
>
> Regards,
> -Paul
>
>
>>
>> I would like to start a discussion about the content of the
>> troubleshooting section of our docs.
>>
>> Answering on the question of my colleges regarding cluster/instances
>> configuration, I can see the same pattern of the questions/issues.
>> Probably our customers will have the same questions. I will try to
>> summarize the questions:
>> 1) How to setup SSH without password. I can say that on Linux,
>> Solaris and Mac it is an easy procedure, but on windows not. I was
>> able to setup ssh without password only on two machines, only under
>> Administrator id and with a work around. I believe we need to
>> provide a reliable windows procedure.
>> 2) Just to be able to run remote commands like asadmin
>> create-node-ssh, asadmin start-instance, asadmin stop-instance, ssh
>> without password has to be preconfigured.
>> 3) There are "local" and "remote" commands. If an object, for example
>> a node, was created using "local" command, the remote commands can
>> not be executed against this object, unless it was upgraded to the
>> "remote" object. (How?). I think it has to explained clearly with
>> wrong and correct examples and error messages.
>> 4) Any remote command needs in java on the remote machine. It will
>> take whatever there, on our Solaris, Linux machines it just
>> /usr/bin/java. Usually /usr/bin/java is linked with jdk 4 or 5. So
>> there will be error messages (for jdk4 a bad error message). Users
>> have to be advised to execute from machine A: ssh <machine B> java
>> -version. And if it is not JDK 6, change it, for example, recreate
>> /usr/bin/java link pointing to the suitable java.
>> 5) If ssh without password was created, before any asadmin command
>> that use ssh would be executed, ssh manually with the machine name
>> that would be used, to put info about the machine in known_hosts.
>> For example, if from machine A ssh <machine B without domain>, but
>> then will try execute asadmin command using a full machine name with
>> domain, it would not work.
>>
>> It is just a start.
>>
>> Do you want me to open a doc bug that can be updated with more
>> information?
>>
>> Thank you,
>>
>> Elena
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>
>
>
> --
>
>
>
> Oracle <http://www.oracle.com>
> Paul Davies| Principal Technical Writer| +1.408.276.3413
> Oracle GlassFish Server Documentation
> 4140 Network Circle, Santa Clara CA 95054, USA
>
> Green Oracle <http://www.oracle.com/commitment> Oracle is committed
> to developing practices and products that help protect the environment
>
>