You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by "Jeffrey Nguyen (JIRA)" <ji...@apache.org> on 2014/10/17 19:10:33 UTC

[jira] [Created] (STRATOS-895) Stratos only includes max of one private IP and one public IP in topology events

Jeffrey Nguyen created STRATOS-895:
--------------------------------------

             Summary: Stratos only includes max of one private IP and one public IP in topology events
                 Key: STRATOS-895
                 URL: https://issues.apache.org/jira/browse/STRATOS-895
             Project: Stratos
          Issue Type: Bug
          Components: Cloud Controller
    Affects Versions: 4.0.0
         Environment: Stratos 4.0.0, Openstack
            Reporter: Jeffrey Nguyen


Currently, Stratos supports multiple private IPs. It currently only support one public IP but that is another problem. Topology events currently only support a max of one private IP and one public IP. The events need to include all the IPs provisioned to the instance.

Please see code snippet below from CloudControllerServiceImpl.java.

                    // public ip 
                    if (node.getPublicAddresses() != null && 
                        node.getPublicAddresses().iterator().hasNext()) { 
                        ip = node.getPublicAddresses().iterator().next(); 
                        publicIp = ip; 
                        memberContext.setPublicIpAddress(ip); 
                        log.info("Retrieving Public IP Address : " + memberContext.toString()); 
                    } 

                    // private IP 
                    if (node.getPrivateAddresses() != null && 
                        node.getPrivateAddresses().iterator().hasNext()) { 
                        ip = node.getPrivateAddresses().iterator().next(); 
                        memberContext.setPrivateIpAddress(ip); 
                        log.info("Retrieving Private IP Address. " + memberContext.toString()); 
                    } 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)