February 2016 - Infra - oVirt List Archives

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 1953 - Failure!
by jenkins＠ovirt.org 18 Jul '16

18 Jul '16

------=_Part_448_1394496766.1454963377637 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merge… Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merge… Build Number: 1953 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/53193 ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1953 [Allon Mureinik] webadmin: Remove Linq#RoleNameComparer ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_448_1394496766.1454963377637--

3 48

Web space in ovirt.org for the REST API documentation
by Juan Hernández 02 Jun '16

02 Jun '16

Hello, Version 4.0 of the oVirt Engine API will include automatically generated documentation of the API. This will be included in the server itself, probably in a URL like "http://engine.example.com/ovir-engine/api/explorer". I would like to have this same documentation available in "ovirt.org", so that users that don't have a server installed can still use the documentation, something like this: https://jhernand.fedorapeople.org/ovirt-api-explorer/#/home The documentation and the application used to explore it require approx 20 MiB of space, for each version of the API (currently only one, version 4). Eventually this web site should be updated by a Jenkins job as part of the release process. Can we host this in ovirt.org? Regards, Juan Hernandez -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.

2 5

Coming (Very) Soon - New ovirt.org Website & Deprecated Wiki
by Mikey Ariel 16 Mar '16

16 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 In the past months we've been working on upgrading the oVirt project infrastructure, to better support the community contributions. One of the main platforms for our user documentation, release management content, and community content has been the MediaWiki site that you all know as ovirt.org. Most of us are familiar with the wiki site format, with all its advantages and disadvantages. After several years of serving the community, I'm happy to announce that we are very near to completing a full upgrade of the website infrastructure from a wiki site to a static site, source-controlled on GitHub and authored in Markdown. This email is the pre-launch announcement, as we are reaching the final stages of the migration, and there are a few actions that might affect your work on website content in the meantime. Why migrate the website ======================= As mentioned, wiki sites provide an open and flexible content editing platform. Unfortunately, as the site grows the content becomes quite difficult to manage and curate, resulting in lots of obsolete, outdated, and incorrect information. By moving to a source-controlled repository and implementing GitHub's contribution workflow, we strive to ease the work of maintaining an up-to-date content site, employ a peer-review process for changes, and standardize the authoring markup language to lower the contribution barrier. The Middleman framework (Ruby-based static site generator) was chosen based on observing successful implementation of other open-source community websites, such as OpenStack RDO, Project Atomic, and Gluster. What we did so far ================== When we started the migration, our Web design team exported all of the wiki content from the old website and converted it to MD files. They also set up the website config flow, auto-deploy, and upgraded the look-and-feel of the website. We then initiated a content review effort as well as a UX review for the new website in a smaller forum, which caught most of the critical issues with the new website and helped us get the new format to a place where we can release the website in a near-GA/public-beta format. Yesterday (Wednesday Feb 17) we exported the website one more time and currently we're running a diff on all the files that changed since the initial export was done, to make sure we grab all the updates and the latest content before we launch the new website. What is about to happen ======================= Today we are initiating a **wiki freeze**, which means the old MediaWiki site will become read-only. This is to ensure that all of our diff scripts reflect the most current state of the content on the website, and that we don't lose any content in the transition. Barring any unexpected blockers, we will port the ovirt.org domain to point to the new website and open the new website for contributions on **Monday February 22** or earlier. What do you need to do right now ================================ If you have any wiki pages that you're actively editing, please don't save them to the old MediaWiki site, and hold onto your pending changes until we send the happy launch email. We will also include instructions on how to contribute/edit/add content to the new website, but in general the workflow will be aligned with the standard GitHub best practices (clone-edit-commit-pullrequest), so you can utilize all of the git commands that you already know or work directly within the GitHub web editor. I'd like to thank all of the people who were involved with this migration so far, ovirt.org is a big website with lots of content and it was no small task to upgrade it. Please feel free to ping me on- or off-list if you have any questions about the next steps, and expect a happy launch email soon! Cheers, Mikey - -- Mikey Ariel Community Lead, oVirt www.ovirt.org "To be is to do" (Socrates) "To do is to be" (Jean-Paul Sartre) "Do be do be do" (Frank Sinatra) Mobile: +420-702-131-141 IRC: mariel / thatdocslady Twitter: @ThatDocsLady -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWxa5AAAoJEHYPPTOszxHow10H/jeuhzMrUrPsCBedLg7OKnNh jdKDujT/aCyA4LgnRHnVBEASunShmVaOJrMdU4r0PZbdkX1Mf5/SvCEFGKY14qAg m/5CnDhlwbp5rqo09VOGLMg20CaMtpUoE1LpKE/epGYEKSBr2JIAA+HAsYa1OEyS 9oHDDx+ZIbfHNlygW1KpW6dsuZRscTbfy4kk8rY83YdJGyQiQN+ulsjT/c2N8ArR WylohBE2OcC7+nzf7AejKJ94loWxnVhO4qWbNWAH00LArG89yFWBBSlMK6ocJUED P4k2IzgG+75eTiCZAAw5/Vaqx0YVU7hScSmBqOPQu/wo4e2t11AR7A8D7Cn+vpU= =XWEH -----END PGP SIGNATURE-----

