- Devel - oVirt List Archives

oVirt Integration Development Team weekly status - 2016-03-21
by Sandro Bonazzola 21 Mar '16

21 Mar '16

- *oVirt Integration Development Team weekly status - 2016-03-21* - - oVirt integration open bugs: https://bugzilla.redhat.com/buglist.cgi?quicksearch=classification%3Aovirt%… - 4.0 - master is now stable enough to be tested - working with Node team to streamline NGN build in jenkins - working with Node team supporting NGN cockpit plugins - working with Infra team on packaging new dashboard nodejs based packages - working with Storage team packaging ovirt image uploader daemon - working on migration path from el6 3.6 to el7 4.0 - ovirt-log-collector works again with Fedora on master - 3.6: - Closed 3.6.4 pending bugs - Released oVirt 3.6.4 RC1 - Announce: http://lists.ovirt.org/pipermail/announce/2016-March/000238.html - Release notes: http://www.ovirt.org/release/3.6.4/ - Fixing 3.6.5 bugs - Preparing to release 3.6.4 RC2 - Infra: - Fixed guest agent jenkins jobs - Fixed repoclosure issues on 3.6 snapshot - CentOS Virt SIG: - Next meeting scheduled on Tue 22nd 16:00 CET - LINK: Roadmap and packages list: http://wiki.centos.org/SpecialInterestGroup/Virtualization/Roadmap - LINK: http://wiki.centos.org/HowTos/oVirt - Meeting minutes will be available on https://www.centos.org/minutes/2016/ *Team updates* - Didi - Worked on several bugs/changes, mainly in otopi - Ido: - getting familiar with Hosted engine installation - getting familiar with Lago installation - Lev: - working on few bugs, mostly on ovirt-live - Rafael: - Working to split engine-backup from ovirt-engine-tools package - Working on configuration query tool for otopi - Worked on 3.6.4 RC1 release - Sandro: - Working with Rafael and Simone on 3.6.4 RC1 release - Working with Fabian on ovirt-release for Next Generation Node - Finishing presentation for Incotro DevOps @ Bologna - Simone: - Worked on hosted-engine compatibility issues with python SDK on master - Adding an additional CLI option to let the user pass a custom vm.conf on hosted-engine - Let user add a 3.6 hosted-engine host on a system that was started with 3.4 by scanning all the volume uuids on disk (at 3.4 time they wasn't in the answerfile) -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Re: [ovirt-devel] ovirt-engine_master_upgrade-db-from-3.6_el7_created test fails with fatal error
by Maor Lipchuk 21 Mar '16

21 Mar '16

Hi all, I'm getting the following error (see [1]) every time when I send a DB patch. any idea what seems to be wrong? [1] fatal: ambiguous argument 'origin/ovirt-engine-3.6': unknown revision or path not in the working tree. see http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-db-from-3.6_el7_cr… Regards, Maor

2 1

Access to memory snapshots?
by Matt Mossholder 17 Mar '16

17 Mar '16

