My interpretation for two sides of TS, is >From tenant point of view, a tenant that has tenant system doesn't need to >distinguish pNIC from vNIC, What tenant view is just a set of NICs that belong to the same tenant system. >From hypervisor point of view or tenant system point of view, tenant system >should know whether it is pNIC or vNIC.
Regards! -Qin -----Original Message----- From: Pat Thaler [mailto:[email protected]] Sent: Saturday, April 20, 2013 3:44 AM To: Thomas Narten Cc: Qin Wu; [email protected] Subject: RE: [nvo3] vNICs and pNics in draft-wu-nvo3-nve2nve-04.txt Agree, Pat -----Original Message----- From: Thomas Narten [mailto:[email protected]] Sent: Friday, April 19, 2013 11:49 AM To: Pat Thaler Cc: Qin Wu; [email protected] Subject: Re: [nvo3] vNICs and pNics in draft-wu-nvo3-nve2nve-04.txt "Pat Thaler" <[email protected]> writes: > In addition to Thomas's point, we should not restrict the number of > physical NICs that a tenant system can have. Some tenant systems > will have more than one physical NIC. Agreed. > We may describe some typical tenant systems as part of examining use > cases, but NVO3 should define behavior in terms of the network > interface, i.e. TSI, behavior and should not restrict tenant system > architecture. Another way of looking at it is that the TSI is an attachement point/interface to the TS. The point where the TSI attaches to the TS has two sides. On the tenant facing side, it appears to be a NIC. It looks like a NIC, behaves like a NIC, etc. On the side facing away from the tenant (e.g., the hypervisor in the case of a virtualized system) we call it a TSI. The TSI side will have attributes that are specific to NVO3. Does that make sense? Thomas _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
