DOCSLIB.ORG

Ubuntu Server Guide Basic Installation Preparing to Install

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Ubuntu Server Guide Basic Installation Preparing to Install Ubuntu Server Guide Changes, errors and bugs This is the current edition for Ubuntu 20.04 LTS, Focal Fossa. Ubuntu serverguides for previous LTS versions: 18.04 (PDF), 16.04 (PDF). If you find any errors or have suggestions for improvements to pages, please use the link at thebottomof each topic titled: “Help improve this document in the forum.” This link will take you to the Server Discourse forum for the specific page you are viewing. There you can share your comments or let us know aboutbugs with each page. Offline Download this guide as a PDF Support There are a couple of different ways that Ubuntu Server Edition is supported: commercial support and community support. The main commercial support (and development funding) is available from Canonical, Ltd. They supply reasonably- priced support contracts on a per desktop or per server basis. For more information see the Ubuntu Advantage page. Community support is also provided by dedicated individuals and companies that wish to make Ubuntu the best distribution possible. Support is provided through multiple mailing lists, IRC channels, forums, blogs, wikis, etc. The large amount of information available can be overwhelming, but a good search engine query can usually provide an answer to your questions. See the Ubuntu Support page for more information. Basic installation This chapter provides an overview of installing Ubuntu 20.04 Server Edition. There is more detailed docu- mentation on other installer topics. Preparing to Install This section explains various aspects to consider before starting the installation. System requirements Ubuntu 20.04 Server Edition provides a common, minimalist base for a variety of server applications, such as file/print services, web hosting, email hosting, etc. This version supports four 64-bit architectures: • amd64 (Intel/AMD 64-bit) • arm64 (64-bit ARM) • ppc64el (POWER8 and POWER9) • s390x (IBM Z and LinuxONE) The recommended system requirements are: • CPU: 1 gigahertz or better 1 • RAM: 1 gigabyte or more • Disk: a minimum of 2.5 gigabytes Server and Desktop Differences The Ubuntu Server Edition and the Ubuntu Desktop Edition use the same apt repositories, making it just as easy to install a server application on the Desktop Edition as on the Server Edition. One major difference is that the graphical environment used for the Desktop Edition is not installed for the Server. This includes the graphics server itself, the graphical utilities and applications, and the various user-supporting services needed by desktop users. Backing Up Before installing Ubuntu Server Edition you should make sure all data on the system is backed up. If this is not the first time an operating system has been installed on your computer, it is likely you willneed to re-partition your disk to make room for Ubuntu. Any time you partition your disk, you should be prepared to lose everything on the disk should you make a mistake or something goes wrong during partitioning. The programs used in installation are quite reliable, most have seen years of use, but they also perform destructive actions. Preparing install media There are platform specific step-by-step examples for s390x LPAR, z/VM and ppc64el installations. For amd64, download the install image from https://releases.ubuntu.com/20.04/. There are many ways to boot the installer but the simplest and commonest way is to create a bootable USB stick to boot the system to be installed with (tutorials for other operating systems are also available). Booting the installer Plug the USB stick into the system to be installed and start it. Most computers will automatically boot from USB or DVD, though in some cases this is disabled to improve boot times. If you don’t see the boot message and the “Welcome” screen which should appear after it, you will need to set your computer to boot from the install media. There should be an on-screen message when the computer starts telling you what key to press for settings or a boot menu. Depending on the manufacturer, this could be Escape, F2,F10 or F12. Simply restart your computer and hold down this key until the boot menu appears, then select the drive with the Ubuntu install media. If you are still having problems, check out the Ubuntu Community documentation on booting from CD/DVD. After a few moments, the installer will start in its language selection screen. welcome_c|690x517 2 Using the installer The installer is designed to be easy to use and have sensible defaults so for a first install you can mostly just accept the defaults for the most straightforward install: • Choose your language • Update the installer (if offered) • Select your keyboard layout • Do not configure networking (the installer attempts to configure wired network interfaces viaDHCP, but you can continue without networking if this fails) • Do not configure a proxy or custom mirror unless you have to in your network • For storage, leave “use an entire disk” checked, and choose a disk to install to, then select “Done” on the configuration screen and confirm the install • Enter a username, hostname and password • Just select Done on the SSH and snap screens • You will now see log messages as the install is completed • Select restart when this is complete, and log in using the username and password provided There is more detailed documentation on all these options. iSCSI The iSCSI protocol can be used to install Ubuntu on systems with or without hard disks attached, and iBFT can be used to automate iSCSI setup on installation and boot. Installation on a diskless system The first steps of a diskless iSCSI installation are identical tothe Installation using debian-installer section up to “Hard drive layout”. The installer will display a warning with the following message: No disk drive was detected. If you know the name of the driver needed by your disk drive, you can select it from the list. Select the item in the list titled login to iSCSI targets. You will be prompted to enter an IP address to scan for iSCSI targets with a description of the format for the address. Enter the IP address for the location of your iSCSI target and navigate to <continue> then hit ENTER If authentication is required in order to access the iSCSI device, provide the username in the next field. Otherwise, leave it blank. If your system is able to connect to the iSCSI provider, you should see a list of available iSCSI targets where the operating system can be installed. The list should be similar to the following : Select the iSCSI targets you wish to use. iSCSI targets on 192.168.1.29:3260: [ ] iqn .2016 −03. TrustyS−iscsitarget :storage.sys0 <Go Back> <Continue> 3 Select the iSCSI target that you want to use with the space bar. Use the arrow keys to navigate to the target that you want to select. Navigate to <Continue> and hit ENTER. If the connection to the iSCSI target is successful, you will be prompted with the [!!] Partition disks installation menu. The rest of the procedure is identical to any normal installation on attached disks. Once the installation is completed, you will be asked to reboot. Installation on a system with disk attached Again, the iSCSI installation on a normal server with one or many disks attached is identical to the Instal- lation using debian-installer section until we reach the disk partitioning menu. Instead of using any of the Guided selection, we need to perform the following steps : Navigate to the Manual menu entry Select the Configure iSCSI Volumes menu entry Choose the Log into iSCSI targets You will be prompted to Enter an IP address to scan for iSCSI targets. with a description of the format for the address. Enter the IP address and navigate to <continue> then hit ENTER If authentication is required in order to access the iSCSI device, provide the username in the next field or leave it blank. If your system is able to connect to the iSCSI provider, you should see a list of available iSCSI targets where the operating system can be installed. The list should be similar to the following : Select the iSCSI targets you wish to use. iSCSI targets on 192.168.1.29:3260: [ ] iqn .2016 −03. TrustyS−iscsitarget :storage.sys0 <Go Back> <Continue> Select the iSCSI target that you want to use with the space bar. Use the arrow keys to navigate to the target that you want to select Navigate to <Continue> and hit ENTER. If successful, you will come back to the menu asking you to Log into iSCSI targets. Navigate to Finish and hit ENTER The newly connected iSCSI disk will appear in the overview section as a device prefixed with SCSI. This is the disk that you should select as your installation disk. Once identified, you can choose any of the partitioning methods. Warning Depending on your system configuration, there may be other SCSI disks attached to the system. Be very careful to identify the proper device before proceeding with the installation. Otherwise, irreversible data loss may result from performing an installation on the wrong disk. Installation with iBFT In order to setup iSCSI based on the iBFT (iSCSI Boot Firmware Table) on the installation and boot, append these options at the installer prompt (or to the preseed file): 4 disk−detect/ibft/enable=true partman−iscsi/iscsi_auto=true This should probe for iBFT information and configure network interface(s) and iSCSI target(s) accordingly during the installation, and configure system boot (initramfs) to do that too in order to find the root device. Warning The support for iBFT is available in the debian-installer on netboot images as of 2019-06-20 and (expected) on ISO images for the 18.04.3 point release and later.
Load more