Hi everyone! I am working on developing a plugin for the cuckoo sandbox ( http://cuckoosandbox.org) that will allow users to select oVirt as a virtualiztion solution. I have it working, for the most part, but one area where I need some guidance is in retrieving memory images. I know that when you take a snapshot, you can request that the memory be stored as well. My issue is that I don't see a way to retrieve the memory, so that it can be feed into analysis tools like Volatility ( http://www.volatilityfoundation.org/) Does anyone have any pointers for me? Thanks! --Matt

4 3

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-----

6 6

[ANN] oVirt 3.6.4 First Release Candidate is now available for testing
by Sandro Bonazzola 16 Mar '16

16 Mar '16

The oVirt Project is pleased to announce the availability of the First Release Candidate of oVirt 3.6.4 for testing, as of March 16th, 2016 This release is available now for: * Fedora 22 * Red Hat Enterprise Linux 6.7 * CentOS Linux 6.7 (or similar) * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later * Fedora 22 This release is also available with experimental support for: * Debian 8.3 Jessie This release candidate includes the following updated packages: - ovirt-engine - vdsm - ovirt-hosted-engine-ha - ovirt-hosted-engine-setup See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO is already available [2]. * Mirrors[3] might need up to one day to synchronize. Additional Resources: * Read more about the oVirt 3.6.3 release highlights: http://www.ovirt.org/release/3.6.4/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/3.6.4/ [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Welcome: New ovirt.org website!
by Mikey Ariel 15 Mar '16

15 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Following yesterday's pre-launch email[1], I'm happy to announce that the new ovirt.org[2] website is now live in **public beta** and available for community review. All the information in this email is also available in the first blog post of our shiny new oVirt blog[3]. Read on for information about new features, known issues, and a call for reviews. The old MediaWiki site is still available in read-only[4], and will be taken offline on **March 1, 2016**. This is to ensure that you can compare pages and review migrated content. What's New ========== The new Website is full of improvements and enhancements, check out these highlights: * Source content is now formatted in Markdown instead of MediaWiki. This means that you can create and edit documentation, blog posts, and feature pages with the same Markdown syntax you know. * The Website is deployed with Middleman and stored on GitHub. This means that you can make changes to content with the same GitHub contribution workflow that you know (fork, clone, edit, commit, submit pull request). We even have an "Edit this page on GitHub" link at the bottom of every page! * New layout and design, from breadcrumbs to sidebards and an upgraded landing page. (This is still WIP, please see known issues.) * Automatic redirects from the old MediaWiki site. This means that if the wiki page exists in the new website, previously-released URLs will redirect to that page. If the page was removed, the Search page will open with the page title auto-filled in the search box. * Hierarchical content structure. This means that instead of flat Wiki-style files, the deployed Website reflects an organized source repo with content sorted into directories and sub-directories. * Official oVirt blog! Our new blog welcomes contributions. This means that if you solved a problem with oVirt, want to share your oVirt story, or describe a cool integration, you can submit a pull request with a blog post and we will provide editorial reviews and help publish your posts. * Standardized contribution process. The GitHub repo now includes a README.md[5] file that you can use to learn about how to add and edit content on the website. We welcome pull requests! Known Issues ============ Despite our best efforts, there are still a few kinks with the new website that you should be aware of: * Attempting to navigate to ovirt.org (without www.) leads to a redirect loop. We have a ticket open with OpenShift, our hosting service to fix this. * Only http is available. We also have a ticket with OpenShift to add SSL and enable https. * Home page and Download page are still being upgraded by our UX experts, expect some cool new changes soon! * Feature pages look-and-feel is still under construction. You can still edit and push feature pages as usual. What's Next =========== Even though the Website is live, the work is hardly over. We'd like to ask for your help in: * Reviewing content for anything obsolete or outdated (each page in the new website includes a header toolbar with metadata from the original wiki page for your convenience) * Submitting blog posts or any other content that you wish to share with the oVirt community * Reporting bugs and proposing enhancements, for example broken links or missing pages We hope you will enjoy the new oVirt Website, looking forward to your feedback and contributions! [1] http://lists.ovirt.org/pipermail/devel/2016-February/012372.html [2] http://www.ovirt.org/ [3] http://www.ovirt.org/blog/2016/02/welcome-to-new-ovirt-site/ [4] http://old.ovirt.org/Home [5] https://github.com/oVirt/ovirt-site/blob/master/README.md - -- 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 iQEcBAEBCAAGBQJWxztZAAoJEHYPPTOszxHoOF4H/2UeK9JTspw4dYU+pUu8fKqf pSrE9ha3k9KpPnGIAx6VTnbXolNr9tHFiT8gcds1C9CVoMEPrKUxns9CTz3kPYBH /mGYCwQ+ncUNBCn+54uiKmXssaAtpVLnuxh8f1z9BDUoFjoY7ASLTzwXu9XTuH9V C9gaR0iGcRgSmBPjfPuAVWuHgimM068x5Ig2BoMSzAeCM7pO6LwiRzt3xX15xlR4 TMkUWLHdnJ1uL1GH267tMofrMnk25veDPIzuzIaPFjwIuTFgtwnUQI82ULbxcet2 NJ+y/UgwQ9JUQheoQL/oOsnSs244kFl0Vl+GuKMDGZ1FwCfoZerejnhEK+1cK0U= =KQLK -----END PGP SIGNATURE-----

3 4

oVirt 3.6.4 RC1 build starting
by Rafael Martins 15 Mar '16

15 Mar '16

Fyi oVirt products maintainers, An oVirt build for an official release is going to start right now. If you're a maintainer for any of the projects included in oVirt distribution and you have changes in your package ready to be released please: - bump version and release to be GA ready - tag your release within git (implies a GitHub Release to be automatically created) - build your packages within jenkins / koji / copr / whatever - verify all bugs on MODIFIED have target release and target milestone set. Thanks, Rafael

1 0

oVirt 3.6.4 RC1 merge / tag / bugzilla reminder
by Rafael Martins 14 Mar '16

14 Mar '16

All stable branch maintainers, please make sure to merge all relevant open bugs until Tuesday morning 11:00 AM TLV time. https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A3.6.… Every package build (i.e oVirt product) - please make sure every bug in MODIFIED has the right Target Release and Target Milestone. A Target release should state the version of the package you're building and should include the same version you used for the tag you just used for this build. (e.g. for ovirt-engine, tag: ovirt-engine-3.6.4, tr: 3.6.4) Thanks, Rafael Martins

1 0

oVirt 3.6.4 RC1 build planned
by Rafael Martins 14 Mar '16

14 Mar '16

Fyi oVirt developers, An oVirt build is planned for this Tuesday 11:00 AM TLV time (10:00 AM CET). Taking into consideration the time it takes for Jenkins to run a full CI everything need to be backported by monday 11PM. Please make sure to mark as verified and CR +2 so it will be ready for merging tuesday morning. https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A3.6.… Thanks Rafael Martins

1 0

oVirt Integration Development Team weekly status - 2016-03-14
by Sandro Bonazzola 14 Mar '16

14 Mar '16

- *oVirt Integration Development Team weekly status - 2016-03-14* - - oVirt integration open bugs: https://bugzilla.redhat.com/buglist.cgi?quicksearch=classification%3Aovirt%… - 4.0 - Adapting projects using ovirt-engine-sdk to v3 comaptibility layer - Migrating ovirt-log-collector to SDK 4 being python3 unavailable on v3 compatibility layer. - Rebasing oVirt Live master on new VDSM API - Rebasing Hosted Engine on new VDSM API - Dropped ovirt-host-deploy-offline package, not used anymore by node and ovirt live - oVirt Host Deploy now has pt_BR localization (thanks to *Wesley Morais de Oliveira*) - Infra: - Fixed several jenkins jobs - Disabled / removed all 3.5 jenkins jobs - CentOS Virt SIG: - 3.6.3 rpms have been released within Virt SIG repos - Wki has been updated with references to the new web site. - LINK: Roadmap and packages list: http://wiki.centos.org/SpecialInterestGroup/Virtualization/Roadmap - LINK: http://wiki.centos.org/HowTos/oVirt - Meeting minutes will be available on https://www.centos.org/minutes/2016/ - *Team updates* - Didi - Worked on ovirt-host-deploy for NGN support - Worked on several bugs - Working on OTOPI for 4.0 / NGN - Ido: - getting familiar with Hosted engine installation - getting familiar with Lago installation - Lev: - Working on 3.6.5 this week - Rafael: - Added Fedora 23 support to ovirt-log-collector - Added SDK4 support to packages maintained by integration - Working to split engine-backup from ovirt-engine-tools package - Sandro: - Worked on oVirt Jenkins - Worked on ovirt-release - Worked on ovirt-host-deploy (dropped offline package) - Stabilized oVirt master (SDK and API rebase) - Simone: - Worked hosted-engine bugs for 3.6.4 - Fixing an issue adding an hosted-engine host on a system started on 3.4 - Looking at network stuff for hosted-engine on master -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0