Re: [ovirt-users] Questions regarding neutron implementation for oVirt 3.5

2014-12-11 Thread Moti Asayag 


- Original Message -
 From: Andrew Brimer abri...@pearlnet.com
 To: Moti Asayag masa...@redhat.com
 Cc: users@ovirt.org
 Sent: Thursday, December 11, 2014 1:04:46 AM
 Subject: RE: Questions regarding neutron implementation for oVirt 3.5
 
 Hi Modi,
 
 In the discussion found at
 https://bugzilla.redhat.com/show_bug.cgi?id=1064231 Comment #12 states that
 the fedora Jackson package will not make a difference because the Jackson
 jar files pre-packaged in JBoss is what is actually used for this. Is that a
 true statement in your opinion? If so, how can I locate the appropriate jar
 and then what is the path in the oVirt Engine that I need to place
 that/those jar file(s) into?

Adding Juan to verify the suggested sequence, and to verify no better 
alternative is
available.

In order to upgrade the jackson module version, you should replace both the 
.jar files
and edit each module.xml of the corresponding jar file:

The files which should be replaced could be identified by:
$ find /usr/share/jboss-as-7.1.1.Final/modules -name jackson*.jar
/usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-jaxrs/main/jackson-jaxrs-1.9.2.jar
/usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-mapper-asl/main/jackson-mapper-asl-1.9.2.jar
/usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-xc/main/jackson-xc-1.9.2.jar
/usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-core-asl/main/jackson-core-asl-1.9.2.jar

Jar files can be downloaded from maven repository:
http://central.maven.org/maven2/org/codehaus/jackson/jackson-jaxrs/1.9.9/jackson-jaxrs-1.9.9.jar
http://central.maven.org/maven2/org/codehaus/jackson/jackson-xc/1.9.9/jackson-xc-1.9.9.jar
http://central.maven.org/maven2/org/codehaus/jackson/jackson-mapper-asl/1.9.9/jackson-mapper-asl-1.9.9.jar
http://central.maven.org/maven2/org/codehaus/jackson/jackson-core-asl/1.9.9/jackson-core-asl-1.9.9.jar

After the replacement, you should have the following:
/usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-jaxrs/main/jackson-jaxrs-1.9.9.jar
/usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-mapper-asl/main/jackson-mapper-asl-1.9.9.jar
/usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-xc/main/jackson-xc-1.9.9.jar
/usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-core-asl/main/jackson-core-asl-1.9.9.jar

Next, update the module.xml version from 1.9.2 to 1.9.9 files detected by:
$ find  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/ -name 
module.xml
/usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-jaxrs/main/module.xml:
resource-root path=jackson-jaxrs-1.9.2.jar/
/usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-mapper-asl/main/module.xml:
resource-root path=jackson-mapper-asl-1.9.2.jar/
/usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-xc/main/module.xml:
resource-root path=jackson-xc-1.9.2.jar/
/usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-core-asl/main/module.xml:
resource-root path=jackson-core-asl-1.9.2.jar/

for example, by editing them in place by:
$ find  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/ -name 
module.xml -exec sed 's/1.9.9/1.9.2/' {} \;

And verify the output is:
$ find  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/ -name 
module.xml | xargs grep 1\.9
/usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-jaxrs/main/module.xml:
resource-root path=jackson-jaxrs-1.9.9.jar/
/usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-mapper-asl/main/module.xml:
resource-root path=jackson-mapper-asl-1.9.9.jar/
/usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-xc/main/module.xml:
resource-root path=jackson-xc-1.9.9.jar/
/usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-core-asl/main/module.xml:
resource-root path=jackson-core-asl-1.9.9.jar/

Last thing is either rename the .jar.index file names to match the new version 
or remove them, so jboss will auto-generate them.
$ find  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/ -name 
.jar.index

 
 Am I on the right track? What is your advice?
 
 Kind Regards,
 
 Andrew Brimer
 
 -Original Message-
 From: Moti Asayag [mailto:masa...@redhat.com]
 Sent: Wednesday, December 10, 2014 4:16 PM
 To: Andrew Brimer
 Cc: users@ovirt.org
 Subject: Re: Questions regarding neutron implementation for oVirt 3.5
 
 
 
 - Original Message -
  From: Andrew Brimer abri...@pearlnet.com
  To: Moti Asayag masa...@redhat.com
  Sent: Wednesday, December 10, 2014 5:55:31 PM
  Subject: RE: Questions regarding neutron implementation for oVirt 3.5
  
  Hi Moti,
  
  Yes. I did not consider sending this out in a way that everyone would
  benefit, sorry. This is the first time that I have posted a question
  for oVirt

Re: [ovirt-users] Questions regarding neutron implementation for oVirt 3.5

2014-12-11 Thread Juan Hernández 
On 12/11/2014 09:56 AM, Moti Asayag wrote:
 
 
 - Original Message -
 From: Andrew Brimer abri...@pearlnet.com
 To: Moti Asayag masa...@redhat.com
 Cc: users@ovirt.org
 Sent: Thursday, December 11, 2014 1:04:46 AM
 Subject: RE: Questions regarding neutron implementation for oVirt 3.5

 Hi Modi,

 In the discussion found at
 https://bugzilla.redhat.com/show_bug.cgi?id=1064231 Comment #12 states that
 the fedora Jackson package will not make a difference because the Jackson
 jar files pre-packaged in JBoss is what is actually used for this. Is that a
 true statement in your opinion? If so, how can I locate the appropriate jar
 and then what is the path in the oVirt Engine that I need to place
 that/those jar file(s) into?
 
 Adding Juan to verify the suggested sequence, and to verify no better 
 alternative is
 available.
 
 In order to upgrade the jackson module version, you should replace both the 
 .jar files
 and edit each module.xml of the corresponding jar file:
 
 The files which should be replaced could be identified by:
 $ find /usr/share/jboss-as-7.1.1.Final/modules -name jackson*.jar
 /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-jaxrs/main/jackson-jaxrs-1.9.2.jar
 /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-mapper-asl/main/jackson-mapper-asl-1.9.2.jar
 /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-xc/main/jackson-xc-1.9.2.jar
 /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-core-asl/main/jackson-core-asl-1.9.2.jar
 
 Jar files can be downloaded from maven repository:
 http://central.maven.org/maven2/org/codehaus/jackson/jackson-jaxrs/1.9.9/jackson-jaxrs-1.9.9.jar
 http://central.maven.org/maven2/org/codehaus/jackson/jackson-xc/1.9.9/jackson-xc-1.9.9.jar
 http://central.maven.org/maven2/org/codehaus/jackson/jackson-mapper-asl/1.9.9/jackson-mapper-asl-1.9.9.jar
 http://central.maven.org/maven2/org/codehaus/jackson/jackson-core-asl/1.9.9/jackson-core-asl-1.9.9.jar
 
 After the replacement, you should have the following:
 /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-jaxrs/main/jackson-jaxrs-1.9.9.jar
 /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-mapper-asl/main/jackson-mapper-asl-1.9.9.jar
 /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-xc/main/jackson-xc-1.9.9.jar
 /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-core-asl/main/jackson-core-asl-1.9.9.jar
 
 Next, update the module.xml version from 1.9.2 to 1.9.9 files detected by:
 $ find  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/ -name 
 module.xml
 /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-jaxrs/main/module.xml:
 resource-root path=jackson-jaxrs-1.9.2.jar/
 /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-mapper-asl/main/module.xml:
 resource-root path=jackson-mapper-asl-1.9.2.jar/
 /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-xc/main/module.xml:
 resource-root path=jackson-xc-1.9.2.jar/
 /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-core-asl/main/module.xml:
 resource-root path=jackson-core-asl-1.9.2.jar/
 
 for example, by editing them in place by:
 $ find  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/ -name 
 module.xml -exec sed 's/1.9.9/1.9.2/' {} \;
 
 And verify the output is:
 $ find  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/ -name 
 module.xml | xargs grep 1\.9
 /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-jaxrs/main/module.xml:
 resource-root path=jackson-jaxrs-1.9.9.jar/
 /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-mapper-asl/main/module.xml:
 resource-root path=jackson-mapper-asl-1.9.9.jar/
 /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-xc/main/module.xml:
 resource-root path=jackson-xc-1.9.9.jar/
 /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-core-asl/main/module.xml:
 resource-root path=jackson-core-asl-1.9.9.jar/
 
 Last thing is either rename the .jar.index file names to match the new 
 version or remove them, so jboss will auto-generate them.
 $ find  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/ -name 
 .jar.index
 

