Re: [ovirt-devel] Tools for developing and building oVirt.js project

2014-09-01 Thread Sandro Bonazzola
Il 29/08/2014 17:16, Vojtech Szocs ha scritto:
 
 
 - Original Message -
 From: Vojtech Szocs vsz...@redhat.com
 To: Sandro Bonazzola sbona...@redhat.com
 Cc: infra in...@ovirt.org, devel@ovirt.org
 Sent: Friday, August 29, 2014 4:43:44 PM
 Subject: Re: [ovirt-devel] Tools for developing and building oVirt.js project



 - Original Message -
 From: Sandro Bonazzola sbona...@redhat.com
 To: Vojtech Szocs vsz...@redhat.com
 Cc: Tomas Jelinek tjeli...@redhat.com, Mooli Tayer
 mta...@redhat.com, devel@ovirt.org, infra
 in...@ovirt.org
 Sent: Friday, August 29, 2014 8:05:58 AM
 Subject: Re: [ovirt-devel] Tools for developing and building oVirt.js
 project

 Il 28/08/2014 21:00, Vojtech Szocs ha scritto:


 - Original Message -
 From: Sandro Bonazzola sbona...@redhat.com
 To: Tomas Jelinek tjeli...@redhat.com, Mooli Tayer
 mta...@redhat.com
 Cc: devel@ovirt.org
 Sent: Tuesday, August 26, 2014 12:03:14 PM
 Subject: Re: [ovirt-devel] Tools for developing and building oVirt.js
 project

 Il 26/08/2014 09:38, Tomas Jelinek ha scritto:


 - Original Message -
 From: Mooli Tayer mta...@redhat.com
 To: Greg Sheremeta gsher...@redhat.com
 Cc: devel@ovirt.org
 Sent: Tuesday, August 26, 2014 9:17:20 AM
 Subject: Re: [ovirt-devel] Tools for developing and building oVirt.js
 project

 Are we talking about using node as a development/test/packaging(minify
 etc
 )
 tool or having a runtime backend (site) on top of node?

 It is only devel environment (e.g. build dependency), not runtime.


 If it's build dependency it's not just devel environment.

 Right, I messed up my comment above, sorry.

 Node.js can be (and typically is) used as both devel  build dependency
 for JavaScript projects.

 We must ensure that all required build dependencies are available and
 properly packaged for all supported distributions.

 Yes, fully agreed.

 Fedora already has some packages we could use, for example:
 http://koji.fedoraproject.org/koji/packageinfo?packageID=15154
 http://koji.fedoraproject.org/koji/packageinfo?packageID=15356

 However, there's one complication (as Greg mentioned before): npm (Node
 package manager) resolves Node-specific packages (esentially JavaScript
 artifacts) via HTTP access, so we'd need some infra to serve these, and
 for each such JS module:
 - either use existing package for that JS module, if one exists
 - or maintain package for that JS module on our own [*]

 [*] I understand that this is not what we want to do in general

 I would add
 - Ask supported distributions to provide needed rpms

 Well, that ^^ would be ideal.



 In other words, there would have to be some infra to support builds for
 JavaScript/Node.js projects, similar to existing infra to support builds
 for Java/Maven projects:
 - package for Node.js + npm
 - package for each JS module (likely problematic)
 - tool (existing Artifactory that serves Maven artifacts?) to serve
   JS modules via HTTP for npm to consume (maybe problematic)


 Adding infra for above


 In any case, we can proceed with developing oVirt.js without requiring
 Node.js as a build dependency. I see two possible solutions here:

 1, avoid using build tools like Traceur (ES6 - ES5 transpiler)
and UglifyJS (code compressor/obfuscator), just concatenate
JS source files into resulting JS target file (either via
command in Makefile or via some Maven plugin)

PROS: no special build requirements
CONS: can't use tools like Traceur

 2, use build tools like Traceur and UglifyJS, commit resulting
JS target file into source tree, maybe with git commit hook
for this

