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

Barak Korren updated OVIRT-1880:

Description:

There are multiple reasons why we may want to manage our bare-metal slaves with beaker:

• It will allow us to have auto-reprovisioning for them, perhaps even after every job

• It will allow us to scale up to multiple jenkins masters while sharing host resources

• If may allow us to safely move `global_setup.sh` to be executed before a jobs starts and not by the job itself.

There are probably multiple pieces of work to be carried out here, each will be tracked in a different ticket that will be set as a blocker to this ticket.

was:

There are multiple reasons why we may want to manage our bare-metal slaves with beaker:

• It will allow us to have auto-reprovisioning for them, perhaps even after every job

• It will allow us to scale up to multiple jenkins masters while sharing host resources

• If may allow us to safely move `global_setup.sh` to be executed before a jobs starts and not by the job itself.

Manage bare metals with beaker

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

There are multiple reasons why we may want to manage our bare-metal slaves with beaker:

• It will allow us to have auto-reprovisioning for them, perhaps even after every job

• It will allow us to scale up to multiple jenkins masters while sharing host resources

• If may allow us to safely move `global_setup.sh` to be executed before a jobs starts and not by the job itself.

There are probably multiple pieces of work to be carried out here, each will be tracked in a different ticket that will be set as a blocker to this ticket.

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