cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anthony Xu <>
Subject RE: [jira] [Created] (CLOUDSTACK-1043) Add AWS Style NIC support
Date Wed, 23 Jan 2013 17:28:18 GMT
Hi Simon,

I'm glad to see ENI feature in CloudStack, I do have some questions,

  it actually allocates IP, should CS limit the number of NIC an account can create to avoid
one account use too many IP? 

 can a NIC be attached to any VM, or only VM in the same network with NIC?
 Will this api apply Security group rules for this NIC? 

since a NIC can only be attached to one VM, I don't think parameter virtualmachineid is necessary.
Will this api remove security group rules for this NIC?

Since the feature moves SG to NIC level from VM level, it might be nice to add content about
SG API behavior changes, and upgrade in this FS.


> -----Original Message-----
> From: Simon Waterhouse (JIRA) []
> Sent: Wednesday, January 23, 2013 4:38 AM
> To:
> Subject: [jira] [Created] (CLOUDSTACK-1043) Add AWS Style NIC support
> Simon Waterhouse created CLOUDSTACK-1043:
> --------------------------------------------
>              Summary: Add AWS Style NIC support
>                  Key: CLOUDSTACK-1043
>                  URL:
> 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
> pport
> --
> 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:
View raw message