Relevant links:

• https://technologyconversations.com/2017/01/23/using-docker-stack-and-compose-yaml-files-to-deploy-swarm-services/

1. Check the existence of a default route that goes thru 192.168.0.1
2. Do not add the default 192.168.0.1 default route to the gateway

Depends on #22

Useful links:

• See --dhcp-host, --expand-hosts options in the dnsmasq man page
• https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol#DHCP_options
• http://www.syslinux.org/wiki/index.php?title=PXELINUX#Configuration
• https://wiki.openwrt.org/doc/howto/dhcp.dnsmasq
• https://wiki.archlinux.org/index.php/PXE
• http://jblevins.org/log/hostname

• Username: ferrarimarco
• Extended Name: Marco Ferrari
• Email: [email protected]

Relevant links:

• https://security.stackexchange.com/questions/45712/how-secure-is-nopasswd-in-passwordless-sudo-mode
• https://serverfault.com/questions/580881/is-it-ok-to-set-up-passwordless-sudo-on-a-cloud-server
• https://github.com/boxcutter/ubuntu/blob/master/script/vagrant.sh

• http://myatus.com/p/poor-mans-device-discovery-dns/
• https://blogging.dragon.org.uk/howto-setup-dnsmasq-as-dns-dhcp/
• http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html
• https://www.linux.com/learn/dnsmasq-easy-lan-name-services

• Choose a Vagrant box
• Configure Network
• Configure hostname
• Configure connection specific DNS suffix

Remember to update europa.ferrari.home network configuration: gateway 192.168.0.1

Let's use the one provided by the home router.

It's not needed and hurts production parity.

Two instances cannot listen on the same machine, given that we are using the --net=host option when launching containers

Docker does not currently support 32-bit environments.

DHCP clients are not reachagle because DNSMASQ receives a request for HOSTNAME.ferrari.home.ferrari.home (double suffix).

Remove the command to install sshpass after ferrarimarco/open-development-environment-ansible#26 is resolved

SSH Keys must be set up to allow SSH access. This should me automatically managed with Ansible.

See:

• https://carlosbuenosvinos.com/github-ansible-deploy-your-public-ssh-keys-to-your-server/
• http://blog.scottlowe.org/2015/05/26/bootstrap-servers-ansible/

Possible implementation:

- name: Ensure SSH keys are installed
  authorized_key: user=root key=https://github.com/{{ item }}.keys
  become: yes
  with_items:
    - ferrarimarco

The network stack is composed (for now) of:

• DHCP
• PXE

Useful links:

• http://blog.arungupta.me/deploy-docker-compose-services-swarm/
• https://rock-it.pl/my-experience-with-docker-swarm-when-you-need-it/
• https://docs.docker.com/engine/swarm/stack-deploy/#set-up-a-docker-registry
• https://technologyconversations.com/2017/01/23/using-docker-stack-and-compose-yaml-files-to-deploy-swarm-services/