Skip to content

Docker, Consul and Nomad (and soon Vault) on systemd using cloud-init.

License

Notifications You must be signed in to change notification settings

diogok/systemd-nomad

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

15 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Systemd Hashcorp Nomad

Scripts and config to provision Hashistack on systemd systems using cloud-init.

Includes:

  • docker
  • cni plugins
  • consul
  • nomad

It can be used as a reference, as a terraform module (maybe...) or to generate and use cloud-init using terraform.

To do:

  • vault

Cloud-init

Testing local

You can test using multipass and terraform.

To launch server:

make launch-server

To launch client:

make launch-client

To see IPs and machines:

make list

More information

  • We setup max_map_count and max open files (fs.file-max)
  • We create a docker network called just network
  • The docker internal network will be 10.2.2.0/24
  • The docker network will have host exposed to the containers at 10.2.2.1
  • Connect is enabled on consul
  • The machine default DNS is set as rescursive DNS on consul
  • Nomad has prometheus metrics endpoint enabled
  • Nomad have docker privilieged and raw exec enabled
  • Nomad is connect enabled
  • Set client or server vars accordingly
  • Set bootstrap_expect var only on first manager
  • It is all managed on systemd
  • Use "join" var to set a seed node ip or cloud auto join string

License

MIT

About

Docker, Consul and Nomad (and soon Vault) on systemd using cloud-init.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published