Default Node Executor

[Shaun Lim]

Hi everyone,

I'm doing some research and testing into Rundeck in a mixed environment comprising both Linux/Unix and Windows servers. As I understand it, we need to create Projects and define the default node executor. I'm not sure how this will work in a mixed environment but I came across some article somewhere on the Internet where there was an example of a resources.xml with a 'node-executor' attribute although I am not certain if it is actually a recognized attribute. The example I am using is as below:

<?xml version="1.0" encoding="UTF-8"?>

<project>

  <node name="esx01.democorp.com" description="VMware ESXi" tags="" hostname="esx01.democorp.com" node-executor="SSH" ssh-password-storage-path="/var/rundeck/projects/testing/key/

esx01.pem" osArch="amd64" osFamily="unix" osName="VMware ESXi" osVersion="6.5.0-5969303" username="root"/>

  <node name="rundeck.democorp.com" description="Rundeck server node" tags="" hostname="rundeck.democorp.com" node-executor="ssh" osArch="amd64" osFamily="unix" osName="Linux" osV

ersion="4.4.0-93-generic" username="rundeck"/>

  <node name="ad01.democorp.com" description="Active Directory" tags="" hostname="ad01.democorp.com" osArch="x86_64" osFamily="windows" osName="Microsoft Windows Server 2016 Stand

ard" osVersion="10.0.14393" username="pent...@democorp.com" />

  <node name="me01.democorp.com" description="Service Desk" tags="" hostname="me01.democorp.com" osArch="x86_64" osFamily="windows" osName="Microsoft Windows Server 2016 Standard

" osVersion="10.0.14393" username="pent...@democorp.com" />

</project>

When I tested running a command directly on the node (esx01 in this example), I get the error as below:

15:01:41	192.168.10.13	Failed dispatching to node esx01.democorp.com: com.dtolabs.rundeck.core.CoreException: No matching plugin found provider: SSH for Service: NodeExecutor
15:01:41		Execution failed: 20 in project testing: [Workflow result: , step failures: {1=Dispatch failed on 1 nodes: [esx01.democorp.com: Unknown: com.dtolabs.rundeck.core.CoreException: No matching plugin found provider: SSH for Service: NodeExecutor]}, Node failures: {esx01.democorp.com=[Unknown: com.dtolabs.rundeck.core.CoreException: No matching plugin found provider: SSH for Service: NodeExecutor]}, status: failed]

However, when I create a job with a single step in the form of a command, I get a different error instead:

01:36:46	192.168.10.13	1. Script	Failed dispatching to node esx01.democorp.com: Configuration error: SSH Keyfile does not exist: /var/lib/rundeck/.ssh/id_rsa
01:36:46			Execution failed: 19 in project testing: [Workflow result: , step failures: {1=NodeDispatchFailure: Failed dispatching to node esx01.democorp.com: Configuration error: SSH Keyfile does not exist: /var/lib/rundeck/.ssh/id_rsa}, Node failures: {esx01.democorp.com=[ConfigurationFailure: Configuration error: SSH Keyfile does not exist: /var/lib/rundeck/.ssh/id_rsa]}, flow control: Continue, status: failed]

So I guess I am wondering if the node-executor attribute in the xml is supposed to be recognized and honored since these two errors seem to contradict one another. In the first instance, it does not appear to recognize it but in the second, it seems to be complaining about an SSH keyfile so I will assume that it picked it up there. For the record, I have set the default node executor for this project to use Winrm.

[Alex Honor]

Hi Shaun,

Yes, you are correct about the node-executor attribute. Nodes can define their own but if not defined will default to the project default. Go the to the Plugins List page, to see the list of installed node-executors in your instance. 
The SSH one is called "jsch-ssh" while the winrm is called, "overthere-winrm". That same page will tell you about config properties you can set to define things like key path or password among other settings.

Thanks

On Sunday, December 10, 2017 at 8:46:36 PM UTC-8, Shaun Lim wrote:

Hi everyone,

