Elena Asarina wrote on 08/12/10 12:13 PM:
> Hello Bill,
>
> Any node when it would be created will be marked in domain.xml either
> SSH or CONFIG
>
> And I think that we need to explain clearly that if a node was marked
> CONFIG, then it doesn't have ssh info,
Yes, although hopefully that's clear based on the fact that you created
it without using the create-node-ssh command and without supplying any
ssh info.
> correspondingly an instance for
> that node can be created only locally.
No, you should be able to login to the remote machine and use
create-local-instance.
> And then only local commands can
> be executed against instances that belong to this node. But if not local
> command would be executed, as I understood, please correct me, if I'm
> wrong, for example stop-instance or start-instance, has to be seen an
> error message. If so, this example with an error message has to be
> provided.
Yes, you should get an error if you try commands that require ssh support
and ssh hasn't been configured. I believe stop-instance should work since
it can talk directly to the instance to ask it to stop. start-instance
won't work, however.
> Unfortunately I don't see a consistent behavior in this area.
> For example, I've just created on Windows a node using
> create-node-config, then create-local-instance, then
> start-local-instance. But then can execute stop-instance/start-instance
> against such instance without any issues.
>
> It is it an expected behavior or not?
stop-instance should work.
I wouldn't expect start-instance to work.
Is the node a different machine than the DAS machine?