CI/CD (Continuous Integration and Deployment) is the success mantra for development teams. The need to accelerate the delivery of revenue-generating applications has resulted in application teams formalizing CI/CD practices and incorporating it into their app delivery mechanisms.
Many enterprises have evolved an approach of using multiple cloud environments to facilitate their CI/CD goals. Many line-of-business execs and their developers like the convenience of the public cloud for the ease of provisioning, configuring and using infrastructure. It helps accelerate the early part of the development cycle.They use the public cloud for development and testing, and then migrate the application to a production environment. This production environment can again be a public cloud or a private cloud environment implemented in their own data center. More often than not, it is a virtualized environment that is not quite a private cloud yet but has some degree of automation.
Historically, developers were not involved in the provisioning of application services such as load balancing or firewalls etc. There simply wasn’t a way for them incorporate these services in their development and test efforts. In the instance that they did need these services to simulate production use, there were lengthy delays in setting up the virtual services for dev and test workloads. Even virtual appliances did not address this issue since the lifecycle management was no less painful. So, what do most enterprises do? Development teams typically move quickly through the early part of the SDLC from development to test phase. But once they are ready for deploying apps in a production environment, they open an IT ticket requesting infrastructure resources to be allocated to the project. The IT team then assesses the resources available and allocates them, or submits a request to procure additional hardware before it can be configured and provisioned to the development team. As you can see in the following illustration, this is the process that slows down the app delivery process significantly.
Figure: Application provisioning with appliance-based ADCs
App teams that are driven by CI/CD goals need self-service mechanisms to provision application services for their dev, test, and production environments. Imagine a world where developers and testers are simply able to provision applications services on-demand, where they need it, and in a programmable way using familiar REST APIs. The IT team still provides the policies and the configuration settings through a centralized administration console and load balancers and VIPs are simply instantiated in software (on any VM, bare-metal server, or container) close to the application. And add to this, the power of real-time insights into the application that help troubleshoot network, latency, security, or end user experience issues as they debug their application. Watch this demo video of the Avi Vantage platform to see how to deploy a software load balancer and provision resources in less than a minute. Learn how you can enable self-service for your line of business teams and change the picture of application delivery from one represented by the previous graphic to the following one:
Figure: Self-service Application Provisioning with Avi Vantage
As you watch the video, look for the following capabilities that can help accelerate application delivery matching your CI/CD goals:
- App-centric view of infrastructure
- Apps, virtual services, and server pools color-coded by the health score
- Spin up a load balancer in <30 seconds
- Analytics dashboard
- Security dashboard
Try this in your own labs, either in the public cloud or in a private cloud by downloading a fully functional trial version at https://avinetworks.com/try.