SE4 Virtualisation TP Wasilewski

De wiki-se.plil.fr
Aller à la navigation Aller à la recherche

Déroulé du TP

Target: discover technologies and use a web server

1. Create VM

  1. Create a virtual machine on Proxmox (server is accessible through: this link) by cloning the template. The virtual machine must be named team-XX with XX being your team number assigned at the beginning of the tutorial.
  2. Manual configure virtual machine's network to be persistent. Your VM's IP must be 10.99.XX.1/16 with the gateway being 10.99.99.254.
  3. Update /etc/hostnameto reflect the VM's name to the hostname
  4. Update /etc/hosts with the two previous updates
  5. Ensure it can ping google.
  6. Reboot the VM and validate it.

2. First web server

  1. Install nginx. (Hint: if it fails, do not forget to configure your VM's DNS).
  2. Setup a custom/cool static page.

3. First load balancer

  1. Install HAProxy 2.8 (Hint: Search "debian haproxy" on your favorite search engine)
  2. Redirect port 8888 to the previously installed nginx.

4. Docker time

  1. Install docker.
  2. Pull nginx image.
  3. Copy your custom static page into the container.
  4. Reconfigure HAProxy to use port 8889 onto the container.

Target: discover technologies and use a web server

5. First Docker image

  1. Create a Docker image based on nginx:latest that use your previously created static page. This image will be named tXX-web and will use semantic versioning.
  2. Publish this new image on the common registry, located at http://10.99.99.254:5000. (Hint: you will have to update your Docker daemon configuration to allow this insecure registry).

6. Nomad installation

  1. Install nomad as a Debian package. See the official documentation
  2. Have Nomad running as client and server. Validate it through its interface which should be accessible through http://10.99.XX.1:4646. (Check it with curl)

7. Access Nomad UI from Zabeth

  1. Add a route on your Zabeth to view Nomad UI from it.

8. First Nomad deployment

  1. Create a nomad job definition with nomad job init command.
  2. Adapt it to deploy the container you created on step 5.

9. Scale and load-balance

  1. Increase job definition count to run 3 container.
  2. Configure HAProxy to redirect port 8890 to those containers through service discovery.

Target: setup a distributed service + deploy from CI

10. Your Nomad joins the common cluster

Reconfigure nomad to use the common consul and common nomad server

11. Starting the "DevOps" way

Create git repo on Gitlab / Store dockerfile + static page

12. Automating deployments

Update job definition in repo / setup CI / deploy new configuration to global nomad

13. Releasing your website to the wild

Update global HAProxy configuration to redirect to the the newly deployed web service.

Your website should now be accessible through http://tXX.se4v.plil.info

Target: build and deploy more complex services

14. Creation of DHCP server

Create new repo as the web repo to build and push a dockerized DHCP server

15. Creation of TFTP server

Create a new repo as the web repo to build and push a dockerized TFTP server with ipxe

16. Creation of your custom Debian image

Create a new repo to build and push on S3 a debootstrap image of latest debian version

Target: boot an OS from the network

17. Host iPXE configuration

Update web server to host an ipxe configuration file boot this new OS

18. Create a remote block disk and use it

Mount `/home/xxx` as rbd volume from Ceph

Now the new OS boots and use remote storage for users.

Extra parts for experimented SE4

Target: build a custom OS

19. Your first kernel

Build a kernel (Bonus: less than 50 Mo + boot time < 2s)

20. Your first init

Build an init that displays your team ID on the terminal (Bonus: pimped init banner)

21. Your second init

Build an init that starts network interfaces

Target: create a logging service

22. Even further with init

Create a script / service that request user credentials, checks its validity against /etc/passwd, then mount dynamically user's home from rbd

23. Finally, a working UI

Improve script and update initrd to have a window manager starting after logging

Notation des élèves

La notation du TP est décomposée en deux parties.

14 points sont liés à l’achèvement des différentes étapes décrites précédemment.

6 points sont liés à la performance. En effet; à la fin de chaque étape, il sera noté le classement des équipes.

Equipe \ Etape 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Récupérée de « http:///mediawiki/index.php?title=SE4_Virtualisation_TP_Wasilewski&oldid=5473 »