{"id":61,"date":"2011-03-29T11:15:55","date_gmt":"2011-03-29T11:15:55","guid":{"rendered":"http:\/\/www.syslog.cl.cam.ac.uk\/?p=61"},"modified":"2011-03-29T11:15:55","modified_gmt":"2011-03-29T11:15:55","slug":"end-to-end-arguments-in-virtualised-system-design","status":"publish","type":"post","link":"https:\/\/www.syslog.cl.cam.ac.uk\/2011\/03\/29\/end-to-end-arguments-in-virtualised-system-design\/","title":{"rendered":"End to end arguments in Virtualised System Design"},"content":{"rendered":"

We've come a long way in virtualisation (some would say around in a big circle, but that's a different blog entry). Now we have routine cloud services (commercial, public and private) based on VMs all over the place. We also have routine VPNs, at least in most layer 2 net setups, and (at much greater expense) as commercial offerings between large corporate sites.<\/p>\n

What virtualisation does is combine two properties - statistical multiplexing (resource pooling) together with isolation (privacy). Some VMs and VPNs allow you to tune the amount of resource pooling (for a price) that you are prepared to tolerate.<\/p>\n

What seems to be lacking is a seamless integration of VM and VPN, and it seems that it is not a trivial thing to solve in a clean way. Obviously, one can simply map a service (e.g. a large Skywriting app running on a set of data centers) to a VPN. But that isn't terribly useful in general. More typically if there are resource pooling design goals, they are more likely, in the network layer to lie in having a wide set of user demands from outside of the VPN (e.g. a hose or sink tree).<\/p>\n

So what should virtualised host+net look like as a building block, and what should the tools be to \"provision\" such things in an expressive, checkable, and simple way?<\/p>\n

 <\/p>\n

Seems like this is a good current challenge... ...<\/p>\n","protected":false},"excerpt":{"rendered":"

We’ve come a long way in virtualisation (some would say around in a big circle, but that’s a different blog entry). Now we have routine cloud services (commercial, public and private) based on VMs all over the place. We also have routine VPNs, at least in most layer 2 net setups, and (at much greater […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.syslog.cl.cam.ac.uk\/wp-json\/wp\/v2\/posts\/61"}],"collection":[{"href":"https:\/\/www.syslog.cl.cam.ac.uk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.syslog.cl.cam.ac.uk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.syslog.cl.cam.ac.uk\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.syslog.cl.cam.ac.uk\/wp-json\/wp\/v2\/comments?post=61"}],"version-history":[{"count":2,"href":"https:\/\/www.syslog.cl.cam.ac.uk\/wp-json\/wp\/v2\/posts\/61\/revisions"}],"predecessor-version":[{"id":63,"href":"https:\/\/www.syslog.cl.cam.ac.uk\/wp-json\/wp\/v2\/posts\/61\/revisions\/63"}],"wp:attachment":[{"href":"https:\/\/www.syslog.cl.cam.ac.uk\/wp-json\/wp\/v2\/media?parent=61"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.syslog.cl.cam.ac.uk\/wp-json\/wp\/v2\/categories?post=61"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.syslog.cl.cam.ac.uk\/wp-json\/wp\/v2\/tags?post=61"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}