Recommended publications
  • What Is the Difference Between San and Nas and How Can I Use Them in My Qlikview Environment?
    WHAT IS THE DIFFERENCE BETWEEN SAN AND NAS AND HOW CAN I USE THEM IN MY QLIKVIEW ENVIRONMENT? QlikView Technical Brief February 2012 qlikview.com This document will highlight some of the conceptual differences between the terms SAN and NAS and describe how they fit into a QlikView Server environment by suggesting some recommended implementations. It will also describe the definition of DAS (Direct-Attached Storage) and how it applies in SAN configurations. Using SAN and NAS in the QlikView Environment | Page 2 Table of Contents Definitions 4 SAN - Storage Area Network 4 Host adapters 4 Typical architecture 5 NAS - Network Attached Storage 7 Typical architecture 7 DAS - Direct-Attached Storage 8 Using SAN/NAS and QlikView Server 8 QlikView Server and Distribution Service cluster inter-communication 8 QlikView Server file storage conformity 9 QlikView file types explained 9 A note on the usage of .shared files 10 Considerations 10 Conclusions 11 Some suggestions 12 QlikView Server Configurations 12 QlikView Server cluster utilizing a virtual Windows based NAS using a SAN 12 QlikView Server cluster utilizing a physical NAS using a SAN 13 Single QlikView Server using a SAN as local storage 14 QlikView Server using a pure Windows based NAS as local storage 14 Using SAN and NAS in the QlikView Environment | Page 3 Definitions It is important to differentiate between the two terms SAN and NAS. Also, the term DAS will be involved to nuance the usage of a SAN. SAN - STORAGE AREA NETWORK A typical definition of a SAN could be; “SANs primarily are used to make storage devices (such as disk arrays, tape libraries, and optical jukeboxes) accessible to servers so that the devices appear as locally attached to the operating system.” (Wikipedia.org) SANs are often used in larger virtualization scenarios or where larger areas of high-speed access storage space is required.
    [Show full text]
  • Design and Implementation Considerations for Storage Area Networks
    Designing and Implementing a SAN 1 Running head: DESIGNING AND IMPLEMENTING A SAN Considerations for the Design and Implementation of a Storage Area Network (SAN) Al Spraker 15 July 2006 Designing and Implementing a SAN 2 Abstract With the ever-increasing need for businesses and organizations to maintain and manage large amounts of data, storage issues have become a concern and an investment priority. Organizations and business must have a good understanding of the features and characteristics of network storage in order to design and implement a network storage system that addresses their present and future needs. This paper will define and compare the storage area networks (SAN) with network-attached storage (NAS) as well as a historical perspective of directly-attached storage (DAS). Some of the benefits associated with establishing a network storage system will also be identified. This paper will identify some of the general characteristics of SAN architecture and protocols, such as Fibre Channel and iSCSI. Another area addressed will be management software issues and its critical role as part of successful SAN deployment. Not only must data be reliable and available at all times, data must also be kept confidential and protected. While the data is being transmitted over the network, security is also a concern that must be addressed. Designing and Implementing a SAN 3 Considerations for the Design and Implementation of a Storage Area Network (SAN) Today’s enterprises are using more complex, sophisticated, and resource-intensive software that generates massive amounts of data. The demand for businesses to maintain and manage large amounts of data has elevated storage issues to a level of significant priority.
    [Show full text]
  • Linux Journal | System Administration Special Issue | 2009
    Cfengine VNC Billix Zenoss Thin Clients MySQL Heartbeat ™ SPECIAL SYSTEM ADMINISTRATION ISSUE Since 1994: The Original Magazine of the Linux Community 2009 | Supplement Issue | www.linuxjournal.com MAY THE SOURCE BE WITH YOU Billix: the Sysadmin Toolkit for Your Pocket Authentication with Fedora Directory Server Remote Desktop Administration with OpenSSH or VNC Manage Configuration Files with Cfengine Setting Up a PXE Boot Server Network Monitoring with Zenoss SPECIAL SYSTEM CONTENTS ADMINISTRATION ISSUE 5 SPECIAL_ISSUE.TAR.GZ 26 PXE MAGIC: FLEXIBLE System Administration: Instant NETWORK BOOTING WITH Gratification Edition MENUS Shawn Powers What if you never had to carry around an install or rescue CD 6 CFENGINE FOR again? Set up a PXE boot server ENTERPRISE with menus and put them all on CONFIGURATION the network. MANAGEMENT Kyle Rankin How to use cfengine to manage configuration files across large 30 CREATING VPNS WITH 17 ZENOSS numbers of machines. IPSEC AND SSL/TLS Scott Lackey The two most common and current techniques for creating VPNs. 10 SECURED REMOTE Rami Rosen Linux Journal DESKTOP/APPLICATION SESSIONS 34 MYSQL 5 STORED 2009 Lineup Different ways to control a Linux PROCEDURES: RELIC OR system over a network. REVOLUTION? JANUARY Mick Bauer Do MySQL 5 Stored Procedures Security produce tiers of joy or sorrow? FEBRUARY Guy Harrison Web Development 38 GETTING STARTED WITH MARCH Desktop HEARTBEAT Availability in a heartbeat. APRIL Daniel Bartholomew System Administration 14 BILLIX: A SYSADMIN’S MAY SWISS ARMY KNIFE 42 FEDORA DIRECTORY Cool Projects SERVER: THE EVOLUTION Build a toolbox in your pocket by JUNE installing Billix on that spare USB key.
    [Show full text]
  • Guide to Open Source Solutions
    White paper ___________________________ Guide to open source solutions “Guide to open source by Smile ” Page 2 PREAMBLE SMILE Smile is a company of engineers specialising in the implementing of open source solutions OM and the integrating of systems relying on open source. Smile is member of APRIL, the C . association for the promotion and defence of free software, Alliance Libre, PLOSS, and PLOSS RA, which are regional cluster associations of free software companies. OSS Smile has 600 throughout the World which makes it the largest company in Europe - specialising in open source. Since approximately 2000, Smile has been actively supervising developments in technology which enables it to discover the most promising open source products, to qualify and assess them so as to offer its clients the most accomplished, robust and sustainable products. SMILE . This approach has led to a range of white papers covering various fields of application: Content management (2004), portals (2005), business intelligence (2006), PHP frameworks (2007), virtualisation (2007), and electronic document management (2008), as well as PGIs/ERPs (2008). Among the works published in 2009, we would also cite “open source VPN’s”, “Firewall open source flow control”, and “Middleware”, within the framework of the WWW “System and Infrastructure” collection. Each of these works presents a selection of best open source solutions for the domain in question, their respective qualities as well as operational feedback. As open source solutions continue to acquire new domains, Smile will be there to help its clients benefit from these in a risk-free way. Smile is present in the European IT landscape as the integration architect of choice to support the largest companies in the adoption of the best open source solutions.
    [Show full text]
  • Introduction to RAW-Sockets Jens Heuschkel, Tobias Hofmann, Thorsten Hollstein, Joel Kuepper
    Introduction to RAW-sockets Jens Heuschkel, Tobias Hofmann, Thorsten Hollstein, Joel Kuepper 16.05.2017 Technical Report No. TUD-CS-2017-0111 Technische Universität Darmstadt Telecooperation Report No. TR-19, The Technical Reports Series of the TK Research Division, TU Darmstadt ISSN 1864-0516 http://www.tk.informatik.tu-darmstadt.de/de/publications/ Introduction to RAW-sockets by Heuschkel, Jens Hofmann, Tobias Hollstein, Thorsten Kuepper, Joel May 17, 2017 Abstract This document is intended to give an introduction into the programming with RAW-sockets and the related PACKET-sockets. RAW-sockets are an additional type of Internet socket available in addition to the well known DATAGRAM- and STREAM-sockets. They do allow the user to see and manipulate the information used for transmitting the data instead of hiding these details, like it is the case with the usually used STREAM- or DATAGRAM sockets. To give the reader an introduction into the subject we will first give an overview about the different APIs provided by Windows, Linux and Unix (FreeBSD, Mac OS X) and additional libraries that can be used OS-independent. In the next section we show general problems that have to be addressed by the programmer when working with RAW-sockets. We will then provide an introduction into the steps necessary to use the APIs or libraries, which functionality the different concepts provide to the programmer and what they provide to simplify using RAW and PACKET-sockets. This section includes examples of how to use the different functions provided by the APIs. Finally in the additional material we will give some complete examples that show the concepts and can be used as a basis to write own programs.
    [Show full text]
  • Analysis and Testing of Voip- Subsystems of Ipbrick
    ANALYSIS AND TESTING OF VOIP- SUBSYSTEMS OF IPBRICK SWAMY H K Julho de 2017 1 ANALYSIS AND TESTING OF VOIP-SUBSYSTEMS OF IPBRICK PORTUGAL, S.A. SWAMY HK Department of Electrical Engineering Master‟s in Electrical Engineering – Power Systems 2017 2 3 Report prepared for the partial satisfaction of the requirements of DSEE Unit Course – Dissertation of the Master‟s in Electrical Engineering – Power Systems Swamy HK, Nº 1150084, [email protected] Professor.Sergio Ramos , [email protected] Company: IP BRICK, Oporto, Portugal Supervisor: Mr. Miguel Ramalhão, [email protected] Department of Electrical Engineering Master‟s in Electrical Engineering – Power Systems 2017 4 5 Where there is righteousness in the heart, There is beauty in the character. When there is beauty in the character, There is harmony in the home. When there is harmony in the home, There is order in the nation. When there is order in the nation, There is peace in the world.” - APJ Abdul Kalam 6 7 ACKNOWLEDGMENT At the end, the last stage of many successful stages over the course of my academic career comes to an end and its pride and pleasure that I completed it. During the development of this thesis work, the support and encouragement of several people were fundamental. So I would like to thank all those who have left their footprints in my way. This journey would not have been possible without the support of my professors, supervisors and mentors, family and friends. To my family thank you for encouraging me in all my pursuits and inspiring me to follow my dreams.
    [Show full text]
  • A Survey of Open Source Products for Building a SIP Communication Platform
    Hindawi Publishing Corporation Advances in Multimedia Volume 2011, Article ID 372591, 21 pages doi:10.1155/2011/372591 Research Article A Survey of Open Source Products for Building a SIP Communication Platform Pavel Segec and Tatiana Kovacikova Department of InfoCom Networks, University of Zilina, Univerzitna 8215/1, 010 26 Zilina, Slovakia Correspondence should be addressed to Tatiana Kovacikova, [email protected] Received 29 July 2011; Revised 31 October 2011; Accepted 15 November 2011 Academic Editor: T. Turletti Copyright © 2011 P. Segec and T. Kovacikova. This is an open access article distributed under the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. The Session Initiation Protocol (SIP) is a multimedia signalling protocol that has evolved into a widely adopted communication standard. The integration of SIP into existing IP networks has fostered IP networks becoming a convergence platform for both real- time and non-real-time multimedia communications. This converged platform integrates data, voice, video, presence, messaging, and conference services into a single network that offers new communication experiences for users. The open source community has contributed to SIP adoption through the development of open source software for both SIP clients and servers. In this paper, we provide a survey on open SIP systems that can be built using publically available software. We identify SIP features for service deve- lopment and programming, services and applications of a SIP-converged platform, and the most important technologies support- ing SIP functionalities. We propose an advanced converged IP communication platform that uses SIP for service delivery.
    [Show full text]
  • Kolokované Nasazení Asterisk PBX a Kamailio SIP Proxy Ve Funkci SBC
    VŠB – Technická univerzita Ostrava Fakulta elektrotechniky a informatiky Katedra telekomunikační techniky Kolokované nasazení Asterisk PBX a Kamailio SIP Proxy ve funkci SBC Combined Implementation of Asterisk PBX and SIP Proxy Kamailio in the Role of the SBC 2017 Bc. Róbert Šimovič Poďakovanie Rád by som poďakoval Ing. Janovi Rozhonovi, Ph.D., za odbornú pomoc a konzultáciu pri vytváraní tejto diplomovej práce. Abstrakt Práca sa zaoberá vytvorením SBC pomocou spoločného nasadenia pobočkovej ústredne Asterisk a SIP proxy Kamailio. Pri návrhu SBC bolo potrebné brať do úvahy spôsob implementácie oboch platforiem na spoločne zdieľanom virtuálnom serveri. Návrh je vystavaný na novších verziách platforiem a využíva tie výhody oboch platforiem, ktoré robia dané riešenie atraktívne. Kľúčové funkcie pre celý systém sú bezpečnosť a variabilita nastavenia SBC, ktoré je možné meniť podľa aktuálnych požiadaviek. V mojom realizovanom prostredí bolo potrebné navrhnúť súbor bezpečnostných funkcií, ktoré naplňovali funkciu SBC. Celý systém bol vystavený výkonnostnému testovaniu, ktorý som vyhodnocoval pomocou grafov. Zásadou metodiky testovania je možnosť reprodukovateľnosti. Kľúčové slová Kamailio, Asterisk, SBC, testovanie, SIPp, bezpečnosť, VoIP, HTABLE, PIKE, TOPOH, RATELIMIT, TLS Abstract This thesis deals with the creation of SBC by the combined implementation of Asterisk PBX and SIP Proxy Kamailio. When designing the SBC, it was necessary to take in consideration the implementation of both platforms on one share virtual server. The design is based on newer versions of mentioned platforms and uses the benefits of both platforms, which make the solution more attractive. The key functions of the whole system are security and variability of the SBC settings, which can be altered according to actual requirements.
    [Show full text]
  • Homer 5 & Captagent 6
    HOMER 5 & CAPTAGENT 6 Presented by: Alexandr Dubovikov Presentation Written by: Alexandr Dubovikov & Lorenzo Mangani HOMER Development Team http://sipcapture.org Introduction About the Authors - Behind the Project Alexandr Dubovikov Senior Voice Expert for QSC AG, one of the major German voice and data providers. Alexandr holds a diploma in physics of Odessa State University and brings 20 years of experience in telecommunication techniques, contributing to many Open Source projects like FreeSwitch, SER, Kamailio, SEMS, Asterisk, SIPp, Wireshark. Alexandr is founder and the main developer of Homer SIP Capture project. Also founder of IRC RusNet Network, one of the biggest national IRC networks in the world. Lorenzo Mangani Sr. Voice Engineer and Designer for the largest international cable operator worldwide, founder of Amsterdam based QXIP BV, Co-Founder and Developer of Homer SIP Capture project and voice specialist of the NTOP Team. Formerly a Sound Engineer, Lorenzo has been deeply involved with telecommunications and VoIP for well over a decade and has contributed ideas, design concepts and code to many voice-related Open-Source and commercial projects specializing in active and passive monitoring solutions. Introduction About this presentation HOMER has been a resident guest since the inception of Kamailio World and over time the event also became the clock of our major project releases and the stage where we love to introduce the fruit of our hard work to a familiar crowd. This year is of course no exception and we proudly bring you: - HOMER v5 New Features ○ New User-Interface! ○ New Core Functionality! ○ Easy to Extend and Integrate ○ … and so much More! - CAPTAGENT v6 ● New Features ○ New Internal Architecture! ○ Capture Scenarios configuration! ○ Multiple sockets, multiple input & outputs! ○ Additional Protocols & Statistics! ○ … and so much More! Proudly Presenting HOMER 5 HOMER 5 Introduction & History HOMER 5? Wait a second! ..
    [Show full text]
  • Low Cost SAN
    Low Cost SAN Date: 25/04/2009 Revision History Version No. Date Prepared by Significant Changes 1. 25/04/2009 Krishna Kumar (NEC HCL ST) 1 Objective The objective of this document is to provide making of Low Cost SAN using FOSS tools. We have tried to set up a SAN which has following features: • Low cost and easily affordable • Ensured Scalability • High Reliability • Easily Manageable • High Performance • Ensured Security • High availability 2 Definitions, Acronyms and Abbreviations This section provides a list of all definitions, acronyms and terms required to properly interpret this document as well as to understand SAN terms and terminology. Abbreviation Description AoE ATA over Ethernet, a open storage protocol ATA Advance Technology Attachment Targets End Point of communication ( normally refers to server side ) Initiators A host that requests access to storage device ( client end ) RHCS Red Hat Clustering Suite Heartbeat A signal periodically sent out by a hardware component in order to inform another component that it is working normally ISCSI Internet Small Computer System Interface SATA Serial ATA, a newer version of ATA interface GFS Global File System, a cluster aware filesystem for Linux SAN Storage Area Networking LVM Logical Volume Manager RAID Redundant Array of Inexpensive disks DRBD Distributed Replicated Block Device NBD Network Block Device ENBD Enhanced Network Block Device GNBD Global Network Block Device HA High Availability, a clustering solution for Linux which provides reliability, availability and serviceability FOSS Free Open Source Software DFS Distributed File System for Windows LVS Linux Virtual Server 3 References This section tells all the references and urls used to prepare this document.
    [Show full text]
  • Cheap Clustering with OCFS2
    Cheap Clustering with OCFS2 Mark Fasheh Oracle August 14, 2006 What is OCFS2 ● General purpose cluster file system – Shared disk model – Symmetric architecture – Almost POSIX compliant ● fcntl(2) locking ● Shared writable mmap ● Cluster stack – Small, suitable only for a file system Why use OCFS2? ● Versus NFS – Fewer points of failure – Data consistency – OCFS2 nodes have direct disk access ● Higher performance ● Widely distributed, supported – In Linux kernel – Novell SLES9, SLES10 – Oracle support for RAC customers OCFS2 Uses ● File Serving – FTP – NFS ● Web serving (Apache) ● Xen image migration ● Oracle Database Why do we need “cheap” clusters? ● Shared disk hardware can be expensive – Fibre Channel as a rough example ● Switches: $3,000 - $20,000 ● Cards: $500 - $2,000 ● Cables, GBIC – Hundreds of dollars ● Disk(s): The sky's the limit ● Networks are getting faster and faster – Gigabit PCI card: $6 ● Some want to prototype larger systems – Performance not nec essarily critical Hardware ● Cheap commodity hardware is easy to find: – Refurbished from name brands (Dell, HP, IBM, etc) – Large hardware stores (Fry's Electronics, etc) – Online – Ebay, Amazon, Newegg, etc ● Impressive Performance – Dual core CPUs running at 2GHz and up – Gigabit network – SATA, SATA II Hardware Examples - CPU ● 2.66GHz, Dual Core w/MB: $129 – Built in video, network Hardware Examples - RAM ● 1GB DDR2: $70 Hardware Examples - Disk ● 100GB SATA: $50 Hardware Examples - Network ● Gigabit network card: $6 – Can direct connect rather than buy a switch, buy two!
    [Show full text]
  • Storage Area Network (SAN) Security and Performance
    MASTER THESIS Evaluation of Storage Area Network (SAN) Security and Performance Master Thesis in Computer Network Engineering November 2013 Author: Siavash Hajirostam Supervisor: Tony Larsson Examiner: Tony Larsson __________________________________ School of Information Science, Computer and Electrical Engineering Halmstad University PO Box 823, SE-301 18 HALMSTAD Sweden Evaluation of Storage Area Network (SAN) Security and Performance Siavash Hajirostam © Copyright Siavash Hajirostam, 2013. All rights reserved. Master thesis report IDE 1325 School of Information Science, Computer and Electrical Engineering Halmstad University Preface I would like to express my appreciation to my supervisor, Professor Tony Larsson, for the many useful discussions, comments and suggestions on this thesis and also my thanks go to the staff of Halmstad University for giving me the opportunity to study in the computer network engineering program. Finally, my special thanks to my family for their encouragement and support during my stud ies. Siavash Hajirostam Halmstad, November 2013 i Abstract Due to growing the number of Information Technology (IT) users all around the world, consequently the amount of data that needs to be stored is increasing day by day. Single attached disks and old storage technologies cannot manage the storing these amounts of data. Storage Area Network (SAN) is a distributed storage technology to manage the data from several nodes in centralize place and secure. This thesis investigates how SAN works, the file system and protocols that are used in implementation of SAN. The thesis also investigate about other storages technologies such as Network Attached Storage (NAS) and Direct Attached Storage (DAS) to figure out the advantages and disadvantages of SAN , The main focus of the thesis project is on identifying the security vulnerabilities in SAN such as possible attacks in different SAN protocols.
    [Show full text]