DOCSLIB.ORG

Performance Evaluation of Openstack Deployment Tools

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Thesis no:MSEE-2016:42 Performance Evaluation of OpenStack Deployment Tools Sesha Sai Srinivas Jayapala Vemula Department of Communication Systems 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 degree of Master of Science in Electrical Engineering with emphasis on Telecommunication Systems. The thesis is equivalent to 20 weeks of full time studies. Contact Information: Authors: Sesha Sai Srinivas Jayapala Vemula E-mail: [email protected] University advisor: Dr. Patrik Arlos Department of Communication Systems (DIKO) 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 i i ABSTRACT Cloud computing allows access to a common collection of computing resources, that can be easily provisioned, configured as well as released on-demand with minimum cost and effort. OpenStack is an open source cloud management platform aimed at providing private or public IaaS cloud on standard hardware. Since, deploying OpenStack manually is tedious and time-consuming, there are several tools that automate the deployment of OpenStack. Usually, cloud admins choose a tool based on its level of automation, ease of use or interoperability with existing tools used by them. However, another desired factor while choosing a deployment tool is its deployment speed. Cloud admins cannot select based on this factor since, there is no previous work on the comparison of deployment tools based on deployment time. This thesis aims to address this issue. The main aim of the thesis is to evaluate the performance of OpenStack deployment tools with respect to operating system provisioning and OpenStack deployment time, on physical servers. Furthermore, the effect of varying number of nodes, OpenStack architecture deployed and resources (cores and RAM) provided to deployment node on provisioning and deployment times, is also analyzed. Also, the tools are classified based on stages of deployment and method of deploying OpenStack services. In this thesis we evaluate the performance of MAAS, Foreman, Mirantis Fuel and Canonical Autopilot. The performance of the tools is measured via experimental research method. Operating system provisioning time and OpenStack deployment times are measured while varying the number of nodes/ OpenStack architecture and resources provided to deployment node i.e. cores and RAM. Results show that provisioning time of MAAS is less than Mirantis Fuel which is less than Foreman for all node scenarios and resources cases considered. Furthermore, for all 3 tools as number of nodes increases provisioning time increases. However, the amount of increase is lowest for MAAS than Mirantis Fuel and Foreman. Similarly, results for bare metal OpenStack deployment time show that, Canonical Autopilot outperforms Mirantis Fuel by a significant difference for all OpenStack scenarios and resources cases considered. Furthermore, as number of nodes in an OpenStack scenario as well as its complexity increases, the deployment time for both the tools increases. From the research, it is concluded that MAAS and Canonical Autopilot perform better as provisioning and bare metal OpenStack deployment tool respectively, than other tools that have been analyzed. Furthermore, from the analysis it can be concluded that increase in number of nodes/ OpenStack architecture, leads to an increase in both provisioning time and OpenStack deployment time for all the tools. Finally, after analyzing the results the tools are classified based on the method of deploying OpenStack services i.e. parallel or role-wise parallel. Keywords: DevOps, Measurements, OpenStack ACKNOWLEDGMENTS Firstly, I would like to express my sincere gratitude to my supervisor Dr. Patrik Arlos, for spending his valuable time in providing immense support during the thesis. I would like to thank him once again for providing several document reviews which helped me refine the document. I would like to express my deepest gratitude to the God for taking care of my health and wellbeing during the thesis. I would also like to thank Adam Stokes of Ubuntu Solutions Engineering/ OpenStack installer at GitHub, for providing critical details needed for installing Canonical Autopilot. I am extremely thankful to my parents for supporting me throughout my studies and thesis work. This accomplishment would not be possible without their encouragement. Finally, I would like to acknowledge my thesis partner Tarun Aluguri and my friend Nihkil Reddy for helping me in the thesis. CONTENTS ABSTRACT ...........................................................................................................................................I ACKNOWLEDGMENTS ................................................................................................................... II CONTENTS ....................................................................................................................................... III LIST OF FIGURES ............................................................................................................................. V LIST OF TABLES .............................................................................................................................. VI LIST OF ABBREVIATIONS .......................................................................................................... VII 1 INTRODUCTION ....................................................................................................................... 8 1.1 MOTIVATION ......................................................................................................................... 9 1.2 PROBLEM STATEMENT ........................................................................................................... 9 1.3 AIM AND OBJECTIVES ............................................................................................................ 9 1.4 RESEARCH QUESTIONS .......................................................................................................... 9 1.5 RESEARCH METHOD ............................................................................................................ 10 1.6 EXPECTED OUTCOMES ......................................................................................................... 10 1.7 THESIS OUTLINE .................................................................................................................. 11 1.8 SPLIT OF WORK ................................................................................................................... 11 2 BACKGROUND ........................................................................................................................ 12 2.1 CLOUD COMPUTING ............................................................................................................. 12 2.2 OPENSTACK ......................................................................................................................... 12 2.3 SERVER DEPLOYMENT AUTOMATION .................................................................................. 13 2.3.1 Network Booting ............................................................................................................. 13 3 TOOLS ........................................................................................................................................ 16 3.1 PROVISIONING TOOLS .......................................................................................................... 16 3.1.1 Cobbler ........................................................................................................................... 16 3.1.2 Metal as a Service (MAAS) ............................................................................................. 17 3.1.3 Foreman .......................................................................................................................... 18 3.2 CONFIGURATION MANAGEMENT TOOLS .............................................................................. 19 3.2.1 Puppet ............................................................................................................................. 19 3.2.2 Juju ................................................................................................................................. 20 3.3 OPENSTACK DEPLOYMENT TOOLS ...................................................................................... 20 3.3.1 Model of a typical Bare Metal OpenStack Deployment Tool .......................................... 21 3.3.2 Mirantis Fuel .................................................................................................................. 21 3.3.3 Canonical’s OpenStack Autopilot ................................................................................... 24 3.3.4 Other tools available ...................................................................................................... 25 4 METHODOLOGY .................................................................................................................... 26 4.1 RESEARCH METHOD ............................................................................................................ 26 4.2 EXPERIMENT TEST-BED ....................................................................................................... 26 4.2.1 Hardware Used ..............................................................................................................
Recommended publications
  • Ubuntu Installation Guide

    Ubuntu Installation Guide

    Ubuntu Installation Guide Ubuntu Installation Guide Copyright © 2004 – 2020 the Debian Installer team Copyright © 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2015, 2018 Canonical Ltd. This document contains installation instructions for the Ubuntu 20.04 system (codename “‘Focal Fossa’”), for the S/390 (“s390x”) architecture. It also contains pointers to more information and information on how to make the most of your new Ubuntu system. This manual is free software; you may redistribute it and/or modify it under the terms of the GNU General Public License. Please refer to the license in Appendix F. Table of Contents Installing Ubuntu 20.04 “Focal Fossa” For s390x...........................................................................ix 1. Welcome to Ubuntu ........................................................................................................................1 1.1. What is Ubuntu?...................................................................................................................1 1.1.1. Sponsorship by Canonical .......................................................................................1 1.2. What is Debian? ...................................................................................................................1 1.2.1. Ubuntu and Debian..................................................................................................2 1.2.1.1. Package selection........................................................................................2 1.2.1.2. Releases.......................................................................................................3
  • Compass – a Streamlined Openstack Deployment System

    Compass – a Streamlined Openstack Deployment System

    2013年11月7日星期四 Compass – A Streamlined OpenStack Deployment System Shuo Yang Principal Architect of Cloud Computing, US R&D Center Outline of This Talk 1 Scope of Problem for Compass 2 Compass Explained 3 DRY, Truly Open Deployment 1 Compass at a Glimpse Think Big, Start Small A General System to Deploy Distributed Systems, Extensibility as a Primary Design Goal Not Limited to OpenStack, but Streamlined Our OpenStack Deployment Like a Charm To Be Open Sourced – Apache 2.0 Soon 100% Python, 5000 Line of Python Code Successfully Deployed Several Dogfood Clusters Compass Wiki Page: https://wiki.openstack.org/wiki/Compass 2 Data Center as a Computer Open Cloud OS (OpenStack) Open Deployment (Compass) OpenStackLinux Quantumeth0, lo Nova/proc Cinder/dev Live Auto CD / Deploy GRUB NIC CPU Disk SwitchSwitchSwitch CPUCPUServer DiskStorage NIC CPU Disk (5020) (2285/1285) (N8000/N900) OpenStack Control Channel LILO/GRUB/LiveCD for OpenStack HW/SW Configuration Deployment Channel 3 Why We Are Doing This? Full HW Portfolio in Data Center No.1 as Storage Revenue Growth No. 2 as `x86 Server Revenue Growth Needless to Say, Networking Gears.. OpenStack Makes the Above a Full Global Excellent Telecom Cloud Solution Cloud Solution Provider of year 2012 4 OpenStack Deployment System Overview Crowbar TripleO (“under the cloud” mode) Pioneer effort, a Ruby web app, Chef based Attractive concept to OpenStack folks: configuration management deploy OpenStack from OpenStack Fuel DevStack A great web apps, Puppet based A great tool for simple OpenStack
  • Red Hat Satellite 6.3 Architecture Guide

    Red Hat Satellite 6.3 Architecture Guide

    Red Hat Satellite 6.3 Architecture Guide Planning Satellite 6 Deployment Last Updated: 2019-04-16 Red Hat Satellite 6.3 Architecture Guide Planning Satellite 6 Deployment Red Hat Satellite Documentation Team [email protected] Legal Notice Copyright © 2019 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
  • Guido Van Rossum on PYTHON 3 Get Your Sleep From

    Guido Van Rossum on PYTHON 3 Get Your Sleep From

    JavaScript | Inform 6 & 7 | Falcon | Sleep | Enlightenment | PHP LINUX JOURNAL ™ THE STATE OF LINUX AUDIO SOFTWARE LANGUAGES Since 1994: The Original Magazine of the Linux Community OCTOBER 2008 | ISSUE 174 Inform 7 REVIEWED JavaScript | Inform 6 & 7 | Falcon | Sleep Enlightenment PHP Audio | Inform 6 & 7 Falcon JavaScript Don’t Get Eaten HP Media by a Grue! Vault 5150 Scalent’s Managing Virtual Operating PHP Code Environment Guido van Rossum on PYTHON 3 Get Your Sleep from OCTOBER Java www.linuxjournal.com 2008 $5.99US $5.99CAN 10 ISSUE Martin Messner Enlightenment E17 Insights from SUSE’s Lightweight Alternative 174 + Security Team Lead to KDE and GNOME 0 09281 03102 4 MULTIPLY ENERGY EFFICIENCY AND MAXIMIZE COOLING. THE WORLD’S FIRST QUAD-CORE PROCESSOR FOR MAINSTREAM SERVERS. THE NEW QUAD-CORE INTEL® XEON® PROCESSOR 5300 SERIES DELIVERS UP TO 50% 1 MORE PERFORMANCE*PERFORMANCE THAN PREVIOUS INTEL XEON PROCESSORS IN THE SAME POWERPOWER ENVELOPE.ENVELOPE. BASEDBASED ONON THETHE ULTRA-EFFICIENTULTRA-EFFICIENT INTEL®INTEL® CORE™CORE™ MICROMICROARCHITECTURE, ARCHITECTURE IT’S THE ULTIMATE SOLUTION FOR MANAGING RUNAWAY COOLING EXPENSES. LEARN WHYWHY GREAT GREAT BUSINESS BUSINESS COMPUTING COMPUTING STARTS STARTS WITH WITH INTEL INTEL INSIDE. INSIDE. VISIT VISIT INTEL.CO.UK/XEON INTEL.COM/XEON. RELION 2612 s 1UAD #ORE)NTEL®8EON® RELION 1670 s 1UAD #ORE)NTEL®8EON® PROCESSOR PROCESSOR s 5SERVERWITHUPTO4" s )NTEL@3EABURG CHIPSET s )DEALFORCOST EFFECTIVE&ILE$" WITH-(ZFRONTSIDEBUS APPLICATIONS s 5PTO'"2!-IN5CLASS s 2!32ELIABILITY !VAILABILITY LEADINGMEMORYCAPACITY 3ERVICEABILITY s -ANAGEMENTFEATURESTOSUPPORT LARGECLUSTERDEPLOYMENTS 34!24).'!4$2429.00 34!24).'!4$1969.00 Penguin Computing provides turnkey x86/Linux clusters for high performance technical computing applications.
  • Bootstack Your Cloud

    Bootstack Your Cloud

    BootStack Your cloud. Built. Managed. Delivered. What is BootStack? % of OpenStack production clouds run on: BootStack (short for: Build, Operate, and Optionally Transfer), is the fully managed cloud offering from 9% Canonical, the company behind Ubuntu. BootStack is a true end-to-end managed solution for OpenStack on Ubuntu including the design, implementation, ongoing maintenance, and the optional transfer of the management function to 26% the customer if desired. 52% Your BootStack cloud will be built on Ubuntu OpenStack, Ubuntu the world’s most popular OpenStack distribution, along with the KVM and LXD hypervisors, and the full set of RedHat / RHEL industry-leading management and monitoring software 13% CentOs from Canonical including MAAS, Juju and Landscape. These Other tools allow for quick and easy provisioning, orchestration, and management of cloud resources. Your cloud can be built Source: OpenStack user survey, 2017 on the hardware at the your datacentre, or offsite with one of Canonical’s trusted partners. What does BootStack include? Why BootStack? BootStack covers cloud deployments from 12 hosts and upwards, thereby meeting the needs of a broad range Enterprises often struggle to deliver OpenStack projects of customer use cases – from very simple setups to multi- on time and on budget, not to mention operating them datacentre production-grade workloads. efficiently and securely once they’re deployed. Acquiring, training and retaining the staff necessary to be successful Build: Canonical cloud consultants will design and is a huge challenge for most enterprises. build a cloud on Ubuntu OpenStack using Canonical’s state-of-the-art tools for hardware provisioning and BootStack from Canonical gives you access to the world’s service deployment.
  • Automating the Enterprise with Ansible

    Automating the Enterprise with Ansible

    AUTOMATING THE ENTERPRISE WITH ANSIBLE Dustin Boyd Solutions Architect September 12, 2017 EVERY ORGANIZATION IS A DIGITAL ORGANIZATION. Today, IT is driving innovation. If you can’t deliver software fast, your organization can’t meet the mission, period. Digital organizations are essentially software. If they expect to thrive in a digital environment, they must have an improved competence in software delivery. Gartner 2015 2 COMPLEXITY KILLS PRODUCTIVITY. Complexity is the enemy of innovation, which is why today’s enterprises are looking to automation and DevOps tools and practices. DevOps can help organizations that are pushing to implement a bimodal strategy to support their digitalization efforts. Gartner 2015 3 WHEN YOU AUTOMATE, YOU ACCELERATE. Ansible loves the repetitive work your people hate. It helps smart people do smarter work. All with fewer errors and better accountability. Automation can crush complexity and it gives you the one thing you can’t get enough of… time. 4 “Ansible delivers DevOps to a broader class of enterprise users that include those inside the business units and teams where agile practices and fast provisioning of infrastructure are in demand.” JAY LYMAN, 451 RESEARCH – NOV 2013 GARTNER COOL VENDOR 2015 “Previous vendors in this [DevOps] market often require unique programming skills. Ansible’s simple language reduces the barrier to adoption and opens it up to a variety of skill sets…” 5 AUTOMATION = ACCELERATION “With Ansible Tower, we just click a button and deploy to production in 5 minutes. It used to take us 5 hours with 6 people sitting in a room, making sure we didn’t do anything wrong (and we usually still had errors).
  • Cobbler Provider

    Cobbler Provider

    Cobbler Provider The Cobbler provider is used to interact with a locally installed Cobbler (http://cobbler.github.io) service. The provider needs to be congured with the proper credentials before it can be used. Use the navigation to the left to read about the available resources. Example Usage provider "cobbler" { username == "${var.cobbler_username}" password == "${var.cobbler_password}" url == "${var.cobbler_url}" } resource "cobbler_distro" "ubuntu-1404-x86_64" { } Argument Reference The following arguments are supported: username - (Required) The username to the Cobbler service. This can also be specied with the COBBLER_USERNAME shell environment variable. password - (Required) The password to the Cobbler service. This can also be specied with the COBBLER_PASSWORD shell environment variable. url - (Required) The url to the Cobbler service. This can also be specied with the COBBLER_URL shell environment variable. insecure - (Optional) Ignore SSL certicate warnings and errors. This can also be specied with the COBBLER_INSECURE shell environment variable. cacert_file - (Optional) The path or contents of an SSL CA certicate. This can also be specied with the COBBLER_CACERT_FILE shell environment variable. cobbler_distro Manages a distribution within Cobbler. Example Usage resource "cobbler_distro" "ubuntu-1404-x86_64" { name == "foo" breed == "ubuntu" os_version == "trusty" arch == "x86_64" kernel == "/var/www/cobbler/ks_mirror/Ubuntu-14.04/install/netboot/ubuntu-installer/amd64/linux" initrd == "/var/www/cobbler/ks_mirror/Ubuntu-14.04/install/netboot/ubuntu-installer/amd64/initrd.gz" } Argument Reference The following arguments are supported: arch - (Required) The architecture of the distro. Valid options are: i386, x86_64, ia64, ppc, ppc64, s390, arm. breed - (Required) The "breed" of distribution. Valid options are: redhat, fedora, centos, scientic linux, suse, debian, and ubuntu.
  • Cobbler Documentation Release 3.0.1

    Cobbler Documentation Release 3.0.1

    Cobbler Documentation Release 3.0.1 Enno Gotthold May 27, 2020 Contents 1 Quickstart 3 1.1 Preparing your OS..........................................3 1.2 Changing settings..........................................3 1.3 DHCP management and DHCP server template...........................4 1.4 Notes on files and directories....................................5 1.5 Starting and enabling the Cobbler service..............................5 1.6 Checking for problems and your first sync..............................5 1.7 Importing your first distribution...................................6 2 Install Guide 9 2.1 Prerequisites.............................................9 2.2 Installation.............................................. 10 2.3 RPM................................................. 10 2.4 DEB................................................. 11 2.5 Relocating your installation..................................... 12 3 Cobbler CLI 13 3.1 General Principles.......................................... 13 3.2 CLI-Commands........................................... 14 3.3 EXIT_STATUS............................................ 24 3.4 Additional Help........................................... 24 4 Cobblerd 25 4.1 Preamble............................................... 25 4.2 Description.............................................. 25 4.3 Setup................................................. 26 4.4 Autoinstallation (Autoyast/Kickstart)................................ 26 4.5 Options................................................ 26 5 Cobbler Configuration
  • Cobbler Documentation Release 2.8.5

    Cobbler Documentation Release 2.8.5

    Cobbler Documentation Release 2.8.5 Jörgen Maas Nov 19, 2020 Contents 1 About 3 1.1 Release Notes.........................................3 1.2 Distribution Support......................................5 1.3 Distribution Notes.......................................7 1.4 How We Model Things..................................... 13 2 Installation 15 2.1 Prerequisites.......................................... 15 2.2 Installing from packages.................................... 16 2.3 Installing from Source..................................... 18 2.4 Configuration Files....................................... 20 2.5 Relocating your installation.................................. 21 3 General 23 3.1 Cobbler Primitives....................................... 23 3.2 Cobbler Direct Commands................................... 54 3.3 Cobbler Settings........................................ 69 3.4 Managing Services with Cobbler............................... 90 3.5 Kickstart Templating...................................... 94 3.6 Snippets............................................ 102 3.7 Package Management and Mirroring............................. 112 3.8 File System Information.................................... 114 4 Advanced 119 4.1 Advanced Networking..................................... 119 4.2 SELinux............................................ 122 4.3 Configuration Management.................................. 123 4.4 Extending cobbler....................................... 131 4.5 Power Management...................................... 135 4.6
  • Building and Managing Virtual Machines at the Tier 1

    Building and Managing Virtual Machines at the Tier 1

    BuildingBuilding andand managingmanaging virtualvirtual machinesmachines atat thethe TierTier 11 Jason A. Smith, John DeStefano, James Pryor System Workflow: From new unconfigured to fully configured & monitored Install New System PXE boot Cobbler RHEL via system w/ Powered off network install Server kickstart. RHEL Install puppet Reboot Fresh booted FusionInventory Manually tell Contact Puppet system w/ Agent reports on Asset Mgmt GLPI to assign system w/ server Puppet RHEL system's assets Service puppet classes Puppet classes Server send catalog to puppet client Puppet configures & Reports back to system w/ makes changes System server via puppet's Puppet Puppet catalog system via catalog Configured exported resources Server The puppet server gives the Nagios server a new Now Nagios knows about the new machine System config catalog. Nagios & service and will automatically begin to Server monitor it. Configured & monitored CobblerCobbler provisioningprovisioning systemsystem System Provisioning Cobbler & Koan Cobbler is provisioning tool-set that allows for rapid setup & installation of systems through the network. It has both a web GUI and a command line interface. Provisioning with Cobbler: ● Just about all non-LinuxFarm machines are PXE booted & provisioned with Cobbler and it's companion tool koan. ● We use Cobbler as the PXE boot kickstart source for RPM packages. ● During post-install of the kickstart, we register the machine against the local Red Hat Satellite. It becomes the sole repo for packages & updates. ● Satellite allows
  • Full Circle the INDEPENDENT MAGAZINE for the UBUNTU COMMUNITY

    Full Circle the INDEPENDENT MAGAZINE for the UBUNTU COMMUNITY

    Issue #2 - June 2007 full circle THE INDEPENDENT MAGAZINE FOR THE UBUNTU COMMUNITY LINSPIRE & MICROSOFT LINSPIRE SIGNS FOR PATENT PROTECTION NEXT WHO'S REVIEW : HOW TO : INSTALL : SYSTEM76 LAPTOP UBUNTU ON A MAC MINI STEP-BY-STEP INSTALL FROM GETTING THE BOX BASIC INSTALL OF VPN OF KUBUNTU 7.04 : TO BOOTING UBUNTU UBUNTU FOR GRANDMA! FEISTY FAWN fullcircle magazine is not affiliated with or endorsed by Canonical Ltd. full circle News p.03 Your monthly update of what's going on in the world of Linux and Open Source Software Flavour of the Month - Kubuntu p.06 This month Robert Clipsham shows us a step-by-step STEP-BY-STEP INSTALL installation of Kubuntu Linux 7.04 P.06 How-To Ubuntu on the Mac Mini p.09 Ubuntu for Grandma p.12 Virtual Private Networking p.16 Scribus - Part 2 p.17 Review - System76 Laptop p.20 P.17 P.16 Thinking of buying a laptop? System76 supplies quality laptops pre-installed with Ubuntu! Interview - GRAMPS p.24 P12 P.20 My Story - 6 Months with Ubuntu p.29 Fighting to live with Linux after years of Windows use. Ubuntu Youth p.31 Letters p.33 Q&A p.35 My Desktop & My PC p.36 P.09 P.24 Show us your mean-machine! The Top 5 p.37 Andrew Min presents his Top5 Widgets How to Contribute p.39 Want to help fill future issues? Here are the details All text and images contained in this magazine are released under the Creative Commons Attribution-By-ShareAlike 3.0 Unported license.
  • Master's Thesis

    Master's Thesis

    CLOUD COMPUTING ENHANCEMENTS AND PRIVATE CLOUD MANAGEMENT A Degree Thesis Submitted to the Faculty of the Escola Tècnica d'Enginyeria de Telecomunicació de Barcelona Universitat Politècnica de Catalunya by Antonio Alonso Gil In partial fulfilment of the requirements for the degree in AUDIOVISUAL SYSTEMS ENGINEERING Advisors: Paulo da Fonseca Pinto Pedro Amaral Jordi Domingo-Pascual Barcelona, May 2018 Abstract This is a project developed in the Departamento de Engenharia Electrotécnica (DEE) in the Faculdade de Ciências e Tecnologia (FCT) from Universidade NOVA de Lisboa (UNL). The objective of this project is to implement a private cloud in a small datacenter network using the MAAS server provisioning tool and the Openstack software platform for cloud computing, leaving it ready to be interconnected it with an experimental SDN Network. The private cloud and Network will serve the telecommunications group undergraduate and post-graduate labs and it will be used both as a production Network and as a test bed for new research with the cloud being used to integrate several available computing resources in order to maximize the available computation power for research tasks. 1 Resum Aquest és un projecte desenvolupat al Departament d'Enginyeria Electrotècnica (DEE) a la Facultat de Ciències i Tecnologia (FCT) de la Universitat NOVA de Lisboa (UNL). L'objectiu d'aquest projecte és implementar un núvol privat en una petita xarxa de centre de dades fent servir la eina d’aprovisionament de servidors MAAS eI projecte de computació en el núvol Openstack per a que posteriorment aquesta sigui interconectada amb una xarxa SDN experimental. El núvol privat i la xarxa serviràn als laboratoris de pregrau i postgrau del grup de telecomunicacions de la Universitat i s'utilitzarà tant com una xarxa de producció com un banc de proves per a noves investigacions, fent servir el núvol per integrar diversos recursos informàtics disponibles per maximitzar la computació disponible per a tasques d'investigació.