Project requirements

Internal Tools:

1.Vagrant setup of 3 vms witch will cover:

- 2x gogs/other git+knowledge base+ticketing system  server

- 3x gluster (3node setup) - each vm should have additional storage for that purpose.

 

Hosts descriptions

VM1
|_ network 192.168.7.XX (connected to enp4s0)
|_ network 10.10.10.1 (connected to brY)
|_ network for vagrant connectivity
|_ dockerized gogs app with mapped storage of gluster listening only on 192.168.7.XX on ports 80,443,22
|_ dockerized gluster listening only on 10.10.10.1

VM2
|_ network 192.168.2.XX (connected to enp7s0.4)
|_ network 10.10.10.2 (connected to brY)
|_ network for vagrant connectivity
|_ dockerized gogs app with mapped storage of gluster listening only on 192.168.2.XX on ports 80,443,22
|_ dockerized gluster listening only on 10.10.10.2

VM3
|_ network 10.10.10.3 (connected to brY)
|_ network for vagrant connectivity
|_ dockerized gluster listening only on 10.10.10.3

 

inscription:
brY - name of bridge created on kvm (everyone should have different - my example "br0")
192.168.2.XX - ip address for network enp7s0.4 (XX higher than 100, everyone should have different - my example "192.168.2.111")
192.168.7.XX - ip address for network  enp4s0 (XX higher than 100, everyone should have different my example "192.168.7.111")

2.Data Flow Diagram

3.Network Flow Diagram

4.Monitoring
|_zabbix agent on vms
   |_ free storage checks
   |_ service running checks

ALL work should be commited into github as a pull request of your name directory to repository /gogs-gluster (my example - karol)