Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

HashiCorp – S1

sec.gov

Post reply on HN
Print view View original

261–270 of 277 posts

Re: HashiCorp – S1

#261

Post by handrous »

sillysaurusx wrote: post #237
handrous wrote: post #112

Earlier quoted context omitted.

> Docker You can basically just treat it like a package manager and config-assistant. It's often easier(!) to configure a Docker image than the corresponding package, or set of packages, in your typical distro. In part this is because documenting where all the config files and data live just kinda falls naturally out of creating a half-decent image, and in part because good images often put commonly-modified config o…

It's often easier(!) to configure a Docker image than the corresponding package, or set of packages, in your typical distro. My original reply was going to be something along the lines of "Bwahahahaha" followed by a comparison of how many seconds it takes to `pip3 install torch` vs how many hours you'd rip your hair out trying to get that running in Docker, let alone on a GPU, and let alone in a way that you can actu…

Oh no, I agree that it's not worth learning to package your "app" with docker that way unless you're planning to make it a big part of your processes, to reap the benefits.

It's just excellent for replacing other methods of installing & configuring daemons you're dependent on, especially if you're already in a "doing things wrong" kind of space (and hey, you and me both).

Very nearly all of my use of it doesn't involve modifying or customizing containers at all, and just lets me use one set of commands to manage packages across most platforms and pin them to my desired version without having to care much about the underlying OS, for dependencies like database systems, entire software packages that I don't need to modify aside from config (as in my personal use of it for things like Jellyfin and a Minecraft server), et c.

My server at home runs Debian Stable. Very little of what I use it for is available in the official repos at all. Docker, though? They're all available at the latest version, with a bunch of older versions available too, just as easily. And if I switch distros out from under them, or upgrade Debian, nothing happens. I just run the same stuff, and it works.

Re: HashiCorp – S1

#262

Post by handrous »

lifeplusplus wrote: post #186
handrous wrote: post #112

Earlier quoted context omitted.

> Docker You can basically just treat it like a package manager and config-assistant. It's often easier(!) to configure a Docker image than the corresponding package, or set of packages, in your typical distro. In part this is because documenting where all the config files and data live just kinda falls naturally out of creating a half-decent image, and in part because good images often put commonly-modified config o…

It's like git. You can get by for a while but when anything out of ordinary happens your understanding needs to go from 2% to 95% very quick. With apps that are really good at package management I fail to see need of docker. Ie node, and go lang.

Oh no, I practically never package my "app" with docker. I use it to install stuff like postgresql, and ensure it's at the same version & configured the same everywhere, regardless of the underlying distro (or even OS), using the same tools no matter where it's running.

Re: HashiCorp – S1

#263

Post by handrous »

remram wrote: post #196
__jem wrote: post #108

Earlier quoted context omitted.

Docker at this point is just a wrapper around OCI spec… why would you go back to Vagrant rather than just using any of the other tools that can build OCI images? Vagrant and Docker seem like fundamentally different tools to me.

Vagrant can use containers, making it also a wrapper around OCI-compatible runtimes. In addition, it also supports VirtualBox, Hyper-V, VMWare, bare metal, SSH targets, and various cloud providers. The real conclusion from your logic would be: why would you go to Docker rather than just using Vagrant?

> The real conclusion from your logic would be: why would you go to Docker rather than just using Vagrant?

I use Docker as a nigh-universal package repository and package manager, with a huge and up-to-date selection of packages. It gives me a consistent way to run daemons my software depends on, nearly everywhere, including pinning the version and ensuring they all use the same config. It's docker-hub, really, that provides most of the value I get from Docker on a day-to-day basis, and that's the part I'd miss. I know there are other ways to create images and run containers, but I almost never create—or even modify—them myself.

Re: HashiCorp – S1

#264

Post by aliswe »

secfirstmd wrote: post #173
whimsicalism wrote: post #168

Earlier quoted context omitted.

I've applied to plenty of much larger and established companies without getting a thanks but no thanks. Twitter has the audacity to email a year after my application to let me know that I was "still under consideration." Google ended my hiring loop by having my emails to my recruiter bounce. So this is not just a shaky company problem.

My Twitter experience: Applied, rejected within a day, got an email from a hiring manager four weeks later asking me to re-apply, very sorry etc etc, bad screener he had to look over everything again. I re-apply, two interviews, asked to do a presentation and then a video on strategic threats to the org, spent two days of my holiday doing it (tight schedule from Twitter), sent, no reply for two weeks, get an email ba…

contact their head of hr/recruitment.

Re: HashiCorp – S1

#265

Post by hangonhn »

abledon wrote: post #174
hangonhn wrote: post #51

