...
- Setting the scope for the discussion
- IaaS? PaaS?
- Workloads and workload characteristics?
- Definitions - Are these the right definitions?
- Cloud
- Multi-cloud environment: clouds from multiple different public cloud providers
- Hybrid-cloud environment: a mix of private and public clouds
- Hybrid-multi-cloud: private and multiple public cloud providers
- Edge - How deeply do we want to go into the edge space? What do we want to/ do not want to define?
- Edge: EUD, IoT devices
- From limited to significant compute capacity, storage and networking bandwidth
- Edge Site: Cloud network periphery or GW
- Every place where Edge devices connect to the cloud network
- May consist of limited to significant compute capacity, storage and networking bandwidth nodes for aggregating, processing and filtering data at the edge, including data from dumb devices
- Zero Ops
- Core Site: in a DC, other large sites (IDC, Co-Lo, etc.)
- Edge Cloud: Hybrid multi cloud
- From single node to small cluster of nodes (HA, resiliency, self-healing, ...)
- Technology: micro k8s, microstack (single package of all key OSTK services (Keystone, Glance, Nova, Neutron (OVN), Cinder, Horizon, Clustering, monitoring)
- Edge: EUD, IoT devices
- Single Plane of Glass: for seamless management of orchestration of workloads in a hybrid multi-cloud
- Cloud
- If discussing workloads
Are these the workload characteristics that should be specified when requesting resources?
Can schedulers take these characteristics into account when identifying the site, node, .. to host the workload?
Workload Characteristics:
Resource sizing
Storage IOPS
Network Latency
HW/SW Accelerators
Special HW or SW
Affinity
...