Re: [dc] draft-khasnabish-vmmi-problems-00.txt

Hello Chris,

Thanks.

>So, the big question is, are you interested in just addressing the network
>portion, or the larger problem (including containers, storage concurrency,
etc)?

We can start with a focus on the "network portion" with only as much as
needed of others (concurrency, containers, de-duplication, etc.). Hope this
helps.

Best.

Bhumip

On Wed, Jan 18, 2012 at 8:00 PM, Christopher LILJENSTOLPE
<cdl@asgaard.org>wrote:

> Greetings Bhumip,
>
>
> On 17Jan2012, at 22.33, Bhumip Khasnabish wrote:
>
> > Tom,
> >
> > Thanks.
> >
> > Yes, seamless migration of VM and VNE can be problematic in both intra-
> and
> > inter-data-center environments, especially in multi-hypervisor case.
>
> Agreed, but it's more than just a network problem, is it not?  ESPECIALLY
> in a multi-hypervisor environment.  So, the big question is, are you
> interested in just addressing the network portion, or the larger problem
> (including containers, storage concurrency, etc)?  If the later, do we have
> the experience and remit to work on that space?
>
>        Chris
>
> >
> > It may be very helpful to bring one or more of these
> > proprietary VM migration approaches to IETF for consideration
> > for standardization, if that is appropriate.
> > Sure, we'll update the draft to articulate these requirements.
> >
> > Best.
> >
> > Bhumip
> >
> >
> > On Tue, Jan 17, 2012 at 10:40 AM, Thomas Narten <narten@us.ibm.com>
> wrote:
> >
> >> Bhumip,
> >>
> >> I skimmed this document and am having trouble figuring out what it is
> >> intended to do.
> >>
> >> The draft name itself has "problem" in it, but there is no single (or
> >> small set of) succinct problems listed. It's all very high level and
> >> hand wavy. I need help making the connection to an IETF action that
> >> could come out of this document.
> >>
> >> For example, it talks about VM migration.
> >>
> >> Is VM Migration a "problem" today? There are properietary approaches
> >> that the market seems to like OK.
> >>
> >> What is wrong with the current approaches? What is "broken" that needs
> >> fixing? Why should the IETF get involved in this space? What value
> >> would the IETF bring?
> >>
> >> Do you want to be able to do VM migration from one vendor's hypervisor
> >> to another vendor's?  If so, please just say so. Then we can see
> >> whether others here think that is an area the IETF (or some other SDO)
> >> should get involved in.
> >>
> >> Thomas
> >>
> >>
> > _______________________________________________
> > dc mailing list
> > dc@ietf.org
> > https://www.ietf.org/mailman/listinfo/dc
>
> --
> 李柯睿
> Check my PGP key here: https://www.asgaard.org/~cdl/cdl.asc
> Current vCard here: https://www.asgaard.org/~cdl/cdl.vcf
>
>