Details
-
Bug
-
Status: Resolved (View Workflow)
-
Blocker
-
Resolution: Fixed
-
None
-
ubuntu amd64 e.g. alestic ami-da0cf8b3
ec2 plugin v 1.9
Description
i can manually create slaves, but they are never created automatically.
Attachments
Activity
Integrated in 
plugins_ec2 #58
[FIXED JENKINS-7883] Stopped (as opposed to terminated) slaves are counted against the active instance count for the purpose of launching; can prevent launching of instances (Revision fb48500653bf851b59022b61ed3eb86ac60ab07f)
Result = SUCCESS
francisu :
Files :
- src/main/java/hudson/plugins/ec2/EC2Cloud.java
akostadinov
added a comment - It's important to count only jenkins instances because otherwise account needs to be dedicated to jenkins. Perhaps make it an option with default value whatever you want but have this capability.
akostadinov
added a comment - It's important to count only jenkins instances because otherwise account needs to be dedicated to jenkins. Perhaps make it an option with default value whatever you want but have this capability. 
Francis Upton
added a comment - @akostadinov - please open a new JIRA requesting that, it's really not part of this issue.
Francis Upton
added a comment - @akostadinov - please open a new JIRA requesting that, it's really not part of this issue. 
max allan
added a comment - Agree with @akostadinov. Our VPC is used by developers so we have a completely variable number of instances. Currently about 120 and we only really want a handful of Jenkins instances. But if someone decides they need a new dev cluster, we'll have 130 in a few minutes. Or if they decide they don't need a cluster we'll be down to 110. So how can I set my cap?
If someone tries to start a load of builds during the day, they could exhaust the free IP addresses / hit EC2's limit on instances without realising if we disable the cap completely.
If a new ticket was raised, please let me know the ID so I can +1 it! If I don't hear anything I'll try to remember to raise one soon.
max allan
added a comment - Agree with @akostadinov. Our VPC is used by developers so we have a completely variable number of instances. Currently about 120 and we only really want a handful of Jenkins instances. But if someone decides they need a new dev cluster, we'll have 130 in a few minutes. Or if they decide they don't need a cluster we'll be down to 110. So how can I set my cap?
If someone tries to start a load of builds during the day, they could exhaust the free IP addresses / hit EC2's limit on instances without realising if we disable the cap completely.
If a new ticket was raised, please let me know the ID so I can +1 it! If I don't hear anything I'll try to remember to raise one soon. 
Code changed in jenkins
User: Francis Upton IV
Path:
src/main/java/hudson/plugins/ec2/EC2Cloud.java
http://jenkins-ci.org/commit/ec2-plugin/fb48500653bf851b59022b61ed3eb86ac60ab07f
Log:
[FIXED JENKINS-7883] Stopped (as opposed to terminated) slaves are counted against the active instance count for the purpose of launching; can prevent launching of instances