starlingx
play

StarlingX Hardened Managed Kubernetes Platform for the Edge BRENT - PowerPoint PPT Presentation

Sep 11, 2023 •35 likes •225 views

StarlingX Hardened Managed Kubernetes Platform for the Edge BRENT ROWSELL STARLINGX TSC MEMBER GREG WAINES STARLINGX CORE BART WENSLEY STARLINGX CORE STARLINGX.IO Agenda Architecture Overview Deployment Models Day 1/Day

  1. StarlingX Hardened Managed Kubernetes Platform for the Edge BRENT ROWSELL – STARLINGX TSC MEMBER GREG WAINES – STARLINGX CORE BART WENSLEY – STARLINGX CORE STARLINGX.IO

  2. Agenda • Architecture Overview • Deployment Models • Day 1/Day 2 Operations • Edge Device Management

  3. StarlingX –Edge Virtualization Platform StarlingX provides a deployment- ready, scalable, highly reliable Edge infrastructure software platform Services from the StarlingX virtualization platform focus on • Easy deployment • Low touch manageability • Rapid response to events • Fast recovery A complete Edge orchestration platform for Bare Metal, VM and Container workloads * OTHER NAMES AND BRANDS MAY BE CLAIMED AS THE PROPERTY OF OTHERS

  4. Edge Computing Use Cases MEC == MULTI-ACCESS EDGE COMPUTING

  5. StarlingX –Evolution OpenStack • StarlingX Release 1.0 provided StarlingX Infrastructure (flock) A hardened OpenStack platform on dedicated physical servers Physical Servers • StarlingX Release 2.0 will provide Containerized Containerized A hardened cloud-native kubernetes Application Workloads OpenStack platform on dedicated physical servers Kubernetes Container Containerized Openstack platform StarlingX Infrastructure (flock) Ability to deploy kubernetes only Edge Physical Servers sites for containerized workloads

  6. Container Platform Details § Kubernetes for the orchestration of container workloads § Local replicated docker image registry § Container Runtime: docker § Networking: Calico § Persistent Storage: CEPH RBD § Package Manager § HELM § Armada for orchestrating the deployment of multiple Helm charts § Integration with openstack keystone § Local docker image registry authentication § Authentication/authorization of k8s API

  7. Container Platform Details (cont’d) § Containerized OpenStack application § Leveraging openstack-helm and armada for deployment § Stein based for release 2 § Networking back ends supported: § Containerized ovs § Bare metal ovs-dpdk § SR-IOV/PCI-PT § Supported services: § nova, neutron, glance, cinder, glance § keystone, barbican, heat, ironic, § ceilometer, aodh, panko, gnocchi

  8. StarlingX – Deployment Models • Scalable deployment models from 1-100 servers addressing the wide range of edge use Minimum-Footprint Highly-Available Frame-Level cases Edge Solution Edge Solution Solution Two servers 4 –100 servers Single server • Focus on minimizing the infrastructure footprint Top of Rack POD POD POD POD POD POD One & two server solution overhead POD POD POD Worker Worker Worker 2 cores/server Control Control Storage Storage Frame level solution Runs all functions POD POD POD POD POD POD 2 server master implementation Worker Worker Control 1 core overhead/worker node Control Control Storage • Storage Storage Storage Redundant design Integrated CEPH for one & two node solutions Fully resilient and Co-located CEPH on master nodes for small geographically distributable frame level deployments Dedicated CEPH storage nodes for larger configurations

  9. Platform Deployment • StarlingX installs on bare metal servers from an installation ISO. The ISO can be built using the build tools and instructions found in the StarlingX repos. ISOs are built daily and available from a public repository. • Docker images for kubernetes components are pulled from public registries or (optionally) pulled from a private registry. • Initial system configuration is driven with Ansible: Modeled specification of target deployment configuration Allows automation of deployments with zero touch provisioning • Kubernetes components are deployed with kubeadm.

  10. Platform Deployment Procedure 1. Install initial server from external PXE Boot Server or USB 2. Run Ansible playbook to configure server as the initial controller / kubernetes master node The playbook can be run locally or from a remote server Deployment specific configuration (e.g. network config) is found in a single bootstrap.yml 3. Install additional controller, storage and worker nodes from the controller node as follows: Power on server and PXE boot from a controller node -> controller discovers server (receives DHCP request) User selects “personality” (controller, worker, storage) -> controller installs software on server Controller runs inventory discovery on new server to find hardware and resources User configures host details (e.g. interfaces, CPUs, disks, memory assignment) User unlocks server and controller brings it into service 4. Apply any additional system configuration through configuration APIs Low touch deployment

  11. OpenStack Deployment • OpenStack is deployed as a containerized Kubernetes application OpenStack control plane running in pods OpenStack virtual machines running on host Leverages Kubernetes’ strengths to manage, scale and update the OpenStack services • Deployed using Helm (using OpenStack-Helm charts) and Armada (orchestrator for deploying Helm charts from OpenStack Airship). • StarlingX provides application APIs to install and configure the containerized OpenStack application Application tarball contains helm charts and armada manifest for StarlingX Automatic generation of helm configuration values based on system configuration User can easily customize helm configuration of OpenStack Services

  12. OpenStack Deployment Procedure 1. Apply labels to nodes which will host OpenStack control plane and compute pods 2. Configure local storage for nova on compute nodes 3. Import and apply the stx-openstack application 4. Configure OpenStack services through the usual OpenStack APIs Streamlined OpenStack deployment

  13. Day 2 Operations • System, Node and Service Configuration Changes, • System, Node and Service Maintenance: Administrative commands (e.g. LOCK Node), Fault Monitoring, Alarming and Recovery, Statistics Collection and Analysis, External Centralized Log Management. • Software Update and Upgrade Management / Orchestration • Backup & Restore.

  14. Future – Edge Device Management Support Kubernetes-enabled Devices to JOIN StarlingX Kubernetes Cluster Devices pre-loaded with Operating System & Kubernetes, StarlingX securely manages ‘ kubeadm join ... ’ of Device to StarlingX Kubernetes Cluster. Value: • Enables Management of Devices’ Containerized Workloads from StarlingX Kubernetes Master, IOT Devices • Enables Devices Apps to access any Services on StarlingX’s Kubernetes Cluster. Ceph-backed PVCs, Local Docker Registry, etc.

  15. Future – Device Management (DEMO)

  16. Future – Device Management (DEMO)

  17. What’s next? • We are actively working on our next release and will be planning the following release this week. Please feel free to join our PTG session, Thursday noon to Friday EOD ! • Additional StarlingX summit sessions: Precision Time Protocol (PTP) on StarlingX, Mon 3:50-4:30 Room Level 505/506 Edge Computing Group’s MVP Architecture - StarlingX making it real!, Tue 9:50-10:30 Room Level 505/506 Getting a new Open Source Project off the ground – the StarlingX story, Tue 9:00-9:40 Room Level 505/506 StarlingX for OpenStack Operators, Wed 9:00-9:40 Ballroom Level 4A StarlingX: Hardened Managed Kubernetes Platform for the Edge, Wed 10:50-11:40 Room Level 403/404 StarlingX - Project Onboarding, Wed 11:40-12:00 Room Level 406 StarlingX hands-on workshop, Wed 1:40-5:50 Ballroom Level 4E/F

  18. A FULLY FEATURED CLOUD FOR THE DISTRIBUTED EDGE T JOIN THE COMMUNITY MAILING LISTS: LISTS.STARLINGX.IO FREENODE IRC: #STARLINGX WEBSITE: WWW.STARLINGX.IO JOIN THE FOUNDATION MAILING LIST TO STAY UP TO DATE ON ALL NEW PROJECTS!

  19. Thank You!

More recommend