+ All Categories
Home > Internet > OpenStack Ousts vCenter for DevOps and Unites IT Silos at AVG Technologies

OpenStack Ousts vCenter for DevOps and Unites IT Silos at AVG Technologies

Date post: 28-Jul-2015
Category:
Upload: jakub-pavlik
View: 112 times
Download: 0 times
Share this document with a friend
19
OpenStack Summit 2015 Vancouver @tcpcloud OpenStack Outs vCenter for DevOps and Unites IT Silos at AVG Technologies
Transcript

OpenStack Summit 2015 Vancouver

@tcpcloud

OpenStack Outs vCenter for DevOps and Unites IT Silos

at AVG Technologies

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

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

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, …

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

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

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

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

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 OpenStack Architecture

AVG Model Driven CI/CD

Monitoring Architecture

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

Thank you! Questions?

Jakub Pavlí[email protected]@JakubPav

Pavel Zají[email protected]


Recommended