tcp cloud & AVG User Story. Does your IT department’s left hand talk to the right hand? Finally ours does at http://www.avg.com/eu-en/homepage! This is the story of OpenStack as our salvation, and important lessons learned in technology and IT politics. Our appsdev team’s devops abilities were being held ransom on vCenter, so we wanted public cloud agility for dev/test/staging. With the help of our IT partner…Full session details here: http://awe.sm/r9Ekr

1. OpenStack Summit 2015 Vancouver
@tcpcloud
OpenStack Outs vCenter for
DevOps and Unites IT Silos
at AVG Technologies

2. Agenda
• About AVG and tcpcloud
• AVG
• tcpcloud
• AVG Goals
• Where we started
• AVG Infrastructure Layers
• PoC Findings
• Implementation Phases
• Cloud Modules
• Production Architecture
• OpenStack Architecture
• Model Driven CI/CD
• Stagging Deployment Process Comparison

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. About tcp cloud
• ISO Certifications (ISO 9001, ISO 20000-1, ISO 27001)
• Certificated experts (cloud, hardware, virtualization, networks, OS, etc…)
• Active in global community (OpenStack, OpenContrail, SaltStack, etc…)
• Own Hi-Tech Datacenter (TIER III, 20kW per rack, hundreds 10Gbps ports, etc…)
• Focused on private open cloud solutions and services (since 2011)
• Maximum Openness
• Open source of course…
• But also technology like
• Hyper-V, VMware, PowerKVM, …
• Thomas-Krenn, IBM, HP, Dell, …
• Juniper, Cisco, …
• Ubuntu, CentOS, Windows, …

5. 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

6. AVG Former Deployment Process

7. 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

8. AVG Infrastructure Layers

9. 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
• Up to 300
compute nodes

10. 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

11. 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

12. 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

13. Cloud Modules Drivers/Backends
Nova Cinder Neutron CM
Monitoring & Billing by

14. AVG OpenStack Architecture

15. AVG Model Driven CI/CD

16. Monitoring Architecture

17. AVG Dashboard

18. 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 teams
Cloud
• Step 1 (5 min)
• Choose template
• Step 2 (10 min)
• Infrastructure deployment
• Step 3 (20 min)
• Application deployment
• Automated tests
Total cca 0,5 h
Staging deployment process description

19. Thank you!
Questions?
Jakub Pavlík
j.pavlik@tcpcloud.eu
@JakubPav
Pavel Zajíc
pavel.zajic@avg.com