[
https://issues.apache.org/jira/browse/CLOUDSTACK-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561009#comment-13561009
]
Marcus Sorensen edited comment on CLOUDSTACK-1043 at 1/23/13 7:43 PM:
----------------------------------------------------------------------
One thing I don't understand about the VPC spec is that it states a VM can only
have one nic. That seems like an arbitrary and unnecessary limitation, as does
the AWS style rules mentioned about a VM not being able to belong to a VPC
network and a non-vpc network, or two VPC networks. The only limitation I'd
like to see is ensuring that a VM doesn't belong to two networks that have the
same or overlapping address ranges (private networks). One of the primary
reasons for being able to add/remove nics is the migration of VMs between
networks, if I have to remove a NIC before adding another because I want to
migrate from VPC to non-VPC or between two VPCs then that causes an unnecessary
outage, when I should just be able to attach the new nic, go into my VM and set
up my dhcp/gateway/routing for that nic, change my DNS or whatever I need to do
to move services to that new nic, and then remove the old.
was (Author: mlsorensen):
One thing I don't understand about the VPC spec is that it states a VM can
only have one nic. That seems like an arbitrary and unnecessary limitation, as
does the one about a VM not being able to belong to a VPC network and a non-vpc
network. The only limitation I'd like to see is ensuring that a VM doesn't
belong to two networks that have the same or overlapping address ranges
(private networks). One of the primary reasons for being able to add/remove
nics is the migration of VMs between networks, if I have to remove a NIC before
adding another because I want to migrate from VPC to non-VPC or between two
VPCs then that causes an unnecessary outage, when I should just be able to
attach the new nic, go into my VM and set up my dhcp/gateway/routing for that
nic, change my DNS or whatever I need to do to move services to that new nic,
and then remove the old.
> Add AWS Style NIC support
> -------------------------
>
> Key: CLOUDSTACK-1043
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1043
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: Future
> Reporter: Simon Waterhouse
>
> The issue is to expose a virtual network interface card (NIC) as a standalone
> entity in the CloudStack API that may be explicitly created/deleted and
> attached/detached from a virtual machine. The intention is to follow the
> pattern pioneered by Amazon with their Elastic Network Interface.
> A desgin document may be found at
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/AWS+Style+NIC+support
--
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
