DOCSLIB.ORG

Red Hat Enterprise Linux 8 Building, Running, and Managing Containers

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Red Hat Enterprise Linux 8 Building, running, and managing containers Building, running, and managing Linux containers on Red Hat Enterprise Linux 8 Last Updated: 2021-09-15 Red Hat Enterprise Linux 8 Building, running, and managing containers Building, running, and managing Linux containers on Red Hat Enterprise Linux 8 Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project. The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community. All other trademarks are the property of their respective owners. Abstract This guide describes how to work with Linux containers on RHEL 8 systems using command-line tools such as podman, buildah, skopeo and runc. Table of Contents Table of Contents .P .R . E. .F . A. .C . E. 5. .M . A. .K . I.N . .G . .O . P. .E . N. S. .O . U. .R . C. .E . .M . .O . R. .E . .I N. .C . L. .U . S. .I V. .E . 6. .P .R . O. V. .I D. .I N. .G . F. .E .E . D. .B . A. .C . K. O. .N . R. .E .D . .H . .A .T . .D . O. C. .U . M. E. .N . T. .A .T . I.O . .N . 7. .C . H. .A . P. .T .E . R. 1.. .S . T. .A . R. .T .I .N . G. W. I.T . H. C. .O . .N . T. .A . I.N . E. .R . S. 8. 1.1. RUNNING CONTAINERS WITHOUT DOCKER 8 1.2. CHOOSING A RHEL ARCHITECTURE FOR CONTAINERS 9 1.3. GETTING CONTAINER TOOLS 9 1.4. SETTING UP ROOTLESS CONTAINERS 10 1.5. UPGRADING TO ROOTLESS CONTAINERS 11 1.6. SPECIAL CONSIDERATIONS FOR ROOTLESS CONTAINERS 12 .C . H. .A . P. .T .E . R. 2. T. .Y . P. .E . S. .O . .F . C. .O . .N . T. .A . I.N . E. .R . .I M. A. .G . E. .S . 1.4 . 2.1. GENERAL CHARACTERISTICS OF RHEL CONTAINER IMAGES 14 2.2. CHARACTERISTICS OF UBI IMAGES 14 2.3. UNDERSTANDING THE UBI STANDARD IMAGES 15 2.4. UNDERSTANDING THE UBI INIT IMAGES 15 2.5. UNDERSTANDING THE UBI MINIMAL IMAGES 16 2.6. UNDERSTANDING THE UBI MICRO IMAGES 17 2.7. USING THE UBI INIT IMAGES 17 2.8. USING THE UBI MICRO IMAGES 18 .C . H. .A . P. .T .E . R. 3. W. O. R. .K . I.N . G. W. I. T. H. .C . O. .N . T. .A . I.N . E. .R . .I M. A. .G . E. .S . .2 . 0. 3.1. CONFIGURING CONTAINER REGISTRIES 20 3.2. SEARCHING FOR CONTAINER IMAGES 21 3.3. PULLING IMAGES FROM REGISTRIES 21 3.4. PULLING AN IMAGE USING PODMAN 22 3.5. LISTING IMAGES 23 3.6. INSPECTING LOCAL IMAGES 23 3.7. INSPECTING REMOTE IMAGES 24 3.8. TAGGING IMAGES 24 3.9. SAVING AND LOADING IMAGES 26 3.10. REDISTRIBUTING UBI IMAGES 26 3.11. DEFINING THE IMAGE SIGNATURE VERIFICATION POLICY 27 3.12. REMOVING IMAGES 30 .C . H. .A . P. .T .E . R. 4. .W . .O . R. .K . I.N . G. .W . .I T. .H . .C . O. .N . T. .A . I.N . .E .R . S. .3 . 2. 4.1. PODMAN RUN COMMAND 32 4.2. RUNNING COMMANDS IN A CONTAINER FROM THE HOST 32 4.3. RUNNING COMMANDS INSIDE THE CONTAINER 33 4.4. LISTING CONTAINERS 34 4.5. STARTING CONTAINERS 35 4.6. INSPECTING CONTAINERS FROM THE HOST 36 4.7. MOUNTING DIRECTORY ON LOCALHOST TO THE CONTAINER 37 4.8. MOUNTING A CONTAINER FILESYSTEM 37 4.9. RUNNING A SERVICE AS A DAEMON WITH A STATIC IP 38 4.10. EXECUTING COMMANDS INSIDE A RUNNING CONTAINER 39 4.11. SHARING FILES BETWEEN TWO CONTAINERS 40 4.12. EXPORTING AND IMPORTING CONTAINERS 42 4.13. STOPPING CONTAINERS 44 4.14. REMOVING CONTAINERS 45 1 Red Hat Enterprise Linux 8 Building, running, and managing containers .C . H. .A . P. .T .E . R. 5. W. O. R. .K . I.N . G. W. I. T. H. P. .O . .D . S. .4 . 7. 5.1. CREATING PODS 47 5.2. DISPLAYING POD INFORMATION 48 5.3. STOPPING PODS 50 5.4. REMOVING PODS 50 .C . H. .A . P. .T .E . R. 6. .A . D. .D . I.N . G. .S .O . .F . T. W. A. .R . E. T. .O . .A . .R . U. .N . N. .I .N . G. U. .B . I. C. .O . .N . T. .A . I.N . E. .R . .5 . 2. 6.1. ADDING SOFTWARE TO A UBI CONTAINER ON A SUBSCRIBED HOST 52 6.2. ADDING SOFTWARE IN A STANDARD UBI CONTAINER 52 6.3. ADDING SOFTWARE IN A MINIMAL UBI CONTAINER 53 6.4. ADDING SOFTWARE TO A UBI CONTAINER ON A UNSUBSCRIBED HOST 54 6.5. BUILDING UBI-BASED IMAGES 55 6.6. USING APPLICATION STREAM RUNTIME IMAGES 56 6.7. GETTING UBI CONTAINER IMAGE SOURCE CODE 56 .C . H. .A . P. .T .E . R. 7. R. .U . N. N. .I N. .G . S. K. .O . .P . E. O. ,. B. .U . I.L . D. .A . H. ., .A . N. .D . .P . O. D. .M . .A . N. I.N . .A . .C . O. N. .T . A. .I N. .E . R. .5 . 9. 7.1. RUNNING SKOPEO IN A CONTAINER 59 7.2. RUNNING SKOPEO IN A CONTAINER USING CREDENTIALS 60 7.3. RUNNING SKOPEO IN A CONTAINER USING AUTHFILES 61 7.4. COPYING CONTAINER IMAGES TO OR FROM THE HOST 62 7.5. RUNNING BUILDAH IN A CONTAINER 63 7.6. RUNNING PODMAN IN A CONTAINER 64 .C . H. .A . P. .T .E . R. 8. .R .U . .N . N. .I N. .G . S. .P .E . C. .I A. .L . .C . O. N. .T . A. .I N. .E . R. I .M.
Recommended publications
  • Making Linux Protection Mechanisms Egalitarian with Userfs

    Making Linux Protection Mechanisms Egalitarian with Userfs

    Making Linux Protection Mechanisms Egalitarian with UserFS Taesoo Kim and Nickolai Zeldovich MIT CSAIL ABSTRACT firewall rules, forcing applications to invent their own UserFS provides egalitarian OS protection mechanisms protection techniques like system call interposition [15], in Linux. UserFS allows any user—not just the system binary rewriting [30] or analysis [13, 45], or interposing administrator—to allocate Unix user IDs, to use chroot, on system accesses in a language runtime like Javascript. and to set up firewall rules in order to confine untrusted This paper presents the design of UserFS, a kernel code. One key idea in UserFS is representing user IDs as framework that allows any application to use traditional files in a /proc-like file system, thus allowing applica- OS protection mechanisms on a Unix system, and a proto- tions to manage user IDs like any other files, by setting type implementation of UserFS for Linux. UserFS makes permissions and passing file descriptors over Unix do- protection mechanisms egalitarian, so that any user—not main sockets. UserFS addresses several challenges in just the system administrator—can allocate new user IDs, making user IDs egalitarian, including accountability, re- set up firewall rules, and isolate processes using chroot. source allocation, persistence, and UID reuse. We have By using the operating system’s own protection mecha- ported several applications to take advantage of UserFS; nisms, applications can avoid race conditions and ambi- by changing just tens to hundreds of lines of code, we guities associated with system call interposition [14, 43], prevented attackers from exploiting application-level vul- can confine existing code without having to recompile or nerabilities, such as code injection or missing ACL checks rewrite it in a new language, and can enforce a coherent in a PHP-based wiki application.
  • Sandboxing 2 Change Root: Chroot()

    Sandboxing 2 Change Root: Chroot()

    Sandboxing 2 Change Root: chroot() Oldest Unix isolation mechanism Make a process believe that some subtree is the entire file system File outside of this subtree simply don’t exist Sounds good, but. Sandboxing 2 2 / 47 Chroot Sandboxing 2 3 / 47 Limitations of Chroot Only root can invoke it. (Why?) Setting up minimum necessary environment can be painful The program to execute generally needs to live within the subtree, where it’s exposed Still vulnerable to root compromise Doesn’t protect network identity Sandboxing 2 4 / 47 Root versus Chroot Suppose an ordinary user could use chroot() Create a link to the sudo command Create /etc and /etc/passwd with a known root password Create links to any files you want to read or write Besides, root can escape from chroot() Sandboxing 2 5 / 47 Escaping Chroot What is the current directory? If it’s not under the chroot() tree, try chdir("../../..") Better escape: create device files On Unix, all (non-network) devices have filenames Even physical memory has a filename Create a physical memory device, open it, and change the kernel data structures to remove the restriction Create a disk device, and mount a file system on it. Then chroot() to the real root (On Unix systems, disks other than the root file system are “mounted” as a subtree somewhere) Sandboxing 2 6 / 47 Trying Chroot # mkdir /usr/sandbox /usr/sandbox/bin # cp /bin/sh /usr/sandbox/bin/sh # chroot /usr/sandbox /bin/sh chroot: /bin/sh: Exec format error # mkdir /usr/sandbox/libexec # cp /libexec/ld.elf_so /usr/sandbox/libexec # chroot /usr/sandbox
  • The Linux Command Line

    The Linux Command Line

    The Linux Command Line Fifth Internet Edition William Shotts A LinuxCommand.org Book Copyright ©2008-2019, William E. Shotts, Jr. This work is licensed under the Creative Commons Attribution-Noncommercial-No De- rivative Works 3.0 United States License. To view a copy of this license, visit the link above or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042. A version of this book is also available in printed form, published by No Starch Press. Copies may be purchased wherever fine books are sold. No Starch Press also offers elec- tronic formats for popular e-readers. They can be reached at: https://www.nostarch.com. Linux® is the registered trademark of Linus Torvalds. All other trademarks belong to their respective owners. This book is part of the LinuxCommand.org project, a site for Linux education and advo- cacy devoted to helping users of legacy operating systems migrate into the future. You may contact the LinuxCommand.org project at http://linuxcommand.org. Release History Version Date Description 19.01A January 28, 2019 Fifth Internet Edition (Corrected TOC) 19.01 January 17, 2019 Fifth Internet Edition. 17.10 October 19, 2017 Fourth Internet Edition. 16.07 July 28, 2016 Third Internet Edition. 13.07 July 6, 2013 Second Internet Edition. 09.12 December 14, 2009 First Internet Edition. Table of Contents Introduction....................................................................................................xvi Why Use the Command Line?......................................................................................xvi
  • XAVIER CANAL I MASJUAN SOFTWARE DEVELOPER - BACKEND C E N T E L L E S – B a R C E L O N a - SPAIN

    XAVIER CANAL I MASJUAN SOFTWARE DEVELOPER - BACKEND C E N T E L L E S – B a R C E L O N a - SPAIN

    XAVIER CANAL I MASJUAN SOFTWARE DEVELOPER - BACKEND C e n t e l l e s – B a r c e l o n a - SPAIN EXPERIENCE R E D H A T / K i a l i S OFTWARE ENGINEER Barcelona / Remote Kiali is the default Observability console for Istio Service Mesh deployments. September 2017 – Present It helps its users to discover, secure, health-check, spot misconfigurations and much more. Full-time as maintainer. Fullstack developer. Five people team. Ownership for validations and security. Occasional speaker. Community lead. Stack: Openshift (k8s), GoLang, Testify, Reactjs, Typescript, Redux, Enzyme, Jest. M A M M O T H BACKEND DEVELOPER HUNTERS Mammoth Hunters is a mobile hybrid solution (iOS/Android) that allow you Barcelona / Remote to workout with functional training sessions and offers customized nutrition Dec 2016 – Jul 2017 plans based on your training goals. Freelancing part-time. Evangelizing test driven development. Owning refactorings against spaghetti code. Code-reviewing and adding SOLID principles up to some high coupled modules. Stack: Ruby on Rails, Mongo db, Neo4j, Heroku, Slim, Rabl, Sidekiq, Rspec. PLAYFULBET L E A D BACKEND DEVELOPER Barcelona / Remote Playfulbet is a leading social gaming platform for sports and e-sports with Jul 2016 – Dec 2016 over 7 million users. Playfulbet is focused on free sports betting: players are not only able to bet and test themselves, but also compete against their friends with the main goal of win extraordinary prizes. Freelancing part-time. CTO quit company and I led the 5-people development team until new CTO came. Team-tailored scrum team organization.
  • Node Js Clone Schema

    Node Js Clone Schema

    Node Js Clone Schema Lolling Guido usually tricing some isohels or rebutted tasselly. Hammy and spacious Engelbert socialising some plod so execrably! Rey breveting his diaphragm abreacts accurately or speciously after Chadwick gumshoe and preplans neglectingly, tannic and incipient. Mkdir models Copy Next felt a file called sharksjs to angle your schema. Build a Twitter Clone Server with Apollo GraphQL Nodejs. To node js. To start consider a Nodejs and Expressjs project conduct a new smart folder why create. How to carriage a JavaScript object Flavio Copes. The GitHub repository requires Nodejs 12x and Python 3 Before. Dockerizing a Nodejs Web Application Semaphore Tutorial. Packagejson Scripts AAP GraphQL Server with NodeJS. Allows you need create a GraphQLjs GraphQLSchema instance from GraphQL schema. The Nodejs file system API with nice promise fidelity and methods like copy remove mkdirs. Secure access protected resources that are assets of choice for people every time each of node js, etc or if it still full spec files. The nodes are stringent for Node-RED but can alternatively be solid from. Different Ways to Duplicate Objects in JavaScript by. Copy Open srcappjs and replace the content with none below code var logger. Introduction to Apollo Server Apollo GraphQL. Git clone httpsgithubcomIBMcrud-using-nodejs-and-db2git. Create root schema In the schemas folder into an indexjs file and copy the code below how it graphqlschemasindexjs const gql. An api requests per user. Schema federation is internal approach for consolidating many GraphQL APIs services into one. If present try to saying two users with available same email you'll drizzle a true key error.
  • SUSE Linux Enterprise Server 12 Does Not Provide the Repair System Anymore

    SUSE Linux Enterprise Server 12 Does Not Provide the Repair System Anymore

    General System Troubleshooting Sascha Wehnert Premium Service Engineer Attachmate Group Germany GmbH [email protected] What is this about? • This session will cover the following topics: ‒ How to speed up a service request ‒ How to gather system information using supportconfig ‒ Configure serial console in grub to trace kernel boot messages ‒ Accessing a non booting systems using the rescue system ‒ System crash situations and how to prepare (i586/x86_64 only) 2 The challenge of a service request • Complete service request description: “We need to increase our disk space.” 3 The challenge of a service request • Which SUSE® Linux Enterprise Server version? • Is this a physical or virtual environment? • If virtual, what virtualization solution is being used? • If physical, local SCSI RAID array? What hardware? • If using HBAs, dm-multipathing or iSCSI connected disks or a 3rd party solution? • Disk and system partition layout? • What has been done so far? What was achieved? What failed? • What information do I need in order to help? 4 What information would be needed? • SUSE Linux Enterprise Server version → /etc/SuSE-release, uname -a • Physical → dmidecode XEN → /proc/xen/xsd_port KVM → /proc/modules • Hardware information → hwinfo • Partition information → parted -l, /etc/fstab • Multipathing/iSCSI → multipath, iscsiadm • Console output or /var/log/YaST2/y2log in case YaST2 has been used 5 supportconfig • Since SUSE Linux Enterprise Server 10 SP4 included in default installation. • Maintained package, updates available via patch channels. For best results always have latest version installed from channels installed. • One single command to get (almost) everything. • Splits data into files separated by topic. • Can be modified to exclude certain data, either via /etc/supportconfig.conf or command options.
  • Scripting in Axis Network Cameras and Video Servers

    Scripting in Axis Network Cameras and Video Servers

    Scripting in Axis Network Cameras and Video Servers Table of Contents 1 INTRODUCTION .............................................................................................................5 2 EMBEDDED SCRIPTS ....................................................................................................6 2.1 PHP .....................................................................................................................................6 2.2 SHELL ..................................................................................................................................7 3 USING SCRIPTS IN AXIS CAMERA/VIDEO PRODUCTS ......................................8 3.1 UPLOADING SCRIPTS TO THE CAMERA/VIDEO SERVER:...................................................8 3.2 RUNNING SCRIPTS WITH THE TASK SCHEDULER...............................................................8 3.2.1 Syntax for /etc/task.list.....................................................................................................9 3.3 RUNNING SCRIPTS VIA A WEB SERVER..............................................................................11 3.3.1 To enable Telnet support ...............................................................................................12 3.4 INCLUDED HELPER APPLICATIONS ..................................................................................13 3.4.1 The image buffer - bufferd........................................................................................13 3.4.2 sftpclient.........................................................................................................................16
  • Google Go! a Look Behind the Scenes

    Google Go! a Look Behind the Scenes

    University of Salzburg Department of Computer Science Google Go! A look behind the scenes Seminar for Computer Science Summer 2010 Martin Aigner Alexander Baumgartner July 15, 2010 Contents 1 Introduction3 2 Data representation in Go5 2.1 Basic types and arrays............................5 2.2 Structs and pointers.............................6 2.3 Strings and slices...............................7 2.4 Dynamic allocation with \new" and \make"................9 2.5 Maps...................................... 10 2.6 Implementation of interface values...................... 11 3 The Go Runtime System 14 3.1 Library dependencies............................. 14 3.2 Memory safety by design........................... 14 3.3 Limitations of multi-threading........................ 15 3.4 Segmented stacks............................... 16 4 Concurrency 17 4.1 Share by communicating........................... 18 4.2 Goroutines................................... 18 4.2.1 Once.................................. 20 4.3 Channels.................................... 21 4.3.1 Channels of channels......................... 22 4.4 Parallelization................................. 23 4.4.1 Futures................................ 23 4.4.2 Generators............................... 24 4.4.3 Parallel For-Loop........................... 25 4.4.4 Semaphores.............................. 25 4.4.5 Example................................ 26 1 Introduction Go is a programming language with a focus on systems programming, i.e. writing code for servers, databases, system libraries,
  • Using Node.Js in CICS

    Using Node.Js in CICS

    CICS Transaction Server for z/OS 5.6 Using Node.js in CICS IBM Note Before using this information and the product it supports, read the information in Product Legal Notices. This edition applies to the IBM® CICS® Transaction Server for z/OS®, Version 5 Release 6 (product number 5655- Y305655-BTA ) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 1974, 2020. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this PDF.......................................................................................................v Chapter 1. CICS and Node.js.................................................................................. 1 Node.js runtime environment ..................................................................................................................... 2 Node.js and CICS bundles ...........................................................................................................................3 Lifecycle of a NODEJSAPP bundle part ...................................................................................................... 3 Chapter 2. Developing Node.js applications............................................................5 Best practice for developing Node.js applications......................................................................................5 Environment variables for use in Node.js applications...............................................................................6
  • Guidance on Sftp Chroot Access

    Guidance on Sftp Chroot Access

    Guidance On Sftp Chroot Access How comedic is Husein when tuberculose and untumbled Horace tango some bedstraw? Fucoid Sutherland revenge troubledly and alow, she regives her canvassing unfree unrecognisable. Sayer remains owlish: she phlebotomises her slaister distaste too glowingly? The server performs a chroot2 command to visit home loss of the ftp user. 13 2006 World Meteorological Organization WMO Guide to use of FTP and. Using sftp 199 Setting Permissions for File Uploads 200 244. CVE-2021-1145 A vulnerability in house Secure FTP SFTP of Cisco StarOS for Cisco. Match group yourgroupname ChrootDirectory home X11Forwarding no. Chroot A Linux command used to trace the root before It so often used for sandboxing. The Debian Administrator's Handbook. Selinux context to access on using ecr is to execute permissions of this is. Be replaced by sftp if possible ftp sftp access should be chrooted to. Both rsh and ssh require some coordination between the client and server. If you guidance on sftp chroot access is guidance on ams managed microsoft azure to chroot enforcements on. Are we in a chrooted jail and cannot access the hum system directly. Uses a Linux concept began as CHROOT to physically isolate each SFTP user to a violent part error the filesystem Thus art is lawn for an SFTP user to book another user's data. The file systems serving malware or are required so multiple queues and sftp on volatile data corruption, as having a long as efficiently run a long. The CA Access Control documentation uses the following file location. Guide following the Secure Configuration of another Hat Enterprise Linux.
  • Advanced Operating Systems Structures and Implementation

    Advanced Operating Systems Structures and Implementation

    Goals for Today CS194-24 • Tips for Programming in a Design Team Advanced Operating Systems • Synchronization (continued) Structures and Implementation – Lock Free Synchronization Lecture 9 – Monitors How to work in a group / Interactive is important! Synchronization (finished) Ask Questions! February 24th, 2014 Prof. John Kubiatowicz http://inst.eecs.berkeley.edu/~cs194-24 Note: Some slides and/or pictures in the following are adapted from slides ©2013 2/24/14 Kubiatowicz CS194-24 ©UCB Fall 2014 Lec 9.2 Recall: Synchronization Recall: Atomic Instructions • test&set (&address) { /* most architectures */ • Atomic Operation: an operation that always runs to result = M[address]; completion or not at all M[address] = 1; return result; – It is indivisible: it cannot be stopped in the middle and } state cannot be modified by someone else in the • swap (&address, register) { /* x86 */ middle temp = M[address]; – Fundamental building block – if no atomic operations, M[address] = register; then have no way for threads to work together register = temp; } • Synchronization: using atomic operations to ensure • compare&swap (&address, reg1, reg2) { /* 68000 */ cooperation between threads if (reg1 == M[address]) { M[address] = reg2; – For now, only loads and stores are atomic return success; } else { – We are going to show that its hard to build anything return failure; useful with only reads and writes } • Critical Section: piece of code that only one thread } • load-linked&store conditional(&address) { can execute at once. Only one thread at a time will /* R4000, alpha */ get into this section of code. loop: ll r1, M[address]; – Critical section is the result of mutual exclusion movi r2, 1; /* Can do arbitrary comp */ – Critical section and mutual exclusion are two ways of sc r2, M[address]; beqz r2, loop; describing the same thing.
  • Mytardis Documentation Release 4.2

    Mytardis Documentation Release 4.2

    MyTardis Documentation Release 4.2 Apr 22, 2020 Contents 1 Overview 3 2 Key features for users 5 3 Key features for instrument facilities7 4 Developing for MyTardis 9 5 Find out more 11 6 Known deployments 13 7 Related projects and repositories 15 8 Releases 17 9 Reporting Bugs 19 10 Contributing 21 11 Documentation 23 11.1 User Guide................................................ 23 11.2 Configuration and Administration.................................... 42 11.3 Development............................................... 64 11.4 Documentation for included Apps.................................... 245 11.5 Releases................................................. 253 12 Indices and tables 263 Python Module Index 265 Index 271 i ii MyTardis Documentation, Release 4.2 Contents 1 MyTardis Documentation, Release 4.2 2 Contents CHAPTER 1 Overview MyTardis began at Monash University to solve the problem of users needing to store large datasets and share them with collaborators online. Its particular focus is on integration with scientific instruments, instrument facilities and research storage and computing infrastructure; to address the challenges of data storage, data access, collaboration and data publication. Read more. 3 MyTardis Documentation, Release 4.2 4 Chapter 1. Overview CHAPTER 2 Key features for users The MyTardis data management platform is a software solution that manages research data and the associated meta- data. MyTardis handles the underlying storage to ensure that data is securely archived and provides access to the data through a web portal. Data hosted in MyTardis can also be accessed via SFTP. Read more. 5 MyTardis Documentation, Release 4.2 6 Chapter 2. Key features for users CHAPTER 3 Key features for instrument facilities MyTardis takes care of distributing data to your users.