[
https://issues.apache.org/jira/browse/STRATOS-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938776#comment-13938776
]
Jeffrey Nguyen commented on STRATOS-180:
----------------------------------------
Hi Nirmal, I noticed in your commit for this JIRA that in the code for the AWS
EC2, you're also using NovaTemplateOptions in AWSEC2Iaas.buildTemplate()
(snippet below).
Is this because both AWS EC2 and Nova both use the same payload for attaching
multiple networks? I'm asking because for STRATOS-507, the JSON format for
defining multiple networks has changed as mentioned on the comments section, so
this code needs to change too.
if
(iaasInfo.getProperty(CloudControllerConstants.NETWORK_INTERFACES) != null) {
String networksStr =
iaasInfo.getProperty(CloudControllerConstants.NETWORK_INTERFACES);
String[] networksArray =
networksStr.split(CloudControllerConstants.ENTRY_SEPARATOR);
template.getOptions()
.as(NovaTemplateOptions.class).networks(Arrays.asList(networksArray));
}
> Support to define multiple networks for cartridges
> --------------------------------------------------
>
> Key: STRATOS-180
> URL: https://issues.apache.org/jira/browse/STRATOS-180
> Project: Stratos
> Issue Type: Sub-task
> Components: Cloud Controller
> Affects Versions: 4.0.0 M5
> Reporter: Reka Thirunavukkarasu
> Assignee: Nirmal Fernando
> Fix For: 4.0.0 Alpha
>
>
> In the current environment, when we define multiple networks, from the jcloud
> one random network got chosen when starting an instance. If we provide a way
> to provide a correct network when starting an instance, then the instance
> will be bound to the correct interface
--
This message was sent by Atlassian JIRA
(v6.2#6252)
