EECS 395/495: Networking Problems in Cloud Computing
Lectures: MW 4:00-5:20pm, Room Tech M152.
This course will cover a broad range of topics related to networking problems in cloud computing, including network structure of Internet Data Centers, layer 2 data network fabric, lease management and partitioning, data placement for geo-distributed cloud services, energy efficient cloud design, flow scheduling, congestion control, i.e., the incast problem, and more.
Students will form teams of three; each team will tackle a well-defined research project during the quarter. A list of suggested project topics will be provided. All projects are subjected to approval by the instructor. The project component will include a short written project proposal, a short mid-term project report, a final project presentation, and a final project report. Each component adds some significant element to the paper, and the overall project grade will be based on the quality of each component of your work. The above project components are due by email to the instructor by the end of the given day of the respective week.
1. Week 1 (Wednesday 3/30) Project presentations by group leaders
2. Week 2 (Monday 4/4) Form groups of 2, choose a topic for your project, and meet with the project leader.
3. Week 3 (Monday 4/11) Write an introduction describing the problem and how you plan to approach it (what will you actually do?). Include motivation (why does the problem matter?) and related work (what have others already done about it?). 2 pages total.
4. Week 6 (Monday 5/2) Midterm presentation. Update your paper to include your preliminary results. 5 pages total.
5. Week 10 (Wednesday 6/1): Presentations by all groups.
6. Week 11 (Friday 6/10) Turn in your completed paper. 10 pages total. You should incorporate the comments received during the presentation.
Each team will have a weekly meeting with project leaders.
1. Paper reviews (15%), presentations (20%) and debating in the class(15%): 50%
2. Projects 50% (Project proposal: 5%; Midterm report: 5%; weekly report and meeting: 10%; project presentation: 10%; final project report: 20%)
3. Research idea report (optional, 3 pages): 10%
There will be no textbook for this class. A key part of the class will be to review and discuss networking research papers. Students must read the assigned papers and submit paper reviews before each lecture. Two teams of students will be chosen to debate and lead the discussion. One team will be designated the offense and the other the defense. In class, the defense team will present first. For 30 minutes the team will discuss the work as if it were their own.
1. The team should present the work and make a compelling case why the contribution is significant. This will include the context of the contribution, prior work, and in cases where papers are previously published, how the work has influenced the research community or industry's directions (impact). If the paper is very recent, the defense should present arguments for the potential impact. Coming up with potential future work can show how the paper opens doors to new research.
2. The presentation should go well beyond a paper "summary". The defense should not critique the work other than to try to pre-empt attacks from the offense (e.g., by explicitly limiting the scope of the contribution).
3. The defense should also try to look up related work to support their case (CiteSeer is a good place to start looking.)
After the defense presentation, the offense team will state their case for 20 minutes.
1. This team should critique the work, and make a case for missing links, unaddressed issues, lack of impact, inappropriateness of the problem formulation, etc.
2. The more insightful and less obvious the criticisms the better.
3. While the offense should prepare remarks in advance, they should also react to the points made by the defense.
4. The offense should also try to look up related work to support their case (CiteSeer is a good place to start looking).
Next, the defense and offense will be allowed follow up arguments, and finally, the class will question either side either for clarifications or to add to the discussions and controversy and make their own points on either side. The presentations should be written in Powerpoint format and will be posted on the course web page after each class.
students must read the assigned papers and write reviews for the papers before
each lecture. Email the reviews to the instructor (firstname.lastname@example.org)
prior to each lecture and the reviews will be posted on the course web page.
Periodically, the instructor will evaluate a random subset of the reviews and
provide feedback and grades to students.
Please send one review in plain text per email in the body of the email message.
A review should summarize the paper sufficiently to demonstrate your understanding, should point out the paper's contributions, strengths as well as weaknesses. Think in terms of what makes good research? What qualities make a good paper? What are the potential future impacts of the work? Note that there is no right or wrong answer to these questions. A review's quality will mainly depend on its thoughtfulness. Restating the abstract/conclusion of the paper will not earn a top grade. Reviews are roughly half-page and should cover all of the following aspects:
1. What is the main result of the paper? (one or two sentence summary)
2. What strengths do you see in this paper? (your review needs have at least one or two positive things to say)
3. What are some key limitations, unproven assumptions, or methodological problems with the work?
4. How could the work be improved?
5. What is its relevance today, or what future work does it suggest?
Course web site: http://networks.cs.northwestern.edu/EECS495-s11//. Check it out regularly for schedule changes and other course-related announcements.