Table

of Contents

Cloud Service Catalogue

Introduction 1.1

Infrastructure Services [cis]

Compute: Processor 2.1

Compute: M emory 2.2

Compute: Instances 2.3

Compute: M etadata 2.4
Compute: Images 2.5

Storage: Block 2.6

Storage: Object 2.7

Network: Ports 2.8

Network: Subnets 2.9
Network: Routers 2.10

Network: Floating IPs 2.11

Network: Security Groups 2.12
Network: Virtual Private Cloud 2.13

Network: Backbone-VPN 2.14

Partitioning: M ultisite 2.15
Partitioning: Regions 2.16

Partitioning: Availability Zones 2.17

Platform Services [cps]

NTP 3.1

DNS 3.2
SM TP 3.3

Load Balancing 3.4

Backup 3.5
BGP 3.6

Tenant GW 3.7

Containers 3.8
CI-Developer Services 3.9

Workflow-Orchestration Services 3.10

Security Services [css]

1
Web Application Firewalls 4.1

Secure Connect 4.2

Integrated Identity and Access M anagement across IaaS services 4.3
Key-Certificate M anagement Services 4.4

Compliance Reporting 4.5

Directory Services 4.6

Framework Services [cfs]

Documentation 5.1
M anagement API access 5.2

M anagement Dashboard access 5.3

M anagement Console access 5.4

Bootstrapping APIs-Portal 5.5

Delegated administration 5.6

M etrics 5.7
M onitoring 5.8

Billing 5.9
Tags 5.10
Autoscaling Groups 5.11

Onboarding Services 5.12

2
Introduction

Version Pan-Net-CS C-2018-12

Categories

[cis]: Cloud Infrastructure Services

[cps]: Cloud Platform Services
[css]: Cloud Security Services
[cfs]: Cloud Framework Services

Abbreviations

IC-Li: Infrastucture Cloud, Lithium release

IC-Be: Infrastucture Cloud, Beryllium release

Status Codes

status code

available +

ongoing ~

planned /

not planned -

3
Compute: Processor

cis-comp-proc

IC- IC-
item metric description
Li Be

cis-comp-proc- a shared vCPU which is a core of an Intel Xeon E5-2660 v4 Processor

count + -
cpu-s0 (Lithium design)

cis-comp-proc- a dedicated vCPU which is a core of an Intel Xeon E5-2660 v4 Processor

count + -
cpu-d0 (Lithium design)

cis-comp-proc- a shared vCPU which is a core of an Intel Xeon Gold 6152 Processor
count - +
cpu-s1 (Beryllium design)

cis-comp-proc- a dedicated vCPU which is a core of an Intel Xeon Gold 6152 Processor
count - +
cpu-d1 (Beryllium design)

explanation

The allocation of CPU resources is based on KVM/QEMU and managed by libvirt .

Terminology:

lscpu socket = kvm cell ~= (numa) node

processor = cpu = #of-sockets x #of-cores x #num-of-threads

siblings: two cpus that are phyisically the same but show up as two as a result of hyperthreading

Lithium design

2 socket: NUM A0 and NUM A1

14 cores per socket
HT enabled
cpu: 2 x 14 x 2 = 56
NUM A0: cpu 0-13, 28-41
NUM A1: cpu 14-27, 42-55

Beryllium design

2 socket: NUM A0 and NUM A1

22 cores per socket
HT enabled
cpu: 2 x 22 x 2 = 88
NUM A0: cpu 0-21, 44-65
NUM A1: cpu 22-43, 66-87

CPU overcommitment

kvm is doing it by default

overcommitment means that if you sum up the assigned vcpus for the VM s it will be a higher number than the physical cpus
thus, in Li-type compute w/o overcommitment you cannot have more than 56 vcpus; similarly, in Be the limit is 88
with 1:5 overcommitment you can have
Lithium: 5x56=280 vcpus
Beryllium: 5x88=440 vcpus
with 1:16 overcommitment you can have 16x56=896 vcpus
Lithium: 16x56=896 vcpus
Beryllium: 16x88=1408 vcpus

cpu allocation scenarios

auto allocation

very efficient; good in a real cloud

you can decide on the ratio; it is not hardcoded into libvirt at all: it just depends on the vcpu:cpu ratio
dedication (pinning)

4
Compute: Processor

you can do it if you manually map vcpu:cpu with the cputune option
can be used for nvfi workload; not really cloudy

cis-comp-proc-cpu-s0 Shared vCPU in Lithium. billing: based on the number of shared vpcus allocated for the tenant.

cis-comp-proc-cpu-d0 Dedicated vCPU in Lithium. billing: based on the number of dedicated vpcus allocated for the tenant.

cis-comp-proc-cpu-s1 Shared vCPU in Beryllium. billing: based on the number of shared vpcus allocated for the tenant.

cis-comp-proc-cpu-d1 Dedicated vCPU in Beryllium. billing: based on the number of dedicated vpcus allocated for the tenant.

future plans

We might offer GPU resources if requested.

5
Compute: M emory

cis-comp-mem

item metric description IC-Li IC-Be

cis-comp-mem-s0 GiB size of shared RAM assigned to a tenant + +

cis-comp-mem-d0 GiB size of dedicated RAM assigned to a tenant + +

explanation

cis-comp-mem-s0 Shared memory can be assigned to another tenant if not used. billing: based on the amount of shared memory

assigned to a tenant/project.

cis-comp-mem-d0 Dedicated memory cannot be assigned to another tenant. billing: based on the amount of dedicated memory assigned

to a tenant/project.

future plans

6
Compute: Instances

cis-comp-inst

IC- IC-
item metric description
Li Be

cis-comp-inst- standard instance type 00: shared vCPU=1 RAM =2GB

count + +
std-00 ROOTDISK=1GB

cis-comp-inst- standard instance type 01: shared vCPU=1 RAM =4GB

count + +
std-01 ROOTDISK=10GB

cis-comp-inst- standard instance type 02: shared vCPU=2 RAM =8GB

count + +
std-02 ROOTDISK=20GB

cis-comp-inst- standard instance type 03: shared vCPU=4 RAM =16GB

count + +
std-03 ROOTDISK=50GB

cis-comp-inst- accelerated instance type 00: dedicated vCPU=4 RAM =16GB

count + +
acc-00 ROOTDISK=50GB

cis-comp-inst- accelerated instance type 01: dedicated vCPU=8 RAM =32GB

count + +
acc-01 ROOTDISK=50GB

explanation

cis-comp-inst-std Standard instances: KVM /QEM U virtual machines with no acceleration. Different sizes. billing: instances are not

counted directly; we count the primitives they are made of

cis-comp-inst-acc Accelerated instances: KVM /QEM U virtual machines with acceleration technology. billing: instances are not

counted directly; we count the primitives they are made of

Lithium design: DPDK

Beryllium design: SmartNICS (DPDK compatible)

future plans

Standard instance-type/flavour definitions

Work Optimized Instances
IO Optimized
Compute Optimized
M emory Optimized
Dense-storage instances
Distributed computing/warehousing - hadoop, etcd, etc
Specialized
GPU, SR-IOV
Bare M etal/Collocated Instances - VPC/IAM integrated

reference: https://aws.amazon.com/ec2/instance-types/

7
Compute: M etadata

cis-comp-meta

item metric description IC-Li IC-Be

cis-comp-meta-items count number of metadata items + +

cis-comp-meta-injfiles count number of injected files + +

cis-comp-meta-injfilesize bytes size of injected content + +

explanation

cis-comp-meta-items Number of metadata items allowed per instance. billing: free if below the default limit

cis-comp-meta-injfiles Number of injected files allowed per project. billing: free if below the default limit

cis-comp-meta-injfilesize Number of content bytes allowed per injected file. billing: free if below the default limit

future plans

8
Compute: Images

cis-comp-img

item metric description IC-Li IC-Be

cis-comp-img-priv GiB total size of images uploaded by the tenant + +

cis-comp-img-pub GiB total size of public images uploaded by the operator + +

explanation

cis-comp-img-priv Tenants provide their custom images. billing: based on the size of the image

cis-comp-img-pub We don't provide custom images as of today. billing: public images are free

future plans

Standard offerings
Distribution images (ubuntu, centos, debian, etc)
Application/PaaS offerings
Application images (postgres, nginx, , etc)
Container optimized images
e.g. Ubuntu Server + SQL Server 2017
Windows AM Is
Up-2-date AM Is - autogenerated
AM I distribution across regions

e.g. https://aws.amazon.com/marketplace

9
Storage: Block

