- La colaboración entre Seguridad y FinOps puede generar beneficios ocultos en la nube
- El papel del CIO en 2024: una retrospectiva del año en clave TI
- How control rooms help organizations and security management
- ITDM 2025 전망 | “효율경영 시대의 핵심 동력 ‘데이터 조직’··· 내년도 활약 무대 더 커진다” 쏘카 김상우 본부장
- 세일포인트 기고 | 2025년을 맞이하며… 머신 아이덴티티의 부상이 울리는 경종
Deploying a multi-service, cloud-native application leveraging IST and ICO
In the first part of this series, we looked at building workflows around IST (Intersight Services for Terraform) automations to provision IKS (Intersight Kubernetes Service) infrastructure and deploy a sample cloud-native application with ICO (Intersight Cloud Orchestrator).
In part 2 and part 3, we leveraged IST and ICO to do a complete deployment of a multi-service Tomcat application and instrumentation for AppDynamics insights. Then in part 4, we created and executed TFCB (Terraform for Cloud Business) workspaces for the complete deployment of a cloud-native application, and instrumentation for AppDynamics insights.
Use case
In this final part of the series, let’s now take that automation a step further by provisioning ICO workflows that leverage the TFCB workspaces that we just created. Let’s take a look at a use case of deploying a multi-service, cloud-native application leveraging IST and ICO. As a value add, the ICO workflows will include AppDynamics Insights for this cloud-native application leveraging AppDynamics Cluster Agent.
In the above diagram, each of the blocks refer to an ICO workflow. As you can see, a single workflow encapsulates not only creating all the TFCB workspaces, assign variables and also account for dependencies. The above workflows will:
- Set up and execute workflow to provision infrastructure and deploy application accounting for any application dependencies
- Set up and execute workflow to generate application load
Please check out this entry in DevNet Code Exchange for details on this use case:
Conclusion
As part of adopting a cloud first strategy, Enterprises will be most successful when they execute on a well formulated cloud strategy. They may well start with the traditional lift-and-shift approach and migrate to cloud native platforms to get the maximum benefits of the cloud. Building workflows, abstractions and ability to swap components becomes imperative as enterprises experiment and innovate.
The main idea behind this blog series is to give the reader a glimpse of how one can start to build a library of workflows and swap them in and out to meet the ever-changing business requirements. It’s just like those Lego blocks. You pick and choose the blocks you want, and Voila! Your masterpiece is ready.
Additional Resources
Links to previous blogs in this series
- “Hello IKS”… from Terraform Cloud!
Provisioning IKS infrastructure and deploying a sample cloud-native application with IST and TFCB (Terraform Cloud for Business).
See DevNet Code Exchange. - “Hello IKS”… from Intersight Cloud Orchestrator!
Provisioning IKS infrastructure and deploying a sample cloud native application with ICO.
See DevNet Code Exchange for details. - Ease your legacy Tomcat App Deployments with IST
Deploy a legacy micro services Java app on VM based infrastructure with IST and AppDynamics.
See DevNet Code Exchange for details. - Step up your legacy Tomcat app deployment with ICO
Deploy a legacy micro services Java app on VM based infrastructure with ICO and AppDynamics.
See DevNet Code Exchange for details. - Modernize both your apps and deployments with IST
Deploy a cloud native micro services Java app on IKS leveraging IST and AppDynamics.
See DevNet Code Exchange for details. - Step up your Cloud-native deployments with ICO
Deploy a cloud native micro services Java app on IKS leveraging ICO and AppDynamics.
See DevNet Code Exchange for details.
We’d love to hear what you think. Ask a question or leave a comment below.
And stay connected with Cisco DevNet on social!
LinkedIn | Twitter @CiscoDevNet | Facebook | Developer Video Channel
Share: