[JIRA] Created: (HUDSON-8374) Launch slave using JNLP

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Created: (HUDSON-8374) Launch slave using JNLP

Kohsuke Kawaguchi
Administrator
Launch slave using JNLP
-----------------------

                 Key: HUDSON-8374
                 URL: http://issues.hudson-ci.org/browse/HUDSON-8374
             Project: Hudson
          Issue Type: Bug
          Components: ec2
    Affects Versions: current
            Reporter: mrdavidlaing
            Assignee: kohsuke
             Fix For: current


I've found that trying to connect to a Windows slave with SSH (using the ec2-sshd project) buggy and very slow compared with windows agents launched with JNLP.

Would it be possible to extend the plugin so that it can cause slaves to start the via JNLP (rather than trying to kickstart things via SSH).

We would just need to find a way to cause the booting AMI to run the following command line:

     javaws http://{hudson.server}/computer/{ec2-name}/slave-agent.jnlp

The command to run with the {hudson.server} and {ec2-name} tokens replaced could perhaps be passed over in the User Data, and then a executed by a start up script?

Seems like a GET http://169.254.169.254/latest/user-data with fetch whatever the instance was started with?
http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/index.html?AESDG-chapter-instancedata.html


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] Updated: (HUDSON-8374) Launch slave using JNLP

Kohsuke Kawaguchi
Administrator

     [ http://issues.hudson-ci.org/browse/HUDSON-8374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

mrdavidlaing updated HUDSON-8374:
---------------------------------

    Issue Type: Improvement  (was: Bug)

> Launch slave using JNLP
> -----------------------
>
>                 Key: HUDSON-8374
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-8374
>             Project: Hudson
>          Issue Type: Improvement
>          Components: ec2
>    Affects Versions: current
>            Reporter: mrdavidlaing
>            Assignee: kohsuke
>             Fix For: current
>
>
> I've found that trying to connect to a Windows slave with SSH (using the ec2-sshd project) buggy and very slow compared with windows agents launched with JNLP.
> Would it be possible to extend the plugin so that it can cause slaves to start the via JNLP (rather than trying to kickstart things via SSH).
> We would just need to find a way to cause the booting AMI to run the following command line:
>      javaws http://{hudson.server}/computer/{ec2-name}/slave-agent.jnlp
> The command to run with the {hudson.server} and {ec2-name} tokens replaced could perhaps be passed over in the User Data, and then a executed by a start up script?
> Seems like a GET http://169.254.169.254/latest/user-data with fetch whatever the instance was started with?
> http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/index.html?AESDG-chapter-instancedata.html

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira