[Users] cant add storage connection via api

Mon Sep 23 10:13:53 UTC 2013

On 09/23/2013 11:34 AM, Michael Pasternak wrote:
> On 09/23/2013 11:22 AM, Yuriy Demchenko wrote:
>> On 09/23/2013 12:13 PM, Alissa Bonas wrote:
>>>
>>> ----- Original Message -----
>>>> From: "Yuriy Demchenko" <demchenko.ya at gmail.com>
>>>> To: "Alissa Bonas" <abonas at redhat.com>
>>>> Cc: "Ofer Schreiber" <oschreib at redhat.com>, users at ovirt.org, "Michael Pasternak" <mpastern at redhat.com>, "Allon
>>>> Mureinik" <amureini at redhat.com>
>>>> Sent: Monday, September 23, 2013 10:57:12 AM
>>>> Subject: Re: [Users] cant add storage connection via api
>>>>
>>>> On 09/23/2013 11:43 AM, Alissa Bonas wrote:
>>>>> ----- Original Message -----
>>>>>> From: "Michael Pasternak" <mpastern at redhat.com>
>>>>>> To: "Yuriy Demchenko" <demchenko.ya at gmail.com>, "Alissa Bonas"
>>>>>> <abonas at redhat.com>, "Alon Bar-Lev"
>>>>>> <alonbl at redhat.com>
>>>>>> Cc: "Ofer Schreiber" <oschreib at redhat.com>, users at ovirt.org
>>>>>> Sent: Monday, September 23, 2013 10:22:49 AM
>>>>>> Subject: Re: [Users] cant add storage connection via api
>>>>>>
>>>>>> On 09/23/2013 10:05 AM, Yuriy Demchenko wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> url [1] (https://ovirt.spb.stone.local/api?rsdl) not working for me -
>>>>>>> gets
>>>>>>> http 500 error with "java.lang.NullPointerException"
>>>>>>>> java.lang.NullPointerException
>>>>>>>>     org.ovirt.engine.api.restapi.resource.BackendApiResource.addSystemVersion(BackendApiResource.java:358)
>>>>>>>>     org.ovirt.engine.api.restapi.resource.BackendApiResource.get(BackendApiResource.java:316)
>>>>>>>>        sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>     sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>     sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>        java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>     org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:155)
>>>>>>>>     org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:257)
>>>>>>>>     org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:222)
>>>>>>>>     org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:211)
>>>>>>>>     org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:525)
>>>>>>>>     org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:502)
>>>>>>>>     org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119)
>>>>>>>>     org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208)
>>>>>>>>     org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55)
>>>>>>>>     org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50)
>>>>>>>>        javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
>>>>>>> api page (without "?rsdl") opens just fine.
>>>>>> this is known issue caused by branding infra, i believe it was fixed in
>>>>>> the
>>>>>> following release (Alon correct me if i'm wrong)
>>>>>>
>>>>>>> Feature "manage storage connections" was mentioned in oVirt-3.3 release
>>>>>>> notes (http://www.ovirt.org/OVirt_3.3_release_notes), under "storage"
>>>>>>> section.
>>>>>> alissa?
>>>>> Storage connections management should be part of 3.3.
>>>>> Yuriy, when did you install the 3.3 and which exact build did you take?
>>>> That was upgrade from 3.2.2 to 3.3, did that on Tuesday 17, from 3.3
>>>> release repo (http://resources.ovirt.org/releases/3.3/rpm/EL/6/)
>>>>
>>>> ovirt-engine-3.3.0-4.el6     noarch     9/17/13 3:05:40 PM MUT
>>>> ovirt-engine-backend-3.3.0-4.el6     noarch     9/17/13 3:05:34 PM MUT
>>>> ovirt-engine-cli-3.2.0.12-1.el6     noarch     6/17/13 11:24:48 AM MUT
>>>> ovirt-engine-dbscripts-3.3.0-4.el6     noarch     9/17/13 3:05:39 PM MUT
>>>> ovirt-engine-lib-3.3.0-4.el6     noarch     9/17/13 2:57:00 PM MUT
>>>> ovirt-engine-restapi-3.3.0-4.el6     noarch     9/17/13 3:05:30 PM MUT
>>>> ovirt-engine-sdk-3.2.0.11-1.el6     noarch     6/17/13 11:24:33 AM MUT
>>>> ovirt-engine-setup-3.3.0-4.el6     noarch     9/17/13 2:57:03 PM MUT
>>>> ovirt-engine-tools-3.3.0-4.el6     noarch     9/17/13 3:05:35 PM MUT
>>>> ovirt-engine-userportal-3.3.0-4.el6     noarch     9/17/13 3:05:29 PM MUT
>>>> ovirt-engine-webadmin-portal-3.3.0-4.el6     noarch     9/17/13 3:06:01
>>>> PM MUT
>>>> ovirt-engine-websocket-proxy-3.3.0-4.el6     noarch     9/17/13 3:21:14
>>>> PM MUT
>>>> ovirt-host-deploy-1.1.1-1.el6     noarch     9/17/13 3:05:15 PM MUT
>>>> ovirt-host-deploy-java-1.1.1-1.el6     noarch     9/17/13 3:05:16 PM MUT
>>>> ovirt-image-uploader-3.3.0-1.el6     noarch     9/17/13 3:05:14 PM MUT
>>>> ovirt-iso-uploader-3.3.0-1.el6     noarch     9/17/13 3:05:17 PM MUT
>>>> ovirt-log-collector-3.3.0-1.el6     noarch     9/17/13 3:05:18 PM MUT
>>>>> Also, can you access the following url (just a regular GET request) ?
>>>>> https://ovirt.spb.stone.local/api/storageconnections
>>>> Yes I can. And I get list of all current connections there.
>>> OK, thank you.
>>> Please let me know 2 more things:
>>> 1. Is the connections subresource for a storage domain available?
>>> It is accessed in the link below with a GET request (please replace domainId placeholder with an id of one of your storage domains, doesn't matter which)
>>> https://ovirt.spb.stone.local/api/storagedomains/<domainId>/storageconnections
>> nope, no "storageconnections" under storagedomains/<id>/, only storage, link, type, master, description and name
>>> 2. In the main storage connections resource which you accessed via the below url - is a single connection's element named storage_connection or storage?
>>> https://ovirt.spb.stone.local/api/storageconnections
>> single element named "storage", not "storage_connection"
>
> so as i suspected this feature is yet not available in this drop,
> Ofer/Mike, when next oVirt release is planed?
>

i suggest to wait with this one to 3.3.1 which we rebased from master 
for, rather than backport these to 3.3.0.
I expect we'll want 2-3 weeks of stabilizing 3.3.1 before releasing it 
(maybe with test builds every week or something like that).