[
https://ovirt-jira.atlassian.net/browse/OVIRT-1451?page=com.atlassian.jir...
]
eedri commented on OVIRT-1451:
------------------------------
[~ederevea][~dron] I think it's crucial for both of you to get familiar with how our
mirrors work because it affects oVirt's infra and also OST debugging.
I think it will be best if [~ederevea] will take this ticket and Dafna will track it,
since it might require too much knowledge of our infra to handle at this point.
Add a CI mirror for Gluster 3.10
--------------------------------
Key: OVIRT-1451
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-1451
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: Repositories Mgmt
Reporter: Barak Korren
Assignee: infra
Priority: High
We currently have mirrors only for Gluster 3.6 and 3.8, since Gluster 3.10 was released,
we need to add a mirror for it.
For more information about mirrors:
http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Transactional_mirrors...
The process to add mirrors is roughly:
# Create a patch to the 'jenkins' repo with:
## Adding upstream repo configuration to the '{{data/mirrors-reposync.conf}}'
file
## Adding a mirror sync job to
'{{jobs/confs/projects/system/sync_mirrors.yaml}}'.
# Verify patch by:
## Running JJB to create the new sync job
## Invoke the new sync job to see that it manages to sync the mirror for the 1st time
## Wait a while to let the job get schedules and run on its own (sync jobs are scheduled
every 8 hours by default)
As part of this work please document the process for adding a new mirror in infra-docs.
--
This message was sent by Atlassian JIRA
(v1000.1068.0#100050)