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

Nomad v1.0 release – workload orchestration

github.com

Post reply on HN
Print view View original

1–10 of 27 posts

Re: Nomad v1.0 release – workload orchestration

#3

Post by mike1o1 »

I really like the idea of Nomad as a simpler alternative to Kubernetes. The documentation is great and provides a lot of examples, but I wish I could find a starter guide on how to deploy a complete application with it and Consul. Something like, here’s how to deploy a Rails app with Sidekiq workers and database migrations.

This along with Waypoint seems like a great solution for smaller side projects.

Re: Nomad v1.0 release – workload orchestration

#4

Post by gavinray »

schmichael wrote: post #2

There's a blog post as well. I'm unsure what makes for the most relevant link: https://www.hashicorp.com/blog/announcing-general-availabili... I'm the Nomad Team Engineering Lead and would be happy to answer any questions people might have.

I'm a big fan conceptually of Nomad, and I love the streams that the Nomad team does to talk about development and answer questions.

My only comments would be:

I wish there was more content available (maybe on HashiCorp Learn Nomad) for working with single-instance Nomad clusters.

And a demo of realworld dev-to-prod workflow. Something like "Okay here's a local Docker Compose setup with Postgres, a backend API, and a frontend web app, and here's the workflow for getting it into production with Nomad."

Re: Nomad v1.0 release – workload orchestration

#6

Post by cs-szazz »

schmichael wrote: post #2

There's a blog post as well. I'm unsure what makes for the most relevant link: https://www.hashicorp.com/blog/announcing-general-availabili... I'm the Nomad Team Engineering Lead and would be happy to answer any questions people might have.

First off, very cool. I'm a big Hashicorp fan, and have been following Nomad for a while, so it's exciting you hit 1.0!

It seems to me one of the advantages K8s has is that there are multiple "Kubernetes as a Service" services out there, such as EKS on AWS, Google Cloud's offering, even Digital Ocean.

Are there any plans to make Nomad Enterprise more accessible? It seems a managed Nomad hits the sweet spot of simple scheduling, which removes a lot of the K8s bloat for many people.

Re: Nomad v1.0 release – workload orchestration

#7

Post by schmichael »

gavinray wrote: post #4
schmichael wrote: post #2

There's a blog post as well. I'm unsure what makes for the most relevant link: https://www.hashicorp.com/blog/announcing-general-availabili... I'm the Nomad Team Engineering Lead and would be happy to answer any questions people might have.

I'm a big fan conceptually of Nomad, and I love the streams that the Nomad team does to talk about development and answer questions. My only comments would be: I wish there was more content available (maybe on HashiCorp Learn Nomad) for working with single-instance Nomad clusters. And a demo of realworld dev-to-prod workflow. Something like "Okay here's a local Docker Compose setup with Postgres, a backend API, and a…

Thanks that's great feedback and you're not alone in that desire.

We do "small" users a pretty big disservice by effectively dismissing single-server deployments and jumping straight to "real" production deployments (3+ servers distinct from the nodes that run workloads).

We have people who use Nomad locally as a systemd alternative. We have people who use single-scheduler-multiple-nodes clusters at home or at work, and it works quite well! If the scheduler crashes, work continues to run uninterrupted, so there's little reason not to start small and scale up.

The problem is largely that it's tricky to separate out and accurately address these various personas. People looking for a systemd alternative are obviously highly technical and will likely figure everything out through experimentation. However, "small" cluster users need to be carefully educated on the differences between an HA cluster (3+ schedulers) and a single scheduler cluster.

Not only that, but we would need to automate testing for each of these recommendations to ensure changes don't break an official recommendation.

Re: Nomad v1.0 release – workload orchestration

#8

Post by schmichael »

cs-szazz wrote: post #6
schmichael wrote: post #2

There's a blog post as well. I'm unsure what makes for the most relevant link: https://www.hashicorp.com/blog/announcing-general-availabili... I'm the Nomad Team Engineering Lead and would be happy to answer any questions people might have.

First off, very cool. I'm a big Hashicorp fan, and have been following Nomad for a while, so it's exciting you hit 1.0! It seems to me one of the advantages K8s has is that there are multiple "Kubernetes as a Service" services out there, such as EKS on AWS, Google Cloud's offering, even Digital Ocean. Are there any plans to make Nomad Enterprise more accessible? It seems a managed Nomad hits the sweet spot of simple…

Thanks! I think you really hit the nail on the head. In a twitter thread I talk about how Nomad 1.0 represents us implementing the "table stakes", the base foundation, for an orchestrator. However, I think what you're noticing is how the table stakes have changed from 5 years ago: orchestrators need hosted options. k8s has push-button support from every major cloud. We can't just ignore that.

And we aren't ignoring that. I have no idea what I can say publicly, so I'll just link to what our cofounder/CTO has already said:

> And hosted Nomad clusters are on the way

https://twitter.com/mitchellh/status/1334198278225682434

Re: Nomad v1.0 release – workload orchestration

#9

Post by ofrzeta »

mike1o1 wrote: post #3

I really like the idea of Nomad as a simpler alternative to Kubernetes. The documentation is great and provides a lot of examples, but I wish I could find a starter guide on how to deploy a complete application with it and Consul. Something like, here’s how to deploy a Rails app with Sidekiq workers and database migrations. This along with Waypoint seems like a great solution for smaller side projects.

I like it, too, but with the integration of CNI it's no longer so much simpler than Kubernetes. Where Kubernetes has etcd Nomad requires Consul which arguably might be simpler.

To compete with Kubernetes Nomad will most likely acquire more features (e.g. storage) until it's as complex as Kubernetes because it's just what some businesses seem to want.

On the other hand Kubernetes gets simpler with projects like k3s or k0s.

Re: Nomad v1.0 release – workload orchestration

#10

Post by cs-szazz »

schmichael wrote: post #8
cs-szazz wrote: post #6

Earlier quoted context omitted.

First off, very cool. I'm a big Hashicorp fan, and have been following Nomad for a while, so it's exciting you hit 1.0! It seems to me one of the advantages K8s has is that there are multiple "Kubernetes as a Service" services out there, such as EKS on AWS, Google Cloud's offering, even Digital Ocean. Are there any plans to make Nomad Enterprise more accessible? It seems a managed Nomad hits the sweet spot of simple…

Thanks! I think you really hit the nail on the head. In a twitter thread I talk about how Nomad 1.0 represents us implementing the "table stakes", the base foundation, for an orchestrator. However, I think what you're noticing is how the table stakes have changed from 5 years ago: orchestrators need hosted options. k8s has push-button support from every major cloud. We can't just ignore that. And we aren't ignoring t…

Thanks! I wish Hashicorp the best of luck getting hosted clusters out the door, totally agree with you about table stakes.
Post reply on HN