Multi-domain%20QoS%20reservation%20scheduling%20and%20QoS%20signalling

1

GRS Grid Resource Scheduling Multi-domain QoS
reservation scheduling and QoS signalling
2
Team Members

• Richard Smith (Coach)
• Andy Liow
• Keiko Tada
• Toshihiro Aiyoshi

3
Why?

• Guarantee Network Capacity
• Timely data transfer
• Fine-grained QoS control
• INTSERV RSVP problems
• DIFFSERV
• micro-manage network capacity allocations at the
  edge of network

4
Background

• GARA (General-purpose Architecture for
  Reservation and Allocation)
• numerous resource reservation
• widely used
• limitations
• GRS (Grid Resource Scheduling) UCL
• NRSE
• DIFFSERV EF service, micro management
• http//www.cs.ucl.ac.uk/research/grs/

5
Network Resource Scheduling Entity Reservation
Model
6
Objectives

• Decentralised QoS Reservation
• Protected capacity
• Specific deadline
• DIFFSERV EF aggregate traffic
• Multiple Domain
• Across various administrative domains

7
Objectives (2)

• One NRSE per domain
• Establish SLS, SLA
• End user NRSE SLAs
• Between NRSE SLAs
• Local administrative controls local policy
• Real-time Non-real-time requests
• Flexibility in non-real-time requests

8
How?

• Methodology Extreme Programming
• Why XP?
• Small team, small project
• Rapidly changing requirements
• Low overhead
• Reduces risk
• Agility and flexibility

9
What is XP?

• Pair programming
• Small releases
• Metaphor
• Simple design
• Testing
• Refactoring

10
Stakeholders

• Customer Project supervisor (Saleem)
• Development
• Richard, Andy, Keiko, Toshihiro
• Business
• Richard, Andy, Keiko, Toshihiro, Saleem
• Planning game

11
Life Cycle

• Exploration
• Planning
• First iterations
• Production iterations
• Maintenance iterations
• Death

12
Iterations

• Agile - very short
• Daily build cycle
• Plan
• Code
• Test
• Re-factor
• Weekly releases code into production early

13
Schedule tasks - Deliverables
14
Development Phases

• Phase 1 Protocol Definition
• Phase 2 Single Domain Scenario
• Concurrent with client application
• Phase 3 Multi Domain Homogenous Scenario
• Phase 4 Multi Domain Heterogeneous Scenario

15
Resources

• Hardware
• 5 Linux machines (3 routers, 2 clients)
• Software Modules and Tools
• Java (Java JDK)
• BEEP (Blocks Extensible Exchange Protocol Core)
• XML
• DIFFSERV
• TC (Traffic Control)
• Xemacs
• GNU Make
• CVS
• MrProject

16
Evaluation and Assessment

• Not lines of code refactoring simplifies
  program
• Load Factor (ratio estimated engineering time /
  actual time)
• Unit tests after each build
• Functional tests after each iteration
• Customer tests features match stories

17
Risk Management

• Most important work first
• Risk log
• Likelihood, impact, mitigation plan,
  Responsibilities
• Update regularly
• Accuracy of assessment
• Incremental development risk included in each
  iteration plan

18
Risk Management (2)
Risk Log (in part)
Risks Likelihood Impact mitigation plan
Each member has different experience and skills, so High Medium - Pair programming - self study with others help
As XP is used for the first time, the understanding of the team Medium Low advice from supervisor(expert) make the first iteration small to understand it easily
19
Monitoring Control

• Task tracking
• Setting checkpoints
• Visualising progress (Gantt chart)
• Meeting with the supervisor once a week
• Variables resources, scope, quality, time
• Change control
• Requests / Specification change log
• Risk log

20
Questions?