4 ms·
Why would you expect a blog entry from someone who invested in the company and wants to celebrate its success to explain the technical details of what it does?
by biot 14y ago
Why would you expect a blog entry from someone who invested in the company and wants to celebrate its success to explain the technical details of what it does? That's like showing up at a party when the first human walks on Mars and walking away disappointed because everyone's drinking champagne rather than giving a technical presentation on the landing mechanism.
If you want the technical details, try Nicira's website. They have a 3 minute Nicira intro video: http://bcove.me/lydym25p http://bcove.me/lydym25p (skip to 1:10 for the meat). Or, just imagine if you had VMs in multiple racks within potentially multiple data centers and, on the fly, you could use an API to provision a private 10.0.0.0 subnet so that the machines could talk to each other as if they were directly connected to the same physical network switch. In a nutshell, virtualized TCP/IP tunneled over TCP/IP.
- samstave 14y agoOne of the best posts I've read on HN; great analogy followed by awesome super succinct explainaion.
- b0 14y agoI thought TCP over TCP was a sin?
- wmf 14y agoIt is, but Nicira does IP over IP.
- bennysaurus 14y agoTechnically Nicira does both. One of the tunnelling protocols it uses is STT (Stateless Transport Tunnelling) Protocol which they effectively made themselves (and is up for draft in the IETF). It's their mechanism of choice for communicating between the network controllers and hypervisors over the physical network. It's not true TCP, but looks enough like like it to allow hardware offloading to the network interfaces of all the tunnelling, saving a lot of CPU power. This allows for throughput speeds in an STT software tunnel to reach the same maximums as "raw" TCP through a given interface.
- trentmb 14y agoBecause the technical details of what it does is why it's successful.
- skeletonjelly 14y agoExactly! It's the "how".
- haberman 14y agoIt's not clear to me that your example actually motivates a new technology. If these VMs all have IP addresses, then they can all talk to each other already -- no special subnet is needed. And unless this virtual subnet is performing VPN-style encryption, this virtual subnet does not provide any additional security or data isolation on top of what TCP/IP already provide (ie. you can only read data addressed to you unless you control the physical hardware and put it in promiscuous mode). I'm not contradicting the idea that this technology is useful (obviously VMWare's acquisition speaks for itself), but I would like to see a motivating example that can't be accommodated with plain TCP/IP.
- deleted 14y ago[deleted]
- taligent 14y agoIt looks remarkably similar to VCider which I personally use and love. And it DOES provide additional security because it reduces the number of open ports that you have to firewall between servers. Mistakes do happen when you are managing large number of servers.