From didi at redhat.com Sun Mar 2 09:32:47 2014 From: didi at redhat.com (Yedidyah Bar David) Date: Sun, 2 Mar 2014 04:32:47 -0500 (EST) Subject: [Engine-devel] hosted-engine rebooting in the middle of setup (was: [vdsm] [Users] [ANN] oVirt 3.4.0 Release Candidate is now available) In-Reply-To: <05A42C7A-7A44-405D-849C-BDCF233469AB@zenfire.com> References: <5310B530.6090504@redhat.com> <05A42C7A-7A44-405D-849C-BDCF233469AB@zenfire.com> Message-ID: <340077152.10472996.1393752767799.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Darrell Budic" > To: "Sandro Bonazzola" > Cc: announce at ovirt.org, "engine-devel" , "arch" , Users at ovirt.org, "VDSM > Project Development" > Sent: Saturday, March 1, 2014 1:56:23 AM > Subject: Re: [vdsm] [Users] [ANN] oVirt 3.4.0 Release Candidate is now available > > Started testing this on two self-hosted clusters, with mixed results. There > were updates from 3.4.0 beta 3. > > On both, got informed the system was going to reboot in 2 minutes while it > was still installing yum updates. > > On the faster system, the whole update process finished before the 2 minutes > were up, the VM restarted, and all appears normal. > > On the other, slower cluster, the 2 minutes hit while the yum updates were > still being installed, and the system rebooted. It continued rebooting every > 3 minutes or so, and the engine console web pages are not available because > the engine doesn?t start. it did this at least 3 times before I went ahead > and reran engine-setup, which completed successfully. The system stopped > restarting and the web interface was available again. A quick perusal of > system logs and engine-setup logs didn?t reveal what requested the reboot. > > That was rather impolite of something to do that without warning :) At least > it was recoverable. Seems like scheduling the reboot while the yum updates > were still running seems like a poor idea as well. Can you please post relevant logs? hosts: /var/log/ovirt-hosted-engine-setup/*, /var/log/ovirt-hosted-engine-ha/*, /var/log/vdsm/* engine: /var/log/ovirt-engine/setup/*, /var/log/ovirt-engine/* You can of course open a bug on bugzilla and attach there logs if you want. Thanks, and thanks for the report! -- Didi From alonbl at redhat.com Sun Mar 2 10:39:16 2014 From: alonbl at redhat.com (Alon Bar-Lev) Date: Sun, 2 Mar 2014 05:39:16 -0500 (EST) Subject: [Engine-devel] [ATN] ovirt-engine dbscritps cleanup (master) In-Reply-To: <1928661724.6478064.1393756285235.JavaMail.zimbra@redhat.com> Message-ID: <1443115816.6478169.1393756756557.JavaMail.zimbra@redhat.com> Hello All, The dbscripts of ovirt-engine master were cleaned up, to match other scripts in tree. Developer visible changes are: 1. Removal of create_schema.sh, upgrade.sh, cleandb.sh, refreshStoredProcedures.sh in favour of single schema.sh script, note the -c parameter. Usage: ./schema.sh [options] -h - This help text. -v - Turn on verbosity (WARNING: lots of output) -l LOGFILE - The logfile for capturing output (def. ) -s HOST - The database servername for the database (def. localhost) -p PORT - The database port for the database (def. 5432) -u USER - The username for the database (def. engine) -d DATABASE - The database name (def. engine) -m MD5FILE - Where to store schema MD5 files (def. ) -c COMMAND - Command: apply|refresh|drop -t - Force cleaning tasks and compensation info. 2. Introduction of schema-dev.sh as a wrapper to schema.sh with defaults as a utility for developers. - always enable md5. - always enable logging. - apply command as default. 3. Shell upgrade script is not receives entire settings via DBFUNC_* environment variables. Regards, Alon Bar-Lev From emesika at redhat.com Sun Mar 2 12:28:00 2014 From: emesika at redhat.com (Eli Mesika) Date: Sun, 2 Mar 2014 07:28:00 -0500 (EST) Subject: [Engine-devel] [ATN] ovirt-engine dbscritps cleanup (master) In-Reply-To: <1443115816.6478169.1393756756557.JavaMail.zimbra@redhat.com> References: <1443115816.6478169.1393756756557.JavaMail.zimbra@redhat.com> Message-ID: <1581639761.11798491.1393763280350.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Alon Bar-Lev" > To: "engine-devel" , "infra" > Cc: "Eli Mesika" > Sent: Sunday, March 2, 2014 12:39:16 PM > Subject: [ATN] ovirt-engine dbscritps cleanup (master) > > Hello All, > > The dbscripts of ovirt-engine master were cleaned up, to match other scripts > in tree. > > Developer visible changes are: > > 1. Removal of create_schema.sh, upgrade.sh, cleandb.sh, > refreshStoredProcedures.sh in favour of single schema.sh script, note the -c > parameter. > > Usage: ./schema.sh [options] > > -h - This help text. > -v - Turn on verbosity (WARNING: lots > of output) > -l LOGFILE - The logfile for capturing output (def. ) > -s HOST - The database servername for the database (def. > localhost) > -p PORT - The database port for the database (def. 5432) > -u USER - The username for the database (def. engine) > -d DATABASE - The database name (def. engine) > -m MD5FILE - Where to store schema MD5 files (def. ) > -c COMMAND - Command: apply|refresh|drop > -t - Force cleaning tasks and compensation info. > > 2. Introduction of schema-dev.sh as a wrapper to schema.sh with defaults as a > utility for developers. > > - always enable md5. > - always enable logging. > - apply command as default. you should use this for create new DB or upgrade the existing one with the same call Example : ./schema-dev.sh -u engine -d engine This will create the engine DB if not exists and upgrade the DB if engine database exists > > 3. Shell upgrade script is not receives entire settings via DBFUNC_* > environment variables. > > Regards, > Alon Bar-Lev > From iheim at redhat.com Sun Mar 2 19:36:47 2014 From: iheim at redhat.com (Itamar Heim) Date: Sun, 02 Mar 2014 21:36:47 +0200 Subject: [Engine-devel] ReST API docs In-Reply-To: References: Message-ID: <5313884F.4020007@redhat.com> On 02/28/2014 08:21 PM, Vikas Kokare wrote: > Only > https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.0/ > has the ReST API document available, and not corresponding versions for > 3.1, 3.2 and 3.3. > > I see differences in 3.0 ReST data structure and what is returned back > from RHEVM 3.2 installation. > > Please point to the REST API Guide for RHEVM 3.2. https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.3/html/Developer_Guide/index.html > > > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > From iheim at redhat.com Sun Mar 2 21:46:00 2014 From: iheim at redhat.com (Itamar Heim) Date: Sun, 02 Mar 2014 23:46:00 +0200 Subject: [Engine-devel] Install rhevm-guest-agent on SLES guest In-Reply-To: <1517939.HdhaHoBtyL@awels> References: <1517939.HdhaHoBtyL@awels> Message-ID: <5313A698.3000303@redhat.com> On 02/21/2014 03:43 PM, Alexander Wels wrote: > Doesn't look like the package exists yet, there is an open bug for it: > https://bugzilla.redhat.com/show_bug.cgi?id=1043471 > > On Friday, February 21, 2014 11:00:40 AM Vikas Kokare wrote: >> We want to install the rhevm-guest-agent package on a virtual machine with >> Suse Linux as the guest OS. The RHEVM 3.2 documentation provides install >> instructions for RHEL and Windows guests but not for Suse Linux. This agent >> is important to monitor virtual resources on guest machines, hence the need. >> How can this be done? > > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > is the suse one relevant for this? http://www.ovirt.org/Feature/GuestAgentOpenSUSE From liran.zelkha at gmail.com Mon Mar 3 12:54:28 2014 From: liran.zelkha at gmail.com (Liran Zelkha) Date: Mon, 3 Mar 2014 14:54:28 +0200 Subject: [Engine-devel] Usage of Dynamic Queries Message-ID: Hi All, As part of an ongoing effort to improve oVirt performance, we're trying to reduce the number of Dynamic Queries usage in the code, and replace it with Postgres stored procedures. You wouldn't believe the performance gain. Please consider before making use of the Dynamic Queries feature - it should ONLY be used for places where users can enter search queries - and not for any other usage. Thanks. Liran -------------- next part -------------- An HTML attachment was scrubbed... URL: From sbonazzo at redhat.com Mon Mar 3 14:25:41 2014 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Mon, 03 Mar 2014 15:25:41 +0100 Subject: [Engine-devel] oVirt 3.4.0 branch creation Message-ID: <531490E5.8060608@redhat.com> Hi, we're going to create ovirt-engine-3.4.0 branch tomorrow morning 09:00 UTC. oVirt 3.4.1 development will continue on ovirt-engine-3.4 branch. Critical fixes for oVirt 3.4.0 GA will need to be pushed to 3.4.0 branch too starting tomorrow morning 09:00 UTC. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From danken at redhat.com Mon Mar 3 14:28:27 2014 From: danken at redhat.com (Dan Kenigsberg) Date: Mon, 3 Mar 2014 14:28:27 +0000 Subject: [Engine-devel] Asynchronous tasks for live merge In-Reply-To: <20140228143016.GC29304@redhat.com> References: <20140228143016.GC29304@redhat.com> Message-ID: <20140303142827.GG17073@redhat.com> On Fri, Feb 28, 2014 at 09:30:16AM -0500, Adam Litke wrote: > Hi all, > > As part of our plan to support live merging of VM disk snapshots it > seems we will need a new form of asynchronous task in ovirt-engine. I > am aware of AsyncTaskManager but it seems to be limited to managing > SPM tasks. For live merge, we are going to need something called > VmTasks since the async command can be run only on the host that > currently runs the VM. > > The way I see this working from an engine perspective is: > 1. RemoveSnapshotCommand in bll is invoked as usual but since the VM is > found to be up, we activate an alternative live merge flow. > 2. We submit a LiveMerge VDS Command for each impacted disk. This is > an asynchronous command which we need to monitor for completion. > 3. A VmJob is inserted into the DB so we'll remember to handle it. > 4. The VDS Broker monitors the operation via an extension to the > already collected VmStatistics data. Vdsm will report active Block > Jobs only. Once the job stops (in error or success) it will cease > to be reported by vdsm and engine will know to proceed. You describe a reasonable way for Vdsm to report whether an async operation has finished. However, may we instead use the oportunity to introduce generic "hsm" tasks? I suggest to have something loosely modeled on posix fork/wait. - Engine asks Vdsm to start an API verb asynchronously and supplies a uuid. This is unlike fork(2), where the system chooses the pid, but that's required so that Engine could tell if the command has reached Vdsm in case of a network error. - Engine may monitor the task (a-la wait(WNOHANG)) - When the task is finished, Engine may collect its result (a-la wait). Until that happens, Vdsm must report the task forever; restart or upgrade are no excuses. On reboot, though, all tasks are forgotten, so Engine may stop monitoring tasks on a fenced host. This may be an over kill for your use case, but it would come useful for other cases. In particular, setupNetwork returns before it is completely done, since dhcp address acquisition may take too much time. Engine may poll getVdsCaps to see when it's done (or timeout), but it would be nicer to have a generic mechanism that can serve us all. Note that I'm suggesting a completely new task framwork, at least on Vdsm side, as the current one (with its broken persistence, arcane states and never-reliable rollback) is beyond redemption, imho. > 5. When the job has completed, VDS Broker raises an event up to bll. > Maybe this could be done via VmJobDAO on the stored VmJob? > 6. Bll receives the event and issues a series of VDS commands to > complete the operation: > a) Verify the new image chain matches our expectations (the snap is > no longer present in the chain). > b) Delete the snapshot volume > c) Remove the VmJob from the DB > > Could you guys review this proposed flow for sanity? The main > conceptual gaps I am left with concern #5 and #6. What is the > appropriate way for VDSBroker to communicate with BLL? Is there an > event mechanism I can explore or should I use the database? I am > leaning toward the database because it is persistent and will ensure > #6 gets completed even if engine is restarted somewhere in the middle. > For #6, is there an existing polling / event loop in bll that I can > plug into? > > Thanks in advance for taking the time to think about this flow and for > providing your insights! From iheim at redhat.com Mon Mar 3 14:36:34 2014 From: iheim at redhat.com (Itamar Heim) Date: Mon, 03 Mar 2014 16:36:34 +0200 Subject: [Engine-devel] Asynchronous tasks for live merge In-Reply-To: <20140303142827.GG17073@redhat.com> References: <20140228143016.GC29304@redhat.com> <20140303142827.GG17073@redhat.com> Message-ID: <53149372.2050203@redhat.com> On 03/03/2014 04:28 PM, Dan Kenigsberg wrote: > On Fri, Feb 28, 2014 at 09:30:16AM -0500, Adam Litke wrote: >> Hi all, >> >> As part of our plan to support live merging of VM disk snapshots it >> seems we will need a new form of asynchronous task in ovirt-engine. I >> am aware of AsyncTaskManager but it seems to be limited to managing >> SPM tasks. For live merge, we are going to need something called >> VmTasks since the async command can be run only on the host that >> currently runs the VM. >> >> The way I see this working from an engine perspective is: >> 1. RemoveSnapshotCommand in bll is invoked as usual but since the VM is >> found to be up, we activate an alternative live merge flow. >> 2. We submit a LiveMerge VDS Command for each impacted disk. This is >> an asynchronous command which we need to monitor for completion. >> 3. A VmJob is inserted into the DB so we'll remember to handle it. >> 4. The VDS Broker monitors the operation via an extension to the >> already collected VmStatistics data. Vdsm will report active Block >> Jobs only. Once the job stops (in error or success) it will cease >> to be reported by vdsm and engine will know to proceed. > > You describe a reasonable way for Vdsm to report whether an async > operation has finished. However, may we instead use the oportunity to > introduce generic "hsm" tasks? > > I suggest to have something loosely modeled on posix fork/wait. > > - Engine asks Vdsm to start an API verb asynchronously and supplies a > uuid. This is unlike fork(2), where the system chooses the pid, but > that's required so that Engine could tell if the command has reached > Vdsm in case of a network error. > > - Engine may monitor the task (a-la wait(WNOHANG)) > > - When the task is finished, Engine may collect its result (a-la wait). > Until that happens, Vdsm must report the task forever; restart or > upgrade are no excuses. On reboot, though, all tasks are forgotten, so > Engine may stop monitoring tasks on a fenced host. > > This may be an over kill for your use case, but it would come useful for > other cases. In particular, setupNetwork returns before it is completely > done, since dhcp address acquisition may take too much time. Engine may > poll getVdsCaps to see when it's done (or timeout), but it would be > nicer to have a generic mechanism that can serve us all. > > Note that I'm suggesting a completely new task framwork, at least on > Vdsm side, as the current one (with its broken persistence, arcane > states and never-reliable rollback) is beyond redemption, imho. > >> 5. When the job has completed, VDS Broker raises an event up to bll. >> Maybe this could be done via VmJobDAO on the stored VmJob? >> 6. Bll receives the event and issues a series of VDS commands to >> complete the operation: >> a) Verify the new image chain matches our expectations (the snap is >> no longer present in the chain). >> b) Delete the snapshot volume >> c) Remove the VmJob from the DB >> >> Could you guys review this proposed flow for sanity? The main >> conceptual gaps I am left with concern #5 and #6. What is the >> appropriate way for VDSBroker to communicate with BLL? Is there an >> event mechanism I can explore or should I use the database? I am >> leaning toward the database because it is persistent and will ensure >> #6 gets completed even if engine is restarted somewhere in the middle. >> For #6, is there an existing polling / event loop in bll that I can >> plug into? >> >> Thanks in advance for taking the time to think about this flow and for >> providing your insights! > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > the way i read Adam's proposal, there is no "task" entity at vdsm side to monitor, rather the state of the object the operation is performed on (similar to CreateVM, where the engine monitors the state of the VM, rather than the CreateVM request). From vfeenstr at redhat.com Mon Mar 3 14:44:40 2014 From: vfeenstr at redhat.com (Vinzenz Feenstra) Date: Mon, 03 Mar 2014 15:44:40 +0100 Subject: [Engine-devel] Install rhevm-guest-agent on SLES guest In-Reply-To: <5313A698.3000303@redhat.com> References: <1517939.HdhaHoBtyL@awels> <5313A698.3000303@redhat.com> Message-ID: <53149558.3030104@redhat.com> On 03/02/2014 10:46 PM, Itamar Heim wrote: > On 02/21/2014 03:43 PM, Alexander Wels wrote: >> Doesn't look like the package exists yet, there is an open bug for it: >> https://bugzilla.redhat.com/show_bug.cgi?id=1043471 >> >> On Friday, February 21, 2014 11:00:40 AM Vikas Kokare wrote: >>> We want to install the rhevm-guest-agent package on a virtual >>> machine with >>> Suse Linux as the guest OS. The RHEVM 3.2 documentation provides >>> install >>> instructions for RHEL and Windows guests but not for Suse Linux. >>> This agent >>> is important to monitor virtual resources on guest machines, hence >>> the need. >>> How can this be done? >> >> _______________________________________________ >> Engine-devel mailing list >> Engine-devel at ovirt.org >> http://lists.ovirt.org/mailman/listinfo/engine-devel >> > > is the suse one relevant for this? > http://www.ovirt.org/Feature/GuestAgentOpenSUSE Only if it is openSUSE, SLES won't currently work though. > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel -- Regards, Vinzenz Feenstra | Senior Software Engineer RedHat Engineering Virtualization R & D Phone: +420 532 294 625 IRC: vfeenstr or evilissimo Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From alitke at redhat.com Mon Mar 3 14:51:15 2014 From: alitke at redhat.com (Adam Litke) Date: Mon, 3 Mar 2014 09:51:15 -0500 Subject: [Engine-devel] Asynchronous tasks for live merge In-Reply-To: <20140303142827.GG17073@redhat.com> References: <20140228143016.GC29304@redhat.com> <20140303142827.GG17073@redhat.com> Message-ID: <20140303145115.GC356@redhat.com> On 03/03/14 14:28 +0000, Dan Kenigsberg wrote: >On Fri, Feb 28, 2014 at 09:30:16AM -0500, Adam Litke wrote: >> Hi all, >> >> As part of our plan to support live merging of VM disk snapshots it >> seems we will need a new form of asynchronous task in ovirt-engine. I >> am aware of AsyncTaskManager but it seems to be limited to managing >> SPM tasks. For live merge, we are going to need something called >> VmTasks since the async command can be run only on the host that >> currently runs the VM. >> >> The way I see this working from an engine perspective is: >> 1. RemoveSnapshotCommand in bll is invoked as usual but since the VM is >> found to be up, we activate an alternative live merge flow. >> 2. We submit a LiveMerge VDS Command for each impacted disk. This is >> an asynchronous command which we need to monitor for completion. >> 3. A VmJob is inserted into the DB so we'll remember to handle it. >> 4. The VDS Broker monitors the operation via an extension to the >> already collected VmStatistics data. Vdsm will report active Block >> Jobs only. Once the job stops (in error or success) it will cease >> to be reported by vdsm and engine will know to proceed. > >You describe a reasonable way for Vdsm to report whether an async >operation has finished. However, may we instead use the oportunity to >introduce generic "hsm" tasks? Sure, I am happy to have that conversation :) If I understand correctly, HSM tasks, while ideal, might be too complex to get right and would block the Live Merge feature for longer than we would like. Has anyone looked into what it would take to implement a HSM Tasks framework like this in vdsm? Are there any WIP implementations? If the scope of this is not too big, it can be completed relatively quickly, and the resulting implementation would cover all known use cases, then this could be worth it. It's important to support Live Merge soon. Regarding deprecation of the current tasks API: Could your suggested HSM Tasks framework be extended to cover SPM/SDM tasks as well? I would hope that a it could. In that case, we could look forward to a unified async task architecture in vdsm. >I suggest to have something loosely modeled on posix fork/wait. > >- Engine asks Vdsm to start an API verb asynchronously and supplies a > uuid. This is unlike fork(2), where the system chooses the pid, but > that's required so that Engine could tell if the command has reached > Vdsm in case of a network error. > >- Engine may monitor the task (a-la wait(WNOHANG)) Allon has communicated a desire to limit engine-side polling. Perhaps the active tasks could be added to the host stats? >- When the task is finished, Engine may collect its result (a-la wait). > Until that happens, Vdsm must report the task forever; restart or > upgrade are no excuses. On reboot, though, all tasks are forgotten, so > Engine may stop monitoring tasks on a fenced host. This could be a good comprimise. I hate the idea of requiring engine to play janitor and clean up stale vdsm data, but there is not much better of a way to do it. Allowing reboot to auto-clear tasks will at least provide some backstop to how long tasks could pile up if forgotten. >This may be an over kill for your use case, but it would come useful for >other cases. In particular, setupNetwork returns before it is completely >done, since dhcp address acquisition may take too much time. Engine may >poll getVdsCaps to see when it's done (or timeout), but it would be >nicer to have a generic mechanism that can serve us all. If we were to consider this, I would want to vet the architecture against all known use cases for tasks to make sure we don't need to create a new framework in 3 months. >Note that I'm suggesting a completely new task framwork, at least on >Vdsm side, as the current one (with its broken persistence, arcane >states and never-reliable rollback) is beyond redemption, imho. Are we okay with abandoning vdsm-side rollback entirely as we move forward? Won't that be a regression for at least some error flows (especially in the realm of SPM tasks)? >> 5. When the job has completed, VDS Broker raises an event up to bll. >> Maybe this could be done via VmJobDAO on the stored VmJob? >> 6. Bll receives the event and issues a series of VDS commands to >> complete the operation: >> a) Verify the new image chain matches our expectations (the snap is >> no longer present in the chain). >> b) Delete the snapshot volume >> c) Remove the VmJob from the DB >> >> Could you guys review this proposed flow for sanity? The main >> conceptual gaps I am left with concern #5 and #6. What is the >> appropriate way for VDSBroker to communicate with BLL? Is there an >> event mechanism I can explore or should I use the database? I am >> leaning toward the database because it is persistent and will ensure >> #6 gets completed even if engine is restarted somewhere in the middle. >> For #6, is there an existing polling / event loop in bll that I can >> plug into? >> >> Thanks in advance for taking the time to think about this flow and for >> providing your insights! -- Adam Litke From iheim at redhat.com Mon Mar 3 14:25:07 2014 From: iheim at redhat.com (Itamar Heim) Date: Mon, 03 Mar 2014 16:25:07 +0200 Subject: [Engine-devel] oVirt February 2014 Updates Message-ID: <531490C3.8060904@redhat.com> 1. Releases - oVirt 3.3.3 was released early in the month: http://www.ovirt.org/OVirt_3.3.3_release_notes - oVirt 3.3.4 about to release. http://www.ovirt.org/OVirt_3.3.4_release_notes - oVirt 3.4.0 about to release! 2. Events - Leonardo Vaz is organizing ovirt attendance at FISL15, the largest FOSS conference in LATAM which will happen from 7th to 10th of May in Porto Alegre, Brazil: http://softwarelivre.org/fisl15 - Allon Mureinik gave a presentation on DR with oVirt at devconf.cz http://www.slideshare.net/AllonMureinik/dev-conf-ovirt-dr - oVirt workshop in korea slides (korean) http://www.slideshare.net/rogan/20140208-ovirtkorea-01 https://www.facebook.com/groups/ovirt.korea - Rogan also presented oVirt integration with OpenStack in OpenStack day in Korea http://alturl.com/m3jnx - Pat Pierson posted on basic network setup http://izen.ghostpeppersrus.com/setting-up-networks/ - Fosdem 2014 sessions (slides and videos) are at: http://www.ovirt.org/FOSDEM_2014 - and some at Infrastructure.Next Ghent the week after forsdem. 3. oVirt Activity (software) - oVirt Jenkins plugin by Dustin Kut Moy Cheung to control VM slaves managed by ovirt/RHEV https://github.com/thescouser89/ovirt-slaves-plugin - Opaque oVirt/RHEV/Proxmox client and source code released https://play.google.com/store/apps/details?id=com.undatech.opaque - great to see the NUMA push from HP: http://www.ovirt.org/Features/NUMA_and_Virtual_NUMA http://www.ovirt.org/Features/Detailed_NUMA_and_Virtual_NUMA 4. oVirt Activity (blogs, preso's) - oVirt's has been accepted as a mentoring project for the Google Summer of Code 2014. - Oved Ourfali posted on "Importing Glance images as oVirt templates" http://alturl.com/h7xid - v2v had seen many active discussions. here's a post by Jon Archer on how to Import regular kvm image to oVirt or RHEV http://jonarcher.info/2014/02/import-regular-kvm-image-ovirt-rhev/ - great reviews on amazon.com for "Getting Started with oVirt 3.3" http://alturl.com/5rk2p - oVirt Deep Dive 3.3 slides (Chinese) http://www.slideshare.net/mobile/johnwoolee/ovirt-deep-dive# - oVirt intro video (russian) http://alturl.com/it546 - how to install oVirt 3.3 on CentOS 6.5 http://www.youtube.com/watch?v=5i5ilSKsmbo 5. Related - NetApp GA'd their Virtual Storage Console for RHEV, which is implemented as an oVirt UI plugin (and then some) http://captainkvm.com/2014/02/vsc-for-rhev-is-ga-today/#more-660 From alitke at redhat.com Mon Mar 3 14:56:56 2014 From: alitke at redhat.com (Adam Litke) Date: Mon, 3 Mar 2014 09:56:56 -0500 Subject: [Engine-devel] Asynchronous tasks for live merge In-Reply-To: <53149372.2050203@redhat.com> References: <20140228143016.GC29304@redhat.com> <20140303142827.GG17073@redhat.com> <53149372.2050203@redhat.com> Message-ID: <20140303145656.GD356@redhat.com> On 03/03/14 16:36 +0200, Itamar Heim wrote: >On 03/03/2014 04:28 PM, Dan Kenigsberg wrote: >>On Fri, Feb 28, 2014 at 09:30:16AM -0500, Adam Litke wrote: >>>Hi all, >>> >>>As part of our plan to support live merging of VM disk snapshots it >>>seems we will need a new form of asynchronous task in ovirt-engine. I >>>am aware of AsyncTaskManager but it seems to be limited to managing >>>SPM tasks. For live merge, we are going to need something called >>>VmTasks since the async command can be run only on the host that >>>currently runs the VM. >>> >>>The way I see this working from an engine perspective is: >>>1. RemoveSnapshotCommand in bll is invoked as usual but since the VM is >>> found to be up, we activate an alternative live merge flow. >>>2. We submit a LiveMerge VDS Command for each impacted disk. This is >>> an asynchronous command which we need to monitor for completion. >>>3. A VmJob is inserted into the DB so we'll remember to handle it. >>>4. The VDS Broker monitors the operation via an extension to the >>> already collected VmStatistics data. Vdsm will report active Block >>> Jobs only. Once the job stops (in error or success) it will cease >>> to be reported by vdsm and engine will know to proceed. >> >>You describe a reasonable way for Vdsm to report whether an async >>operation has finished. However, may we instead use the oportunity to >>introduce generic "hsm" tasks? >> >>I suggest to have something loosely modeled on posix fork/wait. >> >>- Engine asks Vdsm to start an API verb asynchronously and supplies a >> uuid. This is unlike fork(2), where the system chooses the pid, but >> that's required so that Engine could tell if the command has reached >> Vdsm in case of a network error. >> >>- Engine may monitor the task (a-la wait(WNOHANG)) >> >>- When the task is finished, Engine may collect its result (a-la wait). >> Until that happens, Vdsm must report the task forever; restart or >> upgrade are no excuses. On reboot, though, all tasks are forgotten, so >> Engine may stop monitoring tasks on a fenced host. >> >>This may be an over kill for your use case, but it would come useful for >>other cases. In particular, setupNetwork returns before it is completely >>done, since dhcp address acquisition may take too much time. Engine may >>poll getVdsCaps to see when it's done (or timeout), but it would be >>nicer to have a generic mechanism that can serve us all. >> >>Note that I'm suggesting a completely new task framwork, at least on >>Vdsm side, as the current one (with its broken persistence, arcane >>states and never-reliable rollback) is beyond redemption, imho. >> >>>5. When the job has completed, VDS Broker raises an event up to bll. >>> Maybe this could be done via VmJobDAO on the stored VmJob? >>>6. Bll receives the event and issues a series of VDS commands to >>> complete the operation: >>> a) Verify the new image chain matches our expectations (the snap is >>> no longer present in the chain). >>> b) Delete the snapshot volume >>> c) Remove the VmJob from the DB >>> >>>Could you guys review this proposed flow for sanity? The main >>>conceptual gaps I am left with concern #5 and #6. What is the >>>appropriate way for VDSBroker to communicate with BLL? Is there an >>>event mechanism I can explore or should I use the database? I am >>>leaning toward the database because it is persistent and will ensure >>>#6 gets completed even if engine is restarted somewhere in the middle. >>>For #6, is there an existing polling / event loop in bll that I can >>>plug into? >>> >>>Thanks in advance for taking the time to think about this flow and for >>>providing your insights! >>_______________________________________________ >>Engine-devel mailing list >>Engine-devel at ovirt.org >>http://lists.ovirt.org/mailman/listinfo/engine-devel >> > >the way i read Adam's proposal, there is no "task" entity at vdsm side >to monitor, rather the state of the object the operation is performed >on (similar to CreateVM, where the engine monitors the state of the >VM, rather than the CreateVM request). Yeah, we use the term "job" in order to avoid assumptions and implications (ie. rollback/cancel, persistence) that come with the word "task". "Job" essentially means "libvirt Block Job", but I am trying to allow for extension in the future. Vdsm would collect block job information for devices it expects to have active block jobs and report them all under a single structure in the VM statistics. There would be no persistence of information so when a libvirt block job goes poof, vdsm will stop reporting it. -- Adam Litke From danken at redhat.com Mon Mar 3 15:53:02 2014 From: danken at redhat.com (Dan Kenigsberg) Date: Mon, 3 Mar 2014 15:53:02 +0000 Subject: [Engine-devel] Asynchronous tasks for live merge In-Reply-To: <20140303145656.GD356@redhat.com> References: <20140228143016.GC29304@redhat.com> <20140303142827.GG17073@redhat.com> <53149372.2050203@redhat.com> <20140303145656.GD356@redhat.com> Message-ID: <20140303155302.GH17073@redhat.com> On Mon, Mar 03, 2014 at 09:56:56AM -0500, Adam Litke wrote: > On 03/03/14 16:36 +0200, Itamar Heim wrote: > >On 03/03/2014 04:28 PM, Dan Kenigsberg wrote: > >>On Fri, Feb 28, 2014 at 09:30:16AM -0500, Adam Litke wrote: > >>>Hi all, > >>> > >>>As part of our plan to support live merging of VM disk snapshots it > >>>seems we will need a new form of asynchronous task in ovirt-engine. I > >>>am aware of AsyncTaskManager but it seems to be limited to managing > >>>SPM tasks. For live merge, we are going to need something called > >>>VmTasks since the async command can be run only on the host that > >>>currently runs the VM. > >>> > >>>The way I see this working from an engine perspective is: > >>>1. RemoveSnapshotCommand in bll is invoked as usual but since the VM is > >>> found to be up, we activate an alternative live merge flow. > >>>2. We submit a LiveMerge VDS Command for each impacted disk. This is > >>> an asynchronous command which we need to monitor for completion. > >>>3. A VmJob is inserted into the DB so we'll remember to handle it. > >>>4. The VDS Broker monitors the operation via an extension to the > >>> already collected VmStatistics data. Vdsm will report active Block > >>> Jobs only. Once the job stops (in error or success) it will cease > >>> to be reported by vdsm and engine will know to proceed. > >> > >>You describe a reasonable way for Vdsm to report whether an async > >>operation has finished. However, may we instead use the oportunity to > >>introduce generic "hsm" tasks? > >> > >>I suggest to have something loosely modeled on posix fork/wait. > >> > >>- Engine asks Vdsm to start an API verb asynchronously and supplies a > >> uuid. This is unlike fork(2), where the system chooses the pid, but > >> that's required so that Engine could tell if the command has reached > >> Vdsm in case of a network error. > >> > >>- Engine may monitor the task (a-la wait(WNOHANG)) > >> > >>- When the task is finished, Engine may collect its result (a-la wait). > >> Until that happens, Vdsm must report the task forever; restart or > >> upgrade are no excuses. On reboot, though, all tasks are forgotten, so > >> Engine may stop monitoring tasks on a fenced host. > >> > >>This may be an over kill for your use case, but it would come useful for > >>other cases. In particular, setupNetwork returns before it is completely > >>done, since dhcp address acquisition may take too much time. Engine may > >>poll getVdsCaps to see when it's done (or timeout), but it would be > >>nicer to have a generic mechanism that can serve us all. > >> > >>Note that I'm suggesting a completely new task framwork, at least on > >>Vdsm side, as the current one (with its broken persistence, arcane > >>states and never-reliable rollback) is beyond redemption, imho. > >> > >>>5. When the job has completed, VDS Broker raises an event up to bll. > >>> Maybe this could be done via VmJobDAO on the stored VmJob? > >>>6. Bll receives the event and issues a series of VDS commands to > >>> complete the operation: > >>> a) Verify the new image chain matches our expectations (the snap is > >>> no longer present in the chain). > >>> b) Delete the snapshot volume > >>> c) Remove the VmJob from the DB > >>> > >>>Could you guys review this proposed flow for sanity? The main > >>>conceptual gaps I am left with concern #5 and #6. What is the > >>>appropriate way for VDSBroker to communicate with BLL? Is there an > >>>event mechanism I can explore or should I use the database? I am > >>>leaning toward the database because it is persistent and will ensure > >>>#6 gets completed even if engine is restarted somewhere in the middle. > >>>For #6, is there an existing polling / event loop in bll that I can > >>>plug into? > >>> > >>>Thanks in advance for taking the time to think about this flow and for > >>>providing your insights! > >>_______________________________________________ > >>Engine-devel mailing list > >>Engine-devel at ovirt.org > >>http://lists.ovirt.org/mailman/listinfo/engine-devel > >> > > > >the way i read Adam's proposal, there is no "task" entity at vdsm > >side to monitor, rather the state of the object the operation is > >performed on (similar to CreateVM, where the engine monitors the > >state of the VM, rather than the CreateVM request). > > Yeah, we use the term "job" in order to avoid assumptions and > implications (ie. rollback/cancel, persistence) that come with the > word "task". "Job" essentially means "libvirt Block Job", but I am > trying to allow for extension in the future. Vdsm would collect block > job information for devices it expects to have active block jobs and > report them all under a single structure in the VM statistics. There > would be no persistence of information so when a libvirt block job > goes poof, vdsm will stop reporting it. I know, but since we need someothing quite similar for setupNetwork, I'm suggesting to have have something generic enough to fulfill both use cases. Instead of having one part of Engine poll for pending VmJobs, and another polling on whether a network finally got its address from the dhcp server. As Itamar said, a very similar logic exists for migration, and for starting up a new VM. I'm not suggesting rollback, cancelation or fancy persistence. And not even a progress indication, although I'm pretty sure it would come up handy in the future. From danken at redhat.com Mon Mar 3 16:23:33 2014 From: danken at redhat.com (Dan Kenigsberg) Date: Mon, 3 Mar 2014 16:23:33 +0000 Subject: [Engine-devel] Asynchronous tasks for live merge In-Reply-To: <20140303145115.GC356@redhat.com> References: <20140228143016.GC29304@redhat.com> <20140303142827.GG17073@redhat.com> <20140303145115.GC356@redhat.com> Message-ID: <20140303162333.GI17073@redhat.com> On Mon, Mar 03, 2014 at 09:51:15AM -0500, Adam Litke wrote: > On 03/03/14 14:28 +0000, Dan Kenigsberg wrote: > >On Fri, Feb 28, 2014 at 09:30:16AM -0500, Adam Litke wrote: > >>Hi all, > >> > >>As part of our plan to support live merging of VM disk snapshots it > >>seems we will need a new form of asynchronous task in ovirt-engine. I > >>am aware of AsyncTaskManager but it seems to be limited to managing > >>SPM tasks. For live merge, we are going to need something called > >>VmTasks since the async command can be run only on the host that > >>currently runs the VM. > >> > >>The way I see this working from an engine perspective is: > >>1. RemoveSnapshotCommand in bll is invoked as usual but since the VM is > >> found to be up, we activate an alternative live merge flow. > >>2. We submit a LiveMerge VDS Command for each impacted disk. This is > >> an asynchronous command which we need to monitor for completion. > >>3. A VmJob is inserted into the DB so we'll remember to handle it. > >>4. The VDS Broker monitors the operation via an extension to the > >> already collected VmStatistics data. Vdsm will report active Block > >> Jobs only. Once the job stops (in error or success) it will cease > >> to be reported by vdsm and engine will know to proceed. > > > >You describe a reasonable way for Vdsm to report whether an async > >operation has finished. However, may we instead use the oportunity to > >introduce generic "hsm" tasks? > > Sure, I am happy to have that conversation :) If I understand > correctly, HSM tasks, while ideal, might be too complex to get right > and would block the Live Merge feature for longer than we would like. > Has anyone looked into what it would take to implement a HSM Tasks > framework like this in vdsm? Are there any WIP implementations? If > the scope of this is not too big, it can be completed relatively > quickly, and the resulting implementation would cover all known use > cases, then this could be worth it. It's important to support Live > Merge soon. > > Regarding deprecation of the current tasks API: Could your suggested > HSM Tasks framework be extended to cover SPM/SDM tasks as well? I > would hope that a it could. In that case, we could look forward to a > unified async task architecture in vdsm. The current task framework in Vdsm is outrageously complex, yet unreliable. It meant to do all kinds of things, like having the new spm take over a task that was orphaned by the former spm. This has never worked properly. I'm looking for a much simpler infrastructure, where rollback is done by virtue of having an "except" clause, and spm-only verbs simply fail when the host loses spm status for some reason. > > >I suggest to have something loosely modeled on posix fork/wait. > > > >- Engine asks Vdsm to start an API verb asynchronously and supplies a > > uuid. This is unlike fork(2), where the system chooses the pid, but > > that's required so that Engine could tell if the command has reached > > Vdsm in case of a network error. > > > >- Engine may monitor the task (a-la wait(WNOHANG)) > > Allon has communicated a desire to limit engine-side polling. Perhaps > the active tasks could be added to the host stats? Engine is reluctant to add more polling, I understand that. I'd prefer a standalone new getAllTaskStats2() verb, but if lumping it into getVdsStats is going to convince everybody to have it, I'd put my aesthetic taste in the fridge. > >- When the task is finished, Engine may collect its result (a-la wait). > > Until that happens, Vdsm must report the task forever; restart or > > upgrade are no excuses. On reboot, though, all tasks are forgotten, so > > Engine may stop monitoring tasks on a fenced host. > > This could be a good comprimise. I hate the idea of requiring engine > to play janitor and clean up stale vdsm data, but there is not much > better of a way to do it. Allowing reboot to auto-clear tasks will at > least provide some backstop to how long tasks could pile up if > forgotten. > > >This may be an over kill for your use case, but it would come useful for > >other cases. In particular, setupNetwork returns before it is completely > >done, since dhcp address acquisition may take too much time. Engine may > >poll getVdsCaps to see when it's done (or timeout), but it would be > >nicer to have a generic mechanism that can serve us all. > > If we were to consider this, I would want to vet the architecture > against all known use cases for tasks to make sure we don't need to > create a new framework in 3 months. I'm afraid that our time scale is a bit longer (for good and for worse), but for sure, we'd need to list all possible users of such an infrastructure. > > >Note that I'm suggesting a completely new task framwork, at least on > >Vdsm side, as the current one (with its broken persistence, arcane > >states and never-reliable rollback) is beyond redemption, imho. > > Are we okay with abandoning vdsm-side rollback entirely as we move > forward? Won't that be a regression for at least some error flows > (especially in the realm of SPM tasks)? We would have to maintain the current spm task framework. But depending on a Vdsm-side rollback to succeed was an old mistake. Rollback may fail just as roll-forward does; thus Engine must handle the case of a lost task. So why bother? Vdsm should do its best to finish a task, and clean after itself. If it dies while at it, only Engine can ask another Vdsm to pick up the pieces. > > >>5. When the job has completed, VDS Broker raises an event up to bll. > >> Maybe this could be done via VmJobDAO on the stored VmJob? > >>6. Bll receives the event and issues a series of VDS commands to > >> complete the operation: > >> a) Verify the new image chain matches our expectations (the snap is > >> no longer present in the chain). > >> b) Delete the snapshot volume > >> c) Remove the VmJob from the DB From S.Kieske at mittwald.de Mon Mar 3 16:25:39 2014 From: S.Kieske at mittwald.de (Sven Kieske) Date: Mon, 3 Mar 2014 16:25:39 +0000 Subject: [Engine-devel] Tweaking backup/restore of engine Message-ID: <5314ACBF.90305@mittwald.de> Hi, currently all events are stored in the table audit_log which all gets saved when you use the engine-backup shell script. the event log is full of these login lines (engine 3.3.2): 25652 fdfc627c-d875-11e0-90f0-83df133b58cc admin at internal 00000000-0000-0000-0000-000000000000 \N \N \N \N \N 2014-01-20 06:39:17.222+01 USER_VDC_LOGIN 30 0 User admin at internal logged in. f \N \N 00000000-0000-0000-0000-000000000000 \N \N \N \N 00000000-0000-0000-0000-000000000000 \N oVirt -1 30 f \N this makes the log and db grow very large when you use the REST-API to query ovirt for various data. Is this necessary for a working restore? It would be cool if we could tweak the engine-backup tool to just dump necessary tables so you don't have to restore events from the past no one is interested in. How does ovirt react, if I do not restore the content of the audit_log table? If this works (restore without audit_log) I would prefer to have this code upstream in ovirt git so I don't have to maintain my own backupscript. Would it be possible to extend the existing backupscript with a switch to not backup logs? Currently it's just "all" or "just db". I also recall that there shouldn't occur multiple login events any more since ovirt 3.3. but it still seems to be the case. I also do not understand how you would manage a stored authentication via REST as REST is stateless. I would appreciate any feedback or thoughts on this topic. -- Mit freundlichen Gr??en / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K?nigsberger Stra?e 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Gesch?ftsf?hrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen From didi at redhat.com Mon Mar 3 20:41:14 2014 From: didi at redhat.com (Yedidyah Bar David) Date: Mon, 3 Mar 2014 15:41:14 -0500 (EST) Subject: [Engine-devel] Tweaking backup/restore of engine and the table 'audit_log' In-Reply-To: <5314ACBF.90305@mittwald.de> References: <5314ACBF.90305@mittwald.de> Message-ID: <1120227780.11414666.1393879274330.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Sven Kieske" > To: engine-devel at ovirt.org > Sent: Monday, March 3, 2014 6:25:39 PM > Subject: [Engine-devel] Tweaking backup/restore of engine > > Hi, > > currently all events are stored in the table audit_log > which all gets saved when you use the engine-backup > shell script. > > > the event log is full of these login lines (engine 3.3.2): > > 25652 fdfc627c-d875-11e0-90f0-83df133b58cc admin at internal > 00000000-0000-0000-0000-000000000000 \N \N \N \N \N 2014-01-20 > 06:39:17.222+01 USER_VDC_LOGIN 30 0 User admin at internal > logged in. f \N \N 00000000-0000-0000-0000-000000000000 \N \N \N > \N 00000000-0000-0000-0000-000000000000 \N oVirt -1 30 f \N > > this makes the log and db grow very large when you use the REST-API > to query ovirt for various data. > > Is this necessary for a working restore? I have no idea - I guess the data is not necessary. I also guess that the schema is. > It would be cool if we could tweak the engine-backup > tool to just dump necessary tables so you don't have > to restore events from the past no one is interested > in. > > How does ovirt react, if I do not restore the content of the audit_log > table? > > If this works (restore without audit_log) I would prefer to have > this code upstream in ovirt git so I don't have to maintain > my own backupscript. > > Would it be possible to extend the existing backupscript > with a switch to not backup logs? > Currently it's just "all" or "just db". It would be easy to let you pass an "extra options" argument for pg_dump. This will allow adding '-T audit_log'. As I said, I am pretty certain that you do need the table itself, so this will not help you much. I personally think that this isn't the right way to go. If you do not need the data, create a cron job that will periodically truncate it - say, keep the last X days and delete the rest. Perhaps also archive before deleting if you want. If you want, open a bug to provide a script to do that for you. Or make the engine itself do that, etc. Of course, after verifying that this does not have a significant impact on the engine :-) > > I also recall that there shouldn't occur multiple login events any > more since ovirt 3.3. but it still seems to be the case. > > I also do not understand how you would manage a stored authentication > via REST as REST is stateless. > > I would appreciate any feedback or thoughts on this topic. Best regards, -- Didi From alitke at redhat.com Mon Mar 3 22:26:28 2014 From: alitke at redhat.com (Adam Litke) Date: Mon, 3 Mar 2014 17:26:28 -0500 Subject: [Engine-devel] Schema upgrade failure on master Message-ID: <20140303222628.GE31669@redhat.com> Hi, I've recently rebased to master and it looks like the 03_05_0050_event_notification_methods.sql script is failing on schema upgrade. Is this a bug or am I doing something wrong? To upgrade I did the normal proceedure with my development installation: make install-dev ... ~/ovirt/bin/engine-setup Got this result in the log file: psql:/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql:10: ERROR: column "notification_method" contains null values FATAL: Cannot execute sql command: --file=/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql 2014-03-03 17:20:34 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/db/schema.py", line 280, in _misc osetupcons.DBEnv.PGPASS_FILE File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 451, in execute command=args[0], RuntimeError: Command '/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/schema.sh' failed to execute -- Adam Litke From alonbl at redhat.com Mon Mar 3 22:29:59 2014 From: alonbl at redhat.com (Alon Bar-Lev) Date: Mon, 3 Mar 2014 17:29:59 -0500 (EST) Subject: [Engine-devel] Schema upgrade failure on master In-Reply-To: <20140303222628.GE31669@redhat.com> References: <20140303222628.GE31669@redhat.com> Message-ID: <461231136.6928235.1393885799883.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Adam Litke" > To: engine-devel at ovirt.org > Sent: Tuesday, March 4, 2014 12:26:28 AM > Subject: [Engine-devel] Schema upgrade failure on master > > Hi, > > I've recently rebased to master and it looks like the > 03_05_0050_event_notification_methods.sql script is failing on schema > upgrade. Is this a bug or am I doing something wrong? To upgrade I > did the normal proceedure with my development installation: > > make install-dev ... > ~/ovirt/bin/engine-setup > > Got this result in the log file: > > psql:/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql:10: > ERROR: column "notification_method" contains null values > FATAL: Cannot execute sql command: > --file=/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql > > 2014-03-03 17:20:34 DEBUG otopi.context context._executeMethod:152 method > exception > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in > _executeMethod > method['method']() > File > "/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/db/schema.py", > line 280, in _misc > osetupcons.DBEnv.PGPASS_FILE > File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 451, in > execute > command=args[0], > RuntimeError: Command > '/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/schema.sh' > failed to execute > > -- > Adam Litke > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > From mperina at redhat.com Tue Mar 4 05:10:21 2014 From: mperina at redhat.com (Martin Perina) Date: Tue, 4 Mar 2014 00:10:21 -0500 (EST) Subject: [Engine-devel] Schema upgrade failure on master In-Reply-To: <20140303222628.GE31669@redhat.com> References: <20140303222628.GE31669@redhat.com> Message-ID: <1109246737.12800424.1393909821557.JavaMail.zimbra@redhat.com> Hi Adam, I didn't notice any problem with this script. Was the database you tried to upgrade empty? If not could you please send me contents of your event_subscriber table? Thanks Martin Perina ----- Original Message ----- > From: "Adam Litke" > To: engine-devel at ovirt.org > Sent: Monday, March 3, 2014 11:26:28 PM > Subject: [Engine-devel] Schema upgrade failure on master > > Hi, > > I've recently rebased to master and it looks like the > 03_05_0050_event_notification_methods.sql script is failing on schema > upgrade. Is this a bug or am I doing something wrong? To upgrade I > did the normal proceedure with my development installation: > > make install-dev ... > ~/ovirt/bin/engine-setup > > Got this result in the log file: > > psql:/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql:10: > ERROR: column "notification_method" contains null values > FATAL: Cannot execute sql command: > --file=/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql > > 2014-03-03 17:20:34 DEBUG otopi.context context._executeMethod:152 method > exception > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in > _executeMethod > method['method']() > File > "/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/db/schema.py", > line 280, in _misc > osetupcons.DBEnv.PGPASS_FILE > File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 451, in > execute > command=args[0], > RuntimeError: Command > '/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/schema.sh' > failed to execute > > -- > Adam Litke > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > From yzaslavs at redhat.com Tue Mar 4 06:53:59 2014 From: yzaslavs at redhat.com (Yair Zaslavsky) Date: Tue, 4 Mar 2014 01:53:59 -0500 (EST) Subject: [Engine-devel] Tweaking backup/restore of engine In-Reply-To: <5314ACBF.90305@mittwald.de> References: <5314ACBF.90305@mittwald.de> Message-ID: <321031989.25794382.1393916039124.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Sven Kieske" > To: engine-devel at ovirt.org > Sent: Monday, March 3, 2014 6:25:39 PM > Subject: [Engine-devel] Tweaking backup/restore of engine > > Hi, > > currently all events are stored in the table audit_log > which all gets saved when you use the engine-backup > shell script. > > > the event log is full of these login lines (engine 3.3.2): > > 25652 fdfc627c-d875-11e0-90f0-83df133b58cc admin at internal > 00000000-0000-0000-0000-000000000000 \N \N \N \N \N 2014-01-20 > 06:39:17.222+01 USER_VDC_LOGIN 30 0 User admin at internal > logged in. f \N \N 00000000-0000-0000-0000-000000000000 \N \N \N > \N 00000000-0000-0000-0000-000000000000 \N oVirt -1 30 f \N > > this makes the log and db grow very large when you use the REST-API > to query ovirt for various data. > > Is this necessary for a working restore? > It would be cool if we could tweak the engine-backup > tool to just dump necessary tables so you don't have > to restore events from the past no one is interested > in. > > How does ovirt react, if I do not restore the content of the audit_log > table? > > If this works (restore without audit_log) I would prefer to have > this code upstream in ovirt git so I don't have to maintain > my own backupscript. > > Would it be possible to extend the existing backupscript > with a switch to not backup logs? > Currently it's just "all" or "just db". > > I also recall that there shouldn't occur multiple login events any > more since ovirt 3.3. but it still seems to be the case. Hi Sven, This is not entirely accurate - The solution introduced at commit hash cb56de8808cec33b7599828ead890f52e32bcaea solves the problem for a specific case in which we have a multiple login in a very short interval of time - mainly due to attempt to login from webadmin, while UI plugin tries to login as well. We have an "anti flood" mechanism for events, allowing us to define an interval, in which an event will not be logged twice. In the case of the login event this is set to 5 seconds, which is enough to solve the above described scenario. > > I also do not understand how you would manage a stored authentication > via REST as REST is stateless. > > I would appreciate any feedback or thoughts on this topic. > -- > Mit freundlichen Gr??en / Regards > > Sven Kieske > > Systemadministrator > Mittwald CM Service GmbH & Co. KG > K?nigsberger Stra?e 6 > 32339 Espelkamp > T: +49-5772-293-100 > F: +49-5772-293-333 > https://www.mittwald.de > Gesch?ftsf?hrer: Robert Meyer > St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen > Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > From S.Kieske at mittwald.de Tue Mar 4 08:10:31 2014 From: S.Kieske at mittwald.de (Sven Kieske) Date: Tue, 4 Mar 2014 08:10:31 +0000 Subject: [Engine-devel] Tweaking backup/restore of engine and the table 'audit_log' In-Reply-To: <1120227780.11414666.1393879274330.JavaMail.zimbra@redhat.com> References: <5314ACBF.90305@mittwald.de> <1120227780.11414666.1393879274330.JavaMail.zimbra@redhat.com> Message-ID: <53158A33.3010706@mittwald.de> Thanks for your answer so far. Is there anyone around who knows if the audit_log data is needed for a successful restore? I'd rather not try this out myself. The reasoning behind this all is of course to keep backup space as small as possible. Am 03.03.2014 21:41, schrieb Yedidyah Bar David: > I have no idea - I guess the data is not necessary. -- Mit freundlichen Gr??en / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K?nigsberger Stra?e 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Gesch?ftsf?hrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen From S.Kieske at mittwald.de Tue Mar 4 08:25:31 2014 From: S.Kieske at mittwald.de (Sven Kieske) Date: Tue, 4 Mar 2014 08:25:31 +0000 Subject: [Engine-devel] Tweaking backup/restore of engine In-Reply-To: <321031989.25794382.1393916039124.JavaMail.zimbra@redhat.com> References: <5314ACBF.90305@mittwald.de> <321031989.25794382.1393916039124.JavaMail.zimbra@redhat.com> Message-ID: <53158DB6.3070905@mittwald.de> Thanks for the clarification, I couldn't find this change any more, but I knew there was something done. However this makes me think about an RFE: It would be cool if ovirt could provide a way to use the REST-API without always have to login and logout. Maybe something like a hook into some message passing queue like rabbitMQ or zeroMQ or a similar process for receiving and submitting messages. So you could register once with an API consumer and use that. What do you think? Am 04.03.2014 07:53, schrieb Yair Zaslavsky: > Hi Sven, > This is not entirely accurate - > The solution introduced at commit hash cb56de8808cec33b7599828ead890f52e32bcaea solves the problem for a specific case in which we have a multiple login in a very short interval of time - > mainly due to attempt to login from webadmin, while UI plugin tries to login as well. > We have an "anti flood" mechanism for events, allowing us to define an interval, in which an event will not be logged twice. In the case of the login event this is set to 5 seconds, which is enough to solve the above described scenario. -- Mit freundlichen Gr??en / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K?nigsberger Stra?e 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Gesch?ftsf?hrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen From yzaslavs at redhat.com Tue Mar 4 08:38:14 2014 From: yzaslavs at redhat.com (Yair Zaslavsky) Date: Tue, 4 Mar 2014 03:38:14 -0500 (EST) Subject: [Engine-devel] Tweaking backup/restore of engine In-Reply-To: <53158DB6.3070905@mittwald.de> References: <5314ACBF.90305@mittwald.de> <321031989.25794382.1393916039124.JavaMail.zimbra@redhat.com> <53158DB6.3070905@mittwald.de> Message-ID: <1152394439.25821809.1393922294299.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Sven Kieske" > To: engine-devel at ovirt.org > Sent: Tuesday, March 4, 2014 10:25:31 AM > Subject: Re: [Engine-devel] Tweaking backup/restore of engine > > Thanks for the clarification, > > I couldn't find this change any more, but I knew > there was something done. > > However this makes me think about an RFE: > It would be cool if ovirt could provide a way > to use the REST-API without always have to login > and logout. > > Maybe something like a hook into > some message passing queue like rabbitMQ or zeroMQ > or a similar process for receiving and submitting > messages. So you could register once with an API > consumer and use that. > > What do you think? CC'ing Juan - the maintainer of the REST API > > Am 04.03.2014 07:53, schrieb Yair Zaslavsky: > > Hi Sven, > > This is not entirely accurate - > > The solution introduced at commit hash > > cb56de8808cec33b7599828ead890f52e32bcaea solves the problem for a > > specific case in which we have a multiple login in a very short interval > > of time - > > mainly due to attempt to login from webadmin, while UI plugin tries to > > login as well. > > We have an "anti flood" mechanism for events, allowing us to define an > > interval, in which an event will not be logged twice. In the case of the > > login event this is set to 5 seconds, which is enough to solve the above > > described scenario. > > -- > Mit freundlichen Gr??en / Regards > > Sven Kieske > > Systemadministrator > Mittwald CM Service GmbH & Co. KG > K?nigsberger Stra?e 6 > 32339 Espelkamp > T: +49-5772-293-100 > F: +49-5772-293-333 > https://www.mittwald.de > Gesch?ftsf?hrer: Robert Meyer > St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen > Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > From jhernand at redhat.com Tue Mar 4 08:51:36 2014 From: jhernand at redhat.com (Juan Hernandez) Date: Tue, 04 Mar 2014 09:51:36 +0100 Subject: [Engine-devel] Tweaking backup/restore of engine In-Reply-To: <1152394439.25821809.1393922294299.JavaMail.zimbra@redhat.com> References: <5314ACBF.90305@mittwald.de> <321031989.25794382.1393916039124.JavaMail.zimbra@redhat.com> <53158DB6.3070905@mittwald.de> <1152394439.25821809.1393922294299.JavaMail.zimbra@redhat.com> Message-ID: <53159418.2060600@redhat.com> On 03/04/2014 09:38 AM, Yair Zaslavsky wrote: > > > ----- Original Message ----- >> From: "Sven Kieske" >> To: engine-devel at ovirt.org >> Sent: Tuesday, March 4, 2014 10:25:31 AM >> Subject: Re: [Engine-devel] Tweaking backup/restore of engine >> >> Thanks for the clarification, >> >> I couldn't find this change any more, but I knew >> there was something done. >> >> However this makes me think about an RFE: >> It would be cool if ovirt could provide a way >> to use the REST-API without always have to login >> and logout. >> >> Maybe something like a hook into >> some message passing queue like rabbitMQ or zeroMQ >> or a similar process for receiving and submitting >> messages. So you could register once with an API >> consumer and use that. >> >> What do you think? > > CC'ing Juan - the maintainer of the REST API Using the RESTAPI without repeated login/logout is already supported, and it is what the SDKs do by default. In order to use it you need to add the "Prefer: persistent-auth" header to the HTTP request, and keep track of the cookies returned by the engine. For, example, the following example sends events to the engine, without repeatedly performing the login process: #!/bin/sh -x # The details to connect to the engine: url="https://whatever/ovirt-engine/api" user="admin at internal" password="****" # The file where we store the cookies, including the # session id: cookies="cookies.txt" curl \ --insecure \ --request POST \ --header "Accept: application/xml" \ --header "Content-Type: application/xml" \ --header "Prefer: persistent-auth" \ --user "${user}:${password}" \ --cookie "${cookies}" \ --cookie-jar "${cookies}" \ --data " myorigin normal Something from me $(date +%s) " \ ${url}/events This will keep a session alive in the server. If you want to explicitly close it just send an additional request, with the same cookies and without the "Prefer" header. It is described in more detail here: http://www.ovirt.org/Features/RESTSessionManagement >> >> Am 04.03.2014 07:53, schrieb Yair Zaslavsky: >>> Hi Sven, >>> This is not entirely accurate - >>> The solution introduced at commit hash >>> cb56de8808cec33b7599828ead890f52e32bcaea solves the problem for a >>> specific case in which we have a multiple login in a very short interval >>> of time - >>> mainly due to attempt to login from webadmin, while UI plugin tries to >>> login as well. >>> We have an "anti flood" mechanism for events, allowing us to define an >>> interval, in which an event will not be logged twice. In the case of the >>> login event this is set to 5 seconds, which is enough to solve the above >>> described scenario. >> >> -- >> Mit freundlichen Gr??en / Regards >> >> Sven Kieske >> >> Systemadministrator >> Mittwald CM Service GmbH & Co. KG >> K?nigsberger Stra?e 6 >> 32339 Espelkamp >> T: +49-5772-293-100 >> F: +49-5772-293-333 >> https://www.mittwald.de >> Gesch?ftsf?hrer: Robert Meyer >> St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen >> Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen >> _______________________________________________ >> Engine-devel mailing list >> Engine-devel at ovirt.org >> http://lists.ovirt.org/mailman/listinfo/engine-devel >> -- 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. From S.Kieske at mittwald.de Tue Mar 4 09:06:20 2014 From: S.Kieske at mittwald.de (Sven Kieske) Date: Tue, 4 Mar 2014 09:06:20 +0000 Subject: [Engine-devel] python docs in wiki up to date? Message-ID: <53159747.2010904@mittwald.de> Hi, is this still state of the art? http://www.ovirt.org/Testing/PythonApi If not I could update it myself if you provide me with the necessary information. Thanks -- Mit freundlichen Gr??en / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K?nigsberger Stra?e 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Gesch?ftsf?hrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen From liran.zelkha at gmail.com Tue Mar 4 09:15:47 2014 From: liran.zelkha at gmail.com (Liran Zelkha) Date: Tue, 4 Mar 2014 11:15:47 +0200 Subject: [Engine-devel] Schema upgrade failure on master In-Reply-To: <1109246737.12800424.1393909821557.JavaMail.zimbra@redhat.com> References: <20140303222628.GE31669@redhat.com> <1109246737.12800424.1393909821557.JavaMail.zimbra@redhat.com> Message-ID: Happens to me too, on engine_dao_tests. DB is not empty, one line: engine_dao_tests=> select * from event_subscriber; subscriber_id | event_up_name | method_id | method_address | tag_name | notification_method --------------------------------------+---------------+-----------+----------------+----------+--------------------- 9bf7c640-b620-456f-a550-0348f366544a | TestRun | 1 | | testrun | (1 row) On Tue, Mar 4, 2014 at 7:10 AM, Martin Perina wrote: > Hi Adam, > > I didn't notice any problem with this script. Was the database you tried > to upgrade empty? > If not could you please send me contents of your event_subscriber table? > > Thanks > > Martin Perina > > ----- Original Message ----- > > From: "Adam Litke" > > To: engine-devel at ovirt.org > > Sent: Monday, March 3, 2014 11:26:28 PM > > Subject: [Engine-devel] Schema upgrade failure on master > > > > Hi, > > > > I've recently rebased to master and it looks like the > > 03_05_0050_event_notification_methods.sql script is failing on schema > > upgrade. Is this a bug or am I doing something wrong? To upgrade I > > did the normal proceedure with my development installation: > > > > make install-dev ... > > ~/ovirt/bin/engine-setup > > > > Got this result in the log file: > > > > > psql:/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql:10: > > ERROR: column "notification_method" contains null values > > FATAL: Cannot execute sql command: > > > --file=/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql > > > > 2014-03-03 17:20:34 DEBUG otopi.context context._executeMethod:152 method > > exception > > Traceback (most recent call last): > > File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in > > _executeMethod > > method['method']() > > File > > > "/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/db/schema.py", > > line 280, in _misc > > osetupcons.DBEnv.PGPASS_FILE > > File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 451, in > > execute > > command=args[0], > > RuntimeError: Command > > > '/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/schema.sh' > > failed to execute > > > > -- > > Adam Litke > > _______________________________________________ > > Engine-devel mailing list > > Engine-devel at ovirt.org > > http://lists.ovirt.org/mailman/listinfo/engine-devel > > > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sbonazzo at redhat.com Tue Mar 4 09:22:07 2014 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Tue, 04 Mar 2014 10:22:07 +0100 Subject: [Engine-devel] oVrit 3.4.0 branch created Message-ID: <53159B3F.3090403@redhat.com> Hi, as announced yesterday the new branch ovirt-engine-3.4.0 branch has been created from 3.4. Branch commit was: * 9ab9f01 - (origin/ovirt-engine-3.4) core: Remove error messages from log when adding host Only critical fixes will be accepted on ovirt-engine-3.4.0 branch. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From mperina at redhat.com Tue Mar 4 09:50:01 2014 From: mperina at redhat.com (Martin Perina) Date: Tue, 4 Mar 2014 04:50:01 -0500 (EST) Subject: [Engine-devel] Schema upgrade failure on master In-Reply-To: References: <20140303222628.GE31669@redhat.com> <1109246737.12800424.1393909821557.JavaMail.zimbra@redhat.com> Message-ID: <1832002069.12888461.1393926601613.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Liran Zelkha" > To: "Martin Perina" > Cc: "engine-devel" > Sent: Tuesday, March 4, 2014 10:15:47 AM > Subject: Re: [Engine-devel] Schema upgrade failure on master > > Happens to me too, on engine_dao_tests. > DB is not empty, one line: > engine_dao_tests=> select * from event_subscriber; > subscriber_id | event_up_name | method_id | > method_address | tag_name | notification_method > --------------------------------------+---------------+-----------+----------------+----------+--------------------- > 9bf7c640-b620-456f-a550-0348f366544a | TestRun | 1 | > | testrun | > (1 row) This row caused the issue, I wonder how it was created when notification_method column is created during 03_05_0050_event_notification_methods.sql script execution ... Delete this row and after this run schema upgrade. I tested with master and empty db and dao tests work fine. > > > > > On Tue, Mar 4, 2014 at 7:10 AM, Martin Perina wrote: > > > Hi Adam, > > > > I didn't notice any problem with this script. Was the database you tried > > to upgrade empty? > > If not could you please send me contents of your event_subscriber table? > > > > Thanks > > > > Martin Perina > > > > ----- Original Message ----- > > > From: "Adam Litke" > > > To: engine-devel at ovirt.org > > > Sent: Monday, March 3, 2014 11:26:28 PM > > > Subject: [Engine-devel] Schema upgrade failure on master > > > > > > Hi, > > > > > > I've recently rebased to master and it looks like the > > > 03_05_0050_event_notification_methods.sql script is failing on schema > > > upgrade. Is this a bug or am I doing something wrong? To upgrade I > > > did the normal proceedure with my development installation: > > > > > > make install-dev ... > > > ~/ovirt/bin/engine-setup > > > > > > Got this result in the log file: > > > > > > > > psql:/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql:10: > > > ERROR: column "notification_method" contains null values > > > FATAL: Cannot execute sql command: > > > > > --file=/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql > > > > > > 2014-03-03 17:20:34 DEBUG otopi.context context._executeMethod:152 method > > > exception > > > Traceback (most recent call last): > > > File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in > > > _executeMethod > > > method['method']() > > > File > > > > > "/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/db/schema.py", > > > line 280, in _misc > > > osetupcons.DBEnv.PGPASS_FILE > > > File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 451, in > > > execute > > > command=args[0], > > > RuntimeError: Command > > > > > '/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/schema.sh' > > > failed to execute > > > > > > -- > > > Adam Litke > > > _______________________________________________ > > > Engine-devel mailing list > > > Engine-devel at ovirt.org > > > http://lists.ovirt.org/mailman/listinfo/engine-devel > > > > > _______________________________________________ > > Engine-devel mailing list > > Engine-devel at ovirt.org > > http://lists.ovirt.org/mailman/listinfo/engine-devel > > > From S.Kieske at mittwald.de Tue Mar 4 10:00:13 2014 From: S.Kieske at mittwald.de (Sven Kieske) Date: Tue, 4 Mar 2014 10:00:13 +0000 Subject: [Engine-devel] Tweaking backup/restore of engine In-Reply-To: <5314ACBF.90305@mittwald.de> References: <5314ACBF.90305@mittwald.de> Message-ID: <5315A3E9.1090007@mittwald.de> Hi, I forgot to mention a crucial point: How long does the engine store past events, are they stored forever or is there some kind of rotation? We mainly use the engine as a REST provider for managing the virtual machines. -- Mit freundlichen Gr??en / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K?nigsberger Stra?e 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Gesch?ftsf?hrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen From sbonazzo at redhat.com Tue Mar 4 13:02:36 2014 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Tue, 04 Mar 2014 14:02:36 +0100 Subject: [Engine-devel] [ANN] oVirt 3.3.4 release Message-ID: <5315CEEC.7020401@redhat.com> The oVirt development team is pleased to announce the general availability of oVirt 3.3.4 as of March 4th 2014. This release solidifies oVirt as a leading KVM management application and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.5 (or similar). This release of oVirt includes numerous bug fixes. See the release notes [1] for a list of the new features and bugs fixed. The existing repository ovirt-stable has been updated for delivering this release without the need of enabling any other repository. A new oVirt Node build is also available [2]. [1] http://www.ovirt.org/OVirt_3.3.4_release_notes [2] http://resources.ovirt.org/releases/3.3.4/iso/ovirt-node-iso-3.0.4-1.0.201401291204.vdsm33.el6.iso -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From alitke at redhat.com Tue Mar 4 13:18:21 2014 From: alitke at redhat.com (Adam Litke) Date: Tue, 4 Mar 2014 08:18:21 -0500 Subject: [Engine-devel] Schema upgrade failure on master In-Reply-To: <1109246737.12800424.1393909821557.JavaMail.zimbra@redhat.com> References: <20140303222628.GE31669@redhat.com> <1109246737.12800424.1393909821557.JavaMail.zimbra@redhat.com> Message-ID: <20140304131821.GF31669@redhat.com> On 04/03/14 00:10 -0500, Martin Perina wrote: >Hi Adam, > >I didn't notice any problem with this script. Was the database you tried to upgrade empty? >If not could you please send me contents of your event_subscriber table? engine=> select * from event_subscriber ; subscriber_id | event_up_name | method_id | method_address | tag_name --------------------------------------+-----------------------------+----------- +--------------------------+---------- fdfc627c-d875-11e0-90f0-83df133b58cc | VM_SET_TICKET | 0 | alitke at brewer.alitke.net | fdfc627c-d875-11e0-90f0-83df133b58cc | VM_DOWN_ERROR | 0 | alitke at brewer.alitke.net | fdfc627c-d875-11e0-90f0-83df133b58cc | VDS_INITIATED_RUN_VM_FAILED | 0 | alitke at brewer.alitke.net | (3 rows) > >Thanks > >Martin Perina > >----- Original Message ----- >> From: "Adam Litke" >> To: engine-devel at ovirt.org >> Sent: Monday, March 3, 2014 11:26:28 PM >> Subject: [Engine-devel] Schema upgrade failure on master >> >> Hi, >> >> I've recently rebased to master and it looks like the >> 03_05_0050_event_notification_methods.sql script is failing on schema >> upgrade. Is this a bug or am I doing something wrong? To upgrade I >> did the normal proceedure with my development installation: >> >> make install-dev ... >> ~/ovirt/bin/engine-setup >> >> Got this result in the log file: >> >> psql:/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql:10: >> ERROR: column "notification_method" contains null values >> FATAL: Cannot execute sql command: >> --file=/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql >> >> 2014-03-03 17:20:34 DEBUG otopi.context context._executeMethod:152 method >> exception >> Traceback (most recent call last): >> File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in >> _executeMethod >> method['method']() >> File >> "/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/db/schema.py", >> line 280, in _misc >> osetupcons.DBEnv.PGPASS_FILE >> File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 451, in >> execute >> command=args[0], >> RuntimeError: Command >> '/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/schema.sh' >> failed to execute >> >> -- >> Adam Litke >> _______________________________________________ >> Engine-devel mailing list >> Engine-devel at ovirt.org >> http://lists.ovirt.org/mailman/listinfo/engine-devel >> -- Adam Litke From liran.zelkha at gmail.com Tue Mar 4 13:20:57 2014 From: liran.zelkha at gmail.com (Liran Zelkha) Date: Tue, 4 Mar 2014 15:20:57 +0200 Subject: [Engine-devel] Schema upgrade failure on master In-Reply-To: <20140304131821.GF31669@redhat.com> References: <20140303222628.GE31669@redhat.com> <1109246737.12800424.1393909821557.JavaMail.zimbra@redhat.com> <20140304131821.GF31669@redhat.com> Message-ID: had the same issue. Run from psql: truncate table event_subscriber; Then run the script. Note that this will delete all the rows from your table... On Tue, Mar 4, 2014 at 3:18 PM, Adam Litke wrote: > On 04/03/14 00:10 -0500, Martin Perina wrote: > >> Hi Adam, >> >> I didn't notice any problem with this script. Was the database you tried >> to upgrade empty? >> If not could you please send me contents of your event_subscriber table? >> > > engine=> select * from event_subscriber ; > subscriber_id | event_up_name | > method_id | method_address | tag_name > --------------------------------------+--------------------- > --------+----------- > +--------------------------+---------- > fdfc627c-d875-11e0-90f0-83df133b58cc | VM_SET_TICKET | > 0 | alitke at brewer.alitke.net | fdfc627c-d875-11e0-90f0-83df133b58cc | > VM_DOWN_ERROR | 0 | alitke at brewer.alitke.net | > fdfc627c-d875-11e0-90f0-83df133b58cc | VDS_INITIATED_RUN_VM_FAILED | > 0 | alitke at brewer.alitke.net | (3 rows) > > > >> Thanks >> >> Martin Perina >> >> ----- Original Message ----- >> >>> From: "Adam Litke" >>> To: engine-devel at ovirt.org >>> Sent: Monday, March 3, 2014 11:26:28 PM >>> Subject: [Engine-devel] Schema upgrade failure on master >>> >>> Hi, >>> >>> I've recently rebased to master and it looks like the >>> 03_05_0050_event_notification_methods.sql script is failing on schema >>> upgrade. Is this a bug or am I doing something wrong? To upgrade I >>> did the normal proceedure with my development installation: >>> >>> make install-dev ... >>> ~/ovirt/bin/engine-setup >>> >>> Got this result in the log file: >>> >>> psql:/home/alitke/ovirt-**FILTERED**/share/ovirt-** >>> FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_ >>> methods.sql:10: >>> ERROR: column "notification_method" contains null values >>> FATAL: Cannot execute sql command: >>> --file=/home/alitke/ovirt-**FILTERED**/share/ovirt-** >>> FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql >>> >>> 2014-03-03 17:20:34 DEBUG otopi.context context._executeMethod:152 method >>> exception >>> Traceback (most recent call last): >>> File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in >>> _executeMethod >>> method['method']() >>> File >>> "/home/alitke/ovirt-**FILTERED**/share/ovirt-** >>> FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**- >>> setup/ovirt-**FILTERED**/db/schema.py", >>> line 280, in _misc >>> osetupcons.DBEnv.PGPASS_FILE >>> File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 451, in >>> execute >>> command=args[0], >>> RuntimeError: Command >>> '/home/alitke/ovirt-**FILTERED**/share/ovirt-** >>> FILTERED**/dbscripts/schema.sh' >>> failed to execute >>> >>> -- >>> Adam Litke >>> _______________________________________________ >>> Engine-devel mailing list >>> Engine-devel at ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/engine-devel >>> >>> > -- > Adam Litke > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From emesika at redhat.com Tue Mar 4 15:04:33 2014 From: emesika at redhat.com (Eli Mesika) Date: Tue, 4 Mar 2014 10:04:33 -0500 (EST) Subject: [Engine-devel] Schema upgrade failure on master In-Reply-To: References: <20140303222628.GE31669@redhat.com> <1109246737.12800424.1393909821557.JavaMail.zimbra@redhat.com> <20140304131821.GF31669@redhat.com> Message-ID: <144458390.12891044.1393945473963.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Liran Zelkha" > To: "Adam Litke" > Cc: "engine-devel" > Sent: Tuesday, March 4, 2014 3:20:57 PM > Subject: Re: [Engine-devel] Schema upgrade failure on master > > had the same issue. Run from psql: > truncate table event_subscriber; > Then run the script. Note that this will delete all the rows from your > table... Sorry for jumping on that late, but if this occurs when event_subscriber is not empty then this is a bug since it will fail also in customer site. In that case I think that you should open a bug and since the notification mechanism is heavily used , I think this is a blocker Can you please open a bug and assign on me Thanks Eli > > > On Tue, Mar 4, 2014 at 3:18 PM, Adam Litke < alitke at redhat.com > wrote: > > > On 04/03/14 00:10 -0500, Martin Perina wrote: > > > Hi Adam, > > I didn't notice any problem with this script. Was the database you tried to > upgrade empty? > If not could you please send me contents of your event_subscriber table? > > engine=> select * from event_subscriber ; > subscriber_id | event_up_name | method_id | method_address | tag_name > ------------------------------ --------+--------------------- > --------+----------- > +--------------------------+-- -------- > fdfc627c-d875-11e0-90f0- 83df133b58cc | VM_SET_TICKET | 0 | > alitke at brewer.alitke.net | fdfc627c-d875-11e0-90f0- 83df133b58cc | > VM_DOWN_ERROR | 0 | alitke at brewer.alitke.net | fdfc627c-d875-11e0-90f0- > 83df133b58cc | VDS_INITIATED_RUN_VM_FAILED | 0 | alitke at brewer.alitke.net | > (3 rows) > > > > > > Thanks > > Martin Perina > > ----- Original Message ----- > > > From: "Adam Litke" < alitke at redhat.com > > To: engine-devel at ovirt.org > Sent: Monday, March 3, 2014 11:26:28 PM > Subject: [Engine-devel] Schema upgrade failure on master > > Hi, > > I've recently rebased to master and it looks like the > 03_05_0050_event_notification_ methods.sql script is failing on schema > upgrade. Is this a bug or am I doing something wrong? To upgrade I > did the normal proceedure with my development installation: > > make install-dev ... > ~/ovirt/bin/engine-setup > > Got this result in the log file: > > psql:/home/alitke/ovirt-** FILTERED**/share/ovirt-** > FILTERED**/dbscripts/upgrade/ 03_05_0050_event_notification_ methods.sql:10: > ERROR: column "notification_method" contains null values > FATAL: Cannot execute sql command: > --file=/home/alitke/ovirt-** FILTERED**/share/ovirt-** > FILTERED**/dbscripts/upgrade/ 03_05_0050_event_notification_ methods.sql > > 2014-03-03 17:20:34 DEBUG otopi.context context._executeMethod:152 method > exception > Traceback (most recent call last): > File "/usr/lib/python2.7/site- packages/otopi/context.py", line 142, in > _executeMethod > method['method']() > File > "/home/alitke/ovirt-** FILTERED**/share/ovirt-** FILTERED**/setup/bin/../ > plugins/ovirt-**FILTERED**- setup/ovirt-**FILTERED**/db/ schema.py", > line 280, in _misc > osetupcons.DBEnv.PGPASS_FILE > File "/usr/lib/python2.7/site- packages/otopi/plugin.py", line 451, in > execute > command=args[0], > RuntimeError: Command > '/home/alitke/ovirt-** FILTERED**/share/ovirt-** FILTERED**/dbscripts/schema. > sh' > failed to execute > > -- > Adam Litke > ______________________________ _________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/ mailman/listinfo/engine-devel > > > -- > Adam Litke > ______________________________ _________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/ mailman/listinfo/engine-devel > > > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > From alonbl at redhat.com Wed Mar 5 08:13:05 2014 From: alonbl at redhat.com (Alon Bar-Lev) Date: Wed, 5 Mar 2014 03:13:05 -0500 (EST) Subject: [Engine-devel] [ATN][devenv] update for otopi In-Reply-To: <233617332.7313998.1394006939772.JavaMail.zimbra@redhat.com> Message-ID: <187261644.7314299.1394007185010.JavaMail.zimbra@redhat.com> Hello All, I would like to ask you to update your otopi package on your development machines to at least otopi-1.2.0_0.7. It is much closer to what we are going to release and will avoid many unrelated errors within log file due to a change in engine that soon to be applied. Please also notice that the nightly repository was modified recently and it is now changed place and was split here[1] and here[2], so it is a good opportunity to modify this as well in your /etc/yum.repo.d and have them both, dropping the old nightly. Thank you, Alon [1] http://resources.ovirt.org/pub/ovirt-snapshot/ [2] http://resources.ovirt.org/pub/ovirt-snapshot-static/ From iheim at redhat.com Wed Mar 5 09:19:08 2014 From: iheim at redhat.com (Itamar Heim) Date: Wed, 05 Mar 2014 11:19:08 +0200 Subject: [Engine-devel] Tweaking backup/restore of engine In-Reply-To: <5315A3E9.1090007@mittwald.de> References: <5314ACBF.90305@mittwald.de> <5315A3E9.1090007@mittwald.de> Message-ID: <5316EC0C.6090505@redhat.com> On 03/04/2014 12:00 PM, Sven Kieske wrote: > Hi, > > I forgot to mention a crucial > point: > > How long does the engine store past events, are they > stored forever or is there some kind of rotation? > > We mainly use the engine as a REST provider for managing > the virtual machines. > audit log gets deleted after 30 days by default. you can change that via config: packaging/dbscripts/upgrade/pre_upgrade/0000_config.sql:select fn_db_add_config_value('AuditLogAgingThreshold','30','general'); packaging/etc/engine-config/engine-config.properties:AuditLogAgingThreshold.description="Audit Log Aging Threshold (in days)" p From mtayer at redhat.com Wed Mar 5 10:20:12 2014 From: mtayer at redhat.com (Mooli Tayer) Date: Wed, 5 Mar 2014 05:20:12 -0500 (EST) Subject: [Engine-devel] Schema upgrade failure on master In-Reply-To: <144458390.12891044.1393945473963.JavaMail.zimbra@redhat.com> References: <20140303222628.GE31669@redhat.com> <1109246737.12800424.1393909821557.JavaMail.zimbra@redhat.com> <20140304131821.GF31669@redhat.com> <144458390.12891044.1393945473963.JavaMail.zimbra@redhat.com> Message-ID: <2125773437.14217642.1394014812350.JavaMail.zimbra@redhat.com> The problem is creating a p_key with null values. The script will fail on any user that has an event_subscriber record. bug: https://bugzilla.redhat.com/show_bug.cgi?id=1072866 patch: http://gerrit.ovirt.org/#/c/25372/ will need backport to 3.4! Mooli ----- Original Message ----- > > > ----- Original Message ----- > > From: "Liran Zelkha" > > To: "Adam Litke" > > Cc: "engine-devel" > > Sent: Tuesday, March 4, 2014 3:20:57 PM > > Subject: Re: [Engine-devel] Schema upgrade failure on master > > > > had the same issue. Run from psql: > > truncate table event_subscriber; > > Then run the script. Note that this will delete all the rows from your > > table... > > > Sorry for jumping on that late, but if this occurs when event_subscriber is > not empty then this is a bug since it will fail also in customer site. > In that case I think that you should open a bug and since the notification > mechanism is heavily used , I think this is a blocker > > Can you please open a bug and assign on me > > Thanks > Eli > > > > > > > On Tue, Mar 4, 2014 at 3:18 PM, Adam Litke < alitke at redhat.com > wrote: > > > > > > On 04/03/14 00:10 -0500, Martin Perina wrote: > > > > > > Hi Adam, > > > > I didn't notice any problem with this script. Was the database you tried to > > upgrade empty? > > If not could you please send me contents of your event_subscriber table? > > > > engine=> select * from event_subscriber ; > > subscriber_id | event_up_name | method_id | method_address | tag_name > > ------------------------------ --------+--------------------- > > --------+----------- > > +--------------------------+-- -------- > > fdfc627c-d875-11e0-90f0- 83df133b58cc | VM_SET_TICKET | 0 | > > alitke at brewer.alitke.net | fdfc627c-d875-11e0-90f0- 83df133b58cc | > > VM_DOWN_ERROR | 0 | alitke at brewer.alitke.net | fdfc627c-d875-11e0-90f0- > > 83df133b58cc | VDS_INITIATED_RUN_VM_FAILED | 0 | alitke at brewer.alitke.net | > > (3 rows) > > > > > > > > > > > > Thanks > > > > Martin Perina > > > > ----- Original Message ----- > > > > > > From: "Adam Litke" < alitke at redhat.com > > > To: engine-devel at ovirt.org > > Sent: Monday, March 3, 2014 11:26:28 PM > > Subject: [Engine-devel] Schema upgrade failure on master > > > > Hi, > > > > I've recently rebased to master and it looks like the > > 03_05_0050_event_notification_ methods.sql script is failing on schema > > upgrade. Is this a bug or am I doing something wrong? To upgrade I > > did the normal proceedure with my development installation: > > > > make install-dev ... > > ~/ovirt/bin/engine-setup > > > > Got this result in the log file: > > > > psql:/home/alitke/ovirt-** FILTERED**/share/ovirt-** > > FILTERED**/dbscripts/upgrade/ 03_05_0050_event_notification_ > > methods.sql:10: > > ERROR: column "notification_method" contains null values > > FATAL: Cannot execute sql command: > > --file=/home/alitke/ovirt-** FILTERED**/share/ovirt-** > > FILTERED**/dbscripts/upgrade/ 03_05_0050_event_notification_ methods.sql > > > > 2014-03-03 17:20:34 DEBUG otopi.context context._executeMethod:152 method > > exception > > Traceback (most recent call last): > > File "/usr/lib/python2.7/site- packages/otopi/context.py", line 142, in > > _executeMethod > > method['method']() > > File > > "/home/alitke/ovirt-** FILTERED**/share/ovirt-** FILTERED**/setup/bin/../ > > plugins/ovirt-**FILTERED**- setup/ovirt-**FILTERED**/db/ schema.py", > > line 280, in _misc > > osetupcons.DBEnv.PGPASS_FILE > > File "/usr/lib/python2.7/site- packages/otopi/plugin.py", line 451, in > > execute > > command=args[0], > > RuntimeError: Command > > '/home/alitke/ovirt-** FILTERED**/share/ovirt-** > > FILTERED**/dbscripts/schema. > > sh' > > failed to execute > > > > -- > > Adam Litke > > ______________________________ _________________ > > Engine-devel mailing list > > Engine-devel at ovirt.org > > http://lists.ovirt.org/ mailman/listinfo/engine-devel > > > > > > -- > > Adam Litke > > ______________________________ _________________ > > Engine-devel mailing list > > Engine-devel at ovirt.org > > http://lists.ovirt.org/ mailman/listinfo/engine-devel > > > > > > _______________________________________________ > > Engine-devel mailing list > > Engine-devel at ovirt.org > > http://lists.ovirt.org/mailman/listinfo/engine-devel > > > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > From dfediuck at redhat.com Wed Mar 5 10:55:13 2014 From: dfediuck at redhat.com (Doron Fediuck) Date: Wed, 5 Mar 2014 05:55:13 -0500 (EST) Subject: [Engine-devel] oVirt 3.4 RC test day In-Reply-To: <797153670.21010899.1394016856577.JavaMail.zimbra@redhat.com> Message-ID: <2115668151.21011474.1394016913571.JavaMail.zimbra@redhat.com> Hi everyone, tomorrow we're planning the last test day for 3.4, based on the RC release. All the needed information can be found in the 3.4 test day wiki[1]. See you all tomorrow, Doron [1] http://www.ovirt.org/OVirt_3.4_Test_Day From S.Kieske at mittwald.de Wed Mar 5 11:52:20 2014 From: S.Kieske at mittwald.de (Sven Kieske) Date: Wed, 5 Mar 2014 11:52:20 +0000 Subject: [Engine-devel] Tweaking backup/restore of engine In-Reply-To: <5316EC0C.6090505@redhat.com> References: <5314ACBF.90305@mittwald.de> <5315A3E9.1090007@mittwald.de> <5316EC0C.6090505@redhat.com> Message-ID: <53170FAF.9050601@mittwald.de> Wouldn't engine-config -s AuditLogAgingThreshold=X suffice? Am 05.03.2014 10:19, schrieb Itamar Heim: > On 03/04/2014 12:00 PM, Sven Kieske wrote: >> Hi, >> >> I forgot to mention a crucial >> point: >> >> How long does the engine store past events, are they >> stored forever or is there some kind of rotation? >> >> We mainly use the engine as a REST provider for managing >> the virtual machines. >> > > audit log gets deleted after 30 days by default. you can change that via > config: > > packaging/dbscripts/upgrade/pre_upgrade/0000_config.sql:select > fn_db_add_config_value('AuditLogAgingThreshold','30','general'); > packaging/etc/engine-config/engine-config.properties:AuditLogAgingThreshold.description="Audit > Log Aging Threshold (in days)" > p > > > -- Mit freundlichen Gr??en / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K?nigsberger Stra?e 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Gesch?ftsf?hrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen From iheim at redhat.com Wed Mar 5 12:15:08 2014 From: iheim at redhat.com (Itamar Heim) Date: Wed, 05 Mar 2014 14:15:08 +0200 Subject: [Engine-devel] Tweaking backup/restore of engine In-Reply-To: <53170FAF.9050601@mittwald.de> References: <5314ACBF.90305@mittwald.de> <5315A3E9.1090007@mittwald.de> <5316EC0C.6090505@redhat.com> <53170FAF.9050601@mittwald.de> Message-ID: <5317154C.9090107@redhat.com> On 03/05/2014 01:52 PM, Sven Kieske wrote: > Wouldn't engine-config -s AuditLogAgingThreshold=X suffice? > yes. I just sent the line with current value and the description > Am 05.03.2014 10:19, schrieb Itamar Heim: >> On 03/04/2014 12:00 PM, Sven Kieske wrote: >>> Hi, >>> >>> I forgot to mention a crucial >>> point: >>> >>> How long does the engine store past events, are they >>> stored forever or is there some kind of rotation? >>> >>> We mainly use the engine as a REST provider for managing >>> the virtual machines. >>> >> >> audit log gets deleted after 30 days by default. you can change that via >> config: >> >> packaging/dbscripts/upgrade/pre_upgrade/0000_config.sql:select >> fn_db_add_config_value('AuditLogAgingThreshold','30','general'); >> packaging/etc/engine-config/engine-config.properties:AuditLogAgingThreshold.description="Audit >> Log Aging Threshold (in days)" >> p >> >> >> > From emesika at redhat.com Wed Mar 5 14:50:42 2014 From: emesika at redhat.com (Eli Mesika) Date: Wed, 5 Mar 2014 09:50:42 -0500 (EST) Subject: [Engine-devel] Tweaking backup/restore of engine In-Reply-To: <5314ACBF.90305@mittwald.de> References: <5314ACBF.90305@mittwald.de> Message-ID: <1557414399.13494067.1394031042123.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Sven Kieske" > To: engine-devel at ovirt.org > Sent: Monday, March 3, 2014 6:25:39 PM > Subject: [Engine-devel] Tweaking backup/restore of engine > > Hi, > > currently all events are stored in the table audit_log > which all gets saved when you use the engine-backup > shell script. > > > the event log is full of these login lines (engine 3.3.2): > > 25652 fdfc627c-d875-11e0-90f0-83df133b58cc admin at internal > 00000000-0000-0000-0000-000000000000 \N \N \N \N \N 2014-01-20 > 06:39:17.222+01 USER_VDC_LOGIN 30 0 User admin at internal > logged in. f \N \N 00000000-0000-0000-0000-000000000000 \N \N \N > \N 00000000-0000-0000-0000-000000000000 \N oVirt -1 30 f \N > > this makes the log and db grow very large when you use the REST-API > to query ovirt for various data. > > Is this necessary for a working restore? > It would be cool if we could tweak the engine-backup > tool to just dump necessary tables so you don't have > to restore events from the past no one is interested > in. > > How does ovirt react, if I do not restore the content of the audit_log > table? > > If this works (restore without audit_log) I would prefer to have > this code upstream in ovirt git so I don't have to maintain > my own backupscript. > > Would it be possible to extend the existing backupscript > with a switch to not backup logs? > Currently it's just "all" or "just db". Hi Sven engine-backup is calling eventually a postgres utility named pg_dump this utility supports the following flag : --exclude-table-data=TABLE do NOT dump data for the named table(s) I think that a RFE for adding support for this flag in engine-backup will easily solve your problem Eli > > I also recall that there shouldn't occur multiple login events any > more since ovirt 3.3. but it still seems to be the case. > > I also do not understand how you would manage a stored authentication > via REST as REST is stateless. > > I would appreciate any feedback or thoughts on this topic. > -- > Mit freundlichen Gr??en / Regards > > Sven Kieske > > Systemadministrator > Mittwald CM Service GmbH & Co. KG > K?nigsberger Stra?e 6 > 32339 Espelkamp > T: +49-5772-293-100 > F: +49-5772-293-333 > https://www.mittwald.de > Gesch?ftsf?hrer: Robert Meyer > St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen > Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > From emesika at redhat.com Wed Mar 5 14:55:28 2014 From: emesika at redhat.com (Eli Mesika) Date: Wed, 5 Mar 2014 09:55:28 -0500 (EST) Subject: [Engine-devel] Tweaking backup/restore of engine and the table 'audit_log' In-Reply-To: <53158A33.3010706@mittwald.de> References: <5314ACBF.90305@mittwald.de> <1120227780.11414666.1393879274330.JavaMail.zimbra@redhat.com> <53158A33.3010706@mittwald.de> Message-ID: <1088725251.13504118.1394031328297.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Sven Kieske" > To: engine-devel at ovirt.org > Sent: Tuesday, March 4, 2014 10:10:31 AM > Subject: Re: [Engine-devel] Tweaking backup/restore of engine and the table 'audit_log' > > Thanks for your answer so far. > > Is there anyone around who knows > if the audit_log data is needed for a successful restore? > I'd rather not try this out myself. only the table is needed, the data may be truncated and this not affect the way the engine will work, you will just loose the events/alerts history. > > The reasoning behind this all is of course to keep backup > space as small as possible. > > Am 03.03.2014 21:41, schrieb Yedidyah Bar David: > > I have no idea - I guess the data is not necessary. > > -- > Mit freundlichen Gr??en / Regards > > Sven Kieske > > Systemadministrator > Mittwald CM Service GmbH & Co. KG > K?nigsberger Stra?e 6 > 32339 Espelkamp > T: +49-5772-293-100 > F: +49-5772-293-333 > https://www.mittwald.de > Gesch?ftsf?hrer: Robert Meyer > St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen > Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > From didi at redhat.com Wed Mar 5 15:02:40 2014 From: didi at redhat.com (Yedidyah Bar David) Date: Wed, 5 Mar 2014 10:02:40 -0500 (EST) Subject: [Engine-devel] Tweaking backup/restore of engine In-Reply-To: <1557414399.13494067.1394031042123.JavaMail.zimbra@redhat.com> References: <5314ACBF.90305@mittwald.de> <1557414399.13494067.1394031042123.JavaMail.zimbra@redhat.com> Message-ID: <1182666342.13349613.1394031760323.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Eli Mesika" > To: "Sven Kieske" > Cc: engine-devel at ovirt.org > Sent: Wednesday, March 5, 2014 4:50:42 PM > Subject: Re: [Engine-devel] Tweaking backup/restore of engine > > > > ----- Original Message ----- > > From: "Sven Kieske" > > To: engine-devel at ovirt.org > > Sent: Monday, March 3, 2014 6:25:39 PM > > Subject: [Engine-devel] Tweaking backup/restore of engine > > > > Hi, > > > > currently all events are stored in the table audit_log > > which all gets saved when you use the engine-backup > > shell script. > > > > > > the event log is full of these login lines (engine 3.3.2): > > > > 25652 fdfc627c-d875-11e0-90f0-83df133b58cc admin at internal > > 00000000-0000-0000-0000-000000000000 \N \N \N \N \N 2014-01-20 > > 06:39:17.222+01 USER_VDC_LOGIN 30 0 User admin at internal > > logged in. f \N \N 00000000-0000-0000-0000-000000000000 \N \N \N > > \N 00000000-0000-0000-0000-000000000000 \N oVirt -1 30 f \N > > > > this makes the log and db grow very large when you use the REST-API > > to query ovirt for various data. > > > > Is this necessary for a working restore? > > It would be cool if we could tweak the engine-backup > > tool to just dump necessary tables so you don't have > > to restore events from the past no one is interested > > in. > > > > How does ovirt react, if I do not restore the content of the audit_log > > table? > > > > If this works (restore without audit_log) I would prefer to have > > this code upstream in ovirt git so I don't have to maintain > > my own backupscript. > > > > Would it be possible to extend the existing backupscript > > with a switch to not backup logs? > > Currently it's just "all" or "just db". > > Hi Sven > > engine-backup is calling eventually a postgres utility named pg_dump > this utility supports the following flag : > > --exclude-table-data=TABLE do NOT dump data for the named table(s) Oh, didn't notice that one. Added in 9.2, so not for el6. > > > I think that a RFE for adding support for this flag in engine-backup will > easily solve your problem Perhaps better to allow passing arbitrary options to pg_dump. Or something like that. -- Didi From emesika at redhat.com Thu Mar 6 11:17:37 2014 From: emesika at redhat.com (Eli Mesika) Date: Thu, 6 Mar 2014 06:17:37 -0500 (EST) Subject: [Engine-devel] Tweaking backup/restore of engine In-Reply-To: <1182666342.13349613.1394031760323.JavaMail.zimbra@redhat.com> References: <5314ACBF.90305@mittwald.de> <1557414399.13494067.1394031042123.JavaMail.zimbra@redhat.com> <1182666342.13349613.1394031760323.JavaMail.zimbra@redhat.com> Message-ID: <1923409310.14148539.1394104657897.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Yedidyah Bar David" > To: "Eli Mesika" > Cc: "Sven Kieske" , engine-devel at ovirt.org > Sent: Wednesday, March 5, 2014 5:02:40 PM > Subject: Re: [Engine-devel] Tweaking backup/restore of engine > > ----- Original Message ----- > > From: "Eli Mesika" > > To: "Sven Kieske" > > Cc: engine-devel at ovirt.org > > Sent: Wednesday, March 5, 2014 4:50:42 PM > > Subject: Re: [Engine-devel] Tweaking backup/restore of engine > > > > > > > > ----- Original Message ----- > > > From: "Sven Kieske" > > > To: engine-devel at ovirt.org > > > Sent: Monday, March 3, 2014 6:25:39 PM > > > Subject: [Engine-devel] Tweaking backup/restore of engine > > > > > > Hi, > > > > > > currently all events are stored in the table audit_log > > > which all gets saved when you use the engine-backup > > > shell script. > > > > > > > > > the event log is full of these login lines (engine 3.3.2): > > > > > > 25652 fdfc627c-d875-11e0-90f0-83df133b58cc admin at internal > > > 00000000-0000-0000-0000-000000000000 \N \N \N \N \N 2014-01-20 > > > 06:39:17.222+01 USER_VDC_LOGIN 30 0 User admin at internal > > > logged in. f \N \N 00000000-0000-0000-0000-000000000000 \N \N \N > > > \N 00000000-0000-0000-0000-000000000000 \N oVirt -1 30 f \N > > > > > > this makes the log and db grow very large when you use the REST-API > > > to query ovirt for various data. > > > > > > Is this necessary for a working restore? > > > It would be cool if we could tweak the engine-backup > > > tool to just dump necessary tables so you don't have > > > to restore events from the past no one is interested > > > in. > > > > > > How does ovirt react, if I do not restore the content of the audit_log > > > table? > > > > > > If this works (restore without audit_log) I would prefer to have > > > this code upstream in ovirt git so I don't have to maintain > > > my own backupscript. > > > > > > Would it be possible to extend the existing backupscript > > > with a switch to not backup logs? > > > Currently it's just "all" or "just db". > > > > Hi Sven > > > > engine-backup is calling eventually a postgres utility named pg_dump > > this utility supports the following flag : > > > > --exclude-table-data=TABLE do NOT dump data for the named table(s) > > Oh, didn't notice that one. Added in 9.2, so not for el6. > > > > > > > I think that a RFE for adding support for this flag in engine-backup will > > easily solve your problem > > Perhaps better to allow passing arbitrary options to pg_dump. Or something > like that. So backup-engine will pass any additional parameters "as is" to the PG utility, Yes this would be great > -- > Didi > From S.Kieske at mittwald.de Thu Mar 6 12:14:48 2014 From: S.Kieske at mittwald.de (Sven Kieske) Date: Thu, 6 Mar 2014 12:14:48 +0000 Subject: [Engine-devel] Tweaking backup/restore of engine In-Reply-To: <1182666342.13349613.1394031760323.JavaMail.zimbra@redhat.com> References: <5314ACBF.90305@mittwald.de> <1557414399.13494067.1394031042123.JavaMail.zimbra@redhat.com> <1182666342.13349613.1394031760323.JavaMail.zimbra@redhat.com> Message-ID: <53186674.3050702@mittwald.de> I was just writing an RFE, when I read that it's not possible for el6. thats sad :/ Am 05.03.2014 16:02, schrieb Yedidyah Bar David: > Oh, didn't notice that one. Added in 9.2, so not for el6. -- Mit freundlichen Gr??en / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K?nigsberger Stra?e 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Gesch?ftsf?hrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen From S.Kieske at mittwald.de Thu Mar 6 12:24:33 2014 From: S.Kieske at mittwald.de (Sven Kieske) Date: Thu, 6 Mar 2014 12:24:33 +0000 Subject: [Engine-devel] Tweaking backup/restore of engine In-Reply-To: <5314ACBF.90305@mittwald.de> References: <5314ACBF.90305@mittwald.de> Message-ID: <531868BD.7050302@mittwald.de> Here's the RFE: https://bugzilla.redhat.com/show_bug.cgi?id=1073421 -- Mit freundlichen Gr??en / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K?nigsberger Stra?e 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Gesch?ftsf?hrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen From agrawalrohit92 at gmail.com Fri Mar 7 07:53:21 2014 From: agrawalrohit92 at gmail.com (Rohit Agrawal) Date: Fri, 7 Mar 2014 13:23:21 +0530 Subject: [Engine-devel] unable to create ui plugin Message-ID: i am trying to add the sample space shooter plugin and also helloWorld plugin in webadmin of ovirt engine. here is what i followed: 1. copied the folder through git to /usr/share/ovirt-engine/uiplugins 2. restart ovirt-engine Still unable to see the plugin. Any kind of help is appreciated -- rohit -------------- next part -------------- An HTML attachment was scrubbed... URL: From vszocs at redhat.com Fri Mar 7 14:35:40 2014 From: vszocs at redhat.com (Vojtech Szocs) Date: Fri, 7 Mar 2014 09:35:40 -0500 (EST) Subject: [Engine-devel] unable to create ui plugin In-Reply-To: References: Message-ID: <164090257.15699309.1394202940308.JavaMail.zimbra@redhat.com> Hi Rohit, which version of Engine are you using? AFAIK, UI plugins were introduced in 3.2.0 release. If you build Engine from source, you can check commit titled "UI plugins, part one" in git log. The easiest way to test UI plugins is to create a minimal plugin: http://www.ovirt.org/Features/UIPlugins#UI_plugin_cheat_sheet Make sure the plugin descriptor (i.e. minimal.json) is located at /usr/share/ovirt-engine/ui-plugins and readable by Engine. There is no need to restart Engine. Just refresh WebAdmin in your browser to reload all plugins, you should see following line in Engine log: INFO [org.ovirt.engine.ui.frontend.server.gwt.plugin.PluginDataManager] (http--0.0.0.0-8080-1) Reading UI plugin descriptor [/home/vszocs/build/ovirt-engine/share/ovirt-engine/ui-plugins/minimal.json] (Note: in above line, you can see that my Engine is at /home/vszocs/build/ovirt-engine instead of /usr because I'm building Engine from source via development environment.) If you cloned samples-uiplugins git repository and wish to try Space Shooter plugin, just make symlinks to expose plugin descriptor and resources: $ ln -s /path/to/samples-uiplugins/space-shooter-plugin/space-shooter.json /usr/share/ovirt-engine/ui-plugins/space-shooter.json $ ln -s /path/to/samples-uiplugins/space-shooter-plugin/space-shooter-resources /usr/share/ovirt-engine/ui-plugins/space-shooter-resources I've just tested both minimal and Space Shooter plugins, they work with latest Engine (master). If this still doesn't work for you, please send me the plugin and Engine logs. Regards, Vojtech ----- Original Message ----- > From: "Rohit Agrawal" > To: Engine-devel at ovirt.org > Sent: Friday, March 7, 2014 8:53:21 AM > Subject: [Engine-devel] unable to create ui plugin > > > i am trying to add the sample space shooter plugin and also helloWorld plugin > in webadmin of ovirt engine. > here is what i followed: > 1. copied the folder through git to /usr/share/ovirt-engine/uiplugins > 2. restart ovirt-engine > Still unable to see the plugin. > Any kind of help is appreciated > -- > rohit > > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > From vszocs at redhat.com Fri Mar 7 17:34:16 2014 From: vszocs at redhat.com (Vojtech Szocs) Date: Fri, 7 Mar 2014 12:34:16 -0500 (EST) Subject: [Engine-devel] Switched to thread-based GWT worker factory In-Reply-To: <249785196.15773774.1394212485563.JavaMail.zimbra@redhat.com> Message-ID: <480626336.15782436.1394213656657.JavaMail.zimbra@redhat.com> Hi guys, with patch [1] merged into master, GWT compiler will now use only thread-based GWT worker factory (ThreadedPermutationWorkerFactory) when compiling WebAdmin & UserPortal GUI. [1] http://gerrit.ovirt.org/#/c/25163/ In practice, this means that GWT compiler will spawn up to: max_worker_threads = min(localWorkers, 4) when compiling specific permutations (i.e. browser x locale). Note that localWorkers value can be controlled through: EXTRA_BUILD_FLAGS="-Dgwt.compiler.localWorkers=..." DEV_EXTRA_BUILD_FLAGS="-Dgwt.compiler.localWorkers=..." Before this patch was merged, GWT compiler spawned up to: max_external_processes = localWorkers i.e. using separate Java sub-process (CompilePermsServer) that communicates with GWT compiler process via socket. For localWorkers == 1, tests show minimal-to-zero improvement. However, for localWorkers > 1, tests show a slight improvement in favor of thread-based approach. Let me know if you have any questions. Regards, Vojtech From agrawalrohit92 at gmail.com Fri Mar 7 06:55:29 2014 From: agrawalrohit92 at gmail.com (Rohit Agrawal) Date: Fri, 7 Mar 2014 12:25:29 +0530 Subject: [Engine-devel] unable to create ui plugin Message-ID: i am trying to add the sample space shooter plugin and also helloWorld plugin in webadmin of ovirt engine. here is what i followed: 1. copied the folder through git to /usr/share/ovirt-engine/uiplugins 2. restart ovirt-engine Still unable to see the plugin. Any kind of help is appreciated -- rohit -------------- next part -------------- An HTML attachment was scrubbed... URL: From didi at redhat.com Sun Mar 9 08:53:58 2014 From: didi at redhat.com (Yedidyah Bar David) Date: Sun, 9 Mar 2014 04:53:58 -0400 (EDT) Subject: [Engine-devel] [Users] GSoC 14 Idea Discussion - virt-sparsify integration In-Reply-To: References: Message-ID: <109838948.16259456.1394355238193.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Utkarsh Singh" > To: users at ovirt.org > Sent: Friday, March 7, 2014 7:23:16 PM > Subject: [Users] GSoC 14 Idea Discussion - virt-sparsify integration > > Hello, > > I am Utkarsh, a 4th year undergrad from IIT Delhi and a GSoC-14 > aspirant. I have been lately involved in an ongoing project Baadal > Cloud Computing Platform in my institute, which has got me interested > in oVirt for a potential GSoC project. > > I was going through the virt-sparsify integration project idea. I have > gone through the architecture documentation on the oVirt website. As > far as I understand, the virt-sparsify integration needs to be done on > the VDSM daemon, and it's control is either going to be completely > independent of ovirt-engine (for example running it once every 24 > hours), or it's something that is centrally controlled by the > ovirt-engine through XML/RPC calls. The details are not specified in > the project ideas page. I would like to ask - > > 1. What would be the proposed ideal implementation? (Central-Control > or Independent-Control) > 2. Is virt-sparsify usage going to be automated or > administrator-triggered, or a combination of both? > > > There are some aspects of the idea, which I would like to discuss > before I start working on a proposal. > > It's not necessary that an automated usage of virt-sparsify is limited > to any simple idea. Architecture documentation states that > ovirt-engine has features like Monitoring that would allow > administrators (and possibly users) to be aware of vm-guest > performance as well as vm-host performance. I am not very sure about > how this data is collected, Is it done through MoM, or Is this > directly done by VDSM, or is someone else doing this (for hosts). It > would be great if someone can explain that to me. This information > about vm-guest usage and vm-host health can help in determining how > virt-sparsify is to be used. > > I am also not very clear about the Shared Storage component in the > architecture. Does oVirt make any assumptions about the Shared > Storage. For example, the performance difference between running > virt-sparsify on NFS as compared to running it (if possible) directly > on storage hardware. If the Storage solution is necessarily a NAS > instance, then virt-sparsify on NFS mount is the only option. > > > > Right now, I am in the process of setting up oVirt on my system, and > getting more familiar with the architecture. Regarding my experience. > I am acquainted with both Java and Python. I have little experience > with JBoss, but I have worked on some other Web Application Servers > like web2py and Play Framework. My involvement in Baadal Platform has > got me acquainted with libvirt/QEMU, the details of which I have > mentioned below (if anyone is interested). > > Please advise me about the things that I am missing about this > project. If there are some implementation details that I need to know, > kindly help me with that too. > > > > Looking forward. Thanks. > ===================== > Utkarsh > IIT Delhi > > Ongoing project details - > > Article (Old) > http://www.cc.iitd.ernet.in/CSC/index.php?view=article&id=123:baadal-the-iitd-computing-cloud > > Github > https://github.com/apoorvemohan/newbaadal > > My contribution - Deployment Scripting and Sandbox Environment Setup for > Testing > https://github.com/apoorvemohan/newbaadal/tree/master/baadaltesting/sandbox > _______________________________________________ > Users mailing list > Users at ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > (Adding vdsm-devel and engine-devel) -- Didi From chuan.liao at hp.com Mon Mar 10 09:17:13 2014 From: chuan.liao at hp.com (Liao, Chuan (Jason Liao, HPservers-Core-OE-PSC)) Date: Mon, 10 Mar 2014 09:17:13 +0000 Subject: [Engine-devel] Supposed to add per CPU usage related infomation into engine core and vdsm Message-ID: Hi All, In order to support NUMA and guest NUMA feature in ovirt. We need per NUMA node CPU usage or per CPU usage related information on engine core. This information will be used for VM who have NUMA aware information and find the best Host to run it on with best performance. Approach 1: 1. Sample data in vdsm for each CPU stats. (sys, usr, iowait, idle) 2. Calculate the each CPU usage information. (%sys, %usr, %iowait, %idle) 3. Transport the usage data to engine core. 4. Engine core merge per NUMA node CPU usage. (%sys, %usr, %iowait, %idle) Approach 2: 1. Sample data in vdsm for each CPU stats. (sys, usr, iowait, idle) 2. Calculate the each CPU usage information. (%sys, %usr, %iowait, %idle) 3. VDSM merge per NUMA node CPU usage. (%sys, %usr, %iowait, %idle) 4. Transport the usage data to engine core. Which one do you prefer, and why, or other solution. Best Regards, Jason Liao -------------- next part -------------- An HTML attachment was scrubbed... URL: From ofrenkel at redhat.com Mon Mar 10 10:04:59 2014 From: ofrenkel at redhat.com (Omer Frenkel) Date: Mon, 10 Mar 2014 06:04:59 -0400 (EDT) Subject: [Engine-devel] ovirt-engine-3.4.0 is broken In-Reply-To: <525164036.23938124.1394445686209.JavaMail.zimbra@redhat.com> Message-ID: <1378425823.23939362.1394445899356.JavaMail.zimbra@redhat.com> Hi, looks like both commits: http://gerrit.ovirt.org/#/c/25436/ http://gerrit.ovirt.org/#/c/25313/ introduced an upgrade script with the same number to the 3.4.0 branch, and now build fails. can you please fix this? From mperina at redhat.com Mon Mar 10 10:11:11 2014 From: mperina at redhat.com (Martin Perina) Date: Mon, 10 Mar 2014 06:11:11 -0400 (EDT) Subject: [Engine-devel] ovirt-engine-3.4.0 is broken In-Reply-To: <1378425823.23939362.1394445899356.JavaMail.zimbra@redhat.com> References: <1378425823.23939362.1394445899356.JavaMail.zimbra@redhat.com> Message-ID: <1936847087.1277974.1394446271273.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Omer Frenkel" > To: "Moti Asayag" , "Martin Perina" > Cc: "engine-devel" > Sent: Monday, March 10, 2014 11:04:59 AM > Subject: ovirt-engine-3.4.0 is broken > > Hi, > looks like both commits: > http://gerrit.ovirt.org/#/c/25436/ > http://gerrit.ovirt.org/#/c/25313/ > > introduced an upgrade script with the same number to the 3.4.0 branch, and > now build fails. > can you please fix this? > Moti answered me on IRC, that he will look at the issue. Hopefully he will rename 03_04_0650_delete_network_labels_action_groups.sql to 03_04_0660_delete_network_labels_action_groups.sql so the script names will be the same as in ovirt-engine-3.4 branch. From gchaplik at redhat.com Mon Mar 10 11:36:20 2014 From: gchaplik at redhat.com (Gilad Chaplik) Date: Mon, 10 Mar 2014 07:36:20 -0400 (EDT) Subject: [Engine-devel] Supposed to add per CPU usage related infomation into engine core and vdsm In-Reply-To: References: Message-ID: <888059896.16866790.1394451380205.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Chuan Liao (Jason Liao, HPservers-Core-OE-PSC)" > To: "arch" , "vdsm-devel" , engine-devel at ovirt.org > Cc: "Gilad Chaplik" , dfediuck at redhat.com, msivak at redhat.com > Sent: Monday, March 10, 2014 11:17:13 AM > Subject: Supposed to add per CPU usage related infomation into engine core and vdsm > > Hi All, > > In order to support NUMA and guest NUMA feature in ovirt. > We need per NUMA node CPU usage or per CPU usage related information on > engine core. > > This information will be used for VM who have NUMA aware information and find > the best Host to run it on with best performance. > > Approach 1: > > 1. Sample data in vdsm for each CPU stats. (sys, usr, iowait, idle) > > 2. Calculate the each CPU usage information. (%sys, %usr, %iowait, > %idle) > > 3. Transport the usage data to engine core. > > 4. Engine core merge per NUMA node CPU usage. (%sys, %usr, %iowait, > %idle) > +1, since this data can be used for hardware other than NUMA > Approach 2: > > 1. Sample data in vdsm for each CPU stats. (sys, usr, iowait, idle) > > 2. Calculate the each CPU usage information. (%sys, %usr, %iowait, > %idle) > > 3. VDSM merge per NUMA node CPU usage. (%sys, %usr, %iowait, %idle) > > 4. Transport the usage data to engine core. > > Which one do you prefer, and why, or other solution. > > Best Regards, > Jason Liao > > From emesika at redhat.com Mon Mar 10 11:49:55 2014 From: emesika at redhat.com (Eli Mesika) Date: Mon, 10 Mar 2014 07:49:55 -0400 (EDT) Subject: [Engine-devel] Supposed to add per CPU usage related infomation into engine core and vdsm In-Reply-To: <888059896.16866790.1394451380205.JavaMail.zimbra@redhat.com> References: <888059896.16866790.1394451380205.JavaMail.zimbra@redhat.com> Message-ID: <867513868.15558046.1394452195743.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Gilad Chaplik" > To: "Chuan Liao (Jason Liao, HPservers-Core-OE-PSC)" > Cc: engine-devel at ovirt.org, "arch" , "vdsm-devel" > Sent: Monday, March 10, 2014 1:36:20 PM > Subject: Re: [Engine-devel] Supposed to add per CPU usage related infomation into engine core and vdsm > > ----- Original Message ----- > > From: "Chuan Liao (Jason Liao, HPservers-Core-OE-PSC)" > > To: "arch" , "vdsm-devel" > > , engine-devel at ovirt.org > > Cc: "Gilad Chaplik" , dfediuck at redhat.com, > > msivak at redhat.com > > Sent: Monday, March 10, 2014 11:17:13 AM > > Subject: Supposed to add per CPU usage related infomation into engine core > > and vdsm > > > > Hi All, > > > > In order to support NUMA and guest NUMA feature in ovirt. > > We need per NUMA node CPU usage or per CPU usage related information on > > engine core. > > > > This information will be used for VM who have NUMA aware information and > > find > > the best Host to run it on with best performance. > > > > Approach 1: > > > > 1. Sample data in vdsm for each CPU stats. (sys, usr, iowait, idle) > > > > 2. Calculate the each CPU usage information. (%sys, %usr, %iowait, > > %idle) > > > > 3. Transport the usage data to engine core. > > > > 4. Engine core merge per NUMA node CPU usage. (%sys, %usr, %iowait, > > %idle) > > > > +1, since this data can be used for hardware other than NUMA +1 , can be relevant to engine reports as well .... > > > Approach 2: > > > > 1. Sample data in vdsm for each CPU stats. (sys, usr, iowait, idle) > > > > 2. Calculate the each CPU usage information. (%sys, %usr, %iowait, > > %idle) > > > > 3. VDSM merge per NUMA node CPU usage. (%sys, %usr, %iowait, %idle) > > > > 4. Transport the usage data to engine core. > > > > Which one do you prefer, and why, or other solution. > > > > Best Regards, > > Jason Liao > > > > > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > From masayag at redhat.com Mon Mar 10 12:31:53 2014 From: masayag at redhat.com (Moti Asayag) Date: Mon, 10 Mar 2014 08:31:53 -0400 (EDT) Subject: [Engine-devel] ovirt-engine-3.4.0 is broken In-Reply-To: <1936847087.1277974.1394446271273.JavaMail.zimbra@redhat.com> References: <1378425823.23939362.1394445899356.JavaMail.zimbra@redhat.com> <1936847087.1277974.1394446271273.JavaMail.zimbra@redhat.com> Message-ID: <1835007968.1349626.1394454713226.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Martin Perina" > To: "Omer Frenkel" > Cc: "Moti Asayag" , "engine-devel" > Sent: Monday, March 10, 2014 12:11:11 PM > Subject: Re: ovirt-engine-3.4.0 is broken > > > > ----- Original Message ----- > > From: "Omer Frenkel" > > To: "Moti Asayag" , "Martin Perina" > > > > Cc: "engine-devel" > > Sent: Monday, March 10, 2014 11:04:59 AM > > Subject: ovirt-engine-3.4.0 is broken > > > > Hi, > > looks like both commits: > > http://gerrit.ovirt.org/#/c/25436/ > > http://gerrit.ovirt.org/#/c/25313/ > > > > introduced an upgrade script with the same number to the 3.4.0 branch, and > > now build fails. > > can you please fix this? > > > > Moti answered me on IRC, that he will look at the issue. Hopefully > he will rename 03_04_0650_delete_network_labels_action_groups.sql > to 03_04_0660_delete_network_labels_action_groups.sql so the script names > will be the same as in ovirt-engine-3.4 branch. > The patch is ready to be merged on http://gerrit.ovirt.org/#/c/25564/ > > From chuan.liao at hp.com Tue Mar 11 06:02:23 2014 From: chuan.liao at hp.com (Liao, Chuan (Jason Liao, HPservers-Core-OE-PSC)) Date: Tue, 11 Mar 2014 06:02:23 +0000 Subject: [Engine-devel] Consider iowait add into usage CPU percentage Message-ID: Hi All, On engine core, The usage CPU percentage is calculated by %sys + %usr class VdsBrokerObjectsBuilder function updateVDSStatisticsData vds.setCpuSys(AssignDoubleValue(xmlRpcStruct, VdsProperties.cpu_sys)); vds.setCpuUser(AssignDoubleValue(xmlRpcStruct, VdsProperties.cpu_user)); if (vds.getCpuSys() != null && vds.getCpuUser() != null) { vds.setUsageCpuPercent((int) (vds.getCpuSys() + vds.getCpuUser())); } On vdsm, The %sys, %usr and %idle is calculated like below workflow, class API function getStats decStats = self._cif._hostStats.get() class clientIF function __init__ self._hostStats = sampling.HostStatsThread(log=log) self._hostStats.start() class HostStatsThread function get hs0, hs1 = self._samples[0], self._samples[-1] ... jiffies = (hs1.totcpu.user - hs0.totcpu.user) % (2 ** 32) stats['cpuUser'] = jiffies / interval / self._ncpus jiffies = (hs1.totcpu.sys - hs0.totcpu.sys) % (2 ** 32) stats['cpuSys'] = jiffies / interval / self._ncpus stats['cpuIdle'] = max(0.0, 100.0 - stats['cpuUser'] - stats['cpuSys']) class HostSample function __init__ self.totcpu = TotalCpuSample() class TotalCpuSample function __init__ self.user, userNice, self.sys, self.idle = \ map(int, file('/proc/stat').readline().split()[1:5]) self.user += userNice Question1: Why stats['cpuIdle'] do not use the sampling data totcpu.idle for calculating? Question2: There is another data named iowait in /proc/stat, do we need to consider add this into usage CPU percentage for calculating? Best Regards, Jason Liao -------------- next part -------------- An HTML attachment was scrubbed... URL: From sbonazzo at redhat.com Tue Mar 11 07:05:51 2014 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Tue, 11 Mar 2014 08:05:51 +0100 Subject: [Engine-devel] ovirt-engine-3.4.0 is broken In-Reply-To: <1835007968.1349626.1394454713226.JavaMail.zimbra@redhat.com> References: <1378425823.23939362.1394445899356.JavaMail.zimbra@redhat.com> <1936847087.1277974.1394446271273.JavaMail.zimbra@redhat.com> <1835007968.1349626.1394454713226.JavaMail.zimbra@redhat.com> Message-ID: <531EB5CF.5070504@redhat.com> Il 10/03/2014 13:31, Moti Asayag ha scritto: > > > ----- Original Message ----- >> From: "Martin Perina" >> To: "Omer Frenkel" >> Cc: "Moti Asayag" , "engine-devel" >> Sent: Monday, March 10, 2014 12:11:11 PM >> Subject: Re: ovirt-engine-3.4.0 is broken >> >> >> >> ----- Original Message ----- >>> From: "Omer Frenkel" >>> To: "Moti Asayag" , "Martin Perina" >>> >>> Cc: "engine-devel" >>> Sent: Monday, March 10, 2014 11:04:59 AM >>> Subject: ovirt-engine-3.4.0 is broken >>> >>> Hi, >>> looks like both commits: >>> http://gerrit.ovirt.org/#/c/25436/ >>> http://gerrit.ovirt.org/#/c/25313/ >>> >>> introduced an upgrade script with the same number to the 3.4.0 branch, and >>> now build fails. >>> can you please fix this? >>> >> >> Moti answered me on IRC, that he will look at the issue. Hopefully >> he will rename 03_04_0650_delete_network_labels_action_groups.sql >> to 03_04_0660_delete_network_labels_action_groups.sql so the script names >> will be the same as in ovirt-engine-3.4 branch. >> > > The patch is ready to be merged on http://gerrit.ovirt.org/#/c/25564/ Patch merged yesterday. > >> >> > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From S.Kieske at mittwald.de Tue Mar 11 08:09:51 2014 From: S.Kieske at mittwald.de (Sven Kieske) Date: Tue, 11 Mar 2014 08:09:51 +0000 Subject: [Engine-devel] Fwd: [vdsm] ovirt-guest-agent on debian In-Reply-To: <531D8746.5070907@mittwald.de> References: <531D8746.5070907@mittwald.de> Message-ID: <531EC489.3010809@mittwald.de> Forwarding to engine devel, because it seems there is no interest in this feature on vdsm-devel. Could this get integrated somehow? I managed to reuse the ubuntu build of ovirt-guest-agent for debian. -------- Original-Nachricht -------- Betreff: [vdsm] ovirt-guest-agent on debian Datum: Mon, 10 Mar 2014 09:36:11 +0000 Von: Sven Kieske An: VDSM Project Development Hi, I just did some additional research, here are my results: on a clean debian 7 x64 VM inside oVirt: I did as root: apt-get install python-software-properties add-apt-repository -y ppa:zhshzhou/vdsm-ubuntu vim /etc/apt/sources.list.d/zhshzhou-vdsm-ubuntu-wheezy.list change the following lines from: deb http://ppa.launchpad.net/zhshzhou/vdsm-ubuntu/ubuntu wheezy main deb-src http://ppa.launchpad.net/zhshzhou/vdsm-ubuntu/ubuntu wheezy main to: deb http://ppa.launchpad.net/zhshzhou/vdsm-ubuntu/ubuntu precise main deb-src http://ppa.launchpad.net/zhshzhou/vdsm-ubuntu/ubuntu precise main then: apt-get update apt-get install ovirt-guest-agent You get an error: Setting up ovirt-guest-agent (1.0.8.201309301944.gitb7f8f2-1ppa1) ... chown: cannot access `/var/log/ovirt-guest-agent/ovirt-guest-agent.log': No such file or directory but it works: ls -lashi /var/log/ovirt-guest-agent/ovirt-guest-agent.log 533212 4.0K -rw-r--r-- 1 ovirtagent ovirtagent 208 Mar 10 10:20 /var/log/ovirt-guest-agent/ovirt-guest-agent.log service ovirt-guest-agent status [ ok ] ovirt-guest-agent is running. IP information shows up in ovirt. it would be cool if the folder "precise" on the ppa could be cloned to be a folder "wheezy". So you would not need to change the apt-sources entries. I don't know why this chown error occurs, but it seems to work! -- Mit freundlichen Gr??en / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K?nigsberger Stra?e 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Gesch?ftsf?hrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen _______________________________________________ vdsm-devel mailing list vdsm-devel at lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel From iheim at redhat.com Tue Mar 11 08:23:18 2014 From: iheim at redhat.com (Itamar Heim) Date: Tue, 11 Mar 2014 10:23:18 +0200 Subject: [Engine-devel] Fwd: [vdsm] ovirt-guest-agent on debian In-Reply-To: <531EC489.3010809@mittwald.de> References: <531D8746.5070907@mittwald.de> <531EC489.3010809@mittwald.de> Message-ID: <531EC7F6.80803@redhat.com> On 03/11/2014 10:09 AM, Sven Kieske wrote: > Forwarding to engine devel, because it seems there is no interest in > this feature on vdsm-devel. > > Could this get integrated somehow? > I managed to reuse the ubuntu build of ovirt-guest-agent for debian. vinznenz? > > > -------- Original-Nachricht -------- > Betreff: [vdsm] ovirt-guest-agent on debian > Datum: Mon, 10 Mar 2014 09:36:11 +0000 > Von: Sven Kieske > An: VDSM Project Development > > Hi, > > I just did some additional research, here are my results: > > on a clean debian 7 x64 VM inside oVirt: > > I did as root: > apt-get install python-software-properties > add-apt-repository -y ppa:zhshzhou/vdsm-ubuntu > > vim /etc/apt/sources.list.d/zhshzhou-vdsm-ubuntu-wheezy.list > > change the following lines from: > > deb http://ppa.launchpad.net/zhshzhou/vdsm-ubuntu/ubuntu wheezy main > deb-src http://ppa.launchpad.net/zhshzhou/vdsm-ubuntu/ubuntu wheezy main > > to: > > deb http://ppa.launchpad.net/zhshzhou/vdsm-ubuntu/ubuntu precise main > deb-src http://ppa.launchpad.net/zhshzhou/vdsm-ubuntu/ubuntu precise main > > then: > > apt-get update > apt-get install ovirt-guest-agent > > You get an error: > > Setting up ovirt-guest-agent (1.0.8.201309301944.gitb7f8f2-1ppa1) ... > chown: cannot access `/var/log/ovirt-guest-agent/ovirt-guest-agent.log': > No such file or directory > > but it works: > > ls -lashi /var/log/ovirt-guest-agent/ovirt-guest-agent.log > 533212 4.0K -rw-r--r-- 1 ovirtagent ovirtagent 208 Mar 10 10:20 > /var/log/ovirt-guest-agent/ovirt-guest-agent.log > > service ovirt-guest-agent status > [ ok ] ovirt-guest-agent is running. > > IP information shows up in ovirt. > > it would be cool if the folder "precise" on the ppa could > be cloned to be a folder "wheezy". > > So you would not need to change the apt-sources entries. > > I don't know why this chown error occurs, but it seems to work! > > From vfeenstr at redhat.com Tue Mar 11 08:38:29 2014 From: vfeenstr at redhat.com (Vinzenz Feenstra) Date: Tue, 11 Mar 2014 09:38:29 +0100 Subject: [Engine-devel] Fwd: [vdsm] ovirt-guest-agent on debian In-Reply-To: <531EC7F6.80803@redhat.com> References: <531D8746.5070907@mittwald.de> <531EC489.3010809@mittwald.de> <531EC7F6.80803@redhat.com> Message-ID: <531ECB85.3060700@redhat.com> On 03/11/2014 09:23 AM, Itamar Heim wrote: > On 03/11/2014 10:09 AM, Sven Kieske wrote: >> Forwarding to engine devel, because it seems there is no interest in >> this feature on vdsm-devel. There is definitely an interest, I just haven't seen this email yesterday but this morning. Sorry for that. >> >> Could this get integrated somehow? >> I managed to reuse the ubuntu build of ovirt-guest-agent for debian. > > vinznenz? > >> >> >> -------- Original-Nachricht -------- >> Betreff: [vdsm] ovirt-guest-agent on debian >> Datum: Mon, 10 Mar 2014 09:36:11 +0000 >> Von: Sven Kieske >> An: VDSM Project Development >> >> Hi, >> >> I just did some additional research, here are my results: >> >> on a clean debian 7 x64 VM inside oVirt: >> >> I did as root: >> apt-get install python-software-properties >> add-apt-repository -y ppa:zhshzhou/vdsm-ubuntu >> >> vim /etc/apt/sources.list.d/zhshzhou-vdsm-ubuntu-wheezy.list >> >> change the following lines from: >> >> deb http://ppa.launchpad.net/zhshzhou/vdsm-ubuntu/ubuntu wheezy main >> deb-src http://ppa.launchpad.net/zhshzhou/vdsm-ubuntu/ubuntu wheezy main >> >> to: >> >> deb http://ppa.launchpad.net/zhshzhou/vdsm-ubuntu/ubuntu precise main >> deb-src http://ppa.launchpad.net/zhshzhou/vdsm-ubuntu/ubuntu precise >> main >> >> then: >> >> apt-get update >> apt-get install ovirt-guest-agent >> >> You get an error: >> >> Setting up ovirt-guest-agent (1.0.8.201309301944.gitb7f8f2-1ppa1) ... >> chown: cannot access `/var/log/ovirt-guest-agent/ovirt-guest-agent.log': >> No such file or directory >> >> but it works: >> >> ls -lashi /var/log/ovirt-guest-agent/ovirt-guest-agent.log >> 533212 4.0K -rw-r--r-- 1 ovirtagent ovirtagent 208 Mar 10 10:20 >> /var/log/ovirt-guest-agent/ovirt-guest-agent.log >> >> service ovirt-guest-agent status >> [ ok ] ovirt-guest-agent is running. >> >> IP information shows up in ovirt. >> >> it would be cool if the folder "precise" on the ppa could >> be cloned to be a folder "wheezy". >> >> So you would not need to change the apt-sources entries. >> >> I don't know why this chown error occurs, but it seems to work! >> >> > > -- Regards, Vinzenz Feenstra | Senior Software Engineer RedHat Engineering Virtualization R & D Phone: +420 532 294 625 IRC: vfeenstr or evilissimo Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From vikaskokare at gmail.com Tue Mar 11 10:11:41 2014 From: vikaskokare at gmail.com (Vikas Kokare) Date: Tue, 11 Mar 2014 15:41:41 +0530 Subject: [Engine-devel] oVirt Engine 3.2 ReST API Message-ID: As per the API documentation, the host cluster element "data_center id=" is both required at creation(exclamation in a triangle) as well as non-updatable(lock sign). Is it right to consider that, not only is this a required element, but it can't be changed and deleting(disassociation) is out of question? We have a RHEVM environment, where one such host cluster was created initially being associated to a data center. Later someone changed something, that resulted in the specific host cluster having no "data_center" element on it. Could it be that the association was deleted, or that the data_center itself was deleted, but the system didn't honor referential integrity, that it was being referred by other objects? -------------- next part -------------- An HTML attachment was scrubbed... URL: From ofrenkel at redhat.com Tue Mar 11 12:26:36 2014 From: ofrenkel at redhat.com (Omer Frenkel) Date: Tue, 11 Mar 2014 08:26:36 -0400 (EDT) Subject: [Engine-devel] oVirt Engine 3.2 ReST API In-Reply-To: References: Message-ID: <770563300.25027988.1394540796596.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Vikas Kokare" > To: engine-devel at ovirt.org > Sent: Tuesday, March 11, 2014 12:11:41 PM > Subject: [Engine-devel] oVirt Engine 3.2 ReST API > As per the API documentation, the host cluster element "data_center id=" is > both required at creation(exclamation in a triangle) as well as > non-updatable(lock sign). Is it right to consider that, not only is this a > required element, but it can't be changed and deleting(disassociation) is > out of question? > We have a RHEVM environment, where one such host cluster was created > initially being associated to a data center. Later someone changed > something, that resulted in the specific host cluster having no > "data_center" element on it. Could it be that the association was deleted, > or that the data_center itself was deleted, but the system didn't honor > referential integrity, that it was being referred by other objects? > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel it is possible to remove a data-center, even if it has clusters, as long there is no usage in the storage (vms, templates..) this makes the clusters to have no data-center, and then the cluster can be joined to a different data center (new/existing) -------------- next part -------------- An HTML attachment was scrubbed... URL: From sbonazzo at redhat.com Tue Mar 11 16:17:03 2014 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Tue, 11 Mar 2014 17:17:03 +0100 Subject: [Engine-devel] [ANN] oVirt 3.4.0 Second Release Candidate is now available Message-ID: <531F36FF.6000600@redhat.com> The oVirt team is pleased to announce that the 3.4.0 Second Release Candidate is now available for testing. Release notes and information on the changes for this update are still being worked on and will be available soon on the wiki[1]. Please ensure to follow install instruction from release notes if you're going to test it. The existing repository ovirt-3.4.0-prerelease has been updated for delivering this release candidate and future refreshes until final release. An oVirt Node iso will also be available soon. We decided to postpone Final Release by one week in order to properly test the bugs fixed since last Release Candidate. Help us make this the best release ever, testing it yourself! [1] http://www.ovirt.org/OVirt_3.4.0_release_notes -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From vszocs at redhat.com Tue Mar 11 17:57:11 2014 From: vszocs at redhat.com (Vojtech Szocs) Date: Tue, 11 Mar 2014 13:57:11 -0400 (EDT) Subject: [Engine-devel] Small suggestions for engine-log-collector In-Reply-To: <1504474667.17511317.1394559853264.JavaMail.zimbra@redhat.com> Message-ID: <800022326.17517459.1394560631804.JavaMail.zimbra@redhat.com> Hi guys, based on my testing during last week's oVirt 3.4 RC test day [1], I have a couple of small suggestions for engine-log-collector: 1, in /etc/ovirt-engine/logcollector.conf - I think there's typo: #key-file=/etc/pki/engine/keys/engine_id_rsa should be: #key-file=/etc/pki/ovirt-engine/keys/engine_id_rsa 2, to force password-based ssh auth, one has to do this: engine-log-collector -k "" because running this: engine-log-collector -k returns error message: error: -k option requires an argument however, help for -k option mentions *supplying* the argument: If a identity file is not supplied the program will prompt for a password. so either the help text should mention empty string, or -k option should allow missing argument (this was my initial understanding according to help text) Since these are just small things, I'm wondering if I should create RFE or if Keith/others can say if they are relevant. Thanks, Vojtech [1] http://etherpad.ovirt.org/p/3.4-testday-3 From kroberts at redhat.com Tue Mar 11 18:13:08 2014 From: kroberts at redhat.com (Keith Robertson) Date: Tue, 11 Mar 2014 14:13:08 -0400 (EDT) Subject: [Engine-devel] Small suggestions for engine-log-collector In-Reply-To: <800022326.17517459.1394560631804.JavaMail.zimbra@redhat.com> References: <800022326.17517459.1394560631804.JavaMail.zimbra@redhat.com> Message-ID: <651261410.16892578.1394561588396.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Vojtech Szocs" > To: "engine-devel" > Cc: "Keith Robertson" , "Einav Cohen" > Sent: Tuesday, March 11, 2014 1:57:11 PM > Subject: Small suggestions for engine-log-collector > > Hi guys, > > based on my testing during last week's oVirt 3.4 RC test day [1], > I have a couple of small suggestions for engine-log-collector: > > 1, in /etc/ovirt-engine/logcollector.conf - I think there's typo: > > #key-file=/etc/pki/engine/keys/engine_id_rsa > > should be: > > #key-file=/etc/pki/ovirt-engine/keys/engine_id_rsa > ACK > 2, to force password-based ssh auth, one has to do this: > In the normal scenario, the the ovirt user's public key should be installed into each hypervisor. Unless something has changed as a part of the hypervisor registration process this should be something that we can depend upon. Clearly, there are edge cases where you need to collect logs from a hypervisor that isn't properly registered with the RHEV-M. Was this your situation and how common do you think this scenario is? > engine-log-collector -k "" > Yes, you are nulling out the default value which causes the LC to prompt you for a PW. Perhaps we should document this as opposed to supplying a specific option? Sandro? > because running this: > > engine-log-collector -k > > returns error message: > > error: -k option requires an argument > > however, help for -k option mentions *supplying* the argument: > > If a identity file is not supplied the program will prompt for a > password. > > so either the help text should mention empty string, > or -k option should allow missing argument (this was > my initial understanding according to help text) > > Since these are just small things, I'm wondering if I should > create RFE or if Keith/others can say if they are relevant. > > Thanks, > Vojtech > > [1] http://etherpad.ovirt.org/p/3.4-testday-3 > From vszocs at redhat.com Tue Mar 11 18:15:04 2014 From: vszocs at redhat.com (Vojtech Szocs) Date: Tue, 11 Mar 2014 14:15:04 -0400 (EDT) Subject: [Engine-devel] REST API - where did bookmarks go? In-Reply-To: <134681088.17524268.1394561290638.JavaMail.zimbra@redhat.com> Message-ID: <281801554.17527047.1394561704228.JavaMail.zimbra@redhat.com> Hi guys, as part of prototyping new JavaScript binding for oVirt REST API, we chose a couple of business entities (resources) to experiment with. I just realized that requesting /ovirt-engine/api doesn't return any information about bookmarks. Where did bookmarks go? Is it possible to manage bookmarks through REST API? Note: WebAdmin currently gets bookmarks through GWT RPC by calling GetAllBookmarksQuery. Bookmark seems like proper backend business entity (with DAO and everything) so it should be exposed also via REST API.. or am I missing something? Thanks, Vojtech From jhernand at redhat.com Tue Mar 11 18:22:35 2014 From: jhernand at redhat.com (Juan Hernandez) Date: Tue, 11 Mar 2014 19:22:35 +0100 Subject: [Engine-devel] REST API - where did bookmarks go? In-Reply-To: <281801554.17527047.1394561704228.JavaMail.zimbra@redhat.com> References: <281801554.17527047.1394561704228.JavaMail.zimbra@redhat.com> Message-ID: <531F546B.8050104@redhat.com> On 03/11/2014 07:15 PM, Vojtech Szocs wrote: > Hi guys, > > as part of prototyping new JavaScript binding for oVirt REST API, > we chose a couple of business entities (resources) to experiment > with. > > I just realized that requesting /ovirt-engine/api doesn't return > any information about bookmarks. Where did bookmarks go? Is it > possible to manage bookmarks through REST API? > > Note: WebAdmin currently gets bookmarks through GWT RPC by calling > GetAllBookmarksQuery. Bookmark seems like proper backend business > entity (with DAO and everything) so it should be exposed also via > REST API.. or am I missing something? > > Thanks, > Vojtech > The didn't go anywhere, just never existed in the API. Please open a RFE to add them. -- 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. From chuan.liao at hp.com Wed Mar 12 02:09:59 2014 From: chuan.liao at hp.com (Liao, Chuan (Jason Liao, HPservers-Core-OE-PSC)) Date: Wed, 12 Mar 2014 02:09:59 +0000 Subject: [Engine-devel] Consider iowait add into usage CPU percentage In-Reply-To: References: Message-ID: Hi All, Any feedback for this topic? Add Doron and Martin in the mail list. Best Regards, Jason Liao From: vdsm-devel-bounces at lists.fedorahosted.org [mailto:vdsm-devel-bounces at lists.fedorahosted.org] On Behalf Of Liao, Chuan (Jason Liao, HPservers-Core-OE-PSC) Sent: 2014?3?11? 14:02 To: vdsm-devel; engine-devel at ovirt.org Cc: Liang, Shang-Chun (David Liang, HPservers-Core-OE-PSC); Vinod, Chegu; Gilad Chaplik Subject: [vdsm] Consider iowait add into usage CPU percentage Hi All, On engine core, The usage CPU percentage is calculated by %sys + %usr class VdsBrokerObjectsBuilder function updateVDSStatisticsData vds.setCpuSys(AssignDoubleValue(xmlRpcStruct, VdsProperties.cpu_sys)); vds.setCpuUser(AssignDoubleValue(xmlRpcStruct, VdsProperties.cpu_user)); if (vds.getCpuSys() != null && vds.getCpuUser() != null) { vds.setUsageCpuPercent((int) (vds.getCpuSys() + vds.getCpuUser())); } On vdsm, The %sys, %usr and %idle is calculated like below workflow, class API function getStats decStats = self._cif._hostStats.get() class clientIF function __init__ self._hostStats = sampling.HostStatsThread(log=log) self._hostStats.start() class HostStatsThread function get hs0, hs1 = self._samples[0], self._samples[-1] ? jiffies = (hs1.totcpu.user - hs0.totcpu.user) % (2 ** 32) stats['cpuUser'] = jiffies / interval / self._ncpus jiffies = (hs1.totcpu.sys - hs0.totcpu.sys) % (2 ** 32) stats['cpuSys'] = jiffies / interval / self._ncpus stats['cpuIdle'] = max(0.0, 100.0 - stats['cpuUser'] - stats['cpuSys']) class HostSample function __init__ self.totcpu = TotalCpuSample() class TotalCpuSample function __init__ self.user, userNice, self.sys, self.idle = \ map(int, file('/proc/stat').readline().split()[1:5]) self.user += userNice Question1: Why stats[?cpuIdle?] do not use the sampling data totcpu.idle for calculating? Question2: There is another data named iowait in /proc/stat, do we need to consider add this into usage CPU percentage for calculating? Best Regards, Jason Liao -------------- next part -------------- An HTML attachment was scrubbed... URL: From dfediuck at redhat.com Wed Mar 12 02:40:11 2014 From: dfediuck at redhat.com (Doron Fediuck) Date: Tue, 11 Mar 2014 22:40:11 -0400 (EDT) Subject: [Engine-devel] Consider iowait add into usage CPU percentage In-Reply-To: References: Message-ID: <1672560311.25683064.1394592011414.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Chuan Liao (Jason Liao, HPservers-Core-OE-PSC)" > To: "vdsm-devel" , engine-devel at ovirt.org > Cc: "Chegu Vinod" , "Shang-Chun Liang (David Liang, HPservers-Core-OE-PSC)" > > Sent: Wednesday, March 12, 2014 4:09:59 AM > Subject: Re: [Engine-devel] Consider iowait add into usage CPU percentage > > > > Hi All, > > > > Any feedback for this topic? > > Add Doron and Martin in the mail list. > > > > > Best Regards, > Jason Liao > > > > > > From: vdsm-devel-bounces at lists.fedorahosted.org > [mailto:vdsm-devel-bounces at lists.fedorahosted.org] On Behalf Of Liao, Chuan > (Jason Liao, HPservers-Core-OE-PSC) > Sent: 2014 ? 3 ? 11 ? 14:02 > To: vdsm-devel; engine-devel at ovirt.org > Cc: Liang, Shang-Chun (David Liang, HPservers-Core-OE-PSC); Vinod, Chegu; > Gilad Chaplik > Subject: [vdsm] Consider iowait add into usage CPU percentage > > > > > Hi All, > > > > On engine core, The usage CPU percentage is calculated by %sys + %usr > > > > class VdsBrokerObjectsBuilder > > function updateVDSStatisticsData > > vds.setCpuSys(AssignDoubleValue(xmlRpcStruct, VdsProperties.cpu_sys)); > > vds.setCpuUser(AssignDoubleValue(xmlRpcStruct, VdsProperties.cpu_user)); > > if (vds.getCpuSys() != null && vds.getCpuUser() != null) { > > vds.setUsageCpuPercent((int) (vds.getCpuSys() + vds.getCpuUser())); > > } > > > > On vdsm, The %sys, %usr and %idle is calculated like below workflow, > > > > class API > > function getStats > > decStats = self._cif._hostStats.get() > > class clientIF > > function __init__ > > self._hostStats = sampling.HostStatsThread(log=log) > > self._hostStats.start() > > class HostStatsThread > > function get > > hs0, hs1 = self._samples[0], self._samples[-1] > > ? > > jiffies = (hs1.totcpu.user - hs0.totcpu.user) % (2 ** 32) > > stats['cpuUser'] = jiffies / interval / self._ncpus > > jiffies = (hs1.totcpu.sys - hs0.totcpu.sys) % (2 ** 32) > > stats['cpuSys'] = jiffies / interval / self._ncpus > > stats['cpuIdle'] = max(0.0, 100.0 - stats['cpuUser'] - stats['cpuSys']) > > class HostSample > > function __init__ > > self.totcpu = TotalCpuSample() > > class TotalCpuSample > > function __init__ > > self.user, userNice, self.sys, self.idle = \ > > map(int, file('/proc/stat').readline().split()[1:5]) > > self.user += userNice > > > > Question1: Why stats[?cpuIdle?] do not use the sampling data totcpu.idle for > calculating? > I have a vague memory of this calculation which tries to level the numbers. ie- the assumption is that user and sys adds up to something which is less than 100. If this is not the case (multiple core / SMT) idle will be set to 0. But possibly Dan remembers something else? > > > Question2: There is another data named iowait in /proc/stat, do we need to > consider add this into usage CPU percentage for calculating? > Since the above excludes iowait, I wouldn't add it here. Otherwise we may have inconsistency with the numbers. > > > Best Regards, > Jason Liao > > > > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > From ofrenkel at redhat.com Wed Mar 12 06:45:17 2014 From: ofrenkel at redhat.com (Omer Frenkel) Date: Wed, 12 Mar 2014 02:45:17 -0400 (EDT) Subject: [Engine-devel] oVirt Engine 3.2 ReST API In-Reply-To: References: <770563300.25027988.1394540796596.JavaMail.zimbra@redhat.com> Message-ID: <1187183481.25735699.1394606717688.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Vikas Kokare" > To: "Omer Frenkel" > Sent: Wednesday, March 12, 2014 5:24:11 AM > Subject: Re: [Engine-devel] oVirt Engine 3.2 ReST API > The problem is this situation is not obvious from the documentation. The data > center field on the cluster is defined as required during creation and > non-updatable. How can that be explained? So its a question not just for > this example but for other entity associations too. i guess this is a bug in the documentation, this field is editable in this specific case only. can you open a bug? > On Tue, Mar 11, 2014 at 5:56 PM, Omer Frenkel < ofrenkel at redhat.com > wrote: > > > From: "Vikas Kokare" < vikaskokare at gmail.com > > > > > > > To: engine-devel at ovirt.org > > > > > > Sent: Tuesday, March 11, 2014 12:11:41 PM > > > > > > Subject: [Engine-devel] oVirt Engine 3.2 ReST API > > > > > > As per the API documentation, the host cluster element "data_center id=" > > > is > > > both required at creation(exclamation in a triangle) as well as > > > non-updatable(lock sign). Is it right to consider that, not only is this > > > a > > > required element, but it can't be changed and deleting(disassociation) is > > > out of question? > > > > > > We have a RHEVM environment, where one such host cluster was created > > > initially being associated to a data center. Later someone changed > > > something, that resulted in the specific host cluster having no > > > "data_center" element on it. Could it be that the association was > > > deleted, > > > or that the data_center itself was deleted, but the system didn't honor > > > referential integrity, that it was being referred by other objects? > > > > > > _______________________________________________ > > > > > > Engine-devel mailing list > > > > > > Engine-devel at ovirt.org > > > > > > http://lists.ovirt.org/mailman/listinfo/engine-devel > > > > > it is possible to remove a data-center, even if it has clusters, > > > as long there is no usage in the storage (vms, templates..) > > > this makes the clusters to have no data-center, > > > and then the cluster can be joined to a different data center > > (new/existing) > -------------- next part -------------- An HTML attachment was scrubbed... URL: From iheim at redhat.com Wed Mar 12 09:59:16 2014 From: iheim at redhat.com (Itamar Heim) Date: Wed, 12 Mar 2014 11:59:16 +0200 Subject: [Engine-devel] Change in ovirt-engine[master]: core: enable to decrease DC compatibility... In-Reply-To: <201403112226.s2BMQpjX013721@gerrit.ovirt.org> References: <201403112226.s2BMQpjX013721@gerrit.ovirt.org> Message-ID: <53202FF4.6030004@redhat.com> On 03/12/2014 12:26 AM, emesika at redhat.com wrote: > Eli Mesika has submitted this change and it was merged. > > Change subject: core: enable to decrease DC compatibility... > ...................................................................... > > > core: enable to decrease DC compatibility... > > enable to decrease DC compatibility version if DC has no clusters > > This patch enables to decrease the DC compatibility version if DC has no > clusters. Eli - just saw this. I'm pretty sure it would be *bad* to downgrade a DC version if it has storage domains as well. not sure if this is checked already or not. may also be an issue with some logical network features. > > Change-Id: I73284f641b7f80b380b39efbbd7b4566f55119b6 > Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1057029 > Signed-off-by: Eli Mesika > --- > M backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/storage/UpdateStoragePoolCommand.java > 1 file changed, 5 insertions(+), 2 deletions(-) > > Approvals: > Eli Mesika: Verified > Ravi Nori: Looks good to me, but someone else must approve > Yair Zaslavsky: Looks good to me, approved > > > From fsimonce at redhat.com Wed Mar 12 10:41:40 2014 From: fsimonce at redhat.com (Federico Simoncelli) Date: Wed, 12 Mar 2014 06:41:40 -0400 (EDT) Subject: [Engine-devel] Change in ovirt-engine[master]: core: enable to decrease DC compatibility... In-Reply-To: <53202FF4.6030004@redhat.com> References: <201403112226.s2BMQpjX013721@gerrit.ovirt.org> <53202FF4.6030004@redhat.com> Message-ID: <302554462.17939130.1394620900092.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Itamar Heim" > To: engine-devel at ovirt.org > Cc: "Eli Mesika" , "Federico Simoncelli" , "Allon Mureinik" > , "Livnat Peer" > Sent: Wednesday, March 12, 2014 11:59:16 AM > Subject: Re: Change in ovirt-engine[master]: core: enable to decrease DC compatibility... > > On 03/12/2014 12:26 AM, emesika at redhat.com wrote: > > Eli Mesika has submitted this change and it was merged. > > > > Change subject: core: enable to decrease DC compatibility... > > ...................................................................... > > > > > > core: enable to decrease DC compatibility... > > > > enable to decrease DC compatibility version if DC has no clusters > > > > This patch enables to decrease the DC compatibility version if DC has no > > clusters. > > Eli - just saw this. I'm pretty sure it would be *bad* to downgrade a DC > version if it has storage domains as well. not sure if this is checked > already or not. > > may also be an issue with some logical network features. Downgrading a DC from storage perspective is problematic (domain version, storage pool metadata removal, etc). This should be blocked. -- Federico From lpeer at redhat.com Wed Mar 12 10:42:44 2014 From: lpeer at redhat.com (Livnat Peer) Date: Wed, 12 Mar 2014 12:42:44 +0200 Subject: [Engine-devel] Change in ovirt-engine[master]: core: enable to decrease DC compatibility... In-Reply-To: <53202FF4.6030004@redhat.com> References: <201403112226.s2BMQpjX013721@gerrit.ovirt.org> <53202FF4.6030004@redhat.com> Message-ID: <53203A24.4040200@redhat.com> On 03/12/2014 11:59 AM, Itamar Heim wrote: > On 03/12/2014 12:26 AM, emesika at redhat.com wrote: >> Eli Mesika has submitted this change and it was merged. >> >> Change subject: core: enable to decrease DC compatibility... >> ...................................................................... >> >> >> core: enable to decrease DC compatibility... >> >> enable to decrease DC compatibility version if DC has no clusters >> >> This patch enables to decrease the DC compatibility version if DC has no >> clusters. > > Eli - just saw this. I'm pretty sure it would be *bad* to downgrade a DC > version if it has storage domains as well. not sure if this is checked > already or not. > > may also be an issue with some logical network features. > Most of the network features are driven from cluster level, we enable using the features on all DC level (actually >=3.1) but actually enable /disable the feature when attaching the network to a cluster. So from network perspective I think it should be fine to downgrade the DC level even if there are networks in the DC (at least now this could change in future versions). In general I believe the use case for this patch is mostly for empty DCs so for simplicity we should block it if there are networks or SD in the DC when downgrading. Livnat >> >> Change-Id: I73284f641b7f80b380b39efbbd7b4566f55119b6 >> Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1057029 >> Signed-off-by: Eli Mesika >> --- >> M >> backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/storage/UpdateStoragePoolCommand.java >> >> 1 file changed, 5 insertions(+), 2 deletions(-) >> >> Approvals: >> Eli Mesika: Verified >> Ravi Nori: Looks good to me, but someone else must approve >> Yair Zaslavsky: Looks good to me, approved >> >> >> > From iheim at redhat.com Wed Mar 12 10:47:31 2014 From: iheim at redhat.com (Itamar Heim) Date: Wed, 12 Mar 2014 12:47:31 +0200 Subject: [Engine-devel] Change in ovirt-engine[master]: core: enable to decrease DC compatibility... In-Reply-To: <53203A24.4040200@redhat.com> References: <201403112226.s2BMQpjX013721@gerrit.ovirt.org> <53202FF4.6030004@redhat.com> <53203A24.4040200@redhat.com> Message-ID: <53203B43.9000409@redhat.com> On 03/12/2014 12:42 PM, Livnat Peer wrote: > In general I believe the use case for this patch is mostly for empty DCs > so for simplicity we should block it if there are networks or SD in the > DC when downgrading. other than ovirt/rhevm one of course. From vszocs at redhat.com Wed Mar 12 11:05:48 2014 From: vszocs at redhat.com (Vojtech Szocs) Date: Wed, 12 Mar 2014 07:05:48 -0400 (EDT) Subject: [Engine-devel] Small suggestions for engine-log-collector In-Reply-To: <651261410.16892578.1394561588396.JavaMail.zimbra@redhat.com> References: <800022326.17517459.1394560631804.JavaMail.zimbra@redhat.com> <651261410.16892578.1394561588396.JavaMail.zimbra@redhat.com> Message-ID: <41806725.17946913.1394622348436.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Keith Robertson" > To: "Vojtech Szocs" > Cc: "engine-devel" , "Einav Cohen" , "Sandro Bonazzola" > > Sent: Tuesday, March 11, 2014 7:13:08 PM > Subject: Re: Small suggestions for engine-log-collector > > > > ----- Original Message ----- > > From: "Vojtech Szocs" > > To: "engine-devel" > > Cc: "Keith Robertson" , "Einav Cohen" > > > > Sent: Tuesday, March 11, 2014 1:57:11 PM > > Subject: Small suggestions for engine-log-collector > > > > Hi guys, > > > > based on my testing during last week's oVirt 3.4 RC test day [1], > > I have a couple of small suggestions for engine-log-collector: > > > > 1, in /etc/ovirt-engine/logcollector.conf - I think there's typo: > > > > #key-file=/etc/pki/engine/keys/engine_id_rsa > > > > should be: > > > > #key-file=/etc/pki/ovirt-engine/keys/engine_id_rsa > > > > ACK http://gerrit.ovirt.org/#/c/25653/ > > > > 2, to force password-based ssh auth, one has to do this: > > > > In the normal scenario, the the ovirt user's public key should be installed > into each hypervisor. Unless something has changed as a part of the > hypervisor registration process this should be something that we can depend > upon. My host was F19 VM added to oVirt Engine via WebAdmin GUI. I thought that host deploy script should do the public key registration, though. > > Clearly, there are edge cases where you need to collect logs from a > hypervisor that isn't properly registered with the RHEV-M. Was this your > situation and how common do you think this scenario is? It was either a misconfiguration on my part or that I skipped some step with regard to public key registration. > > > engine-log-collector -k "" > > > > Yes, you are nulling out the default value which causes the LC to prompt you > for a PW. Perhaps we should document this as opposed to supplying a > specific option? Sandro? Well, the doc text says "If a identity file is not supplied..." which I understood as not supplying option value (i.e. "") at all, but this was just my understanding. > > > because running this: > > > > engine-log-collector -k > > > > returns error message: > > > > error: -k option requires an argument > > > > however, help for -k option mentions *supplying* the argument: > > > > If a identity file is not supplied the program will prompt for a > > password. > > > > so either the help text should mention empty string, > > or -k option should allow missing argument (this was > > my initial understanding according to help text) > > > > Since these are just small things, I'm wondering if I should > > create RFE or if Keith/others can say if they are relevant. > > > > Thanks, > > Vojtech > > > > [1] http://etherpad.ovirt.org/p/3.4-testday-3 > > > From vszocs at redhat.com Wed Mar 12 11:27:19 2014 From: vszocs at redhat.com (Vojtech Szocs) Date: Wed, 12 Mar 2014 07:27:19 -0400 (EDT) Subject: [Engine-devel] REST API - where did bookmarks go? In-Reply-To: <531F546B.8050104@redhat.com> References: <281801554.17527047.1394561704228.JavaMail.zimbra@redhat.com> <531F546B.8050104@redhat.com> Message-ID: <113223800.17954619.1394623639126.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Juan Hernandez" > To: "Vojtech Szocs" , "engine-devel" > Cc: "Einav Cohen" > Sent: Tuesday, March 11, 2014 7:22:35 PM > Subject: Re: REST API - where did bookmarks go? > > On 03/11/2014 07:15 PM, Vojtech Szocs wrote: > > Hi guys, > > > > as part of prototyping new JavaScript binding for oVirt REST API, > > we chose a couple of business entities (resources) to experiment > > with. > > > > I just realized that requesting /ovirt-engine/api doesn't return > > any information about bookmarks. Where did bookmarks go? Is it > > possible to manage bookmarks through REST API? > > > > Note: WebAdmin currently gets bookmarks through GWT RPC by calling > > GetAllBookmarksQuery. Bookmark seems like proper backend business > > entity (with DAO and everything) so it should be exposed also via > > REST API.. or am I missing something? > > > > Thanks, > > Vojtech > > > > The didn't go anywhere, just never existed in the API. Please open a RFE > to add them. Thanks, Juan. The RFE is here: https://bugzilla.redhat.com/1075556 > > -- > 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. > From lpeer at redhat.com Wed Mar 12 11:32:26 2014 From: lpeer at redhat.com (Livnat Peer) Date: Wed, 12 Mar 2014 13:32:26 +0200 Subject: [Engine-devel] Change in ovirt-engine[master]: core: enable to decrease DC compatibility... In-Reply-To: <53203B43.9000409@redhat.com> References: <201403112226.s2BMQpjX013721@gerrit.ovirt.org> <53202FF4.6030004@redhat.com> <53203A24.4040200@redhat.com> <53203B43.9000409@redhat.com> Message-ID: <532045CA.6050601@redhat.com> On 03/12/2014 12:47 PM, Itamar Heim wrote: > On 03/12/2014 12:42 PM, Livnat Peer wrote: >> In general I believe the use case for this patch is mostly for empty DCs >> so for simplicity we should block it if there are networks or SD in the >> DC when downgrading. > > other than ovirt/rhevm one of course. of course, the management network which is automatically created when creating the DC can be there. > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > > From kroberts at redhat.com Wed Mar 12 12:38:13 2014 From: kroberts at redhat.com (Keith Robertson) Date: Wed, 12 Mar 2014 08:38:13 -0400 Subject: [Engine-devel] Small suggestions for engine-log-collector In-Reply-To: <41806725.17946913.1394622348436.JavaMail.zimbra@redhat.com> References: <800022326.17517459.1394560631804.JavaMail.zimbra@redhat.com> <651261410.16892578.1394561588396.JavaMail.zimbra@redhat.com> <41806725.17946913.1394622348436.JavaMail.zimbra@redhat.com> Message-ID: <53205535.60800@redhat.com> On 03/12/2014 07:05 AM, Vojtech Szocs wrote: > > > ----- Original Message ----- >> From: "Keith Robertson" >> To: "Vojtech Szocs" >> Cc: "engine-devel" , "Einav Cohen" , "Sandro Bonazzola" >> >> Sent: Tuesday, March 11, 2014 7:13:08 PM >> Subject: Re: Small suggestions for engine-log-collector >> >> >> >> ----- Original Message ----- >>> From: "Vojtech Szocs" >>> To: "engine-devel" >>> Cc: "Keith Robertson" , "Einav Cohen" >>> >>> Sent: Tuesday, March 11, 2014 1:57:11 PM >>> Subject: Small suggestions for engine-log-collector >>> >>> Hi guys, >>> >>> based on my testing during last week's oVirt 3.4 RC test day [1], >>> I have a couple of small suggestions for engine-log-collector: >>> >>> 1, in /etc/ovirt-engine/logcollector.conf - I think there's typo: >>> >>> #key-file=/etc/pki/engine/keys/engine_id_rsa >>> >>> should be: >>> >>> #key-file=/etc/pki/ovirt-engine/keys/engine_id_rsa >>> >> >> ACK > > http://gerrit.ovirt.org/#/c/25653/ > >> >> >>> 2, to force password-based ssh auth, one has to do this: >>> >> >> In the normal scenario, the the ovirt user's public key should be installed >> into each hypervisor. Unless something has changed as a part of the >> hypervisor registration process this should be something that we can depend >> upon. > > My host was F19 VM added to oVirt Engine via WebAdmin GUI. I thought that > host deploy script should do the public key registration, though. > I'm pretty sure that public key registration used to be part of the deploy script. If this is no longer the case it is a fairly major supportability issue. >> >> Clearly, there are edge cases where you need to collect logs from a >> hypervisor that isn't properly registered with the RHEV-M. Was this your >> situation and how common do you think this scenario is? > > It was either a misconfiguration on my part or that I skipped some step with > regard to public key registration. > Understand. The reason why we bias the LC towards public key auth and fall back to PW auth is that the LC needs to make multiple calls[1] to each Hypervisor and, if you're not using public key auth it is definitely a sub-optimal usage experience. Multiply [1] times the N number of hyper-visors and the user's annoyance factor will surely reach a boiling point. ;) [1] - 1 ssh call to launch sos - 1 sftp call to get the report and remove it from /tmp >> >>> engine-log-collector -k "" >>> >> >> Yes, you are nulling out the default value which causes the LC to prompt you >> for a PW. Perhaps we should document this as opposed to supplying a >> specific option? Sandro? > > Well, the doc text says "If a identity file is not supplied..." which I > understood as not supplying option value (i.e. "") at all, but this was > just my understanding. > Your understanding is correct and you forced the tool not to find the default identity file with a clever null argument. There's nothing wrong with this usage per-se and maybe we should either document it or provide an explicit option to force PW auth. >> >>> because running this: >>> >>> engine-log-collector -k >>> >>> returns error message: >>> >>> error: -k option requires an argument >>> >>> however, help for -k option mentions *supplying* the argument: >>> >>> If a identity file is not supplied the program will prompt for a >>> password. >>> >>> so either the help text should mention empty string, >>> or -k option should allow missing argument (this was >>> my initial understanding according to help text) >>> >>> Since these are just small things, I'm wondering if I should >>> create RFE or if Keith/others can say if they are relevant. >>> >>> Thanks, >>> Vojtech >>> >>> [1] http://etherpad.ovirt.org/p/3.4-testday-3 >>> >> -- Keith Robertson Supervisor, Software Engineering Red Hat Subscription Engineering From agrawalrohit92 at gmail.com Wed Mar 12 13:49:01 2014 From: agrawalrohit92 at gmail.com (Rohit Agrawal) Date: Wed, 12 Mar 2014 19:19:01 +0530 Subject: [Engine-devel] Dependency checking tool Message-ID: hi, i am now trying to make some changes in ovirt engine code for which i neede to see the dependency. As there are many pom.xml files. Is there any dependency tool to see all the dependency. -- Regards, rohit -------------- next part -------------- An HTML attachment was scrubbed... URL: From awels at redhat.com Wed Mar 12 13:53:47 2014 From: awels at redhat.com (Alexander Wels) Date: Wed, 12 Mar 2014 09:53:47 -0400 Subject: [Engine-devel] Dependency checking tool In-Reply-To: References: Message-ID: <2575735.57VcTU7chS@awels> Rohit, You can run mvn dependency:tree -Dverbose To see the entire dependency tree. On Wednesday, March 12, 2014 07:19:01 PM Rohit Agrawal wrote: > hi, > i am now trying to make some changes in ovirt engine code for which i neede > to see the dependency. > As there are many pom.xml files. Is there any dependency tool to see all > the dependency. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gshereme at redhat.com Wed Mar 12 16:35:39 2014 From: gshereme at redhat.com (Greg Sheremeta) Date: Wed, 12 Mar 2014 12:35:39 -0400 (EDT) Subject: [Engine-devel] Dependency checking tool In-Reply-To: References: Message-ID: <515377229.9303982.1394642139979.JavaMail.zimbra@redhat.com> mvn dependency:tree Greg ----- Original Message ----- > From: "Rohit Agrawal" > To: engine-devel at ovirt.org > Sent: Wednesday, March 12, 2014 9:49:01 AM > Subject: [Engine-devel] Dependency checking tool > hi, > i am now trying to make some changes in ovirt engine code for which i neede > to see the dependency. > As there are many pom.xml files. Is there any dependency tool to see all the > dependency. > -- > Regards, > rohit > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From masayag at redhat.com Wed Mar 12 20:20:52 2014 From: masayag at redhat.com (Moti Asayag) Date: Wed, 12 Mar 2014 16:20:52 -0400 (EDT) Subject: [Engine-devel] Change in ovirt-engine[master]: core: enable to decrease DC compatibility... In-Reply-To: <53203A24.4040200@redhat.com> References: <201403112226.s2BMQpjX013721@gerrit.ovirt.org> <53202FF4.6030004@redhat.com> <53203A24.4040200@redhat.com> Message-ID: <852680674.2850211.1394655652908.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Livnat Peer" > To: "Itamar Heim" , engine-devel at ovirt.org > Sent: Wednesday, March 12, 2014 12:42:44 PM > Subject: Re: [Engine-devel] Change in ovirt-engine[master]: core: enable to decrease DC compatibility... > > On 03/12/2014 11:59 AM, Itamar Heim wrote: > > On 03/12/2014 12:26 AM, emesika at redhat.com wrote: > >> Eli Mesika has submitted this change and it was merged. > >> > >> Change subject: core: enable to decrease DC compatibility... > >> ...................................................................... > >> > >> > >> core: enable to decrease DC compatibility... > >> > >> enable to decrease DC compatibility version if DC has no clusters > >> > >> This patch enables to decrease the DC compatibility version if DC has no > >> clusters. > > > > Eli - just saw this. I'm pretty sure it would be *bad* to downgrade a DC > > version if it has storage domains as well. not sure if this is checked > > already or not. > > > > may also be an issue with some logical network features. > > > > Most of the network features are driven from cluster level, we enable > using the features on all DC level (actually >=3.1) but actually enable > /disable the feature when attaching the network to a cluster. > > So from network perspective I think it should be fine to downgrade the > DC level even if there are networks in the DC (at least now this could > change in future versions). > Actually we block adding or updating networks if the feature is not supported on the network's DC level, for example: STP, Jumbo frames and non-vm network. Therefore if the management network was configured with any of those feature, there is a need to either block the action or to 'initialize' the network to the default settings (as new network being added). > In general I believe the use case for this patch is mostly for empty DCs > so for simplicity we should block it if there are networks or SD in the > DC when downgrading. > > Livnat > > > >> > >> Change-Id: I73284f641b7f80b380b39efbbd7b4566f55119b6 > >> Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1057029 > >> Signed-off-by: Eli Mesika > >> --- > >> M > >> backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/storage/UpdateStoragePoolCommand.java > >> > >> 1 file changed, 5 insertions(+), 2 deletions(-) > >> > >> Approvals: > >> Eli Mesika: Verified > >> Ravi Nori: Looks good to me, but someone else must approve > >> Yair Zaslavsky: Looks good to me, approved > >> > >> > >> > > > > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > From masayag at redhat.com Wed Mar 12 20:26:01 2014 From: masayag at redhat.com (Moti Asayag) Date: Wed, 12 Mar 2014 16:26:01 -0400 (EDT) Subject: [Engine-devel] Dependency checking tool In-Reply-To: References: Message-ID: <604504430.2852784.1394655961197.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Rohit Agrawal" > To: engine-devel at ovirt.org > Sent: Wednesday, March 12, 2014 3:49:01 PM > Subject: [Engine-devel] Dependency checking tool > > hi, > i am now trying to make some changes in ovirt engine code for which i neede > to see the dependency. > As there are many pom.xml files. Is there any dependency tool to see all the > dependency. > If you're using eclipe - with the m2e (maven eclipse integration) plugin, you can click on the pom.xml and view the specific project dependencies and their hierarchies. Intellij should have also dependency viewer (haven't tried it though). > -- > Regards, > rohit > > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > From lpeer at redhat.com Wed Mar 12 20:33:45 2014 From: lpeer at redhat.com (Livnat Peer) Date: Wed, 12 Mar 2014 22:33:45 +0200 Subject: [Engine-devel] Change in ovirt-engine[master]: core: enable to decrease DC compatibility... In-Reply-To: <852680674.2850211.1394655652908.JavaMail.zimbra@redhat.com> References: <201403112226.s2BMQpjX013721@gerrit.ovirt.org> <53202FF4.6030004@redhat.com> <53203A24.4040200@redhat.com> <852680674.2850211.1394655652908.JavaMail.zimbra@redhat.com> Message-ID: <5320C4A9.5010209@redhat.com> On 03/12/2014 10:20 PM, Moti Asayag wrote: > > > ----- Original Message ----- >> From: "Livnat Peer" >> To: "Itamar Heim" , engine-devel at ovirt.org >> Sent: Wednesday, March 12, 2014 12:42:44 PM >> Subject: Re: [Engine-devel] Change in ovirt-engine[master]: core: enable to decrease DC compatibility... >> >> On 03/12/2014 11:59 AM, Itamar Heim wrote: >>> On 03/12/2014 12:26 AM, emesika at redhat.com wrote: >>>> Eli Mesika has submitted this change and it was merged. >>>> >>>> Change subject: core: enable to decrease DC compatibility... >>>> ...................................................................... >>>> >>>> >>>> core: enable to decrease DC compatibility... >>>> >>>> enable to decrease DC compatibility version if DC has no clusters >>>> >>>> This patch enables to decrease the DC compatibility version if DC has no >>>> clusters. >>> >>> Eli - just saw this. I'm pretty sure it would be *bad* to downgrade a DC >>> version if it has storage domains as well. not sure if this is checked >>> already or not. >>> >>> may also be an issue with some logical network features. >>> >> >> Most of the network features are driven from cluster level, we enable >> using the features on all DC level (actually >=3.1) but actually enable >> /disable the feature when attaching the network to a cluster. >> >> So from network perspective I think it should be fine to downgrade the >> DC level even if there are networks in the DC (at least now this could >> change in future versions). >> > > Actually we block adding or updating networks if the feature is not supported > on the network's DC level, for example: STP, Jumbo frames and non-vm network. > >From which DC level we support STP? Jumbo frames? non-vm network? isn't all of them supported in >=3.1 ? > Therefore if the management network was configured with any of those feature, > there is a need to either block the action or to 'initialize' the network to > the default settings (as new network being added). > >> In general I believe the use case for this patch is mostly for empty DCs >> so for simplicity we should block it if there are networks or SD in the >> DC when downgrading. >> >> Livnat >> >> >>>> >>>> Change-Id: I73284f641b7f80b380b39efbbd7b4566f55119b6 >>>> Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1057029 >>>> Signed-off-by: Eli Mesika >>>> --- >>>> M >>>> backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/storage/UpdateStoragePoolCommand.java >>>> >>>> 1 file changed, 5 insertions(+), 2 deletions(-) >>>> >>>> Approvals: >>>> Eli Mesika: Verified >>>> Ravi Nori: Looks good to me, but someone else must approve >>>> Yair Zaslavsky: Looks good to me, approved >>>> >>>> >>>> >>> >> >> _______________________________________________ >> Engine-devel mailing list >> Engine-devel at ovirt.org >> http://lists.ovirt.org/mailman/listinfo/engine-devel >> From masayag at redhat.com Wed Mar 12 20:44:07 2014 From: masayag at redhat.com (Moti Asayag) Date: Wed, 12 Mar 2014 16:44:07 -0400 (EDT) Subject: [Engine-devel] Change in ovirt-engine[master]: core: enable to decrease DC compatibility... In-Reply-To: <5320C4A9.5010209@redhat.com> References: <201403112226.s2BMQpjX013721@gerrit.ovirt.org> <53202FF4.6030004@redhat.com> <53203A24.4040200@redhat.com> <852680674.2850211.1394655652908.JavaMail.zimbra@redhat.com> <5320C4A9.5010209@redhat.com> Message-ID: <577568761.2861329.1394657047677.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Livnat Peer" > To: "Moti Asayag" > Cc: "Itamar Heim" , engine-devel at ovirt.org > Sent: Wednesday, March 12, 2014 10:33:45 PM > Subject: Re: [Engine-devel] Change in ovirt-engine[master]: core: enable to decrease DC compatibility... > > On 03/12/2014 10:20 PM, Moti Asayag wrote: > > > > > > ----- Original Message ----- > >> From: "Livnat Peer" > >> To: "Itamar Heim" , engine-devel at ovirt.org > >> Sent: Wednesday, March 12, 2014 12:42:44 PM > >> Subject: Re: [Engine-devel] Change in ovirt-engine[master]: core: enable > >> to decrease DC compatibility... > >> > >> On 03/12/2014 11:59 AM, Itamar Heim wrote: > >>> On 03/12/2014 12:26 AM, emesika at redhat.com wrote: > >>>> Eli Mesika has submitted this change and it was merged. > >>>> > >>>> Change subject: core: enable to decrease DC compatibility... > >>>> ...................................................................... > >>>> > >>>> > >>>> core: enable to decrease DC compatibility... > >>>> > >>>> enable to decrease DC compatibility version if DC has no clusters > >>>> > >>>> This patch enables to decrease the DC compatibility version if DC has no > >>>> clusters. > >>> > >>> Eli - just saw this. I'm pretty sure it would be *bad* to downgrade a DC > >>> version if it has storage domains as well. not sure if this is checked > >>> already or not. > >>> > >>> may also be an issue with some logical network features. > >>> > >> > >> Most of the network features are driven from cluster level, we enable > >> using the features on all DC level (actually >=3.1) but actually enable > >> /disable the feature when attaching the network to a cluster. > >> > >> So from network perspective I think it should be fine to downgrade the > >> DC level even if there are networks in the DC (at least now this could > >> change in future versions). > >> > > > > Actually we block adding or updating networks if the feature is not > > supported > > on the network's DC level, for example: STP, Jumbo frames and non-vm > > network. > > > > From which DC level we support STP? Jumbo frames? non-vm network? isn't > all of them supported in >=3.1 ? > Yes, mainly the problem with downgrading a DC to 3.0. > > Therefore if the management network was configured with any of those > > feature, > > there is a need to either block the action or to 'initialize' the network > > to > > the default settings (as new network being added). > > > >> In general I believe the use case for this patch is mostly for empty DCs > >> so for simplicity we should block it if there are networks or SD in the > >> DC when downgrading. > >> > >> Livnat > >> > >> > >>>> > >>>> Change-Id: I73284f641b7f80b380b39efbbd7b4566f55119b6 > >>>> Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1057029 > >>>> Signed-off-by: Eli Mesika > >>>> --- > >>>> M > >>>> backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/storage/UpdateStoragePoolCommand.java > >>>> > >>>> 1 file changed, 5 insertions(+), 2 deletions(-) > >>>> > >>>> Approvals: > >>>> Eli Mesika: Verified > >>>> Ravi Nori: Looks good to me, but someone else must approve > >>>> Yair Zaslavsky: Looks good to me, approved > >>>> > >>>> > >>>> > >>> > >> > >> _______________________________________________ > >> Engine-devel mailing list > >> Engine-devel at ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/engine-devel > >> > > From sbonazzo at redhat.com Thu Mar 13 12:27:46 2014 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Thu, 13 Mar 2014 13:27:46 +0100 Subject: [Engine-devel] Small suggestions for engine-log-collector In-Reply-To: <651261410.16892578.1394561588396.JavaMail.zimbra@redhat.com> References: <800022326.17517459.1394560631804.JavaMail.zimbra@redhat.com> <651261410.16892578.1394561588396.JavaMail.zimbra@redhat.com> Message-ID: <5321A442.1030307@redhat.com> Il 11/03/2014 19:13, Keith Robertson ha scritto: > > > ----- Original Message ----- >> From: "Vojtech Szocs" To: "engine-devel" Cc: "Keith Robertson" , "Einav Cohen" >> Sent: Tuesday, March 11, 2014 1:57:11 PM Subject: Small suggestions for engine-log-collector >> >> Hi guys, >> >> based on my testing during last week's oVirt 3.4 RC test day [1], I have a couple of small suggestions for engine-log-collector: >> >> 1, in /etc/ovirt-engine/logcollector.conf - I think there's typo: >> >> #key-file=/etc/pki/engine/keys/engine_id_rsa >> >> should be: >> >> #key-file=/etc/pki/ovirt-engine/keys/engine_id_rsa >> > > ACK merged. > > >> 2, to force password-based ssh auth, one has to do this: >> > > In the normal scenario, the the ovirt user's public key should be installed into each hypervisor. Unless something has changed as a part of the > hypervisor registration process this should be something that we can depend upon. > > Clearly, there are edge cases where you need to collect logs from a hypervisor that isn't properly registered with the RHEV-M. Was this your > situation and how common do you think this scenario is? > >> engine-log-collector -k "" >> > > Yes, you are nulling out the default value which causes the LC to prompt you for a PW. Perhaps we should document this as opposed to supplying a > specific option? Sandro? yes, maybe a better explanation in man page. Vojtech have you opened a bz about that? Thanks for the report and for the patch you submitted! > >> because running this: >> >> engine-log-collector -k >> >> returns error message: >> >> error: -k option requires an argument >> >> however, help for -k option mentions *supplying* the argument: >> >> If a identity file is not supplied the program will prompt for a password. >> >> so either the help text should mention empty string, or -k option should allow missing argument (this was my initial understanding according to >> help text) >> >> Since these are just small things, I'm wondering if I should create RFE or if Keith/others can say if they are relevant. >> >> Thanks, Vojtech >> >> [1] http://etherpad.ovirt.org/p/3.4-testday-3 >> -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From jmoskovc at redhat.com Thu Mar 13 13:27:11 2014 From: jmoskovc at redhat.com (Jiri Moskovcak) Date: Thu, 13 Mar 2014 14:27:11 +0100 Subject: [Engine-devel] hosted engine in 3.4 Message-ID: <5321B22F.2000408@redhat.com> Hi, I was testing the hosted-engine in 3.4 and ran into some troubles, so I'm going to share the results to get some help (or ideas how to fix those problems) Minor: 1. You need to have some MAC address with static ip and FQDN, otherwise you have to change /etc/hosts at least for the first part of the setup - I think the setup wizard should be improved to do this workaround automatically 2. When the VM install is complete I would expect the setup wizard to install the engine to the VM automatically - which at least in my case - doesn't happen - I found a mallformed fedora-virt-prerelease.repoo file on the installed vm, which might be the cause: https://bugzilla.redhat.com/show_bug.cgi?id=1075963 Major: 1. once I managed to install the engine to the vm it tried to add the host it was running on to the engine and it failed with a message "Host compatibility version doesn't match the cluster compatibility version", and then it marked the host as non operational which killed the vm with the engine, so the engine actually committed suicide... - the host and the engine were installed from the same repo, so I guess the incompatibility was caused by the CPU family, and even if I made the mistake I think the engine should be a bit more clever and not kill itself --Jirka From didi at redhat.com Thu Mar 13 13:54:09 2014 From: didi at redhat.com (Yedidyah Bar David) Date: Thu, 13 Mar 2014 09:54:09 -0400 (EDT) Subject: [Engine-devel] hosted engine in 3.4 In-Reply-To: <5321B22F.2000408@redhat.com> References: <5321B22F.2000408@redhat.com> Message-ID: <1585193153.19831369.1394718849438.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Jiri Moskovcak" > To: "engine-devel" > Sent: Thursday, March 13, 2014 3:27:11 PM > Subject: [Engine-devel] hosted engine in 3.4 > > Hi, > I was testing the hosted-engine in 3.4 and ran into some troubles, so > I'm going to share the results to get some help (or ideas how to fix > those problems) > > Minor: > 1. You need to have some MAC address with static ip and FQDN, otherwise > you have to change /etc/hosts at least for the first part of the setup > > - I think the setup wizard should be improved to do this workaround > automatically Not sure what you refer to - the host? VM? Both? deploy lets you change the MAC for the VM if you want, and also shows you the random MAC it have chosen. Both of these should allow you to config your dhcp/dns server at that point and have the VM automatically get the right ip/hostname during OS installation. Not sure what you mean exactly - we never edit /etc/hosts files, and generally expect a stable dhcp/dns installation. That's true also for a normal engine installation. > > 2. When the VM install is complete I would expect the setup wizard to > install the engine to the VM automatically - which at least in my case - > doesn't happen We intend to supply some image (iso/ovf) that will include everything needed. Not sure when this will be ready. For the time being, you do everything by yourself - install the OS, add repos, install and setup the engine, etc. Note that you can choose network boot and make everything automated. > > - I found a mallformed fedora-virt-prerelease.repoo file on the > installed vm, which might be the cause: > https://bugzilla.redhat.com/show_bug.cgi?id=1075963 > > Major: > 1. once I managed to install the engine to the vm it tried to add the > host it was running on to the engine and it failed with a message "Host > compatibility version doesn't match the cluster compatibility version", > and then it marked the host as non operational which killed the vm with > the engine, so the engine actually committed suicide... > > - the host and the engine were installed from the same repo, so I guess > the incompatibility was caused by the CPU family, and even if I made the That's probably because you have a problem with the repo (as pointed above) and install different versions on the host and VM. > mistake I think the engine should be a bit more clever and not kill itself I might agree here, but generally this should not happen. You are of course more than welcome to open bugs where relevant! -- Didi From sbonazzo at redhat.com Thu Mar 13 13:56:37 2014 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Thu, 13 Mar 2014 14:56:37 +0100 Subject: [Engine-devel] hosted engine in 3.4 In-Reply-To: <5321B22F.2000408@redhat.com> References: <5321B22F.2000408@redhat.com> Message-ID: <5321B915.9070405@redhat.com> Il 13/03/2014 14:27, Jiri Moskovcak ha scritto: > Hi, > I was testing the hosted-engine in 3.4 and ran into some troubles, so I'm going to share the results to get some help (or ideas how to fix those > problems) Hi, thanks for testing Hosted Engine > > Minor: > 1. You need to have some MAC address with static ip and FQDN, otherwise you have to change /etc/hosts at least for the first part of the setup > > - I think the setup wizard should be improved to do this workaround automatically Well, you can have DHCP and DNS configured before starting the deploy process and assign the MAC address to the VM you're going to create for getting the right IP and avoid to use /etc/hosts. But yes, otherwise you need to use static IPs and configure /etc/hosts accordingly. > > 2. When the VM install is complete I would expect the setup wizard to install the engine to the VM automatically - which at least in my case - doesn't > happen No, it's a manual step, there's no automation for doing that yet. > > - I found a mallformed fedora-virt-prerelease.repoo file on the installed vm, which might be the cause: > https://bugzilla.redhat.com/show_bug.cgi?id=1075963 Can't reproduce the issue, closed as works for me, please reopen it if you can provide a sequence for reproducing it. > > Major: > 1. once I managed to install the engine to the vm it tried to add the host it was running on to the engine and it failed with a message "Host > compatibility version doesn't match the cluster compatibility version", and then it marked the host as non operational which killed the vm with the > engine, so the engine actually committed suicide... this is indeed due to malformed fedora-virt-prerelease.repoo. You had VDSM running in 3.3 compatibility mode because you're missing latest libvirt while the engine is running a cluster in 3.4 compatibility mode. > > - the host and the engine were installed from the same repo, so I guess the incompatibility was caused by the CPU family, and even if I made the > mistake I think the engine should be a bit more clever and not kill itself I think that we can add a check on vdsm compatibility level and create the engine cluster with the same level, not assuming that people are running latest libvirt. BTW I'm not sure about implications in running Hosted Engine in 3.3 compatibility mode. CCing VDSM people. > > > --Jirka > > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From gshereme at redhat.com Thu Mar 13 15:02:15 2014 From: gshereme at redhat.com (Greg Sheremeta) Date: Thu, 13 Mar 2014 11:02:15 -0400 (EDT) Subject: [Engine-devel] attn ui devs: why do we use inputs for labels? In-Reply-To: <1106090098.9594351.1394722606183.JavaMail.zimbra@redhat.com> Message-ID: <1740187465.9597169.1394722935614.JavaMail.zimbra@redhat.com> Hi fellow UI developers, Can someone explain why we are using "input type=text" fields to render labels? (see screenshot[1]) This seems like bad practice for a few reasons: * it's not semantic HTML * inputs do not have variable sizing like text. They cannot shrink down to the size of the text, which makes positioning difficult. * common browser extensions such as LastPass can be confused (see screenshot[1] -- lastpass sees these labels for the text fields they are, and attempts to help the user fill them in -- that's what those gray asterisks are. Very confusing.) I'd like to pursue correcting this, if possible. Thanks, Greg [1] http://i.imgur.com/AweOhJe.png Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gshereme at redhat.com From jmoskovc at redhat.com Thu Mar 13 14:10:04 2014 From: jmoskovc at redhat.com (Jiri Moskovcak) Date: Thu, 13 Mar 2014 15:10:04 +0100 Subject: [Engine-devel] hosted engine in 3.4 In-Reply-To: <1585193153.19831369.1394718849438.JavaMail.zimbra@redhat.com> References: <5321B22F.2000408@redhat.com> <1585193153.19831369.1394718849438.JavaMail.zimbra@redhat.com> Message-ID: <5321BC3C.5020305@redhat.com> On 03/13/2014 02:54 PM, Yedidyah Bar David wrote: > ----- Original Message ----- >> From: "Jiri Moskovcak" >> To: "engine-devel" >> Sent: Thursday, March 13, 2014 3:27:11 PM >> Subject: [Engine-devel] hosted engine in 3.4 >> >> Hi, >> I was testing the hosted-engine in 3.4 and ran into some troubles, so >> I'm going to share the results to get some help (or ideas how to fix >> those problems) >> >> Minor: >> 1. You need to have some MAC address with static ip and FQDN, otherwise >> you have to change /etc/hosts at least for the first part of the setup >> >> - I think the setup wizard should be improved to do this workaround >> automatically > > Not sure what you refer to - the host? VM? Both? > > deploy lets you change the MAC for the VM if you want, and also shows you > the random MAC it have chosen. Both of these should allow you to config > your dhcp/dns server at that point and have the VM automatically get the > right ip/hostname during OS installation. > > Not sure what you mean exactly - we never edit /etc/hosts files, and > generally expect a stable dhcp/dns installation. That's true also for a > normal engine installation. > - the VM, I was in the situation where I didn't have the chance to change the dhcp config at the time when I was installing the VM, so the only way for me was to change the /etc/hosts to cheat the setup wizard >> >> 2. When the VM install is complete I would expect the setup wizard to >> install the engine to the VM automatically - which at least in my case - >> doesn't happen > > We intend to supply some image (iso/ovf) that will include everything > needed. Not sure when this will be ready. For the time being, you do > everything by yourself - install the OS, add repos, install and setup > the engine, etc. Note that you can choose network boot and make everything > automated. > - I'm talking about the engine install inside the VM. I have the VM with the os, so the hosted-engine-setup can ask for the root password and simply install all the packages and configure the engine (I don't consider this a bug more like a idea for improvements) >> >> - I found a mallformed fedora-virt-prerelease.repoo file on the >> installed vm, which might be the cause: >> https://bugzilla.redhat.com/show_bug.cgi?id=1075963 >> >> Major: >> 1. once I managed to install the engine to the vm it tried to add the >> host it was running on to the engine and it failed with a message "Host >> compatibility version doesn't match the cluster compatibility version", >> and then it marked the host as non operational which killed the vm with >> the engine, so the engine actually committed suicide... >> >> - the host and the engine were installed from the same repo, so I guess >> the incompatibility was caused by the CPU family, and even if I made the > > That's probably because you have a problem with the repo (as pointed above) > and install different versions on the host and VM. - no, when I found the broken repo file I've fixed it to use the same as the host and only after that I've installed the engine > >> mistake I think the engine should be a bit more clever and not kill itself > > I might agree here, but generally this should not happen. > > You are of course more than welcome to open bugs where relevant! > I will, just want to try that once more, to get more details. Thanks, Jirka From ecohen at redhat.com Thu Mar 13 16:14:51 2014 From: ecohen at redhat.com (Einav Cohen) Date: Thu, 13 Mar 2014 12:14:51 -0400 (EDT) Subject: [Engine-devel] attn ui devs: why do we use inputs for labels? In-Reply-To: <1740187465.9597169.1394722935614.JavaMail.zimbra@redhat.com> References: <1740187465.9597169.1394722935614.JavaMail.zimbra@redhat.com> Message-ID: <1579791205.26836676.1394727291548.JavaMail.zimbra@redhat.com> I could be wrong, but there is a chance that using "input type=text" allows selecting/copying the text, rather than a plain label, which doesn't allow that. I am not sure if there are any (additional?) advantages to using "input type=text" (the other UI maintainers will probably know better). > I'd like to pursue correcting this, if possible. if there is a more "correct" way that won't result in losing any existing functionality, +1. ---- Thanks, Einav ----- Original Message ----- > From: "Greg Sheremeta" > To: "engine-devel" > Sent: Thursday, March 13, 2014 11:02:15 AM > Subject: [Engine-devel] attn ui devs: why do we use inputs for labels? > > Hi fellow UI developers, > > Can someone explain why we are using "input type=text" fields to render > labels? (see screenshot[1]) This seems like bad practice for a few reasons: > * it's not semantic HTML > * inputs do not have variable sizing like text. They cannot shrink down to > the size of the text, which makes positioning difficult. > * common browser extensions such as LastPass can be confused (see > screenshot[1] -- lastpass sees these labels for the text fields they are, > and attempts to help the user fill them in -- that's what those gray > asterisks are. Very confusing.) > > I'd like to pursue correcting this, if possible. > > Thanks, > Greg > > [1] http://i.imgur.com/AweOhJe.png > > Greg Sheremeta > Red Hat, Inc. > Sr. Software Engineer, RHEV > Cell: 919-807-1086 > gshereme at redhat.com > _______________________________________________ > Engine-devel mailing list > Engine-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > From gshereme at redhat.com Thu Mar 13 16:24:51 2014 From: gshereme at redhat.com (Greg Sheremeta) Date: Thu, 13 Mar 2014 12:24:51 -0400 (EDT) Subject: [Engine-devel] attn ui devs: why do we use inputs for labels? In-Reply-To: <1579791205.26836676.1394727291548.JavaMail.zimbra@redhat.com> References: <1740187465.9597169.1394722935614.JavaMail.zimbra@redhat.com> <1579791205.26836676.1394727291548.JavaMail.zimbra@redhat.com> Message-ID: <2025637929.9623264.1394727891708.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Einav Cohen" > To: "Greg Sheremeta" > Cc: "engine-devel" > Sent: Thursday, March 13, 2014 12:14:51 PM > Subject: Re: [Engine-devel] attn ui devs: why do we use inputs for labels? > > I could be wrong, but there is a chance that using "input type=text" > allows selecting/copying the text, rather than a plain label, which > doesn't allow that. If that's the reason, it must be a quirky browser thing. I can select and copy