OpenStack Ottawa MeetUp - April 3rd 2018

Agenda
17:00-18:00 - Food, drinks and Networking
18:00-18:30 - Intros, Infos, Updates and Queens
18:30-19:10 - WIND
19:10-19:20 - Break
19:20-20:00 - CENGN

Let’s Say Thanks To Our Sponsors

Your MeetUp Team
Raymond Maika
Paul Belanger
Carlos Rivera
Stacy Véronneau

Now Let’s Talk Openstack!
https://www.openstack.org/summit/vancouver-2018/

OpenStack Days Canada - 2018
Around October 10th
● Sponsors
● Speakers
● Helpers
● Stackers

OpenStack Days Canada Committee
OSDC is now based on OpenStack Days Nordic model
● Will alternate from Montreal to Ottawa or
other Canadian cities willing to host the
event.
Committee members:
● Mohammed Naser (Montreal)
● Stacy Véronneau (Montreal)
● David Moreau Simard (Montreal)
● Paul Belanger (Ottawa)
● Raymond Maika (Ottawa)
● Noura Daadaa (Ottawa)
● Curtis Collicutt (Toronto)
● Stephen Gordon (Toronto)
● George Mihaiescu (Toronto)
● Corey Erickson (Edmonton, Calgary, Vancouver)
● John Studarus (USA)
● Denise Ridolfo (OpenStack Foundation)

Reach out to your organizers for talk submission,
sponsorship or any MeetUp related topics.

Join us on Slack!
http://openstack-canada-slack-invite.herokuapp.com/