PROS: can use tools like Traceur
CONS: storing target JS file in source tree

 3, (?)

 Use something simpler to package for compressing / minimizing like
 http://yui.github.io/yuicompressor/ or any other tool like that at build
 time
 (nothing against Node.js at development time).

 YUI Compressor is written in Java, we could use it within our Java-based
 Engine build. It seems that YUI Compressor uses Rhino (JS engine written
 in Java) with some custom Rhino extensions/tweaks.

 I didn't find Fedora package for YUI Compressor, but I found this:

   http://davidb.github.io/yuicompressor-maven-plugin/

 And luckily, this Maven plugin is also in JBoss Maven repo:

   
 https://repository.jboss.org/nexus/service/local/repositories/central/content/net/alchim31/maven/yuicompressor-maven-plugin/1.4.0/yuicompressor-maven-plugin-1.4.0.pom

 OK, now some bad news. According to this:

   http://www.yuiblog.com/blog/2012/10/16/state-of-yui-compressor/

 development on YUI Compressor continues through JavaScript (surprise!)
 project yUglify (it's based on UglifyJS which I proposed way above):

   https://github.com/yui/yuglify

 And, not surprisingly, yUglify is Node.js module. Here we go :)

 As everyone can see, all popular tools for JavaScript development
 are pretty much centered around Node.js, that is not coincidence.
 Avoiding Node.js for JavaScript 

Re: [ovirt-devel] Moving forward our frontend stack

2014-09-01 Thread Sven Kieske
Well I really think this is a very bad idea.
I'm pretty sure I don't need to introduce
the concept of checksums to anybody on this list
and why this is done.

You must decide whether you want the correct code
or not.
If you decide to disable it on one repo, what is the
justification to not disable it on another/all repos/projects?

just my 2 cents :)

Am 29.08.2014 16:54, schrieb Vojtech Szocs:
 Well, I meant to avoid disabling checksum checking globally.
 If we can selectively disable checksum checking for specific
 Maven artifacts like gwtp etc. then we could do that..

-- 
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
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] ovirt35 - deep dive - AAA improvements - extensions and generic LDAP provider

2014-09-01 Thread Barak Azulay
BEGIN:VCALENDAR
PRODID:Zimbra-Calendar-Provider
VERSION:2.0
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:Asia/Jerusalem
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETTO:+0200
TZOFFSETFROM:+0300
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU
TZNAME:IST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETTO:+0300
TZOFFSETFROM:+0200
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=-1FR
TZNAME:IDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:0fdb010c-90aa-44ef-84ce-b669135c2769
SUMMARY:ovirt35 - deep dive - AAA improvements - extensions and generic LDAP
  provider
ATTENDEE;CN=Alon Bar-Lev;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRU
 E:mailto:alo...@redhat.com
ATTENDEE;CN=Oved Ourfalli;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TR
 UE:mailto:ov...@redhat.com
ATTENDEE;CN=yzaslavs;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:ma
 ilto:yzasl...@redhat.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:users@o
 virt.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:devel@o
 virt.org
ORGANIZER;CN=Barak Azulay:mailto:bazu...@redhat.com
DTSTART;TZID=Asia/Jerusalem:20140902T17
DTEND;TZID=Asia/Jerusalem:20140902T173000
STATUS:CONFIRMED
CLASS:PUBLIC
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
TRANSP:OPAQUE
LAST-MODIFIED:20140901T122305Z
DTSTAMP:20140901T122305Z
SEQUENCE:0
DESCRIPTION:The following is a new meeting request:\n\nSubject: ovirt35 - de
 ep dive - AAA improvements - extensions and generic LDAP provider \nOrganize
 r: Barak Azulay bazu...@redhat.com \n\nTime: Tuesday\, September 2\, 201
 4\, 5:00:00 PM - 5:30:00 PM GMT +02:00 Jerusalem\n \nInvitees: alonbl@redhat
 .com\; ov...@redhat.com\; yzasl...@redhat.com\; us...@ovirt.org\; devel@ovir
 t.org \n\n\n*~*~*~*~*~*~*~*~*~*\n\nWithin ovirt-engine-3.5 a major rework of
  authentication and authorization had been done. \nWithin the scope of the w
 ork a new public extension interface had been introduced\, this interface ma
 y be used for future modularization of the ovirt-engine implementation. \nTh
 roughout this presentation we will walk through the major changes within the
  engine core\, learn the concepts of the extension api and introduce the new
  ldap implementation for authentication and authorization of the engine. \n\
 ngoogle hangout link: https://plus.google.com/events/c7ut1o51g3qb93n2n22kq8u
 l1sk
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER;RELATED=START:-PT5M
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Stable branch gerrit hook and Related-To: bug

2014-09-01 Thread Michal Skrivanek

On Aug 28, 2014, at 16:14 , Martin Sivak msi...@redhat.com wrote:

 Hi,
 
 yeah I think it should be like that.

+1

 
 * Should it pass the same checks than a Bug-Url?
  Most probably yes
  Right now that is:
- Public
- Target release
- Product
 * Should it change the bug statuses too?
  Most probably no
 * Should it update the external trackers of the bug?
  Most probably yes
 
 --
 Martin Sivák
 msi...@redhat.com
 Red Hat Czech
 RHEV-M SLA / Brno, CZ
 
 - Original Message -
 On 08/27, Martin Sivak wrote:
 Hi,
 
 I would like to ask if it might be possible for the gerrit hook to stop
 giving -1 to patches that do not have bug-url, but have related-to.
 
 The reason for this is that I have a rather large patchset that is adding a
 new feature. No single patch by itself fixes the referenced bug and there
 are also patches that are not related to the feature itself, but were
 backported because they did some refactoring that was needed for the code
 to apply and/or work properly.
 
 I have a couple question, which of these should happen for the
 Related-To bugs?
 
 * Should it pass the same checks than a Bug-Url?
  Most probably yes
  Right now that is:
- Public
- Target release
- Product
 * Should it change the bug statuses too?
  Most probably no
 * Should it update the external trackers of the bug?
  Most probably yes
 
 
 --
 Martin Sivák
 msi...@redhat.com
 Red Hat Czech
 RHEV-M SLA / Brno, CZ
 
 ___
 Devel mailing list
 Devel@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/devel
 
 --
 David Caro
 
 Red Hat S.L.
 Continuous Integration Engineer - EMEA ENG Virtualization RD
 
 Tel.: +420 532 294 605
 Email: dc...@redhat.com
 Web: www.redhat.com
 RHT Global #: 82-62605
 
 ___
 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


[ovirt-devel] [vdsm] Error while building ovirt-live from 3.5 snapshot repo

2014-09-01 Thread Sandro Bonazzola
Can you check vdsm on 3.5 branch?
From the live build execution:



Retrieving 
http://resources.ovirt.org/pub/ovirt-3.5-snapshot/rpm/el6/x86_64/vdsm-4.16.2-16.git5629cdd.el6.x86_64.rpm
 ...OK
Retrieving 
http://resources.ovirt.org/pub/ovirt-3.5-snapshot/rpm/el6/noarch/vdsm-cli-4.16.2-16.git5629cdd.el6.noarch.rpm
 ...OK
Retrieving 
http://resources.ovirt.org/pub/ovirt-3.5-snapshot/rpm/el6/noarch/vdsm-jsonrpc-4.16.2-16.git5629cdd.el6.noarch.rpm
 ...OK
Retrieving 
http://resources.ovirt.org/pub/ovirt-3.5-snapshot/rpm/el6/x86_64/vdsm-python-4.16.2-16.git5629cdd.el6.x86_64.rpm
 ...OK
Retrieving 
http://resources.ovirt.org/pub/ovirt-3.5-snapshot/rpm/el6/noarch/vdsm-python-zombiereaper-4.16.2-16.git5629cdd.el6.noarch.rpm
 ...OK
Retrieving 
http://resources.ovirt.org/pub/ovirt-3.5-snapshot/rpm/el6/noarch/vdsm-xmlrpc-4.16.2-16.git5629cdd.el6.noarch.rpm
 ...OK
Retrieving 
http://resources.ovirt.org/pub/ovirt-3.5-snapshot/rpm/el6/noarch/vdsm-yajsonrpc-4.16.2-16.git5629cdd.el6.noarch.rpm
 ...OK



  Installing: vdsm # 
[840/989]Usage: /usr/bin/vdsm-tool [options] action [arguments]
Valid options:
  -h, --help
Show this help menu.
  -l, --logfile path
Redirect logging to file.
  -v, --verbose
Include warning (and errors) messages in log.
  -vv, --vverbose
Include information (and above) messages in log.
  -vvv, --vvverbose
Include debug (and above) messages in log.
  -a, --append
Append to logfile instead of truncating it
(if logging to a file).

 Commands in module dummybr:

 dummybr
usage:
 /usr/bin/vdsm-tool [options] dummybr
Defines dummy bridge on libvirt network.


 Commands in module load_needed_modules:

 load-needed-modules
usage:
 /usr/bin/vdsm-tool [options] load-needed-modules
Load needed modules


 Commands in module nwfilter:

 nwfilter
usage:
 /usr/bin/vdsm-tool [options] nwfilter
Defines network filters on libvirt


 Commands in module passwd:

 remove-saslpasswd
usage:
 /usr/bin/vdsm-tool [options] Remove vdsm password for libvirt connection


 set-saslpasswd
usage:
 /usr/bin/vdsm-tool [options] set-saslpasswd
Set vdsm password for libvirt connection


 Commands in module restore_nets:

 restore-nets
usage:
 /usr/bin/vdsm-tool [options] restore-nets
Restores the networks to what was previously persisted via vdsm.


 Commands in module seboolsetup:

 sebool-config
usage:
 /usr/bin/vdsm-tool [options] sebool-config
Enable the required selinux booleans


 sebool-unconfig
usage:
 /usr/bin/vdsm-tool [options] sebool-unconfig
Disable the required selinux booleans


 Commands in module service:

 service-disable
usage:
 /usr/bin/vdsm-tool [options] service-disable service-name
Disable a system service.

Parameters:
service-name - service to disable


 service-is-managed
usage:
 /usr/bin/vdsm-tool [options] service-is-managed service-name
Check the existence of a service.

Parameters:
service-name - service to query


 service-reload
usage:
 /usr/bin/vdsm-tool [options] service-reload service-name
Notify a system service to reload configurations.

Parameters:
service-name - service to notify


 service-restart
usage:
 /usr/bin/vdsm-tool [options] service-restart service-name
Restart a system service.

Parameters:
service-name - service to restart


 service-start
usage:
 /usr/bin/vdsm-tool [options] service-start service-name
Start a system service.

Parameters:
service-start - service to start


 service-status
usage:
 /usr/bin/vdsm-tool [options] service-status service-name
Get status of a system service.

Parameters:
service-name - service to query


 service-stop
usage:
 /usr/bin/vdsm-tool [options] service-stop service-name
Stop a system service.

Parameters:
service-name - service to stop


 Commands in module transient:

 cleanup-transient-repository
usage:
 /usr/bin/vdsm-tool [options] cleanup-transient-repository
Cleanup the unused transient disks present in the repository.
(NOTE: it is recommended to NOT execute this command when the vdsm
daemon is running)


 setup-transient-repository
usage:
 /usr/bin/vdsm-tool [options] setup-transient-repository
Prepare the transient disks repository


 Commands in module unified_persistence:

 upgrade-unified-persistence
usage:
 /usr/bin/vdsm-tool [options] upgrade-unified-persistence [upgrade-options]
Upgrade host networking persistence from ifcfg to unified if the
persistence model is set as unified in /usr/lib64/python2.X/site-packages/
vdsm/config.py


 Commands in module upgrade:

 Commands in module upgrade_300_networks:

 upgrade-3.0.0-networks
usage:
 /usr/bin/vdsm-tool [options] upgrade-3.0.0-networks [upgrade-options]
Since ovirt-3.0, Vdsm uses libvirt networks (with names vdsm-*) to store
its own networks. Older Vdsms did not have those defined, and used only

Re: [ovirt-devel] feature review - ReportGuestDisksLogicalDeviceName

2014-09-01 Thread Dan Kenigsberg
On Sun, Aug 31, 2014 at 07:20:04AM -0400, Liron Aravot wrote:
 Feel free to review the the following feature.
 
 http://www.ovirt.org/Features/ReportGuestDisksLogicalDeviceName

Thanks for posting this feature page. Two things worry me about this
feature. The first is timing. It is not reasonable to suggest an API
change, and expect it to get to ovirt-3.5.0. We are two late anyway.

The other one is the suggested API. You suggest placing volatile and
optional infomation in getVMList. It won't be the first time that we
have it (guestIPs, guestFQDN, clientIP, and displayIP are there) but
it's foreign to the notion of conf reported by getVMList() - the set
of parameters needed to recreate the VM.

Would you describe the motivation for using this verb? What are the
pros and cons? Which other ideas where considered?

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


[ovirt-devel] [ENGINE] - failure to debug GWT

2014-09-01 Thread Yair Zaslavsky
Hi all,
Maybe one can help me in strange debugging issues I have?
I am running the debug server using the following line -

make gwt-debug DEBUG_MODULE=webadmin 
DEV_EXTRA_BUILD_FLAGS=-Dgwt.persistentunitcache=false

The server listens on port 8000 as expected.
I then connect from Eclipse (using remote debug) to port 8000 - and the server 
crashes, this is what I see -


http://pastebin.com/twapYa9N

Can anyone help with this?

Thanks,
Yair

(I will also paste here the output) -

ERROR] [AppClassLoader@7ffe] info AspectJ Weaver Version 1.6.11 built on 
Tuesday Mar 15, 2011 at 15:31:04 GMT
[ERROR] [AppClassLoader@7ffe] info register classloader 
sun.misc.Launcher$AppClassLoader@7ffe
[ERROR] [AppClassLoader@7ffe] info using configuration 
file:/home/yzaslavs/.m2/upstream_repository/org/ovirt/engine/ui/gwt-extension/3.6.0-SNAPSHOT/gwt-extension-3.6.0-SNAPSHOT.jar!/META-INF/aop.xml
[ERROR] [AppClassLoader@7ffe] info using configuration 
file:/home/yzaslavs/.m2/upstream_repository/org/ovirt/engine/ui/gwt-extension/3.6.0-SNAPSHOT/gwt-extension-3.6.0-SNAPSHOT-sources.jar!/META-INF/aop.xml
[ERROR] [AppClassLoader@7ffe] info register aspect 
org.ovirt.engine.ui.gwtextension.DontPrune
[ERROR] [AppClassLoader@7ffe] info register aspect 
org.ovirt.engine.ui.gwtextension.DontPrune
[ERROR] -bindAddress host 0.0.0.0 unknown
[ERROR] Google Web Toolkit 2.5.1
[ERROR] DevMode [-noserver] [-port port-number | auto] [-whitelist 
whitelist-string] [-blacklist blacklist-string] [-logdir directory] [-logLevel 
level] [-gen dir] [-bindAddress host-name-or-address] [-codeServerPort 
port-number | auto] [-server servletContainerLauncher[:args]] [-startupUrl 
url] [-war dir] [-deploy dir] [-extra dir] [-workDir dir] module[s] 
[ERROR] 
[ERROR] where 
[ERROR]   -noserverPrevents the embedded web server from running
[ERROR]   -portSpecifies the TCP port for the embedded web server 
(defaults to )
[ERROR]   -whitelist   Allows the user to browse URLs that match the 
specified regexes (comma or space separated)
[ERROR]   -blacklist   Prevents the user browsing URLs that match the 
specified regexes (comma or space separated)
[ERROR]   -logdir  Logs to a file in the given directory, as well as 
graphically
[ERROR]   -logLevelThe level of logging detail: ERROR, WARN, INFO, 
TRACE, DEBUG, SPAM, or ALL
[ERROR]   -gen Debugging: causes normally-transient generated types 
to be saved in the specified directory
[ERROR]   -bindAddress Specifies the bind address for the code server and 
web server (defaults to 127.0.0.1)
[ERROR]   -codeServerPort  Specifies the TCP port for the code server (defaults 
to 9997)
[ERROR]   -server  Specify a different embedded web server to run (must 
implement ServletContainerLauncher)
[ERROR]   -startupUrl  Automatically launches the specified URL
[ERROR]   -war The directory into which deployable output files 
will be written (defaults to 'war')
[ERROR]   -deploy  The directory into which deployable but not servable 
output files will be written (defaults to 'WEB-INF/deploy' under the -war 
directory/jar, and may be the same as the -extra directory/jar)
[ERROR]   -extra   The directory into which extra files, not intended 
for deployment, will be written
[ERROR]   -workDir The compiler's working directory for internal use 
(must be writeable; defaults to a system temp dir)
[ERROR] and 
[ERROR]   module[s]Specifies the name(s) of the module(s) to host
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 6:07.100s
[INFO] Finished at: Tue Sep 02 04:51:20 IDT 2014
[INFO] Final Memory: 56M/653M
[INFO] 
[WARNING] The requested profile gwt-user could not be activated because it 
does not exist.
[ERROR] Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:2.4.0:debug 
(default-cli) on project webadmin: Command [[
[ERROR] /bin/sh -c /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/bin/java 
-javaagent:/home/yzaslavs/.m2/upstream_repository/org/aspectj/aspectjweaver/1.6.11/aspectjweaver-1.6.11.jar
 -Xms1024M -Xmx4096M -XX:PermSize=512M -XX:MaxPermSize=1024M \
[ERROR] 
-Dgwt.jjs.permutationWorkerFactory=com.google.gwt.dev.ThreadedPermutationWorkerFactory
 \
[ERROR] -Dgwt.jjs.maxThreads=4 \
[ERROR] 
-Djava.io.tmpdir=/home/yzaslavs/work/ovirt_git/ovirt-engine/frontend/webadmin/modules/webadmin/target/tmp
 \
[ERROR] 
-Djava.util.prefs.systemRoot=/home/yzaslavs/work/ovirt_git/ovirt-engine/frontend/webadmin/modules/webadmin/target/tmp/.java
 \
[ERROR] 
-Djava.util.prefs.userRoot=/home/yzaslavs/work/ovirt_git/ovirt-engine/frontend/webadmin/modules/webadmin/target/tmp/.java
 '-Dgwt.dontPrune=org\.ovirt\.engine\.core\.(common|compat)\..*' -Xdebug 
-Xnoagent