If you are using Fedora 20 then you are also using the
ovirt-engine-jboss-as package. That is a repackaging of JBoss AS 7.1.1
needed because Fedora 20 ships with WildFly, and we don't support it.
What is relevant for you is that the location of the files is not
/usr/share/jboss-as-7.1.1.Final but /usr/share/ovirt-engine-jboss-as.
Other than that the instructions provided by Moti are correct. However
the modifications of those files will be lost when the
ovirt-engine-jboss-as package is updated (unlikely). I'd suggest to
create a new module from scratch, in the
/usr/share/ovirt-engine/modules/common directory. I

Re: [ovirt-users] Questions regarding neutron implementation for oVirt 3.5

2014-12-11 Thread Andrew Brimer 
I have additional log information.

2014-12-10 20:44:25,531 INFO  
[org.ovirt.engine.core.bll.provider.network.AddNetworkOnProviderCommand] 
(ajp--127.0.0.1-8702-8) [7e632508] Running command: AddNetworkOnProviderCommand 
internal: false. Entities affected :  ID: 3713edec-cd32-4730-9647-e349c8e7e4eb 
Type: StoragePoolAction group CREATE_STORAGE_POOL_NETWORK with role type ADMIN
2014-12-10 20:44:25,793 INFO  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(ajp--127.0.0.1-8702-8) [7e632508] Correlation ID: 7e632508, Call Stack: null, 
Custom Event ID: -1, Message: Network extnet was added to Data Center: Zen
2014-12-10 20:44:25,823 INFO  
[org.ovirt.engine.core.bll.network.vm.AddVnicProfileCommand] 
(ajp--127.0.0.1-8702-10) [63250a8] Running command: AddVnicProfileCommand 
internal: false. Entities affected :  ID: 6bb8a6ef-3499-46a5-9a45-4cb4196de990 
Type: NetworkAction group CREATE_NETWORK_VNIC_PROFILE with role type ADMIN
2014-12-10 20:44:25,837 INFO  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(ajp--127.0.0.1-8702-10) [63250a8] Correlation ID: 63250a8, Call Stack: null, 
Custom Event ID: -1, Message: VM network interface profile extnet was added to 
network extnet in Data Center: Zen. (User: admin)
2014-12-10 20:44:25,840 INFO  
[org.ovirt.engine.core.bll.provider.network.AddSubnetToProviderCommand] 
(ajp--127.0.0.1-8702-8) [7fb592ce] Running command: AddSubnetToProviderCommand 
internal: false. Entities affected :  ID: aaa0----123456789aaa 
Type: SystemAction group CREATE_STORAGE_POOL with role type ADMIN
2014-12-10 20:44:25,852 INFO  
[org.ovirt.engine.core.bll.network.cluster.AttachNetworkToVdsGroupCommand] 
(org.ovirt.thread.pool-8-thread-50) [6a02263f] Running command: 
AttachNetworkToVdsGroupCommand internal: false. Entities affected :  ID: 
6bb8a6ef-3499-46a5-9a45-4cb4196de990 Type: NetworkAction group 
ASSIGN_CLUSTER_NETWORK with role type ADMIN
2014-12-10 20:44:25,870 INFO  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(org.ovirt.thread.pool-8-thread-50) [6a02263f] Correlation ID: 6a02263f, Call 
Stack: null, Custom Event ID: -1, Message: Network extnet attached to Cluster 
Zen
2014-12-10 20:44:26,086 ERROR 
[org.ovirt.engine.core.bll.provider.network.AddSubnetToProviderCommand] 
(ajp--127.0.0.1-8702-8) [7fb592ce] Command 
org.ovirt.engine.core.bll.provider.network.AddSubnetToProviderCommand throw Vdc 
Bll exception. With error message VdcBLLException: (Failed with error 
PROVIDER_FAILURE and code 5050)
2014-12-10 20:44:26,093 ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(ajp--127.0.0.1-8702-8) [7fb592ce] Correlation ID: 7fb592ce, Call Stack: null, 
Custom Event ID: -1, Message: Failed to add subnet extsub on provider neutron. 
(User: admin)

-Original Message-
From: Moti Asayag [mailto:masa...@redhat.com] 
Sent: Wednesday, December 10, 2014 10:28 AM
To: Andrew Brimer
Subject: Re: Questions regarding neutron implementation for oVirt 3.5

