Skip to content
Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time




Asperathos is part of Privacy by Evidence (PbE) which is an initiative to improve confidence in applications that handle sensitive data, you can read more about this initiative in: PbE.


Asperathos is a platform to facilitate the deployment and control of applications running in cloud environments. For example, it can provide Quality of Service (QoS) by controlling resources allocated during runtime. Nevertheless, in contrast to other orchestration tools, such as Kubernetes itself or OpenStack Heat, it can be configured to consider application specific metrics and to actuate in a customized fashion.

The architecture from Asperathos is depicted in the following figure. It is composed of three main modules: (i) the Manager is the entry point for the user and is responsible for receiving an application submission, triggering all other steps; (ii) the Monitor gathers, transforms and publishes metrics collected from applications (e.g., the application progress) or environment resources (e.g., CPU usage); and (iii) the Controller is the component that adjusts the amount of allocated resources dedicated to an application.

Each module above can be customized through the use of plugins. For example, a plugin to deploy the application can be specified in the Manager, another to define the application specific metric can be specified in the Monitor, another to control the actuation logic could be configured in the Controller, and so on.

Asperathos was developed by the LSD-UFCG (Distributed Systems Laboratory at Federal University of Campina Grande) as part of the toolset of the EUBra-BIGSEA ecosystem.

EUBra-BIGSEA is committed to making a significant contribution to the cooperation between Europe and Brazil in the area of advanced cloud services for Big Data applications. See more about in EUBra-BIGSEA website.

How does it work?

The Asperathos modules are implemented following a plugin architecture, providing flexibility to customize your deployment using only the plugins you need, avoiding to include unnecessary dependencies (from others plugins) to your deploy environment. All the integrations with different infrastructures and components are made by specific plugins.

This independent architecture allot the combination of different approaches in the same context. For example: running a containerized distributed application using an specific Manager plugin, it is possible to write a Monitor plugin to gather metrics about application progress and another to gather metrics from resources usage at the same time; it is also possible to Write two different Controller plugins where one can watch the resources usage measurements (published by one of the monitor plugins) from VMs to add/kill instances in the cluster, and another plugin to watch the application progress and add more container replicas to speed up the processing of tasks.

It is also possible to easily add external or new components, like: authenticators, authorizers, validators, and so on.

Case studies





Asperathos is being used and expanded by our partners: LNCC, SecureCloud and Atmosphere.


  • Python 2.7
  • Linux packages: python-dev and python-pip
  • Python packages: setuptools, tox and flake8


No description, website, or topics provided.




No releases published


No packages published