Re: [ovirt-devel] Vdsm - 6 years (in 10 minutes)

2017-01-09 Thread Douglas Schilling Landgraf 



On 01/09/2017 10:40 AM, Yaniv Bronheim wrote:

craziness .. cool thing though



Indeed, cool!




On Mon, Jan 9, 2017 at 5:08 PM, Nir Soffer > wrote:

Hi all,

Please enjoy this visualization of vdsm development since 2011:
https://www.youtube.com/watch?v=Ui1ouZiENU0


If you want to create your own:

dnf install gourse ffmpeg
cd /path/to/gitrepo
gource -s 0.1 --date-format "%a, %d %b %Y" -1920x1080 -o - | ffmpeg -y
-r 30 -f image2pipe -vcodec ppm -i - -vcodec libx264 -preset ultrafast
-pix_fmt yuv420p -crf 1 -threads 4 -bf 0 vdsm-6-years.mp4

Nir
___
Devel mailing list
Devel@ovirt.org 
http://lists.ovirt.org/mailman/listinfo/devel





--
*Yaniv Bronhaim.*


___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel


___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] gerrit.ovirt.org projects

2016-06-08 Thread Douglas Schilling Landgraf 

Hi,

On 05/17/2016 07:49 AM, Shlomo Ben David wrote:

Hi,

I have a question about projects on gerrit.ovirt.org 
.
I'm working on cleaning up the gerrit.ovirt.org 
 and updating the replication process to 
github, I've noticed that the projects below weren't updated > ~6 months.


Do you know which of the below projects is still relevant for 
replication (sync to github)?


ovirt-register
This one is not relevant, we have used a different approach for host 
registration in 3.6.



test
chrooter
gluster-nagios-monitoring
ovirt-container-node
ovirt-container-engine
ovirt-engine-sdk-js
vdsm-arch-dependencies
ovirt-node-dbus-backend
samples-portals
jasperreports-server-rpm
ovirt-node-tests
ovirt-engine-sdk-tests
Node
ovirt-tools-common-python
mediawiki-example


Thanks in advanced,

Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
Phone: +972-54-8008858
IRC: sbendavi

OPEN SOURCE - 1 4 011 && 011 4 1


___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel


___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] VARIANT_ID usage - with our without oVirt version?

2016-01-14 Thread Douglas Schilling Landgraf 



On 01/14/2016 08:26 AM, Moti Asayag wrote:


On Wed, Jan 13, 2016 at 5:17 PM, Fabian Deutsch > wrote:


Hey,

we've now merged a patch [0] to use and populate the VARIANT and
VARIANT_ID fields on Node.

Currently the value is something like "ovirt-node-$BRANCH", i.e.
"ovirt-node-master" or "ovirt-node-3.6".

I'd like to question if we should include the oVirt version in the ID,
or if we should just use "ovirt-node" without the version.

From my POV the variant is not depending on a specific version, that
is why I'd like to discuss it.

My point of view is that variant_id doesn't depend of specific version, 
it only shows the
'flavor' of distro and may or may not include numbers as the link [1] 
showed.


One benefit to have the branding/ovirt release in variant id is that in 
the new oVirt Node
it uses Cockpit which reads /etc/os-release (ID + VARIANT_ID ) to show 
to the users in the login

page such data, i.e:

"CentOS oVirt Node 3.6"

Username:
Password:



+1
I agree the variant-id should not be a version specific. It should 
only describe the flavour of the host.
I don't see why the engine should be aware of the specific version of 
it, especially since we'd like to have a unified process for all host 
types and furthermore for the same host type of different versions.


I agree that Engine shouldn't care about a specific version at all but 
probably VDSM will be sending /etc/os-release to Engine for displaying 
data to the users.




The oVirt version can still be retieved like on any other host i.e.
using rpm or maybe some file(?).


 Resolving the supported version of the hypervisor should be done the 
same way as for any host by monitoring the capabilities as reported by 
VDSM.



- fabian

--
[0]

https://gerrit.ovirt.org/gitweb?p=ovirt-release.git;a=blob;f=ovirt-release-master/ovirt-release-master.spec.in;h=8690d39402221acac402a6f2f0c485571ad838fa;hb=HEAD#l140
[1] http://www.freedesktop.org/software/systemd/man/os-release.html




--
Regards,
Moti


___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] oVirt node 3.6 and CPU load indefinitely stuck on 100% while vdsmd indefinitely tries to restart

2015-06-01 Thread Douglas Schilling Landgraf 

On 06/01/2015 03:56 AM, Simone Tiraboschi wrote:



- Original Message -

From: Douglas Schilling Landgraf dougsl...@redhat.com
To: Simone Tiraboschi stira...@redhat.com, devel@ovirt.org
Cc: Fabian Deutsch fdeut...@redhat.com
Sent: Saturday, May 30, 2015 11:28:38 PM
Subject: Re: oVirt node 3.6 and CPU load indefinitely stuck on 100% while vdsmd 
indefinitely tries to restart

On 05/29/2015 06:44 AM, Simone Tiraboschi wrote:

Hi,
I tried to have hosted-engine deploying the engine appliance over oVirt
node. I think it will be quite a common scenario.
I tried with an oVirt node build from yesterday.

Unfortunately I'm not able to conclude the setup cause oVirt node got the
CPU load indefinitely stuck on 100% and so it's almost unresponsive.

The issue seams to be related to vdsmd daemon witch couldn't really start
and so it retries indefinitely using all the available CPU power (it also
runs with niceless -20...).

[root@node36 admin]# grep Unit vdsmd.service entered failed state.
/var/log/messages  | wc -l
368
It tried 368 times in a row in a few minutes.

With journalctl I can read:
May 29 10:06:45 node36 systemd[1]: Unit vdsmd.service entered failed state.
May 29 10:06:45 node36 systemd[1]: vdsmd.service holdoff time over,
scheduling restart.
May 29 10:06:45 node36 systemd[1]: Stopping Virtual Desktop Server
Manager...
May 29 10:06:45 node36 systemd[1]: Starting Virtual Desktop Server
Manager...
May 29 10:06:45 node36 vdsmd_init_common.sh[13697]: vdsm: Running mkdirs
May 29 10:06:45 node36 vdsmd_init_common.sh[13697]: vdsm: Running
configure_coredump
May 29 10:06:45 node36 vdsmd_init_common.sh[13697]: vdsm: Running
configure_vdsm_logs
May 29 10:06:45 node36 vdsmd_init_common.sh[13697]: vdsm: Running
wait_for_network
May 29 10:06:45 node36 vdsmd_init_common.sh[13697]: vdsm: Running
run_init_hooks
May 29 10:06:46 node36 vdsmd_init_common.sh[13697]: vdsm: Running
upgraded_version_check
May 29 10:06:46 node36 vdsmd_init_common.sh[13697]: vdsm: Running
check_is_configured
May 29 10:06:46 node36 vdsmd_init_common.sh[13697]: vdsm: Running
validate_configuration
May 29 10:06:47 node36 vdsmd_init_common.sh[13697]: vdsm: Running
prepare_transient_repository
May 29 10:06:49 node36 vdsmd_init_common.sh[13697]: vdsm: Running
syslog_available
May 29 10:06:49 node36 vdsmd_init_common.sh[13697]: vdsm: Running nwfilter
May 29 10:06:50 node36 vdsmd_init_common.sh[13697]: vdsm: Running dummybr
May 29 10:06:51 node36 vdsmd_init_common.sh[13697]: vdsm: Running
load_needed_modules
May 29 10:06:51 node36 vdsmd_init_common.sh[13697]: vdsm: Running
tune_system
May 29 10:06:51 node36 vdsmd_init_common.sh[13697]: vdsm: Running
test_space
May 29 10:06:51 node36 vdsmd_init_common.sh[13697]: vdsm: Running test_lo
May 29 10:06:51 node36 systemd[1]: Started Virtual Desktop Server Manager.
May 29 10:06:51 node36 systemd[1]: vdsmd.service: main process exited,
code=exited, status=1/FAILURE
May 29 10:06:51 node36 vdsmd_init_common.sh[13821]: vdsm: Running
run_final_hooks
May 29 10:06:52 node36 systemd[1]: Unit vdsmd.service entered failed state.
May 29 10:06:52 node36 systemd[1]: vdsmd.service holdoff time over,
scheduling restart.
May 29 10:06:52 node36 systemd[1]: Stopping Virtual Desktop Server
Manager...
May 29 10:06:52 node36 systemd[1]: Starting Virtual Desktop Server
Manager...
repeated a lot of times

