I've just created a patch: https://github.com/jclouds/jclouds/pull/948
Could you build the pull request branch and test with it?
On 20 April 2016 at 16:49, Ignasi Barrera wrote:
> So teh cause is indeed the missing namespace field in the extensions.
>
> Other APIs work for you because the Port a
So teh cause is indeed the missing namespace field in the extensions.
Other APIs work for you because the Port and Subnet APIs are not
OpenStack extensions but apis that already come with Neutron by
default. Mind opening a JIRA issue so we can relax jclouds
restrictions, and match the extensions j
Hi all,
I have enabled the log and this ( see attached files) is what is logged
from jclouds when I try to create a Router on a test devstack. What is
strange is that i can interact with neutron for other activities (as list
networks, create network, create subnet).
Let me know and thank you in
It looks like the extension api is returning some extensions without
the namespace field, and jclouds expects it to always be present [1]
(jclouds binds extension namespaces and aliases to Java API classes
and uses that to resolve which api to return for each extension).
Could you enable the "jclo
Hi Ignasi,
Me and Antonio are co-worker in these activity than I can answer for him at
your questions:
- the Openstack Version where we try to accede is a Devstack based on
ovn-networking developing branch.
- We have tried also to use the jclouds 2.0.0-SNAPSHOT but with same
result.
D
Hi Antonio,
I've been using the RouterApi with 1.9.1 without issues for a while.
* Which version of Neutron are you connecting to?
* Do you experience the same failure if you use the jclouds 2.0.0-SNAPSHOT?
I.
On 13 April 2016 at 18:53, Antonio Galletta wrote:
> Hi we are using Jclouds v. 1.9
