Post on 12-Feb-2017
@tcpcloud
tcp cloud in
AVG
Agenda• About AVG
• AVG• AVG Goals
• Where We Started• AVG Infrastructure Layers
• Production Architecture• OpenStack Architecture• Model Driven CI/CD
• Stagging Deployment Process Comparison
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
AVG (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
• No time for innovations
AVG Former Deployment Process
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
AVG Infrastructure Layers
Server Virtualization
Network Virtualization
Infrastructure Orchestration
Infrastructure Service
Server & Apps
Neutron SDN solution• All clouds are about networking• Key and the most crucial component of OpenStack• High Availability, Scalability, Migration, Multi-tenancy,
Performance, Security• LBaaS, FWaaS, Service Chainning• Possible solutions:
• Vanilla Neutron• Cisco APIC• VMWare NSX• Juniper Contrail
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
Cloud Modules Drivers/Backends
Nova Cinder Neutron CM
Monitoring & Billing by
AVG Model Driven CI/CD
AVG Dashboard
Staging deployment process
Today• 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 teamsCloud
• Step 1 (1 min)• Choose template
• Step 2 (5 min)• Infrastructure deployment
• Step 3 (10 min) • Application deployment• Automated tests
Total cca 15 min
Staging deployment process description
Thank you! Questions?
Martin KšicaMartin.ksica@avg.com
Pavel Zajícpavel.zajic@avg.com