4 3

[JIRA] (OVIRT-313) deleting yamlized jobs from git doesn't remove them from jenkins
by sbonazzo (oVirt JIRA) 29 Feb '16

29 Feb '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-313?page=com.atlassian.jira.p… ] sbonazzo commented on OVIRT-313: -------------------------------- Yes, still relevant. Jobs removed from yaml are now marked to be removed, but the removal is still manual. See for example: http://jenkins.ovirt.org/user/sbonazzo/my-views/view/to%20be%20deleted/ > deleting yamlized jobs from git doesn't remove them from jenkins > ---------------------------------------------------------------- > > Key: OVIRT-313 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-313 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Affects Versions: Production > Reporter: sbonazzo > Assignee: infra > Labels: yaml > > we have an issue with yamlized jobs: removing them from yaml doesn't disable them and doesn't delete them from jenkins. Example is: > http://jenkins.ovirt.org/job/vdsm_master_create-rpms-el6-x86_64_merged/ > that should have been disabled / removed after job dropped by yaml files with commit 7479c7cde296a6bf8b7202f7483e408470e7e58f -- This message was sent by Atlassian JIRA (v7.2.0-OD-02-009#72000)

1 0

[JIRA] (OVIRT-425) Enable backups for hosted engine on phx
by eyal edri [Administrator] (oVirt JIRA) 28 Feb '16

28 Feb '16

eyal edri [Administrator] created OVIRT-425: ----------------------------------------------- Summary: Enable backups for hosted engine on phx Key: OVIRT-425 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-425 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra http://www.ovirt.org/OVirt_Hosted_Engine_Backup_and_Restore -- This message was sent by Atlassian JIRA (v7.2.0-OD-02-009#72000)

1 0

[JIRA] (OVIRT-424) Review linode01 server before decommision and backup relevant data
by eyal edri [Administrator] (oVirt JIRA) 28 Feb '16

28 Feb '16

eyal edri [Administrator] created OVIRT-424: ----------------------------------------------- Summary: Review linode01 server before decommision and backup relevant data Key: OVIRT-424 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-424 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Before we decommission the server after migrating all services, verify we don't have any relevant info on it, and if so, backup to PHX. -- This message was sent by Atlassian JIRA (v7.2.0-OD-02-009#72000)

1 0

[JIRA] (OVIRT-313) deleting yamlized jobs from git doesn't remove them from jenkins
by eyal edri [Administrator] (oVirt JIRA) 28 Feb '16

28 Feb '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-313?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-313: ------------------------------------------------- [~sbonazzola(a)redhat.com] is this still relevant? can you post example of job which wasn't removed when removed from yaml? > deleting yamlized jobs from git doesn't remove them from jenkins > ---------------------------------------------------------------- > > Key: OVIRT-313 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-313 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Affects Versions: Production > Reporter: sbonazzo > Assignee: infra > Labels: yaml > > we have an issue with yamlized jobs: removing them from yaml doesn't disable them and doesn't delete them from jenkins. Example is: > http://jenkins.ovirt.org/job/vdsm_master_create-rpms-el6-x86_64_merged/ > that should have been disabled / removed after job dropped by yaml files with commit 7479c7cde296a6bf8b7202f7483e408470e7e58f -- This message was sent by Atlassian JIRA (v7.2.0-OD-02-009#72000)

1 0

[JIRA] (OVIRT-390) ovirt master publisher broken due to appliance image
by eyal edri [Administrator] (oVirt JIRA) 28 Feb '16

28 Feb '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-390?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-390: -------------------------------------------- Resolution: Fixed Status: Closed (was: New) job was fixed, back to stable: http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/ > ovirt master publisher broken due to appliance image > ---------------------------------------------------- > > Key: OVIRT-390 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-390 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: infra > > Please see [1], failing on : > *00:28:45* Copied 4 artifacts from > "ovirt-register_master_build-artifacts-el7-x86_64 > <http://jenkins.ovirt.org/job/ovirt-register_master_build-artifacts-el7-x86_…>" > build number 11 > <http://jenkins.ovirt.org/job/ovirt-register_master_build-artifacts-el7-x86_…>*00:28:46* > Copied 4 artifacts from > "unboundid-ldapsdk_master_create-rpms-el7-x86_64_merged > <http://jenkins.ovirt.org/job/unboundid-ldapsdk_master_create-rpms-el7-x86_6…>" > build number 2 <http://jenkins.ovirt.org/job/unboundid-ldapsdk_master_create-rpms-el7-x86_6…>*00:30:05* > FATAL: Failed to copy > /var/lib/jenkins/jobs/ovirt-appliance_master_build-artifacts-el7-x86_64/builds/83/archive/exported-artifacts/ovirt-engine-appliance.qcow2 > to /var/lib/jenkins/workspace/ovirt_master_publish-rpms_nightly/artifacts/ovirt-engine-appliance.qcow2*00:30:05* > hudson.util.IOException2 > <http://stacktrace.jenkins-ci.org/search?query=hudson.util.IOException2>: > Failed to copy /var/lib/jenkins/jobs/ovirt-appliance_master_build-artifacts-el7-x86_64/builds/83/archive/exported-artifacts/ovirt-engine-appliance.qcow2 > to /var/lib/jenkins/workspace/ovirt_master_publish-rpms_nightly/artifacts/ovirt-engine-appliance.qcow2*00:30:05* > at hudson.plugins.[WS-CLEANUP] Deleting project > workspace...[WS-CLEANUP] Skipped based on build state > FAILURE*00:30:05* Finished: FAILURE > [1] > http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/330/console > -- > Eyal Edri > Associate Manager > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v7.2.0-OD-02-009#72000)

1 0

No jenkins jobs ran for reports 3.6 branch patch
by Yedidyah Bar David 28 Feb '16

28 Feb '16

Hi, $subject. Patch is [1]. I now pushed [2] for jenkins. Not sure if that's enough, and/or how to verify. Can someone please have a look? Thanks. [1] https://gerrit.ovirt.org/53773 [2] https://gerrit.ovirt.org/54119 -- Didi

2 1

[oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.6_el6_merged - Build # 911 - Failure!
by jenkins＠ovirt.org 25 Feb '16

25 Feb '16

Project: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/9… Build Number: 911 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/54035 ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #911 [pkliczewski] jsonrpc: version update ----------------- Failed Tests: ----------------- No tests ran.

1 0