June 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-1333) Exclude game/desktop packages from mirrors
by eyal edri (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1333?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1333: ----------------------------- Labels: Icebox first_time_task (was: first_time_task) > Exclude game/desktop packages from mirrors > ------------------------------------------ > > Key: OVIRT-1333 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1333 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Labels: Icebox, first_time_task > > Our mirrors currently contain full copies of the CentOS and Fedora repos, including many large game and desktop productivity packages. > We should probably clean these packages from the repos to save space and bandwidth. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1333) Exclude game/desktop packages from mirrors
by eyal edri (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1333?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1333: ----------------------------- Epic Link: (was: OVIRT-403) > Exclude game/desktop packages from mirrors > ------------------------------------------ > > Key: OVIRT-1333 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1333 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task > > Our mirrors currently contain full copies of the CentOS and Fedora repos, including many large game and desktop productivity packages. > We should probably clean these packages from the repos to save space and bandwidth. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1333) Exclude game/desktop packages from mirrors
by eyal edri (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1333?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1333: ----------------------------- Epic Link: (was: OVIRT-403) > Exclude game/desktop packages from mirrors > ------------------------------------------ > > Key: OVIRT-1333 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1333 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task > > Our mirrors currently contain full copies of the CentOS and Fedora repos, including many large game and desktop productivity packages. > We should probably clean these packages from the repos to save space and bandwidth. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1877) Update docs to indicated adding 'jenkins:' prefix to build URLs
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1877?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1877: -------------------------------- Epic Link: (was: OVIRT-400) > Update docs to indicated adding 'jenkins:' prefix to build URLs > --------------------------------------------------------------- > > Key: OVIRT-1877 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1877 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation > Reporter: Barak Korren > Assignee: infra > > Our infra includes multipile places where users can input text that is used as configuration for repoman. Users are typically expected to place URLs of build jobs there to make repoman acquire built artifacts (For e.g. testing). > So far documentation specified that the plain URL to the build job can be used. This turns out to only be true for builds made on jenkins.ovirt.org. For URLs pointing at other jenkins servers, the '{{jenkins:}}' prefix needs to be added. > Documentation should be updated to teach users to add the '{{jenkins:}}' prefix. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1877) Update docs to indicated adding 'jenkins:' prefix to build URLs
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1877?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1877: -------------------------------- Epic Link: (was: OVIRT-400) > Update docs to indicated adding 'jenkins:' prefix to build URLs > --------------------------------------------------------------- > > Key: OVIRT-1877 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1877 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation > Reporter: Barak Korren > Assignee: infra > > Our infra includes multipile places where users can input text that is used as configuration for repoman. Users are typically expected to place URLs of build jobs there to make repoman acquire built artifacts (For e.g. testing). > So far documentation specified that the plain URL to the build job can be used. This turns out to only be true for builds made on jenkins.ovirt.org. For URLs pointing at other jenkins servers, the '{{jenkins:}}' prefix needs to be added. > Documentation should be updated to teach users to add the '{{jenkins:}}' prefix. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1878) GitHub support for pusher.py
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1878?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1878: -------------------------------- Epic Link: (was: OVIRT-400) > GitHub support for pusher.py > ---------------------------- > > Key: OVIRT-1878 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1878 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task, github > > '{{pusher.py}}' currently only supports gerrit, what this means in practice is that automated polling for upstream source changes is only available for repos that are hosted in Gerrit. > We need to support this in GitHub as well. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1878) GitHub support for pusher.py
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1878?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1878: -------------------------------- Epic Link: (was: OVIRT-400) > GitHub support for pusher.py > ---------------------------- > > Key: OVIRT-1878 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1878 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task, github > > '{{pusher.py}}' currently only supports gerrit, what this means in practice is that automated polling for upstream source changes is only available for repos that are hosted in Gerrit. > We need to support this in GitHub as well. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1885) Remove slave/resource management from Jenkins
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1885?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1885: ----------------------------------- Assignee: (was: infra) > 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 > 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#100087)

1 0

[JIRA] (OVIRT-1885) Remove slave/resource management from Jenkins
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1885?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1885: -------------------------------- Epic Link: (was: 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#100087)

1 0

[JIRA] (OVIRT-1885) Remove slave/resource management from Jenkins
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1885?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1885: -------------------------------- Epic Link: (was: 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#100087)

1 0