scholarly journals VirIoT: A Cloud of Things That Offers IoT Infrastructures as a Service

Sensors ◽  
2021 ◽  
Vol 21 (19) ◽  
pp. 6546
Author(s):  
Andrea Detti ◽  
Hidenori Nakazato ◽  
Juan Antonio Martínez Navarro ◽  
Giuseppe Tropea ◽  
Ludovico Funari ◽  
...  
Keyword(s):  
Open Source ◽  
Data Centers ◽  
Infrastructure Management ◽  
Service Model ◽  
Sensors And Actuators ◽  
Iot Applications ◽  
Software Companies ◽  
Fair Comparison ◽  
Cloud Providers ◽  
Application Developers

Many cloud providers offer IoT services that simplify the collection and processing of IoT information. However, the IoT infrastructure composed of sensors and actuators that produces this information remains outside the cloud; therefore, application developers must install, connect and manage the cloud. This requirement can be a market barrier, especially for small/medium software companies that cannot afford the infrastructural costs associated with it and would only prefer to focus on IoT application developments. Motivated by the wish to eliminate this barrier, this paper proposes a Cloud of Things platform, called VirIoT, which fully brings the Infrastructure as a service model typical of cloud computing to the world of Internet of Things. VirIoT provides users with virtual IoT infrastructures (Virtual Silos) composed of virtual things, with which users can interact through dedicated and standardized broker servers in which the technology can be chosen among those offered by the platform, such as oneM2M, NGSI and NGSI-LD. VirIoT allows developers to focus their efforts exclusively on IoT applications without worrying about infrastructure management and allows cloud providers to expand their IoT services portfolio. VirIoT uses external things and cloud/edge computing resources to deliver the IoT virtualization services. Its open-source architecture is microservice-based and runs on top of a distributed Kubernetes platform with nodes in central and edge data centers. The architecture is scalable, efficient and able to support the continuous integration of heterogeneous things and IoT standards, taking care of interoperability issues. Using a VirIoT deployment spanning data centers in Europe and Japan, we conducted a performance evaluation with a two-fold objective: showing the efficiency and scalability of the architecture; and leveraging VirIoT’s ability to integrate different IoT standards in order to make a fair comparison of some open-source IoT Broker implementations, namely Mobius for oneM2M, Orion for NGSIv2, Orion-LD and Scorpio for NGSI-LD.

scholarly journals Self-healing trans-cloud applications

Computing ◽  
2021 ◽  
Author(s):  
Antonio Brogi ◽  
Jose Carrasco ◽  
Francisco Durán ◽  
Ernesto Pimentel ◽  
Jacopo Soldani
Keyword(s):  
Open Source ◽  
Cloud Services ◽  
Self Healing ◽  
Controlled Experiments ◽  
Fault Handling ◽  
Extensive Evaluation ◽  
Cloud Providers ◽  
Heterogeneous Cloud ◽  
Cloud Applications ◽  
Unstable States

AbstractTrans-cloud applications consist of multiple interacting components deployed across different cloud providers and at different service layers (IaaS and PaaS). In such complex deployment scenarios, fault handling and recovery need to deal with heterogeneous cloud offerings and to take into account inter-component dependencies. We propose a methodology for self-healing trans-cloud applications from failures occurring in application components or in the cloud services hosting them, both during deployment and while they are being operated. The proposed methodology enables reducing the time application components rely on faulted services, hence residing in “unstable” states where they can suddenly fail in cascade or exhibit erroneous behaviour. We also present an open-source prototype illustrating the feasibility of our proposal, which we have exploited to carry out an extensive evaluation based on controlled experiments and monkey testing.

scholarly journals MIFaaS: A Mobile-IoT-Federation-as-a-Service Model for dynamic cooperation of IoT Cloud Providers

2017 ◽  
Vol 70 ◽  
pp. 126-137 ◽  
Author(s):  
I. Farris ◽  
L. Militano ◽  
M. Nitti ◽  
L. Atzori ◽  
A. Iera
Keyword(s):  
Service Model ◽  
Cloud Providers ◽  
Dynamic Cooperation

Open-Source Real-Time Robot Operation and Control System for Highly Dynamic, Modular Machines

2013 ◽  
Author(s):  
Andrew Peekema ◽  
Daniel Renjewski ◽  
Jonathan Hurst
Keyword(s):  
Control System ◽  
Open Source ◽  
Real Time ◽  
High Frequency ◽  
Performance Test ◽  
Frequency Control ◽  
Human Robot Interaction ◽  
Sensors And Actuators ◽  
Key Innovation ◽  
Hard Real Time