I'm doing some research and testing into Rundeck in a mixed environment comprising both Linux/Unix and Windows servers. As I understand it, we need to create Projects and define the default node executor. I'm not sure how this will work in a mixed environment but I came across some article somewhere on the Internet where there was an example of a resources.xml with a 'node-executor' attribute although I am not certain if it is actually a recognized attribute. The example I am using is as below:

<?xml version="1.0" encoding="UTF-8"?>

<project>

  <node name="esx01.democorp.com" description="VMware ESXi" tags="" hostname="esx01.democorp.com" node-executor="SSH" ssh-password-storage-path="/var/rundeck/projects/testing/key/

esx01.pem" osArch="amd64" osFamily="unix" osName="VMware ESXi" osVersion="6.5.0-5969303" username="root"/>

  <node name="rundeck.democorp.com" description="Rundeck server node" tags="" hostname="rundeck.democorp.com" node-executor="ssh" osArch="amd64" osFamily="unix" osName="Linux" osV

ersion="4.4.0-93-generic" username="rundeck"/>

  <node name="ad01.democorp.com" description="Active Directory" tags="" hostname="ad01.democorp.com" osArch="x86_64" osFamily="windows" osName="Microsoft Windows Server 2016 Stand

ard" osVersion="10.0.14393" username="pentadbir@democorp.com" />

  <node name="me01.democorp.com" description="Service Desk" tags="" hostname="me01.democorp.com" osArch="x86_64" osFamily="windows" osName="Microsoft Windows Server 2016 Standard

" osVersion="10.0.14393" username="pentadbir@democorp.com" />

</project>

[Shaun Lim]

Hi Alex,

Thanks for the tip. I did not notice the details on this page before, I only looked at the plugin pages directly on the web. My bad but that does clarify quite a bit. I'll test this out further.

Regards,

Shaun

On Tuesday, 12 December 2017 02:59:09 UTC+11, Alex Honor wrote:

Hi Shaun,

Yes, you are correct about the node-executor attribute. Nodes can define their own but if not defined will default to the project default. Go the to the Plugins List page, to see the list of installed node-executors in your instance. 
The SSH one is called "jsch-ssh" while the winrm is called, "overthere-winrm". That same page will tell you about config properties you can set to define things like key path or password among other settings.

Thanks

On Sunday, December 10, 2017 at 8:46:36 PM UTC-8, Shaun Lim wrote:

Hi everyone,

I'm doing some research and testing into Rundeck in a mixed environment comprising both Linux/Unix and Windows servers. As I understand it, we need to create Projects and define the default node executor. I'm not sure how this will work in a mixed environment but I came across some article somewhere on the Internet where there was an example of a resources.xml with a 'node-executor' attribute although I am not certain if it is actually a recognized attribute. The example I am using is as below:

<?xml version="1.0" encoding="UTF-8"?>

<project>

  <node name="esx01.democorp.com" description="VMware ESXi" tags="" hostname="esx01.democorp.com" node-executor="SSH" ssh-password-storage-path="/var/rundeck/projects/testing/key/

esx01.pem" osArch="amd64" osFamily="unix" osName="VMware ESXi" osVersion="6.5.0-5969303" username="root"/>

  <node name="rundeck.democorp.com" description="Rundeck server node" tags="" hostname="rundeck.democorp.com" node-executor="ssh" osArch="amd64" osFamily="unix" osName="Linux" osV

ersion="4.4.0-93-generic" username="rundeck"/>

  <node name="ad01.democorp.com" description="Active Directory" tags="" hostname="ad01.democorp.com" osArch="x86_64" osFamily="windows" osName="Microsoft Windows Server 2016 Stand

ard" osVersion="10.0.14393" username="pent...@democorp.com" />

  <node name="me01.democorp.com" description="Service Desk" tags="" hostname="me01.democorp.com" osArch="x86_64" osFamily="windows" osName="Microsoft Windows Server 2016 Standard

" osVersion="10.0.14393" username="pent...@democorp.com" />

</project>