Hi Linda, > [Linda] Does it assume that hypervisors will need to add this new > attach/detach function? > > IEEE802.1Qbg defines a Virtual Interface Discovery Protocol (VDP) which > require Hypervisors to send Port Profile upon a new VM is added. However, the > challenge is that Data Center operators may not be able to dictate what > servers/hypervisors being deployed in their data centers.
Yes, VDP is a candidate for the attach/detach protocol. Thanks, --David > -----Original Message----- > From: Linda Dunbar [mailto:[email protected]] > Sent: Tuesday, June 26, 2012 5:30 PM > To: Stiliadis, Dimitrios (Dimitri); [email protected]; Black, David > Cc: [email protected] > Subject: RE: [nvo3] Softswitches > > > > > > If the NVE is on a ToR, then there is a need for an attach/detach > > protocol method hypervisors and ToRs. > > > > > [Linda] Does it assume that hypervisors will need to add this new > attach/detach function? > > IEEE802.1Qbg defines a Virtual Interface Discovery Protocol (VDP) which > require Hypervisors to send Port Profile upon a new VM is added. However, the > challenge is that Data Center operators may not be able to dictate what > servers/hypervisors being deployed in their data centers. > > If you can't dictate any changes to deployed hypervisors, "ARP/ND" might be > able to be used as a way to announce the attachment, and timeout to declare > the "detachment". > > > My two cents. > > Linda Dunbar > > > NVE-2-oracle and oracle-2-rest_of_the_network I highly agree. But I > > am > > > not sure if one size will fit all there. > > > > I think that David has a valid point trying to separate the two and we > > need both. > > > > Dimitri > > > > > > R. > > > > > > >> -----Original Message----- > > > >> From: [email protected] [mailto:[email protected]] On > > Behalf Of > > > Robert > > > >> Raszuk > > > >> Sent: Tuesday, June 26, 2012 3:48 PM > > > >> To: Black, David > > > >> Cc: [email protected] > > > >> Subject: Re: [nvo3] Softswitches > > > >> > > > >> Hi David, > > > >> > > > >> Honestly I think we are getting more into implementation then > > > >> standardization debate. > > > >> > > > >> What I call a softswitch can be either part of the linux kernel > > entirely > > > >> as a loadable module, can be partially in the kernel and partially > > in > > > >> the user space or if you follow NETMAP's direct memory mapping > > from > > > >> interface to user space could sit completely there. > > > >> > > > >> Examples of softswitches which I am experimenting with is as you > > said > > > >> one from VMWare, the other most popular is OVS, there is LINK > > released > > > >> recently and there is at least few more in the works which would > > be > > > >> partially sitting in the end-system kernel or the kernel and user > > space. > > > >> > > > >> At least this is what I meant by using the term "embedded". > > > >> > > > >> The main point I think is that the L2/L3 virtualization/separation > > will > > > >> be happening in all of the above cases which share one very > > important > > > >> common characteristic - thay are all residing on the end host. > > > >> > > > >> Best regards, > > > >> R. > > > > > > > > > _______________________________________________ > > > nvo3 mailing list > > > [email protected] > > > https://www.ietf.org/mailman/listinfo/nvo3 > > _______________________________________________ > > nvo3 mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
