Not sure you can avoid it completely, nor do I know that everyone else in the industry wants to avoid it either. As avoiding VLANs doesn't address the LANs needed to support clusters of servers acting as any single tier of the application model described below. Web clusters, app clusters, etc...
It's a fine balance that is flexible today because we can use the VLANs and IP subnets appropriately depending on the need and scale. We should be sure not to box ourselves into a one size fits all mentality. InterVLAN routing inside a VRF is very appropriate for many DC's for example and used today. -- Paul Unbehagen Sent from my iPad On Jul 27, 2012, at 9:59 AM, Robert Raszuk <[email protected]> wrote: > Paul, > > > Many web apps require cross VM communications, eg Web server to App > > server to DB server back to App server back to web server then > > finally back to user browser. Thus cross fabric flows are typical in > > many applications > > Absolutely. > > That's why avoiding creation of VLANs in the first place in any part of the > DC network where East-West traffic is of non negligible amount is highly > recommended. > > L3VPN over no service aware pure IP transport works very nicely and addresses > the above application model pretty well. > > Best, > R. > >> Many web apps require cross VM communications, eg Web server to App >> server to DB server back to App server back to web server then finally >> back to user browser. Thus cross fabric flows are typical in many >> applications >> >> Size, scale, and design may affect this a bit, but that's a general app >> flow commonality that exists. This is why interVLAN routing is used >> heavily in DC's of many different sizes. >> >> -- >> Paul Unbehagen > _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
