This section shows the reservation process for the different types of resources on the testbed. Currently, there are two aggregate managers on the testbed: VTAM and OFAM. VTAM is used to control and manage the virtualization servers while OFAM is used for network resources.
Both the aggregate managers at UNIVBRIS OFELIA speak Geni API v2 and in the near future, the aggregate managers will be compatible with Geni API v3. There are several Fed4FIRE-supported tools: OMNI (patched), SFI, jFed and Fed4FIRE portal, which can be used to list and reserve resources on the testbed. The table below Table 1 shows the compatibility/ability of these reservation tools with respect with the aggregate managers at UNIVBRIS OFELIA.
Table 1: Status of the compatibility/ability of different reservation tools with UNIVBRIS OFELIA
| Reservation Tool | Tested on UNIVBRIS | Available | Type |
| OMNI | Fully-tested & working | Documentation:http://trac.gpolab.bbn.com/gcf/wiki/Omni | CLI |
| SFI | Fully-tested & working | http://trac.myslice.info/wiki/InstallSfa | CLI |
| jFed (not fully integrated) | Partially tested | http://jfed.iminds.be/ | CLI/GUI |
| Portal (not fully integrated) | Partially tested | https://portal.fed4fire.eu/ | GUI |
OMNI and SFI are basic CLI tools and therefore, they can work “directly” with the aggregate managers of the UNIVBRIS OFELIA. jFed and the Fed4FIRE portal are mainly GUI tools and work by providing an intuitive GUI on top of the CLI tool which is integrated inside them. Hence, the reason why jFed and the portal are not fully compatible with UNIVBRIS OFELIA is the development of the GUI has not been finished for UNIVBRIS OFELIA. It is expected that this development should be finished in the near future. Flash news: jFed Experimenter can now work with UNIVBRIS OFELIA by using the RSpecs Editor button in jFed.
The remaining of this website section will describe the use of OMNI to list and reserve resources on UNIVBRIS OFELIA. It is assumed that the experimenter has configured the OMNI client appropriately; especially the clearinghouse/registry configuration after the experimenter has obtained the appropriate credential from one of the many Fed4FIRE authority providers.