josh2600

56 ms·

601.
by josh2600 12y ago
Terminal.com is hiring. We work on next-generation virtualization technology. We are a hard-working, fast-moving startup based in San Francisco and Palo Alto. We value highly-optimized, correct code. We are building the next generation of c
602.
by josh2600 12y ago
As a very effective substrate for hosting containers, we at Terminal think a lot about which of the container mechanisms will win over the long term. My personal opinion is that the winner will be the group that successfully gets Enterprise
603.
by josh2600 12y ago
I made a snapshot on Terminal.com which lets you try Meteor 1.1 in seconds. Check it out here: https://www.terminal.com/snapshot/be98f98eece7e102bab130b91d... This boots a CentOS 6 box running Meteor 1.1. It's als
604.
by josh2600 12y ago
Ahh cool! That's way better. I thought it was just channel bonding. I can still easily imagine a conflict where your signaling IP and your media IP are different in VoIP, but binding connections to IP addresses is pretty reasonable.
605.
by josh2600 12y ago
This is all well and good until you start doing anything with address sensitive replies. For example a VoIP call would need some way of anchoring the packets to a specific connection for the duration of the call (some kind of session pinnin
606.
by josh2600 12y ago
This is hard. Nothing about this is easy. Moving forward, we should all work to make workplaces where everyone can feel wanted. I don't think Race or Gender matters and I would not want to work somewhere where it does. I want to work i
607.
by josh2600 12y ago
That's a great point, but I think the point of what Bryan has been doing is to make Linux work with Zones (and dtrace). That's a primitive that Joyent has wanted to upstream into the Linux kernel for a long time and has never been
608.
by josh2600 12y ago
Joyent has solved some really hard problems to make this work. I was lucky enough to get the chance to sit down with Bryan last week and talk with him about what this took. It's essentially reimplementing Linux on top of Illumnos, whic
609.
Big Data Meetup in SF 3/31(bigdatasf.eventbrite.com)
1 points by josh2600 12y ago|0 comments
610.
by josh2600 12y ago
Feel free to ping me on the email address in my profile. Be forewarned, we have a pretty serious technical interview for all candidates. I would say it's not easy to get a technical job at Terminal.
611.
by josh2600 12y ago
Terminal.com is writing next generation virtualization. This includes live-migration without hypervisors (already in production) and live-resizing (also in production). I think we'd like to think we're working on the ugly bits of
612.
by josh2600 12y ago
Just make a snapshot on terminal.com and then the state of your web application can be distributed at an instant in time. You can verify its exactly what you say it is since the snapshot is bound to your user name. You can make a snapshot f
613.
by josh2600 12y ago
>Why only 'zero-emissions" vehicles? What incentive does Elon Musk have to lobby for other companies? If he's doing the lobbying work, why wouldn't he structure the regulations to favor his organization?
614.
Terminal.com: The Fastest Secure Linux Cloud(youtube.com)
2 points by josh2600 12y ago|0 comments
615.
by josh2600 12y ago
The market cares about uptime, and cost relative to return. Perfect should never be the enemy of the good.
616.
by josh2600 12y ago
So we implemented a variant of the Bekeley Lab Checkpoint and Restore [0] on terminal.com. You can snapshot RAM state at any given moment and commit it to disk without interrupting operations. You can use it to, for example, start a Spark c
617.
by josh2600 12y ago
You can use abstraction layers to isolate yourself from issues with the underlying metal. For example, I had a good thread the last time the maintenance reboots happened: https://news.ycombinator.com/item?id=9120289 . Solvin
618.
by josh2600 12y ago
How to run Docker in production: http://blog.terminal.com/docker-without-containers-pulldocke... When you run a docker container on terminal, we handle all of the networking and storage problems for you. In addition, we&#x2
619.
by josh2600 12y ago
If you're really worried about having to deal with reboots, you can run Terminal on top of Linode and gain the ability to live-migrate all of your workloads (so you never have to take down your application because of the underlying met
620.
by josh2600 12y ago
I have a friend who works at Patreon.com; it's a different take on this. It's basically a way to have a direct financial relationship between artists and patrons. I am curious as to how this model might work over time. It could be
621.
by josh2600 12y ago
It's faster because we made it fast. What's the difference between migrating a container with network, RAM, CPU and disk state and migrating a VM? IMHO, the difference is that the VM has a massive performance penalty and the conta
622.
by josh2600 12y ago
Or on Bare-metal. It works just the same on Xen but slower because of the VM overhead. Containers are really only part of the solution, there's a lot of other things you have to think about if you want to build a better mousetrap in th
623.
by josh2600 12y ago
It's much faster and doesn't use VMs.
624.
by josh2600 12y ago
Don't know that we have plans around that at this time. I'll try to dig and see if I can flesh out our story around this.
625.
by josh2600 12y ago
Yes. VMWare VMotion and Xen Live Migration are both VM migration tools, not containers. The difference is subtle, but important. VMs have overhead because of virtualizing the kernel, Containers don't (or rather containers benefit from
626.
by josh2600 12y ago
We are running a custom container implementation. The goal of our implementation is containers that perform like VMWare. Process isolation is hard, but we've achieved it. We currently have some tens of thousands of users on our public
627.
by josh2600 12y ago
I don't have docs yet because I haven't written them, but it's running on AWS right now. It runs inside of any hypervisor or on bare metal. Feel free to email me at josh[at]terminal[dot]com if you want to talk more. I can pee
628.
by josh2600 12y ago
We hacked the linux kernel to provide better checkpointing of RAM state and then we write the state to disk. Anyone can then summon the state from disk in the time it takes to read the SSD. It's kinda cool, or at least I think so.
629.
by josh2600 12y ago
It's a custom SDN layer we wrote.
630.
by josh2600 12y ago
We wrote a bunch of hacks to the linux kernel to do it. Custom container implementation, custom networking, custom storage. It's just really good hardcore kernel engineering. If you wanna talk more and you're in SF, come to our me

More ›