- Infra - oVirt List Archives

[JIRA] (OVIRT-1741) Get oVirt listed on https://release-monitoring.org/
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1741?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-1741: ---------------------------------------- [~sbonazzo(a)redhat.com] do you feel this item is useful enough? > Get oVirt listed on https://release-monitoring.org/ > --------------------------------------------------- > > Key: OVIRT-1741 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1741 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: Low > > https://release-monitoring.org/ seems to be a system that sends notification events when opens source projects release new versions. > Various systems seem to be listening and reacting on those events. > We should probably have oVirt listed there and sending events. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-1732) Make 'poll-upstream-chages' job abandon old changes it made
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1732?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-1732: ---------------------------------------- [~dron] can you check if it is already done? > Make 'poll-upstream-chages' job abandon old changes it made > ----------------------------------------------------------- > > Key: OVIRT-1732 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1732 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > Labels: poll-upstream-sources, standard-ci > > The poll-upstream-changes job creates patches when it runs. Not all these patches need or should be merged. When maintainers get around to looking at them, they typically can just merge the latest patch and throw away the rest. > The issue is that over time, the patches created by the job can accumulate, and it can be cumbersome for maintainers to remove un-needed ones manually. > We should make the poll job remove un-needed patches it made. It needs to look at the last SHA in the upstream-sources.yaml file, and remove all that patches that include an older SHA automatically. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-1615) Replace Artifactory with Nexus
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1615?page=com.atlassian.jira.… ] Anton Marchukov updated OVIRT-1615: ----------------------------------- Resolution: Won't Fix Status: Done (was: To Do) We should open items for specific problems instead > Replace Artifactory with Nexus > ------------------------------ > > Key: OVIRT-1615 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1615 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: General > Reporter: Barak Korren > Assignee: infra > Priority: Lowest > Labels: Icebox > > Nexus is the main competitor to Artifactory. It has similar features. Lokking at documentation available about it, it looks like the open source version of it supports a much bigger feature set the Artifactory without requiring an upgrade to a payed version: > https://help.sonatype.com/display/NXRM3/Repository+Manager+Feature+Matrix > Of interest to us are the PyPi (Python) support, the NPM (Javascript) and the Docker support. > It seems that Nexus is available as a container, so we may try deploying it on OpenShift. > I think we need to plan and execute a migration to Nexus. > This ticket should server as a tracking ticket for the entire work. We will create blocker tickets to track needed steps. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-1394) Remove STD-CI cleanup function cleanup_var
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1394?page=com.atlassian.jira.… ] Anton Marchukov updated OVIRT-1394: ----------------------------------- Resolution: Won't Fix Status: Done (was: To Do) Abandoned > Remove STD-CI cleanup function cleanup_var > ------------------------------------------ > > Key: OVIRT-1394 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1394 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Gil Shinar > Assignee: infra > > We do not remember why /var/tmp is being cleaned on each STD-CI job. > /var/tmp is good place for caching stuff (maven for example). > I'll remove the /var/tmp cleanup function and will monitor /var/tmp on slaves to make sure it does not use too much disk space. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-1333) Exclude game/desktop packages from mirrors
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1333?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-1333: ---------------------------------------- [~bkorren(a)redhat.com] is this already done? > Exclude game/desktop packages from mirrors > ------------------------------------------ > > Key: OVIRT-1333 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1333 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Labels: Icebox, first_time_task > > Our mirrors currently contain full copies of the CentOS and Fedora repos, including many large game and desktop productivity packages. > We should probably clean these packages from the repos to save space and bandwidth. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-1318) configure backup of status.ovirt.org
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1318?page=com.atlassian.jira.… ] Anton Marchukov updated OVIRT-1318: ----------------------------------- Resolution: Won't Fix Status: Done (was: To Do) > configure backup of status.ovirt.org > ------------------------------------ > > Key: OVIRT-1318 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1318 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > status.ovirt.org was set up - need to investigate if it needs to be backed up or we can produce documentation to set up a new stats page in case something happens to the existing OpenShift gear. > We can use OpenShift's built in backup/restore functionality: > https://developers.openshift.com/managing-your-applications/backing-up-appl… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 97786, 1 (ovirt-vmconsole) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Feb '19

15 Feb '19

A system test invoked by the "ovirt-4.2" change queue including change 97786,1 (ovirt-vmconsole) failed. However, this change seems not to be the root cause for this failure. Change 97704,6 (ovirt-vmconsole) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97704,6 (ovirt-vmconsole) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/97786/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97704/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3885/

1 0

[CQ]: 97786, 1 (ovirt-vmconsole) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Feb '19

15 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97786,1 (ovirt-vmconsole) failed. However, this change seems not to be the root cause for this failure. Change 97704,6 (ovirt-vmconsole) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97704,6 (ovirt-vmconsole) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/97786/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97704/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12896/

1 0

[JIRA] (OVIRT-769) infra-hiera Autodeploy via Gerrit Hooks
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-769?page=com.atlassian.jira.p… ] Anton Marchukov updated OVIRT-769: ---------------------------------- Resolution: Won't Fix Status: Done (was: To Do) We plan to decommission puppet > infra-hiera Autodeploy via Gerrit Hooks > --------------------------------------- > > Key: OVIRT-769 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-769 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Anton Marchukov > Assignee: infra > > infra-hiera repo is already used and configured in r10k to deploy from git. > However in gerrit there is not hooks that run CI on it and that trigger > publish when it is merged to git. > Looks like it is easy to fix and we can reuse most of the hooks we have for > infra-puppet. Basically the deploy should be done using the same jenkins > job and it already does that just not triggered. > As for CI check than we need to check if puppetlint we use is sufficient. > But it might be a good start. > -- > Anton Marchukov > Senior Software Engineer - RHEV CI - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-768) Decomission of MD5 Password Hashes for Infra Users
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-768?page=com.atlassian.jira.p… ] Anton Marchukov updated OVIRT-768: ---------------------------------- Resolution: Won't Fix Status: Done (was: To Do) > Decomission of MD5 Password Hashes for Infra Users > -------------------------------------------------- > > Key: OVIRT-768 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-768 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Anton Marchukov > Assignee: infra > > During the work of moving password parameters from foreman to internal > hiera I noted that there are some users that still have their passwords > hashed by MD5 algorithm. > MD5 has known crypto research that make it no longer suitable for storing > passwords securely: > https://en.wikipedia.org/wiki/MD5#Security (and corresponding links). > While the hashes are stored in internal repo it is still shared and prone > to information leaks. We should ask all users to rehash their passwords > with SHA-512 and when it is done we can remove MD5 exception > in site/ovirt_infra/manifests/user.pp so MD5 hashed passwords are no > longer accepted. > The current list of users left is available in infra-hiera repo. > -- > Anton Marchukov > Senior Software Engineer - RHEV CI - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0