Horizontal interactions Clause Samples

Horizontal interactions. The horizontal (east-west) interaction enables the creation of a fluid domain among peers, which can share their resources and services, or part of them, based upon a set of policies (e.g., enable sharing from node X but not from node Y). Horizontal interactions are carried out according to a peer-to-peer paradigm, hence without the need for any centralized entity that controls and supervises the entire process. Applications started on a FLUIDOS node can leverage any resource, either local or remote, available in the new virtual space. The FLUIDOS orchestrator is responsible for determining the best location for each component based on (i) the features requested through the intent-based API (e.g., computing power, maximum latency between components and toward end users, resiliency properties, number and location of replicas, reduction of energy and costs or carbon, etc.) and (ii) the additional policies set for the creation of the virtual space and/or the offloading of any component (e.g., no offloading on un-trusted domains for critical components). The establishment of a peering relationship is a multi-step process, which mainly involves the following phases: • Discovery, allowing to discover the existence of other peering candidates. • Negotiation, enabling FLUIDOS nodes to issue requests for resources and/or services to other nodes, which in turn advertise their available capabilities. • Reservation and contract signing, formalizing the acceptance of an offer from a FLUIDOS node, and possibly agreeing on compensations. • Peering, establishing the virtual fabrics required to enable seamless • Usage, leveraging the resources and services acquired by other FLUIDOS nodes to satisfy service requests. • Depeering, tearing down the previously established computing continuum abstractions, which are no longer necessary.