Topic Leader(s)

Topic Overview

60m Ildiko Vancsa  (incl. APAC Topic Leader)

Discussing multi- and hybrid cloud requirements and choices as it is driven by edge and other use cases.

The session is a continuation of the similar discussion at the recent PTG:

Recording of the PTG discussion:

Relevant RM sections:

Relevant RA sections:

Slides & Recording


Please indicate your session type in the blank space below and then remove this Info field.

  • Demo / Informational (non-interactive)
    • You may be asked to pre-record this session which will be made available on-demand.
  • Live Interactive Session

LFN Staff may elect to publish some videos to YouTube.  Please indicate here if you do not want your session to be published to YouTube.

Live Interactive Session

Recording: Multi-Hybrid Cloud.mp4


  • 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)
    • Single Plane of Glass: for seamless management of orchestration of workloads in a hybrid multi-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

      • ... 

  • Multi-cloud considerations
    • Operational Model
    • Deployment Model (it can facilitate on how the workloads are distributed and configured)
      • Controller suites for Network Services distributed across private and public clouds
        • Challenges: Security, QoS, lack of SLA, access to BSS/OSS systems, orchestration across the networks and hyperscalers.
    • Proposals for multi-cloud support (SDO related)


The topic is very broad, so what should we focus on?

  • Should focus on workloads and access, not the business models (PaaS, IaaS).
  • How can the Telecoms leverage the Hyperscaler resources?

Trends are that vendors are providing environments (Cisco for example) that are not compatible with multi-cloud services.  How can telecoms balance the need for control of the infrastructure and the lack of transparency into the hyperscaler architectures?

  • Need to rely on brokers and APIs (who controls and develops the APIs).  All the hyperscalers have extensive incompatible APIs.
  • Open API Forum has been wrestling with the willingness for stakeholders to contribute to OpenAPIs.
    • What is the common interest in open APIs?
      • Walter Kozlowskithinks that the hyperscalars are in fact interested in working with Telecom operators to define a common set of APIs.
      • GSMA has some work in this area.
        • Do the hyperscalers participate in GSMA?
  • Pankaj Goyalnotes that the hyperscalers are in a high growth phase of their business (marketshare acquisition mode).
    • How does 5G fit into this.
    • How do we define the interface with the hyperscalers?
      • Several use cases that need to be addressed – 5G, hosted controller suites, multi-cloud access.
      • Some companies have attempted to bridge  public and private cloud (VMWare, is an example) with mixed success.
      • Chapter 6 in RM covers interfaces with Hyperscalers.
        • Needs to better define the ownership and responsibilities.
      • ETSI documents cover the cloud interfaces, where IFA 40 is the stage 2 doc for interfaces and requirements for container solutions. Stage 3 will be profiling (maps stage 2 to the interface in de-facto standards), not an API specification. The profiling for Kubernetes is started in SOL018 document.  Question about ETSI's work on container architecture.  ETSI is acknowledging the need to cover container and Kubernetes infrastructure, need to have multiple standards.
    • How do we define the management interface to the infrastructure in a multi-cloud environment?   RM Table 6-1

Focus first on RM and see if we need to create an RA3 (maybe best practices) for how to use the Hyperscalars for Telecom workloads.

Action Items


1 Comment

    • Data Center (DC) Cloud is about centralisation, commoditised infrastructure in data centers
    • Hyperscalars (HSP) are mainly Cloud about a few mega-data centers
      • Beginning to
    • Edge is about decentralisation and customisation including infrastructure
      •   Edge cloud is about ability to provide HA and other usability capabilities at the Edge
    • Remote/Intermediate DC lie between DC and Edge –  providing a sort of continuum

    We need to capture that the cloud environment is a continuum.