Congratulations! The IPO is a confirmation of what many of us in this field already knew: Hashicorp makes amazing tools. I love Consul so much. I'm glad the larger world will appreciate the great work Hashicorp has done as well.

quick anecdote of your success w/consul?

I used it to build a highly available and fault tolerant Nagios cluster. I used Consul for health monitoring, KV store, and leadership election.

Re: HashiCorp – S1

#266

Post by denysvitali »

Aperocky wrote: post #177
Sebguer wrote: post #130

Earlier quoted context omitted.

Does this account for how much those companies offload to contractors / staffing agencies?

The economy of scale - at FAANG(MAANG?) scale you can have extremely efficient money making features that only takes a few engineer to support thousands. For things that are completely software, it does not surprise me that millions per employee in earnings is realized - that's just what happens when you operate at that scale. And that's accounting for all of the overhead in personnel that scale entails.

OT: if you want to start with M, then the correct name would be MAANA

Re: HashiCorp – S1

#267

Post by heleninboodler »

sillysaurusx wrote: post #237
handrous wrote: post #112

Earlier quoted context omitted.

> Docker You can basically just treat it like a package manager and config-assistant. It's often easier(!) to configure a Docker image than the corresponding package, or set of packages, in your typical distro. In part this is because documenting where all the config files and data live just kinda falls naturally out of creating a half-decent image, and in part because good images often put commonly-modified config o…

It's often easier(!) to configure a Docker image than the corresponding package, or set of packages, in your typical distro. My original reply was going to be something along the lines of "Bwahahahaha" followed by a comparison of how many seconds it takes to `pip3 install torch` vs how many hours you'd rip your hair out trying to get that running in Docker, let alone on a GPU, and let alone in a way that you can actu…

> And yet, as I go from company to company, I keep being surprised to find zero people using Docker.

Well that's pretty astounding. I work on a service at a Very Large Company that intercepts each docker container as it passes into our production-deployable repos and it inspects about 100 containers per hour. This isn't every build, it's every actual prod deployment. Mind you, we have lot of services doing deployments, but the ones that aren't using docker are in the vast, vast minority.

I think one thing docker brings you is consistency. At our level of scale, you can't be doing "pip install"s on random hosts or you'd never be able to say what state everything is in. Docker isn't the only way to do this, of course, but it's one way. And I'm super happy that other teams the produce tools built on piles of python now package them as docker containers on a standard base so I can just run them rather than spend a day untangle my completely-hosed python environment every few months.

Re: HashiCorp – S1

#268

Post by jordanbeiber »

nuker wrote: post #244
nsotelo wrote: post #233

Earlier quoted context omitted.

There are many scenarios where it's useful, but I will illustrate a simple and important one. When you do a rolling upgrade, a new service must be assigned to an available port different to the existing one. After starting you'll probably run some health checks, and once satisfied you'll want to switch traffic over to the new instance and halt the old. How do you tell the rest of your infrastructure what the new port…

I make a new stack, new VMs, new loadbalancer and just update dns record of the service from old stack to new. Thats blue-green. Rolling is trickier, but still, native cloud solutions do not use service discovery, imho.

What you’re describing took place with on-prem iron as well - nothing cloud about it. At all.

Service discovery is in part DNS with low ttl, but there’s a part of it that ties in to configuration management, monitoring and observability as well.

If you “update dns” that means you’re doing a part of what consul does (only f ex nomad does it for you). Nothing magic, but you still “need it”.

Tags and metadata is a large part of it though, as well as configuring things automatically based on state of the SD and K/V.

In the end - whatever works, I guess.

Re: HashiCorp – S1

#269

Post by NicoJuicy »

johanj wrote: post #241
adeelk93 wrote: post #211

Earlier quoted context omitted.

YouTube and Fitbit come to mind

Both are subsidiaries of Google, not Alphabet.

Chromecast Android ChromeOS

I think Oculus is much more similar to Stadia than something else too.

Additionally, all of those platforms you mention du the same thing: chat and share pics.

Re: HashiCorp – S1

#270

Post by secfirstmd »

aliswe wrote: post #264
secfirstmd wrote: post #173

Earlier quoted context omitted.

My Twitter experience: Applied, rejected within a day, got an email from a hiring manager four weeks later asking me to re-apply, very sorry etc etc, bad screener he had to look over everything again. I re-apply, two interviews, asked to do a presentation and then a video on strategic threats to the org, spent two days of my holiday doing it (tight schedule from Twitter), sent, no reply for two weeks, get an email ba…

contact their head of hr/recruitment.

I took an offer elsewhere. Twitter would have been fun as Mudge was invoked with that team.
Post reply on HN