Overall Architecture
- Fully automated deployment on different platforms: AWS, GCP
- Deploy kubernetes cluster properly configured and tuned for NFV/MEC workloads
- Enablement of real time workloads
- Possibility of deploying apps on virtual machines and containers in parallel
The blueprint is based on site/profile/base pattern:
- base - it will contain a set of Kubernetes manifests that define the common settings of the Kubernetes cluster to be deployed, and the common workloads to be applied on top of it
- profile - specialization of the cluster depending on profiles (libvirt, AWS and baremetal). It will contain specific configs for each platform, and specific workloads to be applied on top of it
- site - individual definition of a site, based on a chosen profile. It will contain specific configurations for the site (name, domain, network/servers settings, etc...)
Platform Architecture
This blueprint is expected to run on multiple environments (libvirt, AWS and baremetal).
Deployments to AWS
| nodes | instance type |
|---|---|
| 1x bootstrap (temporary) | EC2: m4.xlarge, EBS: 120GB GP2 |
| 3x masters | EC2: m4.xlarge, EBS: 120GB GP2 |
| 3x workers | EC2: m4.large, EBS: 120GB GP2 |
Deployments to Bare Metal
| nodes | requirements |
|---|---|
| 1x provisioning host (temporary) | 12 cores, 16GB RAM, 200GB disk free, 3 NICs (1 internet connectivity, 1 provisioning+storage, 1 cluster) |
| 3x masters | 12 cores, 16GB RAM, 200GB disk free, 2 NICs (1 provisioning+storage, 1 cluster) |
| 3x workers | 12 cores, min. 16GB RAM, 200GB disk free, 2 SR/IOV-capable NICs (1 provisioning+storage, 1 cluster) |
The blueprint validation lab uses 7 SuperMicro SuperServer 1028R-WTR (Black) with the following specs:
| Units | Type | Description |
|---|---|---|
| 2 | CPU | BDW-EP 12C E5-2650V4 2.2G 30M 9.6GT QPI |
| 8 | Mem | 16GB DDR4-2400 2RX8 ECC RDIMM |
| 1 | SSD | Samsung PM863, 480GB, SATA 6Gb/s, VNAND, 2.5" SSD - MZ7LM480HCHP-00005 |
| 4 | HDD | Seagate 2.5" 2TB SATA 6Gb/s 7.2K RPM 128M, 512N (Avenger) |
| 2 | NIC | Standard LP 40GbE with 2 QSFP ports, Intel XL710 |
Networking for the machines has to be set up as follows:
Deployments to vBaremetal (KVM)
| nodes | requirements |
|---|---|
| 1x bootstrap (temporary) | 2 vCPUs, 2GB RAM, 2GB (sparse) |
| 3x masters | 4 vCPUs, 8GB RAM, 2GB (sparse) |
| 3x workers | 2 vCPUs, 4GB RAM, 2GB (sparse) |
Software Platform Architecture
deploy on AWS, baremetal, Google Cloud, KVM (libvirt)
Release 4 components:
- CoreOS for all nodes (RT workers too): Red Hat Enterprise Linux CoreOS release 4.6
- CRI-O: xxxxxxx
- Kubernetes (OKD) version: openshift-install v4.6.6, built from commit db0f93089a64c5fd459d226fc224a2584e8cfb7e
release image quay.io/openshift-release-dev/ocp-release@sha256:c7e8f18e8116356701bd23ae3a23fb9892dd5ea66c8300662ef30563d7104f39 - Multus, Cluster/Machine operator, Prometheus: versions provided in 4.6.6 Openshift release
- Ceph: 14.2.8 (2d095e947a02261ce61424021bb43bd3022d35cb) nautilus (stable)
- Kubevirt: 0.27.2
APIs
No specific APIs involved on this blueprint. It relies on Kubernetes cluster so all the APIs used are Kubernetes ones.
Hardware and Software Management
Licensing
Apache license