Hyper-scaling on Openstack with Open Source tooling A use case in - PowerPoint PPT Presentation

Hyper-scaling on Openstack with Open Source tooling A use case in deploying hyper-scale grid computing on Open Telekom Cloud

Why Open Source? Open Open Design Open Choice Standards Community Lead Contributor Model No-Lock in Cloud Design Patterns Standards Community Tested Application Design Patterns Interchangeable Organizations: Distributed Systems Design Patterns Components IEEE, ISOC IEEE ISOC, W3C 3C, IET IETF, IAB IAB, ET ETSI SI, OAS ASIS IS, NIS NIST, CSCC, CSCC, Interoperability ANSI ANSI Reusability Invest in People not Software

Why Openstack ? User Benefits Benefits to Cloud Provider Community: The OpenStack community Community: Sharing ideas with the community is nearing 10,000 members in nearly 100 allows our Developers to learn fast and deliver countries , with foundation support by more than quicker. Contributing advances the entire 200 companies. ecosystem Mixed Hypervisor: OpenStack is the only solution Research & Development: Lowers our R&D cost that allows for mixed hypervisor IT environments and speeds time to market for new PaaS services. Open Source: Open source solutions are now Open Source: Interoperability with most open widely accepted and adopted after 20 years in the source projects such a Kubernetes, Spark, Etc enterprise, paving the way for OpenStack success. providing us the ability to deliver standardized services. Standards: provides a common, open standard Standards: Standardization allows us to delivery through its API and allows portability between cloud environments. T-Systems Hybrid Cloud and Public Cloud and Private Cloud solutions Public Cloud based on Openstack (Same architected exactly the same. Architecture) providing interoperability and ease of We can deliver new PaaS services within 90-120 migration or Burst scenarios. days of requirements from customers.

Openstack Contribution  Adaptability and access to the source code  The open architecture design gives in-house IT more scope to tailor the technology to specific needs  Participating in the community enables us to influence developments  Community: many providers and solutions that enhance functionality  Establishment of multi-cloud scenarios  Hardware neutrality: connectors are available for almost all storage, server and network components on the market  High degree of standardization (open APIs)  Resources can be provisioned and marketed across provider boundaries Source: stackalytics.com  Data and applications can be transferred from provider to provider

How do we contribute to the Open Source community  We developed the Tricircle project which allows Openstack to be a viable Public Cloud architecture.  We contribute regularly to the project listed to the right as leader or team member. Zaqar  We are on the board of governors for Openstack Kuryr  The Openstack and Open Source community benefit Tacker from much of the Research and Development work we Rally do for the public cloud and private cloud services.  We have circa 5,000 engineers dedicated to the Ceilometer Openstack projects for Public and Private Cloud Search Light Solutions who are leading the way on AI, ML, IOT, Karbor Kubernetes Container services. Manila  Corporate member of the Linux Foundation and on Neutron governing board of CNCF, Member LF Deep Learning Zun Foundation. Heat Tricircle

Hybrid Cloud Solution based on OpenStack Small scale Datacenter of O&M Team choice Budapest TSI Datacenter • Public Cloud based on Openstack  Public Cloud Architecture on-premise at customer site or hosted location  Agility and scalability built in  Cloud Native capability Data link (Hybrid/Private Region to public OTC) E.g. Ethernet Connect or MPLS Management Link (OPS – public OTC) Management Link (OPS – Hybrid/Private Region)

Deployment Tooling with Terraforms and Ansible

What is Terraform ?  Terraform is a multi-cloud DevOps tool for building, changing, and versioning infrastructure safely and efficiently. Available as Open Source or Enterprise License.  Enables Infrastructure-As-Code deployments  Open Telekom Provider developed for Terraform

What is Ansible ?  Application Deployment Tooling  Agentless Architecture  Integrates seamlessly with Terraforms

Grid Computing in Finance Industry - Use Case for OTC

What is Grid Computing Grid computing is a distributed architecture of large numbers of computers connected to solve a complex problem. In the grid computing model, servers or personal computers run independent tasks and are loosely linked by the Internet or low-speed networks. Computers may connect directly or via scheduling systems.

Finance Use Case (Grid Computing) Business Requirements • Bank was looking to cloud computing to carry out their complex calculations, marking a shift from investing heavily in in-house systems that are expensive to develop, maintain and upgrade. • Regulatory and Business demands such as Fundamental review of the trading book (FRTB)  Derivatives Valuation Adjustments (XVA) • End-Of-Day & Monte Carlo • IT Requirements • Transforming IT Operations to DevOPS methodology. • Standardized on Open Source tooling and systems such as Ansible, Terraforms, Kubernettes, Kafka, etc) • Need for massively scalable cloud services for Grid Computing, Big Data, and Devops( Kubernetes, ML, Analytics, Open Banking) • Opex payment model. • Do not want to invest in on premise servers that are not used much of the time or ever have enough capacity. • Must speed up time to results to the business (Currently 36 to 48 hours) on FRTB and XVA calculations.

Grid Computing Requirements and Challenges Primary Benefit to Bank – Time is money Technical Requirements Capacity requirements Improvements in Processing time 26,0 ,000 vCPUs minimum 50,0 ,000 vCPUs Burst Grid Software: Tibco Gridserver Ch Chal allenge ges to o Deliv Delivery API Gateway overloaded – Rearchitectected Openstack API services to Infrastructure deployment with Terraform handle up to 10,000 API calls a second. Server provisioning to slow due to delay in image services deployment of images. Improved storage network capacity and latency as well Server Configuration with Ansible image distribution across pools). Elastic Compute (ECS) and Elastic Volume Service Required lots of very large hosts which were not already available. (EVS) Deployed 2000 additional host to meet demand.

Deploying the Grid using Terraforms Full Grid deployed to OTC Terraforms Plan resource "opentelekomcloud_compute_instance_v2" "engine_node1" { count = "${var.vm_engine_count}" availability_zone ="eu-de-01" name = "${var.project}-node${format("%02d", count.index+1)}-az1" image_name = "Enterprise_Windows_STD_2012R2_XEN" flavor_name = "s2.medium.4" key_pair = "${openstack_compute_keypair_v2.keypair.name}" security_groups = [ "AD" ] OTC OTC API #ANSIBLE scripts user_data = "#ps1\nGet-NetAdapter\nnet user ansible Test1234+ /add\nnet localgroup administrators ansible /add\n#ps1\nGet- NetAdapter -name 'Local Area Connection' | Set-DnsClient - ConnectionSpecificSuffix cloudgrid.bank.com - RegisterThisConnectionsAddress:$true - UseSuffixWhenRegistering:$true\nSet-NetFirewallProfile -Profile Domain,Public,Private -Enabled False " Circa 2 Hours to deploy 15,000 vCPUs