Spring
2018
Credits: 3
Meeting Times: Tuesday/Thursday,
Meeting Location: EBII 1226
Wolfware Course Web
Instructor Information:
This course explores design and implementation principles in modern distributed systems. In particular, the course will emphasize on recent techniques used by real-world distributed systems such as cloud systems, enterprise data center, and peer-to-peer file sharing (e.g., BitTorrent). Students will learn the state of the art in distributed system architectures, algorithms, and performance evaluation methodologies. Topics include canonical distributed concepts such as remote procedure call, distributed objects, replication, distributed system security, concensus protocol, and recent distributed system technologies such as peer-to-peer, grid, autonomic computing, distributed massive data processing/Google map-reduce, system machine learning, distributed system debugging, multi-core systems, distributed virtualization. On completing this course, the student should be able to the following:
Distributed
Systems:
Concepts and Design, (4th Edition), G. Coulouris, J.
Dollimore, and T. Kindberg
Distributed
Systems (2nd Edition), Sape Mullender
Distributed
Systems:
Principles and Paradigms, Andrew S. Tanenbaum, Maarten van
Steen
Distributed systems have become the fundamental computing infrastructure for many important real-world applications such as Internet search engine, media streaming servers, online file sharing, information analytics, and scientific exploration. This course explores design and implementation principles in modern distributed systems. In particular, the course will emphasize on recent techniques used by real-world distributed systems such as peer-to-peer file sharing (e.g., BitTorrent), enterprise data center, and Internet search engine (Google). Students will learn the state of the art in distributed system architectures, algorithms, and performance evaluation methodologies. Topics include i) traditional distriubted computing concepts (e.g., distriubted objects, middleware, replication, distributed system security, and concensus protocol); and ii) recent emergent distributed system techniques such as peer-to-peer systems, massive data processing, Grid, and autonomic computing. Students will have opportunities to not only learn the common design methodology of many important distributed systems, but also gain hands-on experience through project implementations. The majority of course materials will be drawn from classic papers and current state-of-the-art work. The instructor will lecture for the first half of the semester and students will present papers and projects in the second half of the semester. Students will read and review papers ahead of time, participate in class discussions, present at least one research topic during the course, and do a term project individually or in a two-member team. Students will also write a paper (as well as review other students' papers) describing their project and present their work at the end of the course, in a "conference" format designed to give students an experience similar to that of participating in a professional conference.
Prerequisites:
CSC501 or equivalents. Programming in C++ or Java in Unix environment. If you are not sure whether you can attend this course, please consult the instructor.
Paper Review:
Review
guidelines: Provide a paragraph of summary about the paper, a
paragraph of 2-3 strong points of the paper (i.e., Why the
paper should be accepted), a paragraph of 2-3 weak points of
the paper (i.e., why the paper should be rejected), brainstorming
ideas
for developing new research ideas related to the work described
in the paper(optional).
Project:
Both project proposal and final report should follow typical paper requirements using ACM Double-Column Paper format. The project proposal should include abstract, introduction, proposed approaches, and related work. The final project report should include a full paper content including abstract, introduction, design and algorithms, experiment evaluation, related work, and conclusion. We will organize a mini-conference for the students to present their project work. Three best papers will be selected during the mini-conference.
W |
Date |
Topic |
Assigned |
Assignments |
1 |
1/9 |
Introduciton [slides]
|
|
Investigate your term project idea and do preparation
for it. A list of candidate project topics will also be
provided to you on the class. Talk to the instructor
about your project idea and talk to other students in
forming a two-three members group. Email the instructor
to setup the appointment.
|
1/11 |
|
|||
2 |
1/16 |
|
|
Investigate your term project idea
and do preparation for it. Talk to the instructor about
your project idea and talk to other students in forming
a group if you would like to work in a group. 1/22
Sunday midnight: Paper presentation signup due. Please send an email to the TA to bid three papers in the list below and list your choices in decreasing order. You will be allocated with one paper to present based on the FCFS policy and paper availability.
|
1/18
|
Project Testbed[slides] |
|||
3 |
1/23 |
Consensus Protocol
|
|
1/29
|
1/25 |
Consensus Protocol
|
|
||
4 |
1/30 |
Consensus Protocol |
|
2/5 midnight: project proposal due.
|
2/1 |
Guest Lecture by Dr. Daniel Dean
|
|
||
5 |
2/6 |
Autonomic Computing [slides] |
|
2/12 midnight: reviews due
|
2/8 |
Peer-to-Peer Systems [slides] |
|
||
6 |
2/13 |
Overlay Networks
|
|
2/19
|
2/15 |
Big Data |
|
||
7 |
2/20 |
System Research Methodology [slides]
|
|
2/26
|
2/22 |
Project Proposal Presentation |
|
||
8 |
2/27 |
Student presentation |
|
|
3/1 |
Student presentation |
|
||
9 |
3/6 |
Spring Break |
|
No paper reading assigned. You should spend time on your term projects. |
3/9 |
Spring Break |
|
||
10 |
3/13 |
Student presentation |
|
No paper reading assigned. You should spend time on your term projects. |
3/15 |
Student presentation |
|
||
11 |
3/20 |
Project MidReview |
No paper reading assigned. You should spend time on your term projects. |
|
3/22 |
Project MidReview |
|||
12 |
3/27 |
Project MidReview |
|
No paper reading assigned. You should spend time on your term projects. |
3/29
|
Student presentation |
|
||
|
4/3 |
Student presentation |
|
|
4/5 |
Student presentation |
|
||
14 |
4/10 |
Student presentation |
|
No paper reading assigned. You should spend time on your term projects. |
4/12 |
Student presentation |
|
||
15 |
4/17 |
Student presentation |
|
No paper reading assigned. You should spend time on your term projects. |
4/19 |
No Class |
|
||
16 |
4/24 |
Project Demo |
|
May 7th midnight: final project report due,
project source code and document due Your project source code and document submission should be a single zip file. The zip file should include your system source code including all other dependent packages, the experimental subjects used in the project report, instructions on how to set up and use the system to reproduce the experimental results, and other documents that help others understand your tool and source code. |
4/26 |
Project Demo Project presentation on 4/27 1pm-5:30pm |
|
Suggested Topics for Student Presentations (You can suggest to the instructor the papers that are not in this list but you would like to present):
Cloud
Computing & Data Center& Big Data
Distributed
Systems Security
The university provides a detailed policy on academic integrity. This policy can be found in the Code of Student Conduct. It is understood that when you submit your homework, you are implicitly agreeing to the university honor pledge: "I have neither given nor received unauthorized aid on this test or assignment."
Academic dishonesty (e.g., cheating or plagiarism) will not be tolerated under any circumstances. If you are having difficultly with any part of the course material, please see me as soon as possible. I will do everything I can to help you with any course-related problems you may be having. If you are found to be guilty of academic dishonesty, however, I will then do everything I can to see that you are punished as forcefully as possible. This may include asking to have you suspended or expelled from the course, the program, and/or the university. At a minimum, you will receive -50% for the assignment in question, and your name will be placed on record with the university as having committed an academic offence. Multiple offences during your academic career will result in suspension or expulsion from the university. I take absolutely no pleasure in pursuing cases of academic misconduct, and would ask that you please do not put me in this position.
All effort will be made to ensure that no students with disabilities are denied any opportunity to successfully complete this course. If you have specific requirements that need to be addressed, please contact me immediately. Possible changes can include (but are not necessarily limited to) rescheduling classes from inaccessible to accessible buildings, or providing access to auxiliary aids such as tape recorders, special lab equipment, or other services such as readers, note takers, or interpreters. This may also include oral or taped tests, readers, scribes, separate testing rooms, or extension of time limits.
None.
None.