Hi Andrew,

Generally, it is preferable to send ovirt related questions to users@ovirt.org 
for the benefit of other community members.

If no concerns, please include it in your next reply's cc.

Regarding your issue - see inline.

- Original Message -
 From: Andrew Brimer abri...@pearlnet.com
 To: masa...@redhat.com
 Sent: Wednesday, December 10, 2014 4:52:14 PM
 Subject: Questions regarding neutron implementation for oVirt 3.5
 
 Good Morning Moti,
 
  
 
 I am hoping that you may be able to help me out if you have a little 
 time Sir.
 
  
 
 I have followed your instructions (youtube and NeutronVirtualAppliance
 document) for integrating Neutron into my oVirt 3.5 system and I am 
 running into some issues when attempting to create a subnet.
 

Were you able to verify connectivity to the neutron appliance after it was 
added to the ovirt-engine as shown on 
https://www.youtube.com/watch?feature=player_detailpagev=naLFSFwHI94#t=510? 

Could you post the /var/log/ovirt-engine/engine.log ?

Thanks,
Moti

  
 
 Networks-extent-Subnets-New
 
 Network: extent
 
 Name: extsubtest
 
 CIDR:10.0.9.0/24
 
 [OK]
 
  
 
  
 
  
 
 Returns: Error while executing action Add Subnet to Provider: Failed 
 to communicate with the external provider.
 
  
 
  
 
  
 
 On the Neutron machine:
 
 neutron net-list shows 'extnet'
 
 neutron subnet-list shows 'extsubtest'
 
 neutron router-list shows nothing
 
  
 
 oVirt Visor 1 is the host that I used when following your instructions 
 and Visor 2 is the additional host added per your instructions towards 
 the end of the video.
 
  
 
 I really appreciate any help that you can provide, I only have Neutron 
 integration to complete and will then have a fully working oVirt 3.5 
 stack running.
 
  
 
 Kind Regards,
 
  
 
 Andrew Brimer
 
 Chief Systems Architect
 
 PearlNet, LLC
 
 abri...@pearlnet.com
 
 770-352-0111 (office)
 
 678-852-8808 (cell)
 
  
 
 The following describes my

Re: [ovirt-users] Questions regarding neutron implementation for oVirt 3.5

2014-12-11 Thread Andrew Brimer 
Hi Modi,

In the discussion found at https://bugzilla.redhat.com/show_bug.cgi?id=1064231 
Comment #12 states that the fedora Jackson package will not make a difference 
because the Jackson jar files pre-packaged in JBoss is what is actually used 
for this. Is that a true statement in your opinion? If so, how can I locate the 
appropriate jar and then what is the path in the oVirt Engine that I need to 
place that/those jar file(s) into?

Am I on the right track? What is your advice?

Kind Regards,

Andrew Brimer

-Original Message-
From: Moti Asayag [mailto:masa...@redhat.com] 
Sent: Wednesday, December 10, 2014 4:16 PM
To: Andrew Brimer
Cc: users@ovirt.org
Subject: Re: Questions regarding neutron implementation for oVirt 3.5



- Original Message -
 From: Andrew Brimer abri...@pearlnet.com
 To: Moti Asayag masa...@redhat.com
 Sent: Wednesday, December 10, 2014 5:55:31 PM
 Subject: RE: Questions regarding neutron implementation for oVirt 3.5
 
 Hi Moti,
 
 Yes. I did not consider sending this out in a way that everyone would 
 benefit, sorry. This is the first time that I have posted a question 
 for oVirt and just saw your email address in the instructions document 
 and quickly fired off an email. I will post to users@ovirt.org for all 
 future questions, I would love to participate in any way possible to 
 help you guys (and those of us who rely on your efforts) move things 
 forward. If you would like for me to forward the next (or this one) 
 message to users@ovirt.org I would be very happy to.
 

Done. I think this will help other users which might face the same problem.

 To answer your question regarding testing connectivity, yes I pressed 
 the test button and was provided the success message. In addition to 
 that, when I create a net and subnet in oVirt I am able to query neutron and 
 find them.
 I can also create a net in neutron (neutron net-create) and import it 
 into oVirt. It seems that the two systems are communicating but that 
 somewhere along the way an error is halting your workflow (see the 
 snippit from the
 /var/log/ovirt-engine/engine.log)
 

