cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcus Sorensen <shadow...@gmail.com>
Subject Re: [DISCUSS] add/remove NIC on VM
Date Wed, 23 Jan 2013 17:19:36 GMT
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"
> > <Simon.Waterhouse@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
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message