/var/log/vdsm/vdsm.log is empty.

while
[root@node36 admin]# /usr/share/vdsm/daemonAdapter -0 /dev/null -1
/dev/null -2 /dev/null /usr/share/vdsm/vdsm; echo $?
1



Thanks for the report Simone. From my tests you are facing:

non-root user cannot `from ovirtnode import ovirtfunctions`: permission
denied: '/var/log/ovirt-node.log' and '/var/log/ovirt.log
https://bugzilla.redhat.com/show_bug.cgi?id=1224400

We should handle this bug very soon. The workaround is chmod o+rw in
/var/log/ovirt.log /var/log/ovirt-node.log


OK. I tried
[root@node36 admin]# chmod o+rw /var/log/ovirt.log /var/log/ovirt-node.log

but now I'm getting:
[root@node36 admin]# systemctl status -l vdsmd
vdsmd.service - Virtual Desktop Server Manager
Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled)
Active: active (running) since Mon 2015-06-01 07:53:09 UTC; 17s ago
   Process: 4040 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh 
--post-stop (code=exited, status=0/SUCCESS)
   Process: 4049 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh 
--pre-start (code=exited, status=0/SUCCESS)
  Main PID: 4164 (vdsm)
CGroup: /system.slice/vdsmd.service
└─4164 /usr/bin/python /usr/share/vdsm/vdsm

Jun 01 07:53:07 node36 vdsmd_init_common.sh[4049]: vdsm: Running nwfilter
Jun 01 07:53:08 node36 vdsmd_init_common.sh[4049]: vdsm: Running dummybr
Jun 01 07:53:09 node36 vdsmd_init_common.sh[4049]: vdsm: Running 
load_needed_modules
Jun 01 07:53:09 node36 vdsmd_init_common.sh[4049]: vdsm: Running tune_system
Jun 01 07:53:09 node36 vdsmd_init_common.sh[4049]: vdsm: Running test_space
Jun 01 07:53:09 node36 vdsmd_init_common.sh[4049

Re: [ovirt-devel] oVirt node 3.6 and CPU load indefinitely stuck on 100% while vdsmd indefinitely tries to restart

2015-05-30 Thread Douglas Schilling Landgraf 

On 05/29/2015 06:44 AM, Simone Tiraboschi wrote:

Hi,
I tried to have hosted-engine deploying the engine appliance over oVirt node. I 
think it will be quite a common scenario.
I tried with an oVirt node build from yesterday.

Unfortunately I'm not able to conclude the setup cause oVirt node got the CPU 
load indefinitely stuck on 100% and so it's almost unresponsive.

The issue seams to be related to vdsmd daemon witch couldn't really start and 
so it retries indefinitely using all the available CPU power (it also runs with 
niceless -20...).

[root@node36 admin]# grep Unit vdsmd.service entered failed state. 
/var/log/messages  | wc -l
368
It tried 368 times in a row in a few minutes.

With journalctl I can read:
May 29 10:06:45 node36 systemd[1]: Unit vdsmd.service entered failed state.
May 29 10:06:45 node36 systemd[1]: vdsmd.service holdoff time over, scheduling 
restart.
May 29 10:06:45 node36 systemd[1]: Stopping Virtual Desktop Server Manager...
May 29 10:06:45 node36 systemd[1]: Starting Virtual Desktop Server Manager...
May 29 10:06:45 node36 vdsmd_init_common.sh[13697]: vdsm: Running mkdirs
May 29 10:06:45 node36 vdsmd_init_common.sh[13697]: vdsm: Running 
configure_coredump
May 29 10:06:45 node36 vdsmd_init_common.sh[13697]: vdsm: Running 
configure_vdsm_logs
May 29 10:06:45 node36 vdsmd_init_common.sh[13697]: vdsm: Running 
wait_for_network
May 29 10:06:45 node36 vdsmd_init_common.sh[13697]: vdsm: Running run_init_hooks
May 29 10:06:46 node36 vdsmd_init_common.sh[13697]: vdsm: Running 
upgraded_version_check
May 29 10:06:46 node36 vdsmd_init_common.sh[13697]: vdsm: Running 
check_is_configured
May 29 10:06:46 node36 vdsmd_init_common.sh[13697]: vdsm: Running 
validate_configuration
May 29 10:06:47 node36 vdsmd_init_common.sh[13697]: vdsm: Running 
prepare_transient_repository
May 29 10:06:49 node36 vdsmd_init_common.sh[13697]: vdsm: Running 
syslog_available
May 29 10:06:49 node36 vdsmd_init_common.sh[13697]: vdsm: Running nwfilter
May 29 10:06:50 node36 vdsmd_init_common.sh[13697]: vdsm: Running dummybr
May 29 10:06:51 node36 vdsmd_init_common.sh[13697]: vdsm: Running 
load_needed_modules
May 29 10:06:51 node36 vdsmd_init_common.sh[13697]: vdsm: Running tune_system
May 29 10:06:51 node36 vdsmd_init_common.sh[13697]: vdsm: Running test_space
May 29 10:06:51 node36 vdsmd_init_common.sh[13697]: vdsm: Running test_lo
May 29 10:06:51 node36 systemd[1]: Started Virtual Desktop Server Manager.
May 29 10:06:51 node36 systemd[1]: vdsmd.service: main process exited, 
code=exited, status=1/FAILURE
May 29 10:06:51 node36 vdsmd_init_common.sh[13821]: vdsm: Running 
run_final_hooks
May 29 10:06:52 node36 systemd[1]: Unit vdsmd.service entered failed state.
May 29 10:06:52 node36 systemd[1]: vdsmd.service holdoff time over, scheduling 
restart.
May 29 10:06:52 node36 systemd[1]: Stopping Virtual Desktop Server Manager...
May 29 10:06:52 node36 systemd[1]: Starting Virtual Desktop Server Manager...
repeated a lot of times

/var/log/vdsm/vdsm.log is empty.

while
[root@node36 admin]# /usr/share/vdsm/daemonAdapter -0 /dev/null -1 /dev/null -2 
/dev/null /usr/share/vdsm/vdsm; echo $?
1



Thanks for the report Simone. From my tests you are facing:

non-root user cannot `from ovirtnode import ovirtfunctions`: permission 
denied: '/var/log/ovirt-node.log' and '/var/log/ovirt.log

https://bugzilla.redhat.com/show_bug.cgi?id=1224400

We should handle this bug very soon. The workaround is chmod o+rw in 
/var/log/ovirt.log /var/log/ovirt-node.log


--
Cheers
Douglas
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Possible documentation fixes - advice needed

2015-05-20 Thread Douglas Schilling Landgraf 

Hello Gina,

On 05/20/2015 03:33 PM, Gina Likins wrote:

Hi all-

I am new to this, so please bear with me. I was researching oVirt, looking for 
information on developer guidelines, and I found some, but they weren't all 
connected or linked iin from the same page.

I think I can fix that (and I've been given wiki permissions), but I want to 
make sure I'm not doing something really stupid before I do.

What I think should happen is that this page:

http://www.ovirt.org/Backend_Coding_Standards

should have links to the following pages on it:
* http://www.ovirt.org/Vdsm_Coding_Guidelines
* http://www.ovirt.org/Infra_Bash_style_guide
* http://www.ovirt.org/Community_guidelines#Code_submission_guidelines
* http://www.ovirt.org/Building_oVirt_Engine/IDE -- see section about engine and 
Checkstyle: Make sure that you import the engine code formatter into eclipse before 
starting development. The engine maven build uses checkstyle to check coding standards. One 
of the standards checked is that the code should not contain tabs or trailing whitespaces. 
Since eclipse inserts tabs by default for code formatting, you can end up with a lot of 
compilation errors in command line maven build if you don't follow this (and the next) 
step.

And this page: http://www.ovirt.org/DevProcess  should have a link to
http://www.ovirt.org/Backend_Coding_Standards on it

If I don't hear from anyone, I'll make these changes on Friday.  If I have it 
wrong, tell me so and I won't make the changes.




From my point of view, looks good, the wiki is there to document the 
project and to be updated as soon someone finds the need of improvement. 
Specially, if this change will help others. I would say: fell free to 
improve adding links to related topic, if someone believes it could be 
in better shape, they can always improve based on your last 
improvements. Without mention that wiki have the history recorded to 
easily recover.


Have fun!

--
Cheers
Douglas
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Greg Sheremeta is now an ovirt-engine UI maintainer

2015-03-26 Thread Douglas Schilling Landgraf 

On 03/26/2015 09:20 AM, Vojtech Szocs wrote:

Congrats Greg! :)


Indeed, Congrats Greg! Well deserved. :-)


