Topics and Schedule
We will cover the following topics:
- Software-defined networks (SDN)
- Programmable networks
- Congestion control in datacenters
- Big data systems
- Cloud storage
The class is graded as follows:
- Project (45%)
- Proposal (5%)
- Checkpoints (10%)
- Midterm presentation (10%)
- Final presentation (10%)
- Final report (10%)
- Paper reviews (15%)
- Final exam (10%)
- Assignments (20%)
- Participation (10%)
The project is a main component of this course. The goal is to eihter build a functional system, conduct high-quality novel research, or reproduce (and ideally build upon) the results of a significant paper related to cloud computing. You may work in groups of 2 to 3 people. The steps in the project are as follows:
- Project proposal: During the first month of the class, you should think about the topic you want to work on and find partners. You are welcome (and encouraged) to explore your own ideas. However, you can also talk with the instructor who will suggest some topics (you need to set an appointment). You will need to submit a project proposal. The proposal should be at most one page and include each of the following:
The proposal can be short. It should simply demonstrate that you have a plausible project and know how to attack it. The instructor will give a grade for the proposal, and either approve the project or ask for a revision.
- the problem you plan to address
- what will be your first steps to attack the problem
- what is the most closely related work, with either (a) citations of at least 2 similar systems (if you are building a system), or (b) at least 3 academic paper citations (if you are working on a research project, either conducting original research or reproducing others' research). You should explain why your proposed problem is different than those or why your proposed solution is better. You should actively search for related work, not just cite systems and papers that the instructor mentions.
- Who the people on your team are and how you plan to partition the work among the team
- Checkpoints: Every two weeks from the date that you submit your proposals, each team should provide a status report describing the progress since the last checkpoint and their contribution.
- Midterm presentation: Give a presentation in class describing what problem you are solving, why existing approaches will not solve your problem (if you are building a system or conducting original research), why you selected that particular paper for reproducing their results (if you are reproducing cloud research), your solution approach, and your progress in your solution. You must demonstrate progress in your solution.
- Final report: This is a short report suitable for submission to a workshop. It should clearly state the system being built or the problem being solved, its importance, related work, your approach, evaluation, and results, conclusion, discussion of limitations, and future work. The paper should be at most 8 pages. But you will be judged on results, not pagecount!
- Presentation: At the end of the course, we will have a presentation session. This will be an opportunity for the students and the instructor to ask questions about your project and to see the cool work that you've done.
Dates for the above steps will be announced on Piazza. In general, you are encouraged to meet with the instructor and seek advice on the project as often as you like.
Can a project be shared with another course's project or independent research?
It is OK, and often a good idea, to work on a class project that complements your other ongoing projects and has a related topic. However, you should identify the piece of the larger project that you are working on for this course, with separate pieces for other courses. Check with your other instructors as well.
For each class, we usually will have one assigned paper that you should read prior to class and be ready to discuss during the class. You should submit one paper review for each class on Pizza publicly (so that it is visible to the instructor and other students) by 5:00pm the day before the lecture for which the paper was assigned.
This review should be relatively short (about one paragraph). It should not summarize the paper or repeat it; we have all read the paper already. Instead your review should include at least two comments on the paper that supply information not in the paper itself. For example, a comment might be:
- a suggestion to build on or extend the paper's ideas in future work
- a criticism of the paper
- an advantage of the paper (not discussed in the paper)
- an alternative solution for the solutions discussed in the paper
- a response to another student's comment
You are encouraged to read and comment on the other students' reviews. However, please write down notes on your own thoughts independently prior to reading other students' reviews.
Collaborating with other students to write reviews is not permitted. Your reviews should ideally include original ideas that do not appear in the other students' reviews. However, If you independently make similar points, that is acceptable.
Each review will be given a score in the [0,2] range. We will ignore the 2 lowest paper review grades which means that you may skip any 2 paper reviews without affecting your grade. You will receive a deduction of one letter grade for missing more than 2 reviews.
There will be 3 or 4 assignments during the semester which includes introducing several tools for experimental research in cloud computing and written questions covering roughly the first 1/3 and 2/3 of the course. You may work alone for assignments.
For reviews, assignemnts, and project milestons: up to 24 hours, 30% deduction, with no submissions accepted past 24 hours late.
We accommodate special medical circumstances, such as death in the family or hospitalization, with appropriate documentation. We cannot accommodate excuses such as "My laptop died".
You are expected to attend all sessions of the class. The general policy is that a student will automatically receive a deduction of one letter grade for missing more than 3 lectures.
Class sessions combine lectures, discussions of reading, and presentations by students. In all cases, the class is focused around discussion. Please comment, question, and interact!
There will be a final exam covering all the topics we discuss in the course as well as the papers that you review. The exam will be open notes and open papers, but closed laptop.
- If you are sick, in particular with an illness that may be contagious, notify me by email but do not come to class. Rather, visit the Health and Wellness: 1 East 31 Street, 410-516-8270. See also http://studentaffairs.jhu.edu/student-life/support-and-assistance/absences-from-class/illness-note-policy/
- All students with disabilities who require accommodations for this course should contact me at their earliest convenience to discuss their specific needs. If you have a documented disability, you must be registered with the JHU Office for Student Disability Services (385 Garland Hall; 410-516-4720; http://web.jhu.edu/disabilities/) to receive accommodations.
- If you are struggling with anxiety, stress, depression or other mental health related concerns, please consider visiting the JHU Counseling Center. If you are concerned about a friend, please encourage that person to seek out our services. The Counseling Center is located at 3003 North Charles Street in Suite S-200 and can be reached at 410-516-8278 and online at http://studentaffairs.jhu.edu/counselingcenter/
I am committed to creating a classroom environment that values the diversity of experiences and perspectives that all students bring. Everyone here has the right to be treated with dignity and respect. I believe fostering an inclusive climate is important because research and my experience show that students who interact with peers who are different from themselves learn new things and experience tangible educational outcomes. Please join me in creating a welcoming and vibrant classroom climate. Note that you should expect to be challenged intellectually by me, the TAs, and your peers, and at times this may feel uncomfortable. Indeed, it can be helpful to be pushed sometimes in order to learn and grow. But at no time in this learning process should someone be singled out or treated unequally on the basis of any seen or unseen part of their identity.
If you ever have concerns in this course about harassment, discrimination, or any unequal treatment, or if you seek accommodations or resources, I invite you to share directly with me or the TAs. I promise that we will take your communication seriously and to seek mutually acceptable resolutions and accommodations. Reporting will never impact your course grade. You may also share concerns with the department/center chair, the Director of Undergraduate Studies, the Assistant Dean for Diversity and Inclusion (Darlene Saporu, email@example.com), or the Office of Institutional Equity (firstname.lastname@example.org). In handling reports, people will protect your privacy as much as possible, but faculty and staff are required to officially report information for some cases (e.g. sexual harassment).
The strength of the university depends on academic and personal integrity. In this course, you must be honest and truthful, abiding by the Computer Science Academic Integrity Policy
"Cheating is wrong. Cheating hurts our community by undermining academic integrity, creating mistrust, and fostering unfair competition. The university will punish cheaters with failure on an assignment, failure in a course, permanent transcript notation, suspension, and/or expulsion. Offenses may be reported to medical, law or other professional or graduate schools when a cheater applies. Violations can include cheating on exams, plagiarism, reuse of assignments without permission, improper use of the Internet and electronic devices, unauthorized collaboration, alteration of graded assignments, forgery and falsification, lying, facilitating academic dishonesty, and unfair competition. Ignorance of these rules is not an excuse.
Academic honesty is required in all work you submit to be graded. Except where the instructor specifies group work, you must solve all homework and programming assignments without the help of others. For example, you must not look at anyone else's solutions (including program code) to your homework problems. However, you may discuss assignment specifications (not solutions) with others to be sure you understand what is required by the assignment.
Falsifying program output or results is prohibited.
Your instructor is free to override parts of this policy for particular assignments. To protect yourself: (1) Ask the instructor if you are not sure what is permissible. (2) Seek help from the instructor, TA or CAs, as you are always encouraged to do, rather than from other students. (3) Cite any questionable sources of help you may have received.
On every exam, you will sign the following pledge: "I agree to complete this exam without unauthorized assistance from any person, materials or device. [Signed and dated]". Your course instructors will let you know where to find copies of old exams, if they are available."
Report any violations you witness to the instructor. You can find more information about university misconduct policies on the web at these sites: (a) For undergraduates: http://e-catalog.jhu.edu/undergrad-students/student-life-policies/, (b) For graduate students: http://e-catalog.jhu.edu/grad-students/graduate-specific-policies/, (c) the departmental honor code: https://www.cs.jhu.edu/academic-integrity-code