NUBOMEDIA: FP7/2007-2013 GA-610576

NUBOMEDIA Roadmap

The following table shows a summary of future requeriments to be implemented in NUBOMEDIA:

ID* Name Description Priority
T&D_R7 Create tutorial videos Elaborate video tutorials bringing all the different parts together that explains to the developers, what the platform is, what services/videos the platform provides and what tools are available on the platform. Medium
IST_R1 Enable full installation of NUBOMEDIA on top of virtual computing resources Support the installation of OpenShift on virtual machines in order to enable the entire NUBOMEDIA architecture to run on a virtual platform. Medium
DBG_R2 Simplify media server logs Simplify the captured text in the MS logs to improve the ability to find errors while deploying/running on the PaaS. We may consider exposing the MS logs via the PaaS GUI Medium
DRT_R8 Restart application It shall be possible to restart applications. Low
DRT_R10 KMS Buildpacks for custom module installation It shall be possible to provide KMS build packs. Buildpacks are scripts that are run when the KMS is instantiated. They are used to install dependencies for the KMSs and configure the instances environments if needed. Low
DRT_R11 Provide billing capabilities The platform would be more attractive for industrial purposes if it were providing billing capabilities, meaning the ability to generate per-developer CDRs illustrating billable events such as number of applications being deployed, time of deployment, time of undeployment, network traffic consumed by an application, computing resources consumed by an application, disk resources consumed by an application, etc. Low
DRT_R12 Provide fault tolerance capabilities The platform would be more attractive for industrial purposes if it were providing fault tolerance meaning the ability to recover from faults on both virtual and physical computing resources as well as the ability to manage network partitions in a consistent way. Low
DRT_R13 Geo-aware multi-site The platform would be more attractive for industrial purposes if it were providing multi-site capabilities meaning the ability to deploy into different geographical locations and having some logic for routing sessions toward the most optimal location. Low
KMS_R2 Live streaming support KMS should provide HLS and MPEG-DASH endpoints enabling the live broadcasting of media streams through those protocols to CDNs or even the creation of Kurento-based CDNs. Low
PGUI_R3 coolDownPeriod should also be configurable parameter in the PaaS GUI in relation to auto-scaling behaviour When developers try to understand the behaviour of the auto-scaling mechanisms, we can appreciate that there is a cool-down period of around 1 minute. However, this can be too much for many applications. Hence, I think that we should be enabling developers to know the default cool-down period and to set-up a different period when appropriate through the PaaS GUI. Medium
PGUI_R4 scaleInThreshold should also be configurable parameter in the PaaS GUI in relation to auto-scaling behaviour Developers don’t know what is the default scaleInThreshold and cannot either configure it when required. This may drive to configuring incorrectly the autoscaling behaviour. For example, when deploying the magic-mirror application setting up the scale-out threshold to 60 (small instances), it seems that NUBOMEDIA may enter into some kind of cycle where scaling-out and scaling-in operations happen in a cycle without modifications on the number of sessions (in my experiment the number of sessions remained fixed to 4) Medium

*Notation:

  • T&D: Tutorials and Demo Examples
  • IST: Installation Requirements
  • DBG: Debugging Requirements
  • DRT: Deployment and Runtime Requirements
  • KMS: Kurento Media Server Requirements
  • PGUI: PaaS GUI Requirements