[vnrg] Some more Acid tests & VN principles

[Sunay Tripathi <[e-mail]>]

So looking at the Acid tests so far and VN principles, it seems like
we need to tighten the isolation case a bit more. Specifically, just
putting a Virtual Output Queue (VoQ) per VN on each link to provide
isolation is not cutting it. The isolation (which translates
into per packet latency and B/W) needs to be on a VN fabric level
rather than on individual link level. Basically the VN should
mirror the non virtualized physical network of same capacity i.e.
a VN for 1Gbps on a 10Gbps network should see same or better
behavior than if it was on a physical 1Gbps switch fabric by
itself. This does need the network elements like switches and
routers to do more work.

Robert, not sure if you are on the VNRG mailing list but this
would be a good place for some of the things we were discussing
related to what we are building.

The other thing is related to management. A VN administrator
needs to be able to administer his resources and name space
independently.

But the issue that is bogging us down is what is the non virtualized
part that ties entities to VN and allows the H/W to enforce the
virtualization - is it the MAC address? Is it the VLAN? The problem
with VLAN is that most hosts don't support Q-in-Q. Do people
have thoughts on this?

Cheers,
Sunay