About Vagrant - Vagrant Vagrant is a tool for building complete development environments. With an easy-to-use workflow and focus on automation, Vagrant lowers development environment setup time, increases development/production parity, and makes the "works on my machine" excuse a relic of the past. Vagrant was started in January 2010 by Mitchell Hashimoto. For almost three years, Vagrant was a side-project for Mitchell, a project that he worked on in his free hours after his full time job. During this time, Vagrant grew to be trusted and used by a range of individuals to entire development teams in large companies. In November 2012, HashiCorp was formed by Mitchell to back the development of Vagrant full time. Vagrant remains and always will be a liberally licensed open source project.
ZeroPC - Your content navigator for the cloud OpenChange Project - Alternative to Microsoft Exchange Because Hadoop isn’t perfect: 8 ways to replace HDFS Hadoop is on its way to becoming the de facto platform for the next-generation of data-based applications, but it’s not without flaws. Ironically, one of Hadoop’s biggest shortcomings now is also one of its biggest strengths going forward — the Hadoop Distributed File System. Within the Apache Software Foundation, HDFS is always improving in terms of performance and availability. But if the growing number of options for replacing HDFS signifies anything, it’s that HDFS isn’t quite where it needs to be. Cassandra (DataStax) Not a file system at all but an open source, NoSQL key-value store, Cassandra has become a viable alternative to HDFS for web applications that rely on fast data access. Ceph Ceph is an open source, multi-pronged storage system that was recently commercialized by a startup called Inktank. Dispersed Storage Network (Cleversafe) Isilon (EMC) Lustre MapR File System NetApp Open Solution for Hadoop Feature image courtesy of Shutterstock user Panos Karapanagiotis.
Btrfs Btrfs (B-tree file system, variously pronounced: "Butter F S", "Butterface", "Better F S", "B-tree F S", or simply by spelling it out) is a GPL-licensed copy-on-write file system for Linux. Development began at Oracle Corporation in 2007. As of August 2014[update], the file system's on-disk format has been marked as stable. History The core data structure of Btrfs—the copy-on-write B-tree—was originally proposed by IBM researcher Ohad Rodeh at a presentation at USENIX 2007. In 2008, the principal developer of the ext3 and ext4 file systems, Theodore Ts'o, stated that although ext4 has improved features, it is not a major advance; it uses old technology and is a stop-gap. In 2011, de-fragmentation features were announced for version 3.0 of the Linux kernel. Besides Mason at Oracle, Miao Xie at Fujitsu contributed performance improvements. In June 2012, Chris Mason left Oracle, but still continues to work on Btrfs. Features Planned features include:
Puppet Open Source: IT Automation Software for System Administrators Puppet Open Source is a flexible, customizable framework available under the Apache 2.0 license designed to help system administrators automate the many repetitive tasks they regularly perform. As a declarative, model-based approach to IT automation, it lets you define the desired state - or the “what” - of your infrastructure using the Puppet configuration language. Once these configurations are deployed, Puppet automatically installs the necessary packages and starts the related services, and then regularly enforces the desired state. Getting Puppet There are several different ways to get Puppet Open Source: You can likely find Puppet in your favorite Linux distro’s package repositoriesIf you’re using Amazon EC2, the Amazon Linux AMI now bundles PuppetGet the source code for Puppet Open Source from githubDownload packages from our Yum and APT repositories.Download the binaries here Community Learn More MCollective Project
Firedrive | Free Cloud Storage for Everyone Review: LiveCode Community is open-source HyperCard for the 21st century Many years ago, there was HyperCard, included free with the Macintosh in the late 1980s. It got a lot of attention because it was one of the first tools that made it trivial to create GUI applications. Apple couldn't figure out how to properly market or position it, so it eventually died of apathy. RunRev has been publishing Revolution, now named LiveCode, as a spiritual successor to Hypercard, for a while, and LiveCode now shares one more important trait with Hypercard: It's now free. LiveCode Community Edition is the free, open-source, implementation of LiveCode. LiveCode applications are based on the concepts of "stacks," with each stack containing one or more "cards," and each card containing a mix of shared items (such as background images and fields) and unique items (such as text in a field, or a control which appears on only one card. The entire development and editing environment for LiveCode is written in LiveCode. A second, minor, bug is some interface oddities.
HDFS Architecture Guide Introduction The Hadoop Distributed File System (HDFS) is a distributed file system designed to run on commodity hardware. It has many similarities with existing distributed file systems. However, the differences from other distributed file systems are significant. Assumptions and Goals Hardware Failure Hardware failure is the norm rather than the exception. Streaming Data Access Applications that run on HDFS need streaming access to their data sets. Large Data Sets Applications that run on HDFS have large data sets. Simple Coherency Model HDFS applications need a write-once-read-many access model for files. “Moving Computation is Cheaper than Moving Data” A computation requested by an application is much more efficient if it is executed near the data it operates on. Portability Across Heterogeneous Hardware and Software Platforms HDFS has been designed to be easily portable from one platform to another. NameNode and DataNodes HDFS has a master/slave architecture. The File System Namespace
oVirt Tonido | Run your own Personal Cloud YUMI - Multiboot USB Creator (Windows) YUMI UEFI Changelog 04/28/19 Version 0.0.1.5: Quick fix to support newer Parted Magic 2019. 04/27/19 Version 0.0.1.4: Update to support Manjaro 18.04, System Rescue Cd 6.0.3. Added support for Raspberry Pi Desktop. 02/14/19 Version 0.0.1.3: Update to support Kodachi and Memtest86. 01/06/19 Version 0.0.1.2: Fix to remove duplicate Linux Distributions Menu entry. 01/05/19 Version 0.0.1.1: Update to support Acronis True Image 2019. 12/27/18 Version 0.0.1.0: Fix case in configfile path (change from EFI/boot to EFI/BOOT) in boot/grub/grub.cfg. 11/04/18 Version 0.0.0.9: Update to support newer Ubuntu and derivatives using initrd instead of initrd.lz,.gz, etc. 04/26/18 Version 0.0.0.8: Fix various broken links. 03/10/18 Version 0.0.0.7: Update to support UEFI 32 bit firmware. 12/10/17 Version 0.0.0.6: Update to support AEOMI Backupper. 10/06/17 Version 0.0.0.5: Update to support newer Tails and Manjaro. 01/19/17 Version 0.0.0.4: Fix to replace empty spaces in Distro filename with dashes.
Google File System Un article de Wikipédia, l'encyclopédie libre. Schéma de principe de Google File System Google File System (GFS) est un système de fichiers distribué propriétaire. Il est développé par Google pour leurs propres applications. Il ne paraît pas être publiquement disponible et il est construit sur du code GPL (ext3 et Linux). Conception[modifier | modifier le code] GFS a été conçu pour répondre aux besoins de stockage de données des applications Google, notamment pour tout ce qui concerne ses activités de recherche sur le Web. Il est optimisé pour la gestion de fichiers de taille importante (jusqu'à plusieurs gigaoctets), et pour les opérations courantes des applications Google : les fichiers sont très rarement supprimés ou réécrits, la plupart des accès portent sur de larges zones et consistent surtout en des lectures, ou des ajouts en fin de fichier (record append); GFS a donc été conçu pour accélérer le traitement de ces opérations. Fichiers[modifier | modifier le code]