Service Management in Networks - Leischner

Practice sheet 10 - DockerSwarmLab (1 Point)

 

Task 1 - Docker Swarm

Customize your Vagrantfile so that the comand vagrant up automatically installs an environment swarm environment DockerSwarmLab .

Please comply with the following instructions:

  • The number of swarm managers manager1, manager2, manager3, ... is controlled by the constant NUMBER_OF_NODES .
  • The manager manager1 creates a swarm, to which the other nodes are joining.

 

Task 2 - Swarm Management Tools

Install the docker swarm management tools portainer and visualizer on your DockerSwarmLab. The two tools are started automatically together with the laboratory by the command vagrant up.

 

Task 3 - Docker Services

Start the services from practice sheet 9 in  your DockerSwarmLab as docker swarm services.

 

Task 4 - Define and run some interesting scenarios

Scaling and fault tolerance are important features of Docker Swarm networks. Consider some scenarios to test these properties in your DockerSwarmLab. Prepare a demo that you can present in the next course. The tools portainer and visualizer will help you to do this.

 

Task 5 - Consolidation of the laboratory environment

Assume that the laboratory you have developed is to be used in other courses. This means that the main requirement for the laboratory is that it must be possible to further develop the laboratory DockerSwarmLab with little effort. Consolidate your laboratory environment so that it meets this rquirement and can be qualified as a best practice project. In particular, perform the following tasks:

  • Comment on your programs in detail so that the concepts you have followed come out clearly.
  • Denote all objects with clearly understandable names.
  • Revise the structure of your vagrant environment. Is your source tree well organized? Adjust the folder structure and the names of folders if necessary.
  • In the course, we tested various provisioning methods. For a consolidated environment, it makes sense (of course only as far as possible and as far as it is practical) to commit to one method and use it with a clearly defined set of rules. Does your lab meet these requirement or do you need to make adjustments?
  • Ansible gives you great freedom in the provisioning process, both in writing the code and in structuring the information. Please consolidate your ansiblle code, if necessary.
  • Remove redundant or no longer needed code.
  • Provide your GIT with a helpful and meaningful README.md.

Result of this task should be a best practice DockerSwarmLab.

 

 

 

 

 

 

Please, submit your answers of the questions as pdf and the git code vagrant.zip as a zip file to LEA - Lernen und Arbeiten online .

 

Impressum | Datenschutz | leischner.inf.h-brs.de, last modification: 05.12.2018-08.02