DOCSLIB.ORG

Integrated Management of Cloud Computing Resources

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Integrated Management of Cloud Computing Resources Instituto Superior de Engenharia do Porto Departamento de Engenharia Eletrotécnica Rua Dr. António Bernardino de Almeida, 431, 4200-072 Porto Integrated Management of Cloud Computing Resources Dissertation submitted to the Instituto Superior de Engenharia do Porto in partial fulfilment of the requirements for the degree of Master of Science in Electrical and Computers Engineering - Major in Telecommunications Fernando Miguel Dias Meireles Supervisor: Prof. Maria Benedita Campos Neves Malheiro Co-supervisor: Prof. Pedro João De-Francesco Assis Academic Year: 2013-2014 To my family. Abstract Lunacloud is a cloud service provider with offices in Portugal, Spain, France and UK that focus on delivering reliable, elastic and low cost cloud Infrastructure as a Service (IaaS) solutions. The company currently relies on a proprietary IaaS platform - the Parallels Automation for Cloud Infrastructure (PACI) - and wishes to expand and integrate other IaaS solutions seamlessly, namely open source solutions. This is the challenge addressed in this thesis. This proposal, which was fostered by Eurocloud Portugal Association, contributes to the promotion of interoperability and standardisation in Cloud Computing. The goal is to investigate, propose and develop an interoperable open source solution with standard interfaces for the integrated management of IaaS Cloud Computing resources based on new as well as existing abstraction libraries or frameworks. The solution should provide both Web and application programming interfaces. The research conducted consisted of two surveys covering existing open source IaaS platforms and PACI (features and API) and open source IaaS abstraction solutions. The first study was focussed on the characteristics of most popular open source IaaS platforms, namely OpenNebula, OpenStack, CloudStack and Eucalyptus, as well as PACI and included a thorough inventory of the provided Application Programming Interfaces (API), i.e., offered operations, followed by a comparison of these platforms in order to establish their similarities and dis- similarities. The second study on existing open source interoperability solutions included the analysis of existing abstraction libraries and frameworks and their comparison. The approach proposed and adopted, which was supported on the conclusions of the carried surveys, reuses an existing open source abstraction solution - the Apache Deltacloud framework. Deltacloud relies on the development of software driver modules to interface with different IaaS platforms, officially provides and supports drivers to sixteen IaaS platform, including OpenNebula and OpenStack, and allows the development of new provider drivers. The latter functionality v was used to develop a new Deltacloud driver for PACI. Furthermore, Deltacloud provides a Web dashboard and REpresentational State Transfer (REST) API interfaces. To evaluate the adopted solution, a test bed integrating OpenNebula, Open- Stack and PACI nodes was assembled and deployed. The tests conducted involved time elapsed and data payload measurements via the Deltacloud framework as well as via the pre-existing IaaS platform API. The Deltacloud framework be- haved as expected, i.e., introduced additional delays, but no substantial over- heads. Both the Web and the REST interfaces were tested and showed identical measurements. The developed interoperable solution for the seamless integration and provi- sion of IaaS resources from PACI, OpenNebula and OpenStack IaaS platforms fulfils the specified requirements, i.e., provides Lunacloud with the ability to ex- pand the range of adopted IaaS platforms and offers a Web dashboard and REST API for the integrated management. The contributions of this work include the surveys and comparisons made, the selection of the abstraction framework and, last, but not the least, the PACI driver developed. Resumo A Lunacloud é uma empresa provedora de serviços de computação em nuvem com escritórios em Portugal, Espanha, França e Reino Unido e focada no provisiona- mento de serviços ao nível da infraestrutura (IaaS). Atualmente, esta empresa de- pende de uma plataforma de IaaS proprietária – Parallels Automation for Cloud Infrastructure (PACI) – e pretende expandir a oferta de serviços através da in- tegração de novas plataformas de IaaS, nomeadamente do tipo open-source. Este é o desafio proposto para a presente tese. Esta proposta encontra-se enquadrada nos esforços de promoção da normalização e interoperabilidade da Associação EuroCloud Portugal. O objetivo do trabalho consiste em investigar, propor e desenvolver uma solução interoperável, baseada na utilização de ferramentas ou bibliotecas de abstracção open-source existentes ou a desenvolver, que apresente interfaces nor- malizadas para a gestão integrada de recursos de computação em nuvem ao nível da infraestrutura. A solução desenvolvida deverá incluir interfaces Web e de programação de aplicações. O trabalho de investigação realizado foi composto por dois estudos referentes à caracterização e análise das interfaces das plataformas de IaaS (plataforma pro- prietária PACI e plataformas open-source) selecionadas e soluções open-source de abstracção de plataformas de IaaS existentes. O primeiro estudo caracterizou as plataformas de IaaS open-source mais conhecidas, nomeadamente, OpenNebula, OpenStack, CloudStack e Eucalyptus, assim como a plataforma de IaaS propri- etária (usada pela Lunacloud) PACI. Foi também incluído neste estudo um in- ventário extensivo e comparação das respetivas bibliotecas de interface de forma a identificar similaridades e diferenças. O segundo estudo contemplou as soluções de interoperabilidade open-source existentes, incluindo a análise e comparação das ferramentas e bibliotecas de abstracção. A abordagem escolhida e adoptada, que se suportou nas conclusões dos estudos realizados, reutiliza uma solução de abstracção já existente – o framework de ab- stracção Deltacloud. Esta ferramenta recorre a módulos de software – drivers – vii para interagir com as diferentes plataformas de IaaS, fornece oficialmente drivers para dezasseis plataformas de IaaS, incluindo as plataformas OpenNebula e Open- Stack, e permite o desenvolvimento de novos drivers para a integração de novos fornecedores/plataformas de IaaS. Esta última funcionalidade foi utilizada para criar um novo driver para a plataforma de IaaS proprietária PACI. Para além das funcionalidades referidas, a ferramenta Deltacloud, também fornece um Web dashboard e bibliotecas de interface REpresentational State Transfer (REST). De forma a avaliar a solução desenvolvida, foi montada uma plataforma de testes integrando as plataformas OpenNebula, OpenStack, CloudStack e PACI. Os testes realizados consistiram na medição dos tempos de resposta e da quan- tidade de informação trocada durante a invocação das operações através da ferra- menta Deltacloud e diretamente às bibliotecas de interface das respectivas plata- formas de IaaS. A ferramenta Deltacloud comportou-se como era esperado, i.e., o tempo de execução das operações sofreu atrasos adicionais e a quantidade de informação trocada manteve-se em geral. Ambas as interfaces Web e REST foram testadas, apresentando medidas similares. A solução de interoperabilidade desenvolvida para a integração e disponibil- ização de recursos de IaaS, através das plataformas PACI, OpenNebula e Open- Stack, cumpre os requisitos especificados, i.e., permite que a empresa Lunacloud expanda a gama de plataformas de IaaS adoptadas, oferecendo um Web dash- board e uma biblioteca de interface para a gestão integrada dos recursos de IaaS. As contribuições deste trabalho incluem os estudos e comparações realizados, a selecção da ferramenta de abstracção e, por último, mas não menos importante, o driver desenvolvido para a plataforma PACI. Contents Contentsi List of Figures xiii List of Tables xv List of Code Snippets xvii Acronyms xix 1 Introduction1 1.1 Motivation ............................... 2 1.2 Thesis.................................. 2 1.3 Objectives................................ 2 1.4 Functional Tests ............................ 3 1.5 Expected Results............................ 3 1.6 Contributions.............................. 4 1.7 Work Plan................................ 4 1.8 Structure of the Dissertation ..................... 5 2 Cloud Computing7 2.1 Definition................................ 7 2.2 Deployment Models .......................... 9 2.2.1 Private Clouds ......................... 10 2.2.2 Community Clouds....................... 11 2.2.3 Public Clouds.......................... 13 2.2.4 Hybrid Clouds ......................... 14 2.3 Service Models ............................. 15 2.3.1 Infrastructure as a Service................... 16 2.3.2 Platform as a Service ..................... 16 2.3.3 Software as a Service...................... 17 i ii CONTENTS 2.4 Characteristics ............................. 17 2.4.1 On-demand Self-service .................... 18 2.4.2 Broad Network Access..................... 18 2.4.3 Resource Pooling........................ 18 2.4.4 Rapid Elasticity ........................ 18 2.4.5 Measured Service........................ 19 2.5 Concerns ................................ 19 2.5.1 Unpredictable Performance .................. 19 2.5.2 Security Risks ......................... 20 2.5.3 Data Privacy.......................... 21 2.6 Virtualization Technologies ...................... 22 2.6.1 Full Virtualization....................... 23 2.6.2 Para-virtualization....................... 24 2.6.3 OS-level Virtualization....................
Load more

