Deployment Options
The CumuLogic platform can be deployed in a variety of situations, depending on how your users want to consume services. Since the CumuLogic platform is designed to work with multiple IaaS types (as well as supporting a pool of pre-installed systems, be they virtual or physical), you get flexibility in where you get your basic infrastructure.
Single Target Cloud
The simplest of deployment scenarios is to have a single target IaaS cloud, be it public or private. In this scenario, a single “target cloud” is registered with the CumuLogic controller, and all applications/services are deployed in that cloud. If that cloud has multiple “zones” available, they can be easily enabled within the CumuLogic controller.
This model is useful for:
- Cloud providers that want to add modular services to their IaaS cloud, making the move from IaaS to IaaS+.
- Private cloud operators that want to add those same modular services to their private cloud environment.
- Application development teams that want to deploy their applications and services on a single target IaaS environment.
Hybrid Model with Multiple Target Clouds
Once you have the CumuLogic controller provisioning services on one target cloud, why stop there? The controller is able to provide modular services and application deployment on multiple target IaaS clouds from the same controller. This can be any number of public clouds, private clouds or even pre-provisioned pools of pre-installed systems ready for allocation.
This model is useful for:
- Enterprise IT departments that want to provide application and service deployment consistency across the organization, while offering departments/teams different infrastructure targets, for example financial systems deployed to a private cloud and marketing applications deployed to a public cloud.
- Application owners that want to push dev/test deployments to a lower performance infrastructure environment, while staging and production are deployed into an infrastructure with a higher SLA.