The control system of a highly dynamic robot requires the ability to respond quickly to changes in the robot’s state. This type of system is needed in varying fields such as dynamic locomotion, multicopter control, and human-robot interaction. Robots in these fields require software and hardware capable of hard real-time, high frequency control. In addition, the application outlined in this paper requires modular components, remote guidance, and mobile control. The described system integrates a computer on the robot for running a control algorithm, a bus for communicating with microcontrollers connected to sensors and actuators, and a remote user interface for interacting with the robot. Current commercial solutions can be expensive, and open source solutions are often time consuming. The key innovation described in this paper is the building of a control system from existing — mostly open source — components that can provide realtime, high frequency control of the robot. This paper covers the development of such a control system based on ROS, OROCOS, and EtherCAT, its implementation on a dynamic bipedal robot, and system performance test results.

scholarly journals Software Defined Storage Implementation Model to Data Centers

2020 ◽  
Vol 9 (1) ◽  
pp. 300-303
Keyword(s):  
Open Source ◽  
Data Centers ◽  
Great Benefit ◽  
Timely Manner ◽  
Implementation Model ◽  
Economic Level ◽  
Systems Software ◽  
Definition Of

This research focuses on deliver a SDS implementation model that facilitate the definition of requirements to be delivered in a timely manner to systems. Software Defined Storage (SDS) enables different hardware technologies to be homogenized and deliver independent storage. The technologies included on the implementation model are the open-source projects Red Hat Gluster Storage and Red Hat Ceph Storage. Both technologies are integrated into a virtualization platform, it is compared at a functional and economic level with respect to some enterprise solutions and it is shown that the same operations are performed as a viable technological alternative. The favorable results of the model are presented and the great benefit that open-source technologies have open scope that allows it to be integrated into other projects is presented.

scholarly journals Data Portability Among Providers o Platform as a Service

2013 ◽  
Vol 21 (Special-Issue) ◽  
pp. 7-11
Author(s):  
Darko Androcec
Keyword(s):  
Data Storage ◽  
Query Languages ◽  
Data Models ◽  
Service Model ◽  
Data Types ◽  
Data Manipulation ◽  
Platform As A Service ◽  
Cloud Providers ◽  
Data Portability ◽  
Lock In

Abstract Platform as a service model has certain obstacles, including data lock-in. It is expensive and time-consuming to move data to the alternative providers. This paper presents data storage options in platform as a service offers and identifies the most common data portability problems between various commercial providers of platform as a service. There are differences among their storage models, data types, remote APIs for data manipulation and query languages. Representing data models of platform as a service and data mappings by means of ontology can provide a common layer to achieve data portability among different cloud providers.

Open Source in the Cloud

2014 ◽  
pp. 179-191
Author(s):  
Egbert de Smet
Keyword(s):  
Open Source ◽  
Power Supply ◽  
Distributed Storage ◽  
End Users ◽  
The Future ◽  
Cloud Providers ◽  
Open Standards ◽  
Living Environments ◽  
Crucial Part ◽  
Opening Up

Whereas “Open Source” in software is still gaining momentum in many fields of applications, it is even more present in the “behind the curtains” scene of the Cloud. It is behind the scenes because Cloud tools are only operated by Cloud providers creating their infrastructure, not by end users. But as that infrastructure is going to be a crucial part of the IT environment of the future, like water and power supply have become for the wider living environments, it is good to note that this infrastructure is not limited to (commercial) proprietary technology and standards, but rather is subject to input from the major Open Source players. This chapter reviews the main technologies of this moment in Cloud software: CloudStack of Citrix and Apache, OpenStack of Suse and Openshift from RedHat. Also the CEPH-technology for distributed storage is added in this overview due to its obvious relevance for the Cloud. The brief review of these products confirms that FOSS indeed plays a major role in the Cloud, opening up that technology for open standards and “public” ownership of this soon-to-be an essential part of our IT environment.

Open Source in Government

2011 ◽  
pp. 1287-1290 ◽  
Author(s):  
D. Berry
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
General Public ◽  
Source Code ◽  
Computer Software ◽  
Free Software ◽  
Software Projects ◽  
Software Companies ◽  
Develop Software ◽  
Software Distribution

