January 2017 - Infra - oVirt List Archives

[JIRA] (OST-32) Add code coverage for OST
by eyal edri [Administrator] (oVirt JIRA) 19 Jan '17

19 Jan '17

eyal edri [Administrator] created OST-32: -------------------------------------------- Summary: Add code coverage for OST Key: OST-32 URL: https://ovirt-jira.atlassian.net/browse/OST-32 Project: oVirt system tests Issue Type: New Feature Reporter: eyal edri [Administrator] Assignee: infra As first step run it on basic suites and publish results in CI. -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OST-32) Add code coverage for OST
by eyal edri [Administrator] (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OST-32?page=com.atlassian.jira.plug… ] eyal edri [Administrator] updated OST-32: ----------------------------------------- Epic Link: OVIRT-400 > Add code coverage for OST > ------------------------- > > Key: OST-32 > URL: https://ovirt-jira.atlassian.net/browse/OST-32 > Project: oVirt system tests > Issue Type: New Feature > Reporter: eyal edri [Administrator] > Assignee: infra > > As first step run it on basic suites and publish results in CI. -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-1012) ovirt-engine-sdk is build on el6 in following branches master, sdk_4.1 and sdk_4.0
by eyal edri [Administrator] (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1012?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1012: -------------------------------------------------- Can you send a patch to the YAML to exclude it or you need help with it? > ovirt-engine-sdk is build on el6 in following branches master, sdk_4.1 and sdk_4.0 > ---------------------------------------------------------------------------------- > > Key: OVIRT-1012 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1012 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > Hello, > The ovirt-engine-sdk is build on el6 in following branches master, sdk_4.1 and sdk_4.0. > This isn't correct. In specified branches the project should be build only for el7, fc24 and fc25. > Thank you. > CC [~jhernand(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-1012) ovirt-engine-sdk is build on el6 in following branches master, sdk_4.1 and sdk_4.0
by Ondra Machacek (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1012?page=com.atlassian.jira.… ] Ondra Machacek commented on OVIRT-1012: --------------------------------------- On 4.1 branch Python SDK is still built for el6: https://gerrit.ovirt.org/#/c/70691/ > ovirt-engine-sdk is build on el6 in following branches master, sdk_4.1 and sdk_4.0 > ---------------------------------------------------------------------------------- > > Key: OVIRT-1012 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1012 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > Hello, > The ovirt-engine-sdk is build on el6 in following branches master, sdk_4.1 and sdk_4.0. > This isn't correct. In specified branches the project should be build only for el7, fc24 and fc25. > Thank you. > CC [~jhernand(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-1012) ovirt-engine-sdk is build on el6 in following branches master, sdk_4.1 and sdk_4.0
by eyal edri [Administrator] (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1012?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1012: -------------------------------------------------- [~juan(a)redhat.com] anything is left to be done here? > ovirt-engine-sdk is build on el6 in following branches master, sdk_4.1 and sdk_4.0 > ---------------------------------------------------------------------------------- > > Key: OVIRT-1012 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1012 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > Hello, > The ovirt-engine-sdk is build on el6 in following branches master, sdk_4.1 and sdk_4.0. > This isn't correct. In specified branches the project should be build only for el7, fc24 and fc25. > Thank you. > CC [~jhernand(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-989) Ensure backup.pxh.ovirt.org has proper data retention cycles
by eyal edri [Administrator] (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-989?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-989: ----------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) Didn't you fixed this with the patch to rsync --delete? > Ensure backup.pxh.ovirt.org has proper data retention cycles > ------------------------------------------------------------ > > Key: OVIRT-989 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-989 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: General > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > Priority: High > > backup.phx.ovirt.org started running out of space, so the disk was expanded form 250G to 500G (While keeping the actual LV at 300G). > We need to ensure old data gets erased eventually, and its not just filling up. -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-1048) Run OST against vdsm+Engine on kubernetes
by eyal edri [Administrator] (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1048?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1048: --------------------------------------------- Priority: Highest (was: High) > Run OST against vdsm+Engine on kubernetes > ----------------------------------------- > > Key: OVIRT-1048 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1048 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins, Lago > Reporter: Fabian Deutsch > Assignee: infra > Priority: Highest > Labels: kubevirt > > Hey, > Yaniv Bronheim is building containers for vdsm and engine. > Lago should become capable of running OST against this setup. > The basic flow is: > 1. Normal CentOS > 2. Install kubernetes > 3. Deploy engine and vdsm pods > The pod definitions are here: > https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree > https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree > A similar script can be found here: > https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh > But this script is deploying kubevirt, instead of the engine + vdsm container. -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-1022) Files are read only after STD-CI jobs run
by eyal edri [Administrator] (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1022?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1022: -------------------------------------------------- was it fixed? > Files are read only after STD-CI jobs run > ----------------------------------------- > > Key: OVIRT-1022 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1022 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Gil Shinar > Assignee: infra > Priority: Highest > > Some check-patch, check-merged, build-artifacts scripts makes changes to files' permissions. > I have added fix for that in cleanup slave phase -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-944) Prepare CI for 4.1 oVirt branch
by eyal edri [Administrator] (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-944?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-944: -------------------------------------------- Resolution: Fixed Status: Done (was: To Do) all of the major flows were added, there might be some projects which didn't branch yet, they will be tracked on separate ticket. > Prepare CI for 4.1 oVirt branch > ------------------------------- > > Key: OVIRT-944 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-944 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > We need to add all relevant jobs and flows for 4.1, lets use this ticket to track all progress > * system tests > * experimental flows > * publishers > * deploy to experimental > * gerrit hooks (?) > * standard flows for various projects > cc [~sbonazolla(a)redhat.com] [~ederevea] [~bkorren(a)redhat.com] [~amarchuk] [~sbendavi(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-879) check if we can analayze oVirt RPM with whitesource
by eyal edri [Administrator] (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-879?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-879: -------------------------------------------- Resolution: Done Status: Done (was: To Do) It can't unfortunately, we'll keep is for tracking vulnerabilities or outdated JARs for now. > check if we can analayze oVirt RPM with whitesource > --------------------------------------------------- > > Key: OVIRT-879 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-879 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri [Administrator] > Assignee: infra > > following ticket: https://whitesource.freshdesk.com/support/tickets/12091# > It might be possible to analyze licenses via the File system Agent: > Example: > We can support this use case by using the File System Agent (FSA) to unarchive all of the RPM files and then importing all specified file extensions (e.g. *.js, *.py, *.tgz, etc) that are contained within each RPM. These settings are specified in the configuration file for the File System Agent. It will probably be easier to explain if we schedule a call by phone, but here is an example of the FSA config file with archive extraction: > ############################################################################################# > # Includes/Excludes Glob patterns - PLEASE USE ONLY ONE EXCLUDE LINE AND ONE INCLUDE LINE > ############################################################################################# > includes=**/*.c **/*.cc **/*.cp**/*.cpp **/*.tgz **/*.c++ **/*.h **/*.py **/*.js > excludes=**/*sources.jar **/*javadoc.jar > case.sensitive.glob=false > followSymbolicLink=true > > ################# > # Archive Properties > ################# > archiveExtractionDepth=5 > archiveIncludes=**/*.rpm **/*.zip > ############################################################################################# -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0