BASIC INFORMATION
Short name: POI – atPaaS
Long name: PaaS deployment on multi-IaaS
Company: atSistemas S.L | atsistemas.com
Country: Spain
Call: F4Fp-01-S (see call details)
Proposal number: F4Fp-01-27-S
SUMMARY REMARKS & TESTBEDS
Platform as a service (PaaS) are cloud computing services providing a platform allowing customers to develop, run, and manage applications without the complexity of building and maintaining the associated infrastructure. PaaS allows for higher-level programming with dramatically reduced complexity and more effective deployment, maintenance and enhancement of applications. Nevertheless, current PaaS solutions are usually coupled to an underlying IaaS provider resulting in a vendor lock-in for the organizations. atSistemas is a specialist in providing PaaS deployment and configuration services using different available technologies in the market. We usually are technologically agnostic so it is important to us to be able to offer our clients a solution avoiding current IaaS providers’ dependency. We already have an up-and-running PaaS (atPaaS) based on VMware vCloud Director IaaS.
atPaaS is a set of libraries and configuration mechanisms for the management of software and hardware resources allowing the implementation of the paradigm “Infrastructure as Code1”. atPaaS allows developers to build platforms (infrastructures, networking and software groups)ignoring the IaaS the application is deployed on. Currently, we are interested in evolving our atPaaS to an enterprise-scale PaaS with support for multiple IaaS. Though we made efforts to serve across multi-IaaS, we were not able so far to test a whole infrastructure lifecycle with multiple IaaS providers. Our objective in using our patrons’ Testbeds is to be able to have access to heterogeneous IaaS instances to deploy our PaaS on top of this heterogeneous set-up. Our experiment will cover the provision and scale-up of heterogeneous infrastructures in a transparent manner. Infrastructure as Code(IaC) is the process of managing and provisioning computing infrastructure (processes, bare-metal servers, virtual servers, etc.) and its configuration through machine-processable definition files, rather than physical hardware configuration or the use of interactive configuration tools.
