Comment 4 for bug 1046766

If you look in Nova, the new network API has a VIF class. It's a very weak class with unstructured data. It would perhaps make sense for that to be tidied up, and then subclassed to provide, from whatever provider, the necessary information to hypervisors to plug into a VIF (particularly bearing in mind that a VIF is not always just the name of a bridge to join). The current 'I have this class that sits off to the side and does all the actions' mechanism is not great and it's also not terribly OO.

The contract between nova and the network code would be 'if you implement this VIF class then you can provide a network endpoint for nova to use'.