Our Speakers
Our first speakers will be Ian Jolliffe and
Yaniv Zadka from Wind River. They will talk
about Wind River and their upstream focus
areas, they'll do a demo of their platform
and also give us an update from the Dublin
PTG (Besides #Snowpenstack).

Our Speakers
Our second speaker will be Raymond Maika
from CENGN who will follow from his talk at
OpenStack Days Canada about OpenStack Helm.
This talk will answer the question: How do
you run OpenStack on Kubernetes? The
answer, OpenStack Helm Charts.

Stacy Véronneau
● Senior Cloud Architect at CloudOps. Focus
on OpenStack and GCP.
● Using public cloud resources since 2007
● OpenStack user since Grizzly
● OpenStack MeetUp organizer across Canada
● Speaker at OpenStack Days and Summit
● OpenStack Mentor since August 2017
● Canadian OpenStack Ambassador since October
2017

Long Live The QUEENS!
● 17th release of OpenStack
● Released on February 28th 2018
● Will be Followed by Rocky on August 28th
● Dedicated to the memory of Shawn Pearce, founder
of Gerrit which has been at the center of
OpenStack’s development process since the Diablo
release.

● New in Nova - Support for vGPUs
○ Cloud admins can define flavors that request vGPU
resources and specify resolutions for vGPUs, and end
users will be able to boot vms which have vGPUs.
● New in Cinder - 1 volume to Multiple VMs
○ one of the most highly-requested features in cloud
environments. An obvious benefit is that you can have
two nodes accessing the same volume, so if one goes down,
the other can take over and has access to the data, which
supports enterprise users who need robust environments
and users who need high availability.

● New in Ironic - Rescue Mode
○ Ironic user growth is going way up
○ With Rescue Mode, Ironic users now have a safety net if
something won’t boot correctly, something’s misconfigured,
they lose an SSH key, etc
● New in Kuryr CNI Daemon - Improving scalability
○ Growing OpenStack project that bridges container networking
frameworks and OpenStack networking.
○ CNI daemon watches pod events now instead of waiting on K8s
API.

● New in Horizon - WYSIWYG for orchestration

● New in Policy - RBAC in code
○ Policy.json SNAFU gone
○ RBAC policies are now in code in the majority of
projects, providing better communication about service
policies and the ability to set more granular defaults in
RBAC policies through that easier discoverability.
○ Congress???

● New Projects
○ OpenStack Helm
■ Package Manager for K8s
○ OpenStack Masakari
■ Helps OpenStack clouds achieve high availability from
various vm failure events and automates the rescue
mechanism.
○ OpenStack LOCI
■ Lightweight OCI (Open Container initiative)
compatible images of OpenStack services.
○ OpenStack Cyborg
■ Management framework for accelerators. Great for
Telco NFV workloads.

● More news on this release at:
○ https://www.openstack.org/software/queens/
○ https://releases.openstack.org/queens/highlights.html

What’s next for ROCKY?
● Fast forward upgrade. I.e., go from
Liberty to Rocky!
● Minimum bandwidth and bandwidth-based
scheduling. Good for NFV and cloud
providers.
● Enable mutable configuration across
services. Change configs without
restarting a service!

OpenStack ‘S’ is STEIN!
Steinstraße or "Stein
Street" in Berlin, can
also be conveniently
abbreviated as

Thank You!
Now Let’s Hear Our First Speakers

© 2018 WIND RIVER. ALL RIGHTS RESERVED.
WHEN IT MATTERS,
IT RUNS ON WIND RIVER.
OpenStack Ottawa
Meetup
Ian Jolliffe / Yaniv Zadka

2 WHEN IT MATTERS, IT RUNS ON WIND RIVER.© 2018 WIND RIVER. ALL RIGHTS RESERVED.
Our software has been deployed in over 2 billion
devices; into environments, systems, and
applications subject to the highest standards of
safety, security and performance.

We believe in the power of Cloud technologies to transform the safety and
security of Software Defined Infrastructure

We invest and innovate in technology and capabilities
that improve reliability, performance, safety and
security of critical infrastructure

Deployed Throughout Wired and Wireless Networks
Secure, reliable, low-latency networking for service providers
Core
Networks
IoT
Infrastructure
Network
Appliances
Radio
Access
Network
Content
Delivery
Networks
Virtual
CPE
Multi-access
Edge
Computing
Vertically Integrated → Multivendor4G → 5GProprietary → Open
Physical → Virtual Appliances → Servers

Software Defined Infrastructure Challenges
Cloud
Enabled
NFV
Telecom
Cloud
§ Open hardware
§ Open API’s and solutions
§ Fast service deployment times
§ Still carrier grade
§ Still high performance demands
§ Complex networks
§ Huge mix of hardware (mostly proprietary)
§ Time-consuming to deploy equipment
§ Time-consuming to deploy services
§ Carrier grade and high performance demands
Traditional Telecom
Vertically Integrated
OpenStack Is an Excellent Foundation

EVOLUTION TO 5G
5G Cloud Centric from Day 1

ADJACENT APPLICATIONS
Critical Infrastructure Satellite Communications
Value and Requirements Match

External Networks
Titanium Cloud System Architecture
Layer 2 Switch
Titanium Cloud
Storage
NodeStorage
Node
Storage
NodeStorage
Node
Control
Node
Control
Node
Compute Node
VM VM VM
Accelerated vSwitch
Compute Platform
Compute
NodeCompute
NodeCompute
NodeCompute
NodeCompute
NodeCompute
NodeCompute
NodeCompute
Node
Compute
NodeCompute
NodeCompute
NodeCompute
NodeCompute
NodeCompute
NodeCompute
NodeCompute
Node
Compute
NodeCompute
NodeCompute
NodeCompute
NodeCompute
NodeCompute
NodeCompute
NodeCompute
Node
Layer 3 Routers

Fully Compatible with ETSI NFV Standards
§ VIM: Virtualized Infrastructure Manager
Manages NFVI compute, storage and
networking
Abstracts NFVI details from VNFM
ETSI-aligned northbound APIs to VNFM
and NFVO
§ NFVI: NFV Infrastructure
Carrier Grade Virtualized Hosting
Infrastructure
oss
NFVI
NFVO
Orchestrator
VNF
Manager(s)
Virtualized
Infrastructure
Manager(s)Virtualization Layer
Virtual
Computing
Virtual
Computing
Virtual
Computing
Hardware Resource
Computing
Hardware
Computing
Hardware
Computing
Hardware
EMS 1
VNF 1
EMS 1
VNF 1
EMS 1
VNF 1
VNF
Manager(s)VNF
Manager(s)
Service, VNF
and
Infrastructure
Description
Titanium
Cloud

Fully Scalable System-Level Architecture
Highly-Available
Edge Solution
Two servers
Compute
VM
Control
VM VM
Storage
1:1 protected pair
of servers
Compute
VM
Control
VM VM
Storage
Compute
VM VM VM
Compute
VM VM VM
Top of Rack
Control
Storage
Control
Storage
Frame-Level
Solution
4 –100 servers
Compute
VM VM VM
Compute
VM VM VM
Top of Rack
Control
Storage
Control
Storage
Compute
VM VM VM
Compute
VM VM VM
Top of Rack
Control
Storage
Control
Storage
Compute
VM VM VM
Compute
VM VM VM
Top of Rack
Control
Storage
Control
Storage
Large-Scale Data Center
Solution
Hundreds of servers
Compute
VM VM VM
Compute
VM VM VM
Top of Rack
Compute
VM VM VM
Compute
VM VM VM
Top of Rack
Compute
VM VM VM
Compute
VM VM VM
Top of Rack
Control
Control
Compute
VM VM VM
Compute
VM VM VM
Top of Rack
Compute
VM VM VM
Compute
VM VM VM
Top of Rack
Compute
VM VM VM
Top of Rack
Compute
VM VM VM
Control
Control
Multi-region cloud
Compute
VM
Control
VM VM
Storage
Minimum-Footprint
Edge Solution
Single server

Titanium Cloud Ecosystem Partners
SDN Controllers
Hardware Infrastructure
System IntegratorsVirtualized Applications
Service Orchestrators

Titanium Cloud Architecture Details
Based on standard open source components
Add critical real-time performance
enhancements to KVM
Add carrier grade accelerated vSwitch
Add carrier grade cloud management and
telco middleware functions
Add carrier grade storage cluster
Host any guest OS
Titanium Cloud Software
Virtual Network
Functions (VNFs)
OSS/BSS Service Orchestration
Any Guest OS
Control Node
Virtualization Infrastructure Manager
(VIM)
Fault
Management
Software
Management
Performance
Management
OAMP
VM High Availability Management
Compute Node
Carrier
Grade
Accelerated
vSwitch
Virtual NICs Intel® DPDK
Storage Node
Carrier Grade
Storage Cluster
Centralized, Local,
or SAN
Carrier Grade Networking
VM
vCPE
VM
vEPC
VM
Other
Carrier
Grade
KVM
KVM
Real-Time
Profile
Low
Latency
Hardened Linux

#SnowpenStack
Image: Cormac Devlin
Well Maybe
https://twitter.com/hashtag/SnowpenStack

Dublin PTG
§ Edge use case working group
§ Nova – working on
– Live migration
– Live resize
– NUMA topology in placement algorithms
§ Masakari – working on Guest API for Introspective guest monitoring

Big News
Edge Stack - Innovation
https://www.akraino.org/
http://blogs.windriver.com/wind_river_blog/2018/03/wind-river-joins-open-
source-initiative-to-accelerate-telecom-edge-cloud-deployments.html

Demo
© 2018 WIND RIVER. ALL RIGHTS RESERVED.17

™

OPENSTACK-HELM:
RUNNING OPENSTACK SERVICES ON KUBERNETES
RAYMOND MAIKA
APRIL 3RD, 2018

OpenStack-Helm components
• Kubernetes
• Kolla/LOCI images
• Helm
• OpenStack-Helm Charts
BM/VM - Ubuntu or CentOS
Networking
(CNI)
Docker
runtime
OpenStack
Kolla
images
Helm
OpenStack-
Helm charts
Storage
CephCalico

Kubernetes
• Leading container orchestration engine
• Provides several different types of container
deployments that are useful in deploying and
maintaining the state of OpenStack services
– Deployments to specific nodes based on
labels
– Constraints on how many replicas are
distributed across nodes
• Min/max that are up, fault tolerance levels
– Service endpoints that can map to
OpenStack service endpoints

OpenStack Dockerized
• Kolla is an OpenStack project
• Mission statement: “Kolla provides production-ready containers and deployment tools
for operating OpenStack clouds that are scalable, fast, reliable, and upgradable using
community best practices.”
• Creates stable docker images
• Tagged images based on OpenStack major releases
– 3.x  Newton
– 4.x  Ocata
– 5.x  Pike

OpenStack Dockerized (part 2)
• OpenStack LOCI is a project designed to quickly build
Lightweight OCI compatible images of OpenStack services
• LOCI is an attempt to create the lightest container images
possible for core OpenStack services
• Optimization for CI/CD and stability
• Can be built from ubuntu:xenial or centos:7 base images

Helm
• “Kubernetes Package Manager”
• Helps to model, configure, and upgrade applications
deployed on k8s
• Facilitates management for immutable containers
– Allows templatizing configurations for install-time
overrides or upgrades
– Greater portability by allowing environment variables to
be injected into configurations at deployment
• Includes rollback workflow when running upgrades

OpenStack-Helm Project
• The OpenStack-Helm project aims to provide a collection of Helm charts to
deploy highly available OpenStack and related services on K8s
• OpenStack-Helm is an official OpenStack project
• Charts provided by OpenStack-Helm currently include (but not limited to):
– openstack-helm: (core OpenStack charts)
• Barbican, Ceilometer, Cinder, Glance, Gnocchi, Heat, Horizon, Keystone,
libvirt, Magnum, Neutron, Nova, Rally
– openstack-helm-infra: (charts for supporting services)
• Ceph, Ingress, MariaDB, Memcached, RabbitMQ, OVS

OpenStack-Helm Charts
• Chart is the basic unit of Helm
• A chart describes an application’s full
deployment, including:
– Templates for all K8s objects to run the
service
– Templates for all OpenStack service configs
– A YAML file called values.yaml that sets all
variables in the chart’s templates
• Tiller (helm server) processes the values from the
YAML files, fills templates and deploys K8s
resources
• Ref: https://docs.openstack.org/openstack-
helm/latest/
HelmChartCharts
Helm-toolkit
etc
*custom* *Conf.tpl
_policyjs
on.tpl
*_paste.i
ni.tpl
Templates
bin
*.tpl
Service.yaml
Deployment.yaml
DaemonSet.yaml
StatefulSet.yaml
Job*.yaml
Configmap-bin.yaml
Secret*.yaml
Ingress.yaml
Values.yaml Requirements.yaml Chart.yaml

Deployment Pattern
• The following pattern is used to deploy OpenStack services using Helm:
– Init and sync to the database
– Build ConfigMap in Helm
– Create Keystone services, users, and endpoints
– Create Deployments or DaemonSets of the control and compute plane Pods
to nodes based on labels
– Use a Kubernetes service to distribute requests to all Pods in the ReplicaSet
• All managed by the Helm server, which can also distribute required changes for
config updates or service upgrades

Deployment: CNI Network
• First after deploying a K8s cluster, need to
initialize a CNI plugin
• In this demo, that is Calico
• Calico is a pure L3 CNI plugin, uses host
gateways to route traffic
• Optional IPIP tunneling between hosts
• Calico and Flannel are supported by openstack-
helm
– Deployed by charts maintained in openstack-
helm-infra
Networking
(CNI)
Calico

Deployment:
OpenStack-Helm Charts
• Once there is a CNI plugin we can start
deploying containers
• The OpenStack-Helm Charts use the
Helm server to deploy and configure
containers on the hosts’ Docker runtimes
• OpenStack Kolla images are Docker
images for OpenStack services
• There are also charts to deploy Ceph and
other OpenStack-related services for
storage and messaging
Docker
runtime
OpenStack
Kolla
images
Helm
OpenStack-
Helm charts
Storage
Ceph

Deployment: Data
• Need data storage for OpenStack services
– Many OpenStack services save their state to a database
– Databases are stateful, need to store their data in
persistent storage
– Ideally with K8s, that storage is available to all worker
nodes
• Ceph is a well-known open source distributed storage solution
– Ceph has docker images available (ref: https://github.com/ceph/ceph-docker)
• These images can be leveraged to run Ceph on K8s
– HA accomplished with several mon and OSDs distributed
across the cluster
– Distributes the volumes used by database pods
Storage
Ceph

Deployment: Data (2)
• With ceph deployed, can deploy the database
onto ceph-backed storage
– This is done with a StorageClass in
Kubernetes
– Allows pods to mount a volume that is
provided (bound) by the StorageClass
• MariaDB is deployed in a 3-pod cluster across
nodes (across nodes with controller label)
• Now the deployment of OpenStack services can
begin
Helm
OpenStack-
Helm chart:
MariaDB

Deployment: Keystone
• First OpenStack service deployed is almost always Keystone, as other services
will register with it later
• Objects being created in Kubernetes by the Helm chart are:
– Secrets with credentials and tokens to be shared to other services
– Cronjobs – Keystone fernet key rotations
– One-time jobs – database init, database sync
– Pod(s) – keystone-api
– ReplicaSets – keystone-api
– Service – keystone-api (load balances to all pods, IP from the service CIDR)

Deployment: Glance, Cinder
• Two basic units for Image and Volume services, along with Nova and Neutron
make up the minimal deployment of an OpenStack cloud
• Helm will deploy the following objects to provide these services:
– Secrets – service credentials for keystone
– One-time Jobs – db_init, db_sync, keystone_[endpoints,user,service], glance-
bootstrap
– Pods – glance-api, glance-registry, cinder-api, cinder-scheduler, cinder-volume
– ReplicaSets – glance-api, glance-registry, cinder-api, cinder-scheduler, cinder-volume
– Services – cinder-api, glance-api, glance-registry

Deployment: Nova
• Basic unit for compute
• Helm deploys the following:
– One-time Jobs – db_init, db_sync, keystone_[endpoints,user,service]
– Pods – nova-api-osapi, nova-api-metadata, nova-conductor, nova-scheduler,
nova-consoleauth, nova-libvirt, nova-compute*
– ReplicaSets – nova-api-osapi, nova-api-metadata, nova-conductor, nova-scheduler,
nova-consoleauth
– Services – nova-api, nova-metadata

Deployment: Neutron
• Basic unit for networking
• Helm deploys the following:
– One-time Jobs – db_init, db_sync, keystone_[endpoints,user,service]
– Pods – neutron-server
– ReplicaSets – neutron-server
– Services – neutron-server

Legend
Demo topology
Pod
con-interface
veth
pairs
IPIP
tunnel
Bare metal
helm-compute[01,02]
ens1f0
helm-controller[01,02]
ens1f0
Calico-node
keystone
nova-
metadata-api
Calico-node
openvswitch
Nova-compute
caliABCcaliABC caliXYZ
glance-api
Kernel routing tableKernel routing table
tunl0 tunl0

Legend
Demo topology (with VMs)
helm-node[01,02]
ens1f0
helm-node[01,02]
ens1f0
Calico-node
keystone
nova-
metadata-api
Calico-node
openvswitch
Nova-compute
vmA vmB vmZ
caliABC tapXYZcaliABC caliXYZ
VM
Pod
con-interface
vm-interface
veth
pairs
glance-api
Kernel routing table
br-tun
Host interface
tunl0 br-tuntunl0
IPIP
tunnel
vxlan
tunnel
openvswitch
Kernel routing table

Benefits of OpenStack-Helm
• Using charts from OpenStack-Helm is a step towards making OpenStack “Cloud Native”
– Lower overhead by containerizing (kola/LOCI), orchestrating (K8s) OpenStack
– Leverage tooling ecosystem of the CNCF – Prometheus, Fluentd, etc
• See all at: https://www.cncf.io/projects/
– Step towards more scalable and distributed OpenStack control plane
• Use native Kubernetes features to manage OpenStack services
– Rolling upgrades
– Healthchecks
– Replica parameters (min/max available, maxUnavailable)
– Logging from and access to all services available across all controllers

OpenStack Ottawa MeetUp - April 3rd 2018

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (19)

Similaire à OpenStack Ottawa MeetUp - April 3rd 2018

Similaire à OpenStack Ottawa MeetUp - April 3rd 2018 (20)

Plus de Stacy Véronneau

Plus de Stacy Véronneau (14)

Dernier

Dernier (20)

OpenStack Ottawa MeetUp - April 3rd 2018