[
https://issues.apache.org/jira/browse/DTACLOUD-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484106#comment-13484106
]
Michal Fojtik commented on DTACLOUD-348:
----------------------------------------
Hi,
So I finally looked on this issue and I prepared a patch that mostly copy what
the script in forum[1] does.
To test this, you need to specify a new network name using the 'network_name'
parameter in URL, when
creating a new VM.
So far I tried to test it using VSphere 4.x and the task started. However I got
into some datastore space issues
so I can't confirm it works as expected :-)
Patch: http://tracker.deltacloud.org/set/104
(also sent to list for review)
[1] http://communities.vmware.com/message/840944#840944
> Allow to change network configuration when creating an instance in Vsphere
> --------------------------------------------------------------------------
>
> Key: DTACLOUD-348
> URL: https://issues.apache.org/jira/browse/DTACLOUD-348
> Project: DeltaCloud
> Issue Type: New Feature
> Components: Server
> Reporter: Michal Fojtik
>
> Add new feature called 'network_name' for instance and allow to pass
> 'network_name' parameter when creating a new instance in Vsphere. This
> parameter will then change the CloneSpec for new VM and change the network
> adapter used by the template.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
