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

How we use HashiCorp Nomad

blog.cloudflare.com

Post reply on HN
Print view View original

81–90 of 166 posts

Re: How we use HashiCorp Nomad

#81

Post by tetha »

rossmohax wrote: post #78
schoolornot wrote: post #41

I'm surprised Hashicorp hasn't repositioned this product. Terraform was a huge breath of fresh air after Cloudformation. If you ask me, deploying apps via k8s is even better. Everyone wants a free lunch and for me, momentum + cloud vendor support + ultimately the Nomad Enterprise features that come free with K8s made the choice easy.

TF can be often suffocating still. Pulumi runs circles around it, when it comes to user experience in writing complex, modular, composable and reusable configurations.

Except now you have to deal with javascript. It's hard enough to turn some operators towards an IaC approach, but throwing Javascript at them isn't going to help.

Re: How we use HashiCorp Nomad

#82

Post by q3k »

AlphaSite wrote: post #72
q3k wrote: post #63

Earlier quoted context omitted.

ytt is even more templating-yaml-with-yaml, so it all ends up being a bargain bin Helm. There's no reason to do this over just serializing plain structures into YAML/JSON/...

It avoids the whole set of issues you get with templating yaml with helm since its structure aware. Also you can actually write pure code libraries in starlark (basically a subset of Python)

I'm aware, but I just don't understand the point of it. How is it in any way better than a purpose-specific configuration language like Dhall/CUE/Jsonnet? What's the point of having it look like YAML at all?

Re: How we use HashiCorp Nomad

#83

Post by schmichael »

tetha wrote: post #68
schmichael wrote: post #17

Earlier quoted context omitted.

Preemption is going OSS! https://github.com/hashicorp/nomad/blob/master/CHANGELOG.md We fully intend to migrate more features to OSS in the future -- especially as we build out more enterprise features. As you can imagine building a sustainable business is quite the balancing act, and there's constant internal discussion. (I'm the Nomad Team Lead at HashiCorp)

This is going to make our AI team very happy because they can just dump experiments into the cluster at low-priority so those'll be done when those are done. It's also going to make the operators very unhappy because it'll be harder to monitor actual memory utilization (allocated memory vs memory really in use) in order to plan cluster extensions. Are there some tools around or work planned to make this kind of scali…

I was going to say "yes!" because we do have some telemetry/metrics improvements coming up, but then I realized those won't address your use case. It seems like aggregating cluster resource usage by job priority is what we need for that. Our UI might be able to calculate that, but I don't think our metrics include job priority so there's no way for your existing tooling to display it.

Please file an issue or link me to an existing issue of you have time. This seems really compelling!

Re: How we use HashiCorp Nomad

#84

Post by toomuchtodo »

4636760295 wrote: post #76
otterley wrote: post #65

Earlier quoted context omitted.

Nomad is open source (or, at least, a significant subset of it is). Anyone is able to continue to improve it, even if Hashicorp is no longer paying people to work on it.

I used to do sales for an enterprise "open source" software product, so I get it, but the truth is as soon as someone stops paying people to keep the project going it will die.

Who pays for k8s development?

Re: How we use HashiCorp Nomad

#85

Post by [deleted] »

schmichael wrote: post #17
q3k wrote: post #10

Earlier quoted context omitted.

The free version of Nomad is missing, IIUC: - no quotas for teams/projects/organizations - no preemption (ie higher priority job preempts lower priority job) - no namespacing So generally it's somewhat useless in organizations where there are multiple different teams that should be able to coexist on a cluster without stepping on eachothers' toes, or even where you want a CI system to access the cluster in a safe man…

Preemption is going OSS! https://github.com/hashicorp/nomad/blob/master/CHANGELOG.md We fully intend to migrate more features to OSS in the future -- especially as we build out more enterprise features. As you can imagine building a sustainable business is quite the balancing act, and there's constant internal discussion. (I'm the Nomad Team Lead at HashiCorp)

[deleted]

Re: How we use HashiCorp Nomad

#86

Post by jugg1es »

I love nomad and architected a large system that used it for several years. We are finally moving away from it, however, because of its lack of native support for autoscaling. I know there are third party solutions for it, but that doesn't work for us. I suspect a large number of k8s users could use nomad instead with way less overhead.

Re: How we use HashiCorp Nomad

#87

Post by sciurus »

rayanimesh wrote: post #30
ognyankulev wrote: post #11

Earlier quoted context omitted.

Helm charts are declarative way of deploying app(s) and their accompanying resources.

> Helm charts are declarative way of deploying app(s) and their accompanying resources. How do you make helm chart deployment declarative? `helm install` is not declarative (in my understanding `kubectl apply` is declarative and `kubectl create` is not. Let me know if my understanding of declarative is wrong). Thanks.

`helm template | kubectl apply` ?

Re: How we use HashiCorp Nomad

#88

Post by sciurus »

4636760295 wrote: post #3

I worked at a hedge fund that also used nomad. The problem, however, is not how well it scales or whatever, but the fact that all the accompanying deployment info and literature is for kubernetes, and k8s has far more features. I like the quality of products from HashiCorp, but k8s is far, far, ahead of where nomad is. What I really want is better integration for Terraform and kubernetes. The current TF k8s support l…

Looked at https://www.hashicorp.com/blog/deploy-any-resource-with-the-... ?

Re: How we use HashiCorp Nomad

#89

Post by closeparen »

toomuchtodo wrote: post #84
4636760295 wrote: post #76

Earlier quoted context omitted.

I used to do sales for an enterprise "open source" software product, so I get it, but the truth is as soon as someone stops paying people to keep the project going it will die.

Who pays for k8s development?

Google. Commoditizing the cloud is their strategy to make GCP relevant.

Re: How we use HashiCorp Nomad

#90

Post by jjeaff »

waynesonfire wrote: post #20
chucky_z wrote: post #5

Cloudflare, make sure you upgrade to 0.11.3, the new scheduling behavior is awesome for large clusters. Also a massive warning to anyone wanting to use hard cpu limits and cgroups (they do work in nomad it’s just not trivial), they don’t work like anyone expects and need to be heavily tested.

are you serious? you've got a major company touting a technology and a key component of it is broken?

Ha, have you ever tried kubernetes?
Post reply on HN