I803 IT Infrastructure services

From ICO wiki
Revision as of 11:48, 16 November 2016 by Asepter (talk | contribs) (→‎Lectures)
Jump to navigationJump to search


I803 IT Infrastructure services

Introduction

Lecturer

Andres Septer >> andres (.) septer (ät) itcollege (.) ee

form of graduation

Comprehensive examination, ECTS 6

Important links

Structure

  • Lectures (I explain stuff)
  • Excercises – practical tasks with easy-to-follow step-by-step instructions. Practicing themes discussed in lectures.
  • Labs – same as exercises, except no step-by-step instructions. You have to find all the necessary information by yourself (Though there is some hints) and solve the problems independedly.

Premises

  • Basic understanding how Operating System and services work
  • Basic Linux shell experience
  • Basic understanding how TCP/IP networking works

We DO repeat some (critical) stuff you learned previously (but not all)

Topics covered

  • Introduction. Seminar: IT Infrastructure and it's components.
  • core services: DHCP, DNS, NTP jms.
  • web services (from Infra admin point of view)
  • Documenting
  • Backup and Archive
  • Monitoring and log aggregation
  • Redundancy and high availability
  • Automation
  • Virtualization
  • Additional themes may add up

Grade

  • You do series of labs and present them to lecturer.
  • All labs have minimum achievements that MUST be met.
  • All labs are mandatory (at least minimum level)
  • All labs must be ready at due date
  • Lab minimums sum up as 50 points. You need at least one additional point to get graded.
  • Additionally you you have to do one 5-minute presentation about IT as teamwork

WAT Presentation

  • Presentation is mandatory homework, as labs. You have to do it, to grade.
  • You have to do it on time.
  • Teams are formed by lecturer. Also I promote team leaders.
  • Team size will depend on how many people attends to course in any given year. (usually 3-4 members per team)

Your task explained

Do a presentation about some major (braindead) design flaw or security hole or misfeature in some Protocol, Operating System, Programming Language, Service, etc. It should not be about some usual misconfiguration problem. Your presentation must rise a questions like: „What they where thinking?“ „Are people who designed this, totally braindead?“, „WAT?“

Your presentation gets valued higher if it's based on real life experience. I.e. member of your team has encountered this problem firsthand and wasted a time to solve a problem that should not exist at all.

If no-one at your team has had such an experience use google. You probably want to search about Windows but Linux and all programming languages contain enough „WAT“s.

Presentation should be comprehensive (and suggestionally funny) describing the problem (and solution, if you have one). Length about 5 minutes, no more than 7 minutes.

Team will be avarded 0—4 points, depending on your performance.

Some examples and materials

Team leader responsibilities

Team leader will be responsible about presentation in general and not missing the deadline. Team leader will delegate tasks (who finds topic, who prepares slides, who does actual presentation etc.) Team leader will share awarded points between team members. He has cmplete freedom to share them whatever way he/she seems appropriate (including taking all the glory (i.e. points) by him/herself) Team leader are responsible for re-scheduling a live presentation time if neended. He/she has to find the team to switch times, make a deal and inform lecturer NO LESS than one day before due date.

2016 teams

Blue team

  • Mohanad Aly Hassan Ali Elsafty, Team Leader
  • Meelis Hass
  • Indrek Taal

Yellow team

  • Lộc Phan Văn, Team Leader
  • Artur Vincent Kerge
  • Artur Ovtšinnikov

Green team

  • Kustas Kurval, Team Leader
  • MD Nazmul Hasan
  • Anton Zolotarjov

Orange team

  • Etienne Iotefa Marie Barrier, Team Leader
  • Ilja Shustov
  • Sheela Gowry Sumathi Raju

Presentation Schedule

  • Green team 19.10
  • Blue team 02.11
  • Orange team 16.11
  • Yellow team 30.11

2016

Lectures