We're reaching a point where slave capacity is slowing development down. I'd like to get an idea of how much more capacity we need and strategies we could adopt around this.
1) If we went with a dedicated Rackspace server, how big of a machine would we need and what would be the per month cost? 2) Could we, if we have the funds, adopt an elastic strategy to handle peak development times? For example, using the Jenkins EC2 [1] plugin? 3) If we beef up efforts to divert systests from Rackspace to ci.centos.org would that free up funds to add more Rackspace slaves? 4) Other? Eric [1] https://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin Due to our usage patterns, the ideal case would seem -- Eric D. Helms Red Hat Engineering Ph.D. Student - North Carolina State University -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
