[Engine-devel] ovirt-cli 3.2.0.6 released
For more details see [1]. [1] http://wiki.ovirt.org/wiki/CLI#Change_Log -- Michael Pasternak RedHat, ENG-Virtualization RD ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] ovirt-sdk at pypi
From now on latest ovirt-sdk will be available at pypi, for more details see [1]. [1] http://wiki.ovirt.org/wiki/SDK#pypi -- Michael Pasternak RedHat, ENG-Virtualization RD ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] ovirt-cli at pypi
From now on latest ovirt-cli will be available at pypi, for more details see [1]. [1] http://wiki.ovirt.org/wiki/CLI#pypi -- Michael Pasternak RedHat, ENG-Virtualization RD ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] [help]how to get the CA certificate when uploader ISO
On 11/01/2012 09:52 PM, Keith Robertson wrote: On 11/01/2012 05:23 AM, Sheldon wrote: On 10/31/2012 09:37 PM, Keith Robertson wrote: On 10/31/2012 01:40 AM, Sheldon wrote: I make a domain name ISO, Domain type is ISO, Storage Type is NFS, Format is V1 $ sudo engine-iso-uploader -v --iso-domain=ISO upload Fedora-17-x86_64-DVD.iso [sudo] password for ovirt: Please provide the REST API username for oVirt Engine (CTRL+D to abort): admin@internal Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to abort): ERROR: Problem connecting to the REST API. Is the service available and does the CA certificate exist? ERROR: 'NoneType' object is not iterable INFO: Use the -h option to see usage. Just to be clear the error in [1] is simply a symptom. It isn't the root cause. The root cause is quite possibly the CA certificate. I have created a patch in [2] that I'd appreciate if you could test as it will provide more debugging information about why the API creation is failing. Simply follow the steps in [3] Cheers, Keith [1] ERROR: 'NoneType' object is not iterable [2] http://gerrit.ovirt.org/8954 [3] Step 1: git clone http://gerrit.ovirt.org/p/ovirt-iso-uploader.git Step 2: Cherry pick the patch... git fetch git://gerrit.ovirt.org/ovirt-iso-uploader refs/changes/54/8954/2 git cherry-pick FETCH_HEAD Step 3: export APP_VERSION=3.0.0; export APP_RELEASE=1 Step 4: cd ovirt-iso-uploader Step 5: make Step 6: Notice the ovirt-iso-uploader*.rpm location in the STDOUT Step 7: yum install /path/to/ovirt-iso-uploader*.rpm still error. but different debug info. Yes. The patch adds additional debug info. $ sudo engine-iso-uploader -v --iso-domain=ISO upload RHEL6.3-20120531.0-Server-x86_64-DVD1.iso Please provide the REST API username for oVirt Engine (CTRL+D to abort): admin@internal Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to abort): DEBUG: url(https://localhost:443/api) DEBUG: user(admin@internal) DEBUG: ca(/etc/pki/ovirt-engine/ca.pem) DEBUG: insecure(False) ERROR: Problem connecting to the REST API. Is the service available and does the CA certificate exist? Error: [ERROR]::oVirt API connection failure, Now we're getting to the good stuff as you can see that you are getting a connection refused. Questions for you: 1) Are you *certain* that 'https://localhost:443/api' is accessible from the local system, that it is the address of your oVirt engine, and is not being blocked by a FW? Easy test on the local box point your browser at that url. I have edited the tls port, it is not 443. It is 4301. I can access https://localhost:4301/api' 2) Are you certain that the CA is valid? To verify this you will need to issue a 'curl' statement and supply the CA. Example: curl -v -k -u $USER:$PASS --cacert /etc/pki/ovirt-engine/ca.pem -X GET -H 'Accept: application/xml' 'https://localhost:443/api/api/vms also: $ curl -v -k -u admin@internal:letmein! --cacert /etc/pki/ovirt-engine/ca.pem -X GET -H 'Accept: application/xml' 'https://localhost:4301/api/vms' is ok and I designate the tls port, now it can work. $ sudo engine-iso-uploader -rlocalhost:4301 -v --iso-domain=ISO upload Fedora-17-x86_64-DVD.iso Thank you. [Errno 111] Connection refused DEBUG: Unable to get host and path information from API. -- Sheldon Feng(冯少合)shao...@linux.vnet.ibm.com IBM Linux Technology Center -- Sheldon Feng(冯少合)shao...@linux.vnet.ibm.com IBM Linux Technology Center ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] ovirt-sdk at pypi
Great Michael! I will update the wiki part I did the other day for different distros. - Original Message - From: Michael Pasternak mpast...@redhat.com To: engine-devel engine-devel@ovirt.org Cc: us...@ovirt.org Sent: Friday, November 2, 2012 8:44:40 AM Subject: [Engine-devel] ovirt-sdk at pypi From now on latest ovirt-sdk will be available at pypi, for more details see [1]. [1] http://wiki.ovirt.org/wiki/SDK#pypi -- Michael Pasternak RedHat, ENG-Virtualization RD ___ 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
Re: [Engine-devel] [help]how to get the CA certificate when uploader ISO
On 11/02/2012 10:01 AM, Sheldon wrote: On 11/01/2012 09:52 PM, Keith Robertson wrote: On 11/01/2012 05:23 AM, Sheldon wrote: On 10/31/2012 09:37 PM, Keith Robertson wrote: On 10/31/2012 01:40 AM, Sheldon wrote: I make a domain name ISO, Domain type is ISO, Storage Type is NFS, Format is V1 $ sudo engine-iso-uploader -v --iso-domain=ISO upload Fedora-17-x86_64-DVD.iso [sudo] password for ovirt: Please provide the REST API username for oVirt Engine (CTRL+D to abort): admin@internal Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to abort): ERROR: Problem connecting to the REST API. Is the service available and does the CA certificate exist? ERROR: 'NoneType' object is not iterable INFO: Use the -h option to see usage. Just to be clear the error in [1] is simply a symptom. It isn't the root cause. The root cause is quite possibly the CA certificate. I have created a patch in [2] that I'd appreciate if you could test as it will provide more debugging information about why the API creation is failing. Simply follow the steps in [3] Cheers, Keith [1] ERROR: 'NoneType' object is not iterable [2] http://gerrit.ovirt.org/8954 [3] Step 1: git clone http://gerrit.ovirt.org/p/ovirt-iso-uploader.git Step 2: Cherry pick the patch... git fetch git://gerrit.ovirt.org/ovirt-iso-uploader refs/changes/54/8954/2 git cherry-pick FETCH_HEAD Step 3: export APP_VERSION=3.0.0; export APP_RELEASE=1 Step 4: cd ovirt-iso-uploader Step 5: make Step 6: Notice the ovirt-iso-uploader*.rpm location in the STDOUT Step 7: yum install /path/to/ovirt-iso-uploader*.rpm still error. but different debug info. Yes. The patch adds additional debug info. $ sudo engine-iso-uploader -v --iso-domain=ISO upload RHEL6.3-20120531.0-Server-x86_64-DVD1.iso Please provide the REST API username for oVirt Engine (CTRL+D to abort): admin@internal Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to abort): DEBUG: url(https://localhost:443/api) DEBUG: user(admin@internal) DEBUG: ca(/etc/pki/ovirt-engine/ca.pem) DEBUG: insecure(False) ERROR: Problem connecting to the REST API. Is the service available and does the CA certificate exist? Error: [ERROR]::oVirt API connection failure, Now we're getting to the good stuff as you can see that you are getting a connection refused. Questions for you: 1) Are you *certain* that 'https://localhost:443/api' is accessible from the local system, that it is the address of your oVirt engine, and is not being blocked by a FW? Easy test on the local box point your browser at that url. I have edited the tls port, it is not 443. It is 4301. I can access https://localhost:4301/api' 2) Are you certain that the CA is valid? To verify this you will need to issue a 'curl' statement and supply the CA. Example: curl -v -k -u $USER:$PASS --cacert /etc/pki/ovirt-engine/ca.pem -X GET -H 'Accept: application/xml' 'https://localhost:443/api/api/vms also: $ curl -v -k -u admin@internal:letmein! --cacert /etc/pki/ovirt-engine/ca.pem -X GET -H 'Accept: application/xml' 'https://localhost:4301/api/vms' is ok and I designate the tls port, now it can work. $ sudo engine-iso-uploader -rlocalhost:4301 -v --iso-domain=ISO upload Fedora-17-x86_64-DVD.iso Thank you. not sure how common are non-default ports. i guess on a local run, the tool can get these parameters from the engine config, but that's won't work for a remote run. ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] eclipse juno vs gwt
Hi, Just noticed that eclipse juno is adding @Ovewrride annotations to methods that are actually overriding something, like in many cases clone and equals methods in some of the classes. This is fine for the java compiler, but it in some cases the GWT compiler is not going to accept this annotation. E.g. if the return type is different than the method with same name in the superclass. Juno is doing this by default without asking, when saving the file. So be extra-careful when editing java classes if they are shared with GWT Laszlo ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] [help]how to get the CA certificate when uploader ISO
On 11/02/2012 04:01 AM, Sheldon wrote: On 11/01/2012 09:52 PM, Keith Robertson wrote: On 11/01/2012 05:23 AM, Sheldon wrote: On 10/31/2012 09:37 PM, Keith Robertson wrote: On 10/31/2012 01:40 AM, Sheldon wrote: I make a domain name ISO, Domain type is ISO, Storage Type is NFS, Format is V1 $ sudo engine-iso-uploader -v --iso-domain=ISO upload Fedora-17-x86_64-DVD.iso [sudo] password for ovirt: Please provide the REST API username for oVirt Engine (CTRL+D to abort): admin@internal Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to abort): ERROR: Problem connecting to the REST API. Is the service available and does the CA certificate exist? ERROR: 'NoneType' object is not iterable INFO: Use the -h option to see usage. Just to be clear the error in [1] is simply a symptom. It isn't the root cause. The root cause is quite possibly the CA certificate. I have created a patch in [2] that I'd appreciate if you could test as it will provide more debugging information about why the API creation is failing. Simply follow the steps in [3] Cheers, Keith [1] ERROR: 'NoneType' object is not iterable [2] http://gerrit.ovirt.org/8954 [3] Step 1: git clone http://gerrit.ovirt.org/p/ovirt-iso-uploader.git Step 2: Cherry pick the patch... git fetch git://gerrit.ovirt.org/ovirt-iso-uploader refs/changes/54/8954/2 git cherry-pick FETCH_HEAD Step 3: export APP_VERSION=3.0.0; export APP_RELEASE=1 Step 4: cd ovirt-iso-uploader Step 5: make Step 6: Notice the ovirt-iso-uploader*.rpm location in the STDOUT Step 7: yum install /path/to/ovirt-iso-uploader*.rpm still error. but different debug info. Yes. The patch adds additional debug info. $ sudo engine-iso-uploader -v --iso-domain=ISO upload RHEL6.3-20120531.0-Server-x86_64-DVD1.iso Please provide the REST API username for oVirt Engine (CTRL+D to abort): admin@internal Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to abort): DEBUG: url(https://localhost:443/api) DEBUG: user(admin@internal) DEBUG: ca(/etc/pki/ovirt-engine/ca.pem) DEBUG: insecure(False) ERROR: Problem connecting to the REST API. Is the service available and does the CA certificate exist? Error: [ERROR]::oVirt API connection failure, Now we're getting to the good stuff as you can see that you are getting a connection refused. Questions for you: 1) Are you *certain* that 'https://localhost:443/api' is accessible from the local system, that it is the address of your oVirt engine, and is not being blocked by a FW? Easy test on the local box point your browser at that url. I have edited the tls port, it is not 443. It is 4301. OK, here *here* is the problem. The ISO Uploader has been configured to use 'localhost:443' while you have customized it to 'localhost:4301'. You need to edit /etc/ovirt-engine/logcollector.conf and set the variable that tells the uploader which host/port combination to use. Note: The other 2 tools will have similar issues (ie. Log Collector and Image Uploader) and, they each have conf files in /etc/ovirt-engine. I can access https://localhost:4301/api' 2) Are you certain that the CA is valid? To verify this you will need to issue a 'curl' statement and supply the CA. Example: curl -v -k -u $USER:$PASS --cacert /etc/pki/ovirt-engine/ca.pem -X GET -H 'Accept: application/xml' 'https://localhost:443/api/api/vms also: $ curl -v -k -u admin@internal:letmein! --cacert /etc/pki/ovirt-engine/ca.pem -X GET -H 'Accept: application/xml' 'https://localhost:4301/api/vms' is ok and I designate the tls port, now it can work. $ sudo engine-iso-uploader -rlocalhost:4301 -v --iso-domain=ISO upload Fedora-17-x86_64-DVD.iso Thank you. [Errno 111] Connection refused DEBUG: Unable to get host and path information from API. -- Sheldon Feng(冯少合)shao...@linux.vnet.ibm.com IBM Linux Technology Center -- Sheldon Feng(冯少合)shao...@linux.vnet.ibm.com IBM Linux Technology Center ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] Time to bump version to 3.2.0?
I think that it is time to bump the version number in the POMs and in the RPM spec to 3.2.0: http://gerrit.ovirt.org/8993 In general I think that we should do this immediately after each release, bumping to the next expected version number. Thoughts? -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L. ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Time to bump version to 3.2.0?
Hi Juan, I think it is time to correct the version, but I was always wondering why we do not use the -SNAPSHOT versioning the maven developers designed? I think once we start pushing artifacts to public repositories, it will be a pain to have released version in our pom files. I think frontend and backend plugin developers will need this. http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-pom-syntax.html Laszlo - Original Message - From: Juan Hernandez jhern...@redhat.com To: engine-devel@ovirt.org Sent: Friday, November 2, 2012 2:42:10 PM Subject: [Engine-devel] Time to bump version to 3.2.0? I think that it is time to bump the version number in the POMs and in the RPM spec to 3.2.0: http://gerrit.ovirt.org/8993 In general I think that we should do this immediately after each release, bumping to the next expected version number. Thoughts? -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L. ___ 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
Re: [Engine-devel] Time to bump version to 3.2.0?
On 11/02/2012 02:54 PM, Laszlo Hornyak wrote: Hi Juan, I think it is time to correct the version, but I was always wondering why we do not use the -SNAPSHOT versioning the maven developers designed? I think once we start pushing artifacts to public repositories, it will be a pain to have released version in our pom files. I think frontend and backend plugin developers will need this. http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-pom-syntax.html Well, I don't have anything against that, but it will break some of the things that we currently do in the Makefile. We deploy artifacts to a local temporary directory during the build process, and we expect them to be named whatever-3.2.0.jar. If we use the SNAPSHOT capability then they will be named whatever-3.2.0-20121102.143802-1.jar and that breaks our build. I prefer not to touch the Makefile at this point, but I am open to fix it and use SNAPSHOT in the future. - Original Message - From: Juan Hernandez jhern...@redhat.com To: engine-devel@ovirt.org Sent: Friday, November 2, 2012 2:42:10 PM Subject: [Engine-devel] Time to bump version to 3.2.0? I think that it is time to bump the version number in the POMs and in the RPM spec to 3.2.0: http://gerrit.ovirt.org/8993 In general I think that we should do this immediately after each release, bumping to the next expected version number. Thoughts? -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L. ___ 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 -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L. ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] eclipse juno vs gwt
Sorry to follow up my own question, but can you give some specific cases where this would be a problem? Thanks! -Chris -Original Message- From: Morrissey, Christopher Sent: Friday, November 02, 2012 6:41 PM To: 'Laszlo Hornyak'; engine-devel Subject: RE: [Engine-devel] eclipse juno vs gwt Hi Laszlo, I have several methods that define the @Override annotation and return something different from the super class. I haven't had any problems compiling them in GWT. The return value does extend from the return value of the super class, although this is a requirement in Java as well so I'm not sure where the difference is. -Chris -Original Message- From: engine-devel-boun...@ovirt.org [mailto:engine-devel-boun...@ovirt.org] On Behalf Of Laszlo Hornyak Sent: Friday, November 02, 2012 6:19 AM To: engine-devel Subject: [Engine-devel] eclipse juno vs gwt Hi, Just noticed that eclipse juno is adding @Ovewrride annotations to methods that are actually overriding something, like in many cases clone and equals methods in some of the classes. This is fine for the java compiler, but it in some cases the GWT compiler is not going to accept this annotation. E.g. if the return type is different than the method with same name in the superclass. Juno is doing this by default without asking, when saving the file. So be extra-careful when editing java classes if they are shared with GWT Laszlo ___ 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
