You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Ignasi Barrera (JIRA)" <ji...@apache.org> on 2015/05/19 21:46:59 UTC

[jira] [Resolved] (JCLOUDS-896) Replace the GCETemplateOptions#network by the TemplateOptions#networks option

     [ https://issues.apache.org/jira/browse/JCLOUDS-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ignasi Barrera resolved JCLOUDS-896.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

Addressed in commit:
http://git-wip-us.apache.org/repos/asf/jclouds-labs-google/commit/cd16d593

> Replace the GCETemplateOptions#network by the TemplateOptions#networks option
> -----------------------------------------------------------------------------
>
>                 Key: JCLOUDS-896
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-896
>             Project: jclouds
>          Issue Type: Sub-task
>          Components: jclouds-labs-google
>    Affects Versions: 1.9.0
>            Reporter: Ignasi Barrera
>              Labels: google-compute-engine
>             Fix For: 2.0.0
>
>
> Currently the GCETemplateOptions provide a way to specify the URI of a network where the VMs will be attached. The portable TemplateOptions already provides that property as a list of Strings, so the provider-specific options should be removed and the portable one should be used instead:
> * If a VM can be attached to multiple networks, then the adapter should honor the property and attach the VM to all them.
> * If not, we should validate the options and fail giving a proper feedback to the user.
> * If no network is explicitly provided, the VMs will be attached to the default network, as suggested in https://github.com/jclouds/jclouds-labs-google/pull/138



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