- Infra - oVirt List Archives

[JIRA] (OVIRT-422) Create jenkins job to compose ovirt 4.0 snaphost early builds
by eyal edri [Administrator] (oVirt JIRA) 22 Feb '16

22 Feb '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-422?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-422: ------------------------------------------------- [~sbonazzola(a)redhat.com] do you know if anyone from the infra team can handle it? > Create jenkins job to compose ovirt 4.0 snaphost early builds > ------------------------------------------------------------- > > Key: OVIRT-422 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-422 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins, repoman > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > We need a more static 4.0 snapshots that will be able to be consumed by people who want to verify a certain build without having a rolling nightly build. > * Add a jjb jenkins job that will run manually/once a week and will create a snap 4.0 repo on > resources.ovirt.org from latest nightlies (will need to create the repo on resources.ovirt.org/pub/ovirt-4.0/ > * Use repoman with the following cmd: "/usr/bin/repoman ovirt_4.0.0_snap1 add conf:ovirt-4.0-snapshots.repoman --keep-latest 1" [1] > * This should collect all latest nightlies for 4.0 into a build dir called ovirt_4.0.0_snap1 > * We'll run repoclosure on it once the copy is finished > * run sanity (either manually or via Lago manual if possible) > * rhevh team run sanity on the node builds from nightly > * Create latest_4.0.0_snapshot link to the repo and update it on each release + create new release rpm with that link. > * Move bugs - either move all MODIFIED bugs with target milestone ovirt-4.0.0 or move only bugs with bug-url from the commit msg. > * Send email to users/devel with info on release (list of bugs + link to release rpm). > [2] cat ovirt-4.0-snapshots.repoman (the conf file) > rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot:latest > rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot-static:latest -- This message was sent by Atlassian JIRA (v7.2.0-OD-01-031#72000)

1 0

[JIRA] (OVIRT-422) Create jenkins job to compose ovirt 4.0 snaphost early builds
by eyal edri [Administrator] (oVirt JIRA) 22 Feb '16

22 Feb '16

eyal edri [Administrator] created OVIRT-422: ----------------------------------------------- Summary: Create jenkins job to compose ovirt 4.0 snaphost early builds Key: OVIRT-422 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-422 Project: oVirt - virtualization made easy Issue Type: Task Components: Jenkins, repoman Reporter: eyal edri [Administrator] Assignee: infra Priority: Highest We need a more static 4.0 snapshots that will be able to be consumed by people who want to verify a certain build without having a rolling nightly build. * Add a jjb jenkins job that will run manually/once a week and will create a snap 4.0 repo on resources.ovirt.org from latest nightlies (will need to create the repo on resources.ovirt.org/pub/ovirt-4.0/ * Use repoman with the following cmd: "/usr/bin/repoman ovirt_4.0.0_snap1 add conf:ovirt-4.0-snapshots.repoman --keep-latest 1" [1] * This should collect all latest nightlies for 4.0 into a build dir called ovirt_4.0.0_snap1 * We'll run repoclosure on it once the copy is finished * run sanity (either manually or via Lago manual if possible) * rhevh team run sanity on the node builds from nightly * Create latest_4.0.0_snapshot link to the repo and update it on each release + create new release rpm with that link. * Move bugs - either move all MODIFIED bugs with target milestone ovirt-4.0.0 or move only bugs with bug-url from the commit msg. * Send email to users/devel with info on release (list of bugs + link to release rpm). [2] cat ovirt-4.0-snapshots.repoman (the conf file) rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot:latest rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot-static:latest -- This message was sent by Atlassian JIRA (v7.2.0-OD-01-031#72000)

1 0

[oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.5_el6_merged - Build # 914 - Failure!
by jenkins＠ovirt.org 22 Feb '16

22 Feb '16

------=_Part_32_668489780.1456135336446 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.5_el6_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.5_el6_merged/9… Build Number: 914 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/53767 ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #914 [Alona Kaplan] engine: No validation for 'passthrough' profile DCs less than 3.6 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_32_668489780.1456135336446--

1 0

Fwd: Infra post from no-reply@rhcloud.com requires approval
by Eyal Edri 22 Feb '16

22 Feb '16

Related to the site migration? ---------- Forwarded message ---------- From: <infra-owner(a)ovirt.org> Date: Feb 18, 2016 6:15 PM Subject: Infra post from no-reply(a)rhcloud.com requires approval To: <infra-owner(a)ovirt.org> Cc: As list administrator, your authorization is requested for the following mailing list posting: List: Infra(a)ovirt.org From: no-reply(a)rhcloud.com Subject: WARNING: Quota exceeded on wiki-ovirt.rhcloud.com Reason: SpamAssassin identified this message as possible spam (score 3.3) At your convenience, visit: http://lists.ovirt.org/mailman/admindb/infra to approve or deny the request. ---------- Forwarded message ---------- From: OpenShift guest <no-reply(a)rhcloud.com> To: infra(a)ovirt.org Cc: Date: Thu, 18 Feb 2016 11:10:04 -0500 Subject: WARNING: Quota exceeded on wiki-ovirt.rhcloud.com Disk quotas for user 847edb45aea84198838f915be6faa066 (uid 3689): Filesystem blocks quota limit grace files quota limit grace /dev/mapper/EBSStore01-user_home01 18596M 0 20006M 31144 0 800k ---------- Forwarded message ---------- From: infra-request(a)ovirt.org To: Cc: Date: Thu, 18 Feb 2016 11:15:33 -0500 Subject: confirm 9cfdf5334ff27f7a4f5a4093265e5035944d94b1 If you reply to this message, keeping the Subject: header intact, Mailman will discard the held message. Do this if the message is spam. If you reply to this message and include an Approved: header with the list password in it, the message will be approved for posting to the list. The Approved: header can also appear in the first line of the body of the reply.

2 1

https/ssl cert on www.ovirt.org
by Yedidyah Bar David 22 Feb '16

22 Feb '16

Firefox tells me: www.ovirt.org uses an invalid security certificate. The certificate is only valid for the following names: *.rhcloud.com, rhcloud.com (Error code: ssl_error_bad_cert_domain) Please handle. Thanks. -- Didi

2 1

fc21-scratchpad-test.phx.ovirt.org - Is this jenkins slave gone?
by Fabian Deutsch 22 Feb '16

22 Feb '16

Hey, http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-fc22-x86_… is not building for a while, and it seems that this is because a specific slave is missing. Does someone know why it is missing or when it will be back? - fabian

1 0

Re: [ovirt-users] ovirt-guest-agent puppet module available for testing
by Eyal Edri 21 Feb '16

21 Feb '16

Hi Rene, Adding the oVirt infra list. It might be useful to use it to manage the jenkins slaves that are running on oVirt right now. Not sure if we are guest agent installed on them right now, but this can come in handy since we use puppet to maintain oVirt infra. e. On Fri, Feb 19, 2016 at 8:16 AM, René Koch <rkoch(a)rk-it.at> wrote: > Hi, > > As I'm trying to manage my infrastructure using puppet, I figured out that > there's no puppet module available for installing and configuring > ovirt-guest-agent (or at least I couldn't find one). So I created a module, > which is tested on Debian 7/8 (please see Readme for limitations) and > CentOS/Scientifc Linux/RHEL 6/7. Other operating systems will follow soon... > > If you're using puppet, feel free to test this module and leave me some > feedback: > https://forge.puppetlabs.com/scrat14/ovirt_guest_agent > > > Regards, > René > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > -- Eyal Edri Associate Manager EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

2 1

Welcome: New ovirt.org website!
by Mikey Ariel 21 Feb '16

21 Feb '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-----

2 1

[JIRA] (OVIRT-421) checkout rhev_check3 as monitoring plugin for icingna for ovirt systems
by eyal edri [Administrator] (oVirt JIRA) 21 Feb '16

21 Feb '16

eyal edri [Administrator] created OVIRT-421: ----------------------------------------------- Summary: checkout rhev_check3 as monitoring plugin for icingna for ovirt systems Key: OVIRT-421 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-421 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra I'm happy to announce version 1.5 of check_rhev3. check_rhev3 is a monitoring plugin for Icinga/Nagios and it's forks, which is used to monitor datacenters, clusters, hosts, vms, vm pools and storage domains of Red Hat Enterprise Virtualization (RHEV) and oVirt virtualization environments. Download this plugin from: https://github.com/ovido/check_rhev3/releases/check_rhev3-1.5 For further information on how to install this plugin visit: https://github.com/ovido/check_rhev3/wiki/Installation-Documentation A detailed usage documentation can be found here: https://github.com/ovido/check_rhev3/wiki/Usage-Documentation Changelog: - New features: - Set cluster to warning if host is in maintenance mode instead of critical (Issue #27) - New storage domain check: -s overall-usage (Issue #28) - Display more detailed information of host and vm status (Issue #35) Bugs fixed: - Wrong CPU Usage on hypervisor maintenance (Issue #26) - Discrepancy in DataCenter Storage usage Output. (Issue #28) - Wrong CPU value for vms (Issue #29) - VM CPU usage graphs show values over 100% (Issue #33) - Unsuccessful stat on filename containing newline (Issue #36) - align behaviour for check_statistics cpu to memory (Issue #39) If you have any questions or ideas, please drop me an email: rkoch(a)rk-it.at. Thank you for using check_rhev3. -- This message was sent by Atlassian JIRA (v7.2.0-OD-01-031#72000)

1 0

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 2086 - Failure!
by jenkins＠ovirt.org 19 Feb '16

19 Feb '16

------=_Part_17_2103039032.1455898241246 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: 2086 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/53754 ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #2086 [Vinzenz Feenstra] frontend: Only warn on timezone difference for Windows VMs [Sandro Bonazzola] build_mock_srcrpm_releng: fix archiving ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_17_2103039032.1455898241246--

1 0