Cloud Computing Lecture 1 BU EC 500 A

Cloud Computing Lecture 1 BU EC 500 A 1 / CS 591 K 1

Instructors & intro • • • Michael Daitzman: michael. daitzman@vecna. com Peter Desnoyers: pjd@ccs. neu. edu Jason Hennesy: henn@bu. edu Orran Krieger: okrieg@bu. edu Ata Turk: ataturk@bu. edu

Resources • Class syllabus: https: //okrieg. github. io/EC 500/index. html – Projects, papers, … • Blackboard: https: //learn. bu. edu/ – Assignment hand in, quizzes to collect information • Piazza: https: //piazza. com/bu/spring 2015/ec 500 cs 591 – Announcements, Paper discussions • Trello: https: //trello. com – Project planning • Github: https: //github. com – Revision control

Three parts http: //okrieg. github. io/EC 500/index. html 1. Academic cloud computing material 2. Agile methodologies 3. A cloud computing project

Strategy for academic materials • We will cover 2 papers per week + agile lesson • You need to read papers & listen to talks at home. • Class time will be largely spent in discussion, you will: – participate in on-line discussions before/after the classes. – be randomly selected to present and answer questions. – submit paper reports. • Check paper reviewing guidelines

Paper reviewing guidelines • Before the class – submit a summary of the paper – contribute questions/comments about the paper • During the class – Be prepared to introduce the gist of the paper – And answer/discuss questions collected about the paper – Whoever presents also gets to write a review of the paper

Project • Teams of 4 to 10 students. • Mentored by developer or product owner who: – Cares about the end result. – Understands the technology needed. • You will be marked on: – Demonstration of agile methodologies – Demos every two weeks and final demo – Project proposal and project report • Read project management guidelines: https: //piazza. com/class/i 1 v 8 n 1 iypqys 1? cid=8 • Some of these projects will fail; then, we will go deep. • Some of these teams will be dysfunctional, mentors may not fully engage….

Marking • 30% paper discussions, summaries, and reviews (written and verbal) • 70% project: shared with your teammates – 10% project proposal – 30% bi-weekly project demo and verbal status in aggregate – 30% final project result and report

This is an experiment • It’s a new course. • Departs from traditional course in: – Flipping a very large course – Focus on Agile methods. – Experiment of involving industry mentors. • But… tons of experience building teams, running industry projects, development • We will adjust as needed. Keep communicating with us what is working and what is not…

PROJECTS

We have an aggressive schedule • To get something real, you will need to organize quickly. • Consider when picking a project: – Industry, MOC, or academic mentor. – License: • you will be required to give up your rights: either to the public or to a company • If unacceptable, please contact the instructors and we will figure out an alternative – Project that will excite and interest you – Skills that match you, or your interest, e. g. , Web UI, server, low-level OS, DB, Visualization, Io. T… • You should: – fill out the poll on blackboard today, that will require you to get us all the information needed to get you on the projects, e. g. , ids, skill sets… – Fill out the doodle poll with preference on projects • The projects will start on Thursday. • If you are going to drop the course, please try to do so by Wednesday.

Open. Daylight & IOT • Programmable Open. Stack Network Services in Maple: http: //okrieg. github. io/EC 500/PROJECTS/sugarbush. ht ml • Prototype of “Multi-Thing” Io. T Applications Running over Open. Daylight: http: //okrieg. github. io/EC 500/PROJECTS/odl-iot. html • Io. T Resource Tree Representation for Massively Large Data Sets: http: //okrieg. github. io/EC 500/PROJECTS/bigtreeui. html

Society • MBTA Bus Performance: Data Capture and Analysis: http: //okrieg. github. io/EC 500/PROJECTS/MBTAB us. Performance. html • Radiology in the cloud: http: //okrieg. github. io/EC 500/PROJECTS/chris. ht ml • Real Time Drug Safety Monitoring in the Cloud: http: //okrieg. github. io/EC 500/PROJECTS/pharma vigilance. html

Company/Startup • CONS 3 RT MOC Connector: http: //okrieg. github. io/EC 500/PROJECTS/CONS 3 R T. html • Network-aware Container Distribution System: http: //okrieg. github. io/EC 500/PROJECTS/jisto. ht ml • Recovery in the cloud: http: //okrieg. github. io/EC 500/PROJECTS/Cloud. R ecovery. html

Extending the MOC • Per-tenant pass-through Open. Stack services: http: //okrieg. github. io/EC 500/PROJECTS/tenantopenstack. html • Plugin architecture for The Mass Open Cloud GUI: http: //okrieg. github. io/EC 500/PROJECTS/MOCSAHARA. html • Extending the MOC GUI: http: //okrieg. github. io/EC 500/PROJECTS/MOC-UI. html • Recursive Haa. S with fast provisioning: http: //okrieg. github. io/EC 500/PROJECTS/recursive. Haa S. html

Community and fun • Continuous Integration in the cloud: http: //okrieg. github. io/EC 500/PROJECTS/conti nt. html • Social news serving system: http: //okrieg. github. io/EC 500/PROJECTS/bu. N ews. html