The REAR (REsource Advertisement and Reservation) protocol enables different actors such as cloud providers and customers to advertise, reserve (and then consume) resources (e.g., virtual machines and their characteristics in terms of CPU, RAM; a Kubernetes cluster, etc.), and services (e.g., a database as a service). A dedicated onthology supports also capabilities (e.g., the availability of GPU hardware in a Kubernetes clusters), in order to better characterize offered resource/services, while being easily extensible and future-proof.

REAR is being defined with a fully open approach, which facilitates the participation of actors that are outside the FLUIDOS community. Current specifications are available at https://github.com/topix-hackademy/Rear/.