Vojtech


- Original Message -

From: Einav Cohen eco...@redhat.com
To: Lior Vernia lver...@redhat.com, Alona Kaplan alkap...@redhat.com, Daniel 
Erez de...@redhat.com,
Gilad Chaplik gchap...@redhat.com, Tomas Jelinek tjeli...@redhat.com, Vojtech 
Szocs vsz...@redhat.com,
Alexander Wels aw...@redhat.com, Kanagaraj kmayi...@redhat.com, Tal Nisan 
tni...@redhat.com, Greg
Sheremeta gsher...@redhat.com
Cc: devel@ovirt.org
Sent: Wednesday, March 25, 2015 5:58:40 PM
Subject: Greg Sheremeta is now an ovirt-engine UI maintainer

Thanks, everyone, for your support.
Greg is now an oVirt-engine UI maintainer.
Greg - congratulations!


Regards,
Einav

- Original Message -

From: Einav Cohen eco...@redhat.com
To: Lior Vernia lver...@redhat.com, Alona Kaplan
alkap...@redhat.com, Daniel Erez de...@redhat.com,
Gilad Chaplik gchap...@redhat.com, Tomas Jelinek
tjeli...@redhat.com, Vojtech Szocs vsz...@redhat.com,
Alexander Wels aw...@redhat.com, Kanagaraj kmayi...@redhat.com,
Tal Nisan tni...@redhat.com
Cc: in...@ovirt.org, devel@ovirt.org
Sent: Wednesday, March 25, 2015 8:59:17 AM
Subject: [ovirt-devel] proposing Greg Sheremeta as an ovirt-engine UI
maintainer

Hello UI Maintainers,

I would like to propose Greg Sheremeta as an ovirt-engine
UI maintainer.

Greg started being actively involved in ovirt on July 2013,
contributing over 150 patches (to 'master' alone), including
improvements to the branding mechanism (e.g. support cascading
resources), grid-column width persistence, phase 1 of the
PatternFly styling adoption, dialog-id (tag) based mapping
infrastructure, multiple automated-UI-tests (Selenium) related
enhancements and the recent overhaul of the tool-tips throughout
the code.

Your response would be highly appreciated.

Many thanks in advance.


Regards,
Einav
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel




___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel




--
Cheers
Douglas
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Why there is no Ovirt Engine register item on Ovirt Node

2014-08-13 Thread Douglas Schilling Landgraf 

On 08/13/2014 05:12 AM, yangtao wrote:

Hi  Fabian,

How to build build plugin and use the kickstart provided in that plugin?
What's more, I use 3.1.0 master version to build.   The ovirt node
master version doesn't include the VSDM plugin, right?


Hi Tao,

In the below link there are steps how to build ovirt-node-plugin-vdsm 
and vdsm. Additionally, there is an example how to add these packages 
into the iso with edit-node tool:


http://dougsland.livejournal.com/123418.html

More info about VDSM, please consult:
http://www.ovirt.org/Vdsm_Developers



Best Regards!
Tao





At 2014-08-13 04:53:55, Fabian Deutsch fdeut...@redhat.com wrote:

- Original Message -

Hi Fabian and Ryan,

Even though the ovirt-node that is built  by myself on CentOS has boot
successfully. However,
When I test my ovirt-node, and  find one problem. please take a look the
follow two ovirt-node running pictures.

1, Offical ovirt-node running screenshot




2， My ovirt-node running screenshot


There is no Ovirt Engine register function. Compare the size of this two
ovirt-node iso, offical node is 250M, but my ovirt-node is 200M.
I think Ovirt Engine register function isn't built into ovirt node.  Who
know how to resolve this problem? Thank you very much!

Looking forward to anyone's feedback. Thanks!


Hey Tao,

the Engine part of Node is part of the ovirt-node-plugin-vdsm.

To build the Node for Engine, you need to build that plugin too and use the 
kickstart provided in that plugin.

- fbaian



Best Regards!
Tao










At 2014-08-13 03:04:41, Fabian Deutsch fdeut...@redhat.com wrote:
- Original Message -
 Hi fdeutsch and Ryan,

 I test the ovirt-node iso that is built by myself. It can boot
 successfully
 from hard disk on physical PC.

 Thanks very much for both's help recently!  Have you a nice day!

 Best Regards!
 Tao

Hey Tao,

that is great news!

Might I ask if you do something special with Node?

Greetings
fabian




___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel






___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel




--
Cheers
Douglas
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] vdsm-4.14.11-2 New build for ovirt-3.4

2014-07-24 Thread Douglas Schilling Landgraf 

On 07/24/2014 04:39 AM, ybronhei wrote:

On 07/23/2014 06:21 PM, Douglas Schilling Landgraf wrote:

On 07/23/2014 05:25 AM, ybronhei wrote:

On 07/23/2014 12:21 PM, Dan Kenigsberg wrote:

On Wed, Jul 23, 2014 at 12:50:07AM +0300, ybronhei wrote:

Hey all,

New build of vdsm for ovirt-3.4 is available:

f20 - http://koji.fedoraproject.org/koji/taskinfo?taskID=7178863
f19 - http://koji.fedoraproject.org/koji/taskinfo?taskID=7182758
el6 - http://koji.fedoraproject.org/koji/taskinfo?taskID=7182831
el7 - http://koji.fedoraproject.org/koji/taskinfo?taskID=7182808


Thank, Yaniv. Do you have any idea why only the f20 build shows up on
https://admin.fedoraproject.org/updates/search/vdsm ? I wanted to give
karma to the el6 build. (I bet that others wants to see it out asap)


yes, now f19 also should be there

and for el6 , we don't have such branch in the fedpkg repo, I only made
a scratch-build
Douglas - is there a way to publish also el6 and epel7 update when we do
only scrach-build?


No, if you want a fedora 'build/update' you must have the branch.
To request new branches for VDSM, please go to:
https://bugzilla.redhat.com/show_bug.cgi?id=745510

Example:
https://bugzilla.redhat.com/show_bug.cgi?id=745510#c23 raising the flag
fedora-cvs.

More info: http://fedoraproject.org/wiki/Package_SCM_admin_requests


can you take care of that? looks like you need to be fedora packager for
that, i can't set the fedora-cvs flag

only need to post:

Package Change Request
==
Package Name: vdsm
New Branches: el6 epel7
Owners: fsimonce danken smizrahi

