Summary of my 3.5 oVirt Test Day - BZ987953, BZ1110566
by Allon Mureinik
Hi all,
Following is a summary of my experience from the 3.5 Test Day.
As a someone who usually isn't very UX-oriented, I decided to test a couple of UX RFEs, both as a learning experience and out of the thought that a pair of fresh eyes may see things that seasoned UX developers may have become used to overlooking.
I wasted about an hour in the morning trying to recover my dev. env. from the mess I left it in, and ultimately decided it was not a good use of my time, and opted to install RPMs on a VM.
Once I passed that hurdle I played around with both features a bit, and tried to systematically apply them to all the main tabs.
Both features seem to be working properly, although I did stumble across "Bug 1114990 - Clusters main tab is not sorted", which I don't believe is related to either feature, but worth fixing nonetheless.
-Allon
11 years
Call for Papers Deadline in Six Days: Linux.conf.au
by Brian Proffitt
Conference: Linux.conf.au
Information: Each year open source geeks from across the globe gather in Australia or New Zealand to meet their fellow technologists, share the latest ideas and innovations, and spend a week discussing and collaborating on open source projects. The conference is well known for the speakers and delegates depth of talent, and its focus on technical linux content.
Possible topics: Virtualization, oVirt, KVM, libvirt, RDO, OpenStack, Foreman
Date: January 12-15, 2015
Location: Auckland, New Zealand
Website: http://lca2015.linux.org.au/
Call for Papers Deadline: July 13, 2014
Call for Papers URL: http://lca2015.linux.org.au/cfp
Contact me for more information and assistance with presentations.
--
Brian Proffitt
oVirt Community Manager
Project Atomic Community Lead
Open Source and Standards, Red Hat - http://community.redhat.com
Phone: +1 574 383 9BKP
IRC: bkp @ OFTC
11 years
use mvn instead of make to deploy
by Roy Golan
just merged http://gerrit.ovirt.org/#/c/25661/ to help us use mvn to
copy the project artifact instead of make.
usage:
#build and deploy to $OVIRT_ENGINE_PREIFX
mvn clean install -Pmake
#just deploy
mvn install -pl org.ovirt.engine:make -Pmake
#alternative prefix
mvn clean install -Pmake -Dprefix=/path/to/prefix
11 years
[VDSM] VDSM threads as in vdsm 4.15.0
by Francesco Romani
Hi,
I'm trying to enumerate all the daemon threads VDSM uses, as in 4.15.0
(to be exact, as in master 3228f5dad8f488192ea62f4e3e39172832435e80)
So far I got:
===
SocketServer: 1 service, short lived thread per request?
VDSM alone, with no VM running
num what where
--------------------------------------------------------
1 libVirtEventLoop lib/vdsm/libvirtconnection.py
P TaskManager vdsm/storage/hsm.py
1 StorageServer vdsm/storage/storageServer.py
1 StorageRefresh vdsm/storage/hsm.py
1 ChannelListener vdsm/virt/vmchannels.py
1 HostStatsThread vdsm/virt/sampling.py
1 MomThread vdsm/momIF.py
1 clientIF vdsm/clientIF.py
1 HostMonitor mom/HostMonitor.py
1 StompReactor vdsm/rpc/BindingJsonRpc.py
1 JsonRpcServer vdsm/rpc/BidningJsonRpc.py
1 GuestManager mom/GuestManager.py
1 PolicyEngine mom/PolicyEngine.py
1 XmlRpcServer? vdsm/rpc/BindingXMLRPC.py
1 Detector vdsm/clientIF.py
1 RPCServer mom/RPCServer.py
1 SocketServer stdlib, triggered by vdsm/rpc/BindingXMLRPC.py
1 IOProcess? vdsm/storage/outOfProcess.py
S DomainMonitor vdsm/storage/domainMonitor.py
P/2 HSM_MailMonitor vdsm/storage/storage_mailbox.py
P/2 SPM_MailMonitor vdsm/storage/storage_mailbox.py
P = pool size (config/irs/thread_pool_size)
Total: 17 + number(StorageDomains) + P * 2
Total with defaults (P=10) = 37 + number(StorageDomains)
Minimum storage domains: 2 (ISO + data)
Baseline: 39 threads
Per VM
1 sampling vdsm/virt/sampling.py
1 GuestMonitor mom/GuestMonitor.py
===
More precise update will follow. In the meantime, anyone please feel free to
point out omissions/errors.
Thanks,
--
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani
11 years
Re: [ovirt-devel] compile vdsm and attach it to a engine
by Nir Soffer
----- Original Message -----
> From: "aaron Beein" <aaronbeein(a)gmail.com>
> To: "Nir Soffer" <nsoffer(a)redhat.com>
> Cc: devel(a)ovirt.org
> Sent: Sunday, July 6, 2014 12:58:44 PM
> Subject: Re: [ovirt-devel] compile vdsm and attach it to a engine
>
> Thank you very much for your patient explanation.
> According to your clues, I selected the centos6.5 and I I've succeeded
> to add my host which contains a compiled vdsm to a engine.
>
> I am working on Cloud Computing and Virtualization. And I like them.
> May be I will modify the vdsm code in the future. So this is the first
> step to
> use modified vdsm.
>
> Thanks again for your help.
When you do have some nice modification, please share it with us.
Nir
>
> aaron
>
> 2014-07-06 3:56 GMT+08:00 Nir Soffer <nsoffer(a)redhat.com>:
> > ----- Original Message -----
> >> From: "aaron Beein" <aaronbeein(a)gmail.com>
> >> To: devel(a)ovirt.org
> >> Sent: Thursday, July 3, 2014 5:16:15 AM
> >> Subject: [ovirt-devel] compile vdsm and attach it to a engine
> >>
> >> Thank you for your great job on ovirt and vdsm. Now I devote myself to
> >> compile vdsm on centos 6.3 host and attach it to a ovirt engine. But when
> >> I
> >> attach the host which contains a compiled vdsm to a ovirt engine , the
> >> status of the host is always ‘Non Responsive’(step 11 below).
> >
> > I think those pages are misleading.
> >
> > 1. First Centos 6.3 is too old, I think that current vdsm requires Centos
> > 6.5.
> > Using old version you may have missing packages.
> > Do you have specific reason to use this version?
> >
> > 2. Why do you want to compile vdsm? Do you plan to modify vdsm or you just
> > need a version that works on your machine?
> >
> > 3. If you want to develop vdsm, first prepare the host:
> >
> > 1. Install on the host one of the supported versions - RHEL 6.5, Centos
> > 6.5
> > or Fedora 19. Fedora 20 should also work.
> >
> > 2. http://www.ovirt.org/Vdsm_Developers#Installing_required_packages
> >
> > 3. http://www.ovirt.org/Vdsm_Developers#Getting_the_source
> >
> > 4. http://www.ovirt.org/Vdsm_Developers#Building_a_Vdsm_RPM
> >
> > 5. You don't need anything else on that page (but see bellow)
> >
> > 4. Add the host to ovirt engine
> >
> > The best way is to do it from the engine, before you install your vdsm
> > you built
> > from source. This will configure network and certificates and will make
> > your life
> > easier.
> >
> > Do not disable ssl or installation from engine, it will only make it
> > more
> > complex for yourself.
> >
> > So add the host the engine - it will install the lastest stable vdsm
> > version
> > on this host and it should be up in few minuets.
> >
> > 5. Install new vdsm version
> >
> > This is the step you will do again and again when developing vdsm.
> >
> > 1. On the engine side, move the host to maintenance
> >
> > 2. On the host, remove vdsm:
> >
> > yum remove -y vdsm\*
> >
> > This is required because the way we version master builds. A version
> > you
> > build from source will typically have older version number compared
> > with
> > latest stable version. Removing vdsm is quick and solve this
> > versioning
> > mess.
> >
> > 3. And install the rpm packages as described in:
> > http://www.ovirt.org/Vdsm_Developers#Basic_installation
> >
> > Important note: the command to install vdsm in the wiki assume that
> > you have only one version of the rpm in rpmbuild/RPMS/*/. If you have
> > multiple versions your installation will fail with strange errors.
> >
> > The best way to avoid this is to remove the RPMS direcotory before you
> > build new rpm. If you want to keep multiple rpms version move them
> > elsewhere
> > after you build.
> >
> > If you have trouble, please attach engine.log and vdsm.log. We cannot help
> > if
> > all the info we have is "host is non-responsive".
> >
> >
> > Nir
> >
> >
> >
> >
> >
> >
> >
>
11 years
ovirt test day report - make ovirt easy configurable to allow redirection of all logs to syslog
by Alona Kaplan
During the test day I tested -
Bug 1078738 - OVIRT35 - [RFE] make ovirt easy configurable to allow redirection of all logs to syslog
There was no feature page so it was very hard to understand how this feature should be tested.
The build contains only a patch that tailors the api to the engine.
abarlev sent me an external rpm with the syslog extension- tested it on f19, seems to work fine.
Alona.
11 years
Summary of my 3.5 oVirt Test Day - BZ1108866, BZ1108866
by Maor Lipchuk
Hi all,
I was testing two features of 3.5 in the oVirt test day
The first feature was: [RFE] Maintenance operations on a VM would ask for an optional reason (BZ1108866)
The feature provides the ability to present a message to the user regarding the reason why this VM has been shutdown.
It seems to work very well except when using shutdown while the VM is powering up or shutting down, then the message gets deleted.
The other feature I was testing was: Allow to clone a (down) VM without snapshot/template (BZ1108866)
This feature provides the ability to clone a VM from the VM itself, instead do it from a snapshot.
I have tested many different scenarios such as cloning a VM which was in PREVIEW, VM containing shared disks and read only disks.
The feature works very well, and the previewed VM which was cloned, was similar to the cloned one.
Regards,
Maor
11 years
compile vdsm and attach it to a engine
by aaron Beein
Hi,
Thank you for your great job on ovirt and vdsm. Now I devote myself to
compile vdsm on centos 6.3 host and attach it to a ovirt engine. But when I
attach the host which contains a compiled vdsm to a ovirt engine , the
status of the host is always ‘Non Responsive’(step 11 below). I reference
the links below:
http://www.ovirt.org/Vdsm_Developers
http://www.ovirt.org/Installing_VDSM_from_rpm
The steps( 1-9 ) are executed on centos6.3 host, and the steps(10--11) are
executed on ovirt engine. So I would be very grateful if you can give me
some clues that if I've missed anything or I done something wrong.
The attachment is the same as the bellow which makes it easier for you to
read.
1 Deployment platform
Centos6.3
Linux bogon 2.6.32-431.20.3.el6.x86_64 #1 SMP Thu Jun 19 21:14:45 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
Ip ： 10.1.8.252
CPU supports hardware virtualization extensions:
# cat /proc/cpuinfo | egrep 'svm|vmx'| grep nx
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr
pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave lahf_lm arat epb
xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr
pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave lahf_lm arat epb
xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid
2 Apply all updates # yum -y update 3 Installing required packages
RHEL 6 users must add EPEL yum repository for installing python-ordereddict
and pyton-pthreading. The rpm bellow will install the epel yum repo and
required gpg keys.
# yum install http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch...
RHEL 6 users must install a newer pep8 version than the one shipped in
EPEL6. Older pep8 versions have a bug that's tickled by vdsm. You can use
`pip`, or
yum install http://danken.fedorapeople.org/python-pep8-1.4.5-2.el6.noarch.rpm
oVirt repo:
yum install http://resources.ovirt.org/releases/ovirt-release.noarch.rpm
RHEL 6 users must add the glusterfs repository, providing newer glusterfs
not available on RHEL 6. Optionally install 'wget' if not present
rpm -q wget 2> /dev/null || yum install wget
wget -O /etc/yum.repos.d/glusterfs-epel.repo
*http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/glusterfs-epel.repo*
<http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/gluste...>
Fedora and RHEL 6 users must verify the following packages are installed
before attempting to build:
yum install make autoconf automake pyflakes logrotate gcc python-pep8
libvirt-python python-devel \
python-nose rpm-build sanlock-python genisoimage python-ordereddict
python-pthreading libselinux-python\
python-ethtool m2crypto python-dmidecode python-netaddr
python-inotify python-argparse git \
python-cpopen bridge-utils libguestfs-tools-c pyparted openssl libnl
libtool gettext-devel python-ioprocess libvirt libvirt-client
libvirt-lock-sanlock
4 Getting the source
cd /root
git clone *http://gerrit.ovirt.org/p/vdsm.git*
<http://gerrit.ovirt.org/p/vdsm.git>
cd vdsm
5 Building a Vdsm RPM
./autogen.sh –system
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
--libdir=/usr/lib --enable-hooks
make rpm NOSE_EXCLUDE=.*
6 Basic installation and start
When building from source, you should enable the ovirt-beta repository, to
satisfy dependencies that are not available yet in the release repository.
# cd ~/rpmbuild/RPMS
# yum install --skip-broken
--enablerepo=ovirt-master-snapshot-static x86_64/* noarch/vdsm-xml*
noarch/vdsm-cli* noarch/vdsm-python-zombiereaper*
noarch/vdsm-*jsonrpc*
Before starting vdsmd service for the first time vdsm requires some
configuration procedures for external services that being used by vdsmd. To
ease this process vdsm provides a utility (vdsm-tool). To perform full
reconfiguration of external services perform:
# vdsm-tool configure --force
(for more information read "vdsm-tool --help")
7 Finally start the vdsmd service
# service vdsmd start
8 Yum install -y bridge-utils
Configuring the bridge Interface as below
Disable the network manager service by executing as root:
systemctl stop NetworkManager.service
systemctl disable NetworkManager.service
service network start
chkconfig network on
Add the following content into a new file named:
*/etc/sysconfig/network-scripts/ifcfg-ovirtmgmt*:
DEVICE=ovirtmgmt
TYPE=Bridge
ONBOOT=yes
DELAY=0
BOOTPROTO=static
IPADDR=10.1.8.252
NETMASK=255.255.255.0
GATEWAY=10.1.8.254
Add the following line into the configuration file of your out going
interface (usually em1/eth0) the file is located at:
*/etc/sysconfig/network-scripts/ifcfg-em1* (assuming the device is em1)
BRIDGE=ovirtmgmt
and remove the IPADDR, NETMASK and BOOTPROTO keys, since the interface
should not have an IP address of its own. Full Example
DEVICE=em1
ONBOOT=yes
BRIDGE=ovirtmgmt
Restart the network service by executing:
service network restart
*Note that if any other bridge (from ovirtmgmt) is present at the time of
host installation, the bridge creation operation is skipped and you have to
change the bridge settings to correspond to above shown configuration
manually.*
*9 Configuring VDSM*
Add the following content into the file: */etc/vdsm/vdsm.conf* (you may
need to create that file):
[vars]
ssl = false
Restart the vdsmd service by executing:
service vdsmd restart
If Vdsm was started earlier with ssl=true, it would refuse to start and you
may need to use the undocumented verb
service vdsmd reconfigure
service vdsmd start
which edits */etc/libvirt/qemu.conf* and changes *spice_tls=1* to
*spice_tls=0*.
10 Connect to overt-engine
*ref: OVirt_-_connecting_development_vdsm_to_ovirt_engine
<http://www.ovirt.org/OVirt_-_connecting_development_vdsm_to_ovirt_engine>.*
*su - postgres -c "psql engine -c \"UPDATE vdc_options set option_value =
'true' where option_name = 'InstallVds'\""*
*service overt-engine restart*
11 Attach the host to the engine
I login the engine Administration Portal , and attach the centos host to a
cluster. But it failed.
11 years
Re: [ovirt-devel] ovirt-engine-3.5 branching
by Oved Ourfali
On Jul 3, 2014 8:27 PM, Antoni Segura Puimedon <asegurap(a)redhat.com> wrote:
>
>
>
> ----- Original Message -----
> > From: "Allon Mureinik" <amureini(a)redhat.com>
> > To: "Oved Ourfali" <ovedo(a)redhat.com>
> > Cc: "Piotr Kliczewski" <pkliczew(a)redhat.com>, devel(a)ovirt.org
> > Sent: Thursday, July 3, 2014 4:57:55 PM
> > Subject: Re: [ovirt-devel] ovirt-engine-3.5 branching
> >
> > I concur.
> >
> > There are too many flows broken on /master/ to consider the 3.5 branch
> > anything remotely near "stable".
>
> Wouldn't it be better to keep the current branch as "stabilization branch"
> and test extensively every patch that goes into it instead of keeping adding
> to the master branch and rebranch and then have the same or similar happen
> in the next test day?
>
> If I remember correctly in the previous release cycle something similar happened
> in the engine an teams tried to push non critical or stabilization patches
> after feature freeze. At the time, it was argued that this release cycle it
> would be branch and backport.
>
> I realize, of course, that it is painstaking to backport a great amount of
> patches, but this is a direct result of letting features get merged too late
> in the cycle and before being up to a certain standard of stability.
>
> I would say "let this backporting frenzy be a lesson to all to be more conservative
> with the timelines in the next cycle" but I understand the other side of the
> argument, so maybe instead we should just count with an extra week between
> freeze and branching (note that this will delay review and merge of work
> on master for the next feature reducing the chances of big features being
> merged early-middle cycle.
>
I think that we all learn the lesson here, and we are just increasing the risk of having things not back ported due to human error, and by that reducing the stabilization... While we know that a lot was fixed. And also some bugs, and not just things that were added at the last minute.
> >
> > wrt to holding off 3.6 features, I can confirm that from the storage side
> > nothing has been merged, and we can keep holding them back.
> >
> >
> > -Allon
> >
> > ----- Original Message -----
> > > From: "Oved Ourfali" <ovedo(a)redhat.com>
> > > To: devel(a)ovirt.org
> > > Cc: "Piotr Kliczewski" <pkliczew(a)redhat.com>
> > > Sent: Thursday, July 3, 2014 5:31:43 PM
> > > Subject: [ovirt-devel] ovirt-engine-3.5 branching
> > >
> > > Hi all,
> > >
> > > The test day revealed a large amount of issues. These issues are being
> > > addressed in the last few days.
> > > To avoid the need to back-port each and every one of them to the
> > > ovirt-engine-3.5 stable branch, I suggest to give a few days for that
> > > effort,
> > > and revisit it on mid next week, to asses it again and decide whether to do
> > > the branching then.
> > >
> > > I ask the different maintainers not to push 3.6 relevant material into
> > > master
> > > in the next few days, until the branching is done.
> > > To my knowledge no major (or any) patch related to 3.6 has been merge on
> > > master, but please correct me if I'm wrong.
> > >
> > > Thanks all for your efforts in stabilizing the version.
> > >
> > > Regards,
> > > Oved
> > > _______________________________________________
> > > Devel mailing list
> > > Devel(a)ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/devel
> > >
> > _______________________________________________
> > Devel mailing list
> > Devel(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> >
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
11 years
