DOCSLIB.ORG

Légende : Montage Webdav/DAFVS2 [Tuto/Howto] [GNU/Linux] Montage

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Légende : Montage Webdav/DAFVS2 [Tuto/Howto] [GNU/Linux] Montage Nebuleuse0rion Lost in the Digital Dimension Search… Quick links FAQ Register Login Index ‹ Techno ‹ Operating System ‹ Memory [Tuto/HowTo] Monter dossier distant sur Raspberry Pi & Ubuntu/Debian Post Reply Search this topic… 7 posts • Page 1 of 1 [Tuto/HowTo] Monter dossier distant sur Raspberry Pi & Ubuntu/Debian by voxdemonix » Mon Apr 25, 2016 12:45 pm P voxdemonix o s Posts: 830 t Joined: Mon Feb 02, 2015 7:28 pm Licence du tuto : - - L'ensemble de ces tutos fonctionne sur : Raspbian, (X|K|L)Ubuntu, Debian et tout ses dérivés Légende : 1. Montage Webdav/DAVFS 2. Montage Webdav/DAVFS via SSH Tunneling over Tor 3. Montage SSHFS 4. Montage SFTP 5. Monter un volume/répertoire GlusterFS 6. Montage Webdav/DAFVS2 cross-canal via SSH Tunneling Last edited by voxdemonix on Sun Dec 18, 2016 6:22 pm, edited 25 times in total. ~ Infernalis Creatorem ~ Rejoins le côté obscure, on a des cookies ! Donation Bitcoin : 1N8QGrhJGWdZNQNSspm3rSGjtXaXv9Ngat Donation Dash : XmowiBRku3tsEREp7PhpheY4TgeLLDyKdM T o Re: [Tuto/HowTo] Monter dossier distant sur Raspberry Pi & Ubuntu/Debian p by voxdemonix » Sat Apr 30, 2016 11:20 pm P o voxdemonix s Montage Webdav/DAFVS2 Posts: 830 t DAFVS2 est entre autre utilisé pour monter localement des dossiers distant hébergés sur un serveur owncloud/nextcloud. Il Joined: Mon Feb 02, 2015 7:28 pm utilise le protocole HTTP(S) se qui le rend plus lent (lag) mais compatible avec le Web. Si vous souhaitez effectuer le montage à travers internet (si vous êtes en adressage dynamique) il vous est conseillé d'utiliser un nom de domaine (ou plusieurs) et/ou un Tor Hidden Service. Note : si votre système freeze (se gèle/plante) lorsque vous ouvrez un dossier distant plein de vidéos jetez un œil sur ce topic : [Tuto/HowTo] [GNU/Linux] Désactiver les prévisualisations (thumbnail) des fichiers vidéos sur Xubuntu Attention : Il y a des problèmes avec certains logiciels (exemple : jdownloader, transmission) qui ont des difficultés en lecture/écriture avec les montages webdav/davfs2. Liens utile : Motion - Exporter les images/clip vers owncloud à la place du stockage local. [Tuto/HowTo] [GNU/Linux] [server] afficher sur son site web des ressources (images, vidéos, etc) rangées sur son cloud [Tuto/HowTo] [CMS&Kit] installer manuellement Owncloud auto hébergé avec apache2/PHP7 [Tuto/HowTo] [GNU/Linux] [CMS&Kit] installer Nextcloud avec apache2, mariadb et PHP7 Pré-requis sur le client 1. Installer les logiciels nécessaire CODE: SELECT ALL sudo apt-get install davfs2 2. Autoriser les utilisateurs non-root à monter le dossier CODE: SELECT ALL sudo dpkg-reconfigure davfs2 3. Créer le point de montage local (adaptez à vos envies) CODE: SELECT ALL sudo mkdir /media/monPointDeMontageLocal 4. Ajoutez l'utilisateur au groupe davfs2 (remplacez $USER par votre utilisateur) CODE: SELECT ALL sudo adduser $USER davfs2 5. Créez le dossier de config de davfs2 CODE: SELECT ALL mkdir $HOME/.davfs2 6. Copiez les fichiers de config de base dans votre dossier de config perso CODE: SELECT ALL cp /etc/davfs2/davfs2.conf $HOME/.davfs2/ sudo cp /etc/davfs2/secrets $HOME/.davfs2 sudo chown $USER $HOME/.davfs2/secrets 7. Il faut ajouter les informations dans le fichier /home/user/.davfs2/secrets CODE: SELECT ALL nano $HOME/.davfs2/secrets Ajoutez à la fin du fichier la ligne suivante en l'adaptant : CODE: SELECT ALL /media/monPointDeMontageLocal monLogin monPasswordEnClair 8. Accorder les bons droits sur les dossiers/fichiers de conf : CODE: SELECT ALL sudo chown $USER $HOME/.davfs2/ -R sudo chmod 400 $HOME/.davfs2/secrets sudo chmod 700 $HOME/.davfs2/cache 9. Télécharger le certificat SSL/TLS : CODE: SELECT ALL openssl s_client -connect HOSTNAME:443 -showcerts </dev/null 2>/dev/null | openssl x509 -outform PEM > certificateOwncloud.pem Note : cette commande a fonctionné en locale mais étonnamment PAS via internet (une erreur étrange en est ressortis), Tor Browser arrive à la rescousse dans ces cas là. Vous vous rendez avec sur votre owncloud, vous cliquez sur le cadena situé à gauche de la barre d'adresse, ensuite la petite flèche puis "Plus d'informations". Dans la fenêtre qui s'ouvre allez dans l'onglet "Sécurité" et cliquez sur "Afficher le certificat". Onglet "Détails" et cliquez enfin sur "Exporter". Utilisez sftp pour expédier rapidement le certificat depuis votre PC vers votre raspberry pi. 10. Déplacer le certificat dans le dossier des trusted CODE: SELECT ALL sudo mv ./certificateOwncloud.pem /etc/davfs2/certs/ 11. Maintenant on va l'ajouter à la liste des trusted de davfs2 CODE: SELECT ALL sudo nano /etc/davfs2/davfs2.conf #mes certificats SSL trust_server_cert /etc/davfs2/certs/certificateOwncloud.pem Monter automatiquement au démarrage sur le client 1. Ouvrez le fichier /etc/fstab CODE: SELECT ALL sudo nano /etc/fstab Et ajoutez le lignes suivantes en les adaptant à votre configuration # Mon montage davfs2 https://HOSTNAME:PORT/owncloud/remote.php/webdav/ /media/monPointDeMontageLocal davfs _netdev,rw,user 0 0 Erreurs : /sbin/mount.davfs: wrong permissions set for cache directory /home/USER/.davfs2/cache/127.0.0.1-owncloud-remote.php- webdav+media-owncloud+USER CODE: SELECT ALL sudo chown $USER /home/USER/.davfs2/cache -R sudo chmod 700 /home/USER/.davfs2/cache -R /sbin/mount.davfs: file /home/USER/.davfs2/secrets has wrong owner CODE: SELECT ALL sudo chown $USER /home/USER/.davfs2/secrets sudo chmod 700 /home/USER/.davfs2/secrets Last edited by voxdemonix on Fri Dec 30, 2016 11:49 pm, edited 26 times in total. ~ Infernalis Creatorem ~ Rejoins le côté obscure, on a des cookies ! Donation Bitcoin : 1N8QGrhJGWdZNQNSspm3rSGjtXaXv9Ngat Donation Dash : XmowiBRku3tsEREp7PhpheY4TgeLLDyKdM T o Re: [Tuto/HowTo] Monter dossier distant sur Raspberry Pi & Ubuntu/Debian p by voxdemonix » Sat Apr 30, 2016 11:57 pm P o voxdemonix Msontage Webdav/DAFVS2 à travers Tor Via SSH Tunneling Posts: 830 t Joined: Mon Feb 02, 2015 7:28 pm Cette fois on va ouvrir un tunnel ssh avec auto-reconnexion en cas de perte de liaison qui transitera à travers le réseau Tor. Utiliser TLS (HTTPS) n'est pas requis dans ce cas de situation, mais tout à fait utilisable (ça fait 3 tunnels : Tor + SSH + TLS). En effet les données sont chiffrées à de multiples reprises dans les tunnels de données créés par le routage en oignons utilisé par Tor et ne sont déchiffrées par Tor que lorsqu'elles sont arrivées sur le Tor Hidden Service. De surcroît le tunnel de données SSH est lui aussi chiffré. Ensuite nous monterons le répertoire distant via davfs en suivant le tuto précédent juste en modifiant une ligne. Par contre avec l'utilisation de tor la bande passante (l'upload/download) est limitée et la consommation de ressources machine plus élevée. Attention : cette méthode lag et provoque un ralentissement désagréable du gestionnaire de fichiers (étrangement y compris dans le shell pour l'auto-complétion de nom de fichiers/dossiers même s'ils se trouvent sur le disque local, l'utilisation de "cd", "ls"). Je vous conseil de désactiver la génération de miniatures (thumbnails) des vidéos en suivant ce topic [Tuto/HowTo] [GNU/Linux] Désactiver les prévisualisations (thumbnail) des fichiers vidéos sur Xubuntu Note : En utilisant ce script pour créer le tunnel SSH, vous pouvez créer un montage distant qui passe par le LAN quand vous êtes sur le même réseau que le serveur et via le réseau Tor lorsque vous êtes sur Internet. Ça blinde votre sécurité tout en diminuant la consommation électrique et ressource machine. Attention : Il y a des problèmes avec certains logiciels (exemple : jdownloader, transmission) qui ont des difficultés en lecture/ écriture avec les montages webdav/davfs2. Sources : [Tuto/HowTo] [GNU/Linux] mettre en place un ou plusieurs Tunnel SSH [Tuto/HowTo] Garder un contrôle discret sur son serveur avec tor et ssh [Tuto/HowTo] Utiliser le client Owncloud à travers Tor via SSH Tunneling Montage DAFVS2 [Tuto/HowTo] [GNU/Linux] SSH [Tuto/HowTo] [GNU/Linux] Montage SSHFS cross-canal (Lan, Wan, Tor, etc) Côté Serveur 1. Tout d'abord, installez Tor et SSH: CODE: SELECT ALL sudo apt-get install tor openssh-server -y 2. Éditez le fichier /etc/tor/torrc : CODE: SELECT ALL sudo nano /etc/tor/torrc 3. Cherchez (CTRL+W) "hidden service" et dé-commentez (ou ajouter selon votre envie) les lignes suivantes : CODE: SELECT ALL HiddenServiceDir /var/lib/tor/hidden_service/ssh HiddenServicePort 22 127.0.0.1:22 4. Ensuite bien entendu créer le dossier /var/lib/tor/hidden_service/ssh et son cheminement : CODE: SELECT ALL sudo mkdir /var/lib/tor/hidden_service sudo mkdir /var/lib/tor/hidden_service/ssh 5. Accordez les permissions : CODE: SELECT ALL sudo chown debian-tor:root -R /var/lib/tor/hidden_service/ sudo chmod 700 -R /var/lib/tor/hidden_service/ 6. Redémarrez Tor : CODE: SELECT ALL sudo service tor restart 7. Récupérez l'adresse de l'hidden service : CODE: SELECT ALL sudo cat /var/lib/tor/hidden_service/ssh/hostname Notez quelque part le retour de cette commande car ça sera utile pour la suite. Côté client : 1. Installez les pré-requis : CODE: SELECT ALL sudo apt-get install openssh-client autossh tor netcat davfs2 -y Section SSH 2. Rendre compatible le client ssh avec tor en éditant le fichier de configuration de ssh ( /etc/ssh/ssh_config ) afin d'ajouter un proxy local (netcat) : CODE: SELECT ALL sudo nano /etc/ssh/ssh_config 3. Ajoutez les lignes suivantes : CODE: SELECT ALL Host *.onion ProxyCommand nc -xlocalhost:9050 -X5 %h %p ( CTRL+X = SAVE&QUIT ) 4. Générez vos clés : CODE: SELECT ALL ssh-keygen -t ed25519 -o -a 100 ssh-keygen -t rsa -b 4096 -o -a 100 5. Exporter votre clés sur votre serveur : CODE: SELECT ALL ssh-copy-id -i ~/.ssh/id_dsa.pub [email protected] 6. Ajoutez la clés à votre client : CODE: SELECT ALL ssh-add Note : si vous avez l'erreur Failed to add the host to the list of know hosts corrigez avec CODE: SELECT ALL sudo chown -v $USER ~/.ssh/known_hosts 7.
Load more

