... | ... | @@ -32,56 +32,56 @@ Main capabilities offered include: |
|
|
|
|
|
The Store GE offers support for selling services to both consumers and developers of Future Internet applications and services and for end-to-end managing of offerings and sales. [More info (...)](http://catalogue.fi-ware.org/enablers/store-wstore)
|
|
|
|
|
|
### Cloud Hosting
|
|
|
- **IaaS Data Center Resource Management GE – IBM Implementation**
|
|
|
| Cloud Hosting |
|
|
|
| ------------- |
|
|
|
|
|
|
This GE provides the facilities to provision virtual machines, as well as to associated compute, storage and network resources. The implementation is based on OpenStack -- the rapidly emerging open source project providing cloud infrastructure middleware, being adopted by the wide ecosystem of organizations across the various industry sectors.
|
|
|
![](/ari/fractals/raw/master/wiki/images/bullet-list-icon.jpg) **IaaS Data Center Resource Management GE – IBM Implementation**
|
|
|
|
|
|
[More info (...)](http://catalogue.fi-ware.org/enablers/iaas-data-center-resource-management-ge-ibm-implementation)
|
|
|
This GE provides the facilities to provision virtual machines, as well as to associated compute, storage and network resources. The implementation is based on OpenStack -- the rapidly emerging open source project providing cloud infrastructure middleware, being adopted by the wide ecosystem of organizations across the various industry sectors. [More info (...)](http://catalogue.fi-ware.org/enablers/iaas-data-center-resource-management-ge-ibm-implementation)
|
|
|
|
|
|
- **Object Storage GE – FI-WARE Implementation**
|
|
|
![](/ari/fractals/raw/master/wiki/images/bullet-list-icon.jpg) **Object Storage GE – FI-WARE Implementation**
|
|
|
|
|
|
This Generic Enabler Implementation provides robust, scalable object storage functionality through an open, standardised interface: it exposes a CDMI interface on top of OpenStack Swift. The CDMI interface provides a standardised mechanism to manipulate both the binary objects that are stored, and the hierarchy of containers in which they are organised. This RESTful API can be accessed from any client technology that can communicate over HTTP. By building on top of OpenStack Swift, all the benefits of this rapidly maturing open-source cloud storage solution can be realised. The highly-available, distributed, and scalable features of swift can be exposed using commodity hardware.
|
|
|
This Generic Enabler Implementation provides robust, scalable object storage functionality through an open, standardised interface: it exposes a CDMI interface on top of OpenStack Swift. The CDMI interface provides a standardised mechanism to manipulate both the binary objects that are stored, and the hierarchy of containers in which they are organised. This RESTful API can be accessed from any client technology that can communicate over HTTP. By building on top of OpenStack Swift, all the benefits of this rapidly maturing open-source cloud storage solution can be realised. The highly-available, distributed, and scalable features of swift can be exposed using commodity hardware. [More info (...)](http://catalogue.fi-ware.org/enablers/object-storage-ge-fi-ware-implementation)
|
|
|
|
|
|
[More info (...)](http://catalogue.fi-ware.org/enablers/object-storage-ge-fi-ware-implementation)
|
|
|
| Data/Context Management |
|
|
|
| ----------------------- |
|
|
|
|
|
|
### Data/Context Management
|
|
|
- **BigData Analysis – Cosmos**
|
|
|
![](/ari/fractals/raw/master/wiki/images/bullet-list-icon.jpg) **BigData Analysis – Cosmos**
|
|
|
|
|
|
Cosmos is an implementation of the Big Data GE, allowing the deployment of private computing clusters based on Hadoop ecosystem. Current version of Cosmos allows users to:
|
|
|
- I/O operations regarding Infinity, a persistent storage cluster based on HDFS.
|
|
|
Cosmos is an implementation of the Big Data GE, allowing the deployment of private computing clusters based on Hadoop ecosystem. Current version of Cosmos allows users to:
|
|
|
- I/O operations regarding Infinity, a persistent storage cluster based on HDFS.
|
|
|
Creation, usage and deletion of private computing clusters based on MapReduce and SQL-like querying systems such as Hive or Pig.
|
|
|
- Manage the platform, in many aspects such as services, users, clusters, etc, from the Cosmos API or the Cosmos CLI
|
|
|
- Manage the platform, in many aspects such as services, users, clusters, etc, from the Cosmos API or the Cosmos CLI
|
|
|
|
|
|
[More info (...)](http://catalogue.fi-ware.org/enablers/bigdata-analysis-cosmos)
|
|
|
[More info (...)](http://catalogue.fi-ware.org/enablers/bigdata-analysis-cosmos)
|
|
|
|
|
|
- **Complex Event Processing (CEP) – IBM Proactive Technology Online**
|
|
|
![](/ari/fractals/raw/master/wiki/images/bullet-list-icon.jpg) **Complex Event Processing (CEP) – IBM Proactive Technology Online**
|
|
|
|
|
|
The CEP GE analyses event data in real-time, generates immediate insight and enables instant response to changing conditions. While standard reactive applications are based on reactions to single events, the CEP GE reacts to situations rather than to single events. A situation is a condition that is based on a series of events that have occurred within a dynamic time window called processing context. Situations include composite events (e.g., sequence), counting operators on events (e.g., aggregation) and absence operators. The IBM Proactive Technology Online (Proton) is an implementation of the FiWARE CEP (Complex Event Processing) GE. The IBM Proactive Technology Online is a scalable integrated platform to support the development, deployment, and maintenance of event-driven applications. The IBM Proactive Technology Online authoring tool allows the definition of CEP applications using a web user interface. The The IBM Proactive Technology Online engine is a runtime tool that receives information on the occurrence of events from event producers, detects situations, and reports the detected situations to external consumers.
|
|
|
The CEP GE analyses event data in real-time, generates immediate insight and enables instant response to changing conditions. While standard reactive applications are based on reactions to single events, the CEP GE reacts to situations rather than to single events. A situation is a condition that is based on a series of events that have occurred within a dynamic time window called processing context. Situations include composite events (e.g., sequence), counting operators on events (e.g., aggregation) and absence operators. The IBM Proactive Technology Online (Proton) is an implementation of the FiWARE CEP (Complex Event Processing) GE. The IBM Proactive Technology Online is a scalable integrated platform to support the development, deployment, and maintenance of event-driven applications. The IBM Proactive Technology Online authoring tool allows the definition of CEP applications using a web user interface. The The IBM Proactive Technology Online engine is a runtime tool that receives information on the occurrence of events from event producers, detects situations, and reports the detected situations to external consumers. [More info (...)](http://catalogue.fi-ware.org/enablers/complex-event-processing-cep-ibm-proactive-technology-online)
|
|
|
|
|
|
[More info (...)](http://catalogue.fi-ware.org/enablers/complex-event-processing-cep-ibm-proactive-technology-online)
|
|
|
![](/ari/fractals/raw/master/wiki/images/bullet-list-icon.jpg) **Publish/Subscribe Context Broker – Orion Context Broker**
|
|
|
|
|
|
- **Publish/Subscribe Context Broker – Orion Context Broker**
|
|
|
The Orion Context Broker is an implementation of the Publish/Subscribe Context Broker GE, providing the NGSI9 and NGSI10 interfaces. Using these interfaces, clients can do several operations:
|
|
|
- Register context producer applications, e.g. a temperature sensor within a room
|
|
|
- Update context information, e.g. send updates of temperature
|
|
|
- Being notified when changes on context information take place (e.g. the temperature has changed) or with a given frequency (e.g. get the temperature each minute)
|
|
|
- Query context information. The Orion Context Broker stores context information updated from applications, so queries are resolved based on that information.
|
|
|
|
|
|
The Orion Context Broker is an implementation of the Publish/Subscribe Context Broker GE, providing the NGSI9 and NGSI10 interfaces. Using these interfaces, clients can do several operations:
|
|
|
- Register context producer applications, e.g. a temperature sensor within a room
|
|
|
- Update context information, e.g. send updates of temperature
|
|
|
- Being notified when changes on context information take place (e.g. the temperature has changed) or with a given frequency (e.g. get the temperature each minute)
|
|
|
- Query context information. The Orion Context Broker stores context information updated from applications, so queries are resolved based on that information.
|
|
|
[More info (...)](http://catalogue.fi-ware.org/enablers/publishsubscribe-context-broker-orion-context-broker)
|
|
|
|
|
|
[More info (...)](http://catalogue.fi-ware.org/enablers/publishsubscribe-context-broker-orion-context-broker)
|
|
|
| IoT Services Eanablement |
|
|
|
| ------------------------ |
|
|
|
|
|
|
### IoT Services Eanablement
|
|
|
- **Configuration Manager – Orion Context Broker**
|
|
|
The Orion Context Broker is an implementation of the Configuration Manager GE, providing the NGSI9 interfaces. Within the IoT chapter, it is aimed to be used in combination with IoT Broker GE (so the IoTBroker deals with NGSI10 in a stateless fashion, relying in Orion as persistent storage for NGSI9 registrations) although it can be also used as a stand alone component. Using the NGSI9 interface, clients can do several operations:
|
|
|
- Register context producer applications, e.g. a temperature sensor within a room
|
|
|
- Discover context producers information, e.g. which sensors are providing temperature for a given entity
|
|
|
- Being notified when changes on context information availability
|
|
|
![](/ari/fractals/raw/master/wiki/images/bullet-list-icon.jpg) **Configuration Manager – Orion Context Broker**
|
|
|
The Orion Context Broker is an implementation of the Configuration Manager GE, providing the NGSI9 interfaces. Within the IoT chapter, it is aimed to be used in combination with IoT Broker GE (so the IoTBroker deals with NGSI10 in a stateless fashion, relying in Orion as persistent storage for NGSI9 registrations) although it can be also used as a stand alone component. Using the NGSI9 interface, clients can do several operations:
|
|
|
- Register context producer applications, e.g. a temperature sensor within a room
|
|
|
- Discover context producers information, e.g. which sensors are providing temperature for a given entity
|
|
|
- Being notified when changes on context information availability
|
|
|
|
|
|
[More info (...)](http://catalogue.fi-ware.org/enablers/configuration-manager-orion-context-broker)
|
|
|
[More info (...)](http://catalogue.fi-ware.org/enablers/configuration-manager-orion-context-broker)
|
|
|
|
|
|
### Security
|
|
|
- **Identity Management - Keyrock**
|
|
|
Identity Management covers a number of aspects involving users' access to networks, services and applications, including secure and private authentication from users to devices, networks and services, authorization & trust management, user profile management, privacy-preserving disposition of personal data, Single Sign-On (SSO) to service domains and Identity Federation towards applications. The Identity Manager is the central component that provides a bridge between IdM systems at connectivity-level and application-level. Furthermore, Identity Management is used for authorising foreign services to access personal data stored in a secure environment. Hereby usually the owner of the data must give consent to access the data; the consent-giving procedure also implies certain user authentication.
|
|
|
| Security |
|
|
|
| -------- |
|
|
|
|
|
|
[More info (...)](http://catalogue.fi-ware.org/enablers/identity-management-keyrock) |
|
|
\ No newline at end of file |
|
|
![](/ari/fractals/raw/master/wiki/images/bullet-list-icon.jpg) **Identity Management - Keyrock**
|
|
|
Identity Management covers a number of aspects involving users' access to networks, services and applications, including secure and private authentication from users to devices, networks and services, authorization & trust management, user profile management, privacy-preserving disposition of personal data, Single Sign-On (SSO) to service domains and Identity Federation towards applications. The Identity Manager is the central component that provides a bridge between IdM systems at connectivity-level and application-level. Furthermore, Identity Management is used for authorising foreign services to access personal data stored in a secure environment. Hereby usually the owner of the data must give consent to access the data; the consent-giving procedure also implies certain user authentication. [More info (...)](http://catalogue.fi-ware.org/enablers/identity-management-keyrock) |
|
|
\ No newline at end of file |