cis-stor-block

IC- IC-
item metric description
Li Be

cis-stor-block-
GiB size of the shared volume based on CEPH technology, full SSD + -
s0

cis-stor-block-
GiB size of the shared volume based on CEPH technology, SSD/HDD hybrid + -
s1

cis-stor-block-
GiB size of the shared volume based on CEPH technology, SSD/SATA hybrid + -
s2

cis-stor-block- size of the shared volume based on CEPH technology, NVM e SSD/SATA
GiB - ~
s3 hybrid

cis-stor-block- size of the dedicated volume based on DATERA technology, NVM e

GiB / ~
d0 SSD/SATA hybrid

explanation

measurement method

target: RAW numbers w/o the virtualization overhead

spotlight:
for small random IO, we can reach 8000 IOPS/sec with 30M B/s write speed
for big sequential IO, we can reach 2200 IOPS/sec with 550M B/s write speed
these numbers belong to a single compute node
rbd bench-write baseline performance measurement statistics
define pools on sas/sata/ssd disks
measure performance from a compute node with rbd bench-write utility
run two tests 4K blocksize 1GB data random workload; 256K blocksize 4GB data sequential workload
rbd -n client.nova-compute-int-std bench-write --io-size 4K --io-total 1G --io-pattern rand
rbd -n client.nova-compute-int-std bench-write --io-size 256K --io-total 4G --io-pattern seq
average performance for a single ceph client

BDC

item 4K rand IOPS /sec 4K rand Mbytes/sec 256K seq IOPS /sec 256K seq Mbytes/sec

cis-stor-block-s0 8300 30 2200 560

cis-stor-block-s1 12500 50 2200 560

cis-stor-block-s2 8600 35 2200 550

cis-stor-block-s3 - - - -

cis-stor-block-d0 - - - -

FDC

item 4K rand IOPS /sec 4K rand Mbytes/sec 256K seq IOPS /sec 256K seq Mbytes/sec

cis-stor-block-s0 - - - -

cis-stor-block-s1 9100 35 2300 580

cis-stor-block-s2 - - - -

cis-stor-block-s3 - - - -

cis-stor-block-d0 - - - -

future plans

10
Storage: Block

offering the cis-stor-block-d0 type in Q1/2019

providing numbers based from within a VM measurement method

11
Storage: Object

cis-stor-object

IC- IC-
item metric description
Li Be

cis-stor- size of the shared object storage based on rados-gw and CEPH technology,
GiB + +
object-s0 S3/SWIFT compatible API

cis-stor- size of the shared object storage based on SWIFT technology, native
GiB ~ ~
object-s1 implementation, SWIFT API only

explanation

The Object Storage can be implemented in different ways.

cis-stor-object-s0 billing: based on the size of the objects used This is the default implementation, based on rados-gw and CEPH

technology. It provides S3 and SWIFT APIs. Unfortunately, the SWIFT implementaion is not complete: e.g. Quota is not implemented.

cis-stor-object-s1 billing: based on the size of the objects used Native SWIFT implementation.

future plans

12
Network: Ports

cis-net-port

item metric description IC-Li IC-Be

cis-net-port-std count number of standard logical ports used by the tenant + +

cis-net-port-acc count number of accelerated logical ports used by the tenant + +

explanation

Ports are basic elements of Openstack: you can attach one or more ports to an instance.

cis-net-port-std Standard port: no acceleration. billing: based on the number of ports assigned to the tenant.

cis-net-port-acc Accelerated port: with acceleration technology. billing: based on the number of ports assigned to the tenant.

Lithium design: DPDK

Beryllium design: SmartNICS (DPDK compatible)

future plans

13
Network: Subnets

cis-net-subnet

item metric description IC-Li IC-Be

cis-net-subnet-std count number of standard subnets used by the tenant + +

explanation

Subnets are basic elements of Openstack. A subnet is a block of IP addresses and associated configuration state. Subnets are used to
allocate IP addresses when new ports are created on a network.

cis-net-subnet-std Standard subnet. billing: based on the number of subnets used by the tenant.

future plans

14
Network: Routers

cis-net-router

item metric description IC-Li IC-Be

cis-net-router-std count number of standard logical routers used by the tenant + +

explanation

Routers are basic elements of Openstack; you can connect your networks with routers. You can also assign FIP (Floating IP) to your
router thus connect your networks to other tenants or provide external connectivity.

