- Infra - oVirt List Archives

[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

[JIRA] (OVIRT-1615) Replace Artifactory with Nexus
by eyal edri (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1615?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1615: ----------------------------- Epic Link: (was: OVIRT-403) > Replace Artifactory with Nexus > ------------------------------ > > Key: OVIRT-1615 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1615 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: General > Reporter: Barak Korren > Assignee: infra > Priority: Lowest > Labels: Icebox > > Nexus is the main competitor to Artifactory. It has similar features. Lokking at documentation available about it, it looks like the open source version of it supports a much bigger feature set the Artifactory without requiring an upgrade to a payed version: > https://help.sonatype.com/display/NXRM3/Repository+Manager+Feature+Matrix > Of interest to us are the PyPi (Python) support, the NPM (Javascript) and the Docker support. > It seems that Nexus is available as a container, so we may try deploying it on OpenShift. > I think we need to plan and execute a migration to Nexus. > This ticket should server as a tracking ticket for the entire work. We will create blocker tickets to track needed steps. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1615) Replace Artifactory with Nexus
by eyal edri (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1615?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1615: ----------------------------- Epic Link: (was: OVIRT-403) > Replace Artifactory with Nexus > ------------------------------ > > Key: OVIRT-1615 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1615 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: General > Reporter: Barak Korren > Assignee: infra > Priority: Lowest > Labels: Icebox > > Nexus is the main competitor to Artifactory. It has similar features. Lokking at documentation available about it, it looks like the open source version of it supports a much bigger feature set the Artifactory without requiring an upgrade to a payed version: > https://help.sonatype.com/display/NXRM3/Repository+Manager+Feature+Matrix > Of interest to us are the PyPi (Python) support, the NPM (Javascript) and the Docker support. > It seems that Nexus is available as a container, so we may try deploying it on OpenShift. > I think we need to plan and execute a migration to Nexus. > This ticket should server as a tracking ticket for the entire work. We will create blocker tickets to track needed steps. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1615) Replace Artifactory with Nexus
by eyal edri (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1615?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1615: ----------------------------- Labels: Icebox (was: ) > Replace Artifactory with Nexus > ------------------------------ > > Key: OVIRT-1615 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1615 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: General > Reporter: Barak Korren > Assignee: infra > Priority: Lowest > Labels: Icebox > > Nexus is the main competitor to Artifactory. It has similar features. Lokking at documentation available about it, it looks like the open source version of it supports a much bigger feature set the Artifactory without requiring an upgrade to a payed version: > https://help.sonatype.com/display/NXRM3/Repository+Manager+Feature+Matrix > Of interest to us are the PyPi (Python) support, the NPM (Javascript) and the Docker support. > It seems that Nexus is available as a container, so we may try deploying it on OpenShift. > I think we need to plan and execute a migration to Nexus. > This ticket should server as a tracking ticket for the entire work. We will create blocker tickets to track needed steps. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1920) Modify ci_env_client.py to be case and signs insensitive
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1920?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1920: -------------------------------- Epic Link: (was: OVIRT-400) > Modify ci_env_client.py to be case and signs insensitive > -------------------------------------------------------- > > Key: OVIRT-1920 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1920 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: mock_runner > Reporter: Daniel Belenky > Assignee: infra > > In OVIRT-1892 we make stdci config be case and signs insensitive. It means that when we will write a runner (or modify mock_runner) to use the new config, ci_env_client will have to deal with a normalized structure (without cases nor signs as dots and dashes). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1920) Modify ci_env_client.py to be case and signs insensitive
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1920?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1920: -------------------------------- Epic Link: (was: OVIRT-400) > Modify ci_env_client.py to be case and signs insensitive > -------------------------------------------------------- > > Key: OVIRT-1920 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1920 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: mock_runner > Reporter: Daniel Belenky > Assignee: infra > > In OVIRT-1892 we make stdci config be case and signs insensitive. It means that when we will write a runner (or modify mock_runner) to use the new config, ci_env_client will have to deal with a normalized structure (without cases nor signs as dots and dashes). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0