Comp517 Project Assignment

The Com517 aims to produce original scholarship in the area You will design and carry out a semester-long research project (done in teams of 2-4). The hope is that these projects will lead to published papers, but need not be that by the end of the semester. You will need to coordinate your work using GitHub and make it possible for others to execute it

Assignment Decriptions

• Group Selection and Topic Statement: select your partner and turn in a topic sentence as a PR on this README file. The section below "Register Teams" requests team name and member information along with focus statement. A form is presented, fill it in (replacing the bracketed sections in the focus statement and listing info for team name and all members. Delete any unused team member template entries.

• Proposal [DUE:9/17/20]: Written proposal for the project that states the problem you will address, the motivation for why this is an interesting problem, the goal of your project, the relationship between your project and other work, the plan and methodology for your project, and the resources needed to carry out your project. Include a set of incremental milestones that you will achieve in carrying out the project and a schedule for meeting these milestones.

• Midterm Meetings [DUE:10/13/20]: meet with me personally to check up on progress for schedule and milestones. The goal is to produce a real system, if implementing, or initial data for measurement projects.

• Midterm Report [DUE:11/5/20]: Preliminary results and report, which is close to final report.

• Project Presentation [DUE:11/17/20]: Each group will present their work at the end of the semester.

• Project Showcases [Week of 12/1/20]: Each group will present demo [15-30 mins] of their system to professor.

• Final Project Report [DUE:12/10/19]: Final project report written in conference style.

I have project ideas, but encourage you to come up with a research idea by yourself. I encourage you to start this process early and to solicit feedback from me.

Register Teams

Research Focus Statement:

• I am studying the architecture of the Firecracker VMM and building a Rust kernel from scratch
• because I want to reason about the technicalities involved in building a kernel that can be integrated with Firecracker
• in order to show my readers a detailed comparison between the current kernel being used in AWS Lambda and our implementation, and how they can build upon our work.

Team Name: RustyRiceOS

Team Member:

• Name: Patrick Tser Jern Kon
• Rice ID: pk37

Team Member:

• Name: Jason Ludmir
• Rice ID: jzl2

Team Member:

• Name: Zhiwei Liang
• Rice ID: zl104

Turning in Instructions

For any part of the project you turn in (aside from focus and presentations), you must Usenix two-column formatting. For an example, feel free to start from the latex template latex-template.tgz or you can use the latex template that I personally use for my papers (this one includes a makefile) latex-example.tgz. Note: You are required to use LaTeX in this class.

The process to turn in a project will include forking this template repository and creating a branch for the specific sub-assignment. The sub-assignment will be turned in by creating a PR in GitHub. The PR model that we will use is patterned off of a common industry PR model. Note that you will originally fork this project from the template repository through the GitHub classroom, so your remote and origin may be slightly different. I will use the GitHub interface to make comments on your work. I will also use a pull and test model to verify code aspects of the project.