cis-net-router-std Standard router. Typically implemented as ip namespace and runs on the Compute or Network nodes. billing:

based on the number of routers used by the tenant.

future plans

15
Network: Floating IPs

cis-net-fip

item metric description IC-Li IC-Be

cis-net-fip-internet count number of internet floating IPs used by the tenant + +

cis-net-fip-dth count number of DT harmonized floating IPs used by the tenant + +

cis-net-fip-pnh count number of Pan-Net harmonized floating IPs used by the tenant + +

explanation

Floating is the harmonized or routeable resource type in Openstack. This is used

to access tenant space from the outside world

to access the external world from tenant space
to publish a service from tenant space
for tenant-tenant communication

cis-net-fip-internet Floating IP which is routable on the internet. billing: free or based on the size of the allocated subnet

cis-net-fip-dth Floating IP which is routable inside DT. billing: free or based on the size of the allocated subnet

cis-net-fip-pnh Floating IP which is routable inside Pan-Net. billing: free

future plans

16
Network: Security Groups

cis-net-secgroup

item metric description IC-Li IC-Be

cis-net-secgroup-item count number of security groups used by the tenant + +

cis-net-secgroup-rule count number of security group rules used by the tenant + +

explanation

Security Groups provide hypervisor level level protection for the tenants. The reference implementation uses iptables .

cis-net-secgroup-item The number of security groups used by the tenant. billing: free if below the default limit

cis-net-secgroup-rule The number of security group rules used by the tenant. billing: free if below the default limit

future plans

17
Network: Virtual Private Cloud

cis-net-vpc

item metric description IC-Li IC-Be

cis-net-vpc-std binary definition is under discussion - -

explanation

We have just a whishlist for this service:

Public, Private Subnets atop Virtual Networks

L3 routing between subnets
Elastic Network Interfaces (for VPC private and public addresses)
Elastic IP Addresses (Requires IPAM )
Network Access Control Lists
Routing Tables
Internet Gateway (igw)
Virtual Private Gateway (vpg)
VPN Gateway
Elastic IPs
DHCP Options Sets
Security Groups
VPC Flow Logging
IPv4 & IPv6
Hardware/Software VPNaaS for Hybrid Cloud through VPG
VPC PrivateLink (secure network to platform services - PCI/DSS/FIPS)
VPC Peering

18
Network: Backbone-VPN

cis-net-vpn

item metric description IC-Li IC-Be

cis-net-vpn-std count number of standard VPNs on the Pan-Net Backbone + +

explanation

Tha Pan-Net Backbone can provide any number of private VPNs.

cis-net-vpn-std Standard VPN. billing: based on the number of configured private VPNs assigned to the tenant.

future plans

19
Partitioning: M ultisite

cis-part-multisite

item metric description IC-Li IC-Be

cis-part-multisite binary use of the Pan-Net M ultisite Package + +

explanation

the Pan-Net M ultisite Package is the combination of different technologies:

Pan-Net backbone connectivity

VPN over the backbone
IP anycast
Global health check
Object storage replication

cis-part-multisite Standard offering. billing: free

future plans

20
Partitioning: Regions

cis-part-region

item metric description IC-Li IC-Be

cis-part-region count number of separate cloud environments used by the tenant + +

explanation

openstack definition:

A discrete OpenStack environment with dedicated API endpoints that typically shares only the Identity (keystone) with other
regions.

Our implementation of regions are more discrete: we have sepratate keystone per environment.

cis-part-region Standard offering. billing: free

future plans

21
Partitioning: Availability Zones

cis-part-az

item metric description IC-Li IC-Be

cis-part-az-li count number of availability zones per cloud environment + -

cis-part-az-be count number of availability zones per cloud environment + +

explanation

Lithium design

cis-part-az-li billing: free

Failure domain representation: host aggregates + flavors

AZ is used for "security placement zone" representation

we define a separate flavor per rack_group
application onboarding uses the different flavors to represent failure domains

Hardware feature representation: host aggregates + flavors

standard (non-dpdk)
dpdk
Security Placement Zone representation: availability zones

AZ: EXT, INT, M GM T, nova (default)

17.1 Beryllium design

cis-part-az-be billing: free

Failure domain representation: host aggregates + availability zones

we create three host aggregates: rack_group1, rack_group2, rack_group3