Recommended publications
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • Irods User Group Meeting 2016 Proceedings
    iRODS User Group Meeting 2016 Proceedings © 2016 All rights reserved. Each article remains the property of the authors. 8TH ANNUAL CONFERENCE SUMMARY The iRODS User Group Meeting of 2016 gathered together iRODS users, Consortium members, and staff to discuss iRODS-enabled applications and discoveries, technologies developed around iRODS, and future development and sustainability of iRODS and the iRODS Consortium. The two-day event was held on June 8th and 9th in Chapel Hill, North Carolina, hosted by the iRODS Consortium, with over 90 people attending. Attendees and presenters represented over 30 academic, government, and commercial institutions. Contents Listing of Presentations .......................................................................................................................................... 1 ARTICLES iRODS Audit (C++) Rule Engine Plugin and AMQP .............................................................................................. 5 Terrell Russell, Jason Coposky, Justin James - RENCI at UNC Chapel Hill Speed Research Discovery with Comprehensive Storage and Data Management .......................................... 21 HGST | PANASAS | iRODS Integrating HUBzero and iRODS ............................................................................................................................ 23 Rajesh Kalyanam, Robert A. Campbell, Samuel P. Wilson, Pascal Meunier, Lan Zhao, Elizabett A. Hillery, Carol Song - Purdue University An R Package to Access iRODS Directly ...........................................................................................................
    [Show full text]
  • The Evolution of File Systems
    The Evolution of File Systems Thomas Rivera, Hitachi Data Systems Craig Harmer, April 2011 SNIA Legal Notice The material contained in this tutorial is copyrighted by the SNIA. Member companies and individuals may use this material in presentations and literature under the following conditions: Any slide or slides used must be reproduced without modification The SNIA must be acknowledged as source of any material used in the body of any document containing material from these presentations. This presentation is a project of the SNIA Education Committee. Neither the Author nor the Presenter is an attorney and nothing in this presentation is intended to be nor should be construed as legal advice or opinion. If you need legal advice or legal opinion please contact an attorney. The information presented herein represents the Author's personal opinion and current understanding of the issues involved. The Author, the Presenter, and the SNIA do not assume any responsibility or liability for damages arising out of any reliance on or use of this information. NO WARRANTIES, EXPRESS OR IMPLIED. USE AT YOUR OWN RISK. The Evolution of File Systems 2 © 2012 Storage Networking Industry Association. All Rights Reserved. 2 Abstract The File Systems Evolution Over time additional file systems appeared focusing on specialized requirements such as: data sharing, remote file access, distributed file access, parallel files access, HPC, archiving, security, etc. Due to the dramatic growth of unstructured data, files as the basic units for data containers are morphing into file objects, providing more semantics and feature- rich capabilities for content processing This presentation will: Categorize and explain the basic principles of currently available file system architectures (e.g.
    [Show full text]
  • Silenus – a Federated Service-Oriented Approach To
    SILENUS – A FEDERATED SERVICE-ORIENTED APPROACH TO DISTRIBUTED FILE SYSTEMS by MAXIMILIAN BERGER, B.S. A DISSERTATION IN COMPUTER SCIENCE Submitted to the Graduate Faculty of Texas Tech University in Partial Fulfillment of the Requirements for the Degree of DOCTOR OF PHILOSOPHY Approved Michael Sobolewski Chairperson of the Committee Noé López-Benitez Michael Shin Per Anderson Accepted John Borrelli Dean of the Graduate School December, 2006 Copyright © 2006 Maximlilian Berger ACKNOWLEDGEMENTS I would like to thank my Advisor Dr. Michael Sobolweski. This thesis could not have been done without his permanent effort to keep me on focused on the goal. I would also like to thank Dr. Noe Lopez-Benitez, Dr. Michael Shin, and Dr. Per Anderson for serving in my comittee. They could provide me with a different viewpoint. A very special thanks goes to Barbara Hartmann for being the greatest person on earth and for making our relationship work half way around the globe for three years. I would also like to thank my best friend and roommate Nathan Larson. He was always there to support, no matter how crazy the idea. ii TABLE OF CONTENTS ACKNOWLEDGMENTS ...................................................................................... ii ABSTRACT .......................................................................................................... viii I. INTRODUCTION .............................................................................................. 1 Problem Statement ........................................................................................
    [Show full text]
  • A Federated Service-Oriented Approach to Distributed File Systems
    Next Generation Concurrent Engineering - M. Sobolewski & P. Ghodous (eds) © 2005 ISPE, Inc., ISBN 0-9768246-0-4 SILENUS - A federated service-oriented approach to distributed file systems Max Berger & Michael Sobolewski SORCER Research Group, Texas Tech University A new approach for a distributed file system SILENUS based on the federated service-oriented computing environment SORCER is presented. Instead of services running on specific computers, the system is build from federating services in the network. The services are: byte-store service (Byzantium) for the storage of the actual date; metadata-store service (Midas) for information about the files; WebDAV adapter (Daphne) for support for legacy applications and operating system; and optimizer services that keep the collaborating federations in a healthy state. This system implements file-based data grid services in the SORCER environment that are needed for collaboration of distributed teams. 1 INTRODUCTION distributed services enabling for robust, secure, and Ever since the introduction of a personal computer shared vast repository of engineering data. there exists the problem of managing distributed data. Under the sponsorship of the National Institute for This data is usually stored on one host and not easily Standards and Technology (NIST) the Federated In- accessible for other users or from other hosts. telligent Product Environment (FIPER) (Sobolewski The current trend goes away from a personal com- 2002a, b, Kolonay & Sobolewski 2004) was devel- puter back to a networked one. We want to work any- oped (1999-2003) as one of the first service-to-service where, anytime, and of course always have the same (S2S) grid computing environments.
    [Show full text]
  • Technical Notes All Changes in Fedora 13
    Fedora 13 Technical Notes All changes in Fedora 13 Edited by The Fedora Docs Team Copyright © 2010 Red Hat, Inc. and others. 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/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. 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, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https:// fedoraproject.org/wiki/Legal:Trademark_guidelines. 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. All other trademarks are the property of their respective owners. Abstract This document lists all changed packages between Fedora 12 and Fedora 13.
    [Show full text]
  • 1. Why POCS.Key
    Symptoms of Complexity Prof. George Candea School of Computer & Communication Sciences Building Bridges A RTlClES A COMPUTER SCIENCE PERSPECTIVE OF BRIDGE DESIGN What kinds of lessonsdoes a classical engineering discipline like bridge design have for an emerging engineering discipline like computer systems Observation design?Case-study editors Alfred Spector and David Gifford consider the • insight and experienceof bridge designer Gerard Fox to find out how strong the parallels are. • bridges are normally on-time, on-budget, and don’t fall ALFRED SPECTORand DAVID GIFFORD • software projects rarely ship on-time, are often over- AS Gerry, let’s begin with an overview of THE DESIGN PROCESS bridges. AS What is the procedure for designing and con- GF In the United States, most highway bridges are budget, and rarely work exactly as specified structing a bridge? mandated by a government agency. The great major- GF It breaks down into three phases: the prelimi- ity are small bridges (with spans of less than 150 nay design phase, the main design phase, and the feet) and are part of the public highway system. construction phase. For larger bridges, several alter- There are fewer large bridges, having spans of 600 native designs are usually considered during the Blueprints for bridges must be approved... feet or more, that carry roads over bodies of water, preliminary design phase, whereas simple calcula- • gorges, or other large obstacles. There are also a tions or experience usually suffices in determining small number of superlarge bridges with spans ap- the appropriate design for small bridges. There are a proaching a mile, like the Verrazzano Narrows lot more factors to take into account with a large Bridge in New Yor:k.
    [Show full text]
  • Apache - Korean Usergroup Webdav : Collaboration Based on Apache
    Apache - Korean UserGroup WebDAV : Collaboration based on Apache 김규([email protected]) 하 CSA,SCNA,CCNA,CISSP Korea technical office - CollabNet,Inc Computer Eng dept. - Hansung University Apache Korean User Group Apache Korean Session Summary User Group ¾ 협업 — WebDAV 이전의 아파치 웹서버 ¾ WebDAV란? — WebDAV Benefits ¾ WebDAV Basics — mod_dav 소개 ¾ WebDAV 활용 — WebDAV softwares ¾ WebDAV 설치 및 운영 ¾ SubVersion이란? — SubVersion & CVS features ¾ SubVersion 설치 및 운영 — SubVersion Basic work scenario — SubVersion softwares ¾ Resources & References ¾ Q&A -2 - Collaborations based on Apache http://www.apache-kr.org Apache Korean 협업 ? User Group ¾ Collaboration ¾ 협업 소프트웨어들 — Collaborative groupwares — Groove — Collaborative tools — Collaboration systems ¾ 협업 소프트웨어의 기본적인 요건들 참여자들의 입장에 따라 보장되는 가시성 완벽하고 실제적인 보안성 다양한 배경의 사용자들을 위한 확장성 언제 어디서든 표준환경으로 참여할 수 있는 접근성 쉬운 사용으로 교육 없이 참여할 수 있는 사용성 -3 - Collaborations based on Apache http://www.apache-kr.org Apache Korean 협업 ? User Group -4 - Collaborations based on Apache http://www.apache-kr.org Apache Korean 협업 ? User Group Tool & Embedded Mobile Service Technology Software Phone Providers Providers Companies Manufacturers Java Libraries IDEs WAP Protocol 1 “2G” CDMA WebSphere iMODE Protocol 2 “2.5G” CDMA IDEs Libraries C# Libraries SKVM IDEs SK WITOP “3G” GSM Content Providers e.g., daum, Yahoo, ISVs Users -5 - Collaborations based on Apache http://www.apache-kr.org Apache Korean 협업 ? User Group ¾ OpenSource Community — 비영리적 오픈소스 커 뮤니티 — 기업 주도의 오픈소스 커뮤니티 -6 - Collaborations based on Apache http://www.apache-kr.org Apache Korean WebDAV 이전의 아파치 웹서버 인프라 User Group ¾ Apache : A patched web server — HTTP 프로토콜을 기반 —WEB을 전 인류에게.
    [Show full text]
  • Machine Learning Cloud Getting Started Guide
    Machine Learning Cloud Getting started guide March 4th, 2020 Tübingen Outline • Who, what, how, … what again? o Our Cloud Infrastructure o Openstack, Storage, ... • General basics o SSH o DNS & TLS, … • Openstack basics: images, flavors, security groups, networks, floating IPs • Usage Terms, • VMs & Baremetal basics • How to create, connect and use • VM Hardening • Difference VM vs. Baremetal • GPUs (Driver, CUDA, within Docker) • Storage: Cinder, Quobyte, S3, WebDAV • Cloud-based services: Gitlab, Nextcloud, … • Docker • Support Who are we ... [email protected] [email protected] [email protected] [email protected] 07071 - 29 70282 Openstack – ML-Cloud Physical infrastructure ML-Cloud - TTR2 server room • 14x 1G Switches & 10x 40G Switches • 2x Provisioningmachines • 2x Loadbalancer • 3x Openstack controllers • 11x Storage servers (~1.8 PB, Quobyte software) • 12x GPU - Hypervisors with 4x Tesla V100 32GB RAM (NVLINK possible) • 7 Baremetal machines with 8x RTX 2080Ti 11GB RAM Insufficient cooling: Automatic server shutdown possibly without warning Openstack – what it is Most used open source IaaS platform o based on python, sql, messaging, http REST APIs, … o started by NASA & Rackspace, currently involved Companies: Red Hat/Ubuntu/Mirantis/... o commercially used (Telekom, …): Projects, Quotas o 2 major releases a year Multiple Services/Components o required: Keystone(Identity), Nova(Compute), Neutron(Network), Glance(Image) o optional: Horizon(Dashboard), Cinder(Blockstorage),
    [Show full text]
  • Grid4all D4.8 User Manual
    Project no. 034567 Grid4All Specific Targeted Research Project (STREP) Thematic Priority 2: Information Society Technologies D4.8 User Manual Due date of deliverable: 01-06-2009 Actual submission date: 20-07-2009 Start date of project: 1 June 2006 Duration: 36 months Contributors : Antares, ICCS, INRIA, FT, KTH, SICS, UPC, UPRC Project co-funded by the European Commission within the Sixth Framework Programme (2002-2006) Dissemination Level PU Public PP Restricted to other programme participants (including the Commission Services) RE Restricted to a group specified by the consortium (including the Commission Services) CO Confidential, only for members of the consortium (including the Commission Services) D4.8 User Manual Grid4All-034567 Table of Contents Abbreviations used in this document ......................................................................................................... 2 Grid4All list of participants .......................................................................................................................... 3 1 Executive Summary .................................................................................................................................... 4 2 Introduction ................................................................................................................................................. 5 3 Core VO services ........................................................................................................................................ 7 3.1 Niche, a Distributed
    [Show full text]
  • EWB Denver Webdisk Manual Version 0.91
    EWB Denver Webdisk Manual version 0.91 Summary This manual is for EWB Denver members for use with the file storage capabilities that are available on our organization's website. Our current web hosting provider calls this service a webdisk. Technically speaking, it's more like a web-based file system than a disk or a folder. However, for the purposes of this manual the term webdisk will be used. This manual is broken into two main sections. First is the users perspective which covers how to use a webdisk, and explains the reasons for using a webdisk. The second section is more for the IT personnel and those tech savvy folks who can set up either the operating system interface, or install the applications that are webdisk-aware. Section 1 – User's Manual What is a Webdisk? A webdisk is a web accessible storage area. Because it uses a communications protocol related to that used for serving web pages, web browsers have built-in capabilities for traversing and reading a webdisk. Additionally, the open standard protocol used with a webdisk allows many operating systems to treat them like a local file systems. Validated users can use familiar operating system utilities, like a file manager, to manipulate a webdisk. Also, applications that are webdisk-aware will allow validated users to use the webdisk as a file storage area. Why use it at EWB Denver? The main purpose for the webdisk is as a temporary shared storage area for preparing project materials. Another is for archiving project materials for future reference.
    [Show full text]
  • A Model to Manage Shared Mutable Data in a Distributed Environment
    THE SEA OF STUFF: A MODEL TO MANAGE SHARED MUTABLE DATA IN A DISTRIBUTED ENVIRONMENT Simone Ivan Conte A Thesis Submitted for the Degree of PhD at the University of St Andrews 2018 Full metadata for this thesis is available in St Andrews Research Repository at: http://research-repository.st-andrews.ac.uk/ Please use this identifier to cite or link to this thesis: http://hdl.handle.net/10023/16827 This item is protected by original copyright This item is licensed under a Creative Commons Licence https://creativecommons.org/licenses/by-nc-nd/4.0/ The Sea of Stuff: a Model to Manage Shared Mutable Data in a Distributed Environment Simone Ivan Conte This thesis is submitted in partial fulfilment for the degree of Doctor of Philosophy (PhD) at the University of St Andrews August 2018 ii Abstract Managing data is one of the main challenges in distributed systems and computer science in general. Data is created, shared, and managed across heterogeneous distributed systems of users, services, applications, and devices without a clear and comprehensive data model. This technological fragmentation and lack of a common data model result in a poor understanding of what data is, how it evolves over time, how it should be managed in a distributed system, and how it should be protected and shared. From a user perspective, for example, backing up data over multiple devices is a hard and error-prone process, or synchronising data with a cloud storage service can result in conflicts and unpredictable behaviours. This thesis identifies three challenges in data management: (1) how to extend the current data abstractions so that content, for example, is accessible irrespective of its location, versionable, and easy to distribute; (2) how to enable transparent data storage relative to locations, users, applications, and services; and (3) how to allow data owners to protect data against malicious users and automatically control content over a distributed system.
    [Show full text]