DOCSLIB.ORG

Evaluation and Improvement of Application Deployment in Hybrid Edge Cloud Environment

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Evaluation and Improvement of Application Deployment in Hybrid Edge Cloud Environment Evaluation and Improvement of Application Deployment in Hybrid Edge Cloud Environment Using OpenStack, Kubernetes, and Spinnaker Khaled Jendi KTH ROYAL INSTITUTE OF TECHNOLOGY SCHOOL OF ELECTRICAL ENGINEERING AND COMPUTER SCIENCE This degree project is supported by: Examinor (KTH): Mihhail Matskin Supervisor (KTH): Ahmad Al-Shishtawy Supervisor (Ericsson, EST): Christopher Price https://wiki.nordix.org/display/RE/Edge+Cloud+project Table of Contents Abstract .......................................................................................................... 1 List of Code Snippet ...................................................................................... 7 List of Abbreviations ...................................................................................... 8 Chapter 1 ....................................................................................................... 9 1 Introduction ............................................................................................. 9 1.1.1 Openstack .......................................................................................... 9 1.1.2 Kubernetes ........................................................................................ 10 1.1.3 System Deployment & Spinnaker ................................................... 10 1.2 Problem ................................................................................................... 10 1.3 Purpose .................................................................................................... 11 1.4 Goal ......................................................................................................... 11 1.4.1 Benefits, Ethics and Sustainability ................................................... 11 1.5 Methodology / Methods ........................................................................ 12 1.6 Delimitations ............................................................................................ 13 1.7 Outline (Disposition) ............................................................................... 13 Chapter 2 ..................................................................................................... 15 2 Edge Cloud Computing Background ................................................ 15 2.1 Traditional and Early Deployment Methods ......................................... 15 2.2 Edge Cloud Computing ......................................................................... 16 2.2.1 Cloud Computing Service Models ................................................ 18 2.3 OpenStack .............................................................................................. 25 2.3.1 History ................................................................................................ 25 2.3.2 OpenStack Architecture ................................................................. 26 2.4 Visualization Principles ........................................................................... 31 2.4.1 Virtual Machines .............................................................................. 31 2.4.2 Containers ........................................................................................ 31 2.5 Kubernetes .............................................................................................. 33 2.5.1 Kubernetes Architecture & Components ..................................... 34 2.6 Spinnaker ................................................................................................ 38 2.6.1 Spinnaker Architecture & Components ........................................ 39 2.7 Related Work ........................................................................................... 41 Chapter 3 ..................................................................................................... 42 3 Methodologies and Deployment Approaches ................................. 42 3.1 Research Approaches ........................................................................... 42 3.1.1 Applied Approach .......................................................................... 42 3.1.2 Qualitative Approach ..................................................................... 42 3.1.3 Empirical & Analytical Approaches ............................................... 42 3.2 Research Process ................................................................................... 43 3.2.1 Solution Overview ............................................................................ 44 3.2.2 Adopted Research Process ............................................................ 46 3.3 Project Management Objectives ......................................................... 49 3.3.1 Project Methods ............................................................................... 50 i 3.3.2 Triple Constraint Theory ................................................................... 52 3.4 Testing & Evaluation ................................................................................ 53 3.4.1 Deployment Using VCS ................................................................... 53 3.4.2 Zero Downtime Testing .................................................................... 53 3.4.3 Google Lighthouse Testing ............................................................. 53 3.5 Deployment Automation Analysis ........................................................ 54 3.6 Project Resources ................................................................................... 54 4 Application Deployment in The Hybrid Cloud .................................. 55 4.1 Cloud Environment Deployment ........................................................... 55 4.1.1 OpenStack Deployment ................................................................. 55 4.1.2 Kubernetes Deployment ................................................................. 59 4.1.3 Spinnaker Deployment .................................................................... 65 4.1.3.1 Deploying Spinnaker Locally ........................................................................................ 65 4.1.3.2 Deploying Distributed Spinnaker ................................................................................ 68 4.2 Test Study (Case Study) .......................................................................... 73 4.2.1 Dockerfile .......................................................................................... 73 4.2.1.1 NodePort and LoadBalancer ......................................................................................... 74 4.2.2 Enabling Git Artifact Provider ......................................................... 76 4.2.3 CHATi Deployment Pipeline ............................................................ 79 Chapter 5 ..................................................................................................... 87 5 Results, Discussions and Conclusions ................................................. 87 5.1 Performance Testing Clusters ................................................................ 87 5.2 Performance Testing Results .................................................................. 87 5.2.1 Downtime During Deployments ..................................................... 88 5.2.2 CPU Usage ........................................................................................ 89 5.2.3 Memory usage ................................................................................. 89 5.2.4 Message Delivery and Request Interruption ................................. 90 5.2.5 Request Duration ............................................................................. 91 5.2.6 Zero Downtime (Distributed Spinnaker) ......................................... 92 Chapter 6 ..................................................................................................... 93 6 Discussions and Conclusions .............................................................. 93 6.1 Descussion and Analysis ........................................................................ 93 6.2 Future Work ............................................................................................. 93 Appendix A .................................................................................................. 95 Appendix B .................................................................................................. 96 Appendix C .................................................................................................. 98 References ................................................................................................. 102 ii iii Abstract Traditional mechanisms of deployment of deferent applications can be costly in terms of time and resources, especially when the application requires a specific environment to run upon and has a different kind of dependencies so to set up such an application, it would need an expert to find out all required dependencies. In addition, it is difficult to deploy applications with efficient usage of resources available in the distributed environment of the cloud. Deploying different projects on the same resources is a challenge. To solve this problem, we evaluated different deployment mechanisms using heterogeneous infrastructure-as-a-service (IaaS) called OpenStack and Microsoft Azure. we also used platform-as-a-service called Kubernetes. Finally, to automate and auto integrate deployments, we used Spinnaker as the continuous delivery framework. The goal of this thesis work is to evaluate and improve
Load more

