This document outlines a master's thesis on developing a scalable heterogeneous software architecture for telecommunication clouds. The thesis will propose an architecture using cloud computing principles and patterns to enable elasticity while providing quality of service guarantees for stateful network functions. It will define and implement the architecture, then evaluate it through an IMS network demonstration. An introduction provides background and motivation, followed by a literature review on existing approaches. The proposed architecture section outlines the framework, distribution of application state, communication approach, and use of patterns like microservices and auto-scaling. Hybrid cloud deployments are also discussed.
Mobility and federation of Cloud computingDavid Wallom
The document discusses different models of mobile cloud computing including private, public, hybrid, and federated clouds. It describes the European Grid Infrastructure (EGI) Federated Cloud, which provides a single access point to multiple cloud providers through standard interfaces. The EGI Federated Cloud has been used productively for several years and supports a variety of applications and research communities through technical support and high-level tools.
This document analyzes the performance of various hypervisors (KVM, XEN, Hyper-V, ESXi) using RabbitMQ message broker server. The authors establish identical VM configurations on each hypervisor with 1 CPU and 1GB RAM. Using RabbitMQ, they stress test the hypervisors by sending a large number of messages between VMs. They measure performance metrics like message throughput, latency and queue length. The results show ESXi had the best performance for most tests, completing tasks significantly faster than other hypervisors. However, no single hypervisor outperformed the others on all tests, indicating workloads may be suited to different virtualization platforms.
O documento propõe deixar de lado conceitos ultrapassados e investir em ideias inovadoras que promovam transformações positivas. Deve-se libertar-se para buscar o novo, imaginar cores, estratégias e emoções capazes de tocar as pessoas e gerar ações. Os serviços incluem diagnóstico, planejamento, conversão, implantação e gestão de projetos de sinalização, letreiros, outdoors e banners para diversos clientes.
Este documento presenta una introducción a los sistemas de computación, incluyendo definiciones de hardware, software, usuarios, información y documentación. Explica que un sistema de computación es un conjunto de elementos que permite administrar componentes y información, y describe brevemente hardware como los componentes físicos de una computadora y software como programas que permiten resolver problemas.
Este documento descreve as condições humanas e materiais da Biblioteca Escolar (BE) do Agrupamento de Escolas de Sabugal. A liderança do professor bibliotecário é eficaz em promover a comunicação e integração dos objetivos da BE com as estruturas educativas. A BE apoia as atividades curriculares e extracurriculares dos alunos e professores, bem como projetos de promoção da leitura que envolvem a comunidade escolar.
Este documento proporciona 8 pasos para subir un video de YouTube a Blogger, que incluyen iniciar sesión en Blogger, crear una entrada, buscar y seleccionar el video deseado en YouTube y subirlo a Blogger.
Mobility and federation of Cloud computingDavid Wallom
The document discusses different models of mobile cloud computing including private, public, hybrid, and federated clouds. It describes the European Grid Infrastructure (EGI) Federated Cloud, which provides a single access point to multiple cloud providers through standard interfaces. The EGI Federated Cloud has been used productively for several years and supports a variety of applications and research communities through technical support and high-level tools.
This document analyzes the performance of various hypervisors (KVM, XEN, Hyper-V, ESXi) using RabbitMQ message broker server. The authors establish identical VM configurations on each hypervisor with 1 CPU and 1GB RAM. Using RabbitMQ, they stress test the hypervisors by sending a large number of messages between VMs. They measure performance metrics like message throughput, latency and queue length. The results show ESXi had the best performance for most tests, completing tasks significantly faster than other hypervisors. However, no single hypervisor outperformed the others on all tests, indicating workloads may be suited to different virtualization platforms.
O documento propõe deixar de lado conceitos ultrapassados e investir em ideias inovadoras que promovam transformações positivas. Deve-se libertar-se para buscar o novo, imaginar cores, estratégias e emoções capazes de tocar as pessoas e gerar ações. Os serviços incluem diagnóstico, planejamento, conversão, implantação e gestão de projetos de sinalização, letreiros, outdoors e banners para diversos clientes.
Este documento presenta una introducción a los sistemas de computación, incluyendo definiciones de hardware, software, usuarios, información y documentación. Explica que un sistema de computación es un conjunto de elementos que permite administrar componentes y información, y describe brevemente hardware como los componentes físicos de una computadora y software como programas que permiten resolver problemas.
Este documento descreve as condições humanas e materiais da Biblioteca Escolar (BE) do Agrupamento de Escolas de Sabugal. A liderança do professor bibliotecário é eficaz em promover a comunicação e integração dos objetivos da BE com as estruturas educativas. A BE apoia as atividades curriculares e extracurriculares dos alunos e professores, bem como projetos de promoção da leitura que envolvem a comunidade escolar.
Este documento proporciona 8 pasos para subir un video de YouTube a Blogger, que incluyen iniciar sesión en Blogger, crear una entrada, buscar y seleccionar el video deseado en YouTube y subirlo a Blogger.
Towards a Lightweight Multi-Cloud DSL for Elastic and Transferable Cloud-nati...Nane Kratzke
The document discusses a proposed lightweight multi-cloud domain-specific language (DSL) for defining elastic and transferable cloud-native applications. It begins by outlining the research context and motivation to avoid vendor lock-in and make applications portable across different cloud infrastructures. The presentation then describes requirements for a cloud programming language, including supporting containerized deployments, application scaling, lightweight definitions, multi-cloud operations, and infrastructure independence. It proposes a core DSL model and shows how it can be made platform agnostic. An evaluation demonstrates deploying an application to different clouds and runtime environments and transferring it between infrastructures. The DSL is found to fulfill the intended requirements within the limitations of its scope.
This document summarizes Fawaz Paraïso's Ph.D research on multi-cloud Platform as a Service (PaaS). It begins with an introduction to cloud computing models and the challenges of vendor lock-in and outages. It then reviews the state of the art in cloud interoperability and elastic applications. Paraïso's contribution is a generic architecture for a federated multi-cloud PaaS that provides portability, interoperability, and elasticity across heterogeneous cloud environments. The multi-cloud PaaS was evaluated using three software applications with results demonstrating improved elasticity and performance over single cloud platforms. Future work involves further monitoring of application performance and large-scale case studies.
The document summarizes a talk on cloud security featuring three speakers. Nikola Bozinovic of Frame discussed how their company provides a secure cloud platform for delivering virtual applications and desktops from the cloud. Matt Keil of Palo Alto Networks emphasized the importance of visibility, segmentation, and policy consistency for cloud security. Michael Schmidt of Nutonian described how their AI techniques can discover patterns in large security data sets that may indicate threats.
Cloud Computing: A Perspective on Next Basic Utility in IT World IRJET Journal
This document discusses cloud computing and its architecture. It begins with an introduction to cloud computing, defining it as a model that provides infrastructure, platforms, and software as services. The key characteristics and service models of cloud computing are described.
The document then discusses the architecture of cloud computing, including the layers of Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). It also describes the deployment models of private cloud, public cloud, community cloud, and hybrid cloud.
The document outlines several challenges of cloud computing, such as resource allocation and scheduling, cost optimization, processing time and speed, memory management, load balancing, security issues, fault
MapR 5.2: Getting More Value from the MapR Converged Data PlatformMapR Technologies
End of maintenance for MapR 4.x is coming in January, so now is a good time to plan your upgrade. Please join us to learn about the recent developments during the past year in the MapR Platform that will make the upgrade effort this year worthwhile.
Cloud computing standards and protocols r.nabatinabati
This document discusses cloud computing standards and protocols. It begins with an introduction to cloud computing and describes the cloud architecture and delivery models including Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). It then outlines several standards groups that are working on cloud standards including DMTF, ETSI, NIST, OGF, and OASIS. It provides examples of standards like OVF for packaging virtual appliances and CIMI for managing cloud infrastructure. In closing, the document emphasizes the importance of standards for interoperability and portability across multiple cloud platforms.
International Journal of Engineering Research and Development (IJERD)IJERD Editor
journal publishing, how to publish research paper, Call For research paper, international journal, publishing a paper, IJERD, journal of science and technology, how to get a research paper published, publishing a paper, publishing of journal, publishing of research paper, reserach and review articles, IJERD Journal, How to publish your research paper, publish research paper, open access engineering journal, Engineering journal, Mathemetics journal, Physics journal, Chemistry journal, Computer Engineering, Computer Science journal, how to submit your paper, peer reviw journal, indexed journal, reserach and review articles, engineering journal, www.ijerd.com, research journals,
yahoo journals, bing journals, International Journal of Engineering Research and Development, google journals, hard copy of journal
The document discusses various building blocks for Internet of Things (IoT) systems, including nodes, operating systems, networks, middleware and platforms. It outlines that initial IoT systems will likely be built from the bottom up using device nodes. It also notes that node operating systems and middleware are becoming more available. Ultimately, IoT platforms aim to make developing, deploying and managing large-scale IoT systems easier by providing interoperability across different systems through standards. The document provides examples and diagrams related to each building block.
Automation, Agility and NFV
The document discusses automation, agility, and network functions virtualization (NFV) in responding to over-the-top providers. It covers automation opportunities across the service lifecycle including order fulfillment, configuration, security, and analytics. Agility requires a DevOps approach using modeling languages and tools. NFV enables new services but faces challenges around integration and standards. Open source projects are important for NFV management and orchestration. Web giants like Facebook and Amazon use custom hardware and management tools rather than just commodity solutions.
This document discusses cloud computing concepts and applications in a military context. It defines cloud computing and describes common cloud themes like scalability, on-demand access, and location independence. It outlines business benefits like automation, data intensive computing, and accessibility from any device. The document also discusses DISA's focus on infrastructure/platform capabilities and lists several of DISA's cloud-related efforts.
The CPaaS.io platform allows to make task logic - e.g., for analytics - to be adaptively moved from the cloud to the edge of an IoT network. This presentation given at the first year review meeting in Tokyo on October 5, 2017 explains how.
Disclaimer:
This document has been produced in the context of the CPaaS.io project which is jointly funded by the European Commission (grant agreement n° 723076) and NICT from Japan (management number 18302). All information provided in this document is provided "as is" and no guarantee or warranty is given that the information is fit for any particular purpose. The user thereof uses the information at its sole risk and liability. For the avoidance of all doubts, the European Commission and NICT have no liability in respect of this document, which is merely representing the view of the project consortium. This document is subject to change without notice.
MPLS/SDN 2013 Intercloud Standardization and Testbeds - SillAlan Sill
This talk givens an overview of several multi-SDO and cross-SDO activities to promote and spur innovation in cloud computing. The focus is on API development and standardization, including testbeds, test use cases, and collaborative activities between organizations to create and carry out development and testing in this area. The focus is on work being pursued through the Cloud and Autonomic Computing Center at Texas Tech University, which is part of the US National Science Foundation's Industry/University Cooperative Research Center, and on work being done by standards organizations such as the Open Grid Forum, Distributed Management Task Force, and Telecommunications Management Forum in which the CAC@TTU is involved. A summary is also given of work to produce a new round of more detailed use cases suitable for testing by the US National Institute of Standards and Technology's Standards Acceleration to Jumpstart Adoption of Cloud Computing (SAJACC) working group, with brief mention also given to other related work going on in this area in other parts of the world. Background and other standards work is also mentioned.
Cluster computing involves connecting multiple computers together to work as a single system. Early cluster products included ARCnet in 1977 and VAXcluster in the 1980s. Clusters provide benefits like price/performance, availability through redundancy, and scalability by allowing addition of nodes. Key components of clusters are processors, memory, networking and software like operating systems, middleware and programming tools. Different types of clusters include high performance, load balancing and high availability clusters. Factors to consider for clusters include networking compatibility, software support, programming for the lowest spec node, and managing performance differences between nodes.
cncf overview and building edge computing using kubernetesKrishna-Kumar
Open Source India Conference 2018 Presentation to the general audience - not a deep technical talk. Narrated like a story for make it interesting......
What Does Real World Mass Adoption of Decentralized Tech Look Like?All Things Open
Presented at All Things Open 2023
Presented by Karl Mozurkewich - Storj
Title: What Does Real World Mass Adoption of Decentralized Tech Look Like?
Abstract: We delve into the transformative potential of decentralized technology. Beginning with a brief overview of the rise of centralization with the advent of the internet and the counter-shift marked by blockchain we explore the intrinsic characteristics of decentralized and distributed systems, such as trustless operations, peer-to-peer networks, and enterprise application scalability. Various sectors, including finance, supply chains, media and entertainment, data science and cloud infrastructure are on the brink of disruption. The societal implications are vast, with the potential for greater individual empowerment, a greener planet and more viable resource utilization, but concerns about data security persist.
Find more info about All Things Open:
On the web: https://www.allthingsopen.org/
Twitter: https://twitter.com/AllThingsOpen
LinkedIn: https://www.linkedin.com/company/all-things-open/
Instagram: https://www.instagram.com/allthingsopen/
Facebook: https://www.facebook.com/AllThingsOpen
Mastodon: https://mastodon.social/@allthingsopen
Threads: https://www.threads.net/@allthingsopen
2023 conference: https://2023.allthingsopen.org/
MapR 5.2: Getting More Value from the MapR Converged Community EditionMapR Technologies
Please join us to learn about the recent developments during the past year in the MapR Community Edition. In these slides, we will cover the following platform updates:
-Taking cluster monitoring to the next level with the Spyglass Initiative
-Real-time streaming with MapR Streams
-MapR-DB JSON document database and application development with OJAI
-Securing your data with access control expressions (ACEs)
We have the Bricks to Build Cloud-native Cathedrals - But do we have the mortar?Nane Kratzke
This is some input for a panel discussion about "Challenges of Cloud Computing-based Systems" I attend at the 9th International Conference on Cloud Computing, GRIDs, and Virtualization (CLOUD COMPUTING 2018) in Barcelona, Spain in February 2018.
Cloud-native applications (CNA) are build more and more often according to microservice and independent system architecture (ISA) approaches. ISA involves two architecture layers: the macro and the micro architecture layer. Software engineering outcomes on the micro layer are often distributed in a standardized form as self-contained deployment units (so called container images). There exist plenty of programming languages to implement these units: JAVA, C, C++, JavaScript, Python, R, PHP, Ruby, ... (this list is almost endless) But on the macro layer, one might mention TOSCA and little more. TOSCA is an OASIS deployment and orchestration standard language to describe a topology of cloud based web services, their components, relationships, and the processes that manage them. This works for static deployments. However, CNA are elastic, self-adaptive - almost the exact opposite of what can be defined efficiently using TOSCA. For these kind of scenarios one might mention Kubernetes or Docker Swarm as container orchestrators which are intentionally build to operate elastic services formed of containers. But these operating platforms do not provide expressive and pragmatic programming languages covering the macro layer of cloud-native applications.
So it seems there is a gap and the question arises, whether we need further (and what kind of) macro layer languages for CNA?
Review and Classification of Cloud Computing Researchiosrjce
IOSR journal of VLSI and Signal Processing (IOSRJVSP) is a double blind peer reviewed International Journal that publishes articles which contribute new results in all areas of VLSI Design & Signal Processing. The goal of this journal is to bring together researchers and practitioners from academia and industry to focus on advanced VLSI Design & Signal Processing concepts and establishing new collaborations in these areas.
Design and realization of microelectronic systems using VLSI/ULSI technologies require close collaboration among scientists and engineers in the fields of systems architecture, logic and circuit design, chips and wafer fabrication, packaging, testing and systems applications. Generation of specifications, design and verification must be performed at all abstraction levels, including the system, register-transfer, logic, circuit, transistor and process levels
Windows server 2016_overview-the_beginning_of_a_hybrid_cloud_inspired_journey...Sumit Dutt
The document summarizes a presentation about Windows Server 2016 and Microsoft's hybrid cloud strategy. The presentation covers key technologies in Windows Server 2016 like software defined networking and storage. It discusses how Windows Server 2016 allows for a unified cloud strategy across private and public clouds. It also highlights new capabilities in Windows Server 2016 like containers and how Microsoft's management tools provide visibility across hybrid cloud environments.
Towards a Lightweight Multi-Cloud DSL for Elastic and Transferable Cloud-nati...Nane Kratzke
The document discusses a proposed lightweight multi-cloud domain-specific language (DSL) for defining elastic and transferable cloud-native applications. It begins by outlining the research context and motivation to avoid vendor lock-in and make applications portable across different cloud infrastructures. The presentation then describes requirements for a cloud programming language, including supporting containerized deployments, application scaling, lightweight definitions, multi-cloud operations, and infrastructure independence. It proposes a core DSL model and shows how it can be made platform agnostic. An evaluation demonstrates deploying an application to different clouds and runtime environments and transferring it between infrastructures. The DSL is found to fulfill the intended requirements within the limitations of its scope.
This document summarizes Fawaz Paraïso's Ph.D research on multi-cloud Platform as a Service (PaaS). It begins with an introduction to cloud computing models and the challenges of vendor lock-in and outages. It then reviews the state of the art in cloud interoperability and elastic applications. Paraïso's contribution is a generic architecture for a federated multi-cloud PaaS that provides portability, interoperability, and elasticity across heterogeneous cloud environments. The multi-cloud PaaS was evaluated using three software applications with results demonstrating improved elasticity and performance over single cloud platforms. Future work involves further monitoring of application performance and large-scale case studies.
The document summarizes a talk on cloud security featuring three speakers. Nikola Bozinovic of Frame discussed how their company provides a secure cloud platform for delivering virtual applications and desktops from the cloud. Matt Keil of Palo Alto Networks emphasized the importance of visibility, segmentation, and policy consistency for cloud security. Michael Schmidt of Nutonian described how their AI techniques can discover patterns in large security data sets that may indicate threats.
Cloud Computing: A Perspective on Next Basic Utility in IT World IRJET Journal
This document discusses cloud computing and its architecture. It begins with an introduction to cloud computing, defining it as a model that provides infrastructure, platforms, and software as services. The key characteristics and service models of cloud computing are described.
The document then discusses the architecture of cloud computing, including the layers of Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). It also describes the deployment models of private cloud, public cloud, community cloud, and hybrid cloud.
The document outlines several challenges of cloud computing, such as resource allocation and scheduling, cost optimization, processing time and speed, memory management, load balancing, security issues, fault
MapR 5.2: Getting More Value from the MapR Converged Data PlatformMapR Technologies
End of maintenance for MapR 4.x is coming in January, so now is a good time to plan your upgrade. Please join us to learn about the recent developments during the past year in the MapR Platform that will make the upgrade effort this year worthwhile.
Cloud computing standards and protocols r.nabatinabati
This document discusses cloud computing standards and protocols. It begins with an introduction to cloud computing and describes the cloud architecture and delivery models including Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). It then outlines several standards groups that are working on cloud standards including DMTF, ETSI, NIST, OGF, and OASIS. It provides examples of standards like OVF for packaging virtual appliances and CIMI for managing cloud infrastructure. In closing, the document emphasizes the importance of standards for interoperability and portability across multiple cloud platforms.
International Journal of Engineering Research and Development (IJERD)IJERD Editor
journal publishing, how to publish research paper, Call For research paper, international journal, publishing a paper, IJERD, journal of science and technology, how to get a research paper published, publishing a paper, publishing of journal, publishing of research paper, reserach and review articles, IJERD Journal, How to publish your research paper, publish research paper, open access engineering journal, Engineering journal, Mathemetics journal, Physics journal, Chemistry journal, Computer Engineering, Computer Science journal, how to submit your paper, peer reviw journal, indexed journal, reserach and review articles, engineering journal, www.ijerd.com, research journals,
yahoo journals, bing journals, International Journal of Engineering Research and Development, google journals, hard copy of journal
The document discusses various building blocks for Internet of Things (IoT) systems, including nodes, operating systems, networks, middleware and platforms. It outlines that initial IoT systems will likely be built from the bottom up using device nodes. It also notes that node operating systems and middleware are becoming more available. Ultimately, IoT platforms aim to make developing, deploying and managing large-scale IoT systems easier by providing interoperability across different systems through standards. The document provides examples and diagrams related to each building block.
Automation, Agility and NFV
The document discusses automation, agility, and network functions virtualization (NFV) in responding to over-the-top providers. It covers automation opportunities across the service lifecycle including order fulfillment, configuration, security, and analytics. Agility requires a DevOps approach using modeling languages and tools. NFV enables new services but faces challenges around integration and standards. Open source projects are important for NFV management and orchestration. Web giants like Facebook and Amazon use custom hardware and management tools rather than just commodity solutions.
This document discusses cloud computing concepts and applications in a military context. It defines cloud computing and describes common cloud themes like scalability, on-demand access, and location independence. It outlines business benefits like automation, data intensive computing, and accessibility from any device. The document also discusses DISA's focus on infrastructure/platform capabilities and lists several of DISA's cloud-related efforts.
The CPaaS.io platform allows to make task logic - e.g., for analytics - to be adaptively moved from the cloud to the edge of an IoT network. This presentation given at the first year review meeting in Tokyo on October 5, 2017 explains how.
Disclaimer:
This document has been produced in the context of the CPaaS.io project which is jointly funded by the European Commission (grant agreement n° 723076) and NICT from Japan (management number 18302). All information provided in this document is provided "as is" and no guarantee or warranty is given that the information is fit for any particular purpose. The user thereof uses the information at its sole risk and liability. For the avoidance of all doubts, the European Commission and NICT have no liability in respect of this document, which is merely representing the view of the project consortium. This document is subject to change without notice.
MPLS/SDN 2013 Intercloud Standardization and Testbeds - SillAlan Sill
This talk givens an overview of several multi-SDO and cross-SDO activities to promote and spur innovation in cloud computing. The focus is on API development and standardization, including testbeds, test use cases, and collaborative activities between organizations to create and carry out development and testing in this area. The focus is on work being pursued through the Cloud and Autonomic Computing Center at Texas Tech University, which is part of the US National Science Foundation's Industry/University Cooperative Research Center, and on work being done by standards organizations such as the Open Grid Forum, Distributed Management Task Force, and Telecommunications Management Forum in which the CAC@TTU is involved. A summary is also given of work to produce a new round of more detailed use cases suitable for testing by the US National Institute of Standards and Technology's Standards Acceleration to Jumpstart Adoption of Cloud Computing (SAJACC) working group, with brief mention also given to other related work going on in this area in other parts of the world. Background and other standards work is also mentioned.
Cluster computing involves connecting multiple computers together to work as a single system. Early cluster products included ARCnet in 1977 and VAXcluster in the 1980s. Clusters provide benefits like price/performance, availability through redundancy, and scalability by allowing addition of nodes. Key components of clusters are processors, memory, networking and software like operating systems, middleware and programming tools. Different types of clusters include high performance, load balancing and high availability clusters. Factors to consider for clusters include networking compatibility, software support, programming for the lowest spec node, and managing performance differences between nodes.
cncf overview and building edge computing using kubernetesKrishna-Kumar
Open Source India Conference 2018 Presentation to the general audience - not a deep technical talk. Narrated like a story for make it interesting......
What Does Real World Mass Adoption of Decentralized Tech Look Like?All Things Open
Presented at All Things Open 2023
Presented by Karl Mozurkewich - Storj
Title: What Does Real World Mass Adoption of Decentralized Tech Look Like?
Abstract: We delve into the transformative potential of decentralized technology. Beginning with a brief overview of the rise of centralization with the advent of the internet and the counter-shift marked by blockchain we explore the intrinsic characteristics of decentralized and distributed systems, such as trustless operations, peer-to-peer networks, and enterprise application scalability. Various sectors, including finance, supply chains, media and entertainment, data science and cloud infrastructure are on the brink of disruption. The societal implications are vast, with the potential for greater individual empowerment, a greener planet and more viable resource utilization, but concerns about data security persist.
Find more info about All Things Open:
On the web: https://www.allthingsopen.org/
Twitter: https://twitter.com/AllThingsOpen
LinkedIn: https://www.linkedin.com/company/all-things-open/
Instagram: https://www.instagram.com/allthingsopen/
Facebook: https://www.facebook.com/AllThingsOpen
Mastodon: https://mastodon.social/@allthingsopen
Threads: https://www.threads.net/@allthingsopen
2023 conference: https://2023.allthingsopen.org/
MapR 5.2: Getting More Value from the MapR Converged Community EditionMapR Technologies
Please join us to learn about the recent developments during the past year in the MapR Community Edition. In these slides, we will cover the following platform updates:
-Taking cluster monitoring to the next level with the Spyglass Initiative
-Real-time streaming with MapR Streams
-MapR-DB JSON document database and application development with OJAI
-Securing your data with access control expressions (ACEs)
We have the Bricks to Build Cloud-native Cathedrals - But do we have the mortar?Nane Kratzke
This is some input for a panel discussion about "Challenges of Cloud Computing-based Systems" I attend at the 9th International Conference on Cloud Computing, GRIDs, and Virtualization (CLOUD COMPUTING 2018) in Barcelona, Spain in February 2018.
Cloud-native applications (CNA) are build more and more often according to microservice and independent system architecture (ISA) approaches. ISA involves two architecture layers: the macro and the micro architecture layer. Software engineering outcomes on the micro layer are often distributed in a standardized form as self-contained deployment units (so called container images). There exist plenty of programming languages to implement these units: JAVA, C, C++, JavaScript, Python, R, PHP, Ruby, ... (this list is almost endless) But on the macro layer, one might mention TOSCA and little more. TOSCA is an OASIS deployment and orchestration standard language to describe a topology of cloud based web services, their components, relationships, and the processes that manage them. This works for static deployments. However, CNA are elastic, self-adaptive - almost the exact opposite of what can be defined efficiently using TOSCA. For these kind of scenarios one might mention Kubernetes or Docker Swarm as container orchestrators which are intentionally build to operate elastic services formed of containers. But these operating platforms do not provide expressive and pragmatic programming languages covering the macro layer of cloud-native applications.
So it seems there is a gap and the question arises, whether we need further (and what kind of) macro layer languages for CNA?
Review and Classification of Cloud Computing Researchiosrjce
IOSR journal of VLSI and Signal Processing (IOSRJVSP) is a double blind peer reviewed International Journal that publishes articles which contribute new results in all areas of VLSI Design & Signal Processing. The goal of this journal is to bring together researchers and practitioners from academia and industry to focus on advanced VLSI Design & Signal Processing concepts and establishing new collaborations in these areas.
Design and realization of microelectronic systems using VLSI/ULSI technologies require close collaboration among scientists and engineers in the fields of systems architecture, logic and circuit design, chips and wafer fabrication, packaging, testing and systems applications. Generation of specifications, design and verification must be performed at all abstraction levels, including the system, register-transfer, logic, circuit, transistor and process levels
Windows server 2016_overview-the_beginning_of_a_hybrid_cloud_inspired_journey...Sumit Dutt
The document summarizes a presentation about Windows Server 2016 and Microsoft's hybrid cloud strategy. The presentation covers key technologies in Windows Server 2016 like software defined networking and storage. It discusses how Windows Server 2016 allows for a unified cloud strategy across private and public clouds. It also highlights new capabilities in Windows Server 2016 like containers and how Microsoft's management tools provide visibility across hybrid cloud environments.
Fast and energy-efficient eNVM based memory organisation at L3-L1 layers for ...
Defense
1. A Scalable Heterogeneous
Software Architecture for the
Telecommunication Cloud
Pascal Potvin
École de Technologie Supérieure, Université du Québec
Montréal, April 26, 2016
Master Thesis in Software Engineering
9. 2016-04-26 9
2009
Google is not virtualized, and virtualization is
not sufficient to qualify as a cloud.
(Erich Clementi, head of IBM cloud computing efforts)
10. 2016-04-26 10
2009
Virtualization is Not the Cloud.
(Rackspace white paper)
Google is not virtualized, and virtualization is
not sufficient to qualify as a cloud.
(Erich Clementi, head of IBM cloud computing efforts)
16. Telecommunication Cloud
• More Stringent Requirements than IT Cloud
– Quality of Service (QoS)
– Interoperability
– Reliability
– Usage of Stateful protocols e.g. SIP
2016-04-26 16
Cloud computing is a model for enabling ubiquitous, convenient, on-
demand network access to a shared pool of configurable computing
resources (e.g., networks, servers, storage, applications, and services)
that can be rapidly provisioned and released with minimal
management effort or service provider interaction.
(Mell and Grance, 2011)
18. Problem Statement & Research Questions
• Telecommunication Cloud
– Can we apply IT cloud principles to the telecommunication cloud?
• Heterogeneous Deployments
– How can it be done?
• Cloud Programming Paradigm
– Which cloud architectural patterns are applicable to the telco cloud?
2016-04-26 18
19. Objectives
• Cloud-native software architecture for telco
– Select architectural patterns
– Define, implement and evaluate architecture
• Elasticity
– While providing QoS
– Distributing application state while minimizing impact on latency
• Heterogeneous deployments
2016-04-26 19
21. Cloud and Telco Scalability
2016-04-26 21
Elasticity QoS Statefulness Interoperability Heterogeneity Patterns
Lu et al., 2013 Virtualization
only
Yang et al.,
2011
On group level HSS Only
Bellavista,
Corradi et
Foschini, 2013
On group level Presence Server
Only
Carella et al.,
2014
On group level
22. Cloud and QoS
2016-04-26 22
Elasticity QoS Statefulness Interoperability Heterogeneity Patterns
Turner, 2013 E-commerce
On average
/
Verma et al.,
2015
/
23. Heterogeneous Cloud
2016-04-26 23
Elasticity QoS Statefulness Interoperability Heterogeneity Patterns
Xu, Wang et Li,
2011
Job based Various Size
Crago et al.,
2011
CPU / GPU
Lee, Chun et
Katz, 2011
Job based Fairness CPU / GPU
24. Cloud Patterns
2016-04-26 24
• Horizontal Scaling (in/out) and Auto-Scaling
• Microservices and the Actor Model
• Sharding
• MapReduce
• Collocate
26. Pattern: Horizontal Scaling
• Adding more of the same compute resource to increase
capacity (Scale out)
– Easy with stateless http… needs some consideration for session based
protocols
2016-04-26 26
30. Pattern: Actor Model
• Serving one instance at a time (High Granularity)
• Actors can:
– Instantiate other actors
– Store internal state
– Asynchronously communicate with other actors
2016-04-26 30
31. Pattern: Sharding
• Scaling by creating domains serving different customers or
end users.
• Consistent Hashing algo. & Rendezvous algo. Considered
– Rendezvous selected for least state synchronization required
2016-04-26 31
HSS
URI: A[…] to F[…]
Core IMS
HSS
URI: G[…] to L[…]
Core IMS
HSS
URI: M[…] to R[…]
Core IMS
HSS
URI: S[…] to Z[…]
Core IMS
Shard aware Load Balancer
32. Pattern: Mapreduce
• Variants are possible
– Usage of Classical Mapreduce for Logging.
2016-04-26 32
Input Files Map Shuffle & Sort Reduce Output
39. Architecture
2016-04-26 39
Pouch Type 1
Pouch Type 1
Pouch Type 1
Unit 1
Unit 1
XaaS
Unit 1
Unit 1
Unit 1
Unit 2
Pouch Type 1
Pouch Type 1
Pouch Type 3
Unit 1
Unit 1
Platform Framework
(incl. CMW, SDS, IDS client, …)
Unit 5
Unit 1
Unit 1
Unit 6
Pouch Type 1
Pouch Type 1
Pouch Type 2
Unit 1
Unit 1
Platform Framework
(incl. CMW, SDS, IDS client, …)
Unit 3
Unit 1
Unit 1
Unit 4
Meta Management
and Orchestrator
Node Selector
Service
Deployment Database
Service
Load Distribution
Service
Element Manager
Information Distribution
Service
Platform Framework
(incl. CMW, SDS, IDS client, …)
Persistence Service
Log Gathering Service
40. Architecture
2016-04-26 40
Element Manager Persistence Service Log Gathering Service
Node Selector
Service
Deployment Database
Service
Information Distribution
Service
Meta Management
and Orchestrator
Load Distribution
Service
Platform Framework
(incl. CMW, SDS, IDS client, …)
Units
Instantiation
Traffic
Distribution
Support Services
41. Microservices and Collocate
2016-04-26 41
Pouch Type 1
Pouch Type 1
Pouch Type 1
Unit 1
Unit 1
Meta Management
and Orchestrator
Node Selector
Service
Deployment Database
Service
Load Distribution
Service
Element Manager
Information Distribution
Service
XaaS
Platform Framework
(incl. CMW, SDS, IDS client, …)
Unit 1
Unit 1
Unit 1
Unit 2
Pouch Type 1
Pouch Type 1
Pouch Type 3
Unit 1
Unit 1
Platform Framework
(incl. CMW, SDS, IDS client, …)
Unit 5
Unit 1
Unit 1
Unit 6
Pouch Type 1
Pouch Type 1
Pouch Type 2
Unit 1
Unit 1
Platform Framework
(incl. CMW, SDS, IDS client, …)
Unit 3
Unit 1
Unit 1
Unit 4
Persistence Service
Log Gathering Service
42. Horizontal Scaling and Auto-Scaling
2016-04-26 42
Pouch Type 1
Pouch Type 1
Pouch Type 1
Unit 1
Unit 1
Meta Management
and Orchestrator
Node Selector
Service
Deployment Database
Service
Load Distribution
Service
Element Manager
Information Distribution
Service
XaaS
Platform Framework
(incl. CMW, SDS, IDS client, …)
Unit 1
Unit 1
Unit 1
Unit 2
Pouch Type 1
Pouch Type 1
Pouch Type 3
Unit 1
Unit 1
Platform Framework
(incl. CMW, SDS, IDS client, …)
Unit 5
Unit 1
Unit 1
Unit 6
Pouch Type 1
Pouch Type 1
Pouch Type 2
Unit 1
Unit 1
Platform Framework
(incl. CMW, SDS, IDS client, …)
Unit 3
Unit 1
Unit 1
Unit 4
Persistence Service
Log Gathering Service
Scaling based on:
• CPU
• Memory
• Bandwidth
• # of Units
Hysteresis with
upper and lower
bounds.
43. Distribution of State
2016-04-26 43
Pouch Type 1
Pouch Type 1
Pouch Type 1
Unit 1
Unit 1
Meta Management
and Orchestrator
Node Selector
Service
Deployment Database
Service
Load Distribution
Service
Element Manager
Information Distribution
Service
XaaS
Platform Framework
(incl. CMW, SDS, IDS client, …)
Unit 1
Unit 1
Unit 1
Unit 2
Pouch Type 1
Pouch Type 1
Pouch Type 3
Unit 1
Unit 1
Platform Framework
(incl. CMW, SDS, IDS client, …)
Unit 5
Unit 1
Unit 1
Unit 6
Pouch Type 1
Pouch Type 1
Pouch Type 2
Unit 1
Unit 1
Platform Framework
(incl. CMW, SDS, IDS client, …)
Unit 3
Unit 1
Unit 1
Unit 4
Persistence Service
Log Gathering Service
44. Mapreduce (for logging purpose)
2016-04-26 44
Pouch Type 1
Pouch Type 1
Pouch Type 1
Unit 1
Unit 1
Meta Management
and Orchestrator
Node Selector
Service
Deployment Database
Service
Load Distribution
Service
Element Manager
Information Distribution
Service
XaaS
Platform Framework
(incl. CMW, SDS, IDS client, …)
Unit 1
Unit 1
Unit 1
Unit 2
Pouch Type 1
Pouch Type 1
Pouch Type 3
Unit 1
Unit 1
Platform Framework
(incl. CMW, SDS, IDS client, …)
Unit 5
Unit 1
Unit 1
Unit 6
Pouch Type 1
Pouch Type 1
Pouch Type 2
Unit 1
Unit 1
Platform Framework
(incl. CMW, SDS, IDS client, …)
Unit 3
Unit 1
Unit 1
Unit 4
Persistence Service
Log Gathering Service
46. Simplistic IMS Demonstrator
2016-04-26 46
Terminating Side
A
T
M
A
Alice
Bob
Originating Side
SIP Msg. UnitInter-Unit Link
SIPh C
DiahH
Node Selector
Service
Diah
T
H
CSIPh
Service Req. Links
HSS
48. Hybrid Cloud
Apcera (blue) and Open Stack (green)
2016-04-26 48
M
M
XaaS
Platform Framework
(incl. CMW, SDS, IDS client, …)
AC
T
H
Diah
P. F. (…)
LDS
SDS
P. F. (…)
SIPh
P. F. (…)
M
O
Platform Framework
(incl. CMW, SDS, IDS client, …)
DB
Meta Management
and Orchestrator
Node Selector
Service
Deployment Database
Service
Load Distribution
Service
Element Manager
Information Distribution
Service
Persistence Service
Log Gathering Service
49. Raspberry Pi
2016-04-26 49
XaaS
Raspberry Pi board
Raspberry Pi board
1st Raspberry Pi board
Platform Framework
(incl. CMW, SDS, IDS client, …)
Meta Management
and Orchestrator
C H
DB
Deployment Database
Service
Platform Framework
(incl. CMW, SDS,
IDS client, …)
SIPh
Element Manager
Information Distribution
Service
T
A M
Raspberry Pi boardsNAS
O
SDS
Node Selector
Service
Load Distribution
Service
Persistence Service
Log Gathering Service
57. Conclusion
• Cloud-native software architecture for telco
– Select architectural patterns
– Define, implement and evaluate architecture
• Elasticity
– While providing QoS
– Distributing application state while minimizing impact on latency
• Heterogeneous deployments
2016-04-26 57
58. Contributions
• Actor model for the telecommunication
– Provide scalability and elasticity
• Pouch concept
– Abstraction of platform for the application (heterogeneous
deployments)
• Proposed Heterogeneous Scalable Software Architecture
providing QoS
• Proposed Mechanism to distribute state information
• Built a POC showing how IMS can be re-architectured
• Published 3 conference papers
2016-04-26 58
59. Future Research Direction
• Multi-agent architecture for telecommunication?
• Finer grained QoS regulation?
• Machine Learning insuring QoS and higher cloud utilization?
2016-04-26 59
Our main objective is to develop a cloud-native software architecture for telecommunication
systems and implement this architecture in order to evaluate its merits. In order to do so we
will determine if we can re-architecture IMS in order to provide its functionality in an ondemand,
per subscriber and per service basis through the usage of the actor model (which can
be seen as a specialization of the Microservices pattern). To our knowledge no approach
proposes the same thing at this point in time.
Our specific objectives to accomplish this objective consist of the following:
O1. Propose a mechanism to efficiently allocate computing resources through multiple cloud
platforms in order to prevent overloading of computing resources and the resulting adverse
impact on QoS. This mechanism will implement an elastic and automatic scalability scheme.
To the best of our knowledge, no research has addressed this question in the
telecommunication sector.
O2. Propose a mechanism to allow for application state information to be distributed on
compute instances, providing resiliency while minimizing impact on latency.
O3. Propose an architecture providing portability between multiple cloud environments for
telecommunication applications, enabling a solution-oriented, heterogeneous cloud
deployment. The deployment could be on pools of bare-metal servers, IaaS, Platform as a
Service (PaaS) or a mix of these. The architecture should enable communication between
services or application components even if distributed on different platforms.
O4. Implement the architecture and measure its characteristics and to validate its
performance and compare it to a traditional telecommunication node-based deployment.
O2. Propose a mechanism to allow for application state information to be distributed on compute instances, providing resiliency while minimizing impact on latency.
O1. Propose a mechanism to efficiently allocate computing resources through multiple cloud platforms in order to prevent overloading of computing resources and the resulting adverse impact on QoS. This mechanism will implement an elastic and automatic scalability scheme. To the best of our knowledge, no research has addressed this question in the telecommunication sector.
O3. Propose an architecture providing portability between multiple cloud environments for telecommunication applications, enabling a solution-oriented, heterogeneous cloud deployment. The deployment could be on pools of bare-metal servers, IaaS, Platform as a Service (PaaS) or a mix of these. The architecture should enable communication between services or application components even if distributed on different platforms.