OpenStack Journey in Tieto Elastic Cloud

OpenStack Journey in Tieto Elastic Cloud

Agenda• About Tieto

• The starting point

• PoC Findings

• Production Architecture

© Tieto Corporation

About TietoTieto is the #1 cloud service provider in Northern Europe with over 150 cloud customers in the region.

Tieto aims to become customers’ first choice for digitalization as the leading Nordic IT service provider.

Turnover is approximately €1.5 billion

Tieto’s shares are listed on NASDAQ in Helsinki and Stockholm

NorwayFinland

Sweden

Czech

Republic

India

RussiaEstonia

3

OpenStack in Tieto (where we started)✓ In 2015 Tieto provides scale-up focused IaaS cloud

offerings and unique application-focused PaaS services.

✓ Shared platform with full API-controlled infrastructure for horizontally scalable workload was missing.

✓ Since 2013, first internal projects evaluating OpenStack Havana, Icehouse in software development projects, utilizing Neutron / Open vSwitch.

✓ In 2016 announcing OpenStack cloud service for Tieto customers, based on tcp cloud (Mirantis) distribution and OpenContrail.


Tieto Goals

✓ Remove Vendor Lock-in

✓ Seamless On-Demand Capacity Fulfillment

✓ Robust Automation and Orchestration

✓ Adopt Innovative Open Source Solutions

✓ Infrastructure as a Code


We started with installer-centric distributions

● Initial evaluation deployments with PackStack/RDO, Fuel 5

with releases around Havana/Icehouse

● Was easy to learn, deploy first environments, gain some

experience

● … happy admins seeing first successful ping through

overlay


But then we realized it’s bring up and leave

● Systems were not easy to maintain later● Configuration in a flat file

○ compute node config looks like this ..., control node this …

○ deviations problematic to manage● Not safe to rerun without existing "compare

configuration" check● Manual changes need always to be documented as an

extra effort to ensure they’re reproducible


… leads to mixed configuration approach

● troubles to customize or extend○ partly due to difference in complexity Puppet vs

SaltStack/Ansible, yet improved with Reclass● results in mixed configuration approach

○ combination of configuration tool, scripts and manual changes

○ manual change has no record for later auditing or troubleshooting support


✓ Open Source – contribute own stuff

✓ Automation – fully automated approach without any manual tasks.

✓ Life cycle – not just deployment tool.

✓ Integration – natively integrated monitoring, log collections or self-generated documentation.

✓ OpenContrail knowledge – skilled team with huge operation experience for OpenContrail and OpenStack

✓ Not just OpenStack - partner who can implement any kind of open source (containers, CI/CD pipelines)

Key Criterias - Why tcp cloud?


Tieto Implementation Phases

• Design Orchestration• An internal application decomposition• Deployment automation• Staging environment

• Lab Setup• Based on OpenVswitch• RDO

• 2 datacenters• Model driven deployment automation

POC with OpenCont

rail (Q4 2015)

Production (Q2 2016)

Future

Lab testing

(Q1 2015)

• Another 4 datacenters• Up to 200 compute nodes• Docker integration (Kubernetes)

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 Chaining

✓ Possible solutions:

✓ Vanilla Neutron

✓ Midokura

✓ OpenContrail


Open source solution with possibility to buy commercial support

Licensing

High availability

Cloud gateway routing

Performance

Key Criterias - Why OpenContrail?

Interconnection between SDN and Fabric

Containers

Nord-South must be routed on physical Edge Routers Juniper MX

Native HA support is the most important criterion

Pps, bandwidth, scalability, etc. (9.6 Gbps)

Dynamically connection legacy world through EVPN or ToR Switches

Use same platform for containers

Tieto Facts✓ tcp cloud Mk.20 (Mirantis)

distribution✓ OpenContrail 2.21✓ Glance image repository

stored at Ceph✓ Cinder backend on Ceph✓ Heat orchestration


Cloud Modules Drivers/Backends

Nova Cinder Neutron CM

Monitoring & Billing by


Openstack Cluster Deployment - sample

© Tieto Corporation16

Experience so far

● complains we had on installer-type distros resolved● we got a robust, scalable infrastructure with

configuration under control● new challenges appear, mainly related to personal skills

and way of working○ sysadmins had to learn developers tools

© Tieto Corporation 17

Still not enough flexible?● over 30 management VMs● need to maintain, patch operating systems● more-or-less manual management of VMs, virtual

drives, too many haproxies, keepalived’s● long time to recover - reprovision manage VMs

OpenStack is just another application workload


Mirantis Cloud Platform Operations-Centric Fabric for BM, VM and Containers

Host Host Host Host Host Host Host Host

Kubernetes

Host Host Host

K8s master K8s minionsBMaaS pool

Ironic

OpenStack Control Plane

OpenStack Computes

K8s workloads

Mon

itorin

g an

d Lo

ggin

g

Bare Metal VMs Containers

Life

cycl

e M

anag

emen

t

18


OpenStack on Kubernetes

19


HA Transformation


PODs mapping to Nova service


Lifecycle Workflow example


Same Metadata Model

23

● No difference between Mk.20 and MCP

● Provide Hybrid - containers or VM

● Reclass YAML as primary method of defining sites

● Metadata model allows:• Hierarchical definition of

sites• Single location for all

operations● All changes as code commits

• Audit trail


Tieto Dashboard

Thank you! Questions?

Jakub Pavlí[email protected]@JakubPav

Lukas KubinLead Cloud [email protected]

Backup slides


Service Chaining Use Cases

NFV through Contrail

2 firewalls between application stacks


MCP Galera HA

29

Technology

OpenStack Journey in Tieto Elastic Cloud