DOCSLIB.ORG

6162 - How to Build and Operate Your Private Cloud with Ubuntu on IBM Power Systems and Openpower

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
6162 - How to Build and Operate Your Private Cloud with Ubuntu on IBM Power Systems and Openpower #6162 - How to Build and Operate Your Private Cloud with Ubuntu on IBM Power Systems and OpenPOWER Ivan Doboš, Solutions Architect, IHV team Canonical Think Conference March 2018 Delivering the economics and agility of hyperscale innovators to enterprises globally Developer productivity | Infrastructure economics 2 IBM / Canonical Power Relationship ● 14.04 LTS first release (April 2014) ● First commercial Linux to support: ■ POWER8 LE ■ CAPI ■ KVM, PowerKVM ■ Docker, LXC, LXD ■ Cloud Foundry ● Canonical is Platinum OpenPower Member ○ Robbie Williamson - Chairman of the Board) ○ Ivan Doboš - Technical Steering Committee ● Ubuntu Open Source ecosystem available for Power; IBM software charms available now Why cloud? ● (Hyper)scale ● Flexibility ● Efficiency ==> better economics ● Successful cloud – Hosting applications – Growing (scaling out) – Providing new features (Regular upgrades) – minimizing operational costs by Automation From bare metal to containers ... ● Hardware (compute, network, storage) ● Operating system ● Applications ● Containers ● Applications ● Containers * ● Applications ● Hypervisor ● Virtual Machines ● Operating System ● Applications ● Containers ● Application * nested containers, Docker under LXD example Cloud Solution Stack: Enabling Operations at Scale Landscape: Systems management & patching Juju Juju: Cloud deployment, integration, scaling, upgrading LXD: Pure-container VMs - Containers Containers (Docker) hypervisor KVM (LXD) Ubuntu OpenStack: Canonical-produced Kubernetes: optimized and interop OpenStack Kubernetes Docker Container tested openstack e coordination p packages a c Enterprise-class, s d hyperscale server n Ubuntu Server operating system a L MAAS: Metal-as-a- MAAS Service for bare-metal provisioning 6 Cloud Edge Elastic hybrid cloud Transactional Edge ( IoT ) Public Public Clouds Clouds Bulk compute data center First things first – Bare metal maas.io Key to Private DC Economics is Automation MAAS Feature Matrix SDDC User Interfaces Disk layout BMC protocols ● IPAM, DNS and DHCP ● Web ● Partitioned ● IPMI ● Dynamic allocation ● REST API ● Raw ● AMT * ● Availability Zones ● CLI ● RAID ● Redfish ● Python ● LVM Chassis support ● bcache Operating Systems ● SSH & BMC credential setup ● Cisco UCS Host NIC config ● Microsoft OCS ● Auto-enlistment via PXE ● CentOS 6, 7 ● Seamicro 15K ● Hardware inventory ● RHEL 6,7 ● Raw ● HP Moonshot ● Auto-tagging ● Ubuntu ● Tagged VLAN ● Custom commissioning ● Windows 2003, 2010 ● Bonded VM Controllers ● Post-install configuration ● Custom ● Bridged* ● KVM Virsh ● PowerKVM ● vSphere Time from request to VM Cloud Metal Request Procure >>> from boto import ec2 >>> c = ec2.connect('us-west-2') Rack >>> r = c.run_instances( Firmware min_count=3, Configure aws_image_id, Install OS instance_type='c1.xlarge') Launch Credentials Automation The devil in the details Node Network Discovery PXE & TFTP DNS, NTP & more bind, ntpd HW inventory lshw Topology & addressing IPAM BMC freeipmi L2 & L3 config DHCP BIOS & firmware fwupd Boot process BIOS & UEFI Infrastructure OS Deployment curtin DCIM Diskless / Ephemeral iSCSI PDUs OpenFlow Storage & Networking cloud-init Switches & routers SNMP MIBs Decommissioning NIST-wipe Storage appliances Vendor stuf MAAS The bare metal API Inventory. Commission. Deploy. IP, DHCP, DNS, PXE, IPMI ready to roll 1 Automated physical provisioning 2 Dynamic allocation to workloads 3 IP Address Management (IPAM) 4 Web interface and REST API 5 Windows, Linux OS install Ubuntu, RHEL, SUSE Windows Custom images Application modeling Machine MAAS configuration “Please give me up a machine of ppc64el architecture, with 24 GB RAM, a root disk of 300GB and at least 6 more 3TB Operator setup disks, with an nVidia GPGPU running Ubuntu.” MAAS 2.0 Changes the provisioning game 100k servers in a Region HA Region Controller (1-3 servers) - highly available - users and groups Rack Controller Rack Controller - resource allocation - central postgres db * ideally on switch - machine inventory * typically in-rack Server * cache of images Single view of server status, API * backup for adjacent racks Server endpoint, web UI. Provides PXE boot and local OS image delivery for installation. Server Server Server Server Server Server Server Server Server Server Server High Availability for Region & Rack services ○ Region HA Region Region ○ Rack HA Rack 1 Rack 2 Rack 3 ubuntu.com/lxd github.com/lxc linuxcontainers.org LXC 2.0 adds the LXD container hypervisor LXD provides machine containers Virtual Linux Machines Containers Machine containers Physical Machines LXD is Canonical’s container hypervisor ➢ Ultra fast “vm-lite” guests (bare metal speed) lxc ➢ Anylxc distribution of Linuxlxc - e.g. Ubuntu, CentOSlxc lxc machine ➢machineStarts in less than machine1 second machine machine ➢ 15x density of KVM or ESX for idle workloads kernel lxd kernel lxd kernel lxd kernel lxd kernel lxd host A host B host C host D host ... LXD REST API nova-lxd lxc cli other restful apps LXD – benefits for Cloud ● Lift and shift for existing applications ● Collocation of different workloads on the same node – Hyper-converged architecture as a default for Canonical OpenStack ● More efficient way of using instances in cloud – typically an instance in Cloud = VM – Run containers inside an instance ● Instances in cloud implemented as LXC containers – LXD as a supported hypervisor for OpenStack – 14x greater density with LXD than with VMs (tested on x86), lower latency Operate big software at scale on any cloud jujucharms.com the phase change of modern software scarcity has shifted from code to ops (Are you ready to operate a SW you don’t understand?) How to fix it? ● Imagine ‘open source operations’ – Free, downloadable, driven by the community and/or SW vendors – Reflecting the release changes of the applications to operate – Providing functions like: ● installation/uninstallation ● upgrades ● configuration management ● scale ● integration between applications ● ‘must to have’ generic and also application specific actions: backup, restore, pause/restart, ... – ? – reuse operations code in completely different architectures Reuse across clouds developer laptop gce / azure / oracle (lxd containers) your app test and dev vm’s aws vmware bare metal openstack Ubuntu OpenStack 65% of large production OpenStack deployments run Ubuntu Canonical OpenStack Management & Infrastructure Automation Services Nova Horizon Landscape Ceilometer Keystone Neutron /Telemetry Swift Cinder Glance Juju Ubuntu 16.04 LTS MAAS 14 OpenStack Architecture example MySQL/0 MySQL/1 MySQL/2 rabbit/0 rabbit/1 rabbit/2 keystone/0 keystone/1 keystone/2 horizon/0 horizon/1 horizon2 Swift Swift Swift Neutron/0 Neutron/1 Neutron/2 Ceph Ceph Ceph pgsql/0 pgsql/1 pgsql/2 cinder/0 cinder/1 cinder/2 MongoDB0 MongoDB1 MongoDB2 Ceilo/0 Ceilo/1 Ceilo/2 glance/0 glance/1 glance/2 juju 0 juju 1 juju3 MAAS 1 LDS0 LDS1 LDS2 Nova-KVM Nova-LXD Baremetal Virtual Machine Linux Container (LXC) OpenStack Archive Upgrade Guarantee 14.04 14.10 15.04 15.10 16.04 16.10 17.04 17.10 18.04 18.10 19.04 Queens LTS Ubuntu 18.04 LTS 5 years Queens LTS Pike 18 months Ocata 18 months extra 18 months for customers Newton 18 months Mitaka LTS 5 years Ubuntu 16.04 LTS 5 years Mitaka LTS 5 years Liberty 18 months Kilo 18 months extra 18 months for customers Juno 18 months Icehouse LTS 5 years Ubuntu 14.04 LTS 5 years Canonical’s distribution of Kubernetes easy, stable, latest release of upstream any CPU architecture x86 s390x extensible by design NFS rich accessory ecosystem Why Canonical? Most popular cloud and Launch partner as a KCSP container operating system Why Canonical Kubernetes? Pure upstream, latest & greatest versions Operates on AWS, Azure, GCE, OpenStack, VMWare Bare metal operations with MAAS 100% compatible with Google’s Kubernetes Secured. TLS, Kernel Live patching, confinement Upgradable between each Kubernetes Release Cost efective at scale Support for GPUs ● Automated GPU Discovery ● Live GPU adjustments ● Automated configuration of applications LXD, Kubernetes & GPUs * Conclusion Hardware Cloud ARM64 Single Host Bare Metal Cluster Cloud Cluster Single Host Cloud Cluster Juju + helm, sudo give me Artificial Intelligence: check! *coming soon to IBM Power In Summary ➢ Ubuntu #1 Linux for Cloud, ScaleOut, Dev Ops – >65% Production OpenStack clouds are Ubuntu – Juju and related cloud tooling supports DevOps speed ➢ Operating on premise with the efficiency and flexibility of a public cloud – Combine maas, LXD, Juju and OpenStack as needed ➢ Ubuntu on IBM Systems: great Ubuntu experience on IBM Power and IBM Z/LinuxONE – Global Partnership with IBM * Canonical & Open Source * Thank You! [email protected] .
Load more

