[oVirt Jenkins] ovirt_engine_upgrade_params - Build # 52 - Still Failing!
Project: http://jenkins.ovirt.org/job/ovirt_engine_upgrade_params/ Build: http://jenkins.ovirt.org/job/ovirt_engine_upgrade_params/52/ Build Number: 52 Build Status: Still Failing Triggered By: Started by user Kiril Nesenko - Changes Since Last Success: - Changes for Build #31 Changes for Build #48 [Sandro Bonazzola] Add new option to the answer file Changes for Build #49 Changes for Build #50 Changes for Build #51 Changes for Build #52 - Failed Tests: - No tests ran. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[oVirt Jenkins] check_gerrit_ovirt_org - Build # 91499 - Fixed!
Project: http://jenkins.ovirt.org/job/check_gerrit_ovirt_org/ Build: http://jenkins.ovirt.org/job/check_gerrit_ovirt_org/91499/ Build Number: 91499 Build Status: Fixed Triggered By: Started by timer - Changes Since Last Success: - Changes for Build #91497 Changes for Build #91498 Changes for Build #91499 - Failed Tests: - No tests ran. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: Moving to new infra vendor for the oVirt project
- Original Message - From: Eyal Edri ee...@redhat.com To: infra infra@ovirt.org Sent: Thursday, December 19, 2013 8:43:16 AM Subject: Moving to new infra vendor for the oVirt project Hi, Due to some technical difficulties and current experience we have decide to switch hosting provider for the oVirt project, to host mostly the Jenkins infra (jenkins slave mostly), but potentially alterway servers as well (for production servers). I would like to hear your thoughts about which servers and HW requirements we need for the infra. The proposed infra layout: === 1. ovirt-engine 3.3.x stable manager to run on a VM[1] 2. 3 bare-metal servers to serve as hypervisors for jenkins slaves and nested vms for automation tests. [2] we'll expect to run at least 4 VMs on each hypervisor for various jenkins slaves, and have the ability to take one host for maintanance w/o affecting the infra downtime too much. 3. external storage for a storage domain (NFS or ISCSI) and backups for all oVirt services. [3] +1 for NFS 4. possibly manage alterway servers on the same ovirt-engine instance if performance won't decline. (we can request for a european datacenter if that will reduce latency). we might want to install another foreman-proxy on that DC to allow installing VMs locally. we will want to migrate the jenkins server which is hosted on bare-metal now on alterway to a VM as well. 5. fast network connection [4] We need to decide on the optimal hardware for this infrastructure, going forward with the oVirt project expanding and needing more resources. an initial estimation for the hardware: (feel free to pitch in and propose/change) === [1] engine VM should have 16GB RAM and 200GB disk, i'm not sure about which CPU will be optimal yet - thoughts? [2] bare metal hosts should have 48GB ram (with option to expand to 96 if needed), no need for too much HD space if we're going to use external storage servers. available servers are: http://www.softlayer.com/dedicated-servers/dual-processor-servers [3] 2TB NAS or Iscsi storage for hosting backups and storage domain for all the VMs [4] they offer public bandwitch of 5000GB, and a choise of uplink speeds - 100mbps for public and private network for no-extra charge or 1GBPS uplink for extra cost. ** current infra on RAX ** our current infra on RAX includes: (generally was OK, but not great performance, low of storage, and slow since we uses local storage) 3 RAX is DELL PowerEdge R720, with specs: 32 GB DELL RAM, GB Memory: 32 Single Socket Six Core Intel Xeon E5-2640 2.5GHz, #Processors: 1, #Cores per Proc: 6 Hard Drive 100GB-2TB (only one server with 2TB, others have 100/300 GB) SAS 7.2K RPM Drive, HDD RPM: 7200, GB Hard Drive: 2048 1GB network. please weigh in your input asap, so we can push forward with migrating to the new infra, Eyal. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: Moving to new infra vendor for the oVirt project
- Original Message - From: Ewoud Kohl van Wijngaarden ewoud+ov...@kohlvanwijngaarden.nl To: infra@ovirt.org Sent: Thursday, December 19, 2013 4:22:18 PM Subject: Re: Moving to new infra vendor for the oVirt project On Thu, Dec 19, 2013 at 01:43:16AM -0500, Eyal Edri wrote: Due to some technical difficulties and current experience we have decide to switch hosting provider for the oVirt project, to host mostly the Jenkins infra (jenkins slave mostly), but potentially alterway servers as well (for production servers). I would like to hear your thoughts about which servers and HW requirements we need for the infra. The proposed infra layout: === 1. ovirt-engine 3.3.x stable manager to run on a VM[1] 2. 3 bare-metal servers to serve as hypervisors for jenkins slaves and nested vms for automation tests. [2] we'll expect to run at least 4 VMs on each hypervisor for various jenkins slaves, and have the ability to take one host for maintanance w/o affecting the infra downtime too much. 3. external storage for a storage domain (NFS or ISCSI) and backups for all oVirt services. [3] 4. possibly manage alterway servers on the same ovirt-engine instance if performance won't decline. (we can request for a european datacenter if that will reduce latency). we might want to install another foreman-proxy on that DC to allow installing VMs locally. we will want to migrate the jenkins server which is hosted on bare-metal now on alterway to a VM as well. 5. fast network connection [4] We need to decide on the optimal hardware for this infrastructure, going forward with the oVirt project expanding and needing more resources. an initial estimation for the hardware: (feel free to pitch in and propose/change) === [1] engine VM should have 16GB RAM and 200GB disk, i'm not sure about which CPU will be optimal yet - thoughts? [2] bare metal hosts should have 48GB ram (with option to expand to 96 if needed), no need for too much HD space if we're going to use external storage servers. available servers are: http://www.softlayer.com/dedicated-servers/dual-processor-servers [3] 2TB NAS or Iscsi storage for hosting backups and storage domain for all the VMs [4] they offer public bandwitch of 5000GB, and a choise of uplink speeds - 100mbps for public and private network for no-extra charge or 1GBPS uplink for extra cost. I'd prefer to start with 96GB RAM. You can never have enough RAM ;) I think that 4 slaves per hypervisor isn't all that much given we also want to start supporting multiple operating systems. Let's say we have Fedora, EL and Ubuntu. For each we support 1 or 2 releases (F19, F20, EL5, EL6, Ubuntu latest LTS) that's already 5 distros. With 2 slaves per distro, that's 10 slaves. Then we also sometimes want to start supporting a beta (F21, EL7, Ubuntu next LTS). More RAM can also lower the requirement on storage because of caching. Network wise I may be spoiled, but at $work it's all 1G and more and more 10G so I'd prefer 1G. That said, I don't know the extra cost. It will also depend on if we want to put resources.ovirt.org there. Maybe we can get more community support by setting up a mirrorlist and lower the requirement. That said, +1 to moving. I'm suprised it was this hard to get things going at Rackspace. +1 for 96GB - Kiril ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Minutes :: oVirt infra weekly :: 2013-12-23
Minutes:http://ovirt.org/meetings/ovirt/2013/ovirt.2013-12-23-15.04.html Minutes (text): http://ovirt.org/meetings/ovirt/2013/ovirt.2013-12-23-15.04.txt Log: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-12-23-15.04.log.html Meeting summary --- * Hosting (knesenko, 15:06:42) * LINK: https://www.softlayer.com/services/storagelayer/quantastor-servers (eedri, 15:18:13) * ACTION: conference call to discuss COLO needs to be scheduled by eedri (orc_orc, 15:40:21) * LINK: http://www.ovirt.org/Feature/OvfOnWantedDomains (laravot, 16:01:21) * ACTION: knesenko add jenkins slaves and hypervisors to http://monitoring.ovirt.org/icinga/ (knesenko, 16:03:11) * ACTION: knesenko install one of cacti, munin or graphite (knesenko, 16:09:46) Meeting ended at 16:15:51 UTC. Action Items * conference call to discuss COLO needs to be scheduled by eedri * knesenko add jenkins slaves and hypervisors to http://monitoring.ovirt.org/icinga/ * knesenko install one of cacti, munin or graphite Action Items, by person --- * eedri * conference call to discuss COLO needs to be scheduled by eedri * knesenko * knesenko add jenkins slaves and hypervisors to http://monitoring.ovirt.org/icinga/ * knesenko install one of cacti, munin or graphite * tal * knesenko install one of cacti, munin or graphite * **UNASSIGNED** * (none) People Present (lines said) --- * eedri (119) * orc_orc (55) * knesenko (54) * ewoud (47) * bkp (10) * ovirtbot (6) * dcaro (2) * tal (2) * laravot (1) * nsoffer (1) * skyy111 (1) - Kiril ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Cron root@linode01 /root/bin/send_stats.sh
Sending logs to a host far far away Processing logfile /var/log/httpd/access_log-20131222.gz Pseudo-terminal will not be allocated because stdin is not a terminal. Address 31.15.26.3 maps to lists.ovirt.org, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! Last failed login: Mon Dec 23 21:51:54 UTC 2013 from 61.147.74.223 on ssh:notty There were 30846 failed login attempts since the last successful login. Address 31.15.26.3 maps to lists.ovirt.org, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! /var/log/httpd/access_log-20131222.gz sent to stats.ovirt.org:/var/log/awstats/linode01.ovirt.org/ Processing logfile /var/log/httpd/lists.ovirt.org-access_log-20131222.gz Pseudo-terminal will not be allocated because stdin is not a terminal. Address 31.15.26.3 maps to lists.ovirt.org, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! Last failed login: Mon Dec 23 21:51:54 UTC 2013 from 61.147.74.223 on ssh:notty There were 30846 failed login attempts since the last successful login. Address 31.15.26.3 maps to lists.ovirt.org, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! /var/log/httpd/lists.ovirt.org-access_log-20131222.gz sent to stats.ovirt.org:/var/log/awstats/lists.ovirt.org/ Processing logfile /var/log/httpd/resources.ovirt.org-access_log-20131222.gz Pseudo-terminal will not be allocated because stdin is not a terminal. Address 31.15.26.3 maps to lists.ovirt.org, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! Last failed login: Mon Dec 23 21:51:54 UTC 2013 from 61.147.74.223 on ssh:notty There were 30846 failed login attempts since the last successful login. Address 31.15.26.3 maps to lists.ovirt.org, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! /var/log/httpd/resources.ovirt.org-access_log-20131222.gz sent to stats.ovirt.org:/var/log/awstats/resources.ovirt.org/ And they lived happily ever after ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[oVirt Jenkins] ovirt_engine_upgrade_params - Build # 53 - Still Failing!
Project: http://jenkins.ovirt.org/job/ovirt_engine_upgrade_params/ Build: http://jenkins.ovirt.org/job/ovirt_engine_upgrade_params/53/ Build Number: 53 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last Success: - Changes for Build #31 Changes for Build #48 [Sandro Bonazzola] Add new option to the answer file Changes for Build #49 Changes for Build #50 Changes for Build #51 Changes for Build #52 Changes for Build #53 - Failed Tests: - No tests ran. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[oVirt Jenkins] check_gerrit_ovirt_org - Build # 91610 - Failure!
Project: http://jenkins.ovirt.org/job/check_gerrit_ovirt_org/ Build: http://jenkins.ovirt.org/job/check_gerrit_ovirt_org/91610/ Build Number: 91610 Build Status: Failure Triggered By: Started by timer - Changes Since Last Success: - Changes for Build #91610 - Failed Tests: - No tests ran. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[oVirt Jenkins] check_gerrit_ovirt_org - Build # 91611 - Fixed!
Project: http://jenkins.ovirt.org/job/check_gerrit_ovirt_org/ Build: http://jenkins.ovirt.org/job/check_gerrit_ovirt_org/91611/ Build Number: 91611 Build Status: Fixed Triggered By: Started by timer - Changes Since Last Success: - Changes for Build #91610 Changes for Build #91611 - Failed Tests: - No tests ran. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
