Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
polvi
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
21 ms
·
61.
▲
CoreOS internships
1 points
by
polvi
13y ago
62.
▲
Go for System Administrators
(blog.lusis.org)
174 points
by
polvi
13y ago
|
61 comments
63.
▲
by
polvi
13y ago
Optionally, by giving the container direct access to the nic. Docker will do more iptables/veth-pair magic, but if you need direct access you can use other methods. We like systemd-nspawn, since it integrates nicely with systemd.
64.
▲
by
polvi
13y ago
CoreOS is like dom0 and your containers are domUs. Shared kernel, but LXC for isolation. We need a better way to explain this...
65.
▲
by
polvi
13y ago
The project is pretty young, but we are already seeing a pretty strong community coming together: http://coreos.com/docs/etcd/#libraries-and-tools We intend to make it a primitive in CoreOS, so plan on it to just
66.
▲
Etcd v0.1.0 release
(coreos.com)
83 points
by
polvi
13y ago
|
28 comments
67.
▲
by
polvi
13y ago
Not at the moment. That said, we will be publishing raw images that should be portable to just about anything.
68.
▲
by
polvi
13y ago
Alex from CoreOS here: This only supports virtualbox at the moment, but we are actively working on adding VMware. Fill out the form on this page if you want us to spam you when we have the vmware image (or others): http://coreos.
69.
▲
by
polvi
13y ago
We're based on the ChromeOS SDKs... which use emerge to build the binaries required to assemble the distro. You can think of emerge/gentoo as the toolchain used to build all the binaries. We also pull base system packages from ups
70.
▲
by
polvi
13y ago
Sorry for the confusion, you don't need to register for anything. SDK (roll your own) docs here: http://coreos.com/docs/sdk/ Our EC2 images: http://coreos.com/docs/ec2/ 46 repos wor
71.
▲
Show HN: CoreOS, a Linux distro for containers
(coreos.com)
417 points
by
polvi
13y ago
|
97 comments
72.
▲
by
polvi
13y ago
These guys might consider allowing people to pay for more requests. Even with the source, it would be easier for some people to just pay you, and you can still keep everything open source.
73.
▲
by
polvi
13y ago
I feel like we are early enough into all of this that we might have a chance at standardization... vs the IaaS APIs which have all diverged at this point.
74.
▲
by
polvi
13y ago
I'm curious what type of deployment APIs people want. It is the docker rest API + git push for your own code? Should we be using heroku APIs? Are we going to invent something new like OpenStack did?
75.
▲
Gitian, a secure source-control oriented software distribution method
(gitian.org)
1 points
by
polvi
13y ago
|
0 comments
76.
▲
Are you the next Tomaž?
1 points
by
polvi
13y ago
77.
▲
Super rare internship with YC S13 company
1 points
by
polvi
14y ago
78.
▲
Offer HN: YC interview pep talk for upcoming candidates (Cloudkick, W09)
(alex.polvi.net)
27 points
by
polvi
14y ago
|
0 comments
79.
▲
Dabbling in the Cryptographic World--A Story
(cm.bell-labs.com)
11 points
by
polvi
15y ago
|
0 comments
80.
▲
by
polvi
15y ago
Rackspace is investing heavily into the cloud. The Cloudkick acquisition was part of that. I am extremely happy to hear that the CP was one of your major pain points, because it is one of (if not the top) priority to improve. The team that
81.
▲
by
polvi
15y ago
I'm one of the co-founders of Cloudkick (YC W09) and now part of the Rackspace. I wanted to reassure everyone that this is a migration, not "killing" off your slices. The Rackspace Cloud is based on the Slicehost technology, but has the ful
82.
▲
by
polvi
15y ago
Congrats guys!
83.
▲
by
polvi
16y ago
Another cool trick: Integrating Cloudkick tags with Fabric. Using the Cloudkick API - you can express things like "run certain_func on everything tagged 'loadbalancer'". https://support.cloudkick.com/Integrating_Fabric_with_Cloudk... We d
84.
▲
by
polvi
16y ago
Sorry - deleted my comment because it sounded too rude. We're on the same page. My argument (for those interested!) was to spend your money once you know what to do with it! No reason to wait. This is not directly related to this idea - whi
85.
▲
Video on YC and the Cloudkick acquisition
(vimeo.com)
50 points
by
polvi
16y ago
|
2 comments
86.
▲
by
polvi
16y ago
Yes, we were afraid that we would push the thing over its limits... thus smoking the turkey at 200-250F. For a little while (and you'll see it in the graph in the post) the thermometer registered 32F because we pushed it too far. Once we go
87.
▲
Cloudkick (YC W09) now supports multi-factor authentication
(cloudkick.com)
23 points
by
polvi
16y ago
|
6 comments
88.
▲
by
polvi
16y ago
Why would google do this?
89.
▲
by
polvi
16y ago
I feel like we should give the moderators benefit of the doubt on this one. HN has been gradually shifting away from quality content, so any effort to correct that is kindly appreciated. Like any process, mistakes are occasionally made.
90.
▲
by
polvi
16y ago
We do pretty exactly what you described on the monitoring overview -- except for the filter in #1. Great feedback, however, and we will look at including that! This is a very different take on visualizing your infrastructure. I encourage yo
More ›