On Thu, Jul 25, 2013 at 3:47 AM, Linda Dunbar <[email protected]>wrote:

> I would think that the interface between NVA and VM orchestration is out
> of the NVO3's scope (if not out of IETF's scope), isn't it?
>
[Lizhong] I don't know which standardization body should work with IETF to
standardize this interface (maybe WG Chair or AD should care about that).
But from a standardized solution point of view, it would have potential
benefit if NVA could be a standalone element, and have standardized
interface with other elements.

Regards
Lizhong



>
> Linda
>
> > -----Original Message-----
> > From: [email protected] [mailto:[email protected]] On Behalf Of
> > Thomas Narten
> > Sent: Wednesday, July 24, 2013 11:56 AM
> > To: Lizhong Jin
> > Cc: [email protected]
> > Subject: [nvo3] Arch: NVA - VM Orchestration interface
> >
> > > 2. Is there a standard interface between NVA and VM orchestration, or
> > a
> > > private interface? Hope to see more description in detail.
> >
> > Today, there are already existing VM orchestration systems that embed
> > some or all of the functionality of the NVA. I don't see those systems
> > as changing or wanting to implement a standard interface just for the
> > sake of doing so. So, today, there are private interfaces that do that
> > and they will presumably continue to exist in the future.
> >
> > However, IMO there is still a need to have a standard interface so
> > that entities other than hypervisors can interact with the
> > NVA. Existing VM orchestration systems that have an embedded NVA may
> > then find it useful to implement such a standard interface, but I
> > would expect they would continue to also support their private
> > interface for backwards compatability with other components of their
> > systems.
> >
> > Thomas
> >
> > _______________________________________________
> > nvo3 mailing list
> > [email protected]
> > https://www.ietf.org/mailman/listinfo/nvo3
>
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3

Reply via email to