Hacker Newsnew | comments | show | ask | jobs | submit | sunyc's comments login

bundling with (unholy-ly immature) SDN is the most damning things for its adoption. It is thought to be needed for "live migration", but I don't see me needing that anytime soon because we run on virtual machines anyway?

Iaas provider is not going away,paying for the cost of SDN now for features that doesn't even exists yet, is insane.

-----


(kubernetes contributor here)

SDN isn't required for k8s, what is required is that each Pod (group of containers) get it's own IP address, and that the IP address is routeable in the cluster. In many cases, the easiest way to achieve this is via an SDN, but it is also achievable by programming traditional routers.

The reason for wanting an IP address per pod is that it eliminates the need for port mangling, which dramatically simplifies wiring applications together.

-----


All applications was already desinged to be port based. I don't see how this would drastically change that.

-----


the problem with port mangling is that your application starts running on random ports, so in addition to requiring discovery for IP addresses, you now also have to do discovery for ports, which pretty much requires custom code and infrastructure linked into your binaries (how do you convince nginx/redis/... to use your lookup service for ports?)

And ports are different between different replicas of your service, since they're chosen at random during scheduling.

It also makes ACLs and QoS harder to define for the network, since you don't have a clean network identity (e.g IP Address) for each application.

-----


reinvented stunnel.

-----


The author uses stunnel to terminate SSL connections[1], so if he reinvented it, it's because he thought it necessary.

[1] http://www.daemonology.net/blog/2009-09-28-securing-https.ht...

-----


Not being stunnel is the entire point of spiped. The author doesn't trust TLS.

-----


i suggest new commer give byobu a try, a wrapper of tmux.

-----


its actually a wrapper for screen as also for tmux, the standard ubuntu package uses screen.

byobu is really recommended because its simple to use yet powerfull.

http://en.wikipedia.org/wiki/Byobu_(software)

-----


one of my server got exposed too, it was being queried for ripe.net

-----


i think its bullshit, just buy 10 vps and write garbage to disk, in a month you can wipe their entire stock of ssd disks.

-----


almost all bgp transit provider have prefix filtering,

-----


checking prog directory might mean they are looking for specific machin with specific system image

-----


does anyone know what size it is now?

-----


50MB zipped, 148MB unzipped

-----


it is under used because most of the time, you just don't have to care. and when it matters it lack the depth you need, like layer 7 detection.

it is almost always better to just pay for bigger pipes.

-----


Wouldn't layer 7 detection drive CPU usage up for a somewhat different use case? You are not trying to give video traffic a lower priority - you are trying to prevent things like backups clogging your pipes.

-----


Can we agree on a standard Linux directory structure first?

-----

More

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: