[JIRA] [core] (JENKINS-35174) Modify cloud API when several shared clouds are defined with the same label

2016-05-27 Thread elliot.wei...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Elliot Weiser commented on  JENKINS-35174 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Modify cloud API when several shared clouds are defined with the same label  
 
 
 
 
 
 
 
 
 
 
Thanks for opening this Félix Belzunce Arcos. Distributing load across clouds would be very desirable. To your point about "expensive" versus "cheap" clouds, there are a number of load balancing algorithms that are potentially worth pursuing (all of which have their merits): 
 

Round Robin
 

Weighted Balance
 

Least Used
 

Least (Current) Load
 
 
I'll try to poke at the source code in my spare time to see what's feasible. I have a picture in my head of how it could work. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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/d/optout.


[JIRA] [core] (JENKINS-35174) Modify cloud API when several shared clouds are defined with the same label

2016-05-27 Thread fbelz...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Félix Belzunce Arcos created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35174 
 
 
 
  Modify cloud API when several shared clouds are defined with the same label  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/May/27 9:30 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Félix Belzunce Arcos 
 
 
 
 
 
 
 
 
 
 
If you define several clouds with the same labels you expect not only one cloud to be used but to share the load between all of them. However, Jenkins always tries to provision a node on the first cloud with matching labels. It will go to other clouds only if provisioning fails - It's a common Jenkins behaviour.  
Several clouds with similar labels will make only the first cloud to be used in a non failure scenario. 
Ideally, you should share the load and even be able to have more "expensive" clouds later in the list and the "cheaper" clouds will be used first until they reach capacity 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment