- Devel - oVirt List Archives

Re: [Engine-devel] Fwd: about ca-file
by Michael Pasternak 21 Apr '13

21 Apr '13

Hi, Please make sure [1] is exist on the file system and has right permissions, btw till you resolve this, you can connect to your site in insecure mode: 1. without host being validated raising --dont-validate-cert-chain flag 2. without no-certificate error being thrown raising --insecure flag (host will be validated once [1] is available/accessible by the shell) [1] /home/leaboy/ovirt_ca/ca_cear.pem On 04/20/2013 11:37 PM, Itamar Heim wrote: > > [Engine-devel] about ca-file.eml > > Subject: > [Engine-devel] about ca-file > From: > "wanglibo" <wanglibo(a)tongfangcloud.com> > Date: > Mon, 8 Apr 2013 18:02:37 +0800 > > To: > <engine-devel(a)ovirt.org> > > > Hi,all: > > I’m in troubling with ca-file, who can tell me which the direction assigned to CA_FILE > > On the webpage http://www.ovirt.org/How_to_Connect_to_SPICE_Console_Without_Portal > > saided from the web: |wget -O ${CA_FILE}| |*http://${OVIRT}/ca.crt* <http://%24%7Bovirt%7D/ca.crt>| > > When I use overt-shell, I get ca.pem like this : > > > > [leaboy@Leaboy ovirt_ca]$ pwd > > /home/leaboy/ovirt_ca > > [leaboy@Leaboy ovirt_ca]$ wget -o ca-cert.pem http://192.168.1.181/ca.pem > > [leaboy@Leaboy ovirt_ca]$ ls > > ca-cert.pem > > [leaboy@Leaboy ovirt_ca]$ > > > > And then, I launched overt-shell and connect to overt-engine like this: > > > > ++++++++++++++++++++++++++++++++++++++++++ > > > > Welcome to oVirt shell > > > > ++++++++++++++++++++++++++++++++++++++++++ > > > > > > [oVirt shell (disconnected)]# *connect --url https://192.168.1.181 --user admin@internal --password 111111 --ca-file /home/leaboy/ovirt_ca/ca_cear.pem* > > > > > > error: [ERROR]::oVirt API connection failure, [Errno 185090050] _ssl.c:340: error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib > > > > > > [oVirt shell (disconnected)]# > > > > > > _______________________________________________ > Engine-devel mailing list > Engine-devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel -- Michael Pasternak RedHat, ENG-Virtualization R&D

1 0

[Engine-devel] Packaging and locales
by Alon Bar-Lev 21 Apr '13

21 Apr '13

Hello, >From recent thread I learned that we package locales within our main package, message bundles are going into jars, and by default we do not build them all. As this is GWT specific as far as I see in build, I have no real visibility of what happening. However, I do expect locales to be packaged and installed as separate packages, side by side with main package. Something like: # yum install ovirt-engine - provides en_US # yum install ovirt-engine-locale-zh_CN - will add zh_CN support. This ease maintenance, as these translations can be maintain using their own release cycle and even out of main tree. Any thoughts? Alon

2 6

[Engine-devel] Why deploy failed? Please help me, thanks.
by 李强 20 Apr '13

20 Apr '13

HI：All OS:F18 Ovirt engine version: the first is 3.2.0 update to 3.2.1 and now I compile the source to other language. MEM:8G CPU:I7 DISK:60G I will use chinese language for ovirt engine, but rpm have not chinese language for default install. So I git clone source, that I compile the source success. >From link: http://www.ovirt.org/Building_oVirt_engine COMPILE COMMAND mvn clean install -Pdep,gwt-admin,gwt-user,all-langs and show message: ------------------------ ------------------------ I deploy: DEPLOY COMMAND: cd ear && mvn clean install -Pdep QUESTION: 1, I open the first page that it show ------------------ Welcome to Open Virtualization Manager. Version 3.2.1- ------------------ Source shoule be 3.3.0? If souce version 3.3.0,then I deploy is not invalid. 2, Change language is failed and is still englist. Other language is invalid. COMMAND DEPLOY: ++++++++++++++++++++++ [liqiang@engine ear]$ mvn clean install -Pdep [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for org.ovirt.engine:engine-server-ear:ear:3.3.0-SNAPSHOT [WARNING] 'distributionManagement.repository.id' must not be 'local', this identifier is reserved for the local repository, using it for other repositories will corrupt your repository metadata. @ line 18, column 11 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building oVirt Server EAR 3.3.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ engine-server-ear --- [INFO] Deleting /home/liqiang/ovirt-engine/ear/target [INFO] [INFO] --- maven-antrun-plugin:1.7:run (undeploy-ear) @ engine-server-ear --- [WARNING] Parameter tasks is deprecated, use target instead [INFO] Executing tasks main: [echo] *** Deleting /usr/share/jboss-as/standalone/deployments/engine.ear/... [delete] Deleting directory /usr/share/jboss-as/standalone/deployments/engine.ear [INFO] Executed tasks [INFO] [INFO] --- maven-ear-plugin:2.8:generate-application-xml (default-generate-application-xml) @ engine-server-ear --- [INFO] Generating application.xml [INFO] [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ engine-server-ear --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/liqiang/ovirt-engine/ear/src/main/java [INFO] Copying 1 resource [INFO] [INFO] --- maven-ear-plugin:2.8:ear (default-ear) @ engine-server-ear --- [INFO] Copying artifact [war:org.ovirt.engine.core:root-war:3.3.0-SNAPSHOT] to [root.war] (unpacked) [INFO] Copying artifact [war:org.ovirt.engine.api:restapi-webapp:3.3.0-SNAPSHOT] to [restapi.war] (unpacked) [INFO] Copying artifact [war:org.ovirt.engine.ui:userportal:3.3.0-SNAPSHOT] to [userportal.war] (unpacked) [INFO] Copying artifact [war:org.ovirt.engine.ui:webadmin:3.3.0-SNAPSHOT] to [webadmin.war] (unpacked) [INFO] Copying artifact [ejb:org.ovirt.engine.core:scheduler:3.3.0-SNAPSHOT] to [scheduler.jar] [INFO] Copying artifact [ejb:org.ovirt.engine.core:bll:3.3.0-SNAPSHOT] to [bll.jar] [INFO] Copying artifact [jar:org.ovirt.engine.core:vdsbroker:3.3.0-SNAPSHOT] to [lib/vdsbroker.jar] [INFO] Copying artifact [jar:org.ovirt.engine.core:compat:3.3.0-SNAPSHOT] to [lib/compat.jar] [INFO] Copying artifact [jar:org.ovirt.engine.core:common:3.3.0-SNAPSHOT] to [lib/common.jar] [INFO] Copying artifact [jar:org.hibernate:hibernate-validator:4.0.2.GA] to [lib/hibernate-validator.jar] [INFO] Copying artifact [jar:javax.validation:validation-api:1.0.0.GA] to [lib/validation-api.jar] [INFO] Copying artifact [jar:javax.xml.bind:jaxb-api:2.1] to [lib/jaxb-api.jar] [INFO] Copying artifact [jar:javax.xml.stream:stax-api:1.0-2] to [lib/stax-api.jar] [INFO] Copying artifact [jar:com.sun.xml.bind:jaxb-impl:2.1.3] to [lib/jaxb-impl.jar] [INFO] Copying artifact [jar:org.ovirt.engine.core:utils:3.3.0-SNAPSHOT] to [lib/utils.jar] [INFO] Copying artifact [jar:commons-beanutils:commons-beanutils:1.8.2] to [lib/commons-beanutils.jar] [INFO] Copying artifact [jar:org.apache.mina:mina-core:2.0.1] to [lib/mina-core.jar] [INFO] Copying artifact [jar:org.apache.sshd:sshd-core:0.7.0] to [lib/sshd-core.jar] [INFO] Copying artifact [jar:org.ovirt.otopi:otopi:1.0.0] to [lib/otopi.jar] [INFO] Copying artifact [jar:org.ovirt.ovirt-host-deploy:ovirt-host-deploy:1.0.0] to [lib/ovirt-host-deploy.jar] [INFO] Copying artifact [jar:org.apache.commons:commons-compress:1.4.1] to [lib/commons-compress.jar] [INFO] Copying artifact [jar:org.tukaani:xz:1.0] to [lib/xz.jar] [INFO] Copying artifact [jar:commons-lang:commons-lang:2.6] to [lib/commons-lang.jar] [INFO] Copying artifact [jar:commons-codec:commons-codec:1.4] to [lib/commons-codec.jar] [INFO] Copying artifact [jar:org.apache.xmlrpc:xmlrpc-client:3.1.3] to [lib/xmlrpc-client.jar] [INFO] Copying artifact [jar:org.apache.xmlrpc:xmlrpc-common:3.1.3] to [lib/xmlrpc-common.jar] [INFO] Copying artifact [jar:org.apache.ws.commons.util:ws-commons-util:1.0.2] to [lib/ws-commons-util.jar] [INFO] Copying artifact [jar:xml-apis:xml-apis:1.0.b2] to [lib/xml-apis.jar] [INFO] Copying artifact [jar:org.ovirt.engine.core:dal:3.3.0-SNAPSHOT] to [lib/dal.jar] [INFO] Copying artifact [jar:org.springframework:spring-jdbc:3.1.1.RELEASE] to [lib/spring-jdbc.jar] [INFO] Copying artifact [jar:org.springframework:spring-tx:3.1.1.RELEASE] to [lib/spring-tx.jar] [INFO] Copying artifact [jar:org.springframework.ldap:spring-ldap-core:1.3.1.RELEASE] to [lib/spring-ldap-core.jar] [INFO] Copying artifact [jar:commons-httpclient:commons-httpclient:3.1] to [lib/commons-httpclient.jar] [INFO] Copying artifact [jar:commons-collections:commons-collections:3.1] to [lib/commons-collections.jar] [INFO] Copying artifact [jar:org.quartz-scheduler:quartz:2.1.2] to [lib/quartz.jar] [INFO] Copying artifact [jar:c3p0:c3p0:0.9.1.1] to [lib/c3p0.jar] [INFO] Copying artifact [jar:org.slf4j:slf4j-api:1.6.1] to [lib/slf4j-api.jar] [INFO] Copying artifact [jar:org.ovirt.engine.core:searchbackend:3.3.0-SNAPSHOT] to [lib/searchbackend.jar] [INFO] Copying artifact [jar:org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.0.Final] to [lib/jboss-interceptors-api_1.1_spec.jar] [INFO] Copying artifact [jar:org.springframework:spring-core:3.1.1.RELEASE] to [lib/spring-core.jar] [INFO] Copying artifact [jar:org.springframework:spring-asm:3.1.1.RELEASE] to [lib/spring-asm.jar] [INFO] Copying artifact [jar:org.springframework:spring-beans:3.1.1.RELEASE] to [lib/spring-beans.jar] [INFO] Copying artifact [jar:org.springframework:spring-context:3.1.1.RELEASE] to [lib/spring-context.jar] [INFO] Copying artifact [jar:org.springframework:spring-aop:3.1.1.RELEASE] to [lib/spring-aop.jar] [INFO] Copying artifact [jar:aopalliance:aopalliance:1.0] to [lib/aopalliance.jar] [INFO] Copying artifact [jar:org.springframework:spring-expression:3.1.1.RELEASE] to [lib/spring-expression.jar] [INFO] Copy ear sources to /home/liqiang/ovirt-engine/ear/target/engine [INFO] Could not find manifest file: /home/liqiang/ovirt-engine/ear/target/engine/META-INF/MANIFEST.MF - Generating one [INFO] Building jar: /home/liqiang/ovirt-engine/ear/target/engine.ear [INFO] [INFO] --- maven-dependency-plugin:2.1:unpack (deploy-modules) @ engine-server-ear --- [INFO] Configured Artifact: org.ovirt.engine.core:dependencies:modules:3.3.0-SNAPSHOT:zip [INFO] Configured Artifact: org.ovirt.engine.core:common:modules:3.3.0-SNAPSHOT:zip [INFO] Configured Artifact: org.ovirt.engine.core:compat:modules:3.3.0-SNAPSHOT:zip [INFO] Configured Artifact: org.ovirt.engine.core:dal:modules:3.3.0-SNAPSHOT:zip [INFO] Configured Artifact: org.ovirt.engine.core:searchbackend:modules:3.3.0-SNAPSHOT:zip [INFO] Configured Artifact: org.ovirt.engine.core:tools:modules:3.3.0-SNAPSHOT:zip [INFO] Configured Artifact: org.ovirt.engine.core:utils:modules:3.3.0-SNAPSHOT:zip [INFO] Unpacking /home/liqiang/.m2/repository/org/ovirt/engine/core/dependencies/3.3.0-SNAPSHOT/dependencies-3.3.0-SNAPSHOT-modules.zip to /usr/share/jboss-as/modules with includes null and excludes:null [WARNING] Unable to expand to file /usr/share/jboss-as/modules/org/apache/commons/configuration/main/module.xml [WARNING] Unable to expand to file /usr/share/java/apache-commons-configuration.jar [INFO] Unpacking /home/liqiang/.m2/repository/org/ovirt/engine/core/common/3.3.0-SNAPSHOT/common-3.3.0-SNAPSHOT-modules.zip to /usr/share/jboss-as/modules with includes null and excludes:null [INFO] Unpacking /home/liqiang/.m2/repository/org/ovirt/engine/core/compat/3.3.0-SNAPSHOT/compat-3.3.0-SNAPSHOT-modules.zip to /usr/share/jboss-as/modules with includes null and excludes:null [INFO] Unpacking /home/liqiang/.m2/repository/org/ovirt/engine/core/dal/3.3.0-SNAPSHOT/dal-3.3.0-SNAPSHOT-modules.zip to /usr/share/jboss-as/modules with includes null and excludes:null [INFO] Unpacking /home/liqiang/.m2/repository/org/ovirt/engine/core/searchbackend/3.3.0-SNAPSHOT/searchbackend-3.3.0-SNAPSHOT-modules.zip to /usr/share/jboss-as/modules with includes null and excludes:null [INFO] Unpacking /home/liqiang/.m2/repository/org/ovirt/engine/core/tools/3.3.0-SNAPSHOT/tools-3.3.0-SNAPSHOT-modules.zip to /usr/share/jboss-as/modules with includes null and excludes:null [INFO] Unpacking /home/liqiang/.m2/repository/org/ovirt/engine/core/utils/3.3.0-SNAPSHOT/utils-3.3.0-SNAPSHOT-modules.zip to /usr/share/jboss-as/modules with includes null and excludes:null [INFO] [INFO] --- maven-antrun-plugin:1.7:run (deploy-ear) @ engine-server-ear --- [WARNING] Parameter tasks is deprecated, use target instead [INFO] Executing tasks main: [echo] *** Copying updated files to /usr/share/jboss-as/standalone/deployments/engine.ear/... [unjar] Expanding: /home/liqiang/ovirt-engine/ear/target/engine.ear into /usr/share/jboss-as/standalone/deployments/engine.ear [echo] *** Touching /usr/share/jboss-as/standalone/deployments/engine.ear/META-INF/application.xml to force redeployment of engine.ear... [echo] *** Touching engine.ear.dodeploy to force deployment of engine.ear... [INFO] Executed tasks [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ engine-server-ear --- [INFO] Installing /home/liqiang/ovirt-engine/ear/target/engine.ear to /home/liqiang/.m2/repository/org/ovirt/engine/engine-server-ear/3.3.0-SNAPSHOT/engine-server-ear-3.3.0-SNAPSHOT.ear [INFO] Installing /home/liqiang/ovirt-engine/ear/pom.xml to /home/liqiang/.m2/repository/org/ovirt/engine/engine-server-ear/3.3.0-SNAPSHOT/engine-server-ear-3.3.0-SNAPSHOT.pom [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 54.354s [INFO] Finished at: Fri Apr 19 10:48:39 EDT 2013 [INFO] Final Memory: 14M/191M [INFO] ------------------------------------------------------------------------ ++++++++++++++++++++++ engine-upgrade COMMAND MESSAGE: ------------------------------------ [root@engine ~]# engine-upgrade Checking for updates... (This may take several minutes)...[ DONE ] 8 Updates available: * ovirt-engine-3.2.1-1.fc18.noarch * ovirt-engine-tools-3.2.1-1.fc18.noarch * ovirt-engine-backend-3.2.1-1.fc18.noarch * ovirt-engine-dbscripts-3.2.1-1.fc18.noarch * ovirt-engine-genericapi-3.2.1-1.fc18.noarch * ovirt-engine-restapi-3.2.1-1.fc18.noarch * ovirt-engine-userportal-3.2.1-1.fc18.noarch * ovirt-engine-webadmin-portal-3.2.1-1.fc18.noarch During the upgrade process, oVirt Engine will not be accessible. All existing running virtual machines will continue but you will not be able to start or stop any new virtual machines during the process. Would you like to proceed? (yes|no): yes Stopping ovirt-engine service... [ DONE ] Stopping DB related services... [ DONE ] Pre-upgrade validations... [ DONE ] Backing Up Database... [ DONE ] Rename Database... [ DONE ] Updating rpms... [ DONE ] Updating Database... [ DONE ] Restore Database name... [ DONE ] Preparing CA... [ DONE ] Running post install configuration... [ DONE ] Starting ovirt-engine service... [ DONE ] oVirt Engine upgrade completed successfully! * Upgrade log available at /var/log/ovirt-engine/ovirt-engine-upgrade_2013_04_19_10_39_54.log * DB Backup available at /var/lib/ovirt-engine/backups/ovirt-engine_db_backup_2013_04_19_10_39_54.sql ------------------------------------

4 14

Re: [Engine-devel] [oss-security] CVE-2012-XXYY Request -- google-authenticator: Information disclosure due insecure requirement on the secrets file
by Michael Pasternak 18 Apr '13

18 Apr '13

FYI On 04/18/2013 01:45 PM, Jan Lieskovsky wrote: > Hello Kurt, Steve, Alexander, vendors, > > as noted in [1]: > > An information disclosure file was found in the way google-authenticator, > a pluggable authentication module (PAM) which allows login using one-time > passcodes conforming to the open standards developed by the Initiative for > Open Authentication (OATH), performed management of its secret / state file > in certain configurations. Due the lack of 'user=' option the secret file > was previously required to be user-readable, allowing (in certain cases) > a local attacker to obtain the (pre)shared client-to-authentication-server > secret, possibly leading to victim's account impersonation. > > A different vulnerability than CVE-2013-0258. > > References: > [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666129 > [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666129#10 > [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666129#20 > [4] https://bugzilla.redhat.com/show_bug.cgi?id=953505 > > Relevant upstream patch: > [5] https://code.google.com/p/google-authenticator/source/detail?r=c3414e9857ad… > > @Alexander - since I am not sure I have described the attack vector above > properly, please correct me if / where required. > > @Kurt * the CVE-2012- identifier should be allocated to this issue, since > the security implications of this problem are for the first time > mentioned here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666129#10 (2012-09-22), > > * from what I have looked, there doesn't seem to be: > http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=authenticator > > a CVE identifier allocated to this issue yet (as noted above > CVE-2013-0258 from that list is different issue). > > => could you allocate one? > > Thank you && Regards, Jan. > -- > Jan iankko Lieskovsky / Red Hat Security Response Team -- Michael Pasternak RedHat, ENG-Virtualization R&D

1 0

Re: [Engine-devel] minutes for sync up on Open Attestation integration with oVirt in 4/9
by Chen, Wei D 18 Apr '13

18 Apr '13

Hi Doron and Ofri, Thanks for your reply, here is some other question. ii. When adding a host into the trusted cluster, the host will be attested via OAT service, only trusted hosted can be added. Would you also kindly tell me if there is any mandatory logic check when adding a host into a cluster, so we can also put attestation logic with these mandatory check together? Some example or code location is better. Thanks a lot. Best Regards, Dave Chen -----Original Message----- From: Doron Fediuck [mailto:dfediuck@redhat.com] Sent: Wednesday, April 10, 2013 8:03 PM To: Ofri Masad Cc: Wei, Gang; Chen, Wei D; Cao, Buddy; Zhang, Lijuan Subject: Re: minutes for sync up on Open Attestation integration with oVirt in 4/9 ----- Original Message ----- > From: "Ofri Masad" <omasad(a)redhat.com> > To: "Gang Wei" <gang.wei(a)intel.com> > Cc: "Wei D Chen" <wei.d.chen(a)intel.com>, "Buddy Cao" > <buddy.cao(a)intel.com>, "Lijuan Zhang" <lijuan.zhang(a)intel.com>, "Doron > Fediuck" <dfediuck(a)redhat.com> > Sent: Wednesday, April 10, 2013 2:23:57 PM > Subject: Re: minutes for sync up on Open Attestation integration with > oVirt in 4/9 > > Hi, > > answers inside the mail body. > > ----- Original Message ----- > > From: "Doron Fediuck" <dfediuck(a)redhat.com> > > To: "Wei D Chen" <wei.d.chen(a)intel.com> > > Cc: "Gang Wei" <gang.wei(a)intel.com>, "Buddy Cao" > > <buddy.cao(a)intel.com>, "Lijuan Zhang" <lijuan.zhang(a)intel.com>, > > "Ofri Masad" <omasad(a)redhat.com> > > Sent: Wednesday, April 10, 2013 12:12:26 PM > > Subject: Re: minutes for sync up on Open Attestation integration > > with oVirt in 4/9 > > > > Hi Dave, > > Adding Ofri to answer your questions. > > > > ----- Original Message ----- > > > From: "Wei D Chen" <wei.d.chen(a)intel.com> > > > To: "Gang Wei" <gang.wei(a)intel.com>, "Doron Fediuck" > > > <dfediuck(a)redhat.com>, > > > "Buddy Cao" <buddy.cao(a)intel.com>, "Lijuan Zhang" > > > <lijuan.zhang(a)intel.com> > > > Sent: Wednesday, April 10, 2013 6:31:05 AM > > > Subject: RE: minutes for sync up on Open Attestation integration > > > with oVirt in 4/9 > > > > > > Hi Doron, > > > > > > > > > iii. Then periodic trust check will be added into background process > > > for > > > all existing hosts, once becoming non-trusted, mark it as > > > non-operational. > > > > > > - [Dave] Would you give me some details about the “background > > > process” mentioned in our sync up meeting? What’s the process and > > > where is related code? > > > > > The use Quartz Job to scheduled background processes. > An example can be found in: > ovirt-engine/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/Backend.java(Line: > 222) > > This code calls a method that is located in: > ovirt-engine/backend/manager/modules/bll/src/main/java/org/ovirt/engin > e/core/bll/quota/QuotaManager.java > (Line: 1000) > the @OnTimerMethodAnnotation annotation and the unique job name > connects the two in runtime. > > The job can query the attestation server for all the host and then set > untrusted hosts to Non-Operational. > the best way would be to call SetNonOperationalVdsCommand with a new > NonOperationalReason. > This command tries to migrate all VMs from the host and then set it > non operational. > (We need to think about non-migrational VMs - should we close those > VMs or keep the host running) > One more thing you may want to consider; If we get a positive response for a host which is currently non-operational, issue an activate command to try and make it operational again. Alternatively, you may decide not to handle it, assuming untrusted hosts can only be activated manually (see below Ofri's response on activating a host). > > > > > > iv. If admin fixed the non-operational node and try to switch it to > > > operational mode again, a trust check will happen to gate the switching. > > > > > > - [Dave] If there is a button provided from UI for checking the > > > logic? or we need add an extra-button for attestation check only? > > > > > In the UI we already have the "Activate" option. What still needs to > be added is the check with the attestation provider to make sure that > if the cluster is defined 'Trusted'. If so, only trusted host will > succeed in the activate command (and, of course, a proper Audit Log > error in case the host failed to activate due to trust issue. > > the correct place to add this check would be in: > ovirt-engine/backend/manager/modules/vdsbroker/src/main/java/org/ovirt > /engine/core/vdsbroker/VdsManager.java:activate() > this is where the re-activation process begins. > > > > > > > Thanks very much. > > > > > > > > > > > > Best Regards, > > > Dave Chen

6 17

[Engine-devel] How get all language WebAdm ?
by 李强 18 Apr '13

18 Apr '13

HI：All I install ovirt engine and open IE9 to manage. But I select Chinese language UI to display and failed. The UI's language always is Englisth and covers to Other language failed. OS:federa 18. Ovirt-Engine:3.2 MEM Size:4G DIsk:60G CPU:intel i7 Manage OS:Win7 Sp1 Manage IE:9 Can you help me? Thanks,

5 10

Re: [Engine-devel] [vdsm] Adding vdsm_api support for gluster vdsm verbs
by Aravinda 17 Apr '13

17 Apr '13

[Adding engine-devel] On 04/16/2013 02:10 PM, Aravinda wrote: > > vdsm/gluster is vdsm plugin for gluster related functionality. These > functionalities are available only when vdsm-gluster package is > installed. So the schema JSON of vdsm-gluster cannot be added to the > same file(vdsm_api/vdsmapi-schema.json) > > Looks like vdsm_api is not providing plugin support. This patch adds > functionality to vdsm_api to read vdsmapi-gluster-schema.json if > available. But with this approach we need to edit the core vdsmapi.py > file. > > http://gerrit.ovirt.org/#/c/13921/ > > Alternate approach: > We can have "vdsm_api/plugins" or "vdsm_api/schema" directory inside > vdsm_api, so that we can modify vdsmapi.py to read all schema files > from that dir. When vdsm-gluster package installed, it copies > vdsmapi-gluster-schema.json into schema directory. > > > -- > regards > Aravinda > > > On 04/15/2013 04:14 PM, Aravinda wrote: >> Hi, >> >> We are trying to add json rpc support for vdsm gluster verbs. I >> submitted a patch to read gluster verbs schema from vdsm/gluster >> directory. >> http://gerrit.ovirt.org/#/c/13921/ >> >> Let me know if the approach is fine. >> >> -- >> regards >> Aravinda >> _______________________________________________ >> vdsm-devel mailing list >> vdsm-devel(a)lists.fedorahosted.org >> https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel > > _______________________________________________ > vdsm-devel mailing list > vdsm-devel(a)lists.fedorahosted.org > https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel

2 2

[Engine-devel] Starting a new translation
by Alex Ont 17 Apr '13

17 Apr '13

Hi, Trying to translate the userportal ... How should one obtain the English properties file to jumpstart the translation? e.g. There are ApplicationConstants_xxx.properties for already translated locales, but there is no English version. Thanks, Alex

2 1

[Engine-devel] upgrade failing with latest master
by Dead Horse 16 Apr '13

16 Apr '13

logs attached First attempt: 2013-04-10 13:57:32::ERROR::common_utils::355::root:: YUM: FAIL: Error in PREUN scriptlet in rpm package ovirt-engine-backend-3.3.0-15.fc17.noarch 2013-04-10 13:57:32::DEBUG::common_utils::347::root:: YUM: VERB: Script sink: /var/tmp/rpm-tmp.J0HyUz: line 1: fg: no job control error: %preun(ovirt-engine-backend-3.3.0-15.fc17.noarch) scriptlet failed, exit status 1 2013-04-10 13:57:32::DEBUG::common_utils::347::root:: YUM: VERB: Done: ovirt-engine-backend-3.3.0-15.fc17.noarch Second attempt: 2013-04-10 15:12:11::DEBUG::common_utils::347::root:: YUM: VERB: Building transaction 2013-04-10 15:12:12::ERROR::common_utils::355::root:: YUM: FAIL: [u'ovirt-engine-backend-3.3.0-14.fc17.noarch requires ovirt-engine = 3.3.0-14.fc17'] 2013-04-10 15:12:12::DEBUG::common_utils::347::root:: YUM: VERB: Performing rollback 2013-04-10 15:12:12::DEBUG::common_utils::1410::root:: Locking rpms in yum-version-lock 2013-04-10 15:12:12::ERROR::engine-upgrade::1299::root:: Traceback (most recent call last): File "/bin/engine-upgrade", line 1292, in <module> main(options) File "/bin/engine-upgrade", line 1142, in main runFunc([rhyum.begin], MSG_INFO_CHECK_UPDATE) File "/bin/engine-upgrade", line 617, in runFunc func() File "/bin/engine-upgrade", line 310, in begin self.emptyTransaction = not self._miniyum.buildTransaction() File "/usr/share/ovirt-engine/scripts/miniyum.py", line 761, in buildTransaction raise yum.Errors.YumBaseError(msg) YumBaseError: [u'ovirt-engine-backend-3.3.0-14.fc17.noarch requires ovirt-engine = 3.3.0-14.fc17'] Realizing things were now hosed: [root@ovirtfoo /]# yum erase ovirt-* otopi-* Loaded plugins: langpacks, presto, refresh-packagekit, versionlock Resolving Dependencies --> Running transaction check ---> Package otopi.noarch 0:3.3.0-15.fc17 will be erased ---> Package otopi-java.noarch 0:3.3.0-15.fc17 will be erased ---> Package ovirt-engine.noarch 0:3.3.0-14.fc17 will be erased ---> Package ovirt-engine-backend.noarch 0:3.3.0-14.fc17 will be erased ---> Package ovirt-engine-backend.noarch 0:3.3.0-15.fc17 will be erased ---> Package ovirt-engine-cli.noarch 0:3.3.0.1-15.fc17 will be erased ---> Package ovirt-engine-dbscripts.noarch 0:3.3.0-14.fc17 will be erased ---> Package ovirt-engine-restapi.noarch 0:3.3.0-14.fc17 will be erased ---> Package ovirt-engine-sdk.noarch 0:3.3.0.1-15.fc17 will be erased ---> Package ovirt-engine-setup.noarch 0:3.3.0-15.fc17 will be erased ---> Package ovirt-engine-tools.noarch 0:3.3.0-14.fc17 will be erased ---> Package ovirt-engine-userportal.noarch 0:3.3.0-14.fc17 will be erased ---> Package ovirt-engine-webadmin-portal.noarch 0:3.3.0-14.fc17 will be erased ---> Package ovirt-host-deploy.noarch 0:3.3.0-15.fc17 will be erased ---> Package ovirt-host-deploy-java.noarch 0:3.3.0-15.fc17 will be erased ---> Package ovirt-image-uploader.noarch 0:3.3.0-15.fc17 will be erased ---> Package ovirt-iso-uploader.noarch 0:3.3.0-15.fc17 will be erased ---> Package ovirt-log-collector.noarch 0:3.3.0-15.fc17 will be erased --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Removing: otopi noarch 3.3.0-15.fc17 @ovirt-engine 463 k otopi-java noarch 3.3.0-15.fc17 @ovirt-engine 27 k ovirt-engine noarch 3.3.0-14.fc17 @ovirt-engine 1.3 M ovirt-engine-backend noarch 3.3.0-14.fc17 @ovirt-engine 20 M ovirt-engine-backend noarch 3.3.0-15.fc17 @ovirt-engine 20 M ovirt-engine-cli noarch 3.3.0.1-15.fc17 @ovirt-engine 557 k ovirt-engine-dbscripts noarch 3.3.0-14.fc17 @ovirt-engine 816 k ovirt-engine-restapi noarch 3.3.0-14.fc17 @ovirt-engine 1.0 M ovirt-engine-sdk noarch 3.3.0.1-15.fc17 @ovirt-engine 3.1 M ovirt-engine-setup noarch 3.3.0-15.fc17 @ovirt-engine 653 k ovirt-engine-tools noarch 3.3.0-14.fc17 @ovirt-engine 178 k ovirt-engine-userportal noarch 3.3.0-14.fc17 @ovirt-engine 23 M ovirt-engine-webadmin-portal noarch 3.3.0-14.fc17 @ovirt-engine 32 M ovirt-host-deploy noarch 3.3.0-15.fc17 @ovirt-engine 211 k ovirt-host-deploy-java noarch 3.3.0-15.fc17 @ovirt-engine 11 k ovirt-image-uploader noarch 3.3.0-15.fc17 @ovirt-engine 923 k ovirt-iso-uploader noarch 3.3.0-15.fc17 @ovirt-engine 98 k ovirt-log-collector noarch 3.3.0-15.fc17 @ovirt-engine 133 k Transaction Summary ================================================================================ Remove 18 Packages Installed size: 104 M Is this ok [y/N]: y Downloading Packages: Running Transaction Check Running Transaction Test Transaction Test Succeeded Running Transaction Erasing : ovirt-engine-backend.noarch 1/18 Erasing : ovirt-engine-dbscripts-3.3.0-14.fc17.noarch 2/18 Erasing : ovirt-engine-restapi-3.3.0-14.fc17.noarch 3/18 Erasing : ovirt-engine-setup-3.3.0-15.fc17.noarch 4/18 Erasing : ovirt-engine-tools-3.3.0-14.fc17.noarch 5/18 Erasing : ovirt-engine-userportal-3.3.0-14.fc17.noarch 6/18 Erasing : ovirt-engine-3.3.0-14.fc17.noarch 7/18 warning: /etc/ovirt-engine/engine.conf saved as /etc/ovirt-engine/engine.conf.rpmsave Erasing : ovirt-engine-webadmin-portal-3.3.0-14.fc17.noarch 8/18 Erasing : ovirt-host-deploy-java-3.3.0-15.fc17.noarch 9/18 Erasing : otopi-java-3.3.0-15.fc17.noarch 10/18 Erasing : ovirt-host-deploy-3.3.0-15.fc17.noarch 11/18 Erasing : ovirt-image-uploader-3.3.0-15.fc17.noarch 12/18 warning: /etc/ovirt-engine/imageuploader.conf saved as /etc/ovirt-engine/imageuploader.conf.rpmsave Erasing : ovirt-iso-uploader-3.3.0-15.fc17.noarch 13/18 warning: /etc/ovirt-engine/isouploader.conf saved as /etc/ovirt-engine/isouploader.conf.rpmsave Erasing : ovirt-log-collector-3.3.0-15.fc17.noarch 14/18 warning: /etc/ovirt-engine/logcollector.conf saved as /etc/ovirt-engine/logcollector.conf.rpmsave Erasing : ovirt-engine-cli-3.3.0.1-15.fc17.noarch 15/18 Erasing : ovirt-engine-sdk-3.3.0.1-15.fc17.noarch 16/18 Erasing : otopi-3.3.0-15.fc17.noarch 17/18 Error in PREUN scriptlet in rpm package ovirt-engine-backend /var/tmp/rpm-tmp.uFqX1f: line 1: fg: no job control error: %preun(ovirt-engine-backend-3.3.0-15.fc17.noarch) scriptlet failed, exit status 1 Verifying : otopi-3.3.0-15.fc17.noarch 1/18 Verifying : otopi-java-3.3.0-15.fc17.noarch 2/18 Verifying : ovirt-log-collector-3.3.0-15.fc17.noarch 3/18 Verifying : ovirt-engine-webadmin-portal-3.3.0-14.fc17.noarch 4/18 Verifying : ovirt-host-deploy-3.3.0-15.fc17.noarch 5/18 Verifying : ovirt-engine-tools-3.3.0-14.fc17.noarch 6/18 Verifying : ovirt-engine-setup-3.3.0-15.fc17.noarch 7/18 Verifying : ovirt-engine-sdk-3.3.0.1-15.fc17.noarch 8/18 Verifying : ovirt-engine-restapi-3.3.0-14.fc17.noarch 9/18 Verifying : ovirt-engine-userportal-3.3.0-14.fc17.noarch 10/18 Verifying : ovirt-host-deploy-java-3.3.0-15.fc17.noarch 11/18 Verifying : ovirt-image-uploader-3.3.0-15.fc17.noarch 12/18 Verifying : ovirt-iso-uploader-3.3.0-15.fc17.noarch 13/18 Verifying : ovirt-engine-cli-3.3.0.1-15.fc17.noarch 14/18 ovirt-engine-backend-3.3.0-15.fc17.noarch was supposed to be removed but is not! Verifying : ovirt-engine-backend-3.3.0-15.fc17.noarch 15/18 Verifying : ovirt-engine-backend-3.3.0-14.fc17.noarch 16/18 Verifying : ovirt-engine-3.3.0-14.fc17.noarch 17/18 Verifying : ovirt-engine-dbscripts-3.3.0-14.fc17.noarch 18/18 Removed: otopi.noarch 0:3.3.0-15.fc17 otopi-java.noarch 0:3.3.0-15.fc17 ovirt-engine.noarch 0:3.3.0-14.fc17 ovirt-engine-backend.noarch 0:3.3.0-14.fc17 ovirt-engine-cli.noarch 0:3.3.0.1-15.fc17 ovirt-engine-dbscripts.noarch 0:3.3.0-14.fc17 ovirt-engine-restapi.noarch 0:3.3.0-14.fc17 ovirt-engine-sdk.noarch 0:3.3.0.1-15.fc17 ovirt-engine-setup.noarch 0:3.3.0-15.fc17 ovirt-engine-tools.noarch 0:3.3.0-14.fc17 ovirt-engine-userportal.noarch 0:3.3.0-14.fc17 ovirt-engine-webadmin-portal.noarch 0:3.3.0-14.fc17 ovirt-host-deploy.noarch 0:3.3.0-15.fc17 ovirt-host-deploy-java.noarch 0:3.3.0-15.fc17 ovirt-image-uploader.noarch 0:3.3.0-15.fc17 ovirt-iso-uploader.noarch 0:3.3.0-15.fc17 ovirt-log-collector.noarch 0:3.3.0-15.fc17 Failed: ovirt-engine-backend.noarch 0:3.3.0-15.fc17 Complete! [root@ovirtfoo /]# rpm -qa | grep oto protobuf-java-2.4.1-12.fc17.x86_64 libgphoto2-2.4.14-1.fc17.x86_64 [root@ovirtfoo /]# rpm -qa | grep ovirt ovirt-engine-backend-3.3.0-15.fc17.noarch [root@ovirtfoo /]# yum erase ovirt-engine-backend-3.3.0-15.fc17.noarch Loaded plugins: langpacks, presto, refresh-packagekit, versionlock Resolving Dependencies --> Running transaction check ---> Package ovirt-engine-backend.noarch 0:3.3.0-15.fc17 will be erased --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Removing: ovirt-engine-backend noarch 3.3.0-15.fc17 @ovirt-engine 20 M Transaction Summary ================================================================================ Remove 1 Package Installed size: 20 M Is this ok [y/N]: y Downloading Packages: Running Transaction Check Running Transaction Test Transaction Test Succeeded Running Transaction Error in PREUN scriptlet in rpm package ovirt-engine-backend-3.3.0-15.fc17.noarch /var/tmp/rpm-tmp.jq1b7e: line 1: fg: no job control error: %preun(ovirt-engine-backend-3.3.0-15.fc17.noarch) scriptlet failed, exit status 1 Verifying : ovirt-engine-backend-3.3.0-15.fc17.noarch 1/1 Failed: ovirt-engine-backend.noarch 0:3.3.0-15.fc17 Complete! - DHC

2 14

[Engine-devel] watchdog
by Laszlo Hornyak 14 Apr '13

14 Apr '13

Hi, A new version of the watchdög feature is available in gerrit: http://gerrit.ovirt.org/13057 - db http://gerrit.ovirt.org/13058 - bll http://gerrit.ovirt.org/13059 - frontend http://gerrit.ovirt.org/13060 - rest http://www.ovirt.org/Features/Watchdog_engine_support Since the last update the patchset has gone through major changes to meet the new architectureal and functional requirements. Also because of the rewrite this is again a preview version under testing with some missing functionality, therefore I re-introduced the [wip] flag on it. Thx, Laszlo

7 16