The cause for the error is documented in bug 1064231 [1] as a result of a buggy 
jackson package version which is delivered by jboss. The bug wasn't fixed for 
f20, and it appears since ovirt-engine-3.4. 

Although requests are being sent to the neutron server and being processed 
successfully, retrieving the subnets from neutron fails due to the bug in 
jackson.

Local upgrade of the jackson package under jboss-as-7.1 to 1.9.9 or using 
jboss-eap-6.3 which is shipped with jackson-1.9.9 will solve this issue.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1064231


 Output (subset) of the /var/log/ovirt-engine/engine.log:
 
 2014-12-10 14:41:23,623 ERROR
 [org.ovirt.engine.core.bll.provider.network.GetExternalSubnetsOnProvid
 erByNetworkQuery]
 (ajp--127.0.0.1-8702-3) Query 
 GetExternalSubnetsOnProviderByNetworkQuery
 failed. Exception message is org.codehaus.jackson.map.JsonMappingException:
 Parameter #0 type for factory method ([method valueOf, annotations:
 {interface
 org.codehaus.jackson.annotate.JsonCreator=@org.codehaus.jackson.annota
 te.JsonCreator()}]) not suitable, must be java.lang.String :
 org.jboss.resteasy.spi.ReaderException:
 org.codehaus.jackson.map.JsonMappingException: Parameter #0 type for 
 factory method ([method valueOf, annotations: {interface
 org.codehaus.jackson.annotate.JsonCreator=@org.codehaus.jackson.annota
 te.JsonCreator()}]) not suitable, must be java.lang.String:
 org.jboss.resteasy.spi.ReaderException:
 org.codehaus.jackson.map.JsonMappingException: Parameter #0 type for 
 factory method ([method valueOf, annotations: {interface
 org.codehaus.jackson.annotate.JsonCreator=@org.codehaus.jackson.annota
 te.JsonCreator()}]) not suitable, must be java.lang.String
 at
 
 org.jboss.resteasy.client.core.BaseClientResponse.readFrom(BaseClientResponse.java:469)
 [resteasy-jaxrs-2.3.2.Final.jar:]
 at
 
 org.jboss.resteasy.client.core.BaseClientResponse.getEntity(BaseClientResponse.java:377)
 [resteasy-jaxrs-2.3.2.Final.jar:]
 at
 
 org.jboss.resteasy.client.core.BaseClientResponse.getEntity(BaseClientResponse.java:350)
 [resteasy-jaxrs-2.3.2.Final.jar:]
 at
 
 org.jboss.resteasy.client.core.BaseClientResponse.getEntity(BaseClientResponse.java:344)
 [resteasy-jaxrs-2.3.2.Final.jar:]
 at
 
 com.woorea.openstack.connector.RESTEasyResponse.getEntity(RESTEasyResponse.java:25)
 [resteasy-connector.jar:]
 at
 
 com.woorea.openstack.base.client.OpenStackClient.execute(OpenStackClient.java:67)
 [openstack-client.jar:]
 at
 
 com.woorea.openstack.base.client.OpenStackRequest.execute(OpenStackRequest.java:98)
 [openstack-client.jar:]
 at

[ovirt-users] Questions regarding neutron implementation for oVirt 3.5

2014-12-11 Thread Andrew Brimer 


-Original Message-
From: Andrew Brimer 
Sent: Wednesday, December 10, 2014 10:56 AM
To: 'Moti Asayag'
Subject: RE: Questions regarding neutron implementation for oVirt 3.5

Hi Moti,

Yes. I did not consider sending this out in a way that everyone would benefit, 
sorry. This is the first time that I have posted a question for oVirt and just 
saw your email address in the instructions document and quickly fired off an 
email. I will post to users@ovirt.org for all future questions, I would love to 
participate in any way possible to help you guys (and those of us who rely on 
your efforts) move things forward. If you would like for me to forward the next 
(or this one) message to users@ovirt.org I would be very happy to.

To answer your question regarding testing connectivity, yes I pressed the test 
button and was provided the success message. In addition to that, when I create 
a net and subnet in oVirt I am able to query neutron and find them. I can also 
create a net in neutron (neutron net-create) and import it into oVirt. It seems 
that the two systems are communicating but that somewhere along the way an 
error is halting your workflow (see the snippit from the 
/var/log/ovirt-engine/engine.log) 