Recommended publications
  • Security in Cloud Computing a Security Assessment of Cloud Computing Providers for an Online Receipt Storage
    Security in Cloud Computing A Security Assessment of Cloud Computing Providers for an Online Receipt Storage Mats Andreassen Kåre Marius Blakstad Master of Science in Computer Science Submission date: June 2010 Supervisor: Lillian Røstad, IDI Norwegian University of Science and Technology Department of Computer and Information Science Problem Description We will survey some current cloud computing vendors and compare them to find patterns in how their feature sets are evolving. The start-up firm dSafe intends to exploit the promises of cloud computing in order to launch their business idea with only marginal hardware and licensing costs. We must define the criteria for how dSafe's application can be sufficiently secure in the cloud as well as how dSafe can get there. Assignment given: 14. January 2010 Supervisor: Lillian Røstad, IDI Abstract Considerations with regards to security issues and demands must be addressed before migrating an application into a cloud computing environment. Different vendors, Microsoft Azure, Amazon Web Services and Google AppEngine, provide different capabilities and solutions to the individual areas of concern presented by each application. Through a case study of an online receipt storage application from the company dSafe, a basis is formed for the evaluation. The three cloud computing vendors are assessed with regards to a security assessment framework provided by the Cloud Security Alliance and the application of this on the case study. Finally, the study is concluded with a set of general recommendations and the recommendation of a cloud vendor. This is based on a number of security as- pects related to the case study’s existence in the cloud.
    [Show full text]
  • Vsrx Deployment Guide for Google Cloud Platform
    vSRX Deployment Guide for Google Cloud Platform Published 2020-09-22 ii Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, California 94089 USA 408-745-2000 www.juniper.net Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. in the United States and other countries. All other trademarks, service marks, registered marks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. vSRX Deployment Guide for Google Cloud Platform Copyright © 2020 Juniper Networks, Inc. All rights reserved. The information in this document is current as of the date on the title page. YEAR 2000 NOTICE Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036. END USER LICENSE AGREEMENT The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted at https://support.juniper.net/support/eula/. By downloading, installing or using such software, you agree to the terms and conditions of that EULA. iii Table of Contents About the Documentation
    [Show full text]
  • Open Cloud Computing with the Simple Cloud API and Apache Libcloud Doug Tidwell Cloud Computing Evangelist, IBM [email protected]
    Open Cloud Computing with the Simple Cloud API and Apache libcloud Doug Tidwell Cloud Computing Evangelist, IBM [email protected] Session 7665 Agenda • Portability and interoperability • A few words about APIs • The Simple Cloud API • Storage • Queues • Documents • Controlling VMs with Apache libcloud • Resources / Next steps The problem Vendor lock-in • If there’s a new technology, any talented programmer will want to use it. • Maybe the shiny new thing is appropriate for what we’re doing. • Maybe not. • We’re probably going to use it anyway. • The challenge is to walk the line between using the newest, coolest thing and avoiding vendor lock-in. Portability and Interoperability • In writing flexible code for the cloud, there are two key concepts: • Portability is the ability to run components or systems written for one cloud provider in another cloud provider’s environment. • Interoperability is the ability to write one piece of code that works with multiple cloud providers, regardless of the differences between them. How standards work • For a standards effort to work, three things have to happen: • The standard has to solve a common problem in an elegant way. • The standard has to be implemented consistently by vendors. • Users have to insist that the products they use implement the standard. How standards work • All three things have to happen. • If the standard doesn't solve a common problem, or if it solves it in an awkward way, the standard fails. • If the standard isn't implemented by anyone, the standard fails. • If customers buy and use products even though they don't implement the standard, the standard fails.
    [Show full text]
  • AWS Risk and Compliance Whitepaper for Additional Details - Policy Available At
    Amazon Web Services: Risk and Compliance January 2017 (Consult http://aws.amazon.com/compliance/resources for the latest version of this paper) Amazon Web Services Risk and Compliance January 2017 This document is intended to provide information to assist AWS customers with integrating AWS into their existing control framework supporting their IT environment. This document includes a basic approach to evaluating AWS controls and provides information to assist customers with integrating control environments. This document also addresses AWS-specific information around general cloud computing compliance questions. Table of Contents Risk and Compliance Overview .......................................................................................................................3 Shared Responsibility Environment ............................................................................................................................................... 3 Strong Compliance Governance ...................................................................................................................................................... 4 Evaluating and Integrating AWS Controls ...................................................................................................4 AWS IT Control Information ........................................................................................................................................................... 5 AWS Global Regions .........................................................................................................................................................................
    [Show full text]
  • Orchestrating Big Data Analysis Workflows in the Cloud: Research Challenges, Survey, and Future Directions
    00 Orchestrating Big Data Analysis Workflows in the Cloud: Research Challenges, Survey, and Future Directions MUTAZ BARIKA, University of Tasmania SAURABH GARG, University of Tasmania ALBERT Y. ZOMAYA, University of Sydney LIZHE WANG, China University of Geoscience (Wuhan) AAD VAN MOORSEL, Newcastle University RAJIV RANJAN, Chinese University of Geoscienes and Newcastle University Interest in processing big data has increased rapidly to gain insights that can transform businesses, government policies and research outcomes. This has led to advancement in communication, programming and processing technologies, including Cloud computing services and technologies such as Hadoop, Spark and Storm. This trend also affects the needs of analytical applications, which are no longer monolithic but composed of several individual analytical steps running in the form of a workflow. These Big Data Workflows are vastly different in nature from traditional workflows. Researchers arecurrently facing the challenge of how to orchestrate and manage the execution of such workflows. In this paper, we discuss in detail orchestration requirements of these workflows as well as the challenges in achieving these requirements. We alsosurvey current trends and research that supports orchestration of big data workflows and identify open research challenges to guide future developments in this area. CCS Concepts: • General and reference → Surveys and overviews; • Information systems → Data analytics; • Computer systems organization → Cloud computing; Additional Key Words and Phrases: Big Data, Cloud Computing, Workflow Orchestration, Requirements, Approaches ACM Reference format: Mutaz Barika, Saurabh Garg, Albert Y. Zomaya, Lizhe Wang, Aad van Moorsel, and Rajiv Ranjan. 2018. Orchestrating Big Data Analysis Workflows in the Cloud: Research Challenges, Survey, and Future Directions.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • Rubyperf.Pdf
    Ruby Performance. Tips, Tricks & Hacks Who am I? • Ezra Zygmuntowicz (zig-mun-tuv-itch) • Rubyist for 4 years • Engine Yard Founder and Architect • Blog: http://brainspl.at Ruby is Slow Ruby is Slow?!? Well, yes and no. The Ruby Performance Dichotomy Framework Code VS Application Code Benchmarking: The only way to really know performance characteristics Profiling: Measure don’t guess. ruby-prof What is all this good for in real life? Merb Merb Like most useful code it started as a hack, Merb == Mongrel + Erb • No cgi.rb !! • Clean room implementation of ActionPack • Thread Safe with configurable Mutex Locks • Rails compatible REST routing • No Magic( well less anyway ;) • Did I mention no cgi.rb? • Fast! On average 2-4 times faster than rails Design Goals • Small core framework for the VC in MVC • ORM agnostic, use ActiveRecord, Sequel, DataMapper or roll your own db access. • Prefer simple code over magic code • Keep the stack traces short( I’m looking at you alias_method_chain) • Thread safe, reentrant code Merb Hello World No code is faster then no code • Simplicity and clarity trumps magic every time. • When in doubt leave it out. • Core framework to stay small and simple and easy to extend without gross hacks • Prefer plugins for non core functionality • Plugins can be gems Key Differences • No auto-render. The return value of your controller actions is what gets returned to client • Merb’s render method just returns a string, allowing for multiple renders and more flexibility • PartController’s allow for encapsualted applets without big performance cost Why not work on Rails instead of making a new framework? • Originally I was trying to optimize Rails and make it more thread safe.
    [Show full text]
  • Polycom Realpresence Cloudaxis Open Source Software OFFER
    Polycom® RealPresence® CloudAXIS™ Suite OFFER of Source for GPL and LGPL Software You may have received from Polycom®, certain products that contain—in part—some free software (software licensed in a way that allows you the freedom to run, copy, distribute, change, and improve the software). As a part of this product, Polycom may have distributed to you software, or made electronic downloads, that contain a version of several software packages, which are free software programs developed by the Free Software Foundation. With your purchase of the Polycom RealPresence® CloudAXIS™ Suite, Polycom has granted you a license to the above-mentioned software under the terms of the GNU General Public License (GPL), GNU Library General Public License (LGPLv2), GNU Lesser General Public License (LGPL), or BSD License. The text of these Licenses can be found at the internet address provided in Table A. For at least three years from the date of distribution of the applicable product or software, we will give to anyone who contacts us at the contact information provided below, for a charge of no more than our cost of physically distributing, the following items: • A copy of the complete corresponding machine-readable source code for programs listed below that are distributed under the GNU GPL • A copy of the corresponding machine-readable source code for the libraries listed below that are distributed under the GNU LGPL, as well as the executable object code of the Polycom work that the library links with The software included or distributed for the product, including any software that may be downloaded electronically via the internet or otherwise (the "Software") is licensed, not sold.
    [Show full text]
  • Next Generation Web Scanning Presentation
    Next generation web scanning New Zealand: A case study First presented at KIWICON III 2009 By Andrew Horton aka urbanadventurer NZ Web Recon Goal: To scan all of New Zealand's web-space to see what's there. Requirements: – Targets – Scanning – Analysis Sounds easy, right? urbanadventurer (Andrew Horton) www.morningstarsecurity.com Targets urbanadventurer (Andrew Horton) www.morningstarsecurity.com Targets What does 'NZ web-space' mean? It could mean: •Geographically within NZ regardless of the TLD •The .nz TLD hosted anywhere •All of the above For this scan it means, IPs geographically within NZ urbanadventurer (Andrew Horton) www.morningstarsecurity.com Finding Targets We need creative methods to find targets urbanadventurer (Andrew Horton) www.morningstarsecurity.com DNS Zone Transfer urbanadventurer (Andrew Horton) www.morningstarsecurity.com Find IP addresses on IRC and by resolving lots of NZ websites 58.*.*.* 60.*.*.* 65.*.*.* 91.*.*.* 110.*.*.* 111.*.*.* 113.*.*.* 114.*.*.* 115.*.*.* 116.*.*.* 117.*.*.* 118.*.*.* 119.*.*.* 120.*.*.* 121.*.*.* 122.*.*.* 123.*.*.* 124.*.*.* 125.*.*.* 130.*.*.* 131.*.*.* 132.*.*.* 138.*.*.* 139.*.*.* 143.*.*.* 144.*.*.* 146.*.*.* 150.*.*.* 153.*.*.* 156.*.*.* 161.*.*.* 162.*.*.* 163.*.*.* 165.*.*.* 166.*.*.* 167.*.*.* 192.*.*.* 198.*.*.* 202.*.*.* 203.*.*.* 210.*.*.* 218.*.*.* 219.*.*.* 222.*.*.* 729,580,500 IPs. More than we want to try. urbanadventurer (Andrew Horton) www.morningstarsecurity.com IP address blocks in the IANA IPv4 Address Space Registry Prefix Designation Date Whois Status [1] -----
    [Show full text]
  • Opennebula 5.4 Advanced Components Guide Release 5.4.6
    OpenNebula 5.4 Advanced Components Guide Release 5.4.6 OpenNebula Systems Jan 24, 2018 This document is being provided by OpenNebula Systems under the Creative Commons Attribution-NonCommercial- Share Alike License. THE DOCUMENT IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IM- PLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE DOCUMENT. i CONTENTS 1 Multi-VM Applications and Auto-scaling1 1.1 Overview.................................................1 1.2 OneFlow Server Configuration......................................1 1.3 OneFlow Services Management.....................................5 1.4 OneFlow Services Auto-scaling..................................... 19 1.5 Virtual Machine Groups (VM Groups)................................. 27 2 Host and VM High Availability 31 2.1 Overview................................................. 31 2.2 OpenNebula HA Setup.......................................... 31 2.3 Virtual Machines High Availability................................... 38 3 Data Center Federation 43 3.1 Overview................................................. 43 3.2 OpenNebula Federation Configuration.................................. 44 3.3 OpenNebula Federation Usage...................................... 47 4 Cloud Bursting 49 4.1 Overview................................................
    [Show full text]