Alien4cloud is an open-platform easing DevOps implementation in large and heterogeneous organizations.
Whenever possible and needed, Alien4Cloud provides the model and tools allowing to ensure applications portability across different infrastructures, leveraging the OASIS TOSCA standard whose goal is to ‘Enhance the portability and operational management of cloud applications and services across their entire lifecycle‘.
But, in order to be able to manage all automation and DevOps scenarios, it is important as well to be able to onboard easily applications that leverage any infrastructure resource, even those potentially not portable.
The objective of this post is to explain the concept of Custom on-demand resource which helps reaching that goal and opens the door to large number of possibilities such as the one to leverage easily resources offered by a Cloud provider (knowing that it might restrict portability of the application outside of this Cloud provider infrastructure).
In the end, for some users, it’s an interesting possibility as it allows to benefit from Alien4Cloud collaborative and productivity Devops features for the enterprise even if portability is not a prime concern at first.
We can now extend the capabilities of our orchestrator by providing custom on-demand resources. For example, this can be used to take the advantages of AWS services that are not managed natively by our orchestrator (such as Elastic Load Balancer, RDS Database and so on …). In combination with recently added Ansible support as implementation artifact, it’s now easy to leverage on extended IAAS services in your topologies.