compute resources will be distributed evenly accross racks
racks will be assigned to the rack_groups evenly
we create three availability zones: az1, az2, az3
az1, az2, az3 represents rack_group1, rack_group2, rack_group3, respectively

22
Partitioning: Availability Zones

we implement the Lithium design also for backward compatibility

Hardware feature representation: host aggregates + flavors

standard (non-dpdk)
accelerated (implemented with smartnics, dpdk-compatible)
Security Placement Zone representation: host aggregates + flavors

availability zones is not used as security placement zone representation

future plans

23
NTP

cps-ntp

item metric description IC-Li IC-Be

cps-ntp-stratum1 binary startum-1 time server - -

cps-ntp-stratum2 binary startum-2 time server + +

cps-ntp-stratum3 binary startum-3 time server + +

explanation

future plans

24
DNS

cps-dns

item metric description IC-Li IC-Be

cps-dns-designate binary use of the designate service + ~

explanation

future plans

25
SM TP

cps-smtp

item metric description IC-Li IC-Be

cps-smtp-relay binary use of the smtp relay - /

explanation

future plans

26
Load Balancing

cps-lb

item metric description IC-Li IC-Be

cps-lb-l4-ecmp count number of ECM P based L4 load balancer instances used by the tenant + +

cps-lb-l4-lbaas4 count number of LBaaS4 based L4 load balancer instances used by the tenant + +

cps-lb-l7-lbaas7 count number of LBaaS7 based L7 load balancer instances used by the tenant ~ ~

cps-lb-l7-octavia count number of Octavia based L7 load balancer instances used by the tenant - -

explanation

future plans

27
Backup

cps-backup

item metric description IC-Li IC-Be

cps-backup-volume GiB amount of backed up data - /

cps-backup-object GiB amount of backed up data - -

explanation

future plans

28
BGP

cps-bgp

item metric description IC-Li IC-Be

cps-bgp binary BGP as a service used by the tenant + +

explanation

future plans

29
Tenant GW

cps-tgw

item metric description IC-Li IC-Be

cps-tgw binary Tenant GW as a service used by the tenant ~ ~

explanation

future plans

30
Containers

cps-caas

item metric description IC-Li IC-Be

cps-caas binary Container as a service used by the tenant ~ ~

explanation

future plans

31
CI-Developer Services

cps-cicd

item metric description IC-Li IC-Be

cps-cicd binary CI/CD as a service used by the tenant + +

explanation

future plans

32
Workflow-Orchestration Services

cps-wflow

item metric description IC-Li IC-Be

cps-wflow binary Workflow as a service used by the tenant ~ ~

explanation

future plans

33
Web Application Firewalls

css-waf

item metric description IC-Li IC-Be

css-waf count number of WAF instances used by the tenant + ~

explanation

future plans

34
Secure Connect

css-seccon

item metric description IC-Li IC-Be

css-seccon count L3 Secure Access to the Provider services + ~

explanation

css-seccon L3 Secure Access to the Provider services

future plans

35
Integrated Identity and Access M anagement across IaaS services

css-iam

item metric description IC-Li IC-Be

css-iam count Identity and Access M anagement for the tenants - -

explanation

css-iam Integrated Identity and Access M anagement across IaaS services.

future plans

36
Key-Certificate M anagement Services

css-cert

item metric description IC-Li IC-Be

css-cert count Key/Certificate M anagement Services for the tenants ~ ~

explanation

css-cert Key/Certificate M anagement Services

future plans

37
Compliance Reporting

css-compliance

item metric description IC-Li IC-Be

css-compliance count Compliance Reporting for the tenants ~ ~

explanation

css-compliance Compliance Reporting

future plans

38
Directory Services

css-dir

item metric description IC-Li IC-Be

css-dir count Directory Services for the tenants - -

explanation

css-dir Directory Services

future plans

39
Documentation

cfs-doc

item metric description IC-Li IC-Be

cfs-doc-hld binary High Level Design + +

cfs-doc-lld binary Low Level Design + +

cfs-doc-adminguide binary Administrators' Guide, including Operation - ~

cfs-doc-userguide binary Users' Guide - ~

explanation

Documentation must satisfy the following requirements:

Structured, easy to access

Indexed, up to date
Publicly accessible, indexable by search engines

future plans

40
M anagement API access

cfs-api