as far as i understand the process, and reopen the bug

Thanks,

Done, request opened.

--
Cheers
Douglas
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] vdsm-4.14.11-2 New build for ovirt-3.4

2014-07-23 Thread Douglas Schilling Landgraf 

On 07/23/2014 05:25 AM, ybronhei wrote:

On 07/23/2014 12:21 PM, Dan Kenigsberg wrote:

On Wed, Jul 23, 2014 at 12:50:07AM +0300, ybronhei wrote:

Hey all,

New build of vdsm for ovirt-3.4 is available:

f20 - http://koji.fedoraproject.org/koji/taskinfo?taskID=7178863
f19 - http://koji.fedoraproject.org/koji/taskinfo?taskID=7182758
el6 - http://koji.fedoraproject.org/koji/taskinfo?taskID=7182831
el7 - http://koji.fedoraproject.org/koji/taskinfo?taskID=7182808


Thank, Yaniv. Do you have any idea why only the f20 build shows up on
https://admin.fedoraproject.org/updates/search/vdsm ? I wanted to give
karma to the el6 build. (I bet that others wants to see it out asap)


yes, now f19 also should be there

and for el6 , we don't have such branch in the fedpkg repo, I only made
a scratch-build
Douglas - is there a way to publish also el6 and epel7 update when we do
only scrach-build?


No, if you want a fedora 'build/update' you must have the branch.
To request new branches for VDSM, please go to:
https://bugzilla.redhat.com/show_bug.cgi?id=745510

Example:
https://bugzilla.redhat.com/show_bug.cgi?id=745510#c23 raising the flag 
fedora-cvs.


More info: http://fedoraproject.org/wiki/Package_SCM_admin_requests

--
Cheers
Douglas
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] python-ioprocess for el7?

2014-07-12 Thread Douglas Schilling Landgraf 

On 07/11/2014 07:46 AM, Dan Kenigsberg wrote:

On Thu, Jul 10, 2014 at 05:01:21PM -0400, Adam Litke wrote:

Hi,

I am looking for python-ioprocess RPMs (new enough for latest vdsm
requirements).  Can anyone point me in the right direction?  Thanks!


Looking at

https://admin.fedoraproject.org/updates/search/python-pthreading
https://admin.fedoraproject.org/updates/search/python-cpopen
https://admin.fedoraproject.org/updates/search/ioprocess

I can confirm that we miss quite a bit of our dependencies for el7.

Douglas, Yaniv: can you have them built? I see that
http://dl.fedoraproject.org/pub/epel/beta/7/x86_64/ already exists, and
I hope to see out packages there.



Sure, please refresh, python-cpopen and python-pthreading should be 
there now. However, ioprocess requires Saggi interaction.



--
Cheers
Douglas
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] oVirt 3.5 test day 1 results

2014-07-01 Thread Douglas Schilling Landgraf 

Hi,

This time I have tested the below RFE:

[RFE] Change the Slot field to Service Profile when cisco_ucs is 
selected as the fencing type.

https://bugzilla.redhat.com/show_bug.cgi?id=1090803

Test Data
===
Running oVirt 3.5 with Power Management enabled in hosts when selecting 
Type cisco_ucs the Slot field get replaced by Service Profile as RFE 
requested. The same test under 3.4 the field is not replaced.

I would say this RFE is 100% accomplished.



--
Cheers
Douglas
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Fwd: Re: Mass bug: packages should not auto-enable systemd units

2014-05-06 Thread Douglas Schilling Landgraf 

On 04/30/2014 05:32 PM, Dan Kenigsberg wrote:

On Wed, Apr 30, 2014 at 07:57:32PM +0200, Vinzenz Feenstra wrote:


Due to some confusion around how alternatives worked, I screwed up the
list of packages here.  I've updated it below.  I'll give it a few
more days before filing the actual bugs.

On Wed, Apr 23, 2014 at 4:59 PM, Andrew Lutomirski l...@mit.edu wrote:

Hi everyone-

This is a notice in accordance with the mass bug filing procedure.

A number of packages install systemd units and enable them
automatically.  They should not.  Please update these packages to use the
macroized scriptlet
(https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd).

If your package has an exception from FESCo permitting it to enable
itself, please make sure that the service in question is listed in the
appropriate preset file.

There is a general exception described here:

https://fedoraproject.org/wiki/Starting_services_by_default

If your package falls under the general exception, then it is possible
that no change is required.  Nevertheless, if you are relying on the
exception, please make sure that your rpm scripts are sensible.  The
exception is:

In addition, any service which does not remain persistent on the
system (aka, it runs once then goes away), does not listen to
incoming connections during initialization, and does not require
configuration to be functional may be enabled by default (but is not
required to do so). An example of runs once then goes away service
is iptables.

Given that this issue can affect Fedora 20 users who install your
package as a dependency, these bugs should be fixed in Fedora 20 and
Rawhide.

The tracker bug is here:

https://bugzilla.redhat.com/show_bug.cgi?id=1090684

I created it early because three of the bugs are pre-existing.  Next
week, I'll file bugs against the packages below.  If you fix your
package in the mean time, please let me know.

After three weeks, provenpackagers may step in and fix these issues.



Vinzenz, I suppose that your main point is this part of the list


vdsm


Douglas/Yaniv - can infra take care of this?


Sure, I noticed we got a bug (1094936) report from it as well

--
Cheers
Douglas
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [Devel] Vdsm functional tests

2014-04-06 Thread Douglas Schilling Landgraf 

On 04/03/2014 12:24 PM, Dan Kenigsberg wrote:

On Thu, Apr 03, 2014 at 12:31:44PM -0400, Douglas Schilling Landgraf wrote:

On 04/03/2014 11:08 AM, Dan Kenigsberg wrote:

Functional tests are intended to verify that a running Vdsm instance
does what it should, when treated as a black box, over its public API.

They should be comprehensive and representative of a typical field usage
of Vdsm. It is a sin to break such a test - but we must be able to know
when such a sin is committed.

We currently have the following functional tests modules:

- sosPluginTests.py
   supervdsmFuncTests.py


Sure, count with me.


Thanks! When do you think you could write a job similar to
http://jenkins.ovirt.org/view/By%20Project/view/vdsm/job/vdsm_network_functional_tests/configure
running whenever there's a change in the modules relevant to
sosPluginTests and supervdsmFuncTests?



Hi,

Instead of to split by domain like (network, infra, storage), why not 
have a single functional test job? If something fail, it should trigger 
the volunteers.


For while, I started a creation of infra based on the above one.
http://jenkins.ovirt.org/job/vdsm_infra_functional_tests

--
Cheers
Douglas
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [Engine-devel] Problem creating hosts.

2014-02-04 Thread Douglas Schilling Landgraf 

Oi Sérgio,

On 02/04/2014 07:16 PM, Sérgio Ribeiro wrote:

I’m newbie in ovirt and after installing ovirt, with comand engine-setup,
i go to localhost/ovirt-engine and i log on the webpage. On data center
only appears a default data-center with no hosts. i trie to create a
host and appears na error because the name and address of the host. its
a local machine for tests with no domain.
the config that i use is name:host1.localdomain, address: 192.168.2.1,
and i created this config on etc/hosts file.

can you help me?



Did you add these address/host into /etc/hosts on ovirt-engine and 
ovirt-node? You could use the ip address directly too on admin portal.


Additionally, do you have any error on event log window? (below on the 
Admin Portal)



--
Cheers
Douglas
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel

Re: [Engine-devel] oVirt 3.4.0 beta is now available

2014-01-22 Thread Douglas Schilling Landgraf 

Hi Eli,

On 01/22/2014 01:10 PM, Eli Mesika wrote:



- Original Message -

From: Sandro Bonazzola sbona...@redhat.com
To: Martin Perina mper...@redhat.com
Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org
Sent: Wednesday, January 22, 2014 5:01:55 PM
Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available

