Use Case: SLA-aware cloud infrastructure using SLA@SOI

• Name: SLA-aware cloud infrastructure using SLA@SOI
• Contact: Andy Edmonds, SLA@SOI.
• Description: See the presentation from OGF25 Cloud BOF.
• Functional Requirements
  • VM Description: request format important - In this area is where there is least coherency amongst providers.
  • VM Description: A means to add non-functional constraints on functional attributes.
  • VM Management: all parameters in the request should be "monitor-able" and verifiable. Full control of resources (VMs) allocated required; at a minimum: start, stop, suspend, resume.
  • VM Monitoring: Monitoring non-functional constraints declared in provisioning request
  • Network Management: resources assignable by network tag - defaults of public and private further sub-categorisaton could be allowed e.g. tag of web could be assigned to the public network group.
  • Storage Management: simple mount points, reuse storage SaaS offerings
• Non-functional Requirements
  • Security: Transport and user level (ACLs? oAuth?) security
  • Quality of Service: Can be many - Part of service offering from the infrastructure provider e.g. security, QoS, geo-location, isolation levels - NFPs are the basic building blocks of differentiating IaaS providers.
  • Scheduling Information: When a particular resource is to be run. Also in which order should a collection of resources be ran in the case that one resource is dependent on another.