Recommended publications
  • Upgrading Cfengine Nova a Cfengine Special Topics Handbook
    Upgrading CFEngine Nova A CFEngine Special Topics Handbook CFEngine AS This document describes how software updates work in CFEngine Nova. ¨ © Copyright c 2010- CFEngine AS 1 v i Table of Contents What does upgrading mean? ::::::::::::::::::::::::::::::::::::::::: 3 Why do I need to upgrade?::::::::::::::::::::::::::::::::::::::::::: 3 How does upgrading work? ::::::::::::::::::::::::::::::::::::::::::: 3 How can I do phased deployment? :::::::::::::::::::::::::::::::::::: 4 What if I have multiple operating system platforms? ::::::::::::::::::: 4 How do Nova policies update if I already have my own policy? ::::::::: 4 Appendix A Manual package upgrade commands ::::::: 5 3 What does upgrading mean? A software upgrade involves obtaining a new version of the CFEngine software from soft- ware.CFEngine.com and installing it in place of the old. When software is updated, the previous version of the software is retained. From version 1.1 of CFEngine Nova, CFEngine is fully capable of managing its own updates ¨ and service restarts with a minimum of manual work on the policy server. Existing users of version 1.0 will need to upgrade the software manually on the affected sys- tems, or use the existing CFEngine to assist in the manual process. Please contact CFEngine Professional Services for for assistance (see Appendix). © Why do I need to upgrade? Bug fixes and new features are included in new software releases. To gain access to these fixes, you need to upgrade the software. Changes to the standard Community Open Promise Body Library might make use of new features, so upgrading brings you access to these new methods. How does upgrading work? CFEngine packages its software in operating sytsem compatible package formats (RPM, PKG, MSI, etc).
    [Show full text]
  • 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
    [Show full text]
  • Trusted Docker Containers and Trusted Vms in Openstack
    Trusted Docker Containers and Trusted VMs in OpenStack Raghu Yeluri Abhishek Gupta Outline o Context: Docker Security – Top Customer Asks o Intel’s Focus: Trusted Docker Containers o Who Verifies Trust ? o Reference Architecture with OpenStack o Demo o Availability o Call to Action Docker Overview in a Slide.. Docker Hub Lightweight, open source engine for creating, deploying containers Provides work flow for running, building and containerizing apps. Separates apps from where they run.; Enables Micro-services; scale by composition. Underlying building blocks: Linux kernel's namespaces (isolation) + cgroups (resource control) + .. Components of Docker Docker Engine – Runtime for running, building Docker containers. Docker Repositories(Hub) - SaaS service for sharing/managing images Docker Images (layers) Images hold Apps. Shareable snapshot of software. Container is a running instance of image. Orchestration: OpenStack, Docker Swarm, Kubernetes, Mesos, Fleet, Project Docker Layers Atomic, Lattice… Docker Security – 5 key Customer Asks 1. How do you know that the Docker Host Integrity is there? o Do you trust the Docker daemon? o Do you trust the Docker host has booted with Integrity? 2. How do you verify Docker Container Integrity o Who wrote the Docker image? Do you trust the image? Did the right Image get launched? 3. Runtime Protection of Docker Engine & Enhanced Isolation o How can Intel help with runtime Integrity? 4. Enterprise Security Features – Compliance, Manageability, Identity authentication.. Etc. 5. OpenStack as a single Control Plane for Trusted VMs and Trusted Docker Containers.. Intel’s Focus: Enable Hardware-based Integrity Assurance for Docker Containers – Trusted Docker Containers Trusted Docker Containers – 3 focus areas o Launch Integrity of Docker Host o Runtime Integrity of Docker Host o Integrity of Docker Images Today’s Focus: Integrity of Docker Host, and how to use it in OpenStack.
    [Show full text]
  • Providing User Security Guarantees in Public Infrastructure Clouds
    1 Providing User Security Guarantees in Public Infrastructure Clouds Nicolae Paladi, Christian Gehrmann, and Antonis Michalas Abstract—The infrastructure cloud (IaaS) service model offers improved resource flexibility and availability, where tenants – insulated from the minutiae of hardware maintenance – rent computing resources to deploy and operate complex systems. Large-scale services running on IaaS platforms demonstrate the viability of this model; nevertheless, many organizations operating on sensitive data avoid migrating operations to IaaS platforms due to security concerns. In this paper, we describe a framework for data and operation security in IaaS, consisting of protocols for a trusted launch of virtual machines and domain-based storage protection. We continue with an extensive theoretical analysis with proofs about protocol resistance against attacks in the defined threat model. The protocols allow trust to be established by remotely attesting host platform configuration prior to launching guest virtual machines and ensure confidentiality of data in remote storage, with encryption keys maintained outside of the IaaS domain. Presented experimental results demonstrate the validity and efficiency of the proposed protocols. The framework prototype was implemented on a test bed operating a public electronic health record system, showing that the proposed protocols can be integrated into existing cloud environments. Index Terms—Security; Cloud Computing; Storage Protection; Trusted Computing F 1 INTRODUCTION host level. While support data encryption at rest is offered by several cloud providers and can be configured by tenants Cloud computing has progressed from a bold vision to mas- in their VM instances, functionality and migration capabil- sive deployments in various application domains. However, ities of such solutions are severely restricted.
    [Show full text]
  • Ein Wilder Ritt Distributionen
    09/2016 Besichtigungstour zu den skurrilsten Linux-Distributionen Titelthema Ein wilder Ritt Distributionen 28 Seit den frühen 90ern schießen die Linux-Distributionen wie Pilze aus dem Boden. Das Linux-Magazin blickt zurück auf ein paar besonders erstaunliche oder schräge Exemplare. Kristian Kißling www.linux-magazin.de © Antonio Oquias, 123RF Oquias, © Antonio Auch wenn die Syntax anderes vermu- samer Linux-Distributionen aufzustellen, Basis für Evil Entity denkt (Grün!), liegt ten lässt, steht der Name des klassischen denn in den zweieinhalb Jahrzehnten falsch. Tatsächlich basierte Evil Entity auf Linux-Tools »awk« nicht für Awkward kreuzte eine Menge von ihnen unseren Slackware und setzte auf einen eher düs- (zu Deutsch etwa „tolpatschig“), sondern Weg. Während einige davon noch putz- ter anmutenden Enlightenment-Desktop für die Namen seiner Autoren, nämlich munter in die Zukunft blicken, ist bei an- (Abbildung 3). Alfred Aho, Peter Weinberger und Brian deren nicht recht klar, welche Zielgruppe Als näher am Leben erwies sich der Fo- Kernighan. Kryptische Namen zu geben sie anpeilen oder ob sie überhaupt noch kus der Distribution, der auf dem Ab- sei eine lange etablierte Unix-Tradition, am Leben sind. spielen von Multimedia-Dateien lag – sie heißt es auf einer Seite des Debian-Wiki wollten doch nur Filme schauen. [1], die sich mit den Namen traditioneller Linux für Zombies Linux-Tools beschäftigt. Je kaputter, desto besser Denn, steht dort weiter, häufig halten Apropos untot: Die passende Linux- Entwickler die Namen ihrer Tools für Distribution für Zombies ließ sich recht Auch Void Linux [4], der Name steht selbsterklärend oder sie glauben, dass einfach ermitteln. Sie heißt Undead Linux je nach Übersetzung für „gleichgültig“ sie die User ohnehin nicht interessieren.
    [Show full text]
  • NOVA: a Log-Structured File System for Hybrid Volatile/Non
    NOVA: A Log-structured File System for Hybrid Volatile/Non-volatile Main Memories Jian Xu and Steven Swanson, University of California, San Diego https://www.usenix.org/conference/fast16/technical-sessions/presentation/xu This paper is included in the Proceedings of the 14th USENIX Conference on File and Storage Technologies (FAST ’16). February 22–25, 2016 • Santa Clara, CA, USA ISBN 978-1-931971-28-7 Open access to the Proceedings of the 14th USENIX Conference on File and Storage Technologies is sponsored by USENIX NOVA: A Log-structured File System for Hybrid Volatile/Non-volatile Main Memories Jian Xu Steven Swanson University of California, San Diego Abstract Hybrid DRAM/NVMM storage systems present a host of opportunities and challenges for system designers. These sys- Fast non-volatile memories (NVMs) will soon appear on tems need to minimize software overhead if they are to fully the processor memory bus alongside DRAM. The result- exploit NVMM’s high performance and efficiently support ing hybrid memory systems will provide software with sub- more flexible access patterns, and at the same time they must microsecond, high-bandwidth access to persistent data, but provide the strong consistency guarantees that applications managing, accessing, and maintaining consistency for data require and respect the limitations of emerging memories stored in NVM raises a host of challenges. Existing file sys- (e.g., limited program cycles). tems built for spinning or solid-state disks introduce software Conventional file systems are not suitable for hybrid mem- overheads that would obscure the performance that NVMs ory systems because they are built for the performance char- should provide, but proposed file systems for NVMs either in- acteristics of disks (spinning or solid state) and rely on disks’ cur similar overheads or fail to provide the strong consistency consistency guarantees (e.g., that sector updates are atomic) guarantees that applications require.
    [Show full text]
  • Red Hat Enterprise Linux Openstack Platform on Inktank Ceph Enterprise
    Red Hat Enterprise Linux OpenStack Platform on Inktank Ceph Enterprise Cinder Volume Performance Performance Engineering Version 1.0 December 2014 100 East Davie Street Raleigh NC 27601 USA Phone: +1 919 754 4950 Fax: +1 919 800 3804 Linux is a registered trademark of Linus Torvalds. Red Hat, Red Hat Enterprise Linux and the Red Hat "Shadowman" logo are registered trademarks of Red Hat, Inc. in the United States and other countries. Dell, the Dell logo and PowerEdge are trademarks of Dell, Inc. Intel, the Intel logo and Xeon are registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. All other trademarks referenced herein are the property of their respective owners. © 2014 by Red Hat, Inc. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, V1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/). The information contained herein is subject to change without notice. Red Hat, Inc. shall not be liable for technical or editorial errors or omissions contained herein. Distribution of modified versions of this document is prohibited without the explicit permission of Red Hat Inc. Distribution of this work or derivative of this work in any standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from Red Hat Inc. The GPG fingerprint of the [email protected] key is: CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E www.redhat.com 2 Performance Engineering Table of Contents 1 Executive Summary ........................................................................................
    [Show full text]
  • Firecracker: Lightweight Virtualization for Serverless Applications
    Firecracker: Lightweight Virtualization for Serverless Applications Alexandru Agache, Marc Brooker, Andreea Florescu, Alexandra Iordache, Anthony Liguori, Rolf Neugebauer, Phil Piwonka, and Diana-Maria Popa, Amazon Web Services https://www.usenix.org/conference/nsdi20/presentation/agache This paper is included in the Proceedings of the 17th USENIX Symposium on Networked Systems Design and Implementation (NSDI ’20) February 25–27, 2020 • Santa Clara, CA, USA 978-1-939133-13-7 Open access to the Proceedings of the 17th USENIX Symposium on Networked Systems Design and Implementation (NSDI ’20) is sponsored by Firecracker: Lightweight Virtualization for Serverless Applications Alexandru Agache Marc Brooker Andreea Florescu Amazon Web Services Amazon Web Services Amazon Web Services Alexandra Iordache Anthony Liguori Rolf Neugebauer Amazon Web Services Amazon Web Services Amazon Web Services Phil Piwonka Diana-Maria Popa Amazon Web Services Amazon Web Services Abstract vantage over traditional server provisioning processes: mul- titenancy allows servers to be shared across a large num- Serverless containers and functions are widely used for de- ber of workloads, and the ability to provision new func- ploying and managing software in the cloud. Their popularity tions and containers in milliseconds allows capacity to be is due to reduced cost of operations, improved utilization of switched between workloads quickly as demand changes. hardware, and faster scaling than traditional deployment meth- Serverless is also attracting the attention of the research com- ods. The economics and scale of serverless applications de- munity [21,26,27,44,47], including work on scaling out video mand that workloads from multiple customers run on the same encoding [13], linear algebra [20, 53] and parallel compila- hardware with minimal overhead, while preserving strong se- tion [12].
    [Show full text]
  • Introduction to Fmxlinux Delphi's Firemonkey For
    Introduction to FmxLinux Delphi’s FireMonkey for Linux Solution Jim McKeeth Embarcadero Technologies [email protected] Chief Developer Advocate & Engineer For quality purposes, all lines except the presenter are muted IT’S OK TO ASK QUESTIONS! Use the Q&A Panel on the Right This webinar is being recorded for future playback. Recordings will be available on Embarcadero’s YouTube channel Your Presenter: Jim McKeeth Embarcadero Technologies [email protected] | @JimMcKeeth Chief Developer Advocate & Engineer Agenda • Overview • Installation • Supported platforms • PAServer • SDK & Packages • Usage • UI Elements • Samples • Database Access FireDAC • Migrating from Windows VCL • midaconverter.com • 3rd Party Support • Broadway Web Why FMX on Linux? • Education - Save money on Windows licenses • Kiosk or Point of Sale - Single purpose computers with locked down user interfaces • Security - Linux offers more security options • IoT & Industrial Automation - Add user interfaces for integrated systems • Federal Government - Many govt systems require Linux support • Choice - Now you can, so might as well! Delphi for Linux History • 1999 Kylix: aka Delphi for Linux, introduced • It was a port of the IDE to Linux • Linux x86 32-bit compiler • Used the Trolltech QT widget library • 2002 Kylix 3 was the last update to Kylix • 2017 Delphi 10.2 “Tokyo” introduced Delphi for x86 64-bit Linux • IDE runs on Windows, cross compiles to Linux via the PAServer • Designed for server side development - no desktop widget GUI library • 2017 Eugene
    [Show full text]
  • SPARTAN ILY Fee Hikes May Stop KEEPING FIT and EDUCATED
    VOLUME 108, NO. 88 TUESDAY MAY 6. 1 9 9 7 INSIDE * INSIDE a IS ell Spirit of friendship goes 4,#..sk The Offspring gives its.. w leehi beyond competition dose of alternative rock(---' Page 5 1" -V-- Page 8 Ma Ser San Jose State University Since 1 93 .1 SPARTAN ILY Fee hikes may stop KEEPING FIT AND EDUCATED By Dennis Knight said Ducheny, the chair of the Spartan Daily Stuff Write, Assembly Budget Committee, in a press release. "Not only would AB 01 pay Students who are tired 1318 hold the line on fee hikes for at California ing exorbitant fees die rest of the decade, but it would soon find relief if universities may give working families the opportu- Act of the College Affordability nity to plan and save for their chil- the 1997 makes its way through dren's education." State Assembly. Besides freezing fees until the Written by Assemblywoman turn of the century, AB 1318 (D - Denise Moreno Ducheny would limit student fee increases Vista), the bill, known as Chula after the year 2000 to no more AB 1318. would freeze student fees than the rise in personal income University, in the t ..difornia State from the prior year. The bill would California and University of also express the intent of the legis- College California Community lature to financially support public the year 2000. systems until colleges based on growth in enroll- continues in the spirit "This act ment and personal income, accord- 1960 in mak- of the Master Plan of ing to Ducheny. as essible ing our public colleges Currently, the cost for students by laying out a rational and pre- dictable policy for student lees," See Fees, page 5 It's standing room only in the Washington Square Hall let, ture room as author Anne Lamott speaks to SJSU students Friday afternoon.
    [Show full text]
  • Ubuntu: Unleashed 2017 Edition
    Matthew Helmke with Andrew Hudson and Paul Hudson Ubuntu UNLEASHED 2017 Edition 800 East 96th Street, Indianapolis, Indiana 46240 USA Ubuntu Unleashed 2017 Edition Editor-in-Chief Copyright © 2017 by Pearson Education, Inc. Mark Taub All rights reserved. Printed in the United States of America. This publication is protected Acquisitions Editor by copyright, and permission must be obtained from the publisher prior to any prohib- Debra Williams ited reproduction, storage in a retrieval system, or transmission in any form or by any means, electronic, mechanical, photocopying, recording, or likewise. For information Cauley regarding permissions, request forms and the appropriate contacts within the Pearson Managing Editor Education Global Rights & Permissions Department, please visit www.pearsoned.com/ permissions/. Sandra Schroeder Many of the designations used by manufacturers and sellers to distinguish their Project Editor products are claimed as trademarks. Where those designations appear in this book, and Lori Lyons the publisher was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals. Production Manager The author and publisher have taken care in the preparation of this book, but make Dhayanidhi no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in Proofreader connection with or arising out of the use of the information or programs contained Sasirekha herein. Technical Editor For information about buying this title in bulk quantities, or for special sales opportunities (which may include electronic versions; custom cover designs; and content José Antonio Rey particular to your business, training goals, marketing focus, or branding interests), Editorial Assistant please contact our corporate sales department at [email protected] or (800) 382-3419.
    [Show full text]
  • Instalacion Juju
    Universidad Nacional de Quilmes Laboratorio de Sistemas Operativos y Redes Trabajo Práctico JUJU - UBUNTU Elaborado: Gabriel Angel Garcia Descripción del proyecto: Juju (antes Ensemble ) es una herramienta de gestión de implementacion de servicios desarrollada por Canonical Ltd. Es un proyecto de software libre presentado en Launchpad y liberado bajo la licencia pública general de Affero (AGPL). Juju se concentra en la noción del servicio, abstrayendo la noción de la máquina o el servidor, y define las relaciones entre aquellos servicios que son actualizados automáticamente cuando dos servicios relacionados observan una modificación notable. Esto permite subir o bajar escaladamente los servicios a través de la llamada de un simple comando. Por ejemplo, un servicio web denominado Charm , que tiene una relación establecida con un equilibrador de carga, puede subirse horizontalmente con una simple orden de "añadir unidad" sin tener que preocuparse de volver a configurar el equilibrador de carga para declarar las nuevas instancias: las relaciones basadas en eventos del Charm se encargan de eso. Los Charms de Juju pueden ser escritos en cualquier lenguaje ejecutable. Relevamiento de características de la maquina utilizada: Procesador: Pentium Dual Core E5300 Ram: 2 GB Disco Rigido: 200 GB Relevamiento de sistema operativo y software utilizado y/o necesario: Ubuntu 16.04 JUJU Charms: son conjuntos de scripts para desplegar y administrar servicios. Con el manejo de eventos integrado, pueden declarar interfaces que encajan con otros servicios, por lo que pueden formarse relaciones. LXD: es un hypervisor (plataforma que permite aplicar diversas técnicas de control de virtualización) para contenedores Linux desarrollado por Canonical Ltd. Es un complemento para los contenedores de Linux (LXC) que facilita su uso y añade nuevas posibilidades.
    [Show full text]