From: Qin Wu <[email protected]<mailto:[email protected]>> Date: Thursday, April 11, 2013 2:59 AM To: Larry Kreeger <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [nvo3] 答复: 答复: NVO3 Terminology changes
>[Qin]: In that case, vNIC is not equivalent to Tenant System interface since >tenant system interface can be either physical interface or virtual interface. >The reason I propose such change is vNIC is virtual NIC not physical NIC, >therefore if you replace vNIC with Tenant system interface, that means Tenant >system interface only corresponds to virtual interfacel. >LK2> Again, I don't want to replace all instances of VNIC with TSI, but use >the more general term TSI when it is not a specific example of a TS that is a >Virtual Machine. So, a VNIC is one type of TSI, but all TSIs are not >VNICs. [Qin]: Great, we are on the same page. LK3> Great! >>I believe one tenant system can host multiple VMs, each VM may have multiple >>vNIC adapters that it uses to communicate with both the virtual and physical >>networks. >LK> A VM is one example of a tenant system…so it would not host VMs. You may >be thinking of "End Device". >[Qin]: Not sure about that, the definition of “Tenant system” in Framework >said: “ > Tenant System: A physical or virtual system that can play the role > of a host, or a forwarding element such as a router, switch, > firewall, etc. It belongs to a single tenant and connects to one or > more VNs of that tenant. ” >So tenant system can be a host and host one or multiple VMs on it. What am I >missing? >LK2> I think that you are assuming that "host" is synonymous with >"Hypervisor". In the definition above, I believe the term host relates to the >more traditional definition of an internet host such as in RFC 1122. [Qin]: So “Host” in the definition of tenant system seems misleading since we two have different interpretation to it. I agree Hypersor or Server or Server blade can host multiple VMs, however in the framework document, it also said, a host can be server or server blade in the definition of End device. LK3> Only servers or server blades that are running hypervisors can host multiple VMs. When we mean hypervisor we must say hypervisor (what form factor of server it is running on is irrelevant). All hypervisors run on servers, but all servers are not running hypervisor software. Suppose one tenant A have 2 VMs resided in the server1 or hypervisor1. Tenant B have 3 VMs resided in the server 1. Can we say each VM belonging to the same tenant is a tenant system LK3> Yes or multiple VMs of each tenant sharing the same Server belong to the same single tenant system? i.e., Tenant System A corresponding to Tenant A contains 2 VMs. Tenant System B corresponding to Tenant B contains 3 VMs. LK3> No, that would be a really bad idea IMO. The fact that two VMs happen to be running on the same server hardware is an ephemeral thing. From one moment to the next a VM may migrate to a different server where it becomes separated from the other VMs. Furthermore, I see no advantage in defining a Tenant System to be a grouping of VMs from a networking perspective since the thing that connects multiple VMs together is the network.
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