Recommended publications
  • Continuous Delivery with Spinnaker Fast, Safe, Repeatable Multi-Cloud Deployments
    Continuous Delivery with Spinnaker Fast, Safe, Repeatable Multi-Cloud Deployments Emily Burns, Asher Feldman, Rob Fletcher, Tomas Lin, Justin Reynolds, Chris Sanden, Lars Wander, and Rob Zienert Beijing Boston Farnham Sebastopol Tokyo Continuous Delivery with Spinnaker by Emily Burns, Asher Feldman, Rob Fletcher, Tomas Lin, Justin Reynolds, Chris Sanden, Lars Wan‐ der, and Rob Zienert Copyright © 2018 Netflix, Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online edi‐ tions are also available for most titles (http://oreilly.com/safari). For more information, contact our corporate/institutional sales department: 800-998-9938 or [email protected]. Acquisitions Editor: Nikki McDonald Interior Designer: David Futato Editor: Virginia Wilson Cover Designer: Karen Montgomery Production Editor: Nan Barber Illustrator: Rebecca Demarest Copyeditor: Charles Roumeliotis Technical Reviewers: Chris Devers and Jess Males Proofreader: Kim Cofer May 2018: First Edition Revision History for the First Edition 2018-05-11: First Release The O’Reilly logo is a registered trademark of O’Reilly Media, Inc. Continuous Delivery with Spin‐ naker, the cover image, and related trade dress are trademarks of O’Reilly Media, Inc. While the publisher and the authors have used good faith efforts to ensure that the information and instructions contained in this work are accurate, the publisher and the authors disclaim all responsi‐ bility for errors or omissions, including without limitation responsibility for damages resulting from the use of or reliance on this work. Use of the information and instructions contained in this work is at your own risk.
    [Show full text]
  • Google AMP and What It Can Do for Mobile Applications in Terms of Rendering Speed and User-Experience
    URI: urn:nbn:se:bth-17952 Google AMP and what it can do for mobile applications in terms of rendering speed and user-experience Niklas Andersson Oscar B¨ack June 3, 2019 Faculty of Computing Blekinge Institute of Technology SE-371 79 Karlskrona Sweden This thesis is submitted to the Faculty of Computing at Blekinge Institute of Technology in partial fulfillment of the requirements for the bachelor degree in Software Engineering. The thesis is equivalent to 10 weeks of full time studies. The authors declare that they are the sole authors of this thesis and that they have not used any sources other than those listed in the bibliography and identi- fied as references. They further declare that they have not submitted this thesis at any other institution to obtain a degree. Contact Information: Authors: Niklas Andersson [email protected] Oscar B¨ack [email protected] External Advisor: Simon Nord, Prisjakt [email protected] University Advisor: Michel Nass [email protected] Faculty of Computing Internet: www.bth.se Blekinge Institute of Technology Phone: +46 455 38 50 00 SE-371 79 Karlskrona, Sweden Fax: +46 455 38 50 57 1 1 Abstract On today’s web, a web page needs to load fast and have a great user experience in order to be successful. The faster the better. A server side rendered web page can have a prominent initial load speed while a client side rendered web page will have a great interactive user experience. When combining the two, some users with a bad internet connection or a slow device could receive a poor user experience.
    [Show full text]
  • By Media Lounge
    BY MEDIA LOUNGE WWW.MEDIALOUNGE.CO.UK PART 01 Search Engine Optimisation As one of the most popular eCommerce platforms in the world, Magento certainly packs a powerful punch in terms of functionality and customisation. Harnessing this power however can be tricky, especially when it comes to getting the most from your site in terms of SEO 01performance. Stores built on Magento can take advantage of some fantastic built-in features that can be individually tuned with just a few clicks, all helping to bring extra visitors and improve the rankings of your site on Google’s SERPs (Search Engine Results Pages). It’s important to remember the value of search engine optimisation when considering any marketing strategy, especially when you’re in the business of selling products solely through an online store - the bigger your audience, the more sales you’re likely to generate. The brilliant thing about SEO is that all the visitors your site receives through this channel are free, which means you don’t need to risk any of that precious advertising budget to see results. We’re going to highlight a handful of these SEO features that you can use to improve your site’s rankings and drive more organic traffic to your store. These simple Magento practices can be implemented by anyone - there’s no requirement for much in the way of technical knowledge, but you will need to dedicate some time to getting things set up correctly. Let’s go! BY CHRIS BY Optimising Meta Titles & Descriptions Hidden within the pages of your website lies the key to success - meta data.
    [Show full text]
  • Searchmetrics Lighthouse Report Your Keywords – Your Market – Your Insights
    Searchmetrics Lighthouse Report Your Keywords – Your Market – Your Insights GET YOUR CUSTOM REPORT www.searchmetrics.com Introduction Work stream overview The project will look at the ranking pages for the most important keywords for your domain in your market. Google search results and relevant URLs will be compared in order to analyze correlations between competitors’ domains based on Google Lighthouse data and reveal ranking factors in the specified market. Work stream details Your most relevant ranking factors will be presented through tables and graphs showing the first 20 positions of Google search results for relevant keyword queries. Results will be related to SEO values, performance and accessibility metrics, as well as best practices in optimization of website performance. www.searchmetrics.com Contents Your custom Lighthouse Report from Searchmetrics includes: • An overview of your domain’s ranking pages’ performance in all Lighthouse categories, based on the keyword set provided • A detailed breakdown of results by ranking position for all Lighthouse categories and the most important audits • A direct comparison for each audit between your domain and your relevant online market (based on the respective keyword set) – revealing where you can improve to match and outpace your competitors • An analysis and actionable recommendations from our experts explain how to optimize to improve your website’s Google Lighthouse results • An executive summary of results and priorities, showing which optimizations are most relevant for your website and where you have the biggest potential for improvement www.searchmetrics.com Overview Of All Categories Performance Progressive Web Accessibility Best Practices SEO Score App Score Score Score Score 75 27 68 70 97 Score Scale: 90–100 50–89 0–49 The scores that you see at the top of any Lighthouse report represent the five category scores.
    [Show full text]
  • The 2020 Ecommerce Leaders Survey
    2020 eCOMMERCE LEADERS SURVEY Site Performance & Innovation Trends “When they get frustrated by a slow site, shoppers’ actions are damaging to a retailer in every possible way: they leave, they buy from a competitor, and they likely won’t be coming back to the site.” – Retail Systems Research (RSR) The 3rd annual eCommerce Leaders Survey Report on Site Performance examines key online retail trends based on interviews with over 120 eCommerce executives from some of 67% worry that 3rd party technologies will the industry’s biggest brands. Here are some of the key findings threaten compliance from this year’s report: with privacy laws PRIVACY COMPLIANCE 3RD PARTY TECHNOLOGIES • 67% worry that 3rd party technologies • 68% have multiple 3rd parties will threaten compliance with privacy laws performing similar functions • 55% spend 500K to $4M on 3rd parties • 64% say IT restricts 3rd parties each year and growing. And 20% are due to page “heaviness” adding even more! WEBSITE SPEED FAST FLEXIBILITY • 61% agree faster web performance • 62% agree that headless commerce results in higher conversions can significantly improve engagement • 65% believe they only have 2-3 and conversions seconds to engage shoppers • 77% are focused on closing the order and distribution management gap that Amazon has set Similar to last year, the 2020 eCommerce Leaders Survey Report combines primary research data gathered from online retail 61% agree faster web performance executives with findings from the “eCommerce 3rd Party Technology results in higher Index”, published in October of 2019. The 3rd Party Technology Index conversions examined the performance impact of close to 400 of the most widely adopted 3rd parties used on eCommerce sites.
    [Show full text]
  • Continuous Delivery with Spinnaker on Kubernetes Cluster
    Continuous Delivery with Spinnaker on Kubernetes Cluster Ananda Dwi Rahmawati [email protected] About Me Cloud Engineer [at] Boer Technology Applied Undergraduate Student [at] UGM Activist [at] BlankOn Tech Enthusiast Keep in touch with me [at] @misskecupbung Requirement(s) - Bash Shell - Cloud Provider - Docker - Kubernetes Continuous Integration Integrating Continuous Integration Store Code Build Unit Test(s) Artifacts Test Pass Test Fail QA and Prod Can Use Continuous Integration with Containers Integrating Continuous Integration Store in Build Container Unit Code Container Container Test(s) Registry Test Fail Test Pass QA and Prod Can Use for Deployments Deployment or Delivery? Code Build Unit Test(s) Store Artifacts … Delivery Continuous …. Manual Deployment Store Get Code Stage Test Artifacts Auto Deployment … Deployment Deployment or Delivery? - Delivery: - Land of Operator - Deployment may be automated, but often as a part of idempotent deployment tools (e.g Ansible, Puppet, etc) - Deployment: - Release and idempotently deploy an application - Need to support rollback - May still make us of deployment tools - Containers make this much simpler Spinnaker - Pronunciation → spĭnʹəkər - Open Source multi-cloud CD platform | Inventory + Pipelines - A supplemental sail to the main sail, especially a triangular one, used on yachts for running before the wind - Initially developed by Netflix's Asgard (2014), Open-Sourced in 2015 | Built for releasing software changes with high velocity, confidence | Designed with pluggability in mind - Support
    [Show full text]
  • Fawkes: Faster Mobile Page Loads Via App-Inspired Static Templating
    Fawkes: Faster Mobile Page Loads via App-Inspired Static Templating Shaghayegh Mardani, UCLA; Mayank Singh, IIT Delhi; Ravi Netravali, UCLA https://www.usenix.org/conference/nsdi20/presentation/mardani This paper is included in the Proceedings of the 17th USENIX Symposium on Networked Systems Design and Implementation (NSDI ’20) February 25–27, 2020 • Santa Clara, CA, USA 978-1-939133-13-7 Open access to the Proceedings of the 17th USENIX Symposium on Networked Systems Design and Implementation (NSDI ’20) is sponsored by Fawkes: Faster Mobile Page Loads via App-Inspired Static Templating Shaghayegh Mardani*, Mayank Singh†, Ravi Netravali* *UCLA, †IIT Delhi Abstract Despite the rapid increase in mobile web traffic, page loads still fall short of user performance expectations. State-of- Mobile the-art web accelerators optimize computation or network App fetches that occur after a page’s HTML has been fetched. However, clients still suffer multiple round trips and server processing delays to fetch that HTML; during that time, a browser cannot display any visual content, frustrating users. This problem persists in warm cache settings since HTML is most often marked as uncacheable because it usually embeds Web a mixture of static and dynamic content. Page Inspired by mobile apps, where static content (e.g., lay- out templates) is cached and immediately rendered while dynamic content (e.g., news headlines) is fetched, we built 300 ms 1100 ms 2900 ms Fawkes. Fawkes leverages our measurement study finding Figure 1: Comparing the mobile app and mobile web browser that 75% of HTML content remains unchanged across page loading processes for BBC News over an LTE cellular network.
    [Show full text]
  • Performance Enhancement of Webpage Using Progressive Web App Features
    International Journal of Innovative Research in Advanced Engineering (IJIRAE) ISSN: 2349-2163 Issue 03, Volume 4 (March 2017) www.ijirae.com PERFORMANCE ENHANCEMENT OF WEBPAGE USING PROGRESSIVE WEB APP FEATURES Dr. V. Karpagam, Padmavathe. R, Professor/IT Department IV Information Technology Sri Ramakrishna Engineering College Sri Ramakrishna Engineering College Coimbatore, India Coimbatore, India Lakshana. R, Priyadharshini.S IV Information Technology IV Information Technology Sri Ramakrishna Engineering College Sri Ramakrishna Engineering College Coimbatore, India Coimbatore, India Manuscript History Number: IJIRAE/RS/Vol.04/Issue03/MRAE10102 Received: 07, March 2017 Final Correction: 20, March 2017 Final Accepted: 28, March 2017 Published: March 2017 Abstract— The progressive web application combines the best of web and mobile apps. It is a website built using web technologies that acts like an app. Recent advancements in the browser, availability of service workers, Cache and Push APIs have enabled web developers to allow users to install web apps to their home screen, receive push notifications and even work offline. To use a traditional app, the user must install it beforehand which includes multiple clicks making the app unappealing to the user. This problem is solved by using PWA enabled webpage. The user is given the advantage of accessing the webpage app-like by creating a desktop icon which eliminates the need for multiple clicks. The primary characteristic of this progressive web app is that it must work on all devices and must enhance on devices and browsers that allow it. They take advantage of the much larger web ecosystem, plugins and community and the relative ease of deploying and maintaining a website when compared to a native application in the respective app stores.
    [Show full text]
  • A Web Developer Tool for Simplifying Mobile Pages Through Javascript Optimizations
    JSAnalyzer: A Web Developer Tool for Simplifying Mobile Pages Through JavaScript Optimizations MOUMENA CHAQFEH, New York University Abu Dhabi, UAE JACINTA HU, New York University Abu Dhabi, UAE WALEED HASHMI, New York University Abu Dhabi, UAE RUSSELL COKE, New York University Abu Dhabi, UAE LAKSHMI SUBRAMANIAN, New York University, USA YASIR ZAKI, New York University Abu Dhabi, UAE The amount of JavaScript embedded in Web pages has substantially grown in the past decade, leading to large and complex pages that are computationally intensive for mobile devices. In this paper, we propose JSAnalyzer, an easy-to-use tool that enables Web developers to quickly optimize and generate simpler versions of existing web pages for mobile users. JSAnalyzer can selectively enable or disable JavaScript elements in a page while visually observing their impact, such that non-critical elements can be removed without sacricing the visual content or the interactive functionality. Our quantitative evaluation results show that JSAnalyzer achieves more than 88% relative increase in performance scoring for low-end mobile phones (i.e., from 32% to 60%), and reduces the page load time by 30%. A qualitative study of 22 users shows that JSAnalyzer maintains more than 90% visual similarity to the original pages, whereas a developer evaluation study conducted with 23 developers shows that JSAnalyzer scores more than 80% in terms of usefulness and usability while retaining the page content and functional features. Additionally, we show that JSAnalyzer outperforms state-of-the-art solutions such as JSCleaner and Google AMP. 1 INTRODUCTION Mobile web user experience has become a major concern due to two main reasons: the increasing complexity of the pages, and the processing limitations of mobile devices.
    [Show full text]
  • Introduction to Devops on AWS AWS Whitepaper Introduction to Devops on AWS AWS Whitepaper
    Introduction to DevOps on AWS AWS Whitepaper Introduction to DevOps on AWS AWS Whitepaper Introduction to DevOps on AWS: AWS Whitepaper Copyright © Amazon Web Services, Inc. and/or its affiliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. Introduction to DevOps on AWS AWS Whitepaper Table of Contents Abstract ............................................................................................................................................ 1 Abstract .................................................................................................................................... 1 Introduction ...................................................................................................................................... 2 Continuous Integration ....................................................................................................................... 3 AWS CodeCommit ...................................................................................................................... 3 AWS CodeBuild .......................................................................................................................... 3 AWS CodeArtifact ......................................................................................................................
    [Show full text]
  • The Developer's Guide to Azure
    E-book Series The Developer’s Guide to Azure Published May 2019 May The Developer’s 2 2019 Guide to Azure 03 / 40 / 82 / Introduction Chapter 3: Securing Chapter 6: Where your application and how to deploy We’re here to help your Azure services How can Azure help secure 05 / your app? How can Azure deploy your Encryption services? Chapter 1: Getting Azure Security Center Infrastructure as Code started with Azure Logging and monitoring Azure Blueprints Containers in Azure What can Azure do for you? Azure Stack Where to host your 51 / Where to deploy, application and when? Chapter 4: Adding Azure App Service Features Azure Functions intelligence to Azure Logic Apps your application 89 / Azure Batch Containers How can Azure integrate AI Chapter 7: Share your What to use, and when? into your app? code, track work, and ship Making your application Azure Search software more performant Cognitive Services Azure Front Door Azure Bot Service How can Azure help you plan Azure Content Delivery Azure Machine Learning smarter, collaborate better, and ship Network Studio your apps faster? Azure Redis Cache Developer tooling for AI Azure Boards AI and mixed reality Azure Repos Using events and messages in Azure Pipelines 22 / your application Azure Test Plans Azure Artifacts Chapter 2: Connecting your app with data 72 / 98 / What can Azure do for Chapter 5: Connect your your data? business with IoT Chapter 8: Azure in Action Where to store your data Azure Cosmos DB How can Azure connect, secure, Walk-through: Azure portal Azure SQL Database manage, monitor,
    [Show full text]
  • Running Containerized Microservices on AWS AWS Whitepaper Running Containerized Microservices on AWS AWS Whitepaper
    Running Containerized Microservices on AWS AWS Whitepaper Running Containerized Microservices on AWS AWS Whitepaper Running Containerized Microservices on AWS: AWS Whitepaper Copyright © Amazon Web Services, Inc. and/or its affiliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. Running Containerized Microservices on AWS AWS Whitepaper Table of Contents Abstract ............................................................................................................................................ 1 Abstract .................................................................................................................................... 1 Introduction ...................................................................................................................................... 2 Componentization Via Services ............................................................................................................ 3 Organized Around Business Capabilities ................................................................................................ 5 Products Not Projects ........................................................................................................................
    [Show full text]