Output (subset) of the /var/log/ovirt-engine/engine.log:

2014-12-10 14:41:23,623 ERROR 
[org.ovirt.engine.core.bll.provider.network.GetExternalSubnetsOnProviderByNetworkQuery]
 (ajp--127.0.0.1-8702-3) Query GetExternalSubnetsOnProviderByNetworkQuery 
failed. Exception message is org.codehaus.jackson.map.JsonMappingException: 
Parameter #0 type for factory method ([method valueOf, annotations: {interface 
org.codehaus.jackson.annotate.JsonCreator=@org.codehaus.jackson.annotate.JsonCreator()}])
 not suitable, must be java.lang.String : 
org.jboss.resteasy.spi.ReaderException: 
org.codehaus.jackson.map.JsonMappingException: Parameter #0 type for factory 
method ([method valueOf, annotations: {interface 
org.codehaus.jackson.annotate.JsonCreator=@org.codehaus.jackson.annotate.JsonCreator()}])
 not suitable, must be java.lang.String: 
org.jboss.resteasy.spi.ReaderException: 
org.codehaus.jackson.map.JsonMappingException: Parameter #0 type for factory 
method ([method valueOf, annotations: {interface 
org.codehaus.jackson.annotate.JsonCreator=@org.code
 haus.jackson.annotate.JsonCreator()}]) not suitable, must be java.lang.String
at 
org.jboss.resteasy.client.core.BaseClientResponse.readFrom(BaseClientResponse.java:469)
 [resteasy-jaxrs-2.3.2.Final.jar:]
at 
org.jboss.resteasy.client.core.BaseClientResponse.getEntity(BaseClientResponse.java:377)
 [resteasy-jaxrs-2.3.2.Final.jar:]
at 
org.jboss.resteasy.client.core.BaseClientResponse.getEntity(BaseClientResponse.java:350)
 [resteasy-jaxrs-2.3.2.Final.jar:]
at 
org.jboss.resteasy.client.core.BaseClientResponse.getEntity(BaseClientResponse.java:344)
 [resteasy-jaxrs-2.3.2.Final.jar:]
at 
com.woorea.openstack.connector.RESTEasyResponse.getEntity(RESTEasyResponse.java:25)
 [resteasy-connector.jar:]
at 
com.woorea.openstack.base.client.OpenStackClient.execute(OpenStackClient.java:67)
 [openstack-client.jar:]
at 
com.woorea.openstack.base.client.OpenStackRequest.execute(OpenStackRequest.java:98)
 [openstack-client.jar:]
at 
org.ovirt.engine.core.bll.provider.network.openstack.OpenstackNetworkProviderProxy.getAllSubnets(OpenstackNetworkProviderProxy.java:132)
 [bll.jar:]
at 
org.ovirt.engine.core.bll.provider.network.GetExternalSubnetsOnProviderByNetworkQuery.executeQueryCommand(GetExternalSubnetsOnProviderByNetworkQuery.java:28)
 [bll.jar:]
at 
org.ovirt.engine.core.bll.QueriesCommandBase.executeCommand(QueriesCommandBase.java:73)
 [bll.jar:]
at 
org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:31) 
[dal.jar:]
at org.ovirt.engine.core.bll.Backend.runQueryImpl(Backend.java:492) 
[bll.jar:]
at org.ovirt.engine.core.bll.Backend.runQuery(Backend.java:466) 
[bll.jar:]
at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) 
[:1.7.0_71]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 [rt.jar:1.7.0_71]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_71]
at 
org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72)
 [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at 
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) 
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at 
org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:374)
 [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at 
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:114)
 [jboss-as-weld-7.1.1.Final.jar:7.1.1.Final]
at

Re: [ovirt-users] Questions regarding neutron implementation for oVirt 3.5

2014-12-11 Thread Andrew Brimer 
That did the trick guys. Thanks so much to both of you for all of your help. I 
may return with some additional questions regarding placing 
neutron/keystone/rabbit on a separate blade using devstack or something to 
quickly implement. If you have any comments please don't hesitate to let me 
know if you think that I would be going down a bad path or such.

Again, thanks for everything.

Regards,
Andrew Brimer

