![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Francis Upton
|
|
Components:
|
ec2, plugin |
|
Created:
|
03/Aug/13 11:24 AM
|
|
Description:
|
From help message in EC2Cloud Configuration, I need to let spot instance notify Jenkins master know this slave alive after it is available.
As My AMI is based on CentOS, I cannot take the script it mentioned.
Here is my understanding on the callback process.
Jenkins Master does the spot instance request also with a default parameter in instance userdata, like:
JENKINS_URL=http://1.1.1.1:8080/&SLAVE_NAME=XXXXXXX&USER_DATA=
Then the callback script will first download the "slave.jar" and use it to notify Jenkins Master know this slave alive:
java -jar slave.jar -jnlpUrl http://1.1.1.1:8080/XXXXXXX/slave-agent.jnlp
However, due to my Jenkins master deployed internally with no public access, so it makes Jenkins master considers this slave not ready.
I also try to run these commands into an internal machine and wish Maser could let it go. But with 403 forbidden response.
Could you please help me on this issue?
I feel this deployment is also quite common.
Thanks
Henry
|
|
Environment:
|
Jenkins 1.525, Amazon EC2 plugin v1.19-unreleased (last commit: #1e009adfa3)
|
|
Project:
|
Jenkins
|
|
Labels:
|
master
spot
instance
ec2-plugin
internal
notification
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Henry Huang
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
