Deployment of Juniper Contrail in AVG Technologies
0 likes642 views
The document details the deployment of Juniper Contrail at AVG Technologies, highlighting the company's goals to automate internal processes, eliminate vendor lock-in, and adopt open-source solutions. Key findings from the proof of concept include successful live migration and automated DNS registration, resulting in significant time savings in the deployment process. The document outlines implementation phases, criteria for choosing OpenContrail, and future plans for robust automation and orchestration.
Deployment of Juniper Contrail in AVG Technologies
- 1. Virtualization Forum 2015, Prague 7-OCT @tcpcloud Deployment of Juniper Contrail in AVG Technologies
- 2. Agenda • About AVG • Issues & Troubles • AVG Goals • The Chosen Solution • Benefits
- 3. About AVG Technologies • internet security, performance optimization, and personal privacy and identity protection applications • top global antivirus company • over 202 million active users used AVG´s software products and services • products distributed over 100 countries
- 4. AVG Issues & Troubles (Where we started) • IT Silos (different departments, technologies, domain specialists) • Manual deployment processes • Impossible to make frequent changes • Vendor specific technologies (VMware, Cisco, etc.) • Insuficcient APIs • Legacy virtualize architecture with VMware vCenter, VLANs and Fibre Channel • Very limited time for the innovations
- 5. AVG Goals • Remove Vendor Lock-in • Reuse current Hardware Infrastructure with minimum intial costs • Automate internal deployment processes (speed and complexity) • Self-service tool for application life cycle management • Robust Automation & Orchestration • Seamless On-Demand Capacity Fulfillment • Adopt Open Source Solutions based on OpenStack
- 6. AVG Infrastructure Layers Server Virtualization Network Virtualization Infrastructure Orchestration Infrastructure Service Server & Apps
- 7. AVG Implementation Phases PoC (Q4 2014) Pilot (Q1 2015) Production (Q2 2015) Future • Lab Setup • Design and test network approach • Integrate Hitachi storage • Live Migration • LBaaS • Automatic DNS • Design Orchestration • An internal application decomposition • Deployment automation • Stagging environment • Physical F5 integration • 2 datacenters • Model driven deployment automation • Another datacenter • Add compute nodes
- 8. Key Criterias - Why OpenContrail? • Licensing – open source solution with possibility to buy commercial support • High Availability – native HA support is the most important criterium • Cloud Gateway Routing – Nord-South must be routed on physical Edge Routers • Performance – pps, bandwith, scalability, etc. (9.6 Gbps) • Interconnection between SDN and Fabric – dynamically connection legacy world • Physicall F5 integration – LBaaS Heat resources
- 9. AVG PoC findings • Live Migration VM • Production instances booted from volume – Hitachi VSP driver • Automatic DNS registration • OpenContrail DNS – Virtual, Tenant • Glance image repository stored at EMC NFS • Heat orchestration
- 10. Cloud Modules Drivers/Backends Nova Cinder Neutron CM Monitoring & Billing by
- 11. AVG Model Driven CI/CD
- 12. AVG Dashboard
- 13. Staging deployment process Legacy • Step 1 (1 MD) • deploy F5 configuration • deploy FW and network configuration • Step 2 (3 MD) • spawn server • 1. deploy app+content • prepare application deploy scripts • Step 3 (3 MD) • basic tests • final tuning Total 48h in 10 days due delays when work is transmitted between teams Cloud • Step 1 (1 min) • Choose template • Step 2 (5 min) • Infrastructure deployment • Step 3 (10 min) • Application deployment • Automated tests Total cca 1/4 h Staging deployment process description
- 14. Thank you! Closer & Add. info in Juniper Presentation room Even TODAY Jakub Pavlík j.pavlik@tcpcloud.eu @JakubPav Pavel Zajíc pavel.zajic@avg.com