News for hackers. Stuff that matters.

A comment on Container orchestration: Moving from fleet to Kubernetes. Parent comment

Re:Container orchestration: Moving from fleet to Kubernetes by schmichael on Tuesday February 07, 2017 @05:11PM (#13593390)
Nomad dev here. We should definitely tick the simplicity box for you. If not, let me know. :)

Nomad is a single executable for the servers, clients, and CLI. Just download[0] & unzip the binary and run:

    nomad agent -dev > out &
    nomad init
    nomad run example.nomad
    nomad status example
And you have an example redis container running locally!

Nomad supports non-Docker drivers too: rkt, lxc templates, exec, raw exec, qemu, java.[1] To use the "exec" driver that doesn't use Docker for containerization you'll need to run nomad as root.

[0] https://www.nomadproject.io/downloads.html

[1] https://www.nomadproject.io/docs/drivers/index.html

[ Parent | on HN ]
Re:Container orchestration: Moving from fleet to Kubernetes by mercur1o on Tuesday February 07, 2017 @06:14PM (#13593921)
Nomad user here. No k8s experience. I have been using it for more than 6 months (docker container + short running jobs). If I can name the main features I like: deployment simplicity, responsive scheduling, disaster recovery and service discovery integration.
[ Parent | on HN ]
Re:Container orchestration: Moving from fleet to Kubernetes by pslijkhuis on Wednesday February 08, 2017 @01:31AM (#13596274)
Completely unusable product for us because of the lack of persistent storage.
[ Parent | on HN ]
Re:Container orchestration: Moving from fleet to Kubernetes by schmichael on Wednesday February 08, 2017 @06:13PM (#13603111)
Sorry to hear that! We've definitely focused on stateless containers until 0.5 which introduced sticky volumes and migrations. Useful in some cases but definitely doesn't cover all persistent storage needs.

Extensible volume support will be coming in the 0.6 series via plugins.

[ Parent | on HN ]