Il 22/01/2014 15:49, Martin Perina ha scritto:

Hi,

I tried to install on F19, but openstack* packages = 3.0.2 are missing:


thanks, updated release page, it needs updates-testing


I had enabled ovirt-updates-testing and still got this :


Here it worked, without looking your 'yum repolist' output I do guess 
you need to enable the repo from:

/etc/yum.repos.d/fedora-updates-testing.repo

# yum install ovirt-engine
snip
Installing:
 ovirt-enginenoarch 
  3.4.0-0.5.beta1.fc19 
ovirt-3.4.0-prerelease  1.3

/snip

snip
Installing for dependencies:
 openstack-java-glance-clientnoarch 
  3.0.2-1.fc19updates-testing 
21 k
 openstack-java-glance-model noarch 
  3.0.2-1.fc19updates-testing 
18 k
 openstack-java-keystone-client  noarch 
  3.0.2-1.fc19updates-testing 
33 k
 openstack-java-keystone-model   noarch 
  3.0.2-1.fc19updates-testing 
30 k
 openstack-java-quantum-client   noarch 
  3.0.2-1.fc19updates-testing 
20 k
 openstack-java-quantum-modelnoarch 
  3.0.2-1.fc19updates-testing 
24 k

/snip



-- Finished Dependency Resolution
Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch 
(ovirt-3.4.0-prerelease)
Requires: openstack-java-quantum-model = 3.0.2
Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch 
(updates)
openstack-java-quantum-model = 3.0.1-1.fc19
Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch 
(ovirt-3.4.0-prerelease)
Requires: openstack-java-glance-client = 3.0.2
Available: openstack-java-glance-client-3.0.1-1.fc19.noarch 
(updates)
openstack-java-glance-client = 3.0.1-1.fc19
Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch 
(ovirt-3.4.0-prerelease)
Requires: openstack-java-glance-model = 3.0.2
Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates)
openstack-java-glance-model = 3.0.1-1.fc19
Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch 
(ovirt-3.4.0-prerelease)
Requires: openstack-java-client = 3.0.2
Available: openstack-java-client-3.0.1-1.fc19.noarch (updates)
openstack-java-client = 3.0.1-1.fc19
Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch 
(ovirt-3.4.0-prerelease)
Requires: openstack-java-keystone-model = 3.0.2
Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch 
(updates)
openstack-java-keystone-model = 3.0.1-1.fc19
Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch 
(ovirt-3.4.0-prerelease)
Requires: openstack-java-resteasy-connector = 3.0.2
Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch 
(updates)
openstack-java-resteasy-connector = 3.0.1-1.fc19
Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch 
(ovirt-3.4.0-prerelease)
Requires: openstack-java-quantum-client = 3.0.2
Available: openstack-java-quantum-client-3.0.1-1.fc19.noarch 
(updates)
openstack-java-quantum-client = 3.0.1-1.fc19
Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch 
(ovirt-3.4.0-prerelease)
Requires: openstack-java-keystone-client = 3.0.2
Available: openstack-java-keystone-client-3.0.1-1.fc19.noarch 
(updates)
openstack-java-keystone-client = 3.0.1-1.fc19
  You could try using --skip-broken to work around the problem
  You could try running: rpm -Va --nofiles --nodigest









Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch
(ovirt-3.4.0-prerelease)
Requires: openstack-java-quantum-model = 3.0.2
Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch
(updates)
openstack-java-quantum-model = 3.0.1-1.fc19
Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch
(ovirt-3.4.0-prerelease)
Requires: openstack-java-glance-client = 3.0.2
Available: openstack-java-glance-client-3.0.1-1.fc19.noarch
(updates)
openstack-java-glance-client = 3.0.1-1.fc19
Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch

Re: [Engine-devel] [Users] oVirt 3.4.0 beta is now available

2014-01-22 Thread Douglas Schilling Landgraf 

On 01/22/2014 03:00 PM, Eli Mesika wrote:



- Original Message -

From: Eli Mesika emes...@redhat.com
To: dougsl...@redhat.com
Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org
Sent: Wednesday, January 22, 2014 9:48:54 PM
Subject: Re: [Users] [Engine-devel] oVirt 3.4.0 beta is now available



- Original Message -

From: Douglas Schilling Landgraf dougsl...@redhat.com
To: Eli Mesika emes...@redhat.com, Sandro Bonazzola
sbona...@redhat.com
Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org
Sent: Wednesday, January 22, 2014 9:31:59 PM
Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available

Hi Eli,

On 01/22/2014 01:10 PM, Eli Mesika wrote:



- Original Message -

From: Sandro Bonazzola sbona...@redhat.com
To: Martin Perina mper...@redhat.com
Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org
Sent: Wednesday, January 22, 2014 5:01:55 PM
Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available

Il 22/01/2014 15:49, Martin Perina ha scritto:

Hi,

I tried to install on F19, but openstack* packages = 3.0.2 are
missing:


thanks, updated release page, it needs updates-testing


I had enabled ovirt-updates-testing and still got this :


Here it worked, without looking your 'yum repolist' output I do guess
you need to enable the repo from:
/etc/yum.repos.d/fedora-updates-testing.repo



Thanks, I enabled ovirt-updates-testing in ovirt repo . :-(


engine-setup fails with the following error

Failed to execute stage 'Misc configuration': Command '/bin/systemctl' failed 
to execute

any ideas ?


Hi Eli,

Would be nice too see your engine-setup log file to determine which 
error happened. Should be available here:  /var/log/ovirt-engine/setup/


Anyway, I could reproduce a similar output during a setup (below the 
log) and in my case was postgresql with error: FATAL:  could not create 
shared memory segment: Invalid argument


Resolved with wiki:
http://www.ovirt.org/Troubleshooting#Installation

In session:
I am having trouble connecting to the database. In the system log, I 
get the following message from Postgres


@Sandro, should or maybe installer detect this kind of situation?

=

2014-01-22 17:37:52 DEBUG otopi.plugins.otopi.services.systemd 
plugin.execute:446 execute-output: ('/bin/systemctl', 'start', 
'postgresql.service') stderr:
Job for postgresql.service failed. See 'systemctl status 
postgresql.service' and 'journalctl -xn' for details.


2014-01-22 17:37:52 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 
/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/provisioning/postgres.py, 
line 182, in _misc

self._provisioning.provision()
  File /usr/share/ovirt-engine/setup/ovirt_engine_setup/postgres.py, 
line 552, in provision

self._restart()
  File /usr/share/ovirt-engine/setup/ovirt_engine_setup/postgres.py, 
line 407, in _restart

state=state,
  File /usr/share/otopi/plugins/otopi/services/systemd.py, line 138, 
in state

'start' if state else 'stop'
  File /usr/share/otopi/plugins/otopi/services/systemd.py, line 77, 
in _executeServiceCommand

raiseOnError=raiseOnError
  File /usr/lib/python2.7/site-packages/otopi/plugin.py, line 451, in 
execute

command=args[0],
RuntimeError: Command '/bin/systemctl' failed to execute
2014-01-22 17:37:52 ERROR otopi.context context._executeMethod:161 
Failed to execute stage 'Misc configuration': Command '/bin/systemctl' 
failed to execute
2014-01-22 17:37:52 DEBUG otopi.transaction transaction.abort:131 
aborting 'Yum Transaction'
2014-01-22 17:37:52 INFO otopi.plugins.otopi.packagers.yumpackager 
yumpackager.info:92 Yum Performing yum transaction rollback

Loaded plugins: versionlock


--
Cheers
Douglas
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel

Re: [Engine-devel] oVirt 3.4.0 alpha repository closure failure

2014-01-10 Thread Douglas Schilling Landgraf 

On 01/10/2014 05:01 AM, Dan Kenigsberg wrote:

On Fri, Jan 10, 2014 at 08:48:52AM +0100, Sandro Bonazzola wrote:

Hi,
oVirt 3.4.0 alpha repository has been composed but alpha has not been announced 
due to repository closure failures:

on CentOS 6.5:

# repoclosure -r ovirt-3.4.0-alpha -l ovirt-3.3.2 -l base -l epel -l 
glusterfs-epel -l updates -l extra -l glusterfs-noarch-epel -l ovirt-stable -n
Reading in repository metadata - please wait
Checking Dependencies
Repos looked at: 8
base
epel
glusterfs-epel
glusterfs-noarch-epel
ovirt-3.3.2
ovirt-3.4.0-alpha
ovirt-stable
updates
Num Packages in Repos: 16581
package: mom-0.3.2-20140101.git2691f25.el6.noarch from ovirt-3.4.0-alpha
   unresolved deps:
  procps-ng


Adam, this seems like a real bug in http://gerrit.ovirt.org/#/c/22087/ :
el6 still carries the older procps (which is, btw, provided by
procps-ng).



package: vdsm-hook-vhostmd-4.14.0-1.git6fdd55f.el6.noarch from ovirt-3.4.0-alpha
   unresolved deps:
  vhostmd


Douglas, could you add a with_vhostmd option to the spec, and have it
default to 0 on el*, and to 1 on fedoras?


Done
http://gerrit.ovirt.org/#/c/23126/

--
Cheers
Douglas
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel

[Engine-devel] UseSecureConnectionWithServers

2013-10-03 Thread Douglas Schilling Landgraf 

Hi,

This email is just a heads up about UseSecureConnectionWithServers 
option in database that got renamed [1] to EncryptHostCommunication to 
be more descriptive.


Additionally, the EncryptHostCommunication was added to engine-config 
tool [2].


Fore more info:
[1] http://gerrit.ovirt.org/#/c/19305/
[2] http://gerrit.ovirt.org/#/c/19202/

Thanks!

--
Cheers
Douglas
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel

Re: [Engine-devel] [Users] [Feedback required][host-deploy] Fedora-19 misses tar at minimal setup

2013-07-30 Thread Douglas Schilling Landgraf 

On 07/30/2013 09:25 AM, Michal Skrivanek wrote:


On Jul 30, 2013, at 15:12 , Alon Bar-Lev alo...@redhat.com wrote:


Hello All,

Starting the discussion again...

I would like to receive feedback regarding how we should cope with a state 
presented to use by Fedora.

Fedora-19 minimal setup does not install tar utility which is required to deploy 
files during the host-deploy process (Hosts-Add Host).

I guess because of 2.8M in size (including translations) -- a standard commonly 
used utility was removed.


How about filing bug on that? This is such a basic utility I can't imagine 
anyone removing it.


+1 I do agree with Michael. I have opened a thread in fedora devel 
mailing list anyway.








There are three alternatives :

1. Instruct users who are using minimal installations to manually install tar 
utility just like they configure repository, dns, etc..

Benefit: simplicity.
Benefit: use standard tools.
Benefit: lower payload to transmit.
Drawback: require tar at destination machine.

2. Do not use tar but self extracting python script, a patch is ready[1].

Benefit: ability to deploy environment in which tar is missing.
Drawback: non standard tool at destination machine.
Drawback: complexity within our code.

3. Do not use tar but cpio, a patch is ready[2].

Benefit: simplicity.
Benefit: use standard tools.
Benefit: lower payload to transmit.
Benefit: ability to use Fedora-19 minimal.
Drawback: cpio is even less common than tar, even if it exists in Fedora-19 it 
can be removed without anyone notice.
Drawback: most other distributions will not have cpio in their minimal 
installation.

[[[
There was 4rd alternative, using python tar module to deploy tar.
However, there is a bug in that module when processing last block if empty.
This is edge condition but happened to at least one of the users and I could
reproduce it.
]]]

What option do you prefer?

Regards,
Alon Bar-Lev

[1] http://gerrit.ovirt.org/#/c/17295/
[2] http://gerrit.ovirt.org/#/c/17396/
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel


___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel




--
Cheers
Douglas
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel

Re: [Engine-devel] fail to add host from portal

2013-07-24 Thread Douglas Schilling Landgraf 

Hello,

On 07/24/2013 11:05 PM, Chen, Wei D wrote:

It fails when add a host from portal, and error info as follows, anyone can 
give us some suggestion?

2013-07-25 22:55:39,539 INFO  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(VdsDeploy) Correlation ID:
296737fb, Call Stack: null, Custom Event ID: -1, Message: Installing Host 
onode. Logs at host located at:
'/tmp/ovirt-host-deploy-20130725105531.log'.
2013-07-25 22:55:39,563 ERROR [org.ovirt.engine.core.bll.VdsDeploy] (VdsDeploy) 
Error during deploy dialog:
java.lang.NullPointerException
 at 
org.ovirt.otopi.dialog.MachineDialogParser.cliEnvironmentGet(MachineDialogParser.java:236)
 [otopi.jar:]
 at org.ovirt.engine.core.bll.VdsDeploy$14.call(VdsDeploy.java:347) 
[bll.jar:]
 at 
org.ovirt.engine.core.bll.VdsDeploy._nextCustomizationEntry(VdsDeploy.java:579) 
[bll.jar:]
 at org.ovirt.engine.core.bll.VdsDeploy._threadMain(VdsDeploy.java:791) 
[bll.jar:]
 at org.ovirt.engine.core.bll.VdsDeploy.access$1800(VdsDeploy.java:76) 
[bll.jar:]
 at org.ovirt.engine.core.bll.VdsDeploy$44.run(VdsDeploy.java:882) 
[bll.jar:]
 at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]

2013-07-25 22:55:39,565 ERROR [org.ovirt.engine.core.bll.VdsDeploy] 
(pool-6-thread-5) [296737fb] Error during host
onode.sh.intel.com install: java.lang.NullPointerException
 at 
org.ovirt.otopi.dialog.MachineDialogParser.cliEnvironmentGet(MachineDialogParser.java:236)
 [otopi.jar:]
 at org.ovirt.engine.core.bll.VdsDeploy$14.call(VdsDeploy.java:347) 
[bll.jar:]
 at 
org.ovirt.engine.core.bll.VdsDeploy._nextCustomizationEntry(VdsDeploy.java:579) 
[bll.jar:]
 at org.ovirt.engine.core.bll.VdsDeploy._threadMain(VdsDeploy.java:791) 
[bll.jar:]
 at org.ovirt.engine.core.bll.VdsDeploy.access$1800(VdsDeploy.java:76) 
[bll.jar:]
 at org.ovirt.engine.core.bll.VdsDeploy$44.run(VdsDeploy.java:882) 
[bll.jar:]
 at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]

2013-07-25 22:55:39,568 ERROR [org.ovirt.engine.core.bll.VdsDeploy] 
(pool-6-thread-5) [296737fb] Error during host
onode.sh.intel.com install, prefering first exception: 
java.lang.NullPointerException
 at 
org.ovirt.otopi.dialog.MachineDialogParser.cliEnvironmentGet(MachineDialogParser.java:236)
 [otopi.jar:]
 at org.ovirt.engine.core.bll.VdsDeploy$14.call(VdsDeploy.java:347) 
[bll.jar:]
 at 
org.ovirt.engine.core.bll.VdsDeploy._nextCustomizationEntry(VdsDeploy.java:579) 
[bll.jar:]
 at org.ovirt.engine.core.bll.VdsDeploy._threadMain(VdsDeploy.java:791) 
[bll.jar:]
 at org.ovirt.engine.core.bll.VdsDeploy.access$1800(VdsDeploy.java:76) 
[bll.jar:]
 at org.ovirt.engine.core.bll.VdsDeploy$44.run(VdsDeploy.java:882) 
[bll.jar:]
 at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]

2013-07-25 22:55:39,569 ERROR [org.ovirt.engine.core.bll.InstallVdsCommand] 
(pool-6-thread-5) [296737fb] Host installation failed
for host 00c50bb0-f843-442a-a032-acebe0d092c4, onode.: 
java.lang.NullPointerException
 at 
org.ovirt.otopi.dialog.MachineDialogParser.cliEnvironmentGet(MachineDialogParser.java:236)
 [otopi.jar:]
 at org.ovirt.engine.core.bll.VdsDeploy$14.call(VdsDeploy.java:347) 
[bll.jar:]
 at 
org.ovirt.engine.core.bll.VdsDeploy._nextCustomizationEntry(VdsDeploy.java:579) 
[bll.jar:]
 at org.ovirt.engine.core.bll.VdsDeploy._threadMain(VdsDeploy.java:791) 
[bll.jar:]
 at org.ovirt.engine.core.bll.VdsDeploy.access$1800(VdsDeploy.java:76) 
[bll.jar:]
 at org.ovirt.engine.core.bll.VdsDeploy$44.run(VdsDeploy.java:882) 
[bll.jar:]
 at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]

2013-07-25 22:55:39,572 INFO  
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-6-thread-5) 
[296737fb] START,
SetVdsStatusVDSCommand(HostName = onode, HostId = 
00c50bb0-f843-442a-a032-acebe0d092c4, status=InstallFailed,
nonOperationalReason=NONE), log id: 39c3919d
2013-07-25 22:55:39,581 INFO  
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-6-thread-5) 
[296737fb] FINISH,
SetVdsStatusVDSCommand, log id: 39c3919d
2013-07-25 22:55:39,589 INFO  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(pool-6-thread-5) [296737fb]
Correlation ID: 296737fb, Call Stack: null, Custom Event ID: -1, Message: Host 
onode installation failed. Please refer to engine.log
and log files under /var/log/ovirt-engine/host-deploy/ on the engine for 
further details..




On Engine side, can you please check the log available at: 
/var/log/ovirt-engine/host-deploy/  ?




--
Cheers
Douglas
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel

[Engine-devel] testDisplayPort - VmMapperTest

2013-07-20 Thread Douglas Schilling Landgraf 

Hi,

Anyone else failing on this unittest?

$ make install-dev PREFIX=$HOME/ovirt-engine BUILD_UT=1

Results :

Tests in error:
  testDisplayPort(org.ovirt.engine.api.restapi.types.VmMapperTest)

Tests run: 121, Failures: 0, Errors: 1, Skipped: 0

[INFO] 


[INFO] Reactor Summary:
[INFO]
[INFO] ovirt-root  SUCCESS [0.443s]
[INFO] oVirt Build Tools root  SUCCESS [0.010s]
[INFO] oVirt checkstyle .. SUCCESS [1.054s]
[INFO] oVirt JBoss Modules Maven Plugin .. SUCCESS [3.084s]
[INFO] oVirt Checkstyle Checks ... SUCCESS [0.762s]
[INFO] oVirt Modules - backend ... SUCCESS [0.004s]
[INFO] oVirt Manager . SUCCESS [0.004s]
[INFO] oVirt Engine dependencies . SUCCESS [1.428s]
[INFO] oVirt Modules - manager ... SUCCESS [0.466s]
[INFO] CSharp Compatibility .. SUCCESS [2.694s]
[INFO] Common Code ... SUCCESS [10.024s]
[INFO] Common utilities .. SUCCESS [19.154s]
[INFO] Data Access Layer . SUCCESS [7.966s]
[INFO] engine scheduler bean . SUCCESS [1.462s]
[INFO] Vds broker  SUCCESS [7.028s]
[INFO] Search Backend  SUCCESS [2.866s]
[INFO] Backend Logic @Service bean ... SUCCESS [28.853s]
[INFO] oVirt RESTful API Backend Integration . SUCCESS [0.094s]
[INFO] oVirt RESTful API interface ... SUCCESS [0.119s]
[INFO] oVirt Engine API Definition ... SUCCESS [10.331s]
[INFO] oVirt Engine API Commom Parent POM  SUCCESS [0.068s]
[INFO] oVirt Engine API Common JAX-RS  SUCCESS [5.188s]
[INFO] oVirt RESTful API Backend Integration Type Mappers  FAILURE 
[1:49.300s]

[INFO] oVirt RESTful API Backend Integration JAX-RS Resources  SKIPPED
[INFO] oVirt RESTful API Backend Integration Webapp .. SKIPPED
[INFO] oVirt Engine Web Root . SKIPPED
[INFO] oVirt Engine Tools  SKIPPED
[INFO] oVirt Modules :: Frontend . SKIPPED
[INFO] oVirt Modules :: Webadmin . SKIPPED
[INFO] oVirt Modules - ui  SKIPPED
[INFO] Extensions for GWT  SKIPPED
[INFO] UI Utils Compatibility (for UICommon) . SKIPPED
[INFO] Frontend for GWT UI Projects .. SKIPPED
[INFO] UICommonWeb ... SKIPPED
[INFO] oVirt GWT UI common infrastructure  SKIPPED
[INFO] WebAdmin .. SKIPPED
[INFO] UserPortal  SKIPPED
[INFO] oVirt Server EAR .. SKIPPED
[INFO] 


[INFO] BUILD FAILURE
[INFO] 


[INFO] Total time: 3:33.247s
[INFO] Finished at: Sat Jul 20 04:09:04 BRT 2013
[INFO] Final Memory: 165M/881M
[INFO] 


[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.7.2:test
(default-test) on project restapi-types: There are test failures.

Thanks!

--
Cheers
Douglas
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel

Re: [Engine-devel] Unknown operation 'force-start' when starting VDSM

2013-07-18 Thread Douglas Schilling Landgraf 

Hello Greg,

On 07/18/2013 04:38 PM, Greg Sheremeta wrote:

Engine is installed and working on a fresh laptop install of Fedora 19. Rebased 
ovirt-engine from gerrit/master this morning. Trying to install host on a fresh 
Fedora 19 VM -- I'm trying to get a nested host setup.

Host installation fails with:

Jul 18 16:24:52 ovirt-host-fedora-2 systemd[1]: Starting Virtual Desktop Server 
Manager...
Jul 18 16:24:53 ovirt-host-fedora-2 systemd-vdsmd[3956]: Note: Forwarding 
request to 'systemctl disable libvirt-guests.service'.
Jul 18 16:24:53 ovirt-host-fedora-2 systemd-vdsmd[3956]: vdsm: libvirt already 
configured for vdsm [  OK  ]
Jul 18 16:24:53 ovirt-host-fedora-2 systemd-vdsmd[3956]: Starting multipathd...
Jul 18 16:24:53 ovirt-host-fedora-2 systemd-vdsmd[3956]: Redirecting to 
/bin/systemctl start  multipathd.service
Jul 18 16:24:53 ovirt-host-fedora-2 systemd-vdsmd[3956]: Redirecting to 
/bin/systemctl force-start  iscsid.service
Jul 18 16:24:53 ovirt-host-fedora-2 systemd-vdsmd[3956]: Unknown operation 
'force-start'.
Jul 18 16:24:53 ovirt-host-fedora-2 systemd[1]: vdsmd.service: control process 
exited, code=exited status=1
Jul 18 16:24:53 ovirt-host-fedora-2 systemd[1]: Failed to start Virtual Desktop 
Server Manager.
Jul 18 16:24:53 ovirt-host-fedora-2 systemd[1]: Unit vdsmd.service entered 
failed state.

I've never heard of force-start before, and googling for fedora force-start 
brings up this as the second result:
https://ask.fedoraproject.org/question/27737/vdsmdservice-fails-bc-iscsid-is-started-using-force-start/

So someone else out there is having this problem too :)



vdsm-4.10.3-18 should fix it.

Please check:
http://permalink.gmane.org/gmane.comp.emulators.ovirt.user/9488


