This method is used to delete all VMs that are running a particular service. As a side effect, all IP addresses associated to the VMs will be released.
No data is needed on the response of the request. The response returns a 200 code if the request can be completed successfully or the appropriate return code otherwise.
Chapter 19
Proxy Design
19.1
OPTIMIS reference architecture overview
In order to understand where the proxy is placed within the OPTIMIS platform, it is worth giving an overview of its architecture.
The architecture is formed by 3 toolsets: the basic toolkit, the IP tools and the SP tools (see diagram 19.1, where the components that will play a role in the project have been high- lighted). Altogether, these sets of tools enable SPs and IPs to manage services (and infrastruc- ture) throughout the whole service lifecycle (service construction, deployment and operation). The architecture has been designed following the modularity principle, where each component is as decoupled as possible from the others, thus allowing providers to only adopt a part of the OPTIMIS toolkit. Most of the core components are implemented as web services in order to enable a distributed platform deployment between SPs and IPs.
TheBasic Toolkitis a set of fundamental tools for monitoring and assessing clouds services
and infrastructures, as well as interconnecting these securely.
• TheMonitoring infrastructure allows the runtime state of physical infrastructure and
virtual infrastructure to be captured, stored, and analyzed.
• TheTREC-factors provide a framework for SPs and IPs to take management decisions based on the following factors:
– TheTrusttools enable SPs and IPs to assess each other’s reputation prior to engag-
ing in a business relationship.
– TheRisk management tools allow SPs and IPs to reason about certain aspects of service deployment and operation, the risk factors associated with these, and esti- mate the potential consequences.
– TheEco-efficiencytools enable an IP to assess power consumption, carbon emis-
sions, etc. in order to achieve certain ecological goals.
– TheCosttools can be used to assess and predict the service operation costs, both from an SP and IP perspective.
• TheSecurity Frameworkprovides a set of access and credential management capabili-
ties that facilitates the interconnection of multiple clouds, as well as services that operate across these.
Base Toolkit
Monitoring Infrastructure Security Framework
TREC Infrastructure Provider Tools
Admission Control CloudQoS
Data Manager VM Manager
Fault Tolerance Engine Elasticity Engine
Cloud Optimizer
Service Provider Tools
Programming Model Image Creation Service
VM Contextualization Liscense Management Integrated Development Environment Service Deployment Optimizer Service Manager
Diagram 19.1: Component-level view of the OPTIMIS architecture
The Infrastructure Providers tools allow an OPTIMIS IP to optimize provisioning of
services according to its requirements.
• TheAdmission Controlcomponent is used to determine whether or not to accept a new
service request, and thus handle the tradeoff between increased revenue and increased workload (with potential SLA violations as a consequence).
• TheCloudQoS(CQoS) component is used to model, negotiate, and monitor SLAs be-
tween the IP and SPs whose services the IP runs. It is also responsible for interacting with the necessary components to initiate the deployment of a service.
• TheData Managerprovides mechanisms to transfer VM images between SPs and IPs.
• TheVM Managerhandles the VM lifecycle (launches VMs, monitors VMs, shuts VMs
down) as well as performs VM placement in order to maximize the utility of the IPs infrastructure.
• TheElasticity Enginehas the purpose of adjusting the capacity (in terms of VMs) allo-
cated to a service in order to meet SLAs upon rapid changes in workload of the VMs that constitute the services.
• The Fault Tolerance Engineprovides a VM re-starting service, thus contributing to a self-healing cloud infrastructure.
• TheCloud Optimizer(CO) orchestrates the monitoring system, the IP-level TREC as-
sessment tools, and the above listed management engines to create a self-managed cloud infrastructure driven by infrastructure requirements.
TheService Providerstools allow OPTIMIS SPs to create, deploy, and run services.
• The OPTIMIS Programming Model simplifies the construction of SOA applications, either single web services or orchestration of services.
• The Image Creation Service allows the construction of VM images that embed the
applications developed with the programming model.
• TheIntegrated Development Environmentprovides a user-friendly way to implement
and prepare services for deployment, using the programming model and image creation service.
• TheLicense Managementtools allow SPs to incorporate license-protected software in
services, and also provide the runtime support needed to manage software licenses for services deployed in remote IPs.
• TheService Deployment Optimizer(SDO) coordinates the service deployment process;
ranks and selects suitable IPs, negotiates SLAs for the service, prepares the VM images and transfers these, and ensures that the service is launched properly.
• TheVM Contextualization tools provide a convenient mechanism to prepare VM im-
ages with information needed for services to self-contextualize once launched. This can be any data: propagation of network parameters, security credentials, etc.
• The Service Manager monitors the runtime state of deployed services, allowing the
SP to keep track of its services and manage these, e.g. by migrating a service upon unacceptable behavior.
The components highlighted in diagram 19.1 (Monitoring Infrastructure, Data Manager and CloudQoS) form the point of contact with external IPs, along with the SDO that orchestrates the deployment of a service to an external IP, during service deployment and operation.