incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chip Childers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-645) add/remove network on VM
Date Tue, 08 Jan 2013 19:24:12 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547141#comment-13547141
] 

Chip Childers commented on CLOUDSTACK-645:
------------------------------------------

Marcus,

Can you please start a thread on the dev list to propose this?  Also, at least a minimal func
spec is needed.  Last, what feature branch are you going to use (or will it be via reviewboard
submissions)?

Thank you!
                
> add/remove network on VM
> ------------------------
>
>                 Key: CLOUDSTACK-645
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-645
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>            Reporter: Marcus Sorensen
>            Assignee: Marcus Sorensen
>             Fix For: 4.1.0
>
>
> We would like the ability to move VMs between networks and/or reconfigure a VM's network,
in order to accomodate hybrid/traditional server loads. We've implemented 3 API calls and
would like to submit these for the community to edit/adjust/approve. The three calls are 'addNicToVirtualMachine','removeNicFromVirtualMachine',
and 'updateDefaultNicForVirtualMachine'. One provides a VM Id and a network id, default Nics
cannot be removed. The names might need adjustment to better fit the API, perhaps 'attachNetworkToVirtualMachine',
etc.  Looking for feedback, advice, potential pitfalls... does a feature branch need to be
created or just a review?
> Release Planning:
> Dev list discussion: unknown
> Functional spec: unknown
> Feature branch: unknown

--
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

Mime
View raw message