DOCSLIB.ORG

Guide to the Open Cloud Current Trends and Open Source Projects

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Guide to the Open Cloud Current trends and open source projects November 2016 AUTHORS Libby Clark and Mark Hinkle The Linux Foundation www.linuxfoundation.org Contents Introduction 3 What is the Open Cloud Today, Why It’s Important, and How It’s Advancing 5 Emerging Trends 6 Cloud Native Applications 6 Containers 7 Unikernels 7 Why is the Open Cloud Important? 7 Profile Methodology 9 Profiles 11 Infrastructure as a Service (IaaS) 11 Platform as a Service (PaaS) 12 Virtualization, Containers and Cloud Operating Systems 13 Micro or Minimalist OSes 13 Virtualization 14 Management and Automation 15 Unikernels 17 DevOps CI/CD 19 Complete CI/CD cycle 19 Configuration management 20 Logging and Monitoring 21 Software-Defined Networking (SDN) 22 Networking for containers 23 Software-Defined Storage 24 2 Guide to the Open Cloud: Current trends and open source projects Introduction This third annual Guide to the Open Cloud aims to help companies stay informed on the latest open source cloud technologies and trends. The Linux Foundation’s cloud experts have curated a list of the most useful, influential, and promising open source projects with which IT managers and practitioners can build, manage, and monitor their current and future mission-critical cloud resources. In doing so, we’re also helping companies identify projects they can best leverage for external R&D through strategic open source participation. Contributing knowledge and code to open source projects not only helps companies meet their business objectives, but it creates thriving communities that keep projects strong and relevant over time, advances the technology, and benefits the entire open source cloud ecosystem. Cloud computing is the cornerstone of the digital economy. Companies across industries now use the cloud—private, public or somewhere in between—to deliver their products and services. Forty-one percent of all enterprise workloads are currently running in some type of public or private cloud1. That number is expected to rise to 60 percent by mid-2018. And some 95 percent of companies are at least experimenting in the cloud2. Enterprises are continuing to shift workloads to the cloud as their expertise and experience with the technology increases. From banking and finance to automotive and healthcare, companies are facing the reality that they’re now in the technology business. In this new reality, cloud strategies can make or break an organization’s market success. And successful cloud strategies are built on Linux and open source software. Some of the most successful public companies today are built around cloud-native applications—a fashionable term that simply means they’re designed to run in the cloud. Netflix, Facebook, LinkedIn, Twitter, and Amazon have all leveraged open source components within a distributed, microservices-based architecture to quickly deliver new products and services that are cost-effective and responsive to market demands and changes. By breaking applications up into microservices, or distinct, single-purpose services that are loosely coupled with dependencies and explicitly described through service endpoints, they have significantly increased the overall agility and maintainability of applications and used that to gain competitive advantage. 1 451 Research, “Voice of the Enterprise: Cloud Transformation - Workloads and Key Projects,” Sept. 1, 2016. 2 RightScale, “2016 State of the Cloud Report,” January, 2016. 3 Guide to the Open Cloud: Current trends and open source projects The rest of the market has scrambled to replicate this architecture and approach, cobbling together their own solutions using custom scripts and open source software—often using the open source versions of these web giants’ own infrastructure (ie Google’s borg, which became Kubernetes; Twitter’s Mesos project, VMware’s Cloud Foundry, etc.) This experimentation has set off a chain of innovation with four notable trends, still playing out today: • Increasing consumption of public cloud resources • Adoption of container technologies like Docker and others (Fifty-three percent of organizations are either investigating or using containers in development or in production3.) • The rise of DevOps as the most effective method for application delivery in the cloud • An explosion in available open source tooling as user companies like Walmart and Capital One release their management software under open source licenses. While deployment and management remain a challenge, microservices architecture is now becoming mainstream. In a recent Nginx survey4 of 1,800 IT professionals, 44 percent said they’re using microservices in development or in production. Adoption was highest among small and medium-sized businesses. Not coincidentally, the use of public cloud is also predominant among SMBs5, which are more nimble and faster to respond to market changes than large enterprises with legacy applications and significant on-premise infrastructure investments. Many reports tout hybrid cloud as a fast-growing segment of the cloud. Demand is growing at a compound rate of 27 percent, “far outstripping growth of the overall IT market,” according to researcher MarketsandMarkets6. And IDC predicts that more than 80 percent of enterprise IT organizations will commit to hybrid cloud architectures by 20177. However, this growth is happening predominantly among large enterprises with legacy applications and the budget and staffing to build private clouds. They turn to cloud for storage and scale-out capabilities, but keep most critical workloads on premise. In the mid-market, hybrid cloud adoption stands at less than 10 percent, according to 451 Research. Hybrid cloud is, then, a good transition point for legacy workloads and experimenting with cloud implementation. But it suffers from several challenges with more advanced cloud implementations, including management complexity and cost. “Most organizations are already using a combination of cloud services from different cloud providers. While public cloud usage will continue to increase, the use of private cloud and hosted private cloud services is also expected to increase at least through 2017. The increased use of multiple public cloud providers, plus growth in various types of private cloud services, will create a multi-cloud environment in most enterprises and a need to coordinate cloud usage using hybrid scenarios. 3 Cloud Foundry, ”Hope Vs. Reality: Containers in 2016,” June 2016. 4 Nginx, “The Future of App Development and Delivery,” March 2016. 5 RightScale, “2016 State of the Cloud Report,” January, 2016. 6 Wall Street Journal, “Special Report: CIOs Say Hybrid Cloud Takes Off,” Oct. 2015. 7 IDC, “IDC FutureScape: Worldwide Cloud 2016 Predictions — Mastering the Raw Material of Digital Transformation,” 2016. 4 Guide to the Open Cloud: Current trends and open source projects “Although hybrid cloud scenarios will dominate, there are many challenges that inhibit working hybrid cloud implementations. Organizations that are not planning to use hybrid cloud indicated a number of concerns, including: integration challenges, application incompatibilities, a lack of management tools, a lack of common APIs and a lack of vendor support,” according to Gartner’s 2016 Public Cloud Services worldwide forecast.8 Over the long term, workloads are shifting away from hybrid cloud to a public cloud market dominated by providers like AWS, Azure, and Google Compute. “The share of enterprise workloads moved to the public cloud is expected to triple over the next five years,” from 16 percent to 41.3 percent of workloads running in the public cloud, according to a recent JP Morgan survey of enterprise CIOs9. Among this group, 13 percent said they view AWS as “intrinsic to future growth.” AWS still very much dominates the cloud industry and has continued to grow at an incredible rate. It looks like hosted services are going to be a huge second line of business for the company. Based on its July 2016 earnings release, Amazon’s web business is on pace to be a $9 billion business this year.10 The shift to the public cloud will continue to accelerate as costs come down and security concerns are allayed. Security is still a top concern among companies considering moving workloads to the public cloud, according to Gartner, despite a strong track record of security and increased transparency from cloud providers. Rather, security is still an issue largely due to companies’ inexperience and improper use of cloud services. As companies gain more experience with public cloud use, security concerns will become less of a hindrance. As cloud adoption grows, open source technologies will continue to be the source of innovation and the foundation for new markets and ecosystems. Each of the projects listed in this report is actively involved in creating the future of IT infrastructure on which companies will deliver their products and services, in the coming year and beyond. Let this report be your guide to become familiar with these projects, the categories of technology in which they are influential, and the ways in which they can help companies remain competitive in this age of digital transformation. What is the open cloud today, why it’s important, and how it’s advancing Many companies are still building their own cloud stacks—assembling open source components to run a private or hybrid infrastructure. And you’ll find these components on our list, as they were in the past. But the drive is no longer to build enterprise alternatives to large, proprietary public clouds. Instead, more companies are turning to public cloud to run their applications and services, and as they do so the nature of the open cloud today is changing. 8 Gartner, “Forecast Analysis: Public Cloud Services, Worldwide, 2Q16 Update,” Sept., 2016. 9 Business Insider, “CIOs See Momentous Shift in Public Cloud Usage,” April 2016. 10 Amazon, “Q2 2016 Financial Results,” July 2016. 11 Gartner, “Gartner Says Worldwide Public Cloud Services Market to Grow 17 Percent in 2016,” Sept. 2016. 5 Guide to the Open Cloud: Current trends and open source projects As cloud computing continues to evolve, the infrastructure is becoming more flexible and programmable.
Recommended publications
  • Report on the 2020 FOSS Contributor Survey

    Report on the 2020 FOSS Contributor Survey

    Report on the 2020 FOSS Contributor Survey The Linux Foundation & The Laboratory for Innovation Science at Harvard Frank Nagle Harvard Business School David A. Wheeler The Linux Foundation Hila Lifshitz-Assaf New York University Haylee Ham Jennifer L. Hoffman Laboratory for Innovation Science at Harvard Acknowledgments This report and the research behind it would not have been possible without the leadership of the Core Infrastructure Initiative’s Advisory Committee, composed of Josh Corman, Steve Lipner, Audris Mockus, Henning Piezunka, and Sam Ransbotham. Frank Nagle would also like to thank his fellow co-directors of the Core Infrastructure Initiative, Jim Zemlin at the Linux Foundation and Karim Lakhani at the Laboratory for Innovation Science at Harvard, for their counsel and direction throughout this project. Gratitude and thanks to Michael Dolan and Kate Stewart at the Linux Foundation for their ongoing commitment to this undertaking. Thank you to James Dana for laying the initial groundwork for this survey. Finally — and perhaps, most importantly — thank you to all the individuals who contribute to FOSS projects. Without their tireless efforts, our core digital infrastructure and the feats enabled by it would not be sustainable. REVISED: This report has been updated since its original release on 8 December 2020. This second version, released on 10 December 2020, corrects errors found in the original text and graphics. Contents Executive Summary 4 Introduction 7 Methodology 9 Overview of Findings 10 Demographics 10 Figure 1: Gender
  • The Next Generation Cloud: the Rise of the Unikernel

    The Next Generation Cloud: the Rise of the Unikernel

    The Next Generation Cloud: The Rise of the Unikernel A Xen Project publication April 2015 xenproject.org Docker and Linux container technologies dominate headlines today as a powerful, easy way to package applications, especially as cloud computing becomes more mainstream. While still a work-in-progress, they offer a simple, clean and lean way to distribute application workloads. With enthusiasm continuing to grow for container innovations, a related technology called unikernels is also beginning to attract attention. Known also for their ability to cleanly separate functionality at the component level, unikernels are developing a variety of new approaches to deploy cloud services. Traditional operating systems run multiple applications on a single machine, managing resources and isolating applications from one another. A unikernel runs a single application on a single virtual machine, relying instead on the hypervisor to isolate those virtual machines. Unikernels are constructed by using “library operating systems,” from which the developer selects only the minimal set of services required for an application to run. These sealed, fixed-purpose images run directly on a hypervisor without an intervening guest OS such as Linux. As well as improving upon container technologies, unikernels are also able to deliver impressive flexibility, speed and versatility for cross-platform environments, big data analytics and scale-out cloud computing. Like container-based solutions, this technology fulfills the promise of easy deployment, but unikernels also offer an extremely tiny, specialized runtime footprint that is much less vulnerable to attack. There are several up-and-coming open source projects to watch this year, including ClickOS, Clive, HaLVM, LING, MirageOS, Rump Kernels and OSv among others, with each of them placing emphasis on a different aspect of the unikernel approach.
  • What Is Bluemix

    What Is Bluemix

    IBM Brings Bluemix to Developers! This document has been prepared for the TMForum Hackathon in Nice, France. The first section of this document shares Bluemix related notes, and it is followed by notes appropriate for viewing content from exposed APIs (provided by TMForum and FIware) then you see the node flows that are available for you. IBM® Bluemix™ is an open-standard, cloud-based platform for building, managing, and running apps of all types, such as web, mobile, big data, and smart devices. Capabilities include Java, mobile back-end development, and application monitoring, as well as features from ecosystem partners and open source—all provided as-a-service in the cloud. Get started with Bluemix: ibm.biz/LearnBluemix Sign up for Bluemix: https://ibm.biz/sitefrbluemix Getting started with run times: http://bluemix.net/docs/# View the catalog and select the mobile cloud boilerplate: http://bluemix.net/#/store/cloudOEPaneId=store Tap into the Internet of Things: http://bluemix.net/#/solutions/solution=internet_of_things Bluemix tutorial in Open Classroom: http://openclassrooms.com/courses/deployez-des-applications- dans-le-cloud-avec-ibm-bluemix This table below can be used for general enablement. It is been useful to developers are previous hackathons. Source Code : Quick Start Technical Asset Name URL/Mobile App Technical Asset Description Guide Uses Node.js runtime, Internet Connected Home Automation ibm.biz/ATTconnhome2 of Things boilerplate, Node-RED ibm.biz/ATTconnhome2qs App editor and MQTT protocol Uses Node.js runtime, Connected
  • Flexible and Integrated Resource Management for Iaas Cloud Environments Based on Programmability

    Flexible and Integrated Resource Management for Iaas Cloud Environments Based on Programmability

    UNIVERSIDADE FEDERAL DO RIO GRANDE DO SUL INSTITUTO DE INFORMÁTICA PROGRAMA DE PÓS-GRADUAÇÃO EM COMPUTAÇÃO JULIANO ARAUJO WICKBOLDT Flexible and Integrated Resource Management for IaaS Cloud Environments based on Programmability Thesis presented in partial fulfillment of the requirements for the degree of Doctor of Computer Science Advisor: Prof. Dr. Lisandro Z. Granville Porto Alegre December 2015 CIP — CATALOGING-IN-PUBLICATION Wickboldt, Juliano Araujo Flexible and Integrated Resource Management for IaaS Cloud Environments based on Programmability / Juliano Araujo Wick- boldt. – Porto Alegre: PPGC da UFRGS, 2015. 125 f.: il. Thesis (Ph.D.) – Universidade Federal do Rio Grande do Sul. Programa de Pós-Graduação em Computação, Porto Alegre, BR– RS, 2015. Advisor: Lisandro Z. Granville. 1. Cloud Computing. 2. Cloud Networking. 3. Resource Man- agement. I. Granville, Lisandro Z.. II. Título. UNIVERSIDADE FEDERAL DO RIO GRANDE DO SUL Reitor: Prof. Carlos Alexandre Netto Vice-Reitor: Prof. Rui Vicente Oppermann Pró-Reitor de Pós-Graduação: Prof. Vladimir Pinheiro do Nascimento Diretor do Instituto de Informática: Prof. Luis da Cunha Lamb Coordenador do PPGC: Prof. Luigi Carro Bibliotecária-chefe do Instituto de Informática: Beatriz Regina Bastos Haro “Life is like riding a bicycle. To keep your balance you must keep moving.” —ALBERT EINSTEIN ACKNOWLEDGMENTS First of all, I would like to thank my parents and brother for the unconditional support and example of determination and perseverance they have always been for me. I am aware that time has been short and joyful moments sporadic, but if today I am taking one more step ahead this is due to the fact that you always believed in my potential and encourage me to move on.
  • Deliverable No. 5.3 Techniques to Build the Cloud Infrastructure Available to the Community

    Deliverable No. 5.3 Techniques to Build the Cloud Infrastructure Available to the Community

    Deliverable No. 5.3 Techniques to build the cloud infrastructure available to the community Grant Agreement No.: 600841 Deliverable No.: D5.3 Deliverable Name: Techniques to build the cloud infrastructure available to the community Contractual Submission Date: 31/03/2015 Actual Submission Date: 31/03/2015 Dissemination Level PU Public X PP Restricted to other programme participants (including the Commission Services) RE Restricted to a group specified by the consortium (including the Commission Services) CO Confidential, only for members of the consortium (including the Commission Services) Grant Agreement no. 600841 D5.3 – Techniques to build the cloud infrastructure available to the community COVER AND CONTROL PAGE OF DOCUMENT Project Acronym: CHIC Project Full Name: Computational Horizons In Cancer (CHIC): Developing Meta- and Hyper-Multiscale Models and Repositories for In Silico Oncology Deliverable No.: D5.3 Document name: Techniques to build the cloud infrastructure available to the community Nature (R, P, D, O)1 R Dissemination Level (PU, PP, PU RE, CO)2 Version: 1.0 Actual Submission Date: 31/03/2015 Editor: Manolis Tsiknakis Institution: FORTH E-Mail: [email protected] ABSTRACT: This deliverable reports on the technologies, techniques and configuration needed to install, configure, maintain and run a private cloud infrastructure for productive usage. KEYWORD LIST: Cloud infrastructure, OpenStack, Eucalyptus, CloudStack, VMware vSphere, virtualization, computation, storage, security, architecture. The research leading to these results has received funding from the European Community's Seventh Framework Programme (FP7/2007-2013) under grant agreement no 600841. The author is solely responsible for its content, it does not represent the opinion of the European Community and the Community is not responsible for any use that might be made of data appearing therein.
  • A Linux in Unikernel Clothing Lupine

    A Linux in Unikernel Clothing Lupine

    A Linux in Unikernel Clothing Hsuan-Chi Kuo+, Dan Williams*, Ricardo Koller* and Sibin Mohan+ +University of Illinois at Urbana-Champaign *IBM Research Lupine Unikernels are great BUT: Unikernels lack full Linux Support App ● Hermitux: supports only 97 system calls Kernel LibOS + App ● OSv: ○ Fork() , execve() are not supported Hypervisor Hypervisor ○ Special files are not supported such as /proc ○ Signal mechanism is not complete ● Small kernel size ● Rumprun: only 37 curated applications ● Heavy ● Fast boot time ● Community is too small to keep it rolling ● Inefficient ● Improved performance ● Better security 2 Can Linux behave like a unikernel? 3 Lupine Linux 4 Lupine Linux ● Kernel mode Linux (KML) ○ Enables normal user process to run in kernel mode ○ Processes can still use system services such as paging and scheduling ○ App calls kernel routines directly without privilege transition costs ● Minimal patch to libc ○ Replace syscall instruction to call ○ The address of the called function is exported by the patched KML kernel using the vsyscall ○ No application changes/recompilation required 5 Boot time Evaluation Metrics Image size Based on: Unikernel benefits Memory footprint Application performance Syscall overhead 6 Configuration diversity ● 20 top apps on Docker hub (83% of all downloads) ● Only 19 configuration options required to run all 20 applications: lupine-general 7 Evaluation - Comparison configurations Lupine Cloud Operating Systems [Lupine-base + app-specific options] OSv general Linux-based Unikernels Kernel for 20 apps
  • Tracking Known Security Vulnerabilities in Third-Party Components

    Tracking Known Security Vulnerabilities in Third-Party Components

    Tracking known security vulnerabilities in third-party components Master’s Thesis Mircea Cadariu Tracking known security vulnerabilities in third-party components THESIS submitted in partial fulfillment of the requirements for the degree of MASTER OF SCIENCE in COMPUTER SCIENCE by Mircea Cadariu born in Brasov, Romania Software Engineering Research Group Software Improvement Group Department of Software Technology Rembrandt Tower, 15th floor Faculty EEMCS, Delft University of Technology Amstelplein 1 - 1096HA Delft, the Netherlands Amsterdam, the Netherlands www.ewi.tudelft.nl www.sig.eu c 2014 Mircea Cadariu. All rights reserved. Tracking known security vulnerabilities in third-party components Author: Mircea Cadariu Student id: 4252373 Email: [email protected] Abstract Known security vulnerabilities are introduced in software systems as a result of de- pending on third-party components. These documented software weaknesses are hiding in plain sight and represent the lowest hanging fruit for attackers. Despite the risk they introduce for software systems, it has been shown that developers consistently download vulnerable components from public repositories. We show that these downloads indeed find their way in many industrial and open-source software systems. In order to improve the status quo, we introduce the Vulnerability Alert Service, a tool-based process to track known vulnerabilities in software projects throughout the development process. Its usefulness has been empirically validated in the context of the external software product quality monitoring service offered by the Software Improvement Group, a software consultancy company based in Amsterdam, the Netherlands. Thesis Committee: Chair: Prof. Dr. A. van Deursen, Faculty EEMCS, TU Delft University supervisor: Prof. Dr. A.
  • Kernel Validation with Kselftest Shuah Khan, Kernel Maintainer and Fellow, the Linux Foundation

    Kernel Validation with Kselftest Shuah Khan, Kernel Maintainer and Fellow, the Linux Foundation

    Kernel Validation With Kselftest Shuah Khan, Kernel Maintainer and Fellow, The Linux Foundation • Why do we test? • Kinds of testing/tests ... – Unit, developer, regression, integration • Linux kernel testing philosophy – Developer and community driven testing – Reliance on community and users • Linux kernel release cycle – Time based - not feature based – Continuous and parallel development/testing model • Linux kernel testing and validation – Writing tests • Kernel test frameworks - Kselftest & KUnit – Developer testing • Kselftest, KUnit and others. – Regression testing • Kselftest, KUnit and others. • Linux kernel testing and validation – Continuous Integration testing • Static analysis tools (sparse, smatch, coccicheck etc.) • Dynamic analysis tools (fuzzers, syzbot etc.) • Where does this all happen? – Developer test systems – Continuous Integration Rings • Kernel CI Dashboard — Home • 0-Day - Boot and Performance issues • 0-Day - Build issues • Linaro QA • Buildbot • Hulk Robot • What is tested? – Kernel repositories: • linux mainline • linux-next • developer git repositories – Active kernel releases • Basic testing – Boot and usage test – Run basic sanity tests • Basic sanity tests – Does networking (wifi/wired) work correctly? – Does ssh work? – rsync a large file(s) from another system – Download files: wget, ftp, git clone etc. – Play audio/video • Examine kernel logs – Look for new critical and error messages – Check for new warning messages – Check for panic traces • Kernel selftest (Kselftest) – Regression test suite • Kernel
  • Architecting for the Cloud: Lessons Learned from 100 Cloudstack Deployments

    Architecting for the Cloud: Lessons Learned from 100 Cloudstack Deployments

    Architecting for the cloud: lessons learned from 100 CloudStack deployments Sheng Liang CTO, Cloud Platforms, Citrix CloudStack History 2008 2009 2010 2011 2012 Sept 2008: Nov 2009: May 2010: July 2011: April 2012: VMOps CloudStack Cloud.com Citrix Apache Founded 1.0 GA Launch & Acquires CloudStack CloudStack Cloud.com 2.0 GA The inventor of IaaS cloud – Amazon EC2 Amazon eCommerce Platform EC2 API Amazon Proprietary Orchestration Software Open Source Xen Hypervisor Commodity Networking Storage Servers CloudStack is inspired by Amazon EC2 Amazon CloudPortaleCommerce Platform CloudEC2 APIAPIs Amazon ProprietaryCloudStack Orchestration Software ESX Hyper-VOpen SourceXenServer Xen Hypervisor KVM OVM Commodity Networking Storage Servers There will be 1000s of clouds SP Data center mgmt Desktop Owner | Operator Owner and automation Cloud IT Horizontal Vertical General Purpose Special Purpose Learning from 100s of CloudStack deployments Service Providers Web 2.0 Enterprise What is the biggest difference between traditional-style data center automation and Amazon-style cloud? How to handle failures • Server failure comes from: ᵒ 70% - hard disk ᵒ 6% - RAID controller ᵒ 5% - memory ᵒ 18% - other factors 8% • Application can still fail for Annual Failure Rate of servers other reasons: ᵒ Network failure ᵒ Software bugs Kashi Venkatesh Vishwanath and ᵒ Human admin error Nachiappan Nagappan, Characterizing Cloud Computing Hardware Reliability, SoCC’10 11 Internet Core Routers … Access Routers Aggregation Switches Load Balancers … Top of Rack Switches Servers •Bugs in failover mechanism •Incorrect configuration 40 % •Protocol issues such Effectiveness of network as TCP back-off, redundancy in reducing failures timeouts, and spanning tree reconfiguration Phillipa Gill, Navendu Jain & Nachiappan Nagappan, Understanding Network Failures in Data Centers: Measurement, Analysis and Implications , SIGCOMM 2011 13 A.
  • Titans and Trolls of the Open Source Arena

    Titans and Trolls of the Open Source Arena

    Titans and Trolls Enter the Open-Source Arena * by DEBRA BRUBAKER BURNS I. Introduction .................................................................................... 34 II. Legal Theories for Open Source Software License Enforcement ................................................................................... 38 A. OSS Licensing .......................................................................... 38 B. Legal Theories and Remedies for OSS Claims .................... 40 1. Legal Protections for OSS under Copyright and Contract Law ..................................................................... 40 Stronger Protections for OSS License under Copyright Law ................................................................... 40 2. Copyright-Ownership Challenges in OSS ....................... 42 3. Potential Legal Minefields for OSS under Patent Law ...................................................................................... 45 4. Added Legal Protection for OSS under Trademark Law ...................................................................................... 46 5. ITC 337 Action as Uncommon Legal Protection for OSS ..................................................................................... 49 III. Enforcement Within the OSS Community .................................. 49 A. Software Freedom Law Center Enforces OSS Licenses .... 50 B. Federal Circuit Finds OSS License Enforceable Under Copyright Law ......................................................................... 53 C. Commercial OSS
  • Cloud Computing Bible Is a Wide-Ranging and Complete Reference

    Cloud Computing Bible Is a Wide-Ranging and Complete Reference

    A thorough, down-to-earth look Barrie Sosinsky Cloud Computing Barrie Sosinsky is a veteran computer book writer at cloud computing specializing in network systems, databases, design, development, The chance to lower IT costs makes cloud computing a and testing. Among his 35 technical books have been Wiley’s Networking hot topic, and it’s getting hotter all the time. If you want Bible and many others on operating a terra firma take on everything you should know about systems, Web topics, storage, and the cloud, this book is it. Starting with a clear definition of application software. He has written nearly 500 articles for computer what cloud computing is, why it is, and its pros and cons, magazines and Web sites. Cloud Cloud Computing Bible is a wide-ranging and complete reference. You’ll get thoroughly up to speed on cloud platforms, infrastructure, services and applications, security, and much more. Computing • Learn what cloud computing is and what it is not • Assess the value of cloud computing, including licensing models, ROI, and more • Understand abstraction, partitioning, virtualization, capacity planning, and various programming solutions • See how to use Google®, Amazon®, and Microsoft® Web services effectively ® ™ • Explore cloud communication methods — IM, Twitter , Google Buzz , Explore the cloud with Facebook®, and others • Discover how cloud services are changing mobile phones — and vice versa this complete guide Understand all platforms and technologies www.wiley.com/compbooks Shelving Category: Use Google, Amazon, or
  • Google App Engine

    Google App Engine

    Basics of Cloud Computing – Lecture 6 PaaS - Platform as a Service Google App Engine Pelle Jakovits 18 March, 2014, Tartu Outline • Introduction to PaaS • Google Cloud • Google AppEngine – DEMO - Creating applications – Available Google Services – Costs & Quotas • Windows Azure PaaS • PaaS Advantages & Disadvantages 2 Cloud Services 3 Platform as a Service - PaaS • Model of Cloud Computing where users are provided with a full platform for their applications • Enables businesses to build and run web-based, custom applications in on -demand fashion • Eliminates the expense and complexity of selecting , purchasing, configuring , and managing the hardware and software. • Provides access to unlimited computing power, decreasing upfront costs dramatically 4 PaaS Characteristics • Multi-tenant architecture • Built-in scalability of deployed software • Integrated with web services and databases • Users are provided with tools to simplify creating and deploying applications • Simplifies prototyping and deploying startup solutions 5 PaaS Characteristics • Users only pay for the service that they use. • More fine grained cost model • Provides tools to handle billing and subscription management • Using PaaS typically results in a vendor lock-in. 6 Types of PaaS • Stand Alone Application Platforms – Typically built on top of an existing IaaS – Provides development tools for designing and deploying software. – Provide all required computing resources and services needed for hosted applications • Social Application Development Platforms – Used to develop addons and internal applications for social websites like Google+ and Facebook. – Integrated API with the social website platform. – Can be seen as extending a SaaS • Open-Computing Platforms – Not tied to a single IaaS provider. – Supports applications that are written in numerous languages and that use any type of database, operating system, and server.