[Copied to stratos dev]
Hi Subbu,
I'm sorry for the delayed response. Actually this is not configurable at
the moment, if jclouds return both private and public IP addresses after
spawning an instance, cloud controller updates those values in the
topology. However I believe we need to make the process of assigning public
IP address configurable because not all cartridges need to have a public
IP.
Regarding what you have noticed, I guess the IaaS has not returned the
public IP address at the time the Complete Topology Event was triggered.
What Complete Topology Event does is that, it takes the current topology in
cloud controller periodically and publish it to the message broker.
Was the public IP address visible in IaaS for this member? If so what we
could do is to check the following info log cloud controller:
org.apache.stratos.cloud.controller.impl.CloudControllerServiceImpl.IpAllocator:
log.info("Retrieving Public IP Address : " + memberContext.toString());
Thanks
Imesh
On Tue, Mar 11, 2014 at 7:28 PM, Subbu Sundararajan (subbus) <
[email protected]> wrote:
> Hi Imesh,
>
> PublicIP in the CompleteTopologyEvent seems to be null when we
> subscribe and new VM is activated. Whereas the getMemberIp() in the Member,
> returns the floating IP which is for external network reachability.
>
> Is this configurable? Why the CompleteTopologyEvent doesn't get both the
> addresses? And how to get the eth0 (mgmt) interface IP (private) rather
> than the floating IP upon receiving topology events?
>
> Code snippet:
> System.out.println("Member IP:
> public=> " + member.getMemberPublicIp() + " private=> " +
> member.getMemberIp());
>
> Thanks,
> Subbu
>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PPMC Member, Apache Stratos
