This document discusses CloudLabs' focus on rack scale reference platforms and integrated solutions. It provides an overview of CloudLabs' investments in rack solutions including CORD, OPNFV, OCP, and Intel RSA architectures. It also summarizes Stacki for baremetal provisioning, OpenStack-Ansible for OpenStack deployment, and CloudLabs' benchmarking framework for validating solutions from baremetal to rack scale.
2. 1 CONFIDENTIAL Restricted – share with permission only.
CloudLabs Helps Ecosystem Deliver Solutions
Integrated solution with SW,
HW across networking, storage
& compute offer differentiation
possibilities at many layers
CEC
HW
Services/SLAs Layer
SW
HW
SW
SW
HW
STORAGE
HW
Enterprise Application Layer
BI/Analytics
Operations
ERP/SCM
Infrastructure Layer
Telco and Cloud solutions
requires multiple decisions
across various platforms and
vendors developing specific
solution
CloudLabs goal is to provide
integrated solutions based on
partnerships across key
vendors
3. 2 CONFIDENTIAL Restricted – share with permission only.
CloudLabs focuses on Rack Scale Reference Platforms
EMS Services
JDM Hardware
System Integration
Firmware/BIOS
Platform software
Appliance
Applications
APPLIANCE READY NODE
Cloud Reference Architecture
Cloudlabs Focus
Node N
System Integration
CLOUD OS
Node 1
Rack Scale
Integration
Current Ciii
Customers
Ciii Cloud
Customers
Cloud-enabled Apps
& Workloads
Enterprise
Customers
Cloud-enabled Apps &
Workloads
APPLIANCE READY RACK
4. Rack Scale Solution Workflow
Architect
Ciii RSP Engineering flex
1
Integrate Test Manufacture
32 5
Optimize
4
Services
Support
6
FlexBench and FlexConfig
Storage
Compute
Switch
5. 4
CloudLabs Investment in Rack Solutions
CORD
Platform
OPNFV
based IaaS
Telco Infra
Project
platforms
OCP Based
Platform
Intel RSA
Architecture
Service Provider Driven Solutions
Services bring differentiation
Multi-vendor Spares Management Full rack integration
Repair / Returns Custom ServicesSupply chain ‘as a service’
6. Server Provisioning with Stacki
Open Source
Simplified Baremetal Provisioning
Mac address targeted PXE Booting
Customizable Local CentOS and Ubuntu Repositories
Hardware & Software RAID Support
NIC Bonding
Post-Install Configuration
http://www.stacki.com/
7. OpenStack(i) - Ansible
• Using Ansible to deploy OpenStack
• First released in April 2015 (Kilo)
• https://github.com/openstack/openstack-ansible
• OpenStack-Ansible deployment steps:
8. 7 CONFIDENTIAL Restricted – share with permission only.
Benchmarking Overview
Benchmarking Framework
Automated and Agent-Less
with a full-featured web
interface to launch tasks
from.
Baremetal to Rackscale
Node deployment including
server imaging and Cluster
OpenStack deployment,
and virtual machine
creation.
Multi-Level Validation
Validate and Benchmark at
all levels including node-
level components,
databases, containers, and
cloud.
Data and Log Analytics
Results, Logs, and Node
metadata provide
visualizations and raw data
for deeper investigations.
10. Stacki Host Tasks
• These tasks show utilizing the Stacki
Ansible Host Module to:
Remove host if it exists on in Stacki
Add a new host to Stacki
Wait for node to return from imaging
process
11. 10
Stacki Inventory Script
• JSON Formatted output of host information via
Stacki APIs
• Made to work for Ansible dynamic inventory to
be passed to ansible or ansible-playbook
• Uses yml formatted parameter file for required
arguments
# stacki.yml
---
stacki:
auth:
stacki_user: admin
stacki_password: abcdefghijklmnopqrstuvwxyz123456789
stacki_endpoint: http://192.168.1.10/stack
use_hostnames: false
We have a robust existing manufacturing automation platform, but as new server architectures have begun to arrive, we wanted a more agile, modern process that could also be used for R&D and developing reference solutions.
As we moved to the rack scale and began both software and hardware partnerships, the reference solution matrix began to grow so we needed a strong imaging solution and the ability to rapidly deploy software stacks from partners, automate the deployment of applications, and deliver requested performance data quickly.
We noticed that Configuration Management tools had greatly matured in the past 3 years, and we tried a number of them. They each had their strengths, and Hugh’s going to talk about why we chose Ansible and how we developed our test solution around it.
1. Multitrack enterprise cloud (Open Stack)
2. Multi vendor rack appliance (Cisco, Tintri, Open Stack)
3. Mirantis Open Stack – SW from M. – HW from flex and third party
4. Open NFV software stack for Telco - network virtualization
Cloud-In-Box
Openstack Based
Vmware CAN/EVO Rack
Hadoop Data Analytics
Openstack Sahara
Cloudera-Teradata
NFV IaaS
NFV Optimized Rack Scale
OCP Based Designs
Smart Rack Design
Compute/Network/Storage Sleds
Intel Rack Scale Reference Designs
These are the multiple areas where CloudLabs is currently focused on or looking into as a roadmap. Within each category, we have a partner we are working with to define solution.
Cloud in a Box solutions currently are based on our work done with Mirantis Openstack.
NFV related work is based on using SDN/NFV vendors such as Plumgrid, Contrail and also Open Daylight based controllers.
OCP based platforms are on the roadmap and we are looking at common unifying theme to base the architecture on. There have been multiple different views on OCP, however, most companies are looking at OCP as a base platform to start from. For instance Nokia Airframe has borrowed ideas from OCP for product form factor definition. Our familiarity and comfort with such standards provides us ability to engage in customer conversations in a well informed manner.
Intel RSA based Architecture is primarily a data center management framework which would be run on our Victoria/Queensland based racks.
To help us validate our hardware, we utilize an open-source provisioning tool called Stacki.
It allows us to quickly PXE boot the proper machines with the proper image, with RAID and NIC Bonding support.
It also utilizes local repositories which makes the process that much faster.
It also has the ability to run additional configuration after the initial OS install to further automate the process.
Red outline is for showing where stacki comes in to play