[ https://ovirt-jira.atlassian.net/browse/OVIRT-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Barak Korren updated OVIRT-1885:

Epic Link: OVIRT-400

Remove slave/resource management from Jenkins

     Key: OVIRT-1885
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1885
 Project: oVirt - virtualization made easy
         Issue Type: Improvement
         Components: Jenkins Master, Jenkins Slaves
Reporter: Barak Korren
Assignee: infra
  Labels: scale

The way out infra is configure right now, resource allocation and management is done by Jenkins itself. This means that all resources need to pre-allocated to Jenkins in the form of slaves. If we want to have separate Jenkins masters, our current configuration will force us to hard-split the resources between different Jenkins masters. If we want to share our pool of resources between multiple masters, it means that resource allocation needs to move out of Jenkins to external tools. Potential tools for different types of resources are:

• Beaker for managing physical hosts

• oVirt + a Jenkins could provider plugin for managing VMs

• OpenShift for managing containers (As a replacement for chroots).

— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)