-Original Message-
From: Moti Asayag [mailto:masa...@redhat.com] 
Sent: Thursday, December 11, 2014 5:49 AM
To: Juan Hernández
Cc: Andrew Brimer; users@ovirt.org
Subject: Re: [ovirt-users] Questions regarding neutron implementation for oVirt 
3.5



- Original Message -
 From: Juan Hernández jhern...@redhat.com
 To: Moti Asayag masa...@redhat.com, Andrew Brimer 
 abri...@pearlnet.com
 Cc: users@ovirt.org
 Sent: Thursday, December 11, 2014 11:23:37 AM
 Subject: Re: [ovirt-users] Questions regarding neutron implementation 
 for oVirt 3.5
 
 On 12/11/2014 09:56 AM, Moti Asayag wrote:
  
  
  - Original Message -
  From: Andrew Brimer abri...@pearlnet.com
  To: Moti Asayag masa...@redhat.com
  Cc: users@ovirt.org
  Sent: Thursday, December 11, 2014 1:04:46 AM
  Subject: RE: Questions regarding neutron implementation for oVirt 
  3.5
 
  Hi Modi,
 
  In the discussion found at
  https://bugzilla.redhat.com/show_bug.cgi?id=1064231 Comment #12 
  states that the fedora Jackson package will not make a difference 
  because the Jackson jar files pre-packaged in JBoss is what is 
  actually used for this. Is that a true statement in your opinion? 
  If so, how can I locate the appropriate jar and then what is the 
  path in the oVirt Engine that I need to place that/those jar 
  file(s) into?
  
  Adding Juan to verify the suggested sequence, and to verify no 
  better alternative is available.
  
  In order to upgrade the jackson module version, you should replace 
  both the .jar files and edit each module.xml of the corresponding 
  jar file:
  
  The files which should be replaced could be identified by:
  $ find /usr/share/jboss-as-7.1.1.Final/modules -name jackson*.jar
  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson
  -jaxrs/main/jackson-jaxrs-1.9.2.jar
  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson
  -mapper-asl/main/jackson-mapper-asl-1.9.2.jar
  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson
  -xc/main/jackson-xc-1.9.2.jar 
  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson
  -core-asl/main/jackson-core-asl-1.9.2.jar
  
  Jar files can be downloaded from maven repository:
  http://central.maven.org/maven2/org/codehaus/jackson/jackson-jaxrs/1
  .9.9/jackson-jaxrs-1.9.9.jar 
  http://central.maven.org/maven2/org/codehaus/jackson/jackson-xc/1.9.
  9/jackson-xc-1.9.9.jar 
  http://central.maven.org/maven2/org/codehaus/jackson/jackson-mapper-
  asl/1.9.9/jackson-mapper-asl-1.9.9.jar
  http://central.maven.org/maven2/org/codehaus/jackson/jackson-core-as
  l/1.9.9/jackson-core-asl-1.9.9.jar
  
  After the replacement, you should have the following:
  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson
  -jaxrs/main/jackson-jaxrs-1.9.9.jar
  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson
  -mapper-asl/main/jackson-mapper-asl-1.9.9.jar
  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson
  -xc/main/jackson-xc-1.9.9.jar 
  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson
  -core-asl/main/jackson-core-asl-1.9.9.jar
  
  Next, update the module.xml version from 1.9.2 to 1.9.9 files 
  detected
  by:
  $ find  
  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/ -name 
  module.xml
  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-jaxrs/main/module.xml:
  resource-root path=jackson-jaxrs-1.9.2.jar/
  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-mapper-asl/main/module.xml:
  resource-root path=jackson-mapper-asl-1.9.2.jar/
  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-xc/main/module.xml:
  resource-root path=jackson-xc-1.9.2.jar/
  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-core-asl/main/module.xml:
  resource-root path=jackson-core-asl-1.9.2.jar/
  
  for example, by editing them in place by:
  $ find  
  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/ -name 
  module.xml -exec sed 's/1.9.9/1.9.2/' {} \;
  
  And verify the output is:
  $ find  
  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/ -name 
  module.xml | xargs grep 1\.9
  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-jaxrs/main/module.xml:
  resource-root path=jackson-jaxrs-1.9.9.jar/
  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-mapper-asl/main/module.xml:
  resource-root path=jackson-mapper-asl-1.9.9.jar/
  /usr/share/jboss-as-7.1.1.Final/modules/org/codehaus/jackson/jackson-xc