>> >>-----Original Message----- >> From: [email protected] [mailto:[email protected]] On Behalf Of >> Ivan Pepelnjak >> Sent: Tuesday, August 28, 2012 12:22 AM >> To: Stiliadis, Dimitrios (Dimitri) >> Cc: Black, David; [email protected]; Linda Dunbar >> Subject: Re: [nvo3] Let's refocus on real world (was: Comments on Live >> Migration and VLAN-IDs) >> >> Dimitri, >> >> We're more in agreement than it might seem. I might have my doubts >> about >> the operational viability of the OpenStack-to-baremetal use case you >> described below, but I'm positive someone will try to do that as well. >> >> In any case, regardless of whether we're considering VMs or bare-metal >> servers, in the simplest scenario the server-to-NVE connection is a >> point-to-point link, usually without VLAN tagging. >> >> In the VM/hypervisor case, NVE is implemented in the hypervisor soft >> switch; in the baremetal server case, it has to be implemented in the >> ToR switch. > > This is certainly only today's restriction. If nov3 takes off, there > certainly could be a pseudo-driver in Linux that could implement the > NVE (like a VLAN driver) without much additional overhead.
That doesn't work if you assume that tenants and DC operators are different entities. The DC operator cannot rely on the tenant to do the right encapsulation. Different administrative and trust domains. That's why in my original email I was talking about "trust boundaries". Dimitri > _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
