Assignment 3

This assignment was modified on July 8th, 2015

Due Date

Friday, July 10, 2015 (i.e., Saturday before 1 am)

Objectives

  • Introduction to autonomic systems
  • Introduction to autonomic elements
  • Introduction to autonomic managers and resource management
  • Introduction to autonomic policies
  • Introduction to feedback systems
  • Design, implementation, and simulation of autonomic element
  • Managed web services
  • Service level agreements (SLAs)

Instructions

This assignment consists of two parts. In Part I you are to design an autonomic element to control a managed element. In Part II you are to implement a policy-driven autonomic manager and its managed resource.

Part I

In Part I you are to define a policy for an autonomic element.
  • Describe the managed resource: the model, properties, sensors, and effectors. Note: for the managed resource you may choose to implement a simple web server, web crawler, or background service.
  • Describe a policy for an autonomic element to govern the chosen managed resource.
  • Describe a four-stage autonomic manager (monitoring, analysis, planning, and execution) to realize this policy. Specify the information to be stored in the knowledge base if any.
Maximum 4 typeset pages for this part 

Do not copy verbatim from any source. Write your own prose.
Cite your sources.

Part II - Group Project (3 people max per group)

In Part II you are to implement an autonomic element consisting of the managed resource of your choice and an autonomic manager governed by a policy.

Implementation and Demo:
  • Implement one of the managed resources you selected in Part I.
  • Implement the autonomic manager to manage this resource. Code the four phases of the the MAPE-K loop and the knowledge as separate components.
  • Implement a manageability interface to close the feedback loop between the managed resource and the autonomic manager.
  • Make the autonomic manager policy driven. Make sure you can change the policy and that your implementation is compliant with respect to the your chosen policy.
  • Submit all the code you need for your implementation

Report:  Document the architecture of your implementation.

  • Software components diagrams
  • Data flow diagrams. Document the information that is exchanged among the components are well defined and well described.

NOTE: The marking of this part requires that the group presents to the TAs a 5min live demo on July 13th, 2015. (Time slots below), in which the criteria will be revised. Students are responsible for bringing the required equipment for their demos and make sure these work properly. Only working demos will be marked!

All group members have to work on all parts together. Learn from each other!
Articulate in your submission how the individual group members contributed to Part II.

You only need to one submission per group.
Do not copy verbatim from any source.
Cite your sources.

Groups

 G1

Rodney Gelera, Conner McConkley, Darren Prince

 G2

Richard Wagner, Jon Bowen, MacKay McGillivray 

 G3

Miles Barr, Adnan Duale, Mohammed Nader Zuhri Yafi

 G4

Navdeep Bahia, Evan Wilde, Sean Debroni

 G5

Alex Li, Daniel Oon, Samuel Navarrete

 G6

David Bayly, Elliot Wyman, Dustin Faulkner

 G7

Arturo Reyes Lopez, Babak Tootoonchi, Maria Ferman Guerra

 G8

Bill Xiong, Junnan Ly, Colum McClay

 G9

Tim Dalton, Sahib Deep, Zhanxue Zhu

 G10

Sumit Kadyan, Fraser Delisle, Simon Taft

 G11

Francis Harrison, Muhammad Zubair, Jorge Conde Gomez Llanos

 G12

Parminder Kaur, Navpreet Kaur, Simar Arora

 G13

Waseem Ullah Khan, Anthony Kohan

 G14

Adel Adil, Jason Yu, Jason Cho

 G15

Ernest Aaron, Harshit Jain, Stephan Heinemann, Adithya Rathakrishnan

 G16

Patrick Lavoie, Carlene Lebeuf

 G17

Siqi Li, Pufan Zheng, Zhenyu Zhang

 G18

Mohammad Bin Abdulsalam, Ian Leslie

 G19

Khushboo Gandhi, Tory Borsboom-Hanson


Demo details - July 13, 2015

ECS 660 [9:30 - 11:30]
The demos start at 10:00, the room is available to students from 9:45 to get the set up ready.

ECS 418 [12:15 - 12:55]
The demos are 5 min long. there is 5 min extra between demos to allow groups' set up given the restrictions of the space.

Email submit@rigiresearch.com to take a time slot, these will be assigned in order of arrival

NOTE: Students with classes in the morning will have preference for section 4 which is during the class time. Please be considerate about this restriction to your fellow classmates and take a morning time slot if you don't have class (or other impediment) in the morning


PlaceSectionTimeNo. Groups
ECS 660
1A10:00 - 10:05[1]: G7
1B10:05 - 10:10[1]: G13
1C10:10 - 10:15[1]: G4
1D10:15 - 10:20[1]: G10



2A10:25 - 10:30[1]: G16
2B10:30 - 10:35[1]
2C10:35 - 10:40[1]
2D10:40 - 10:45[1]: G6



3A10:50 - 10:55[2]: G17, 
3B10:55 - 11:00[2]: G3,
3C11:00 - 11:05[2]: G1,
3D11:05 - 11:10[2]: G8, G2




ECS 418
4A12:15 - 12:20[1]: G11
4B12:25 - 12:30[1]: G5
4C12:35 - 12:40[1]: G12
4D12:45 - 12:50[1]: G9
4E12:50 - 12:55[1]: G14

Marking details

During your 5 minute demo you will be asked the following questions, please be prepared to answer them:
  1. What is the managed resource? Explain properties, sensors, and effectors
  2. What is the implementation of the autonomic manager? All four phases should be in separated components, this is, separated programs
  3. How the information flows between each component? Explain the communication mechanism to connect the managed resource with the autonomic manager, as well as among the elements of the autonomic manager
  4. What is the information being monitored (from the environment or the system)? Explain how the sensor is picking up the information
  5. What are the possible adaptations of the managed resource? Explain what things might change in the system when the autonomic manager decides that adaptations are required. Explain how the effector is making those adaptations.
  6. Demonstrate that the autonomic manager handles changes in the policy. Provide 3 test scenarios in which the policy could be violated or changed. It should be possible to see how the autonomic manager handles the decisions, for instance, through console messages OR log files, as well as the corresponding adaptations

How to submit

Send e-mail with solution in pdf format to submit@rigiresearch.com. Ensure e-mail subject line is in the following format:

<course_number>-A3

and filename is in the following format:

<course_numb>-<first_name>-<last_name>-<student_number>.pdf

where course_number is either seng480a, csc485a, or csc586a. 

e.g.: 
subject: seng480a-A3
filename: seng480a-john-doe-v00666.pdf

For Part II, the person submitting for the group must include the list of their group members in the following format:

<course_numb>-<first_name>-<last_name>-<student_number>

This list should be added at the end of Part II (i.e.: inside the pdf).

Marking

Part I is worth 50% and Part II 50%.