Open source software (OSS) is computer software that has its underlying source code made available under a licence. This can allow developers and users to adapt and improve it (Raymond, 2001). Computer software can be broadly split into two development models: • Proprietary, or closed software, owned by a company or individual. Copies of the binary are made public; the source code is not usually made public. • Open-source software (OSS), where the source code is released with the binary. Users and developers can be licenced to use and modify the code, and to distribute any improvements they make. Both OSS and proprietary approaches allow companies to make a profit. Companies developing proprietary software make money by developing software and then selling licences to use the software. For example, Microsoft receives a payment for every copy of Windows sold with a personal computer. OSS companies make their money by providing services, such as advising clients on the GPL licence. The licencee can either charge a fee for this service or work free of charge. In practice, software companies often develop both types of software. OSS is developed by an ongoing, iterative process where people share the ideas expressed in the source code. The aim is that a large community of developers and users can contribute to the development of the code, check it for errors and bugs, and make the improved version available to others. Project management software is used to allow developers to keep track of the various versions. There are two main types of open-source licences (although there are many variants and subtypes developed by other companies): • Berkeley Software Distribution (BSD) Licence: This permits a licencee to “close” a version (by withholding the most recent modifications to the source code) and sell it as a proprietary product; • GNU General Public Licence (GNU, GPL, or GPL): Under this licence, licencees may not “close” versions. The licencee may modify, copy, and redistribute any derivative version, under the same GPL licence. The licencee can either charge a fee for this service or work free of charge. Free software first evolved during the 1970s but in the 1990s forked into two movements, namely free software and open source (Berry, 2004). Richard Stallman, an American software developer who believes that sharing source code and ideas is fundamental to freedom of speech, developed a free version of the widely used Unix operating system. The resulting GNU program was released under a specially created General Public Licence (GNU, GPL). This was designed to ensure that the source code would remain openly available to all. It was not intended to prevent commercial usage or distribution (Stallman, 2002). This approach was christened free software. In this context, free meant that anyone could modify the software. However, the term “free” was often misunderstood to mean no cost. Hence, during the 1990s, Eric Raymond and others proposed that open-source software was coined as a less contentious and more business-friendly term. This has become widely accepted within the software and business communities; however there are still arguments about the most appropriate term to use (Moody, 2002). The OSMs are usually organised into a network of individuals who work collaboratively on the Internet, developing major software projects that sometimes rival commercial software but are always committed to the production of quality alternatives to those produced by commercial companies (Raymond, 2001; Williams, 2002). Groups and individuals develop software to meet their own and others’ needs in a highly decentralised way, likened to a Bazaar (Raymond, 2001). These groups often make substantive value claims to support their projects and foster an ethic of community, collaboration, deliberation, and intellectual freedom. In addition, it is argued by Lessig (1999) that the FLOSS community can offer an inspiration in their commitment to transparency in their products and their ability to open up governmental regulation and control through free/libre and open source code.

scholarly journals Transportable open-source application program interface and user interface for generic humanoids: TOUGH

2020 ◽  
Vol 17 (3) ◽  
pp. 172988142092160
Author(s):  
Vinayak Jagtap ◽  
Shlok Agarwal ◽  
Ameya Wagh ◽  
Michael Gennert
Keyword(s):  
User Interface ◽  
Open Source ◽  
Humanoid Robots ◽  
Application Program Interface ◽  
Sensors And Actuators ◽  
Seamless Integration ◽  
Application Program ◽  
Diverse Field ◽  
High Level ◽  
Program Interface

Humanoid robotics is a complex and highly diverse field. Humanoid robots may have dozens of sensors and actuators that together realize complicated behaviors. Adding to the complexity is that each type of humanoid has unique application program interfaces, thus software written for one humanoid does not easily transport to others. This article introduces the transportable open-source application program interface and user interface for generic humanoids, a set of application program interfaces that simplifies the programming and operation of diverse humanoid robots. These application program interfaces allow for quick implementation of complex tasks and high-level controllers. Transportable open-source application program interface and user interface for generic humanoids has been developed for, and tested on, Boston Dynamics’ Atlas V5 and NASA’s Valkyrie R5 robots. It has proved successful for experiments on both robots in simulation and hardware, demonstrating the seamless integration of manipulation, perception, and task planning. To encourage the rapid adoption of transportable open-source application program interface and user interface for generic humanoids for education and research, the software is available as Docker images, which enable quick setup of multiuser simulation environments.

scholarly journals Stateless IoT

Information ◽  
2020 ◽  
Vol 11 (2) ◽  
pp. 85 ◽  
Author(s):  
Augusto Ciuffoletti
Keyword(s):  
Energy Saving ◽  
Design Principle ◽  
Internal State ◽  
Use Case ◽  
System Operation ◽  
Sensors And Actuators ◽  
Iot Applications ◽  
Basic Model ◽  
Energy Footprint ◽  
Save Energy

Energy consumption is a relevant matter in the design of IoT applications. Edge units—sensors and actuators—save energy by operating intermittently. When idle, they suspend their operation, losing the content of the onboard memory. Their internal state, needed to resume their work, is recorded on external storage: in the end, their internal operation is stateless. The backend infrastructure does not follow the same design principle: concentrators, routers, and servers are always-on devices that frustrate the energy-saving operation of edge devices. In this paper, we show how serverless functions, asynchronously invoked by the stateless edge devices, are an energy-saving option. We introduce a basic model for system operation and energy footprint evaluation. To demonstrate its soundness, we study a simple use case, from the design to a prototype.

Sign in / Sign up

Export Citation Format

Share Document