[JIRA] (OVIRT-1373) Setup a container registry in PHX (But only on demand)
by Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-1373:
-----------------------------------
Summary: Setup a container registry in PHX (But only on demand)
Key: OVIRT-1373
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1373
Project: oVirt - virtualization made easy
Issue Type: New Feature
Components: Repositories Mgmt
Reporter: Barak Korren
Assignee: infra
As we've been discussing the CI/CD process for containers with various developers. The possibility arose that we might need to run our own container registry on the PHX infrastructure.
Our preference would actually be to use DockerHub or some other public registry, as opposed to running our own service, but it might end up being insufficient from performance or reliability reasons. We will try that first, so for the time being this ticket is for planning and research purposes as opposed to actual deployment.
The container registry will be used by the CI system directly so it needs to be quite fast and very reliable. It will probably contain multiple versions of the CentOS and Fedora base images as well as many other images built on top of them, so storage requirements may not be modest either.
--
This message was sent by Atlassian JIRA
(v1000.929.2#100040)
7 years, 6 months
[JIRA] (OVIRT-1373) Setup a container registry in PHX (But only on demand)
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1373?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1373:
--------------------------------
Epic Link: OVIRT-403
> Setup a container registry in PHX (But only on demand)
> ------------------------------------------------------
>
> Key: OVIRT-1373
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1373
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: Repositories Mgmt
> Reporter: Barak Korren
> Assignee: infra
>
> As we've been discussing the CI/CD process for containers with various developers. The possibility arose that we might need to run our own container registry on the PHX infrastructure.
> Our preference would actually be to use DockerHub or some other public registry, as opposed to running our own service, but it might end up being insufficient from performance or reliability reasons. We will try that first, so for the time being this ticket is for planning and research purposes as opposed to actual deployment.
> The container registry will be used by the CI system directly so it needs to be quite fast and very reliable. It will probably contain multiple versions of the CentOS and Fedora base images as well as many other images built on top of them, so storage requirements may not be modest either.
--
This message was sent by Atlassian JIRA
(v1000.929.2#100040)
7 years, 6 months
oVirt infra daily report - unstable production jobs - 318
by jenkins@jenkins.phx.ovirt.org
------=_Part_150_91694275.1494457202975
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Good morning!
Attached is the HTML page with the jenkins status report. You can see it also here:
- http://jenkins.ovirt.org/job/system_jenkins-report/318//artifact/exported...
Cheers,
Jenkins
------=_Part_150_91694275.1494457202975
Content-Type: text/html; charset=us-ascii; name=upstream_report.html
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=upstream_report.html
Content-ID: <upstream_report.html>
<!DOCTYPE html><head><style type="text/css">
table.gridtable {
border-collapse: collapse;
table-layout:fixed;
width:1600px;
font-family: monospace;
font-size:13px;
}
.head {
font-size:20px;
font-family: arial;
}
.sub {
font-size:18px;
background-color:#e5e5e5;
font-family: arial;
}
pre {
font-family: monospace;
display: inline;
white-space: pre-wrap;
white-space: -moz-pre-wrap !important;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;
}
</style>
</head>
<body>
<table class="gridtable" border=2>
<tr><th colspan=2 class=head>
RHEVM CI Jenkins Daily Report - 10/05/2017
</th></tr><tr><th colspan=2 class=sub>
<font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font>
</th></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_master-ansible-system-tests/">ovirt_master-ansible-system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
------=_Part_150_91694275.1494457202975--
7 years, 6 months
Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #326
by jenkins@jenkins.phx.ovirt.org
See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/326/disp...>
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/>
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Pruning obsolete local branches
Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git
> git --version # timeout=10
> git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/changes/13/75913/5:patch --prune
> git rev-parse origin/patch^{commit} # timeout=10
> git rev-parse patch^{commit} # timeout=10
Checking out Revision 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f (patch)
> git config core.sparsecheckout # timeout=10
> git checkout -f 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f
> git rev-list 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f # timeout=10
[system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/hudson7393981636863892699.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf
Checking if mirror needs a resync
Traceback (most recent call last):
File "/usr/bin/reposync", line 343, in <module>
main()
File "/usr/bin/reposync", line 175, in main
my.doRepoSetup()
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup
return self._getRepos(thisrepo, True)
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos
self._repos.doSetup(thisrepo)
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup
self.retrieveAllMD()
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD
dl = repo._async and repo._commonLoadRepoXML(repo)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML
if self._latestRepoXML(local):
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1434, in _latestRepoXML
oxml = self._saveOldRepoXML(local)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1292, in _saveOldRepoXML
shutil.copy2(local, old_local)
File "/usr/lib64/python2.7/shutil.py", line 131, in copy2
copystat(src, dst)
File "/usr/lib64/python2.7/shutil.py", line 100, in copystat
os.chmod(dst, mode)
OSError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/centos-updates-el6/repomd.xml.old.tmp'
Build step 'Execute shell' marked build as failure
7 years, 6 months