You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Simon Waterhouse <Si...@eu.citrix.com> on 2013/01/10 17:36:28 UTC
[DISCUSS] add/remove NIC on VM
There is an issue https://issues.apache.org/jira/browse/CLOUDSTACK-645 to add/remove a network on VM.
I would like to alter the interface proposed so we instead add methods to explicitly create/destroy a NIC and attach/detach it from a VM - the feature would then be directly analogous to the AWS Elastic Network Interface.
I am a newcomer to CloudStack development, but I would be happy to take on some work in this area (write feature spec, implement API methods etc.) to build upon the work contributed by Marcus and team - from what I can see from CLOUDSTACK-645 much of the required functionality is already in place; I am just suggesting we expose it in a slightly different way...
Regards
Simon
RE: [DISCUSS] add/remove NIC on VM
Posted by Simon Waterhouse <Si...@eu.citrix.com>.
It sounds like a good plan to leave 645 as is, and do the ENI compatibility as follow on work. As Chiradeep points out, that will be a fair bit more work than is in scope for 645 plus being able to add/remove NICs from existing VMs is a great extra feature on its own.
As far as API strategy/evolution goes, I guess this would boil down to a first step of adding the attach/detach NIC commands as part of 645 and then the follow on work would add create/destroy/list NIC commands.
-----Original Message-----
From: Marcus Sorensen [mailto:shadowsor@gmail.com]
Sent: 10 January 2013 19:07
To: cloudstack-dev@incubator.apache.org
Subject: Re: [DISCUSS] add/remove NIC on VM
That would be great. We'll put the code in a feature branch and you can look at it and help us make any adjustments. Brian has been spending a lot of time on it, and I've wanted him to have credit for that by submitting to reviews.apache.org, once that happens we can create a branch for it.
I think the proposal is a bit out of scope of 645 as it's more about making NICs their own entity like volumes are (and potentially entailing all of the extras Chiradeep mentions), whereas 645 is much simpler, its about modifying a VM that is already deployed rather than having to recreate it to get a network you want, but ultimately yours is a better long term method.
I am wondering if it would be best to leave this particular feature 645 as-is, and then take on a separate effort to make NICs into standalone resources and pull in all of those other associated features. 645 would be a subset of the proposed functionality without really hindering us from moving on to the better solution. Alternatively we can drop 645 or make it a child of the bigger effort and just work toward it for 4.2.
On Thu, Jan 10, 2013 at 11:45 AM, Chiradeep Vittal < Chiradeep.Vittal@citrix.com> wrote:
> +1 on ENI-compatibility.
> Note that there is more than just CLOUDSTACK-645
> - with ENI you can have multiple Ips per ENI
> - with ENI the security group is attached to the nic instead of the vm
> - there's additional APIs obviously to manage the lifecycle.
>
> On 1/10/13 8:36 AM, "Simon Waterhouse"
> <Si...@eu.citrix.com>
> wrote:
>
> >There is an issue
> >https://issues.apache.org/jira/browse/CLOUDSTACK-645 to add/remove a network on VM.
> >
> >I would like to alter the interface proposed so we instead add
> >methods to explicitly create/destroy a NIC and attach/detach it from
> >a VM - the feature would then be directly analogous to the AWS
> >Elastic Network Interface.
> >
> >I am a newcomer to CloudStack development, but I would be happy to
> >take on some work in this area (write feature spec, implement API
> >methods
> >etc.) to build upon the work contributed by Marcus and team - from
> >what I can see from CLOUDSTACK-645 much of the required functionality
> >is already in place; I am just suggesting we expose it in a slightly
> >different way...
> >
> >Regards
> >Simon
>
>
RE: [DISCUSS] add/remove NIC on VM
Posted by Simon Waterhouse <Si...@eu.citrix.com>.
Sorry, just looked again at the AWS spec and saw the ability to change security groups on a NIC
I will add support for this in the spec. too.
-----Original Message-----
From: Simon Waterhouse [mailto:Simon.Waterhouse@eu.citrix.com]
Sent: 25 January 2013 11:20
To: cloudstack-dev@incubator.apache.org
Cc: Chiradeep Vittal
Subject: RE: [DISCUSS] add/remove NIC on VM
Chiradeep,
Thanks for the comments. I will update the design spec. as follows:
1. Add a requirement to update instance metadata
2. Add API changes for enableStaticNat and createPortForwardingRule so these can take either virtualmachineid or nicid as request parameters.
3. Add a requirement to provide upgrade scripts/mechanisms
To answer the other questions
1. I had not anticipated providing a command to change the security group(s) on a NIC - is this a desired feature?
2. I regarded any UI changes as not in the initial scope of the change - assuming there were UI specialists who would control and design a consistent UI for the product. If the normal practice is for any new UI to be implemented along with the feature please let me know.
Regards
Simon
-----Original Message-----
From: Chiradeep Vittal
Sent: 25 January 2013 00:23
To: cloudstack-dev@incubator.apache.org
Cc: Simon Waterhouse
Subject: Re: [DISCUSS] add/remove NIC on VM
Thanks Simon.
AWS also updates the instance metadata [1] with the nic information. Are you going to be taking care of this? For example:
network/interfaces/macs/mac/device-number
network/interfaces/macs/mac/security-group-ids
network/interfaces/macs/mac/subnet-id
CloudStack supports the Static NAT feature (like the EIP feature of AWS):
cmd=enableStaticNat&ipaddressid=foo&vm_id=blah
Are we going to update this API to take the nic id instead of the vm id?
Ditto for the createPortForwardingRule API
Do you plan to relax the restriction that instances cannot change security groups? That is, nics can change security groups.
Do you anticipate any UI changes?
During an upgrade from 4.1 -> 4.2, are you going to be creating / modifying any nic entries?
[1]
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AESDG-chapter-instanceda
ta.html#instancedata-data-categories
On 1/23/13 4:43 AM, "Simon Waterhouse" <Si...@eu.citrix.com>
wrote:
>I submitted a feature request (CLOUDSTACK-1043) and put together an
>initial design document (principally API specification) at
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/AWS+Style+NIC+su
>ppo
>rt
>
>I would appreciate comments & suggestions
>
>Simon
>
>-----Original Message-----
>From: Marcus Sorensen [mailto:shadowsor@gmail.com]
>Sent: 10 January 2013 19:07
>To: cloudstack-dev@incubator.apache.org
>Subject: Re: [DISCUSS] add/remove NIC on VM
>
>That would be great. We'll put the code in a feature branch and you can
>look at it and help us make any adjustments. Brian has been spending a
>lot of time on it, and I've wanted him to have credit for that by
>submitting to reviews.apache.org, once that happens we can create a
>branch for it.
>
>I think the proposal is a bit out of scope of 645 as it's more about
>making NICs their own entity like volumes are (and potentially
>entailing all of the extras Chiradeep mentions), whereas 645 is much
>simpler, its about modifying a VM that is already deployed rather than
>having to recreate it to get a network you want, but ultimately yours
>is a better long term method.
>
>I am wondering if it would be best to leave this particular feature 645
>as-is, and then take on a separate effort to make NICs into standalone
>resources and pull in all of those other associated features. 645 would
>be a subset of the proposed functionality without really hindering us
>from moving on to the better solution. Alternatively we can drop 645
>or make it a child of the bigger effort and just work toward it for 4.2.
>
>
>On Thu, Jan 10, 2013 at 11:45 AM, Chiradeep Vittal <
>Chiradeep.Vittal@citrix.com> wrote:
>
>> +1 on ENI-compatibility.
>> Note that there is more than just CLOUDSTACK-645
>> - with ENI you can have multiple Ips per ENI
>> - with ENI the security group is attached to the nic instead of the
>> vm
>> - there's additional APIs obviously to manage the lifecycle.
>>
>> On 1/10/13 8:36 AM, "Simon Waterhouse"
>> <Si...@eu.citrix.com>
>> wrote:
>>
>> >There is an issue
>> >https://issues.apache.org/jira/browse/CLOUDSTACK-645 to add/remove a
>>network on VM.
>> >
>> >I would like to alter the interface proposed so we instead add
>> >methods to explicitly create/destroy a NIC and attach/detach it from
>> >a VM - the feature would then be directly analogous to the AWS
>> >Elastic Network Interface.
>> >
>> >I am a newcomer to CloudStack development, but I would be happy to
>> >take on some work in this area (write feature spec, implement API
>> >methods
>> >etc.) to build upon the work contributed by Marcus and team - from
>> >what I can see from CLOUDSTACK-645 much of the required
>> >functionality is already in place; I am just suggesting we expose it
>> >in a slightly different way...
>> >
>> >Regards
>> >Simon
>>
>>
RE: [DISCUSS] add/remove NIC on VM
Posted by Simon Waterhouse <Si...@eu.citrix.com>.
Chiradeep,
Thanks for the comments. I will update the design spec. as follows:
1. Add a requirement to update instance metadata
2. Add API changes for enableStaticNat and createPortForwardingRule so these can take either virtualmachineid or nicid as request parameters.
3. Add a requirement to provide upgrade scripts/mechanisms
To answer the other questions
1. I had not anticipated providing a command to change the security group(s) on a NIC - is this a desired feature?
2. I regarded any UI changes as not in the initial scope of the change - assuming there were UI specialists who would control and design a consistent UI for the product. If the normal practice is for any new UI to be implemented along with the feature please let me know.
Regards
Simon
-----Original Message-----
From: Chiradeep Vittal
Sent: 25 January 2013 00:23
To: cloudstack-dev@incubator.apache.org
Cc: Simon Waterhouse
Subject: Re: [DISCUSS] add/remove NIC on VM
Thanks Simon.
AWS also updates the instance metadata [1] with the nic information. Are you going to be taking care of this? For example:
network/interfaces/macs/mac/device-number
network/interfaces/macs/mac/security-group-ids
network/interfaces/macs/mac/subnet-id
CloudStack supports the Static NAT feature (like the EIP feature of AWS):
cmd=enableStaticNat&ipaddressid=foo&vm_id=blah
Are we going to update this API to take the nic id instead of the vm id?
Ditto for the createPortForwardingRule API
Do you plan to relax the restriction that instances cannot change security groups? That is, nics can change security groups.
Do you anticipate any UI changes?
During an upgrade from 4.1 -> 4.2, are you going to be creating / modifying any nic entries?
[1]
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AESDG-chapter-instanceda
ta.html#instancedata-data-categories
On 1/23/13 4:43 AM, "Simon Waterhouse" <Si...@eu.citrix.com>
wrote:
>I submitted a feature request (CLOUDSTACK-1043) and put together an
>initial design document (principally API specification) at
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/AWS+Style+NIC+su
>ppo
>rt
>
>I would appreciate comments & suggestions
>
>Simon
>
>-----Original Message-----
>From: Marcus Sorensen [mailto:shadowsor@gmail.com]
>Sent: 10 January 2013 19:07
>To: cloudstack-dev@incubator.apache.org
>Subject: Re: [DISCUSS] add/remove NIC on VM
>
>That would be great. We'll put the code in a feature branch and you can
>look at it and help us make any adjustments. Brian has been spending a
>lot of time on it, and I've wanted him to have credit for that by
>submitting to reviews.apache.org, once that happens we can create a
>branch for it.
>
>I think the proposal is a bit out of scope of 645 as it's more about
>making NICs their own entity like volumes are (and potentially
>entailing all of the extras Chiradeep mentions), whereas 645 is much
>simpler, its about modifying a VM that is already deployed rather than
>having to recreate it to get a network you want, but ultimately yours
>is a better long term method.
>
>I am wondering if it would be best to leave this particular feature 645
>as-is, and then take on a separate effort to make NICs into standalone
>resources and pull in all of those other associated features. 645 would
>be a subset of the proposed functionality without really hindering us
>from moving on to the better solution. Alternatively we can drop 645
>or make it a child of the bigger effort and just work toward it for 4.2.
>
>
>On Thu, Jan 10, 2013 at 11:45 AM, Chiradeep Vittal <
>Chiradeep.Vittal@citrix.com> wrote:
>
>> +1 on ENI-compatibility.
>> Note that there is more than just CLOUDSTACK-645
>> - with ENI you can have multiple Ips per ENI
>> - with ENI the security group is attached to the nic instead of the
>> vm
>> - there's additional APIs obviously to manage the lifecycle.
>>
>> On 1/10/13 8:36 AM, "Simon Waterhouse"
>> <Si...@eu.citrix.com>
>> wrote:
>>
>> >There is an issue
>> >https://issues.apache.org/jira/browse/CLOUDSTACK-645 to add/remove a
>>network on VM.
>> >
>> >I would like to alter the interface proposed so we instead add
>> >methods to explicitly create/destroy a NIC and attach/detach it from
>> >a VM - the feature would then be directly analogous to the AWS
>> >Elastic Network Interface.
>> >
>> >I am a newcomer to CloudStack development, but I would be happy to
>> >take on some work in this area (write feature spec, implement API
>> >methods
>> >etc.) to build upon the work contributed by Marcus and team - from
>> >what I can see from CLOUDSTACK-645 much of the required
>> >functionality is already in place; I am just suggesting we expose it
>> >in a slightly different way...
>> >
>> >Regards
>> >Simon
>>
>>
Re: [DISCUSS] add/remove NIC on VM
Posted by Marcus Sorensen <sh...@gmail.com>.
That's very well laid out, I look forward to this feature!
On Wed, Jan 23, 2013 at 5:43 AM, Simon Waterhouse <
Simon.Waterhouse@eu.citrix.com> wrote:
> I submitted a feature request (CLOUDSTACK-1043) and put together an
> initial design document (principally API specification) at
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/AWS+Style+NIC+support
>
> I would appreciate comments & suggestions
>
> Simon
>
> -----Original Message-----
> From: Marcus Sorensen [mailto:shadowsor@gmail.com]
> Sent: 10 January 2013 19:07
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS] add/remove NIC on VM
>
> That would be great. We'll put the code in a feature branch and you can
> look at it and help us make any adjustments. Brian has been spending a lot
> of time on it, and I've wanted him to have credit for that by submitting to
> reviews.apache.org, once that happens we can create a branch for it.
>
> I think the proposal is a bit out of scope of 645 as it's more about
> making NICs their own entity like volumes are (and potentially entailing
> all of the extras Chiradeep mentions), whereas 645 is much simpler, its
> about modifying a VM that is already deployed rather than having to
> recreate it to get a network you want, but ultimately yours is a better
> long term method.
>
> I am wondering if it would be best to leave this particular feature 645
> as-is, and then take on a separate effort to make NICs into standalone
> resources and pull in all of those other associated features. 645 would be
> a subset of the proposed functionality without really hindering us from
> moving on to the better solution. Alternatively we can drop 645 or make it
> a child of the bigger effort and just work toward it for 4.2.
>
>
> On Thu, Jan 10, 2013 at 11:45 AM, Chiradeep Vittal <
> Chiradeep.Vittal@citrix.com> wrote:
>
> > +1 on ENI-compatibility.
> > Note that there is more than just CLOUDSTACK-645
> > - with ENI you can have multiple Ips per ENI
> > - with ENI the security group is attached to the nic instead of the vm
> > - there's additional APIs obviously to manage the lifecycle.
> >
> > On 1/10/13 8:36 AM, "Simon Waterhouse"
> > <Si...@eu.citrix.com>
> > wrote:
> >
> > >There is an issue
> > >https://issues.apache.org/jira/browse/CLOUDSTACK-645 to add/remove a
> network on VM.
> > >
> > >I would like to alter the interface proposed so we instead add
> > >methods to explicitly create/destroy a NIC and attach/detach it from
> > >a VM - the feature would then be directly analogous to the AWS
> > >Elastic Network Interface.
> > >
> > >I am a newcomer to CloudStack development, but I would be happy to
> > >take on some work in this area (write feature spec, implement API
> > >methods
> > >etc.) to build upon the work contributed by Marcus and team - from
> > >what I can see from CLOUDSTACK-645 much of the required functionality
> > >is already in place; I am just suggesting we expose it in a slightly
> > >different way...
> > >
> > >Regards
> > >Simon
> >
> >
>
Re: [DISCUSS] add/remove NIC on VM
Posted by Chiradeep Vittal <Ch...@citrix.com>.
Thanks Simon.
AWS also updates the instance metadata [1] with the nic information. Are
you going to be taking care of this? For example:
network/interfaces/macs/mac/device-number
network/interfaces/macs/mac/security-group-ids
network/interfaces/macs/mac/subnet-id
CloudStack supports the Static NAT feature (like the EIP feature of AWS):
cmd=enableStaticNat&ipaddressid=foo&vm_id=blah
Are we going to update this API to take the nic id instead of the vm id?
Ditto for the createPortForwardingRule API
Do you plan to relax the restriction that instances cannot change security
groups? That is, nics can change security groups.
Do you anticipate any UI changes?
During an upgrade from 4.1 -> 4.2, are you going to be creating /
modifying any nic entries?
[1]
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AESDG-chapter-instanceda
ta.html#instancedata-data-categories
On 1/23/13 4:43 AM, "Simon Waterhouse" <Si...@eu.citrix.com>
wrote:
>I submitted a feature request (CLOUDSTACK-1043) and put together an
>initial design document (principally API specification) at
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/AWS+Style+NIC+suppo
>rt
>
>I would appreciate comments & suggestions
>
>Simon
>
>-----Original Message-----
>From: Marcus Sorensen [mailto:shadowsor@gmail.com]
>Sent: 10 January 2013 19:07
>To: cloudstack-dev@incubator.apache.org
>Subject: Re: [DISCUSS] add/remove NIC on VM
>
>That would be great. We'll put the code in a feature branch and you can
>look at it and help us make any adjustments. Brian has been spending a
>lot of time on it, and I've wanted him to have credit for that by
>submitting to reviews.apache.org, once that happens we can create a
>branch for it.
>
>I think the proposal is a bit out of scope of 645 as it's more about
>making NICs their own entity like volumes are (and potentially entailing
>all of the extras Chiradeep mentions), whereas 645 is much simpler, its
>about modifying a VM that is already deployed rather than having to
>recreate it to get a network you want, but ultimately yours is a better
>long term method.
>
>I am wondering if it would be best to leave this particular feature 645
>as-is, and then take on a separate effort to make NICs into standalone
>resources and pull in all of those other associated features. 645 would
>be a subset of the proposed functionality without really hindering us
>from moving on to the better solution. Alternatively we can drop 645 or
>make it a child of the bigger effort and just work toward it for 4.2.
>
>
>On Thu, Jan 10, 2013 at 11:45 AM, Chiradeep Vittal <
>Chiradeep.Vittal@citrix.com> wrote:
>
>> +1 on ENI-compatibility.
>> Note that there is more than just CLOUDSTACK-645
>> - with ENI you can have multiple Ips per ENI
>> - with ENI the security group is attached to the nic instead of the vm
>> - there's additional APIs obviously to manage the lifecycle.
>>
>> On 1/10/13 8:36 AM, "Simon Waterhouse"
>> <Si...@eu.citrix.com>
>> wrote:
>>
>> >There is an issue
>> >https://issues.apache.org/jira/browse/CLOUDSTACK-645 to add/remove a
>>network on VM.
>> >
>> >I would like to alter the interface proposed so we instead add
>> >methods to explicitly create/destroy a NIC and attach/detach it from
>> >a VM - the feature would then be directly analogous to the AWS
>> >Elastic Network Interface.
>> >
>> >I am a newcomer to CloudStack development, but I would be happy to
>> >take on some work in this area (write feature spec, implement API
>> >methods
>> >etc.) to build upon the work contributed by Marcus and team - from
>> >what I can see from CLOUDSTACK-645 much of the required functionality
>> >is already in place; I am just suggesting we expose it in a slightly
>> >different way...
>> >
>> >Regards
>> >Simon
>>
>>
RE: [DISCUSS] add/remove NIC on VM
Posted by Simon Waterhouse <Si...@eu.citrix.com>.
I submitted a feature request (CLOUDSTACK-1043) and put together an initial design document (principally API specification) at https://cwiki.apache.org/confluence/display/CLOUDSTACK/AWS+Style+NIC+support
I would appreciate comments & suggestions
Simon
-----Original Message-----
From: Marcus Sorensen [mailto:shadowsor@gmail.com]
Sent: 10 January 2013 19:07
To: cloudstack-dev@incubator.apache.org
Subject: Re: [DISCUSS] add/remove NIC on VM
That would be great. We'll put the code in a feature branch and you can look at it and help us make any adjustments. Brian has been spending a lot of time on it, and I've wanted him to have credit for that by submitting to reviews.apache.org, once that happens we can create a branch for it.
I think the proposal is a bit out of scope of 645 as it's more about making NICs their own entity like volumes are (and potentially entailing all of the extras Chiradeep mentions), whereas 645 is much simpler, its about modifying a VM that is already deployed rather than having to recreate it to get a network you want, but ultimately yours is a better long term method.
I am wondering if it would be best to leave this particular feature 645 as-is, and then take on a separate effort to make NICs into standalone resources and pull in all of those other associated features. 645 would be a subset of the proposed functionality without really hindering us from moving on to the better solution. Alternatively we can drop 645 or make it a child of the bigger effort and just work toward it for 4.2.
On Thu, Jan 10, 2013 at 11:45 AM, Chiradeep Vittal < Chiradeep.Vittal@citrix.com> wrote:
> +1 on ENI-compatibility.
> Note that there is more than just CLOUDSTACK-645
> - with ENI you can have multiple Ips per ENI
> - with ENI the security group is attached to the nic instead of the vm
> - there's additional APIs obviously to manage the lifecycle.
>
> On 1/10/13 8:36 AM, "Simon Waterhouse"
> <Si...@eu.citrix.com>
> wrote:
>
> >There is an issue
> >https://issues.apache.org/jira/browse/CLOUDSTACK-645 to add/remove a network on VM.
> >
> >I would like to alter the interface proposed so we instead add
> >methods to explicitly create/destroy a NIC and attach/detach it from
> >a VM - the feature would then be directly analogous to the AWS
> >Elastic Network Interface.
> >
> >I am a newcomer to CloudStack development, but I would be happy to
> >take on some work in this area (write feature spec, implement API
> >methods
> >etc.) to build upon the work contributed by Marcus and team - from
> >what I can see from CLOUDSTACK-645 much of the required functionality
> >is already in place; I am just suggesting we expose it in a slightly
> >different way...
> >
> >Regards
> >Simon
>
>
Re: [DISCUSS] add/remove NIC on VM
Posted by Marcus Sorensen <sh...@gmail.com>.
That would be great. We'll put the code in a feature branch and you can
look at it and help us make any adjustments. Brian has been spending a lot
of time on it, and I've wanted him to have credit for that by submitting to
reviews.apache.org, once that happens we can create a branch for it.
I think the proposal is a bit out of scope of 645 as it's more about making
NICs their own entity like volumes are (and potentially entailing all of
the extras Chiradeep mentions), whereas 645 is much simpler, its about
modifying a VM that is already deployed rather than having to recreate it
to get a network you want, but ultimately yours is a better long term
method.
I am wondering if it would be best to leave this particular feature 645
as-is, and then take on a separate effort to make NICs into standalone
resources and pull in all of those other associated features. 645 would be
a subset of the proposed functionality without really hindering us from
moving on to the better solution. Alternatively we can drop 645 or make it
a child of the bigger effort and just work toward it for 4.2.
On Thu, Jan 10, 2013 at 11:45 AM, Chiradeep Vittal <
Chiradeep.Vittal@citrix.com> wrote:
> +1 on ENI-compatibility.
> Note that there is more than just CLOUDSTACK-645
> - with ENI you can have multiple Ips per ENI
> - with ENI the security group is attached to the nic instead of the vm
> - there's additional APIs obviously to manage the lifecycle.
>
> On 1/10/13 8:36 AM, "Simon Waterhouse" <Si...@eu.citrix.com>
> wrote:
>
> >There is an issue https://issues.apache.org/jira/browse/CLOUDSTACK-645 to
> >add/remove a network on VM.
> >
> >I would like to alter the interface proposed so we instead add methods to
> >explicitly create/destroy a NIC and attach/detach it from a VM - the
> >feature would then be directly analogous to the AWS Elastic Network
> >Interface.
> >
> >I am a newcomer to CloudStack development, but I would be happy to take
> >on some work in this area (write feature spec, implement API methods
> >etc.) to build upon the work contributed by Marcus and team - from what
> >I can see from CLOUDSTACK-645 much of the required functionality is
> >already in place; I am just suggesting we expose it in a slightly
> >different way...
> >
> >Regards
> >Simon
>
>
Re: [DISCUSS] add/remove NIC on VM
Posted by Chiradeep Vittal <Ch...@citrix.com>.
+1 on ENI-compatibility.
Note that there is more than just CLOUDSTACK-645
- with ENI you can have multiple Ips per ENI
- with ENI the security group is attached to the nic instead of the vm
- there's additional APIs obviously to manage the lifecycle.
On 1/10/13 8:36 AM, "Simon Waterhouse" <Si...@eu.citrix.com>
wrote:
>There is an issue https://issues.apache.org/jira/browse/CLOUDSTACK-645 to
>add/remove a network on VM.
>
>I would like to alter the interface proposed so we instead add methods to
>explicitly create/destroy a NIC and attach/detach it from a VM - the
>feature would then be directly analogous to the AWS Elastic Network
>Interface.
>
>I am a newcomer to CloudStack development, but I would be happy to take
>on some work in this area (write feature spec, implement API methods
>etc.) to build upon the work contributed by Marcus and team - from what
>I can see from CLOUDSTACK-645 much of the required functionality is
>already in place; I am just suggesting we expose it in a slightly
>different way...
>
>Regards
>Simon