Specialization Software-defined Networking (Winter 2014/2015): Difference between revisions

← Older edit

Specialization Software-defined Networking (Winter 2014/2015) (view source)

Revision as of 14:04, 21 April 2015

592 bytes added , 21 April 2015

→‎25 March

Marumai1

783

edits

@@ Line 1: / Line 1: @@
-{{Announcement|Note: Please register in FlexNow by today}}
+{{Announcement|Note: The final report is due on April 30th.}}
 == Details ==
 {{CourseDetails
 |credits=150h, 5 ECTS
-|module=M.Inf.1230: Specialization Software-defined Networks (SDN)
+|module=M.Inf.1230: Specialization Software-defined Networks (SDN)); ITIS: 3.32
 |lecturer=[https://www.net.informatik.uni-goettingen.de/people/mayutan_arumaithurai?lang=de Dr. Mayutan Arumaithurai]
 |ta=tba
@@ Line 13: / Line 13: @@
 ==Course Overview==
+{{Announcement|Note: See the Last section titled "Due date for Reports" to know the final requirements for this course and what needs to be submitted.}}
 Software-defined networking (SDN) has recently attracted both researchers in academia and big players in communication technologies, and is currently probably the 'hottest' topic in computer networking. This course is a continuation of the "Introduction to SDN" course and we will focus on gaining an advanced knowledge of SDN.
@@ Line 96: / Line 99: @@
 === 25 March ===
-* Exercise V: Firewall (contd. ) [https://dl.dropboxusercontent.com/u/1652374/SDN_Course/3.Firewall.zip] (Exempt: ALL except Gurjinder)
+* Exercise V: Firewall (contd. ) [https://dl.dropboxusercontent.com/u/1652374/SDN_Course/3.Firewall.zip] (Exempt: ALL)
 * Exercise VI: Pyretic firewall [https://dl.dropboxusercontent.com/u/1652374/SDN_Course/4.pyretic_firewall.zip] (Exempt: Khawar, Omar, Martin, Thomas, Sameer, Eeran)
@@ Line 107: / Line 110: @@
 === 27 March ===
-* Exercise IX: Pyretic Debugging (Exempt: None)
+* Exercise IX: Pyretic Debugging (Exempt: Omar, Martin, Thomas, Sameer, Eeran)
 '''HINT:''' You might have to use the "$ dpctl dump-flows tcp:127.0.0.1:6634" or "mininet> dpctl dump-flows" command frequently.
 ** In this debugging exercise, we take solutions available in the Internet for the gardenwall problem and try to fix bugs in it.
@@ Line 116: / Line 119: @@
 *** start mininet: sudo mn --controller=remote --topo=single,3 --mac --arp
 *** check h1 ping h2
-*** Now infect h1: python json_sender.py -n infected -l True --flow="{srcmac=00:00:00:00:00:01}" -a 127.0.0.1 -p 50001
+*** Now infect h1 (in /home/mininet/pyretic/pyretic/kinetic folder): python json_sender.py -n infected -l True --flow="{srcmac=00:00:00:00:00:01}" -a 127.0.0.1 -p 50001
 *** check h1 ping h2. We should be able to observe that this traffic is blocked.
 *** Now, we move on to the debugging part
 **** check h2 ping h3, what happens?
 **** Now, modify the given code to allow h2 traffic to pass through to h3, when h1 is "infected".
-** If time permits, check if the "exempt" case is working fine too
+** Now, check if the "exempt" case is working fine too
+** if time permits, check and improve code to allow h1 to ping h2
 ** If time permits, try fixing [https://dl.dropboxusercontent.com/u/1652374/SDN_Course/Exercises/pyretic_gardenwall_internetsolution.py this] code for the "infected" case.
@@ Line 167: / Line 171: @@
 * A Distributed and Robust SDN Control Plane for Transactional Network Updates, Infocom 2015 [https://dl.dropboxusercontent.com/u/1652374/SDN_Course/Finally-selected-papers/infocom15-distributed-sdn-control-plane.pdf]
-==Due Dates for Reports (E-Mail to Mayutan)==
-'''NOTE:''' Currently, the information below is tentative. I will update and post the final version by early next week.
+==Requirement and Due Date for Final Report (E-Mail to Mayutan)==
+{{Announcement|Note: The final report is due on April 30th.}}
 * Submit your final report (in .pdf format) as well as code (in .py format) as one zipped file with your name.
-** subject line of email: Submission of work for Specialization in SDN
-** Name of attachment: name.zip, e.g., if when I submit the final work, the file will be named: Mayutan.zip
+ subject line of email: Submission of work for Specialization in SDN
+ Name of attachment: name.zip, e.g., if when I submit the final work, the file will be named: Mayutan.zip
 '''NOTE:''' Your final report ([ftp://ftp.springer.de/pub/tex/latex/llncs/latex2e/llncs2e.zip LaTeX Template]) should include:
@@ Line 178: / Line 188: @@
 * Papers discussed during GD-I, GD-II, GD-III (see Group-Discussion section to see the list of those who need to submit a report)
-  Papers of each GD should be summarized in 1-2 pages
+  Papers of each GD should be summarized in 1-2 pages using the [http://user.informatik.uni-goettingen.de/~dkoll/files/sdn/review.docx review form].
-* One review form for the paper you were assigned during the course (Use this [http://user.informatik.uni-goettingen.de/~dkoll/files/sdn/review.docx review form]).
+* One review form for the paper you were assigned during the course for the final presentation (Use this [http://user.informatik.uni-goettingen.de/~dkoll/files/sdn/review.docx review form]).
   One review per participant is mandatory to pass.
-  Those who need to write a larger report must submit review of another paper presented during the final presentation.
+  Those who need to write the extra three pages (Guryash, Siddhartha, Pranay, Gurjinder) will preferable have to submit review of another paper presented during the final presentation.
   Make sure that you write your own review. Copy/Paste reviews from other participants of the course will not be accepted. The reviews are individual work.
+* screenshots to prove that the code is working for those who didn't show it to me during the lecture. Please refer to the Exercise Section above.
 * The slides (if any) you used for presenting your papers in class.
   No need to improve the slides after presenting.