- Infra - oVirt List Archives

[JIRA] (OVIRT-1164) Remove most of the images from glance.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1164?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1164: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Remove most of the images from glance.ovirt.org > ----------------------------------------------- > > Key: OVIRT-1164 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1164 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Reporter: Yaniv Kaul > Assignee: Evgheni Dereveanchin > > I'd like to make sure people are not abusing and downloading images from Glance that are not directly related to oVirt. Providing it as a service for download is not our aim. > Currently, it has a lot of different images, multiple versions of them, etc. > Specifically, multiple versions of Ubuntu, and older versions of Atomic, CentOS, Fedora should be removed. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1231) Security: do we need HSTS for oVirt services?
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1231?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-1231: --------------------------------------------- [~duck] are we already using this? > Security: do we need HSTS for oVirt services? > --------------------------------------------- > > Key: OVIRT-1231 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1231 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eedri > Assignee: infra > > https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security > Most of the browsers already supports it and some websites started to enforce it. > cc [~dfediuck] -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1245) Consider way for organize disaster recovery solution for lists
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1245?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1245: ------------------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > Consider way for organize disaster recovery solution for lists > -------------------------------------------------------------- > > Key: OVIRT-1245 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1245 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: Marc Dequènes (Duck) > > │08:50:51 sbonazzo1 | landgraf: we're lucky enough we have mirrors for users │ > │08:51:05 sbonazzo1 | landgraf: too bad we don't have redundant CI infra :-) │ > │08:51:27 landgraf | sbonazzo1: and lists.. │ > │08:51:40 landgraf | sbonazzo1: so we cannot send outage ntifications there :) │ > │08:51:51 sbonazzo1 | landgraf: yep │ > │08:52:03 sbonazzo1 | landgraf: maybe worth to open a jira ticket for it │ > │08:52:10 sbonazzo1 | landgraf: it will be a huge improvement │ > │08:53:30 sbonazzo1 | landgraf: do we have a disaster recovery plan? -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1281) Add 'patch owner' feature to Gerrit
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1281?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1281: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Add 'patch owner' feature to Gerrit > ------------------------------------ > > Key: OVIRT-1281 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1281 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eedri > Assignee: Evgheni Dereveanchin > > Details still TBD, but we want to check if there is a way for the patch author who is the patch 'owner' or 'maintainer' and has the responsibility to make sure the patch is reviewed in time and pushed and not left behind. > It might be Gerrit doesn't support such feature, but we'll check. > [~oourfali(a)redhat.com][~ykaul][~danken] please add more info as needed. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1288) Find out why Gerrit always fails re-basing when trying to submit more then 3 changes at once
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1288?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1288: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Find out why Gerrit always fails re-basing when trying to submit more then 3 changes at once > -------------------------------------------------------------------------------------------- > > Key: OVIRT-1288 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1288 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Gerrit/git > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > > Gerrit has a feature where if you have multiple dependant patches, and they all have all the flags properly set, the submit button for changes with unmerged dependencies becomes 'Submit including parents' and lets you submit a whole set of changes at once. > I've found out that of you have more then 3 dependent changes in a chain, Gerrit will always fail submitting the 4th change and claim there is a rebase conflict, even when there is none. > This sounds like an artificial limitation, and we need to at least know where it comes from. And consider removing it. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1295) Add job to auto-rebase patches that are ready to be merged
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1295?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-1295: ---------------------------------------- Priority: Low (was: Medium) > Add job to auto-rebase patches that are ready to be merged > ----------------------------------------------------------- > > Key: OVIRT-1295 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1295 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eedri > Assignee: infra > Priority: Low > > We want to help stable branch maintainers to minimize the time needed for merging approved changes ( i.e CR +2 and VERIFY +1 ) and also to reduce the chance of merge conflicts. > A suggestion was made to create a job which will detect patches ready to be merged with the flags CR +2 and V +1 set and will auto rebase them, so when a maintainer is ready to submit a patch, hopefully the patch won't need a rebase and can be merged without further waiting for rebase or CI. > This approach might introduce challenges when working on patches that are dependent on other patches and a specific logic might be required to handle special cases. > [~tnisan(a)redhat.com][~ykaul][~dfediuck] I hope this conveys the need and requirement, please comment or add thoughts if I missed anything. > Initially we'll try enabling it for ovirt-engine on 4.1 branch. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1311) Nightliy publisher 'move_jenkins_nightly' cron job failes when the *.ready dir is empty
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1311?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-1311: ---------------------------------------- Epic Link: OVIRT-400 (was: OVIRT-403) > Nightliy publisher 'move_jenkins_nightly' cron job failes when the *.ready dir is empty > --------------------------------------------------------------------------------------- > > Key: OVIRT-1311 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1311 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > > If The '{{*.ready}}' directory does not contain any RPMs, the cron job fails. This failure causes all repos not to get published until the failure is fixed. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1311) Nightliy publisher 'move_jenkins_nightly' cron job failes when the *.ready dir is empty
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1311?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-1311: ---------------------------------------- Epic Link: OVIRT-400 (was: OVIRT-403) > Nightliy publisher 'move_jenkins_nightly' cron job failes when the *.ready dir is empty > --------------------------------------------------------------------------------------- > > Key: OVIRT-1311 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1311 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > > If The '{{*.ready}}' directory does not contain any RPMs, the cron job fails. This failure causes all repos not to get published until the failure is fixed. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1312) Make 'scan_for_artifacts.sh' publish repos separately
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1312?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-1312: ---------------------------------------- Epic Link: OVIRT-400 (was: OVIRT-403) > Make 'scan_for_artifacts.sh' publish repos separately > ----------------------------------------------------- > > Key: OVIRT-1312 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1312 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > > The '{{scan_for_artifacts.sh}}' cron job runs on the resources server and syncs packages into the nightly snapshot repos. It tries to serially sync all repos for all oVirt versions. > The issue is that if one of the repos fails to sync, the rest do not get synced either. > We need to make the cron job sync each repo separately so failure mfor one repo will not affect the others. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1312) Make 'scan_for_artifacts.sh' publish repos separately
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1312?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-1312: ---------------------------------------- Epic Link: OVIRT-400 (was: OVIRT-403) > Make 'scan_for_artifacts.sh' publish repos separately > ----------------------------------------------------- > > Key: OVIRT-1312 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1312 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > > The '{{scan_for_artifacts.sh}}' cron job runs on the resources server and syncs packages into the nightly snapshot repos. It tries to serially sync all repos for all oVirt versions. > The issue is that if one of the repos fails to sync, the rest do not get synced either. > We need to make the cron job sync each repo separately so failure mfor one repo will not affect the others. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0