One of the main responsabilities of i2CAT in GEYSERS is leading the WP3: GEYSERS Logical Infrastructure Composition Layer (LICL), which has been busy the last two months working with the LICL development, to deliver a first prototype by the end of the year.
What is the LICL?
The LICL is the layer in the GEYSERS architecture responsible of providing virtualized resources to the upper layers. It manages the physical infrastructure, abstracts it and creates slices of independent and isolated virtual infrastructures for the Virtual Infratructure Operator (VIO), one of the GEYSERS-defined roles for the Future Internet.
The LICL is divided in two layers, each of them provides the necessary functions to the Physical Infrastructure Provider (PIP) and the Virtual Infrastructure Provider (VIP). The PIP is the role in GEYSERS architecture that owns the physical infrastructure, responsible of performing the abstraction and partitioning of the physical substrate. On the other hand, the VIP handles and composes the virtual resources provided to produce the virtual infrastructures, enabling its operation for the VIOs.
Previous to the pure development and implementation, several discussions have been mantained between WP3 partners to decide on which will be the development platform, either to use SOAP or REST for the interaction with other components on the architecture, or what should be the license under which publish the LICL code. For the first two issues, we have come to an agreement, deciding to develope the LICL over FUSE and use REST for the communication with the other components from GEYSERS architecture. However we are still engaged on the license discussion, and hope to reach an agreement soon.
Regarding implementation, so far the lower LICL is capable of abstracting new resources available on the physical substrate using both the information provided by the LICL administrator and the information retrieved by the physical resource itself; and later on, publish aggregated information to the upper LICL. This aggregated information consists on which types of resources a PIP can provide virtualized, and some additional information such as how granular a partition of this resource can be.
And right now we are busy implementing the VI planning and instantiation. The VI planning is making a reservation of a portion of some concrete physical resources so that a VI can be created over them. The instantiation makes the reservation effective, by creating virtual resources as isolated partitions of the physical ones and giving the operator the rights to operate over them.
Visit the GEYSERS both at the FIA event to discover how these concepts work 🙂