[JIRA] (OVIRT-2479) CQ Failure - Alot of ovirt-hosted-engine-setup
messages.
by Ehud Yonasi (oVirt JIRA)
Ehud Yonasi created OVIRT-2479:
----------------------------------
Summary: CQ Failure - Alot of ovirt-hosted-engine-setup messages.
Key: OVIRT-2479
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2479
Project: oVirt - virtualization made easy
Issue Type: Outage
Components: Change Queue, OST
Reporter: Ehud Yonasi
Assignee: infra
Since 3rd september there were alot of changes coming out of the blue to CQ about ovirt-hosted-engine-setup.
while investigating why it happened, I found out that the remote repo was deleted somehow and was restored.
That restoration caused all the project patches all-at-once triggers hundreds of jobs in build-art + CQ.
In order to recover from that situation i had to find the last patch of that project and asked for a re-merge (ci re-merge please).
After that change and multiple runs of CQ it passed.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100091)
6 years, 2 months
[JIRA] (OVIRT-2477) optimize storage of tested repos
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2477?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2477:
--------------------------------
Epic Link: OVIRT-2344
> optimize storage of tested repos
> --------------------------------
>
> Key: OVIRT-2477
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2477
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Reporter: Evgheni Dereveanchin
> Assignee: infra
> Priority: Low
>
> Currently tested repos that are used by CI are stored on the same FS as released RPMs.
> This has several downsides:
> * a single large FS is harder to manage (tested consumes half of this space)
> * a single vNIC is used by both external repo consumers and internal CI workloads
> * CI-related repo update jobs induce disk load and consume extra memory
> Some options to solve this:
> * move tested to a separate webserver
> * keep using resources.ovirt.org but mount a separate FS under /repos/ovirt/tested
> * store tested in some kind of object store?
> Opening a ticket to discuss our workflows and improvement options.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100091)
6 years, 2 months
[JIRA] (OVIRT-2477) optimize storage of tested repos
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2477?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2477:
--------------------------------
Epic Link: OVIRT-2344
> optimize storage of tested repos
> --------------------------------
>
> Key: OVIRT-2477
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2477
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Reporter: Evgheni Dereveanchin
> Assignee: infra
> Priority: Low
>
> Currently tested repos that are used by CI are stored on the same FS as released RPMs.
> This has several downsides:
> * a single large FS is harder to manage (tested consumes half of this space)
> * a single vNIC is used by both external repo consumers and internal CI workloads
> * CI-related repo update jobs induce disk load and consume extra memory
> Some options to solve this:
> * move tested to a separate webserver
> * keep using resources.ovirt.org but mount a separate FS under /repos/ovirt/tested
> * store tested in some kind of object store?
> Opening a ticket to discuss our workflows and improvement options.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100091)
6 years, 2 months
[JIRA] (OVIRT-2477) optimize storage of tested repos
by Evgheni Dereveanchin (oVirt JIRA)
Evgheni Dereveanchin created OVIRT-2477:
-------------------------------------------
Summary: optimize storage of tested repos
Key: OVIRT-2477
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2477
Project: oVirt - virtualization made easy
Issue Type: Improvement
Reporter: Evgheni Dereveanchin
Assignee: infra
Priority: Low
Currently tested repos that are used by CI are stored on the same FS as released RPMs.
This has several downsides:
* a single large FS is harder to manage (tested consumes half of this space)
* a single vNIC is used by both external repo consumers and internal CI workloads
* CI-related repo update jobs induce disk load and consume extra memory
Some options to solve this:
* move tested to a separate webserver
* keep using resources.ovirt.org but mount a separate FS under /repos/ovirt/tested
* store tested in some kind of object store?
Opening a ticket to discuss our workflows and improvement options.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100091)
6 years, 2 months