--
Cheers
Douglas
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel

Re: [Engine-devel] Introduce mail

2013-06-29 Thread Douglas Schilling Landgraf 

Oi Fellipe,

On 06/27/2013 05:48 PM, Fellipe Henrique wrote:

hello folks!

I'm here today, to introduce myself. I want to start to contribute to
oVirt project, I'm developing most of time in python, and I'll love to
contribute in python, but can be in C.


Nice, welcome!



I love developing and virtualization, and I think this project have all
I like.

well, like I said, this is a introduce email, and I'll like suggestion
how can I help, and show my code to you guys.


Which part of world are you located? :) If you are Brazilian (I am 
guessing based on your last name), are you going to FISL next week?


If yes, we will have a booth there with talks about oVirt, demos and I 
am pretty sure we can talk about development, debugging env (on node 
side), eclipse and so on.


As Alon already shared, there are tasks that you can help.

Fell free to contact me offline list for more details about FISL.

--
Cheers
Douglas
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel

Re: [Engine-devel] NPE approving node

2013-06-28 Thread Douglas Schilling Landgraf 

On 06/27/2013 04:50 AM, Juan Hernandez wrote:

Any idea why?


Facing the same issue with updated tree. Cannot approve node.

$ git log -1
commit b5438e34e0b179ef4f8ee20ce6e0d7b25cd2a36a



2013-06-27 10:37:40,219 INFO
[org.ovirt.engine.core.bll.ApproveVdsCommand] (pool-6-thread-5)
[3dd1f412] Running command: ApproveVdsCommand internal: false. Entities
affected :  ID: 0be6cd89-c5f5-4a4e-b498-504bb2c23eb2 Type: VDS
2013-06-27 10:37:40,239 INFO
[org.ovirt.engine.core.bll.InstallVdsCommand] (pool-6-thread-5)
[3dd1f412] Before Installation host
0be6cd89-c5f5-4a4e-b498-504bb2c23eb2, h0.example.com
2013-06-27 10:37:40,294 ERROR
[org.ovirt.engine.core.bll.InstallVdsCommand] (pool-6-thread-5)
[3dd1f412] Host installation failed for host
0be6cd89-c5f5-4a4e-b498-504bb2c23eb2, h0.example.com.:
java.lang.NullPointerException
 at
org.ovirt.engine.core.utils.ssh.EngineSSHDialog.useDefaultKeyPair(EngineSSHDialog.java:32)
[utils.jar:]
 at
org.ovirt.engine.core.bll.VdsDeploy.useDefaultKeyPair(VdsDeploy.java:804) 
[bll.jar:]

 at
org.ovirt.engine.core.bll.InstallVdsCommand.executeCommand(InstallVdsCommand.java:170)
[bll.jar:]
 at
org.ovirt.engine.core.bll.ApproveVdsCommand.executeCommand(ApproveVdsCommand.java:49)
[bll.jar:]
 at
org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1065)
[bll.jar:]
 at
org.ovirt.engine.core.bll.CommandBase.executeActionInTransactionScope(CommandBase.java:1150)
[bll.jar:]
 at
org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:1613)
[bll.jar:]
 at
org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInSuppressed(TransactionSupport.java:174)
[utils.jar:]
 at
org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:116)
[utils.jar:]
 at
org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1168)
[bll.jar:]
 at
org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:316) 
[bll.jar:]

 at
org.ovirt.engine.core.bll.MultipleActionsRunner.executeValidatedCommand(MultipleActionsRunner.java:174)
[bll.jar:]
 at
org.ovirt.engine.core.bll.MultipleActionsRunner.RunCommands(MultipleActionsRunner.java:156)
[bll.jar:]
 at
org.ovirt.engine.core.bll.MultipleActionsRunner$1.run(MultipleActionsRunner.java:94)
[bll.jar:]
 at
org.ovirt.engine.core.utils.threadpool.ThreadPoolUtil$InternalWrapperRunnable.run(ThreadPoolUtil.java:71)
[utils.jar:]
 at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
[rt.jar:1.7.0_09-icedtea]
 at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
[rt.jar:1.7.0_09-icedtea]
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
[rt.jar:1.7.0_09-icedtea]
 at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_09-icedtea]
 at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_09-icedtea]
 at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]




--
Cheers
Douglas
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel

Re: [Engine-devel] NPE approving node

2013-06-28 Thread Douglas Schilling Landgraf 

On 06/28/2013 02:22 PM, Alon Bar-Lev wrote:



- Original Message -

From: Douglas Schilling Landgraf dougsl...@redhat.com
To: engine-devel@ovirt.org
Cc: Alon Bar-Lev alo...@redhat.com, Yaniv Bronheim ybron...@redhat.com
Sent: Friday, June 28, 2013 9:55:02 PM
Subject: Re: [Engine-devel] NPE approving node

On 06/27/2013 04:50 AM, Juan Hernandez wrote:

Any idea why?


Facing the same issue with updated tree. Cannot approve node.

$ git log -1
commit b5438e34e0b179ef4f8ee20ce6e0d7b25cd2a36a


This[1] should have fixed that.

Can you please send the exception?

[1] http://gerrit.ovirt.org/#/c/16184/


I have cleanup/refresh my working tree, looks like it's gone. Thanks!

--
Cheers
Douglas
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel

[Engine-devel] Jenkins failure - findbugs failed: Timeout: killed the sub-process

2013-06-28 Thread Douglas Schilling Landgraf 

Hi,

Anyone else facing the below jenkins failure when sending patches to 
gerrit?


[ERROR] Failed to execute goal 
org.codehaus.mojo:findbugs-maven-plugin:2.5.2:findbugs (default-cli) on 
project jboss-modules-maven-plugin: Execution default-cli of goal 
org.codehaus.mojo:findbugs-maven-plugin:2.5.2:findbugs failed: Timeout: 
killed the sub-process - [Help 1]


http://jenkins.ovirt.org/job/ovirt_engine_find_bugs_gerrit/2650/

Thanks!

--
Cheers
Douglas
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel

Re: [node-devel] RC for oVirt Node 3.0.0 is now available

2013-05-20 Thread Douglas Schilling Landgraf 

On 05/20/2013 08:03 AM, Mike Burns wrote:

On 05/20/2013 04:48 AM, Alon Bar-Lev wrote:



- Original Message -

From: Mike Burns mbu...@redhat.com
To: node-devel node-devel@ovirt.org, annou...@ovirt.org
Sent: Friday, May 17, 2013 7:12:48 PM
Subject: [node-devel] RC for oVirt Node 3.0.0 is now available

What can I test?
You can focus on hardware support, package integration, the
installation (all paths) and the TUI.


Hi!


Thanks for the testing Alon!



1. ovirt-node-upgrade should be moved to /usr/sbin as it is a tool to
be executed by admin, and it is not working properly.

ssh host ovirt-node-upgrade --iso=- --reboot=10  iso


Joey,  can you post a patch to move it into /usr/sbin?



2. when I try to enable ssh and save, I get the following on black
text screen:

An error appeared in the UI: invalidData 'Passwords do not match'
Press ENTER to logout...
or enter 's' to drop to shell


Ryan, can you look into this?



3. I don't understand the difference of gray and non gray fields... I
can access both...


Do you have examples?

Fabian, can you investigate?



4. Registration of HTTP does not work for some reason... do not think
it is a new problem.

5. Registration using HTTPS produces a dialog with the following content:

   @ENGINENAME@ Fingerprint
   TBD
   ...

6. Saving Save  Register does not configure vdsm-reg.conf nor
starting it.


These 3 -- yes, there are a number of things broken on the page.  I
filed a bug over the weekend:

https://bugzilla.redhat.com/show_bug.cgi?id=964320

Mike/Alon Should I start from this point?


--
Cheers
Douglas
___
node-devel mailing list
node-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/node-devel