item metric description IC-Li IC-Be

cfs-api-openstack-int binary internal access to the Openstack API + +

cfs-api-openstack-ext binary external (internet) access to the Openstack API - /

cfs-api-contrail-int binary internal access to the Contrail API + +

cfs-api-contrail-ext binary external (internet) access to the Contrail API - -

cfs-api-objstor-int binary internal access to the Object Storage + +

cfs-api-objstor-ext binary external (internet) access to the Object Storage - /

explanation

Lithium API access cfs-api-openstack-int cfs-api-contrail-int

APIs are binded to non-routable addresses

APIs are routed on BOR side
not designed for tenant access
publishing via OAM FW (not ideal)

cfs-api-objstor-int

not designed for tenant access

workaround: LLS contrail feauture

cfs-api-openstack-ext cfs-api-contrail-ext cfs-api-objstor-ext

not planned to implement it

Beryllium API access cfs-api-openstack-int cfs-api-contrail-int

APIs are binded to routable addresses

APIs are routed on TOR side
designed for tenant access
publishing via tenant space API proxy

cfs-api-objstor-int

designed for tenant access

publishing via tenant space rados-gw

cfs-api-openstack-ext

publishing via WAF + API proxy

cfs-api-contrail-ext

not planned to implement it

cfs-api-objstor-ext

publishing via WAF + rados-gw

future plans

41
M anagement Dashboard access

cfs-dashboard

item metric description IC-Li IC-Be

cfs-dashboard-int binary internal access to the Openstack Dashboard + +

cfs-dashboard-ext binary external access to the Openstack Dashboard - /

explanation

cfs-dashboard-int The Openstack Dashboard (Horizon) is "just another client" that can access the APIs.

cfs-dashboard-ext Publishing the Dashboard on the internet will be implemented with WAF protection.

future plans

42
M anagement Console access

cfs-console

item metric description IC-Li IC-Be

cfs-console-int binary internal access to the console of the instances + +

cfs-console-ext binary external access to the console of the instances - ~

explanation

cfs-console-int Console access is a bit sensitive since it requires client-compute (hypervisor) communication. It will be implemented

via the API proxy.

cfs-console-ext Publishing the Console access on the internet will be implemented via WAF + API proxy.

future plans

43
Bootstrapping APIs-Portal

cfs-portal

item metric description IC-Li IC-Be

cfs-portal-selfreg binary Self Registration on the Portal - /

cfs-portal-tenantadm binary Tenant related Self-Administration - /

explanation

cfs-portal-selfreg

Possible self registration on the Portal

cfs-portal-tenantadm

Tenant Creation
User/Project Creation
Quota Calculations/Allocations
Custom Flavour Definitions
M anual/Static IP Allocation to tenants
Contrail Configuration (Route Targets, etc)
Backup/Restore of data/configuration
Storage configuration
PaaS configuration requests

future plans

44
Delegated administration

cfs-delegation

item metric description IC-Li IC-Be

cfs-delegation binary internal access to the console of the instances - -

explanation

cfs-delegation Delegated tenant administrator will be possible with keystone V3. Our current design is the following:

Lithium: based on M itaka, default is keystone V2

Beryllium: based on Ocata, default is keystone V2
Boron: based on Queens, default is keystone V3

future plans

45
M etrics

cfs-metrics

item metric description IC-Li IC-Be

cfs-metrics binary metrics of tenant's resource consumption / /

explanation

future plans

46
M onitoring

cfs-monitoring

item metric description IC-Li IC-Be

cfs-monitoring binary monitroing of tenant's resources / /

explanation

future plans

47
Billing

cfs-billing

item metric description IC-Li IC-Be

cfs-billing binary billing of tenant's resource consumption / /

explanation

future plans

48
Tags

cfs-tags

item metric description IC-Li IC-Be

cfs-tags binary tags can be used to logically group objects for access - -

explanation

future plans

49
Autoscaling Groups

cfs-autoscale

item metric description IC-Li IC-Be

cfs-autoscale binary automatic scale out service - -

explanation

cfs-autoscale Auto Scaling monitors your applications and automatically adjusts capacity to maintain steady, predictable

performance at the lowest possible cost.

future plans

50
Onboarding Services

cfs-onboarding

item metric description IC-Li IC-Be

cfs-onboarding binary automatic scale out service + +

explanation

future plans

51