We use proprietary and third party's cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
D.4.4.2 User and Programmers Guide front page - FIWARE Forge Wiki

D.4.4.2 User and Programmers Guide front page

From FIWARE Forge Wiki

Jump to: navigation, search

Private Public Partnership Project (PPP)
Large-scale Integrated Project (IP)


D.4.4.2: FI-WARE User and Programmers Guide

Project acronym: FI-WARE
Project full title: Future Internet Core Platform
Contract No.: 285248
Strategic Objective: FI.ICT-2011.1.7 Technology foundation: Future Internet Core Platform
Project Document Number: ICT-2011-FI-285248-WP4-D.4.4.2
Project Document Date: 2013-04-30
Deliverable Type and Security: Public
Author: FI-WARE Consortium
Contributors: FI-WARE Consortium

Executive Summary

FIWARE WIKI editorial remark:
WPL, please add a summary here

About This Document

This document comes along with the Software implementation of components, each release of the document being referred to the corresponding Software release (as per D.x.3), to provide documentation of the features offered by the components and interfaces to users/adopters. Moreover, it explains the way they can be exploited in their developments.

Intended Audience

The document targets users as well as programmers of FI-WARE Generic Enablers.

Chapter Context

The Cloud Chapter offers Generic Enablers that comprise the foundation for designing a modern cloud hosting infrastructure that can be used to develop, deploy and manage Future Internet applications and services, as outlined in Materializing Cloud Hosting in FI-WARE.

The capabilities available in the second release of FI-WARE Cloud Hosting platform are outlined in Roadmap of Cloud Hosting.

The following diagram shows the main components (Generic Enablers) that comprise the second release of FI-WARE architecture.

Cloud Architecture Overview

The architecture comprises a set of Generic Enablers that together provide hosting capabilities of several kinds and at several levels of resource abstraction -- aiming at the needs of different applications hosted on the cloud platform. IaaS Data Center Resource Management (DCRM) GE is offering provisioning and life cycle management of virtualized resources (compute, storage, network) associated with virtual machines, which can run general purpose Operating Systems as well as arbitrary software stacks. Application developers and providers can use these virtual machines to develop and deploy their own software components that comprise their application stacks. Object Storage GE offers provisioning and life cycle management of object-based storage containers and elements, which can be efficiently used to store unstructured fixed content (such as images, videos, etc) as well as accompanying metadata. Job Scheduler GE offers the application to submit and manage computational jobs in a unified and scalable manner. Edgelet Management GE offers the capability to host lightweight application components, called edgelets, on devices typically located outside of the Data Center, such as those provided by the Cloud Proxy GE (developed jointly by the Cloud chapter and the Interfaces to Network and Devices chapter). Software Deployment and Configuration (SDC) GE offers a flexible framework for installation and customization of software products within individual virtual machines. Policy Manager GE provides a framework for rule-based management of cloud resources, including application auto-scaling based leveraging metrics collected by Monitoring GE. Lastly, PaaS Management GE uses the above capabilities to offer holistic provisioning and ongoing management of complex workloads comprising sophistical combination of interdependent VMs and associated resources (such as multi-tier web applications or even complete custom-built PaaS environments), as well as configuration and management of software components within the VMs.

Each of the above GEs provides a REST API that can be used programmatically. The human actor represents the programmatic user of the different capabilities of the Cloud GEs via REST APIs. Moreover, the Cloud chapter provides a Web-based Portal (part of of the UI layer) , which surfaces main capabilities in an interactive manner --such as provisioning and monitoring of VM instances and services.

Cloud Hosting Generic Enablers are using the Identity Management and Access Control framework provided by the Security chapter, as outlined in the Cloud Security Architecture.

Structure of this Document

The document is generated out of a set of documents provided in the FI-WARE wiki. For the current version of the documents, please visit the wiki at http://wiki.fi-ware.eu

The following resources were used to generate this document:

IaaS Data Center Resource Management - User and Programmers Guide
IaaS Service Management - User and Programmers Guide
Self-Service Interfaces - User and Programmers Guide
Object Storage - User and Programmers Guide
Software Management And Configuration - User and Programmers Guide
Monitoring - User and Programmers Guide
PaaS Management - User and Programmers Guide
Job Scheduler - User and Programmers Guide

Typographical Conventions

Starting with October 2012 the FI-WARE project improved the quality and streamlined the submission process for deliverables, generated out of our wikis. The project is currently working on the migration of as many deliverables as possible towards the new system.

This document is rendered with semi-automatic scripts out of a MediaWiki system operated by the FI-WARE consortium.

Links within this document

The links within this document point towards the wiki where the content was rendered from. You can browse these links in order to find the "current" status of the particular content.

Due to technical reasons part of the links contained in the deliverables generated from wiki pages cannot be rendered to fully working links. This happens for instance when a wiki page references a section within the same wiki page (but there are other cases). In such scenarios we preserve a link for readability purposes but this points to an explanatory page, not the original target page.

In such cases where you find links that do not actually point to the original location, we encourage you to visit the source pages to get all the source information in its original form. Most of the links are however correct and this impacts a small fraction of those in our deliverables.


Figures are mainly inserted within the wiki as the following one:


Only if the wiki-page uses this format, the related caption is applied on the printed document. As currently this format is not used consistently within the wiki, please understand that the rendered pages have different caption layouts and different caption formats in general. Due to technical reasons the caption can't be numbered automatically.

Sample software code

Sample API-calls may be inserted like the following one.



The current document has been elaborated using a number of collaborative tools, with the participation of Working Package Leaders and Architects as well as those partners in their teams they have decided to involve; IBM, Intel, Technicolor, Telefonica.

Keyword list

FI-WARE, PPP, Architecture Board, Steering Board, Roadmap, Reference Architecture, Generic Enabler, Open Specifications, I2ND, Cloud, IoT, Data/Context Management, Applications/Services Ecosystem, Delivery Framework , Security, Developers Community and Tools , ICT, es.Internet, Latin American Platforms, Cloud Edge, Cloud Proxy.

Changes History

Release Major changes description Date Editor
v1 First draft of deliverable submission generated 2013-04-22 TID
v2 Consolidated version 2013-05-10 IBM
v3 Version after revision 2013-05-13 IBM
v4 Version for delivery 2013-05-14 TID

Table of Contents

FIWARE WIKI editorial remark:
In the final deliverable, somebody would include the TOC here
Personal tools
Create a book