Hi,
I'm currently exploring ways of moving parts of XenServer/XCP's domain0 into
helper domains and I think the openvswitch may be able to help. FYI here's the
kind of thing I'm thinking of:
* Client sends HTTP request to domain0's management IP (call this M)
* xapi binds a random local port on the management IP (call this P)
* xapi boots up a helper domain, tells it to listen on M:P
* xapi uses openflow (or ovs-ofctl) to program the local openvswitch to
redirect TCP traffic to M:P to the helper domain's switch port, while
translating the MACs using mod_dl_{src,dst}
* xapi issues an HTTP 302 redirect to M:P
Although sharing the management IP between two domains is a bit hacky :) it's
nice not to require the admin to configure a means for xapi to allocate IP
addresses for all its non-domain0 children.
Apart from comments on the general (in)sanity (which I'm also interested in),
I'm curious about how connecting a controller would affect this scheme. My
understanding is that the controller "owns" all the rules in the lower
switches: would a controller always wipe out these "local" rules I've added, or
does that just depend on the controller? Is there any general way to prevent a
controller doing that, for some small subset of the rules?
Any comments appreciated.
Cheers,
Dave
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
