Future Internet: Infrastructures and Services
Contents: 1) Cloud Infrastructures 2) Cloud Applications 3) XIFI 4) Fiware 5) Fi-Star
Cloud Virtual Machine (VM) Future Past/Present CPU MEMORY STORAGE OS Cloud Virtual Machine (VM) Local Workstation Terminal & Browser based OS
Desktop Apps Cloud Apps Multi-user Applications No installation for user Accessible over the network User subscribes to service Single-user Applications Machine specific installation User buys software
Desktop Apps Cloud Apps Local Storage Cloud Storage MS Office E.g., DropBox MS Office Google Docs
How the Cloud works… Virtualization of resources: Compute, Network and Storage
How the Cloud works… Cloud provisioning models
Cloud Services
Cloud Main Advantages 1. Scalability 2. Elasticity 3. High Availability
Scalability Add nodes on the fly! - Create new VMs through software rather than setup new machines. - Upgrades VMs with the click of a button - Add nodes to extend the cloud infrastructure without downtime
Elasticity Allows automated scaling in order to adapt to the current demands Exampe: Video streaming company
High Availability Minimized downtime for services Increased IT-efficiency results to a better infrastructure management reducing downtime significantly
Allows the virtualization of resources Offers services to manage the virtualized resources
OpenStack architecture Distributed, modular and scalable.
Virtualization
Horizon: Provides a GUI for basic cloud administration functionality KeyStone: Authorization. Manages users, tenants, roles etc. Ceilometer: Monitors, collects and stores usage data
Heat: Orchestration. Automates deployment for compute, storage and network resources. Cinder: Block storage for VMs Neutron: Networking
Swift: Object storage service for storing and retrieving data. Glance: Disk image service Nova: Compute Service. Schedules and manages VM instances
OpenStack architecture
Openstack Architecture of Intellicloud Cloud Compute Cloud Compute Cloud Compute Cloud Controller Cloud Network Cloud Compute Cloud Compute c06.intellicloud cloud.intellicloud network.intellicloud c01.intellicloud Identity Service (Keystone) Image Service (Glance) Compute Service (Nova) Block Storage (Cinder) Network Service (Quantum) Dashboard Service (Horizon) MySQL Server RabbitMQ Server NTP Server Network Service (Quantum) Virtual Network Service (OpenVSwitch) NTP Server Compute Service (Nova) Network Service (Quantum) Virtual Network Service (OpenVSwitch) KVM Hypervisor NTP Server Openstack Grizzly, 8 nodes installation 48 Cores 256 GB Ram 8 TB
Physical Network Architecture Internet Physical Network Architecture eth0 147.25.50.4 10.10.10.12 c02 147.25.50.5 10.10.10.13 c03 147.25.50.6 10.10.10.14 c04 147.25.50.7 10.10.10.15 c05 147.25.50.8 10.10.10.16 c06 c01 cloud eth0 eth1 147.25.50.3 10.10.10.11 147.25.50.1/141 10.10.10.10 eth0 br-ex network 147.25.50.2/142 10.10.10.9 eth1, br-int local switch Openstack Management Network eth1 Openstack VM Configuration Network br-int Openstack VM Internet Access br-ex
Intellicloud Services Current Cloud Services GEs IaaS CPU Memory HD Network & Internet Virtual Topologies OS Images PaaS IaaS + GE (Development Platform) SaaS IaaS + PaaS A Future Internet Application
Building Applications on the Cloud
Cloud Application Web Application = Cloud Application
Cloud Application Use Generic Enablers as building blocks for apps!
Cloud Application Business Logic Authentication Database connect GE2
Generic Enablers A GE consists of a set of services with common background all designed using the REST architectural style. Example GE Services: Get users Get user Delete user Create new user
GE Generic Enablers REST API services GET – POST -DELETE Output: Call service using the URL: GET www.myservice.com/users GE POST www.myservice.com/users DELETE www.myservice.com/users?id=1 Output: JSON or XML & response code GET – POST -DELETE
SE Specific Enablers GE2 GE1 REST API Output: JSON or XML Combination of services from at least 2 different GEs GE2 GE1 SE REST API Output: JSON or XML
Example Architecture: Interact
XIFI Federation
The aim of FI-WARE is to be useful for Europe Other Usage areas eHealth Tourism Smart Grid Transport E- business Utilities and environment FI-WARE platform will serve objectives of usage areas and will have the ambition of fulfilling the needs of a broader market The aim of FI-WARE is to be useful for Europe 08/04/2019
Transport, Mobility and Logistics Advanced OpenStack-based Cloud + rich library of Generic Enablers eHealth tourism Transport, Mobility and Logistics e-government Smart Energy Grid …
Apps/Services Provider The VISION FI-WARE will be a technological foundation to satisfy the demands of application/services providers and consumers across various usage areas, stimulating and cultivating a sustainable FI service ecosystem Consumers People Businesses Apps/Services Provider Platform Provider
Elements & Functions of FI Core Platform The FI Core Platform comprises a set of technological “Generic Enablers” which are considered general purpose and common to several current and future “usage areas” Generic Enablers (therefore, the FI Core Platform) will provide open interfaces for development of Applications Usage area projects under the PPP Cloud Hosting App/Service Delivery Support Services Interface to IoT Interface to Network Security, Trust Dev Tools
FI-WARE Generic Enablers (GEs) User authentication Why not having a unique authentication system for all our actions? Identity management GE Offers authentication and authorization for users, services or applications
FI-WARE Generic Enablers (GEs) JSON Data Storage A service that provides an API for storing and retrieving json objects. We don’t need to worry about scaling! The service takes care of that!
FI-WARE Generic Enablers (GEs) Context Broker Users subscribe to context and get notified on context updates. Allows efficient filtering E.g., Interest topic distribution application
Generic Enablers GEs at a glance: Open specification for developing modules Implementation from a service provider Images with installed GEs (available by FI-WARE) Documentation Installation Administration Testing parameter configuration Protocol Adapter GE data collection sensor connectivity sensor detection Gateway Device Management GE sensor connectivity subscription interface Publish/Subscribe GE data registration context data acquisition Data Handling GE configuration parameter data collection (GUI) IoT Broker GE configuration parameters (NGSI10) context management (NGSI9) Configuration management GE context management (NGSI9) context to device (NGSI9) Mediator GE communication protocol communication protocol Identity management GE login authentication access token …
Cloud in sensitive domains: Healthcare provisioning Why cloud computing & what is the problem? Standards, regulations, recommendation legislation, ISO standards Security standards (ISO 27000) there are severe restrictions to data transfer, storage, aggregation and analysis Cloud computing: remote services (data management in distant datacenters)
Problem area: Healthcare provisioning Data Data Data Data Data Data Data Data Data Data Data Data Data BigData Data Data Data Data Data Data Data Data Data Data Data Data Data Data Data Data Data Data Data
Hybrid Cloud Deployment: Software to Data A reverse cloud approach that offer the required framework (Public Cloud) to allow Software Enablers to be initiated at clients’ sites and to be hosted in a Private Cloud Software to data cloud model Provider Edge Consumer Edge Healthcare private cloud Platform for developers Provider of services Deployment of Software Blocks as utility services Provision of Software Blocks
FI-STAR at a glance Future Internet Social and Technological Alignment Research (FISTAR) project attempting to identify suitable software to data solutions based on Generic Enabler technology provided from FI-WARE to establish early trials in the health domain FI-STAR will develop and deploy 8 use case Future Internet (FI) applications FI-STAR Use Case Private Cloud FI-STAR developers Provider: FI-WARE Deployment of Software Blocks as utility services Provision of Software Blocks 45
Overall Goal FI-STAR establishes early trials in the Health Care domain building on Future Internet (FI) technology leveraging on the outcomes of FI-PPP Phase 1. To meet the requirements of a global Health industry FI-STAR will use a fundamentally different, “reverse” cloud approach that is. It will bring the software to the data, rather than bringing the data to the software. FI-STAR will deploy and execute 7 early trials across Europe FI-STAR will validate the FI-PPP core platform concept by using GEs to build its framework (7 use cases applications)
Building blocks of FI-Applications Generic Enablers (GEs) are considered as software modules: offer various functionalities along with protocols interfaces for operation and communication. Using GEs FI-STAR will develop Specific Enablers (SEs) that highlight: Light-weight applications Robust security and privacy functionality Optimal usage of network resources Virtualization of resources
Generic Enablers GEs at a glance: Open specification for developing modules Implementation from a service provider Images with installed GEs (available by FI-WARE) Documentation Installation Administration Testing parameter configuration Protocol Adapter GE data collection sensor connectivity sensor detection Gateway Device Management GE sensor connectivity subscription interface Publish/Subscribe GE data registration context data acquisition Data Handling GE configuration parameter data collection (GUI) IoT Broker GE configuration parameters (NGSI10) context management (NGSI9) Configuration management GE context management (NGSI9) context to device (NGSI9) Mediator GE communication protocol communication protocol Identity management GE login authentication access token …
The High level architecture of the diabetes care FI application
Architecture of GEs
Example 1
Example 2 http://147.27.50.51/clientfiles/test_index
Example 3