DOCSLIB.ORG

Inselverwaltung Von Thorsten Scherf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

PRAXIS I Workshop Administration virtualisierter Infrastrukturen mit Archipel Inselverwaltung von Thorsten Scherf Virtuelle Maschinen-Instanzen laufen heutzutage auf einer Vielzahl unterschiedlicher Hypervisor-Systeme. Ein einheitliches Management-Tool ist notwendig, um den Zoo an virtuellen Systemen und deren Hosts im Überblick zu behalten und entsprechend zu verwalten. Mit Archipel steht nun ein recht neues Tool dieser Gattung zur Verfügung, das durch seine administrationsfreundliche Oberfläche besticht. Dieser Workshop stellt die Fähigkeiten des Management-Werkzeugs vor und zeigt dessen Inbetriebnahme. Quelle: pixelio.de eben dem Platzhirschen VMware eine ungesicherte wie auch mit TLS ge- zierung erfolgt wahlweise mittels eines N hat auch das Open Source-Umfeld schützte TCP-Verbindung übertragen. passenden SASL-Plug-Ins, beispielsweise viele sehr elegante und leistungsstarke Vir- Auch der Einsatz eines SSH-Tunnels ist Kerberos oder aber auch mit Hilfe von tualisierungswerkzeuge zu Tage gefördert. von Haus aus denkbar. Eine Authentifi- X.509-Zertifikaten. Die beiden Zugpferde sind hier sicherlich KVM (Kernel-based Virtual Machine) und XEN. Daneben existieren jedoch weitere Physikalische Architektur Lösungen wie beispielsweise VirtualBox, OpenVZ oder auch Linux-Container Physical Hypervisor Physical Hypervisor (LXC). Setzt ein Unternehmen nun un- Archipel Agent Archipel Agent terschiedliche Technologien ein, bedeutet dies im Umkehrschluss auch den Einsatz unterschiedlicher Management-Tools. Dass dies jedoch nicht zwangsläufig der Physical Hypervisor Physical Hypervisor Fall sein muss, ist spätestens seit Erscheinen des Virtualisierung-Frameworks libvirt be- Archipel Agent Archipel Agent kannt. Das Framework bringt diverse Trei- ber für den Zugriff auf die unterschied- lichsten Virtualisierungstechnologien von XMPP Hause aus mit [1] und gestattet somit ei- XMPP Server HTTP Server nen einheitlichen Zugriff auf virtuelle Maschinen unabhängig davon, auf wel- EJabberd Archipel GUI chem Hypervisor diese laufen. Als Management-Tools stehen für libvirt XMPP (bosh) HTTP / HTTPS auf der Kommandozeile virsh und virt- install zum Verwalten und Erzeugen von virtuellen Maschinen-Instanzen zur Ver- User computer User computer User computer fügung und mit virt-manager existiert ein grafisches Frontend. Die Tools müssen Safari / Webkit Safari / Webkit Safari / Webkit dabei nicht zwingend auf dem jeweiligen Hypervisor installiert sein und ein Re- mote-Zugriff ist ohne weiteres möglich. Um die Daten zwischen der Workstation und dem Hypervisor zu übertragen, exis- tieren diverse Möglichkeiten: So lässt sich Bild 1: Bei Archipel kommen diverse OpenSource-Komponenten zum Einsatz. Die zentrale Rolle spielt dabei ein beispielsweise der IP-Traffic sowohl über XMPP-Server, der für die Echtzeit-Kommunikation zwischen den einzelnen Komponenten verantwortlich ist. www.it-administrator.de August 2011 45 PRAXIS I Workshop Dank der großen Flexibilität von libvirt Komponente, die auf jedem Hypervisor- # /etc/ejabberd/ejabberd.cfg kommt es in diversen anderen Virtualisie- System zu installieren ist und als eine Art {loglevel, 4}. rungs-Projekten zum Einsatz, so beispiels- Bindeglied zwischen dem XMPP-Server {hosts, [“rawhide.tuxgeek.de”,”tuxgeek.de”, ”localhost”]}. weise in oVirt [2] oder aber auch in Archipel und dem libvirt-Framework des Hypervi- {listen, [3]. Archipel ersetzt dabei die etwas ange- sors dient. Der Agent selbst kommuniziert [ {5222, ejabberd_c2s, [ staubte GTK+-Oberfläche des virt-mana- gar nicht mit dem Hypervisor sondern {access, c2s}, {shaper, c2s_shaper}, gers durch eine schicke und modere Cap- überlässt diese Aufgabe libvirt. Somit ist ein {max_stanza_size, 65536} puccino-basierte Oberfläche und fügt Zugriff auf sämtliche Hypervisoren mög- ]}, {5269, ejabberd_s2s_in, [ weitere Features, die beispielsweise virt-ma- lich, die libvirt unterstützt. Der Archipel- {shaper, s2s_shaper}, nager nicht besitzt, hinzu. Dank des JavaS- Client ist dabei die Komponente, die – {max_stanza_size, 131072} ]}, cript-basierten Frameworks, erfolgt der Zu- meistens zusammen mit dem XMPP-Ser- {5280, ejabberd_http, [ griff auf Archipel über nahezu jeden ver – auf einem zentralen Management- captcha, http_bind, beliebigen Webbrowser – eine zusätzliche Server läuft und die jedem zugreifenden http_poll, web_admin Anwendung oder eine lokale libvirt-Instal- Client eine hübsche Weboberfläche prä- ]} lation sind dabei nicht notwendig. sentiert. Der komplette Client ist dabei in ]}. {auth_method, internal}. Javascript geschrieben und basiert auf dem {shaper, normal, {maxrate, 1000}}. XMPP-Server als zentrale Strophe.js-Framework. Archipel erzeugt {shaper, fast, {maxrate, 50000}}. {max_fsm_queue, 1000}. Architektur-Komponente zur Weiterverarbeitung Cappuchino-Ob- {acl, local, {user_regexp, “”}}. {access, max_user_sessions, [{10, all}]}. Archipel besteht aus mehreren Kompo- jekte. Diese lassen sich dann mit nahezu {access, max_user_offline_messages, [{5000, nenten die untereinander über das bekann- jedem beliebigen Javascript fähigen Web- admin}, {100, all}]}. {access, local, [{allow, local}]}. te XMPP-Protokoll (ehemals Jabber) kom- brower abrufen. Bild 1 zeigt die Architektur {access, c2s, [{deny, blocked}, munizieren. Die Zustellung von Nach- des Archipel-Frameworks. {allow, all}]}. {access, c2s_shaper, [{none, admin}, richten findet somit nahezu in Echtzeit {normal, all}]}. statt. Zentrale Komponente der gesamten {access, s2s_shaper, [{fast, all}]}. Installation {access, announce, [{allow, admin}]}. Architekur ist ein XMPP-Server der als Kommt der ejabberd-Server als XMPP- {access, configure, [{allow, admin}]}. {access, muc_admin, [{allow, admin}]}. eine Art Nachrichtenzentrale agiert. Die Komponente zum Einsatz, so ist darauf zu {access, muc_create, [{allow, local}]}. Archipel-Entwickler empfehlen den Ein- achten, dass dieser die beiden Module {access, muc, [{allow, all}]}. {access, pubsub_createnode, [{allow, local}]}. satz des ejabberd-Servers, jedoch sollte “mod_admin_extra” und “ejabberd_ {access, register, [{allow, all}]}. auch jeder andere XMPP-Server funktio- xmlrpc” enthält. Ist dies nicht der Fall, müs- {language, “en”}. {modules, nieren. Die ejabberd-Software ist Bestand- sen Sie diese manuell nachliefern. Hierzu [ {mod_adhoc, []}, teil sämtlicher Linux-Distributionen und verwenden Sie die Sourcen der ejabberd- {mod_caps, []}, lässt sich somit recht einfach über den je- Module und das Erlang-XMLRPC-Archiv {mod_disco, []}, {mod_irc, []}, weiligen Paket-Manager installieren. und übersetzen diese. Unter Umständen {mod_http_bind, []}, sind noch die Dateisystem-Pfade im Ma- {mod_last, []}, {mod_muc, [ Über die Download-Seite von Archipel [4] kefile anzupassen, dies hängt von der ein- {access, muc}, stehen dann die beiden Komponenten Ar- gesetzten Linux-Distribution ab. Die resul- {access_create, muc_create}, {access_persistent, muc_create}, chipel-Agent und Archipel-Client zur Ver- tierenden beam-Dateien gehören dann in {access_admin, muc_admin} ]}, fügung. Beim Agent handel es sich um die das ebin-Verzeichnis des ejabberd-Servers {mod_offline, [{access_max_user_messages, (Listing 1 und Listing 2). max_user_offline_messages}]}, {mod_ping, []}, cd /usr/local/src {mod_privacy, []}, wget http://ejabberd.jabber.ru/files/ Hat dies soweit funktioniert, müssen Sie {mod_private, []}, contributions/xmlrpc-1.13-ipr2.tgz {mod_pubsub, [ tar -xzf xmlrpc-1.13-ipr2.tgz schließlich noch die Konfigurationsdatei {access_createnode, pubsub_createnode}, cd xmlrpc-1.13/src {last_item_cache, false}, make des XMPP-Servers anpassen. Hierbei han- ]}, cp - a ebin/*.beam /usr/lib/ejabberd/ebin/ delt es sich um die Datei /etc/ejabberd/ejab- {mod_register, [ {welcome_message, {“Welcome!”, berd.cfg. Wichtig ist hierbei, dass Sie den Listing 1: Installation des “Hi.\nWelcome to this XMPP lokalen Rechnernamen und die zusätzlich server.”}}, ejabberd_xmlrpc Moduls {ip_access, [{allow, “127.0.0.0/8”}, installierten ejabberd-Module korrekt an- {deny, “0.0.0.0/0”}]}, {access, register} geben. Listing 3 zeigt eine beispielhafte ]}, cd /usr/local/src Konfiguration (die ejabberd Default-Kon- {mod_roster, []}, svn checkout http://svn.process-one.net/ {mod_shared_roster,[]}, ejabberd-modules/ figuration wollte in unserem Praxis-Test {mod_stats, []}, cd mod_admin_extra/trunk/ nicht mit Archipel zusammenarbeiten). {mod_time, []}, ./build.sh {mod_vcard, []}, cp ebin/mod_admin_extra.beam {mod_version, []} /usr/lib/ejabberd/ebin/ Der Aufruf von /etc/init.d/ejabberd start ak- ]}. Listing 2: Installation des tiviert schließlich den Server. Sollten Fehler Listing 3: Die Konfigurationsdatei ejabberd_xmlrpc Moduls auftreten, so finden Sie die entsprechenden des XMPP-Servers Logeinträge in der Datei /var/log/ejabberd/ 46 August 2011 Alle Listings zum Download auf www.it-administrator.de PRAXIS I Workshop nutzen Sie entweder den letzten Night- lyBuild oder den letzten StableBuild [4]. Noch einfacher gelingt die Installation über den zentralen Python Package Index (PyPi) – dies setzt jedoch eine Internet- Verbindung und das Paket python-setup- tools auf den Hypervisor-Systemen vo- raus. Über den Aufruf von easy_install archipel-agent installieren Sie dann den Ar- chipel-Agent auf dem lokalen System. In der Konfigurationsdatei /etc/archipel/ar- chipel.conf müssen Sie wieder darauf ach- ten, dass der richtige Rechnername für Bild 2: Nach der Installation des Management-Systems steht dieses für erste Zugriffe bereit den lokalen Hypervisor und den zentralen XMPP-Server zum Einsatz kommen. ejabberd.log. Um die
Recommended publications
  • Open Virtualization Infrastructure for Large Telco: How Turkcell Adopted Ovirt for Its Test and Development Environments

    Open Virtualization Infrastructure for Large Telco: How Turkcell Adopted Ovirt for Its Test and Development Environments

    Open Virtualization Infrastructure for large Telco: How Turkcell adopted oVirt for its test and development environments DEVRIM YILMAZ SAYGIN BAKTIR Senior Expert Cloud Engineer Cloud Systems Administrator 09/2020 This presentation is licensed under a Creative Commons Attribution 4.0 International License About Turkcell ● Turkcell is a digital operator headquartered in Turkey ● Turkcell Group companies operate in 5 countries – Turkey, Ukraine, Belarus, Northern Cyprus, Germany ● Turkcell is the only NYSE-listed company in Turkey. ● www.turkcell.com.tr 3 Business Objectives ● Alternative solutions compatible with Turkcell operational and security standards ● Dissemination of open source infrastructure technologies within the company ● Competitive infrastructure with cost advantage 3 The journey of oVirt 4 The Journey of oVirt 3. Step three 1. Research & 2. Go-Live 3. Go-Live 4. Private Cloud 5. Go-Live Development Phase-1 Phase-2 Automation RHV 5 Research & Development ● Motivation Factors ○ Cost 1. Research & ○ Participation Development ○ Regulation ○ Independence ○ Expertise ● Risk Factors ○ Security ○ Quality ○ Compliance ○ Support ○ Worst Practices 6 Research & Development ● Why oVirt? ○ Open Source licensing 1. Research & ○ Community contribution Development ○ The same roadmap with commercial product ○ Support via subscription if required ○ Adequate features for enterprise management ○ Rest API support 6 Research & Development ● Difficulties for new infra solution ○ Integration with current infrastructure 1. Research & - Centralized Management Development - Certified/Licensed Solutions - Integration Cost ○ Incident & Problem Management - 3rd Party Support - Support with SLA ○ Acquired Habits - Customer Expectations - Quality of IT Infrastructure Services 6 Research & Development ● What we achieved ○ Building of PoC environment 1. Research & ○ V2V Migration Development ○ Upgrade Tests starting with v.4.3.2 ○ Functional Tests ○ Backup Alternative Solutions 6 Go-Live Phase-1 ● Phase-1 contains : ○ Building of new oVirt platform with unused h/w 2.
  • VDI with UDS Enterprise and Microsoft Hyper-V

    VDI with UDS Enterprise and Microsoft Hyper-V

    UDS Enterprise VDI with UDS Enterprise & Microsoft Hyper-V www.udsenterprise.com About UDS Enterprise UDS Enterprise functionalities UDS Enterprise is a multiplatform connection broker . Scalable platform. It supports configurations for: in high availability by deploying several UDS Enterprise brokers in cluster . VDI: Windows and Linux virtual desktops . Unlimited number of configurations thanks to administration and deployment its additional module management system . Windows and Linux app virtualization and the definition of configuration variables . Desktop services consolidation on two levels: . Remote access to physical and virtual devices o Definition of configuration variables at system level UDS Enterprise is ideal for managing workstations o Definition of independent module because, among other functions, it allows you to configuration variables perform the following tasks: . Virtual desktop cache system in two levels for fast connection . Manage the life cycle of the endpoint . Administer and manage Windows and Linux . Management of unlimited services (Microsoft virtual desktops, virtualized applications and Hyper-V, Microsoft Azure, VMware vSphere, IP services deployed on different platforms Nutanix Acropolis, OpenNebula, OpenStack, from a single console Proxmox, oVirt, Terminal Server…) . Connect users and user groups of different . Unlimited user and device authentication authentication systems at the same time with systems (AD, Microsoft Azure Active virtual desktops and different IP services Directory, eDirectory, LDAP, SAML, internal . Connect users with remote desktop services by enabling one or more connection authentication system, authentication by IP) protocols at the same time . Log visualization system and system . Define policies for the use of deployed virtual statistics desktops or other resources . Deployment of virtual desktops in multiple . Deploy template-based virtual desktops hypervisors at the same time and managed .
  • Tools for Cloud Infrastructure: Build & Release

    Tools for Cloud Infrastructure: Build & Release

    Tools for Cloud Infrastructure: Build & Release With source code management tools like Git, we can easily version the code and retrieve the same bits we saved in the past. This saves a lot of time and helps developers automate most of the non-coding activities, like creating automated builds, running tests, etc. Extending the same analogy to infrastructure would allow us to create a reproducible deployment environment, which is referred to as Infrastructure as a Code. Infrastructure as a Code helps us create a near production-like environment for development, staging, etc. With some tooling around them, we can also the create same environments on different cloud providers. By combining Infrastructure as a Code with versioned software, we are guaranteed to have a re-producible build and release environment every time. In this chapter we will take a look into two such tools: Terraform and BOSH. Introduction to Terraform Terraform is a tool that allows us to define the infrastructure as code. This helps us deploy the same infrastructure on VMs, bare metal or cloud. It helps us treat the infrastructure as software. The configuration files can be written in HCL (HashiCorp Configuration Language). Terraform Providers Physical machines, VMs, network switches, containers, etc. are treated as resources, which are exposed by providers. A provider is responsible for understanding API interactions and exposing resources, which makes Terraform agnostic to the underlying platforms. A custom provider can be created through plugins. Terraform has providers in different stacks: IaaS: AWS, DigitalOcean, GCE, OpenStack, etc. PaaS: Heroku, CloudFoundry, etc. SaaS: Atlas, DNSimple, etc. Features According to the Terraform website, it has following "key features: Infrastructure as Code: Infrastructure is described using a high-level configuration syntax.
  • Model to Implement Virtual Computing Labs Via Cloud Computing Services

    Model to Implement Virtual Computing Labs Via Cloud Computing Services

    S S symmetry Article Model to Implement Virtual Computing Labs via Cloud Computing Services Washington Luna Encalada 1,2,* ID and José Luis Castillo Sequera 3 ID 1 Department of Informatics and Electronics, Polytechnic School of Chimborazo, Riobamba 060155, EC, Ecuador 2 Department of Doctorate in Systems Engineering and Computer Science, National University of San Marcos, Lima 15081, Peru; [email protected] 3 Department of Computer Sciences, Higher Polytechnic School, University of Alcala, 28871 Alcala de Henares, Spain; [email protected] * Correspondence: [email protected]; Tel.: +593-032-969-472 Academic Editor: Yunsick Sung Received: 1 May 2017; Accepted: 3 July 2017; Published: 13 July 2017 Abstract: In recent years, we have seen a significant number of new technological ideas appearing in literature discussing the future of education. For example, E-learning, cloud computing, social networking, virtual laboratories, virtual realities, virtual worlds, massive open online courses (MOOCs), and bring your own device (BYOD) are all new concepts of immersive and global education that have emerged in educational literature. One of the greatest challenges presented to e-learning solutions is the reproduction of the benefits of an educational institution’s physical laboratory. For a university without a computing lab, to obtain hands-on IT training with software, operating systems, networks, servers, storage, and cloud computing similar to that which could be received on a university campus computing lab, it is necessary to use a combination of technological tools. Such teaching tools must promote the transmission of knowledge, encourage interaction and collaboration, and ensure students obtain valuable hands-on experience.
  • Attacker Chatbots for Randomised and Interactive Security Labs, Using Secgen and Ovirt

    Attacker Chatbots for Randomised and Interactive Security Labs, Using Secgen and Ovirt

    Hackerbot: Attacker Chatbots for Randomised and Interactive Security Labs, Using SecGen and oVirt Z. Cliffe Schreuders, Thomas Shaw, Aimée Mac Muireadhaigh, Paul Staniforth, Leeds Beckett University Abstract challenges, rewarding correct solutions with flags. We deployed an oVirt infrastructure to host the VMs, and Capture the flag (CTF) has been applied with success in leveraged the SecGen framework [6] to generate lab cybersecurity education, and works particularly well sheets, provision VMs, and provide randomisation when learning offensive techniques. However, between students. defensive security and incident response do not always naturally fit the existing approaches to CTF. We present 2. Related Literature Hackerbot, a unique approach for teaching computer Capture the flag (CTF) is a type of cyber security game security: students interact with a malicious attacker which involves collecting flags by solving security chatbot, who challenges them to complete a variety of challenges. CTF events give professionals, students, security tasks, including defensive and investigatory and enthusiasts an opportunity to test their security challenges. Challenges are randomised using SecGen, skills in competition. CTFs emerged out of the and deployed onto an oVirt infrastructure. DEFCON hacker conference [7] and remain common Evaluation data included system performance, mixed activities at cybersecurity conferences and online [8]. methods questionnaires (including the Instructional Some events target students with the goal of Materials Motivation Survey (IMMS) and the System encouraging interest in the field: for example, PicoCTF Usability Scale (SUS)), and group interviews/focus is an annual high school competition [9], and CSAW groups. Results were encouraging, finding the approach CTF is an annual competition for students in Higher convenient, engaging, fun, and interactive; while Education (HE) [10].
  • Ovirt and Openstack Storage (Present and Future)

    Ovirt and Openstack Storage (Present and Future)

    oVirt and OpenStack Storage (present and future) Federico Simoncelli Principal Software Engineer, Red Hat January 2014 1 Federico Simoncelli – oVirt and OpenStack Storage (present and future) Agenda ● Introduction ● oVirt and OpenStack Overview ● Present ● oVirt and Glance Integration ● Importing and Exporting Glance Images ● Current Constraints and Limitations ● Future ● Glance Future Integration ● Keystone Authentication in oVirt ● oVirt and Cinder Integration 2 Federico Simoncelli – oVirt and OpenStack Storage (present and future) oVirt Overview ● oVirt is a virtualization management application ● manages hardware nodes, storage and network resources, in order to deploy and monitor virtual machines running in your data center ● Free open source software released under the terms of the Apache License 3 Federico Simoncelli – oVirt and OpenStack Storage (present and future) The oVirt Virtualization Architecture 4 Federico Simoncelli – oVirt and OpenStack Storage (present and future) OpenStack Overview ● Cloud computing project to provide an Infrastructure as a Service (IaaS) ● Controls large pools of compute, storage, and networking resources ● Free open source software released under the terms of the Apache License ● Project is managed by the OpenStack Foundation, a non-profit corporate entity established in September 2012 5 Federico Simoncelli – oVirt and OpenStack Storage (present and future) OpenStack Glance Service ● Provides services for discovering, registering, and retrieving virtual machine images ● RESTful API that allows querying
  • Ovirt and Docker Integration

    Ovirt and Docker Integration

    oVirt and Docker Integration October 2014 Federico Simoncelli Principal Software Engineer – Red Hat oVirt and Docker Integration, Oct 2014 1 Agenda ● Deploying an Application (Old-Fashion and Docker) ● Ecosystem: Kubernetes and Project Atomic ● Current Status of Integration ● oVirt Docker User-Interface Plugin ● “Dockerized” oVirt Engine ● Docker on Virtualization ● Possible Future Integration ● Managing Containers as VMs ● Future Multi-Purpose Data Center oVirt and Docker Integration, Oct 2014 2 Deploying an Application (Old-Fashion) ● Deploying an instance of Etherpad # yum search etherpad Warning: No matches found for: etherpad No matches found $ unzip etherpad-lite-1.4.1.zip $ cd etherpad-lite-1.4.1 $ vim README.md ... ## GNU/Linux and other UNIX-like systems You'll need gzip, git, curl, libssl develop libraries, python and gcc. *For Debian/Ubuntu*: `apt-get install gzip git-core curl python libssl-dev pkg- config build-essential` *For Fedora/CentOS*: `yum install gzip git-core curl python openssl-devel && yum groupinstall "Development Tools"` *For FreeBSD*: `portinstall node, npm, git (optional)` Additionally, you'll need [node.js](http://nodejs.org) installed, Ideally the latest stable version, be careful of installing nodejs from apt. ... oVirt and Docker Integration, Oct 2014 3 Installing Dependencies (Old-Fashion) ● 134 new packages required $ yum install gzip git-core curl python openssl-devel Transaction Summary ================================================================================ Install 2 Packages (+14 Dependent
  • Oracle® Linux Virtualization Manager Getting Started Guide

    Oracle® Linux Virtualization Manager Getting Started Guide

    Oracle® Linux Virtualization Manager Getting Started Guide F25124-11 September 2021 Oracle Legal Notices Copyright © 2019, 2021 Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
  • Paas Solutions Evaluation

    Paas Solutions Evaluation

    PaaS solutions evaluation August 2014 Author: Sofia Danko Supervisors: Giacomo Tenaglia Artur Wiecek CERN openlab Summer Student Report 2014 CERN openlab Summer Student Report 2014 Project Specification OpenShift Origin is an open source software developed mainly by Red Hat to provide a multi- language PaaS. It is meant to allow developers to build and deploy their applications in a uniform way, reducing the configuration and management effort required on the administration side. The aim of the project is to investigate how to deploy OpenShift Origin at CERN, and to which extent it could be integrated with CERN "Middleware on Demand" service. The student will be exposed to modern cloud computing concepts such as PaaS, and will work closely with the IT middleware experts in order to evaluate how to address service needs with a focus on deployment in production. Some of the tools that are going to be heavily used are Puppet and Openstack to integrate with the IT infrastructure. CERN openlab Summer Student Report 2014 Abstract The report is a brief summary of Platform as a Service (PaaS) solutions evaluation including investigation the current situation at CERN and Services on Demand provision, homemade solutions, external market analysis and some information about PaaS deployment process. This first part of the report is devoted to the current status of the process of deployment OpenShift Origin at existing infrastructure at CERN, as well as specification of the common issues and restrictions that were found during this process using different machines for test. Furthermore, the following open source software solutions have been proposed for the investigation of possible PaaS provision at CERN: OpenShift Online; Cloud Foundry; Deis; Paasmaster; Cloudify; Stackato; WSO2 Stratos.
  • Openshift Vs Pivotal Cloud Foundry Comparison Red Hat Container Stack - Pivotal Cloud Foundry Stack

    Openshift Vs Pivotal Cloud Foundry Comparison Red Hat Container Stack - Pivotal Cloud Foundry Stack

    OPENSHIFT VS PIVOTAL CLOUD FOUNDRY COMPARISON RED HAT CONTAINER STACK - PIVOTAL CLOUD FOUNDRY STACK 3 AT A GLANCE PIVOTAL CF OPENSHIFT • ●Garden and Diego • ●Docker and Kubernetes • ●.NET and Spring • ●.NET, Spring and JBoss Middleware • ●Only Cloud-native apps (including full Java EE) • ●Container security on Ubuntu • ●Cloud-native and stateful apps • ●Deployment automation • ●Enterprise-grade security on • ●Open Core Red Hat Enterprise Linux • ●Pivotal Labs consulting method • ●Complete Ops Management • ●100% Open Source 5X PRICE • ●Red Hat Innovation Labs consulting method BRIEF COMPARISON PIVOTAL CF OPENSHIFT GARDEN & DIEGO DOCKER & KUBERNETES • ●Garden uses OCI runC backend • ●Portable across all docker platforms • ●Not portable across Cloud Foundry distros • ●IP per container • ●Containers share host IP • ●Integrated image registry • ●No image registry • ●Image build from source and binary • ●Private registries are not supported • ●Adoption in many solutions • ●No image build • ●Adoption only in Cloud Foundry 11 NO NATIVE DOCKER IN CLOUD FOUNDRY Converters Are Terrible Cloud Foundry is based on the Garden container runtime, not Docker, and then has RunC and Windows backends. RunC is not Docker, just the lowest runtime layer Docker Developer Experience Does Not Exist in PCF PCF “cf push” Dev Experience does not exist for Docker. In Openshift v3 we built S2I to provide that same experience on top of native Docker images/containers Diego Is Not Kubernetes Kubernetes has become the defacto standard for orchestrating docker containers.
  • Red Hat Openshift 4.2 on Dell EMC Vxflex Ready Nodes Installation and Configuration Overview with Vxflex Ready Nodes

    Red Hat Openshift 4.2 on Dell EMC Vxflex Ready Nodes Installation and Configuration Overview with Vxflex Ready Nodes

    White Paper White Paper Red Hat OpenShift 4.2 on Dell EMC VxFlex Ready Nodes Installation and Configuration overview with VxFlex Ready Nodes Abstract This white paper provides guidance on deployment and exercising basic functionality of Red Hat® OpenShift® Container Platform on Dell EMC VxFlex Ready Nodes for customers requiring an on-premises container platform solution. March 2020 000062 Revisions Revisions Date Description March 2020 Initial release Acknowledgements This paper was produced by the following: Author: Sunil Kumar HS and Raghavendra Biligiri Support: Raghvendra Tripathi, David J Adams and Shalini G The information in this publication is provided “as is.” Dell Inc. makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any software described in this publication requires an applicable software license. Copyright © 2020 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. [3/27/2020] [White Paper] [000062] 2 Red Hat OpenShift 4.2 on Dell EMC VxFlex Ready Nodes | 000062 Table of contents Table of contents Revisions............................................................................................................................................................................. 2 Acknowledgements
  • From a Pipeline to a Government Cloud

    From a Pipeline to a Government Cloud

    From a pipeline to a government cloud Toby Lorne SRE @ GOV.UK Platform-as-a-Service www.toby.codes github.com/tlwr github.com/alphagov From a pipeline to a government cloud How the UK government deploy a Platform-as-a-Service using Concourse, an open-source continuous thing-doer From a pipeline to a government cloud 1. GOV.UK PaaS overview 2. Concourse overview 3. Pipeline walkthrough 4. Patterns and re-use What is GOV.UK PaaS? What is a Platform-as-a Service? What are some challenges with digital services in government? How does GOV.UK PaaS make things better? What is a PaaS? Run, manage, and maintain apps and backing services Without having to buy, manage, and maintain infrastructure or needing specialist expertise Here is my source code Run it for me in the cloud I do not care how Deploy to production safer and faster Reduce waste in the development process Proprietary Open source Heroku Cloud Foundry Pivotal application service DEIS EngineYard Openshift Google App Engine kf AWS Elastic Beanstalk Dokku Tencent BlueKing Rio Why does government need a PaaS? UK-based web hosting for government services Government should focus on building useful services, not managing infrastructure Enable teams to create services faster Reduce the cost of procurement and maintenance An opinionated platform promotes consistency Communication within large bureaucracies can be slow Diverse app workloads are impossible to reason about Highly leveraged team requires trust and autonomy Only able to do this because of open source software and communities APPS