e code or the class
> location of this.
>
>
>
>
>
> Thanks !
>
>
>
>
>
> On Tue, Nov 4, 2014 at 2:10 PM, Zack Shoylev
> wrote:
>
>
>
>
>
> We have support for the floating ip api extension for neutron in jclouds
> 1.8.1.
>
>
>
>
>
>
1.8.1
-Zack
From: Manula Chathurika Thantriwatte [manu...@wso2.com]
Sent: Tuesday, November 04, 2014 2:58 AM
To: user@jclouds.apache.org
Subject: Re: Associate floating ip to a specified network interface support in
JClouds 1.8.1
Hi Zack,
Thanks for the confirmation. Can you
> *From:* Manula Chathurika Thantriwatte [manu...@wso2.com]
> *Sent:* Tuesday, November 04, 2014 12:39 AM
> *To:* user@jclouds.apache.org
> *Subject:* Associate floating ip to a specified network interface support
> in JClouds 1.8.1
>
> Hi All,
>
> According t
interface support in
JClouds 1.8.1
Hi All,
According to the mail thread in [1] and JIRA in [2], previous JCloud version
didn't support to associate floating IP to a specified network interface. Is
this feature available in JClouds latest release 1.8.1.
[1]
http://mail-archives.apach
Hi All,
According to the mail thread in [1] and JIRA in [2], previous JCloud
version didn't support to associate floating IP to a specified network
interface. Is this feature available in JClouds latest release 1.8.1.
[1]
http://mail-archives.apache.org/mod_mbox/jclouds-user/201408
: Thursday, August 21, 2014 7:17 AM
To: user@jclouds.apache.org
Cc: d...@jclouds.apache.org
Subject: Re: Associate floating ip to a specified network interface
That's right, but you'll have to also rename the "@PayloadParam" from
pool to address.
On 21 August 2014 14:07, Udara L
That's right, but you'll have to also rename the "@PayloadParam" from
pool to address.
On 21 August 2014 14:07, Udara Liyanage wrote:
> Hi Ignasi,
>
> I am trying to figure out how the response is generated by looking at method
> declaration and know requests.
>
> For instance, if I change the me
Hi Ignasi,
I am trying to figure out how the response is generated by looking at
method declaration and know requests.
For instance, if I change the method as
@Payload("%7B\"addFloatingIp\":%7B\"address\":\"{address}\",\"interface\":\"{interface}\"%7D%7D")
FloatingIP allocateFromPool(@PayloadPar
Hi Udara,
There is no implementation for the API interfaces. jclouds dynamically
generates the HTTP requests on the fly, based on the annotations of
the invoked method. Adding an operation to the FloatingIpApi should
only require to add the method to the interface with the corresponding
annotation
Hi Zack,
Thanks for the confirmation. Could you please point me to the place where
REST API call is made to the Openstack so I would give a try patching
Jclouds. I had a look at the code, I only found FloatingIpAPI.java which is
the interface. I could not find the place where REST API call is made
Hi,
Created a jira for this [1]
[1] https://issues.apache.org/jira/browse/JCLOUDS-682
On Wed, Aug 20, 2014 at 10:53 PM, Udara Liyanage wrote:
> Hi,
>
> I create instances with multiple network interfaces. However when I
> associate an floating ip to the instance as below, floating ip is alwa
I don't think this particular neutron extension is supported right now.
Hopefully we can add support for it soon!
From: Udara Liyanage [ud...@wso2.com]
Sent: Wednesday, August 20, 2014 12:23 PM
To: user@jclouds.apache.org
Subject: Associate floating ip
Hi,
I create instances with multiple network interfaces. However when I
associate an floating ip to the instance as below, floating ip is always
get allocated to the first interface of the instance.
api.addToServer(ip, server-id);
How do I get the floating ip assigned to the second or an interfa
13 matches
Mail list logo
