- Infra - oVirt List Archives

[JIRA] (OVIRT-1303) add monitoring to mirrors.phx
by Evgheni Dereveanchin (oVirt JIRA) 05 Apr '17

05 Apr '17

Evgheni Dereveanchin created OVIRT-1303: ------------------------------------------- Summary: add monitoring to mirrors.phx Key: OVIRT-1303 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1303 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra Add monitoring to ensure we don't run out of space on the FS or LVM pool of the mirrors VM in PHX. -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6212 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Apr '17

05 Apr '17

------=_Part_247_914655397.1491419877676 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6212/, Build Number: 6212, Build Status: FAILURE ------=_Part_247_914655397.1491419877676--

1 1

Duplicate user in gerrit
by Ori Liel 05 Apr '17

05 Apr '17

Hi, I was informed that there's a problem adding me as a reviewer in gerrit, since my user is duplicated. Can you please help me with this? Thanks, Ori.

2 2

[JIRA] (OVIRT-1294) oliel - Duplicate user in gerrit
by Barak Korren (oVirt JIRA) 05 Apr '17

05 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1294?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1294: -------------------------------- Blocked By: Blocking on contacting user to verify fix Status: Blocked (was: To Do) > oliel - Duplicate user in gerrit > -------------------------------- > > Key: OVIRT-1294 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1294 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Barak Korren > > Forwarding to infra-support to open a ticket. > ---------- Forwarded message ---------- > From: Ori Liel <oliel(a)redhat.com> > Date: 3 April 2017 at 08:34 > Subject: Duplicate user in gerrit > To: infra <infra(a)ovirt.org> > Hi, > I was informed that there's a problem adding me as a reviewer in > gerrit, since my user is duplicated. > Can you please help me with this? > Thanks, > Ori. > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6202 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Apr '17

05 Apr '17

------=_Part_215_1852687810.1491384212001 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6202/, Build Number: 6202, Build Status: FAILURE ------=_Part_215_1852687810.1491384212001--

1 9

[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories
by Michal Skrivanek (oVirt JIRA) 05 Apr '17

05 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.… ] Michal Skrivanek commented on OVIRT-1299: ----------------------------------------- +1 for ovirt-web-ui, we're going to use the same flow > Please provide a koji (and if possible bodhi) instance for ovirt repositories > ----------------------------------------------------------------------------- > > Key: OVIRT-1299 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1299 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: infra > > Some of the maintainers of oVirt project wants to have control on the builds going into the release repositories without 3rd party intervention on it. > They would like to have a dist-git + koji like developer experience. > A bodhi instance would help reviewing the package before it lands on repositories. -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories
by Martin Sivak (oVirt JIRA) 05 Apr '17

05 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.… ] Martin Sivak commented on OVIRT-1299: ------------------------------------- Exactly what I would like to achieve. With one improvement in step 3. I usually release in the same copr repo so in the ideal world I would just provide the repo url once and every time you do a compose (or nightly) the tooling would check for updates. > Please provide a koji (and if possible bodhi) instance for ovirt repositories > ----------------------------------------------------------------------------- > > Key: OVIRT-1299 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1299 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: infra > > Some of the maintainers of oVirt project wants to have control on the builds going into the release repositories without 3rd party intervention on it. > They would like to have a dist-git + koji like developer experience. > A bodhi instance would help reviewing the package before it lands on repositories. -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

[JIRA] (OVIRT-1302) Please merge my multiple gerrit identies
by Barak Korren (oVirt JIRA) 05 Apr '17

05 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1302?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1302: ----------------------------------- Assignee: Barak Korren (was: infra) > Please merge my multiple gerrit identies > ---------------------------------------- > > Key: OVIRT-1302 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1302 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: vfeenstr > Assignee: Barak Korren > > I added new auth methods (Github and Gmail) and now I can't be assigned anymore by others to reviews etc. > vfeenstr @ RH -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories
by Barak Korren (oVirt JIRA) 05 Apr '17

05 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1299: ------------------------------------- {quote} The difference is that you depend on gerrit and on specific branch name to know which build-artifact script to execute. My requests does not require that, I will provide the git url and tarball url (or a dir with those) instead. {quote} It does not have to be in Gerrit, nor is there a need for specific branches ATM. The discussion about branches was trying to come up with a scheme to auto-detect things that are currently specified in the project YAML in the Jenkins repo. Since we did not implement that yet, you can use any branch names you'd like and map them to oVirt releases in the YAML file. The one thing we do strongly depend on, is that every change starts with a commit somewhere so that we can track it, and use the hash as a reliable unique identifier for the change. I think this is important. Without it you cannot track changes. {quote} Something very similar to what I want is the releng tools repository Sandro uses. An example: https://gerrit.ovirt.org/gitweb?p=releng-tools.git;a=blob;f=releases/ovirt-… The only issue we have with this is that it is not properly documented (inheritance rules, ...), does not support source tarballs and CI is probably not using it at all. {quote} That is a repoman configuration file. All it does is collect files together. This is not a reliable source of information, not is it located in the right place, because AFAIK deciding which package builds go to which oVirt releases is the responsibility of the individual package maintainers, not the integration team. But still, I'm not sure I understand where you are trying to go. Let me try to describe the process you are tying to get to as I understand it: # You merge a new commit to mom # You go and launch a build in copr manually. # When the build is done you go to some file in some repo, specify the url to the build in it and submit a new commit. # Once the new commit is merged the CY system downloads the new build and publishes it in the oVirt repos. > Please provide a koji (and if possible bodhi) instance for ovirt repositories > ----------------------------------------------------------------------------- > > Key: OVIRT-1299 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1299 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: infra > > Some of the maintainers of oVirt project wants to have control on the builds going into the release repositories without 3rd party intervention on it. > They would like to have a dist-git + koji like developer experience. > A bodhi instance would help reviewing the package before it lands on repositories. -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

[JIRA] (OVIRT-1302) Please merge my multiple gerrit identies
by vfeenstr (oVirt JIRA) 05 Apr '17

05 Apr '17

vfeenstr created OVIRT-1302: ------------------------------- Summary: Please merge my multiple gerrit identies Key: OVIRT-1302 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1302 Project: oVirt - virtualization made easy Issue Type: Task Reporter: vfeenstr Assignee: infra I added new auth methods (Github and Gmail) and now I can't be assigned anymore by others to reviews etc. vfeenstr @ RH -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0